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

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]

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.

[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]

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 the 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.

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 PCMAX –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, PCMAX, 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 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 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:

– 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:

– 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 PCMAX –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).

[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.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 PCMAXpreambleInitialReceivedTargetPowerdeltaPreambleMsg3 – 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

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 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.

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.

– 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:

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 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 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 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.

– 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.

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.

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

7.1.2.5.3 Test description

7.1.2.5.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].

7.1.2.5.3.2 Test procedure sequence

Table 7.1.2.5.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?

–>

PRACH Preamble

1

P

3

The SS transmits a MAC PDU addressed to UE RA-RNTI, containing multiple RAR’s but none of the MAC sub headers contains a matching RAPID

<–

Random Access Response

EXCEPTION: In parallel with step 4, parallel behaviour defined in table 7.1.2.5.3.2-2 is executed

4

Check: Does the UE re-transmit a preamble on PRACH?

–>

PRACH Preamble

1

P

5

The SS transmits a MAC PDU addressed to UE RA-RNTI, containing multiple RAR’s one of the MAC sub headers contains a matching RAPID

<–

Random Access Response

6

Check: Does the UE transmit a MAC PDU containing RRCConnectionRequest message?

–>

MAC PDU (RRCConnectionRequest)

2

P

7

The SS sends a MAC PDU containing matching Contention Resolution Identity MAC control element

<–

MAC Control PDU

7A

SS transmit RRCConnectionSetup message

<–

8

The UE transmit RRCConnectionSetupComplete message including SERVICE REQUEST message.

–>

9-12

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.

Table 7.1.2.5.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE transmit an RRCConnectionRequest message.

–>

MAC PDU (RRCConnectionRequest)

1

F

7.1.2.5.3.3 Specific message contents

None.

7.1.2.6 Maintenance of uplink time alignment

7.1.2.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state and having initiated a random access procedure }

ensure that {

when { The SS transmits a Timing Advance Command in a Random Access Response message }

then { the UE applies the received Timing Advance value in the next transmitted MAC PDU}

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { Timing Advanced Command MAC control element is received and UE has pending data during the period the timeAlignmentTimer is running }

then { UE does not send any Random Access Preamble, but Scheduling Requests to request transmission of data while timeAlignmentTimer is running }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when{ timeAlignmentTimer has expired or is not running and UL transmission is required}

then { UE triggers a RA Procedure }

}

7.1.2.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.2.

[TS 36.321 clause 5.2]

The UE has a configurable timer timeAlignmentTimer which is used to control how long the UE is considered uplink time aligned.

The UE shall:

– when a Timing Advance Command MAC control element is received:

– apply the Timing Advance Command;

– start or restart timeAlignmentTimer.

– when a Timing Advance Command is received in a Random Access Response message:

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

– apply the Timing Advance Command;

– start or restart timeAlignmentTimer.

– else, if the timeAlignmentTimer is not running:

– apply the Timing Advance Command;

– start timeAlignmentTimer;

– when the contention resolution is considered not successful as described in subclause 5.1.5, stop timeAlignmentTimer.

– else:

– ignore the received Timing Advance Command.

– when timeAlignmentTimer expires:

– flush all HARQ buffers;

– notify RRC to release PUCCH/SRS;

– clear any configured downlink assignments and uplink grants.

7.1.2.6.3 Test description

7.1.2.6.3.1 Pre-test condition

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The generic procedure to get UE in state Registered, Idle mode, UE Test Mode Activated (State 2a) according to TS 36.508 clause 4.5 is executed.

7.1.2.6.3.2 Test procedure sequence

Table 7.1.2.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS pages the UE

<–

2

SS respond to UE Random Access request by a Random Access Response with TA field within message set to 600(FDD) or 160(TDD) (Note 2).

<–

MAC PDU(Random Access Response (TA=600))

3

Check: Does UE send an RRCConnectionRequest message in the first scheduled UL transmission using the Timing Advance value sent by the SS in step 2?

–>

MAC PDU (RRCConnectionRequest)

1

P

4

The SS transmits a valid MAC PDU containing “UE Contention Resolution Identity” MAC control element with matching “Contention Resolution Identity” and RA Procedure considered a success.

<–

MAC PDU (UE Contention Resolution Identity)

5

The SS sends an RRCConnectionSetup message.

<–

MAC PDU

6

Check: Does the UE transmit an RRCConnectionSetupComplete?

–>

MAC PDU (RRCConnectionSetupComplete)

1

P

7

The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed with UL SDU size set to ‘0’ (no data returned in uplink) using parameters as specified in Table 7.1.2.6.3.3-1

8

SS transmits Timing Advance command. SS does not send any subsequent alignments.

<–

MAC PDU (Timing Advance Command MAC Control Element)

9

After 600ms (0.8 * timeAlignmentTimer) SS sends a MAC PDU containing a RLC PDU with SN=0 and poll bit set to trigger UE to transmit a status report in uplink. SS does not respond to any scheduling requests or Random Access Preambles from the UE.

<–

MAC PDU

10

Check: For 0.2* timeAlignmentTimer does UE transmit Scheduling Requests, but no Random Access Preamble message?

(Note 1)

–>

SR

2

P

11

Void

12

Check: Does the UE transmit a Random Access Preamble?

–>

Random Access Preamble

3

P

13

SS responds with a valid Random Access Response

<–

MAC PDU (Random Access Response (Temporary C-RNTI))

14

Check: Does the UE transmit a MAC PDU with C-RNTI containing RLC STATUS PDU for the acknowledgement of the DL Data with the Temporary C-RNTI set to the value received in the Random Access Response message??

–>

MAC PDU(RLC STATUS PDU (ACK_SN =1))

3

P

15

The SS Transmits a PDCCH transmission addressed to the C-RNTI stored in the UE and contains an UL grant for a new transmission

<–

Note 1 A conformant UE correctly applies Timing Advance Command MAC Control and restarts timeAlignmentTimer, causing the uplink to stay in sync for a period equal to the received Time Alignment Value.

Note 2 For FDD, TA value of 600 has been chosen arbitrarily in the middle of the range 0 to 1282 and corresponds to 0.3125 ms (timing advance in ms = 1000 x NTA x where NTA = TA ×16 and seconds according to TS 36.213 and TS 36.211).
For TDD, TA value of 160 has been chosen and corresponds to 0.1036 ms (timing advance in ms = 1000 x (N_TA + N_TA_offset) x Ts where N_TA = TA x 16, N_TA_offset = 624Ts, and Ts = 1/(15000 x 2048) seconds according to TS 36.213 and TS 36.211).

7.1.2.6.3.3 Specific Message Contents

Table 7.1.2.6.3.3-1: SchedulingRequest-Configuration (RRCConnectionReconfiguration, step 7 table 7.1.2.6.3.2-1)

Derivation Path: 36.508 clause 4.6.3-20

Information Element

Value/remark

Comment

Condition

SchedulingRequest-Configuration ::= CHOICE {

setup SEQUENCE {

dsr-TransMax

n64

Max value allowed

}

}

7.1.2.7 MAC contention resolution / Temporary C-RNTI

7.1.2.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state and after transmitting an RRCConnectionRequest message }

ensure that {

when { SS does not send any MAC PDU including ‘UE Contention Resolution Identity’ MAC control element before contention resolution timer expires }

then { UE re-transmits RRCConnectionRequest }

}

(2)

with { UE in E-UTRA RRC_IDLE state and after transmitting an RRCConnectionRequest message }

ensure that {

when { SS transmits a valid MAC PDU containing RRCConnectionSetup, but not including ‘UE Contention Resolution Identity’ MAC control element }

then { UE re-transmits RRCConnectionRequest }

}

(3)

with { UE in E-UTRA RRC_IDLE state and after transmitting an RRCConnectionRequest message }

ensure that {

when { SS transmits a valid MAC PDU containing RRCConnectionSetup, including ‘UE Contention Resolution Identity’ MAC control element but with un-matched ‘Contention Resolution Identity’ }

then { UE re-transmits RRCConnectionRequest }

}

(4)

with { UE in E-UTRA RRC_IDLE state and after transmitting an RRCConnectionRequest message }

ensure that {

when { SS transmits a valid MAC PDU containing a RRCConnectionSetup, including ‘UE Contention Resolution Identity’ MAC control element and matching ‘Contention Resolution Identity’ }

then { UE transmits an RRCConnectionSetupComplete message }

}

7.1.2.7.2 Conformance requirements

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

