U – S

Message

–

EXCEPTION: Step 1 below and Step 1 in Table 4.5A.1-2 describe behaviour that depends on the contents of the latest PDN CONNECTIVITY REQUEST message sent by the UE prior to this procedure.

–

–

–

EXCEPTION: In parallel to the event described in step 1 below the step specified in Table 4.5A.1-2 may take place.

–

–

1

If the "PDN type" in the latest PDN CONNECTIVITY REQUEST message prior to this procedure was ‘IPv4’ or ‘IPv4v6’ then, IPv4 address allocation by DHCPv4 may occur on the user plane bearer established for the default EPS bearer context activated with the latest ACTIVATE DEFAULT EPS BEARER CONTEXT message prior to this procedure.

–

–

U – S

Message

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 occurs on the user plane bearer established for the default EPS bearer context activated with the latest ACTIVATE DEFAULT EPS BEARER CONTEXT message prior to this procedure.

–

–

U – S

Message

1

The SS transmits system information on the cell specified in the test case.

<–

RRC: SYSTEM INFORMATION (BCCH)

2

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

–>

RRC: RRCConnectionRequest

3

SS transmits an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

The UE transmits an RRCConnectionSetupComplete 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 NAS: TRACKING AREA UPDATE REQUEST

5

SS responds with TRACKING AREA UPDATE ACCEPT message.

<–

RRC: DLInformationTransfer

NAS: TRACKING AREA UPDATE ACCEPT

6

The UE transmits a TRACKING AREA UPDATE COMPLETE

–>

RRC: ULInformationTransfer

NAS: TRACKING AREA UPDATE COMPLETE

7

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

<–

RRC: RRCConnectionRelease

U – S

Message

1-9

Void

–

–

–

EXCEPTION: Steps 10a1 to 10a2b1 describe a transaction that depends on the UE capability

10a1

IF pc_IMS then the SS starts timer Timer_1 = 10 s (Note 1)

–

–

–

EXCEPTION: Steps 10a2a1 to 10a2b1 describe a transaction that depends on the UE implementation

–

–

10a2a1-10a2a9

Registration procedure according TS 34.229-1 [43] subclause C.2 (steps 3-11)

Note: SS cancels timer Timer_1 at step 10a2a1.

–

–

10a2b1

The SS waits for Timer_1 expiry

–

–

U – S

Message

–

EXCEPTION: Steps 1a1 to 1a2b1 describe a transaction that depends on UE capability.

–

–

1a1

IF pc_IMS then the SS starts timer Timer_1 = 10 s

–

–

EXCEPTION: Steps 1a2a1 to 1a2a15 describe a transaction that depends on the UE supporting IMS over UTRA.

–

–

1a2a1

UE transmits a RRC CONNECTION REQUEST message.

–>

RRC CONNECTION REQUEST

1a2a2

SS transmits a RRC CONNECTION SETUP message.

<–

RRC CONNECTION SETUP

1a2a3

The UE transmits a RRC CONNECTION SETUP COMPLETE message

–>

RRC CONNECTION SETUP COMPLETE

1a2a4

The UE transmits a SERVICE REQUEST message

–>

INITIAL DIRECT TRANSFER

1a2a5

SS transmits a GMM AUTHENTICATION AND CIPHERING REQUEST message

<–

GMM AUTHENTICATION AND CIPHERING REQUEST

1a2a6

The UE transmits a GMM AUTHENTICATION AND CIPHERING RESPONSE

–>

GMM AUTHENTICATION AND CIPHERING RESPONSE

1a2a7

SS transmits a SECURITY MODE COMMAND message

<–

SECURITY MODE COMMAND

1a2a8

UE transmits a SECURITY MODE COMPLETE message

–>

SECURITY MODE COMPLETE

1a2a9

The UE transmits a ACTIVATE PDP CONTEXT REQUEST message

–>

ACTIVATE PDP CONTEXT REQUEST

1a2a10

The SS transmits a RADIO BEARER SETUP message

<–

RADIO BEARER SETUP

1a2a11

The UE transmits a RADIO BEARER SETUP COMPLETE message

–>

RADIO BEARER SETUP COMPLETE

1a2a13

The SS transmits a ACTIVATE PDP CONTEXT ACCEPT message

<–

ACTIVATE PDP CONTEXT ACCEPT

–

IF initiated by the UE for IP address allocation

–

–

1a2a13A1a

IP address allocation in the U-plane specified in TS 34.108 [5] subclause 7.2.6 takes place performing IP address allocation in the U-plane.

–

–

1a2a13A2-1a2a13A10

Registration procedure according TS 34.229-1 [43] subclause C.2 (steps 3-11) whereby the UE is allowed to retransmit the requests in steps 4, 6, and 8 when using UDP.

Note: SS cancels timer Timer_1 at step 1a2a13a1.

–

–

1a2a14

Upon completion of the U-plane signalling, the SS transmits a RRC CONNECTION RELEASE message

<–

RRC CONNECTION RELEASE

1a2a15

The UE transmits a RRC CONNECTION RELEASE COMPLETE message

–>

RRC CONNECTION RELEASE COMPLETE

1a2b1

The SS waits for Timer_1 expiry

Information Element

Value/remark

Comment

Condition

Requested NSAPI

NSAPI value

‘0101’B

NSAPI 5

Requested LLC SAPI

LLC SAPI value

‘0011’B

LLC SAPI 3

Requested PDP address

PDP type organisation

‘0001’

IETF allocated address

PDP type number

Any value between ‘00100001’B, ‘01010111’B, ‘10001101’B

The allowed values are respectively IPv4, IPv6, IPv4v6 and "unused but interpreted as Ipv4 by the network"

Address information

Not present

Access point name

Not present or any allowed value

Protocol configuration options

Any allowed Value

The SS shall remember this IE and its contents because this affects subsequent SS behaviour, e.g. coding of ACTIVATE PDP CONTEXT ACCEPT

Information Element

Value/remark

Comment

Condition

Negotiated LLC SAPI

LLC SAPI value

Same as requested in ACTIVATE PDP CONTEXT REQUEST

PDP address

PDP type number

‘00100001’B

IPv4

IPv4

PDN address information

IPv4 address

The SS provides a valid IPv4 address

NOT IPv4-DHCP

0.0.0.0

DHCPv4 is to be used to allocate the IPv4 address

IPv4-DHCP

PDP type number

‘01010111’B

IPv6

IPv6

PDN address information

IPv6 address

The SS provides a valid IPv6 address

PDP type number

‘10001101’B

IPv4v6

IPv4v6

