8.1.2 RRC connection 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.1.2.1 Void

NOTE: The present test (RRC connection establishment / Success) is superseded by test case 8.1.1.3 (i.e. all requirements which the present test verified are verified in test case 8.1.1.3).

8.1.2.2 RRC connection establishment / Reject with wait time

8.1.2.2.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE receives an RRCConnectionReject message including an IE waitTime set to non-zero value }

then { UE doesn’t re-send RRCConnectionRequest before the waitTime is expired}

}

8.1.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.3.2, 5.3.3.3 and 5.3.3.8.

[TS 36.331, clause 5.3.3.2]

…

Upon initiation of the procedure, the UE shall:

1> if the UE is establishing the RRC connection for mobile terminating calls:

2> if timer T302 is running:

3> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else if the UE is establishing the RRC connection for emergency calls:

…

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> if timer T302 or T303 is running:

3> consider access to the cell as barred;

…

1> If access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up to date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to perform system information acquisition upon re-selection.

…

[TS 36.331, clause 5.3.3.3]

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the IE ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else

3> draw a random value in the range 0 .. 2⁴⁰-1 and set the ue-Identity to this value;

NOTE 1 Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> Set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCConnectionRequest message to lower layers for transmission.

…

[TS 36.331, clause 5.3.3.8]

The UE shall:

1> stop timer T300;

1> reset MAC and release the MAC configuration;

1> start timer T302, with the timer value set to the waitTime;

1> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls, mobile originating signalling and mobile terminating access is applicable, upon which the procedure ends.

8.1.2.2.3 Test description

8.1.2.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 (serving cell) according to [18].

8.1.2.2.3.2 Test procedure sequence

Table 8.1.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	–	–	–	–
1A	Wait for 1 s after the IP packet has been transmitted in step 1. (Note 3)
1B	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease
1C	The SS transmits a Paging message with a matching UE identity.	<–	Paging
2	The UE transmits an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
3	The SS responds with RRCConnectionReject message with IE waitTime set to 10s.	<–	RRCConnectionReject	–	–
–	EXCEPTION: the behaviour in table 8.1.2.2.3.2-2 runs in parallel with steps 4 and 5 below.	–	–	–	–
4	Void	–	–	–	–
5	The SS transmits a Paging message with a matching UE identity.	<–	Paging	–	–
6	The SS starts timer Timer_1 = 5 s (Note 1)	–	–	–	–
–	EXCEPTION: Steps 7a1 to 7 b2 describe a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.(Note 2)	–	–	–	–
7a1	Check: Does UE transmit RRCConnectionRequest message when Cell 1 is treated as normal cell and access is granted for originating call?	–	RRCConnectionRequest	1	P
7a2-7a6	Steps 4 to 8 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed.	–	–	–	–
	EXCEPTION: Step 7a7 and 7a8 can occur in any order
7a7	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.	–>	RRCConnectionReconfigurationComplete
7a8	The UE loop backs the IP packet received in step 1 on the DRB associated with the default EPS bearer context on Cell 1.
7a9	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
7b1	The SS waits for Timer_1 expiry	–	–	–	–
7b2	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?	–	–	1	–
Note 1: Test step 6 is always executed 10s after step 3, i.e. when the reject timer is expired in the UE and the UE is allowed to answer paging and initiate calls again. This is because test steps 4 and 5 of the main behaviour run in parallel with test step 1 of the parallel behaviour, which lasts 10s unless the verdict is "Failed". Note 2: A UE may send RRCConnectionRequest for the pending data sent at step 1. Note 3: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS in step 1 to the UE test loop function before the RRCConnectionRelease message is sent by the SS in step 1B.

Table 8.1.2.2.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit an RRCConnectionRequest message within 10s.	–>	RRCConnectionRequest	1	F

8.1.2.2.3.3 Specific message contents

Table 8.1.2.2.3.3-1: RRCConnectionReject (step 3, table 8.1.2.2.3.2-1)

Derivation path: 36.508 table 4.6.1-14
Information Element	Value/Remark	Comment	Condition
RRCConnectionReject ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReject-r8 SEQUENCE {
waitTime	10	10 seconds
}
}
}
}

Table 8.1.2.2.3.3-2: CLOSE UE TEST LOOP (preamble, Table 8.1.2.2.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	‘0000 0101’B	5 seconds

8.1.2.3 RRC connection establishment / Return to idle state after T300 timeout

8.1.2.3.1 Test Purpose (TP)

(1)

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

ensure that {
when { the SS does not answer to the UE during T300}

then {UE goes to RRC_IDLE}

}

8.1.2.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.3.6.

[TS 36.331, clause 5.3.3.6]

The UE shall:

1> if timer T300 expires

2> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends.

8.1.2.3.3 Test description

8.1.2.3.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.1.2.3.3.2 Test procedure sequence

Table 8.1.2.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0A	SS is configured not to transmit MAC control element with matched UE Contention Resolution Identity	–	–	–	–
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	The UE transmits an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
3	The SS waits for 2s. Note: the UE may transmit one or more RRCConnectionRequest messages but the SS does not answer to these messages.	–>	RRCConnectionRequest	–	–
3A	SS is configured to transmit MAC control element with matched UE Contention Resolution Identity	–	–	–	–
4	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?	–	–	1	–

8.1.2.3.3.3 Specific message contents

Table 8.1.2.3.3.3-1: RRCConnectionRequest (step 2 and step 3, Table 8.1.2.3.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
}
}
}

8.1.2.4 Void

8.1.2.5 RRC connection establishment / 0% access probability for MO calls, no restriction for MO signalling

8.1.2.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating 0% access probability for MO calls }

ensure that {
when { UE has user data pending }

then { UE does not transmit any RRCConnectionRequest message }

}

(2)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts a SystemInformationBlockType2 indicating no restriction for MO signalling }

then { UE transmits an RRCConnectionRequest message }

}

8.1.2.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.2.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if the UE is establishing the RRC connection for mobile terminating calls:

…

1> else if the UE is establishing the RRC connection for emergency calls:

…

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> if timer T302 or T303 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand’ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand’ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Data:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else (the UE is establishing the RRC connection for mobile originating signalling):

2> if timer T302 or T305 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Signalling is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand’ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand’ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Signalling:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> else:

2> if the UE is establishing the RRC connection for mobile originating calls and if both timers T302 and T303 are not running:

3> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

3> start timer T303 with the timer value calculated as follows, using the ac-BarringTime included in ac-BarringForMO-Data:

T303= (0.7+ 0.6 _* rand) _* ac-BarringTime

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls is applicable, upon which the procedure ends;

…

8.1.2.5.3 Test description

8.1.2.5.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 11 (HPLMN in different TA).

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 (serving cell) according to [18].

8.1.2.5.3.2 Test procedure sequence