[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 notification of a reception of a PDCCH transmission is received from lower layers, the UE shall:

– else if the CCCH SDU was included in Msg3 and the PDCCH transmission is addressed to its Temporary C-RNTI:

– if the MAC PDU is successfully decoded:

– stop mac-ContentionResolutionTimer;

– if the MAC PDU contains a UE Contention Resolution Identity MAC control element; and

– if the UE Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in Msg3:

– consider this Contention Resolution successful and finish the disassembly and demultiplexing of the MAC PDU;

– set the C-RNTI to the value of the Temporary C-RNTI;

– discard the Temporary C-RNTI;

– consider this Random Access procedure successfully completed.

– else

– discard the Temporary C-RNTI;

– consider this Contention Resolution not successful and discard the successfully decoded MAC PDU.

– 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.

– 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.7.3 Test description

7.1.2.7.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

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

7.1.2.7.3.2 Test procedure sequence

Table 7.1.2.7.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.

<–

1

2

The UE transmits a MAC PDU containing an RRCConnectionRequest message.

–>

MAC PDU

1

3

Check: For time equal to ‘Contention Resolution Timer’, does UE send a PRACH preamble?

–>

PRACH preamble

1

F

4

Check: does the UE transmit a MAC PDU containing an RRCConnectionRequest message?

–>

MAC PDU (RRCConnectionRequest)

1

P

EXCEPTION: In parallel with steps 5 to 8, the parallel behaviour in table 7.1.2.7.3.2-2 is running.

5

The SS Transmits a valid MAC PDU containing RRCConnectionSetup, but not including ‘UE Contention Resolution Identity’ MAC control element

<–

MAC PDU (RRCConnectionSetup)

2

6

Check: does the UE transmit a MAC PDU containing an RRCConnectionRequest message?

–>

MAC PDU (RRCConnectionRequest)

2

P

7

The SS Transmits a valid MAC PDU containing RRCConnectionSetup, and including ‘UE Contention Resolution Identity’ MAC control element but with un matched ‘Contention Resolution Identity’

<–

MAC PDU

3

8

Check: does the UE transmit a MAC PDU containing an RRCConnectionRequest message?

–>

MAC PDU

3

P

9

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

4

10

Check: does the UE transmit a MAC PDU containing an RRCConnectionSetupComplete message including SERVICE REQUEST message?

–>

MAC PDU (RRCConnectionSetupComplete)

4

P

11-14

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.

Table 7.1.2.7.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: UE transmits a MAC PDU containing an RRCConnectionSetupComplete message indicating acceptance of RRCConnectionSetup message?

–>

MAC PDU (RRCConnectionSetupComplete)

2,3

F

7.1.2.7.3.3 Specific message contents

7.1.2.7.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.7.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 {

preambleTransMax

N10

Max value

mac-ContentionResolutionTimer

sf64

Max value

}

}

}

}

7.1.2.8 MAC contention resolution / C-RNTI

7.1.2.8.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and after transmitting a RRCConnectionReconfigurationComplete message for a handover without dedicated preamble }

ensure that {

when { The SS does not schedule any PDCCH transmission addressed to UE C-RNTI before Contention resolution timer expiry }

then { The UE retransmits the RRCConnectionReconfigrationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and after transmitting a RRCConnectionReconfigurationComplete message for a handover without dedicated preamble }

ensure that {

when { UE receive PDCCH transmission addressed to its C-RNTI before Contention resolution timer expiry }

then { The UE does not retransmit the RRCConnectionReconfigrationComplete message }

}

7.1.2.8.2 Conformance requirements

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

[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 notification of a reception of a PDCCH transmission is received from lower layers, the UE shall:

– if the C-RNTI MAC control element was included in Msg3:

– if the Random Access procedure was initiated by the MAC sublayer itself and the PDCCH transmission is addressed to the C-RNTI and contains an UL grant for a new transmission; or

– if the Random Access procedure was initiated by a PDCCH order and the PDCCH transmission is addressed to the C-RNTI:

– consider this Contention Resolution successful;

– stop mac-ContentionResolutionTimer;

– discard the Temporary C-RNTI;

– consider this Random Access procedure successfully completed.

– else

– discard the Temporary C-RNTI;

– consider this Contention Resolution not successful and discard the successfully decoded MAC PDU.

– 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.

– 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.8.3 Test description

7.1.2.8.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

– System information as in table 7.1.2.8.3.3-1.

UE:

None.

Preamble:

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

7.1.2.8.3.2 Test procedure sequence

Table 7.1.2.8.3.2-0 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 7.1.2.8.3.2-0: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

Table 7.1.2.8.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

The SS changes Cell 1 and Cell 2 level according to the row "T1" in table 7.1.2.8.3.2-0

1

The SS transmits a MAC PDU containing an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2, not including explicit Random Access Preamble.

<–

MAC PDU

2

The UE transmits on cell 2 a MAC PDU containing RRCConnectionReconfigurationComplete, including C-RNTI MAC control element. SS is configured to not transmit RLC ACK for this transmission.

–>

MAC PDU

3

SS Does not schedule any PDCCH transmission for UE C-RNTI

4

Check: does the UE transmit a PRACH preamble within time equal to ‘Contention Resolution Timer’?

–>

(PRACH preamble)

1

F

5

Check: does the UE transmit on cell 2 a MAC PDU containing RRCConnectionReconfigurationComplete with RLC SN 0, including C-RNTI MAC control element?

–>

MAC PDU (RLC SN = 0 )

1

P

6

SS sends PDCCH transmission for UE C-RNTI

<–

7

Check: does the UE transmit MAC PDU containing RRCConnectionReconfigurationComplete with RLC SN 0 within the next 2s?

–>

MAC PDU (RLC SN = 0 )

2

F

8

Check: does the test result of CALL generic procedure indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 2?

2

7.1.2.8.3.3 Specific message contents

Table 7.1.2.8.3.3-1: SystemInformationBlockType2 (all steps, Table 7.1.2.8.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 {

preambleTransMax

N10

Max value

mac-ContentionResolutionTimer

sf64

Max value

}

}

}

}

Table 7.1.2.8.3.3-2: RRCConnectionReconfiguration (step 1, Table 7.1.2.8.3.2-1)

Derivation path: 36.508 table 4.6.1-6, condition RBC-HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInformation SEQUENCE {

MobilityControlInformation-HO

targetCellIdentity

PhysicalCellIdentity of Cell 2 (see 36.508 clause 4.4.4.2)

eutra-CarrierFreq

Not present

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.9 MAC back off indicator

7.1.2.9.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state and having initiated a random access procedure }

ensure that {

when { SS sends a Random Access Response including a Backoff Indicator and the Random Access Preamble identifier is different from the value received from the UE }

then { UE triggers RA preamble after a random time between 0 and the indicated Backoff parameter }

}

(2)

with { UE in E-UTRA RRC_IDLE state and having initiated a random access procedure }

ensure that {

when { SS sends a Random Access Response containing Backoff Indicator and a Random Access Preamble identifier with the same value as received from the UE }

then { UE stores Backoff Indicator and sends a RRC connection request in the first scheduled UL transmission }

}

(3)

with { UE in E-UTRA RRC_IDLE state and having initiated a random access procedure }

ensure that {

when { UE receives a Contention Resolution failure }

then { UE triggers RA preamble after random time between 0 and the UE stored Backoff parameter }

}

7.1.2.9.2 Conformance requirements

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

[TS 36.321 clause 5.1.4]

– 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 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 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:

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

– based on the backoff parameter in the UE, 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;

[TS 36.321 clause 5.1.5]

– 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.

– based on the backoff parameter in the UE, 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 (see subclause 5.1.2).

[TS 36.321 clause 7.2]

Back off Parameter values are presented in Table 7.2-1.

Table 7.2-1: Backoff Parameter values

Index

Backoff Parameter value (ms)

0

0

1

10

2

20

3

30

4

40

5

60

6

80

7

120

8

160

9

240

10

320

11

480

12

960

13

Reserved

14

Reserved

15

Reserved

The reserved values of the backoff parameter if received by the current release version UEs shall be taken as 960 ms.

7.1.2.9.3 Test description

7.1.2.9.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].

Table 7.1.2.9.3.1-1: Void

7.1.2.9.3.2 Test procedure sequence

Table 7.1.2.9.3.2-1: Back off Parameter values.

x: Index

y: Back off Parameter value (ms)

1

10

2

20

3

30

4

40

5

60

6

80

7

120

8

160

9

240

10

320

11

480

12

960

13

960

14

960

15

960

Table 7.1.2.9.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: Steps 1 to 5e are repeated for values of ‘x’ and ‘y’ according to table 7.1.2.9.3.2-1

1

SS pages the UE

<–

2

UE sends a Random Access Preamble

–>

Random Access Preamble

3

SS sends a Random Access Response with the back off parameter set to value Index field ‘x’ and with the Random Access Preamble identifier different from the value received from the UE in the Random Access Preamble.
The SS sets Timer_T1 to the Back off value ‘y’ associated with the Index value ‘x’ and starts Timer_T1.

<–

Random Access Response(BI, RAPID)

4

Check: Does UE send a Random Access Preamble while Timer_T1 is running?

–>

Random Access 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

5A

The UE transmits an RRCConnectionRequest message.

–>

5B

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

5C

The UE transmits an RRCConnectionSetupComplete message.

–>

5D

SS transmits SERVICE REJECT message with EMM cause "Congestion" to complete the procedure

Note: The EMM cause chosen is just for convenience, to ensure that UE will abort the procedure without side effects.

<–

5E

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

<–

EXCEPTION: Steps 6 to 20 are repeated for values of ‘x’ and ‘y’ according to table 7.1.2.9.3.2-1

6

SS pages the UE

<–

7

UE sends a Random Access Preamble

–>

Random Access Preamble

8

SS sends Random Access Response with a back off parameter set to value Index field ‘x’ and the Random Access Preamble identifier value set to the same value as received from the UE in the Random Access Preamble.

<–

Random Access Response(BI, RAPID)

9

Check: Does UE sends an RRCConnectionRequest in the grant associated to the Random Access ´Response received in step 8?

–>

