- Verify that if IUT receives a SERVICE REQUEST message or a CONTROL PLANE SERVICE REQUEST message before the network-initiated de-registration procedure has been completed (e.g. the DEREGISTRATION REQUEST message is pending to be sent to the UE), the network shall progress the de-registration procedure.
# TP objectives ideas
## 6.3.1.1 (FF)
- TP_5GNAS_AMF_UPA_ACC_01
- Verify that the IUT, upon receiving the PDU SESSION AUTHENTICATION COMPLETE Message after completing the PDU session authentication and authorization procedure, successfully completes the process by sending PDU SESSION ESTABLISHMENT ACCEPT.
## 6.3.1.2.3 Abnormal cases on the network side (FF)
- TP_5GNAS_AMF_UPA_ABN_01
- Verify that the IUT retransmits PDU SESSION AUTHENTICATION COMMAND message after timer T3590 expiration first time.
- TP_5GNAS_AMF_UPA_ABN_02
- Verify that the IUT aborts the procedure after timer T3590 expiration four times.
## 6.4.1.3 UE-requested PDU session establishment procedure accepted by the network (FF)
- TP_5GNAS_AMF_UPE_ACC_01
@@ -191,17 +201,24 @@
- Verify that the IUT sends a PDU SESSION ESTABLISHMENT REJECT with cause #29 (user authentication or authorization failed), when the UE sends a PDU SESSION ESTABLISHMENT REQUEST with type initial request and the provided authentication and authorization data don't match local policy and user's subscription data.
## 6.3.1.1 (FF)
- TP_5GNAS_AMF_UPA_ACC_01
- Verify that the IUT, upon receiving the PDU SESSION AUTHENTICATION COMPLETE Message after completing the PDU session authentication and authorization procedure, successfully completes the process by sending PDU SESSION ESTABLISHMENT ACCEPT.
## 6.4.2.4.1 UE-requested PDU session modification procedure not accepted by the network (FF)
- TP_5GNAS_AMF_UPN_REJ_01
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request of LADN modification and UE outside service area, sends a SESSION MODIFICATION REJECT with reason #46 (out of LADN service area).
## 6.3.1.2.3 Abnormal cases on the network side (FF)
- TP_5GNAS_AMF_UPA_ABN_01
- Verify that the IUT retransmits PDU SESSION AUTHENTICATION COMMAND message after timer T3590 expiration first time.
- TP_5GNAS_AMF_UPN_REJ_02
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a not supported service by the PLMN, sends a SESSION MODIFICATION REJECT with reason #32 (Service option not supported).
- TP_5GNAS_AMF_UPA_ABN_02
- Verify that the IUT aborts the procedure after timer T3590 expiration four times.
- TP_5GNAS_AMF_UPN_REJ_03
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request including a PTI that is already in use, sends a SESSION MODIFICATION REJECT with reason #35 (PTI already in use).
- TP_5GNAS_AMF_UPN_REJ_04
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a wrong 5QI, sends a SESSION MODIFICATION REJECT with reason #59 (Unsupported 5QI value).
## 6.4.3.6 Abnormal cases on the network side (FF)
- TP_5GNAS_AMF_UPR_ABN_01
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST with a wrong PDU Sesiion ID by the UE and not accepts the session release with reason #43 (Invalid PDU session identity).
# TP objectives ideas
## 6.4.3.2, 6.4.3.4 (FF)
- TP_5GNAS_AMF_UPR_ACC_01
@@ -216,32 +233,12 @@
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST by the UE and not accepts the session release with reason #43 (Invalid PDU session identity).
Note: there can be other protocol reasons for not accepting the PDU Session release
## 6.4.3.6 Abnormal cases on the network side (FF)
- TP_5GNAS_AMF_UPR_ABN_01
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST with a wrong PDU Sesiion ID by the UE and not accepts the session release with reason #43 (Invalid PDU session identity).
Note: possible to test? In this case the IUT can't be triggered with a (interface) message.
[KSCH] Potential Tigger is also the UE originateed PDU SESSION RELEASE REQUEST, besides others e.g. O&M Disable SMF
[KSCH] There are several procedures, which can't be triggered with an interfce message. We should not restrict the environment in that way, as the overall test coverage would be reduced drastically. As mentioned above an O&M Interface has to be supported for other reasons as well.
## 6.4.2.4.1 UE-requested PDU session modification procedure not accepted by the network (FF)
- TP_5GNAS_AMF_UPN_REJ_01
- Verify that the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request of LADN modification and UE outside service area, sends a SESSION MODIFICATION REJECT with reason #46 (out of LADN service area).
[KSCH] should read as "Verify the IUT ..."
- TP_5GNAS_AMF_UPN_REJ_02
- Verify that the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a not supported service by the PLMN, sends a SESSION MODIFICATION REJECT with reason #32 (Service option not supported).
[KSCH] should read as "Verify the IUT ..."
- TP_5GNAS_AMF_UPN_REJ_03
- Verify that the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request including a PTI that is already in use, sends a SESSION MODIFICATION REJECT with reason #35 (PTI already in use).
[KSCH] should read as "Verify the IUT ..."
- TP_5GNAS_AMF_UPN_REJ_04
- Verify that the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a wrong 5QI, sends a SESSION MODIFICATION REJECT with reason #59 (Unsupported 5QI value).
[KSCH] should read as "Verify the IUT ..."
[KSCH] General Remark on Test Coverage
Potential Proedures to be tested - for the sake of total test coverage
