- 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
[KSCH]:Trigger for NW Initiated De-Registration missing. Chapter 5.5.2.3.1 mentions some triggers to perform NW-Initiation De-Registraton e.g. network slice-specific authentication and authorization failure or revocation as specified in subclause 4.6.2.4
- 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
- TP_5GNAS_AMF_DRG_REQ_02
- Verify that the IUT initiates network de-registration by sending a DEREGISTRATION REQUEST message and if UE does not send DEREGISTRATION ACCEPT then IUT retransmits DEREGISTRATION REQUEST message after timer T3522 expiration. NOTE: explicit network deregistration triggered by O&M - UE deregistration
[KSCH]:See above or rephrase to "Verify the in case of T3522 Timeout the IUT re-sends DEREGISTRATION REQUEST" More appropriate reference would be 5.5.2.3.5 Abnormal cases in the network side case a) T3522 time-out
- Verify that the IUT initiates network de-registration by sending a DEREGISTRATION REQUEST message and if UE does not send DEREGISTRATION ACCEPT then IUT retransmits DEREGISTRATION REQUEST message after timer T3522 expiration. **NOTE:** explicit network deregistration triggered by O&M - UE deregistration
- TP_5GNAS_AMF_DRG_REQ_03
- Verify that the IUT initiates network de-registration by sending DEREGISTRATION REQUEST message containing De-registration type IE with re-registration required and the access type based on the UE’s registration status (3GPP access only). NOTE 1: UE sends DEREGISTRATION ACCEPT and starts with re-registration procedure.(also used ref 5.5.2.3.2 1st paragraph) NOTE 2: explicit network deregistration triggered by O&M - UE deregistration
[KSCH]:Trigger for NW Initiated De-Registration missing. Under what circumstances the IUT has to trigger De-Registration and has to include Re-Registration Required and Access Type.
[BPIN]:NOTE's to all above 3 TOs are added to clarify triggering of network de-registration. Triggering of network de-registration is related to O&M.
- Verify that the IUT initiates network de-registration by sending DEREGISTRATION REQUEST message containing De-registration type IE with re-registration required and the access type based on the UE’s registration status (3GPP access only). **NOTE 1:** UE sends DEREGISTRATION ACCEPT and starts with re-registration procedure.(also used ref 5.5.2.3.2 1st paragraph) **NOTE 2:** explicit network deregistration triggered by O&M - UE deregistration
- 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.1.2.8 Abnormal cases on the network side - Initial Registrtaion (SINTESIO)
[BPIN] Those TOs were identified but they may not be for the first round of implementation
- TP_5GNAS_AMF_REG_ABN_01
- Verify that the IUT retransmits the REGISTRATION ACCEPT message and restarts timer T3550 upon the first four expirations.
- TP_5GNAS_AMF_REG_ABN_02
- Verify that the IUT aborts the registration procedure for initial registration and enters the 5GMM-REGISTERED state on the fifth expiry. NOTE: 5GMM-REGISTERED state can be checked over O&M
- TP_5GNAS_AMF_REG_ABN_03
- Verify that the IUT aborts the registration procedure for initial registration and enters the 5GMM-REGISTERED state when a lower layer failure occurs before receiving the REGISTRATION COMPLETE message while timer T3550 is running. NOTE: 5GMM-REGISTERED state can be checked over O&M
- TP_5GNAS_AMF_REG_ABN_04 [BPIN: It shall be investigate what kind of message can be constructed to get proposed cause. Should be possible since 5G-NAS is not ASN1 and therefore type system fully controled by ttcn-3]
- Verify that the IUT responds to a REGISTRATION REQUEST message with a protocol error by sending a REGISTRATION REJECT message with appropriate 5GMM cause values:
#96: Invalid mandatory information
#99: Information element non-existent or not implemented
#100: Conditional IE error
#111: Protocol error, unspecified.
- TP_5GNAS_AMF_REG_ABN_05
- Verify that the IUT aborts the previous registration procedure and initiates a new registration procedure if the information elements in a second REGISTRATION REQUEST message differ from those in the first and if the REGISTRATION COMPLETE message has not been received for first registration.
- TP_5GNAS_AMF_REG_ABN_06
- Verify that the IUT resends the REGISTRATION ACCEPT message and restarts T3550 if the information elements in the first and second REGISTRATION REQUEST message do not differ and if the REGISTRATION COMPLETE message has not been received for first registration. The retransmission counter related to T3550 is not incremented.
- TP_5GNAS_AMF_REG_ABN_07
- Verify that the IUT aborts the registration procedure for initial registration and progresses the de-registration procedure as specified when a DEREGISTRATION REQUEST is received before the REGISTRATION COMPLETE message.
- TP_5GNAS_AMF_REG_ABN_08
- Validate that the AMF rejects a REGISTRATION REQUEST message with invalid or unacceptable UE security capabilities by sending a REGISTRATION REJECT message.
## 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
[BPIN] Those TOs were identified but they may not be 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).
@@ -125,16 +149,16 @@
- 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
- TP_5GNAS_AMF_DRG_ABN_04
- 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
- TP_5GNAS_AMF_DRG_ABN_05
- 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
- TP_5GNAS_AMF_DRG_ABN_06
- 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
- TP_5GNAS_AMF_DRG_ABN_07
- 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.