MAC PDU (RRCConnectionRequest)

2

P

10

The SS sends a Contention Resolution Failure. The SS sets Timer_T1 to the Back off value ‘y’ associated with the Index value ‘x’ and starts Timer_T1.

<–

MAC Control PDU (Un matching UE Contention Resolution Identity)

11

Check: Does UE send a Random Access Preamble while Timer_T1 is running?

–>

Random Access 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 (RRCConnectionSetup)

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.

20

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

<–

7.1.2.9.3.3 Specific Message Contents

Table 7.1.2.9.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.9.3.2-2)

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-ConfigCommon-v1310

Not present

PRACH-ConfigSIB-v1310-CEMODE

CEmodeA,

CEmodeB

}

}

Condition

Explanation

CEmodeA

Used for CE mode A testing

CEmodeB

Used for CE mode B testing

Table 7.1.2.9.3.3-2: PRACH-ConfigSIB-v1310-CEMODE (Table 7.1.2.9.3.2-1)

Derivation Path: 36.508 clause 4.6.3, Table 4.6.3-7b

Information Element

Value/remark

Comment

Condition

PRACH-ConfigSIB-v1310-DEFAULT ::= SEQUENCE {

prach-ParametersListCE-r13 SEQUENCE (SIZE(1..maxCE-Level-r13)) OF SEQUENCE {

prach-StartingSubframe-r13[1]

Not present

}

..}

7.1.2.10 CA / Random access procedure / SCell

7.1.2.10.1 CA / Random access procedure / SCell / Intra-band Contiguous CA

7.1.2.10.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state having activated SCell with uplink configured }

ensure that {

when { PDCCH order is sent on the scheduling cell of the activated SCell providing Random Access Preamble }

then { UE sends the Random Access Preamble given in the PDCCH Order on the activated SCell }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and transmitting Random Access Preamble }

ensure that {

when { UE has data to send on the PCell }

then { UE sends the SR/ack/nack on PUCCH and data on the PUSCH of PCell in parallel with the Preamble transmission on the activated SCell }

}

(3)

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 on the activated SCell }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE has sent the Preamble on the activated SCell }

then { UE receives the Random Access Response on the PCell }

}

(5)

with { UE in E-UTRA RRC_CONNECTED state and completed the Random Access procedure on SCell }

ensure that {

when { UE has data to send and receives the UL Grant scheduled for the SCell }

then { UE transmits the data on the SCell }

}

7.1.2.10.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.1, clauses 5.1.2, 5.1.4 and 5.1.6; TS 36.212, clause 5.3.3.1.3; TS 36.213, clause 5.1.1.1. Unless otherwise stated these are Rel-11 requirements.

[TS 36.321, clause 5.1.1]

The Random Access procedure described in this subclause is initiated by a PDCCH order or by the MAC sublayer itself. Random Access procedure on a SCell shall only be initiated by a PDCCH order. If a UE receives a PDCCH transmission consistent with a PDCCH order [5] masked with its C-RNTI, and for a specific Serving Cell, the UE shall initiate a Random Access procedure on this Serving Cell. For Random Access on the PCell a PDCCH order or RRC optionally indicate the ra-PreambleIndex and the ra-PRACH-MaskIndex; and for Random Access on a SCell, the PDCCH order indicates the ra-PreambleIndex with a value different from 000000 and the ra-PRACH-MaskIndex. For the pTAG preamble transmission on PRACH and reception of a PDCCH order are only supported for PCell.

Before the procedure can be initiated, the following information for related Serving Cell is assumed to be available [8]:

– the available set of PRACH resources for the transmission of the Random Access Preamble, prach-ConfigIndex.

– the RA response window size ra-ResponseWindowSize.

– the power-ramping factor powerRampingStep.

– the maximum number of preamble transmission preambleTransMax.

– the initial preamble power preambleInitialReceivedTargetPower.

– the preamble format based offset DELTA_PREAMBLE (see subclause 7.6).

[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 of the PCell 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:

– 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.

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:

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

– indicate a Random Access problem to upper layers;

– if the Random Access Preamble is transmitted on a SCell:

– consider the Random Access procedure unsuccessfully completed.

[TS 36.321, clause 5.1.6]

At completion of the Random Access procedure, the UE shall:

– discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any;

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

[TS 36.212, clause 5.3.3.1.3]

DCI format 1A is used for the compact scheduling of one PDSCH codeword in one cell and random access procedure initiated by a PDCCH order. The DCI corresponding to a PDCCH order can be carried by PDCCH or EPDCCH.

The following information is transmitted by means of the DCI format 1A:

– Carrier indicator – 0 or 3 bits. This field is present according to the definitions in [3].

– Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A

Format 1A is used for random access procedure initiated by a PDCCH order only if format 1A CRC is scrambled with C-RNTI and all the remaining fields are set as follows:

– Localized/Distributed VRB assignment flag – 1 bit is set to ‘0’

– Resource block assignment – bits, where all bits shall be set to 1

– Preamble Index – 6 bits

– PRACH Mask Index – 4 bits, [5]

– All the remaining bits in format 1A for compact scheduling assignment of one PDSCH codeword are set to zero

[TS 36.213, clause 5.1.1.1]

If the UE is configured with multiple TAGs, the UE shall, when requested by higher layers, to transmit PRACH in a secondary serving cell in parallel with PUSCH/PUCCH in a different serving cell belonging to a different TAG, adjust the transmission power of PUSCH/PUCCH so that its total transmission power does not exceed on the overlapped portion.

7.1.2.10.1.3 Test description

7.1.2.10.1.3.1 Pre-test conditions

System Simulator:

  • Cell 1 (PCell) and Cell 3(SCell)
  • Cell 3 is an Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.2.10.1.3.3-1 and 7.1.2.10.1.3.3-2.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.2.10.1.3.2 Test procedure sequence

Table 7.1.2.10.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message with SCell (Cell 3) addition

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) addition.

–>

RRCConnectionReconfiguration Complete

3

The SS transmits an Activation MAC control element to activate SCell (Cell 3).

<–

MAC PDU (Activation (C1=1))

4

The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC1)

5

The SS transmits a PDCCH order providing Random Access Preamble on SCell (Cell 3)

<–

(PDCCH Order)

EXCEPTION: In parallel with step 6 to 8, parallel behaviour defined in table 7.1.2.10.1.3.2-2 is executed

.

6

Check: Does the UE transmit a preamble on PRACH using the same preamble index as given in step 5 on SCell (Cell3)?

–>

(PRACH Preamble)

1

P

7

Check: Does the UE transmit a preamble on PRACH after ra-ResponseWindowSize using the same preamble index as given in step 5 on SCell (Cell3)?

–>

(PRACH Preamble)

3

P

8

Check: Does the UE transmit a preamble on PRACH after ra-ResponseWindowSize using the same preamble index as given in step 5 on SCell (Cell3)?

–>

(PRACH Preamble)

3

P

9

The SS transmits Random Access Response with RAPID corresponding to Preamble in step 5 on PCell (Cell 1).

<–

Random Access Response

10

The SS indicates a new transmission on PDCCH of CC2 (Cell 3) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

11

The SS sends an UL grant suitable for transmitting loop back PDU on Cell 3.

<–

(UL Grant)

12

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 10?

–>

MAC PDU(CC2)

4, 5

P

13

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 12

<–

MAC PDU (CC2)

Table 7.1.2.10.1.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

2

P

2

The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1.

<–

(UL Grant)

3

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 4?

–>

MAC PDU

2

P

4

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 3

<–

MAC PDU (CC1)

7.1.2.10.1.3.3 Specific message contents

Table 7.1.2.10.1.3.3-1: RRCConnectionReconfiguration (preamble)

Derivation path: 36.508 Table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.2.10.1.3.3-2: SchedulingRequest-Configuration (preamble)

Derivation Path: 36.508 clause 4.6.3-20

Information Element

Value/remark

Comment

Condition

SchedulingRequest-Configuration ::= CHOICE {

setup SEQUENCE {

dsr-TransMax

n8

}

}

Table 7.1.2.10.1.3.3-3: RRCConnectionReconfiguration (step 1, Table 7.1.2.10.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.2.10.1.3.3-4: MAC-MainConfig-RBC (Table 7.1.2.10.1.3.3-3)

Derivation Path: 36.508, Table 4.8.2.1.5-1, condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

MAC-MainConfig-RBC ::= SEQUENCE {

stag-ToAddModList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

Not present

stag-Id-r11

1

timeAlignmentTimerSTAG-r11

infinity

}

}

Table 7.1.2.10.1.3.3-5: SCellToAddMod-r10 (Table 7.1.2.10.1.3.3-3)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 7.1.2.10.1.3.3-6: RadioResourceConfigCommonSCell-r10-f2 (Table 7.1.2.10.1.3.3-5)