Table 8.1.2.5.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. The configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.1.2.5.3.2-2.

Table 8.1.2.5.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 11	Remark
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy RCell 1 < RCell 11.

Table 8.1.2.5.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Void	–	–	–	–
2	Void	–	–	–	–
2A	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
2B	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
3	The SS changes Cell 1 and Cell 11 level according to the row "T1" in table 8.1.2.5.3.2-1.	–	–	–	–
3A	Check: Does the UE transmit an RRCConnectionRequest on Cell 11?	–>	RRCConnectionRequest	2	P
3B-3F	Steps 2 to 6 of the generic test procedure in TS 36.508 [18] subclause 6.4.2.7 are performed on Cell 11. Note: The UE performs a TAU procedure and the RRC connection is released.	–	–	–	–
4-9	Void	–	–	–	–
10	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
10A	Generic test procedure in TS 36.508 subclause 4.5.3.3 is performed on Cell 11. NOTE: The UE performs the establishment of the new data radio bearer associated with the default EPS bearer context.	–	–	–	–
10B	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 11.	–	–	–	–
10C	Wait for 1 s after the IP packet has been transmitted in step 10B. (Note 1)	–	–	–	–
11-13	Void	–	–	–	–
14	The SS transmits an RRCConnectionRelease message on Cell 11.	<–	RRCConnectionRelease	–	–
15	Check: Does the UE transmit an RRCConnectionRequest message on Cell 11 within 30s?	–>	RRCConnectionRequest	1	F
16	Void	–	–	–	–
–	EXCEPTION: Step 26 and Step 27a1 can happen in any order	–	–	–	–
17 – 26	Check: Does the test result of steps 1 to 10 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 11?	–	–	1,2	–
–	EXCEPTION: Step 27a1 describes behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence that takes place if the UE has user data pending.	–	–	–	–
27a1	IF the UE has user data pending THEN the UE loop backs the IP packet received in step 10C on the DRB associated with the default EPS bearer context on Cell 11 within 10s.	–	–	–	–
Note 1: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS in step 10B to the UE test loop function before the RRCConnectionRelease message is sent by the SS in step 14.

8.1.2.5.3.3 Specific message contents

Table 8.1.2.5.3.3-1: SystemInformationBlockType2 for Cell 11 (preamble and all steps, Table 8.1.2.5.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	FALSE
ac-BarringForMO-Signalling	Not present
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor	p00
ac-BarringTime	s512
ac-BarringForSpecialAC	‘11111’B
}
}
}

Table 8.1.2.5.3.3-1A: CLOSE UE TEST LOOP (preamble, Table 8.1.2.5.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	‘0000 0101’B	5 seconds

Table 8.1.2.5.3.3-2: RRCConnectionRequest (step 3A, Table 8.1.2.5.3.2-2)

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

8.1.2.6 RRC connection establishment / Non-zero percent access probability for MO calls, no restriction for MO signalling

8.1.2.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating non zero percent access probability for MO calls }

ensure that {
when { UE has user data pending }

then { UE does not transmit any RRCConnectionRequest message or UE transmits an RRCConnectionRequest message }

}

(2)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts a SystemInformationBlockType2 indicating no restriction for MO signalling }

then { UE transmits an RRCConnectionRequest message }

}

8.1.2.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.2.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if the UE is establishing the RRC connection for mobile terminating calls:

…

1> else if the UE is establishing the RRC connection for emergency calls:

…

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> if timer T302 or T303 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Data:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else (the UE is establishing the RRC connection for mobile originating signalling):

2> if timer T302 or T305 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is present:

…

2> else:

3> consider access to the cell as not barred;

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> else:

2> if the UE is establishing the RRC connection for mobile originating calls and if both timers T302 and T303 are not running:

3> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

3> start timer T303 with the timer value calculated as follows, using the ac-BarringTime included in ac-BarringForMO-Data:

T303= (0.7+ 0.6 _* rand) _* ac-BarringTime

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls is applicable, upon which the procedure ends;

2> else if the UE is establishing the RRC connection for mobile originating signalling and if both timers T302 and T305 are not running:

3> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

3> start timer T305 with the timer value calculated as follows, using the ac-BarringTime included in ac-BarringForMO-Signalling:

T305= (0.7+ 0.6 _* rand) _* ac-BarringTime

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

8.1.2.6.3 Test description

8.1.2.6.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 11.

UE:

None.

Preamble:

– UE is in state Generic RB Established, UE Test Mode Activated (state 3A) on Cell 1 according to [18].

8.1.2.6.3.2 Test procedure sequence

Table 8.1.2.6.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 11	Remark
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy R_{Cell 1}< R_{Cell 11}.

Table 8.1.2.6.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS initializes an internal counter K to 0 and L to 0.	–	–	–	–
2	Void	–	–	–	–
–	EXCEPTION: Step 2Aa1 to 3b9 shall be repeated maximum 50 times unless K > 0 and L >0. (Note 1)	–	–	–	–
–	EXCEPTION: Step 2Aa1 describes behaviour that depends on the internal counters.	–	–	–	–
2Aa1	IF K>0 or L>0 THEN The SS opens the UE test loop mode.	–	–	–	–
2B	The SS closes the UE test loop mode.	–	–	–	–
2C	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	–	–	–	–
2D	Wait for 1 s after the IP packet has been transmitted in step 2C.	–	–	–	–
2E	SS transmits an RRCConnectionRelease message to release the RRC connection.	<–	RRCConnectionRelease	–	–
2F	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
–	EXCEPTION: Steps 3a1 to 3b9 describe behaviours which vary depending on whether the UE transmits an RRCConnectionRequest message or not.	–	–	–	–
3a1	IF the UE does not transmit any RRCConnectionRequest message within 5s (Note 3) THEN the SS increments the counter K by 1.	–	–	–	–
–	EXCEPTION: Steps 3a9 to 3a10 can occur in any order	–	–	–	–
3a2-3a9	Steps 2 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed (Note 2).	–	–	–	–
–	EXCEPTION: Step 3a10 describes behaviour that depends on UE implementation; step 3a10 takes place if the UE has user data pending.	–	–	–	–
3a10	IF the UE has user data pending THEN the UE loop backs the IP packet received in step 2D on the DRB associated with the default EPS bearer context on Cell 1 within 10 s.	–	–	–	–
3b1	ELSE IF the UE transmits an RRCConnectionRequest message on Cell 1 THEN the SS increments the counter L by 1.	–>	RRCConnectionRequest	–	–
3b2	Void	–	–	–	–
–	EXCEPTION: Steps 3b8 to 3b9 can occur in any order	–	–	–	–
3b3-3b8	Steps 4 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed.	–	–	–	–
3b9	The UE loop backs the IP packet received in step 4 on the DRB associated with the default EPS bearer context on Cell 1.	–	–	–	–
3b10-3b14	Void	–	–	–	–
4	Check: Is the counter K > 0 and L > 0?	–	–	1	P
4A	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
4B	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
5	The SS changes the power level setting according to the row “T1” in table 8.1.2.6.3.2-1.	–	–	–	–
6	Check: Does the UE transmit an RRCConnectionRequest message on Cell 11?	–>	RRCConnectionRequest	2	P
7-11	Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 6.4.2.7 are performed on Cell 11. NOTE: The UE performs a TAU procedure and the RRC connection is released.	–	–	–	–
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 11?	–	–	1,2	–
Note 1: There is an extremely low probability that the UE originating calls are barred, or not barred, 50 times consecutively. (The probability is 1.78×10^-15). Therefore, 50 times is enough number of trials for this test case. Note 2: After UE enters RRC_CONNECTED T303 is stopped. Note 3: The UE starts T303.

