WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
1. Only list parameters with expected/set value setting; especially for Mandatory Parameters
2. RAN and AMF O&M Interface required
- Example: TP_NGAP_GNB_IMP_02 - GNB has to send RAN Configuration Update after Config Change via O&M
same is true for AMF Configuration Update.
3. Verification
- Example: If the AMF supports IAB, the AMF shall include the IAB Supported IE in the NG SETUP RESPONSE message. If the
IAB Supported IE is included in the NG SETUP RESPONSE message, the NG-RAN node shall, if supported, store this
information and use it for further AMF selection for the IAB-MT.
Sending Message with mandatory parameters is not an appropriate conformance criterion.
4. Avoid "Generic ensure that when clauses"
- Example: ensure that when "the IUT indicate a Downlink RAN Early Status Transfer procedure"
5. How to trigger?
- Xn-Handover
- N2 Handover
- Radio Link Failure
- ...
# TP (objectives) updated
# TP (objectives) updated
# New TPs required
- NG SETUP REQUEST sent by GNB
NGAP Chapter 8.7.1.2
If the RAN Node Name IE is included in the NG SETUP REQUEST message, the AMF may use this IE as a human
readable name of the NG-RAN node. If the Extended RAN Node Name IE is included in the NG SETUP REQUEST
message, the AMF may use this IE as a human readable name of the NG-RAN node and shall ignore the RAN Node
Name IE if also included.
- NG SETUP RESPONSE sent by AMF
IAB Support - PICS Required
- UE CONTEXT RELEASE REQUEST received by AMF
When GNB sends an UE CONTEXT RELEASE REQUEST the AMF sends UE CONTEXT RELEASE COMMAND
- NG Reset Received by GNB
Partial Interface Reset
- NG Reset Received by AMF
Partial Interface Reset
- UE CONTEXT RELEASE REQUEST sent by GNB
Different reasons and Cause Values
- UPLINK NAS TRANSPORT received by AMF
# TP objective reviewed
# TP objective reviewed
- GNB Interface Management
- TP_NGAP_GNB_IMP_01
- Verify that the GNB node successfully sends an NG SETUP REQUEST message to the AMF.
ETSI TS 138 413 [1], Clauses 8.7.1.2 and 9.2.6.1
Proposal: Verify the GNB Node after TNL establishment sends NG SETUP REQUEST
- TP_NGAP_GNB_IMP_05
- Verify that the GNB node successfully processes an NG RESET message that contains mandatory IEs and answers with NG RESET ACKNOWLEDGE to acknowledge the reset.
ETSI TS 138 413 [1], Clauses 8.7.4.2.1, 9.2.6.11 and 9.2.6.12
Remark: Precondition - UE isRegisteredTo the AMF - Not really
- Verify that the AMF node successfully decline an NG SETUP REQUEST message and answers with NG SETUP FAILURE when the AMF is not able to handle the request.
ETSI TS 138 413 [1], Clauses 8.7.1.3, 9.2.6.1 and 9.2.6.3
Remark: Who To provoke "the AMF is not able to handle the request"
Remark: Specify appropriate Cause Value
- TP_NGAP_AMF_IMP_04
- Verify that the AMF node successfully processes an NG SETUP REQUEST message with different optional fields and answers with NG SETUP RESPONSE to acknowledge the setup.
ETSI TS 138 413 [1], Clauses 8.7.1.2, 9.2.6.1 and 9.2.6.2
Remark: More Specific and Verify behaviour according NGAP chapter 8.7.1.2 and TS 23 501 and TS 23 502
- TP_NGAP_AMF_IMP_05
- Verify that the AMF node successfully processes a RAN CONFIGURATION UPDATE message with RAN CONFIGURATION UPDATE ACKNOWLEDGE to acknowledge the update.
ETSI TS 138 413 [1], Clauses 8.7.2.2, 9.2.6.4 and 9.2.6.5
Remark: How to trigger RAN CONFIGURATION UPDATE Update? More specific check for changed configuration
- TP_NGAP_AMF_IMP_06
- Verify that the AMF node successfully declines a RAN CONFIGURATION UPDATE message with RAN CONFIGURATION UPDATE FAILURE when the AMF is not able to handle the request.
ETSI TS 138 413 [1], Clauses 8.7.2.2 and 9.2.6.4 and 9.2.6.6
Remark: How To provoke "the AMF is not able to handle the request". Verify Specify Cause Value
- TP_NGAP_AMF_IMP_08
- Verify that the AMF node successfully processes an NG RESET message that contains mandatory IEs and answers with NG RESET ACKNOWLEDGE to acknowledge the reset.
ETSI TS 138 413 [1], Clauses 8.7.4.2.2, 9.2.6.11 and 9.2.6.12
Remark: Precondition??? NG_Reset May be sent in any case
Remark: Additional Test for Partial Reset
# GNB Context Management
- TP_NGAP_GNB_CMP_07
- Verify that the NG-RAN node successfully requests the _AMF to release the UE-associated logical NG-connection.
ETSI TS 138 413 [1], Clauses 8.3.2.2 and 9.2.2.4
Remark: How to provoke? e.g. Radio Link Failure, expiry of the timer TNGRELOCOverall, O&M Intervention or
BearerContextInactivityNotification controlled by Inactivity Timer "the AMF is not able to handle the request". Verify Specify Cause Value
Remark: Verify Cause Value
# AMF Context Management
- TP_NGAP_AMF_CMP_01
- Verify that the IUT can send an INITIAL CONTEXT SETUP REQUEST containing mandatory IEs.
ETSI TS 138 413 [1], Clauses 8.3.1.2
Remark: "Verify the IUT correctly sets the UE Context after Authentication and Security procedure has been executed."
Remark: Initial Condition: the UE isRegisteredTo the AMF - This typically is last step in Registration Procedure
Remark: Typically contains NAS Registration Accept Message and there is no PDU Session to be established at this stage - New Test Case?
Remark: Verify UE Radio Capability
Remark: Verify UE Radio Capability for Paging
- TP_NGAP_AMF_CMP_02
- Verify that the IUT can send a UE CONTEXT RELEASE COMMAND that contains both the AMF UE NGAP ID IE and the RAN UE NGAP ID IE.
ETSI TS 138 413 [1], Clauses 8.3.3 and 9.2.2.5
Remark: Verify Cause Value
- TP_NGAP_AMF_CMP_03
- Verify that the IUT can send a UE CONTEXT RELEASE COMMAND where both the AMF UE NGAP ID IE and the RAN UE NGAP ID IE are not available.
ETSI TS 138 413 [1], Clauses 8.3.3
Remark: At least to be re-phased to "only AMF_UE_NGAP_ID is present
Remark: How to trigger?
- TP_NGAP_AMF_CMP_05
- Verify that the IUT can send a CONNECTION ESTABLISHMENT INDICATION that contains mandatory IEs.
ETSI TS 138 413 [1], Clauses 8.3.6.2 and 9.2.2.11
Remark: Copy Paste and "Generic ensure phrase"
# GNB UE Radio Capability Management Procedures
- TP_NGAP_GNB_URP_01
- Verify that the IUT can send a UE_RADIO_CAPABILITY_INFO_INDICATION.
ETSI TS 138 413 [1], Clauses 8.14.1.2 and 9.2.13.1
Remark: IUT sends UE_RADIO_CAPABILITY_INFO_INDICATION after reception of RRC UE Capability Info message
Remark: Requires ASN.1 RRC Message Definition
# AMF Transport of NAS Messages
- TP_NGAP_AMF_NAS_01
- Verify that the IUT can send a DOWNLINK NAS TRANSPORT message to carry NAS information over the NG interface.
ETSI TS 138 413 [1], Clauses 8.6.2.2, 9.2.5.1 and 9.2.5.2
Remark: Expected Behaviour - First Auth and Security Proc to be executed. First DL NAS normally is contained in Initial Context Setup Request
# TP objectives from release 1.1.1
# TP objectives from release 1.1.1
- TP_NGAP_GNB_PDU_01
- TP_NGAP_GNB_PDU_01
- Verify that the NG-RAN node successfully processes a PDU SESSION RESOURCE SETUP REQUEST containing mandatory IEs and answers with PDU SESSION RESOURCE SETUP RESPONSE for successfully established PDU session.
- Verify that the NG-RAN node successfully processes a PDU SESSION RESOURCE SETUP REQUEST containing mandatory IEs and answers with PDU SESSION RESOURCE SETUP RESPONSE for successfully established PDU session.
@@ -75,11 +239,7 @@
- Verify that the NG-RAN node successfully processes an INITIAL CONTEXT SETUP REQUEST containing mandatory IEs and answers with INITIAL CONTEXT SETUP RESPONSE with failed PDU session.
- Verify that the NG-RAN node successfully processes an INITIAL CONTEXT SETUP REQUEST containing mandatory IEs and answers with INITIAL CONTEXT SETUP RESPONSE with failed PDU session.
ETSI TS 138 413 [1], Clauses 8.3.1.2, 9.2.2.1 and 9.2.2.2
ETSI TS 138 413 [1], Clauses 8.3.1.2, 9.2.2.1 and 9.2.2.2
- TP_NGAP_GNB_CMP_07
- TP_NGAP_GNB_CMP_08_
- Verify that the NG-RAN node successfully requests the AMF to release the UE-associated logical NG-connection.
ETSI TS 138 413 [1], Clauses 8.3.2.2 and 9.2.2.4
- TP_NGAP_GNB_CMP_08
- Verify that the NG-RAN node successfully processes a UE CONTEXT RELEASE COMMAND that contains both the AMF UE NGAP ID IE and the RAN UE NGAP ID IE and answers with UE CONTEXT RELEASE COMPLETE with successfully release UE context.
- Verify that the NG-RAN node successfully processes a UE CONTEXT RELEASE COMMAND that contains both the AMF UE NGAP ID IE and the RAN UE NGAP ID IE and answers with UE CONTEXT RELEASE COMPLETE with successfully release UE context.
ETSI TS 138 413 [1], Clauses 8.3.3, 9.2.2.6 and 9.2.2.5
ETSI TS 138 413 [1], Clauses 8.3.3, 9.2.2.6 and 9.2.2.5
@@ -175,10 +335,6 @@
- Verify that the IUT can send a NAS NON DELIVERY INDICATION message to the AMF.
- Verify that the IUT can send a NAS NON DELIVERY INDICATION message to the AMF.
ETSI TS 138 413 [1], Clauses 8.6.4.2 and 9.2.5.4
ETSI TS 138 413 [1], Clauses 8.6.4.2 and 9.2.5.4
- TP_NGAP_GNB_IMP_01
- Verify that the GNB node successfully sends an NG SETUP REQUEST message to the AMF.
ETSI TS 138 413 [1], Clauses 8.7.1.2 and 9.2.6.1
- TP_NGAP_GNB_IMP_02
- TP_NGAP_GNB_IMP_02
- Verify that the IUT can send a RAN CONFIGURATION UPDATE message to the AMF.
- Verify that the IUT can send a RAN CONFIGURATION UPDATE message to the AMF.
ETSI TS 138 413 [1], Clauses 8.7.2.2 and 9.2.6.4
ETSI TS 138 413 [1], Clauses 8.7.2.2 and 9.2.6.4
@@ -191,9 +347,6 @@
- Verify that the GNB node can send an AMF CONFIGURATION UPDATE FAILURE.
- Verify that the GNB node can send an AMF CONFIGURATION UPDATE FAILURE.
ETSI TS 138 413 [1], Clauses 8.7.3.2, 9.2.6.7 aqnd 9.2.6.9
ETSI TS 138 413 [1], Clauses 8.7.3.2, 9.2.6.7 aqnd 9.2.6.9
- TP_NGAP_GNB_IMP_05
- Verify that the GNB node successfully processes an NG RESET message that contains mandatory IEs and answers with NG RESET ACKNOWLEDGE to acknowledge the reset.
ETSI TS 138 413 [1], Clauses 8.7.4.2.1, 9.2.6.11 and 9.2.6.12
- TP_NGAP_GNB_IMP_06
- TP_NGAP_GNB_IMP_06
- Verify that the GNB can send an ERROR INDICATION to the AMF when an error occurs.
- Verify that the GNB can send an ERROR INDICATION to the AMF when an error occurs.
@@ -251,10 +404,6 @@
- Verify that the IUT can send a LOCATION REPORT message that contains mandatory IEs to provide the UE's current location.
- Verify that the IUT can send a LOCATION REPORT message that contains mandatory IEs to provide the UE's current location.
ETSI TS 138 413 [1], Clauses 8.12.3 and 9.2.11.3
ETSI TS 138 413 [1], Clauses 8.12.3 and 9.2.11.3
- TP_NGAP_GNB_URP_01
- Verify that the IUT can send a UE_RADIO_CAPABILITY_INFO_INDICATION.
ETSI TS 138 413 [1], Clauses 8.14.1.2 and 9.2.13.1
- TP_NGAP_GNB_URP_02
- TP_NGAP_GNB_URP_02
- Verify that the IUT can send a UE RADIO CAPABILITY CHECK RESPONSE message that contains mandatory IEs to provide the UE radio capabilities.
- Verify that the IUT can send a UE RADIO CAPABILITY CHECK RESPONSE message that contains mandatory IEs to provide the UE radio capabilities.
ETSI TS 138 413 [1], Clauses 8.14.2.2, 9.2.13.2 and 9.2.13.3
ETSI TS 138 413 [1], Clauses 8.14.2.2, 9.2.13.2 and 9.2.13.3
@@ -291,26 +440,10 @@
- Verify that the AMF node processes a PDU_SESSION_RESOURCE_MODIFY_INDICATION containing mandatory IEs and answers with PDU_SESSION_RESOURCE_MODIFY_CONFIRM for not successfully modified PDU session.
- Verify that the AMF node processes a PDU_SESSION_RESOURCE_MODIFY_INDICATION containing mandatory IEs and answers with PDU_SESSION_RESOURCE_MODIFY_CONFIRM for not successfully modified PDU session.
ETSI TS 138 413 [1], Clauses 8.2.5.2 and 9.2.1.8
ETSI TS 138 413 [1], Clauses 8.2.5.2 and 9.2.1.8
- TP_NGAP_AMF_CMP_01
- Verify that the IUT can send an INITIAL CONTEXT SETUP REQUEST containing mandatory IEs.
ETSI TS 138 413 [1], Clauses 8.3.1.2
- TP_NGAP_AMF_CMP_02
- Verify that the IUT can send a UE CONTEXT RELEASE COMMAND that contains both the AMF UE NGAP ID IE and the RAN UE NGAP ID IE.
ETSI TS 138 413 [1], Clauses 8.3.3 and 9.2.2.5
- TP_NGAP_AMF_CMP_03
- Verify that the IUT can send a UE CONTEXT RELEASE COMMAND where both the AMF UE NGAP ID IE and the RAN UE NGAP ID IE are not available.
ETSI TS 138 413 [1], Clauses 8.3.3
- TP_NGAP_AMF_CMP_04
- TP_NGAP_AMF_CMP_04
- Verify that the IUT can send a UE CONTEXT MODIFICATION REQUEST containing mandatory IEs.
- Verify that the IUT can send a UE CONTEXT MODIFICATION REQUEST containing mandatory IEs.
ETSI TS 138 413 [1], Clauses 8.3.4.2 and 9.2.2.7
ETSI TS 138 413 [1], Clauses 8.3.4.2 and 9.2.2.7
- TP_NGAP_AMF_CMP_05
- Verify that the IUT can send a CONNECTION ESTABLISHMENT INDICATION that contains mandatory IEs.
ETSI TS 138 413 [1], Clauses 8.3.6.2 and 9.2.2.11
- TP_NGAP_AMF_CMP_06
- TP_NGAP_AMF_CMP_06
- Verify that the IUT can send an AMF CP RELOCATION INDICATION that contains mandatory IEs.
- Verify that the IUT can send an AMF CP RELOCATION INDICATION that contains mandatory IEs.
ETSI TS 138 413 [1], Clauses 8.3.7.2 and 9.2.2.12
ETSI TS 138 413 [1], Clauses 8.3.7.2 and 9.2.2.12
@@ -375,9 +508,6 @@
- Verify that the IUT can send a PAGING message to enable the AMF to page a UE.
- Verify that the IUT can send a PAGING message to enable the AMF to page a UE.
ETSI TS 138 413 [1], Clauses 8.5.1.2 and 9.2.4.1
ETSI TS 138 413 [1], Clauses 8.5.1.2 and 9.2.4.1
- TP_NGAP_AMF_NAS_01
- Verify that the IUT can send a DOWNLINK NAS TRANSPORT message to carry NAS information over the NG interface.
ETSI TS 138 413 [1], Clauses 8.6.2.2, 9.2.5.1 and 9.2.5.2
- TP_NGAP_AMF_NAS_02
- TP_NGAP_AMF_NAS_02
- Verify that the IUT can send a REROUTE NAS REQUEST message to reroute the INITIAL UE MESSAGE message to another AMF.
- Verify that the IUT can send a REROUTE NAS REQUEST message to reroute the INITIAL UE MESSAGE message to another AMF.
@@ -387,34 +517,14 @@
- Verify that the AMF node successfully processes an NG SETUP REQUEST message that contains mandatory IEs and answers with NG SETUP RESPONSE to acknowledge the setup.
- Verify that the AMF node successfully processes an NG SETUP REQUEST message that contains mandatory IEs and answers with NG SETUP RESPONSE to acknowledge the setup.
ETSI TS 138 413 [1], Clauses 8.7.1.2, 9.2.6.1 and 9.2.6.2
ETSI TS 138 413 [1], Clauses 8.7.1.2, 9.2.6.1 and 9.2.6.2
- TP_NGAP_AMF_IMP_02
- Verify that the AMF node successfully decline an NG SETUP REQUEST message and answers with NG SETUP FAILURE when the AMF is not able to handle the request.
ETSI TS 138 413 [1], Clauses 8.7.1.3, 9.2.6.1 and 9.2.6.3
- TP_NGAP_AMF_IMP_03
- TP_NGAP_AMF_IMP_03
- Verify that the AMF node successfully processes an NG SETUP REQUEST message with optional field UE Retention Information and answers with NG SETUP RESPONSE to acknowledge the setup.
- Verify that the AMF node successfully processes an NG SETUP REQUEST message with optional field UE Retention Information and answers with NG SETUP RESPONSE to acknowledge the setup.
ETSI TS 138 413 [1], Clauses 8.7.1.2, 9.2.6.1 and 9.2.6.2
ETSI TS 138 413 [1], Clauses 8.7.1.2, 9.2.6.1 and 9.2.6.2
- TP_NGAP_AMF_IMP_04
- Verify that the AMF node successfully processes an NG SETUP REQUEST message with different optional fields and answers with NG SETUP RESPONSE to acknowledge the setup.
ETSI TS 138 413 [1], Clauses 8.7.1.2, 9.2.6.1 and 9.2.6.2
- TP_NGAP_AMF_IMP_05
- Verify that the AMF node successfully processes a RAN CONFIGURATION UPDATE message with RAN CONFIGURATION UPDATE ACKNOWLEDGE to acknowledge the update.
ETSI TS 138 413 [1], Clauses 8.7.2.2, 9.2.6.4 and 9.2.6.5
- TP_NGAP_AMF_IMP_06
- Verify that the AMF node successfully declines a RAN CONFIGURATION UPDATE message with RAN CONFIGURATION UPDATE FAILURE when the AMF is not able to handle the request.
ETSI TS 138 413 [1], Clauses 8.7.2.2 and 9.2.6.4 and 9.2.6.6
- TP_NGAP_AMF_IMP_07
- TP_NGAP_AMF_IMP_07
- Verify that the IUT can send an AMF CONFIGURATION UPDATE message to the AMF.
- Verify that the IUT can send an AMF CONFIGURATION UPDATE message to the AMF.
ETSI TS 138 413 [1], Clauses 8.7.3.2 and 9.2.6.7
ETSI TS 138 413 [1], Clauses 8.7.3.2 and 9.2.6.7
- TP_NGAP_AMF_IMP_08
- Verify that the AMF node successfully processes an NG RESET message that contains mandatory IEs and answers with NG RESET ACKNOWLEDGE to acknowledge the reset.
ETSI TS 138 413 [1], Clauses 8.7.4.2.2, 9.2.6.11 and 9.2.6.12
- TP_NGAP_AMF_IMP_09
- TP_NGAP_AMF_IMP_09
- Verify that the AMF can send an ERROR INDICATION to the GNB when a error occurs.
- Verify that the AMF can send an ERROR INDICATION to the GNB when a error occurs.