Derivation Path: 36.508, Table 4.6.3-13A, condition UL_CA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10-DEFAULT ::= SEQUENCE {

rach-ConfigCommonSCell-r11 SEQUENCE {

powerRampingParameters-r11 SEQUENCE {

powerRampingStep

dB2

preambleInitialReceivedTargetPower

dBm-104 (default)

Thermal noise = -113 dBm

NF = 5 dB

IoT = 6 dB

Required SNR = -8 dB (See table 8.4.2-1 in TS 36.104 [30])

-> -110 dB

(default value is acceptable)

}

ra-SupervisionInfo-r11 SEQUENCE {

preambleTransMax-r11

n6

}

}

prach-ConfigSCell-r11 SEQUENCE {

rootSequenceIndex

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-4 in TS 36.211 [41] for PRACH format 0-3

FDD

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-5 in TS 36.211 [41] for PRACH format 4

TDD

prach-ConfigInfo SEQUENCE {

prach-ConfigIndex

3

Typical value in real network for FDD (see table 5.7.1-1 and 5.7.1-2 in TS 36.211 [41])

FDD

51

Typical value in real network for TDD (see table 5.7.1-3 and 5.7.1-4 in TS 36.211 [41])

TDD

highSpeedFlag

FALSE

zeroCorrelationZoneConfig

prach-FreqOffset

See TS 36.508 [18] clause 4.6.8

Channel-bandwidth-dependent parameter

}

}

uplinkPowerControlCommonSCell-v1130 SEQUENCE

Not present

}

Table 7.1.2.10.1.3.3-7: RadioResourceConfigDedicatedSCell-r10-f2 (Table 7.1.2.10.1.3.3-5)

Derivation Path: 36.508, Table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10

PhysicalConfigDedicatedSCell-r10-DEFAULT

mac-MainConfigSCell-r11 SEQUENCE {

stag-Id-r11

1

}

}

7.1.2.10.2 CA / Random access procedure / SCell / Inter-band CA

The scope and description of the present TC is the same as test case 7.1.2.10.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Active SCell according to [18] cl. 6.3.4

7.1.2.10.3 CA / Random access procedure / SCell / Intra-band non-contiguous CA

The scope and description of the present TC is the same as test case 7.1.2.10.1 with the following differences:

– CA configuration: Intra-band non-contiguous CA replaces Intra-band Contiguous CA

7.1.2.11 CA / Maintenance of uplink time alignment / Multiple TA

7.1.2.11.1 CA / Maintenance of uplink time alignment / Multiple TA / Intra-band Contiguous CA

7.1.2.11.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and having initiated a random access procedure on SCell }

ensure that {

when { The SS transmits a Timing Advance Command in a Random Access Response message }

then { UE applies the received Timing Advance value in the next transmitted MAC PDU on the SCell and starts the timeAlignmentTimerSTAG for this sTAG to which the SCell belongs }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and having completed the random access procedure on the SCell }

ensure that {

when { Timing Advance Command MAC control element with the TAG Id associated with the SCell is received and UE has pending data during the period the timeAlignmentTimer for the PCell and timeAlignmentTimerSTAG are running }

then { UE applies the received Timing Advance value for the next transmission of data and restarts the timeAlignmentTimerSTAG for this sTAG to which the SCell belongs }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when{ timeAlignmentTimer associated with the pTAG is running and timeAlignmentTimerSTAG associated with the sTAG has expired or is not running }

then { UE releases the SRS }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when{ timeAlignmentTimer associated with the pTAG expires and timeAlignmentTimerSTAG for the sTAG had not yet expired and UL transmission is required }

then { UE considers all timeAlignmentTimers, including the one for sTAG, as expired, triggers a RA Procedure on the PCell and releases SRS }

}

7.1.2.11.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clauses 5.2 and 6.1.3.5. Unless otherwise stated these are Rel-11 requirements.

[TS 36.321 clause 5.2]

The UE has a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer is used to control how long the UE considers the Serving Cells belonging to the associated TAG to be uplink time aligned [8].

The UE shall:

– when a Timing Advance Command MAC control element is received:

– apply the Timing Advance Command for the indicated TAG;

– start or restart the timeAlignmentTimer associated with the indicated TAG.

– when a Timing Advance Command is received in a Random Access Response message for a serving cell belonging to a TAG:

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

– apply the Timing Advance Command for this TAG;

– start or restart the timeAlignmentTimer associated with this TAG.

– else, if the timeAlignmentTimer associated with this TAG is not running:

– apply the Timing Advance Command for this TAG;

– start the timeAlignmentTimer associated with this TAG;

– when the contention resolution is considered not successful as described in subclause 5.1.5, stop timeAlignmentTimer associated with this TAG.

– else:

– ignore the received Timing Advance Command.

– when a timeAlignmentTimer expires:

– if the timeAlignmentTimer is associated with the pTAG:

– flush all HARQ buffers for all serving cells;

– notify RRC to release PUCCH/SRS for all serving cells;

– clear any configured downlink assignments and uplink grants;

– consider all running timeAlignmentTimers as expired;

– else if the timeAlignmentTimer is associated with an sTAG, then for all Serving Cells belonging to this TAG:

– flush all HARQ buffers;

– notify RRC to release SRS.

The UE shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble transmission when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not running. Furthermore, when the timeAlignmentTimer associated with the pTAG is not running, the UE shall not perform any uplink transmission on any Serving Cell except the Random Access Preamble transmission on the PCell.

NOTE: A UE stores or maintains NTA upon expiry of associated timeAlignmentTimer, where NTA is defined in [7]. The UE applies a received Timing Advance Command MAC control element and starts associated timeAlignmentTimer also when the timeAlignmentTimer is not running.

[TS 36.321 clause 6.1.3.5]

The Timing Advance Command MAC control element is identified by MAC PDU subheader with LCID as specified in table 6.2.1-1.

It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.5-1):

– TAG Identity (TAG Id): This field indicates the TAG Identity of the addressed TAG. The TAG containing the PCell has the TAG Identity 0. The length of the field is 2 bits;

– Timing Advance Command: This field indicates the index value TA (0, 1, 2… 63) used to control the amount of timing adjustment that UE has to apply (see subclause 4.2.3 of [2]). The length of the field is 6 bits.

Figure 6.1.3.5-1: Timing Advance Command MAC control element

7.1.2.11.1.3 Test description

7.1.2.11.1.3.1 Pre-test condition

System Simulator:

  • Cell 1 (PCell) and Cell 3(SCell)
  • Cell 3 is an Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.2.11.1.3.3-1 and 7.1.2.11.1.3.3-2.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.2.11.1.3.2 Test procedure sequence

Table 7.1.2.11.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message with SCell (Cell 3) and the related sTAG addition.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) and sTAG addition.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an Activation MAC control element to activate SCell (Cell 3).

<–

MAC PDU (Activation (C1=1))

4

The SS transmits a PDCCH order providing Random Access Preamble on SCell (Cell 3)

<–

(PDCCH Order)

5

The UE transmits a preamble on PRACH using the same preamble index as given in step 4 on SCell (Cell 3)

–>

(PRACH Preamble)

6

The SS transmits Random Access Response with RAPID corresponding to Preamble in step 4 on PCell (Cell 1) and with TA field within message set to 61(FDD) or 22(TDD) (Note 2).

Note: UE starts the timeAlignmentTimerSTAG

<–

