Skip to content

Conformance and robustness

Jump to bottom
Lucas Baleeiro Dominato edited this page Sep 29, 2022 · 18 revisions

OBS: If you read the article, here more about the tests used in the article

OBS: First to use the tests presents in article use the release version v1.0.0

OBS: For conformance and robustness tests you can use the command line ./app ue to trigger the UE registration. Wireshark can be used to capture any traffic with ngap || sctp || nas || icmp || gtp to visualize procedures for registration of UE.

The configuration file used is different from the one in the master, as it contains a greater number of options. Specified below:

NG-RAN or gNB Configuration:

  • controlif: IP and Port for N2 interface for NG-RAN. NG-RAN will use IP and Port to communicates with AMF and receive NAS/NGAP packets from AMF via SCTP socket. It's usually your machine's ip. Change depending on your environment.

  • dataif: IP and Port for N3 interface for NG-RAN. NG-RAN will use IP and Port to communicates with UPF and receive GTP packets from UPF via UDP socket. It's usually your machine's ip. Change depending on your environment.

  • plmnlist: contains MCC (Mobile Country Code value)/ MNC (Mobile Network Code), TAC (Tracking Area Code) and gnbid information. These information must be consistent with AMF configuration and UE's SUCI.

  • slicesupportlist: The list of slices supported by this gNB by tracking area. It's usually the slice that you will want to connect in the 5G Core. These information must be consistent with AMF configuration

  • test: two options for trigger different behaviors for 5GC in UE Registration flow, set the field with test name to testing:

    • test-normal-registration: put the UEContextRequest field in Initial UE Message. This setting generates a certain message flow in the UE registration
    • test-context-registration: do not put the UEContextRequest field in Initial UE Message. This setting generates a different message flow in the UE registration

UE Configuration:

  • msin: MSIN number of the UE and it is part of IMSI information. The MCC and MNC must be included in hplmn field.

  • key: Permanent Subscription Key. The key must be the same set in web ui of 5GC for UE. This field is used for authentication of UE. Currently the my5GTester only supports 5G-AKA authentication method.

  • opc: Operator Code Value. The key must be the same set in web ui of 5GC for UE. This field is used for authentication of UE.

  • amf: Authentication Management Field (AMF). This field is used for authentication of UE.

  • sqn: Sequence Number. The default value must work in the basics case, e.g, registration of UE. If you want to trigger resynchronization of Sequence Number (SQN) in authentication process with 5GC, try to change this value.

  • dnn: refers information about PDU Session. In this case, specifies the data network for the PDU Session and can be used for SMF/UPF selection.

  • hplmn: the MCC and MNC part of IMSI information for the UE.

  • snssai: refers information about PDU Session. In this case, specifies the slice for the PDU Session and can be used for SMF/UPF selection.

  • integrity: select one integrity and one ciphering algorithm using true.

  • test: options for trigger different behaviors for 5GC in UE Registration flow, set the field with test name to testing:

    • test-imei: send Security Mode Complete message without IMEISV and then sends IMEI in clear-text (if requested by 5GC).
    • test-non-clear-text: send non-clear text IEs as clear text IEs in Registration Request message (for example, 5GMM capability).
    • test-5g-guti: send Registration Request message with 5G-guti not know by AMF for triggering identification procedure.
    • test-without-identity: send Registration Request message without 5GS mobile identity
    • test-resend-registration-request: send Security Mode Complete without a retransmission of Registration Request
    • test-invalid-flows: does not send Security Mode Complete instead, send UL NAS Transport/PDU Session Establishment Request without any NAS context security
    • test-authentication-reject: bypass MAC verification in Authentication Request and sends Authentication Response with invalid response for the challenge of authentication
    • blank: test normal behavior of NAS messages in UE registration

AMF Configuration:

  • Ip: AMF IP address. This information is part of N2 endpoint.
  • Port: AMF Port address. This information is part of N2 endpoint
Clone this wiki locally