Network slicing support in RM510Q-GL

Hi, we acquired a RM510Q-GL module and wanted to know whether network slicing (the selection of a specific SST/SD for a PDU session) is supported.

All of the following AT commands we tried returned an error:

at+cgdcont=1,“IP”,“slicing”,“0.0.0.0”,0,0,0,0,“1”,0
at+cgdcont=1,“IP”,“slicing”,“0.0.0.0”,0,0,0,0,“01”,0
at+cgdcont=1,“IP”,“slicing”,“0.0.0.0”,0,0,0,0,“01.000001”,0

We found the above syntax in the RG520N&RG525F&RG5x0F&RM5x0N Series AT Commands Manual, but not in the RG50xQ&RM5xxQ Series AT Commands Manual. However, when we run at+cgdcont? we see the following:

+CGDCONT: 1,“IP”,“slicing”,“0.0.0.0”,0,0,0,0,“”,0

Given that we see a field where the S-NSSAI would go, we are unsure if our module supports this option.

We would appreciate to know whether the RM510Q-GL module supports slicing or not, and, if yes, how we can configure it.

Thanks in advance and best regards.

Dear @Jorge_Sasiain
Please use the AT command as below:

Hi Silvia, thank you very much for the response. I have looked at the AT command manual and at other posts in this forum.

Our gNB/CN has the following two slices: SST:1 SD:0 ; SST:2 SD:0. I am trying to make the quectel UE use the second.

I have done:

at+c5gnssai=4,“02.000000”
at+cgdcont=4,“IP”,“slicing”,1,“02.000000”,

The results seem good:

at+cgdcont?
+CGDCONT: 1,“IP”,“slicing”,“0.0.0.0”,0,0,0,0,“”,0
+CGDCONT: 2,“IPV4V6”,“ims”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,"“0
+CGDCONT: 3,“IPV4V6”,“sos”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,1,”"0
+CGDCONT: 4,“IP”,“slicing_URLLC000000”,“0.0.0.0”,0,0,0,0,1,“02.000000”,0

AT+C5GNSSAIRDP=0
+C5GNSSAIRDP: 4,“02.000000”

at+cgact?
+CGACT: 1,1
+CGACT: 2,0
+CGACT: 3,0
+CGACT: 4,0

at+cgact=0,1
OK

However, when I try to activate PDU with ID 4:

at+cgact=1,4
ERROR

And indeed I see in the base station logs (“Registration Accept” messages) that the slice is not being used:

Allowed NSSAI:
S-NSSAI
Length of S-NSSAI contents = 1 (SST)
SST = 0x01
Rejected NSSAI:
Rejected S-NSSAI
Length of rejected S-NSSAI = 4
Cause = 0 (S-NSSAI not available in the current PLMN or SNPN)
SST = 0x01
SD = 0x000001

To connect the Quectel UE, I use this command:

qmicli -v --device=/dev/cdc-wdm0 --device-open-proxy --wds-start-network=“ip-type=4,apn=slicing_URLLC000000” --client-no-release-cid

I would appreciate any suggestion. Besides, I’m trying to configure verbose error messages, but even though the at+cmee command is successful, I still see only “ERROR” in error messages:

at+cmee=2
OK
at+cgact=1,4
ERROR

Thank you very much in advance

Dear @Jorge_Sasiain
Did your device register on 5G network?Please check via AT+C5GREG.

Hi Silvia,

This is the output of AT+C5GREG:

at+c5greg=2
OK
at+c5greg?
+C5GREG: 2,1,“1”,“1234501”,11,1,“01”

This is the content of some relevant messages I see being sent:

RRC setup complete

09:34:49.742 [RRC] UL 0031 01 DCCH-NR: RRC setup complete
{
message c1: rrcSetupComplete: {
rrc-TransactionIdentifier 0,
criticalExtensions rrcSetupComplete: {
selectedPLMN-Identity 1,
registeredAMF {
amf-Identifier '800101’H
},
guami-Type native,
dedicatedNAS-Message '7E004171000BF200F1108001014D165C8E2E04F070F070’H
}
}
}

Registration request

09:34:49.742 [NAS] UL 0031 5GMM: Registration request
Protocol discriminator = 0x7e (5GS Mobility Management)
Security header = 0x0 (Plain 5GS NAS message, not security protected)
Message type = 0x41 (Registration request)
5GS registration type:
Follow-on request bit = 0
Value = 1 (initial registration)
ngKSI:
TSC = 0
NAS key set identifier = 7
5GS mobile identity:
5G-GUTI
MCC = 001
MNC = 01
AMF Region ID = 128
AMF Set ID = 4
AMF Pointer = 1
5G-TMSI = 0x4d165c8e
UE security capability:
0xf0 (5G-EA0=1, 128-5G-EA1=1, 128-5G-EA2=1, 128-5G-EA3=1, 5G-EA4=0, 5G-EA5=0, 5G-EA6=0, 5G-EA7=0)
0x70 (5G-IA0=0, 128-5G-IA1=1, 128-5G-IA2=1, 128-5G-IA3=1, 5G-IA4=0, 5G-IA5=0, 5G-IA6=0, 5G-IA7=0)
0xf0 (EEA0=1, 128-EEA1=1, 128-EEA2=1, 128-EEA3=1, EEA4=0, EEA5=0, EEA6=0, EEA7=0)
0x70 (EIA0=0, 128-EIA1=1, 128-EIA2=1, 128-EIA3=1, EIA4=0, EIA5=0, EIA6=0, EIA7=0)

I only see “Requested NSSAI” information in a Security mode complete message in the core (however, from the above messages, it seems that UE requests don’t contain this information):

Requested NSSAI:
S-NSSAI
Length of S-NSSAI contents = 1 (SST)
SST = 0x01
S-NSSAI
Length of S-NSSAI contents = 4 (SST and SD)
SST = 0x01
SD = 0x000001

Dear @Jorge_Sasiain
Is it possible to capture a log via Qlog?

Hi Slivia,

Could you please tell me how to do it or refer me to documentation?

I connect to the module via USB with a laptop running Ubuntu 20.04 (I send AT commands via minicom)

Thanks

Dear @Jorge_Sasiain
As checked internally, you can’t use AT command to dail up, please use external dai up.

For QLog, I will send the tool to you.