8.1.2.6.3.3 Specific message contents

Table 8.1.2.6.3.3-1: SystemInformationBlockType2 for Cell 1 and Cell 11 (preamble and all steps, Table 8.1.2.6.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	FALSE
ac-BarringForMO-Signalling	Not present
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor	p50
ac-BarringTime	s64
ac-BarringForSpecialAC	‘00000’B
}
}
}

Table 8.1.2.6.3.3-2: RRCConnectionRequest (step 3b1, Table 8.1.2.6.3.2-2)

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

Table 8.1.2.6.3.3-3: Void

Table 8.1.2.6.3.3-4: RRCConnectionRequest (step 6, Table 8.1.2.6.3.2-2)

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

Table 8.1.2.6.3.3-5: CLOSE UE TEST LOOP (step 2B, Table 8.1.2.6.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	‘0000 1000’B	8 seconds

8.1.2.7 RRC connection establishment / 0% access probability for AC 0 to 9, AC 10 is barred, AC 11 to 15 are not barred, access for UE with access class in the range 11 to 15 is allowed

8.1.2.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having an Access Class with a value in the range 11..15 and having received a SystemInformationBlockType2 indicating 0% access probability for AC 0..9 for both MO call and MO signalling, access restriction for AC 10 and no restriction for AC 11..15 for both MO call and MO signalling }

ensure that {
when { UE has user data pending }

then { UE transmits an RRCConnectionRequest message }

}

(2)

with { UE in E-UTRA RRC_IDLE state having an Access Class with a value in the range 11..15 }

ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts a SystemInformationBlockType2 indicating 0% access probability for AC 0..9 for both MO call and MO signalling, access restriction for AC 10 and no restriction for AC 11..15 for both MO call and MO signalling }

then { UE transmits an RRCConnectionRequest message }

}

8.1.2.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.2.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if the UE is establishing the RRC connection for mobile terminating calls:

2> if timer T302 is running:

…

2> else:

3> consider access to the cell as not barred;

1> else if the UE is establishing the RRC connection for emergency calls:

…

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> if timer T302 or T303 is running:

…

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to zero:

4> consider access to the cell as not barred;

3> else:

…

1> else (the UE is establishing the RRC connection for mobile originating signalling):

2> if timer T302 or T305 is running:

…

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Signalling is set to zero:

4> consider access to the cell as not barred;

3> else:

…

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

…

8.1.2.7.3 Test description

8.1.2.7.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 11 (HPLMN in different TA).

UE:

– None

Preamble:

The UE is in state Switched OFF (state 1) according to TS 36.508 [18].

8.1.2.7.3.2 Test procedure sequence

Table 8.1.2.7.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions at the beginning of each iteration of the test body, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.1.2.7.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 11	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	-91	The power level values are assigned to satisfy SrxlevCell 1 > SrxlevCell 11.
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy RCell 1 < RCell 11.
T2	Cell-specific RS EPRE	dBm/15kHz	Off	Off	The power level values are set to “cell off”.

Table 8.1.2.7.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: Steps 0 to 29 are run 5 times using test parameter values as given for each iteration in table 8.1.2.7.3.2-3	–	–	–	–
0	Insert USIM with EFACC as per table 8.1.2.7.3.2-3
0A	Void	–	–	–	–
0B	The SS changes Cell 1 and Cell 11 level according to the row "T0" in table 8.1.2.7.3.2-1.	–	–	–	–
0BA	The UE is switched on and brought to state Loop Back Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 according to [18]	–	–	–	–
0C	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	–	–	–	–
0D	Wait for 1 s after the IP packet has been transmitted in step 0. (Note 1)	–	–	–	–
1	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
2	Check: Does the UE transmit an RRCConnectionRequest message on Cell 1?	–>	RRCConnectionRequest	1	P
3	The SS transmits an RRCConnectionSetup message on Cell 1.	<–	RRCConnectionSetup	–	–
3A	The UE transmits an RRCConnectionSetupComplete message on Cell 1. This message includes a SERVICE REQUEST message.	–>	RRCConnectionSetupComplete	–	–
3B	The SS transmits a SecurityModeCommand message on Cell 1.	<–	SecurityModeCommand	–	–
3C	The UE transmits a SecurityModeComplete message on Cell 1.	–>	SecurityModeComplete	–	–
3D	The SS transmits an RRCConnectionReconfiguration message on Cell 1.	<–	RRCConnectionReconfiguration	–	–
–	EXCEPTION: Step 3E and 3EA can occur in any order	–	–	–	–
3E	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.	–>	RRCConnectionReconfigurationComplete	–	–
3EA	The UE loop backs the IP packet received in step 0 on the DRB associated with the default EPS bearer context on Cell 1.	–	–	–	–
3EB	The SS sends OPEN TEST LOOP message to open the UE test loop.	–	DLInformationTransfer	–	–
3EC	The UE responds with OPEN TEST LOOP COMPLETE message.	–	ULInformationTransfer	–	–
3F	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
3G	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
4	The SS changes Cell 1 and Cell 11 level according to the row "T1" in table 8.1.2.7.3.2-1.	–	–	–	–
4A	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 11 and that the UE has performed TAU procedure with establishment cause ‘high priority access’? NOTE: The UE performs a TAU procedure and the RRC connection is released.	–	–	2	–
5-10	Void	–	–	–	–
11	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
12-20	Void	–	–	–	–
21	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 11 and that the UE responds to paging with establishment cause ‘high priority access’?	–	–	1,2	–
22-28	The UE Switch off/Power off procedure is performed as per clause 10.1.2.1 of 36.523-3 [20]	–	–	–	–
29	The SS changes Cell 1 and Cell 11 level according to the row "T2" in table 8.1.2.7.3.2-1.	–	–	–	–
Note 1: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS in step 0 to the UE test loop function before the RRCConnectionRelease message is sent by the SS in step 1.

Table 8.1.2.7.3.3: Test Parameters

