We have onboarded Free5GC CNFs onto ONAP EMCO and then orchestrated them onto Kubernetes K8s (https://youtu.be/kIMgVwIDwr4). We are now going to do some testing with a commercial UE/gNB emulator. If anybody is interested in collaborating, please let me know.
Hi,
That’s sounds interesting!
If there is anything needed to be modify on free5GC either on config or on NF manager to make it easier to be used, please let us know!
Hello,
We are facing an error while integrating the gNB emulator with the free5G.
UE registration request to AMF is failing for us. Can you please give us some pointers?
The log that we see in the AMF is,
*NFO[2020-10-29T06:47:31Z]/src/amf/gmm/gmm_handler/handler.go:1618 free5gc/src/amf/gmm/gmm_handler.startAuthenticationProcedure() Start authentication procedure AMF=Gmm*
*ERRO[2020-10-29T06:47:31Z]/src/amf/gmm/gmm_handler/handler.go:1649 free5gc/src/amf/gmm/gmm_handler.startAuthenticationProcedure() Nausf_UEAU Authenticate Request Error[Problem Detail: &{Type: Title: Status:0 Detail: Instance: Cause:AV_GENERATION_PROBLEM InvalidParams:[]}] AMF=Gmm*
The log in the AUSF
*INFO[2020-10-28T11:58:15Z]/src/ausf/ausf_producer/UEAuthentication.go:193 free5gc/src/ausf/ausf_producer.HandleUeAuthPostRequest() 403 Forbidden AUSF=UeAuthPost*
*INFO[2020-10-29T06:47:31Z]/src/ausf/ausf_producer/UEAuthentication.go:182 free5gc/src/ausf/ausf_producer.HandleUeAuthPostRequest() Serving network authorized AUSF=UeAuthPost*
*INFO[2020-10-29T06:47:31Z]/src/ausf/ausf_producer/UEAuthentication.go:193 free5gc/src/ausf/ausf_producer.HandleUeAuthPostRequest() 403 Forbidden*
The registration request from the UE,
Frame 1641: 140 bytes on wire (1120 bits), 140 bytes captured (1120 bits)
Linux cooked capture
Internet Protocol Version 4, Src: 192.168.122.142, Dst: 192.168.2.2
Stream Control Transmission Protocol, Src Port: 38422 (38422), Dst Port: 38412 (38412)
NG Application Protocol
NGAP-PDU: initiatingMessage (0)
initiatingMessage
procedureCode: id-InitialUEMessage (15)
criticality: ignore (1)
value
InitialUEMessage
protocolIEs: 4 items
Item 0: id-RAN-UE-NGAP-ID
Item 1: id-NAS-PDU
ProtocolIE-Field
id: id-NAS-PDU (38)
criticality: reject (0)
value
NAS-PDU: 7e004101000d0102f839f0ff000000000047781001002e02…
Non-Access-Stratum 5GS (NAS)PDU
Plain NAS 5GS Message
Extended protocol discriminator: 5G mobility management messages (126)
0000 .... = Spare Half Octet: 0
.... 0000 = Security header type: Plain NAS message, not security protected (0)
Message type: Registration request (0x41)
5GS registration type
.... 0... = Follow-On Request bit (FOR): No follow-on request pending
.... .001 = 5GS registration type: initial registration (1)
NAS key set identifier
0... .... = Type of security context flag (TSC): Native security context (for KSIAMF)
.000 .... = NAS key set identifier: 0
5GS mobile identity
Length: 13
0... .... = Spare: 0
.000 .... = SUPI format: IMSI (0)
.... 0... = Spare: 0
.... .001 = Type of identity: SUCI (1)
Mobile Country Code (MCC): France (208)
Mobile Network Code (MNC): Thales communications & Security (93)
Routing indicator: 0
.... 0000 = Protection scheme Id: NULL scheme (0)
Home network public key identifier: 0
Scheme output: 0000007487
5GMM capability
Element ID: 0x10
Length: 1
0... .... = Spare: 0
.0.. .... = Spare: 0
..0. .... = Spare: 0
...0 .... = Spare: 0
.... 0... = Spare: 0
.... .0.. = LTE Positioning Protocol (LPP) capability: Not Requested
.... ..0. = HO attach: Not supported
.... ...0 = S1 mode: Not Requested
UE security capability
Element ID: 0x2e
Length: 2
1... .... = 5G-EA0: Supported
.1.. .... = 128-5G-EA1: Supported
..0. .... = 128-5G-EA2: Not supported
...0 .... = 128-5G-EA3: Not supported
.... 0... = 5G-EA4: Not supported
.... .0.. = 5G-EA5: Not supported
.... ..0. = 5G-EA6: Not supported
.... ...0 = 5G-EA7: Not supported
1... .... = 5G-IA0: Supported
.1.. .... = 128-5G-IA1: Supported
..0. .... = 128-5G-IA2: Not supported
...0 .... = 128-5G-IA3: Not supported
.... 0... = 5G-IA4: Not supported
.... .0.. = 5G-IA5: Not supported
.... ..0. = 5G-IA6: Not supported
.... ...0 = 5G-IA7: Not supported
NSSAI - Requested NSSAI
Element ID: 0x2f
Length: 2
S-NSSAI 1
Length: 1
Slice/service type (SST): 2
Item 2: id-UserLocationInformation
ProtocolIE-Field
id: id-UserLocationInformation (121)
criticality: reject (0)
value
UserLocationInformation: userLocationInformationNR (1)
userLocationInformationNR
nR-CGI
pLMNIdentity: 02f839
Mobile Country Code (MCC): France (208)
Mobile Network Code (MNC): Thales communications & Security (93)
nRCellIdentity: 0x000e000000
tAI
pLMNIdentity: 02f839
Mobile Country Code (MCC): France (208)
Mobile Network Code (MNC): Thales communications & Security (93)
tAC: 1 (0x000001)
Item 3: id-RRCEstablishmentCause
ProtocolIE-Field
id: id-RRCEstablishmentCause (90)
criticality: ignore (1)
value
RRCEstablishmentCause: highPriorityAccess (1)
Thanks
-Sandeep
Sandeep,
I’ve done something similar myself, also having built both 5GMANO and 5GC running in k8s.
I’d be more than happy to collaborate
Donal