U – S

Message

–

EXCEPTION: Steps 1 to 2 below describe behaviour that depends on the contents of the latest PDN CONNECTIVITY REQUEST message sent by the UE prior to this procedure.

–

–

1

If the "PDN type" in the latest PDN CONNECTIVITY REQUEST message prior to this procedure was ‘IPv6’ or ‘IPv4v6’ then stateless address auto configuration may occurs over SRB1bis, UE may send an ICMPv6 Router Solicitation

–>

RRC: ULInformationTransfer-NB

NAS: ESM DATA TRANSPORT

2

The SS sends an ICMPv6 Router Advertisement containing the IPv6 prefix.

<–

RRC: DLInformationTransfer-NB

NAS: ESM DATA TRANSPORT

U – S

Message/PDU/SDU

1

SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordLists.

<–

RRC: Paging-NB

–

–

2

Check: Does the UE transmit an RRCConnectionRequest-NB message "mt-access"?

–>

RRC: RRCConnectionRequest-NB

–

P

3

SS transmits an RRCConnectionSetup-NB message.

<–

RRC: RRCConnectionSetup-NB

–

–

–

EXCEPTION: Steps 4a1a1 to 4a1b3b1 describe behaviour which depends on UE implementation; the "lower case letter" identifies a step sequence which takes place depending on whether the UE is configured or not to establish PDN upon establishing RRC connection and whether UE has pending data to transmit.

–

–

–

–

4a1a1

IF UE is configured to establish PDN upon establishing RRC connection and UE has pending data to transmit THEN

Check: Does the UE transmit an RRCConnectionSetupComplete-NB message and a CONTROL PLANE SERVICE REQUEST message containing a ESM DATA TRANSPORT message in the ESM message container IE?

–>

RRC: RRCConnectionSetupComplete-NB

NAS: CONTROL PLANE SERVICE REQUEST

NAS: ESM DATA TRANSPORT

–

P

4a1b1

ELSE

Check: Does the UE transmit an RRCConnectionSetupComplete-NB message and a CONTROL PLANE SERVICE REQUEST message not containing user data (there is not yet a PDN) not containing a PDN CONNECTIVITY REQUEST message?

–>

RRC: RRCConnectionSetupComplete-NB

NAS: CONTROL PLANE SERVICE REQUEST

–

P

4a1b2

SS starts wait timer 2 sec.

Note: The Service request procedure success is guarded in the UE by timer T3417 = 5 sec after which expiry without any DL action the UE will consider the procedure as failed.

–

–

–

–

–

EXCEPTION: Steps 4a1b3a1 to 4a1b3a4 describe behaviour which depends on UE implementation; the "lower case letter" identifies a step sequence which takes place depending on whether the UE is configured or not to establish PDN in RRC-CONNECTED after it sends the CONTROL PLANE SERVICE REQUEST message.

–

–

–

–

4a1b3a1

The UE transmits a PDN CONNECTIVITY REQUEST message.

–>

RRC: ULInformationTransfer-NB

NAS: PDN CONNECTIVITY REQUEST

–

–

4a1b3a2

Stop timer wait timer 2 sec.

–

–

–

–

4a1b3a3

The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

<–

RRC: DLInformationTransfer-NB

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

–

–

EXCEPTION: IF pc_IP_PDN AND not all IP address information was allocated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent in step 4a1b3a3 TNEN

In parallel to the events described in steps 4a1b3a4 the Generic ‘Procedure for IP address allocation in the CP CIoT’ described in TS 36.508 [18], clause 8.1.5A.1 takes place.

–

–

–

–

4a1b3a4

The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message.

–>

RRC: ULInformationTransfer-NB

NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

–

–

4a1b3b1

Timer 2 sec expires

–

–

–

–

5

The SS transmits a SERVICE ACCEPT message.

<–

RRC: DLInformationTransfer-NB

NAS: SERVICE ACCEPT

–

–

Information Element

Value/Remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mt-Access

}

}

}

Information Element

Value/Remark

Comment

Condition

