Remark: Who To provoke "the AMF is not able to handle the request"
Remark: Specify appropriate Cause Value
[BPIN: newly proposed TO to check not matched PLMNs/SNPNs so that TO is more specific:
- Verify that the AMF, upon receiving an NG SETUP REQUEST message containing only PLMNs/SNPNs that it does not recognize or support(or not supported TAC, slice) , rejects the NG Setup procedure by responding with an NG SETUP FAILURE message including the appropriate cause value ("unknown-PLMN-or-SNPN").
See TP_AMF_NGAP_v211.tplan2 file.
]
- 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
[BPIN: I would propose to use TP_NGAP_AMF_IMP_01 where Correct PIXIT for PLMN, TAC and slice(STT+SD) information is set in NG Setup Request supported by AMF.
Then gNB as TS expect NG Setup Response with correct values.
Current TP_NGAP_AMF_IMP_04 already contains plenty of optional IEs. Which would be the best to check?
]
- 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
[BPIN: TO looks fine to me. AMF is SUT. GNB/RAN as TS sends RAN CONFIGURATION UPDATE with i.e additional TAI slice Supported List or TAC]
- 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
[BPIN: Slightly modified TO:
- Verify that the AMF node successfully declines a RAN CONFIGURATION UPDATE message with RAN CONFIGURATION UPDATE FAILURE and appropriate cause value (unknown-PLMN-or-SNPN) when the AMF is not able to handle not suported TAC in the request.
ETSI TS 138 413 [1], Clauses 8.7.2.3 and 9.2.6.4 and 9.2.6.6
Remark: Similar new ones can be done or this one can be modified with not supported PLMN or not supported slice.
]
- 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.
@@ -111,7 +128,11 @@
Remark: Precondition??? NG_Reset May be sent in any case
Remark: Additional Test for Partial Reset
[BPIN: we could put as initial precondition in next step when TP will be written in TDL/TO:
the gNB entity hasEstablished_NG-C_AssociationTo the AMF and
Tests TP_NGAP_AMF_IMP_08(full) and TP_NGAP_AMF_IMP_08_2(partial) are proposed. See TP_AMF_NGAP_v211.tplan2 file.
]
# GNB Context Management
@@ -139,22 +160,30 @@
Remark: Verify UE Radio Capability
Remark: Verify UE Radio Capability for Paging
[BPIN: This one was wrong. One proposal is prepared.]
- 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
[BPIN: Updated.]
- 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?
[BPIN: Updated. I don't know how to trigger. Probably shoud be combined with previous one to expect one or another possibility? Do you agree?]
- 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"
[BPIN: Updated.]
# GNB UE Radio Capability Management Procedures
@@ -174,6 +203,8 @@
Remark: Expected Behaviour - First Auth and Security Proc to be executed. First DL NAS normally is contained in Initial Context Setup Request
[BPIN: DOWNLINK NAS TRANSPORT carry NAS: Authentication request or Security mode command.]
# TP objectives from release 1.1.1
- 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.
