Immediate RRC Release with my Sionna-RK when using an actual UE with B210

[rgeeva]

Hi There...When using an actual UE, I notice authentication and registration is successful with no issue. Immediately after this the RRC Connection is released with the following....

              deprioritisationReq  
                 deprioritisationType = nr
                 deprioritisationTimer = min10

Has anyone seen this before? Is there somewhere to configure this? I haven't quite figured it out. Thanks in advance.

[rgeeva]

Here's a breakdown of the events:

Successful Initial Procedures: The logs show the UE successfully completing the Security Mode Complete and subsequently sending a Registration Complete message after its initial registration.
AMF Communication Failures: Immediately after the Security Mode Complete and while processing the Registration Request within the NAS container, the AMF encountered critical issues:
UDM Communication Failure: At 2026-03-26 13:00:34.237, the AMF attempted to register the UE with the UDM (http://oai-udm:80/nudm-uecm/...), but it failed to get a response (HTTP code: 0).
PCF Communication Failure: Similarly, at 2026-03-26 13:00:34.237, the AMF attempted to establish a policy association with the PCF (/npcf-am-policy-control//policies), but this also failed (HTTP code: 0).
UE Context Release Command: Despite the UE completing its registration and security procedures, the AMF, unable to establish essential network functions with the UDM and PCF, issued a UEContextReleaseCommand at 2026-03-26 13:00:34.331. This command directly leads to the RRC Release.

[SebastianCa]

Hi @rgeeva,
can you please share the amf and gnb log?
Do you use the standard SionnaRK config? Is the sim-card properly configured?

[rgeeva]

OAIAMFlogsMar30.txt
OAIgNBlogsMar30.txt

Thanks again @SebastianCa for your help! AMF and gNB logs are attached. I'm using the standard Sionna RK config. As far as I know, my SIM card is properly configured. There are some separate lab config IMPU and IMPI values that may not be specific to the Sionna RK setup but I don't think it should matter since it does not perform any IMS registration.

[SebastianCa]

This seems to be more a caore network issue; did you modify the dnn entry? According to the logs, it seems as if there is a special character in dnn":"\u0003oai".

[rgeeva]

We are using DNN "oai". Is this what you use?

[SebastianCa]

yes, that's correct. In your amf log is seems as if there is a special character \u0003; please double check that it doesn't come from your config.

[rgeeva]

Thanks @SebastianCa. Is it possible this could be a bug? Can you advise a specific config file that we can check this in?

[SebastianCa]

Please check the config/common/sys_config.yaml

[rgeeva]

Thanks @SebastianCa ...I don't see anything out of the ordinary here unless you see something I don't

################################################################################

Licensed to the OpenAirInterface (OAI) Software Alliance under one or more

contributor license agreements. See the NOTICE file distributed with

this work for additional information regarding copyright ownership.

The OpenAirInterface Software Alliance licenses this file to You under

the OAI Public License, Version 1.1 (the "License"); you may not use this file

except in compliance with the License.

You may obtain a copy of the License at

http://www.openairinterface.org/?page_id=698

Unless required by applicable law or agreed to in writing, software

distributed under the License is distributed on an "AS IS" BASIS,

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and

limitations under the License.

#-------------------------------------------------------------------------------

For more information about the OpenAirInterface (OAI) Software Alliance:

contact@openairinterface.org

################################################################################

OAI CN Configuration File

This file can be used by all OAI NFs

Some fields are specific to an NF and will be ignored by other NFs

NOTE ON YAML ANCHORS

We use YAML anchors to ease the configuration and to avoid duplicating parts of the configuration.

This is especially true for the SNSSAIs, as we have to define them for multiple NFs.

Please note that the use of anchors is not mandatory, and you can define the SNSSAI in each NF yourself.

You can read more about anchors here: https://yaml.org/spec/1.2.2/#anchors-and-aliases

############# Common configuration

Log level for all the NFs

log_level:
general: debug

If you enable registration, the other NFs will use the NRF discovery mechanism

register_nf:
general: no

http_version: 1

############## SBI Interfaces

Each NF takes its local SBI interfaces and remote interfaces from here, unless it gets them using NRF discovery mechanisms

nfs:
amf:
host: oai-amf
sbi:
port: 80
api_version: v1
interface_name: eth0
n2:
interface_name: eth0
port: 38412
smf:
host: oai-smf # 192.168.71.133 Use IP instead of hostname for N4
sbi:
port: 80
api_version: v1
interface_name: eth0
n4:
host: oai-smf #192.168.71.133 Explicitly set SMF N4 IP
port: 8805

upf:
host: oai-upf
sbi:
port: 80
api_version: v1
interface_name: eth0
n3:
interface_name: eth0
port: 2152
n4:
host: oai-upf # 192.168.71.134 UPF's N4 IP on public_net
port: 8805
n6:
interface_name: eth1
n9:
interface_name: eth0
port: 2152

Common for UDR and AMF

database:
host: mysql
user: test
type: mysql
password: test
database_name: oai_db
generate_random: true
connection_timeout: 300 # seconds

general single_nssai configuration

Defines YAML anchors, which are reused in the config file

snssais:

• &embb_slice1
  sst: 1
  sd: "FFFFFF" # 6 hex digits, no 0x prefix - matches Quectel modem request

############## NF-specific configuration
amf:
amf_name: "OAI-AMF"

This really depends on if we want to keep the "mini" version or not

support_features_options:
enable_simple_scenario: yes # "no" by default with the normal deployment scenarios with AMF/SMF/UPF/AUSF/UDM/UDR/NRF.
# set it to "yes" to use with the minimalist deployment scenario (including only AMF/SMF/UPF) by using the internal AUSF/UDM implemented inside AMF.
# There's no NRF in this scenario, SMF info is taken from "nfs" section.
enable_nssf: no
enable_smf_selection: no
relative_capacity: 30
statistics_timer_interval: 20 # in seconds
emergency_support: false
served_guami_list:
- mcc: 262
mnc: 99
amf_region_id: 01
amf_set_id: 001
amf_pointer: 01
plmn_support_list:
- mcc: 262
mnc: 99
tac: 0x0001
nssai:
- *embb_slice1
supported_integrity_algorithms:
- "NIA0"
- "NIA1"
- "NIA2"
supported_encryption_algorithms:
- "NEA0"
- "NEA1"
- "NEA2"

smf:
ue_mtu: 1500
support_features:
use_local_subscription_info: yes # Use infos from local_subscription_info or from UDM
use_local_pcc_rules: yes # Use infos from local_pcc_rules or from PCF
upfs:
- host: 192.168.71.134 # UPF's N4 on traffic_net (SMF auto-bound to this network) - FIXED: was 192.168.72.134
port: 8805
config:
enable_usage_reporting: no
# follows UPFInfo from 3GPP TS 29.510, currently only these values from interfaceUpfInfoList are supported
upf_info:
sNssaiUpfInfoList:
- sNssai: *embb_slice1
dnnUpfInfoList:
- dnn: "oai"
interfaceUpfInfoList:
- interfaceType: "N3"
networkInstance: "access.oai.org"
- interfaceType: "N6"
networkInstance: "core.oai.org"
ue_dns:
primary_ipv4: "8.8.8.8"
primary_ipv6: "2001:4860:4860::8888"
secondary_ipv4: "8.8.8.8"
secondary_ipv6: "2001:4860:4860::8888"
ims:
pcscf_ipv4: "127.0.0.1"
pcscf_ipv6: "fe80::7915:f408:1787:db8b"

the DNN you configure here should be configured in "dnns"

follows the SmfInfo datatype from 3GPP TS 29.510

smf_info:
sNssaiSmfInfoList:
- sNssai: *embb_slice1
dnnSmfInfoList:
- dnn: "oai"
local_subscription_infos:
- single_nssai: *embb_slice1
dnn: "oai"
qos_profile:
5qi: 9
session_ambr_ul: "200Mbps"
session_ambr_dl: "400Mbps"

upf:
support_features:
enable_bpf_datapath: no # If "on": BPF is used as datapath else simpleswitch is used, DEFAULT= off
enable_snat: yes # If "on": Source natting is done for UE, DEFAULT= off
remote_n6_gw: "192.168.72.135" # Dummy host since simple-switch does not use N6 GW
upf_info:
sNssaiUpfInfoList:
- sNssai: *embb_slice1
dnnUpfInfoList:
- dnn: "oai"

DNN configuration

dnns:

• dnn: "oai"
  pdu_session_type: "IPV4"
  ipv4_subnet: "12.1.1.0/24"

[SebastianCa]

This looks fine. Have you modified anything in the configuration files? Could you please test it using the default configs provided on GitHub?

[rgeeva]

Just to be 100% sure, we'll try a fresh install and get back to you. Thanks @SebastianCa

[rgeeva]

FYI @SebastianCa . Once we disabled IPV6 on the module everything worked fine. Thanks for your support!