Ts 13652301v120300p

ETSI TS 136 523-1 V12.3.
0 (2014-11)
TECHNICAL SPECIFICATION
LTE;
Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC);
User Equipment (UE) conformance specification;
Part 1: Protocol conformance specification
(3GPP TS 36.523-1 version 12.3.0 Release 12)
3GPP TS 36.523-1 version 12.3.0 Release 12 1 ETSI TS 136 523-1 V12.3.0 (2014-11)
Reference
RTS/TSGR-0536523-1vc30
Keywords
LTE
ETSI
650 Route des Lucioles

F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C

Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:

http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2014.

All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
Intellectual Property Rights

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by the ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology

In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Modal verbs terminology....................................................................................................................................2
Foreword...........................................................................................................................................................26
Introduction ......................................................................................................................................................26
1 Scope ......................................................................................................................................................27
2 References ..............................................................................................................................................27
3 Definitions, symbols and abbreviations .................................................................................................29
3.1 Definitions ........................................................................................................................................................ 29
3.2 Abbreviations ................................................................................................................................................... 30
4 Overview ................................................................................................................................................30
4.1 Test methodology ............................................................................................................................................. 30
4.1.1 Testing of optional functions and procedures ............................................................................................. 30
4.1.2 Test interfaces and facilities........................................................................................................................ 30
4.2 Implicit testing.................................................................................................................................................. 30
4.3 Repetition of tests ............................................................................................................................................. 30
4.4 Handling of differences between conformance requirements in different releases of cores specifications ...... 30
5 Reference conditions ..............................................................................................................................31
5.1 Generic setup procedures ................................................................................................................................. 31
6 Idle mode operations ..............................................................................................................................31
6.0 Introduction ...................................................................................................................................................... 31
6.0.1 PLMN and TAC ......................................................................................................................................... 31
6.0.2 Other ........................................................................................................................................................... 32
6.0.2.1 Values of parameters calculated by the UE........................................................................................... 32
6.1 In a pure E-UTRAN environment .................................................................................................................... 32
6.1.1 PLMN selection .......................................................................................................................................... 32
6.1.1.1 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode ............. 32
6.1.1.1a PLMN selection / Automatic mode/between FDD and TDD................................................................ 37
6.1.1.1b PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
Single Frequency operation................................................................................................................... 41
6.1.1.2 PLMN selection of "Other PLMN/access technology combinations" / Automatic mode ..................... 44
6.1.1.2a PLMN selection of "Other PLMN/access technology combinations" / Automatic mode / Single
Frequency operation .............................................................................................................................. 48
6.1.1.3 Cell reselection of ePLMN in manual mode ......................................................................................... 50
6.1.1.3a Cell reselection of ePLMN in manual mode / between FDD and TDD ................................................ 52
6.1.1.3b Cell reselection of ePLMN in manual mode / Single Frequency operation .......................................... 56
6.1.1.4 PLMN selection in shared network environment / Automatic mode .................................................... 57
6.1.1.4a PLMN selection in shared network environment / Automatic mode / Between FDD and TDD .......... 60
6.1.1.5 Void....................................................................................................................................................... 64
6.1.1.6 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
User reselection ..................................................................................................................................... 64
6.1.1.6a PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
User reselection / Single Frequency operation ...................................................................................... 68
6.1.1.7 PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer ............................................. 71
6.1.1.7a PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer / Single Frequency
operation ............................................................................................................................................... 74
6.1.2 Cell selection and reselection...................................................................................................................... 76
6.1.2.1 Void....................................................................................................................................................... 76
6.1.2.2 Cell selection / Qrxlevmin .................................................................................................................... 76
6.1.2.2a Cell selection / Qqualmin ...................................................................................................................... 79
6.1.2.3 Cell selection / Intra E-UTRAN / Serving cell becomes non-suitable (S<0 or barred) ......................... 83
ETSI
6.1.2.3a Cell selection / Intra E-UTRAN / Serving cell becomes non-suitable (Srxlev > 0 and Squal < 0) ....... 87
6.1.2.4 Cell reselection ...................................................................................................................................... 91
6.1.2.5 Cell reselection for interband operation ................................................................................................ 93
6.1.2.6 Cell reselection using Qhyst, Qoffset and Treselection .................................................................................... 96
6.1.2.7 Cell reselection / Equivalent PLMN ................................................................................................... 101
6.1.2.7a Cell reselection / Equivalent PLMN / Single Frequency operation .................................................... 105
6.1.2.8 Cell reselection using cell status and cell reservations / Access control class 0 to 9 .......................... 108
6.1.2.8a Cell reselection using cell status and cell reservations / Access control class 0 to 9 / Single
Frequency operation ............................................................................................................................ 112
6.1.2.9 Cell reselection using cell status and cell reservations / Access control class 11 to 15 ...................... 116
6.1.2.9a Cell reselection using cell status and cell reservations / Access control class 11 to 15 / Single
Frequency operation ............................................................................................................................ 120
6.1.2.10 Cell reselection in shared network environment ................................................................................. 124
6.1.2.11 Inter-frequency cell reselection ........................................................................................................... 127
6.1.2.12 Cell reselection / Cell-specific reselection parameters provided by the network in a neighbouring
cell list ................................................................................................................................................. 129
6.1.2.13 Cell reselection, Sintrasearch, Snonintrasearch ................................................................................................ 132
6.1.2.14 Speed-dependent cell reselection ........................................................................................................ 138
6.1.2.15 Inter-frequency cell reselection according to cell reselection priority provided by SIBs .................... 142
6.1.2.15a Inter-frequency cell reselection according to cell reselection priority provided by SIBs / Between
FDD and TDD ..................................................................................................................................... 147
6.1.2.15b Inter-band cell reselection according to cell reselection priority provided by SIBs ............................ 152
6.1.2.16 Cell reselection / interband operation / Between FDD and TDD ........................................................ 154
6.1.2.17 Cell reselection for Squal to check against SIntraSearchQ and SnonIntraSearchQ ............................................. 159
6.1.2.18 Inter-frequency cell reselection based on common priority information with parameters ThreshX,
HighQ, ThreshX, LowQ and ThreshServing, LowQ ............................................................................................ 166
6.1.2.19 Intra-frequency cell reselection / MFBI .............................................................................................. 170
6.1.2.20 Inter-frequency cell reselection / MFBI .............................................................................................. 174
6.1.2.21 Inter-band cell reselection / MFBI ...................................................................................................... 177
6.2 Multi-mode environment (E-UTRAN, UTRAN, GERAN, CDMA2000)...................................................... 180
6.2.1 Inter-RAT PLMN selection ...................................................................................................................... 180
6.2.1.1 Inter-RAT PLMN Selection / Selection of correct RAT for OPLMN / Automatic mode ................... 180
6.2.1.2 Inter-RAT PLMN Selection / Selection of correct RAT for UPLMN / Automatic mode ................... 185
6.2.1.3 Inter-RAT PLMN Selection / Selection of correct PLMN and RAT in shared network
environment / Automatic mode ........................................................................................................... 187
6.2.1.4 Inter-RAT PLMN Selection / Selection of correct RAT from the OPLMN list / Manual mode......... 191
6.2.1.5 ............................................................................................................................................................ 194
6.2.1.6 Inter-RAT Background HPLMN Search / Search for correct RAT for HPLMN / Automatic
Mode ................................................................................................................................................... 194
6.2.2 Inter-RAT cell selection............................................................................................................................ 196
6.2.2.1 Inter-RAT cell selection / From E-UTRA RRC_IDLE to UTRA_Idle / Serving cell becomes
non-suitable ......................................................................................................................................... 196
6.2.2.2 Inter-RAT cell selection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_idle / Serving
cell becomes non-suitable ................................................................................................................... 202
6.2.2.3 Inter-RAT Cell selection / From E-UTRA RRC_IDLE to HRPD Idle / Serving cell becomes
non-suitable ......................................................................................................................................... 208
6.2.2.4 Inter-RAT Cell selection / From E-UTRAN RRC_IDLE to 1xRTT idle / Serving cell becomes
non-suitable ......................................................................................................................................... 211
6.2.2.5 Cell selection / No USIM .................................................................................................................... 214
6.2.2.6 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-UTRA_RRC_IDLE /
Serving cell becomes non-suitable ...................................................................................................... 216
6.2.2.7 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-UTRA_RRC_IDLE ,when
the serving cell is barred. .................................................................................................................... 217
6.2.2.8 Inter-RAT cell selection / From UTRA_Idle to E-UTRA RRC_IDLE / Serving cell becomes
non-suitable ......................................................................................................................................... 219
6.2.3 Inter-RAT cell reselection ........................................................................................................................ 225
6.2.3.1 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_Idle ............... 225
6.2.3.1a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_Idle (Squal
< ThreshServing, LowQ, Srxlev > ThreshX, LowP and Srxlev > ThreshX, HighP) ............................................. 230
6.2.3.2 Void..................................................................................................................................................... 235
6.2.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE............................................ 235
ETSI
6.2.3.3a Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE (QqualminEUTRA,

SqualServingCell < Threshserving,low2, SqualnonServingCell,x > Threshx, low2 and SqualnonServingCell,x > Threshx,
high2) ..................................................................................................................................................... 240
6.2.3.4 Inter-RAT cell reselection / From UTRA_CELL_PCH state to E-UTRA RRC_IDLE ...................... 246
6.2.3.4a Inter-RAT cell reselection / From UTRA_CELL_PCH state to E-UTRA RRC_IDLE based on
RSRQ+RSRP evaluation..................................................................................................................... 251
6.2.3.5 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle............................................ 258
6.2.3.5a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle (Squal > ThreshX, HighQ,
Squal < ThreshServing, LowQ, Squal > ThreshX, LowQ and SnonIntraSearchQ) ................................................... 261
6.2.3.6 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle according to RAT
priority provided by dedicated signalling ............................................................................................ 269
6.2.3.7 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is higher
reselection priority than E-UTRA ....................................................................................................... 278
6.2.3.7a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is higher
reselection priority than E-UTRA (Srxlev > ThreshHRPD, HighP) ........................................................... 283
6.2.3.8 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD is lower
reselection priority than E-UTRA ....................................................................................................... 288
6.2.3.8a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is lower
reselection priority than E-UTRA (Squal < ThreshServing, LowQ and Srxlev > ThreshHRPD, LowP ............. 293
6.2.3.9 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT Dormant– When
CDMA2000 1xRTT cell is higher reselection priority than E-UTRA ................................................ 298
6.2.3.9a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant / 1xRTT cell is
higher reselection priority than E-UTRA (Srxlev > Thresh1xRTT, HighP) ............................................... 303
6.2.3.10 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT Idle – When
CDMA2000 1xRTT is lower reselection priority than E-UTRA ........................................................ 308
6.2.3.10a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant / 1xRTT cell is
lower reselection priority than E-UTRA (Squal < ThreshServing, LowQ and Srxlev > Thresh1xRTT,
LowP) ..................................................................................................................................................... 313
6.2.3.11 Void..................................................................................................................................................... 319
6.2.3.12 Void..................................................................................................................................................... 319
6.2.3.13 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE according to RAT
priority provided by dedicated signalling ............................................................................................ 319
6.2.3.14 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA (priority of E-
UTRA cells are higher than the serving cell) ...................................................................................... 326
6.2.3.15 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA (priority of E-
UTRA cells are lower than the serving cell) ....................................................................................... 329
6.2.3.16 Inter-RAT Cell Reselection / from GSM_Idle to E-UTRAN /based on H_PRIO criteria .................. 331
6.2.3.17 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA (priority E-UTRA
cells) .................................................................................................................................................... 334
6.2.3.18 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA (blacklisted E-
UTRA cells) ........................................................................................................................................ 336
6.2.3.19 Redirection to E-UTRA upon the release of the CS connection ......................................................... 338
6.2.3.20 Void..................................................................................................................................................... 341
6.2.3.21 Inter-RAT cell reselection / From GPRS Packet_Transfer (NC0 mode) to E-UTRA ......................... 341
6.2.3.22 Void..................................................................................................................................................... 343
6.2.3.23 Inter-RAT Cell Reselection from GPRS Packet transfer to E-UTRA in CCN Mode (PACKET
CELL CHANGE CONTINUE) .......................................................................................................... 343
6.2.3.24 Inter-RAT Cell Reselection from GPRS Packet transfer to E-UTRA in CCN Mode (PACKET
CELL CHANGE ORDER) ................................................................................................................. 347
6.2.3.25 Void..................................................................................................................................................... 350
6.2.3.26 Inter-RAT Autonomous Cell Reselection GPRS Packet_transfer to E-UTRA (NC1 mode) .............. 350
6.2.3.27 Inter-RAT Cell selection from GPRS Packet_transfer to E-UTRA (NC2 Mode) ............................... 354
6.2.3.28 Inter-RAT Cell Reselection from GPRS Packet_transfer to E-UTRA (Network Assisted Cell
Change) ............................................................................................................................................... 358
6.2.3.29 Inter-RAT cell Reselection from GPRS packet_transfer to E-UTRA in CCN mode (PACKET
MEASUREMENT ORDER)............................................................................................................... 363
6.2.3.30 Inter-RAT Cell Reselection failure from GPRS Packet transfer to E-UTRA (Network Assisted
Cell Change) ....................................................................................................................................... 368
6.2.3.31 Inter-RAT cell reselection / From UTRA_Idle (low priority) to E-UTRA RRC_IDLE (high
priority) according to RAT priority provided by dedicated signalling ................................................ 373
6.2.3.32 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle, Snonintrasearch ........................ 379
ETSI
6.2.3.33 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle / Squal based cell
reselection parameters are broadcasted in E-UTRAN / UE does not support Squal based cell
reselection in UTRAN......................................................................................................................... 383
6.2.3.34 Inter-RAT cell reselection from E-UTRA to UTRA / MFBI .............................................................. 386
6.2.4 Inter-RAT absolute priority based reselection in UTRA CELL_FACH ................................................... 389
6.2.4.1 Inter-RAT absolute priority based reselection in UTRA CELL_FACH to E-UTRA RRC_IDLE
(Higher Priority Layers, Srxlev,x > Threshx,high and Srxlev,serv > Sprioritysearch1 and
SqualServ > Sprioritysearch2) ............................................................................................................ 389
6.2.4.2 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (Higher Priority Layers,
no cell reselection to E-UTRA RRC_IDLE when Srxlev,serv < Sprioritysearch1) ............................ 392
6.2.4.3 Inter-RAT absolute priority based reselection in UTRA _CELL_FACH to E-UTRA RRC_IDLE
(Higher Priority Layers, Squal,x > Threshx,high2 and Srxlev,serv > Sprioritysearch1 and
SqualServ > Sprioritysearch2) ............................................................................................................ 394
6.2.4.4 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (lower priority) to E-
UTRA RRC_IDLE (higher priority) (All Layers, Srxlev,x > Threshx,high) ...................................... 397
6.2.4.5 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (lower priority) to E-
UTRA RRC_IDLE (higher priority) (All Layers, Squal,x >ThreshX,high2) .................................... 400
6.2.4.6 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (higher priority) to E-
UTRA RRC_IDLE (lower priority) (All Layers, Srxlev,serv < Sprioritysearch1 , Srxlev,serv
<Thresh serv,low and Srxlev,x > Threshx,low) .................................................................................. 404
6.2.4.7 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (higher priority) to E-
UTRA RRC_IDLE (lower priority) (All Layers, Srxlev,serv < Sprioritysearch1 , Squal,serv
<Thresh serv,low2 and Squal,x > ThreshX,low2) ............................................................................... 407
6.3 Closed Subscriber Group cells ....................................................................................................................... 411
6.3.1 Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-CSG cell to E-UTRA RRC_IDLE
CSG cell .................................................................................................................................................... 411
6.3.2 Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA idle CSG cell .................. 415
6.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE CSG cell .................................. 420
6.3.4 Inter-RAT cell reselection / From UTRA CELL_PCH state to E-UTRA RRC_IDLE CSG cell ............. 427
6.3.5 Manual support for CSG ID selection....................................................................................................... 433
6.3.6 Ignoring CSG cells in cell selection/reselection when allowed CSG list is empty or not supported ........ 438
6.3.7 Inter-RAT Cell reselection from E-UTRA idle non-CSG cell to a UTRA CSG cell ................................ 442
6.3.8 Inter-RAT CSG Cell Reselection from E-UTRA CSG cell to UTRA CSG cell....................................... 448
6.3.9 Manual CSG ID selection across PLMNs................................................................................................. 456
6.3.10 Void .......................................................................................................................................................... 459
6.3.11 Void .......................................................................................................................................................... 459
6.3.12 Inter-RAT cell selection / From E-UTRA RRC_IDLE to UTRA_Idle / CSG cell on same PLMN as
previously visited CSG cell ...................................................................................................................... 459
6.4 Hybrid cells .................................................................................................................................................... 463
6.4.1 Manual CSG ID selection / Hybrid cell whose CSG ID is not in the Allowed CSG list nor Operator’s
list ............................................................................................................................................................. 463
6.4.2 Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-CSG cell to E-UTRA RRC_IDLE
member hybrid cell ................................................................................................................................... 467
6.4.3 Inter-RAT cell reselection / From E-UTRA RRC_IDLE non-CSG cell to UTRA_Idle member
hybrid cell ................................................................................................................................................. 472
6.4.4 Inter-RAT cell reselection / From E-UTRA RRC_IDLE non-member hybrid cell to UTRA_Idle
member hybrid cell ................................................................................................................................... 477
6.4.5 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE member hybrid cell ................. 484
6.4.6 Inter-RAT cell reselection / From UTRA CELL_PCH to E-UTRA RRC_IDLE member hybrid cell ..... 490
6.4.7 Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA RRC_IDLE member
hybrid cell ................................................................................................................................................. 496
7 Layer 2..................................................................................................................................................502
7.1 MAC ............................................................................................................................................................... 502
7.1.1 Mapping between logical channels and transport channels ...................................................................... 502
7.1.1.1 CCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID .............................................. 502
7.1.1.2 DTCH or DCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID .............................. 505
7.1.2 RACH ....................................................................................................................................................... 509
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 ................. 509
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 .. 512
ETSI
7.1.2.3 Correct selection of RACH parameters / Preamble selected by MAC itself / Contention based
random access procedure .................................................................................................................... 514
7.1.2.4 Random access procedure / Successful ............................................................................................... 519
7.1.2.5 Random access procedure / MAC PDU containing multiple RARs ................................................... 525
7.1.2.6 Maintenance of uplink time alignment ................................................................................................ 528
7.1.2.7 MAC contention resolution / Temporary C-RNTI .............................................................................. 532
7.1.2.8 MAC contention resolution / C-RNTI................................................................................................. 535
7.1.2.9 MAC back off indicator ...................................................................................................................... 538
7.1.2.10 CA / Random access procedure / SCell............................................................................................... 542
7.1.2.10.1 CA / Random access procedure / SCell / Intra-band Contiguous CA............................................ 542
7.1.2.10.2 CA / Random access procedure / SCell / Inter-band CA ............................................................... 549
7.1.2.10.3 CA / Random access procedure / SCell / Intra-band non-contiguous CA ..................................... 549
7.1.2.11 CA / Maintenance of uplink time alignment / Multiple TA ................................................................ 549
7.1.2.11.1 CA / Maintenance of uplink time alignment / Multiple TA / Intra-band Contiguous CA ............. 549
7.1.2.11.2 CA / Maintenance of uplink time alignment / Multiple TA / Inter-band CA ................................ 557
7.1.2.11.3 CA / Maintenance of uplink time alignment / Multiple TA / Intra-band non-contiguous CA....... 557
7.1.3 DL-SCH data transfer ............................................................................................................................... 557
7.1.3.1 Correct handling of DL assignment / Dynamic case ........................................................................... 557
7.1.3.2 Correct handling of DL assignment / Semi-persistent case ................................................................. 559
7.1.3.3 MAC PDU header handling ................................................................................................................ 567
7.1.3.4 Correct HARQ process handling / DCCH and DTCH ........................................................................ 572
7.1.3.5 Correct HARQ process handling / CCCH ........................................................................................... 576
7.1.3.6 Correct HARQ process handling / BCCH ........................................................................................... 580
7.1.3.7 MAC padding ...................................................................................................................................... 585
7.1.3.8 Void..................................................................................................................................................... 587
7.1.3.9 MAC reset / DL................................................................................................................................... 587
7.1.3.10 ............................................................................................................................................................ 590
7.1.3.11 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell ..................................... 590
7.1.3.11.1 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Intra-band
Contiguous CA .............................................................................................................................. 590
7.1.3.11.2 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Inter-band CA ..... 595
7.1.3.11.3 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Intra-band non-
Contiguous CA .............................................................................................................................. 595
7.1.3.12 TDD additional special subframe configuration / Special subframe pattern 9 with Normal Cyclic
Prefix / CRS based transmission scheme ........................................................................................... 595
7.1.3.12a TDD additional special subframe configuration / Special subframe pattern 7 with Extended
Cyclic Prefix / CRS based transmission scheme ................................................................................. 600
7.1.3.13 TDD additional special subframe configuration / Special subframe pattern 9 with Normal Cyclic
Prefix / UE-specific reference signals based transmission scheme .................................................... 604
7.1.3.13a TDD additional special subframe configuration / Special subframe pattern 7 with Extended
Cyclic Prefix / UE-specific reference signals based transmission scheme .......................................... 613
7.1.3.14 Correct handling of DL assignment / Dynamic case / EPDCCH ........................................................ 621
7.1.3.15 Correct handling of DL assignment / Semi-persistent case / EPDCCH .............................................. 624
7.1.4 UL-SCH data transfer ............................................................................................................................... 634
7.1.4.1 Correct handling of UL assignment / Dynamic case ........................................................................... 634
7.1.4.2 Correct handling of UL assignment / Semi-persistent case ................................................................. 637
7.1.4.3 Logical channel prioritization handling .............................................................................................. 645
7.1.4.4 Correct handling of MAC control information / Scheduling requests and PUCCH............................ 648
7.1.4.5 Correct handling of MAC control information / Scheduling requests and random access
procedure............................................................................................................................................. 650
7.1.4.6 Correct handling of MAC control information / Buffer status / UL data arrive in the UE Tx
buffer and retransmission of BSR / Regular BSR ............................................................................... 655
7.1.4.7 Correct handling of MAC control information / Buffer Status / UL resources are allocated /
Padding BSR ....................................................................................................................................... 662
7.1.4.7a Correct handling of MAC control information / Buffer Status / UL resources are allocated /
Cancellation of Padding BSR.............................................................................................................. 667
7.1.4.8 Correct handling of MAC control information / Buffer status / Periodic BSR timer expires ............. 673
7.1.4.9 Void..................................................................................................................................................... 678
7.1.4.10 MAC padding ...................................................................................................................................... 678
7.1.4.11 Correct HARQ process handling......................................................................................................... 681
7.1.4.12 MAC reset / UL................................................................................................................................... 688
7.1.4.13 MAC PDU header handling ................................................................................................................ 692
ETSI
7.1.4.14 Correct HARQ process handling / TTI bundling ................................................................................ 697

7.1.4.15 UE power headroom reporting / Periodic reporting ............................................................................ 704
7.1.4.16 UE power headroom reporting / DL pathloss change reporting .......................................................... 707
7.1.4.17 711
7.1.4.18 Correct handling of MAC control information / Buffer Status / UL data arrive in the UE Tx
buffer / Extended buffer size ............................................................................................................... 711
7.1.4.18.1 Test Purpose (TP) .................................................................................................................... 711
7.1.4.18.3 Test description ............................................................................................................................. 713
7.1.4.18.3.1 Pre-test conditions.................................................................................................................... 713
7.1.4.18.3.2 Definition of system information messages ............................................................................. 714
7.1.4.18.3.3 Specific message contents........................................................................................................ 714
7.1.4.19 CA / UE power headroom reporting / SCell activation and DL pathloss change reporting /
Extended PHR ..................................................................................................................................... 714
7.1.4.19.1 CA / UE power headroom reporting / SCell activation and DL pathloss change reporting /
Extended PHR / Intra-band Contiguous CA .................................................................................. 714
Extended PHR / Inter-band CA ..................................................................................................... 720
Extended PHR / Intra-band non-Contiguous CA .......................................................................... 720
7.1.4.20 CA / Correct handling of MAC control information / Buffer status ................................................... 720
7.1.4.20.1 CA / Correct handling of MAC control information / Buffer status / Intra-band Contiguous
CA ................................................................................................................................................. 720
7.1.4.20.2 CA / Correct handling of MAC control information / Buffer status / Inter-band CA.................... 725
7.1.4.21 UE power headroom reporting / Extended PHR ................................................................................. 725
7.1.4.22 Correct HARQ process handling / UL MIMO .................................................................................... 730
7.1.5 PUSCH Hopping ...................................................................................................................................... 737
7.1.5.1 Inter-TTI PUSCH hopping by uplink grant ........................................................................................ 737
7.1.5.2 Predefined intra-TTI PUSCH hopping (N_sb=1)................................................................................ 740
7.1.5.3 Predefined intra-TTI PUSCH hopping (N_sb=2/3/4) ......................................................................... 744
7.1.5.4 Predefined inter-TTI PUSCH hopping (N_sb=1)................................................................................ 746
7.1.5.5 Predefined inter-TTI PUSCH hopping (N_sb=2/3/4) ......................................................................... 747
7.1.6 DRX operation .......................................................................................................................................... 748
7.1.6.1 DRX operation / Short cycle not configured / Parameters configured by RRC .................................. 748
7.1.6.2 DRX Operation / Short cycle not configured / DRX command MAC control element reception ...... 755
7.1.7 Transport block size selection ................................................................................................................... 760
7.1.7.0 Specific configurations........................................................................................................................ 760
7.1.7.1 DL-SCH transport block size selection ............................................................................................... 761
7.1.7.1.1 DL-SCH transport block size selection / DCI format 1 / RA type 0.............................................. 761
7.1.7.1.2 DL-SCH transport block size selection / DCI format 1 / RA type 1.............................................. 774
7.1.7.1.3 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Localised VRB ............... 788
7.1.7.1.4 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Distributed VRB............. 802
7.1.7.1.5 DL-SCH transport block size selection / DCI format 2A / RA type 0 / Two transport blocks
enabled / Transport block to codeword swap flag value set to ’0’ ................................................ 816
7.1.7.1.6 DL-SCH Transport Block Size selection / DCI format 2A / RA type 1 / Two transport blocks
enabled / Transport block to codeword swap flag value set to ’1’ ................................................ 832
7.1.7.2 UL-SCH transport block size support ................................................................................................. 847
7.1.7.2.1 UL-SCH transport block size selection / DCI format 0 ................................................................. 847
7.1.8 Reporting of Rank Indicator (RI) .............................................................................................................. 860
7.1.8.1 Periodic RI reporting using PUCCH / Category 1 UE / Transmission mode 3/4 ................................ 860
7.1.9 Activation/Deactivation of SCells ............................................................................................................ 864
7.1.9.1 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element
reception / sCellDeactivationTimer .................................................................................................... 864
7.1.9.1.1 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element
reception / sCellDeactivationTimer / Intra-band Contiguous CA ................................................. 864
reception / sCellDeactivationTimer / Inter-band CA ..................................................................... 868
reception / sCellDeactivationTimer / Intra-band non-Contiguous CA .......................................... 868
7.1.10 Coordinated Multi-Point Operation (CoMP) for LTE .............................................................................. 869
7.1.10.1 Sending SR on PUCCH with DMRS generated by using virtual cell identity / nPUCCH-Identity .... 869
7.1.10.2 Transmitting data on PUSCH with DMRS generated by using virtual cell identity / nPUSCH-
Identity ................................................................................................................................................ 872
ETSI
7.2 RLC ................................................................................................................................................................ 876

7.2.1 General...................................................................................................................................................... 876
7.2.2 Unacknowledged mode............................................................................................................................. 876
7.2.2.1 UM RLC / Segmentation and reassembly / 5-bit SN / Framing info field .......................................... 876
7.2.2.2 UM RLC / Segmentation and reassembly / 10-bit SN / Framing info field ........................................ 878
7.2.2.3 UM RLC / Reassembly / 5-bit SN / LI value > PDU size ................................................................... 880
7.2.2.4 UM RLC / Reassembly / 10-bit SN / LI value > PDU size ................................................................. 881
7.2.2.5 UM RLC / Correct use of sequence numbering .................................................................................. 882
7.2.2.5.1 UM RLC / 5-bit SN / Correct use of sequence numbering ............................................................ 882
7.2.2.5.2 UM RLC / 10-bit SN / Correct use of Sequence numbering ......................................................... 886
7.2.2.6 UM RLC / Concatenation, segmentation and reassembly................................................................... 889
7.2.2.7 UM RLC / In sequence delivery of upper layer PDUs without residual loss of RLC PDUs /
Maximum re-ordering delay below t-Reordering ............................................................................... 894
7.2.2.8 UM RLC / In sequence delivery of upper layer PDUs without residual loss of RLC PDUs /
Maximum re-ordering delay exceeds t-Reordering ............................................................................ 897
7.2.2.9 UM RLC / In sequence delivery of upper layer PDUs with residual loss of RLC PDUs /
Maximum re-ordering delay exceeds t-Reordering ............................................................................ 899
7.2.2.10 UM RLC / Duplicate detection of RLC PDUs .................................................................................... 901
7.2.2.11 UM RLC / RLC re-establishment procedure ...................................................................................... 903
7.2.3 Acknowledged mode ................................................................................................................................ 906
7.2.3.1 AM RLC / Concatenation and reassembly .......................................................................................... 906
7.2.3.2 AM RLC / Segmentation and reassembly / No PDU segmentation .................................................... 909
7.2.3.3 AM RLC / Segmentation and reassembly / Framing info field ........................................................... 911
7.2.3.4 AM RLC / Segmentation and reassembly / Different numbers of length indicators ........................... 913
7.2.3.5 AM RLC / Reassembly / LI value > PDU size ................................................................................... 916
7.2.3.6 AM RLC / Correct use of sequence numbering .................................................................................. 917
7.2.3.7 AM RLC / Control of transmit window .............................................................................................. 921
7.2.3.8 AM RLC / Control of receive window................................................................................................ 924
7.2.3.9 AM RLC / Polling for status ............................................................................................................... 925
7.2.3.10 AM RLC / Receiver status triggers ..................................................................................................... 930
7.2.3.11 Void..................................................................................................................................................... 935
7.2.3.12 Void..................................................................................................................................................... 935
7.2.3.13 AM RLC / Reconfiguration of RLC parameters by upper layers........................................................ 935
7.2.3.14 AM RLC / In sequence delivery of upper layers PDUs ...................................................................... 941
7.2.3.15 AM RLC / Re-ordering of RLC PDU segments ................................................................................. 944
7.2.3.16 AM RLC / Re-transmission of RLC PDU without re-segmentation ................................................... 949
7.2.3.17 AM RLC / Re-segmentation RLC PDU / SO, FI, LSF ....................................................................... 952
7.2.3.18 AM RLC / Reassembly / AMD PDU reassembly from AMD PDU segments, Segmentation
Offset and Last Segment Flag fields ................................................................................................... 956
7.2.3.19 Void..................................................................................................................................................... 961
7.2.3.20 AM RLC / Duplicate detection of RLC PDUs .................................................................................... 961
7.2.3.21 AM RLC / RLC re-establishment at RRC connection reconfiguration including
mobilityControlInfo IE ........................................................................................................................ 963
7.3 PDCP .............................................................................................................................................................. 965
7.3.1 Maintenance of PDCP sequence numbers for radio bearers ..................................................................... 965
7.3.1.1 Maintenance of PDCP sequence numbers / User plane / RLC AM .................................................... 965
7.3.1.2 Maintenance of PDCP sequence numbers / User plane / RLC UM / Short PDCP SN (7 bits) ........... 968
7.3.1.3 Maintenance of PDCP sequence numbers / User plane / RLC UM / Long PDCP SN (12 bits) ......... 970
7.3.2 Void .......................................................................................................................................................... 972
7.3.3 PDCP ciphering and deciphering .............................................................................................................. 972
7.3.3.1 Ciphering and deciphering / Correct functionality of EPS AS encryption algorithms / SNOW 3G ... 972
7.3.3.2 Ciphering and deciphering / Correct functionality of EPS UP encryption algorithms / SNOW 3G ... 975
7.3.3.3 Ciphering and deciphering / Correct functionality of EPS AS encryption algorithms / AES ............. 977
7.3.3.4 Ciphering and deciphering / Correct functionality of EPS UP encryption algorithms / AES ............. 979
7.3.3.5 Ciphering and deciphering / Correct functionality of EPS AS encryption algorithms / ZUC ............. 980
7.3.3.6 Ciphering and deciphering / Correct functionality of EPS UP encryption algorithms / ZUC ............. 982
7.3.4 PDCP integrity protection ......................................................................................................................... 984
7.3.4.1 Integrity protection / Correct functionality of EPS AS integrity algorithms / SNOW3G ................... 984
7.3.4.2 Integrity protection / Correct functionality of EPS AS integrity algorithms / AES ............................ 989
7.3.4.3 Integrity protection / Correct functionality of EPS AS integrity algorithms / ZUC ............................ 992
7.3.5 PDCP handover ........................................................................................................................................ 995
7.3.5.1 Void..................................................................................................................................................... 995
ETSI
7.3.5.2 PDCP handover / Lossless handover / PDCP sequence number maintenance .................................... 995
7.3.5.3 PDCP handover / Non-lossless handover PDCP sequence number maintenance ............................... 998
7.3.5.4 PDCP handover / Lossless handover / PDCP status report to convey the information on missing
or acknowledged PDCP SDUs at handover ...................................................................................... 1001
7.3.5.5 PDCP handover / In-order delivery and duplicate elimination in the downlink ............................... 1005
7.3.6 PDCP Others ........................................................................................................................................... 1009
7.3.6.1 PDCP Discard ................................................................................................................................... 1009
8 RRC ....................................................................................................................................................1011
8.1 RRC connection management procedures .................................................................................................... 1011
8.1.1 Paging ..................................................................................................................................................... 1011
8.1.1.1 RRC / Paging for connection in idle mode........................................................................................ 1011
8.1.1.2 RRC / Paging for notification of BCCH modification in idle mode ................................................. 1014
8.1.1.3 RRC / Paging for connection in idle mode / Multiple paging records .............................................. 1018
8.1.1.4 RRC / Paging for connection in idle mode / Shared network environment ...................................... 1022
8.1.1.5 Void................................................................................................................................................... 1026
8.1.1.6 RRC / BCCH modification in connected mode ................................................................................ 1026
8.1.1.7 RRC / Paging for connection in idle mode........................................................................................ 1028
8.1.2 RRC connection establishment ............................................................................................................... 1032
8.1.2.1 RRC connection establishment / Ks=1.25/ Success .......................................................................... 1032
8.1.2.2 RRC connection establishment / Reject with wait time .................................................................... 1035
8.1.2.3 RRC connection establishment / Return to idle state after T300 timeout ......................................... 1039
8.1.2.4 Void................................................................................................................................................... 1040
8.1.2.5 RRC connection establishment / 0% access probability for MO calls, no restriction for MO
signalling ........................................................................................................................................... 1040
8.1.2.6 RRC connection establishment / Non-zero percent access probability for MO calls, no restriction
for MO signalling .............................................................................................................................. 1045
8.1.2.7 RRC connection establishment / 0% access probability for AC 0 to 9, AC 10 is barred, AC 11 to
15 are not barred, access for UE with access class in the range 11 to 15 is allowed ......................... 1050
8.1.2.8 RRC connection establishment / Range of access baring time ......................................................... 1054
8.1.2.9 RRC Connection Establishment / 0% access probability for MO calls, non-zero percent access
probability for MO signalling ........................................................................................................... 1059
8.1.2.10 Void................................................................................................................................................... 1065
8.1.2.11 RRC connection establishment of emergency call ............................................................................ 1065
8.1.2.12 RRC connection establishment of emergency call / Limited Service ............................................... 1067
8.1.2.13 RRC connection establishment / 0% access probability for MO calls, 0% access probability for
MO signalling ................................................................................................................................... 1070
8.1.2.14 RRC connection establishment / High speed flag ............................................................................. 1075
8.1.3 RRC connection release .......................................................................................................................... 1076
8.1.3.1 RRC connection release / Success .................................................................................................... 1076
8.1.3.2 Void................................................................................................................................................... 1078
8.1.3.3 Void................................................................................................................................................... 1078
8.1.3.4 RRC connection release / Redirection to another E-UTRAN frequency .......................................... 1078
8.1.3.5 RRC connection release / Success / With priority information ......................................................... 1080
8.1.3.6 RRC connection release / Redirection from E-UTRAN to UTRAN ................................................. 1085
8.1.3.6a RRC connection release / Redirection from E-UTRAN to UTRAN / Pre-redirection info .............. 1088
8.1.3.7 RRC connection release / Redirection from UTRAN to E-UTRAN ................................................. 1091
8.1.3.8 RRC connection release / Redirection from E-UTRAN to GERAN ................................................. 1098
8.1.3.9 RRC connection release / Redirection from E-UTRAN to CDMA2000-HRPD............................... 1101
8.1.3.10 RRC connection release / Redirection from E-UTRAN to CDMA2000-1xRTT .............................. 1103
8.1.3.11 RRC connection release / Redirection to another E-UTRAN band .................................................. 1105
8.1.3.11a RRC connection release / Redirection to another E-UTRAN band / Between FDD and TDD ......... 1108
8.1.3.12 RRC connection release / Success / With priority information / Inter-band ..................................... 1111
8.1.3.12a RRC connection release / Success / With priority information / Inter- band / Between FDD and
TDD .................................................................................................................................................. 1116
8.1.3.12b RRC connection release / Success / With priority information / Inter-band (Single frequency
operation in source band) .................................................................................................................. 1122
8.2 RRC connection reconfiguration .................................................................................................................. 1122
8.2.1 Radio bearer establishment ..................................................................................................................... 1122
8.2.1.1 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE to
RRC_CONNECTED / Success / Default bearer / Early bearer establishment.................................. 1122
8.2.1.2 Void................................................................................................................................................... 1124
ETSI
8.2.1.3 RRC connection reconfiguration / Radio bearer establishment / Success / Dedicated bearer ........... 1124
8.2.1.4 Void................................................................................................................................................... 1126
8.2.1.5 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_Idle to
RRC CONNECTED / Success / Latency check ................................................................................ 1126
8.2.1.6 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_Idle to
RRC CONNECTED / Success / Latency check / SecurityModeCommand and
RRCConnectionReconfiguration transmitted in the same TTI ......................................................... 1132
8.2.1.7 RRC connection reconfiguration / Radio bearer establishment / Success / SRB2 ............................ 1136
8.2.1.8 RRC connection reconfiguration / Radio bearer establishment / Success / Dedicated bearer /
ROHC configured ............................................................................................................................. 1138
8.2.2 Radio resource reconfiguration ............................................................................................................... 1142
8.2.2.1 RRC connection reconfiguration / Radio resource reconfiguration / Success ................................... 1142
8.2.2.2 RRC connection reconfiguration / SRB/DRB reconfiguration / Success .......................................... 1145
8.2.2.3 CA / RRC connection reconfiguration / SCell addition/modification/release / Success ................... 1148
8.2.2.3.1 CA / RRC connection reconfiguration / SCell addition/modification/release / Success / Intra-
band Contiguous CA ................................................................................................................... 1148
8.2.2.3.2 CA / RRC connection reconfiguration / SCell addition/modification/release / Success / Inter-
Band CA ...................................................................................................................................... 1157
8.2.2.3.3 CA / RRC connection reconfiguration / SCell addition/ modification/release / Success / Intra-
band non-contiguous CA ............................................................................................................. 1158
8.2.2.4 CA / RRC connection reconfiguration / SCell SI change / Success .................................................. 1159
8.2.2.4.1 CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band Contiguous
CA ............................................................................................................................................... 1159
8.2.2.4.2 CA / RRC connection reconfiguration / SCell SI change / Success / Inter-Band CA ................. 1164
8.2.2.4.3 CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band non-
contiguous CA ............................................................................................................................. 1164
8.2.2.5 CA / RRC connection reconfiguration / SCell addition without UL / Success ................................. 1164
8.2.2.5.1 CA / RRC connection reconfiguration / SCell addition without UL / Success / Intra-band
Contiguous CA ............................................................................................................................ 1164
8.2.2.5.2 CA / RRC connection reconfiguration / SCell addition without UL / Success / Inter-band CA . 1167
8.2.2.5.3 CA / RRC connection reconfiguration / SCell addition without UL / Success / Intra-band
non-Contiguous CA ..................................................................................................................... 1167
8.2.2.6 RRC connection reconfiguration/ UE Assistance Information ......................................................... 1167
8.2.2.6.1 RRC connection reconfiguration/ UE Assistance Information/power preference indication
setup and release .......................................................................................................................... 1167
8.2.2.6.2 RRC connection reconfiguration/ UE Assistance Information/power preference indication
release on connection re-establishment ....................................................................................... 1171
8.2.2.6.3 RRC connection reconfiguration/ UE Assistance Information/T340 running ............................. 1178
8.2.2.7 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success .................. 1181
8.2.2.7.1 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success / Intra-
band Contiguous CA ................................................................................................................... 1181
8.2.2.7.2 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success / Inter-
Band CA ...................................................................................................................................... 1187
8.2.2.7.3 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success / Intra-
band non-contiguous CA ............................................................................................................. 1187
8.2.2.8 feICIC/ RRC connection reconfiguration / SIB1 information / Success ........................................... 1187
8.2.3 Radio bearer release ................................................................................................................................ 1190
8.2.3.1 RRC connection reconfiguration / Radio bearer release / Success.................................................... 1190
8.2.4 Handover ................................................................................................................................................ 1192
8.2.4.1 RRC connection reconfiguration / Handover / Success / Dedicated preamble ................................. 1192
8.2.4.2 RRC connection reconfiguration / Handover / Success / Common preamble ................................... 1201
8.2.4.3 RRC connection reconfiguration / Handover / Success / Intra-cell / Security reconfiguration ......... 1205
8.2.4.4 RRC connection reconfiguration / Handover / Failure / Intra-cell / Security reconfiguration ......... 1209
8.2.4.5 RRC connection reconfiguration / Handover / All parameters included ........................................... 1214
8.2.4.6 RRC connection reconfiguration / Handover / Success / Inter-frequency......................................... 1220
8.2.4.7 RRC connection reconfiguration / Handover / Failure / Re-establishment successful ...................... 1224
8.2.4.8 RRC connection reconfiguration / Handover / Failure / Re-establishment failure ............................ 1238
8.2.4.9 RRC connection reconfiguration / Handover / Inter-band blind handover / Success ........................ 1245
8.2.4.10 RRC connection reconfiguration / Handover (between FDD and TDD) .......................................... 1248
8.2.4.11 Void................................................................................................................................................... 1253
8.2.4.12 RRC connection reconfiguration / Handover / Setup and release of MIMO..................................... 1253
8.2.4.13 RRC connection reconfiguration / Handover / Success (with measurement) / Inter-band ................ 1257
ETSI
8.2.4.13a RRC connection reconfiguration / Handover / Success (with measurement) / Inter-band /

Between FDD and TDD .................................................................................................................... 1262
8.2.4.14 RRC connection reconfiguration / Handover / Failure / Re-establishment successful / Inter-band .. 1270
8.2.4.14a RRC connection reconfiguration / Handover / Failure / Re-establishment successful / Inter-band /
8.2.4.15 RRC connection reconfiguration / Handover / Failure / Re-establishment failure / Inter-band ........ 1293
8.2.4.15a RRC connection reconfiguration / Handover / Failure / Re-establishment failure / Inter-band /
8.2.4.16 CA / RRC connection reconfiguration / Setup and Change of MIMO.............................................. 1312
8.2.4.16.1 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band Contiguous
CA ............................................................................................................................................... 1312
8.2.4.16.2 CA / RRC connection reconfiguration / Setup and Change of MIMO / Inter-band CA .............. 1316
8.2.4.16.3 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band non-
contiguous CA ............................................................................................................................. 1316
8.2.4.17 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell addition .... 1316
8.2.4.17.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell
addition / Intra-band Contiguous CA .......................................................................................... 1316
addition / Inter-band CA .............................................................................................................. 1324
addition / Intra-band non-contiguous CA .................................................................................... 1324
8.2.4.18 CA / RRC connection reconfiguration / Handover / Success / SCell release .................................... 1324
8.2.4.18.1 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band
Contiguous CA ............................................................................................................................ 1324
8.2.4.18.2 CA / RRC connection reconfiguration / Handover / Success / SCell release / Inter-band CA .... 1331
8.2.4.18.3 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band non-
contiguous CA ............................................................................................................................. 1331
8.2.4.19 ............ CA / RRC connection reconfiguration / Handover / Success / PCell Change / SCell no Change 1332
8.2.4.19.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change / SCell no
Change / Intra-band Contiguous CA ........................................................................................... 1332
Change / Inter-band CA............................................................................................................... 1338
Change / Intra-band non-contiguous CA ..................................................................................... 1339
8.2.4.20 CA / RRC connection reconfiguration / Handover / Success / SCell Change ................................... 1339
8.2.4.20.1 CA / RRC connection reconfiguration / Handover / Success / SCell Change / Intra-band
Contiguous CA ............................................................................................................................ 1339
8.2.4.20.2 CA / RRC connection reconfiguration / Handover / Success / SCell Change / Inter-band CA ... 1345
8.2.4.20.3 CA / RRC connection reconfiguration / Handover / Success / SCell Change Intra-band non-
contiguous CA ............................................................................................................................. 1345
8.2.4.21 CA / RRC connection reconfiguration / Handover / Success / SCell release .................................... 1345
8.2.4.21.1 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band
Contiguous CA ............................................................................................................................ 1345
8.2.4.21.2 CA / RRC connection reconfiguration / Handover / Success / SCell release / Inter-band CA .... 1352
8.2.4.21.3 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band non-
Contiguous CA ............................................................................................................................ 1352
8.2.4.22 RRC connection reconfiguration / Handover / MFBI / Target cell broadcasting information
disregarded by the UE ....................................................................................................................... 1353
8.2.4.23 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful ............. 1358
8.2.4.23.1 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful /
Intra-band Contiguous CA........................................................................................................... 1358
Inter-band CA .............................................................................................................................. 1368
Intra-band non-Contiguous CA ................................................................................................... 1369
8.3 Measurement configuration control and reporting ....................................................................................... 1370
8.3.1 Intra E-UTRAN measurements............................................................................................................... 1370
8.3.1.1 Measurement configuration control and reporting / Intra E-UTRAN measurements / Event A1 ..... 1370
8.3.1.3 Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A3 (intra and inter-frequency measurements) .................................................. 1380
ETSI
8.3.1.3a Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A3 (intra and inter-frequency measurements) / RSRQ based measurements ... 1388
8.3.1.4 Measurement configuration control and reporting / Intra E-UTRAN measurements / Periodic
reporting (intra and inter-frequency measurements) ......................................................................... 1397
simultaneous event A3 (intra-frequency measurements) .................................................................. 1407
simultaneous events A2 and A3 (inter-frequency measurements) .................................................... 1416
8.3.1.7 Measurement configuration control and reporting / Intra E-UTRAN measurements / Blacklisting . 1423
8.3.1.8 Measurement configuration control and reporting / Intra E-UTRAN measurements / Handover /
IE measurement configuration present .............................................................................................. 1432
8.3.1.9 Measurement configuration control and reporting / Intra E-UTRAN measurements / Intra-
frequency handover / IE measurement configuration not present ..................................................... 1438
8.3.1.9a Measurement configuration control and reporting / Intra Frequency measurements / Intra-
frequency handover / IE measurement configuration not present / Single Frequency operation ...... 1445
8.3.1.10 Measurement configuration control and reporting / Intra E-UTRAN measurements / Inter-
frequency handover / IE measurement configuration not present ..................................................... 1449
8.3.1.11 Measurement configuration control and reporting / Intra E-UTRAN measurements /
Continuation of the measurements after RRC connection re-establishment ..................................... 1456
8.3.1.11a Measurement configuration control and reporting / Intra Frequency measurements / Continuation
of the measurements after RRC connection re-establishment / Single Frequency operation ............ 1467
simultaneous events A3 (inter-band measurements) ......................................................................... 1475
simultaneous events A3 (inter-band measurements) / Between FDD and TDD ............................... 1483
8.3.1.13 Measurement configuration control and reporting / Intra E-UTRAN measurements / Periodic
reporting (intra-frequency and inter-band measurements) ................................................................ 1497
8.3.1.13a Measurement configuration control and reporting / Intra E-UTRAN measurements / Periodic
reporting (intra-frequency and inter-band measurements) / Between FDD and TDD ...................... 1505
simultaneous events A2 and A3 (inter-band measurements) ............................................................ 1520
simultaneous events A2 and A3 (inter-band measurements) / Between FDD and TDD................... 1528
8.3.1.15 Measurement configuration control and reporting / Intra E-UTRAN measurements / Inter-band
handover / IE measurement configuration not present ...................................................................... 1540
8.3.1.15a Measurement configuration control and reporting / Intra E-UTRAN measurements / Inter-band
handover / IE measurement configuration not present / Between FDD and TDD ............................ 1547
8.3.1.16 Measurement configuration control and reporting / Intra E-UTRAN measurements /
Continuation of the measurements after RRC connection re-establishment / Inter-band.................. 1556
8.3.1.16a Measurement configuration control and reporting / Intra E-UTRAN measurements /
Continuation of the measurements after RRC connection re-establishment / Inter-band / Between
FDD and TDD ................................................................................................................................... 1566
8.3.1.17 CA / Measurement configuration control and reporting / Intra E-UTRAN measurements / Event
A6 ...................................................................................................................................................... 1580
8.3.1.17.1 CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
Event A6 / Intra-band Contiguous CA ........................................................................................ 1580
Event A6 / Inter-band CA ............................................................................................................ 1591
Event A6 / Intra-band non-contiguous CA .................................................................................. 1592
8.3.1.18 CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
Additional measurement reporting .................................................................................................... 1593
Additional measurement reporting / Intra-band Contiguous CA ................................................. 1593
Additional measurement reporting / Inter-band CA .................................................................... 1603
Additional measurement reporting / Intra-band non-contiguous CA .......................................... 1604
8.3.1.19 eICIC/ Measurement configuration control and reporting / CSI change ........................................... 1604
8.3.1.20 eICIC / Measurement configuration control and reporting / Event A3 / RSRP and RSRQ
measurement / Neighbour ABS......................................................................................................... 1610
ETSI
8.3.1.21 eICIC / Measurement configuration control and reporting / Event A3 Handover / Neighbour
RSRP measurement configuration change ........................................................................................ 1616
8.3.1.22 CA / Measurement configuration control and reporting / Intra E-UTRAN measurements / Event
A1 / Event A2 ................................................................................................................................... 1623
Event A1 / Event A2 / Intra-band Contiguous CA ...................................................................... 1623
Event A1 / Event A2 / Inter-band CA ......................................................................................... 1631
Event A1/Event A2 / Intra-band non-contiguous CA .................................................................. 1632
8.3.1.25 Measurement configuration control and reporting / Intra E-UTRAN measurements / Event A5 /
RSRQ based measurements .............................................................................................................. 1646
8.3.1.26 Measurement configuration control and reporting / Intra E-UTRAN measurements / Event A5
(Inter-frequency measurements) ....................................................................................................... 1653
8.3.1.27 Measurement configuration control and reporting / Intra E-UTRAN measurements / Event A5
(Inter-frequency measurements) / RSRQ based measurements ........................................................ 1660
8.3.1.28 eICIC / Measurement configuration control and reporting / Event A3 / RSRP and RSRQ
measurement / Serving ABS ............................................................................................................. 1667
8.3.2 Inter-RAT measurements ........................................................................................................................ 1671
8.3.2.1 Measurement configuration control and reporting / Inter-RAT measurements / Event B2 /
Measurement of GERAN cells .......................................................................................................... 1671
8.3.2.2 Measurement configuration control and reporting / Inter-RAT measurements / Periodic reporting
/ Measurement of GERAN cells........................................................................................................ 1678
Measurement of UTRAN cells .......................................................................................................... 1685
8.3.2.3a Measurement configuration control and reporting / Inter-RAT measurements / Event B2 /
Measurement of UTRAN cells / RSRQ based measurements .......................................................... 1694
/ Measurement of UTRAN cells........................................................................................................ 1703
/ Measurements of E-UTRAN, UTRAN and GERAN cells ............................................................. 1713
8.3.2.6 Measurement configuration control and reporting / Inter-RAT measurements / Simultaneous A2
and two B2 / Measurements of E-UTRAN, UTRAN and GERAN cells .......................................... 1723
8.3.2.7 Measurement configuration control and reporting / Inter-RAT measurements / Event B2
(measurement HRPD cells) ............................................................................................................... 1731
/ Measurement of HRPD cells) ......................................................................................................... 1738
Measurement of 1xRTT cells)........................................................................................................... 1748
/ Measurement of 1xRTT cells .......................................................................................................... 1756
8.3.2.11 Measurement configuration control and reporting / Inter-RAT Measurements / Event B1 /
Measurement of UTRAN cells .......................................................................................................... 1768
8.3.3 Measurements for self optimized networks ............................................................................................ 1775
8.3.3.1 Measurement configuration control and reporting / SON / ANR / CGI reporting of E-UTRAN
cell ..................................................................................................................................................... 1775
8.3.3.2 Measurement configuration control and reporting / SON / ANR / CGI reporting of UTRAN cell .. 1787
8.3.3.3 Measurement configuration control and reporting / SON / ANR / CGI reporting of GERAN cell .. 1799
8.3.3.4 Measurement configuration control and reporting / SON / ANR / CGI reporting of HRPD cell ..... 1809
8.3.3.5 Void................................................................................................................................................... 1821
8.3.4 Measurement for CSG, Hybrid and Open cells ...................................................................................... 1821
8.3.4.1 Intra-frequency SI acquisition / CSG cell and non-CSG cell ............................................................ 1821
8.3.4.2 Inter-frequency SI acquisition / Non-member hybrid cell................................................................. 1835
8.3.4.3 Inter-frequency SI acquisition / Member hybrid cell ........................................................................ 1843
8.3.4.4 Inter-RAT SI acquisition / RRC_CONNECTED / UMTS member CSG cell .................................. 1851
8.3.4.5 Inter-frequency E-UTRAN FDD – FDD / CSG Proximity Indication .............................................. 1858
8.4 Inter-RAT handover ..................................................................................................................................... 1868
8.4.1 Inter-RAT handover E-UTRA to UTRA ................................................................................................ 1868
8.4.1.1 Void................................................................................................................................................... 1868
8.4.1.2 Inter-RAT handover / From E-UTRA to UTRA PS / Data ............................................................... 1868
ETSI
8.4.1.3 Void................................................................................................................................................... 1871

8.4.1.4 Inter-RAT handover / From E-UTRA to UTRA HSDPA / Data ...................................................... 1871
8.4.1.5 Inter-RAT Handover / from E-UTRA to UTRA(HSUPA/HSDPA) / Data ...................................... 1875
8.4.2 Inter-RAT handover UTRA to E-UTRA ................................................................................................ 1879
8.4.2.1 Void................................................................................................................................................... 1879
8.4.2.2 Inter-RAT handover / From UTRA PS to E-UTRA / Data ............................................................... 1879
8.4.2.3 Void................................................................................................................................................... 1886
8.4.2.4 Inter-RAT handover / From UTRA HSPA to E-UTRA / Data ......................................................... 1886
8.4.2.5 Void................................................................................................................................................... 1892
8.4.2.6 Void................................................................................................................................................... 1892
8.4.2.7 CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell
addition ............................................................................................................................................. 1892
8.4.2.7.1 CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell
addition / Intra-band Contiguous CA .......................................................................................... 1892
addition / Inter-band CA .............................................................................................................. 1900
addition / Intra-band non-contiguous CA .................................................................................... 1900
8.4.3 Inter-RAT mobility E-UTRA to GERAN ............................................................................................... 1900
8.4.3.1 Inter-RAT handover / From E-UTRA to GPRS / PS HO.................................................................. 1900
8.4.3.2 Inter-RAT cell change order / From E-UTRA data RRC_CONNECTED to GPRS / Without
NACC ............................................................................................................................................... 1902
8.4.3.3 Inter-RAT cell change order / From E-UTRA data to GPRS / With NACC..................................... 1907
8.4.4 Void ........................................................................................................................................................ 1912
8.4.5 Inter-RAT handover E-UTRA to HRPD ................................................................................................ 1912
8.4.5.1 Void................................................................................................................................................... 1912
8.4.5.2 Void................................................................................................................................................... 1912
8.4.5.3 Void................................................................................................................................................... 1912
8.4.5.4 Pre-registration at HRPD and inter-RAT handover / From E-UTRA to HRPD Active / Data ......... 1912
8.4.6 Inter-RAT handover HRPD to E-UTRA ................................................................................................ 1925
8.4.7 Inter-RAT mobility E-UTRA to 1xRTT ................................................................................................. 1925
8.4.7.1 Inter-RAT handover / SRVCC from E-UTRA to 1xRTT(CS) / Speech ........................................... 1925
8.4.7.2 Void................................................................................................................................................... 1938
8.4.7.3 Pre-registration at 1xRTT and inter-RAT Redirection / CS fallback from E-UTRA RRC_IDLE
to 1xRTT / MT call ........................................................................................................................... 1938
8.4.7.4 Pre-registration at 1xRTT and inter-RAT Redirection / CS fallback from E-UTRA
RRC_CONNECTED to 1xRTT / MO call ....................................................................................... 1946
8.4.7.5 Pre-registration at 1xRTT and inter-RAT Handover / Enhanced CS fallback from E-UTRA
RRC_IDLE to 1xRTT/MT call ......................................................................................................... 1953
8.4.7.6 Pre-registration at 1xRTT and inter-RAT handover / Enhanced CS fallback from E-UTRA
RRC_CONNECTED to 1xRTT/MO call .......................................................................................... 1965
8.4.7.7 Pre-registration at 1xRTT and inter-RAT handover / Enhanced CS fallback from E-UTRA
RRC_CONNECTED to e1XCSFB ECAM-based 1xRTT / MO call ................................................ 1976
RRC_CONNECTED to 1xRTT / ECAM-based MT call ................................................................. 1989
RRC_CONNECTED to 1xRTT / Extended Service Reject / MO call .............................................. 2001
8.4.7.10 Pre-registration at 1xRTT and inter-RAT Handover / Enhanced CS fallback from E-UTRA call
failure – GCSNA with Release Order ............................................................................................... 2008
8.5 RRC others ................................................................................................................................................... 2017
8.5.1 Radio link failure .................................................................................................................................... 2017
8.5.1.1 Radio link failure / RRC connection re-establishment success ......................................................... 2017
8.5.1.2 Radio link failure / T301 expiry ........................................................................................................ 2022
8.5.1.3 Radio link failure / T311 expiry ........................................................................................................ 2025
8.5.1.4 Radio link failure / RRC connection re-establishment reject ............................................................ 2027
8.5.1.5 Radio link failure / Radio link recovery while T310 is running ........................................................ 2028
8.5.1.6 Radio link failure / T311 expiry / Dedicated RLF timer ................................................................... 2030
8.5.1.7 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell ................................. 2035
8.5.1.7.1 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band
Contiguous CA ............................................................................................................................ 2035
8.5.1.7.2 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Inter-band CA . 2039
ETSI
8.5.1.7.3 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band
non-Contiguous CA ..................................................................................................................... 2039
8.5.2 Redirection to E-UTRAN ....................................................................................................................... 2039
8.5.2.1 Redirection to E-UTRAN / From UTRAN upon reception of RRC CONNECTION REJECT ....... 2039
8.5.3 Void ........................................................................................................................................................ 2042
8.5.4 UE capability transfer ............................................................................................................................. 2042
8.5.4.1 UE capability transfer / Success ........................................................................................................ 2042
8.6 Minimization of Drive Test Specific Procedures ......................................................................................... 2061
8.6.1 Immediate MDT ..................................................................................................................................... 2061
8.6.1.1 Immediate MDT / Reporting / Location information ........................................................................ 2061
8.6.1.2 Immediate MDT / Reporting / Location information / Request from eNB / Event A2 ..................... 2066
8.6.2 Logged MDT .......................................................................................................................................... 2071
8.6.2.1 Logged MDT / Intra-frequency measurement, logging and reporting .............................................. 2071
8.6.2.2 Logged MDT / Inter-frequency measurement, logging and reporting .............................................. 2080
8.6.2.3 Logged MDT / Logging and reporting / Limiting area scope ........................................................... 2086
8.6.2.3a Logged MDT / Logging and reporting / Limiting area scope / TAC list with PLMN identity ......... 2097
8.6.2.4 Logged MDT / logging and reporting / Indication of logged measurements at E-UTRA handover . 2104
8.6.2.5 Logged MDT / Logging and reporting / Indication of logged measurements at E-UTRA re-
establishment ..................................................................................................................................... 2109
8.6.2.6 Logged MDT / Release of logged MDT measurement configuration / Expire of duration timer ..... 2115
8.6.2.7 Logged MDT / Release of logged MDT measurement configuration / Reception of new logged
measurement configuration, Detach or UE power off....................................................................... 2121
8.6.2.8 Logged MDT / Maintaining logged measurement configuration / UE state transitions and
mobility ............................................................................................................................................. 2128
8.6.2.9 Logged MDT / Location information ................................................................................................ 2137
8.6.2.10 Logged MDT / Logging and reporting / Reporting at RRC connection establishment / PLMN list . 2143
8.6.2.11 Logged MDT / Logging and reporting / Reporting at intra LTE handover / PLMN list ................... 2149
8.6.2.12 Logged MDT / Logging and reporting / Reporting at RRC connection re-establishment / PLMN
list ...................................................................................................................................................... 2156
8.6.2.13 Void................................................................................................................................................... 2162
8.6.3 Inter-RAT Logged MDT ........................................................................................................................ 2163
8.6.3.1 Logged MDT / UTRAN Inter-RAT measurement, logging and reporting........................................ 2163
8.6.3.2 Logged MDT / GERAN Inter-RAT measurement, logging and reporting........................................ 2171
8.6.3.3 Logged MDT / CDMA2000 Inter-RAT measurement, logging and reporting ................................. 2178
8.6.3.4 Logged MDT / Logging and reporting / Reporting at UTRAN Inter-RAT handover / PLMN list ... 2184
8.6.4 Logged Radio Link Failure ..................................................................................................................... 2194
8.6.4.1 Radio Link Failure logging / Reporting of Intra-frequency measurements....................................... 2194
8.6.4.2 Radio Link Failure logging / Reporting of Inter-frequency measurements....................................... 2202
8.6.4.3 Radio Link Failure logging / Reporting at RRC connection establishment and reestablishment...... 2210
8.6.4.4 Radio Link Failure logging / Reporting at E-UTRA handover ......................................................... 2219
8.6.4.5 Radio Link Failure logging / Reporting of ECGI of the PCell .......................................................... 2234
8.6.4.6 Void................................................................................................................................................... 2243
8.6.4.7 Radio Link Failure logging / Location information .......................................................................... 2243
8.6.4.8 Radio Link Failure logging / Logging and reporting / Reporting at RRC connection
establishment / PLMN list ................................................................................................................. 2247
8.6.4.9 Radio Link Failure logging / Logging and reporting / Reporting at intra LTE handover / PLMN
list ...................................................................................................................................................... 2253
8.6.4.10 Radio Link Failure logging / Logging and reporting / Reporting at RRC connection re-
8.6.5 Inter-RAT Logged Radio Link Failure ................................................................................................... 2268
8.6.5.1 Radio Link Failure logging / Reporting at UTRAN Inter-RAT handover ........................................ 2268
8.6.5.1a Radio Link Failure logging / Reporting at UTRAN Inter-RAT handover / PLMN list .................... 2279
8.6.5.2 Radio Link Failure logging / Reporting at GERAN Inter-RAT handover ........................................ 2291
8.6.5.3 Radio Link Failure logging / Reporting CDMA2000 neighbour cell information ............................ 2303
8.6.5.4 Radio Link Failure logging / Reporting of selected UTRA cell........................................................ 2312
8.6.6 Logged Handover Failure ....................................................................................................................... 2322
8.6.6.1 Handover Failure logging / Reporting of Intra-frequency measurements ......................................... 2322
8.6.6.2 Handover Failure logging / Reporting of Inter-frequency measurements ......................................... 2330
8.6.6.3 Void................................................................................................................................................... 2338
8.6.6.4 Handover Failure logging / Location information............................................................................. 2338
8.6.6.5 Handover Failure logging / Logging and reporting / Reporting at RRC connection establishment
/ PLMN list........................................................................................................................................ 2342
ETSI
8.6.6.6 Handover Failure logging / Logging and reporting / Reporting at intra LTE handover / PLMN
list ...................................................................................................................................................... 2352
8.6.6.7 Handover Failure logging / Logging and reporting / Reporting at RRC connection re-
8.6.7 Inter-RAT Logged Handover Failure ..................................................................................................... 2372
8.6.7.1 Handover Failure logging / Reporting of UTRAN Inter-RAT measurements .................................. 2372
8.6.7.2 Handover Failure logging / Reporting of GERAN Inter-RAT measurements .................................. 2384
8.6.7.3 Handover Failure logging / Reporting of CDMA2000 Inter-RAT measurements ............................ 2396
8.6.7.4 Handover Failure logging / Reporting at UTRAN Inter-RAT handover / PLMN list....................... 2408
8.6.8 Connection Establishment Failure .......................................................................................................... 2421
8.6.8.1 Connection Establishment Failure logging / Logging and reporting / T300 expiry .......................... 2421
8.6.8.2 Connection Establishment Failure logging / Logging and reporting / Reporting at intra-LTE
handover ............................................................................................................................................ 2425
8.6.8.3 Connection Establishment Failure logging / Logging and reporting / Reporting at RRC
connection re-establishment .............................................................................................................. 2431
8.6.8.4 Connection Establishment Failure logging / Logging and reporting / Location Information ........... 2435
8.6.8.5 Connection Establishment Failure logging / Logging and reporting / Reporting of Intra-
frequency measurements ................................................................................................................... 2439
8.6.8.6 Connection Establishment Failure logging / Logging and reporting / Reporting of Inter-
frequency measurements ................................................................................................................... 2444
8.6.9 Inter-RAT Connection Establishment Failure ........................................................................................ 2448
8.6.9.1 Connection Establishment Failure logging / Logging and reporting / Reporting at UTRAN Inter-
RAT handover ................................................................................................................................... 2448
8.6.9.2 Connection Establishment Failure logging / Logging and reporting / Reporting of UTRAN Inter-
RAT measurements ........................................................................................................................... 2454
8.6.9.3 Connection Establishment Failure logging / Logging and reporting / Reporting of GERAN Inter-
RAT measurements ........................................................................................................................... 2459
8.6.9.4 Connection Establishment Failure logging / Logging and reporting / Reporting of CDMA2000
Inter-RAT measurements .................................................................................................................. 2463
8.6.10 Inter-RAT Immediate MDT .................................................................................................................... 2468
8.6.10.1 Inter-RAT Immediate MDT / Reporting / Location information / Event B2 .................................... 2468
8.6.11 RACH Optimisation ............................................................................................................................... 2472
8.6.11.1 RACH Optimisation .......................................................................................................................... 2472
8.7 Automatic Neighbour Relation (ANR) for UTRAN Specific Procedures.................................................... 2474
8.7.1 Inter-RAT / UTRAN ANR measurement, logging and reporting / E-UTRAN cell................................ 2474
9 EPS mobility management .................................................................................................................2479
9.1 EMM common procedures ........................................................................................................................... 2479
9.1.1 Void ........................................................................................................................................................ 2479
9.1.1.1 Void................................................................................................................................................... 2479
9.1.1.2 Void................................................................................................................................................... 2479
9.1.2 Authentication procedure ........................................................................................................................ 2479
9.1.2.1 Authentication accepted .................................................................................................................... 2479
9.1.2.2 Void................................................................................................................................................... 2482
9.1.2.3 Authentication not accepted by the network / GUTI used / Authentication reject and re-
authentication .................................................................................................................................... 2482
9.1.2.4 Authentication not accepted by the UE / MAC code failure ............................................................. 2484
9.1.2.5 Authentication not accepted by the UE / SQN failure....................................................................... 2487
9.1.2.6 Abnormal cases / Network failing the authentication check ............................................................. 2490
9.1.2.7 Authentication not accepted by the UE/ non-EPS authentication unacceptable................................ 2492
9.1.3 Security mode control procedure ............................................................................................................ 2495
9.1.3.1 NAS security mode command accepted by the UE........................................................................... 2495
9.1.3.2 NAS security mode command not accepted by the UE..................................................................... 2499
9.1.3.3 No emergency bearer service / NAS security mode command with EIA0 not accepted by the UE . 2502
9.1.4 Identification procedure .......................................................................................................................... 2505
9.1.4.1 Void................................................................................................................................................... 2505
9.1.4.2 Identification procedure / IMEI / IMEISV requested........................................................................ 2505
9.1.5 EMM information procedure .................................................................................................................. 2507
9.1.5.1 EMM information procedure ............................................................................................................ 2507
9.1.5.2 EMM information procedure not supported by the UE ..................................................................... 2509
9.2 EMM specific procedures ............................................................................................................................ 2510
9.2.1 Attach procedure ..................................................................................................................................... 2510
ETSI
9.2.1.1 Attach procedure for EPS services .................................................................................................... 2510

9.2.1.1.0 General ........................................................................................................................................ 2510
9.2.1.1.1 Attach / Success / Valid GUTI .................................................................................................... 2510
9.2.1.1.1a Attach Procedure / Success / Last visited TAI, TAI list and equivalent PLMN list handling ..... 2518
9.2.1.1.1b Attach Procedure / Success / Last visited TAI, TAI list and equivalent PLMN list handling /
Single Frequency operation ......................................................................................................... 2526
9.2.1.1.2 Attach Procedure / Success / With IMSI / GUTI reallocation ..................................................... 2527
9.2.1.1.2a Attach Procedure / AttachWithIMSI configured / Selected PLMN is neither the registered
PLMN nor in the list of equivalent PLMNs / Success ................................................................. 2530
9.2.1.1.3 Attach Procedure / Success / Request for obtaining the IPv6 address of the home agent ........... 2532
9.2.1.1.4 Attach Procedure / Success / Request for obtaining the IPv4 address of the home agent ........... 2538
9.2.1.1.5 Void ............................................................................................................................................. 2543
9.2.1.1.6 Void ............................................................................................................................................. 2543
9.2.1.1.7 Attach Procedure / Success / List of equivalent PLMNs in the ATTACH ACCEPT message ... 2543
9.2.1.1.7a Attach Procedure / Success / List of equivalent PLMNs in the ATTACH ACCEPT message /
Single Frequency operation ......................................................................................................... 2547
9.2.1.1.7b Attach / Success / native GUMMEI ............................................................................................ 2551
9.2.1.1.8 Void ............................................................................................................................................. 2555
9.2.1.1.9 Attach / Rejected / IMSI invalid .................................................................................................. 2555
9.2.1.1.10 Attach / Rejected / Illegal ME ..................................................................................................... 2558
9.2.1.1.11 Attach / Rejected / EPS services and non-EPS services not allowed .......................................... 2559
9.2.1.1.12 Attach / Rejected / EPS services not allowed .............................................................................. 2565
9.2.1.1.13 Attach / Rejected / PLMN not allowed........................................................................................ 2569
9.2.1.1.13a Attach / Rejected / PLMN not allowed / Single Frequency operation......................................... 2573
9.2.1.1.14 Attach / Rejected / Tracking area not allowed ............................................................................. 2576
9.2.1.1.15 Attach / Rejected / Roaming not allowed in this tracking area .................................................... 2581
9.2.1.1.15a Attach / Rejected / Roaming not allowed in this tracking area / Single Frequency operation ..... 2585
9.2.1.1.16 Attach / Rejected / EPS services not allowed in this PLMN ....................................................... 2588
9.2.1.1.16a Attach / Rejected / EPS services not allowed in this PLMN / Single Frequency operation ........ 2593
9.2.1.1.17 Attach / Rejected / No suitable cells in tracking area .................................................................. 2595
9.2.1.1.18 Attach / Rejected / Not authorized for this CSG ......................................................................... 2601
9.2.1.1.19 Attach / Abnormal case / Failure due to non integrity protection ................................................ 2604
9.2.1.1.20 Attach / Abnormal case / Access barred because of access class barring or NAS signalling
connection establishment rejected by the network ...................................................................... 2609
9.2.1.1.21 Attach / Abnormal case / Success after several attempts due to no network response ................ 2614
9.2.1.1.22 Attach / Abnormal case / Unsuccessful attach after 5 attempts ................................................... 2616
9.2.1.1.23 Attach / Abnormal case / Repeated rejects for network failures.................................................. 2619
9.2.1.1.24 Attach / Abnormal case / Change of cell into a new tracking area .............................................. 2623
9.2.1.1.25 Attach / Abnormal case / Mobile originated detach required ...................................................... 2627
9.2.1.1.26 Attach / Abnormal case / Detach procedure collision ................................................................. 2628
9.2.1.1.27 Attach / Abnormal case / Network reject with Extended Wait Timer ......................................... 2631
9.2.1.1.27a Attach Procedure / EAB broadcast handling / ExtendedAccessBarring configured in the UE ... 2634
9.2.1.1.28 Attach / Success / IMS ................................................................................................................ 2638
9.2.1.1.29 Attach / Rejected / IMEI not accepted ......................................................................................... 2641
9.2.1.1.30 Attach / Abnormal case / ESM failure ......................................................................................... 2643
9.2.1.2 Combined attach procedure for EPS services and non-EPS services ................................................ 2646
9.2.1.2.1 Combined attach procedure / Success / EPS and non-EPS services ............................................ 2646
9.2.1.2.1b Combined attach procedure / Success / SMS only ...................................................................... 2652
9.2.1.2.1c Combined attach procedure / Success / EPS and CS Fallback not preferred............................... 2661
9.2.1.2.1d Combined attach procedure / Success / EPS and CS Fallback not preferred/data centric UE ..... 2669
9.2.1.2.2 Combined attach procedure / Success / EPS services only / IMSI unknown in HSS .................. 2674
9.2.1.2.3 Successful combined attach procedure / EPS service only / MSC temporarily not reachable .... 2681
9.2.1.2.4 Successful combined attach procedure / EPS service only / CS domain not available................ 2690
9.2.1.2.4a Successful combined attach procedure / EPS service only / Congestion..................................... 2697
9.2.1.2.5 Combined attach / Rejected / IMSI invalid ................................................................................. 2700
9.2.1.2.6 Combined attach / Rejected / Illegal ME ..................................................................................... 2705
9.2.1.2.7 Combined attach / Rejected / EPS services and non-EPS services not allowed .......................... 2706
9.2.1.2.8 Combined attach / Rejected / EPS services not allowed.............................................................. 2707
9.2.1.2.9 Combined attach / Rejected / PLMN not allowed ....................................................................... 2710
9.2.1.2.10 Combined attach / Rejected / Tracking area not allowed ............................................................ 2714
9.2.1.2.11 Combined attach / Rejected / Roaming not allowed in this tracking area ................................... 2717
9.2.1.2.12 Combined attach / Rejected / EPS services not allowed in this PLMN ....................................... 2724
ETSI
9.2.1.2.13 Combined attach / Rejected / No suitable cells in tracking area .................................................. 2728
9.2.1.2.14 Combined attach / Rejected / Not authorized for this CSG ......................................................... 2735
9.2.1.2.15 Combined attach / Abnormal case / Handling of the EPS attach attempt counter ....................... 2738
9.2.2 Detach procedure .................................................................................................................................... 2743
9.2.2.1 UE initiated detach procedure ........................................................................................................... 2743
9.2.2.1.1 UE initiated detach / UE switched off ......................................................................................... 2743
9.2.2.1.2 UE initiated detach / USIM removed from the UE...................................................................... 2745
9.2.2.1.3 UE initiated detach / EPS capability of the UE is disabled ......................................................... 2747
9.2.2.1.4 UE initiated detach / detach for non-EPS services ...................................................................... 2752
9.2.2.1.5 Void ............................................................................................................................................. 2753
9.2.2.1.6 UE initiated detach / Abnormal case / Local detach after 5 attempts due to no network
response ....................................................................................................................................... 2753
9.2.2.1.7 UE initiated detach / Abnormal case / Detach procedure collision ............................................. 2756
9.2.2.1.8 UE initiated detach / Abnormal case / Detach and EMM common procedure collision ............. 2758
9.2.2.1.9 UE initiated detach / Abnormal case / Change of cell into a new tracking area .......................... 2761
9.2.2.1.10 UE initiated detach / Mapped security context ............................................................................ 2764
9.2.2.2 Network initiated detach procedure .................................................................................................. 2767
9.2.2.2.1 NW initiated detach / Re-attach required .................................................................................... 2767
9.2.2.2.2 NW initiated detach / IMSI detach .............................................................................................. 2769
9.2.2.2.3 to 9.2.2.2.13 Void ........................................................................................................................................... 2772
9.2.2.2.14 NW initiated detach / Abnormal case / EMM cause not included ............................................... 2772
9.2.3 Tracking area updating procedure (S1 mode only) ................................................................................. 2774
9.2.3.1 Normal and periodic tracking area updating ..................................................................................... 2774
9.2.3.1.1 Normal tracking area update / Accepted ..................................................................................... 2774
9.2.3.1.2 Void ............................................................................................................................................. 2778
9.2.3.1.3 Void ............................................................................................................................................. 2778
9.2.3.1.4 Normal tracking area update / List of equivalent PLMNs in the TRACKING AREA
UPDATE ACCEPT message....................................................................................................... 2778
9.2.3.1.5 Periodic tracking area update / Accepted .................................................................................... 2781
9.2.3.1.5a Periodic tracking area update / Accepted / Per-device timer ....................................................... 2786
9.2.3.1.6 Normal tracking area update / UE with ISR active moves to E-UTRAN .................................... 2791
9.2.3.1.7 Void ............................................................................................................................................. 2800
9.2.3.1.8 UE receives an indication that the RRC connection was released with cause "load balancing
TAU required" ............................................................................................................................. 2800
9.2.3.1.8a Normal tracking area update / low priority override ................................................................... 2803
9.2.3.1.8b Normal tracking area update / EAB broadcast handling / ExtendedAccessBarring configured
in the UE / ExtendedAccessBarring and Override_ExtendedAccessBarring configured in the
UE................................................................................................................................................ 2805
9.2.3.1.9 Normal tracking area update / Correct handling of CSG list ....................................................... 2809
9.2.3.1.9a Normal tracking area update / NAS signalling connection recovery........................................... 2814
9.2.3.1.10 Normal tracking area update / Rejected / IMSI invalid ............................................................... 2816
9.2.3.1.11 Normal tracking area update / Rejected / Illegal ME .................................................................. 2819
9.2.3.1.12 Normal tracking area update / Rejected / EPS service not allowed ............................................. 2820
9.2.3.1.13 Normal tracking area update / Rejected / UE identity cannot be derived by the network ........... 2822
9.2.3.1.14 Normal tracking area update / Rejected / UE implicitly detached ............................................... 2824
9.2.3.1.15 Normal tracking area update / Rejected / PLMN not allowed ..................................................... 2825
9.2.3.1.15a Normal tracking area update / Rejected / PLMN not allowed / Single Frequency operation ...... 2830
9.2.3.1.16 Normal tracking area update / Rejected / Tracking area not allowed .......................................... 2834
9.2.3.1.17 Normal tracking area update / Rejected / Roaming not allowed in this tracking area ................. 2838
9.2.3.1.18 Normal tracking area update / Rejected / EPS services not allowed in this PLMN .................... 2842
9.2.3.1.18a Normal tracking area update / Rejected / EPS services not allowed in this PLMN / Single
Frequency operation .................................................................................................................... 2848
9.2.3.1.19 Normal tracking area update / Rejected / No suitable cells in tracking Area .............................. 2851
9.2.3.1.20 Normal tracking area update / Rejected / Not authorized for this CSG ....................................... 2853
9.2.3.1.20a Normal tracking area update / Rejected / Congestion ................................................................. 2856
9.2.3.1.21 Void ............................................................................................................................................. 2858
9.2.3.1.22 Normal tracking area update / Abnormal case / access barred due to access class control or
NAS signalling connection establishment rejected by the network ............................................. 2858
9.2.3.1.23 Normal tracking area update / Abnormal case / Success after several attempts due to no
network response / TA belongs to TAI list and status is UPDATED / TA does not belong to
TAI list or status is not UPDATED ............................................................................................. 2863
9.2.3.1.24 Void ............................................................................................................................................. 2869
ETSI
9.2.3.1.25 Normal tracking area update / Abnormal case / Failure after 5 attempts due to no network
response ....................................................................................................................................... 2869
9.2.3.1.26 Normal tracking area update / Abnormal case / TRACKING AREA UPDATE REJECT ......... 2875
9.2.3.1.27 Normal tracking area update / Abnormal case / Change of cell into a new tracking area ........... 2879
9.2.3.1.28 Normal tracking area update / Abnormal case / Tracking area updating and detach procedure
collision ....................................................................................................................................... 2882
9.2.3.2 Combined tracking area updating ..................................................................................................... 2884
9.2.3.2.1 Combined tracking area update / Successful ............................................................................... 2884
9.2.3.2.1a Combined tracking area update / Successful / Check of last visited TAI and handling of TAI
list, LAI and TMSI ...................................................................................................................... 2889
9.2.3.2.1b Combined tracking area update / Success / SMS only ................................................................ 2899
9.2.3.2.1c Combined tracking area update / Success / CS Fallback not preferred ....................................... 2906
9.2.3.2.2 Combined tracking area update / Successful for EPS services only / IMSI unknown in HSS .... 2910
9.2.3.2.3 Combined tracking area update / Successful for EPS services only / MSC temporarily not
reachable ...................................................................................................................................... 2913
9.2.3.2.4 Combined tracking area update / Successful for EPS services only / CS domain not available.. 2920
9.2.3.2.4a Combined tracking area update / Successful for EPS services only / Congestion....................... 2922
9.2.3.2.5 Combined tracking area update / Rejected / IMSI invalid ........................................................... 2925
9.2.3.2.6 Combined tracking area update / Rejected / Illegal ME .............................................................. 2928
9.2.3.2.7 Combined tracking area update / Rejected / EPS services and non-EPS services not allowed ... 2929
9.2.3.2.8 Combined tracking area update / Rejected / EPS services not allowed ....................................... 2929
9.2.3.2.9 Combined tracking area update / Rejected / UE identity cannot be derived by the network ....... 2933
9.2.3.2.10 Combined tracking area update / Rejected / UE implicitly detached .......................................... 2938
9.2.3.2.11 Combined tracking area update / Rejected / PLMN not allowed ................................................ 2940
9.2.3.2.12 Combined tracking area update / Rejected / Tracking area not allowed...................................... 2945
9.2.3.2.13 Combined tracking area update / Rejected / Roaming not allowed in this tracking area............. 2949
9.2.3.2.14 Combined tracking area update / Rejected / EPS services not allowed in the PLMN ................. 2953
9.2.3.2.15 Combined tracking area update / Rejected / No suitable cells in tracking area ........................... 2957
9.2.3.2.16 Combined tracking area update / Rejected / Not authorized for this CSG .................................. 2959
9.2.3.2.17 Combined tracking area update / Abnormal case / handling of the EPS tracking area updating
attempt counter ............................................................................................................................ 2962
9.2.3.3 Iu mode to S1 mode inter-system change in idle mode ..................................................................... 2966
9.2.3.3.1 First Iu mode to S1 mode inter-system change after attach ......................................................... 2966
9.2.3.3.2 Iu mode to S1 mode intersystem change / ISR is active / Expiry of T3312 in E-UTRAN or
T3412 in UTRAN and further intersystem change ...................................................................... 2977
9.2.3.3.3 Iu mode to S1 mode intersystem change / Periodic TAU and RAU/ ISR activated, T3423
expired ......................................................................................................................................... 2986
9.2.3.3.4 First S1 mode to Iu mode inter-system change after attach ......................................................... 2992
9.2.3.3.5 Periodic routing area update ........................................................................................................ 3009
9.2.3.3.5a Periodic Location Update ............................................................................................................ 3017
9.2.3.3.6 Void ............................................................................................................................................. 3020
9.2.3.4 A/Gb mode to S1 mode inter-system change .................................................................................... 3020
9.2.3.4.1 TAU/RAU procedure for inter-system cell reselection between A/Gb and S1 modes ................ 3020
9.3 EMM connection management procedures (S1 mode only) ........................................................................ 3033
9.3.1 Service request procedure ....................................................................................................................... 3033
9.3.1.1 Service request initiated by UE for user data .................................................................................... 3033
9.3.1.2 Void................................................................................................................................................... 3036
9.3.1.3 Service request / Mobile originating CS fallback.............................................................................. 3036
9.3.1.4 Service request / Rejected / IMSI invalid .......................................................................................... 3039
9.3.1.5 Service request / Rejected / Illegal ME ............................................................................................. 3045
9.3.1.6 Service request / Rejected / EPS services not allowed ...................................................................... 3047
9.3.1.7 Service request / Rejected / UE identity cannot be derived by the network ...................................... 3052
9.3.1.7a Service request / Rejected / UE implicitly detached ......................................................................... 3054
9.3.1.8 to 9.3.1.12 Void ................................................................................................................................................. 3056
9.3.1.12a Extended service request / Rejected / CS domain temporarily not available .................................... 3056
9.3.1.13 Void................................................................................................................................................... 3058
9.3.1.14 Void................................................................................................................................................... 3058
9.3.1.15 Void................................................................................................................................................... 3058
9.3.1.16 Service request / Abnormal case / Switch off ................................................................................... 3058
9.3.1.17 Service request / Abnormal case / Procedure collision ..................................................................... 3059
9.3.1.18 Service Request / Rejected / Not authorized for this CSG ................................................................ 3062
9.3.2 Paging procedure .................................................................................................................................... 3065
ETSI
9.3.2.1 Paging procedure............................................................................................................................... 3065

9.3.2.2 Paging for CS fallback / Idle mode ................................................................................................... 3066
9.3.2.2a Paging for CS fallback / Connected mode ........................................................................................ 3069
9.4 NAS Security................................................................................................................................................ 3072
9.4.1 Integrity protection / Correct functionality of EPS NAS integrity algorithm / SNOW3G...................... 3072
9.4.2 Integrity protection / Correct functionality of EPS NAS integrity algorithm / AES ............................... 3075
9.4.3 Ciphering and deciphering / Correct functionality of EPS NAS encryption algorithm / SNOW3G ...... 3075
9.4.4 Ciphering and deciphering / Correct functionality of EPS NAS encryption algorithm / AES................ 3079
9.4.5 Integrity protection / Correct functionality of EPS NAS integrity algorithm / ZUC .............................. 3079
9.4.6 Ciphering and deciphering / Correct functionality of EPS NAS encryption algorithm / ZUC ............... 3080
10 EPS session management ...................................................................................................................3081
10.1 Void .............................................................................................................................................................. 3081
10.2 Dedicated EPS bearer context activation...................................................................................................... 3081
10.2.1 Dedicated EPS bearer context activation / Success ................................................................................ 3081
10.3 EPS bearer context modification .................................................................................................................. 3083
10.3.1 EPS bearer context modification / Success ............................................................................................. 3083
10.4 EPS bearer context deactivation ................................................................................................................... 3087
10.4.1 EPS bearer context deactivation / Success .............................................................................................. 3087
10.4.2 EPS bearer context deactivation / Re-establishment ............................................................................... 3100
10.5 UE requested PDN connectivity................................................................................................................... 3103
10.5.1 UE requested PDN connectivity accepted by the network ..................................................................... 3103
10.5.1a UE requested PDN connectivity accepted / Dual priority / T3396 override ........................................... 3110
10.5.1b UE requested PDN connectivity accepted / Dual priority / T3346 override ........................................... 3115
10.5.2 Void ........................................................................................................................................................ 3118
10.5.3 UE requested PDN connectivity not accepted ........................................................................................ 3118
10.5.4 UE requested PDN connectivity not accepted / Network reject with Extended Wait Timer .................. 3123
10.6 UE requested PDN disconnect ..................................................................................................................... 3128
10.6.1 UE requested PDN disconnect procedure accepted by the network ....................................................... 3128
10.6.2 Void ........................................................................................................................................................ 3131
10.7 UE requested bearer resource allocation ...................................................................................................... 3131
10.7.1 UE requested bearer resource allocation accepted by the network / New EPS bearer context ............... 3131
10.7.2 UE requested bearer resource allocation accepted by the network / Existing EPS bearer context ......... 3133
10.7.3 UE requested bearer resource allocation not accepted by the network ................................................... 3135
10.7.4 UE requested bearer resource allocation / Expiry of timer T3480 .......................................................... 3138
10.7.5 UE requested bearer resource allocation / BEARER RESOURCE ALLOCATION REJECT message
including cause #43 "invalid EPS bearer identity" ................................................................................. 3140
10.8 UE requested bearer resource modification.................................................................................................. 3143
10.8.1 UE requested bearer resource modification accepted by the network / New EPS bearer context .......... 3143
10.8.2 UE requested bearer resource modification accepted by the network / Existing EPS bearer context ..... 3145
10.8.3 UE requested bearer resource modification not accepted by the network .............................................. 3147
10.8.4 UE requested bearer resource modification / Cause #36 "regular deactivation" .................................... 3150
10.8.5 UE requested bearer resource modification / BEARER RESOURCE MODIFICATION REJECT
message including cause #43 "invalid EPS bearer identity" ................................................................... 3153
10.8.6 UE requested bearer resource modification / Collision of a UE requested bearer resource
modification procedure and EPS bearer context deactivation procedure................................................ 3156
10.8.7 UE requested bearer resource modification / Expiry of timer T3481 ..................................................... 3158
10.8.8 UE requested bearer resource modification / Dual priority / low priority override ................................ 3161
10.9 UE routing of uplink packets ........................................................................................................................ 3164
10.9.1 UE routing of uplinks packets................................................................................................................. 3164
11 General tests .......................................................................................................................................3187
11.1 SMS over SGs .............................................................................................................................................. 3187
11.1.1 MT-SMS over SGs / Idle mode .............................................................................................................. 3187
11.1.2 MT-SMS over SGs / Active mode .......................................................................................................... 3189
11.1.3 MO-SMS over SGs / Idle mode .............................................................................................................. 3192
11.1.4 MO-SMS over SGs / Active mode ......................................................................................................... 3195
11.1.5 Multiple MO-SMS over SGs / Idle mode ............................................................................................... 3198
11.1.6 Multiple MO-SMS over SGs / Active mode ........................................................................................... 3203
11.2 Emergency calls over IMS ........................................................................................................................... 3207
11.2.0 General.................................................................................................................................................... 3207
ETSI
11.2.1 Emergency bearer services / Normal cell / NORMAL-SERVICE / Local Emergency Numbers List
sent in the Attach / PDN connect new emergency EPS bearer context / Service request / Emergency
PDN disconnect ...................................................................................................................................... 3207
11.2.2 Emergency bearer services / Normal cell / LIMITED-SERVICE / Attach / PDN connect .................... 3212
11.2.3 Emergency bearer services / CSG cell / LIMITED-SERVICE / Attach / Security mode control
procedure without prior authentication / PDN connect / Service request / PDN disconnect / Detach
upon UE switched off / Temporary storage of EMM information.......................................................... 3215
11.2.4 Emergency bearer services / Normal cell / NO-IMSI / Attach / No EPS security context / PDN
connect / Service request / Timer T3412 expires .................................................................................... 3221
11.2.5 Emergency bearer services / Normal cell / NORMAL-SERVICE / Local Emergency Numbers List
NOT sent in the Attach / PDN connect new emergency EPS bearer context / Authentication SQN
code failure - MME aborts authentication continues using current security context / Service request ... 3228
11.2.6 Handling of Local Emergency Numbers List provided during Attach and Normal tracking area
update procedures ................................................................................................................................... 3234
11.2.7 UE has PDN connection for emergency bearer services / Normal tracking area update / Accepted /
Local Emergency Numbers List is not sent by the network / Handling of the lists of forbidden
tracking areas .......................................................................................................................................... 3241
11.2.8 Attach for emergency bearer services / Rejected / No suitable cells in tracking area / Emergency call
using the CS domain / UTRA or GERAN .............................................................................................. 3248
11.2.8a Attach for emergency bearer services / Rejected / No suitable cells in tracking area / Emergency call
using the CS domain / CDMA 2000 1xRTT........................................................................................... 3253
11.2.9 Void ........................................................................................................................................................ 3255
11.2.10 LIMITED-SERVICE / EPS does not support IMS Emergency / Emergency call using the CS
domain .................................................................................................................................................... 3255
11.2.11 LIMITED-SERVICE / Inter-system mobility / E-UTRA to UTRA CS / SRVCC Emergency Call
Handover to UTRAN .............................................................................................................................. 3259
12 E-UTRA radio bearer tests .................................................................................................................3269
12.1 General ......................................................................................................................................................... 3269
12.1.0 Definition of radio bearer combinations ................................................................................................. 3269
12.1.1 Generic E-UTRA radio bearer test procedure / MIMO not configured .................................................. 3269
12.1.2 Generic E-UTRA radio bearer test procedure / MIMO configured ........................................................ 3271
12.2 MIMO not configured .................................................................................................................................. 3272
12.2.1 Data transfer of E-UTRA radio bearer combinations 1, 3, 6 and 9......................................................... 3272
12.2.2 Data transfer of E-UTRA radio bearer combinations 2,4,7 and 10......................................................... 3273
12.2.3 Data transfer of E-UTRA radio bearer combinations 5,8,11 and 12....................................................... 3274
12.2.4 Data transfer of E-UTRA radio bearer combination 13 .......................................................................... 3275
12.3 MIMO configured ........................................................................................................................................ 3276
12.3.1 Data transfer of E-UTRA radio bearer combinations 1,3,6 and 9 / MIMO ............................................ 3276
12.3.2 Data transfer of E-UTRA radio bearer combinations 2,4,7 and 10 / MIMO .......................................... 3277
12.3.3 Data transfer of E-UTRA radio bearer combinations 5,8,11 and 12 / MIMO ........................................ 3278
12.3.4 Data transfer of E-UTRA radio bearer combination 13 / MIMO............................................................ 3279
13 Multi layer Procedures .......................................................................................................................3280
13.1 Call setup ...................................................................................................................................................... 3280
13.1.1 Activation and deactivation of additional data radio bearer in E-UTRA ................................................ 3280
13.1.2 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection / MO call .............. 3284
13.1.2a Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection including System
Information / MO call ............................................................................................................................. 3287
13.1.3 Call setup from E-UTRAN RRC_CONNECTED / CS fallback to UTRAN with Redirection / MT
call .......................................................................................................................................................... 3294
13.1.4 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with Handover / MT call ................ 3303
13.1.5 Call setup from E-UTRAN RRC_CONNECTED / CS fallback to UTRAN with handover / MO call .. 3314
13.1.6 Void ........................................................................................................................................................ 3318
13.1.7 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with redirection / MT call....................... 3318
13.1.8 Call setup from E-UTRA RRC_CONNECTED/ CS fallback to GSM with Redirection / MO call ....... 3329
13.1.9 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with CCO without NACC / MO call ...... 3335
13.1.10 Call setup from E-UTRA RRC_CONNECTED / CS fallback to GSM with CCO without NACC /
MT call ................................................................................................................................................... 3339
13.1.11 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with PSHO / EDTM not supported /
MT call ................................................................................................................................................... 3347
ETSI
13.1.12 Call setup from E-UTRA RRC_CONNECTED / CS fallback to GSM with PSHO / EDTM not
supported / MO call ................................................................................................................................ 3357
13.1.13 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with PSHO / EDTM supported / MT
call .......................................................................................................................................................... 3363
13.1.14 Void ........................................................................................................................................................ 3374
13.1.15 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection / MT call /
UTRAN cell is barred ............................................................................................................................. 3374
13.1.16 Emergency call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with handover............... 3378
13.1.17 Call setup from E-UTRAN RRC_IDLE / mobile originating 1xCS fallback emergency call to
1xRTT ..................................................................................................................................................... 3382
13.1.18 Call setup from E-UTRAN RRC_IDLE / mobile originating enhanced 1xCS fallback emergency call
to 1xRTT................................................................................................................................................. 3387
13.2 RRC connection reconfiguration .................................................................................................................. 3399
13.2.1 RRC connection reconfiguration / E-UTRA to E-UTRA ....................................................................... 3399
13.3 Connection re-establishment ........................................................................................................................ 3403
13.3.1 Intra-system connection re-establishment ............................................................................................... 3403
13.3.1.1 Intra-system connection re-establishment / Radio link recovery while T310 is running .................. 3403
13.3.1.2 Intra-system connection re-establishment / Re-establishment of a new connection when further
data is to be transferred ..................................................................................................................... 3405
13.3.1.3 RRC connection reconfiguration / Full configuration / DRB establishment ..................................... 3407
13.3.2 Inter-system connection re-establishment ............................................................................................... 3412
13.3.2.1 Inter-system connection re-establishment / E-UTRAN to UTRAN / Further data are to be
transferred ......................................................................................................................................... 3412
13.3.2.2 Inter-system connection re-establishment / E-UTRAN to GPRS / Further data are to be
transferred ......................................................................................................................................... 3415
13.4 Mobility ........................................................................................................................................................ 3417
13.4.1 Intra-system mobility .............................................................................................................................. 3417
13.4.1.1 Void................................................................................................................................................... 3417
13.4.1.2 Inter-frequency mobility / E-UTRA to E-UTRA packet ................................................................... 3417
13.4.1.3 Intra-system mobility / E-UTRA FDD to E-UTRA TDD to E-UTRA FDD packet ......................... 3421
13.4.1.4 Inter-band mobility / E-UTRA to E-UTRA packet ........................................................................... 3428
13.4.1.5 RRC connection reconfiguration / Handover/ Full configuration / DRB establishment ................... 3432
13.4.2 Inter-system mobility packet................................................................................................................... 3437
13.4.2.1 Inter-system mobility / E-UTRA to UTRA packet ........................................................................... 3437
13.4.2.2 Inter-system mobility / E-UTRAN to GPRS packet ......................................................................... 3447
13.4.2.3 Void................................................................................................................................................... 3459
13.4.2.4 Inter-system mobility / Service based redirection from UTRA to E-UTRA ..................................... 3459
13.4.2.5 Inter-system mobility/Service based redirection from GSM/GPRS to E-UTRA .............................. 3463
13.4.2.6 Inter-RAT PS Handover / from GPRS Packet_transfer to E-UTRA cell .......................................... 3466
13.4.2.7 Inter-RAT PS Handover / Synchronised / From GPRS Packet_transfer to E-UTRA cell (CCN
mode) ................................................................................................................................................ 3470
13.4.2.8 Inter-RAT PS Handover / Synchronised / From GPRS Packet_transfer to E-UTRA cell (NC2
mode) ................................................................................................................................................ 3475
13.4.3 Inter-system mobility voice .................................................................................................................... 3481
13.4.3.0 General .............................................................................................................................................. 3481
13.4.3.1 Inter-system mobility / E-UTRA voice to UTRA CS voice / SRVCC.............................................. 3481
13.4.3.2 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / SRVCC ........ 3490
13.4.3.3 Inter-system mobility / E-UTRA voice to GSM CS voice / SRVCC ................................................ 3501
13.4.3.4 Inter-system mobility / E-UTRA voice to UTRA CS voice / Unsuccessful case / Retry on old cell
/ SRVCC ........................................................................................................................................... 3509
13.4.3.5 Inter-system mobility / E-UTRA voice to GSM CS voice / Unsuccessful case / Retry on old cell /
SRVCC ............................................................................................................................................. 3520
13.4.3.6 Inter-system mobility / E-UTRA PS voice + PS Data / HO cancelled / Notification procedure /
SRVCC ............................................................................................................................................. 3533
13.4.3.7 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call ............................ 3539
13.4.3.8 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call / Forked
responses ........................................................................................................................................... 3550
13.4.3.9 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call / SRVCC HO
failure ................................................................................................................................................ 3562
13.4.3.10 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MT call ............................ 3572
13.4.3.11 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MT call / SRVCC HO
failure ................................................................................................................................................ 3583
ETSI
13.4.3.12 Void................................................................................................................................................... 3593

13.4.3.13 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MT call / SRVCC HO
cancelled / User answers in PS domain ............................................................................................. 3593
13.4.3.14 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / aSRVCC /
MO call ............................................................................................................................................. 3600
MO call / SRVCC HO cancelled....................................................................................................... 3612
MT call .............................................................................................................................................. 3620
13.4.3.17 Void................................................................................................................................................... 3633
13.4.3.18 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / bSRVCC /
MO call ............................................................................................................................................. 3634
13.4.3.19 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / bSRVCC /
MO call / SRVCC HO cancelled....................................................................................................... 3643
13.4.3.20 Inter-system mobility / E-UTRA voice to UTRA CS voice / bSRVCC / MO call / SRVCC HO
failure ................................................................................................................................................ 3652
13.4.3.21 Inter-system mobility / E-UTRA PS voice to GSM CS voice / bSRVCC / MO call ........................ 3662
13.4.3.22 Inter-system mobility / E-UTRA PS voice to GSM CS voice / bSRVCC / MO call / SRVCC HO
cancelled ........................................................................................................................................... 3672
13.4.3.23 Inter-system mobility / E-UTRA voice to GSM CS voice / bSRVCC / MO call / SRVCC HO
failure ................................................................................................................................................ 3681
13.4.3.24 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MO call .............................. 3692
13.4.3.25 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MO call / Forked
responses ........................................................................................................................................... 3702
13.4.3.26 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MO call / SRVCC HO
failure ................................................................................................................................................ 3714
13.4.3.27 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MT call .............................. 3725
13.4.3.28 Inter-system mobility / E-UTRA voice to GERAN CS voice / aSRVCC / MT call / SRVCC HO
failure ................................................................................................................................................ 3735
13.4.3.29 Void................................................................................................................................................... 3744
13.4.3.30 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MT call / SRVCC HO
cancelled / User answers in PS domain ............................................................................................. 3744
13.4.4 Inter-system session management........................................................................................................... 3752
13.4.4.1 Pre-registration at 1xRTT and Cell reselection / 1x Zone Registration ............................................ 3752
13.4.4.2 Pre-registration at 1xRTT and Cell reselection / 1x Ordered Registration........................................ 3759
13.4.4.3 Inter-system session management / Multiple PDN connection establishment in eHRPD pre-
registration state ................................................................................................................................ 3763
13.4.4.4 Inter-system session management / Pre-registration at HRPD and Cell reselection / HRPD Zone
Registration ....................................................................................................................................... 3770
13.4.4.5 Pre-Registration at 1xRTT / Power Down Registration .................................................................... 3778
14 ETWS .................................................................................................................................................3784
14.1 ETWS reception in RRC_IDLE state / Duplicate detection ......................................................................... 3784
14.2 ETWS reception in RRC_CONNECTED state / Duplicate detection .......................................................... 3788
14.3 Void .............................................................................................................................................................. 3793
15 Mobility management based on DSMIPv6 (Dual-Stack Mobile IPv6) ..............................................3793
15.1 Discovery of the home agent via DNS ......................................................................................................... 3793
15.2 Discovery of the Home Agent via DHCP .................................................................................................... 3795
15.3 Void .............................................................................................................................................................. 3798
15.4 Security association establishment with Home Agent reallocation procedure ............................................. 3798
15.5 Security association establishment without home agent reallocation procedure .......................................... 3809
15.6 Registration of a new IPv6 CoA (Binding Update/Acknowledgment procedure in IPv6 network) ............. 3823
15.7 Registration of a new IPv4 CoA (Binding Update/Acknowledgment procedure in IPv4 network) ............. 3826
15.8 Re-registration of IPv6 CoA......................................................................................................................... 3829
15.9 Re-registration of IPv4 CoA......................................................................................................................... 3830
15.10 Return to home link ...................................................................................................................................... 3831
15.11 Dual-Stack Mobile IPv6 detach in IPv6 network ......................................................................................... 3833
15.12 Dual-Stack Mobile IPv6 detach in IPv4 network ......................................................................................... 3835
16 Home (e)NB related ...........................................................................................................................3838
16.1 UE Idle Mode Operations............................................................................................................................. 3838
16.1.1 Cell Selection and Reselection................................................................................................................ 3838
ETSI
16.1.1.1 Void................................................................................................................................................... 3838

16.1.1.2 Void................................................................................................................................................... 3838
17 MBMS in LTE ...................................................................................................................................3838
17.1 MCCH Information Acquisition................................................................................................................... 3838
17.1.1 MCCH information acquisition/ UE is switched on ............................................................................... 3838
17.1.2 MCCH information acquisition/ cell reselection to a cell in a new MBSFN area .................................. 3840
17.1.3 MCCH information acquisition/ UE handover to a cell in a new MBSFN area ..................................... 3843
17.1.4 MCCH information acquisition/ UE is receiving an MBMS service ...................................................... 3848
17.1.5 MCCH information acquisition/ UE is not receiving MBMS data ......................................................... 3852
17.2 MBMS Data Reception ................................................................................................................................ 3854
17.2.1 UE Acquire the MBMS data based on the SIB13 and MCCH message /MCCH and MTCH are on
the same MCH ........................................................................................................................................ 3854
17.2.2 UE Acquire the MBMS data based on the SIB13 and MCCH message /MCCH and MTCH are on
different MCHs ....................................................................................................................................... 3859
17.2.3 UE receives the MBMS data when this data is in the beginning of the MSP ......................................... 3864
17.2.4 Reception of PDCCH DCI format 0 and PHICH in MBSFN subframes ................................................ 3869
17.3 MBMS Counting Procedure ......................................................................................................................... 3873
17.3.1 MBMS Counting / UE not receiving MBMS service ............................................................................. 3873
17.3.2 MBMS Counting / UE receiving MBMS service ................................................................................... 3877
17.4 MBMS Service Continuity ........................................................................................................................... 3883
17.4.1 Cell reselection to intra-frequency cell to continue MBMS service reception........................................ 3883
17.4.1a Cell reselection to intra-frequency cell to continue MBMS service reception / Single Frequency
operation (inter-band neighbouring cell) ................................................................................................ 3887
17.4.2 Cell reselection to inter- frequency cell to start MBMS service reception ............................................. 3888
17.4.2a Cell reselection to inter- band cell to start MBMS service reception ..................................................... 3891
17.4.3 Handover to inter-frequency cell to start MBMS service reception ....................................................... 3892
17.4.3a Handover to inter-band cell to start MBMS service reception................................................................ 3899
17.4.4 Handover to intra-frequency cell to continue MBMS service reception................................................. 3900
17.4.5 Conditional retransmission of MBMS Interest Indication after handover .............................................. 3904
17.4.6 MBMS Interest Indication retransmission after returning from cell not broadcasting SIB15 ................ 3909
17.4.7 MBMS Interest Indication after Radio Link Failure ............................................................................... 3915
17.4.8 Continued MBMS service reception after E-UTRAN release of unicast bearer..................................... 3918
17.4.9 CA / Start MBMS reception on Non-Serving Cell / Continue MBMS reception on SCell after SCell
addition ................................................................................................................................................... 3921
17.4.9.1 CA / Start MBMS reception on Non-Serving Cell / Continue MBMS reception on SCell after
SCell addition / Intra-band Contiguous CA ...................................................................................... 3921
17.4.9.2 CA / Start MBMS reception on Non-Serving Cell / Continue MBMS reception on SCell after
SCell addition / Inter-band CA.......................................................................................................... 3929
17.4.10 CA / Start MBMS reception on SCell / Continue MBMS reception on Non-Serving after SCell
release ..................................................................................................................................................... 3930
17.4.10.1 CA / Start MBMS reception on SCell / Continue MBMS reception on Non-Serving after SCell
release / Intra-band Contiguous CA .................................................................................................. 3930
17.4.10.2 CA / Start MBMS reception on SCell / Continue MBMS reception on Non-Serving after SCell
release / Inter-band CA ..................................................................................................................... 3937
17.4.11 CA / Start MBMS reception on PCell / Continue MBMS reception after swap of SCell and PCell ...... 3938
17.4.11.1 CA / Start MBMS reception on PCell / Continue MBMS reception after swap of SCell and PCell
/ Intra-band Contiguous CA .............................................................................................................. 3938
17.4.11.2 CA / Start MBMS reception on PCell / Continue MBMS reception after swap of SCell and PCell
/ Inter-band CA ................................................................................................................................. 3951
18 PWS.............................................................................................................................................................. 3952
18.1 CMAS on LTE ............................................................................................................................................. 3952
18.1.1 PWS reception in RRC_IDLE state / Duplicate detection ...................................................................... 3952
18.1.2 PWS reception in RRC_CONNECTED state / Duplicate detection ....................................................... 3957
18.1.3 PWS reception in RRC_CONNECTED State/Power On ....................................................................... 3962
Annex A (informative): Change history ...........................................................................................3968

History ..........................................................................................................................................................4051
ETSI
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document is the first part of a multi-part conformance specification. 3GPP TS 36.523-2 [18] contains a pro-
forma for the Implementation Conformance Statement (ICS) and an applicability table, indicating the release from
which each test case is applicable. 3GPP TS 36.523-3 [19] contains a TTCN-3 design frame work, test model and Test
Suites (the detailed test specifications in TTCN-3).
For at least a minimum set of services, the prose descriptions of test cases will have a matching detailed test case
implemented in TTCN [19].
The present document may contain descriptions of tests for additional services, but these tests may not have matching
TTCN test cases.
The present document will not contain any tests on the USIM, or the interface between the UE and the USIM. These
tests are documented elsewhere.
ETSI
1 Scope
The present document specifies the protocol conformance testing for the 3rd Generation E-UTRAN User Equipment
(UE).
This is the first part of a multi-part test specification. The following information can be found in this part:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The following information relevant to testing could be found in accompanying specifications:
- the default setting of the test parameters [18];
- the applicability of each test case [19].
A detailed description of the expected sequence of messages could be found in the 3rd part of this test specification.
The Implementation Conformance Statement (ICS) pro-forma could be found in the 2nd part of the present document.
The present document is valid for UE implemented according to 3GPP releases starting from Release 8 up to the
Release indicated on the cover page of the present document.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[3] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[4] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols;
Stage 3".
[5] 3GPP TS 34.108: "Common Test Environments for User Equipment (UE) Conformance Testing".
[6] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions".
[7] 3GPP TS 34.123-1: "User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification".
[8] 3GPP TS 34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
ETSI
[9] 3GPP TS 34.123-3: "User Equipment (UE) conformance specification; Part 3: Abstract Test Suites
(ATS)".
[10] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[11] 3GPP TS 36.302: "Services provided by the physical layer for E-UTRA".
[12] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE)
Procedures in idle mode ".
[13] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE)
Radio Access capabilities ".
[14] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access
Control (MAC) protocol specification".
[15] 3GPP TS 36.322: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link Control
(RLC) protocol specification".
[16] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA) Packet Data
Convergence Protocol (PDCP) specification".
[17] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource
Control (RRC) Protocol Specification".
Terrestrial Radio Access (E-UTRAN); Common Test Environments for User Equipment (UE)
Conformance Testing".
[19] 3GPP TS 36.523-2: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance
specification; Part 2: Implementation Conformance Statement (ICS) proforma specification".
[20] 3GPP TS 36.523-3: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance
specification; Part 3: Abstract Test Suites (ATS)".
[21] 3GPP TR 24.801: "3GPP System Architecture Evolution; CT WG1 Aspects".
[22] 3GPP TS 23.401: "3GPP System Architecture Evolution; GPRS enhancements for E-UTRAN
access".
[23] 3GPP TS 51.010-1: "Mobile Station (MS) conformance specification; Part 1: Conformance
specification".
[24] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework".
Terrestrial Radio Access Network (E-UTRAN); Special conformance testing functions for User
Equipment (UE)".
[26] 3GPP TS 33.102: "3G Security; Security architecture"
[27] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[28] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".
[29] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
channel coding".
[30] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures"
ETSI
[31] 3GPP TS 36.101: “Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception”
[32] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".
[33] 3GPP2 A.S0008-C v4.0: "Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
Radio Access Network Interfaces with Session Control in the Access Network"
[34] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management"
[35] 3GPP TS 34.229-1: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE)
conformance specification; Part 1: Protocol conformance specification ".
[36] 3GPP TS 45.008: "Technical Specification Group GSM/EDGE Radio Access Network; Radio
subsystem link control"
[37] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station
System (BSS) interface; Radio Link Control (RLC) / Medium Access Control (MAC) protocol"
[38] 3GPP TS 44.018: "Technical Specification Group GSM/EDGE Radio Access Network; Mobile
radio interface layer 3 specification; Radio Resource Control Protocol"
[39] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive
mode"
[40] 3GPP TS 25.133: "Requirements for support of Radio Resource Management (FDD)"
[41] 3GPP TS 25.123: "Requirements for support of Radio Resource Management (TDD)"
[42] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected
Mode"
[43] 3GPP TS 25.367: "Mobility Procedures for Home NodeB; Overall Description; Stage 2"
[44] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and
Modulation"
[45] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)"
[46] 3GPP TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6; Stage 3"
[47] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[48] 3GPP2 C.S0005- Fv1.0: "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread
Spectrum Systems - Release F".
[49] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)"
[50] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs"
3 Definitions, symbols and abbreviations

3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
Floor: Floor(x) is the largest integer smaller than or equal to x.
Ceil: Ceil (x) is the smallest integer larger than or equal to x.
ETSI
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
ENB Evolved Node B

FDD Frequency Division Duplex
FFS For Further Study
ICS Implementation Conformance Statement
ROHC RObust Header Compression
USD User Service Description
4 Overview
4.1 Test methodology
4.1.1 Testing of optional functions and procedures
Any function or procedure which is optional, as indicated in the present document, may be subject to a conformance test
if it is implemented in the UE.
A declaration by the apparatus supplier (ICS) is used to determine whether an optional function/procedure has been
implemented.
4.1.2 Test interfaces and facilities

Detailed descriptions of the UE test interfaces and special facilities for testing is provided in 3GPP TS 36.509 [25].
4.2 Implicit testing

For some 3GPP signalling and protocol features conformance is not verified explicitly in the present document. This
does not imply that correct functioning of these features is not essential, but that these are implicitly tested to a
sufficient degree in other tests.
4.3 Repetition of tests

As a general rule, the test cases specified in the present document are highly reproducible and don't need to be repeated
unless otherwise stated. However, the rate of correct UE behaviour such as cell re-selection, measurement and handover
is specified statistically, e.g. "at least 90%" [34]. Additionally, in some of the test cases , presented in TS 36.523-3
clause 7.3.2, HARQ retransmissions are not tolerated, because of characteristics of the test case [20]. It is the case that
for those tests expecting such UE behaviour (stated above) are not 100% reproducible, therefore if a UE does not pass
the test after its first trial and the tester suspects the reason is due to the statistical nature of the test, then the UE should
be re-tested one or more times. For non-HARQ retransmission tolerant test cases re-testing applies, when test case does
not pass, which is caused by unspecified HARQ retransmission.
4.4 Handling of differences between conformance requirements

in different releases of cores specifications
The conformance requirements which determine the scope of each test case are explicitly copy-pasted from relevant
core specifications in the especially dedicated for this section of each test with the title 'Conformance requirements'.
When differences between conformance requirements in different releases of the cores specifications have impact on
the Pre-test conditions, Test procedure sequence or/and the Specific message contents, the Conformance requirements
related to different releases are specified separately with clear indication of the Release of the spec from which they
were copied.
When there is no Release indicated for a conformance requirement text, this should be understood either as the
Conformance requirements in the latest version of the spec with release = the TC Applicability release (which can be
ETSI
found in 36.523-2, Table 4-1: Applicability of tests and additional information for testing, column 'Release'), or, as the
Conformance requirements in the latest version of the spec of the release when the feature was introduced to the core
specs.
5 Reference conditions
The reference environments used by all signalling and protocol tests will be specified in TS 36.508 [18]. Where a test
requires an environment that is different, this will be specified in the test itself.
5.1 Generic setup procedures

A set of basic generic procedures for radio resource signalling, and generic setup procedures for layer 3 NAS signalling
will be described in TS 36.508 [18]. These procedures will be used in numerous test cases throughout the present
document.
6 Idle mode operations

6.0 Introduction
6.0.1 PLMN and TAC
The PLMN numbers indicated in Table 6.0.1-1 are used in test cases to associate a cell with an MCC and MNC for that
cell. If no PLMN is explicitly specified, the default value is PLMN 1.
Table 6.0.1-1: Tracking Area Identity (TAI) in System Information Block Type 1
broadcast on the BCCH (E-UTRAN)
PLMN MCC1 MCC2 MCC3 MNC1 MNC2 MNC3 TAC

1 0 0 1 0 1 Not present See
2 0 0 2 1 1 Not present Table
3 0 0 3 2 1 Not present 6.0.1-2
4 0 0 4 3 1 Not present
NOTE: The Location Area Information (LAI) for UTRA and GSM could be re-used from TS 34.123-1 clause 6.
If no TAC for E-UTRAN cell is explicitly specified in the test case description, the TACs for E-UTRAN cells indicated
in Table 6.0.1-2 are used in the test case.
ETSI
Table 6.0.1-2: Tracking Area Code (TAC) for E-UTRAN cells
cell ID TAC
Cell 1 1
Cell 2 2
Cell 3 3
Cell 4 4
Cell 6 6
Cell 10 10
Cell 11 11
Cell 12 12
Cell 13 13
Cell 14 14
Cell 23 23
Cell 28 28
Cell 29 29
Cell 30 30
If no RAI for UTRAN cell is explicitly specified in the test case description, the RAI for UTRAN cells indicated in
Table 4.4.4-2 in [18] are used in the test case.
6.0.2 Other
6.0.2.1 Values of parameters calculated by the UE
Values of some parameters calculated by the UE, such as Srxlev, are provided in the test case description without
explicitly taking into account SS signal generation and UE measurement uncertainties. These values are for information
purpose only and therefore shall not be directly used to determine the UE behaviour; instead a range of values resulting
from uncertainties specific for given test case conditions shall be considered.
6.1 In a pure E-UTRAN environment

6.1.1 PLMN selection
6.1.1.1 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /
Automatic mode
6.1.1.1.1 Test Purpose (TP)
(1)
with { UE in Automatic network selection mode and RPLMN, HPLMN, UPLMN and OPLMN E-UTRAN cells
available and UE is fitted with a USIM indicating RPLMN should be selected }
ensure that {
when { UE is switched on or return to coverage }
then { UE selects a cell of the RPLMN and UE attempts Tracking area update on the selected cell
and when successfully registered indicates the selected PLMN to the user. }
}
(2)
with { UE camped on an E-UTRAN VPLMN cell and cells of a higher priority E-UTRAN PLMN available }
ensure that {
when { higher priority PLMN search timer T expires }
then { UE selects and camps on a cell of the highest priority PLMN and UE attempts Tracking area
updateon the selected cell and when successfully registered indicates the selected PLMN to the user.
}
}
(3)
with { UE in Automatic network selection mode and HPLMN, UPLMN and OPLMN E-UTRAN cells available and
UE is fitted with a USIM with Access Technology data files for each PLMN and there are no equivalent
HPLMNs defined}
ensure that {
ETSI
then { UE selects a cell of the highest priority PLMN and UE attempts Tracking area updateon the
selected cell and when successfully registered indicates the selected PLMN to the user. }
}
(4)
with { UE camped on an E-UTRAN VPLMN cell and cells of a E-UTRAN HPLMN available }
ensure that {
then { UE selects and camps on a cell of HPLMN and UE attempts Tracking area update on the
selected cell and when successfully registered indicates the selected PLMN to the user. }
}
6.1.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1,
4.4.3.1.1 and 4.4.3.3.
[TS 23.122, clause 4.4.3.1]
At switch on, or following recovery from lack of coverage, the MS selects the registered PLMN or equivalent PLMN (if
it is available) using all access technologies that the MS is capable of and if necessary (in the case of recovery from lack
of coverage, see clause 4.5.2) attempts to perform a Location Registration.
...
If successful registration is achieved, the MS indicates the selected PLMN.
If there is no registered PLMN, or if registration is not possible due to the PLMN being unavailable or registration
failure, the MS follows one of the following two procedures depending on its PLMN selection operating mode. At
switch on, if the MS provides the optional feature of user preferred PLMN selection operating mode at switch on then
this operating mode shall be used.
...
NOTE 1: If successful registration is achieved, then the current serving PLMN becomes the registered PLMN and
the MS does not store the previous registered PLMN for later use.
[TS 23.122, clause 4.4.3.1.1]
The MS selects and attempts registration on other PLMN/access technology combinations, if available and allowable, in
the following order:
i) either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is
available (if the EHPLMN list is present) ;
ii) each PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology"
data file in the SIM (in priority order);
iii) each PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access
Technology" data file in the SIM (in priority order);
iv) …
v) ...
When following the above procedure the following requirements apply:
a) …
b) ...
ETSI
c) In ii and iii, the MS should limit its search for the PLMN to the access technology or access technologies
associated with the PLMN in the appropriate PLMN Selector with Access Technology list (User Controlled or
Operator Controlled selector list). An MS using a SIM without access technology information storage (i.e. the
"User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with
Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN
in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of and shall
assume GSM access technology as the highest priority radio access technology.
d) ...
e) ...
f) In i, the MS shall search for all access technologies it is capable of. No priority is defined for the preferred access
technology and the priority is an implementation issue, but "HPLMN Selector with Access Technology" data file
on the SIM may be used to optimise the procedure.
g) ...
h) ...
NOTE 1: ...
NOTE 2: ...
NOTE 3: High quality signal is defined in the appropriate AS specification.
[TS 23.122, clause 4.4.3.3]
If the MS is in a VPLMN, the MS shall periodically attempt to obtain service on its HPLMN (if the EHPLMN list is not
present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a higher priority PLMN/access
technology combinations listed in "user controlled PLMN selector" or "operator controlled PLMN selector" by scanning
in accordance with the requirements that are applicable to i), ii) and iii) as defined in the Automatic Network Selection
Mode in clause 4.4.3.1.1. In the case that the mobile has a stored "Equivalent PLMNs" list the mobile shall only select a
PLMN if it is of a higher priority than those of the same country as the current serving PLMN which are stored in the
"Equivalent PLMNs" list. For this purpose, a value T minutes may be stored in the SIM, T is either in the range 6
minutes to 8 hours in 6 minute steps or it indicates that no periodic attempts shall be made. If no value is stored in the
SIM, a default value of 60 minutes is used.
The attempts to access the HPLMN or an EHPLMN or higher priority PLMN shall be as specified below:
a) The periodic attempts shall only be performed in automatic mode when the MS is roaming;
b) After switch on a period of at least 2 minutes and at most T minutes shall elapse before the first attempt is made;
c) The MS shall make the following attempts if the MS is on the VPLMN at time T after the last attempt;
d) Periodic attempts shall only be performed by the MS while in idle mode;
e) If the HPLMN (if the EHPLMN list is not present or is empty) or a EHPLMN (if the list is present) or a higher
priority PLMN is not found, the MS shall remain on the VPLMN.
f) In steps i), ii) and iii) of subclause 4.4.3.1.1 the MS shall limit its attempts to access higher priority
PLMN/access technology combinations to PLMN/access technology combinations of the same country as the
current serving VPLMN, as defined in Annex B.
g) ...
h) If the PLMN of the highest priority PLMN/access technology combination available is the current VPLMN, or
one of the PLMNs in the "Equivalent PLMNs" list, the MS shall remain on the current PLMN/access technology
combination.
ETSI
6.1.1.1.3 Test description
6.1.1.1.3.1 Pre-test conditions
System Simulator:
- Four inter-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
PLMNs as indicated in Table 6.1.1.1.3.1-1.
- The PLMNs are identified in the test by the identifiers in Table 6.1.1.1.3.1-1.
Table 6.1.1.1.3.1–1: PLMN identifiers
Cell PLMN name MCC MNC

1 PLMN4 001 01
12 PLMN1 001 11
13 PLMN2 001 21
14 PLMN3 001 31
UE:
- The UE is in Automatic PLMN selection mode.
- The UE is registered to PLMN1 before it is switched off.
- The UE is equipped with a USIM containing default values (as per TS 36.508) except for those listed in Table
6.1.1.1.3.1-2.
Table 6.1.1.1.3.1–2: USIM configuration
USIM field Priority Value Access Technology Identifier

EFIMSI The HPLMN (MCC+MNC) of the
IMSI is set to PLMN4.
EFPLMNwAcT 1 Default Default
2 PLMN3 All specified
3 PLMN2 E-UTRAN
Remaining mandatory entries use
default values
EFOPLMNwACT 1 PLMN1 All specified
Remaining defined entries use
default values
EFHPLMNwAcT 1 PLMN4 E-UTRAN
EFUST Services 20, 42, 43 and 74 are
supported. Service 71 is not
supported (there is no EHPLMN
list).
EFHPPLMN 1 (6 minutes)
Preamble:
- The UE is made to camp on Cell 12 and then Switched OFF (State 1).
6.1.1.1.3.2 Test procedure sequence
Table 6.1.1.1.3.2 – 1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configurations marked “T1”, “T2” etc are applied at the points indicated in the Main behaviour
description in Table 6.1.1.1.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in
TS36.508 Table 6.2.2.1-1.
ETSI
Table 6.1.1.1.3.2-1: Cell configuration changes over time
Parameter Unit Cell 1 Cell 12 Cell 13 Cell 14 Remarks

T0 RS EPRE dBm/15kHz “Off” -85 “Off” “Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T1 RS EPRE dBm/15kHz -85 -85 -85 ”Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T2 RS EPRE dBm/15kHz “Off” -85 -85 “Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T3 RS EPRE dBm/15kHz “Off” -85 -85 -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
ETSI
Table 6.1.1.1.3.2-2: Main behaviour
St Procedure Message Sequence TP Verdict

U-S Message
1 SS adjusts cell levels according to row T1 of - - - -
table 6.1.1.1.3.2-1
2 Power on the UE. - - - -
3 Check: Does the UE send an --> RRCConnectionRequest 1 P
RRCConnectionRequest on Cell 12?
4- Steps 3 to 17 of the registration procedure - - - -
18 described in TS 36.508 subclause 4.5.2.3 are
performed on Cell 12.
NOTE: The UE performs registration and the
RRC connection is released.
19 Check: Is PLMN1 indicated by the UE? - - 1 P
RRCConnectionRequest on Cell 1 after 120
seconds, but before 660seconds (Note 2) from
power on?
21- Steps 2 to 6 of the generic test procedure in - - - -
25 TS 36.508 subclause 6.4.2.7 are performed on
Cell 1.
NOTE: The UE performs a TAU procedure and
the RRC connection is released.
27 Void - - - -
table 6.1.1.1.3.2-1
29 Check: Does the test result of generic test - - 3 -
procedure in TS 36.508 subclause 6.4.2.7
indicate that the UE is camped on E-UTRAN
Cell 13?
table 6.1.1.1.3.2-1
seconds, but before 660 seconds after step29
? (Note 1 and 2)
37 TS 36.508 subclause 6.4.2.7 are performed.
39 Void - - - -
Note 1: Following attempts to access the HPLMN/EHPLMN/higher priority PLMN in VPLMN is operator specific
setting (Refer to TS 23.122 Rel-12).Hence, window between 120s to T+Tolerance is being used,, where
the high priority PLMN search timer T defined by EFHPPLMN.
Note 2: Tolerance of 5min is added to allow time for the UE to find the proper PLMN
6.1.1.1.3.3 Specific message contents
None
6.1.1.1a PLMN selection / Automatic mode/between FDD and TDD

6.1.1.1a.1 Test Purpose (TP)
(1)
with { UE in Automatic network selection mode and camp on a cell of a PLMN with FDD mode }
ensure that {
then { UE selects a cell of a PLMN with TDD mode and UE attempts registration on the selected
cell and when successfully registered indicates the selected PLMN to the user. }
ETSI
(2)
with { UE in Automatic network selection mode and camp on a cell of a PLMN with TDD mode}
ensure that {
then { UE selects a cell of a PLMN with FDD mode and UE attempts registration on the selected
}
6.1.1.1a.2 Conformance requirements
4.4.3.1.1 and 4.4.3.3.
[TS 23.122, clause 4.4.3.1]
...
...
...
NOTE2: …
[TS 23.122, clause 4.4.3.1.1]
iv) …
v) ...
a) …
b) ...
ETSI
Operator Controlled selector list). An MS using a SIM without access technology information storage (i.e. the
"User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with
Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN
in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of and shall
assume GSM access technology as the highest priority radio access technology.
d) ...
e) ...
g) ...
h) ...
NOTE 1: ...
NOTE 2: ...
...
6.1.1.1a.3 Test description
6.1.1.1a.3.1 Pre-test conditions
System Simulator
- Two FDD and TDD inter-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured
broadcasting default PLMNs as indicated in TS 36.508 Table 4.4.2-2.
- The PLMNs are identified in the test by the identifiers in Table 6.1.1.1a.3.1-1.
Table 6.1.1.1a.3.1-1: PLMN identifiers
Cell PLMN name MODE

1 PLMN1 FDD
28 PLMN2 TDD
UE
6.1.1.1a.3.1-2.
Table 6.1.1.1a.3.1-2: USIM configuration

EFLOCI PLMN1 (See preamble) E-UTRAN
EFIMSI The HPLMN (MCC+MNC) of the E-UTRAN
2 PLMN2 E-UTRAN
default values
EFOPLMNwACT 1 PLMN1 E-UTRAN
default values
ETSI
Preamble
- The UE is in state Switched OFF (State 1).
6.1.1.1a.3.2 Test procedure sequence
Table 6.1.1.1a.3.2 – 1 shows the cell configurations used during the test. The configuration T0 indicates the initial
description in Table 6.1.1.1a.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in
TS36.508 Table 6.2.2.1-1.
Table 6.1.1.1a.3.2-1: Cell configuration changes over time
Parameter Unit Cell 1 Cell 28 Remarks

T0 RS EPRE dBm/15kHz -85 “Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T1 RS EPRE dBm/15kHz ”Off” -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T2 RS EPRE dBm/15kHz -85 “Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
Table 6.1.1.1a.3.2-2: Main behaviour

U-S Message

18 PLMN1 is indicated by the UE. - - - -
19 Power off the UE, and wait [15 seconds]. - -
table 6.1.1.1a.3.2-1
21 Power on the UE
22 Check: Does the UE send an - - 1 P

39 Power off the UE, and wait [15 seconds]. - - - -
table 6.1.1.1a.3.2-1
41 Power on the UE - - - -
42 Check: Does the UE send an - - 2 P
performed on Cell1.

ETSI
6.1.1.1a.3.3 Specific message contents
None
6.1.1.1b PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /

Automatic mode / Single Frequency operation
6.1.1.1b.1 Test Purpose (TP)
Same Test Purpose as in clause 6.1.1.1.1
6.1.1.1b.2 Conformance requirements
Same Conformance requirements as in clause 6.1.1.1.2
6.1.1.1b.3 Test description
6.1.1.1b.3.1 Pre-test conditions
System Simulator:
- Four intra-frequency multi-PLMN cells.
- The PLMNs are identified in the test by the identifiers in Table 6.1.1.1b.3.1-1.
Table 6.1.1.1b.3.1–1: PLMN identifiers

1 PLMN4 001 01
2 PLMN1 001 11
4 PLMN2 001 21
11 PLMN3 001 31
UE:
6.1.1.1b.3.1-2.
Table 6.1.1.1b.3.1–2: USIM configuration

2 PLMN3 All specified
3 PLMN2 E-UTRAN
default values
default values
EFUST Services 20, 42, 43 and 74 are
list).
Preamble:
- The UE is made to camp on Cell 2 and then Switched OFF (State 1).
ETSI
6.1.1.1b.3.2 Test procedure sequence
Table 6.1.1.1b.3.2 – 1 shows the cell configurations used during the test. The configuration T0 indicates the initial
description in Table 6.1.1.1b.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in
TS36.508 Table 6.2.2.1-1.
Table 6.1.1.1b.3.2-1: Cell configuration changes over time

T0 RS EPRE dBm/15kHz “Off” -85 “Off” “Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
defined in TS36.508
Table 6.2.2.1-1
defined in TS36.508
Table 6.2.2.1-1
T3 RS EPRE dBm/15kHz “Off” -85 -79 “Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
defined in TS36.508
Table 6.2.2.1-1
ETSI
Table 6.1.1.1b.3.2-2: Main behaviour

U-S Message
table 6.1.1.1b.3.2-1
A table 6.1.1.1b.3.2-1
seconds, but before 660seconds (Note 2) from
power on?
Cell 1.
27 Void - - - -
table 6.1.1.1b.3.2-1
Cell 4?
table 6.1.1.1b.3.2-1
seconds, but before 660 seconds after step
29? (Note 1 and 2)
39 Void - - - -
Note 1: Following attempts to access the HPLMN/EHPLMN/higher priority PLMN in VPLMN is operator specific
setting (Refer to TS 23.122 Rel-12).Hence, window between 120s to T+Tolerance is being used , where
the high priority PLMN search timer T defined by EFHPPLMN
Note 2: Tolerance of 5min is added to allow time for the UE to find the proper PLMN
ETSI
6.1.1.1b.3.3 Specific message contents
Table 6.1.1.1b.3.3-1: SystemInformationBlockType3 for cells 2 and 4 (preamble and all steps, table
6.1.1.1b.3.2-2)
Derivation Path: 36.508 table 4.4.3.3-2

Information Element Value/remark Comment
SystemInformationBlockType3 ::= SEQUENCE {
cellReselectionInfoCommon SEQUENCE {
q-Hyst dB24
}
}
6.1.1.2 PLMN selection of "Other PLMN/access technology combinations" /

Automatic mode
(1)
with { UE in Automatic network selection mode and EHPLMN, UPLMN, OPLMN and other PLMN/access
technology combinations cells available and UE is fitted with a USIM with Access Technology data
files for each PLMN }
ensure that {
then { UE selects a cell of the EPLMN and UE attempts a location registration on the selected
}
(2)
with { UE in Automatic network selection mode and UPLMN, OPLMN and other PLMN/access technology
combinations cells available and UE is fitted with a USIM with Access Technology data files for each
PLMN }
ensure that {
then { UE selects a cell of the UPLMN and UE attempts a location registration on the selected
}
(3)
with { UE in Automatic network selection mode and OPLMN and other PLMN/access technology
combinations cells available and UE is fitted with a USIM with Access Technology data files for each
PLMN }
ensure that {
then { UE selects a cell of the OPLMN and UE attempts a location registration on the selected
}
(4)
with { UE in Automatic network selection mode and other PLMN/access technology combinations cells
not belonging to any of EHPLMN, UHPLMN or OPLMN available }
ensure that {
then { UE selects a cell of other PLMN/access technology combinations and UE attempts a location
registration on the selected cell and when successfully registered indicates the selected PLMN to
the user. }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1.1.
[TS 23.122, clause 4.4.3.1.1]
ETSI
4.4.3.1.1 Automatic Network Selection Mode Procedure
available (if the EHPLMN list is present);
iv) other PLMN/access technology combinations with received high quality signal in random order;
v) other PLMN/access technology combinations in order of decreasing signal quality.
a) An MS with voice capability shall ignore PLMNs for which the MS has identified at least one GSM COMPACT.
b) In A/Gb mode or GSM COMPACT, an MS with voice capability, or an MS not supporting packet services shall
not search for CPBCCH carriers.
Operator Controlled selector list).
An MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector
with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are
not present) shall instead use the "PLMN Selector" data file, for each PLMN in the "PLMN Selector" data file,
the MS shall search for all access technologies it is capable of. The priority ordering amongst the access
technologies is implementation dependent.
d) In iv and v, the MS shall search for all access technologies it is capable of, before deciding which PLMN to
select.
e) In ii, and iii, a packet only MS which supports GSM COMPACT, but using a SIM without access technology
information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator
Controlled PLMN Selector with Access Technology" data files are not present) shall instead use the "PLMN
Selector" data file, for each PLMN in the "PLMN Selector" data file, the MS shall search for all access
technologies it is capable of and shall assume GSM COMPACT access technology as the lowest priority radio
access technology.
g) In i, an MS using a SIM without access technology information storage (i.e. the "HPLMN Selector with Access
Technology" data file is not present) shall search for all access technologies it is capable of. The priority ordering
amongst the access technologies is implementation dependent. A packet only MS which supports GSM
COMPACT using a SIM without access technology information storage shall also assume GSM COMPACT
access technology as the lowest priority radio access technology.
h) In v, the MS shall order the PLMN/access technology combinations in order of decreasing signal quality within
each access technology. The order between PLMN/access technology combinations with different access
technologies is an MS implementation issue.
NOTE 1: Requirements a) and b) apply also to requirement d), so a GSM voice capable MS should not search for
GSM COMPACT PLMNs, even if capable of GSM COMPACT.
NOTE 2: Requirements a) and b) apply also to requirement f), so a GSM voice capable MS should not search for
GSM COMPACT PLMNs, even if this is the only access technology on the "HPLMN Selector with
Access Technology" data file on the SIM.
ETSI
If registration cannot be achieved because no PLMNs are available and allowable, the MS indicates "no service" to the
user, waits until a new PLMN is available and allowable and then repeats the procedure.
If there were one or more PLMNs which were available and allowable, but an LR failure made registration on those
PLMNs unsuccessful or an entry in any of the lists "forbidden LAs for roaming", "forbidden TAs for roaming",
"forbidden LAs for regional provision of service" or "forbidden TAs for regional provision of service" prevented a
registration attempt, the MS selects the first such PLMN again and enters a limited service state.
System Simulator:
default PLMNs as indicated in TS 36.508 Table 4.4.2-2.
Cell PLMN name

1 PLMN1
12 PLMN2
13 PLMN3
14 PLMN4
UE:
6.1.1.2.3.1-2.

EFEHPLMN 1 PLMN1
default values
EFPLMNwAcT 1 PLMN2 E-UTRAN
default values
default values
EFUST Services 20, 42 and 71 are
supported.
Preamble:
conditions. Subsequent configurations marked “T1”, “T2” “T3” “T4”etc are applied at the points indicated in the Main
behaviour description in Table 6.1.1.2.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as
defined in TS36.508 Table 6.2.2.1-1.
ETSI

T1 RS EPRE dBm/15kHz -85 -85 -85 “Off”
defined in TS36.508
Table 6.2.2.1-1
T3 RS EPRE dBm/15kHz “Off” ”Off” -85 -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T4 RS EPRE dBm/15kHz “Off” ”Off” ”Off” -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1

U-S Message
1 SS adjusts cell levels according to row T1of - - - -
table 6.1.1.2.3.2-1
table 6.1.1.2.3.2-1
Cell 12.
table 6.1.1.2.3.2-1
Cell 13.
table 6.1.1.2.3.2-1
Cell 14.
None
ETSI
6.1.1.2a PLMN selection of "Other PLMN/access technology combinations" /

Automatic mode / Single Frequency operation
System Simulator:
- Four intra-frequency multi-PLMN cells.
Table 6.1.1.2a.3.1–1: PLMN identifiers
Cell PLMN name

1 PLMN1
2 PLMN2
4 PLMN3
11 PLMN4
UE:
6.1.1.2a.3.1-2.
Table 6.1.1.2a.3.1–2: USIM configuration

EFEHPLMN 1 PLMN1
default values
default values
default values
EFUST Services 20, 42 and 71 are
supported.
Preamble:
conditions. Subsequent configurations marked “T1”, “T2” “T3” “T4”etc are applied at the points indicated in the Main
behaviour description in Table 6.1.1.2a.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as
defined in TS36.508 Table 6.2.2.1-1.
ETSI

T1 RS EPRE dBm/15kHz -79 -85 -85 “Off”
defined in TS36.508
Table 6.2.2.1-1
T3 RS EPRE dBm/15kHz “Off” ”Off” -79 -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T4 RS EPRE dBm/15kHz “Off” ”Off” ”Off” -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1

U-S Message
table 6.1.1.2a.3.2-1
table 6.1.1.2a.3.2-1
Cell 2.
table 6.1.1.2a.3.2-1
Cell 4.
table 6.1.1.2a.3.2-1
Cell 11.
None
ETSI
6.1.1.3 Cell reselection of ePLMN in manual mode

(1)
with { UE camped normally on a cell and network has downloaded a list of equivalent PLMNs during the
Attach procedure }
ensure that {
when { higher ranked cell is a cell of a PLMN in the downloaded equivalent PLMN list }
then { UE reselects to the equivalent PLMN cell. }
}
(2)
Tracking Area Update procedure }
ensure that {
when { highest ranked cell is a cell of a PLMN not in the downloaded equivalent PLMN list }
then { UE does not reselect to the cell. }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clause 4.4.3.1.2.
[TS 23.122, clause 4.4.3.1.2]
Once the UE has registered on a PLMN selected by the user, the UE shall not automatically register on a different
PLMN unless:
i) the new PLMN is declared as an equivalent PLMN by the registered PLMN; or
ii) the user selects automatic mode.
System Simulator
- Three inter-frequency multi-PLMN cells.
- Each cell has only a single PLMN identity. The PLMNs are identified in the test by the identifiers in Table
6.1.1.3.3.1-1.
Table 6.1.1.3.3.1-1: PLMN identifiers
Cell PLMN name

1 PLMN1
12 PLMN2
13 PLMN3
- System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE
- The UE is in Manual PLMN selection mode.
ETSI
Preamble
- The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508[18] clause 4.5.2.3 except
that the ATTACH ACCEPT message indicates PLMN2 in the Equivalent PLMN list as described in Table
6.1.1.3.3.3-2.
- The UE is in state Registered, Idle Mode (State 2) on Cell 1 according to TS 36.508[18];
Table 6.1.1.3.3.2-1: Time instances of cell power level changes
Parameter Unit Cell 1 Cell 12 Cell 13 Remarks

T1 RS EPRE dBm/15kHz -97 -82 -67
T2 RS EPRE dBm/15kHz -85 -97 “Off” Power level “Off” is defined in TS36.508
Table 6.2.2.1-1

U-S Message
table 6.1.1.3.3.2-1
2 Check: Does the test result of generic test - - 1,2 P
Cell 12?
NOTE: The TAU is accepted with PLMN1
listed as an Equivalent PLMN
3 Check: Is PLMN2 indicated by the UE? - - 1,2 P
4 Check: Does the UE send an - - 2 F
RRCConnectionRequest on Cell 1 and 13
within 60s?
5 Set UE to Automatic PLMN selection mode. - - - -
table 6.1.1.3.3.2-1
7 The generic test procedure in TS 36.508 - - - -
subclause 6.4.2.7 is performed on cell 1.
Note 1: In Step 4 no further cell reselections are expected.
Note 2: Cell 13 is the highest ranked cell, but never appears in the ePLMN list.
Note 3: Steps 5 - 7 are to ensure UE is set back to automatic PLMN selection mode for the next test case.
ETSI
Table 6.1.1.3.3.3-1: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table
6.1.1.3.3.2-2)
Derivation path: 36.508 Table 4.4.3.3-4

Information Element Value/Remark Comment Condition
interFreqCarrierFreqList SEQUENCE (SIZE
(1..maxFreq)) OF SEQUENCE {
dl-CarrierFreq[1] Same downlink EARFCN
as used for Cell 12
cellReselectionPriority[1] 4
as used for Cell 13
}
}
6.1.1.3.3.2-2)

as used for Cell 1
as used for Cell 13
}
}
Table 6.1.1.3.3.3-3: ATTACH ACCEPT for Cell 1 (preamble)
Derivation path: 36.508 Table 4.7.2-1

Equivalent PLMNs PLMN2 Cell 1
Table 6.1.1.3.3.3-4: TRACKING AREA UPDATE ACCEPT for Cell 12 (step 2, Table 6.1.1.3.3.2-2)

6.1.1.3a Cell reselection of ePLMN in manual mode / between FDD and TDD
(1)
Attach procedure }
ensure that {
when { higher ranked cell is a cell of a PLMN in the downloaded equivalent PLMN list }
then { UE reselects to the equivalent PLMN cell. }
}
ETSI
(2)
Tracking Area Update procedure }
ensure that {
when { highest ranked cell is a cell of a PLMN not in the downloaded equivalent PLMN list }
then { UE does not reselect to the cell. }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clause 4.4.3.1.2.
[TS 23.122, clause 4.4.3.1.2]
Once the UE has registered on a PLMN selected by the user, the UE shall not automatically register on a different
PLMN unless:
i) the new PLMN is declared as an equivalent PLMN by the registered PLMN; or
ii) the user selects automatic mode.
System Simulator
- Four multi-PLMN cells. Cell 1 and Cell 2 are set to LTE-FDD mode while Cell 28 and Cell 29 are set to LTE-
TDD mode.
6.1.1.3a.3.1-1. Note Cell 2 is in a different PLMN to Cell 1.
Cell PLMN name

1 PLMN1
28 PLMN2
2 PLMN3
29 PLMN3
- System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 and Table 6.3.1.2-2 is used in E-
UTRA cells.
UE
- The UE is equipped with a USIM containing default values (as per TS 36.508) except for those shown in Table
6.1.1.3a.3.1-2.

EFLOCI PLMN1 (See pre-amble)
Preamble
6.1.1.3a.3.3-1.
ETSI
Table 6.1.1.3a.3.2-1: Time instances of cell power level changes
Paramet Unit Cell 1 Cell 28 Cell 2 Cell 29 Remarks

er
T1 RS dBm/15
EPRE kHz -97 -82 -67 OFF
T2 RS dBm/15
EPRE kHz -82 -97 OFF -67
T3 RS dBm/15
EPRE kHz -97 -82 OFF OFF
T4 RS dBm/15
EPRE kHz -82 -97 OFF OFF

U-S Message
table 6.1.1.3a.3.2-1
Cell 28?
RRCConnectionRequest on Cell 2 within 60s?
table 6.1.1.3a.3.2-1
Cell 1?
RRCConnectionRequest on Cell 29 within
60s?
8 Generic test procedure in TS 36.508
subclause 4.5.3.3 is performed on Cell 1.
NOTE: The UE performs the establishment of
the new data radio bearer associated with the
default EPS bearer context.
9 SS adjusts cell levels according to row T3 of - - -
table 6.1.1.3a.3.2-1
10 SS transmits an RRCConnectionRelease <-- RRCConnectionRelease
message (IE redirectedCarrierInfo including
eutra CarrierFreq of Cell 28).
12 Set UE to Automatic PLMN selection mode. - - - -
table 6.1.1.3a.3.2-1
Note 2: Cell 3 and Cell 29 are the highest ranked cell, but never appears in the ePLMN list.
Note 3: Steps 8 -14 are to ensure UE is set back to automatic PLMN selection mode for the next test case.
ETSI
Table 6.1.1.3a.3.3-1: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table
6.1.1.3a.3.2-2)

as used for Cell 28
}
}
6.1.1.3a.3.2-2)

as used for Cell 1
}
}
Table 6.1.1.3a.3.3-3: ATTACH ACCEPT for Cell 1 (preamble)

Equivalent PLMNs PLMN2
Table 6.1.1.3a.3.3-4: TRACKING AREA UPDATE ACCEPT for Cell 28 (step 2, Table 6.1.1.3a.3.2-2)


ETSI
Table 6.1.1.3a.3.3-6: RRCConnectionRelease message (step 10, Table 6.1.1.3a.3.2-2)
Derivation Path: 36.508 table 4.6.1-15

Information Element Value/remark Comment Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
eutra Downlink EARFCN of cell
28
}
}
}
}
}
6.1.1.3b Cell reselection of ePLMN in manual mode / Single Frequency operation

System Simulator
- Two intra-frequency multi-PLMN cells.
6.1.1.3b.3.1-1.
Table 6.1.1.3b.3.1-1: PLMN identifiers
Cell PLMN name

1 PLMN1
2 PLMN2
UE
Preamble
6.1.1.3b.3.3-2.
ETSI
Table 6.1.1.3b.3.2-1: Time instances of cell power level changes

T1 RS EPRE dBm/15kHz -88 -82

U-S Message
1 SS adjusts cell levels according to row T1 of -- - -
table 6.1.1.3b.3.2-1
Cell 2?
listed as an Equivalent PLMN. Note 2.
3A SS adjusts cell levels according to row T2 of - - - -
table 6.1.1.3b.3.2-1
Note 2: PLMN3 is dummy PLMN, which is not associated on any cell, to able to satisfy test purpose.
Table 6.1.1.3b.3.3-1: ATTACH ACCEPT for Cell 1 (preamble)

Table 6.1.1.3b.3.3-2: TRACKING AREA UPDATE ACCEPT for Cell 2 (step 2, Table 6.1.1.3b.3.2-2)

6.1.1.4 PLMN selection in shared network environment / Automatic mode

(1)
with { the UE is in automatic network selection mode and there is a suitable cell with multiple PLMN
identities among which the HPLMN but not the registered PLMN }
ensure that {
when { the UE is switched on }
then { the UE attaches to the HPLMN on the shared cell }
}
(2)
with { the UE in automatic network selection mode and there is a suitable cell with multiple PLMN
identities among which the registered PLMN }
ensure that {
when { the UE returns to coverage }
ETSI
then { the UE performs a location registration to the registered PLMN on the shared cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 5.1.2.2, TS
23.122 clauses 4.4.3 and 4.4.3.1.1, TS 24.301 clauses 5.5.1.1 and 5.5.3.1, and TS 36.331 clause 5.3.3.4.
[TS 36.304 clause 5.1.2.2]
The UE shall scan all RF channels in the E-UTRA bands according to its capabilities to find available PLMNs. On each
carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN(s)
the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN (see the
PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value),
Once the UE has selected a PLMN, the cell selection procedure shall be performed in order to select a suitable cell of
that PLMN to camp on.
[TS 23.122 clause 4.4.3]
When the MS reselects to a cell in a shared network, the AS may indicate multiple PLMN identities to the NAS
according to 3GPP TS 25.304 [32]. The MS shall choose one of these PLMNs. If the registered PLMN is available
among these PLMNs, the MS shall not choose a different PLMN.
[TS 23.122 clause 4.4.3.1.1]
[TS 24.301 clause 5.5.1.1]
...
In a shared network, the UE shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [6]. The UE shall
construct the TAI of the cell from this chosen PLMN identity and the TAC received as part of the broadcast system
information. The chosen PLMN identity shall be indicated to the E-UTRAN (see 3GPP TS 36.331 [22]).
...
[TS 24.301 clause 5.5.3.1]
...
construct the TAI of the cell from this chosen PLMN identity and the TAC received on the broadcast system
...
[TS 36.331 clause 5.3.3.4]
The UE shall:
ETSI
...
1> set the content of RRCConnectionSetupComplete message as follows:
2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35])
from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;
...
2> submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the
procedure ends;
System Simulator:
- Cells 1 and 2, as specified in TS36.508 clause 4.4.1.2 are configured according to Table 4.4.2-2 in [18] except
for multiple broadcasted PLMN identities as shown in Table 6.1.1.4.3.1–1: PLMN identifiers broadcasted by
cells in shared network.
Cell PLMN names

1 PLMN15, PLMN1
2 PLMN15, PLMN1, PLMN16
UE:
6.1.1.4.3.1-2.

EFLOCI PLMN4
EFPLMNwAcT Empty
EFUST Service 74 is supported.
EFLRPLMNSI 00
Preamble:
- The UE is in state Switched OFF (state 1) according to [18].
Table 6.1.1.4.3.2–1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configuration marked “T1”is applied at the points indicated in the Main behaviour description in
Table 6.1.1.4.3.2-2. Cell powers are chosen for a serving cell and a non-suitable cell as defined in TS36.508 Table
6.2.2.1-1.

T0 RS EPRE dBm/15kHz -85 Off The power level values are assigned to such that
camping on Cell 1 is guaranteed. Cell 2 is “off”.
T1 RS EPRE dBm/15kHz Off -85 Cell 1 becomes “off”. UE shall select Cell 2.
ETSI

U-S Message
1 The SS adjusts cell levels according to row T0 - - - -
of table 6.1.1.4.3.2-1
3 Check: Does the UE transmits an --> RRCConnectionRequest 1 P
4 The SS transmits an RRCConnectionSetup <-- RRCConnectionSetup - -
5 Check; Does the UE transmit an --> RRCConnectionSetupComplete 1 P
RRCConnectionSetupComplete message
indicating the HPLMN (second PLMN in the
list)?
Note: this message contains an ATTACH
REQUEST and a PDN CONNECTIVITY
REQUEST message according to default
message contents.
of table 6.1.1.4.3.2-1
21 Check: Does the UE transmit an --> RRCConnectionRequest 2 P
22 - Steps 2 to 6 of the generic test procedure in - - - -
27 Check: Is the same PLMN as indicated by UE - - 2 P
in step 19 again indicated by the UE?
Table 6.1.1.4.3.3-1: RRCConnectionSetupComplete (step 5 and 23, Table 6.1.1.4.3.2-2)
Derivation Path: 36.508, Table 4.6.1-18

RRCConnectionSetupComplete ::= SEQUENCE {
c1 CHOICE{
rrcConnectionSetupComplete-r8 SEQUENCE {
selectedPLMN-Identity 2 PLMN1
}
}
}
}
6.1.1.4a PLMN selection in shared network environment / Automatic mode / Between

FDD and TDD
(1)
with { the UE is in automatic network selection mode and there is a suitable cell with multiple PLMN
identities among which the EHPLMN list is present }
ensure that {
when { the UE returns to coverage }
then { the UE performs a location registration to the highest priority EHPLMN that is
available with FDD mode on the shared cell }
}
ETSI
(2)
with { the UE in automatic network selection mode and there is a suitable cell with multiple PLMN
identities among which the EHPLMN list is present }
ensure that {
when { the UE is switched on }
then { the UE performs a location registration to the highest priority EHPLMN that is
available with TDD mode on the shared cell }
}
23.122 clauses 4.4.3 and 4.4.3.1.1, TS 24.301 clauses 5.5.1.1 and 5.5.3.1, and TS 36.331 clause 5.3.3.4.
[TS 36.304 clause 5.1.2.2]
PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value),
[TS 23.122 clause 4.4.3]
[TS 23.122 clause 4.4.3.1.1]
[TS 24.301 clause 5.5.1.1]
...
construct the TAI of the cell from this chosen PLMN identity and the TAC received as part of the broadcast system
...
[TS 24.301 clause 5.5.3.1]
...
construct the TAI of the cell from this chosen PLMN identity and the TAC received on the broadcast system
ETSI
...
[TS 36.331 clause 5.3.3.4]
The UE shall:
...
...
procedure ends;
System Simulator:
- Cell 1, Cell 2, Cell 28 and Cell 30 as specified in TS36.508 clause 4.4.1.2 are configured according to Table
4.4.2-2 in [18] except for multiple broadcasted PLMN identities as shown in Table 6.1.1.4a.3.1–1.
Cell PLMN names MODE

1 PLMN2,PLMN15 FDD
28 PLMN4,PLMN16 TDD
30 PLMN3,PLMN17 TDD
2 PLMN1,PLMN18 FDD
UE:
6.1.1.4a.3.1-2.

EFLOCI PLMN4
EFPLMNwAcT Empty
EFIMSI The HPLMN (MCC+MNC) of the E-UTRAN
EFUST Service 71 and 74 are supported.
EFLRPLMNSI 00
EFEHPLMN 1 PLMN2 E-UTRAN
2 PLMN1 E-UTRAN
3 PLMN4 E-UTRAN
default values
Preamble:
- The UE is in state Registered, Idle mode (state 2) on Cell 28 (serving cell) according to [18].
Table 6.1.1.4a.3.2–1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configuration marked “T1”is applied at the points indicated in the Main behaviour description in
ETSI
Table 6.1.1.4a.3.2-2. Cell powers are chosen for a serving cell and a non-suitable cell as defined in TS36.508 Table
6.2.2.1-1.

T0 RS EPRE dBm/15kHz ”Off” -85 ”Off” ”Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T1 RS EPRE dBm/15kHz -79 ”Off” ”Off” -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T2 RS EPRE dBm/15kHz ”Off” -85 -73 ”Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1

U-S Message
of table 6.1.1.4a.3.2-1
3– Steps 3 to 7 of the generic test procedure in - - - -
7 TS 36.508 subclause 4.5A.2.1-1 are
NOTE: The UE performs TAU procedure and
8– VOID - - - -
17
19 Power off the UE.
of table 6.1.1.4a.3.2-1
21 Power on the UE.
23 Steps 3 to 17 of the generic test procedure in - - - -
– TS 36.508 subclause 4.5.2.3 are performed.
37 NOTE: The UE performs registration and the
Table 6.1.1.4a.3.3-1: RRCConnectionSetupComplete (step 4, Table 6.1.1.4a.3.2-2)

c1 CHOICE{
}
}
}
}
ETSI
6.1.1.5 Void
6.1.1.6 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /
Automatic mode / User reselection
(1)
with { UE in Automatic network selection mode registered to UPLMN and RPLMN, UPLMN and OPLMN E-UTRAN
cells available }
ensure that {
when { UE is requested to initiate reselection and registration onto an available PLMN }
then { UE reselects to the cell which belongs to higher priority OPLMN }
}
(2)
with { UE in Automatic network selection mode registered to OPLMN and only RPLMN E-UTRAN cell
available }
ensure that {
then { UE remains on the current cell which belongs to RPLMN. }
}
(3)
with { UE in Automatic network selection mode registered to OPLMN and RPLMN, UPLMN and OPLMN E-UTRAN
cells available }
ensure that {
then { UE reselects to the cell which belongs to UPLMN }
}
(4)
with { UE in Automatic network selection mode registered to UPLMN and RPLMN, UPLMN, OPLMN and HPLMN
E-UTRAN cells available }
ensure that {
then { UE reselects to the cell which belongs to HPLMN }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause 4.4.3.2 and
4.4.3.2.1.
[TS 23.122, clause 4.4.3.2]
At any time the user may request the MS to initiate reselection and registration onto an available PLMN, according to
the following procedures, dependent upon the operating mode.
[TS 23.122, clause 4.4.3.2.1]
The MS selects and attempts registration on PLMNs, if available and allowable, in all of its bands of operation in
accordance with the following order:
i) the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if
the EHPLMN list is present);
ii) PLMN/access technology combinations contained in the "User Controlled PLMN Selector with Access
Technology" data file in the SIM (in priority order) excluding the previously selected PLMN/access technology
combination;
iii) PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access
Technology" data file in the SIM (in priority order) excluding the previously selected PLMN/access technology
combination;
ETSI
iv) other PLMN/access technology combinations with the received high quality signal in random order excluding
the previously selected PLMN/access technology combination;
v) other PLMN/access technology combinations, excluding the previously selected PLMN/access technology
combination in order of decreasing signal quality or, alternatively, the previously selected PLMN/access
technology combination may be chosen ignoring its signal quality;
vi) The previously selected PLMN/access technology combination.
The previously selected PLMN/access technology combination is the PLMN/access technology combination which the
MS has selected prior to the start of the user reselection procedure.
NOTE 1: If the previously selected PLMN is chosen, and registration has not been attempted on any other PLMNs,
then the MS is already registered on the PLMN, and so registration is not necessary.
The equivalent PLMNs list shall not be applied to the user reselection in Automatic Network Selection Mode.
System Simulator:
default NAS parameters as indicated in TS 36.508 Table 4.4.2-2.
• Cell • PLMN name

• 1 • PLMN1
• 12 • PLMN2
• 13 • PLMN3
• 14 • PLMN4
UE:
6.1.1.6.3.1-2.

EFLOCI PLMN1
default values
2 PLMN4 E-UTRAN
default values
EFUST Service 71 is not supported
Preamble:
- The UE is in state Registered, Idle Mode (State 2) on Cell 1 according to [18].
ETSI
Table 6.1.1.6.3.2-1: Time instances of cell power level and parameter changes
Parameter Unit Cell 1 Cell 12 Cell 13 Cell 14 Remark

The power level values are
Cell-specific RS dBm/15 assigned to satisfy RCell 1 = RCell 12 =
T1 -85 -85 "Off" -85
EPRE kHz RCell 14.
(NOTE 1).
Cell-specific RS dBm/15 Only Cell 12 is available.
T2 "Off" -85 "Off" "Off"
EPRE kHz (NOTE 1).
Cell-specific RS dBm/15 assigned to satisfy RCell 1 = RCell 13 =
T3 -85 "Off" -85 -85
EPRE kHz RCell 14.
(NOTE 1).
NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.
ETSI

U-S Message
1 The SS changes the power level setting - - - -
according to the row “T1” in table 6.1.1.6.3.2-1
2 Cause the UE in Automatic network selection - - - -
mode to initiate user reselection and
registration onto an available PLMN. (see
Note)
4-8 Steps 2 to 6 of the generic test procedure in - - - -
TS 36.508 subclause 6.4.2.7 are performed on
Cell 12.
9 Check: Is PLMN 2 indicated by the UE? - - 1 P
according to the row “T2” in table 6.1.1.6.3.2-1.
Note)
12 Check: Does the UE send an --> RRCConnectionRequest 2 F
RRCConnectionRequest on Cell 12 within 90
s?
Note)
Cell 1.
Note)
Cell 13.
Note: MMI command “TRIGGER_USER_RESELECTION” to be used. AT command AT+COPS is not suitable to
achieve the test purpose.
None
ETSI
6.1.1.6a PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /

Automatic mode / User reselection / Single Frequency operation
System Simulator:
- Four intra-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
Cell PLMN name

1 PLMN1
2 PLMN2
4 PLMN3
11 PLMN4
UE:
6.1.1.6a.3.1-2.

EFLOCI PLMN1
default values
2 PLMN4 E-UTRAN
default values
EFUST Service 71 is not supported
Preamble:
ETSI
Table 6.1.1.6a.3.2-1: Time instances of cell power level and parameter changes

Cell-specific RS dBm/15 (NOTE 1)
T1 -85 -79 "Off" -85
EPRE kHz
Cell-specific RS dBm/15 Only Cell 2 is available.
T2 "Off" -85 "Off" "Off"
EPRE kHz (NOTE 1)
Cell-specific RS dBm/15 (NOTE 1).
T3 -79 -85 "Off" -85
EPRE kHz
Cell-specific RS dBm/15 (NOTE 1)
T4 -85 "Off" -79 -85
EPRE kHz
ETSI

U-S Message
according to the row “T1” in table 6.1.1.6a.3.2-
1
Note)
Cell 2.
1.
Note)
RRCConnectionRequest on Cell 2 within 90 s?
1.
Note)
Cell 1.
1.
Note)
Cell 4.
Note: MMI command “TRIGGER_USER_RESELECTION” to be used. AT command AT+COPS is not suitable to
achieve the test purpose..
ETSI
Table 6.1.1.6a.3.3-1: SystemInformationBlockType3 for cells 1 and 2 (preamble and all steps, table
6.1.1.6a.3.2-2)

q-Hyst dB24
}
}
6.1.1.7 PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer

(1)
with { UE configured with “MinimumPeriodicSearchTimer“ and camped on an E-UTRAN VPLMN cell and cells
of a higher priority E-UTRAN PLMN available }
ensure that {
when { the higher priority PLMN search timer T stored in the USIM or the default value for T is
less than the MinimumPeriodicSearchTimer }
then { T shall be set to the MinimumPeriodicSearchTimer. After the first attempt to the higher
priority PLMN cell is made, the UE shall not use a value for T that is less than the
MinimumPeriodicSearchTimer. When the T expires the UE selects and camps on a cell of the highest
priority PLMN and UE attempts a location registration on the selected cell and when successfully
registered indicates the selected PLMN to the user. }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1 and
4.4.3.3.1.
[TS 23.122, clause 4.4.3.1]
...
...
ETSI
[TS 23.122, clause 4.4.3.3.1]
Mode in subclause 4.4.3.1.1. In the case that the mobile has a stored "Equivalent PLMNs" list the mobile shall only
select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN which are stored
in the "Equivalent PLMNs" list. For this purpose, a value T minutes may be stored in the SIM, T is either in the range
6 minutes to 8 hours in 6 minute steps or it indicates that no periodic attempts shall be made. If no value is stored in the
SIM, a default value of 60 minutes is used for T.
If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or

3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the
value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the
MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer.
a) The periodic attempts shall only be performed in automatic mode when the MS is roaming, and not while the
MS is attached for emergency bearer services or has a PDN connection for emergency bearer services;
….
System Simulator:
- Three multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting PLMNs as
indicated in Table 6.1.1.7.3.1-1.

1 PLMN4 001 01
12 PLMN1 001 11
13 PLMN2 001 21
UE:
- The UE is configured with a value of MinimumPeriodicSearchTimer set to 7 minutes
6.1.1.7.3.1-2.
ETSI
Table 6.1.1.7.3.1-2: USIM configuration

EFLOCI PLMN1 (See preamble)
2 PLMN2 E-UTRAN
default values
default values
EFUST Services 20, 42, 43, 74 and 96 are
list).
EFNASCONFIG MinimumPeriodicSearchTimer set
to 7 minutes
Preamble:
conditions. Subsequent configurations marked “T1” is applied at the point indicated in the Main behaviour description
in Table 6.1.1.7.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS36.508
Table 6.2.2.1-1.

T0 RS EPRE dBm/15kHz “Off” -85 “Off” Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T1 RS EPRE dBm/15kHz “Off” -85 -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
T2 RS EPRE dBm/15kHz -85 -85 -85 Power level “Off” is
defined in TS36.508
Table 6.2.2.1-1
ETSI

U-S Message
table 6.1.1.7.3.2-1
19 UE selects PLMN1 - - - -
seconds, but before 420 seconds from power
on?
Cell 13.
table 6.1.1.7.3.2-1
seconds from step 20?
Cell 1.
Note 1: Timers in Steps 20 and 28 are derived from the value defined by the MinimumPeriodicSearchTimer
None
6.1.1.7a PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer /

Single Frequency operation
System Simulator:
- Three intra-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
PLMNs as indicated in TS 36.508 Table 4.4.2-2.
System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
ETSI

1 PLMN4 001 01
2 PLMN1 001 11
4 PLMN2 001 21
UE:
- The UE is configured with a value of MinimumPeriodicSearchTimer set to 7 minutes
6.1.1.7a.3.1-2.

EFLOCI PLMN1 (See preamble)
2 PLMN2 E-UTRAN
default values
default values
EFUST Services 20, 42, 43, 74 and 96 are
list).
EFNASCONFIG MinimumPeriodicSearchTimer set
to 7 minutes
Preamble:
conditions. Subsequent configurations marked “T1” is applied at the point indicated in the Main behaviour description
in Table 6.1.1.7a.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS36.508
Table 6.2.2.1-1.
Parameter Unit Cell 1 Cell 2 Cell 4 Remark

Power level “Off” is
Cell-specific dBm/15kH
T0 "Off" -85 "Off" defined in TS36.508
RS EPRE z
Table 6.2.2.1-1
Power level “Off” is
T1 "Off" -85 -79 defined in TS36.508
RS EPRE z
Table 6.2.2.1-1
T2 -79 "Off" -85
RS EPRE z
ETSI

U-S Message
table 6.1.1.7a.3.2-1
19 UE selects PLMN1 - - - -
seconds, but before 420 seconds from power
on?
Cell 4.
table 6.1.1.7a.3.2-1
seconds from step 20?
Cell 1.
Note 1: Timers in Steps 20 and 28 are derived from the value defined by the MinimumPeriodicSearchTimer
None
6.1.2 Cell selection and reselection

6.1.2.1 Void
6.1.2.2 Cell selection / Qrxlevmin
(1)
with { UE in E-UTRA RRC_IDLE state }
ensure that {
when { a cell fulfils all requirements for a suitable cell except the cell selection criteria
which are not fulfilled (S<0)}
then { the UE does not consider the cell suitable and no camping on this cell can take place }
}
(2)
ensure that {
when { a cell fulfils all requirements for a suitable cell including the cell selection criteria
for a cell which are also fulfilled (S>0)}
then { the UE considers the cell suitable and camps on it }
}
ETSI
References: The conformance requirements covered in the current TC are specified in: TS36.300, clause 10.1.1.1 and
TS 36.304, clause 4.1, 5.1.2.2, 5.2.3.1, 5.2.3.2 and 5.2.8.
[TS 36.300, clause 10.1.1.1]
Cell selection:
- The UE NAS identifies a selected PLMN and equivalent PLMNs;
- The UE searches the E-UTRA frequency bands and for each carrier frequency identifies the strongest cell. It
reads cell system information broadcast to identify its PLMN(s):
- The UE may search each carrier in turn ("initial cell selection") or make use of stored information to shorten
the search ("stored information cell selection").
- The UE seeks to identify a suitable cell; if it is not able to identify a suitable cell it seeks to identify an
acceptable cell. When a suitable cell is found or if only an acceptable cell is found it camps on that cell and
commence the cell reselection procedure:
- A suitable cell is one for which the measured cell attributes satisfy the cell selection criteria; the cell PLMN
is the selected PLMN, registered or an equivalent PLMN; the cell is not barred or reserved and the cell is not
part of a tracking area which is in the list of "forbidden tracking areas for roaming";
- An acceptable cell is one for which the measured cell attributes satisfy the cell selection criteria and the cell
is not barred;
[TS 36.304, clause 4.1]
When a UE is switched on, a public land mobile network (PLMN) is selected by NAS. For the selected PLMN,
associated RAT(s) may be set [5]. The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use
for cell selection and cell reselection.
With the cell selection, the UE searches for a suitable cell of the selected PLMN and chooses that cell to provide
available services, further the UE shall tune to its control channel. This choosing is known as "camping on the cell".
The UE will, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of
the chosen cell and as outcome of a successful Location Registration the selected PLMN becomes the registered PLMN
[5].
[TS 36.304, clause 5.1.2.2]
PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value), provided
that the following high quality criterion is fulfilled:
1. For an E-UTRAN cell, the measured RSRP value shall be greater than or equal to -110 dBm.
Found PLMNs that do not satisfy the high quality criterion, but for which the UE has been able to read the PLMN
identities are reported to the NAS together with the RSRP value. The quality measure reported by the UE to NAS shall
be the same for each PLMN found in one cell.
...
[TS 36.304, clause 5.2.3.1]
The UE shall use one of the following two cell selection procedures:
a) Initial Cell Selection
ETSI
This procedure requires no prior knowledge of which RF channels are E-UTRA carriers. The UE shall scan all
RF channels in the E-UTRA bands according to its capabilities to find a suitable cell. On each carrier frequency,
the UE need only search for the strongest cell. Once a suitable cell is found this cell shall be selected.
[TS 36.304, clause 5.2.3.2]
The cell selection criterion S is fulfilled when:
Srxlev > 0
Where:
Srxlev = Qrxle vmeas – (Qrxlevmin + Qrxlevminoffset) - Pcompensation
Where:
the signalled value QrxlevminOffset is only applied when a cell is evaluated for cell selection as a result of a periodic
search for a higher priority PLMN while camped normally in a VPLMN [5]. During this periodic search for higher
priority PLMN the UE may check the S criteria of a cell using parameter values stored from a different cell of this
higher priority PLMN.
Srxlev Cell Selection RX level value (dB)

Qrxlevmeas Measured cell RX level value (RSRP).
Qrxlevmin Minimum required RX level in the cell (dBm)
Qrxlevminoffset Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a
result of a periodic search for a higher priority PLMN while camped normally in
a VPLMN [5]
Pcompensation max(PEMAX – PUMAX, 0) (dB)
PEMAX Maximum TX power level an UE may use when transmitting on the uplink in
the cell (dBm) defined as PEMAX in [TS 36.101]
PUMAX Maximum RF output power of the UE (dBm) according to the UE power class
as defined in [TS 36.101]
[TS 36.304, clause 5.2.8]
In this state, the UE shall attempt to find an acceptable cell of any PLMN to camp on, trying all RATs that are
supported by the UE and searching first for a high quality cell, as defined in subclause 5.1.2.2.
The UE, which is not camped on any cell, shall stay in this state until an acceptable cell is found.
System Simulator:
- Cell 1
UE:
- None.
Preamble:
Table 6.1.2.2.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cell 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. Configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour
description in Table 6.1.2.2.3.2-2
ETSI
Parameter Unit Cell 1 Remark

T1 Cell-specific RS dBm/ -95 The power level value is such to satisfy SrxlevCell 1 < 0 but the UE is
EPRE 15kH able to read the PLMN identity
z
Qrxlevmin dBm -84
Qrxlevminoffset dB 0
Pcompensation dB 0
T2 Cell-specific RS dBm/ -75 The power level is such that SrxlevCell 1 > 0
EPRE 15kH
z
Note: The downlink signal level uncertainty is specified in TS 36.508 section 4.3.4.1

U-S Message
0A SS re-adjusts the cell-specific reference signal - - - -
level of Cell 1 according to row "T1" in table
6.1.2.2.3.2-1.
0B Wait for 1.1* modification period to allow the - - - -
new system information to take effect.
1 The UE is switched on. - - - -
RRCConnectionRequest on Cell 1 within the
next 60 s?
3 SS re-adjusts the cell-specific reference signal - - - -
level of Cell 1 level according to row "T2" in
table 6.1.2.2.3.2-1.
Table 6.1.2.2.3.3-1: SystemInformationBlockType1 for cell 1 (all steps)
Derivation Path: 36.508 clause 4.4.3.2

cellSelectionInfo SEQUENCE {
q-RxLevMin -42 (-84 dBm)
}
}
6.1.2.2a Cell selection / Qqualmin

(1)
ensure that {
when { a cell fulfils all requirements for a suitable cell except the cell selection criteria
which are not fulfilled (Srxlev>0 AND Squal<0)}
then { the UE does not consider the cell suitable and no camping on this cell can take place }
}
ETSI
(2)
ensure that {
when { a cell fulfils all requirements for a suitable cell including the cell selection criteria
for a cell which are also fulfilled (Srxlev>0 AND Squal>0)}
then { the UE considers the cell suitable and camps on it }
}
TS 36.304, clause 4.1, 5.1.2.2, 5.2.3.1, 5.2.3.2 and 5.2.8.
[TS 36.300, clause 10.1.1.1]
Cell selection:
- The UE may search each carrier in turn (“initial cell selection”) or make use of stored information to shorten
the search (“stored information cell selection”).
part of a tracking area which is in the list of “forbidden tracking areas for roaming”;
is not barred;
[TS 36.304, clause 4.1]
When a UE is switched on, a public land mobile network (PLMN) is selected by NAS. For the selected PLMN,
associated RAT(s) may be set [5]. The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use
for cell selection and cell reselection.
The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of
[5].
[TS 36.304, clause 5.1.2.2]
PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value), provided
that the following high quality criterion is fulfilled:
1. For an E-UTRAN cell, the measured RSRP value shall be greater than or equal to -110 dBm.
Found PLMNs that do not satisfy the high quality criterion, but for which the UE has been able to read the PLMN
identities are reported to the NAS together with the RSRP value. The quality measure reported by the UE to NAS shall
be the same for each PLMN found in one cell.
...
ETSI
[TS 36.304, clause 5.2.3.1]
This procedure requires no prior knowledge of which RF channels are E-UTRA carriers. The UE shall scan all
RF channels in the E-UTRA bands according to its capabilities to find a suitable cell. On each carrier frequency,
the UE need only search for the strongest cell. Once a suitable cell is found this cell shall be selected.
[TS 36.304, clause 5.2.3.2]
Srxlev > 0 AND Squal > 0
where:
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) – Pcompensation
Squal = Qqualmeas – (Qqualmin + Qqualminoffset)
where:
Srxlev Cell selection RX level value (dB)

Squal Cell selection quality value (dB)
Qrxlevmeas Measured cell RX level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qqualmin Minimum required quality level in the cell (dB)
Qrxlevminoffset Offset to the signalled Qrxlevmin taken into account in the Srxlev
evaluation as a result of a periodic search for a higher priority PLMN
while camped normally in a VPLMN [5]
Qqualminoffset Offset to the signalled Qqualmin taken into account in the Squal
Pcompensation max(PEMAX –PPowerClass, 0) (dB)
PEMAX Maximum TX power level an UE may use when transmitting on the
uplink in the cell (dBm) defined as PEMAX in [TS 36.101]
PPowerClass Maximum RF output power of the UE (dBm) according to the UE
power class as defined in [TS 36.101]
[TS 36.304, clause 5.2.8]
In this state, the UE shall attempt to find an acceptable cell of any PLMN to camp on, trying all RATs that are
System Simulator:
- Cell 1
ETSI
UE:
- None.
Preamble:
Table 6.1.2.2a.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cell at
description in Table 6.1.2.2a.3.2-2

T1 Cell-specific RS
dBm/ -95 The power level value is such to satisfy SrxlevCell 1 > 0 and SqualCell
EPRE 15kH 1 < 0 but the UE is able to read the PLMN identity
z
RSRQ dB -32
Noc dBm/ -75
15kH
z
Qrxlevmin dBm -106 (default value in 36.508 Table 4.4.3.2-3)
Qqualmin dB -18
Qqualminoffset dB 0
Pcompensation dB 0
T2 Cell-specific RS dBm/ -65 The power level is such that SrxlevCell 1 > 0 and SqualCell 1 > 0
EPRE 15kH
z
RSRQ dB -5
Noc dBm/ -75
15kH
z

U-S Message
6.1.2.2a.3.2-1.
2 Wait for 1.1* modification period to allow the - - - -
new system information to take effect.
next 60 s?
level of Cell 1 level according to row "T2" in
table 6.1.2.2a.3.2-1.
ETSI
Table 6.1.2.2a.3.3-1: SystemInformationBlockType1 for Cell 1 (all steps)

nonCriticalExtension SEQUENCE {
lateNonCriticalExtension Not present
ims-EmergencySupport-r9 Not present
cellSelectionInfo-v920 SEQUENCE {
q-QualMin-r9 -18 dB
q-QualMinOffset-r9 Not present
}
}
}
}
6.1.2.3 Cell selection / Intra E-UTRAN / Serving cell becomes non-suitable (S<0 or
barred)
(1)
ensure that {
when { the serving cell becomes non-suitable (S<0)and there is a suitable neighbour cell (S>0) }
then { UE selects the suitable neighbourgh cell }
}
(2)
ensure that {
when { the serving cell becomes barred and there is a suitable neighbour cell}
}
TS 36.304, clause 4.1, 5.2.1, 5.2.3.2, 5.2.4.6 and 5.3.1.
[TS 36.300, clause 10.1.1.1]
Cell selection:
ETSI
is not barred;
[TS 36.304, clause 4.1]
[5].
If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it.
If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is
performed.
[TS 36.304, clause 5.2.1]
When camped on a cell, the UE shall regularly search for a better cell according to the cell reselection criteria. If a
better cell is found, that cell is selected.
[TS 36.304, clause 5.2.3.2]
Srxlev > 0
Where:
Srxlev = Qrxlevmeas – (Qrxlevmin – Qrxlevminoffset) - Pcompensation
Where:

PUMAX Maximum RF output power of the UE (dBm) according to the UE
[TS 36.304, clause 5.2.4.6]
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
- the new cell is better ranked than the serving cell during a time interval TreselectionRAT;
- more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 36.304, clause 5.3.1]
Cell status and cell reservations are indicated in the SystemInformationBlockType1 [3] by means of two Information
Elements:
ETSI
- cellBarred (IE type: "barred" or "not barred")

In case of multiple PLMNs indicated in SIB1 sharing, this IE is common for all PLMNs
...
When cell status is indicated as "not barred" and "not reserved" for operator use,
- All UEs shall treat this cell as candidate during the cell selection and cell re-selection procedures.
...
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
- The UE is not permitted to select/re-select this cell, not even for emergency calls.
- The UE shall select another cell according to the following rule:
- If the cell is a CSG cell:
- the UE may select another cell on the same frequency if the selection/reselection criteria are fulfilled.
- else
- If the IE intraFreqReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to

"allowed", the UE may select another cell on the same frequency if re-selection criteria are fulfilled.
- The UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.
- If the IE intraFreqReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to "not

allowed" the UE shall not re-select a cell on the same frequency as the barred cell.
- The UE shall exclude the barred cell and the cells on the same frequency as a candidate for cell
selection/reselection for 300 seconds.
System Simulator:
- Cell 1 and Cell 2 have different tracking areas according to table 6.0.1-2.
UE:
None.
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell 1(serving cell) according to [18].
Table 6.1.2.3.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
description in Table 6.1.2.3.3.2-2.
ETSI
Parameter Unit Cell 1 Cell 2 Remark

dBm/ SrxlevCell 1 < 0 (NOTE 1)
Cell-specific RS EPRE 15kH "Off" -85
T1
z
Srxlev* dB - 25 Cell 2 becomes the strongest cell
Cell-specific RS EPRE dBm/ -91 -85 SrxlevCell 2 > 0, SrxlevCell 1 > 0 , RCell 1 < RCell 2
15kH
T2 z
Srxlev* dB 19 25 Cell 1 becomes suitable
cellBarred - notBarred barred Serving cell becomes barred
NOTE: If the UE fails the test because of a failure to detect and reselect to a right cell, then the operator may re-run
the test.

U-S Message
level of Cell 1 and Cell 2 according to row "T1"
in table 6.1.2.3.3.2-1.
Cell 2?
3 SS changes Cell 1 signal level and SIB1 IE <-- Paging - -
cellBarred according to row "T2" in table
6.1.2.3.3.2-1 and transmits a Paging message
including systemInfoModification. The
systemInfoValueTag in the
SystemInformationBlockType1 is increased.
Cell 1?
Table 6.1.2.3.3.3-1: Void
Table 6.1.2.3.3.3-2: SystemInformationBlockType1 for cells 1 and 2 (preamble and all steps, Table
6.1.2.3.3.2-2)

}
systemInfoValueTag The value is increased in
step 3
}
ETSI
Table 6.1.2.3.3.3-3: SystemInformationBlockType3 for cells 1 and 2 (Preamble and all steps, table
6.1.2.3.3.2-2)
Derivation Path: 36.508 clause 4.4.3.3, Table 4.4.3.3-2

q-Hyst dB0
}
intraFreqCellReselectionInfo SEQUENCE {
t-ReselectionEUTRA 7
}
}
Table 6.1.2.3.3.3-4: SystemInformationBlockType1 for cell 2 (step 3, Table 6.1.2.3.3.2-2)

cellAccessRelatedInfo SEQUENCE {
cellBarred barred
intraFreqReselection allowed
}
systemInfoValueTag 1 Previous value is
0
}
Table 6.1.2.3.3.3-5: Paging (step 3, Table 6.1.2.3.3.2-2)

Paging ::= SEQUENCE {
pagingRecordList Not present
systemInfoModification True
etws-PrimaryNotificationIndication Not present
nonCriticalExtension SEQUENCE {} Not present
}
6.1.2.3a Cell selection / Intra E-UTRAN / Serving cell becomes non-suitable (Srxlev >
0 and Squal < 0)
(1)
ensure that {
when { the serving cell becomes non-suitable (Srxlev > 0 and Squal < 0)and there is a suitable
neighbour cell (Srxlev > 0 and Squal > 0) }
}
TS 36.304, clause 4.1, 5.2.1, 5.2.3.2 and 5.2.4.6.
[TS 36.300, clause 10.1.1.1]
Cell selection:
ETSI
- The UE may search each carrier in turn (“initial cell selection”) or make use of stored information to shorten
the search (“stored information cell selection”).
part of a tracking area which is in the list of “forbidden tracking areas for roaming”;
is not barred;
[TS 36.304, clause 4.1]
[5].
performed.
[TS 36.304, clause 5.2.1]
better cell is found, that cell is selected. The change of cell may imply a change of RAT. Details on performance
requirements for cell reselection can be found in [10].
[TS 36.304, clause 5.2.3.2]
Srxlev > 0 AND Squal > 0
where:
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) – Pcompensation
Squal = Qqualmeas – (Qqualmin + Qqualminoffset)
where:
ETSI
Srxlev Cell selection RX level value (dB)

Squal Cell selection quality value (dB)
Qrxlevmeas Measured cell RX level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qqualmin Minimum required quality level in the cell (dB)
Qqualminoffset Offset to the signalled Qqualmin taken into account in the Squal
Pcompensation max(PEMAX –PPowerClass, 0) (dB)
PPowerClass Maximum RF output power of the UE (dBm) according to the UE
[TS 36.304, clause 5.2.4.6]
System Simulator:
UE:
None.
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell 1(serving cell) according to [18].
Table 6.1.2.3a.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
texts in this clause. Configurations marked "T1" is applied at the points indicated in the Main behaviour description in
Table 6.1.2.3a.3.2-2.

dBm/1 SrxlevCell 1 > 0 and SqualCell 1 < 0
Cell-specific RS EPRE -97 -85
5kHz
RSRQ dB -15.28 -3.28
Qrxlevmin dBm -106 -92
T1 Qrxlevminoffset dB 0 0
Qqualmin dB -5 -20
Qqualminoffset dB 0 0
Pcompensation dB 0 0
Srxlev* dB 9 7 Cell 2 is suitable cell
Squal* dB -10.28 16.72 Squal = Qqualmeas – (Qqualmin + Qqualminoffset)
Noc dBm/1 Off Off
5kHz
ETSI

U-S Message
level of Cell 1 and Cell 2 according to row "T1"
in table 6.1.2.3a.3.2-1.
Cell 2?
Table 6.1.2.3a.3.3-0: Conditions for table 6.1.2.3a.3.3-1, 6.1.2.3a.3.3-2
Condition descriptions
Cell 1
This condition applies to system information transmitted on Cell 1.
Cell 2
Table 6.1.2.3a.3.3-1: SystemInformationBlockType1 for Cell 1 and 2 (all steps, Table 6.1.2.3a.3.2-2)

q-RxLevMin -53 (-106 dBm) Cell 1
}
q-QualMin-r9 -5 dB Cell 1
}
}
}
}
ETSI
Table 6.1.2.3a.3.3-2: SystemInformationBlockType3 for Cell 1 and 2 (all steps, table 6.1.2.3a.3.2-2)

q-Hyst dB0
}
}
lateNonCriticalExtension {
s-IntraSearch-v920 SEQUENCE {} Not present
s-NonIntraSearch-v920 SEQUENCE {} Not present
threshServingLowQ-r9 Not present
}
}
6.1.2.4 Cell reselection

(1)
ensure that {
when { UE detects the cell ranked as the best cell }
then { UE reselects the new cell }
}
5.2.4.6.
[TS 36.304, clause 5.2.4.2]
When evaluating for reselection purposes cell selection criterion or SnonServingCell,x, the UE shall use parameters
provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
- If Sintrasearch is sent in the serving cell and SServingCell > Sintrasearch, UE may choose to not perform intra-frequency
measurements.
- If SServingCell <= Sintrasearch, or Sintrasearch is not sent in the serving cell UE shall perform intra-frequency
measurements.
- The UE shall apply the following rules for E-UTRAN inter-frequencies and inter-RAT frequencies which are
indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:
- For an E-UTRAN inter-frequency or inter-RAT frequency with a reselection priority higher than the
reselection priority of the current E-UTRA frequency the UE shall perform measurements of higher priority
E-UTRAN inter-frequency inter-RAT frequencies according to [10].
- For an E-UTRAN inter-frequency with an equal or lower reselection priority than the reselection priority of
the current E-UTRA frequency and for inter-RAT frequency with lower reselection priority than the
reselection priority of the current E-UTRAN frequency:
- If Snonintrasearch is sent in the serving cell and SServingCell > Snonintrasearch UE may choose not to perform
measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority.
ETSI
- If SServingCell <= Snonintrasearch or Snonintrasearch is not sent in the serving cell the UE shall perform
measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority
according to [10].
Where SServingCell is the Srxlev-value of the serving cell.
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
Rs = Q meas,s + Qhyst s
Rn = Qmeas,n - Qoffset
where:
Qmeas RSRP measurement quantity used in cell reselections.

Qoffset For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid,
otherwise this equals to zero.
For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if
Qoffsets,n is valid, otherwise this equals to Qoffsetfrequency.
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2, but may
exclude all CSG cells that are known by the UE to be not allowed.
The cells shall be ranked according to the R criteria specified above, deriving Qmeas,n and Qmeas,s and calculating the R
values using averaged RSRP results.
If a cell is ranked as the best cell the UE shall perform cell re-selection to that cell. If this cell is found to be not-
suitable, the UE shall behave according to subclause 5.2.4.4.
- the new cell is better ranked than the serving cell during a time interval TreselectionRAT
System Simulator:
- Cell 1 and Cell 2.
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) on Cell 1(serving cell) according to [18].
various time instants of the test execution. The configuration marked "T1" is applied at the point indicated in the Main
behaviour description in Table 6.1.2.4.3.2-2.
ETSI

T1 Cell- dBm/ -85 -79 The power level values are assigned to
specific RS 15kH satisfy RCell 1 < RCell 2.
EPRE z

U-S Message
1 The SS changes Cell 2 level according to the - - - -
row "T1" in table 6.1.2.4.3.2-1.
Cell 2?
Table 6.1.2.4.3.3-1: Void
6.1.2.5 Cell reselection for interband operation

(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell on the different frequency
band }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.1,
5.2.4.2 and 5.2.4.5.
[TS 36.304, clause 5.2.4.1]
Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the
system information, in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell
(re)selection. In the case of system information, an E-UTRAN frequency or inter-RAT frequency may be listed without
providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in
dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any
cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves
priorities provided by dedicated signalling unless specified otherwise. When the UE in camped normally state, has only
dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest
priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG
cell, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight
network configured values), irrespective of any other priority value allocated to this frequency. The UE shall delete
priorities provided by dedicated signalling when:
- the UE enters RRC_CONNECTED state; or
- the optional validity time of dedicated priorities (T320) expires; or
- a PLMN selection is performed on request by NAS [5].
NOTE: Equal priorities between RATs are not supported.
The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are
given in system information and for which the UE has a priority provided.
ETSI
The UE shall not consider any black listed cells as candidate for cell reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e., T320 in E-
UTRA, T322 in UTRA and T3230 in GERAN), if configured, at inter-RAT cell (re)selection.
NOTE: The network may assign dedicated cell reselection priorities for frequencies not configured by system
information.
[TS 36.304, clause 5.2.4.2]
measurements.
measurements.
E-UTRAN inter-frequency or inter-RAT frequencies according to [10].
- If SServingCell <= Snonintrasearchor Snonintrasearch is not sent in the serving cell the UE shall perform
according to [10].
[TS 36.304, clause 5.2.4.5]
Criteria 1: the SnonServingCell,x of a cell on evaluated frequency is greater than Threshx, high during a time interval
TreselectionRAT;
Cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than serving frequency shall
be performed if:
- A cell of a higher priority E-UTRAN frequency or inter-RAT frequency fulfils criteria 1; and
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based on ranking for Intra-frequency cell
reselection as defined in sub-clause 5.2.4.6.
Cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than serving frequency shall
be performed if:
- No cell on a higher priority E-UTRAN frequency or inter-RAT frequency than serving frequency fulfils the
criteria 1; and
- No cell on serving frequency or on an equal priority E-UTRAN frequency fulfils the criteria in 5.2.4.6; and
- SServingCell < Threshserving, low and the SnonServingCell,x of a cell of a lower priority E-UTRAN frequency or inter-RAT
frequency is greater than Threshx, low during a time interval TreselectionRAT; and
ETSI
For GERAN, UTRAN, and E-UTRAN, SnonServingCell,x is the Srxlev-value of an evaluated cell. For UTRAN FDD, Squal
is higher than 0, as defined in [8]. For cdma2000 RATs, SnonServingCell,x is equal to FLOOR(-2 x 10 x log10 Ec/Io) in units
of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, Threshx, high and Threshx, low are equal to -1 times the values signalled for the corresponding
parameters in the system information.
In all the above criteria the value of TreselectionRAT is scaled when the UE is in the medium or high mobility state as
defined in subclause 5.2.4.3.1. If more than one cell meets the above criteria, the UE shall reselect a cell ranked as the
best cell among the cells meeting the criteria on the highest priority frequencies or the highest priority RAT if the
highest priority RAT is E-UTRA according to criteria defined in 5.2.4.6.
System Simulator:
- Cell 1, cell 10.
UE:
None.
Preamble:

T1 Cell- dBm/ -85 -73 Cell 10 become stronger than Threshx, high.
specific RS 15kH
EPRE z

U-S Message
1 The SS changes Cell 10 power level according - - - -
to the row "T1" in table 6.1.2.5.3.2-1.
Cell 10?
Table 6.1.2.5.3.3-0: Conditions for specific message contents

in Tables 6.1.2.5.3.3-1 and 6.1.2.5.3.3-2
Condition Explanation
Cell 1 This condition applies to system information transmitted on Cell 1.
ETSI
Table 6.1.2.5.3.3-1: SystemInformationBlockType3 for Cell 1 and Cell 10 (preamble and all steps,
Table 6.1.2.5.3.2-2)
Derivation path: 36.508 table 4.4.3.3-2

cellReselectionServingFreqInfo SEQUENCE {
cellReselectionPriority 1 Cell 1
5 Cell 10
}
}
Table 6.1.2.5.3.2-2)

dl-CarrierFreq Same downlink EARFCN Cell 1
as used for Cell 10
Same downlink EARFCN Cell 10
as used for Cell 1
threshX-High 10 20dB
1 Cell 10
}
}
6.1.2.6 Cell reselection using Qhyst, Qoffset and Treselection

(1)
with { UE in E-UTRA RRC_IDLE state, and the UE is not in high mobility state }
ensure that {
when { Qhyst is non-zero or its value changes in system information }
then { UE reselects the highest ranked cell taking the actual Qhyst value into account}
}
(2)
ensure that {
when { cell reselection criteria are fulfilled during a time interval Treselection }
then { UE reselects the highest ranked cell }
}
(3)
ensure that {
when { Qoffset is non-zero or its value changes in system information }
then { UE reselects the highest ranked cell taking the actual Qoffset value into account }
}
TS 36.304, clauses 5.2.1 and 5.2.4.6 and TS 36.331 clause 6.3.1.
[TS 36.300, clause 10.1.1.2]
ETSI
UE in RRC_IDLE performs cell reselection. The principles of the procedure are the following:
- The UE makes measurements of attributes of the serving and neighbour cells to enable the reselection process:
- There is no need to indicate neighbouring cell in the serving cell system information to enable the UE to
search and measure a cell i.e. E-UTRAN relies on the UE to detect the neighbouring cells;
- For the search and measurement of inter-frequency neighbouring cells, only the carrier frequencies need to be
indicated;
- Measurements may be omitted if the serving cell attribute fulfils particular search or measurement criteria.
- Cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria which
involves measurements of the serving and neighbour cells:
- Intra-frequency reselection is based on ranking of cells;
...
- Cell reselection parameters are applicable for all UEs in a cell, ...
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.4.6]
Rs = Qmeas,s + QHyst
where:

If a cell is ranked as the best cell the UE shall perform cell re-selection to that cell.
...
- the new cell is better ranked than the serving cell during a time interval TreselectionRAT,
[TS 36.331, clause 6.3.1]
The IE SystemInformationBlockType4 contains neighbouring cell related information relevant only for intra-frequency
cell re-selection. The IE includes cells with specific re-selection parameters as well as blacklisted cells.
ETSI
System Simulator:
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) on Cell 1 according to [18].
texts in this clause. Configurations marked "T1", "T2", "T3", "T4", "T5", "T6" and "T7" are applied at the points
indicated in the Main behaviour description in Table 6.1.2.6.3.2-2.
Table 6.1.2.6.3.2-1: Time instances of cell power level and parameter change
Ti Parameter Unit Cell 1 Cell 2 Remark

dBm/ Cell 2 becomes stronger than Cell 1
Cell-specific RS
T1 15kH -91 -85 but Cell 1 remains the highest ranked
EPRE
z one due to QhystsCell1
Qhysts QhystsCell1 change causes Cell 2 to
T2 dB 0 0
become highest ranked cell
dBm/ Cell 1 becomes the strongest and
Cell-specific RS
15kH -85 -91 highest ranked one due to
T3 EPRE
z
Qoffsets,n dB 24 0 Qoffsets,nCell2 remains zero
dBm/ Cell 1 becomes weaker but it remains
Cell-specific RS
T4 15kH -91 -85 the highest ranked one due to
EPRE
z Qoffsets,nCell 1
Qoffsets,n Cell 2 becomes the highest ranked
T5 dB 0 0
one due to Qoffsets,nCell1 change
dBm/ Cell 1 becomes the highest ranked
Cell-specific RS
15kH -85 -91 one
T6 EPRE
z
TreselectionEUTRAN s 7 0
dBm/ Cell 2 becomes the highest ranked
Cell-specific RS
T7 15kH -91 -85 cell
EPRE
z
Note: The total test tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1) and
relative UE measurement accuracy of RSRP (TS 36.133 clause 9.1.2.2).
ETSI

U-S Message
0 Wait for 1 second to allow UE to enter - - - -
RRC_IDLE state on cell 1.
levels according to row "T1" in table
6.1.2.6.3.2-1.
next 10s?
3 SS resets QhystsCell1 according to row "T2" in <-- Paging - -
table 6.1.2.6.3.2-1 and notifies UE of the
system information change. The
Cell 2? (Note 1)
5 Void - - - -
5A SS changes Qoffsets,nCell1 according to rows <-- Paging - -
"T3" in table 6.1.2.6.3.2-1 and sends
notification of the system information change.
The systemInfoValueTag in the
5B Wait for 2.1* modification period (Note 2) to - - - -
allow the new system information to take
effect.
5C SS re-adjusts cell-specific reference signal - - - -
levels according to rows "T3" in table
6.1.2.6.3.2-1.
6 Wait until there is any RRCConnectionRequest --> RRCConnectionRequest - -
send from the UE on Cell 1.
Cell 1.
A RRC_IDLE state on cell 1.
12 SS re-adjusts cell-specific reference signal - - - -
6.1.2.6.3.2-1.
next 10s?
14 SS resets Qoffsets,nCell1 according to row "T5" <-- Paging - -
in table 6.1.2.6.3.2-1 and notifies UE of the
system information change. The
Cell 2? (Note 1)
16 Void - - - -
16 SS changes TreselectionEUTRAN Cell 1 <-- Paging - -
A according to rows "T6" in table 6.1.2.6.3.2-1
and sends notification of the system
information change. The systemInfoValueTag
in the SystemInformationBlockType1 is
increased.
ETSI
16 Wait for 2.1* modification period (Note 2) to - - - -

B allow the new system information to take
effect.
C levels according to rows "T6" in table
6.1.2.6.3.2-1.
17 Wait until there is any RRCConnectionRequest --> RRCConnectionRequest - -
send from the UE on Cell 1
Cell 1.
A RRC_IDLE state on cell 1.
levels according to rows "T7" in table
6.1.2.6.3.2-1.
next 6s?
next 12s?
Cell 2.
NOTE: The UE performs a TAU procedure.
NOTE 1: The time interval in step 4 and 15 is set to cover TevaluateFDD,intra (TS 36.133 clause 4.2.2.3) + 1280
ms for DRX cycle + 1280 ms for system information block type scheduling. The timer tolerances are
taken into account according to [18].
NOTE 2: The wait time of 2.1* modification period in step 5B and 16B is to allow for the network to paging the
system information change during the next modification period, and update the system information at the
subsequent modification period. UE should acquire the updated system information within 100ms of the
start of modification period.
Table 6.1.2.6.3.3-1: Void
Table 6.1.2.6.3.3-2: SystemInformationBlockType1 for cells 1 (preamble and all steps, Table
6.1.2.6.3.2-2)

schedulingInformation ::= SEQUENCE (SIZE
(1..maxSI-Message)) OF SEQUENCE {}
systemInfoValueTag The value is increased by
1 in step 3, step 5A, step
14 and step 16A
}
Table 6.1.2.6.3.3-3: SystemInformationBlockType3 for cell 1 (preamble, table 6.1.2.6.3.2-2)

q-Hyst dB24 QhystsCell1
}
}
ETSI
Table 6.1.2.6.3.3-4: SystemInformationBlockType3 for cell 1 (step 3, table 6.1.2.6.3.2-2)

}
}
Table 6.1.2.6.3.3-5: SystemInformationBlockType3 for cell 1 (step 16A, table 6.1.2.6.3.2-2)

}
t-ReselectionEUTRA 7 seconds
}
}
Table 6.1.2.6.3.3-6: SystemInformationBlockType4 for cell 1 (step 5A, table 6.1.2.6.3.2-2)

intraFreqNeighCellList SEQUENCE (SIZE
(1..maxCellIntra)) OF SEQUENCE {
physCellId [1] Physical cell identity of
Cell 2
q-OffsetCell [1] dB24 Qoffsets,nCell 1
}
}
Table 6.1.2.6.3.3-7: SystemInformationBlockType4 for cell 1 (step 14, table 6.1.2.6.3.2-2)

intraFreqNeighCellList SEQUENCE (SIZE
(1..maxCellIntra)) OF SEQUENCE {
physCellId [1] Physical cell identity of
Cell 2
q-OffsetCell [1] dB0 Qoffsets,nCell 1
}
}
6.1.2.7 Cell reselection / Equivalent PLMN

(1)
Location Registration procedure }
ensure that {
when { a suitable neighbour cell on an equivalent PLMN becomes better ranked than the suitable
Serving cell }
then { UE reselects to this equivalent PLMN cell. }
}
ETSI
(2)
ensure that {
when { the Serving cell becomes unsuitable due to S<0 and a suitable cell exists on an equivalent
PLMN }
}
(3)
ensure that {
when { the UE evaluates cells for reselection }
then { UE ignores suitable cells for which the UE has no reselection priority provided. }
}
23.122 clause 4.4.3.
[TS 36.304, clause 5.2.4.1]
UE shall only perform reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in
system information and for which the UE has a priority provided.
[TS 23.122, clause 4.4.3]
The Mobile Equipment stores a list of "equivalent PLMNs". This list is replaced or deleted at the end of each location
update procedure, routing area update procedure and GPRS attach procedure. The stored list consists of a list of
equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that downloaded the
list. All PLMNs in the stored list, in all access technologies supported by the PLMN, are regarded as equivalent to each
other for PLMN selection, cell selection/re-selection and handover.
System Simulator:
- Three inter-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
Cell PLMN name

1 PLMN1
12 PLMN2
13 PLMN3
- All cells are high quality.
- All cells are suitable cells.
UE:
6.1.2.7.3.1-2.
ETSI

Preamble:
- The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508 clause 4.5.2.3 except that
the ATTACH ACCEPT message indicates PLMN3 in the Equivalent PLMN list as described in Table
6.1.2.7.3.3-1.
Table 6.1.2.7.3.2–1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configurations marked “T1” and “T2” are applied at the points indicated in the Main behaviour
description in Table 6.1.2.7.3.2-2. `

T0 RS EPRE dBm/15kHz -67 -82 -97 All cells S>0
T1 RS EPRE dBm/15kHz -115 -82 -97 Cell 1 S < 0 as described in TS

36.508 clause 6.2.2.1
Note 1: The default values (including “not present”) for all other parameters influencing cell reselection are suitable
for this test. The values are defined in TS 36.508 clauses 4.4.3.2 and 4.4.3.3.
ETSI

U-S Message
RRCConnectionRequest within the next 100
seconds?
2 SS adjusts cell levels according to row T1 of table - - - -
6.1.2.7.3.2-1.
3 Check: Does the test result of generic test - - 2 P
indicate that the UE is camped on E-UTRAN Cell
13?
NOTE: The UE performs a TAU procedure with
PLMN1 and PLMN2 listed as an Equivalent PLMN
in the TRACKING AREA UPDATE ACCEPT
message, and the RRC connection is released.
4 Void - - - -
12?
6 Void - - - -
6.1.2.7.3.2-1.
8 Check: Does the UE send an --> RRCConnectionRequest 1,3 F
seconds?
6.1.2.7.3.2-1.
10 Void - - - -
13?
Note 1: In Steps 1 and 8, a wait time long enough to ensure that the UE has detected, measured and evaluated the
neighbour inter-frequency cells is provided, see 36.133 clause 4.2.2.4.
Note 2: In Step 11, the UE moves to Cell 13 because no reselection priority is defined for Cell 1, see Table
6.1.2.7.3.3-6.

Table 6.1.2.7.3.3-2: TRACKING AREA UPDATE ACCEPT for Cell 13 (steps 3 & 11 , Table 6.1.2.7.3.2-2)

Equivalent PLMNs PLMN1, 2
ETSI

Table 6.1.2.7.3.3-4: Void
Table 6.1.2.7.3.3-5: Void
6.1.2.7.3.2-2)

interFreqCarrierFreqList SEQUENCE (SIZE 2 entries
as used for Cell 1
cellReselectionPriority[1] Not present UE does not have
a priority for
frequency of Cell 1
as used for Cell 13
}
}
6.1.2.7.3.2-2)

as used for Cell 1
cellReselectionPriority[1] Not present UE does not have
a priority for
frequency of Cell 1
as used for Cell 12
}
}
6.1.2.7a Cell reselection / Equivalent PLMN / Single Frequency operation

(1)
ensure that {
when { a suitable neighbour cell on an equivalent PLMN becomes better ranked than the suitable
Serving cell }
}
ETSI
(2)
ensure that {
when { the Serving cell becomes unsuitable due to S<0 and a suitable cell exists on an equivalent
PLMN }
}

System Simulator:
- Three intra-frequency multi-PLMN cells.
Cell PLMN name

1 PLMN1
2 PLMN2
4 PLMN3
- All cells are suitable cells.
UE:
6.1.2.7a.3.1-2.

Preamble:
- The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508 clause 4.5.2.3 except that
the ATTACH ACCEPT message indicates PLMN3 in the Equivalent PLMN list as described in Table
6.1.2.7a.3.3-1.
Table 6.1.2.7a.3.2–1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configurations marked “T1” and “T2” are applied at the points indicated in the Main behaviour
description in Table 6.1.2.7a.3.2-2. `
ETSI
Paramete Unit Cell 1 Cell 2 Cell 4 Remarks

r
T1 RS EPRE dBm/15kHz -115 -88 -82 Cell 1 S < 0 as described in TS

36.508 clause 6.2.2.1
T2 RS EPRE dBm/15kHz -115 -82 -88
Note 1: The default values (including “not present”) for all other parameters influencing cell reselection are suitable
for this test. The values are defined in TS 36.508 clauses 4.4.3.2 and 4.4.3.3.

U-S Message
seconds?
6.1.2.7a.3.2-1.
4?
6.1.2.7a.3.2-1.
2?
6.1.2.7a.3.2-1.
4?
Note 1: In Step 1, a wait time long enough to ensure that the UE has detected, measured and evaluated the neighbour
intra-frequency cells is provided, see 36.133 clause 4.2.2.3.

ETSI
Table 6.1.2.7a.3.3-2: TRACKING AREA UPDATE ACCEPT for Cell 4 (steps 3 & 7 , Table 6.1.2.7a.3.2-2)


6.1.2.8 Cell reselection using cell status and cell reservations / Access control class
0 to 9
(1)
with { UE camped normally in state E-UTRA RRC_IDLE and UE fitted with a USIM with access class 0..9}
ensure that {
when { a higher ranked cell is found with cell status "barred" }
then { UE does not attempt to reselect to the higher ranked cell }
}
(2)
with { UE camped normally in state E-UTRA RRC_IDLE and UE fitted with a USIM with access class 0..9}
ensure that {
when { a higher ranked cell is found "reserved" for Operator use }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clauses 5.2.4.4 and
5.3.1.
[TS 36.304, clause 5.2.4.4]
For the highest ranked cell (including serving cell) according to cell reselection criteria specified in subclause 5.2.4.6,
the UE shall check if the access is restricted according to the rules in subclause 5.3.1.
If that cell and other cells have to be excluded from the candidate list, as stated in subclause 5.3.1, the UE shall not
consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes.
[TS 36.304, clause 5.3.1]
Elements:

…
- cellReservedForOperatorUse (IE type: "reserved" or "not reserved")

…
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
- ...
ETSI
- UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 and UEs with AC 11 or 15 not operating in
theirHLPMN/EHPLMN shall behave as if the cell status is “barred” in case the cell is “reserved for operator
use” for the PLMN the UE is currently registered with.
NOTE 1: ...
- ...
- else
- If the IE intraFrequencyReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to


System Simulator:
- Three inter-frequency cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting default NAS
parameters as indicated in TS 36.508 Table 4.4.2-2, except that TAC values use the codes in Table 6.0.1-2.
- SIB 1 of Cell 3 and Cell 6 indicate cellBarred=barred.
- Each cell has only a single PLMN identity.
- The cell power levels are configured as shown in Table 6.1.2.8.3.1-1.
Table 6.1.2.8.3.1-1: Cell power configuration

(min UL)
RS EPRE dBm/15kHz -97 -82 -67 S>0 for all cells
Note 1: The default values (including “not present”) for all other parameters influencing cell reselection are
suitable for this test. The values are defined in TS36.508 clauses 4.4.3.2 and 4.4.3.3
UE:
6.1.2.8.3.1-2.
ETSI
Table 6.1.2.8.3.1–2: USIM Configuration
USIM field Value

EFACC Type “A” as defined in TS34.108 clause
8.3.2.15
Preamble:

U-S Message
1 SS adjusts SIB1 of Cell 3 to indicate - - - -
cellBarred=notBarred
Cell 3?
3 The SS notifies the UE of change of System <-- Paging - -
Information. SS adjusts SIB1 of Cell 3 to
indicate cellBarred=barred. (Cell 3 and Cell 6
are now both barred).
4 Void - - - -
Cell 1?
6 SS adjusts SIB1 of both Cell 3 and Cell 6: Cell - - - -
3 indicates cellBarred=notBarred; Cell 6
indicates cellBarred=notBarred and
cellReservedForOperatorUse = reserved.
Cell 3?
indicate cellReservedForOperatorUse =
reserved.
9 Void - - - -
Cell 1?

in Tables 6.1.2.8.3.3-1, 6.1.2.8.3.3-2, 6.1.2.8.3.3-4 and 6.1.2.8.3.3-5
ETSI
Table 6.1.2.8.3.3-1: SystemInformationBlockType1 for Cell 3 and Cell 6 (pre-test conditions, Table
6.1.2.8.3.2-1)

SystemInformationBlockType1 ::=
SEQUENCE {
plmn-IdentityList SEQUENCE (SIZE (1..6)) 1 entry
OF SEQUENCE {
cellReservedForOperatorUse notReserved Cell 3
Cell 6
}
cellBarred barred Cell 3
Cell 6
}
}
Table 6.1.2.8.3.3-2: SystemInformationBlockType1 for Cell 3 and Cell 6 (step 1, Table 6.1.2.8.3.2-1)

plmn-IdentityList SEQUENCE (SIZE (1..6)) OF 1 entry
SEQUENCE {
Cell 6
}
cellBarred notBarred Cell 3
barred Cell 6
}
systemInfoValueTag 1 Cell 3
0 Cell 6
}
Table 6.1.2.8.3.3-2A: SystemInformationBlockType1 for Cell 3 and Cell 6 (step 3, Table 6.1.2.8.3.2-1)

SEQUENCE {
Cell 6
}
Cell 6
}
0 Cell 6
}
ETSI
Table 6.1.2.8.3.3-3: Paging (steps 3 & 8, Table 6.1.2.8.3.2-1)
Derivation Path: 36.508 Table 4.6.1-7

systemInfoModification true
etws-Indication Not present
}

SEQUENCE {
reserved Cell 6
}
Cell 6
}
1 Cell 6
}

SEQUENCE {
cellReservedForOperatorUse reserved Cell 3
Cell 6
}
Cell 6
}
1 Cell 6
}
6.1.2.8a Cell reselection using cell status and cell reservations / Access control class
0 to 9 / Single Frequency operation
Same Conformance requirement as in clause 6.1.2.8.2
ETSI
System Simulator:
- Three intra-frequency cells Cell 1, Cell 2 and Cell 4 as specified in TS36.508 clause 4.4.1.2 are configured
broadcasting default NAS parameters as indicated in TS 36.508 Table 4.4.2-2, except that TAC values use the
codes in Table 6.0.1-2.
- SIB 1 of Cell 4 indicates cellBarred=barred.
- The cell power levels are configured as shown in Table 6.1.2.8a.3.1-1.
Table 6.1.2.8a.3.1-1: Cell power configuration

T1 RS EPRE dBm/15kH -73 -67 -97 Cell 2 is best ranked cell
z
z
UE:
6.1.2.8a.3.1-2.
Table 6.1.2.8a.3.1–2: USIM Configuration
USIM field Value

EFACC Type “A” as defined in TS34.108 clause
8.3.2.15
Preamble:
ETSI

U-S Message
1 SS adjusts cell power levels according to row - - - -
T1 of table 6.1.2.8a.3.1–1.
Cell 2?
5 Check: Does the test result of generic - - 1 -
indicate that the UE does not respond to
paging in cell 2 when paged with S-TMSI
allocated to UE with CN domain indicator set
to "PS"?
SS adjusts cell levels according to row T2 of
table 6.1.2.8a.3.1–1
paging in cell 2 when paged with S-TMSI
to "PS"?
indicate cellReservedForOperatorUse =
notReserved.
Cell 4?
Note : In steps 6-11, UE will have barred all the cells for 300 seconds hence may take more than 300 seconds to
initiate the TAU procedure. The default value of intraFreqReselection is 'not allowed' in 36.508 table 4.4.3.2-3.
Table 6.1.2.8a.3.3-0: Conditions for specific message contents

in Tables 6.1.2.8a.3.3-4
ETSI
Table 6.1.2.8a.3.3-1: SystemInformationBlockType1 for Cell 4 (pre-test conditions, Table 6.1.2.8a.3.2-

1)

SEQUENCE {
OF SEQUENCE {
cellReservedForOperatorUse notReserved
}
cellBarred barred
}
}
Table 6.1.2.8a.3.3-2: Void
Table 6.1.2.8a.3.3-2A: SystemInformationBlockType1 for Cell 2 (step 3, Table 6.1.2.8a.3.2-1)

SEQUENCE {
}
cellBarred barred
}
systemInfoValueTag 1
}
Table 6.1.2.8a.3.3-3: Paging (steps 3 & 10, Table 6.1.2.8a.3.2-1)

}
Table 6.1.2.8a.3.3-4: SystemInformationBlockType1 for Cell 2 and Cell 4 (step 6, Table 6.1.2.8a.3.2-1)

SEQUENCE {
reserved Cell 4
}
Cell 4
}
1 Cell 4
}
ETSI
Table 6.1.2.8a.3.3-5: SystemInformationBlockType1 for Cell 4 (step 10, Table 6.1.2.8a.3.2-1)

SEQUENCE {
}
cellBarred notBarred
}
}
6.1.2.9 Cell reselection using cell status and cell reservations / Access control class
11 to 15
(1)
with { UE camped normally in state E-UTRA RRC_IDLE and UE fitted with a USIM with access class 0..9
and access classes 11..15 inclusive }
ensure that {
when { a higher ranked cell is found with cell status "barred" }
}
(2)
with { UE camped normally in state E-UTRA RRC_IDLE and UE fitted with a USIM with access class 0..9
and access classes 11..15 inclusive }
ensure that {
when { a higher ranked cell is found "reserved" for Operator use }
then { UE re-selects to the higher ranked cell }
}
5.3.1.
[TS 36.304, clause 5.2.4.4]
For the highest ranked cell (including serving cell) according to cell reselection criteria specified in subclause 5.2.4.6,
the UE shall check if the access is restricted according to the rules in subclause 5.3.1.
If that cell and other cells have to be excluded from the candidate list, as stated in subclause 5.3.1, the UE shall not
consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes.
[TS 36.304, clause 5.3.1]
Elements:

…
- cellReservedForOperatorUse (IE type: "reserved" or "not reserved")

…
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
ETSI
- UEs assigned to Access Class 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate
during the cell selection and reselection procedures if the IE cellReservedForOperatorUse for that PLMN set to
“reserved”.
- UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 and UEs with AC 11 or 15 not operating in
theirHLPMN/EHPLMN shall behave as if the cell status is “barred” in case the cell is “reserved for operator
use” for the PLMN the UE is currently registered with.
NOTE 1: ...
- ...
- else
- If the IE intraFrequencyReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to

"allowed", the UE may select another cell on the same frequency if selection/re-selection criteria are fulfilled.
- The UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.- If the IE
intraFreqReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to "not allowed" the
UE shall not re-select a cell on the same frequency as the barred cell.
System Simulator:
- Three inter-frequency cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting default NAS
- SIB 1 of Cell 3 and Cell 6 indicate cellBarred=barred
- The cell power levels are configured as shown in Table 6.1.2.9.3.1-1.
Table 6.1.2.9.3.1–1: Cell power configuration

RS EPRE dBm/15kHz -97 -82 -67 S>0 for all cells
UE:
6.1.2.9.3.1-2.
ETSI
Table 6.1.2.9.3.1–2: USIM Configuration
USIM field Value

EFACC Type “B” as defined in TS34.108 clause
8.3.2.15
Preamble:

U-S Message
cellBarred=notBarred
Cell 3?
NOTE: The UE performs a TAU procedure
with establishment cause ‘high priority access'
and the RRC connection is released.
are now both barred) .
4 Void - - - -
Cell 1?
cellReservedForOperatorUse = reserved
Cell 6?
with establishment cause ‘high priority access’

in Tables 6.1.2.9.3.3-1, 6.1.2.9.3.3-2 and 6.1.2.8.3.3-4
ETSI
Table 6.1.2.9.3.3-1: SystemInformationBlockType1 for Cell 3 and Cell 6 (pre-test conditions, Table
6.1.2.9.3.2-1)

SEQUENCE {
OF SEQUENCE {
Cell 6
}
Cell 6
}
}

SEQUENCE {
Cell 6
}
barred Cell 6
}
0 Cell 6
}
Table 6.1.2.9.3.3-2A: SystemInformationBlockType1 for Cell 3 and Cell 6 (step 3, Table 6.1.2.8.3.2-1)

SEQUENCE {
Cell 6
}
Cell 6
}
Cell 6
0
}
ETSI

}

SEQUENCE {
reserved Cell 6
}
Cell 6
}
1 Cell 6
}
Table 6.1.2.9.3.3-5: RRCConnectionRequest (step2, step5 and step7, Table 6.1.2.9.3.2-1)

RRCConnectionRequest ::= SEQUENCE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause highPriorityAccess
}
}
}
6.1.2.9a Cell reselection using cell status and cell reservations / Access control class
11 to 15 / Single Frequency operation
Same Test Purpose as in clause 6.1.2.9.1.
Same Conformance requirement as in clause 6.1.2.9.2.
System Simulator:
- Three intra-frequency cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting default NAS
- SIB 1 of Cell 2 and Cell 4 indicate cellBarred=barred
ETSI
- The cell power levels are configured as shown in Table 6.1.2.9a.3.1-1.
Table 6.1.2.9a.3.1–1: Cell power configuration

z
z
UE:
6.1.2.9a.3.1-2.
Table 6.1.2.9a.3.1–2: USIM Configuration
USIM field Value

EFACC Type “B” as defined in TS34.108 clause
8.3.2.15
Preamble:
ETSI

U-S Message
cellBarred=notBarred and cell levels according
to row T1 of table 6.1.2.9a.3.1–1.
2 Check: Does the test result of generic test - - - -
Cell 2?
3A Wait for 2.1* modification period (Note 2) to - - - -
effect.
4 Void - - - -
paging in Cell 2 when paged with S-TMSI
to "PS"?
5A Check: Does the UE send an - - 1 F
RRCConnectionRequest on Cell 1, Cell 2 or
Cell 4 within 300 s of step 3?
SS adjusts cell levels according to row T2 of
table 6.1.2.9a.3.1–1.
Cell 4?
with establishment cause ‘high priority access’
Note 1: In steps 3-5A , UE will have barred all the cells for 300 seconds. The default value of intraFreqReselection is
'not allowed' in 36.508 table 4.4.3.2-3.
Note 2: The wait time of 2.1* modification period in step 3A is to allow for the network to paging the system
information change during the next modification period, and update the system information at the subsequent
modification period. UE should acquire the updated system information within 100ms of the start of modification
period.
Table 6.1.2.9a.3.3-0: Conditions for specific message contents

in Tables 6.1.2.9a.3.3-1, 6.1.2.9a.3.3-2, 6.1.2.9a.3.3-2A and 6.1.2. 9a.3.3-4
ETSI
Table 6.1.2.9a.3.3-1: SystemInformationBlockType1 for Cell 2 and Cell 4 (pre-test conditions, Table
6.1.2.9a.3.2-1)

SEQUENCE {
OF SEQUENCE {
Cell 4
}
Cell 4
}
}

SEQUENCE {
Cell 4
}
barred Cell 4
}
0 Cell 4
}
Table 6.1.2.9a.3.3-2A: SystemInformationBlockType1 for Cell 2 and Cell 4 (step 3, Table 6.1.2. 9a.3.2-
1)

SEQUENCE {
Cell 4
}
Cell 4
}
Cell 4
0
}
ETSI
Table 6.1.2.9a.3.3-3: Paging (step 3, Table 6.1.2.9a.3.2-1)

}

SEQUENCE {
reserved Cell 4
}
Cell 4
}
1 Cell 4
}
Table 6.1.2.9a.3.3-5: RRCConnectionRequest (step2, step5 and step7, Table 6.1.2.9a.3.2-1)

}
}
}
6.1.2.10 Cell reselection in shared network environment

with { the UE is in E-UTRA RRC_Idle and registered on the HPLMN }
ensure that {
when { a cell of a different PLMN but shared with the HPLMN becomes highest ranked cell }
then { the UE reselects the cell shared with the HPLMN }
References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 5.2.4.2 and TS
23.122 clause 4.4.3.
[TS 36.304, clause 5.2.4.6]
ETSI
where:

If a cell is ranked as the best cell the UE shall perform cell reselection to that cell. If this cell is found to be not-suitable,
the UE shall behave according to subclause 5.2.4.4.
[TS 23.122, clause 4.4.3]
...
...
System Simulator:
- Cell 1 (HPLMN)
- Cell 2 (primary PLMN: same MCC like HPLMN but different MNC, secondary PLMN: HPLMN)
UE:
None.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the conditions after the 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.
ETSI

T0 Cell- dBm/ -85 Off
specific RS 15kH
EPRE z
T1 Cell- dBm/ -85 -73 The power level values are assigned to satisfy SrxlevCell 2 >
specific RS 15kH SrxlevCell 1
EPRE z

U-S Message
1 The SS changes Cell 1 and Cell 2level - - - -
according to the row "T1" in table 6.1.2.10.3.2-
1.
4 Check; Does the UE transmit an --> RRCConnectionSetupComplete 1 P
indicating the HPLMN (second PLMN in the
list)?
Note: this message contains an TRACKING
AREA UPDATE REQUEST message
according to default message contents.
Table 6.1.2.10.3.3-1: SystemInformationBlockType1 (Cell 1, all steps, Table 6.1.2.10.3.2-2)

plmn-IdentityList SEQUENCE (SIZE (1..6)) OF
SEQUENCE {
plmn-Identity[1] Set to the same Mobile
Country Code and Mobile
Network Code stored in
EFIMSI on the test USIM
card
}
}
}
ETSI
Table 6.1.2.10.3.3-2: SystemInformationBlockType1 (Cell 2, all steps, Table 6.1.2.10.3.2-2)

SEQUENCE {
plmn-Identity[1] Set to the same Mobile
Country Code stored in
EFIMSI on the test USIM,
MNC=02
plmn-Identity[2] Set to the same Mobile This is the same
Country Code and Mobile PLMN as Cell 1
Network Code stored in
EFIMSI on the test USIM
card
}
}
}
Table 6.1.2.10.3.3-3: RRCConnectionSetupComplete (step 4, Table 6.1.2.10.3.2-2)

c1 CHOICE{
selectedPLMN-Identity 2 HPLMN
}
}
}
}
6.1.2.11 Inter-frequency cell reselection

(1)
ensure that {
when { UE detects both intra-frequency and equal priority inter-frequency neigbour cells and the
inter-frequency cell is the highest ranked cell }
then { UE reselects the inter-frequency cell }
}
5.2.4.6.
[TS 36.304, clause 5.2.4.5]
[TS 36.304, clause 5.2.4.6]
ETSI
where:

System Simulator:
- Cell 1,Cell 2 and Cell 3 have different tracking areas according to table 6.0.1-2.
UE:
None.
Preamble:

T1 Cell-specific dBm/15kHz -85 -91 -73 The power level values are set so that RCell 2
RS EPRE < RCell 1 < RCell 3.
ETSI

U-S Message
1 The SS changes the cells power level setting - - - -
1.
Cell 3?
Table 6.1.2.11.3.3-1: Void
Table 6.1.2.11.3.3-2: Void
Table 6.1.2.11.3.3-3: Void
6.1.2.12 Cell reselection / Cell-specific reselection parameters provided by the

network in a neighbouring cell list
6.1.2.12.1 Test Purpose
(1)
with { the UE is in RRC_IDLE and SystemInformationBlockType4 contain a cell-specific Qoffset for a
neighbour intra frequency cell }
ensure that {
when { the neighbour cell has lower power than the serving cell but it is higher ranked due to the
cell-specific Qoffset }
then { the UE reselects the neighbour cell with cell-specific Qoffset }
}
(2)
with { the UE is in RRC_IDLE and SystemInformationBlockType4 contain a black listed cell }
ensure that {
when { a black listed cell becomes higher ranked than the serving cell }
then { the UE remains camped on the serving cell }
}
6.1.2.12.2 Conformance Requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.304, clauses 5.2.4.1 and
5.2.4.6.
[TS 36.304 clause 5.2.4.1]
[TS 36.304 clause 5.2.4.6]
where:
ETSI

System Simulator:
- cells 1, 2, and 4 on the same E-UTRA frequency and in different tracking areas
- only 2 cells are simultaneously active, Cell 4 can be implemented as minimum uplink cell
- cell 1 is transmitting SystemInformationBlockType4 according to specific message contents (Qoffset1,2 is -24dB)
- cell 2 is transmitting SystemInformationBlockType4 according to specific message contents (Qoffset2,1 is 24dB,

cell 4 is on black list)
NOTE: Qoffset2,1 does not serve any test purpose, but symmetrical Qoffset values may be more realistic.
UE:
None.
Preamble:
- the UE is in state Registered, Idle mode (state 2) on Cell 1 according to [18].
various time instants of the test execution. Rows marked "T0" denote the conditions after the preamble, while rows
marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are
described in the texts in this clause.
ETSI
Ti Parameter Unit Cell 1 Cell 2 Cell 4 Remark

T0 Cell- dBm/ -85 Off Off Only Cell 1 is on
specific RS 15kH
EPRE z
T1 Cell- -85 -91 Off Cell 2 has lower power but is higher ranked
specific RS due to cell-specific Qoffset1,2
EPRE
(FDD)
Cell- -85 -89 Off
specific RS
EPRE
(TDD)
T2 Cell- Off -91 Off
specific RS
EPRE
(FDD)
Cell- Off -89 Off
specific RS
EPRE
(TDD)
T3 Cell- Off -91 -85 Cell 4 has higher power than Cell 2 but is
specific RS black listed
EPRE
(FDD)
Cell- Off -89 -85
specific RS
EPRE
(TDD)

U-S Message
1 The SS re-adjusts the cell-specific reference - - - -
signal levels according to row "T1" in table
6.1.2.12.3.2-1.
2 Void
2A- Check: Does the test result of test steps 1 to 5 - - 1 -
2E of generic procedure 6.4.2.7 indicate that the
UE is camped on Cell 2?
2F The SS re-adjusts the cell-specific reference - - - -
6.1.2.12.3.2-1
2G The SS waits for 1s. - - - -
Note: Delay is added to ensure cell power
levels set at T2 has settled on correct level
(36.523-3 cl. 7.4.2) before RRC connection is
released.
2H The SS transmits an RRCConnectionRelease <-- RRC: RRCConnectionRelease - -
message to release RRC connection and
move to RRC_IDLE.
6.1.2.12.3.2-1.
4 Check: Does the UE initiate a random access - - 2 F
procedure on Cell 4 within the next 120s?
ETSI
Table 6.1.2.12.3.3-1: SystemInformationBlockType4 for cell 1 (all steps, Table 6.1.2.12.3.2-2)

intraFreqNeighCellList SEQUENCE { 1 entry
physCellId[1] PhysicalCellID of Cell 2
q-OffsetCell[1] dB-24
}
}
Table 6.1.2.12.3.3-2: SystemInformationBlockType4 for cell 2 (all steps, Table 6.1.2.12.3.2-2)

intraFreqNeighCellList { 1 entry
physCellId[1] PhysicalCellID of Cell 1
q-OffsetCell[1] dB24
}
intraFreqBlackCellList SEQUENCE { 1 entry
start[1] PhysicalCellID of Cell 4
range[1] Not present
}
}
6.1.2.13 Cell reselection, Sintrasearch, Snonintrasearch

(1)
ensure that {
when { Sintrasearch is non-zero in system information }
then { UE perform measurement and reselects the highest ranked cell upon Srxlev < Sintrasearch }
}
(2)
ensure that {
when { Snonintrasearch is non-zero in system information }
then { UE perform measurement and reselects the cell which belong to the equal priority
frequency cell upon Srxlev < Snonintrasearch }
}
(3)
ensure that {
then { UE perform measurement and reselects the cell which belong to the high priority
frequency cell upon Srxlev > Snonintrasearch }
}
References: The conformance requirements covered in the current TC are specified in: TS36.304, clauses 5.2.4.2,
5.2.4.5 and 5.2.4.6; TS36.331, clause 6.3.1; TS36.133, clause 4.2.2.4.
[TS 36.304, clause 5.2.4.2]
ETSI
measurements.
measurements.
according to [10].
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
.....
.....
[TS 36.304, clause 5.2.4.6]
where:

ETSI
...
[TS 36.331, clause 6.3.1]
The IE SystemInformationBlockType3 contains cell re-selection information common for intra-frequency, inter-
frequency and/ or inter-RAT cell re-selection (i.e. applicable for more than one type of cell re-selection but not
necessarily all) as well as intra-frequency cell re-selection information other than neighbouring cell related.
[TS 36.133, clause 4.2.2.4]
The UE shall be able to evaluate whether a newly detectable inter-frequency cell meets the reselection criteria defined
in TS36.304 within Kcarrier * Tdetect,EUTRAN_Inter if at least carrier frequency information is provided for inter-frequency
neighbour cells by the serving cells when Treselection = 0 provided that the reselection criteria is met by a margin of at
least 5dB for reselections based on ranking or 6dB for RSRP reselections based on absolute priorities or 4dB for RSRQ
reselections based on absolute priorities.
System Simulator:
- Cell 1, Cell 2 and Cell 3 have different tracking areas according to table 6.0.1-2.
UE:
None.
Preamble:
texts in this clause. Configurations marked "T1", "T2" and "T3" are applied at the points indicated in the Main
ETSI

Cell-specific RS Srxlev of Cell 1 is less than Sintrasearch.
dBm/15kHz -91 -79 "Off"
EPRE
T1
Qrxlevmin dBm -106 -106 -106
Sintrasearch dB 22 22 22
Cell-specific RS Srxlev of Cell 2 is less than Snonintrasearch.
dBm/15kHz "Off" -97 -79
T2 EPRE
Snonintrasearch dB 16 16 16
Cell-specific RS
T3 dBm/15kHz "Off" "Off" -79
EPRE
Cell-specific RS Srxlev of Cell 3 is greater than
dBm/15kHz -85 "Off" -79
T4 EPRE Snonintrasearch but Cell 1 is high priority cell.
Note: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.
ETSI

U-S Message
6.1.2.13.3.2-1.
2 Check: Does UE transmit an --> RRCConnectionRequest 1 P

RRCConnectionRequest message on Cell 2?
TS 36.508 subclause 6.4.2.7 are performed
on Cell 2.
6.1.2.13.3.2-1.
9 Check: Does UE transmit an --> RRCConnectionRequest 2 P
14 TS 36.508 subclause 6.4.2.7 are performed
on Cell 3.
14A The SS re-adjusts the cell-specific reference
6.1.2.13.3.2-1.
Information and changes the system
information for Cell 3. The
16 Wait for 15 s for the UE to receive system - - - -
information.
16A SS modifies SIB3 in Cell 1 and the - - - -
signal levels according to row " T4" in table
6.1.2.13.3.2-1.
18 Check: Does the test result of steps 1 to 5 of - - 3 -
the generic test procedure in TS 36.508
subclause 6.4.2.7 indicate that the UE is
camped on E-UTRAN Cell 1? (Note1)
Note: UE uses the new SIB3 modified in step

16A.
Note1: UE shall search higher priority layer (i.e. E-UTRA carrier frequency of Cell 1) at least every (60 * Nlayers)
seconds, where Nlayers = 1 as specified in [4.2.2, 34].
ETSI
Table 6.1.2.13.3.3-1: Void
Table 6.1.2.13.3.3-2: SystemInformationBlockType3 for Cells 1, 2 and 3 (preamble and all steps, table
6.1.2.13.3.2-2)

s-NonIntraSearch 8 (16 dB)
}
s-IntraSearch 11 (22 dB)
}
}
Table 6.1.2.13.3.3-3: SystemInformationBlockType1 for Cell 3 (step 15, Table 6.1.2.13.3.2-2)

systemInfoValueTag 1 Previous value is 0
}

interFreqCarrierFreqList SEQUENCE (SIZE 1 entry
dl-CarrierFreq[1] EARFCN of Cell 1
threshX-High[1] 5 10 dB
}
}

}
ETSI
Table 6.1.2.13.3.3-6: SystemInformationBlockType3 for Cell 1 (step 16A, table 6.1.2.13.3.2-2)

cellReselectionPriority 5
}
}
}
Table 6.1.2.13.3.3-7: SystemInformationBlockType1 for Cell 1 (step 16A, Table 6.1.2.13.3.2-2)

}
6.1.2.14 Speed-dependent cell reselection

(1)
with { UE in E-UTRA RRC_IDLE state and in high mobility state }
ensure that {
when { UE detects the cell ranked as the best cell taking into account scaling factor }
}
5.2.4.3.1. TS 36.133, clause 4.2.2.3.
[TS 36.304, clause 5.2.4.3]
Besides Normal-mobility state a High-mobility and a Medium-mobility state are applicable if the parameters (TCRmax,
NCR_H, NCR_M and TCRmaxHyst) are sent in the system information broadcast of the serving cell.
State detection criteria:
...
High-mobility state criteria:
- If number of cell reselections during time period TCRmax exceeds NCR_H
The UE shall not count consecutive reselections between same two cells into mobility state detection criteria if same
cell is reselected just after one other reselection.
State transitions:
The UE shall:
- if the criteria for High-mobility state is detected:
- enter High-mobility state.
...
ETSI
If the UE is in High- or Medium-mobility state, the UE shall apply the speed dependent scaling rules as defined in
subclause 5.2.4.3.1.
[TS 36.304, clause 5.2.4.3.1]
UE shall apply the following scaling rules:
- If neither Medium- nor Highmobility state is detected:
- no scaling is applied.
- If High-mobility state is detected:
- Add the sf-High of "Speed dependent ScalingFactor for Qhyst” to Qhyst if sent on system information
- For E-UTRAN cells multiply TreselectionEUTRA by the sf-High of "Speed dependent ScalingFactor for
TreselectionEUTRA” if sent on system information
- For UTRAN cells multiply TreselectionUTRA by the sf-High of "Speed dependent ScalingFactor for
TreselectionUTRA” if sent on system information
- For GERAN cells multiply TreselectionGERA by the sf-High of "Speed dependent ScalingFactor for
TreselectionGERA state” if sent on system information
- For CDMA2000 HRPD cells Multiply TreselectionCDMA_HRPD by the sf-High of "Speed dependent
ScalingFactor for TreselectionCDMA_HRPD” if sent on system information
- For CDMA2000 1xRTT cells Multiply TreselectionCDMA_1xRTT by the sf-High of "Speed dependent
ScalingFactor for TreselectionCDMA_1xRTT” if sent on system information
...
In case scaling is applied to any TreselectionRAT parameter the UE shall round up the result after all scalings to the
nearest second.
[TS 36.133, clause 4.2.2.3]
The UE shall be able to identify new intra-frequency cells and perform RSRP and RSRQ measurements of identified
intra-frequency cells without an explicit intra-frequency neighbour list containing physical layer cell identities.
The UE shall be able to evaluate whether a newly detectable intra-frequency cell meets the reselection criteria defined
in TS36.304 within Tdetect,EUTRAN_Intra when that Treselection= 0 . An intra frequency cell is considered to be detectable
according to RSRP, RSRP Ês/Iot, SCH_RP and SCH Ês/Iot defined in Annex B.1.1 for a corresponding Band.
The UE shall measure RSRP and RSRQ at least every Tmeasure,EUTRAN_Intra (see table 4.2.2.3-1) for intra-frequency cells
that are identified and measured according to the measurement rules.
The UE shall filter RSRP and RSRQ measurements of each measured intra-frequency cell using at least 2
measurements. Within the set of measurements used for the filtering, at least two measurements shall be spaced by at
least Tmeasure,EUTRAN_Intra/2
The UE shall not consider a E-UTRA neighbour cell in cell reselection, if it is indicated as not allowed in the
measurement control system information of the serving cell.
For an intra-frequency cell that has been already detected, but that has not been reselected to, the filtering shall be such
that the UE shall be capable of evaluating that the intra-frequency cell has met reselection criterion defined [1] within
Tevaluate,E-UTRAN_intra when Treselection = 0 as specified in table 4.2.2.3-1 provided that the cell is at least 3dB better ranked.
When evaluating cells for reselection, the side conditions for RSRP and SCH apply to both serving and non-serving
intra-frequency cells.
If Treselection timer has a non zero value and the intra-frequency cell is better ranked than the serving cell, the UE shall
evaluate this intra-frequency cell for the Treselection time. If this cell remains better ranked within this duration, then the
UE shall reselect that cell.
ETSI
Table 4.2.2.3-1: Tdetect,EUTRAN_Intra, Tmeasure,EUTRAN_Intra and Tevaluate, E-UTRAN_intra
DRX Tdetect,EUTRAN_Intra Tmeasure,EUTRAN_Intra Tevaluate,E-UTRAN_intra

cycle [s] (number of [s] (number of [s] (number of DRX
length DRX cycles) DRX cycles) cycles)
[s]
0.32 11.52 (36) 1.28 (4) 5.12 (16)
0.64 17.92 (28) 1.28 (2) 5.12 (8)
1.28 32(25) 1.28 (1) 6.4 (5)
2.56 58.88 (23) 2.56 (1) 7.68 (3)
System Simulator:
- Cell 1, Cell 2, and Cell 4.
UE:
None.
Preamble:

T1 Cell-specific dBm/ -91 -85 -91 Cell 2 becomes the highest ranked cell.
RS EPRE 15kH
z
RS EPRE 15kH
z
RS EPRE 15kH
z
ETSI

U-S Message
1.
2 Wait for 40s for the UE to perform cell - - - -
reselection procedure.(Note 1, Note 5)
according to the row “T2” in table 6.1.2.14.3.2-
1.
reselection procedure.(Note 2, Note 6)
1.
reselection procedure. (Note 3, Note 6)
1.
reselection procedure. (Note 4, Note 6)
9 The SS changes the TAC for Cell 4 to 2. - - - -
1.
(Note 7)
(Note 8)
13- Steps 2 to 6 of the generic test procedure in - - 1 -
Cell 4.
Note 1: NCR (number of cell reselection) is 1.
Note 2: NCR is 2.
Note 3: NCR is 3.
Note 4: NCR is 4 and the UE enters high mobility state because number of cell reselections during time period TCRmax
exceeds NCR_H.
Note 5: The wait time for reselection to a newly detected intra frequency cell is selected to cover
Tdetect,EUTRAN_Intra(25*1280ms=32s) + Treselection (7s) + 320 ms system information block type scheduling =
39.32s rounded up to 40s.
Note 6: The wait time for reselection to an already detected intra frequency cell is selected to cover Tevaluate,E-
UTRAN_intra(6.4s) + Treselection (7s) + 320 ms system information block type scheduling = 13.72s rounded up
to 14s.
Note 7: The wait time for evaluating an intra-frequency cell is Treselection after scaling (2s) + 320 ms system
information block type scheduling. This wait time is rounded down to nearest second (i.e. 2s in this case).
Note 8: The wait time for cell reselection procedure is selected to cover Tevaluate,E-UTRAN_intra (6.4s) + Treselection after
scaling (7*0.25) + 320 ms system information block type scheduling = 8.47s rounded up to 9s. The actual
wait time is 7s which covers 9s - 2s (wait time in step 11).
ETSI
Table 6.1.2.14.3.3-1: SystemInformationBlockType1 for Cell 2, and Cell 4 (preamble, Table

6.1.2.14.3.2-2)
Derivation Path: 36.508 Table 4.4.3.2-3

cellAccessRelatedInformation SEQUENCE {
trackingAreaCode 1
}
}
Table 6.1.2.14.3.3-2: SystemInformationBlockType3 for Cell 1, Cell 2, and Cell 4 (preamble and all
steps, Table 6.1.2.14.3.2-2)
Derivation Path: 36.508, Table 4.4.3.3-2

speedStateReselectionPars SEQUENCE {
mobilityStateParameters SEQUENCE {
t-Evalulation s240
t-HystNormal s240
n-CellChangeMedium 3
n-CellChangeHigh 3
}
q-HystSF SEQUENCE {
sf-Medium dB0
sf-High dB0
}
}
}
t-ReselectionEUTRAN 7
t-ReselectionEUTRA-SF SEQUENCE {
sf-Medium oDot25
sf-High oDot25
}
}
}

trackingAreaCode 2
}
}
6.1.2.15 Inter-frequency cell reselection according to cell reselection priority provided

by SIBs
(1)
ensure that {
ETSI
when { UE detects the cell re-selection criteria are met for the cell which belongs to the equal
priority frequency }
then { UE reselects the cell which belongs to the equal priority frequency }
}
(2)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher
then { UE reselects the cell which belongs to the higher priority frequency }
}
(3)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the lower
then { UE reselects the cell which belongs to the lower priority frequency }
}
5.2.4.2, 5.2.4.5 and 5.2.4.6.
[TS 36.304, clause 5.2.4.1]
priority frequency (i.e. lower than the eight network configured values). The UE shall delete priorities provided by
dedicated signalling when:
UTRA, T322 in UTRA and [T3230, FFS] in GERAN), if configured, at inter-RAT cell (re)selection.
information.
[TS 36.304, clause 5.2.4.2]
ETSI
measurements.
measurements.
according to [10].
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
be performed if:
be performed if:
criteria 1; and
or if:
- there are no candidate cells for reselection on serving frequency according to 5.2.4.4 or 5.3.1.
is higher than 0, as defined in [8].For cdma2000 RATs, SnonServingCell,x is equal to FLOOR(-2 x 10 x log10 Ec/Io) in units
ETSI
[TS 36.304, clause 5.2.4.6]
where:

System Simulator:
- Cell 1, Cell 3 and Cell 6.
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configurations marked "T1", "T2" and "T3" are applied at the
points indicated in the Main behaviour description in Table 6.1.2.15.3.2-2.
ETSI

T1 Cell- dBm/ -85 -73 ”Off” The power level values are assigned to
EPRE z (NOTE 1).
T2 Cell- dBm/ ”Off” -73 -73 The power level values are assigned to
specific RS 15kH satisfy SrxlevCell 1 < 0 and SrxlevCell 6 >
EPRE z ThreshCell 6, high.
(NOTE 1).
specific RS 15kH satisfy SrxlevCell 6 < Threshserving, low and
EPRE z SrxlevCell 3 > ThreshCell 3, low, SrxlevCell 1< 0.
(NOTE 1).

U-S Message
Cell 3?
3 The SS changes Cell 1 and Cell 6 power level - - - -
1.
Cell 6?
Cell 3?
Table 6.1.2.15.3.3-1: Void
Table 6.1.2.15.3.3-2: Void
6.1.2.15.3.2-2)

threshServingLow 10 20 dB
}
}
ETSI
6.1.2.15.3.2-2)

}
}
6.1.2.15.3.2-2)

dl-CarrierFreq[n] EARFCN of Cell 6
threshX-High[n] 10 20 dB
cellReselectionPriority[n] 5
}
}
6.1.2.15a Inter-frequency cell reselection according to cell reselection priority provided

by SIBs / Between FDD and TDD
(1)
with { UE in E-UTRA RRC_IDLE state in FDD mode}
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the equal
priority TDD frequency }
then { UE reselects the cell which belongs to the equal priority TDD frequency }
}
(2)
with { UE in E-UTRA RRC_IDLE state in TDD mode}
ensure that {
priority FDD frequency }
then { UE reselects the cell which belongs to the higher priority FDD frequency }
}
(3)
with { UE in E-UTRA RRC_IDLE state in FDD mode}
ensure that {
priority TDD frequency }
then { UE reselects the cell which belongs to the lower priority TDD frequency }
}
ETSI
5.2.4.2, 5.2.4.5 and 5.2.4.6.
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.2]
measurements.
measurements.
ETSI
according to [10].
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
be performed if:
be performed if:
criteria 1; and
or if:
is higher than 0, as defined in [8].For cdma2000 RATs, SnonServingCell,x is equal to FLOOR(-2 x 10 x log10 Ec/Io) in units
[TS 36.304, clause 5.2.4.6]
where:

ETSI
System Simulator:
- Cell 1 and Cell 3 are set to LTE-FDD mode and Cell 10 is set to LTE-TDD mode.
UTRA cells.
UE:
None.
Preamble:
points indicated in the Main behaviour description in Table 6.1.2.15a.3.2-2.

EPRE z (NOTE 1).
(NOTE 1).
EPRE z SrxlevCell 10 > ThreshCell 3, low, SrxlevCell 1< 0.
(NOTE 1).
Note 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.
ETSI

U-S Message
to the row "T1" in table 6.1.2.15a.3.2-1.
Cell 10?
3 The SS changes Cell 1 and Cell 3 power level - - - -
according to the row "T2" in table
6.1.2.15a.3.2-1.
Cell 3?
Cell 10?
6.1.2.15a.3.2-2)

}
}
6.1.2.15a.3.2-2)

}
}
ETSI
6.1.2.15a.3.2-2)

}
}
6.1.2.15b Inter-band cell reselection according to cell reselection priority provided by

SIBs
Same Test Purposes as in clause 6.1.2.15.1
System Simulator:
- Cell 1, cell 10 and ‘If (px_SinglePLMN_Tested = Multi PLMN in primary band)’ Cell 3 ‘ELSE If
(px_SinglePLMN_Tested = Multi PLMN in Secondary band)’ Cell 28.
UE:
None.
Preamble:
Table 6.1.2.15b.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
points indicated in the Main behaviour description in Table 6.1.2.15b.3.2-2.
ETSI
Table 6.1.2.15b.3.2-1: Time instances of cell power level and parameter changes
Parameter Unit Cell 1 Cell 3 or Cell 10 Remark

Cell 28 (If
Present)
specific RS 15kH satisfy RCell 1 < RCell 3 or 28
EPRE z (NOTE 1).
(NOTE 1).
T3 Cell- dBm/ -73 ”Off” -95 The power level values are assigned to
EPRE z SrxlevCell 1 > ThreshCell 1, low, SrxlevCell 3 or 28<
0.
(NOTE 1).

U-S Message
- Exception: Steps 1a1 and 1a2 are executed if - - - -
cell 3 or cell 28 are configured
1a1 The SS changes Cell 3/ Cell 28 power level - - - -
6.1.2.15b.3.2-1.
1a2 Check: Does the test result of generic test - - 1 -
Cell 3/ Cell 28 (if present)?
2 The SS changes Cell 1 and Cell10 power level - - - -
6.1.2.15b.3.2-1.
Cell 10?
4 The SS changes Cell 10 and cell 1 power level - - - -
6.1.2.15b.3.2-1.
Cell 1?
Table 6.1.2.15b.3.3-1: SystemInformationBlockType3 for Cell 10 (preamble and all steps, Table
6.1.2.15b.3.2-2)

}
}
ETSI
Table 6.1.2.15b.3.3-2: SystemInformationBlockType5 for Cell 1 (preamble and all steps, Table
6.1.2.15b.3.2-2)

dl-CarrierFreq[1] EARFCN of Cell 3/Cell
28
}
}
Table 6.1.2.15b.3.3-3: SystemInformationBlockType5 for Cell 3/Cell 28 (preamble and all steps, Table
6.1.2.15b.3.2-2)

}
}
6.1.2.16 Cell reselection / interband operation / Between FDD and TDD

(1)
with { UE in E-UTRA RRC_IDLE state in FDD mode }
ensure that {
when { UE detects the cell re-selection criteria are met for the cell on the different TDD
frequency band }
}
(2)
with { UE in E-UTRA RRC_IDLE state in TDD mode }
ensure that {
when { UE detects the cell re-selection criteria are met for the cell on the different FDD
frequency band }
}
5.2.4.2 and 5.2.4.5.
[TS 36.304, clause 5.2.4.1]
ETSI
information.
[TS 36.304, clause 5.2.4.2]
measurements.
measurements.
- If SServingCell <= Snonintrasearchor Snonintrasearch is not sent in the serving cell the UE shall perform
according to [10].
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
ETSI
be performed if:
be performed if:
criteria 1; and
System Simulator:
- Cell 1 is FDD mode, Cell 28,Cell30 are TDD mode in the same TDD band.
Cell PLMN name

1 PLMN1
28 PLMN2
30 PLMN3
UTRA cells.
UE:
6.1.2.16.3.1-2.
ETSI

Preamble:
that the ATTACH ACCEPT message indicates PLMN2/PLMN3 in the Equivalent PLMN list as described in
Table 6.1.2.16.3.3-5.

T1 Cell- dBm/15kHz -73 Off -73 Cell 1 and Cell 30 becomes stronger
specific RS than Threshx, high., but Cell 30 has the
EPRE higher priority (NOTE 1).
T2 Cell- dBm/15kHz -73 -73 -85 Cell 1 and Cell 28 become stronger
specific RS than Threshx, high., but Cell 1 has the
EPRE higher priority(NOTE 1).
Note 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

U-S Message
2 Check: Does the test result of generic test - - 1,
Cell 30?
with PLMN1 and PLMN2 listed as Equivalent
PLMN list in the TRACKING AREA UPDATE
ACCEPT message, and the RRC connection is
released.
- The SS changes the - - - -
SystemInformationBlockType3 and
SystemInformationBlockType5 in the system
information and transmits a Paging message
including a systemInfoModification.
3 The SS changes Cell 1, Cell 28 and Cell 30 - - - -
power level according to the row "T2" in table
6.1.2.16.3.2-1.
4 Check: Does the test result of generic test - - 2
Cell 1?
with PLMN2 and PLMN3 listed as Equivalent
PLMN list in the TRACKING AREA UPDATE
ACCEPT message, and the RRC connection is
released.
ETSI

in Tables 6.1.2.16.3.3-1 and 6.1.2.16.3.3-2
Table 6.1.2.16.3.3-1: SystemInformationBlockType3 for Cell 1 and Cell 30 (preamble and step 1 and 2,
Table 6.1.2.16.3.2-2)

5 Cell 30
}
}
Table 6.1.2.16.3.3-2: SystemInformationBlockType3 for Cell 1, Cell 28 and Cell 30 (step 3 and step 4,
Table 6.1.2.16.3.2-2)

4 Cell 28
3 Cell 30
}
}
Table 6.1.2.16.3.3-3: SystemInformationBlockType5 for Cell 1 and Cell 30 (preamble and step 1 and 2,
Table 6.1.2.16.3.2-2)

as used for Cell 30
as used for Cell 1
t-ReselectionEUTRA 5 Cell 1
5 Cell 30
3 Cell 30
}
}
ETSI
Table 6.1.2.16.3.3-4: SystemInformationBlockType5 for Cell 1, Cell 28, and Cell 30 (step 3 and 4, Table
6.1.2.16.3.2-2)

dl-CarrierFreq[n] Same downlink EARFCN Cell 1
as used for Cell 28
Same downlink EARFCN Cell 28,
as used for Cell 1 Cell 30
t-ReselectionEUTRA[n] 7 Cell 1
5 Cell 30
threshX-High[n] 10 20dB
cellReselectionPriority[n] 4 Cell 1
5 Cell 28,
Cell 30
dl-CarrierFreq[m] Same downlink EARFCN Cell 1,
as used for Cell 30 Cell 28
as used for Cell 28
t-ReselectionEUTRA[m] 5 Cell 1
7 Cell 30
threshX-High[m] 10 20dB
cellReselectionPriority[m] 3 Cell 1,
Cell 28
4 Cell 30
}
}

Equivalent PLMNs PLMN2,3


6.1.2.17 Cell reselection for Squal to check against SIntraSearchQ and SnonIntraSearchQ
(1)
ensure that {
when { SIntraSearchQ is non-zero in system information }
then { UE perform measurement and reselects the highest ranked cell upon Squal < SIntraSearchQ }
}
ETSI
(2)
ensure that {
when { SnonIntraSearchQ is non-zero in system information }
then { UE perform measurement and reselects the cell which belong to the equal priority
frequency cell upon Squal < SnonIntraSearchQ }
}
(3)
ensure that {
when { SnonIntraSearchQ is non-zero in system information }
then { UE perform measurement and reselects the cell which belong to the high priority
frequency cell upon Squal > SnonIntraSearchQ }
}
5.2.4.5 and 5.2.4.6; TS36.331, clause 6.3.1.
[TS 36.304, clause 5.2.4.2]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided
by the serving cell.
- If the serving cell fulfils Srxlev > SIntraSearchP and Squal > SIntraSearchQ, the UE may choose not to perform intra-
frequency measurements.
- Otherwise, the UE shall perform intra-frequency measurements.
- If the serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE may choose not to
perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower
priority.
- Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells
of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a higher priority E-

UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
- A cell of a higher priority EUTRAN or UTRAN FDD RAT/ frequency fulfils Squal > ThreshX, HighQ during a
time interval TreselectionRAT; or
- A cell of a higher priority UTRAN TDD, GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, HighP
during a time interval TreselectionRAT; and
- More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving
frequency shall be performed if:
ETSI
- A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval
TreselectionRAT; and
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a lower priority E-

- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority EUTRAN or UTRAN FDD RAT/
frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT; or
- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority UTRAN TDD, GERAN or
CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
Otherwise, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving
- The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils Srxlev >
ThreshX, LowP during a time interval TreselectionRAT; and
Cell reselection to a higher priority RAT/ frequency shall take precedence over a lower priority RAT/ frequency, if
multiple cells of different priorities fulfil the cell reselection criteria.
…..
defined in subclause 5.2.4.3.1. If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
- If the highest-priority frequency is an E-UTRAN frequency, a cell ranked as the best cell among the cells on the
highest priority frequency(ies) meeting the criteria according to section 5.2.4.6;
- If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the
highest priority frequency(ies) meeting the criteria of that RAT.
[TS 36.304, clause 5.2.4.6]
where:

ETSI
[TS 36.331, clause 6.3.1]
System Simulator:
UE:
None.
Preamble:
texts in this clause. Configurations marked "T1", "T2" and "T3" are applied at the points indicated in the Main

Cell-specific RS Squal of Cell 1 is less than SIntraSearchQ.
dBm/15kHz -91 -85 -115
EPRE
RSRQ dB -11.68 -5.68 -30.8
Qrxlevmin dBm -106 -106 -106
T1 Qqualmin dB -20 -20 -20
SIntraSearchQ dB 20 20 20
Noc dBm/15kHz -95 -95 -95
Srxlev dB 15 21 -9
Squal dB 8.32 14.32 -10.8
Cell-specific RS Squal of Cell 2 is less than SnonIntraSearchQ.
dBm/15kHz -115 -91 -85
EPRE
RSRQ dB -32.32 -8.32 -5.05
T2
SnonIntraSearchQ dB 20 20 20
Srxlev dB -9 15 21
Squal dB -12.32 11.68 14.95
Cell-specific RS Squal of Cell 3 is greater than
dBm/15kHz -85 -115 -85
EPRE SnonIntraSearchQ but Cell 1 is high priority
RSRQ dB [-6] [-25] [-6] cell.
T3
SnonIntraSearchQ dB 20 20 2
Srxlev dB 21 -9 21
Squal dB 14.95 -15.05 14.95
Note: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.
ETSI

U-S Message
6.1.2.17.3.2-1.
2 Check: Does UE transmits an --> RRCConnectionRequest 1 P
RRCConnectionRequest message on Cell 2
within [6 minutes]?
3 - 7 Steps 2 to 6 of the generic test procedure in - - - -
TS 36.508 subclause 6.4.2.7 are performed
on Cell 2.
6.1.2.17.3.2-1.
9 Check: Does UE transmits an --> RRCConnectionRequest 2 P
within [6 minutes]?
14 TS 36.508 subclause 6.4.2.7 are performed
on Cell 3.
15 The SS waits 1 second. - - - -
information for Cell 1, 2 & 3. The
17 Void - - - -
6.1.2.13.3.2-1.
19 Check: Does the test result of the generic test - - 3 -
Cell 1? (Note1)
Note1: UE shall search higher priority layer (i.e. E-UTRA carrier frequency of Cell 1) at least every (60 * Nlayers)
ETSI
Table 6.1.2.17.3.3-1: SystemInformationBlockType1 for Cells 1, 2 and 3 (preamble, Table 6.1.2.17.3.2-

2)

}
q-QualMin-r9 -20 dB
}
}
}
}
Table 6.1.2.17.3.3-2: SystemInformationBlockType3 for Cells 1, 2 and 3 (preamble, Table 6.1.2.17.3.2-

2)

s-IntraSearch-v920 SEQUENCE {
s-IntraSearchP-r9 0 (0 dB)
s-IntraSearchQ-r9 20 dB
}
s-NonIntraSearch-v920 SEQUENCE {
s-NonIntraSearchP-r9 0 (0 dB)
s-NonIntraSearchQ-r9 20 dB
}
q-QualMin-r9 -20 dB
}
}

q-QualMin-r9 -20 dB
}
}
}
}
ETSI
Table 6.1.2.17.3.3a: SystemInformationBlockType3 for Cell 3 (step 16, Table 6.1.2.17.3.2-2)

s-NonIntraSearch-v920 SEQUENCE {
s-NonIntraSearchP-r9 0 (0 dB)
s-NonIntraSearchQ-r9 2 dB
}
}
}

interFreqCarrierFreqList SEQUENCE (SIZE 1 entry
}
}
Table 6.1.2.17.3.3-4a: SystemInformationBlockType3 for Cell 1 and 2 (step 16, Table 6.1.2.17.3.2-2)

s-NonIntraSearch Not present
threshServingLow 0 (0 dB)
}
}

}
Table 6.1.2.17.3.3-6: SystemInformationBlockType1 for Cell 1, Cell 2 and Cell 3 (step 16, Table
6.1.2.17.3.2-2)

ETSI
6.1.2.18 Inter-frequency cell reselection based on common priority information with

parameters ThreshX, HighQ, ThreshX, LowQ and ThreshServing, LowQ
(1)
ensure that {
}
(2)
ensure that {
then { UE reselects the cell which belongs to the lower priority frequency }
}
5.2.4.2 and 5.2.4.5.
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.2]
ETSI
priority.
- Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT

frequency cells of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]

- A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT;
and

ETSI
…..
System Simulator:
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configurations marked "T1" and "T2" are applied at the points

specific RS 15kHz satisfy SrxlevCell 1 > 0, SrxlevCell 3 < ThreshCell
EPRE 3, highP, SqualCell 1 > 0 and SqualCell 3 >
RSRQ dB -3 -3 ThreshCell 3, highQ.
Qqualmin dB -20 -20
Noc dBm/1 off off
5kHz
specific RS 15kHz satisfy SrxlevCell 3 > Threshserving, lowP,
EPRE SqualCell 3 < Threshserving, lowQ and SqualCell 1 >
RSRQ dB -3 -3 ThreshCell 1, lowQ.
ETSI

U-S Message
Cell 3?
2A The SS notifies the UE of change of System <-- Paging - -
information 3. The systemInfoValueTag in the
Cell 1?

in Tables 6.1.2.18.3.3-2 and 6.1.2.18.3.3-3
Table 6.1.2.18.3.3-2: SystemInformationBlockType3 for Cell 1 and Cell 3 (preamble, Table 6.1.2.18.3.2-
2)

threshServingLow 1 2 dB Cell 3
}
}
q-QualMin-r9 -20 dB
threshServingLowQ-r9 0 dB Cell 1
4 dB Cell 3
}
}
ETSI
Table 6.1.2.18.3.2-2)

dl-CarrierFreq[n] EARFCN of Cell 1 Cell 3
EARFCN of Cell 3 Cell 1
q-RxLevMin[n] -50 (-100 dBm)
t-ReselectionEUTRA[n] 7
threshX-High[n] 10 (20 dB) Cell 1
5 Cell 1
q-QualMin-r9[n] -20 dB
threshX-Q-r9[n] SEQUENCE {
threshX-HighQ-r9[n] 4 4 dB
threshX-LowQ-r9[n] 2 2 dB
}
}
}
Table 6.1.2.18.3.3-2: SystemInformationBlockType3 for Cell 3 (Step 2A, Table 6.1.2.18.3.2-2)

q-QualMin-r9 -20 dB
threshServingLowQ-r9 26 dB
}
}
Table 6.1.2.18.3.3-3: SystemInformationBlockType1 for Cell 3 (Step 2A, Table 6.1.2.18.3.2-2)

6.1.2.19 Intra-frequency cell reselection / MFBI

(1)
ensure that {
when { an equal priority E-UTRAN Intra-frequency neighbouring cell which has been included in the
multiBandInfoList provided by the serving
cell becomes available, and, is better ranked than the serving cell during a time interval
TreselectionRAT, and, more than 1 second has elapsed since the UE camped on the current serving cell
}
then { the UE reselects the new cell }
}
5.2.4.6, TS 36.331, clause 5.2.2.7 and 6.3.1. Unless otherwise stated these are Rel-8 requirements.
ETSI
[TS 36.304, clause 5.2.4.2]
When evaluating for reselection purposes cell selection criterion or SnonServingCell, x, the UE shall use parameters
measurements.
measurements.
E-UTRAN inter-frequency inter-RAT frequencies according to [10].
according to [10].
[TS 36.304, clause 5.2.4.6]
where:

- the new cell is better ranked than the serving cell during a time interval TreselectionRAT
ETSI
[TS 36.331, clause 5.2.2.7]
Upon receiving the SystemInformationBlockType1 either via broadcast or via dedicated signalling, the UE shall:
1> if in RRC_CONNECTED while T311 is not running, and the UE supports multi-band cells as defined by bit 31
in featureGroupIndicators:
2> disregard the freqBandIndicator and multiBandInfoList, if received, while in RRC_CONNECTED;
2> forward the cellIdentity to upper layers;
2> forward the trackingAreaCode to upper layers;
1> else:
2> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE;
or
2> if the UE supports multiBandInfoList, and if one or more of the frequency bands indicated in the
multiBandInfoList are part of the frequency bands supported by the UE:
2> else:
3> consider the cell as barred in accordance with TS 36.304 [4]; and
3> perform barring as if intraFreqReselection is set to notAllowed, and as if the csg-Indication is set to
FALSE;
[TS 36.331, clause 6.3.1]
- SystemInformationBlockType2
The IE SystemInformationBlockType2 contains radio resource configuration information that is common for all UEs.
NOTE: UE timers and constants related to functionality for which parameters are provided in another SIB are
included in the corresponding SIB.
SystemInformationBlockType2 field descriptions

multiBandInfoList
A list of additionalSpectrumEmission i.e. one for each additional frequency band included in multiBandInfoList in
SystemInformationBlockType1, listed in the same order.
System Simulator:
- Cell 1 and Cell 2 have different tracking areas according to table 6.0.1-2 and are MFBI capable cells.
- Cell 1 belongs to the absolute centre frequency which overlaps between bands controlled by IXITs
px_MFBI_FrequencyBand and px_OverlappingNotSupportedFrequencyBandMFBI.
- Cell 2 belongs to another absolute centre frequency which again overlaps between bands controlled by IXITs
UE:
None.
ETSI
Preamble:

T1 Cell-specific dBm/15kHz -85 -79 The power level values are set so that RCell 1
RS EPRE < RCell 2.

U-S Message
0 Wait 1 second. (to ensure than 1 second has - - - -
elapsed since the UE camped on the current
serving cell)
1.
Cell 2?
Table 6.1.2.19.3.2-2)

freqBandIndicator An overlapping not Cell 1
supported frequency Cell 2
band MFBI under test
(px_OverlappingNotSupp
ortedFrequencyBandMF
BI).
lateNonCriticalExtension
SystemInformationBlockType1-v8h0-IEs ::=
SEQUENCE {
multiBandInfoList SEQUENCE {
freqBandIndicator An overlapping Band Cell 1
under test Cell 2
(px_MFBI_FrequencyBan
d).
}
}
}
ETSI
Table 6.1.2.19.3.2-2)

SEQUENCE {
AdditionalSpectrumEmission 1 (NS_01) A-MPR doesn’t
apply by
default.
See TS 36.101
table 6.2.4-1.
}
}
}
6.1.2.20 Inter-frequency cell reselection / MFBI

(1)
ensure that {
when { an equal priority E-UTRAN inter-frequency neighbouring cell which has been included in the
multiBandInfoList provided by the serving cell becomes available, and, is better ranked than the
serving cell during a time interval TreselectionRAT, and, more than 1 second has elapsed since the
UE camped on the current serving }
}
TS 36.331, clause 6.3.1. Unless otherwise stated these are Rel-8 requirements.
[TS 36.304, clause 5.2.4.6]
where:

ETSI
[TS 36.331, clause 6.3.1]
The IE SystemInformationBlockType5 contains information relevant only for inter-frequency cell re-selection i.e.
information about other E-UTRA frequencies and inter-frequency neighbouring cells relevant for cell re-selection. The
IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters.

multiBandInfoList
Indicates the list of frequency bands in addition to the band represented by dl-CarrierFreq for which cell reselection
parameters are common. E-UTRAN indicates at most maxMultiBands frequency bands (i.e. the total number of entries
across both multiBandInfoList and multiBandInfoList-v9e0 is below this limit).
System Simulator:
- Cell 1 and Cell 3 have different tracking areas according to table 6.0.1-2 and are MFBI capable cells.
UE:
None.
Preamble:

T1 Cell-specific dBm/15kHz -85 -73 The power level values are set so that RCell 1
RS EPRE < RCell 2.
ETSI

U-S Message
0 Wait 1 second (to ensure than 1 second has - - - -
serving cell)
1.
Cell 3?
Table 6.1.2.20.3.3-1: SystemInformationBlockType1 for cell 1 and cell 3 (preamble)

BI).
SEQUENCE {
freqBandIndicator An Overlapping Band Cell 1
under test Cell 3
d).
}
}
}
Table 6.1.2.20.3.3-2: SystemInformationBlockType5 for cell 1 and cell 3 (preamble)

SEQUENCE {
InterFreqCarrierFreqList-v8h0 SEQUENCE {
InterFreqCarrierFreqInfo-v8h0 SEQUENCE {
freqBandIndicator An Overlapping Cell 1
Bandunder test Cell 3
d).
}
}
}
}
}
ETSI
6.1.2.21 Inter-band cell reselection / MFBI

(1)
ensure that {
when { an equal priority E-UTRAN another band neighbouring cell which has been included in the
multiBandInfoList provided by the serving cell becomes available, and, is better ranked than the
serving cell during a time interval TreselectionRAT, and, more than 1 second has elapsed since the
UE camped on the current serving cell }
}
5.2.4.6; TS 36.331, clause 6.3.1. Unless otherwise stated these are Rel-8 requirements.
[TS 36.304, clause 5.2.4.5]
[TS 36.304, clause 5.2.4.6]
where:

[TS 36.331, clause 6.3.1]
The IE SystemInformationBlockType5 contains information relevant only for inter-frequency cell re-selection i.e.
information about other E-UTRA frequencies and inter-frequency neighbouring cells relevant for cell re-selection. The
IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters.
ETSI

multiBandInfoList
Indicates the list of frequency bands in addition to the band represented by dl-CarrierFreq for which cell reselection
parameters are common. E-UTRAN indicates at most maxMultiBands frequency bands (i.e. the total number of entries
across both multiBandInfoList and multiBandInfoList-v9e0 is below this limit).
System Simulator:
- Cell 10 is MFBI capable cell.
- The E-UTRA Primary frequency band under test (px_ePrimaryFrequencyBand) is supported by the UE.
UE:
None.
Preamble:

T1 Cell-specific dBm/15kHz -85 -73 Cell 10 become stronger than Threshx, high.
RS EPRE

U-S Message
0 Wait 1 second. (to ensure than 1 second has - - - -
serving cell)
1.
Cell 10 belonging to the MFBI band
(px_MFBI_FrequencyBand)?
ETSI

in Tables 6.1.2.21.3.3-3 and 6.1.2.21.3.3-4
6.1.2.21.3.2-2)

supported frequency
(px_OverlappingNotSup
portedFrequencyBandM
FBI).
SEQUENCE {
under test
(px_MFBI_FrequencyBa
nd).
}
}
}
6.1.2.21.3.2-2)

SEQUENCE {
AdditionalSpectrumEmission 1 (NS_01) A-MPR doesn’t
apply by
default.
See TS 36.101
table 6.2.4-1.
}
}
}
ETSI
Table 6.1.2.21.3.2-2)

5 Cell 10
}
}
Table 6.1.2.21.3.2-2)

as used for Cell 10
as used for Cell 1
1 Cell 10
}
lateNonCriticalExtension Cell 1
SystemInformationBlockType5-v8h0-IEs ::= Cell 1
SEQUENCE {
InterFreqCarrierFreqList-v8h0 SEQUENCE (SIZE Cell 1
InterFreqCarrierFreqInfo-v8h0 [n] SEQUENCE { Cell 1
multiBandInfoList SEQUENCE { Cell 1
freqBandIndicator An overlapping Band for Cell 1
Cell 10 under test
(px_MFBI_FrequencyBa
nd).
}
}
}
}
}
6.2 Multi-mode environment (E-UTRAN, UTRAN, GERAN,

CDMA2000)
6.2.1 Inter-RAT PLMN selection
6.2.1.1 Inter-RAT PLMN Selection / Selection of correct RAT for OPLMN / Automatic
mode
(1)
with { UE pre-set in Automatic network selection mode }
ensure that {
when { UE is switched on and there are suitable E-UTRAN and UTRAN cells some on the OPLMN list and
some not on the OPLMN list, none of them being part of the RPLMN }
ETSI
then { UE selects the highest priority OPLMN and RAT combination, attaches on the selected cell
and when successfully registered indicates the PLMN to the user }
}
(2)
with { UE in Automatic network selection mode }
ensure that {
when { UE returns to coverage and there are suitable E-UTRAN and GERAN cells some on the OPLMN
list and some not on the OPLMN list , none of them being part of the RPLMN }
}
(3)
with { UE in Automatic network selection mode }
ensure that {
when { UE returns to coverage and there are suitable E-UTRAN and UTRAN cells some on the OPLMN
list and some not on the OPLMN list , none of them being part of the RPLMN }
}
4.4.3.1.1.
[TS 23.122, clause 4.4.3.1]
...
[TS 23.122, clause 4.4.3.1.1]
System Simulator
5 cells are used maximum 3 are operating at the same time:
- 3 cells belong to E-UTRAN (Cell 1, Cell 2 and Cell 3)
- IF pc_GERAN 1 cell belongs to GERAN (Cell 24)
- 1 cell belongs to UTRAN (Cell 9).
ETSI
UE
- The HPLMN is PLMN1
- There is no RPLMN.
USIM field Priority Value Access Comment

technology
EFPLMNwAcT 3GPP TS 31.102, The EF is empty.
Annex E
EFOPLMNwAcT 1 PLMN2 E-UTRAN
2 PLMN13 GERAN
3 PLMN13 UTRAN
4 PLMN13 E-UTRAN
Table 6.2.1.1.3.1-2: Void
Preamble
- The UE is in state Switched OFF (State 1)
Tables 6.2.1.1.3.2-1 and 2 show the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configuration marked "T1" to "T4" are applied at the point indicated in the Main behaviour
description in Table 6.2.1.1.3.2-3. Cell powers for the E-UTRAN, UTRAN and GERAN cells are defined in TS 36.508
Table 6.2.2.1-1.
Table 6.2.1.1.3.2-1: Cell PLMN identities
Cell PLMN name

1 PLMN2
9 PLMN13
3 PLMN14
24 PLMN13
2 PLMN13
ETSI
Parameter Unit Cell 1 Cell 2* Cell 3* Cell 9 Cell 24

name
T0 RS EPRE dBm/15kHz Serving cell OFF Serving cell
CPICH_Ec dBm/3.84 MHz Serving cell
P-CCPCH dBm/1.28 MHz Serving cell
RF Signal dBm OFF
Level
T1 RS EPRE dBm/15kHz OFF Serving cell Serving cell
RF Signal dBm OFF
Level
T2 RS EPRE dBm/15kHz Serving cell OFF OFF
CPICH_Ec dBm/3.84 MHz OFF
P-CCPCH dBm/1.28 MHz OFF
RF Signal dBm OFF
Level
T3 RS EPRE dBm/15kHz Serving cell OFF Serving cell
RF Signal dBm Serving cell
Level
T4 RS EPRE dBm/15kHz OFF Serving cell Serving cell
Level
*Only minimum uplink cell configuration required (See 6.3.3.2 in 36.508)
ETSI

U–S Message
2 Check: Does the UE send --> RRCConnectionRequest 1 P
3- Steps 3-17 of the registration procedure - - - -
17 described in TS 36.508 table 4.5.2.3-1 take
place. All messages are observed on Cell 1.
18 Check: Is PLMN2 indicated by the UE as the - - 1 P
PLMN on which the UE is camped?
table 6.2.1.1.3.2-2.
19 Check: Does the UE send RRC --> RRC CONNECTION REQUEST 3 P
A CONNECTION REQUEST on Cell 9?
19 Steps 2-10 of the routing area update - - - -
B- procedure described in TS 36.508 Table
19J 6.4.2.8-1 take place. All messages are
observed on Cell 9.
19 Check: Is PLMN13 indicated by the UE as the - - 3 P
K PLMN on which the UE is camped?
- EXCEPTION: Steps 20a1 to 20a32 describe
behaviour that depends on UE capabilities; the
"lower case letter" identifies a step sequence
that take place if the UE supports GERAN.
20a IF pc_GERAN THEN SS adjusts cell levels - - - -
1 according to row T2 of table 6.2.1.1.3.2-2.
20a The UE sends RRCConnectionRequest on --> RRCConnectionRequest - -
2 Cell 1
20a Steps 2-8 of generic test procedure in TS - - - -
3- 36.508 Table 6.4.2.7A-1 take place (the UE
20a performs a TAU procedure and the RRC
9 connection is released). All messages are
observed on Cell 1.
20a Void - - - -
10
–
20a
17
20a SS adjusts cell levels according to row T3 of - - - -
18 table 6.2.1.1.3.2-2.
20a Wait for 1s to allow the stable cell condition - - - -
19 before the next cell adjustments and catch any
not allowed UE behaviour (the UE is expected
not to do anything).
20a SS adjusts cell levels according to row T4 of - - - -
20 table 6.2.1.1.3.2-2.
20a Check: Does the UE send a CHANNEL --> CHANNEL REQUEST 2 P
21 REQUEST on Cell 24?
20a Steps 2-11 of the routing area update - - - -
22- procedure described in 36.508 table 6.4.2.9-1
20a take place. All messages are observed on Cell
31 24.
20a Check: Is PLMN13 indicated by the UE? - - 2 P
32
21- Void - - - -
46
ETSI
Table 6.2.1.1.3.3-1: System Information Block type 19 for Cell 9 (preamble and all steps from step 1
up to step 20a1, Table 6.2.1.1.3.2-3)

SysInfoType19 ::= SEQUENCE {
eutra-FrequencyAndPriorityInfoList Not present
}
Table 6.2.1.1.3.3-2: Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24 (step 20a2
onwards, Table 6.2.1.1.3.2-3)

Repeated E-UTRAN Neighbour Cells 0 Not Present
6.2.1.2 Inter-RAT PLMN Selection / Selection of correct RAT for UPLMN / Automatic
mode
(1)
with { UE in Automatic network selection mode and UPLMN and OPLMN cells available on E-UTRAN and
UTRAN}
ensure that {
when { UE is switched on}
then { UE selects a the highest priority UPLMN and RAT combination and UE attempts to attach on
the selected cell and when successfully registered indicates the PLMN to the user. }
}
(2)
with { UE in Automatic network selection mode and UPLMN and OPLMN cells available on E-UTRAN and
UTRAN}
ensure that {
when { UE returns to coverage}
then { UE selects a the highest priority VPLMN and RAT combination and UE attempts to attach on
the selected cell and when successfully registered indicates the PLMN to the user. }
}
4.4.3.1.1.
[TS 23.122, clause 4.4.3.1]
...
[TS 23.122, clause 4.4.3.1.1]
ETSI
System Simulator
- 3 cells are used: 2 cells belong to E-UTRAN and 1 cell belongs to UTRAN. The cells are configured as
specified in TS 36.508 clause 4.4.1.4 and Table 4.4.2-2.
UE
- The HPLMN is PLMN1

technology
2 PLMN14 UTRAN
EFOPLMNwAcT 1 PLMN2 All
2 PLMN14 UTRAN
3 PLMN13 E-UTRAN
Preamble
- Cell levels are set according to row T0 of table 6.2.1.2.3.2-2.
Tables 6.2.1.2.3.2 – 1 and 2 show the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configuration marked “T1” is applied at the point indicated in the Main behaviour description in
Table 6.2.1.2.3.2-3. Cell powers for the E-UTRAN cell are defined in TS36.508 Table 6.2.2.1-1 and cell powers for the
UTRAN cells are defined in TS 36.508 Table 6.2.2.1-1.
Cell PLMN name

1 PLMN2
9 PLMN14
12 PLMN13
ETSI
Parameter Unit Cell 1* Cell 9 Cell 12

name
T0 RS EPRE dBm/15kHz Serving cell Serving cell
T1 RS EPRE dBm/15kHz Serving cell Non-suitable
“Off”

U–S Message
3- The UE performs Steps 3-17 of the registration - - - -
17 procedure described in TS 36.508 table
4.5.2.3-1.
table 6.2.1.2.3.2-2.
20 Check: Does the UE send a RRC --> RRC CONNECTION REQUEST 2 P
CONNECTION REQUEST on Cell 9?
21- The UE performs Steps 2-10 of the routing - - - -
29 area update procedure described in TS 36.508
Table 6.4.2.8-1.
Table 6.2.1.2.3.3-1: System Information Block type 19 for Cell 9 (preamble and all steps, Table
6.2.1.2.3.2-2)

eutra-FrequencyAndPriorityInfoList Not present
6.2.1.3 Inter-RAT PLMN Selection / Selection of correct PLMN and RAT in shared
network environment / Automatic mode
(1)
with { UE in Automatic network selection mode and shared OPLMN cells available on E-UTRAN and UTRAN
}
ensure that {
when { UE is switched on}
then { UE selects a the highest priority OPLMN and RAT combination and UE attempts to attach on
the selected cell and PLMN and when successfully registered indicates the correct PLMN to the user.
}
}
(2)
with { UE in Automatic network selection mode and shared OPLMN cells available on E-UTRAN and UTRAN
}
ensure that {
ETSI
then { UE selects a the highest priority OPLMN and RAT combination and UE attempts to attach on
the selected cell and PLMN and when successfully registered indicates the correct PLMN to the user.
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3, 4.4.3.1
and 4.4.3.1.1.
[TS 23.122, clause 4.4.3]
[TS 23.122, clause 4.4.3.1]
of coverage, see subclause 4.5.2) attempts to perform a Location Registration.
[TS 23.122, clause 4.4.3.1.1]
System Simulator
- 3 cells are used: 2 cells belong to E-UTRAN and 1 cell belongs to UTRAN. The cells are configured as
UE
- The HPLMN is PLMN1.
ETSI

technology
2 PLMN2 UTRAN
3 PLMN14 UTRAN
4 PLMN13 E-UTRAN
Preamble
conditions. Subsequent configuration marked “T1” is applied at the point indicated in the Main behaviour description in
Table 6.2.1.3.3.2-3. Cell powers for the E-UTRAN cell are defined in TS 36.508 Table 6.2.2.1-1 and cell powers for the
UTRAN cells are defined in TS 36.508 Table 6.2.2.1-1.
Cell PLMN name

1 PLMN13,PLMN2
9 PLMN14, PLMN13
12 PLMN13, PLMN14
Parameter Unit Cell 1 Cell 9 Cell 12*

name
T1 RS EPRE dBm/15kHz Non-suitable Serving cell
“Off”
ETSI

U–S Message
3- The UE performs Steps 3-17 of the registration - - - -
17 procedure described in TS 36.508 table
4.5.2.3-1.
table 6.2.1.3.3.2-2.
20 Check: Does the UE send a RRC --> RRC CONNECTION REQUEST 2 P
CONNECTION REQUEST on Cell 9?
20 Void - - - -
A
20 Void - - - -
B
21- The UE performs Steps 2-10 of the routing - - - -
29 area update procedure described in TS 36.508
Table 6.4.2.8-1.
Table 6.2.1.3.3.3-1: SystemInformationBlockType1 for Cell 1(all steps, Table 6.2.1.3.3.2-3)

SEQUENCE {
plmn-Identity[1] PLMN13.
plmn-Identity[2] PLMN2
}
}
}
Table 6.2.1.3.3.3-2: MasterInformationBlock for Cell 9 (all steps, Table 6.2.1.3.3.2-3)
Derivation path: 34.108 Section 6.1.0a

- Supported PLMN types
- PLMN type GSM-MAP
- PLMN identity PLMN14
- Multiple PLMN List
- MIB PLMN Identity TRUE
- PLMN identity with Optional MCC[1] PLMN13
ETSI
Table 6.2.1.3.3.3-3: SystemInformationBlockType1 for Cell 12 (all steps, Table 6.2.1.3.3.2-3)

SEQUENCE {
}
}
}
Table 6.2.1.3.3-4: RRCConnectionSetupComplete (Step 5, Table 6.2.1.3.3.2-3)
Derivation Path: 36.331 clause 6.2.2

c1 CHOICE {
Table 6.2.1.3.3-5: INITIAL DIRECT TRANSFER (Step 23, Table 6.2.1.3.3.2-3)

PLMN identity PLMN14
Intra Domain NAS Node Selector
- CHOICE version R99
- CHOICE CN type GSM-MAP
- CHOICE Routing basis (P)TMSI of different
PLMN
Table 6.2.1.3.3-6: System Information Block type 19 for Cell 9 (all steps, Table 6.2.1.3.3.2-3)

eutra-FrequencyAndPriorityInfoList ::= SEQUENCE
(SIZE (1..maxNumEUTRAFreqs) OF SEQUENCE {
earfcn [n] Same downlink EARFCN
as used for Cell 12
priority [n] 2
}
}
6.2.1.4 Inter-RAT PLMN Selection / Selection of correct RAT from the OPLMN list /
Manual mode
(1)
with { UE in Manual network selection mode and OPLMN cells available on E-UTRAN and GERAN}
ensure that {
when { the USER selects an OPLMN}
then { UE selects a the highest priority RAT for the OPLMN and UE attempts to attach on the
selected cell and when successfully registered indicates the PLMN to the user. }
}
ETSI
(2)
with { UE in Manual network selection mode and OPLMN cells available on E-UTRAN and GERAN}
ensure that {
when { the USER selects an OPLMN and RAT combination}
then {UE attempts to attach on the selected OPLMN and RAT combination and when successfully
registered indicates the PLMN to the user. }
}
[TS 23.122, clause 4.4.3.1.2]
The MS indicates whether there are any PLMNs, which are available using all supported access technologies. This
includes PLMNs in the "forbidden PLMNs" list and PLMNs which only offer services not supported by the MS. An MS
which supports GSM COMPACT shall also indicate GSM COMPACT PLMNs (which use PBCCH).
If displayed, PLMNs meeting the criteria above are presented in the following order:
i)- either the HPLMN (if the EHPLMN list is not present or is empty) or, if one or more of the EHPLMNs are
available then based on an optional data field on the SIM either only the highest priority available EHPLMN is
to be presented to the user or all available EHPLMNs are presented to the user in priority order. If the data field
is not present on the SIM, then only the highest priority available EHPLMN is presented;
ii)- PLMN/access technology combinations contained in the " User Controlled PLMN Selector with Access
Technology " data file in the SIM (in priority order);
iii)- PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access
iv)- other PLMN/access technology combinations with received high quality signal in random order;
v)- other PLMN/access technology combinations in order of decreasing signal quality.
The user may select his desired PLMN and the MS then initiates registration on this PLMN using the access technology
chosen by the user for that PLMN or using the highest priority available access technology for that PLMN, if the
associated access technologies have a priority order. (This may take place at any time during the presentation of
PLMNs). For such a registration, the MS shall ignore the contents of the "forbidden LAs for roaming", "forbidden TAs
for roaming", "forbidden LAs for regional provision of service", "forbidden TAs for regional provision of service",
"forbidden PLMNs for GPRS service" and "forbidden PLMNs" lists.
NOTE 1: It is an MS implementation option whether to indicate access technologies to the user. If the MS does
display access technologies, then the access technology selected by the user is only used for initial
registration on the selected PLMN. If the MS does not display access technologies, then the access
technology chosen for a particular PLMN should be the highest priority available access technology for
that PLMN, if the associated access technologies have a priority order, and is only used for initial
registration.
System Simulator
- 3 cells are used: 2 cells belong to E-UTRAN and 1 cell belongs to GERAN. The cells are configured as
UE
ETSI

technology
2 PLMN2 GERAN
3 PLMN2 UTRAN
4 PLMN13 E-UTRAN
Preamble
- The UE is equipped with a USIM with default settings except for the ones specified in table 6.2.1.4.3.1–1 then
the UE is attached to PLMN1 and the UE is set to Manual PLMN selection mode before it is switched off.
conditions after preamble. Cell powers for the E-UTRAN cell are defined in TS36.508 Table 6.2.2.1-1 and cell powers
for the GERAN cell are defined in TS 36.508 Table 6.2.2.1-1.
Cell PLMN name

1 PLMN2
12 PLMN13
24 PLMN2
Parameter Unit Cell 1 Cell 12* Cell 24

name
Level
ETSI

U–S Message
2 Make the UE display the list of available - - - -
PLMNs.
3 Void - - - -
4 Void - - - -
5- Void - - - -
19
20 Void - - - -
- EXCEPTION: Steps 21a1 to 21b18 describe - - - -
behaviour that depends on UE capabilities; the
that takes place if the condition is met.
21a IF pc_Available_PLMNs_AcT_Ind (Support of - - - -
1 Access Technology Indication in available
PLMNs list)
THEN
PLMN2 (GERAN) is selected
21a The UE completes the registration procedure - - - -
2 on GERAN cell 24 as specified in TS 51.010-1
clause 41.2.8.1.1.
21a Check: Is PLMN2 indicated by the UE as the - - 2 P
3 PLMN on which the UE is registered?
21b ELSE (No Access Technology shown to the
1 User)
PLMN2 is selected
21b Check: Does the UE send an --> RRCConnectionRequest 1 P
2 RRCConnectionRequest on cell 1?
21b The UE performs Steps 3-17 of the registration - - - -
3- procedure described in TS 36.508 table
21b 4.5.2.3-1.
17
21b Check: Is PLMN2 indicated by the UE as the - - 1 P
18 PLMN on which the UE is registered?
None
6.2.1.5
6.2.1.6 Inter-RAT Background HPLMN Search / Search for correct RAT for HPLMN /
Automatic Mode
with { UE in Automatic network selection mode is camped on a GERAN VPLMN cell and HPLMN cell
available on E-UTRAN}
ensure that {
then { UE detects E_UTRA cell and camps on the E-UTRA cell }
}
[TS 23.122, clause 4.4.3.3.1]
ETSI
Mode in subclause 4.4.3.1.1. In the case that the mobile has a stored "Equivalent PLMNs" list the mobile shall only
select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN which are stored
in the "Equivalent PLMNs" list. For this purpose, a value T minutes may be stored in the SIM, T is either in the range
6 minutes to 8 hours in 6 minute steps or it indicates that no periodic attempts shall be made. If no value is stored in the
SIM, a default value of 60 minutes is used.
a) The periodic attempts shall only be performed in automatic mode when the MS is roaming, and not while
attached for emergency bearer services;
c) The MS shall make the following attempts if the MS is on the VPLMN at time T after the last attempt;
d) Periodic attempts shall only be performed by the MS while in idle mode;
e) If the HPLMN (if the EHPLMN list is not present or is empty) or a EHPLMN (if the list is present) or a higher
priority PLMN is not found, the MS shall remain on the VPLMN.
f) In steps i), ii) and iii) of subclause 4.4.3.1.1 the MS shall limit its attempts to access higher priority
PLMN/access technology combinations to PLMN/access technology combinations of the same country as the
current serving VPLMN, as defined in Annex B.
g) Only the priority levels of Equivalent PLMNs of the same country as the current serving VPLMN, as defined in
Annex B, shall be taken into account to compare with the priority level of a selected PLMN.
h) If the PLMN of the highest priority PLMN/access technology combination available is the current VPLMN, or
one of the PLMNs in the "Equivalent PLMNs" list, the MS shall remain on the current PLMN/access technology
combination.
System Simulator
- GERAN VPLMN Cell 24 serving cell
- E-UTRAN HPLMN Cell 1 off
- Table 6.2.1.6.3.1-1 shows the cell configuration used during the test
- Table 6.2.1.6.3.1-1: Cell PLMN identities
Cell PLMN name

1 PLMN1
24 PLMN15
ETSI
UE

technology
2 PLMN15 GERAN
EFHPPLMN 1(=6 min) The HPLMN Search Period on
the USIM shall be set to 6
minutes.
Preamble
- The UE is equipped with a USIM with default settings except for the ones specified in table 6.2.1.6.3.1–2.
- The UE is switched off..
Tables 6.2.1.6.3.2 – 1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
texts in this clause. Cell powers for the E-UTRAN cell are defined in TS36.508 Table 6.2.2.1-1 and cell powers for the
GERAN cell are defined in TS 36.508 Table 6.2.2.1-1.
Parameter Unit Cell 1 Cell 24

name
T1 RS EPRE dBm/15kHz -60 Same as before
*Only minimum uplink cell configuration required(See 6.3.3.2 in 36.508)

U–S Message
0A Power on the UE. - - - -
1 SS starts timer of tmin = 2 minutes and tmax - - - -
=(6 minutes + cell selection time)
(Note 1)
1A The UE completes the registration procedure - - - -
on GERAN cell as specified in TS 51.010-1
clause 41.2.8.1.1.
2 SS adjusts cell levels for Cell 1 according to - - - -
row T1 of table 6.2.1.6.3.2-1
3 Check: Does the UE send an --> RRC: RRCConnectionRequest 1 P
RRCConnectionRequest on cell 1 after tmin
but before tmax expires?
(Note 1)
4- The steps from step 2 to step 8 as specified in - - - -
10 TS 36.508 Table 6.4.2.7A-2 shall take place
Note 1: Timers tmin and tmax in step 1 and 3 are derived from the high priority PLMN search timer T defined by
EFHPPLMN
6.2.2 Inter-RAT cell selection

6.2.2.1 Inter-RAT cell selection / From E-UTRA RRC_IDLE to UTRA_Idle / Serving
cell becomes non-suitable
(1)
ETSI
ensure that {
when { the serving cell becomes non-suitable and there is a suitable UTRA neighbour cell }
then { UE selects the suitable UTRA neighbour cell }
(2)
ensure that {
when { the serving cell becomes barred and there is a suitable UTRA neighbour cell}
then { UE selects the suitable UTRA neighbour cell }
}
Note: (SServingCell<0 or barred) conidtion is for rel 8; (Srxlev<0 or Squal<0 or barred) condition
is for rel 9.
References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3,5.2.1,
5.2.3.2 and 5.3.1. TS 25.304, clause 5.2.3.2.
[TS 36.304, clause 4.1]
[5].
performed.
[TS 36.304, clause 4.3]
suitable cell:
A "suitable cell" is a cell on which the UE may camp on to obtain normal service. Such a cell shall fulfil all the
following requirements.
- The cell is part of either:
- the selected PLMN, or:
- the registered PLMN, or:
- a PLMN of the Equivalent PLMN list
according to the latest information provided by NAS:
- The cell is not barred, see subclause 5.3.1;
- The cell is part of at least one TA that is not part of the list of "forbidden tracking areas for roaming" [4], which
belongs to a PLMN that fulfils the first bullet above;
- The cell selection criteria are fulfilled, see subclause 5.2.3.2;
- For a CSG cell, the CSG ID is part of the allowed CSG list of the UE.
If more than one PLMN identity is broadcast in the cell, the cell is considered to be part of all TAs with TAIs
constructed from the PLMN identities and the TAC broadcast in the cell.
barred cell:
A cell is barred if it is so indicated in the system information [3].
[TS 36.304, clause 5.2.1]
ETSI
[TS 36.304, clause 5.2.3.2]
Srxlev > 0
Where:
Where:

[TS 36.304, clause 5.3.1]
Elements:

In case of multiple PLMNs indicated in SIB1, this IE is common for all PLMNs
- else

ETSI

The cell selection of another cell may also include a change of RAT.
[TS 25.304, clause 5.2.3.2]
for FDD cells: Srxlev > 0 AND Squal > 0
for TDD cells: Srxlev > 0
Where:
Squal = Qqualmeas – Qqualmin
Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation
Squal Cell Selection quality value (dB)

Applicable only for FDD cells.
Qqualmeas Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0
(dB) for FDD cells. CPICH Ec/N0 shall be averaged as specified in [10]. Applicable only
for FDD cells.
Qrxlevmeas Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm)
and P-CCPCH RSCP for TDD cells (dBm).
Qqualmin Minimum required quality level in the cell (dB). Applicable only for FDD cells.
Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB)
UE_TXPWR_MAX_RACH Maximum TX power level an UE may use when accessing the cell on RACH (read in
system information) (dBm)
P_MAX Maximum RF output power of the UE (dBm)
System Simulator:
- Cell 1 and Cell 5
UE:
None.
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell 1 (serving cell) according to [18].
ETSI
Tables 6.2.2.1.3.2-1 & 6.2.2.1.3.2-2 illustrates the downlink power levels and other changing parameters to be applied
for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and " T3" are
applied at the points indicated in the Main behaviour description in Table 6.2.2.1.3.2-3.

Cell-specific RS EPRE dBm -120 SrxlevCell 1 < 0
T1
Srxlev* dB -10 Cell 5 becomes the strongest cell
T2 Cell-specific RS EPRE dBm -60
Cell-specific RS EPRE dBm -60 SrxlevCell 1 > SrxlevCell 5 > 0
T3 Srxlev* dB 50
cellBarred - Barred Serving cell becomes barred
Note: Srxlev is calculated in the UE

T1 CPICH_Ec dBm/3.84 MHz -70 SrxlevCell 5 > 0,for FDD
P-CCPCH dBm/1.28 MHz -72 SrxlevCell 5 > 0,for TDD
Srxlev* dB 9 Cell 5 becomes the strongest cell or
the suitable cell
T2 CPICH_Ec dBm/3.84 MHz OFF
T3 CPICH_Ec dBm/3.84 MHz -70 SrxlevCell 5 > 0,for FDD
P-CCPCH dBm/1.28 MHz -72 SrxlevCell 5 > 0,for TDD
Srxlev* dB 9
ETSI

U-S Message
0 Wait for 6 s for UE to receive system - - - -
information.
6.2.2.1.3.2-1 & Cell 5 power level is set
according to row "T1" in table 6.2.2.1.3.2-2.
indicate that the UE is camped on UTRAN Cell
5?
NOTE: The UE performs a RAU procedure
4 Generic test procedure in TS 36.508 Table - - - -
6.4.2.7A-1 is performed and the UE will
camped on E-UTRAN Cell 1.
information.
6 SS changes Cell 5 power level according to <-- Paging - -
row "T3" in table 6.2.2.1.3.2-2 and modifies
System Information so that Cell 1 becomes
barred according to row "T3" in table
6.2.2.1.3.2-1. The SS transmits a Paging
message including systemInfoModification.
6A Void - - - -
5?
NOTE: The UE performs a RAU procedure.
Table 6.2.2.1.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble and steps 1 to 5, Table

6.2.2.1.3.2-3)

q-Rxlevmin -55 (-110 dBm)
q-Rxlevminoffset Not present
}
}
Table 6.2.2.1.3.3-2: Paging for Cell 1 (step 6, Table 6.2.2.1.3.2-3)

}
ETSI

cellBarred barred
}
}
0
}
6.2.2.2 Inter-RAT cell selection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS

Packet_idle / Serving cell becomes non-suitable
(1)
ensure that {
when { the serving cell becomes non-suitable and there is a suitable GSM neighbour cell }
then { UE selects the suitable GSM neighbour cell }
(2)
ensure that {
when { the serving cell becomes barred and there is a suitable GSM neighbour cell}
then { UE selects the suitable GSM neighbour cell }
}
NOTE: (SServingCell<0 or barred) conidtion is for Rel 8; (Srxlev<0 or Squal<0 or barred) condition is for Rel 9.
References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3,5.2.1,
5.2.3.2, 5.3.1, 43.022, clause 3.6 and TS 45.008, clause 6.4.
[TS 36.304, clause 4.1]
[5].
performed.
[TS 36.304, clause 4.3]
suitable cell:
ETSI
barred cell:
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]
Srxlev > 0
Where:
Where:

[TS 36.304, clause 5.3.1]
Elements:
ETSI

In case of multiple PLMNs indicated in SIB1, this IE is common for all PLMNs
- else


The cell selection of another cell may also include a change of RAT.
[TS 43.022, clause 3.6]
The MS uses a "path loss criterion" parameter C1 to determine whether a cell is suitable to camp on. C1 depends on 4
parameters:
i) The received signal level (suitably averaged);
ii) The parameter RXLEV_ACCESS_MIN, which is broadcast as system information, and is related to the
minimum signal that the operator wants the network to receive when being initially accessed by an MS;
iii) The parameter MS_TXPWR_MAX_CCH, which is also broadcast as system information, and is the maximum
power that an MS may use when initially accessing the network;
iv) The maximum power of the MS.
The formula for determining C1 is given in 3GPP TS 45.008.
Use of the parameter C1 enables the MS to determine whether communication is possible with the network in the
absence of interference. However because of the possibility of interference degrading the communications, an additional
safeguard is used. This is to monitor the success rate of the MS in decoding signalling blocks of the paging subchannel.
If there is a downlink signalling failure, i.e. the success rate drops too low, this indicates probable interference on the
downlink, and the MS attempts to find another suitable cell. Downlink signalling failure monitoring is specified in
3GPP TS 45.008.
In order to optimize cell reselection, additional cell reselection parameters can be broadcast as system information of
each cell. The cell reselection process employs a parameter C2 which depends on these parameters.
The parameters used to calculate C2 are as follows:
i) CELL_RESELECT_OFFSET (see subclause 3.5.2.2);
ii) PENALTY_TIME;
ETSI
When the MS places the cell on the list of the strongest carriers as specified in 3GPP TS 45.008, it starts a timer
which expires after the PENALTY_TIME. This timer will be reset when the cell is taken off the list. For the
duration of this timer, C2 is given a negative offset. This will tend to prevent fast moving MSs from selecting the
cell.
iii) TEMPORARY_OFFSET;
This is the amount of the negative offset described in (ii) above. An infinite value can be applied, but a number
of finite values are also possible.
The permitted values of these parameters and the way in which they are combined to calculate C2 are defined in 3GPP
TS 45.008.
Instead of the parameter C2, a GPRS MS applies the corresponding GPRS parameter if provided.
[TS 45.008, clause 6.4]
The path loss criterion parameter C1 used for cell selection and reselection is defined by:
C1 = (A - Max(B,0))
where
A = RLA_C - RXLEV_ACCESS_MIN
B = MS_TXPWR_MAX_CCH - P
except for the class 3 DCS 1 800 MS where:
B = MS_TXPWR_MAX_CCH + POWER OFFSET - P

RXLEV_ACCESS_MIN = Minimum received signal level at the MS required for access to the
system.
MS_TXPWR_MAX_CCH = Maximum TX power level an MS may use when accessing the system
until otherwise commanded.
POWER OFFSET = The power offset to be used in conjunction with the MS TXPWR
MAX CCH parameter by the class 3 DCS 1 800 MS.
P = Maximum RF output power of the MS.
All values are expressed in dBm.
The path loss criterion (3GPP TS 43.022) is satisfied if C1 > 0.
System Simulator:
- Cell 1 and Cell 24
UE:
None.
Preamble:
for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and "T3" are
ETSI

Cell-specific RS EPRE dBm -120 SrxlevCell 1 < 0
T1
Srxlev* dB -10 Cell 24 becomes the strongest cell
T2 Cell-specific RS EPRE dBm -60
Cell-specific RS EPRE dBm -60 SrxlevCell 1 > SrxlevCell 24 > 0
T3 Srxlev* dB 50
cellBarred - Barred Serving cell becomes barred

T1 RF Signal Level dBm -80 SrxlevCell 24 > 0
C1* dB 20 Cell 24 becomes the strongest cell
T2 RF Signal Level dBm OFF
T3 RF Signal Level dBm -80 SrxlevCell 24 > 0
C1* dB 20
Note: C1 is calculated in the UE

U-S Message
0 Void - - - -
6.2.2.2.3.2-1 & cell 24 power level is set
indicate that the UE is camped on GERAN Cell
24?
4 Generic test procedure in TS 36.508 Table - - - -
6.4.2.7A-1 is performed and the UE will be
camped on E-UTRAN Cell 1.
5 Void - - - -
6 SS changes Cell 24 power level according to <-- Paging - -
6.2.2.2.3.2-1. SI2Quater for cell 24 is updated
according to table 6.2.2.2.3.3-4 to reflect the
cell barring. The SS transmits a Paging
message including systemInfoModification.
24?
ETSI
Table 6.2.2.2.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble and steps 1 to 5, Table

6.2.2.2.3.2-3)

}
}

cellBarred barred
}
}
0
}
Table 6.2.2.2.3.3-3: Paging for Cell 1 (step 6, Table 6.2.2.2.3.2-3)

}
Table 6.2.2.2.3.3-4: Repeated E-UTRAN Neighbour Cells struct of SI2Quarter for Cell 24 (step 6, Table
6.2.2.3.2-3)

Repeated E-UTRAN Not Allowed Cells struct > ::= {
Not Allowed Cells : < PCID Group IE >>{
PCID} ‘000000000’B PCID=0, Meaning
that the Cell 1 which
have PCID=0 will not
be allowed
E-UTRAN_FREQUENCY_INDEX ‘000’B Cell 1
}
ETSI
6.2.2.3 Inter-RAT Cell selection / From E-UTRA RRC_IDLE to HRPD Idle / Serving
(1)
ensure that {
when { the serving cell becomes non-suitable and there is a suitable neighbour HRPD cell (S>0) }
then { UE selects the suitable neighbour HRPD cell }
}
is for rel 9.
TS 36.304, clause 4.1, 5.2.1, and 5.2.3.2.
[TS 36.300, clause 10.1.1.1]
Cell selection:
is not barred;
[TS 36.304, clause 4.1]
[5].
performed.
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]
ETSI
Srxlev > 0
Where:
Where:

Pcompensation [FFS]
System Simulator:
- Cell 1 is a cell on E-UTRA
- Cell 15 is a cell on HRPD
UE:
None
Preamble:
various time instants of the test execution. Subsequent configurations marked "T1" and “T2” are applied at the points
ETSI
Îor/Ioc dB - -5 Cell 15 is on
Ioc dBm/1.23 MHz - -55
T1
Pilot Ec/Io (Note 1) dB - -6
Cell-specific RS EPRE dBm/15 KHz -60
Cell-specific RS EPRE dBm/15 kHz -120 - SrxlevCell 1 <0 and Cell 15 becomes the
Srxlev* dB -10 strongest cell
T2 Îor/Ioc dB - -5
Note 1: This parameter is not directly settable, but is derived by calculation from the other parameters set by the
SS.

U-S Message
level of Cell 15 according to "T1" in 6.2.2.3.3.2-
1.
1A SS waits [10s] to allow the UE to read the - - - -
system information
level of Cell 1 according to "T2" in 6.2.2.3.3.2-
1.
3 Check: Does the UE transmit an Access Probe --> Access Probe 1 P
on Cell 15?
Table 6.2.2.3.3.3-1 SystemInformationBlockType1 to Cell 1 (Preamble and all steps, table 6.2.2.3.3.2-2)
Derivation path: 36.508 table clause 4.4.3.2

}
}
ETSI
Table 6.2.2.3.3.3-2: SystemInformationBlockType8 to Cell 1 (Preamble and all steps, table 6.2.2.3.3.2-
2)
Derivation path: 36.508 table 4.4.3.3

systemTimeInfo SEQUENCE {
cdma-EUTRA-Synchronisation TRUE
cdma-SystemTime CHOICE {
synchronousSystemTime A valid value as per TS
36.331 and calculated by
the SS
}
}
searchWindowSize 5
parametersHRPD SEQUENCE {
cellReselectionParametersHRPD SEQUENCE {
bandClassList SEQUENCE (SIZE (1..maxCDMA - The same number of
BandClass)) OF SEQUENCE { entries as the configured
HRPD carriers
bandClass Band Class of frequency [Set according to
under test specific test case]
cellReselectionPriority 5 [3 is applicable
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]
threshX-High 30(-30) INTEGER (0..63)
threshX-Low 32(-32) INTEGER (0..63)
}
t-ReselectionCDMA2000 0 INTEGER (0..7)
}
}
}
6.2.2.4 Inter-RAT Cell selection / From E-UTRAN RRC_IDLE to 1xRTT idle / Serving
(1)
ensure that {
when { the serving cell becomes non-suitable and
there is a suitable neighbour 1xRTT cell (S>0) }
then { UE selects the suitable neighbour 1xRTT cell }
}
is for rel 9.
TS 36.304, clause 4.1, 5.2.1, and 5.2.3.2.
[TS 36.300, clause 10.1.1.1]
Cell selection:
ETSI
is not barred;
[TS 36.304, clause 4.1]
the chosen cell and as outcome of a successful Location Registration the selected PLMN becomes the registered PLMN.
performed.
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]
Srxlev > 0
Where:
Where:
search for a higher priority PLMN while camped normally in a VPLMN. During this periodic search for higher priority
PLMN the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher
priority PLMN.

Pcompensation [FFS]
ETSI
System Simulator:
- Cell 1 is a cell on E-UTRA
- Cell 19 is a cell on 1xRTT
UE:
None.
Preamble:
various time instants of the test execution. The configurations marked "T1" and “T2” are applied at the point indicated
in the Main behaviour description in Table 6.2.2.4.3.2-2

T1 Îor/Ioc dB - 0 Cell 19 is on
Pilot Ec/ Ior -7
Ioc dBm - -75
CPICH_Ec/Io (Note 1) dB - -10
Cell-specific RS EPRE dBm/15 KHz -75 -
T2 Îor/Ioc dB - 0 SrxlevCell 1 <0 and Cell 19 becomes the
Pilot Ec/ Ior dB - -7 strongest cell
Cell-specific RS EPRE dBm/15 KHz -120 -
SS.

U-S Message
levels according to row “T1” in Table
6.2.2.4.3.2-1.
1A SS waits [10s] to allow the UE to read the - - - -
system information.
levels according to row "T2" in Table
6.2.2.4.3.2-1.
on Cell 19?
ETSI
Table 6.2.2.4.3.3-1 SystemInformationBlockType1 to Cell 1 (Preamble and all steps, table 6.2.2.4.3.2-1)

}
}
6.2.2.5 Cell selection / No USIM

(1)
with { UE fitted with no SIM/USIM }
ensure that {
when { UE is switched on }
then { UE camps on a non-LTE cell }
}
(2)
with { UE fitted with no SIM/USIM and camped on a non-LTE cell }
ensure that {
when { UE is requested to make an emergency call }
then { UE transmits an RRC CONNECTION REQUEST message }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 4.1.
[TS 36.304, clause 4.1]
A UE which is not equipped with a valid USIM (i.e. no UICC or SIM only), or which shall consider the USIM as
invalid for EPS services as defined in [15] and [16] (e.g. due to a LR reject #3, #6, #7, #8) shall disable all its E-
UTRAN capabilities until switching off or the UICC containing the USIM is removed.
System Simulator:

Cell-specific RS EPRE dBm -70 -
CPICH_Ec (UTRA -75
dBm/3.84 MHz -
FDD)
T0
PCCPCH_Ec (UTRA
dBm/1.28 MHz - -77
LCR TDD)
UE:
- The UE is not equipped with a USIM.
ETSI
Preamble:

U-S Message
1 The UE is switched on. -
- - -
2 Wait for 60s for the UE to complete cell -
- - -
selection. E-UTRA cell is more powerful than
UTRA cell
3 Cause the UE to originate Emergency call. - - - -
(see Note 1)
4 Check: Does the UE transmit an RRC --> RRC CONNECTION REQUEST 1, 2 P
CONNECTION REQUEST message on Cell
5?
5 The SS transmits an RRC CONNECTION <-- RRC CONNECTION SETUP - -
SETUP message on Cell 5.
6 The UE transmits an RRC CONNECTION --> RRC CONNECTION SETUP - -
SETUP COMPLETE message on Cell 5. COMPLETE
7 The UE transmits an INITIAL DIRECT --> INITIAL DIRECT TRANSFER - -
TRANSFER message on Cell 5.
This message includes a CM SERVICE
REQUEST message.
8 The SS transmits a DOWNLINK DIRECT <-- DOWNLINK DIRECT TRANSFER - -
This message includes a CM SERVICE
ACCEPT message.
9 The UE transmits an UPLINK DIRECT --> UPLINK DIRECT TRANSFER - -
This message includes an EMERGENCY
SETUP message.
This message includes a CALL PROCEEDING
message.
11 The SS transmits a RADIO BEARER SETUP <-- RADIO BEARER SETUP - -
message on Cell 5.
12 The UE transmits a RADIO BEARER SETUP --> RADIO BEARER SETUP - -
COMPLETE message on Cell 5. COMPLETE
This message includes an ALERTING
message.
This message includes a CONNECT message.
15 The UE transmits an UPLINK DIRECT --> UPLINK DIRECT TRANSFER - -
This message includes a CONNECT
ACKNOWLEDGE message.
Note 1: The request is assumed to be triggered by AT command D.
None.
ETSI
6.2.2.6 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-

UTRA_RRC_IDLE / Serving cell becomes non-suitable
(1)
with { UE in GSM/GPRS Registered state and no RR connection }
ensure that {
when { the serving cell becomes non-suitable and there is a suitable E-UTRA neighbour cell }
then { UE selects the suitable E-UTRA neighbour cell }
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.4 .
...
[TS 45.008, clause 6.4]
C1 = (A - Max(B,0))
where

system.
System Simulator:
- Two cells:
- One GERAN cell, Cell 24 is serving cell.
- One E-UTRAN cell, Cell 1 is Suitable neighbour inter-RAT cell.
UE:
None.
Preamble:
ETSI
Tables 6.2.2.6.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 the preamble, while
rows marked "T1" are to be applied subsequently. The exact instants on which these values shall be applied are

Cell-specific RS EPRE dBm/15kHz -120 - SrxlevCell 1 < 0
Qrxlevmin dBm -110 - -
T0
Srxlev* dB N/A - -
RF Signal level dBm - -80 -
Cell-specific RS EPRE dBm/15kHz -70 - -
Srxlev* dB 30 - SrxlevCell 1 >THRESH_E-
T1
UTRAN_high
RF Signal level dBm - OFF -

U-S Message
table 6.2.2.6.3.2-1
procedure in TS 36.508 subclause 6.4.2.7 A-2
Cell 1?
None.
6.2.2.7 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-

UTRA_RRC_IDLE ,when the serving cell is barred.
(1)
ensure that {
when { the serving cell becomes barred and there is a suitable E-UTRA neighbour cell}
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.4 and 6.6.1,
&TS 43.022 clause 3.2.1.
...
[TS 45.008, clause 6.4]
ETSI
C1 = (A - Max(B,0))
where

system.
[TS 45.008, clause 6.6.1]
The MS shall attempt to decode the full BCCH data of the serving cell at least every 30 seconds or at least as often as
possible in the case that system information scheduling period exceeds 30 seconds.
If SI13 is broadcast, the MS supporting change mark in SI13 (See 3GPP TS 44.018) is only required to confirm system
information on the BCCH of the serving cell if indicated by change mark in SI13.
[TS 43.022, clause 3.2.1]
The choice of such a suitable cell for the purpose of receiving normal service is referred to as "normal camping". There
are various requirements that a cell must satisfy before an MS can perform normal camping on it:
i) It should be a cell of the selected PLMN or, if the selected PLMN is equal to the last registered PLMN, an
equivalent PLMN;
ii) It should not be "barred" (see subclause 3.5.1);
System Simulator:
- Two cells:
- One E-UTRAN cell, Cell 1 is Suitable neighbour inter-RAT cell.
UE:
None.
Preamble:
Tables 6.2.2.7.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
ETSI

Cell-specific RS EPRE dBm/15kHz -120 - SrxlevCell 1 < 0
Qrxlevmin dBm -110 -
Srxlev* dB N/A -
T0
RF Signal Level dBm - -80
RXLEV_ACCESS_MIN dBm - -101
C1* dB - 21
Cell-specific RS EPRE dBm/15kHz -70 -
Srxlev* dB 30 - SrxlevCell 1 >THRESH_E-
UTRAN_high
T1
RF Signal Level dBm - -80
RXLEV_ACCESS_MIN dBm - 21
C1* dB - Barred

U-S Message
1 SS adjusts cells according to row T1 of table - - - -
6.2.2.7.3.2-1 and SI2 IE cellBarred according
to row "T1" in table 6.2.2.7.3.2-1.
procedure in TS 36.508 Table 6.4.2.7A-2
Cell 1?
Table 6.2.2.7.3.3-1: RACH Control Parameters of SI2, SI3 and SI4 for Cell 24(step 1, Table 6.2.2.7.3.2-3)
Derivation Path: 51.010-1 clause 40.2.1.1

RACH Control Parameters{
Cell Barred for Access Barred
}
Table 6.2.2.7.3.3-2: SI 13 Rest Octets of , SI13 for Cell 24(step 1, Table 6.2.2.7.3.2-3)
Derivation Path: 51.010-1 clause 40.2.1.1

BCCH_CHANGE_MARK { 001
SI_CHANGE_FIELD 0000
}
6.2.2.8 Inter-RAT cell selection / From UTRA_Idle to E-UTRA RRC_IDLE / Serving

(1)
with { UE in UTRA RRC_IDLE state }
ensure that {
when { the serving cell becomes non-suitable and there is a suitable E-UTRA neighbour cell }
ETSI
(2)
with { UE in UTRA RRC_IDLE state }
ensure that {
when { the serving cell becomes barred and there is a suitable E-UTRA neighbour cell}
}
is for rel 9.
References: The conformance requirements covered in the current TC are specified in: TS 25.304, clause 5.2.1, 4.3,
5.2.1.4, 5.2.3.2. TS 36.304, clause 4.1, 4.3,5.2.1 and 5.2.3.2.
[TS 25.304, clause 5.2.1]
[TS 25.304, clause 4.3]
suitable cell:
- The cell shall be part of either:
the selected PLMN, or:
the registered PLMN, or:
a PLMN of the Equivalent PLMN list
according to the latest information provided by the NAS.
- The cell is not barred, see subclause 5.3.1.1;
- The cell is part of at least one LA that is not part of the list of "forbidden LAs for roaming" [9], which belongs to
a PLMN that fulfils the first bullet above;
- The cell selection criteria are fulfilled, see subclause 5.2.3.1.2.
- For a CSG cell the CSG ID is part of the CSG whitelist of the UE.
If the IE “Multiple PLMN List” [4] is broadcast in the cell, the cell is considered to be part of all LAs with LAIs
constructed from the PLMN identities in the “Multiple PLMN List” and the LAC broadcast in the cell.
barred cell:
[TS 25.304, clause 5.2.5.1]
When camped normally, the UE shall perform the following tasks:
- execute the cell reselection evaluation process on the following occasions/triggers:
1) UE internal triggers, so as to meet performance as specified in [10] and [11];
2) When information on the BCCH used for the cell reselection evaluation procedure has been modified
[TS 36.304, clause 4.1]
ETSI
[5].
performed.
[TS 36.304, clause 4.3]
suitable cell:
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]
Srxlev > 0
Where:
Where:
ETSI

[TS 25.304, clause 5.2.3.2]
Where:
Squal = Qqualmeas – Qqualmin
Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation

for FDD cells.
System Simulator:
- Cell 1 and Cell 5
UE:
None.
Preamble:
- UE is in state Registered, Idle Mode (state 3 or 7) on Cell 5 (serving cell) according to [5].
ETSI
for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and " T3" are
Table 6.2.2.8.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell

Cell 1 becomes the strongest cell or
Cell-specific RS EPRE dBm/15kHz -70
T1 the suitable cell
Srxlev* dB 36 SrxlevCell 1 > 0
Power level “Off” is defined in
T2 Cell-specific RS EPRE dBm/15kHz “Off”
TS36.508 Table 6.2.2.1-1.
T3
Srxlev* dB 21
Table 6.2.2.8.3.2-2: Time instances of cell power level and parameter changes for UTRA cell

CPICH_Ec dBm/3.84 MHz -90 SrxlevCell 5 < 0,for FDD
T1 P-CCPCH dBm/1.28 MHz -92 SrxlevCell 5 < 0,for TDD
Srxlev* dB -11
CPICH_Ec dBm/3.84 MHz -60
T2 P-CCPCH dBm/1.28 MHz -62
Srxlev* dB 19
P-CCPCH dBm/1.28 MHz -52
T3 Srxlev* dB 29 SrxlevCell 5 > SrxlevCell 1 > 0
Serving cell becomes barred

Note : Srxlev is calculated in the UE
ETSI

U-S Message
procedure in TS 36.508 Table 6.4.2.7A-2 is
performed and the UE is camped on E-UTRAN
Cell 1?
2A Wait for [5] s for UE to receive system - - - -
information.
4 Generic test procedure in TS 36.508 - - - -
camped on UTRAN Cell 5.
5 SS changes Cell 1 power level according to <-- PAGING TYPE 1 - -
6.2.2.8.3.2-2. The SS transmits a PAGING
TYPE 1 message including "BCCH
Modification Information”.
Cell 1?
the RRC Connection is released.
Table 6.2.2.8.3.3-2: PAGING TYPE 1 for Cell 5 (step 5, Table 6.2.2.8.3.2-3)
Derivation path: 34.108 clause 9.1.1

PagingType1 ::= SEQUENCE {
bcch-ModificationInfo ::= SEQUENCE {
mib-ValueTag Set to (Current MIB
value tag + 1)
bcch-ModificationTime Not present
}
laterNonCriticalExtensions SEQUENCE {} Not present
}

- Cell Access Restriction
- Cell barred barred
- Intra-frequency cell re-selection indicator Not present
- Tbarred Not present
ETSI
6.2.3 Inter-RAT cell reselection

6.2.3.1 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS
Packet_Idle
(1)
ensure that {
priority inter-RAT(GERAN) frequency for TreselectionRAT }
then { UE reselects the cell which belongs to the higher priority inter-RAT(GERAN) frequency }
}
(2)
ensure that {
priority inter-RAT(GERAN) frequency for TreselectionRAT}
then { UE reselects the cell which belongs to the lower priority inter-RAT(GERAN) frequency }
}
5.2.4.2 and 5.2.4.5.
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.2]
ETSI
measurements.
measurements.
according to [10].
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
be performed if:
be performed if:
- No cell on serving frequency or on an equal priority E-UTRAN frequency or on a higher priority E-UTRAN
frequency or inter-RAT frequency than serving frequency fulfils the criteria 1; and
or if:
of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured From the evaluated cell.
ETSI
System Simulator:
UE:
None.
Preamble:
Table 6.2.3.1.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cells

Cell-specific RS EPRE dBm/15kHz -70 SrxlevCell 1 >0
T1
Srxlev* dB 36 SrxlevCell 1 > SrxlevCell 24 > 0
Cell-specific RS EPRE dBm/15kHz -60 SrxlevCell 1 >20
T2
Srxlev* dB 46
T3 Cell-specific RS EPRE dBm/15kHz -100 SrxlevCell 1 <20 [threshServingLow]
Table 6.2.3.1.3.2-2: Time instances of cell power level and parameter changes for GERAN cells
T1 RF Signal Level dBm -80 OFF SrxlevCell 24 > 4[threshX-High]
C1* dB 21 N/A
T2 RF Signal Level dBm OFF OFF
C1* dB N/A 21
T3 RF Signal Level dBm OFF -80 SrxlevCell 25 > 4[threshX-Low]
ETSI

U-S Message
information.
1 The SS changes Cell 1 according to the row - - - -
"T1" in table 6.2.3.1.3.2-1and Cell 24 level
according to the row "T1" in table 6.2.3.1.3.2-2.
24?
3 Void - - - -
4 Wait for [5 s]. - - - -
"T2" in table 6.2.3.1.3.2-1and Cell 24 level
according to the row "T2" in table 6.2.3.1.3.2-2
6 UE reselects Cell 1 and completes tracking - - - -
area update procedure.
Steps 1 to 22 of the generic test procedure
described in TS 36.508 Table 6.4.2.7A-2 are
7 Wait for [5 s]. - - - -
"T3" in table 6.2.3.1.3.2-1 and Cell 25 level
9 Void - - - -
25?
Table 6.2.3.1.3.3-1: SystemInformationBlockType3 cell 1 (preamble and all steps, Table 6.2.3.1.3.2-3)

threshServingLow 10 Actual value =20
dB
cellReselectionPriority 4 A middle value in
the range has
been selected.
}
}
ETSI
Table 6.2.3.1.3.3-2: SystemInformationBlockType7 cell 1 (preamble and all steps, Table 6.2.3.1.3.2-3)

t-ReselectionGERAN 7 INTEGER (0..7)
speedDependentScalingParameters SEQUENCE Not present
{}
carrierFreqsInfoList SEQUENCE (SIZE
(1..maxGNFG)) OF SEQUENCE {
carrierFreqsGERAN SEQUENCE [n] {
startingARFCN Same as cell 24
bandIndicator Same as cell 24
followingARFCNs CHOICE {
explicitListOfARFCNs Empty
}
}
commonInfo SEQUENCE {
cellReselectionPriority 5 Greater than
EUTRA Freq
ncc-Permitted ‘01000000’B
q-RxLevMin 2 The actual value
of Qrxlevmin in dBm
= (IE value * 2) −
115.
threshX-High 2 Actual value =4
dB
threshX-Low 2 Actual value =4
dB
}
carrierFreqsGERAN SEQUENCE [m] {
explicitListOfARFCNs Empty
}
}
cellReselectionPriority 3 Less than EUTRA
Freq
of Qrxlevmin in dBm
= (IE value * 2) −
115.
dB
dB
}
}
}
Table 6.2.3.1.3.3-3: System Information 2 Quater for Cell 24 in Preamble and all test steps
Derivation Path: 36.508 4.4.5-1

Serving Cell Priority Parameters Description::= {
GERAN_PRIORITY 5 Greater than EUTRA
freq
}
ETSI
Table 6.2.3.1.3.3-4: System Information 2 Quater for Cell 25 in Preamble and all test steps

GERAN_PRIORITY 3 Less than EUTRA
freq
}
Repeated E-UTRAN Neighbour Cells 1 Present
{
EARFCN Same as cell 1
E-UTRAN_QRXLEVMIN 21 (-98 dBm)
} ** 0
6.2.3.1a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS

Packet_Idle (Squal < ThreshServing, LowQ, Srxlev > ThreshX, LowP and Srxlev >
ThreshX, HighP)
(1)
ensure that {
when { UE detects the cell re-selection criteria(Srxlev > ThreshX, HighP) is met for the cell which
belong to the higher priority inter-RAT(GERAN) frequency for TreselectionRAT }
then { UE reselects the cell which belongs to the higher priority inter-RAT(GERAN) frequency }
}
(2)
ensure that {
when { UE detects the cell re-selection criteria(Squal < ThreshServing, LowQ and Srxlev > ThreshX, LowP)
is met for the cell which belong to the lower priority inter-RAT(GERAN) frequency for TreselectionRAT
}
then { UE reselects the cell which belongs to the lower priority inter-RAT(GERAN) frequency }
}
References: The conformance requirements covered in the current TC are specified in: TS36.304, clause 5.2.4.5.
[TS 36.304, clause 5.2.4.5]

and
ETSI

For cdma2000 RATs, Srxlev is equal to -FLOOR(-2 x 10 x log10 Ec/Io) in units of 0.5 dB, as defined in [18], with
Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, ThreshX, HighP and ThreshX, LowP are equal to -1 times the values signalled for the corresponding
System Simulator:
UE:
None
Preamble:
Tables 6.2.3.1a.3.2-1 & 6.2.3.1a.3.2-2 illustrates the downlink power levels and other changing parameters to be applied
applied at the points indicated in the Main behaviour description in Table 6.2.3.1a.3.2-3.
ETSI
Table 6.2.3.1a.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cells

T1 Cell-specific RS EPRE dBm/15kHz -70 SrxlevCell 1 >0
T2 Cell-specific RS EPRE dBm/15kHz -60
RSRQ dB -3.01 Make SqualCell 1 < threshServingLowQ
Noc dBm/15kHz off
Note: Srxlev and Squal is calculated in the UE.
Table 6.2.3.1a.3.2-2: Time instances of cell power level and parameter changes for GERAN cells

T1 RF Signal Level dBm -80 OFF SrxlevCell 24 > 4[threshX-High]
C1* dB 21 N/A
T2 RF Signal Level dBm OFF OFF
C1* dB N/A N/A
T3 RF Signal Level dBm OFF -80 SrxlevCell 25 > 4[threshX-Low]
Note: C1 is calculated in the UE.

U-S Message
information.
"T1" in table 6.2.3.1a.3.2-1and Cell 24 level
according to the row "T1" in table 6.2.3.1a.3.2-
2.
24?
3 The SS send CHANNEL RELEASE message <-- CHANNEL RELEASE - -
to UE.
"T2" in table 6.2.3.1a.3.2-1and Cell 24 level
2
5 UE performs generic test procedure in TS - - - -
36.508 subclause 6.4.2.7A-2 and camp on E-
UTRA Cell 1.
"T3" in table 6.2.3.1a.3.2-1 and Cell 25 level
2.
25?
9 The SS send CHANNEL RELEASE message <-- CHANNEL RELEASE - -
to UE.
ETSI
Table 6.2.3.1a.3.3-1: SystemInformationBlockType1 cell 1 (preamble and all steps, Table 6.2.3.1a.3.2-
3)

SEQUENCE {
q-QualMin-r9 -20
q-QualMinOffset-r9 1
}
nonCriticalExtension Not present
}
}
}
3)

threshServingLow 0 Actual value =0
dB
cellReselectionPriority 4 A middle value in
the range has
been selected.
}
}
}
ETSI
3)

t-ReselectionGERAN-SF Not present
{}
carrierFreqsGERAN SEQUENCE [n] {
equallySpacedARFCNs SEQUENCE {
arfcn-Spacing Same as cell 24
numberOfFollowingARFCNs Same as cell 24
}
}
}
EUTRA Freq
of Qrxlevmin in dBm
= (IE value * 2) −
115.
dB
dB
}
carrierFreqsGERAN SEQUENCE [m] {
}
}
}
cellReselectionPriority 2 Less than EUTRA
Freq
of Qrxlevmin in dBm
= (IE value * 2) −
115.
dB
dB
}
}
}
ETSI
Table 6.2.3.1a.3.3-4: System Information 2 Quater for Cell 24 (Preamble and all test steps, , Table
6.2.3.1a.3.2-3)

GERAN_PRIORITY 5 Greater than EUTRA
freq
}
Table 6.2.3.1a.3.3-5: System Information 2 Quater for Cell 25 (Preamble and all test steps, , Table
6.2.3.1a.3.2-3)

2 Less than EUTRA freq
1 Present
Same as cell 1
21 (-98 dBm)
} ** 0
6.2.3.2 Void
6.2.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE
(1)
with { UE in UTRA_Idle state }
ensure that {
priority inter-RAT E-UTRA cell}
then { UE reselects the cell which belongs to the lower priority inter-RAT E-UTRA cell }
}
(2)
ensure that {
then { UE reselects the cell which belongs to the higher priority inter-RAT E-UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, clause 5.2.6.1.2a and
5.2.6.1.4a.
[TS 25.304, clause 5.2.6.1.2a]
If the UE has received absolute priority information for inter-RAT layers, the UE shall follow these rules:
- The UE shall perform measurements of inter-RAT layers with a priority higher than the priority of the current
serving cell.
NOTE: The rate of these measurements may vary depending on whether Srxlev and Squal of the serving cell are
above or below Sprioritysearch1 and Sprioritysearch2. This is specified in [10].
- For inter-RAT layers with a priority lower than the priority of the current serving cell:
ETSI
- If SrxlevServingCell > Sprioritysearch1 and SqualServingCell > Sprioritysearch2 the UE may choose not to perform
measurements of inter-RAT layers of lower priority.
- If SrxlevServingCell <= Sprioritysearch1 or SqualServingCell <= Sprioritysearch2 the UE shall perform measurements of
inter-RAT layers of lower priority.
[TS 25.304, clause 5.2.6.1.4a]
Absolute priorities of different absolute priority layers may be provided to the UE. The following cell reselection
criteria are used for inter-frequency cells if absolute priority information for inter-frequency is available to the UE, and
inter-RAT cells if absolute priority information for inter-RAT is available to the UE.
...
The following definitions apply:
- Criterion 1: the SrxlevnonServingCell,x of a cell on an evaluated higher absolute priority layer is greater than
Threshx,high during a time interval Treselection;
- Criterion 3: SrxlevServingCell < Threshserving,low or SqualServingCell < 0 and the SrxlevnonServingCell,x of a cell on an
evaluated lower absolute priority layer is greater than Threshx,low during a time interval Treselection;
Cell reselection to a cell on a higher absolute priority layer than the camped frequency shall be performed if criterion 1
is fulfilled.
...
Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall be performed if criterion 3 is
fulfilled.
If more than one cell meets the above criteria, the UE shall reselect the cell with the highest SrxlevnonServingCell,x among
the cells meeting the criteria on the highest absolute priority layer.
The UE shall not perform cell reselection to cells for which the cell selection criterion S is not fulfilled.
The UE shall not perform cell reselection until more than 1 second has elapsed since the UE camped on the current
serving cell.
System Simulator:
- Cell 1 and Cell 5
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 3 or 7) on Cell 5 (serving cell) according to [5].
Tables 6.2.3.3.3.2-1 & Table 6.2.3.3.3.2-2 illustrate the downlink power levels and other changing parameters to be
applied for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and
"T3" are applied at the points indicated in the Main behaviour description in Table 6.2.3.3.3.2-3.
ETSI

Srxlev* dB 21 Srxlev = Cell-specific RS EPRE -
T1
qRxLevMinEUTRA
S nonServingCell, Cell1 > Thresh Cell1,low
T3
qRxLevMinEUTRA
S nonServingCell, Cell1 > Thresh Cell1,high

Srxlev* dB -11 SrxlevServingCell < Thresh Serving,low
Srxlev* dB 19
Srxlev* dB 9

U-S Message
1 The SS changes Cell 1 and Cell 5 levels - - - -
and table 6.2.3.3.3.2-2.
Cell 1?
2A Wait for 6 s for UE to receive system - - - -
information.
and table 6.2.3.3.3.2-2.
4 Generic test procedure in TS 36.508 subclause - - - -
6.4.2.8 indicate that the UE is camped on
UTRAN Cell 5.
NOTE: The UE performs a RAU procedure and
5 The SS changes the E-UTRA cell priority - - - -
broadcast in system information.
6 Notify UE change of System Information. <-- PAGING TYPE 1 - -
and table 6.2.3.3.3.2-2.
Cell 1?
ETSI
Table 6.2.3.3.3.3-1: System Information Block type 19 for Cell 5 (preamble, Table 6.2.3.3.3.2-3)

utra-PriorityInfoList ::= SEQUENCE {
utra-ServingCell ::= SEQUENCE {
priority 4
s-PrioritySearch1 8 (16 dB)
s-PrioritySearch2 Not present
}
utran-FDD-FrequencyList Not present UTRA-
FDD
utran-TDD-FrequencyList Not present UTRA-
TDD
}
gsm-PriorityInfoList Not present
as used for Cell 1
measurementBandwidth [n] Not present
priority [n] 3
qRxLevMinEUTRA [n] -60 (-120 dBm)
threshXhigh [n] 16 (32 dB)
threshXlow [n] 10 (20 dB)
eutra-blackListedCellList [n] Not present
eutraDetection [n] TRUE
}
}
Note: GERAN cell priority is not allocated, hence it will be considered as the less than all allowed values of 0 to
7.
ETSI
Table 6.2.3.3.3.3-2: System Information Block type 19 for Cell 5 (step 5, Table 6.2.3.3.3.2-3)

priority 4
s-PrioritySearch2 Not present
}
FDD
TDD
}
as used for Cell 1
priority [n] 5
}
}
7.
UTRA-FDD UTRA FDD cell environment
UTRA-TDD UTRA TDD cell environment
Table 6.2.3.3.3.3-3: PAGING TYPE 1 (step 6, Table 6.2.3.3.3.2-3)

value tag + 1)
}
}
Table 6.2.3.3.3.3-4:SystemInformationBlockType3 for Cell 1(preamble, Table 6.2.3.3.3.2-3)

}
}
ETSI
Table 6.2.3.3.3.3-5:SystemInformationBlockType3 for Cell 1(step 5, Table 6.2.3.3.3.2-3)

}
}
Table 6.2.3.3.3.3-6:SystemInformationBlockType6 for Cell 1(preamble, Table 6.2.3.3.3.2-3)

CarrierFreqListUTRA-FDD SEQUENCE (SIZE UTRA-FDD
(1..maxUTRA-FDD-Carrier)) OF SEQUENCE {
carrierFreq[n] Same downlink
UARFCN as used
for cell 5
}
CarrierFreqListUTRA-TDD SEQUENCE (SIZE UTRA-TDD
(1..maxUTRA-TDD-Carrier)) OF SEQUENCE {
UARFCN as used
for cell 5
}
}
Table 6.2.3.3.3.3-7:SystemInformationBlockType1 for Cell 1(step 5, Table 6.2.3.3.3.2-3)

systemInfoValueTag The value is
increased
}
6.2.3.3a Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE

(QqualminEUTRA, SqualServingCell < Threshserving,low2, SqualnonServingCell,x >
Threshx, low2 and SqualnonServingCell,x > Threshx, high2)
(1)
ensure that {
}
(2)
ensure that {
ETSI
}
5.2.6.1.4a.
[TS 25.304, clause 5.2.6.1.2a]
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
...
The following definitions apply for the layers for which Threshx,high2 or Threshx,low2 are not provided:
- Criterion 3: (SrxlevServingCell < Threshserving,low or SqualServingCell <= 0) and the SrxlevnonServingCell,x of a cell on an
The following definitions apply for the layers for which both Threshx,high2 and Threshx,low2 are provided:
- Criterion 4: the SqualnonServingCell,x of a cell on an evaluated higher absolute priority layer is greater than
Threshx,high2 during a time interval Treselection;
- Criterion 5: (SqualServingCell < Threshserving,low2 or SrxlevServingCell <= 0) and the SqualnonServingCell,x of a cell on an
evaluated lower absolute priority layer is greater than Threshx,low2 during a time interval Treselection;
or 4 is fulfilled.
...
Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall be performed if criterion 3
or 5 is fulfilled.
ETSI
serving cell.
...
Cell reselection from UTRAN to E-UTRAN, for which Squal (RSRQ) based cell reselection parameters are broadcast
in system information, shall be performed based on the Squal criteria (criterion 4 or 5) if the UE supports Squal based
cell reselection from E-UTRAN to UTRAN. Otherwise, cell reselection to E-UTRAN shall be performed based on
Srxlev criteria.
System Simulator:
- Cell 1 and Cell 5
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 3 or 7) on Cell 5 (serving cell) according to [5].
Tables 6.2.3.3a.3.2-1 & Table 6.2.3.3a.3.2-2 illustrate the downlink power levels and other changing parameters to be
"T3" are applied at the points indicated in the Main behaviour description in Table 6.2.3.3a.3.2-3.
Table 6.2.3.3a.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell

Cell-specific RS EPRE dBm/15kHz -85 Squal nonServingCell, Cell1 > Thresh
RSRQ dB -3 Cell1,low2 (4 dB)
T1
Qqualmin dB -20
Noc dBm/15kHz Off
T2
RSRQ dB -3
T3
RSRQ dB -3 S nonServingCell, Cell1 > Thresh Cell1,high2
Table 6.2.3.3a.3.2-2: Time instances of cell power level and parameter changes for UTRA cell

CPICH_Ec dBm/3.84 MHz -80 SqualServingCell < ThreshServing,low2 (25
P-CCPCH dBm/1.28 MHz -82 dB)
CPICH_Ec/No dB -2.89
T1
Qrxlevmin dBm -99
Qqualmin dB -20
Ioc dBm/3.84MHz off
ETSI

U-S Message
1 and table 6.2.3.3a.3.2-2.
Cell 1?
3 Void - - - -
1 and table 6.2.3.3a.3.2-2.
5 The UE selects UTRAN cell 5 and performs the - - - -
generic test procedure in TS 36.508 subclause
6.4.2.8.
6 The SS changes the E-UTRA cell priority - - - -
7 Notify UE change of System Information. <-- PAGING TYPE 1 - -
1 and table 6.2.3.3a.3.2-2.
Cell 1?
ETSI
Table 6.2.3.3a.3.3-1: System Information Block type 19 for Cell 5 (preamble, Table 6.2.3.3a.3.2-3)

priority 4
}
}
as used for Cell 1
priority [n] 3
}
v920NonCriticalExtensions SEQUENCE {
sysInfoType19-v920ext SEQUENCE {
utra-PriorityInfoList-v920ext SEQUENCE {
threshServingLow2 25 (25dB)
}
eutra-FrequencyAndPriorityInfoList-v920ext (SIZE
(1..maxNumEUTRAFreqs)) OF SEQUENCE {
threshXhigh2[n] 30 (30dB)
threshXlow2[n] 4 (4dB)
}
}
}
}
7.
ETSI
Table 6.2.3.3a.3.3-2: System Information Block type 19 for Cell 5 (step 6, Table 6.2.3.3a.3.2-3)

priority 4
}
}
as used for Cell 1
priority [n] 5
}
}
}
}
}
}
7.
Table 6.2.3.3a.3.3-3: PAGING TYPE 1 (step 7, Table 6.2.3.3a.3.2-3)

value tag + 1)
}
}
Table 6.2.3.3a.3.3-4:SystemInformationBlockType3 for Cell 1(preamble, Table 6.2.3.3a.3.2-3)

}
q-QualMin-r9 -20 dB
}
ETSI
Table 6.2.3.3a.3.3-5:SystemInformationBlockType3 for Cell 1(step 6, Table 6.2.3.3a.3.2-3)

}
q-QualMin-r9 -20 dB
}
}
Table 6.2.3.3a.3.3-6:SystemInformationBlockType6 for Cell 1(preamble, Table 6.2.3.3a.3.2-3)

UARFCN as used
for cell 5
q-QualMin[n] -20 (-20 dB)
threshX-HighQ-r9 31 (31dB)
}
}
UARFCN as used
for cell 5
threshX-HighQ-r9 31 (31dB)
}
}
}
6.2.3.4 Inter-RAT cell reselection / From UTRA_CELL_PCH state to E-UTRA

RRC_IDLE
(1)
with { UE in UTRA_CELL_PCH state }
ensure that {
}
ETSI
5.2.6.1.4a; TS 25.331, clause 8.3.9.2, 8.3.9.3, Annex E.
[TS 25.304, clause 5.2.6.1.2a]
The measurement rules below apply in Idle, URA_PCH, CELL_PCH states.
...
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
...
is fulfilled.
...
serving cell.
For UE in RRC connected mode states CELL_PCH or URA_PCH the interval Treselections,PCH applies, if provided in
SIB4 (see [4]), while for UE in RRC connected mode state CELL_FACH the interval Treselections,FACH applies, if
provided in SIB4 (see [4]).
In all the above criteria the values of Treselections, Treselections,PCH or Treselections,FACH apply for Treselection and are
scaled according to the UE mobility state and target RAT, as specified in 5.2.6.1.1a.
[TS 25.331, 8.3.9.2]
This procedure is applicable in states CELL_FACH, CELL_PCH or URA_PCH. Inter-RAT cell reselection to E-
UTRAN in CELL_FACH state is not supported in this version of the specification.
ETSI
When the UE based on received system information makes a cell reselection to a radio access technology other than
UTRAN, e.g. GSM/GPRS or E-UTRA, according to the criteria specified in [4], the UE shall:
...
[TS 25.331, 8.3.9.3]
When the UE has succeeded in reselecting a cell in the target radio access technology, the UE shall:
1> release all UTRAN specific resources.
UTRAN should:
1> release all UE dedicated resources upon indication that the UE has completed a connection establishment to the
other radio access technology.
[TS 25.331, Annex E]
This annex contains the definitions of the bits in EUTRA Feature Group Indicators.
In this release of the specification the UE shall include the optional EUTRA Feature Group Indicators IE in the UE
multi-mode/multi RAT capability IE of the RRC message. For a specific indicator, if all functionalities for a feature
group listed in Table E.1 have been implemented and tested, the UE shall set the indicator as "true" (as one), else (i.e. if
any one of the functionalities in a feature group listed in Table E.1 have not been implemented or tested), the UE shall
set the indicator as zero.
The UE shall set all indicators, which do not have a definition in the table E.1, as "false" (as zero).
If the optional EUTRA Feature Group Indicators IE is not included by a UE supporting a future release of the
specification, the network may assume the UE supports all features in the feature groups listed in table E.1 and
deployed in the network.
Table E.1: Definitions of feature group indicators
Index of Definition Notes

indicator (description of the supported functionality, if indicator set to ‘true’)
(bit
number)
1 (leftmost - UTRA CELL_PCH to EUTRA RRC_IDLE cell reselection
bit) - UTRA URA_PCH to EUTRA RRC_IDLE cell reselection
2 EUTRAN measurements and reporting in connected mode
3 Undefined
4 Undefined
Clarification for mobility to EUTRAN
For mobility to E-UTRAN, it is assumed that we have 6 main "functions":
A. Support of measurements and cell reselection procedure in idle mode
B. Support of measurements and cell reselection procedure in CELL/URA_PCH
C. Support of RRC release with redirection procedure
D. Support of RRC reject with redirection procedure
E. Support of EUTRAN measurements and reporting in connected mode
F. Support of handover procedure in connected mode
Of the above, all UEs that indicate support of E-UTRA in UE capability signalling "Support of E-UTRA FDD" or
"Support of E-UTRA TDD" support A), C) and D) EUTRA bands.
For B) above, UEs indicate support by the Group 1 indicator bit (if Group 1 is set to "true", it is supported for all
EUTRA bands the UE supports).
ETSI
For E) above, UEs indicate support by the Group 2 indicator bit (if Group 2 is set to "true", it is supported for all
EUTRA bands the UE supports). The compressed mode capability for supported E-UTRA frequency bands ("Need for
compressed mode") in "Measurement capability extension" is ignored by the network when Group 2 is set to "false".
For F) above, UEs indicate support by the separate UE capability signalling "Support of Inter-RAT PS Handover to E-
UTRA FDD/TDD" defined in TS 25.306 (if this bit is set to "true", PS handover is supported for all EUTRA bands the
UE supports). This bit can only be set to "true" if the UE has set the Group 2 indicator bit to "true".
System Simulator:
- Cell 1 suitable neighbour E-UTRA cell
- Cell 5 UTRA serving cell
UE:
None.
Preamble:
- The UE is in state CELL_PCH (state 6-12) on Cell 5 according to [5].
- The cell power level and parameter for Cell 5 is as follow:

Qrxlevmin (FDD) dBm -79 Default value
Qrxlevmin(TDD) dBm -81 Default value
Table 6.2.3.4.3.2-1: Time instance of cell power level and parameter changes for E-UTRA cell and
UTRA cell

qRxLevMinEUTRA
T1 S nonServingCell, Cell1 > Thresh Cell1,high
Srxlev* dB 9
ETSI

U-S Message
(Note 1)
Cell 1? (Note 2)
Note 1: SS should not send any RRC message after UE has successfully proceed to CELL_PCH state in preamble.
Note 2: UE shall search higher priority layer (i.e. E-UTRA carrier frequency of Cell 1) at least every (60 * Nlayers)
6.2.3.4.3.2-2)

priority 4
}
eutra-FrequencyAndPriorityInfoList ::= SEQUENCE 1 entry
earfcn [1] Same downlink EARFCN
as used for Cell 1
priority [1] 5
qRxLevMinEUTRA [1] -53 (-106 dBm)
threshXhigh [1] 10 (20 dB)
threshXlow [1] 5 (10 dB)
}
}
Table 6.2.3.4.3.3-2: Void
Table 6.2.3.4.3.3-3:SystemInformationBlockType3 for Cell 1 (preamble and all steps, Table 6.2.3.4.3.2-
2)

CellReselectionPriority 5
}
}
ETSI
Table 6.2.3.4.3.3-4:SystemInformationBlockType6 for Cell 1 (preamble and all steps, Table 6.2.3.4.3.2-
2)

carrierFreq[n] Same as Cell 5
}
}
}
6.2.3.4a Inter-RAT cell reselection / From UTRA_CELL_PCH state to E-UTRA

RRC_IDLE based on RSRQ+RSRP evaluation
(1)
with { UE in UTRA_CELL_PCH state }
ensure that {
when { UE detects the cell re-selection criteria ( RSRQ => Squal >0 , RSRP => Srxlev >0 )are met
for the cell which belongs to the higher priority inter-RAT E-UTRA cell}
}
5.2.6.1.4a; TS 25.331, clause 8.3.9.2, 8.3.9.3, Annex E.
[TS 25.304, clause 5.2.6.1.2a]
The measurement rules below apply in Idle, URA_PCH, CELL_PCH states.
...
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
ETSI
...
is fulfilled.
...
[TS 25.304, clause 5.2.6.1.4a]
...
- Criterion 3: (SrxlevServingCell < Threshserving,low or SqualServingCell <= 0) and the SrxlevnonServingCell,x of a cell on an
- Criterion 5: (SqualServingCell < Threshserving,low2 or SrxlevServingCell <= 0) and the SqualnonServingCell,x of a cell on an
evaluated lower absolute priority layer is greater than Threshx,low2 during a time interval Treselection;
or 4 is fulfilled.
...
Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall be performed if criterion 3
or 5 is fulfilled.
serving cell.
serving cell.
ETSI
For UE in RRC connected mode states CELL_PCH or URA_PCH the interval Treselections,PCH applies, if provided in
SIB4 (see [4]), while for UE in RRC connected mode state CELL_FACH the interval Treselections,FACH applies, if
provided in SIB4 (see [4]).
In all the above criteria the values of Treselections, Treselections,PCH or Treselections,FACH apply for Treselection and are
scaled according to the UE mobility state and target RAT, as specified in 5.2.6.1.1a.
...
Cell reselection from UTRAN to E-UTRAN, for which Squal (RSRQ) based cell reselection parameters are broadcast
in system information, shall be performed based on the Squal criteria (criterion 4 or 5) if the UE supports Squal based
cell reselection from E-UTRAN to UTRAN. Otherwise, cell reselection to E-UTRAN shall be performed based on
Srxlev criteria.
[TS 25.331, 8.3.9.2]
This procedure is applicable in states CELL_FACH, CELL_PCH or URA_PCH. Inter-RAT cell reselection to E-
UTRAN in CELL_FACH state is not supported in this version of the specification.
When the UE based on received system information makes a cell reselection to a radio access technology other than
UTRAN, e.g. GSM/GPRS or E-UTRA, according to the criteria specified in [4], the UE shall:
...
[TS 25.331, 8.3.9.3]
When the UE has succeeded in reselecting a cell in the target radio access technology, the UE shall:
1> release all UTRAN specific resources.
UTRAN should:
1> release all UE dedicated resources upon indication that the UE has completed a connection establishment to the
other radio access technology.

(bit
number)
3 Undefined
4 Undefined
ETSI
System Simulator:
UE:
None.
Preamble:
- UE is in state Registered, Idle Mode ( state 3 or 7) on Cell 5 (serving cell) according to [5].
- The cell power level and parameter for Cell 5 is as follow:

applied for the cells applied at the points indicated in the Main behaviour description in Table 6.2.3.4a.3.2-3.
ETSI

T1 Cell-specific RS dBm/15 -75 Steps 1-3, SqualnonServingCell,1 < Threshx,high2(26 dB)
EPRE kHz Steps 4-7, SqualnonServingCell,1 >Threshx,high2(4 dB)
RSRQ dB -3
Qrxlevmin dBm -84
Qqualmin dB -20
dBm/15
Noc off
kHz

T1 CPICH_Ec/Io dB -2.89
QqualminFDD dB -20
Ioc dBm/3.84MHz off

U-S Message
according to the row "T1" in table 6.2.3.4a.3.2-1
and 6.2.3.4a.3.2-2.
2 The UE is brought to state CELL_PCH (state 6- - - -
12) on Cell 5 according to [5] with modified SIB-
19 info so that Cell 1 Squal cell 1 <
threshXhigh2 according to table 6.2.3.4a.3.2-1
indicate that the UE is NOT camped on E-
UTRAN Cell 1? (Note 2)
4 The SS changes the SIB-19 info so that for Cell - - - -
1 Squalcell1> threshXhigh2 according to table
6.2.3.4a.3.2-2.
5 Notify UE change of System Information. <- - PAGING TYPE 1
6 Wait for 6 s for UE to receive system - - -
information.
Cell 1? (Note 2)
Note 1: Void
Note 2: UE shall search higher priority layer (i.e. E-UTRA carrier frequency of Cell 1) at least every (60 * Nlayers)
ETSI
Table 6.2.3.4a.3.3-1: System Information Block type 19 for Cell 5 ( at preamble, Table 6.2.3.4a.3.2-3)

Priority 3
}
FDD
TDD
}
as used for Cell 1
priority [n] 5
qRxlevMinEUTRA [n] -84 (-168 dBm)
qQualminEUTRA [n] -20
}
}
qQualMinEUTRA[n] -20 (-20dB)
}
}
nonCriticalExtensions SEQUENCE {} Not present
}
}
7.
ETSI
Table 6.2.3.4a.3.3-2: System Information Block type 19 for Cell 5 ( at step 4, Table 6.2.3.4a.3.2-3)

priority 3
}
FDD
TDD
}
as used for Cell 1
priority [n] 5
qRxlevMinEUTRA [n] -84 (164 dBm)
qQualminEUTRA [n] -20
}
}
}
}
}
}
7.
ETSI
Table 6.2.3.4a.3.3-3: PAGING TYPE 1 for Cell 5 (step 5, Table 6.2.2.4a.3.2-3)

value tag + 1)
}
}
Table 6.2.3.4a.3.3-4:SystemInformationBlockType3 for Cell 1 (preamble and all steps, Table

6.2.3.4a.3.2-3)

}
q-QualMin-r9 -20 dB
}
}
Table 6.2.3.4a.3.3-5:SystemInformationBlockType6 for Cell 1 (preamble and all steps, Table

6.2.3.4a.3.2-3)

}
}
}
6.2.3.5 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle

(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the neighbour cell which belongs to
the higher priority UTRAN frequency }
ETSI
then { UE reselects the UTRA cell }

}
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.5.
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
be performed if:
For GERAN, UTRAN, and E-UTRAN, SnonServingCell,x is the Srxlev-value of an evaluated cell. ...
System Simulator:
- 2 cells, one E-UTRA and one UTRA cell :
- Cell 1 is a E-UTRA cell
- Cell 5 is a UTRA cell
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configuration marked "T1" is applied at the points indicated in
the Main behaviour description in Table 6.2.3.5.3.2-2.

T1 CPICH_Ec dBm/3.84 MHz - -65 S nonServingCell, Cell5 > Thresh Cell 5,high
ETSI

U-S Message
information.
5?
NOTE: The UE performs an RAU procedure
Table 6.2.3.5.3.3-1: Void
Table 6.2.3.5.3.3-2: Void
6.2.3.5.3.2-2)

carrierFreqListUTRA-FDD SEQUENCE (SIZE UTRA-
(1..maxUTRA-FDD-Carrier)) OF SEQUENCE { FDD
carrierFreq[n] Same downlink UARFCN
as used for cell 5
cellReselectionPriority[n] 5 Higher priority
than E-UTRA
}
carrierFreqListUTRA-TDD SEQUENCE (SIZE UTRA-
(1..maxUTRA-TDD-Carrier)) OF SEQUENCE { TDD
as used for cell 5
than E-UTRA
}
}
6.2.3.5.3.2-2)

priority 5
}
}
ETSI
6.2.3.5a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle (Squal >
ThreshX, HighQ, Squal < ThreshServing, LowQ, Squal > ThreshX, LowQ and
SnonIntraSearchQ)
(1)
with { UE in E-UTRA_Idle state }
ensure that {
priority inter-RAT UTRA cell}
then { UE reselects the cell which belongs to the lower priority inter-RAT UTRA cell }
}
(2)
with { UE in E-UTRA_Idle state }
ensure that {
priority inter-RAT UTRA cell}
then { UE reselects the cell which belongs to the higher priority inter-RAT UTRA cell }
}
(3)
ensure that {
when { threshX-HighQ-r9 is non-zero in system information }
then { UE perform measurement and reselects the cell which belong to the high priority UTRA
cell upon Squal > threshX-HighQ-r9 }
}
5.2.4.5.
[TS 36.304, clause 5.2.4.2]
priority.
- Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells
of equal or lower priority according to [10].
ETSI
[TS 36.304, clause 5.2.4.5]

and
...

...
Cell reselection to another RAT, for which Squal based cell reselection parameters are broadcast in system information,
shall be performed based on the Squal criteria if the UE supports Squal (RSRQ) based cell reselection to E-UTRAN
from all the other RATs provided by system information which UE supports. Otherwise, cell reselection to another
RAT shall be performed based on Srxlev criteria.
System Simulator:
UE:
None.
Preamble:
ETSI
"T3" are applied at the points indicated in the Main behaviour description in Table 6.2.3.5a.3.2-3.

Cell-specific RS EPRE dBm/15kHz -85 Squal ServingCell, Cell1 < ThreshServing,
RSRQ dB -3 LowQ
T1
Qqualmin dB -20
Noc dBm/15kHz off
T2
RSRQ dB -3
T3
RSRQ dB -3

CPICH_Ec dBm/3.84 MHz -60 Note 1
T1
Ioc dBm/3.84MHz Off
CPICH_Ec/No dB off
Note 1: Since no interference is occurred, SqualnonServingCell, Cell 5 > ThreshCell5, LowQ is satisfied,
Note 2: Since no interference is occurred, SqualServingCell, Cell 5 < 0 is satisfied.
Note 3: Since no interference is occurred, Squal nonServingCell, Cell5 > Thresh Cell5,highQ is satisfied,
ETSI

U-S Message
information.
1 and table 6.2.3.5a.3.2-2.
procedure in TS 36.508 Table 6.4.2.8 indicate
that the UE is camped on UTRAN Cell 5?
NOTE: The UE performs a RAU procedure and
1 and table 6.2.3.5a.3.2-2.
5 The UE selects E-UTRAN Cell 1 and performs - - - -
the generic test procedure in TS 36.508 Table
6.4.2.7A-1.
6 The SS changes the UTRA cell priority - - - -
7 Notify UE change of System Information. <-- Paging - -
information.
1 and table 6.2.3.5a.3.2-2.
10- Check: Does the test result of steps 1 to 8 - - 2, 3 -
17 generic test procedure in TS 36.508 Table
UTRAN Cell 5?
Table 6.2.3.5a.3.3-1:SystemInformationBlockType3 for Cell 1 (preamble, Table 6.2.3.5a.3.2-3)

q-QualMin-r9 -20 dB
}
}
ETSI
Table 6.2.3.5a.3.3-2:SystemInformationBlockType6 for Cell 1 (preamble, Table 6.2.3.5a.3.2-3)

UARFCN as used
for Cell 5
threshX-High[n] 13 (26 dB)
threshX-HighQ-r9 24 (24 dB)
threshX-LowQ-r9 9 (9 dB)
}
}
UARFCN as used
for Cell 5
}
}
ETSI
Table 6.2.3.5a.3.3-3: System Information Block type 19 for Cell 5 (preamble, Table 6.2.3.5a.3.2-3)

priority 3
}
utran-FDD-FrequencyList Not present UTRA-FDD
utran-TDD-FrequencyList Not present UTRA-TDD
}
as used for Cell 1
priority [n] 4
qRxlevMinEUTRA [n] -53 (-106 dBm)
eutraDetection [n] [TRUE]
}
}
}
}
}
}
7.
ETSI
Table 6.2.3.5a.3.3-4: Void
Table 6.2.3.5a.3.3-5:SystemInformationBlockType6 for Cell 1 (step 6, Table 6.2.3.5a.3.2-3)

UARFCN as used
for Cell 5
threshX-High[n] 10 (20 dB)
threshX-HighQ-r9 9 (9 dB)
threshX-LowQ-r9 24 (24 dB)
}
}
UARFCN as used
for Cell 5
}
}
ETSI
Table 6.2.3.5a.3.3-6: System Information Block type 19 for Cell 5 (step 6, Table 6.2.3.5a.3.2-3)

priority 5
}
utran-FDD-FrequencyList Not present UTRA-FDD
utran-TDD-FrequencyList Not present UTRA-TDD
}
as used for Cell 1
priority [n] 4
qRxlevMinEUTRA [n] -53 (106 dBm)
eutraDetection [n] [TRUE]
}
}
}
}
}
}
7.
Table 6.2.3.5a.3.3-7: Paging (step 7, Table 6.2.3.5a.3.2-3)

etws-PrimaryNotificationIndication Not present
}
ETSI
6.2.3.6 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle

according to RAT priority provided by dedicated signalling
(1)
with { UE in E-UTRA RRC_IDLE state having received an RRCConnectionRelease message including a
cellReselectionPriority }
ensure that {
priority RAT }
then { UE reselects the cell which belongs to the higher priority RAT }
}
(2)
ensure that {
priority RAT }
then { UE reselects the cell which belongs to the lower priority RAT }
}
(3)
ensure that {
when { T320 expires }
then { UE reselects a cell by applying the cellReselectionPriority broadcast in the system
information }
}
(4)
with { UE in E-UTRA RRC_IDLE state, and reselection priorities have been provided in dedicated
signalling }
ensure that {
when { T320 has not expired }
then { The UE shall ignore all the priorities provided in system information, and not perform
cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies for which the UE
doesn’t have a priority provided }
}
5.2.4.5 and TS 36.331, clause 5.3.8.3 and 5.3.8.4.
[TS 36.304, clause 5.2.4.1]
ETSI
information.
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
be performed if:
be performed if:
- No cell on a higher priority E-UTRAN frequency or inter-RAT frequency than serving frequency fulfills the
criteria 1; and
...
is higher than 0, as defined in [8]. For cdma2000 RATs, SnonServingCell,x is equal to -FLOOR(-2 x 10 x log10 Ec/Io) in
units of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this sub-clause 60 ms from the moment the RRCConnectionRelease
message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease
message has been successfully acknowledged, whichever is earlier;
1> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
ETSI
2> store the cell reselection priority information provided by the idleModeMobilityControlInfo;
2> if the t320 is included:
3> start timer T320, with the timer value set according to the value of t320;
1> else:
2> apply the cell reselection priority information broadcast in the system information;
1> if the releaseCause received in the RRCConnectionRelease message indicates 'loadBalancingTAURequired':
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'load
balancing TAU required';
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other';
[TS 36.331, clause 5.3.8.4]
The UE shall:
1> if T320 expires:
2> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or
inherited from another RAT;
System Simulator:
- Cell 1(E-UTRA) and Cell 5(UTRA).
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while
columns marked "T1", "T2", "T3", "T4" and "T5" are to be applied subsequently. The exact instants on which these
values are applied are described in the texts in this clause.
ETSI

Cell-specific RS dBm/15k The power level values are
-70 -
EPRE Hz assigned to satisfy SrxlevCell 1 > 0
dBm/3.8 and SrxlevCell 5 < 0.
T0 CPICH Ec - -90
4 MHz
PCCPCH dBm/1.2
-92
RSCP 8MHz
-90 -
EPRE Hz assigned to satisfy Threshx,high <
dBm/3.8 Srxlevcell 5.
T1 CPICH Ec - -65
4 MHz
PCCPCH dBm/1.2
-65
RSCP 8MHz
Cell-specific RS dBm/15k The power level values are such
-70 -
EPRE Hz that camping on Cell 1 is
dBm/3.8 guaranteed.
T2 CPICH Ec - -90
4 MHz
PCCPCH dBm/1.2
-92
RSCP 8MHz
-115 -
EPRE Hz assigned to satisfy Srxlevcell 1 <
dBm/3.8 Threshserving, low and Threshx,low <
T3 CPICH Ec - -65 Srxlevcell 5.
4 MHz
PCCPCH dBm/1.2
-65
RSCP 8MHz
-70 -
dBm/3.8 guaranteed.
T4 CPICH Ec - -90
4 MHz
PCCPCH dBm/1.2
-92
RSCP 8MHz
-70 -
EPRE Hz assigned to satisfy Srxlevcell 1 >
dBm/3.8 Threshserving, low and Threshx,high <
T5 CPICH Ec - -65 Srxlevcell 5.
4 MHz
PCCPCH dBm/1.2
-65
RSCP 8MHz
ETSI

U-S Message
1 The SS transmits an RRCConnectionRelease <-- RRCConnectionRelease - -
message with an idleModeMobilityControlInfo
including a cellReselectionPriority on Cell 1.
2 The SS changes Cell 5 level according to row - - - -
"T1" in table 6.2.3.6.3.2-1.
3 Check: Does the UE transmit an RRC --> RRC CONNECTION REQUEST 4 F
CONNECTION REQUEST message within the
next 30s on Cell 5?
4 The SS transmits a Paging message including <-- Paging - -
matched identity on Cell 1.
5 UE transmit an RRCConnectionRequest --> RRCConnectionRequest - -
message on Cell 1.
message on Cell 1.
7 The UE transmits an --> RRCConnectionSetupComplete - -
RRCConnectionSetupComplete on Cell 1.
message with an idleModeMobilityControlInfo
including a cellReselectionPriority on Cell 1.
5?
10 The SS changes Cell 1 and Cell 5 parameters - - - -
subclause 6.4.2.7 A-1 is performed on Cell 1.
5?
subclause 6.4.2.7 A-1 is performed on Cell 1.
17 Wait for 5 minutes from step 15 to ensure that - - - -
T320 expires.
5?
ETSI
Table 6.2.3.6.3.3-1: Void
6.2.3.6.3.2-2)

threshServingLow 1
}
}
6.2.3.6.3.2-2)

carrierFreqListUTRA-FDD SEQUENCE (SIZE UTRA-FDD
as used for Cell 5
p-MaxUTRA[n] 0
}
carrierFreqListUTRA-TDD SEQUENCE (SIZE UTRA-TDD
as used for Cell 5
p-MaxUTRA[n] 0
}
}
ETSI
Table 6.2.3.6.3.3-4: RRCConnectionRelease (Step 1, Table 6.2.3.6.3.2-2)
Derivation path: 36.508 table 4.6.1-15

c1 CHOICE {
IdleModeMobilityControlInfo ::= SEQUENCE {
freqPriorityListEUTRA SEQUENCE (SIZE (1.. 1 entry
maxFreq)) OF SEQUENCE {
carrierFreq[1] Same downlink
EARFCN as used for
Cell1
}
freqPriorityListGERAN Not present
freqPriorityListUTRA-FDD Not present UTRA-TDD
freqPriorityListUTRA-TDD Not present UTRA-FDD
bandClassPriorityListHRPD Not present
bandClassPriorityList1XRTT Not present
t320 Not present
}
}
}
}
}
ETSI
Table 6.2.3.6.3.3-5: RRCConnectionRelease (step 8, Table 6.2.3.6.3.2-2)

c1 CHOICE {
idleModeMobilityControlInfo SEQUENCE {
carrierFreq[1] Same downlink EARFCN
as used for Cell 1
}
freqPriorityListUTRA-FDD SEQUENCE (SIZE 1 entry UTRA-FDD
carrierFreq[1] Same downlink ARFCN
as used for Cell 5
}
freqPriorityListUTRA-TDD SEQUENCE (SIZE 1 entry UTRA-TDD
as used for Cell 5
}
t320 Not present
}
}
}
}
}
ETSI

c1 CHOICE {
as used for Cell 1
}
as used for Cell 5
}
as used for Cell 5
}
t320 Not present
}
}
}
}
}
ETSI

c1 CHOICE {
as used for Cell 1
}
as used for Cell 5
}
as used for Cell 5
}
t320 min5
}
}
}
}
}
Table 6.2.3.6.3.3-8: System Information Block type 19 for Cell 5 (preamble, Table 6.2.3.6.3.2-2)

priority 5
}
6.2.3.7 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD
cell is higher reselection priority than E-UTRA
(1)
with { UE in E-UTRA RRC_IDLE state and UE detects the cell re-selection criteria that HRPD cell is
higher reselection priority than E-UTRAN serving cell }
ensure that { when { UE searches for and measures HRPD cell at least every Thigher_priority_search
and Srxlev,HRPD > ThreshX, HighP }
then { UE reselects the HRPD cell }
}
ETSI
5.2.4.2 and 5.2.4.5 and TS 36.133, clause 4.2.2.5 and 4.2.2.5.4.
[TS 36.304, clause 5.2.4.1]
system information , in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell
[TS 36.304, clause 5.2.4.2]
measurements.
measurements.
- If Snonintrasearch is sent in the serving cell and SServingCell > Snonintrasearch UE may choose not to
priority.
according to [10].
[TS 36.304, clause 5.2.4.5]
ETSI
If ThreshX-Q is provided, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency
than the serving frequency shall be performed if:
- A cell of a higher priority RAT/ frequency fulfils Squal > ThreshX, HighQ during a time interval TreselectionRAT;
and
and
If ThreshX-Q is provided, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency
- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority RAT/ frequency fulfils Squal >
ThreshX, LowQ during a time interval TreselectionRAT; and
[TS 36.133, clause 4.2.2.5]
If the SServingCellof the E-UTRA serving cell is greater than Snonintrasearch, then the UE shall search for inter-RAT layers
of higher priority at least every Thigher_priority_search where Thigher_priority_search is described in section 4.2.2.
If the SServingCellof the E-UTRA serving cell is less than or equal to Snonintrasearchthen the UE shall search for and measure inter-
RAT layers of higher, lower priority in preparation for possible reselection. In this scenario, the minimum rate at which
the UE is required to search for and measure higher priority inter-RAT layers shall be the same as that defined below
for lower priority RATs.
[TS 36.133, clause 4.2.2.5.4]
In order to perform measurement and cell reselection to HRPD cell, the UE shall acquire the timing of HRPD cells.
When the measurement rules indicate that HRPD cells are to be measured, the UE shall measure CDMA2000 HRPD
Pilot Strength of HRPD cells in the neighbour cell list at the minimum measurement rate specified in this section.
The parameter ‘Number of HRPD Neighbour Frequency’, which is transmitted on E-UTRAN BCCH, is the number of
carriers used for all HRPD cells in the neighbour cell list.
When the RSRP of the E-UTRA serving cell (or other cells on the same frequency layer) is lower than ‘HRPD Start
Measuring E-UTRAN Rx Power Strength Threshold’ and HRPD is of lower priority than the currently selected E-
UTRAN frequency layer, the UE shall measure CDMA2000 HRPD Pilot Strength of the HRPD cells at least every
(Number of HRPD Neighbour Frequency)*TmeasureHRPD.
ETSI
The UE shall be capable of evaluating that the HRPD cell has met cell reselection criterion defined in [1] within
TevaluateHRPD.
Table 4.2.2.5.4-1 gives values of TmeasureHRPD and TevaluateHRPD.
Table 4.2.2.5.4-1: TmeasureHRPD and TevaluateHRPD

DRX TmeasureHRPD TevaluateHRPD [s]
cycle [s] (number (number of
length of DRX DRX cycles)
[s] cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
System Simulator:
- Cell 1 for E-UTRAN
- Cell 15 for HRPD with higher reselection priority than Cell 1
UE:
None.
Preamble:
in the Main behaviour description in Table 6.2.3.7.3.2-2.
T1 Îor/Ioc dB - -20 Cell 15 is on

dBm/1. Srxlev,HRPD of Cell 15 < ThreshX, HighP
Ioc 23 - -75
MHz
dBm/1
Cell-specific RS EPRE -60
5 KHz
T2 Îor/Ioc dB - 0 Increase pilot power of HRPD cell such
dBm/1. that Srxlev,HRPD of Cell 15 > ThreshX, HighP
Ioc 23 - -75
MHz
dBm/1
5 KHz
SS.
ETSI

U-S Message
1 Void - - - -
"T1" in table 6.2.3.7.3.2-1. Cell 15 is on and it
has higher reselection priority than Cell1.
3 UE performs measurement for Cell 15 at every - - - -
Thigher_priority_search
4 Check: Does the UE transmit an Access Probe --> Access Probe 1 F
on Cell 15 within the next [60s]?
5 SS adjust HRPD cell signal level to make sure - - - -
SnonServingCell,HRPD of Cell 15 > ThreshHRPD, high,
according to “T2” in table 6.2.3.7.3.2-2
on Cell 15?
1)

}
ETSI
1)

the SS
}
}
searchWindowSize 5
parametersHRPD SEQUENCE { HRPD
HRPD carriers
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]
}
}
}
}
6.2.3.7a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD
cell is higher reselection priority than E-UTRA (Srxlev > ThreshHRPD, HighP)
(1)
with { UE in E-UTRA RRC_IDLE }
ensure that {
when { UE detects a HRPD cell with higher reselection priority than the E-UTRAN serving cell }
then { UE does not reselect the HRPD cell }
}
Note: The UE is expected during this time to do measurements on the HRPD cell at least every
Thigher_priority_search but this cannot be easily verified
(2)
with { UE in E-UTRA RRC_IDLE having detected a HRPD cell with higher reselection priority than the
E-UTRAN serving cell } ensure that {
when { Srxlev,HRPD > ThreshHRPD, HighP }
}
ETSI
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.2]
priority.
- Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency

cells of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]
ETSI

and

[TS 36.133, clause 4.2.2.5]
If Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ then the UE shall search for inter-RAT layers of higher priority at
least every Thigher_priority_search where Thigher_priority_search is described in section 4.2.2
If Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ then the UE shall search for and measure inter-RAT layers of higher,
lower priority in preparation for possible reselection. In this scenario, the minimum rate at which the UE is required to
ETSI
search for and measure higher priority inter-RAT layers shall be the same as that defined below for lower priority
RATs.
[TS 36.133, clause 4.2.2.5.4]
When the E-UTRA serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE shall search for
CDMA2000 HRPD layers of higher priority at least every Thigher_priority_search where Thigher_priority_search is defined in section
4.2.2.
For CDMA2000 HRPD cells which have been detected, the UE shall measure CDMA2000 HRPD Pilot Strength at
least every (Number of HRPD Neighbour Frequency)*TmeasureHRPD, when the E-UTRA serving cell Srxlev ≤
SnonIntraSearchP or Squal ≤ SnonIntraSearchQ.
The UE shall be capable of evaluating that the CDMA2000 HRPD cell has met cell reselection criterion defined in [1]
within TevaluateHRPD.

[s] cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
If Treselection timer has a non zero value and the CDMA2000 HRPD cell is satisfied with the reselection criteria which are
defined in [1], the UE shall evaluate this CDMA2000 HRPD cell for the Treselection time. If this cell remains satisfied with
the reselection criteria within this duration, then the UE shall reselect that cell.
System Simulator:
- Cell 15 for HRPD with higher reselection priority than Cell 1
UE:
None.
Preamble:
ETSI

dBm/1. Srxlev,HRPD of Cell 15 < ThreshHRPD,HighP
Ioc 23 - -75
MHz
dBm/1
5 KHz
T2 Îor/Ioc dB - 0 Increase pilot power of HRPD cell such
dBm/1. that Srxlev,HRPD of Cell 15 >
Ioc 23 - -75 ThreshHRPD,HighP
MHz
dBm/1
5 KHz
SS.

U-S Message
"T1" in table 6.2.3.7a.3.2-1. Cell 15 is on and it
has higher reselection priority than Cell1.
Srxlev of Cell 15 > ThreshHRPD, HighP, according
to “T2” in table 6.2.3.7a.3.2-1
on Cell 15?
Note 1: The UE is expected during this time to do measurements on the HRPD cell at least every Thigher_priority_search
but this cannot be easily verified.
Table 6.2.3.7a.3.3-1: SystemInformationBlockType1 to Cell 1 (Preamble and all steps, table 6.2.3.7.3.2-
2)

}
ETSI
Table 6.2.3.7a.3.3-2: Void
Table 6.2.3.7a.3.3-3: SystemInformationBlockType8 to Cell 1 (Preamble and all steps, table

6.2.3.7a.3.2-2)

the SS
}
}
searchWindowSize 5
HRPD carriers
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]
}
}
}
}
6.2.3.8 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD
is lower reselection priority than E-UTRA
(1)
with { UE in E-UTRA RRC_IDLE state and UE detects the cell re-selection criteria that HRPD cell is
equial to or lower reselection priority than E-UTRAN serving cell }
ensure that {
When{ SServingCell <= ThreshServing, LowP and Srxlev > ThreshHRPD, low }
then { UE searches for and measures HRPD cell at least every TmeasureHRPD and reselects the HRPD
cell }
}
[TS 36.304, clause 5.2.4.1]
system information or in the RRC message releasing the RRC connection. If priorities are assigned via dedicated
signalling, the UE shall ignore all the priorities provided in system information. The UE shall delete priorities provided
by dedicated signalling when:
ETSI
UE shall only perform reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in
system information and for which the UE has a priority provided.
[TS 36.304, clause 5.2.4.2]
- If SServingCell > Sintrasearch, UE may choose to not perform intra-frequency measurements.
- If SServingCell <= Sintrasearch, UE shall perform intra-frequency measurements.
o For an E-UTRAN inter-frequency or inter-RAT frequency with a reselection priority higher than the
o For an E-UTRAN inter-frequency with a equal or lower reselection priority than the reselection priority of
If SServingCell > Snonintrasearch UE may choose not to perform measurements of E-UTRAN inter-
frequencies or inter-RAT frequencies of equal or lower priority.
If SServingCell <= Snonintrasearch the UE shall perform measurements of E-UTRAN inter-frequencies

or inter-RAT frequencies cells of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]
and
and
ETSI
[TS 36.133, clause 4.2.2.5]
If the SServingCellof the E-UTRA serving cell (or other cells on the same frequency layer) is greater than Snonintrasearch,
then
- the UE may not search for, or measure inter-RAT layers of equal or lower priority.
- the UE shall search for inter-RAT layers of higher priority at least every Thigher_priority_search where Thigher_priority_search
is described in section 4.2.2.
If the SServingCellof the E-UTRA serving cell is less than or equal to Snonintrasearch, then the UE shall search for and measure inter-
RAT layers of higher, equal or lower priority in preparation for possible reselection. In this scenario, the minimum rate
at which the UE is required to search for and measure such layers is not reduced and shall be the same as that defined
below for lower priority RATs.
[TS 36.133, clause 4.2.2.5.4]
When the RSRP of the E-UTRA serving cell (or other cells on the same frequency layer) is lower than ‘HRPD Start
Measuring E-UTRAN Rx Power Strength Threshold’ and HRPD is of lower priority than the currently selected E-
UTRAN frequency layer, the UE shall measure CDMA2000 HRPD Pilot Strength of the HRPD cells at least every
(Number of HRPD Neighbour Frequency)*TmeasureHRPD. In case HRPD is of higher priority than the currently selected E-
UTRAN frequency layer the UE shall measure HRPD cells at least every (Number of HRPD Neighbour Frequency)*
Thigher_proirty_search. The parameter Thigher_proirty_search is defined in section 4.2.2.
The UE shall be capable of evaluating that the HRPD cell has met cell reselection criterion defined in [1] within
TevaluateHRPD.

[s] cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
ETSI
System Simulator:
- Cell 15 for HRPD with lower reselection priority than Cell 1
UE:
None.
Preamble:

dBm/
Ioc 1.23 - -55
MHz
dBm/1 SServingCellof the E-UTRA > ThreshServing, LowP
Cell-specific RS EPRE -70 -
5kHz and Srxlev,HRPD of Cell 15 < Threshx,
Srxlev (Note 1) dB 40 -40 low
T2 Îor/Ioc dB - -5 Increase pilot power of HRPD cell
dBm/1. such that SnonServingCell,HRPD of Cell 15 >
Ioc 23 - -55 Threshx, low
MHz
Pilot Ec/Io (Note 1) dB - -6.2
dBm/1
5kHz
Srxlev (Note 1) dB -10 -12
SS.
Note 2: Default value of ThreshServing, LowP is 0.
ETSI

U-S Message
1 Cell 15 is on and it has lower reselection - - - -
priority than Cell 1, according to “T1” in
6.2.3.8.3-1.
SS adjusts the serving cell signal level so that
SServingCellof the E-UTRA <= Snonintrasearch.2
2 Void
TmeasureHRPD
SnonServingCell,HRPD of Cell 15 > ThreshHRPD, low
according to “T2” in 6.2.3.8.3.2-1.
on Cell 15?
1)

}
}
ETSI
1)

the SS
}
}
searchWindowSize 5
HRPD carriers
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]
threshX-High 30[-30] INTEGER (0..63)
threshX-Low 32[-32] INTEGER (0..63)
}
}
}
}
6.2.3.8a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD
cell is lower reselection priority than E-UTRA (Squal < ThreshServing, LowQ and
Srxlev > ThreshHRPD, LowP
(1)
ensure that {
when { UE detects a HRPD cell with equal or lower reselection priority than the E-UTRAN serving
cell }
then { UE does not reselect the HRPD cell }
}
Note: The UE is expected during this time to do measurements on

the HRPD cell at least every TmeasureHRPD but this cannot be easily verified
(2)
with { UE in E-UTRA RRC_IDLE having detected a HRPD cell with equal or lower reselection priority
than the E-UTRAN serving cell }
ensure that {
when { Srxlev, HRPD > ThreshHRPD, LowP }
}
ETSI
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.2]
priority.
ETSI
- Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of
equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]

and

[TS 36.133, clause 4.2.2.5]
ETSI
RATs.
[TS 36.133, clause 4.2.2.5.4]
CDMA2000 HRPD layers of higher priority at least every Thigher_priority_search where Thigher_priority_search is defined in section
4.2.2.
For CDMA2000 HRPD cells which have been detected, the UE shall measure CDMA2000 HRPD Pilot Strength at
least every (Number of HRPD Neighbour Frequency)*TmeasureHRPD, when the E-UTRA serving cell Srxlev ≤
SnonIntraSearchP or Squal ≤ SnonIntraSearchQ.
The UE shall be capable of evaluating that the CDMA2000 HRPD cell has met cell reselection criterion defined in [1]
within TevaluateHRPD.

[s] cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
If Treselection timer has a non zero value and the CDMA2000 HRPD cell is satisfied with the reselection criteria which are
defined in [1], the UE shall evaluate this CDMA2000 HRPD cell for the Treselection time. If this cell remains satisfied with
System Simulator:
- Cell 15 for HRPD with lower reselection priority than Cell 1
UE:
None.
Preamble:
ETSI

dBm/
Ioc 1.23 - -55
MHz
dBm/1 - SServingCellof the E-UTRA > ThreshServing, LowP
5kHz and Srxlev,HRPD of Cell 15 <
Srxlev (Note 1) dB 40 -40 ThreshHRPD, LowP
T2 Îor/Ioc dB - -5 Increase pilot power of HRPD cell
dBm/1. such that SnonServingCell,HRPD of Cell 15 >
Ioc 23 - -55 ThreshHRPD,LowP
MHz
Pilot Ec/Io (Note 1) dB - -6.2
dBm/1
5kHz
Srxlev (Note 1) dB -10 -12
SS.

U-S Message
6.2.3.8a.3.2-1.
SS adjusts the serving cell signal level so that
E-UTRA serving cell Squal <= SnonIntraSearchQ
TmeasureHRPD
Srxlev of Cell 15 > ThreshHRPD, LowP according
to “T2” in 6.2.3.8a.3.2-1.
on Cell 15?
Note 1: The UE is expected during this time to do measurements on the HRPD cell at least every TmeasureHRPD but
this cannot be easily verified.

6.2.3.8a.3.2-2)

}
}
ETSI
Table 6.2.3.8a.3.3-2: SystemInformationBlockType3 for Cell 1 (Preamble and all steps, table
6.2.3.8a.3.2-2)

threshServingLow 5 (10dB)
}
threshServingLowQ-r9 26
}
}

6.2.3.8a.3.2-2)

the SS
}
}
searchWindowSize 5
HRPD carriers
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]
threshX-High 30[-30] INTEGER (0..63)
threshX-Low 32[-32] INTEGER (0..63)
}
}
}
}
6.2.3.9 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT

Dormant– When CDMA2000 1xRTT cell is higher reselection priority than E-
UTRA
(1)
with { UE in E-UTRA RRC_IDLE and UE detects a 1xRTT cell with higher reselection priority than E-
UTRAN serving cell }
ensure that {
ETSI
when { SnonServingCell,CDMA2000_1x <= Thresh1xRTT, high }

then { UE does not reselect the CDMA2000 1xRTT cell }
}
(2)
with { UE in E-UTRA RRC_IDLE and UE detects a 1xRTT cell with higher reselection priority than E-
UTRAN serving cell }
ensure that {
when { SnonServingCell,CDMA2000_1x > Thresh1xRTT, high }
then { UE reselects the CDMA2000 1xRTT cell }
}
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.5]
and
and
ETSI
- If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest
priority frequency(ies) meeting the criteria of that RAT.
[TS 36.133, clause 4.2.2.5]
RATs.
[TS 36.133, clause 4.2.2.5.5]
In order to perform measurement and cell reselection to cdma2000 1X cell, the UE shall acquire the timing of
cdma2000 1X cells.
When the measurement rules indicate that cdma2000 1X cells are to be measured, the UE shall measure cdma2000 1x
RTT Pilot Strength of cdma2000 1X cells in the neighbour cell list at the minimum measurement rate specified in this
section.
The parameter ‘Number of CDMA2000 1X Neighbour Frequency’, which is transmitted on E-UTRAN BCCH, is the
number of carriers used for all cdma2000 1X cells in the neighbour cell list.
If SServingCell of the E-UTRA serving cell is greater than Snonintrasearch, the UE shall search for cdma2000 1X layers of
higher priority at least every Thigher_priority_search where Thigher_priority_search is defined in section 4.2.2.
ETSI
For CDMA2000 1X cells which have been detected, the UE shall measure CDMA2000 1xRTT Pilot Strength at least
every (Number of CDMA2000 1X Neighbour Frequency)*TmeasureCDMA2000_1X, when the SServingCell of the E-UTRA
serving cell is less than or equal to Snonintrasearch.
The UE shall be capable of evaluating that the cdma2000 1X cell has met cell reselection criterion defined in [1] within
TevaluateCDMA2000_1X.
Table 4.2.2.5.5-1 gives values of TmeasureCDMA2000_1X and TevaluateCDMA2000_1X.
Table 4.2.2.5.5-1: TmeasureCDMA2000 1X and TevaluateCDMA2000 1X

DRX TmeasureCDMA2000_1X TevaluateCDMA2000_1X
cycle [s] (number of [s] (number of
length DRX cycles) DRX cycles)
[s]
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
If Treselection timer has a non zero value and the CDMA2000 1X cell is better ranked than the serving cell, the UE shall
evaluate this CDMA2000 1X cell for the Treselection time. If this cell remains better ranked within this duration, then the
System Simulator:
- Cell 19 for CDMA2000 1xRTT with higher reselection priority than Cell 1
UE:
None.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows marked "T1"
and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the
texts in this clause.
ETSI

T0 - The power levels are such that camping
on Cell 1 is guaranteed.
T1 Cell-specific RS EPRE dBm/15 KHz -75 Cell 19 is on
Îor/Ioc dB -15
Pilot Ec/ Ior -7
Ioc dBm - -75
Pilot Ec/ Io (Note 1) dB - -22
T2 Cell-specific RS EPRE dBm/15 KHz -75 Increase pilot power of 1xRTT cell such
Îor/Ioc dB 0 that SnonServingCell, of Cell 19 > Thresh1xRTT,
Pilot Ec/ Ior dB - -7 high
SS.

U-S Message
1 Cell 19 is on and it has higher reselection - - - -
priority than Cell1, according to “T1” in
6.2.3.9.3.2-1
2 Void - - - -
on Cell 19 within the next 60s?
4 SS adjust CDMA2000 1xRTT cell signal level - - - -
to make sure SnonServingCell, 1xRTT of Cell 19 >
Thresh1xRTT, high, according to “T2” in
6.2.3.9.3.2-1
on Cell 19?
1)

}
}
ETSI
1)

the SS
}
}
searchWindowSize 5
parameters1XRTT SEQUENCE { 1XRTT
cellReselectionParameters1XRTT SEQUENCE {
1xRTT carriers
bandClass Band Class of frequency ENUMERATED {
under test bc0, bc1, bc2,
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2, spare1,
...}
when 1xRTT is
lower priority than
E-UTRA. 5 is
applicable when
1xRTTis higher
priority than E-
UTRA]
}
}
}
}
6.2.3.9a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant /

1xRTT cell is higher reselection priority than E-UTRA (Srxlev > Thresh1xRTT,
HighP)
(1)
ensure that {
when { UE detects a 1xRTT cell with higher reselection priority than the E-UTRAN serving cell }
then { UE does not reselect the 1xRTT cell }
}
Note: The UE is expected during this time to do measurements on the 1xRTT cell at least every
Thigher_priority_search but this cannot be easily verified.
ETSI
(2)
with { UE in E-UTRA RRC_IDLE having detected a 1xRTT cell with higher reselection priority than the
E-UTRAN serving cell } ensure that {
when { Srxlev,CDMA2000_1x > Thresh1xRTT, HighP }
}
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.5]

and
ETSI

[TS 36.133, clause 4.2.2.5]
RATs.
[TS 36.133, clause 4.2.2.5.5]
cdma2000 1X cells.
section.
cdma2000 1X layers of higher priority at least every Thigher_priority_search where Thigher_priority_search is defined in section 4.2.2.
ETSI
every (Number of CDMA2000 1X Neighbour Frequency)*TmeasureCDMA2000_1X, when the E-UTRA serving cell Srxlev ≤
SnonIntraSearchP or Squal ≤ SnonIntraSearchQ. The UE shall be capable of evaluating that the cdma2000 1X cell has met cell
reselection criterion defined in [1] within TevaluateCDMA2000_1X.

[s]
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
If Treselection timer has a non zero value and the CDMA2000 1X cell is satisfied with the reselection criteria which are
defined in [1], the UE shall evaluate this CDMA2000 1X cell for the Treselection time. If this cell remains
satisfied with the reselection criteria within this duration, then the UE shall reselect that cell.
System Simulator:
- Cell 19 for CDMA2000 1xRTT with higher reselection priority than Cell 1
UE:
None.
Preamble:
ETSI

T1 Cell-specific RS EPRE dBm/15 KHz -75 Cell 19 is on
Îor/Ioc dB -15
Pilot Ec/ Ior -7
Ioc dBm - -75
T2 Cell-specific RS EPRE dBm/15 KHz -75 Increase pilot power of 1xRTT cell such
Îor/Ioc dB 0 that SnonServingCell, of Cell 19 > Thresh1xRTT,
Pilot Ec/ Ior dB - -7 HighP
SS.

U-S Message
1 Cell 19 is on and it has higher reselection -- - -
priority than Cell1, according to “T1” in
6.2.3.9a.3.2-1
4 SS adjust CDMA2000 1xRTT cell signal level - - - -
to make sure Srxlev of Cell 19 > Thresh1xRTT,
HighP, according to “T2” in 6.2.3.9a.3.2-1
on Cell 19?
Note 1: The UE is expected during this time to do measurements on the HRPD cell at least every Thigher_priority_search
but this cannot be easily verified.

6.2.3.9a.3.2-2)

}
}
ETSI
Table 6.2.3.9a.3.3-2: Void

6.2.3.9a.3.2-2)

the SS
}
}
searchWindowSize 5
1xRTT carriers
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2, spare1,
...}
when 1xRTT is
lower priority than
E-UTRA. 5 is
applicable when
1xRTTis higher
priority than E-
UTRA]
}
}
}
}
6.2.3.10 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT

Idle – When CDMA2000 1xRTT is lower reselection priority than E-UTRA
(1)
with { UE in E-UTRA RRC_IDLE state and UE detects the cell re-selection criteria that CDMA2000 1xRTT
cell is equial to or lower reselection priority than E-UTRAN serving cell }
ensure that {
When{ SServingCell <= Snonintrasearch }
then { UE searches for and measures CDMA2000 1xRTT cell at least every TmeasureCDMA2000_1X }
when { SnonServingCell,1xRTT > Thresh1xRTT, low }
ETSI
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.5]
and
and
ETSI
- If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest
priority frequency(ies) meeting the criteria of that RAT.
[TS 36.133, clause 4.2.2.5]
If the SServingCellof the E-UTRA serving cell (or other cells on the same frequency layer) is greater than Snonintrasearch,
then
- the UE may not search for, or measure inter-RAT layers of equal or lower priority.
- the UE shall search for inter-RAT layers of higher priority at least every Thigher_priority_search where Thigher_priority_search
is described in section 4.2.2.
If the SServingCellof the E-UTRA serving cell is less than or equal to Snonintrasearch, then the UE shall search for and measure inter-
RAT layers of higher, equal or lower priority in preparation for possible reselection. In this scenario, the minimum rate
at which the UE is required to search for and measure such layers is not reduced and shall be the same as that defined
below for lower priority RATs.
[TS 36.133, clause 4.2.2.5]
RATs.
[TS 36.133, clause 4.2.2.5.5]
cdma2000 1X cells.
section.
ETSI
If SServingCell of the E-UTRA serving cell is greater than Snonintrasearch, the UE shall search for cdma2000 1X layers of
higher priority at least every Thigher_priority_search where Thigher_priority_search is defined in section 4.2.2.
every (Number of CDMA2000 1X Neighbour Frequency)*TmeasureCDMA2000_1X, when the SServingCell of the E-UTRA
serving cell is less than or equal to Snonintrasearch.
The UE shall be capable of evaluating that the cdma2000 1X cell has met cell reselection criterion defined in [1] within
TevaluateCDMA2000_1X.

[s]
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
If Treselection timer has a non zero value and the CDMA2000 1X cell is better ranked than the serving cell, the UE shall
evaluate this CDMA2000 1X cell for the Treselection time. If this cell remains better ranked within this duration, then the
System Simulator:
- Cell 19 for CDMA2000 1xRTT with lower reselection priority than Cell 1
UE:
None.
Preamble:
ETSI

T1 Cell-specific RS EPRE dBm/15 KHz -100 - Cell 19 is on and SnonServingCell, of Cell 19 <
Îor/Ioc dB - -15 Thresh1xRTT, Low
Pilot Ec/ Ior -7
Ioc dBm - -75
T2 Cell-specific RS EPRE dBm/15 KHz -120 - Increase pilot power of 1xRTT cell such
Îor/Ioc dB - 0 that SnonServingCell, of Cell 19 > Thresh1xRTT,
Pilot Ec/ Ior dB - -7 Low and SServingCellof the E-UTRA < ThreshServing,
Ioc dBm/1.23 MHz - -75 LowP
Note 1: This parameter is not directly settable, but is derived by calculation from the other parameters set by the SS.

U-S Message
6.2.3.10.3.2-1
SS adjust the serving cell signal level so that
SServingCellof the E-UTRA <= Snonintrasearch
2 UE performs measurement for Cell 19 at every - -
TmeasureCDMA2000_1X
4 SS adjust CDMA2000 1xRTT Cell 19 signal
level to make sure SnonServingCell,1xRTT of Cell 19
> Thresh1xRTT, low, according to “T2” in
6.2.3.10.3.2-1
on Cell 19?
Table 6.2.3.10.3.3-1: SystemInformationBlockType1 to Cell 1 (Preamble and all steps, table

6.2.3.10.3.2-1)

}
}
ETSI
Table 6.2.3.10.3.3-2: SystemInformationBlockType8 to Cell 1 (Preamble and all steps, table

6.2.3.10.3.2-1)

the SS
}
}
searchWindowSize 5
1xRTT carriers
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2, spare1,
...}
when 1xRTT is
lower priority than
E-UTRA. 5 is
applicable when
1xRTTis higher
priority than E-
UTRA]
}
}
}
}
6.2.3.10a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant /

1xRTT cell is lower reselection priority than E-UTRA (Squal < ThreshServing,
LowQ and Srxlev > Thresh1xRTT, LowP)
(1)
ensure that {
when { UE detects a CDMA2000 1xRTT cell with equal or lower reselection priority than the E-UTRAN
serving cell }
then { UE does not reselect the a CDMA2000 1xRTT cell }
}
Note: The UE is expected during this time to do measurements on the CDMA2000 1xRTT cell at least
every TmeasureCDMA2000_1X but this cannot be easily verified
ETSI
(2)
with { UE in E-UTRA RRC_IDLE having detected a HRPD cell with equal or lower reselection priority
than the E-UTRAN serving cell } ensure that {
when { Srxlev,1xRTT > Thresh1xRTT, LowP }
}
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.5]

and
ETSI

[TS 36.133, clause 4.2.2.5]
RATs.
[TS 36.133, clause 4.2.2.5.5]
cdma2000 1X cells.
section.
cdma2000 1X layers of higher priority at least every Thigher_priority_search where Thigher_priority_search is defined in section 4.2.2.
ETSI
every (Number of CDMA2000 1X Neighbour Frequency)*TmeasureCDMA2000_1X, when the E-UTRA serving cell Srxlev ≤
SnonIntraSearchP or Squal ≤ SnonIntraSearchQ. The UE shall be capable of evaluating that the cdma2000 1X cell has met cell
reselection criterion defined in [1] within TevaluateCDMA2000_1X.

[s]
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)
If Treselection timer has a non zero value and the CDMA2000 1X cell is satisfied with the reselection criteria which are
defined in [1], the UE shall evaluate this CDMA2000 1X cell for the Treselection time. If this cell remains satisfied with
System Simulator:
- Cell 19 for CDMA2000 1xRTT with lower reselection priority than Cell 1
UE:
None.
Preamble:
ETSI

T1 Cell-specific RS EPRE dBm/15 KHz -100 - Cell 19 is on and SnonServingCell, of Cell 19 <
Îor/Ioc dB - -15 Thresh1xRTT, LowP
Pilot Ec/ Ior -7
Ioc dBm - -75
T2 Cell-specific RS EPRE dBm/15 KHz -120 - Increase pilot power of 1xRTT cell such
Îor/Ioc dB - 0 that SnonServingCell, of Cell 19 > Thresh1xRTT,
Pilot Ec/ Ior dB - -7 LowP and SServingCellof the E-UTRA <
Ioc dBm/1.23 MHz - -75 ThreshServing, LowP

U-S Message
6.2.3.10a.3.2-1
SS adjust the serving cell signal level so that
E-UTRA serving cell Squal <= SnonIntraSearchQ
2 UE performs measurement for Cell 19 at every - -
TmeasureCDMA2000_1X
4 SS adjust CDMA2000 1xRTT Cell 19 signal
level to make sure Srxlev of Cell 19 >
Thresh1xRTT, low, according to “T2” in
6.2.3.10a.3.2-1
on Cell 19?
Note 1: The UE is expected during this time to do measurements on the HRPD cell at least every
TmeasureCDMA2000_1X but this cannot be easily verified.

6.2.3.10.3.2-2)

}
}
Table 6.2.3.10a.3.3-2: SystemInformationBlockType3 for Cell 1 (Preamble and all steps, table
6.2.3.10a.3.2-2)

}
ETSI
}
}

6.2.3.10a.3.2-2)

the SS
}
}
searchWindowSize 5
1xRTT carriers
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2, spare1,
...}
when 1xRTT is
lower priority than
E-UTRA. 5 is
applicable when
1xRTTis higher
priority than E-
UTRA]
}
}
}
}
ETSI
6.2.3.11 Void
6.2.3.12 Void
6.2.3.13 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE
according to RAT priority provided by dedicated signalling
(1)
ensure that {
priority inter-RAT E-UTRA cell based on the configured RAT priority provided by dedicated signaling
}
}
(2)
with { UE in E-UTRA RRC_IDLE state having inherit RAT priority provided by dedicated signaling with
the remaining validity time }
ensure that {
when { UE discard the inherit RAT priority upon connection establishment }
then { UE reselects a cell by applying the cellReselectionPriority broadcast in the system
information }
}
5.2.6.1.4a; TS 25.331, clause 8.3.3.3 and 8.6.7.23; TS 36.331, clause 5.3.3.4; TS 25.133, clause 4.2.2.5a
[TS 25.304, clause 5.2.6.1.2a]
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
ETSI
is fulfilled.
fulfilled.
serving cell.
[TS 25.331, clause 8.3.3.3]
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:
1> act on received information elements as specified in subclause 8.6;
1> if the IE "Dedicated Priority Information" is present:
2> act upon the received IE as described in subclause 8.6.7.23.
[TS 25.331, clause 8.6.7.23]
If the CHOICE "Action" has the value "Configure dedicated priorities", the UE shall:
1> clear the variable PRIORITY_INFO_LIST;
1> stop timer T322, if it is running;
1> set the value of IE "Priority status" in the variable PRIORITY_INFO_LIST to "dedicated_priority";
1> for each occurrence of the IE "Priority Level List":
2> create a new entry in the IE "Priority Info List" in the variable PRIORITY_INFO_LIST, and in that new
entry:
3> set the CHOICE "Radio Access Technology" to the value received in the IE "Priority Level List";
3> set the IE "priority" to the value received in the IE "Priority Level List";
3> set the values in IE "Frequency List" or "BCCH ARFCN List" to the values received in the IE "Priority
Level List".
1> set the IE "E-UTRA detection" to the value received in the IE "Priority Level List".
1> if the IE "T322" is present:
2> start timer T322 using the value signalled in this IE.
1> if the UE is not in CELL_DCH state:
2> take the actions as described in subclause 8.1.1.6.19 using stored System information Block type 19.
[TS 36.331, clause 5.3.3.4]
The UE shall:
ETSI
1> perform the radio resource configuration procedure in accordance with the received
radioResourceConfigDedicated and as specified in 5.3.10;
1> stop timer T300;
1> stop timer T302, if running;
1> perform the actions as specified in 5.3.3.7;
1> enter RRC_CONNECTED;
1> stop the cell re-selection procedure;
...
procedure ends;
[TS 25.133, clause 4.2.2.5a]
The UE shall be able to evaluate whether a new detectable lower priority inter-RAT E-UTRA cell meets the reselection
criteria defined in [1] within Kcarrier * TdetectE-UTRA, where TdetectE-UTRA is given in Table 4.2, if E-UTRA carrier frequency
information is provided in the inter-RAT measurement control system information when Treselection=0 provided that
the reselection criteria is met by at least 6dB. The parameter Kcarrier is the number of E-UTRA carrier frequencies
indicated in the inter-RAT measurement control system information. An inter RAT E-UTRAN cell is considered to be
detectable if:
- RSRP|dBm according to Annex B.1.1 for a corresponding Band
For an inter-RAT E-UTRA cell that has been already detected, but that has not been reselected to, the filtering shall be
such that the UE shall be capable of evaluating that the E-UTRA cell has met reselection criterion defined TS 36.304
within Kcarrier * TevaluateEUTRA as specified in table 4.2 provided that the reselection criteria is met by at least 6dB and the
Treselection timer is set to zero.
System Simulator:
NOTE: Common Priority information for Cell 1 & Cell 5: UTRA priority = 3; E-UTRA priority = 4.
UE:
None.
ETSI
Preamble:
- The UE is in state PS-DCCH+DTCH_DCH (state 6-10) on Cell 5 according to [5].
Tables 6.2.3.13.3.2-1 and 6.2.3.13.3.2-2 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 conditions after the
preamble, while row marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values
shall be applied are described in the texts in this clause.

T0 Qrxlevmin dBm -106 Default value
Srxlev* dB 9
T1
qRxLevMinEUTRA
S nonServingCell, Cell1 > Thresh Cell1,low
T2
Qrxlevmin dBm -106 Default value
Srxlev* dB 9

The power levels are such that
camping on Cell 5 is guaranteed.
Srxlev* dB 19
Srxlev* dB 4 SrxlevServingCell < Thresh Serving,low
Srxlev* dB 19
ETSI

U-S Message
1 The SS provides dedicated priority information <-- UTRAN MOBILITY - -
(UTRA priority = 5; E-UTRA priority = 4) and INFORMATION
validity timer to the UE.
2 The SS receives the UTRAN MOBILITY --> UTRAN MOBILITY - -
INFOMRATION CONFIRM message. INFORMATION CONFIRM
3 The SS releases the UE connection. <-- RRC CONNECTION RELEASE - -
4 The SS receives UE release complete --> RRC CONNECTION RELEASE - -
message. COMPLETE
message. COMPLETE
message. COMPLETE
1 and table 6.2.3.13.3.2-2.
8 Check: does the test result of generic test - - 1 -
Cell 1?
9 Void - - - -
information.
1 and table 6.2.3.13.3.2-2.
5?
ETSI
Table 6.2.3.13.3.3-1: UTRAN MOBILITY INFORMATION for Cell 5 (step 1, Table 6.2.3.13.3.2-3)
Derivation Path: 34.108, clause 9

UTRANMobilityInformation ::= CHOICE {
later-than-r3 SEQUENCE {
r7 SEQUENCE {
utranMobilityInformation-v860ext SEQUENCE
{
dedicatedPriorityInformation SEQUENCE {
action CHOICE {
configureDedicatedPriorities SEQUENCE
{
t-322 5 Time in minutes
priorityLevelList SEQUENCE (SIZE 2 entry
(1..maxPrio)) OF SEQUENCE {
priority[1] 5
radioAccessTechnology[1] CHOICE {
utraFDD SEQUENCE (SIZE 1 entry UTRA-
(1..maxNumFDDFreqs)) OF SEQUENCE { FDD
uarfcn Same downlink UARFCN
as used for Cell 5
}
utraTDD SEQUENCE (SIZE 1 entry UTRA-
(1..maxNumTDDFreqs)) OF SEQUENCE { TDD
as used for Cell 5
}
}
priority[2] 4
eutra SEQUENCE (SIZE 1 entry
earfcn Same downlink EARFCN
as used for Cell 1
}
}
}
E-UTRA detection TRUE
}
}
}
}
}
}
}
}
}
}
ETSI
Table 6.2.3.13.3.3-2: RRC CONNECTION RELEASE for Cell 5 (step 3, Table 6.2.3.13.3.2-3)

RRCConnectionRelease ::= CHOICE {
r4 SEQUENCE {
n-308 2 2 (for CELL_DCH
state). Not
Present (for UE in
other connected
mode states).
releaseCause normalEvent
rplmn-information Not Present
}
v4d0NonCriticalExtensions SEQUENCE {} Not Present
}
}
}
}
6.2.3.13.3.2-3)

}
}
as used for Cell 1
}
}
Note: GERAN cell priority is not allocated, hence it will be considered as the less than all allowed values of 0 to 7.
6.2.3.13.3.2-3)

}
}
ETSI
Table 6.2.3.13.3.3-5: SystemInformationBlockType6 for Cell 1 (preamble and all steps, Table 6.2.3.
13.3.2-3)

carrierFreq[n] Downlink UARFCN of
Cell 5
threshX-High[n] 5 (10dB)
threshX-Low[n] 5 (10dB)
}
carrierFreq[n] Downlink UARFCN of
Cell 5
threshX-High[n] 5 (10dB)
threshX-Low[n] 5 (10dB)
}
}
6.2.3.14 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA

(priority of E-UTRA cells are higher than the serving cell)
(1)
ensure that {
when { Priority of E-UTRA neighbour cell is set lower than GERAN cell }
then { UE does not reselects the lower priority E-UTRA neighbour cell }
}
(2)
ensure that {
when { Priority of E-UTRA neighbour cell is set higher than GERAN cell }
then { UE reselects the higher priority inter-RAT E-UTRA neighbour cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 10.1.3.3 & TS
44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 10.1.3.3]
Cell reselection to a cell of another inter-RAT frequency shall be performed if any of the conditions below (to be
evaluated in the order shown) is satisfied:
- The S_non-serving_XXX of one or more cells of a higher priority inter-RAT frequency is greater than
THRESH_XXX_high (or, in case of an E-UTRAN target, THRESH_E-UTRAN_high_Q, if provided) during a time
interval T_reselection; in that case, the mobile station shall consider the cells for reselection in decreasing order of
priority and, for cells of the same inter-RAT frequency or of inter-RAT frequencies of equal priority, in decreasing
order of S_non-serving_XXX, and reselect the first cell that satisfies the conditions above;
...
ETSI
If the mobile station applies either common priorities or individual priorities received through dedicated signalling and
priorities are available only for some inter-RAT frequencies, cells belonging to frequencies for which no priority is
available or no threshold is provided by the serving cell shall not be considered for measurement and for cell re-
selection.
If a mobile station in camped normally state (see 3GPP TS 43.022) applies individual priorities received through
dedicated signalling and no priority is available for the serving cell, the mobile station shall consider any GSM cell
(including the serving cell) to have lowest priority (i.e. lower than the eight network configured values).
[TS 44.018, clause 3.4.1.2.1.1a]
This applies only to a multi-RAT MS supporting E-UTRAN. One or more instances of the Measurement Information
message or SI2quater message may provide E-UTRAN Neighbour Cell Description information in one or more
instances of the Repeated E-UTRAN Neighbour Cells IE. This is used to build the E-UTRAN Neighbour Cell list. The
E-UTRAN Neighbour Cell list may contain up to 8 E-UTRAN frequencies. For each E-UTRAN frequency, zero or
more E-UTRAN neighbour cells may be specified that are not allowed for cell reselection. The list of not allowed cells
is defined in the Not Allowed Cells IEs.
Each EARFCN in each instance of the Repeated E-UTRAN Neighbour Cells IE is added to the E-UTRAN Neighbour
Cell list in the order in which it is received.
System Simulator:
- Two cells:
- One E-UTRAN cell, Cell 1 is Suitable neighbour inter-frequency cell.
UE:
None.
Preamble:
- The UE is in state Registered, IDLE (GPRS) on Cell 24 (3GPP TS 51.010-1 clause 41.2.8.1.1)

U-S Message
next 75 s (70 s + T_reselect)?
2 The SS changes SI2Quater in Cell 24 - - - -
according to table 6.2.3.14.3.3-2.
3 The SS changes SI13 in Cell 24 according to - - - -
table 6.2.3.14.3.3-3.
4 Void - - - -
Cell 1?
ETSI
Table 6.2.3.14.3.3-1: Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24 in Preamble

GERAN_PRIORITY 5
THRESH_Priority_Search 0
THRESH_GSM_low 0
}
Repeated E-UTRAN Neighbour Cells ::= {
EARFCN Same as cell 1 This field specifies
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
Measurement Bandwidth Same as cell 1
E-UTRAN_PRIORITY ‘100’B 4
THRESH_E-UTRAN_high ‘00010’B Actual value =4 dB
THRESH_E-UTRAN_low ‘00010’B Actual value =4 dB
}
Table 6.2.3.14.3.3-2: Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24 in table
6.2.3.14.3.2-1 step 2

SI 2QUATER REST OCTETS
MP Change Mark 1
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
E-UTRAN_PRIORITY ‘110’B 6
}
Table 6.2.3.14.3.3-3: SI13 for Cell 24 in table 6.2.3.14.3.2-1 step 3
Derivation Path: 51.010-1 clause 40.2.1.1.1

SI 13 Rest Octets ::= {
BCCH_CHANGE_MARK ‘001’B
SI_CHANGE_FIELD ‘0010’B Update of SI2, SI2
bis or SI2 ter
message or any
instance of SI2quater
messages.
}
ETSI

(priority of E-UTRA cells are lower than the serving cell)
(1)
ensure that {
when { Srxleveutran < THRESH_E-UTRAN_low for the lower priority inter-RAT E-UTRA cell }
then { UE does not reselects the lower priority inter-RAT E-UTRA cell }
}
(2)
ensure that {
when { Srxleveutran > THRESH_E-UTRAN_low for the lower priority inter-RAT E-UTRA cell }
then { UE reselects the lower priority inter-RAT E-UTRA cell }
}
44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 10.1.3.3]
...
- The value of S_serving is lower than THRESH_serving_low for the serving cell and all measured GSM cells; in
this case, the mobile station shall consider for reselection the inter-RAT cells in the following order, and reselect
the first one that satisfies the following criteria:
- cells of a lower priority inter-RAT frequency whose S_non-serving_XXX is greater than

THRESH_XXX_low during a time interval T_reselection; these cells shall be considered in decreasing order
of priority and, for cells of the same RAT, in decreasing order of S_non-serving_XXX;
[TS 44.018, clause 3.4.1.2.1.1a]
System Simulator:
- Two cells:
- One E-UTRAN cell, Cell 1 is Suitable neighbour inter-frequency cell.
None.
ETSI
Preamble:
- The UE is in state Registered, IDLE (GPRS) on Cell 24 (3GPP TS 51.010-1 clause 41.2.8.1.1).

U–S Message
next 30 s (25 s+T_reselect)?
according to table 6.2.3.15.3.3-2. SrxlevCell 1 >
THRESH_E-UTRAN_low.
table 6.2.3.15.3.3-3.
4 Void - - - -
Cell 1?

GERAN_PRIORITY 7
THRESH_GSM_low 15 MS is always allowed
to reselect to lower
priority cells
}
Repeated E-UTRAN Neighbour Cells ::=
SEQUENCE {
EARFCN Same as Cell 1 This field specifies
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
Measurement Bandwidth Same as Cell 1
E-UTRAN_PRIORITY ‘001’B
THRESH_E-UTRAN_high ‘00010’B Actual value = 4 dB
THRESH_E-UTRAN_low ‘10010’B Actual value = 36 dB
}
ETSI
6.2.3.15.3.2-1 step 2

3G BA Indicator 1
MP Change Mark 1
Serving Cell Priority Parameters Description ::= {
THRESH GSM low 15 MS is always allowed
priority cells
}
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
}

bis or SI2 ter
message or any
messages.
}
6.2.3.16 Inter-RAT Cell Reselection / from GSM_Idle to E-UTRAN /based on H_PRIO

criteria
(1)
ensure that {
when { Srxleveutran < THRESH_E-UTRAN_low for the lower priority inter-RAT E-UTRA cell and H_PRIO is
off }
then { UE does not reselects the lower priority inter-RAT E-UTRA cell }
}
(2)
ensure that {
when { Srxleveutran < THRESH_E-UTRAN_low for the lower priority inter-RAT E-UTRA cell and when
Srxleveutran is higher than ServingCell by at least H_PRIO}
then { UE reselects the inter-RAT E-UTRA cell based on H_PRIO}
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.6.6 & TS
44.018, clause 3.4.1.2.1.1a.
ETSI
[TS 45.008, clause 6.6.6]
...
- The value of S_GSM is lower than THRESH_GSM_low for the serving cell and all measured GSM cells during
a time interval T_reselection; in this case, the mobile station shall consider for reselection the inter-RAT cells in
the following order, and reselect the first one that satisfies the following criteria:

THRESH_XXX_low (or, in case of an E-UTRAN target, THRESH_E-UTRAN_low_Q, if provided) during
a time interval T_reselection; these cells shall be considered in decreasing order of priority and, for cells of
the same RAT, in decreasing order of S_non-serving_XXX;
- if no cells satisfy the criterion above, inter-RAT cells for which, during a time interval T_reselection, S_non-
serving_XXX is higher than S_GSM for the serving cell by at least a specific hysteresis H_PRIO; these cells
shall be considered in decreasing order of S_non-serving_XXX.
[TS 44.018, clause 3.4.1.2.1.1a]
System Simulator:
- Two cells:
- One E-UTRAN cell, Cell 1.
None.
Preamble:

Qrxlevmin dBm -112 -
Srxlev* dB 32 - Srxlev should be at least 4dB >
T0 C1
RF Signal level dBm - -80
RXLEV_ACCESS_MIN dBm - -101
C1* dB - 21
Note: Srxlev and C1 is calculated in the UE
ETSI

U–S Message
next 30s (25 s+T_reselect)?
according to table 6.2.3.16.3.3-2. H_PRIO=2
(4dB)
table 6.2.3.16.3.3-3.
4 Void - - - -
5 Check: Does the test result of generic test - - 2 p
Cell 1?

GERAN_PRIORITY 7
priority cells
H_PRIO 0 Rule disabled
}
SEQUENCE {
}
ETSI
6.2.3.16.3.2-1 step 2

MP Change Mark 1
GERAN_PRIORITY 7
priority cells
H_PRIO 2 Reselect to inter-RAT
cell which is at least
4dB higher than
Serving cell
}
SEQUENCE {
}

bis or SI2 ter
message or any
messages.
}

(priority E-UTRA cells)
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which has priority}
then { UE does not reselects the inter-RAT E-UTRA cell without priority}
}
44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 6.6.6]
The network shall provide priority information if E-UTRAN frequencies are included in the neighbour cell list; the
network may provide priority information if only UTRAN frequencies are included in the neighbour cell list. If priority
information is available to the mobile station and the mobile station supports priority based inter-RAT cell re-selection,
the algorithm in this subclause shall be used for inter-RAT reselection towards all RATs. The rules regarding which set
of priorities is valid at any given time are defined in 3GPP TS 44.018.
ETSI
[TS 44.018, clause 3.4.1.2.1.1a]
System Simulator:
- Cell 24 is serving cell.
- Cell 1 and Cell 3 off cells.
UE:
None.
Preamble:
Parameter Unit Cell 1 Cell3 Cell 24 Remark

T1 Cell-specific RS EPRE dBm/15kHz -60 -80 -
Qrxlevmin dBm -110 -110 -
Srxlev* dB 50 30 -
RF Signal level dBm -80
C1 dB 21

U–S Message
table 6.2.2.17.3.2-1
procedure in TS 36.508 subclause 6.4.2.7A-2
Cell 3?
ETSI
Table 6.2.3.17.3.3-1 Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24

GERAN_PRIORITY 7
priority cells
}
SEQUENCE {
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
E-UTRAN_PRIORITY ‘0’ Not Present
}
{
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
Measurement Bandwidth} Same as Cell 3
E-UTRAN_PRIORITY 2
}

(blacklisted E-UTRA cells)
(1)
ensure that {
when { Priority of E-UTRA neighbour cells are set higher than GERAN cell. Among two E-UTRA
neighbor cells, the cell with higher priority is blacklisted }
then { UE ignores black listed E-UTRA neighbour cell
}
44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 6.6.6]
THRESH_XXX_high (or, in case of an E-UTRAN target, THRESH_E-UTRAN_high_Q, if provided) during a
time interval T_reselection; in that case, the mobile station shall consider the cells for reselection in decreasing
order of priority and, for cells of the same inter-RAT frequency or of inter-RAT frequencies of equal priority, in
decreasing order of S_non-serving_XXX, and reselect the first cell that satisfies the conditions above;
ETSI
….
E-UTRAN cells which are included in the list of not allowed cells shall not be considered as candidates for cell
reselection. If the strongest cells on a E-UTRAN frequency are included in the list of not allowed cells, the mobile
station may reselect the strongest valid cell (see subclause 8.4.7) on that frequency.
[TS 44.018, clause 3.4.1.2.1.1a]
System Simulator:
- Cell 24 is serving cell.
- Cell 1 and Cell 3 off cells
None.
Preamble:
Parameter Unit Cell 1 Cell3 Cell 24 Remark

T1 Cell-specific RS EPRE dBm/15kHz -60 OFF -
Srxlev* dB 50 - -
RF Signal level dBm - - -80
C1 - - - 21
T2 Cell-specific RS EPRE dBm/15kHz -60 -80 -
Qrxlevmin dBm -110 -110 -
Srxlev* dB 50 30 -
RF Signal level dBm - - -80
C1 dB - - 21
ETSI

U–S Message
table 6.2.2.18.3.2-1
next 75 s (70 s+T_reselect)?
table 6.2.2.18.3.2-1
Cell 3?
Table 6.2.3.18.3.3-1 Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24

THRESH_Priority_Search ‘0000’B Actual value=0
}
SEQUENCE {
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
E-UTRAN_PRIORITY ‘111’B Actual value=7
}
{
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
E-UTRAN_PRIORITY ‘101’B Actual value=5
}
Repeated E-UTRAN Not Allowed Cells struct > ::=
{
Not Allowed Cells : < PCID Group IE >>{
PCID} ‘000000000’B PCID=0, Meaning
that the Cell 1 which
have PCID=0 will not
be allowed
E-UTRAN_FREQUENCY_INDEX ‘000’B Cell 1
}
6.2.3.19 Redirection to E-UTRA upon the release of the CS connection

(1)
with { UE in CS Active state }
ETSI
ensure that {
when { UE receives CHANNEL RELEASE message including an IE Cell selection indicator after release
of all TCH and SDCCH,including E-UTRAN carrier frequency of Cell 1}
then { UE enters RRC_IDLE state on E-UTRAN Carrier included in IE Cell selection indicator info }
}
References: The conformance requirements covered in the current TC are specified in: TS 44.018, clause 3.4.13.1.1,
and TS 45.008, clause 6.7.1.
[TS 44.018, clause 3.4.13.1.1]
The CHANNEL RELEASE message may include the information element "Cell selection indicator after release of all
TCH and SDCCH" which shall be used by the mobile station in its cell selection algorithm after release of all TCH and
SDCCH (see 3GPP TS 45.008).
The CHANNEL RELEASE message may include Individual priorities IE to convey individual priorities information to
the MS (see subclause 3.2.4). When the MS receives an Individual priorities IE it shall start an instance of timer T3230
with the value supplied in the Individual priorities IE.
[TS 45.008, clause 6.7.1]
In A/Gb mode, when the MS releases all TCHs or SDCCH and returns to idle mode, packet idle mode or MAC-Idle
state, it shall, as quickly as possible, camp on the cell whose channel has just been released. Similarly in Iu mode, when
the MS releases all DBPSCHs and returns to MAC-Idle state, it shall, as quickly as possible, camp on the cell whose
channel has just been released. However, in both modes (A/Gb mode or Iu mode), if the CHANNEL RELEASE
message contains a “cell selection indicator after release of all TCH and SDCCH” (see TS 44.018), the MS shall as
quickly as possible camp on an indicated GSM, UTRAN or E-UTRAN cell that has been identified by the CHANNEL
RELEASE message. If UTRAN or E-UTRAN frequency only is indicated the MS shall as quickly as possible camp on
a suitable cell of this frequency.
In case the “cell selection indicator after release of all TCHs and SDCCH” is not present, then if the full (P)BCCH data
for that cell was not decoded in the preceding 30s, the MS shall attempt to decode the full (P)BCCH data. Until the MS
has decoded the (P)BCCH data required for determining the paging group, it shall also monitor all paging blocks on
timeslot 0 of the BCCH carrier or, for GPRS if PCCCH exists and for Iu mode, on the PDCH indicated on BCCH for
possible paging messages that might address it. If the MS receives a page before having decoded the full (P)BCCH data
for the cell, the MS shall store the page and respond once the relevant (P)BCCH data has been decoded, provided that
the cell is not barred and the MS's access class is allowed. Reception of full BCCH(BA) information is not required
before responding to the page.
If the CHANNEL RELEASE does not contain a “cell selection indicator after release of all TCH and SDCCH”, and the
MS has the knowledge that the cell whose channel is being released is not suitable (see 3GPP TS 43.022), the MS is
allowed to camp on any suitable cell.
If the CHANNEL RELEASE contains a “cell selection indicator after release of all TCH and SDCCH” and
- the MS cannot find a suitable cell from the indicated ones within 10 s, or
- none of the indicated cells are suitable,
the MS is allowed to camp on any suitable cell.
NOTE: The received signal level measurements on surrounding cells made during the last 5 seconds on the TCH
or SDCCH in A/Gb mode, or on the DBPSCH in Iu mode, may be averaged and used, where possible, to
speed up the process. However, it should be noted that the received signal level monitoring while on the
TCH or SDCCH in A/Gb mode, or on the DBPSCH in Iu mode, is on carriers in BA (SACCH), while the
carriers to be monitored for cell reselection are in BA (BCCH) or BA (GPRS).
After decoding the relevant (P)BCCH data the MS shall perform cell reselection as specified in 3GPP TS 43.022.
ETSI
System Simulator:
- 2 cells, one GSM and one E-UTRA cell:
- Cell 24 GSM serving cell
UE:
None
Preamble:
U10 Active state on cell 24.as per TS 51.010 clause 40.4.3.22

U–S Message
1 SS initiate a disconnect call <-- DISCONNECT - -
2 UE sends RELEASE message --> RELEASE - -
3 SS sends RELEASE COMPLETE message <-- RELEASE COMPLETE - -
4 The SS transmits an CHANNEL RELEASE <-- CHANNEL RELEASE - -
message with IE, Cell selection indicator after
release of all TCH and SDCCH including E-
UTRAN carrier frequency of Cell 1
Cell 1?
6.2.3.19.3.3 Specific message or IE contents
Table 6.2.3.19.3.3-1: Channel Release message (step 4, Table 6.2.3.19.3.2-1]

Protocol Discriminator 0110 RR Management
Skip Indicator 0000
Message Type 00001101
RR Cause
- RR Cause Value Normal event.
<Cell Selection Indicator after release of all TCH and
SDCCH IE > ::=
E-UTRAN Description 011 { 1 <E-UTRAN
Description : < E-
UTRAN Description
struct >> }
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
TARGET_PCID Same as cell 1
ETSI
6.2.3.20 Void
6.2.3.21 Inter-RAT cell reselection / From GPRS Packet_Transfer (NC0 mode) to E-
UTRA
(1)
with { UE in GPRS Registered state with active packet data transfer in NC0 mode }
ensure that {
}
44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 10.1.3.3]
The algorithm in this subclause shall be used for inter-RAT cell reselection if priority information is available to the MS
and threshold information is provided by the network. The network shall provide priority information if E-UTRAN
frequencies are included in the neighbour cell list. The mobile station may apply either priorities broadcast in system
information or individual priorities received through dedicated signalling. The rules regarding which set of priorities
shall apply are defined in 3GPP TS 44.018 and 3GPP TS 44.060.
NOTE: Throughout the specification, the phrase “neighbour cell list” will include also the E-UTRAN Neighbour
Cell list and/or the GPRS E-UTRANNeighbour Cell list where appropriate.
If the GPRS 3G Cell Reselection list or the GPRS E-UTRAN Neighbour Cell list include frequencies of other radio
access technologies, the MS shall, at least every 5 seconds update the value RLA_P for the serving cell and each of the
at least 6 strongest non serving GSM cells.
The MS shall then reselect a suitable (see 3GPP TS 25.304 for UTRAN and 3GPP TS 36.304 for E-UTRAN) cell of
another radio access technology if the criteria below are satisfied. S_non-serving_XXX is the measurement quantity of
a non-serving inter-RAT cell and XXX indicates the other radio access technology/mode. S_non-serving_XXX is
defined in subclause 6.6.6.
THRESH_XXX_high during a time interval T_reselection; in that case, the mobile station shall consider the
cells for reselection in decreasing order of priority and, for cells of the same inter-RAT frequency, in decreasing
order of S_non-serving_XXX, and reselect the first cell that satisfies the conditions above;
- The value of S_serving is lower than THRESH_serving_low for the serving cell and all measured GSM cells; in
this case, the mobile station shall consider for reselection the inter-RAT cells in the following order, and reselect
the first one that satisfies the following criteria:

THRESH_XXX_low during a time interval T_reselection; these cells shall be considered in decreasing order
of priority and, for cells of the same RAT, in decreasing order of S_non-serving_XXX;
- if no cells satisfy the criterion above, inter-RAT cells for which, during a time interval T_reselection, S_non-
serving_XXX is higher than S_serving by at least a specific hysteresis H_PRIO; these cells shall be
considered in decreasing order of S_non-serving_XXX.
A UTRAN FDD cell shall only be reselected if, in addition to the criteria above, its measured Ec/No value is equal to or
greater than FDD_Qmin - FDD_Qmin_Offset..
Cell reselection to a cell of another radio access technology (e.g. UTRAN or E-UTRAN) shall not occur within [5]
seconds after the MS has reselected a GSM cell from an inter-RAT cell if a suitable GSM cell can be found.
ETSI
If the mobile station applies individual priorities received through dedicated signalling and priority information is
available only for some inter-RAT frequencies, cells belonging to frequencies for which no individual priority is
available or no threshold is broadcast in system information shall not be considered for measurement and for cell re-
selection.
If a mobile station in camped normally state (see 3GPP TS 43.022) applies individual priorities received through
dedicated signalling and no priority is available for the serving cell, the mobile station shall consider any GSM cell
(including the serving cell) to have lowest priority (i.e. lower than the eight network configured values).
A mobile station in camped on any cell state (see 3GPP TS 43.022) shall ignore individual priorities received through
dedicated signalling and shall apply priorities received from the system information of the serving cell while attempting
to find a suitable cell. If the mobile station supports CS voice services, the MS shall avoid reselecting acceptable (but
not suitable) E-UTRA cells regardless of the priorities provided in system information.
NOTE: If the MS is camping on an acceptable cell, individual priorities are not discarded until an event leading to
their deletion occurs.
In case of a reselection attempt towards a barred UTRAN cell, the MS shall abandon further reselection attempts
towards this UTRAN cell as defined by the Tbarred value on the barred UTRAN cell (see 3GPP TS 25.331).
NOTE: It is FFS whether a similar requirement should be added in case of a reselection attempt towards a barred
E-UTRAN cell.
NOTE: Requirements for cells belonging to “forbidden LAs for roaming” should be included here.
[TS 44.018, clause 3.4.1.2.1.1a]
System Simulator:
2 cells, one GSM and one E-UTRA cell:
- Cell 24 GSM serving cell
- Cell 1 suitable neighbour E-UTRA cell Cell 1 is off.
UE:
None.
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to [23].
ETSI

T1 Srxlev* dB 30 SrxlevCell 1 >THRESH_E-
UTRAN_high

U -- S Message
1 UE is brought into downlink packet transfer - - - -
mode
- EXCEPTION: Step 2 is repeated 5 times. - - - -
2 The SS sends one downlink data block - - -
3 Void - - -
row T1 of table 6.2.3.21.3.2-1
- EXCEPTION: Step 5 is repeated until the - - - -
parallel behaviour in table 6.2.3.21.3.2-3 takes
place.
5 The SS sends one downlink data block - - -
Table 6.2.3.21.3.2-3: Parallel behaviour

U -- S Message
Cell 1?
Table 6.2.3.21.3.3-1: Void
6.2.3.22 Void
6.2.3.23 Inter-RAT Cell Reselection from GPRS Packet transfer to E-UTRA in CCN
Mode (PACKET CELL CHANGE CONTINUE)
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell and in CCN mode }
then { UE leaves CCN mode, reselects the E-UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008 section 6.6.6,
10.1.3.3,10.1.4 and TS44.060 section 5.5.1.1a.2 and 5.5.2.3
[TS 45.008, section 6.6.6 and 10.1.3.3]
The algorithm in this subclause shall be used for inter-RAT cell reselection if priorities are available to the MS and
thresholds are provided by the network, and if the mobile station supports priority based inter-RAT cell re-selection and
priority information for the serving cell is provided by the network. A mobile station supporting E-UTRAN shall
support priority based inter-RAT cell re-selection towards all the supported RATs. A mobile station not supporting E-
ETSI
UTRAN and supporting UTRAN and supporting priority based reselection from UTRAN to GERAN shall support
priority based inter-RAT cell re-selection towards UTRAN
The network shall provide priority information if E-UTRAN frequencies are included in the neighbour cell list. If
priority information is available to the mobile station and the mobile station supports priority based inter-RAT cell re-
selection, the algorithm in this subclause shall be used for inter-RAT reselection towards all RATs.
If the 3G Cell Reselection list or the E-UTRAN Neighbour Cell list include frequencies of other radio access
technologies, the MS shall, at least every 5 s update the value RLA_C for the serving cell and each of the at least 6
strongest non serving GSM cells.
a non-serving inter-RAT cell and XXX indicates the other radio access technology/mode and is defined as follows:
- for a E-UTRAN cell, is the measured RSRP value for the cell minus E-UTRAN_QRXLEVMIN for the cell’s
frequency if THRESH_E-UTRAN_high_Q is not provided; otherwise, if THRESH_E-UTRAN_high_Q is provided, is
the measured RSRQ value for the cell minus E-UTRAN_QQUALMIN for the cell’s frequency.
[TS 45.008, clause 10.1.4]
The network may request measurement reports from the MS and control its cell re-selection. This is indicated by the
parameter NETWORK_CONTROL_ORDER. The meaning of the different parameter values is specified as follows:
NC0 Normal MS control

The MS shall perform autonomous cell re-selection.
NC1 MS control with measurement reports

The MS shall send measurement reports to the network as defined in subclause 10.1.4.1.
NC2 Network control

The MS shall only perform autonomous cell re-selection when the reselection is triggered by a
downlink signalling failure as defined in subclause 6.5 or a random access failure as defined in
3GPP TS 44.018 and 3GPP TS 44.060 or if the cell is barred or the C1 criterion falls below zero.
The MS shall only determine whether the cell is barred once camped on the cell.
RESET The MS shall return to the broadcast parameters. Only sent on PCCCH or PACCH.
All signalling for support of network controlled cell re-selection and measurement reports are defined in 3GPP TS
44.060 section 5.5.1.1a.2 and 5.5.2.3.
System Simulator:
- Cell 24 is serving GERAN Cell
- Cell 1 is OFF
UE:
None.
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to section 41.2.8.1.1 and 40.4.3.15 of
TS51010-1
ETSI
Parameter Unit Cell 1 Cell24 Remark

No change The power level is
T1 Cell-specific RS EPRE dBm/15kHz -60 such that
SrxlevCell 1 > 0

U-S Message
1 Uplink dynamic allocation two phase access - - - -
according to TS 51.010 clause 40.4.3.9 using
n=5000 octets of data
2 EXCEPTION: MS continues to transfer data - - - -
and send measurement reports for cell 1 in
PACKET MEASUREMENT REPORT in
parallel to steps 3 to 4
row T1 of table 6.2.3.23.3.2-1
4 The UE transmits PACKET CELL CHANGE --> PACKET CELL CHANGE
NOTIFICATION to E_UTRA cell on 24 NOTIFICATION
5 The SS sends PACKET CELL CHANGE <-- PACKET CELL CHANGE - -
CONTINUE for cell 1 as the target cell on cell CONTINUE
24
6 Check: Does UE send RRC CONNECTION --> RRCConnectionRequest 1 P
REQUEST on cell1?
7 SS sends RRCConnectionSetup to the UE <-- RRCConnectionSetup - -
8 Check: Does the UE send --> RRCConnectionSetupComplete 1 P
RRCConnectionSetupComplete message on
cell 1?
ETSI
Table 6.2.3.23.3.3-1: SI2Quater for Cell 24[Preamble]

NC Measurement parameters ::={
NETWORK_CONTROL_ORDER ‘01’B NC1
NC_REPORTING_PERIOD_I ‘111’B 61.44 sec
NC_REPORTING_PERIOD_T ‘111’B 61.44 sec
}
Serving Cell Priority Parameters ::= {
GERAN_PRIORITY ‘001’B This filed specifies
GERAN cell priority
}
E-UTRAN Measurement Parameters Description ::=
{
Qsearch_C_E-UTRAN_Initial ‘0111’ B This filed indicates
the Qsearch value to
be used in dedicated
/ dual transfer mode
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
cells if signal level
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
E-UTRAN_REP_QUANT ‘0’ B This filed indicates
the reporting quantity
for
E-UTRAN cells
E-UTRAN_MULTIRAT_REPORTING ‘01’ B This field indicates
the number of cells
that shall be included
in the list of strongest
cells or in the
measurement report.
}
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
E-UTRAN_PRIORITY ‘100’B Same as cell 1
}
E-UTRAN Parameters Description struct ::= {
E-UTRAN_CCN_ACTIVE 1 CCN is enabled in
the cell
}
Table 6.2.3.23.3.3-2: PACKET CELL CHANGE CONTINUE (step 5, Table 6.2.3.23.3.3-2)

Packet Cell Change Continue message content ::=
PAGE_MODE ‘00’B Normal Paging
Global TFI TFI of the uplink TBF
ETSI
Table 6.2.3.23.3.3-3: SI 13 for Cell 24 (Preamble)

6.2.3.24 Inter-RAT Cell Reselection from GPRS Packet transfer to E-UTRA in CCN
Mode (PACKET CELL CHANGE ORDER)
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell and in CCN mode }
then { UE leaves CCN mode,reselects the E-UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008 section 6.6.6,
10.1.3.3,10.1.4 and TS 44.060 section 5.5.1.1a.2 and 5.5.2.3
[TS 44.060, section 5.5.1.1a.2]
A mobile station, which has CCN Enabled, can enter CCN Mode.
The mobile station shall enable CCN when the following criteria are fulfilled:
- the mobile station is camping on a cell (see 3GPP TS 45.008); and
- the network indicates CCN ACTIVE/3G CCN ACTIVE/E-UTRAN CCN ACTIVE either in system information
to all mobile stations in the cell or in an individual order to a certain mobile station; and
- the mobile station is neither in dedicated mode nor Dual Transfer Mode; and
- the mobile station is in NC0 or in NC1 mode; and
- the mobile station is in Packet Transfer mode.
The CCN procedures and the criteria for entering and leaving CCN mode are specified in sub-clauses 8.8.2 and 8.8.3.
[TS 45.008, section 6.6.6 and 10.1.3.3]
ETSI
[TS 45.008, clause 10.1.4]


NC2 Network control

44.060 section 5.5.1.1a.2 and 5.5.2.3.
System Simulator:
- Cell 1 is OFF
UE:
None.
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to section 41.2.8.1.1 and 40.4.3.15 of TS
51010-1

Same as The power level is
T1 Cell-specific RS EPRE dBm/15kHz -60 before such that
SrxlevCell 1 > 0
ETSI

U-S Message
- EXCEPTION: MS continues to transfer data in - - - -
parallel to steps 2 to 4
row T1 of table 6.2.3.24.3.2-1
NOTIFICATION to E_UTRA cell on 24 NOTIFICATION
4 The SS sends PACKET CELL CHANGE <-- PACKET CELL CHANGE ORDER - -
ORDER for cell 1 as the target cell on cell 24
REQUEST on cell1?
6 SS sends RRCConnectionSetup to the UE <-- RRCConnectionSetup - -
7 Check: Does the UE send --> RRCConnectionSetupComplete 1 P
cell 1?
Table 6.2.3.24.3.3-1 Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24[Preamble]

Serving Cell Priority Parameters ::=
{
GERAN cell priority
}
{
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
}
E-UTRAN Parameters Description struct ::=
{
the cell
}
ETSI
Table 6.2.3.24.3.3-2: PACKET CELL CHANGE ORDER (step 5, Table 6.2.3.24.3.2-2)
Information element Value/remark

< PAGE_MODE : bit (2) > 00 (Normal Paging)
0 | 10 0
< GLOBAL_TFI : Global TFI IE > <5 bit Uplink TFI>
0|1 1
Message Escape 00
< IMMEDIATE_REL > 1 (Immediate abort of operation in the old cell is required)
0|1<UTRAN FDD Target cell IE> 0 (not present )
0|1<UTRAN TDD Target cell IE> 0 (not present )
Additions in Rel-5 1
0 | 1 < G-RNTI extension 0 (not present )
Additions in Rel-8 1
0|1<E-UTRAN Target cell IE> 1
EARFCN EARFCN of the cell 1
0 | 1 < Measurement Bandwidth 0 (not present )
Physical Layer Cell identity PCID of the cell 1
0 | 1 < Individual Priorities 0 (not present )
6.2.3.25 Void
6.2.3.26 Inter-RAT Autonomous Cell Reselection GPRS Packet_transfer to E-UTRA
(NC1 mode)
(1)
ensure that {
priority inter-RAT E-UTRA cell }
then { UE performs autonomous,reselection to the E-UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008 section 6.6.6, 10.1.3.3
and 10.1.4:
[TS 45.008, section 6.6.6 and 10.1.3.3]
ETSI
[TS 45.008, clause 10.1.4]


NC2 Network control

44.060 section 5.5.1.1a.2 and 5.5.2.3.
System Simulator:
- Cell 1 is suitable E-UTRAN Cell
UE:
None.
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to section 41.2.8.1.1 and 40.4.3.15 of TS
51.010-1
Tables 6.2.3.26.3.2-1& 6.2.3.26.3.2-2 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 the
preamble, while rows marked "T1" are to be applied subsequently. The exact instants on which these values shall be
applied are described in the texts in this clause.

Cell-specific RS EPRE dBm/15kHz OFF
T0 Qrxlevmin dBm -106
Srxlev* dB N/A
T1 Srxlev* dB 30 SrxlevCell 1 >THRESH_E-
UTRAN_high
ETSI

RF Signal Level dBm -80 Camping on Cell 24 is guaranteed
T0 RXLEV_ACCESS_MIN dBm -101
C1* dB 21
RF Signal Level dBm Same as before
T1 RXLEV_ACCESS_MIN dBm Sa me as before
C1* dB Same as before

U-S Message
1 Downlink TBF is established according to TS - - - -
51.010 clause 40.4.3.14
- EXCEPTION: Steps 2 and 3 are repeated until - - - -
measurement results for cell 1 are included in
PACKET MEASUREMENT REPORT
2 SS sends downlink data <--
3 UE sends PACKET MEASUREMENT --> PACKET MEASUREMENT
REPORT REPORT
row T1 of table 6.2.3.26.3.2-1
- EXCEPTION: Steps 5 and 6 are repeated until - - - -
the parallel behaviour in table 6.2.3.26.3.2-3
takes place
5 SS sends downlink data
6 UE sends PACKET MEASUREMENT --> PACKET MEASUREMENT
REPORT REPORT

U-S Message
Cell 1?
ETSI
Table 6.2.3.26.3.3-1: Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24[Preamble]

Serving Cell Priority Parameters ::= {
GERAN cell priority
}
{
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
for
E-UTRAN cells
the number of cells
cells or in the
measurement report.
}
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
}
ETSI
Table 6.2.3.26.3.3-2: Message ATTACH REQUEST (Preamble)
Derivation Path: Table 9.4.1/3GPP TS 24.008

MS Radio Access capability
E-UTRA FDD support ‘0’B or ‘1’B C1
E-UTRA TDD support ‘0’B or ‘1’B C1
GERAN to E-UTRA support in GERAN packet ‘10’B or ‘11’B UTRAN Neighbour
transfer mode Cell measurements
and MS autonomous
cell reselection to E-
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN
C1 At least one of these fields shall be set to ‘1’B
6.2.3.27 Inter-RAT Cell selection from GPRS Packet_transfer to E-UTRA (NC2 Mode)
(1) with { UE in GPRS Registered state with active packet data transfer in NC2 mode }
ensure that {
when { UE detects network re-selection criteria are met on the E-UTRA cell}
then { UE performs cell change to E-UTRA cell and the data transfer is continued and completed
in E-UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.4, 10.1.4,
10.1.4.1 and 10.1.4.2, TS 44.018, clause 3.4.1.2.1.1a:
[TS 45.008, clause 6.4]
C1 = (A - Max(B,0))
where

system.
[TS 45.008, clause 10.1.4]
ETSI


NC2 Network control

A list given by Packet Cell Change Order applies in the new cell. This list may also include cells with other radio access
technologies.
44.060.
If the MS operates in NC2 mode, the following rules shall be applied:
- The network controls the measurements of UTRAN cells by the parameter Qsearch_P. The network controls the
measurements of E-UTRAN cells by the parameter Qsearch_P_E-UTRAN.
- The network may control UTRAN measurements per individual UTRAN frequency by the parameters
Measurement_Control_UTRAN and E-UTRAN measurements per individual E-UTRAN frequency by the
parameters Measurement_Control_E-UTRAN.
[TS 45.008, clause 10.1.4.1]
When ordered to send measurement reports, the MS shall continuously monitor all carriers in BA(GPRS) or as
indicated by the parameter NC_FREQUENCY_LIST and the BCCH carrier of the serving cell. The measurement
requirements are defined in subclause 10.1.1 for the actual packet mode
[TS 44.018, clause 3.4.1.2.1.1a]
fast acquisition of system information procedure, as defined in subclause 3.4.1.2.1.11, shall be used to acquire E-
UTRAN measurement parameters and neighbour cell information from SI2quater and MEASUREMENT
INFORMATION.
System Simulator:
- 2 Cells, one GSM and one E-UTRA:
-Cell 24 GSM serving cell
-Cell 1 non-suitable “Off” cell
UE:
- None
ETSI
Preamble:
- The UE is GPRS attached to the home PLMN and the PDP context 2 activated according to TS 51.010-1 clause
40.4.3.15.
Table 6.2.3.27.3.2-1: Time instances of cell power level and parameter changes (E-UTRA and GERAN
cell)

Cell-specific RS EPRE dBm/15kHz -70 - SrxlevCell1 > 0
T1 Qrxlevminoffset dB 0 - -
Pcompensation dB 0 - -
C1* dB - <0 Cell 24 become
weakest cell
C1 is calculated in the UE

U-S Message
1 Uplink dynamic allocation two phase access --> - - -
n=1500 octets of data.
2 The UE transmits PACKET MEASUREMENT --> PACKET MEASUREMENT - -
REPORT REPORT
table 6.2.3.27.3.2-1.
- EXCEPTION: Step 2 is repeated until - - - -
the PACKET MEASUREMENT REPORT
message in step 4. SS continues to transfer
data in parallel of step 4.
4 The UE transmits PACKET MEASUREMENT --> PACKET MEASUREMENT - -
REPORT for cell 1 are included in the REPORT
PACKET MEASUREMENT REPORT message
REQUEST on cell 1?
6 SS sends RRCCconnectionSetup to the UE <-- RRCCconnectionSetup - -
7 Check: Does the UE send --> RRCCconnectionSetupComplete 1 P
RRCCconnectionSetupComplete message on NAS: TRACKING AREA UPDATE
cell 1? REQUEST
8- Steps 4 to 7 from generic prodedure 36.508 - - - -
11 Table 6.4.2.7A-1 are executed
{How to handle data from GERAN to E- - - - -
UTRAN is under FFS}
ETSI
Table 6.2.3.27.3.3-1: SI2Quater for Cell 24 (Preamble)
Derivation Path: 44.018 Table 10.5.2.33b.1

Serving Cell Priority Parameters Description::=
SEQUENCE {
GERAN_PRIORITY 7
THRESH_GSM_low 0(-98 dBm)
H_PRIO 0 Hysteresis used in
the priority
reselection algorithm
T_Reselection 3(=20 seconds) Time hysteresis in
the reselection
algorithm
}
{
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
for
E-UTRAN cells
the number of cells
cells or in the
measurement report.
}
SEQUENCE {
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
}
ETSI

and MS autonomous
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN
Table 6.2.3.27.3.3-3: RRCConnectionRequest (step 5, Table 6.2.3.27.3.2-2)

ue-Identity Any allowed value
6.2.3.28 Inter-RAT Cell Reselection from GPRS Packet_transfer to E-UTRA (Network

Assisted Cell Change)
(1) with { UE in GPRS Registered state with active packet data transfer in NC2 mode }
ensure that {
when { UE detects network assisted cell change and the target E-UTRA cell}
then { UE reselects for the target E-UTRA cell}
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 10.1.4,
10.1.4.1 and 10.1.4.2, TS 44.018, clause 3.4.1.2.1.1a:
[TS 45.008, clause 10.1.4]


NC2 Network control

ETSI
technologies.
44.060.
[TS 45.008, clause 10.1.4.1]
[TS 45.008, clause 10.1.4.2]
A cell re-selection command may be sent from the network to an MS. When the MS receives the command, it shall re-
select the cell according to the included cell description and change the network control mode according to the
command (see 3GPP TS 44.060). The command may include re-selection of another radio access technology/mode.
[TS 44.018, clause 3.4.1.2.1.1a]
fast acquisition of system information procedure, as defined in subclause 3.4.1.2.1.11, shall be used to acquire E-
UTRAN measurement parameters and neighbour cell information from SI2quater and MEASUREMENT
INFORMATION.
System Simulator:
UE:
Preamble:
- The UE is GPRS attached to the home PLMN and the PDP context 2 activated according to [23].
Tables 6.2.3.28.3.2-1 & 6.2.3.28.3.2-2 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
the preamble, while rows marked "T1" are to be applied subsequently. The exact instants on which these values shall be
ETSI
Table 6.2.3.28.3.2-1: Time instances of cell power level and parameter changes for the E-UTRA cell

Qrxlevmin dBm -106
T0
Pcompensation dB 0
Cell-specific RS EPRE dBm/15kHz -70 SrxlevCell1 > 0
Qrxlevmin dBm -106
T1
Pcompensation dB 0
Table 6.2.3.28.3.2-2: Time instances of cell power level and parameter changes for the GERAN cell

C1* dB 21
RF Signal Level dBm -80
C1* dB 21

U-S Message
1 UE is brought into downlink packet transfer <-- PACKET DOWNLINK - -
mode . SS sends PACKET DOWNLINK ASSIGNMENT
ASSIGNMENT
2 SS sends PACKET MEASUREMENT ORDER <-- PACKET MEASUREMENT - -
ORDER
3 SS sends downlink data <-- - - -
4 The UE transmits PACKET MEASUREMENT --> PACKET MEASUREMENT
REPORT REPORT
tables 6.2.3.28.3.2-1 and 6.2.3.28.3.2-2.
6 EXCEPTION: Step 3 to 4 are repeated until - - - -
message
7 SS sends PACKET CELL CHANGE ORDER <-- PACKET CELL CHANGE ORDER - -
for cell 1 as the target cell
REQUEST on cell 1?
9 SS sends RRCCconnectionSetup to the UE <-- RRCCconnectionSetup - -
10 Check: Does the UE send --> RRCCconnectionSetupComplete 1 P
RRCCconnectionSetupComplete message on
cell 1?
ETSI
Table 6.2.3.28.3.3-1: SI2Quater for Cell 24 (Preamble)

{
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
for
E-UTRAN cells
the number of cells
cells or in the
measurement report.
}
SEQUENCE {
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
}

and MS autonomous
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN
ETSI
Table 6.2.3.28.3.3-3: Message PACKET MEASUREMENT ORDER (step 2, Table 6.2.3.28.3.2-3)
Derivation Path: 44.060 Table 11.2.9b.1

MESSAGE TYPE ‘000011’ B
PAGE MODE ‘00’ B
PMO_INDEX ‘000’B
PMO_COUNT ‘000’B
}
NC_FREQUENCY_LIST 0 Not present
E-UTRAN Parameters Description ::= {
the cell
GPRS E-UTRAN Measurement Parameters struct
::= {
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
for
E-UTRAN cells
the number of cells
cells or in the
measurement report.
}
}
SEQUENCE {
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
}
ETSI
Table 6.2.3.28.3.3-4: Message PACKET CELL CHANGE ORDER (step 7, Table 6.2.3.28.3.2-3)

IMMEDIATE_REL 1
E-UTRAN Target cell IE
EARFCN specified for cell 1
Physical Layer Cell Identity specified for cell 1

6.2.3.29 Inter-RAT cell Reselection from GPRS packet_transfer to E-UTRA in CCN

mode (PACKET MEASUREMENT ORDER)
(1)
with { UE in GPRS packet_transfer state with active data transfer in NC1 mode }
ensure that {
when { UE with CCN enable detects E-UTRA cell, enters CCN mode, receives PACKET MEASUREMENT
ORDER to enter NC2 and subsequently receives PACKET CELL CHANGE ORDER }
then { UE does not perform autonomous reselection, but performs cell change to E-UTRA cell
only on receipt of PACKET CELL CHANGE ORDER }
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.6.6, 10.1.4,
10.1.4.1, 10.1.4.2, TS 44.060 clause 5.5.1.1a.2, and TS 36.331 clause 5.4.6.2:
[TS 45.008, clause 6.6.6]
priority based inter-RAT cell re-selection towards UTRAN.
The network shall provide priority information if E-UTRAN frequencies are included in the neighbour cell list; the
network may provide priority information if only UTRAN frequencies are included in the neighbour cell list. If priority
information is available to the mobile station and the mobile station supports priority based inter-RAT cell re-selection,
the algorithm in this subclause shall be used for inter-RAT reselection towards all RATs. The rules regarding which set
of priorities is valid at any given time are defined in 3GPP TS 44.018.
NOTE 1: “Priority information” includes priorities and thresholds which are related to each UTRAN or E-UTRAN
frequency (e.g. UTRAN_PRIORITY, E-UTRAN_PRIORITY, THRESH_UTRAN_high, THRESH_E-
UTRAN_high) and information related to the serving cell (e.g. GERAN_PRIORITY,
THRESH_GSM_low).
NOTE 2: Throughout the specification, the phrase “neighbour cell list” will include also the E-UTRAN Neighbour
Cell list where appropriate.
NOTE 3: Priorities need to be provided also for frequencies of networks that do not support priority-based cell
reselection.
ETSI
- for a UTRAN cell, is the measured RSCP value for the cell minus UTRAN_QRXLEVMIN for the cell’s
frequency;
frequency if THRESH_E-UTRAN_high_Q is not provided; otherwise, if THRESH_E-UTRAN_high_Q is
provided, is the measured RSRQ value for the cell minus E-UTRAN_QQUALMIN for the cell’s frequency.
[TS 45.008, clause 10.1.4]


NC2 Network control

technologies.
44.060.
[TS 45.008, clause 10.1.4.1]
[TS 45.008, clause 10.1.4.2]
[TS 44.060, clause 5.5.1.1a.2]
A mobile station, which has CCN Enabled, can enter CCN Mode.
The mobile station shall enable CCN when the following criteria are fulfilled:
- the mobile station is camping on a cell (see 3GPP TS 45.008); and
- the network indicates CCN ACTIVE/3G CCN ACTIVE/E-UTRAN CCN ACTIVE either in system information
to all mobile stations in the cell or in an individual order to a certain mobile station; and
- the mobile station is neither in dedicated mode nor Dual Transfer Mode; and
ETSI
- the mobile station is in NC0 or in NC1 mode; and
- the mobile station is in Packet Transfer mode.
The CCN procedures and the criteria for entering and leaving CCN mode are specified in sub-clauses 8.8.2 and 8.8.3.
[TS 36.331, clause 5.4.6.2]
The procedure is initiated when a radio access technology other than E-UTRAN, e.g. GSM/GPRS, using procedures
specific for that RAT, orders the UE to change to an E-UTRAN cell. In response, upper layers request the establishment
of an RRC connection as specified in subclause 5.3.3.
NOTE: Within the message used to order the UE to change to an E-UTRAN cell, the source RAT should specify
the identity of the target E-UTRAN cell as specified in the specifications for that RAT.
The UE shall:
1> upon receiving an RRCConnectionSetup message:
2> consider the inter-RAT cell change order procedure to have completed successfully;
System Simulator:
- GERAN Cell 24 serving cell
- E-UTRAN Cell 1 off
UE:
None
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to section 40.4.3.15 of TS51010-1
Table 6.2.3.29.3.2-1: Time instances of cell power level and parameter changes (GERAN and E-UTRA
cells)

No change The power level is
T1 Cell-specific RS EPRE dBm/15kHz -60 such that
SrxlevCell 1 > 0
ETSI

U-S Message
- UE continues to transfer data. See Note. - - - -
row T1 of table 6.2.3.29.3.2-1
NOTIFICATION to E_UTRA cell on cell 24 NOTIFICATION
4 SS sends PACKET MEASUREMENT ORDER <-- PACKET MEASUREMENT
activating NC2 ORDER
5 The UE moves out of CCN mode and does not --> RRCConnectionRequest 1 F
perform cell reselection
Check: Does UE send
RRCConnectionRequest on cell 1?
6 The UE sends PACKET MEASUREMENT --> PACKET MEASUREMENT - -
REPORT including the Cell 1 information in the REPORT
message.
7 SS sends PACKET CELL CHANGE ORDER <-- PACKET CELL CHANGE ORDER
8 Check: Does UE send --> RRCConnectionRequest 1 P
RRCConnectionRequest on cell 1?
9- Steps 2 to 7 from generic prodedure 36.508 - - - -
14 Table 6.4.2.7A-1 are executed
Note: Uplink data transfer can be completed in any step after step 4 and before step 7 in Cell 24, or any step after
step 7 in Cell 1
ETSI
Table 6.2.3.29.3.3-1: Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24 (Preamble)

Serving Cell Priority Parameters ::=
GERAN_PRIORITY ‘001’B This field specifies
GERAN cell priority
E-UTRAN Parameters Description ::=
the cell
{
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
for
E-UTRAN cells
the number of cells
cells or in the
measurement report.
}
{
}
Table 6.2.3.29.3.3-2 Message ATTACH REQUEST (Preamble)

and MS autonomous
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN
..E-UTRA TDD support ‘0’B or ‘1’B C1
ETSI

}

IMMEDIATE_REL 1
6.2.3.30 Inter-RAT Cell Reselection failure from GPRS Packet transfer to E-UTRA
(Network Assisted Cell Change)
(1)
ensure that {
when { UE detects network assisted cell change and cell re-selection failure for the target E-UTRA
cell}
then { UE reselects back the GERAN cell and downlink data transfer is continued and completed in
GERAN cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 10.1.4, and
10.1.4.2:
[TS 45.008, clause 10.1.4]


NC2 Network control

ETSI
technologies.
44.060.
[TS 45.008, clause 10.1.4.2]
If a UTRAN capable MS receives a cell re-selection command towards a not known UTRAN cell (see 3GPP TS 25.133
and 3GPP TS 25.123), or if a E-UTRAN capable MS receives a cell re-selection command towards a not known E-
UTRAN cell (see 3GPP TS 36.133), then the MS shall search for synchronisation information up to 800 ms. In case of
failure, the MS shall return to the old cell and indicate a packet cell change failure (see 3GPP TS 44.060).
System Simulator:
UE:
The HPLMN is PLMN1.
Preamble:
- The UE is GPRS attached to the home PLMN and the PDP context 2 activated according to [23].
Tables 6.2.3.30.3.2-1 & 6.2.3.30.3.2-2 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
the preamble, while rows marked "T1" are to be applied subsequently. The exact instants on which these values shall be

Qrxlevmin dBm -106
T0
Pcompensation dB 0
The power level is such that
SrxlevCell 1 > 0
ETSI

C1* dB 21
C1* dB 21

U-S Message
1 Downlink TBF is established according to TS - -
51.010 clause 40.4.3.14
2 SS sends PACKET MEASUREMENT ORDER <-- PACKET MEASUREMENT - -
ORDER
3 SS sends downlink data <-- - - -
4 The UE transmits PACKET MEASUREMENT --> PACKET MEASUREMENT
REPORT REPORT
row T1 of table 6.2.3.30.3.2-1
6 EXCEPTION: Step 3 to 4 are repeated until - - - -
message
7 SS sends PACKET CELL CHANGE ORDER <-- PACKET CELL CHANGE ORDER - -
8 UE sends RRCConnectionRequest to cell 1 --> RRCConnectionRequest - -
9 SS sends RRCConnectionReject to the UE <-- RRCConnectionReject - -
10 All the UL/DL messages sent in steps 11-20 - - -
shall be sent on cell 24.
11 Check: Does the UE send CHANNEL --> CHANNEL REQUEST 1 P
REQUEST ?
12 SS sends IMMEDIATE ASSIGNMENT <-- IMMEDIATE ASSIGNMENT - -
13 Check: Does the UE send PACKET CELL --> PACKET CELL CHANGE 1 P
CHANGE FAILURE? FAILURE
- EXCEPTION: Steps 14a to 14c describe - - - -
behaviour that depends on the UE capability;
the "lower case letter" identifies a step
sequence that takes place. This is checked for
a period of 1s
14a the UE transmit a ROUTING AREA UPDATE --> ROUTING AREA UPDATE - -
REQUEST message? REQUEST
14b The SS transmits a ROUTING AREA UPDATE <-- ROUTING AREA UPDATE - -
ACCEPT message. ACCEPT
14c The UE transmits a ROUTING AREA UPDATE --> ROUTING AREA UPDATE - -
COMPLETE message. COMPLETE
15 Downlink TBF is established according to TS
51.010 clause 40.4.3.14
16 SS sends downlink data until downlink <-- - - -
data transfer is complete
Note 1: GERAN cell priority is not allocated, hence it will be considered as the less than all allowed values of 1 to 8.
ETSI
Table 6.2.3.30.3.3-1: Message SI2Quater for Cell 24 (Preamble)

{
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
for
E-UTRAN cells
the number of cells
cells or in the
measurement report.
}
SEQUENCE {
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.
}

and MS autonomous
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN
ETSI

}
E-UTRAN Parameters Description ::= {
the cell
GPRS E-UTRAN Measurement Parameters struct
::= {
before
Qsearch_C_E-
UTRAN is received,
Search for E-UTRAN
below threshold (0-
7):
- 98, - 94, … , - 74
dBm, ∞ (always)
for
E-UTRAN cells
the number of cells
cells or in the
measurement report.
}
}

IMMEDIATE_REL 1

ETSI
Table 6.2.3.30.3.3-6: Message PACKET CELL CHANGE FAILURE (step 13, Table 6.2.3.30.3.2-3)

CAUSE ‘0010’B
6.2.3.31 Inter-RAT cell reselection / From UTRA_Idle (low priority) to E-UTRA

RRC_IDLE (high priority) according to RAT priority provided by dedicated
signalling
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the high
priority inter-RAT E-UTRA cell based on the configured RAT priority provided by dedicated signaling
}
}
5.2.6.1.4a; TS 25.331, clause 8.3.3.3 and 8.6.7.23; TS 36.331, clause 5.3.3.4.
[TS 25.304, clause 5.2.6.1.2a]
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
ETSI
is fulfilled.
fulfilled.
serving cell.
[TS 25.331, clause 8.3.3.3]
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:
1> act on received information elements as specified in subclause 8.6;
1> if the IE "Dedicated Priority Information" is present:
2> act upon the received IE as described in subclause 8.6.7.23.
[TS 25.331, clause 8.6.7.23]
If the CHOICE "Action" has the value "Configure dedicated priorities", the UE shall:
1> clear the variable PRIORITY_INFO_LIST;
1> stop timer T322, if it is running;
1> set the value of IE "Priority status" in the variable PRIORITY_INFO_LIST to "dedicated_priority";
1> for each occurrence of the IE "Priority Level List":
2> create a new entry in the IE "Priority Info List" in the variable PRIORITY_INFO_LIST, and in that new
entry:
3> set the CHOICE "Radio Access Technology" to the value received in the IE "Priority Level List";
3> set the IE "priority" to the value received in the IE "Priority Level List";
3> set the values in IE "Frequency List" or "BCCH ARFCN List" to the values received in the IE "Priority
Level List".
1> set the IE "E-UTRA detection" to the value received in the IE "Priority Level List".
1> if the IE "T322" is present:
2> start timer T322 using the value signalled in this IE.
1> if the UE is not in CELL_DCH state:
2> take the actions as described in subclause 8.1.1.6.19 using stored System information Block type 19.
[TS 36.331, clause 5.3.3.4]
The UE shall:
ETSI
1> stop timer T300;
...
procedure ends;
System Simulator:
NOTE: Common Priority information for Cell 1 & Cell 5: UTRA priority = 3; E-UTRA priority = 4.
UE:
None.
Preamble:
- The UE is in state PS-DCCH+DTCH_DCH (state 6-10) on Cell 5 according to [5].
Tables 6.2.3.31.3.2-1 and 6.2.3.31.3.2-2 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 conditions after the
preamble, while row marked "T1" is to be applied subsequently. The exact instants on which these values shall be

T0 Qrxlevmin dBm -106 Default value
Srxlev* dB 9
T1 Srxlev* dB 24 Srxlev = Cell-specific RS EPRE -

qRxLevMinEUTRA
S nonServingCell, Cell1 > Thresh Cell1,high
ETSI

Srxlev* dB 19
Srxlev* dB 4

U-S Message
1 The SS provides dedicated priority information <-- UTRAN MOBILITY - -
(UTRA priority = 3; E-UTRA priority = 4) and INFORMATION
validity timer to the UE.
2 The UE transmits UTRAN MOBILITY --> UTRAN MOBILITY - -
INFOMRATION CONFIRM message on Cell 5. INFORMATION CONFIRM
3 The SS transmits an RRC CONNECTION <-- RRC CONNECTION RELEASE - -

RELEASE message to release UE connection.
4 The UE transmits an RRC CONNECTION --> RRC CONNECTION RELEASE - -

RELEASE COMPLETE message on Cell 5. COMPLETE

1 and table 6.2.3.31.3.2-2.
8- Check: Does the test result of steps 1 to 7 of - - 1 -

14 the generic test procedure in TS 36.508 Table
6.4.2.7A-1 indicate that the UE is camped on
E-UTRAN Cell 1?
- At the end of this test procedure sequence, the - - - -
UE is in end state E-UTRA connected
(E2_T3440) according to TS 36.508.
ETSI
Table 6.2.3.31.3.3-1: UTRAN MOBILITY INFORMATION for Cell 5 (step 1, Table 6.2.3.31.3.2-3)

UTRANMobilityInformation ::= CHOICE {
r7 SEQUENCE {
utranMobilityInformation-v860ext SEQUENCE
{
dedicatedPriorityInformation SEQUENCE {
action CHOICE {
configureDedicatedPriorities SEQUENCE
{
t-322 5 Time in minutes
priorityLevelList SEQUENCE (SIZE 2 entry
(1..maxPrio)) OF SEQUENCE {
priority[1] 3
utraFDD SEQUENCE (SIZE 1 entry UTRA-
(1..maxNumFDDFreqs)) OF SEQUENCE { FDD
as used for Cell 5
}
utraTDD SEQUENCE (SIZE 1 entry UTRA-
(1..maxNumTDDFreqs)) OF SEQUENCE { TDD
as used for Cell 5
}
}
priority[2] 4
eutra SEQUENCE (SIZE 1 entry
earfcn Same downlink EARFCN
as used for Cell 1
}
}
}
e-UTRA detection TRUE
}
}
}
}
}
}
}
}
}
}
ETSI
Table 6.2.3.31.3.3-2: RRC CONNECTION RELEASE for Cell 5 (step 3, Table 6.2.3.31.3.2-3)

RRCConnectionRelease ::= CHOICE {
r4 SEQUENCE {
n-308 2 2 (for CELL_DCH
state). Not
Present (for UE in
other connected
mode states).
releaseCause normalEvent
rplmn-information Not Present
}
v4d0NonCriticalExtensions SEQUENCE {} Not Present
}
}
}
}
6.2.3.31.3.2-3)

}
}
eutra-FrequencyAndPriorityInfoList ::= SEQUENCE 1 entry
earfcn [1] Same downlink EARFCN
as used for Cell 1
measurementBandwidth [1] Not present
qRxLevMinEUTRA [1] -53 (-106 dBm)
threshXhigh [1] 9 (18 dB)
threshXlow [1] 15 (30 dB)
}
}
6.2.3.31.3.2-3)

}
}
ETSI
6.2.3.31.3.2-3)

carrierFreqListUTRA-FDD SEQUENCE (SIZE 1 entry UTRA-FDD
carrierFreq[1] Downlink UARFCN of
Cell 5
threshX-High[1] 5 (10dB)
threshX-Low[1] 5 (10dB)
}
carrierFreqListUTRA-TDD SEQUENCE (SIZE 1 entry UTRA-TDD
carrierFreq[1] Downlink UARFCN of
Cell 5
threshX-High[1] 5 (10dB)
threshX-Low[1] 5 (10dB)
}
}
6.2.3.32 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle,

Snonintrasearch
(1)
ensure that {
then { UE perform measurement and reselects the cell which belong to the high priority UTRA
cell upon Srxlev > Snonintrasearch }
}
5.2.4.5 and 5.2.4.6; TS36.331, clause 6.3.1.
[TS 36.304, clause 5.2.4.2]
measurements.
measurements.
ETSI
according to [10].
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
be performed if:
.....
[TS 36.304, clause 5.2.4.6]
where:

...
ETSI
[TS 36.331, clause 6.3.1]
[TS 36.133, clause 4.2.2.5.1]
The UE shall evaluate whether newly detectable UTRA FDD cells have met the reselection criteria in TS 36.304 within
time (NUTRA_carrier) * TdetectUTRA_FDD when Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ when TreselectionRAT = 0
provided that the reselection criteria is met by a margin of at least 6dB for reselections based on RSCP, or a margin of
at least 3dB for reselections based on Ec/Io.
For a cell that has been already detected, but that has not been reselected to, the filtering shall be such that the UE shall
be capable of evaluating that an already identified UTRA FDD cell has met reselection criterion defined in 3GPP TS
36.304 [1] within (NUTRA_carrier) * TevaluateUTRA_FDD when Treselection = 0 as speficied in table 4.2.2.5.1-1 provided that the
reselection criteria is met by a margin of at least 6dB for reselections based on RSCP, or a margin of at least 3dB for
reselections based on Ec/Io.
[TS 36.133, clause 4.2.2.5.2]
The UE shall evaluate whether newly detectable UTRA TDD cells have met the reselection criteria in TS 36.304 within
time (NUTRA_carrier_TDD) * TdetectUTRA_TDD when Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ when Treselection = 0 provided
that the reselection criteria is met by a margin of at least 6dB.
For a cell that has been already detected, but that has not been reselected to, the filtering shall be such that the UE shall
be capable of evaluating that an already identified UTRA TDD cell has met reselection criterion defined in [1] within
NUTRA_carrier_TDD *TevaluateUTRA_TDD when Treselection = 0 as specified in table 4.2.2.5.2-1 provided that the reselection criteria
is met by a margin of at least 6dB.
System Simulator:
UE:
None.
Preamble:
Table 6.2.3.32.3.2-1 and 6.2.3.32.3.2-2 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. Configurations marked "T1" is applied at the points indicated in the
Main behaviour description in Table 6.2.3.32.3.2-3.
ETSI
Table 6.2.3.32.3.2-1: Time instances of cell power level and parameter change for E-UTRA cell

Cell-specific RS Srxlev of Cell 1 is greater than Snonintrasearch
dBm/15kHz -85
EPRE
T1 Qrxlevmin dBm -106
Snonintrasearch dB [14]
Srxlev* dB 21

Srxlev* dB 19 SrxlevnonServingCell, Cell 5 > Thresh Cell 5,high

U-S Message
information.
6.2.3.32.3.2-1 and 6.2.3.32.3.2-2.
2 Check: Does the test result of steps 1 to 8 of - - 1 -
the generic test procedure in TS 36.508
camped on UTRAN Cell 5? (Note 1)
Note 1: UE shall search higher priority layer (i.e. UTRA carrier frequency of Cell 5) at least every (60 * Nlayers)
Table 6.2.3.32.3.3-1: SystemInformationBlockType3 for Cell 1 (preamble and all steps, table
6.2.3.32.3.2-3)

}
}
}
ETSI
6.2.3.32.3.2-3)

UARFCN as used
for cell 5
}
UARFCN as used
for cell 5
}
}
Table 6.2.3.32.3.3-3: System Information Block Type 19 for Cell 5 (preamble and all steps, Table
6.2.3.32.3.2-3)

utra-PriorityInfoList SEQUENCE {
priority 5
}
}
6.2.3.33 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle / Squal

based cell reselection parameters are broadcasted in E-UTRAN / UE does
not support Squal based cell reselection in UTRAN
(1)
with { UE in E-UTRA RRC_IDLE state not supporting Squal based inter RAT cell reselection from UTRAN
to E-UTRAN and having received SystemInformationBlockType3 containing Squal based cell reselection
parameters from serving E-UTRAN cell }
ensure that {
when { UE detects the cell re-selection criteria based on Srxlev are met for the neighbour UTRA
cell }
}
[TS 36.304, clause 5.2.4.5]

ETSI
and
...

...
Cell reselection to another RAT, for which Squal based cell reselection parameters are broadcast in system information,
shall be performed based on the Squal criteria if the UE supports Squal (RSRQ) based cell reselection to E-UTRAN
from all the other RATs provided by system information which UE supports. Otherwise, cell reselection to another
RAT shall be performed based on Srxlev criteria.
System Simulator:
- Cell 1 and Cell 5
- System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1.
UE:
None.
Preamble:
ETSI

T1 Cell-specific dBm/15kHz -97 - The power level value is assigned to satisfy
RS EPRE SrxlevCell 1 < ThreshServing, LowP. (20 dB)
SqualCell 1 > ThreshServing, LowQ(4 dB)
Noc dBm/15kHz Off -
CPICH_Ec dBm/3.84 MHz - -65 The power level value is assigned to satisfy
SrxlevCell 5 > Threshx, LowP. (2 dB)
P-CCPCH dBm/1.28 MHz - -67
Ioc dBm/3.84kHz - Off
CPICH_Ec/No dB - -2.89

U-S Message
information.
2 The SS changes Cell 1 and Cell 5 level - - - -
1.
5?
6.2.3.33.3.2-2)

}
s-IntraSearch-v920 SEQUENCE {} Not present Default of infinity
applied.
s-NonIntraSearch-v920 SEQUENCE {} Not present Default 0 dB
applied
q-QualMin-r9 -20 dB
}
}
Table 6.2.3.33.3.3-2: Void
ETSI
6.2.3.33.3.2-2)

eutra-FrequencyAndPriorityInfoList SEQUENCE
(SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE {
earfcn[n] Same downlink
EUARFCN as used for
Cell 1
qRxLevMinEUTRA[n] -53 -106 dBm
threshXhigh[n] 15 30 dB
}
}
6.2.3.34 Inter-RAT cell reselection from E-UTRA to UTRA / MFBI

(1)
ensure that {
when { an higher priority UTRAN neighbouring cell which has been included in the multiBandInfoList
provided by the serving cell becomes available, and, is better ranked than the serving cell during a
time interval TreselectionRAT, and, more than 1 second has elapsed since the UE camped on the
current serving cell }
}
[TS 36.304, clause 5.2.4.5]
TreselectionRAT;
be performed if:
For GERAN, UTRAN, and E-UTRAN, SnonServingCell,x is the Srxlev-value of an evaluated cell. ...
[TS 36.331, clause 6.3.1]
The IE SystemInformationBlockType6 contains information relevant only for inter-RAT cell re-selection i.e.
information about UTRA frequencies and UTRA neighbouring cells relevant for cell re-selection. The IE includes cell
re-selection parameters common for a frequency.

multiBandInfoList
Indicates the list of frequency bands in addition to the band represented by carrierFreq in the CarrierFreqUTRA-FDD
for which UTRA cell reselection parameters are common.
ETSI
System Simulator:
- 2 cells, one E-UTRA and one UTRA cell :
- Cell 1 is a E-UTRA cell and is an MFBI capable cell
- Cell 5 is a UTRA cell and is an MFBI capable cell
- Cell 5 belongs to absolute centre frequency which overlaps between bands controlled by IXITs
px_MFBI_UTRAN_FrequencyBand and px_UTRAN_OverlappingNotSupportedFrequencyBandMFBI.
- System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is used in the E-UTRA cell.
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configuration marked "T1" is applied at the points indicated in

T1 CPICH_Ec dBm/3.84 MHz - -65 S nonServingCell, Cell5 > Thresh Cell 5,high

U-S Message
information.
1.
5?
ETSI
Table 6.1.2.20.3.3-1: SystemInformationBlockType1 for cell 1 (preamble)

freqBandIndicator An overlapping not
supported frequency
BI).
SEQUENCE {
freqBandIndicator Overlapping Bands for Cell 1
Cell 1 under test
d).
}
}
}
6.2.3.34.3.2-2)

as used for cell 5
than E-UTRA
}
as used for cell 5
than E-UTRA
}
}
SEQUENCE {
CarrierFreqListUTRA-FDD-v8h0 SEQUENCE {
CarrierFreqInfoUTRA-FDD-v8h0 SEQUENCE {
FreqBandIndicator-UTRA-FDD Overlapping Bands for Cell 5
Cell 5 under test
d).
}
}
}
}
ETSI
6.2.3.34.3.2-2)

Priority 5
}
}
6.2.3.34.3.2-2)
Derivation Path: 25.331 clause 10.2.48.8.8

Frequency Band Indicator Not Present A1
px_UTRAN_Overlapping A2
NotSupportedFrequency
BandMFBI
Extension indicator A3
Frequency Band Indicator 2 Not Present A1
Not Present A2
px_UTRAN_Overlapping A3
NotSupportedFrequency
BandMFBI
Multiple Frequency Band indicator list px_MFBI_UTRAN_Frequ
encyBand
A1 Band I, Band II, Band III
A2 Band V, Band VI, Band VII
A3 Band VIII & bands beyond Band X
6.2.4 Inter-RAT absolute priority based reselection in UTRA CELL_FACH

6.2.4.1 Inter-RAT absolute priority based reselection in UTRA CELL_FACH to E-
UTRA RRC_IDLE (Higher Priority Layers, Srxlev,x > Threshx,high and
Srxlev,serv > Sprioritysearch1 and SqualServ > Sprioritysearch2)
(1)
with { UE in UTRA Cell FACH state and absolute priority measurement indicated }
ensure that {
when { Threshx,high2 or Threshx,low2 are not provided and the Srxlev for a higher absolute
priority E-UTRA cell is greater than Threshx,high }
then { the UE performs cell reselection to the E-UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, 5.2.6.1.2a, 5.2.6.1.4a
and TS 25.331, 8.1.1.6.19.
[TS 25.304, clause 5.2.6.1.2a]
The measurement rules below apply in Idle, URA_PCH, CELL_PCH states. In CELL_FACH state, if (High Priority
Layers is indicated in CELL_FACH Absolute Priority Measurement Indicator [4] and SrxlevServingCell >
Sprioritysearch1 and SqualServingCell > Sprioritysearch2) or (All Layers is indicated in CELL_FACH Absolute
ETSI
Priority Measurement Indicator [4]) then the measurement rules below apply, otherwise the measurement rules in
5.2.6.1.1 and 5.2.6.1.2 apply.
The UE is required to perform measurements of inter-frequency and inter-RAT cells listed in system information
according to Measurement requirements are specified in [10]. UE specific priorities are not applied in camped on any
cell state.
serving cell.
- In CELL_FACH state: If there are UTRAN inter-frequency, GERAN and E-UTRAN neighbours configured and
required to be measured according to the measurement rules above, then the UE shall perform measurements on
UTRAN inter-frequency and E-UTRAN layers (i.e. the UE is not required to measure GERAN, regardless of whether
GERAN has absolute priorities assigned).
[TS 25.304, clause 5.2.6.1.4a]
...Cell reselection to a cell on a higher absolute priority layer than the camped frequency shall be performed if criterion
1 or 4 is fulfilled.
[TS 25.331, clause 8.1.1.6.19]
If the cell is not operating in MBSFN mode according to subclause 8.1.1.6.3 the UE should store all relevant IEs
included in this system information block. If the cell is not operating in MBSFN mode according to subclause 8.1.1.6.3
the UE shall:
1> if the value of the IE "Priority status" in the variable PRIORITY_INFO_LIST equals "dedicated_priority":
2> clear every stored value of "Threshx, high", "Threshx, low", "Threshx, high2", "Threshx, low2" and "EUTRA-RSRQ-
offsetWB" in every occurrence of the IE "Priority Info List" in the variable PRIORITY_INFO_LIST.
1> otherwise:
2> clear the variable PRIORITY_INFO_LIST.
1> clear the variable EUTRA_FREQUENCY_INFO_LIST;
1> act upon the received IE "UTRA priority info list" as described in subclause 8.6.7.3a;
1> if the IE "GSM priority info list" is present:
2> act upon the received IE as described in subclause 8.6.7.3b.
1> if the IE "E-UTRA frequency and priority info list" is present:
2> act upon the received IE as described in subclause 8.6.7.3c.
1> if the IE "E-UTRA frequency RACH reporting information" is present; and
1> if the UE supports E-UTRA RACH reporting:
2> store the IE "E-UTRA frequency RACH reporting information" into the variable
EUTRA_FREQUENCY_INFO_LIST_FACH and act upon the received IE as described in subclause 8.5.23.
ETSI
System Simulator:
- Cell 1
- Cell 5
UE:
None.
Preamble:
- The UE is in state PS-DCCH+DTCH FACH (state 6-11) on Cell 5 according to [5].
Table 6.2.4.1.3.2-1 and Table 6.2.4.1.3.2-2 illustrate 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, while
row 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.

Cell-specific RS Power level “Off” is defined in
dBm/15kHz “Off”
T0 EPRE TS36.508 Table 6.2.2.1-1.
Qrxlevmin dBm -106
Cell-specific RS
dBm/15kHz -85
EPRE
T1
qRxLevMinEUTRA

T0 Qrxlevmin (FDD) dBm -79 Default value
Srxlev* dB 19
Srxlev* dB 19

U-S Message
1 The SS change Cell 1 level according to the - - - -
row "T1" in table 6.2.4.1.3.2-1.
Cell 1
ETSI
Table 6.2.4.1.3.3-1: System Information Block type 19 for Cell 5 (Pre-test conditions and all steps,
Table 6.2.4.1.3.2-3

sysInfoType19-v920ext SEQUENCE {}
va80NonCriticalExtensions SEQUENCE {
sysInfoType19-va80ext SEQUENCE {}
vb30NonCriticalExtensions SEQUENCE {
sysInfoType19-vb30ext SEQUENCE {
cell-fach-meas-ind high-priority-layers
vb50NonCriticalExtensions SEQUENCE {}
}
}
}
}
}
}
6.2.4.2 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (Higher

Priority Layers, no cell reselection to E-UTRA RRC_IDLE when Srxlev,serv <
Sprioritysearch1)
(1)
ensure that {
when { Srxlev for serving cell is lower than Sprioritysearch1 }
then { the UE performs no cell reselection to the E-UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, 5.2.6.1.2a and TS
25.331, 8.1.1.6.19.
[TS 25.304, clause 5.2.6.1.2a]
5.2.6.1.1 and 5.2.6.1.2 apply.
[TS 25.331, clause 8.1.1.6.19]
the UE shall:
1> otherwise:
ETSI
System Simulator:
- Cell 1
- Cell 5
UE:
None.
Preamble:

dBm/15kHz “Off”
T0 EPRE TS36.508 Table 6.2.2.1-1.
Qrxlevmin dBm -106
Cell-specific RS
dBm/15kHz -85
EPRE
T1
qRxLevMinEUTRA
ETSI

Srxlev* dB 19
Srxlev* dB 19

U-S Message
row "T1" in table 6.2.4.2.3.2-1.
next 10s?
Table 6.2.4.2.3.2-3

utra-ServingCell SEQUENCE {
s-PrioritySearch1 62 (124 dB) Highest
}
}
}
}
}
}
}
}
6.2.4.3 Inter-RAT absolute priority based reselection in UTRA _CELL_FACH to E-

UTRA RRC_IDLE (Higher Priority Layers, Squal,x > Threshx,high2 and
Srxlev,serv > Sprioritysearch1 and SqualServ > Sprioritysearch2)
(1)
ensure that {
when { the Squal for a higher absolute priority E-UTRA cell is greater than Threshx,high }
then { the UE performs cell reselection to the E-UTRA cell }
}
ETSI
and TS 25.331, 8.1.1.6.19.
[TS 25.304, clause 5.2.6.1.2a]
5.2.6.1.1 and 5.2.6.1.2 apply.
cell state.
serving cell.
UTRAN inter-frequency and E-UTRAN layers (i.e. the UE is not required to measure GERAN, regardless of
whether GERAN has absolute priorities assigned).
[TS 25.304, clause 5.2.6.1.4a]
Threshx,high2 during a time interval Treselection;...Cell reselection to a cell on a higher absolute priority layer than
the camped frequency shall be performed if criterion 1 or 4 is fulfilled.
[TS 25.331, clause 8.1.1.6.19]
the UE shall:
1> otherwise:
ETSI
System Simulator:
- Cell 1
- Cell 5
UE:
None.
Preamble:

dBm/15kHz “Off”
T0 EPRE TS36.508 Table 6.2.2.1-1.
Qrxlevmin dBm -106
Cell-specific RS
dBm/15kHz -85
EPRE
T1
qRxLevMinEUTRA

Srxlev* dB 19
Srxlev* dB 19
ETSI

U-S Message
row "T1" in table 6.2.4.3.3.2-1.
Cell 1
Table 6.2.4.3.3.2-3
Derivation Path: 36.508 clause 4.4.4.1, Table 4.4.4.1-1, condition QBASED

(SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE {
threshXhigh[n] 62 (124 dB) Highest value, so
threshXhigh2 is
applicable.
}
}
}
}
}
}
}
6.2.4.4 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (lower

priority) to E-UTRA RRC_IDLE (higher priority) (All Layers, Srxlev,x >
Threshx,high)
(1)
with { UE in UTRA Cell FACH state and Cell FACH absolute priority measurement indicated as All
Layers }
ensure that {
when { Threshx,high2 or Threshx,low2 are not provided and the Srxlev for a higher absolute
priority E-UTRA cell is greater than Threshx,high }
then { the UE performs cell reselection to the higher priority E-UTRA cell }
}
and TS 25.331, 8.1.1.6.19.
ETSI
[TS 25.304, clause 5.2.6.1.2a]
5.2.6.1.1 and 5.2.6.1.2 apply.
cell state.
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
[TS 25.331, clause 8.1.1.6.19]
the UE shall:
1> otherwise:
ETSI
System Simulator:
- Cell 1
- Cell 5
UE:
None.
Preamble:

dBm/15kHz “Off”
T0 EPRE TS36.508 Table 6.2.2.1-1.
Qrxlevmin dBm -106
Cell-specific RS
dBm/15kHz -85
EPRE
T1
qRxLevMinEUTRA

Srxlev* dB 19
Srxlev* dB 19
ETSI

U-S Message
row "T1" in table 6.2.4.4.3.2-1.
Cell 1
Table 6.2.4.4.3.2-3)

cell-fach-meas-ind all-layers
}
}
}
}
}
}
6.2.4.5 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (lower

priority) to E-UTRA RRC_IDLE (higher priority) (All Layers, Squal,x
>ThreshX,high2)
(1)
Layers }
ensure that {
when { Threshx,high2 and Threshx,low2 are both provided and the Squal for a higher absolute
priority E-UTRA cell is greater than Threshx,high2 }
}
and TS 25.331, 8.1.1.6.19.
[TS 25.304, clause 5.2.6.1.2a]
5.2.6.1.1 and 5.2.6.1.2 apply.
ETSI
cell state.
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
[TS 25.331, clause 8.1.1.6.19]
the UE shall:
1> otherwise:
ETSI
System Simulator:
- Cell 1
- Cell 5
- System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 with QBASED is used in E-
UTRA Cell 1.
UE:
None.
Preamble:

Cell-specific RSRQ dB -32
Noc dBm/15kHz -75
The power level value is such to
Cell-specific RS satisfy SrxlevCell 1 > 0 and
dBm/15kHz -95
EPRE SqualCell 1 < 0 but the UE is able to
T0
read the PLMN identity
(default value in 36.508 Table
Qrxlevmin dBm -106
4.4.3.2-3)
Qqualmin dB -18
Squal dB -14 Squal< Threshx,high2
Noc -75
T1 Cell-specific RS
dBm/15kHz -65
EPRE
Squal dB 13 Squal > Threshx,high2

T0
Threshx,high2 dB 5
Srxlev* dB 19
Srxlev* dB 19
ETSI

U-S Message
The SS change Cell 1 level according to the
1 - - - -
row "T1" in table 6.2.4.5.3.2-1.
Check: Does the test result of the generic test
2 - - 1 -
Cell 1
Table 6.2.4.5.3.3-1: SystemInformationBlockType1 for Cell 1 (Pre-test conditions and all steps, Table
6.2.4.5.3.2-3)

q-QualMin-r9 -18 dB
}
}
}
}
Table 6.2.4.5.3.2-3)

}
}
}
}
}
}
ETSI
6.2.4.6 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (higher

priority) to E-UTRA RRC_IDLE (lower priority) (All Layers, Srxlev,serv <
Sprioritysearch1 , Srxlev,serv <Thresh serv,low and Srxlev,x > Threshx,low)
(1)
Layers }
ensure that {
when { Threshx,high2 or Threshx,low2 are not provided, Srxlev < Sprioritysearch1 and Srxlev <
Thresh serv,low for serving UTRA cell, and the Srxlev for a lower absolute priority E-UTRA cell is
greater than Threshx,low }
then { the UE performs cell reselection to the lower priority E-UTRA cell }
}
and TS 25.331, 8.1.1.6.19.
[TS 25.304, clause 5.2.6.1.2a]
5.2.6.1.1 and 5.2.6.1.2 apply.
cell state.
...
[TS 25.304, clause 5.2.6.1.4a]
- Criterion 3: (SrxlevServingCell < Threshserving,low or SqualServingCell <= Threshserving,low2) and the SrxlevnonServingCell,x of a
cell on an evaluated lower absolute priority layer is greater than Threshx,low during a time interval Treselection;
... Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall be performed if criterion
[TS 25.331, clause 8.1.1.6.19]
ETSI
the UE shall:
1> otherwise:
System Simulator:
- Cell 1
- Cell 5
UE:
None.
Preamble:
ETSI

dBm/15kHz “Off”
T0 EPRE TS36.508 Table 6.2.2.1-1.
Qrxlevmin dBm -106
Cell-specific RS
dBm/15kHz -85
EPRE
T1
qRxLevMinEUTRA

Srxlev* dB 19
Srxlev* dB 19

U-S Message
row "T1" in table 6.2.4.6.3.2-1.
Cell 1
ETSI
Table 6.2.4.6.3.2-3)

priority 3
s-PrioritySearch1 11 (22dB)
s-PrioritySearch2 Not present default value is 0
}
eutra-FrequencyAndPriorityInfoList SEQUENCE The same number of n denotes the
(SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE entries as the configured index of the entry
eutra carriers
For Signalling test cases,
see table 6.3.1.7-1
earfcn[n] Downlink EARFCN under
test
see table 6.3.1.7-1
measurementBandwidth[n] Set according to EUTRA
band ChBw in Table 5.6-
1 of TS36.104.
priority[n] 2
qRxLevMinEUTRA[n] -53 (-106 dBm) For signalling test
cases
threshXhigh[n] 2 (4 dB)
threshXlow[n] 1 (2 dB)
eutra-blackListedCellList[n] Not present
eutraDetection[n] TRUE
}
6.2.4.7 Inter-RAT absolute priority based reselection in UTRA CELL_FACH (higher

priority) to E-UTRA RRC_IDLE (lower priority) (All Layers, Srxlev,serv <
Sprioritysearch1 , Squal,serv <Thresh serv,low2 and Squal,x >
ThreshX,low2)
(1)
Layers }
ensure that {
when { Threshx,high2 and Threshx,low2 are both provided and the Squal for a higher absolute
priority E-UTRA cell is greater than Threshx,low2 and the Squal for the serving cell is lower than
Thresh serv,low2}
}
and TS 25.331, 8.1.1.6.19.
[TS 25.304, clause 5.2.6.1.2a]
ETSI
5.2.6.1.1 and 5.2.6.1.2 apply.
cell state.
serving cell.
[TS 25.304, clause 5.2.6.1.4a]
- Criterion 5: for FDD, (SrxlevServingCell < =Threshserving,low or SqualServingCell < Threshserving,low2) and the
SqualnonServingCell,x of a cell on an evaluated lower absolute priority layer is greater than Threshx,low2 during a time
interval Treselection; for 1.28 Mcps TDD, (SrxlevServingCell < Threshserving,low) and the SqualnonServingCell,x of a cell
on an evaluated lower absolute priority layer is greater than Threshx,low2 during a time interval Treselection;
...
Cell reselection to a cell on a higher absolute priority layer than the camped frequency shall be performed if
criterion 1 or 4 is fulfilled.
[TS 25.331, clause 8.1.1.6.19]
the UE shall:
1> otherwise:
ETSI
System Simulator:
- Cell 1
- Cell 5
- System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 with QBASED is used in E-
UTRA Cell 1.
UE:
None.
Preamble:

Noc dBm/15kHz -75
The power level value is such to
Cell-specific RS satisfy SrxlevCell 1 > 0 and
dBm/15kHz -95
EPRE SqualCell 1 < 0 but the UE is able to
T0
read the PLMN identity
(default value in 36.508 Table
Qrxlevmin dBm -106
4.4.3.2-3)
Qqualmin dB -18
Squal dB -14
Noc -75
T1 Cell-specific RS
dBm/15kHz -65
EPRE
Squal dB 13
ETSI

CPICH Ec/N0 dB -10
Qrxlevmin (TDD) dBm -81 Default value
T0 Qqualmin (FDD) dB -24 Default value
Threshserving,low dB 25
Threshserving,low2 dB 7
Threshx,low2 dB 5
Srxlev dB 19
Squal (FDD) dB 14
CPICH Ec/N0 dB -18
Srxlev dB 19
Squal (FDD) dB 6

U-S Message
The SS change Cell 1 level according to the
1 - - - -
row "T1" in table 6.2.4.7.3.2-1.
Check: Does the test result of the generic test
2 - - 1 -
Cell 1
Table 6.2.4.7.3.3-1: SystemInformationBlockType1 for Cell 1 (Pre-test conditions and all steps, Table
6.2.4.7.3.2-3)

q-QualMin-r9 -18 dB
}
}
}
}
ETSI
Table 6.2.4.7.3.2-3)

}
}
}
}
}
}
}
eutra-FrequencyAndPriorityInfoList-v920ext The same number of n denotes the
(SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE { entries as the configured index of the entry
eutra carriers
see table 6.3.1.7-1
threshXhigh2[n] 15
}
}
6.3 Closed Subscriber Group cells

6.3.1 Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-
CSG cell to E-UTRA RRC_IDLE CSG cell
6.3.1.1 Test Purpose (TP)
(1)
ensure that {
when { Manual CSG ID selection is requested }
then { UE selects the requested CSG cell }
}
(2)
with { UE in E-UTRA RRC_IDLE state on a non-CSG cell and UE’s Allowed CSG list is not empty }
ensure that {
when { a previously visited allowed E-UTRA CSG cell becomes the strongest cell on its frequency }
then { UE reselects the E-UTRA CSG cell }
}
6.3.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.8.1, and
36.133, clauses 4.2.2.10 and 4.2.2.10.1.
[TS 36.304, clause 5.2.4.8.1]
ETSI
In addition to normal cell reselection, the UE shall use an autonomous search function to detect at least previously
visited allowed CSG cells on non-serving frequencies, including inter-RAT frequencies, according to the performance
requirements specified in [10], when at least one CSG ID is included in the UE’s CSG whitelist. The UE may also use
autonomous search on the serving frequency. The UE shall disable the autonomous search function for CSG cells if the
UE’s CSG whitelist is empty.
NOTE: The UE autonomous search function, per UE implementation, determines when and/or where to search
for allowed CSG cells.
If the UE detects one or more suitable CSG cells on different frequencies, then the UE shall reselect to one of the
detected cells irrespective of the frequency priority of the cell the UE is currently camped on, if the concerned CSG cell
is the highest ranked cell on that frequency.
[TS 36.133, clause 4.2.2.10]
Reselection from non CSG to CSG cells may be performed using UE autonomous search as defined in [1] when at least
one CSG ID is included in the UE’s CSG whitelist. The requirements in this section are valid for reselection to CSG
cells previously visited by the UE when the radio configuration parameters, including the carrier frequency and physical
cell identity of the CSG cell, non CSG cell and other neighbour cells are unchanged from the most recent previous visit.
[TS 36.133, clause 4.2.2.10.1]
The UE shall perform search and reselection to an allowed inter-frequency CSG cell that has met reselection criterion
defined in [1] and that is in its whitelist, within 6 minutes in the conditions shown in table 4.2.2.10.1-1. There is no need
for statistical testing of this requirement.
Table 4.2.2.10.1-1: Parameters for CSG inter-frequency reselection

Note1
EARFCN Channel 1 Channel 2
CSG indicator False True
Note1
Physical cell identity 1 2
CSG identity Not sent Already stored
in UE whitelist
from previous
visit
Propagation conditions Static, non multipath
CSG cell previously Yes
visited by UE
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
N oc dBm/15 kHz Off
Note2
RSRP dBm/15 KHz -110 -110
Note 1: For this requirement to be applicable, the EARFCN and physical cell
identity for cell 1 and cell 2 shall be unchanged from when the CSG cell
was visited previously
Note 2: Chosen to ensure that CSG autonomous search has a high probability of
success on every attempt made by UE
ETSI
6.3.1.3 Test description
6.3.1.3.1 Pre-test conditions
System Simulator:
- Cell 1, Cell 3, Cell 11 and Cell 23 have different tracking areas according to table 6.0.1-2.
- Cell 1, Cell 11 and Cell 23 are not CSG cells.
- Cell 3 is a CSG cell.
- System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1,Cell 11
and Cell 23.
UE:
- The UE’s Allowed CSG list is empty.
Preamble:
6.3.1.3.2 Test procedure sequence
Table 6.3.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. Configurations marked "T0", "T1", "T2", "T3" and "T4" are applied at the
points indicated in the Main behaviour description in Table 6.3.1.3.2-2.
Table 6.3.1.3.2-1: Time instances of cell power level and parameter changes

-65 Off Off Off The power levels are such
Cell-specific RS dBm/15k
that camping on Cell 1 is
EPRE Hz
T0 guaranteed.
Qrxlevmin dBm -140 -140 -140 -140
Srxlev* dB 75 - - -
T1 Cell-specific RS dBm/15k -65 -85 Off -91
EPRE Hz
Srxlev* dB 75 55 - 49
T2 Cell-specific RS dBm/15k Off Off -65 Off The power levels are such
guaranteed.
Srxlev* dB - - 75 -
T3 Cell-specific RS dBm/15k -65 Off -91 -85
EPRE Hz
Srxlev* dB 75 - 49 55
EPRE Hz
Srxlev* dB 75 55 - 49
ETSI
Table 6.3.1.3.2-2: Main behaviour

U-S Message
NOTE: the UE performs registration and the
according to row "T1" in table 6.3.1.3.2-1.
19 The UE is made to perform manual CSG ID - - - -
selection and select Cell 3.
indicate that the UE is camped on Cell 3?
21 The SS changes Cell1, Cell 3, Cell 11 and Cell - - - -
23 levels according to row "T2" in table
6.3.1.3.2-1.
22- Steps 1 to 6 of the TAU procedure described - - - -
27 in TS 36.508 subclause 6.4.2.7 are performed
on Cell 11.
NOTE: the UE performs a TAU and the RRC
connection is released.
levels according to row "T3" in table 6.3.1.3.2-
1.
on Cell 1.
1.
36- Check: Does the test result of Steps 1 to 5 of - - 2 -
40 the generic test procedure in TS 36.508
camped on Cell 3 within 6 mins from "T4" to
the time RRCConnectionRequest received by
SS?
6.3.1.3.3 Specific message contents
Table 6.3.1.3.3-1: Conditions for table 6.3.1.3.3-2
ETSI
Table 6.3.1.3.3-2: SystemInformationBlockType1 for Cell 1, 3, 11 and 23 (preamble and all steps,
Table 6.3.1.3.2-2)

csg-Indication FALSE Cell 1
Cell 11
Cell 23
TRUE Cell 3
csg-Identity Not present Cell 1
Cell 11
Cell 23
'000 0000 0000 0000 Cell 3
0000 0000 0011'B
}
}
Table 6.3.1.3.3-3: SystemInformationBlockType4 for Cell 3 (Pre-test conditions and all steps, table
6.3.1.3.2-2)

csg-PhysCellIdRange ::= SEQUENCE {
start 3
range Not present The UE shall
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
6.3.2 Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-

UTRA idle CSG cell
(1)
ensure that {
then { UE select the suitable E-UTRAN CSG cell }
}
(2)
with { UE in GSM/GPRS Registered state and no RR connection and UE’s Allowed CSG list is not empty }
ensure that {
when { UE detects a suitable E-UTRAN CSG cell previously visited }
then { UE reselects the suitable previously visited E-UTRAN CSG cell irrespective of the EUTRAN
cell reselection priority }
}
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.3.2.4, TS
45.008, clause 6.6.7.1, TS 45.008, clause 6.6.7.2 and TS 36.304, clause 10.1.3.4.
ETSI
[TS 24.301, clause 5.5.3.2.4]
If the UE has initiated the tracking area updating procedure due to manual CSG selection and receives a TRACKING
AREA UPDATE ACCEPT message, the UE shall check if the CSG ID of the cell where the UE has sent the
TRACKING AREA UPDATE REQUEST message is contained in the Allowed CSG list. If not, the UE shall add that
CSD ID to the Allowed CSG list.
[TS 45.008, clause 6.6.7.1]
If a mobile station is a member of at least one Closed Subscriber Group, i.e. at least one CSG ID is included in the MS’s
"Allowed CSG list", then, in addition to normal cell reselection, the MS shall use an autonomous search function to
detect UTRAN and/or E-UTRAN CSG cells. The autonomous search function shall at least detect previously visited
allowed CSG cells.
NOTE 1: The autonomous search function is implementation dependent and controls when and/or where to search
If the strongest cell (see 3GPP TS 25.304 and 3GPP TS 36.304 for the definition of the strongest cell) which the MS has
detected on a UTRAN or E-UTRAN frequency during a time interval T_reselection is a suitable CSG cell (see 3GPP
TS 25.304 and 3GPP TS 36.304 for suitability criteria for UTRAN and E-UTRAN CSG cells respectively), the MS
shall reselect to this cell irrespective of the cell reselection rules applicable for the cell on which the MS is currently
camped.
The following requirements are valid for reselection to allowed CSG cells previously visited by the MS when the radio
configuration parameters, including the carrier frequency and PSC/PCI (whichever and if it is applicable) of the CSG
cell, non CSG cell and other neighbour cells, are unchanged from the most recent previous visit. The autonomous
search and cell re-selection to a previously visited allowed CSG cell shall meet the performance requirements defined as
follows:
- the MS shall perform search and re-selection to a previously visited allowed UTRAN FDD CSG cell, that has
met the CSG cell re-selection criterion defined above, within 6 minutes in the radio conditions specified for an
UTRAN FDD CSG cell in 3GPP TS 36.133 in terms of parameters for CSG inter-RAT UTRAN FDD
reselection; UARFCN and PSC shall be unchanged from the most recent previous visit of the UTRAN FDD
CSG cell; Serving GSM cell at RXLEV= -70 dBm, with 6 GSM neighbours at RXLEV= -75 dBm;
- the MS shall perform search and re-selection to a previously visited allowed E-UTRAN CSG cell, that has met
the CSG cell re-selection criterion defined above, within 6 minutes in the radio conditions specified for an E-
UTRAN CSG cell in 3GPP TS 25.133 in terms of parameters for CSG inter-RAT E-UTRA reselection; E-
UARFCN and PCI shall be unchanged from the most recent previous visit of the E-UTRAN CSG cell; Serving
GSM cell at RXLEV= -70 dBm, with 6 GSM neighbours at RXLEV= -75 dBm.
NOTE 4: The above performance requirements are minimum requirements defined to ensure the testability of
autonomous CSG search.
[TS 45.008, clause 6.6.7.2]
If NAS requests AS to search for available CSG IDs, the MS shall perform the search and report the results to NAS as
described in 3GPP TS 25.304 for UTRAN and as described in 3GPP TS 36.304 for E-UTRAN.
If a CSG ID is manually selected by NAS, the MS shall behave as specified in 3GPP TS 25.304 or in 3GPP TS 36.304,
depending on the RAT type of the selected CSG cell.
[TS 45.008, clause 10.1.3.4]
"Allowed CSG list", then, in addition to normal cell reselection, the MS shall use an autonomous search function to
detect UTRAN and/or E-UTRAN CSG cells. The autonomous search function shall at least detect previously visited
allowed CSG cells.
ETSI
System Simulator:
- Cell 2 is CSG cell.
- Cell 24 and Cell 25 have different Routing Area.
UE:
Preamble:
Tables 6.3.2.3.2-1 and 6.3.2.3.2-2 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, while rows
marked "T1", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values shall be
Table 6.3.2.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell

dBm/15kHz “Off” “Off”
T0 EPRE TS36.508 Table 6.2.2.1-1.
Cell-specific RS
dBm/15kHz -91 -85
EPRE
T1 Srxlev* dB 15 21 Srxlev = Cell-specific RS EPRE -
qRxLevMinEUTRA

EPRE TS 36.508 Table 6.2.2.1-1.
T2
Srxlev* dB “Off” “Off” S nonServingCell, Cell7 > Thresh Cell7,high
Cell-specific RS
T3 dBm/15kHz -85 “Off”
EPRE
Cell-specific RS
dBm/15kHz -91 -85
EPRE
T4
Srxlev* dB 15 21 Srxlev = Cell-specific RS EPRE -
qRxLevMinEUTRA
ETSI
Table 6.3.2.3.2-2: Time instances of cell power level and parameter changes for GERAN cell

RF Signal Level dBm -80 “Off”
T0
RXLEV_ACCESS_MIN dBm -101 “Off”
C1* dB 21 “Off”
T1 RXLEV_ACCESS_MIN dBm -101 “Off”
C1* dB 21 “Off”
“Off” The power levels are such that
T2
RXLEV_ACCESS_MIN dBm “Off” -101
C1* dB “Off” 21
RF Signal Level dBm -80 -90
T3 RXLEV_ACCESS_MIN dBm -101 -101
C1* dB 21 11
C1* dB 21 “Off”

U-S Message
2 Call the registration procedure described in TS - - - -
34.123-3 subclause 6.10.2.7.1.1 performed on
Cell 24.
RR connection is released.
according to the row "T1" in table 6.3.2.3.2-1.
Cell 2?
5A Wait for 6 s for UE to receive system - - - -
information.
6 The SS changes Cell 1, Cell 2, Cell 24 and - - - -
Cell 25 levels according to row "T2" in table
6.3.2.3.2-1 and table 6.3.2.3.2-2.
7- Steps 1 to 11 of the Routing Area Update - - - -
17 procedure described in TS 36.508 subclause
6.4.2.9 are performed on Cell 25.
NOTE: The UE performs RAU and the RR
1 and table 6.3.2.3.2-2.
level according to row "T4" in table 6.3.2.3.2-1
and table 6.3.2.3.2-2.
Cell 2 within 6 mins?
ETSI
Table 6.3.2.3.3-1: SystemInformationBlockType1 for Cell 2 (preamble and all steps, Table 6.3.2.3.2-3)

csg-Indication TRUE
csg-Identity 1
}
}

csg-PhysCellIdRange SEQUENCE {
start 2
range n4
}
}
Table 6.3.2.3.3-3: SYSTEM INFORMATION TYPE 2 Quarter for Cell 24 and Cell 25 (Pre-test conditions
and all steps, Table 6.3.2.3.2-3)
Derivation Path: 36.508 clause 4.4.5, Table 4.4.5-1

Additions in release 8 H
Priority and E-UTRAN Parameters Description 1 Present
Serving Cell Priority Parameters Description 1 Present
GERAN_PRIORITY 5 Higher priority
than E-UTRA
ETSI
Table 6.3.2.3.3-4: SystemInformationBlockType7 for Cell 1 and Cell 2 (Pre-test conditions and all
steps, Table 6.3.2.3.2-3)

{}
carrierFreqsGERAN SEQUENCE [1] {
}
}
}
cellReselectionPriority 5 Higher priority
than EUTRA Freq
}
}
}
}
cellReselectionPriority 5 Higher priority
than EUTRA Freq
}
}
}
6.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE

CSG cell
(1)
with { UE in UTRA IDLE state }
ensure that {
}
(2)
with { UE in UTRA IDLE state and UE’s Allowed CSG list is not empty }
ensure that {
}
ETSI
References: The conformance requirements covered in the present TC are specified in: TS 25.304, clause 5.6.1,
5.2.6.4.1, TS 36.304 clause 5.2.4.8.1, 5.2.4.6, 5.2.4.8.2, 5.2.4.1 and TS 25.133, clause 4.2.2.11.2.
[TS 24.301, clause 5.5.3.2.4]
AREA UPDATE ACCEPT message, the UE shall check if the CSG ID of the cell where the UE has sent the
TRACKING AREA UPDATE REQUEST message is contained in the Allowed CSG list. If not, the UE shall add that
CSD ID to the Allowed CSG list.
[TS 25.304, clause 5.6.1]
In the UE on request of NAS, the AS shall scan all RF channels in the UTRA bands according to its capabilities to find
available CSG IDs. On each carrier, the UE shall at least search for the strongest cell, read its system information and
report available CSG ID(s) together with their “HNB name” (if broadcast) and PLMN(s) to the NAS. The search for
available CSG IDs may be stopped on request of the NAS.
If NAS has selected a CSG ID and provided this selection to AS, the UE shall search for an acceptable or suitable cell
belonging to the selected CSG ID to camp on.
[TS 25.304, clause 5.2.6.4.1]
requirements specified in [10], when at least one CSG ID is included in the UE’s CSG whitelist. The UE is required to
perform autonomous search function in Idle, Cell_PCH and URA_PCH states. The UE shall disable the autonomous
search function for CSG cells if the UE’s CSG whitelist is empty. If "Dedicated CSG frequency(ies) " IE is present, the
UE may use the autonomous search function only on these dedicated frequencies and on the other frequencies listed in
the system information.
When the UE has no or an empty CSG whitelist, the UE may ignore cells with PSC in the stored range "CSG PSC Split
Information" [4] reserved for CSG cells for intra-frequency and inter-frequency measurements and cell re-selections.
If the UE detects a suitable CSG cell on a different frequency it shall reselect this cell irrespective of the cell reselection
rules applicable for the cell the UE is currently camped on, if the detected suitable CSG cell is the strongest cell on that
frequency. If suitable CSG cells are detected on different frequencies and these are the strongest cells on their
frequencies, then the UE shall reselect to any one of them.
If the UE detects one or more suitable CSG cell on another RAT, the UE shall reselect to one of them according to [18].
[TS 25.133, clause 4.2.2.11.2]
The UE shall perform search and reselection to an allowed inter-RAT E-UTRA CSG cell that has met CSG reselection
criterion defined in [1] and that is in its whitelist, within 6 minutes in the conditions shown in table 4.2.2.11.2-1. There
is no need for statistical testing of this requirement.
ETSI
Table 4.2.2.11.2-1: Parameters for CSG inter-RAT E-UTRA reselection

Note1
UARFCN Channel 1 N/A
Note1
EARFCN N/A Channel 2
Primary scrambling code Scrambling N/A
Note1
code 1
Note1
Physical cell identity N/A 2
CSG identity Not sent Sent
(Already stored
in UE whitelist
from previous
visit)
visited by UE
Note2
CPICH_RSCP dBm -100
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCCPCH_Ec/Ior dB -12
AICH_Ec/Ior dB -15 N/A
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
I oc dBm/3.84 MHz Off
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
Note2
RSRP dBm/15 KHz -110
Note 1: For this requirement to be applicable, the UARFCN and scrambling
code for cell 1 and the EARFCN and physical cell identity for cell 2 shall
be unchanged from when the CSG cell was visited previously
Note 2: Chosen to ensure that CSG autonomous search has a high probability
of success on every attempt made by UE
[TS 36.304, clause 5.2.4.8.1]
If the UE detects a suitable CSG cell on the same frequency, it shall reselect to this cell as per normal reselection rules
(5.2.4.6.).
ETSI
[TS 36.304, clause 5.2.4.6]
where:

[TS 36.304, clause 5.2.4.8.2]
While camped on a suitable CSG cell, the UE shall apply the normal cell reselection rules as defined in subclause 5.2.4.
[TS 36.304, clause 5.2.4.1]
(re)selection.
While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest
priority frequency (i.e. higher than the eight network configured values), irrespective of any other priority value
allocated to this frequency.
System Simulator:
ETSI
UE:
Preamble:
Tables 6.3.3.3.2-1 and 6.3.3.3.2-2 illustrate the downlink power levels and other changing parameters to be applied for

T0 EPRE TS36.508 Table 6.2.2.1-1.
Cell-specific RS
dBm/15kHz -91 -85
EPRE
qRxLevMinEUTRA
Power level “Off” is defined in

Cell-specific RS
dBm/15kHz “Off” “Off” TS 36.508 Table 6.2.2.1-1.
EPRE
T2
Srxlev* dB N/A N/A S nonServingCell, Cell7 > Thresh Cell7,high
Cell-specific RS
EPRE
Cell-specific RS
dBm/15kHz -91 -85
EPRE
qRxLevMinEUTRA
Table 6.3.3.3.2-2: Time instances of cell power level and parameter changes for UTRA cell

CPICH_Ec dBm/3.84 MHz -60 “Off”
P-CCPCH dBm/1.28 MHz -62 “Off”
T0 camping on Cell 5 is guaranteed.
Qrxlevmin (FDD) dBm -79 -79 Default value
Qrxlevmin(TDD) dBm -81 -81 Default value
Srxlev* dB 19 “Off”
T1 P-CCPCH dBm/1.28 MHz -62 “Off”
CPICH_Ec dBm/3.84 MHz “Off” -60
T2 P-CCPCH dBm/1.28 MHz “Off” -62
Srxlev* dB “Off” 19
CPICH_Ec dBm/3.84 MHz -60 -70
T3 P-CCPCH dBm/1.28 MHz -62 -72
Srxlev* dB 19 9
T4 P-CCPCH dBm/1.28 MHz -62 “Off”
ETSI

U-S Message
13 described in TS 34.108 subclause 7.2.2.3.3
are performed on Cell 5.
Cell 2?
A information.
17 The SS changes Cell 1, Cell 2, Cell 5 and Cell - - - -
6.3.3.3.2-1 and table 6.3.3.3.2-2.
NOTE: The UE performs RAU and the RRC
1 and table 6.3.3.3.2-2.
NOTE: The UE performs RAU and the RRC
39 The SS changes Cell 1, Cell 2 and Cell 7 level - - - -
according to row "T4" in table 6.3.3.3.2-1 and
table 6.3.3.3.2-2.
E-UTRAN Cell 2 within 6 mins from "T4" to the
time RRCConnectionRequest received by SS?
Table 6.3.3.3.3-1: Conditions for specific message contents

in Table 6.3.3.3.3-2
ETSI
Table 6.3.3.3.3-2: SystemInformationBlockType1 for Cell 1 and Cell 2 (preamble and all steps, Table
6.3.3.3.2-3)

TRUE Cell 2
1 Cell 2
}
}
}

start 2
range n4
}
}
Table 6.3.3.3.3-4: System Information Block type 19 for Cell 5 and Cell 7 (Pre-test conditions and all
steps, Table 6.3.3.3.2-3

priority 5 Higher priority
than E-UTRA
}
(SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE
earfcn[n] Same downlink EARFCN
as used for cell 1
priority[n] 4
}
}
ETSI

as used for cell 5
}
as used for cell 5
}
}
6.3.4 Inter-RAT cell reselection / From UTRA CELL_PCH state to E-

UTRA RRC_IDLE CSG cell
(1)
with { UE in UTRA Cell PCH state and UE’s Allowed CSG list is not empty }
ensure that {
when { UE detects a suitable CSG cell that is not the strongest cell on that frequency }
then { UE does not reselect to the CSG cell }
}
(2)
with { UE in UTRA Cell PCH state and UE’s Allowed CSG list is not empty }
ensure that {
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, 5.2.6.4.1, TS 36.304
clause 5.2.4.8.1, 5.2.4.6, 5.2.4.8.2, 5.2.4.1, TS 25.133 clause 4.2.2.11.2 and TS 25.331, Annex E.
[TS 25.304, clause 5.2.6.4.1]
NOTE: The UE autonomous search function, per UE implementation, determines when and/or where to search for
allowed CSG cells.
ETSI
[TS 25.133, clause 4.2.2.11.2]

Note1
Note1
EARFCN N/A Channel 2
Note1
code 1
Note1
(Already stored
in UE whitelist
from previous
visit)
visited by UE
Note2
CPICH_ RSCP dBm -100
CPICH_Ec/Ior dB -10
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
Note2
code for cell 1 and the EARFCN and physical cell identity for cell 2 shall
ETSI
[TS 36.304, clause 5.2.4.8.1]
(5.2.4.6.).
[TS 36.304, clause 5.2.4.6]
where:

[TS 36.304, clause 5.2.4.8.2]
[TS 36.304, clause 5.2.4.1]
(re)selection.
ETSI

(bit
number)
3 Undefined
4 Undefined
System Simulator:
ETSI
- Cell 5.
- Cell 1, Cell 5 are not CSG cells.
UE:
- The UE’s Allowed CSG list is not empty and it includes the CSG ID of Cell 2. This is realized by using either
manual CSG selection or a USIM with field EFACSGL preconfigured.
Preamble:
- Cell 2 is a previously visited cell.
Table 6.3.4.3.2-1 and Table 6.3.4.3.2-2 illustrate the downlink power levels and other changing parameters to be
rows marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied
are described in the texts in this clause.

T0 EPRE TS36.508 Table 6.2.2.1-1.
Cell-specific RS
dBm/15kHz -85 -91
EPRE
qRxLevMinEUTRA
Cell-specific RS
dBm/15kHz -91 -85
EPRE
T2
qRxLevMinEUTRA

Srxlev* dB 19
Srxlev* dB 19
Srxlev* dB 19
ETSI

U-S Message
(Note 1)
minutes?
E-UTRAN Cell 2 within 6 minutes from "T2" to
the time RRCConnctionRequest received by
SS?

in Table 6.3.4.3.3-2
6.3.4.3.2-3)

TRUE Cell 2
1 Cell 2
}
}

start 2
range n4
}
}
ETSI
Table 6.3.4.3.3-4: System Information Block type 19 for Cell 5 (Pre-test conditions and all steps, Table
6.3.4.3.2-3

than E-UTRA
}
eutra-FrequencyAndPriorityInfoList SEQUENCE 1 entry the first entry only
priority[1] 4
}
}
Table 6.3.4.3.3-5: Void

carrierFreqListUTRA-FDD SEQUENCE (SIZE 1 entry the first entry only UTRA-FDD
}
carrierFreqListUTRA-TDD SEQUENCE (SIZE 1 entry the first entry only UTRA-TDD
}
}
6.3.5 Manual support for CSG ID selection

(1)
ensure that {
when { an intra-frequency CSG ID cell in the CSG subscription data for the UE at the network side
is manually selected }
then { UE camps on a cell with the selected CSG ID }
}
(2)
ensure that {
when { an inter-frequency CSG ID cell in the UE’s Allowed CSG list but not in the CSG subscription
data for the UE at the network side is CSG autonomously selected, and when trying to camp on the
selected cell the UE is rejected by the network by sending TRACKING AREA UPDATE REJECT with cause
#25 }
then { the UE updates the Allowed CSG list by deleting this CSG ID from the UE’s Allowed CSG
list }
}
ETSI
(3)
ensure that {
when { an inter-frequency CSG ID cell not in the UE’s Allowed CSG list but in the CSG subscription
data for the UE at the network side is manually selected }
then { UE camps on the strongest cell with the selected CSG ID, performs a TAU procedure and
updates the UE’s Allowed CSG list by adding this CSG ID into the UE’s Allowed CSG list }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.5.1, clause
5.2.4.8.2, TS 23.122, clause 3.1A and clause 4.4.3.1.3.
[TS 36.304, clause 5.5.1]
In the UE on request of NAS, the AS shall scan all RF channels in the E-UTRA bands according to its capabilities to
find available CSG IDs of available CSG cells. On each carrier, the UE shall at least search for the strongest cell, read
its system information and report available CSG ID(s) belonging to the registered PLMN together with their “HNB
name” (if broadcast) to the NAS. The search for available CSG IDs may be stopped on request of the NAS.
[TS 36.304, clause 5.2.4.8.2]
[TS 23.122, clause 3.1A ]
If the MS supports CSG, it is provisioned with a list of allowed CSG identities and associated PLMN identities from the
USIM if the list is available in the USIM or as described in 3GPP TS 24.285 [47] if the list is not available in the USIM.
This list has zero or more entries. There are two modes of CSG selection:
- Manual mode: In this mode, the MS indicates to the user the list of available CSGs in the currently registered
PLMN. The list of CSGs presented to the user is not restricted by the Allowed CSG list stored in the MS. After
the user makes a selection, the MS camps on a cell with the selected CSG identity and may attempt to register
with the associated PLMN (see 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A]).
[TS 23.122, clause 4.4.3.1.3 ]
The MS displays to the user the CSGs that are available with the currently registered PLMN using all access
technologies which support CSGs and which are supported by the MS. For each entry in the list, an indication is
provided whether that CSG identity is in the Allowed CSG list stored in the UE for this PLMN. Additional
requirements for the display, including for the display of HNB name, can be found in 3GPP TS 22.011 [9].
The user may select a CSG from the available ones and the MS then camps on a cell with the selected CSG identity.
The MS attempts to perform a Location Registration on the currently registered PLMN if the selected CSG Identity is
not in the allowed CSG list stored in the MS.
System Simulator:
- Cell 1, Cell 6, Cell 3 and Cell 4.
- Cell 1 is not a CSG cell.
- CSG 4 (Cell 4), CSG 2 ( Cell 6), and CSG 3 (Cell 3)
- CSG 4 and CSG 3 are in the CSG subscription data for the UE, CSG 2 is not.
ETSI
- Cell 3 and Cell 4 have the same tracking areas
- System information combination 13 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 6 and Cell 3.
- System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.
- System information combination 7 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 4.
UE:
- CSG 2 is in the UE’s Allowed CSG list, while CSG 3 and CSG 4 is not. This is realized by using either manual
CSG selection or a USIM with field EFACSGL preconfigured.
Preamble:
- The UE is in state Registered, Idle mode (State 2) according to [18] on Cell 1.
various time instants of the test execution. Configurations marked "T0","T1", "T2", "T3" and "T4" are applied at the

T0 Cell-specific RS dBm/15k -65 Off Off Off Cell 1 serving cell
EPRE Hz
Srxlev* dB 75 - - -
T1 Cell-specific RS dBm/15k -71 Off Off -65
EPRE Hz
Srxlev* dB 69 - - 75
T2 Cell-specific RS dBm/15k -65 Off Off -95
EPRE Hz
Srxlev* dB 75 - - 45
T3 Cell-specific RS dBm/15k -71 -65 Off Off
EPRE Hz
Srxlev* dB 69 75 - -
EPRE Hz
Srxlev* dB 69 - 75 45
ETSI

U-S Message
selection and select CSG 4.
4 The SS changes Cell1 and Cell 4 levels - - - -
5- Steps 1 to 6 of the procedure described in TS - - - -
10 36.508 subclause 6.4.2.7 is performed on Cell
1.
1.
12 Void - - - -
13 The UE transmits an RRCConnectionRequest --> RRCConnectionRequest - -
on Cell 6 within the next 6 minutes [Note]
14 SS transmits an RRCConnectionSetup RRC: RRCConnectionSetup - -
<--
message.
15 The UE transmits a --> RRC: - -
RRCConnectionSetupComplete message to RRCConnectionSetupComplete
confirm the successful completion of the NAS: TRACKING AREA UPDATE
connection establishment and a TRACKING REQUEST
AREA UPDATE REQUEST message is sent to
update the registration of the actual tracking
area.
16 The SS transmits a TRACKING AREA <-- RRC: DLInformationTransfer - -
UPDATE REJECT message with cause #25 NAS: TRACKING AREA UPDATE
(not authorized for this CSG) to fail the UE’s REJECT
TAU on Cell 6.
17 The SS transmits an RRCConnectionRelease <-- RRC: RRCConnectionRelease - -
move to RRC_IDLE.
18 Void - - - -
A- procedure (steps 1 to 6) in TS 36.508
18F subclause 6.4.2.7indicate that the UE is
camped on Cell 1?
G RRCConnectionRequest on Cell 6 within the
next 6 minutes [Note]
6.3.5.3.2-1.
selection and select CSG 3.
21- Check: Does the test result of generic test - - 3 P
26 procedure (steps 1 to 6) in TS 36.508
camped on Cell 3?
27 Check: Is CSG 3 added in the UE’s Allowed - - 3 P
CSG list?
Note: 6 minutes is allowed for automatic cell reslection to inter-frequency CSG cell [TS 36.133, clause 4.2.2.10.1]
ETSI
Table 6.3.5.3.3-1: Conditions for table 6.3.5.3.3-2, 6.3.5.3.3-3 and 6.3.5.3.3-4
Cell 4 This condition applies to system information transmitted on Cell 4
Table 6.3.5.3.3-2: SystemInformationBlockType1 for Cell 6, 3 and 4 (preamble and all steps except
step 11, Table 6.3.5.3.2-2)

csg-Indication TRUE Cell 6
Cell 3
Cell 4
csg-Identity '000 0000 0000 0000 Cell 6
0000 0000 0010'B
'000 0000 0000 0000 Cell 3
0000 0000 0011'B
'000 0000 0000 0000 Cell 4
0000 0000 0100'B
}
}
Table 6.3.5.3.3-3: SystemInformationBlockType3 for Cell 4 (preamble and all steps, table 6.3.5.3.2-2)

q-Hyst dB20
}
}
Table 6.3.5.3.3-4: SystemInformationBlockType4 for Cell 6, 3 and 4 (preamble and all steps, table
6.3.5.3.2-2)

start 0 Indicates the
lowest physical
cell identity in the
range
range n12 Indicates the
number of
physical cell
identities in the
range (including
start).
}
}
ETSI
Table 6.3.5.3.3-5: SystemInformationBlockType9 for Cell 6, 3 and 4 (preamble and all steps except for
step 11, table 6.3.5.3.2-2)

hnb-Name “3gppTest_CSG2” Cell 6
“3gppTest_CSG3” Cell 3
“3gppTest_CSG4” Cell 4
}
Table 6.3.5.3.3-6: TRACKING AREA UPDATE REJECT (step 16, Table 6.3.5.3.2-2)

EMM cause ‘00011001’ B Not authorized for
this CSG
Table 6.3.5.3.3-7: TRACKING AREA UPDATE REQUEST (step 18C, Table 6.3.5.3.2-2)

EPS update type '000'B “TA updating” TA_only
EPS update type ‘010’B "combined TA/LA combined_
updating with IMSI TA_LA
attach"
6.3.6 Ignoring CSG cells in cell selection/reselection when allowed CSG

list is empty or not supported
(1)
with { UE in E-UTRA RRC_IDLE state and UE does not support Allowed CSG list or UE’s Allowed CSG list
is empty }
ensure that {
when { Srxlev < 0 for non-CSG cell and Srxlev > 0 for intra-frequency CSG cell and Srxlev > 0 for
inter-frequency CSG cell }
then { UE does not select the intra-freq CSG cell nor the inter-frequency CSG cell }
}
(2)
is empty }
ensure that {
when { Srxlev > 0 for non-CSG cell and Srxlev of non-CSG cell > Srxlev of intra-frequency CSG cell
and Srxlev of non-CSG cell < Srxlev of inter-frequency CSG cell }
then { UE selects the non-CSG cell }
}
(3)
is empty }
ensure that {
when { UE detects an intra-frequency CSG cell with Rn higher than Rs }
then { UE does not reselect to the intra-frequency CSG cell }
}
(4)
is empty }
ETSI
ensure that {
when { UE detects an inter-frequency CSG cell with Rn higher than Rs }
then { UE does not reselect to the inter-frequency CSG cell }
}
5.2.4.6 and TS 36.331, clause B.2.
[TS 36.304, clause 5.2.3.2]
Srxlev > 0
Where:
Where:

[TS 36.304, clause 5.2.4.6]
where:

The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2
ETSI
[TS 36.331, clause B.2]
In this release of the protocol, it is mandatory for the UE to support a minimum set of CSG functionality consisting of:
- Identifying whether a cell is CSG or not;
- Ignoring CSG cells in cell selection/reselection.
System Simulator:
- Cell 1 is not a CSG cell.
- Cell 2 and Cell 3 are CSG cells.
- System information combination 13 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 2 and
Cell 3.
UE:
- If pc_Allowed_CSG_list, the UE’s Allowed CSG list is empty. This is realized by using either manual CSG
selection or a USIM with field EFACSGL preconfigured.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows marked "T1",
"T2" and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in

Cell-specific RS dBm/15k -115 -97 -85 SrxlevCell 1 < 0 and SrxlevCell 3 >
EPRE Hz SrxlevCell 2 > 0.
T0 Qrxlevmin dBm -106 -106 -106
Qhyst dB 0 0 0
Srxlev* dB -9 9 21 Cell 3 is the strongest cell
Cell-specific RS dBm/15k -85 -91 -73 SrxlevCell 3 > SrxlevCell 1 > SrxlevCell 2
T1 EPRE Hz > 0.
Srxlev* dB 21 15 33 Cell 3 is the strongest cell
T2 Cell-specific RS dBm/15k -85 -79 -115 The power level values are assigned
EPRE Hz to satisfy RCell 1 < RCell 2.
T3 Cell-specific RS dBm/15k -85 -115 -73 The power level values are assigned
EPRE Hz to satisfy RCell 1 < RCell 3.
ETSI

U-S Message
RRCConnectionRequest on Cell 2 or Cell 3
within 60 seconds?
1.
1.
seconds?
1.
seconds?
Table 6.3.6.3.3-1: Conditions for tables 6.3.6.3.3-2 and 6.3.6.3.3-4
Table 6.3.6.3.3-2: SystemInformationBlockType1 for Cell 1, 2 and 3 (Pre-test conditions and all steps,
Table 6.3.6.3.2-2)

TRUE Cell 2
Cell 3
'000 0000 0000 0000 Cell 2
0000 0000 0010'B
'000 0000 0000 0000 Cell 3
0000 0000 0011'B
}
}
ETSI
Table 6.3.6.3.3-3: SystemInformationBlockType3 for Cell 1, 2 and 3 (Pre-test conditions and all steps,
table 6.3.6.3.2-2)

q-Hyst dB0
}
}
Table 6.3.6.3.3-4: SystemInformationBlockType4 for Cell 2 and 3 (Pre-test conditions and all steps,
table 6.3.6.3.2-2)

start 2 Cell 2
3 Cell 3
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
6.3.7 Inter-RAT Cell reselection from E-UTRA idle non-CSG cell to a

UTRA CSG cell
(1)
with { UE in E-UTRA RRC_IDLE state and UE’s Allowed CSG list is not empty }
ensure that {
when { UE detects a suitable UTRA CSG cell previously visited }
then { UE selects the suitable UTRA CSG cell irrespective of its lower priority than EUTRA
cells}
}
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.8, 4.3,
TS 25.304, clause 5.6.1, 5.2.3.1.2, TS 25.367, clause 6.1, 7.2.3 and TS 36.133, clause 4.2.2.10.2.
[TS 36.304, clause 5.2.4.8]
In addition to normal cell reselection, the UE shall use an autonomous search function to detect allowed CSG cells on
non-serving frequencies, including inter-RAT frequencies, when at least one CSG ID is included in the UE’s CSG
whitelist. The UE may also use autonomous search on the serving frequency. The UE shall disable the autonomous
search function for CSG cells if the UE’s CSG whitelist is empty.
If the UE detects one or more suitable CSG cells on another RAT, the UE shall reselect to one of them, if allowed
according to [19].
[TS 36.304, clause 4.3]
suitable cell:
ETSI
[TS 25.304, clause 5.6.1]
report available CSG ID(s) belonging to the registered PLMN together with their “HNB name” (if broadcast) to the
NAS. The search for available CSG IDs may be stopped on request of the NAS.
[TS 25.304, clause 5.2.3.1.2]
Where:
Squal = Q qualm eas – (Qqualm in + Qqualm inO ffset)
Srxlev = Q rxlevm eas – (Q rxlevm in + Qrxlevm inOffset) – Pcom pensation
Where:
the signalled values QqualminOffset and QrxlevminOffset are only applied when a cell is evaluated for cell selection as
a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]. During this periodic
search for higher priority PLMN the UE may check the S criteria of a cell using parameter values stored from a
different cell of this higher priority PLMN.
ETSI

for FDD cells.
QqualminOffset Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of
a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]
QrxlevminOffset Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of
[TS 25.367, clause 6.1]
During manual CSG ID selection a UE is allowed to perform Location Registration procedure on a CSG cell whose
CSD ID is not in the CSG whitelist.
Based on the outcome of a Location Registration procedure initiated on a CSG cell, the UE’s CSG whitelist is updated.
[TS 25.367, clause 7.2.3]
Inter-RAT reselection to an allowed CSG cell is supported when the UE is camped on another RAT. The UE
requirements are defined in the specifications of the concerned RAT.
[TS 36.133, clause 4.2.2.10.2]
The UE shall perform search and reselection to an allowed inter-RAT UTRAN FDD CSG cell that has met CSG
reselection criterion defined in [1] and that is in its whitelist, within 6 minutes in the conditions shown in table
4.2.2.10.2-1. There is no need for statistical testing of this requirement.
ETSI
Table 4.2.2.10.2-1: Parameters for CSG inter-RAT UTRAN FDD reselection

Note1
EARFCN Channel 1 N/A
Note1
UARFCN N/A Channel 2
Note1
Physical cell identity 1 N/A
Primary scrambling code N/A Scrambling
Note1
code 2
(Already
stored in UE
whitelist from
previous visit)
visited by UE
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
Note2
Note2
CPICH_RSCP dBm -100
CPICH_Ec/Ior dB -10
AICH_Ec/Ior dB N/A -15
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
identity for cell 1 and the UARFCN and scrambling code for cell 2 shall
System Simulator:
- Cell 1 and Cell 2 are E-UTRAN cells
- Cell 5 and Cell 7 are UTRAN cells
- Cell 5 is a UTRA CSG cell
UE:
ETSI
Preamble:
- UE is in state Registered, Idle Mode (state 2) according to [18] in Cell 1.
Tables 6.3.7.3.2-1 & 6.3.7.3.2-2 illustrate the downlink power levels and other changing parameters to be applied for
marked "T1","T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values shall be
Table 6.3.7.3.2-1: Time instances of cell power level and parameter changes for E-UTRA Cell 1 and
Cell 2

Cell-specific RS
dBm/15kHz -85 OFF
EPRE
Qrxlevmin dBm -106 -106 Default value
T0
Qrxlevminoffset dB 0 0 Default value
Qhyst dB 0 0 Default value
Srxlev* dB 21 N/A Cell 1 is the strongest cell
Cell-specific RS
dBm/15kHz -85 OFF
T1 EPRE
Srxlev* dB 21 N/A
Cell-specific RS
dBm/15kHz OFF -85
T2 EPRE
Srxlev* dB N/A 21
Cell-specific RS
dBm/15kHz -85 -91
T3 EPRE
Srxlev* dB 21 15
Cell-specific RS
dBm/15kHz -85 OFF
T4 EPRE
Srxlev* dB 21 N/A
Table 6.3.7.3.2-2: Time instances of cell power level and parameter changes for UTRA Cell 5 and Cell
7

CPICH_Ec dBm/3.84 MHz OFF OFF Camping on Cell 1 is guaranteed
PCCPCH RSCP dBm/1.28 MHz OFF OFF Camping on Cell 1 is guaranteed
T0 Qrxlevmin (FDD) dBm -79 -79 Default value
Qrxlevmin (TDD) dBm -81 -81 Default value
Srxlev* dB N/A N/A
T1 CPICH_Ec dBm/3.84 MHz -60 -66 SrxlevCell 5 > 0, for FDD
PCCPCH RSCP dBm/1.28 MHz -62 -68 SrxlevCell 5 > 0, for TDD
Srxlev* dB 19 13 Cell 5 becomes the suitable cell
T2 CPICH_Ec dBm/3.84 MHz OFF OFF
PCCPCH RSCP dBm/1.28 MHz OFF OFF
Srxlev* dB N/A N/A
T3 CPICH_Ec dBm/3.84 MHz OFF -66
PCCPCH RSCP dBm/1.28 MHz OFF -68
Srxlev* dB N/A 13
T4 CPICH_Ec dBm/3.84 MHz -60 -66 SrxlevCell 5 > 0,for FDD
ETSI

U-S Message
information.
2 UE performs manual CSG ID selection. CSG - - - -
Identity ('000 0000 0000 0000 0000 0000
0010'B) is selected manually and added in
UE’s Allowed CSG list.
3- Steps 1 to 10 of the generic test procedure - - - -
performed on UTRA CSG Cell 5.
7 levels according to the row "T2" in table
6.3.7.3.2-1 and table 6.3.7.3.2-2.
21 36.508 Table 6.4.2.7A-1 is performed on Cell
2.
levels according to the row "T3" in table
6.3.7.3.2-1 and table 6.3.7.3.2-2.
1.
A information.
according to the row "T4" in table 6.3.7.3.2-1
and table 6.3.7.3.2-2.
37 generic test procedure in TS 36.508 subclause
UTRAN CSG Cell 5 in 6 mins from "T4" to the
time RRC CONNECTION REQUEST received
by SS?
Table 6.3.7.3.3-1: Void
Table 6.3.7.3.3-2: Void
ETSI
6.3.7.3.2-3)

cellReselectionPriority[1] 3 Lower priority than
E-UTRA
}
E-UTRA
}
}
Table 6.3.7.3.3-4: Master Information Block for Cell 5 (preamble and all steps, Table 6.3.7.3.2-3)
Derivation Path: 34.108 clause 6.1.0a.3

- CSG Indicator TRUE
Table 6.3.7.3.3-5: System Information Block type 3 for Cell 5 (preamble and all steps, Table 6.3.7.3.2-
3)
Derivation Path: 34.108 clause 6.1.0b

- CSG Identity '000 0000 0000 0000
0000 0000 0010'B
- CSG PSC Split Information
- Start PSC 104
- Number of PSCs 5
- PSC Range 2 Offset Not present
Table 6.3.7.3.3-6: System Information Block type 19 for Cell 5 and Cell 7 (preamble and all steps,
Table 6.3.7.3.2-3)

priority 3 Lower priority than
E-UTRA
}
priority[1] 4
}
}
6.3.8 Inter-RAT CSG Cell Reselection from E-UTRA CSG cell to UTRA
CSG cell
(1)
with { UE in E-UTRA RRC_IDLE state and UE’s Allowed CSG list is not empty and EUTRA broadcasted as
being the higher priority RAT }
ETSI
ensure that {
when { UE detects a suitable UTRA CSG cell previously visited }
then { UE selects the suitable UTRA CSG cell irrespective of its lower priority than EUTRA cells
}
}
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.8.1,
5.2.4.8.2, 4.3, TS 25.304, clause 4.3, 5.6.1, 5.2.3.1.2, TS 25.367, clause 6.1, 7.4 and TS 36.133, clause 4.2.2.10.2.
Unless otherwise stated these are Rel-8 requirements.
[TS 36.304, clause 5.2.4.8.1]
In addition to normal cell reselection, to detect suitable CSG cells the UE shall use an autonomous search function for
CSG cells on non-serving frequencies when at least one CSG ID with associated PLMN identity is included in the UE’s
allowed CSG list. This UE autonomous search for CSG cells may also include CSG cells of RATs other than E-
UTRAN. The UE may also use autonomous search on the serving frequency. The UE shall disable the autonomous
search function for CSG cells if the UE’s allowed CSG list is empty.
...
If the UE detects one or more suitable CSG cells on another RAT, the UE shall reselect to one of them, if allowed
according to [19].
[TS 36.304, clause 5.2.4.8.2]
To search for suitable CSG cells on non-serving frequencies, the UE may use an autonomous search function. If the UE
detects a CSG cell on a non-serving frequency, the UE may reselect to the detected CSG cell if it is the highest ranked
cell on its frequency.
If the UE detects one or more suitable CSG cells on another RAT, the UE may reselect to one of them if allowed
according to [19].
[TS 36.304, clause 4.3]
suitable cell:
[TS 25.304, clause 4.3]
suitable cell:
ETSI
- The cell shall be part of either:
according to the latest information provided by the NAS.
- The cell is not barred, see subclause 5.3.1.1;
- The cell is part of at least one LA that is not part of the list of "forbidden LAs for roaming" [9], which belongs to
a PLMN that fulfils the first bullet above;
- The cell selection criteria are fulfilled, see subclause 5.2.3.1.2.
- For a CSG cell the CSG ID is part of the Allowed CSG list of the UE.
If the IE “Multiple PLMN List” [4] is broadcast in the cell, the cell is considered to be part of all LAs with LAIs
constructed from the PLMN identities in the “Multiple PLMN List” and the LAC broadcast in the cell.
[TS 25.304, clause 5.6.1]
report available CSG ID(s) belonging to the registered PLMN together with their “HNB name” (if broadcast) to the
NAS. The search for available CSG IDs may be stopped on request of the NAS.
[TS 25.304, clause 5.2.3.1.2]
Where:
Squal = Q qualm eas – (Qqualm in + Qqualm inO ffset)
Srxlev = Q rxlevm eas – (Q rxlevm in + Qrxlevm inOffset) – Pcom pensation
Where:
the signalled values QqualminOffset and QrxlevminOffset are only applied when a cell is evaluated for cell selection as
a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]. During this periodic
search for higher priority PLMN the UE may check the S criteria of a cell using parameter values stored from a
different cell of this higher priority PLMN.
ETSI

for FDD cells.
QqualminOffset Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of
QrxlevminOffset Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of
[TS 25.367, clause 6.1]
During manual CSG ID selection a UE is allowed to perform Location Registration procedure on a CSG cell whose
CSD ID is not in the CSG whitelist.
Based on the outcome of a Location Registration procedure initiated on a CSG cell, the UE’s CSG whitelist is updated.
[TS 25.367, clause 7.4]
For reselection between allowed CSG cells, the UE follows the same cell ranking rules as those defined for the UTRA
case in [2].
[TS 36.133, clause 4.2.2.10.2]
ETSI

Note1
EARFCN Channel 1 N/A
Note1
Note1
Note1
code 2
(Already stored
in UE whitelist
from previous
visit)
visited by UE
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
Note2
Note2
CPICH_RSCP dBm -100
CPICH_Ec/Ior dB -10
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
System Simulator:
- Cell 1, Cell 2 and Cell 5
- Cell 1 is an E-UTRA CSG cell
- Cell 5 is a UTRA CSG cell
ETSI
UE:
- The UE’s Allowed CSG list is not empty and it includes a CSG ID of Cell 1.
Preamble:
- UE is in state Registered, Idle Mode (state 2) according to [18] in Cell 1.
Tables 6.3.8.3.2-1 & 6.3.8.3.2-2 illustrate the downlink power levels and other changing parameters to be applied for
marked "T1", "T2" and "T3" are to be applied subsequently. The exact instants on which these values shall be applied
are described in the text in this clause.
Table 6.3.8.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cells

Cell-specific RS EPRE dBm/15kHz -85 -91
T0
Srxlev* dB 21 15 Cell 1 is the strongest cell and
camping on Cell 1 is guaranteed
T1
Srxlev* dB 21 15
T2
Srxlev* dB 21 15
T3
Srxlev* dB 15 21

CPICH_Ec dBm/3.84 MHz OFF Camping on Cell 1 is guaranteed
PCCPCH RSCP dBm/1.28 MHz OFF Camping on Cell 1 is guaranteed
T0 Qrxlevmin (FDD) dBm -79
Qrxlevmin (TDD) dBm -81 Default value
Srxlev* dB N/A
T1 CPICH_Ec dBm/3.84 MHz -60 SrxlevCell 5 > 0, for FDD
PCCPCH RSCP dBm/1.28 MHz -62 SrxlevCell 5 > 0, for TDD
Srxlev* dB 19
T2 PCCPCH RSCP dBm/1.28 MHz OFF
Srxlev* dB N/A
T3 CPICH_Ec dBm/3.84 MHz -60 SrxlevCell 5 > 0, for FDD
PCCPCH RSCP dBm/1.28 MHz -62 SrxlevCell 5 > 0, for TDD
Srxlev* dB 19
ETSI

U-S Message
information.
1 The SS change Cell 5 levels according to the - - - -
row "T1" in table 6.3.8.3.2-2.
2 UE performs manual CSG ID selection and - - - -
CSG Identity ('000 0000 0000 0000 0000 0000
0100'B) is selected manually and added in
UE’s Allowed CSG list.
12 described in TS 36.508 subclause 6.4.2.8 is
13 The SS changes Cell 5 levels according to the - - - -
row "T2" in table 6.3.8.3.2-2.
14- Steps 1 to 8 of the generic procedure - - - -
21 described in TS 36.508 Table 6.4.2.7A-1 are
A information.
6.3.8.3.2-1 and table 6.3.8.3.2-2.
- EXCEPTION: Steps 22Aa1-22Aa6 are optional - - - -
and depend on UE implementation (e.g. the
UE may detect Cell 2 as suitable for camping
before it detects Cell 5).
22 Steps 1 to 6 of the generic procedure - - - -
Aa described in TS 36.508 Table 6.4.2.7-1 are
1- performed on Cell 2.
22 NOTE: The UE performs a TAU procedure.
Aa
6
UTRAN Cell 5 in 6 mins from "T3" to the time
RRC CONNECTION REQUEST received by
SS?
Table 6.3.8.3.3-1: Conditions for Tables 6.3.8.3.3-2, 6.3.8.3.3-3, 6.3.8.3.3-4, 6.3.8.3.3-5, 6.3.8.3.3-6 and
6.3.8.3.3-7
ETSI
6.3.8.3.2-3)

csg-Indication TRUE Cell 1
0000 0000 0010'B
}
Cell 2
}
}

start 2
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
6.3.8.3.2-3)

E-UTRA
}
E-UTRA
}
}
ETSI

3)

- CSG Identity '000 0000 0000 0000
0000 0000 0100'B
- Start PSC 104
- Number of PSCs 5
3)

Priority 3 Lower priority than
E-UTRA
}
priority[1] 4
}
}
6.3.9 Manual CSG ID selection across PLMNs

(1)
ensure that {
when { a CSG cell not belonging to the Registered PLMN is manually selected }
then { UE selects the requested CSG cell }
}
(2)
with { UE having selected a CSG cell not belonging to the initial Registered PLMN }
ensure that {
when { the UE is no longer within coverage of the CSG cell }
then { UE returns to the stored duplicate PLMN selection mode and selects a cell on the initial
Registered PLMN }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause 4.4.3.1.3.3.
[TS 23.122, clause 4.4.3.1.3.3]
If the user selects a CSG in a PLMN that is different from the RPLMN, then the following applies:
ETSI
i) The MS shall store a duplicate of the RPLMN and a duplicate of the current PLMN selection mode;
ii) The MS shall enter into Manual mode of PLMN selection in state M4 (Trying PLMN) as defined in
subclause 4.3.1.2;
iii) The MS shall select the PLMN corresponding to the CSG and attempt to register on the selected CSG cell in the
PLMN; and
iv) If the registration fails or the MS is no longer in the coverage of the CSG, then the MS shall return to the stored
duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
System Simulator:
- Cell 1 and Cell 12 are not CSG cells.
- Cell 3 is a CSG cell.
- System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1 and
Cell 12.
Cell PLMN name

1 PLMN1
3 PLMN2
12 PLMN2
UE:
- The UE’s Operator CSG list is empty.
Preamble:
various time instants of the test execution. Configurations marked "T0", "T1" and "T2" are applied at the points
indicated in the Main behaviour description in Table 6.3.9.3.2-2.

-65 Off Off The power levels are such
T0 EPRE Hz
guaranteed.
Srxlev* dB 41 - -
T1 Cell-specific RS dBm/15k -65 -85 Off
EPRE Hz
Srxlev* dB 41 21 -
T2 Cell-specific RS dBm/15k -85 Off -65
EPRE Hz
Srxlev* dB 21 - 41
ETSI

U-S Message
"T1" in table 6.3.9.3.2-1.
1.
camped on Cell 1?
Table 6.3.9.3.3-2: SystemInformationBlockType1 for Cell 1, 3 and 12 (preamble and all steps, Table
6.3.9.3.2-2)

Cell 12
TRUE Cell 3
Cell 12
'000 0000 0000 0000 Cell 3
0000 0000 0011'B
}
}
ETSI
6.3.9.3.2-2)

start 3
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
6.3.10 Void
6.3.11 Void
6.3.12 Inter-RAT cell selection / From E-UTRA RRC_IDLE to UTRA_Idle /
CSG cell on same PLMN as previously visited CSG cell
(1)
with { UE in E-UTRA RRC IDLE state and UE’s Allowed CSG list is not empty }
ensure that {
when { UE in “any cell selection” state detects a strongest UTRAN CSG cell, previously not
visited, on the same PLMN and the same frequency as the previously visited weaker CSG cell}
then { UE selects the strongest previously not visited UTRAN CSG cell irrespective of stored CSG
PSC Split Information }
}
References: The conformance requirements covered in the present TC are specified in: TS 24.008 clause 4.7.5.1.3, TS
25.331 clause 8.6.2.4, TS 25.304 clauses 5.2.6.4.2, 5.2.8 and 5.6.1 and TS 36.304 clause 5.2.4.8.1.
[TS 24.008, clause 4.7.5.1.3]
If the MS has initiated the routing area updating procedure due to manual CSG selection and receives a ROUTING
AREA UPDATE ACCEPT message, and the MS sent the ROUTING AREA UPDATE REQUEST message in a CSG
cell, the MS shall check if the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list.
If not, the MS shall add that CSG ID and associated PLMN identity to the Allowed CSG list and the MS may add the
HNB Name (if provided by lower layers) to the Allowed CSG list if the HNB Name is present in neither the Operator
CSG list nor the Allowed CSG list.
[TS 25.331, clause 8.6.2.4]
The UE shall:
1> if the IE "CSG PSC Split Information" is included in a received message:
2> consider the CSG PSC split information received on this cell to be valid for:
3> the UARFCN of the carrier on which it was received;
3> any cell not referenced in SIB18, or when SIB18 is not broadcast, while the cell the UE is camped on has
a PLMN which is the same as the PLMN of the cell where the CSG PSC split information was received;
ETSI
3> any cell referenced in SIB18 that has the same PLMN as the PLMN of the cell in which the CSG PSC
split information was received;
3> while UE is not in Any Cell Selection state [4];
3> 24 hours from the time it was received.
NOTE 1: If the IE "CSG PSC Split Information" is received in both SIB3 and SIB11bis in the same cell then UE
behaviour is unspecified.
NOTE 2: The PLMN of a cell in the above paragraph is the PLMN in IE ‘PLMN identity’ of that cell.
NOTE 3: The 6 hour validity restriction (section 8.1.1.6) does not apply to this field.
[TS 25.304, clause 5.2.6.4.2]
While camped on a suitable CSG cell, the UE shall consider the frequency of the serving cell to be the highest priority
frequency (i.e. higher than the eight network configured values or highest HCS priority) and shall not reselect to non-
CSG cell as long as the serving cell remains the highest ranked cell on that frequency (This includes the case when the
UE has only dedicated priorities for other frequencies but not for the current frequency, i.e. the UE does not consider
the current frequency to be the lowest priority frequency according to rules in 5.2.6.1.2a and 5.2.6.1.4a). Cell
reselection rules as defined in section 5.2.6.1 are applied for cell reselection from a CSG cell to non-CSG cell.
[TS 25.304, clause 5.2.8]
Any Cell Selection state
In this state, the UE shall attempt to find an acceptable cell of an any PLMN to camp on, trying all RATs that are
[TS 25.304, clause 5.6.1]
available CSGs. On each carrier, the UE shall at least search for the strongest cell, read its system information and
available CSGs may be stopped on request of the NAS.
If NAS has selected a CSG and provided this selection to AS, the UE shall search for an acceptable or suitable cell
belonging to the selected CSG to camp on.
[TS 36.304, clause 5.2.4.8.1]
requirements specified in [10], when at least one CSG ID with associated PLMN identity is included in the UE’s CSG
whitelist. The UE may also use autonomous search on the serving frequency. The UE shall disable the autonomous
search function for CSG cells if the UE’s CSG whitelist is empty.
(5.2.4.6.).
If the UE detects one or more suitable CSG cells on another RAT, the UE shall reselect to one of them according to
[19].
ETSI
System Simulator:
- Cell 1 (non-CSG cell)
- Cell 5 and Cell 7 (CSG cells on the same PLMN)
UE:
Preamble:
- The UE is in state Registered, Idle mode (State 2) according to [18] on Cell 1.
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows marked "T1",
"T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described

CPICH_Ec dBm/3.84 MHz - “Off” “Off”
PCCPCH RSCP dBm/1.28 MHz - “Off” “Off”
Qrxlevmin dBm -106 - - Default value
T0 Qrxlevminoffset dB 0 - - Default value
Qhyst dB 0 - - Default value
Qrxlevmin (FDD) dBm - -79 -79 Default value
Qrxlevmin (TDD) dBm - -81 -81 Default value
Srxlev* dB 21 - -
Cell-specific RS EPRE dBm/15kHz “Off” - -
CPICH_Ec dBm/3.84 MHz - -60 “Off”
T1
PCCPCH RSCP dBm/1.28 MHz - -62 “Off”
Srxlev* dB - 19 -
CPICH_Ec dBm/3.84 MHz - “Off” “Off”
T2
PCCPCH RSCP dBm/1.28 MHz - “Off” “Off”
Srxlev* dB 21 - -
Cell-specific RS EPRE dBm/15kHz “Off” - -
CPICH_Ec dBm/3.84 MHz - -66 -60
T3 PCCPCH RSCP dBm/1.28 MHz - -68 -62
Both cells are suitable but
Srxlev* dB - 13 19
Cell 7 is stronger
ETSI

U-S Message
1 The SS changes cell levels according to the - - - -
row "T1" in table 6.3.12.3.2-1.
2 UE performs manual CSG ID selection to Cell - - - -
5. CSG Identity ('000 0000 0000 0000 0000
0000 0010'B) is selected manually and added
in UE’s Allowed CSG list.
performed on UTRA CSG Cell 5.
row "T2" in table 6.3.12.3.2-1.
1.
row "T3" in table 6.3.12.3.2-1.
23 Check: Does the UE transmit a RRC - RRC CONNECTION REQUEST 1 P
CONNECTION REQUEST message on Cell 7
within 6 mins?
24- Steps 2 to 8 of generic test procedure in TS - - 1 -
30 36.508 subclause 6.4.2.8 are performed on
UTRAN CSG Cell 7.
Table 6.3.12.3.3-1: Master Information Block for Cell 5 and Cell 7 (preamble and all steps, Table
6.3.12.3.2-2)

Table 6.3.12.3.3-2: System Information Block type 3 for Cell 5 (preamble and all steps, Table
6.3.12.3.2-2)

- CSG Identity '000 0000 0000 0000
0000 0000 0010'B
- Start PSC Primary Scrambling Code
of Cell 5
- Number of PSCs 5 This shall
not
encompas
s the PSC
of Cell 7
ETSI
Table 6.3.12.3.3-3: System Information Block type 3 for Cell 7 (preamble and all steps, Table
6.3.12.3.2-2)

- CSG Identity '000 0000 0000 0000
0000 0000 0010'B
6.4 Hybrid cells

6.4.1 Manual CSG ID selection / Hybrid cell whose CSG ID is not in the
Allowed CSG list nor Operator’s list
(1)
ensure that {
when { a hybrid cell whose CSG ID is not included in the Allowed CSG list nor Operator CSG List is
manually selected }
then { UE selects the requested hybrid cell }
}
(2)
with { UE camping on a non-CSG cell in which the UE previously selected a hybrid cell manually whose
CSG ID is not included in the Allowed CSG list nor Operator CSG List }
ensure that {
when { the hybrid cell the UE previously selected is activated }
then { UE does not reselect the hybrid cell against normal cell reselection criteria }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause 4.4.3.1.3.1
and 4.4.3.1.3.2, TS 23.401, clause 5.3.3.2, TS 36.133, clause 4.2.2.10.1 and TS 36.304, clause 5.4.2.9.
[TS 23.122, clause 4.4.3.1.3.1]
The HPLMN may configure the MS whether to provide to the user CSGs for a certain PLMN without any restriction or
to provide to the user only CSGs in the Operator CSG List for that PLMN. This configuration may be done either:
- in the USIM if the Operator CSG list is available in the USIM; or
- as described in 3GPP TS 24.285 [47].
In the absence of such configuration from the HPLMN for a certain PLMN, the MS shall by default provide to the user
CSGs for that PLMN without any restriction.
For PLMNs where no restriction is configured, the MS provides to the user the CSGs that are available and the
associated PLMNs using all access technologies which support CSGs (see 3GPP TS 23.003 [22A]) and which are
supported by the MS. For each entry in the list, an indication is provided whether that CSG identity is in the Allowed
CSG list or in the Operator CSG List stored in the MS for this PLMN.
For PLMNs where the MS is configured to provide to the user only CSGs in the Operator CSG List, the MS provides to
the user the CSGs that are available and in the Operator CSG list, using all access technologies which support CSGs
(see 3GPP TS 23.003 [22A]) and which are supported by the MS. For each entry in the list, the MS provides to the user
the associated PLMN and an indication that the CSG identity is in the Operator CSG List stored in the MS for this
PLMN.
Additional requirements for the display, including for the display of HNB name, can be found in 3GPP TS 22.220 [49].
The user may select a CSG from the indicated CSGs.
ETSI
If the MS has a PDN connection for emergency bearer services, manual CSG selection shall not be performed.
[TS 23.122, clause 4.4.3.1.3.2]
If the user selects a CSG whose CSG identity is not included in the Allowed CSG list or Operator CSG list, then the MS
shall attempt to register on a cell that corresponds to the CSG.
[TS 23.401, clause 5.3.3.2]
NOTE 7: If the UE receives a TAU Accept message via a hybrid cell, the UE does not add the corresponding CSG
ID to its Allowed CSG list. Adding a CSG ID to the UE's local Allowed CSG list for a hybrid cell is
performed only by OTA or OMA DM procedures.
[TS 36.133, clause 4.2.2.10.1]
The UE shall perform search and reselection to an allowed inter-frequency CSG cell that has met CSG reselection

Note1
E-UARFCN Channel 1 Channel 2
Note1
(Already stored
in UE whitelist
from previous
visit)
visited by UE
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
N oc dBm/15 kHz Off
[≥TBD] [≥TBD]
Note2
RSRP dBm/15 KHz
Note 1: For this requirement to be applicable, the E-UARFCN and physical cell
was visited previously.
of success on every attempt made by UE.
[TS 36.304, clause 5.2.4.9]
In addition to normal cell reselection rules, the UE shall use an autonomous search function to detect at least previously
visited hybrid cells whose CSG IDs are in the UE’s CSG whitelist according to the performance requirements specified
in [10]. The UE shall treat detected hybrid cells as CSG cells if the CSG ID of the hybrid cell is in the UE’s CSG
whitelist and as normal cells otherwise.
ETSI
System Simulator:
- Cell 1 and Cell 3 are E-UTRAN cells and have different tracking areas according to table 6.0.1-2.
- Cell 1 is a non-CSG cell.
- Cell 3 is a hybrid cell.
UE:
- the UE’s Allowed CSG list is empty. This is realized by using either manual CSG selection or a USIM with field
EFACSGL preconfigured.
- the UE’s Operator CSG list is empty. This is realized by using either manual CSG selection or a USIM with field
EFOCSGL preconfigured.
Preamble:
various time instants of the test execution. The configurations marked "T1" and "T2" are applied at the points indicated
in the Main behaviour description in Table 6.4.1.3.2-2.

T1 Cell-specific dBm/15kHz -97 -85 The power level values are assigned so that the UE
RS EPRE can detect Cell 3.
T2 Cell-specific dBm/15kHz -85 "Off" The power level values are assigned so that
RS EPRE camping on Cell 1 is guaranteed.
ETSI

U-S Message
according to row "T1" in Table 6.4.1.3.2-1.
7 Check: Does the UE transmit an --> RRCConnectionRequest 2 F
within 6 minutes?
indicate that the UE is in E-UTRA RRC_IDLE
state on Cell 1?

cellReselectionPriority[n] 3 lower priority than
the frequency for
Cell 1
}
}

csg-Identity '000 0000 0000 0000
0000 0000 0011'B
}
}
ETSI

cellReselectionPriority 3 lower priority than
the frequency for
Cell 1
}
}

}
}

start 4
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
6.4.2 Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-

CSG cell to E-UTRA RRC_IDLE member hybrid cell
(1)
ensure that {
then { UE selects the requested hybrid cell }
}
(2)
ensure that {
when { a previously visited E-UTRA member hybrid cell becomes the strongest cell on its frequency
}
then { UE reselects the E-UTRA member hybrid cell }
}
ETSI
5.2.4.8.1, and 36.133, clauses 4.2.2.10 and 4.2.2.10.1.
[TS 36.304, clause 5.2.4.9]
[TS 36.304, clause 5.2.4.8.1]
[TS 36.133, clause 4.2.2.10]
[TS 36.133, clause 4.2.2.10.1]
The UE shall perform search and reselection to an allowed inter-frequency CSG cell that has met reselection criterion
defined in [1] and that is in its whitelist, within [6] minutes in the conditions shown in table 4.2.2.10.1-1. There is no
need for statistical testing of this requirement.

Note1
E-UARFCN Channel 1 Channel 2
Note1
CSG identity Not sent Already stored
in UE whitelist
from previous
visit
visited by UE
PBCH_RA dB
PBCH_RB dB
PSS_RA dB 0 0
SSS_RA dB
PCFICH_RB dB
ETSI
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
N oc dBm/15 kHz Off
[≥TBD] [≥TBD]
Note2
RSRP dBm/15 KHz
was visited previously
Note 2: Chosen to ensure that CSG autonomous search has a high probability of
success on every attempt made by UE
System Simulator:
- System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1, Cell
11 and Cell 23.
- Cell 1, Cell 3, Cell 11 and Cell 23 have different tracking areas according to table 6.0.1-2.
UE:
- The UE’s Allowed CSG list contains the CSG ID of Cell 3. This is realized by using either manual CSG
Preamble:
various time instants of the test execution. Configurations marked "T0", "T1", "T2", "T3" and "T4" are applied at the
ETSI

-65 Off Off Off The power levels are such
T0 EPRE Hz
guaranteed.
Srxlev* dB 41 - - -
EPRE Hz
Srxlev* dB 41 21 - 15
T2 Cell-specific RS dBm/15k Off Off -65 Off The power levels are such
guaranteed.
Srxlev* dB - - 41 -
EPRE Hz
Srxlev* dB 41 - 15 21
EPRE Hz
Srxlev* dB 41 21 - 15
ETSI

U-S Message
6.4.2.3.2-1.
on Cell 11.
1.
on Cell 1.
1.
camped on Cell 3 within [6] min from T4 to the
time the RRCConnectionRequest is received
by the SS?
ETSI
Table 6.4.2.3.3-2: SystemInformationBlockType1 for Cell 1, 3, 11 and 23 (preamble and all steps,
Table 6.4.2.3.2-2)

csg-Indication FALSE
Cell 11
Cell 23
'000 0000 0000 0000 Cell 3
0000 0000 0011'B
}
}
6.4.2.3.2-2)

start 3
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
6.4.3 Inter-RAT cell reselection / From E-UTRA RRC_IDLE non-CSG cell

to UTRA_Idle member hybrid cell
(1)
ensure that {
when { a previously visited UTRA member hybrid cell becomes the strongest cell on its frequency }
then { UE reselects the suitable UTRA member hybrid cell irrespective of its lower priority than
EUTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, clause 5.6.1; TS
36.304, clauses 5.2.4.8.1 and 5.2.4.9; and TS 36.133, clauses 4.2.2.10 and 4.2.2.10.2.
[TS 25.304, clause 5.6.1]
ETSI
[TS 36.304, clause 5.2.4.8.1]
[TS 36.304, clause 5.2.4.9]
[TS 36.133, clause 4.2.2.10]
[TS 36.133, clause 4.2.2.10.2]
ETSI

Note1
E-UARFCN Channel 1 N/A
Note1
Note1
Note1
code 2
(Already stored
in UE whitelist
from previous
visit)
visited by UE
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
[≥TBD]
Note2
RSRP dBm/15 KHz
[≥TBD]
Note2
CPICH_Ec dBm
CPICH_Ec/Ior dB -10
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
be unchanged from when the CSG cell was visited previously.
of success on every attempt made by the UE.
System Simulator:
ETSI
UE:
Preamble:
- The UE is in state Registered, Idle Mode (state 2) according to [18] in Cell 1.
Table 6.4.3.3.2-1 & 6.4.3.3.2-2 illustrates the downlink power levels and other changing parameters to be applied for
the cells at various time instants of the test execution. Configurations marked "T0", "T1", "T2", "T3" and "T4" are
applied at the points indicated in the Main behaviour description in Table 6.4.3.3.2-3.
Cell 2

Cell-specific RS
dBm/15kHz -85 OFF
EPRE
T0
Cell-specific RS
dBm/15kHz -85 OFF
T1 EPRE
Srxlev* dB 21 N/A
Cell-specific RS
dBm/15kHz OFF -85
T2 EPRE
Srxlev* dB N/A 21
Cell-specific RS
dBm/15kHz -85 -91
T3 EPRE
Srxlev* dB 21 15
Cell-specific RS
dBm/15kHz -85 OFF
T4 EPRE
Srxlev* dB 21 N/A
7

Srxlev* dB N/A N/A
Srxlev* dB N/A N/A
Srxlev* dB N/A 15
ETSI

U-S Message
select Cell 5.
6.4.3.3.2-1 and table 6.4.3.3.2-2.
2.
6.4.3.3.2-1 and table 6.4.3.3.2-2.
1.
and table 6.4.3.3.2-2.
6.4.2.8 indicate that the UE is camped on Cell
5 within 6 mins from "T4" to the time RRC
CONNECTION REQUEST received by SS?
6.4.3.3.2-3)

E-UTRA
}
E-UTRA
}
}
ETSI

- CSG Indicator Not present
3)

- CSG Identity '000 0000 0000 0000
0000 0000 0010'B
- Start PSC 104
- Number of PSCs 5
Table 6.4.3.3.2-3)

Utra-PriorityInfoList SEQUENCE {
E-UTRA
}
priority[1] 4
}
}
6.4.4 Inter-RAT cell reselection / From E-UTRA RRC_IDLE non-member

hybrid cell to UTRA_Idle member hybrid cell
(1)
with { UE in E-UTRA RRC_IDLE state on a non-member hybrid cell and UE’s Allowed CSG list is not
empty }
ensure that {
when { a previously visited UTRA member hybrid cell becomes the strongest cell on its frequency }
then { UE reselects the suitable UTRA member hybrid cell irrespective of its lower priority than
EUTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, clause 5.6.1; TS
36.304, clauses 5.2.4.8.1 and 5.2.4.9; and TS 36.133, clauses 4.2.2.10 and 4.2.2.10.2.
[TS 25.304, clause 5.6.1]
ETSI
[TS 36.304, clause 5.2.4.8.1]
[TS 36.304, clause 5.2.4.9]
[TS 36.133, clause 4.2.2.10]
[TS 36.133, clause 4.2.2.10.2]
ETSI

Note1
E-UARFCN Channel 1 N/A
Note1
Note1
Note1
code 2
(Already stored
in UE whitelist
from previous
visit)
visited by UE
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
[≥TBD]
Note2
RSRP dBm/15 KHz
[≥TBD]
Note2
CPICH_Ec dBm
CPICH_Ec/Ior dB -10
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
be unchanged from when the CSG cell was visited previously.
System Simulator:
- Cell 1 and Cell 7 are not CSG cells.
- Cell 2 and Cell 5 are hybrid cells.
ETSI
UE:
Preamble:
- The UE is in state Registered, Idle Mode (state 2) according to [18] in Cell 1.
the cells at various time instants of the test execution. Configurations marked "T0", "T1", "T2", "T3", "T4" and "T5" are
Cell 2

Cell-specific RS
dBm/15kHz -85 OFF
EPRE
T0
Cell-specific RS
dBm/15kHz -91 -85
T1 EPRE
Srxlev* dB 15 21
Cell-specific RS
dBm/15kHz OFF -85
T2 EPRE
Srxlev* dB N/A 21
Cell-specific RS
dBm/15kHz -85 OFF
T3 EPRE
Srxlev* dB 21 N/A
Cell-specific RS
dBm/15kHz -91 -85
T4 EPRE
Srxlev* dB 15 21
Cell-specific RS
dBm/15kHz OFF -85
T5 EPRE
Srxlev* dB N/A 21
ETSI
7

Srxlev* dB N/A N/A
Srxlev* dB N/A N/A
Srxlev* dB N/A N/A
Srxlev* dB N/A 15
ETSI

U-S Message
2-8 Steps 1 to 6 of the procedure described in TS - - - -
36.508 subclause 6.4.2.7 is performed on Cell
2.
6.4.4.3.2-1 and table 6.4.4.3.2-2.
select Cell 5.
6.4.4.3.2-1 and table 6.4.4.3.2-2.
1.
6.4.4.3.2-1 and table 6.4.4.3.2-2.
2.
6.4.2.8 indicate that the UE is camped on Cell
5 within 6 mins from "T5" to the time RRC
CONNECTION REQUEST received by SS?
ETSI
6.4.4.3.2-3)

0000 0000 0011'B
}
}
Table 6.4.4.3.3-3: SystemInformationBlockType4 for Cell 2 (preamble and all steps, table 6.4.4.3.2-3)

start 4
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
6.4.4.3.2-3)

E-UTRA
}
E-UTRA
}
}

- CSG Indicator Not present
ETSI
3)

- CSG Identity '000 0000 0000 0000
0000 0000 0010'B
- Start PSC 104
- Number of PSCs 5
Table 6.4.4.3.2-3)

E-UTRA
}
priority[1] 4
}
}
6.4.5 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE

member hybrid cell
(1)
with { UE in UTRA IDLE state and UE’s Allowed CSG list is not empty }
ensure that {
when { a previously visited E-UTRA member hybrid cell becomes the strongest cell on its frequency
}
then { UE reselects the suitable E-UTRA member hybrid cell irrespective of its lower priority
than UTRA cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, clauses 5.2.6.4.1 and
5.2.6.5; TS 25.133, clauses 4.2.2.11 and 4.2.2.11.2; TS 36.304, clause 5.5.1.
[TS 25.304, clause 5.2.6.4.1]
ETSI
If the UE detects a suitable CSG cell on the same frequency it shall reselect this cell if the concerned CSG cell is the
highest ranked cell, according to 5.2.6.1.4.
[TS 25.304, clause 5.2.6.5]
visited hybrid cells whose CSG IDs are in the UE's CSG whitelist according to the performance requirements specified
[TS 36.304, clause 5.5.1]
In the UE on request of NAS, the AS shall scan all RF channels in the E-UTRA bands according to its capabilities to
find available CSG IDs. On each carrier, the UE shall at least search for the strongest cell, read its system information
and report available CSG ID(s) together with their “HNB name” (if broadcast) and PLMN(s) to the NAS. The search
for available CSG IDs may be stopped on request of the NAS.
[TS 25.133, clause 4.2.2.11]
[TS 25.133, clause 4.2.2.11.2]
ETSI
a) Parameter a) Unit a) Cell 1 a) Cell 2

Note1
Note1
E-UARFCN N/A Channel 2
Note1
code 1
Note1
(Already stored
in UE whitelist
from previous
visit)
visited by UE
[≥TBD]
Note2
CPICH_Ec dBm
CPICH_Ec/Ior dB -10
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
[≥TBD]
Note2
RSRP dBm/15 KHz
code for cell 1 and the E-UARFCN and physical cell identity for cell 2
shall be unchanged from when the CSG cell was visited previously.
System Simulator:
- Cell 1 and Cell 2 are E-UTRAN cells.
- Cell 5 and Cell 7 are UTRAN cells and have different routing areas.
ETSI
UE:
Preamble:
- The UE is in state Registered, Idle Mode (state 3 or 7) according to [5] in Cell 5.
the cells at various time instants of the test execution. Configurations marked "T0", "T1", "T2", "T3" and "T4" are
Cell 2

Cell-specific RS
dBm/15kHz -OFF OFF
EPRE
T0
Srxlev* dB N/A N/A
Cell-specific RS SrxlevCell 2 > 0
dBm/15kHz -85 -79
T1 EPRE
Cell-specific RS
dBm/15kHz OFF OFF
T2 EPRE
Srxlev* dB N/A N/A
Cell-specific RS
dBm/15kHz -85 OFF
T3 EPRE
Srxlev* dB 21 N/A
Cell-specific RS SrxlevCell 2 > 0
dBm/15kHz -85 -79
T4 EPRE
7

CPICH_Ec dBm/3.84 MHz -60 OFF Camping on Cell 5 is guaranteed
PCCPCH RSCP dBm/1.28 MHz -62 OFF Camping on Cell 5 is guaranteed
T1 CPICH_Ec dBm/3.84 MHz -60 OFF
PCCPCH RSCP dBm/1.28 MHz -62 OFF
Srxlev* dB 19 N/A
Srxlev* dB N/A 19
T3 CPICH_Ec dBm/3.84 MHz -60 -64
PCCPCH RSCP dBm/1.28 MHz -62 -66
Srxlev* dB 19 15
T4 CPICH_Ec dBm/3.84 MHz -60 OFF
PCCPCH RSCP dBm/1.28 MHz -62 OFF
Srxlev* dB 19 N/A
ETSI

U-S Message
select Cell 2.
24 described in TS 36.508 Table 6.4.2.7A-2 are

6.4.5.3.2-1 and table 6.4.5.3.2-2.
7.
6.4.5.3.2-1 and table 6.4.5.3.2-2.
5.
and table 6.4.5.3.2-2.
Cell 2 within 6 mins from "T4" to the time
RRCConnectionRequest received by SS?

in Table 6.4.5.3.3-3
ETSI
Table 6.4.5.3.2-3)

than E-UTRA
}
priority[1] 4
}
}
6.4.5.3.2-3)

0000 0000 0010'B
}
}

start 4
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.
}
}
ETSI
6.4.5.3.2-3)

cellReselectionPriority[1] 5 Higher priority
than E-UTRA
}
cellReselectionPriority[1] 5 Higher priority
than E-UTRA
}
}
6.4.6 Inter-RAT cell reselection / From UTRA CELL_PCH to E-UTRA

RRC_IDLE member hybrid cell
(1)
with { UE in UTRA Cell PCH state and UE’s CSG whitelist is not empty }
ensure that {
when { UE detects a suitable E-UTRA member hybrid cell that is not the strongest cell on that
frequency }
then { UE does not reselect to the E-UTRA member hybrid cell }
}
(2)
with { UE in UTRA Cell PCH state and UE’s CSG whitelist is not empty }
ensure that {
when { UE detects a suitable E-UTRA member hybrid cell previously visited }
then { UE reselects the suitable previously visited E-UTRA member hybrid cell irrespective of
the EUTRAN cell reselection priority }
}
References: The conformance requirements covered in the present TC are specified in: TS 25.304, 5.2.6.5, 5.2.6.4.1, TS
36.304 clause 5.2.4.9, 5.2.4.8.1, 5.2.4.6, 5.2.4.8.2, 5.2.4.1 and TS 25.133 clause 4.2.2.11.2.
[TS 25.304, clause 5.2.6.5]
visited hybrid cells whose CSG IDs are in the UE's CSG whitelist according to the performance requirements specified
[TS 25.304, clause 5.2.6.4.1]
ETSI
[TS 25.133, clause 4.2.2.11.2]
ETSI

Note1
Note1
E-UARFCN N/A Channel 2
Note1
code 1
Note1
(Already stored
in UE whitelist
from previous
visit)
visited by UE
[≥TBD]
Note2
CPICH_Ec dBm
CPICH_Ec/Ior dB -10
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB N/A
PDSCH_RA dB
PDSCH_RB dB
Note 1
OCNG_RA dB
Note 1
OCNG_RB dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
[≥TBD]
Note2
RSRP dBm/15 KHz
code for cell 1 and the E-UARFCN and physical cell identity for cell 2
shall be unchanged from when the CSG cell was visited previously
[TS 36.304, clause 5.2.4.9]
[TS 36.304, clause 5.2.4.8.1]
ETSI
(5.2.4.6.).
[TS 36.304, clause 5.2.4.6]
where:

[TS 36.304, clause 5.2.4.8.2]
[TS 36.304, clause 5.2.4.1]
(re)selection.
System Simulator:
- Cell 1 and Cell 2 are E-UTRAN Cells.
- Cell 5 is UTRAN Cell.
ETSI
- Cell 1, Cell 5 are not CSG or Hybrid CSG cells.
- Cell 2 is Hybrid CSG cell.
- System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cell 1.
UE:
- UE’s CSG whitelist contains the CSG ID of Cell 2.
This is realized by using either manual CSG selection or a USIM with field EFACSGL preconfigured.
Preamble:
- Cell 2 is a previously visited cell.
Table 6.4.6.3.2-1 and Table 6.4.6.3.2-2 illustrate the downlink power levels and other changing parameters to be
rows marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied
are described in the texts in this clause.

T0 EPRE TS36.508 Table 6.2.2.1-1.
Cell-specific RS
dBm/15kHz -85 -91
EPRE
qRxLevMinEUTRA
Cell-specific RS
dBm/15kHz -91 -85
EPRE
T2
qRxLevMinEUTRA

Srxlev* dB 19
Srxlev* dB 19
Srxlev* dB 19
ETSI

U-S Message
(Note 1)
minutes?
E-UTRAN Cell 2 within 6 minutes from T2 to
the time RRCConnctionRequest received by
SS?

in Table 6.4.6.3.3-2
6.4.6.3.2-3)

csg-Identity Not Present Cell 1
0000 0000 0001'B
}

csg-PhysCellIdRange
Start 4
Range Not present
}
ETSI
Table 6.4.6.3.3-4: System Information Block type 19 for Cell 5 (Pre-test conditions and all steps, Table
6.4.6.3.2-3

Priority 5 Higher priority
than E-UTRA
}
priority[1] 4
}
}

}
}
}
6.4.7 Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-

UTRA RRC_IDLE member hybrid cell
(1)
ensure that {
}
(2)
with { UE in GSM/GPRS Registered state and no RR connection and UE’s Allowed CSG list is not empty }
ensure that {
when { UE detects a suitable E-UTRA member hybrid cell previously visited }
}
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.3.2.4, TS
45.008, clause 6.6.7.1, TS 45.008, clause 6.6.7.2 and TS 36.304, clause 10.1.3.4.
ETSI
[TS 24.301, clause 5.5.3.2.4]
AREA UPDATE ACCEPT message, and the UE sent the TRACKING AREA UPDATE REQUEST message in a CSG
cell, the UE shall check if the CSG ID of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST
message is contained in the Allowed CSG list. If not, the UE shall add that CSD ID to the Allowed CSG list and the UE
may add the HNB Name (if provided by lower layers) to the Allowed CSG list if the HNB Name is present in neither
the Operator CSG list nor the Allowed CSG list.
[TS 45.008, clause 6.6.7.1a]
If a mobile station is a member of at least one Closed Subscriber Group then, in addition to normal cell reselection, the
MS shall use an autonomous search function to detect hybrid cells. The autonomous search function shall at least detect
previously visited hybrid cells whose CSG IDs are included in the CSG Whitelist of the MS.
NOTE: The autonomous search for hybrid cells does not imply that the MS needs to constantly check the CSG
IDs of all cells it sees, and the impact on battery consumption should be minimised.
If a neighbour cell has been detected as a hybrid cell and the CSG ID of the hybrid cell is included in the CSG Whitelist
of the MS, reselection to that cell shall follow the rules for CSG cells in subclause 6.6.7.1. Otherwise normal cell
reselection rules (see subclause 6.6.5 and 6.6.6) shall apply.
[TS 45.008, clause 6.6.7.1]
CSG Whitelist, then, in addition to normal cell reselection, the MS shall use an autonomous search function to detect
UTRAN and/or E-UTRAN CSG cells. The autonomous search function shall at least detect previously visited allowed
CSG cells.
NOTE 1: The autonomous search function is implementation dependent and controls when and/or where to search
If the strongest cell (see 3GPP TS 25.304 and 3GPP TS 36.304 for the definition of the strongest cell) which the MS has
detected on a UTRAN or E-UTRAN frequency during a time interval T_reselection is a suitable CSG cell (see 3GPP
TS 25.304 and 3GPP TS 36.304 for suitability criteria for UTRAN and E-UTRAN CSG cells respectively), the MS
shall reselect to this cell irrespective of the cell reselection rules applicable for the cell on which the MS is currently
camped.
The following requirements are valid for reselection to allowed CSG cells previously visited by the MS when the radio
configuration parameters, including the carrier frequency and PSC/PCI (whichever and if it is applicable) of the CSG
cell, non CSG cell and other neighbour cells, are unchanged from the most recent previous visit. The autonomous
search and cell re-selection to a previously visited allowed CSG cell shall meet the performance requirements defined as
follows:
- the MS shall perform search and re-selection to a previously visited allowed UTRAN FDD CSG cell, that has
met the CSG cell re-selection criterion defined above, within 6 minutes in the radio conditions specified for an
UTRAN FDD CSG cell in 3GPP TS 36.133 in terms of parameters for CSG inter-RAT UTRAN FDD
reselection; UARFCN and PSC shall be unchanged from the most recent previous visit of the UTRAN FDD
CSG cell; Serving GSM cell at RXLEV= -70 dBm, with 6 GSM neighbours at RXLEV= -75 dBm;
- the MS shall perform search and re-selection to a previously visited allowed E-UTRAN CSG cell, that has met
the CSG cell re-selection criterion defined above, within 6 minutes in the radio conditions specified for an E-
UTRAN CSG cell in 3GPP TS 25.133 in terms of parameters for CSG inter-RAT E-UTRA reselection; E-
UARFCN and PCI shall be unchanged from the most recent previous visit of the E-UTRAN CSG cell; Serving
GSM cell at RXLEV= -70 dBm, with 6 GSM neighbours at RXLEV= -75 dBm.
NOTE 4: The above performance requirements are minimum requirements defined to ensure the testability of
autonomous CSG search.
[TS 45.008, clause 6.6.7.2]
If NAS requests AS to search for available CSG IDs, the MS shall perform the search and report the results to NAS as
described in 3GPP TS 25.304 for UTRAN and as described in 3GPP TS 36.304 for E-UTRAN.
ETSI
If a CSG ID is manually selected by NAS, the MS shall behave as specified in 3GPP TS 25.304 or in 3GPP TS 36.304,
depending on the RAT type of the selected CSG cell.
[TS 45.008, clause 10.1.3.4]
CSG Whitelist, then, in addition to normal cell reselection, the MS shall use an autonomous search function to detect
UTRAN and/or E-UTRAN CSG cells and hybrid cells. The autonomous search function shall at least detect previously
visited allowed CSG cells and previously visited hybrid cells whose CSG IDs are included in the CSG Whitelist of the
MS.
System Simulator:
- Cell 1 and Cell 2 are E-UTRAN Cells.
- Cell 24 and Cell 25 are GERAN Cells.
- Cell 1, Cell 24 and Cell 25 are not CSG cells or hybrid cells.
- Cell 2 is E-UTRAN Hybrid Cell.
UE:
- The UE’s CSG whitelist contains the CSG ID of Cell 2. This is realized by using either manual CSG selection or
a USIM with field EFACSGL preconfigured.
Preamble:
Tables 6.4.7.3.2-1 and 6.4.7.3.2-2 illustrates the downlink power levels and other changing parameters to be applied for
ETSI

T0 EPRE TS36.508 Table 6.2.2.1-1.
Cell-specific RS
dBm/15kHz -91 -85
EPRE
T1
qRxLevMinEUTRA
EPRE TS 36.508 Table 6.2.2.1-1.
T2
Srxlev* dB “Off” “Off” S nonServingCell, Cell7 > Thresh Cell7,high
Cell-specific RS
EPRE
Cell-specific RS
dBm/15kHz -91 -85
EPRE
T4
qRxLevMinEUTRA
Table 6.4.7.3.2-2: Time instances of cell power level and parameter changes for GERAN cell

T0
RXLEV_ACCESS_MIN dBm -101 “Off”
C1* dB 21 “Off”
C1* dB 21 “Off”
“Off” The power levels are such that
T2
RXLEV_ACCESS_MIN dBm “Off” -101
C1* dB “Off” 21
RF Signal Level dBm -80 -90
T3 RXLEV_ACCESS_MIN dBm -101 -101
C1* dB 21 11
C1* dB 21 “Off”
ETSI

U-S Message
2 Call the registration procedure described in TS - - - -
34.123-3 subclause 6.10.2.7.1.1 performed on
Cell 24.
RR connection is released.
Cell 2?
6 The SS changes Cell 1, Cell 2, Cell 24 and - - - -
Cell 25 levels according to row "T2" in table
6.4.7.3.2-1 and table 6.4.7.3.2-2.
1 and table 6.4.7.3.2-2.
level according to row "T4" in table 6.4.7.3.2-1
and table 6.4.7.3.2-2.
Cell 2 within 6 mins?

csg-Identity '000 0000 0000 0000
0000 0000 0001'B
}

csg-PhysCellIdRange
Start 4
Range Not present
}
ETSI
Table 6.4.7.3.3-3: SYSTEM INFORMATION TYPE 2 Quarter for Cell 24 and Cell 25 (Pre-test conditions
and all steps, Table 6.4.7.3.2-3
Derivation Path: 36.508 clause 4.4.5, Table 4.4.5-1

Additions in release 8 H
Priority and E-UTRAN Parameters Description 1 Present
Serving Cell Priority Parameters Description 1 Present
GERAN_PRIORITY 5 Higher priority
than E-UTRA

{}
}
}
}
EUTRA Freq
}
}
}
}
EUTRA Freq
}
}
}
ETSI
7 Layer 2
For all layer 2 test cases, default values for periodicBSR-Timer, retxBSR-Timer and phr-Config shall be taken
according to the condition no_periodic_BSR_or_PHR as specified in TS 36.508 subclause 4.8.2.1.5 unless test case
specific values are given in the test case.
In all MAC and RLC handover test cases during the execution of generic test procedure defined in [18] section 4.5.3A
following specific message content should be used for RRC Connection Reconfiguration message transmitted at step 8
of the table 4.5.3.3-1 [18]
Table 7-1: PDCP-Config-DRB-AM

PDCP-Config-DRB-AM ::= SEQUENCE {
rlc-AM SEQUENCE {
statusReportRequired FALSE
}
}
7.1 MAC
7.1.1 Mapping between logical channels and transport channels
7.1.1.1 CCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID
(1)
with { UE in E-UTRA RRC_IDLE state and after transmitting a RRCConnectionRequest message }
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its T-CRNTI but including a reserved value
for LCID }
then { UE discards the MAC PDU }
}
(2)
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its T-CRNTI with value ‘00000’B as LCID }
then { UE forwards to upper layers the disassembled and demultiplexed SDU on logical channel
CCCH }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.11, 6.2.1 ,
5.3.3 and 6.1.2.
[TS 36.321, clause 5.11]
When a MAC entity receives a MAC PDU for the UE’s C-RNTI or Semi-Persistent Scheduling C-RNTI, containing
reserved or invalid values, the MAC entity shall:
- discard the received PDU.
[TS 36.321, clause 6.2.1]
The MAC header is of variable size and consists of the following fields:
ETSI
- LCID: The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or
the type of the corresponding MAC control element or padding as described in tables 6.2.1-1 and 6.2.1-2 for the
DL and UL-SCH respectively. There is one LCID field for each MAC SDU, MAC control element or padding
included in the MAC PDU. The LCID field size is 5 bits;
...
Table 6.2.1-1: Values of LCID for DL-SCH
Index LCID values

00000 CCCH
00001-01010 Identity of the logical channel
01011-11011 Reserved
11100 UE Contention Resolution Identity
11101 Timing Advance
11110 DRX Command
11111 Padding
[TS 36.321, clause 5.3.3]
The UE shall disassemble and demultiplex a MAC PDU as defined in subclause 6.1.2.
[TS 36.321, clause 6.1.2]
A MAC PDU consists of a MAC header, zero or more MAC Service Data Units (MAC SDU), zero, or more MAC
control elements, and optionally padding; as described in Figure 6.1.2-3.
Both the MAC header and the MAC SDUs are of variable sizes.
A MAC PDU header consists of one or more MAC PDU sub-headers; each subheader corresponds to either a MAC
SDU, a MAC control element or padding.
A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last subheader in the MAC PDU
and for fixed sized MAC control elements. The last subheader in the MAC PDU and sub-headers for fixed sized MAC
control elements consist solely of the four header fields R/R/E/LCID. A MAC PDU subheader corresponding to
padding consists of the four header fields R/R/E/LCID.
Figure 6.1.2-1: R/R/E/LCID/F/L MAC subheader
Figure 6.1.2-2: R/R/E/LCID MAC subheader
MAC PDU sub-headers have the same order as the corresponding MAC SDUs, MAC control elements and padding.
ETSI
MAC control elements, are always placed before any MAC SDU.
Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may
have any value and the UE shall ignore it.
When single-byte or two-byte padding is required, one or two MAC PDU sub-headers corresponding to padding are
placed at the beginning of the MAC PDU before any other MAC PDU subheader.
A maximum of one MAC PDU can be transmitted per TB per UE.
R/R/E/LCID
sub-header
R/R/E/LCID
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
... R/R/E/LCID/F/L
sub-header
R/R/E/LCID padding
sub-header
MAC header MAC Control MAC Control MAC SDU ... MAC SDU Padding
element 1 element 2 (opt)
MAC payload
Figure 6.1.2-3: Example of MAC PDU consisting of MAC header, MAC control elements, MAC SDUs
and padding
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18].
ETSI

U-S Message
EXCEPTION: Steps 1 to 4 shall be repeated - - - -
for decreasing reserved LCID values from
01011 to 11011.
1 The SS transmits a Paging message including <-- - - -
a matched identity.
2 The UE transmits an RRCConnectionRequest --> - - -
message.
3 The SS Transmits a valid MAC PDU <-- MAC PDU - -
containing RRCConnectionSetup, and
Contention Resolution Identity MAC Control
Element except for LCID in MAC Header set to
reserved value 11011 or lower (depending on
iteration number).
EXCEPTION: In parallel with step 4, UE may - - - -
execute parallel behaviour defined in table
7.1.1.1.3.2-2
4 Check: For 5 seconds after Step3, does the --> RRCConnectionSetupComplete 1 F
UE transmit RRCConnectionSetupComplete
message?
a matched identity.
message.
7 The SS transmits a valid MAC PDU containing <-- MAC PDU - -
RRCConnectionSetup, and Contention
Resolution Identity MAC Control Element and
LCID in MAC Header set correctly to CCCH
00000
8 Check: does the UE transmit an --> RRCConnectionSetupComplete 2 P
including SERVICE REQUEST message?
9- Steps 6 to 9 of the generic radio bearer - - - -
12 establishment procedure (TS 36.508 4.5.3.3-1)
are executed to successfully complete the
service request procedure.

U-S Message
message.
None.
7.1.1.2 DTCH or DCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID

(1)
with { UE in E-UTRA RRC_Connected state with DRB [Logical channel ID 3] established }
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its CRNTI but including a reserved value
for LCID }
then { UE shall not forward the disassembled and demultiplexed SDU on the configured logical
channels }
}
ETSI
(2)
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its CRNTI with value ‘00011’B as LCID }
then { UE shall forward the disassembled and demultiplexed SDU on the corresponding logical
channel }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 6.2.1, 5.3.3
and 6.1.2.
[TS 36.321, clause 6.2.1]
[Rel-8]
included in the MAC PDU. The LCID field size is 5 bits;
...
Index LCID values

00000 CCCH
11101 Timing Advance
11110 DRX Command
11111 Padding
[Rel-10]
the type of the corresponding MAC control element or padding as described in tables 6.2.1-1, 6.2.1-2 and 6.2.1-4
for the DL-SCH, UL-SCH and MCH respectively. There is one LCID field for each MAC SDU, MAC control
element or padding included in the MAC PDU. In addition to that, one or two additional LCID fields are
included in the MAC PDU, when single-byte or two-byte padding is required but cannot be achieved by padding
at the end of the MAC PDU. The LCID field size is 5 bits;
Table 6.2.1-1 Values of LCID for DL-SCH
Index LCID values

00000 CCCH
11011 Activation/Deactivation
11101 Timing Advance Command
11110 DRX Command
11111 Padding
[TS 36.321, clause 5.3.3]
ETSI
The UE shall disassemble and demultiplex a MAC PDU as defined in subclause 6.1.2.
[TS 36.321, clause 6.1.2]
A MAC PDU header consists of one or more MAC PDU sub-headers; each subheader corresponds to either a MAC
A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last subheader in the MAC PDU
and for fixed sized MAC control elements. The last subheader in the MAC PDU and sub-headers for fixed sized MAC
Figure 6.1.2-1: R/R/E/LCID/F/L MAC subheader
Figure 6.1.2-2: R/R/E/LCID MAC subheader
have any value and the UE shall ignore it.
ETSI
R/R/E/LCID
sub-header
R/R/E/LCID
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
... R/R/E/LCID/F/L
sub-header
R/R/E/LCID padding
sub-header
MAC payload
and padding
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18].
NOTE: In the following, the established DRB is assumed to have Logical channel ID 3
ETSI

U-S Message
EXCEPTION: - - - -
IF UE is Release 8 or Release 9, steps 1 and 2
are repeated for decreasing reserved LCID
values from 01011 to 11011
ELSE IF UE is Release 10 onwards, steps 1
and 2 are repeated for decreasing reserved
LCID values from 01011 to 11010.
a RLC PDU except for LCID in MAC Header
set to reserved value .
2 Check: does the UE transmit a Scheduling --> (SR) 1 F
Request on PUCCH within 5 seconds after
step 1?
containing RLC PDU with LCID in MAC
Header set correctly to DRB 00011.
4 Check: does the UE transmit a Scheduling --> (SR) 2 P
Request on PUCCH?
5 The SS sends an UL grant suitable for the loop <-- (UL Grant) - -
back PDU to transmitted
6 Check: does the UE transmit a MAC PDU with --> MAC PDU 2 P
LCID set to DRB 00011?
None.
7.1.2 RACH
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
(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 }
}
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]
ETSI
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.
System Simulator:
UE:
None.
Preamble:
- UE is in state Generic RB Established (state 3) according to [18] in cell 1.
columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are
ETSI

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

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 - - - -
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 Preamble) 1 P
PRACH corresponding to ra-PreambleIndex in
step 1?
3 The SS transmits Random Access Response <-- Random Access Response - -
on cell 2, with RAPID corresponding to ra-
PreambleIndex in step 1
4 Check: Does the UE sends on cell 2, a MAC --> MAC PDU 1 P
PDU containing (RRCConnectionReconfigurationC
RRCConnectionReconfigurationComplete? omplete)
indicates that UE is in E-UTRA
RRC_CONNECTED state in cell 2?
ETSI
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

RRCConnectionReconfiguration ::= SEQUENCE {
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 FDD
5.7.1-2)
ra-PreambleIndex 52 (see TS 36.211 Table TDD
5.7.1-3)
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
(1)
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 }
}
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]
ETSI
[TS 36.321, clause 5.1.4]
monitoring for Random Access Response(s) after successful reception of a Random Access Response containing the
...
powerRampingStep);
...
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).
System Simulator:
- Cell 1
ETSI
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18] in cell 1

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

radioResourceConfigCommon SEQUENCE {
rach-Configuration SEQUENCE {
ra-SupervisionInformation SEQUENCE {
preambleTransMax N4 PREAMBLE_TRA
NS_MAX
}
}
}
}
}
7.1.2.3 Correct selection of RACH parameters / Preamble selected by MAC itself /

Contention based random access procedure
(1)
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 }
ETSI
(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)
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 }
}
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]
...
- 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.
ETSI
- 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:
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;
- indicate a Random Access problem to upper layers.
...
System Simulator:
- Cell 1.
- System information set using parameters as specified in Table 7.1.2.3.3.3-1.
ETSI
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode, Test Mode Activated (State 2A) according to [18].
ETSI

U-S Message
1 The SS transmits a Paging message including - - - -
a matched identity.
2 Check: Does the UE transmit preamble on --> PRACH Preamble 1 P
PRACH using a preamble in group A defined
in SIB2 (numberOfRA-Preambles and
sizeOfRA-PreamblesGroupA)?
with RAPID corresponding to the transmitted
Preamble in step 4, including T-CRNTI and not
including Back off Indicator sub header.
6 The UE transmits an RRCConnectionRequest --> MAC PDU - -
message.
PRACH using a preamble belonging to group
A?
8 Check: Does the UE continue to repeatedly --> PRACH Preamble 2, 3 P
transmit for 2s after step 2 a preamble
belonging to group A?
Note: 2s is the value of T300.
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 <-- MAC PDU - -
PDCP SDU of size 320 bits[>208].
- 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.
PRACH using a preamble in group B defined
Preamble in step 15, including T-CRNTI and
not including Back off Indicator sub header.
17 The UE transmits a MAC PDU with C-RNTI -> MAC PDU - -
containing loop backed PDCP SDU
18 The SS ignores the UL MAC PDU and does - - - -
not allocate UL grant for the C-RNTI in step
17.
PRACH using a preamble belonging to group
B?
ETSI

Preamble in step 19
21 The UE transmits a MAC PDU containing loop --> MAC PDU - -
backed PDCP SDU
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.
Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1

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

RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit ms200
}
}
}
7.1.2.4 Random access procedure / Successful

(1)
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 }
ETSI
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 }
}
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]
- 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:
- 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:
subframe.
- else:
subframe and the next two consecutive subframes.
- else:
ETSI
- 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]
subframes and has length ra-ResponseWindowSize subframes The RA-RNTI associated with the PRACH in which the
RA-RNTI= t1 + _id+10*f_id
- if the Random Access Response contains a Back off Indicator sub header:
- set the back off parameter value in the UE as indicated by the BI field of the Back off Indicator sub
header and Table 7.2-1.
- else, set the back off parameter value in the UE to 0 ms.
- indicate thepreambleInitialReceivedTargetPower and the amount of power ramping applied to the latest
powerRampingStep);
- 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:
ETSI
- 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.
...
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
ETSI
E/T/R/R/BI E/T/RAPID E/T/RAPID E/T/RAPID

subheader subheader 1 subheader 2 ... subheader n
MAC header MAC RAR 1 MAC RAR 2 ... MAC RAR n Padding
(opt)
MAC payload
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.
a. 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 n + k1 ,
k1 ≥ 6 , 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.
System Simulator:
- Cell 1
- System information are set according to table 7.1.2.4.3.3-1
UE:
None.
ETSI
Preamble:

U-S Message
1 The SS transmits a Paging message including - - - -
a matched identity.
2 Check: does the UE transmit a preamble on --> PRACH Preamble 1 P
PRACH, in frame number X, subframe number
2, 5, 8 (FDD)/2,3,8(TDD)?
3 Check: does the UE transmit a preamble on --> PRACH Preamble 1,2 P
PRACH, in frame number X+1 or X+2,
subframe number 2, 5, 8 (FDD)/ 2,3,8 (TDD)?
PRACH, in frame number X+2, X+3 or X+4,
5 The SS transmits a Random Access <-- Random Access Response - -
Response with not-matching RA-Id, including
T-CRNTI and not including Back off Indicator
sub header.
PRACH in frame number X+4, X+5 or X+6,
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
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 Preamble 3 P
PRACH using a preamble in subframe number
2,5,8 for FDD and subframe number 2,3 or 8
for TDD?
not including Back off Indicator sub header.
message.
including ‘UE Contention Resolution Identity’
MAC control element with matching
‘Contention Resolution Identity’
15 The UE transmits an --> - - -
RRCConnectionSetupComplete message.
ETSI
Derivation path: 36.508 table 4.4.3.3.-1

mac-ContentionResolutionTimer Sf48 Timer for
contention
resolution is 48
subframes
ra-ResponseWindowSize sf10
}
}
prach-Configuration SEQUENCE {
prach-ConfigInfo SEQUENCE {
prach-ConfigurationIndex 10 As per table 5.7.1- FDD
2 of 36.211, this
results in PRACH
preamble
transmission start
in any frame
numbers and sub-
frame number 2,
5, 8
prach-ConfigurationIndex 9 As per table 5.7.1- TDD
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
}
}
}
}
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

(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 }
ETSI
then { UE transmits MAC PDU containing RRCConnectionRequest }

}
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]
monitoring for Random Access Response(s) after successful reception of a Random Access Response containing the
powerRampingStep);
- 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;
ETSI
- 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.
...
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
a matched identity.
2 Check: Does the UE transmit a preamble on --> PRACH Preamble 1 P
PRACH?
3 The SS transmits a MAC PDU addressed to <-- Random Access Response - -
UE RA-RNTI, containing multiple RAR’s but
none of the MAC sub headers contains a
matching RAPID
- 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 Preamble 1 P
PRACH?
5 The SS transmits a MAC PDU addressed to <-- Random Access Response - -
UE RA-RNTI, containing multiple RAR’s one
of the MAC sub headers contains a matching
RAPID
6 Check: Does the UE transmit a MAC PDU --> MAC PDU 2 P
containing RRCConnectionRequest message? (RRCConnectionRequest)
7 The SS sends a MAC PDU containing <-- MAC Control PDU - -
matching Contention Resolution Identity MAC
control element
7A SS transmit RRCConnectionSetup message <-- - - -
8 The UE transmit --> - - -
including SERVICE REQUEST message.

U-S Message
1 Check: Does the UE transmit an --> MAC PDU 1 F
RRCConnectionRequest message. (RRCConnectionRequest)
None.
7.1.2.6 Maintenance of uplink time alignment

(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)
ensure that {
ETSI
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)
ensure that {
when{ timeAlignmentTimer has expired or is not running and UL transmission is required}
then { UE triggers a RA Procedure }
}
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:
- start or restart timeAlignmentTimer.
- else, if the timeAlignmentTimer is not running:
- 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.1 Pre-test condition
System Simulator:
- Cell 1
ETSI
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.
ETSI

U–S Message
1 SS pages the UE <-- - - -
2 SS respond to UE Random Access request <-- MAC PDU(Random Access - -
by a Random Access Response with TA field Response (TA=600))
within message set to 600(FDD) or
160(TDD) (Note 2).
3 Check: Does UE send an --> MAC PDU 1 P
RRCConnectionRequest message in the first (RRCConnectionRequest)
scheduled UL transmission using the Timing
Advance value sent by the SS in step 2?
4 The SS transmits a valid MAC PDU <-- MAC PDU (UE Contention - -
containing “UE Contention Resolution Resolution Identity)
Identity” MAC control element with matching
“Contention Resolution Identity” and RA
Procedure considered a success.
5 The SS sends an RRCConnectionSetup <-- MAC PDU - -
message.
6 Check: Does the UE transmit an --> MAC PDU 1 P
RRCConnectionSetupComplete? (RRCConnectionSetupComplete)
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 <-- MAC PDU (Timing Advance - -
does not send any subsequent alignments. Command MAC Control Element)
9 After 600ms (0.8 * timeAlignmentTimer) SS <-- MAC PDU - -
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.
10 Check: For 0.2* timeAlignmentTimer does --> SR 2 P
UE transmit Scheduling Requests, but no
Random Access Preamble message?
(Note 1)
11 Void - - - -
12 Check: Does the UE transmit a Random --> Random Access Preamble 3 P
Access Preamble?
13 SS responds with a valid Random Access <-- MAC PDU (Random Access - -
Response Response (Temporary C-RNTI))
14 Check: Does the UE transmit a MAC PDU --> MAC PDU(RLC STATUS PDU 3 P
with C-RNTI containing RLC STATUS PDU (ACK_SN =1))
for the acknowledgement of the DL Data with
the Temporary C-RNTI set to the value
received in the Random Access Response
message??
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 Ts where NTA = TA ×16 and Ts = 1 (15000 × 2048)
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)
ETSI
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

SchedulingRequest-Configuration ::= CHOICE {
setup SEQUENCE {
dsr-TransMax n64 Max value allowed
}
}
7.1.2.7 MAC contention resolution / Temporary C-RNTI

(1)
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)
ensure that {
when { SS transmits a valid MAC PDU containing RRCConnectionSetup, but not including 'UE
Contention Resolution Identity' MAC control element }
}
(3)
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' }
}
(4)
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 a RRCConnectionSetupComplete message }
}
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]

retransmission;
ETSI
- 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;
- consider this Random Access procedure successfully completed.
- else
- consider this Contention Resolution not successful and discard the successfully decoded MAC
PDU.
System Simulator:
- Cell 1
UE:
None.
ETSI
Preamble:

U-S Message
1 The SS transmits a Paging message including <-- - 1 -
a matched identity.
2 The UE transmits a MAC PDU containing an --> MAC PDU 1 -
RRCConnectionRequest message.
3 Check: For time equal to ‘Contention --> PRACH preamble 1 F
Resolution Timer’, does UE send a PRACH
preamble?
4 Check: does the UE transmit a MAC PDU --> MAC PDU 1 P
containing an RRCConnectionRequest (RRCConnectionRequest)
message?
- 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 <-- MAC PDU 2 -
containing RRCConnectionSetup, but not (RRCConnectionSetup)
MAC control element
containing an RRCConnectionRequest (RRCConnectionRequest)
message?
MAC control element but with un matched
containing an RRCConnectionRequest
message?
containing an RRCConnectionSetupComplete (RRCConnectionSetupComplete)
message including SERVICE REQUEST
message?

U-S Message
1 Check: UE transmits a MAC PDU containing --> MAC PDU 2,3 F
an RRCConnectionSetupComplete message (RRCConnectionSetupComplete)
indicating acceptance of
RRCConnectionSetup message?
ETSI
7.1.2.7.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.7.3.2-1)

preambleTransMax N10 Max value
mac-ContentionResolutionTimer sf64 Max value
}
}
}
}
7.1.2.8 MAC contention resolution / C-RNTI

(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 }
}
[TS 36.321, clause 5.1.5]

retransmission;
- 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;
ETSI
- stop mac-ContentionResolutionTimer;
- consider this Random Access procedure successfully completed.
...
- else
- consider this Contention Resolution not successful and discard the successfully decoded MAC
PDU.
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.

T1 -85 -79
EPRE Hz
ETSI

U-S Message
1 The SS transmits a MAC PDU containing an <-- MAC PDU - -
handover to Cell 2, not including explicit
Random Access Preamble.
2 The UE transmits on cell 2 a MAC PDU --> MAC PDU - -
containing
RRCConnectionReconfigurationComplete,
including C-RNTI MAC control element. SS is
configured to not transmit RLC ACK for this
transmission.
3 SS Does not schedule any PDCCH - - - -
transmission for UE C-RNTI
4 Check: does the UE transmit a PRACH --> (PRACH preamble) 1 F
preamble within time equal to ‘Contention
Resolution Timer’?
5 Check: does the UE transmit on cell 2 a MAC --> MAC PDU (RLC SN = 0 ) 1 P
PDU containing
RRCConnectionReconfigurationComplete with
RLC SN 0, including C-RNTI MAC control
element?
6 SS sends PDCCH transmission for UE C-RNTI <-- - - -
7 Check: does the UE transmit MAC PDU --> MAC PDU (RLC SN = 0 ) 2 F
containing
RRCConnectionReconfigurationComplete with
RLC SN 0 within the next 2s?
8 Check: does the test result of CALL generic - - 2 -
procedure indicate that the UE is in E-UTRA
RRC_CONNECTED state on Cell 2?
Table 7.1.2.8.3.3-1: SystemInformationBlockType2 (all steps, Table 7.1.2.8.3.2-1)

preambleTransMax N10 Max value
mac-ContentionResolutionTimer sf64 Max value
}
}
}
}
ETSI
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

c1 CHOICE{
mobilityControlInformation SEQUENCE { MobilityControlInformatio
n-HO
targetCellIdentity PhysicalCellIdentity of
4.4.4.2)
eutra-CarrierFreq Not present
}
}
}
}
}
7.1.2.9 MAC back off indicator

(1)
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)
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)
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 }
}
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]
ETSI
...
...
- 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]
- 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 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.
ETSI
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
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

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
2 UE sends a Random Access Preamble --> Random Access Preamble - -
3 SS sends a Random Access Response with <-- Random Access Response(BI, - -
the back off parameter set to value Index field RAPID)
‘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.
4 Check: Does UE send a Random Access --> Random Access Preamble 1 P
Preamble while Timer_T1 is running?
Preamble in step 4, including T-CRNTI and not
including Back off Indicator sub header
5A The UE transmits an RRCConnectionRequest --> - - -
message.
5B The SS Transmits a valid MAC PDU <-- MAC PDU - -
ETSI
containing RRCConnectionSetup, and (RRCConnectionSetup)

5C The UE transmits an --> - - -
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 <-- - - -
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
7 UE sends a Random Access Preamble --> Random Access Preamble - -
8 SS sends Random Access Response with a <-- Random Access Response(BI, - -
back off parameter set to value Index field ‘x’ RAPID)
and the Random Access Preamble identifier
value set to the same value as received from
the UE in the Random Access Preamble.
9 Check: Does UE sends an --> MAC PDU 2 P
RRCConnectionRequest in the grant (RRCConnectionRequest)
associated to the Random Access ´Response
received in step 8?
10 The SS sends a Contention Resolution Failure. <-- MAC Control PDU (Un - -
The SS sets Timer_T1 to the Back off value ‘y’ matching UE Contention
associated with the Index value ‘x’ and starts Resolution Identity)
Timer_T1.
11 Check: Does UE send a Random Access --> Random Access Preamble 3 P
Preamble while Timer_T1 is running?
not including Back off Indicator sub header
message.
containing RRCConnectionSetup, and (RRCConnectionSetup)
20 The SS transmits an RRCConnectionRelease <-- - - -
move to RRC_IDLE.
None
ETSI
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)
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]:
ETSI
- 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]
[TS 36.321, clause 5.1.4]
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:
...
- 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);
...
ETSI
- 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’
- ⎡ DL
Resource block assignment – log 2 ( N RB DL
( N RB ⎤
+ 1) / 2) 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 PCMAX 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.
ETSI
Preamble:
7.1.2.10.1.3.2 Test procedure sequence
Table 7.1.2.10.1.3.2-1: Main behaviour

U-S Message
1 The SS transmits an <-- RRCConnectionReconfiguration - -
RRCConnectionReconfiguration message with
SCell (Cell 3) addition
2 The UE transmits an --> RRCConnectionReconfiguration - -
RRCConnectionReconfigurationComplete Complete
message to confirm SCell (Cell 3) addition.
3 The SS transmits an Activation MAC control <-- MAC PDU (Activation (C1=1)) - -
element to activate SCell (Cell 3).
4 The SS indicates a new transmission on <-- MAC PDU (CC1) - -
PDCCH of CC1 (Cell 1) and transmits a MAC
PDU (containing an RLC PDU )
Random Access Preamble on SCell (Cell 3)
- 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 Preamble) 1 P
PRACH using the same preamble index as
given in step 5 on SCell (Cell3)?
the same preamble index as given in step 5 on
SCell (Cell3)?
the same preamble index as given in step 5 on
SCell (Cell3)?
with RAPID corresponding to Preamble in step
5 on PCell (Cell 1).
11 The SS sends an UL grant suitable for <-- (UL Grant) - -
transmitting loop back PDU on Cell 3.
12 Check: Does the UE transmit a MAC PDU --> MAC PDU(CC2) 4, 5 P
containing the loop back PDU corresponding
to step 10?
13 The SS transmits a MAC PDU containing RLC <-- MAC PDU (CC2) - -
status PDU acknowledging reception of RLC
PDU in step 12
ETSI
Table 7.1.2.10.1.3.2-2: Parallel behaviour

U-S Message
1 The UE transmits a Scheduling Request on --> (SR) 2 P
PUCCH
to step 4?
PDU in step 3
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

c1 CHOICE{
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig SEQUENCE {
timeAlignmentTimerDedicated Infinity
}
}
}
}
}
}
Table 7.1.2.10.1.3.3-2: SchedulingRequest-Configuration (preamble)

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

MAC-MainConfig-RBC ::= SEQUENCE {
stag-ToAddModList-r11 SEQUENCE (SIZE Not present
(1..maxSTAG-r11)) OF SEQUENCE {
stag-Id-r11 1
timeAlignmentTimerSTAG-r11 infinity
}
}
ETSI
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

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
}
}
ETSI
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

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] See table 5.7.2-4 FDD
clause 4.4.2, Table 4.4.2- in TS 36.211 [41]
1A and clause 6.3.2.2 for PRACH format
Table 6.3.2.2-2 0-3
See TS 36.508 [18] See table 5.7.2-5 TDD
Table 6.3.2.2-2 4
prach-ConfigIndex 3 Typical value in FDD
real network for
FDD (see table
5.7.1-1 and 5.7.1-
2 in TS 36.211
[41])
51 Typical value in TDD
real network for
TDD (see table
5.7.1-3 and 5.7.1-
4 in TS 36.211
[41])
highSpeedFlag FALSE
zeroCorrelationZoneConfig
prach-FreqOffset See TS 36.508 [18] Channel-
clause 4.6.8 bandwidth-
dependent
parameter
}
}
uplinkPowerControlCommonSCell-v1130 Not present
SEQUENCE
}
Table 7.1.2.10.1.3.3-7: RadioResourceConfigDedicatedSCell-r10-f2 (Table 7.1.2.10.1.3.3-5)
ETSI
Derivation Path: 36.508, Table 4.6.3-19AA

RadioResourceConfigDedicatedSCell-r10 ::=
SEQUENCE {
physicalConfigDedicatedSCell-r10 PhysicalConfigDedicated
SCell-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
7.1.2.10.3 CA / Random access procedure / SCell / Intra-band non-contiguous CA

- 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
(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)
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 }
}
ETSI
(4)
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 }
}
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.
ETSI
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.1 Pre-test condition
System Simulator:
7.1.2.11.1.3.3-1 and 7.1.2.11.1.3.3-2.
UE:
None.
Preamble:
ETSI

U–S Message
RRCConnectionReconfiguration message
with SCell (Cell 3) and the related sTAG
addition.
2 The UE transmits an --> RRCConnectionReconfigurationCo - -
RRCConnectionReconfigurationComplete mplete
message to confirm SCell (Cell 3) and sTAG
addition.
5 The UE transmits a preamble on PRACH --> (PRACH Preamble) - -
using the same preamble index as given in
step 4 on SCell (Cell 3)
6 The SS transmits Random Access Response <-- MAC PDU(Random Access - -
with RAPID corresponding to Preamble in Response (TA=600(FDD) or
step 4 on PCell (Cell 1) and with TA field TA=160(TDD))
160(TDD) (Note 2).
Note: UE starts the
timeAlignmentTimerSTAG
8 60ms After step 7 the SS sends an UL grant <-- (UL Grant) - -
suitable for transmitting loop back PDU on
Cell 3.
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?
10 The SS transmits Timing Advance command <-- MAC PDU (Timing Advance - -
with TAG Id equalling to sTAG id. Command MAC Control Element)
Note: UE restarts the
timeAlignmentTimerSTAG.
12 60ms After step 11, the SS sends an UL <-- (UL Grant) - -
grant suitable for transmitting loop back PDU
on Cell 3.
to step 10 in the first scheduled UL
transmission using the Timing Advance
value sent by the SS in step 6?
14 Wait for the timeAlignmentTimerSTAG --> (SRS) 3 F
equalling to 750ms to expire.
Check: Does the UE send the SRS on the
SCell (Cell 3)?
16 The UE transmits a preamble on PRACH --> (PRACH Preamble) - -
using the same preamble index as given in
step 15 on SCell (Cell 3)
17 The SS transmits Random Access Response <-- MAC PDU(Random Access - -
with RAPID corresponding to Preamble in Response (TA=600 or
step 16 on PCell (Cell 1) and with TA field TA=160(TDD))
160(TDD) (Note 2).
ETSI
Note: UE starts the

18 SS transmits Timing Advance command with <-- MAC PDU (Timing Advance - -
TAG Id equalling to pTAG id 0. Command MAC Control Element)
timeAlignmentTimerDedicated for PCell to
apply the new TAT value configured in step
1.
19 300 ms after step 18, The SS transmits <-- MAC PDU (Timing Advance - -
Timing Advance command with TAG Id Command MAC Control Element)
equalling to sTAG id.
timeAlignmentTimerSTAG.
20 After 600ms (0.8 * <-- MAC PDU - -
timeAlignmentTimerDedicated for pTAG)
after step 18 SS sends a MAC PDU
containing a RLC PDU on cell 3 k.
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 --> Random Access Preamble 4 P
Access Preamble on PCell?
23 SS responds with a valid Random Access <-- MAC PDU (Random Access - -
Response on PCell. Response (Temporary C-RNTI))
transmitting loop back PDU on PCell.
to step 20?
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 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 Ts where NTA = TA ×16 and Ts = 1 (15000 × 2048)
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)

U-S Message
1 Check: Does the UE send the SRS on the --> (SRS) 4 F
SCell (Cell 3)?
ETSI
7.1.2.11.1.3.3 Specific Message Contents

c1 CHOICE{
}
}
}
}
}
}

setup SEQUENCE {
dsr-TransMax n8
}
}
Derivation Path: 36.508, Table 4.8.2.1.5-1, condition SCell_AddMod

timeAlignmentTimerDedicated sf750
stag-ToAddModList-r11 SEQUENCE (SIZE Not present
stag-Id-r11 1
timeAlignmentTimerSTAG-r11 sf750
}
mac-MainConfig-v1020 SEQUENCE {
sCellDeactivationTimer-r10 rf128
}
}
ETSI

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
}
ETSI
Derivation Path: 36.508, Table 4.6.3-13A, condition UL_CA

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] See table 5.7.2-4 FDD
Table 6.3.2.2-2 0-3
See TS 36.508 [18] See table 5.7.2-5 TDD
Table 6.3.2.2-2 4
prach-ConfigIndex 3 Typical value in FDD
real network for
FDD (see table
5.7.1-1 and 5.7.1-
2 in TS 36.211
[41])
51 Typical value in TDD
real network for
TDD (see table
5.7.1-3 and 5.7.1-
4 in TS 36.211
[41])
highSpeedFlag FALSE
zeroCorrelationZoneConfig
prach-FreqOffset See TS 36.508 [18] Channel-
clause 4.6.8 bandwidth-
dependent
parameter
}
}
uplinkPowerControlCommonSCell-v1130 Not present
SEQUENCE {
}
}
ETSI

SEQUENCE {
SCell-r10-DEFAULT
stag-Id-r11 1
}
}
7.1.2.11.2 CA / Maintenance of uplink time alignment / Multiple TA / Inter-band CA

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

contiguous CA
7.1.3 DL-SCH data transfer

7.1.3.1 Correct handling of DL assignment / Dynamic case
(1)
ensure that {
when { UE receives downlink assignment on the PDCCH for the UE’s C-RNTI and receives data in the
associated subframe and UE performs HARQ operation }
then { UE sends a HARQ feedback on the HARQ process }
}
(2)
ensure that {
when { UE receives downlink assignment on the PDCCH with a C-RNTI unknown by the UE and data is
available in the associated subframe }
then { UE does not send any HARQ feedback on the HARQ process }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 5.3.1
[TS 36.321, clause 5.3.1]
Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a particular UE
and provide the relevant HARQ information.
When the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI
during which it monitors PDCCH:
ETSI
- if a downlink assignment for this TTI has been received on the PDCCH for the UE’s C-RNTI, or Temporary
C-RNTI:
- if this is the first downlink assignment for this Temporary C-RNTI:
- consider the NDI to have been toggled.
- if the downlink assignment is for UE’s C-RNTI and if the previous downlink assignment indicated to the
HARQ entity of the same HARQ process was either a downlink assignment received for the UE’s Semi-
Persistent Scheduling C-RNTI or a configured downlink assignment:
- consider the NDI to have been toggled regardless of the value of the NDI.
- indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ
entity for this TTI.
System Simulator:
- Cell 1
7.1.3.1.3.3-1
UE:
None.
Preamble:
- The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is
executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no
data in uplink.

U-S Message
1 SS transmits a downlink assignment including <-- (PDCCH (C-RNTI)) - -
the C-RNTI assigned to the UE
2 SS transmits in the indicated downlink <-- MAC PDU - -
assignment a RLC PDU in a MAC PDU.
3 Check: Does the UE transmit an HARQ ACK --> HARQ ACK 1 P
on PUCCH?
4 SS transmits a downlink assignment to <-- (PDCCH (unknown C-RNTI)) - -
including a C-RNTI different from the assigned
to the UE
6 Check: Does the UE send any HARQ ACK on --> HARQ ACK 2 F
PUCCH?
NOTE 1: For TDD, the timing of ACK/NACK is not constant as FDD, see Table 10.1-1 of TS 36.213.
ETSI
Table 7.1.3.1.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)
Derivation path: 36.508 table 4.8.2.1.5-1

c1 CHOICE{
mac-MainConfig CHOICE {
}
}
}
}
}
}
Table 7.1.3.1.3.3-2: Void
Table 7.1.3.1.3.3-3: Void
7.1.3.2 Correct handling of DL assignment / Semi-persistent case

(1)
with { UE in E-UTRA RRC_Connected state with DRB established and sps-Configuration in DL is enabled
}
ensure that {
when { UE receives a DL assignment addressed to its stored SPS-CRNTI in SF-Num y and with NDI set
as 0 }
then { UE starts receiving DL MAC PDU in SF-Nums y+n*[semiPersistSchedIntervalDL] where ‘n’ is
positive integer starting at zero }
}
(2)
with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive
MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a DL assignment addressed to its SPS-CRNTI in SF-Num p and with NDI set as 0,
where p!= y+n*[semiPersistSchedIntervalDL] }
then { UE starts receiving DL MAC PDU in SF-Nums p+n*[semiPersistSchedIntervalDL] and stops
receiving DL MAC PDU at SF-Nums y+n*[semiPersistSchedIntervalDL]where ‘n’ is positive integer
starting at zero }
}
(3)
MAC PDU at SF-Num p+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a DL assignment [for retransmission] addressed to its SPS-CRNTI in SF-Num z and
with NDI set as 1, where z!= p+n*[semiPersistSchedIntervalDL] }
then { UE receives MAC PDU in SF-Num z as per the new grant for SPS-CRNTI }
}
(4)
ensure that {
when { UE receives a DL assignment addressed to its CRNTI in SF-Num p, such that p!=
y+n*[semiPersistSchedIntervalDL] }
ETSI
then { UE receives MAC PDU in SF-Num p as per assignment addressed to its C-RNTI }
}
(5)
with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS grant to receive MAC
PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a RRCConnectionReconfiguration including sps-Configuration with sps-
ConfigurationDL set as ‘disable’ and hence resulting in DL SPS grant deactivation }
then { UE deletes the stored sps-Configuration DL parameters and stops receiving DL MAC PDU’s as
per stored SPS assignment in SF-Num z+n*[semiPersistSchedIntervalDL] }
}
(6)
MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a PDCCH [for DL SPS explicit release according to Table 9.2-1A in TS 36.213]
addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p!=
z+n*[semiPersistSchedIntervalDL] }
then { UE sends an ACK to SS and releases the configured SPS assignment and stops receiving MAC
PDU in SF-Num z+n*[semiPersistSchedIntervalDL] as per assignment addressed to its SPS C-RNTI }
}
NOTE: SF-Num = [10*SFN + subframe] modulo 10240.
References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.3.1, 5.10 &
5.10.1, 36.331 clause 5.3.10.5, 36.300 clause 11.1.1 and 36.213 clause 9.2.
[TS 36.321, clause 5.3.1]
C-RNTI:
- else, if a downlink assignment for this TTI has been received on the PDCCH for the UE’s Semi-Persistent
Scheduling C-RNTI:
- if the NDI in the received HARQ information is 1:
- consider the NDI not to have been toggled;
- indicate the presence of a downlink assignment and deliver the associated HARQ information to the
HARQ entity for this TTI.
- else, if the NDI in the received HARQ information is 0:
ETSI
- if PDCCH contents indicate SPS release:
- clear the configured downlink assignment (if any);
- if timeAlignmentTimer is running:
- instruct the physical layer to transmit a positive acknowledgement.
- else:
- store the downlink assignment and the associated HARQ information as configured downlink
assignment;
- initialise (if not active) or re-initialise (if already active) the configured downlink assignment to start
in this TTI and to recur according to rules in subclause 5.10.1;
- set the HARQ Process ID to the HARQ Process ID associated with this TTI;
- consider the NDI bit to have been toggled;
- indicate the presence of a configured downlink assignment and deliver the stored HARQ information
to the HARQ entity for this TTI.
- else, if a downlink assignment for this TTI has been configured and there is no measurement gap in this TTI:
- instruct the physical layer to receive, in this TTI, transport block on the DL-SCH according to the configured
downlink assignment and to deliver it to the HARQ entity;
- indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the
For downlink assignments received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI and for
configured downlink assignments, the HARQ Process ID associated with this TTI is derived from the following
equation:
HARQ Process ID = [floor(CURRENT_TTI/(Downlink Semi-Persistent Scheduling Interval))] modulo Number of

Configured SPS Processes,
where CURRENT_TTI=[(SFN * 10) + subframe number], Downlink Semi-Persistent Scheduling Interval is the
periodicity of semi-persistent scheduling signalled via RRC and Number of Configured SPS Processes is the number of
HARQ processes allocated for semi-persistent scheduling signalled via RRC.
[TS 36.321, clause 5.10]
When Semi-Persistent Scheduling is enabled by upper layer, the following information is provided:
- Semi-Persistent Scheduling C-RNTI;
- Uplink Semi-Persistent Scheduling Interval semiPersistSchedIntervalUL and number of empty transmissions

before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the uplink;
- Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;
- Downlink Semi-Persistent Scheduling Interval semiPersistSchedIntervalDL and number of configured HARQ

processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is
enabled for the downlink;
When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or
configured assignment shall be discarded.
[TS 36.321, clause 5.10.1]
ETSI
After a Semi-Persistent downlink assignment is configured, the UE shall consider that the assignment recurs in each
subframe for which:
- (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * (Downlink Semi-Persistent Scheduling
Interval)] modulo 10240, for all N>0.
Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the configured downlink
assignment were (re-)initialised.
[TS 36.331, clause 5.3.10.5]
The UE shall:
1> reconfigure the semi-persistent scheduling in accordance with the received sps-Config:
[TS 36.300, clause 11.1.1]
In addition, E-UTRAN can allocate semi-persistent downlink resources for the first HARQ transmissions to UEs:
- RRC defines the periodicity of the semi-persistent downlink grant;
- PDCCH indicates whether the downlink grant is a semi-persistent one i.e. whether it can be implicitly reused in
the following TTIs according to the periodicity defined by RRC.
When required, retransmissions are explicitly signalled via the PDCCH(s). In the sub-frames where the UE has semi-
persistent downlink resource, if the UE cannot find its C-RNTI on the PDCCH(s), a downlink transmission according to
the semi-persistent allocation that the UE has been assigned in the TTI is assumed. Otherwise, in the sub-frames where
the UE has semi-persistent downlink resource, if the UE finds its C-RNTI on the PDCCH(s), the PDCCH allocation
overrides the semi-persistent allocation for that TTI and the UE does not decode the semi-persistent resources.
[TS 36.213, clause 9.2]
A UE shall validate a Semi-Persistent Scheduling assignment PDCCH only if all the following conditions are met:
- the CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-
RNTI
- the new data indicator field is set to ‘0’. In case of DCI formats 2 and 2A, the new data indicator field refers to
the one for the enabled transport block.
Validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-
1A.
If validation is achieved, the UE shall consider the received DCI information accordingly as a valid semi-persistent
activation or release.
If validation is not achieved, the received DCI format shall be considered by the UE as having been received with a
non-matching CRC.
Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation
DCI format 0 DCI format 1/1A DCI format 2/2A

TPC command for set to ‘00’ N/A N/A
scheduled PUSCH
Cyclic shift DM RS set to ‘000’ N/A N/A
Modulation and coding MSB is set to ‘0’ N/A N/A
scheme and
redundancy version
HARQ process number N/A FDD: set to ‘000’ FDD: set to ‘000’
TDD: set to ‘0000’ TDD: set to ‘0000’
Modulation and coding N/A MSB is set to ‘0’ For the enabled
scheme transport block:
MSB is set to ‘0’
Redundancy version N/A set to ‘00’ For the enabled
transport block:
set to ‘00’
ETSI
Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH Validation
DCI format 0 DCI format 1A

TPC command for scheduled set to ‘00’ N/A
PUSCH
Cyclic shift DM RS set to ‘000’ N/A
Modulation and coding scheme and set to ‘11111’ N/A

redundancy version
Resource block assignment and Set to all ‘1’s N/A
hopping resource allocation
HARQ process number N/A FDD: set to ‘000’
TDD: set to ‘0000’
Modulation and coding scheme N/A set to ‘11111’
Redundancy version N/A set to ‘00’
Resource block assignment N/A Set to all ‘1’s
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].
- The UL RLC SDU size is set to not return any data.
ETSI

U-S Message
1 The SS Transmits a DL assignment using UE’s <-- (DL SPS Grant) - -
SPS C-RNTI in SF-Num ‘Y’, NDI=0
2 The SS transmits in SF-Num ‘Y’, a DL MAC <-- MAC PDU - -
PDU containing a RLC PDU (DL-SQN=0)on
UM DRB
3 Check: Does the UE transmit a HARQ ACK? --> HARQ ACK 1 P
4 The SS transmits in SF-Num <-- MAC PDU - -

‘Y+X(semiPersistSchedIntervalDL)’, a DL MAC
DRB
SPS C-RNTI in SF-Num ‘P’, NDI=0;
(Where Y+X<P< Y+2X)
7 The SS transmits in SF-Num ‘P’, a DL MAC <-- MAC PDU - -
UM DRB
9 The SS transmits in SF-Num ‘Y+2X’, a DL <-- MAC PDU - -
MAC PDU containing a RLC PDU (DL-
SQN=3)on UM DRB
10 Check: Does the UE transmit a HARQ --> HARQ ACK/NACK 2 F
Feedback?
10A The SS Transmits a DL assignment using UE’s <-- (DL Grant) - -
C-RNTI in SF-Num
‘P+X(semiPersistSchedIntervalDL)’, NDI=0
‘P+X(semiPersistSchedIntervalDL)’, a DL MAC
UM DRB;
12 Void - - - -
13 Void - - - -
14 Void - - - -
‘P+2X(semiPersistSchedIntervalDL)’, a DL
SQN=4)on UM DRB
SPS C-RNTI in SF-Num in SF-Num
‘P+3X(semiPersistSchedIntervalDL)’ . (Note
1a)
MAC PDU containing 1 RLC PDU’s (DL-
SQN=5)on UM DRB;Note 1
19A Check: Does the UE transmit a HARQ NACK? --> HARQ NACK
EXCEPTION: Step 19b and 19c shall be
repeated until HARQ retransmission count = 3
is reached for MAC PDU at step 19 (Note 1b).
19b The SS Transmits a DL assignment using UE’s <-- (DL SPS Grant)
SPS C-RNTI in SF-Num ‘Z’, NDI=1;
Where (P+3X < Z <P+4X); The DL HARQ
process is same as in step 11
19c The SS re-transmits in SF-Num ‘Z’, a DL MAC <-- MAC PDU
ETSI

UM DRB; (Note 1a)
EXCEPTION: Up to 3 HARQ NACK from the
UE should be allowed at step 20 (Note 1b).
21 The SS Transmits a PDCCH [for DL SPS <-- PDCCH [for DL SPS explicit - -
explicit release] using UE’s SPS C-RNTI in SF- release]
Num ‘Q’, NDI=0; Where (P+3X< Q <P+4X).
SQN=6)on UM DRB;
Feedback?
SPS C-RNTI in SF-Num ‘P+6X’, NDI=0
26 The SS transmits in SF-Num ‘P+6X’, a DL <-- MAC PDU - -
SQN=6)on UM DRB
28 Void - - - -
29 Void - - - -
30 SS Transmits RRCConnectionReconfiguration - - - -
to disable SPS-ConfigurationDL
31 The UE transmits --> - - -
SQN=7) on UM DRB;
33 Check: Dose the UE transmit a HARQ --> HARQ ACK/NACK 5 F
Feedback?
Note 1: The DL assignment for C-RNTI and hence the size of MAC PDU is different in size than stored SPS C-RNTI
DL assignment in step 6. This assures UE is receiving DSCH data as per DL assignment for C-RNTI and not
as per stored grant for SPS C-RNTI.
Note 1a: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in
TBSize of 328 and having coding rate more than 1.
Note 1b: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption
that, given the radio conditions used in this test case, a UE soft combiner implementation should have
sufficient retransmissions to be able to successfully decode the data in its soft buffer.
Note 2: For TDD, the subframe number for ‘Y’, ‘P’, ‘Z’ and ‘Q’ should be ‘0’, ‘4’, ‘5’ and ‘9’ respectively based on TDD
configuration 1.
ETSI
Table 7.1.3.2.3.3-1: RRCConnectionReconfiguration. RadioResourceConfigDedicated (Preamble)

RadioResourceConfigDedicated::= SEQUENCE {
sps-Configuration ::= SEQUENCE {
semiPersistSchedC-RNTI ‘FFF0’H
sps-ConfigurationDL::=CHOICE{
enable SEQUENCE {
semiPersistSchedIntervalDL sf40 40 Subframe
numberOfConfSPS-Processes 8 FDD
numberOfConfSPS-Processes 7 Max DL HARQ TDD
processes is 7
considering TDD
configuration 1.
n1Pucch-AN-Persistent 0
}
}
sps-ConfigurationUL Not Present
}
}
Table 7.1.3.2.3.3-2: RRCConnectionReconfiguration. RadioResourceConfigDedicated (step 30 of table

7.1.3.2.3.2-1)

semiPersistSchedC-RNTI Not Present
disable NULL
}
}
}

c1 CHOICE{
drx-Config CHOICE { pc_FeatrGr
p_5 AND
DRX_S
setup SEQUENCE {
onDurationTimer psf40
}
}
}
}
}
}
}
}
ETSI
DRX_S Used for DRX configuration with small DRX cycle length
7.1.3.3 MAC PDU header handling

(1)
ensure that {
when { UE receives a MAC PDU containing an AMD PDU that is larger than 128 bytes with padding at
the end }
then { UE successfully decodes the MAC PDU and forward to higher layer }
}
(2)
ensure that {
when { UE receives a MAC PDU containing an AMD PDU that is smaller than 128 bytes with padding at
the end }
}
(3)
ensure that {
when { UE receives a MAC PDU containing an single AMD PDU with no padding }
}
(4)
ensure that {
when { UE receives a MAC PDU containing multiple MAC SDUs each containing an AMD PDU and no
padding }
then { UE successfully decodes the MAC PDU and forwards the AMD PDUs to higher layer }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 6.1.2
and 6.2.1.
[TS 36.321, clause 6.1.2]
A MAC PDU header consists of one or more MAC PDU sub-headers; each sub header corresponding to either a MAC
A MAC PDU sub header consists of the six header fields R/R/E/LCID/F/L but for the last sub header in the MAC PDU
and for fixed sized MAC control elements. The last sub header in the MAC PDU and sub-headers for fixed sized MAC
control elements consist solely of the four header fields R/R/E/LCID. It follows that a MAC PDU sub header
corresponding to padding consists of the four header fields R/R/E/LCID.
ETSI
Figure 6.1.2-1: R/R/E/LCID/F/L MAC sub header
Figure 6.1.2-2: R/R/E/LCID MAC sub header
have any value and the UE shall ignore it. When padding is performed at the end of the MAC PDU, zero or more
padding bytes are allowed.
placed at the beginning of the MAC PDU before any other MAC PDU subheader. A maximum of one MAC PDU can
be transmitted per TB per UE.
R/R/E/LCID
sub-header
R/R/E/LCID[/F/L]
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
... R/R/E/LCID/F/L
sub-header
R/R/E/LCID padding
sub-header
MAC payload
and padding
[TS 36.321, clause 6.2.1]
ETSI
included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU,
when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC
PDU. The LCID field size is 5 bits;
- L: The Length field indicates the length of the corresponding MAC SDU or MAC control element in bytes.
There is one L field per MAC PDU sub header except for the last sub header and sub-headers corresponding to
fixed-sized MAC control elements. The size of the L field is indicated by the F field;
- F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per
MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control
elements. The size of the F field is 1 bit. If the size of the MAC SDU or MAC control element is less than 128
bytes, the UE shall set the value of the F field to 0, otherwise the UE shall set it to 1;
- E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set
to "1" to indicate another set of at least R/R/E/LCID fields. The E field is set to "0" to indicate that either a MAC
SDU, a MAC control element or padding starts at the next byte;
- R: Reserved bits, set to "0".
The MAC header and sub-headers are octet aligned.
Index LCID values

00000 CCCH
11101 Timing Advance Command
11110 DRX Command
11111 Padding
Table 6.2.1-2: Values of LCID for UL-SCH
Index LCID values

00000 CCCH
11010 Power Headroom Report
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding
Table 6.2.1-3: Values of F field:
Index Size of Length field (in bits)

0 7
1 15
System Simulator:
- Cell 1
UE:
None.
ETSI
Preamble:
ETSI

U-S Message
1 The SS transmits a MAC PDU containing a <-- MAC PDU (R/R/E/LCID/F/L MAC - -
RLC SDU of 130 bytes in an AMD PDU sub-header (E=’1’, LCID=’00011’,
(SN=0) with polling field ‘P’ set to ‘1’ and 5 F=’1’, L=’132’), MAC R/R/E/LCID
bytes of padding. The MAC header contains MAC sub-header (E=’0’,
two MAC sub-headers where the first MAC LCID=’11111’), 132 bytes MAC
sub-header is a 3-byte R/R/E/LCID/F/L MAC SDU and 5 bytes padding)
sub-header with ‘E’ field set to ‘1’, the ‘F’ set to
‘1’, the ‘LCID’ field set to ‘00011’ and the ‘L’
field set to ‘132’ bytes. The second MAC sub-
header is a padding control 1byte R/R/E/LCID
MAC sub-header with ‘E’ field set to ‘0’ and
‘LCID’ field set to ‘11111’.
2 Check: Does the UE transmit a MAC PDU --> MAC PDU (RLC STATUS PDU 1 P
containing an RLC STATUS PDU (ACK_SN ‘1’))
acknowledging the reception of the AMD PDU
in step 1?
3 The SS transmits a MAC PDU containing a <-- MAC PDU (R/R/E/LCID/F/L MAC - -
RLC SDU of 40 bytes in an AMD PDU(SN=1) sub-header (E=’1’, LCID=’00011’,
with polling field ‘P’ set to ‘1’and 4 bytes of F=’0’, L=’42’), R/R/E/LCID MAC
padding. The MAC header contains two MAC sub-header (E=’0’, LCID=’11111’),
sub-headers where the first MAC sub-header 42 bytes MAC SDU and 4 bytes
is a 2-byte R/R/E/LCID/F/L MAC sub-header padding)
with ‘E’ field set to ‘1’, the ‘F’ set to ‘0’, the
‘LCID’ field set to ‘00011’ and the ‘L’ field set to
‘42’ bytes. The second MAC sub-header is a
padding control 1byte R/R/E/LCID MAC sub-
header with ‘E’ field set to ‘0’ and ‘LCID’ field
set to ‘11111’.
in step 3?
5 The SS transmits a MAC PDU containing a <-- MAC PDU (R/R/E/LCID MAC sub- - -
MAC SDU with a RLC SDU of 130 bytes in an header (E=’0’, LCID=’00011’), 132
AMD PDU(SN=2) with polling field ‘P’ set to ‘1’. bytes MAC SDU)
The MAC header contains one R/R/E/LCID
MAC sub-header with ‘E’ field set to ‘0’ and the
‘LCID’ field set to ‘00011’.
in step 5?
7 The SS transmits a MAC PDU containing one <-- MAC PDU (R/R/E/LCID/L MAC 4 -
MAC SDU containing a RLC SDU of size 128 sub-header (E=’1’, LCID=’00011’,
bytes in an AMD PDU (SN=3) and five MAC F=’1’, L=’ 130’), 4 x R/R/E/LCID/L
SDUs each containing a RLC SDU of 41 bytes MAC sub-header (E=’1’,
in an AMD PDU (SN=4 to 8) in an AMD PDU LCID=’00011’, F=’0’, L=’43’),
with the polling field ‘P’ set to ‘1’ in the last R/R/E/LCID MAC sub-header
AMD PDU. The MAC header contains six MAC (E=’0’, LCID=’00011’), 130 bytes
sub-headers where the first MAC sub-header MAC SDU, 5 x 43 bytes MAC
contains a 3 byte R/R/E/LCID/F/L MAC sub- SDUs)
header with ‘E’ field set to ‘1’ , ‘LCID’ field set
to ‘00011’, ‘F’ field set to ‘1’ and the ‘L’ field set
to ‘130’. The second to fifth MAC sub-header
are two byte R/R/E/LCID/F/L MAC sub-
headers with ‘E’ field set to ‘1’ , ‘LCID’ field set
to ‘00011’, ‘F’ field set to ‘0’ and the ‘L’ field set
to ‘43’ bytes. The sixth MAC sub-header is a
one byte R/R/E/LCID MAC sub-header with ‘E’
field set to ‘0’ and the ‘LCID’ field set to
‘00011’.
ETSI
acknowledging the reception of the AMD PDUs
in step 7?

preambleInformation SEQUENCE {
numberOfRA-Preambles n64
preamblesGroupAConfig := {SEQUENCE {
sizeOfRA-PreamblesGroupA n28
messageSizeGroupA b208
messagePowerOffsetGroupB minusinfinity
}
}
}
}
t300 ms1500 T300
}
}
}
}
7.1.3.4 Correct HARQ process handling / DCCH and DTCH

(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established }
ensure that {
when { the UE receives a MAC PDU for DRB and decode fails }
then { the UE transmits a NACK for the corresponding HARQ process }
}
(2)
ensure that {
when { the UE receives a MAC PDU retransmission for DRB, and results in successful decode}
then { the UE transmits an ACK for the corresponding HARQ process and delivers data to upper
layers }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 &
5.3.2.2.
[TS 36.321, clause 5.3.2.1]
There is one HARQ entity at the UE which maintains a number of parallel HARQ processes. Each HARQ process is
associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received
on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).
The number of DL HARQ processes is specified in [2], clause 7.
ETSI
When the physical layer is configured for spatial multiplexing [2], one or two TBs are expected per subframe and they
are associated with the same HARQ process. Otherwise, one TB is expected per subframe.
The UE shall:
- If a downlink assignment has been indicated for this TTI:
- allocate the TBs received from the physical layer and the associated HARQ information to the HARQ
process indicated by the associated HARQ information.
- If a downlink assignment has been indicated for the broadcast HARQ process:
- allocate the received TB to the broadcast HARQ process.
NOTE: In case of BCCH a dedicated broadcast HARQ process is used.
[TS 36.321, clause 5.3.2.2]
For each subframe where a transmission takes place for the HARQ process, one or two (in case of spatial multiplexing)
TBs and the associated HARQ information are received from the HARQ entity.
For each received TB and associated HARQ information, the HARQ process shall:
- if the NDI, when provided, has been toggled compared to the value of the previous received transmission
corresponding to this TB; or
- if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB
according to the system information schedule indicated by RRC; or
- if this is the very first received transmission for this TB(i.e. there is no previous NDI for this TB):
- consider this transmission to be a new transmission.
- else:
- consider this transmission to be a retransmission.
The UE then shall:
- if this is a new transmission
- replace the data currently in the soft buffer for this TB with the received data.
- else if this is a retransmission:
- if the data has not yet been successfully decoded:
- combine the received data with the data currently in the soft buffer for this TB.
- if the TB size is different from the last valid TB size signalled for this TB:
- the UE may replace the data currently in the soft buffer for this TB with the received data.
- attempt to decode the data in the soft buffer for this TB;
- if the data in the soft buffer was successfully decoded for this TB:
- if the HARQ process is equal to the broadcast process, deliver the decoded MAC PDU to upper layers.
- else if this is the first successful decoding of the data in the soft buffer for this TB:
-deliver the decoded MAC PDU to the disassembly and demultiplexing entity.
- generate a positive acknowledgement (ACK) of the data in this TB.
- else:
- generate a negative acknowledgement (NACK) of the data in this TB.
ETSI
- if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention
Resolution is not successful (see subclause 5.1.5); or
- if the HARQ process is equal to the broadcast process; or
- - if timeAlignmentTimer is stopped or expired:
- do not indicate the generated positive or negative acknowledgement to the physical layer.
- else:
- indicate the generated positive or negative acknowledgement for this TB to the physical layer.
The UE shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when
determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.
System Simulator:
- Cell 1
7.1.3.4.3.3-1
UE:
None.
Preamble:
ETSI

U-S Message
- EXCEPTION: Steps 1 to 7 are run - - - -
8[FDD]/7[TDD] times using test parameter
values as given for each iteration in table
7.1.3.4.3.2.-2.
1 The SS indicates a new transmission on <-- MAC PDU 1 -
PDCCH and transmits a MAC PDU (containing
an RLC PDU), with content set so that UE
could not successfully decode the data from its
soft buffer. The AMD PDU contains a full RLC
SDU. (Note 1)
2 Check: Does the UE transmit a HARQ NACK? --> HARQ NACK P
EXCEPTION: Step 3 shall be repeated till
HARQ ACK is received at step 4 or until HARQ
retransmission count = 4 is reached for MAC
PDU at step 3 (Note 2).
3 The SS indicates a retransmission on PDCCH <-- MAC PDU - -
and transmits the same MAC PDU like step 1
(Note 1).
UE should be allowed at step 4 (Note 2).
4 Check: Does the UE send a HARQ ACK? --> HARQ ACK 2 P
5 UE transmit a Scheduling Request on PUCCH --> (SR) - -
back PDU to transmitted
7 The UE transmit a MAC PDU containing the --> MAC PDU - -
loop back PDU corresponding to step 1 and 3
Note 1: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in
Note 2: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption
Table 7.1.3.4.3.2-2: Test Parameters
Iteration DL HARQ process

(X)
1 0
2 1
3 2
4 3
5 4
6 5
7 6
8 7[only for FDD]
Note: The maximum DL HARQ process is 7 for
TDD configuration 1.
ETSI

c1 CHOICE{
}
}
}
}
}
}
7.1.3.5 Correct HARQ process handling / CCCH

(1)
with { UE in E-UTRA RRC_ IDLE state with RRC connection establishment procedure initiated }
ensure that {
when { UE receives a MAC PDU addressed to RA-RNTI }
then { UE does not transmit ACK/NACK for the corresponding HARQ process }
}
(2)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI without UE Contention Resolution Identity
matching the one included in the RRCConnectionRequest message }
then { UE does not transmit a ACK/NACK for the corresponding HARQ process }
}
(3)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI and cannot decode properly }
then { UE does not transmits a NACK for the corresponding HARQ }
}
(4)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI with UE Contention Resolution Identity matching
the one included in the RRCConnectionRequest message }
then { UE transmits an ACK for the corresponding HARQ process and delivers data to upper layers
}
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 and
5.3.2.2.
[TS 36.321, clause 5.3.2.1]
ETSI
The UE shall:
[TS 36.321, clause 5.3.2.2]
- if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB
according to the system information schedule indicated by RRC; or
- else:
The UE then shall:
- if this is a new transmission
- if a retransmission is indicated for this TB:
- if the HARQ process is equal to the broadcast process:
- deliver the decoded MAC PDU to upper layers.
ETSI
- deliver the decoded MAC PDU to the disassembly and demultiplexing entity.
- else:
- if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and a UE the
Contention Resolution Identity match is not indicated successful (see subclause 5.1.5); or
- - if timeAlignmentTimer is stopped or expired:
- else:
determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.
System Simulator:
- Cell 1
- System information taking into account parameters in table 7.1.3.5.3.3-1
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode state (state 2) according to [18].
ETSI

U-S Message
a matched identity.
2 The UE transmits Preamble on PRACH --> PRACH Preamble - -
with matching RA-Id and including T-CRNTI.
The CRC is calculated in such a way, it will
result in CRC error on UE side
4 Check: does the UE transmit a HARQ --> HARQ ACK/NACK 1 F
ACK/NACK?
with matching RA-Id and including T-CRNTI .
The CRC is calculated in such a way, it will
result in CRC pass on UE side.
ACK/NACK?
8 The UE transmits a MAC PDU containing an --> MAC PDU - -
RRCConnectionSetup, and including ‘UE
Contention Resolution Identity’ MAC control
element with not matching ‘Contention
Resolution Identity’.
ACK/NACK?
RRCConnectionSetup, and including ‘UE
Contention Resolution Identity’ MAC control
element with matching ‘Contention Resolution
Identity’. The CRC is calculated in such a way
that it will result in CRC error on UE side
15 Check: Does UE transmit a HARQ NACK? --> HARQ NACK 3 F
19 The SS transmits the same MAC PDU like in <-- MAC PDU - -
step 14, but the CRC is calculated in such a
way that it will result in CRC pass on UE side
20 Check: does the UE transmit a HARQ ACK? --> HARQ ACK 4 P
including SERVICE REQUEST message
indicating acceptance of
RRCConnectionSetup message
ETSI

preambleTransMax n8
mac-ContentionResolutionTimer sf64 Max Value
}
}
prach-Configuration SEQUENCE {
prach-ConfigurationIndex 1 As per table 5.7.1- FDD
2 of 36.211, this
results in PRACH
preamble
transmission start
in even frame
numbers and sub-
frame number 4
prach-ConfigurationIndex 0 As per table 5.7.1- TDD
4 of 36.211, this
results in PRACH
preamble
transmission with
frequency
resource index=0;
occurring in even
radio frames;
resource is
located in first half
frame and sub
frame number 3
Note 1
}
}
}
t300 ms2000 T300
}
}
7.1.3.6 Correct HARQ process handling / BCCH

(1)
ensure that {
when { UE receives a MAC PDU addressed to SI-RNTI }
then { UE does not send any ACK/NACK for the corresponding dedicated HARQ process }
}
5.3.2.2.
[TS 36.321, clause 5.3.2.1]
ETSI
The UE shall:
[TS 36.321, clause 5.3.2.2]
- if the HARQ process is equal to the broadcast process and if the physical layer indicates a new transmission for
the TB according to the system information schedule indicated by RRC; or
- else:
The UE then shall:
- if this is a new transmission:
- else if this is a retransmission:
- if the HARQ process is equal to the broadcast process:
- deliver the decoded MAC PDU to upper layers.
ETSI
- deliver the decoded MAC PDU to the disassembly and demultiplexing entity.
- else:
- if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention
Resolution is not yet successful (see subclause 5.1.5); or
- if timeAlignmentTimer is stopped or expired:
- else:
determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous
transmission.
System Simulator:
- Cell 1
UE:
- None.
Preamble:
- RRC Connection Reconfiguration (Preamble: Table 4.5.3.3-1) using parameters as specified in Table 7.1.3.6.3.3-
4
ETSI

U-S Message
A The SS transmits a Paging message including - - - -
the systemInfoModification. (Note 1)
1 The SS transmits an updated system <-- - - -
information with SI-RNTI addressed in L1/L2
header at the start of the modification period.
CRC is calculated in such a way, it will result in
CRC fail on UE side. Dedicated HARQ
process for broadcast is used.
ACK/NACK? (Note 2 and 3)
3 Void - - - -
4 Void - -
5 Void - - - -
6 After 100ms of step 2, the SS transmits an - - - -
updated system information [contents same as
in step 1] with SI-RNTI addressed in L1/L2
header. CRC is calculated in such a way, it will
result in CRC pass on UE side. Dedicated
HARQ process for broadcast is used.
7 Check: Does the UE transmit an ACK/NACK? -> HARQ ACK/NACK 1 F
(Note 2 and 4)
8 SS is configured to not allocate UL Grants on - - - -
Scheduling Request
9 The SS Transmits MAC PDU containing a RLC <-- MAC PDU - -
PDU
10 The UE transmits a HARQ ACK --> HARQ ACK - -
11 Check: Does the UE transmit PRACH --> PRACH Preamble 1 P
Preamble, using PRACH resources as in new
SI?
13 The UE transmits a MAC PDU with C-RNTI --> MAC PDU - -
containing loop backed RLC PDU
14 SS sends PDCCH transmission for UE C-RNTI - - - -
to complete contention resolution.
Note 1: To guarantee that the UE will receive at least one Paging in the Modification Period preceding the SysInfo
change, SS should send the Paging message in every eligible PO in this Modification Period.
Note 2: When requested to check HARQ feedback for the dedicated broadcast HARQ process, the SS
shall assume the same PUCCH reception requirement as specified in TS 36.213 section 10 for a normal
HARQ process.
Note 3: For duration of 100ms, the SS should check HARQ NACK for all broadcast SIBs. This duration is sufficient
to ensure that SS transmits few times SIBs with CRC corruption.
Note 4: For duration of 5020ms (5120 - 100), the SS should check HARQ ACK for all broadcast SIBs. 5120ms is
the system information modification period calculated based on the default values of parameters specified
in TS 36.508.( modification period = modificationPeriodCoeff * defaultPagingCycle,and in TS 36.508,
modificationPeriodCoeff=4 and defaultPagingCycle=128radio frames).
ETSI
Table 7.1.3.6.3.3-1: SystemInformationBlockType2 (steps 1 and 6 of table 7.1.3.6.3.2-1)

prach-Config SEQUENCE {
rootSequenceIndex 20 (u = 2, Value different FDD
than default in TS
36.508)
rootSequenceIndex 2 (u = 2, Value different rootSequenceInde TDD
than default in TS x should take
36.508) value from table of
5.7.2-5 in TS
36.211 since, the
PRACH format 4
is used as default
for testing for
TDD.
}
}
}
Table 7.1.3.6.3.3-2: Paging (step A, 5 of table 7.1.3.6.3.2-1)

}
Table 7.1.3.6.3.3-3: SystemInformationBlockType1 (step 1 of table 7.1.3.6.3.2-1)

}
Table 7.1.3.6.3.3-4: RRCConnectionReconfiguration (Preamble)

c1 CHOICE{
}
}
}
}
}
}
ETSI
7.1.3.7 MAC padding

(1)
ensure that {
when{ UE is receiving RLC PDUs in MAC PDUs with padding greater than 2 bytes }
then { UE acknowledges reception of the RLC PDUs }
}
(2)
ensure that {
when { UE is receiving RLC PDUs in MAC PDUs with padding equal to or less than 2 bytes }
then { UE acknowledges reception of the RLC PDUs }
}
(3)
ensure that {
when { SS is transmitting a MAC control Timing Advance PDU with padding equal to or less than 2
bytes and no Data MAC PDU sub-headers followed by transmitting a RLC PDU }
then { UE acknowledges reception of the RLC PDU using the new Timing Advance }
}
[TS 36.321 clause 6.1.2]
When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding are
R/R/E/LCID
sub-header
R/R/E/LCID
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
... R/R/E/LCID/F/L
sub-header
R/R/E/LCID padding
sub-header
MAC payload
and padding
ETSI
System Simulator:
- Cell 1
UE:
None.
Preamble:

U-S Message
1 The SS transmits a MAC PDU containing an <-- MAC PDU(AMD PDU, 7-byte - -
RLC SDU in an AMD PDU with polling field ‘P’ padding)
set to ‘1’. The MAC SDU payload is set 8 bytes
smaller than the TB size allocated in the DL
Assignment minus AMD PDU and MAC
headers. SS adds a 7-byte padding at the end
of the MAC PDU and inserts a MAC padding
sub-header after the MAC SDU sub-header.
2 Check: Does the UE transmit an RLC STATUS --> RLC STATUS PDU (ACK_SN ‘1’) 1 P
PDU with ACK_SN field equal to 1?
3 The SS transmits a MAC PDU containing an <-- MACPDU(AMD PDU, one byte - -
RLC SDU in an AMD PDU with polling field ‘P’ padding)
set to ‘1’. The MAC SDU payload is set to 1-
byte smaller than the TB size allocated in the
DL Assignment minus AMD PDU and MAC
headers. SS adds a 1 byte padding by
inserting a MAC PDU sub-header before first
Data MAC PDU sub-header.
4 Check: Does the UE transmit an RLC STATUS --> MAC PDU(RLC STATUS PDU 2 P
PDU with ACK_SN field equal to 2? (ACK_SN =2) )
5 The SS sets the downlink assignment for TBS - - - -
of ’16-bits’
6 The SS transmits a Timing Advance without <-- MAC Control PDU(Timing - -
any additional padding. Start Timer_1 = Time Advance)
Alignment timer value.
7 The SS sets the downlink assignment for TBS - - - -
of ’24-bits’
8 The SS waits a time period equal to 0.5 of <-- MAC Control Element (Timing - -
Timer_1 value and configures a MAC PDU that Advance) + 1-byte padding
consists of only a Control MAC PDU sub
header (8-bits). Transmit another Timing
Advance MAC PDU (8-bits) which leaves 1-
byte padding. The SS does not transmit any
subsequent timing alignment. Restart Timer_1
= Time Alignment timer value
9 The SS waits a time period equal to 0.7 of - - - -
Timer_1.
9A SS transmits MAC PDU containing one RLC <-- MAC PDU(AMD PDU (SN=2, - -
SDU in an AMD PDU with polling field ‘P’ set P=1))
to ‘1’.
10 Check: Does the UE transmit an RLC STATUS --> MAC PDU(RLC STATUS PDU 3 P
PDU acknowledging the reception of the RLC (ACK_SN =3))
PDU in step 9 with new Timing Advance?
ETSI
None.
7.1.3.8 Void
7.1.3.9 MAC reset / DL
(1)
ensure that {
when { UE MAC is reset, due to handover to a new cell }
then { UE flushes DL HARQ buffer }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state )
ensure that {
when{ UE MAC is reset, due to handover to a new cell }
then { UE considers the next transmission for each DL HARQ process as very first }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.9.
[TS 36.321 clause 5.9]
If a reset of the MAC entity is requested by upper layers, the UE shall:
- initialize Bj for each logical channel to zero;
- stop (if running) all timers;
- consider the timeAlignmentTimer as expired and perform the corresponding actions in subclause 5.2;
- set the NDIs for all uplink HARQ processes to the value 0;
- stop, if any, ongoing RACH procedure;
- flush Msg3 buffer;
- cancel, if any, triggered Scheduling Request procedure;
- cancel, if any, triggered Buffer Status Reporting procedure;
- cancel, if any, triggered Power Headroom Reporting procedure;
- flush the soft buffers for all DL HARQ processes;
- for each DL HARQ process, consider the next received transmission for a TB as the very first;
- release, if any, Temporary C-RNTI.
System Simulator:
- Cell 1 and Cell 2
ETSI
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) in Cell 1 according to [18] using parameters as specified in
Table 7.1.3.9.3.3-3.
various time instants of the test execution. Row marked "T0" denotes the initial conditions, 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.

T0 Cell-specific RS EPRE dBm/15Khz -85 Off
T1 Cell-specific RS EPRE dBm/15Khz -85 -79
Table 7.1.3.9.3.3-2 illustrates the specific message content of RRC Connection Reconfiguration message during
preamble.

U-S Message
to the row "T1" in table 7.1.3.9.3.2-1
2 The SS transmits a MAC PDU containing one <-- MAC PDU (1 RLC SDU of 40 - -
RLC SDU on DRB, but the CRC is calculated bytes on DRB)
in such a way that it will result in CRC error on
UE side.
3 The UE transmit a HARQ NACK --> HARQ NACK - -
4 Void - - - -
5 The SS transmits an <-- - - -
handover to Cell 2
6 The UE transmits on Cell 2, --> - - -
7 Check: For 100 ms, does the UE transmit any --> HARQ NACK 1 F
HARQ NACK?
8 The SS transmits a MAC PDU containing RLC <-- MAC PDU (1 RLC SDU of 40 - -
SDU on DRB. The HARQ Process and NDI on bytes on DRB)
PDCCH is same as in step 2. The SS shall
ensure that the HARQ process used at step 2
will not be used in between steps 4 and 7.
9 Check: Does the UE transmit a scheduling --> (SR) 2 P
request?
10 The SS allocates UL Grant sufficient for one <-- Uplink Grant - -
RLC SDU to be loop backed in a TTI, and NDI
indicates new transmission
11 The UE transmits a MAC PDU including one --> MAC PDU - -
RLC SDU
ETSI
Derivation Path: 36.508, Table 4.6.1-8, condition HO

c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityControlInfo-HO
4.6.5)
}
}
}
}
}

c1 CHOICE{
}
}
}
}
}
}
Table 7.1.3.9.3.3-3: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1,

step 8)}

am SEQUENCE {
}
}
}
ETSI
7.1.3.10
7.1.3.11 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell
7.1.3.11.1 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Intra-
band Contiguous CA
(1)
with { UE in E-UTRA RRC_CONNECTED state with SCell activated }
ensure that {
when { the UE receives a MAC PDU for DRB and decode fails }
then { the UE transmits a NACK for the corresponding HARQ process within HARQ entity }
}
(2)
ensure that {
when { the UE receives a MAC PDU retransmission for DRB, and results in successful decode }
then { the UE transmits an ACK for the corresponding HARQ process within HARQ entity and
delivers data to upper layers }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1.
[TS 36.321, clause 5.3.2.1]
There is one HARQ entity at the UE for each Serving Cell which maintains a number of parallel HARQ processes. Each
HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and
associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).
The number of DL HARQ processes per HARQ entity is specified in [2], clause 7.
When the physical layer is configured for downlink spatial multiplexing [2], one or two TBs are expected per subframe
and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.
The UE shall:
- allocate the TB(s) received from the physical layer and the associated HARQ information to the HARQ
System Simulator:
7.1.3.11.1.3.3-1 and 7.1.3.11.1.3.3-2.
ETSI
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) on Cell 1 according to [18].
In Table 7.1.3.11.1.3.2-1, Row marked "T0" denotes the initial conditions which illustrates the downlink power levels
and other changing parameters to be applied for the cells after preamble.
Table 7.1.3.11.1.3.2-1: Time instances of cell power level and parameter changes

Cell-specific dBm/15k
T0 -85 -85
RS EPRE Hz
ETSI

U-S Message
RRConnectionReconfiguration message
containing a sCellToAddModList on Cell 1 with
SCell (Cell 3) addition.
2 The UE transmit an --> RRCConnectionReconfigurationC - -
RRCConnectionReconfigurationComplete omplete
message.
3 The SS transmits Activation MAC control <-- MAC PDU (Activation (C1=1)) - -
element to activate Scell (Cell 3).
PDCCH of CC1 and transmits a MAC PDU
(containing an RLC PDU with SN=0), with
content set so that UE could not successfully
decode the data from its soft buffer. (Note 1)
5 Check: Does the UE transmit a HARQ NACK --> HARQ NACK (CC1) 1 P
for the DL data corresponding DL CC1?
- EXCEPTION: Step 6 shall be repeated till - - - -
HARQ ACK is received at step 7 or until
HARQ retransmission count = 4 is reached for
MAC PDU at step 7 (Note 2).
6 The SS indicates a retransmission on PDCCH <-- MAC PDU (CC1) - -
of CC1 and transmits the same MAC PDU like
step 4 (Note 1).
EXCEPTION: Up to 3 HARQ NACK from the - - -
7 Check: Does the UE send a HARQ ACK for --> HARQ ACK (CC1) 2 P
the DL data corresponding to DL CC1?
8 The UE transmit a Scheduling Request on --> (SR) - -
PUCCH
loop back PDU corresponding to step 4 and 6
10a The SS transmits a MAC PDU containing RLC <-- MAC PDU (CC1) - -
PDU in step 10
(containing an RLC PDU with SN=1), with
content set so that UE could not successfully
decode the data from its soft buffer. (Note 1)
12 Check: Does the UE transmit a HARQ NACK --> HARQ NACK (CC2) 1 P
for the DL data corresponding to DL CC2?
HARQ ACK is received at step 14 or until
HARQ retransmission count = 4 is reached for
MAC PDU at step 14 (Note 2).
13 The SS indicates a retransmission on PDCCH <-- MAC PDU (CC2) - -
of CC2 and transmits the same MAC PDU like
step 11 (Note 1).
EXCEPTION: Up to 3 HARQ NACK from the - - - -
14 Check: Does the UE send a HARQ ACK for --> HARQ ACK (CC2) 2 P
the DL data corresponding to DL CC2?
15 UE transmit a Scheduling Request on PUCCH --> (SR) - -
loop back PDU corresponding to step 11 and
13
PDU in step 17
ETSI
- EXCEPTION: Steps 18 to 21 are run 8 [FDD]/7 - - - -

[TDD] times using test parameter values as
given for each iteration in table 7.1.3.11.1.3.2-
4 (Note 6).
18 The SS indicates new transmissions on <-- MAC PDU (CC1) and MAC PDU - -
PDCCHs of CC1 and CC2 and transmits a (CC2)
MAC PDU (containing an RLC PDU) on both
CCs respectively with contents set so that UE
could not successfully decode the data from its
soft buffers. (Note 1) (Note 6).
19 Check: Does the UE transmit HARQ NACK for --> HARQ NACK (CC1 and CC2) 1 P
the DL data corresponding to DL CC1 and CC2
respectively?
- EXCEPTION: In parallel with steps 20 to 21, - - - -
the parallel behaviour in table 7.1.3.11.1.3.2-3
is running.
HARQ ACK is received at step 21 for the data
corresponding both DL CC1 and DL CC2 or
until HARQ retransmission count = 4 is
reached for MAC PDUs at step 21 (Note 2).
20 The SS indicates retransmissions on PDCCHs <-- MAC PDU (CC1) and MAC - -
of CC1 and CC2 and transmits the same MAC PDU(CC2)
PDUs like step 18 (Note 1)(Note 3).
- EXCEPTION: Up to 3 HARQ NACK per CC - - - -
from the UE should be allowed at step 21
(Note 2).
21 Check: Does the UE send a HARQ ACKs for --> HARQ ACK (CC1) and HARQ 2 P
the DL data corresponding to DL CC1 and DL ACK (CC2)
CC2 (Note 7)?
Note 1: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in
Note 2: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption
Note 3: Retransmission is done only for the DL CCs, for which HARQ NACK was received.
Note 4: Void.
Note 5: CC1 corresponds to Pcell (Cell 1) and CC2 corresponds to Scell (Cell 3).
Note 6: At each iteration RLC PDU SN is incremented by 1 such that RLC PDUs with SN = 2, 4, 6, 8, 10 (and 12)
are being transmitted on CC1 whereas RLC PDUs with SN = 3, 5, 7, 9, 11 (and 13) on CC2.
Note 7: HARQ ACKs are expected only for those CCs for which retransmission was done in step 20.

U–S Message
PUCCH
2 Wait for 30ms to ensure HARQ processes for - - - -
both CCs are finished.
3 The SS allocates UL Grant sufficient for two <-- (UL Grant) - -
RLC SDU to be loop backed on Cell 1.
4 The UE transmits a MAC PDU including two --> MAC PDU - -
RLC SDU corresponding to step 18 in table
7.1.3.11.1.3.2-2.
PDUs in step 4
ETSI
Table 7.1.3.11.1.3.2-4: Test Parameters
Iteration DL HARQ process

(X)
1 0
2 1
3 2
4 3
5 4
6 5
7 6
8 7[only for FDD]
Note: The maximum DL HARQ process is 7 for
TDD configuration 1.
Derivation path: 36.508 Table 4.8.2.1.5-1

c1 CHOICE{
}
}
}
}
}
}

setup SEQUENCE {
dsr-TransMax n8
}
}
ETSI

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
}
Table 7.1.3.11.1.3.3-5: MAC-MainConfig-RBC (Table 7.1.3.11.3.3-4)
Derivation Path: 36.508, Table 4.8.2.1.5, condition SCell_AddMod

mac-MainConfig-v1020
mac-MainConfig-v1020SEQUENCE {
sCellDeactivationTimer-r10 rf128
}
7.1.3.11.2 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Inter-
band CA
- Cell 10 is an Active SCell according to [18] cl. 6.3.4.
7.1.3.11.3 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Intra-
band non-Contiguous CA
- CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
7.1.3.12 TDD additional special subframe configuration / Special subframe pattern 9

with Normal Cyclic Prefix / CRS based transmission scheme
(1)
with { UE in E-UTRA TDD RRC_CONNECTED state }
ensure that {
when { UE is configured with tdd-Config-v1130 equalling to ssp9 for normal cyclic prefix which is
configured in UL-CyclicPrefixLength equalling to len1, network schedules and transmits PDSCH data in
DwPTS }
then { UE sends ACK to the network after successfully receive and decode the data }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.211 clause 4.2, TS 36.213
clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.
[TS 36.211, clause 4.2]
ETSI
Frame structure type 2 is applicable to TDD. Each radio frame of length Tf = 307200 ⋅ Ts = 10 ms consists of two half-
frames of length 153600 ⋅Ts = 5 ms each. Each half-frame consists of five subframes of length 30720 ⋅Ts = 1 ms . The
supported uplink-downlink configurations are listed in Table 4.2-2 where, for each subframe in a radio frame, “D”
denotes the subframe is reserved for downlink transmissions, “U” denotes the subframe is reserved for uplink
transmissions and “S” denotes a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS
and UpPTS is given by Table 4.2-1 subject to the total length of DwPTS, GP and UpPTS being equal
to 30720 ⋅Ts = 1 ms . Each subframe i is defined as two slots, 2i and 2i + 1 of length Tslot = 15360 ⋅ Ts = 0.5 ms in each
subframe.
Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity are supported.
In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe exists in both half-frames.
In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe exists in the first half-frame only.
Subframes 0 and 5 and DwPTS are always reserved for downlink transmission. UpPTS and the subframe immediately
following the special subframe are always reserved for uplink transmission.
In case multiple cells are aggregated, the UE may assume that the guard period of the special subframe in the different
cells have an overlap of at least 1456 ⋅ Ts .
In case multiple cells with different uplink-downlink configurations are aggregated and the UE is not capable of
simultaneous reception and transmission in the aggregated cells, the following constraints apply:
- if the subframe in the primary cell is a downlink subframe, the UE shall not transmit any signal or channel on a
secondary cell in the same subframe
- if the subframe in the primary cell is an uplink subframe, the UE is not expected to receive any downlink
transmissions on a secondary cell in the same subframe
- if the subframe in the primary cell is a special subframe and the same subframe in a secondary cell is a downlink
subframe, the UE is not expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the secondary cell in the
same subframe, and the UE is not expected to receive any other signals on the secondary cell in OFDM symbols that
overlaps with the guard period or UpPTS in the primary cell.
Figure 4.2-1: Frame structure type 2 (for 5 ms switch-point periodicity)
ETSI
Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS)
Special subframe Normal cyclic prefix in downlink Extended cyclic prefix in downlink
configuration DwPTS UpPTS DwPTS UpPTS
Normal Extended Normal cyclic Extended cyclic
cyclic prefix cyclic prefix prefix in uplink prefix in uplink
in uplink in uplink
0 6592 ⋅ Ts 7680 ⋅ Ts
1 19760 ⋅ Ts 20480 ⋅ Ts
2192 ⋅ Ts 2560 ⋅ Ts
2 21952 ⋅ Ts 2192 ⋅ Ts 2560 ⋅ Ts 23040 ⋅ Ts
3 24144 ⋅ Ts 25600 ⋅ Ts
4 26336 ⋅ Ts 7680 ⋅ Ts
5 6592 ⋅ Ts 20480 ⋅ Ts
4384 ⋅ Ts 5120 ⋅ Ts
6 19760 ⋅ Ts 23040 ⋅ Ts
7 21952 ⋅ Ts 4384 ⋅ Ts 5120 ⋅ Ts 12800 ⋅ Ts
8 24144 ⋅ Ts - - -
9 13168 ⋅ Ts - - -
[TS 36.213, clause 7.1.7]
To determine the modulation order and transport block size(s) in the physical downlink shared channel, the UE shall
first
- read the 5-bit “modulation and coding scheme” field ( I MCS ) in the DCI
and second if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then
- for DCI format 1A:
1A
- set the Table 7.1.7.2.1-1 column indicator N PRB to N PRB from Section 5.3.3.1.3 in [4]
- for DCI format 1C:
- use Table 7.1.7.2.3-1 for determining its transport block size.
else
- set ′ to the total number of allocated PRBs based on the procedure defined in Section 7.1.6.
N PRB
if the transport block is transmitted in DwPTS of the special subframe in frame structure type 2, then
- for special subframe configuration 9 with normal cyclic prefix or special subframe configuration 7 with
extended cyclic prefix:
- set the Table 7.1.7.2.1-1 column indicator { ′ × 0.375⎥⎦ , 1 ,

N PRB = max ⎢⎣ N PRB }
- for other special subframe configurations:

′ .
else, set the Table 7.1.7.2.1-1 column indicator N PRB = N PRB
The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than
0.930, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits)
divided by the number of physical channel bits on PDSCH. If the UE skips decoding, the physical layer indicates to
higher layer that the transport block is not successfully decoded. For the special subframe configurations 0 and 5 with
normal downlink CP or configurations 0 and 4 with extended downlink CP, shown in Table 4.2-1 of [3], there shall be
no PDSCH transmission in DwPTS of the special subframe.
ETSI
[TS 36.306, clause 4.3.4.21]
This field defines whether the UE supports TDD special subframe as specified in [TS 36.211]. It is mandatory for UEs
of this release of the specification.
[TS 36.331, clause 6.3.2]
The IE TDD-Config is used to specify the TDD specific physical channel configuration.
TDD-Config information element

-- ASN1START
TDD-Config ::= SEQUENCE {

subframeAssignment ENUMERATED {
sa0, sa1, sa2, sa3, sa4, sa5, sa6},
specialSubframePatterns ENUMERATED {
ssp0, ssp1, ssp2, ssp3, ssp4,ssp5, ssp6, ssp7,
ssp8}
}
TDD-Config-v1130 ::= SEQUENCE {

specialSubframePatterns-v1130 ENUMERATED {ssp7,ssp9}
}
-- ASN1STOP
TDD-Config field descriptions

specialSubframePatterns
Indicates Configuration as in TS 36.211 [21, table 4.2-1] where ssp0 points to Configuration 0, ssp1 to Configuration 1
etc. Value ssp7 points to Configuration 7 for extended cyclic prefix and value ssp9 points to Configuration 9 for normal
cyclic prefix. E-UTRAN signals ssp7 only when setting specialSubframePatterns (without suffix i.e. the version defined
in REL-8) to ssp4. E-UTRAN signals value ssp9 only when setting specialSubframePatterns (without suffix) to ssp5. If
specialSubframePatterns-v1130 is present, the UE shall ignore specialSubframePatterns (without suffix).
subframeAssignment
Indicates DL/UL subframe configuration where sa0 point to Configuration 0, sa1 to Configuration 1 etc. as specified in
TS 36.211 [21, table 4.2-2]. E-UTRAN configures the same value for serving cells residing on same frequency band.
System Simulator:
- Cell 1
UE:
None.
Preamble:
section 7.1.3.12.3.3.
ETSI

U-S Message
1 The SS indicates a new transmission on <-- MAC PDU - -
PDCCH and transmits a MAC PDU in SF-Num
1 or 6 where the DwPTS belongs to.
3 The UE transmits a Scheduling Request on --> (SR) - -
PUCCH
back PDU to be transmitted
5 The UE transmits a MAC PDU containing the --> MAC PDU - -
loop back PDU corresponding to step 1
Table 7.1.3.12.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.12.3.2-1)

SEQUENCE {
tdd-Config SEQUENCE { TDD
subframeAssignment sa1
specialSubframePatterns ssp5
}
tdd-Config-v1130 SEQUENCE {
specialSubframePatterns-v1130 ssp9
}
}
}
}
}
Table 7.1.3.12.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.12.3.2-1)

ul-CyclicPrefixLength len1
}
}
ETSI

c1 CHOICE{
}
}
}
}
}
}
7.1.3.12a TDD additional special subframe configuration / Special subframe pattern 7

with Extended Cyclic Prefix / CRS based transmission scheme
(1)
ensure that {
when { UE is configured with tdd-Config-v1130 equalling to ssp7 for extended cyclic prefix which
is configured in UL-CyclicPrefixLength equalling to len2, network schedules and transmits PDSCH data
in DwPTS }
then { UE sends ACK to the network after successfully receive and decode the data }
}
clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.
[TS 36.211, clause 4.2]
frames of length 153600 ⋅ Ts = 5 ms each. Each half-frame consists of five subframes of length 30720 ⋅ Ts = 1 ms . The
to 30720 ⋅ Ts = 1 ms . Each subframe i is defined as two slots, 2i and 2i + 1 of length Tslot = 15360 ⋅ Ts = 0.5 ms in each
subframe.
ETSI
in uplink in uplink
0 6592 ⋅ Ts 7680 ⋅ Ts
1 19760 ⋅ Ts 20480 ⋅ Ts
2192 ⋅ Ts 2560 ⋅ Ts
2 21952 ⋅ Ts 2192 ⋅ Ts 2560 ⋅ Ts 23040 ⋅ Ts
3 24144 ⋅ Ts 25600 ⋅ Ts
4 26336 ⋅ Ts 7680 ⋅ Ts
5 6592 ⋅ Ts 20480 ⋅ Ts
4384 ⋅ Ts 5120 ⋅ Ts
6 19760 ⋅ Ts 23040 ⋅ Ts
7 21952 ⋅ Ts 4384 ⋅ Ts 5120 ⋅ Ts 12800 ⋅ Ts
8 24144 ⋅ Ts - - -
9 13168 ⋅ Ts - - -
[TS 36.213, clause 7.1.7]
first
1A
- set the Table 7.1.7.2.1-1 column indicator N PRB to N PRB from Section 5.3.3.1.3 in [4]
- for DCI format 1C:
ETSI
- use Table 7.1.7.2.3-1 for determining its transport block size.
else
- set ′ to the total number of allocated PRBs based on the procedure defined in Section 7.1.6.
N PRB
- for special subframe configuration 9 with normal cyclic prefix or special subframe configuration 7 with
extended cyclic prefix:

- for other special subframe configurations:

′ .
normal downlink CP or configurations 0 and 4 with extended downlink CP, shown in Table 4.2-1 of [3], there shall be
no PDSCH transmission in DwPTS of the special subframe.
[TS 36.306, clause 4.3.4.21]
[TS 36.331, clause 6.3.2]

-- ASN1START

ssp8}
}

}
-- ASN1STOP

subframeAssignment
ETSI
System Simulator:
- Cell 1
UE:
None.
Preamble:
section 7.1.3.12a.3.3.

U-S Message
PDCCH and transmits a MAC PDU in SF-Num
1 or 6 where the DwPTS belongs to.
PUCCH
Table 7.1.3.12a.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.12a.3.2-1)

SEQUENCE {
}
}
}
}
}
}
ETSI
Table 7.1.3.12a.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.12a.3.2-1)

}
}
Table 7.1.3.12a.3.3-3: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

c1 CHOICE{
}
}
}
}
}
}
7.1.3.13 TDD additional special subframe configuration / Special subframe pattern 9

with Normal Cyclic Prefix / UE-specific reference signals based transmission
scheme
(1)
ensure that {
when { UE is configured with tdd-Config-v1130 equalling to ssp9 for normal cyclic prefix which is
configured in UL-CyclicPrefixLength equalling to len1 under tm8 transmission mode, network uses DCI
format 2B for PDSCH scheduling and transmits PDSCH data in DwPTS }
then { UE sends ACK to the network after UE successfully receives and decodes the data }
}
clause 6.10.3.2 and clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.
[TS 36.211, clause 4.2]
frames of length 153600 ⋅ Ts = 5 ms each. Each half-frame consists of five subframes of length 30720 ⋅ Ts = 1 ms . The
to 30720 ⋅ Ts = 1 ms . Each subframe i is defined as two slots, 2i and 2i + 1 of length Tslot = 15360 ⋅ Ts = 0.5 ms in each
subframe.
ETSI
Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS).
in uplink in uplink
0 6592 ⋅ Ts 7680 ⋅ Ts
1 19760 ⋅ Ts 20480 ⋅ Ts
2192 ⋅ Ts 2560 ⋅ Ts
2 21952 ⋅ Ts 2192 ⋅ Ts 2560 ⋅ Ts 23040 ⋅ Ts
3 24144 ⋅ Ts 25600 ⋅ Ts
4 26336 ⋅ Ts 7680 ⋅ Ts
5 6592 ⋅ Ts 20480 ⋅ Ts
4384 ⋅ Ts 5120 ⋅ Ts
6 19760 ⋅ Ts 23040 ⋅ Ts
7 21952 ⋅ Ts 4384 ⋅ Ts 5120 ⋅ Ts 12800 ⋅ Ts
8 24144 ⋅ Ts - - -
9 13168 ⋅ Ts - - -
[TS 36.213, clause 6.10.3.2]
ETSI
For antenna ports p = 7 , p = 8 or p = 7,8, K,υ + 6 , in a physical resource block with frequency-domain index n PRB
assigned for the corresponding PDSCH transmission, a part of the reference signal sequence r (m) shall be mapped to
complex-valued modulation symbols a k( ,pl ) in a subframe according to
Normal cyclic prefix:
a k( ,pl ) = w p (l ' ) ⋅ r (3 ⋅ l '⋅N RB

max, DL
+ 3 ⋅ nPRB + m' )
where
⎧w p (i) (m'+ nPRB ) mod 2 = 0

w p (i ) = ⎨
w
⎩ p (3 − i ) (m'+ nPRB ) mod 2 = 1
k = 5m'+ N scRB nPRB + k '
⎧1 p ∈ {7,8,11,13}
k' = ⎨
⎩0 p ∈ {9,10,12,14}
⎧l ' mod 2 + 2 if in a special subframe with configuration 3, 4, 8 or 9 (see Table 4.2 - 1)
⎪
l = ⎨l ' mod 2 + 2 + 3⎣l ' / 2⎦ if in a special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎪l ' mod 2 + 5
⎩ if not in a special subframe
⎧0,1,2,3 if ns mod 2 = 0 and in a special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎪
l ' = ⎨0,1 if ns mod 2 = 0 and not in special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎪2,3 if ns mod 2 = 1 and not in special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎩
m' = 0,1,2
The sequence w p (i ) is given by Table 6.10.3.2-1.
Table 6.10.3.2-1: The sequence w p (i ) for normal cyclic prefix.
Antenna port p [w p (0) w p (1) w p (2) w p (3) ]

7 [+ 1 + 1 + 1 + 1]
8 [+ 1 − 1 + 1 − 1]
9 [+ 1 + 1 + 1 + 1]
10 [+ 1 − 1 + 1 − 1]
11 [+ 1 + 1 − 1 − 1]
12 [− 1 − 1 + 1 + 1]
13 [+ 1 − 1 − 1 + 1]
14 [− 1 + 1 + 1 − 1]
Extended cyclic prefix:
ak( ,pl ) = w p (l ' mod 2) ⋅ r ( 4 ⋅ l '⋅ N RB

max, DL
+ 4 ⋅ nPRB + m' )
where
ETSI
⎧ w p (i ) m ′ mod 2 = 0
w p (i ) = ⎨
⎩w p (1 − i ) m ′ mod 2 = 1
k = 3m'+ N scRB n PRB + k '
⎧1 if ns mod 2 = 0 and p ∈ {7,8}
k' = ⎨
⎩2 if ns mod 2 = 1 and p ∈ {7,8}
l = l ′ mod 2 + 4
⎧0,1 if n s mod 2 = 0 and in a special subframe with configuration 1, 2, 3, 5 or 6 (see Table 4.2 - 1)
⎪
l ' = ⎨0,1 if n s mod 2 = 0 and not in a special subframe
⎪⎩2,3 if n s mod 2 = 1 and not in a special subframe
m' = 0,1,2,3
Table 6.10.3.2-2: The sequence w p (i ) for extended cyclic prefix.
Antenna port p [w p (0) w p (1) ]

7 [+ 1 + 1]
8 [− 1 + 1]
For extended cyclic prefix, UE-specific reference signals are not supported on antenna ports 9 to 14.
Resource elements (k , l ) used for transmission of UE-specific reference signals to one UE on any of the antenna ports
in the set S , where S = {7,8,11,13} or S = {9,10,12,14} shall
- not be used for transmission of PDSCH on any antenna port in the same slot, and
- not be used for UE-specific reference signals to the same UE on any antenna port other than those in S in the
same slot.
Figure 6.10.3.2-3 illustrates the resource elements used for UE-specific reference signals for normal cyclic prefix for
antenna ports 7, 8, 9 and 10. Figure 6.10.3.2-4 illustrates the resource elements used for UE-specific reference signals
for extended cyclic prefix for antenna ports 7, 8.
ETSI
7r
o R7 R7 R7 R7 R8 R8 R8 R8
6, R9 R9 R9 R9 R10 R10 R10 R10
,21
no
tia
ru
gfi R7 R7 R7 R7 R8 R8 R8 R8
onc R9 R9 R9 R9 R10 R10 R10 R10
,e
m
ar
fb
us
la
ic R7 R7 R7 R7 R8 R8 R8 R8
ep R10 R10 R10 R10
S R9 R9 R9 R9
l=0 l =6 l =0 l =6 l =0 l=6 l=0 l=6 l=0 l =6 l =0 l =6 l=0 l =6 l =0 l =6
9r R7 R7 R7 R7 R8 R8 R8 R8
o
8, R9 R9 R9 R9 R10 R10 R10 R10
,43
no
i
atr
ug
if R7 R7 R7 R7 R8 R8 R8 R8
no R9 R9 R9 R9 R10 R10 R10 R10
c,
e
m
ar
bfu
sl
iac
R7 R7 R7 R7 R8 R8 R8 R8
ep R9 R9 R9 R9 R10 R10 R10 R10
S l=0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l=0 l =6 l =0 l =6 l=0 l =6 l =0 l =6
R7 R7 R7 R7 R8 R8 R8 R8
R9 R9 R9 R9 R10 R10 R10 R10
es
m
raf
bu
s
kn
il R7 R7 R7 R7 R8 R8 R8 R8
n
w
od
R9 R9 R9 R9 R10 R10 R10 R10
re
tho
ll
A R7 R7 R7 R7 R8 R8 R8 R8
R9 R9 R9 R9 R10 R10 R10 R10
l=0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6
Figure 6.10.3.2-3: Mapping of UE-specific reference signals, antenna ports 7, 8, 9 and 10 (normal
cyclic prefix)
[TS 36.213, clause 7.1]
For frame structure type 2,
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in any subframe in
which the number of OFDM symbols for PDCCH with normal CP is equal to four;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in the two PRBs to
which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a transmission of
PBCH in the same subframe;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 7, 8, 9, 10, 11, 12, 13
or 14 in the two PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency
with a transmission of primary or secondary synchronisation signals in the same subframe;
- with normal CP configuration, the UE is not expected to receive PDSCH on antenna port 5 for which
distributed VRB resource allocation is assigned in the special subframe with configuration #1 or #6;
- the UE is not expected to receive PDSCH on antenna port 7 for which distributed VRB resource allocation is
assigned;
- with normal cyclic prefix, the UE is not expected to receive PDSCH resource blocks transmitted on antenna
port 5 in DwPTS when the UE is configured with special subframe configuration 9.
ETSI
- The UE may skip decoding the transport block(s) if it does not receive all assigned PDSCH resource blocks.
If the UE skips decoding, the physical layer indicates to higher layer that the transport block(s) are not
successfully decoded.
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the C-RNTI, the UE shall decode the
PDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5. The
scrambling initialization of PDSCH corresponding to these PDCCHs is by C-RNTI.
If a UE is configured by higher layers to decode EPDCCH with CRC scrambled by the C-RNTI, the UE shall decode
the EPDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5A. The
scrambling initialization of PDSCH corresponding to these EPDCCHs is by C-RNTI.
If the UE is configured with the carrier indicator field for a given serving cell and, if the UE is configured by higher
layers to decode PDCCH/EPDCCH with CRC scrambled by the C-RNTI, then the UE shall decode PDSCH of the
serving cell indicated by the carrier indicator field value in the decoded PDCCH/EPDCCH.
When a UE configured in transmission mode 3, 4, 8, 9 or 10 receives a DCI Format 1A assignment, it shall assume that
the PDSCH transmission is associated with transport block 1 and that transport block 2 is disabled.
When a UE is configured in transmission mode 7, scrambling initialization of UE-specific reference signals

corresponding to these PDCCHs/EPDCCHs is by C-RNTI.
The UE does not support transmission mode 8 if extended cyclic prefix is used in the downlink.
When a UE is configured in transmission mode 9 or 10, in the subframes indicated by the higher layer parameter mbsfn-
SubframeConfigList except in subframes for the serving cell
- indicated by higher layers to decode PMCH or,
- configured by higher layers to be part of a positioning reference signal occasion and the positioning reference
signal occasion is only configured within MBSFN subframes and the cyclic prefix length used in subframe #0 is
normal cyclic prefix,
the UE shall upon detection of a PDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for
the UE or, upon detection of an EPDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for
the UE, decode the corresponding PDSCH in the same subframe.
A UE configured in transmission mode 10 can be configured with scrambling identities, nID DMRS,i
, i = 0,1 by higher
layers for UE-specific reference signal generation as defined in Section 6.10.3.1 of [3] to decode PDSCH according to a
detected PDCCH/EPDCCH with CRC scrambled by the C-RNTI with DCI format 2D intended for the UE.
ETSI
Table 7.1-5: PDCCH and PDSCH configured by C-RNTI
Transmission DCI format Search Space Transmission scheme of PDSCH

mode corresponding to PDCCH
Mode 1 DCI format 1A Common and Single-antenna port, port 0 (see subclause
UE specific by C-RNTI 7.1.1)
DCI format 1 UE specific by C-RNTI Single-antenna port, port 0 (see subclause
7.1.1)
Mode 2 DCI format 1A Common and Transmit diversity (see subclause 7.1.2)
UE specific by C-RNTI
DCI format 1 UE specific by C-RNTI Transmit diversity (see subclause 7.1.2)
DCI format 2A UE specific by C-RNTI Large delay CDD (see subclause 7.1.3) or
Transmit diversity (see subclause 7.1.2)
DCI format 2 UE specific by C-RNTI Closed-loop spatial multiplexing (see
subclause 7.1.4)or Transmit diversity (see
subclause 7.1.2)
DCI format 1D UE specific by C-RNTI Multi-user MIMO (see subclause 7.1.5)
DCI format 1B UE specific by C-RNTI Closed-loop spatial multiplexing (see
subclause 7.1.4) using a single
transmission layer
Mode 7 DCI format 1A Common and If the number of PBCH antenna ports is
UE specific by C-RNTI one, Single-antenna port, port 0 is used
(see subclause 7.1.1), otherwise Transmit
diversity (see subclause 7.1.2)
7.1.1)
DCI format 2B UE specific by C-RNTI Dual layer transmission, port 7 and 8 (see
subclause 7.1.5A) or single-antenna port,
port 7 or 8 (see subclause 7.1.1)
Mode 9 DCI format 1A Common and Non-MBSFN subframe: If the number of
UE specific by C-RNTI PBCH antenna ports is one, Single-
antenna port, port 0 is used (see subclause
7.1.1), otherwise Transmit diversity (see
subclause 7.1.2)
MBSFN subframe: Single-antenna port,
port 7 (see subclause 7.1.1)
DCI format 2C UE specific by C-RNTI Up to 8 layer transmission, ports 7-14 (see
subclause 7.1.5B) or single-antenna port,
subclause 7.1.2)
DCI format 2D UE specific by C-RNTI Up to 8 layer transmission, ports 7-14 (see
[TS 36.306, clause 4.3.4.21]
ETSI
[TS 36.331, clause 6.3.2]

-- ASN1START

ssp8}
}

}
-- ASN1STOP

subframeAssignment
System Simulator:
- Cell 1
UE:
None.
Preamble:
section 7.1.3.13.3.3.

U-S Message
PDCCH by using DCI format 2B and transmits
a MAC PDU in SF-Num 1 or 6 where the
DwPTS belongs to.
PUCCH
ETSI
Table 7.1.3.13.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.13.3.2-1)

SEQUENCE {
}
}
}
}
}
}
Table 7.1.3.13.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.13.3.2-1)

}
}

c1 CHOICE {
}
}
}
}
}
}
ETSI
Table 7.1.3.13.3.3-4: PhysicalConfigDedicated-DEFAULT (preamble: Table 4.5.3.3-1, step 8)

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
antennaInfo CHOICE {
explicitValue SEQUENCE { 2TX
transmissionMode tm8-v920
ue-TransmitAntennaSelection CHOICE {
Release NULL
}
}
}
}
7.1.3.13a TDD additional special subframe configuration / Special subframe pattern 7

with Extended Cyclic Prefix / UE-specific reference signals based
transmission scheme
(1)
ensure that {
when { UE is configured with tdd-Config-v1130 equalling to ssp7 for extended cyclic prefix which
is configured in UL-CyclicPrefixLength equalling to len2 under tm8 transmission mode, network uses
DCI format 1 for PDSCH scheduling and transmits PDSCH data in DwPTS }
then { UE sends ACK to the network after UE successfully receives and decodes the data }
}
clause 6.10.3.2 and clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.
[TS 36.211, clause 4.2]
frames of length 153600 ⋅Ts = 5 ms each. Each half-frame consists of five subframes of length 30720 ⋅Ts = 1 ms . The
to 30720 ⋅Ts = 1 ms . Each subframe i is defined as two slots, 2i and 2i + 1 of length Tslot = 15360 ⋅ Ts = 0.5 ms in each
subframe.
ETSI
in uplink in uplink
0 6592 ⋅ Ts 7680 ⋅ Ts
1 19760 ⋅ Ts 20480 ⋅ Ts
2192 ⋅ Ts 2560 ⋅ Ts
2 21952 ⋅ Ts 2192 ⋅ Ts 2560 ⋅ Ts 23040 ⋅ Ts
3 24144 ⋅ Ts 25600 ⋅ Ts
4 26336 ⋅ Ts 7680 ⋅ Ts
5 6592 ⋅ Ts 20480 ⋅ Ts
4384 ⋅ Ts 5120 ⋅ Ts
6 19760 ⋅ Ts 23040 ⋅ Ts
7 21952 ⋅ Ts 4384 ⋅ Ts 5120 ⋅ Ts 12800 ⋅ Ts
8 24144 ⋅ Ts - - -
9 13168 ⋅ Ts - - -
[TS 36.213, clause 6.10.3.2]
For antenna ports p = 7 , p = 8 or p = 7,8, K,υ + 6 , in a physical resource block with frequency-domain index n PRB
assigned for the corresponding PDSCH transmission, a part of the reference signal sequence r (m) shall be mapped to
complex-valued modulation symbols a k( ,pl ) in a subframe according to
Normal cyclic prefix:
a k( ,pl ) = w p (l ' ) ⋅ r (3 ⋅ l '⋅N RB

max, DL
+ 3 ⋅ nPRB + m' )
where
ETSI
⎧w p (i) (m'+ nPRB ) mod 2 = 0

w p (i ) = ⎨
w
⎩ p (3 − i ) (m'+ nPRB ) mod 2 = 1
k = 5m'+ N scRB nPRB + k '
⎧1 p ∈ {7,8,11,13}
k' = ⎨
⎩0 p ∈ {9,10,12,14}
⎧l ' mod 2 + 2 if in a special subframe with configuration 3, 4, 8 or 9 (see Table 4.2 - 1)
⎪
l = ⎨l ' mod 2 + 2 + 3⎣l ' / 2⎦ if in a special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎪l ' mod 2 + 5
⎩ if not in a special subframe
⎧0,1,2,3 if ns mod 2 = 0 and in a special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎪
l ' = ⎨0,1 if ns mod 2 = 0 and not in special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎪2,3 if ns mod 2 = 1 and not in special subframe with configuration 1, 2, 6, or 7 (see Table 4.2 - 1)
⎩
m' = 0,1,2
Table 6.10.3.2-1: The sequence w p (i ) for normal cyclic prefix
Antenna port p [w p (0) w p (1) w p (2) w p (3) ]

7 [+ 1 + 1 + 1 + 1]
8 [+ 1 − 1 + 1 − 1]
9 [+ 1 + 1 + 1 + 1]
10 [+ 1 − 1 + 1 − 1]
11 [+ 1 + 1 − 1 − 1]
12 [− 1 − 1 + 1 + 1]
13 [+ 1 − 1 − 1 + 1]
14 [− 1 + 1 + 1 − 1]
Extended cyclic prefix:
ak( ,pl ) = w p (l ' mod 2) ⋅ r ( 4 ⋅ l '⋅ N RB

max, DL
+ 4 ⋅ nPRB + m' )
where
⎧ w p (i ) m ′ mod 2 = 0
w p (i ) = ⎨
⎩w p (1 − i ) m ′ mod 2 = 1
k = 3m'+ N scRB n PRB + k '
⎧1 if ns mod 2 = 0 and p ∈ {7,8}
k' = ⎨
⎩2 if ns mod 2 = 1 and p ∈ {7,8}
l = l ′ mod 2 + 4
⎧0,1 if n s mod 2 = 0 and in a special subframe with configuration 1, 2, 3, 5 or 6 (see Table 4.2 - 1)
⎪
l ' = ⎨0,1 if n s mod 2 = 0 and not in a special subframe
⎪⎩2,3 if n s mod 2 = 1 and not in a special subframe
m' = 0,1,2,3
ETSI
Table 6.10.3.2-2: The sequence w p (i ) for extended cyclic prefix.
Antenna port p [w p (0) w p (1) ]

7 [+ 1 + 1]
8 [− 1 + 1]
For extended cyclic prefix, UE-specific reference signals are not supported on antenna ports 9 to 14.
Resource elements (k , l ) used for transmission of UE-specific reference signals to one UE on any of the antenna ports
in the set S , where S = {7,8,11,13} or S = {9,10,12,14} shall
- not be used for transmission of PDSCH on any antenna port in the same slot, and
- not be used for UE-specific reference signals to the same UE on any antenna port other than those in S in the
same slot.
Figure 6.10.3.2-3 illustrates the resource elements used for UE-specific reference signals for normal cyclic prefix for
antenna ports 7, 8, 9 and 10. Figure 6.10.3.2-4 illustrates the resource elements used for UE-specific reference signals
for extended cyclic prefix for antenna ports 7, 8.
7r
o R7 R7 R7 R7 R8 R8 R8 R8
6, R9 R9 R9 R9 R10 R10 R10 R10
,21
no
i
atr
ug
if R7 R7 R7 R7 R8 R8 R8 R8
no
c, R9 R9 R9 R9 R10 R10 R10 R10
e
am
rf
bu
sl
ai R7 R7 R7 R7
ecp
R8 R8 R8 R8
R10 R10 R10 R10
S R9 R9 R9 R9
l=0 l =6 l =0 l =6 l =0 l=6 l=0 l=6 l=0 l =6 l =0 l =6 l=0 l =6 l =0 l =6
9r R7 R7 R7 R7 R8 R8 R8 R8
o
8, R9 R9 R9 R9 R10 R10 R10 R10
4,
3
no
it
rau
gfi R7 R7 R7 R7 R8 R8 R8 R8
no R9 R9 R9 R9 R10 R10 R10 R10
c,
e
m
ar
fb
us
ali R7 R7 R7 R7 R8 R8 R8 R8
ce R9 R9 R10 R10 R10 R10
pS R9 R9
l=0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l=0 l =6 l =0 l =6 l=0 l =6 l =0 l =6
R7 R7 R7 R7 R8 R8 R8 R8
R9 R9 R9 R9 R10 R10 R10 R10
es
m
a
frb
us
kn
il R7 R7 R7 R7 R8 R8 R8 R8
n
w
od
R9 R9 R9 R9 R10 R10 R10 R10
re
tho
ll
A R7 R7 R7 R7 R8 R8 R8 R8
R9 R9 R9 R9 R10 R10 R10 R10
l=0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6 l =0 l =6
Figure 6.10.3.2-3: Mapping of UE-specific reference signals, antenna ports 7, 8, 9 and 10 (normal
cyclic prefix)
[TS 36.213, clause 7.1]
For frame structure type 2,
ETSI
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in any subframe in
which the number of OFDM symbols for PDCCH with normal CP is equal to four;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in the two PRBs to
which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a transmission of
PBCH in the same subframe;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 7, 8, 9, 10, 11, 12, 13
or 14 in the two PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency
with a transmission of primary or secondary synchronisation signals in the same subframe;
- with normal CP configuration, the UE is not expected to receive PDSCH on antenna port 5 for which
distributed VRB resource allocation is assigned in the special subframe with configuration #1 or #6;
- the UE is not expected to receive PDSCH on antenna port 7 for which distributed VRB resource allocation is
assigned;
- with normal cyclic prefix, the UE is not expected to receive PDSCH resource blocks transmitted on antenna
port 5 in DwPTS when the UE is configured with special subframe configuration 9.
- The UE may skip decoding the transport block(s) if it does not receive all assigned PDSCH resource blocks.
If the UE skips decoding, the physical layer indicates to higher layer that the transport block(s) are not
successfully decoded.
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the C-RNTI, the UE shall decode the
PDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5. The
scrambling initialization of PDSCH corresponding to these PDCCHs is by C-RNTI.
If a UE is configured by higher layers to decode EPDCCH with CRC scrambled by the C-RNTI, the UE shall decode
the EPDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5A. The
scrambling initialization of PDSCH corresponding to these EPDCCHs is by C-RNTI.
If the UE is configured with the carrier indicator field for a given serving cell and, if the UE is configured by higher
layers to decode PDCCH/EPDCCH with CRC scrambled by the C-RNTI, then the UE shall decode PDSCH of the
serving cell indicated by the carrier indicator field value in the decoded PDCCH/EPDCCH.
When a UE configured in transmission mode 3, 4, 8, 9 or 10 receives a DCI Format 1A assignment, it shall assume that
the PDSCH transmission is associated with transport block 1 and that transport block 2 is disabled.
When a UE is configured in transmission mode 7, scrambling initialization of UE-specific reference signals

corresponding to these PDCCHs/EPDCCHs is by C-RNTI.
The UE does not support transmission mode 8 if extended cyclic prefix is used in the downlink.
When a UE is configured in transmission mode 9 or 10, in the subframes indicated by the higher layer parameter mbsfn-
SubframeConfigList except in subframes for the serving cell
- indicated by higher layers to decode PMCH or,
- configured by higher layers to be part of a positioning reference signal occasion and the positioning reference
signal occasion is only configured within MBSFN subframes and the cyclic prefix length used in subframe #0 is
normal cyclic prefix,
the UE shall upon detection of a PDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for
the UE or, upon detection of an EPDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for
the UE, decode the corresponding PDSCH in the same subframe.
A UE configured in transmission mode 10 can be configured with scrambling identities, nID DMRS,i
, i = 0,1 by higher
layers for UE-specific reference signal generation as defined in Section 6.10.3.1 of [3] to decode PDSCH according to a
detected PDCCH/EPDCCH with CRC scrambled by the C-RNTI with DCI format 2D intended for the UE.
ETSI
Table 7.1-5: PDCCH and PDSCH configured by C-RNTI
Transmission DCI format Search Space Transmission scheme of PDSCH

mode corresponding to PDCCH
Mode 1 DCI format 1A Common and Single-antenna port, port 0 (see subclause
UE specific by C-RNTI 7.1.1)
7.1.1)
DCI format 1 UE specific by C-RNTI Transmit diversity (see subclause 7.1.2)
DCI format 2A UE specific by C-RNTI Large delay CDD (see subclause 7.1.3) or
Transmit diversity (see subclause 7.1.2)
DCI format 2 UE specific by C-RNTI Closed-loop spatial multiplexing (see
subclause 7.1.4)or Transmit diversity (see
subclause 7.1.2)
DCI format 1D UE specific by C-RNTI Multi-user MIMO (see subclause 7.1.5)
DCI format 1B UE specific by C-RNTI Closed-loop spatial multiplexing (see
subclause 7.1.4) using a single
transmission layer
7.1.1)
DCI format 2B UE specific by C-RNTI Dual layer transmission, port 7 and 8 (see
subclause 7.1.5A) or single-antenna port,
subclause 7.1.2)
DCI format 2C UE specific by C-RNTI Up to 8 layer transmission, ports 7-14 (see
subclause 7.1.2)
DCI format 2D UE specific by C-RNTI Up to 8 layer transmission, ports 7-14 (see
[TS 36.306, clause 4.3.4.21]
ETSI
[TS 36.331, clause 6.3.2]

-- ASN1START

ssp8}
}

}
-- ASN1STOP

subframeAssignment
System Simulator:
- Cell 1
UE:
None.
Preamble:
section 7.1.3.13a.3.3.

U-S Message
PDCCH by using DCI format 1 and transmits a
MAC PDU in SF-Num 1 or 6 where the DwPTS
belongs to.
PUCCH
ETSI
Table 7.1.3.13a.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.13a.3.2-1)

SEQUENCE {
}
}
}
}
}
}
Table 7.1.3.13a.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.13a.3.2-1)

}
}

c1 CHOICE {
}
}
}
}
}
}
ETSI
Table 7.1.3.13a.3.3-4: PhysicalConfigDedicated-DEFAULT (preamble: Table 4.5.3.3-1, step 8)

transmissionMode tm7
Release NULL
}
}
}
}
7.1.3.14 Correct handling of DL assignment / Dynamic case / EPDCCH

(1)
with { UE in E-UTRA RRC_CONNECTED state with EPDCCH in localized transmission type }
ensure that {
when { UE receives downlink assignment on the EPDCCH for the UE’s C-RNTI and receives data in the
associated subframe and UE performs HARQ operation }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and EPDCCH in localized transmission type }
ensure that {
when { UE receives downlink assignment on the EPDCCH with a C-RNTI unknown by the UE and data is
available in the associated subframe }
}
(3)
ensure that {
when { EPDCCH is configured with distributed transmission type and UE receives downlink assignment
on the EPDCCH for the UE’s C-RNTI and receives data in the associated subframe and UE performs HARQ
operation }
}
(4)
ensure that {
when { EPDCCH is configured with distributed transmission type and UE receives downlink assignment
on the EPDCCH with a C-RNTI unknown by the UE and data is available in the associated subframe }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 3.1 and
5.3.1. Unless otherwise stated these are Rel-11 requirements.
[36.321, clause 3.1]
PDCCH: Refers to the PDCCH [7], EPDCCH (in subframes when configured) or, for an RN with R-PDCCH
configured and not suspended, to the R-PDCCH.
[TS 36.321, clause 5.3.1]
ETSI
C-RNTI:
System Simulator:
- Cell 1
7.1.3.1.3.3-1
UE:
None.
Preamble:
- The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is
executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no
data in uplink.
ETSI

U-S Message
1 SS transmits a downlink assignment including <-- (EPDCCH (C-RNTI)) - -
on PUCCH?
4 SS transmits a downlink assignment to <-- (EPDCCH (unknown C-RNTI)) - -
to the UE
6 Check: Does the UE send any HARQ ACK/ --> HARQ ACK/ NACK 2 F
NACK on PUCCH?
7 SS sends RRCConnectionReconfiguration to - - - -
configure EPDCCH in distributed transmission
mode
8 SS transmits a downlink assignment including <-- (EPDCCH (C-RNTI)) - -
on PUCCH?
11 SS transmits a downlink assignment to <-- (EPDCCH (unknown C-RNTI)) - -
to the UE
13 Check: Does the UE send any HARQ ACK/ --> HARQ ACK/ NACK 4 F
NACK on PUCCH?
NOTE 1: For TDD, the timing of ACK/NACK is not constant as FDD, see Table 10.1-1 of TS 36.213.
Table 7.1.3.14.3.3-1: MAC-MainConfig-RBC (preamble: Table 4.5.3.3-1, step 8)

}
Table 7.1.3.14.3.3-2: PhysicalConfigDedicated (Preamble and step 7)
Derivation Path: 36.508 clause 4.8.2.1.6, Table 4.8.2.1.6-1 with condition ePDCCH
ETSI
Table 7.1.3.14.3.3-3: EPDCCH-Config-r11 (Preamble)
Derivation Path: 36.508 clause 4.6.3, Table 4.6.3-2B

EPDCCH-Config-r11 ::= SEQUENCE{
startSymbol-r11 3
setConfigToAddModList-r11 SEQUENCE 1 entry
(SIZE(1..maxEPDCCH-Set-r11)) OF SEQUENCE {
setConfigId-r11[1] 0
transmissionType-r11[1] localised
resourceBlockAssignment-r11[1] SEQUENCE{
numberPRB-Pairs-r11 n8
resourceBlockAssignment-r11 11100100101110110011
001101100
}
dmrs-ScramblingSequenceInt-r11[1] 0
pucch-ResourceStartOffset-r11[1] 0
re-MappingQCL-ConfigListId-r11[1] Not present
}
}
}
}
Table 7.1.3.14.3.3-4: Void
7.1.3.15 Correct handling of DL assignment / Semi-persistent case / EPDCCH

(1)
and EPDCCH in localized transmission mode }
ensure that {
when { UE receives a DL assignment addressed to its stored SPS-CRNTI in SF-Num y and with NDI set
as 0 }
}
(2)
MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }
ensure that {
when { UE receives a DL assignment addressed to its SPS-CRNTI in SF-Num p and with NDI set as 0,
where p!= y+n*[semiPersistSchedIntervalDL] }
starting at zero }
}
(3)
MAC PDU at SF-Num p+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }
ensure that {
when { UE receives a DL assignment [for retransmission] addressed to its SPS-CRNTI in SF-Num z and
with NDI set as 1, where z!= p+n*[semiPersistSchedIntervalDL] }
}
(4)
MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }
ensure that {
when { UE receives a DL assignment addressed to its CRNTI in SF-Num p, such that p!=
ETSI
}
(5)
PDU at SF-Num z+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }
ensure that {
ConfigurationDL set as ‘disable’ and hence resulting in DL SPS grant deactivation }
}
(6)
MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }
ensure that {
when { UE receives a EPDCCH [for DL SPS explicit release according to Table 9.2-1A in TS 36.213]
addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p!=
z+n*[semiPersistSchedIntervalDL] }
}
(7)
}
ensure that {
when { EPDCCH is configured with distributed transmission type and UE receives a DL assignment
addressed to its stored SPS-CRNTI in SF-Num y and with NDI set as 0 }
}
(8)
ensure that {
addressed to its SPS-CRNTI in SF-Num p and with NDI set as 0, where p!=
starting at zero }
}
(9)
MAC PDU at SF-Num p+n*[semiPersistSchedIntervalDL] }
ensure that {
[for retransmission] addressed to its SPS-CRNTI in SF-Num z and with NDI set as 1, where z!=
p+n*[semiPersistSchedIntervalDL] }
}
(10)
ensure that {
addressed to its CRNTI in SF-Num p, such that p!= y+n*[semiPersistSchedIntervalDL] }
}
ETSI
(11)
PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { EPDCCH is configured with distributed transmission type and UE receives a
RRCConnectionReconfiguration including sps-Configuration with sps-ConfigurationDL set as ‘disable’
and hence resulting in DL SPS grant deactivation }
}
(12)
MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { EPDCCH is configured with distributed transmission type and UE receives a ePDCCH [for DL
SPS explicit release according to Table 9.2-1A in TS 36.213] addressed to its SPS C-RNTI in SF-Num p
and with NDI set as 0, where p!= z+n*[semiPersistSchedIntervalDL] }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.3.1, 5.10 &
5.10.1, 36.331 clause 5.3.10.5, 36.300 clause 11.1.1 and 36.213 clause 9.2. Unless otherwise stated these are Rel-11
requirements.
[TS 36.321, clause 5.3.1]
C-RNTI:
- else, if a downlink assignment for this TTI has been received on the PDCCH for the UE’s Semi-Persistent
Scheduling C-RNTI:
- indicate the presence of a downlink assignment and deliver the associated HARQ information to the
- else, if the NDI in the received HARQ information is 0:
ETSI
- clear the configured downlink assignment (if any);
- if timeAlignmentTimer is running:
- instruct the physical layer to transmit a positive acknowledgement.
- else:
- store the downlink assignment and the associated HARQ information as configured downlink
assignment;
- initialise (if not active) or re-initialise (if already active) the configured downlink assignment to start
in this TTI and to recur according to rules in subclause 5.10.1;
- indicate the presence of a configured downlink assignment and deliver the stored HARQ information
to the HARQ entity for this TTI.
- else, if a downlink assignment for this TTI has been configured and there is no measurement gap in this TTI:
- instruct the physical layer to receive, in this TTI, transport block on the DL-SCH according to the configured
downlink assignment and to deliver it to the HARQ entity;
- indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the
For downlink assignments received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI and for
configured downlink assignments, the HARQ Process ID associated with this TTI is derived from the following
equation:
HARQ Process ID = [floor(CURRENT_TTI/(Downlink Semi-Persistent Scheduling Interval))] modulo Number of

Configured SPS Processes,
where CURRENT_TTI=[(SFN * 10) + subframe number], Downlink Semi-Persistent Scheduling Interval is the
periodicity of semi-persistent scheduling signalled via RRC and Number of Configured SPS Processes is the number of
HARQ processes allocated for semi-persistent scheduling signalled via RRC.
[TS 36.321, clause 5.10]
When Semi-Persistent Scheduling is enabled by upper layer, the following information is provided:


[TS 36.321, clause 5.10.1]
After a Semi-Persistent downlink assignment is configured, the UE shall consider that the assignment recurs in each
subframe for which:
ETSI
- (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * (Downlink Semi-Persistent Scheduling
Interval)] modulo 10240, for all N>0.
Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the configured downlink
assignment were (re-)initialised.
[TS 36.331, clause 5.3.10.5]
The UE shall:
[TS 36.300, clause 11.1.1]
In addition, E-UTRAN can allocate semi-persistent downlink resources for the first HARQ transmissions to UEs:
- RRC defines the periodicity of the semi-persistent downlink grant;
- PDCCH indicates whether the downlink grant is a semi-persistent one i.e. whether it can be implicitly reused in
the following TTIs according to the periodicity defined by RRC.
When required, retransmissions are explicitly signalled via the PDCCH(s). In the sub-frames where the UE has semi-
persistent downlink resource, if the UE cannot find its C-RNTI on the PDCCH(s), a downlink transmission according to
the semi-persistent allocation that the UE has been assigned in the TTI is assumed. Otherwise, in the sub-frames where
the UE has semi-persistent downlink resource, if the UE finds its C-RNTI on the PDCCH(s), the PDCCH allocation
overrides the semi-persistent allocation for that TTI and the UE does not decode the semi-persistent resources.
[TS 36.213, clause 9.2]
RNTI
- the new data indicator field is set to ‘0’. In case of DCI formats 2, 2A, 2B, 2C and 2D, the new data indicator
field refers to the one for the enabled transport block.
A UE shall validate a Semi-Persistent Scheduling assignment EPDCCH only if all the following conditions are met:
- the CRC parity bits obtained for the EPDCCH payload are scrambled with the Semi-Persistent Scheduling C-
RNTI
- the new data indicator field is set to ‘0’. In case of DCI formats 2, 2A, 2B, 2C and 2D, the new data indicator
field refers to the one for the enabled transport block.
1A.
non-matching CRC.
ETSI
Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH/EPDCCH Validation
DCI format 0 DCI format 1/1A DCI format

2/2A/2B/2C/2D
scheduled PUSCH
scheme and
redundancy version
transport block:
set to ‘00’
Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH/EPDCCH Validation

PUSCH
redundancy version
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
UM DRB

DRB
(Where Y+X<P< Y+2X)
UM DRB
SQN=3)on UM DRB
Feedback?
C-RNTI in SF-Num
UM DRB;
SQN=4)on UM DRB
1a)
SQN=5)on UM DRB; Note 1
UM DRB; (Note 1a)
18 The SS Transmits a EPDCCH [for DL SPS <-- EPDCCH [for DL SPS explicit - -
ETSI

SQN=6)on UM DRB;
Feedback?
SQN=6)on UM DRB
SQN=7) on UM DRB
Feedback?
29 SS sends RRCConnectionReconfiguration to - - - -
configure EPDCCH in distributed transmission
mode
UM DRB
DRB
(Where Y+X<P< Y+2X)
UM DRB
SQN=3)on UM DRB
Feedback?
C-RNTI in SF-Num
UM DRB;
SQN=4)on UM DRB
ETSI
1a)
SQN=5)on UM DRB; Note 1
UM DRB; (Note 1a)
47 The SS Transmits a EPDCCH [for DL SPS <-- EPDCCH [for DL SPS explicit - -
SQN=6)on UM DRB
Feedback?
SQN=6)on UM DRB
SQN=7) on UM DRB
Feedback?
Note 1: The DL assignment for C-RNTI and hence the size of MAC PDU is different in size than stored SPS C-RNTI
DL assignment in step 6. This assures UE is receiving DSCH data as per DL assignment for C-RNTI and not
as per stored grant for SPS C-RNTI.
Note 1a: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in
Note 1b: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption
Note 2: For TDD, the subframe number for ‘Y’, ‘P’, ‘Z’ and ‘Q’ should be ‘0’, ‘4’, ‘5’ and ‘9’ respectively based on TDD
configuration 1.
ETSI
Table 7.1.3.15.3.3-1: RadioResourceConfigDedicated (Preamble)

explicitValue SEQUENCE{
drx-Config CHOICE { pc_FeatrGrp
_5 AND
DRX_S
setup SEQUENCE {
}
}
}
}
sps-Config ::= SEQUENCE {
enable SEQUENCE {
semiPersistSchedIntervalDL sf40 40 Subframe
numberOfConfSPS-Processes 8 FDD
numberOfConfSPS-Processes 7 Max DL HARQ TDD
processes is 7
considering TDD
configuration 1.
n1Pucch-AN-Persistent 0
}
}
}
}
Table 7.1.3.15.3.3-2: PhysicalConfigDedicated (Preamble in Table 4.5.3.3-1 step 8, and step 29 in

Table 7.1.3.15.3.2-1)
Derivation Path: 36.508 clause 4.8.2.1.6, Table 4.8.2.1.6-1 with condition ePDCCH
Table 7.1.3.15.3.3-3: RadioResourceConfigDedicated (step 25 and 54 of table 7.1.3.15.3.2-1)

disable NULL
}
}
}
ETSI
Table 7.1.3.15.3.3-4: EPDCCH-SetConfig-r11 (preamble: Table 4.5.3.3-1, step 8)
Derivation Path: 36.508 clause 4.6.3, Table 4.6.3-2B

EPDCCH-Config-r11 ::= SEQUENCE{
startSymbol-r11 3
setConfigToAddModList-r11 SEQUENCE 1 entry
(SIZE(1..maxEPDCCH-Set-r11)) OF SEQUENCE {
setConfigId-r11[1] 0
transmissionType-r11[1] localised
resourceBlockAssignment-r11[1] SEQUENCE{
numberPRB-Pairs-r11 n8
resourceBlockAssignment-r11 11100100101110110011
001101100
}
dmrs-ScramblingSequenceInt-r11[1] 0
pucch-ResourceStartOffset-r11[1] 0
re-MappingQCL-ConfigListId-r11[1] Not present
}
}
}
}
Table 7.1.3.15.3.3-5: Void
7.1.4 UL-SCH data transfer

7.1.4.1 Correct handling of UL assignment / Dynamic case
(1)
ensure that {
when { UE receives for a TTI an uplink grant with valid C-RNTI }
then { UE transmits data and associated HARQ information to the HARQ entity for this TTI }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 5.4.1.
[TS 36.321, clause 5.4.1]
In order to transmit on the UL-SCH the UE must have a valid uplink grant (except for non-adaptive HARQ
retransmissions) which it may receive dynamically on the PDCCH or in a Random Access Response or which may be
configured semi-persistently. To perform requested transmissions, the MAC layer receives HARQ information from
lower layers.
When timeAlignmentTimer is running and the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-
RNTI, the UE shall for each TTI :
- if an uplink grant for this TTI has been received in a Random Access Response:
- set NDI to the value 0 and consider the NDI to have been toggled.
- if an uplink grant for this TTI has been received on the PDCCH for the UE’s C-RNTI or Temporary C-
RNTI; or
- if the uplink grant is for UE’s C-RNTI and if the previous uplink grant delivered to the HARQ entity for the
same HARQ process was either an uplink grant received for the UE’s Semi-Persistent Scheduling C-RNTI or
a configured uplink grant:
ETSI
- deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.
- else, if an uplink grant for this TTI has been received on the PDCCH for the UE’s Semi-Persistent C-RNTI:
- indicate a valid uplink grant and the associated HARQ information to the HARQ entity for this TTI.
...
NOTE 1: The period of configured uplink grants is expressed in TTIs.
NOTE 2: If the UE receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi
persistent scheduling C-RNTI requiring transmissions in the same UL subframe, the UE may choose to
continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling
C-RNTI.
NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH
transmission during a measurement gap, the UE processes the grant but does not transmit on UL-SCH.
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS ignores scheduling requests and does - - - -
not allocate any uplink grant.
2 SS transmits a MAC PDU including a RLC <-- MAC PDU 1 -
SDU
3 Void --> - - -
- EXCEPTION: Step 4 runs in parallel with - - - -
behaviour in table 7.1.4.1.3.2-2
4 The SS is configured for Uplink Grant <-- (UL Grant (unknown C-RNTI)) - -
Allocation Type 2. For 400 ms SS transmits
an UL Grant every 10 ms, allowing the UE to
return the RLC SDU as received in step 2, on
PDCCH, but with the C-RNTI different from the
C-RNTI assigned to the UE. Note 1.
5 Check: Does the UE transmit a MAC PDU --> MAC PDU 1 F
corresponding to grant in step 4?
6 The SS is configured for Uplink Grant <-- (UL Grant (C-RNTI)) - -
Allocation Type 2. SS transmits an UL Grant,
allowing the UE to return the RLC SDU as
received in step 2, on PDCCH with the C-RNTI
assigned to the UE.
Note 1: Note 400 ms corresponding to 40 frames is selected to be sufficiently large than loop back delay and small
than the time needed for Scheduling Request to be repeated dsr-TransMax times( {64-1}* 20 milliseconds).

U-S Message
1 UE transmits a Scheduling Request. --> (SR) - -
7.1.4.1.3.3 Specific message contents.
Table 7.1.4.1.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration

in preamble

setup SEQUENCE {
}
}
ETSI

c1 CHOICE{
}
}
}
}
}
}
7.1.4.2 Correct handling of UL assignment / Semi-persistent case

(1)
with { UE in E-UTRA RRC_Connected state with DRB established and sps-Configuration in UL is enabled
}
ensure that {
when { UE receives a UL grant addressed to its stored SPS-CRNTI in SF-Num y and with NDI set as 0
}
then { UE starts transmitting UL MAC PDU in SF-Num F1 }
}
(2)
with { UE in E-UTRA RRC_Connected state with DRB established and stored UL SPS grant to transmit MAC
PDU at SF-Num F1 }
ensure that {
when { UE receives a UL grant addressed to its SPS-CRNTI in SF-Num-frame p and with NDI set as 0,
where p+4!=F1(FDD) or p+k(p)!=F1(TDD) }
then { UE starts transmitting UL MAC PDU in SF-Num F2 and stops transmitting UL MAC PDU at SF-
Num F1 }
}
(3)
PDU at SF-Num F1 }
ensure that {
when { UE receives a UL grant [for retransmission] addressed to its SPS-CRNTI in SF-Num z and with
NDI set as 1, for the corresponding HARQ Process, where z+4!=F1(FDD) or z+k(z)!=F1(TDD) }
then { UE re-transmits MAC PDU in SF-Num z+4(FDD) or z+k(z)(TDD) as per the new grant for SPS-
CRNTI }
}
(4)
PDU at SF-Num F3 }
ensure that {
when { UE receives a UL grant addressed to its CRNTI in SF-Num p, such that in SF-Num p+4=F3(FDD)
or p+k(p)=F3(TDD) }
then { UE transmits MAC PDU in SF-Num p+4(FDD) or p+k(p)(TDD) as per grant addressed to its C-
RNTI }
}
(5)
PDU at SF-Num F3 }
ETSI
ensure that {
ConfigurationUL set as ‘disable’ and hence resulting in UL SPS grant deactivation }
then { UE deletes the stored sps-Configuration UL parameters and stops transmitting UL MAC PDU’s
as per stored SPS grant in SF-Num F3 }
}
(6)
with { UE in E-UTRA RRC_Connected state with DRB established and configured UL SPS grant }
ensure that {
when { UE transmits ‘implicitReleaseAfter‘ MAC PDU’s on SPS-Grant containing zero MAC SDU }
then { UE clears configured SPS grant }
}
(7)
PDU at SF-Num F3 }
ensure that {
when { UE receives a PDCCH [for UL SPS explicit release according to Table 9.2-1A in TS 36.213]
addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p+4!=F3(FDD) or p+k(p)!=F3(TDD)
}
then { UE releases the configured SPS grant and stops transmitting UL MAC PDU in SF-Num F3 as
per grant addressed to its SPS C-RNTI }
}
NOTE 2: The value of the k(y), k(p), k(z) is k value determined according to the table 8-2 in the TS 36.213, given
that UL grant is in subframe y, p, z.
NOTE 3: The Subframe_Offset(y+k(y)), Subframe_Offset(p+k(p)), Subframe_Offset(z+k(z)) is subframe_offset

value determined according to the clause 5.10.2 in the TS36.321, given the position of initial Semi-
Persistent grant on subframe y+k(y), p+k(p), z+k(z).
NOTE 4: To simply the TP description, following abbreviations are defined:
For FDD:
F1 = y+4+n*[semiPersistSchedIntervalUL]
F2 = p+4+n*[semiPersistSchedIntervalUL]
F3 = z+4+n*[semiPersistSchedIntervalUL]
For TDD:
F1 = y+k(y)+n*[semiPersistSchedIntervalUL]+ Subframe_Offset(y+k(y))*(n modulo 2)
F2 = p+k(p)+n*[semiPersistSchedIntervalUL]+ Subframe_Offset(p+k(p))*(n modulo 2)
F3 = z+k(z)+n*[semiPersistSchedIntervalUL]+ Subframe_Offset(z+k(z))*(n modulo 2)
n >= 0
References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.1, 5.10,
5.10.2, 7.4, 36.331 clause 5.3.10.5, 36.213 clause 8, 9.2 and 36.300 clause 11.1.2.
[TS 36.321, clause 5.4.1]
In order to transmit on the UL-SCH the UE must have a valid uplink grant (except for non-adaptive HARQ
retransmissions) which it may receive dynamically on the PDCCH or in a Random Access Response or which may be
configured semi-persistently. To perform requested transmissions, the MAC layer receives HARQ information from
lower layers.
When timeAlignmentTimer is running and the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-
RNTI, the UE shall for each TTI:
ETSI
- set NDI to the value 0 and consider the NDI to have been toggled.
- if an uplink grant for this TTI has been received on the PDCCH for the UE’s C-RNTI or Temporary C-RNTI; or
- if the uplink grant is for UE’s C-RNTI and if the previous uplink grant delivered to the HARQ entity for the
same HARQ process was the uplink grant is for UE’s C-RNTI and if the previous uplink grant delivered to
the HARQ entity for the same HARQ process was either an uplink grant received for the UE’s Semi-
Persistent Scheduling C-RNTI or a configured uplink grant:
- else, if an uplink grant for this TTI has been received on the PDCCH for the UE’s Semi-Persistent Scheduling C-
RNTI:
- else if the NDI in the received HARQ information is 0:
- clear the configured uplink grant (if any).
- else:
- store the uplink grant and the associated HARQ information as configured uplink grant;
- initialise (if not active) or re-initialise (if already active) the configured uplink grant to start in this TTI
and to recur according to rules in subclause 5.10.2;
- deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this
TTI.
- else, if an uplink grant for this TTI has been configured:
- deliver the configured uplink grant, and the associated HARQ information to the HARQ entity for this TTI.
NOTE 1: The period of configured uplink grants is expressed in TTIs.
NOTE 2: If the UE receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi
persistent scheduling C-RNTI requiring transmissions in the same UL subframe, the UE may choose to
continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling
C-RNTI.
NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH
transmission during a measurement gap, the UE processes the grant but does not transmit on UL-SCH.
[TS 36.321, clause 5.10]
When Semi-Persistent Scheduling is enabled by RRC, the following information is provided:

ETSI

[TS 36.321, clause 5.10.2]
After a Semi-Persistent Scheduling uplink grant is configured, the UE shall:
- if twoIntervalsConfig is enabled by upper layer;
- set the Subframe_Offset according to Table 7.4-1.
- else:
- set Subframe_Offset to 0.
- consider that the grant recurs in each subframe for which:
- (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * semiPersistSchedIntervalUL +

Subframe_Offset * (N modulo 2)] modulo 10240, for all N>0.
Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the configured uplink grant
were (re-)initialised.
The UE shall clear the configured uplink grant immediately after implicitRelease after number of consecutive new
MAC PDUs each containing zero MAC SDUs have been provided by the Multiplexing and Assembly entity, on the
Semi-Persistent Scheduling resource.
NOTE 4: Retransmissions for Semi-Persistent Scheduling can continue after clearing the configured uplink grant.
[TS 36.321, clause 7.4]
Subframe_Offset values are presented in Table 7.4-1.
Table 7.4-1: Subframe_Offset values
TDD UL/DL configuration Position of initial Semi-Persistent grant Subframe_Offset value (ms)
0 N/A 0
Subframes 2 and 7 1
1
Subframes 3 and 8 -1
Subframe 2 5
2
Subframe 7 -5
Subframes 2 and 3 1
3
Subframe 4 -2
Subframe 2 1
4
Subframe 3 -1
5 N/A 0
6 N/A 0
[TS 36.331, clause 5.3.10.5]
The UE shall:
[TS 36.213, clause 8]
For TDD UL/DL configurations 1 and 6 and subframe bundling operation, the UE shall upon detection of a PDCCH
with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in subframe n-l
ETSI
with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe n+k, with k
given in Table 8-2, according to the PDCCH and PHICH information.
Table 8-2 k for TDD configurations 0-6
TDD UL/DL DL subframe number n

Configuration 0 1 2 3 4 5 6 7 8 9
0 4 6 4 6
1 6 4 6 4
2 4 4
3 4 4 4
4 4 4
5 4
6 7 7 7 7 5
…
[TS 36.213, clause 9.2]
RNTI
- the new data indicator field is set to ‘0’. In case of DCI formats 2 and 2A, the new data indicator field refers to
the one for the enabled transport block.
1A.
non-matching CRC.
Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation
DCI format 0 DCI format 1/1A DCI format 2/2A

scheduled PUSCH
scheme and
redundancy version
transport block:
set to ‘00’
ETSI
Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH Validation

PUSCH

redundancy version
[TS 36.300, clause 11.1.2]
In addition, E-UTRAN can allocate a semi-persistent uplink resource for the first HARQ transmissions and potentially
retransmissions to UEs:
- RRC defines the periodicity of the semi-persistent uplink grant;
- PDCCH indicates whether the uplink grant is a semi-persistent one i.e. whether it can be implicitly reused in the
following TTIs according to the periodicity defined by RRC.
In the sub-frames where the UE has semi-persistent uplink resource, if the UE cannot find its C-RNTI on the
PDCCH(s), an uplink transmission according to the semi-persistent allocation that the UE has been assigned in the TTI
can be made. The network performs decoding of the pre-defined PRBs according to the pre-defined MCS. Otherwise, in
the sub-frames where the UE has semi-persistent uplink resource, if the UE finds its C-RNTI on the PDCCH(s), the
PDCCH allocation overrides the persistent allocation for that TTI and the UE’s transmission follows the PDCCH
allocation, not the semi-persistent allocation. Retransmissions are either implicitly allocated in which case the UE uses
the semi-persistent uplink allocation, or explicitly allocated via PDCCH(s) in which case the UE does not follow the
semi-persistent allocation.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL of same
size.
ETSI

U-S Message
0A SS transmits RRCConnectionReconfiguration <-- - - -
to configure UL SPS
0B The UE transmits --> - - -
1 The SS transmits a DL MAC PDU containing <-- MAC PDU - -
10 RLC SDU’s on UM DRB.
2 The UE transmits a Scheduling Request, --> (SR) - -
indicating that loop back PDUs are ready for
transmission in UL RLC
3 The SS transmits an UL Grant using UE’s SPS <-- (UL SPS Grant) - -
C-RNTI in SF-Num ‘4’, NDI=0, allowing the UE
to transmit one loop back PDU per MAC PDU.
4 Check: Does the UE transmit a MAC PDU in --> MAC PDU 1 P
SF-Num ‘8’ as per grant in step 3?
5 The SS transmits a HARQ ACK <-- HARQ ACK - -
SF-Num ‘48(FDD)/47(TDD)’ as per grant in
step 3?
8 The SS Transmits an UL Grant using UE’s <-- (UL SPS Grant) - -
SPS C-RNTI in SF-Num ‘64’, NDI=0 and
allowing the UE to transmit two loop back
PDUs per MAC PDU.
11 Check: Does the UE transmit a MAC PDU in --> MAC PDU 2 F
step 8?
SPS C-RNTI in SF-Num ‘120 (FDD)/121
(TDD)’, NDI=1; the UL HARQ process is the
same as in step 12
15 Check: Does the UE transmit in SF-Num ‘124 --> MAC PDU 3 P
(FDD)/127 (TDD)’ a MAC PDU as in step 12?
19 The SS Transmits an UL Grant using UE’s C- <-- (UL Grant) - -
RNTI in SF-Num ‘164(FDD)/161(TDD)’;
allowing UE to transmit a MAC PDU containing
two RLC SDU’s
step 19?
22 The SS transmits a PDCCH [for UL SPS <-- PDCCH [for UL SPS explicit - -
Num ‘180’ with NDI=0.
SF-Num ‘188’ as per grant in step 8 containing
zero MAC SDU?
24 The SS transmits an UL Grant using UE’s SPS <-- (UL SPS Grant) - -
C-RNTI in SF-Num ‘399’, NDI=0, transmit one
loop back PDU per MAC PDU
SF-Num ‘403’ as per grant in step 24
ETSI
containing zero MAC SDU?

SF-Num ‘443 (FDD)/442 (TDD)’ as per grant in
step 24 containing zero MAC SDU?
SPS C-RNTI in SF-Num ‘604’, NDI=0, transmit
one loop back PDU per MAC PDU.
SF-Num ‘608’ as per grant in step 30
containing zero MAC SDU?
33 SS Transmits RRCConnectionReconfiguration <-- - - -
to disable SPS-ConfigurationUL.
35 The SS transmits a DL MAC PDU containing 1 <-- MAC PDU - -
RLC SDU
36 Void - - - -
SF-Num ‘648 (FDD)/647 (TDD)’ as per grant in
step 30?
Table 7.1.4.2.3.3-1: RRCConnectionReconfiguration. RadioResourceConfigDedicated (Step 0A)

sps-ConfigurationDL Not Present
sps-ConfigurationUL::=CHOICE{
enable SEQUENCE {
semiPersistSchedIntervalUL sf40 40 Subframe
implicitReleaseAfter e2
p0-Persistent Not Present
twoIntervalConfig Not Present FDD
twoIntervalConfig true TDD
}
}
}
}
Table 7.1.4.2.3.3-2: RRCConnectionReconfiguration. RadioResourceConfigDedicated (step 33 of table

7.1.4.2.3.2-1)

sps-ConfigurationDL Not Present
sps-ConfigurationUL::=CHOICE{
disable NULL
}
}
}
ETSI

c1 CHOICE{
drx-Config CHOICE { pc_FeatrGr
p_5 AND
DRX_S
setup SEQUENCE {
}
}
}
}
}
}
}
7.1.4.3 Logical channel prioritization handling

(1)
ensure that {
when { sending data on the uplink }
then { UE serves the logical channels according to their priority and configured PBR }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 5.4.3.1.
[TS 36.321, clause 5.4.3.1]
The Logical Channel Prioritization procedure is applied when a new transmission is performed.
RRC controls the scheduling of uplink data by signalling for each logical channel: priority where an increasing priority
value indicates a lower priority level, prioritisedBitRate which sets the Prioritized Bit Rate (PBR), bucketSizeDuration
which sets the Bucket Size Duration (BSD).
The UE shall maintain a variable Bj for each logical channel j. Bj shall be initialized to zero when the related logical
channel is established, and incremented by the product PBR × TTI duration for each TTI, where PBR is Prioritized Bit
Rate of logical channel j. However, the value of Bj can never exceed the bucket size and if the value of Bj is larger than
the bucket size of logical channel j, it shall be set to the bucket size. The bucket size of a logical channel is equal to
PBR × BSD, where PBR and BSD are configured by upper layers.
The UE shall perform the following Logical Channel Prioritization procedure when a new transmission is performed:
- The UE shall allocate resources to the logical channels in the following steps:
- Step 1: All the logical channels with Bj > 0 are allocated resources in a decreasing priority order. If the PBR
of a radio bearer is set to “infinity”, the UE shall allocate resources for all the data that is available for
transmission on the radio bearer before meeting the PBR of the lower priority radio bearer(s);
- Step 2: the UE shall decrement Bj by the total size of MAC SDUs served to logical channel j in Step 1
ETSI
NOTE: The value of Bj can be negative.
- Step 3: if any resources remain, all the logical channels are served in a strict decreasing priority order
(regardless of the value of Bj) until either the data for that logical channel or the UL grant is exhausted,
whichever comes first. Logical channels configured with equal priority should be served equally.
- The UE shall also follow the rules below during the scheduling procedures above:
- the UE should not segment an RLC SDU (or partially transmitted SDU or retransmitted RLC PDU) if the
whole SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources;
- if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill
the grant as much as possible;
- UE should maximise the transmission of data.
The UE shall not transmit data for a logical channel corresponding to a radio bearer that is suspended (the conditions for
when a radio bearer is considered suspended are defined in [8]).
For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in
decreasing order:
- MAC control element for C-RNTI or data from UL-CCCH;
- MAC control element for BSR, with exception of BSR included for padding;
- MAC control element for PHR;
- data from any Logical Channel, except data from UL-CCCH;
- MAC control element for BSR included for padding.
System Simulator:
- Cell 1
UE:
None
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.1.4.3.3.1-2
applicable for the configured UM DRBs and table 7.1.4.3.3.1-3 for SR configuration.
- The 3 UM DRBs are configured according to table 7.1.4.3.3.1-1.
Table 7.1.4.3.3.1-1: Priority, PBR and Bucket Delay settings
DRB priority prioritizedBitRate bucketSizeDuration

(kbytes/s) (ms)
DRB1 6 8 100
DRB2 7 16 100
DRB3 8 32 100
Table 7.1.4.3.3.1-2: PDCP Settings
Parameter Value
Discard_Timer ms1500
ETSI
Table 7.1.4.3.3.1-3: SchedulingRequest-Config

dsr-TransMax n16

U-S Message
- EXCEPTION: Steps 0 to 4 are run 4 times - - - -
using the parameters specified for each run in
table 7.1.4.3.3.2-3.
0 Void - - - -
1 The SS transmits N1 320-octet RLC SDUs on <-- (RLC SDUs) - -
DRB1, N2 320-octet RLC SDUs on DRB2, and
N3 320-octet RLC SDUs on DRB3.
- EXCEPTION: In parallel to the event described - - - -
in step 2 the events specified in Table
7.1.4.3.3.2-2 shall take place.
2 The SS is configured for Uplink Grant <-- (UL grants) - -
Allocation Type 2. 150 ms after Step 1 (Note1),
for a duration of T2, the SS transmits an UL
grant of D octets every T1.
3 Check: are the total number of octets of the UL - - 1 P
RLC SDUs received at the SS for each DRB
as follows?
- the total number of octets received for DRB1

is D1 octets +/- 10%
4 The SS re-establishes the RLC for each RB at - - - -

the UE by sending an
RRCConnectionReconfiguration for intra-cell
handover with SR configuration set as per
Table 7.1.4.3.3.1-3.
Note 1: This wait time will ensure that a) all octets have been completely received by the UE on all 3 DRBs before
the first UL grant is received and b) the Bjs for each logical channel have reached their maximum value i.e.
the bucket size of the corresponding logical channel before the first UL grant is received.

U-S Message
1 Check: Does the UE transmit the RLC SDUs --> - 1 P
back to the SS?
ETSI
Table 7.1.4.3.3.2-3: Test parameter values
Parameter First run Second run Third run Fourth run

N1 (SDUs) 13 13 7 104
N2 (SDUs) 25 25 50 25
N3 (SDUs) 50 50 50 50
D (octets) 1143 573 1143 1143
T1 (ms) 20 20 20 10
T2 (ms) 500 700 500 500
D1 (octets) 4160 4160 2240 33000 (Note 1)
D2 (octets) 8000 8000 10260 (Note 1) 8000
D3 (octets) 16000 7790 (Note 1) 16000 16000
Note 1: It is calculated from the following equation for the case of the least header size.
(D1 + D2 + D3) = (D - 3) * T2 / T1
NOTE: the numbers above and the test procedure assume that the UE has a loopback buffer of at least 57280
octets.
Derivation Path: 36.508 table 4.6.1-8: RRCConnectionReconfiguration, condition HO

c1 CHOICE{
mobilityControlInfo SEQUENCE {
targetPhysCellId Set to the physical cell
identity of cell 1
}
}
}
}
}
7.1.4.4 Correct handling of MAC control information / Scheduling requests and

PUCCH
(1)
ensure that {
when { PUCCH is configured and UE has UL data available for transmission and UE has no UL-SCH
resources available and SR_COUNTER is less than dsr-TransMax }
then { the UE transmits a SR on every available PUCCH until resources are granted }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and has pending SR(s) }
ensure that {
when { UE receives an UL grant for a new transmission }
then { UE cancels all pending SR(s) }
}
ETSI
[TS 36.321, clause 5.4.4]
The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.
When an SR is triggered, it shall be considered as pending until it is cancelled.
If an SR is triggered and there is no other SR pending, the UE shall set the SR_COUNTER to 0.
As long as one SR is pending, the UE shall for each TTI:
- if no UL-SCH resources are available for a transmission in this TTI:
- if the UE has no valid PUCCH resource for SR configured in any TTI: initiate a Random Access procedure
(see subclause 5.1) and cancel all pending SRs;
- else if the UE has a valid PUCCH resource for SR configured for this TTI and if this TTI is not part of a
measurement gap:
- if SR_COUNTER < dsr-TransMax:
- increment SR_COUNTER by 1;
- instruct the physical layer to signal the SR on PUCCH;
- else:
- initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs.
- else if UL-SCH resources for new transmission are granted in this TTI, cancel all pending SR(s).7.1.4.4.3 Test
description
System Simulator:
- - Cell 1
7.1.4.4.3.3-1
UE:
None.
Preamble:
Table 7.1.4.4.3.1-1: RLC settings
Parameter Value
t-PollRetransmit 250 ms
ETSI

U-S Message
1 The SS transmits a MAC PDU containing 10 <-- MAC PDU (containing 10 MAC - -
MAC SDUs each containing a RLC SDU SDUs)
- EXCEPTION: Step 2 runs in parallel with - - - -
behaviour in table 7.1.4.4.3.2-2.
2 Check: Does the UE transmit 6 Scheduling --> (SR) 1 P
Requests separately on 6 consecutively
available PUCCHs? (Note 1)
3 The SS is configured for Uplink Grant <-- (UL Grant ) - -
Allocation Type 3. The SS transmits an UL
grant to allocate UL-SCH resources that are
enough to transmit MAC PDU containing 10
MAC SDUs
4 Check: Does the UE transmit a MAC PDU --> MAC PDU (containing 10 MAC 1 P
containing 10 RLC PDUs? SDUs)
5 Check: 1 second does the UE transmit a --> (SR) 1,2 F
Scheduling Request in the next 100ms?
Note 1: The UE repeats the scheduling requests on every available PUCCH as long as SR_COUNTER < dsr-
TransMax and there is UL data available for transmission and there are no resources available to transmit
it. At the reception of first Scheduling Request from the UE, SS will be scheduled to transmit a grant after
100ms. Hence SS will receive 6 Scheduling Requests as sr-ConfigIndex = 30.

U-S Message
1 Check: Does the UE transmit a MAC PDU? --> MAC PDU 1 F
Table 7.1.4.4.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration

in preamble

SchedulingRequest-Configuration::= CHOICE {
enable SEQUENCE {
dsr-TransMax n64
}
}
None.
7.1.4.5 Correct handling of MAC control information / Scheduling requests and

random access procedure
(1)
with { The UE is in E-UTRA RRC_CONNECTED state and no PUCCH resource for SR is configured }
ensure that {
when { UE has UL data available for transmission, UE has no UL-SCH resources available and time
alignment timer expires }
then { the UE initiates the random access procedure }
}
ETSI
(2)
with { The UE in E-UTRA RRC_CONNECTED state )
ensure that {
when { PUCCH Configured and UE has UL data available for transmission and UE has no UL-SCH
resources available and SR_COUNTER becomes equal to dsr-TransMax }
then { the UE transmits a PRACH Preamble to initiate a Random Access procedure }
:}
References: The conformance requirements covered in the current TC are specified in: TS 36.321 , clause 5.4.4.
[TS 36.321 clause 5.4.4]
When an SR is triggered, it shall be considered as pending until it is cancelled.
If an SR is triggered and there is no other SR pending, the UE shall set the SR_COUNTER to 0.
As long as one SR is pending, the UE shall for each TTI:
- if no UL-SCH resources are available for a transmission in this TTI:
- if the UE has no valid PUCCH resource for SR configured in any TTI: initiate a Random Access procedure
(see subclause 5.1) and cancel all pending SRs;
- else if the UE has a valid PUCCH resource for SR configured for this TTI and if this TTI is not part of a
measurement gap:
- if SR_COUNTER < dsr-TransMax:
- increment SR_COUNTER by 1;
- instruct the physical layer to signal the SR on PUCCH;
- else:
- initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs.- else if UL-SCH resources
for new transmission are granted in this TTI, cancel all pending SR(s).
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS transmits a MAC PDU containing a <-- MAC PDU (Timing Advance - -
Timing Advance Command MAC Control Command)
Element, but does not send any subsequent
alignments.
1A The SS transmits a MAC PDU containing a <-- MAC PDU (MAC SDU) - -
MAC SDU
- EXCEPTION: Step 2B is repeated less than 64 - - - -
times (dsr-TransMax)
2B The UE may transmit Scheduling Requests --> (SR) - -
before time alignment timer expires. The SS
shall not respond to the Scheduling Requests
in this step. (Note 5)
PRACH? (Note 1)
3 The SS transmits a Random Access Response <-- Random Access Response - -
including an UL grant to enable UE to transmit
C-RNTI MAC Control Element and the MAC
SDU as received in step 1A.
4 The UE transmit a MAC PDU including a C- --> MAC PDU (C-RNTI control - -
RNTI MAC Control Element and a MAC SDU. element, MAC SDU)
(Note 2)
5 The SS sends PDCCH transmission for UE C- <-- - - -
RNTI
5A The SS transmits <-- - -
RRCConnectionReconfiguration containing a
radioResourceConfiguration with a physical
channel reconfiguration
- EXCEPTION: Steps 5A1 to 5A4 are optionally - - -
executed. (Note 6)
5A The UE transmits a preamble on PRACH. --> (PRACH Preamble) - -
1 (Note 6)
5A The SS transmits a Random Access Response <-- Random Access Response - -
2 including an UL grant of 7 bytes. (Note 7)
5A The UE transmit a MAC PDU including a C- --> - - -
3 RNTI MAC Control Element
5A The SS sends PDCCH transmission for UE C- <-- - - -
4 RNTI of 5 bytes (Note 9)
5B The UE transmits a Scheduling Request on --> (SR) - -
PUCCH. (Note 8)
5C The SS transmits an UL grant to enable UE to <-- (UL Grant) - -
transmit the
message. (Note 10)
5D The UE transmits --> - - -
message.
5E Void - - - -
6 The SS ignores any Scheduling Requests from - - - -
the UE.
7 The SS transmits a MAC PDU containing one <-- MAC PDU MAC SDU) - -
MAC SDU containing a RLC SDU
- EXCEPTION: Step 8 shall be repeated 8 - - - -
times.
PUCCH (Note 3)
PRACH? (Note 4)
10 The SS transmits a Random Access Response <-- Random Access Response - -
including an UL grant to enable UE to transmit
C-RNTI MAC Control Element and the MAC
SDU as received in step 7.
ETSI
11 The UE transmit a MAC PDU including a C- --> MAC PDU (C-RNTI control - -
RNTI MAC Control Element and a MAC SDU. element, MAC SDU)
(Note 2)
12 The SS sends PDCCH transmission for UE C- <-- - - -
RNTI
Note 1: When UL time alignment timer expires in the UE then "UL synchronization" is lost and the UE initiates a
Random Access Procedure.
Note 2: The UE transmission of the MAC PDU ensures that the random access procedure was successful.
Note 3: The UE repeats the scheduling requests as long as SR_COUNTER < dsr-TransMax and there is data in
the transmission buffer and there are no resources available to transmit it.
Note 4: Reception of PRACH Preamble by the SS verifies that UE has initiated a Random Access procedure
triggered by SR_COUNTER having reached dsr-TransMax.
Note 5: In step 2B, SR repetition of 63 times (dsr-TransMax (64)) will take at least 63*20 = 1260 ms which is much
larger than TA timer 750ms.
Note 6: RLC status PDU may trigger the UE to transmit PRACH Preamble.
Note 7: UL grant of 56 bits (ITBS=4, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to
transmit C-RNTI MAC Control Element but not allowing the UE to transmit RRCConnectionReconfiguration
Complete. 7 bytes allow transmission of C-RNTI + Short BSR or C-RNTI + STATUS PDU.
Note 8: If RRCConnectionReconfigurationComplete was not ready for transmission in step 5A3 then SR is
triggered when RRC message arrives in the transmission buffer. Otherwise
(RRCConnectionReconfigurationComplete was ready for the transmission in step 5A3) the SR is triggered
because expiry of the retxBSR-Timer.
Note 9: 5 bytes are assigned so that STATUS PDU can be included if it was not transmitted by the UE in step 5A3
(see Note 7) (5 bytes assignment allow transmission of Short BSR + STATUS PDU)
Note 10: STATUS PDU is included if optional test steps 5A1 to 5A4 were not executed.
Table 7.1.4.5.3.3-1: SchedulingRequest-Config to be used in RRCConnectionReconfiguration (

preamble, Table 7.1.4.5.3.2-1)

SchedulingRequest-Config-DEFAULT::= CHOICE {
setup SEQUENCE {
dsr-TransMax n64
}
}
Table 7.1.4.5.3.3-2: RRCConnectionReconfiguration (step 5A, Table 7.1.4.5.3.2-1)

rrc-TransactionIdentifier RRC-
TransactionIdentifier-DL
c1 CHOICE{
measConfig Not present
mobilityControlInfo Not present
dedicatedInfoNASList Not present
radioResourceConfigDedicated RadioResourceConfigDe
dicated-Step5a
securityConfigHO Not present
}
}
}
}
ETSI
Table 7.1.4.5.3.3-3: RadioResourceConfigDedicated-Step5A (Table 7.1.4.5.3.3-2)

RadioResourceConfigDedicated-HO ::= SEQUENCE
{
srb-ToAddModList Not present
drb-ToAddModList Not present
drb-ToReleaseList Not present
mac-MainConfig Not present
sps-Config Not present
physicalConfigDedicated PhysicalConfigDedicated-
Step5a
}
Table 7.1.4.5.3.3-4: PhysicalConfigDedicated-Step5A (Table 7.1.4.5.3.3-3)

pdsch-ConfigDedicated Not present
pucch-ConfigDedicated Not present
pusch-ConfigDedicated Not present
uplinkPowerControlDedicated Not present
tpc-PDCCH-ConfigPUCCH Not present
tpc-PDCCH-ConfigPUSCH Not present
cqi-ReportConfig CQI-ReportConfig- See subclause
DEFAULT using 4.6.3 of 36.508
condition
CQI_PERIODIC
soundingRS-LU-ConfigDedicated SoundingRS-ULl- See subclause
ConfigDedicated- 4.6.3 of 36.508
DEFAULT
antennaInfo Not present
schedulingRequestConfig SchedulingRequest-
Config- Config-Step5a
}
Table 7.1.4.5.3.3-5: SchedulingRequest-Config-Step5A (Table 7.1.4.5.3.3-4)

SchedulingRequest-Config::= CHOICE {
enable SEQUENCE {
dsr-TransMax n8
}
}
Table 7.1.4.5.3.3-6: MAC-MainConfig-RBC in RRCConnectionReconfiguration(preamble)
Derivation Path: 36.508 table 4.8.2.1.5-1

MAC-MainConfigRBC- ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
retxBSR-Timer sf320
}
}
ETSI
7.1.4.6 Correct handling of MAC control information / Buffer status / UL data arrive in
the UE Tx buffer and retransmission of BSR / Regular BSR
(1)
with ( UE in E-UTRA RRC_CONNECTED state )
ensure that {
when { UL data arrives in the UE transmission buffer and the data belongs to a logical channel
with higher priority than those for which data is already available for transmission and the new
logical channel and the existing logical channels belongs to the different LCG }
then { UE Reports a Long Buffer Status Reporting (BSR) }
}
(2)
ensure that {
when { UL data arrives in the UE transmission buffer and there is no data available for
transmission for any of the logical channels which belong to a LCG }
then { UE Reports a Short Buffer Status Reporting (BSR) }
}
(3)
ensure that {
when { UL data arrives in the UE transmission buffer and the data belongs to a logical channel
with higher priority than those for which data is already available for transmission and the new
logical channel and existing logical channels belong to the same LCG }
then { UE Reports a Short Buffer Status Reporting (BSR) }
}
(4)
ensure t hat {
when{RETX_BSR_TIMER expires and only one LCG has data available for transmission }
then { UE triggers a regular BSR and Reports a Short Buffer Status Reporting ( BSR)}
}
(5)
with (UE in E-UTRA RRC_CONNECTED stat e)
ensure that {
when { a Regular BSR has been triggered and UE has pending data for transmission and UE has only
resources to send either BSR report or data }
then { UE transmits the BSR report }
}
(6)
ensure that {
when { UE determines that a BSR has been triggered since the last transmission of a BSR and UE has
no UL resources allocated for new transmission for this TTI }
then { UE transmits a scheduling request }
}
(7)
with (UE in E-UTRA RRC_CONNECTED state)
ensure that {
when { a Regular BSR has been triggered and UE has pending data on several logical channels for
transmission and UE has only UL resources to send all pending data available for transmission, but
UL grant is not sufficient to additionally accommodate the BSR MAC control element}
then { UE cancels the triggered BSR report and transmits the UL data}
}
(8)
with (UE in E-UTRA RRC_CONNECTED state)
ETSI
ensure that {
when { a Regular BSR has been triggered and UE has pending data on several logical channels for
transmission and UE has UL resources to send all pending data including BSR }
then { UE transmits the UL data and reports buffer status reporting (BSR) that indicates there
is no more data in the buffer}
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1, 5.4.5,
6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323 clause 4.5.
[TS 36.321 clause 5.4.3.1]
decreasing order:
[TS 36.321 clause 5.4.4]
[TS 36.321 clause 5.4.5]
The Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data
available for transmission in the UL buffers of the UE. RRC controls BSR reporting by configuring the two timers
periodicBSR-Timer and retxBSR-Timer and by, for each logical channel, optionally signalling logicalChannelGroup
which allocates the logical channel to an LCG [8].
For the Buffer Status reporting procedure, the UE shall consider all radio bearers which are not suspended and may
consider radio bearers which are suspended.
A Buffer Status Report (BSR) shall be triggered if any of the following events occur:
- UL data, for a logical channel which belongs to a LCG, becomes available for transmission in the RLC entity or
in the PDCP entity (the definition of what data shall be considered as available for transmission is specified in
[3] and [4] respectively) and either the data belongs to a logical channel with higher priority than the priorities of
the logical channels which belong to any LCG and for which data is already available for transmission, or there
is no data available for transmission for any of the logical channels which belong to a LCG, in which case the
BSR is referred below to as "Regular BSR";
- UL resources are allocated and number of padding bits is equal to or larger than the size of the Buffer Status
Report MAC control element plus its subheader, in which case the BSR is referred below to as "Padding BSR";
- retxBSR-Timer expires and the UE has data available for transmission for any of the logical channels which
belong to a LCG, in which case the BSR is referred below to as "Regular BSR";
- periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".
For Regular and Periodic BSR:
- if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long
BSR;
- else report Short BSR.
For Padding BSR:
ETSI
- if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller
than the size of the Long BSR plus its subheader:
- if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report
Truncated BSR of the LCG with the highest priority logical channel with data available for transmission;
- else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader, report
Long BSR.
If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:
- if the UE has UL resources allocated for new transmission for this TTI:
- instruct the Multiplexing and Assembly procedure to generate a BSR MAC control element;
- start or restart periodicBSR-Timer except when the BSR is a Truncated BSR;
- start or restart retxBSR-Timer.
- else if a Regular BSR has been triggered:
- a Scheduling Request shall be triggered.
A MAC PDU shall contain at most one MAC BSR control element, even when multiple events trigger a BSR by the
time a BSR can be transmitted in which case the Regular BSR and the Periodic BSR shall have precedence over the
padding BSR.
The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on UL-SCH.
All triggered BSRs shall be cancelled in case the UL grant can accommodate all pending data available for transmission
but is not sufficient to additionally accommodate the BSR MAC control element plus its subheader. All triggered BSRs
shall be cancelled when a BSR is included in a MAC PDU for transmission.
[TS 36.321 clause 6.1.2]
MAC control elements are always placed before any MAC SDU.
[TS 36.321 clause 6.1.3.1]
Buffer Status Report (BSR) MAC control elements consist of either:
- Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure
6.1.3.1-1); or
- Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2).
The BSR formats are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1.-1.
The fields LCG ID and Buffer Size are defined as follow:
- LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is
being reported. The length of the field is 2 bits;
- Buffer Size: The Buffer Size field identifies the total amount of data available across all logical channels of a
logical channel group after the MAC PDU has been built. The amount of data is indicated in number of bytes. It
shall include all data that is available for transmission in the RLC layer and in the PDCP layer; the definition of
what data shall be considered as available for transmission is specified in [3] and [4] respectively. The size of
the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 6 bits.
The values taken by the Buffer Size field are shown in Table 6.1.3.1-1.
Figure 6.1.3.1-1: Short BSR and Truncated BSR MAC control element
ETSI
Figure 6.1.3.1-2: Long BSR MAC control element
Table 6.1.3.1-1: Buffer size levels for BSR
Index Buffer Size (BS) value [bytes] Index Buffer Size (BS) value [bytes]
0 BS = 0 32 1132 < BS <= 1326
1 0 < BS <= 10 33 1326 < BS <= 1552
2 10 < BS <= 12 34 1552 < BS <= 1817
3 12 < BS <= 14 35 1817 < BS <= 2127
4 14 < BS <= 17 36 2127 < BS <= 2490
5 17 < BS <= 19 37 2490 < BS <= 2915
6 19 < BS <= 22 38 2915 < BS <= 3413
7 22 < BS <= 26 39 3413 < BS <= 3995
8 26 < BS <= 31 40 3995 < BS <= 4677
9 31 < BS <= 36 41 4677 < BS <= 5476
10 36 < BS <= 42 42 5476 < BS <= 6411
11 42 < BS <= 49 43 6411 < BS <= 7505
12 49 < BS <= 57 44 7505 < BS <= 8787
13 57 < BS <= 67 45 8787 < BS <= 10287
14 67 < BS <= 78 46 10287 < BS <= 12043
15 78 < BS <= 91 47 12043 < BS <= 14099
16 91 < BS <= 107 48 14099 < BS <= 16507
17 107 < BS <= 125 49 16507 < BS <= 19325
18 125 < BS <= 146 50 19325 < BS <= 22624
19 146 < BS <= 171 51 22624 < BS <= 26487
20 171 < BS <= 200 52 26487 < BS <= 31009
21 200 < BS <= 234 53 31009 < BS <= 36304
22 234 < BS <= 274 54 36304 < BS <= 42502
23 274 < BS <= 321 55 42502 < BS <= 49759
24 321 < BS <= 376 56 49759 < BS <= 58255
25 376 < BS <= 440 57 58255 < BS <= 68201
26 440 < BS <= 515 58 68201 < BS <= 79846
27 515 < BS <= 603 59 79846 < BS <= 93479
28 603 < BS <= 706 60 93479 < BS <= 109439
29 706 < BS <= 826 61 109439 < BS <= 128125
30 826 < BS <= 967 62 128125 < BS <= 150000
31 967 < BS <= 1132 63 BS > 150000
[TS 36.321 clause 6.2.1]
ETSI
Index LCID values

00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding
[TS 36.323 clause 4.5]
For the purpose of MAC buffer status reporting, the UE shall consider the following as data available for transmission
in the PDCP layer:
For SDUs for which no PDU has been submitted to lower layers:
- the SDU itself, if the SDU has not yet been processed by PDCP, or
- the PDU (control or data) if the SDU has been processed by PDCP.
System Simulator :
- Cell 1
7.1.4.6.3.3-1
UE:
None.
Preamble:
- 3 AM DRBS are configured with the following parameters:
Table 7.1.4.6.3.1-1: Logical Channel Configuration Settings
Parameter Value DRB1 Value DRB2 Value DRB3

LogicalChannel-Identity 3 4 5
Priority 8 7 6
prioritizedBitRate 0 kB/s 0 kB/s 0 kB/s
logicalChannelGroup 2 (LCG ID#2) 2 (LCG ID#2) 1 (LCG ID#1)
ETSI

U-S Message
2 The SS transmits a MAC PDU containing two <-- MAC PDU (2 RLC SDUs on LC 3) - -
RLC SDUs of size 10 bytes on LC 3
3 SS allocates an UL Grant of 32 bits. (Note 1) <-- (UL Grant, 32 bits) - -
4 Check: Does the UE transmit a Short BSR with --> MAC PDU (MAC Short BSR (LCG 2,5 P
‘LCG ID’ field set to ‘2’ and ‘Buffer size’ field ID=‘2’, Buffer Size=’6’ or bigger))
set to value ‘6’ or bigger? (Note 2)
5 Wait for retxBSR-Timer expiry on UE side. - - - -
request?
7 The SS respond to the scheduling request in <-- (UL Grant, 32 bits) - -
step 6 by an UL Grant of 32 bits. (Note 1)
‘LCG ID’ field set to ‘2’ and ‘Buffer size’ field ID=‘2’, Buffer Size=’6’ or bigger))
9 The SS transmits a MAC PDU containing one <-- MAC PDU (1 RLC SDUs on LC 4) - -
request?
step 10 by an UL Grant of 32 bits. (Note 1)
‘LCG ID’ field set to ‘2’ and ‘Buffer size#1’ field ID=‘2’, Buffer Size=’8’ or bigger))
13 The SS transmits a MAC PDU containing two <-- MAC PDU (2 RLC SDUs on LC 5) - -
request?
step 14 by one UL Grant of 32 bits. (Note 1)
16 Check: Does the UE transmit a Long BSR with --> MAC PDU (MAC Long BSR 1,5 P
‘Buffer size#1’ field set to value ‘1’, ‘Buffer (Buffer size#1=’1’ or bigger, Buffer
size#2’ field set to value ‘8’ or bigger? (Note 3) size#2=’8’ or bigger)
17 Wait for retxBSR-Timer expiry on the UE side. - - -
request?
19 SS allocates an UL Grant of 424 bits. (Note 4) <-- (UL Grant, 424 bits) - -
20 Check: Does the UE transmit a MAC PDU --> MAC PDU (SDU subheader, AMD 7 P
including five RLC SDUs and not including any PDU header and 2 RLC SDUs on
BSR? (Note 5) LC 3, SDU subheader, AMD PDU
header and 1 RLC SDUs on LC 4,
SDU subheader, AMD PDU
header and 2 RLC SDUs on LC
5)
21 The SS transmits a MAC PDU containing two <-- MAC PDU (MAC sub-header - -
MAC SDUs, the first containing a 8 byte RLC (E=’1’, LCID=’00011’, F=’0’,
SDU with LCID set to ‘00011’ and the second L=’10’), MAC sub-header (E=’0’,
containing a 7 byte RLC SDU with LCID set to LCID=’00101’,), AMD PDU, AMD
‘00101’. PDU)
22 The UE sends Scheduling Request --> (SR) - -
23 The SS transmits an uplink grant of size 256 <-- (UL grant) - -
bits. (Note 6)
24 Check: Does the UE return a MAC PDU of --> MAC PDU (Short BSR MAC sub- 8 P
length 256 bits including 2 RLC SDUs, header (E=’1’, LCID=’11101’,
Padding and Short BSR or LongBSR with MAC sub-header (E=’1’, F=’0’),
Buffer size(s) set to ‘0’? (Note 5) (Note 7) MAC sub-header (E=’1’, F=’0’),
F=’0’), padding MAC sub-header
(E=’0’, LCID=’11111’), Short BSR
( Buffer Size=’0’), AMD PDU,
AMD PDU, padding)
ETSI
Or
MAC PDU (Long BSR MAC sub-
header (E=’1’, LCID=’11101’,
MAC sub-header (E=’1’, F=’0’),
(E=’0’, LCID=’11111’), LongBSR (
Buffer Size=’0’), AMD PDU, AMD
PDU, padding)
25 SS transmits an RLC STATUS PDU to <--RLC STATUS PDU (ACK_SN=1)
acknowledge correctly received
data(LCID=’00011’)
26 SS transmits an RLC STATUS PDU to <-- RLC STATUS PDU (ACK_SN=1)
Note 1: 32 bits enables UE to transmit a MAC PDU with a MAC BSR header and a Short BSR (1 bytes) or a Long
BSR (3 byte).
Note 2: UE triggers a Short BSR of type "Regular BSR" to report buffer status for one LCG for that TTI. The UE
should not send any of the received RLC SDUs (segmented) due to Regular BSR has higher priority than
U-plane logical channels.
Note 3: UE triggers and transmit a Long BSR of type "Regular BSR". The UL grant would be enough for UE to
transmit one RLC SDU as received in step 8, but Regular BSR has higher priority than U-plane logical
channels.
Note 4: The UE has 38 bytes of user data (received in steps 2, 9 and 13) in the transmission buffer. 424 bits
enables UE to transmit user data in MAC PDU with 2 bytes SDU subheader for LC 3, 2 bytes SDU
subheader for LC 4 and 1 byte SDU subheader for LC 5, 24 bytes MAC SDU for LC 3 (2 RLC SDUs, 10
bytes each and 4 bytes AMD PDU header), 12 bytes MAC SDU for LC 4 (1 RLC SDU, 10 bytes and 2
bytes AMD PDU header, 12 bytes MAC SDU for LC 5 (2 RLC SDUs, 4 bytes each and 4 bytes AMD PDU
header)) equals to 424 bits (53 bytes).
Note 5 The MAC SDUs for the different logical channels may be in any order in the MAC PDU.
Note 6: UL grant of 256 bits (ITBS=6, NPRB=3, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit two
MAC SDUs of size 10 and 9 bytes in a MAC PDU (8 bytes RLC SDU + 2 bytes AMD PDU header + 7
bytes RLC SDU+ 2 bytes AMD PDU header) + 1 byte Short BSR+6 byte padding + one byte BSR header+
2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) = 32bytes = 256
bits) or UL grant of 256 bits (ITBS=6, NPRB=3, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to
transmit two MAC SDUs of size 10 and 9 bytes in a MAC PDU (8 bytes RLC SDU + 2 bytes AMD PDU
header + 7 bytes RLC SDU+ 2 bytes AMD PDU header) + 3 byte LongBSR + 4 byte padding + one byte
BSR header+ 2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) =
32bytes = 256 bits).
Note 7: It is left up to UE implementation whether ShortBSR or LongBSR is reported.
ETSI

c1 CHOICE{
Explicit SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx n5
periodicBSR-Timer Infinity
retxBSR-Timer sf320
ttiBundling FALSE
}
}
}
}
}
}
}
}
7.1.4.7 Correct handling of MAC control information / Buffer Status / UL resources

are allocated / Padding BSR
(1)
ensure that {
when { UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size
of a Short BSR plus its subheader but smaller than the size of a Long BSR plus its subheader and the
UE has available data for transmission from more than one LCG in the TTI where the BSR is
transmitted }
then { UE reports a Truncated BSR of the LCG with the highest priority logical channel with data
available for transmission }
}
(2)
ensure that {
when { UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size
of a Short BSR plus its subheader but smaller than the size of a Long BSR plus its subheader and the
UE has available data for transmission form only one LCG in the TTI where the BSR is transmitted }
then { UE reports a Short BSR }
}
(3)
ensure that {
when{ UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size of
a Long BSR plus its subheader }
then { UE reports a long BSR }
}
6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323, clause 4.5.
ETSI
[TS 36.321 clause 5.4.3.1]
decreasing order:
[TS 36.321 clause 5.4.5]
...
...
For padding BSR:
- if the number of padding bits is equal to or larger than the size of the Short BSR plus its sub header but smaller
- else if the number of padding bits is equal to or larger than the size of the Long BSR plus its sub header, report
Long BSR.
- start or restart the periodicBSR-Timer except when the BSR is a Truncated BSR;
padding BSR.
ETSI
[TS 36.321 clause 6.1.2]
[TS 36.321 clause 6.1.3.1]
6.1.3.1-1); or
The BSR formats are identified by MAC PDU sub headers with LCIDs as specified in table 6.2.1.-2.
[TS 36.321 clause 6.2.1]
Index LCID values

00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding
[TS 36.323 clause 4.5]
ETSI
For the purpose of MAC buffer status reporting, the UE shall consider PDCP Control PDUs, as well as the following as
data available for transmission in the PDCP layer:
System Simulator:
- Cell 1
7.1.4.7.3.3-1
UE:
None.
Preamble:
- 2 AM DRBS are configured with the parameters specified in table 7.1.4.7.1-1.
Table 7.1.4.7.1-1: Logical Channel Configuration Settings
Parameter DRB1 DRB2

LogicalChannel-Identity 3 4
Priority 7 6
prioritizedBitRate 0kbs 0kbs
logicalChannelGroup 2 (LCG ID#2) 1 (LCG ID#1)
ETSI

U-S Message
- EXCEPTION: Step 2 shall be repeated for 2 - - - -
times
2 The SS transmits a MAC PDU including an <-- MAC PDU (RLC SDU on LC 4) -
RLC SDU of size 12 bytes on logical channel
4.
3 The SS transmits a MAC PDU including an <-- MAC PDU (RLC SDU on LC 3) - -
3.
4 UE transmits a Scheduling Request on --> (SR) - -
PUCCH.
5 The SS sends an uplink grant of size 32 bits. <-- (UL grant) - -
(Note 1)
6 The UE transmit a Long BSR report --> MAC PDU (Long BSR header - -
(LCID=’11110’), Long BSR)
7 The SS is configured for Uplink Grant <-- (UL grant) - -
Allocation Type 3. The SS sends an uplink
grant of size 136 bits. (Note 2)
8 Check: Does UE transmit a MAC PDU --> MAC PDU (Truncated BSR 1 P
containing an RLC SDU and a Truncated BSR header (LCID=’11100’), Truncated
indicating pending data (‘Buffer size’ field > ‘0’) BSR(LCG ID =’01’, Buffer
for logicalChannelGroup 1 (‘LCG ID’ field set to size>’0’), RLC SDU)
‘01’)?
9 Void - - - -
grant of size 136 bits
(Note 2)
11 Check: Does UE transmit a MAC PDU --> MAC PDU (Short BSR 2 P
containing an RLC SDU and with a Short BSR header(LCID=’11101’), Short
indicating pending data (‘Buffer size’ field > ‘0’) BSR(LCG ID =’10’,Buffer size>’0’),
for logicalChannelGroup 2 (‘LCG ID’ field RLC SDU)
=’10’)?
12 Void - - - -
13 Void - - - -
15 Check: Does UE transmit a MAC PDU --> MAC PDU (Long BSR header 3 P
containing a RLC SDU and a Long BSR? (LCID=’11110’), Long BSR), RLC
SDU)
Note 1: SS transmit an UL grant of 32 bits (ITBS=0, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a
Regular BSR triggered by the new data received logicalChannelGroup 1 and 2 in steps 2 and 3. This to
enable testing of Padding BSR which has lower priority than Regular BSR.
Note 2: UL grant of 136 bits (ITBS=9, NPRB=1, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU
padding bits will be equal to or larger than the size of Short/Truncated BSR and smaller than Long BSR.
RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for
MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of
Short BSR/Truncated BSR is one byte, i.e. setting UL grant to 17 bytes (136 bits) enable UE to include
Short/Truncated BSR.
padding bits will be equal to or larger than the size of Long BSR. RLC SDU size is 12 bytes, size of AMD
PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID
for last sub header and 1 byte for BSR sub-header) and size of Long BSR is 3 bytes, i.e. setting UL grant
to 19 bytes (152 bits) enable UE to include padding Long BSR.
None
ETSI
7.1.4.7a Correct handling of MAC control information / Buffer Status / UL resources

are allocated / Cancellation of Padding BSR
(1)
ensure that {
when { UE has transmitted a MAC PDU with a Regular BSR and padding such that a padding BSR is
triggered AND UE has remaining data causing continuous data transmission while periodicBSR-Timer is
running without causing any Regular BSR or padding BSR to be triggered }
then { UE reports a Periodic BSR }
}
6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323, clause 4.5.
[TS 36.321 clause 5.4.3.1]
decreasing order:
[TS 36.321 clause 5.4.5]
BSR;
ETSI
For padding BSR:
- if the number of padding bits is equal to or larger than the size of the Short BSR plus its sub header but smaller
- else if the number of padding bits is equal to or larger than the size of the Long BSR plus its sub header, report
Long BSR.
padding BSR.
[TS 36.321 clause 6.1.2]
[TS 36.321 clause 6.1.3.1]
6.1.3.1-1); or
ETSI
[TS 36.321 clause 6.2.1]
Index LCID values

00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding
[TS 36.323 clause 4.5]
data available for transmission in the PDCP layer:
System Simulator:
- Cell 1
- RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Tables
7.1.4.7a.3.3-1-3.
UE:
None.
Preamble:
- 3 AM DRBS are configured with the parameters specified in table 7.1.4.7a.1-1.
ETSI
Table 7.1.4.7a.1-1: Logical Channel Configuration Settings
Parameter Value DRB1 Value DRB2 Value DRB3

LogicalChannel-Identity 3 4 5
Priority 8 7 6
prioritizedBitRate 0 kB/s 0 kB/s 0 kB/s
logicalChannelGroup 2 (LCG ID#2) 1 (LCG ID#1) 1 (LCG ID#1)
ETSI

U-S Message
2 The SS transmits a MAC PDU including an <-- MAC PDU (RLC SDU on LC 5) -
5.
- EXCEPTION: Step 3 shall be repeated 4 times - - - -
4.
- EXCEPTION: Step 4 shall be repeated 5 times - - - -
3.
5 Void - - - -
6 60 ms after step 4, t he SS sends an uplink <-- (UL grant) - -
7 The UE transmits a longBSR triggered by a --> MAC PDU (Long BSR header - -
Regular BSR report (LCID=’11110’), MAC SDU
header, Long BSR, RLC SDU,
padding)
8 20 ms after step 4, the SS sends an uplink - - - -
th
grant of 104 bits for every 5 uplink TTI 10
times. (Note 2)
- EXCEPTION: In parallel with step 9, the - - - -
parallel behaviour in table 7.1.4.7a.3.2-2 is
running until the periodic BSR is received in
step 9.
9 Check: Does UE transmit a MAC PDU --> MAC PDU (Long BSR header, 1 P
containing a periodic BSR? ,MAC SDU header, Long BSR
(Note 3 and Note 4) RLC SDU segment)
- EXCEPTION: In parallel with step 10, the - - - -
parallel behaviour in table 7.1.4.7a.3.2-3 is
running. Step 10 shall occur at least once.
(Note 4)
10 CHECK: Does UE transmit a MAC PDU --> MAC PDU (RLC SDU segments) 1 P
containing a MAC SDU
padding bits (padding header + padding payload) will be equal to or larger to trigger a padding BSR (Short
BSR), i.e. 2 bytes or more (one byte for BSR sub-header and 1 bytes for a Short BSR). RLC SDU size is
11 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 4 bytes (1 byte for BSR sub header, 2
byte for MAC SDU sub-header using R/R/E/LCID/F/L and 1 byte for R/R/E padding sub header) and size of
Long BSR (Regular BSR) is 3 bytes and padding is 2 bytes, i.e. setting UL grant to 22 bytes (176 bits). The
remaining 3 bytes would have enabled the UE to segment a second RLC SDU if the RLC SDU belongs to
the same logical channel. However, as there is only one RLC SDU available for transmission for LC5
(highest priority) then would the UE have to add a second MAC SDU to transmit a segment of an additional
RLC SDU from LC4. This would require 4 bytes or more and the UE will instead add 3 bytes of padding,
which will trigger a padding BSR.
Note 2: UL grant of 104 bits (ITBS=3, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE is able to
transmit a MAC PDU that fits exactly a PDCP SDU to enable periodic BSR to be triggered when
periodicBSR-Timer expires. RLC SDU size is 10 bytes, size of AMD PDU header is 2 bytes and size of
MAC header is 1 byte (1 byte for MAC SDU sub-header using R/R/E/LCID for last sub header), i.e. setting
th
UL grant to 13 bytes (104 bits). The UL grant is sent by the SS 10 times (every 5 TTI) to enable UE to
transmit the remaining 9 RLC SDUs and at least one periodic BSR,
Note 3: The Periodic BSR is triggered by the expiry of the periodiBSR-Timer (32 sub-frames, see Table
7.1.4.7a.3.3-1) and verifies that the triggered padding BSR in step 7 in Table 7.1.4.7a.3.2-1 is cancelled by
the UE. If the UE would not have cancelled the triggered padding BSR then would the UE reset the
periodicBSR-Timer after each transmission causing the timer to not expire.
Note 4: If UE has cancelled the triggered padding BSR in step 7 in Table 7.1.4.7a.3.2-1 then the periodicBSR-
Timer will expire before all data in the transmission buffer has been sent by the UE. This verifies that the
received BSR report in step 9 is triggered by a periodic BSR report and not due to a regular or padding
BSR.
ETSI
Table 7.1.4.7a.3.2-2: Parallel behaviour

U-S Message
1 UE transmits a MAC PDU containing an RLC --> MAC PDU (RLC SDU) - -
SDU

U-S Message
1 UE transmits a MAC PDU containing an RLC --> MAC PDU (Long BSR header, - -
SDU ,MAC SDU header, Long BSR
RLC SDU segment)
or
MAC PDU (Short BSR header,
,MAC SDU header, Short BSR
RLC SDU segment)
7.1.4.7a.3.3 Specific Message Contents

c1 CHOICE{
Explicit SEQUENCE {
maxHARQ-Tx n5
periodicBSR-Timer Sf32 32 subframes
retxBSR-Timer sf320
ttiBundling FALSE
}
}
}
}
}
}
}
}
ETSI
Table 7.1.4.7a.3.3-2: SchedulingRequest-Configuration (preamble: Table 4.5.3.3-1, step 8)

setup SEQUENCE {
}
}
Table 7.1.4.7a.3.3-3: RLC-Config-DRB-AM (preamble: Table 4.5.3.3-1, step 8)

am SEQUENCE {
}
}
}
7.1.4.8 Correct handling of MAC control information / Buffer status / Periodic BSR
timer expires
(1)
ensure that {
when { periodicBSR-Timer expires and more than one LCG has buffered data in a TTI }
then { UE triggers a Periodic BSR and reports Long BSR }
}
(2)
ensure that {
when { periodicBSR-Timer expires and one LCG has buffered data in a TTI }
then { UE triggers a Periodic BSR and reports Short BSR and restarts the periodicBSR-Timer}
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.5, 6.1.2,
6.1.3.1 and 6.2.1; TS 36.323 clause 4.5.
[TS 36.321 clause 5.4.5]
...
ETSI
BSR;
...
padding BSR.
[TS 36.321 clause 6.1.2]
[TS 36.321 clause 6.1.3.1]
6.1.3.1-1); or
ETSI
[TS 36.321 clause 6.2.1]
Table: 6.2.1-2 Values of LCID for UL-SCH
Index LCID values

00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding
[TS 36.323 clause 4.5]
data available for transmission :
- the PDU if the SDU has been processed by PDCP.
System Simulator:
- Cell 1
7.1.4.8.3.3-1
UE:
None.
Preamble;
ETSI
Parameter DRB1 DRB2

priority 7 6
logicalChannelGroup 2 1
ETSI

U–S Message
2 The SS transmits a MAC PDU containing an <-- MAC PDU (RLC PDU)
RLC PDU on logical channel 4 (LCG ID 1),
which contains 1 RLC SDU of size 14 bytes.
4 The UE transmits a short BSR report. (Note 6) --> MAC PDU ((LCID=’11101’, LCG - -
ID='01', Buffer size index > 0)
- EXCEPTION: Steps 5 to 6 shall be repeated - - - -
two times (Note 4)
5 Wait for periodicBSR-Timer expiry. - - - -
5A The SS sends an uplink grant of size 32 bits - - - -
6 Check: Does UE transmit a MAC PDU --> MAC PDU (LCID=’11101’, LCG 2 P
containing a Short BSR with ‘LCG ID’ field set ID=’01’, Buffer Size index > 0)
to ‘01’ (logicalChannelGroup 1) and Buffer
Size Index > 0?
7 Void
8 The SS transmits a MAC PDU containing an <-- MAC PDU (RLC PDU) - -
RLC PDU on logical channel 3 (LCG ID 2),
which contains 1 RLC SDU of size 14 bytes.
8A The SS sends an uplink grant of size 32 bits <-- (UL grant) - -
(Note 3)
8B The UE transmits a long BSR report with --> MAC PDU (( ‘Buffer size#1 index’ - -
‘Buffer size#1’ (LCG ID=1) and ‘Buffer size#2’ > 0, ‘Buffer size#2 index=’ >0’)
(LCG ID=2) fields set to value > ‘0’
9 Void
- EXCEPTION: Step 9A to 10 shall be repeated - - - -
twice. (Note 5)
10 Check: Does UE transmit a MAC PDU --> MAC PDU 1 P
containing a Long BSR with ‘Buffer size#1’
(LCG ID=1) and ‘Buffer size#2’ (LCG ID=2)
fields set to value > ‘0’?
10 The SS is configured for Uplink Grant - -
A Allocation Type 3. The SS transmits 1 UL grant
of size 328 bits to enable the UE to loopback
RLC SDU on LCG ID = 1 and LCG = 2. (Note
7)
11 The UE transmits MAC PDU containing the --> MAC PDU - -
remaining RLC SDUs as sent by the SS in
steps 2 and 8.
Note 1: Void
Note 2: SS transmits an UL grant of 32 bits (ITBS=0, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a
Regular BSR triggered by the new data received logicalChannelGroup 1 in step 2.
Note 3: SS transmits an UL grant of 32 bits (ITBS=0, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a
Regular BSR triggered by the new data received logicalChannelGroup 2 in step 8.
Note 4: One short BSR due to first expiry of periodicBSR-Timer and one short BSR due to second expire of
periodicBSR-Timer.
Note 5: One long BSR due to expire of periodicBSR-Timer and one long BSR due to second expiry of
periodicBSR-Timer.
Note 6: The UE starts periodicBSR-Timer.
Note 7: SS transmits an UL grant of 328 bits (ITBS=7, NPRB=3, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit
RLC SDU on LCG =1 (14 bytes) and LCG = 2 (14 bytes) and a minimum MAC header of 3 bytes.
ETSI

c1 CHOICE{
explicit SEQUENCE {
maxHARQ-Tx n5
periodicBSR-Timer sf10
retxBSR-Timer sf10240
ttiBundling FALSE
}
}
}
}
}
}
}
}
7.1.4.9 Void
7.1.4.10 MAC padding
(1)
ensure that {
when { UE is to transmit a MAC PDU with padding exceeding 2 bytes }
then { Padding goes to the end of the MAC PDU }
}
(2)
ensure that {
when { UE is to transmit a MAC PDU with single-byte padding and there is a data MAC PDU sub-header
present }
then { UE is inserting padding MAC PDU subheader before any other MAC PDU sub-header }
}
(3)
ensure that {
when { UE is to transmit a MAC PDU with two-byte padding and there is a data MAC PDU sub-header }
then { UE is inserting two padding MAC PDU subheaders before any other MAC PDU sub-header or one
padding MAC PDU subheader as a last MAC PDU subheader }
}
(4)
ensure that {
when { UE is to transmit a MAC PDU with single-byte padding and there is no data MAC PDU sub-
header but a MAC Control element is present }
then { UE is inserting a padding MAC PDU subheader before any other MAC PDU sub-header }
}
ETSI
(5)
ensure that {
when { UE is to transmit a MAC PDU with two-byte padding and there is no data MAC PDU sub-header
but a MAC Control element is present}
then { UE is inserting two padding MAC PDU subheaders before any other MAC PDU sub-header or one
padding MAC PDU subheader as a last MAC PDU subheader and one byte padding at the end of the MAC PDU
}
}
References: The conformance requirements covered in the current TC are specified in TS 36.321, clause 6.1.2.
[TS 36.321 clause 6.1.2]
R/R/E/LCID
sub-header
R/R/E/LCID[/F/L]
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
... R/R/E/LCID/F/L
sub-header
R/R/E/LCID padding
sub-header
MAC payload
and padding
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
2 The SS transmits a MAC PDU with 10 bytes <-- MAC PDU(AMD PDU) - -
MAC SDU.
3 The UE transmits a Scheduling Request on - (SR) - -
PUCCH.
bits. (Note 1)
5 Check: Does the UE transmit a MAC PDU with --> MAC PDU (BSR sub-header, MAC 1 P
a MAC SDU of length 10 bytes and where the SDU sub-header, Padding MAC
last MAC sub-header has the Extension field sub-header (E=’0’,
‘E’ set to ‘0’ and the Logical Channel ID field LCID=’11111’),Short BSR, MAC
‘LCID’ set to ‘11111’? SDU, padding)
6 The SS transmits a MAC PDU with 13 bytes <-- MAC PDU(AMD PDU) - -
MAC SDU.
PUCCH.
bits. (Note 2)
9 Check: Does the UE transmit a MAC PDU with --> MAC PDU (Padding MAC-sub- 2 P
a MAC SDU of length 13 bytes and with a header (E=’1’, LCID=’11111’),
padding MAC sub-header, with Extension field MAC SDU sub-header, MAC
‘E’ is set to ‘1’ and the Logical Channel ID field SDU)
‘LCID’ is set to ‘11111’, inserted before the
MAC SDU sub-header?
10 The SS transmits a MAC PDU with 10 bytes <-- MAC PDU (AMD PDU) - -
MAC SDU.
PUCCH.
bits. (Note 3)
two padding MAC sub-headers, with Extension header#1 (E=’1’, LCID=’11111’),
field ‘E’ is set to ‘1’ and the Logical Channel ID Padding MAC-sub-header#2
field ‘LCID’ is set to ‘11111’, inserted before (E=’1’, LCID=’11111’), BSR sub-
the BSR sub-header and the MAC SDU sub- header, MAC SDU sub-header,
header Or a MAC PDU with BSR sub-header Short BSR, MAC-SDU)
with Extension field ‘E’ is set to ‘1’ and MAC Or
SDU sub-header (R/R/E/LCID/F/L) inserted MAC PDU(BSR sub-header, MAC
before the Padding MAC sub-header? SDU sub-header, Padding MAC-
sub-header(E=’0’, LCID=’11111’),
Short BSR, MAC-SDU)
14 The SS transmits a Timing Advance command <-- MAC PDU - -
and does not send any subsequent timing (Timing Advance Command)
alignments. Start Timer_T1 = Time Alignment
timer value on SS.
15 40 to 50 TTI before Timer_T1 expires the SS <-- MAC PDU (AMD PDU) - -
transmits a MAC PDU containing an RLC AMD
PDU.
16 The SS ignores scheduling requests and waits --> (PRACH preamble) - -
until the UE transmits a preamble on PRACH.
17 The SS transmits a Random Access <-- Random Access Response - -
Response, with an UL Grant of 56-bits. (Note
4)
18 Check: Does the UE transmit a MAC PDU with --> MAC PDU (BSR sub-header, MAC - -
a BSR sub-header (8-bits), a Control sub- Control sub-header, Padding MAC
header (8-bits) , a short BSR (8-bits) and a C- sub-header (E=’0’, LCID=’11111’),
RNTI MAC Control Element (16-bits) ? (Note Short BSR, C-RNTI control
6) element, padding)
Or
MAC PDU (
Padding MAC-sub-header#1
ETSI
(E=’1’, LCID=’11111’),
Padding MAC-sub-header#2
(E=’1’, LCID=’11111’),
BSR sub-header,
MAC Control sub-header,
Short BSR,
C-RNTI control element)
19 The SS transmits an UL grant of 24 bits. <-- (UL grant) - -

(Note 5)
A a padding MAC sub header with Extension header (E=’1’, LCID=’11111’),
field ‘E’ is set to ‘1’ and ‘LCID’ field set to BSR sub-header, Short BSR)
‘11111’ (8-bits) inserted before a BSR sub-
header (8bits) and a short BSR (8 bits)?
20 The SS transmits an uplink grant enabling UE <-- (UL grant) - -
to transmit loop back PDU.
21 The UE transmits Loop back PDU. --> MAC PDU(AMD PDU) - -
Note 1: UL grant of 176 bits (ITBS=3, NPRB=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU
padding will be larger than 2 bytes. RLC SDU size is 8 bytes, size of AMD PDU header is 2 bytes, size of
MAC header is 4 bytes (2 bytes for MAC SDU sub-header using 7-bit LI, 1 byte for BSR sub-header and 1
byte for padding MAC sub-header) and size of Short BSR is 1 byte, equals to 120 bits (15 bytes) and
resulting into 56 bits padding.
padding will be a single byte. RLC SDU size is 11 bytes, size of AMD PDU header is 2 bytes and size of
MAC header is 1 byte for MAC SDU sub-header, equals to 112 bits (14 bytes) and resulting into 1 single
byte padding.
padding will be equal to 2 bytes. RLC SDU size is 8 bytes, size of AMD PDU header is 2 bytes, size of
MAC header is 4 bytes (1 bytes for MAC SDU sub-header, 1 byte for Short BSR sub-header and 2 bytes
for padding MAC sub-header) and size of Short BSR is 1 byte, equals to 120 bits (15 bytes) and resulting
no padding at the end of the MAC PDU.
Note 4: UL grant of 56 bits (ITBS=0, NPRB=3, see TS 36.213 Table 7.1.7.2.1-1) is as 36.321 clause 5.1.4 states that
the eNB should not provide a grant smaller than 56 bits in the Random Access Response.
padding will be equal to a single byte.
Note 6: The order of short BSR and C-RNTI control element is not restricted, i.e. the short BSR can be placed
before the C-RNTI control element and vice versa. The same applies for the related sub-headers.
None.
7.1.4.11 Correct HARQ process handling

(1)
ensure that {
when { UE receives an UL Grant with toggled NDI and has data available for transmission }
then { UE transmits a new MAC PDU using redundancy version 0 }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less
than maxHARQ-Tx times }
ensure that {
when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the
HARQ process }
then { UE performs non-adaptive retransmission of the MAC PDU with redundancy version toggled by
one of the last (re)transmission [0,2,3,1 order] }
}
ETSI
(3)
ensure that {
when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process
with old NDI [not toggled], irrespective of ACK/NACK is received for previous (re)transmission }
then { UE performs an adaptive retransmission of the MAC PDU with redundancy version as received
on PDCCH }
}
(4)
ensure that {
when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the
HARQ process }
then { UE does not retransmit the MAC PDU }
}
(5)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU
maxHARQ-Tx times }
ensure that {
with not toggled NDI }
then { UE does not retransmit the MAC PDU but transmit a MAC Padding PDU}
}
(6)
ensure that {
with toggled NDI, and data are not available for transmission }
then { UE transmits any MAC Padding PDU }
}
(7)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU
maxHARQ-Tx times }
ensure that {
HARQ process }
then { UE does not transmit any MAC PDU }
}
5.4.2.2.
[TS 36.321, clause 5.4.2.1]
There is one HARQ entity at the UE, which maintains a number of parallel HARQ processes allowing transmissions to
take place continuously while waiting for the feedback on the successful or unsuccessful reception of previous
transmissions.
The number of parallel HARQ processes is specified in [2], clause 8.
At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process for which a
transmission should take place. It also routes the received feedback (ACK/NACK information), MCS and resource,
relayed by the physical layer, to the appropriate HARQ process.
If TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle. TTI
bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of
ETSI
the same bundle. Within a bundle HARQ retransmissions are non-adaptive and triggered without waiting for feedback
from previous transmissions according to TTI_BUNDLE_SIZE. The feedback for a bundle is only received for the last
TTI of the bundle (i.e. the TTI corresponding to TTI_BUNDLE_SIZE ), regardless of whether a transmission in that
TTI takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is also a TTI bundle.
For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply. For each TTI, the
HARQ entity shall:
- identify the HARQ process associated with this TTI;
- if an uplink grant has been indicated for this TTI:
- if the received grant was not addressed to a Temporary C-RNTI on PDCCH and if the NDI provided in the
associated HARQ information has been toggled compared to the value in the previous transmission of this
HARQ process; or
- if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is
empty; or- if the uplink grant was received in a Random Access Response:
- if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access
Response:
- obtain the MAC PDU to transmit from the Msg3 buffer.
- else:
- obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;
- deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;
- instruct the identified HARQ process to trigger a new transmission.
- else:
- deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;
- instruct the identified HARQ process to generate an adaptive retransmission.
- else, if the HARQ buffer of the HARQ process corresponding to this TTI is not empty:
- instruct the identified HARQ process to generate a non-adaptive retransmission.
When determining if NDI has been toggled compared to the value in the previous transmission UE shall ignore NDI
received in all uplink grants on PDCCH for its Temporary C-RNTI.
[TS 36.321, clause 5.4.2.2]
Each HARQ process is associated with a HARQ buffer.
Each HARQ process shall maintain a state variable CURRENT_TX_NB, which indicates the number of transmissions
that have taken place for the MAC PDU currently in the buffer, and a state variable HARQ_FEEDBACK, which
indicates the HARQ feedback for the MAC PDU currently in the buffer. When the HARQ process is established,
CURRENT_TX_NB shall be initialized to 0.
The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of
redundancy versions. This variable is up-dated modulo 4.
New transmissions are performed on the resource and with the MCS indicated on PDCCH or Random Access
Response. Adaptive retransmissions are performed on the resource and, if provided, with the MCS indicated on
PDCCH. Non-adaptive retransmission is performed on the same resource and with the same MCS as was used for the
last made transmission attempt,
The UE is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ
transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes
and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of
transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, maximum
number of transmissions shall be set to maxHARQ-Msg3Tx.
ETSI
When the HARQ feedback is received for this TB, the HARQ process shall:
- set HARQ_FEEDBACK to the received value.
If the HARQ entity requests a new transmission, the HARQ process shall:
- set CURRENT_TX_NB to 0;
- set CURRENT_IRV to 0;
- store the MAC PDU in the associated HARQ buffer;
- store the uplink grant received from the HARQ entity;
- set HARQ_FEEDBACK to NACK;
- generate a transmission as described below.
If the HARQ entity requests a retransmission, the HARQ process shall:
- increment CURRENT_TX_NB by 1;
- if the HARQ entity requests an adaptive retransmission:
- set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ
information;
- else if the HARQ entity requests a non-adaptive retransmission:
- if HARQ_FEEDBACK = NACK:
NOTE: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.
NOTE: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ
feedback can be received and a non-adaptive retransmission follows.
To generate a transmission, the HARQ process shall:
- if there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission
does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer:
- instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy
version corresponding to the CURRENT_IRV value;
- increment CURRENT_IRV by 1;
- if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the
MAC PDU was not obtained from the Msg3 buffer:
- set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.
After performing above actions, the HARQ process then shall:
- if CURRENT_TX_NB = maximum number of transmissions - 1:
- flush the HARQ buffer.
ETSI
System Simulator:
- Cell 1
- System information takes into account the parameters in table 7.1.2.11.3.1-1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] using parameters as specified in Table
7.1.4.11.3.3-1 and 7.1.4.11.3.3-2.
- The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.
- No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.
ETSI

U-S Message
containing RLC PDU
2 Void - - - -
3 The SS is configured for Uplink Grant <-- Uplink Grant - -
Allocation Type 3. The SS allocates an UL
Grant for one HARQ process X, sufficient for
one RLC SDU to be loop backed in a TTI, and
NDI indicates new transmission
including one RLC SDU, in HARQ process X,
redundancy version 0?
(Note 1)
5 The SS transmits a NACK <-- HARQ NACK - -
6 Check: Does the UE retransmit the MAC PDU --> MAC PDU 2 P
for HARQ process X, redundancy version 2?
(Note 1)
(Note 1)
(Note 1)
(Note 1)
13 Void - - - -
14 Void - - - -
15 The SS transmits an ACK <-- HARQ ACK - -
16 Check: Does the UE retransmit the MAC PDU --> MAC PDU 4 F
for HARQ process X?
17 The SS transmits an UL grant corresponding <-- Uplink Grant - -
to TTI for HARQ process X, with NDI not
toggled and redundancy version to be used as
‘1’
in for HARQ process X, using redundancy
version 1?
(Note 1)
to next TTI for HARQ process X, with NDI not
toggled and redundancy version to be used as
‘3’
for HARQ process X, using next redundancy
version 3?
(Note 1)
in the next TTIs corresponding to HARQ
process X?
to TTI for HARQ process X, with NDI not
toggled
EXCEPTION: In parallel with step 25, UE - - - -
executes parallel behaviour defined in table
7.1.4.11.3.2-2
ETSI

process X?
25 The SS transmits an RLC STATUS PDU to the <-- RLC STATUS PDU (ACK_SN=1) - -
A UE

RLC PDU
27 Void - - - -
Allocation Type 3. The SS allocates UL Grant
for one HARQ process Y, sufficient for one
including one RLC SDU, in HARQ process Y,
redundancy version 0?
(Note 1)
Allocation Type 3. The SS allocates UL Grant
for one HARQ process Y, sufficient for one
7.1.4.11.3.2-2.
process Y?
32 The SS transmits an RLC STATUS PDU to the <-- RLC STATUS PDU (ACK_SN=2) - -
UE
Note 1: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by
receiving the UL MAC PDU correctly at SS.

U-S Message
1 The UE transmits a MAC Padding PDU --> MAC PDU - -
Table 7.1.4.11.3.3-1: MAC-MainConfig {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1,

step 8)}

maxHARQ-Tx n8
}
}
ETSI
Table 7.1.4.11.3.3-2: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-

1, step 8)}

am SEQUENCE {
}
}
}
7.1.4.12 MAC reset / UL

(1)
with(UE in E-UTRA RRC_CONNECTED state, with Scheduling Request procedure triggered)
ensure that {
then { UE cancels Scheduling Request procedure }
}
(2)
ensure that {
then { UE flushes UL HARQ buffer }
}
(3)
with (UE in E-UTRA RRC_CONNECTED state )
ensure that {
then { UE Considers the next transmission for each UL HARQ process as very first }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.9.
[TS 36.321 clause 5.9]
If a reset of the MAC entity is requested by upper layers, the UE shall:
- initialize Bj for each logical channel to zero;
- stop (if running) all timers;
- consider timeAlignmentTimer as expired and perform the corresponding actions in subclause 5.2;
- stop, if any, ongoing RACH procedure;
- flush Msg3 buffer;
- cancel, if any, triggered Scheduling Request procedure;
- cancel, if any, triggered Buffer Status Reporting procedure;
- cancel, if any, triggered Power Headroom Reporting procedure;
- flush the soft buffers for all DL HARQ processes;
ETSI
- for each DL HARQ process, consider the next received transmission for a TB as the very first transmission;
- release, if any, Temporary C-RNTI.
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) in Cell 1 according to [18].
is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this
clause.

T0 Cell-specific RS EPRE dBm/15Khz -85 Off
ETSI

U-S Message
2 The SS transmits a MAC PDU containing one <-- MAC PDU (1 RLC SDU of 40 - -
RLC SDU on LC 4 bytes on DRB)
3 The UE transmit a scheduling request --> (SR) - -
4 Wait for 50ms [Discard timer] to expire at UE. - - - -
5 The SS changes power level according to the - - - -
row "T1" in table 7.1.4.12.3.2-1
handover to Cell 2.
7 The UE transmits on cell 2, --> - - -
8 Check: For 2 seconds, if UE transmits a --> (SR) 1 F
scheduling request?
SDU on LC 4 bytes on DRB)
11 The SS allocate UL Grant sufficient for one <-- Uplink Grant - -
12 The UE transmit a MAC PDU including one --> MAC PDU - -
RLC SDU
13 The SS changes power level according to the - - - -
A row "T2" in table 7.1.4.12.3.2-1
handover to Cell 1
15 The UE transmits on cell 1, --> - - -
16 Check: For 2 seconds, does UE transmit MAC --> MAC PDU (1 RLC SDU of 40 2 F
PDU containing Loop Back PDU? bytes on DRB)
SDU on LC 4 bytes on DRB)
19 The SS allocate UL Grant sufficient for one <-- Uplink Grant - -
20 Check: Does UE transmit a MAC PDU --> MAC PDU 3 P
including one RLC SDU?
Table 7.1.4.12.3.3-1: MAC-MainConfiguration {RRCConnectionReconfiguration (preamble)}

MAC-MainConfiguration-RBC ::= SEQUENCE {
maxHARQ-Tx n28
}
}
ETSI
Table 7.1.4.12.3.3-2: PDCP-Configuration-DRB-UM {RRCConnectionReconfiguration (preamble)}
Derivation Path: 36.508 clause 4.8.2.1.2.1-1

PDCP-Configuration-DRB-UM ::= SEQUENCE {
discardTimer ms50 Lowest value
}
Table 7.1.4.12.3.3-3: SchedulingRequest-Configuration {RRCConnectionReconfiguration (preamble)}

SchedulingRequest-Configuration::= CHOICE {
enable SEQUENCE {
}
}

c1 CHOICE{
n-HO
4.4.4.2)
}
}
}
}
}

c1 CHOICE{
n-HO
4.4.4.2)
}
}
}
}
}
ETSI
7.1.4.13 MAC PDU header handling

(1)
ensure that {
when { UE has a MAC SDU to be transmitted that is less smaller 128 bytes }
then { UE sets F field to 0 }
}
(2)
ensure that {
when { UE has a MAC SDU to be transmitted that is larger than 128 bytes }
then { UE sets F field to 1 }
}
(3)
ensure that {
when { UE inserts a R/R/E/LCID field in the MAC header and there is a subsequent R/R/E/LCID field
to be inserted }
then { UE sets E field to 1 }
}
(4)
ensure that {
when { UE inserts a R/R/E/LCID field in the MAC header and a MAC SDU or a MAC control element
starts at the next byte }
then { UE sets E field to 0 }
}
(5)
ensure that {
when { UE inserts the last MAC sub-header in the MAC PDU }
then { UE inserts a MAC sub-header consist solely of the four header fields R/R/E/LCID }
}
(6)
ensure that {
when { UE inserts padding at the end of a MAC PDU }
then { UE inserts the last MAC sub-header as a padding MAC subheader consisting solely of the
four header fields R/R/E/LCID with LCID set to Padding }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 6.1.2
and 6.2.1.
[TS 36.321, clause 6.1.2]
A MAC PDU header consists of one or more MAC PDU sub-headers; each sub header corresponding to either a MAC
ETSI
A MAC PDU sub header consists of the six header fields R/R/E/LCID/F/L but for the last sub header in the MAC PDU
and for fixed sized MAC control elements. The last sub header in the MAC PDU and sub-headers for fixed sized MAC
Figure 6.1.2-1: R/R/E/LCID/F/L MAC sub header
Figure 6.1.2-2: R/R/E/LCID MAC sub header
R/R/E/LCID
sub-header
R/R/E/LCID[/F/L]
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
... R/R/E/LCID/F/L
sub-header
R/R/E/LCID padding
sub-header
MAC payload
and padding
[TS 36.321, clause 6.2.1]
ETSI
included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU,
when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC
PDU. The LCID field size is 5 bits;
- L: The Length field indicates the length of the corresponding MAC SDU or MAC control element in bytes.
There is one L field per MAC PDU sub header except for the last sub header and sub-headers corresponding to
fixed-sized MAC control elements. The size of the L field is indicated by the F field;
- F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per
MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control
elements. The size of the F field is 1 bit. If the size of the MAC SDU or MAC control element is less than 128
bytes, the UE shall set the value of the F field to 0, otherwise the UE shall set it to 1;
- E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set
to "1" to indicate another set of at least R/R/E/LCID fields. The E field is set to "0" to indicate that either a MAC
SDU, a MAC control element or padding starts at the next byte;
- R: Reserved bits, set to "0".
The MAC header and sub-headers are octet aligned.
...
Index LCID values

00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding
…
Table 6.2.1-3: Values of F field:
Index Size of Length field (in bits)

0 7
1 15
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI
- 2 AM DRBs are configured with the parameters specified in table 7.1.4.13.3.1-1.
Table 7.1.4.13.3.1-1: Logical Channel Configuration Settings
Parameter DRB1 DRB2

Priority 7 6
logicalChannelGroup 2 1
ETSI

U-S Message
2 The SS transmits a MAC PDU containing a <-- MAC PDU (MAC sub-header ( - -
MAC SDU of size 127 bytes (RLC SDU of size LCID=’00011’), AMD PDU)
125 bytes + AMD PDU header 2 bytes
) with the Logical Channel ID field ‘LCID’ set to
‘00011’, and 1 Byte Padding in the associated
MAC SDU sub-header.
bits. (Note 1)
5 Check: does the UE transmit a MAC PDU with --> MAC PDU (MAC sub-header ( 1 P
a MAC SDU sub-header with Logical Channel LCID=’00011’, F=’0’, L=’127’
ID field ‘LCID’ set to ‘00011’, Format field ‘F’ bytes), AMD PDU)
set to ‘0’ and Length field ‘L’ set to ‘127’? (Note
6)
5a The SS transmits an RLC STATUS PDU to <-- RLC STATUS PDU (ACK_SN=1) - -
acknowledge correctly received data
6 The SS transmits a MAC PDU containing a <-- MAC PDU (MAC sub-header - -
MAC SDU of size 128 bytes (RLC SDU of 126 (LCID=’00011’), AMD PDU)
bytes + AMD PDU header 2 bytes) with the
Logical Channel ID field ‘LCID’ set to ‘00011’.
7 The UE send Scheduling Request --> (SR) - -
bits. (Note 2)
9 Check: Does the UE transmit a MAC PDU --> MAC PDU (MAC sub-header 2 P
with a MAC SDU sub-header with Format field (LCID=’00011’, F=’1’, L=128),
‘F’ set to ‘1’ and Logical Channel ID field ‘LCID’ AMD PDU)
set to ‘00011’? (Note 6)
10 The SS transmits an RLC STATUS PDU to <-- RLC STATUS PDU (ACK_SN=2) - -
acknowledge correctly received data
containing s 6 byte RLC SDU with LCID set to LCID=’00100’), AMD PDU, AMD
‘00100’. PDU)
bits. (Note 3)
14 Check: Does the UE return a MAC PDU of --> MAC PDU (MAC sub-header 3,4, P
length 176 bits containing two MAC sub- (E=’1’, (LCID=’00011’, L=’11) or 5
headers where the first MAC sub-header have (LCID=’00100’,L=’8), MAC sub-
the Expansion bit ‘E’ set to ‘1’ and the second header (E=’0’, no Length field
MAC sub-header has the Expansion bit ‘E’ set present), AMD PDU, AMD PDU)
to ‘0’ and no length field? (Note 5)
15 SS transmits an RLC STATUS PDU to <-- RLC STATUS PDU (ACK_SN=3) - -
containing a 7 byte RLC SDU with LCID set to LCID=’00100’,), AMD PDU, AMD
‘00100’. PDU)
bits. (Note 4)
20 Check: Does the UE return a MAC PDU of --> MAC PDU (Long BSR MAC sub- 3,4, P
length 256 bits containing four MAC sub- header (E=’1’, LCID=’11110’, 6
ETSI
headers where the first three MAC sub-header MAC sub-header (E=’1’, F=’0’),
have the Expansion bit ‘E’ set to ‘1’ and the MAC sub-header (E=’1’, F=’0’),
last MAC sub-header has the Expansion bit ‘E’ F=’0’), padding MAC sub-header
set to ‘0’ and the LCID field set to ‘11111’? (E=’0’, LCID=’11111’), Long BSR,
(Note 5) (Note 7) AMD PDU, AMD PDU, padding)
Or
MAC PDU (Short BSR MAC sub-
header (E=’1’, LCID=’11101’,
(E=’0’, LCID=’11111’), Short BSR,
AMD PDU, AMD PDU, padding)
Note 1: UL grant of 1096 bits (ITBS=8, NPRB=8, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit a
MAC SDU of size 127 bytes in a MAC PDU (125 bytes RLC SDU size + 2 bytes AMD PDU header + 2
bytes MAC header (7 bit LI) = 129 bytes = 1032 bits < 1096 bits.
Note 2: UL grant of 1096 bits (ITBS=8, NPRB=8, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit a
MAC SDU of size 128 bytes in a MAC PDU (126 bytes RLC SDU size + 2 bytes AMD PDU header + 3
bytes MAC header (15 bit LI) = 131 bytes = 1048 bits < 1096 bits.
MAC SDUs, one of size 11 and one of size 8 bytes, in a MAC PDU (9 bytes RLC SDU + 2 bytes AMD PDU
header + 6 bytes RLC SDU +2 bytes AMD PDU header + 2 bytes MAC sub-header (7 bit LI) + one byte
MAC sub-header (R/R/E/LCID) = 22 bytes = 176 bits)
MAC SDUs of size 10 and 9 bytes in a MAC PDU ( (8 bytes RLC SDU + 2 bytes AMD PDU header + 7
bytes RLC SDU+ 2 bytes AMD PDU header) + 3 byte Long BSR+4 byte padding + one byte BSR header+
2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) = 32bytes = 256
bits) or (8 bytes RLC SDU + 2 bytes AMD PDU header + 7 bytes RLC SDU+ 2 bytes AMD PDU header) +
1 byte Short BSR+6 byte padding + one byte BSR header+ 2 x 2 bytes MAC sub-header (7 bit LI) + one
byte padding MAC sub-header (R/R/E/LCID) = 32bytes = 256 bits))
Note 5: MAC SDU for LCID 3 and 4 can come in any order
Note 6: At this step UE shall include a BSR and report it on any of the configured Logical Channel Groups: 0
(SRB2), 1 (DRB2) and 2 (DRB1),
Note 7: It is left up to UE implementation whether ShortBSR or LongBSR is reported.
None.
7.1.4.14 Correct HARQ process handling / TTI bundling

(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and TTI bundling configured }
ensure that {
when { UE receives an UL Grant with toggled NDI and has data available for transmission }
then { UE transmits a new MAC PDU and non-adaptive retransmissions for 3 additional consecutive
UL subframes }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having
transmitted a MAC PDU less than maxHARQ-Tx times }
ensure that {
bundled HARQ process }
then { UE performs non-adaptive retransmissions of the MAC PDU for 4 consecutive UL subframes }
}
ETSI
(3)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having
transmitted a MAC PDU less than maxHARQ-Tx times }
ensure that {
with old NDI, irrespective of ACK/NACK is received for previous (re)transmission }
on PDCCH in first UL subframe and non-adaptive retransmissions in 3 additional consecutive UL
subframes }
}
(4)
ensure that {
when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the
HARQ process }
then { UE does not retransmit the TTI Bundle }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1,
5.4.2.2 & 7.5, TS 36.213 clause 8, 8.3, 8.6.1 & 9.1.2.
[TS 36.321, clause 5.4.2.1]
There is one HARQ entity at the UE, which maintains a number of parallel HARQ processes allowing transmissions to
take place continuously while waiting for HARQ the feedback on the successful or unsuccessful reception of previous
transmissions.
The number of parallel HARQ processes is specified in [2], clause 8.
At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process for which a
transmission should take place. It also routes the received HARQ feedback (ACK/NACK information), MCS and
resource, relayed by the physical layer, to the appropriate HARQ process.
When TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle.
TTI bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is
part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and triggered without waiting for
feedback from previous transmissions according to TTI_BUNDLE_SIZE. The HARQ feedback of a bundle is only
received for the last TTI of the bundle (i.e. the TTI corresponding to TTI_BUNDLE_SIZE), regardless of whether a
transmission in that TTI takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is
also a TTI bundle.
For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply.
For each TTI, the HARQ entity shall:
- identify the HARQ process associated with this TTI;
- if an uplink grant has been indicated for this TTI:
- if the received grant was not addressed to a Temporary C-RNTI on PDCCH and if the NDI provided in the
associated HARQ information has been toggled compared to the value in the previous transmission of this
HARQ process; or
- if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is
empty; or
- if the uplink grant was received in a Random Access Response:
Response:
ETSI
- else:
- deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;
- else:
- deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ
process;
- else, if the HARQ buffer of the HARQ process corresponding to this TTI is not empty:
[TS 36.321, clause 5.4.2.2]
last made transmission attempt.
transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum
ETSI
information;
NOTE 1: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.
NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ
- if the MAC PDU was obtained from the Msg3 buffer; or
does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer in this TTI:
- if CURRENT_TX_NB = maximum number of transmissions – 1:
- flush the HARQ buffer;
[TS 36.321, clause 7.5]
The parameter TTI_BUNDLE_SIZE is 4.
[TS 36.213, clause 8]
For FDD, there shall be 8 HARQ processes in the uplink for non-subframe bundling operation, i.e. normal HARQ
operation, and 4 HARQ processes in the uplink for subframe bundling operation. The subframe bundling operation is
configured by the parameter ttiBundling provided by higher layers.
In case higher layers configure the use of subframe bundling for FDD and TDD, the subframe bundling operation is
only applied to UL-SCH, such that four consecutive uplink subframes are used.
For FDD and subframe bundling operation, the UE shall upon detection of a PDCCH with DCI format 0 in subframe n
intended for the UE, and/or a PHICH transmission in subframe n-5 intended for the UE, adjust the corresponding first
PUSCH transmission in the bundle in subframe n+4 according to the PDCCH and PHICH information.
For TDD UL/DL configurations 1 and 6 and subframe bundling operation, the UE shall upon detection of a PDCCH
with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in subframe n-l
with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe n+k, with k
given in Table 8-2, according to the PDCCH and PHICH information.
ETSI
Table 8-2: k for TDD configurations 0-6

Configuration 0 1 2 3 4 5 6 7 8 9
0 4 6 4 6
1 6 4 6 4
2 4 4
3 4 4 4
4 4 4
5 4
6 7 7 7 7 5
Table 8-2a: l for TDD configurations 0, 1 and 6

Configuration 0 1 2 3 4 5 6 7 8 9
0 9 6 9 6
1 2 3 2 3
6 5 5 6 6 8
[TS 36.213, clause 8.3]
For Frame Structure type 1, an ACK/NACK received on the PHICH assigned to a UE in subframe i is associated with
the PUSCH transmission in subframe i-4.
For Frame Structure type 2 UL/DL configuration 1-6, an ACK/NACK received on the PHICH assigned to a UE in
subframe i is associated with the PUSCH transmission in the subframe i-k as indicated by the following table 8.3-1.
…
Table 8.3-1 k for TDD configurations 0-6
TDD UL/DL DL subframe number i

Configuration 0 1 2 3 4 5 6 7 8 9
0 7 4 7 4
1 4 6 4 6
2 6 6
3 6 6 6
4 6 6
5 6
6 6 4 7 4 6
[TS 36.213, clause 8.6.1]
For 0 ≤ I MCS ≤ 28 , the modulation order ( Q m ) is determined as follows:
− If the parameter ttiBundling provided by higher layers is set to TRUE, then the resource allocation size is
restricted to N PRB ≤ 3 and the modulation order is set to Q m = 2 .
[TS 36.213, clause 9.1.2]
For scheduled PUSCH transmissions in subframe n, a UE shall determine the corresponding PHICH resource in
subframe n+ kPHICH, where kPHICH is always 4 for FDD and is given in table 9.1.2-1 for TDD. For subframe bundling
operation, the corresponding PHICH resource is associated with the last subframe in the bundle.
Table 9.1.2-1: kPHICH for TDD
TDD UL/DL UL subframe index n
ETSI
Configuration 0 1 2 3 4 5 6 7 8 9
0 4 7 6 4 7 6
1 4 6 4 6
2 6 6
3 6 6 6
4 6 6
5 6
6 4 6 6 4 7
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
0A SS Transmits RRCConnectionReconfiguration <-- - - -
to configure TTI bundling
containing RLC PDU of size 312 bits on UM
Bearer.
2 The UE transmits a Scheduling Request --> Scheduling Request - -
3 The SS allocates an UL Grant of 328 bits with <-- Uplink Grant - -
NDI indicating new transmission (i.e. Nprb=3
and Imcs=7)(Note 1)
including one RLC SDU, with redundancy
version 0, ‘k’ subframes after step 3?
(Note 3)
5 Check: Does UE repeat non-adaptive --> MAC PDU 1 P
retransmission of MAC PDU in step 4, for 3
consecutive UL subframes with redundancy
version 2, 3 and 1 respectively?
(Note 3)
6 The SS transmits a NACK, ‘kk’ subframes after <-- HARQ NACK - -
last transmission in step 5.
7 Check: Does the UE make non-adaptive --> MAC PDU 2 P
retransmissions of the MAC PDU ‘m’
subframes after NACK in step 6, for 4
consecutive UL subframes with redundancy
version 0, 2, 3 and 1 respectively?
(Note 3)
8 The SS transmits an ACK, ‘kk’ subframes after <-- HARQ ACK - -
9 The SS allocates an UL Grant with NDI <-- Uplink Grant - -
indicating retransmission, start redundancy
version =2[i.e. Nprb=3 and Imcs=30], ‘l’
subframes after ACK in step 8.
10 Check: Does the UE perform an adaptive --> MAC PDU 3 P
retransmission of the MAC PDU ‘k’ subframes
after grant in step 9, using redundancy version
2?
(Note 3)
11 Check: Does UE repeat non-adaptive --> MAC PDU 3 P
retransmission of MAC PDU in step 10, for 3
consecutive UL sub-frames with redundancy
version 3, 1 and 0 respectively?
(Note 3)
12 The SS transmits an ACK, ‘kk’ subframes after <-- HARQ ACK - -
13 Check: Does the UE make any --> MAC PDU 4 F
retransmissions of the MAC PDU ‘m’
subframes after ACK in step 12, for 4
consecutive UL subframes?
Note 1: In step3, for TDD, the subframe number of allocating UL grant should be selected from {‘1’, ‘4’, ‘6’, ‘9’}
based on TDD default UL/DL configuration 1.
Note 2: For FDD value of ‘k’, ‘kk’ is 4, ‘l’ is 5 and ‘m’ is 9.
For TDD UL/DL configuration 1, values of ‘k’, ‘l’, ‘m’ and ‘kk’ are given in table 7.1.4.14.3.2-2.
ETSI
Table 7.1.4.14.3.2-2: Values for parameter ‘k’, ‘l’, ‘m’ and ‘kk’ in Main behaviour.
Parameter DL sub-frame number n

0 1 2 3 4 5 6 7 8 9
k 6 4 6 4
l 3 2 3 2
m 7 8 7 8
kk 4 6 4 6
Table 7.1.4.14.3.3-1: MAC-MainConfig-RBC in RRCConnectionReconfiguration(Step 0A)

MAC-MainConfigRBC- ::= SEQUENCE {
maxHARQ-Tx n28 Max value allowed
periodicBSR-Timer Infinity
ttiBundling TRUE
}
}
7.1.4.15 UE power headroom reporting / Periodic reporting

(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic power headroom reporting
configured }
ensure that {
when { periodicPHR-Timer is configured in RRCConnectionReconfiguration procedure }
then { UE transmits a MAC PDU containing Power Headroom MAC Control Element }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic power headroom reporting
configured }
ensure that {
when { periodicPHR-Timer expires and UL resources allocated for new transmission }
}
(3)
ensure that {
when { power headroom reporting is disabled }
then { UE stops transmitting Power Headroom MAC Control Element }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and
6.1.3.6, 36.331.
[TS 36.321, clause 5.4.6]
The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference
between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. The reporting
period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of 3GPP TS 36.133 [9]. RRC controls
Power Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by
signalling dl-PathlossChange which sets the change in measured downlink pathloss to trigger a PHR [8].
ETSI
A Power Headroom Report (PHR) shall be triggered if any of the following events occur:
- the prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB
since the transmission of a PHR when UE has UL resources for new transmission;
- periodicPHR-Timer expires;
- upon configuration and reconfiguration of the power headroom reporting functionality by upper layers [8], which
is not used to disable the function.
If the UE has UL resources allocated for new transmission for this TTI:
- if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer.
- if the Power Headroom reporting procedure determines that at least one PHR has been triggered since the last
transmission of a PHR r this is the first time that a PHR is triggered, and;
- if the allocated UL resources can accommodate a PHR MAC control element plus its subheader as a result of
logical channel prioritization:
- obtain the value of the power headroom from the physical layer;
- instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element
based on the value reported by the physical layer;
- start or restart periodicPHR-Timer;
- start or restart prohibitPHR-Timer;
- cancel all triggered PHR(s).
[TS 36.321, clause 6.1.3.6]
The Power Headroom MAC control element is identified by a MAC PDU sub header with LCID as specified in table
6.2.1-2. It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.6-1):
- R: reserved bit, set to "0";
- Power Headroom(PH): this field indicates the power headroom level. The length of the field is 6 bits. The
reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 below (the
corresponding measured values in dB can be found in subclause 9.1.8.4 of [19])
Figure 6.1.3.6-1: Power Headroom MAC control element
Table 6.1.3.6-1: Power Headroom levels for PHR
PH Power Headroom Level

0 POWER_HEADROOM_0
1 POWER_HEADROOM_1
2 POWER_HEADROOM_2
3 POWER_HEADROOM_3
… …
60 POWER_HEADROOM_60
ETSI
System Simulator:
- Cell 1
UE:
None.
Preamble:

U-S Message
1 The SS is configured for Uplink Grant - --> - -
Allocation Type 2. The SS transmits UL grant
for the UE at every TTI for FDD and every 5ms
in a DL subframe for TDD.
provide Power Headroom parameters
containing Power Headroom MAC Control
Element?
message to confirm the setup of Power
Headroom parameters.
Element 200ms after step 3?
disable Power Headroom reporting
message to confirm the disabling of Power
Headroom parameters
8 Check: for 2 seconds, does the UE transmit a --> MAC PDU 3 F
MAC PDU containing Power Headroom MAC
Control Element?
Note: Steps 3 and 4 can happen in 2 MAC PDU’s, or may be combined in one MAC PDU.
ETSI

c1 CHOICE{
explicitValue SEQUENCE {
phr-Confign CHOICE {
setup SEQUENCE {
periodicPHR-Timer sf200
prohibitPHR-Timer sf1000
dl-PathlossChange infinity
}
}
}
}
}
}
}
}
}

c1 CHOICE{
phr-Config CHOICE {
release NULL
}
}
}
}
}
}
}
}
7.1.4.16 UE power headroom reporting / DL pathloss change reporting

(1)
with { UE in E-UTRA RRC_Connected state with DRB established, Power headroom reporting for dl-
PathlossChange configured }
ensure that {
when { the DL Pathloss has changed more than dl-PathlossChange dB and prohibitPHR-Timer is running
}
then { UE does not transmit a MAC PDU containing Power Headroom MAC Control Element }
}
ETSI
(2)
with { UE in E-UTRA RRC_Connected state with DRB established, Power headroom reporting for dl-
PathlossChange configured }
ensure that {
when { prohibitPHR-Timer expires and power headroom report is triggered due to DL Pathloss change
}
}
6.1.3.6
[TS 36.321, clause 5.4.6]
between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. The reporting
period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of [9]. RRC controls Power Headroom
reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-
PathlossChange which sets the change in measured downlink pathloss to trigger a PHR [8].
- prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB since
the transmission of a PHR when UE has UL resources for new transmission;
- upon configuration or reconfiguration of the power headroom reporting functionality by upper layers [8], which
is not used to disable the function.
- if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer;
transmission of a PHR or this is the first time that a PHR is triggered, and;
- if the allocated UL resources can accommodate a PHR MAC control element plus its subheader as a result of
logical channel prioritization:
- obtain the value of the power headroom from the physical layer;
based on the value reported by the physical layer;
[TS 36.321, clause 6.1.3.6]
The Power Headroom MAC control element is identified by a MAC PDU sub header 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.6-1):
- Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The
reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6.1-1 below (the
corresponding measured values in dB can be found in subclause 9.1.8.4 of [17]).
ETSI
Figure 6.1.3.6-1: Power Headroom MAC control element
Table 6.1.3.6-1: Power Headroom levels for PHR
PH Power Headroom Level

0 POWER_HEADROOM_0
1 POWER_HEADROOM_1
2 POWER_HEADROOM_2
3 POWER_HEADROOM_3
… …
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS is configured for Uplink Grant - - - -
Allocation Type 2. SS is configured to transmit
UL grant for UE at every TTI for FDD, and
every 5ms in a DL subframe for TDD.
provide Power Headroom parameters
message to confirm the setup of Power
Headroom parameters.
4 Wait for T1= 10% of prohibitPHR-Timer. - - - -
5 Reduce SS power level so as to cause a - - - -
DL_Pathloss change at UE by 5dB.
6 Check: for 80% of prohibitPHR-Timer since --> MAC PDU 1 F
step 3, does the UE transmit a MAC PDU
Element?
7 Check: after prohibitPHR-Timer after step 3, --> MAC PDU 2 P
does the UE transmit a MAC PDU containing
Power Headroom MAC Control Element?
8 Increase SS power level so as to cause a - - - -
DL_Pathloss change at UE by 5dB.
Element?
Power Headroom MAC Control Element?
Note: Steps 3 in main behaviour and step 1 in parallel behaviour can happen in 2 MAC PDU’s, or may be
combined in one MAC PDU.

U-S Message
1 The UE transmits a MAC PDU containing --> MAC PDU - -
Power Headroom MAC Control Element.
ETSI

c1 CHOICE{
phr-Config CHOICE {
setup SEQUENCE {
periodicPHR-Timer infinity
dl-PathlossChange dB3
}
}
}
}
}
}
}
}
}
7.1.4.17
7.1.4.18 Correct handling of MAC control information / Buffer Status / UL data arrive in
the UE Tx buffer / Extended buffer size
(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, and ExtendedBSR-Sizes is configured in
RRCConnectionReconfiguration procedure }
ensure that {
when { UL data arrives in the UE transmission buffer}
then { UE transmits a MAC PDU containing 'Buffer Status Report' MAC control element with
Extended Buffer size }
}
References: The conformance requirements covered in the current TC are specified in: TS36.321, clause 5.4.3 ,5.4.5
and 6.1.3.1.
[36.321, clause 5.4.3.1]
decreasing order:
- MAC control element for PHR or Extended PHR;
ETSI
[36.321, clause 5.4.5]
padding BSR.
The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on any UL-SCH.
All triggered BSRs shall be cancelled in case the UL grant(s) in this subframe can accommodate all pending data
available for transmission but is not sufficient to additionally accommodate the BSR MAC control element plus its
subheader. All triggered BSRs shall be cancelled when a BSR is included in a MAC PDU for transmission.
The UE shall transmit at most one Regular/Periodic BSR in a TTI. If the UE is requested to transmit multiple MAC
PDUs in a TTI, it may include a padding BSR in any of the MAC PDUs which do not contain a Regular/Periodic BSR.
All BSRs transmitted in a TTI always reflect the buffer status after all MAC PDUs have been built for this TTI. Each
LCG shall report at the most one buffer status value per TTI and this value shall be reported in all BSRs reporting
buffer status for this LCG.
NOTE: A Padding BSR is not allowed to cancel a triggered Regular/Periodic BSR. A Padding BSR is triggered
for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built.
[36.321, clause 6.1.3.1]
6.1.3.1-1); or
The BSR formats are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1-2.
logical channel group after all MAC PDUs for the TTI have been built. The amount of data is indicated in
number of bytes. It shall include all data that is available for transmission in the RLC layer and in the PDCP
layer; the definition of what data shall be considered as available for transmission is specified in [3] and [4]
respectively. The size of the RLC and MAC headers are not considered in the buffer size computation. The
length of this field is 6 bits. If extendedBSR-Sizes is not configured, the values taken by the Buffer Size field are
shown in Table 6.1.3.1-1. If extendedBSR-Sizes is configured, the values taken by the Buffer Size field are
shown in Table 6.1.3.1-2.
ETSI
Table 6.1.3.1-2: Extended Buffer size levels for BSR
Index Buffer Size (BS) value [bytes] Index Buffer Size (BS) value [bytes]
0 BS = 0 32 4940 < BS <= 6074
1 0 < BS <= 10 33 6074 < BS <= 7469
2 10 < BS <= 13 34 7469 < BS <= 9185
3 13 < BS <= 16 35 9185 < BS <= 11294
4 16 < BS <= 19 36 11294 < BS <= 13888
5 19 < BS <= 23 37 13888 < BS <= 17077
6 23 < BS <= 29 38 17077 < BS <= 20999
7 29 < BS <= 35 39 20999 < BS <= 25822
8 35 < BS <= 43 40 25822 < BS <= 31752
9 43 < BS <= 53 41 31752 < BS <= 39045
10 53 < BS <= 65 42 39045 < BS <= 48012
11 65 < BS <= 80 43 48012 < BS <= 59039
12 80 < BS <= 98 44 59039 < BS <= 72598
13 98 < BS <= 120 45 72598 < BS <= 89272
14 120 < BS <= 147 46 89272 < BS <= 109774
15 147 < BS <= 181 47 109774 < BS <= 134986
16 181 < BS <= 223 48 134986 < BS <= 165989
17 223 < BS <= 274 49 165989 < BS <= 204111
18 274 < BS <= 337 50 204111 < BS <= 250990
19 337 < BS <= 414 51 250990 < BS <= 308634
20 414 < BS <= 509 52 308634 < BS <= 379519
21 509 < BS <= 625 53 379519 < BS <= 466683
22 625 < BS <= 769 54 466683 < BS <= 573866
23 769 < BS <= 945 55 573866 < BS <= 705666
24 945 < BS <= 1162 56 705666 < BS <= 867737
25 1162 < BS <= 1429 57 867737 < BS <= 1067031
26 1429 < BS <= 1757 58 1067031 < BS <= 1312097
27 1757 < BS <= 2161 59 1312097 < BS <= 1613447
28 2161 < BS <= 2657 60 1613447 < BS <= 1984009
29 2657 < BS <= 3267 61 1984009 < BS <= 2439678
30 3267 < BS <= 4017 62 2439678 < BS <= 3000000
31 4017 < BS <=4940 63 BS > 3000000

System Simulator:
- Cell 1
UE:
None.
Preamble:
- The condition SRB2-DRB (1, 0) is used for step 8 in 4.5.3A.3 according to [18].
ETSI
7.1.4.18.3.2 Definition of system information messages

U-S Message
1 Void - - - -
2 Void - - - -
3 The SS transmits a MAC PDU containing an <-- MAC PDU(RLC SDU) - -
RLC SDU of size 60 bytes.
4 The UE transmit a scheduling request. --> (SR) - -
step 4 by an UL Grant of 32 bits.
6 Check: Does The UE transmit a short BSR --> MAC PDU (MAC Short BSR 1 P
with ‘Buffer size’ field set to ‘10’? (Buffer Size=’10’))
grant of size 520 bits.
8 UE transmits a MAC PDU containing a RLC --> MAC PDU(RLC SDU) - -
SDU.
Table 7.1.4.18.3.3-1: RRCConnectionReconfiguration (Preamble)

c1 CHOICE{
mac-MainConfig-v1020 CHOICE {
extendedBSR-Sizes-r10 Setup
}
}
}
}
}
}
7.1.4.19 CA / UE power headroom reporting / SCell activation and DL pathloss

change reporting / Extended PHR
7.1.4.19.1 CA / UE power headroom reporting / SCell activation and DL pathloss change
reporting / Extended PHR / Intra-band Contiguous CA
(1)
with { UE in E-UTRA RRC_Connected state with DRB established, Extended Power headroom reporting and
an SCell with uplink addition configured }
ensure that {
when { UE receives an Activation MAC Control Element activating the SCell }
then { UE transmits a MAC PDU containing Extended Power Headroom MAC Control Element }
}
(2)
with { UE in E-UTRA RRC_Connected state with DRB established, Extended Power headroom reporting for
DL_Pathloss change configured }
ensure that {
when { the DL Pathloss changes and prohibitPHR-Timer is running }
then { UE does not transmit a MAC PDU containing Extended Power Headroom MAC Control Element }
}
ETSI
(3)
with { UE in E-UTRA RRC_Connected state with DRB established, Extended Power headroom reporting for
DL_Pathloss change configured }
ensure that {
when { prohibitPHR-Timer expires and extended power headroom report is triggered due to DL
Pathloss change }
}
6.1.3.6a
[TS 36.321, clause 5.4.6]
between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated
Serving Cell and also with information about the difference between the nominal UE maximum power and the
estimated power for UL-SCH and PUCCH transmission on PCell.
The reporting period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of [9]. RRC controls Power
Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-
PathlossChange which sets the change in measured downlink pathloss and the required power backoff due to power
management (as allowed by P-MPRc [10]) to trigger a PHR [8].
- prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB for at
least one activated Serving Cell which is used as a pathloss reference since the last transmission of a PHR when
the UE has UL resources for new transmission;
is not used to disable the function;
- activation of an SCell with configured uplink.
- prohibitPHR-Timer expires or has expired, when the UE has UL resources for new transmission, and the
following is true in this TTI for any of the active Serving Cells with configured uplink:
- there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the
required power backoff due to power management (as allowed by P-MPRc [10]) for this cell has changed
more than dl-PathlossChange dB since the last transmission of a PHR when the UE had UL resources
allocated for transmission or PUCCH transmission on this cell.
NOTE: The UE should avoid triggering a PHR when the required power backoff due to power management
decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid reflecting such
temporary decrease in the values of PCMAX,c/PH when a PHR is triggered by other triggering conditions.
- if the allocated UL resources can accommodate a PHR MAC control element plus its subheader if extendedPHR
is not configured, or the Extended PHR MAC control element plus its subheader if extendedPHR is configured,
as a result of logical channel prioritization:
- if extendedPHR is configured:
- for each activated Serving Cell with configured uplink:
ETSI
- obtain the value of the Type 1 power headroom;
- if the UE has UL resources allocated for transmission on this Serving Cell for this TTI:
- obtain the value for the corresponding PCMAX,c field from the physical layer;
- if simultaneousPUCCH-PUSCH is configured:
- obtain the value of the Type 2 power headroom for the PCell;
- if the UE has a PUCCH transmission in this TTI:
- instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC
control element as defined in subclause 6.1.3.6a based on the values reported by the physical layer;
- else:
- obtain the value of the Type 1 power headroom from the physical layer;
as defined in subclause 6.1.3.6 based on the value reported by the physical layer;
[TS 36.321, clause 6.1.3.6a]
The Extended Power Headroom MAC control element is identified by a MAC PDU subheader with LCID as specified
in table 6.2.1-2. It has a variable size and is defined in Figure 6.1.3.6a-2. When Type 2 PH is reported, the octet
containing the Type 2 PH field is included first after the octet indicating the presence of PH per SCell and followed by
an octet containing the associated PCMAX,c field (if reported). Then follows in ascending order based on the
ServCellIndex [8] an octet with the Type 1 PH field and an octet with the associated PCMAX,c field (if reported), for the
PCell and for each SCell indicated in the bitmap.
The Extended Power Headroom MAC Control Element is defined as follows:
- Ci: this field indicates the presence of a PH field for the SCell with SCellIndex i as specified in [8]. The Ci field
set to "1" indicates that a PH field for the SCell with SCellIndex i is reported. The Ci field set to "0" indicates that
a PH field for the SCell with SCellIndex i is not reported;
- V: this field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0
indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2
PH, V=0 indicates real transmission on PUCCH and V=1 indicates that a PUCCH reference format is used.
Furthermore, for both Type 1 and Type 2 PH, V=0 indicates the presence of the associated PCMAX,c field, and
V=1 indicates that the associated PCMAX,c field is omitted;
reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding
measured values in dB can be found in subclause 9.1.8.4 of [9]);
- P: this field indicates whether the UE applies power backoff due to power management (as allowed by P-MPR
[10]). The UE shall set P=1 if the corresponding PCMAX,c field would have had a different value if no power
backoff due to power management had been applied;
~
- PCMAX,c: if present, this field indicates the PCMAX,c or PCMAX ,c [2] used for calculation of the preceding PH field.
The reported PCMAX,c and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.6a-1
(the corresponding measured values in dBm can be found in subclause 9.6.1 of [9]).
Figure 6.1.3.6a-1: Void
ETSI
C7 C6 C5 C4 C3 C2 C1 R
P V PH (Type 2, PCell)
R R PCMAX,c 1
R R PCMAX,c 2
P V PH (Type 1, SCell 1)
R R PCMAX,c 3
...
P V PH (Type 1, SCell n)
R R PCMAX,c m
Figure 6.1.3.6a-2: Extended Power Headroom MAC Control Element
Table 6.1.3.6a-1: Nominal UE transmit power level for Extended PHR
PCMAX,c Nominal UE transmit power level

0 PCMAX_C_00
1 PCMAX_C_01
2 PCMAX_C_02
… …
61 PCMAX_C_61
62 PCMAX_C_62
63 PCMAX_C_63
System Simulator:
- Cell 1 is the PCell, Cell 3 is the SCell to be added
UE:
None.
Preamble:
Table 7.1.4.19.1.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions after preamble. Subsequent configurations marked “T1”, “T2” etc are applied at the points indicated in the
Main behaviour description in Table 7.1.4.19.1.3.2-1. Cell powers are chosen for a serving cell and a non-suitable “Off”
cell as defined in TS36.508 Table 6.2.2.1-1.
ETSI
Table 7.1.4.19.1.3.2-0: Cell configuration changes over time

T0 Cell- dBm/15k -82 -82
specific RS Hz
EPRE
T1 Cell- dBm/15k -89 -82
specific RS Hz
EPRE
T2 Cell- dBm/15k -82 -82
specific RS Hz
EPRE
T3 Cell- dBm/15k -82 -89
specific RS Hz
EPRE
T4 Cell- dBm/15k -82 -82
specific RS Hz
EPRE

U-S Message
2 The UE transmits an --> RRCConnectionReconfigurationC - -
3 The SS is configured for Uplink Grant - - - -
Allocation Type 2. SS is configured to transmit
UL grant for UE at every TTI for FDD, and
every 5ms in a DL subframe for TDD.
provide Extended Power Headroom
parameters
7.1.4.19.1.3.2-2
message to confirm the setup of Extended
Power Headroom parameters
containing Extended Power Headroom MAC
Control Element?
8 Wait for T1= 10% of prohibitPHR-Timer. - - - -
table 7.1.4.19.1.3.2-0.
Control Element?
Extended Power Headroom MAC Control
Element?
table 7.1.4.19.1.3.2-0..
Control Element?
ETSI

Element?
table 7.1.4.19.1.3.2-0.
Control Element?
Element?
table 7.1.4.19.1.3.2-0.
Control Element?
Element?

U-S Message
1 The UE transmits a MAC PDU containing --> MAC PDU - -
Element.
Derivation path: 36.508 table 4.6.1-8 condition SCell_AddMod

c1 CHOICE{
phr-Config CHOICE {
setup SEQUENCE {
periodicPHR-Timer infinity
dl-PathlossChange dB3
}
}
sCellDeactivationTimer-r10 Not Present
extendedBSR-Sizes-r10 Not Present
extendedPHR-r10 setup
}
}
}
}
}
}
}
}
ETSI

reporting / Extended PHR / Inter-band CA

reporting / Extended PHR / Intra-band non-Contiguous CA
7.1.4.20 CA / Correct handling of MAC control information / Buffer status

7.1.4.20.1 CA / Correct handling of MAC control information / Buffer status / Intra-band
Contiguous CA
(1)
with { UE in E-UTRA RRC_CONNECTED state with SCell configured and activated }
ensure that {
when { UL data arrives in the UE transmission buffer and UE is scheduled to transmit on both PCell
and SCell in a TTI }
then { UE transmits two MAC PDUs in a TTI, and one of the MAC PDU includes a Regular BSR,
another MAC PDU includes a padding BSR }
}
(2)
ensure that {
when{ UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size of
a Long BSR plus its subheader }
then { UE reports a long BSR }
}
(3)
with { UE in E-UTRA RRC_CONNECTED state with SCell configured and activated }
ensure that {
when { periodicBSR-Timer expires and UE is scheduled to transmit on both PCell and SCell in a TTI
}
then { UE transmits two MAC PDUs in a TTI, and one of the MAC PDU includes a Periodic BSR,
another MAC PDU includes a padding BSR }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1 and
5.4.5.
[TS 36.321 clause 5.4.3.1]
decreasing order:
ETSI
- MAC control element for PHR or Extended PHR;
NOTE: When the UE is requested to transmit multiple MAC PDUs in one TTI, steps 1 to 3 and the associated
rules may be applied either to each grant independently or to the sum of the capacities of the grants. Also
the order in which the grants are processed is left up to UE implementation. It is up to the UE
implementation to decide in which MAC PDU a MAC control element is included when UE is requested
to transmit multiple MAC PDUs in one TTI.
[TS 36.321 clause 5.4.5]
BSR;
For Padding BSR:
- if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller
- else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader, report
Long BSR.
- instruct the Multiplexing and Assembly procedure to generate the BSR MAC control element(s);
ETSI
- start or restart periodicBSR-Timer except when all the generated BSRs are Truncated BSRs;
- if an uplink grant is not configured or the Regular BSR was not triggered due to data becoming available for
transmission for a logical channel for which logical channel SR masking (logicalChannelSR-Mask) is setup
by upper layers:
padding BSR.
The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on any UL-SCH.
All triggered BSRs shall be cancelled in case the UL grant(s) in this subframe can accommodate all pending data
available for transmission but is not sufficient to additionally accommodate the BSR MAC control element plus its
subheader. All triggered BSRs shall be cancelled when a BSR is included in a MAC PDU for transmission.
The UE shall transmit at most one Regular/Periodic BSR in a TTI. If the UE is requested to transmit multiple MAC
PDUs in a TTI, it may include a padding BSR in any of the MAC PDUs which do not contain a Regular/Periodic BSR.
All BSRs transmitted in a TTI always reflect the buffer status after all MAC PDUs have been built for this TTI. Each
LCG shall report at the most one buffer status value per TTI and this value shall be reported in all BSRs reporting
buffer status for this LCG.
NOTE: A Padding BSR is not allowed to cancel a triggered Regular/Periodic BSR. A Padding BSR is triggered
for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built.
System Simulator :
- Cell 1(PCell), Cell 3 (SCell)
7.1.4.20.1.3.3-1
UE:
None.
Preamble:
Parameter DRB1 DRB2

Priority 7 6
logicalChannelGroup 2 (LCG ID#2) 1 (LCG ID#1)
ETSI

U-S Message
- EXCEPTION: Steps 4 and 5 shall be repeated - - - -
for 2 times
4 The SS transmits a MAC PDU including an <-- MAC PDU (RLC SDU on LC3) -
PUCCH.
7 The SS sends two uplink grants with same <-- (UL grant) - -
size of 136 bits for Cell 1 and Cell 3 in the
same TTI (Note2)
8 Check: Does the UE transmit a MAC PDU --> MAC PDU (Short BSR header 1 P
containing an RLC SDU and a short BSR and (LCID=’11101’), MAC sub-header
another MAC PDU containing an RLC SDU (E=’0’, F=’0’), Short BSR, AMD
and a padding BSR in a TTI? PDU),
MAC PDU (Short BSR header
(LCID=’11101’),MAC sub-
header(E=’0’, F=’0’),, Short BSR,
AMD PDU)
8a The SS transmits a MAC PDU containing RLC <-- MAC PDU - -
PDUs in step 8
size of 152 bits for both Cell 1 and Cell 3 in the
same TTI (Note 3)
10 Check: Does the UE transmit two MAC PDUs, --> MAC PDU (Long BSR header 2 P
the second one containing an RLC SDU and a (LCID=’11110’), MAC sub-header,
long padding BSR in a TTI? Long BSR, RLC SDU) ( the
scheduling procedures is applied
to the sum of the capacities of the
grants)
Or MAC PDU (MAC sub-header,
AMD PDU, RLC SDU) (the
to each grant independently)
MAC PDU (Long BSR header
(LCID=’11110’), Long BSR, RLC
SDU)
PDUs in step 10
- EXCEPTION: Steps 11 and 12 shall be - - - -
repeated for 2 times
PUCCH.
grant of size 32 bits.(Note 1)
15 The UE transmits a long BSR report with --> MAC PDU (( ‘Buffer size#1 index’ - -
‘Buffer size#1’ (LCG ID=1) and ‘Buffer size#2’ > 0, ‘Buffer size#2 index=’ >0’)
ETSI
(LCG ID=2) fields set to value > ‘0’

16 Wait for periodicBSR-Timer expiry. - - - -
size of 136 bits for Cell 1 and Cell 3 in the
same TTI (Note2)
18 Check: Does UE transmit a MAC PDU --> MAC PDU (Short BSR header 3 P
containing a Short BSR with ‘LCG ID’ field set (LCID=’11101’),’, Short BSR,
to ‘10’ (logicalChannelGroup 1) and Buffer (LCG ID= ’10’, Buffer Size index >
Size Index > 0 and another MAC PDU 0), AMD PDU)
containing an RLC SDU and a padding BSR in
a TTI? MAC PDU (Short BSR,
(LCID=’11101’),MAC sub-header,
Short BSR,AMD PDU)
PDUs in step 18
size of 152 bits for both Cell 1 and Cell 3 in the
same TTI (Note 3)
20 Check: Does the UE transmit two MAC PDUs, --> MAC PDU (Long BSR header 2 P
the second one containing an RLC SDU and a (LCID=’11110’), Long BSR, RLC
long padding BSR in a TTI?? SDU) ( the scheduling procedures
is applied to the sum of the
capacities of the grants)
Or MAC PDU (MAC sub-header,
AMD PDU, RLC SDU) (the
to each grant independently)
MAC PDU (Long BSR header

(LCID=’11110’), Long BSR, RLC
SDU)
21 The SS transmits a MAC PDU containing RLC <-- MAC PDU - -
PDUs in step 21
Note 1: SS transmit an UL grant of 32 bits (ITBS=0, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a
Regular BSR triggered by the new data received logicalChannelGroup 1 and 2 in steps 2 and 3. This to
enable testing of Padding BSR which has lower priority than Regular BSR.
padding bits will be equal to or larger than the size of Short/Truncated BSR and smaller than Long BSR.
RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for
MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of
Short BSR/Truncated BSR is one byte, i.e. setting UL grant to 17 bytes (136 bits) enable UE to include
Short/Truncated BSR.
padding bits will be equal to or larger than the size of Long BSR. RLC SDU size is 12 bytes, size of AMD
PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID
for last sub header and 1 byte for BSR sub-header) and size of Long BSR is 3 bytes, i.e. setting UL grant
to 19 bytes (152 bits) enable UE to include padding Long BSR.
ETSI
Table 7.1.4.20.1.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

c1 CHOICE{
explicit SEQUENCE {
maxHARQ-Tx n5
ttiBundling FALSE
}
}
}
}
}
}
}
}
7.1.4.20.2 CA / Correct handling of MAC control information / Buffer status / Inter-band CA

- Cell 10 is an Active SCell according to [18] cl. 6.3.47.1.4.20.3 CA / Correct handling of MAC control
information / Buffer status / Intra-band non-Contiguous CA
7.1.4.21 UE power headroom reporting / Extended PHR

(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established Extended PHR reporting configured }
ensure that {
when { periodicPHR-Timer is configured in RRCConnectionReconfiguration procedure }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, Extended PHR reporting configured }
ensure that {
when { periodicPHR-Timer expires and UL resources allocated for new transmission }
}
(3)
ETSI
ensure that {
when { Extended power headroom reporting is disabled }
then { UE stops transmitting Extended Power Headroom MAC Control Element }
}
6.1.3.6a.
[TS 36.321, clause 5.4.6]
between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated
Serving Cell and also with information about the difference between the nominal UE maximum power and the
estimated power for UL-SCH and PUCCH transmission on PCell.
The reporting period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of [9]. RRC controls Power
Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-
PathlossChange which sets the change in measured downlink pathloss and the required power backoff due to power
management (as allowed by P-MPRc [10]) to trigger a PHR [8].
- prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB for at
least one activated Serving Cell which is used as a pathloss reference since the last transmission of a PHR when
the UE has UL resources for new transmission;
is not used to disable the function;
- activation of an SCell with configured uplink.
- prohibitPHR-Timer expires or has expired, when the UE has UL resources for new transmission, and the
following is true in this TTI for any of the active Serving Cells with configured uplink:
- there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the
required power backoff due to power management (as allowed by P-MPRc [10]) for this cell has changed
more than dl-PathlossChange dB since the last transmission of a PHR when the UE had UL resources
allocated for transmission or PUCCH transmission on this cell.
NOTE: The UE should avoid triggering a PHR when the required power backoff due to power management
decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid reflecting such
temporary decrease in the values of PCMAX,c/PH when a PHR is triggered by other triggering conditions.
- if the allocated UL resources can accommodate a PHR MAC control element plus its subheader if extendedPHR
is not configured, or the Extended PHR MAC control element plus its subheader if extendedPHR is configured,
as a result of logical channel prioritization:
- if extendedPHR is configured:
- for each activated Serving Cell with configured uplink:
- obtain the value of the Type 1 power headroom;
- if the UE has UL resources allocated for transmission on this Serving Cell for this TTI:
ETSI
- if simultaneousPUCCH-PUSCH is configured:
- obtain the value of the Type 2 power headroom for the PCell;
- if the UE has a PUCCH transmission in this TTI:
- instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC
control element as defined in subclause 6.1.3.6a based on the values reported by the physical layer;
- else:
- obtain the value of the Type 1 power headroom from the physical layer;
as defined in subclause 6.1.3.6 based on the value reported by the physical layer;
[TS 36.321, clause 6.1.3.6a]
The Extended Power Headroom MAC control element is identified by a MAC PDU subheader with LCID as specified
in table 6.2.1-2. It has a variable size and is defined in Figure 6.1.3.6a-2. When Type 2 PH is reported, the octet
containing the Type 2 PH field is included first after the octet indicating the presence of PH per SCell and followed by
an octet containing the associated PCMAX,c field (if reported). Then follows in ascending order based on the
ServCellIndex [8] an octet with the Type 1 PH field and an octet with the associated PCMAX,c field (if reported), for the
PCell and for each SCell indicated in the bitmap.
The Extended Power Headroom MAC Control Element is defined as follows:
- Ci: this field indicates the presence of a PH field for the SCell with SCellIndex i as specified in [8]. The Ci field
set to "1" indicates that a PH field for the SCell with SCellIndex i is reported. The Ci field set to "0" indicates that
a PH field for the SCell with SCellIndex i is not reported;
- V: this field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0
indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2
PH, V=0 indicates real transmission on PUCCH and V=1 indicates that a PUCCH reference format is used.
Furthermore, for both Type 1 and Type 2 PH, V=0 indicates the presence of the associated PCMAX,c field, and
V=1 indicates that the associated PCMAX,c field is omitted;
reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding
measured values in dB can be found in subclause 9.1.8.4 of [9]);
- P: this field indicates whether the UE applies power backoff due to power management (as allowed by P-MPR
[10]). The UE shall set P=1 if the corresponding PCMAX,c field would have had a different value if no power
backoff due to power management had been applied;
~
- PCMAX,c: if present, this field indicates the PCMAX,c or PCMAX ,c [2] used for calculation of the preceding PH field.
The reported PCMAX,c and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.6a-1
(the corresponding measured values in dBm can be found in subclause 9.6.1 of [9]).
Figure 6.1.3.6a-1: Void
ETSI
C7 C6 C5 C4 C3 C2 C1 R
R R PCMAX,c 1
R R PCMAX,c 2
P V PH (Type 1, SCell 1)
R R PCMAX,c 3
...
P V PH (Type 1, SCell n)
R R PCMAX,c m
Figure 6.1.3.6a-2: Extended Power Headroom MAC Control Element
Table 6.1.3.6a-1: Nominal UE transmit power level for Extended PHR
PCMAX,c Nominal UE transmit power level

0 PCMAX_C_00
1 PCMAX_C_01
2 PCMAX_C_02
… …
61 PCMAX_C_61
62 PCMAX_C_62
63 PCMAX_C_63
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS is configured for Uplink Grant --> - - -
Allocation Type 2. The SS transmits UL grant
for the UE at every TTI for FDD and every 5ms
in a DL subframe for TDD.
provide Extended Power Headroom
parameters
Control Element?
message to confirm the setup of Extended
Power Headroom parameters.
Control Element 200ms after step 3?
disable Extended Power Headroom reporting
message to confirm the disabling of Extended
Power Headroom parameters
8 Check: for 2 seconds, does the UE transmit a --> MAC PDU 3 F
MAC PDU containing Power Headroom MAC
Control Element?
Note: Steps 3 and 4 can happen in 2 MAC PDU’s, or may be combined in one MAC PDU.
ETSI

c1 CHOICE{
phr-Confign CHOICE {
setup SEQUENCE {
dl-PathlossChange infinity
}
}
extendedPHR-r10 setup
}
}
}
}
}
}
}
}

c1 CHOICE{
phr-Config CHOICE {
release NULL
}
}
}
}
}
}
}
}
7.1.4.22 Correct HARQ process handling / UL MIMO

(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and UL MIMO configured }
ensure that {
when { UE receives one uplink grant (DCI format 4) with toggled NDI and two transport blocks
enabled, and has data available for transmission }
then { UE transmits two new MAC PDUs both using redundancy version 0 for two HARQ processes in a
TTI }
ETSI
(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted two MAC PDUs
less than maxHARQ-Tx times }
ensure that {
when { UE receives NACKs for two HARQ processes and no uplink grant is included for the next TTI
corresponding to the two HARQ processes }
then { UE performs non-adaptive retransmission of the two MAC PDUs with redundancy version
toggled by one of the last (re)transmission [0,2,3,1 order] }
}
(3)
ensure that {
when { UE receives NACK for one of the HARQ process and ACK for another HARQ process and no uplink
grant is included for the next TTI corresponding to the HARQ processes }
then { UE performs non-adaptive retransmission of the MAC PDU with redundancy version toggled by
one of the last (re)transmission [0,2,3,1 order] for the HARQ process that receives NACK and does
not retransmit any MAC PDUs for another HARQ process that receives ACK }
}
(4)
ensure that {
when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the two HARQ
processes with old NDI [not toggled] for one HARQ process and with toggled NDI for another HARQ
process, irrespective of ACK/NACK is received for previous (re)transmission }
on PDCCH for HARQ process with old NDI and transmits a new MAC PDU for HARQ process with new NDI }
}
(5)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted two MAC PDU less
ensure that {
when { UE receives ACKs and no uplink grant is included for the next TTI corresponding to the two
HARQ processes }
then { UE does not retransmit any MAC PDUs for the two HARQ processes }
}
5.4.2.2; TS 36.212, clause 5.3.3.1.8.
[TS 36.321, clause 5.4.2.1]
There is one HARQ entity at the UE for each Serving Cell with configured uplink, which maintains a number of parallel
HARQ processes allowing transmissions to take place continuously while waiting for the HARQ feedback on the
successful or unsuccessful reception of previous transmissions.
The number of parallel HARQ processes per HARQ entity is specified in [2], clause 8.
When the physical layer is configured for uplink spatial multiplexing [2], there are two HARQ processes associated
with a given TTI. Otherwise there is one HARQ process associated with a given TTI.
At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process(es) for which
a transmission should take place. It also routes the received HARQ feedback (ACK/NACK information), MCS and
resource, relayed by the physical layer, to the appropriate HARQ process(es).
When TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle.
TTI bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is
part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and triggered without waiting for
ETSI
feedback from previous transmissions according to TTI_BUNDLE_SIZE. The HARQ feedback of a bundle is only
received for the last TTI of the bundle (i.e. the TTI corresponding to TTI_BUNDLE_SIZE), regardless of whether a
transmission in that TTI takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is
also a TTI bundle. TTI bundling is not supported when the UE is configured with one or more SCells with configured
uplink.
TTI bundling is not supported for RN communication with the E-UTRAN in combination with an RN subframe
configuration.
For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply.
For each TTI, the HARQ entity shall:
- identify the HARQ process(es) associated with this TTI, and for each identified HARQ process:
- if an uplink grant has been indicated for this process and this TTI:
- if the received grant was not addressed to a Temporary C-RNTI on PDCCH and if the NDI provided in
the associated HARQ information has been toggled compared to the value in the previous transmission of
this HARQ process; or
- if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified
process is empty; or
- if the uplink grant was received in a Random Access Response:
Response:
- else:
- deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ
process;
- else:
- deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ
process;
- else, if the HARQ buffer of this HARQ process is not empty:
[TS 36.321, clause 5.4.2.2]
ETSI
last made transmission attempt.
transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum
information;
NOTE 1: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.
NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ
- if the MAC PDU was obtained from the Msg3 buffer; or
does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer in this TTI:
ETSI
- if CURRENT_TX_NB = maximum number of transmissions – 1:
- flush the HARQ buffer.
[TS 36.212, clause 5.3.3.1.8]
DCI format 4 is used for the scheduling of PUSCH in one UL cell with multi-antenna port transmission mode,
The following information is transmitted by means of the DCI format 4:
- Carrier indicator – 0 or 3 bits. The field is present according to the definitions in [3].
⎛
max⎜ ⎡log 2 ( N RB
UL UL
( N RB
⎡ ⎛⎛
+ 1) / 2) ⎤ , ⎢log 2 ⎜ ⎜⎜
⎡N RBUL / P + 1⎤⎞⎟ ⎞⎟⎤⎥ ⎞⎟
⎜ ⎜ ⎟⎟ ⎟
⎝ ⎢
⎢ ⎝⎝ 4 ⎠ ⎠⎥
⎥ ⎠ bits,
- Resource block assignment -
- where P is the UL RBG size as defined in section 8.1.2 of [3]
- For resource allocation type 0:
⎛
⎡
⎜ log 2 ( N RB ( N RB + 1) / 2)
UL UL
⎤ ⎞⎟⎠
- The ⎝ LSBs provide the resource allocation in the UL subframe as defined in section
8.1.1 of [3]
- For resource allocation type 1:
⎡ ⎛ ⎛ ⎡N RB
UL
/ P + 1⎤⎞ ⎞⎟⎤
- The ⎢ 2⎜⎜
log ⎜ ⎜ ⎟ ⎥ LSBs provide the resource allocation in the UL subframe as defined in
⎟⎟
⎢⎢ ⎝⎝ 4 ⎠ ⎠⎥⎥
section 8.1.2 of [3]
- TPC command for scheduled PUSCH – 2 bits as defined in section 5.1.1.1 of [3]
- Cyclic shift for DM RS and OCC index – 3 bits as defined in section 5.5.2.1.1 of [2]
- UL index – 2 bits as defined in sections 5.1.1.1, 7.2.1, 8 and 8.4 of [3] (this field is present only for TDD
operation with uplink-downlink configuration 0)
- Downlink Assignment Index (DAI) – 2 bits as defined in section 7.3 of [3] (this field is present only for TDD
operation with uplink-downlink configurations 1-6)
- CSI request – 1 or 2 bits as defined in section 7.2.1 of [3]. The 2-bit field only applies to UEs that are configured
with more than one DL cell.
- SRS request – 2 bits as defined in section 8.2 of [3]
- Resource allocation type – 1 bit as defined in section 8.1 of [3]
In addition, for transport block 1:
- Modulation and coding scheme and redundancy version – 5 bits as defined in section 8.6 of [3]
- New data indicator – 1 bit
ETSI
Precoding information and number of layers: number of bits as specified in Table 5.3.3.1.8-1. Bit field as shown in
Table 5.3.3.1.8-2 and Table 5.3.3.1.8- 3. Note that TPMI for 2 antenna ports indicates which codebook index is to be
used in Table 5.3.3A.2-1 of [2], and TPMI for 4 antenna ports indicates which codebook index is to be used in Table
5.3.3A.2-2, Table 5.3.3A.2-3, Table 5.3.3A.2-4 and Table 5.3.3A.2-5 of [2]. If both transport blocks are enabled,
transport block 1 is mapped to codeword 0; and transport block 2 is mapped to codeword 1. In case one of the transport
blocks is disabled, the transport block to codeword mapping is specified according to Table 5.3.3.1.5-2. For a single
enabled codeword, indices 24 to 39 in Table 5.3.3.1.8-3 are only supported for retransmission of the corresponding
transport block if that transport block has previously been transmitted using two layers.
Table 5.3.3.1.8-1: Number of bits for precoding information
Number of antenna ports at UE Number of bits for precoding information

2 3
4 6
Table 5.3.3.1.8-2: Content of precoding information field for 2 antenna ports
One codeword: Two codewords:

Codeword 0 enabled Codeword 0 enabled
Codeword 1 disabled Codeword 1 enabled
Bit field mapped to index Message Bit field mapped to index Message
0 1 layer: TPMI=0 0 2 layers: TPMI=0
1 1 layer: TPMI=1 1-7 reserved
2 1 layer: TPMI=2
… …
5 1 layer: TPMI=5
6-7 reserved
Table 5.3.3.1.8-3: Content of precoding information field for 4 antenna ports

Codeword 0 enabled Codeword 0 enabled
Bit field mapped to index Message Bit field mapped to index Message
… … … …
24 2 layers: TPMI=0 16 3 layers: TPMI=0
… … … …
40-63 reserved 28 4 layers: TPMI=0
29 - 63 Reserved
If the number of information bits in format 4 is equal to the payload size for DCI format 1, 2, 2A, 2B or 2C associated
with the configured DL transmission mode in the same serving cell, one zero bit shall be appended to format 4.
System Simulator:
- Cell 1
ETSI
- System information takes into account the parameters in table 7.1.2.11.3.1-1.
UE:
UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] using parameters as specified in Table
7.1.4.22.3.3-1 and 7.1.4.22.3.3-2.
- The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

U-S Message
1 The SS transmits one MAC PDU including two <-- MAC PDU (2 RLC SDUs) - -
RLC SDUs
2 The SS transmits one UL Grant sufficient for <-- Uplink Grant - -
transmitting loop back two RLC SDUs for two DCI: (DCI Format 4, redundancy
HARQ process X and Y, and both NDI indicate version#1= 0, redundancy
new transmission. version#2= 0)
3 Check: Does the UE transmit two MAC PDUs --> Transport block 1: 1 P
both including one RLC SDU in HARQ process MAC PDU
X and Y in a TTI, both redundancy version 0? Transport block 2:
(Note 1) MAC PDU
4 The SS transmits two NACKs for HARQ <-- HARQ NACK#X - -
process X and Y HARQ NACK#Y
5 Check: Does the UE retransmit the MAC PDUs --> Transport block 1: 2 P
for HARQ process X and Y, redundancy MAC PDU
version 2? Transport block 2:
(Note 1) MAC PDU
6 The SS transmits a NACK for HARQ process <-- HARQ NACK#X - -
X and ACK for HARQ process Y HARQ ACK#Y
7 Check: Does the UE retransmit the MAC PDU --> Transport block 1: 3 P
for HARQ process X, redundancy version 3? MAC PDU
(Note 1)
8 The SS transmits ACK for HARQ process X <-- HARQ ACK#X - -
9 Check: Does the UE retransmit the MAC PDUs --> Transport block 1: 5 F
for HARQ process X and Y? MAC PDU
Transport block 2:
MAC PDU
10 The SS transmits one MAC PDU including one <-- MAC PDU (1 RLC SDU) - -
RLC SDU
11 The SS transmits one UL grant for HARQ <-- Uplink Grant - -
process X and Y, with NDI not toggled and
redundancy version to be used as ‘1’ for
process X, with NDI toggled for process Y
12 Check: Does the UE retransmit the MAC PDU --> Transport block 1: 4 P
for HARQ process X using redundancy version MAC PDU (redundancy version 1)
1 and transmit a new MAC PDU sent by SS in Transport block 2:
step 10 for HARQ process Y? MAC PDU
(Note 1)
ETSI
Table 7.1.4.22.3.3-1: MAC-MainConfig {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1,

step 8)}

maxHARQ-Tx n6
}
}
Table 7.1.4.22.3.3-2: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-

1, step 8)}

am SEQUENCE {
}
}
}
7.1.5 PUSCH Hopping

7.1.5.1 Inter-TTI PUSCH hopping by uplink grant
(1)
with { UE in E-UTRA RRC_CONNECTED state and ‘Hopping-mode’ is set to ‘InterSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop’ bits indicating
Type 1 PUSCH Hopping }
then { UE transmits UL data on resource blocks as per type 1 PUSCH hopping}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.212 clause
5.3.3.1.1 and 36.213 clause 8.4, 8.4.1 & 8.4,2.
[TS 36.212, clause 5.3.3.1.1]
DCI format 0 is used for the scheduling of PUSCH.
- Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
- Hopping flag – 1 bit as defined in section 8.4 of [3]
⎡ UL
- Resource block assignment and hopping resource allocation – log 2 ( N RB UL
( N RB + 1) / 2) ⎤ bits
- For PUSCH hopping:
- NUL_hop MSB bits are used to obtain the value of n~PRB (i ) as indicated in subclause [8.4] of [3]
ETSI
- ⎛
⎜
⎝
⎡log 2 ( N RB
UL UL
( N RB + 1) / 2)⎤ − N UL_hop ⎞⎟ bits provide the resource allocation of the first slot in the UL
⎠
subframe
- For non-hopping PUSCH:
- ⎛
⎜
⎝
⎡log 2 ( N RB
UL UL
( N RB + 1) / 2) ⎤ ⎞⎟ bits provide the resource allocation in the UL subframe as defined in section
⎠
8.1 of [3]
[TS 36.213, clause 8.4]
The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding
PDCCH with DCI format 0 is set to 1 otherwise no PUSCH frequency hopping is performed.
A UE performing PUSCH frequency hopping shall determine its PUSCH resource allocation (RA) for the first slot of a
S1
subframe (S1) including the lowest index PRB ( n PRB (n) ) in subframe n from the resource allocation field in the latest
PDCCH with DCI format 0 for the same transport block. If there is no PDCCH for the same transport block, the UE
shall determine its hopping type based on
- the hopping information in the most recent semi-persistent scheduling assignment PDCCH, when the initial
PUSCH for the same transport block is semi-persistently scheduled or
- the random access response grant for the same transport block, when the PUSCH is initiated by the random
access response grant.
The resource allocation field in DCI format 0 excludes either 1 or 2 bits used for hopping information as indicated by
Table 8.4-1 below where the number of PUSCH resource blocks is defined as
⎧ N RB
UL ~ HO
− N RB − N RB
UL
(
mod 2 ) Type 1 PUSCH hopping
⎪ UL
N PUSCH
RB = ⎨ N RB Type 2 N sb = 1 PUSCH hopping
⎪ UL ~ HO
⎩ N RB − N RB Type 2 N sb > 1 PUSCH hopping
~ HO
For type 1 and type 2 PUSCH hopping, N RB = N RB
HO
+ 1 if N RB
HO
is an odd number where N RB HO
defined in [3].
~ HO
N RB = N RB in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits
HO
shall be y = ⎡log 2 ( N RB
UL UL
( N RB + 1) / 2) ⎤ − N UL _ hop , where NUL_hop = 1 or 2 bits. The number of contiguous RBs
that can be assigned to a type-1 hopping user is limited to ⎣2 y / N RBUL ⎦ . The number of contiguous RBs that can be
min( ⎣ ⎦ , ⎣N
assigned to a type-2 hopping user is limited to 2 y / N RB
UL
/ N ⎦ ,where the number of sub-bands
PUSCH
RB sb
)
N sb is given by higher layers.
A UE performing PUSCH frequency hopping shall use one of two possible PUSCH frequency hopping types based on
the hopping information. PUSCH hopping type 1 is described in section 8.4.1 and type 2 is described in section 8.4.2.
Table 8.4-1: Number of Hopping Bits NUL_hop vs. System Bandwidth
System BW #Hopping bits for

N UL 2nd slot RA
RB
(NUL_hop)
6-49 1
50-110 2
The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is “inter-subframe”
or “intra and inter-subframe”.
[TS 36.213, clause 8.4.1]
ETSI
For PUSCH hopping type 1 the hopping bit or bits indicated in Table 8.4-1 determine n~PRB (i ) as defined in Table 8.4-2.
~ HO
~ S 1 (i ) + N
) of the 1st slot RA in subframe i is defined as nPRB (i ) = n
S1 S1
The lowest index PRB ( n PRB PRB RB / 2 , where
S1
n PRB (i ) = RBSTART , and RBSTART is obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
~ HO
~ (i ) + N
The lowest index PRB ( n PRB (i ) ) of the 2nd slot RA in subframe i is defined as nPRB (i ) = n PRB RB / 2 .
The set of physical resource blocks to be used for PUSCH transmission are LCRBs contiguously allocated resource
S1
blocks from PRB index n PRB for the 1st slot, and from PRB index n PRB (i ) for the 2nd slot, respectively, where LCRBs is
obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
If the Hopping-mode is "inter-subframe", the 1st slot RA is applied to even CURRENT_TX_NB, and the 2nd slot RA is
applied to odd CURRENT_TX_NB, where CURRENT_TX_NB is defined in [8].
[TS 36.213, clause 8.4.2]
Table 8.4-2: PDCCH DCI Format 0 Hopping Bit Definition
System BW Number of Information in

n~PRB (i )
N UL
RB Hopping bits hopping bits
6 – 49 1
0
⎛
⎜
⎝
⎣N RBPUSCH / 2⎦ + n~PRB
S1
(i ) ⎞⎟ mod N RB
⎠
PUSCH
,
1 Type 2 PUSCH Hopping
00
⎛
⎜
⎝
S1
⎠
PUSCH
50 – 110 2
01
⎛
⎜−
⎝
S1
⎠
PUSCH
10
⎛
⎜
⎝
S1
⎠
PUSCH
System Simulator
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
Exception: Steps 2 to 5 are executed as per
table 7.1.5.1.3.2-2
2 SS transmits a MAC PDU including 8 <-- MAC PDU - -
(FDD)/4(TDD) RLC SDU’s
3 The SS waits for 60 ms - - - -
Exception: Steps 4 and 5 are repeated such
that UE sends data in 8 ([FDD)/4(TDD)
consecutive UL TTI’s.
allowing the UE to return 1 RLC SDU as
received in step 2. Hopping flag’ set as 1, all
bits in ‘NUL_hop’ are set as per table 7.1.5.3.2-2
for various execution runs
5 Check: Does the UE transmit a MAC PDU - - 1 P
Note 1: Steps 4 and 5 are repeated for 8 times corresponding to 8 sub frames for FDD and 4 for default TDD
configuration 1.
Note 2: The grant allocated in step 4 is such that the loop back PDU's are received in 8 (FDD)/4(TDD) UL TTI's
Table 7.1.5.1.3.2-2: Bandwidth dependent parameters
Number of Hopping Information in hopping

System BW Execution Counter K bits
bits
5 MHz 1 1 0
1 00
10/20 MHz 2 2 01
3 10
None
7.1.5.2 Predefined intra-TTI PUSCH hopping (N_sb=1)

(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands 'N-sb' is set to 1 and ‘Hopping-mode’
is set to 'intraAndInterSubFrame'}
ensure that {
when { UE receives for a TTI an uplink grant with 'Hopping flag' set as 1, 'NUL_hop' bits all set to
1(Type 2 predefined hopping) }
then { UE transmits data with predefined, intra-TTI PUSCH hopping}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.211 clause 5.3.4 ,
36.212 clause 5.3.3.1.1 and 36.213 clause 8.4, 8.4.2.
[TS 36.211, clause 5.3.4]
ETSI
If uplink frequency-hopping with predefined hopping pattern is enabled, the set of physical resource blocks to be used
for transmission in slot ns is given by the scheduling grant together with a predefined pattern according to
(
n~PRB (ns ) = n~VRB + f hop (i ) ⋅ N RB
sb
((
+ N RB
sb
) (
− 1 − 2 n~VRB mod N RB
sb
))
⋅ f m (i ) mod( N RB
sb
)
⋅ N sb )
⎧⎣ns 2⎦ inter − subframe hopping
i=⎨
⎩ns intra and inter − subframe hopping
⎧⎪ n~PRB (ns ) N sb = 1
nPRB (ns ) = ⎨ ~
⎡
⎪⎩nPRB (ns ) + N RB 2
HO
⎤ N sb > 1
⎧⎪ nVRB N sb = 1
n~VRB = ⎨
⎡
⎪⎩nVRB − N RB 2
HO
⎤ N sb > 1
where nVRB is obtained from the scheduling grant as described in Section 8.1 in [4]. The parameter pusch-
HO sb
HoppingOffset, N RB , is provided by higher layers.. The size N RB of each sub-band is given by,
⎧
⎪
UL
N RB N sb = 1
=⎨
⎣( )
sb
N RB
⎪
⎩
UL
N RB − HO
N RB − HO
N RB mod 2 N sb ⎦ N sb > 1
where the number of sub-bands N sb is given by higher layers. The function f m (i ) ∈ {0,1} determines whether mirroring
is used or not. The parameter Hopping-mode provided by higher layers determines if hopping is “inter-subframe” or
“intra and inter-subframe”.
The hopping function f hop (i ) and the function f m (i ) are given by
⎧ 0 N sb = 1
⎪ i⋅10+ 9
⎪( f hop (i − 1) + ∑ c(k ) × 2
k −( i⋅10+1)
⎪ ) mod N sb N sb = 2
f hop (i ) = ⎨ k =i⋅10+1
⎪ ⎛ i⋅10+9 ⎞
⎪( f hop (i − 1) + ⎜ ∑ c(k ) × 2 k −( i⋅10+1) ⎟ mod( N sb − 1) + 1) mod N sb N sb > 2
⎪
⎩ ⎝ k =i⋅10+1 ⎠
⎧i mod 2 N sb = 1 and intra and inter − subframe hopping

⎪
f m (i ) = ⎨CURRENT _ TX _ NB mod 2 N sb = 1 and inter − subframe hopping
⎪ c(i ⋅ 10) N sb > 1
⎩
where f hop (−1) =0 and the pseudo-random sequence c(i ) is given by section 7.2 and CURRENT_TX_NB indicates
the transmission number for the transport block transmitted in slot ns as defined in [8]. The pseudo-random sequence
cinit = N ID for FDD and cinit = 2 ⋅ (n f mod 4) + N ID for TDD at the start of
cell 9 cell
generator shall be initialised with
each frame.
[TS 36.212, clause 5.3.3.1.1]
UL
- Resource block assignment and hopping resource allocation – log 2 ( N RB UL
( N RB⎡+ 1) / 2) ⎤ bits
ETSI
- ⎛
⎜
⎝
⎡log 2 ( N RB
UL UL
⎠
subframe
- ⎛
⎜
⎝
⎡log 2 ( N RB
UL UL
( N RB + 1) / 2) ⎤ ⎞⎟ bits provide the resource allocation in the UL subframe as defined in section
⎠
8.1 of [3]
[TS 36.213, clause 8.4]
The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding
PDCCH with DCI format 0 is set to 1 otherwise no PUSCH frequency hopping is performed.
A UE performing PUSCH frequency hopping shall determine its PUSCH resource allocation (RA) for the first slot of a
S1
subframe (S1) including the lowest index PRB ( n PRB (n) ) in subframe n from the resource allocation field in the latest
PDCCH with DCI format 0 for the same transport block. If there is no PDCCH for the same transport block, the UE
shall determine its hopping type based on
- the hopping information in the most recent semi-persistent scheduling assignment PDCCH, when the initial
PUSCH for the same transport block is semi-persistently scheduled or
- the random access response grant for the same transport block, when the PUSCH is initiated by the random
The resource allocation field in DCI format 0 excludes either 1 or 2 bits used for hopping information as indicated by
Table 8.4-1 below where the number of PUSCH resource blocks is defined as
⎧ N RB
UL ~ HO
− N RB − N RB
UL
(
mod 2 ) Type 1 PUSCH hopping
⎪ UL
N PUSCH
RB = ⎨ N RB Type 2 N sb = 1 PUSCH hopping
⎪ UL ~ HO
⎩ N RB − N RB Type 2 N sb > 1 PUSCH hopping
~ HO
For type 1 and type 2 PUSCH hopping, N RB = N RB
HO
+ 1 if N RB
HO
is an odd number where N RB HO
defined in [3].
~ HO
N RB = N RB in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits
HO
shall be y = ⎡log 2 ( N RB
UL UL
( N RB + 1) / 2) ⎤ − N UL _ hop , where NUL_hop = 1 or 2 bits. The number of contiguous RBs
⎣ y UL
⎦
that can be assigned to a type-1 hopping user is limited to 2 / N RB . The number of contiguous RBs that can be
assigned to a type-2 hopping user is limited to

min( ⎣2 y / N RBUL ⎦ , ⎣N PUSCH
RB / N sb ⎦ ,where the number of sub-bands
)
N sb is given by higher layers.
A UE performing PUSCH frequency hopping shall use one of two possible PUSCH frequency hopping types based on
the hopping information. PUSCH hopping type 1 is described in section 8.4.1 and type 2 is described in section 8.4.2.
Table 8.4-1: Number of Hopping Bits NUL_hop vs. System Bandwidth
System BW #Hopping bits for

N UL 2nd slot RA
RB
(NUL_hop)
6-49 1
50-110 2
The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is “inter-subframe”
or “intra and inter-subframe”.
ETSI
[TS 36.213, clause 8.4.2]
In PUSCH hopping type 2 the set of physical resource blocks to be used for transmission in slot ns is given by the
scheduling grant together with a predefined pattern according to [3] section 5.3.4. If the system frame number is not
acquired by the UE yet, the UE shall not transmit PUSCH with type-2 hopping and Nsb>1 for TDD, where Nsb is defined
in [3].
Table 8.4-2: PDCCH DCI Format 0 Hopping Bit Definition
System BW Number of Information in

n~PRB (i )
N UL
RB Hopping bits hopping bits
6 – 49 1
0
⎛
⎜
⎝
S1
⎠
PUSCH
,
00
⎛
⎜
⎝
S1
⎠
PUSCH
50 – 110 2
01
⎛
⎜−
⎝
S1
⎠
PUSCH
10
⎛
⎜
⎝
S1
⎠
PUSCH
System Simulator
- Cell 1
UE:
None.
Preamble:

U-S Message
2 SS transmits a MAC PDU including 8 <-- MAC PDU - -
(FDD)/4(TDD) RLC SDU’s
3 The SS waits for 60 ms - - - -
Exception: Steps 4 and 5 are repeated such
that UE sends data in 8 ([FDD)/4(TDD)
consecutive UL TTI’s.
allowing the UE to return 1 RLC SDU as
bits in ‘NUL_hop’ are set to 1.
Note 1: steps 4 and 5 are repeated for 8 times corresponding to 8 sub frames for FDD and 4 for default TDD
configuration 1.
Note 2: The grant allocated in step 4 is such that the loop back PDU's are received in 8 (FDD)/4(TDD) UL TTI's
ETSI
Table 7.1.5.2.3.3-1: SystemInformationBlockType2(preamble)

SEQUENCE {
radioResourceConfigCommon SEQUENCE {} RadioResourceCo
nfigCommonSIB-
DEFAULT-7152
}
Table 7.1.5.2.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7152(Table 7.1.5.2.3.3-1)

RadioResourceConfigCommonSIB-DEFAULT-7152
::= SEQUENCE {
pusch-Config PUSCH-ConfigCommon-
DEFAULT-7152
}
Table 7.1.5.2.3.3-3: PUSCH-ConfigCommon-DEFAULT-7152(Table 7.1.5.2.3.3-2)

PUSCH-ConfigCommon-DEFAULT-7152 ::=
SEQUENCE {
pusch-ConfigBasic SEQUENCE {
n-SB 1 Default value
hoppingMode intraAndInterSubFrame
pusch-HoppingOffset See subclause Default value
4.6.8[36.508]
}
}
7.1.5.3 Predefined intra-TTI PUSCH hopping (N_sb=2/3/4)

(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands ‘N-sb’ is set to 2/3/4 and ‘Hopping-
mode’ is set to ‘intraAndInterSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop’ bits all set to
then { UE transmits data with predefined, inter-TTI PUSCH hopping}
}
System Simulator
- Cell 1
ETSI
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode, Test Mode Activated (State 2A) according to [18].

U-S Message
EXCEPTION: Step 0 to 7 are repeated for
execution counter k=1 to 3
0 The SS transmits a Paging message in a <-- Paging - -
paging occasion including a
systemInfoModification.
0a From the beginning of the next modification - - - -
period the SS transmits a modified
SystemInformationBlockType2 as specified.
1 The UE is brought to state Loopback - - - -
Activated (state 4) according to [18]
SDU
4 The SS waits for 60 ms - - -
received in step 2. Hopping flag’ set as 1,
‘NUL_hop’ is set to 1.
6 Check: Does the UE transmit a MAC PDU - - 1 P
7 The SS releases the RRC connection - - - -
Table 7.1.5.3.3.3-1: SystemInformationBlockType2 (Step 0 of Table 7.1.5.3.3.2-1)

SEQUENCE {
ac-BarringInfo SEQUENCE {} Not present
nfigCommonSIB-
DEFAULT-7153
}
Table 7.1.5.3.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7153

::= SEQUENCE {
DEFAULT-7153
}
ETSI
Table 7.1.5.3.3.3-3: PUSCH-ConfigCommon-DEFAULT-7153

SEQUENCE {
n-SB 2 Execution
counter k =1
n-SB 3 Execution
counter k =2
n-SB 4 Execution
counter k =3
hoppingMode intraAndInterSubFrame
pusch-HoppingOffset See subclause 4.6.8 Default value
enable64QAM FALSE Default value
}
}
7.1.5.4 Predefined inter-TTI PUSCH hopping (N_sb=1)

(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands 'N-sb' is set to 1 and 'Hopping-mode'
is set to 'interSubFrame'}
ensure that {
when { UE receives for a TTI an uplink grant with 'Hopping flag' set as 1, 'NUL_hop' bits all set to
}
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands 'N-sb' is set to 1, 'Hopping-mode' is
set to 'interSubFrame' has transmitted a transport block with predefined, inter-TTI PUSCH hopping }
ensure that {
when { UE has to make a non adaptive retransmission) }
}
Same Pre-test conditions as in clause 7.1.5.2.3.1
ETSI

U-S Message
SDU
3 The SS waits for 60 ms. - - - -
bits in ‘NUL_hop’ are set to 1.
5 Check: Does the UE transmit a MAC PDU - MAC PDU 1 P
6 The SS transmits a HARQ NACK <-- HARQ NACK - -
corresponding to grant in step 4, for same
HARQ process as in step 5?
12 The SS transmits an HARQ ACK <-- HARQ ACK - -
Note: 4 HARQ transmissions is selected to be less than MaxHARQ-Tx (=5)
None
7.1.5.5 Predefined inter-TTI PUSCH hopping (N_sb=2/3/4)

(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands ‘N-sb’ is set to 2/3/4 and ‘Hopping-
mode’ is set to ‘interSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop’ bits are all
set to 1(Type 2 predefined hopping) }
}
Same Pre-test conditions as in clause 7.1.5.3.3.1
Same Test procedure sequence as in table 7.1.5.3.3.2-1
ETSI
Table 7.1.5.5.3.3-1: SystemInformationBlockType2 (Step 0 of Table 7.1.5.3.3.2-1)

SEQUENCE {
ac-BarringInfo SEQUENCE {} Not present
nfigCommonSIB-
DEFAULT-7155
}
Table 7.1.5.5.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7155

::= SEQUENCE {
DEFAULT-7155
}
Table 7.1.5.5.3.3-3: PUSCH-ConfigCommon-DEFAULT-7155

SEQUENCE {
n-SB 2 Execution
counter k =1
n-SB 3 Execution
counter k =2
n-SB 4 Execution
counter k =3
hoppingMode interSubFrame Default value
pusch-HoppingOffset See subclause 4.6.8 Default value
enable64QAM FALSE Default value
}
}
7.1.6 DRX operation

7.1.6.1 DRX operation / Short cycle not configured / Parameters configured by RRC
(1)
with { UE in CONNECTED mode }
ensure that {
when { Long DRX cycle is configured and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) =
drxStartOffset }
then { UE starts the OnDurationTimer and monitors the PDCCH for OnDurationTimer PDCCH-subframes
}
}
(2)
ensure that {
when { Long DRX cycle is configured and a new DL transmission is indicated on the PDCCH during
Active Time }
ETSI
then { UE starts or restarts the Drx-InactivityTimer and monitors the PDCCH for Drx-
InactivityTimer PDCCH sub-frames starting from the next PDCCH sub-frame of the PDCCH sub-frame where
the DL new transmission was indicated }
}
(3)
ensure that {
when { Long DRX cycle is configured and if a HARQ RTT Timer expires in this subframe and the data
in the soft buffer of the corresponding HARQ process was not successfully decoded }
then { UE starts the drx-RetransmissionTimer for the corresponding HARQ process and monitors the
PDCCH for drx-RetransmissionTimer consecutive PDCCH-subframes }
}
(4)
ensure that {
when { Long DRX cycle is configured and an uplink grant for a pending HARQ retransmission can
occur in this subframe }
then { UE monitors the PDCCH in this subframe }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH
in PDCCH-subframes.
...
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure
3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH
indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL

retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
...
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission
is expected by the UE.
ETSI
...
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and
subframes including DwPTS.
[TS 36.321, clause 5.7]
The UE may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring activity for
the UE’s C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and Semi-Persistent Scheduling C-RNTI (if configured).
When in RRC_CONNECTED, if DRX is configured, the UE is allowed to monitor the PDCCH discontinuously using
the DRX operation specified in this subclause; otherwise the UE monitors the PDCCH continuously. When using DRX
operation, the UE shall also monitor PDCCH according to requirements found in other subclauses of this specification.
RRC controls DRX operation by configuring the timers onDurationTimer, drx-InactivityTimer, drx-
RetransmissionTimer (one per DL HARQ process except for the broadcast process), the longDRX-Cycle, the value of
the drxStartOffset and optionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timer per DL HARQ
process (except for the broadcast process) is also defined (see subclause 7.7).
When a DRX cycle is configured, the Active Time includes the time while:
- onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or mac-ContentionResolutionTimer (as

described in subclause 5.1.5) is running; or
- a Scheduling Request sent on PUCCH is pending (as described in subclause 5.4.4); or
- an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ
buffer; or
- a PDCCH indicating a new transmission addressed to the C-RNTI of the UE has not been received after
successful reception of a Random Access Response for the explicitly signalled preamble (as described in
subclause 5.1.4).
When DRX is configured, the UE shall for each subframe:
- If the Short DRX Cycle is used and [(SFN * 10) + subframe number] modulo (shortDRX-Cycle) =
(drxStartOffset) modulo (shortDRX-Cycle); or
- if the Long DRX Cycle is used and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) =
drxStartOffset:
- start onDurationTimer.
- if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ
process was not successfully decoded:
- start the drx-RetransmissionTimer for the corresponding HARQ process.
- if a DRX Command MAC control element is received:
- stop onDurationTimer;
- stop drx-InactivityTimer.
- if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
- if the short DRX cycle is configured:
- start or restart drxShortCycleTimer;
- use the Short DRX Cycle.
- else:
- use the Long DRX cycle.
- if drxShortCycleTimer expires in this subframe:
ETSI
- use the long DRX cycle.
- during the Active Time, for a PDCCH-subframe if the subframe is not required for uplink transmission for half-
duplex FDD UE operation and if the subframe is not part of a configured measurement gap:
- monitor the PDCCH;
- if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
- start the HARQ RTT Timer for the corresponding HARQ process;
- stop the drx-RetransmissionTimer for the corresponding HARQ process.
- if the PDCCH indicates a new transmission (DL or UL):
- start or restart drx-InactivityTimer.
- when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such
is expected.
NOTE: A UE may optionally choose to not send CQI/PMI/RI reports on PUCCH and/or SRS transmissions for
up to 4 subframes following a PDCCH indicating a new transmission (UL or DL) received in the last
subframe of active time. The choice not to send CQI/PMI/RI reports on PUCCH and/or SRS
transmissions is not applicable for subframes where onDurationTimer is running.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] configured to return no data in UL.
For FDD, NormalSF(current SFN,current subframe number,y)=y; For TDD, NormalSF(current SFN,current subframe
number,y) counts the minimum number of normal subframes needed to cover y number of PDCCH-subframes until
next PDCCH-subframe available, starting from current subframe number on current SFN. For example at step 1,
drxStartOffset can point to UL or DL subframe for TDD. If it points to a UL subframe, NormalSF(current SFN,current
subframe number,0) counts the number of normal subframes until reach the first DL/special subframe available. If
drxStartOffset points to a DL subframe, NormalSF(current SFN,current subframe number,0)=0.
For example at step 13, assuming drxStartOffset points to subframe number 0 at frame number A, NormalSF(A, 0,
onDurationTimer-2) is first added, which counts 18 PDCCH-subframes/30 normal subframes in this case. The current
subframe becomes subframe number 0 at frame number A+3. Secondly, HARQ RTT timer is added, which is 11 normal
subframes. The current subframe becomes subframe number 1 at frame number A+4. To further add in NormalSF(A+4,
1, drx-RetransmissionTimer-1), which is to counts 5 PDCCH-subframes/9 normal subframes, the current subframe is
subframe number 0 at frame number A+5.
ETSI
Table 7.1.6.1.3.2-1: Main Behaviour

U-S Message
to configure specific DRX parameters
1 In the first PDCCH sub frame when the <-- MAC PDU - -
OnDurationTimer is running, the SS indicates
the transmission of a DL MAC PDU on the
PDCCH.
i.e., on the subframe with the subframe

number = [csfn1 + NormalSF(SFN1, csfn1, 0)]
modulo 10, and system frame number = SFN1
+ floor([csfn1 + NormalSF(SFN1, csfn1,
0)]/10); where [(SFN1 * 10) + csfn1] modulo
(LongDRX-Cycle) = drxStartOffset
2 Check: Does the UE transmit a HARQ ACK for --> HARQ ACK 1 P
the DL MAC PDU in Step 1?
3 At least drx-InactivityTimer PDCCH-sub <-- MAC PDU - -
frames after the transmission of the MAC PDU
in Step 1 has been indicated(This means the
next DRX cycle or later after Step 1) in the last
PDCCH sub frame while the onDurationTimer
is still running, the SS indicates the
transmission a DL MAC PDU on the PDDCH.
(Note 4).

number = [csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer-1)]
+ floor([csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer-
5 drx-InactivityTimer PDCCH-subframes after <-- MAC PDU - -
the transmission of the MAC PDU transmitted
in step 3 was indicated on the PDCCH, the SS
indicates the transmission of a DL MAC PDU
on the PDCCH. (Note 4)
i.e. on the subframe with the subframe number

= [csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer + drx-
InactivityTimer-1)] modulo 10, and system
frame number = SFN2 + floor([csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer+ drx-
InactivityTimer-1)]/10)
7 At least drx-InactivityTimer PDCCH sub frames <-- Invalid MAC PDU - -
after the transmission of the MAC PDU in Step
5 has been indicated (This means the next
DRX cycle or later after Step 3) and 1 PDCCH
sub-frame before the OnDurationTimer
expires, the SS indicates the transmission of a
DL MAC PDU on the PDDCH. The DL MAC
PDU transmitted is invalid. (Note 1, Note 4)

number = [csfn3 + NormalSF(SFN3, csfn3,
onDurationTimer-2)] mod 10, and system
ETSI
frame number = SFN3 + floor([csfn3 +

NormalSF(SFN3, csfn3, onDurationTimer-
8 Check: Does the UE transmit a HARQ NACK --> HARQ NACK 1 P

for the DL MAC PDU in Step 7?
9 In the first PDCCH sub frame when the Drx- <-- MAC PDU - -
RetransmissionTimer for the MAC PDU in Step
7 is started, the SS indicates the transmission
of a DL MAC PDU on the PDCCH.

number = [csfn4 + NormalSF(SFN4, csfn4, 0)]
+ floor([csfn4 + NormalSF(SFN4, csfn4,
0)]/10); where csfn4 = [csfn3 +
2)+HARQ RTT timer] modulo 10 and
SFN4=SFN3+floor([csfn3 + NormalSF(SFN3,
csfn3, onDurationTimer-2)+HARQ RTT
timer]/10)
For TDD the HARQ RTT timer is the HARQ

RTT timer for the DL transmission in Step 7.
11 At least drx-InactivityTimer PDCCH sub frames <-- Invalid MAC PDU - -
after the transmission of the DL MAC PDU in
Step 9 has been indicated (This means the
next DRX cycle or later after Step 9) and 1
PDCCH sub-frame before the
OnDurationTimer expires, the SS indicates the
transmission of DL MAC PDU on the PDCCH.
The DL MAC PDU transmitted is invalid(Note
1, Note 4)

onDurationTimer-2)] modulo 10 and system
frame number=SFN5+floor([csfn5 +
2)]/10) ; where [(SFN5 * 10) + csfn5] modulo
12 Check: Does the UE transmit a HARQ NACK --> HARQ NACK 1 P

13 In the last PDCCH sub frame when the drx- <-- MAC PDU - -
RetransmissionTimer for MAC PDU in Step 11
is still running, the SS indicates the
transmission of a DL MAC PDU on the
PDCCH.
i.e. on the subframe with subframe number =

[csfn6 + NormalSF(SFN6,csfn6,drx-
RetransmissionTimer -1)] modulo 10 and the
system frame number=SFN6+floor([csfn6 +
NormalSF(SFN6,csfn6,drx-
RetransmissionTimer -1)]/10); where the csfn6
= [csfn5 + NormalSF(SFN5, csfn5,
onDurationTimer-2)+HARQ RTT timer] modulo
10 and SFN6=SFN5+floor([csfn5 +
2)+HARQ RTT timer]/10);

ETSI

15 The SS is configured for Uplink Grant <-- UL grant on PDCCH - -
Allocation Type 2. At least drx-InactivityTimer
PDCCH sub frames after the transmission of
the DL MAC PDU in Step 13 has been
indicated in the last sub-frame when the
onDuratiopnTimer is still running (This means
the next DRX cycle or later after Step 7), the
SS indicates an UL grant to the UE on the
PDCCH. (Note 4)

onDurationTimer-1)] modulo 10 and system
frame number=SFN7 + floor([csfn7 +
16 Check: Does the UE transmit a Buffer Status --> Buffer Status Report MAC control - -
Report on the UL indicating an empty buffer? element
17 X sub frames after the sub frame in which the <-- MAC PDU - -
UL grant was indicated on the PDCCH for the
UL MAC PDU sent in the previous step the SS
indicates the transmission of a DL MAC PDU
on the PDCCH.
X is the number of sub frames required to do a

retransmission of the UL MAC PDU
transmitted in the previous Step maxHARQ-Tx
-1 times (for FDD this is 8x maxHARQ-Tx sub
frames, for TDD this is 10x maxHARQ-Tx sub
frames considering the default configuration
1.).
Note 1: Invalid MAC PDU is a MAC PDU that fails the CRC check.
Note 2: All the DL MAC PDU are transmitted with the NDI set on the PDCCH.
Note 3: Timer tolerances for the MAC DRX related timers measured in subframes or PDCCH subframes is 0. These
timers are: drx-InactivityTimer, drx-RetransmissionTimer, HARQ RTT Timer.
Note 4: The drx-InactivityTimer is started in the next PDCCH sub-frame of the PDCCH sub-frame where DL new
transmission is indicated.
ETSI
Table 7.1.6.1.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 0A of table

7.1.6.1.3.2-1)

radioResourceConfigDedicated::= SEQUENCE {
explicitValue::= SEQUENCE {
maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
drx-InactivityTimer psf6
drx-RetransmissionTimer psf6
longDRX-CycleStartOffset CHOICE {
sf640 4
}
shortDRX Not present
}
}
timeAlignmentTimerDedicated infinity
phr-Config CHOICE {
release NULL
}
}
}
}
7.1.6.2 DRX Operation / Short cycle not configured / DRX command MAC control
element reception
(1)
ensure that {
when { long DRX cycle is configured and a DRX Command MAC control element is received }
then { UE successfully decodes the MAC control PDU }
}
(2)
ensure that {
when { long DRX cycle is configured and the HARQ RTT Timer is running and a DRX Command MAC
control element is received }
then { UE continues running the HARQ RTT timer }
}
(3)
ensure that {
ETSI
when { long DRX cycle is configured and the drx-RetransmissionTimer is running and a DRX Command
MAC control element is received }
then { UE continues running the drx-RetransmissionTimer and monitors the PDCCH }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH
in PDCCH-subframes.
...
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure
3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH
indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL

retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
...
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission
is expected by the UE.
...
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and
subframes including DwPTS.
[TS 36.321, clause 5.7]
- if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ
process was not successfully decoded:
- start the drx-RetransmissionTimer for the corresponding HARQ process.
- if a DRX Command MAC control element is received:
- stop onDurationTimer;
- stop drx-InactivityTimer.
ETSI
- if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
- if the short DRX cycle is configured:
- start or restart drxShortCycleTimer;
- use the Short DRX Cycle.
- else:
- use the Long DRX cycle.
- if drxShortCycleTimer expires in this subframe:
- use the long DRX cycle.
- during the Active Time, for a PDCCH-subframe except if the subframe is required for uplink transmission for
half-duplex FDD UE operation and except if the subframe is part of a configured measurement gap:
- monitor the PDCCH;
- if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
- start the HARQ RTT Timer for the corresponding HARQ process;
- stop the drx-RetransmissionTimer for the corresponding HARQ process.
- if the PDCCH indicates a new transmission (DL or UL):
- start or restart drx-InactivityTimer.
- when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such
is expected.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] configured to return no data in UL.
The definition of NormalSF(current SFN,current subframe number,y) can be found in clause 7.1.6.1.3.2.
ETSI

U-S Message
to configure specific DRX parameters
1 In a PDCCH sub frame which is X PDCCH sub MAC PDU - -
frames before the PDCCH sub-frame in which
the onDurationTimer expires,
with drx-InactivityTimer< X < the number of
PDCCH subframes encapsulated by HARQ
RTT timer, the SS indicates the transmission
of a DL MAC PDU on the PDCCH. The SS
transmits an invalid MAC PDU.(Note 1)
<--
number csfn2 = [csfn1+NormalSF(SFN1,
csfn1, onDurationTimer-1-X)] modulo 10, and
the system frame number SFN2 =
SFN1+floor([csfn1+NormalSF(SFN1, csfn1,
onDurationTimer-1-X)]/10); and [(SFN1 * 10) +
csfn1] modulo (Long DRX Cycle) =
drxStartOffset.
2 Check: Does the UE transmit a HARQ NACK HARQ NACK 1 P

-->
3 In a PDCCH sub frames before the MAC PDU(DRX MAC Control - -
onDurationTimer expires, the SS indicates the element)
transmission of a DL MAC PDU on the
PDCCH. The SS transmits a DL MAC PDU
with DRX MAC Control element.
UE successfully decodes the MAC PDU.
<--
csfn1, onDurationTimer-1-X+Y)] modulo 10,
and the system frame number SFN3 =
onDurationTimer-1-X+Y)]/10); and 0<Y<X)
4 Check: Does the UE transmit a HARQ ACK for HARQ ACK 1 P

-->
5 In the PDCCH sub frame when the drx- MAC PDU - -
RetransmissionTimer for the MAC PDU
indicated in Step 1 on the PDCCH is started
the SS indicates the transmission of a DL MAC
PDU. The SS transmits an invalid MAC
PDU.(Note 1)

<--
csfn4, 0)] modulo 10, and the system frame
number SFN5 =
0)]/10); where csfn4 = [csfn2+HARQ RTT
Timer] modulo 10, and the SFN4 =
SFN2+floor([csfn2+HARQ RTT Timer]/10);

RTT timer for the DL transmission in Step 1
6 Check: Does the UE transmit a HARQ NACK HARQ NACK 2,3 P
-->
7 Z PDCCH sub frames, MAC PDU(DRX MAC Control - -
where Z>drx-InactivityTimer, before the element)
<--
PDCCH sub-frame in which the drx-
RetransmissionTimer for the DL MAC PDU in
ETSI
Step 5 expires, the SS indicates the

transmission of a DL MAC PDU. The SS
transmits a DL MAC PDU with DRX MAC
Control element.

number = [csfn6+NormalSF(SFN6, csfn6, drx-
RetransmissionTimer –Z)] modulo 10, and the
system frame number =
drx-RetransmissionTimer –Z)]/10); where
csfn6 = [csfn5+HARQ RTT Timer] modulo 10,
and the SFN6 = SFN5+floor([csfn5+HARQ
RTT Timer]/10);

8 Check: Does the UE transmit a HARQ ACK for HARQ ACK 2,3, P
-->
the DL MAC PDU in Step 7? 1
9 In the last sub frame when the Drx- MAC PDU - -
RetransmissionTimer for the DL MAC PDU
indicated on the PDCCH in Step 5 is still
running, the SS indicates the transmission of a
DL MAC PDU.
<--
number = [csfn6+NormalSF(SFN6, csfn6, drx-
RetransmissionTimer –1)] modulo 10, and the
system frame number =
drx-RetransmissionTimer –1)]/10);
10 Check: Does the UE transmit a HARQ ACK for HARQ ACK 2,3 P
-->
Note 1: Invalid MAC PDU is a MAC PDU that fails the CRC check.
Note 2: All DL MAC PDUs are transmitted with the NDI set on the PDCCH.
Note 3: Timer tolerances for the MAC DRX related timers measured in subframes or PDCCH subframes is 0. These
timers are: drx-InactivityTimer, drx-RetransmissionTimer, HARQ RTT Timer.
ETSI
Table 7.1.6.2.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 0A of table

7.1.6.2.3.2-1)

radioResourceConfigDedicated::= SEQUENCE {
explicitValue::= SEQUENCE {
maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
drx-InactivityTimer psf6
drx-RetransmissionTimer psf6
longDRX-CycleStartOffset CHOICE {
sf640 4
}
shortDRX Not present
}
}
timeAlignmentTimerDedicated infinity
phr-Config CHOICE {
release NULL
}
}
}
}
7.1.7 Transport block size selection

7.1.7.0 Specific configurations
The configurations defined in table 7.1.7.0-1 is used after step 7 of table 4.5.3.3-1 [18] in the preamble and in all steps
in the main behaviour of the test cases in clause 7.1.7.
Table 7.1.7.0-1: Power allocation for OFDM symbols and reference signals, single SS Tx antenna
Physical Channel EPRE Ratio Comment

PBCH PBCH_RA = 0 dB
PBCH_RB = 0 dB
PSS PSS_RA = 0 dB
SSS SSS_RA = 0 dB
PCFICH PCFICH_RB = 0 dB
PDCCH PDCCH_RA = 0 dB
PDCCH_RB = 0 dB
PDSCH PDSCH_RA = 0 dB
PDSCH_RB = 0 dB
PHICH PHICH_RB = 0 dB
The configurations defined in table 7.1.7.0-2 is used in step 8 of table 4.5.3.3-1 [18] in the preamble of the test cases in
clause 7.1.7.
ETSI
Table 7.1.7.0-2: PDSCH-ConfigDedicated-DEFAULT

PDSCH-ConfigDedicated-DEFAULT ::= SEQUENCE
{
p-a dB0 1TX
dB-3 2TX
}
7.1.7.1 DL-SCH transport block size selection

7.1.7.1.1 DL-SCH transport block size selection / DCI format 1 / RA type 0
(1)
ensure that {
when { UE on PDCCH receives DCI format 1 indicating Resource Allocation Type 0, a resource block
assignment correspondent to N PRB physical resource blocks and a modulation and coding scheme I MCS
}
then { UE decodes the received transport block of size correspondent to the read N PRB and I MCS
and forwards it to higher layers }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.212, clause 5.3.3.1.2; TS
36.213, clauses 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
DCI format 1 is used for the scheduling of one PDSCH codeword.
- Resource allocation header (resource allocation type 0 / type 1) – 1 bit as defined in section 7.1.6 of [3]
If downlink bandwidth is less than or equal to 10 PRBs, there is no resource allocation header and resource
allocation type 0 is assumed.
- Resource block assignment:
- For resource allocation type 0 as defined in section 7.1.6.1 of [3]:
⎡ DL
- N RB ⎤
/ P bits provide the resource allocation
...
where the value of P depends on the number of DL resource blocks as indicated in section 7.1.6 of [3]
- Modulation and coding scheme – 5 bits as defined in section 7.1.7 of [3]
If the number of information bits in format 1 is equal to that for format 0/1A, one bit of value zero shall be appended to
format 1.
If the number of information bits in format 1 belongs to one of the sizes in Table 5.3.3.1.2-1, one or more zero bit(s)
shall be appended to format 1 until the payload size of format 1 does not belong to one of the sizes in Table 5.3.3.1.2-1
and not equal to that of format 0/1A.
ETSI
Table 5.3.3.1.2-1: Ambiguous Sizes of Information Bits
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
[TS 36.213 clause 7.1.6.1]
In resource allocations of type 0, resource block assignment information includes a bitmap indicating the resource block
groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive physical resource blocks
(PRBs). Resource block group size (P) is a function of the system bandwidth as shown in Table 7.1.6.1-1. The total
DL
number of RBGs ( N RBG ) for downlink system bandwidth of N RB PRBs is given by N RBG = N RB
DL
⎡
/ P where ⎤
⎣N RB
DL
/ P⎦ DL
of the RBGs are of size P and if N RB mod P > 0 then one of the RBGs is of size N RB
DL
− P ⋅ N RB
DL
⎣ ⎦
/ P . The
bitmap is of size N RBG bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be
indexed in the order of increasing frequency and non-increasing RBG sizes starting at the lowest frequency. The order
of RBG to bitmap bit mapping is in such way that RBG 0 to RBG N RBG − 1 are mapped to MSB to LSB of the bitmap.
The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE
otherwise.
Table 7.1.6.1-1: Type 0 Resource Allocation RBG Size vs. Downlink System Bandwidth
System Bandwidth RBG Size

DL
N RB (P)
≤10 1
11 – 26 2
27 – 63 3
64 – 110 4
[TS 36.213 clause 7.1.7]
first
− read the 5-bit “modulation and coding scheme” field ( I MCS ) in the DCI
...
else
− set the Table 7.1.7.2.1-1 column indicator ′ to the total number of allocated PRBs based on the procedure
N PRB
defined in Section 7.1.6.
set the Table 7.1.7.2.1-1 column indicator { ′ × 0.75⎥⎦ , 1 ,

′ .
normal CP or configurations 0 and 4 with extended CP, shown in table 4.2-1 [3], there shall be no PDSCH transmission
in DwPTS of the special subframe.
[TS 36.213 clause 7.1.7.1]
ETSI
The UE shall use Q m = 2 if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI, otherwise, the UE shall
use I MCS and Table 7.1.7.1-1 to determine the modulation order ( Q m ) used in the physical downlink shared channel.
Table 7.1.7.1-1: Modulation and TBS index table for PDSCH
MCS Index Modulation Order TBS Index

I MCS Qm I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4 reserved
31 6
[TS 36.213 clause 7.1.7.2]
If the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then
- the UE shall set the TBS index ( I TBS ) equal to I MCS and determine its TBS by the procedure in Section
7.1.7.2.1.
...
else
- for 0 ≤ I MCS ≤ 28 , the UE shall first determine the TBS index ( I TBS ) using I MCS and Table 7.1.7.1-1 except if the
transport block is disabled in DCI formats 2 and 2A as specified below. For a transport block that is not mapped
to two-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.1. For a transport
block that is mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in Section
7.1.7.2.2.
- for 29 ≤ I MCS ≤ 31 , the TBS is assumed to be as determined from DCI transported in the latest PDCCH for the
same transport block using 0 ≤ I MCS ≤ 28 . If there is no latest PDCCH for the same transport block
ETSI
using 0 ≤ I MCS ≤ 28 , and if the initial PDSCH for the same transport block is semi-persistently scheduled, the
TBS shall be determined from the most recent semi-persistent scheduling assignment PDCCH.
- In DCI formats 2 and 2A a transport block is disabled if I MCS = 0 and if rvidx = 1 otherwise the transport block is
enabled.
The NDI and HARQ process ID, as signalled on PDCCH, and the TBS, as determined above, shall be delivered to
higher layers.
[TS 36.213 clause 7.1.7.2.1]
For 1 ≤ N PRB ≤ 110 , the TBS is given by the ( I TBS , N PRB ) entry of Table 7.1.7.2.1-1.
ETSI
Table 7.1.7.2.1-1: Transport block size table (dimension 27×110)
N PRB
I TBS
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
ETSI
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
ETSI
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
ETSI
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
ETSI
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
ETSI
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
[TS 36.306 clause 4.1]
The field ue-Category defines a combined uplink and downlink capability. The parameters set by the UE Category are
defined in subclause 4.2. Tables 4.1-1 and 4.1-2 define the downlink and, respectively, uplink physical layer parameter
values for each UE Category. A UE indicating category 6 or 7 shall also indicate category 4. A UE indicating category
8 shall also indicate category 5. A UE indicating category 9 shall also indicate category 6 and 4. A UE indicating
category 10 shall also indicate category 7 and 4. Table 4.1-4 defines the minimum capability for the maximum number
of bits of a MCH transport block received within a TTI for an MBMS capable UE.
Table 4.1-1: Downlink physical layer parameter values set by the field ue-Category
UE Category Maximum number of Maximum number Total number of Maximum number

DL-SCH transport of bits of a DL- soft channel bits of supported
block bits received SCH transport layers for spatial
within a TTI block received multiplexing in DL
within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
Category 6 301504 149776 (4 layers) 3654144 2 or 4
75376 (2 layers)
75376 (2 layers)
Category 8 2998560 299856 35982720 8
75376 (2 layers)
75376 (2 layers)
NOTE: In carrier aggregation operation, the DL-SCH processing capability can be shared by the UE with that
of MCH received from a serving cell. If the total eNB scheduling for DL-SCH and an MCH in one
serving cell at a given TTI is larger than the defined processing capability, the prioritization between
DL-SCH and MCH is left up to UE implementation.
Table 4.1-2: Uplink physical layer parameter values set by the field ue-Category
UE Category Maximum number of Maximum number Support for

bits of an UL-SCH of bits of an UL- 64QAM in UL
transport block SCH transport
transmitted within a block transmitted
TTI within a TTI
Category 1 5160 5160 No
Category 5 75376 75376 Yes
Category 7 102048 51024 No
Category 8 1497760 149776 Yes
Category 10 102048 51024 No
System Simulator:
- Cell 1.
ETSI
- Uplink and downlink bandwidth set to the maximum bandwidth for the E-UTRA Band under test as specified in
Table 5.6.1-1 in [31] (to enable testing of N PRB up to maximum value). For Band 18, Band 19 and Band 25,
based on industry requirement, uplink and downlink bandwidth set to 10MHz.
UE:
None.
Preamble:
Table 7.1.7.1.1.3.2-1: Maximum TBsize for different UE categories
UE Category Maximum number of

bits of a DL-SCH
transport block
received within a TTI
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776
Category 6 149776
Category 7 149776
Category 8 299856
Category 9 149776
Category 10 149776
ETSI
Table 7.1.7.1.1.3.2-2: Number of downlink PDCP SDUs and PDCP SDU size used as test data
TBsize Number of PDCP SDU size

[bits] PDCP SDUs [bits]
See note 1
104 ≤ TBsize ≤12096note 2 1 8*FLOOR((TBsize – 96)/8)
12097 ≤ TBsize ≤24128 2 8*FLOOR((TBsize – 128)/16))
24129 ≤ TBsize ≤ 36152 3 8*FLOOR((TBsize – 152)/24))
TBsize> 72240 7 8*FLOOR((TBsize – 264)/56))
Note 1. Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS
24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is
PDCP SDU size = (TBsize – N*PDCP header size - AMD PDU header size - MAC header size – Size of
Timing Advance – RLC Status PDU size) / N, where
PDCP header size is 16 bits for the RLC AM and 12-bit SN case;
AMD PDU header size is CIEL[(16+(N-1)*12)/8] bytes which includes 16 standard AM header and (N-1)
Length indicators; and
MAC header size = 40 bits as MAC header size can be

1) R/R/E/LCID MAC subheader (8 bits for Timing Advance) + R/R/E/LCID MAC subheader (16 bits for
MAC SDU for RLC Status PDU)R/R/E/LCID MAC subheader (8 bits for MAC SDU) = for AMD PDU 8 + 8
16+bits = 32 bits
Or
MAC SDU for AMD PDU, Note: Length can be of 2 bytes depending upon the size of AMD PDU)+
R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Status PDU) + = 8+24 + 8 bits = 40 bits
Therefore Maximum MAC header size can be 40 bits
Size of Timing Advance MAC CE is 8 bits (if no Timing Advance and/or RLC status needs to be sent,
padding will occur instead)
RLC Status PDU size = 16 bits
This gives:
PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CIEL((16+(N-1)*12)/8) – 64)/(8*N)) bits

Note 2: According to TS 36.213 Table 7.1.7.2.1-1 and the final PDCP SDU size formula in Note 1, the smallest
TBsize that can be tested is 104 bits.
Table 7.1.7.1.1.3.2-2a: Bandwidth Dependent Parameters
Max Bandwidth Max N PRB Allowed N PRB Values

10 Mhz 50 2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18, 20, 21, 23, 24, 26,
27, 29, 30, 32, 33, 35, 36, 38, 39, 41, 42, 44, 45, 47, 48,
50
15 Mhz 75 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32,
35, 36, 39, 40, 43, 44 ,47, 48, 51, 52, 55, 56, 59, 60, 63,
64, 67, 68, 71, 72, 75
20 Mhz 100 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64,
68, 72, 76, 80, 84, 88, 92, 96, 100
Note : Maximum bandwidth for EUTRA bands is 10/15/20 Mhz.
Table 7.1.7.1.1.3.2-2b: Ambiguous Sizes of Information Bits
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
ETSI

U–S Message
- EXCEPTION: Steps 1 to 4 are - - - -
repeated for allowed values of
N PRB as per table 7.1.7.1.1.3.2-
2a and I MCS from 0 to 28.
1 SS looks up I TBS in table 7.1.7.1- - - - -
1 in TS 36.213 based on the value
of I MCS . SS looks up TBsize in
table 7.1.7.2.1-1 in TS 36.213
based on values of N PRB and
I TBS .
performed if TBsize is less than or
equal to UE capability “Maximum
number of DL-SCH transport
block bits received within a TTI”
as specified in Table 7.1.7.1.1.3.2-
1 and larger than or equal to 104
bits as specified in Table
7.1.7.1.1.3.2-2, and the effective
channel code rate, as defined in
TS 36.213 clause 7.1.7, is lower
than or equal to 0.930.
2 SS creates one or more PDCP - - - -
SDUs, depending on TBsize, in
accordance with Table
7.1.7.1.1.3.2-2.
3 SS transmits the PDCP SDUs <-- MAC PDU (NxPDCP - -
concatenated into a MAC PDU SDUs)
and indicates on PDCCH DCI DCI: (DCI Format 1, RA
Format 1 with RA type 0 and a type 0, RBA( N PRB ), I MCS )
resource block assignment (RBA)
correspondent to N PRB as
specified in 7.1.6.1 in TS 36.213
and modulation and coding
scheme I MCS .
If the number of information bits in

format 1 is equal to that for format
0/1A, one bit of value zero shall
be appended to format 1 by the
SS.

format 1 belongs to one of the
sizes in Table 7.1.7.1.1.3.2-2b,
one or more zero bit(s) shall be
appended to format 1 by the SS
until the payload size of format 1
does not belong to one of the
sizes in Table 7.1.7.1.1.3.2-2b
and not equal to that of format
0/1A.
3A At the reception of scheduling <-- (UL Grant) - -
request the SS transmits UL Grant
for transmitting loop back PDCP
SDUs.
4 CHECK: Does UE return the --> (NxPDCP SDUs) 1 P
same number of PDCP SDUs with
same content as transmitted by
ETSI
the SS in step 3?
Table 7.1.7.1.1.3.3.1: MAC-MainConfig-RBC (preamble Table 4.5.3.3-1 [18]: Step 8)
Derivation Path: 36.508 Table 4.8.2.1.5-1

retxBSR-Timer sf320
Table 7.1.7.1.1.3.3-2: UECapabilityInformation (Preamble Table 4.5.2.3-1 [18]: Step 13)

UECapabilityInformation ::= SEQUENCE {
c1 CHOICE{
ueCapabilityInformation-r8 SEQUENCE {
ue-CapabilityRAT-ContainerList SEQUENCE 1 entry
(SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {
ueCapabilityRAT-Container
ue-EUTRA-Capability SEQUENCE {
ue-Category Checked against UE
Category indications in
the PICS
}
}
}
}
}
}
7.1.7.1.2 DL-SCH transport block size selection / DCI format 1 / RA type 1

(1)
ensure that {
when { UE on PDCCH receives DCI format 1 indicating Resource Allocation Type 1, a resource block
assignment correspondent to N PRB physical resource blocks and a modulation and coding scheme I MCS
}
}
36.213, clauses 7.1.6.2, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
DCI format 1 is used for the scheduling of one PDSCH codeword.
ETSI
- For resource allocation type 1 as defined in section 7.1.6.2 of [3]:
- ⎡log 2 (P )⎤ bits of this field are used as a header specific to this resource allocation type to indicate the
selected resource blocks subset
- 1 bit indicates a shift of the resource allocation span
(⎡DL
- N RB ⎤
/ P − ⎡log 2 (P )⎤ − 1) bits provide the resource allocation
where the value of P depends on the number of DL resource blocks as indicated in section 7.1.6 of [3]
If the number of information bits in format 1 is equal to that for format 0/1A, one bit of value zero shall be appended to
format 1.
If the number of information bits in format 1 belongs to one of the sizes in Table 5.3.3.1.2-1, one or more zero bit(s)
shall be appended to format 1 until the payload size of format 1 does not belong to one of the sizes in Table 5.3.3.1.2-1
and not equal to that of format 0/1A.
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

[TS 36.213 clause 7.1.6.2]
In resource allocations of type 1, a resource block assignment information of size N RBG indicates to a scheduled UE
the PRBs from the set of PRBs from one of P RBG subsets. Also P is the RBG size associated with the system
bandwidth as shown in Table 7.1.6.1-1. A RBG subset p , where 0 ≤ p < P , consists of every P th RBG starting
from RBG p . The resource block assignment information consists of three fields [4].
The first field with ⎡log 2 ( P)⎤ bits is used to indicate the selected RBG subset among P RBG subsets.
The second field with one bit is used to indicate a shift of the resource allocation span within a subset. A bit value of 1
indicates shift is triggered. Shift is not triggered otherwise.
The third field includes a bitmap, where each bit of the bitmap addresses a single PRB in the selected RBG subset in
such a way that MSB to LSB of the bitmap are mapped to the PRBs in the increasing frequency order. The PRB is
allocated to the UE if the corresponding bit value in the bit field is 1, the PRB is not allocated to the UE otherwise. The
TYPE1
portion of the bitmap used to address PRBs in a selected RBG subset has size N RB and is defined as
TYPE1
N RB ⎡
= N RB
DL
/P ⎤ − ⎡log 2 ( P )⎤ − 1
The addressable PRB numbers of a selected RBG subset start from an offset, Δ shift ( p) to the smallest PRB number
within the selected RBG subset, which is mapped to the MSB of the bitmap. The offset is in terms of the number of
PRBs and is done within the selected RBG subset. If the value of the bit in the second field for shift of the resource
allocation span is set to 0, the offset for RBG subset p is given by Δ shift ( p ) = 0 . Otherwise, the offset for RBG
subset p is given by Δ shift ( p ) = N RB
RBG subset
( p ) − N RB
TYPE1
, where the LSB of the bitmap is justified with the highest
RBG subset
PRB number within the selected RBG subset. N RB ( p) is the number of PRBs in RBG subset p and can be
calculated by the following equation,
ETSI
⎧ ⎢ N RB
DL
− 1⎥ DL
⎢ N RB − 1⎥
⎪⎢ 2 ⎥⋅P +P ,p< ⎢ ⎥ mod P
⎪⎣ P ⎦ ⎣ P ⎦
⎪
⎪ ⎢ N RB − 1⎥ − 1⎥
DL DL
⎢ N RB
RBG subset
N RB ( p) = ⎨⎢ 2 ⎥⋅P + ( N RB
DL
− 1) mod P + 1 ,p=⎢ ⎥ mod P
⎪ ⎣ P ⎦ ⎣ P ⎦
⎪
⎢ N RB − 1⎥ − 1⎥
DL DL
⎢ N RB
⎪
⎢ ⎥⋅P ,p>⎢ ⎥ mod P
⎪⎣ P 2 ⎦ ⎣ P ⎦
⎩
Consequently, when RBG subset p is indicated, bit i for i = 0,1, L, N TYPE1

RB − 1 in the bitmap field indicates PRB
number,
⎢ i + Δ shift ( p) ⎥ 2
( p) = ⎢ ⎥ P + p ⋅ P + (i + Δ shift ( p) ) mod P
RBG subset
nPRB
⎣ P ⎦
[TS 36.213 clause 7.1.7]
first
...
else
N PRB

′ .
[TS 36.213 clause 7.1.7.1]
ETSI

I MCS Qm I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4 reserved
31 6
[TS 36.213 clause 7.1.7.2]
− for DCI format 1A:
o the UE shall set the TBS index ( I TBS ) equal to I MCS and determine its TBS by the procedure in
Section 7.1.7.2.1.
...
else
− for 0 ≤ I MCS ≤ 28 , the UE shall first determine the TBS index ( I TBS ) using I MCS and Table 7.1.7.1-1 except if
the transport block is disabled in DCI formats 2 and 2A as specified below. For a transport block that is not
mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.1. For a
transport block that is mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in
Section 7.1.7.2.2.
− for 29 ≤ I MCS ≤ 31 , the TBS is assumed to be as determined from DCI transported in the latest PDCCH for the
ETSI
− In DCI formats 2 and 2A a transport block is disabled if I MCS = 0 and if rvidx = 1 otherwise the transport block
is enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
ETSI
N PRB
I TBS
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
ETSI
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
ETSI
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
ETSI
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
ETSI
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
ETSI
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
[TS 36.306 clause 4.1]
The field ue-Category parameter defines a combined uplink and downlink capability. The parameters set by the UE
Category are defined in subclause 4.2. Tables 4.1-1 and 4.1-2 define the downlink and, respectively, uplink physical
layer parameter values for each UE Category. A UE indicating category 6 or 7 shall also indicate category 4. A UE
indicating category 8 shall also indicate category 5. A UE indicating category 9 shall also indicate category 6 and 4. A
UE indicating category 10 shall also indicate category 7 and 4. Table 4.1-4 defines the minimum capability for the
maximum number of bits of a MCH transport block received within a TTI for an MBMS capable UE.

within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
75376 (2 layers)
75376 (2 layers)
Category 8 2998560 299856 35982720 8
75376 (2 layers)
75376 (2 layers)
ETSI

TTI within a TTI
Category 7 102048 51024 No
Category 8 1497760 149776 Yes
Category 10 102048 51024 No
System Simulator:
- Cell 1.
UE:
None.
Preamble:

bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776
Category 6 149776
Category 7 149776
Category 8 299856
Category 9 149776
Category 10 149776
ETSI

See note 1
104 ≤ TBsize ≤12096 1 8*FLOOR((TBsize - 96)/8)
note 2
48185 ≤ TBsize ≤60208 5 8*FLOOR((TBsize - 208)/40))
Note 1: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS
24.301 clause 9.9.4.12).
PDCP SDU size = (TBsize – N*PDCP header size - AMD PDU header size - MAC header size – Size of
MAC header size = 40 bits as MAC header can be
R/R/E/LCID MAC subheader (8 bits for Timing Advance) + R/R/E/LCID MAC subheader (16 bits for MAC
SDU for RLC Status PDU) +R/R/E/LCID MAC subheader (8 bits for MAC SDU for AMD PDU) = 8 + 16+ 8
bits = 32 bits
OR
SDU for AMD PDU, Note: Length can be 2 bytes depending on the size of AMD PDU) +R/R/E/LCID MAC
subheader (8 bits for MAC SDU for RLC Status PDU) = 8 + 24+ 8 bits = 40 bits
Therefore maximum MAC header size can be 40 bits
This gives:
PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CIEL((16+(N-1)*12)/8) – 64)/(8*N)) bits

Max Bandwidth TYPE1

Max N PRB N RB
10 Mhz 50 14
15 Mhz 75 16
20 Mhz 100 22
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U–S Message
ETSI
repeated for values of N PRB from

TYPE1
1 to N RB as per table
7.1.7.1.2.3.2-2a and I MCS from 0
to 28.
table 7.1.7.2.1-1 in TS 36.213
I TBS .
7.1.7.1.2.3.2-2.
and indicates on PDCCH DCI DCI: (DCI Format 1, RA
Format 1 with RA type 1 and a type 1, RBA( N PRB ), I MCS )
resource block assignment (RBA)
scheme I MCS .

format 1 is equal to that for format
0/1A, one bit of value zero shall
be appended to format 1 by the
SS.

format 1 belongs to one of the
one or more zero bit(s) shall be
appended to format 1 by the SS
until the payload size of format 1
does not belong to one of the
sizes in Table 7.1.7.1.2.3.2-2b
and not equal to that of format
0/1A.
3A At the reception of scheduling <-- (UL Grant)
SDUs.
the SS in step 3?
ETSI

retxBSR-Timer sf320

c1 CHOICE{
the PICS
}
}
}
}
}
}
7.1.7.1.3 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Localised
VRB
(1)
ensure that {
when { UE on PDCCH receives DCI format 1A indicating Resource Allocation Type 2 with Localized
VRB, a resource block assignment correspondent to N PRB physical resource blocks and a modulation
and coding scheme I MCS }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.212, clauses 5.3.3.1.2 and
5.3.3.1.3; TS 36.213, clauses 7.1.6.3, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
[TS 36.212 clause 5.3.3.1.3]
ETSI
DCI format 1A is used for the compact scheduling of one PDSCH codeword and random access procedure initiated by a
PDCCH order.
Otherwise,
- Localized/Distributed VRB assignment flag – 1 bit as defined in 7.1.6.3 of [3]
⎡ DL
- Resource block assignment – log 2 ( N RB DL
( N RB ⎤
+ 1) / 2) bits as defined in section 7.1.6.3 of [3]:
- For localized VRB:
⎡log 2 ( N RBDL ( N RBDL + 1) / 2)⎤ bits provide the resource allocation

- For distributed VRB:
DL
- If N RB < 50 or if the format 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI
⎡ DL
- log 2 ( N RB DL
( N RB ⎤
+ 1) / 2) bits provide the resource allocation
- Else
- 1 bit, the MSB indicates the gap value, where value 0 indicates N gap = N gap,1 and value 1 indicates
N gap = N gap,2
⎡ DL
- ( log 2 ( N RB DL
( N RB + 1) / 2) ⎤ − 1) bits provide the resource allocation
- Modulation and coding scheme – 5bits as defined in section 7.1.7 of [3]
If the number of information bits in format 1A is less than that of format 0, zeros shall be appended to format 1A until
the payload size equals that of format 0.
If the number of information bits in format 1A belongs to one of the sizes in Table 5.3.3.1.2-1, one zero bit shall be
appended to format 1A.
...
[TS 36.213 clause 7.1.6.3]
In resource allocations of type 2, the resource block assignment information indicates to a scheduled UE a set of
contiguously allocated localized virtual resource blocks or distributed virtual resource blocks. In case of resource
allocation signalled with PDCCH DCI format 1A, 1B or 1D, one bit flag indicates whether localized virtual resource
blocks or distributed virtual resource blocks are assigned (value 0 indicates Localized and value 1 indicates Distributed
VRB assignment) while distributed virtual resource blocks are always assigned in case of resource allocation signalled
with PDCCH DCI format 1C. Localized VRB allocations for a UE vary from a single VRB up to a maximum number
of VRBs spanning the system bandwidth. For DCI format 1A the distributed VRB allocations for a UE vary from a
DL DL
single VRB up to N VRB VRBs, where N VRB is defined in [3], if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or
SI-RNTI. With PDCCH DCI format 1B, 1D, or 1A with a CRC scrambled with C-RNTI, distributed VRB allocations
DL DL DL
for a UE vary from a single VRB up to N VRB VRBs if N RB is 6-49 and vary from a single VRB up to 16 if N RB is 50-
step
110. With PDCCH DCI format 1C, distributed VRB allocations for a UE vary from N RB VRB(s) up to
⎣N VRB / N RB ⎦ ⋅ N RB VRBs with an increment step of N RB , where N RB value is determined depending on the downlink
DL step step step step
system bandwidth as shown in Table 7.1.6.3-1.
ETSI
Table 7.1.6.3-1: N RB
step
values vs. Downlink System Bandwidth
System BW step
N RB
DL
(N RB ) DCI format 1C
6-49 2
50-110 4
For PDCCH DCI format 1A, 1B or 1D, a type 2 resource allocation field consists of a resource indication value (RIV)
corresponding to a starting resource block ( RBstart ) and a length in terms of virtually contiguously allocated resource
blocks LCRBs . The resource indication value is defined by
if ( LCRBs − 1) ≤ ⎣N RB
DL
/ 2⎦ then
RIV = N RB
DL
( LCRBs − 1) + RB start
else
RIV = N RB
DL DL
( N RB − LCRBs + 1) + ( N RB
DL
− 1 − RB start )
where LCRBs ≥ 1 and shall not exceed

DL
N VRB − RBstart .
For PDCCH DCI format 1C, a type 2 resource block assignment field consists of a resource indication value (RIV)
step
corresponding to a starting resource block ( RBstart = 0 , N RB step
, 2N RB ,…, ( ⎣N VRB
DL step
/ N RB ⎦ − 1) N RBstep ) and a length in terms
step
of virtually contiguously allocated resource blocks ( LCRBs = N RB step
, 2N RB ,…, ⎣N VRB
DL step
/ N RB ⎦ ⋅ N RBstep ). The resource
indication value is defined by
if ′ − 1) ≤ ⎣NVRB
( LCRBs ′ DL / 2⎦ then
′ DL ( LCRBs
RIV = NVRB ′ − 1) + RBstart
′
else
′ DL ( NVRB
RIV = NVRB ′ DL − LCRBs
′ + 1) + ( NVRB
′ DL − 1 − RBstart
′ )
where ′ = LCRBs / N RB
LCRBs step
′ = RBstart / N RB
, RBstart
step
′ DL = ⎣NVRB
and NVRB
DL step
/ N RB ⎦. Here,
′ ≥ 1 and shall not exceed NVRB
LCRBs ′ DL − RBstart
′ .
[TS 36.213 clause 7.1.7]
first
...
else
N PRB
ETSI

′ .
[TS 36.213 clause 7.1.7.1]

I MCS Qm I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4 reserved
31 6
[TS 36.213 clause 7.1.7.2]
7.1.7.2.1.
ETSI
...
else
− for 0 ≤ I MCS ≤ 28 , the UE shall first determine the TBS index ( I TBS ) using I MCS and Table 7.1.7.1-1 except if
the transport block is disabled in DCI formats 2 and 2A as specified below. For a transport block that is not
mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.1. For a
transport block that is mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in
Section 7.1.7.2.2.
− for 29 ≤ I MCS ≤ 31 , the TBS is assumed to be as determined from DCI transported in the latest PDCCH for the
− In DCI formats 2 and 2A a transport block is disabled if I MCS = 0 and if rvidx = 1 otherwise the transport block
is enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
ETSI
N PRB
I TBS
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
ETSI
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
ETSI
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
ETSI
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
ETSI
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
ETSI
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
[TS 36.306 clause 4.1]

within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
75376 (2 layers)
75376 (2 layers)
Category 8 2998560 299856 35982720 8
75376 (2 layers)
75376 (2 layers)

TTI within a TTI
Category 7 102048 51024 No
Category 8 1497760 149776 Yes
Category 10 102048 51024 No
ETSI
System Simulator:
- Cell 1.
UE:
None.
Preamble:

bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776
Category 6 149776
Category 7 149776
Category 8 299856
Category 9 149776
Category 10 149776
ETSI

See note 1
note 2
24.301 clause 9.9.4.12).
PDCP SDU size = (TBsize – N*PDCP header size -AMD PDU header size - MAC header size – Size of

SDU for RLC Status PDU) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for AMD PDU) = 8 + 16+ 8
bits = 32 bits
Or
SDU for AMD PDU, Note: Length can be 2 bytes depending on the size of AMD PDU) +R/R/E/LCID MAC
subheader (8 bits for MAC SDU for RLC Status PDU) = 8 + 24+ 8 bits = 40 bits
This gives:
PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CIEL((16+(N-1)*12)/8) – 64)/(8*N)) bits.

Max Bandwidth Max N PRB

10 Mhz 50
15 Mhz 75
20 Mhz 100
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U–S Message
ETSI

1 to Max N PRB as per table
7.1.7.1.3.3.2-2a and I MCS from 0
to 28.
table 7.1.7.2.1-1 in TS 36.213
I TBS .
7.1.7.1.3.3.2-2.
and indicates on PDCCH DCI DCI: (DCI Format 1A, RA
Format 1A with RA type 2 using type 2,
Localized VRB and a resource Localized/Distributed VRB
block assignment (RBA) assignment flag =’0’,
correspondent to N PRB as RBA( N PRB ), I MCS )
scheme I MCS .

format 1A is less than that of
format 0, zeros shall be appended
by the SS to format 1A until the
payload size equals that of format
0.

format 1A belongs to one of the
one zero bit shall be appended by
the SS to format 1A.
SDUs.
the SS in step 3?
ETSI

retxBSR-Timer sf320

c1 CHOICE{
accessStratumRelease Any allowed value
the PICS
pdcp-Parameters Any allowed value
phyLayerParameters Any allowed value
rf-Parameters Any allowed value
measParameters Any allowed value
featureGroupIndicators Any allowed value
interRAT-Parameters Any allowed value
nonCriticalExtension Any allowed value
}
}
}
}
}
}
7.1.7.1.4 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Distributed
VRB
(1)
ensure that {
when { UE on PDCCH receives DCI format 1A indicating Resource Allocation Type 2 with Distributed
VRB, a resource block assignment correspondent to N PRB physical resource blocks and a modulation
and coding scheme I MCS }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.212, clauses 5.3.3.1.2 and
5.3.3.1.3; TS 36.213, clauses 7.1.6.3, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
ETSI
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
[TS 36.212 clause 5.3.3.1.3]
DCI format 1A is used for the compact scheduling of one PDSCH codeword and random access procedure initiated by a
PDCCH order.
Otherwise,
- Localized/Distributed VRB assignment flag – 1 bit as defined in 7.1.6.3 of [3]
⎡ DL
- Resource block assignment – log 2 ( N RB DL
( N RB ⎤
+ 1) / 2) bits as defined in section 7.1.6.3 of [3]:
- For localized VRB:
⎡log 2 ( N RBDL ( N RBDL + 1) / 2)⎤ bits provide the resource allocation

- For distributed VRB:
DL
- If N RB < 50 or if the format 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI
⎡ DL
- log 2 ( N RB DL
( N RB ⎤
+ 1) / 2) bits provide the resource allocation
- Else
- 1 bit, the MSB indicates the gap value, where value 0 indicates N gap = N gap,1 and value 1 indicates
N gap = N gap,2
⎡ DL
- ( log 2 ( N RB DL
( N RB + 1) / 2) ⎤ − 1) bits provide the resource allocation
- Modulation and coding scheme – 5bits as defined in section 7.1.7 of [3]
If the number of information bits in format 1A is less than that of format 0, zeros shall be appended to format 1A until
the payload size equals that of format 0.
...
[TS 36.213 clause 7.1.6.3]
In resource allocations of type 2, the resource block assignment information indicates to a scheduled UE a set of
contiguously allocated localized virtual resource blocks or distributed virtual resource blocks. In case of resource
allocation signalled with PDCCH DCI format 1A, 1B or 1D, one bit flag indicates whether localized virtual resource
blocks or distributed virtual resource blocks are assigned (value 0 indicates Localized and value 1 indicates Distributed
VRB assignment) while distributed virtual resource blocks are always assigned in case of resource allocation signalled
with PDCCH DCI format 1C. Localized VRB allocations for a UE vary from a single VRB up to a maximum number
of VRBs spanning the system bandwidth. For DCI format 1A the distributed VRB allocations for a UE vary from a
DL DL
single VRB up to N VRB VRBs, where N VRB is defined in [3], if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or
SI-RNTI. With PDCCH DCI format 1B, 1D, or 1A with a CRC scrambled with C-RNTI, distributed VRB allocations
DL DL DL
for a UE vary from a single VRB up to N VRB VRBs if N RB is 6-49 and vary from a single VRB up to 16 if N RB is 50-
ETSI
step
110. With PDCCH DCI format 1C, distributed VRB allocations for a UE vary from N RB VRB(s) up to
⎣ VRB RB ⎦ RB
N DL
/ N step
⋅ N step
VRBs with an increment step of N step
RB
, where N step
RB
value is determined depending on the downlink
system bandwidth as shown in Table 7.1.6.3-1.
Table 7.1.6.3-1: N RB
step
values vs. Downlink System Bandwidth
System BW step
N RB
DL
(N RB ) DCI format 1C
6-49 2
50-110 4
For PDCCH DCI format 1A, 1B or 1D, a type 2 resource allocation field consists of a resource indication value (RIV)
corresponding to a starting resource block ( RBstart ) and a length in terms of virtually contiguously allocated resource
blocks LCRBs . The resource indication value is defined by
if ( LCRBs − 1) ≤ ⎣N RB
DL
/ 2⎦ then
RIV = N RB
DL
( LCRBs − 1) + RB start
else
RIV = N RB
DL DL
( N RB − LCRBs + 1) + ( N RB
DL
− 1 − RB start )
where LCRBs ≥ 1 and shall not exceed

DL
N VRB − RBstart .
For PDCCH DCI format 1C, a type 2 resource block assignment field consists of a resource indication value (RIV)
step
corresponding to a starting resource block ( RBstart = 0 , N RB step
, 2N RB ,…, ( ⎣N VRB
DL step
/ N RB ⎦ − 1) N RBstep ) and a length in terms
step
of virtually contiguously allocated resource blocks ( LCRBs = N RB step
, 2N RB ,…, ⎣N VRB
DL step
/ N RB ⎦ ⋅ N RBstep ). The resource
indication value is defined by
if ′ − 1) ≤ ⎣NVRB
( LCRBs ′ DL / 2⎦ then
′ DL ( LCRBs
RIV = NVRB ′ − 1) + RBstart
′
else
′ DL ( NVRB
RIV = NVRB ′ DL − LCRBs
′ + 1) + ( NVRB
′ DL − 1 − RBstart
′ )
where ′ = LCRBs / N RB
LCRBs step
′ = RBstart / N RB
, RBstart
step
′ DL = ⎣NVRB
and NVRB
DL step
/ N RB ⎦. Here,
′ ≥ 1 and shall not exceed NVRB
LCRBs ′ DL − RBstart
′ .
[TS 36.213 clause 7.1.7]
first
...
else
ETSI
N PRB

′ .
[TS 36.213 clause 7.1.7.1]

I MCS Qm I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4 reserved
31 6
[TS 36.213 clause 7.1.7.2]
ETSI
7.1.7.2.1.
...
else
7.1.7.2.2.
enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
ETSI
N PRB
I TBS
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
ETSI
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
ETSI
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
ETSI
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
ETSI
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
ETSI
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
[TS 36.306 clause 4.1]

within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
75376 (2 layers)
75376 (2 layers)
Category 8 2998560 299856 35982720 8
75376 (2 layers)
75376 (2 layers)

TTI within a TTI
Category 7 102048 51024 No
Category 8 1497760 149776 Yes
Category 10 102048 51024 No
ETSI
System Simulator:
- Cell 1.
- DCI format 1C shall be used for BCCH, PCH and RAR (note).
UE:
None.
Preamble:
NOTE: To maximize resources for DL-SCH TB size testing for DCI format 1A/RA type 2/Distributed VRB then
the SS need to use DCI Format 1C for BCCH, PCH and RAR

bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776
Category 6 149776
Category 7 149776
Category 8 299856
Category 9 149776
Category 10 149776
ETSI

See note 1
note 2
24.301 clause 9.9.4.12).
PDCP SDU size = (TBsize – N*PDCP header size - AMD PDU header size - MAC header size –
Size of Timing Advance – RLC Status PDU size) / N, where
AMD PDU header size is CIEL[(16+(N-1)*12)/8] bytes which includes 16 standard AM header
and (N-1) Length indicators; and
R/R/E/LCID MAC subheader (8 bits for Timing Advance) + R/R/E/LCID MAC subheader (16 bits
for MAC SDU for RLC Status PDU) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for
AMD PDU) = 8 + 16 + 8 bits = 32 bits
OR
R/R/E/LCID MAC subheader (8 bits for Timing Advance) + R/R/E/LCID MAC subheader (24 bits
for MAC SDU for AMD PDU, Note: Length can be 2 bytes depending on the size of AMD PDU)
+R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Status PDU) = 8 + 24+ 8 bits = 40
bits

This gives:
PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CIEL((16+(N-1)*12)/8) – 64)/(8*N)) bits.

Max Bandwidth Max N PRB MAX VRB

10 Mhz 50 16
15 Mhz 75 16
20 Mhz 100 16
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U–S Message
ETSI

1 to 16[MAX VRB] and I MCS from
0 to 28.
table 7.1.7.2.1-1 in TS 36.213
I TBS .
TS 36.213 clause 7.1.7 is lower
7.1.7.1.4.3.2-2.
and indicates on PDCCH DCI DCI: (DCI Format 1A, RA
Format 1A with RA type 2 using type 2,
Distributed VRB and a resource Localized/Distributed VRB
block assignment (RBA) assignment flag =’1’,
correspondent to N PRB as RBA( N PRB ), I MCS )
scheme I MCS .

format 1A is less than that of
format 0, zeros shall be appended
by the SS to format 1A until the
payload size equals that of format
0.

format 1A belongs to one of the
one zero bit shall be appended by
the SS to format 1A.
SDUs.
the SS in step 3?
ETSI

retxBSR-Timer sf320

c1 CHOICE{
the PICS
}
}
}
}
}
}
7.1.7.1.5 DL-SCH transport block size selection / DCI format 2A / RA type 0 / Two
transport blocks enabled / Transport block to codeword swap flag value set to ’0’
(1)
ensure that {
when { UE has two transport blocks enabled and on PDCCH receives DCI format 2A indicating Resource
Allocation Type 0, a resource block assignment correspondent to N PRB physical resource blocks, the
Transport block to codeword swap flag value set to ’0’ and a modulation and coding scheme I MCS for
two transport blocks }
then { UE decodes the received transport blocks of sizes correspondent to the read N PRB and
I MCS for transport block 1 and I MCS for transport block 2 and forwards it to higher layers }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.212, clauses 5.3.3.1.2,
5.3.3.1.5 and 5.3.3.1.5A; TS 36.213, clauses 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.7.2.1 and 7.1.7.2.2; and TS 36.306
clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
[TS 36.212 clause 5.3.3.1.5]
ETSI
Table 5.3.3.1.5-1: Transport block to codeword mapping

(two transport blocks enabled)
transport block
codeword 0 codeword 1
to codeword
(enabled) (enabled)
swap flag value
0 transport block 1 transport block 2

(one transport block enabled)
Transport block 1 transport block 2
(enabled) (disabled)
transport
enabled disabled -
block 1
transport
disabled enabled -
block 2
[TS 36.212 clause 5.3.3.1.5A]
- For resource allocation type 0 as defined in section 7.1.6.1 of [3]
⎡ DL
- N RB ⎤
/ P bits provide the resource allocation
...
where the value of P depends on the number of DL resource blocks as indicated in subclause [7.1.6.1] of [3]
...
- Transport block to codeword swap flag – 1 bit
- Redundancy version – 2 bits
...
Precoding information – number of bits as specified in Table 5.3.3.1.5A-1
If both transport blocks are enabled, the transport block to codeword mapping is specified according to Table
5.3.3.1.5-1.
ETSI
In case one of the transport blocks is disabled, the transport block to codeword swap flag is reserved and the transport
block to codeword mapping is specified according to Table 5.3.3.1.5-2.
The precoding information field is defined according to Table 5.3.3.1.5A-2. For a single enabled codeword, index 1 in
Table 5.3.3.1.5A-2 is only supported for retransmission of the corresponding transport block if that transport block has
previously been transmitted using two layers with open-loop spatial multiplexing.
For transmission with 2 antenna ports, the precoding information field is not present. The number of transmission layers
is equal to 2 if both codewords are enabled; transmit diversity is used if codeword 0 is enabled while codeword 1 is
disabled.
Table 5.3.3.1.5A-1: Number of bits for precoding information
Number of antenna ports at eNodeB Number of bits for precoding information

2 0
4 2
Table 5.3.3.1.5A-2: Content of precoding information field for 4 antenna ports
Codeword 0 enabled, Codeword 0 enabled,

Bit field Bit field
mapped to Message mapped Message
index to index
0 4 layers: Transmit 0 2 layers: precoder
diversity cycling with large delay
CDD
1 2 layers: precoder 1 3 layers: precoder
cycling with large delay cycling with large delay
CDD CDD
2 reserved 2 4 layers: precoder
cycling with large delay
CDD
3 reserved 3 reserved
[TS 36.213 clause 7.1.6.1]
DL
DL
⎡
/ P where ⎤
⎣N RB
DL
/ P⎦ DL
DL
− P ⋅ N RB
DL
⎣ ⎦
/ P . The
otherwise.
ETSI

DL
N RB (P)
≤10 1
11 – 26 2
27 – 63 3
64 – 110 4
[TS 36.213 clause 7.1.7]
first
...
else
- set the Table 7.1.7.2.1-1 column indicator ′ to the total number of allocated PRBs based on the procedure
N PRB

′ .
[TS 36.213 clause 7.1.7.1]
ETSI

I MCS Qm I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4 reserved
31 6
[TS 36.213 clause 7.1.7.2]
7.1.7.2.1.
...
else
7.1.7.2.2.
ETSI
enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
ETSI
N PRB
I TBS
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
ETSI
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
ETSI
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
ETSI
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
ETSI
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
ETSI
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
[TS 36.213 clause 7.1.7.2.2]
For 1 ≤ N PRB ≤ 55 , the TBS is given by the ( I TBS , 2 ⋅ N PRB ) entry of Table 7.1.7.2.1-1.
For 56 ≤ N PRB ≤ 110 , a baseline TBS_L1 is taken from the ( I TBS , N PRB ) entry of Table 7.1.7.2.1-1, which is then
translated into TBS_L2 using the mapping rule shown in Table 7.1.7.2.2-1. The TBS is given by TBS_L2.
Table 7.1.7.2.2-1: One-layer to two-layer TBS translation table
TBS_L1 TBS_L2 TBS_L1 TBS_L2 TBS_L1 TBS_L2 TBS_L1 TBS_L2

1544 3112 3752 7480 10296 20616 28336 57336
1608 3240 3880 7736 10680 21384 29296 59256
1672 3368 4008 7992 11064 22152 30576 61664
1736 3496 4136 8248 11448 22920 31704 63776
1800 3624 4264 8504 11832 23688 32856 66592
1864 3752 4392 8760 12216 24496 34008 68808
1928 3880 4584 9144 12576 25456 35160 71112
1992 4008 4776 9528 12960 25456 36696 73712
2024 4008 4968 9912 13536 27376 37888 76208
2088 4136 5160 10296 14112 28336 39232 78704
2152 4264 5352 10680 14688 29296 40576 81176
2216 4392 5544 11064 15264 30576 42368 84760
2280 4584 5736 11448 15840 31704 43816 87936
2344 4776 5992 11832 16416 32856 45352 90816
2408 4776 6200 12576 16992 34008 46888 93800
2472 4968 6456 12960 17568 35160 48936 97896
2536 5160 6712 13536 18336 36696 51024 101840
2600 5160 6968 14112 19080 37888 52752 105528
2664 5352 7224 14688 19848 39232 55056 110136
2728 5544 7480 14688 20616 40576 57336 115040
2792 5544 7736 15264 21384 42368 59256 119816
2856 5736 7992 15840 22152 43816 61664 124464
2984 5992 8248 16416 22920 45352 63776 128496
3112 6200 8504 16992 23688 46888 66592 133208
3240 6456 8760 17568 24496 48936 68808 137792
3368 6712 9144 18336 25456 51024 71112 142248
3496 6968 9528 19080 26416 52752 73712 146856
3624 7224 9912 19848 27376 55056 75376 149776
[TS 36.306 clause 4.1]
ETSI

within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
75376 (2 layers)
75376 (2 layers)
Category 8 2998560 299856 35982720 8
75376 (2 layers)
75376 (2 layers)

TTI within a TTI
Category 7 102048 51024 No
Category 8 1497760 149776 Yes
Category 10 102048 51024 No
...
System Simulator
- Cell 1.
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] condition 2TX to configure MIMO.
ETSI

bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776
Category 6 149776
Category 7 149776
Category 8 299856
Category 9 149776
Category 10 149776
ETSI
Table 7.1.7.1.5.3.2-2: Number of downlink PDCP SDUs and PDCP SDU size used as test data for
transport block 1 and transport block 2
Total TBsize (sum of the sizes of TBsize#1 and TBsize#2) Number of PDCP SDU size
(bits) PDCP SDUs (bits]
See note 1
136 ≤ TBsize ≤ 12120 See note 2 1 8*FLOOR((TBsize - 120)/8)
48209 ≤ TBsize ≤ 60232 5 8*FLOOR((TBsize - 232/40))
TBsize ≥ 144433 13 8*FLOOR((TBsize – 456)/104))
24.301 clause 9.9.4.12).
PDCP SDU size = (Total TBsize –N*PDCP header size - AMD PDU header size - - MAC header size –
Size of Timing Advance– RLC Status PDU size) / N, where
AMD PDU header size is CEIL[(Number of TBs *16+(N-1)*12)/8] bytes which includes one 16 bit standard
AM header per TB and N-1 Length indicators of 12 bits corresponding to the worst case when one of the
PDCP SDU is split between the two transport blocks. If no PDCP SDU is split between the transport blocks
then there will be only N-2 LIs and MAC padding will occur instead of one LI;
MAC header size = R/R/E/LCID MAC subheader (8 bits for Timing Advance) + R/R/E/LCID MAC
subheader (24 bits for MAC SDU for RLC data PDU)+ Number of TBs R/R/E/LCID MAC subheaders (8
bits for MAC SDU for RLC status PDU) = 8 +24 + Number of TBs * 8 bits; If status PDU is not included or,
MAC LI is included for MAC SDU for RLC status PDU instead of RLC data PDU, MAC padding will occur
in place of unused bits
Size of Timing Advance MAC CE is 8 bits (if no Timing Advance needs to be sent, padding will occur
instead);
RLC Status PDU size = 16 bits (including one ACK SQN triggered in execution X+1, due to loop back
transmission in execution X and as all loop backed PDUs in execution X have been correctly received, the
status PDU will carry an ACK SQN only.
This gives:
PDCP SDU size = 8*FLOOR((Total TBsize – N*16- 8*CEIL((2*16+(N-1)*12)/8) – 72)/(8*N)) bits
total TBsize that can be tested (corresponding to N=1, and PDCP SDU size of 16) is 136 bits.
ETSI

10 Mhz 502, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18, 20, 21, 23, 24, 26,
27, 29, 30, 32, 33, 35, 36, 38, 39, 41, 42, 44, 45, 47, 48,
50
15 Mhz 75 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32,
35, 36, 39, 40, 43, 44 ,47, 48, 51, 52, 55, 56, 59, 60, 63,
64, 67, 68, 71, 72, 75
20 Mhz 100 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64,
68, 72, 76, 80, 84, 88, 92, 96, 100
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U–S Message
2a and for each I MCS from 0 to
28
1 - - - -
SS looks up I TBS in table 7.1.7.1-
table 7.1.7.2.1-1 in TS 36.213
I TBS .
The SS uses the same I MCS and

TBsize for both transport blocks:
I MCS#1 = I MCS#2 = I MCS

TBsize#1 = TBsize#2= TBsize
performed if the sum of the sizes
of TBsize#1 and TBsize#2 is less than
or equal to UE capability
“Maximum number of DL-SCH
transport block bits received within
a TTI” as specified in Table
7.1.7.1.5.3.2-1 and larger than or
equal to 136 bits as specified in
Table 7.1.7.1.5.3.2-2, and the
effective channel code rate, as
defined in TS 36.213 clause 7.1.7,
is lower than or equal to 0.930.
SDUs for transport block 1 and 2
depending on TBsize#1, and
TBsize#2 in accordance with Table
7.1.7.1.5.3.2-2.
3 SS transmits the PDCP SDUs for <-- Transport block 1: - -
ETSI
transport block 1 and 2 MAC PDU

concatenated into a MAC PDU Transport block 2:
per transport block and indicates MAC PDU
on PDCCH DCI Format 2A with DCI: (DCI Format 2A, RA
RA type 0 and a resource block type 0, RBA( N PRB ),
assignment (RBA) correspondent
to N PRB as specified in 7.1.6.1 in I MCS#1 , I MCS#2 )
TS 36.213 and modulation and
coding scheme I MCS#1 for
transport block 1 and I MCS#2 for
transport block 2. The N PDCP
SDUs are split between MAC
PDU 1 and 2;
3a SS transmits one or more UL <-- (UL Grant) - -
Grants sufficient for transmitting
loop back PDCP SDUs.
4 CHECK: Does UE return the --> ( N x PDCP SDUs) 1 P
the SS in step 3?

c1 CHOICE{
the PICS
}
}
}
}
}
}
7.1.7.1.6 DL-SCH Transport Block Size selection / DCI format 2A / RA type 1 / Two
transport blocks enabled / Transport block to codeword swap flag value set to ’1’
(1)
ensure that {
when { UE has two transport blocks enabled and on PDCCH receives DCI format 2A indicating Resource
Allocation Type 1, a resource block assignment correspondent to N PRB physical resource blocks, the
Transport block to codeword swap flag value set to ’1’ and a modulation and coding scheme I MCS for
two transport blocks }
then { UE decodes the two transport blocks of sizes correspondent to the read N PRB and I MCS for
transport block 1 and I MCS for transport block 2 and forwards it to higher layers }
}
ETSI
5.3.3.1.5 and 5.3.3.1.5A; TS 36.213, clauses 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.7.2.1 and 7.1.7.2.2; and TS 36.306
clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
[TS 36.212 clause 5.3.3.1.5]

(two transport blocks enabled)
transport block
to codeword
(enabled) (enabled)
swap flag value
[TS 36.212 clause 5.3.3.1.5A]
...
- For resource allocation type 1 as defined in section 7.1.6.2 of [3]
- ⎡log 2 (P )⎤ bits of this field are used as a header specific to this resource allocation type to indicate the
selected resource blocks subset
- 1 bit indicates a shift of the resource allocation span
(⎡DL
- N RB ⎤
/ P − ⎡log 2 (P )⎤ − 1) bits provide the resource allocation
where the value of P depends on the number of DL resource blocks as indicated in subclause [7.1.6.1] of [3]
...
- Transport block to codeword swap flag – 1 bit
ETSI
...
If both transport blocks are enabled, the transport block to codeword mapping is specified according to Table
5.3.3.1.5-1.
...
[TS 36.213 clause 7.1.6.1]
DL
DL
⎡
/ P where ⎤
⎣N RB
DL
/ P⎦ DL
DL
− P ⋅ N RB
DL
⎣ ⎦
/ P . The
otherwise.

DL
N RB (P)
≤10 1
11 – 26 2
27 – 63 3
64 – 110 4
[TS 36.213 clause 7.1.7]
first
...
else
- set the Table 7.1.7.2.1-1 column indicator ′ to the total number of allocated PRBs based on the procedure
N PRB

′ .
ETSI
[TS 36.213 clause 7.1.7.1]

I MCS Qm I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4 reserved
31 6
[TS 36.213 clause 7.1.7.2]
7.1.7.2.1.
...
else
ETSI
7.1.7.2.2.
enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
ETSI
N PRB
I TBS
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
ETSI
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
ETSI
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
ETSI
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
ETSI
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
ETSI
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
[TS 36.213 clause 7.1.7.2.2]
For 1 ≤ N PRB ≤ 55 , the TBS is given by the ( I TBS , 2 ⋅ N PRB ) entry of Table 7.1.7.2.1-1.
For 56 ≤ N PRB ≤ 110 , a baseline TBS_L1 is taken from the ( I TBS , N PRB ) entry of Table 7.1.7.2.1-1, which is then
translated into TBS_L2 using the mapping rule shown in Table 7.1.7.2.2-1. The TBS is given by TBS_L2.
Table 7.1.7.2.2-1: One-layer to two-layer TBS translation table
TBS_L1 TBS_L2 TBS_L1 TBS_L2 TBS_L1 TBS_L2 TBS_L1 TBS_L2

1544 3112 3752 7480 10296 20616 28336 57336
1608 3240 3880 7736 10680 21384 29296 59256
1672 3368 4008 7992 11064 22152 30576 61664
1736 3496 4136 8248 11448 22920 31704 63776
1800 3624 4264 8504 11832 23688 32856 66592
1864 3752 4392 8760 12216 24496 34008 68808
1928 3880 4584 9144 12576 25456 35160 71112
1992 4008 4776 9528 12960 25456 36696 73712
2024 4008 4968 9912 13536 27376 37888 76208
2088 4136 5160 10296 14112 28336 39232 78704
2152 4264 5352 10680 14688 29296 40576 81176
2216 4392 5544 11064 15264 30576 42368 84760
2280 4584 5736 11448 15840 31704 43816 87936
2344 4776 5992 11832 16416 32856 45352 90816
2408 4776 6200 12576 16992 34008 46888 93800
2472 4968 6456 12960 17568 35160 48936 97896
2536 5160 6712 13536 18336 36696 51024 101840
2600 5160 6968 14112 19080 37888 52752 105528
2664 5352 7224 14688 19848 39232 55056 110136
2728 5544 7480 14688 20616 40576 57336 115040
2792 5544 7736 15264 21384 42368 59256 119816
2856 5736 7992 15840 22152 43816 61664 124464
2984 5992 8248 16416 22920 45352 63776 128496
3112 6200 8504 16992 23688 46888 66592 133208
3240 6456 8760 17568 24496 48936 68808 137792
3368 6712 9144 18336 25456 51024 71112 142248
3496 6968 9528 19080 26416 52752 73712 146856
3624 7224 9912 19848 27376 55056 75376 149776
[TS 36.306 clause 4.1]
ETSI

within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
75376 (2 layers)
75376 (2 layers)
Category 8 2998560 299856 35982720 8
75376 (2 layers)
75376 (2 layers)

TTI within a TTI
Category 7 102048 51024 No
Category 8 1497760 149776 Yes
Category 10 102048 51024 No
...
System Simulator
- Cell 1.
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] condition 2TX to configure MIMO.
ETSI

bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776
Category 6 149776
Category 7 149776
Category 8 299856
Category 9 149776
Category 10 149776
ETSI
Table 7.1.7.1.6.3.2-2: Number of downlink PDCP SDUs and PDCP SDU size used as test data for
transport block 1 and transport block 2
Total TBsize (sum of the sizes of TBsize#1 and Number of PDCP SDU size
TBsize#2) PDCP SDUs (bits]
(bits) See note 1
136 ≤ TBsize ≤ 12120 See note 2 1 8*FLOOR((TBsize - 120)/8)
48209 ≤ TBsize ≤ 60232 5 8*FLOOR((TBsize - 232/40))
8
84289 ≤ TBsize ≤ 96320 8*FLOOR((TBsize
– 320)/64))
24.301 clause 9.9.4.12).
PDCP SDU size = (Total TBsize –N*PDCP header size - AMD PDU header size - - MAC header size – Size of
Timing Advance– RLC Status PDU size) / N, where
AMD PDU header size is CEIL[(Number of TBs *16+(N-1)*12)/8] bytes which includes one 16 bit standard AM
header per TB and N-1 Length indicators of 12 bits corresponding to the worst case when one of the PDCP
SDU is split between the two transport blocks. If no PDCP SDU is split between the transport blocks then
there will be only N-2 LIs and MAC padding will occur instead of one LI;
MAC header size = R/R/E/LCID MAC subheader (8 bits for Timing Advance) + R/R/E/LCID MAC subheader
(24 bits for MAC SDU for RLC data PDU)+ Number of TBs R/R/E/LCID MAC subheaders (8 bits for MAC SDU
for RLC status PDU) = 8 +24 + Number of TBs * 8 bits; If status PDU is not included or, MAC LI is included for
MAC SDU for RLC status PDU instead of RLC data PDU, MAC padding will occur in place of unused bits
Size of Timing Advance MAC CE is 8 bits (if no Timing Advance needs to be sent, padding will occur instead);
RLC Status PDU size = 16 bits (including one ACK SQN triggered in execution X+1, due to loop back
transmission in execution X and as all loop backed PDUs in execution X have been correctly received, the
status PDU will carry an ACK SQN only.
This gives:
PDCP SDU size = 8*FLOOR((Total TBsize – N*16- 8*CEIL((2*16+(N-1)*12)/8) – 72)/(8*N)) bits
Note 2: According to TS 36.213 Table 7.1.7.2.1-1 and the final PDCP SDU size formula in Note 1, the smallest total
TBsize that can be tested (corresponding to N=1, and PDCP SDU size of 16) is 136 bits.
ETSI

10 Mhz 50
2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18, 20, 21, 23, 24, 26,
27, 29, 30, 32, 33, 35, 36, 38, 39, 41, 42, 44, 45, 47, 48,
50
15 Mhz 75 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32,
35, 36, 39, 40, 43, 44 ,47, 48, 51, 52, 55, 56, 59, 60, 63,
64, 67, 68, 71, 72, 75
20 Mhz 100 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64,
68, 72, 76, 80, 84, 88, 92, 96, 100
Note: Maximum bandwidth for EUTRA bands is 10/15/20 Mhz.
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U–S Message
2a and for each I MCS from 0 to
28
1 - - - -
SS looks up I TBS in table 7.1.7.1-
table 7.1.7.2.1-1 in TS 36.213
I TBS .
The SS uses the same I MCS and

TBsize for both transport blocks:
I MCS#1 = I MCS#2 = I MCS

TBsize#1 = TBsize#2= TBsize
performed if the sum of the sizes
of TBsize#1 and TBsize#2 is less than
or equal to UE capability
“Maximum number of DL-SCH
transport block bits received within
a TTI” as specified in Table
7.1.7.1.6.3.2-1 and larger than or
equal to 136 bits as specified in
Table 7.1.7.1.6.3.2-2, and the
effective channel code rate, as
defined in TS 36.213 clause 7.1.7,
is lower than or equal to 0.930.
SDUs for transport block 1 and 2
depending on TBsize#1 and
TBsize#2, in accordance with Table
7.1.7.1.6.3.2-2.
3 SS transmits the PDCP SDUs for <-- Transport block 1: - -
transport block 1 and 2 MAC PDU
concatenated into a MAC PDU Transport block 2:
ETSI
per transport block and indicates MAC PDU

on PDCCH DCI Format 2A with DCI: (DCI Format 2A, RA
RA type 1 and a resource block type 1, RBA( N PRB ),
assignment (RBA) correspondent
Transport block to
to N PRB as specified in 7.1.6.1 in codeword swap flag value
TS 36.213, transport block to
codeword swap flag value set to
set to=’1’, I MCS#1 ,
’1’ and modulation and coding I MCS#2 )
scheme I MCS#1 for transport block
1 and I MCS#2 for transport block
2. . The N PDCP SDUs are split
between MAC PDU 1 and 2;
3a SS transmits one or more UL <-- (UL Grant) - -
Grants sufficient for transmitting
loop back PDCP SDUs.
4 CHECK: Does UE return the --> ( N1 x PDCP SDUs, 1 P
same number of PDCP SDUs with N2 x PDCP SDUs)
the SS in step 3?

c1 CHOICE{
the PICS
}
}
}
}
}
}
7.1.7.2 UL-SCH transport block size support

7.1.7.2.1 UL-SCH transport block size selection / DCI format 0
(1)
ensure that {
when { UE has pending data for transmission and receives a Resource Block Assignment correspondent
to N PRB physical resource blocks and a modulation and coding scheme I MCS for PUSCH scheduling }
then { UE transmits MAC PDU on PUSCH on the granted resources using a transport block size
correspondent to the read N PRB and I MCS }
}
ETSI
36.213, clauses 8.1, 8.6, 8.6.1, 8.6.2 and 7.1.7.2.1; TS 36.211, clause 5.3.3; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.1]
- Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format
1A
- UL
Resource block assignment and hopping resource allocation – log 2 ( N RB ⎡ UL
( N RB + 1) / 2) ⎤ bits
- ⎛
⎜
⎝
⎡log 2 ( N RB
UL UL
⎠
subframe
- ⎛
⎜
⎝
⎡log 2 ( N RB
UL UL
( N RB + 1) / 2) ⎤ ⎞⎟ bits provide the resource allocation in the UL subframe as defined in
⎠
section 8.1 of [3]
[TS 36.213 clause 8.1]
The resource allocation information indicates to a scheduled UE a set of contiguously allocated virtual resource block
indices denoted by nVRB . A resource allocation field in the scheduling grant consists of a resource indication value
(RIV) corresponding to a starting resource block ( RBSTART ) and a length in terms of contiguously allocated resource
blocks ( LCRBs ≥ 1). The resource indication value is defined by
⎣
if ( LCRBs − 1) ≤ N RB
UL
/2 ⎦ then
RIV = N RB
UL
( LCRBs − 1) + RBSTART
else
RIV = N RB
UL UL
( N RB − LCRBs + 1) + ( N RB
UL
− 1 − RBSTART )
A UE shall discard PUSCH resource allocation in the corresponding PDCCH with DCI format 0 if consistent control
information is not detected.
[TS 36.213 clause 8.6]
To determine the modulation order, redundancy version and transport block size for the physical uplink shared channel,
the UE shall first
- read the 5-bit “modulation and coding scheme and redundancy version” field ( I MCS ) in the DCI, and
- check the “CQI request” bit in DCI, and
- compute the total number of allocated PRBs ( N PRB ) based on the procedure defined in Section 8.1, and
ETSI
- compute the number of coded symbols for control information..
[TS 36.213 clause 8.6.1]
For 0 ≤ I MCS ≤ 28 , the modulation order ( Q m ) is determined as follows:
− If the UE is capable of supporting 64QAM in PUSCH and has not been configured by higher layers to transmit
only QPSK and 16QAM, the modulation order is given by Q m' in Table 8.6.1-1.
− If the UE is not capable of supporting 64QAM in PUSCH or has been configured by higher layers to transmit
only QPSK and 16QAM, Q m' is first read from Table 8.6.1-1. The modulation order is set to Q m = min(4, Qm' ) .
− If the parameter ttiBundling provided by higher layers is set to TRUE, then the resource allocation size is
restricted to N PRB ≤ 3 and the modulation order is set to Q m = 2 .
For 29 ≤ I MCS ≤ 31 , If I MCS = 29 , the “CQI request” bit in DCI format 0 is set to 1 and N PRB ≤ 4 , the modulation order
is set to Qm = 2 . Otherwise, the modulation order shall be determined from the DCI transported in the latest PDCCH
with DCI format 0 for the same transport block using 0 ≤ I MCS ≤ 28 . If there is no PDCCH with DCI format 0 for the
same transport block using 0 ≤ I MCS ≤ 28 , the modulation order shall be determined from
− the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport
block is semi-persistently scheduled, or,
the random access response grant for the same transport block, when the PUSCH is initiated by the random access
response grant.
The UE shall use I MCS and Table 8.6.1-1 to determine the redundancy version (rvidx) to use in the physical uplink shared
channel.
ETSI
Table 8.6.1-1: Modulation, TBS index and redundancy version table for PUSCH
MCS Index Modulation Order TBS Index Redundancy

I MCS Q '
I TBS Version
m
rvidx
0 2 0 0
1 2 1 0
2 2 2 0
3 2 3 0
4 2 4 0
5 2 5 0
6 2 6 0
7 2 7 0
8 2 8 0
9 2 9 0
10 2 10 0
11 4 10 0
12 4 11 0
13 4 12 0
14 4 13 0
15 4 14 0
16 4 15 0
17 4 16 0
18 4 17 0
19 4 18 0
20 4 19 0
21 6 19 0
22 6 20 0
23 6 21 0
24 6 22 0
25 6 23 0
26 6 24 0
27 6 25 0
28 6 26 0
29 1
30 reserved 2
31 3
[TS 36.213 clause 8.6.2]
For 0 ≤ I MCS ≤ 28 , the UE shall first determine the TBS index ( I TBS ) using I MCS and Table 8.6.1-1. The UE shall then
follow the procedure in Section 7.1.7.2.1 to determine the transport block size.
For 29 ≤ I MCS ≤ 31 , If I MCS = 29 , the “CQI request” bit in DCI format 0 is set to 1 and N PRB ≤ 4 , then there is no
transport block for the UL-SCH and only the control information feedback for the current PUSCH reporting mode is
transmitted by the UE. Otherwise, the transport block size shall be determined from the initial PDCCH for the same
transport block using 0 ≤ I MCS ≤ 28 . If there is no initial PDCCH with DCI format 0 for the same transport block using
0 ≤ I MCS ≤ 28 , the transport block size shall be determined from
− the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport
block is semi-persistently scheduled, or,
− the random access response grant for the same transport block, when the PUSCH is initiated by the random
[TS 36.213 clause 7.1.7.2.1]
ETSI
N PRB
I TBS
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
ETSI
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
ETSI
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
ETSI
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
ETSI
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
ETSI
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
[TS 36.211 clause 5.3.3]
The block of complex-valued symbols d (0),..., d ( M symb − 1) is divided into M symb M scPUSCH sets, each corresponding
to one SC-FDMA symbol. Transform precoding shall be applied according to
M scPUSCH −1 2πik
−j
∑
1 M scPUSCH
z (l ⋅ M scPUSCH + k) = d (l ⋅ M scPUSCH + i )e
M scPUSCH i =0
k = 0,..., M scPUSCH − 1
l = 0,..., M symb M scPUSCH − 1
resulting in a block of complex-valued symbols z (0),..., z ( M symb − 1) . The variable M scPUSCH = M RB

PUSCH
⋅ N scRB , where
PUSCH
M RB represents the bandwidth of the PUSCH in terms of resource blocks, and shall fulfil
PUSCH
M RB = 2α 2 ⋅ 3α 3 ⋅ 5α 5 ≤ N RB
UL
where α 2 ,α 3 ,α 5 is a set of non-negative integers.
[TS 36.306 clause 4.1]
values for each UE Category.

within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
UE Category Maximum number of Support for

bits of an UL-SCH 64QAM in UL
transport block
transmitted within a
TTI
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No
Category 5 75376 Yes
ETSI
System Simulator:
- Cell 1.
Table 5.6.1-1 in [31](to enable testing of N PRB up to maximum value). For Band 18, Band 19 and Band 25,
UE:
None.
Preamble:

bits of an UL-SCH
transport block
transmitted within a
TTI
Category 1 5160
Category 2 25456
Category 3 51024
Category 4 51024
Category 5 75376
Category 6 51024
Category 7 51024
Category 8 149776
Category 9 51024
Category 10 51024
ETSI

[bits] PDCP SDUs, [bits]
NSDUs See note 1
104 ≤ TBsize ≤12096 1 8*FLOOR((TBsize – 96)/8)
note 2
TBsize> 72240 7 8*FLOOR((TBsize 264/56))
24.301 clause 9.9.4.12).
N PDCP SDUs are transmitted in N AMD PDUs concatenated into a MAC PDU. The PDCP SDU size of
each PDCP SDU is
PDCP SDU size = (TBsize – N*PDCP header size - N*AMD PDU header size - MAC header – Size of
AMD PDU header size is 16 bits;
MAC header si40 bits as MAC header size can be:
MAC SDU for RLC Status PDU) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for AMD PDU) = 8 +
16 + 8 bits= 32 bits
or
MAC SDU for AMD PDU, Note: Length can be of 2 bytes depending upon the size of AMD PDU)+
R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Status PDU) + = 8+24 + 8 bits = 40 bits
Therefore Maximum MAC header size can be 40 bits
RLC Status PDU size = 16 bit sIze =
This gives:
PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CIEL((16+(N-1)*12)/8) –64)/(8*N)) bits.

Max Bandwidth
Max N PRB
10 Mhz 50
15 Mhz 75
20 Mhz 100
Note: Maximum bandwidth for EUTRA bands is 10/15/20 Mhz.

U–S Message
1 The SS ignores scheduling - - - -
requests and does not allocate
any uplink grant.
ETSI
1 to Max N PRB and I MCS from 0

N
to 28, where PRB satisfies
values equal to
2α 2 ⋅ 3α 3 ⋅ 5α 5 ≤ N RB
UL
and
α ,α ,α
where 2 3 5 is a set of non-
negative integers.
2 SS looks up I TBS in table 8.6.1-1 - - - -
in TS 36.213 based on the value
table 7.1.7.2.1-1 in TS 36.213
I TBS .
number of UL-SCH transport
7.1.7.2.1.3.2-2.
7.1.7.2.1.3.2-2.
4 After 300ms, the SS transmits all <-- MAC PDU (NSDUs x PDCP - -
PDCP SDUs (NSDUs) as created in SDU)
step 3 in a MAC PDU.
5 After 60ms of step 4, the allocates <-- (UL Grant) - -
an uplink grant SS indicating DCI DCI: (DCI Format 0, RVI
Format 0 with a RVI ( N PRB ), I MCS )
specified in 8.1 in TS 36.213 and
modulation and coding scheme
I MCS as specified in Table 8.6.1-1
in TS 36.213.
6 Void - - - -
7 CHECK: Does UE return the --> MAC PDU (NSDUs x PDCP 1 P
same number of PDCP SDUs with SDU)
the SS in step 4 using the
Resource Block Assignment and
modulation and coding scheme as
configured by the SS in step 5?
ETSI

c1 CHOICE{
the PICS
}
}
}
}
}
}
7.1.8 Reporting of Rank Indicator (RI)

7.1.8.1 Periodic RI reporting using PUCCH / Category 1 UE / Transmission mode 3/4
(1)
ensure that {
when { Category 1 UE is configured to transmission mode 3}
then { UE always reports RI equals to one}
}
(2)
ensure that {
when { Category 1 UE is configured to transmission mode 4}
then { UE always reports RI equals to one}
}
References: The conformance requirements covered in the present TC are specified in: TS 36.306 clause 4 and clause
4.1, TS 36.213 clause 7.2.2.
[TS 36.306, clause 4]
The following subclauses define the UE radio access capability parameters. Only parameters for which there is the
possibility for UEs to signal different values are considered as UE radio access capability parameters. Therefore,
mandatory capabilities that are the same for all UEs are not listed here.
[TS 36.306, clause 4.1]
values for each UE Category.
ETSI

within a TTI
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4
[TS 36.213, clause 7.2.2]
A UE is semi-statically configured by higher layers to periodically feed back different CQI, PMI, and RI on the PUCCH
using the reporting modes given in Table 7.2.2-1 and described below.
Table 7.2.2-1: CQI and PMI Feedback Types for PUCCH reporting Modes
PMI Feedback Type

No PMI Single PMI
PUCCH CQI Feed-
Wideband Mode 1-0 Mode 1-1

back Type
(wideband CQI)
UE Selected Mode 2-0 Mode 2-1

(subband CQI)
For each of the transmission modes defined in Section 7.1, the following reporting modes are supported on PUCCH:
- Transmission mode 1 : Modes 1-0, 2-0
- Transmission mode 8 : Modes 1-1, 2-1 if the UE is configured with PMI/RI reporting; modes 1-0, 2-0 if the UE is
configured without PMI/RI reporting
Four CQI/PMI and RI reporting types with distinct periods and offsets are supported for each PUCCH reporting mode
as given in Table 7.2.2-3:
- Type 1 report supports CQI feedback for the UE selected sub-bands
- Type 2 report supports wideband CQI and PMI feedback.
- Type 3 report supports RI feedback
- Type 4 report supports wideband CQI
The periodicity N p (in subframes) and offset NOFFSET ,CQI (in subframes) for CQI/PMI reporting are determined based on
the parameter cqi-pmi-ConfigIndex ( I CQI / PMI ) given in Table 7.2.2-1A for FDD and table 7.2.2-1C for TDD. The periodicity
M RI and relative offset N OFFSET , RI for RI reporting are determined based on the parameter ri-ConfigIndex ( I RI ) given in
ETSI
Table 7.2.2-1B. Both cqi-pmi-ConfigIndex and ri-ConfigIndex are configured by higher layer signalling. The relative
reporting offset for RI N OFFSET , RI takes values from the set {0, −1,..., −( N p − 1)}
- Wideband feedback
- Mode 1-1 description:
- In the subframe where RI is reported (only for transmission mode 4 and transmission mode 8):
- A UE shall determine a RI assuming transmission on set S subbands.
- The UE shall report a type 3 report consisting of one RI
- In the subframe where CQI/PMI is reported:
- A single precoding matrix is selected from the codebook subset assuming transmission on set S
subbands
- A UE shall report a type 2 report on each respective successive reporting opportunity consisting of
- A single wideband CQI value which is calculated assuming the use of a single precoding matrix in
all subbands and transmission on set S subbands.
- The selected single precoding matrix indicator (wideband PMI)
- When RI>1, a 3-bit wideband spatial differential CQI, which is shown in Table 7.2-2.
- For transmission mode 4 and transmission mode 8, the PMI and CQI are calculated conditioned on the
last reported periodic RI. For other transmission modes they are calculated conditioned on
transmission rank 1.
System Simulator:
- Cell 1
- System Simulator transmits according to the rank reported by UE
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18]
ETSI

U-S Message
- EXCEPTION: Step 1 is repeated 5 times - - - -
1 CHECK: Does the UE transmit PUCCH type 3 --> (RI) 1 P
report with RI set to 1? (NOTE)
2 The SS transmits a MAC PDU containing an <-- MAC PDU - -
RRCConnectionReconfiguration message to (RRCConnectionReconfiguration)
reconfigure the UE transmission mode to tm4
RRCConnectionReconfigurationComplete (RRCConnectionReconfigurationC
message omplete)
- EXCEPTION: Step 4 is repeated 5 times - - - -
4 CHECK: Does the UE transmit PUCCH type 3 --> (RI) 2 P
report with RI set to 1? (NOTE)
5 Check: Does the test result of CALL generic - - 2 -
indicate that UE is in E-UTRA
Note: In this test case, it is configured for wideband CQI/PMI reporting for transmission mode tm3 and tm4, the
reporting instances of RI reporting are subframes satisfying:
( )
10 × n f + ⎣n s / 2⎦ − N OFFSET ,CQI − N OFFSET , RI mod( N P ⋅ M RI ) = 0 the default configuration in TS 36.508,
the cqi-pmi-ConfigIndex( I CQI / PMI ) = 25(FDD)/24(TDD), ri-ConfigIndex( I RI ) = 483(FDD) / 484(TDD), as
per the Table 7.2.2-1A, 7.2.2-1B and 7.2.2-1C in TS 36.213, the periodicity N p (in subframes) =
20ms(FDD) / 20ms(TDD), N OFFSET ,CQI (in subframes) = 8ms(FDD) / 8ms(TDD), The periodicity M RI =
8(FDD) / 8(TDD) and relative offset N OFFSET , RI = 0(FDD) / -1(TDD)
Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)
Table 7.1.8.1.3.3-2: PhysicalConfigDedicated-DEFAULT (step 2, Table 7.1.8.1.3.2-1)

defaultValue NULL
transmissionMode tm4
codebookSubsetRestriction CHOICE {
n2TxAntenna-tm4 '111111' BIT STRING
(SIZE (6))
}
Release NULL
}
}
}
}
ETSI
7.1.9 Activation/Deactivation of SCells

7.1.9.1 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control
element reception / sCellDeactivationTimer
7.1.9.1.1 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control
element reception / sCellDeactivationTimer / Intra-band Contiguous CA
(1)
with { UE in E-UTRA RRC_CONNECTED state with SCell configure }
ensure that {
when { the UE receives an Activation MAC Control Element activating the Scell }
then { the UE starts monitoring PDCCH on activated Scell }
}
(2)
ensure that {
when { the UE receives an UL grant on Scell PDCCH}
then { the UE restarts the sCellDeactivationTimer }
}
(3)
ensure that {
when { the UE sCellDeactivationTimer expires}
then { the UE deactivates the Scell and stops monitoring PDCCH on Scell }
}
(4)
with { UE in E-UTRA RRC_CONNECTED state with SCell Activated }
ensure that {
when { the UE receives a deactivation MAC Control Element deactivating the Scell }
then { the UE deactivates the Scell and stops monitoring PDCCH on Scell }
}
(5)
ensure that {
when { the UE receives a DL assignment on Scell PDCCH}
then { the UE restarts the sCellDeactivationTimer }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.13 &
6.1.3.8.
[TS 36.321, clause 5.13]
If the UE is configured with one or more SCells, the network may activate and deactivate the configured SCells. The
PCell is always activated. The network activates and deactivates the SCell(s) by sending the Activation/Deactivation
MAC control element described in subclause 6.1.3.8. Furthermore, the UE maintains a sCellDeactivationTimer timer
per configured SCell and deactivates the associated SCell upon its expiry. The same initial timer value applies to each
instance of the sCellDeactivationTimer and it is configured by RRC. The configured SCells are initially deactivated
upon addition and after a handover.
The UE shall for each TTI and for each configured SCell:
- if the UE receives an Activation/Deactivation MAC control element in this TTI activating the SCell, the UE
shall in the TTI according to the timing defined in [2]:
ETSI
- activate the SCell; i.e. apply normal SCell operation including:
- SRS transmissions on the SCell;
- CQI/PMI/RI/PTI reporting for the SCell;
- PDCCH monitoring on the SCell;
- PDCCH monitoring for the SCell
- start or restart the sCellDeactivationTimer associated with the SCell;
- else, if the UE receives an Activation/Deactivation MAC control element in this TTI deactivating the SCell; or
- if the sCellDeactivationTimer associated with the activated SCell expires in this TTI:
- in the TTI according to the timing defined in [2]:
- deactivate the SCell;
- stop the sCellDeactivationTimer associated with the SCell;
- flush all HARQ buffers associated with the SCell.
- if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or
- if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment
for the activated SCell:
- restart the sCellDeactivationTimer associated with the SCell;
- if the SCell is deactivated:
- not transmit SRS on the SCell;
- not report CQI/PMI/RI/PTI for the SCell;
- not transmit on UL-SCH on the SCell;
- not monitor the PDCCH on the SCell;
- not monitor the PDCCH for the SCell.
[TS 36.321, clause 6.1.3.8]
The Activation/Deactivation MAC control element is identified by a MAC PDU subheader with LCID as specified in
table 6.2.1-1. It has a fixed size and consists of a single octet containing seven C-fields and one R-field. The
Activation/Deactivation MAC control element is defined as follows (figure 6.1.3.8-1).
- Ci: if there is an SCell configured with SCellIndex i as specified in [8], this field indicates the
activation/deactivation status of the SCell with SCellIndex i , else the UE shall ignore the Ci field. The Ci field is
set to "1" to indicate that the SCell with SCellIndex i shall be activated. The Ci field is set to "0" to indicate that
the SCell with SCellIndex i shall be deactivated;
- R: Reserved bit, set to “0”.
Figure 6.1.3.8-1: Activation/Deactivation MAC control element
ETSI
System Simulator:
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) on Cell 1 according to [18].

T0 -85 -85
RS EPRE Hz
ETSI

U-S Message
containing a sCellToAddModList on Cell 1 with
SCell (Cell 3) addition.
message.
4 200 ms after step 3, the SS indicates a new <-- MAC PDU (CC2) - -
transmission on PDCCH of CC2 and transmits
a MAC PDU (containing an RLC PDU )
5 Check: Does the UE transmit a Scheduling --> (SR) 1 P
Request on PUCCH?
PDU in step 7
Request on PUCCH?
PDU in step 11
14 Check: Does the UE transmit a Scheduling --> (SR) 3 F
Request on PUCCH in next 1 second?
16 200 ms after step 15 The SS indicates a new <-- MAC PDU (CC2) - -
a MAC PDU (containing just padding or RLC
status PDU, but no RLC data PDU )
17 400 ms after step 15 the SS indicates a new <-- MAC PDU (CC2) - -
18 Check: Does the UE transmit a Scheduling --> (SR) 1,5 P
Request on PUCCH?
PDU in step 19
21 The SS transmits Deactivation MAC control <-- MAC PDU (Deactivation (C1=0)) - -
element to de-activate Scell (Cell 3).
(containing an RLC PDU )
23 Check: Does the UE transmit a Scheduling --> (SR) 4 F
Request on PUCCH in next 1 second?
ETSI
Table 7.1.9.1.1.3.3-1: RRCConnectionReconfiguration (Table 7.1.9.1.1.3.2-1, step 1)
Derivation path: 36.508 table 4.6.1-8 condition SCell_AddMod

c1 CHOICE{
explicit MAC-MainConfig-RBC
}
}
}
}
}
}
Derivation path: 36.508 table 4.8.2.1.5-1 condition DRX_L

MAC-MainConfig-RBC SEQUENCE {
sCellDeactivationTimer-r10 rf32 320 milliseconds
}
}

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
}

element reception / sCellDeactivationTimer / Inter-band CA
- CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
- Cells configuration: Cell 10 replaces Cell 3.

element reception / sCellDeactivationTimer / Intra-band non-Contiguous CA
ETSI
- CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
7.1.10 Coordinated Multi-Point Operation (CoMP) for LTE

7.1.10.1 Sending SR on PUCCH with DMRS generated by using virtual cell identity /
nPUCCH-Identity
(1)
with { UE in E-UTRA RRC_CONNECTED state with nPUCCH-Identity-r11 configured }
ensure that {
when { UE has UL data available for transmission and UE has no UL-SCH resources available and
SR_COUNTER is less than dsr-TransMax }
then { the UE transmits an SR on every available PUCCH until resources are granted }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.211 clauses 5.4, 5.5.1.3,
and 5.5.1.5. Unless otherwise stated these are Rel-11 requirements.
[TS 36.211, clause 5.4]
The physical uplink control channel, PUCCH, carries uplink control information. Simultaneous transmission of PUCCH
and PUSCH from the same UE is supported if enabled by higher layers. For frame structure type 2, the PUCCH is not
transmitted in the UpPTS field.
The physical uplink control channel supports multiple formats as shown in Table 5.4-1.
Formats 2a and 2b are supported for normal cyclic prefix only.
Table 5.4-1: Supported PUCCH formats
PUCCH format Modulation scheme Number of bits per subframe, M bit

1 N/A N/A
1a BPSK 1
1b QPSK 2
2 QPSK 20
2a QPSK+BPSK 21
2b QPSK+QPSK 22
3 QPSK 48
cell
All PUCCH formats use a cyclic shift, n cs (ns , l ) , which varies with the symbol number l and the slot number ns
according to
∑i =0 c(8Nsymb
cell 7 UL
ncs (ns , l ) = ⋅ ns + 8l + i ) ⋅ 2i
where the pseudo-random sequence c(i ) is defined by clause 7.2. The pseudo-random sequence generator shall be
initialized with cinit = nID
RS RS
, where nID cell
is given by clause 5.5.1.5 with N ID corresponding to the primary cell, at the
beginning of each radio frame.
[TS 36.211, clause 5.5.1.3]
The sequence-group number u in slot ns is defined by a group hopping pattern f gh (ns ) and a sequence-shift pattern
f ss according to
ETSI
( )
u = f gh (ns ) + f ss mod 30
There are 17 different hopping patterns and 30 different sequence-shift patterns. Sequence-group hopping can be
enabled or disabled by means of the cell-specific parameter Group-hopping-enabled provided by higher layers.
Sequence-group hopping for PUSCH can be disabled for a certain UE through the higher-layer parameter Disable-
sequence-group-hopping despite being enabled on a cell basis unless the PUSCH transmission corresponds to a
Random Access Response Grant or a retransmission of the same transport block as part of the contention based random
access procedure.
The group-hopping pattern f gh (ns ) may be different for PUSCH, PUCCH and SRS and is given by
⎧⎪0 if group hopping is disabled

f gh (ns ) = ⎨⎛ 7
c(8ns + i ) ⋅ 2i ⎞⎟ mod 30 if group hopping is enabled
⎪⎩⎜⎝ ∑i =0 ⎠
⎢ n RS ⎥
initialized with cinit = ⎢ ID
⎥
RS
at the beginning of each radio frame where nID is given by clause 5.5.1.5.
⎢
⎣ 30 ⎥
⎦
The sequence-shift pattern f ss definition differs between PUCCH, PUSCH and SRS.
For PUCCH, the sequence-shift pattern f ssPUCCH is given by f ssPUCCH = nID

RS RS
mod 30 where nID is given by clause
5.5.1.5.
[TS 36.211, clause 5.5.1.5]

RS
The definition of nID depends on the type of transmission.
Transmissions associated with PUCCH:
- RS
nID = N ID
cell PUCCH
if no value for nID is configured by higher layers,
- RS
nID = nID
PUCCH
otherwise.
System Simulator:
2 Cells
- Cell 1 is the macro cell with higher power level that is further from UE than Cell 2.
- Cell 2 is the micro cell with lower power level that is nearer to UE compared to Cell 1.
- Two cells have the same virtual cell identity as configured in Table 7.1.10.1.3.3-3.
UE:
None.
Preamble:
section 7.1.10.1.3.3.
ETSI
Table 7.1.10.1.3.2-1shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions.
Table 7.1.10.1.3.2-1: Cell configuration


U-S Message
PDCCH and transmits a MAC PDU.
Request on PUCCH whose DMRS is
generated by using the configured nPUCCH-
Identity-r11 encoded so that it can be received
on Cell 1 and Cell 2?
loop back PDU corresponding to step 1.
Table 7.1.10.1.3.3-1: RRCConnectionReconfiguration (preamble, step 8, TS 36.508 table 4.5.3.3-1)
Derivation path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)
Table 7.1.10.1.3.3-2: PhysicalConfigDedicated-DEFAULT (Table 7.1.10.1.3.3-1)
Derivation Path: 36.508 table 4.8.2.1.6-1, condition SRB1

pucch-ConfigDedicated-v1020 PUCCH- 2TX AND
ConfigDedicated-v1020- FDD, TDD
DEFAULT
pucch-ConfigDedicated-v1130 SEQUENCE { PUCCH-
ConfigDedicated-v1130
pusch-ConfigDedicated-v1130 Not present
uplinkPowerControlDedicated-v1130 Not present
}
ETSI
Table 7.1.10.1.3.3-3: PUCCH-ConfigDedicated-v1130
Derivation Path: 36.508 clause 4.6.3-9AA

PUCCH-ConfigDedicated-v1130 ::= SEQUENCE {
n1PUCCH-AN-CS-v1130 CHOICE {
setup SEQUENCE { 2 entries
n1PUCCH-AN-CS-ListP1-r11[1] 5
n1PUCCH-AN-CS-ListP1-r11[2] 6
}
}
nPUCCH-Param-r11 CHOICE {
setup SEQUENCE {
nPUCCH-Identity-r11 2
n1PUCCH-AN-r11 3
}
}
}
7.1.10.2 Transmitting data on PUSCH with DMRS generated by using virtual cell
identity / nPUSCH-Identity
(1)
with { UE in E-UTRA RRC_CONNECTED state with nPUSCH-Identity-r11 configured }
ensure that {
when { UE has UL data available for transmission }
then { UE transmits the data to the network on PUSCH with DMRS generated by using nPUSCH-
Identity-r11 }
}
5.5.1.4, 5.5.1.5 and 5.5.2.1.1. Unless otherwise stated these are Rel-11 requirements.
[TS 36.211, clause 5.5.1.3]
The sequence-group number u in slot ns is defined by a group hopping pattern f gh (ns ) and a sequence-shift pattern
f ss according to
( )
u = f gh (ns ) + f ss mod 30
There are 17 different hopping patterns and 30 different sequence-shift patterns. Sequence-group hopping can be
enabled or disabled by means of the cell-specific parameter Group-hopping-enabled provided by higher layers.
Sequence-group hopping for PUSCH can be disabled for a certain UE through the higher-layer parameter Disable-
sequence-group-hopping despite being enabled on a cell basis unless the PUSCH transmission corresponds to a
Random Access Response Grant or a retransmission of the same transport block as part of the contention based random
access procedure.
The group-hopping pattern f gh (ns ) may be different for PUSCH, PUCCH and SRS and is given by
⎧⎪0 if group hopping is disabled

f gh (ns ) = ⎨⎛ 7 i⎞
⎪⎩⎜⎝ ∑i =0
c(8ns + i ) ⋅ 2 ⎟ mod 30 if group hopping is enabled
⎠
⎢ n RS ⎥
initialized with cinit = ⎢ ID
⎥
RS
at the beginning of each radio frame where nID is given by clause 5.5.1.5.
⎢
⎣ 30 ⎥
⎦
ETSI
The sequence-shift pattern f ss definition differs between PUCCH, PUSCH and SRS.
(
For PUSCH, the sequence-shift pattern f ssPUSCH is given by f ssPUSCH = N ID
cell
)
+ Δ ss mod 30 , where Δ ss ∈ {0,1,...,29} is
PUSCH
configured by higher layers, if no value for nID is provided by higher layers or if the PUSCH transmission
corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the
contention based random access procedure, otherwise it is given by f ssPUSCH = n ID
RS RS
mod 30 with nID given by clause
5.5.1.5.
ETSI
[TS 36.211, clause 5.5.1.4]
Sequence hopping only applies for reference-signals of length M scRS ≥ 6N scRB .
For reference-signals of length M scRS < 6N scRB , the base sequence number v within the base sequence group is given by
v=0.
For reference-signals of length M scRS ≥ 6N scRB , the base sequence number v within the base sequence group in slot n s
is defined by
⎧c(n ) if group hopping is disabled and sequence hopping is enabled

v=⎨ s
⎩0 otherwise
where the pseudo-random sequence c(i ) is given by clause 7.2. The parameter Sequence-hopping-enabled provided by
higher layers determines if sequence hopping is enabled or not. Sequence hopping for PUSCH can be disabled for a
certain UE through the higher-layer parameter Disable-sequence-group-hopping despite being enabled on a cell basis
unless the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same
transport block as part of the contention based random access procedure.
⎢ n RS ⎥ 5
For PUSCH, the pseudo-random sequence generator shall be initialized with cinit = ⎢ ID
⎥⋅2 + f ssPUSCH at the
⎣⎢ 30 ⎦⎥
RS
beginning of each radio frame where nID is given by clause 5.5.1.5.
[TS 36.211, clause 5.5.1.5]

RS
The definition of nID depends on the type of transmission.
Transmissions associated with PUSCH:
- RS
nID = N ID
cell PUSCH
if no value for nID is configured by higher layers or if the PUSCH transmission corresponds to
a Random Access Response Grant or a retransmission of the same transport block as part of the contention based
random access procedure,
- RS
nID = nID
PUSCH
otherwise.
System Simulator:
2 Cells
- Cell 1 is the macro cell with higher power level that is further from UE than Cell 2.
- Cell 2 is the micro cell with lower power level that is nearer to UE compared to Cell 1.
- Two cells have the same virtual cell identity as configured in Table 7.1.10.2.3.3-3.
UE:
None.
Preamble:
section 7.1.10.2.3.3.
ETSI
Table 7.1.10.2.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions.
Table 7.1.10.2.3.2-1: Cell configuration


U-S Message
PDCCH and transmits a MAC PDU.
PUCCH whose DMRS is generated by using
the configured nPUCCH-Identity-r11?
to step 1 with the DMRS generated by using
the configured nPUSCH-Identity-r11 encoded
so that it can be received on Cell 1 and Cell 2?
Derivation path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)
Table 7.1.10.2.3.3-2: PhysicalConfigDedicated-DEFAULT (Table 7.1.10.2.3.3-1)
Derivation Path: 36.508 table 4.8.2.1.6-1, condition SRB1

pucch-ConfigDedicated-v1130 Not present
pusch-ConfigDedicated-v1130 PUSCH-
ConfigDedicated-v1130
uplinkPowerControlDedicated-v1130 Not present
}
Table 7.1.10.2.3.3-3: PUSCH-ConfigDedicated-v1130 (Table 7.1.10.2.3.3-1)
Derivation Path: 36.508 clause 4.6.3-11AA

PUSCH-ConfigDedicated-v1130 ::= SEQUENCE {
pusch-DMRS-r11 CHOICE {
setup SEQUENCE {
nPUSCH-Identity-r11 3
nDMRS-CSH-Identity-r11 4
}
}
}
ETSI
7.2 RLC
7.2.1 General
For UM tests, the UM test DRB is set up using the Generic Procedure described in clause 4.5 of [18], with the
parameters described in clause 4.8.2.1.3.1 of [18], except for the tests that explicitly specify a different DRB
configuration.
For AM tests, the AM test DRB is set up using the Generic Procedure described in clause 4.5 of [18], with the
parameters described in clause 4.8.2.1.3.2 of [18], except for the tests that explicitly specify a different DRB
configuration.
Unless specified otherwise in the test procedure sequence, the data field of each RLC PDU transmitted by the SS
contains a complete RLC SDU.
7.2.2 Unacknowledged mode

7.2.2.1 UM RLC / Segmentation and reassembly / 5-bit SN / Framing info field
(1)
ensure that {
when { UE receives a 5 bit SN configured UMD PDU containing a FI field set to 00 }
then { UE correctly decodes the received UMD PDU }
}
(2)
ensure that {
}
(3)
ensure that {
}
(4)
ensure that {
}
6.2.2.6.
[TS 36.322, clause 6.2.1.3]
An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. When the 5 bit SN is configured, the
length of the fixed part of the UMD PDU header is one byte. When the 10 bit SN is configured, the fixed part of the
UMD PDU header is identical to the fixed part of the AMD PDU header, except for D/C, RF and P fields all being
replaced with R1 fields. The extension part of the UMD PDU header is identical to the extension part of the AMD PDU
header (regardless of the configured SN size).
ETSI
[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
The FI field indicates whether a RLC SDU is segmented at the beginning and/or at the end of the Data field.
Specifically, the FI field indicates whether the first byte of the Data field corresponds to the first byte of a RLC SDU,
and whether the last byte of the Data field corresponds to the last byte of a RLC SDU. The interpretation of the FI field
is provided in Table 6.2.2.6-1.
Table 6.2.2.6-1: FI field interpretation
Value Description
00 First byte of the Data field corresponds to the first byte of a RLC SDU.
Last byte of the Data field corresponds to the last byte of a RLC SDU.
Last byte of the Data field does not correspond to the last byte of a RLC SDU.
10 First byte of the Data field does not correspond to the first byte of a RLC SDU.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
applicable for the configured UM DRB.
Table 7.2.2.1.3.1-1: RLC parameters
Uplink RLC
sn-FieldLength size5
Downlink RLC
ETSI

U-S Message
1 The SS transmits UMD PDU#1 containing a <-- UMD PDU#1 - -
complete RLC SDU#1 (FI field = 00).
2 Check: Does the UE transmit RLC SDU#1? --> (RLC SDU#1) 1 P
3 The SS transmits UMD PDU#2 containing the <-- UMD PDU#2 - -
first segment of RLC SDU#2 (FI field = 01).
second segment of RLC SDU#2 (FI field = 11).
last segment of RLC SDU#2 (FI field = 10).
6 Check: Does the UE transmit RLC SDU#2? --> (RLC SDU#2) 2,3, P
4
None.
7.2.2.2 UM RLC / Segmentation and reassembly / 10-bit SN / Framing info field

(1)
ensure that {
}
(2)
ensure that {
}
(3)
ensure that {
}
(4)
ensure that {
}
6.2.2.6.
[TS 36.322, clause 6.2.1.3]
ETSI
[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
Value Description
System Simulator:
- Cell 1.
UE:
None.
Preamble:

U-S Message
1 The SS transmits UMD PDU#1 containing a <-- UMD PDU#1 - -
6 Check: Does the UE transmit RLC SDU#2? --> (RLC SDU#2) 2, 3, P
4
None.
ETSI
7.2.2.3 UM RLC / Reassembly / 5-bit SN / LI value > PDU size

(1)
ensure that {
when { UE receives a 5 bit SN configured RLC PDU with Length Indicator value larger than RLC PDU
size }
then { UE discards the RLC PDU }
}
See TS 36.322 clauses 6.2.2.5 and 5.5.1
References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1 and
6.2.2.5.
[TS 36.322, clause 5.5.1]
When an RLC entity receives an RLC PDU that contains reserved or invalid values, the RLC entity shall:
[TS 36.322, clause 6.2.2.5]
Length: 11 bits.
The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU
delivered/received by an UM or an AM RLC entity. The first LI present in the RLC data PDU header corresponds to the
first Data field element present in the Data field of the RLC data PDU, the second LI present in the RLC data PDU
header corresponds to the second Data field element present in the Data field of the RLC data PDU, and so on. The
value 0 is reserved.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Uplink RLC
Downlink RLC
ETSI

U-S Message
- EXCEPTION: the behaviour described in table - - - -
7.2.2.3.3.2-2 runs in parallel with steps 1 to 5
below.
1 The SS transmits UMD PDU#1 containing first <-- UMD PDU#1 (SN=0) - -
segment of RLC SDU#1.
2 The SS transmits UMD PDU#2 containing last <-- UMD PDU#2 (SN=1) - -
segment of RLC SDU#1 and first segment of
RLC SDU#2.
segment of RLC SDU#2, first segment of RLC
SDU#3 and with Length Indicator that points
beyond the end of the UMD PDU#3.
5 The SS transmits UMD PDU#5 containing RLC <-- UMD PDU#5 (SN=4) - -
SDU#4.

U-S Message
1 The UE transmits RLC SDU#1. --> (RLC SDU#1) - -
2 Check: Does the UE transmit RLC SDU#2? --> (RLC SDU#2) 1 F
None.
7.2.2.4 UM RLC / Reassembly / 10-bit SN / LI value > PDU size

(1)
ensure that {
when { UE receives an RLC PDU with Length Indicator value larger than RLC PDU size }
then { UE discards the RLC PDU }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1.
[TS 36.322, clause 5.5.1]
System Simulator:
- Cell 1.
ETSI
UE:
None.
Preamble:

U-S Message
- EXCEPTION: The behaviour described in table - - - -
7.2.2.4.3.2-2 runs in parallel with steps 1 to 5
below.
1 The SS transmits UMD PDU#1 containing first <-- UMD PDU#1 (SN=0) - -
segment of RLC SDU#1 and first segment of
RLC SDU#2.
segment of RLC SDU#2, first segment of RLC
SDU#3 and with Length Indicator that points
beyond the end of the RLC PDU#3.
5 The SS transmits UMD PDU#5 containing RLC <-- UMD PDU#5 (SN=4) - -
SDU#4.

U-S Message
None.
7.2.2.5 UM RLC / Correct use of sequence numbering

7.2.2.5.1 UM RLC / 5-bit SN / Correct use of sequence numbering
(1)
ensure that {
when { UE transmits the first PDU }
then { UE sets the sequence Number field equal to 0 }
}
(2)
ensure that {
when { UE transmits subsequent PDUs }
then { SN incremented by 1 for each PDU transmitted }
}
ETSI
(3)
with { UE in E-UTRA RRC_CONNECTED state and an UM RLC DRB is configured using 5 bit SN }
ensure that {
when { UE transmits more than 32 PDUs }
then { UE wraps the Sequence Number after transmitting the 32 PDU }
}
(4)
ensure that {
when { more than 32 PDUs are sent to UE }
then { UE accepts PDUs with SNs that wrap around every 32 PDU }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause
5.1.2.1.1, 5.1.2.2, 6.2.1.3, 6.2.2.3 and 7.1.
[TS 36.322, clause 5.1.2.1.1]
When delivering a new UMD PDU to lower layer, the transmitting UM RLC entity shall:
- set the SN of the UMD PDU to VT(US), and then increment VT(US) by one.
[TS 36.322, clause 5.1.2.2]
The receiving UM RLC entity shall maintain a reordering window according to state variable VR(UH) as follows:
- a SN falls within the reordering window if (VR(UH) – UM_Window_Size) <= SN < VR(UH);
- a SN falls outside of the reordering window otherwise.
When receiving an UMD PDU from lower layer, the receiving UM RLC entity shall:
- either discard the received UMD PDU or place it in the reception buffer (see sub clause 5.1.2.2.2);
- if the received UMD PDU was placed in the reception buffer:
- update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop t-Reordering as
needed (see sub clause 5.1.2.2.3);
When an UMD PDU with SN = x is received from lower layer, the receiving UM RLC entity shall:
- if VR(UR) < x < VR(UH) and the UMD PDU with SN = x has been received before; or
- if (VR(UH) – UM_Window_Size) <= x < VR(UR):
- discard the received UMD PDU;
- else:
- place the received UMD PDU in the reception buffer.
When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall:
- if x falls outside of the reordering window:
- update VR(UH) to x + 1;
- reassemble RLC SDUs from any UMD PDUs with SN that falls outside of the reordering window, remove
RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the
RLC SN if not delivered before;
- if VR(UR) falls outside of the reordering window:
ETSI
- set VR(UR) to (VR(UH) – UM_Window_Size);
- if the reception buffer contains an UMD PDU with SN = VR(UR):
- update VR(UR) to the SN of the first UMD PDU with SN > current VR(UR) that has not been received;
- reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing
so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered
before;
[TS 36.322, clause 6.2.1.3]
[TS 36.322, clause 6.2.2.3]
The SN field indicates the sequence number of the corresponding UMD…The sequence number is incremented by one
for every UMD...
[TS 36.322, clause 7.1]
All state variables and all counters are non-negative integers.
All state variables related to UM data transfer can take values from 0 to [2[sn-FieldLength] – 1]. All arithmetic operations
contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e.
final value = [value from arithmetic operation] modulo 2[sn-FieldLength].
When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.
VR(UH) – UM_Window_Size shall be assumed as the modulus base at the receiving side of an UM RLC entity. This
modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. (VR(UH) –
UM_Window_Size) <= SN < VR(UH) is evaluated as [(VR(UH) – UM_Window_Size) – (VR(UH) –
UM_Window_Size)] modulo 2[sn-FieldLength] <= [SN – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] < [VR(UH)
– (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength]).
Each transmitting UM RLC entity shall maintain the following state variables:
a) VT(US)
This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU. It is initially set to
0, and is updated whenever the UM RLC entity delivers an UMD PDU with SN = VT(US).
Each receiving UM RLC entity shall maintain the following state variables:
a) VR(UR) – UM receive state variable
ETSI
This state variable holds the value of the SN of the earliest UMD PDU that is still considered for reordering. It is
initially set to 0.
b) VR(UX) – UM t-Reordering state variable
This state variable holds the value of the SN following the SN of the UMD PDU which triggered t-Reordering.
c) VR(UH) – UM highest received state variable
This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received
UMD PDUs, and it serves as the higher edge of the reordering window. It is initially set to 0.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.5.1.3.1-1
Table 7.2.2.5.1.3.1-1: RLC parameters
Uplink RLC
Downlink RLC

U-S Message/PDU/SDU
- EXCEPTION: Step 3 to 4 is executed 31 times. - - - -
1 The SS transmits an UMD PDU. SN equals 0. <-- UMD PDU - -
2 Check: Does the UE transmit an UMD PDU --> UMD PDU 1 P
with SN = 0?
3 The SS transmits an UMD PDU. SN equals 1 <-- UMD PDU - -
and is incremented for each PDU transmitted.
with SN increased by 1 compared with the
previous one?
6 Check: Does the UE transmit an UMD PDU --> UMD PDU 3, 4 P
with SN=0?
None.
ETSI
7.2.2.5.2 UM RLC / 10-bit SN / Correct use of Sequence numbering

(1)
ensure that {
then { UE sets the Sequence Number field equal to 0 }
}
(2)
ensure that {
}
(3)
ensure that {
}
(4)
ensure that {
}
5.1.2.1.1, 5.1.2.2, 6.2.1.3, 6.2.2.3 and 7.1.
[TS 36.322, clause 5.1.2.1.1]
When delivering a new UMD PDU to lower layer, the transmitting UM RLC entity shall:
- set the SN of the UMD PDU to VT(US), and then increment VT(US) by one.
[TS 36.322, clause 5.1.2.2]
ETSI
- else:
before;
[TS 36.322, clause 6.2.1.3]
[TS 36.322, clause 6.2.2.3]
The SN field indicates the sequence number of the corresponding UMD…The sequence number is incremented by one
for every UMD...
[TS 36.322, clause 7.1]
All state variables related to UM data transfer can take values from 0 to [2[sn-FieldLength]– 1]. All arithmetic operations
contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e.
final value = [value from arithmetic operation] modulo 2[sn-FieldLength]).
When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.
ETSI
VR(UH) – UM_Window_Size shall be assumed as the modulus base at the receiving side of an UM RLC entity. This
modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. (VR(UH) –
UM_Window_Size) <= SN < VR(UH) is evaluated as [(VR(UH) – UM_Window_Size) – (VR(UH) –
UM_Window_Size)] modulo 2[sn-FieldLength] <= [SN – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] < [VR(UH)
– (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength]).
Each transmitting UM RLC entity shall maintain the following state variables:
a) VT(US)
This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU. It is initially
set to 0, and is updated whenever the UM RLC entity delivers an UMD PDU with SN = VT(US).
Each receiving UM RLC entity shall maintain the following state variables:
a) VR(UR) – UM receive state variable
This state variable holds the value of the SN of the earliest UMD PDU that is still considered for reordering. It is
initially set to 0.
b) VR(UX) – UM t-Reordering state variable
This state variable holds the value of the SN following the SN of the UMD PDU which triggered t-Reordering.
c) VR(UH) – UM highest received state variable
This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received
UMD PDUs, and it serves as the higher edge of the reordering window. It is initially set to 0.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with PDCP Data PDUs using 7 bit SN length.
ETSI

U-S Message/PDU/SDU
- EXCEPTION: Steps 3 to 4 are executed 1023 - - - -
times.
with SN = 0?
3 The SS transmits an UMD PDU. SN equals 1 <-- UMD PDU - -
and is incremented for each PDU transmitted.
previous one?
6 Check: Does the UE transmit an UMD PDU --> UMD PDU 3, 4 P
with SN=0?
None.
7.2.2.6 UM RLC / Concatenation, segmentation and reassembly

(1)
ensure that {
when { The UE has multiple RLC SDUs in the transmission buffer that fits into the available UMD
PDU size }
then { The UE concatenates the RLC SDUs in the transmission buffer into one UMD PDU and
transmits it}
}
(2)
ensure that {
when { The UE receives UMD PDUs containing concatenated RLC SDUs}
then { The UE reassembles the RLC SDUs in accordance with the Framing Info and Length Indicators
indicated in UMD PDUs }
}
(3)
ensure that {
when { The UE has RLC SDU in the transmission buffer that does not fit into the available UMD PDU
size }
then { The UE segments the RLC SDU in accordance with the Framing Info and Length Indicators
indicated in UMD PDUs }
}
4.2.1.2.2, 4.2.1.2.3, 4.4, 6.2.1.3 and 6.2.2.6.
[TS 36.322, clause 4.2.1.2.2]
When a transmitting UM RLC entity forms UMD PDUs from RLC SDUs, it shall:
- segment and/or concatenate the RLC SDUs so that the UMD PDUs fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity notified by lower layer;
ETSI
- include relevant RLC headers in the UMD PDU.
[TS 36.322, clause 4.2.1.2.3]
When a receiving UM RLC entity receives UMD PDUs, it shall:
- reassemble RLC SDUs from the reordered UMD PDUs (not accounting for RLC PDUs for which losses have
been detected) and deliver the RLC SDUs to upper layer in ascending order of the RLC SN;
[TS 36.322, clause 4.4]
The following functions are supported by the RLC sub layer:
- concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer);
[TS 36.322, clause 6.2.1.3]
UMD PDU consists of a Data field and an UMD PDU header.
UMD PDU header consists of a fixed part (fields that are present for every UMD PDU) and an extension part (fields
that are present for an UMD PDU when necessary). The fixed part of the UMD PDU header itself is byte aligned and
consists of a FI, an E and a SN. The extension part of the UMD PDU header itself is byte aligned and consists of E(s)
and LI(s).
An UMD PDU header consists of an extension part only when more than one Data field elements are present in the
UMD PDU, in which case an E and a LI are present for every Data field element except the last. Furthermore, when an
UMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI.
Figure 6.2.1.3-1: UMD PDU with 5 bit SN (No LI)
ETSI
Figure 6.2.1.3-2: UMD PDU with 10 bit SN (No LI)
Figure 6.2.1.3-3: UMD PDU with 5 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, …)
FI E SN Oct 1
E LI1 Oct 2
LI1 E LI2 Oct 3
LI2 Oct 4
E LIK-1 Oct [2+1.5*K-3]
LIK-1 E LIK Oct [2+1.5*K-2]
LIK Oct [2+1.5*K-1]
Data Oct [2+1.5*K]
Oct N
Figure 6.2.1.3-4: UMD PDU with 5 bit SN (Even number of LIs, i.e. K = 2, 4, 6, …)
ETSI
Figure 6.2.1.3-5: UMD PDU with 10 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, …)
R1 R1 R1 FI E SN Oct 1
SN Oct 2
E LI1 Oct 3
LI1 E LI2 Oct 4
LI2 Oct 5
E LIK-1 Oct [2+1.5*K-2]
LIK Oct [2+1.5*K]
Data Oct [2+1.5*K+1]
Oct N
Figure 6.2.1.3-6: UMD PDU with 10 bit SN (Even number of LIs, i.e. K = 2, 4, 6, …)
[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
ETSI
Value Description
System Simulator:
- Cell 1.
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS does not allocate any uplink grant. - - - -
2 The SS transmits UMD PDU#1. This PDU <-- UMD PDU#1 (RLC SDU#1) - -
carries SDU#1 with size of 50 bytes.
4 SS transmits UL grants to enable UE to return <-- (UL grants) - -
RLC SDU#1 and RLC SDU#2 both in one
UMD PDU.
5 Check: Does UE transmit RLC SDU#1 and --> UMD PDU#1 (RLC SDU#1 and 1 P
RLC SDU#2 within UMD PDU with FI field set RLC SDU#2)
to ‘00’, E field in the fixed part set to ‘1’, first E
field in the extension part set to ‘0’ and first LI
field set to 50 bytes?
5A The SS does not allocate any uplink grant. - - - -
6 SS transmits an UMD PDU#3 including RLC <-- UMD PDU#3 (RLC SDU#3 and - -
SDU#3 and RLC SDU#4 each with size of 50 RLC SDU#4)
bytes. Header of UMD PDU#3 contains
FI=’00’, E=’1’, SN=2, E1=’0’, LI1=’50’.
7 The SS waits for 60 ms and then allocates 2 <-- (UL grants) - -
UL grants (UL grant allocation type 2) with a
time spacing of 5 ms to enable UE to return
each RLC SDU in one UMD PDU.
8 Check: Does UE transmit RLC SDU#3 within --> UMD PDU#3 (RLC SDU#3) 2 P
an UMD PDU with FI field set to ‘00’ and E
field in the fixed part set to ‘0’?
9 Check: Does UE transmit RLC SDU#4 within --> UMD PDU#4 (RLC SDU#4) 2 P
an UMD PDU with FI field set to ‘00’ and E
field in the fixed part set to ‘0’?
11 The SS waits for 60 ms and then allocates 2 <-- (UL grants) - -
time spacing of 5 ms to enable UE to return
RLC SDU#5 in two UMD PDUs.
st
12 Check: Does UE transmit 1 part of RLC --> UMD PDU#5 3 P
SDU#5 within UMD PDU#5 with FI field set to
‘01’ and E field in the fixed part set to ‘0’?
13 Check: Does UE transmit last part of RLC --> UMD PDU#6 3 P
SDU#5 within an UMD PDU#6 with FI field set
to ‘10’and E field in the fixed part set to ‘0’?
None.
7.2.2.7 UM RLC / In sequence delivery of upper layer PDUs without residual loss of
RLC PDUs / Maximum re-ordering delay below t-Reordering
(1)
with { UE in E-UTRAN RRC_CONNECTED state }
ensure that {
when { UE receives missing PDUs whose SN is within the reordering window before t-Reordering has
expired }
then { RLC reassembles and reorders the UMD PDUs and delivers them to the upper layer in
sequence }
}
ETSI
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 5.1.2.2.
[TS 36.322, clause 5.1.2.2]
- else:
before;
- if t-Reordering is running:
- if VR(UX) <= VR(UR); or
- if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH)::
- stop and reset t-Reordering;
- if t-Reordering is not running (includes the case when t-Reordering is stopped due to actions above):
ETSI
- if VR(UH) > VR(UR):
- start t-Reordering;
- set VR(UX) to VR(UH).
System Simulator:
- Cell 1.
UE:
None.
Preamble
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.7.3.1-1
Downlink RLC
t-Reordering ms200

U-S Message
1 The SS transmits an UMD PDU. This PDU <-- UMD PDU#1 - -
carries SDU#1. SN equals 0.
contains the last part of SDU#4. SN equals 3.
The UE starts t-Reordering.
st
contains the last part of SDU#3, and the 1
part of SDU#4. SN equals 2.
st
carries SDU#2 and the 1 part of SDU#3. SN
equals 1. (Note)
5A The SS waits for 60 ms and then allocates 3 - - - -
time spacing of 5 ms of size enough for the UE
to loop back one SDU in one UMD PDU
Note: The UE stops t-Reordering, reassembles UMD PDUs and delivers RLC SDU#2, RLC SDU#3 and RLC
SDU#4 to the upper layer in sequence.
None.
ETSI
7.2.2.8 UM RLC / In sequence delivery of upper layer PDUs without residual loss of
RLC PDUs / Maximum re-ordering delay exceeds t-Reordering
(1)
ensure that {
when { a PDU is received out of order after t-Reordering has expired }
then { UE discards the corresponding PDU and delivers all correctly received RLC SDUs to upper
layer in the correct order }
}
5.1.2.2.3 and 5.1.2.2.4.
[TS 36.322, clause 5.1.2.2.2]
- else:
[TS 36.322, clause 5.1.2.2.3]
before;
- if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH):
ETSI
[TS 36.322, clause 5.1.2.2.4]
When t-Reordering expires, the receiving UM RLC entity shall:
- update VR(UR) to the SN of the first UMD PDU with SN >= VR(UX) that has not been received;
- reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so
and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Downlink RLC
t-Reordering ms200

U-S Message
1 The SS transmits RLC PDU#1 containing first <-- UMD PDU#1 - -
Note T1
2 The SS does not transmit RLC PDU#2 - - - -
containing last segment of RLC SDU#1.
3 The SS transmits RLC PDU#3 containing RLC <-- UMD PDU#3 - -
SDU#2.
3A Check 1: Does the UE transmit RLC SDU#2 --> (RLC SDU#2) 1 P
after t-Reordering (200 ms) expiry?
Note T2
Check 2: Is (T2 – T1) > t-reordering?
3B The SS transmits RLC PDU#2 containing last <-- UMD PDU#2 - -
4 Check: Does the UE transmit RLC SDU#1 --> (RLC SDU#1) 1 F
within 100 ms?
ETSI
None.
7.2.2.9 UM RLC / In sequence delivery of upper layer PDUs with residual loss of
RLC PDUs / Maximum re-ordering delay exceeds t-Reordering
(1)
ensure that {
when { UE detects that RLC PDUs constructing different RLC SDUs are lost }
then { UE delivers all received RLC SDUs to upper layer in the correct order }
}
5.1.2.2.3 and 5.1.2.2.4.
[TS 36.322, clause 5.1.2.2.2]
- else:
[TS 36.322, clause 5.1.2.2.3]
before;
- if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH):
ETSI
[TS 36.322, clause 5.1.2.2.4]
When t-Reordering expires, the receiving UM RLC entity shall:
- update VR(UR) to the SN of the first UMD PDU with SN >= VR(UX) that has not been received;
- reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so
and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;
- start t-Reordering.;
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.9.3.1-1
Downlink RLC
t-Reordering ms200
ETSI

U-S Message
1 The SS transmits UMD PDU#1 containing first <-- UMD PDU#1 - -
2 The SS does not transmit UMD PDU#2 - - - -
4 The SS transmits UMD PDU#4 containing last <-- UMD PDU#4 - -
6 The SS does not transmit UMD PDU#6 - - - -
8 The SS transmits UMD PDU#8 containing last <-- UMD PDU#8 - -
9 Wait for 200 ms to ensure that t-Reordering for - - - -
the UMD PDU#2 expires.
11 Wait for 200 ms to ensure that t-Reordering for - - - -
the UMD PDU#6 expires.
None.
7.2.2.10 UM RLC / Duplicate detection of RLC PDUs

(1)
ensure that {
when { UE receives duplicate UMD PDUs }
then { UE discards the duplicate UMD PDUs }
}
(2)
ensure that {
when { UE receives UMD PDUs whose SN is within the reordering window and duplicate UMD PDUs }
then { UE discards the duplicate UMD PDUs }
}
4.2.1.2.3 and 5.1.2.2.2.
[TS 36.322, clause 4.2.1.2.3]
When a receiving UM RLC entity receives UMD PDUs, it shall:
- detect whether or not the UMD PDUs have been received in duplication, and discard duplicated UMD PDUs;
- reorder the UMD PDUs if they are received out of sequence;
- detect the loss of UMD PDUs at lower layers and avoid excessive reordering delays;
ETSI
- reassemble RLC SDUs from the reordered UMD PDUs (not accounting for RLC PDUs for which losses have
been detected) and deliver the RLC SDUs to upper layer in ascending order of the RLC SN;
[TS 36.322, clause 5.1.2.2.2]
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.10.3.1-1.
Parameter Value
t-Reordering ms100
ETSI

U-S Message
st
contains SDU#2 and the 1 part of SDU# 3.
SN equals 1.
6 The UE transmit RLC SDU#2. --> (RLC SDU#2) - -
st
contains SDU#2 and the 1 part of SDU#3. SN
equals 1.
A not allocate any uplink grant.
10 The SS enables the indication of scheduling - - - -
B requests till step 15.
11 After 100 ms the SS transmits an UMD PDU. <-- UMD PDU#5 - -
This PDU carries SDU#5. SN equals 4.
14 Check: Does the UE transmit scheduling --> (SR) 2 F
request before transmission of UMD PDU at
step 15?
15 After 75 ms from step 11 the SS transmits an <-- UMD PDU#4 - -
UMD PDU. This PDU carries SDU#4. SN
equals 3.
15 The SS waits for 60 ms and then allocates 1 <-- (UL Grant) - -
A UL grant of size enough for the UE to loop
back 3 RLC SDU in one UMD PDU
16 SS receives SDU#4, SDU#5 and SDU#6 in a --> (RLC SDU#4, RLC SDU#5 and 1,2 P
single PDU RLC SDU#6)
17 Void
18 Void
None.
7.2.2.11 UM RLC / RLC re-establishment procedure

(1)
ensure that {
when { RLC re-establishment is performed upon request by RRC }
then { The UE discards all UMD PDUs where no RLC SDUs can be reassembled }
}
(2)
ensure that {
when { RLC re-establishment is performed upon request by RRC }
ETSI
then { The UE resets variable VT(US), VR(UH) and VR(UR) to its initial value }
}
4.2.1.2.3 and 5.4.
[TS 36.322, clause 4.2.1.2.3]
At the time of RLC re-establishment, the receiving UM RLC entity shall:
- if possible, reassemble RLC SDUs from the UMD PDUs that are received out of sequence and deliver them to
upper layer;
- discard any remaining UMD PDUs that could not be reassembled into RLC SDUs;
- initialize relevant state variables and stop relevant timers.
[TS 36.322, clause 5.4]
RLC re-establishment is performed upon request by RRC, and the function is applicable for AM, UM and TM RLC
entities.
When RRC indicates that an RLC entity should be re-established, the RLC entity shall:
- if it is a receiving UM RLC entity:
- when possible, reassemble RLC SDUs from UMD PDUs with SN < VR(UH), remove RLC headers when
doing so and deliver all reassembled RLC SDUs to upper layer in ascending order of the RLC SN, if not
delivered before;
- discard all remaining UMD PDUs;
- reset all state variables to their initial values.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- UE is in Loopback Activated state (state 4) according to TS 36.508 clause 4.5 [18] with the exceptions listed in
table 7.2.2.11.3.1-1 applicable for the configured UM DRB.
Downlink RLC
t-Reordering ms200
ETSI

U-S Message
1 The SS transmits UMD PDU#1. Header of <-- UMD PDU#1 - -
UMD PDU#1 contains SN=0. This PDU carries
RLC SDU#1.
st
the 1 segment of SDU#2.
4 SS performs a RRC Connection - - - -
Reconfiguration procedure including the
mobilityControlInfo IE in
RRCConnectionReconfiguration triggering
RLC re-establishment.
the last segment of RLC SDU#2. The UE
starts t-Reordering.
7 300 ms (1.5 * t-Reordering) after step 5 the SS <-- UMD PDU#4 - -
transmits UMD PDU#4. Header of UMD
PDU#4 contains SN=3. This PDU carries RLC
SDU#3.
8 The UE transmit RLC SDU#3. Header of UMD --> (RLC SDU#3) - -
PDU carrying RLC SDU#3 contains SN=0.
RLC SDU#4.
10 The UE transmits RLC SDU#4. Header of --> (RLC SDU#4) - -
UMD PDU carrying RLC SDU#4 contains
SN=1.
11 SS performs a RRC Connection - - - -
Reconfiguration procedure including the
MobilityControlInfo IE in
RRCConnectionReconfiguration triggering
RLC re-establishment.
RLC SDU#5.
13 Check 1: Does the UE transmit RLC SDU#5? --> (RLC SDU#5) 2 P
Check 2: Does header of UMD PDU carrying
RLC SDU#5 contain SN=0?
Table 7.2.2.11.3.3-1: RRCConnectionReconfiguration (step 4 and step 11, Table 7.2.2.11.3.2-1)
Table 7.2.2.11.3.3-2: MobilityControlInfo (step 4 and step 11, Table 7.2.2.11.3.2-1)

MobilityControlInfo ::= SEQUENCE {
Cell 1
}
ETSI
7.2.3 Acknowledged mode

7.2.3.1 AM RLC / Concatenation and reassembly
(1)
ensure that {
when { The UE has multiple RLC SDUs in the transmission buffer that fits into the available AMD
PDU size }
then { The UE concatenates the RLC SDUs in the transmission buffer into an AMD PDU and transmits
it}
}
(2)
ensure that {
when { The UE receives an AMD PDUs containing concatenated RLC }
then { The UE reassembles the RLC SDUs in accordance with the Framing Info and Length Indicators
indicated in AMD PDUs }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.322, clauses 4.2.1.3.2 ,
4.2.1.3.3, 6.2.1.4 and 6.2.2.6.
[TS 36.322, clause 4.2.1.3.2]
When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs, it shall:
- segment and/or concatenate the RLC SDUs so that the AMD PDUs fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity notified by lower layer.
[TS 36.322, clause 4.2.1.3.3]
When the receiving side of an AM RLC entity receives RLC data PDUs, it shall:
....
- reassemble RLC SDUs from the reordered RLC data PDUs and deliver the RLC SDUs to upper layer in
sequence.
[TS 36.322, clause 6.2.1.4]
AMD PDU consists of a Data field and an AMD PDU header.
AMD PDU header consists of a fixed part (fields that are present for every AMD PDU) and an extension part (fields
that are present for an AMD PDU when necessary). The fixed part of the AMD PDU header itself is byte aligned and
consists of a D/C, a RF, a P, a FI, an E and a SN. The extension part of the AMD PDU header itself is byte aligned and
consists of E(s) and LI(s).
An AMD PDU header consists of an extension part only when more than one Data field elements are present in the
AMD PDU, in which case an E and a LI are present for every Data field element except the last. Furthermore, when an
AMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI.
ETSI
Figure 6.2.1.4-1: AMD PDU (No LI)
Figure 6.2.1.4-2: AMD PDU (Odd number of LIs, i.e. K = 1, 3, 5, ...)
D/C RF P FI E SN Oct 1
SN Oct 2
E LI1 Oct 3
LI1 E LI2 Oct 4
LI2 Oct 5
E LIK-1 Oct [2+1.5*K-2]

LIK Oct [2+1.5*K]
Data Oct [2+1.5*K+1]
Oct N
Figure 6.2.1.4-3: AMD PDU (Even number of LIs, i.e. K = 2, 4, 6, ...)
ETSI
[TS 36.322, clause 6.2.2.6]
Value Description
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.3.1.3.1-
1.
Parameter Value
t-StatusProhibit 500 ms
ETSI

U-S Message
1 During the whole test sequence, the SS should - - - -
not allocate UL grants unless when explicitly
stated so in the procedure.
2 The SS transmits an AMD PDU including two <-- AMD PDU(AMD PDU - -
RLC SDUs of size 40 bytes each with poll bit header(D/C=’1’, RF=’0’, P=’1’,
set to ‘1’. FI=’00’,E=’1’, SN=’0’,E1=’0’,
LI1=’40’ bytes), 2 RLC SDUs of 40
bytes)
3 The SS waits for 60 ms and the allocates an <-- (UL grant, 776 bits) - -
UL grant (UL grant allocation type 3) of size
776 bits (Note 1).
4 Check: Does the UE transmit a STATUS PDU --> STATUS PDU (ACK SN=1) 2 P
with positive acknowledgement?
5 Check: Does the UE transmit two RLC SDUs --> AMD PDU(AMD PDU 1, 2 P
within an AMD PDU with FI field set to ‘00’, header(P=’1’, FI=’00’, E=’1’,SN=0,
first E field in the fixed part set to ‘1’, first E E1=’0’, LI1=’40’) ), two RLC SDUs
field in the extension part set to ‘0’, first LI field of size 40 bytes)
set to 40 bytes?
6 The SS transmits a STATUS PDU. <-- STATUS PDU (ACK SN=1) - -
7 After 500 ms the SS transmits an AMD PDU <-- AMD PDU(AMD PDU - -
including three RLC SDU of size 40 bytes with header(D/C=’1’, RF=’0’, P=’1’,
P field set to "1". FI=’00’,E=’1’, SN=’1’, E1=’1’,
LI1=’40’ bytes, E2=’0’, LI2=’40’
bytes), three RLC SDUs of size 40
bytes)
8 The SS waits for 60 ms and then allocates an <-- (UL grant, 1096 bits) - -
UL grant (UL grant allocation type 3) of size
1096 bits. (Note 2).
9 Check: Does the UE transmit a STATUS PDU --> STATUS PDU (ACK SN=2) 2 P
with positive acknowledgement?
10 Check: Does the UE transmit three RLC SDUs --> AMD PDU(AMD PDU 1, 2 P
within an AMD PDU with FI field set to “00”, header(P=’1’, FI=’00’, SN=1,
first E field in the fixed part set to ‘1’, first E E1=’1’, LI1=’40’, E2=’0’, LI2=’40’),
field in the extension part set to ‘1’, first LI field three RLC SDUs of size 40 bytes)
set to 40 bytes, second E field in the extension
part set to ‘0’, second LI field set to 40 bytes
and P field set to “1”?
Note 1 UL grant of 776 bits (ITBS=11, NPRB=4, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will fit two
RLC SDUs of 40 bytes within one AMD PDU. MAC PDU of 776 bits=97 bytes fits an AMD PDU payload of
80 bytes (two 40 byte RLC SDUs) + 4 bytes AMD PDU header + 13 bytes spare for MAC header and
possible RLC STATUS PDU and BSR report.
Note 2 UL grant of 1096 bits (ITBS=8, NPRB=8, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will fit three
RLC SDUs of 40 bytes within one AMD PDU. MAC PDU of 1096 bits=137 bytes fits an AMD PDU payload
of 120 bytes (three 40 byte RLC SDUs) + 5 bytes AMD PDU header + 12 bytes spare for MAC header and
possible RLC STATUS PDU and BSR report.
None.
7.2.3.2 AM RLC / Segmentation and reassembly / No PDU segmentation

(1)
ensure that {
when { the UE has a RLC SDU with larger size than available AMD PDU size in the transmission
buffer }
ETSI
then { the UE segments the RLC SDU in accordance with the available AMD PDU size }
}
(2)
ensure that {
when { the UE receives AMD PDUs containing a segmented RLC SDU }
then { the UE reassembles the RLC SDUs in accordance with the Framing Info and Length Indicators
indicated in the AMD PDUs }
}
4.2.1.3.3 and 6,2.2.6.
[TS 36.322, clause 4.2.1.3.2]
[TS 36.322, clause 4.2.1.3.3]
....
sequence.
[TS 36.322, clause 6.2.2.6]
Value Description
System Simulator:
- Cell 1.
UE:
None.
ETSI
Preamble:

U-S Message/PDU/SDU
2 The SS transmits a RLC SDU of size 80 bytes <-- (RLC SDU#1) - -
segmented into two AMD PDUs. The two AMD AMD PDU#1(FI=’01’,SN=0)
PDUs are transmitted in separate TTIs. AMD PDU#2(FI=’10’,SN=1)
3 60 ms after step 2 the SS allocates 2 UL <-- (UL grants) - -
grants (UL grant allocation type 2) with a time
spacing of 5 ms of size 392 bits. (Note 1).
4 Check: Does the UE return a RLC SDU with --> (RLC SDU#1) 1,2 P
equal content as sent in downlink in step 2 AMD PDU#1
segmented into two AMD PDUs and received AMD PDU#2
in different TTIs?
(Note2: Details for AMD PDU#2)
6 The SS sends a RLC SDU of size 120 bytes <-- (RLC SDU#2) - -
octets segmented into three AMD PDUs. AMD PDU#1(FI=’01’,SN=2)
AMD PDU#2(FI=’11’,SN=3)
AMD PDU#3(FI=’10’,SN=4)
7 60 ms after step 6 the SS allocates 3 UL <-- (UL grants) - -
grants (UL grant allocation type 2) with a time
spacing of 5 ms of size 392 bits. (Note 1).
8 Check: Does the UE return a RLC SDU with --> (RLC SDU#2) 1,2 P
equal content as sent in downlink in step 6 AMD PDU#1
segmented into three AMD PDUs where each AMD PDU#2
AMD PDU is received in different TTI? AMD PDU#3
(Note2: Details for AMD PDU#3)
Note 1: UL grant of 392 bits (ITBS=8, NPRB=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen to force the UE to
segment the returned UL RLC SDU into multiple AMD PDUs. An UL grant of 392 bits=49 bytes allows the
UE to transmit one AMD PDU of maximum 46 bytes (49 bytes – 2 byte AMD PDU header - minimum 1 byte
MAC header). UE at step 4 and step 8 during transmission of AMD PDU#1 will transmit BSR MCE which
will take 2 bytes and hence AMD PDU size will be 44 bytes.
Note2: Polling bit will be set for this PDU by the UE and SS transmits a STATUS PDU.
None.
7.2.3.3 AM RLC / Segmentation and reassembly / Framing info field

(1)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment containing a FI field set to 00 }
then { UE correctly decodes the received AMD PDU or AMD PDU segment }
}
(2)
ensure that {
}
ETSI
(3)
ensure that {
then { UE correctly decodes the received AMD PDU or AMD PDU segment}
}
(4)
ensure that {
}
[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
Value Description
System Simulator:
- Cell 1.
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS transmits AMD PDU#1 containing a <-- AMD PDU#1 - -
2A The SS transmits a STATUS PDU. <-- STATUS PDU (ACK SN=1) - -
3 The SS transmits AMD PDU#2 containing the <-- AMD PDU#2 - -
4
7 The t-PollRetransmit timer for RLC PDU#5 - - - -
expires and SS assumes that the transmission
of AMD PDU#5 containing a complete RLC
SDU#3 and a complete RLC SDU#4 is failed
and consider RLC PDU#5 for re-transmission
8 The SS transmits AMD PDU segment <-- AMD PDU segment - -
containing a complete RLC SDU#3 (FI field =
00).
containing the first segment of RLC SDU#4 (FI
field = 01).
containing the second segment of RLC SDU#4
(FI field = 11).
containing the last segment of RLC SDU#4 (FI
field = 10).
4
None.
7.2.3.4 AM RLC / Segmentation and reassembly / Different numbers of length

indicators
(1)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment with no LI field }
}
(2)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment with one LI field }
}
ETSI
(3)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment with two LI fields }
}
[TS 36.322, clause 6.2.2.5]
Length: 11 bits.
The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU
delivered/received by an UM or an AM RLC entity. The first LI present in the RLC DATA PDU header corresponds to
the first Data field element present in the Data field of the RLC DATA PDU, the second LI present in the RLC DATA
PDU header corresponds to the second Data field element present in the Data field of the RLC DATA PDU, and so on.
The value 0 is reserved.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
1.
Parameter Value
t-Reordering 150 ms
ETSI

U-S Message
- During the whole test sequence, the SS should - - - -
complete RLC SDU#1 without LI field.
2 The SS transmits an uplink grant allowing the <-- (UL grant) - -
UE to transmit 1 RLC SDU.
3 Check: Does the UE transmit an AMD PDU --> AMD PDU (RLC SDU#1) 1 P
containing RLC SDU#1?
complete RLC SDU#2 and a complete RLC
SDU#3 with one LI field.
5 The SS waits for 60 ms then assigns an UL <-- (UL grant) - -
grant sufficient for the UE to loopback RLC
SDU#2 and RLC SDU#3.
6 Check: Does the UE transmit an AMD PDU --> AMD PDU (RLC SDU#2, RLC 2 P
containing RLC SDU#2 and RLC SDU#3 in its SDU#3)
data field?
complete RLC SDU#4, a complete RLC
SDU#5 and a complete RLC SDU#6 with two
LI fields.
grant sufficient for the UE to loopback RLC
SDU#4, RLC SDU#5 and RLC SDU#6.
containing RLC SDU#4, RLC SDU#5 and RLC SDU#5, RLC SDU#6)
SDU#6 in its data field?
12 Void - - - -
13 The t-PollRetransmit timer for AMD PDU#4 - - - -
expires and SS assumes that the transmission
of AMD PDU#4 containing a complete RLC
SDU#7, a complete RLC SDU#8, a complete
RLC SDU#9, a complete RLC SDU#10, a
SDU#12 is failed and consider AMD PDU#4
for re-transmission.
containing a complete RLC SDU#7 without LI
field.
15 The SS waits for 60 ms and then assigns an <-- (UL grant) - -
uplink grant (UL grant allocation type 3)
allowing the UE to transmit 1 RLC SDU.
16 Check: Does the UE transmit an AMD PDU --> AMD PDU (RLC SDU#7) 1 P
containing RLC SDU#7?
A
containing a complete RLC SDU#8 and a
complete RLC SDU#9 with one LI field.
UL grant (UL grant allocation type 3) sufficient
for the UE to loopback RLC SDU#8 and RLC
SDU#9.
containing RLC SDU#8 and RLC SDU#9 in its SDU#9)
data field?
ETSI

containing a complete RLC SDU#10, a
SDU#12 with two LI fields.
UL grant (UL grant allocation type 3) sufficient
for the UE to loopback RLC SDU#10, RLC
SDU#11 and RLC SDU#12.
containing RLC SDU#10, RLC SDU#11 and SDU#11, RLC SDU#12)
RLC SDU#12 in its data field?
25 Void - - - -
None.
7.2.3.5 AM RLC / Reassembly / LI value > PDU size

(1)
ensure that {
when { UE receives PDU with "Length Indicators" that point beyond the end of the PDU }
then { UE discards PDU }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clauses 5.5.1
and 6.2.2.5.
[TS 36.322, clause 5.5.1]
[TS 36.322, clause 6.2.2.5]
Length: 11 bits.
The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU. The
first LI present in the RLC data PDU header corresponds to the first Data field element present in the Data field of the
RLC data PDU, the second LI present in the RLC data PDU header corresponds to the second Data field element
present in the Data of the RLC data PDU, and so on. The value 0 is reserved.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with the loopback size set to 98 bytes.
ETSI

U-S Message/PDU/SDU
1 The SS transmits an AMD PDU containing the <-- AMD PDU#1 (SN = 0) - -
first half (50 bytes) of SDU#1 in its data field to
the UE.
2 The SS transmits an AMD PDU containing the <-- AMD PDU#2 (SN=1) - -
second half (50 bytes) of SDU#1 and the first
half (50 bytes) of SDU#2 in its data field to the
UE. LI associated with PDU#2 has a value >
PDU size, i.e. > 100.
UE.
second half (50 bytes) of SDU#3 in its data
field to the UE.
4A 100 ms after step 4 t he SS assigns an UL <-- (UL grant, 56 bits) - -
grant (UL grant allocation type 3) of size 56
bits (Note 1).
5 Check: Does the UE transmit a STATUS PDU --> STATUS PDU 1 P
with NACK_SN field set to 1?
UE. The LI is correct.
6A The SS waits for 60 ms to ensure UE RLC has
all the required SDU available in UL for
loopback.
6B The SS transmits an UL grant (UL grant <-- (UL grant, 2536 bits) - -
allocation type 3) of size 2536 bits (Note 2).
7 Check: Does the UE transmit RLC SDU#1, --> AMD PDU(RLC SDU#1, RLC 1 P
SDU#2, and SDU#3? SDU#2, RLC SDU#3)
(Note 3: Details for RLC PDU carrying RLC
SDU#3)
Note 1: UL grant of 56 bits (ITBS=1, NPRB=2, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will be enabled
to send the status PDU.
Note 2: UL grant of 2536 bits (ITBS=13, NPRB=10, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will fit all 3
SDU in one AMD PDU.
Note 3: In step 7, poll is set so SS will send STATUS PDU to UE in step 8.
None.
7.2.3.6 AM RLC / Correct use of sequence numbering

(1)
ensure that {
then { UE sets the Sequence Number field equal to 0 }
}
(2)
ETSI
ensure that {
}
(3)
ensure that {
}
(4)
ensure that {
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clauses
5.1.3.1.1, 6.2.2.3 and 7.1.
[TS 36.322, clause 5.1.3.1.1]
The transmitting side of an AM RLC entity shall prioritize transmission of RLC control PDUs over RLC data PDUs.
The transmitting side of an AM RLC entity shall prioritize retransmission of RLC data PDUs over transmission of new
AMD PDUs.
The transmitting side of an AM RLC entity shall maintain a transmitting window according to state variables VT(A)
and VT(MS) as follows:
- a SN falls within the transmitting window if VT(A) <= SN < VT(MS);
- a SN falls outside of the transmitting window otherwise.
The transmitting side of an AM RLC entity shall not deliver to lower layer any RLC data PDU whose SN falls outside
of the transmitting window.
When delivering a new AMD PDU to lower layer, the transmitting side of an AM RLC entity shall:
- set the SN of the AMD PDU to VT(S), and then increment VT(S) by one.
The transmitting side of an AM RLC entity can receive a positive acknowledgement (confirmation of successful
reception by its peer AM RLC entity) for a RLC data PDU by the following:
- STATUS PDU from its peer AM RLC entity.
When receiving a positive acknowledgement for an AMD PDU with SN = VT(A), the transmitting side of an AM RLC
entity shall:
- set VT(A) equal to the SN of the AMD PDU with the smallest SN, whose SN falls within the range VT(A) <=
SN <= VT(S) and for which a positive acknowledgment has not been received yet.
- if positive acknowledgements have been received for all AMD PDUs associated with a transmitted RLC SDU :-
send an indication to the upper layers of successful delivery of the RLC SDU.
[TS 36.322, clause 6.2.2.3]
Length: 10bits for AMD PDU, AMD PDU segments and STATUS PDUs. ...
The SN field indicates the sequence number of the corresponding ... AMD PDU. For an AMD PDU segment, the SN
field indicates the sequence number of the original AMD PDU from which the AMD PDU segment was constructed
from. The sequence number is incremented by one for every ... AMD PDU.
[TS 36.322, clause 7.1]
ETSI
...
All state variables related to AM data transfer can take values from 0 to 1023. All arithmetic operations contained in the
present document on state variables related to AM data transfer are affected by the AM modulus (i.e. final value =
[value from arithmetic operation] modulo 1024).
AMD PDUs ... are numbered integer sequence numbers (SN) cycling through the field: 0 to 1023 for AMD PDU ...
...
c) VT(S) – Send state variable
This state variable holds the value of the SN to be assigned for the next newly generated AMD PDU. It is initially set to
0, and is updated whenever the AM RLC entity delivers an AMD PDU with SN = VT(S).
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18].
ETSI

U-S Message/PDU/SDU
- During the whole test sequence, the SS should - - - -
- EXCEPTION: SS is configured 500ms in - - - -
advance for step 1 and 2. Step 1 is executed
512 times such that 1 AMD PDU is transmitted
every second radio frame. (Note 1) . Step 2 is
started 60 ms after the first DL AMD PDU has
been transmitted in step 1 (Note 1).
- EXCEPTION: In parallel to steps 1 and 2, the - - - -
behaviour described in table 7.2.3.6.3.2-2 is
running.
1 The SS transmits an AMD PDU to the UE. SN <-- AMD PDU - -
equals 0 and is incremented for each PDU
transmitted (Note 1).
2 The SS transmits 1 UL grant (UL grant <-- (UL grants) - -
allocation type 2) in every second radio frame
to enable the UE to return each received AMD
PDU in one looped back AMD PDU (Note 1).
advance for step 2B and 2C.Step 2B is
executed 512 times such that 1 AMD PDU is
transmitted every second radio frame. (Note 1)
. Step 2C is started 60 ms after the first DL
AMD PDU has been transmitted in step 2B
(Note 1).
- EXCEPTION: In parallel to steps 2B and 2C, - - - -
the behaviour described in table 7.2.3.6.3.2-3
is running.
2B The SS transmits an AMD PDU to the UE. SN <-- AMD PDU - -
equals 512 and is incremented for each PDU
transmitted.
2C The SS transmits 1 UL grant (UL grant <-- (UL grants) - -
allocation type 2) in every second radio frame
to enable the UE to return each received AMD
PDU in one looped back AMD PDU (Note 1). .
3 The SS transmits an AMD PDU to the UE. SN <-- AMD PDU - -
equals 0.
4 Void - - - -
4A The SS starts the UL default grant - - - -
transmission
5 Check: Does the UE transmit an AMD PDU --> AMD PDU 3,4 P
with SN=0?
6 The SS transmits a STATUS PDU with <-- STATUS PDU - -
ACK_SN = 1.
Note 1: 20 ms gap between transmissions both in DL and UL respectively allows TTCN to tolerate one HARQ
retransmission (FDD/TDD) per transport block, if such happen (TS 36.523-3).
Note 2: Delaying first UL grant for 60 ms, ensures that UE UL buffer does not become empty every time one UL AMD
PDU is sent i.e. UE does not enable polling for every UL AMD PDU. SS continuously transmits the grants
until it has received all PDUs in UL.
ETSI

U-S Message
1 Check: Does the UE transmit an AMD PDU --> AMD PDU 1 P
with SN = 0?
- EXCEPTION: Steps 2 and 3a1 are executed - - - -
511 times.
previous one?
EXCEPTION: Step 3a1 describes behaviour - - - -
that depends on the contents of the AMD PDU
transmitted at Step 2.
3a1 IF the UE has set the poll bit in the AMD PDU <-- STATUS PDU - -
transmitted at Step 2 THEN the SS transmits a
Status Report.

U-S Message
- EXCEPTION: Steps 1 and 2a1 are executed - - - -
512 times.
previous one?
EXCEPTION: Step 2a1 describes behaviour - - - -
that depends on the contents of the AMD PDU
transmitted at Step 1.
2a1 IF the UE has set the poll bit in the AMD PDU <-- STATUS PDU - -
transmitted at Step 1 THEN the SS transmits a
Status Report.
None.
7.2.3.7 AM RLC / Control of transmit window

(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and pending uplink data for
transmission}
ensure that {
when { AMD PDUs in transmission buffer fall outside VT(A) <= SN < VT(MS) }
then { UE does not transmit these AMD PDUs }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and pending uplink data for
transmission }
ensure that {
when { receiving a STATUS PDU where ACK_SN acknowledges at least one AMD PDU not yet acknowledged
}
then { UE transmits AMD PDUs within updated window range}
}
5.1.3.1.1, 7.1 and 7.2.
[TS 36.322, clause 5.1.3.1.1]
ETSI
...
The transmitting side of an AM RLC entity shall maintain a transmitting window according to state variables VT(A)
and VT(MS) as follows:
- a SN falls within the transmitting window if VT(A) <= SN < VT(MS);
- a SN falls outside of the transmitting window otherwise.
The transmitting side of an AM RLC entity shall not deliver to lower layer any RLC data PDU whose SN falls outside
of the transmitting window.
When delivering a new AMD PDU to lower layer, the transmitting side of an AM RLC entity shall:
- set the SN of the AMD PDU to VT(S), and then increment VT(S) by one.
The transmitting side of an AM RLC entity can receive a positive acknowledgement (confirmation of successful
reception by its peer AM RLC entity) for a RLC data PDU by the following:
When receiving a positive acknowledgement for an AMD PDU with SN = VT(A), the transmitting side of an AM RLC
entity shall:
- set VT(A) equal to the SN of the AMD PDU with the smallest SN, whose SN falls within the range VT(A) <=
SN <= VT(S) and for which a positive acknowledgment has not been received yet.
- if positive acknowledgements have been received for all AMD PDUs associated with a transmitted RLC SDU :
- send an indication to the upper layers of successful delivery of the RLC SDU.
[TS 36.322, clause 7.2]
a) AM_Window_Size
This constant is used by both the transmitting side and the receiving side of each AM RLC entity to calculate VT(MS)
from VT(A), and VR(MR) from VR(R). AM_Window_Size = 512.
...
[TS 36.322, clause 7.1]
a) VT(A) – Acknowledgement state variable
This state variable holds the value of the SN of the next AMD PDU for which a positive acknowledgment is to be
received in-sequence, and it serves as the lower edge of the transmitting window). It is initially set to 0, and is
updated whenever the AM RLC entity receives a positive acknowledgment for an AMD PDU with SN = VT(A).
b) VT(MS) – Maximum send state variable
This state variable equals VT(A) + AM_Window_Size, and it serves as the higher edge of the transmitting window.
...
System Simulator:
- Cell 1.
UE:
None.
ETSI
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the loopback size set to 100 bytes, and with
the expectations listed in table 7.2.3.7.3.1-1.
Table 7.2.3.7.3.1-1: RLC Settings
Parameter Value
PollPDU pInfinity
PollByte kBinfinity

dsr-TransMax n8

U-S Message
- The SS does not allocate any uplink grant. - - - -
- EXCEPTION: The SS is configured for step 1 - - - -
and 1A 500ms in advance. Step 1 is repeated
W+1 times, where W = AM_Window_Size. The
transmission is performed every second radio
frame. (Note 2). Step 1A is started 100 ms
after the first DL AMD PDU has been
transmitted in step 1.
- EXCEPTION: In parallel to steps 1 and 1A, the - - - -
behaviour described in table 7.2.3.7.3.2-2 is
running.
1 The SS transmits an AMD PDU containing a <-- AMD PDU - -
SDU to the UE.
1A In the following steps the SS transmits 1 UL <-- (UL grants) - -
grant (UL grant allocation type 2) in every
second radio frame to enable the UE to return
each received AMD PDU in one looped back
AMD PDU. (Note 2)
1B Void - - - -
1C Check: Does the UE transmit an AMD PDU --> AMD PDU(SN=W-1), Poll 1 P
with the Poll bit set and with the contents of the
SDU?
1D The SS starts the UL default grant - - - -
transmission
2 Check: Does the UE transmit an AMD PDU --> AMD PDU 1 F
within t-PollRetransmit/2?
3 The SS transmits a STATUS PDU to <-- STATUS PDU - -
acknowledge the W uplink AMD PDUs with
SN=0 to SN=W-1. ACK_SN = W.
3A Check: Does the UE transmit an AMD PDU --> AMD PDU(SN=W), Poll 2 P
with the Poll bit set and with the contents of the
SDU?
3B The SS transmits a STATUS PDU with <-- STATUS PDU - -
ACK_SN = W+1.
Note 1: SDUs are numbered 1,2, …, W+1
ETSI

U-S Message
- EXCEPTION: Step 1 is executed W-1 times. - - - -
1 The UE transmits an AMD PDU with the same --> AMD PDU - -
data as received in the corresponding DL AMD
PDU.
None.
7.2.3.8 AM RLC / Control of receive window

(1)
ensure that {
when { the UE receives AMD PDUs with SN outside the upper boundary of the receive window }
then { the UE discards these AMD PDUs }
}
(2)
ensure that {
when { the receive window has been moved }
then { UE continues accepting AMD PDUs within updated window range }
}
5.1.3.2.1 and 7.2.
[TS 36.322, clause 5.1.3.2.1]
The receiving side of an AM RLC entity shall maintain a receiving window according to state variables VR(R) and
VR(MR) as follows:
- a SN falls within the receiving window if VR(R) <= SN < VR(MR);
- a SN falls outside of the receiving window otherwise.
When receiving a RLC data PDU from lower layer, the receiving side of an AM RLC entity shall:
- either discard the received RLC data PDU or place it in the reception buffer (see sub clause 5.1.3.2.2);
- if the received RLC data PDU was placed in the reception buffer:
needed (see sub clause 5.1.3.2.3).
When t-Reordering expires, the receiving side of an AM RLC entity shall:
- update state variables and start t-Reordering as needed (see sub clause 5.1.3.2.4).
[TS 36.322, clause 7.2]
a) AM_Window_Size
This constant is used by both the transmitting side and the receiving side of each AM RLC entity to calculate
VT(MS) from VT(A), and VR(MR) from VR(R). AM_Window_Size = 512.
...
ETSI
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loopback size of 0 byte.

U-S Message/PDU/SDU
advance for step 1. Step 1 shall be repeated W
times, where W is AM_Window_Size. Polling
bit enabled for the Wth RLC PDU transmitted.
The SS shall set the Sequence Number field
for the first AMD PDU to 0 and increment it by
1 for every execution of Step 1. The
transmission is performed in every second
radio frame.(Note 3)
1 The SS transmits an AMD PDU to the UE <-- AMD PDU
acknowledging W PDUs? (ACK_SN = W)
3 The SS transmits the (W+1)th AMD PDU to <-- AMD PDU - -
the UE with the Sequence Number field set to
((2W mod 1024) = 0) and the Polling bit set.
4 Check: does the UE transmit a STATUS PDU --> STATUS PDU 1 P
acknowledging W PDUs? (ACK_SN = W)
(Note 1)
5 The SS transmits the (W+2)th AMD PDU to <-- AMD PDU - -
the UE with the Sequence Number field set to
W and the Polling bit set.
acknowledging W +1 PDUs? (ACK_SN field =
W+1) (Note 2)
Note 1: This shows that the UE has discarded the (W+1)th PDU.
Note 2: This shows that the UE did not discard the (W+2)th PDU and has updated the Receive Window correctly.
None.
7.2.3.9 AM RLC / Polling for status

(1)
with { UE in E-UTRA RRC_CONNECTED state and using AM RLC }
ensure that {
when { last data in the buffer was transmitted }
then { UE transmits a Poll }
}
ETSI
(2)
ensure that {
when { the t-PollRetransmit timer expires }
}
(3)
ensure that {
when { PDU_WITHOUT_POLL=pollPDU }
}
(4)
ensure that {
when { BYTE_WITHOUT_POLL=pollByte }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clauses 5.2.2.
[TS 36.322, clause 5.2.2]
Upon assembly of a new AMD PDU, the transmitting side of an AM RLC entity shall:
- increment PDU_WITHOUT_POLL by one;
- increment BYTE_WITHOUT_POLL by every new byte of Data field element that it maps to the Data field of
the RLC data PDU;
- if PDU_WITHOUT_POLL >= pollPDU; or
- if BYTE_WITHOUT_POLL >= pollByte;
- include a poll in the RLC data PDU as described below.
Upon assembly of an AMD PDU or AMD PDU segment, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC data
PDU awaiting for acknowledgements) after the transmission of the RLC data PDU; or
- if no further RLC data PDU can be transmitted after the transmission of the RLC data PDU (e.g. due to window
stalling);
To include a poll in a RLC data PDU, the transmitting side of an AM RLC entity shall:
- set the P field of the RLC data PDU to "1";
- set PDU_WITHOUT_POLL to 0;
- set BYTE_WITHOUT_POLL to 0;
After delivering a RLC data PDU including a poll to lower layer and after incrementing of VT(S) if necessary, the
transmitting side of an AM RLC entity shall:
- set POLL_SN to VT(S) – 1;
- if t-PollRetransmit is not running:
ETSI
- start t-PollRetransmit;
- else:
- restart t-PollRetransmit;
[TS 36.322, clause 5.2.2.3]
Upon expiry of t-PollRetransmit, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer are empty (excluding transmitted RLC data PDU
awaiting for acknowledgements); or
- if no new RLC data PDU can be transmitted (e.g. due to window stalling):
- consider the AMD PDU with SN = VT(S) – 1 for retransmission;
- consider any AMD PDU which has not been positively acknowledged for retransmission;
- include a poll in a RLC data PDU as described in section 5.2.2.1.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.3.9.3.1-1 and
7.2.3.9.3.1-2.
Table 7.2.3.9.3.1-1: RLC Settings
Parameter Value
pollPDU p256
pollByte kB25

dsr-TransMax n8
ETSI

U-S Message
1 The SS transmits 4 AMD PDUs such that 1 <-- AMD PDU (SN=0) - -
AMD PDU is sent every second radio frame, AMD PDU (SN=1)
each containing an RLC SDU of 2 560 bits. AMD PDU (SN=2)
(Note 2) AMD PDU (SN=3)
- EXCEPTION: In parallel to the events - - - -
described in step 1A, the step specified in
Table 7.2.3.9.3.2-2 should take place.
1A The SS waits for 100 ms after the first DL AMD - - - -
PDU has been transmitted in step 1, then
starts assigning UL grants (UL grant allocation
type 2) in every second radio frame of size 2
600 bits. (Note 1) (Note 2)
2 Check 1: Does the UE transmit an AMD PDU --> AMD PDU 2 P
with a SN in range 0 to 3 and P=1?
Record time TB.
Check 2: Is (TB – TA) = t-PollRetransmit?
transmission
3 Upon receiving the Poll, the SS transmits an <-- STATUS PDU - -
RLC Status Report.
4 Check: Does the UE retransmit an AMD PDU --> AMD PDU 2 F
within 1 sec?
5 SS performs an RRC Connection - - - -
Reconfiguration procedure changing pollPDU
to p4.
5A The SS does not allocate any UL grant. - - - -
6 The SS transmits 8 AMD PDUs such that 1 <-- AMD PDU (SN=4) - -
AMD PDU is sent every second radio frame, AMD PDU (SN=5)
each containing an RLC SDU of 2 560 bits. ...
(Note 2) AMD PDU (SN=11)
described in step 6A, the step specified in
6A The SS waits for 100 ms after the first DL AMD - - - -
PDU has been transmitted in step 6, then
type 2) in every second radio frame of size 2
7 The SS transmits a Status Report with <-- STATUS PDU - -
ACK_SN=12, NACK_SN=4, NACK_SN=5,
NACK_SN=6, NACK_SN=8 and NACK_SN=9.
8 Check: Does the UE transmit AMD PDUs with --> AMD PDU (SN=4, P=0) 3 P
the following SN and P values? AMD PDU (SN=5, P=0)
AMD PDU, SN=4, P=0 AMD PDU (SN=6, P=0)
AMD PDU, SN=8, P=0
AMD PDU, SN=9, P=1
A transmission
8A The SS transmits a Status Report with <-- STATUS PDU - -
ACK_SN=12 and no NACK_SN.
9 SS performs an RRC Connection - - - -
Reconfiguration procedure changing pollPDU
to p256.
9A The SS does not allocate any UL grant. - - - -
10 After 500 ms the SS transmits 160 AMD PDUs <-- AMD PDU (SN=12) - -
such that 1 AMD PDU is sent every second AMD PDU (SN=13)
ETSI
radio frame, each containing an RLC SDU of ...

size 2 560 bits. (Note 2) AMD PDU (SN=171)
described in step 10A, the steps specified in
10 The SS waits for 100 ms after the first DL AMD - - - -
A PDU has been transmitted in step 10, then
type 2) in every second radio frame of size
10 The SS starts the UL default grant - - - -
B transmission
Note 1: UL grant of 2600 bits (ITBS=14, NPRB=9, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to loop
back one SDU of size 2560 bits and one short BSR (8 bits) into each MAC PDU sent in the uplink (2600
bits - 16 bit AMD PDU header - 8 bit MAC BSR subheader - 8 bit MAC PDU subheader). The UE will
include an SDU of size 2560 bits and one short BSR in the looped back MAC PDU.
Note 2: 20ms gap between transmissions both in DL and UL respectively allows TTCN to tolerate one HARQ

U-S Message
1 Check: Does the UE transmit 4 AMD PDUs, --> AMD PDUs 1 P
with only the last one having the poll bit set?
Record time TA when the PDU with the poll bit
set is received at the SS.

U-S Message
1 Check: Does the UE transmit 8 AMD PDUs, --> AMD PDUs 3 P
th th
with the poll bit set only in the 4 and the 8
PDUs?

U-S Message
1 Check: Does the UE transmit 79 AMD PDUs, --> AMD PDUs 1,4 P
th
with the poll bit set only in the last (79 ) one?
(Note 1)
2 The SS transmits an RLC Status Report. <-- STATUS PDU - -
th
with the poll bit set only in the last (158 ) one?
(Note 1)
th
with the poll bit set only in the last (160 )
one?
Note 1: (2560 bits x 79 PDUs) / 8 = 25 280 > 25 KB, with 1 kB = 1000 bytes (TS 36.331, cl. 3.2)
None.
ETSI
7.2.3.10 AM RLC / Receiver status triggers

(1)
ensure that {
when { Reception failure of an RLC data PDU is detected }
then { UE initiates Status Reporting when t-Reordering expires }
}
(2)
ensure that {
when { Status Reporting is triggered and t-StatusProhibit is running}
then { UE wait until t-StatusProhibit has expired to send Status Report }
}
(3)
ensure that {
when { Polling from peer AM RLC entity is detected and the sequence number of the PDU that carries
the Poll is less than VR(MS) }
then { UE initiates Status Reporting }
}
(4)
ensure that {
when { Polling from peer AM RLC entity is detected and the sequence number of the PDU that carries
the Poll is greater than or equal to VR(MS) }
then { UE waits until VR(MS) becomes greater than the sequence number of the PDU with the Poll
before initiating Status Reporting }
}
(5)
ensure that {
when { the UE needs to send a Status Report and the UL grant is not large enough to accommodate
the whole report }
then { UE includes as many NACK SNs in the Status Report as allowed by the UL grant }
}
[TS 36.322, clause 5.2.3]
An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative
acknowledgements of RLC PDUs (or portions of them).
RRC configures whether or not the status prohibit function is to be used an AM RLC entity.
Triggers to initiate STATUS reporting include:
- Polling from its peer AM RLC entity:
- When a RLC data PDU with SN = x and the P field set to "1" is received from lower layer, the receiving side
of an AM RLC entity shall:
- if the PDU is to be discarded as specified in subclause 5.1.3.2.2; or
- if x < VR(MS) or x >= VR(MR):
- trigger a STATUS report;
ETSI
- else:
- delay triggering the STATUS report until x < VR(MS) or x >= VR(MR).
NOTE: This ensures that the RLC Status report is transmitted after HARQ reordering.
- Detection of reception failure of an RLC data PDU:
- The receiving side of an AM RLC entity shall trigger a STATUS report when t-Reordering expires.
NOTE: The expiry of T_reordering triggers both VR(MS) to be updated and a STATUS report to be triggered,
but the STATUS report shall be triggered after VR(MS) is updated.
When STATUS reporting has been triggered, the receiving side of an AM RLC entity shall:
- if t-StatusProhibit is not running:
- at the first transmission opportunity indicated by lower layer, construct a STATUS PDU and deliver it to
lower layer;
- else:
- at the first transmission opportunity indicated by lower layer after t-StatusProhibit expires, construct a single
STATUS PDU even if status reporting was triggered several times while t-StatusProhibit was running and
deliver it to lower layer;
When a STATUS PDU has been delivered to lower layer, the receiving side of an AM RLC entity shall:
- start t-StatusProhibit.
When constructing a STATUS PDU, the AM RLC entity shall:
- for the AMD PDUs with SN such that VR(R) <= SN < VR(MS) that has not been completely received yet, in
increasing SN order of PDUs and increasing byte segment order within PDUs, starting with SN = VR(R) up to
the point where the resulting STATUS PDU still fits to the total size of RLC PDU(s) indicated by lower layer:
- for an AMD PDU for which no byte segments have been received yet for an AMD PDU:
- include in the STATUS PDU a NACK_SN which is set to the SN of the AMD PDU;
- for a continuous sequence of byte segments of a partly received AMD PDU that have not been received yet :
- include in the STATUS PDU a set of NACK_SN, SOstart and SOend
- set the ACK_SN to the SN of the next not received RLC Data PDU which is not indicated as missing in the
resulting STATUS PDU.
System Simulator:
- Cell 1.
UE:
None.
Preamble
1.
ETSI
Parameter Value
t-Reordering ms150
t-StatusProhibit ms300
ETSI

U-S Message
- The SS ignores scheduling requests and does - - - -
1 The SS transmits 4 AMD PDUs with SN=0, 1, <-- AMD PDU (SN=0, P=0) - -
2, and 4. The SS sets the P field of all the AMD PDU (SN=1, P=0)
AMD PDUs to 0. AMD PDU (SN=2, P=0)
Record time TA when the AMD PDU with SN=4 AMD PDU (SN=4, P=0)
is sent.
1A The SS waits for 60 ms after the transmission <-- (UL grants, 840 bits) - -
of the first AMD PDU to ensure UE RLC has all
the required SDUs available and then assigns
3 UL grants (UL grant allocation type 2) with a
time spacing of 5 ms of size 840 bits (UL Grant
Allocation type 2). (Note 1, Note 5)
1B The UE transmits RLC SDU#1. --> (RLC SDU#1) - -
1C The UE transmits RLC SDU#2. --> (RLC SDU#2) - -
1D The UE transmits RLC SDU#3. --> (RLC SDU#3) - -
1E The SS transmits a STATUS PDU <-- STATUS PDU - -
1F The SS starts the UL default grant - - - -
transmission
2 Check 1: Does the UE transmit a Status --> STATUS PDU 1 P
Report with NACK_SN=3 and ACK_SN=5?
Record time TB
Check 2: (TB – TA) = t-Reordering
3 100 ms after the Status Report is received at <-- AMD PDU (SN=5, P=0) - -
Step 2, the SS transmits 4 AMD PDUs with AMD PDU (SN=6, P=0)
SN=5, 6, 8 and 9. The SS sets the P field of all AMD PDU (SN=8, P=0)
the AMD PDUs to 0. AMD PDU (SN=9, P=0)
3A Void - - - -
3B Check 1: Does the UE transmit a Status --> STATUS PDU 2 P
Report with NACK_SN=3, ACK_SN=7?
Record time TC
Check 2: (TC – TB) = t-StatusProhibit
3C Void - - - -
4 The UE transmit a Status Report with --> STATUS PDU
NACK_SN=3, NACK_SN=7 and ACK_SN=10
4A The SS ignores scheduling requests unless - - - -
otherwise specified and does not allocate any
uplink grant and is configured for Uplink Grant
Allocation Type 3.
5 Void - - - -
6 After 300 ms the SS transmits 2 AMD PDUs <-- AMD PDU (SN=3, P=0) - -
with SN=3, SN=7. The SS sets the P field of all AMD PDU (SN=7, P=1)
the AMD PDUs to 0 except for that of the AMD
PDU with SN=7.
6A The SS waits for 60 ms to ensure UE RLC has <-- (UL grant, 40 bits) - -
all the required SDUs available and then
assigns 1 UL grant (UL grant allocation type 3)
of size 40 bits. (Note 2)
7 Check: Does the UE transmit a Status Report --> STATUS PDU 3 P
with no NACK_SN and ACK_SN = 10?
7A In the subframe following the one scheduled in <-- (UL grant, 840 bits) - -
step 6A the SS assigns 7 UL grants (UL grant
allocation type 2) with a time spacing of 5 ms
7E The UE transmits RLC SDU#7. --> (RLC SDU#7) - -
7F The UE transmits RLC SDU#8. --> (RLC SDU#8) - -
7G The UE transmits RLC SDU#9. --> (RLC SDU#9) - -
7H The UE transmits RLC SDU#10. --> (RLC SDU#10) - -
ETSI
7I The SS transmits a STATUS PDU <-- STATUS PDU - -

8 Void - - - -
9 After 300 ms the SS transmits an AMD PDU <-- AMD PDU (SN=10, P=0) - -
with SN=10 and P=0, and an AMD PDU with AMD PDU (SN=12, P=1)
SN=12 and P=1.
9A Check: Does the UE transmits a scheduling --> (SR) 4 F
request within t-Reordering / 2 ms?
10 Within t-Reordering / 2 ms after Step 9, the SS <-- AMD PDU (SN=11, P=0) - -
transmits an AMD PDU with SN=11 and P=0.
Note: AMD PDUs with SN 10,11 and 12 carry
RLC SDU #11.
10 The SS waits for 60 ms to ensure UE RLC has <-- (UL grants, 40 bits) - -
A all the required SDUs available and then
assigns 1 UL grant (UL grant allocation type 3)
with no NACK_SN and ACK_SN=13?
11 The SS assigns 1 UL grant (UL grant <-- (UL grant, 840 bits) - -
A allocation type 3) of size 840 bits. (Note 1)
11 The UE transmit RLC SDU#11. --> (RLC SDU#11) - -
B
11 The SS transmits a STATUS PDU <-- STATUS PDU - -
C
12 Void - - - -
13 Void - - - -
14 After 300 ms the SS transmits an AMD PDU <-- AMD PDU (SN=13, P=0) - -
with SN=13 and P=0, and an AMD PDU with AMD PDU (SN=19, P=1)
SN=19 and P=1.
15 The SS waits for t-Reordering ms to ensure - - - -
expiry.
16 Void - - - -
17 60 ms after step 15 the SS assigns an UL <-- (UL Grant) - -
bits. (Note 3)
18 Void - - - -
- Steps 18a1 and 18b1 depends on the UE - - - -
behaviour; the "lower case letter" identifies a
step sequence that takes place if a specific
behaviour happens
18a Check: Does the UE transmit a Status Report --> STATUS PDU 5 P
1 with ACK_SN=16 and 2 NACK_SNs: 14 and
15?
18b Check: Does the UE transmit a Status Report --> STATUS PDU 5 P
1 with ACK_SN=18 and 4 NACK_SNs: 14,15, 16
and 17?
19 Void - - - -
20 Void - - - -
21 After 300 ms The SS transmits an AMD PDU <-- AMD PDU (SN=14, P=1) - -
with SN=14 and P=1.
22 60 ms after step 21 the SS assigns an UL <-- (UL Grant) - -
bits. (Note 4)
with ACK_SN=20 and 4 NACK_SNs: 15, 16,
17 and 18?
24 60 ms after step 22 t he SS transmits 4 AMD <-- AMD PDU (SN=15, P=0) - -
PDU with SN=15, 16, 17, 18. AMD PDU (SN=16, P=0)
Note: AMD PDUs with SN 13 to 19 carry RLC AMD PDU (SN=17, P=0)
SDU #12. AMD PDU (SN=18, P=0)
24 60 ms after step 24 the SS assigns 1 UL grant <-- (UL grant, 840 bits) - -
A (UL grant allocation type 3) of size 840 bits.
(Note 1)
25 The UE loopbacks the complete RLC SDU. --> (RLC SDU#12) - -
Note 1: UL grant of 840 bits (ITBS=14, NPRB=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit
one PDU at a time.
Note 2: UL grant of 40 bits (ITBS=3, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit a
ETSI
Status Report with ACK_SN and (8-bit short BSR + 2x 8-bit MAC PDU subheader + 4-bit D/C/CPT + 10-bit
ACK_SN + 1-bit E1 + 1bit padding).
Note 3: UL grant of 72 bits (ITBS=2, NPRB=2, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit (a
Status Report with ACK_SN and 2 NACK_SNs (3x 8-bit MAC PDU subheader +8-bit Short BSR + 4-bit
D/C/CPT + 10-bit ACK_SN + 1-bit E1 + 2 x (12-bit NACK_SN/E1/E2) + 1-bit Padding) ) or (a Status Report
with ACK_SN and 4 NACK_SNs (8-bit MAC PDU subheader +4-bit D/C/CPT + 10-bit ACK_SN + 1-bit E1 +
4 x (12-bit NACK_SN/E1/E2) +1-bit padding)).
Note 4: UL grant of 72 bits (ITBS=2, NPRB=2, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit a
Status Report with ACK_SN and 4 NACK_SNs (8-bit MAC PDU subheader + 4-bit D/C/CPT + 10-bit
ACK_SN + 1-bit E1 + 4 x (12-bit NACK_SN/E1/E2) +1-bit padding).
Note 5: The first AMD PDU is transmitted in subframe #4. This subframe is as well suitable for the transmission of UL
grants in TDD.
None.
7.2.3.11 Void
7.2.3.12 Void
7.2.3.13 AM RLC / Reconfiguration of RLC parameters by upper layers
(1)
ensure that {
when { t-PollRetransmit value is changed during reconfiguration of RLC parameters by upper layers
}
then { UE starts using new t-PollRetransmit value }
}
(2)
ensure that {
when { t-Reordering value is changed during reconfiguration of RLC parameters by upper layers }
then { UE starts using new t-Reordering value }
}
(3)
ensure that {
when { t-StatusProhibit value is changed during reconfiguration of RLC parameters by upper layers}
then { UE starts using new t-StatusProhibit value }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clause 5.2.2,
5.2.2.1, 5.2.2.2, 5.2.2.3 and 5.2.3.
[TS 36.322, clause 5.2.2]
An AM RLC entity can poll its peer AM RLC entity in order to trigger STATUS reporting at the peer AM RLC entity.
[TS 36.322, clause 5.2.2.1]
Upon assembly of a new AMD PDU, the transmitting side of an AM RLC entity shall:
- increment PDU_WITHOUT_POLL by one;
- increment BYTE_WITHOUT_POLL by every new byte of Data field element that it maps to the Data field of
the RLC data PDU;
- if PDU_WITHOUT_POLL >= pollPDU; or
ETSI
- if BYTE_WITHOUT_POLL >= pollByte;
Upon assembly of a AMD PDU or AMD PDU segment, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC data
PDU awaiting for acknowledgements) after the transmission of the RLC data PDU; or
- if no new RLC data PDU can be transmitted after the transmission of the RLC data PDU (e.g. due to window
stalling);
To include a poll in a RLC data PDU, the transmitting side of an AM RLC entity shall:
- set the P field of the RLC data PDU to "1";
- set PDU_WITHOUT_POLL to 0;
- set BYTE_WITHOUT_POLL to 0;
After delivering a RLC data PDU including a poll to lower layer and after incrementing of VT(S) if necessary, the
transmitting side of an AM RLC entity shall:
- set POLL_SN to VT(S) – 1;
- if t-PollRetransmit is not running:
- start t-PollRetransmit;
- else:
- restart t-PollRetransmit;
[TS 36.322, clause 5.2.2.2]
Upon reception of a STATUS report from the receiving RLC AM entity the transmitting side of an AM RLC entity
shall:
- if the STATUS report comprises a positive or negative acknowledgement for the RLC data PDU with sequence
number equal to POLL_SN:
- if the t-PollRetransmit is running:
- stop and reset t-PollRetransmit.
[TS 36.322, clause 5.2.2.3]
Upon expiry of t-PollRetransmit, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer are empty (excluding transmitted RLC data PDU
awaiting for acknowledgements); or
- if no new RLC data PDU can be transmitted (e.g. due to window stalling):
- consider the AMD PDU with SN = VT(S) – 1 for retransmission; or
- consider any AMD PDU which has not been positively acknowledged for retransmission;
- include a poll in a RLC data PDU as described in section 5.2.2.1.
[TS 36.322, clause 5.2.3]
An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative
acknowledgements of RLC PDUs (or portions of them).
RRC configures whether or not the status prohibit function is to be used for an AM RLC entity.
ETSI
Triggers to initiate STATUS reporting include:
- Polling from its peer AM RLC entity:
- When a RLC data PDU with SN = x and the P field set to “1” is received from lower layer, the receiving side
of an AM RLC entity shall:
- if the PDU is to be discarded as specified in subclause 5.1.3.2.2; or
- if x < VR(MS) or x >= VR(MR):
- trigger a STATUS report;
- else:
- delay triggering the STATUS report until x < VR(MS) or x >= VR(MR).
NOTE: This ensures that the RLC Status report is transmitted after HARQ reordering.
- Detection of reception failure of an RLC data PDU:
- The receiving side of an AM RLC entity shall trigger a STATUS report when t-Reordering expires.
NOTE: The expiry of T_reordering triggers both VR(MS) to be updated and a STATUS report to be triggered,
but the STATUS report shall be triggered after VR(MS) is updated.
When STATUS reporting has been triggered, the receiving side of an AM RLC entity shall:
- if t-StatusProhibit is not running:
- at the first transmission opportunity indicated by lower layer, construct a STATUS PDU and deliver it to
lower layer;
- else:
- at the first transmission opportunity indicated by lower layer after t-StatusProhibit expires, construct a single
STATUS PDU even if status reporting was triggered several times while T_status_prohibit was running and
deliver it to lower layer;
When a STATUS PDU has been delivered to lower layer, the receiving side of an AM RLC entity shall:
- start t-StatusProhibit.
When constructing a STATUS PDU, the AM RLC entity shall:
- for the AMD PDUs with SN such that VR(R) <= SN < VR(MS) that has not been completely received yet, in
increasing SN order of PDUs and increasing byte segment order within PDUs, starting with SN = VR(R) up to
the point where the resulting STATUS PDU still fits to the total size of RLC PDU(s) indicated by lower layer:
- for an AMD PDU for which no byte segments have been received yet :
- include in the STATUS PDU a NACK_SN which is set to the SN of the AMD PDU;
- for a continuous sequence of byte segments of a partly received AMD PDU that have not been received yet
- include in the STATUS PDU a set of NACK_SN, SOstart and SOend
- set the ACK_SN to the SN of the next not received RLC Data PDU which is not indicated as missing in the
resulting STATUS PDU.
System Simulator:
- Cell 1.
ETSI
UE:
None.
Preamble:
1.
Parameter Value
t-Reordering ms150
pollPDU pInfinity
pollByte kBinfinity
ETSI

U-S Message/PDU/SDU
1 Void - - - -
The SS ignores scheduling requests and does - - - -
2 The SS transmits 4 AMD PDUs with P=0 and <-- AMD PDU#1 (SN=0, P=0) - -
SN=0, 1, 2 and 4. AMD PDU#2 (SN=1, P=0)
The SS record time TA when AMD PDU#5 AMD PDU#3 (SN=2, P=0)
(with SN=4) is sent. AMD PDU#5 (SN=4, P=0)
2A The SS waits for 60 ms after the transmission <-- (UL grants, 840 bits) - -
of the first AMD PDU to ensure UE RLC has all
3 UL grants of size 840 bits (UL Grant
Allocation type 2) with a time spacing of 5 ms.
(Note 2, Note 5)
2E The SS transmits a STATUS PDU <-- STATUS PDU - -
transmission
3 Check 1: Does the UE transmit a STATUS --> STATUS PDU - -
PDU with NACK_SN=3 and ACK_SN=5?
Record time TB.
Check 2: Is (TB – TA ) = t-Reordering?
4 100 ms after the Status Report received at <-- AMD PDU#6 (SN=5, P=0) - -
Step 3, he SS sends 4 AMD PDUs with P=0 AMD PDU#7 (SN=6, P=0)
and SN=5, 6, 8 and 9. AMD PDU#9 (SN=8, P=0)
AMD PDU#10 (SN=9, P=0)
4A Check 1: Does the UE transmit a Status --> STATUS PDU - -
Report with NACK_SN=3, ACK_SN=7?
Record time TC
Check 2: (TC – TB) = t-StatusProhibit?
5 The UE transmits a STATUS PDU with --> STATUS PDU - -
NACK_SN=3, NACK_SN=7 and ACK_SN=10.
7 After 300 ms the SS transmits 3 AMD PDUs <-- AMD PDU#4 (SN=3, P=0) - -
with SN=3, 7 and 9. The SS sets the P field of AMD PDU#8 (SN=7, P=0)
all the AMD PDUs to 0 except for that of the AMD PDU#10 (SN=9, P=1)
AMD PDU with SN=9.
7A The SS waits for 60 ms to ensure UE RLC has <-- (UL grant, 40 bits) - -
assigns 1 UL grant of size 40 bits (UL Grant
Allocation type 3). (Note 3)
8 The UE transmits a Status Report with no --> STATUS PDU - -
NACK_SN and ACK_SN = 10.
8A In the subframe following the one scheduled in <-- (UL grants, 840 bits) - -
step 7A the SS assigns 7 UL grants of size
840 bits (UL Grant Allocation type 2) with a
time spacing of 5 ms. (Note 2)
ETSI

8E The UE transmits RLC SDU#7. --> (RLC SDU#7) - -
8G The UE transmits RLC SDU#9. --> (RLC SDU#9) - -
8H The UE transmits RLC SDU#10. --> (RLC SDU#10) - -
9 The SS transmits an AMD PDU to the UE. <-- AMD PDU#11 (SN=10, P=0) - -
transmission
10 The UE transmits an AMD PDU with the same --> AMD PDU#11 (SN=10, P=1) - -
PDU. Record time TD.
11 Check 1: Does the UE set the poll bit as both --> AMD PDU#11 (SN=10, P=1) 1 P
the transmission and retransmission buffers
become empty? Record time TE.
Check 2: Is (TE – TD ) = t-PollRetransmit?
A
12 The SS reconfigures RLC in the UE and sets: - - - -
- t-Reordering to ms200,
- t-StatusProhibit to ms400,
- t-PollRetransmit to ms500.
(Note 1)
13 The SS transmits 4 AMD PDUs with P=0 and <-- AMD PDU#12 (SN=11, P=0) - -
SN=11, 12, 13 and 15. AMD PDU#13 (SN=12, P=0)
The SS record time TF when AMD PDU#16 AMD PDU#14 (SN=13, P=0)
(with SN=15) is sent. AMD PDU#16 (SN=15, P=0)
13 The SS waits for 60 ms after the transmission <-- (UL grants, 840 bits) - -
A of the first AMD PDU to ensure UE RLC has all
3 UL grants of size 840 bits (UL Grant
Allocation type 2) with a time spacing of 5 ms.
(Note 2, Note 5)
B
C
D
E
transmission
14 Check 1: Does the UE transmit a STATUS --> STATUS PDU 2 P
PDU with NACK_SN=14 and ACK_SN=16?
Record time TG.
Check 2: Is (TG – TF ) = updated value of t-
Reordering?
15 100 ms after the Status Report received at <-- AMD PDU#17 (SN=16, P=0) - -
Step 14, t he SS sends 4 AMD PDUs with P=0 AMD PDU#18 (SN=17, P=0)
and SN=16, 17, 19 and 20. AMD PDU#20 (SN=19, P=0)
AMD PDU#21 (SN=20, P=0)
15 Check 1: Does the UE transmit a STATUS --> STATUS PDU 3 P
A PDU with NACK_SN=14 and ACK_SN=18?
Record time TH.
Check 2: Is (TH – TG ) = updated value of t-
StatusProhibit?
NACK_SN=14, NACK_SN=18 and
ACK_SN=21.
18 After 450 ms the SS transmits 3 AMD PDUs <-- AMD PDU#15 (SN=14, P=0) - -
ETSI
with SN=14, 18 and 20. The SS sets the P AMD PDU#19 (SN=18, P=0)
field of all the AMD PDUs to 0 except for that AMD PDU#21 (SN=20, P=1)
of the AMD PDU with SN=20.
18 The SS waits for 60 ms to ensure UE RLC has <-- (UL grant, 40 bits) - -
assigns 1 UL grant of size 40 bits (UL Grant
Allocation type 3). (Note 3)
19 The UE transmits a Status Report with no --> STATUS PDU - -
NACK_SN and ACK_SN = 21.
19 In the subframe following the one scheduled in <-- (UL grants, 840 bits) - -
A step 18A the SS assigns 7 UL grants of size
840 bits (UL Grant Allocation type 2) with a
time spacing of 5 ms. (Note 2)
B
C
D
E
G
H
20 The SS transmits an AMD PDU to the UE. <-- AMD PDU#22 (SN=21, P=0) - -
20 The SS starts the UL default grant - - - -
A transmission
21 The UE transmits an AMD PDU with the same --> AMD PDU#22 (SN=21, P=1) - -
PDU. Record time TI.
22 Check 1: Does the UE set the poll bit as both --> AMD PDU#22 (SN=21, P=1) 1 P
the transmission and retransmission buffers
become empty? Record time TJ.
Check 2: Is (TJ – TI ) = updated value of t-
PollRetransmit?
Note 1: The RRC Connection Reconfiguration procedure is performed.
Note 2: UL grant of 840 bits (ITBS=14, NPRB=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to
transmit one PDU at a time.
a Status Report with ACK_SN and (16-bit short BSR + 8-bit MAC PDU subheader + 4-bit D/C/CPT + 10-bit
ACK_SN + 1-bit E1 + 1bit padding).
Note 4: Every DL AMD PDU contains 1 RLC SDU size of 100 bytes.
Note 5: The first AMD PDU is transmitted in subframe #4. This subframe is as well suitable for the transmission of UL
grants in TDD.
None.
7.2.3.14 AM RLC / In sequence delivery of upper layers PDUs

(1)
ensure that {
when { UE receives duplicate AMD PDUs }
then { UE discards the duplicate AMD PDUs }
}
(2)
ETSI
ensure that {
when { UE receives an AMD PDU with a SN gap }
then { UE sends STATUS PDU to request retransmissions of PDUs in the SN gap}
}
(3)
ensure that {
when { UE receives PDUs within a SN gap }
then { RLC reassembles and reorders the AMD PDUs and deliver them to the upper layer in sequence }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clause
4.2.1.3.3.
[TS 36.322, clause 4.2.1.3.3]
- detect whether or not the RLC data PDUs have been received in duplication, and discard duplicated RLC data
PDUs;
- reorder the RLC data PDUs if they are received out of sequence;
- detect the loss of RLC data PDUs at lower layers and request retransmissions to its peer AM RLC entity;
sequence.
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS transmits an AMD PDU to the UE. This <-- AMD PDU#1 (SN=0)
PDU carries SDU#1.
2 The SS transmits an AMD PDU to the UE. This <-- AMD PDU#1 (SN=0) - -
PDU carries SDU#1.
(Note)
st
PDU contains SDU#2, and the 1 part of
SDU#3.
st
SDU#3.
nd
PDU contains the 2 part of SDU#3.
PDU contains the last part of SDU#6.
nd
PDU contains the 2 part of SDU#5, and the
st
1 part of SDU#6.
A
st
PDU carries SDU#4 and the 1 part of SDU#5.
A grant sufficient for the UE to loopback SDU#4,
SDU#5 and SDU#6.
15 Void - - - -
16 The SS transmits an AMD RLC PDU to the <-- AMD PDU#9 (SN=8, P=1) - -
UE. This PDU contains the last part of SDU#9.
NACK_SN/E1/E2 fields set correctly to inform
SS of missing PDUs #7, #8, (ACK_SN =9,
NACK_SN = 6, NACK_SN = 7)?
st
SDU#9.
A
PDU carries SDU#7.
19 The SS waits for 60 ms then assigns an UL <-- (UL grants) - -
A grant sufficient for the UE to loopback SDU#7,
SDU#8 and SDU#9.
22 Void - - - -
Note: UE may transmit RLC SDU #1 between Step 1 and Step 2.
ETSI
None.
7.2.3.15 AM RLC / Re-ordering of RLC PDU segments

(1)
ensure that {
when { UE receives RLC AM PDU segments }
then { UE reorders RLC AMD PDU segments received out of sequence }
}
(2)
ensure that {
when { t-Reordering expires }
then { Set VR(MS) to SN of the first AMD PDU with SN >= VR(X) for which not all byte segments
have been received }
}
4.2.1.3.3, 5.1.3.2.1, 5.1.3.2.2, 5.1.2.3.3 and 5.1.2.3.4.
[TS 36.322, clause 4.2.1.3.3]
...
sequence.
...
[TS 36.322, clause 5.1.3.2.1]
The receiving side of an AM RLC entity shall maintain a receiving window according to state variables VR(R) and
VR(MR) as follows:
- a SN falls within the receiving window if VR(R) <= SN < VR(MR);
- a SN falls outside of the receiving window otherwise.
When receiving a RLC data PDU from lower layer, the receiving side of an AM RLC entity shall:
- either discard the received RLC data PDU or place it in the reception buffer (see sub clause 5.1.3.2.2);
- if the received RLC data PDU was placed in the reception buffer:
needed (see sub clause 5.1.3.2.3).
- update state variables and start t-Reordering as needed (see sub clause 5.1.3.2.4).
[TS 36.322, clause 5.1.3.2.2]
When a RLC data PDU is received from lower layer, where the RLC data PDU contains byte segment numbers y to z of
an AMD PDU with SN = x, the receiving side of an AM RLC entity shall:
ETSI
- if x falls outside of the receiving window; or
- if byte segment numbers y to z of the AMD PDU with SN = x have been received before:
- discard the received RLC data PDU;
- else:
- place the received RLC data PDU in the reception buffer;
- if some byte segments of the AMD PDU contained in the RLC data PDU have been received before:
- discard the duplicate byte segments.
[TS 36.322, clause 5.1.3.2.3]
When a RLC data PDU with SN = x is placed in the reception buffer, the receiving side of an AM RLC entity shall:
- if all byte segments of the AMD PDU with SN = VR(MS) are received:
- update VR(MS) to the SN of the first AMD PDU with SN > current VR(MS) for which not all byte segments
have been received;
- if x = VR(R):
- if all byte segments of the AMD PDU with SN = VR(R) are received:
- update VR(R) to the SN of the first AMD PDU with SN > current VR(R) for which not all byte segments
have been received;
- update VR(MR) to the updated VR(R) + AM_Window_Size;
- reassemble RLC SDUs from any byte segments of AMD PDUs with SN that falls outside of the receiving
window and in-sequence byte segments of the AMD PDU with SN = VR(R), remove RLC headers when
doing so and deliver the reassembled RLC SDUs to upper layer in sequence if not delivered before;
- if x >= VR(H)
- update VR(H) to x+ 1;
- if VR(X) = VR(R); or
- if VR(X) falls outside of the receiving window and VR(X) is not equal to VR(MR):
- if t-Reordering is not running (includes the case t-Reordering is stopped due to actions above):
- if VR (H) > VR(R):
- set VR(X) to VR(H).
[TS 36.322, clause 5.1.3.2.4]
- update VR(MS) to the SN of the first AMD PDU with SN >= VR(X) for which not all byte segments have been
received;
- if VR(H) > VR(MS):
- set VR(X) to VR(H).
ETSI
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loop back size of 98 bytes.
ETSI

U-S Message/PDU/SDU
1 The SS transmits one AMD PDU containing <-- AMD PDU#8 (SN=7) - -
SDU#8 (100 bytes) in its data field to the UE.
SN=7 indicates the loss of 7 PDUs.
2 The SS transmits one AMD PDU segment <-- AMD PDU#1 (SN=0) - -
containing 50 bytes of SDU#1 in its data field segment 1
to the UE. This AMD PDU segment carries
part 1 of AMD PDU#1, which contained
SDU#1 (100 bytes) in its data field. SO=0 and
LSF=0.
LSF=1.
LSF=0.
LSF=1.
part 1of AMD PDU#4, which contained SDU#4
(100 bytes) in its data field. SO=0 and LSF=0.
LSF=1.
8 Void
LSF=0.
10 Void
part 2 of PDU#3, which contained SDU#3 (100
bytes) in its data field. SO=50 and LSF=1.
A containing 50 bytes of SDU#7 in its data field segment 1
part 1 of PDU #7, which contained SDU#7
(100 bytes) in its data field. SO=0 and LSF=0.
B containing 50 bytes of SDU#6 in its data field segment 2
segment 2 of AMD PDU#6, which contained
LSF=1.
ETSI
11 The SS waits for 60 ms then SS transmits 4 <-- (UL grants) - -

C uplink grants (UL grant allocation type 2) with a
time spacing of 5 ms, each allowing the UE to
transmit 1 RLC SDU.
11 Check: Does the UE transmit an RLC SDU --> (RLC SDU#1) 1 P
D containing SDU#1 in its data field?
E containing SDU#2 in its data field?
containing SDU#3 in its data field?
14 The SS transmits an RLC STATUS PDU to the <-- STATUS PDU - -
UE. This PDU acks PDUs up to those
including SDU#4. ACK_SN=4.
15 Void
16 Void
17 Wait for t-Reordering to run out at the UE side. - - - -
with NACK_SN=4, NACK_SN=5 with
SOStart=0 and SOEnd=49, and NACK_SN=6
with SOStart=50 and SOEnd=32767 (special
SOEnd value), and ACK_SN=8?
LSF=1.
LSF=0.
LSF=0.
22 Wait for t-Reordering to run out at the UE side. - - - -
with NACK_SN=4 with SOStart=50 and
SOEnd=32767 (special SOEnd value), and
ACK_SN=8?
LSF=1.
24 The SS waits for 60 ms then SS transmits 4 <-- (UL grants) - -
A uplink grants (UL grant allocation type 2) with a
time spacing of 5 ms, each allowing the UE to
transmit 1 RLC SDU.
29 The SS transmits an RLC STATUS PDU to the <-- STATUS PDU - -
UE. This PDU acks PDUs up to those
including SDU#7. ACK_SN=8.
ETSI
None.
7.2.3.16 AM RLC / Re-transmission of RLC PDU without re-segmentation

(1)
ensure that {
when { UE receives a STATUS PDU including a NACK_SN for missing AMD PDUs and missing AMD PDUs can
fit into within the total size of RLC PDU(s) indicated by lower layer at the particular transmission
opportunity}
then { UE successfully retransmits missing AMD PDUs without re-segmentation}
}
(2)
ensure that {
when { NACK received for missing AMD PDUs and RETX_COUNT < maxRetxThreshold }
then { UE retransmits AMD PDUs }
}
(3)
ensure that {
when { an AMD PDU or a portion of an AMD PDU is considered for retransmission and if RETX_COUNT =
maxRetxThreshold }
then { UE indicates to upper layers that max retransmission has been reached }
}
[TS 36.322 clause 5.2.1]
The transmitting side of an AM RLC entity can receive a negative acknowledgement (notification of reception failure
by its peer AM RLC entity) for an AMD PDU or a portion of an AMD PDU by the following:
When receiving a negative acknowledgement for an AMD PDU or a portion of an AMD PDU by a STATUS PDU from
its peer AM RLC entity, the transmitting side of the AM RLC entity shall:
- if the SN of the corresponding AMD PDU falls within the range VT(A) <= SN < VT(S):
- consider the AMD PDU or the portion of the AMD PDU for which a negative acknowledgement was
received for retransmission.
When an AMD PDU or a portion of an AMD PDU is considered for retransmission, the transmitting side of the AM
RLC entity shall:
- if the AMD PDU is considered for retransmission for the first time:
- set the RETX_COUNT associated with the AMD PDU to zero;
- else, if it (the AMD PDU or the portion of the AMD PDU that is considered for retransmission) or a portion of it
is not pending for retransmission already:
- increment the RETX_COUNT;
- if RETX_COUNT = maxRetxThreshold:
- indicate to upper layers that max retransmission has been reached.
ETSI
When retransmitting an AMD PDU, the transmitting side of an AM RLC entity shall:
- if the AMD PDU can entirely fit within the total size of RLC PDU(s) indicated by lower layer at the particular
transmission opportunity:
- deliver the AMD PDU as it is except for the P field (the P field should be set according to sub clause 5.2.2) to
lower layer;
- otherwise:
- segment the AMD PDU form a new AMD PDU segment which will fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity and deliver the new AMD PDU segment
to lower layer.
When retransmitting a portion of an AMD PDU, the transmitting side of an AM RLC entity shall:
- segment the portion of the AMD PDU as necessary, form a new AMD PDU segment which will fit within the
total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity and deliver the new
AMD PDU segment to lower layer.
When forming a new AMD PDU segment, the transmitting side of an AM RLC entity shall:
- only map the Data field of the original AMD PDU to the Data field of the new AMD PDU segment;
- set the header of the new AMD PDU segment in accordance with the description in sub clause 6.;
- set the P field according to sub clause 5.2.2.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loopback size of 98 bytes with the
exceptions listed in table 7.2.3.16.3.1-1.
Table 7.2.3.16.3.1-1: PDCP-Config-DRB-AM

PDCP-Config-DRB-AM ::= SEQUENCE {
rlc-AM SEQUENCE {
statusReportRequired FALSE
}
}
ETSI

U-S Message
1 The SS transmits one AMD PDU containing <-- AMD PDU#1 - -
SDU#1 (100 bytes) in its data field.
2 The UE transmits one AMD PDU containing --> AMD PDU#1 (SN=0) - -
SDU#1 in its data field.
4 The UE transmits one AMD PDU containing --> AMD PDU#2 (SN=1) - -
5 The SS transmits an RLC STATUS PDU. <-- STATUS PDU - -
ACK_SN=2, NACK_SN=0.
6 Check: Does the UE transmit the AMD PDU --> AMD PDU#1 (SN=0) 1 P
not yet acknowledged?
ACK_SN=2.
9 The UE transmits an AMD PDU containing --> AMD PDU#3 (SN=2) - -
- EXCEPTION: Step 10 to 11 shall be repeated - - - -
maxRetxThreshold times
ACK_SN =3 and NACK_SN =2.
11 Check: Does the UE retransmit the AMD PDU --> AMD PDU#3 (SN=2) 2 P
not yet acknowledged?
ACK_SN =3 and NACK_SN =2.
13 Check: Does the UE transmit an RRC - 3 P
Connection Re-establishment Request
message?
Note 1
14 The SS transmits - - - -
RRCConnectionReestablishment message.
15 The UE transmits - - - -
RRCConnectionReestablishmentComplete
message.
16 The SS transmits an - - - -
resume SRB2 and DRB1.
- EXCEPTION: Step 17 and Step 18 can - - - -
happen in any order.
17 The UE transmits an - - - -
message.
18 The UE retransmits the AMD PDU not yet --> AMD PDU#3 (SN=0) - -
acknowledged.
Note 2.
Note 1: The RRC Connection Re-establishment procedure is initiated. See 36.331 cl. 5.3.7.2 and 5.3.11.3.
Note 2: The PDCP PDU contained in this AMD PDU carries PDCP SN=2.
ETSI

c1 CHOICE{
dicated-HO
}
}
}
}
7.2.3.17 AM RLC / Re-segmentation RLC PDU / SO, FI, LSF

(1)
ensure that {
when { AMD PDU to be retransmitted does not fit in new allocated TBS }
then { UE segments AMD PDU into AMD PDU segments }
}
(2)
ensure that {
when { AMD PDU segment to be retransmitted does not fit in new allocated TBS }
then { UE resegments AMD PDU segment to fit TBS }
}
4.2.1.3.2, 5.2.1, 6.2.1.4 and 6.2.1.5.
[TS 36.322, clause 4.2.1.3.2]
The transmitting side of an AM RLC entity supports retransmission of RLC data PDUs (ARQ):
- if the RLC data PDU to be retransmitted does not fit within the total size of RLC PDU(s) indicated by lower
layer at the particular transmission opportunity notified by lower layer, the AM RLC entity can re-segment the
RLC data PDU into AMD PDU segments;
- the number of re-segmentation is not limited.
When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs received from upper layer or
AMD PDU segments from RLC data PDUs to be retransmitted, it shall:
- include relevant RLC headers in the RLC data PDU.
[TS 36.322 clause 5.2.1]
...
When retransmitting an AMD PDU, the transmitting side of an AM RLC entity shall:
ETSI
- if the AMD PDU can entirely fit within the total size of RLC PDU(s) indicated by lower layer at the particular
transmission opportunity:
- deliver the AMD PDU as it is except for the P field (the P field should be set according to sub clause 5.2.2) to
lower layer;
- otherwise:
- segment the AMD PDU form a new AMD PDU segment which will fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity and deliver the new AMD PDU segment
to lower layer.
When retransmitting a portion of an AMD PDU, the transmitting side of an AM RLC entity shall:
- segment the portion of the AMD PDU as necessary form a new AMD PDU segment which will fit within the
total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity and deliver the new
AMD PDU segment to lower layer.
When forming a new AMD PDU segment, the transmitting side of an AM RLC entity shall:
- only map the Data field of the original AMD PDU to the Data field of the new AMD PDU segment;
- set the header of the new AMD PDU segment in accordance with the description in sub clause 6.;
- set the P field according to sub clause 5.2.2.
[TS 36.322, clause 6.2.1.4]
AMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI
....
[TS 36.322, clause 6.2.1.5]
AMD PDU segment consists of a Data field and an AMD PDU segment header.
AMD PDU segment header consists of a fixed part (fields that are present for every AMD PDU segment) and an
extension part (fields that are present for an AMD PDU segment when necessary). The fixed part of the AMD PDU
segment header itself is byte aligned and consists of a D/C, a RF, a P, a FI, an E, a SN, a LSF and a SO. The extension
part of the AMD PDU segment header itself is byte aligned and consists of E(s) and LI(s).
An AMD PDU segment header consists of an extension part only when more than one Data field elements are present
in the AMD PDU segment, in which case an E and a LI are present for every Data field element except the last.
Furthermore, when an AMD PDU segment header consists of an odd number of LI(s), four padding bits follow after the
last LI.
...
System Simulator:
- Cell 1.
ETSI
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loop back size of 98 bytes and the
exceptions listed in table 7.2.3.17.3.1-1 applicable for the configured AM DRB.
Parameter Value
ETSI

U-S Message/PDU/SDU
0 The SS stops the UL grant transmission. - - - -
1A 60 ms after step 1 the SS assigns one default <-- (UL grant, 840 bits) - -
grant (UL grant allocation type 2). (Note 6)
2 The UE transmits an AMD PDU with the same --> AMD PDU#1 (SN=0) - -
data contents as received in the corresponding
part of DL PDU#1?
3 20 ms after step 1 The SS transmits one AMD <-- AMD PDU#2 - -
PDU containing SDU#2 (100 bytes) in its data
field.
3A 60 ms after step 3 the SS assigns one default <-- (UL grant, 840 bits) - -
grant (UL grant allocation type 2). (Note 6)
4 The UE transmits an AMD PDU with the same --> AMD PDU#2 (SN=1) - -
data contents as received in the corresponding
part of DL PDU#2?
5 Void - - - -
6 The SS transmits a STATUS PDU. This PDU <-- STATUS PDU - -
nacks the AMD PDU with SN=0. NACK_SN=0
and ACK_SN=2.
6A The SS waits for 20 ms and then allocates 2 <-- (UL grants, 472 bits) - -
UL grants (UL grant allocation type 2) of size
472 bits such that there is 20 ms gap between
UL grants (Note 1, Note 4)
7 Check: Does the UE transmit an AMD PDU --> AMD PDU#1 segment 1 (SN=0) 1 P
segment with SO=0, LSF=0 and the same data
contents at the received positions as in the
original AMD PDU?
8 Check: Does the UE transmit an AMD PDU --> AMD PDU#1 segment 2 (SN=0) 1 P
segment with SO=<x>, LSF=1 and the same
data contents at the received positions as in
the original AMD PDU? (Note 3)
9 Void - - - -
10 After 100 ms the SS transmits a STATUS <-- STATUS PDU - -
PDU. This PDU nacks the AMD PDU with
SN=0. NACK_SN=0, SOStart=0, SOEnd=<x-
1> and ACK_SN =2. (Note 3, Note 5)
10 The SS waits for 20 ms and then allocates 2 <-- (UL grants, 472 bits) - -
A UL grants (UL grant allocation type 2) of size
328 bits such that there is 20 ms gap between
UL grants (Note 2) (Note 4)
st
11 Check: Does the UE transmit an AMD PDU --> AMD PDU#1 segment 1, 1 part 2 P
segment with SO=0, LSF=0 and the same data (SN=0)
contents at the received positions as in the
original AMD PDU?
nd
12 Check: Does the UE transmit an AMD PDU --> AMD PDU#1 segment 1, 2 part 2 P
segment with SO=<y>, LSF=0 and the same (SN=0)
data contents at the received positions as in
the original AMD PDU? (Note 3)
13 The SS transmits a STATUS PDU. This PDU <-- STATUS PDU - -
acks the AMD PDUs with SN=0 and SN=1.
ACK_SN=2.
Note 1: UL grant of 472 bits (ITBS=7, NPRB=4, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will segment
into 2 AMD PDUs. MAC PDU of 472 bits=59 bytes fits an AMD PDU payload of >= 50 bytes + 2 bytes AMD
PDU header + 2 bytes of segment header + ? bytes spare for MAC header and possible RLC STATUS
PDU and BSR report.
Note 2: UL grant of 328 bits (ITBS=5, NPRB=4, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will segment
into 2 AMD PDUs. MAC PDU of 328 bits=41 bytes fits an AMD PDU payload of >= 25 bytes + 2 bytes AMD
PDU header + 2 bytes of segment header + ? bytes spare for MAC header and possible RLC STATUS
PDU and BSR report.
Note 3: The values x and y depend upon the need of the UE to add RLC STATUS PDU and BSR report. The TBS has
been chosen to ensure that the PDUs to be resegmented can be carried in 2 segments.
ETSI
Note 5: As <x> becomes available in step 8 only the transmission in step 10 can only be scheduled afterwards. This
requires a 100 ms activation time.
one PDU at a time.
None.
7.2.3.18 AM RLC / Reassembly / AMD PDU reassembly from AMD PDU segments,
Segmentation Offset and Last Segment Flag fields
(1)
ensure that {
when { UE receives AM PDU segments }
then { UE delivers reassembled RLC SDU to upper layer}
}
(2)
ensure that {
when { UE receives RLC AM PDU segments without segment header extension part }
then { UE correctly reassembles RLC AMD PDU segments into RLC AMD PDUs }
}
(3)
ensure that {
when { UE receives RLC AM PDU segments with segment header extension part }
then { UE correctly reassembles RLC AMD PDU segments into RLC AMD PDUs }
}
(4)
ensure that {
when { UE receives duplicate RLC AM PDU segments }
then { UE discards duplicate RLC AMD PDU segments }
}
(5)
ensure that {
when { UE receives RLC AM PDU segments out of sequence }
then { UE delivers reassembled RLC SDU to upper layer }
}
(6)
ensure that {
when { UE receives RLC AMD PDU segments with segments lost }
then { UE transmits STATUS PDU to request retransmission of missing segments }
}
(7)
ensure that {
when { UE receives overlapping RLC AMD PDU segments }
then { UE discards duplicate RLC AMD PDU byte segments }
}
ETSI
4.2.1.3.3, 5.1.3.2.2, 6.2.1.4 and 6.2.1.5.
[TS 36.322, clause 4.2.1.3.3]
PDUs;
- reorder the RLC data PDUs if they are received out of sequence;
sequence.
...
[TS 36.322, clause 5.1.3.2.2]
When a RLC data PDU is received from lower layer, where the RLC data PDU contains byte segment numbers y to z of
an AMD PDU with SN = x, the receiving side of an AM RLC entity shall:
- if x falls outside of the receiving window; or
- if byte segment numbers y to z of the AMD PDU with SN = x have been received before:
- discard the received RLC data PDU;
- else:
- place the received RLC data PDU in the reception buffer;
- if some byte segments of the AMD PDU contained in the RLC data PDU have been received before:
- discard the duplicate byte segments.
[TS 36.322, clause 6.2.1.4]
AMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI.
...
[TS 36.322, clause 6.2.1.5]
AMD PDU segment consists of a Data field and an AMD PDU segment header.
AMD PDU segment header consists of a fixed part (fields that are present for every AMD PDU segment) and an
extension part (fields that are present for an AMD PDU segment when necessary). The fixed part of the AMD PDU
segment header itself is byte aligned and consists of a D/C, a RF, a P, a FI, an E, a SN, a LSF and a SO. The extension
part of the AMD PDU segment header itself is byte aligned and consists of E(s) and LI(s).
An AMD PDU segment header consists of an extension part only when more than one Data field elements are present
in the AMD PDU segment, in which case an E and a LI are present for every Data field element except the last.
ETSI
Furthermore, when an AMD PDU segment header consists of an odd number of LI(s), four padding bits follow after the
last LI.
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loop back size of 98 bytes.
ETSI

U-S Message/PDU/SDU
1 The SS transmits an AMD PDU containing the <-- AMD PDU#1 (SN=WindowSize+3) - -
first half (50 bytes) of SDU#1 in its data field.
This PDU is in error (SN falls outside of the
receiving window) and is to be discarded by
the UE.
2 The SS transmits an AMD PDU containing <-- AMD PDU#2 (SN=1, P=1) - -
SDU#2 (100 bytes) in its data field with the P-
bit set.
NACK_SN field indicating missing PDU#1.
ACK_SN=2, NACK_SN=0.
3A The SS stops the UL grant transmission. - - - -
4 After 100 ms the SS transmits an AMD PDU <-- AMD PDU#1 (SN=0) - -
segment of AMD PDU#1 (AMD PDU#1 carries segment 1
SDU#1) containing the first 50 bytes of SDU#1
in its data field. SO=0 and LSF=0. No header
extension part is provided.
5 The SS transmits an AMD PDU segment of <-- AMD PDU #1 (SN=0, P=1) - -
AMD PDU#1 (AMD PDU#1 carries SDU#1) segment 2
containing the last 50 bytes of SDU#1 in its
data field with the P-bit set. SO=50 and
LSF=1. No header extension part is provided.
5A The SS waits for 60 ms to ensure UE RLC has <-- (UL grant) - -
assigns one default UL grant (UL grant
allocation type 3).
with ACK_SN=2, thus acknowledging the
reception of PDUs with SN=0 and SN=1, and
no NACK_SN provided?
7 Check: Does the UE transmit RLC SDU#1 and --> AMD PDU (RLC SDU#1, RLC 1 P
RLC SDU#2? SDU#2)
8 Void - - - -
9 After 100 ms the SS transmits an AMD PDU <-- AMD PDU#3 (SN=2, P=1) - -
SDU#3 and SDU#4) containing the last 50
bytes of SDU#4 in its data field, with the P-bit
set. FI=10, SO=150 and LSF=1. No header
9A 100 ms after step 9 the SS assigns one default <-- (UL grant) - -
grant (UL grant allocation type 3).
10 The UE transmits a STATUS PDU NACK_SN --> STATUS PDU - -
field for receipt of PDU#3. ACK_SN=3,
NACK_SN=2, SOStart=0/SOEnd=149.
SDU#3 and SDU#4) containing SDU#3 (100
bytes) and the first 50 bytes of SDU#4 in its
data field, with the P-bit set. FI=01, SO=0 and
LSF=0. Header extension part present: E in
fixed part header=1, E in extension part
header=0, LI=100.
11 The SS waits for 60 ms to ensure UE RLC has <-- (UL grant) - -
allocation type 3).
with ACK_SN=3?
13 Void - - - -
14 Check: Does the UE transmit RLC SDU#3 and --> AMD PDU (RLC SDU#3, RLC 1,5 P
RLC SDU#4? SDU#4)
ETSI

A
16 The SS transmits an AMD PDU segment of <-- AMD PDU#4 (SN=3) - -
containing the first 50 bytes of SDU#5 in its
data field. SO=0 and LSF=0. No header
17 The SS transmits an AMD PDU segment of <-- AMD PDU#4 (SN=3, P=1) - -
containing the last 50 bytes of SDU#5 in its
data field, with the P-bit set. SO=50 and
allocation type 3).
reception of PDUs with SN=0 to SN=3, and no
NACK_SN provided?
A
SDU#7) containing the last 50 bytes of SDU#7
in its data field, with the P-bit set. This AMD
PDU segment is sent with SN=5. SO=50 and
20 100 ms after step 20 the SS assigns one <-- (UL grant) - -
A default grant (UL grant allocation type 3).
reception of PDUs with SN=0 to SN=5, and
NACK_SN=4, E1/E2 field for receipt of PDU#5
and NACK_SN=5, SOStart=0/SOEnd=49 for
segment 1 of PDU#6?
23 The SS transmits one AMD PDU containing <-- AMD PDU#5 (SN=4, P=1) - -
SDU#6 (100 bytes) in its data field, with the P-
bit set.
allocation type 3).
ACK_SN=6, thus acknowledging the reception
of PDUs with SN=0 to SN=5, and no
NACK_SN provided.
25 Void - - - -
26 Check: Does the UE transmit RLC SDU#6 and --> AMD PDU (RLC SDU#6, RLC 2,5 P
RLC SDU#7? SDU#7)
A
SDU#8, SDU#9 and SDU#10) containing the
last 20 bytes of SDU#9 and the complete
SDU#10 (100 bytes) in its data field, with the
ETSI
P-bit set. FI=10, SO=180 and LSF=1. Header

extension part present: E in fixed part
header=1, E in extension part header=0,
LI=20.
27 100 ms after step 27 the SS assigns one <-- (UL grant) - -
A default grant (UL grant allocation type 3).
28 The UE transmits a STATUS PDU NACK_SN --> STATUS PDU - -
SDU#8, SDU#9 and SDU#10) containing the
last 20 bytes of SDU#8 and the complete
SDU#9 in its data field, with the P-bit set.
FI=10, SO=80 and LSF=0. Header extension
part present: E in fixed part header=1, E in
extension part header=0, LI=20.
29 30 ms after step 29 the SS assigns one default <-- (UL grant) - -
A grant (UL grant allocation type 3).
30 The UE transmits a STATUS PDU NACK_SN --> STATUS PDU 7 P
31 60 ms after step 29 the SS transmits an AMD <-- AMD PDU#7 (SN=6, P=1) - -
PDU segment of AMD PDU#7 (AMD PDU#7 segment 1
carries SDU#8, SDU#9 and SDU#10)
containing the first 80 bytes of SDU#8 in its
data field, with the P-bit set. SO=0 and LSF=0.
No header extension part is provided.
Note 4
allocation type 3).
reception of PDUs with SN=0 to SN=6, and no
NACK_SN provided?
33 Void - - - -
34 Void - - - -
35 Check: Does the UE transmit RLC SDU#8, --> AMD PDU (RLC SDU#8, RLC 7 P
RLC SDU#9 and RLC SDU#10? SDU#9, RLC SDU#10)
Note 1: From steps 4 onwards, the transmission of AMD PDUs is scheduled. The activation time of 100 ms for the
first of possibly several AMD PDUs is greater than t-StatusProhibit, and therefore there is no need to wait
for the expiry of this timer. Subsequent AMD PDU transmissions are using subsequent TTIs.
Note 2: In steps 6-8, 12-14, 18-19, 24-26, 32-35 the STATUS PDU and the AMD PDU consisting of one or more
RLC SDUs are received as a PDU list in one TTI.
Note 3: In step 29A it is assumed that the UE will react upon the AMD PDU within 30 ms.
Note 4: Step 31 shall be executed within 60 ms after step 29 to ensure that the UE receives the AMD PDU before
the expiry of t-Reordering at the UE.
None.
7.2.3.19 Void
7.2.3.20 AM RLC / Duplicate detection of RLC PDUs
(1)
ensure that {
when { UE is in AM mode and receives duplicated RLC data PDUs having the same sequence number}
then { UE discards the duplicated RLC data PDUs }
ETSI
References: The conformance requirements covered in the current TC are specified in: TS 36.322, clause 4.2.1.3.3.
[TS 36.322, clause 4.2.1.3.3]
PDUs;
System Simulator:
- Cell 1.
UE:
None.
Preamble:

U-S Message
1 SS creates 3 RLC SDUs of size 40 bytes <-- RLC AMD PDU#1 (SN=0) - -
segmented into two AMD PDUs each. AMD RLC AMD PDU#2 (SN=1)
PDU#1 and AMD PDU#2 belong to RLC RLC AMD PDU#3 (SN=2)
SDU#1, AMD PDU#3 and #4 belong to RLC RLC AMD PDU#3 (SN=2)
SDU#2 and AMD PDU#5 and #6 belong to
RLC SDU#3.
SS transmits AMD PDU#1 with SN=0, AMD

PDU#2 with SN=1 and AMD PDU#3 twice with
SN=2.
(Note 1)
3 SS transmits AMD PDU#4 with SN=3. <-- RLC AMD PDU#4 (SN=3) - -
5 SS transmits AMD PDU#6 twice with SN=5. <-- RLC AMD PDU#6 (SN=5) - -
RLC AMD PDU#6 (SN=5)
6 SS transmits AMD PDU#5 twice with SN=4. <-- RLC AMD PDU#5 (SN=4) - -
RLC AMD PDU#5 (SN=4)
7 Check: Does the UE transmit RLC SDU#3 --> (RLC SDU#3) 1 P
once?
(Note 2)
Note 1: The duplicated AMD PDU#3 have been discarded by the conformant UE in step 1.
Note 2: The duplicated AMD PDU#5 and AMD PDU#6 have been discarded by the conformant UE in steps 5 and
6.
7.2.3.20.3.3 Specific message content
None.
ETSI
7.2.3.21 AM RLC / RLC re-establishment at RRC connection reconfiguration including

mobilityControlInfo IE
(1)
ensure that {
when { UE is requested to perform a RRC Connection reconfiguration including mobilityControlInfo
IE }
then { UE discards the remaining AMD PDUs; and discards all RLC SDUs in the transmitting side;
and reset all state variables to their initial values. }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.322, clause 5.4 and TS
36.331 clause 5.3.5.4.
[TS 36.322, clause 5.4]
RLC re-establishment is performed upon request by RRC, and the function is applicable for AM, UM and TM RLC
entities.
When RRC indicates that an RLC entity should be re-established, the RLC entity shall:
- if it is an AM RLC entity:
- when possible, reassemble RLC SDUs from any byte segments of AMD PDUs with SN < VR(MR) in the
receiving side, remove RLC headers when doing so and deliver all reassembled RLC SDUs to upper layer in
ascending order of the RLC SN, if not delivered before;
- discard the remaining AMD PDUs and byte segments of AMD PDUs in the receiving side;
- discard all RLC SDUs and AMD PDUs in the transmitting side;
- discard all RLC control PDUs.
- stop and reset all timers;
- reset all state variables to their initial values.
[TS 36.331, clause 5.3.5.4]
If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the
configuration included in this message, the UE shall:
….
1> re-establish RLC for all RBs that are established;
System Simulator:
- Cell 1.
UE:
None.
ETSI
Preamble:
1.
Parameter Value
t-Reordering ms150

U-S Message
1 SS creates 3 RLC SDUs of size 40 bytes <-- AMD PDU#1 - -
segmented into two AMD PDUs each. AMD AMD PDU#2
PDU#1 and AMD PDU#2 belong to RLC AMD PDU#4
SDU#1, AMD PDU#3 and #4 belong to RLC
SDU#2 and AMD PDU#5 and #6 belong to
RLC SDU#3. SS transmits AMD PDU#1
(SN=0), AMD PDU#2 (SN=1) and AMD
PDU#4 (SN=3).
1A 60 ms after step 1 the SS allocates 1 UL grant <-- (UL grant)
of default size (UL grant allocation type 3).
2 The UE returns RLC SDU#1. --> (RLC SDU#1) - -
3 SS does not acknowledge the reception of - - - -
RLC SDU#1.
4 90 ms after step 1 SS performs a RRC - - - -
Connection Reconfiguration procedure
including the mobilityControlInfo IE triggering
RLC-reestablishment.
(Note 1)
A transmissions
4A The UE retransmits RLC SDU #1. --> (RLC SDU#1) - -

(Note 1A)
4B SS transmits a STATUS PDU (ACK_SN = 1). <-- STATUS PDU - -
5 SS transmits AMD PDU#5 with SN=0 and the <-- AMD PDU#5 - -
P field set to "1"
6 Check: Does the UE transmit a STATUS --> STATUS PDU (ACK_SN = 1) 1 P
PDU?
(Note 2)
7 SS transmits AMD PDU#6 with <-- AMD PDU#6 - -
SN=Receiving_AM_Window_Size+2
8 Check: Does the UE return RLC SDU#3 within (RLC SDU#3) 1 F
1s? -->
(Note 3)
9 SS transmits AMD PDU#6 with SN=1 <-- AMD PDU#6 - -
10 Check: Does the UE return RLC SDU#3 with (RLC SDU#3) 1 P
-->
its first AMD PDU set to SN=1?
Note 1: Upon a RLC re-establishment a conformant UE discards any remaining AMD PDUs in the receiver and
transmitter side, stops and resets all timers and resets all state variables to their initial values.
Note 1A: The UE will retransmit the PDCP SDU associated with RLC SDU#1 in accordance to TS 36.323 clause
5.2.1.1.
Note 2: AMD PDU#4 is discarded by a conformant UE in step 4.
Note 3: AMD PDU#6 is discarded by a conformant UE due to being outside the receiving window size.
ETSI
Derivation Path: 36.508 table 4.6.1-8: RRCConnectionReconfiguration, condition HO

c1 CHOICE{
mobilityControlInfo SEQUENCE {
targetPhysCellId Set to the physical cell
identity of cell 1
}
radioResourceConfigCommon Not present
}
}
}
}
7.3 PDCP
7.3.1 Maintenance of PDCP sequence numbers for radio bearers
7.3.1.1 Maintenance of PDCP sequence numbers / User plane / RLC AM
(1)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on AM RLC }
then { UE increments SN with 1 for each transmitted PDU for SN=0 to Maximum_PDCP_SN }
}
(2)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on AM RLC and, after incrementation,
Next_PDCP_TX_SN is larger than the Maximum_PDCP_SN }
then { UE sets SN to 0 in the next transmitted PDCP SDU}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.1.1,
5.1.2.2 and 6.2.3.
[TS 36.323, clause 5.1.1]
At reception of a PDCP SDU from upper layers, the UE shall:
- discardTimerstart the associated with this PDCP SDU (if configured);
For a PDCP SDU received from upper layers, the UE shall:
- associate the PDCP SN corresponding to Next_PDCP_TX_SN to this PDCP SDU;
- perform header compression of the PDCP SDU (if configured) as specified in the subclause 5.5.4;
- perform integrity protection (if applicable), and ciphering (if applicable) using COUNT based on TX_HFN and
the PDCP SN associated with this PDCP SDU as specified in the subclause 5.7 and 5.6, respectively;
- increment Next_PDCP_TX_SN by one;
ETSI
- if Next_PDCP_TX_SN > Maximum_PDCP_SN:
- set Next_PDCP_TX_SN to 0;
- increment TX_HFN by one;
- submit the resulting PDCP Data PDU to lower layer.
[TS 36.323, clause 5.1.2.1.2]
For DRBs mapped on RLC AM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- if received PDCP SN – Last_Submitted_PDCP_RX_SN > Reordering_Window or 0 <=

Last_Submitted_PDCP_RX_SN – received PDCP SN < Reordering_Window:
- if received PDCP SN > Next_PDCP_RX_SN:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN - 1 and the
received PDCP SN;
- else:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN and the
received PDCP SN;
- perform header decompression (if configured) as specified in the subclause 5.5.5;
- discard this PDCP SDU;
- else if Next_PDCP_RX_SN – received PDCP SN > Reordering_Window:
- increment RX_HFN by one;
- use COUNT based on RX_HFN and the received PDCP SN for deciphering the PDCP PDU;
- set Next_PDCP_RX_SN to the received PDCP SN + 1;
- else if received PDCP SN – Next_PDCP_RX_SN > =Reordering_Window:
- use COUNT based on RX_HFN – 1 and the received PDCP SN for deciphering the PDCP PDU;
- else if received PDCP SN >= Next_PDCP_RX_SN:
- if Next_PDCP_RX_SN is larger than Maximum_PDCP_SN:
- set Next_PDCP_RX_SN to 0;
- else if received PDCP SN < Next_PDCP_RX_SN:
- if the PDCP PDU has not been discarded in the above:
- perform deciphering and header decompression (if configured) for the PDCP PDU as specified in the
subclauses 5.6 and 5.5.5, respectively;
- if a PDCP SDU with the same PDCP SN is stored:
- else:
- store the PDCP SDU;
ETSI
- if the PDCP PDU received by PDCP is not due to the re-establishment of lower layers:
- deliver to upper layers in ascending order of the associated COUNT value:
- all stored PDCP SDU(s) with an associated COUNT value less than the COUNT value associated with
the received PDCP SDU;
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT value
associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers;
- else if received PDCP SN = Last_Submitted_PDCP_RX_SN + 1 or received PDCP SN =

Last_Submitted_PDCP_RX_SN – Maximum_PDCP_SN:
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT value
associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers.
[TS 36.323, clause 6.2.3]
Figure 6.2.3.1 shows the format of the PDCP Data PDU when a 12 bit SN length is used. This format is applicable for
PDCP Data PDUs carrying data from DRBs mapped on RLC AM or RLC UM.
Figure 6.2.3.1: PDCP Data PDU format for DRBs using a 12 bit SN
System Simulator
- Cell 1
- SS PDCP set to Transparent Mode
UE:
None.
Preamble
ETSI
U-S Message
- EXCEPTION: Steps 1 and 2 shall be repeated
for k=0 to Maximum_PDCP_SN (increment=1).
1 SS transmits a PDCP Data PDU on DRB1 <-- PDCP Data PDU (SN = k)
containing one IP packet without header
compression.
2 CHECK: Does UE transmit a PDCP Data PDU --> PDCP Data PDU (SN = k) 1 P
with SN=0 for the first iteration and then
incremented by 1 at each iteration?
3 SS transmits a PDCP Data PDU on DRB1 <-- PDCP Data PDU (SN = 0)
compression.
4 CHECK: Does UE transmit a PDCP Data PDU --> PDCP Data PDU (SN = 0) 2 P
with SN=0?
5 SS sends a PDCP Data PDU on DRB1 <-- PDCP Data PDU (SN = 1)
compression.
with SN=1?
None
7.3.1.2 Maintenance of PDCP sequence numbers / User plane / RLC UM / Short

PDCP SN (7 bits)
(1)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for short PDCP SN
size (7 bits)}
}
(2)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for short PDCP SN
size (7 bits); and, after incrementation, Next_PDCP_TX_SNis larger than the Maximum_PDCP_SN }
}
5.1.2.1.3 and 6.2.4.
[TS 36.323, clause 5.1.1]
- start the discardTimer associated with this PDCP SDU (if configured);
ETSI
[TS 36.323, clause 5.1.2.1.3]
For DRBs mapped on RLC UM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- if received PDCP SN < Next_PDCP_RX_SN:
- decipher the PDCP Data PDU using COUNT based on RX_HFN and the received PDCP SN as specified in the
subclause 5.6;
- if Next_PDCP_RX_SN > Maximum_PDCP_SN:
- perform header decompression (if configured) of the deciphered PDCP Data PDU as specified in the subclause
5.5.5;
- deliver the resulting PDCP SDU to upper layer.
[TS 36.323, clause 6.2.4]
PDCP Data PDUs carrying data from DRBs mapped on RLC UM.
Figure 6.2.4.1: PDCP Data PDU format for DRBs using 7 bit SN
System Simulator
- Cell 1
UE:
None.
Preamble
ETSI

U-S Message
1 SS transmits a PDCP Data PDU on UM DRB <-- PDCP Data PDU (SN = k)
compression.
3 SS transmits a PDCP Data PDU on UM DRB <-- PDCP Data PDU (SN = 0)
compression.
with SN=0?
5 SS sends a PDCP Data PDU on UM DRB <-- PDCP Data PDU (SN = 1)
compression.
with SN=1?
None
7.3.1.3 Maintenance of PDCP sequence numbers / User plane / RLC UM / Long

PDCP SN (12 bits)
(1)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for long PDCP SN size
(12 bits)}
}
(2)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for long PDCP SN size
(12 bits); and, after incrementation, Next_PDCP_TX_SN is larger than the Maximum_PDCP_SN limit }
}
5.1.2.1.3 and 6.2.3.
[TS 36.323, clause 5.1.1]
- start the discardTimer associated with this PDCP SDU (if configured);
ETSI
[TS 36.323, clause 5.1.2.1.3]
For DRBs mapped on RLC UM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- decipher the PDCP Data PDU using COUNT based on RX_HFN and the received PDCP SN as specified in the
subclause 5.6;
- perform header decompression (if configured) of the deciphered PDCP Data PDU as specified in the subclause
5.5.5;
- deliver the resulting PDCP SDU to upper layer.
[TS 36.323, clause 6.2.3]
PDCP Data PDUs carrying data from DRBs mapped on RLC AM or RLC UM.
Figure 6.2.3.1: PDCP Data PDU format for DRBs using a 12 bit SN
ETSI
System Simulator
- Cell 1
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] with the RLC UM bearer configured for long
PDCP SN size (12 bits).

U-S Message
1 SS transmits a PDCP Data PDU on UM DRB <-- PDCP Data PDU (SN = k)
compression.
3 SS transmits a PDCP Data PDU on UM DRB <-- PDCP Data PDU (SN = 0)
compression.
with SN=0?
5 SS sends a PDCP Data PDU on UM DRB <-- PDCP Data PDU (SN = 1)
compression.
with SN=1?
None
7.3.2 Void
7.3.3 PDCP ciphering and deciphering
7.3.3.1 Ciphering and deciphering / Correct functionality of EPS AS encryption
algorithms / SNOW 3G
(1)
with { UE in RRC_IDLE/E-UTRA RRC_CONNECTED state }
ensure that {
when { Functionality of EPS AS encryption algorithms with SNOW 3G is taken into use }
then { UE performs correct AS ciphering function in PDCP entities associated with SRBs. }
}
ETSI
References: The conformance requirements covered in the present TC are specified in: TS 36.323, clause 5.6 , TS
33.401, clause 5.1.3.2 and TS 36.331, clause 6.3.3.
[TS 36.323, clause 5.6]
The ciphering function includes both ciphering and deciphering and is performed in PDCP. For the control plane, the
data unit that is ciphered is the data part of the PDCP PDU (see subclause 6.3.3) and the MAC-I (see subclause 6.3.4).
For the user plane, the data unit that is ciphered is the data part of the PDCP PDU (see subclause 6.3.3); ciphering is not
applicable to PDCP Control PDUs.
The ciphering algorithm and key to be used by the PDCP entity are configured by upper layers [3] and the ciphering
method shall be applied as specified in [6].
The ciphering function is activated by upper layers [3]. After security activation, the ciphering function shall be applied
to all PDCP PDUs indicated by upper layers [3] for the downlink and the uplink, respectively.
The parameters that are required by PDCP for ciphering are defined in [6] and are input to the ciphering algorithm. The
required inputs to the ciphering function include the COUNT value, and DIRECTION (direction of the transmission: set
as specified in [6]).The parameters required by PDCP which are provided by upper layers [3] are listed below:
- BEARER (defined as the radio bearer identifier in [6]. It will use the value RB identity –1 as in [3]);
- KEY (the ciphering keys for the control plane and for the user plane are KRRCenc and KUPenc, respectively).
[TS 33.401, clause 5.1.3.2]
All algorithms specified in this subclause are algorithms with a 128-bit input key except Null ciphering algorithm.
NOTE: Deviations from the above requirement have to be indicated explicitly in the algorithm identifier list
below.
Each EPS Encryption Algorithm (EEA) will be assigned a 4-bit identifier. Currently, the following values have been
defined for NAS, RRC and UP ciphering:
"00012" 128-EEA1 SNOW 3G based algorithm
The remaining values have been reserved for future use.
UEs and eNBs shall implement EEA0, 128-EEA1 and 128-EEA2 for both RRC signalling ciphering and UP ciphering.
UEs and eNBs may implement 128-EEA3 for both RRC signalling ciphering and UP ciphering.
[TS 36.331, clause 6.3.3]
The IE SecurityAlgorithmConfig is used to configure AS integrity protection algorithm (SRBs) and AS ciphering
algorithm (SRBs and DRBs). For RNs, the IE SecurityAlgorithmConfig is also used to configure AS integrity protection
algorithm for DRBs between the RN and the E-UTRAN.
SecurityAlgorithmConfig field descriptions

cipheringAlgorithm
Indicates the ciphering algorithm to be used for SRBs and DRBs, as specified in TS 33.401 [32, 5.1.3.2].
integrityProtAlgorithm
Indicates the integrity protection algorithm to be used for SRBs, as specified in TS 33.401 [32, 5.1.4.2]. For RNs, also
indicates the integrity protection algorithm to be used for integrity protection-enabled DRB(s).
ETSI
System Simulator:
- Cell 1.
UE:
- None.
Preamble:
- The UE shall be in Registered Idle Mode (State 2) according to [18].

U-S Message
1 The SS sends a Paging message to the UE on the <-- Paging (PCCH) - -
appropriate paging block, and including the UE
identity in one entry of the IE pagingRecordLists.
2 Check: Does The UE transmit a --> RRCConnectionRequest 1 P
RRCConnectionRequest message without related
PDCP Data PDU being ciphered?
3 The SS transmits an RRCConnectionSetup RRCConnectionSetup - -
message. This message related PDCP Data PDU <--
should not be integrity protected and ciphered.
4 Check: Does the UE transmit a --> RRCConnectionSetupCompl 1 P
RRCConnectionSetupComplete message to ete
confirm the successful completion of the
connection establishment and to initiate the
session management procedure by including the
SERVICE REQUEST message (State3), and
without related PDCP Data PDU being ciphered?
5 The SS transmits a SecurityModeCommand <-- SecurityModeCommand - -
message to activate EPS AS encryption algorithm
security. The message related PDCP Data PDU
should be integrity protected but not ciphered.
6 Check: Does the UE transmit a --> SecurityModeComplete 1 P
SecurityModeComplete message and establishes
the initial security configuration without the
message related PDCP Data PDU being
ciphered?
7 The SS configures a new data radio bearer, <-- RRCConnectionReconfigurat - -
associated with the default EPS bearer context. ion
This message related PDCP Data PDU should be
integrity protected and ciphered. The COUNT of
this message related PDCP Data PDU can be
used for deciphering.
8 The UE transmits a --> RRCConnectionReconfigurat 1 P
RRCConnectionReconfigurationComplete ionComplete
message to confirm the establishment of the new
data radio bearer, associated with the default
EPS bearer context. This message related PDCP
Data PDU should be integrity protected and
ciphered. The COUNT of this message related
PDCP Data PDU can be used for deciphering.
ETSI
Table 7.3.3.1.3.3-1 SecurityModeCommand (step 6, Table 7.3.3.1.3.2-1)
Derivation Path: TS36.508 clause 4.6.1 table 4.6.1-19

SecurityModeCommand ::= SEQUENCE {
c1 CHOICE{
securityModeCommand-r8 SEQUENCE {
securityConfigSMC SEQUENCE {
securityAlgorithmConfig SEQUENCE {
cipheringAlgorithm eea1
integrityProtAlgorithm Default value specified
in TS 36.508
}
}
}
}
}
}
7.3.3.2 Ciphering and deciphering / Correct functionality of EPS UP encryption

algorithms / SNOW 3G
(1)
ensure that {
when { UE is requested to achieve functionality of EPS UP encryption algorithms with SNOW 3G }
then { UE performs correct UP ciphering function in PDCP entities associated with DRBs. }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.323, clause 5.6, TS
[TS 36.323, clause 5.6]
required inputs to the ciphering function include the COUNT value, and DIRECTION (direction of the transmission: 0
for uplink, 1 for downlink).The parameters required by PDCP which are provided by upper layers [3] are listed below:
[TS 33.401, clause 5.1.3.2]
ETSI
below.
"00012" 128-EEA1 SNOW 3G based algorithm
[TS 36.331, clause 6.3.3]

cipheringAlgorithm
System Simulator:
- Cell 1.
UE:
- None.
Preamble
- The UE shall be in Loopback Activation state (State 4) according to TS36.508.

U-S Message
1 SS Transmits PDCP PDU on DRB ciphered. <-- PDCP PDU - -
2 Check: Does the UE transmit loop backed PDCP --> PDCP PDU 1 P
PDU ciphered.
ETSI
Table 7.3.3.2.3.3-1 SecurityModeCommand (in the preamble)

c1 CHOICE{
}
}
}
}
}

algorithms / AES
(1)
ensure that {
when { UE is requested to achieve functionality of EPS AS encryption algorithms with AES }
}
[TS 36.323, clause 5.6]
[TS 33.401, clause 5.1.3.2]
below.
ETSI
"00102" 128-EEA2 AES based algorithm
[TS 36.331, clause 6.3.3]

cipheringAlgorithm
Same Pre-test conditions as in clause 7.3.3.1.3.1.
Same Test procedure sequence as in Table 7.3.3.1.3.2.
Table 7.3.3.3.3.3-1 SecurityModeCommand (step 6)

c1 CHOICE{
}
}
}
}
}
ETSI

algorithms / AES
(1)
ensure that {
when { UE is requested to achieve functionality of EPS UP encryption algorithms with AES }
}
[TS 36.323, clause 5.6]
[TS 33.401, clause 5.1.3.2]
below.
"00102" 128-EEA2 AES based algorithm
[TS 36.331, clause 6.3.3]
ETSI

cipheringAlgorithm
Table 7.3.3.4.3.3-1 SecurityModeCommand (in the preamble)

c1 CHOICE{
Not present
}
}
}
}
}

algorithms / ZUC
(1)
ensure that {
when { UE is requested to achieve functionality of EPS AS encryption algorithms with ZUC }
}
[TS 36.323, clause 5.6]
ETSI
[TS 33.401, clause 5.1.3.2]
below.
"00112" 128-EEA3 ZUC based algorithm
[TS 36.331, clause 6.3.3]

cipheringAlgorithm
ETSI
Table 7.3.3.5.3.3-1: SecurityModeCommand (step 6)

c1 CHOICE{
cipheringAlgorithm eea3-v11xy
}
}
}
}
}

algorithms / ZUC
(1)
ensure that {
when { UE is requested to achieve functionality of EPS UP encryption algorithms with ZUC }
}
[TS 36.323, clause 5.6]
required inputs to the ciphering function include the COUNT value, and DIRECTION (direction of the transmission: 0
for uplink, 1 for downlink).The parameters required by PDCP which are provided by upper layers [3] are listed below:
- KEY (the ciphering keys for the control plane and for the user plane are KRRCenc and KUPenc, respectively)
[TS 33.401, clause 5.1.3.2]
ETSI
below.
"00112" 128-EEA3 ZUC based algorithm
UEs and MMEs shall implement EEA0, 128-EEA1 and 128-EEA2 for NAS signalling ciphering. UEs and MMEs may
implement 128-EEA3 for NAS signalling ciphering.
[TS 36.331, clause 6.3.3]

cipheringAlgorithm
7.3.3.6.3.2 Test procedure sequences
Table 7.3.3.6.3.3-1: SecurityModeCommand (in the preamble)

c1 CHOICE{
CipheringAlgorithm eea3-v11xy
}
}
}
}
}
ETSI
7.3.4 PDCP integrity protection

7.3.4.1 Integrity protection / Correct functionality of EPS AS integrity algorithms /
SNOW3G
(1)
ensure that {
when { Functionality of EPS AS integrity algorithms with SNOW3G is taken into use }
then { UE performs the integrity protection function in PDCP entities associated with SRBs. }
}
(2)
ensure that {
when { SecurityModeCommand fails the integrity protection check }
then { UE transmits SecurityModeFailure message and continues using the configuration used
prior to the reception of the SecurityModeCommand message }
}
(3)
ensure that {
when { UE has AS security activated and integrity check fails }
then { UE initiates RRC connection re-establishment procedure }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.7,
clause 5.1.2.2, TS 33.401 clause 5.1.4.2 and TS 36.331 clause 6.3.3.
[TS 36.323, clause 5.7]
The integrity protection function includes both integrity protection and integrity verification and is performed in PDCP
for PDCP entities associated with SRBs. The data unit that is integrity protected is the PDU header and the data part of
the PDU before ciphering.
The integrity protection algorithm and key to be used by the PDCP entities are configured by upper layers [3] and the
integrity protection method shall be applied as specified in [6].
The integrity protection function is activated by upper layers [3]. After security activation, the integrity protection
function shall be applied to all PDUs including and subsequent to the PDU indicated by upper layers [3] for the
downlink and the uplink, respectively.
NOTE: As the RRC message which activates the integrity protection function is itself integrity protected with the
configuration included in this RRC message, this message needs first be decoded by RRC before the
integrity protection verification could be performed for the PDU in which the message was received.
The parameters that are required by PDCP for integrity protection are defined in [6] and are input to the integrity
protection algorithm. The required inputs to the integrity protection function include the COUNT value, and
DIRECTION (direction of the transmission: set as specification in [6]). The parameters required by PDCP which are
provided by upper layers [3] are listed below:
- KEY (KRRCint).
At transmission, the UE computes the value of the MAC-I field and at reception it verifies the integrity of the PDCP
PDU by calculating the X-MAC based on the input parameters as specified above. If the calculated X-MAC
corresponds to the received MAC-I, integrity protection is verified successfully.
ETSI
[TS 36.323, clause 5.1.2.2]
- if integrity verification is not applicable:
- deliver the resulting PDCP SDU to upper layer;
- else, if integrity verification is applicable and the integrity verification fails:
- discard the received PDCP Data PDU;
- indicate the integrity verification failure to upper layer.
[TS 33.401, clause 5.1.4.2]
All algorithms specified in this subclause are algorithms with a 128-bit input key.
below.
Each EPS Integrity Algorithm (EIA) will be assigned a 4-bit identifier. Currently, the following values have been
defined:
"00012" 128-EIA1 SNOW 3G
UEs and eNBs shall implement 128-EIA1 and 128-EIA2 for RRC signalling integrity protection. UEs and eNBs may
implement 128-EIA3 for RRC signalling integrity protection.
UEs shall implement EIA0 for integrity protection of NAS and RRC signalling. As specified in clause 5.1.4.1 of this
specification, EIA0 is only allowed for unauthenticated emergency calls. EIA0 shall not be used for integrity protection
between RN and DeNB.
Implementation of EIA0 in MMEs and eNBs is optional, EIA0, if implemented, shall be disabled in MMEs and eNBs in
the deployments where support of unauthenticated emergency calling is not a regulatory requirement.
[TS 36.331, clause 6.3.3]
ETSI

cipheringAlgorithm
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Registered, Idle Mode (State 2) according to [18].
ETSI

U-S Message
1 The SS sends a Paging message to the UE on - Paging (PCCH) - -
the appropriate paging block, and including the
UE identity in one entry of the IE
pagingRecordLists.
2 The UE transmit a RRCConnectionRequest --> RRCConnectionRequest - -
message .
message.
4 Does: The UE transmit a --> RRCConnectionSetupComplete 1 P
RRCConnectionSetupComplete message to
connection establishment and to initiate the
session management procedure by including
the SERVICE REQUEST message without
related PDCP Data PDU being integrity
protected?
message to activate AS security with
SNOW3G integrity algorithms protected.
SecurityModeComplete message with
SNOW3G integrity algorithms and RRC
integrity key protected and establish the initial
security configuration.
7 Check: Does the SecurityModeComplete - - 1 P
message from the UE pass the SS’ integrity
protection check.
message.
9 Wait for 5 s for the UE to enter E-UTRA - -
RRC_IDLE state.
a matched identity.
11 The UE transmit an RRCConnectionRequest --> RRCConnectionRequest - -
message.
message.
This message includes a SERVICE REQUEST
message.
message. MAC-I is calculated in such way, it
will result in integrity check failure on UE side.
15 Check: Does the UE transmit a --> SecurityModeFailure 2 P
SecurityModeFailure message without integrity
protection nor ciphering?
message to activate AS security with
SNOW3G integrity algorithms protected.
17 The UE transmits a SecurityModeComplete --> SecurityModeComplete - -
message. The message related PDCP Data
PDU should be integrity protected but not
ciphered.
18 The SS transmits an UECapabilityEnquiry <-- UECapabilityEnquiry - -
message to initiate the UE radio access
capability transfer procedure. MAC-I is
calculated in such way, it will result in integrity
check failure on UE side.
19 Check: Does the UE transmit a --> RRCConnectionReestablishment 3 P
RRCConnectionReestablishmentRequest Request
message on Cell 1?
ETSI
20 The SS transmits a <-- RRCConnectionReestablishment - -

RRCConnectionReestablishment message
21 The UE transmits --> RRCConnectionReestablishment - -
RRCConnectionReestablishmentComplete Complete
message.
A RRCConnectionReconfiguration message.
B RRCConnectionReconfigurationComplete omplete
message.
indicate that the UE is in E-UTRA
Table 7.3.4.1.3.3-1: SecurityModeCommand message (steps 5, 14 and 16, Table 7.3.4.1.3.2-1)

c1 CHOICE{
integrityProtAlgorithm eia1 128-EIA1
SNOW 3G
}
}
}
}
}
}
Table 7.3.4.1.3.3-2: RRCConnectionReestablishmentRequest (step 19, Table 7.3.4.1.3.2-1)

RRCConnectionReestablishmentRequest ::=
SEQUENCE {
rrcConnectionReestablishmentRequest-r8
SEQUENCE {
ue-Identity SEQUENCE {
c-RNTI the value of the C-RNTI
of the UE
physCellId PhysicalCellIdentity of
Cell 1
shortMAC-I The same value as the
16 least significant bits of
the XMAC-I value
calculated by SS
}
reestablishmentCause otherFailure
}
}
}
ETSI

AES
(1)
ensure that {
when { Functionality of EPS AS integrity algorithms with AES is taken into use }
}
(2)
ensure that {
}
(3)
ensure that {
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.7,
clause 5.1.2.2, TS 33.401 clause 5.1.4.2 and TS 36.331 clause 6.3.3.
[TS 36.323, clause 5.7]
The integrity protection algorithm and key to be used by the PDCP entities are configured by upper layers [3] and the
DIRECTION (direction of the transmission: set as specification in [6]). The parameters required by PDCP which are
- KEY (KRRCint).
ETSI
[TS 36.323, clause 5.1.2.2]
- if integrity verification is not applicable:
- indicate the integrity verification failure to upper layer.
[TS 33.401, clause 5.1.4.2]
below.
defined:
"00102" 128-EIA2 AES
[TS 36.331, clause 6.3.3]
ETSI

cipheringAlgorithm
Same Test procedure sequence as in table 7.3.4.1.3.2-1, except the integrity protection algorithm is AES.
Table 7.3.4.2.3.3-1: SecurityModeCommand message (step 5, 14 and 16, Table 7.3.4.1.3.2-1)

c1 CHOICE{
integrityProtAlgorithm eia2 128-EIA2 AES
}
}
}
}
}
}

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS
}
}
}
}
ETSI

ZUC
(1)
ensure that {
when { Functionality of EPS AS integrity algorithms with ZUC is taken into use }
}
(2)
ensure that {
}
(3)
ensure that {
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.7,
clause 5.1.2.2, TS 33.401 clause 5.1.4.2 and TS 36.331 clause 6.3.3
[TS 36.323, clause 5.7]
For RNs, the integrity protection function is performed also for PDCP entities associated with DRBs if integrity
protection is configured.
The integrity protection algorithm and key to be used by the PDCP entity are configured by upper layers [3] and the
DIRECTION (direction of the transmission: set as specified in [6]). The parameters required by PDCP which are
- KEY (KRRCint).
- for RNs, KEY (KUPint)
ETSI
[TS 36.323, clause 5.1.2.2]
if integrity verification is not applicable:
- indicate the integrity verification failure to upper layer
[TS 33.401, clause 5.1.4.2]
below.
defined:
"00112" 128-EIA3 ZUC
[TS 36.331, clause 6.3.3]
ETSI

cipheringAlgorithm
Same Test procedure sequence as in table 7.3.4.1.3.2-1, except the integrity protection algorithm is ZUC.
Table 7.3.4.3.3.3-1: SecurityModeCommand message (step 5, 14 and 16, Table 7.3.4.1.3.2-1)

c1 CHOICE{
integrityProtAlgorithm eia3-v11xy 128-EIA3 ZUC
}
}
}
}
}
}

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS
}
}
}
}
ETSI
7.3.5 PDCP handover

7.3.5.1 Void
7.3.5.2 PDCP handover / Lossless handover / PDCP sequence number
maintenance
(1)
with {UE in E-UTRA RRC_CONNECTED state with default RB using RLC-AM}
ensure that {
when { UE is requested to make a lossless handover by SS }
then { UE retransmits the unacknowledged data}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.2.1.1.
[TS 36.323, clause 5.2.1.1]
When upper layers request a PDCP re-establishment, the UE shall:
- reset the header compression protocol for uplink (if configured);
- apply the ciphering algorithm and key provided by upper layers during the re-establishment procedure;
- from the first PDCP SDU for which the successful delivery of the corresponding PDCP PDU has not
been confirmed by lower layers, perform retransmission or transmission of all the PDCP SDUs already
associated with PDCP SNs in ascending order of the COUNT values associated to the PDCP SDU prior
to the PDCP re-establishment as specified below:
- perform ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in
the subclause 5.6;
- submit the resulting PDCP Data PDU to lower layer
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] and table 7.3.5.2.3. 3-2 for SR configuration.
ETSI
Table 7.3.5.2.3.2.0-1: Time instances of cell power level

T1 -85 -79
EPRE Hz
ETSI

U-S Message
1 The SS creates 5 PDCP Data PDUs and the - - - -
Next_PDCP_TX_SN is set to "0".
- EXCEPTION: Step 2 and 3 A shall be - - - -
repeated for k=0 to 1(increment=1).
2 The SS sends the PDCP Data PDU#k via <-- PDCP PDU DATA #k - -
RLC-AM RB with the following content to the
UE:
D/C field = 1 (PDCP Data PDU) and PDCP
SN = k.
After having sent a PDU, the SS set
Next_PDCP_TX_SN= k+1.
3 The UE sends the PDCP Data PDU#k via --> PDCP PDU DATA #k - -
UE:
SN = k.
Data is previously received data from PDU #k.
(Note 1)
3A Wait for the expiry of t-PollRetransmit - - - -
4 Configure SS not to allocate UL grant to the - - - -
UE in Cell 1.
- EXCEPTION: Step 5 shall be repeated for - -
m=2 to 4 (increment=1).
5 The SS sends the PDCP Data PDU #m via <-- PDCP PDU DATA #m - -
UE:
D/C field = 1 (PDCP Data PDU) and PDCP SN
=m.
Next_PDCP_TX_SN = m+1.
5A The SS changes Cell 2 parameters according - - - -
to the row "T1" in table 7.3.5.2.3.2.0-1.
5B Configure SS to allocate Default UL grant to - - - -
the UE in Cell 2 (Note 2).
Note: These grants will be requested by the
UE to send data after the handover
6 The SS requests UE to make a handover to <-- RRCConnectionReconfiguration - -
Cell2 with the RRCConnectionReconfiguration
message sent on Cell 1.
7 SS assigns UL grant during the Random - - - -
Access procedure to allow the UE to send only
message.
8 The UE on Cell 2 transmits a --> RRCConnectionReconfigurationC - -
message.
8A The UE send PDCP Control PDUs via RLC- --> PDCP STATUS REPORT - -
AM RB with the following content to the SS:
D/C field = 0 (PDCP control PDU) and PDU
Type =000, FMS field = 5.
8B The SS generates a PDCP status report <-- PDCP STATUS REPORT - -
message and sends it to UE: D/C field = 0
(PDCP control PDU) and PDU Type =000,
FMS field = 2.
8C Configure SS to allocate Default UL grant to - - - -
the UE in Cell 2
EXCEPTION: Step 9 shall be repeated for - - - -
m=2 to 4 (increment=1).
9 Check: Does the UE send the PDCP Data --> PDCP PDU DATA #m 1 P
PDU #m via RLC-AM RB with the following
content to the SS:
= m?
ETSI
Data is previously received data from PDU #m.

Note 1: The SS acknowledges the received data.
Note 2: SS transmit an UL grant of 72 bits (ITBS=2, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit
only PDCP Status report.

c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityControlInfo
-HO
Cell 2
}
}
}
}
}
Table 7.3.5.2.3. 3-2: SchedulingRequest-Config (RRC Connection Reconfiguration, preamble Table

4.5.3.3-1: Step8)

dsr-TransMax n64
7.3.5.3 PDCP handover / Non-lossless handover PDCP sequence number

maintenance
(1)
with {UE in E-UTRA RRC_CONNECTED state with bearer using RLC-UM}
ensure that {
when {UE is requested to make a non-lossless handover by SS}
then {UE transmits next PDCP Data PDU with SN value 0 }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.2.1.2.
[TS 36.323, clause 5.2.1.2]
When upper layers request a PDCP re-establishment, the UE shall:
- reset the header compression protocol for uplink (if configured);
- set Next_PDCP_TX_SN, and TX_HFN to 0;
- apply the ciphering algorithm and key provided by upper layers during the re-establishment procedure;
- for each PDCP SDU already associated with a PDCP SN but for which a corresponding PDU has not
previously been submitted to lower layers:
- consider the PDCP SDUs as received from upper layer;
ETSI
- perform transmission of the PDCP SDUs in ascending order of the COUNT value associated to the PDCP SDU
prior to the PDCP re-establishment, as specified in the subclause 5.1.1 without restarting the discard-Timer.
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:

T1 -85 -79
EPRE Hz
ETSI

U-S Message
1 The SS creates 3 PDCP Data PDUs and the - - - -
EXCEPTION: Step 2 and 3 shall be repeated
for k=0 to 1 (increment=1).
2 The SS sends the PDCP Data PDU #k via <-- PDCP PDU DATA #k - -
RLC-UM RB with the following content to the
UE:
SN = k.
3 The UE sends the PDCP Data PDU #k via --> PDCP PDU DATA #k
SS:
SN = k.
Data is previously received data PDU #k.
the UE in Cell 2
4 The SS requests UE to make a handover to <-- RRCConnectionReconfiguration
Cell 2 with the RRCConnectionReconfiguration
message.
4A SS assigns UL grant during the Random - - - -
message.
5 The UE transmits a --> RRCConnectionReconfigurationC -
message.
6 The SS sends the PDCP Data PDU #2 via <-- PDCP PDU DATA #2
UE:
SN = 2.
7 Check: Does the UE send the PDCP Data --> PDCP PDU DATA #2 1 P
PDU #2 via RLC-UM RB with the following
content back to the SS:
= 0.
Data is previously received data PDU #2.
ETSI
Table 7.3.5.3.3-1: RRCConnectionReconfiguration (step 4, 7.3.5.3.3.2-1)

c1 CHOICE{
-HO
Cell 2
}
}
}
}
}
7.3.5.4 PDCP handover / Lossless handover / PDCP status report to convey the
information on missing or acknowledged PDCP SDUs at handover
(1)
with { UE in E-UTRA RRC_CONNECTED state with default RB used RLC-AM mode }
ensure that {
when { UE is requested to make a handover by SS }
then { UE creates a PDCP status report to SS}}
(2)
with { UE in E-UTRA RRC_CONNECTED state with default RB used RLC-AM mode }
ensure that {
then { UE discards the corresponding PDCP PDU and PDCP SDU according to the PDCP status report
from SS }}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.3 and
5.4
[TS 36.323, clause 5.3.1]
When upper layers request a PDCP re-establishment, for radio bearers that are mapped on RLC AM, the UE shall:
- if the radio bearer is configured by upper layers to send a PDCP status report in the uplink, compile a status
report as indicated below after processing the PDCP Data PDUs that are received from lower layers due to the
re-establishment of the lower layers as specified in the subclause 5.2.2.1, and submit it to lower layers as the first
PDCP PDU for the transmission, by:
- setting the FMS field to the PDCP SN of the first missing PDCP SDU;
- if there is at least one out-of-sequence PDCP SDU stored, allocating a Bitmap field of length in bits equal to
the number of PDCP SNs from and not including the first missing PDCP SDU up to and including the last
out-of-sequence PDCP SDUs, rounded up to the next multiple of 8;
- setting as ‘0’ in the corresponding position in the bitmap field for all PDCP SDUs that have not been
received as indicated by lower layers, and optionally PDCP SDUs for which decompression have failed;
- indicating in the bitmap field as ‘1’ for all other PDCP SDUs.
[TS 36.323, clause 5.3.2]
ETSI
When a PDCP status report is received in the downlink, for radio bearers that are mapped on RLC AM:
- for each PDCP SDU, if any, with the bit in the bitmap set to '1', or with the associated COUNT value less than
the COUNT value of the PDCP SDU identified by the FMS field, the successful delivery of the corresponding
PDCP SDU is confirmed, and the UE shall process the PDCP SDU as specified in the subclause 5.4.
[TS 36.323, clause 5.4]
When the Discard_Timer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP
status report, the UE shall discard the PDCP SDU along with the corresponding PDCP PDU. If the corresponding
PDCP PDU has already been submitted to lower layers the discard is indicated to lower layers.
TC is applicable to:
- All UEs supporting E-UTRA.
System Simulator:
- Cell 1 and Cell 2
- ROHC is not used for headerCompression settings.
UE:
- UE in UE Loopback Activated test state (state 4) with default RB using RLC-AM in Cell 1 and table 7.3.5.4.
3.3-2 for SR configuration.
Table 7.3.5.4.3.2-1: Time instances of cell power level

T1 -85 -79
EPRE Hz
ETSI

U-S Message
1 Next_PDCP_TX_SN is set to "0". The SS - - -
creates 4 PDCP Data PDUs.
2 The SS sends the PDCP Data PDU #0 via <-- PDCP DATA PDU #0 - -
UE:
=0.
The SS sets Next_PDCP_TX_SN = 1.
3 The UE sends a PDCP Data PDU #0 via RLC- --> PDCP DATA PDU #0 - -
AM RB with the following content back to the
SS:
SN = 0
data: previously received packet.
(Note 1)
4 The SS is configured on Cell 1 not to send
RLC acknowledgements (RLC ACK s) to the
UE.
4A Configure SS not to allocate UL grant to the - - - -
UE in Cell 1.
5 After 100 ms the SS sends the PDCP Data <-- PDCP DATA PDU#1
PDU #1 via RLC-AM RB with the following
content to the UE:
=1.
The SS set Next_PDCP_TX_SN = 2.
5A The SS waits for 60 ms and then allocates 1 <-- (UL grants) - -
UL grants (UL grant allocation type 2, Default
UL Grant size) to enable UE to return PDCP
Data PDU
6 The UE sends a PDCP Data PDU #1 via RLC- --> PDCP DATA PDU#1
SS:
SN = 1
6B The SS ignores scheduling requests and does - - - -
not allocate any uplink grant in cell 2.
7 The SS requests UE to make a handover to <-- RRCConnectionReconfiguration - -
Cell2 with the RRCConnectionReconfiguration message.
message sent on Cell1.
message.
8 The UE transmits a --> RRCConnectionReconfigurationC - -
RRCConnectionReconfigurationComplete omplete message.
message on Cell2.
8A The SS generates a PDCP status report <-- PDCP status report - -
FMS field = 2.
8B SS waits for 500 ms of ensure UE PDCP has
discarded PDCP PDU and is ready to transmit
PDCP status report and then assigns 1 UL
bits. (Note 2)
9 Check: Does the UE send PDCP Control --> PDCP status report 1 P
PDUs via RLC-AM RB with the following
content to the SS: D/C field = 0 (PDCP control
ETSI
PDU) and PDU Type =000, FMS field = 2.

10 Void - - - -
10 Configure SS to allocate Default UL grant to - - - -
A the UE in Cell 2
EXCEPTION: Step 11 shall be repeated for
k=2 to 3 (increment=1).
11 The SS sends the PDCP Data PDU #k via <-- PDCP DATA PDU #k - -
UE:
= k.
Next_PDCP_TX_SN = k + 1.
12 Check: Does the UE send a PDCP Data --> PDCP DATA PDU #2 2 P
PDU#2 via RLC-AM RB with the following
SN = 2
13 Check: Does the UE send a PDCP Data --> PDCP DATA PDU #3 2 P
PDU#3 via RLC-AM RB with the following
=3
Note 1: The SS sends RLC ACK to the UE
Table 7.3.5.4.3.3-1: RRCConnectionReconfiguration (Step 7, table 7.3.5.4.3.2-2)

c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityControlInf
o-HO
Cell 2
}
RadioResourceConfigDedicated-HO {
drb-ToAddModifyList {
PDCP-Configuration-DRB-AM {
discardTimer infinity
rlc-AM SEQUENCE {
statusReportRequired TRUE
}
}
}
}
}
}
}
}
ETSI
Table 7.3.5.4.3.3-2: SchedulingRequest-Config (RRC Connection Reconfiguration, preamble Table

4.5.3.3-1: Step8 and table 7.3.5.4.3.2-2, step 7)

dsr-TransMax n64
7.3.5.5 PDCP handover / In-order delivery and duplicate elimination in the downlink
(1)
with { UE in E-UTRA RRC_CONNECTED state with default RB using RLC-AM }
ensure that {
then { UE achieves in-order delivery and duplicate elimination in the downlink }
}
5.1.2.1.2.
[TS 36.323, clause 5.1.2.1.2]
For DRBs mapped on RLC AM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- if received PDCP SN – Last_Submitted_PDCP_RX_SN > Reordering_Window or 0 <=

Last_Submitted_PDCP_RX_SN – received PDCP SN < Reordering_Window:
- if received PDCP SN > Next_PDCP_RX_SN:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN - 1 and the
received PDCP SN;
- else:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN and the
received PDCP SN;
- perform header decompression (if configured) as specified in the subclause 5.5.5;
- else if Next_PDCP_RX_SN – received PDCP SN > Reordering_Window:
- else if received PDCP SN – Next_PDCP_RX_SN >= Reordering_Window:
- use COUNT based on RX_HFN – 1 and the received PDCP SN for deciphering the PDCP PDU;
- else if received PDCP SN >= Next_PDCP_RX_SN:
- if Next_PDCP_RX_SN is larger than Maximum_PDCP_SN:
ETSI
- else if received PDCP SN < Next_PDCP_RX_SN:
- if the PDCP PDU has not been discarded in the above:
- perform deciphering and header decompression (if configured) for the PDCP PDU as specified in the
subclauses 5.6 and 5.5.5, respectively;
- if a PDCP SDU with the same PDCP SN is stored:
- else:
- store the PDCP SDU;
- if the PDCP PDU received by PDCP is not due to the re-establishment of lower layers:
- all stored PDCP SDU(s) with an associated COUNT value less than the COUNT value associated
with the received PDCP SDU;
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT
value associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers;
- else if received PDCP SN = Last_Submitted_PDCP_RX_SN + 1 or received PDCP SN =

Last_Submitted_PDCP_RX_SN – Maximum_PDCP_SN:
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT
value associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers.
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:

T1 -85 -79
EPRE Hz
ETSI

U-S Message
1 The Next PDCP_TX_SN is set to “0”. The SS - - - -
creates a PDCP Data PDU#0.
2 The SS sends the PDCP Data PDU#0 via <-- PDCP DATA PDU#0 - -
UE:
PDCP Data PDU #0 (
SN=0 )
(Note 1)
3 The UE transmits a PDCP Data PDU via RLC- --> PDCP DATA PDU #0 - -
SS
SN=0
data: previously received packet in PDCP Data
PDU#0
(Note 2)
4 Next_PDCP_TX_SN is set to 1. - - - -
The SS creates a PDCP Data PDU#1 (not

transmitted).
5 The Next_PDCP_TX_SN is set to “2”. The SS - - - -
creates a PDCP Data PDU #2.
6 The SS sends the PDCP Data PDU#2 via <-- PDCP DATA PDU #2 - -
UE:
PDCP Data PDU#1;
SN=2
(Note 3)
7 Check: Does the UE transmit a PDCP DATA --> PDCP DATA PDU#2 1 F
PDU#2?
the UE in Cell 2 (Note 6).
8 The SS requests UE to make a handover to <--- RRCConnectionReconfiguration - -
Cell 2 with the RRCConnectionReconfiguration
message.
message.
9 The UE transmits a --> RRCConnectionReconfigurationC - -
message in the new cell.
9A The UE send PDCP Control PDUs via RLC- --> PDCP STATUS REPORT - -
AM RB with the following content to the SS:
D/C field = 0 (PDCP control PDU) and PDU
Type =000, FMS field = 1, Bitmap = 0x80.
9B The SS generates a PDCP status report <-- PDCP STATUS REPORT - -
FMS field = 1.
9C Configure SS to allocate Default UL grant to - - - -
the UE in Cell 2
ETSI

UE:
PDCP Data PDU #0(
SN=0)
(Note 4)
11 Check: Does the UE transmit PDCP Data PDU --> PDCP DATA PDU #0 1 F
via RLC-AM RB with the following content
back to the SS?
SN=0
PDU #0
UE:
PDCP Data PDU#1 (
SN=1)
(Note 5)
13 Check: Does the UE transmit a PDCP Data --> PDCP DATA PDU #1 1 P
PDU via RLC-AM RB with the following
content back to the SS?
SN=1
PDU#1
14 Check: Does the UE transmit PDCP Data PDU --> PDCP DATA PDU #2 1 P
via RLC-AM RB with the following content
back to the SS?
SN=2
PDU#2
Note 1: PDCP Data PDU#0 is sent in RLC PDU#0: SN=0.
Note 2: The SS sends RLC ACK to the UE
Note 3: PDCP Data PDU #2 is sent in RLC PDU#2: SN=2
Note 4: PDCP Data PDU #0 is sent in RLC PDU#1: SN=1
Note 5: PDCP Data PDU #1 is sent in RLC PDU #2:SN = 2
Table 7.3.5.5.3.3-1: RRCConnectionReconfiguration (Step 4, Table 7.3.5.5.3.2-1)

c1 CHOICE{
-HO
Cell 2
}
}
}
}
}
ETSI
7.3.6 PDCP Others

7.3.6.1 PDCP Discard
(1)
ensure that {
when { the Discard Timer for a PDCP SDU expires }
then { UE discards the corresponding PDCP SDU }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.9.
[TS 36.323, clause 5.4]
When the Discard_Timer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP
status report, the UE shall discard the PDCP SDU along with the corresponding PDCP PDU. If the corresponding
PDCP PDU has already been submitted to lower layers the discard is indicated to lower layers.
System Simulator:
- Cell 1
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18 with the exceptions listed in table 7.3.6.1.3.1-1
applicable for the configured UM DRB and table 7.3.6.1.3.1-2 for SR configuration.
Table 7.3.6.1.3.1-1: PDCP Settings
Parameter Value
Discard_Timer 500 ms
Table 7.3.6.1.3.1-2: SchedulingRequest-Config (preamble Table 4.5.3.3-1: Step8)

dsr-TransMax n64
ETSI

U-S Message
- EXCEPTION: The SS should not allocate UL - - - -
grants unless when explicitly stated so in the
procedure.
1 The SS creates 5 PDCP Data PDUs and the - - -
2 Void
- EXCEPTION: Step 3 shall be repeated for k=0 to 2 - - - -
(increment=1) with the below specified PDU size
sent to the UE:
Data PDU#1 = 46 bytes for k=0
3 The SS sends a PDCP Data PDU via RLC-UM RB <-- PDCP DATA PDU (SN=k)
with the following content to the UE:
D/C field = 1 (PDCP Data PDU) and PDCP SN = k
After having sent a PDU, the SS sets
Next_PDCP_TX_SN = k+1.
4 Wait for Discard_Timer to expire. - - - -
Note: According to TS36.508, timer tolerance
should be 10% of Discard_Timer or 5 x RTT,
whichever is greater. RTT = 8 TTIs for FDD and
RTT = 16 TTIs for TDD
- EXCEPTION: Step 5 shall be repeated for k=3 to 4 - - - -
(increment=1) with the below specified PDU size
sent to the UE:
5 The SS sends a PDCP Data PDU via RLC-UM RB <-- PDCP DATA PDU (SN=k) - -
with the following content to the UE:
D/C field = 1 (PDCP Data PDU) and PDCP SN = k
Next_PDCP_TX_SN = k+1.
6 The SS resumes normal UL grant allocation. - - - -
7 Check: Does UE transmit a PDCP Data PDU # 4 of --> PDCP Data PDU # 4 1 P
size 94 bytes? (Note1)
8 Check: Does UE transmit a PDCP Data PDU # 5 of --> PDCP Data PDU # 5 1 P
size 110 bytes ? (Note1)
Note1: PDCP Data PDU contents are checked to verify that the UL PDU is same as the DL PDU.
None.
ETSI
8 RRC
8.1 RRC connection management procedures
8.1.1 Paging
8.1.1.1 RRC / Paging for connection in idle mode
(1)
ensure that {
when { UE receives a Paging message including an ue-Identity set an unmatched S-TMSI i.e. other
than the one allocated to the UE at the UE registration procedure }
then { UE does not establish an RRC connection }
}
(2)
ensure that {
when { UE receives a Paging message including an ue-Identity set to the S-TMSI which was allocated
to the UE at the UE registration procedure }
then { UE establishes an RRC connection }
}
5.3.3.2, 5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.2.3]
Upon receiving the Paging message, the UE shall:
1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:
2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:
3> forward the ue-Identity, and the cn-Domain to the upper layers.
...
[TS 36.331, clause 5.3.3.2]
The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in
RRC_IDLE.
Upon initiation of the procedure, the UE shall:
...
1>if access to the cell, as specified above, is not barred:
2> apply the default physical channel configuration as specified in 9.2.4;
2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;
2> apply the default MAC main configuration as specified in 9.2.2;
2> apply the CCCH configuration as specified in 9.1.1.2;
2> apply the timeAlignmentTimerCommon included in SystemInfoBlockType2;
ETSI
2> start timer T300;
2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;
NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up
to date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to
perform system information acquisition upon cell re-selection.
...
[TS 36.331, clause 5.3.3.3]
The UE shall set the contents of RRCConnectionRequest message as follows:
1> set the ue-Identity as follows:
2> if upper layers provide an S-TMSI:
3> set the ue-Identity to the value received from upper layers;
2> else:
3> draw a random value in the range 0 .. 240-1 and set the ue-Identity to this value;
NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.
1> set the establishmentCause in accordance with the information received from upper layers;
The UE shall submit the RRCConnectionRequest message to lower layers for transmission.
The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for
cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.
[TS 36.331, clause 5.3.3.4]
NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];
The UE shall:
1> stop timer T300;
2> if upper layers provide the ‘Registered MME’, include and set the registeredMME as follows:
ETSI
3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers:
4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the
‘Registered MME’ received from upper layers;
3> set the mmegi and the mmec to the value received from upper layers;
2> set the dedicatedInfoNAS to include the information received from upper layers;
procedure ends.
System Simulator:
- Cell 1.
UE:
None.
Preamble:

U-S Message
an unmatched identity (incorrect S-TMSI).
RRCConnectionRequest message within 5 s?
a matched identity.
RRCConnectionRequest message?
message.
6 Check: Does the UE transmit an --> RRCConnectionSetupComplete 2 P
including SERVICE REQUEST to confirm the
successful completion of the connection
establishment?
6A- Steps 6 to 9 of the generic radio bearer - - - -
6D establishment procedure (TS 36.508 4.5.3.3-1)
7 Check: Does the test result of generic test - - 1, 2 -
ETSI

pagingRecordList SEQUENCE (SIZE 1 entry
(1..maxPageRec)) OF SEQUENCE {
ue-Identity[1] CHOICE {
s-TMSI SEQUENCE {
mmec Set to the different value
from the S-TMSI of the
UE
m-TMSI Set to the different value
UE
}
}
}
}

establishmentCause mt-Access
}
}
}
8.1.1.2 RRC / Paging for notification of BCCH modification in idle mode

(1)
ensure that {
when { UE receives a Paging message including a systemInfoModification }
then { UE re-acquires and applies the new system information about the correct prach-ConfigIndex
in random access }
}
5.2.2.3, and 5.2.2.4.
[TS 36.331, clause 5.3.2.3]
1> if in RRC_IDLE, for each of the PagingRecord, if any included in the Paging message:
3> forward the ue-Identity and the cn-Domain to the upper layers;
1> if the systemInfoModification is included:
ETSI
2> re-acquire the required system information using the system information acquisition procedure as specified in
5.2.2.
...
[TS 36.331, clause 5.2.2.3]
The UE shall:
1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as
the 'required' system information:
2> if in RRC_IDLE:
3> the MasterInformationBlock and SystemInformationBlockType1 as well as SystemInformationBlockType2

through SystemInformationBlockType8, depending on support of the concerned RATs;
...
[TS 36.331, clause 5.2.2.4]
The UE shall:
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> if the procedure is triggered by a system information change notification:
2> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification
period following the one in which the change notification was received;
...
The UE may apply the received SIBs immediately, i.e. the UE does not need to delay using a SIB until all SI messages
have been received. The UE may delay applying the received SIBs until completing lower layer procedures associated
with a received or a UE originated RRC message, e.g. an ongoing random access procedure.
NOTE 3: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer
present, the UE should stop trying to acquire the particular SIB.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
ETSI

U-S Message
a matched identity.
message.
3A The UE transmits an --> RRCConnectionSetupComplete - -
message.
3B The SS transmits a SecurityModeCommand <-- SecurityModeCommand - -
message.
3C The UE transmits a SecurityModeComplete --> SecurityModeComplete - -
message.
3D The SS transmits an <-- RRCConnectionReconfiguration - -
RRCConnectionReconfiguration message.
3E The UE transmits an --> RRCConnectionReconfigurationC - -
message.
3F The SS transmits an RRCConnectionRelease <-- RRCConnectionRelease - -
message.
3G Wait for 5 s for the UE to enter E-UTRA - - - -
RRC_IDLE state.
4 The SS changes the prach-ConfigIndex in the - - - -
system information
a systemInfoModification.
6 Wait for 15s for the UE to receive system - - - -
information.
a matched identity.
7A Check: Does the UE re-transmit a random - - 1 P
access using prach-ConfigIndex given in step
4?
8 The UE transmit an RRCConnectionRequest --> RRCConnectionRequest - -
message.
message.
message.
message.
message.
RRCConnectionReconfiguration message.
message.
message.
RRC_IDLE state.
state on Cell 1?
ETSI
Table 8.1.1.2.3.3-1: RRCConnectionRequest (step 2 and step 8, Table 8.1.1.2.3.2-1)

}
}
}
Table 8.1.1.2.3.3-2A: RRCConnectionReconfiguration (step 3D and step 9D, Table 8.1.1.2.3.2-1)
Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(1, 0)

}
Table 8.1.1.2.3.3-2A: SystemInformationBlockType1 (step 6, table 8.1.1.2.3.2-1)

systemInfoValueTag 1 Default value is 0
}
Table 8.1.1.2.3.3-3: SystemInformationBlockType2 (step 6, Table 8.1.1.2.3.2-1)

prach-ConfigIndex 5 FDD
prach-ConfigIndex 52 Set to index which TDD
denote subframe
numbers different
from the default
one.
}
}
}
}
FDD FDD cell environment
TDD TDD cell environment
ETSI
8.1.1.3 RRC / Paging for connection in idle mode / Multiple paging records
(1)
ensure that {
when { UE receives a Paging message including only unmatched identities }
then { UE does not establish any RRC connection }
}
(2)
ensure that {
when { UE receives a Paging message including any matched identity }
}
5.3.3.2, 5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.2.3]
Upon receiving the Paging message, the UE shall
1> If in RRC_IDLE, for each of the Paging records included in the Paging message:
2> If the ue-identity included in the pagingRecordList matches one of the UE identities allocated by upper
layers:
3> forward the ue-Identity, the cn-Domain and the pagingCause to the upper layers.
...
[TS 36.331, clause 5.3.3.2]
RRC_IDLE state.
...
1> If access to the cell, as specified above, is not barred:
2> apply the default configuration applicable for the antennaInformation as specified in 9.2.3, until explicitly
receiving a configuration;
perform system information acquisition upon re-selection.
...
[TS 36.331, clause 5.3.3.3]
1> set the IE ue-Identity as follows:
ETSI
2> else
3> draw a random value and set the ue-Identity to this value;
NOTE 1 Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.
1> Set the establishmentCause in accordance with the information received from upper layers;
[TS 36.331, clause 5.3.3.4]
NOTE: Prior to this, lower layers allocate a C-RNTI. For further details see TS 36.321 [6];
The UE shall:
1> establish SRB1 in accordance with the received radioResourceConfiguration and as specified in 5.3.10;
1> if stored, discard the Inter-frequency priority information and the Inter-RAT priority information provided via
dedicated signalling using the IE idleModeMobilityControlInfo;
1> stop timer T300;
1> enter RRC_CONNECTED state;
2> set the selectedPLMN-Identity to the PLMN selected by upper layers [TS 23.122, TS 24.008] from the
PLMN(s) included in the plmn-IdentityList broadcast, within SystemInformationBlockType1, in the cell
where the RRC connection was established;
2> if upper layers provide the ‘Registered MME’, set the registeredMME as follows:
3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers,
set the IE plmnIdentity to the value received from upper layers;
3> set the IEs mmegi and mmec to the value received from upper layers;
2> set the nas-DedicatedInformation to include the information received from upper layers;
procedure ends.
System Simulator:
- Cell 1
ETSI
UE:
None.
Preamble:

U-S Message
1 The SS transmits a Paging message including <-- Paging 1 -
only unmatched identities (incorrect S-TMSI).
RRCConnectionRequest message within 10s?
3 The SS transmits a Paging message including <-- Paging 2 -
two unmatched identities and a matched
identity.
message.
establishment.
6D establishment procedure in TS 36.508
subclause 4.5.3.3 are executed to successfully
complete the service request procedure.
7 Check: Does the test result of generic test - - 1,2 -
ETSI

pagingRecordList SEQUENCE (SIZE 3 entries
s-TMSI Set to the different value
UE
}
cn-Domain [1] ps
UE
}
cn-Domain [2] ps
UE
}
cn-Domain [3] ps
}
}

pagingRecordList SEQUENCE (SIZE 3 entries
UE
}
cn-Domain [1] ps
UE
}
cn-Domain [2] ps
s-TMSI Set to the value of the S-
TMSI of the UE
}
cn-Domain [3] ps
}
}
ETSI

}
}
}
8.1.1.4 RRC / Paging for connection in idle mode / Shared network environment
(1)
with { UE in E-UTRA RRC_IDLE state having been registered in the TA of the current cell which has
broadcasted a SystemInformationBlockType1 message including multiple PLMN identities }
ensure that {
when { UE receives a Paging message including an IE ue-Identity set to the S-TMSI which was
allocated to the UE at the UE registration procedure }
}
5.3.3.2, 5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.2.3]
3> forward the ue-Identity and the cn-Domain to the upper layers.
...
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
1> if access to the cell, as specified above, is not barred:
2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;
2> start timer T300
ETSI
...
[TS 36.331, clause 5.3.3.3]
2> else
[TS 36.331, clause 5.3.3.4]
The UE shall:
1> stop timer T300;
3> if the PLMN identity of the 'Registered MME' is different from the PLMN selected by the upper layers;
'Registered MME' received from upper layers;
ETSI
procedure ends.
System Simulator:
- Cell 1
UE:
None.
Preamble:

U-S Message
a matched identity.
3 The SS transmit an RRCConnectionSetup <-- RRCConnectionSetup - -
message.
including SERVICE REQUEST and an IE
selectedPLMN-Identity corresponding to the
PLMN on which the UE has been registered to
connection establishment?
ETSI
Table 8.1.1.4.3.3-1: SystemInformationBlockType1 (all steps, Table 8.1.1.4.3.2-1)

plmn-IdentityList SEQUENCE (SIZE (1..6)) OF 2 entries
SEQUENCE {
plmn-Identity[1] SEQUENCE {
mcc See Table 8.1.1.4.3.3-1A
mnc See Table 8.1.1.4.3.3-1A
}
cellReservedForOperatorUse[1] notReserved
plmn-Identity[2] SEQUENCE {
mcc See Table 8.1.1.4.3.3-1A
mnc See Table 8.1.1.4.3.3-1A
}
cellReservedForOperatorUse[2] notReserved
}
}
}
The PLMN Identity list broadcasted on the BCCH in Cell 1 shall be configured as defined in the table below.
Table 8.1.1.4.3.3-1A: PLMN Identity List broadcasted for Cell 1
Cell PLMN Identity (1) PLMN Identity (2)

MCC digits MNC digits MCC digits MNC digits
1 PLMN 1 PLMN 1 PLMN 2 PLMN 2
The definition of each PLMN code is found in table below.
PLMN MCC digit MNC digit

1 2 3 1 2 3
1 (NOTE 2) (NOTE 2)
2 (NOTE 3) 0 2 -
NOTE 1: “–“ (dash) denotes “not present”
NOTE 2: Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card
for PLMN 1.
NOTE 3: Set to the same Mobile Country Code stored in EFIMSI on the test USIM card for PLMN 2.

}
}
}
ETSI
Table 8.1.1.4.3.3-3: RRCConnectionSetupComplete (step 4, Table 8.1.1.4.3.2-1)

c1 CHOICE{
selectedPLMN-Identity Set to the PLMN selected
by upper layers
}
}
}
}
8.1.1.5 Void
8.1.1.6 RRC / BCCH modification in connected mode
with { the UE is in E-UTRA RRC_CONNECTED }
ensure that {
when { the UE receives a Paging message including the systemInfoModification }
then { the UE re-acquires the MasterInformationBlock, SystemInformationBlockType1 and
SystemInformationBlockType2 }
References: The conformance requirements covered in the present test case are specified in: TS 36.331 clauses 5.3.2.3,
5.2.2.3 and 5.2.2.4.
[TS 36.331, clause 5.3.2.3]
...
1> if the systemInfoModification is included:
2> re-acquire the required system information using the system information acquisition procedure as specified in
5.2.2.
...
[TS 36.331, clause 5.2.2.3]
The UE shall:
1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as
the 'required' system information:
...
2> if in RRC_CONNECTED:
3> the MasterInformationBlock, SystemInformationBlockType1 and SystemInformationBlockType2 as well as

SystemInformationBlockType8, depending on support of CDMA2000;
...
[TS 36.331, clause 5.2.2.4]
The UE shall:
1> apply the specified BCCH configuration defined in 9.1.1.1;
ETSI
1> if the procedure is triggered by a system information change notification:
2> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification
period following the one in which the change notification was received;
NOTE 1: The UE continues using the previously received system information until the new system information has
been acquired.
...
The UE may apply the received SIBs immediately, i.e. the UE does not need to delay using a SIB until all SI messages
have been received. The UE may delay applying the received SIBs until completing lower layer procedures associated
with a received or a UE originated RRC message, e.g. an ongoing random access procedure.
NOTE 2: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer
present, the UE should stop trying to acquire the particular SIB.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18], and using the condition
no_periodic_BSR_or_PHR.

U-S Message
1 The SS transmits a Paging message paging <-- Paging - -
occasion including a systemInfoModification.
2 From the beginning of the next modification - - - -
period the SS transmits a modified
SystemInformationBlockType2 as specified.
3 During the first on duration period after the end - - - -
of the modification period where
SystemInformationBlockType2 was modified
(see step 2), the SS transmits a PDCCH order
including a dedicated preamble.
4 Check: Does the UE initiate a random access - - 1 P
procedure using prach-ConfigIndex given in
step 2 (i.e. for FDD n subframe number 7 and
for TDD in subframe number 6)?
5 The SS transmits Random Access Response - - - -
with RAPID corresponding to preamble in
steps 3 and 4.
ETSI

c1 CHOICE {
rrcConnectionReconfiguration-r8 {
radioResourceConfigDedicated {
mac-MainConfig {
explicitValue {
drx-Config Not present
}
}
}
}
}
}
}
Table 8.1.1.6.3.3-2: SystemInformationBlockType1 (step 2, table 8.1.1.6.3.2-1)

systemInfoValueTag 1 Default value is 0
}
Table 8.1.1.6.3.3-3: SystemInformationBlockType2 (step 2, table 8.1.1.6.3.2-1)

prach-ConfigIndex 5 The default is 3 FDD
prach-ConfigIndex 52 The default is 51 TDD
}
}
}
}
8.1.1.7 RRC / Paging for connection in idle mode

(1)
with { UE in E-UTRA RRC_IDLE state and configured for “Extended Access Barring” }
ensure that {
when { when EAB is being broadcast by the network and UE receives a Paging message including an
ue-Identity set to the S-TMSI which was allocated to the UE at the UE registration procedure }
}
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause D.1, TS
36.331, clause 5.3.2.3, 5.3.3.2, 5.3.3.3 and 5.3.3.4.
[TS 24.301, clause D.1]
ETSI
When EMM requests the establishment of a NAS-signalling connection, the RRC establishment cause used by the UE
shall be selected according to the NAS procedure as specified in table D.1.1. The EMM shall also indicate to the lower
layer for the purpose of access control, the call type associated with the RRC establishment cause as specified in
table D.1.1. If the UE is configured for EAB (see the "ExtendedAccessBarring" leaf of NAS configuration MO in
3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17]), the EMM shall indicate to the lower layer for the purpose of access
control that EAB applies for this request except for the following cases:
- the UE is accessing the network with one of the access classes 11 – 15;
- the UE is answering to paging;
- the RRC Establishment cause is set to "Emergency call"; or
- the UE is configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of the NAS
configuration MO as specified in 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17]) and receives an indication
from the upper layers to override EAB.
[TS 36.331, clause 5.3.2.3]
3> forward the ue-Identity, and the cn-Domain to the upper layers.
...
1> if in RRC_IDLE, the eab-ParamModification is included and the UE is EAB capable:
2> consider previously stored SystemInformationBlockType14 as invalid;
2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information
modification period boundary as specified in 5.2.1.6;
2> re-acquire SystemInformationBlockType14 using the system information acquisition procedure as specified in
5.2.2.4;
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
1>if access to the cell, as specified above, is not barred:
2> apply the timeAlignmentTimerCommon included in SystemInfoBlockType2;
ETSI
...
[TS 36.331, clause 5.3.3.3]
2> else:
NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.
[TS 36.331, clause 5.3.3.4]
The UE shall:
1> stop timer T300;
ETSI
procedure ends.
System Simulator:
- Cell 1.
- System information combination 21 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
- The UE is configured for “Extended Access Barring”
- The UE belong to access class 0
The UE is equipped with a USIM containing values shown in Table8.1.1.7.3–1.
Table 8.1.1.7.3-1: USIM Configuration
USIM field Value

EFUST Service 96 is supported.
EFNASCONFIG “ExtendedAccessBarring is set to 1 which
indicate the extended access barring is
applied for the UE” as defined in TS 24.368,
clause 5.6.
Preamble:

U-S Message
1 Wait for 15s for the UE to receive system - - - -
information.
a matched identity.
message.
establishment?
6-9 Steps 6 to 9 of the generic radio bearer - - - -
establishment procedure (TS 36.508 4.5.3.3-1)
ETSI
Table 8.1.1.7.3.3-1: SystemInformationBlockType14 (all steps in table 8.1.1.7.3.2-1)
Derivation path: 36.508 Table Table 4.4.3.3-13A

SystemInformationBlockType14-r11 ::= SEQUENCE {
eab-Common-r11 ::= SEQUENCE {
eab-Config-r11 ::= SEQUENCE {
eab-Category-r11 ‘a’ All UEs
eab-BarringBitmap-r11 ‘1000000000’ EAB active for
access class 0
}
}
}

}
}
}
8.1.2 RRC connection establishment

8.1.2.1 RRC connection establishment / Ks=1.25/ Success
(1)
with {UE in E-UTRA RRC_IDLE state}
ensure that {
when { UE is requested to make an outgoing call }
then { UE establishes an RRC Connection }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.3.2,
5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.3.2]
The UE initiates the procedure when upper layers request establishment of a signalling connection while the UE is in
RRC_IDLE state.
...
ETSI
NOTE 2 Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up
...
[TS 36.331, clause 5.3.3.3]
2> else
...
[TS 36.331, clause 5.3.3.4]
...
The UE shall:
1> perform the radio resource configuration procedure in accordance with the received radioResourceConfiguration
and as specified in 5.3.10;
1> stop timer T300;
1> set the contents of RRCConnectionSetupComplete message as follows:
from the PLMNs included in the plmn-IdentityList in SystemInformationBlockType1;
ETSI
3> set the mmegi and mmec to the value received from upper layers;
2> set the nas-DedicatedInformation to include the information received from upper layers;
procedure ends.
System Simulator:
- Cell 1
UE:
None.
Preamble:

U-S Message
1 SS sends a Paging message to the UE on the <-- Paging - -
identity in one entry of the IE
pagingRecordLists.
2 Check: does the UE transmit an --> RRCConnectionRequest 1 P
3 The SS transmit an RRCConnectionSetup RRCConnectionSetup - -
<--
message with SRB1 configuration (Note 1).
RRCConnectionSetupComplete including
SERVICE REQUEST message to confirm the
establishment?
Note 1: Contains a SERVICE REQUEST NAS message.
ETSI
Table 8.1.2.1.3.3-1: RRCConnectionSetup-DeltaMCS (step 3, Table 8.1.2.1.3-1)

RRCConnectionSetup-DeltaMCS ::= SEQUENCE {
c1 CHOICE {
rrcConnectionSetup-r8 SEQUENCE {
dicated-SRB1-DeltaMCS
}
}
}
}
Table 8.1.2.1.3.3-2: RadioResourceConfigDedicated-SRB1-DeltaMCS (Table 8.1.2.1.3.3-1)
Derivation Path: 36.508, Table 4.6.3-15,

RadioResourceConfigDedicated-SRB1-DeltaMCS ::=
SEQUENCE {
physicalConfigDedicated PhysicalConfigDedicated
--DeltaMCS using
condition SRB1
}
Table 8.1.2.1.3.3-3: PhysicalConfigDedicated—DeltaMCS (Table 8.1.2.1.3.3-2)
Derivation Path: 36.508, Table 4.8.2.1.6-1

PhysicalConfigDedicated--DeltaMCS ::= SEQUENCE
{
uplinkPowerControlDedicated UplinkPowerControlDedic SRB1
ated--DeltaMCS
}
Table 8.1.2.1.3.3-4: UplinkPowerControlDedicated--DeltaMCS (Table 8.1.2.1.3.3-3)

UplinkPowerControlDedicated--DeltaMCS ::=
SEQUENCE {
deltaMCS-Enabled en1 Corresponds to
Ks value 1.25
corresponding to
“enabled”.
}
8.1.2.2 RRC connection establishment / Reject with wait time

(1)
with { UE in E-UTRA RRC_IDLE state and has sent an RRCConnectionRequest message }
ensure that {
when { UE receives an RRCConnectionReject message including an IE waitTime set to non-zero value }
then { UE doesn't re-send RRCConnectionRequest before the waitTime is expired}
}
ETSI
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.3.2,
5.3.3.3 and 5.3.3.8.
[TS 36.331, clause 5.3.3.2]
1> if the UE is establishing the RRC connection for mobile terminating calls:
2> if timer T302 is running:

3> consider access to the cell as barred;
2> else:
3> consider access to the cell as not barred;
1> else if the UE is establishing the RRC connection for emergency calls:
...
1> else if the UE is establishing the RRC connection for mobile originating calls:
2> if timer T302 or T303 is running:
...
...
[TS 36.331, clause 5.3.3.3]
2> else
ETSI
...
[TS 36.331, clause 5.3.3.8]
The UE shall:
1> stop timer T300;
1> reset MAC and release the MAC configuration;
1> start timer T302, with the timer value set to the waitTime;
1> inform upper layers about the failure to establish the RRC connection and that access barring for mobile
originating calls, mobile originating signalling and mobile terminating access is applicable, upon which the
procedure ends.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 (serving
cell) according to [18].
ETSI

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

U-S Message
RRCConnectionRequest message within 10s.
Table 8.1.2.2.3.3-1: RRCConnectionReject (step 3, table 8.1.2.2.3.2-1)

RRCConnectionReject ::= SEQUENCE {
c1 CHOICE {
rrcConnectionReject-r8 SEQUENCE {
waitTime 10 10 seconds
}
}
}
}
Table 8.1.2.2.3.3-2: CLOSE UE TEST LOOP (preamble, Table 8.1.2.2.3.2-1)
Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B

UE test loop mode B LB setup
IP PDU delay '0000 0101'B 5 seconds
8.1.2.3 RRC connection establishment / Return to idle state after T300 timeout
(1)
with {UE in E-UTRA RRC_IDLE state having sent an RRCConnectionRequest message}
ensure that {
when { the SS does not answer to the UE during T300}
then {UE goes to RRC_IDLE}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.3.6.
[TS 36.331, clause 5.3.3.6]
The UE shall:
1> if timer T300 expires
2> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;
2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends.
System Simulator:
- Cell 1
ETSI
UE:
None.
Preamble:

U-S Message
0A SS is configured not to transmit MAC control - - - -
element with matched UE Contention
Resolution Identity
pagingRecordLists.
2 TheUEtransmitsanRRCConnectionRequestme --> RRCConnectionRequest - -
ssage.
3 The SS waits for 2s. --> RRCConnectionRequest - -
Note: the UE may transmit one or more
RRCConnectionRequest messages but the SS
does not answer to these messages.
3A SS is configured to transmit MAC control - - - -
element with matched UE Contention
Resolution Identity
state on Cell 1?
Table 8.1.2.3.3.3-1: RRCConnectionRequest (step 2 and step 3, Table 8.1.2.3.3.2-1)

}
}
}
8.1.2.4 Void
8.1.2.5 RRC connection establishment / 0% access probability for MO calls, no
restriction for MO signalling
(1)
with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating 0%
access probability for MO calls }
ensure that {
when { UE has user data pending }
then { UE does not transmit any RRCConnectionRequest message }
}
ETSI
(2)
ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts a
SystemInformationBlockType2 indicating no restriction for MO signalling }
then { UE transmits an RRCConnectionRequest message }
}
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
...
2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:
3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which
is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and
3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in
ac-BarringForMO-Data is set to zero:
3> else:
4> draw a random number 'rand' uniformly distributed in the range: 0 ≤ rand < 1;
4> if 'rand' is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Data:
4> else:
2> else:
1> else (the UE is establishing the RRC connection for mobile originating signalling):
2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is

present:
ETSI
ac-BarringForMO-Signalling is set to zero:
3> else:
4> if 'rand' is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-
Signalling:
4> else:
2> else:
1> else:
2> if the UE is establishing the RRC connection for mobile originating calls and if both timers T302 and T303
are not running:
3> draw a random number 'rand' that is uniformly distributed in the range 0 ≤ rand < 1;
3> start timer T303 with the timer value calculated as follows, using the ac-BarringTime included in ac-
BarringForMO-Data:
T303= (0.7+ 0.6 * rand) * ac-BarringTime
originating calls is applicable, upon which the procedure ends;
...
ETSI
System Simulator:
- Cell 1 and Cell 11 (HPLMN in different TA).
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 (serving
cell) according to [18].

Cell-specific RS dBm/15
T1 -85 -79 assigned to satisfy RCell 1 < RCell
EPRE kHz
11.
ETSI

U-S Message
1 Void - - - -
2 Void - - - -
2A The SS transmits an RRCConnectionRelease <-- RRCConnectionRelease - -
message on Cell 1.
2B Wait for 5 s for the UE to enter E-UTRA - - - -
RRC_IDLE state.
3A Check: Does the UE transmit an --> RRCConnectionRequest 2 P
3B- Steps 2 to 6 of the generic test procedure in - - - -
3F TS 36.508 [18] subclause 6.4.2.7 are
Note: The UE performs a TAU procedure and
4-9 Void - - - -
10 Wait for 5 s for the UE to enter E-UTRA - - - -
RRC_IDLE state.
A subclause 4.5.3.3 is performed on Cell 11.
B the DRB associated with the default EPS
10 Wait for 1 s after the IP packet has been - - - -
C transmitted in step 10B. (Note 1)
11- Void - - - -
13
message on Cell 11.
within 30s?
16 Void - - - -
- EXCEPTION: Step 26 and Step 27a1 can - - - -
happen in any order
17 - Check: Does the test result of steps 1 to 10 - - 1,2 -
6.4.2.2 indicate that the UE is in E-UTRA
RRC_IDLE state on Cell 11?
- EXCEPTION: Step 27a1 describes behaviour - - - -
that depends on UE implementation; the
that takes place if the UE has user data
pending.
27a IF the UE has user data pending THEN the UE - - - -
1 loop backs the IP packet received in step 10C
on the DRB associated with the default EPS
bearer context on Cell 11 within 10s.
Note 1: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted
by the SS in step 10B to the UE test loop function before the RRCConnectionRelease message is sent by
the SS in step 14.
ETSI
8.1.2.5.3.2-2)

ac-BarringInfo SEQUENCE {
ac-BarringForEmergency FALSE
ac-BarringForMO-Signalling Not present
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor p00
ac-BarringTime s512
ac-BarringForSpecialAC '11111'B
}
}
}
Table 8.1.2.5.3.3-1A: CLOSE UE TEST LOOP (preamble, Table 8.1.2.5.3.2-2)

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

establishmentCause mo-Signalling
}
}
}
8.1.2.6 RRC connection establishment / Non-zero percent access probability for MO

calls, no restriction for MO signalling
(1)
with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating non zero
percent access probability for MO calls }
ensure that {
then { UE does not transmit any RRCConnectionRequest message or UE transmits an
RRCConnectionRequest message }
}
(2)
ensure that {
SystemInformationBlockType2 indicating no restriction for MO signalling }
}
ETSI
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
...

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

present:
3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15,
which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and
3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained
in ac-BarringForMO-Data is set to zero:
3> else:
4> else:
2> else:


present:
...
2> else:
ETSI
1> else:
are not running:
BarringForMO-Data:
2> else if the UE is establishing the RRC connection for mobile originating signalling and if both timers T302
and T305 are not running:
BarringForMO-Signalling:
originating signalling is applicable, upon which the procedure ends;
System Simulator:
UE:
None.
Preamble:
- UE is in state Generic RB Established, UE Test Mode Activated (state 3A) on Cell 1 according to [18].

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

U-S Message
1 The SS initializes an internal counter K to 0 - - - -
and L to 0.
2 Void - - - -
- EXCEPTION: Step 2Aa1 to 3b9 shall be - - - -
repeated maximum 50 times unless K > 0 and
L >0. (Note 1)
- EXCEPTION: Step 2Aa1 describes behaviour - - - -
that depends on the internal counters.
2Aa1 IF K>0 or L>0 THEN The SS opens the UE - - - -
test loop mode.
2B The SS closes the UE test loop mode. - - - -
2C The SS transmits one IP packet to the UE on - - - -
2D Wait for 1 s after the IP packet has been - - - -
transmitted in step 2C.
2E SS transmits an RRCConnectionRelease <-- RRCConnectionRelease - -
message to release the RRC connection.
2F Wait for 5 s for the UE to enter E-UTRA - - - -
RRC_IDLE state.
behaviours which vary depending on whether
the UE transmits an RRCConnectionRequest
message or not.
3a1 IF the UE does not transmit any - - - -
RRCConnectionRequest message within 5s
(Note 3) THEN the SS increments the counter
K by 1.
- EXCEPTION: Steps 3a9 to 3a10 can occur in - - - -
any order
3a2- Steps 2 to 9 of the generic radio bearer - - - -
3a9 establishment procedure (TS 36.508 4.5.3.3-1)
are executed (Note 2).
that depends on UE implementation; step 3a10
takes place if the UE has user data pending.
3a10 IF the UE has user data pending THEN the UE - - - -
loop backs the IP packet received in step 2D
bearer context on Cell 1 within 10 s.
3b1 ELSE IF the UE transmits an --> RRCConnectionRequest - -
THEN the SS increments the counter L by 1.
3b2 Void - - - -
- EXCEPTION: Steps 3b8 to 3b9 can occur in - - - -
any order
3b3- Steps 4 to 9 of the generic radio bearer - - - -
3b8 establishment procedure (TS 36.508 4.5.3.3-1)
are executed.
3b9 The UE loop backs the IP packet received in - - - -
step 4 on the DRB associated with the default
3b10 Void - - - -
-
3b14
4 Check: Is the counter K > 0 and L > 0? - - 1 P
4A The SS transmits an RRCConnectionRelease <-- RRCConnectionRelease - -
message on Cell 1.
4B Wait for 5 s for the UE to enter E-UTRA - - - -
RRC_IDLE state.
ETSI

Cell 11.
state on Cell 11?
Note 1: There is an extremely low probability that the UE originating calls are barred, or not barred, 50 times
-15
consecutively. (The probability is 1.78×10 ). Therefore, 50 times is enough number of trials for this test
case.
Note 2: After UE enters RRC_CONNECTED T303 is stopped.
Note 3: The UE starts T303.
Table 8.1.2.6.3.2-2)

ac-BarringForMO-Signalling Not present
ac-BarringTime s64
ac-BarringForSpecialAC ‘00000’B
}
}
}
Table 8.1.2.6.3.3-2: RRCConnectionRequest (step 3b1, Table 8.1.2.6.3.2-2)

establishmentCause mo-Data
}
}
}
Table 8.1.2.6.3.3-3: Void

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

8.1.2.7 RRC connection establishment / 0% access probability for AC 0 to 9, AC 10

is barred, AC 11 to 15 are not barred, access for UE with access class in the
range 11 to 15 is allowed
(1)
with { UE in E-UTRA RRC_IDLE state having an Access Class with a value in the range 11..15 and
having received a SystemInformationBlockType2 indicating 0% access probability for AC 0..9 for both
MO call and MO signalling, access restriction for AC 10 and no restriction for AC 11..15 for both MO
call and MO signalling }
ensure that {
}
(2)
with { UE in E-UTRA RRC_IDLE state having an Access Class with a value in the range 11..15 }
ensure that {
SystemInformationBlockType2 indicating 0% access probability for AC 0..9 for both MO call and MO
signalling, access restriction for AC 10 and no restriction for AC 11..15 for both MO call and MO
signalling }
}
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
2> else:
...
...
2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:
ETSI
ac-BarringForMO-Data is set to zero:
3> else:
...
...

present:
3> else:
...
...
System Simulator:
- Cell 1 and Cell 11 (HPLMN in different TA).
UE:
- USIM set to Type C in 34.108[5] subclause 8.3.2.15 is inserted.
ETSI
Preamble:
- The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 according
to [18].

T0 -85 -91 assigned to satisfy SrxlevCell 1 >
EPRE kHz
SrxlevCell 11.
T1 -85 -79 assigned to satisfy RCell 1 < RCell
EPRE kHz
11.
ETSI

U-S Message
0A Wait for 1 s after the IP packet has been - - - -
message on Cell 1.
message on Cell 1.
Cell 1.
message.
message on Cell 1.
message on Cell 1.
Cell 1.
- EXCEPTION: Step 3E and 3EA can occur in - - - -
any order
message on Cell 1.
3E The UE loop backs the IP packet received in - - - -
A step 0 on the DRB associated with the default
message on Cell 1.
RRC_IDLE state.
4A Check: Does the test result of generic test - - 2 -
Cell 11 and that the UE has performed TAU
procedure with establishment cause ‘high
priority access’?
5- Void - - - -
10
RRC_IDLE state.
12- Void - - - -
20
state on Cell 11 and that the UE responds to
paging with establishment cause ‘high priority
access’?
Note 1: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by
the SS in step 0 to the UE test loop function before the RRCConnectionRelease message is sent by the SS
in step 1.
ETSI
Table 8.1.2.7.3.3-1: SystemInformationBlockType2 for Cell 1 and Cell 11 (preamble, Table 8.1.2.7.3.2-
2)

ac-BarringForEmergency TRUE
ac-BarringForMO-Signalling SEQUENCE {
ac-BarringTime s4
}
ac-BarringTime s4
}
}
}
Table 8.1.2.7.3.3-1A: CLOSE UE TEST LOOP (preamble, Table 8.1.2.7.3.2-2)

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

}
}
}
Table 8.1.2.7.3.3-3: Void
Table 8.1.2.7.3.3-4: Void
Table 8.1.2.7.3.3-5: Void
Table 8.1.2.7.3.3-6: Void
Table 8.1.2.7.3.3-7: Void
Table 8.1.2.7.3.3-8: RRCConnectionReconfiguration (step 3D, Table 8.1.2.7.3.2-2)
Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(1, 0)
8.1.2.8 RRC connection establishment / Range of access baring time

(1)
with { UE in E-UTRA RRC_IDLE state with T303 running }
ETSI
ensure that {
}
(2)
with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 with no restriction }
ensure that {
}
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.

2> else:
2> if SystemInformationBlockType2 includes the ac-BarringInfo:
3> if the ac-BarringForEmergency is set to FALSE:
3> else if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15,
which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11]:
NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the
HPLMN/ EHPLMN.
4> if the ac-BarringInfo includes ac-BarringForMO-Data, and for all of the valid Access Classes for the
UE, the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set
to one:
4> else:
3> else:
2> else:

ETSI

present:
3> else:
4> else:
2> else:


present:
3> else:
Signalling:
4> else:
2> else:
ETSI
1> else:
are not running:
BarringForMO-Data:
3> inform upper layers about the failure to establish the RRC connection and that access barring for
emergency calls is applicable, upon which the procedure ends;
2> else:
3> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends;
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in Registered, Idle mode state (state 2) according to [18].
ETSI

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

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

ac-BarringForEmergency FALSE For AC 10
ac-BarringTime s16
}
ac-BarringTime s16
ac-BarringForSpecialAC '11111'B For AC 11..15
}
}
}
8.1.2.9 RRC Connection Establishment / 0% access probability for MO calls, non-

zero percent access probability for MO signalling
(1)
ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts
SystemInformationBlockType2 indicating non zero percent access probability for MO signalling }
then { UE does not transmit any RRCConnectionRequest message when access to the cell is
considered as barred and UE transmits an RRCConnectionRequest message when access to the cell is
considered as not barred }
}
(2)
with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 indicating 0% access
probability for MO call }
ensure that {
}
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
ETSI
...
...


present:
3> else:
4> else:
2> else:


present:
3> else:
Signalling:
4> else:
ETSI
2> else:
1> else:
are not running:
...
System Simulator:
UE:
None.
Preamble:
to [18].
ETSI

T1 -85 -79
T2 -85 -91
EPRE kHz assigned to satisfy RCell 1 > RCell 11.
ETSI

U-S Message
message on Cell 1.
RRC_IDLE state.
3 The SS initializes internal counters: K to 0 and - - - -
L to 0.
- EXCEPTION: Steps 4 to 5b15 shall be - - - -
repeated maximum 50 times unless K > 0 and
L >0. (Note 1)
behaviours which vary depending on whether
the UE transmits an RRCConnectionRequest
message or not.
5a1 IF the UE does not transmit any - - - -
RRCConnectionRequest message within 34 s
when K=0 and L=0 and within 8 s for other
≠ ≠
repeat times, i.e. K 0 or L 0 (Note 2) THEN
the SS increments the counter K by 1.
5a2 The SS changes the power level setting - - - -
5a3 The SS waits for 20s for the UE to perform cell - - - -
reselection procedure. (Note 3)
5b1 ELSE IF the UE transmits an --> RRCConnectionRequest - -
THEN the SS increments the counter L by 1.
5b2- Steps 2 to 6 of the generic test procedure in - - - -
5b6 TS 36.508 [18] subclause 6.4.2.7 are
5b7 Wait for 5 s for the UE to enter E-UTRA - - - -
RRC_IDLE state.
5b8 The SS changes the power level setting - - - -
5b9 The UE transmits an RRCConnectionRequest --> RRCConnectionRequest - -
message on Cell 1.
5b10 Steps 2 to 6 of the generic test procedure in - - - -
- TS 36.508 [18] subclause 6.4.2.7 are
5b14 performed on Cell 1.
5b15 Wait for 5 s for the UE to enter E-UTRA - - - -
RRC_IDLE state.
6 Check: Is the counter K > 0 and L > 0? - - 1 P
message on Cell 1.
within 30s?
ETSI
12- Check: Does the test result of steps 1 to 10 - - 1,2 -

pending.
loop backs the IP packet received in step 8 on
Note 1: There is an extremely low probability that the UE originating calls are barred, or not barred, 50 times
-15
consecutively. (The probability is 1.78×10 ). Therefore, 50 times is enough number of trials for this test
case.
Note 3: The UE stops T305 upon cell reselection.
in step 10.
8.1.2.9.3.2-2)

ac-BarringForMO-Signalling SEQUENCE {} Not present
ac-BarringTime s512
}
}
}
8.1.2.9.3.2-2)

ac-BarringTime s64
}
ac-BarringForMO-Data SEQUENCE {} Not present
}
}
ETSI

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

}
}
}
8.1.2.10 Void
8.1.2.11 RRC connection establishment of emergency call
(1)
ensure that {
when { UE is requested to make an outgoing emergency call }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.331 clause 5.3.3.2.
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
…
…
2> else:
ETSI
[TS 36.331, clause 5.3.3.3]
System Simulator:
- Cell 1
UE:
None.
Preamble:

U-S Message
1 Make the UE attempt an IMS emergency call - - - -
3- Steps 3 to 15 of the generic test procedure for - - - -
15 IMS Emergency call establishment in EUTRA:
Normal Service (TS 36.508 4.5A.4.4-1).
Table 8.1.2.11.3.2-2: Void

establishmentCause emergency
}
}
}
ETSI
8.1.2.12 RRC connection establishment of emergency call / Limited Service

(1)
ensure that {
when { UE camp on an acceptable cell and is requested to make an outgoing emergency call }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.304 clause 4.3, 5.2.3.1
and TS 36.331 clause 5.3.3.2.
[TS 36.304, clause 4.3]
This clause defines the level of service that may be provided by the network to a UE in Idle mode.
The action of camping on a cell is necessary to get access to some services. Three levels of services are defined for UE:
- Limited service (emergency calls, ETWS and CMAS on an acceptable cell)
- Normal service (for public use on a suitable cell)
- Operator service (for operators only on a reserved cell)
Furthermore, the cells are categorised according to which services they offer:
acceptable cell:
An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls and
receive ETWS and CMAS notifications). Such a cell shall fulfil the following requirements, which is the minimum set
of requirements to initiate an emergency call and to receive ETWS and CMAS notification in a E-UTRAN network:
suitable cell:
A "suitable cell" is a cell on which the UE may camp on to obtain normal service. The UE shall have a valid USIM and
such a cell shall fulfil all the following requirements.
- The cell is part of at least one TA that is not part of the list of "forbidden tracking areas for roaming", which
- For a CSG cell, the CSG ID is part of the CSG whitelist of the UE.
ETSI
[TS 36.304, clause 5.2.3.1]
This procedure requires no prior knowledge of which RF channels are E-UTRA carriers. The UE shall scan
all RF channels in the E-UTRA bands according to its capabilities to find a suitable cell. On each carrier
frequency, the UE need only search for the strongest cell. Once a suitable cell is found this cell shall be
selected.
b) Stored Information Cell Selection
This procedure requires stored information of carrier frequencies and optionally also information on cell
parameters, from previously received measurement control information elements or from previously detected
cells. Once the UE has found a suitable cell the UE shall select it. If no suitable cell is found the Initial Cell
Selection procedure shall be started.
NOTE: Priorities between different frequencies or RATs provided to the UE by system information or dedicated
signalling are not used in the cell selection process.
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
…
…
2> else:
[TS 36.331, clause 5.3.3.3]
[TS 36.331, clause 6.2.2]
ETSI

…
ims-EmergencySupport
Indicates whether the cell supports IMS emergency bearer services for UEs in limited service mode. If absent, IMS
emergency call is not supported by the network in the cell for UEs in limited service mode.
System Simulator:
- Cell 1
- The PLMN is defined in Table 8.1.2.12.3.1-1.
Table 8.1.2.12.3.1–1: PLMN identifier
Cell PLMN name

1 PLMN4
UE:
- The UE is equipped with a USIM containing default values except for those listed in Table 8.1.2.12.3.1-2.

EFFPLMN PLMN4
EFPLMNwAcT 1 Default E-UTRAN
Preamble:
- The UE is Switched OFF (State 1) according to [18].

U-S Message
2 Wait 60s for the UE to camp on Cell 1 as an - - - -
acceptable cell.
3 Make the UE attempt an IMS emergency call - - - -
5- Steps 3 to 19 of the generic test procedure for - - - -
21 IMS Emergency call establishment in EUTRA:
Limited Service (TS 36.508 4.5A.5.3-1).
ETSI
Table 8.1.2.12.3.2-2: Void

establishmentCause emergency
}
}
}
Table 8.1.2.12.3.3-2: Void
8.1.2.13 RRC connection establishment / 0% access probability for MO calls, 0%

access probability for MO signalling
(1)
ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts
SystemInformationBlockType2 indicating 0% access probability for MO signalling }
}
(2)
probability for MO call and for MO signalling }
ensure that {
when { UE receives a Paging message }
}
(3)
probability for MO call }
ensure that {
}
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
...
ETSI


present:
3> else:
4> else:
2> else:


present:
3> else:
Signalling:
4> else:
2> else:
ETSI
NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up to
date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to perform
system information acquisition upon cell re-selection.
1> else:
are not running:
...
System Simulator:
UE:
None.
Preamble:
to [18].

T1 -85 -79
T2 -85 -91
EPRE kHz assigned to satisfy RCell 1 > RCell 11.
ETSI

U-S Message
message on Cell 1.
RRC_IDLE state.
1.
within 40s? (Note 1)
a matched identity allocated in Cell 1.
within 30s? (Note 2)
7 The SS changes the - - - -
SystemInformationBlockType2 on Cell 1
according to Table 8.1.2.13.3.3-1.
7A Wait for 2.1* modification period (Note 5) to - - - -
effect.
7B The SS changes the power level setting - - - -
1.
8 The SS waits for 40s the UE to perform cell - - - -
reselection procedure (Note 3).
9 The SS sends a Paging message to the UE on <-- Paging - -
pagingRecordLists on Cell 1.
Cell 1.
message on Cell 1.
within 10s?
21- Check: Does the test result of steps 1 to 10 - - 1,2, -
30 generic test procedure in TS 36.508 subclause 3
pending.
loop backs the IP packet received in step 17
ETSI

Note 2: In case that the UE did not response to paging on Cell 1, it is considered that the UE is camped on Cell 11.
Note 3: The UE stops T305 upon cell reselection.
in step 19.
Note 5: The wait time of 2.1* modification period in step 7A is to allow for the network to paging the system
information change during the next modification period, and update the system information at the subsequent
modification period. UE should acquire the updated system information within 100ms of the start of
modification period.

ac-BarringFactor p0
ac-BarringTime s8
}
ac-BarringFactor p0
ac-BarringTime s512
}
}
}

}
8.1.2.13.3.2-2)

ac-BarringFactor p0
ac-BarringTime s512
}
ac-BarringForMO-Data SEQUENCE {} Not present
}
}
ETSI

8.1.2.14 RRC connection establishment / High speed flag

(1)
with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating an IE
highSpeedFlag set to true }
ensure that {
when { UE receives a Paging message }
}
6.3.2.
[TS 36.331, clause 5.2.2.9]
Upon receiving SystemInformationBlockType2, the UE shall:
...
1> apply the configuration included in the radioResourceConfigCommon;
[TS 36.331, clause 6.3.2]
PRACH-Config field descriptions

…
highSpeedFlag
Parameter: High-speed-flag, see TS 36.211, [21, 5.7.2].TRUE corresponds to Restricted set and FALSE to
Unrestricted set.
System Simulator:
UE:
None.
Preamble:
Table 8.1.2.14.3.2-1 illustrates the downlink power levels to be applied for the cells at various time instants of the test
execution. The configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table
8.1.2.14.3.2-2.
ETSI

T1 -85 -79

U-S Message
1 The SS changes Cell 2 level according to the - - - -
row “T1” in table 8.1.2.14.3.2-1.
2 The SS waits for 40s for the UE to perform cell - - - -
reselection procedure.
3 The SS transmits a Paging message on Cell 2. <-- Paging - -
5-10 Steps 4 to 9 of the generic radio bearer - - - -
establishment procedure (TS 36.508 4.5.3.3-1)
service request procedure on Cell 2.
8.1.2.14.3.2-2)

rootSequenceIndex 86
highSpeedFlag true
}
}
}
}
8.1.3 RRC connection release

8.1.3.1 RRC connection release / Success
(1)
with { UE in RRC_CONNECTED state}
ensure that {
when { UE receives an RRCConnectionRelease message }
then { UE releases the signalling connection, the established EPS bearer and all radio resources
and enters in RRC_IDLE state }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.8.3
and 5.3.12.
[TS 36.331, clause 5.3.8.3]
ETSI
The UE shall:
1> delay the following actions defined in this sub-clause 60ms from the moment the RRCConnectionRelease
...
1> if the releaseCause received in the RRCConnectionRelease message indicates ‘loadBalancingTAURequired’:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘load
balancing TAU required’;
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
1> reset MAC;
1> stop all timers that are running except T320;
1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP
entity for all established RBs;
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the
case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18].

U-S Message
1 SS transmits an RRCConnectionRelease <-- RRCConnectionRelease - -
message to release the RRC connection.
2 SS waits for 5s. - - - -
state on Cell 1?
ETSI
None.
8.1.3.2 Void
8.1.3.3 Void
8.1.3.4 RRC connection release / Redirection to another E-UTRAN frequency
(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with
eutra different from the frequency UE was on in RRC_CONNECTED state}
then { UE enters RRC_IDLE state on new frequency included in IE redirectedCarrierInfo }
}
5.3.12 and TS 36.304, clauses 5.2.4.1, 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
1> else:
[TS 36.331, clause 5.3.12]
[TS 36.304, clause 5.2.4.1]
ETSI
UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given
in system information and for which the UE has a priority provided.
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to
redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on
an EUTRA carrier. If no suitable cell is found, the UE shall perform a cell selection starting with Stored Information
Cell Selection procedure in order to find a suitable cell to camp on.
...
System Simulator:
- 2 cells on different E-UTRA frequencies and different tracking areas:
- Cell 1 serving cell
- Cell 23 suitable neighbour inter-frequency cell
- Cell power levels are selected according to [18] so that camping on Cell 1 is guaranteed
UE:
None.
Preamble:

U-S Message
eutra of Cell 23).
Cell 23?
Table 8.1.3.4.3.3-1: Conditions for table 8.1.3.4.3.3-3
Cell 1
Cell 23
ETSI
Table 8.1.3.4.3.3-2: Void
8.1.3.4.3.2-1)

as used for Cell 23
as used for Cell 1
cellReselectionPriority[n] Not present
}
}
Table 8.1.3.4.3.3-4: RRCConnectionRelease message (step 1, Table 8.1.3.4.3.2-1)

c1 CHOICE {
23
}
}
}
}
}
8.1.3.5 RRC connection release / Success / With priority information

(1)
with { UE in E-UTRA RRC_IDLE state having received an RRCConnectionRelease message with the
freqPriorityListEUTRA with higher priority frequency}
ensure that {
}
TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5.
[TS 36.331, clause 5.3.8.3]
The UE shall:
ETSI
1> else:
...
1> else:
[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.2]
ETSI
priority.

[TS 36.304, clause 5.2.4.5]

- A cell of a higher priority EUTRAN or UTRAN RAT/ frequency fulfils Squal > ThreshX, HighQ during a time
interval TreselectionRAT; or
- A cell of a higher priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time
interval TreselectionRAT; and
and
More than 1 second has elapsed since the UE camped on the current serving cell.

- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority EUTRAN or UTRAN RAT/
- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority GERAN or CDMA2000 RAT/
frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
ETSI
System Simulator:
- Cell 1, Cell 3 and Cell6.
NOTE: For Cell 3 and 6 TAI is set to TAI-2
UE:
None.
Preamble:

dBm/ The power level values are
Cell-specific RS
T0 15kH -85 "off” "off” assigned to satisfy SrxlevCell 1 >
EPRE
z Sintrasearch. (NOTE 1)
dBm/
Cell-specific RS assigned to satisfy both
T1 15kH -85 -73 -73
EPRE Threshx, low < SrxlevCell 3 and
z
Threshx, high <SrxlevCell 6.

U-S Message
message including the freqPriorityListEUTRA
on Cell 1.
RRC_IDLE state on Cell 1.
3 The SS changes Cell 1, Cell 3 and Cell 6 level - - - -
4 Void - - - -
Cell 6?
ETSI

c1 CHOICE {
freqPriorityListEUTRA SEQUENCE (SIZE 3 entries
as used for Cell 1
as used for Cell 3
as used for Cell 6
}
freqPriorityListUTRA-FDD Not present
freqPriorityListUTRA-TDD Not present
t320 Not present
}
}
}
}
}
8.1.3.5.3.2-2)

dl-CarrierFreq[n] Same downlink EARFCN
as used for Cell 3
dl-CarrierFreq[m] Same downlink EARFCN
as used for Cell 6
threshX-Low[n] 11
threshX-High[m] 11
}
}
ETSI

as used for Cell 1
as used for Cell 3
cellReselectionPriority [2] 1
}
}
8.1.3.6 RRC connection release / Redirection from E-UTRAN to UTRAN

(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectionInformation with
utra-CarrierFreq UTRA frequency }
then { UE enters RRC_IDLE state on UTRA frequency included in IE redirectionInformation }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12
and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
1> else:
[TS 36.331, clause 5.3.12]
ETSI
[TS 36.304, clause 5.2.7]
an EUTRA carrier.
...
System Simulator:
- 2 cells, one E-UTRA and one UTRA cell and different location areas:
- Cell 1 E-UTRA serving cell
- Cell 5 suitable neighbour UTRA cell
- The parameters settings and power levels for Cell 1 and Cell 5 are selected according to [18], [5] and Table
8.1.3.6.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 5 can take place (utra
priority is lower than serving and S Cell 1 > Thresh Cell 1,low).
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) on cell 1 according to [18].
Table 8.1.3.6.3.2-0 shows the cell power levels after the preamble.

Cell-specific RS EPRE dBm/15kHz -75 - The power levels are such that
T0 CPICH_Ec dBm/3.84 MHz - -70 camping on Cell 1 is guaranteed.

U-S Message
message (IE redirectionInformation including
UTRA-CarrierFreq of Cell 5).
5?
ETSI
Table 8.1.3.6.3.3-1: Void
Table 8.1.3.6.3.3-2: Void
Table 8.1.3.6.3.3-3: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 8.1.3.6.3.2-
1)

as used for cell 5
cellReselectionPriority[n] 3 Lower priority than
E-UTRA
}
as used for cell 5
E-UTRA
}
}
Table 8.1.3.6.3.3-4 RRCConnectionRelease message (step 1, Table 8.1.3.6.3.2-1)

c1 CHOICE {
utra-FDD Downlink UARFCN of cell UTRA-
5 FDD
utra-TDD Downlink UARFCN of cell UTRA-
5 TDD
}
}
}
ETSI
8.1.3.6.3.2-1)

Utra-PriorityInfoList ::= SEQUENCE {
priority 5
}
}
8.1.3.6a RRC connection release / Redirection from E-UTRAN to UTRAN / Pre-

redirection info
(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with
utra-CarrierFreq UTRA frequency }
then { UE sends an RRC CONNECTION REQUEST message including IE Pre-redirection info set to FALSE
on UTRA frequency included in IE redirectionInformation and enters RRC_IDLE state on that UTRA
frequency }
}
and TS 36.304, clause 5.2.7 and TS 25.331, clause 8.1.3.3, 10.2.39 with additional clarification in R2-105061.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
1> else:
[TS 36.331, clause 5.3.12]
ETSI
[TS 36.304, clause 5.2.7]
an EUTRA carrier.
[TS 25.331, clause 8.1.3.3]
...
1> if the UE supports E-UTRA:
2> if the UE is attempting to establish the signalling connection as a result of being redirected by E-UTRA; and
2> if this is the first attempt to establish the signalling connection;
3> do not include the IE "Pre-Redirection info";
[TS 25.331, clause 10.2.39]
Pre-redirection info OP Pre- The presence of REL-8

redirection this IE indicates
info the UE support of
10.3.3.25a radio access
technologies that
the UE could be
directed to, and
that the UE was
not redirected
from EUTRA.
System Simulator:
- 2 cells, one E-UTRA and one UTRA cell and different location areas:
- Cell 5 suitable neighbour UTRA cell
- The parameters settings and power levels for Cell 1 and Cell 5 are selected according to [18], [5] and Table
8.1.3.6a.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 5 can take place (utra
UE:
None.
Preamble:
Table 8.1.3.6a.3.2-0 shows the cell power levels after the preamble.
ETSI

T0 CPICH_Ec dBm/3.84 MHz - -70 camping on Cell 1 is guaranteed.

U-S Message
UTRA-CarrierFreq of Cell 5).
5?
8.1.3.6a.3.3 Specific message or IE contents
Table 8.1.3.6a.3.3-1: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table
8.1.3.6a.3.2-1)

as used for cell 5
E-UTRA
}
as used for cell 5
E-UTRA
}
}
ETSI
Table 8.1.3.6a.3.3-2 RRCConnectionRelease message (step 1, Table 8.1.3.6a.3.2-1)

c1 CHOICE {
utra-FDD Downlink UARFCN of cell UTRA-
5 FDD
utra-TDD Downlink UARFCN of cell UTRA-
5 TDD
}
cellInfoList-r9 ::= CHOICE {} Not present redirection with
SIB is optional
}
}
}
}
}
}
Table 8.1.3.6a.3.3-3: System Information Block type 19 for Cell 5 (preamble and all steps, Table
8.1.3.6a.3.2-1)

Utra-PriorityInfoList ::= SEQUENCE {
priority 5
}
}
Table 8.1.3.6a.3.3-4 RRC CONNECTION REQUEST (step 2, Table 8.1.3.6a.3.2-1)
Derivation Path: 36.508 table 4.7B.1-7

Pre-redirection info Not present The presence of
this IE indicates
the UE support of
radio access
technologies that
the UE could be
directed to, and
that the UE was
not redirected
from EUTRA
8.1.3.7 RRC connection release / Redirection from UTRAN to E-UTRAN

(1)
with { UE in UTRA Idle state }
ETSI
ensure that {
when { UE is requested to make an outgoing PS call }
then { UE includes in the RRC CONNECTION REQUEST the IE Pre-Redirection info" }
}
(2)
with { UE in UTRA CELL_DCH state }
ensure that {
when { UE receives an RRC CONNECTION RELEASE message including an IE Redirection info with E-UTRA
target info E-UTRA frequency }
then { UE enters RRC_IDLE state on E-UTRAN Carrier included in IE Redirection info }
}
References: The conformance requirements covered in the current TC are specified in: TS 25.331, clause 8.1.3.3,
8.1.4.3 and clause 8.5.2.
[TS 25.331, clause 8.1.3.3]
The UE shall, in the transmitted RRC CONNECTION REQUEST message:
1> if the UE supports E-UTRA:
2> if the variable EUTRA_FREQUENCY_INFO_LIST contains no E-UTRA frequencies;
3> include the IE "Pre-Redirection info";
3> if the UE supports E-UTRA FDD:
4> set the IE "Support of E-UTRA FDD" to TRUE.
3> if the UE supports E-UTRA TDD:
4> set the IE "Support of E-UTRA TDD" to TRUE.
2> if the UE supports any of the bands that the E-UTRA frequencies included in the variable
EUTRA_FREQUENCY_INFO_LIST belong to;
3> include the IE "Pre-Redirection info";
3> if the UE supports any of the bands that the E-UTRA FDD frequencies included in the variable
EUTRA_FREQUENCY_INFO_LIST belong to:
4> set the IE "Support of E-UTRA FDD" to TRUE.
3> if the UE supports any of the bands that the E-UTRA TDD frequencies included in the variable
EUTRA_FREQUENCY_INFO_LIST belong to:
4> set the IE "Support of E-UTRA TDD" to TRUE.
[TS 25.331, clause 8.1.4.3]
The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH
and CELL_PCH (FDD only). Furthermore this procedure can interrupt any ongoing procedures with the UE in the
above listed states.
When the UE receives the first RRC CONNECTION RELEASE message; and
1> if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable
U_RNTI; or
1> if the message is received on DCCH:
the UE shall perform the RRC connection release procedure as specified below.
ETSI
When the UE receives the first RRC CONNECTION RELEASE message; and
1> if the message is received on the CCCH, the IE "UTRAN group identity" is present and there is a group identity
match according to subclause 8.6.3.13:
the UE shall perform the RRC connection release procedure as specified below.
The UE shall:
1> in state CELL_DCH:
2> initialise the counter V308 to zero;
2> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the
value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the
table "Accepted transactions" in the variable TRANSACTIONS;
2> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using
UM RLC on the DCCH to the UTRAN;
2> if the IE "Rplmn information" is present:
3> the UE may:
4> store the IE on the ME together with the PLMN id for which it applies;
3> the UE may then:
4> utilise this information, typically indicating where a number of BCCH frequency ranges of a RAT
may be expected to be found, during subsequent Rplmn selections of the indicated PLMN.
2> if the IE "UE Mobility State Indicator" is present:
3> consider the High-mobility state to have being detected when entering idle mode.
2> start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio
interface.
1> in state CELL_FACH:
2> if the RRC CONNECTION RELEASE message was received on the DCCH:
3> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to
the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in
the table "Accepted transactions" in the variable TRANSACTIONS;
3> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission
using AM RLC on the DCCH to the UTRAN.
3> when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been
confirmed by the lower layers:
4> release all its radio resources; and
4> indicate the release of the established signalling connections (as stored in the variable
ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in
the variable ESTABLISHED_RABS) to upper layers; and
4> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions"
and "Rejected transactions" in the variable TRANSACTIONS;
4> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
4> clear the variable ESTABLISHED_RABS;
4> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to
upper layers;
ETSI
4> enter idle mode;
4> perform the actions specified in subclause 8.5.2 when entering idle mode.
3> and the procedure ends.
2> if the RRC CONNECTION RELEASE message was received on the CCCH:
3> release all its radio resources;
3> indicate the release of the established signalling connections (as stored in the variable
ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the
variable ESTABLISHED_RABS) to the upper layers;
3> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions"
and "Rejected transactions" in the variable TRANSACTIONS;
3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
3> clear the variable ESTABLISHED_RABS;
3> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to
upper layers;
3> enter idle mode;
3> perform the actions specified in subclause 8.5.2 when entering idle mode;
3> and the procedure ends.
[TS 25.331, clause 8.5.2]
When entering idle mode from connected mode, the UE shall:
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4;
1> if the RRC CONNECTION RELEASE message was received and the IE "Redirection info" was present therein:
2> if the IE "Frequency info" is present, attempt to camp on a suitable cell on the indicated UTRA carrier
included in the RRC CONNECTION RELEASE message;
2> if the IE "GSM target cell info" is present, attempt to camp on a suitable cell of the list of cells for the
indicated RAT included in the RRC CONNECTION RELEASE message. If no cells were indicated for that
RAT or no suitable cell of the indicated cells for that RAT is found within 10s, attempt to camp on any
suitable cell of that RAT; or
2> if the IE "E-UTRA target info" is present, attempt to camp on any of the frequencies for the indicated RAT
included in the RRC CONNECTION RELEASE message, excluding any cell indicated in the list of not
allowed cells for that RAT, if present. If no suitable cell on the indicated frequencies for that RAT is found
within 10s, attempt to camp on any suitable cell of that RAT, excluding any cell indicated in the list of not
allowed cells for that RAT; or
2> if no suitable cell is found on the indicated UTRA carrier or RAT camp on any suitable cell.
System Simulator:
- 2 cells, one UTRA and one E-UTRA cell:
- Cell 5 UTRA serving cell (priority 4 default)
- Cell 1 suitable neighbour E-UTRA cell (priority 3)
ETSI
UE:
UTRAN Idle state
Preamble:
State 3 or state 7 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
various time instants of the test execution. Subsequent configurations marked "T1" is applied at the point indicated in

-70 -
EPRE Hz that entering condition for event 3c
CPICH Ec dBm/3.8 is satisfied.
- -85
T1 (UTRA FDD) 4 MHz
PCCPCH Ec
dBm/1.2
(UTRA LCR - -85
8 MHz
TDD)
ETSI

U-S Message
1 Make the UE initiate an outgoing PS call. - - - -
2 Check: Does the UE include the IE Pre- --> RRC CONNECTION REQUEST 1 P
redirection info with Support of E-UTRA set to
TRUE?
3 The SS transmits a RRC CONNECTION RRC CONNECTION SETUP - -
<--
SETUP on SRB1 on Cell 5.
4 The UE transmits an RRC CONNECTION --> RRC CONNECTION SETUP - -
SETUP COMPLETE message COMPLETE
5 The UE transmits the SERVICE REQUEST --> INITIAL DIRECT TRANSFER - -
message for PS data call
- EXCEPTION: Steps 6a1 and 6a2 describe
sequence that takes place if a capability is
supported.
UTRAN FDD:
IF pc_UTRA_CompressedModeRequired and
pc_UTRA_FeatrGrp_2 THEN Steps 6a1, 6a2
UTRAN TDD: go to step 6Aa1

6a1 The SS transmits a PHYSICAL CHANNEL <-- PHYSICAL CHANNEL - -
RECONFIGURATION message on Cell 5 RECONFIGURATION
including the DPCH compressed mode info.
6a2 The UE transmits a PHYSICAL CHANNEL --> PHYSICAL CHANNEL - -
RECONFIGURATION COMPLETE message RECONFIGURATION
on Cell 5. COMPLETE
- EXCEPTION: Steps 6Aa1 and 6Aa2 describe
supported.
IF pc_UTRA_FeatrGrp_2 THEN 6Aa1 to 6Aa2.

6Aa1 The SS configures the Inter-RAT <-- MEASUREMENT CONTROL - -
measurement with E-UTRA frequency list
including the DL Carrier frequency of Cell 1
6Aa2 The SS changes Cell 1 and Cell 5 power level - - - -
Note: The UE starts sending MEASUREMENT
REPORT messages during the Authentication
Phase
7-9 Void
10 The SS starts the Authentication and Ciphering <-- DOWNLINK DIRECT TRANSFER - -
Request procedure
11 The UE transmits the Authentication and --> UPLINK DIRECT TRANSFER - -
Ciphering Response
12 The SS transmits a SECURITY MODE <-- SECURITY MODE COMMAND - -
COMMAND message.
EXCEPTION: Step 13A and Step 14a can
occur in any order.
13 The UE transmits a SECURITY MODE --> SECURITY MODE COMPLETE - -
COMPLETE message
13A The UE transmits an ACTIVATE PDP --> UPLINK DIRECT TRANSFER
CONTEXT REQUEST message
NOTE: Retransmission of this message is
ignored
- EXCEPTION: Step 14a describes behaviour
that depends on the UE capability; the "lower
case letter" identifies a step sequence that
takes place if a capability is supported.
14a IF pc_UTRA_FeatrGrp_2 THEN if --> MEASUREMENT REPORT - -
MEASUREMENT REPORT is received during
ETSI
the authentication and security phase (from

step 10 to 13) goto next step otherwise the SS
waits for MEASUREMENT REPORT message.
15 The SS transmits an RRC CONNECTION <-- RRC CONNECTION RELEASE - -
RELEASE message (IE E-UTRA target info
including DL Carrier frequency of Cell 1).
16 The UE transmits a RRC CONNECTION --> RRC CONNECTION RELEASE - -
RELEASE COMPLETE message COMPLETE
17 The UE transmits a RRC CONNECTION --> RRC CONNECTION RELEASE - -
RELEASE COMPLETE message COMPLETE
Cell 1?
NOTE: pc_ UTRA_FeatrGrp_2 is always set to TRUE when pc_UTRA_CompressedModeRequired is TRUE
Table 8.1.3.7.3.3-1 System Information Block type 19 for Cell 5 (preamble and all steps, Table
8.1.3.7.3.2-1)
Derivation Path: 36.508 table Table 4.4.4.1-1

priority 4
}
eutra-FrequencyAndPriorityInfoList SEQUENCE 1 entry
earfcn[1] Downlink EARFCN of
Cell 1
priority[1] 3
}
}
Table 8.1.3.7.3.3-2: RRC CONNECTION REQUEST (step 2, Table 8.1.3.7.3.2-1)
Derivation path: 34.108 default RRC CONNECTION REQUEST in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA
TDD
Pre-redirection info The presence of
this IE indicates
the UE support of
radio access
technologies that
the UE could be
directed to
Support of E-UTRA FDD TRUE E-UTRA-
FDD
Support of E-UTRA TDD TRUE E-UTRA-
TDD
Table 8.1.3.7.3.3-3: MEASUREMENT CONTROL (step 6Aa1, Table 8.1.3.7.3.2-1)
Derivation Path: 36.508, clause 4.7B.1 Table 4.7B.1-3

CHOICE Measurement type Inter-RAT measurement
CHOICE report criteria Inter-RAT measurement
reporting criteria
Parameters required for each event 1 entry
Inter-RAT event identity 3c
Threshold own system Not present
W Not present
ETSI
DPCH Compressed mode status info UTRA CM-

Support
TGPS reconfiguration CFN (Current CFN + (256 –
TTI/10msec))mod 256
Transmission gap pattern sequence 1 entry
TGPSI 1
TGPS Status Flag activate
TGCFN (Current CFN + (256 –
TTI/10msec))mod 256
DPCH Compressed mode status info Not Present UTRA CM-
Not
Supported
UTRA CM- UTRAN Compressed Mode configuration supported
Supported
UTRA CM-Not UTRAN Compressed Mode configuration not supported
Supported
Table 8.1.3.7.3.3-4: RRC CONNECTION RELEASE (step 15, Table 8.1.3.7.3.2-1)
Derivation path: 34.108 default RRC CONNECTION RELEASE in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA TDD
N308 1
Redirection info
Frequency info Omitted
Inter-RAT info E-UTRA
E-UTRA target info
E-UTRA Target Frequency Info List 1 Entry
FDD E-UTRA-FDD
DL Carrier frequency The DL Carrier frequency
of Cell 1
Blacklisted cells per freq list Omitted
TDD E-UTRA-TDD
DL Carrier frequency The DL Carrier frequency
of Cell 1
Blacklisted cells per freq list Omitted
Table 8.1.3.7.3.3-5: PHYSICAL CHANNEL RECONFIGURATION (step 6a1, Table 8.1.3.7.3.2-1)
Derivation path: 36.508, clause 4.7B.1 Table 4.7B.1-5

CHOICE UL/DL Mode UL and DL, UL only or
DL only (depending on
the UE capability)
Downlink compressed mode method SF/2(or not sent,
depending on the UE
capability)
Uplink compressed mode method SF/2(or not sent,
depending on the UE
capability)
8.1.3.8 RRC connection release / Redirection from E-UTRAN to GERAN

(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo set to
geran }
then { UE enters Idle mode on GERAN Cell included in IE redirectedCarrierInfo }
}
ETSI
and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
1> else:
[TS 36.331, clause 5.3.12]
2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of
leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, a UE shall attempt to camp on the last cell for which it was in
RRC_CONNECTED or any cell on a frequency or frequency of RAT assigned by RRC in the state transition message.
...
System Simulator:
- 2 cells, one E-UTRA and one GERAN cell and different location areas:
- Cell 1 E-UTRA serving cell (priority 4 default)
- Cell 24 GERAN neighbouring cell (priority 3)
- The parameters settings and power levels for Cell 1 and Cell 24 are selected according to [18], [5], [25] and
Table 8.1.3.8.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 24 can take place
(GERAN priority is lower than serving and S Cell 1 > Thresh Cell 1,low)
ETSI
UE:
None.
Preamble:

T0
GERAN Cell Power dBm - -70 camping on Cell 1 is guaranteed.
T1 reselection back to cell 1 should not
GERAN Cell Power dBm -70
occur

U-S Message
startingARFCN of Cell 24).
1A The UE sends a CHANNEL REQUEST --> CHANNEL REQUEST - -
message on the cell 24
1B An uplink TBF is established in order to allow - - - -
the UE to transmit a ROUTING AREA
UPDATE REQUEST message signalling.
1C The UE transmits a ROUTING AREA UPDATE --> ROUTING AREA UPDATING - -
REQUEST message. REQUEST
1D The SS changes cell 1 level according to the
row “T1” in table 8.1.3.8.3.2-0
steps 4-11 indicate that the UE is camped on
GERAN Cell 24?
NOTE: The UE completes the RAU procedure.
ETSI
Table 8.1.3.8.3.3-1: Void
Table 8.1.3.8.3.3-2: SystemInformationBlockType7 for cell 1 (preamble and all steps, Table 8.1.3.8.3.2-
1)

carrierFreqs SEQUENCE [n] {
}
}
}
}
}
}

c1 CHOICE {
redirectedCarrierInfo CHOICE {
geran SEQUENCE {
startingARFCN Downlink ARFCN of Cell
24
bandIndicator The same band indicator
of the Cell 24
explicitListOfARFCNs 0 Entries
}
}
}
}
}
}
}
8.1.3.9 RRC connection release / Redirection from E-UTRAN to CDMA2000-HRPD

(1)
ensure that {
cdma2000-HRPD }
then { UE enters cdma2000-HRPD mode }
}
ETSI
and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
2> use the idle mobility parameters broadcast in the system information;
1> else:
[TS 36.331, clause 5.3.12]
[TS 36.304, clause 5.2.7]
...
System Simulator:
- 2 cells, one E-UTRA and one HRPD cell:
- Cell 15 suitable neighbour HRPD cell
- The parameters settings and power levels for Cell 1 and Cell 15 are selected according to [18], [xx] and Table
8.1.3.9.3.2-1 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 15 can take place (hrpd
ETSI
UE:
None.
Preamble:
Note: UE is not pre-registered in Cell 15.

Îor/Ioc dB - -5 camping on Cell 1 is guaranteed.
T0
Pilot Ec /Io (Note 1) dB - -6

U-S Message
cdma2000-HRPD of Cell 15).
on Cell 15 to initiate registration?
Table 8.1.3.9.3.3-1: Void

c1 CHOICE {
cdma2000-HRPD cdma2000-CarrierInfo for
Cell 15
}
}
}
}
}
8.1.3.10 RRC connection release / Redirection from E-UTRAN to CDMA2000-1xRTT

(1)
ensure that {
cdma2000-1xRTT }
then { UE enters cdma2000-1xRTT mode }
ETSI
and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
1> else:
[TS 36.331, clause 5.3.12]
[TS 36.304, clause 5.2.7]
...
System Simulator:
- 2 cells, one E-UTRA and one 1xRTT cell:
- Cell 19 suitable neighbour 1xRTT cell
- The parameters settings and power levels for Cell 1 and Cell 19 are selected according to [18] and Table
8.1.3.10.3.2-1 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 19 can take place
(1xRTT priority is lower than serving and S Cell 1 > Thresh Cell 1,low).
ETSI
UE:
- UE is not pre-registered in Cell 19.
Preamble:

Îor/Ioc dB - 0 camping on Cell 1 is guaranteed.
T0 Pilot Ec/ Ior dB - -7

U-S Message
message.
on Cell 19 to initiate registration?
Table 8.1.3.10.3.3-1: Void

c1 CHOICE {
cdma2000-1xRTT cdma2000-CarrierInfo for
Cell 19
}
}
}
}
}
8.1.3.11 RRC connection release / Redirection to another E-UTRAN band

(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo with E-
UTRA CarrierFreq on different E-UTRAN band }
then { UE enters RRC_IDLE state on new E-UTRA frequency included in IE redirectedCarrierInfo }
}
ETSI
5.3.12 and TS 36.304, clauses 5.2.4.1, 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
1> else:
[TS 36.331, clause 5.3.12]
[TS 36.304, clause 5.2.4.1]
[TS 36.304, clause 5.2.7]
...
System Simulator:
- 2 cells on different E-UTRA frequencies and different tracking areas:
ETSI
- Cell 1 serving cell
- Cell 10 suitable neighbour inter-band cell
- Cell power levels are selected according to [18] so that camping on Cell 1 is guaranteed
UE:
None.
Preamble:

U-S Message
eutra of Cell 10).
Cell 10?
Table 8.1.3.11.3.3-1: Conditions for table 8.1.3.11.3.3-3
Cell 1
Cell 10
8.1.3.11.3.2-1)

as used for Cell 10
as used for Cell 1
}
}
ETSI

c1 CHOICE {
10
}
}
}
}
}
8.1.3.11a RRC connection release / Redirection to another E-UTRAN band / Between

FDD and TDD
(1)
with { UE in E-UTRA FDD RRC_CONNECTED state }
ensure that {
UTRA CarrierFreq on different E-UTRAN TDD band }
then { UE enters RRC_IDLE state on new E-UTRA TDD frequency included in IE redirectedCarrierInfo
}
}
(2)
ensure that {
UTRA CarrierFreq on different E-UTRAN FDD band }
then { UE enters RRC_IDLE state on new E-UTRA FDD frequency included in IE redirectedCarrierInfo
}
}
5.3.12 and TS 36.304, clauses 5.2.4.1, 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
ETSI
1> else:
[TS 36.331, clause 5.3.12]
[TS 36.304, clause 5.2.4.1]
[TS 36.304, clause 5.2.7]
...
System Simulator:
- 2 cells on different E-UTRA bands which are in different E-UTRA mode (E-UTRA FDD and E-UTRA TDD)
and PLMNs, both PLMNs are UE’s EPLMN.
- Cell 1 is FDD cell and Cell 28 is TDD cell
8.1.3.11a.3.1-1.
Cell PLMN name

1 PLMN1
28 PLMN2
UTRA cells.
UE:
None.
ETSI
Preamble:
8.1.3.11a.3.3-3.
- The UE is in state Generic RB Established (state 3) according to [18] on Cell 1.

U-S Message
eutra CarrierFreq of Cell 28.
Cell 28?
subclause 4.5.3.3 is performed to make the UE
enter state Generic RB Established (state 3)
on Cell 28.
eutra CarrierFreq of Cell 1).
Cell 1?

c1 CHOICE {
eutra Downlink EARFCN of
Cell 28
}
}
}
}
}
ETSI

c1 CHOICE {
1
}
}
}
}
}



8.1.3.12 RRC connection release / Success / With priority information / Inter-band

(1)
with { UE in E-UTRA RRC_IDLE state having received an RRCConnectionRelease message with the
freqPriorityListEUTRA with higher priority frequency in different band}
ensure that {
priority band }
then { UE reselects the cell which belongs to the higher priority band}
}
TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5.
[TS 36.331, clause 5.3.8.3]
The UE shall:
ETSI
1> else:
...
1> else:
[TS 36.304, clause 5.2.4.1]
NOTE 1: Equal priorities between RATs are not supported.
NOTE 2: The network may assign dedicated cell reselection priorities for frequencies not configured by system
information.
[TS 36.304, clause 5.2.4.2]
ETSI
priority.

[TS 36.304, clause 5.2.4.5]

and

ETSI
System Simulator:
NOTE 3: For Cell 10 TAI is set to TAI-2
UE:
None.
Preamble:

dBm/ The power level values are
Cell-specific RS
T0 15kH -85 "off” "off” assigned to satisfy SrxlevCell 1 >
EPRE
z Snonintrasearch. (NOTE 1)
dBm/
Cell-specific RS assigned to satisfy both
T1 15kH -85 -73 -73
EPRE Threshx, low < SrxlevCell 3 and
z
Threshx, high <SrxlevCell 10.

U-S Message
on Cell 1.
level according to the row "T1" in table
8.1.3.12.3.2-1.
Cell 10?
ETSI

c1 CHOICE {
as used for Cell 1
as used for Cell 10
as used for Cell 3
}
t320 Not present
}
}
}
}
}
8.1.3.12.3.2-2)

as used for Cell 3
as used for Cell 10
threshX-Low[1] 11
threshX-High[2] 11
}
}
ETSI

as used for Cell 1
as used for Cell 3
cellReselectionPriority [2] 1
}
}
8.1.3.12a RRC connection release / Success / With priority information / Inter- band /
Between FDD and TDD
(1)
with { UE in E-UTRA RRC_IDLE state in LTE FDD mode having received an RRCConnectionRelease message
with the freqPriorityListEUTRA with higher priority frequency on different LTE TDD band }
ensure that {
priority frequency on different LTE TDD band }
then { UE reselects the cell which belongs to the higher priority frequency on different LTE TDD
band }
}
(2)
with { UE in E-UTRA RRC_IDLE state in LTE TDD mode having received an RRCConnectionRelease message
with the freqPriorityListEUTRA with lower priority frequency on different LTE FDD band }
ensure that {
priority frequency on different LTE FDD band }
then { UE reselects the cell which belongs to the lower priority frequency on different LTE FDD
band }
}
TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> else:
...
ETSI
1> else:
[TS 36.304, clause 5.2.4.1]
NOTE 1: Equal priorities between RATs are not supported.
NOTE 2: The network may assign dedicated cell reselection priorities for frequencies not configured by system
information.
[TS 36.304, clause 5.2.4.2]
ETSI
priority.

[TS 36.304, clause 5.2.4.5]

and

ETSI
System Simulator:
- Cell 1 and Cell 2 are FDD cell and Cell 10 is TDD cell
UTRA cells.
NOTE 1: For Cell 10 TAI is set to TAI-2
UE:
None.
Preamble:

T0 -79 "off” "off” assigned to satisfy SrxlevCell 1 >
EPRE Hz
Sintrasearch. (NOTE 1)
assigned to satisfy SrxlevCell 10
T1 -79 -73 -73 > Threshx, high when reselect to
EPRE Hz
higher priority Cell 10 from
lower priority Cell 1
assigned to satisfy both
T2 -79 -73 -85 SrxlevCell 2 > Threshx, low (good
EPRE Hz
enough ) and SrxlevCell 10 <
Threshserving,low(bad enough)
ETSI

U-S Message
on Cell 1.
8.1.3.12a.3.2-1.
4-8 Check: Does the test result of generic test - - 1 -
procedure in TS 36.508 steps 1 to 5 of
camped on E-UTRAN Cell 10?”
on Cell 10.
8.1.3.12a.3.2-1.
12- Check: Does the test result of generic test - - 2 -
17 procedure in TS 36.508 subclause 6.4.2.7
Cell 2?
Table 8.1.3.12a.3.3-1: RRCConnectionRelease (step 1 and step 9, Table 8.1.3.12a.3.2-2)

c1 CHOICE {
as used for Cell 1
as used for Cell 10
}
t320 Not present
}
}
}
}
}
ETSI
8.1.3.12a.3.2-2)

as used for Cell 10
threshX-High[1] 11 Actual value of
threshold = IE
value * 2 [dB]
threshX-Low[1] 11 Actual value of
threshold = IE
value * 2 [dB]
}
}
8.1.3.12a.3.2-2)
Derivation Path: TS 36.508 [7] clause 4.4.3.3, Table 4.4.3.3-2

threshServingLow 14 (28 dB) 28 is actual value
in dB (14 * 2 dB)
}
}
8.1.3.12a.3.2-2)

as used for Cell 1
threshX-High[1] 11 Actual value of
threshold = IE
value * 2 [dB]
threshX-Low[1] 11 Actual value of
threshold = IE
value * 2 [dB]
}
}
Table 8.1.3.12a.3.3-5: SystemInformationBlockType3 for Cells 1 and 2 (preamble and all steps, Table
8.1.3.12a.3.2-2)
Derivation Path: TS 36.508 [7] clause 4.4.3.3, Table 4.4.3.3-2

}
ETSI
8.1.3.12b RRC connection release / Success / With priority information / Inter-band

(Single frequency operation in source band)
The scope and description of the present TC is the same as test case 8.1.3.12 with the following differences:
- Cell configuration: Cell 28 with frequency f6 replaces Cell 3 with frequency f2.
8.2 RRC connection reconfiguration

8.2.1 Radio bearer establishment
8.2.1.1 RRC connection reconfiguration / Radio bearer establishment for transition
from RRC_IDLE to RRC_CONNECTED / Success / Default bearer / Early
bearer establishment
(1)
with { UE having completed the RRC connection establishment procedure }
ensure that {
when { SS sends in sequence a SecurityModeCommand and an RRCConnectionReconfiguration message }
then { UE establishes the initial security configuration in accordance with the received
securityConfigSMC included in SecurityModeCommand and successfully completes the connection
reconfiguration }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.1.2,
5.3.1.1, 5.3.5.3, 5.3.10.1 and 5.3.10.3. The following represent an extraction of the requirements relevant to the test
purpose.
[TS 36.331, clause 5.1.2]
The UE shall:
1> process the received messages in order of reception by RRC, i.e. the processing of a message shall be completed
before starting the processing of a subsequent message;
NOTE: 1 E-UTRAN may initiate a subsequent procedure prior to receiving the UEs response of a previously
initiated procedure.
[TS 36.331, clause 5.3.1.1]
After having initiated the initial security activation procedure, E-UTRAN initiates the establishment of SRB2 and
DRBs, i.e. E-UTRAN may do this prior to receiving the confirmation of the initial security activation from the UE. In
any case, E-UTRAN will apply both ciphering and integrity protection for the RRC connection reconfiguration
messages used to establish SRB2 and DRBs.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply
with the configuration included in this message, the UE shall:
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC
Connection Re-establishment procedure:
...
1> else:
2> If the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
ETSI
NOTE 2: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than
SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an
outstanding acknowledgment of the SecurityModeComplete message.
...
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new
configuration, upon which the procedure ends;
[TS 36.331, clause 5.3.10.1]
The UE shall:
1> for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration
(SRB establishment):
2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;
2> establish a PDCP entity and configure it with the current security configuration, if applicable;
2> establish an RLC entity in accordance with the received rlc-Config;
2> establish a DCCH logical channel in accordance with the received logicalChannelConfig and with the logical
channel identity set in accordance with 9.1.2
[TS 36.331, clause 5.3.10.3]
The UE shall:
1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration
(DRB establishment):
2> establish a PDCP entity and configure it with the current security configuration and in accordance with the
received pdcp-Config;
2> establish a DTCH logical channel in accordance with the received logicalChannelIdentity and the received
logicalChannelConfig;
1> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
pagingRecordLists.
2 UE transmits an RRCConnectionRequest --> RRCConnectionRequest - -
message.
3 SS transmit an RRCConnectionSetup RRCConnectionSetup - -
<--
message
RRCConnectionSetupComplete to confirm the
establishment. (Note 1)
5 SS transmits a SecurityModeCommand <-- SecurityModeCommand - -
message to activate AS security.
6 Using the same TTI as the <-- RRCConnectionReconfiguration - -
SecurityModeCommand message in step 5,
the SS transmits an
establish a data radio bearer.
SecurityModeComplete message?
8 Check: Does the UE transmit an --> RRCConnectionReconfigurationC 1 P
message to confirm the establishment of data
radio bearer?
indicate that UE is in E-UTRA
Note 1: Contains a SERVICE REQUEST NAS message.
8.2.1.2 Void
8.2.1.3 RRC connection reconfiguration / Radio bearer establishment / Success /
Dedicated bearer
(1)
ensure that {
when { SS sends an RRCConnectionReconfiguration message including a drb-Identity that is not part
of the current UE configuration and a dedicatedInfoNASList}
then { UE successfully establish the radio bearer according to IE radioResourceConfigDedicated }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.3
and 5.3.10.3.
The following represent an extraction of the requirements relevant to the test purpose.
ETSI
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInformation and the UE is able to
comply with the configuration included in this message, the UE shall:
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection
Re-establishment procedure:
1> else:
1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:
2> forward each element of the dedicatedInfoNASList to upper layers;
[TS 36.331, clause 5.3.10.3]
The UE shall:
(DRB establishment):
2> establish a DTCH logical channel in accordance with the received logicalChannelIdentity and the received
logicalChannelConfig;
1> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
message?
3 The UE transmits an ULInformationTransfer --> ULInformationTransfer - -

message. This message includes an
ACTIVATE DEDICATED EPS BEARER
CONTEXT ACCEPT message.
Derivation Path: 36.508 table 4.6.1-8, condition DRB(1,0)

c1 CHOICE{
dedicatedInfoNASList SEQUENCE 1 entry
(SIZE(1..maxDRB)) OF
dedicatedInfoNAS [1] ACTIVATE DEDICATED According 36.508
EPS BEARER table 4.7.3-3
CONTEXT REQUEST
with EPS bearer identity
corresponding to drb-
Identity 2
}
}
}
}
8.2.1.4 Void
from RRC_Idle to RRC CONNECTED / Success / Latency check
(1)
with { UE in E-UTRA RRC_IDLE state and has sent an RRCConnectionRequest message }
ensure that {
when { UE receive a RRCConnectionSetup message and 16 subframes later receives an UL grant }
then { UE successfully transmit RRCConnectionSetupComplete message }
}
(2)
ensure that {
when { UE receive a SecurityModeCommand message and 11 subframes later receives an UL grant }
ETSI
then { UE successfully establish the initial AS security activation according to IE

securityConfigSMC }
}
(3)
ensure that {
when { UE receive a RRCConnectionReconfiguration message including a drb-Identity that is not part
of the current UE configuration and a nas-DedicatedInformation and 16 subframes later receives an UL
grant }
then { UE successfully establish the radio bearer according to IE radioResourceConfiguration }
}
(4)
ensure that {
when { UE receives an UECapabilityEnquiry message after AS security is activated and at 11
subframes later receives an UL grant }
then { UE successfully transmits an UECapabilityInformation message including UE radio access
capability information corresponding to the ue-RadioAccessCapRequest variable }
}
5.3.4.3, 5.3.5.3, 5.6.3.3 and 11.2.
[TS 36.331, clause 5.3.3.4]
The UE shall:
1> stop timer T300;
ETSI
procedure ends;
[TS 36.331, clause 5.3.4.3]
The UE shall:
1> derive the KeNB key, as specified in TS 33.401 [32];
1> derive the KRRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.401 [32];
1> request lower layers to verify the integrity protection of the SecurityModeCommand message, using the
algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the
KRRCint key;
1> if the SecurityModeCommand message passes the integrity protection check:
2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm indicated in the
SecurityModeCommand message, as specified in TS 33.401 [32];
2> configure lower layers to apply integrity protection using the indicated algorithm and the KRRCint key
immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE,
including the SecurityModeComplete message;
2> configure lower layers to apply ciphering using the indicated algorithm, the KRRCenc key and the KUPenc key
after completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent
by the UE, except for the SecurityModeComplete message which is sent unciphered;
2> consider AS security to be activated;
2> submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends;
[TS 36.331, clause 5.3.5.3]
1> else:
2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
[TS 36.331, clause 5.6.3.3]
The UE shall:
ETSI
1> set the contents of UECapabilityInformation message as follows:
2> if the ue-CapabilityRequest includes ‘eutra’:
3> include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to
‘eutra’;
2> if the ue-CapabilityRequest includes ‘geran-cs’ and if the UE supports GERAN CS domain:
3> include the UE radio access capabilities for GERAN CS within a ue-CapabilityRAT-Container and with
the rat-Type set to ‘geran-cs’;
2> if the ue-CapabilityRequest includes ‘geran-ps’ and if the UE supports GERAN PS domain:
3> include the UE radio access capabilities for GERAN PS within a ue-CapabilityRAT-Container and with
the rat-Type set to ‘geran-ps’;
2> if the ue-CapabilityRequest includes ‘utra’ and if the UE supports UTRA:
3> include the UE radio access capabilities for UTRA within a ue-CapabilityRAT-Container and with the
rat-Type set to ‘utra’;
1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;
[TS 36.331, clause 11.2]
The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:
N = the number of 1ms subframes from the end of reception of the E-UTRAN -> UE message on the UE physical layer
up to when the UE shall be ready for the reception of uplink grant for the UE -> E-UTRAN response message with no
access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or
physical layer synchronisation).
Figure 11.2-1: Illustration of RRC procedure delay
Procedure title: E-UTRAN -> UE UE -> E-UTRAN N Notes

RRC Connection Control Procedures
RRC connection RRCConnectionSetu RRCConnectionSetupCo 15
establishment p mplete
RRC connection re- RRCConnectionReco RRCConnectionReconfigu 15
configuration (radio nfiguration rationComplete
resource configuration)
Initial security SecurityModeComma SecurityModeCommandC 10
activation nd omplete/SecurityModeCo
mmandFailure
Other procedures
UE capability transfer UECapabilityEnquiry UECapabilityInformation 10
ETSI
System Simulator:
- Cell 1
UE:
None.
Preamble:

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

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

RRCConnectionSetup ::= SEQUENCE {
c1 CHOICE {
radioResourceConfigDedicated SEQUENCE {
}
}
}
}
}
}

c1 CHOICE{
}
}
}
}
}
}
ETSI
Table 8.2.1.5.3.3-4: RRCConnectionReconfiguration (preamble: Table 4.5.2.3-1 [18], step 14)

c1 CHOICE{
}
}
}
}
}
}

from RRC_Idle to RRC CONNECTED / Success / Latency check /
SecurityModeCommand and RRCConnectionReconfiguration transmitted in
the same TTI
(1)
ensure that {
when { UE received SecurityModeCommand message and RRCConnectionReconfiguration message including
a drb-Identity that is not part of the current UE configuration and a nas-DedicatedInformation in
the same TTI and 21 subframes later receives an UL grant }
then { UE successfully establish the initial AS security activation according to IE
securityConfigSMC and the radio bearer according to IE radioResourceConfiguration }
}
5.3.5.3 and 11.2.
[TS 36.331, clause 5.3.4.3]
The UE shall:
1> derive the KeNB key, as specified in TS 33.401 [32];
1> derive the KRRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.401 [32];
1> request lower layers to verify the integrity protection of the SecurityModeCommand message, using the
algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the
KRRCint key;
1> if the SecurityModeCommand message passes the integrity protection check:
2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm indicated in the
SecurityModeCommand message, as specified in TS 33.401 [32];
2> configure lower layers to apply integrity protection using the indicated algorithm and the KRRCint key
immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE,
including the SecurityModeComplete message;
ETSI
2> configure lower layers to apply ciphering using the indicated algorithm, the KRRCenc key and the KUPenc key
after completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent
by the UE, except for the SecurityModeComplete message which is sent unciphered;
2> consider AS security to be activated;
2> submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends;
[TS 36.331, clause 5.3.5.3]
1> else:
[TS 36.331, clause 11.2]
The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:
N = the number of 1ms subframes from the end of reception of the E-UTRAN -> UE message on the UE physical layer
up to when the UE shall be ready for the reception of uplink grant for the UE -> E-UTRAN response message with no
access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or
physical layer synchronisation).
Figure 11.2-1: Illustration of RRC procedure delay
ETSI

RRC Connection Control Procedures
Initial security SecurityModeComma RRCConnectionReconfigu 20 The two DL messages are
activation + RRC nd, rationComplete transmitted in the same TTI
connection re- RRCConnectionReco
configuration (RB nfiguration
establishment)
System Simulator:
- Cell 1
UE:
None.
Preamble:

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

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

RRCConnectionSetup ::= SEQUENCE {
c1 CHOICE {
}
}
}
}
}
}

c1 CHOICE{
}
}
}
}
}
}
ETSI
Table 8.2.1.6.3.3-4: RRCConnectionReconfiguration (preamble: Table 4.5.2.3-1 [18], step 14)

c1 CHOICE{
}
}
}
}
}
}

SRB2
with { UE in E-UTRA RRC_CONNECTED state without SRB2}
ensure that {
when { SS sends an RRCConnectionReconfiguration message including SRB2 configuration }
then { UE successfully establish the signalling radio bearer }
}
and 5.3.10.1.
[TS 36.331, clause 5.3.5.3]
1> else:
[TS 36.331, clause 5.3.10.1]
The UE shall:
1> for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration
(SRB establishment):
ETSI
2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;
2> establish a PDCP entity and configure it with the current security configuration, if applicable;
2> establish a DCCH logical channel in accordance with the received logicalChannelConfig and with the logical
channel identity set in accordance with 9.1.2;
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Registered, Idle Mode (State 2) according to [18].

U-S Message
1-7 Generic Radio Bearer Establishment (State 3) - -
step 1 to 7 in TS 36.508 subclause 4.5.3.3.
establish SRB2.
9 Check: Does the UE transmits an --> RRCConnectionReconfigurationC 1 P
message?
indicates that UE is in E-UTRA
ETSI
Table 8.2.1.7.3.3-1: RRCConnectionReconfiguration (step 8, Table 8.2.1.7.3.2-1))

C1 CHOICE{
srb-ToAddModList SEQUENCE (SIZE (1..2))
OF SEQUENCE {
srb-ToAddMod[1] SEQUENCE {
rlc-Config CHOICE {
explicitValue RLC-Config-NON-
DEFAULT-SRB2
}
}
}
}
}
}
}
}
}
Table 8.2.1.7.3.3-2: RLC-Config-NON-DEFAULT-SRB2 ( Table 8.2.1.7.3.3-1))
Derivation Path: 36.331 clauses 6.3.2, 9.2.1.2

RLC-Config-NON-DEFAULT-SRB2 ::= CHOICE {
am SEQUENCE {
pollPDU p16
pollByte kb500
maxRetxThreshold t6
}
dl-AM-RLC SEQUENCE {
t-Reordering ms100
}
}
}

Dedicated bearer / ROHC configured
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including IE headerCompression set to
"rohc" }
then { UE transmits an RRCConnectionReconfigurationComplete message }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.5.3, clause
5.3.10.0, clause 5.3.10.3, TS 36.323, clause 5.5.1, 5.5.2 and TS 36.306, clause 4.3.1.1.
ETSI
[TS 36.331, clause 5.3.5.3]
...
1> else:
[TS 36.331, clause 5.3.10.0]
The UE shall:
...
1> if the received radioResourceConfigDedicated includes the drb-ToAddModList:
2> perform DRB addition or reconfiguration as specified in 5.3.10.3;
[TS 36.331, clause 5.3.10.3]
The UE shall:
(DRB establishment including the case when full configuration option is used):
[TS 36.323, clause 5.5.1]
The header compression protocol is based on the Robust Header Compression (ROHC) framework [7]. There are
multiple header compression algorithms, called profiles, defined for the ROHC framework. Each profile is specific to
the particular network layer, transport layer or upper layer protocol combination e.g. TCP/IP and RTP/UDP/IP.
The detailed definition of the ROHC channel is specified as part of the ROHC framework in RFC 4995 [7]. This
includes how to multiplex different flows (header compressed or not) over the ROHC channel, as well as how to
associate a specific IP flow with a specific context state during initialization of the compression algorithm for that flow.
The implementation of the functionality of the ROHC framework and of the functionality of the supported header
compression profiles is not covered in this specification.
In this version of the specification the support of the following profiles is described:
Table 5.5.1.1: Supported header compression protocols and profiles
Profile Usage: Reference

Identifier
0x0000 No compression RFC 4995
0x0001 RTP/UDP/IP RFC 3095, RFC 4815
0x0002 UDP/IP RFC 3095, RFC 4815
0x0003 ESP/IP RFC 3095, RFC 4815
0x0004 IP RFC 3843, RFC 4815
0x0006 TCP/IP RFC 4996
0x0101 RTP/UDP/IP RFC 5225
0x0102 UDP/IP RFC 5225
0x0103 ESP/IP RFC 5225
0x0104 IP RFC 5225
ETSI
[TS 36.323, clause 5.5.2]
PDCP entities associated with DRBs can be configured by upper layers [3] to use header compression.
[TS 36.306, clause 4.3.1.1]
This field defines which ROHC profiles from the list below are supported by the UE.
- 0x0000 ROHC uncompressed (RFC 4995)
- 0x0001 ROHC RTP (RFC 3095, RFC 4815)
- 0x0002 ROHC UDP (RFC 3095, RFC 4815)
...
'IMS capable UEs supporting voice' shall support ROHC profiles 0x0000, 0x0001, 0x0002 and be able to compress and
decompress headers of PDCP SDUs at a PDCP SDU rate corresponding to supported IMS voice codecs.
System Simulator:
- Cell 1
UE:
None.
Preamble:

U-S Message
message?
3 The UE transmits an ULInformationTransfer --> ULInformationTransfer - -
message. This message includes an
ACTIVATE DEDICATED EPS BEARER
CONTEXT ACCEPT message.
Derivation Path: TS 36.508 Table 4.6.1-8, condition DRB(0, 1)

c1 CHOICE{
ETSI
DedicatedInfoNAS[1] ACTIVATE DEDICATED According 36.508
EPS BEARER table 4.7.3-3
CONTEXT REQUEST
with EPS bearer identity
corresponding to drb-
Identity 2
}
}
}
}
Table 8.2.1.8.3.3-2: PDCP-Config (Table 8.2.1.8.3.3-1)
Derivation Path: TS 36.508 Table 4.8.2.1.2.1-1

PDCP-Config-DRB-UM ::= SEQUENCE {
rlc-UM SEQUENCE {
pdcp-SN-Size len7bits
}
headerCompression CHOICE {
rohc SEQUENCE {
maxCID 15 DEFAULT 15
profiles SEQUENCE { IMS capable UEs
supporting voice
shall support
ROHC profiles
0x0000, 0x0001,
0x0002.
profile0x0001 TRUE
profile0x0002 TRUE
profile0x0003 FALSE
profile0x0004 FALSE
profile0x0006 FALSE
profile0x0101 FALSE
profile0x0102 FALSE
profile0x0103 FALSE
profile0x0104 FALSE
}
}
}
}
Table 8.2.1.8.3.3-3: RLC-Config (Table 8.2.1.8.3.3-1)
Derivation Path: TS 36.508 Table 4.8.2.1.3.1-1

RLC-Config-DRB-UM ::= CHOICE {
um-Bi-Directional SEQUENCE {
ul-UM-RLC SEQUENCE {
}
dl-UM-RLC SEQUENCE {
}
}
}
ETSI
8.2.2 Radio resource reconfiguration

8.2.2.1 RRC connection reconfiguration / Radio resource reconfiguration / Success
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a
radioResourceConfigDedicated with SRB, DRB, transport channel and physical channel reconfiguration }
then { UE reconfigures the data and signalling radio bearers and sends an
RRCConnectionReconfigurationComplete message }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.5.3,
5.3.10.1, 5.3.10.3, 5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.3]
1> else:
[TS 36.331, clause 5.3.10.1]
The UE shall:
1> for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration (SRB
reconfiguration):
2> reconfigure the RLC entity in accordance with the received rlc-Config;
2> reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;
[TS 36.331, clause 5.3.10.3]
1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration (DRB
reconfiguration):
2> if the pdcp-Config is included:
3> reconfigure the PDCP entity in accordance with the received pdcp-Config;
2> if the rlc-Config is included:
ETSI
3> reconfigure the RLC entity or entities in accordance with the received rlc-Config;
2> if the logicalChannelConfig is included:
3> reconfigure the DTCH logical channel in accordance with the received logicalChannelConfig;
NOTE: Removal and addition of the same drb-Identity in single radioResourceConfiguration is not supported.
[TS 36.331, clause 5.3.10.4]
1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;
[TS 36.331, clause 5.3.10.6]
The UE shall:
1> reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated;
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The condition SRB2-DRB(2, 0) is used for step 8 in 4.5.3.3 according to [18].

U-S Message
containing a radioResourceConfigDedicated
with SRBs, DRB, transport channel and
physical channel reconfiguration.
message?
ETSI

c1 CHOICE{
dicated-RECONFIG
}
}
}
}
Table 8.2.2.1.3.3-2: RadioResourceConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-1)

RadioResourceConfigDedicated ::= SEQUENCE {
srb-ToAddModList SRB-ToAddModList- TS 36.508 Table
RECONFIG 4.6.3-22A
drb-ToAddModList DRB-ToAddModList- TS 36.508 Table
RECONFIG 4.6.3-2A
explicitValue MAC-MainConfig-
RECONFIG
}
physicalConfigDedicated PhysicalConfigDedicated
-RECONFIG
}
Table 8.2.2.1.3.3-3: MAC-MainConfig-RECONFIG (Table 8.2.2.1.3.3-2)

MAC-MainConfig ::= SEQUENCE {
}
phr-Config CHOICE {
setup SEQUENCE {
}
}
}
ETSI
Table 8.2.2.1.3.3-4: PhysicalConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-2)

PhysicalConfigDedicated ::= SEQUENCE {
pdsch-ConfigDedicated PDSCH-
ConfigDedicated-
RECONFIG
pucch-ConfigDedicated Not present
pusch-ConfigDedicated Not present
uplinkPowerControlDedicated Not present
tpc-PDCCH-ConfigPUCCH Not present
tpc-PDCCH-ConfigPUSCH Not present
cqi-ReportConfig Not present
soundingRsUL-ConfigDedicated Not present
defaultValue NULL
}
schedulingRequestConfig Not present
}
Table 8.2.2.1.3.3-5: PDSCH-ConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-4)

PDSCH-ConfigDedicated ::= SEQUENCE {
p-a dB1
}
8.2.2.2 RRC connection reconfiguration / SRB/DRB reconfiguration / Success

(1)
with { UE in E-UTRA RRC_CONNECTED state}
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing SRB reconfiguration }
then { UE reconfigures affected SRBs and sends an RRCConnectionReconfigurationComplete message }
}
(2)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing DRB reconfiguration }
then { UE reconfigures affected DRBs and sends an RRCConnectionReconfigurationComplete message }
}
References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3,
5.3.10.1 and 5.3.10.3.
[TS 36.331, clause 5.3.5.3]
1> else:
3>perform the Radio resource configuration procedure as specified in 5.3.10;
ETSI
[TS 36.331, clause 5.3.10.1]
The UE shall:
1> for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration (SRB
reconfiguration):
2> reconfigure the RLC entity in accordance with the received rlc-Config;
2> reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;
[TS 36.331, clause 5.3.10.3]
The UE shall:
1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration (DRB
reconfiguration):
2> if the pdcp-Config is included:
3> reconfigure the PDCP entity in accordance with the received pdcp-Config;
2> if the rlc-Config is included:
3> reconfigure the RLC entity or entities in accordance with the received rlc-Config;
2> if the logicalChannelConfig is included:
3> reconfigure the DTCH logical channel in accordance with the received logicalChannelConfig;
NOTE: Removal and addition of the same drb-Identity in single radioResourceConfiguration is not supported.
8.2.2.2.3 Test Description
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
containing a radioResourceConfigDedicated
with SRB reconfiguration.
message?
3 SS transmits RRCConnectionReconfiguration <-- RRCConnectionReconfiguration - -
message containing a
radioResourceConfigDedicated with DRB
reconfiguration.
message?

c1 CHOICE{
dicated-SRBRECONFIG
}
}
}
}
Table 8.2.2.2.3.3-2: RadioResourceConfigDedicated-SRBRECONFIG (Table 8.2.2.2.3.3-1)

srb-ToAddModList SRB-ToAddModList- TS 36.508 Table
RECONFIG 4.6.3-22A
physicalConfigDedicated Not present
}
ETSI

c1 CHOICE{
dicated-DRBRECONFIG
}
}
}
}
Table 8.2.2.2.3.3-4: RadioResourceConfigDedicated-DRBRECONFIG (Table 8.2.2.2.3.3-3)

drb-ToAddModList DRB-ToAddModList- TS 36.508 Table
RECONFIG 4.6.3-2A
}
Table 8.2.2.2.3.3-5: Void
Table 8.2.2.2.3.3-6: Void
8.2.2.3 CA / RRC connection reconfiguration / SCell addition/modification/release /

Success
8.2.2.3.1 CA / RRC connection reconfiguration / SCell addition/modification/release /
Success / Intra-band Contiguous CA
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with a
SCell addition }
then { UE adds the new SCell, configures lower layers to consider the SCell to be in deactivated
state and sends an RRCConnectionReconfigurationComplete message }
}
(2)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with SCell
modification }
then { UE modifies the affected SCell dedicated configurations and sends an
}
(3)
ensure that {
ETSI
when { UE receives an RRCConnectionReconfiguration message containing sCellToReleaseList with a

sCellIndex equling to one of the current UE SCell configuration }
then { UE releases this SCell and sends an RRCConnectionReconfigurationComplete message }
}
5.3.10.3a and 5.3.10.3b
[TS 36.331, clause 5.3.5.3]
1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:
2> perform SCell release as specified in 5.3.10.3a;
1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:
2> perform SCell addition or modification as specified in 5.3.10.3b;
[TS 36.331, clause 5.3.10.3a]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell;
1> if the release is triggered by RRC connection re-establishment:
2> release all SCells that are part of the current UE configuration;
[TS 36.331, clause 5.3.10.3b]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration
(SCell addition):
2> add the SCell, corresponding to the cellIdentification, in accordance with the received
radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell;
2> configure lower layers to consider the SCell to be in deactivated state;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell
modification):
2> modify the SCell configuration in accordance with the received radioResourceConfigDedicatedSCell;
ETSI
8.2.2.3.1.3 Test Description
System Simulator:
- Cell 1 is the PCell, Cell3 is the SCell to be added.
- Cell 3 is an Inactive SCell according to [18] cl. 6.3.4.
UE:
None.
Preamble:
Table 8.2.2.3.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 the
configuration marked "T1" and "T2" are applied at the point indicated in the Main behaviour description in Table
8.2.2.3.1.3.2-2.

Cell-specific dBm/15k The power level values are such that
T0 -79 Off
RS EPRE Hz camping on Cell 1 is guarantee.
Cell-specific dBm/15k measurement results for Cell 1 (M1)
T1 -79 -85
RS EPRE Hz and Cell 3 (M3) satisfy entry condition
for event A3 (M3 > M1).
T2 -79 -97
RS EPRE Hz and Cell 3 (M3) satisfy the leave
condition for event A3 (M3 < M1).
ETSI

U-S Message
Cell 1 to setup inter Frequency measurement.
message on Cell 1.
3 The SS changes Cell 3 parameters according - - - -
4 The UE transmits a MeasurementReport --> MeasurementReport - -
containing an sCellToAddModList with SCell
Cell 3 addition.
message?
containing an sCellToAddModList with SCell
Cell 3 modification and including measConfig
to release measurement gap.
message?
containing an sCellToReleaseList with an
sCellIndex equalling to the Cell 3 cell index in
the current UE configuration.
message?
Table 8.2.2.3.1.3.3-0: Conditions for specific message contents

in Tables 8.2.2.3.1.3.3-7, 8.2.2.3.1.3.3-8 and 8.2.2.3.1.3.3-11
Uplink_CA The UE supports carrier aggregation in UL under the test band.
Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS
ETSI
Table 8.2.2.3.1.3.3-2: MeasConfig (Table 8.2.2.3.1.3.3-1)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-1, condition INTER-FREQ

MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE 2 entries
(1..maxObjectId)) OF SEQUENCE {
measObjectId[1] IdMeasObject-f1
measObject[1] MeasObjectEUTRA- Cell 1
GENERIC(f1)
GENERIC(f2)
}
reportConfigToAddModList SEQUENCE (SIZE 1 entry
(1..maxReportConfigId)) OF SEQUENCE {
reportConfigId[1] IdReportConfig-A3
reportConfig[1] ReportConfig-A3
}
measIdToAddModList SEQUENCE (SIZE 1 entry
(1..maxMeasId)) OF SEQUENCE {
measId[1] 1
}
}
Table 8.2.2.3.1.3.3-3: ReportConfig-A3 (step 1, Table 8.2.2.3.1.3.2-2)
Derivation Path: 36.508 clause 4.6.6 table 4.6.6-6

ReportConfigEUTRA-A3 ::= SEQUENCE {
triggerType CHOICE {
event SEQUENCE {
eventId CHOICE {
eventA SEQUENCE {
a3-Offset -24 (-12 dB)
reportOnLeave TRUE
}
}
}
}
}
ETSI
Table 8.2.2.3.1.3.3-4: MeasurementReport (step 4, Table 8.2.2.3.1.3.2-2)

MeasurementReport ::= SEQUENCE {
c1 CHOICE {
measurementReport-r8 SEQUENCE {
measResults ::= SEQUENCE {
measId 1
measResultPCell ::= SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultNeighCells CHOICE {
measResultListEUTRA ::= SEQUENCE (SIZE Report Cell 3
(1..maxCellReport)) OF SEQUENCE {
physCellId [1] physicalCellId of Cell 3
cgi-Info [1] SEQUENCE {} Not present
measResult [1] SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
additionalSI-Info-r9 SEQUENCE {} Not present
}
}
}
measResultForECID-r9 SEQUENCE {} Not present
locationInfo-r10 SEQUENCE {} Not present
measResultServFreqList-r10 SEQUENCE {} Not present
}
}
}
}
}

c1 CHOICE{
sCellToReleaseList-r10 Not present
sCellToAddModList-r10 SCellToAddMod-r10-f2- SCell addition for
Add Cell 3
}
}
}
}
}
}
}
ETSI
Table 8.2.2.3.1.3.3-6: SCellToAddMod-r10-f2-Add (Table 8.2.2.3.1.3.3-5)
Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

SCellToAddMod-r10 ::= SEQUENCE (SIZE 1 entry
(1..maxSCell-r10)) OF SEQUENCE {
sCellIndex-r10 1
physCellId-r10 Physical Cell Identity of
Cell 3
as used for Cell 3
}
radioResourceConfigCommonSCell-r10 RadioResourceConfigCom
monSCell-r10-f2
radioResourceConfigDedicatedSCell-r10 RadioResourceConfigDedi
catedSCell-r10-f2
}
Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

RadioResourceConfigCommonSCell-r10 ::=
SEQUENCE {
nonUL-Configuration-r10 SEQUENCE {
dl-Bandwidth-r10 Same downlink system
bandwidth as used for
Cell 3
}
Ul-Configuration-r10 Not present
ul-Configuration-r10 SEQUENCE { Uplink_CA
ul-FreqInfo-r10 SEQUENCE {
ul-CarrierFreq-r10 Same uplink EARFCN as OP FDD
used for Cell 3
Not present TDD
ul-Bandwidth-r10 Same uplink system optional FDD
Cell 3
Not present TDD
additionalSpectrumEmissionSCell-r10 Same
additionalSpectrumEmiss
ion as used for Cell 3
}
}
}
ETSI
Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

SEQUENCE {
physicalConfigDedicatedSCell-r10 SEQUENCE {
ul-Configuration-r10 Not present
antennaInfoUL-r10 Not present
pusch-ConfigDedicatedSCell-r10 Not present
uplinkPowerControlDedicatedSCell-r10 UplinkPowerControlDedic
atedSCell-r10-DEFAULT
cqi-ReportConfigSCell-r10 CQI-ReportConfigSCell-
r10-DEFAULT
soundingRS-UL-ConfigDedicated-r10 Not present
soundingRS-UL-ConfigDedicated-v1020 Not present
soundingRS-UL-ConfigDedicatedAperiodic-r10 Not present
}
}
}

c1 CHOICE {
measConfig SEQUENCE {
measGapConfig CHOICE {
release NULL
}
}
sCellToAddModList-r10 SCellToAddMod-r10-f2- SCell modification
Mod for Cell 3
}
}
}
}
}
}
}
Table 8.2.2.3.1.3.3-10: SCellToAddMod-r10-f2-Mod (Table 8.2.2.3.1.3.3-9)

sCellIndex-r10 1
cellIdentification-r10 Not present
radioResourceConfigCommonSCell-r10 Not present
radioResourceConfigDedicatedSCell-r10 RadioResourceConfigDedi pc_FeatrGr
catedSCell-r10-f2-Mod p_102
}
ETSI
Table 8.2.2.3.1.3.3-11: RadioResourceConfigDedicatedSCell-r10-f2-Mod (Table 8.2.2.3.1.3.3-10)

SEQUENCE {
antennaInfo-r10 SEQUENCE {
antennaPortsCount an2
}
crossCarrierSchedulingConfig-r10 Not present
csi-RS-Config-r10 Not present
pdsch-ConfigDedicated-r10 Not present
}
antennaInfoUL-r10 SEQUENCE {
transmissionModeUL-r10 tm1
fourAntennaPortActivated-r10 Not present OP setup
}
pusch-ConfigDedicatedSCell-r10 PUSCH-
ConfigDedicated-
DEFAULT
uplinkPowerControlDedicatedSCell-r10 Not present
cqi-ReportConfigSCell-r10 Not present
SoundingRS-UL- pc_FeatrG
ConfigDedicated-Mod rp_113
SoundingRS-UL- pc_FeatrG
ConfigDedicated-v1020- rp_113
Mod
}
}
}
Table 8.2.2.3.1.3.3-11A: SoundingRS-UL-ConfigDedicated-Mod (Table 8.2.2.3.1.3.3-11)

SoundingRS-UL-ConfigDedicated ::= CHOICE{
setup SEQUENCE {
srs-Bandwidth bw3
srs-HoppingBandwidth hbw3
freqDomainPosition 0
duration TRUE
srs-ConfigIndex 7
transmissionComb 0
cyclicShift cs0
}
}
Table 8.2.2.3.1.3.3-11B: SoundingRS-UL-ConfigDedicated-v1020-Mod (Table 8.2.2.3.1.3.3-11)
Derivation Path: 36.331, clause 6.3.2

SoundingRS-UL-ConfigDedicated-v1020 ::=
SEQUENCE {
srs-AntennaPort-r10 an1
}
ETSI
Derivation path: 36.508 4.6.1 table 4.6.1-5

c1 CHOICE {
measId 1
measResultPCell::= SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultForECID-r9 Not present
locationInfo-r10 Not present
measResultServFreqList-r10 SEQUENCE
(SIZE (1..maxServCell-r10)) OF SEQUENCE {
servFreqId-r10 1
measResultSCell-r10 SEQUENCE { Cell 3
rsrpResultSCell-r10 (0..97)
rsrqResultSCell-r10 (0..34)
}
}
}
}
}
}

c1 CHOICE {
sCellToReleaseList-r10 SEQUENCE (SIZE 1 entry
(1..maxSCell-r10) OF SEQUENCE {
sCellIndex-r10[1] 1 SCell release for
Cell 3
}
sCellToAddModList-r10 Not present
}
}
}
}
}
}
}
8.2.2.3.2 CA / RRC connection reconfiguration / SCell addition/modification/release /

Success / Inter-Band CA
Same as TC 8.2.2.3.1 but applied to Inter-band CA case.
ETSI
Same as TC 8.2.2.3.1 but applied to Inter-band CA case.
Same as test case 8.2.2.3.1 with the following differences:
- Cell 10 is an Inactive SCell according to [18] cl. 6.3.4
Same as test case 8.2.2.3.1 with the following differences:
- CA configuration: Inter-band CA replaces Inter-band Contiguous CA

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
}
}
8.2.2.3.3 CA / RRC connection reconfiguration / SCell addition/ modification/release /

Success / Intra-band non-contiguous CA
- CA configuration Intra-band non-contiguous CA replaces Intra-band Contiguous CA
ETSI
8.2.2.4 CA / RRC connection reconfiguration / SCell SI change / Success

8.2.2.4.1 CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band
Contiguous CA
(1)
with { UE in E-UTRA RRC_CONNECTED state with SCell(s) configured }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including sCellToReleaseList and
sCellToAddModList with the same concerned SCell to release and add, and with the change of the
relevant system information of the configured SCell }
then { UE first releases the concerned SCell and then adds the concerned SCell, configures lower
layers to consider the concerned SCell to be in deactivated state and sends an
}
clauses 5.3.5.3, 5.3.10.3a and 5.3.10.3b.
[TS 36.331, clause 5.2.1.1]
The UE applies the system information acquisition and change monitoring procedures for the PCell only. For an SCell,
E-UTRAN provides, via dedicated signalling, all system information relevant for operation in RRC_CONNECTED
when adding the SCell. Upon change of the relevant system information of a configured SCell, E-UTRAN releases and
subsequently adds the concerned SCell, which may be done with a single RRCConnectionReconfiguration message.
NOTE 2: E-UTRAN may configure via dedicated signalling different parameter values than the ones broadcast in
the concerned SCell.
[TS 36.331, clause 5.3.5.3]
[TS 36.331, clause 5.3.10.3a]
The UE shall:
ETSI
[TS 36.331, clause 5.3.10.3b]
The UE shall:
(SCell addition):
modification):
System Simulator:
- Cell 1 is the PCell, Cell 3 is the SCell to be added.
UE:
None.
Preamble:

U-S Message
containing a sCellToAddModList with Cell 3 as
SCell addition.
message
containing a sCellToReleaseList with a SCell
release and a sCellToAddModList with a SCell
addition for SCell relevant system information
changes, the SCellIndex-r10 in both IEs
indicate the same SCell as configured in step
1.
message?
ETSI

in Tables 8.2.2.4.1.3.3-3, 8.2.2.4.1.3.3-4 and 8.2.2.4.1.3.3-7

c1 CHOICE{
Add Cell 3
}
}
}
}
}
}
}

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
monSCell-r10-f2
catedSCell-r10-f2
}
ETSI

SEQUENCE {
Cell 3
}
ul-CarrierFreq-r10 Same uplink EARFCN as FDD
used for Cell 3
Not present TDD
Cell 3
Not present TDD
}
}
}

SEQUENCE {
antennaInfoUL-r10 Not present
pusch-ConfigDedicatedSCell-r10 Not present
uplinkPowerControlDedicatedSCell-r10 UplinkPowerControlDedic
atedSCell-r10-DEFAULT
cqi-ReportConfigSCell-r10 CQI-ReportConfigSCell-
r10-DEFAULT
}
}
}
ETSI

c1 CHOICE {
Cell 3
}
Add-SIchange Cell 3
}
}
}
}
}
}
}
Table 8.2.2.4.1.3.3-6: SCellToAddMod-r10-f2-Add-SIchange (Table 8.2.2.4.1.3.3-5)

sCellIndex-r10 1
physCellId-r10 Physical Cell Identity of Cell
3
as used for Cell 3
}
monSCell-r10-f2-SIchange
}
ETSI
Table 8.2.2.4.1.3.3-7: RadioResourceConfigCommonSCell-r10-f2-SIchange (Table 8.2.2.4.1.3.3-6)

SEQUENCE {
Cell 3
antennaInfoCommon-r10 SEQUENCE {
}
}
used for Cell 3
Not present TDD
Cell 3
Not present TDD
}
}
}
8.2.2.4.2 CA / RRC connection reconfiguration / SCell SI change / Success / Inter-Band

CA
8.2.2.4.3 CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band

non-contiguous CA
- CA configuration Intra-band non-contiguous CA replaces Intra-band Contiguous CA
8.2.2.5 CA / RRC connection reconfiguration / SCell addition without UL / Success

8.2.2.5.1 CA / RRC connection reconfiguration / SCell addition without UL / Success /
Intra-band Contiguous CA
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with SCell
addition without UL carrier }
then { UE adds the new SCell and sends an RRCConnectionReconfigurationComplete message }
}
ETSI
5.3.10.3b.
[TS 36.331, clause 5.3.5.3]
[TS 36.331, clause 5.3.10.3b]
The UE shall:
(SCell addition):
modification):
System Simulator:
- Cell 1 is the PCell, Cell 3 is the SCell to be added.
UE:
None.
Preamble:
ETSI

U-S Message
containing a sCellToAddModList with SCell
Cell 3 addition without UL carrier.
message?

c1 CHOICE{
Add Cell 3 without UL
carrier
}
}
}
}
}
}
}

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
monSCell-r10-f2
catedSCell-r10-f2
}
ETSI

SEQUENCE {
Cell 3
}
Ul-Configuration-r10 Not present
}

SEQUENCE {
}
}

Inter-band CA

Intra-band non-Contiguous CA
8.2.2.6 RRC connection reconfiguration/ UE Assistance Information

8.2.2.6.1 RRC connection reconfiguration/ UE Assistance Information/power preference
indication setup and release
(1)
with { UE in E-UTRA RRC_CONNECTED state and it is not configured to provide power preference
indications }
ensure that {
when { UE is caused to send UEAssistanceInformation message indicating "lowPowerConsumption" }
then { the UE does not transmit a UEAssistanceInformation message }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and it is configured to provide power preference indications
with T340 set to 0s}
ensure that {
when { UE prefers a configuration primarily optimised for power saving and sends the message
UEAssistanceInformation}
ETSI
then { the UE includes powerPrefIndication set to lowPowerConsumption in the message

UEAssistanceInformation }
}
(3)
and it has previously sent UEAssistanceInformation message indicating "lowPowerConsumption" }
ensure that {
when { UE is caused to send UEAssistanceInformation message indicating "lowPowerConsumption" }
then { the UE does not transmit a UEAssistanceInformation message with powerPrefIndication set
to lowPowerConsumption }
}
(4)
}
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing a otherConfig that includes
the powerPrefIndicationConfig set to Release }
then { the UE does not transmit any more UEAssistanceInformation message }
5.6.10.2, 5.6.10.3 and 6.3.6. Unless otherwise stated these are Rel-11 requirements.
[TS 36.331, clause 5.3.10.9]
The UE shall:
...
1> if the received otherConfig includes the powerPrefIndicationConfig:
2> if powerPrefIndicationConfig is set to setup:
3> consider itself to be configured to provide power preference indications in accordance with 5.6.10;
2> else:
3> consider itself not to be configured to provide power preference indications;
[TS 36.331, clause 5.6.10.2]
A UE capable of providing power preference indications in RRC_CONNECTED may initiate the procedure in several
cases including upon being configured to provide power preference indications and upon change of power preference.
Upon initiating the procedure, the UE shall:
1> if configured to provide power preference indications:
2> if the UE did not transmit a UEAssistanceInformation message since it was configured to provide power
preference indications; or
2> if the current power preference is different from the one indicated in the last transmission of the
UEAssistanceInformation message and timer T340 is not running:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;
[TS 36.331, clause 5.6.10.3]
The UE shall set the contents of the UEAssistanceInformation message:
1> if the UE prefers a configuration primarily optimised for power saving:
2> set powerPrefIndication to lowPowerConsumption;
ETSI
1> else:
2> start or restart timer T340 with the timer value set to the powerPrefIndicationTimer;
2> set powerPrefIndication to normal;
The UE shall submit the UEAssistanceInformation message to lower layers for transmission.
[TS 36.331, clause 6.3.6]

powerPrefIndicationTimer
Prohibit timer for Power Preference Indication reporting. Value in seconds. Value s0 means prohibit timer is set to 0
second or not set, value s0dot5 means prohibit timer is set to 0.5 second, value s1 means prohibit timer is set to 1
second and so on.
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
1 Cause the UE to send - -
UEAssistanceInformation message indicating
"lowPowerConsumption".
(Note 1)
2 Check: Does the UE send a --> UEAssistanceInformation 1 F
UEAssistanceInformation message within the
next 5s?
3 The SS transmits an <-- RRCConnectionReconfiguration
containing a otherConfig includes the
powerPrefIndicationConfig set to Setup
message.
(Note 1)
6 Check: Does the UE transmit a --> UEAssistanceInformation 2 P
UEAssistanceInformation message with
powerPrefIndication set to
lowPowerConsumption?
7 Cause the UE to send
(Note 1)
next 5s?
powerPrefIndicationConfig set to Release.
message
"normal".
(Note 2)
next 5s?
(Note 1)
next 5s?
Note 1: This indication may be triggered with the AT command +CEPPI/+CNMPSD or any alternative way.
Note 2: This indication may be triggered with the AT command +CEPPI or any alternative way.
Table 8.2.2.6.1.3.3-1: RRCConnectionReconfiguration (Steps 3 and 9, Table 8.2.2.6.1.3.2-1)
Derivation Path: 36.508, Table 4.6.1-8, condition OtherConfig
ETSI
Table 8.2.2.6.1.3.3-2: OtherConfig-r9 (step 3, Table 8.2.2.6.1.3.2-1)
Derivation Path: 36.508, Table 4.6.3-28 condition Setup

OtherConfig-r9 SEQUENCE {
PowerPrefIndicationConfig-r11 CHOICE {
setup SEQUENCE {
powerPrefIndicationTimer-r11 s0
}
}
}
Table 8.2.2.6.1.3.3-2: UEAssistanceInformation (Step 6, Table 8.2.2.6.1.3.2-1)
Derivation Path: 36.508, Table 4.6.1-26 condition Low_Power
Table 8.2.2.6.1.3.3-3: OtherConfig-r9 (Step 9, Table 8.2.2.6.1.3.2-3)
Derivation Path: 36.508, Table 4.6.3-28 condition Release
8.2.2.6.2 RRC connection reconfiguration/ UE Assistance Information/power preference

indication release on connection re-establishment
(1)
with { UE in E-UTRA RRC_Connected state & configured to provide power preference indication }
ensure that {
when { RRC Connection re-establishment procedure is initiated }
then { UE shall stop T340 }
}
(2)
with { UE in E-UTRA RRC_Connected state & configured to provide power preference indication }
ensure that {
when { RRC Connection re-establishment procedure is initiated }
then { UE shall release the powerPrefIndicationConfig }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.6.10.1,
5.6.10.2, 5.6.10.3 and 5.3.7.2. Unless otherwise stated these are Rel-11 requirements.
[TS 36.331 clause 5.6.10.1]
UE EUTRAN
RRC connection reconfiguration
UEAssistanceInformation
Figure 5.6.10.1-1: UE Assistance Information
ETSI
The purpose of this procedure is to inform E-UTRAN of the UE’s power saving preference. Upon configuring the UE
to provide power preference indications E-UTRAN may consider that the UE does not prefer a configuration primarily
optimised for power saving until the UE explicitly indicates otherwise.
[TS 36.331 clause 5.6.10.2]
[TS 36.331 clause 5.6.10.3]
1> else:
[TS 36.331 clause 5.3.7.2]
The UE shall only initiate the procedure when AS security has been activated. The UE initiates the procedure when one
of the following conditions is met:
1> upon detecting radio link failure, in accordance with 5.3.11; or
1> upon handover failure, in accordance with 5.3.5.6; or
1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or
1> upon integrity check failure indication from lower layers; or
1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5;
1> suspend all RBs except SRB0;
1> reset MAC;
1> release the SCell(s), if configured, in accordance with 5.3.10.3a;
ETSI
1> release powerPrefIndicationConfig, if configured and stop timer T340, if running;
1> release reportProximityConfig and clear any associated proximity status reporting timer;
1> release obtainLocationConfig, if configured;
1> release idc-Config, if configured;
1> release measSubframePatternPCell, if configured;
1> if connected as an RN and configured with an RN subframe configuration:
2> release the RN subframe configuration;
1> perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];
System Simulator:
- Cell 1 & Cell 3.
- System information combination 2 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA Cell 1.
UE:
- The UE supporting power preference indication.
Preamble:
columns marked "T1", and "T2" are to be applied subsequently. The exact instants on which these values shall be

Cell-specific measurement results for Cell 1 (M1) and
T0 dBm/15kHz -85 -91
RS EPRE Cell 3 (M3) satisfy exit condition for event
A3 (M3 < M1).
T1 dBm/15kHz -85 -79
RS EPRE Cell 3 (M3) satisfy entry condition for
event A3 (M3 > M1).
The power level values are assigned to
Cell-specific satisfy SrxlevCell 3 < 0 such that
T2 dBm/15kHz -85 "Off"
RS EPRE selecting Cell 1 is guaranteed
(NOTE 1).
ETSI

U-S Message
setup intra frequency measurement on Cell 1
& to configure power preference indication.
message on Cell 1.
3 Cause the UE to send - - - -
"lowPowerConsumption". (Note1).
4 UE transmits UEAssistanceInformation --> UEAssistanceInformation - -
message with powerPrefIndication IE set to
lowPowerConsumption.
"normal"(Note2).
6 UE transmits UEAssistanceInformation --> UEAssistanceInformation - -
message with powerPrefIndication IE set to
normal and starts timer T340 with the timer
value set to the powerPrefIndicationTimer.
according to the row "T1" in table 8.2.2.6.2.3.2-
1.
Cell 1 to order the UE to perform intra
frequency handover to Cell 3.
described in step 9 the steps specified in Table
8.2.2.6.2.3.2-3 should take place.
according to the row "T2" in table 8.2.2.6.2.3.2-
1.
11 The UE releases the configured --> RRCConnectionReestablishment - -
powerPrefIndicationConfig, stops timer T340 Request
and transmit an
RRCConnectionReestablishmentRequest
message on Cell 1.
12 The SS transmits an <-- RRCConnectionReestablishment - -
RRCConnectionReestablishment message to
resume SRB1 operation and re-activate
security on Cell 1.
13 The UE transmits an --> RRCConnectionReestablishment - -
message on Cell 1.
15 Check: Does the UE transmit --> UEAssistanceInformation 2 F
UEAssistanceInformation message? (Note 3).
resume existing radio bearer on Cell 1 & to
configure power preference indication.
message on Cell 1.
ETSI
19 Check: Does the UE transmit --> UEAssistanceInformation 1 P

powerPrefIndication IE set to
lowPowerConsumption? (Note 4).
Note 3: This is a negative check for TP2 to make sure that the UE has released the configured
powerPrefIndicationConfig at step 11.
Note 4: The total time to execute step 6 – step 17 should be less than the T340 timer value
powerPrefIndicationTimer configured at step 1 and started at step 6. This is to make sure that timer T340
has been stopped successfully at step 11 and only then UE will initiate UEAssistanceInformation message
with powerPrefIndication IE set to lowPowerConsumption at step 17.

U-S Message
- EXCEPTION: The steps 1 and 2 below are - - - -
repeated for the duration of T304.
1 The UE attempts to perform the intra - - - -
frequency handover using MAC Random
Access Preamble on Cell 3.
2 The SS does not respond. - - - -
Derivation Path: 36.508, Table 4.6.1-8, conditions MEAS & OtherConfig

MeasConfig SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE 1 entry
measObject[1] MeasObjectEUTRA-
GENERIC(f1)
}
reportConfig[1] ReportConfigEUTRA-A3
}
measId[1] 1
}
}
ETSI
Table 8.2.2.6.2.3.3-3: OtherConfig-r9 (Table 8.2.2.6.2.3.3-1)

setup SEQUENCE {
}
}
}
Table 8.2.2.6.2.3.3-4: UEAssistanceInformation (step 4, 15 & 19, Table 8.2.2.6.2.3.2-2)

powerPreferenceIndication-r11 lowPowerConsumption
Table 8.2.2.6.2.3.3-5: UEAssistanceInformation (step 6, Table 8.2.2.6.2.3.2-2)
Derivation Path: 36.508, Table 4.6.1-26 condition Normal

powerPreferenceIndication-r11 normal

c1 CHOICE{
measResults SEQUENCE {
measId 1
measResultPcell SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListEUTRA SEQUENCE (SIZE 1 entry
physCellId[1] PhysicalCellIdentity of
Cell 3
cgi-Info[1] Not present
measResult[1] SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
Table 8.2.2.6.2.3.3-8: MobilityControlInfo (8.2.2.6.2.3.3-7)

Cell 3
}
Table 8.2.2.6.2.3.3-9: RRCConnectionReestablishmentRequest (step 11, Table 8.2.2.6.2.3.2-2)

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
reestablishmentCause handoverFailure
}
}
}
Table 8.2.2.6.2.3.3-10: RRCConnectionReestablishmentComplete (step 13, Table 8.2.2.6.2.3.2-2)

RRCConnectionReestablishmentComplete ::=
SEQUENCE {
rrcConnectionReestablishmentComplete-r8
SEQUENCE {
}
}
}
Derivation Path: 36.508, Table 4.6.1-8 & condition OtherConfig

c1 CHOICE{
dicated-HO
}
}
}
}
ETSI
Table 8.2.2.6.2.3.3-12: OtherConfig-r9 (Table 8.2.2.6.2.3.3-11)
Derivation Path: 36.508, Table 4.6.3-28, condition Setup

setup SEQUENCE {
}
}
}
8.2.2.6.3 RRC connection reconfiguration/ UE Assistance Information/T340 running

(1)
with { UE in E-UTRA RRC_CONNECTED state and T340 is running }
ensure that {
when { UE is caused to send UEAssistanceInformation message }
then { the UE does not transmit a UEAssistanceInformation message }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and the UE has received a new value for
powerPrefIndicationTimer}
ensure that {
when { UE is caused to send UEAssistanceInformation message indicating "lowPowerConsumption" after
T340 expired }
then { the UE does transmits a UEAssistanceInformation message with powerPrefIndication set to
lowPowerConsumption}
}
References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.6.10.2 and
[TS 36.331, clause 5.6.10.2]
[TS 36.331, clause 5.6.10.3]
1> else:
ETSI
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
powerPrefIndicationConfig set to Setup
message.
(Note 1)
4 The UE transmits a UEAssistanceInformation --> UEAssistanceInformation - -
message with powerPrefIndication set to
"normal".
(Note 2)
normal.
The UE starts T340.
7 Before T340 expires, cause the UE to send - -
(Note 1)
UEAssistanceInformation message before
T340 expires?
"lowPowerConsumption" after T340 has
expired.
(Note 1)
powerPrefIndicationConfig set to Setup and a
new value for powerPrefIndicationTimer.
message.
"normal".
(Note 2)
normal.
The UE starts T340.
Start timer T=300s(this is the same value as
the powerPrefIndicationTimer value set in Step
1).
15 After T340 expires but before T expires cause - -
the UE to send UEAssistanceInformation
message indicating "lowPowerConsumption".
(Note 1)
16 Check: Does the UE send a --> UEAssistanceInformation 2 P
ETSI
powerPrefIndication set to
lowPowerConsumption?
Table 8.2.2.6.3.3.3-1: RRCConnectionReconfiguration (Steps 1 and 11 Table 8.2.2.6.3.3.2-1)
Derivation Path: 36.508, Table 4.6.1-8, condition OtherConfig

setup SEQUENCE {
}
}
}
Table 8.2.2.6.3.3.3-3: UEAssistanceInformation (Steps 4 and 10 Table 8.2.2.6.3.3.2-1)
Table 8.2.2.6.3.3.3-4: UEAssistanceInformation (Steps 6 and 14, Table 8.2.2.6.3.3.2-1)
Derivation Path: 36.508, Table 4.6.1-26 condition Normal

setup SEQUENCE {
}
}
}
8.2.2.7 CA / RRC connection reconfiguration / sTAG addition/modification/release /

Success
8.2.2.7.1 CA / RRC connection reconfiguration / sTAG addition/modification/release /
Success / Intra-band Contiguous CA
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing stag-ToAddModList with a
sTAG addition and sCellToAddModList with a SCell addition which is associated with the new sTAG }
then { UE adds the new SCell and associates it with the new sTAG, sends an
}
ETSI
(2)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing stag-ToAddModList with a
sTAG modification }
then { UE modifies the affected sTAG dedicated configurations and sends an
}
(3)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing sCellToReleaseList with a
sCellIndex equalling to one of the current UE SCell configuration and stag-ToReleaseList to release
the empty sTAG after the last SCell is removed from this sTAG }
then { UE releases this SCell and sTAG and sends an RRCConnectionReconfigurationComplete message
}
}
5.3.10.3a, 5.3.10.4 and 6.3.2. Unless otherwise stated these are Rel-11 requirements.
[TS 36.331, clause 5.3.5.3]
1> else:
[TS 36.331, clause 5.3.10.3a]
The UE shall:
[TS 36.331, clause 5.3.10.4]
ETSI
The UE shall:
1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig other than stag-
ToReleaseList and stag-ToAddModList;
1> if the received mac-MainConfig includes the stag-ToReleaseList:
2> for each STAG-Id value included in the stag-ToReleaseList that is part of the current UE configuration:
3> release the STAG indicated by STAG-Id;
1> if the received mac-MainConfig includes the stag-ToAddModList:
2> for each stag-Id value included in stag-ToAddModList that is not part of the current UE configuration (STAG
addition):
3> add the STAG, corresponding to the stag-Id, in accordance with the received timeAlignmentTimerSTAG;
2> for each stag-Id value included in stag-ToAddModList that is part of the current UE configuration (STAG
modification):
3> reconfigure the STAG, corresponding to the stag-Id, in accordance with the received
timeAlignmentTimerSTAG;
[TS 36.331, clause 6.3.2]
MAC-MainConfig field descriptions

…
stag-Id
Indicates the TAG of an SCell, see TS 36.321 [6]. If the field is not configured for an SCell (e.g. absent in MAC-
MainConfigSCell), the SCell is part of the PTAG.
stag-ToAddModList, stag-ToReleaseList
Used to configure one or more STAGs. E-UTRAN ensures that a STAG contains at least one SCell with configured
uplink. If, due to SCell release a reconfiguration would result in an ‘empty’ TAG, E-UTRAN includes release of the
concerned TAG.
Indicates the value of the time alignment timer for an STAG, see TS 36.321 [6].
…
System Simulator:
- Cell 1 is the PCell, Cell3 is the SCell to be added.
- Cell 3 is an Inactive SCell according to [18] cl. 6.3.4.
UE:
None.
Preamble:
ETSI
St Procedure Message Sequence TP Verdi

ct
U-S Message
containing stag-ToAddModList with a sTAG
addition and sCellToAddModList with SCell
Cell 3 addition which is associated with the
added sTAG.
message?
containing a stag-ToAddModList with
timeAlignmentTimerSTAG-r11 modification.
message?
containing an sCellToReleaseList with an
sCellIndex equalling to the Cell 3 cell index in
the current UE configuration and stag-
ToReleaseList-r11 with STAG-Id equalling to
the stag-id with which the Cell 3 is associated.
message?

in Tables 8.2.2.7.1.3.3-7, 8.2.2.7.1.3.3-8 and 8.2.2.7.1.3.3-11
ETSI
Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8, condition SCell_AddMod

c1 CHOICE{
stag-ToAddModList-r11 SEQUENCE (SIZE
stag-Id-r11[1] 1
timeAlignmentTimerSTAG-r11[1] Infinity
}
}
}
Add Cell 3
}
}
}
}
}
}
}

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
monSCell-r10-f2
catedSCell-r10-f2
}
ETSI
Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A, condition UL CA

SEQUENCE {
Cell 3
}
ul-Configuration-r10 SEQUENCE {
used for Cell 3
Not present TDD
ul-Bandwidth-r10 Same uplink system FDD
Cell 3
Not present TDD
}
}
}
Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19AA

SEQUENCE {
SCell-r10-DEFAULT
stag-Id-r11 1
}
}

c1 CHOICE{
stag-ToAddModList-r11 SEQUENCE (SIZE
stag-Id-r11[1] 1
timeAlignmentTimerSTAG-r11[1] sf750
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
stag-ToReleaseList-r11 SEQUENCE (SIZE
stag-Id-r11[1] 1
}
}
Cell 3
}
}
}
}
}
}
}
}

Success / Inter-Band CA

Success / Intra-band non-contiguous CA
8.2.2.8 feICIC/ RRC connection reconfiguration / SIB1 information / Success

(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing SIB1 information with a
change of TAI}
then { UE reads the SIB1 information and sends an RRCConnectionReconfigurationComplete message
followed by TRACKING AREA UPDATE REQUEST message to update the registration of the actual tracking
area }
}
ETSI
References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.2.2.7, and
5.3.5.3. Unless otherwise stated these are Rel-11 requirements
[TS 36.331, clause 5.2.2.7]
1> else:
or
2> else:
FALSE;
[TS 36.331, clause 5.3.5. 3]
1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:
2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;
8.2.2.8.3 Test Description
System Simulator:
- Cell 1
UE:
None.
Preamble:
ETSI

U-S Message
0 The SS stops transmitting SIB1 information on - - - -
Cell 1.
containing SIB1 information.
message?
3 Check: Does UE transmit a TRACKING AREA --> RRC: ULInformationTransfer 1 P
UPDATE REQUEST message to update the NAS: TRACKING AREA UPDATE
registration of the actual tracking area? REQUEST
4 SS responds with TRACKING AREA UPDATE <-- RRC: DLInformationTransfer - -
ACCEPT message. NAS: TRACKING AREA UPDATE
ACCEPT
5 The UE send a TRACKING AREA UPDATE --> RRC: ULInformationTransfer - -
COMPLETE message. NAS: TRACKING AREA UPDATE
COMPLETE
6 The SS resumes transmitting SIB1 information. - - - -

c1 CHOICE{
systemInfomationBlockType1Dedicated-r11 systemInfomationBlockTy
pe1

}
}
}
}
}
}
}
}
Table 8.2.2.8.3.3-2: SystemInformationBlockType1 (Table 8.2.2.8.3.3-1 and step 6, Table 8.2.2.8.3.2-1)
Derivation Path: 36.508 clause 4.4.3.2-3

trackingAreaCode TAC =2
}
}
ETSI
8.2.3 Radio bearer release

8.2.3.1 RRC connection reconfiguration / Radio bearer release / Success
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a drb-ToReleaseList }
then { for each drb-Identity release the PDCP entity and RLC entity and DTCH logical channel
and indicate release of the DRB(s) to upper layers }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.5.3
and 5.3.10.2.
[TS 36.331, clause 5.3.5.3]
1> else:
[TS 36.331, clause 5.3.10.2]
The UE shall:
1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration (DRB
release):
2> release the PDCP entity;
2> release the RLC entity;
2> release the DTCH logical channel;
1> indicate the release of the DRB(s) and the eps-BearerIdentity of the released DRB(s) to upper layers;
System Simulator:
- Cell 1
UE:
None.
ETSI
Preamble:

U-S Message
a drb-ToReleaseList.
message?
2a The UE transmits an ULInformationTransfer --> ULInformationTransfer - -
message.

c1 CHOICE{
DedicatedInfoNAS[1] DEACTIVATE EPS According 36.508
BEARER CONTEXT table 4.7.3-12 and
REQUEST with EPS regular
bearer identity deactivation of a
corresponding to drb- second DRB
Identity 2 and ESM
cause #36
radioResourceConfigDedicated RadioResourceConfigDe Table 8.2.3.1.3.3-
dicated-DRB-RELEASE 2
}
}
}
}
ETSI
Table 8.2.3.1.3.3-2: RadioResourceConfigDedicated-DRB-RELEASE (Table 8.2.3.1.3.3-1)

drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) 1 entry
OF
drb-Identity[1] 2
mac-MainConfig CHOICE { } Not present
}
8.2.4 Handover
8.2.4.1 RRC connection reconfiguration / Handover / Success / Dedicated preamble
(1)
with { UE having completed the radio bearer establishment and initial security activation procedure
and performed the intra frequency measurement}
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo with a
rach-ConfigDedicated }
}
(2)
and performed the intra frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a nextHopChainingCount which
is different from the NCC associated with the currently active KeNB }
then { UE derives new KeNB key from the nextHopChainingCount }
}
(3)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a nextHopChainingCount which
is same as the NCC associated with the currently active KeNB }
then { UE derives new KeNB key from the currently active KeNB }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4,
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;
1> if the carrierFreq is included:
ETSI
2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity
indicated by the targetPhysCellId;
1> else:
2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the
targetPhysCellId;
1> start synchronising to the DL of the target cell;
NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message
triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this
message.
1> reset MAC;
1> re-establish PDCP for all RBs that are established;
NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the
re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling
of the SN and the HFN, is specified in TS 36.323 [8].
1> apply the value of the newUE-Identity as the C-RNTI;
1> configure lower layers in accordance with the received radioResourceConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the
received mobilityControlInfo;
1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:
2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC
procedure, as specified in TS 33.401 [32];
1> else:
2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated
in the securityConfigHO, as specified in TS 33.401 [32];
1> store the nextHopChainingCount value;
1> if the securityAlgorithmConfig is included in the securityConfigHO:
2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];
2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401
[32];
1> else:
2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];
2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS
33.401 [32];
1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection
configuration shall be applied to all subsequent messages received and sent by the UE, including the message
used to indicate the successful completion of the procedure;
ETSI
1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering
1> perform the measurement related actions as specified in 5.5.6.1;
1> if the RRCConnectionReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;
1> if MAC successfully completes the random access procedure:
2> stop timer T304;
2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS
configuration that do not require the UE to know the SFN of the target cell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN
of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding
RS configuration), if any, upon acquiring the SFN of the target cell;
NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it
applies the new configuration, except for the cases addressed by the above statements.
2> the procedure ends;
NOTE 4: The UE is not required to determine the SFN of the target cell by acquiring system information from that
cell before performing RACH access in the target cell.
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
1> if the antennaInfo is included and set to 'explicitValue':
2> if the configured transmissionMode is not 'tm3' or 'tm4' release ri-ConfigIndex in cqi-ReportPeriodic, if
previously configured;
1> else if the antennaInfo is included and set to 'defaultValue':
2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;
System Simulator:
UE:
None.
Preamble:
ETSI
columns marked "T1", "T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be

The power level values are such
that measurement results for
T0 -85 -91 ”Off” Cell 1 (M1) and Cell 4 (M4)
EPRE Hz
satisfy exit condition for event
A3 (M4 < M1)(NOTE 1).
T1 -85 -79 ”Off” Cell 1 (M1) and Cell 4 (M4)
EPRE Hz
satisfy entry condition for event
A3 (M4 > M1)(NOTE 1).
T2 -85 -91 "Off" Cell 1 (M1) and Cell 4 (M4)
EPRE Hz
A3 (M1 > M4)(NOTE 1).
The power level value are such
T3 -85 “Off” -79 Cell 1 (M1) and Cell 11 (M11)
EPRE Hz
A3 (M11 > M1).
ETSI

U-S Message
setup intra frequency measurement on Cell 1.
message on Cell 1.
parameters according to the row "T1" in table
8.2.4.1.3.2-1.
message to report event A3 on Cell 1 with the
handover to Cell 4.
6 Check: Does the UE transmit an --> RRCConnectionReconfigurationC 1,3 P
message on Cell 4 using dedicated preamble
to confirm the successful completion of the
intra frequency handover?
Check2: Does the UE transmit an
using the security key derived from the
currently active KeNB?
8.2.4.1.3.2-1.
handover to Cell 1.
nextHopChainingCount?
11 The SS changes Cell 1 and Cell 11 - - - -
parameters and switches Cell 4 off according
measured RSRP,RSRQ value for Cell 11.
handover to Cell 11.
nextHopChainingCount?
14A The UE transmit a TRACKING AREA UPDATE - - - -
ETSI
REQUEST message on Cell 11.

14B SS responds with a TRACKING AREA - - - -
UPDATE ACCEPT message.
14C The UE transmits a TRACKING AREA - - - -

UPDATE COMPLETE message.
Derivation Path: 36.508, Table 4.6.1-8, condition MEAS
Table 8.2.4.1.3.3-2: MeasConfig (Table 8.2.4.1.3.3-1)

GENERIC(f1)
}
}
measId[1] 1
}
}
ETSI
Table 8.2.4.1.3.3-3: MeasurementReport (step 4, Table 8.2.4.1.3.2-2)

c1 CHOICE{
measId 1
measResultServCell SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 4
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.2.4.1.3.3-5: MobilityControlInfo (Table 8.2.4.1.3.3-4)

Cell 4
ra-PreambleIndex 63
ra-PRACH-MaskIndex 0
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 1
ra-PreambleIndex 63 -
}
}
Table 8.2.4.1.3.3-9: SecurityConfigHO (step 9, Table 8.2.4.1.3.2-2)

SecurityConfigHO ::= SEQUENCE {
handoverType CHOICE {
intraLTE SEQUENCE {
nextHopChainingCount 2
}
}
}
ETSI

c1 CHOICE{
measuredResults SEQUENCE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 11
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 11
ra-PreambleIndex 63
}
}
ETSI
Table 8.2.4.1.3.3-13: SecurityConfigHO (Table 8.2.4.1.3.3-11)

intraLTE SEQUENCE {
}
}
}
8.2.4.2 RRC connection reconfiguration / Handover / Success / Common preamble

(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo without
a rach-ConfigDedicated }
}
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
1> else:
[32];
1> else:
33.401 [32];
2> stop timer T304;
...
ETSI
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
UE:
None.
Preamble:

T0 -85 -91
A3 (M2 < M1).
T1 -85 -79
A3 (M2 > M1).
ETSI

U-S Message
message on Cell 1.
message on Cell 2 using common preamble to
confirm the successful completion of the intra
frequency handover?

GENERIC(f1)
}
}
measId[1] 1
}
}
ETSI
Table 8.2.4.2.3.3-3 MeasurementReport (step 4, Table 8.2.4.2.3.2-2)

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 2
}
8.2.4.3 RRC connection reconfiguration / Handover / Success / Intra-cell / Security

reconfiguration
(1)
}
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a securityConfigHO }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4.
ETSI
[TS 36.331, clause 5.3.5.4]
2> consider the target cell to be one on the frequency indicated by the eutra-CarrierFreq with a physical cell
identity indicated by the targetPhysCellId;
1> else:
targetPhysCellId;
message.
1> reset MAC;
1> apply the value of the newUE-Identity; as the C-RNTI
2> update the KeNB key based on the KASME key taken into use with the previous successful NAS SMC
1> else:
2> update the KeNB key based on the KASME key to which the current KeNB is associated, using the
nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];
[32];
1> else:
33.401 [32];
ETSI
2> stop timer T304;
2> apply the parts of the configuration that do not require the UE to know the SFN of the target cell;
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
ETSI

U-S Message
1 The SS transmits an AUTHENTICATION <-- DLInformationTransfer - -
REQUEST message to initiate the EPS
authentication and AKA procedure.
2 The UE transmits an AUTHENTICATION --> ULInformationTransfer - -
RESPONSE message and re-establishes
mutual authentication.
3 The SS transmits a NAS SECURITY MODE <-- DLInformationTransfer - -
COMMAND message to reactivate NAS
security.
4 The UE transmits a NAS SECURITY MODE --> ULInformationTransfer - -
COMPLETE message and re-establishes the
security configuration.
perform intra cell handover and security
reconfiguration.
message using the security key indicated by
the keyChangeIndicator and
nextHopChainingCount, as well as the
indicated algorithms, to confirm the successful
completion of the intra cell handover and
security reconfiguration?

Cell 1
}

intraLTE SEQUENCE {
keyChangeIndicator TRUE
}
}
}
ETSI
8.2.4.4 RRC connection reconfiguration / Handover / Failure / Intra-cell / Security

reconfiguration
(1)
and after receiving an RRCConnectionReconfiguration message including a SecurityConfigHO }
ensure that {
when { UE detects handover failure and the initial cell is selectable }
then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA
RRC_CONNECTED state }
}
5.3.5.4, 5.3.5.6, 5.3.7.4 and 5.3.7.5.
[TS 36.331, clause 5.3.5.3]
2> re-establish PDCP for SRB2 and for all DRBs that are established, if any;
2> re-establish RLC for SRB2 and for all DRBs that are established, if any;
2> resume SRB2 and all DRBs that are suspended, if any;
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
ETSI
1> reset MAC;
1> else:
[32];
1> else:
33.401 [32];
2> stop timer T304;
ETSI
[TS 36.331, clause 5.3.5.6]
The UE shall:
1> if T304 expires (handover failure):
NOTE: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not
available for use by the UE anymore.
2> revert back to the configuration used in the source cell, excluding the configuration configured by the
physicalConfigDedicated, the mac-MainConfig and the sps-Config;
2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection
reconfiguration procedure ends;
[TS 36.331, clause 5.3.7.4]
The UE shall set the contents of RRCConnectionReestablishmentRequest message as follows:
2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used
in the cell in which the trigger for the re-establishment occurred (other cases);
2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA
failure) or of the cell in which the trigger for the re-establishment occurred (other cases);
2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:
3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;
3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and
mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other
cases); and
3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;
1> set the reestablishmentCause as follows:
2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is
unable to comply with the reconfiguration):
3> set the reestablishmentCause to the value 'reconfigurationFailure';
2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE
handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):
3> set the reestablishmentCause to the value 'handoverFailure';
2> else:
3> set the reestablishmentCause to the value 'otherFailure';
The UE shall submit the RRCConnectionReestablishmentRequest message to lower layers for transmission.
ETSI
[TS 36.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
1> re-establish PDCP for SRB1;
1> re-establish RLC for SRB1;
1> resume SRB1;
nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS
33.401 [32];
1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401
[32];
1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as
specified in TS 33.401 [32];
1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint
key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the
UE, including the message used to indicate the successful completion of the procedure;
1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the
KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE,
including the message used to indicate the successful completion of the procedure;
1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the
procedure ends;
System Simulator:
- Cell 1.
UE:
None.
Preamble:
ETSI

U-S Message
perform intra cell handover and security
reconfiguration.
8.2.4.4.3.2-2 should take place.
2 Wait for 1 s to ensure that T304 expires. - - - -
3 Check: Does the UE transmit an --> RRCConnectionReestablishment 1 P
message?
resume SRB1 operation and reactivate
security.
message.
resume the existing radio bearer.
message.
indicates that the UE is in E-UTRA

U-S Message
1 The UE attempts to perform the intra cell - - - -
handover using MAC Random Access
Preamble.

Cell 1
}
ETSI

intraLTE SEQUENCE {
}
}
}

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}

c1 CHOICE{
dicated-HO
}
}
}
}
8.2.4.5 RRC connection reconfiguration / Handover / All parameters included

(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo is
provided with all parameters included }
}
ETSI
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
1> else:
ETSI
[32];
1> else:
33.401 [32];
2> stop timer T304;
...
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
ETSI
System Simulator:
UE:
None.
Preamble:

T0 -85 -91
A3 (M2 < M1).
T1 -85 -79
A3 (M2 > M1).

U-S Message
message on Cell 1 to confirm the setup of intra
frequency measurement.
measured RSRP and RSRQ values for Cell 2.
message on Cell 2 to confirm the successful
completion of the intra frequency handover?
ETSI

GENERIC(f1)
}
}
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

Cell 2
carrierFreq SEQUENCE {
dl-CarrierFreq Same downlink EARFCN
as used for Cell 2
ul-CarrierFreq Same uplink EARFCN as FDD
used for Cell 2
ul-CarrierFreq Not present TDD
}
carrierBandwidth SEQUENCE {
dl-Bandwidth Same downlink system
Cell 2
ul-Bandwidth Same uplink system FDD
Cell 2
ul-Bandwidth Not present TDD
}
additionalSpectrumEmission Same
additionalSpectrumEmis
sion as used for Cell 2
t304 ms1000
newUE-Identity SS arbitrarily selects a
value between ‘003C’H
and ‘FFF2’H.
rach-ConfigCommon RACH-ConfigCommon-
DEFAULT
prach-Config PRACH-Config-
DEFAULT
pdsch-ConfigCommon PDSCH-ConfigCommon-
DEFAULT
pusch-ConfiCommon PUSCH-ConfigCommon-
DEFAULT
phich-Config PHICH-Config-DEFAULT
pucch-ConfigCommon PUCCH-ConfigCommon-
DEFAULT
soundingRS-UL-ConfigCommon SoundingRsUl-
ConfigCommon-
DEFAULT
uplinkPowerControlCommon UplinkPowerControlCom
mon-DEFAULT
antennaInfoCommon SEQUENCE {
}
p-Max Not present
tdd-Config Not present FDD
TDD-Config-DEFAULT TDD
}
rach-ConfigDedicated Not present
}
ETSI
8.2.4.6 RRC connection reconfiguration / Handover / Success / Inter-frequency

(1)
and performed the inter frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo
indicating a different E-UTRA frequency}
}
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
1> else:
[32];
1> else:
33.401 [32];
2> stop timer T304;
...
[TS 36.331, clause 5.3.10.4]
The UE shall:
ETSI
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
UE:
None.
Preamble:

T0 -85 -97
A3 (M3 < M1).
T1 -85 -73
A3 (M3 > M1).
ETSI

U-S Message
Cell 1 to setup inter frequency measurement.
message on Cell 1.
Cell 1 to order the UE to perform inter
completion of the inter frequency handover?
Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

GENERIC(f1)
GENERIC(f2)
}
}
measId[1] 1
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 3
as used for Cell 3
ul-CarrierFreq Not present
}
}
8.2.4.7 RRC connection reconfiguration / Handover / Failure / Re-establishment

successful
(1)
and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo
indicating a different E-UTRA cell having attempted intra frequency handover }
ensure that {
when { UE detects handover failure and the initial cell is selectable }
ETSI
(2)
with { UE having transmitted an RRCConnectionReestablishmentRequest message }
ensure that {
when { UE receives an RRCConnectionReestablishment message with a nextHopChainingCount which is
different from the NCC associated with the currently active KeNB }
then { UE derives new KeNB from the nextHopChainingCount }
}
(3)
with { UE having transmitted an RRCConnectionReestablishmentRequest message }
ensure that {
same as the NCC associated with the currently active KeNB }
then { UE derives new KeNB from the currently active KeNB }
}
5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
1> else:
[32];
1> else:
33.401 [32];
2> stop timer T304;
...
[TS 36.331, clause 5.3.5.6]
The UE shall:
ETSI
[TS 36.331, clause 5.3.7.2]
...
...
1> reset MAC;
[TS 36.331, clause 5.3.7.4]
cases); and
ETSI
...
[TS 36.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
1> resume SRB1;
33.401 [32];
[32];
procedure ends;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
ETSI
System Simulator:
UE:
None.
Preamble:
columns marked "T1", "T2", "T3", "T4", "T5" and "T6" are to be applied subsequently. The exact instants on which
these values shall be applied are described in the texts in this clause.

measurement results for Cell 1 (M1) Cell
Cell-specific
T0 dBm/15kHz -85 -91 -91 4 (M4) and Cell 11(M11) satisfy exit
RS EPRE
condition for event A3 (M4 < M1 and M11
< M1).
T1 dBm/15kHz -85 -79 -91
event A3 (M4 > M1).
satisfy SrxlevCell 1 < 0 and SrxlevCell 11
Cell-specific
T2 dBm/15kHz "Off" -79 "Off" < 0 such that selecting Cell 4 is
RS EPRE
guaranteed
(NOTE 1).
measurement results for Cell 1 (M1) and
Cell-specific
T3 dBm/15kHz -73 -79 "Off" Cell 4 (M4) satisfy entry condition for
RS EPRE
event A3 (M1> M4).
(NOTE 1).
satisfy SrxlevCell 4 < 0 and SrxlevCell 11
Cell-specific
T4 dBm/15kHz -73 "Off" "Off" < 0 such that selecting Cell 1 is
RS EPRE
guaranteed.
(NOTE 1).
Cell-specific
T5 dBm/15kHz -73 "Off" -67 Cell 11 (M11) satisfy entry condition for
RS EPRE
event A3 (M11> M1).
(NOTE 1).
satisfy SrxlevCell 1 < 0 and SrxlevCell 4 <
Cell-specific
T6 dBm/15kHz "Off" "Off" -67 0 such that selecting Cell 11 is
RS EPRE
guaranteed.
(NOTE 1).
ETSI

U-S Message
message on Cell 1.
8.2.4.7.3.2-1.
8.2.4.7.3.2-1.
message on Cell 4?
security on Cell 4.
message using the security key derived from
the currently active KeNB on Cell 4?
resume existing radio bearer on Cell 4.
11 The UE transmits an --> RRCConnectionReconfigurationtC - -
message on Cell 4.
8.2.4.7.3.2-1.
described in step 15 the steps specified in
8.2.4.7.3.2-1.
message on Cell 1?
security on Cell 1.
ETSI
the nextHopChainingCount on Cell 1?
message on Cell 1.
8.2.4.7.3.2-1.
8.2.4.7.3.2-1.
message on Cell 11?
security on Cell 11.
message on Cell 11.
29A The UE transmit a TRACKING AREA UPDATE - - - -
REQUEST message on Cell 11.
29B SS responds with TRACKING AREA UPDATE - - - -
ACCEPT message.
UPDATE COMPLETE.

U-S Message
ETSI

U-S Message

U-S Message
Table 8.2.4.7.3.3-0: SystemInformationBlockType2 for Cell 1, cell 4 and Cell 11 (preamble and all the
steps in Table 8.2.4.7.3.2-2)

ra-SupervisionInfo SEQUENCE {
preambleTransMax n50
}

GENERIC(f1)
}
}
measId[1] 1
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 4
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 4
ra-PreambleIndex 63
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}
Table 8.2.4.7.3.3-7: RRCConnectionReestablishment (step 8, Table 8.2.4.7.3.2-2)

RRCConnectionReestablishment ::= SEQUENCE {
c1 CHOICE{
rrcConnectionReestablishment-r8 SEQUENCE {
}
}
}
}
Table 8.2.4.7.3.3-8: RRCConnectionReconfiguration (step 10, step 19 and step 28, Table 8.2.4.7.3.2-2)

c1 CHOICE{
dicated-HO
}
}
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 1
ra-PreambleIndex 63
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 4
the XMAC-I value
calculated by SS.
}
}
}
}

c1 CHOICE{
}
}
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 11
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 11
ra-PreambleIndex 63
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}

c1 CHOICE{
}
}
}
}

failure
(1)
and after receiving an RRCConnectionReconfiguration message including an IE
mobilityControlInformation indicating a different E-UTRA cell having attempted intra frequency
handover }
ensure that {
when { UE detects handover failure and fails an RRC connection re-establishment procedure }
then { UE enters the E-UTRA RRC_IDLE state and trigger TAU procedure in order to recover RRC
connection }
}
5.3.5.6, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.7 and 5.3.12.
[TS 36.331, clause 5.3.5.4]
...
If the RRCConnectionReconfiguration message includes the mobilityControlInformation and the UE is able to comply
ETSI
1> start timer T304 with the timer value set to t304, as included in the mobilityControlInformation;
1> request PDCP to initiate the PDCP Re-establishment procedure for all RBs that are established;
NOTE 2: The handling of the radio bearers after the successful completion of the L2 re-establishment, e.g. the re-
transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of
the SN and the HFN, is specified in [8].
1> reset MAC and re-establish RLC for all RBs that are established;
1> If the RRCConnectionReconfiguration message includes the radioResourceConfiguration:
2> perform the Radio resource configuration procedure as specified in 5.3.10;
1> set the C-RNTI to the value of the newUE-Identity;
1> if the eutra-CarrierFreq is included:
identity indicated by the targetCellIdentity;
1> else:
targetCellIdentity;
1> if the dl-Bandwidth is included:
2> for the target cell, apply the downlink bandwidth indicated by the dl-Bandwidth;
1> else:
2> for the target cell, apply the same downlink bandwidth as for the current cell;
1> if the ul-Bandwidth is included:
2> for the target cell, apply the uplink bandwidth indicated by the ul-Bandwidth;
1> else:
2> for the target cell, apply the same uplink bandwidth as for the current cell;
1> If the RRCConnectionReconfiguration message includes the securityConfiguration:
2> apply the AS-derived keys associated with the AS-base key indicated by the keyIndicator;
2> configure lower layers to apply the indicated integrity protection algorithm, i.e. the indicated integrity
protection configuration shall be applied to all subsequent messages received and sent by the UE in the target
cell, including the message used to indicate the successful completion of the procedure;
2> configure lower layers to apply the indicated ciphering algorithm, i.e. the indicated ciphering configuration
shall be applied to all subsequent messages received and sent by the UE in the target cell, including the
message used to indicate the successful completion of the procedure;
1> If the RRCConnectionReconfiguration message includes the measurementConfiguration:
2> perform the Measurement configuration procedure as specified in 5.5.2;
1> synchronise to the DL of the target cell;
configuration;
1> If MAC successfully completes the random access procedure:
ETSI
2> stop timer T304;
2> If the physicalConfigDedicated is included in the RRCConnectionReconfiguration message:
3> If the UE needs the SFN of the target cell to apply the PUCCH and Sounding RS configuration:
4> apply the new PUCCH and Sounding RS configuration upon acquiring the SFN of the target cell;
3> else:
4> apply the new PUCCH and Sounding RS configuration;
2> indicate to PDCP to complete the PDCP Re-establishment procedure for all DRBs that are established, if any;
2> the procedure ends.
...
[TS 36.331, clause 5.3.5.6]
The UE shall:
1> If T304 expires (handover failure):
NOTE 1: Following T304 expiry dedicated preambles, if provided within the rach-ConfigDedicated, are not
2> revert back to the configuration used in the source cell, excluding the physical layer configuration;
NOTE 2: The UE reverts to the RRC configuration as well as the layer 2 configuration (PDCP/RLC/MAC) used in
the source cell.
reconfiguration procedure ends.
[TS 36.331, clause 5.3.7.2]
The UE shall only initiate the procedure when security has been activated. The UE initiates the procedure when one of
the following conditions is met:
...
...
...
transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and
the HFN, is specified in [8].
1> select a suitable cell in accordance with the cell selection process as specified in [4];
[TS 36.331, clause 5.3.7.3]
...
2> initiate transmission of the RRCConnectionReestablishmentRequest message in accordance with 5.3.7.4;
ETSI
...
[TS 36.331, clause 5.3.7.4]
2> set the c-RNTI to the C-RNTI used in the source cell (handover failure case) or used in the cell in which the
trigger for the re-establishment occurred (other cases);
2> set the cellIdentity to the Physical layer identity of the source cell (handover failure case) or of the cell in
which the trigger for the re-establishment occurred (other cases);
3> over the concatenation of the ASN.1 encoded CellIdentity of the current cell, PhysicalCellIdentity of the
cell the UE was connected to prior to the failure and C-RNTI that the UE had in the cell it was connected
to prior to the failure;
3> with the integrity protection key and integrity protection algorithm that was used in the cell the UE was
connected to prior to the failure; and
3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones.
1> set the IE reestablishmentCause as follows:
...
3> set the reestablishmentCause to the value ‘handoverFailure’;
...
[TS 36.331, clause 5.3.7.7]
Upon T311 expiry, the UE shall:
1> perform the actions upon moving from RRC_CONNECTED to RRC_IDLE as specified in 5.3.12.
...
[TS 36.331, clause 5.3.12]
Upon moving from RRC_CONNECTED to RRC_IDLE, the UE shall:
...
1> release all radio resources, including release of the RLC entity and the associated PDCP entity for all established
RBs;
1> indicate the release of the RRC connection to upper layers;
1> enter RRC_IDLE.
ETSI
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:

T0 Cell- dBm/15 -85 -91 The power level values are such that measurement
specific RS kHz results for Cell 1 (M1) and Cell 2 (M2) satisfy entry
EPRE condition for event A3 (M1 > M2)
T2 Cell- dBm/15 -85 "Off" The power level values are such that SrxlevCell 1 >
specific RS kHz SrxlevCell 2 and SrxlevCell 2 <0.(NOTE 1).
EPRE
ETSI

U-S Message
message on Cell 1.
measured RSRP and RSRQ value for Cell 2.
message on Cell 1.
8 The SS does not respond to any - - - -
message and waits for 1s to ensure that T301
expires and the UE goes to RRC_IDLE state
on Cell 1.
9- The UE will perform TAU procedure based on - - - -
13 steps 1 to 5 of subclause 6.4.2.7 in TS 36.508
on Cell 1.
NOTE: The UE performs a TAU procedure due
to NAS signalling connection recovery.

U-S Message
repeated for the duration of T304
Access Preamble on Cell 2
Derivation path: 36.508 Table 4.6.1-8, condition MEAS
ETSI
Table 8.2.4.8.3.3-1A: MeasConfig (Table 8.2.4.8.3.3-1)

GENERIC(f1)
}
}
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Derivation path: 36.508 Table 4.6.1-8, condition HO
ETSI
Table 8.2.4.8.3.3-3A: MobilityControlInfo (Table 8.2.4.8.3.3-4)

Cell 2
}
Table 8.2.4.8.3.3-4: Void

SEQUENCE {
SEQUENCE {
c-RNTI The value of the C-RNTI
of the UE.
Cell 1
the XMAC-I value
calculated by SS
}
}
}
}
8.2.4.9 RRC connection reconfiguration / Handover / Inter-band blind handover /

Success
(1)
}
ensure that {
indicating an E-UTRA frequency on different frequency band }
}
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
ETSI
1> else:
targetPhysCellId;
message.
1> reset MAC;
...
1> else:
[32];
1> else:
33.401 [32];
ETSI
2> stop timer T304;
...
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
UE:
None.
Preamble:
ETSI

U-S Message
Cell 1 to order the UE to perform inter band
message on Cell 10?

Cell 10
as used for Cell 10
}
}
8.2.4.10 RRC connection reconfiguration / Handover (between FDD and TDD)

(1)
in FDD mode}
ensure that {
when { UE receives an RRCConnectionReconfiguration message including an IE
mobilityControlInformation with TDD configuration parameters included }
}
(2)
in TDD mode}
ensure that {
when { UE receives an RRCConnectionReconfiguration message including an IE
mobilityControlInformation with FDD configuration parameters included }
}
ETSI
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
1> else:
ETSI
[32];
1> else:
33.401 [32];
2> stop timer T304;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
ETSI
System Simulator:
- Cell 1 in FDD and Cell 10 in TDD
UE:
None.
Preamble:

U-S Message
including TDD-Config to order the UE to
perform inter band handover to Cell 10.
message on Cell 10?
without including TDD-Config to order the UE
to perform inter band handover to Cell 1.
message on Cell 1?
ETSI

MobilityControlInfo-HO ::= SEQUENCE {
targetPhysCellId PhysicalCellIdentity of Cell 10
dl-CarrierFreq Same downlink EARFCN as used
for Cell 10
}
dl-Bandwidth Same downlink system bandwidth
as used for Cell 10
ul-Bandwidth Not present
}
additionalSpectrumEmission as
used for Cell 10
radioResourceConfigCommon RadioResourceConfigCommon-
withTDDconfig
}
Table 8.2.4.10.3.3-2A: RadioResourceConfigCommon-withTDDconfig (Table 8.2.4.10.3.3-2)

RadioResourceConfigCommon-DEFAULT
::= SEQUENCE {
tdd-Config TDD-Config-DEFAULT
}

targetPhysCellId PhysicalCellIdentity of Cell 1
dl-CarrierFreq Same downlink EARFCN as used
for Cell 1
ul-CarrierFreq Same uplink EARFCN as used for
Cell 1
}
dl-Bandwidth Same downlink system bandwidth
as used for Cell 1
ul-Bandwidth Same uplink system bandwidth as
used for Cell 1
}
additionalSpectrumEmission as
used for Cell 1
radioResourceConfigCommon RadioResourceConfigCommon-
withoutTDDconfig
}
ETSI
Table 8.2.4.10.3.3-5: RadioResourceConfigCommon-withoutTDDconfig (Table 8.2.4.10.3.3-4)

RadioResourceConfigCommon-DEFAULT
::= SEQUENCE {
tdd-Config Not present
}
8.2.4.11 Void
8.2.4.12 RRC connection reconfiguration / Handover / Setup and release of MIMO
(1)
}
ensure that {
indicating a cell with 2 antenna ports }
}
(2)
}
ensure that {
indicating a cell with 1 antenna port }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.4
and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
of the SN and the HFN, is specified in TS 36.323.
1> else:
1> else:
33.401 [32];
2> stop timer T304;
ETSI
[TS 36.331, clause 5.3.10.6]
The UE shall:
2> if the configured transmissionMode is not 'tm3' or 'tm4' or 'tm8':
2> if the configured transmissionMode is 'tm8' and pmi-RI-Report is not present:
System Simulator:
- Cell 1 and Cell 2 (2 antenna ports MIMO)
UE:
None.
Preamble:

T0 -91 -85
EPRE Hz
T1 -85 -91
EPRE Hz
ETSI

U-S Message
handover to Cell 2.
message on Cell 2?
3A The SS changes Cell 1 and Cell 2 parameters - - - -
0.
handover to Cell 1.
message on Cell 1?

Cell 2
radioResourceConfigCommon RadioResourceConfigCo
mmon-DEFAULT
}
Table 8.2.4.12.3.3-3: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.12.3.3-2)
Derivation Path: 36.508, Table 4.6.3-13, condition 2TX
ETSI

Cell 1
radioResourceConfigCommon RadioResourceConfigCo
mmon-DEFAULT
}
Table 8.2.4.12.3.3-6: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.12.3.3-5)

antennaInfoCommon SEQUENCE {
}
8.2.4.13 RRC connection reconfiguration / Handover / Success (with measurement) /

Inter-band
(1)
and performed the inter-band measurement }
ensure that {
indicating an E-UTRA frequency on different frequency band }
}
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
ETSI
1> reset MAC;
1> if the RRCConnectionReconfiguration message includes the fullConfig:
2> perform the radio configuration procedure as specified in section 5.3.5.8;
1> else:
[32];
1> else:
33.401 [32];
1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:
ETSI
2> perform the proximity indication in accordance with the received reportProximityConfig;
2> stop timer T304;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
UE:
None.
Preamble:
ETSI

T0 -85 -97
EPRE Hz Cell 10 (M10) satisfy exit condition for
event A3 (M10 < M1).
T1 -85 -73
EPRE Hz Cell 10 (M10) satisfy entry condition for
event A3 (M10 > M1).

U-S Message
Cell 1 to setup inter-band measurement.
message on Cell 1.
8.2.4.13.3.2-1.
Cell 1 to order the UE to perform inter-band
completion of the inter-band handover?
ETSI

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
additionalSI-Info-r9 Not present
}
}
}
}
}
}
}
}
ETSI

Cell 10
as used for Cell 10
}
}
8.2.4.13a RRC connection reconfiguration / Handover / Success (with measurement) /

Inter-band / Between FDD and TDD
(1)
with { UE in E-UTRA FDD RRC_CONNECTED state and having completed the radio bearer establishment and
initial security activation procedure and performed the inter band LTE TDD measurement }
ensure that {
indicating a different E-UTRA TDD frequency }
}
(2)
with { UE in E-UTRA TDD RRC_CONNECTED state and having completed the radio bearer establishment and
initial security activation procedure and performed the inter band LTE FDD measurement }
ensure that {
indicating a different E-UTRA FDD frequency }
}
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
ETSI
message.
1> reset MAC;
1> else:
[32];
1> else:
33.401 [32];
ETSI
2> stop timer T304;
...
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
- Cell 1 is FDD cell and Cell 28 is TDD cell.
8.2.4.13a.3.1-1.
Cell PLMN name

1 PLMN1
28 PLMN2
UTRA cells.
UE:
None.
ETSI
Preamble:
8.2.4.13a.3.3-9.

T0 -85 -97
RS EPRE Hz and Cell 28 (M28) satisfy exit condition
for event A3 (M28 < M1).
T1 -85 -73
RS EPRE Hz and Cell 28 (M28) satisfy entry
condition for event A3 (M28 > M1).
T2 -73 -85
RS EPRE Hz and Cell 28 (M28) satisfy entry
ETSI

U-S Message
Cell 1 to setup inter band measurement.
message on Cell 1.
measured RSRP, RSRQ values for Cell 28.
completion of the inter band handover?
6A The UE transmits a TRACKING AREA - - - -
UPDATE REQUEST message on Cell 28.
listed as an Equivalent PLMN.
Cell 28 to setup inter band measurement.
message on Cell 28.
10 The SS changes Cell 1 and Cell 28 power - - - -
8.2.4.13a.3.2-1.
measured RSRP, RSRQ values for Cell 1.
handover to Cell 1.
completion of the inter band handover?
listed as an Equivalent PLMN.
ETSI
Table 8.2.4.13a.3.3-1: RRCConnectionReconfiguration (step 1 and step 8, Table 8.2.4.13a.3.2-2)
Table 8.2.4.13a.3.3-2: MeasConfig (step 1, Table 8.2.4.13a.3.3-1)

GENERIC(f1)
GENERIC(f6)
}
}
measId[1] 1
}
}
ETSI
Table 8.2.4.13a.3.3-3: MeasurementReport (step 4, Table 8.2.4.13a.3.2-2)

c1 CHOICE{
measId 1
measResultServCell SEQUENCE { Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 28
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.2.4.13a.3.3-5: MobilityControlInfo (step 5, Table 8.2.4.13a.3.3-4)

Cell 28
as used for Cell 28
}
}
ETSI

GENERIC(f6)
GENERIC(f1)
}
}
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

Cell 1
as used for Cell 1
}
}

Table 8.2.4.13a.3.3-10: TRACKING AREA UPDATE ACCEPT for Cell 28 (step 6B, Table 8.2.4.13a.3.2-2)



successful / Inter-band
(1)
indicating a different E-UTRA cell having attempted inter-band handover }
ensure that {
when { UE detects handover failure and the target cell is selectable }
}
5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
ETSI
1> else:
targetPhysCellId;
message.
1> reset MAC;
1> else:
[32];
1> else:
33.401 [32];
ETSI
2> stop timer T304;
[TS 36.331, clause 5.3.5.6]
The UE shall:
NOTE 4: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not
2> store the following handover failure information in VarRLF-Report by setting its fields as follows:
3> clear the information included in VarRLF-Report, if any;
3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);
3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the PCell based on
measurements collected up to the moment the UE detected handover failure;
[TS 36.331, clause 5.3.7.2]
...
...
ETSI
1> reset MAC;
[TS 36.331, clause 5.3.7.4]
cases); and
...
[TS 36.331, clause 5.3.7.5]
NOTE 5: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];
The UE shall:
1> stop timer T301;
ETSI
1> resume SRB1;
NOTE 6: E-UTRAN should not transmit any message on SRB1 prior to receiving the
RRCConnectionReestablishmentComplete message.
33.401 [32];
[32];
1> set the content of RRCConnectionReestablishmentComplete message as follows:
2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the
RPLMN is included in plmn-IdentityList stored in VarRLF-Report:
3> include the rlf-InfoAvailable;
1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;
procedure ends;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
ETSI
System Simulator:
UE:
None.
Preamble:
columns marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be

T0 dBm/15kHz -85 -91
RS EPRE Cell 10 (M10) satisfy exit condition for
T1 dBm/15kHz -85 -79
T2 dBm/15kHz "Off" -79
(NOTE 1).
ETSI

U-S Message
setup inter-band measurement on Cell 1.
message on Cell 1.
8.2.4.14.3.2-1.
8.2.4.14.3.2-1.
message on Cell 10?
message on Cell 10.
message on Cell 10.

U-S Message
1 The UE attempts to perform the inter-band - - - -
Preamble on Cell 10.
ETSI
Table 8.2.4.14.3.3-1: SystemInformationBlockType2 for Cell 10 (preamble and all the steps in Table
8.2.4.14.3.2-2)

rach-ConfigCommon SEQUENCE {
}
}
}
ssac-BarringForMMTEL-Voice-r9 Not present
ssac-BarringForMMTEL-Video-r9 Not present
}

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 10
as used for Cell 10
}
ra-PreambleIndex 63
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}
Table 8.2.4.14.3.3-8: RRCConnectionReestablishmentComplete (step 9, Table 8.2.4.14.3.2-2)

SEQUENCE {
rrcConnectionReestablishmentComplete-r8
SEQUENCE {
nonCriticalExtension SEQUENCE {} Not present Rel-8
nonCriticalExtension SEQUENCE {} Not checked Rel-9
nonCriticalExtension SEQUENCE { Rel-10 and
above
rlf-InfoAvailable-r9 true
}
}
}
}

c1 CHOICE{
dicated-HO
}
}
}
}
ETSI
8.2.4.14a RRC connection reconfiguration / Handover / Failure / Re-establishment

successful / Inter-band / Between FDD and TDD
(1)
initial security activation procedure and after receiving an RRCConnectionReconfiguration message
including a mobilityControlInfo indicating a different E-UTRA TDD cell having attempted inter-mode
handover }
ensure that {
when { UE detects handover failure and the initial E-UTRA TDD cell is selectable }
RRC_CONNECTED state on the E-UTRA TDD cell }
}
(2)
with { UE in E-UTRA FDD RRC_CONNECTED state and having transmitted an
RRCConnectionReestablishmentRequest message on E-UTRA TDD cell }
ensure that {
same as the NCC associated with the currently active KeNB }
then { UE derives new KeNB from the currently active KeNB }
}
(3)
initial security activation procedure and after receiving an RRCConnectionReconfiguration message
including a mobilityControlInfo indicating a different E-UTRA FDD cell having attempted inter-mode
handover }
ensure that {
when { UE detects handover failure and the initial E-UTRA FDD cell is selectable }
RRC_CONNECTED state on the E-UTRA FDD cell }
}
(4)
with { UE in E-UTRA TDD RRC_CONNECTED state and having transmitted an
RRCConnectionReestablishmentRequest message on E-UTRA FDD cell }
ensure that {
different from the NCC associated with the currently active KeNB }
then { UE derives new KeNB from the nextHopChainingCount }
}
5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1> else:
ETSI
targetPhysCellId;
message.
1> reset MAC;
1> else:
[32];
1> else:
33.401 [32];
ETSI
2> stop timer T304;
...
[TS 36.331, clause 5.3.5.6]
The UE shall:
[TS 36.331, clause 5.3.7.2]
...
...
1> reset MAC;
[TS 36.331, clause 5.3.7.4]
ETSI
cases); and
...
[TS 36.331, clause 5.3.7.5]
NOTE 5: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];
The UE shall:
1> stop timer T301;
1> resume SRB1;
NOTE 6: E-UTRAN should not transmit any message on SRB1 prior to receiving the
RRCConnectionReestablishmentComplete message.
33.401 [32];
[32];
ETSI
1> set the content of RRCConnectionReestablishmentComplete message as follows:
2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the
RPLMN is included in plmn-IdentityList stored in VarRLF-Report:
3> include the rlf-InfoAvailable;
procedure ends;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
- Cell 1 is FDD cell and Cell 28 is TDD cell.
- Cell 28 has a valid UE context
8.2.4.14a.3.1-1.
Cell PLMN name

1 PLMN1
28 PLMN2
UTRA cells.
ETSI
UE:
None.
Preamble:
8.2.4.14a.3.3-15.
columns marked "T1", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values

T0 dBm/15kHz -85 -97
RS EPRE Cell 28 (M28) satisfy exit condition for
T1 dBm/15kHz -85 -73
(NOTE 1).
T3 dBm/15kHz -85 -97
event A3 (M1> M28).
T4 dBm/15kHz -85 "Off"
RS EPRE selecting Cell 1 is guaranteed.
(NOTE 1).
ETSI

U-S Message
message on Cell 1.
8.2.4.14a.3.2-3 should take place.
message on Cell 28?
the currently active KeNB on Cell 28?
message on Cell 28.
8.2.4.14a.3.2-1.
handover to Cell 1.
Table 8.2.4.14a.3.2-4 should take place.
message on Cell 1?
ETSI

security on Cell 1.
message on Cell 1.

U-S Message

U-S Message
Preamble on Cell 1.
Table 8.2.4.14a.3.3-0: SystemInformationBlockType2 for Cell 1 and Cell 28 (preamble and all the steps
in Table 8.2.4.14a.3.2-2)

}
ETSI
Table 8.2.4.14a.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.14a.3.2-2)
Table 8.2.4.14a.3.3-2: MeasConfig (Table 8.2.4.14a.3.3-1)
Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ

GENERIC(f1)
GENERIC(f6)
}
}
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 28
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
Table 8.2.4.14a.3.3-5: MobilityControlInfo (Table 8.2.4.14a.3.3-4)

Cell 28
as used for Cell 28
}
ra-PreambleIndex 63
}
}
Table 8.2.4.14a.3.3-6: RRCConnectionReestablishmentRequest (step 7, Table 8.2.4.14a.3.2-2)

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}
Table 8.2.4.14a.3.3-7: RRCConnectionReestablishment (step 8, Table 8.2.4.14a.3.2-2)

c1 CHOICE{
}
}
}
}
ETSI
Table 8.2.4.14a.3.3-7A: RRCConnectionReestablishmentComplete (step 9 and step 18, Table

8.2.4.14a.3.2-2)

SEQUENCE {
rrcConnectionReestablishmentComplete-r8 =
SEQUENCE {
nonCriticalExtension SEQUENCE {} Not present Rel-8
nonCriticalExtension SEQUENCE {} Not checked Rel-9
nonCriticalExtension SEQUENCE { Rel-10 and
above
rlf-InfoAvailable-r9 true
}
}
}
}

c1 CHOICE{
dicated-HO
}
}
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 1
as used for Cell 1
}
ra-PreambleIndex 63
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 28
the XMAC-I value
calculated by SS.
}
}
}
}

c1 CHOICE{
}
}
}
}

Table 8.2.4.14a.3.3-16: TRACKING AREA UPDATE ACCEPT for Cell 28 (step 11B, Table 8.2.4.14a.3.2-
2)


ETSI

failure / Inter-band
(1)
and after receiving an RRCConnectionReconfiguration message including an IE
mobilityControlInformation indicating a different E-UTRA cell having attempted inter-band handover }
ensure that {
then { UE enters the E-UTRA RRC_IDLE state and trigger TAU procedure in order to recover RRC
connection }
}
5.3.5.6, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.7 and 5.3.12
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
1> else:
[32];
1> else:
33.401 [32];
2> stop timer T304;
ETSI
[TS 36.331, clause 5.3.5.6]
The UE shall:
NOTE 5: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not
[TS 36.331, clause 5.3.7.2]
...
...
1> reset MAC;
[TS 36.331, clause 5.3.7.3]
Upon selecting a suitable E-UTRA cell, the UE shall:
1> stop timer T311;
NOTE 6: This procedure applies also if the UE returns to the source cell.
[TS 36.331, clause 5.3.7.4]
ETSI
cases); and
2> else:
3> set the reestablishmentCause to the value 'otherFailure';
[TS 36.331, clause 5.3.7.6]
1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';
[TS 36.331, clause 5.3.12]
1> reset MAC;
1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP
entity for all established RBs;
2> enter RRC_IDLE and perform procedures as specified in TS 36.304 [4, 5.2.7];
System Simulator:
ETSI
UE:
None.
Preamble:

specific RS kHz results for Cell 1 (M1) and Cell 10 (M10) satisfy exit
T2 Cell- dBm/15 -85 "Off" The power level values are such that SrxlevCell 1 >
specific RS kHz SrxlevCell 10 and SrxlevCell 10 <0.
EPRE (NOTE 1)
ETSI

U-S Message
message on Cell 1.
8.2.4.15.3.2-1.
8.2.4.15.3.2-1.
message on Cell 1.
on Cell 1.
9-13 The UE will perform TAU procedure based on - - - -
steps 1 to 5 of subclause 6.4.2.7 in TS 36.508
on Cell 1.

U-S Message
Preamble on Cell 10
Derivation Path: 36.508 Table 4.6.1-8, condition MEAS
ETSI

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

Cell 10
as used for Cell 10
}
}

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS
}
}
}
}
8.2.4.15a RRC connection reconfiguration / Handover / Failure / Re-establishment

failure / Inter-band / Between FDD and TDD
(1)
initial security activation procedure on E-UTRA FDD cell and after receiving an
RRCConnectionReconfiguration message including an IE mobilityControlInfo indicating a different E-
UTRA TDD cell having attempted inter-mode handover }
ensure that {
then { UE enters the E-UTRA FDD RRC_IDLE state and trigger TAU procedure in order to recover RRC
connection on E-UTRA FDD cell }
}
(2)
initial security activation procedure on E-UTRA TDD cell and after receiving an
RRCConnectionReconfiguration message including an IE mobilityControlInfo indicating a different E-
UTRA FDD cell having attempted inter-mode handover }
ETSI
ensure that {
then { UE enters the E-UTRA TDD RRC_IDLE state and trigger TAU procedure in order to recover RRC
connection on E-UTRA TDD cell }
}
5.3.5.6, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.7 and 5.3.12.
[TS 36.331, clause 5.3.5.4]
...
If the RRCConnectionReconfiguration message includes the mobilityControlInformation and the UE is able to comply
1> start timer T304 with the timer value set to t304, as included in the mobilityControlInformation;
transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of
the SN and the HFN, is specified in [8].
1> If the RRCConnectionReconfiguration message includes the radioResourceConfiguration:
2> perform the Radio resource configuration procedure as specified in 5.3.10;
1> set the C-RNTI to the value of the newUE-Identity;
1> if the eutra-CarrierFreq is included:
identity indicated by the targetCellIdentity;
1> else:
targetCellIdentity;
1> if the dl-Bandwidth is included:
2> for the target cell, apply the downlink bandwidth indicated by the dl-Bandwidth;
1> else:
2> for the target cell, apply the same downlink bandwidth as for the current cell;
1> if the ul-Bandwidth is included:
2> for the target cell, apply the uplink bandwidth indicated by the ul-Bandwidth;
1> else:
2> for the target cell, apply the same uplink bandwidth as for the current cell;
1> If the RRCConnectionReconfiguration message includes the securityConfiguration:
2> apply the AS-derived keys associated with the AS-base key indicated by the keyIndicator;
ETSI
2> configure lower layers to apply the indicated integrity protection algorithm, i.e. the indicated integrity
protection configuration shall be applied to all subsequent messages received and sent by the UE in the target
cell, including the message used to indicate the successful completion of the procedure;
2> configure lower layers to apply the indicated ciphering algorithm, i.e. the indicated ciphering configuration
shall be applied to all subsequent messages received and sent by the UE in the target cell, including the
message used to indicate the successful completion of the procedure;
1> If the RRCConnectionReconfiguration message includes the measurementConfiguration:
1> synchronise to the DL of the target cell;
configuration;
1> If MAC successfully completes the random access procedure:
2> stop timer T304;
2> If the physicalConfigDedicated is included in the RRCConnectionReconfiguration message:
3> If the UE needs the SFN of the target cell to apply the PUCCH and Sounding RS configuration:
4> apply the new PUCCH and Sounding RS configuration upon acquiring the SFN of the target cell;
3> else:
4> apply the new PUCCH and Sounding RS configuration;
2> indicate to PDCP to complete the PDCP Re-establishment procedure for all DRBs that are established, if any;
2> the procedure ends.
...
[TS 36.331, clause 5.3.5.6]
The UE shall:
1> If T304 expires (handover failure):
NOTE 1: Following T304 expiry dedicated preambles, if provided within the rach-ConfigDedicated, are not
2> revert back to the configuration used in the source cell, excluding the physical layer configuration;
NOTE 2: The UE reverts to the RRC configuration as well as the layer 2 configuration (PDCP/RLC/MAC) used in
the source cell.
reconfiguration procedure ends.
[TS 36.331, clause 5.3.7.2]
The UE shall only initiate the procedure when security has been activated. The UE initiates the procedure when one of
the following conditions is met:
...
...
...
ETSI
transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and
the HFN, is specified in [8].
1> select a suitable cell in accordance with the cell selection process as specified in [4];
[TS 36.331, clause 5.3.7.3]
...
...
[TS 36.331, clause 5.3.7.4]
2> set the c-RNTI to the C-RNTI used in the source cell (handover failure case) or used in the cell in which the
trigger for the re-establishment occurred (other cases);
2> set the cellIdentity to the Physical layer identity of the source cell (handover failure case) or of the cell in
which the trigger for the re-establishment occurred (other cases);
3> over the concatenation of the ASN.1 encoded CellIdentity of the current cell, PhysicalCellIdentity of the
cell the UE was connected to prior to the failure and C-RNTI that the UE had in the cell it was connected
to prior to the failure;
3> with the integrity protection key and integrity protection algorithm that was used in the cell the UE was
connected to prior to the failure; and
3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones.
1> set the IE reestablishmentCause as follows:
...
3> set the reestablishmentCause to the value ‘handoverFailure’;
...
[TS 36.331, clause 5.3.7.7]
1> perform the actions upon moving from RRC_CONNECTED to RRC_IDLE as specified in 5.3.12.
...
[TS 36.331, clause 5.3.12]
Upon moving from RRC_CONNECTED to RRC_IDLE, the UE shall:
ETSI
...
1> release all radio resources, including release of the RLC entity and the associated PDCP entity for all established
RBs;
1> indicate the release of the RRC connection to upper layers;
1> enter RRC_IDLE.
System Simulator:
- Cell 1 is an LTE FDD cell, Cell 10 and Cell 30 are LTE TDD cells.
8.2.4.15 a.3.1-1.
Table 8.2.4.15 a.3.1-1: PLMN identifiers
Cell PLMN name

1 PLMN1
10 PLMN1
30 PLMN2
UTRA cells.
UE:
None.
Preamble:
8.2.4.15a.3.3-13.
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while columns marked
"T1", "T2", "T3", "T4" and "T5" are to be applied subsequently. The exact instants on which these values shall be
ETSI

Cell-specific dBm/15k measurement results for Cell 1 (M1) and Cell
T0 -85 -97 “Off”
RS EPRE Hz 10 (M10) satisfy exit condition for event A3
(M10 < M1).
Cell-specific dBm/15k measurement results for Cell 1 (M1) and Cell
T1 -85 -73 “Off”
RS EPRE Hz 10 (M10) satisfy entry condition for event A3
(M10 > M1).
The power level values are assigned to satisfy
Cell-specific dBm/15k SrxlevCell 10 < 0 such that selecting Cell 1 is
T2 -85 "Off" “Off”
RS EPRE Hz guaranteed
(NOTE 1).
measurement results for Cell 1 (M1) and Cell
T3 -85 "Off" -73 30 (M30) satisfy entry condition for event A3
RS EPRE Hz
(M30> M1).
(NOTE 1).
Cell-specific dBm/15k measurement results for Cell 30 (M30) satisfy
T4 -73 "Off" -85
RS EPRE Hz entry condition for event A3 (M1> M30).
(NOTE 1).
The power level values are assigned to satisfy
Cell-specific dBm/15k SrxlevCell 1 < 0 such that selecting Cell 30 is
T5 "Off" "Off" -85
RS EPRE Hz guaranteed
(NOTE 1).
ETSI

U-S Message
setup inter-band measurement on Cell 1 for
Cell 10.
message on Cell 1.
message on Cell 1.
on Cell 1.
9 Generic test procedure described in TS 36.508 - - - -
10 Generic test procedure described in TS 36.508 - - 1 -
subclause 4.5.3.3.is executed
setup inter-band measurement on Cell 1 for
Cell 30.
message on Cell 1.
handover
17 The UE transmits a TRACKING AREA - - - -
18 SS responds with a TRACKING AREA - - - -
ETSI

8.2.4.15a.3.2-1.
handover to Cell 1.
message on Cell 30.
on Cell 30.
26- The UE will perform TAU procedure based on - - - -
30 steps 1 to 5 of subclause 6.4.2.7 in TS 36.508
on Cell 30.
to NAS signalling connection recovery or TAI
change.

U-S Message
Preamble on Cell 10

U-S Message
Preamble on Cell 1
ETSI
Derivation path: 36.508 Table 4.6.1-8, condition MEAS
Table 8.2.4.15a.3.3-2: MeasConfig (step 1 and step 11, Table 8.2.4.15a.3.3-1)

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.2.4.15a.3.3-4A: RRCConnectionReconfiguration (step 15, Table 8.2.4.15a.3.2-2)
Derivation path: 36.508 Table 4.6.1-8, condition HO and condition MEAS
Table 8.2.4.15a.3.3-4B: MeasConfig (step 15 Table 8.2.4.15a.3.3-4A)

Cell 10
as used for Cell 10
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE.
Cell 1
the XMAC-I value
calculated by SS
}
}
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 30
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
Table 8.2.4.15a.3.3-8: MobilityControlInfo (step 15, Table 8.2.4.15a.3.3-4A)

Cell 30
as used for Cell 30
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
physCellId[1] PhysicalCellIdentity of Cell 1
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 1
as used for Cell 1
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE.
Cell 30
the XMAC-I value
calculated by SS
}
}
}
}

Table 8.2.4.15a.3.3-13: TRACKING AREA UPDATE ACCEPT for Cell 1 (steps 9, Table 8.2.4.15a.3.2-2)


Table 8.2.4.15a.3.3-15: TRACKING AREA UPDATE ACCEPT for Cell 30 (steps 26-30, Table
8.2.4.15a.3.2-2)

8.2.4.16 CA / RRC connection reconfiguration / Setup and Change of MIMO

8.2.4.16.1 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band
Contiguous CA
(1)
and configured an Scell }
ETSI
ensure that {
when { UE receives an RRCConnectionReconfiguration message indicating PCell and Scell TM
modification}
then { UE sends an RRCConnectionReconfigurationComplete message and changes transmission mode of
the Pcell and SCell}
}
[TS 36.331, clause 5.3.10.6]
The UE shall:
1> if the antennaInfo-r10 is included in the received physicalConfigDedicated and the previous version of this field
that was received by the UE was antennaInfo (without suffix i.e. the version defined in REL-8):
2> apply the default antenna configuration as specified in section 9.2.4;
1> if the cqi-ReportConfig-r10 is included in the received physicalConfigDedicated and the previous version of this
field that was received by the UE was cqi-ReportConfig (without suffix i.e. the version defined in REL-8):
2> apply the default CQI reporting configuration as specified in 9.2.4;
NOTE: Application of the default configuration involves release of all extensions introduced in REL-9 and later.
1> if the antennaInfo is included and set to explicitValue:
2> if the configured transmissionMode is not tm3 or tm4 or tm8 or tm9; or
2> if the configured transmissionMode is tm8 and pmi-RI-Report is not present; or
2> if the configured transmissionMode is tm9 and pmi-RI-Report is not present; or
2> if the configured transmissionMode is tm9 and pmi-RI-Report is present and antennaPortsCount within csi-
RS is set to an1:
1> else if the antennaInfo is included and set to defaultValue:
System Simulator:
- Cell 1 and Cell 3
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) on Cell 1 in TM2 according to [18].
various time instants of the test execution. Row marked "T0" denotes the initial conditions. The exact instants on which
these values shall be applied are described in the texts in this clause.
ETSI

T0 -85 -107
RS EPRE Hz
T1 -85 -91
RS EPRE Hz

U-S Message
1 The SS changes Cell 1 and Cell 3 parameters
1.
2 The SS transmits an <-- RRCConnectionReconfiguration 1 P
Cell 1 to reconfigure Cell 3 as a Scell and
reconfiguring transmission mode for both PCell
and SCell.
message on Cell 1.
reconfigure transmission mode on both PCell
and SCell.
5 The UE transmits an --> RRCConnectionReconfigurationC 1 P
message on Cell 1.

c1 CHOICE{
RadioResourceConfigCommon-DEFAULT ::=
SEQUENCE {
antennaInfo-r10 TM3
}
}
}
}
}
}
ETSI

sCellIndex-r10 1
Cell 3
dl-CarrierFreq-r10 DEFAULT EARFCN
}
}
Table 8.2.4.16.1.3.3-3: RadioResourceConfiDedicatedSCell-r10 (Table 8.2.4.16.1.3.3-1)

SEQUENCE {
PhysicalConfigDedicatedSCell-r10 ::=
SEQUENCE {
antennaInfo-r10 {
transmissionMode-r10 TM2
}
}
}
}
Derivation Path: 36.508, Table 4.6.1-8, condition SCell_AddMod

c1 CHOICE{
RadioResourceConfigCommon-DEFAULT ::=
SEQUENCE {
antennaInfo-r10 TM2
}
}
}
}
}
}

sCellIndex-r10 1
Cell 3
dl-CarrierFreq-r10 DEFAULT EARFCN
}
}
ETSI
Table 8.2.4.16.1.3.3-6: RadioResourceConfiDedicatedSCell-r10 (Table 8.2.4.16.1.3.3-5)

SEQUENCE {
PhysicalConfigDedicatedSCell-r10 ::=
SEQUENCE {
antennaInfo-r10 {
transmissionMode-r10 TM3
}
}
}
}
8.2.4.16.2 CA / RRC connection reconfiguration / Setup and Change of MIMO / Inter-band

CA
- CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
8.2.4.16.3 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band

non-contiguous CA
- CA configuration: Intra-band non-contiguous CA replaces Intra-band contiguous CA
8.2.4.17 CA / RRC connection reconfiguration / Handover / Success / PCell Change

and SCell addition
8.2.4.17.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change and
SCell addition / Intra-band Contiguous CA
(1)
ensure that {
indicating a different E-UTRA frequency to be handover to one of the SCell and sCellToAddModList
with an SCell addition }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4
[TS 36.331, clause 5.3.5.4]
ETSI
2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity
1> else:
2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated
by the targetPhysCellId;
1> start synchronising to the DL of the target PCell;
message.
1> reset MAC;
1> configure lower layers to consider the SCell(s), if configured, to be in deactivated state;
1> else:
2> if connected as an RN:
3> derive the KUPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];
[32];
1> else:
ETSI
3> derive the KUPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];
33.401 [32];
2> configure lower layers to apply the integrity protection algorithm and the KUPint key, for current or
subsequently established DRBs that are configured to apply integrity protection, if any;
1> set the content of RRCConnectionReconfigurationComplete message as follows:
2> if the UE has radio link failure or handover failure information available in VarRLF-Report and plmn-Identity
stored in VarRLF-Report is equal to the RPLMN:
3> include rlf-InfoAvailable;
2> if the UE has logged measurements available for E-UTRA and plmn-Identity stored in VarLogMeasReport is
equal to the RPLMN:
3> include the logMeasAvailable;
2> stop timer T304;
configuration that do not require the UE to know the SFN of the target PCell, if any;
of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration,
sounding RS configuration), if any, upon acquiring the SFN of the target PCell;
ETSI
NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from
that cell before performing RACH access in the target PCell.
System Simulator:
- Cell 1 is the PCell and Cell 3 SCell
UE:
None.
Preamble:

Cell-specific dBm/15k The power level values are such that
T0 -85 Off
RS EPRE Hz camping on Cell 1 is guarantee.
Power levels are such that entry
Cell-specific dBm/15k condition for event A3 (measId 1) is
T1 -85 -79 satisfied:
RS EPRE Hz
Mn + Ofn + Ocn − Hys > Ms + Ofs + Ocs + O
ETSI

U-S Message
including sCellToAddModList with Cell 3 as
SCell addition.
message
Cell 1 to setup event A3 reporting
configuration.
message on Cell 1.
Cell 1 to order the UE to perform handover to
Cell 3 with Cell 1 as SCell addition at the same
time.
completion of the handover and SCell addition
of Cell 1?

c1 CHOICE{
sCellToAddModList-r10 SCellToAddMod-r10-f2 SCell addition for
Cell 3
}
}
}
}
}
}
}
ETSI
Table 8.2.4.17.1.3.3-2: SCellToAddMod-r10-f2 (Table 8.2.4.17.1.3.3-1)

sCellIndex-r10[1] 1
cellIdentification-r10[1] SEQUENCE {
physCellId-r10[1] Physical Cell Identity of
Cell 3
dl-CarrierFreq-r10[1] Same downlink EARFCN
as used for Cell 3
}
radioResourceConfigCommonSCell-r10[1] RadioResourceConfigCom
monSCell-r10-f2
}

SEQUENCE {
Cell 3
}
}
Table 8.2.4.17.1.3.3-4: Void

GENERIC(f1)
GENERIC(f2)
}
}
measId[1] 1
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListEUTRA ::= SEQUENCE (SIZE 1 entry
physCellId[1] physicalCellId of Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
servFreqId-r10 1
}
}
}
}
}
}
}
ETSI
Derivation Path: 36.508 Table 4.6.1-8 condition HO

c1 CHOICE {
sCellToReleaseList-r10 SEQUENCE (SIZE
SCellIndex-r10[1] 1
}
sCellToAddModList-r10 SCellToAddMod-r10-f1 SCell addition for
Cell 1
}
}
}
}
}
}
}
Table 8.2.4.17.1.3.3-9: MobilityControlInfo (Table 8.2.4.17.1.3.3-8)

Cell 3
as used for Cell 3
}
}

sCellIndex-r10[1] 1
Cell 1
as used for Cell 1
}
monSCell-r10-f1
}
ETSI

SEQUENCE {
Cell 1
}
}

SCell addition / Inter-band CA

SCell addition / Intra-band non-contiguous CA
- CA configuration: Intra-band non-contiguous CA replaces Intra-band Contiguous CA.
8.2.4.18 CA / RRC connection reconfiguration / Handover / Success / SCell release

8.2.4.18.1 CA / RRC connection reconfiguration / Handover / Success / SCell release /
(1)
with { UE having completed the radio bearer establishment and initial security activation procedure,
performed the intra-frequency measurement and configured an SCell }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and
including sCellToReleaseList with an sCellIndex set to the configured SCell }
then { UE sends an RRCConnectionReconfigurationComplete message }
}
5.3.10.3a.
[TS 36.331, clause 5.3.5.4]
ETSI
1> else:
message.
1> reset MAC;
1> else:
[32];
1> else:
ETSI
33.401 [32];
equal to the RPLMN:
2> stop timer T304;
ETSI
[TS 36.331, clause 5.3.10.3a]
The UE shall:
System Simulator:
- Cell 1 is PCell, Cell 2 is intra-frequency cell of PCell, and Cell 3 is SCell to be added
UE:
None.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the 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

Cell-specific dBm/15k measurement results for Cell 1 (M1) and Cell 2
T0 -85 -91 -97
RS EPRE Hz (M2) do not satisfy entry condition for event A3
(M2 < M1).
T1 -85 -79 -97
RS EPRE Hz (M2) satisfy entry condition for event A3 (M2 >
M1).
ETSI

U-S Message
Cell 1 to configure Cell 3 as a SCell.
message on Cell 1.
setup intra-frequency measurement reporting
for event A3 on Cell 1.
message on Cell 1.
"T1" in Table 8.2.4.18.1.3.2-1.
message on Cell 1 to report event A3.
perform intra-frequency handover and SCell
release on Cell 1.
message on Cell 2?

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
}
ETSI
Table 8.2.4.18.1.3.3-3: RadioResourceConfigCommonSCell-r10 (Table 8.2.4.18.1.3.3-2)
Derivation Path: 36.508, Table 4.6.3-13A

SEQUENCE {
Cell 3
}
}

GENERIC(f1)
GENERIC(f2)
}
}
measIdToAddModListSEQUENCE (SIZE
measId[1] 1
}
}
Table 8.2.4.18.1.3.3-5A: ReportConfig-A3 (Table 8.2.4.18.1.3.3-5)
Derivation path: 36.508, Table 4.6.6-6

event SEQUENCE {
timeToTrigger ms2560
}
}
}
ETSI

c1 CHOICE{
measId 1
measResultPCell SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
measResultServFreqList-r10 SEQUENCE 1 entry
servFreqId-r10[1] 1 Cell 3
measResultSCell-r10[1] SEQUENCE {
}
measResultBestNeighCell-r10[1] Not present
}
}
}
}
}
}
ETSI

c1 CHOICE{
otherConfig-r9 Not present
fullConfig-r9 Not present
SCellIndex-r10[1] 1
}
}
}
}
}
}
}
}

Cell 2
}

Inter-band CA

Intra-band non-contiguous CA
- Cells configuration: Cell 6 replaces Cell 1 and Cell 13 replaces Cell 2.
ETSI
8.2.4.19 CA / RRC connection reconfiguration / Handover / Success / PCell Change /

SCell no Change
8.2.4.19.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change /
SCell no Change / Intra-band Contiguous CA
(1)
performed the inter-frequency measurement and configured an SCell }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including mobilityControlInfo
indicating change of the PCell and sCellToAddModList with an SCell same from configured SCell
representing an intra-band contiguous CA }
then { UE sends an RRCConnectionReconfigurationComplete message and does not change SCell }
}
References: The conformance requirements covered in the present TC are specified in TS 36.331, clauses 5.3.5.4 and
5.3.10.3b.
[TS 36.331, clause 5.3.5.4]
1> else:
message.
1> reset MAC;
ETSI
1> else:
[32];
1> else:
33.401 [32];
ETSI
equal to the RPLMN:
2> stop timer T304;
[TS 36.331, clause 5.3.10.3b]
The UE shall:
(SCell addition):
modification):
System Simulator:
- Cell 3 is the PCell, Cell 1 is the SCell to be added and Cell 6 is the inter-frequency neighbour cell.
ETSI
UE:
None.
Preamble:

T0 -91 -85 -97
RS EPRE Hz (M2) do not satisfy entry condition for event A3
(M2 < M1).
T1 -91 -85 -79
RS EPRE Hz (M3) satisfy entry condition for event A3 (M3 >
M1).

U-S Message
Cell 3 to configure Cell 1 as an SCell.
message on Cell 3.
setup inter-frequency measurement reporting
message on Cell 3.
"T1" in Table 8.2.4.19.1.3.2-1.
perform inter-frequency handover.
message on Cell 6?
ETSI

sCellIndex-r10 1
Cell 1
as used for Cell 1
}
}

SEQUENCE {
Cell 1
}
}
Table 8.2.4.19.1.3.3-4: Void
ETSI

GENERIC(f1)
GENERIC(f2)
GENERIC(f3)
}
reportConfig[1]
ReportConfig-A3
}
measId[1] 1
}
}
Table 8.2.4.19.1.3.3-6A : ReportConfig-A3 (Table 8.2.4.19.1.3.3-6)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-6

event SEQUENCE {
}
}
}
ETSI

c1 CHOICE{
measId 1
measResultPCell SEQUENCE { Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 6
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
servFreqId-r10[1] 1
measResultSCell-r10[1] SEQUENCE { Cell 1
}
}
}
}
}
}
}

Cell 6
carrierFreq Same DL EARFCN as
used for Cell 6
}

SCell no Change / Inter-band CA
ETSI
- Cells configuration: Cell 10 replaces Cell 1& Cell 1 replaces Cell 6.

SCell no Change / Intra-band non-contiguous CA
- CA configuration: Intra-band non-contiguous CA replaces Intra-band Contiguous CA.
- Cells configuration: Cell 1 replaces Cell 3 and Cell 10 replaces Cell 1. I.e. Cell 1 is the PCell, Cell 10 is the
SCell to be added and Cell 6 is the inter-frequency neighbour cell.
8.2.4.20 CA / RRC connection reconfiguration / Handover / Success / SCell Change

8.2.4.20.1 CA / RRC connection reconfiguration / Handover / Success / SCell Change /
(1)
ensure that {
sCellToAddModList with an SCell different from configured SCell }
then { UE sends an RRCConnectionReconfigurationComplete message and changes SCell }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.10.3b.
[TS 36.331, clause 5.3.10.3b]
The UE shall:
(SCell addition):
modification):
System Simulator:
- Cell 1 is the PCell, Cell 3 is the SCell to be added and Cell 12 is the intra-frequency neighbour cell of Cell 3.
- Cell 1 and Cell 3 are Inactive SCells according to [18] cl. 6.3.4
- 3 E-UTRA Cells with the same PLMN.
ETSI
UE:
None.
Preamble:

Cell-specific dBm/15k measurement results for Cell 12 (M12) and
T0 -85 -91 -97
RS EPRE Hz Cell 3 (M2) do not satisfy entry condition for
event A6.
T1 -85 -85 -79 measurement results for Cell 12 (M12) and
RS EPRE Hz
Cell 3 (M3) satisfy entry condition for event A6.
ETSI

U-S Message
1 Wait 1 s to allow for the switching of cells. - - - -
message on Cell 1.
EXCEPTION: If UE does not support FGI bit
111, i.e. Event A6, the following step 4 to step
7 except step 6 should not be executed
setup intra-frequency measurement reporting
message on Cell 1.
6 The SS changes power level according to row - - - -
"T1" in Table 8.2.4.20.3.2-1.
perform inter-frequency handover to Cell 12
with original SCell Cell 3 release and new
SCell Cell1addition.
message on Cell 12?
UPDATE REQUEST message to update the
registration of the actual tracking area.
11 The SS responds with TRACKING AREA - - - -
UPDATE COMPLETE.

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
}
ETSI

SEQUENCE {
Cell 3
}
}

GENERIC(f1)
}
{
GENERIC(f2)
}
}
measId[1] 1
}
}
ETSI
Derivation Path: 36.508, clause 4.6.1 table 4.6.1-5

c1 CHOICE{
measId 1
measResultPCell SEQUENCE { Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 12
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
servFreqId-r10[1] 1
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
SCellToReleaseList-r10 ::= SEQUENCE
(SIZE (1..maxSCell-r10)) OF SEQUENCE {
SCellIndex-r10[1] 1
}
SCellToAddModList-r10 SCellToAddMod-r10-f1
}
}
}
}
}
}
}
Derivation Path: clause 4.6.5-1

Cell 12
used for Cell 12
}

sCellIndex-r10[1] 1
Cell 1
as used for Cell 1
}
monSCell-r10-f1
}
ETSI

SEQUENCE {
Cell 1
}
8.2.4.20.2 CA / RRC connection reconfiguration / Handover / Success / SCell Change /

Inter-band CA
- Cells configuration: Cell 10 replaces Cell 3& Cell 30 replaces Cell 12.
- Cell 1 and Cell 10 are Inactive SCells according to [18] cl. 6.3.4.
- Cell 1, Cell 10 and Cell 30 with the same PLMN.
8.2.4.20.3 CA / RRC connection reconfiguration / Handover / Success / SCell Change Intra-

band non-contiguous CA
- CA configuration: Intra-band non contiguous CA replaces Intra-band Contiguous CA
- Cell 1 and Cell 10 are Inactive SCells according to [18] cl. 6.3.4
8.2.4.21 CA / RRC connection reconfiguration / Handover / Success / SCell release

(1)
performed the inter-frequency measurement and configured an SCell }
ensure that {
including sCellToReleaseList with an sCellIndex set to the configured SCell }
then { UE sends an RRCConnectionReconfigurationComplete message }
}
5.3.10.3a.
[TS 36.331, clause 5.3.5.4]
ETSI
1> else:
message.
1> reset MAC;
1> else:
[32];
1> else:
ETSI
33.401 [32];
equal to the RPLMN:
2> stop timer T304;
ETSI
[TS 36.331, clause 5.3.10.3a]
The UE shall:
System Simulator:
- Cell 1 is the PCell, Cell 3 is the SCell to be added and Cell 6 is the inter-frequency neighbour cell of PCell.
UE:
None.
Preamble:

T0 -85 -91 -97
RS EPRE Hz (M6) do not satisfy entry condition for event
A5.
T1 -85 -85 -79 measurement results for Cell 1 (M1) and Cell 6
RS EPRE Hz
(M6) satisfy entry condition for event A5.
ETSI

U-S Message
message on Cell 1.
setup inter-frequency measurement reporting
message on Cell 1.
"T1" in Table 8.2.4.21.1.3.2-1.
perform inter-frequency handover to Cell 6 and
release SCell Cell 3.
message on Cell 6?

sCellIndex-r10 1
Cell 3
as used for Cell 3
}
}
ETSI

SEQUENCE {
Cell 3
}
}

measConfig ::= SEQUENCE {
GENERIC(f1)
GENERIC(f2)
GENERIC(f3)
}
}
measId[1] 1
}
}
Table 8.2.4.21.1.3.3-6: ReportConfig-A5 (Table 8.2.4.21.1.3.3-5)
Derivation path: 36.508 clause 4.6.6 table ReportConfigEUTRA-A5(-76, -88)

ReportConfigEUTRA ::= SEQUENCE {
reportAmount infinity
event SEQUENCE {
}
}
}
}
ETSI
Derivation Path: 36.508, clause 4.6.1 table 4.6.1-5

c1 CHOICE{
measId 1
measResultPCell SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 6
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
servFreqId-r10[1] 1
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measIdToRemoveList SEQUENCE (SIZE 1 entry
measId[1] 1
}
}
SCellToReleaseList-r10 ::= SEQUENCE
(SIZE (1..maxSCell-r10)) OF SEQUENCE {
SCellIndex-r10[1] 1
}
SCellToAddModList-r10 Not present
}
}
}
}
}
}
}

Cell 6
used for Cell 6
}

Inter-band CA
- Cells configuration:
- Cell 10 replaces Cell 3, and then
- If f6 is supported as per TS 36.508 Table 6.2.3.2-2 by the band combination in which the test case is executed,
then Cell 28 replaces Cell 6; otherwise Cell 3 replaces Cell 6. When Cell 28 is used its PLMN shall be set to
PLMN 1.

Intra-band non-Contiguous CA
ETSI
- Cells configuration:
- Cell 6 replaces Cell 1 as a PCell
- Cell 1 replaces Cell 6 as an inter-frequency neighbour cell of PCell
8.2.4.22 RRC connection reconfiguration / Handover / MFBI / Target cell broadcasting

information disregarded by the UE
(1)
with {UE in RRC_CONNECTED and T311 is not running, and the UE supports multi-band cells as defined
by bit 31 in featureGroupIndicators}
ensure that {
when { UE receives freqBandIndicator and multiBandInfoList from SystemInformationBlockType1 and
additionalSpectrumEmission and ul-CarrierFreq from SystemInformationBlockType2 }
then { the UE disregard the related system information fields and continues connected mode
operations}
}
[TS 36.331, clause 5.2.2.7]
1> else:
or
2> else:
FALSE;
[TS 36.331, clause 5.2.2.9]
Upon receiving SystemInformationBlockType2, the UE shall:
1> apply the configuration included in the radioResourceConfigCommon;
1> if upper layers indicate that a (UE specific) paging cycle is configured:
ETSI
2> apply the shortest of the (UE specific) paging cycle and the defaultPagingCycle included in the
radioResourceConfigCommon;
1> if the mbsfn-SubframeConfigList is included:
2> consider that DL assignments may occur in the MBSFN subframes indicated in the mbsfn-
SubframeConfigList under the conditions specified in [23, 7.1];
1> apply the specified PCCH configuration defined in 9.1.1.3;
1> not apply the timeAlignmentTimerCommon;
1> if in RRC_CONNECTED and UE is configured with RLF timers and constants values received within rlf-
TimersAndConstants:
2> not update its values of the timers and constants in ue-TimersAndConstants except for the value of timer
T300;
1> if in RRC_CONNECTED while T311 is not running; and the UE supports multi-band cells as defined by bit 31
2> disregard the additionalSpectrumEmission and ul-CarrierFreq, if received, while in RRC_CONNECTED;
System Simulator:
- Cell 1 and Cell 2 are MFBI capable cells.
UE:
None.
Preamble:

T0 -85 -91
A3 (M2 < M1).
T1 -85 -79
A3 (M2 > M1).
ETSI

U-S Message
message on Cell 1.
1.
6 Check: Does the UE transmit an --> RRCConnectionReconfigurationC - -
message on Cell 2 using common preamble to
confirm the successful completion of the intra
frequency handover?
7 Wait 10 secs to ensure that the UE receives - - - -
system information from the Cell 2 and ignores
freqBandIndicator and multiBandInfoList from
additionalSpectrumEmission and ul-
CarrierFreq from
SystemInformationBlockType2 as the UE is in
connected mode.
Table 8.2.4.22.3.3-0A: SystemInformationBlockType1 for Cell 1 and Cell 2 (preamble and all steps,
Table 8.2.4.22.3.2-2)

BI).
SEQUENCE {
under test Cell 2
d).
}
}
}
ETSI

GENERIC(f1)
}
}
measId[1] 1
}
}
Table 8.2.4.22.3.3-2A: MeasObjectEUTRA-GENERIC (Table 8.2.4.22.3.3-2)

MeasObjectEUTRA-GENERIC ::= SEQUENCE {
carrierFreq SEQUENCE {} Corresponding Downlink
EARFCN of the Band in
px_MFBI_FrequencyBan
d
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 2
AdditionalSpectrumEmission 1 (NS_01) Correct value for
Cell 2 is
transmitted.
}
ETSI

freqInfo SEQUENCE {
AdditionalSpectrumEmission 4 (NS_04) When in
connected mode,
UE shall ignore
the
AdditionalSpectru
mEmission value
if transmitted.
To check this a
incorrect value is
transmitted.
}
SEQUENCE {
AdditionalSpectrumEmission 5 (NS_05) When in
connected mode,
UE shall ignore
the
AdditionalSpectru
mEmission value
if transmitted.
To check this a
incorrect value is
transmitted.
}
}
}
8.2.4.23 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment

successful
8.2.4.23.1 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment
successful / Intra-band Contiguous CA
(1)
indicating a different E-UTRA cell }
ensure that {
when { UE detects handover failure and the source PCell is selectable }
then { UE successfully performs an RRC connection re-establishment procedure on source PCell
while releases the configured SCell }
}
(2)
indicating a different E-UTRA cell }
ensure that {
when { UE detects handover failure and the initial SCell is selectable }
then { UE successfully performs an RRC connection re-establishment procedure on original SCell
and the original SCell becomes the PCell while releases the configured SCell }
}
ETSI
5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.1.3]
The source eNB should, for some time, maintain a context to enable the UE to return in case of handover failure. After
having detected handover failure, the UE attempts to resume the RRC connection either in the source PCell or in
another cell using the RRC re-establishment procedure. This connection resumption succeeds only if the accessed cell is
prepared, i.e. concerns a cell of the source eNB or of another eNB towards which handover preparation has been
performed. The cell in which the re-establishment procedure succeeds becomes the PCell while SCells and STAGs, if
configured, are released..
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
1> else:
[32];
1> else:
33.401 [32];
2> stop timer T304;
...
[TS 36.331, clause 5.3.5.6]
The UE shall:
ETSI
[TS 36.331, clause 5.3.7.2]
...
...
1> reset MAC;
[TS 36.331, clause 5.3.7.4]
cases); and
...
ETSI
[TS 36.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
1> resume SRB1;
33.401 [32];
[32];
procedure ends;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
ETSI
8.2.4.23.1.3.1.1 Pre-test conditions
System Simulator:
- Cell 1 is the PCell and Cell 3 is the SCell
UE:
None.
Preamble:
columns marked "T1", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values

T0 dBm/15kHz -85 -91
RS EPRE Cell 3 (M3) satisfy exit condition for event
A3 (M3 < M1).
T1 dBm/15kHz -85 -79
event A3 (M3 > M1).
(NOTE 1).
Cell-specific
T3 dBm/15kHz -85 -79 Cell 3 (M3) satisfy entry condition for
RS EPRE
event A3 (M3> M1).
(NOTE 1).
RS EPRE selecting Cell 3 is guaranteed.
(NOTE 1).
ETSI

U-S Message
message on Cell 1.
configuration.
message on Cell 1.
8.2.4.23.1.3.2-1.
Cell 1 to order the UE to perform inter
8.2.4.23.1.3.2-3 should take place.
8.2.4.23.1.3.2-1.
message on Cell 1?
security on Cell 1.
11 The UE transmits an --> RRCConnectionReestablishment - =
message
resume existing radio bearer on Cell 1 and
configure Cell 3 as an SCell
message on Cell 1
configuration.
message on Cell 1.
8.2.4.23.1.3.2-1.
Cell 1 to order the UE to perform handover to
Cell 3.
ETSI

Table 8.2.4.23.1.3.2-3 should take place.
8.2.4.23.1.3.2-1.
message on Cell 3?
security on Cell 3.
message
message on Cell 3.

U-S Message
1 The UE attempts to perform the inter - - - -
Table 8.2.4.23.1.3.3-0: SystemInformationBlockType2 for Cell 1 and cell 3 (preamble and all the steps
in Table 8.2.4.23.3.2-2)

}
Table 8.2.4.23.1.3.3-1: RRCConnectionReconfiguration (steps 1 and 12, Table 8.2.4.23.1.3.2-2)
ETSI

sCellIndex-r10[1] 1
Cell 3
as used for Cell 3
}
monSCell-r10-f2
}

SEQUENCE {
Cell 3
}
}

GENERIC(f1)
GENERIC(f2)
}
}
measId[1] 1
}
}
ETSI
Table 8.2.4.23.1.3.3-6: ReportConfig-A3 (Table 8.2.4.18.1.3.3-5)
Derivation path: 36.508, Table 4.6.6-6

event SEQUENCE {
}
}
}
Table 8.2.4.23.1.3.3-7: MeasurementReport (steps 6 and 17, Table 8.2.4.23.1.3.2-2)

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListEUTRA ::= SEQUENCE (SIZE 1 entry
physCellId[1] physicalCellId of Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
servFreqId-r10 1
}
}
}
}
}
}
}
ETSI

Cell 3
ra-PreambleIndex 63
}
}
Table 8.2.4.23.1.3.3-10: RRCConnectionReestablishmentRequest (steps 9 and 20, Table 8.2.4.23.1.3.2-

2)

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}
Table 8.2.4.23.1.3.3-11: RRCConnectionReestablishment (steps 10 and 21, Table 8.2.4.23.1.3.2-2)

c1 CHOICE{
}
}
}
}

successful / Inter-band CA
- Cell 10 is Inactive SCells according to [18] cl. 6.3.4
ETSI

successful / Intra-band non-Contiguous CA
ETSI
8.3 Measurement configuration control and reporting

8.3.1 Intra E-UTRAN measurements
8.3.1.1 Measurement configuration control and reporting / Intra E-UTRAN
measurements / Event A1
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A1 with event based
periodical reporting }
ensure that {
when { Serving cell becomes better than absolute threshold plus hysteresis }
then { UE sends MeasurementReport message at regular intervals while entering conditions for
event A1 are satisfied }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and periodical measurement reporting triggered by event A1
ongoing}
ensure that {
when { Serving cell becomes worse than absolute threshold minus hysteresis }
then { UE stops sending MeasurementReport message }
}
5.5.4.1, 5.5.4.2 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
1> for each measId included in the measIdList within VarMeasConfig:
2> else:
...
3> if the corresponding measObject concerns EUTRA:
4> consider any neighbouring cell detected on the associated frequency to be applicable when the
concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for
this measId;
...
2> if the triggerType is set to ‘event’ and if the entry condition applicable for this event, i.e. the event
corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one
ETSI
or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for
this event within the VarMeasConfig, while the VarMeasReportList does not include an entry for this measId
(a first cell triggers the event):
3> include a measurement reporting entry within the VarMeasReportList for this measId;
3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;
3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;
3> initiate the measurement reporting procedure, as specified in 5.5.5;
or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering
taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the
event):
measId;
2> if the triggerType is set to ‘event’ and if the leaving condition applicable for this event is fulfilled for one or
more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for
all measurements after layer 3 filtering taken during of timeToTrigger defined within the
VarMeasurementConfiguration for this event:
3> remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;
3> if reportOnLeave is set to TRUE for the corresponding reporting configuration:
3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:
4> remove the measurement reporting entry within the VarMeasReportList for this measId;
4> stop the periodical reporting timer for this measId, if running;
2> upon expiry of the periodical reporting timer for this measId:
NOTE 2: The UE does not stop the periodical reporting with triggerType set to ‘event’ or to ‘periodical’ while the
corresponding measurement is not performed due to the serving cell RSRP being equal to or better than s-
Measure or due to the measurement gap not being setup.
[TS 36.331, clause 5.5.4.2]
The UE shall:
1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled;
InequalityA1-1 (Entering condition)
ETSI
Ms − Hys > Thresh
InequalityA1-2 (Leaving condition)
Ms + Hys < Thresh
The variables in the formula are defined as follows:
Ms is the measurement result of the serving cell, not taking into account any offsets.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigEUTRA for this
event).
Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Hys is expressed in dB.
Thresh is expressed in the same unit as Ms.
[TS 36.331, clause 5.5.5]
For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within
the MeasurementReport message as follows:
1> set the measId to the measurement identity that triggered the measurement reporting;
1> set the measResultServCell to include the quantities of serving cell;
1> if there is at least one applicable neighbouring cell to report:
...
1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;
1> stop the periodical reporting timer, if running;
1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the
reportAmount as defined within the corresponding reportConfig for this measId;
2> start the periodical reporting timer with the value of reportInterval as defined within the reportConfig for this
measId;
1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.
System Simulator:
- Cell 1
Preamble:
Table 8.3.1.1.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test
execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1" and "T2" are to be
applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
ETSI
Table 8.3.1.1.3.2-1: Power levels

Cell-specific RS dBm/15 -85 Power level is such that Ms + Hys < Thresh
T0
EPRE kHz
Cell-specific RS dBm/15 -59 Power level is such that entry condition for event
T1
EPRE kHz A1 is satisfied Ms – Hys > Thresh
Cell-specific RS dBm/15 -85 Power level is such that exit condition for event
T2
EPRE kHz A1 is satisfied Ms + Hys < Thresh
Note: The total test tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1)
and absolute UE measurement accuracy (TS 36.133 clause 9).

U-S Message
1 SS transmits an <-- RRCConnectionReconfiguration - -
including MeasConfig to setup intra LTE
measurement and reporting for event A1.
RCConnectionReconfigrationComplete omplete
message.
level according to row "T1" in table 8.3.1.1.3.2-
1.
4 Check: Does the UE transmit a --> MeasurementReport 1 P
MeasurementReport message to report event
A1 with the measured RSRP and RSRQ value
for Cell 1?
- EXCEPTION: Step 5 below is repeated until 3 - - - -
MeasurementReport messages are received
from the UE
MeasurementReport message, with the
measured RSRP and RSRQ value for Cell 1?
1.
7 Wait and ignore MeasurementReport - - - -
messages for 15 s to allow change of power
levels for Cell 1 and UE measurement.
8 Check: Does the UE attempt to transmit an - - 2 F
uplink message within the next 10s?
ETSI
Table 8.3.1.1.3.3-2: MeasConfig (step 1, Table 8.3.1.1.3.2-2)

GENERIC(f1)
}
reportConfig[1] ReportConfig-A1-H
}
measId[1] 1
}
}
Table 8.3.1.1.3.3-3: ReportConfig-A1-H (step 1, Table 8.3.1.1.3.2-2)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-4 ReportConfigEUTRA-A1(-72)

event SEQUENCE {
hysteresis 6 3dB
}
}
}
Table 8.3.1.1.3.3-4: MeasurementReport (steps 4 and 5, Table 8.3.1.1.3.2-2)

c1 CHOICE {
measId 1
measResultServCell ::= SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultNeighCells CHOICE {} Not present
}
}
}
}
}
ETSI

(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A2 with event based
periodical reporting }
ensure that {
when { Serving cell becomes worse than absolute threshold minus hysteresis }
then { UE sends MeasurementReport message at regular intervals while entering conditions for
event A2 are satisfied }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and periodical measurement reporting triggered by event A2
ongoing}
ensure that {
when { Serving cell becomes better than absolute threshold plus hysteresis }
then { UE stops sending MeasurementReport message }
}
5.5.4.1, 5.5.4.3 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
4> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned
cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;
...
this event within the VarMeasConfig while the VarMeasReportList does not include a measurement reporting
entry for this measId (a first cell triggers the event):
ETSI
measId;
event):
measId;
all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for
this event:
measId;
[TS 36.331, clause 5.5.4.3]
The UE shall:
InequalityA2-1 (Entering condition)
Ms + Hys < Thresh

InequalityA2-2 (Leaving condition)
Ms − Hys > Thresh

ETSI
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within the reportConfigEUTRA for this
event).
Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within the reportConfigEUTRA for
this event).
[TS 36.331, clause 5.5.5]
...
reportAmount as defined within the corresponding reportConfigfor this measId :
2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding
reportConfig for this measId;
...
System Simulator:
- Cell 1
Preamble:
Table 8.3.1.2.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test
ETSI

T0 -70 Power level is such that Ms > Thresh + Hys
Cell-specific RS dBm/15 -96 Power level is such that entry condition for event
T1
EPRE kHz A2 is satisfied Ms + Hys < Thresh
-70 Power level is such that exit condition for event
T2
A2 is satisfied Ms > Thresh + Hys
Note: The total tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1) and
absolute UE measurement accuracy (TS 36.133 clause 9).

U-S Message
including measConfig to setup intra LTE
message.
1.
A2 with the measured RSRP and RSRQ value
for Cell 1?
- EXCEPTION: Step 5 below is repeated until 3 - - - -
MeasurementReport messages are received
from the UE
MeasurementReport message, with the
measured RSRP and RSRQ value for Cell 1?
1.
messages for 15 s to allow change of power
levels for Cell 1 and UE measurement.
8 Check: Does the UE attempt to transmit an - 2 F
uplink message within the next 10s?
ETSI

GENERIC(f1)
}
}
measId[1] 1
}
}

event SEQUENCE {
hysteresis 6 3 dB
}
}
}
Table 8.3.1.2.3.3-4: MeasurementReport (steps 4 and 5, Table 8.3.1.2.3.2-2)
Derivation path: 36.508 table clause 4.6.1 table 4.6.1-5

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
ETSI

measurements / Two simultaneous events A3 (intra and inter-frequency
measurements)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurements configured for two event A3 at the same
time}
ensure that {
when { Entry condition for event A3 is not met }
then { UE does not send MeasurementReport }
}
(2)
time}
ensure that {
when { Neighbour becomes offset better than serving }
then { UE sends MeasurementReport with correct measId for event A3 }
}
5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
1> If the RRCConnectionReconfiguration message includes the measConfig:
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> if the corresponding reportConfig includes a purpose set to ‘reportStrongestCellsForSON’:
3> consider any neighbouring cell detected on the associated frequency to be applicable;
2> else if the corresponding reportConfig includes a purpose set to ‘reportCGI’:
3> consider any neighbouring cell detected on the associated frequency/ set of frequencies (GERAN) which
has a physical cell identity matching the value of the cellForWhichToReportCGI included in the
corresponding measObject within the VarMeasConfig to be applicable;
2> else:
3> if the corresponding measObject concerns E-UTRA:
this measId;
3> else if the corresponding measObject concerns UTRA or CDMA2000:
ETSI
4> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is
included in the cellsToAddModList defined within the VarMeasConfig for this measId (i.e. the cell is
included in the white-list);
3> else if the corresponding measObject concerns GERAN:
4> consider a neighbouring cell on the associated set of frequencies to be applicable when the concerned
cell matches the ncc-Permitted defined within the VarMeasConfig for this measId;
this event within the VarMeasConfig, while the VarMeasReportList does not include an measurement
reporting entry for this measId (a first cell triggers the event):
measId;
event):
measId;
this event:
measId;
2> if the purpose is included and set to ‘reportStrongestCells’ or to ‘reportStrongestCellsForSON’ and if a

(first) measurement result is available for one or more applicable cells:
ETSI
NOTE 1: If the purpose is set to ‘reportStrongestCells’, the UE initiates a first measurement report immediately
after the quantity to be reported becomes available for at least either serving cell or one of the applicable
cells. If the purpose is set to ‘reportStrongestCellsForSON’, the UE initiates a first measurement report
when it has determined the strongest cells on the associated frequency.
2> if the purpose is included and set to ‘reportCGI’ and if the UE acquired the information needed to set all
fields of cellGlobalId for the requested cell:
3> stop timer T321;
2> upon expiry of the T321 for this measId:
NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered and
periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].
[TS 36.331, clause 5.5.4.4]
The UE shall:
Inequality A3-1 (Entering condition)
Mn + Ofn + Ocn − Hys > Ms + Ofs + Ocs + Off
Inequality A3-2 (Leaving condition)
Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the frequency of the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Ofs is the frequency specific offset of the serving frequency (i.e. offsetFreq as defined within measObjectEUTRA
corresponding to the serving frequency).
Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the serving frequency), and is set to zero if not configured for the serving cell.
ETSI
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA for this event).
Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Ofs, Ocs, Hys, Off are expressed in dB.
[TS 36.331, clause 5.5.5]
UE EUTRAN
MeasurementReport
Figure 5.5.5-1: Measurement reporting
The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN.
2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with
the following:
3> if the triggerType is set to ‘event’:
4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this
measId;
3> else:
4> include the applicable cells for which the new measurement results became available since the last
periodical reporting or since the measurement was initiated or reset;
NOTE: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency)
depends on the measurement configuration i.e. the reportInterval. The related performance requirements
are specified in TS 36.133 [16].
3> for each cell that is included in the measResultNeighCells, include the physCellId;
3> if the triggerType is set to ‘event’; or the purpose is set to ‘reportStrongestCells’ or to

‘reportStrongestCellsForSON’:
4> for each included cell, include the layer 3 filtered measured results in accordance with the
reportConfig for this measId, ordered as follows:
5> if the measObject associated with this measId concerns E-UTRA:
6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the
concerned reportConfig in order of decreasing triggerQuantity, i.e. the best cell is included
first;
5> else:
ETSI
6> set the measResult to the quantity as configured for the concerned RAT within the
quantityConfig in order of decreasing quantity, i.e. the best cell is included first;
3> else if the purpose is set to ‘reportCGI’:
4> if the mandatory present fields of the cellGlobalId for the cell indicated by the
cellForWhichToReportCGI in the associated measObject have been obtained:
5> include the cgi-Info containing all the fields that have been successfully acquired;
reportAmount as defined within the corresponding reportConfig for this measId:
1> else:
2> if the triggerType is set to ‘periodical’:
3> remove the entry within the VarMeasReportList for this measId;
3> remove this measId from the measIdList within VarMeasConfig;
1> if the measured results are for CDMA2000 HRPD:
2> set the preRegistrationStatusHRPD to the UE’s CDMA2000 upper layer’s HRPD preRegistrationStatus;
1> if the measured results are for CDMA2000 1xRTT:
2> set the preRegistrationStatusHRPD to ‘FALSE’;
1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends;
System Simulator:
UE:
None.
Preamble:
Table 8.3.1.3.3.2-1 illustrates the downlink power levels to be applied for Cell 1, Cell 2 and Cell 3 at various time
instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1"and
"T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts
in this clause.
ETSI

(DL only) (DL only)
T0 Cell-specific dBm/15kHz -85 -91 Off Power levels are such that entry condition for
RS EPRE event A3 (measId 1 & 2) is not satisfied:
RS EPRE event A3 (measId 1) is satisfied:
T2 Cell-specific dBm/15kHz -85 Off -73 Power levels are such that entry condition for

U-S Message
including MeasConfig to setup intra E-UTRAN
measurement and reporting for two event A3
(measId 1 and measId 2) (intra and inter
frequency measurement).
message.
3 Check: Does the UE transmit a --> MeasurementReport 1 F
MeasurementReport message within the next
10s?
1.
A3 (measId 1) with the measured RSRP value
for Cell 2?
1.
7 Void - - - -
for Cell 3?
ETSI

GENERIC(f1)
GENERIC(f2)
}
}
measIdToAddModList SEQUENCE (SIZE 2 entries
measId[1] 1
measId[2] 2
}
}
Derivation path: 36.508 clause 4.6.6 table 4.6.6-6 ReportConfigEUTRA-A3

event SEQUENCE {
timeToTrigger ms0
}
}
reportQuantity sameAsTriggerQuantity
}
ETSI

c1 CHOICE {
measId 1
measResultServCell::= SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
MeasResultEUTRA ::= SEQUENCE (SIZE Report Cell 2
physCellId physCellId of the Cell 2.
measResult SEQUENCE{
rsrpResult (0..97)
rsrqResult Not present
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}
ETSI
8.3.1.3a Measurement configuration control and reporting / Intra E-UTRAN

measurements / Two simultaneous events A3 (intra and inter-frequency
measurements) / RSRQ based measurements
(1)
with { UE in E-UTRA RRC_CONNECTED state, measurements configured for two event A3 at the same time
and triggerQuantity set to rsrq }
ensure that {
}
(2)
with { UE in E-UTRA RRC_CONNECTED state, measurements configured for two event A3 at the same time
and triggerQuantity set to rsrq }
ensure that {
}
5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> if the corresponding reportConfig includes a purpose set to 'reportStrongestCellsForSON':
2> else if the corresponding reportConfig includes a purpose set to 'reportCGI':
2> else:
4> if the ue-RxTxTimeDiffPeriodical, eventA1 or eventA2 is configured in the corresponding

reportConfig:
5> consider only the serving cell to be applicable;
4> else:
ETSI
concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig
for this measId;
NOTE 0: The UE may also consider a neighbouring cell on the associated UTRA frequency to be applicable when
the concerned cell is included in the csg-allowedReportingCells within the VarMeasConfig for this
measId, if configured in the corresponding measObjectUTRA (i.e. the cell is included in the range of
physical cell identities for which reporting is allowed).
2> if the triggerType is set to 'event' and if the entry condition applicable for this event, i.e. the event
measId;
event):
measId;
2> if the triggerType is set to 'event' and if the leaving condition applicable for this event is fulfilled for one or
this event:
measId;
ETSI
2> if the purpose is included and set to 'reportStrongestCells' or to 'reportStrongestCellsForSON' and if a (first)
measurement result is available for one or more applicable cells:
NOTE 1: If the purpose is set to 'reportStrongestCells', the UE initiates a first measurement report immediately
cells. If the purpose is set to 'reportStrongestCellsForSON', the UE initiates a first measurement report
2> if the purpose is included and set to 'reportCGI' and if the UE acquired the information needed to set all
fields of cgi-Info for the requested cell:
3> stop timer T321;
NOTE 2: The UE does not stop the periodical reporting with triggerType set to 'event' or to 'periodical' while the
[TS 36.331, clause 5.5.4.4]
The UE shall:
Inequality A3-1 (Entering condition):
Inequality A3-2 (Leaving condition):
ETSI
[TS 36.331, clause 5.5.5]
UE EUTRAN
MeasurementReport
the following:
3> if the triggerType is set to 'event':
measId;
3> else:
3> if the triggerType is set to 'event'; or the purpose is set to 'reportStrongestCells' or to

'reportStrongestCellsForSON':
ETSI
first;
5> else:
quantityConfig in order of either decreasing quantity for UTRA and GERAN or increasing
quantity for CDMA2000 pilotStrength, i.e. the best cell is included first;
3> else if the purpose is set to 'reportCGI':
4> if the mandatory present fields of the cgi-Info for the cell indicated by the cellForWhichToReportCGI
in the associated measObject have been obtained:
5> if the cell broadcasts a CSG identity:
6> include the csg-Identity;
6> include the csg-MemberStatus and set it to 'member' if the cell is a CSG member cell;
5> if the 'si-RequestForHO' is configured within the reportConfig associated with this measId:
6> include the cgi-Info containing all the fields that have been successfully acquired, except for
the plmn-IdentityList;
5> else:
1> if the ue-RxTxTimeDiffPeriodical is configured within the corresponding reportConfig for this measId;
2> set the ue-RxTxTimeDiffResult to the measurement result provided by lower layers;
2> set the currentSFN;
1> else:
2> if the triggerType is set to 'periodical':
2> set the preRegistrationStatusHRPD to the UE's CDMA2000 upper layer's HRPD preRegistrationStatus;
2> set the preRegistrationStatusHRPD to 'FALSE';
ETSI
System Simulator:
UE:
None.
Preamble:
Table 8.3.1.3a.3.2-1 illustrates the downlink power levels to be applied for Cell 1, Cell 2 and Cell 3 at various time
in this clause.

(DL only) (DL only)
T0 Cell-specific
dBm/15 -85 -91 "Off" Power levels are such that entry condition for
RS EPRE kHz event A3 (measId 1 & 2) is not satisfied:
RSRQ dB -8 -14 - Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off
Noc dBm/15 -90 -90 -100
kHz
T1 Cell-specific dBm/15 -91 -85 "Off" Power levels are such that entry condition for
RS EPRE kHz event A3 (measId 1) is satisfied:
RSRQ dB -14 -8 - Mn + Ofn + Ocn − Hys > Ms + Ofs + Ocs + Off
T2 Cell-specific dBm/15 -91 "Off" -85 Power levels are such that entry condition for
RS EPRE kHz event A3 (measId 2) is satisfied:
RSRQ dB -12.33 - -3.76 Mn + Ofn + Ocn − Hys > Ms + Ofs + Ocs + Off
NOTE 1: Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1.
ETSI

U-S Message
Cell 1 including MeasConfig to setup intra E-
UTRAN measurement and reporting for two
event A3 (measId 1 and measId 2) (intra and
inter frequency measurement).
message on Cell 1.
MeasurementReport message on Cell 1 within
the next 10s?
3A The SS notifies the UE of change of System <-- Paging - -
information 3. The systemInfoValueTag in the
signal level according to row "T1" in table
8.3.1.3a.3.2-1.
MeasurementReport message on Cell 1 to
report event A3 (measId 1) with the measured
RSRP and RSRQ values for Cell 2?
signal level according to row "T2" in table
8.3.1.3a.3.2-1.
report event A3 (measId 2) with the measured
RSRP and RSRQ values for Cell 3?
ETSI

GENERIC(f1)
GENERIC(f2)
}
reportConfig[1] ReportConfigEUTRA-A3-
RSRQ
}
measId[1] 1
measId[2] 2
}
}
Table 8.3.1.3a.3.3-3: ReportConfigEUTRA-A3-RSRQ (Table 8.3.1.3a.3.3-2)

triggerQuantity rsrq
si-RequestForHO-r9 Not present
ue-RxTxTimeDiffPeriodical-r9 Not present
}
Table 8.3.1.3a.3.3-3a: SystemInformationBlockType3 for Cell 1 (Step 3A, Table 6.1.2.18.3.2-2)

q-QualMin-r9 -30 dB
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
cgi-Info Not present
measResult SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.3a.3.3-6: Paging (step 3A, Table 8.3.1.3a.3.2-2)

}

measurements / Periodic reporting (intra and inter-frequency measurements)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for periodic reporting of intra
frequency cells and inter frequency cells on specified frequency }
ensure that {
when { The UE receives reference signal power for cells on the serving frequency and cells on the
frequency where measurements are configured }
then { UE sends MeasurementReport message at regular intervals for these cells }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and a MeasurementReport message for a configured periodic
measurement reporting of intra and inter frequency cells was sent }
ensure that {
when { A previously reported cell become unavailable or the UE receives reference signal power on
a reported frequency for a cell which was previously not reported }
then { UE sends MeasurementReport message at regular intervals for the available intra and inter
frequency cells }
ETSI
(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting ongoing}
ensure that {
when { The UE receives a RRCConnectionReconfiguration message removing measIds for periodic
reporting }
then { UE stops sending MeasurementReport messages for these measIds }
}
5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.2.2]
The UE shall:
1> for each measId value included in the received measIdToRemoveList that is part of the current UE configuration
in varMeasConfig:
2> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;
2> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
this measId;

ETSI
...
[TS 36.331, clause 5.5.5]
For the measId for which the measurement reporting procedure was triggered, the UE shall set the measuredResults
within the MeasurementReport message as follows:
2> set the measResultsNeighCells to include the best neighbouring cells up to maxReportCells in accordance
with the following:
measId;
3> else:
3> for each cell that is included in the measResultsNeighCells, include the physCellId;

first;
ETSI
1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than to
reportAmount as defined corresponding reportConfig for this measId:
...
1> submit the MEASUREMENT REPORT message to lower layers for transmission, upon which the procedure
ends.
System Simulator:
- Cell 1, Cell 2, Cell 3, Cell 4 and Cell 6
UE:
None.
Preamble:
Parameter Unit Cell 1 Cell 2 Cell 3 Cell 4 Cell 6 Remark

(DL (DL (DL (DL
only) only) only) only)
T0 Cell-specific dBm/ -85 -91 -85 Off Off
RS EPRE 15kH
z
T1 Cell-specific dBm/ -85 Off -85 -91 Off
RS EPRE 15kH
z
T2 Cell-specific dBm/ -85 Off Off -91 -85
RS EPRE 15kH
z
ETSI

U-S Message
measurements and periodical reporting for
intra and inter frequency cells.
message.
2A Wait and ignore MeasurementReport - - - -
messages for 8 s to allow for the switching of
the cells and UE to measure the neighbouring
cells.
- EXCEPTION: In parallel to events described in
step 3 the steps specified in table 8.3.1.4.3.2-
3, 8.3.1.4.3.2-4 and the table 8.3.1.4.3.2-4A
shall take place
3 Wait for 30 s to ensure that the UE performs a - - 1 -
periodical intra frequency reporting and a
periodical inter frequency reporting.
4 SS sets the cell-specific reference signal levels - - - -
and switches Cell 2 “Off” and Cell 4 “On”
cells and the UE measurement.
4, 8.3.1.4.3.2-4A and table 8.3.1.4.3.2-5 shall
take place.
6 Wait for 30 s to ensure that the UE performs a - - 1, 2 -
and switches Cell 3 “Off” and Cell 6 ”On”
cells and UE measurement.
- EXCEPTION: In parallel to events described in - - - -
steps 9 to 11 the steps specified in table
8.3.1.4.3.2-5 8.3.1.4.3.2-6 and the table
8.3.1.4.3.2-6A shall take place
including measConfig to remove measIds for
periodical reporting.
message
uplink message for the next 10s?
ETSI

U-S Message
- EXCEPTION: After the 1st message is - - - -
received, step 1 below shall be repeated every
time the duration indicated in the IE
reportInterval has elapsed
MeasurementReport message to perform
periodical intra frequency reporting for Cell
2(NOTE1)?
NOTE 1: In the first report UE may not include measResultNeighCells for cell 2.

U-S Message
reportInterval has elapsed.
periodical inter frequency reporting for Cell
3(NOTE2)?
NOTE 2: In the first report UE may not include measResultNeighCells for the cell 3.
Table 8.3.1.4.3.2-4A: Parallel behaviour

U-S Message
periodical inter frequency reporting configured
for cell 6 and without measResultNeighCells
for the cell 6?

U-S Message
- EXCEPTION: Step 1 below shall be repeated - - - -
every time the duration indicated in the IE
1 Check: Does the UE transmit a --> MeasurementReport 1, 2 P
periodical intra frequency reporting for Cell 4(
NOTE3)?
ETSI

U-S Message
- EXCEPTION: Step 1 below shall be repeated
periodical inter frequency reporting for Cell 6 (
NOTE4)?

U-S Message
1 Check: Does the UE transmit a --> MeasurementReport - -
periodical inter frequency reporting configured
for the cell 3?
ETSI

GENERIC(f1)
GENERIC(f2)
GENERIC(f3)
}
reportConfigToAddModiList SEQUENCE (SIZE 1 entry
reportConfigId[1] IdReportConfig-
PERIODICAL
reportConfig[1] ReportConfigEUTRA-
PERIODICAL
}
measId[1] 1
PERIODICAL
measId[2] 2
PERIODICAL
measId[3] 3
PERIODICAL
}
}
Table 8.3.1.4.3.3-3 Void

measIdToRemoveList SEQUENCE (SIZE 3 entries
MeasId[1] 1
MeasId[2] 2
MeasId[3] 3
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
physCellId [1] physicalCellIdentity-Cell2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.4.3.3-7A: MeasurementReport (step 1, Table 8.3.1.4.3.2-4A)

c1 CHOICE {
measId 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 3
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.4.3.3-9: MeasurementReport (step 1, Table 8.3.1.4.3.2-6A)

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}

measurements / Two simultaneous event A3 (intra-frequency measurements)
(1)
time}
ensure that {
}
ETSI
(2)
time}
ensure that {
}
5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
this measId;
ETSI
measId;
event):
measId;
this event:
measId;

3> stop timer T321;
ETSI
[TS 36.331, clause 5.5.4.4]
The UE shall:
[TS 36.331, clause 5.5.5]
ETSI
UE EUTRAN
MeasurementReport
the following:
measId;
3> else:

first;
5> else:
ETSI
1> else:
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) on Cell 1 according to [18]
Table 8.3.1.5.3.2-1 illustrates the downlink power levels to be applied for Cell 1 and Cell 2 at various time instants of
the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1"and "T2" are to
be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this
clause.

(DL
only)
T0 Cell-specific RS dBm/1 -85 -110 Power levels are such that entry condition for event A3
EPRE 5kHz (measId 1 & 2) is not satisfied:
EPRE 5kHz (measId 1) is satisfied:
EPRE 5kHz (measId 2) is satisfied:
ETSI

U-S Message
(measId 1 and measId 2) with different
parameters.
RCConnectionReconfigurationComplete omplete
message.
10s?
1.
for Cell 2?
1.
for Cell 2?
ETSI

GENERIC(f1)
}
reportConfigToAddModList SEQUENCE (SIZE 2 entries
reportConfigId[1] 1
reportConfig[1] ReportConfig-A3-
Lowerthreshold
reportConfigId[2] 2
Higherthreshold
}
measId[1] 1
reportConfigId[1] IdReportConfig-A3-
Lowerthreshold
measId[2] 2
Higherthreshold
}
}
Table 8.3.1.5.3.3-3: ReportConfig-A3-Lowerthreshold (step 1, Table 8.3.1.5.3.2-2)

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset -20 -10 dB
}
}
timeToTrigger ms0
}
}
}
ETSI
Table 8.3.1.5.3.3-4: ReportConfig-A3-Higherthreshold (step 1, Table 8.3.1.5.3.2-2)

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset 0 0 dB
}
}
timeToTrigger ms0
}
}
}

c1 CHOICE {
MeasResults ::= SEQUENCE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
physCellId PhysCellId of the Cell 2.
rsrpResult (0..97)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}

measurements / Two simultaneous events A2 and A3 (inter-frequency
measurements)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurements configured for event A2 and event A3 }
ensure that {
when { Serving becomes worse than threshold }
then { UE sends MeasurementReport for event A2 }
}
(2)
ensure that {
}
5.5.4.1, 5.5.4.3, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
ETSI
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:

reportConfig:
4> else:
for this measId;
measId;
event):
measId;
this event:
measId;
ETSI
3> stop timer T321;
NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered
and periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].
[TS 36.331, clause 5.5.4.3]
The UE shall:
Ms + Hys < Thresh
Ms − Hys > Thresh
ETSI
event).
[TS 36.331, clause 5.5.4.4]
The UE shall:
[TS 36.331, clause 5.5.5]
the following:
ETSI
measId;
3> else:

first;
5> else:
System Simulator:
- Cell 1 and Cell 3
UE:
None.
Preamble:
ETSI
clause.
Table 8.3.1.6.3.2-1 : Power levels

(DL
only)
EPRE 5kHz and event A3 is not satisfied:
Ms − Hys > Thresh
AND
T1 Cell-specific RS dBm/1 -93 -105 Power level of Cell 1 is such that entry condition for
EPRE 5kHz event A2 is satisfied:
Ms + Hys < Thresh
AND
Power levels of Cell 1 and Cell 3 are such that entry
condition for event A3 is not satisfied:
T2 Cell-specific RS dBm/1 -85 -73 Power levels are such that entry condition for event A3 is
EPRE 5kHz satisfied:

U-S Message
measurement and reporting for event A2 and
event A3 (inter frequency measurement)
RRCConnectionReconfigrationComplete omplete
message.
10s?
level according to row "T1" in table 8.3.1.6.32.-
1.
A2 with the measured RSRP value for Cell 1?
level according to row "T2" in table 8.3.1.6.32.-
1.
ETSI

GENERIC(f1)
GENERIC(f2)
}
}
measId[1] 1
measId[2] 2
}
}
Table 8.3.1.6.3.3-3: ReportConfig-A2 (step 1, Table 8.3.1.6.3.2-2)

event SEQUENCE {
hysteresis 6 3 dB
}
}
}

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset 0 0 dB
}
}
}
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultEUTRA ::= SEQUENCE (SIZE Report Cell 3
rsrpResult (0..97)
}
}
}
}
}
}
}
}

measurements / Blacklisting
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A3 reporting }
ensure that {
when { Blacklisted neighbour cell satisfies entry condition for event A3 }
then { It is not considered in event evaluation and UE does not send MeasurementReport message }
}
ETSI
(2)
with { UE in E-UTRA RRC_CONNECTED state and measurement reporting triggered by event A3 is ongoing}
ensure that {
when { Blacklisted neighbour cell satisfies entry condition for event A3 }
then { It is not considered in measurement reporting }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.5.1, 5.5.4.1,
and 5.5.5.
[TS 36.331, clause 5.5.1]
The UE reports measurement information in accordance with the measurement configuration as provided by E-
UTRAN. E-UTRAN provides the measurement configuration applicable for a UE in RRC_CONNECTED state by
means of dedicated signalling, i.e. using the RRCConnectionReconfiguration message.
...
- For intra-frequency and inter-frequency measurements a measurement object is a single E-UTRA carrier
frequency. Associated with this carrier frequency, E-UTRAN can configure a list of cell specific offsets and a
list of ‘blacklisted’ cells. Blacklisted cells are not considered in event evaluation or measurement reporting.
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
this measId;
corresponding with the eventId of the corresponding reportConfig within VarMeaConfig, is fulfilled for one
this event within the VarMeasConfig while the VarMeasReportList does not include a measurement reporting
entry for this measId (a first cell triggers the event):
measId;
ETSI
event):
measId;
this event:
measId;
[TS 36.331, clause 5.5.5]
1> set the IE measId to the measurement identity that triggered the measurement reporting;
with the following:
measId;

4> for each included cell include the layer 3 filtered measured results in accordance with the
reportConfigList for this measId, ordered as follows:
first;
ETSI
...
System Simulator:
- Cell 1, Cell 2 and Cell 4:
- Cell 1 is the serving cell
- Cell 2 and Cell 4 are intra-frequency neighbour cells
UE:
None.
Preamble:
instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1" and
in this clause.
Table 8.3.1.7.3.2-1 : Power level

(DL only) (DL only)
T0 -85 -97 -97 Power levels are such that that exit condition
for event A3 is satisfied for all cells (M2 + Hys
< M1 + Off and M4 + Hys < M1 + Off) with all
offset parameters set to 0 dB.
T1 Cell-specific dBm/ -85 -79 -97 Power level of Cell 2 is set such that
RS EPRE 15kH measurement results for Cell 1 (M1) and Cell 2
z (M2) satisfy entry condition for event A3 (M2 -
Hys > M1 + Off).
T2 -85 -79 -79 Power level of Cell 4 is set such that
measurement results for Cell 1 (M1) and Cell 4
(M4) satisfy entry condition for event A3 (M4 -
Hys > M1 + Off).
ETSI
Table 8.3.1.7.3.2-2 : Main behaviour

U-S Message
including measConfig to setup intraLTE
message.
8.3.1.7.3.2.-1.
4 Check: does the UE transmit a - MeasurementReport 1 F
MeasurementReport messages within the next
10s?
8.3.1.7.3.2.-1.
6 Check: does the UE transmit a --> MeasurementReport 2 P
A3 with the measured RSRP values for Cell 1
and Cell 4 without Cell 2 results?
including measConfig to remove Cell 2 from
the blacklisted cell list.
message
- EXCEPTION: Steps 8Aa1 to 8Ab1 describe a - - - -
behaviour happens.
8A IF the UE detects event A3 for Cell 4 before --> MeasurementReport - -
a1 event A3 for Cell 2 THEN the UE may transmit
and Cell 4.
8A IF the UE detects event A3 for Cell 2 before --> MeasurementReport - -
b1 event A3 for Cell 4 THEN the UE may transmit
and Cell 2.
9 Check: does the UE transmit a --> MeasurementReport 1, 2 P
A3 with the measured RSRP values for Cell 1,
Cell 2 and Cell 4?
ETSI

GENERIC(f1)
}
}
measId[1] 1
}
}
Table 8.3.1.7.3.3-3; MeasObjectEUTRA-GENERIC (Table 8.3.1.7.3.3-2)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-3 MeasObjectEUTRA-GENERIC(f1)

MeasObjectEUTRA-GENERIC(f1) ::= SEQUENCE {
blackCellsToAddModList ::= SEQUENCE (SIZE 1 entry Add Cell 2
(1..maxCellMeas)) OF SEQUENCE {
cellIndex[1] 1
physCellIdRange[1] physicalCellIdentity-Cell2
}
}
Table 8.3.1.7.3.3-4: ReportConfig-A3 (Table 8.3.1.7.3.3-2)

maxReportCells 3 Report Cell 1, Cell
2 and Cell 4
reportInterval Not present
}
ETSI

GENERIC(f1)
}
}
Table 8.3.1.7.3.3-7: MeasObjectEUTRA-GENERIC (Table 8.3.1.7.3.3-6)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-3 MeasObjectEUTRA-GENERIC(f1)

MeasObjectEUTRA-GENERIC(f1) ::= SEQUENCE {
blackCellsToRemoveList ::= SEQUENCE (SIZE 1 entry Remove Cell 2
(1..maxCellMeas)) OF SEQUENCE {
CellIndex[1] 1
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListEUTRA ::= SEQUENCE (SIZE Report Cell 2 and
(1..maxCellReport)) OF SEQUENCE { Cell 4
rsrpResult (0..97)
rsrqResult (0..34)
}
physCellId[2] physicalCellIdentity-Cell4
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Note: IE “measresult” for cells 2 and 4 can appear in any order (i.e. cell 2 then cell 4 or cell 4 then cell 2)
ETSI
Table 8.3.1.7.3.3-10: MeasurementReport (step 8Aa1, Table 8.3.1.7.3.2-2)

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.7.3.3-11: MeasurementReport (step 8Ab1, Table 8.3.1.7.3.2-2)

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

measurements / Handover / IE measurement configuration present
(1)
with { UE having completed the radio bearer establishment, initial security activation procedure and
performed the intra frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and a
measConfig for removing intra frequency measurement }
then { UE performs intra frequency handover and stops the intra frequency measurement }
}
5.5.2.2, 5.5.2.6 and 5.5.4.4.
[TS 36.331, clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
1> else:
[32];
1> else:
33.401 [32];
2> stop timer T304;
[TS 36.331, clause 5.5.2.2]
The UE shall:
1> for each measId included in the received measIdToRemoveList that is part of the current UE configuration in
varMeasConfig:
ETSI
[TS 36.331, clause 5.5.2.6]
The UE shall:
1> for each reportConfigId included in the received reportConfigToRemoveList that is part of the current UE
configuration in varMeasConfig:
2> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
2> remove all measId associated with the reportConfigId from the measIdList within the VarMeasConfig, if any;
2> if a measId is removed from the measIdList:
NOTE: The UE does not consider the message as erroneous if the reportConfigToRemoveList includes any
reportConfigId value that is not part of the current UE configuration.
[TS 36.331, clause 5.5.4.4]
The UE shall:
ETSI
System Simulator:
UE:
None.
Preamble:

Cell-specific RS dBm/15k measurement re85sults for Cell 1 (M1) and
T0 -85 -91
A3 (M2 < M1).
T1 -85 -79
A3 (M2 > M1).
ETSI

U-S Message
message on Cell 1 to confirm the setup of intra
frequency measurement.
a measConfig on Cell 1 for removing event A3
reporting, to order the UE to perform intra
message on Cell 2?
perform event A3 reporting during the next
30s?

GENERIC(f1)
}
}
measId[1] 1
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Derivation Path: 36.508, Table 4.6.1-8, condition HO and MEAS

measObjectToRemoveList SEQUENCE (SIZE (1.. 1 entry
maxObjectId)) OF SEQUENCE {
}
reportConfigToRemoveList SEQUENCE (SIZE 1 entry
}
measIdToRemoveList SEQUENCE (SIZE 1 entry
measId[1] 1
}
}
ETSI

Cell 2
}

measurements / Intra-frequency handover / IE measurement configuration
not present
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and not
including a measConfig }
then { UE performs intra frequency handover and continues the intra frequency measurement }
}
(2)
performed the inter frequency measurement }
ensure that {
then { UE performs intra frequency handover and continues the inter frequency measurement after
the activation of the measurement gaps }
}
5.5.6.1.
[TS 36.331, clause 5.5.4.4]
The UE shall:
ETSI
[TS 36.331, clause 5.5.6.1]
E-UTRAN applies the handover procedure as follows:
- when performing the handover procedure, as specified in 5.3.5.4, ensure that a measObjectId corresponding to
the handover target carrier frequency is configured as a result of the procedures described in this sub-clause and
in 5.3.5.4;
...
The UE shall:
3> remove this measId from the measIdList within VarMeasConfig:
1> if the procedure was triggered due to inter-frequency handover or successful re-establishment to an inter-
frequency cell, update the measId values in the measIdList within VarMeasConfig as follows:
2> if a measObjectId value corresponding to the target carrier frequency exists in the measObjectList within
VarMeasConfig:
3> for each measId value in the measIdList:
4> if the measId value is linked to the measObjectId value corresponding to the source carrier frequency:
5> link this measId value to the measObjectId value corresponding to the target carrier frequency;
4> else if the measId value is linked to the measObjectId value corresponding to the target carrier
frequency:
5> link this measId value to the measObjectId value corresponding to the source carrier frequency;
2> else:
3> remove all measId values that are linked to the measObjectId value corresponding to the source carrier
frequency;
1> remove all measurement reporting entries within VarMeasReportList;
1> reset the periodical reporting timer or timer T321, whichever one is running, as well as associated information
(e.g. timeToTrigger) for all measId;
1> release the measurement gaps, if activated;
NOTE: If the UE requires measurement gaps to perform inter-frequency or inter-RAT measurements, the UE
resumes the inter-frequency and inter-RAT measurements after the E-UTRAN has setup the measurement
gaps.
ETSI
System Simulator:
UE:
None.
Preamble:
columns marked "T1", "T2","T3" and "T4" are to be applied subsequently. The exact instants on which these values

(DL
only)
T0 -85 "Off" -97 (M3) do not satisfy entry condition for event A3
RS EPRE Hz
(M3 < M1).
(NOTE 1)
T1 -85 "Off" -73 (M3) satisfy entry condition for event A3 (M3 >
RS EPRE Hz
M1).
(NOTE 1)
T2 -85 -79 "Off" (M2) satisfy entry condition for event A3 (M2 >
RS EPRE Hz
M1).
(NOTE 1)
T3 "Off" -85 -73 (M3) satisfy entry condition for event A3 (M3 >
RS EPRE Hz
M2).
(NOTE 1)
T4 -79 -85 "Off" (M2) satisfy entry condition for event A3 (M1 >
RS EPRE Hz
M2).
(NOTE 1)
ETSI

U-S Message
setup intra and inter frequency measurements
on Cell 1.
message to confirm the setup of intra and inter
frequency measurements on Cell 1.
- EXCEPTION: Steps 3a1 to 3a2 describe - - - -
supported.
3a1 IF pc_FeatrGrp_25 THEN the SS changes Cell - - - -
1, Cell 2 and Cell 3 parameters according to
the row "T1" in table 8.3.1.9.3.2-1.
3a2 The UE transmits a MeasurementReport --> MeasurementReport - -
message on Cell 1 to report event A3 for Cell
3.
8.3.1.9.3.2-1.
2.
without a measConfig message on Cell 1, to
handover to Cell 2.
message on Cell 2?
supported.
8a1 IF pc_FeatrGrp_25 THEN the SS transmits an <-- RRCConnectionReconfiguration - -
activate the measurement gaps on Cell 2.
8a2 The UE transmits an --> RRCConnectionReconfigurationC - -
message to confirm the activation of the
measurement gaps on Cell 2.
8a3 The SS changes Cell 1, Cell 2 and Cell 3 - - - -
8.3.1.9.3.2-1.
8a4 Check: Does the UE transmit a --> MeasurementReport 2 P
report event A3 for Cell 3?
8.3.1.9.3.2-1.
ETSI

measObjectToAddModList SEQUENCE (SIZE 1entry or 2 entries number of entry
(1..maxObjectId)) OF SEQUENCE { depending on the
UE capability
GENERIC(f1)
measObjectId[2] IdMeasObject-f2 pc_FeatrGr
p_25
measObject[2] MeasObjectEUTRA- pc_FeatrGr
GENERIC(f2) p_25
}
}
measIdToAddModList SEQUENCE (SIZE 1entry or 2 entries number of entry
(1..maxMeasId)) OF SEQUENCE { depending on the
UE capability
measId[1] 1 Intra frequency
measId[2] 2 Inter frequency pc_FeatrGr
p_25
p_25
reportConfigId[2] IdReportConfig-A3 pc_FeatrGr
p_25
}
}
ETSI
Table 8.3.1.9.3.3-3: MeasurementReport (step 3a2 and 8a4, Table 8.3.1.9.3.2-2)

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

Cell 2
}
Table 8.3.1.9.3.3-7: RRCConnectionReconfiguration (step 8a1, Table 8.3.1.9.3.2-2)

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
8.3.1.9a Measurement configuration control and reporting / Intra Frequency

measurements / Intra-frequency handover / IE measurement configuration
not present / Single Frequency operation
(1)
ensure that {
then { UE performs intra frequency handover and continues the intra frequency measurement }
}
}
5.5.6.1.
[TS 36.331, clause 5.5.4.4]
The UE shall:
[TS 36.331, clause 5.5.6.1]
ETSI
in 5.3.5.4;
...
The UE shall:
VarMeasConfig:
frequency:
2> else:
frequency;
gaps.
System Simulator:
- Cell 1, Cell 2.
UE:
None.
Preamble:
ETSI
column marked "T1 " and "T2" are to be applied subsequently. The exact instants on which these values shall be

T0 -85 off (M2) satisfy entry condition for event A3 (M2 >
RS EPRE Hz
M1).
(NOTE 1)
T1 -85 -79 (M2) satisfy entry condition for event A3 (M2 >
RS EPRE Hz
M1).
(NOTE 1)
T2 -79 -85 (M2) satisfy entry condition for event A3 (M1 >
RS EPRE Hz
M2).
(NOTE 1)

U-S Message
setup intra frequency measurements on Cell 1.
message to confirm the setup of intra
1.
2.
without a measConfig message on Cell 1, to
handover to Cell 2.
message on Cell 2?
1.
ETSI

measObjectToAddModList SEQUENCE (SIZE 1entry
GENERIC(f1)
}
}
measIdToAddModList SEQUENCE (SIZE 1entry
measId[1] 1 Intra frequency
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
Table 8.3.1.9a.3.3-5: MobilityControlInfo (Table 8.1.3.9.3.3-4)

Cell 2
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

measurements / Inter-frequency handover / IE measurement configuration
not present
(1)
performed the intra frequency and inter frequency measurements }
ensure that {
indicating a different E-UTRA frequency and not including a measConfig }
then { UE performs inter frequency handover, continues the intra frequency measurement and
continues inter frequency measurement after the activation of the measurement gaps }
}
ETSI
[TS 36.331, clause 5.5.6.1]
the handover target carrier frequency is configured as a result of the procedures described in this subclause and
in 5.3.5.4;
...
The UE shall:
VarMeasConfig
5> link this measId value to the measObjectId value corresponding to the target carrierfrequency;
frequency:
2> else:
frequency;
gaps.
System Simulator:
UE:
None.
ETSI
Preamble:
columns marked "T1", "T2","T3", and "T4" are to be applied subsequently. The exact instants on which these values

(DL (DL
only) only)
that measurement results for Cell 1
Cell-specific RS dBm/15 (M1) and Cell 2 (M2) do not satisfy
T0 -85 -91 -97 "Off"
EPRE kHz entry condition for event A3 (M2 <
M1).
(NOTE 1).
T1 -85 -79 -97 "Off" (M1) and Cell 2 (M2) satisfy entry
EPRE kHz
(NOTE 1).
T2 -85 "Off" -73 "Off" (M1) and Cell 3 (M3) satisfy entry
EPRE kHz
(NOTE 1).
T3 -97 "Off" -85 -79 (M3) and Cell 12 (M12) satisfy entry
EPRE kHz
(NOTE 1).
EPRE kHz
(NOTE 1).
ETSI

U-S Message
on Cell 1.
3 The SS changes the cell-specific reference - - - -
signal levels of Cell 2 according to the row "T1"
in table 8.3.1.10.3.2-1.
4 The UE transmits a MeasurementReport - MeasurementReport - -
message on Cell 1 to perform event A3 intra
frequency reporting for Cell 2 during the next
30 s.
signal levels of Cell 3 and switches "Off" Cell 2
message on Cell 1 to perform event A3 inter
30 s.
without a measConfig, to order the UE to
perform inter frequency handover to Cell 3.
message to Cell 3?
signal levels of Cell 1 and Cell 3 and switches
"On" Cell 12 according to the row "T3" in table
8.3.1.10.3.2-1.
perform event A3 intra frequency reporting for
Cell 12 during the next 30 s?
signal levels of Cell 1 and switches Cell 12 off
perform event A3 inter frequency reporting for
ETSI

GENERIC(f1)
GENERIC(f2)
}
}
measId[1] 1
measId[2] 2
}
}
Table 8.3.1.10.3.3-3: Void

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 3
used for Cell 3
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 12
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

measurements / Continuation of the measurements after RRC connection re-
establishment
(1)
performed the intra frequency measurement and after receiving an RRCConnectionReconfiguration
message including a mobilityControlInfo indicating a different E-UTRA cell having attempted intra
frequency handover}
ensure that {
when { UE detects handover failure and the intra frequency cell is selectable }
then {UE performs RRC Connection Re-establishment, continues the intra frequency measurement }
}
(2)
performed the inter frequency measurement and after receiving an RRCConnectionReconfiguration
frequency handover}
ensure that {
then {UE performs RRC Connection Re-establishment, continues the inter frequency measurement
after the activation of the measurement gaps }
}
5.3.5.6, 5.3.7.2 and 5.5.6.1.
[TS 36.331,clause 5.3.5.4]
1> else:
targetPhysCellId;
message.
1> reset MAC;
ETSI
2> stop timer T304;
[TS 36.331,clause 5.3.5.6]
The UE shall:
[TS 36.331,clause 5.3.7.2]
ETSI
1> reset MAC;
[TS 36.331,clause 5.5.6.1]
E-UTRAN applies the re-establishment procedure as follows:
- when performing the connection re-establishment procedure, as specified in 5.3.7, ensure that a measObjectId
corresponding to the target carrier frequency is configured as a result of the procedure described in this sub-
clause and the subsequent connection reconfiguration procedure immediately following the re-establishment
procedure;
The UE shall:
VarMeasConfig:
frequency:
2> else:
frequency;
gaps.
System Simulator:
ETSI
UE:
None.
Preamble:
columns marked "T1", "T2","T3", "T4", "T5" are to be applied subsequently. The exact instants on which these values
Table 8.3.1.11.3.2-1: Time instances of cell power levels

(DL
only)
T0 -85 ”off” ”off”
EPRE kHz
T1 -85 ”off” -73 (M1) and Cell 3 (M3) satisfy entry
EPRE kHz
condition for event A3 (M3 - Hys >
M1).
T2 -85 -79 ”off” (M1) and Cell 2 (M2) satisfy entry
EPRE kHz
M1).
assigned values to satisfy
T3 ”off” -79 ”off” SrxlevCell 1 < 0 and SrxlevCell 3 <
EPRE kHz
0 such that selecting Cell 2 is
guaranteed
T4 -79 -85 ”off” (M2) and Cell 1 (M1) satisfy entry
EPRE kHz
M2).
T5 ”off” -85 -73 (M2) and Cell 3 (M3) satisfy entry
EPRE kHz
M2).
ETSI

U-S Message
on Cell 1.
supported.
3a1 IF pc_FeatrGrp_25 THEN the SS changes Cell - - - -
3 power levels according to the row "T1" in
Table 8.3.1.11.3.2-1.
3a2 The UE transmits a MeasurementReport --> MeasurementReport - -
3.
4 The SS changes Cell 2 and Cell 3 power levels - - - -
according to the row "T2" in Table
8.3.1.11.3.2-1.
frequency reporting for Cell 2.
including a mobilityControlInfo, to order the UE
to perform intra frequency handover to Cell 2.
7 The SS changes Cell 1 power levels according - - - -
to the row "T3" in Table 8.3.1.11.3.2-1.
8 Check: Does the UE transmit an --> RRCConnectionReestablishmentR 1,2 P
RRCConnectionReestablishmentRequest equest
message on Cell 2?
security on Cell 2.
10 The UE transmits an --> RRCConnectionReestablishmentC - -
RRCConnectionReestablishmentComplete omplete
message on Cell 2.
message on Cell 2.
8.3.1.11.3.2-1.
Cell 1?
supported.
ETSI

15a3 The SS changes Cell 1 and Cell 3 power levels - - - -
8.3.1.11.3.2-1.
15a4 Check: Does the UE transmit a --> MeasurementReport 2 P
16 Check: Does the test result of CALL generic - - 1,2 -
test procedure in 36.508 subclause 6.2.4.3

U-S Message
ETSI

GENERIC(f1)
p_25
measObject[2] MeasObjectEUTRA- pc_FeatrGr
GENERIC(f2) p_25
}
}
measId[1] 1
measId[2] 2 pc_FeatrGr
p_25
p_25
reportConfigId[2] IdReportConfig-A3 pc_FeatrGr
p_25
}
}
ETSI
Table 8.3.1.11.3.3-3: Void
Table 8.3.1.11.3.3-4: MeasurementReport (step 3a2,Table 8.3.1.11.3.2-2)

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.11.3.3-6: RRCConnectionReconfiguration (step 6,Table 8.3.1.11.3.2-2)
Table 8.3.1.11.3.3-7: MobilityControlInfo (step 6, Table 8.1.3.11.3.2-2)

Cell 2
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}

c1 CHOICE{
}
}
}
}

c1 CHOICE{
dicated-HO
}
}
}
}
ETSI
Table 8.3.1.11.3.3-11: MeasurementReport (step 14,Table 8.3.1.11.3.2-2)

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.11.3.3-12: RRCConnectionReconfiguration (step 15a1,Table 8.3.1.11.3.2-2)
Derivation Path: 36.508, Table 4.6.1-8 condition MEAS
Table 8.3.1.11.3.3-13: MeasConfig (step 15a1,Table 8.3.1.11.3.2-2)
ETSI
Table 8.3.1.11.3.3-14: MeasurementReport (step 15a4, Table 8.3.1.11.3.2-2)

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.11.3.3-15: SystemInformationBlockType2 for Cell 1, cell 2 and Cell 3 (preamble and all the
steps in Table 8.3.1.11.3.2-2)

}
8.3.1.11a Measurement configuration control and reporting / Intra Frequency

establishment / Single Frequency operation
(1)
performed the intra frequency measurement and after receiving an RRCConnectionReconfiguration
frequency handover}
ensure that {
then {UE performs RRC Connection Re-establishment, continues the intra frequency measurement }
}
5.3.5.6, 5.3.7.2 and 5.5.6.1.
[TS 36.331,clause 5.3.5.4]
ETSI
1> else:
targetPhysCellId;
message.
1> reset MAC;
2> stop timer T304;
[TS 36.331,clause 5.3.5.6]
The UE shall:
ETSI
[TS 36.331,clause 5.3.7.2]
1> reset MAC;
[TS 36.331,clause 5.5.6.1]
procedure;
The UE shall:
VarMeasConfig:
ETSI
frequency:
2> else:
frequency;
gaps.
System Simulator:
UE:
None.
Preamble:
columns marked "T1", "T2",and "T3" are to be applied subsequently. The exact instants on which these values shall be
ETSI
Table 8.3.1.11a.3.2-1: Time instances of cell power levels

T0 -85 ”off”
EPRE kHz
T1 -85 -79 (M1) and Cell 2 (M2) satisfy entry
EPRE kHz
M1).
Cell-specific RS dBm/15 assigned values to satisfy
T2 ”off” -79
EPRE kHz SrxlevCell 1 < 0 such that selecting
Cell 2 is guaranteed
T3 -79 -85 (M2) and Cell 1 (M1) satisfy entry
EPRE kHz
M2).
ETSI

U-S Message
setup intra frequency measurements on Cell 1.
to the row "T1" in Table 8.3.1.11a.3.2-1.
to perform intra frequency handover to Cell 2.
7 Check: Does the UE transmit an --> RRCConnectionReestablishmentR 1 P
message on Cell 2?
security on Cell 2.
message on Cell 2.
message on Cell 2.
8.3.1.11a.3.2-1.
Cell 1?

U-S Message
ETSI
Derivation Path: 36.508, Table 4.6.6-1,

GENERIC(f1)
}
}
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
Table 8.3.1.11a.3.3-4: RRCConnectionReconfiguration (step 6,Table 8.3.1.11a.3.2-2)
Table 8.3.1.11a.3.3-5: MobilityControlInfo (step 6, Table 8.1.3.11.3.2-2)

Cell 2
}

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}

c1 CHOICE{
}
}
}
}
ETSI

c1 CHOICE{
dicated-HO
}
}
}
}
Table 8.3.1.11a.3.3-9: MeasurementReport (step 13,Table 8.3.1.11a.3.2-2)

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

measurements / Two simultaneous events A3 (inter-band measurements)
(1)
time}
ensure that {
}
ETSI
5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
this measId;
measId;
ETSI
event):
measId;
this event:
measId;

3> stop timer T321;
ETSI
[TS 36.331, clause 5.5.4.4]
The UE shall:
[TS 36.331, clause 5.5.5]
UE EUTRAN
MeasurementReport
ETSI
the following:
measId;
3> else:
NOTE 4: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency)

first;
5> else:
1> else:
ETSI
System Simulator:
UE:
None.
Preamble:
in this clause.

(DL only) (DL only)
RS EPRE event A3 (measId 1 & 2) is not satisfied:
T2 Cell-specific dBm/15kHz -85 Off -73 Power levels are such that entry condition for
ETSI

U-S Message
(measId 1 and measId 2) (intra and inter
frequency measurement).
message.
level according to row "T1" in table
8.3.1.12.3.2-1.
for Cell 2?
8.3.1.12.3.2-1.
for Cell 10?

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
measId[2] 2
}
}
ETSI

event SEQUENCE {
timeToTrigger ms0
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}

measurements / Two simultaneous events A3 (inter-band measurements) /
Between FDD and TDD
(1)
with { UE in E-UTRA FDD RRC_CONNECTED state and measurements configured for two event A3 at the same
time for E-UTRA TDD cell }
ensure that {
}
(2)
with { UE in E-UTRA FDD RRC_CONNECTED state and measurements configured for two event A3 at the same
time for E-UTRA TDD cell }
ensure that {
when { Neighbour E-UTRA TDD cell becomes offset better than serving E-UTRA FDD cell }
}
(3)
with { UE in E-UTRA TDD RRC_CONNECTED state and measurements configured for two event A3 at the same
time for E-UTRA FDD cell }
ensure that {
}
ETSI
(4)
with { UE in E-UTRA TDD RRC_CONNECTED state and measurements configured for two event A3 at the same
time for E-UTRA FDD cell }
ensure that {
when { Neighbour E-UTRA FDD cell becomes offset better than serving E-UTRA TDD cell }
}
5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
this measId;
ETSI
measId;
event):
measId;
this event:
measId;

3> stop timer T321;
ETSI
[TS 36.331, clause 5.5.4.4]
The UE shall:
[TS 36.331, clause 5.5.5]
ETSI
UE EUTRAN
MeasurementReport
the following:
measId;
3> else:

first;
5> else:
ETSI
1> else:
System Simulator:
- Cell 1 is LTE FDD cell, Cell 28 is LTE TDD cell.
8.3.1.12a.3.1-1.
Cell PLMN name

1 PLMN1
28 PLMN2
UTRA cells.
UE:
None.
Preamble:
8.3.1.12a.3.3-15.
- The UE is in state Generic RB Established (state 3) on Cell 1 according to [18]
Table 8.3.1.12a.3.2-1 illustrates the downlink power levels to be applied for Cell 1 and Cell 2 at various time instants of
the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1", "T2", "T3",
"T4" and "T5" are to be applied subsequently. The exact instants on which these values shall be applied are described in
ETSI
Table 8.3.1.12a.3.2-1: Power levels

The power levels are such that that measurement results for Cell 1
Cell-specific dBm/15 (M1) and Cell 28 (M28) satisfy exit condition for event A3 (measId
T0 -85 -110 1 & 2) (M28 < M1).
RS EPRE kHz
The power levels are such that measurement results for Cell 1
Cell-specific dBm/15 (M1) and Cell 28 (M28) satisfy entry condition for event A3
T1 -85 -85 (measId 1) (M28 > M1):
RS EPRE kHz
T2 -85 -73 (measId 2) (M28 > M1):
RS EPRE kHz
The power levels are such that that measurement results for Cell 1
Cell-specific dBm/15 (M1) and Cell 28 (M28) satisfy exit condition for event A3 (measId
T3 -110 -85
RS EPRE kHz 1 & 2) (M1 < M28): Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off
T4 -85 -85 (measId 1) (M1 > M28):
RS EPRE kHz
T5 -73 -85 (measId 2) (M1 > M28):
RS EPRE kHz
ETSI

U-S Message
including MeasConfig to setup inter-band
parameters for E-UTRA TDD Cell 28.
message.
10s?
8.3.1.12a.3.2-1.
for Cell 28?
8.3.1.12a.3.2-1.
for Cell 28?
behaviour that depends on the UE capability
that if UE has set FGI bit 30 to 1; the "lower
handover
8a3 The UE transmits a TRACKING AREA - - - -
8a4 SS responds with a TRACKING AREA - - - -
8a6 The SS transmits an <-- RRCConnectionReconfiguration - -
8b1 ELSE IF NOT pc_FeatrGrp_30 THEN the SS <-- RRCConnectionRelease - -
transmits an RRCConnectionRelease
eutra CarrierFreq of Cell 28) on Cell 1
8b2 Generic test procedure described in TS 36.508 - - - -
subclause 6.4.2.7 is performed on Cell 28
ETSI
8b4 The SS transmits an <-- RRCConnectionReconfiguration - -

parameters for E-UTRA FDD Cell 1.
8b5 The UE transmits an --> RRCConnectionReconfigurationC - -
message.
8.3.1.12a.3.2-1.
10s?
8.3.1.12a.3.2-1.
for Cell 1?
8.3.1.12a.3.2-1.
for Cell 1?
Table 8.3.1.12a.3.3-1: RRCConnectionReconfiguration (step 1 and step 8b4, Table 8.3.1.12a.3.2-2)
ETSI

GENERIC(f1)
GENERIC(f6)
}
reportConfigId[1] 1
Lowerthreshold
reportConfigId[2] 2
Higherthreshold
}
measId[1] 1
Lowerthreshold
measId[2] 2
Higherthreshold
}
}
Table 8.3.1.12a.3.3-3: ReportConfig-A3-Lowerthreshold (Table 8.3.1.12a.3.3-2)

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset -12 -6 dB
}
}
timeToTrigger ms0
}
}
}
ETSI
Table 8.3.1.12a.3.3-4: ReportConfig-A3-Higherthreshold (Table 8.3.1.12a.3.3-2)

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset 12 6 dB
}
}
timeToTrigger ms0
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
physCellId PhysCellId of the Cell 28
rsrpResult (0..97)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}
Table 8.3.1.12a.3.3-7: RRCConnectionReconfiguration (step 8a1, Table 8.3.1.12a.3.2-2)

Cell 28
as used for Cell 28
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}
ETSI
Table 8.3.1.12a.3.3-13: RRCConnectionRelease (step 8b1, Table 8.3.1.12a.3.2-2)

c1 CHOICE {
Cell 28
}
}
}
}
}

GENERIC(f6)
GENERIC(f1)
}
reportConfigId[1] 1
Lowerthreshold
reportConfigId[2] 2
Higherthreshold
}
measId[1] 1
Lowerthreshold
measId[2] 2
Higherthreshold
}
}

ETSI
Table 8.3.1.12a.3.3-16: TRACKING AREA UPDATE ACCEPT for Cell 28 (steps 8a4 and 8b5, Table
8.3.1.12a.3.2-2)


measurements / Periodic reporting (intra-frequency and inter-band
measurements)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for periodic reporting of intra-
frequency cells and inter-band cells }
ensure that {
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and a MeasurementReport message for a configured periodic
measurement reporting of intra-frequency and inter-band cells was sent }
ensure that {
when { A previously reported cell become unavailable or the UE receives reference signal power on
then { UE sends MeasurementReport message at regular intervals for the available intra-frequency
and inter-band cells }
}
(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting ongoing}
ensure that {
reporting }
}
5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.2.2]
The UE shall:
in varMeasConfig:
ETSI
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
this measId;

...
[TS 36.331, clause 5.5.5]
with the following:
ETSI
measId;
3> else:

first;
...
ends.
System Simulator:
- Cell 1, Cell 2, and Cell 10
UE:
None.
Preamble:
ETSI

(DL (DL
only) only)
T0 Cell-specific dBm/ -85 -91 Off
RS EPRE 15kH
z
T1 Cell-specific dBm/ -85 -91 -85
RS EPRE 15kH
z
T2 Cell-specific dBm/ -85 Off -85
RS EPRE 15kH
z
ETSI

U-S Message
intra and inter-band cells.
message.
3 Void - - - -
3, and the table 8.3.1.13.3.2-4A shall take
place
periodical intra-frequency reporting and a
periodical inter-band reporting.
and switches Cell 10 “On” according to row
"T1" in table 8.3.1.13.3.2-1.
messages for 8s to allow for the switching of
cells and the UE measurement.
3, and table 8.3.1.13.3.2-4 shall take place.
and switches Cell 2 “Off” according to row "T2"
in table 8.3.1.13.3.2-1.
cells and UE measurement.
8.3.1.13.3.2-3A and the table 8.3.1.13.3.2-4
shall take place
message
ETSI

U-S Message
periodical intra-frequency reporting for Cell
2(NOTE1)?

U-S Message
periodical intra-frequency reporting configured
for the cell 2?

U-S Message
periodical inter-band reporting for Cell
10(NOTE2)?

U-S Message
periodical inter-band reporting configured for
cell 10 and without measResultNeighCells for
the cell 10?
ETSI

GENERIC(f1)
GENERIC(f5)
}
PERIODICAL
PERIODICAL
}
measId[1] 1
PERIODICAL
measId[2] 2
PERIODICAL
}
}

MeasId[1] 1
MeasId[2] 2
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
physCellId [1] physicalCellIdentity-
Cell10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}

measurements / Periodic reporting (intra-frequency and inter-band
measurements) / Between FDD and TDD
(1)
with { UE in E-UTRA FDD RRC_CONNECTED state and measurement configured for periodic reporting of
intra frequency cells and inter-band E-UTRA TDD cells on specified frequency }
ETSI
ensure that {
}
(2)
with { UE in E-UTRA FDD RRC_CONNECTED state and a MeasurementReport message for a configured
periodic measurement reporting of intra frequency and inter-band E-UTRA TDD cells was sent }
ensure that {
when { A previously reported cell becomes unavailable or the UE receives reference signal power on
then { UE sends MeasurementReport message at regular intervals for the available intra frequency
and inter-band E-UTRA TDD cells }
}
(3)
with { UE in E-UTRA FDD RRC_CONNECTED state and periodic measurement reporting ongoing }
ensure that {
reporting }
}
(4)
with { UE in E-UTRA TDD RRC_CONNECTED state and measurement configured for periodic reporting of
intra frequency cells and inter-band E-UTRA FDD cells on specified frequency }
ensure that {
}
(5)
with { UE in E-UTRA TDD RRC_CONNECTED state and a MeasurementReport message for a configured
periodic measurement reporting of intra frequency and inter-band E-UTRA FDD cells was sent }
ensure that {
when { A previously reported cell becomes unavailable or the UE receives reference signal power on
then { UE sends MeasurementReport message at regular intervals for the available intra frequency
and inter-band E-UTRA FDD cells }
}
(6)
with { UE in E-UTRA TDD RRC_CONNECTED state and periodic measurement reporting ongoing }
ensure that {
reporting }
}
5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
ETSI
...
[TS 36.331, clause 5.5.2.2]
The UE shall:
in varMeasConfig:
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:
this measId;

...
[TS 36.331, clause 5.5.5]
ETSI
with the following:
measId;
3> else:

first;
...
ends.
System Simulator:
- Cell 1, Cell 2 and Cell 4 are E-UTRA FDD cells, Cell 10 and Cell 30 are E-UTRA TDD cells.
8.3.1.13 a.3.1-1.
ETSI
Cell PLMN name

1 PLMN1
2 PLMN1
4 PLMN1
10 PLMN1
30 PLMN2
UTRA cells.
UE:
None.
Preamble:
8.3.1.13a.3.3-17.
Table 8.3.1.13a.3.2-1 illustrates the downlink power levels to be applied for the cells at various time instants of the test
execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1","T2", "T3" and "T4",
are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in
this clause.
Parameter Unit Cell 1 Cell Cell Cell Cell 30 Remark

2(DL 4(DL 10(DL
only) only) only)
Cell-specific dBm/1
T0 -85 -91 Off -85 Off
RS EPRE 5kHz
Cell-specific dBm/1
T1 -85 Off -91 -85 Off
RS EPRE 5kHz
Cell-specific dBm/1
T2 -85 Off -91 Off -73
RS EPRE 5kHz
Cell-specific dBm/1
T3 Off -91 Off -91 -85
RS EPRE 5kHz
Cell-specific dBm/1
T4 Off Off -91 -91 -85
RS EPRE 5kHz
ETSI

U-S Message
intra frequency and inter-band cells.
message.
2A Wait and ignore MeasurementReport - - - -
the cells and UE to measure the neighbouring
cells.
step 3 the steps specified in table
8.3.1.13a.3.2-3 and table 8.3.1.13a.3.2-5 shall
take place
periodical intra frequency reporting for Cell 2
and a periodical inter-band reporting for Cell
10.
8.3.1.13a.3.2-1.
Cell 2 and UE to measure the neighbouring
cells.
take place.
10.
8.3.1.13a.3.2-1.
cells.
take place
30.
message
- EXCEPTION: Steps 13a1 to 13b3describe - - - -
ETSI
13a IF pc_FeatrGrp_30 THEN the SS transmits an <-- RRCConnectionReconfiguration - -

1 RRCConnectionReconfiguration message on
13a The UE transmits an --> RRCConnectionReconfigurationC - -
2 RRCConnectionReconfigurationComplete omplete
message on Cell 30 to confirm the handover
13a The UE transmits a TRACKING AREA - - - -
3 UPDATE REQUEST message on Cell 30.
13a SS responds with a TRACKING AREA - - - -
4 UPDATE ACCEPT message.
13a The UE transmits a TRACKING AREA - - - -
5 UPDATE COMPLETE message.
13b ELSE IF NOT pc_FeatrGrp_30 THEN the SS <-- RRCConnectionRelease - -
1 transmits an RRCConnectionRelease
EUTRA CarrierFreq of Cell 30) on Cell 1
13b The generic test procedure described in TS - - - -
30
13b Generic test procedure described in TS 36.508 - - - -
3 subclause 4.5.3.3.is executed
8.3.1.13a.3.2-1.
intra frequency and inter-band cells.
message.
A messages for 8 s to allow for the switching of
cells.
take place.
17 Wait for 30 s to ensure that the UE performs a - - 4,5 -
and a periodical inter-band reporting for Cell 2.
8.3.1.13a.3.2-1.
Cell2 and UE to measure the neighbouring
cells.
take place
20 Wait for 30 s to ensure that the UE performs a - - 4,5 -
and a periodical inter-band reporting for Cell 4.
ETSI
message

U-S Message
2(NOTE1)?

U-S Message
periodical intra frequency reporting for Cell 4(
NOTE2)?

U-S Message
periodical inter-band reporting for Cell
10(NOTE3)?

U-S Message
periodical inter band reporting for Cell
2(NOTE4)?
ETSI

U-S Message
1 Check: Does the UE transmit a --> MeasurementReport 4,5 P
periodical inter band reporting for Cell 4(
NOTE5)?

U-S Message
10(NOTE6)?

U-S Message
periodical inter band reporting for Cell
30(NOTE7)?
Table 8.3.1.13a.3.3-1: RRCConnectionReconfiguration (step 1, step 10, step 15 and step 21, Table
8.3.1.13a.3.2-2)
ETSI

GENERIC(f1)
GENERIC(f5)
}
PERIODICAL
PERIODICAL
}
measId[1] 1
PERIODICAL
measId[2] 2
PERIODICAL
}
}

MeasId[1] 1
MeasId[2] 2
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 30
as used for Cell 30
}
}
ETSI

GENERIC(f5)
GENERIC(f1)
}
PERIODICAL
PERIODICAL
}
measId[1] 1
PERIODICAL
measId[2] 2
PERIODICAL
}
}

MeasId[1] 1
MeasId[2] 2
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell30
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
Table 8.3.1.13a.3.3-15: TRACKING AREA UPDATE ACCEPT (steps 13a4 and 13b2, Table 8.3.1.13a.3.2-
2)


c1 CHOICE {
Eutra Downlink EARFCN of cell
Cell 30
}
}
}
}
}
Table 8.3.1.13a.3.3-17: ATTACH ACCEPT (preamble)


measurements / Two simultaneous events A2 and A3 (inter-band
measurements)
(1)
ensure that {
when { Serving becomes worse than threshold }
}
(2)
ensure that {
}
5.5.4.1, 5.5.4.3, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
ETSI
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:

reportConfig:
4> else:
for this measId;
measId;
event):
measId;
this event:
measId;
ETSI
3> stop timer T321;
[TS 36.331, clause 5.5.4.3]
The UE shall:
Ms + Hys < Thresh
Ms − Hys > Thresh
ETSI
event).
[TS 36.331, clause 5.5.4.4]
The UE shall:
[TS 36.331, clause 5.5.5]
the following:
ETSI
measId;
3> else:

first;
5> else:
System Simulator:
UE:
None.
ETSI
Preamble:
clause.

(DL
only)
Ms − Hys > Thresh
AND
Ms + Hys < Thresh
AND
EPRE 5kHz satisfied:

U-S Message
event A3 (inter-band measurement)
message.
10s?
8.3.1.14.3.2-1.
8.3.1.14.3.2-1.
ETSI

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
measId[2] 2
}
}

event SEQUENCE {
hysteresis 6 3 dB
}
}
}
ETSI

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset 0 0 dB
}
}
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}

measurements / Two simultaneous events A2 and A3 (inter-band
measurements) / Between FDD and TDD
(1)
with { UE in E-UTRA FDD RRC_CONNECTED state and measurements configured for event A2 and event A3 }
ensure that {
when { Serving E-UTRA FDD cell becomes worse than threshold }
}
(2)
with { UE in E-UTRA FDD RRC_CONNECTED state and measurements configured for event A2 and event A3 }
ensure that {
when { Neighbour E-UTRA TDD cell becomes offset better than serving E-UTRA FDD cell }
}
(3)
with { UE in E-UTRA TDD RRC_CONNECTED state and measurements configured for event A2 and event A3 }
ensure that {
when { Serving E-UTRA TDD cell becomes worse than threshold }
}
(4)
with { UE in E-UTRA TDD RRC_CONNECTED state and measurements configured for event A2 and event A3 }
ensure that {
when { Neighbour E-UTRA FDD cell becomes offset better than serving E-UTRA TDD cell }
ETSI

}
5.5.4.1, 5.5.4.3, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2> else:

reportConfig:
4> else:
for this measId;
measId;
event):
ETSI
measId;
this event:
measId;
3> stop timer T321;
NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered
and periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].
[TS 36.331, clause 5.5.4.3]
ETSI
The UE shall:
Ms + Hys < Thresh
Ms − Hys > Thresh
event).
[TS 36.331, clause 5.5.4.4]
The UE shall:
ETSI
[TS 36.331, clause 5.5.5]
the following:
measId;
3> else:

first;
5> else:
ETSI
System Simulator:
- Cell 1 is E-UTRA FDD cell and Cell 28 is E-UTRA TDD cell.
8.3.1.14a.3.1-1.
Cell PLMN name

1 PLMN1
28 PLMN2
UTRA cells.
UE:
None.
Preamble:
8.3.1.14a.3.3-15.
Table 8.3.1.14a.3.2-1 illustrates the downlink power levels to be applied for Cell 1 and Cell 28 at various time instants
of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1"and "T2" are
to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this
clause.
ETSI

Ms − Hys > Thresh
AND
Ms + Hys < Thresh
AND
EPRE 5kHz satisfied for Cell 1, and the entry condition for event A2
and event A3 are not satisfied for Cell 28 after the
handover:
Ms + Hys < Thresh
AND
EPRE 5kHz satisfied for Cell 28:
ETSI

U-S Message
event A3 (inter-band measurement) on Cell 1
message.
10s?
8.3.1.14a.3.2.-1.
8.3.1.14a.3.2.-1.
handover to Cell 28 and to activate the
measurement gaps.
handover
8a4 SS responds with a TRACKING AREA - - - -
8b1 ELSE IF NOT pc_FeatrGrp_30 THEN the SS <-- RRCConnectionRelease - -
transmits an RRCConnectionRelease
eutra CarrierFreq of Cell 28) on Cell 1
8b2 The generic test procedure described in TS
36.508 subclause 6.4.2.7 is performed on Cell
28
8b4 The SS transmits an <-- RRCConnectionReconfiguration - -
event A3 on Cell 28.
8b5 The UE transmits an --> RRCConnectionReconfigurationC - -
message.
ETSI

10s?
8.3.1.14a.3.2.-1.
8.3.1.14a.3.2.-1.
Table 8.3.1.14a.3.3-1: RRCConnectionReconfiguration (step 1 and step 8b4, Table 8.3.1.14a.3.2-2)

GENERIC(f1)
GENERIC(f6)
}
}
measId[1] 1
measId[2] 2
}
}
ETSI
Table 8.3.1.14a.3.3-3: ReportConfig-A2 (step 1 and step 8b4, Table 8.3.1.14a.3.3-2)

event SEQUENCE {
hysteresis 6 3 dB
}
}
}
Table 8.3.1.14a.3.3-4: ReportConfig-A3 (step 1 and step 8b4, Table 8.3.1.14a.3.3-2)

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset 0 0 dB
}
}
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
ETSI

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}
Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with conditions MEAS and HO
Table 8.3.1.14a.3.3-8: MeasConfig (step 8a1, Table 8.3.1.14a.3.3-7)
Table 8.3.1.14a.3.3-9: MobilityControlInfo (step 8a1, Table 8.3.1.14a.3.3-7)

Cell 28
dl-CarrierFreq Same DL EARFCN as
used for Cell 28
}
}
ETSI

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
rsrpResult (0..97)
}
}
}
}
}
}
}
}
Table 8.3.1.14a.3.3-12: TRACKING AREA UPDATE ACCEPT for Cell 28 (steps 8a4 and 8b2, Table
8.3.1.14a.3.2-2)

ETSI

c1 CHOICE {
Cell 28
}
}
}
}
}
Table 8.3.1.14a.3.3-14: MeasConfig (step 8b4, Table 8.3.1.14a.3.3-1)

GENERIC(f1)
GENERIC(f6)
}
}
measId[1] 1
measId[2] 2
}
}

measurements / Inter-band handover / IE measurement configuration not
present
(1)
performed the intra-frequency and inter-band measurements }
ensure that {
indicating a different E-UTRA frequency band and not including a measConfig }
then { UE performs inter-band handover, continues the intra-frequency measurement and continues
inter-band measurement after the activation of the measurement gaps }
}
ETSI
[TS 36.331, clause 5.5.6.1]
in 5.3.5.4;
...
The UE shall:
VarMeasConfig:
frequency:
2> else:
frequency;
1> stop the periodical reporting timer or timer T321, whichever one is running, as well as associated information
gaps.
System Simulator:
- Cell 1, Cell 2, Cell 10 and Cell 30
ETSI
UE:
None.
Preamble:

(DL (DL
only) only)
T0 -85 -91 -97 "Off"
M1).
(NOTE 1).
EPRE kHz
(NOTE 1).
EPRE kHz
(NOTE 1).
that measurement results for Cell
Cell-specific RS dBm/15 10 (M10) and Cell 30 (M30) satisfy
T3 -97 "Off" -85 -79
EPRE kHz entry condition for event A3 (M30 >
M10).
(NOTE 1).
EPRE kHz
(NOTE 1).
ETSI

U-S Message
setup intra-frequency and inter-band
measurements on Cell 1.
message to confirm the setup of intra-
frequency and inter-band measurements on
Cell 1.
in table 8.3.1.15.3.2-1.
message on Cell 1 to perform event A3 intra-
30 s.
signal levels of Cell 10 and switches "Off" Cell
2 according to row "T2" in table 8.3.1.15.3.2-1.
message on Cell 1 to perform event A3 inter-
band reporting for Cell 10 during the next 30 s.
perform inter-band handover to Cell 10.
message to Cell 10?
8.3.1.15.3.2-1.
perform event A3 intra-frequency reporting for
perform event A3 inter-band reporting for Cell
1 during the next 30 s?
ETSI

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
measId[2] 2
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Derivation Path: 36.508 Table 4.6.1-8, condition HO

Cell 10
as used for Cell 10
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 30
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

measurements / Inter-band handover / IE measurement configuration not
present / Between FDD and TDD
(1)
with { UE in E-UTRA FDD RRC_CONNECTED state and having completed the radio bearer establishment,
initial security activation procedure and performed the intra frequency and inter-band E-UTRA TDD
frequency measurements }
ensure that {
indicating a different E-UTRA TDD frequency in different band and not including a measConfig }
then { UE performs inter-band handover, continues the intra frequency measurement and continues
}
(2)
with { UE in E-UTRA TDD RRC_CONNECTED state and having completed the radio bearer establishment,
initial security activation procedure and performed the intra frequency and inter-band E-UTRA FDD
frequency measurements }
ensure that {
indicating a different E-UTRA FDD frequency in different band and not including a measConfig }
then { UE performs inter-band handover, continues the intra frequency measurement and continues
}
ETSI
[TS 36.331, clause 5.5.6.1]
the handover target carrier frequency is configured as a result of the procedures described in this subclause and
in 5.3.5.4;
...
The UE shall:
VarMeasConfig
frequency:
2> else:
frequency;
gaps.
System Simulator:
- Cell 1 and Cell 2 are E-UTRA FDD cells, Cell 10 and Cell 30 are E-UTRA TDD cell
8.3.1.15a.3.1-1.
ETSI
Cell PLMN name

1 PLMN1
2 PLMN1
10 PLMN1
30 PLMN2
s
UTRA cells.
UE:
None.
Preamble:
8.3.1.15a.3.3-12.
ETSI

(DL (DL
only) only)
T0 -85 -91 -97 "Off"
M1).
(NOTE 1).
EPRE kHz
(NOTE 1).
EPRE kHz
(NOTE 1).
that measurement results for Cell
Cell-specific RS dBm/15 10 (M10) and Cell 30 (M30) satisfy
T3 -97 "Off" -85 -79
EPRE kHz entry condition for event A3 (M30 >
M10).
(NOTE 1).
EPRE kHz
(NOTE 1).
EPRE kHz
(NOTE 1).
EPRE kHz
(NOTE 1).
ETSI

U-S Message
setup intra frequency and inter-band
Cell 1.
in table 8.3.1.15a.3.2-1.
4 The UE transmits a MeasurementReport - MeasurementReport - -
30 s.
signal levels of Cell 10 and switches "Off" Cell
2 according to row "T2" in table 8.3.1.15a.3.2-
1.
message to Cell 10?
10 Void - - - -
A
10 Void - - - -
B
10 Void - - - -
C
8.3.1.15a.3.2-1.
according to row "T4" in table 8.3.1.15a.3.2-1.
ETSI
1 during the next 30 s?

message to Cell 1?
A UPDATE REQUEST message on Cell 1.
16 SS responds with a TRACKING AREA - - - -
B UPDATE ACCEPT message.
C UPDATE COMPLETE message.
18 Void - - - -
A
18 Void - - - -
B
18 Void - - - -
C
signal levels of Cells according to the row "T5"
in table 8.3.1.15a.3.2-1.
20 The UE transmits a MeasurementReport - MeasurementReport 2 P
30 s.
signal levels of Cells according to row "T6" in
table 8.3.1.15a.3.2-1.
22 The UE transmits a MeasurementReport --> MeasurementReport 2 P
ETSI

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
measId[2] 2
}
}
Table 8.3.1.15a.3.3-3: MeasurementReport (step 4 and step 20, Table 8.3.1.15a.3.2-2)

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI
Table 8.3.1.15a.3.3-4: MeasurementReport (step 6 and step 22, Table 8.3.1.15a.3.2-2)

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 10
used for Cell 10
}
}
ETSI

Cell 1
used for Cell 1
ul-CarrierFreq Same UL EARFCN as
used for Cell 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 30
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


establishment / Inter-band
(1)
performed the inter-band measurement and after receiving an RRCConnectionReconfiguration message
including a mobilityControlInfo indicating a different E-UTRA cell having attempted intra-frequency
handover }
ensure that {
when { UE detects handover failure and the intra-frequency cell is selectable }
then { UE performs RRC Connection Re-establishment and continues the inter-band measurement
after the activation of the measurement gaps }
}
5.3.5.6, 5.3.7.2 and 5.5.6.1.
[TS 36.331, clause 5.3.5.4]
ETSI
1> else:
targetPhysCellId;
message.
1> reset MAC;
...
2> stop timer T304;
ETSI
[TS 36.331, clause 5.3.5.6]
The UE shall:
[TS 36.331, clause 5.3.7.2]
1> reset MAC;
[TS 36.331, clause 5.5.6.1]
procedure;
ETSI
The UE shall:
VarMeasConfig:
frequency:
2> else:
frequency;
1> stop the periodical reporting timer or timer T321, whichever one is running, as well as associated information
gaps.
System Simulator:
UE:
None.
Preamble:
columns marked "T1", "T2", "T3", and "T4" are to be applied subsequently. The exact instants on which these values
ETSI
Table 8.3.1.16.3.2-1: Time instances of cell power levels

(DL only)
T0 Cell-specific dBm/15 -85 "Off" "Off" (NOTE 1)
RS EPRE kHz
T1 Cell-specific dBm/15 -85 "Off" -73 The power level values are such that
RS EPRE kHz measurement results for Cell 1 (M1) and Cell
10 (M10) satisfy entry condition for event A3
(M10 > M1). (NOTE 1)
T2 Cell-specific dBm/15 -85 -79 "Off" The power level values are such that
RS EPRE kHz measurement results for Cell 1 (M1) and Cell 2
(M2) satisfy entry condition for event A3 (M2 >
M1). (NOTE 1)
T3 Cell-specific dBm/15 "Off" -79 "Off" The power level values are such that
RS EPRE kHz SrxlevCell 1 < 0 and SrxlevCell 10 < 0 are
satisfied. (NOTE 1)
T4 Cell-specific dBm/15 "Off" -85 -73 The power level values are such that
RS EPRE kHz measurement results for Cell 2 (M2) and Cell
10 (M10) satisfy entry condition for event A3
(M10 > M2). (NOTE 1)
NOTE 1: Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1.
ETSI

U-S Message
setup intra-frequency and inter-band
message to confirm the setup of intra-
Cell 1.
10.
levels according to the row "T2" in Table
8.3.1.16.3.2-1.
message on Cell 1 to perform event A3 intra-
to perform intra-frequency handover to Cell 2.
message on Cell 2?
security on Cell 2.
message on Cell 2.
message on Cell 2.
8.3.1.16.3.2-1.
ETSI

U-S Message
1 The UE attempts to perform the intra- - - - -
8.3.1.16.3.2-2)

rach-ConfigCommon SEQUENCE {
}
}
}
ssac-BarringForMMTEL-Voice-r9 Not present
ssac-BarringForMMTEL-Video-r9 Not present
}
ETSI

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
measId[2] 2
}
}
Table 8.3.1.16.3.3-4: MeasurementReport (step 4 and 17, Table 8.3.1.16.3.2-2)

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 2
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS
}
}
}
}
Table 8.3.1.16.3.3-9: RRCConnectionReestablishmentComplete (step 11, Table 8.3.1.16.3.2-2)

SEQUENCE {
SEQUENCE {
}
}
}

c1 CHOICE{
dicated-HO
}
}
}
}
ETSI

establishment / Inter-band / Between FDD and TDD
(1)
initial security activation procedure and performed the intra frequency measurement and after
receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a
different E-UTRA TDD cell having attempted inter- mode handover }
ensure that {
when { UE detects handover failure and the inter-band E-UTRA TDD cell is selectable }
then { UE performs RRC Connection Re-establishment, continues the intra frequency measurement }
}
(2)
initial security activation procedure and performed the inter-band measurement and after receiving
an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-
UTRA TDD cell having attempted inter- mode handover}
ensure that {
when { UE detects handover failure and the inter-band E-UTRA TDD cell is selectable }
then {UE performs RRC Connection Re-establishment, continues the inter-band measurement after the
activation of the measurement gaps }
}
(3)
initial security activation procedure and performed the intra frequency measurement and after
receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a
different E-UTRA FDD cell having attempted inter- mode handover }
ensure that {
when { UE detects handover failure and the inter-band E-UTRA FDD cell is selectable }
then { UE performs RRC Connection Re-establishment, continues the intra frequency measurement }
}
(4)
initial security activation procedure and performed the inter-band measurement and after receiving
an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-
UTRA FDD cell having attempted inter- mode handover}
ensure that {
when { UE detects handover failure and the inter-band E-UTRA FDD cell is selectable }
then {UE performs RRC Connection Re-establishment, continues the inter-band measurement after the
activation of the measurement gaps }
}
5.3.5.6, 5.3.7.2 and 5.5.6.1.
[TS 36.331, clause 5.3.5.4]
ETSI
1> else:
targetPhysCellId;
message.
1> reset MAC;
2> stop timer T304;
[TS 36.331, clause 5.3.5.6]
The UE shall:
[TS 36.331, clause 5.3.7.2]
ETSI
1> reset MAC;
[TS 36.331,clause 5.5.6.1]
procedure;
The UE shall:
VarMeasConfig:
frequency:
2> else:
ETSI
frequency;
gaps.
System Simulator:
- Cell 1 and Cell 2 are E-UTRA FDD cells, Cell 10 and Cell 30 are E-UTRA TDD cells.
8.3.1.16 a.3.1-1.
Table 8.3.1.16 a.3.1-1: PLMN identifiers
Cell PLMN name

1 PLMN1
2 PLMN1
10 PLMN1
30 PLMN2
UTRA cells.
UE:
None.
Preamble:
8.3.1.16a.3.3-19.
columns marked "T1", "T2","T3", "T4", "T5" are to be applied subsequently. The exact instants on which these values
ETSI
Table 8.3.1.16a.3.2-1: Time instances of cell power levels

T0 -85 ”off” ”off” “off”
EPRE kHz
T1 -85 -79 “off” “off” (M1) and Cell 2 (M2) satisfy entry
EPRE kHz
M1).
T2 -85 “off” -73 “off” (M1) and Cell 10 (M10) satisfy entry
EPRE kHz
M1).
The power level values are assigned
Cell-specific RS dBm/15 values to satisfy SrxlevCell 1 < 0
T3 ”off” “off” -73 “off”
EPRE kHz and SrxlevCell 2 < 0 such that
selecting Cell 10 is guaranteed
T4 “off” “off” -85 -79 (M10) and Cell 30 (M30) satisfy
EPRE kHz
entry condition for event A3 (M30 -
Hys > M10).
EPRE kHz
M10).
The power level values are assigned
Cell-specific RS dBm/15 values to satisfy SrxlevCell 10 < 0
T6 -73 “off” “off” “off”
EPRE kHz and SrxlevCell 2 < 0 such that
selecting Cell 1 is guaranteed
T7 -85 -79 “off” “off” (M1) and Cell 2 (M2) satisfy entry
EPRE kHz
M1).
EPRE kHz
M1).
ETSI

U-S Message
setup intra frequency and inter-band
Cell 1.
8.3.1.16a.3.2-1.
band reporting for Cell 10.
to perform inter-band handover to Cell 10.
message on Cell 10?
message on Cell 10.
message on Cell 10.
8.3.1.16a.3.2-1.
Cell 30?

ETSI

8.3.1.16a.3.2-1.
1?
to perform inter-band handover to Cell 1.
message on Cell 1?
security on Cell 1.
message on Cell 1.
message on Cell 1.
8.3.1.16a.3.2-1.
Cell 2?
8.3.1.16a.3.2-1.
10?
33 Check: Does the test result of CALL generic - - 3,4 -
ETSI

U-S Message

U-S Message
Preamble on Cell 1.
Table 8.3.1.16a.3.3-1: SystemInformationBlockType2 for Cell 1, Cell 2, Cell 10 and Cell 30 (preamble
and all the steps in Table 8.3.1.16a.3.2-2)

}
ETSI

GENERIC(f1)
GENERIC(f5)
}
}
measId[1] 1
measId[2] 2
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 10
used for Cell 10
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 1
the XMAC-I value
calculated by SS.
}
}
}
}
Table 8.3.1.16a.3.3-9: RRCConnectionReestablishment (step 10 and step 23, Table 8.3.1.16a.3.2-2)

c1 CHOICE{
}
}
}
}
Table 8.3.1.16a.3.3-9A: RRCConnectionReestablishmentComplete (step 11 and step 24, Table

8.3.1.16a.3.2-2)

SEQUENCE {
SEQUENCE {
nonCriticalExtension SEQUENCE { Not present
}
}
}
}
ETSI

c1 CHOICE{
dicated-HO
}
}
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 30
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
Table 8.3.1.16a.3.3-13: MeasConfig (step 16 and step 29, Table 8.3.1.16a.3.2-12)

quantityConfig Not present
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Cell 1
used for Cell 1
ul-CarrierFreq Same UL EARFCN as
used for Cell 1
}
}
ETSI

SEQUENCE {
SEQUENCE {
of the UE
Cell 10
the XMAC-I value
calculated by SS.
}
}
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 2
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}
ETSI

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Cell 10
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

8.3.1.17 CA / Measurement configuration control and reporting / Intra E-UTRAN

8.3.1.17.1 CA / Measurement configuration control and reporting / Intra E-UTRAN
measurements / Event A6 / Intra-band Contiguous CA
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurements configured for event A6 }
ensure that {
}
(2)
ensure that {
when { Intra-frequency neighbour becomes offset better than SCell }
(3)
ensure that {
ETSI
when { UE receives a RRCConnectionReconfiguration message containing sCellToReleaseList with a

sCellIndex equal to one of the current UE SCell configuration }
then { UE remove measId associated with event A6 and stops sending MeasurementReport message }
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.5.3
5.5.2.2a, 5.5.4.1, 5.5.4.6a and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.2.2a]
The UE shall:
2> if the associated reportConfig concerns an event involving a serving cell while the concerned serving cell is
not configured:
3> remove the measId from the measIdList within the VarMeasConfig;
3> stop the periodical reporting timer if running, and reset the associated information (e.g. timeToTrigger)
for this measId;
NOTE 1: The above UE autonomous removal of measId's applies only for measurement events A1, A2 and A6.
NOTE 2: When performed during re-establishment, the UE is only configured with a primary frequency (i.e. the
SCell(s) are released, if configured).
[TS 36.331, clause 5.5.4.1]
The UE shall:
ETSI
2> else:
4> if the ue-RxTxTimeDiffPeriodical is configured in the corresponding reportConfig:
5> consider only the PCell to be applicable;
4> else if the eventA1 or eventA2 is configured in the corresponding reportConfig:
4> else:
5>consider any neighbouring cell detected on the associated frequency to be applicable when the
for this measId;
5> for events involving a serving cell on one frequency and neighbours on another frequency,
consider the serving cell on the other frequency as a neighbouring cell;
NOTE 0: The UE may also consider a neighbouring cell on the associated UTRA frequency to be applicable when
the concerned cell is included in the csg-allowedReportingCells within the VarMeasConfig for this
measId, if configured in the corresponding measObjectUTRA (i.e. the cell is included in the range of
physical cell identities for which reporting is allowed).
measId;
event):
measId;
ETSI
this event:
measId;

3> stop timer T321;
[TS 36.331, clause 5.5.4.6a]
The UE shall:
ETSI
1> for this measurement, consider the (secondary) cell that is configured on the frequency indicated in the
associated measObjectEUTRA to be the serving cell;
NOTE: The neighbour(s) is on the same frequency as the SCell i.e. both are on the frequency indicated in the
associated measObject.
Mn + Ocn − Hys > Ms + Ocs + Off
Mn + Ocn + Hys < Ms + Ocs + Off
Ocn, Ocs, Hys, Off are expressed in dB.
[TS 36.331, clause 5.5.5]
UE EUTRAN
MeasurementReport
1> set the measResultPCell to include the quantities of the PCell;
1> set the measResultServFreqList to include for each SCell that is configured, if any, within measResultSCell the
quantities of the concerned SCell;
1> if the reportConfig associated with the measId that triggered the measurement reporting includes
reportAddNeighMeas:
ETSI
2> for each serving frequency for which measObjectId is referenced in the measIdList, other than the frequency
corresponding with the measId that triggered the measurement reporting:
3> set the measResultServFreqList to include within measResultBestNeighCell the physCellId and the
quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;
the following:
measId;
3> else:
4> include the applicable cells for which th

Ts 13652301v120300p

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ts 13652301v120300p

Uploaded by

Copyright:

Available Formats

ETSI TS 136 523-1 V12.3.

650 Route des Lucioles

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C

The present document can be downloaded from:

© European Telecommunications Standards Institute 2014.

Intellectual Property Rights

Modal verbs terminology

6.2.3.3a Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE (QqualminEUTRA,

7.1.4.14 Correct HARQ process handling / TTI bundling ................................................................................ 697

7.2 RLC ................................................................................................................................................................ 876

8.2.4.13a RRC connection reconfiguration / Handover / Success (with measurement) / Inter-band /

8.4.1.3 Void................................................................................................................................................... 1871

9.2.1.1 Attach procedure for EPS services .................................................................................................... 2510

9.3.2.1 Paging procedure............................................................................................................................... 3065

13.4.3.12 Void................................................................................................................................................... 3593

16.1.1.1 Void................................................................................................................................................... 3838

Annex A (informative): Change history ...........................................................................................3968

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

- the overall test structure;

- the test configurations;

- the conformance requirement and reference to the core specifications;

- the test purposes; and

The following information relevant to testing could be found in accompanying specifications:

- the default setting of the test parameters [18];

- the applicability of each test case [19].

• For a specific reference, subsequent revisions do not apply.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 23.003: "Numbering, Addressing and Identification".

[21] 3GPP TR 24.801: "3GPP System Architecture Evolution; CT WG1 Aspects".

[26] 3GPP TS 33.102: "3G Security; Security architecture"

[45] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)"

3 Definitions, symbols and abbreviations

example: text used to clarify abstract rules by applying them literally.

Floor: Floor(x) is the largest integer smaller than or equal to x.

Ceil: Ceil (x) is the smallest integer larger than or equal to x.

ENB Evolved Node B

4.1.2 Test interfaces and facilities

4.2 Implicit testing

4.3 Repetition of tests

4.4 Handling of differences between conformance requirements

5.1 Generic setup procedures

6 Idle mode operations

PLMN MCC1 MCC2 MCC3 MNC1 MNC2 MNC3 TAC

Table 6.0.1-2: Tracking Area Code (TAC) for E-UTRAN cells

6.1 In a pure E-UTRAN environment

6.1.1.1.2 Conformance requirements

[TS 23.122, clause 4.4.3.1]

If successful registration is achieved, the MS indicates the selected PLMN.

[TS 23.122, clause 4.4.3.1.1]

When following the above procedure the following requirements apply:

NOTE 3: High quality signal is defined in the appropriate AS specification.

If successful registration is achieved, the MS indicates the selected PLMN.

[TS 23.122, clause 4.4.3.3]

d) Periodic attempts shall only be performed by the MS while in idle mode;

6.1.1.1.3 Test description

6.1.1.1.3.1 Pre-test conditions

Table 6.1.1.1.3.1–1: PLMN identifiers

Cell PLMN name MCC MNC

- The UE is in Automatic PLMN selection mode.