Iteration	EFACC
1	File size: 2 Bytes Default values (BIN): Byte 1: 100000 Byte 2: ******
2	File size: 2 Bytes Default values (BIN): Byte 1: 010000 Byte 2: ******
3	File size: 2 Bytes Default values (BIN): Byte 1: 001000 Byte 2: ******
4	File size: 2 Bytes Default values (BIN): Byte 1: 000100 Byte 2: ******
5	File size: 2 Bytes Default values (BIN): Byte 1: 000010 Byte 2: ******
Note: The test house may set any single bit shown by "*" to "1". This determines the access control class of the USIM

8.1.2.7.3.3 Specific message contents

Table 8.1.2.7.3.3-1: SystemInformationBlockType2 for Cell 1 and Cell 11 (preamble, Table 8.1.2.7.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	TRUE
ac-BarringForMO-Signalling SEQUENCE {
ac-BarringFactor	p00
ac-BarringTime	s4
ac-BarringForSpecialAC	‘00000’B
}
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor	p00
ac-BarringTime	s4
ac-BarringForSpecialAC	‘00000’B
}
}
}

Table 8.1.2.7.3.3-1A: CLOSE UE TEST LOOP (preamble, Table 8.1.2.7.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	‘0000 1010’B	10 seconds

Table 8.1.2.7.3.3-2: RRCConnectionRequest (step 2, step 4A and step 21, Table 8.1.2.7.3.2-2)

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

Table 8.1.2.7.3.3-3: Void

Table 8.1.2.7.3.3-4: Void

Table 8.1.2.7.3.3-5: Void

Table 8.1.2.7.3.3-6: Void

Table 8.1.2.7.3.3-7: Void

Table 8.1.2.7.3.3-8: RRCConnectionReconfiguration (step 3D, Table 8.1.2.7.3.2-2)

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

8.1.2.8 RRC connection establishment / Range of access baring time

8.1.2.8.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state with T303 running }

ensure that {
when { UE is requested to make an outgoing call }

then { UE does not transmit any RRCConnectionRequest message }

}

(2)

with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 with no restriction }

ensure that {
when { UE is requested to make an outgoing call }

then { UE transmits an RRCConnectionRequest message }

}

8.1.2.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.2.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if the UE is establishing the RRC connection for mobile terminating calls:

2> if timer T302 is running:

3> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else if the UE is establishing the RRC connection for emergency calls:

2> if SystemInformationBlockType2 includes the ac-BarringInfo:

3> if the ac-BarringForEmergency is set to FALSE:

4> consider access to the cell as not barred;

3> else if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11]:

NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

4> if the ac-BarringInfo includes ac-BarringForMO-Data, and for all of the valid Access Classes for the UE, the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to one:

5> consider access to the cell as barred;

4> else:

5> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> if timer T302 or T303 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Data:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else (the UE is establishing the RRC connection for mobile originating signalling):

2> if timer T302 or T305 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Signalling is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Signalling:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> else:

2> if the UE is establishing the RRC connection for mobile originating calls and if both timers T302 and T303 are not running:

3> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

3> start timer T303 with the timer value calculated as follows, using the ac-BarringTime included in ac-BarringForMO-Data:

T303= (0.7+ 0.6 _* rand) _* ac-BarringTime

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls is applicable, upon which the procedure ends;

2> else if the UE is establishing the RRC connection for mobile originating signalling and if both timers T302 and T305 are not running:

3> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

3> start timer T305 with the timer value calculated as follows, using the ac-BarringTime included in ac-BarringForMO-Signalling:

T305= (0.7+ 0.6 _* rand) _* ac-BarringTime

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

2> else if the UE is establishing the RRC connection for emergency calls:

3> inform upper layers about the failure to establish the RRC connection and that access barring for emergency calls is applicable, upon which the procedure ends;

2> else:

3> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends;

8.1.2.8.3 Test description

8.1.2.8.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

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

8.1.2.8.3.2 Test procedure sequence

Table 8.1.2.8.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including systemInfoModification. (Note 3)	<–	Paging	–	–
2	The SS changes SystemInformationBlockType2 parameters to 0% access probability for MO calls.	–	–	–	–
3	Wait for 15 s for the UE to receive system information.	–	–	–	–
4	Void	–	–	–	–
5	Cause the UE to request connectivity to an additional PDN. (Note 5)	–	–	–	–
5A	The UE does not transmit any RRCConnectionRequest message (The UE starts T303) (Note 2)	–	–	–	–
5B	Void	–	–	–	–
6	Cause the UE to request connectivity to an additional PDN. (Note 5)	–	–	–	–
7	Check: Does the UE transmit an RRCConnectionRequest message within 5s?	–>	RRCConnectionRequest	1	F
8	Wait for 20 s to ensure that T303 expires.	–	–	–	–
9	The SS transmits a Paging message including systemInfoModification (Note 3).	<–	Paging	–	–
10	The SS changes SystemInformationBlockType2 parameters to default values (Note 4).	–	–	–	–
11	The SS starts timer Timer_1 = 20 s.	–	–	–	–
–	EXCEPTION: Steps 12a1 to 12 b3 describe a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.(Note 6)	–	–	–	–
12a1	Check: Does the UE transmit an RRCConnectionRequest message? SS stops timer Timer_1	–>	RRCConnectionRequest	2	P
12b1	The SS waits for Timer_1 expiry	–	–	–	–
12 b2	Cause the UE to request connectivity to an additional PDN. (Note 5)	–	–	–	–
12b3	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	2	P
13	Void	–	–	–	–
14-23	Steps 2a2 to 6 of the generic test procedure in TS 36.508 [18] subclause 6.4.3.2 are performed on Cell 1	–	–	–	–
Note 1: Void. Note 2: The UE is establishing the RRC connection for mobile originating calls, and consider access to the cell as barred, the UE should draw a rand number “rand” in the range 0 ≤ rand < 1, and start T303 with value set to the maximum value: T303= (0.7+ 0.6 _* rand) _* ac-BarringTime. Note 3: To guarantee that the UE will receive at least one Paging in the Modification Period preceding the SysInfo change, SS should send the Paging message in every eligible PO in this Modification Period. Note 4: The default values refer to TS36.508 table 4.4.3.3-1. Note 5: The triggers in step 5, step 6 and step 12 b2 are the same as in the generic procedure in 36.508 clause 6.4.3.2. Note 6: A UE may send RRCConnectionRequest for the pending procedure triggered at step 6.

8.1.2.8.3.3 Specific message contents

Table 8.1.2.8.3.3-1: Paging (step 1 and step 9, Table 8.1.2.8.3.2-1)

Derivation path: 36.508 table 4.6.1-7
Information Element	Value/Remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList	Not present
systemInfoModification	True
}

