RM500Q-AE 5GNSSAI configuration for multiple slices

Hi,
I am trying to configure my quectel module for multiple slices following manual but unable to do so,my setup is as following:
RM500Q-AE with fw:RM500QAEAAR11A03M4G_01.200.01.200
Core: Open5gs v2.7.1
RAN: srsRAN
gNB: USRP B210

I am trying to congigure slices for “00101”

Please let me know if you need any more information!

Hi @jimi_,

please note that you have to use AT+C5GNSSAI=4,"02.000000" according to TS 27.007.

Please include AT logs as code blocks instead of images in the future.

Regards,
Reinhard

Hi @rspmn ,thankyou for your feedback

yes i configured as you suggested but i still can’t connect to repective APN against that sst value and also how can i configure it for particular plmn_id(“00101”) as you can in picture i have multiple sst values for other plmn_id:90170

+C5GNSSAIRDP: 4,"02.000000"
+C5GNSSAIRDP: "00101",,,1,"01"
+C5GNSSAIRDP: "90170",,,10,"07:02.000032:03:04:05:06:01"
CGDCONT: 1,"IP","5g1","0.0.0.0",0,0,0,0,,,,,,,,,"",,,,0
+CGDCONT: 2,"IP","5g1_EMBB","0.0.0.0",0,0,0,0,,,,,,,,1,"01",,,,0
+CGDCONT: 3,"IP","5g2","0.0.0.0",0,0,0,0,,,,,,,,,"",,,,0
+CGDCONT: 4,"IP","5g2_URLLC000000","0.0.0.0",0,0,0,0,,,,,,,,1,"02.000000",,,,0
sudo ./quectel-CM -n 2 -m 1
[05-21_11:19:42:843] QConnectManager_Linux_V1.6.5.1
[05-21_11:19:42:843] Find /sys/bus/usb/devices/2-1 idVendor=0x2c7c idProduct=0x800, bus=0x002, dev=0x003
[05-21_11:19:42:844] Auto find qmichannel = /dev/cdc-wdm0
[05-21_11:19:42:844] Auto find usbnet_adapter = wwan0
[05-21_11:19:42:844] netcard driver = qmi_wwan, driver version = 6.5.0-35-generic
[05-21_11:19:42:844] Modem works in QMI mode
[05-21_11:19:42:880] cdc_wdm_fd = 7
[05-21_11:19:42:964] Get clientWDS = 16
[05-21_11:19:42:996] Get clientDMS = 1
[05-21_11:19:43:028] Get clientNAS = 4
[05-21_11:19:43:060] Get clientUIM = 1
[05-21_11:19:43:092] Get clientWDA = 1
[05-21_11:19:43:123] requestBaseBandVersion RM500QAEAAR11A03M4G
[05-21_11:19:43:252] requestGetSIMStatus SIMStatus: SIM_READY
[05-21_11:19:43:348] requestGetProfile[pdp:2 index:2] 5g1_EMBB///0/IPV4
[05-21_11:19:43:380] requestRegistrationState2 MCC: 1, MNC: 1, PS: Attached, DataCap: 5G_SA
[05-21_11:19:43:412] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[05-21_11:19:43:412] ip addr flush dev wwan0
[05-21_11:19:43:421] ip link set dev wwan0 down
[05-21_11:19:43:860] requestSetupDataCall WdsConnectionIPv4Handle: 0x1f819420
[05-21_11:19:43:988] ip link set dev wwan0 up
[05-21_11:19:43:996] No default.script found, it should be in '/usr/share/udhcpc/' or '/etc//udhcpc' depend on your udhcpc version!
[05-21_11:19:43:996] busybox udhcpc -f -n -q -t 5 -i wwan0
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending select for 10.46.0.3
udhcpc: lease of 10.46.0.3 obtained, lease time 7200
[05-21_11:19:44:146] ip -4 address flush dev wwan0
[05-21_11:19:44:151] ip -4 address add 10.46.0.3/29 dev wwan0
[05-21_11:19:44:159] ip -4 route add default via 10.46.0.4 dev wwan0
^C[05-21_11:19:53:556] requestDeactivateDefaultPDP WdsConnectionIPv4Handle
[05-21_11:19:53:620] ip addr flush dev wwan0
[05-21_11:19:53:632] ip link set dev wwan0 down
[05-21_11:19:53:812] QmiWwanThread exit
[05-21_11:19:53:812] qmi_main exit
sudo ./quectel-CM -n 4 -m 2
[05-21_11:20:01:304] QConnectManager_Linux_V1.6.5.1
[05-21_11:20:01:304] Find /sys/bus/usb/devices/2-1 idVendor=0x2c7c idProduct=0x800, bus=0x002, dev=0x003
[05-21_11:20:01:304] Auto find qmichannel = /dev/cdc-wdm0
[05-21_11:20:01:304] Auto find usbnet_adapter = wwan0
[05-21_11:20:01:305] netcard driver = qmi_wwan, driver version = 6.5.0-35-generic
[05-21_11:20:01:305] Modem works in QMI mode
[05-21_11:20:01:340] cdc_wdm_fd = 7
[05-21_11:20:01:428] Get clientWDS = 16
[05-21_11:20:01:460] Get clientDMS = 1
[05-21_11:20:01:492] Get clientNAS = 4
[05-21_11:20:01:524] Get clientUIM = 1
[05-21_11:20:01:556] Get clientWDA = 1
[05-21_11:20:01:587] requestBaseBandVersion RM500QAEAAR11A03M4G
[05-21_11:20:01:716] requestGetSIMStatus SIMStatus: SIM_READY
[05-21_11:20:01:876] requestGetProfile[pdp:4 index:4] 5g2_URLLC000000///0/IPV4
[05-21_11:20:01:908] requestRegistrationState2 MCC: 1, MNC: 1, PS: Attached, DataCap: 5G_SA
[05-21_11:20:01:940] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[05-21_11:20:01:940] ip addr flush dev wwan0
[05-21_11:20:01:945] ip link set dev wwan0 down
[05-21_11:20:01:972] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
[05-21_11:20:01:972] call_end_reason is 1
[05-21_11:20:01:972] call_end_reason_type is 2
[05-21_11:20:01:972] call_end_reason_verbose is 265
[05-21_11:20:01:972] try to requestSetupDataCall 5 second later
[05-21_11:20:06:996] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
[05-21_11:20:06:996] call_end_reason is 1
[05-21_11:20:06:996] call_end_reason_type is 2
[05-21_11:20:06:996] call_end_reason_verbose is 265
[05-21_11:20:06:996] try to requestSetupDataCall 10 second later
^C[05-21_11:20:08:468] QmiWwanThread exit
[05-21_11:20:08:468] qmi_main exit