RRCConnectionSetupComplete-NB ::= SEQUENCE {

rrc-TransactionIdentifier

the same value as included in the RRCConnectionSetup-NB message received from SS

criticalExtensions CHOICE {

rrcConnectionSetupComplete-r13 SEQUENCE {

attachWithoutPDN-Connectivity-r13

True

px_DoAttachWithoutPDN

Not Present

NOT px_DoAttachWithoutPDN

}

}

}

Information Element

Value/Remark

Comment

Condition

Access point name

Not Present or Any allowed value

Protocol configuration options

Not Present

Header compression configuration

Any allowed value

pc_HCCPCIoT AND pc_IP_PDN

Extended protocol configuration options

Not Present or Any allowed value

Information Element

Value/Remark

Comment

Condition

Protocol configuration options

Not present

Header compression configuration

0000H

No Compression profile

NOTE: For the purposes of CIoT (NAS) testing regardless of the Compression files supported by the UE and indicated in the PDN CONNECTIVITY REQUEST, the SS does not agree header compression to be applied.

pc_HCCPCIoT AND pc_IP_PDN

Control plane only indication

‘0001’B

PDN connection can be used for control plane CIoT EPS optimization only

Extended protocol configuration options

The content of the IE below uses the same fields and Conditions (and their meaning) as those defined in TS 36.508 [18] for the IE ‘Protocol configuration options’

Container ID n

‘0003’H

n assigned to next available number

DNS IPv6

Length of container ID n contents

Length value determined by the TTCN implementation

Container ID n contents

IPv6 address

DNS IPv6 Address

Container ID n+1

‘000D’H

n assigned to next available number

DNS IPv4

Length of container ID n+1 contents

Length value determined by the TTCN implementation

Container ID n+1 contents

IPv4 address

DNS IPv4 Address

Serving PLMN rate control

‘11111111 11111111’B

Unrestricted

Max number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send via a PDN connection per 6 minute interval

Information Element

Value/Remark

Comment

Condition

Protocol configuration options

Not present

Extended protocol configuration options

Not present or any allowed value

U – S

Message/PDU/SDU

1

Check: Does the UE transmit an RRCConnectionRequest-NB message?

–>

RRC: RRCConnectionRequest-NB

–

P

2

SS transmits an RRCConnectionSetup-NB message.

<–

RRC: RRCConnectionSetup-NB

–

–

–

EXCEPTION: Steps 3a1 to 3b1 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.

–

–

–

–

3a1a1

Void.

–

–

–

–

3a1b1

IF px_DoAttachWithoutPDN THEN

Check: Does the UE transmit an RRCConnectionSetupComplete-NB message and a CONTROL PLANE SERVICE REQUEST message?

–>

RRC: RRCConnectionSetupComplete-NB

NAS: CONTROL PLANE SERVICE REQUEST

–

P

3a1b2

Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message?

–>

RRC: ULInformationTransfer-NB

NAS: PDN CONNECTIVITY REQUEST

–

P

3a2

The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

<–

RRC: DLInformationTransfer-NB

NAS:

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

–

–

EXCEPTION: IF pc_IP_PDN AND not all IP address information was allocated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent in step 3a2 TNEN

In parallel to the events described in steps 3a3 the Generic ‘Procedure for IP address allocation in the CP CIoT’ described in TS 36.508 [18], clause 8.1.5A.1 takes place.

–

–

–

–

3a3

Check: Does the UE transmit an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?

–>

RRC: ULInformationTransfer-NB

NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

–

P

3a4

Check: Does the UE send an ESM DATA TRANSPORT message containing user data?

–>

RRC: ULInformationTransfer-NB

NAS: ESM DATA TRANSPORT

–

P

3b1

ELSE (NOT px_DoAttachWithoutPDN)

Check: Does the UE transmit an RRCConnectionSetupComplete-NB message and a CONTROL PLANE SERVICE REQUEST message containing user data encapsulated in an ESM DATA TRANSPORT message included in the ESM message container IE?

–>

RRC: RRCConnectionSetupComplete-NB

NAS: CONTROL PLANE SERVICE REQUEST