Table 8.1.2.8.3.3-1A: SystemInformationBlockType1 (step 2, Table 8.1.2.8.3.2-1)

Derivation Path: 36.508, Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	1
}

Table 8.1.2.8.3.3-1B: SystemInformationBlockType1-BR-r13 (step 2 when UE under test is CAT-M1, Table 8.1.2.8.3.2-1)

Derivation Path: 36.508, Table 4.4.3.2-3A
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
systemInfoValueTag	1
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {	Not present
nonCriticalExtension SEQUENCE {			UECAT0
nonCriticalExtension SEQUENCE {
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE {
systemInfoValueTagList-r13 SEQUENCE (SIZE (1..maxSI-Message)) OF	n entries	The same number of entries, and listed in the same order, as in SchedulingInfoList (without suffix)
SystemInfoValueTagSI-r13[1]	SystemInfoValueTagSI-r13[k]=1, where k is the entry corresponding to the system info including SystemInformationBlockType2. For all other entries the value is set to 0 (same as in the default SystemInformationBlockType1-BR-r13 message).
SystemInfoValueTagSI-r13[n]
}
}
}
}
}
}
}

Table 8.1.2.8.3.3-2: SystemInformationBlockType2 (step 2, Table 8.1.2.8.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	FALSE	For AC 10
ac-BarringForMO-Signalling SEQUENCE {
ac-BarringFactor	p00
ac-BarringTime	s16
ac-BarringForSpecialAC	‘11111’B
}
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor	p00
ac-BarringTime	s16
ac-BarringForSpecialAC	‘11111’B	For AC 11..15
}
}
}

Table 8.1.2.8.3.3-3: SystemInformationBlockType1 (step 10, Table 8.1.2.8.3.2-1)

Derivation Path: 36.508, Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	2
}

Table 8.1.2.8.3.3-4: SystemInformationBlockType1-BR-r13 (step 10 when UE under test is CAT-M1, Table 8.1.2.8.3.2-1)

Derivation Path: 36.508, Table 4.4.3.2-3A
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
systemInfoValueTag	2
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {	Not present
nonCriticalExtension SEQUENCE {			UECAT0
nonCriticalExtension SEQUENCE {
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE {
systemInfoValueTagList-r13 SEQUENCE (SIZE (1..maxSI-Message)) OF	n entries	The same number of entries, and listed in the same order, as in SchedulingInfoList (without suffix)
SystemInfoValueTagSI-r13[1]	SystemInfoValueTagSI-r13[k]=2, where k is the entry corresponding to the system info including SystemInformationBlockType2. For all other entries the value is set to 0 (same as in the default SystemInformationBlockType1-BR-r13 message)
SystemInfoValueTagSI-r13[n]
}
}
}
}
}
}
}

8.1.2.9 RRC Connection Establishment / 0% access probability for MO calls, non-zero percent access probability for MO signalling

8.1.2.9.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE reselects a new cell which belongs to different TA and has received SystemInformationBlockType2 indicating non zero percent access probability for MO signalling }

then { UE does not transmit any RRCConnectionRequest message when access to the cell is considered as barred and UE transmits an RRCConnectionRequest message when access to the cell is considered as not barred }

}

(2)

with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 indicating 0% access probability for MO call }

ensure that {
when { UE has user data pending }

then { UE does not transmit any RRCConnectionRequest message }

}

8.1.2.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.2.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if the UE is establishing the RRC connection for mobile terminating calls:

…

1> else if the UE is establishing the RRC connection for emergency calls:

…

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> if timer T302 or T303 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Data:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else (the UE is establishing the RRC connection for mobile originating signalling):

2> if timer T302 or T305 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Signalling is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Signalling:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> else:

2> if the UE is establishing the RRC connection for mobile originating calls and if both timers T302 and T303 are not running:

…

2> else if the UE is establishing the RRC connection for mobile originating signalling and if both timers T302 and T305 are not running:

3> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

3> start timer T305 with the timer value calculated as follows, using the ac-BarringTime included in ac-BarringForMO-Signalling:

T305= (0.7+ 0.6 _* rand) _* ac-BarringTime

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

8.1.2.9.3 Test description

8.1.2.9.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 11.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 according to [18]. The preamble is employed in such a way that user initiated PDN disconnection is avoided because the cell 1 is access barred during the preamble. The 2nd PDN, if established, is deactived by the SS.

8.1.2.9.3.2 Test procedure sequence

Table 8.1.2.9.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 11	Remark
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy R_{Cell 1}< R_{Cell 11}.
T2	Cell-specific RS EPRE	dBm/15kHz	-85	-91	The power level values are assigned to satisfy R_{Cell 1} > R_{Cell 11}.

Table 8.1.2.9.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
2	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
3	The SS initializes internal counters: K to 0 and L to 0.	–	–	–	–
–	EXCEPTION: Steps 4 to 5b15 shall be repeated maximum 50 times unless K > 0 and L >0. (Note 1)	–	–	–	–
4	The SS changes the power level setting according to the row “T1” in table 8.1.2.9.3.2-1.	–	–	–	–
–	EXCEPTION: Steps 5a1 to 5b15 describe behaviours which vary depending on whether the UE transmits an RRCConnectionRequest message or not.	–	–	–	–
5a1	IF the UE does not transmit any RRCConnectionRequest message within 34 s when K=0 and L=0 and within 8 s for other repeat times, i.e. K ≠0 or L≠0 (Note 2) THEN the SS increments the counter K by 1.	–	–	–	–
5a2	The SS changes the power level setting according to the row “T2” in table 8.1.2.9.3.2-1.	–	–	–	–
5a3	The SS waits for 20s for the UE to perform cell reselection procedure. (Note 3)	–	–	–	–
5b1	ELSE IF the UE transmits an RRCConnectionRequest message on Cell 11 THEN the SS increments the counter L by 1.	–>	RRCConnectionRequest	–	–
5b2-5b6	Steps 2 to 6 of the generic test procedure in TS 36.508 [18] subclause 6.4.2.7 are performed on Cell 11. Note: The UE performs a TAU procedure and the RRC connection is released.	–	–	–	–
5b7	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
5b8	The SS changes the power level setting according to the row “T2” in table 8.1.2.9.3.2-1.	–	–	–	–
5b9	The UE transmits an RRCConnectionRequest message on Cell 1.	–>	RRCConnectionRequest	–	–
5b10-5b14	Steps 2 to 6 of the generic test procedure in TS 36.508 [18] subclause 6.4.2.7 are performed on Cell 1. Note: The UE performs a TAU procedure and the RRC connection is released.	–	–	–	–
5b15	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
6	Check: Is the counter K > 0 and L > 0?	–	–	1	P
7	Generic test procedure in TS 36.508 subclause 4.5.3.3 is performed on Cell 1. NOTE: The UE performs the establishment of the new data radio bearer associated with the default EPS bearer context.	–	–	–	–
8	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	–	–	–	–
9	Wait for 1 s after the IP packet has been transmitted in step 8. (Note 4)	–	–	–	–
10	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
11	Check: Does the UE transmit an RRCConnectionRequest message on Cell 1 within 30s?	–>	RRCConnectionRequest	2	F
–	EXCEPTION: Step 21 and Step 22a1 can happen in any order.	–	–	–	–
12-21	Check: Does the test result of steps 1 to 10 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?	–	–	1,2	–
–	EXCEPTION: Step 22a1 describes behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence that takes place if the UE has user data pending.	–	–	–	–
22a1	IF the UE has user data pending THEN the UE loop backs the IP packet received in step 8 on the DRB associated with the default EPS bearer context on Cell 1 within 10 s.	–	–	–	–
Note 1: There is an extremely low probability that the UE originating calls are barred, or not barred, 50 times consecutively. (The probability is 1.78×10^-15). Therefore, 50 times is enough number of trials for this test case. Note 2: The UE starts T305. Note 3: The UE stops T305 upon cell reselection. Note 4: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS in step 8 to the UE test loop function before the RRCConnectionRelease message is sent by the SS in step 10.