PDN address information (Octets 5 to 8)

IPv4 address

The SS provides a valid IPv4 address

NOT IPv4-DHCP

0.0.0.0

DHCPv4 is to be used to allocate the IPv4 address

IPv4-DHCP

PDN address information (Octets 9 to 24)

IPv6 address

The SS provides a valid IPv6 address

IPv6

Protocol configuration options

Configuration protocol

‘000’B

Container ID 1

‘0001’H

P-CSCF IPv6

Length of container ID 1 contents

Length value determined by the TTCN implementation

Container ID 1 contents

IPv6 address

P-CSCF IPv6 Address

Container ID 2

‘000C’H

P-CSCF IPv4

Length of container ID 2 contents

Length value determined by the TTCN implementation

Container ID 2 contents

IPv4 address

P-CSCF IPv4 Address

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

IPv4

If the ACTIVATE PDP CONTEXT REQUEST message, contains the PDN type as Ipv4

IPv6

If the ACTIVATE PDP CONTEXT REQUEST message, contains the PDN type as Ipv6

IPv4v6

If the ACTIVATE PDP CONTEXT REQUEST message, contains the PDN type as Ipv4v6

IPv4-DHCP

If the ACTIVATE PDP CONTEXT REQUEST message sent prior to this message, the IE Protocol configuration options contains a configuration protocol option "IPv4 address allocation via DHCPv4", length of contents = 0).

Note 1: This condition is used in conjunction with IPv4 or IPv4v6 as indicated in the "PDN address row" just above.

P-CSCF IPv6

If the ACTIVATE PDP CONTEXT REQUEST sent prior to this message, the Protocol configuration options and the additional parameter list was included with a “P-CSCF IPv6 Address Request”.

Note 1: This condition is only applicable for UEs with IMS support (TS 36.523-2 A.4.4-1/25).

P-CSCF IPv4

If in the ACTIVATE PDP CONTEXT REQUEST message sent prior to this message, the Protocol configuration options and the additional parameter list was included with a “P-CSCF IPv4 Address Request”

Note 1: This condition is only applicable for UEs with IMS support (TS 36.523-2 A.4.4-1/25).

DNS IPv6

If the ACTIVATE PDP CONTEXT REQUEST message sent prior to this message, the Protocol configuration options and the additional parameter list was included with a “DNS IPv6 Address Request”.

DNS IPv4

If the ACTIVATE PDP CONTEXT REQUEST message sent prior to this message, the Protocol configuration options and the additional parameter list was included with a “DNS IPv4 Address Request”.

U – S

Message

–

EXCEPTION: Steps 1a1 to 1a2b1 describe a transaction that depends on UE capability.

–

–

1a1

IF pc_IMS then the SS starts timer Timer_1 = 10 s

–

–

EXCEPTION: Steps 1a2a1 to 1a2a4 describe a transaction that depends on the UE supporting IMS over GERAN

–

–

1a2a1

UE transmits CHANNEL REQUEST

–>

CHANNEL REQUEST

1a2a2

SS sends IMMEDIATE ASSIGNMENT

<–

IMMEDIATE ASSIGNMENT

1a2a3

The UE transmits a ACTIVATE PDP CONTEXT REQUEST message

–>

ACTIVATE PDP CONTEXT REQUEST

1a2a4

The SS transmits a ACTIVATE PDP CONTEXT REJECT message

<–

ACTIVATE PDP CONTEXT REJECT

1a2a5

The SS waits for 5 seconds

–

–

1a2b1

The SS waits for Timer_1 expiry

Information Element

Value/remark

Comment

Condition

Requested NSAPI

NSAPI value

‘0101’B

NSAPI 5

Requested LLC SAPI

LLC SAPI value

‘0011’B

LLC SAPI 3

Requested PDP address

PDP type organisation

‘0001’

IETF allocated address

PDP type number

Any allowed value

The allowed values are respectively IPv4, IPv6, IPv4v6 and "unused but interpreted as Ipv4 by the network"

Address information

Not present

Access point name

Not present or any allowed value

Protocol configuration options

Any allowed Value

The SS shall remember this IE and its contents because this affects subsequent SS behaviour, e.g. coding of ACTIVATE PDP CONTEXT ACCEPT

Information Element

Value/remark

Comment

Condition

Protocol discriminator

‘1010’B

Transaction identifier

Same as requested in ACTIVATE PDP CONTEXT REQUEST

Activate PDP context reject message identity

‘01000011’B

SM cause

’42’O

#66 Requested APN not supported in current RAT and PLMN combination

Protocol configuration options

omit

Back-off timer value

omit

Re-attempt indicator

omit

U – S

Message

1

Make the UE attempt an IMS emergency call

–

–

2

The UE transmits an RRCConnectionRequest message with ‘establishmentCause’ set to ’emergency’.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

–>

RRC: RRCConnectionSetupComplete

NAS: 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 message is using condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context obtained during the attach procedure is established

<–

RRC: RRCConnectionReconfiguration

8

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

–>

RRC: RRCConnectionReconfigurationComplete

9

The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN, with ‘Request type’ set to ’emergency (‘0100’B )’.

–>

PDN CONNECTIVITY REQUEST

10

The SS configures a new data radio bearer, associated with the default EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. EPS bearer context #2 (QCI 5) according to table 6.6.1-1: Reference default EPS bearer context is used.

Note: The APN is set to the test APN defined for emergency bearer services.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 11 to 15 below, the behaviour in table 4.5A.4.3-2 occurs. (Optional IP address allocation followed by IMS emergency registration and IMS emergency speech call establishment)

–

–

11

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for emergency call.

–>

RRC: RRCConnectionReconfigurationComplete

12

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

13

The SS configures a new RLC-UM data radio bearer, associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 10

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

14

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for emergency IMS signalling.

–>

RRC: RRCConnectionReconfigurationComplete

15

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

–

EXCEPTION: Step 1 describes behaviour that depends on the UE behaviour.

–

–

1

If initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

–

–

2-5

Steps 1-4 expected sequence defined in annex C.20 of TS 34.229-1 [35]. Emergency registration procedure is performed.

–

–

6-10

Steps 1-5 defined in annex C.22 of TS 34.229-1 [35]. IMS Emergency call for EPS is established.

–

–

Information Element

Value/Remark

Comment

Condition

Access point name

sos

APN value as recommended by IR.88 clause 6.4 [56]

EPS QoS

According to reference default EPS bearer context #2 – in table 6.6.1-1

SS defines an additional dedicated EPS QoS

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

Default EBId-2 (same value like in table 4.5A.4.4-1)