NAS: ESM DATA TRANSPORT

–

P

4

The SS transmits a SERVICE ACCEPT message.

<–

RRC: DLInformationTransfer-NB

NAS: SERVICE ACCEPT

–

–

Information Element

Value/Remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-data

}

}

}

Information Element

Value/Remark

Comment

Condition

RRCConnectionSetupComplete-NB ::= SEQUENCE {

rrc-TransactionIdentifier

the same value as included in the RRCConnectionSetup-NB message received from SS

criticalExtensions CHOICE {

rrcConnectionSetupComplete-r13 SEQUENCE {

attachWithoutPDN-Connectivity-r13

True

px_DoAttachWithoutPDN

Not Present

NOT px_DoAttachWithoutPDN

}

}

}

Information Element

Value/Remark

Comment

Condition

Data service type

..Data service type value

mobile originating request

ESM message container

ESM DATA TRANSPORT message, User data container not checked

If the ESM DATA TRANSPORT message ‘User data container’ IE needs to be checked and then its content shall be specified in TC

Information Element

Value/Remark

Comment

Condition

Access point name

Not Present or Any allowed value

Protocol configuration options

Not Present

Header compression configuration

Any allowed value

pc_HCCPCIoT AND pc_IP_PDN

Extended protocol configuration options

Not Present or Any allowed value

Information Element

Value/Remark

Comment

Condition

Protocol configuration options

Not present

Header compression configuration

0000H

No Compression profile

NOTE: For the purposes of CIoT (NAS) testing regardless of the Compression files supported by the UE and indicated in the PDN CONNECTIVITY REQUEST, the SS does not agree header compression to be applied.

pc_HCCPCIoT AND pc_IP_PDN

Control plane only indication

‘0001’B

PDN connection can be used for control plane CIoT EPS optimization only

Extended protocol configuration options

The content of the IE below uses the same fields and Conditions (and their meaning) as those defined in TS 36.508 [18] for the IE ‘Protocol configuration options’

Container ID n

‘0003’H

n assigned to next available number

DNS IPv6

Length of container ID n contents

Length value determined by the TTCN implementation

Container ID n contents

IPv6 address

DNS IPv6 Address

Container ID n+1

‘000D’H

n assigned to next available number

DNS IPv4

Length of container ID n+1 contents

Length value determined by the TTCN implementation

Container ID n+1 contents

IPv4 address

DNS IPv4 Address

Serving PLMN rate control

‘11111111 11111111’B

Unrestricted

Max number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send via a PDN connection per 6 minute interval

Information Element

Value/Remark

Comment

Condition

Protocol configuration options

Not present

Extended protocol configuration options

Not present or any allowed value

U – S

Message/PDU/SDU

1

Check: Does the UE transmit an RRCConnectionRequest-NB message?

–>

RRC: RRCConnectionRequest-NB

–

P

2

SS transmits an RRCConnectionSetup-NB message.

<–

RRC: RRCConnectionSetup-NB

–

–

3a1

Void.

–

–

–

–

3a2

Void.

–

–

–

–

3a3

Void.

–

–

–

–

3b1

Check: Does the UE transmit an RRCConnectionSetupComplete-NB message and a CONTROL PLANE SERVICE REQUEST message , data service type="mobile originating request", integrity protected and partially ciphered and including the SMS in the NAS message container IE, and, not containing a PDN CONNECTIVITY REQUEST message?

–>

RRC: RRCConnectionSetupComplete-NB

NAS: CONTROL PLANE SERVICE REQUEST

–

P

3b2

SS starts wait timer 2 sec.

Note: The Service request procedure success is guarded in the UE by timer T3417 = 5 sec after which expiry without any DL action the UE will consider the procedure as failed.

–

–

–

–

–

EXCEPTION: Steps 3b3a1 to 3b3b1 describe behaviour which depends on UE implementation; the "lower case letter" identifies a step sequence which takes place depending on whether the UE is configured or not to establish PDN in RRC-CONNECTED after it sends the CONTROL PLANE SERVICE REQUEST message.

–

–

–

–

3b3a1