8.1.2.9.3.3 Specific message contents

Table 8.1.2.9.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble and all steps, Table 8.1.2.9.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	FALSE
ac-BarringForMO-Signalling SEQUENCE {}	Not present
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor	p00
ac-BarringTime	s512
ac-BarringForSpecialAC	‘11111’B
}
}
}

Table 8.1.2.9.3.3-2: SystemInformationBlockType2 for Cell 11 (preamble and all steps, Table 8.1.2.9.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	FALSE
ac-BarringForMO-Signalling SEQUENCE {
ac-BarringFactor	p50
ac-BarringTime	s64
ac-BarringForSpecialAC	‘00000’B
}
ac-BarringForMO-Data SEQUENCE {}	Not present
}
}

Table 8.1.2.9.3.3-3: CLOSE UE TEST LOOP (preamble, Table 8.1.2.9.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	‘0000 0101’B	5 seconds

Table 8.1.2.9.3.3-4: RRCConnectionRequest (step 5b1 and step 5b9, Table 8.1.2.9.3.2-2)

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

8.1.2.10 Void

8.1.2.11 Void

NOTE: The present test (RRC connection establishment of emergency call) is superseded by test case 11.2.1 (i.e. all requirements which the present test verified are verified in test case 11.2.1).

8.1.2.12 Void

NOTE: The present test (RRC connection establishment of emergency call / Limited Service) is superseded by test case 11.2.2 (i.e. all requirements which the present test verified are verified in test case 11.2.2).

8.1.2.13 RRC connection establishment / 0% access probability for MO calls, 0% access probability for MO signalling

8.1.2.13.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts SystemInformationBlockType2 indicating 0% access probability for MO signalling }

then { UE does not transmit any RRCConnectionRequest message }

}

(2)

with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 indicating 0% access probability for MO call and for MO signalling }

ensure that {
when { UE receives a Paging message }

then { UE transmits an RRCConnectionRequest message }

}

(3)

with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 indicating 0% access probability for MO call }

ensure that {
when { UE has user data pending }

then { UE does not transmit any RRCConnectionRequest message }

}

8.1.2.13.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.2.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if the UE is establishing the RRC connection for mobile terminating calls:

…

1> else if the UE is establishing the RRC connection for emergency calls:

…

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> if timer T302 or T303 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Data:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> else (the UE is establishing the RRC connection for mobile originating signalling):

2> if timer T302 or T305 is running:

3> consider access to the cell as barred;

2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Signalling is set to zero:

4> consider access to the cell as not barred;

3> else:

4> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

4> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Signalling:

5> consider access to the cell as not barred;

4> else:

5> consider access to the cell as barred;

2> else:

3> consider access to the cell as not barred;

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> else:

2> if the UE is establishing the RRC connection for mobile originating calls and if both timers T302 and T303 are not running:

…

2> else if the UE is establishing the RRC connection for mobile originating signalling and if both timers T302 and T305 are not running:

3> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

3> start timer T305 with the timer value calculated as follows, using the ac-BarringTime included in ac-BarringForMO-Signalling:

T305= (0.7+ 0.6 _* rand) _* ac-BarringTime

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

8.1.2.13.3 Test description

8.1.2.13.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 11.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 according to [18].

8.1.2.13.3.2 Test procedure sequence

Table 8.1.2.13.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 11	Remark
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy R_{Cell 1}< R_{Cell 11}.
T2	Cell-specific RS EPRE	dBm/15kHz	-85	-91	The power level values are assigned to satisfy R_{Cell 1} > R_{Cell 11}.

Table 8.1.2.13.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
2	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
3	The SS changes the power level setting according to the row “T1” in table 8.1.2.13.3.2-1.	–	–	–	–
4	Check: Does the UE transmit an RRCConnectionRequest message on Cell 11 within 40s? (Note 1)	–>	RRCConnectionRequest	1	F
5	The SS transmits a Paging message including a matched identity allocated in Cell 1.	<–	Paging	–	–
6	Check: Does the UE transmit an RRCConnectionRequest message on Cell 1 within 30s? (Note 2)	–>	RRCConnectionRequest	1	F
7	The SS changes the SystemInformationBlockType1 and SystemInformationBlockType2 on Cell 1 according to Table 8.1.2.13.3.3-1.	–	–	–	–
7A	Wait for 2.1* modification period (Note 5) to allow the new system information to take effect.	–	–	–	–
7B	The SS changes the power level setting according to the row “T2” in table 8.1.2.13.3.2-1.	–	–	–	–
8	The SS waits for 40s the UE to perform cell reselection procedure (Note 3).	–	–	–	–
9	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 pagingRecordLists on Cell 1.	<–	Paging	–	–
10	Check: Does the UE transmit an RRCConnectionRequest message on Cell 1?	–>	RRCConnectionRequest	2	P
11-16	Steps 4 to 9 of the generic test procedure in TS 36.508 subclause 4.5.3.3 are performed on Cell 1. NOTE: The UE performs the establishment of the new data radio bearer associated with the default EPS bearer context.	–	–	–	–
17	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	–	–	–	–
18	Wait for 1 s after the IP packet has been transmitted in step 17. (Note 4)	–	–	–	–
19	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease	–	–
20	Check: Does the UE transmit an RRCConnectionRequest message on Cell 1 within 10s?	–>	RRCConnectionRequest	3	F
–	EXCEPTION: Step 30 and Step 31a1 can happen in any order.	–	–	–	–
21-30	Check: Does the test result of steps 1 to 10 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?	–	–	1,2,3	–
–	EXCEPTION: Step 31a1 describes behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence that takes place if the UE has user data pending.	–	–	–	–
31a1	IF the UE has user data pending THEN the UE loop backs the IP packet received in step 17 on the DRB associated with the default EPS bearer context on Cell 1 within 10 s.	–	–	–	–
Note 1: The UE starts T305. Note 2: In case that the UE did not response to paging on Cell 1, it is considered that the UE is camped on Cell 11. Note 3: The UE stops T305 upon cell reselection. Note 4: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS in step 17 to the UE test loop function before the RRCConnectionRelease message is sent by the SS in step 19. Note 5: The wait time of 2.1* modification period in step 7A is to allow for the network to paging the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

