7.1.2 RACH

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

7.1.2.1 Correct selection of RACH parameters / Random access preamble and PRACH resource explicitly signalled to the UE by RRC / Non-contention based random access procedure

7.1.2.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { SS sends an RRCConnectionReconfiguration message including RACH-ConfigDedicated information element }

then { UE sends a prach preamble given in the RACH-ConfigDedicated on the target cell }

}

7.1.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.2 and 5.1.4.

[TS 36.321, clause 5.1.2]

The Random Access Resource selection procedure shall be performed as follows:

– If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000:

– the Random Access Preamble and the PRACH Mask Index are those explicitly signalled.

[TS 36.321, clause 5.1.4]

Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the UE shall monitor the PDCCH for Random Access Response(s) identified by the RA-RNTI defined below, in the RA Response window which starts at the subframe that contains the end of the preamble transmission [7] plus three subframes and has length ra-ResponseWindowSize subframes. The RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as:

RA-RNTI= 1 + t_id+10*f_id

Where t_id is the index of the first subframe of the specified PRACH (0≤ t_id <10), and f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0≤ f_id< 6). The UE may stop monitoring for Random Access Response(s) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted Random Access Preamble.

– If a downlink assignment for this TTI has been received on the PDCCH for the RA-RNTI and the received TB is successfully decoded, the UE shall regardless of the possible occurrence of a measurement gap:

…

– if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble (see subclause 5.1.3), the UE shall:

– consider this Random Access Response reception successful;

– process the received Timing Advance Command (see subclause 5.2);

– indicate the preambleInitialReceivedTargetPower and the amount of power ramping applied to the latest preamble transmission to lower layers (i.e., (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep);

– process the received UL grant value and indicate it to the lower layers;

– if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC):

– consider the Random Access procedure successfully completed.

7.1.2.1.3 Test description

7.1.2.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

UE:

None.

Preamble:

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

7.1.2.1.3.2 Test procedure sequence

Table 7.1.2.1.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 after preamble, 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 7.1.2.1.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 2	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	-91	The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy exit condition for event A3 (M2 < M1).
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M2 > M1).

Table 7.1.2.1.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0A	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup intra frequency measurement.	<–	–	–	–
0B	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.	–>	–	–	–
0C	The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 7.1.2.1.3.2-1.	–	–	–	–
0D	The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 2.	–>	–	–	–
1	The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2, including explicit Random Access Preamble.	<–	–	–	–
2	Check: Does the UE transmit Preamble on PRACH corresponding to ra-PreambleIndex in step 1?	–>	(PRACH Preamble)	1	P
3	The SS transmits Random Access Response on cell 2, with RAPID corresponding to ra-PreambleIndex in step 1	<–	Random Access Response	–	–
4	Check: Does the UE sends on cell 2, a MAC PDU containing RRCConnectionReconfigurationComplete?	–>	MAC PDU (RRCConnectionReconfigurationComplete)	1	P
5	Check: Does the test result of generic procedure in TS 36.508 subclause 6.4.2.3 indicates that UE is in E-UTRA RRC_CONNECTED state in cell 2?	–	–	1	–

7.1.2.1.3.3 Specific message contents

Table 7.1.2.1.3.3-0: Conditions for specific message contents
in Table 7.1.2.1.3.3-0B

Condition	Explanation
Band > 64	If band > 64 is selected

Table 7.1.2.1.3.3-0A: RRCConnectionReconfiguration (step 0A, Table 7.1.2.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 7.1.2.1.3.3-0B: MeasConfig (Table 7.1.2.1.3.3-0A)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1
Information Element	Value/remark	Comment	Condition
measConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	1 entry
measObjectId[1]	IdMeasObject-f1
measObject[1]	MeasObjectEUTRA-GENERIC(f1)
measObject[1]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfig-A3
reportConfig[1]	ReportConfig-A3
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f1
reportConfigId[1]	IdReportConfig-A3
}
measGapConfig	MeasGapConfig-CE		intraFreq-CE-NeedForGaps
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	1 entry		Band > 64
measObjectEUTRA-v9e0[1] SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
}
}

Condition	Explanation
intraFreq-CE-NeedForGaps	For UE having set pc_intraFreq-CE-Need ForGaps to TRUE.

Table 7.1.2.1.3.3-0C; MeasObjectEUTRA-GENERIC (Table 7.1.2.1.3.3-0B)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-3 MeasObjectEUTRA-GENERIC(f1)
Information Element	Value/remark	Comment	Condition
MeasObjectEUTRA-GENERIC(f1) ::= SEQUENCE {
blackCellsToAddModList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE {	1 entry	Add Cell 2
cellIndex[1]	1
physCellIdRange[1]	physicalCellIdentity-Cell2
}
}

Table 7.1.2.1.3.3-0D: ReportConfig-A3 (Table 7.1.2.1.3.3-0C)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-6 ReportConfigEUTRA-A3
Information Element	Value/remark	Comment	Condition
ReportConfigEUTRA-A3 ::= SEQUENCE {
maxReportCells	1	Report Cell 2
reportInterval	Not present
}

Table 7.1.2.1.3.3-1: RRCConnectionReconfiguration (step 1, table 7.1.2.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition RBC-HO
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInfo SEQUENCE {	MobilityControlInfo-HO
targetPhysCellId	PhysicalCellIdentity of Cell 2 (see 36.508 clause 4.4.4.2)
carrierFreq	Not present
rach-ConfigDedicated SEQUENCE {
ra-PreambleIndex	52 (see TS 36.211 Table 5.7.1-2)		FDD
ra-PreambleIndex	52 (see TS 36.211 Table 5.7.1-3)		TDD
ra-PRACH-MaskIndex	0	All
}
}
nonCriticalExtension SEQUENCE {			CEmodeA CEmodeB
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {
otherConfig-r9	Not present
fullConfig-r9	Not present
nonCriticalExtension SEQUENCE {
sCellToReleaseList-r10	Not present
sCellToAddModList-r10	Not present
nonCriticalExtension SEQUENCE {
systemInformationBlockType1Dedicated-r11	SystemInformationBlockType1-BR-r13 of Cell 2
nonCriticalExtension	Not present
}
}
}
}
}
}
}
}

7.1.2.1a Correct selection of RACH parameters / Random access preamble and PRACH resource explicitly signalled to the UE by RRC / Non-contention based random access procedure for high speed scenario

7.1.2.1a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { SS sends an RRCConnectionReconfiguration message including RACH-ConfigDedicated information element }

then { UE sends a prach preamble given in the RACH-ConfigDedicated on the target cell which is identified in high speed train area}

}

7.1.2.1a.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.2 and 5.1.4, and TS 36.211, clauses 5.7.1 and 5.7.2.

[TS 36.321, clause 5.1.2]

The Random Access Resource selection procedure shall be performed as follows:

– If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000:

– the Random Access Preamble and the PRACH Mask Index are those explicitly signalled.

[TS 36.321, clause 5.1.4]

RA-RNTI= 1 + t_id+10*f_id