EPS QoS

According to reference dedicated EPS bearer context #1 – in table 6.6.2-1

SS defines an additional dedicated EPS QoS

TFT

According to reference dedicated EPS bearer context #1 – in table 6.6.2-1

Information Element

Value/remark

Comment

Condition

Access point name

Not present or any value

U – S

Message

1

Make the UE attempt an IMS emergency call

–

–

2

The UE transmits an RRCConnectionRequest message with ‘establishmentCause’ set to ’emergency’.

–>

RRCConnectionRequest

3

SS transmits an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message, EPS attach type set to “EPS emergency attach" (‘0110’B). The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST, with ‘Request type’ set to ’emergency (‘0100’B)’.

–>

RRC: RRCConnectionSetupComplete

NAS: ATTACH REQUEST

NAS: PDN CONNECTIVITY REQUEST

5a1 – 6b1

Void

7

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

Note: KSI value is set to "000" and EIA0 (NULL integrity), and EEA0 (NULL ciphering) algorithms are used.

<–

RRC: DLInformationTransfer

NAS: SECURITY MODE COMMAND

8

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

–>

RRC: ULInformationTransfer

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 last PDN CONNECTIVITY REQUEST message THEN the SS transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.

<–

RRC: DLInformationTransfer

NAS: ESM INFORMATION REQUEST

9a2

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

–>

RRC: ULInformationTransfer

NAS: ESM INFORMATION RESPONSE

10

The SS transmits a SecurityModeCommand message to activate AS security.

Note: eia0 (NULL integrity), and eea0 (NULL ciphering) algorithms are used.

<–

RRC: SecurityModeCommand

11

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

–>

RRC: SecurityModeComplete

12

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

<–

RRC: UECapabilityEnquiry

13

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

–>

RRC: UECapabilityInformation

14

The SS transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context #2 (QCI 5) according to table 6.6.1-1: Reference default EPS bearer contexts, obtained during the attach procedure, is established.

This message includes the ATTACH ACCEPT message with EPS attach result set to “EPS only" (‘001’B). The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT.

Note: The APN is set to the test APN defined for emergency bearer services

<–

RRC: RRCConnectionReconfiguration

NAS: ATTACH ACCEPT

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 15 to 19 below, the behaviour in table 4.5A.5.3-2 occurs. (Optional IP address allocation followed by IMS emergency speech call establishment)

–

–

15

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer.

–>

RRC: RRCConnectionReconfigurationComplete

16

This message includes the ATTACH COMPLETE message. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE.

–>

RRC: ULInformationTransfer

NAS: ATTACH COMPLETE

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

17

The SS configures a new RLC-UM data radio bearer, associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.

EPS bearer context #4 (QCI 1) according to table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 10

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

18

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for emergency IMS signalling.

–>

RRC: RRCConnectionReconfigurationComplete

19

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

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

–

EXCEPTION: Step 1 describes behaviour that depends on the UE behaviour.

–

–

1

If initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

–

–

2-6

Steps 1-5 defined in annex C.22 of TS 34.229-1 [35]. IMS Emergency call for EPS is established.

–

–

Information Element

Value/remark

Comment

Condition

Type of integrity protection algorithm

EIA0

Type of ciphering algorithm

EIA0

NAS key set identifier

NAS key set identifier

‘000’B

TSC

‘0’B

native security context (for KSI_ASME)

Spare half octet

‘0000’B

Information Element

Value/remark

Comment

Condition

SecurityModeCommand ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

