State 1-NB

Switched OFF

—–

—–

—–

—–

—–

State 2-NB

Attach, Connected Mode

RRC_CONNECTED

0, 1 or 2 data radio bearers configured as specified in the test cases

ECM-CONNECTED

EMM-REGISTERED

0 or 1 default EPS bearer context active and N (0 ≤ N ≤ 1) dedicated EPS bearer active as specified in the test cases.

Not active

State 2A-NB

Attach, Connected Mode, UE Test Mode Activated

RRC_CONNECTED

0, 1 or 2 data radio bearers configured as specified in the test cases

ECM-CONNECTED

EMM-REGISTERED

0 or 1 default EPS bearer context active and N (0 ≤ N ≤ 1) dedicated EPS bearer active as specified in the test cases.

Active

State 2B-NB

Attach, Connected Mode, UE Loopback Activated UL User data transmission pending

RRC_CONNECTED

0,1 or 2 data radio bearers configured as specified in the test cases

ECM-CONNECTED

EMM-REGISTERED

0 or 1 default EPS bearer context active and N (0 ≤ N ≤ 1) dedicated EPS bearer active as specified in the test cases.

Active and Closed

State 3-NB

Registered, Idle Mode

RRC_IDLE

ECM-IDLE

EMM-REGISTERED

0 or 1 default EPS bearer context active as specified in the test cases.

Not active

State 3A-NB

Registered, Idle Mode, UE Test Mode Activated

RRC_IDLE

ECM-IDLE

EMM-REGISTERED

0 or 1 default EPS bearer context active as specified in the test cases.

Active

S1_U_DataTransfer

UE_S1_U_CIoT_Optimisation AND TC_Require_S1_U_DataTransfer

User Plane CIoT Optimisation or S1_U is supported by UE (UE capability), pc_User_Plane_CIoT_Optimisation or pc_S1_U_DataTransfer, and both the Network and test case require Attach with S1_U Data Transfer

UE_S1_U_DataTransfer =pc_User_Plane_CIoT_Optimisation or pc_S1_U_DataTransfer

TC_Require_S1_U_DataTransfer =FALSE

U – S

Message

1

SS transmits system information.

<–

RRC: SYSTEM INFORMATION-NB (BCCH)

1A

Switch-on the UE

–

–

2

UE transmits an RRCConnectionRequest-NB message.

–>

RRC: RRCConnectionRequest-NB

3

SS transmits an RRCConnectionSetup-NB message.

<–

RRC: RRCConnectionSetup-NB

–

EXCEPTION: Steps 4a1 and 4b1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on whether the UE is configured to do Attach Without PDN or not.

–

–

4a1

IF (NOT S1_U_DataTransfer AND px_Do AttachWithoutPDN THEN

The UE transmits an RRCConnectionSetupComplete-NB message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message. An ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST.

–>

RRC: RRCConnectionSetupComplete-NB

NAS: ATTACH REQUEST

NAS: ESM DUMMY MESSAGE

4b1

ELSE

The UE transmits an RRCConnectionSetupComplete-NB message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message. A PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST.

–>

RRC: RRCConnectionSetupComplete-NB

NAS: ATTACH REQUEST

NAS: PDN CONNECTIVITY REQUEST

5

The SS transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure.

<–

RRC: DLInformationTransfer-NB

NAS: AUTHENTICATION REQUEST

6

The UE transmits an AUTHENTICATION RESPONSE message and establishes mutual authentication.

–>

RRC: ULInformationTransfer-NB

NAS: AUTHENTICATION RESPONSE

7

The SS transmits a NAS SECURITY MODE COMMAND message to activate NAS security.

<–

RRC: DLInformationTransfer-NB

NAS: SECURITY MODE COMMAND

8

The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration.

–>

RRC: ULInformationTransfer-NB

NAS: SECURITY MODE COMPLETE

–

EXCEPTION: Steps 9a1 to 9a2 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that take place if the UE has ESM information which needs to be transferred.

–

–

9a1

IF the UE sets the ESM information transfer flag in the PDN CONNECTIVITY REQUEST message sent in step 4b1 THEN the SS transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.

<–

RRC: DLInformationTransfer-NB

NAS: ESM INFORMATION REQUEST

9a2

The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN.

–>

RRC: ULInformationTransfer-NB

NAS: ESM INFORMATION RESPONSE

–

EXCEPTION: Steps 10a1 to 10a2 describe behaviour that depends on UE configuration and test case condition; the "lower case letter" identifies a step sequence that take place if S1_U_DataTransfer condition is evaluated as true.

–

–

10a1

IF S1_U_DataTransfer THEN the SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

10a2

The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

–>

RRC: SecurityModeComplete

11

The SS transmits a UECapabilityEnquiry-NB message to initiate the UE radio access capability transfer procedure.

<–

RRC: UECapabilityEnquiry-NB

12

The UE transmits a UECapabilityInformation-NB message to transfer UE radio access capability.

–>

RRC: UECapabilityInformation-NB

–

EXCEPTION: Steps 13a1 to 13c1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on whether the UE is configured for S1_U_DataTransfer and if not then if it is configured to do Attach Without PDN or not.

–

–

13a1

IF S1_U_DataTransfer THEN the SS transmits a RRCConnectionReconfiguration-NB message to establish the default bearer with condition DRB(1) according to [8.1.8].

This message includes the ATTACH ACCEPT message and the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in the ATTACH ACCEPT

<–

RRC: RRCConnectionReconfiguration-NBNAS: ATTACH ACCEPT

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

13a2

The UE transmits an RRCConnectionReconfigurationComplete-NB message to confirm the establishment of default bearer,

–>

RRC: RRCConnectionReconfigurationComplete-NB

13b1

ELSE IF px_DoAttachWithoutPDN THEN

SS transmits an ATTACH ACCEPT message and an ESM DUMMY MESSAGE is piggybacked in the ATTACH ACCEPT.

<–

RRC: DLInformationTransfer-NB

NAS: ATTACH ACCEPT

NAS: ESM DUMMY MESSAGE

13c1

ELSE

SS transmits an ATTACH ACCEPT message and an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in the ATTACH ACCEPT

If PDN type "IP" was included in the PDN CONNECTIVITY REQUEST step 4b1 then the network shall include the PDN type and the PDN address information within the PDN address IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent to the UE

<–

RRC: DLInformationTransfer-NB

NAS: ATTACH ACCEPT

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

EXCEPTION: Steps 14a1 to 14b1 describe behaviour which depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on whether the UE is configured to do Attach Without PDN or not.

–

–

14a1

IF px_DoAttachWithoutPDN THEN

The UE transmit an ATTACH COMPLETE message and an ESM DUMMY MESSAGE is piggybacked in the ATTACH COMPLETE.

–>

RRC: ULInformationTransfer-NB

NAS: ATTACH COMPLETE

NAS: ESM DUMMY MESSAGE

–

EXCEPTION: IF not all IP address information was allocated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent in steps 13a1 or 13c1 THEN

IF pc_User_Plane_CIoT_Optimisation or pc_S1_U_DataTransfer THEN In parallel to the event described in step 14b1 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 [18] subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

ELSE In parallel to the events described in step 14b1 below the Generic ‘Procedure for IP address allocation in the CP CIoT’ described in TS 36.508 [18], clause 8.1.5A.1 takes place.

–

–

14 b1

ELSE

UE transmits and ATTACH COMPLETE message and an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in the ATTACH COMPLETE.

–>

RRC: ULInformationTransfer-NBNAS: ATTACH COMPLETE

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

ue-Identity-r13

Any allowed value

}

}

}