8.1.2.13.3.3 Specific message contents

Table 8.1.2.13.3.3-1: SystemInformationBlockType2 for Cell 1 (step 7, Table 8.1.2.13.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	FALSE
ac-BarringForMO-Signalling SEQUENCE {
ac-BarringFactor	p0
ac-BarringTime	s8
ac-BarringForSpecialAC	‘11111’B
}
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor	p0
ac-BarringTime	s512
ac-BarringForSpecialAC	‘11111’B
}
}
}

Table 8.1.2.13.3.3-2: SystemInformationBlockType1 for Cell 1 (step 7, Table 8.1.2.13.3.2-2)

Derivation Path: 36.508, Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	1
}

Table 8.1.2.13.3.3-2A: SystemInformationBlockType1-BR-r13 for Cell 1 (step 7 when UE under test is CAT M1, Table 8.1.2.13.3.2-2)

Derivation Path: 36.508, Table 4.4.3.2-3A
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
systemInfoValueTag	1
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE {
systemInfoValueTagList-r13 SEQUENCE (SIZE (1..maxSI-Message)) OF	n entries	The same number of entries, and listed in the same order, as in SchedulingInfoList (without suffix)
SystemInfoValueTagSI-r13[1]	SystemInfoValueTagSI-r13[k]=1, where k is the entry corresponding to the system info including SystemInformationBlockType2. For all other entries the value is set to 0 (same as in the default SystemInformationBlockType1-BR-r13 message).
…. SystemInfoValueTagSI-r13[n]
}
}
}
}
}
}
}

Table 8.1.2.13.3.3-3: SystemInformationBlockType2 for Cell 11 (preamble and all steps, Table 8.1.2.13.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency	FALSE
ac-BarringForMO-Signalling SEQUENCE {
ac-BarringFactor	p0
ac-BarringTime	s512
ac-BarringForSpecialAC	‘11111’B
}
ac-BarringForMO-Data SEQUENCE {}	Not present
}
}

Table 8.1.2.13.3.3-4: CLOSE UE TEST LOOP (preamble, Table 8.1.2.13.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	‘0000 0101’B	5 seconds

8.1.2.14 RRC connection establishment / High speed flag

8.1.2.14.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating an IE highSpeedFlag set to true }

ensure that {
when { UE receives a Paging message }

then { UE establishes an RRC connection }

}

8.1.2.14.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.2.2.9 and 6.3.2.

[TS 36.331, clause 5.2.2.9]

Upon receiving SystemInformationBlockType2, the UE shall:

…

1> apply the configuration included in the radioResourceConfigCommon;

[TS 36.331, clause 6.3.2]

PRACH-Config field descriptions
…
highSpeedFlag Parameter: High-speed-flag, see TS 36.211, [21, 5.7.2].TRUE corresponds to Restricted set and FALSE to Unrestricted set.

PRACH-Config field descriptions

…

highSpeedFlag

Parameter: High-speed-flag, see TS 36.211, [21, 5.7.2].TRUE corresponds to Restricted set and FALSE to Unrestricted set.

8.1.2.14.3 Test description

8.1.2.14.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

UE:

None.

Preamble:

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

8.1.2.14.3.2 Test procedure sequence

Table 8.1.2.14.3.2-1 illustrates the downlink power levels to be applied for the cells at various time instants of the test execution. The configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.1.2.14.3.2-2.

Table 8.1.2.14.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 2	Remark
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy R_{Cell 1}< R_{Cell 2}.

Table 8.1.2.14.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes Cell 2 level according to the row “T1” in table 8.1.2.14.3.2-1.	–	–	–	–
2	The SS waits for 40s for the UE to perform cell reselection procedure.	–	–	–	–
3	The SS transmits a Paging message on Cell 2.	<–	Paging	–	–
4	Check: Does the UE transmit an RRCConnectionRequest message on Cell 2?	–>	RRCConnectionRequest	1	P
5-10	Steps 4 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure on Cell 2.	–	–	–	–
11	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 2?	–	–	1	–

8.1.2.14.3.3 Specific message contents

Table 8.1.2.14.3.3-1: SystemInformationBlockType2 for Cell 2 (preamble and all steps, Table 8.1.2.14.3.2-2)

Derivation Path: 36.508 Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
prach-Config SEQUENCE {
rootSequenceIndex	86
prach-ConfigInfo SEQUENCE {
highSpeedFlag	true
}
}
}
}

8.1.2.15 RRC connection establishment / Extended and spare fields in SI

8.1.2.15.1 Test Purpose (TP)

(1)

with { UE is powered on and receives system information }

ensure that {

when { UE receives an optional spare or extended field in system information that it does not comprehend }

then { UE treats system information as if the spare or extended field were absent and system information is not ignored, and UE establishes an RRC connection }

}

8.1.2.15.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.2.2.3, 5.7.1 and 5.7.3.

[TS 36.331 clause 5.2.2.3]

The UE shall:

1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as the ‘required’ system information:

2> if in RRC_IDLE:

3> if the UE is a NB-IoT UE:

4> the MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB and SystemInformationBlockType1-NB as well as SystemInformationBlockType2-NB through SystemInformationBlockType5-NB, SystemInformationBlockType22-NB;

3> else:

4> the MasterInformationBlock and SystemInformationBlockType1 (or SystemInformationBlockType1-BR depending on whether the UE is a BL UE or the UE in CE) as well as SystemInformationBlockType2 through SystemInformationBlockType8 and SystemInformationBlockType24 (depending on support of the concerned RATs), SystemInformationBlockType17 (depending on support of RAN-assisted WLAN interworking when the UE is connected to EPC), SystemInformationBlockType25 (depending on support of E-UTRA/5GC);

2> if in RRC_INACTIVE:

3> the MasterInformationBlock and SystemInformationBlockType1 as well as SystemInformationBlockType2 through SystemInformationBlockType8 (depending on support of the concerned RATs), SystemInformationBlockType25;

2> if in RRC_CONNECTED; and

2> the UE is not a BL UE; and

2> the UE is not in CE; and

2> the UE is not a NB-IoT UE:

3> the MasterInformationBlock, SystemInformationBlockType1 and SystemInformationBlockType2 as well as SystemInformationBlockType8 (depending on support of CDMA2000), SystemInformationBlockType17 (depending on support of RAN-assisted WLAN interworking when the UE is connected to EPC), SystemInformationBlockType25 (depending on support of E-UTRA/5GC);

2> if in RRC_CONNECTED and T311 is running; and

2> the UE is a BL UE or the UE is in CE or the UE is a NB-IoT UE;

3> the MasterInformationBlock (or MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT), SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) and SystemInformationBlockType2 (or SystemInformationBlockType2-NB in NB-IoT), and for NB-IoT SystemInformationBlockType22-NB;

1> delete any stored system information after 3 hours or 24 hours from the moment it was confirmed to be valid as defined in 5.2.1.3, unless specified otherwise;

1> consider any stored system information except SystemInformationBlockType10, SystemInformationBlockType11, systemInformationBlockType12 and systemInformationBlockType14 (systemInformationBlockType14-NB in NB-IoT) to be invalid if systemInfoValueTag included in the SystemInformationBlockType1 (MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT) is different from the one of the stored system information and in case of NB-IoT UEs, BL UEs and UEs in CE, systemInfoValueTagSI is not broadcasted. Otherwise consider system information validity as defined in 5.2.1.3;

[TS 36.331 clause 5.7.1]

The generic error handling defined in the subsequent sub-clauses applies unless explicitly specified otherwise e.g. within the procedure specific error handling.

The UE shall consider a value as not comprehended when it is set:

– to an extended value that is not defined in the version of the transfer syntax supported by the UE.

– to a spare or reserved value unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/ reserved value.

The UE shall consider a field as not comprehended when it is defined:

– as spare or reserved unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/ reserved field.

[TS 36.331 clause 5.7.3]

The UE shall, when receiving an RRC message on any logical channel:

1> if the message includes a field that has a value that the UE does not comprehend:

2> if a default value is defined for this field:

3> treat the message while using the default value defined for this field;

2> else if the concerned field is optional:

3> treat the message as if the field were absent and in accordance with the need code for absence of the concerned field;

2> else:

3> treat the message as if the field were absent and in accordance with sub-clause 5.7.4;

8.1.2.15.3 Test description

8.1.2.15.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Switched OFF (state 1) according to TS 36.508 [18].

8.1.2.15.3.2 Test procedure sequence

Table 8.1.2.15.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	System information that includes extended and spare fields that the UE does not comprehend is broadcasted on BCCH and BCCH-BR. NOTE: Spare field testing is not applicable for Rel-12 UE because a spare field in MIB or SIB1 does not exist in Rel-12.	<–	RRC: SYSTEM INFORMATION (BCCH and BCCH-BR)	–	–
2	The UE is switched on.	–	–	–	–
3	Does the UE transmit an RRCConnectionRequest message on Cell 1?	–>	RRCConnectionRequest	1	P
4	The SS transmits an RRCConnectionSetup message on Cell 1.	<–	RRCConnectionSetup	–	–
5	Check: Does the UE transmit an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message? The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST.	–>	RRCConnectionSetupComplete NAS: ATTACH REQUEST NAS: PDN CONNECTIVITY REQUEST	1	P
6-18	Steps 5 to 17 of the registration procedure described in TS 36.508 subclause 4.5.2.3 are performed on Cell 1.	–	–	–	–
NOTE: SIB-Type and si-WindowLength-BR-r13 in SystemInformationBlockType1 and SystemInformationBlockType1-BR are set to values in Rel-16 to check spare and extended fields in UE up to Rel-15.

8.1.2.15.3.3 Specific message contents

Table 8.1.2.15.3.3-1: Message MasterInformationBlock (step 1, Table 8.1.2.15.3.2-1)

Derivation Path: 36.508 Table 4.4.3.2-1
Information Element	Value/remark	Comment	Condition
MasterInformationBlockType1 ::= SEQUENCE {
dl-Bandwidth	Downlink system bandwidth under test.
phich-Config SEQUENCE {}	PHICH-Config-Default
systemFrameNumber	A valid value as defined in TS 36.331 [17]
schedulingInfoSIB1-BR-r13	10
spare	‘1111’B	From Rel-8 to Rel-15, the lowest 4 bits are considered spares according to TS 36.331 [17].	For Rel-8 to Rel-15
}

Table 8.1.2.15.3.3-2: Message SystemInformationBlockType1 (step 1, Table 8.1.2.15.3.2-1)

Derivation Path: 36.508 Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {	3 entries
si-Periodicity[1]	rf16
sib-MappingInfo[1]		SIB2, SIB3
si-Periodicity[2]	As per TS 36.508[18] clause 4.4.3.4
sib-MappingInfo[2]	sibType3
si-Periodicity[3]	rf32
sib-MappingInfo[3] SEQUENCE (SIZE (0..maxSIB-1)) OF {	1 entry
SIB-Type[1]	sibType26-v1530	From Rel-8 to Rel-14, the field used for sibType26-v1530 is considered an extended field according to TS 36.331 [17].	For Rel-8 to Rel-14
SIB-Type[1]	sibType29-v1610	For Rel-15, the field used for sibType29-v1610 is considered an extended field according to TS 36.331 [17].	For Rel-15
}
}
}

Table 8.1.2.15.3.3-3: Message SystemInformationBlockType1-BR-r13 (step 1, Table 8.1.2.15.3.2-1)

Derivation Path: 36.508 Table 4.4.3.2-3A
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {	3 entries
si-Periodicity[1]	rf16
sib-MappingInfo[1]		SIB2, SIB3
si-Periodicity[2]	As per TS 36.508[18] clause 4.4.3.4.
sib-Mappinginfo[2]	sibType3
si-Periodicity[3]	rf32
sib-MappingInfo[3] SEQUENCE (SIZE (0..maxSIB-1)) OF {	1 entry
SIB-Type[1]	sibType26-v1530	From Rel-13 to Rel-14, the field used for sibType26-v1530 is considered an extended field according to TS 36.331 [17].	For Rel-13 to Rel-14
SIB-Type[1]	sibType29-v1610	For Rel-15, the field used for sibType29-v1610 is considered an extended field according to TS 36.331 [17].	For Rel-15.
}
}
}

Iteration	EFACC
1	File size: 2 Bytes Default values (BIN): Byte 1: 100000 Byte 2: ******
2	File size: 2 Bytes Default values (BIN): Byte 1: 010000 Byte 2: ******
3	File size: 2 Bytes Default values (BIN): Byte 1: 001000 Byte 2: ******
4	File size: 2 Bytes Default values (BIN): Byte 1: 000100 Byte 2: ******
5	File size: 2 Bytes Default values (BIN): Byte 1: 000010 Byte 2: ******
Note: The test house may set any single bit shown by "*" to "1". This determines the access control class of the USIM