8.2.1 Radio bearer establishment

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.2.1.1 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE to RRC_CONNECTED / Success / Default bearer / Early bearer establishment

8.2.1.1.1 Test Purpose (TP)

(1)

with { UE having completed the RRC connection establishment procedure }

ensure that {
when { SS sends in sequence a SecurityModeCommand and an RRCConnectionReconfiguration message }

then { UE establishes the initial security configuration in accordance with the received securityConfigSMC included in SecurityModeCommand and successfully completes the connection reconfiguration }

}

(2)

with { UE in RRC_CONNECTED state}

ensure that {
when { UE receives an RRCConnectionRelease message }

then { UE releases the signalling connection, the established EPS bearer and all radio resources and enters in RRC_IDLE state }

}

8.2.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.1.2, 5.3.1.1, 5.3.5.3, 5.3.10.1, 5.3.10.3, 5.3.8.3 and 5.3.12. The following represent an extraction of the requirements relevant to the test purpose.

[TS 36.331, clause 5.1.2]

The UE shall:

1> process the received messages in order of reception by RRC, i.e. the processing of a message shall be completed before starting the processing of a subsequent message;

NOTE: 1 E-UTRAN may initiate a subsequent procedure prior to receiving the UEs response of a previously initiated procedure.

[TS 36.331, clause 5.3.1.1]

After having initiated the initial security activation procedure, E-UTRAN initiates the establishment of SRB2 and DRBs, i.e. E-UTRAN may do this prior to receiving the confirmation of the initial security activation from the UE. In any case, E-UTRAN will apply both ciphering and integrity protection for the RRC connection reconfiguration messages used to establish SRB2 and DRBs.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

…

1> else:

2> If the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

NOTE 2: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an outstanding acknowledgment of the SecurityModeComplete message.

…

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.1]

The UE shall:

1> for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment):

2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;

2> establish a PDCP entity and configure it with the current security configuration, if applicable;

2> establish an RLC entity in accordance with the received rlc-Config;

2> establish a DCCH logical channel in accordance with the received logicalChannelConfig and with the logical channel identity set in accordance with 9.1.2

[TS 36.331, clause 5.3.10.3]

The UE shall:

1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment):

2> establish a PDCP entity and configure it with the current security configuration and in accordance with the received pdcp-Config;

2> establish an RLC entity in accordance with the received rlc-Config;

2> establish a DTCH logical channel in accordance with the received logicalChannelIdentity and the received logicalChannelConfig;

1> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

[TS 36.331, clause 5.3.8.3]

The UE shall:

1> delay the following actions defined in this sub-clause 60ms from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;

…

1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘load balancing TAU required’;

1> else:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.

[TS 36.331, clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320;

1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:

2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].

8.2.1.1.3 Test description

8.2.1.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

8.2.1.1.3.2 Test procedure sequence

Table 8.2.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
St	Procedure	U – S	Message	TP	Verdict
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.	<–	Paging	–	–
2	UE transmits an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
3	SS transmit an RRCConnectionSetup message	<–	RRCConnectionSetup	–	–
4	The UE transmits an RRCConnectionSetupComplete to confirm the successful completion of the connection establishment. (Note 1)	–>	RRCConnectionSetupComplete	–	–
5	SS transmits a SecurityModeCommand message to activate AS security.	<–	SecurityModeCommand	–	–
6	Using the same TTI as the SecurityModeCommand message in step 5, the SS transmits an RRCConnectionReconfiguration message to establish a data radio bearer.	<–	RRCConnectionReconfiguration	–	–
7	Check: Does the UE transmit a SecurityModeComplete message?	–>	SecurityModeComplete	1	P
8	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message to confirm the establishment of data radio bearer?	–>	RRCConnectionReconfigurationComplete	1	P
9	Check: Does the test result of CALL generic procedure in TS 36.508 subclause 6.4.2.3 indicate that UE is in E-UTRA RRC_CONNECTED state?	–	–	1	–
10	SS transmits an RRCConnectionRelease message to release the RRC connection.	<–	RRCConnectionRelease	–	–
11	SS waits for 5s.	–	–	–	–
12	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.2 indicate that the UE is in E-UTRA RRC_IDLE state on Cell 1?	–	–	2	–
Note 1: Contains a SERVICE REQUEST NAS message.