…

– if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble (see subclause 5.1.3), the UE shall:

– consider this Random Access Response reception successful;

– process the received Timing Advance Command (see subclause 5.2);

– process the received UL grant value and indicate it to the lower layers;

– if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC):

– consider the Random Access procedure successfully completed.

[TS 36.211, clause 5.7.1]

…

For non-BL/CE UEs there are up to two PRACH configurations in a cell. The first PRACH configuration is configured by higher layers with a PRACH configuration index (prach-ConfigurationIndex) and a PRACH frequency offset (prach-FrequencyOffset). The second PRACH configuration (if any) is configured by higher layers with a PRACH configuration index (prach-ConfigurationIndexHighSpeed) and a PRACH frequency offset (prach-FrequencyOffsetHighSpeed).

…

[TS 36.211, clause 5.7.2 Preamble sequence generation]

The random access preambles are generated from Zadoff-Chu sequences with zero correlation zone, generated from one or several root Zadoff-Chu sequences. The network configures the set of preamble sequences the UE is allowed to use.

There are up to two sets of 64 preambles available in a cell where Set 1 corresponds to higher layer PRACH configuration using prach-ConfigurationIndex and prach-FrequencyOffset and Set 2, if configured, corresponds to higher layer PRACH configuration using prach-ConfigurationIndexHighSpeed and prach-FrequencyOffsetHighSpeed. The set of 64 preamble sequences in a cell is found by including first, in the order of increasing cyclic shift, all the available cyclic shifts of a root Zadoff-Chu sequence with the logical index rootSequenceIndexHighSpeed (for Set 2, if configured) or with the logical index RACH_ROOT_SEQUENCE (for Set 1), where both rootSequenceIndexHighSpeed (if configured) and RACH_ROOT_SEQUENCE are broadcasted as part of the System Information. Additional preamble sequences, in case 64 preambles cannot be generated from a single root Zadoff-Chu sequence, are obtained from the root sequences with the consecutive logical indexes until all the 64 sequences are found.
The logical root sequence order is cyclic: the logical index 0 is consecutive to 837. The relation between a logical root sequence index and physical root sequence index is given by Tables 5.7.2-4 and 5.7.2-5 for preamble formats 0 – 3 and 4, respectively.

The root Zadoff-Chu sequence is defined by

where the length of the Zadoff-Chu sequence is given by Table 5.7.2-1. From the root Zadoff-Chu sequence, random access preambles with zero correlation zones of length are defined by cyclic shifts according to

where the cyclic shift is given by

and is given by Tables 5.7.2-2 and 5.7.2-3 for preamble formats 0-3 and 4, respectively, where the higher-layer parameters zeroCorrelationZoneConfig and zeroCorrelationZoneConfigHighSpeed shall be used for PRACH preamble Set 1 and Set 2 (if configured), respectively. Restricted set type B shall be used for PRACH preamble Set 2 (if configured), and the parameter High-speed-flag provided by higher layers determines if unrestricted set or restricted set type A shall be used for PRACH preamble Set 1.

…

Table 5.7.2-2: for preamble generation (preamble formats 0-3)

zeroCorrelationZoneConfig, zeroCorrelationZoneConfigHighSpeed	value
	Unrestricted set	Restricted set type A	Restricted set type B
0	0	15	15
1	13	18	18
2	15	22	22
3	18	26	26
4	22	32	32
5	26	38	38
6	32	46	46
7	38	55	55
8	46	68	68
9	59	82	82
10	76	100	100
11	93	128	118
12	119	158	137
13	167	202	–
14	279	237	–
15	419	–	–

7.1.2.1a.3 Test description

7.1.2.1a.3.1 Pre-test conditions

See Clause 7.1.2.1.3.1

7.1.2.1a.3.2 Test procedure sequence

See clause 7.1.2.1.3.2

7.1.2.1a.3.3 Specific message contents

Table 7.1.2.1a.3.3-1: RRCConnectionReconfiguration (step 1, table 7.1.2.1a.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition RBC-HO
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInfo SEQUENCE {	MobilityControlInfo-HO
targetPhysCellId	PhysicalCellIdentity of Cell 2 (see 36.508 clause 4.4.4.2)
carrierFreq	Not present
radioResourceConfigCommon ::= SEQUENCE{	RadioResourceConfigCommon-DEFAULT
highSpeedConfig-r14	HighSpeedConfig-r14-DEFAULT
prach-Config-v1430	PRACH-Config-v1430-DEFAULT
}
rach-ConfigDedicated SEQUENCE {
ra-PreambleIndex	52 (see TS 36.211		FDD
ra-PreambleIndex	52 (see TS 36.211 )		TDD
ra-PRACH-MaskIndex	0	All
}
}
}
}
}
}

7.1.2.2 Correct selection of RACH parameters / Random access preamble and PRACH resource explicitly signalled to the UE in PDCCH Order / Non-contention based random access procedure

7.1.2.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { PDCCH control command is received providing Random Access Preamble }

then { UE sends a prach preamble given in the PDCCH Order }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and transmitted PRACH Preamble, after reception of PDCCH order }

ensure that {

when { UE does not receive a matching Random Access response in ra-ResponseWindowSize (hence considers RACH attempt as failed) and PREAMBLE_TRANSMISSION_COUNTER is less than PREAMBLE_TRANS_MAX }

then { UE retransmits the Preamble given in the PDCCH Order }

}

7.1.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.2 and 5.1.24.

[TS 36.321, clause 5.1.2]

The Random Access Resource selection procedure shall be performed as follows:

– If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000:

– the Random Access Preamble and the PRACH Mask Index are those explicitly signalled.

[TS 36.321, clause 5.1.4]

RA-RNTI= 1 + t_id+10*f_id

Where t_id is the index of the first subframe of the specified PRACH (0≤ t_id <10), and f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0≤ f_id< 6). The UE may stop monitoring for Random Access Response(s) after successful reception of a Random Access Response containing the Random Access Preamble identifiers that matches the transmitted Random Access Preamble.

…

– if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble (see subclause 5.1.3), the UE shall:

– consider this Random Access Response reception successful;

– process the received Timing Advance Command (see subclause 5.2);

– process the received UL grant value and indicate it to the lower layers;

– if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC):

– consider the Random Access procedure successfully completed.

…

If no Random Access Response is received within the RA Response window, or if none of all received Random Access Responses contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble, the Random Access Response reception is considered not successful and the UE shall:

– increment PREAMBLE_TRANSMISSION_COUNTER by 1;

– If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:

– indicate a Random Access problem to upper layers

– if in this Random Access procedure, the Random Access Preamble was selected by MAC:

– based on the back off parameter in the UE, select a random back off time according to a uniform distribution between 0 and the Back off Parameter Value;

– delay the subsequent Random Access transmission by the back off time;

– proceed to the selection of a Random Access Resource (see subclause 5.1.2).

7.1.2.2.3 Test description

7.1.2.2.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] in cell 1

7.1.2.2.3.2 Test procedure sequence

