Changes for test_purposes/NGNAS_Common.tdltx: 4 added lines, 3 removed lines.
Original line number
Diff line number
Diff line
@@ -15,7 +15,8 @@ Package NGNAS_Common {
Event indicateUEdeactivation //The UE is administratively deactivated in the 5GC.
Event indicateUEderegistration //The UE is administratively de-registered in the 5GC.
Event hasSubscribedSNSSAIAllowedByAMF // The UE has a subscribed S-NSSAI configured for the test which is allowed by the AMF in the current registration area.
Event hasNoValidNasSecurityContext // Indicates that the UE has no valid 5G NAS security context available for protecting the initial NAS message.
Event hasValidNasSecurityContext // Indicates that the UE has valid 5G NAS security context available for protecting the initial NAS message.
// This template may be used as default AUTHENTICATION REQUEST message within a DOWNLINK NAS TRANSPORT message. */
@@ -26,7 +27,7 @@ Package NGNAS_Common {
security_header_type set to NOT_SECURITY_PROTECTED,
message_type set to AUTHENTICATION_REQUEST,
ngKSI containing {
nas_key_set_identifier set to "111"},
nas_key_set_identifier set to RV_NGKSI},
ABBA containing {
ABBA_contents set to " '0000'H "},
Authentication_parameter_RAND set to RV_Authentication_parameter_RAND,
@@ -47,7 +48,7 @@ Package NGNAS_Common {
type_of_ciphering_algorithm set to PX_SELECTED_NAS_CIPHERING_ALGORITHM,
type_of_integrity_algorithm set to PX_SELECTED_NAS_INTEGRITY_ALGORITHM },
ngKSI containing {
nas_key_set_identifier set to "111" },
nas_key_set_identifier set to RV_NGKSI },
replayed_UE_security_capabilities set to PX_UE_SECURITY_CAPABILITIES}} // UE security capability 9.11.3.54
Changes for test_purposes/TP_AMF_NGNAS.tdltx: 94 added lines, 8 removed lines.
Original line number
Diff line number
Diff line
@@ -934,7 +934,7 @@ Package TP_AMF_NGNAS {
}
}// end TP_5GNAS_AMF_REG_ACC_05
Test Purpose TP_5GNAS_AMF_REG_ACC_06 {
Test Purpose TP_5GNAS_AMF_REG_ACC_06 { //!SUCI case
Objective: "Verify that, during the initial registration procedure, when the REGISTRATION_REQUEST message contains a Requested NSSAI IE with one S-NSSAI that is allowed by the IUT, then the IUT sends a REGISTRATION_ACCEPT message containing an Allowed NSSAI IE with the requested S-NSSAI."
@@ -949,14 +949,15 @@ Package TP_AMF_NGNAS {
the UE entity isNotRegisteredToAMF and
the UE entity hasNoValidNasSecurityContext and
the IUT entity receives an INITIAL_UE_MESSAGE containing {
UE_Context_Request_IE set to "requested", //reference ts_138413v171500p, clause 8.6.1.2: presence of this IE obliges the AMF to trigger the Initial Context Setup procedure
UE_Context_Request_IE set to "requested", //!reference ts_138413v171500p, clause 8.6.1.2: presence of this IE obliges the AMF to trigger the Initial Context Setup procedure
NAS_PDU containing {
extended_protocol_discriminator set to 5GS_MOBILITY_MANAGEMENT_MESSAGES,
security_header_type set to NOT_SECURITY_PROTECTED,
message_type set to REGISTRATION_REQUEST,
5GS_registration_type containing {
5GS_registration_type_value set to INITIAL_REGISTRATION,
Follow_on_request_indicator set to FOLLOW_ON_REQUEST_PENDING}, //deliberately set to "pending" so that the connection-release condition of TS 123 502 [2], clause 4.2.2.2.2, bullet 22 does not apply; this TP verifies Allowed NSSAI only and is kept independent from any subsequent connection release behaviour
5GS_registration_type_value set to INITIAL_REGISTRATION}, //Follow-On Request Indicator not asserted: this TP verifies Allowed NSSAI only and is independent of connection-release behaviour (TS 123 502 [2], clause 4.2.2.2.2/22), which is covered by a separate TP
ngKSI containing {
nas_key_set_identifier set to "111"}, //!cleartext IE (ref. clause 4.4.6 cleartext IE list); value "111" = "no key is available" (TS 124 501 [1], clause 9.11.3.32), consistent with hasNoValidNasSecurityContext
5GS_mobile_identity containing {
SUPI_format set to IMSI,
Type_of_identity set to SUCI,
@@ -965,7 +966,7 @@ Package TP_AMF_NGNAS {
Routing_indicator set to PX_ROUTING_INDICATOR,
Protection_scheme_id set to PX_PROTECTION_SCHEME_ID,
Home_network_public_key_identifier set to PX_HOME_NETWORK_PUBLIC_KEY_IDENTIFIER,
MSIN set to PX_MSIN}}} //cleartext IEs only; Requested NSSAI is a non-cleartext IE and is therefore not present here (see TS 124 501 [1], clause 4.4.6)
MSIN set to PX_MSIN}}} //!cleartext IEs only; Requested NSSAI is a non-cleartext IE and is therefore not present here (see TS 124 501 [1], clause 4.4.6)
from the GNB entity and
event SECURITY_MODE_COMMAND occurs
}
@@ -984,8 +985,9 @@ Package TP_AMF_NGNAS {
security_header_type set to NOT_SECURITY_PROTECTED,
message_type set to REGISTRATION_REQUEST,
5GS_registration_type containing {
5GS_registration_type_value set to INITIAL_REGISTRATION,
Follow_on_request_indicator set to FOLLOW_ON_REQUEST_PENDING},
5GS_registration_type_value set to INITIAL_REGISTRATION},
ngKSI containing {
nas_key_set_identifier set to "111"}, //!echoes the value as originally composed by the UE before security establishment (ref. clause 4.4.6 a)1): "the entire REGISTRATION REQUEST message")
5GS_mobile_identity containing {
SUPI_format set to IMSI,
Type_of_identity set to SUCI,
@@ -997,7 +999,7 @@ Package TP_AMF_NGNAS {
MSIN set to PX_MSIN},
Requested_NSSAI containing {
S_NSSAI_1 containing {
SST set to PX_SST_1, //PX_SST_1/PX_SD_1 identify an S-NSSAI that must be provisioned as allowed in the UE's subscription data at the AMF/UDM (IXIT precondition, not modelled as an Event)
SST set to PX_SST_1, //!PX_SST_1/PX_SD_1 identify an S-NSSAI that must be provisioned as allowed in the UE's subscription data at the AMF/UDM (PIXIT precondition)
SD set to PX_SD_1}}}}}}
from the GNB entity
}
@@ -1025,6 +1027,90 @@ Package TP_AMF_NGNAS {
}
}// end TP_5GNAS_AMF_REG_ACC_06
Test Purpose TP_5GNAS_AMF_REG_ACC_06_1 { //!5G-GUTI case of TP_5GNAS_AMF_REG_ACC_06
Objective: "Verify that, during the initial registration procedure, when the REGISTRATION_REQUEST message contains a Requested NSSAI IE with one S-NSSAI that is allowed by the IUT, then the IUT sends a REGISTRATION_ACCEPT message containing an Allowed NSSAI IE with the requested S-NSSAI."
the IUT entity receives an INITIAL_UE_MESSAGE containing {
UE_Context_Request_IE set to "requested", //!reference ts_138413v171500p, clause 8.6.1.2: presence of this IE obliges the AMF to trigger the Initial Context Setup procedure
NAS_PDU containing {
extended_protocol_discriminator set to 5GS_MOBILITY_MANAGEMENT_MESSAGES,
security_header_type set to INTEGRITY_PROTECTED, //!ref. TS 124 501 [1], clause 4.4.6: "the UE shall set the security header type of the initial NAS message to 'integrity protected'" when a NAS message container IE is included
message_type set to REGISTRATION_REQUEST,
5GS_registration_type containing {
5GS_registration_type_value set to INITIAL_REGISTRATION},
ngKSI containing {
nas_key_set_identifier set to RV_NGKSI},
5GS_mobile_identity containing {
Type_of_identity set to 5G_GUTI, //!cleartext IE; native 5G-GUTI previously assigned to the UE
MCC set to PX_MCC,
MNC set to PX_MNC,
AMF_Region_ID set to PX_AMF_REGION_ID,
AMF_Set_ID set to PX_AMF_SET_ID,
AMF_Pointer set to PX_AMF_POINTER,
5G_TMSI set to RV_5G_TMSI},
NAS_message_container containing { //!ciphered non-cleartext IEs, included in the same REGISTRATION_REQUEST message (ref. clause 4.4.6 b)1), no SECURITY_MODE_COMMAND/COMPLETE exchange needed
NAS_PDU containing {
extended_protocol_discriminator set to 5GS_MOBILITY_MANAGEMENT_MESSAGES,
security_header_type set to NOT_SECURITY_PROTECTED,
message_type set to REGISTRATION_REQUEST,
5GS_registration_type containing {
5GS_registration_type_value set to INITIAL_REGISTRATION},
ngKSI containing {
nas_key_set_identifier set to RV_NGKSI},
5GS_mobile_identity containing {
Type_of_identity set to 5G_GUTI,
MCC set to PX_MCC,
MNC set to PX_MNC,
AMF_Region_ID set to PX_AMF_REGION_ID,
AMF_Set_ID set to PX_AMF_SET_ID,
AMF_Pointer set to PX_AMF_POINTER,
5G_TMSI set to RV_5G_TMSI},
Requested_NSSAI containing {
S_NSSAI_1 containing {
SST set to PX_SST_1, //!PX_SST_1/PX_SD_1 identify an S-NSSAI that must be provisioned as allowed in the UE's subscription data at the AMF/UDM (PIXIT precondition)
SD set to PX_SD_1}}}}}}
from the GNB entity
}
then {
//NOTE: REGISTRATION_ACCEPT may be carried within INITIAL_CONTEXT_SETUP_REQUEST or within DOWNLINK_NAS_TRANSPORT, depending on IUT implementation; no explicit normative statement mandating one or the other has been identified in TS 138 413, TS 124 501 or TS 123 502. INITIAL_CONTEXT_SETUP_REQUEST is used here, consistent with TP_5GNAS_AMF_REG_ACC_01/04/05/06 and with the UE_Context_Request_IE set to "requested" in the Initial conditions above; pending confirmation with interoperability partners, this may be revised to allow both alternatives.
the IUT entity sends a INITIAL_CONTEXT_SETUP_REQUEST containing {
NAS_PDU containing {
extended_protocol_discriminator set to 5GS_MOBILITY_MANAGEMENT_MESSAGES,
security_header_type set to INTEGRITY_PROTECTED_AND_CIPHERED,
message_type set to REGISTRATION_ACCEPT,
5G_GUTI containing {
Type_of_identity set to 5G_GUTI,
MCC set to PX_MCC,
MNC set to PX_MNC,
AMF_Region_ID set to PX_AMF_REGION_ID,
AMF_Set_ID set to PX_AMF_SET_ID,
AMF_Pointer set to PX_AMF_POINTER,
5G_TMSI set to RV_5G_TMSI},
Allowed_NSSAI containing {
S_NSSAI_1 containing {
SST set to PX_SST_1,
SD set to PX_SD_1}}}}
to the GNB entity
}
}
}// end TP_5GNAS_AMF_REG_ACC_06_1
Test Purpose TP_5GNAS_AMF_REG_REJ_01 {
Objective: "Verify that the IUT sends a REGISTRATION_REJECT message with 5GMM cause value #22 'congestion' and includes the T3346 value IE when the initial registration request is rejected due to general NAS level mobility management congestion control."