8.2.1.1.3.3 Specific message contents

Table 8.2.1.1.3.3-1: RRCConnectionReconfiguration (step 6, Table 8.2.1.1.3.2-1)

Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)

8.2.1.2 Void

8.2.1.3 RRC connection reconfiguration / Radio bearer establishment / Success / Dedicated bearer

8.2.1.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { SS sends an RRCConnectionReconfiguration message including a drb-Identity that is not part of the current UE configuration and a dedicatedInfoNASList}

then { UE successfully establish the radio bearer according to IE radioResourceConfigDedicated }

}

8.2.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.3 and 5.3.10.3.

The following represent an extraction of the requirements relevant to the test purpose.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInformation and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

…

1> else:

2> If the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:

2> forward each element of the dedicatedInfoNASList to upper layers;

…

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3]

The UE shall:

1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment):

2> establish a PDCP entity and configure it with the current security configuration and in accordance with the received pdcp-Config;

2> establish an RLC entity in accordance with the received rlc-Config;

2> establish a DTCH logical channel in accordance with the received logicalChannelIdentity and the received logicalChannelConfig;

1> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

8.2.1.3.3 Test description

8.2.1.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18].

8.2.1.3.3.2 Test procedure sequence

Table 8.2.1.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message to establish a data radio bearer.	<–	RRCConnectionReconfiguration	–	–
2	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?	–>	RRCConnectionReconfigurationComplete	1	P
3	The UE transmits an ULInformationTransfer message. This message includes an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	ULInformationTransfer	–	–
4	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?	–	–	1	–

8.2.1.3.3.3 Specific message contents

Table 8.2.1.3.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.1.3.3.2-1)

Derivation Path: 36.508 table 4.6.1-8, condition DRB(1,0)
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF	1 entry
dedicatedInfoNAS [1]	ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST with EPS bearer identity corresponding to drb-Identity 2	According 36.508 table 4.7.3-3
}
}
}
}

8.2.1.4 Void

8.2.1.5 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE to RRC CONNECTED / Success / Latency check

8.2.1.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state and has sent an RRCConnectionRequest message }

ensure that {

when { UE receive a RRCConnectionSetup message and 16 subframes later receives an UL grant }

then { UE successfully transmit RRCConnectionSetupComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receive a SecurityModeCommand message and 11 subframes later receives an UL grant }

then { UE successfully establish the initial AS security activation according to IE securityConfigSMC }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receive a RRCConnectionReconfiguration message including a drb-Identity that is not part of the current UE configuration and a nas-DedicatedInformation and 16 subframes later receives an UL grant }

then { UE successfully establish the radio bearer according to IE radioResourceConfiguration }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives an UECapabilityEnquiry message after AS security is activated and at 11 subframes later receives an UL grant }

then { UE successfully transmits an UECapabilityInformation message including UE radio access capability information corresponding to the ue-RadioAccessCapRequest variable }

}

8.2.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.4, 5.3.4.3, 5.3.5.3, 5.6.3.3 and 11.2.

[TS 36.331, clause 5.3.3.4]

The UE shall:

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

1> stop timer T300;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> enter RRC_CONNECTED;

1> stop the cell re-selection procedure;

1> set the content of RRCConnectionSetupComplete message as follows:

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]) from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

2> if upper layers provide the ‘Registered MME’, include and set the registeredMME as follows:

3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers:

4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the ‘Registered MME’ received from upper layers;

3> set the mmegi and the mmec to the value received from upper layers;

2> set the dedicatedInfoNAS to include the information received from upper layers;

2> submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.3.4.3]

The UE shall:

1> derive the K_eNB key, as specified in TS 33.401 [32];

1> derive the K_RRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.401 [32];

1> request lower layers to verify the integrity protection of the SecurityModeCommand message, using the algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the K_RRCint key;

1> if the SecurityModeCommand message passes the integrity protection check:

2> derive the K_RRCenc key and the K_UPenc key associated with the cipheringAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.401 [32];

2> configure lower layers to apply integrity protection using the indicated algorithm and the K_RRCint key immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE, including the SecurityModeComplete message;