Table 7.1.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a PDCCH order providing Random Access Preamble.	<–	(PDCCH Order)	–	–
2	Check: does the UE transmit a preamble on PRACH using the same preamble index as given in step 1?	–>	(PRACH Preamble)	1	P
3	Check: does the UE transmit a preamble on PRACH after ra-ResponseWindowSize using the same preamble index as given in step 1?	–>	(PRACH Preamble)	2	P
4	Check: does the UE transmit a preamble on PRACH after ra-ResponseWindowSize using the same preamble index as given in step 1?	–>	(PRACH Preamble)	2	P
5	Check: does the UE transmit a preamble on PRACH after ra-ResponseWindowSize using the same preamble index as given in step 1?	–>	(PRACH Preamble)	2	P
6	The SS transmits Random Access Response with RAPID corresponding to Preamble in step 1.	<–	Random Access Response	–	–
7	Check: does the test result of CALL generic procedure indicate that UE is in E-UTRA RRC_CONNECTED state?	–	–	2	–

7.1.2.2.3.3 Specific message contents

Table 7.1.2.2.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.2.3.2-1)

Derivation Path: 36.508 clause 4.4.3.3, Table Nr. 4.4.3.3.-1
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
rach-Configuration SEQUENCE {
ra-SupervisionInformation SEQUENCE {
preambleTransMax	N4	PREAMBLE_TRANS_MAX
}
}
}
}
}

7.1.2.3 Correct selection of RACH parameters / Preamble selected by MAC itself / Contention based random access procedure

7.1.2.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {

when { SS sends a Paging message to the UE and MAC PDU Size carrying CCCH PDU is less than messageSizeGroupA }

then { UE transmits a random access preamble using a preamble in group A of random access preambles indicated in SIB2 }

}

(2)

with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 }

ensure that {

when { SS does not respond before contention resolution timer expiry }

then { UE transmits a random access preamble using a preamble in the same group of random access preambles as used for the first transmission of Msg3 }

}

(3)

with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 }

ensure that {

when { SS does not respond before contention resolution timer expiry after more than preambleTransMax transmissions from UE }

then { UE transmits a random access preamble using a preamble in the same group of random access preambles as used for the first transmission of Msg3 }

}

(4)

with { UE in E-UTRA RRC_IDLE state }

ensure that {

when { UE has data available for transmission and the MAC PDU Size carrying this data is greater than messageSizeGroupA }

then { UE transmits a random access preamble using a preamble in group B of random access preambles indicated in SIB2 }

}

7.1.2.3.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.2 and 5.1.5.

[TS 36.321, clause 5.1.2]

The Random Access Resource selection procedure shall be performed as follows:

– If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000:

…

– else the Random Access Preamble shall be selected by the UE as follows:

– If Msg3 has not yet been transmitted, the UE shall:

– if Random Access Preambles group B exists and if the potential message size (data available for transmission plus MAC header and, where required, MAC control elements) is greater than messageSizeGroupA and if the pathloss is less than P_CMAX–preambleInitialReceivedTargetPower – deltaPreambleMsg3 – messagePowerOffsetGroupB, then:

– select the Random Access Preambles group B;

– else:

– select the Random Access Preambles group A.

– else, if Msg3 is being retransmitted, the UE shall, the UE shall:

– select the same group of Random Access Preambles as was used for the preamble transmission attempt corresponding to the first transmission of Msg3.

– randomly select a Random Access Preamble within the selected group. The random function shall be such that each of the allowed selections can be chosen with equal probability;

– set PRACH Mask Index to 0.

– determine the next available subframe containing PRACH permitted by the restrictions given by the prach-ConfigIndex and PRACH Mask Index (see subclause 7.3) and physical layer timing requirements [2] (a UE may take into account the possible occurrence of measurement gaps when determining the next available PRACH subframe);

– if the transmission mode is TDD and the PRACH Mask Index is equal to zero:

– if ra-PreambleIndex was explicitly signalled and the signalled random access preamble ID was not 000000 (i.e., not selected by MAC):

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe.

– else:

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe and the next two consecutive subframes.

– else:

– determine a PRACH within the determined subframe in accordance with the requirements of the PRACH Mask Index.

– proceed to the transmission of the Random Access Preamble (see subclause 5.1.3).

[TS 36.321, clause 5.1.5]

Contention Resolution is based on either C-RNTI on PDCCH or UE Contention Resolution Identity on DL-SCH..

Once Msg3 is transmitted, the UE shall:

– start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission;

– regardless of the possible occurrence of a measurement gap, monitor the PDCCH until mac-ContentionResolutionTimer expires or is stopped;

– …

– if mac-ContentionResolutionTimer expires:

– discard the Temporary C-RNTI;

– consider the Contention Resolution not successful.

– if the Contention Resolution is considered not successful the UE shall:

– flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer;

– increment PREAMBLE_TRANSMISSION_COUNTER by 1;

– If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:

– indicate a Random Access problem to upper layers.

…

– proceed to the selection of a Random Access Resource (see subclause 5.1.2).

7.1.2.3.3 Test description

7.1.2.3.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– System information set using parameters as specified in Table 7.1.2.3.3.3-1.

UE:

None.

Preamble:

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

7.1.2.3.3.2 Test procedure sequence

