PICS PICS_A4_5_2 //AMF - Transport of NAS Messages Procedures - DOWNLINK NAS TRANSPORT
PICS PICS_A4_5_2 //AMF - Transport of NAS Messages Procedures - DOWNLINK NAS
PICS PICS_A4_5_2_1 //AMF - Transport of NAS Messages Procedures - DOWNLINK NAS - ALLOW_SKIP_PIGGY_BACK -IUT conveys REGISTRATION_ACCEPT via DOWNLINK_NAS_TRANSPORT instead of piggybacking it in the INITIAL_CONTEXT_SETUP_REQUEST, when UE_Context_Request_IE is present in the INITIAL_UE_MESSAGE (ref. TS 138 413, clause 9.2.2.1: NAS-PDU IE is optional in INITIAL_CONTEXT_SETUP_REQUEST)
PICS PICS_A4_5_5 //AMF - Transport of NAS Messages Procedures - REROUTE NAS REQUEST
Changes for test_purposes/TP_AMF_NGNAS.tdltx: 4 added lines, 2 removed lines.
Original line number
Diff line number
Diff line
@@ -1086,7 +1086,7 @@ Package TP_AMF_NGNAS {
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 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,
@@ -1106,6 +1106,7 @@ Package TP_AMF_NGNAS {
SD set to PX_SD_1}}}}
to the GNB entity
or
// PICS_NGAP_A4_5_2_1 SKIP_PIGGYBACK
the IUT entity sends a DOWNLINK_NAS_TRANSPORT containing {
NAS_PDU containing {
extended_protocol_discriminator set to 5GS_MOBILITY_MANAGEMENT_MESSAGES,
@@ -1189,7 +1190,7 @@ Package TP_AMF_NGNAS {
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.