MAC PDU(Random Access Response (TA=61(FDD) or TA=22(TDD))

7

The SS indicates a new transmission on PDCCH of CC2 (Cell 3) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

8

60ms After step 7 the SS sends an UL grant suitable for transmitting loop back PDU on Cell 3.

<–

(UL Grant)

9

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 7 on SCell Cell 3 in the first scheduled UL transmission using the Timing Advance value sent by the SS in step 6?

–>

MAC PDU

1

P

10

The SS transmits Timing Advance command with TAG Id equalling to sTAG id.

Note: UE restarts the timeAlignmentTimerSTAG.

<–

MAC PDU (Timing Advance Command MAC Control Element)

11

The SS indicates a new transmission on PDCCH of CC2 (Cell 3) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

12

60ms After step 11, the SS sends an UL grant suitable for transmitting loop back PDU on Cell 3.

<–

(UL Grant)

13

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 11 in the first scheduled UL transmission using the Timing Advance value sent by the SS in step 10?

–>

MAC PDU

2

P

14

Wait for the timeAlignmentTimerSTAG equalling to 750ms to expire.

Check: Does the UE send the SRS on the SCell (Cell 3)?

–>

(SRS)

3

F

15

The SS transmits a PDCCH order providing Random Access Preamble on SCell (Cell 3)

<–

(PDCCH Order)

16

The UE transmits a preamble on PRACH using the same preamble index as given in step 15 on SCell (Cell 3)

–>

(PRACH Preamble)

17

The SS transmits Random Access Response with RAPID corresponding to Preamble in step 16 on PCell (Cell 1) and with TA field within message set to 61(FDD) or 22(TDD) (Note 2).

Note: UE starts the timeAlignmentTimerSTAG

<–

MAC PDU(Random Access Response (TA=61(FDD) or TA=22(TDD))

17A

The SS transmits a RRCConnectionReconfiguration message to re-initialize UL SRS for SCell.

<–

RRCConnectionReconfiguration

17B

The UE transmits a RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

18

SS transmits Timing Advance command with TAG Id equalling to pTAG id 0.

Note: UE restarts the timeAlignmentTimerDedicated for PCell to apply the new TAT value configured in step 1.

<–

MAC PDU (Timing Advance Command MAC Control Element)

19

300 ms after step 18, The SS transmits Timing Advance command with TAG Id equalling to sTAG id.

Note: UE restarts the timeAlignmentTimerSTAG.

<–

MAC PDU (Timing Advance Command MAC Control Element)

20

After 600ms (0.8 * timeAlignmentTimerDedicated for pTAG) after step 18 SS sends a MAC PDU containing a RLC PDU on cell 3 k.

<–

MAC PDU

21

Wait the timeAlignmentTimerDedicated for pTAG to expire.

EXCEPTION: In parallel with step 22, parallel behaviour defined in table 7.1.2.11.1.3.2-2 is executed

22

Check: Does the UE transmit a Random Access Preamble on PCell?

–>

Random Access Preamble

4

P

23

SS responds with a valid Random Access Response on PCell.

<–

MAC PDU (Random Access Response (Temporary C-RNTI))

24

The SS sends an UL grant suitable for transmitting loop back PDU on PCell.

<–

(UL Grant)

25

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 20?

–>

MAC PDU

4

P

Note 1: A conformant UE correctly applies Timing Advance Command MAC Control and restarts timeAlignmentTimer, causing the uplink to stay in sync for a period equal to the timeAlignmentTimer.

Note 2: For FDD, TA value of 61 has been chosen to not exceed the maximum uplink transmission timing difference between TAGs for inter-band carrier aggregation that a UE should be able to handle and corresponds to 0.3177 ms (timing advance in ms = 1000 x NTA x where NTA = TA ×16 and seconds according to TS 36.213 and TS 36.211).
For TDD, TA value of 22 has been chosen and corresponds to 0.03177 ms (timing advance in ms = 1000 x (N_TA + N_TA_offset) x Ts where N_TA = TA x 16, N_TA_offset = 624Ts, and Ts = 1/(15000 x 2048) seconds according to TS 36.213 and TS 36.211).

Table 7.1.2.11.1.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE send the SRS on the SCell (Cell 3)?

–>

(SRS)

4

F

7.1.2.11.1.3.3 Specific Message Contents

Table 7.1.2.11.1.3.3-1: RRCConnectionReconfiguration (preamble)

Derivation path: 36.508 Table 4.6.1-8

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.2.11.1.3.3-2: SchedulingRequest-Configuration (preamble)

Derivation Path: 36.508 clause 4.6.3-20

Information Element

Value/remark

Comment

Condition

SchedulingRequest-Configuration ::= CHOICE {

setup SEQUENCE {

dsr-TransMax

n8

}

}

Table 7.1.2.11.1.3.3-3: RRCConnectionReconfiguration (step 1, Table 7.1.2.11.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.2.11.1.3.3-4: MAC-MainConfig-RBC (Table 7.1.2.11.1.3.3-3)

Derivation Path: 36.508, Table 4.8.2.1.5-1, condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

MAC-MainConfig-RBC ::= SEQUENCE {

timeAlignmentTimerDedicated

sf750

stag-ToAddModList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

Not present

stag-Id-r11

1

timeAlignmentTimerSTAG-r11

sf750

}

mac-MainConfig-v1020 SEQUENCE {

sCellDeactivationTimer-r10

rf128

}

}

Table 7.1.2.11.1.3.3-5: SCellToAddMod-r10 (Table 7.1.2.11.1.3.3-3)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 7.1.2.11.1.3.3-6: RadioResourceConfigCommonSCell-r10-f2 (Table 7.1.2.11.1.3.3-5)

Derivation Path: 36.508, Table 4.6.3-13A, condition UL_CA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10-DEFAULT ::= SEQUENCE {

rach-ConfigCommonSCell-r11 SEQUENCE {

powerRampingParameters-r11 SEQUENCE {

powerRampingStep

dB2

preambleInitialReceivedTargetPower

dBm-104 (default)

Thermal noise = -113 dBm

NF = 5 dB

IoT = 6 dB

Required SNR = -8 dB (See table 8.4.2-1 in TS 36.104 [30])

-> -110 dB

(default value is acceptable)

}

ra-SupervisionInfo-r11 SEQUENCE {

preambleTransMax-r11

n6

}

}

prach-ConfigSCell-r11 SEQUENCE {

rootSequenceIndex

prach-ConfigInfo SEQUENCE {

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-4 in TS 36.211 [41] for PRACH format 0-3

FDD

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-5 in TS 36.211 [41] for PRACH format 4

TDD

prach-ConfigIndex

3

Typical value in real network for FDD (see table 5.7.1-1 and 5.7.1-2 in TS 36.211 [41])

FDD

51

Typical value in real network for TDD (see table 5.7.1-3 and 5.7.1-4 in TS 36.211 [41])

TDD

highSpeedFlag

FALSE

zeroCorrelationZoneConfig

prach-FreqOffset

See TS 36.508 [18] clause 4.6.8

Channel-bandwidth-dependent parameter

}

}

uplinkPowerControlCommonSCell-v1130 SEQUENCE {

Not present

}

}

Table 7.1.2.11.1.3.3-7: RadioResourceConfigDedicatedSCell-r10-f2 (Table 7.1.2.11.1.3.3-5)

Derivation Path: 36.508, Table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10 ::= SEQUENCE {

ul-Configuration-r10 ::= SEQUENCE {

soundingRS-UL-ConfigDedicated-r10

SoundingRS-UL-ConfigDedicated-DEFAULT

soundingRS-UL-ConfigDedicated-v1020 ::= SEQUENCE {

srs-AntennaPort-r10

an1

}

}

}

mac-MainConfigSCell-r11 SEQUENCE {

stag-Id-r11

1

}

}

Table 7.1.2.11.1.3.3-8: RRCConnectionReconfiguration (step 17A, Table 7.1.2.11.1.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.2.11.1.3.3-9: SCellToAddMod-r10 (Table 7.1.2.11.1.3.3-8)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

}

Table 7.1.2.11.1.3.3-10: RadioResourceConfigDedicatedSCell-r10-f2 (Table 7.1.2.11.1.3.3-9)

Derivation Path: 36.508, Table 4.6.3-19AA, condition UL_CA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10 ::= SEQUENCE {

ul-Configuration-r10 ::= SEQUENCE {

soundingRS-UL-ConfigDedicated-r10 ::= SEQUENCE {

srs_Bandwidth

bw0

srs_HoppingBandwidth

hbw0

freqDomainPosition

0

duration

true

srs_ConfigIndex

20

transmissionComb

0

cyclicShift

cs0

}

soundingRS-UL-ConfigDedicated-v1020 ::= SEQUENCE {

srs-AntennaPort-r10

an1

}

}

7.1.2.11.2 CA / Maintenance of uplink time alignment / Multiple TA / Inter-band CA

The scope and description of the present TC is the same as test case 7.1.2.11.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Active SCell according to [18] cl. 6.3.4

7.1.2.11.3 CA / Maintenance of uplink time alignment / Multiple TA / Intra-band non-contiguous CA

The scope and description of the present TC is the same as test case 7.1.2.11.1 with the following differences:

– CA configuration: Intra-band non-contiguous CA replaces Intra-band Contiguous CA

7.1.2.11.4 FDD-TDD CA / Maintenance of uplink time alignment / Multiple TA

7.1.2.11.4.1 Test Purpose (TP)

(1)

with { UE supporting of FDD-TDD CA in E-UTRA RRC_CONNECTED state with two different frame structure type SCells in one sTAG }

ensure that {

when { The SS transmits a Timing Advance Command in a Random Access Response message }

then { UE applies the received Timing Advance value in the next transmitted MAC PDU on the SCell by using NTAoffset = 624 }

}

(2)

with { UE supporting of FDD-TDD CA in E-UTRA RRC_CONNECTED state with two different frame structure type SCells in one sTAG }

ensure that {

when { The SS transmits Timing Advance Command MAC control element with the TAG Id associated with the sTAG which includes two different frame structure type SCells }

then { UE applies the received Timing Advance value in the next transmitted MAC PDU on the SCell by using NTAoffset = 624 }

}

7.1.2.11.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.213 clauses 5.2 and 6.1.3.5; TS 36.213 clause 4.2.3. Unless otherwise stated these are Rel-12 requirements.

[TS 36.321 clause 5.2]

The UE has a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer is used to control how long the UE considers the Serving Cells belonging to the associated TAG to be uplink time aligned [8].

The UE shall:

– when a Timing Advance Command MAC control element is received:

– apply the Timing Advance Command for the indicated TAG;

– start or restart the timeAlignmentTimer associated with the indicated TAG.

– when a Timing Advance Command is received in a Random Access Response message for a serving cell belonging to a TAG:

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

– apply the Timing Advance Command for this TAG;

– start or restart the timeAlignmentTimer associated with this TAG.

– else, if the timeAlignmentTimer associated with this TAG is not running:

– apply the Timing Advance Command for this TAG;

– start the timeAlignmentTimer associated with this TAG;

– when the contention resolution is considered not successful as described in subclause 5.1.5, stop timeAlignmentTimer associated with this TAG.

– else:

– ignore the received Timing Advance Command.

The UE shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble transmission when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not running. Furthermore, when the timeAlignmentTimer associated with the pTAG is not running, the UE shall not perform any uplink transmission on any Serving Cell except the Random Access Preamble transmission on the PCell.

NOTE: A UE stores or maintains NTA upon expiry of associated timeAlignmentTimer, where NTA is defined in [7]. The UE applies a received Timing Advance Command MAC control element and starts associated timeAlignmentTimer also when the timeAlignmentTimer is not running.

[TS 36.321 clause 6.1.3.5]

The Timing Advance Command MAC control element is identified by MAC PDU subheader with LCID as specified in table 6.2.1-1.

It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.5-1):

– TAG Identity (TAG Id): This field indicates the TAG Identity of the addressed TAG. The TAG containing the PCell has the TAG Identity 0. The length of the field is 2 bits;

– Timing Advance Command: This field indicates the index value TA (0, 1, 2… 63) used to control the amount of timing adjustment that UE has to apply (see subclause 4.2.3 of [2]). The length of the field is 6 bits.

Figure 6.1.3.5-1: Timing Advance Command MAC control element

[TS 36.213 clause 4.2.3]

Upon reception of a timing advance command for a TAG not containing the primary cell or PSCell, if a serving cell in the TAG has a different frame structure type compared to the frame structure type of another serving cell in the same TAG, the UE shall adjust uplink transmission timing for PUSCH/SRS of all the secondary cells in the TAG by using NTAoffset = 624 regardless of the frame structure type of the serving cells and based on the received timing advance command where the UL transmission timing for PUSCH /SRS is the same for all the secondary cells in the TAG. NTAoffset is described in [3].

7.1.2.11.4.3 Test description

7.1.2.11.4.3.1 Pre-test condition

System Simulator:

PCell , SCell 1 (FDD) and SCell 2 (TDD)

  • SCell 1 and SCell 2 are Active SCell according to [18] cl. 6.3.4.
  • If PCell is TDD, PCell(Cell 10), SCell 1(Cell 1), SCell 2(Cell 28), SCell 2 is on the same band as PCell.
  • If PCell is FDD, PCell(Cell 1)., SCell 1(Cell 3), SCell 2(Cell 10), SCell 1 is on the same band as PCell.

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.2.11.4.3.3-1 and 7.1.2.11.4.3.3-2.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.2.11.4.3.2 Test procedure sequence

Table 7.1.2.11.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message with SCell ( SCell 1 and SCell 2) and the related sTAG addition.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell ( SCell 1 and SCell 2) and sTAG addition.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an Activation MAC control element to activate SCell ( SCell 1 and SCell 2).

<–

MAC PDU (Activation (C1=1, C2=1))

4

The SS transmits a PDCCH order providing Random Access Preamble on SCell ( SCell 1)

<–

(PDCCH Order)

5

The UE transmits a preamble on PRACH using the same preamble index as given in step 4 on SCell ( SCell 1)

–>

(PRACH Preamble)

6

The SS transmits Random Access Response with RAPID corresponding to Preamble in step 4 on PCell and with TA field within message set to TA=160 (Note 2).

Note: UE starts the timeAlignmentTimerSTAG

<–

MAC PDU(Random Access Response (TA=160)

7

The SS indicates a new transmission on PDCCH of CC2 ( SCell 1) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

8

60ms After step 7 the SS sends an UL grant suitable for transmitting loop back PDU on Cell 10.

<–

(UL Grant)

9

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 7 on SCell ( SCell 1) in the first scheduled UL transmission using the Timing Advance value sent by the SS in step 6 by using NTAoffset=624?

–>

MAC PDU

1

P

10

The SS transmits Timing Advance command with TAG Id equalling to sTAG id.

Note: UE restarts the timeAlignmentTimerSTAG.

<–

MAC PDU (Timing Advance Command MAC Control Element)

11

The SS indicates a new transmission on PDCCH of CC2 ( SCell 1) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

12

60ms After step 11 the SS sends an UL grant suitable for transmitting loop back PDU on Cell 10.

<–

(UL Grant)

13

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 11 in the first scheduled UL transmission using the Timing Advance value sent by the SS in step 10 by using NTAoffset=624?

–>

MAC PDU

2

P

14

The SS transmits a PDCCH order providing Random Access Preamble on SCell ( SCell 2)

<–

(PDCCH Order)

15

The UE transmits a preamble on PRACH using the same preamble index as given in step 14 on SCell ( SCell 2)

–>

(PRACH Preamble)

16

The SS transmits Random Access Response with RAPID corresponding to Preamble in step 15 on PCell and with TA field within message set to 160 (Note 2).

Note: UE starts the timeAlignmentTimerSTAG

<–

MAC PDU(Random Access Response (TA=160)

17

The SS indicates a new transmission on PDCCH of CC3 ( SCell 2) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC3)

18

60ms After step 17 the SS sends an UL grant suitable for transmitting loop back PDU on Cell 28.

<–

(UL Grant)

19

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 17 on SCell ( SCell 2) in the first scheduled UL transmission using the Timing Advance value sent by the SS in step 16 by using NTAoffset=624?

–>

MAC PDU

1

P

20

The SS transmits Timing Advance command with TAG Id equalling to sTAG id.

Note: UE restarts the timeAlignmentTimerSTAG.

<–

MAC PDU (Timing Advance Command MAC Control Element)

21

The SS indicates a new transmission on PDCCH of CC3 ( SCell 2) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU

22

60ms After step 21 the SS sends an UL grant suitable for transmitting loop back PDU on SCell ( SCell 2).

<–

(UL Grant)

23

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 21 on SCell ( SCell 2) in the first scheduled UL transmission using the Timing Advance value sent by the SS in step 20 by using NTAoffset=624?

–>

MAC PDU

2

P

Note 1: A conformant UE correctly applies Timing Advance Command MAC Control and restarts timeAlignmentTimer, causing the uplink to stay in sync for a period equal to the timeAlignmentTimer.

Note 2: For FDD-TDD CA with the TAG not containing a primary cell includes the serving cells with different frame structure types, TA value of 160 has been chosen and corresponds to 0.1036 ms (timing advance in ms = 1000 x (N_TA + N_TA_offset) x Ts where N_TA = TA x 16, N_TA_offset = 624Ts, and Ts = 1/(15000 x 2048) seconds according to TS 36.213 and TS 36.211).

7.1.2.11.4.3.3 Specific Message Contents

Table 7.1.2.11.4.3.3-0: Conditions for specific message contents
in Tables 7.1.2.11.4.3.3-5 and 7.1.2.11.4.3.3-6

Condition

Explanation

Band > 64

If band > 64 is selected

Table 7.1.2.11.4.3.3-1: RRCConnectionReconfiguration (preamble)

Derivation path: 36.508 Table 4.6.1-8

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.2.11.4.3.3-2: SchedulingRequest-Configuration (preamble)

Derivation Path: 36.508 clause 4.6.3-20

Information Element

Value/remark

Comment

Condition

SchedulingRequest-Configuration ::= CHOICE {

setup SEQUENCE {

dsr-TransMax

n8

}

}

Table 7.1.2.11.4.3.3-3: RRCConnectionReconfiguration (step 1, Table 7.1.2.11.4.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.2.11.4.3.3-4: MAC-MainConfig-RBC (Table 7.1.2.11.4.3.3-3)

Derivation Path: 36.508, Table 4.8.2.1.5-1, condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

MAC-MainConfig-RBC ::= SEQUENCE {

timeAlignmentTimerDedicated

sf750

stag-ToAddModList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

Not present

stag-Id-r11

1

timeAlignmentTimerSTAG-r11

sf750

}

mac-MainConfig-v1020 SEQUENCE {

sCellDeactivationTimer-r10

rf128

}

}

Table 7.1.2.11.4.3.3-5: SCellToAddMod-r10-f5 (Table 7.1.2.11.1.3.3-3)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 10

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 10

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 10

Band > 64

}

Table 7.1.2.11.4.3.3-6: SCellToAddMod-r10-f6 (Table 7.1.2.11.1.3.3-3)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

2

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 28

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 28

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 28

Band > 64

}

Table 7.1.2.11.4.3.3-7: RadioResourceConfigCommonSCell-r10-f5 and f6 (Table 7.1.2.11.4.3.3-5)

Derivation Path: 36.508, Table 4.6.3-13A, condition UL_CA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10-DEFAULT ::= SEQUENCE {

rach-ConfigCommonSCell-r11 SEQUENCE {

powerRampingParameters-r11 SEQUENCE {

powerRampingStep

dB2

preambleInitialReceivedTargetPower

dBm-104 (default)

Thermal noise = -113 dBm

NF = 5 dB

IoT = 6 dB

Required SNR = -8 dB (See table 8.4.2-1 in TS 36.104 [30])

-> -110 dB

(default value is acceptable)

}

ra-SupervisionInfo-r11 SEQUENCE {

preambleTransMax-r11

n6

}

}

prach-ConfigSCell-r11 SEQUENCE {

rootSequenceIndex

prach-ConfigInfo SEQUENCE {

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-4 in TS 36.211 [41] for PRACH format 0-3

FDD

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-5 in TS 36.211 [41] for PRACH format 4

TDD

prach-ConfigIndex

3

Typical value in real network for FDD (see table 5.7.1-1 and 5.7.1-2 in TS 36.211 [41])

FDD

51

Typical value in real network for TDD (see table 5.7.1-3 and 5.7.1-4 in TS 36.211 [41])

TDD

highSpeedFlag

FALSE

zeroCorrelationZoneConfig

prach-FreqOffset

See TS 36.508 [18] clause 4.6.8

Channel-bandwidth-dependent parameter

}

}

uplinkPowerControlCommonSCell-v1130 SEQUENCE {

Not present

}

}