2> configure lower layers to apply ciphering using the indicated algorithm, the K_RRCenc key and the K_UPenc key after completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent by the UE, except for the SecurityModeComplete message which is sent unciphered;

2> consider AS security to be activated;

2> submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

…

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:

2> forward each element of the dedicatedInfoNASList to upper layers;

…

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.6.3.3]

The UE shall:

1> set the contents of UECapabilityInformation message as follows:

2> if the ue-CapabilityRequest includes ‘eutra’:

3> include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to ‘eutra’;

2> if the ue-CapabilityRequest includes ‘geran-cs’ and if the UE supports GERAN CS domain:

3> include the UE radio access capabilities for GERAN CS within a ue-CapabilityRAT-Container and with the rat-Type set to ‘geran-cs’;

2> if the ue-CapabilityRequest includes ‘geran-ps’ and if the UE supports GERAN PS domain:

3> include the UE radio access capabilities for GERAN PS within a ue-CapabilityRAT-Container and with the rat-Type set to ‘geran-ps’;

2> if the ue-CapabilityRequest includes ‘utra’ and if the UE supports UTRA:

3> include the UE radio access capabilities for UTRA within a ue-CapabilityRAT-Container and with the rat-Type set to ‘utra’;

…

1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 11.2]

The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:

N = the number of 1ms subframes from the end of reception of the E-UTRAN -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> E-UTRAN response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation).

Figure 11.2-1: Illustration of RRC procedure delay

Table 11.2-1: Procedures

Procedure title:	E-UTRAN -> UE	UE -> E-UTRAN	N
RRC Connection Control Procedures
RRC connection establishment	RRCConnectionSetup	RRCConnectionSetupComplete	15
RRC connection re-configuration (radio resource configuration)	RRCConnectionReconfiguration	RRCConnectionReconfigurationComplete	15
Initial security activation	SecurityModeCommand	SecurityModeCommandComplete/SecurityModeCommandFailure	10
Other procedures
UE capability transfer	UECapabilityEnquiry	UECapabilityInformation	10

8.2.1.5.3 Test description

8.2.1.5.3.1 Pre-test conditions

System Simulator:

– Cell 1

– Uplink and downlink bandwidth set to the maximum bandwidth for the E-UTRA Band under test as specified in Table 5.6.1-1 in [31] (to enable allocation of Nprb up to maximum value to avoid segmentation of UECapabilityInformation message).

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

8.2.1.5.3.2 Test procedure sequence

Table 8.2.1.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
St	Procedure	U – S	Message	TP	Verdict
1	The SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordList.	<–	Paging	–	–
2	The UE transmits an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
3	The SS transmit an RRCConnectionSetup message. (Note 3)	<–	RRCConnectionSetup
4	Check: Does the UE transmit an RRCConnectionSetupComplete message within 20 (FDD)/23 (TDD) subframes after successful completion of step 3? (Note 2)	–>	RRCConnectionSetupComplete	1	P
5	The SS transmits a SecurityModeCommand message to activate AS security. (Note 3)	<–	SecurityModeCommand
6	Check: Does the UE transmit a SecurityModeComplete message within 15 (FDD)/18 (TDD) subframes after successful completion of step 5? (Note 2)	–>	SecurityModeComplete	2	P
7	The SS transmits an RRCConnectionReconfiguration message to establish a data radio bearer. (Note 3)	<–	RRCConnectionReconfiguration	–	–
8	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message within 20 (FDD)/23 (TDD) subframes after successful completion of step 7? (Note 2)	–>	RRCConnectionReconfigurationComplete	3	P
9	The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E UTRA only. (Note 3)	<–	UECapabilityEnquiry	–	–
10	Check: Does the UE transmit a UECapabilityInformation message within 15 (FDD)/18 (TDD) subframes after successful completion of step 9? (Note 2)	–>	UECapabilityInformation	4	P
Note 1: The SS is configured for RRC procedure delay testing according to TS 36.523-3 clause 7.12.1. Note 2: 5 (FDD) / 8 (TDD) subframes is added on top of RRC processing delay requirement, because UL grant is allocated for the next subframe after RRC procedure delay and because of transmission delay after UL grant. For TDD, consider the max 7 TTI transmission delay after UL grant. Note 3: The DL resource allocation sent on PDCCH is big enough to guarantee transmission of all DL RRC PDU in single TTI.