securityModeCommand-r8 SEQUENCE {

securityConfigSMC

SecurityConfigSMC-LimitedService

Table 4.5A.5.4-3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Information Element

Value/remark

Comment

Condition

SecurityConfigSMC- LimitedService ::= SEQUENCE {

securityAlgorithmConfig SEQUENCE {

cipheringAlgorithm

eea0

integrityProtAlgorithm

eea0

}

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

Default EBId-2 (same value as in table 4.5A.5.4-4)

EPS QoS

See Reference dedicated EPS bearer context #4 in table 6.6.2-1

TFT

See Reference dedicated EPS bearer context #4 in table 6.6.2-1

Information Element

Value/Remark

Comment

Condition

Access point name

sos

APN value as recommended by IR.88 clause 6.4 [56]

EPS QoS

According to reference default EPS bearer context #2 – in table 6.6.1-1

SS defines an additional dedicated EPS bearer

Information Element

Value/remark

Comment

Condition

Access point name

Not present or any value

U – S

Message

1

Make the UE attempt an IMS speech call

–

–

2

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘ mo-Data ‘.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

–>

RRC: RRCConnectionSetupComplete

NAS: 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 message is using condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context obtained during the attach procedure is established

<–

RRC: RRCConnectionReconfiguration

–

EXCEPTION: In parallel to the events described in steps 8 below, the behaviour in table 4.5A.6.3-2 occurs. (IMS MTSI MO speech call establishment)

–

–

8

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

–>

RRC: RRCConnectionReconfigurationComplete

–

EXCEPTION: Steps 9a1 to 11b1 describe behaviour that depends on the UE category.

–

–

9a1-11a1

IF not pc_ue_CategoryDL_M1 THEN steps 3-4 from the expected sequence defined in annex C.21of TS 34.229-1 [35]. MTSI MO speech call for EPS take place.

–

–

9b1-11b1

IF pc_ue_CategoryDL_M1 THEN steps 3-4 from the expected sequence defined in annex C.21d of TS 34.229-1 [35]. MTSI MO speech call for EPS / UE category M1 take place.

–

–

12

The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 13-14 below, the behaviour in table 4.5A.6.3-3 occurs. (IMS MTSI MO speech call establishment)

–

–

13

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

–>

RRC: RRCConnectionReconfigurationComplete

14

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

–

. EXCEPTION: Steps 1a1 to 1b1 describe behaviour that depends on the UE category.

1a1

IF not pc_ue_CategoryDL_M1 THEN THEN the step 2 expected sequence defined in annex C.21 of TS 34.229-1 [35]. UE sends INVITE take place.

–

–

1b1

IF pc_ue_CategoryDL_M1 THEN THEN Step 2 from the expected sequence defined in annex C.21d of TS 34.229-1 [35]. UE sends INVITE take place.

–

–

U – S

Message

–

. EXCEPTION: Steps 1a1 to 8b1 describe behaviour that depends on the UE category.

1a1-8a1

IF not pc_ue_CategoryDL_M1 THEN HEN the steps from the 5-13 expected sequence defined in annex C.21 of TS 34.229-1 [35]. MTSI MO speech call for EPS take place.

–

–

1b1-8b1

IF pc_ue_CategoryDL_M1 THEN the steps 5-13 from the expected sequence defined in annex C.21d of TS 34.229-1 [35]. MTSI MO speech call for EPS / UE category M1 take place.

–

–

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 (PCCH)

2

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘mt-Access’.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

–>

RRC: RRCConnectionSetupComplete

NAS: 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 message is using condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context obtained during the attach procedure is established

<–

RRC: RRCConnectionReconfiguration

8

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

–>

RRC: RRCConnectionReconfigurationComplete

–

EXCEPTION: Steps 9a1 to 12b3 describe behaviour that depends on the UE category.

9a1-12a3

IF not pc_ue_CategoryDL_M1 THEN THEN the steps 1-6 from the expected sequence defined in annex C.11 of TS 34.229-1 [35]. MTSI MT speech call take place.

–

–

9b1-12b3

IF pc_ue_CategoryDL_M1 THEN steps 1-6 from the expected sequence defined in annex C.11d of TS 34.229-1 [35]. MTSI MT speech call / UE category M1 take place.

–

–

13

The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

14

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

–>

RRC: RRCConnectionReconfigurationComplete

15

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

–

EXCEPTION: Steps 18a1 to 22b1 describe behaviour that depends on the UE category.

16a1-17

Void

–

–

18a1-22a1

IF not pc_ue_CategoryDL_M1 THEN steps 7-11 from the expected sequence defined in annex C.11 of TS 34.229-1 [35] MTSI MT speech call take place.

–

–

18b1-22b1

IF pc_ue_CategoryDL_M1 THEN the steps 7-11 from the expected sequence defined in annex C.11d of TS 34.229-1 [35] MTSI MT speech call / UE category M1 take place.

–

–

–

EXCEPTION: Steps 23Aa1 to 23Ab1 describe behaviour that depends on the UE category.

23Aa1

IF not pc_ue_CategoryDL_M1 THEN step 11A from the expected sequence defined in annex C.11 of TS 34.229-1 [35] MTSI MT speech call take place.

–

–

23Ab1

IF pc_ue_CategoryDL_M1 THEN step 11A from the expected sequence defined in annex C.11d of TS 34.229-1 [35] MTSI MT speech call / UE category M1 take place.

–

–

–

EXCEPTION: Steps 23a1 to 24b1 describe behaviour that depends on the UE category.

23a1-24a1

IF not pc_ue_CategoryDL_M1 THEN steps 12-13 expected sequence defined in annex C.11 of TS 34.229-1 [35] MTSI MT speech call take place.

–

–

23b1-24b1

IF pc_ue_CategoryDL_M1 THEN steps 12-13 from the expected sequence defined in annex C.11d of TS 34.229-1 [35] MTSI MT speech call / UE category M1 take place.

–

–

–

EXCEPTION: Steps 25a1 to 26b1 describe behaviour that depends on the UE category.

25a1-26a2

IF not pc_ue_CategoryDL_M1 THEN steps 14-15 from the expected sequence defined in annex C.11 of TS 34.229-1 [35] MTSI MT speech call take place.

–

–

25b1-26b1

IF pc_ue_CategoryDL_M1 THEN steps 14-15 from the expected sequence defined in annex C.11d of TS 34.229-1 [35] MTSI MT speech call / UE category M1 take place.

–

–

U – S

Message

1

Make the UE attempt an IMS video call

–

–

2

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘ mo-Data ‘.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

–>

RRC: RRCConnectionSetupComplete

NAS: 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 message is using condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context obtained during the attach procedure is established

<–

RRC: RRCConnectionReconfiguration

–

EXCEPTION: In parallel to the events described in steps 8 below, the behaviour in table 4.5A.8.3-2 occurs. (IMS MTSI MO video call establishment)

–

–

8

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

–>

RRC: RRCConnectionReconfigurationComplete

9-11

Steps 3-4 expected sequence defined in annex C.25 of TS 34.229-1 [35]. MTSI MO video call for EPS.

–

–

12

The SS configures two new RLC-UM data radio bearers with condition DRB (0,2), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer. One EPS bearer context #4 (QCI 1) and one EPS bearer context #3 (QCI 2) according table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 13-14 below, the behaviour in table 4.5A.8.3-3 occurs. (IMS MTSI MO video call establishment).

–

–

13

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the dedicated EPS bearer. EPS bearer context #4 (QCI 1) according table to 6.6.2-1: Reference dedicated EPS bearer contexts.

–>

RRC: RRCConnectionReconfigurationComplete

14

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer.

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

15

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the second bearer.

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

1

Step 2 expected sequence defined in annex C.25 of TS 34.229-1 [35]. UE sends INVITE.

–

–

U – S

Message

1-8

Steps 5-13 expected sequence defined in annex C.25 of TS 34.229-1 [35]. MTSI MO video call for EPS.

–

–

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 (PCCH)

2

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘mt-Access’.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

–>

RRC: RRCConnectionSetupComplete

NAS: 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 message is using condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context obtained during the attach procedure is established

<–

RRC: RRCConnectionReconfiguration

8

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

–>

RRC: RRCConnectionReconfigurationComplete

9-12b

Steps 1-6 expected sequence defined in annex C.26 of TS 34.229-1 [35]. MTSI MT video call.

–

–

13

The SS configures a new RLC-UM data radio bearer with condition DRB (0,2), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer. One EPS bearer context #4 (QCI 1) and one EPS bearer context #3 (QCI 2) according table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

14

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

–>

RRC: RRCConnectionReconfigurationComplete

15

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer.

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

16

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the second bearer.

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

17-18

Void

–

–

19-27

Steps 7-15 expected sequence defined in annex C.26 of TS 34.229-1 [35]. MTSI MT video call for EPS.

–

–

U – S

Message

1

Make the UE attempt an IMS speech call

–

–

2

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘ mo-Data ‘.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

–>

RRC: RRCConnectionSetupComplete

NAS: 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 message is using condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context obtained during the attach procedure is established

<–

RRC: RRCConnectionReconfiguration

–

EXCEPTION: In parallel to the events described in steps 8 below, the behaviour in table 4.5A.10.3-2 occurs. Initiate MTSI MO speech.

–

–

8

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

–>

RRC: RRCConnectionReconfigurationComplete

9-11

Steps 3-4 expected sequence defined in annex C.21 of TS 34.229-1 [35]. MTSI MO speech call for EPS.

–

–

12

The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

EXCEPTION: In parallel to the events described in steps 13-14 below, the behaviour in table 4.5A.10.3-3 occurs. MTSI MO speech call to alerting state.

–

–

13

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

–>

RRC: RRCConnectionReconfigurationComplete

14

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

1

Step 2 expected sequence defined in annex C.21 of TS 34.229-1 [35]. UE sends INVITE.

–

–

U – S

Message

1-7

Steps 5-11 expected sequence defined in annex C.21 of TS 34.229-1 [35]. MTSI MO speech call to alerting state for EPS.

–

–

U – S

Message

1

Make the UE attempt add IMS video to the voice call.

–

–

2-4

Steps 2-4 expected sequence defined in expected sequence test case 17.1.4 of TS 34.229-1 [35]. MO Speech, add video remove video.

–

–

5

The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #3 (QCI 2) according to table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 6-7 below, the behaviour in table 4.5A.11.3-2 occurs. (IMS MTSI MO video call establishment).

–

–

6

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the dedicated EPS bearer. EPS bearer context #3 (QCI 2) according table to 6.6.2-1: Reference dedicated EPS bearer contexts.

–>

RRC: RRCConnectionReconfigurationComplete

7

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer.

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

1-6

Steps 5-10 expected sequence defined in test case 17.1.4 of TS 34.229-1 [35]. MO Speech, add video remove video.

–

–

U – S

Message

1-3b

Steps 1-5 expected sequence defined in expected sequence test case 17.2.4 of TS 34.229-1 [35]. MT Speech, add video remove video.

–

–

4

The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #3 (QCI 2) according to table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

5

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the dedicated EPS bearer. EPS bearer context #3 (QCI 2) according table to 6.6.2-1: Reference dedicated EPS bearer contexts.

–>

RRC: RRCConnectionReconfigurationComplete

6

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer.

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

7-8

Void

–

–

9-12

Steps 6-9 expected sequence defined in test case 17.2.4 of TS 34.229-1 [35], MT Speech, add video remove video.

–

–

U – S

Message

1

Make the UE attempt XCAP signalling.

–

–

2

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘mo-Data ‘.

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

4

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

–>

RRC: RRCConnectionSetupComplete

NAS: 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 message is using condition SRB2-DRB(1, 0) in case of pc_XCAP_only_APN==true or using condition SRB2-DRB(2, 0) in case of pc_XCAP_over_Internet_APN==true. The DRBs associated with the respective default EPS bearer context obtained during the attach procedure are established

<–

RRC: RRCConnectionReconfiguration

8

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

–>

RRC: RRCConnectionReconfigurationComplete

EXCEPTION:

IF pc_XCAP_only_APN THEN

additional PDN connectivity shall be established as specified in TS 36.508 subclause 4.5A.16 (condition: NOT ADD_IMS)

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to deactivate an EPS bearer.

<–

RRC: RRCConnectionReconfiguration

NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the event described in step2 the step specified in Table 4.5A.15.3-2 should take place.

–

–

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the deactivation of EPS bearer.

–>

RRC: RRCConnectionReconfigurationComplete

3

Void

–

–

U – S

Message

1

The UE transmits an ULInformationTransfer message to accept deactivation of the EPS bearer.

–>

RRC: ULInformationTransfer

NAS: DEACTIVATE EPS BEARER CONTEXT ACCEPT

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

EPS bearer identity

Same value as in the activation message.

ESM cause

00100100

regular deactivation

Information Element

Value/remark

Comment

Condition

EPS bearer identity

EPS bearer identity

The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.

Procedure transaction identity

0

No procedure transaction identity assigned

U – S

Message

–

EXCEPTION: Step 1Aa describes behaviour that depends on UE capabilities/configuration; the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured. The SS shall wait up to 5s for the UE to trigger the PDN Disconnect procedure.

NOTE: The specified wait period of 5s is a working assumption to facilitate test case implementation.

–

–

1Aa

The UE transmits a PDN DISCONNECT REQUEST

–>

RRC: ULInformationTransfer

PDN DISCONNECT REQUEST

1

The SS transmits an RRCConnectionReconfiguration message to deactivate an EPS bearer.

<–

RRC: RRCConnectionReconfiguration

NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the event described in step2 the step specified in Table 4.5A.15A.3-2 should take place.

–

–

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the deactivation of EPS bearer.

–>

RRC: RRCConnectionReconfigurationComplete

U – S

Message

1

The UE transmits an ULInformationTransfer message to accept deactivation of the EPS bearer.

–>

RRC: ULInformationTransfer

NAS: DEACTIVATE EPS BEARER CONTEXT ACCEPT

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

EPS bearer identity

Same value as in the activation message.

ESM cause

00100100

regular deactivation

Information Element

Value/remark

Comment

Condition

EPS bearer identity

EPS bearer identity

The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.

Procedure transaction identity

0

No procedure transaction identity assigned

ADD_IMS

true if this procedure is part of the initial registration (PDN2_IMS==true according to definitions in clause 4.5.2);

false for all other cases

MobileData_OFF

Mobile data associated with Internet PDN is disabled on the DUT. It is configured via setting px_MobileDataOn (TS 36.523-3[20] Table 9.1-1) = false

U – S

Message

–

EXCEPTION: Depending upon UE configuration Step 0a1 may be performed

–

–

0a1

If IMS_Internet and MobileData_OFF then the request of connectivity to an additional PDN is performed by MMI or AT command with APN “Internet”.

–

–

1

The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN.

–>

RRC: ULInformationTransfer

NAS: PDN CONNECTIVITY REQUEST

2

The SS configures a new data radio bearer, associated with the additional default EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

3

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of additional default bearer.

–>

RRC: RRCConnectionReconfigurationComplete

–

EXCEPTION: In parallel to the event described in step 4 below, if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

–

–

–

EXCEPTION: IF ADD_IMS THEN in parallel to the event described in step 4 below the generic procedure for IMS signalling in the U-plane specified in TS 36.508 subclause 4.5A.3 takes place if requested by the UE

–

–

4

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

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

Information Element

Value/remark

Comment

Condition

Access point name

Any allowed value

The UE includes a new APN.

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

‘0101’B

arbitrary value used for PDN connectivity being maintained during the test case

ADD_IMS

EPS bearer identity

‘1100’B

arbitrary value used for additional non-IMS PDN connectivity

NOT ADD_IMS

Procedure transaction identity

PTI-1

SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

(same value as used in step 2)

Procedure transaction identity

0

No procedure transaction identity assigned

U – S

Message

1

Cause the UE to request disconnection from the additional PDN (see Note 1)

–

–

2

The UE transmits an RRCConnectionRequest

–>

RRCConnectionRequest

3

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

–

EXCEPTION: Steps 4a1 to 4b1 describe behaviour which depends on earlier network indication of supported features.

–

–

4a1

IF the network indicated support of EXTENDED SERVICE REQUEST for packet services in the preceding ATTACH ACCEPT message, THEN the UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the EXTENDED SERVICE REQUEST message

–>

RRC: RRCConnectionSetupComplete

NAS: EXTENDED SERVICE REQUEST

4b1

ELSE, the UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.

–>

RRC: RRCConnectionSetupComplete

NAS: 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 transmits a RRCConnectionReconfiguration message to establish SRB2 and DRBs associated with all default EPS bearer contexts

<–

RRC: RRCConnectionReconfiguration

8

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of SRB2 and DRBs associated with all default EPS bearer contexts.

–>

RRC: RRCConnectionReconfigurationComplete

9

The UE transmits a PDN DISCONNECT REQUEST

–>

RRC: ULInformationTransfer

PDN DISCONNECT REQUEST

10

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message included in an RRCConnectionReconfiguration message.

<–

RRC: RRCConnectionReconfiguration

NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST

11

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the release of the bearer.

–>

RRC: RRCConnectionReconfigurationComplete

12

The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.

–>

RRC: ULInformationTransfer

DEACTIVATE EPS BEARER CONTEXT ACCEPT

13

The SS transmits an RRCConnectionRelease message to release RRC connection

<–

RRC: RRCConnectionRelease

NOTE 1: The request to disconnect from a PDN may be performed by MMI or AT command; in any case the EPS bearer identity of the Default EPS Bearer of the PDN to be released needs to be handed over to the UE

Information Element

Value/remark

Comment

Condition

EPS bearer identity

‘0000’

"no EPS bearer identity assigned"

Procedure transaction identity

PTI-1

UE assigns a particular PTI not yet used between 1 and 254

Linked EPS bearer identity

(bearer identity as handed over at step 1)

Information Element

Value/remark

Comment

Condition

EPS bearer identity

(same as in Linked EPS bearer identity of step 9)

Procedure transaction identity

PTI-1

SS re-uses the particular PTI defined by UE for this present PDN disconnection procedure.

UE-INITIATED

ESM cause

00100100

regular deactivation

Information Element

Value/remark

Comment

Condition

EPS bearer identity

(same as in DEACTIVATE EPS BEARER CONTEXT REQUEST of step 10)

The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.

Procedure transaction identity

0

No procedure transaction identity assigned

U – S

Message

1-7

Steps 1 to 7 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1)

8

The SS transmits a RRCConnectionReconfiguration message to establish SRB2 and DRBs associated with all default EPS bearer contexts

<–

RRC: RRCConnectionReconfiguration

9

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of SRB2 and DRBs associated with all default EPS bearer contexts.

–>

RRC: RRCConnectionReconfigurationComplete

10

SS releases the PDN connectivity by transmitting a RRCConnectionReconfiguration containing a DEACTIVATE EPS BEARER CONTEXT REQUEST

<–

RRC: RRCConnectionReconfiguration

NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST

11

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the release of the bearer.

–>

RRC: RRCConnectionReconfigurationComplete

12

The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

13

The SS transmits an RRCConnectionRelease message to release RRC connection

<–

RRC: RRCConnectionRelease

NOTE: The bid for the AM DRBs shall be 1 and 8 instead of 1 and 2.

Information Element

Value/remark

Comment

Condition

EPS bearer identity

(identity of default EPS bearer associated with the PDN to be released)

ESM cause

00011010

Insufficient resources

Information Element

Value/remark

Comment

Condition

EPS bearer identity

(same as in DEACTIVATE EPS BEARER CONTEXT REQUEST of step 10)

The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.

Procedure transaction identity

0

No procedure transaction identity assigned

U – S

Message

1-7

Same as table 4.5A.6.3-1, steps 1-7.

–

EXCEPTION: In parallel to the events described in steps 8 below, the behaviour in table 4.5A.19.3-2 occurs. (IMS MTSI MO speech call establishment)

–

–

8

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

–>

RRC: RRCConnectionReconfigurationComplete

9-11

Steps 3-4 expected sequence defined in annex C.44 of TS 34.229-1 [35]. MTSI MO speech call for EPS / EVS.

–

–

12

The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 13-14 below, the behaviour in table 4.5A.19.3-3 occurs. (IMS MTSI MO speech call establishment)

–

–

13

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

–>

RRC: RRCConnectionReconfigurationComplete

14

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

1

Step 2 expected sequence defined in annex C.44 of TS 34.229-1 [35]. UE sends INVITE.

–

–

U – S

Message

1-9

Steps 5-13 expected sequence defined in annex C.44 of TS 34.229-1 [35]. MTSI MO speech call for EPS / EVS.

–

–

U – S

Message

1-8

Same as table 4.5A.7.3-1, steps 1-8.

9-11b

Steps 1-6 expected sequence defined in annex C.45 of TS 34.229-1 [35], MTSI MT speech call for EPS / EVS.

–

–

12-14

Same as table 4.5A.7.3-1, steps 13-15.

15-16

Void

–

–

17-25

Steps 7-15 expected sequence defined in annex C.45 of TS 34.229-1 [35], MTSI MT speech call for EPS / EVS.

–

–

26

Void

–

–

U – S

Message

1-12

See table 4.5A.6.3-1, steps 1-12

–

–

–

EXCEPTION: In parallel to the events described in steps 13-14 below, the behaviour in table 4.5A.21.3-2 occurs. (IMS MTSI MO CAT and speech call establishment)

–

–

13-14

See table 4.5A.6.3-1, steps 13-14

–

–

U – S

Message

1-14

Steps 5-18 expected sequence defined in 20.1.4 of TS 34.229-1 [35]. MTSI MO CAT and speech call for EPS.

–

–

U – S

Message

1

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘mo-Data ‘.

–>

RRCConnectionRequest

2

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

3

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

–>

RRC: RRCConnectionSetupComplete

NAS: SERVICE REQUEST

4

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

5

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

–>

RRC: SecurityModeComplete

6

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

The RRCConnectionReconfiguration message is using condition SRB2-DRB(1, 0). The DRB associated with default EPS bearer context obtained during the attach procedure is established

<–

RRC: RRCConnectionReconfiguration

7

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

–>

RRC: RRCConnectionReconfigurationComplete

8-10

Steps 1-3 of procedure 4.5A.16.3.

–

–

–

EXCEPTION: In parallel to the event described in step 11 below, the behaviour described in Table 4.5A.22.3-2 takes place.

–

–

11

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

U – S

Message

–

EXCEPTION: Step 1a1 describes behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that take place if the UE does not have a preconfigured IP address.

–

–

1a1

If initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

–

–

2

The UE transmits a ClientHello message including PSK-based ciphersuites.

–>

TLS: ClientHello

3

The SS transmits the ServerHello, ServerKeyExchange and ServerHelloDone messages indicating GBA as required.

<–

TLS: ServerHello

TLS: ServerKeyExchange

TLS: ServerHelloDone

4-7

The generic procedure for GBA authentication according TS 34.229-1 [43] subclause C.29.2 (steps 1-4) takes place.

–

–

8

The UE transmits the ClientKeyExchange including a PSK identity, ChangeCipherSpec and Finished messages.

–>

TLS: ClientKeyExchange

TLS: ChangeCipherSpec

TLS: Finished

9

The SS transmits the ChangeCipherSpec and Finished messages.

<–

TLS: ChangeCipherSpec

TLS: Finished

–

EXCEPTION: Steps 10a1 to 10d2 describe behaviour which depends on the ProSe Procedure being applied

–

–

10a1

IF ANNOUNCE/MONITOR REQUEST THEN

The UE transmits a DISCOVERY_REQUEST message over the PC3 (UE to ProSe Function) interface.

–>

HTTP Request containing

DISCOVERY_REQUEST

10a2

The SS transmits a DISCOVERY_RESPONSE message over the PC3 (UE to ProSe Function) interface.

<–

HTTP Response containing

DISCOVERY_RESPONSE

10a3

The UE transmits a SidelinkUEInformation message.

–>

SidelinkUEInformation

10b1

IF MATCH REPORT THEN

The UE transmits a MATCH_REPORT message over the PC3 (UE to ProSe Function) interface.

–>

HTTP Request containing

MATCH_REPORT

10b2

The SS transmits a MATCH_REPORT_ACK message over the PC3 (UE to ProSe Function) interface.

<–

HTTP Response containing

MATCH_REPORT_ACK

10c1

IF UEREGISTRATION THEN

The UE transmits an UE_REGISTRATION_REQUEST message over the PC3 (UE to ProSe Function) interface.

–>

HTTP Request containing

UE_REGISTRATION_REQUEST

10c2

The SS transmits an APPLICATION_REGISTRATION_RESPONSE message with a response-register.

<–

HTTP Response containing

UE_REGISTRATION_RESPONSE

10d1

IF USAGEINFOREPORT THEN

The UE transmits an USAGE_INFORMATION_REPORT_LIST message over the PC3ch (UE to ProSe Function) interface.

–>

HTTP Request containing

USAGE_INFORMATION_REPORT_LIST

10d2

SS sends USAGE_INFORMATION_REPORT_LIST_RESPONSE message.

<–

HTTP Response containing

USAGE_INFORMATION_REPORT_LIST_RESPONSE

ANNOUNCE/MONITOR REQUEST

Steps applicable to Announce request procedure OR Monitor request procedure

MATCH REPORT

Steps applicable to Match report procedure

UEREGISTRATION

Steps applicable to EPC-level ProSe discovery / UE registration procedure

USAGEINFOREPORT

Steps applicable to usage information report list sending procedure.

U – S

Message

–

EXCEPTION: Steps 1a1 to 1a7 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if the UE is in RRC_IDLE state.

–

–

1a1

The UE transmits an RRCConnectionRequest message with ‘ establishmentCause’ set to ‘mo-Data ‘.

–>

RRCConnectionRequest

1a 2

SS transmit an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

1a 3

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

–>

RRC: RRCConnectionSetupComplete

NAS: SERVICE REQUEST

1a 4

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

1a 5

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

–>

RRC: SecurityModeComplete

1a 6

The SS configures two new data radio bearers, associated with the two default EPS bearer contexts.

The RRCConnectionReconfiguration message is using condition SRB2-DRB(2, 0).

<–

RRC: RRCConnectionReconfiguration

1a 7

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

–>

RRC: RRCConnectionReconfigurationComplete

2-10

Void

–

EXCEPTION: Steps 10a1 to 10d2 describe behaviour which depends on the ProSe Procedure being applied

–

–

10a1-10d2

Steps 10a1-10d2 of Table 4.5A.22.3-2.

–

–

U – S

Message

1

The UE is switched on

–

–

2

The UE associates with the WLAN AP and obtains the local IP address

–

–

3

The UE performs a dynamic selection of ePDG using DNS query

–

–

4

The UE establishes an IPsec tunnel using the IKEv2 protocol as defined in 3GPP TS 33.402 [55] clause 8.2.2, Figure 8.2.2-1.

–

–

5-13

The UE performs the IMS registration procedure according TS 34.229-1 [43] subclause C.2c (steps 2-9).

–

–

U – S

Message

1

The UE initiates a disconnection from the existing IPsec tunnel as defined in 3GPP TS 24.302 [53] clause 7.2.4.1, which is acknowledged by the SS.

NOTE: It is assumed that the WLAN AP association remains throughout the procedure.

U – S

Message

1

The UE is triggered to initiate an emergency call

–

–

2

Void

–

–

3

The UE performs a dynamic selection of an ePDG that supports emergency services using DNS query

–

–

4

The UE establishes an additional IPsec tunnel using the IKEv2 protocol as defined in 3GPP TS 33.402 [55] clause 8.2.2, Figure 8.2.2-1.

–

–

NOTE 1: It is assumed that the WLAN AP association remains throughout the procedure.

NOTE 2: This procedure is based on 3GPP Release 14.

U – S

Message

1

Make the UE attempt XCAP signalling.

–>

–

2

The UE establishes an additional PDN and IPsec tunnel using the IKEv2 protocol as defined in 3GPP TS 33.402 [55] clause 8.2.2, Figure 8.2.2-1.

–

–

U – S

Message

1-8a7

Steps 3 to 10a7 of the generic radio bearer establishment procedure from TS 36.508 subclause 4.5.3.3-3 are executed

–

–

9

The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN, with ‘Request type’ set to ’emergency (‘0100’B)’.

–>

NAS: PDN CONNECTIVITY REQUEST

10

The SS configures a new data radio bearer, associated with the default EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. EPS bearer context #2 (QCI 5) according to table 6.6.1-1: Reference default EPS bearer context is used.

Note: The APN is set to the test APN defined for emergency bearer services.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 11 to 15 below, the behaviour in table 4.5A.26.3-2 occurs. (Optional IP address allocation followed by IMS emergency registration and eCall over IMS establishment)

–

–

11

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for emergency call.

–>

RRC: RRCConnectionReconfigurationComplete

12

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

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

13

The SS configures a new RLC-UM data radio bearer, associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 2

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

14

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for emergency IMS signalling.

–>

RRC: RRCConnectionReconfigurationComplete

15

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

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

–

EXCEPTION: Step 1 describes behaviour that depends on the UE behaviour.

–

–

1

If initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

–

–

2-5

Steps 1-4 expected sequence defined in annex C.20 of TS 34.229-1 [35]. Emergency registration procedure is performed.

–

–

6-8

Steps 1-3 defined in annex C.47 of TS 34.229-1 [35] Generic Test Procedure for NG eCall setup.

–

–

Information Element

Value/remark

Comment

Condition

Request type

‘0100’B

Emergency

Access point name

Not present or any value

Information Element

Value/Remark

Comment

Condition

Access point name

sos

APN value as recommended by IR.88 clause 6.4 [56]

EPS QoS

According to reference default EPS bearer context #2 – in table 6.6.1-1

SS defines an additional dedicated EPS QoS

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

Default EBId-2 (same value like in table 4.5A.4.4-1)

EPS QoS

According to reference dedicated EPS bearer context #1 – in table 6.6.2-1

SS defines an additional dedicated EPS QoS

TFT

According to reference dedicated EPS bearer context #1 – in table 6.6.2-1

U – S

Message

1

The UE is switched on and SS waits 15 sec to allow the UE to camp on the serving cell and enter and remain in substate EMM-DEREGISTERED.eCALL-INACTIVE.

–

–

2

Make the UE attempt an eCall (See Note 1)

–

–

3-18

Steps 1 to 16 of the generic test procedure for UE registration sub clause 4.5.2.3.

–

–

19

The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN, with ‘Request type’ set to ’emergency (‘0100’B)’.

–>

NAS: PDN CONNECTIVITY REQUEST

20

The SS configures a new data radio bearer, associated with the default EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. EPS bearer context #2 (QCI 5) according to table 6.6.1-1: Reference default EPS bearer context is used.

Note: The APN is set to the test APN defined for emergency bearer services.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

EXCEPTION: In parallel to the events described in steps 21 to 25 below, the behaviour in table 4.5A.27.3-2 occurs. (Optional IP address allocation followed by IMS emergency registration and eCall over IMS establishment)

–

–

21

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for emergency call.

–>

RRC: RRCConnectionReconfigurationComplete

22

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

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

23

The SS configures a new RLC-UM data radio bearer, associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to table 6.6.2-1: Reference dedicated EPS bearer contexts is used.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 2

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

24

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer for emergency IMS signalling.

–>

RRC: RRCConnectionReconfigurationComplete

25

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

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

U – S

Message

–

EXCEPTION: Step 1 describes behaviour that depends on the UE behaviour.

–

–

1

If initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

–

–

2-5

Steps 1-4 expected sequence defined in annex C.20 of TS 34.229-1 [35]. Emergency registration procedure is performed.

–

–

6-8

Steps 1-3 defined in annex C47 of TS 34.229-1 [35] Generic procedure for NG eCall Setup.

–

–

Information Element

Value/remark

Comment

Condition

Request type

‘0100’B

Emergency

Access point name

Not present or any value

Information Element

Value/Remark

Comment

Condition

Access point name

sos

APN value as recommended by IR.88 clause 6.4 [56]

EPS QoS

According to reference default EPS bearer context #2 – in table 6.6.1-1

SS defines an additional dedicated EPS QoS

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

Default EBId-2 (same value like in table 4.5A.4.4-1)

EPS QoS

According to reference dedicated EPS bearer context #1 – in table 6.6.2-1

SS defines an additional dedicated EPS QoS

TFT

According to reference dedicated EPS bearer context #1 – in table 6.6.2-1

U – S

Message

1

The UE is switched on

2-16

Steps 2-16 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.

–

–

17-20

Steps 1-4 of the generic procedure to establish an additional PDN Connection specified in TS 36.508 subclause 4.5A.16.

Information Element

Value/remark

Comment

Condition

Access point name

Any allowed value

The UE includes a new APN.

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

‘0101’B

arbitrary value used for PDN connectivity being maintained during the test case

ADD_IMS_MultiMedia and SMS

EPS bearer identity

‘1100’B

arbitrary value used for additional non-IMS PDN connectivity

ADD_IMS_Advanced_Messaging

Procedure transaction identity

PTI-1

SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure

EPS QoS

See Reference default EPS bearer context #2 in table 6.6.1-1

Access point name

APN as provided in ESM INFORMATION RESPONSE or PDN CONNECTIVITY REQUEST

ADD_IMS_MultiMedia and SMS

pc_IMS AND
pc_Provide_IMS_as_second_APN

UE performs IMS registration for multi-media telephony and SMSoIP first, and IMS registration for advanced messaging services second.

ADD_IMS_Advanced_Messaging

pc_IMS AND
NOT pc_Provide_IMS_as_second_APN

UE performs IMS registration for advanced messaging services first, and IMS registration for multi-media telephony and SMSoIP second.

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

(same value as used in step 2)

Procedure transaction identity

0

No procedure transaction identity assigned

U – S

Message

1

The UE establishes an IPsec tunnel using the IKEv2 protocol as defined in 3GPP TS 33.402 [55] clause 8.2.2, Figure 8.2.2-1.

–

–

2-9

The UE performs the IMS registration procedure according TS 34.229-1 [43] subclause C.2c (steps 2-9).

NOTE: It is assumed that the WLAN AP association remains throughout the procedure.

U – S

Message

–

EXCEPTION: Steps 1a1 to

1a2a10/1a2b1 describe behaviour that depends on the UE capability

–

–

1a1

IF pc_IMS then the SS starts timer Timer_1 = 10s.

–

–

–

EXCEPTION: Steps 1a2a1 to 1a2b1 describe a behaviour that depends on the UE implementation

–

–

1a2a1-1a2a7

Steps 3 to 9 of the generic radio bearer

establishment procedure in TS 36.508

subclause 4.5.3.3 are executed.

–

–

1a2a8-1a2a9

The UE performs IMS re-registration using the

generic procedure defined in 34.229-1 [35]

Annex C.46.

Note: SS cancels timer Timer_1 at step 1a2a8.

–

–

1a2a10

The SS releases the RRC connection.

–

–

1a2b1

The SS waits for Timer_1 expiry

–

–