Table 7.1.2.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity.	–	–	–	–
2	Check: Does the UE transmit preamble on PRACH using a preamble in group A defined in SIB2 (numberOfRA-Preambles and sizeOfRA-PreamblesGroupA)?	–>	PRACH Preamble	1	P
3	Check: Does the UE transmit preamble on PRACH using a preamble in group A defined in SIB2 (numberOfRA-Preambles and sizeOfRA-PreamblesGroupA)?	–>	PRACH Preamble	1	P
4	Check: Does the UE transmit preamble on PRACH using a preamble in group A defined in SIB2 (numberOfRA-Preambles and sizeOfRA-PreamblesGroupA)?	–>	PRACH Preamble	1	P
5	The SS transmits Random Access Response with RAPID corresponding to the transmitted Preamble in step 4, including T-CRNTI and not including Back off Indicator sub header.	<–	Random Access Response	–	–
6	The UE transmits an RRCConnectionRequest message.	–>	MAC PDU	–	–
7	Check: Does the UE transmit preamble on PRACH using a preamble belonging to group A?	–>	PRACH Preamble	2	P
8	Check: Does the UE continue to repeatedly transmit for 2s after step 2 a preamble belonging to group A? Note: 2s is the value of T300.	–>	PRACH Preamble	2, 3	P
9	The UE is in state Loopback Activated (state 4) according to [18] using parameters as specified in Table 7.1.2.3.3.3-2	–	–	–	–
10	The SS transmits a MAC PDU containing a PDCP SDU of size 320 bits[>208].	<–	MAC PDU	–	–
–	Exception: steps 11 and 12 are repeated dsr-TransMax times.	–	–	–	–
11	UE transmits a Scheduling Request.	–>	Scheduling Request	–	–
12	The SS does not allocate UL grant for the scheduling request in step 11.	–	–	–	–
13	Check: Does the UE transmit preamble on PRACH using a preamble in group B defined in SIB2 (numberOfRA-Preambles and sizeOfRA-PreamblesGroupA)?	–>	PRACH Preamble	4	P
14	Check: Does the UE transmit preamble on PRACH using a preamble in group B defined in SIB2 (numberOfRA-Preambles and sizeOfRA-PreamblesGroupA)?	–>	PRACH Preamble	4	P
15	Check: Does the UE transmit preamble on PRACH using a preamble in group B defined in SIB2 (numberOfRA-Preambles and sizeOfRA-PreamblesGroupA)?	–>	PRACH Preamble	4	P
16	The SS transmits Random Access Response with RAPID corresponding to the transmitted Preamble in step 15, including T-CRNTI and not including Back off Indicator sub header.	<–	Random Access Response	–	–
17	The UE transmits a MAC PDU with C-RNTI containing loop backed PDCP SDU	->	MAC PDU	–	–
18	The SS ignores the UL MAC PDU and does not allocate UL grant for the C-RNTI in step 17.	–	–	–	–
19	Check: Does the UE transmit preamble on PRACH using a preamble belonging to group B?	–>	PRACH Preamble	2	P
20	The SS transmits Random Access Response with RAPID corresponding to the transmitted Preamble in step 19	<–	Random Access Response	–	–
21	The UE transmits a MAC PDU containing loop backed PDCP SDU	–>	MAC PDU	–	–
22	SS sends PDCCH transmission for UE C-RNTI	–	–	–	–
Note: Size of RRCConnectionRequest message is 45 bits, octet aligned =48 bits. With 8 bits of MAC Header the minimum size of MAC PDU carrying RRCConnectionRequest is 56 bits.

7.1.2.3.3.3 Specific message contents

Table 7.1.2.3.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.3.3.2-1)

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
rach-Configuration SEQUENCE {
preambleInformation SEQUENCE {
numberOfRA-Preambles	n64
preamblesGroupAConfig := {SEQUENCE {
sizeOfRA-PreamblesGroupA	n28
messageSizeGroupA	b208
messagePowerOffsetGroupB	minusinfinity
}
}
}
}
ue-TimersAndConstants SEQUENCE{
t300	ms2000	T300
}
}
}
}

Table 7.1.2.3.3.3-2: RLC-Config-DRB-AM

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms200
}
}
}

7.1.2.3a Correct selection of RACH parameters/ Preamble selected by MAC itself/ Contention based random access procedure/ Enhanced coverage

7.1.2.3a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {

when { UE in enhanced coverage receives a Paging message and preambles contained in Random Access Preamble groups in preambleMappingInfoList for each CE level is indicated in SIB2 }

then { UE in enhanced coverage transmits correct preamble calculated based on firstPreamble and lastPreamble indicated in SIB2 }

}

(2)

with { UE in E-UTRA RRC_IDLE state and has transmitted initial Msg1}

ensure that {

when { SS sends numRepetitionPerPreambleAttempt in SIB2 }

then { UE in enhanced coverage transmits a preamble with the number of repetitions required for preamble transmission corresponding to the selected preamble group using the selected PRACH corresponding to the selected CE level, corresponding RA-RNTI, prach-ConfigIndex and preambleInitialReceivedTargetPower indicated in SIB2}

}

(3)

with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 }

ensure that {

when { SS does not respond before contention resolution timer expiry }

then { UE in enhanced coverage transmits a random access preamble using a preamble contained in Random Access Preamble groups in preambleMappingInfoList as used for the first transmission of Msg3 }

}

(4)

with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 }

ensure that {

when { SS does not respond before contention resolution timer expiry after more than maxNumPreambleAttemptCE transmissions from UE }

then { UE in enhanced coverage transmits a random access preamble using a preamble calculated based on firstPreamble and lastPreamble corresponding to the next enhanced coverage level indicated in SIB2 }

}

7.1.2.3a.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.1, 5.1.2, 5.1.3 and 5.1.5. Unless otherwise stated these are Rel-13 requirements.

[TS 36.321, clause 5.1.1]

The following information for related Serving Cell is assumed to be available before the procedure can be initiated for NB-IoT UEs, BL UEs or UEs in enhanced coverage:

– if the UE is a BL UE or a UE in enhanced coverage:

– the available set of PRACH resources associated with each enhanced coverage level supported in the Serving Cell for the transmission of the Random Access Preamble, prach-ConfigIndex.

– the groups of Random Access Preambles and the set of available Random Access Preambles in each group, preambleMappingInfo (SpCell only).

The preambles that are contained in Random Access Preambles groups for each enhanced coverage level, if it exists, are calculated from the parameters firstPreamble and lastPreamble.

…

– the criteria to select PRACH resources based on RSRP measurement per enhanced coverage level supported in the Serving Cell rsrp-ThresholdsPrachInfoList.

– the maximum number of preamble transmission attempts per enhanced coverage level supported in the Serving Cell maxNumPreambleAttemptCE.

– the number of repetitions required for preamble transmission per attempt for each enhanced coverage level supported in the Serving Cell numRepetitionPerPreambleAttempt.

– the configured UE transmitted power of the Serving Cell performing the Random Access Procedure, P_{CMAX, c} [10].

– the RA response window size ra-ResponseWindowSize and the Contention Resolution Timer mac-ContentionResolutionTimer (SpCell only) per enhanced coverage level supported in the Serving Cell.

– the power-ramping factor powerRampingStep.

– the maximum number of preamble transmission preambleTransMax-CE.

– the initial preamble power preambleInitialReceivedTargetPower.

– the preamble format based offset DELTA_PREAMBLE (see subclause 7.6). For NB-IoT the DELTA_PREAMBLE is set to 0.

– if sizeOfRA-PreamblesGroupA is not equal to numberOfRA-Preambles, then Random Access Preambles group B exists for all enhanced coverage levels and is calculated as above.

[TS 36.321, clause 5.1.2]

The Random Access Resource selection procedure shall be performed as follows:

– If, except for NB-IoT, ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000:

– the Random Access Preamble and the PRACH Mask Index are those explicitly signalled;

…

– else the Random Access Preamble shall be selected by the MAC entity as follows:

– If Msg3 has not yet been transmitted, the MAC entity shall, for NB-IoT UEs, BL UEs or UEs in enhanced coverage:

– select the Random Access Preambles group and the PRACH resource corresponding to the selected enhanced coverage level and, in case of NB-IoT, additionally corresponding to the support for multi-tone Msg3 transmission;

…

– else, if Msg3 is being retransmitted, the MAC entity shall:

– select the same group of Random Access Preambles as was used for the preamble transmission attempt corresponding to the first transmission of Msg3.

– randomly select a Random Access Preamble within the selected group. The random function shall be such that each of the allowed selections can be chosen with equal probability;

– except for NB-IoT, set PRACH Mask Index to 0.