Specific message contents

Table 8.2.1.5.3.3-1: RRCConnectionRequest (step 2, Table 8.2.1.5.3.2-1)

Derivation Path: 36.508, Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 8.2.1.5.3.3-2: RRCConnectionSetup (step 3, Table 8.2.1.5.3.2-1)

Derivation Path: 36.508, Table 4.6.1-17
Information Element	Value/remark	Comment	Condition
RRCConnectionSetup ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionSetup-r8 SEQUENCE {
radioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 8.2.1.5.3.3-3: RRCConnectionReconfiguration (step 7, Table 8.2.1.5.3.2-1)

Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
drx-Config	Not present
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 8.2.1.5.3.3-4: RRCConnectionReconfiguration (preamble: Table 4.5.2.3-1 [18], step 14)

Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
drx-Config	Not present
}
}
}
}
}
}

8.2.1.6 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE to RRC CONNECTED / Success / Latency check / SecurityModeCommand and RRCConnectionReconfiguration transmitted in the same TTI

8.2.1.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE received SecurityModeCommand message and RRCConnectionReconfiguration message including a drb-Identity that is not part of the current UE configuration and a nas-DedicatedInformation in the same TTI and 21 subframes later receives an UL grant }

then { UE successfully establish the initial AS security activation according to IE securityConfigSMC and the radio bearer according to IE radioResourceConfiguration }

}

8.2.1.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.4.3, 5.3.5.3 and 11.2.

[TS 36.331, clause 5.3.4.3]

The UE shall:

1> derive the K_eNB key, as specified in TS 33.401 [32];

1> derive the K_RRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.401 [32];

1> if the SecurityModeCommand message passes the integrity protection check:

2> derive the K_RRCenc key and the K_UPenc key associated with the cipheringAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.401 [32];

2> consider AS security to be activated;

2> submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

…

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:

2> forward each element of the dedicatedInfoNASList to upper layers;

…

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 11.2]

The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:

Figure 11.2-1: Illustration of RRC procedure delay

Table 11.2-1: RRC procedure

Procedure title:	E-UTRAN -> UE	UE -> E-UTRAN	N	Notes
RRC Connection Control Procedures
Initial security activation + RRC connection re-configuration (RB establishment)	SecurityModeCommand, RRCConnectionReconfiguration	RRCConnectionReconfigurationComplete	20	The two DL messages are transmitted in the same TTI

8.2.1.6.3 Test description

8.2.1.6.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

8.2.1.6.3.2 Test procedure sequence

Table 8.2.1.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
St	Procedure	U – S	Message	TP	Verdict
1	The SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordList.	<–	Paging	–	–
2	The UE transmits an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
3	The SS transmit an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
4	The UE transmit an RRCConnectionSetupComplete message.	–>	RRCConnectionSetupComplete	–	–
5	The SS transmits a SecurityModeCommand message to activate AS security. (Note 3)	<–	SecurityModeCommand	–	–
6	The SS transmits a RRCConnectionReconfiguration message to establish a data radio bearer. (Note 3)	<–	RRCConnectionReconfiguration	–	–
7	Check: Does the UE transmit an SecurityModeComplete message within 25 (FDD)/28 (TDD) subframes after successful completion of step 5? (Note 2)	–>	SecurityModeComplete	1	P
8	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message within 25 (FDD)/28 (TDD) subframes after successful completion of step 6? (Note 2)	–>	RRCConnectionReconfigurationComplete	1	P
Note 1: The SS is configured for RRC procedure delay testing according to TS 36.523-3 clause 7.12.1. Note 2: 5 (FDD) / 8 (TDD) subframes is added on top of RRC processing delay requirement, because UL grant is allocated for the next subframe after RRC procedure delay and because of transmission delay after UL grant. For TDD, consider the max 7 TTI transmission delay after UL grant. Note 3: The DL resource allocation sent on PDCCH is big enough to guarantee transmission of all DL RRC PDU in single TTI.

8.2.1.6.3.3 Specific message contents

Table 8.2.1.6.3.3-1: RRCConnectionRequest (step 2, Table 8.2.1.6.3.2-1)

