U – S

Message

1

The SS transmits a Paging message.

<–

NR RRC: Paging

–

–

2

Check: Does the UE transmit an RRCSetupRequest message with ‘establishmentCause’ set to ‘mt-Access’?

–>

NR RRC: RRCSetupRequest

–

P

3

The SS transmits an RRCSetup message.

<–

NR RRC: RRCSetup

–

–

4

Check: Does the UE transmit an RRCSetupComplete message and a SERVICE REQUEST message?

–>

NR RRC: RRCSetupComplete

5GMM: SERVICE REQUEST

–

P

5

The SS transmits a SecurityModeCommand message.

<–

NR RRC: SecurityModeCommand

–

–

6

The UE transmits a SecurityModeComplete message.

–>

NR RRC: SecurityModeComplete

–

–

7

The SS transmits an RRCReconfiguration message and a SERVICE ACCEPT message to establish SRB2 and DRB(s).

The RRCReconfiguration message is configured using RRCReconfiguration-SRB2-DRB(n, m) where n and m are the number of DRB(s) configured with RLC-AM and RLC-UM respectively.

<–

NR RRC: RRCReconfiguration

5GMM: SERVICE ACCEPT

–

–

8

Check: Does the UE transmit an RRCReconfigurationComplete message?

–>

NR RRC: RRCReconfigurationComplete

–

P

–

EXCEPTION: Steps 9a1 to 9b5 describe behaviour that depends on UE configuration; the “lower case letter” identifies a step sequence that takes place if such configuration was conducted.

–

–

–

–

9a1-9a5

IF the UE is configured to use preconditions THEN steps 1-5 of Annex A.16.1 of TS 34.229-5 [47] take place.

–

–

–

–

9b1-9b5

ELSE steps 1-5 of Annex A.16.2 of TS 34.229-5 [47] take place.

–

–

–

–

10

The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND message.

<–

NR RRC: RRCReconfiguration
5GMM: DL NAS TRANSPORT
5GSM: PDU SESSION MODIFICATION COMMAND

–

–

–

EXCEPTION: Depending upon UE implementation, steps 11 and 12 can occur in any order

–

–

–

–

11

The UE transmits an RRCReconfigurationComplete message

–>

NR RRC: RRCReconfigurationComplete

–

–

12

Check: Does the UE transmit a ULInformationTransfer message, an UL NAS TRANSPORT message and an PDU SESSION MODIFICATION COMPLETE message?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMPLETE

–

P

–

EXCEPTION: Steps 13a1 to 13b7 describe behaviour that depends on UE configuration; the “lower case letter” identifies a step sequence that takes place if such configuration was conducted.

–

–

–

–

13a1-13a7

IF the UE is configured to use preconditions THEN steps 6-12 of Annex A.16.1 of TS 34.229-5 [47] take place.

–

–

–

–

13b1-13b5

ELSE steps 6-10 of Annex A.16.2 of TS 34.229-5 [47] take place.

–

–

–

–

Information Element

Value/remark

Comment

Condition

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest SEQUENCE {

establishmentCause

mt-Access

}

}

Information Element

Value/remark

Comment

Condition

Service type

Service type value

’0010’B

Mobile Terminated Services

Information Element

Value/remark

Comment

Condition

PDU session ID

Same value as sent in PDU SESSION ESTABLISHMENT REQUEST message.

Authorized QoS rules

Reference QoS rule #7 as defined in TS 38.508-1, Table 4.8.2.1-7 using conditions IMS_VOICE and IMS_VIDEO.

Authorized QoS flow descriptions

Reference QoS flow #5 and QoS flow #6 as defined in TS 38.508-1, Table 4.8.2.3-5 & Table 4.8.2.3-6 respectively.

Mapped EPS bearer contexts

Not Present

Mapped EPS bearer contexts

Interworking_with_EPS

Mapped EPS bearer context

EPS bearer identity

The same value as the one specified in the Reference QoS flow referred to from the Reference QoS rule indicated in the IE Authorized QoS rules

Operation code

‘001’B

Create new EPS bearer

E bit

‘1’B

Parameters list is included

Number of EPS parameters

’0001’B

1 parameter

Mapped EPS QoS parameters

See reference dedicated EPS bearer context #3 and EPS bearer context #4 in TS 36.508 table 6.6.2-1

Traffic flow Template

See reference dedicated EPS bearer context #3 and EPS bearer context #4 in TS 36.508 table 6.6.2-1

Interworking_with_EPS

If the UE has indicated support of S1, then the SS shall include this IE to provide details for the interworking with EPS being supported for a PDU session. This requirement is set up for the purpose of facilitating the test description. It is not mandatory for the Network to support Mapped EPS bearer contexts.