Commit 22e385fb authored by Yann Garcia's avatar Yann Garcia
Browse files

Review TP_5GNAS_AMF_AUT_ABN_01 and TC_5GNAS_AMF_AUT_ABN_01

parent ccceaa6a
Loading
Loading
Loading
Loading
+4.19 KiB

File added.

No diff preview for this file type.

+3 −2
Changes for etc/Ats_NG_NAS/Ats_NG_NAS_AMF_open5gs.cfg_: 3 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -14,6 +14,7 @@ NGAP_Pics.PICS_NGAP_GNB_IUT := false
NG_NAS_Pics.PICS_NGNAS         := true
NG_NAS_Pics.PICS_NAS_A4_1_2     := true  # 5G AKA based primary authentication and key agreement (TC_5GNAS_AMF_AUT_REQ_xx)
NG_NAS_Pics.PICS_NAS_A4_1_2_2_1 := false # open5gs: AUTHENTICATION REJECT on #20 MAC failure, no identification (TC_5GNAS_AMF_AUT_REQ_04)
NG_NAS_Pics.PICS_NAS_A4_1_2_3_1 := false # open5gs: AUTHENTICATION REJECT on #26 non-5G authentication unacceptable, no identification (TC_5GNAS_AMF_AUT_ABN_01)
NG_NAS_Pics.PICS_NAS_A4_1_2_4   := true  # open5gs re-authenticates on #71 ngKSI already in use (TC_5GNAS_AMF_AUT_REQ_05)

LibNGAP_Pics.PICS_OFFLINE_MODE := false # true to use offline mode with pcap files, false to use online mode with real network functions
@@ -178,9 +179,9 @@ system.utHttpPort.params := "HTTP/TCP(server=127.0.0.1,port=12200,use_ssl=0,debu
# Verify that the IUT sends an IDENTITY_REQUEST message correctly upon receipt of an AUTHENTICATION_FAILURE message indicating a 5GMM cause value #20 - MAC failure
#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_04
# Verify that the IUT sends a new AUTHENTICATION_REQUEST message with new ngKSI value to re-initiate the 5G AKA based primary authentication upon receipt of an AUTHENTICATION_FAILURE message indicating a 5GMM cause value #71 - ngKSI already in use
NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_05
#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_05
# Verify that the IUT sends an IDENTITY_REQUEST message to obtain the SUCI from the UE upon receipt of an AUTHENTICATION_FAILURE message indicating a 5GMM cause value #26 - non-5G authentication unacceptable
#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_ABN_01
NG_NAS_TestCases.TC_5GNAS_AMF_AUT_ABN_01
# Verify that the IUT sends a SECURITY MODE COMMAND message correctly to indicate NAS security mode procedure upon receipt of a NAS AUTHENTICATION RESPONSE
#NG_NAS_TestCases.TC_5GNAS_AMF_SEC_COM_01
# Verify that the IUT, upon receiving the NAS SECURITY MODE COMPLETE message after completing the NAS Authentication and Security procedure, successfully completes the registration process by accepting the registration
+5 −4
Changes for test_purposes/TP_AMF_NGNAS.tdltx: 5 added lines, 4 removed lines.
Original line number Diff line number Diff line
@@ -274,11 +274,12 @@ Package TP_AMF_NGNAS {
                            security_header_type set to NOT_SECURITY_PROTECTED,
                            message_type set to AUTHENTICATION_REQUEST,
                            ngKSI containing {
                                nas_key_set_identifier set to "111"},
                                type_of_security_context set to NATIVE_SECURITY_CONTEXT,
                                nas_key_set_identifier set to RV_NGKSI}, //!any value other than "111" (reserved from network to UE)
                            ABBA containing {
                                ABBA_contents set to " '0000'H "},
                                ABBA_contents set to " '0000'O "},
                            Authentication_parameter_RAND set to RV_Authentication_parameter_RAND,
                            Authentication_parameter_AUTN set to PX_Authentication_parameter_AUTN_NON_5G_UNACCEPTABLE}} //!the "separation bit" in the AMF field of AUTN is set to 0
                            Authentication_parameter_AUTN set to RV_Authentication_parameter_AUTN}} //!built by the IUT, which the test system cannot set: the test system (UE) answers with #26 whatever the AUTN, simulating a UE that finds the "separation bit" of the AMF field of AUTN set to 0; only the UE checks this bit
                to the GNB entity
            }

@@ -288,7 +289,7 @@ Package TP_AMF_NGNAS {
                        the IUT entity receives an UPLINK_NAS_TRANSPORT containing {
                            NAS_PDU containing {
                                extended_protocol_discriminator set to 5GS_MOBILITY_MANAGEMENT_MESSAGES, //!reference ts_124007v180200p: Table 11.2.3.1.1A.1: EPD values 
                                security_header_type set to INTEGRITY_PROTECTED,
                                security_header_type set to NOT_SECURITY_PROTECTED, //!no 5G NAS security context yet
                                message_type set to AUTHENTICATION_FAILURE,
                                5GMM_cause set to "Non-5G authentication unacceptable (26)"}}
                        from the GNB entity 
+7 −0
Changes for ttcn/Ats_NG_NAS/NG_NAS_Pics.ttcn: 7 added lines, 0 removed lines.
Original line number Diff line number Diff line
@@ -31,6 +31,13 @@ module NG_NAS_Pics {
         */
        modulepar boolean PICS_NAS_A4_1_2_2_1 := false;

        /**
         * @desc Does the IUT initiate the identification procedure on receipt of an AUTHENTICATION FAILURE message containing
         *       5GMM cause #26 "non-5G authentication unacceptable"? (optional behaviour, TS 24.501 clause 5.4.1.3.7 d))
         * @see  ETSI TS 103 921-1 Table A.4 (PICS_NAS_A4_1_2_3_1)
         */
        modulepar boolean PICS_NAS_A4_1_2_3_1 := false;

        /**
         * @desc Does the IUT re-initiate the 5G AKA based primary authentication on receipt of an AUTHENTICATION FAILURE message
         *       containing 5GMM cause #71 "ngKSI already in use"? (TS 24.501 clause 5.4.1.3.7 e))
Loading