U – S

Message

0

Switch-on the UE

–

–

1-9a2

Same procedure for steps 0 to 9a2 as specified in the procedure in clause 8.1.5.2.3

–

–

10

The SS transmits an ACTIVATE TEST MODE message to activate test mode procedure.

<–

RRC: DLInformationTransfer-NB

TC: ACTIVATE TEST MODE

11

The UE transmits an ACTIVATE TEST MODE COMPLETE message.

–>

RRC: ULInformationTransfer-NB

TC: ACTIVATE TEST MODE COMPLETE

12a1-16b1

Same procedure for steps 10a1 to 14b1 as specified in the procedure in clause 8.1.5.2.3

–

–

Information Element

Value/remark

Comment

Condition

UE test loop mode

‘00000110’B

UE TEST LOOP MODE G

(NOTE 1)

‘00000111’B

UE TEST LOOP MODE H

(NOTE 1)

‘00001000’B

UE TEST LOOP MODE I

(NOTE 1)

‘00000000’B

UE TEST LOOP MODE A (NOTE 2)

‘00000001’B

UE TEST LOOP MODE B (NOTE 2)

‘00000101’B

UE TEST LOOP MODE F

NOTE 1: UE TEST LOOP MODE G/H/I is applicable only IF NOT S1_U_DataTransfer.

NOTE 2: UE TEST LOOP MODE A/B is applicable only IF S1_U_DataTransfer.

UE – SS

Message

1

The SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode.

<–

RRC: DLInformationTransfer-NB

TC: CLOSE UE TEST LOOP

2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message.

–>

RRC: ULInformationTransfer-NB

TC: CLOSE UE TEST LOOP COMPLETE

Information Element

Value/Remark

Comment

Condition

UE test loop mode

‘00000110’B

UE test loop mode G setup

TL_MODE_G

‘00000111’B

UE test loop mode H setup

TL_MODE_H

‘00001000’B

UE test loop mode

I setup

TL_MODE_I

‘00000101’B

UE test loop mode

F setup

TL_MODE_F

Operation mode and repetitions

TL_MODE_G,

TL_MODE_H

M0

0

return_via_EMM_SMC

1

NBIOT_return_via_RLC

R6..R0

‘0000001’B

1

The received DL message in uplink shall be looped back 1 time (once)

Uplink data delay

‘00000000’B

T_delay_modeG timer=0 sec

SC-MTCH ID

‘0100’H

same value as g-RNTI indicated in the default SCPTMConfiguration-NB message

TL_MODE_F

TL_MODE_G

Test loop mode G is applied

TL_MODE_H

Test loop mode H is applied

TL_MODE_I

Test loop mode I is applied

TL_MODE_F

Test loop mode F is applied

return_via_EMM_SMC

data is returned in uplink at the EMM entity for UE test loop mode G or the SMC SAP for UE test loop mode H

NBIOT_return_via_RLC

data is returned in uplink at the RLC AM-SAP of SRB1bis for NB-IoT UE used in MAC and RLC test cases

UE – SS

Message

1

The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE.

<–

RRC: RRCConnectionRelease-NB

UE – SS

Message

1

The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE.

<–

RRC: RRCConnectionRelease-NB