Regarding the "plmn-id" parameter in Nudm or so on SBI messages, it is specified explicitly as json format.
However, your AMF encodes it as plain string format. (ex. plmn-id=00101; here, MCC is "001" and "MNC is "01".)
To Reproduce
Steps to reproduce the behavior:
Start NRF, NSSF, AUSF, PCF and UDM Simulators over my own Tester 1.
Start AMF, SMF and UPF NFs of your free5GC S/W.
Start UE/gNB Simulator over my own Tester 2.
From the UE/gNB Simulator, start "Initial Registration" Test Case.
Monitor and check the N1/N2 and SBI messages through WireShark
Expected behavior
The "plmn-id" parameter should be encoded as like as plmn-id={"mcc"="001", "mnc"="01"}.
Environment (please complete the following information):
Describe the bug
Regarding the "plmn-id" parameter in Nudm or so on SBI messages, it is specified explicitly as json format. However, your AMF encodes it as plain string format. (ex. plmn-id=00101; here, MCC is "001" and "MNC is "01".)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The "plmn-id" parameter should be encoded as like as plmn-id={"mcc"="001", "mnc"="01"}.
Environment (please complete the following information):
PCAP File
1-1_20210625144656_SBI-TestCase-Ph1.1.zip
System architecture (Option)
Additional context
------TS29503_Nudm_SDM.yaml; Line#49---------------------------------
------TS29571_CommonData.yaml; Line#975---------------------------------
PlmnId: type: object properties: mcc: $ref: '#/components/schemas/Mcc' mnc: $ref: '#/components/schemas/Mnc' required: