Commit 131832d9 authored by Bostjan Pintar's avatar Bostjan Pintar
Browse files

new TOs added

parent e9bb9c0a
Loading
Loading
Loading
Loading
+26 −3
Original line number Diff line number Diff line
@@ -91,9 +91,6 @@
- TP_5GNAS_AMF_DRG_ACC_02
    - Verify that the IUT, upon receiving a DEREGISTRATION REQUEST message containing the De-registration type IE with "Switch off" from the UE, does not send a DEREGISTRATION ACCEPT message and IUT completes de-registration procedure.


# TP objectives ideas

## Section 5.5.2.3.1 Network-initiated de-registration procedure initiation (SINTESIO)
- TP_5GNAS_AMF_DRG_REQ_01
    - Verify that the IUT initiates network de-registration by sending a DEREGISTRATION REQUEST message containing De-registration type IE with re-registration not required and the access type based on the UE’s registration status (3GPP access only). NOTE: explicit network deregistration triggered by O&M - deactivation of UE
@@ -113,3 +110,29 @@

- TP_5GNAS_AMF_DRG_REQ_04
    - Verify that if de-registration is triggered due to IUT slice-specific authentication and authorization failure or revocation, the network sets the 5GMM cause value to #62 "No network slices available" and includes the rejected NSSAI IE in the DEREGISTRATION REQUEST message.

# TP objectives ideas

## 5.5.2.3.5 Abnormal cases in the network side (SINTESIO)
[BPIN] Those TOs were identified but they are not for the first round of implementation

- TP_5GNAS_AMF_DRG_ABN_01
    - Verify that the IUT retransmits DEREGISTRATION REQUEST message after timer T3522 expiration four times (i.e. on the fifth expiry of timer T3522, the de-registration procedure shall be aborted).
	
- TP_5GNAS_AMF_DRG_ABN_02	
    - Verify that if IUT receives a DEREGISTRATION REQUEST message with "switch off" indication, before the network-initiated de-registration procedure has been completed, both procedures shall be considered completed.

- TP_5GNAS_AMF_DRG_ABN_03
    - Verify that if IUT receives a DEREGISTRATION REQUEST message without "switch off" indication, before the network-initiated de-registration procedure has been completed, the IUT shall send a DEREGISTRATION ACCEPT message to the UE.

- TP_5GNAS_AMF_REG_ABN_01
    - Verify that if IUT receives a REGISTRATION REQUEST message indicating "initial registration" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the IUT shall aborted the de-registration procedure and the registration procedure shall be progressed.

- TP_5GNAS_AMF_DRG_ABN_04
    - Verify that if IUT sends a DEREGISTRATION REQUEST message without 5GMM cause value #11, #12, #13 or #15 and the IUT receives a REGISTRATION REQUEST message indicating either "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the de-registration procedure shall be progressed, i.e. the REGISTRATION REQUEST message shall be ignored.

- TP_5GNAS_AMF_DRG_ABN_05
    - Verify that if IUT sends a DEREGISTRATION REQUEST message with 5GMM cause value #11, #12, #13 or #15 and the IUT receives a REGISTRATION REQUEST message indicating either "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the de-registration procedure shall be aborted and the registration procedure shall be progressed.

- TP_5GNAS_AMF_SRV_ABN_01
    - 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.