U – S

Message/PDU/SDU

–

EXCEPTION: Unless otherwise stated all the messages below are transmitted on the cell specified in the test case.

–

–

–

–

1

The UE transmits an RRCSetupRequest message.

–>

NR RRC: RRCSetupRequest

–

–

2

SS transmit an RRCSetup message.

<–

NR RRC: RRCSetup

–

–

3

The UE transmits an RRCSetupComplete message to confirm the successful completion of the connection establishment and a REGISTRATION REQUEST message indicating "mobility registration updating" is sent to update the registration of the actual tracking area.

–>

NR RRC: RRCSetupComplete

5GMM: REGISTRATION REQUEST

–

–

4

SS sends a REGISTRATION ACCEPT message containing a 5G-GUTI.

(NOTE 1, NOTE 2)

<–

NR RRC: DLInformationTransfer

5GMM: REGISTRATION ACCEPT

–

–

5

Check: Does the UE send a REGISTRATION COMPLETE?

–>

NR RRC: ULInformationTransfer

5GMM: REGISTRATION COMPLETE

–

P

–

EXCEPTION: Step 6a1 describes a step sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value

–

–

–

–

6a1

IF ‘connected without release‘ is not present THEN the SS transmits an RRCRelease message to release RRC connection and move the UE to RRC_IDLE.

<–

NR RRC: RRCRelease

–

–

NOTE 1: If a PDU session status IE was included in the REGISTRATION REQUEST message then the SS includes a PDU session status IE in the REGISTRATION ACCEPT message indicating that all the PDU sessions are active.

NOTE 2: If the UE has indicated S1 mode supported then the SS shall indicate in the 5GS network feature support IE in the REGISTRATION ACCEPT message the IWK N26 bit set to "interworking without N26 not supported". The setting of the "interworking without N26 not supported" has been chosen to ensure that the UE is operating in the single-registration mode allowing for a clearly pre-determined UE behaviour.