Table 7.1.2.11.4.3.3-8: RadioResourceConfigDedicatedSCell-r10-f5 and f6 (Table 7.1.2.11.4.3.3-5)

Derivation Path: 36.508, Table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10

PhysicalConfigDedicatedSCell-r10-DEFAULT

mac-MainConfigSCell-r11 SEQUENCE {

stag-Id-r11

1

}

}

7.1.2.12 CA / Random access procedure / TDD SCell without PUSCH/PUCCH transmission

7.1.2.12.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex and ul-Configuration-r14 }

ensure that {

when { UE transmits PRACH Preamble after reception of PDCCH order on the TDD SCell, and UE does not receive a matching Random Access response in ra-ResponseWindowSize }

then { UE doesn’t retransmit the Preamble given in the PDCCH order }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex and ul-Configuration-r14 }

ensure that {

when { UE receives Random Access Response along with UL grant }

then { UE ignores the UL grant }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex and ul-Configuration-r14 }

ensure that {

when { timeAlignmentTimer associated with the pTAG is running and timeAlignmentTimerSTAG associated with the sTAG has expired or is not running }

then { UE releases the SRS }

}

7.1.2.12.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.2, 5.1.4, 5.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]

The MAC entity 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 MAC entity shall regardless of the possible occurrence of a measurement gap or a Sidelink Discovery Gap for Transmission or a Sidelink Discovery Gap for Reception:

– if the Random Access Response contains a Backoff Indicator subheader:

– set the backoff parameter value as indicated by the BI field of the Backoff Indicator subheader and Table 7.2-1, except for NB-IoT where the value from Table 7.2-2 is used.

– else, set the backoff parameter value 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 MAC entity shall:

– consider this Random Access Response reception successful and apply the following actions for the serving cell where the Random Access Preamble was transmitted:

– 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);

– if the SCell is configured with ul-Configuration-r14, ignore the received UL grant otherwise process the received UL grant value and indicate it to the lower layers;

[…]

If no Random Access Response or, for NB-IoT UEs, BL UEs or UEs in enhanced coverage for mode B operation, no PDCCH scheduling 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 MAC entity shall:

– if the notification of power ramping suspension has not been received from lower layers:

– increment PREAMBLE_TRANSMISSION_COUNTER by 1;

– 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;

– else:

– if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:

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

– indicate a Random Access problem to upper layers;

– if the Random Access Preamble is transmitted on an SCell:

– 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;

– else if the SCell where the Random Access Preamble was transmitted is configured with ul-Configuration-r14:

– delay the subsequent Random Access transmission until the Random Access Procedure is initiated by a PDCCH order with the same ra-PreambleIndex and ra-PRACH-MaskIndex;

[TS 36.321, clause 5.2]

The MAC entity shall:

– when a timeAlignmentTimer expires:

– if the timeAlignmentTimer is associated with the pTAG:

– else if the timeAlignmentTimer is associated with an sTAG, then for all Serving Cells belonging to this TAG:

– flush all HARQ buffers;

– notify RRC to release SRS;

– notify RRC to release PUCCH, if configured.

– consider all running timeAlignmentTimers as expired;

7.1.2.12.3 Test description

7.1.2.12.3.1 Pre-test conditions

System Simulator:

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

7.1.2.12.3.2 Test procedure sequence

Table 7.1.2.12.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList with SCell Cell 3 addition without UL carrier the related sTAG addition. The SRS configuration on the last symbol of 4th subframe every radio frame is setup in SCell Cell3.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) and sTAG addition.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits a PDCCH order providing Random Access Preamble in SCell Cell 3.

<–

(PDCCH Order)

4

Check: does the UE transmit a preamble on PRACH using the same preamble index as given in step 3 in SCell Cell 3?

–>

(PRACH Preamble)

1

P

5

Check: does the UE transmit a preamble on PRACH after ra-ResponseWindowSize using the same preamble index as given in step 3 in SCell Cell 3?

–>

(PRACH Preamble)

1

F

6

The SS transmits a PDCCH order providing Random Access Preamble in SCell Cell 3.

<–

(PDCCH Order)

7

Check: does the UE transmit a preamble on PRACH using the same preamble index as given in step 6 in SCell Cell 3?

–>

(PRACH Preamble)

1

P

8

60ms After step 7 The SS transmits a Random Access Response including an UL grant of 7 bytes in SCell Cell 3.

Note: UE starts the timeAlignmentTimerSTAG

<–

Random Access Response

9

Check: Does the UE transmit a MAC PDU including a C-RNTI MAC Control Element in SCell Cell 3?

–>

MAC PDU

2

F

10

Wait for the timeAlignmentTimerSTAG equalling to 750ms to expire.

Check: Does the UE send the SRS in the SCell (Cell 3)?

–>

(SRS)

3

F

7.1.2.12.3.3 Specific Message Contents

Table 7.1.2.12.3.3-1: RRCConnectionReconfiguration (step 1, Table 7.1.2.12.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.2.12.3.3-2: MAC-MainConfig-RBC (Table 7.1.2.12.3.3-1)

Derivation Path: 36.508, Table 4.8.2.1.5-1, condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

MAC-MainConfig-RBC ::= SEQUENCE {

timeAlignmentTimerDedicated

Infinity

stag-ToAddModList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

Not present

stag-Id-r11

1

timeAlignmentTimerSTAG-r11

sf750

}

mac-MainConfig-v1020 SEQUENCE {

sCellDeactivationTimer-r10

rf128

}

}

Table 7.1.2.12.3.3-3: SCellToAddMod-r10-DEFAULT (Table 7.1.2.12.3.3-1)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 7.1.2.12.3.3-4: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 7.1.2.12.3.3-3)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10-DEFAULT ::= SEQUENCE {

rach-ConfigCommonSCell-r11 SEQUENCE {

powerRampingParameters-r11 SEQUENCE {

powerRampingStep

dB2

preambleInitialReceivedTargetPower

dBm-104 (default)

}

ra-SupervisionInfo-r11 SEQUENCE {

preambleTransMax-r11

n6

}

}

ul-Configuration-r14 SEQUENCE {

prach-ConfigSCell-r14 SEQUENCE {

prach-ConfigIndex-r10

51

}

}

}

Table 7.1.2.12.3.3-5: RadioResourceConfigDedicatedSCell-r10-DEFAULT (Table 7.1.2.12.3.3-3)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10 ::= SEQUENCE {

PhysicalConfigDedicatedSCell-r10-DEFAULT with condition SRS-Switching

soundingRS-UL-PeriodicConfigDedicatedList-r14 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

soundingRS-UL-ConfigDedicated ::= CHOICE {

SoundingRS-Ul-ConfigDedicated-DEFAULT

setup SEQUENCE {

srs-ConfigIndex

18

INTEGER (0..1023) See Table 8.2-2 in TS 36.213

}

}

}

}

mac-MainConfigSCell-r11 SEQUENCE {

stag-Id-r11

1

}

}

7.1.2.13 CA / PUCCH SCell / Maintenance of uplink time alignment

7.1.2.13.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and PUCCH SCell configured and activated }

ensure that {

when{ timeAlignmentTimer associated with the pTAG is running and timeAlignmentTimerSTAG associated with the sTAG has expired or is not running }

then { UE releases the PUCCH resource in PUCCH SCell }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and PUCCH SCell configured and activated }

ensure that {

when{ timeAlignmentTimer associated with the pTAG expires and timeAlignmentTimerSTAG for the sTAG had not yet expired and UL transmission is required }

then { UE considers all timeAlignmentTimers, including the one for sTAG, as expired, triggers a RA Procedure on the PCell and releases PUCCH resource in PUCCH SCell }

}

7.1.2.13.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clauses 5.2 and 6.1.3.5. Unless otherwise stated these are Rel-13 requirements.

[TS 36.321 clause 5.2]

The MAC entity has a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer is used to control how long the MAC entity considers the Serving Cells belonging to the associated TAG to be uplink time aligned, as specified in TS 36.331 [8].

The MAC entity shall:

– when a timeAlignmentTimer expires:

– if the timeAlignmentTimer is associated with the pTAG:

– flush all HARQ buffers for all serving cells;

– notify RRC to release PUCCH/SPUCCH for all serving cells;

– notify RRC to release SRS for all serving cells;

– for NB-IoT, notify RRC to release all dedicated resources for SR;

– clear any configured downlink assignments and uplink grants;

– consider all running timeAlignmentTimers as expired;

– else if the timeAlignmentTimer is associated with an sTAG, then for all Serving Cells belonging to this TAG:

– flush all HARQ buffers;

– notify RRC to release SRS;

– notify RRC to release PUCCH/SPUCCH, if configured;

– clear any configured downlink assignments and uplink grants.

When the MAC entity stops uplink transmissions for an SCell due to the fact that the maximum uplink transmission timing difference (as described in subclause 7.9.2 of TS 36.133 [9]) or the maximum uplink transmission timing difference the UE can handle between TAGs of any MAC entity of the UE is exceeded, the MAC entity considers the timeAlignmentTimer associated with the SCell as expired.

The MAC entity shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble transmission when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not running. Furthermore, when the timeAlignmentTimer associated with the pTAG is not running, the MAC entity shall not perform any uplink transmission on any Serving Cell except the Random Access Preamble transmission on the SpCell.