Derivation Path: 36.508, Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 8.2.1.6.3.3-2: RRCConnectionSetup (step 3, Table 8.2.1.6.3.2-1)

Derivation Path: 36.508, Table 4.6.1-17
Information Element	Value/remark	Comment	Condition
RRCConnectionSetup ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionSetup-r8 SEQUENCE {
radioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 8.2.1.6.3.3-3: RRCConnectionReconfiguration (step 6, Table 8.2.1.6.3.2-1)

Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
drx-Config	Not present
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 8.2.1.6.3.3-4: RRCConnectionReconfiguration (preamble: Table 4.5.2.3-1 [18], step 14)

Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
drx-Config	Not present
}
}
}
}
}
}

8.2.1.7 RRC connection reconfiguration / Radio bearer establishment / Success / SRB2

8.2.1.7.1 Test Purpose (TP)

with { UE in E-UTRA RRC_CONNECTED state without SRB2}

ensure that {
when { SS sends an RRCConnectionReconfiguration message including SRB2 configuration }

then { UE successfully establish the signalling radio bearer }

}

8.2.1.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.3, and 5.3.10.1.

The following represent an extraction of the requirements relevant to the test purpose.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

…

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

…

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.1]

The UE shall:

1> for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment):

2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;

2> establish a PDCP entity and configure it with the current security configuration, if applicable;

2> establish an RLC entity in accordance with the received rlc-Config;

2> establish a DCCH logical channel in accordance with the received logicalChannelConfig and with the logical channel identity set in accordance with 9.1.2;

8.2.1.7.3 Test description

8.2.1.7.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Registered, Idle Mode (State 2) according to [18].

8.2.1.7.3.2 Test procedure sequence

Table 8.2.1.7.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1-7	Generic Radio Bearer Establishment (State 3) step 1 to 7 in TS 36.508 subclause 4.5.3.3.			–	–
8	The SS transmits an RRCConnectionReconfiguration message to establish SRB2.	<–	RRCConnectionReconfiguration	–	–
9	Check: Does the UE transmits an RRCConnectionReconfigurationComplete message?	–>	RRCConnectionReconfigurationComplete	1	P
10	Check: Does the test result of CALL generic procedure in TS 36.508 subclause 6.4.2.3 indicates that UE is in E-UTRA RRC_CONNECTED state on Cell 1?	–	–	1	–

8.2.1.7.3.3 Specific message contents

Table 8.2.1.7.3.3-1: RRCConnectionReconfiguration (step 8, Table 8.2.1.7.3.2-1))

Derivation Path: 36.508 table 4.6.1-6, condition SRB2-DRB(1, 0)
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
C1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SEQUENCE {
srb-ToAddMod[1] SEQUENCE {
rlc-Config CHOICE {
explicitValue	RLC-Config-NON-DEFAULT-SRB2
}
}
}
}
}
}
}
}
}

Table 8.2.1.7.3.3-2: RLC-Config-NON-DEFAULT-SRB2 ( Table 8.2.1.7.3.3-1))

Derivation Path: 36.331 clauses 6.3.2, 9.2.1.2
Information Element	Value/remark	Comment	Condition
RLC-Config-NON-DEFAULT-SRB2 ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms100
pollPDU	p16
pollByte	kb500
maxRetxThreshold	t6
}
dl-AM-RLC SEQUENCE {
t-Reordering	ms100
t-StatusProhibit	ms200
}
}
}

8.2.1.8 RRC connection reconfiguration / Radio bearer establishment / Success / Dedicated bearer / ROHC configured

8.2.1.8.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including IE headerCompression set to "rohc" }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.1.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.5.3, clause 5.3.10.0, clause 5.3.10.3, TS 36.323, clause 5.5.1, 5.5.2 and TS 36.306, clause 4.3.1.1.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

…

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

[TS 36.331, clause 5.3.10.0]

The UE shall:

…

1> if the received radioResourceConfigDedicated includes the drb-ToAddModList:

2> perform DRB addition or reconfiguration as specified in 5.3.10.3;

[TS 36.331, clause 5.3.10.3]

The UE shall:

1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used):

2> establish a PDCP entity and configure it with the current security configuration and in accordance with the received pdcp-Config;

[TS 36.323, clause 5.5.1]