IF px_nonSMSTransport_CP_CIoT AND px_DoAttachWithoutPDN THEN

The UE transmits a PDN CONNECTIVITY REQUEST message.

–>

RRC: ULInformationTransfer-NB

NAS: PDN CONNECTIVITY REQUEST

–

–

3b3a2

Stop timer wait timer 2 sec.

–

–

–

–

3b3a3

The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

<–

RRC: DLInformationTransfer-NB

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

–

–

EXCEPTION: IF pc_IP_PDN AND not all IP address information was allocated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent in step 3b3a3 TNEN

In parallel to the events described in steps 3b3a4 the Generic ‘Procedure for IP address allocation in the CP CIoT’ described in TS 36.508 [18], clause 8.1.5A.1 takes place.

–

–

–

–

3b3a4

The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message.

–>

RRC: ULInformationTransfer-NB

NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

–

–

3b3b1

Timer 2 sec expires

–

–

–

–

4

The SS transmits a SERVICE ACCEPT message.

<–

RRC: DLInformationTransfer-NB

NAS: SERVICE ACCEPT

–

–

Information Element

Value/Remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-data

}

}

}

Information Element

Value/Remark

Comment

Condition

RRCConnectionSetupComplete-NB ::= SEQUENCE {

rrc-TransactionIdentifier

the same value as included in the RRCConnectionSetup-NB message received from SS

criticalExtensions CHOICE {

rrcConnectionSetupComplete-r13 SEQUENCE {

attachWithoutPDN-Connectivity-r13

True

px_DoAttachWithoutPDN

Not Present

NOT px_DoAttachWithoutPDN

}

}

}

Information Element

Value/Remark

Comment

Condition

Data service type

..Data service type value

mobile originating request

NAS message container

SMS – content not checked

If the SMS needs to be checked and then its content shall be specified in TC

Information Element

Value/Remark

Comment

Condition

Access point name

Not Present or Any allowed value

Protocol configuration options

Not Present

Header compression configuration

Any allowed value

pc_HCCPCIoT AND pc_IP_PDN

Extended protocol configuration options

Not Present or Any allowed value

Information Element

Value/Remark

Comment

Condition

Protocol configuration options

Not present

Header compression configuration

0000H

No Compression profile

NOTE: For the purposes of CIoT (NAS) testing regardless of the Compression files supported by the UE and indicated in the PDN CONNECTIVITY REQUEST, the SS does not agree header compression to be applied.

pc_HCCPCIoT AND pc_IP_PDN

Control plane only indication

‘0001’B

PDN connection can be used for control plane CIoT EPS optimization only

Extended protocol configuration options

The content of the IE below uses the same fields and Conditions (and their meaning) as those defined in TS 36.508 [18] for the IE ‘Protocol configuration options’

Container ID n

‘0003’H

n assigned to next available number

DNS IPv6

Length of container ID n contents

Length value determined by the TTCN implementation

Container ID n contents

IPv6 address

DNS IPv6 Address

Container ID n+1

‘000D’H

n assigned to next available number

DNS IPv4

Length of container ID n+1 contents

Length value determined by the TTCN implementation

Container ID n+1 contents

IPv4 address

DNS IPv4 Address

Serving PLMN rate control

‘11111111 11111111’B

Unrestricted

Max number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send via a PDN connection per 6 minute interval

Information Element

Value/Remark

Comment

Condition

Protocol configuration options

Not present

Extended protocol configuration options

Not present or any allowed value

U – S

Message/PDU/SDU

–

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

–

–

–

–

1

SS starts timer 60 sec

–

–

–

–

–

EXCEPTION: Steps 2a1-2b3 describe behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence which may take place depending on whether the UE will initiate PDN deactivation.

–

–

–

–

2a1

Check: Does the UE transmit a PDN DISCONNECT REQUEST message?

–>

RRC: ULInformationTransfer

NAS: PDN DISCONNECT REQUEST

–

P

2a2

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message.

<–

RRC: DLInformationTransfer-NB

NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST

–

–

2a3