The MAC entity shall not perform any sidelink transmission which is performed based on UL timing of the corresponding serving cell and any associated SCI transmissions when the corresponding timeAlignmentTimer is not running.

NOTE: A MAC entity stores or maintains NTA upon expiry of associated timeAlignmentTimer, where NTA is defined in TS 36.211 [7]. The MAC entity applies a received Timing Advance Command MAC control element and starts associated timeAlignmentTimer also when the timeAlignmentTimer is not running.

[TS 36.321 clause 6.1.3.5]

The Timing Advance Command MAC control element is identified by MAC PDU subheader with LCID as specified in table 6.2.1-1.

It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.5-1):

– TAG Identity (TAG Id): This field indicates the TAG Identity of the addressed TAG. The TAG containing the PCell has the TAG Identity 0. The length of the field is 2 bits;

– Timing Advance Command: This field indicates the index value TA (0, 1, 2… 63) used to control the amount of timing adjustment that UE has to apply (see subclause 4.2.3 of [2]). The length of the field is 6 bits.

Figure 6.1.3.5-1: Timing Advance Command MAC control element

7.1.2.13.3 Test description

7.1.2.13.3.1 Pre-test condition

System Simulator:

  • Cell 1 (PCell) and Cell 3(SCell)
  • Cell 3 is an Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.2.13.3.3-1 and 7.1.2.13.3.3-2.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.2.13.3.2 Test procedure sequence

Table 7.1.2.13.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message with SCell (Cell 3) and the related sTAG addition. Cell 3 is configured as PUCCH SCell.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) and sTAG addition.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an Activation MAC control element to activate SCell (Cell 3).

<–

MAC PDU (Activation (C1=1))

4

The SS transmits a PDCCH order providing Random Access Preamble on SCell (Cell 3)

<–

(PDCCH Order)

5

The UE transmits a preamble on PRACH using the same preamble index as given in step 4 on SCell (Cell 3)

–>

(PRACH Preamble)

6

The SS transmits Random Access Response with RAPID corresponding to Preamble in step 4 on PCell (Cell 1) and with TA field within message set to 61(FDD) or 22(TDD) (Note 2).

Note: UE starts the timeAlignmentTimerSTAG

<–

MAC PDU(Random Access Response (TA=61(FDD) or TA=22(TDD))

7

The SS indicates a new transmission on PDCCH of CC2 (Cell 3) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

8

UE sends HARQ ACK on PUCCH of CC2 (Cell 3)

–>

HARQ ACK

9

Wait for the timeAlignmentTimerSTAG for sTAG to expire.

10

The SS indicates a new transmission on PDCCH of CC2 (Cell 3) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

11

Check: Does UE send HARQ ACK on PUCCH of CC2 (Cell 3)?

–>

HARQ ACK

1

F

12

The SS transmits a PDCCH order providing Random Access Preamble on SCell (Cell 3)

<–

(PDCCH Order)

13

The UE transmits a preamble on PRACH using the same preamble index as given in step 12 on SCell (Cell 3)

–>

(PRACH Preamble)

14

The SS transmits Random Access Response with RAPID corresponding to Preamble in step 12 on PCell (Cell 1) and with TA field within message set to 61(FDD) or 22(TDD) (Note 2).

Note: UE starts the timeAlignmentTimerSTAG

<–

MAC PDU(Random Access Response (TA=61(FDD) or TA=22(TDD))

15

The SS transmits an RRCConnectionReconfiguration message adding PUCCH configuration on SCell (Cell 3).

<–

RRCConnectionReconfiguration

16

The UE transmits an RRCConnectionReconfigurationComplete message to confirm PUCCH configuration on SCell (Cell 3).

–>

RRCConnectionReconfigurationComplete

17

The SS indicates a new transmission on PDCCH of CC2 (Cell 3) and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

18

UE sends HARQ ACK on PUCCH of CC2 (Cell 3)

–>

HARQ ACK

19

SS transmits Timing Advance command with TAG Id equalling to pTAG id 0.

Note: UE restarts the timeAlignmentTimerDedicated for PCell to apply the new TAT value configured in step 1.

<–

MAC PDU (Timing Advance Command MAC Control Element)

20

300 ms after step 19, The SS transmits Timing Advance command with TAG Id equalling to sTAG id.

Note: UE restarts the timeAlignmentTimerSTAG.

<–

MAC PDU (Timing Advance Command MAC Control Element)

21

Wait the timeAlignmentTimerDedicated for pTAG to expire.

22

The SS indicates a new transmission on PDCCH of CC2 (Cell 3) and transmits a MAC PDU (containing an RLC PDU)

<–

MAC PDU (CC2)

23

Check: Does UE send HARQ ACK on PUCCH of CC2 (Cell 3)?

–>

HARQ ACK

2

F

24

Check: Does the UE transmit a Random Access Preamble on PCell?

–>

Random Access Preamble

2

P

Note 1: A conformant UE correctly applies Timing Advance Command MAC Control and restarts timeAlignmentTimer, causing the uplink to stay in sync for a period equal to the timeAlignmentTimer.

Note 2: For FDD, TA value of 61 has been chosen to not exceed the maximum uplink transmission timing difference between TAGs for inter-band carrier aggregation that a UE should be able to handle and corresponds to 0.3177 ms (timing advance in ms = 1000 x NTA x where NTA = TA ×16 and seconds according to TS 36.213 and TS 36.211).
For TDD, TA value of 22 has been chosen and corresponds to 0.03177 ms (timing advance in ms = 1000 x (N_TA + N_TA_offset) x Ts where N_TA = TA x 16, N_TA_offset = 624Ts, and Ts = 1/(15000 x 2048) seconds according to TS 36.213 and TS 36.211).

7.1.2.13.3.3 Specific Message Contents

Table 7.1.2.13.3.3-1: RRCConnectionReconfiguration (preamble)

Derivation path: 36.508 Table 4.6.1-8

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.2.13.3.3-2: SchedulingRequest-Configuration (preamble)

Derivation Path: 36.508 clause 4.6.3-20

Information Element

Value/remark

Comment

Condition

SchedulingRequest-Configuration ::= CHOICE {

setup SEQUENCE {

dsr-TransMax

n8

}

}

Table 7.1.2.13.3.3-3: RRCConnectionReconfiguration (step 1, Table 7.1.2.13.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.2.13.3.3-4: MAC-MainConfig-RBC (Table 7.1.2.13.3.3-3)

Derivation Path: 36.508, Table 4.8.2.1.5-1, condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

MAC-MainConfig-RBC ::= SEQUENCE {

timeAlignmentTimerDedicated

sf750

stag-ToAddModList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

Not present

stag-Id-r11

1

timeAlignmentTimerSTAG-r11

sf500

}

mac-MainConfig-v1020 SEQUENCE {

sCellDeactivationTimer-r10

rf128

}

}

Table 7.1.2.13.3.3-5: SCellToAddMod-r10 (Table 7.1.2.13.3.3-3)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 7.1.2.13.3.3-6: RadioResourceConfigCommonSCell-r10-f2 (Table 7.1.2.13.3.3-5)

Derivation Path: 36.508, Table 4.6.3-13A, condition UL_CA and PUCCH-SCell

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10-DEFAULT ::= SEQUENCE {

rach-ConfigCommonSCell-r11 SEQUENCE {

powerRampingParameters-r11 SEQUENCE {

powerRampingStep

dB2

preambleInitialReceivedTargetPower

dBm-104 (default)

Thermal noise = -113 dBm

NF = 5 dB

IoT = 6 dB

Required SNR = -8 dB (See table 8.4.2-1 in TS 36.104 [30])

-> -110 dB

(default value is acceptable)

}

ra-SupervisionInfo-r11 SEQUENCE {

preambleTransMax-r11

n6

}

}

prach-ConfigSCell-r11 SEQUENCE {

rootSequenceIndex

prach-ConfigInfo SEQUENCE {

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-4 in TS 36.211 [41] for PRACH format 0-3

FDD

See TS 36.508 [18] clause 4.4.2, Table 4.4.2-1A and clause 6.3.2.2 Table 6.3.2.2-2

See table 5.7.2-5 in TS 36.211 [41] for PRACH format 4

TDD

prach-ConfigIndex

3

Typical value in real network for FDD (see table 5.7.1-1 and 5.7.1-2 in TS 36.211 [41])

FDD

51

Typical value in real network for TDD (see table 5.7.1-3 and 5.7.1-4 in TS 36.211 [41])

TDD

highSpeedFlag

FALSE

zeroCorrelationZoneConfig

prach-FreqOffset

See TS 36.508 [18] clause 4.6.8

Channel-bandwidth-dependent parameter

}

}

uplinkPowerControlCommonSCell-v1130 SEQUENCE {

Not present

}

}

Table 7.1.2.13.3.3-7: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 7.1.2.13.3.3-5)

Derivation path: 36.508 table 4.6.3-6A, condition PUCCH-SCell

Table 7.1.2.13.3.3-8: RRCConnectionReconfiguration (step 15, Table 7.1.2.13.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.2.13.3.3-9: SCellToAddMod-r10 (Table 7.1.2.13.3.3-8)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

}

Table 7.1.2.13.3.3-10: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 7.1.2.13.3.3-9)

Derivation path: 36.508 table 4.6.3-6A, condition PUCCH-SCell