The header compression protocol is based on the Robust Header Compression (ROHC) framework [7]. There are multiple header compression algorithms, called profiles, defined for the ROHC framework. Each profile is specific to the particular network layer, transport layer or upper layer protocol combination e.g. TCP/IP and RTP/UDP/IP.

The detailed definition of the ROHC channel is specified as part of the ROHC framework in RFC 4995 [7]. This includes how to multiplex different flows (header compressed or not) over the ROHC channel, as well as how to associate a specific IP flow with a specific context state during initialization of the compression algorithm for that flow.

The implementation of the functionality of the ROHC framework and of the functionality of the supported header compression profiles is not covered in this specification.

In this version of the specification the support of the following profiles is described:

Table 5.5.1.1: Supported header compression protocols and profiles

Profile Identifier	Usage:	Reference
0x0000	No compression	RFC 4995
0x0001	RTP/UDP/IP	RFC 3095, RFC 4815
0x0002	UDP/IP	RFC 3095, RFC 4815
0x0003	ESP/IP	RFC 3095, RFC 4815
0x0004	IP	RFC 3843, RFC 4815
0x0006	TCP/IP	RFC 4996
0x0101	RTP/UDP/IP	RFC 5225
0x0102	UDP/IP	RFC 5225
0x0103	ESP/IP	RFC 5225
0x0104	IP	RFC 5225

[TS 36.323, clause 5.5.2]

PDCP entities associated with DRBs can be configured by upper layers [3] to use header compression.

[TS 36.306, clause 4.3.1.1]

This field defines which ROHC profiles from the list below are supported by the UE.

– 0x0000 ROHC uncompressed (RFC 4995)

– 0x0001 ROHC RTP (RFC 3095, RFC 4815)

– 0x0002 ROHC UDP (RFC 3095, RFC 4815)

…

‘IMS capable UEs supporting voice’ shall support ROHC profiles 0x0000, 0x0001, 0x0002 and be able to compress and decompress headers of PDCP SDUs at a PDCP SDU rate corresponding to supported IMS voice codecs.

8.2.1.8.3 Test description

8.2.1.8.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18].

8.2.1.8.3.2 Test procedure sequence

Table 8.2.1.8.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message to establish a data radio bearer.	<–	RRCConnectionReconfiguration	–	–
2	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?	–>	RRCConnectionReconfigurationComplete	1	P
3	The UE transmits an ULInformationTransfer message. This message includes an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	ULInformationTransfer	–	–
4	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state?	–	–	1	–

8.2.1.8.3.3 Specific message contents

Table 8.2.1.8.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.1.8.3.2-1)

Derivation Path: TS 36.508 Table 4.6.1-8, condition DRB(0, 1)
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF	1 entry
DedicatedInfoNAS[1]	ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST with EPS bearer identity corresponding to drb-Identity 2	According 36.508 table 4.7.3-3
}
}
}
}

Table 8.2.1.8.3.3-2: PDCP-Config (Table 8.2.1.8.3.3-1)

Derivation Path: TS 36.508 Table 4.8.2.1.2.1-1
Information Element	Value/remark	Comment	Condition
PDCP-Config-DRB-UM ::= SEQUENCE {
rlc-UM SEQUENCE {
pdcp-SN-Size	len12bits
}
headerCompression CHOICE {
rohc SEQUENCE {
maxCID	15	DEFAULT 15
profiles SEQUENCE {		IMS capable UEs supporting voice shall support ROHC profiles 0x0000, 0x0001, 0x0002.
profile0x0001	TRUE
profile0x0002	TRUE
profile0x0003	FALSE
profile0x0004	FALSE
profile0x0006	FALSE
profile0x0101	FALSE
profile0x0102	FALSE
profile0x0103	FALSE
profile0x0104	FALSE
}
}
}
}

Table 8.2.1.8.3.3-3: RLC-Config (Table 8.2.1.8.3.3-1)

Derivation Path: TS 36.508 Table 4.8.2.1.3.1-1
Information Element	Value/remark	Comment	Condition
RLC-Config-DRB-UM ::= CHOICE {
um-Bi-Directional SEQUENCE {
ul-UM-RLC SEQUENCE {
sn-FieldLength	size10
}
dl-UM-RLC SEQUENCE {
sn-FieldLength	size10
}
}
}