Check: Does the UE transmit a DEACTIVATE EPS BEARER CONTEXT ACCEPT message?

–>

RRC: ULInformationTransfer

NAS: DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

P

2a4

SS stops 60 sec timer.

–

–

–

–

2b1

60 sec timer expires.

–

–

–

–

2b2

SS releases the PDN connectivity by transmitting a DEACTIVATE EPS BEARER CONTEXT REQUEST message.

<–

RRC: DLInformationTransfer-NB

NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST

–

–

2b3

Check: Does the UE transmit a DEACTIVATE EPS BEARER CONTEXT ACCEPT message?

–>

RRC: ULInformationTransfer-NB

NAS: DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

P

Information Element

Value/remark

Comment

Condition

ESM cause

00100100

regular deactivation

Information Element

Value/remark

Comment

Condition

ESM cause

00100100

regular deactivation

U – S

Message

1

The UE transmits an RRCConnectionRequest-NB message on the cell specified in the test case.

–>

RRC: RRCConnectionRequest-NB

–

–

2

SS transmit an RRCConnectionSetup-NB message.

<–

RRC: RRCConnectionSetup-NB

–

–

3

The UE transmits an RRCConnectionSetupComplete-NB message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.

–>

RRC: RRCConnectionSetupComplete-NB NAS: TRACKING AREA UPDATE REQUEST

–

–

4

SS responds with TRACKING AREA UPDATE ACCEPT message.

<–

RRC: DLInformationTransfer-NB

NAS: TRACKING AREA UPDATE ACCEPT

–

–

5

Check: Does the UE send a TRACKING AREA UPDATE COMPLETE on the cell specified in the test case?

–>

RRC: ULInformationTransfer-NB

NAS: TRACKING AREA UPDATE COMPLETE

–

P

6

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

<–

RRC: RRCConnectionRelease-NB

–

–

U – S

Message

1

The UE transmits an RRCConnectionResumeRequest-NB message on the cell specified in the test case.

–>

RRC: RRCConnectionResumeRequest-NB

–

–

2

SS transmits an RRCConnectionResume-NB message.

<–

RRC: RRCConnectionResume-NB

–

–

3

The UE transmits an RRCConnectionResumeComplete-NB message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.

–>

RRC: RRCConnectionResumeComplete-NB NAS: TRACKING AREA UPDATE REQUEST

–

–

4

SS responds with TRACKING AREA UPDATE ACCEPT message.

<–

RRC: DLInformationTransfer-NB

NAS: TRACKING AREA UPDATE ACCEPT

–

–

5

Check: Does the UE send a TRACKING AREA UPDATE COMPLETE on the cell specified in the test case?

–>

RRC: ULInformationTransfer-NB

NAS: TRACKING AREA UPDATE COMPLETE

–

P

6

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

<–

RRC: RRCConnectionRelease-NB

–

–

U – S

Message/PDU/SDU

1

The SS sends UECapabilityEnquiry-NB message to the UE.

<–

UECapabilityEnquiry-NB

–

–

2

Check: Does the UE send a UECapabilityInformation-NB message?

–>

UECapabilityInformation-NB

–

P

U – S

Message

1

SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordLists.

<–

RRC: Paging-NB

2

UE transmits an RRCConnectionRequest-NB message.

–>

RRC: RRCConnectionRequest-NB

3

SS transmit an RRCConnectionSetup-NB message.

<–

RRC: RRCConnectionSetup-NB

4

The UE transmits an RRCConnectionSetupComplete-NB message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the CONTROL PLANE SERVICE REQUEST message.

–>

RRC: RRCConnectionSetupComplete-NB

NAS: CONTROL PLANE SERVICE REQUEST

5

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

6

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

–>

RRC: SecurityModeComplete

7

The SS configures a new data radio bearer, associated with the default EPS bearer context.

The RRCConnectionReconfiguration-NB message is using condition DRB(1).

<–

RRC: RRCConnectionReconfiguration-NB

8

The UE transmits an RRCConnectionReconfigurationComplete-NB message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer context.

–>

RRC: RRCConnectionReconfigurationComplete-NB