– determine the next available subframe containing PRACH permitted by the restrictions given by the prach-ConfigIndex (except for NB-IoT), the PRACH Mask Index (except for NB-IoT, see subclause 7.3), physical layer timing requirements [2] and in case of NB-IoT selected enhanced coverage level and the support for multi-tone Msg3 transmission (a MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH subframe);

– if the transmission mode is TDD and the PRACH Mask Index is equal to zero:

– if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC):

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe.

– else:

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe and the next two consecutive subframes.

– else:

– determine a PRACH within the determined subframe in accordance with the requirements of the PRACH Mask Index.

– for NB-IoT UEs, BL UEs or UEs in enhanced coverage, select the ra-ResponseWindowSize and mac-ContentionResolutionTimer corresponding to the selected enhanced coverage level and PRACH.

[TS 36.321, clause 5.1.3]

The random-access procedure shall be performed as follows:

– set PREAMBLE_RECEIVED_TARGET_POWER to preambleInitialReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep;

– if the UE is a BL UE or a UE in enhanced coverage:

– the PREAMBLE_RECEIVED_TARGET_POWER is set to:
PREAMBLE_RECEIVED_TARGET_POWER – 10 * log10(numRepetitionPerPreambleAttempt);

…

– if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage:

– instruct the physical layer to transmit a preamble with the number of repetitions required for preamble transmission corresponding to the selected preamble group (i.e., numRepetitionPerPreambleAttempt) using the selected PRACH corresponding to the selected enhanced coverage level, corresponding RA-RNTI, preamble index or for NB-IoT subcarrier index, and PREAMBLE_RECEIVED_TARGET_POWER.

– else:

– instruct the physical layer to transmit a preamble using the selected PRACH, corresponding RA-RNTI, preamble index and PREAMBLE_RECEIVED_TARGET_POWER.

[TS 36.321, clause 5.1.4]

…

– if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage:

– if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax-CE + 1:

– if the Random Access Preamble is transmitted on the SpCell:

– indicate a Random Access problem to upper layers;

– if NB-IoT:

– consider the Random Access procedure unsuccessfully completed;

…

– if in this Random Access procedure, the Random Access Preamble was selected by MAC:

– based on the backoff parameter, select a random backoff time according to a uniform distribution between 0 and the Backoff Parameter Value;

– delay the subsequent Random Access transmission by the backoff time;

…

– if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage:

– increment PREAMBLE_TRANSMISSION_COUNTER_CE by 1;

– if PREAMBLE_TRANSMISSION_COUNTER_CE = maxNumPreambleAttemptCE for the corresponding enhanced coverage level + 1:

– reset PREAMBLE_TRANSMISSION_COUNTER_CE;

– consider to be in the next enhanced coverage level, if it is supported by the Serving Cell and the UE, otherwise stay in the current enhanced coverage level;

– for a BL UE or a UE in enhanced coverage, select the Random Access Preambles group and the PRACH resource corresponding to the selected enhanced coverage level;- if the UE is an NB-IoT UE:

– if the Random Access Procedure was initiated by a PDCCH order:

– randomly select one of the PRACH resources corresponding to the selected enhanced coverage level according to the configured probability distribution;

…

– consider the selected PRACH resource as explicitly signalled;

– proceed to the selection of a Random Access Resource (see subclause 5.1.2).

[TS 36.321, clause 5.1.5]

Contention Resolution is based on either C-RNTI on PDCCH of the SpCell or UE Contention Resolution Identity on DL-SCH. If the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage, the MAC entity shall use the mac-ContentionResolutionTimer for the corresponding enhanced coverage level if it exists.

Once Msg3 is transmitted, the MAC entity shall:

– start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission;

– regardless of the possible occurrence of a measurement gap or Sidelink Discovery Gap for Reception, monitor the PDCCH until mac-ContentionResolutionTimer expires or is stopped;

…

– if mac-ContentionResolutionTimer expires:

– discard the Temporary C-RNTI;

– consider the Contention Resolution not successful.

– if the Contention Resolution is considered not successful the MAC entity shall:

…

– if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage:

– if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax-CE + 1:

– indicate a Random Access problem to upper layers.

– if NB-IoT:

– consider the Random Access procedure unsuccessfully completed;

– else:

– if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:

– indicate a Random Access problem to upper layers.

– based on the backoff parameter, select a random backoff time according to a uniform distribution between 0 and the Backoff Parameter Value;

– delay the subsequent Random Access transmission by the backoff time;

– proceed to the selection of a Random Access Resource

7.1.2.3a.3 Test description

7.1.2.3a.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– System information set using parameters as specified in Table 7.1.2.3a.3.4-1.

UE:

None.

Preamble:

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

7.1.2.3a.3.2 Test procedure sequence

Table 7.1.2.3a.3.2-1 illustrates the downlink power levels to be applied for the cell at various time instance of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1", "T2", and "T3" are to be applied subsequently. The exact instance on which these values shall be applied are described in the texts in this clause.

Table 7.1.2.3a.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-70	The power level value is such that UE satisfies CE level 0
T1	Cell-specific RS EPRE	dBm/15kHz	-79	The power level value is such that UE satisfies CE level 1
T2	Cell-specific RS EPRE	dBm/15kHz	-88	The power level value is such that UE satisfies CE level 2
T3	Cell-specific RS EPRE	dBm/15kHz	-96	The power level value is such that UE satisfies CE level 3

Table 7.1.2.3a.3.3-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
	Exception: if CE MODE B, Steps 1-9 are repeated once each for time instant T0 to T3 specified in table 7.1.2.3a.3.2-1, else Steps 1-9 are repeated once each for time instant T0 and T1 specified in table 7.1.2.3a.3.2-1.	–	–	–	–
1	The SS transmits a Paging message including a matched identity.	<–	Paging	–	–
	Exception: For each PRACH preamble attempt in step2, step3 and step4 the Preamble transmission is repeated for numRepetitionPerPreambleAttempt times configured for corresponding CE level.	–	–	–	–
2	Check: Does the UE transmit a preamble on PRACH, calculated based on parameters firstPreamble-r13 and lastPreamble-r13 for corresponding CE level defined in SIB2?	–>	PRACH Preamble	1, 2	P
3	Check: Does the UE transmit a preamble on PRACH, calculated based on parameters firstPreamble-r13 and lastPreamble-r13 for corresponding CE level defined in SIB2?	–>	PRACH Preamble	1, 2	P
4	Check: Does the UE transmit a preamble on PRACH, calculated based on parameters firstPreamble-r13 and lastPreamble-r13 for corresponding CE level defined in SIB2?	–>	PRACH Preamble	1,2	P
5	The SS transmits Random Access Response with RAPID corresponding to the transmitted Preamble in step 4, including T-CRNTI and not including backoff Indicator sub-header.	<–	Random Access Response	–	–
6	The UE transmits an RRCConnectionRequest message.	–>	MAC PDU	–	–
	Exception: For each PRACH preamble attempt in step7 and step 7A the preamble transmission is repeated for numRepetitionPerPreambleAttempt times configured for corresponding CE level.	–	–	–	–