Hi @jimi_,

call_end_reason_type 2 is “WDS internal error” and call_end_reason_verbose is not listed in CodeLinaro / qsdk / oss / lklm / gobinet · GitLab so it is hard to tell what is going on here.

Can you check in your Core network that the Allowed NSSAI IE in the NAS 5GS Registration accept
message sent to the RM500Q-AE contains the URLLC SST = 2?

Regards,
Reinhard

hi @rspmn ,
it replied with only sst=01

Regards

@jimi_ Then the AT+C5GNSSAIRDP output is consistent with what the network sent.
Do you see a Requested NSSAI IE in the TS 24.501 Registration request sent from the RM500Q-AE
to the network? If yes, which SST does it contain?

Regards,
Reinhard

Hi @jimi_,
if the UE does not request for registration on a specific slice, it is up to the network which slices it allows.
In a similar (non Open5GS setup) I have seen

        NSSAI - Allowed NSSAI
            Element ID: 0x15
            Length: 9
            S-NSSAI 1
                Length: 1
                Slice/service type (SST): eMBB (1)
            S-NSSAI 2
                Length: 1
                Slice/service type (SST): URLLC (2)
            S-NSSAI 3
                Length: 4
                Slice/service type (SST): MIoT (3)
                Slice differentiator (SD): 50

in the Registration accept.
Your AT+CGNSSAIRDP output for the 90170 network indicates that it allows registration on more than one slice for the RM500Q-AE similar to the example above.

Regards,
Reinhard

hi @rspmn ,
sorry for the confusion i just figured out that actually UE does request NSSAI as shown below,

Regards

Hi @rspmn,following is updated scenario even i changed default NSSAI but i can not assign another NSSAI in
C5GNSSAIRDP info for respective slice and also UE doesn’t request all slices.I have sent you some logs by email also.

please can you help with configuring another NSSAI with my PLMN!

at+cgdcont?

+CGDCONT: 1,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,"",,,,0
+CGDCONT: 2,"IP","5g1_EMBB000000","0.0.0.0",0,0,0,0,,,,,,,,1,"01.000000",,,,0
+CGDCONT: 3,"IP","5g2_URLLC000000","0.0.0.0",0,0,0,0,,,,,,,,1,"02.000000",,,,0

OK
at+c5gnssai?

+C5GNSSAI: 8,"01.000000:02.000000"

OK
at+c5gnssairdp=3

+C5GNSSAIRDP: 8,"01.000000:02.000000"
+C5GNSSAIRDP: "00101",,,4,"01.000000"

OK
at+c5greg=2

OK
at+c5greg?

+C5GREG: 2,1,"000001","00066C000",11,4,"01.000000"

OK

Regfards

Hi @jimi_,

I have also observed the effect that changes to the AT+C5GNSSAI setting are ignored by the device if it already has a valid 5G TMSI from a previous 5G SA network registration.

TS 27.007 also defines a AT+C5GPNSSAI command which seems to provide additional facilities for changing the requested NSSAI. Unfortunately I have not seen a Qualcomm-based device upto SDX62 implementing it.

Try to exchange the SIM with another one which does not have a valid 5G TMSI after you have changed the AT+C5GNSSAI setting and see if it helps.

Retarting your test network would probably also help ot invalidate the 5G TMSI without exchanging SIMs but might not make you too popular with other users of your test network I guess :wink:

Regards,
Reinhard