2 RegistrationTPs and de-registration TPs added

# TP objective ideas reviewed

## Section 5.5.1.2.4: Initial registration accepted by the network (SINTESIO)

- Verify that the IUT sends a REGISTRATION ACCEPT message containing the 5GS registration result, TAI list, 5G-GUTI and T3512 when initial registration is accepted by the network.

- Verify that the IUT sends a REGISTRATION ACCEPT message indicating SMS over NAS allowed when initial registration with SMS over NAS is requested and network allows SMS service.

- Verify that the IUT sends a REGISTRATION ACCEPT message indicating SMS over NAS not allowed when initial registration with SMS over NAS is requested and network does not support SMS service.

# TP objectives ideas

- Verify that the IUT stops re-sending an Identity REQUEST message if no Identity RESPONSE message is received on the fifth expiry of timer T3519.

## Section 5.5.1.2.4: Initial registration accepted by the network

- Verify that the IUT sends a REGISTRATION ACCEPT message containing the 5GS registration result, TAI list, 5G-GUTI and T3512 when initial registration is accepted by the network.

- Verify that the IUT sends a REGISTRATION ACCEPT message indicating SMS over NAS allowed when initial registration with SMS over NAS is requested and network allows SMS service.

- Verify that the IUT sends a REGISTRATION ACCEPT message indicating SMS over NAS not allowed when initial registration with SMS over NAS is requested and network does not support SMS service.

## Section 5.5.1.2.4: Initial registration accepted by the network (SINTESIO)

- Verify that the IUT sends a REGISTRATION ACCEPT message containing the allowed NSSAI for the current PLMN and mapped S-NSSAI(s) for the 

allowed NSSAI contained in the requested NSSAI from the UE if the UE included the requested NSSAI in the REGISTRATION REQUEST message and 

the AMF allows one or more S-NSSAIs in the requested NSSAI.

- Verify that the IUT includes the allowed NSSAI in the REGISTRATION ACCEPT message when the UE includes a requested NSSAI in the REGISTRATION REQUEST message and the network allows one or more S-NSSAIs from the requested NSSAI.

- Verify that the IUT sends a REGISTRATION ACCEPT message containing rejected NSSAI if the UE included several requested NSSAI in the REGISTRATION REQUEST message and the AMF rejects one NSSAI.

- Verify that the IUT optionally includes rejected NSSAI in the REGISTRATION ACCEPT message when the network rejects one or more S-NSSAIs from the requested NSSAI.

## Section 8.2.10, 8.2.11

**Note:** This test idea could be unnecessary. Since the messages DL and UL NAS transport are intrinsically linked to PDU Sessions, their functionality is already verified within the scope of sections 6.3 and 6.4.

## Section 5.5.2 De-registration procedure (TBD Sintesio)

## Section 5.5.2.2.3 UE-initiated de-registration procedure completion (SINTESIO)

- Verify that the IUT, upon receiving a DEREGISTRATION REQUEST message containing the De-registration type IE with "Normal de-registration" from the UE, sends a DEREGISTRATION ACCEPT message.

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

## Section 5.5.2.3.1 Network-initiated de-registration procedure initiation (SINTESIO)

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

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

- 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: UE sends DEREGISTRATION ACCEPT and starts with re-registration procedure.(also used ref 5.5.2.3.2 1st paragraph)

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