7	Check: Does the UE transmit a preamble on PRACH using a preamble belonging to same CE level as of step 2?	–>	PRACH Preamble	2, 3	P
7A	Check: Does the UE transmit a preamble on PRACH using a preamble belonging to same CE level as of step 2?	–>	PRACH Preamble	1, 2	P
7B	Check: Does the UE transmit a preamble on PRACH, calculated based on parameters firstPreamble-r13 and lastPreamble-r13 corresponding to the next CE level defined in SIB2?	–>	PRACH Preamble	2, 4	P
8	The SS waits for the UE to repeatedly transmit for preambleTransMax-CE + 1 further PRACH preambles until 2s after step 2 and ignores them. Note: 2s is the value of T300.	–	–	–	–
–	At the end of this test procedure sequence, the UE is in end state E-UTRA idle (E1) according to TS 36.508 [18].	–	–	–	–

7.1.2.3a.3.4 Specific message contents

Table 7.1.2.3a.3.4-1: SystemInformationBlockType2 (all steps, table 7.1.2.3a.3.3-1)

Derivation Path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
RadioResourceConfigCommonSIB-DEFAULT ::= SEQUENCE {
PRACH-ConfigSIB-v1310-DEFAULT ::= SEQUENCE {
rsrp-ThresholdsPrachInfoList-r13 SEQUENCE (SIZE(1..3)) OF {			CEmodeA
RSRP-Range[1]	64	-76 dBm
}
rsrp-ThresholdsPrachInfoList-r13 SEQUENCE (SIZE(1..3)) OF {			CEmodeB
RSRP-Range[1]	64	-76 dBm
RSRP-Range[2]	56	-84 dBm
RSRP-Range[3]	47	-93 dBm
}
}
prach-ParametersListCE-r13 SEQUENCE (SIZE(1..maxCE-Level-r13)) OF SEQUENCE {			CEmodeA, CEmodeB
prach-StartingSubframe-r13[2]	sf16
numRepetitionPerPreambleAttempt-r13[2]	n16
}
ue-TimersAndConstants SEQUENCE {
t300	ms2000	T300
}
}

7.1.2.3b Correct selection of RACH parameters / Preamble selected by MAC itself / Contention based random access procedure for high speed scenario

7.1.2.3b.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state and camp on a cell identified in the high speed train area}

ensure that {

when { SS sends a Paging message to the UE and MAC PDU Size carrying CCCH PDU is less than messageSizeGroupA }

then { UE transmits a random access preamble using a preamble in group A of random access preambles indicated in SIB2 }

}

(2)

with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 to a cell identified in the high speed train area }

ensure that {

when { SS does not respond before contention resolution timer expiry }

then { UE transmits a random access preamble using a preamble in the same group of random access preambles as used for the first transmission of Msg3 }

}

(3)

with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 to a cell identified in the high speed train area }

ensure that {

when { SS does not respond before contention resolution timer expiry after more than preambleTransMax transmissions from UE }

then { UE transmits a random access preamble using a preamble in the same group of random access preambles as used for the first transmission of Msg3 }

}

(4)

with { UE in E-UTRA RRC_IDLE state and camp on a cell identified in the high speed train area }

ensure that {

when { UE has data available for transmission and the MAC PDU Size carrying this data is greater than messageSizeGroupA }

then { UE transmits a random access preamble using a preamble in group B of random access preambles indicated in SIB2 }

}

7.1.2.3b.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.2 and 5.1.5.

[TS 36.321, clause 5.1.2]

The Random Access Resource selection procedure shall be performed as follows:

– If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000:

…

– else the Random Access Preamble shall be selected by the UE as follows:

– If Msg3 has not yet been transmitted, the UE shall:

– select the Random Access Preambles group B;

– else:

– select the Random Access Preambles group A.

– else, if Msg3 is being retransmitted, the UE shall, the UE shall:

– select the same group of Random Access Preambles as was used for the preamble transmission attempt corresponding to the first transmission of Msg3.

– randomly select a Random Access Preamble within the selected group. The random function shall be such that each of the allowed selections can be chosen with equal probability;

– set PRACH Mask Index to 0.

– if the transmission mode is TDD and the PRACH Mask Index is equal to zero:

– if ra-PreambleIndex was explicitly signalled and the signalled random access preamble ID was not 000000 (i.e., not selected by MAC):

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe.

– else:

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe and the next two consecutive subframes.

– else:

– determine a PRACH within the determined subframe in accordance with the requirements of the PRACH Mask Index.

– proceed to the transmission of the Random Access Preamble (see subclause 5.1.3).

[TS 36.321, clause 5.1.5]

Contention Resolution is based on either C-RNTI on PDCCH or UE Contention Resolution Identity on DL-SCH..

Once Msg3 is transmitted, the UE shall:

– start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission;

– regardless of the possible occurrence of a measurement gap, monitor the PDCCH until mac-ContentionResolutionTimer expires or is stopped;

– …

– if mac-ContentionResolutionTimer expires:

– discard the Temporary C-RNTI;

– consider the Contention Resolution not successful.

– if the Contention Resolution is considered not successful the UE shall:

– flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer;

– increment PREAMBLE_TRANSMISSION_COUNTER by 1;

– If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:

– indicate a Random Access problem to upper layers.

…

– proceed to the selection of a Random Access Resource (see subclause 5.1.2).

[TS 36.211, clause 5.7.1]

….

…

[TS 36.211, clause 5.7.2 Preamble sequence generation]

The root Zadoff-Chu sequence is defined by

where the cyclic shift is given by

…

Table 5.7.2-2: for preamble generation (preamble formats 0-3)

zeroCorrelationZoneConfig, zeroCorrelationZoneConfigHighSpeed	value
	Unrestricted set	Restricted set type A	Restricted set type B
0	0	15	15
1	13	18	18
2	15	22	22
3	18	26	26
4	22	32	32
5	26	38	38
6	32	46	46
7	38	55	55
8	46	68	68
9	59	82	82
10	76	100	100
11	93	128	118
12	119	158	137
13	167	202	–
14	279	237	–
15	419	–	–

7.1.2.3b.3 Test description

7.1.2.3b.3.1 Pre-test conditions

See clause 7.1.2.3.3.1

7.1.2.3b.3.2 Test procedure sequence

See clause 7.1.2.3b.3.2

7.1.2.3b.3.3 Specific message contents

Table 7.1.2.3b.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.3b.3.2-1)

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
rach-Configuration SEQUENCE {
preambleInformation SEQUENCE {
numberOfRA-Preambles	n64
preamblesGroupAConfig := {SEQUENCE {
sizeOfRA-PreamblesGroupA	n28
messageSizeGroupA	b208
messagePowerOffsetGroupB	minusinfinity
}
}
highSpeedConfigSCell-r14	HighSpeedConfigSCell-r14-DEFAULT
prach-Config-v1430	PRACH-Config-v1430-DEFAULT
}
}
ue-TimersAndConstants SEQUENCE{
t300	ms2000	T300
}
}
}
}

Table 7.1.2.3b.3.3-2: RLC-Config-DRB-AM

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms200
}
}
}

7.1.2.4 Random access procedure / Successful

7.1.2.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {

when { The SS pages the UE with a matching identity }

then { UE transmits a random access preamble in the next available Random Access occasion }

}

(2)

with { UE in E-UTRA RRC_IDLE state after transmission of a PRACH preamble }

ensure that {

when { SS does not answer with a matching Random Access Response within ra-ResponseWindowSize }

then { UE retransmits a PRACH preamble }

}

(3)

with { SS transmits Random Access Response and UE send msg3 }

ensure that {

when { SS ignores the RRCConnectionRequest and does not send any Response }

then { UE select available PRACH resource to retransmits a PRACH preamble according to the timing requirement }

}

7.1.2.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.2, 5.1.3 & 5.1.4.

[TS 36.321, clause 5.1.2]

The Random Access Resource selection procedure shall be performed as follows:

– If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000:

– the Random Access Preamble and the PRACH Mask Index are those explicitly signalled.

– else the Random Access Preamble shall be selected by the UE as follows:

– If Msg3 has not yet been transmitted, the UE shall:

– if Random Access Preambles group B exists and if the potential message size (data available for transmission plus MAC header and, where required, MAC control elements) is greater than messageSizeGroupA and if the pathloss is less than P_CMAX – preambleInitialReceivedTargetPower – deltaPreambleMsg3 – messagePowerOffsetGroupB, then:

– select the Random Access Preambles group B;

– else:

– select the Random Access Preambles group A.

– else, if Msg3 is being retransmitted, the UE shall:

– select the same group of Random Access Preambles as was used for the preamble transmission attempt corresponding to the first transmission of Msg3.

– randomly select a Random Access Preamble within the selected group. The random function shall be such that each of the allowed selections can be chosen with equal probability;

– set PRACH Mask Index to 0.

– determine the next available subframe containing PRACH permitted by the restrictions given by the prach-ConfigurationIndex and the PRACH Mask Index (see subclause 7.3) (a UE may take into account the possible occurrence of measurement gaps when determining the next available PRACH subframe);

– if the transmission mode is TDD and the PRACH Mask Index is equal to zero:

– if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC):

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe.

– else:

– randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe and the next two consecutive subframes.

– else:

– determine a PRACH within the determined subframe in accordance with the requirements of the PRACH Mask Index.

– proceed to the transmission of the Random Access Preamble (see subclause 5.1.3).

[TS 36.321, clause 5.1.3]

The random-access procedure shall be performed as follows:

– set PREAMBLE_RECEIVED_TARGET_POWER to preambleInitialReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep;]

– instruct the physical layer to transmit a preamble using the selected PRACH, corresponding RA-RNTI, preamble index and PREAMBLE_RECEIVED_TARGET_POWER.

[TS 36.321, clause 5.1.4]

Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the UE shall monitor the PDCCH for Random Access Response(s) identified by the RA-RNTI defined below, in the RA Response window which starts at the subframe that contains the end of the preamble transmission [7] plus three subframes and has length ra-ResponseWindowSize subframes The RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as:

RA-RNTI= t1 + _id+10*f_id

– if the Random Access Response contains a Back off Indicator sub header:

– set the back off parameter value in the UE as indicated by the BI field of the Back off Indicator sub header and Table 7.2-1.

– else, set the back off parameter value in the UE to 0 ms.

– if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble (see subclause 5.1.3), the UE shall:

– consider this Random Access Response reception successful;

– process the received Timing Advance Command (see subclause 5.2);

– indicate thepreambleInitialReceivedTargetPower and the amount of power ramping applied to the latest preamble transmission to lower layers (i.e., (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep);

– process the received UL grant value and indicate it to the lower layers;

– if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC):

– consider the Random Access procedure successfully completed.

– else, if the Random Access Preamble was selected by UE MAC:

– set the Temporary C-RNTI to the value received in the Random Access Response message no later than at the time of the first transmission corresponding to the UL grant provided in the Random Access Response message;

– if this is the first successfully received Random Access Response within this Random Access procedure:

– if the transmission is not being made for the CCCH logical channel, indicate to the Multiplexing and assembly entity to include a C-RNTI MAC control element in the subsequent uplink transmission;

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity and store it in the Msg3 buffer.

NOTE: When an uplink transmission is required, e.g., for contention resolution, the eNB should not provide a grant smaller than 56 bits in the Random Access Response.

NOTE: If within a Random Access procedure, an uplink grant provided in the Random Access Response for the same group of Random Access Preambles has a different size than the first uplink grant allocated during that Random Access procedure, the UE behaviour is not defined.

– increment PREAMBLE_TRANSMISSION_COUNTER by 1;

– If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:

– indicate a Random Access problem to upper layers.

…

– proceed to the selection of a Random Access Resource (see subclause 5.1.2).

TS 36.321, clause 6.1.5

A MAC PDU consists of a MAC header and one or more MAC Random Access Responses (MAC RAR) and optionally padding as described in figure 6.1.5-4.

The MAC header is of variable size.

A MAC PDU header consists of one or more MAC PDU sub-headers; each subheader corresponding to a MAC RAR except for the Backoff Indicator sub-header. If included, the Back off Indicator sub-header is only included once and is the first sub-header included within the MAC PDU header.

A MAC RAR consists of the four fields R/Timing Advance Command/UL Grant/Temporary C-RNTI (as described in figure 6.1.5-3).

Padding may occur after the last MAC RAR. Presence and length of padding is implicit based on TB size, size of MAC header and number of RARs.

Figure 6.1.5-3: MAC RAR

Figure 6.1.5-4: Example of MAC PDU consisting of a MAC header and MAC RARs

[TS 36.213, clause 6.1]

For the L1 random access procedure, UE’s uplink transmission timing after a random access preamble transmission is as follows.

1. If a PDCCH with associated RA-RNTI is detected in subframe n, and the corresponding DL-SCH transport block contains a response to the transmitted preamble sequence, the UE shall, according to the information in the response, transmit an UL-SCH transport block in the first subframe , , if the UL delay field in section 6.2 is set to zero. The UE shall postpone the PUSCH transmission to the next available UL subframe if the field is set to 1.

[TS 36.213, clause 6.2]

The higher layers indicate the 20-bit UL Grant to the physical layer, as defined in [8]. This is referred to the Random Access Response Grant in the physical layer. The content of these 20 bits starting with the MSB and ending with the LSB are as follows:

– Hopping flag – 1 bit

– Fixed size resource block assignment – 10 bits

– Truncated modulation and coding scheme – 4 bits

– TPC command for scheduled PUSCH – 3 bits

– UL delay – 1 bit

– CQI request – 1 bit

…

The UL delay applies for both TDD and FDD and this field can be set to 0 or 1 to indicate whether the delay of PUSCH is introduced as shown in section 6.1.1.

7.1.2.4.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information are set according to table 7.1.2.4.3.3-1

UE:

None.

Preamble:

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

7.1.2.4.3.2 Test procedure sequence

Table 7.1.2.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity.	–	–	–	–
2	Check: does the UE transmit a preamble on PRACH, in frame number X, subframe number 2, 5, 8 (1, 4, 7 for CAT-M1 UEs) (FDD)/2,3,8(TDD)?	–>	PRACH Preamble	1	P
3	Check: does the UE transmit a preamble on PRACH, in frame number X+1 or X+2 (X+2 or X+3 for CAT-M1 UEs), subframe number 2, 5, 8 (1, 4, 7 for CAT-M1 UEs) (FDD)/ 2,3,8 (TDD)?	–>	PRACH Preamble	1,2	P
4	Check: does the UE transmit a preamble on PRACH, in frame number X+2, X+3 or X+4 (X+5 or X+6 for CAT-M1 UEs), subframe number 2, 5, 8 (1, 4, 7 for CAT-M1 UEs) (FDD)/ 2,3,8 (TDD)?	–>	PRACH Preamble	1,2	P
5	The SS transmits a Random Access Response with not-matching RA-Id, including T-CRNTI and not including Back off Indicator sub header.	<–	Random Access Response	–	–
6	Check: does the UE transmit a preamble on PRACH in frame number X+4, X+5 or X+6 (X+8 or X+9 or X+10 for CAT-M1 UEs), subframe number 2, 5, 8 (1, 4, 7 for CAT-M1 UEs) (FDD)/ 2,3,8 (TDD)?	–>	PRACH Preamble	1,2	P
7	The SS transmits Random Access Response with RAPID corresponding to the transmitted Preamble in step 6, including T-CRNTI and UL grant and not including Back off Indicator sub header. The UL delay bit in the UL grant field is set to 0	<–	Random Access Response	–	–
8	The UE transmits an RRCConnectionRequest message.	–>	–	–	–
9	The SS ignores the RRCConnectionRequest message and does not send any response.	–	–	–	–
10	UE waits for mac-ContentResolutionTimer expire.	–	–	–	–
11	Check: does the UE transmit preamble on PRACH using a preamble in subframe number 2,5,8 for FDD and subframe number 2,3 or 8 for TDD?	–>	PRACH Preamble	3	P
12	The SS transmits Random Access Response with RAPID corresponding to the transmitted Preamble in step 11, including T-CRNTI and not including Back off Indicator sub header.	<–	Random Access Response	–	–
13	The UE transmits an RRCConnectionRequest message.	–>	–	–	–
14	The SS Transmits a valid MAC PDU containing RRCConnectionSetup, and including ‘UE Contention Resolution Identity’ MAC control element with matching ‘Contention Resolution Identity’	<–	MAC PDU	–	–
15	The UE transmits an RRCConnectionSetupComplete message.	–>	–	–	–
16-19	Steps 6 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.	–	–	–	–

7.1.2.4.3.3 Specific message contents

Table 7.1.2.4.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.4.3.2-1)

Derivation path: 36.508 table 4.4.3.3.-1
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
rach-Configuration SEQUENCE {
ra-SupervisionInformation SEQUENCE {
mac-ContentionResolutionTimer	Sf48	Timer for contention resolution is 48 subframes
ra-ResponseWindowSize	sf10
}
}
prach-Configuration SEQUENCE {
prach-ConfigInfo SEQUENCE {
prach-ConfigurationIndex	10 (9 for CAT-M1 UEs)	As per table 5.7.1-2 of 36.211, this results in PRACH preamble transmission start in any frame numbers and sub-frame number 2, 5, 8 (1, 4, 7 for CAT-M1 UEs)	FDD
prach-ConfigurationIndex	9	As per table 5.7.1-4 of 36.211, this results in PRACH preamble transmission with frequency resource index=0; occurring in any radio frames; resource is located in sub frame number 2,3 ,8 Note 1	TDD
}
}
}
}
Note 1: 36.508, Table 4.4.3.2-3 specifies tdd-Configuration-> subframeAssignment as sa1.

Table 7.1.2.4.3.3-2: SystemInformationBlockType2 (all steps, table 7.1.2.4.3.2-1) when UE under test is CAT M1

Derivation path: 36.508 table 4.4.3.3.-1
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
rach-Configuration SEQUENCE {
RACH-CE-LevelInfoList-r13 SEQUENCE (SIZE (1..maxCE-Level-r13)) OF RACH-CE-LevelInfo-r13 {
RACH-CE-LevelInfo-r13[1] SEQUENCE {
ra-ResponseWindowSize-r13	sf20
mac-ContentionResolutionTimer-r13	sf80
rar-HoppingConfig-r13	off
}
}
}
PRACH-ConfigSIB-v1310-DEFAULT ::= SEQUENCE {
prach-ParametersListCE-r13 SEQUENCE {
prach-ConfigIndex-r13[1]	10 (9 for CAT-M1 UEs)	As per table 5.7.1-2 of 36.211, this results in PRACH preamble transmission start in any frame numbers and sub-frame number 2, 5, 8 (1, 4, 7 for CAT-M1 UEs)	FDD
prach-ConfigIndex-r13[1]	9	As per table 5.7.1-4 of 36.211, this results in PRACH preamble transmission with frequency resource index=0; occurring in any radio frames; resource is located in sub frame number 2,3 ,8 Note 1	TDD
}
}
}
}
Note 1: 36.508, Table 4.4.3.2-3 specifies tdd-Configuration-> subframeAssignment as sa1.

7.1.2.5 Random access procedure / MAC PDU containing multiple RARs

7.1.2.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state and transmitted PRACH preamble }

ensure that {

when { UE receives during TTI window [RA_WINDOW_BEGIN—RA_WINDOW_END] MAC PDU containing multiple RAR’s but none of the subheaders contains a RAPID corresponding to the UE }

then { UE transmits a random access preamble in the next available Random Access occasion }

}

(2)

with { UE in E-UTRA RRC_IDLE state and transmitted PRACH preamble }

ensure that {

when { UE receives during TTI window [RA_WINDOW_BEGIN—RA_WINDOW_END] MAC PDU containing multiple RAR’s and one of the subheaders contains a RAPID corresponding to the UE }

then { UE transmits MAC PDU containing RRCConnectionRequest }

}

7.1.2.5.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.3 and 5.1.4.

[TS 36.321, clause 5.1.3]

The random-access procedure shall be performed as follows:

– set PREAMBLE_RECEIVED_TARGET_POWER to preambleInitialReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep;]

– instruct the physical layer to transmit a preamble using the selected PRACH resource, corresponding RA-RNTI, preamble index and PREAMBLE_RECEIVED_TARGET_POWER.

[TS 36.321, clause 5.1.4]

Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the UE shall monitor the PDCCH for Random Access Response(s) identified by the RA-RNTI defined below, in the RA Response window which starts at the subframe that contains the end of the preamble transmission [7] plus three subframes and has length ra-ResponseWindowSize subframes. The RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as: