3GPP - Ts 36.133
Uploaded by
Kevin Night3GPP - Ts 36.133
Uploaded by
Kevin NightETSI TS 136 133 V14.3.
0 (2017-04)
TECHNICAL SPECIFICATION
LTE;
Evolved Universal Terrestrial Radio Access (E-UTRA);
Requirements for support of radio resource management
(3GPP TS 36.133 version 14.3.0 Release 14)
3GPP TS 36.133 version 14.3.0 Release 14 1 ETSI TS 136 133 V14.3.0 (2017-04)
Reference
RTS/TSGR-0436133ve30
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/standards-search
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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 2017.
All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
3GPPTM 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
3GPP TS 36.133 version 14.3.0 Release 14 2 ETSI TS 136 133 V14.3.0 (2017-04)
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 (https://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", "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
3GPP TS 36.133 version 14.3.0 Release 14 3 ETSI TS 136 133 V14.3.0 (2017-04)
Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Modal verbs terminology....................................................................................................................................2
Foreword...........................................................................................................................................................65
1 Scope ......................................................................................................................................................66
2 References ..............................................................................................................................................66
3 Definitions, symbols and abbreviations .................................................................................................67
3.1 Definitions ........................................................................................................................................................ 67
3.2 Symbols ............................................................................................................................................................ 69
3.3 Abbreviations ................................................................................................................................................... 70
3.4 Test tolerances .................................................................................................................................................. 72
3.5 Additional notation ........................................................................................................................................... 72
3.5.1 Groups of bands .......................................................................................................................................... 72
3.6 General ............................................................................................................................................................. 74
3.6.1 Applicability of requirements in this specification version ........................................................................ 74
4 E-UTRAN RRC_IDLE state mobility....................................................................................................77
4.1 Cell Selection ................................................................................................................................................... 77
4.2 Cell Re-selection .............................................................................................................................................. 77
4.2.1 Introduction................................................................................................................................................. 77
4.2.2 Requirements .............................................................................................................................................. 77
4.2.2.1 Measurement and evaluation of serving cell ......................................................................................... 78
4.2.2.2 Void....................................................................................................................................................... 79
4.2.2.3 Measurements of intra-frequency E-UTRAN cells ............................................................................... 79
4.2.2.4 Measurements of inter-frequency E-UTRAN cells ............................................................................... 81
4.2.2.5 Measurements of inter-RAT cells ......................................................................................................... 83
4.2.2.5.1 Measurements of UTRAN FDD cells.............................................................................................. 84
4.2.2.5.2 Measurements of UTRAN TDD cells ............................................................................................. 85
4.2.2.5.3 Measurements of GSM cells............................................................................................................ 87
4.2.2.5.4 Measurements of HRPD cells.......................................................................................................... 88
4.2.2.5.5 Measurements of cdma2000 1X ...................................................................................................... 89
4.2.2.6 Evaluation of cell re-selection criteria................................................................................................... 90
4.2.2.7 Maximum interruption in paging reception........................................................................................... 90
4.2.2.8 void ....................................................................................................................................................... 90
4.2.2.9 UE measurement capability .................................................................................................................. 90
4.2.2.9a UE measurement capability (Increased UE carrier monitoring) ........................................................... 91
4.2.2.10 Reselection to CSG cells ....................................................................................................................... 91
4.2.2.10.1 Reselection from a non CSG to an inter-frequency CSG cell.......................................................... 91
4.2.2.10.2 Reselection from a non CSG to an inter-RAT UTRAN FDD CSG cell .......................................... 92
4.2.2.11 Measurement and evaluation requirements for UE in enhanced coverage ................................................. 93
4.2.2.11.1 Measurement and evaluation of serving cell ................................................................................... 93
4.2.2.11.2 Measurement and evaluation of intra-frequency E-UTRAN cells................................................... 94
4.2.2.12 Maximum interruption in paging reception for Category M1 UEs in normal coverage ....................... 96
4.2.2.13 Maximum interruption in paging reception for Category M1 UEs in extended coverage .................... 96
4.3 Minimization of Drive Tests (MDT) ................................................................................................................ 97
4.3.1 Introduction................................................................................................................................................. 97
4.3.2 Measurements ............................................................................................................................................. 97
4.3.2.1 Requirements ........................................................................................................................................ 97
4.3.3 Relative Time Stamp Accuracy .................................................................................................................. 97
4.3.3.1 Requirements ........................................................................................................................................ 98
4.3.4 Relative Time Stamp Accuracy for RRC Connection Establishment Failure Log Reporting .................... 98
4.3.4.1 Requirements ........................................................................................................................................ 98
4.3.5 Relative Time Stamp Accuracy for Radio Link Failure and Handover Failure Log Reporting.................. 98
4.3.5.1 Requirements for timeSinceFailure....................................................................................................... 98
4.4 MBSFN Measurements .................................................................................................................................... 98
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 4 ETSI TS 136 133 V14.3.0 (2017-04)
4.4.1 Introduction................................................................................................................................................. 98
4.4.2 MBSFN RSRP measurements .................................................................................................................... 99
4.4.3 MBSFN RSRQ measurements .................................................................................................................... 99
4.4.4 MCH BLER measurements ........................................................................................................................ 99
4.5 Proximity-based Services ................................................................................................................................. 99
4.5.1 Introduction................................................................................................................................................. 99
4.5.2 Requirements .............................................................................................................................................. 99
4.5.2.1 Interruptions with ProSe Direct Discovery ........................................................................................... 99
4.5.2.2 Interruptions with ProSe Direct Communication ................................................................................ 100
4.5.2.3 Initiation/Cease of SLSS transmissions with ProSe Direct Discovery................................................ 100
4.5.2.4 Initiation/Cease of SLSS transmissions with ProSe Direct Communication ...................................... 100
4.6 Cell Selection and Re-selection Requirements for UE category NB1 ............................................................ 101
4.6.1 Cell Selection ............................................................................................................................................ 101
4.6.2 Cell Re-selection ....................................................................................................................................... 101
4.6.2.1 Measurement and evaluation of serving NB-IoT cell for UE category NB1 in normal coverage ....... 101
4.6.2.2 Measurements of intra-frequency NB-IoT cells for UE category NB1 in normal coverage ............... 102
4.6.2.3 Measurement and evaluation of serving NB-IoT cell for UE category NB1 in enhanced coverage ... 103
4.6.2.4 Measurements of intra-frequency NB-IoT cells for UE category NB1 in enhanced coverage ........... 104
4.6.2.5 Measurements of inter-frequency NB cells for UE category NB1 in normal coverage ...................... 105
4.6.2.6 Measurements of inter-frequency NB-IoT cells for UE category NB1 in enhanced coverage ........... 107
4.6.2.7 Maximum interruption in paging reception in normal coverage ......................................................... 108
4.6.2.7A Maximum interruption in paging reception in enhanced coverage ..................................................... 108
4.6.2.8 UE measurement capability ................................................................................................................ 108
4.7 Cell Selection and Re-selection Requirements for UE category M2 .............................................................. 108
4.7.1 Cell Selection ............................................................................................................................................ 108
4.7.2 Cell Re-selection ....................................................................................................................................... 109
4.7.2.1 Cell Re-selection requirements for UE category M2 in normal coverage ........................................... 109
4.7.2.1.1 Measurement and evaluation of serving cell for UE category M2 in normal coverage ................. 109
4.7.2.1.2 Measurements of intra-frequency cells for UE category M2 in normal coverage ......................... 109
4.7.2.1.3 Measurements of inter-frequency cells for UE category M2 in normal coverage ......................... 109
4.7.2.1.4 Maximum allowed layers for multiple monitoring for UE category M2 in normal coverage ....... 109
4.7.2.2 Cell Re-selection requirements for UE category M2 in enhanced coverage ....................................... 109
4.7.2.2.1 Measurement and evaluation of serving cell for UE category M2 in enhanced coverage ............. 109
4.7.2.2.2 Measurements of intra-frequency cells for UE category M2 in enhanced coverage ..................... 109
4.7.2.2.3 Measurements of inter-frequency cells for UE category M2 in enhanced coverage ..................... 110
4.7.2.2.4 Maximum allowed layers for multiple monitoring for UE category M2 in enhanced coverage ... 111
5 E-UTRAN RRC_CONNECTED state mobility ..................................................................................112
5.1 E-UTRAN Handover ...................................................................................................................................... 112
5.1.1 Introduction............................................................................................................................................... 112
5.1.2 Requirements ............................................................................................................................................ 112
5.1.2.1 E-UTRAN FDD – FDD ...................................................................................................................... 112
5.1.2.1.1 Handover delay.............................................................................................................................. 112
5.1.2.1.2 Interruption time ............................................................................................................................ 113
5.2.2.2 E-UTRAN FDD – TDD ...................................................................................................................... 114
5.2.2.2.1 (Void) ............................................................................................................................................ 114
5.2.2.2.2 (Void) ............................................................................................................................................ 114
5.2.2.3 E-UTRAN TDD – FDD ...................................................................................................................... 114
5.2.2.3.1 (Void) ............................................................................................................................................ 114
5.2.2.3.2 (Void) ............................................................................................................................................ 114
5.2.2.4 E-UTRAN TDD – TDD ...................................................................................................................... 114
5.2.2.4.1 Handover delay ................................................................................................................................... 115
5.2.2.4.2 Interruption time ............................................................................................................................ 115
5.2.2.5 E-UTRAN HD–FDD .......................................................................................................................... 116
5.2.2.5.1 Handover delay.............................................................................................................................. 116
5.2.2.5.2 Interruption time ............................................................................................................................ 117
5.3 Handover to other RATs ................................................................................................................................ 118
5.3.1 E-UTRAN - UTRAN FDD Handover ...................................................................................................... 118
5.3.1.1 Introduction ......................................................................................................................................... 118
5.3.1.1.1 Handover delay.............................................................................................................................. 118
5.3.1.1.2 Interruption time ............................................................................................................................ 118
5.3.2 E-UTRAN - UTRAN TDD Handover ...................................................................................................... 119
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 5 ETSI TS 136 133 V14.3.0 (2017-04)
5.3.2.1 Introduction ......................................................................................................................................... 119
5.3.2.2 Requirements ...................................................................................................................................... 119
5.3.2.2.1 Handover delay.............................................................................................................................. 119
5.3.2.2.2 Interruption time ............................................................................................................................ 120
5.3.3 E-UTRAN - GSM Handover .................................................................................................................... 120
5.3.3.1 Introduction ......................................................................................................................................... 120
5.3.3.2 Requirements ...................................................................................................................................... 120
5.3.3.2.1 Handover delay.............................................................................................................................. 120
5.3.3.2.2 Interruption time ............................................................................................................................ 121
5.4 Handover to Non-3GPP RATs ....................................................................................................................... 121
5.4.1 E-UTRAN – HRPD Handover.................................................................................................................. 121
5.4.1.1 Introduction ................................................................................................................................... 121
5.4.1.1.1 Handover delay.............................................................................................................................. 121
5.4.1.1.2 Interruption time ............................................................................................................................ 121
5.4.2 E-UTRAN – cdma2000 1X Handover ...................................................................................................... 122
5.4.2.1 Introduction ................................................................................................................................... 122
5.4.2.1.1 Handover delay.............................................................................................................................. 122
5.4.2.1.2 Interruption time ............................................................................................................................ 122
5.5 E-UTRAN Handover for Cat-M1 UEs in CEModeA..................................................................................... 123
5.5.1 Introduction............................................................................................................................................... 123
5.5.2 Requirements ............................................................................................................................................ 123
5.5.2.1 E-UTRAN FDD – FDD for Cat-M1 FDD UEs .................................................................................. 123
5.5.2.1.1 Handover delay.............................................................................................................................. 123
5.5.2.1.2 Interruption time ............................................................................................................................ 123
5.5.2.2 E-UTRAN FDD – FDD for Cat-M1 HD – FDD UEs ......................................................................... 123
5.5.2.3 E-UTRAN TDD – TDD for Cat-M1 TDD UEs .................................................................................. 124
5.5.2.3.1 Handover delay.............................................................................................................................. 124
5.5.2.3.2 Interruption time ............................................................................................................................ 124
5.6 E-UTRAN Handover for Cat-M1 UEs in CEModeB ..................................................................................... 124
5.6.1 Introduction............................................................................................................................................... 124
5.6.2 Requirements ............................................................................................................................................ 124
5.6.2.1 E-UTRAN FDD – FDD for Cat-M1 FDD UEs .................................................................................. 124
5.6.2.1.1 Handover delay.............................................................................................................................. 125
5.6.2.1.2 Interruption time ............................................................................................................................ 125
5.6.2.2 E-UTRAN FDD – FDD for Cat-M1 HD – FDD UEs ......................................................................... 125
5.6.2.3 E-UTRAN TDD – TDD for Cat-M1 TDD UEs .................................................................................. 125
5.6.2.3.1 Handover delay.............................................................................................................................. 125
5.6.2.3.2 Interruption time ............................................................................................................................ 126
6 RRC Connection Mobility Control ......................................................................................................126
6.1 RRC Re-establishment ................................................................................................................................... 126
6.1.1 Introduction............................................................................................................................................... 126
6.1.2 Requirements ............................................................................................................................................ 126
6.1.2.1 UE Re-establishment delay requirement ............................................................................................. 127
6.2 Random Access .............................................................................................................................................. 127
6.2.1 Introduction............................................................................................................................................... 127
6.2.2 Requirements ............................................................................................................................................ 127
6.2.2.1 Contention based random access......................................................................................................... 127
6.2.2.1.1 Correct behaviour when receiving Random Access Response reception ...................................... 127
6.2.2.1.2 Correct behaviour when not receiving Random Access Response reception ................................ 128
6.2.2.1.3 Correct behaviour when receiving a NACK on msg3 ................................................................... 128
6.2.2.1.4 Void ............................................................................................................................................... 128
6.2.2.1.5 Correct behaviour when receiving a message over Temporary C-RNTI ....................................... 128
6.2.2.1.6 Correct behaviour when contention Resolution timer expires ....................................................... 128
6.2.2.2 Non-Contention based random access ................................................................................................ 128
6.2.2.2.1 Correct behaviour when receiving Random Access Response ...................................................... 128
6.2.2.2.2 Correct behaviour when not receiving Random Access Response ................................................ 128
6.2.3 Requirements for Cat-M1 UEs ................................................................................................................. 128
6.3 RRC Connection Release with Redirection.................................................................................................... 129
6.3.1 Introduction............................................................................................................................................... 129
6.3.2 Requirements ............................................................................................................................................ 129
6.3.2.1 RRC connection release with redirection to UTRAN FDD ................................................................ 129
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 6 ETSI TS 136 133 V14.3.0 (2017-04)
6.3.2.2 RRC connection release with redirection to GERAN ......................................................................... 129
6.3.2.3 RRC connection release with redirection to UTRAN TDD ................................................................ 130
6.4 CSG Proximity Indication for E-UTRAN and UTRAN ................................................................................. 130
6.4.1 Introduction............................................................................................................................................... 130
6.4.2 Requirements ............................................................................................................................................ 130
6.5 RRC Re-establishment for NB-IoT UEs ........................................................................................................ 131
6.5.1 Introduction............................................................................................................................................... 131
6.5.2 Requirements ............................................................................................................................................ 131
6.5.2.1 UE Re-establishment delay requirement in normal coverage ............................................................. 131
6.5.2.2 UE Re-establishment delay requirement in enhanced coverage.......................................................... 131
6.6 Random Access for UE category NB1 ........................................................................................................... 132
6.6.1 Introduction............................................................................................................................................... 132
6.6.2 Requirements ............................................................................................................................................ 132
6.6.2.1 Correct behaviour when receiving Random Access Response reception ............................................ 132
6.6.2.2 Correct behaviour when not receiving Random Access Response reception ...................................... 132
6.6.2.3 Correct behaviour when receiving a NACK on msg3 ......................................................................... 132
6.6.2.4 Correct behaviour when receiving a message over Temporary C-RNTI ............................................ 132
6.6.2.5 Correct behaviour when contention Resolution timer expires ............................................................ 133
6.6.3 Requirements for NPRACH configuration ............................................................................................... 133
6.7 RRC Re-establishment for Cat-M1 UEs ........................................................................................................ 133
6.7.1 Introduction............................................................................................................................................... 133
6.7.2 Requirements ............................................................................................................................................ 133
6.7.2.1 UE Re-establishment delay requirement for CEModeA ..................................................................... 133
6.7.2.2 UE Re-establishment delay requirement for CEModeB ..................................................................... 134
6.8 RRC Connection Release with Redirection for Cat-M1 UEs ......................................................................... 134
6.8.1 Introduction............................................................................................................................................... 134
6.8.2 Requirements ............................................................................................................................................ 135
6.8.2.1 RRC connection release with redirection to E-UTRAN with CE Mode A ......................................... 135
6.9 RRC Connection Redirection to Non-anchor Carrier in NB-IoT ................................................................... 135
6.9.1 Introduction............................................................................................................................................... 135
6.9.2 Requirements ............................................................................................................................................ 135
7 Timing and signalling characteristics ...................................................................................................136
7.1 UE transmit timing ......................................................................................................................................... 136
7.1.1 Introduction............................................................................................................................................... 136
7.1.2 Requirements ............................................................................................................................................ 136
7.2 UE timer accuracy .......................................................................................................................................... 137
7.2.1 Introduction............................................................................................................................................... 137
7.2.2 Requirements ............................................................................................................................................ 138
7.3 Timing Advance ............................................................................................................................................. 138
7.3.1 Introduction............................................................................................................................................... 138
7.3.2 Requirements ............................................................................................................................................ 138
7.3.2.1 Timing Advance adjustment delay ...................................................................................................... 138
7.3.2.2 Timing Advance adjustment accuracy ................................................................................................ 138
7.4 Cell phase synchronization accuracy (TDD) .................................................................................................. 138
7.4.1 Definition .................................................................................................................................................. 138
7.4.2 Minimum requirements............................................................................................................................. 138
7.5 Synchronization Requirements for E-UTRAN to 1xRTT and HRPD Handovers.......................................... 139
7.5.1 Introduction............................................................................................................................................... 139
7.5.2 eNodeB Synchronization Requirements ................................................................................................... 139
7.5.2.1 Synchronized E-UTRAN .................................................................................................................... 139
7.5.2.2 Non-Synchronized E-UTRAN ............................................................................................................ 139
7.6 Radio Link Monitoring ................................................................................................................................... 140
7.6.1 Introduction............................................................................................................................................... 140
7.6.2 Requirements ............................................................................................................................................ 141
7.6.2.1 Minimum requirement when no DRX is used..................................................................................... 141
7.6.2.2 Minimum requirement when DRX is used.......................................................................................... 142
7.6.2.3 Minimum requirement at transitions ................................................................................................... 143
7.6.2.4 Minimum requirement during SI Acquisition with autonomous gaps ................................................ 143
7.6.2.5 Minimum requirement under IDC Interference .................................................................................. 144
7.7 SCell Activation and Deactivation Delay for E-UTRA Carrier Aggregation ................................................ 144
7.7.1 Introduction............................................................................................................................................... 144
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 7 ETSI TS 136 133 V14.3.0 (2017-04)
7.7.2 SCell Activation Delay Requirement for Deactivated SCell .................................................................... 144
7.7.3 SCell Deactivation Delay Requirement for Activated SCell .................................................................... 145
7.7.4 SCell Activation Delay Requirement for Deactivated SCell with Muliple Downlnk SCells.................... 145
7.7.5 SCell Deactivation Delay Requirement for Activated SCell with Multiple Downlink SCells ................. 146
7.7.6 SCell Activation Delay Requirement for Deactivated PUCCH SCell ...................................................... 146
7.7.7 SCell Activation Delay Requirement for Deactivated PUCCH SCell with Multiple SCells .................... 147
7.7.8 SCell Deactivation Delay Requirement for Activated PUCCH SCell ...................................................... 148
7.7.9 SCell Deactivation Delay Requirement for Activated PUCCH SCell with Multiple SCells .................... 148
7.7.10 SCell Activation Delay Requirement for Deactivated SCell under Frame Structure 3............................. 148
7.7.11 SCell Deactivation Delay Requirement for Activated SCell under Frame Structure 3............................. 149
7.7.12 SCell Activation Delay Requirement for Deactivated SCell with Multiple Downlink SCells under
Frame Structure 3 ..................................................................................................................................... 149
7.7.13 SCell Deactivation Delay Requirement for Activated SCell with Multiple Downlink SCells under
Frame Structure 3 ..................................................................................................................................... 150
7.8 Interruptions with Carrier Aggregation .......................................................................................................... 150
7.8.1 Introduction............................................................................................................................................... 150
7.8.2 Requirements ............................................................................................................................................ 151
7.8.2.1 Interruptions at SCell addition/release for intra-band CA ................................................................... 151
7.8.2.2 Interruptions at SCell addition/release for inter-band CA ................................................................... 151
7.8.2.3 Interruptions at SCell activation/deactivation for intra-band CA ........................................................ 151
7.8.2.4 Interruptions at SCell activation/deactivation for inter-band CA ........................................................ 151
7.8.2.5 Interruptions during measurements on SCC for intra-band CA .......................................................... 151
7.8.2.6 Interruptions during measurements on SCC for inter-band CA .......................................................... 151
7.8.2.7 Interruptions at SCell addition/release with multiple downlink SCells............................................... 151
7.8.2.8 Interruptions at SCell activation/deactivation with multiple downlink SCells.................................... 152
7.8.2.9 Interruptions during measurements on SCC with multiple downlink SCells ...................................... 152
7.8.2.10 Interruptions at overlapping addition/release/activation/deactivation of SCells ................................. 153
7.8.2.11 Interruptions during RSSI measurements on one SCC under Frame Structure 3 ................................ 153
7.8.2.12 Interruptions during RSSI measurements on multiple SCCs under Frame Structure 3 ....................... 153
7.8.2.13 Interruptions at SRS carrier based switching ...................................................................................... 154
7.9 Maximum Transmission Timing Difference in Carrier Aggregation ............................................................. 155
7.9.1 Introduction............................................................................................................................................... 155
7.9.2 Minimum Requirements for Interband Carrier Aggregation .................................................................... 155
7.9.3 Minimum Requirements for Intraband non-contiguous Carrier Aggregation ........................................... 155
7.9.4 Minimum Requirements for Inter-Band Carrier Aggregation under Frame Structure 3 ........................... 155
7.10 Interruptions with RSTD Measurements with Carrier Aggregation ............................................................... 156
7.10.1 Introduction............................................................................................................................................... 156
7.10.2 Requirements ............................................................................................................................................ 156
7.10.2.1 Interruptions during RSTD measurements on SCC for intra-band CA with one downlink SCell ...... 156
7.10.2.2 Interruptions during RSTD measurements on SCC for inter-band CA with one downlink SCell ...... 156
7.10.2.3 Interruptions during RSTD measurements on SCC with multiple downlink SCells ........................... 156
7.10.2.4 Interruptions at overlapping RSTD and inter-frequency measurements ............................................. 157
7.11 Radio Link Monitoring for UE Category 0 .................................................................................................... 157
7.11.1 Introduction............................................................................................................................................... 157
7.11.2 Requirements for FD-FDD and TDD ....................................................................................................... 158
7.11.2.1 Minimum requirement when no DRX is used..................................................................................... 158
7.11.2.2 Minimum requirement when DRX is used.......................................................................................... 159
7.11.2.3 Minimum requirement at transitions ................................................................................................... 160
7.11.3 Requirements for HD-FDD ...................................................................................................................... 160
7.11.3.1 Minimum requirement when no DRX is used..................................................................................... 160
7.11.3.2 Minimum requirement when DRX is used.......................................................................................... 160
7.11.3.3 Minimum requirement at transitions ................................................................................................... 161
7.12 Interruptions with Dual Connectivity ............................................................................................................. 161
7.12.1 Introduction............................................................................................................................................... 161
7.12.2 Requirements ............................................................................................................................................ 161
7.12.2.1 Interruptions at PSCell addition/release .............................................................................................. 161
7.12.2.2 Interruptions at transitions between active and non-active during DRX ............................................. 161
7.12.2.3 Interruptions at transitions from non-DRX to DRX ............................................................................ 162
7.12.2.4 Interruptions at SCell addition/release ................................................................................................ 162
7.12.2.5 Interruptions at SCell activation/deactivation ..................................................................................... 162
7.12.2.6 Interruptions during measurements on SCC ....................................................................................... 163
7.12.2.7 Interruptions at SRS carrier based switching ...................................................................................... 163
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 8 ETSI TS 136 133 V14.3.0 (2017-04)
7.13 Cell phase synchronization accuracy (Synchronized mode of dual connectivity) .......................................... 164
7.13.1 Definition .................................................................................................................................................. 164
7.13.2 Minimum requirements............................................................................................................................. 164
7.14 PSCell Addition and Release Delay for E-UTRA Dual Connectivity ............................................................ 164
7.14.1 Introduction............................................................................................................................................... 164
7.14.2 PSCell Addition Delay Requirement ........................................................................................................ 164
7.14.3 PSCell Release Delay Requirement .......................................................................................................... 165
7.15 Maximum Receive Timing Difference in Dual Connectivity ........................................................................ 165
7.15.1 Introduction............................................................................................................................................... 165
7.15.2 Minimum Requirements for Inter-band Dual Connectivity ...................................................................... 165
7.16 Proximity-based Services ............................................................................................................................... 165
7.16.1 Introduction............................................................................................................................................... 165
7.16.2 Requirements ............................................................................................................................................ 166
7.16.2.1 ProSe UE transmission timing ............................................................................................................ 166
7.16.2.1.1 Serving cell or PCell as timing reference ...................................................................................... 166
7.16.2.1.2 SCell or non-serving cell as timing reference ................................................................................ 166
7.16.3 Interruptions with ProSe ........................................................................................................................... 166
7.16.3.1 Interruptions at ProSe Direct Discovery configuration ....................................................................... 167
7.16.3.2 Interruptions at ProSe Direct Communication configuration .............................................................. 167
7.16.3.3 Interruptions during ProSe Direct Discovery ...................................................................................... 167
7.16.3.4 Interruptions during ProSe Direct Discovery with discovery gaps ..................................................... 167
7.16.3.5 Interruptions during ProSe Direct Communication ............................................................................. 168
7.16.4 Cell reselection for ProSe Direct Discovery on non-serving frequency ................................................... 168
7.16.4.1 Measurement and evaluation of selected cell ...................................................................................... 168
7.16.4.2 Measurement of intra-frequency E-UTRAN cells .............................................................................. 168
7.16.5 Selection / Reselection of ProSe relay UE ................................................................................................ 169
7.17 Maximum Transmission Timing Difference in Dual Connectivity ................................................................ 169
7.17.1 Introduction............................................................................................................................................... 169
7.17.2 Minimum Requirements for maximum transmission timing difference Inter-band Dual Connectivity ... 170
7.18.1 Introduction............................................................................................................................................... 170
7.18.2 SCell Activation Delay Requirement for Deactivated SCell .................................................................... 170
7.18.3 SCell Deactivation Delay Requirement for Activated SCell .................................................................... 170
7.19 Radio Link Monitoring for UE Category M1 ................................................................................................. 170
7.19.1 Introduction............................................................................................................................................... 170
7.19.2 Requirements for FD-FDD and TDD CE mode A.................................................................................... 170
7.19.2.1 Minimum requirement when no DRX is used..................................................................................... 171
7.19.2.2 Minimum requirement when DRX is used.......................................................................................... 171
7.19.2.3 Minimum requirement at transitions ................................................................................................... 172
7.19.3 Requirements for HD-FDD with CE mode A ........................................................................................... 172
7.19.3.1 Minimum requirement when no DRX is used..................................................................................... 172
7.19.3.2 Minimum requirement when DRX is used.......................................................................................... 172
7.19.3.3 Minimum requirement at transitions ................................................................................................... 173
7.19.4 Requirements for FD-FDD and TDD with CE mode B ............................................................................ 174
7.19.4.1 Minimum requirement when no DRX is used..................................................................................... 174
7.19.4.2 Minimum requirement when DRX is used.......................................................................................... 174
7.19.4.3 Minimum requirement at transitions ................................................................................................... 175
7.19.5 Requirements for HD-FDD with CE mode B ........................................................................................... 175
7.19.5.1 Minimum requirement when no DRX is used..................................................................................... 176
7.19.5.2 Minimum requirement when DRX is used.......................................................................................... 176
7.19.5.3 Minimum requirement at transitions ................................................................................................... 177
7.20 UE transmit timing for NB-IoT ...................................................................................................................... 177
7.20.1 Introduction............................................................................................................................................... 177
7.20.2 Requirements ............................................................................................................................................ 177
7.21 UE timer accuracy for NB-IoT ....................................................................................................................... 178
7.21.1 Introduction............................................................................................................................................... 178
7.21.2 Requirements ............................................................................................................................................ 178
7.22 Timing Advance for NB-IoT .......................................................................................................................... 178
7.22.1 Introduction............................................................................................................................................... 178
7.22.2 Requirements ............................................................................................................................................ 178
7.22.2.1 Timing Advance adjustment delay ...................................................................................................... 178
7.22.2.2 Timing Advance adjustment accuracy ................................................................................................ 178
7.23 Radio Link Monitoring for Category NB1 UE ............................................................................................... 179
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 9 ETSI TS 136 133 V14.3.0 (2017-04)
7.23.1 Introduction............................................................................................................................................... 179
7.23.2 Requirements for HD-FDD Category NB1 UE ........................................................................................ 179
7.23.2.1 Minimum requirement when no DRX is used..................................................................................... 179
7.23.2.2 Minimum requirement when DRX is used.......................................................................................... 180
7.23.2.3 Minimum requirement at transitions ................................................................................................... 180
7.24 UE transmit timing for Category M1 ............................................................................................................. 181
7.24.1 Introduction............................................................................................................................................... 181
7.24.2 Requirements ............................................................................................................................................ 181
7.25 Cell phase synchronization accuracy for MBMS services (FDD) .................................................................. 182
7.25.1 Definition .................................................................................................................................................. 182
7.25.2 Minimum requirements............................................................................................................................. 182
8 UE Measurements Procedures in RRC_CONNECTED State .............................................................182
8.1 General Measurement Requirements.............................................................................................................. 182
8.1.1 Introduction............................................................................................................................................... 182
8.1.2 Requirements ............................................................................................................................................ 183
8.1.2.1 UE measurement capability ................................................................................................................ 183
8.1.2.1.1 Monitoring of multiple layers using gaps ...................................................................................... 184
8.1.2.1.1a Monitoring of multiple layers using gaps (Increased UE carrier monitoring) ............................... 186
8.1.2.2 E-UTRAN intra frequency measurements .......................................................................................... 187
8.1.2.2.1 E-UTRAN FDD intra frequency measurements ............................................................................ 187
8.1.2.2.2 E-UTRAN TDD intra frequency measurements ........................................................................... 191
8.1.2.2.3 E-UTRAN FDD intra frequency measurements with autonomous gaps ....................................... 195
8.1.2.2.4 E-UTRAN TDD intra frequency measurements with autonomous gaps ....................................... 196
8.1.2.3 E-UTRAN inter frequency measurements .......................................................................................... 197
8.1.2.3.1 E-UTRAN FDD – FDD inter frequency measurements ................................................................ 197
8.1.2.3.2 E-UTRAN TDD – TDD inter frequency measurements ............................................................... 201
8.1.2.3.3 E-UTRAN TDD – FDD inter frequency measurements................................................................ 205
8.1.2.3.4 E-UTRAN FDD – TDD inter frequency measurements................................................................ 205
8.1.2.3.5 E-UTRAN FDD-FDD inter frequency measurements with autonomous gaps .............................. 205
8.1.2.3.6 E-UTRAN TDD-FDD inter frequency measurements using autonomous gaps ............................ 206
8.1.2.3.7 E-UTRAN TDD-TDD inter frequency measurements with autonomous gaps ............................. 207
8.1.2.3.8 E-UTRAN FDD-TDD inter frequency measurements using autonomous gaps ............................ 208
8.1.2.4 Inter RAT measurements .................................................................................................................... 209
8.1.2.4.1 E-UTRAN FDD – UTRAN FDD measurements .......................................................................... 209
8.1.2.4.2 E-UTRAN TDD – UTRAN FDD measurements .......................................................................... 214
8.1.2.4.3 E-UTRAN TDD – UTRAN TDD measurements .......................................................................... 214
8.1.2.4.4 E-UTRAN FDD – UTRAN TDD measurements .......................................................................... 218
8.1.2.4.5 E-UTRAN FDD – GSM measurements ........................................................................................ 218
8.1.2.4.6 E-UTRAN TDD – GSM measurements ........................................................................................ 224
8.1.2.4.7 E-UTRAN FDD – UTRAN FDD measurements for SON ............................................................ 224
8.1.2.4.8 E-UTRAN TDD – UTRAN FDD measurements for SON............................................................ 226
8.1.2.4.9 E-UTRAN FDD – cdma2000 1xRTT measurements .................................................................... 226
8.1.2.4.9.1A E-UTRAN FDD – cdma2000 1xRTT measurements when no DRX is used ................................ 226
8.1.2.4.10 E-UTRAN TDD – cdma2000 1xRTT measurements .................................................................... 226
8.1.2.4.11 E-UTRAN FDD – HRPD measurements ...................................................................................... 226
8.1.2.4.12 E-UTRAN TDD – HRPD measurements ...................................................................................... 226
8.1.2.4.13 E-UTRAN TDD – UTRAN TDD measurements for SON ........................................................... 226
8.1.2.4.14 E-UTRAN FDD – UTRAN TDD measurements for SON............................................................ 228
8.1.2.4.15 E-UTRAN FDD – cdma2000 1xRTT measurements for SON ANR ............................................ 228
8.1.2.4.16 E-UTRAN TDD – cdma2000 1xRTT measurements for SON ANR ............................................ 229
8.1.2.4.17 E-UTRAN FDD-UTRAN FDD measurements with autonomous gaps ........................................ 229
8.1.2.4.18 E-UTRAN TDD-UTRAN FDD measurements with autonomous gaps ........................................ 229
8.1.2.4.19 E-UTRAN FDD – WLAN measurements ..................................................................................... 230
8.1.2.4.20 E-UTRAN TDD – WLAN measurements ..................................................................................... 231
8.1.2.5 E-UTRAN OTDOA Intra-Frequency RSTD Measurements .............................................................. 231
8.1.2.5.1 E-UTRAN FDD Intra-Frequency OTDOA Measurements ........................................................... 232
8.1.2.5.2 E-UTRAN TDD Intra-Frequency OTDOA Measurements ........................................................... 233
8.1.2.6 E-UTRAN Inter-Frequency OTDOA Measurements.......................................................................... 235
8.1.2.6.1 E-UTRAN FDD-FDD Inter-Frequency OTDOA Measurements .................................................. 235
8.1.2.6.2 E-UTRAN TDD-FDD Inter-Frequency OTDOA Measurements ................................................. 237
8.1.2.6.3 E-UTRAN TDD-TDD Inter-Frequency OTDOA Measurements ................................................. 238
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 10 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.6.4 E-UTRAN FDD-TDD Inter-Frequency OTDOA Measurements ................................................. 240
8.1.2.7 E-UTRAN E-CID Measurements ....................................................................................................... 242
8.1.2.7.1 E-UTRAN FDD UE Rx-Tx Time Difference Measurements ....................................................... 242
8.1.2.7.2 E-UTRAN TDD UE Rx-Tx Time Difference Measurements ....................................................... 243
8.1.2.7.3 E-UTRAN FDD Intra-frequency E-CID RSRP and RSRQ Measurements .................................. 245
8.1.2.7.4 E-UTRAN TDD Intra-frequency E-CID RSRP and RSRQ Measurements .................................. 245
8.1.2.8 E-UTRAN intra-frequency measurements under time domain measurement resource restriction ..... 246
8.1.2.8.1 E-UTRAN FDD intra-frequency measurements ........................................................................... 246
8.1.2.8.2 E-UTRAN TDD intra-frequency measurements ........................................................................... 249
8.1.2.8.3 E-UTRAN FDD intra-frequency measurements with CRS assistance information ...................... 252
8.1.2.8.4 E-UTRAN TDD intra-frequency measurements with CRS assistance infromation ...................... 255
8.1.2.9 E-UTRAN E-CID Measurements when Time Domain Measurement Resource Restriction
Pattern is Configured........................................................................................................................... 259
8.1.2.9.1 E-UTRAN FDD UE Rx-Tx Time Difference Measurements ....................................................... 259
8.1.2.9.2 E-UTRAN TDD UE Rx-Tx Time Difference Measurements ....................................................... 259
8.1.2.9.3 E-UTRAN FDD UE Rx-Tx Time Difference Measurements with CRS Assistance
Information .................................................................................................................................... 260
8.1.2.9.4 E-UTRAN TDD UE Rx-Tx Time Difference Measurements with CRS Assistance
Information .................................................................................................................................... 260
8.2 Capabilities for Support of Event Triggering and Reporting Criteria ............................................................ 261
8.2.1 Introduction............................................................................................................................................... 261
8.2.2 Requirements ............................................................................................................................................ 261
8.3 Measurements for E-UTRA carrier aggregation ............................................................................................ 264
8.3.1 Introduction............................................................................................................................................... 264
8.3.2 Measurements of the primary component carrier ..................................................................................... 264
8.3.3 Measurements of a secondary component carrier ..................................................................................... 264
8.3.3.1 Measurements of a secondary component carrier with active SCell ................................................... 264
8.3.3.2 Measurements of a secondary component carrier with deactivated SCell .......................................... 265
8.3.3.2.1 E-UTRAN secondary component carrier measurements when no common DRX is used ............ 265
8.3.3.2.2 E-UTRAN secondary component carrier measurements when common DRX is used ................. 266
8.4 OTDOA RSTD Measurements for E-UTRAN carrier aggregation ............................................................... 267
8.4.1 Introduction............................................................................................................................................... 267
8.4.2 Measurements on the primary component carrier ..................................................................................... 268
8.4.3 Measurements on a secondary component carrier .................................................................................... 268
8.4.4 Measurements on both primary component carrier and a secondary component carrier .......................... 269
8.4.5 Measurements on different secondary component carriers ....................................................................... 270
8.5 Measurements for UE category 0 ................................................................................................................... 271
8.5.1 Introduction............................................................................................................................................... 271
8.5.2 Requirements ............................................................................................................................................ 271
8.5.2.1 E-UTRAN intra frequency measurements .......................................................................................... 271
8.5.2.1.1 E-UTRAN FDD intra frequency measurements ............................................................................ 271
8.5.2.1.2 E-UTRAN intra frequency measurements for HD-FDD ............................................................... 275
8.5.2.1.3 E-UTRAN TDD intra frequency measurements ........................................................................... 277
8.5.2.1.4 E-UTRAN FDD intra frequency measurements with autonomous gaps for UE category 0 ......... 280
8.5.2.1.5 E-UTRAN intra frequency measurements with autonomous gaps for HD-FDD UE category 0 .. 281
8.5.2.1.6 E-UTRAN TDD intra frequency measurements with autonomous gaps for UE category 0 ......... 281
8.6 Discovery signal measurements ..................................................................................................................... 282
8.6.1 Introduction............................................................................................................................................... 282
8.6.2 Requirements for CRS based discovery signal measurements ................................................................. 282
8.6.2.1 E-UTRAN intra frequency measurements .......................................................................................... 282
8.6.2.1.1 E-UTRAN FDD intra frequency measurements ............................................................................ 283
8.6.2.1.2 E-UTRAN TDD intra frequency measurements ........................................................................... 285
8.6.2.2 E-UTRAN inter frequency measurements .......................................................................................... 288
8.6.2.2.1 E-UTRAN FDD – FDD inter-frequency measurements ............................................................... 288
8.6.2.2.2 E-UTRAN TDD – TDD inter frequency measurements ............................................................... 291
8.6.2.2.3 E-UTRAN TDD – FDD inter frequency measurements................................................................ 293
8.6.2.2.4 E-UTRAN FDD – TDD inter frequency measurements................................................................ 294
8.6.3 Requirements for CSI-RS based discovery signal measurements............................................................. 294
8.6.3.1 E-UTRAN intra frequency measurements .......................................................................................... 294
8.6.3.1.1 E-UTRAN FDD intra frequency measurements ............................................................................ 294
8.6.3.1.2 E-UTRAN TDD intra frequency measurements ........................................................................... 297
8.6.3.2 E-UTRAN inter frequency measurements .......................................................................................... 299
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 11 ETSI TS 136 133 V14.3.0 (2017-04)
8.6.3.2.1 E-UTRAN FDD – FDD inter frequency measurements ................................................................ 299
8.6.3.2.2 E-UTRAN TDD – TDD inter frequency measurements ............................................................... 302
8.6.3.2.3 E-UTRAN TDD – FDD inter frequency measurements................................................................ 305
8.6.3.2.4 E-UTRAN FDD – TDD inter frequency measurements................................................................ 305
8.7 Discovery signal measurements for E-UTRA carrier aggregation ................................................................. 305
8.7.1 Introduction............................................................................................................................................... 305
8.7.2 Requirements for CRS based discovery signal measurements for E-UTRA carrier aggregation ............. 305
8.7.2.1 Measurements of the primary component carrier ................................................................................ 305
8.7.2.2 Measurements of a secondary component carrier ............................................................................... 305
8.7.2.3 Measurements of a secondary component carrier with active SCell ................................................... 306
8.7.2.4 Measurements of a secondary component carrier with deactivated SCell .......................................... 306
8.7.2.4.1 E-UTRAN secondary component carrier measurements when no common DRX is used ............ 306
8.7.2.4.2 E-UTRAN secondary component carrier measurements when common DRX is used ................. 307
8.7.3 Requirements for CSI-RS based discovery signal measurements for E-UTRA carrier aggregation ........ 309
8.7.3.1 Measurements of the primary component carrier ................................................................................ 309
8.7.3.2 Measurements of a secondary component carrier ............................................................................... 309
8.7.3.3 Measurements of a secondary component carrier with active SCell ................................................... 309
8.7.3.4 Measurements of a secondary component carrier with deactivated SCell .......................................... 309
8.7.3.4.1 E-UTRAN secondary component carrier measurements when no common DRX is used ............ 309
8.7.3.4.2 E-UTRAN secondary component carrier measurements when common DRX is used ................. 311
8.8 Measurements for E-UTRA dual connectivity ............................................................................................... 312
8.8.1 Introduction............................................................................................................................................... 312
8.8.2 Intra-frequency measurements requirements on PCell ............................................................................. 312
8.8.3 Intra-frequency measurements requirements on PSCell ........................................................................... 313
8.8.4 Inter-frequency and inter-RAT measurement requirements ..................................................................... 313
8.8.5 Intra-frequency measurements with autonomous gaps ............................................................................. 313
8.8.5.1 Identification of a new CGI of E-UTRA cell with autonomous gaps ................................................. 313
8.8.5.2 ECGI reporting delay .......................................................................................................................... 314
8.8.6 Inter-frequency measurements with autonomous gaps ............................................................................. 314
8.8.6.1 Identification of a new CGI of E-UTRA cell with autonomous gaps ................................................. 314
8.8.6.2 ECGI reporting delay .......................................................................................................................... 315
8.8.7 SSTD Measurements ................................................................................................................................ 315
8.8.7.1 Introduction ......................................................................................................................................... 315
8.8.7.2 SSTD Measurement requirements ...................................................................................................... 315
8.8.7.3 SSTD Measurement Reporting Delay ................................................................................................. 316
8.8.8 Intra-frequency measurements requirements on SCell ............................................................................. 316
8.9 MBSFN Measurements .................................................................................................................................. 316
8.9.1 Introduction............................................................................................................................................... 316
8.9.2 MBSFN RSRP Measurements .................................................................................................................. 316
8.9.3 MBSFN RSRQ Measurements ................................................................................................................. 317
8.9.4 MCH BLER Measurements ...................................................................................................................... 317
8.10 Proximity-based Services ............................................................................................................................... 317
8.10.1 Introduction............................................................................................................................................... 317
8.10.2 Requirements ............................................................................................................................................ 317
8.10.2.1 Initiation/Cease of SLSS transmissions with ProSe Direct Discovery................................................ 317
8.10.2.2 Initiation/Cease of SLSS transmissions with ProSe Direct Communication ...................................... 318
8.11 Discovery Signal Measurements under Operation with Frame Structure 3.................................................... 319
8.11.1 Introduction............................................................................................................................................... 319
8.11.2 CRS based discovery signal measurements .............................................................................................. 319
8.11.2.1 E-UTRAN intra-frequency measurements .......................................................................................... 319
8.11.2.1.1 Requirements ................................................................................................................................. 319
8.11.2.1.1.1 Requirements when no DRX is used ....................................................................................... 319
8.11.2.1.1.1.1 Measurement Reporting Requirements .............................................................................. 321
8.11.2.1.1.2 Requirements when DRX is used ............................................................................................ 322
8.11.2.1.1.2.1 Measurement Reporting Requirements .............................................................................. 323
8.11.2.2 E-UTRAN inter-frequency measurements .......................................................................................... 324
8.11.2.2.1 E-UTRAN FDD-FS3 inter-frequency measurements .................................................................... 324
8.11.2.2.2 E-UTRAN TDD – FS3 inter-frequency measurements ................................................................. 328
8.11.3 CSI-RS based discovery signal measurements ......................................................................................... 329
8.11.3.1 E-UTRAN intra-frequency measurements .......................................................................................... 329
8.11.3.1.1 Requirements ................................................................................................................................. 329
8.11.3.1.1.1 Requirements when no DRX is used ....................................................................................... 329
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 12 ETSI TS 136 133 V14.3.0 (2017-04)
8.11.3.1.1.1.1 Measurement Reporting Requirements .............................................................................. 330
8.11.3.1.1.2 Requirements when DRX is used ............................................................................................ 331
8.11.3.1.1.2.1 Measurement Reporting Requirements .............................................................................. 332
8.11.3.2 E-UTRAN inter-frequency measurements .......................................................................................... 333
8.11.3.2.1 E-UTRAN FDD – FS3 inter-frequency measurements ................................................................. 333
8.11.3.2.2 E-UTRAN TDD – FS3 inter-frequency measurements ................................................................. 337
8.11.4 RSSI measurements .................................................................................................................................. 337
8.11.4.1 E-UTRAN intra-frequency measurements .......................................................................................... 337
8.11.4.2 E-UTRAN inter-frequency measurements .......................................................................................... 337
8.11.5 Channel occupancy measurements ........................................................................................................... 337
8.11.5.1 E-UTRAN intra-frequency channel occupancy measurements........................................................... 337
8.11.5.2 E-UTRAN inter-frequency channel occupancy measurements........................................................... 338
8.12 Discovery Signal Measurements for E-UTRA Carrier Aggregation under Operation with Frame
Structure 3 ...................................................................................................................................................... 338
8.12.1 Introduction............................................................................................................................................... 338
8.12.2 CRS based discovery signal measurements for E-UTRA carrier aggregation .......................................... 338
8.12.2.1 Introduction ......................................................................................................................................... 338
8.12.2.2 Measurements of a secondary component carrier ............................................................................... 338
8.12.2.3 Measurements of a secondary component carrier with active SCell ................................................... 338
8.12.2.4 Measurements of a secondary component carrier with deactivated SCell .......................................... 338
8.12.2.4.1 E-UTRAN secondary component carrier measurements when no common DRX is used ............ 339
8.12.2.4.2 E-UTRAN secondary component carrier measurements when common DRX is used ................. 341
8.12.3 Requirements for CSI-RS based discovery signal measurements for E-UTRA carrier aggregation ........ 344
8.12.3.1 Introduction ......................................................................................................................................... 344
8.12.3.2 Measurements of a secondary component carrier ............................................................................... 344
8.12.3.3 Measurements of a secondary component carrier with active SCell ................................................... 344
8.12.3.4 Measurements of a secondary component carrier with deactivated SCell .......................................... 344
8.12.3.4.1 E-UTRAN secondary component carrier measurements when no common DRX is used ............ 344
8.12.3.4.2 E-UTRAN secondary component carrier measurements when common DRX is used ................. 346
8.13 Measurements for UE Category M1............................................................................................................... 348
8.13.1 Introduction............................................................................................................................................... 348
8.13.2 Requirements for UE category M1 with CE mode A ............................................................................... 348
8.13.2.1 E-UTRAN intra frequency measurements by UE category M1 with CE mode A .............................. 348
8.13.2.1.1 E-UTRAN FDD intra frequency measurements ............................................................................ 349
8.13.2.1.2 E-UTRAN intra frequency measurements for HD-FDD ............................................................... 352
8.13.2.1.3 E-UTRAN TDD intra frequency measurements ........................................................................... 354
8.13.2.2 E-UTRAN E-CID Measurements Requirements for UE category M1 with CE mode A ................... 357
8.13.2.2.1 E-UTRAN FDD Intra-frequency E-CID RSRP Measurements .................................................... 357
8.13.2.2.2 E-UTRAN HD-FDD Intra-frequency E-CID RSRP Measurements ............................................. 357
8.13.2.2.3 E-UTRAN TDD Intra-frequency E-CID RSRP Measurements .................................................... 358
8.13.3 Requirements for UE category M1 with CE mode B ............................................................................... 358
8.13.3.1 E-UTRAN intra frequency measurements by UE category M1 with CE mode B .............................. 358
8.13.3.1.1 E-UTRAN FDD intra frequency measurements ............................................................................ 358
8.13.3.1.2 E-UTRAN intra frequency measurements for HD-FDD ............................................................... 362
8.13.3.1.3 E-UTRAN TDD intra frequency measurements ........................................................................... 364
8.13.3.1.4 E-UTRAN FDD intra frequency measurements with autonomous gaps for UE category M1
with CE mode B ............................................................................................................................ 368
8.13.3.1.5 E-UTRAN intra frequency measurements with autonomous gaps for HD-FDD UE category
M1 with CE mode B ...................................................................................................................... 369
8.13.3.1.6 E-UTRAN TDD intra frequency measurements with autonomous gaps for UE category M1
with CE mode B ............................................................................................................................ 369
8.13.3.2 E-UTRAN E-CID Measurements Requirements for UE category M1 with CE mode B .................... 370
8.13.3.2.1 E-UTRAN FDD Intra-frequency E-CID RSRP Measurements .................................................... 370
8.13.3.2.2 E-UTRAN HD-FDD Intra-frequency E-CID RSRP Measurements ............................................. 371
8.13.3.2.3 E-UTRAN TDD Intra-frequency E-CID RSRP Measurements .................................................... 371
8.14 Measurements for UE category NB1.............................................................................................................. 372
8.14.1 Introduction............................................................................................................................................... 372
8.14.2 NB-IoT intra frequency measurements under normal coverage ............................................................... 372
8.14.2.1 NB-IoT intra frequency measurements when no DRX is used ........................................................... 372
8.14.2.2 NB-IoT intra frequency measurements when DRX is used ................................................................ 372
8.14.3 NB-IoT intra frequency measurements under enhanced coverage ........................................................... 372
8.14.3.1 NB-IoT intra frequency measurements when no DRX is used ........................................................... 372
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 13 ETSI TS 136 133 V14.3.0 (2017-04)
8.14.3.2 NB-IoT intra frequency measurements when DRX is used ................................................................ 372
8.15 Measurements for UE Category M2............................................................................................................... 373
8.15.1 Introduction............................................................................................................................................... 373
8.15.2 Requirements for UE category M2 with CE mode A ............................................................................... 373
8.15.2.1 Maximum allowed layers for multiple monitoring for UE category M2 with CE mode A................. 373
8.15.2.2 E-UTRAN intra frequency measurements by UE category M2 with CE mode A .............................. 373
8.15.2.2.1 E-UTRAN FDD intra frequency measurements ............................................................................ 373
8.15.2.2.2 E-UTRAN intra frequency measurements for HD-FDD ............................................................... 376
8.15.2.2.3 E-UTRAN TDD intra frequency measurements ........................................................................... 379
8.15.2.3 E-UTRAN inter frequency measurements by UE category M2 with CE mode A .............................. 382
8.15.2.3.1 E-UTRAN FDD - FDD inter frequency measurements ................................................................ 382
8.15.2.3.2 E-UTRAN inter-frequency measurements for HD-FDD ............................................................... 385
8.15.2.3.3 E-UTRAN TDD inter frequency measurements ........................................................................... 388
8.15.2.4 E-UTRAN E-CID Measurements Requirements for UE category M2 with CE mode A ................... 391
8.15.2.4.1 Intra-frequency FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in CEModeA ..... 391
8.15.2.4.2 Intra-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeA ...................................................................................................................................... 392
8.15.2.4.3 Intra-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in CEModeA ..... 392
8.15.2.4.4 Inter-frequency FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in CEModeA ..... 392
8.15.2.4.5 Inter-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeA ...................................................................................................................................... 393
8.15.2.4.6 Inter-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in CEModeA ..... 393
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.1 and 9.1.x.2.8.15.3.......... Requirements for UE category M2 with CE mode
B ............................................................................................................................................................... 394
8.15.3.1 Maximum allowed layers for multiple monitoring for UE category M2 with CE mode B ................. 394
8.15.3.2 E-UTRAN intra frequency measurements by UE category M2 with CE mode B .............................. 394
8.15.3.2.1 E-UTRAN FDD intra frequency measurements ............................................................................ 394
8.15.3.2.2 E-UTRAN intra frequency measurements for HD-FDD ............................................................... 398
8.15.3.2.3 E-UTRAN TDD intra frequency measurements ........................................................................... 401
8.15.3.3 E-UTRAN inter frequency measurements by UE category M2 with CE Mode B .............................. 405
8.15.3.3.1 E-UTRAN FDD - FDD inter frequency measurements ................................................................ 405
8.15.3.3.2 E-UTRAN inter-frequency measurements for HD-FDD ............................................................... 409
8.15.3.3.3 E-UTRAN TDD inter frequency measurements ........................................................................... 411
8.15.3.4 E-UTRAN E-CID Measurements Requirements for UE category M2 with CE mode B .................... 415
8.15.3.4.1 Intra-frequency E-CID FDD RSRP and RSRQ Measurements for Cat-M2 UE in CEModeB ..... 415
8.15.3.4.2 Intra-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeB ...................................................................................................................................... 416
8.15.3.4.3 Intra-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in CEModeB ..... 416
8.15.3.4.4 Inter-frequency E-CID FDD RSRP and RSRQ Measurements for Cat-M2 UE in CEModeB ..... 416
8.15.3.4.5 Inter-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeB ...................................................................................................................................... 417
8.15.3.4.6 Inter-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in CEModeB ..... 417
9 Measurements performance requirements for UE................................................................................418
9.1 E-UTRAN measurements ............................................................................................................................... 418
9.1.1 Introduction............................................................................................................................................... 418
9.1.2 Intra-frequency RSRP Accuracy Requirements........................................................................................ 418
9.1.2.1 Absolute RSRP Accuracy ................................................................................................................... 418
9.1.2.2 Relative Accuracy of RSRP ................................................................................................................ 419
9.1.2.3 Absolute RSRP Accuracy under Time Domain Measurement Resource Restriction ......................... 420
9.1.2.4 Relative Accuracy of RSRP under Time Domain Measurement Resource Restriction ...................... 420
9.1.2.5 Absolute RSRP Accuracy under Time Domain Measurement Resource Restriction with CRS
assistance information ......................................................................................................................... 421
9.1.2.6 Relative Accuracy of RSRP under Time Domain Measurement Resource Restriction with CRS
assistance information ......................................................................................................................... 422
9.1.2.7 Absolute RSRP Accuracy for UE Category 1bis ................................................................................ 423
9.1.2.8 Relative Accuracy of RSRP for UE Category 1bis ............................................................................. 424
9.1.2A Intra-frequency RSRP Accuracy Requirements in High Doppler Conditions .......................................... 425
9.1.2A.1 Absolute RSRP Accuracy in high Doppler conditions........................................................................ 425
9.1.2A.2 Relative Accuracy of RSRP in high Doppler conditions .................................................................... 425
9.1.3 Inter-frequency RSRP Accuracy Requirements........................................................................................ 426
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 14 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.3.1 Absolute RSRP Accuracy ................................................................................................................... 426
9.1.3.2 Relative Accuracy of RSRP ................................................................................................................ 427
9.1.3.3 Absolute RSRP Accuracy for UE Category 1bis ................................................................................ 428
9.1.3.4 Relative Accuracy of RSRP for UE Category 1bis ............................................................................. 428
9.1.3A Inter-frequency RSRP Accuracy Requirements in High Doppler Conditions .......................................... 429
9.1.3A.1 Absolute RSRP Accuracy in high Doppler conditions........................................................................ 429
9.1.3A.2 Relative Accuracy of RSRP in high Doppler conditions .................................................................... 430
9.1.4 RSRP Measurement Report Mapping ....................................................................................................... 431
9.1.5 Intra-frequency RSRQ Accuracy Requirements ....................................................................................... 431
9.1.5.1 Absolute RSRQ Accuracy................................................................................................................... 431
9.1.5.2 Absolute RSRQ Accuracy under Time Domain Measurement Resource Restriction ......................... 432
9.1.5.3 Absolute RSRQ Accuracy under Time Domain Measurement Resource Restriction with CRS
assistance information ......................................................................................................................... 433
9.1.5.4 Absolute WB-RSRQ Accuracy ........................................................................................................... 434
9.1.5.5 Absolute RSRQ Accuracy for UE Category 1bis................................................................................ 435
9.1.5A Intra-frequency RSRQ Accuracy Requirements in High Doppler Conditions ......................................... 436
9.1.5A.1 Absolute RSRQ Accuracy in high Doppler conditions ....................................................................... 436
9.1.6 Inter-frequency RSRQ Accuracy Requirements ....................................................................................... 436
9.1.6.1 Absolute RSRQ Accuracy................................................................................................................... 436
9.1.6.2 Relative Accuracy of RSRQ ............................................................................................................... 437
9.1.6.3 Absolute WB-RSRQ Accuracy ........................................................................................................... 438
9.1.6.4 Relative WB-RSRQ Accuracy ............................................................................................................ 439
9.1.6.5 Absolute RSRQ Accuracy for UE Category 1bis................................................................................ 440
9.1.6.6 Relative Accuracy of RSRQ for UE Category 1bis ............................................................................ 441
9.1.6A Inter-frequency RSRQ Accuracy Requirements in High Doppler Conditions ......................................... 442
9.1.6A.1 Absolute RSRQ Accuracy in high Doppler conditions ....................................................................... 442
9.1.6A.2 Relative Accuracy of RSRQ in high Doppler conditions .................................................................... 443
9.1.7 RSRQ Measurement Report Mapping ...................................................................................................... 444
9.1.8 Power Headroom ...................................................................................................................................... 444
9.1.8.1 Period .................................................................................................................................................. 445
9.1.8.2 Reporting Delay .................................................................................................................................. 445
9.1.8.3 Void..................................................................................................................................................... 445
9.1.8.4 Report Mapping .................................................................................................................................. 445
9.1.9 UE Rx – Tx time difference ...................................................................................................................... 445
9.1.9.1 Measurement Requirement ................................................................................................................. 445
9.1.9.2 Measurement Report mapping ............................................................................................................ 446
9.1.9.3 Measurement Requirement under Time Domain Measurement Resource Restriction ....................... 447
9.1.9.4 Measurement Requirement when Time Domain Measurement Resource Restriction Pattern is
Configured with CRS Assistance Information .................................................................................... 447
9.1.10 Reference Signal Time Difference (RSTD) .............................................................................................. 449
9.1.10.1 Intra-Frequency Accuracy Requirement ............................................................................................. 449
9.1.10.2 Inter-Frequency Accuracy Requirement ............................................................................................. 450
9.1.10.3 RSTD Measurement Report Mapping................................................................................................. 452
9.1.10.4 Higher-Resolution RSTD Measurement Report Mapping .................................................................. 452
9.1.11 Carrier aggregation measurement accuracy .............................................................................................. 453
9.1.11.1 Primary component carrier accuracy requirement .............................................................................. 453
9.1.11.2 Secondary component carrier accuracy requirement........................................................................... 453
9.1.11.3 Primary and secondary component carrier relative accuracy requirement .......................................... 453
9.1.11.4 Secondary component carrier relative accuracy requirement .............................................................. 453
9.1.12 Reference Signal Time Difference (RSTD) Measurement Accuracy Requirements for Carrier
Aggregation .............................................................................................................................................. 454
9.1.13 Measurement accuracy for UE category 0 ................................................................................................ 454
9.1.13.1 Intra-frequency Absolute RSRP Accuracy for UE category 0 ............................................................ 454
9.1.13.2 Intra-frequency Relative Accuracy of RSRP for UE category 0 ......................................................... 455
9.1.13.3 Intra-frequency Absolute RSRQ Accuracy for UE category 0 ........................................................... 455
9.1.14 Accuracy requirements for Discovery Signal Measurements ................................................................... 456
9.1.14.1 Introduction ......................................................................................................................................... 456
9.1.14.2 RSRP measurements in discovery signal occasions ............................................................................ 456
9.1.14.3 CSI-RSRP measurements in discovery signal occasions .................................................................... 457
9.1.14.3.1 Intra-frequency CSI-RSRP measurements .................................................................................... 457
9.1.14.3.1.1 Absolute CSI-RSRP measurement requirements ..................................................................... 457
9.1.14.3.1.2 Relative CSI-RSRP measurement requirements ...................................................................... 457
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 15 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.14.3.2 Inter-frequency CSI-RSRP measurements .................................................................................... 458
9.1.14.3.2.1 Absolute CSI-RSRP measurement requirements ..................................................................... 458
9.1.14.3.2.2 Relative CSI-RSRP measurement requirements ...................................................................... 459
9.1.14.3.3 CSI-RSRP measurement report mapping ...................................................................................... 460
9.1.14.4 RSRQ measurements in discovery signal occasions ........................................................................... 460
9.1.15 Discovery signal measurements accuracy for E-UTRAN carrier aggregation ......................................... 460
9.1.15.1 Requirements for CRS based discovery signal measurements accuracy for E-UTRAN carrier
aggregation .......................................................................................................................................... 460
9.1.15.1.1 Primary component carrier accuracy requirement ......................................................................... 460
9.1.15.1.2 Secondary component carrier accuracy requirement ..................................................................... 460
9.1.15.1.3 Primary and secondary component carrier relative accuracy requirement .................................... 461
9.1.15.1.4 Secondary component carrier relative accuracy requirement ........................................................ 461
9.1.15.2 Requirements for CSI-RS based discovery signal measurements accuracy for E-UTRAN carrier
aggregation .......................................................................................................................................... 461
9.1.15.2.1 Primary component carrier accuracy requirement ......................................................................... 461
9.1.15.2.2 Secondary component carrier accuracy requirement ..................................................................... 461
9.1.15.2.3 Primary and secondary component carrier relative accuracy requirement .................................... 461
9.1.15.2.4 Secondary component carrier relative accuracy requirement ........................................................ 461
9.1.16 Accuracy requirements for RSRQ measurement on all OFDM symbols ................................................. 461
9.1.17 RS-SINR Measurements ........................................................................................................................... 462
9.1.17.1 Measurement Report Mapping ............................................................................................................ 462
9.1.17.2 Intra-frequency RS-SINR Measurement Accuracy Requirements ...................................................... 462
9.1.17.2.1 Absolute RS-SINR Measurement Accuracy Requirements .......................................................... 462
9.1.17.3 Inter-frequency RS-SINR Measurement Accuracy Requirements ...................................................... 463
9.1.17.3.1 Absolute RS-SINR Measurement Accuracy Requirements .......................................................... 463
9.1.17.3.2 Relative RS-SINR Measurement Accuracy Requirements............................................................ 464
9.1.18 Accuracy Requirements for Measurements under Operation with Frame Structure 3.............................. 464
9.1.18.1 Introduction ......................................................................................................................................... 464
9.1.18.2 RSRP measurements ........................................................................................................................... 464
9.1.18.2.1 RSRP measurement report mapping .............................................................................................. 464
9.1.18.2.2 Inter-frequency absolute RSRP measurement accuracy requirements .......................................... 464
9.1.18.2.3 Inter-frequency relative RSRP measurement accuracy requirements ............................................ 465
9.1.18.2.4 Intra-frequency absolute RSRP measurement accuracy requirements .......................................... 465
9.1.18.2.5 Intra-frequency relative RSRP measurement accuracy requirements ............................................ 466
9.1.18.3 RSRQ measurements .......................................................................................................................... 467
9.1.18.3.1 RSRQ measurement report mapping ............................................................................................. 467
9.1.18.3.2 Inter-frequency absolute RSRQ measurement accuracy requirements .......................................... 467
9.1.18.3.3 Inter-frequency relative RSRQ measurement accuracy requirements ........................................... 467
9.1.18.3.4 Intra-frequency absolute RSRQ measurement accuracy requirements .......................................... 468
9.1.18.4 CSI-RSRP measurements.................................................................................................................... 468
9.1.18.4.1 CSI-RSRP measurement report mapping ...................................................................................... 468
9.1.18.4.2 Inter-frequency absolute CSI-RSRP measurement accuracy requirements ................................... 468
9.1.18.4.3 Inter-frequency relative CSI-RSRP measurement accuracy requirements .................................... 469
9.1.18.4.4 Intra-frequency absolute CSI-RSRP measurement accuracy requirements ................................... 469
9.1.18.4.5 Intra-frequency relative CSI-RSRP measurement accuracy requirements .................................... 470
9.1.18.5 RSSI measurements ............................................................................................................................ 471
9.1.18.5.1 RSSI measurement report mapping ............................................................................................... 471
9.1.18.5.2 Intra-frequency absolute RSSI measurement accuracy requirements ............................................ 471
9.1.18.5.3 Inter-frequency absolute RSSI measurement accuracy requirements ............................................ 471
9.1.18.6 Channel occupancy measurements ...................................................................................................... 471
9.1.18.6.1 Intra-frequency channel occupancy measurement accuracy requirements .................................... 471
9.1.18.6.2 Inter-frequency channel occupancy measurement accuracy requirements .................................... 472
9.1.19 Accuracy Requirements for Carrier Aggregation for Measurements under Operation with Frame
Structure 3................................................................................................................................................. 472
9.1.19.1 Introduction ......................................................................................................................................... 472
9.1.19.2 Accuracy requirements for measurements on SCC ............................................................................. 472
9.1.19.3 Relative accuracy requirements for measurements on different SCCs ............................................... 473
9.1.20 SFN and Subframe Time Difference (SSTD) ........................................................................................... 473
9.1.20.1 SSTD Accuracy Requirement ............................................................................................................. 473
9.1.20.2 SSTD Measurement Report Mapping ................................................................................................. 474
9.1.21 Measurement accuracy for UE category M1 ............................................................................................ 474
9.1.21.1 Intra-frequency Absolute RSRP Accuracy for UE category M1 with CE mode A ............................. 474
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 16 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.21.2 Intra-frequency Relative Accuracy of RSRP for UE category M1 with CE mode A.......................... 475
9.1.21.3 Intra-frequency Absolute RSRP Accuracy for UE category M1 with CE mode B ............................. 476
9.1.21.4 Intra-frequency Relative Accuracy of RSRP for UE category M1 with CE mode B .......................... 477
9.1.21.5 RSRP Measurement Report Mapping ................................................................................................. 478
9.1.22 Measurement accuracy for UE Category NB1.......................................................................................... 478
9.1.22.1 Intra-frequency Absolute NRSRP Accuracy for UE Category NB1 ................................................... 478
9.1.22.2 Void..................................................................................................................................................... 479
9.1.22.3 Intra-frequency Absolute NRSRQ Accuracy for UE Category NB1 in Normal Mode ....................... 479
9.1.22.4 Void..................................................................................................................................................... 480
9.1.22.5 Inter-frequency Absolute NRSRP Accuracy for UE Category NB1 ................................................... 480
9.1.22.6 Void..................................................................................................................................................... 480
9.1.22.7 Inter-frequency Absolute NRSRQ Accuracy for UE Category NB1 .................................................. 480
9.1.22.8 Void..................................................................................................................................................... 481
9.1.23 Power Headroom for UE Category NB1 .................................................................................................. 481
9.1.23.1 Period .................................................................................................................................................. 481
9.1.23.2 Reporting Delay .................................................................................................................................. 481
9.1.23.3 Report Mapping for UE Category NB1 .............................................................................................. 481
9.1.23.3.1 Report Mapping for UE Category NB1 in normal coverage ......................................................... 481
9.1.23.3.2 Report Mapping for UE Category NB1 in enhanced coverage ..................................................... 482
9.2 UTRAN FDD Measurements ......................................................................................................................... 482
9.2.1 UTRAN FDD CPICH RSCP .................................................................................................................... 482
9.2.2 Void .......................................................................................................................................................... 483
9.2.3 UTRAN FDD CPICH Ec/No .................................................................................................................... 483
9.3 UTRAN TDD Measurements ......................................................................................................................... 483
9.3.1 UTRAN TDD P-CCPCH RSCP ............................................................................................................... 484
9.3.2 Void .......................................................................................................................................................... 484
9.3.3 Void .......................................................................................................................................................... 484
9.4 GSM Measurements ....................................................................................................................................... 484
9.4.1 GSM carrier RSSI ..................................................................................................................................... 484
9.5 CDMA2000 1x RTT Measurements .............................................................................................................. 484
9.5.1 CDMA2000 1x RTT Pilot Strength .......................................................................................................... 485
9.6 PCMAX,c ............................................................................................................................................................ 485
9.6.1 Report Mapping ........................................................................................................................................ 485
9.6.2 Estimation Period...................................................................................................................................... 485
9.6.3 Reporting Delay ........................................................................................................................................ 485
9.7 IEEE802.11 Measurements ............................................................................................................................ 485
9.7.1 WLAN RSSI ............................................................................................................................................. 485
9.7.2 WLAN RSSI Measurement Report Mapping ........................................................................................... 486
9.8 MBSFN Measurements .................................................................................................................................. 486
9.8.1 Introduction............................................................................................................................................... 486
9.8.2 MBSFN RSRP .......................................................................................................................................... 486
9.8.2.1 Absolute MBSFN RSRP measurement accuracy requirements .......................................................... 486
9.8.2.2 MBSFN RSRP measurement report mapping ..................................................................................... 487
9.8.3 MBSFN RSRQ ......................................................................................................................................... 487
9.8.3.1 Absolute MBSFN RSRQ measurement accuracy requirements ......................................................... 487
9.8.3.2 MBSFN RSRQ measurement report mapping .................................................................................... 488
9.8.4 MCH BLER .............................................................................................................................................. 488
9.8.4.1 Measurement report mapping for MCH BLER ................................................................................... 488
9.8.4.2 Measurement report mapping for MCH Block Number ..................................................................... 489
9.9 ProSe Measurements ...................................................................................................................................... 490
9.9.1 Introduction............................................................................................................................................... 490
9.9.2 Intra-Frequency S-RSRP Measurement Accuracy Requirements............................................................. 490
9.9.2.1 Absolute S-RSRP Accuracy ................................................................................................................ 490
9.9.2.2 Relative Accuracy of S-RSRP............................................................................................................. 491
9.9.3 Intra-Frequency SD-RSRP Measurement Accuracy Requirements .......................................................... 492
9.9.3.1 Absolute SD-RSRP Accuracy ............................................................................................................. 492
9.9.3.2 Relative Accuracy of SD-RSRP .......................................................................................................... 492
9.10 V2X Measurements ........................................................................................................................................ 493
9.10.1 Introduction............................................................................................................................................... 493
9.10.2 Intra-Frequency S-RSRP Measurement Accuracy Requirements............................................................. 494
9.10.2.1 Absolute S-RSRP Accuracy ................................................................................................................ 494
9.10.2.2 Relative Accuracy of S-RSRP............................................................................................................. 494
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 17 ETSI TS 136 133 V14.3.0 (2017-04)
9.10.3 PSSCH-RSRP Measurement Accuracy Requirements ............................................................................. 495
9.10.3.1 Intra-frequency Absolute PSSCH-RSRP Accuracy ............................................................................ 495
9.10.4 S-RSSI Measurement Accuracy Requirements ........................................................................................ 496
9.10.4.1 Intra-frequency absolute S-RSSI measurement accuracy requirements .............................................. 496
9.10.4.2 Intra-frequency relative S-RSSI measurement accuracy requirements ............................................................. 496
10 Measurements Performance Requirements for E-UTRAN ..................................................................497
10.1 Received Interference Power .......................................................................................................................... 497
10.1.1 Absolute accuracy requirement................................................................................................................. 497
10.1.2 Relative accuracy requirement .................................................................................................................. 497
10.1.3 Received Interference Power measurement report mapping..................................................................... 497
10.2 Angle of Arrival (AOA) ................................................................................................................................. 497
10.2.1 Range/mapping ......................................................................................................................................... 497
10.3 Timing Advance (TADV) ................................................................................................................................. 498
10.3.1 Report mapping ........................................................................................................................................ 498
11 ProSe Requirements in Any Cell Selection state .................................................................................498
11.1 Introduction .................................................................................................................................................... 498
11.2 UE Transmit Timing for ProSe in Any Cell Selection State .......................................................................... 499
11.2.1 Introduction............................................................................................................................................... 499
11.2.2 ProSe UE transmission timing .................................................................................................................. 499
11.3 Initiation/Cease of SLSS Transmissions ........................................................................................................ 499
11.3.1 Introduction............................................................................................................................................... 499
11.3.2 Requirements ............................................................................................................................................ 499
11.4 Measurements for ProSe in Any Cell Selection State .................................................................................... 499
11.4.1 Introduction............................................................................................................................................... 499
11.4.2 Requirements ............................................................................................................................................ 500
11.4.2.1 E-UTRA FDD ..................................................................................................................................... 500
11.4.2.2 E-UTRA TDD ..................................................................................................................................... 500
11.5 Selection / Reselection of ProSe Synchronization Reference ........................................................................ 501
11.5.1 Introduction............................................................................................................................................... 501
11.5.2 Selection/Reselection to intra-frequency SyncRef UE ............................................................................. 501
11.5.2.1 Introduction ......................................................................................................................................... 501
11.5.2.2 Requirements ...................................................................................................................................... 501
11.6 Void ................................................................................................................................................................ 501
11.7 Selection / Reselection of ProSe relay UE ..................................................................................................... 501
11.7.1 Introduction............................................................................................................................................... 501
11.7.2 Selection / Reselection of intra-frequency ProSe relay UE ...................................................................... 501
12 V2V Sidelink Communication Requirements for V2V Operation on Dedicated V2V Carrier ...........502
12.1 Introduction .................................................................................................................................................... 502
12.2 Transmit Timing ............................................................................................................................................. 502
12.2.1 GNSS as timing reference......................................................................................................................... 502
12.3 Interruption ..................................................................................................................................................... 503
12.4 Reliability of GNSS signal ............................................................................................................................. 503
13 V2X Requirements ...............................................................................................................................503
13.1 Introduction .................................................................................................................................................... 503
13.2 UE Transmit Timing ...................................................................................................................................... 503
13.2.1 Introduction............................................................................................................................................... 503
13.2.2 GNSS as timing reference......................................................................................................................... 504
13.2.3 eNB as timing reference ........................................................................................................................... 504
13.2.4 SyncRef UE as timing reference ............................................................................................................... 504
13.3 Initiation/Cease of SLSS Transmissions ........................................................................................................ 504
13.3.1 Introduction............................................................................................................................................... 504
13.3.1.1 Initiation/Cease of SLSS transmissions with eNB as timing reference ............................................... 504
13.3.1.2 Initiation/Cease of SLSS transmissions with GNSS as timing reference ............................................ 505
13.3.1.3 Initiation/Cease of SLSS transmissions with SyncRef UE as timing reference .................................. 505
13.4 Selection / Reselection of V2X Synchronization Reference .......................................................................... 505
13.5 Autonomous Resource Selection/Reselection measurements ........................................................................ 506
13.5.1 Introduction............................................................................................................................................... 506
13.5.2 PSSCH-RSRP measurements ................................................................................................................... 506
13.5.3 S-RSSI measurements............................................................................................................................... 506
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 18 ETSI TS 136 133 V14.3.0 (2017-04)
13.6 Congestion Control measurements ................................................................................................................. 507
13.7 Interruption ..................................................................................................................................................... 507
13.7.1 Interruptions to WAN due to V2X Sidelink Communication ................................................................... 507
13.7.2 V2X Sidelink Communication Dropping due to synchronization source change ..................................... 507
Annex A (normative): Test Cases .....................................................................................................508
A.1 Purpose of annex ..................................................................................................................................508
A.2 Requirement classification for statistical testing ..................................................................................508
A.2.1 Types of requirements in TS 36.133 .............................................................................................................. 508
A.2.1.1 Time and delay requirements on UE higher layer actions ........................................................................ 508
A.2.1.2 Measurements of power levels, relative powers and time ........................................................................ 509
A.2.1.3 Implementation requirements ................................................................................................................... 509
A.2.1.4 Physical layer timing requirements ........................................................................................................... 509
A.3 RRM test configurations ......................................................................................................................510
A.3.1 Reference Measurement Channels ................................................................................................................. 510
A.3.1.1 PDSCH ..................................................................................................................................................... 510
A.3.1.1.1 FDD..................................................................................................................................................... 510
A.3.1.1.2 TDD .................................................................................................................................................... 511
A.3.1.1.3 FDD for UE category 0 ....................................................................................................................... 513
A.3.1.1.4 HD-FDD for UE category 0 ................................................................................................................ 514
A.3.1.1.5 TDD for UE category 0 ....................................................................................................................... 515
A.3.1.1.6 Frame Structure 3 ................................................................................................................................ 516
A.3.1.2 PCFICH/PDCCH/PHICH ......................................................................................................................... 517
A.3.1.2.1 FDD..................................................................................................................................................... 517
A.3.1.2.2 TDD .................................................................................................................................................... 517
A.3.1.2.3 HD-FDD for UE category 0 ................................................................................................................ 518
A.3.1.2.4 FS 3 ..................................................................................................................................................... 518
A.3.1.3 MPDCCH Reference Channels for Cat-M1 UEs ...................................................................................... 519
A.3.1.3.1 FDD in CEModeA .............................................................................................................................. 519
A.3.1.3.2 HD-FDD in CEModeA ....................................................................................................................... 519
A.3.1.3.3 TDD in CEModeA .............................................................................................................................. 520
A.3.1.3.4 FDD in CEModeB .............................................................................................................................. 520
A.3.1.3.5 HD-FDD in CEModeB ....................................................................................................................... 521
A.3.1.3.6 TDD in CEModeB .............................................................................................................................. 521
A.3.1.4 PDSCH Reference Channel for Cat-M1 UEs ........................................................................................... 522
A.3.1.4.1 FDD in CEModeA .............................................................................................................................. 522
A.3.1.4.2 HD-FDD in CEModeA ....................................................................................................................... 523
A.3.1.4.3 TDD in CEModeA .............................................................................................................................. 524
A.3.1.4.4 FDD in CEModeB .............................................................................................................................. 525
A.3.1.4.5 HD-FDD in CEModeB ...................................................................................................................... 526
A.3.1.4.6 TDD in CEModeB .............................................................................................................................. 527
A.3.1.5 NPDSCH Reference Channel for UE category NB1 ................................................................................ 528
A.3.1.5.1 HD-FDD in-band operation ................................................................................................................ 528
A.3.1.5.2 Void..................................................................................................................................................... 529
A.3.1.5.3 HD-FDD standalone operation............................................................................................................ 529
A.3.1.5.4 Void..................................................................................................................................................... 530
A.3.1.5.5 HD-FDD guard band operation ........................................................................................................... 530
A.3.1.5.6 Void..................................................................................................................................................... 530
A.3.1.6 NPDCCH Reference Channel for UE category NB1 ................................................................................ 530
A.3.1.6.1 HD-FDD in-band operation ................................................................................................................ 530
A.3.1.6.2 Void..................................................................................................................................................... 531
A.3.1.6.3 HD-FDD standalone operation............................................................................................................ 531
A.3.1.6.4 Void..................................................................................................................................................... 531
A.3.1.6.5 HD-FDD guard band operation ........................................................................................................... 531
A.3.1.6.6 Void..................................................................................................................................................... 531
A.3.2 OFDMA Channel Noise Generator (OCNG) ................................................................................................. 531
A.3.2.1 OCNG Patterns for FDD........................................................................................................................... 531
A.3.2.1.1 OCNG FDD pattern 1: outer resource blocks allocation in 10 MHz .................................................. 532
A.3.2.1.2 OCNG FDD pattern 2: full bandwidth allocation in 10 MHz ............................................................. 533
A.3.2.1.3 OCNG FDD pattern 3: outer resource blocks allocation in 1.4 MHz ................................................. 534
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 19 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.4 OCNG FDD pattern 4: full bandwidth allocation in 1.4 MHz ............................................................ 534
A.3.2.1.5 OCNG FDD pattern 5: outer resource blocks allocation in 10 MHz (without MBSFN) .................... 535
A.3.2.1.6 OCNG FDD pattern 6: full bandwidth allocation in 10 MHz (without MBSFN) ............................... 536
A.3.2.1.7 OCNG FDD pattern 7: full bandwidth allocation in 1.4 MHz (without MBSFN) .............................. 536
A.3.2.1.8 OCNG FDD pattern 8: outer resource blocks allocation in 10 MHz for MBSFN ABS ...................... 536
A.3.2.1.9 OCNG FDD pattern 9: full bandwidth allocation in 10 MHz for MBSFN ABS ................................ 537
A.3.2.1.10 OCNG FDD pattern 10: outer resource blocks allocation in 10 MHz with user data in every
subframe (without MBSFN)................................................................................................................ 538
A.3.2.1.11 OCNG FDD pattern 11: outer resource blocks allocation in 20 MHz ................................................ 538
A.3.2.1.12 OCNG FDD pattern 12: full bandwidth allocation in 20 MHz ........................................................... 539
A.3.2.1.13 OCNG FDD pattern 13: outer resource blocks allocation in 20 MHz (without MBSFN) .................. 540
A.3.2.1.14 OCNG FDD pattern 14: full bandwidth allocation in 20 MHz (without MBSFN) ............................. 540
A.3.2.1.15 OCNG FDD pattern 15: outer resource blocks allocation in 5 MHz .................................................. 541
A.3.2.1.16 OCNG FDD pattern 16: full bandwidth allocation in 5 MHz ............................................................. 542
A.3.2.1.17 OCNG FDD pattern 17: outer resource blocks allocation in 20 MHz with user data in every
subframe (without MBSFN)................................................................................................................ 542
A.3.2.1.18 OCNG FDD pattern 18: outer resource blocks allocation in 5 MHz (without MBSFN) .................... 543
A.3.2.1.19 OCNG FDD pattern 19: full bandwidth allocation in 5 MHz (without MBSFN) ............................... 543
A.3.2.1.20 OCNG FDD pattern 20: outer resource blocks allocation in 5 MHz with user data in every
subframe (without MBSFN)................................................................................................................ 544
A.3.2.1.21 OCNG FDD pattern 21: Generic resource blocks allocation (without MBSFN) ................................ 544
A.3.2.1.22 OCNG FDD pattern 22: Generic resource blocks allocation in 5MHz (without MBSFN) ................. 545
A.3.2.2 OCNG Patterns for TDD .......................................................................................................................... 545
A.3.2.2.1 OCNG TDD pattern 1: outer resource blocks allocation in 10 MHz .................................................. 546
A.3.2.2.2 OCNG TDD pattern 2: full bandwidth allocation in 10 MHz ............................................................. 546
A.3.2.2.3 OCNG TDD pattern 3: outer resource blocks allocation in 1.4 MHz ................................................. 547
A.3.2.2.4 OCNG TDD pattern 4: full bandwidth allocation in 1.4 MHz ............................................................ 547
A.3.2.2.5 OCNG TDD pattern 5: outer resource blocks allocation in 10 MHz for MBSFN ABS ..................... 548
A.3.2.2.6 OCNG TDD pattern 6: full bandwidth allocation in 10 MHz for MBSFN ABS ................................ 549
A.3.2.2.7 OCNG TDD pattern 7: outer resource blocks allocation in 20 MHz .................................................. 550
A.3.2.2.8 OCNG TDD pattern 8: full bandwidth allocation in 20 MHz ............................................................. 551
A.3.2.2.9 OCNG TDD pattern 9: outer resource blocks allocation in 5 MHz .................................................... 551
A.3.2.2.10 OCNG TDD pattern 10: full bandwidth allocation in 5 MHz ............................................................. 552
A.3.2.2.11 OCNG TDD pattern 11: Generic resource blocks allocation (without MBSFN) ................................ 553
A.3.2.3 OCNG Patterns for Narrowband IoT ........................................................................................................ 553
A.3.2.3.1 Narrowband IoT OCNG FDD pattern 1: In-band NB-IoT in 10 MHz EUTRAN cell ........................ 555
A.3.2.3.2 Narrowband IoT OCNG FDD pattern 2: guard band NB-IoT in 10 MHz EUTRAN cell .................. 555
A.3.2.3.3 Narrowband IoT OCNG FDD pattern 3: standalone NB-IoT ............................................................. 556
A.3.3 Reference DRX Configurations ..................................................................................................................... 557
A.3.4 ABS Transmission Configurations ................................................................................................................. 557
A.3.4.1 Non-MBSFN ABS Transmission Configurations ..................................................................................... 557
A.3.4.1.1 Non-MBSFN ABS Transmission, 1x2 antenna with PBCH ............................................................... 557
A.3.4.1.2 Non-MBSFN ABS Transmission, 2x2 antenna without PBCH .......................................................... 558
A.3.4.2 MBSFN ABS Transmission Configurations ............................................................................................. 559
A.3.4.2.1 MBSFN ABS Transmission, 1x2 antenna ........................................................................................... 559
A.3.4.2.2 MBSFN ABS Transmission, 2x2 antenna ........................................................................................... 559
A.3.5 Impact of Reference Sensitivity Degradation with Carrier Aggregation on Test Cases ................................. 560
A.3.5.1 Impact of Reference Sensitivity Degradation due to Insertion Loss ......................................................... 560
A.3.6 Carrier Aggregation Test Cases with Different Channel Bandwidth Combinations ...................................... 560
A.3.6.1 Introduction............................................................................................................................................... 560
A.3.7 Test Cases with Different Channel Bandwidths ............................................................................................. 560
A.3.7.1 Introduction............................................................................................................................................... 560
A.3.7.2 Principle of testing .................................................................................................................................... 560
A.3.8 Antenna Configuration ................................................................................................................................... 561
A.3.8.1 Antenna connection for 4 Rx capable UEs ............................................................................................... 561
A.3.8.1.1 Introduction ..................................................................................................................................................... 561
A.3.8.1.2 Principle of testing ........................................................................................................................................... 561
A.3.8.1.2.1 Single carrier tests ........................................................................................................................................ 561
A.3.8.1.2.2 Carrier aggregation and Dual connectivity tests ............................................................................ 562
A.3.8.1.2.3 Antenna connection for bands where 2RX is supported ................................................................ 563
A.3.8.1.2.4 Antenna connection for bands where 4RX is supported ................................................................ 563
A.3.9 Carrier Aggregation Test Cases with Different Duplex Modes...................................................................... 563
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 20 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.9.1 Introduction............................................................................................................................................... 563
A.3.9.2 Principle of testing .................................................................................................................................... 563
A.3.10 Carrier Aggregation Test Cases with Different CA Configurations ............................................................... 563
A.3.10.1 Introduction............................................................................................................................................... 563
A.3.10.2 Principle of testing .................................................................................................................................... 564
A.3.11 Test Cases for Synchronous and Asynchronous Dual Connectivity .............................................................. 564
A.3.11.1 Introduction............................................................................................................................................... 564
A.3.11.2 Principle of Testing................................................................................................................................... 564
A.3.12 Proximity-based Services ............................................................................................................................... 564
A.3.12.1 Introduction............................................................................................................................................... 564
A.3.12.2 Reference DRX configurations for ProSe tests ......................................................................................... 564
A.3.12.3 Test Cases with Different Channel Bandwidths ....................................................................................... 564
A.3.12.3.1 Introduction ......................................................................................................................................... 564
A.3.12.3.2 Principle of testing .............................................................................................................................. 565
A.3.12.4 Reference resource pool configurations for ProSe Direct Discovery ....................................................... 565
A.3.12.5 Reference resource pool configurations for ProSe Direct Communication .............................................. 571
A.3.12.6 Reference Measurement Channels for ProSe Direct Discovery ............................................................... 573
A.3.12.6.1 FDD..................................................................................................................................................... 573
A.3.12.7 Reference measurement channels for ProSe Direct Communication ....................................................... 573
A.3.12.7.1 FDD..................................................................................................................................................... 573
A.3.12.8 ProSe Receive Traffic Generator .............................................................................................................. 574
A.3.12.8.1 ProSe Direct Communication Receive Traffic Generator for FDD .................................................... 574
A.3.12.8.2 ProSe Direct Discovery Receive Traffic Generator for FDD .............................................................. 574
A.3.13 Time Offset between Cells ............................................................................................................................. 575
A.3.13.1 Introduction............................................................................................................................................... 575
A.3.13.2 Definition .................................................................................................................................................. 575
A.3.14 Carrier Aggregation under operation with Frame Structure 3 Test Cases with Different Duplex Modes ...... 575
A.3.14.1 Introduction............................................................................................................................................... 575
A.3.14.2 Principle of testing .................................................................................................................................... 575
A.3.15 Dual connectivity test cases with different combination of duplex mode ...................................................... 575
A.3.15.1 Introduction............................................................................................................................................... 575
A.3.15.2 Principle of testing .................................................................................................................................... 575
A.3.16 Reference PRACH Configurations ................................................................................................................. 576
A.3.17 Listen before talk model ................................................................................................................................. 576
A.3.17.1 Introduction............................................................................................................................................... 576
A.3.17.2 Definition .................................................................................................................................................. 577
A.3.18 Reference NPRACH Configurations .............................................................................................................. 577
A.3.19 Dual connectivity test cases with different bandwidth combinations ............................................................. 578
A.3.19.1 Introduction............................................................................................................................................... 578
A.3.19.2 Principle of testing .................................................................................................................................... 578
A.3.20 Category M1 UE Test Cases .......................................................................................................................... 578
A.3.20.1 Introduction............................................................................................................................................... 578
A.3.20.2 Principle of Cat-M1 UE Testing ............................................................................................................... 579
A.3.21 V2V Sidelink Communication on Dedicated V2V Carrier ............................................................................ 579
A.3.21.1 Introduction............................................................................................................................................... 579
A.3.21.2 Reference resource pool configurations for V2V Sidelink Communication............................................. 580
A.3.21.3 Reference measurement channels for V2V Sidelink Communication ...................................................... 581
A.4 E-UTRAN RRC_IDLE state ................................................................................................................582
A.4.2 Cell Re-Selection............................................................................................................................................ 582
A.4.2.1 E-UTRAN FDD – FDD Intra frequency case ........................................................................................... 582
A.4.2.1.1 Test Purpose and Environment ........................................................................................................... 582
A.4.2.1.2 Test Requirements ............................................................................................................................... 583
A.4.2.2 E-UTRAN TDD – TDD Intra frequency case .......................................................................................... 584
A.4.2.2.1 Test Purpose and Environment ........................................................................................................... 584
A.4.2.2.2 Test Requirements ............................................................................................................................... 585
A.4.2.3 E-UTRAN FDD – FDD Inter frequency case ........................................................................................... 586
A.4.2.3.1 Test Purpose and Environment ........................................................................................................... 586
A.4.2.3.2 Test Requirements ............................................................................................................................... 587
A.4.2.4 E-UTRAN FDD – TDD Inter frequency case........................................................................................... 588
A.4.2.4.1 Test Purpose and Environment ........................................................................................................... 588
A.4.2.4.2 Test Requirements ............................................................................................................................... 589
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 21 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.2.5 E-UTRAN TDD – FDD Inter frequency case........................................................................................... 590
A.4.2.5.1 Test Purpose and Environment ........................................................................................................... 590
A.4.2.5.2 Test Requirements ............................................................................................................................... 591
A.4.2.6 E-UTRAN TDD – TDD: Inter frequency case ......................................................................................... 592
A.4.2.6.1 Test Purpose and Environment ........................................................................................................... 592
A.4.2.6.2 Test Requirements ............................................................................................................................... 593
A.4.2.7 E-UTRAN FDD – FDD Inter frequency case in the existence of non-allowed CSG cell ........................ 594
A.4.2.7.1 Test Purpose and Environment ........................................................................................................... 594
A.4.2.7.2 Test Requirements ............................................................................................................................... 595
A.4.2.8 E-UTRAN TDD – TDD Inter frequency case in the existence of non-allowed CSG cell ........................ 596
A.4.2.8.1 Test Purpose and Environment ........................................................................................................... 596
A.4.2.8.2 Test Requirements ............................................................................................................................... 597
A.4.2.9 E-UTRAN FDD – FDD Intra frequency case for 5MHz bandwidth ........................................................ 598
A.4.2.9.1 Test Purpose and Environment ........................................................................................................... 598
A.4.2.9.2 Test Requirements ............................................................................................................................... 598
A.4.2.10 E-UTRAN FDD – FDD reselection using an increased number of carriers ............................................. 598
A.4.2.10.1 Test Purpose and Environment ........................................................................................................... 598
A.4.2.10.2 Test Requirements ............................................................................................................................... 601
A.4.2.11 E-UTRAN TDD – TDD reselection using an increased number of carriers............................................. 601
A.4.2.11.1 Test Purpose and Environment ........................................................................................................... 601
A.4.2.11.2 Test Requirements ............................................................................................................................... 604
A.4.2.12 E-UTRAN FDD – FDD Intra frequency case for Cat-M1 UE in normal coverage .................................. 604
A.4.2.12.1 Test Purpose and Environment ........................................................................................................... 604
A.4.2.12.2 Test Requirements ............................................................................................................................... 606
A.4.2.13 E-UTRAN HD – FDD Intra frequency case for Cat-M1 UE in normal coverage .................................... 607
A.4.2.13.1 Test Purpose and Environment ........................................................................................................... 607
A.4.2.13.2 Test Requirements ............................................................................................................................... 608
A.4.2.14 E-UTRAN TDD – TDD Intra frequency case for Cat-M1 UE in normal coverage ................................. 609
A.4.2.14.1 Test Purpose and Environment ........................................................................................................... 609
A.4.2.14.2 Test Requirements ............................................................................................................................... 610
A.4.2.15 E-UTRAN FDD – FDD Intra frequency case for Cat-M1 UE in enhanced coverage ...................................... 611
A.4.2.15.1 Test Purpose and Environment ........................................................................................................... 611
A.4.2.15.2 Test Requirements ............................................................................................................................... 612
A.4.2.16 E-UTRAN HD – FDD Intra frequency case for Cat-M1 UE in enhanced coverage ........................................ 613
A.4.2.16.1 Test Purpose and Environment ........................................................................................................... 613
A.4.2.16.2 Test Requirements ............................................................................................................................... 614
A.4.2.17 E-UTRAN TDD – TDD Intra frequency case for Cat-M1 UE in enhanced coverage ..................................... 615
A.4.2.17.1 Test Purpose and Environment ........................................................................................................... 615
A.4.2.17.2 Test Requirements ............................................................................................................................... 616
A.4.2.18 HD – FDD Intra frequency case for UE Category NB1 In-Band mode in normal coverage ............................ 617
A.4.2.18.1 Test Purpose and Environment ........................................................................................................... 617
A.4.2.18.2 Test Requirements ............................................................................................................................... 619
A.4.2.19 HD – FDD Intra frequency case for UE Category NB1 In-Band mode in enhanced coverage ................ 620
A.4.2.19.1 Test Purpose and Environment ........................................................................................................... 620
A.4.2.19.2 Test Requirements ............................................................................................................................... 622
A.4.3 E-UTRAN to UTRAN Cell Re-Selection ...................................................................................................... 623
A.4.3.1 E-UTRAN FDD – UTRAN FDD: ............................................................................................................ 623
A.4.3.1.1 EUTRA FDD-UTRA FDD cell reselection: UTRA FDD is of higher priority................................... 623
A.4.3.1.1.1 Test Purpose and Environment ...................................................................................................... 623
A.4.3.1.1.2 Test Requirements ......................................................................................................................... 625
A.4.3.1.2 EUTRA FDD-UTRA FDD cell reselection: UTRA FDD is of lower priority.................................... 625
A.4.3.1.2.1 Test Purpose and Environment ...................................................................................................... 625
A.4.3.1.2.2 Test Requirements ......................................................................................................................... 628
A.4.3.1.3 EUTRA FDD-UTRA FDD cell reselection in fading propagation conditions: UTRA FDD is of
lower priority....................................................................................................................................... 628
A.4.3.1.3.1 Test Purpose and Environment ...................................................................................................... 628
A.4.3.1.3.2 Test Requirements ......................................................................................................................... 631
A.4.3.1.4 EUTRA FDD-UTRA FDD cell reselection: UTRA FDD is of lower priority for 5MHz
bandwidth ............................................................................................................................................ 631
A.4.3.1.4.1 Test Purpose and Environment ...................................................................................................... 631
A.4.3.1.4.2 Test Requirements ......................................................................................................................... 632
A.4.3.1.5 Idle mode FDD to UTRA FDD interRAT reselection ........................................................................ 632
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 22 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.1.5.1 Test Purpose and Environment ...................................................................................................... 632
A.4.3.1.5.2 Test Requirements ......................................................................................................................... 635
A.4.3.2 E-UTRAN FDD – UTRAN TDD: ............................................................................................................ 636
A.4.3.2.1 Test Purpose and Environment ........................................................................................................... 636
A.4.3.2.1.1 Void ............................................................................................................................................... 636
A.4.3.2.1.2 1.28Mcps TDD option ................................................................................................................... 636
A.4.3.2.1.3 Void ............................................................................................................................................... 638
A.4.3.2.2 Test Requirements ............................................................................................................................... 638
A.4.3.2.2.1 1.28Mcps TDD option ................................................................................................................... 638
A.4.3.2A E-UTRA FDD to UTRA TDD cell re-selection for IncMon .................................................................... 638
A.4.3.2A.1 Test Purpose and Environment ........................................................................................................... 638
A.4.3.2A.2 Test Requirements ............................................................................................................................... 642
A.4.3.3 E-UTRAN TDD – UTRAN FDD: ...................................................................................................... 642
A.4.3.3.1 Test Purpose and Environment ........................................................................................................... 642
A.4.3.3.2 Test Requirements ............................................................................................................................... 645
A.4.3.3A Idle mode TDD to UTRA FDD interRAT reselection .............................................................................. 645
A.4.3.3A.1 Test Purpose and Environment ........................................................................................................... 645
A.4.3.3A.2 Test Requirements ............................................................................................................................... 649
A.4.3.4 E-UTRAN TDD – UTRAN TDD: ............................................................................................................ 650
A.4.3.4.1 E-UTRA to UTRA TDD cell re-selection: UTRA is of higher priority .............................................. 650
A.4.3.4.1.1 Test Purpose and Environment ...................................................................................................... 650
A.4.3.4.1.2 Test Requirements ......................................................................................................................... 652
A.4.3.4.2 E-UTRA to UTRA TDD cell re-selection: UTRA is of lower priority ............................................... 652
A.4.3.4.2.1 Test Purpose and Environment ...................................................................................................... 652
A.4.3.4.2.2 Test Requirements ......................................................................................................................... 654
A.4.3.4.3 EUTRA TDD-UTRA TDD cell reselection in fading propagation conditions: UTRA TDD is of
lower priority....................................................................................................................................... 655
A.4.3.4.3.1 Test Purpose and Environment ...................................................................................................... 655
A.4.3.4.3.2 Test Requirements ......................................................................................................................... 657
A.4.3.4.4 E-UTRA TDD to UTRA TDD cell re-selection for IncMon .............................................................. 657
A.4.3.4.4.1 Test Purpose and Environment ...................................................................................................... 657
A.4.3.4.4.2 Test Requirements ......................................................................................................................... 661
A.4.4 E-UTRAN to GSM Cell Re-Selection............................................................................................................ 661
A.4.4.1 E-UTRAN FDD – GSM: .......................................................................................................................... 661
A.4.4.1.1 Test Purpose and Environment ........................................................................................................... 661
A.4.4.1.2 Test Requirements ............................................................................................................................... 663
A.4.4.2 E-UTRAN TDD – GSM: .................................................................................................................... 663
A.4.4.2.1 Test Purpose and Environment ........................................................................................................... 663
A.4.4.2.2 Test Requirements ............................................................................................................................... 665
A.4.5 E-UTRAN to HRPD Cell Re-Selection.......................................................................................................... 666
A.4.5.1 E-UTRAN FDD – HRPD ......................................................................................................................... 666
A.4.5.1.1 E-UTRAN FDD – HRPD Cell Reselection: HRPD is of Lower Priority ........................................... 666
A.4.5.1.1.1 Test Purpose and Environment ...................................................................................................... 666
A.4.5.1.1.2 Test Requirements ............................................................................................................................... 668
A.4.5.2 E-UTRAN TDD – HRPD ......................................................................................................................... 668
A.4.5.2.1 E-UTRAN TDD – HRPD Cell Reselection: HRPD is of Lower Priority ........................................... 668
A.4.5.2.1.1 Test Purpose and Environment ...................................................................................................... 668
A.4.5.2.1.2 Test Requirements ......................................................................................................................... 671
A.4.6 E-UTRAN to cdma2000 1X Cell Re-Selection ........................................................................................ 671
A.4.6.1 E-UTRAN FDD – cdma2000 1X ........................................................................................................ 671
A.4.6.1.1 E-UTRAN FDD – cdma2000 1X Cell Reselection: cdma2000 1X is of Lower Priority .................... 671
A.4.6.1.1.1 Test Purpose and Environment ........................................................................................................... 671
A.4.6.1.1.2 Test Requirements ............................................................................................................................... 674
A.4.6.2 E-UTRAN TDD – cdma2000 1X ............................................................................................................. 674
A.4.6.2.1 E-UTRAN TDD –cdma2000 1X Cell Reselection: cdma2000 1X is of Lower Priority..................... 674
A.4.6.2.1.1 Test Purpose and Environment ...................................................................................................... 674
A.4.6.2.1.2 Test Requirements ......................................................................................................................... 677
A.5 E-UTRAN RRC CONNECTED Mode Mobility .................................................................................677
A.5.1 E-UTRAN Handover ...................................................................................................................................... 677
A.5.1.1 E-UTRAN FDD - FDD Intra frequency handover ................................................................................... 677
A.5.1.1.1 Test Purpose and Environment ........................................................................................................... 677
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 23 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.1.1.2 Test Requirements .................................................................................................................................... 679
A.5.1.2 E-UTRAN TDD - TDD Intra frequency handover ................................................................................... 679
A.5.1.2.1 Test Purpose and Environment ........................................................................................................... 679
A.5.1.2.2 Test Requirements ............................................................................................................................... 681
A.5.1.3 E-UTRAN FDD – FDD Inter frequency handover ................................................................................... 681
A.5.1.3.1 Test Purpose and Environment ........................................................................................................... 681
A.5.1.3.2 Test Requirements ............................................................................................................................... 683
A.5.1.4 E-UTRAN TDD – TDD Inter frequency handover .................................................................................. 683
A.5.1.4.1 Test Purpose and Environment ........................................................................................................... 683
A.5.1.4.2 Test Requirements ............................................................................................................................... 685
A.5.1.5 E-UTRAN FDD – FDD Inter frequency handover: unknown target cell ................................................. 685
A.5.1.5.1 Test Purpose and Environment ........................................................................................................... 685
A.5.1.5.2 Test Requirements ............................................................................................................................... 687
A.5.1.6 E-UTRAN TDD – TDD Inter frequency handover; unknown Target Cell............................................... 687
A.5.1.6.1 Test Purpose and Environment ........................................................................................................... 687
A.5.1.6.2 Test Requirements ............................................................................................................................... 689
A.5.1.7 E-UTRAN FDD – TDD Inter frequency handover................................................................................... 689
A.5.1.7.1 Test Purpose and Environment ........................................................................................................... 689
A.5.1.7.2 Test Requirements ............................................................................................................................... 692
A.5.1.8 E-UTRAN TDD – FDD Inter frequency handover................................................................................... 692
A.5.1.8.1 Test Purpose and Environment ........................................................................................................... 692
A.5.1.8.2 Test Requirements ............................................................................................................................... 695
A.5.1.9 E-UTRAN FDD - FDD Intra frequency handover for 5MHz bandwidth ................................................. 695
A.5.1.9.1 Test Purpose and Environment ........................................................................................................... 695
A.5.1.9.2 Test Requirements ............................................................................................................................... 696
A.5.1.10 E-UTRAN FDD - FDD Intra frequency handover for UE category 0 ...................................................... 696
A.5.1.10.1 Test Purpose and Environment ........................................................................................................... 696
A.5.1.10.2 Test Requirements ............................................................................................................................... 698
A.5.1.11 E-UTRAN HD - FDD Intra frequency handover for UE category 0 ........................................................ 698
A.5.1.11.1 Test Purpose and Environment ........................................................................................................... 698
A.5.1.11.2 Test Requirements ............................................................................................................................... 700
A.5.1.12 E-UTRAN TDD - TDD Intra frequency handover for UE category 0 ..................................................... 700
A.5.1.12.1 Test Purpose and Environment ........................................................................................................... 700
A.5.1.12.2 Test Requirements ............................................................................................................................... 702
A.5.1.13 E-UTRAN FDD-FDD Intra frequency handover for Cat-M1 UEs in CEModeA .................................... 702
A.5.1.13.1 Test Purpose and Environment ........................................................................................................... 702
A.5.1.13.2 Test Requirements ............................................................................................................................... 704
A.5.1.14 E-UTRAN HD-FDD Intra frequency handover for Cat-M1 UEs in CEModeA....................................... 705
A.5.1.14.1 Test Purpose and Environment ........................................................................................................... 705
A.5.1.14.2 Test Requirements ............................................................................................................................... 706
A.5.1.15 E-UTRAN TDD Intra frequency handover for Cat-M1 UEs in CEModeA ............................................. 707
A.5.1.15.1 Test Purpose and Environment ........................................................................................................... 707
A.5.1.15.2 Test Requirements ............................................................................................................................... 708
A.5.1.16 E-UTRAN FDD-FDD Intra frequency handover for Cat-M1 UEs in CEModeB..................................... 709
A.5.1.16.1 Test Purpose and Environment ........................................................................................................... 709
A.5.1.16.2 Test Requirements ............................................................................................................................... 710
A.5.1.17 E-UTRAN HD-FDD Intra frequency handover for Cat-M1 UEs in CEModeB ....................................... 711
A.5.1.17.1 Test Purpose and Environment ........................................................................................................... 711
A.5.1.17.2 Test Requirements ............................................................................................................................... 712
A.5.1.18 E-UTRAN TDD Intra frequency handover for Cat-M1 UEs in CEModeB .............................................. 713
A.5.1.18.1 Test Purpose and Environment ........................................................................................................... 713
A.5.1.18.2 Test Requirements ............................................................................................................................... 714
A.5.2 E-UTRAN Handover to other RATs .............................................................................................................. 715
A.5.2.1 E-UTRAN FDD – UTRAN FDD Handover............................................................................................. 715
A.5.2.1.1 Test Purpose and Environment ........................................................................................................... 715
A.5.2.1.2 Test Requirements ............................................................................................................................... 716
A.5.2.2 E-UTRAN TDD - UTRAN FDD Handover ............................................................................................. 717
A.5.2.2.1 Test Purpose and Environment ........................................................................................................... 717
A.5.2.2.2 Test Requirements ............................................................................................................................... 720
A.5.2.3 E-UTRAN FDD- GSM Handover ............................................................................................................ 720
A.5.2.3.1 Test Purpose and Environment ...................................................................................................... 720
A.5.2.3.2 Test Requirements ......................................................................................................................... 721
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 24 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.2.4 E-UTRAN TDD - UTRAN TDD Handover ............................................................................................. 722
A.5.2.4.1 Test Purpose and Environment ........................................................................................................... 722
A.5.2.4.1.1 Void ............................................................................................................................................... 722
A.5.2.4.1.2 1.28 Mcps TDD option .................................................................................................................. 722
A.5.2.4.1.3 Void ............................................................................................................................................... 725
A.5.2.4.2 Test Requirements ............................................................................................................................... 725
A.5.2.4.2.1 Void ............................................................................................................................................... 725
A.5.2.4.2.2 1.28 Mcps TDD option .................................................................................................................. 725
A.5.2.4.2.3 Void ............................................................................................................................................... 725
A.5.2.5 E-UTRAN FDD – UTRAN TDD Handover ............................................................................................ 725
A.5.2.5.1 Test Purpose and Environment ........................................................................................................... 725
A.5.2.5.1.3 Void ............................................................................................................................................... 728
A.5.2.5.2 Test Requirements ............................................................................................................................... 728
A.5.2.5.2.1 Void ............................................................................................................................................... 728
A.5.2.5.2.2 1.28 Mcps TDD option .................................................................................................................. 728
A.5.2.5.2.3 Void ............................................................................................................................................... 728
A.5.2.6 E-UTRAN TDD - GSM Handover ..................................................................................................... 728
A.5.2.6.1 Test Purpose and Environment ...................................................................................................... 728
A.5.2.6.2 Test Requirements ......................................................................................................................... 730
A.5.2.7 E-UTRAN FDD – UTRAN FDD Handover; Unknown Target Cell ........................................................ 731
A.5.2.7.1 Test Purpose and Environment ........................................................................................................... 731
A.5.2.7.2 Test Requirements ............................................................................................................................... 733
A.5.2.8 E-UTRAN FDD - GSM Handover; Unknown Target Cell....................................................................... 733
A.5.2.8.1 Test Purpose and Environment ........................................................................................................... 733
A.5.2.8.2 Test Requirements ............................................................................................................................... 734
A.5.2.9 E-UTRAN TDD - GSM Handover; Unknown Target Cell ...................................................................... 735
A.5.2.9.1 Test Purpose and Environment ........................................................................................................... 735
A.5.2.9.2 Test Requirements ............................................................................................................................... 736
A.5.2.10 E-UTRAN TDD to UTRAN TDD handover: unknown target cell .......................................................... 737
A.5.2.10.1 Test Purpose and Environment ........................................................................................................... 737
A.5.2.10.2 Test Requirements ............................................................................................................................... 739
A.5.2.10A E-UTRAN FDD – UTRAN FDD Multicarrier Handover with two target cells ....................................... 739
A.5.2.10A.1 Test Purpose and Environment ........................................................................................................... 739
A.5.2.10A.2 Test Requirements ............................................................................................................................... 742
A.5.2.10B E-UTRAN TDD – UTRAN FDD Multicarrier Handover with two target cells ....................................... 742
A.5.2.10B.1 Test Purpose and Environment ........................................................................................................... 742
A.5.2.10B.2 Test Requirements ............................................................................................................................... 745
A.5.2.11 E-UTRAN FDD – UTRAN FDD Handover for 5MHz Bandwidth ......................................................... 745
A.5.2.11.1 Test Purpose and Environment ........................................................................................................... 745
A.5.2.11.2 Test Requirements ............................................................................................................................... 746
A.5.3 E-UTRAN Handover to Non-3GPP RATs ......................................................................................... 746
A.5.3.1 E-UTRAN FDD – HRPD Handover ................................................................................................... 746
A.5.3.1.1 Test Purpose and Environment ........................................................................................................... 746
A.5.3.1.2 Test Requirements ............................................................................................................................... 749
A.5.3.2 E-UTRAN FDD – cdma2000 1X Handover ....................................................................................... 749
A.5.3.2.1 Test Purpose and Environment ........................................................................................................... 749
A.5.3.2.2 Test Requirements ............................................................................................................................... 752
A.5.3.3 E-UTRAN FDD – HRPD Handover; Unknown Target Cell .................................................................... 752
A.5.3.3.1 Test Purpose and Environment ........................................................................................................... 752
A.5.3.3.2 Test Requirements ............................................................................................................................... 754
A.5.3.4 E-UTRAN FDD – cdma2000 1X Handover; Unknown Target cell ......................................................... 755
A.5.3.4.1 Test Purpose and Environment ........................................................................................................... 755
A.5.3.4.2 Test Requirements ............................................................................................................................... 756
A.5.3.5 E-UTRAN TDD – HRPD Handover ........................................................................................................ 757
A.5.3.5.1 Test Purpose and Environment ........................................................................................................... 757
A.5.3.5.2 Test Requirements ............................................................................................................................... 759
A.5.3.6 E-UTRAN TDD – cdma2000 1X Handover............................................................................................. 760
A.5.3.6.1 Test Purpose and Environment ........................................................................................................... 760
A.5.3.6.2 Test Requirements ............................................................................................................................... 763
A.6 RRC Connection Control .....................................................................................................................763
A.6.1 RRC Re-establishment ................................................................................................................................... 763
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 25 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.1.1 E-UTRAN FDD Intra-frequency RRC Re-establishment ......................................................................... 763
A.6.1.1.1 Test Purpose and Environment ........................................................................................................... 763
A.6.1.1.2 Test Requirements ............................................................................................................................... 764
A.6.1.2 E-UTRAN FDD Inter-frequency RRC Re-establishment ......................................................................... 765
A.6.1.2.1 Test Purpose and Environment ........................................................................................................... 765
A.6.1.2.2 Test Requirements ............................................................................................................................... 766
A.6.1.3 E-UTRAN TDD Intra-frequency RRC Re-establishment ........................................................................ 767
A.6.1.3.1 Test Purpose and Environment ........................................................................................................... 767
A.6.1.3.2 Test Requirements ............................................................................................................................... 768
A.6.1.4 E-UTRAN TDD Inter-frequency RRC Re-establishment ........................................................................ 769
A.6.1.4.1 Test Purpose and Environment ........................................................................................................... 769
A.6.1.4.2 Test Requirements ............................................................................................................................... 770
A.6.1.5 E-UTRAN FDD Intra-frequency RRC Re-establishment for 5MHz bandwidth ...................................... 771
A.6.1.5.1 Test Purpose and Environment ........................................................................................................... 771
A.6.1.5.2 Test Requirements ............................................................................................................................... 771
A.6.1.6 E-UTRAN FD-FDD Intra-frequency RRC Re-establishment for UE category 0 ..................................... 771
A.6.1.6.1 Test Purpose and Environment ........................................................................................................... 771
A.6.1.6.2 Test Requirements ............................................................................................................................... 773
A.6.1.7 E-UTRAN HD-FDD Intra-frequency RRC Re-establishment for UE category 0 .................................... 774
A.6.1.7.1 Test Purpose and Environment ........................................................................................................... 774
A.6.1.7.2 Test Requirements ............................................................................................................................... 775
A.6.1.8 E-UTRAN TDD Intra-frequency RRC Re-establishment for UE category 0 ........................................... 776
A.6.1.8.1 Test Purpose and Environment ........................................................................................................... 776
A.6.1.8.2 Test Requirements ............................................................................................................................... 777
A.6.1.9 E-UTRAN FD-FDD Intra-frequency RRC Re-establishment for Cat-M1 UE in CEModeA ................... 778
A.6.1.9.1 Test Purpose and Environment ........................................................................................................... 778
A.6.1.9.2 Test Requirements ............................................................................................................................... 779
A.6.1.10 E-UTRAN HD-FDD Intra-frequency RRC Re-establishment for Cat-M1 UE in CEModeA .................. 780
A.6.1.10.1 Test Purpose and Environment ........................................................................................................... 780
A.6.1.10.2 Test Requirements ............................................................................................................................... 781
A.6.1.11 E-UTRAN TDD Intra-frequency RRC Re-establishment for Cat-M1 UE in CEModeA ......................... 782
A.6.1.11.1 Test Purpose and Environment ........................................................................................................... 782
A.6.1.11.2 Test Requirements ............................................................................................................................... 783
A.6.1.12 E-UTRAN FD-FDD Intra-frequency RRC Re-establishment for Cat-M1 UE in CEModeB ................... 784
A.6.1.12.1 Test Purpose and Environment ........................................................................................................... 784
A.6.1.12.2 Test Requirements ............................................................................................................................... 785
A.6.1.13 E-UTRAN HD-FDD Intra-frequency RRC Re-establishment for Cat-M1 UE in CEModeB .................. 786
A.6.1.13.1 Test Purpose and Environment ........................................................................................................... 786
A.6.1.13.2 Test Requirements ............................................................................................................................... 787
A.6.1.14 E-UTRAN TDD Intra-frequency RRC Re-establishment for Cat-M1 UE in CEModeB ......................... 788
A.6.1.14.1 Test Purpose and Environment ........................................................................................................... 788
A.6.1.14.2 Test Requirements ............................................................................................................................... 789
A.6.1.15 HD-FDD Intra-frequency RRC Re-establishment for UE category NB1 in In-Band mode under
enhanced coverage .................................................................................................................................... 790
A.6.1.15.1 Test Purpose and Environment ........................................................................................................... 790
A.6.1.15.2 Test Requirements ............................................................................................................................... 792
A.6.1.16 HD-FDD Inter-frequency RRC Re-establishment for UE category NB1 in In-Band mode under
normal coverage........................................................................................................................................ 793
A.6.1.16.1 Test Purpose and Environment ........................................................................................................... 793
A.6.1.16.2 Test Requirements ............................................................................................................................... 795
A.6.2 Random Access .............................................................................................................................................. 796
A.6.2.1 E-UTRAN FDD – Contention Based Random Access Test ..................................................................... 796
A.6.2.1.1 Test Purpose and Environment ........................................................................................................... 796
A.6.2.1.2 Test Requirements ............................................................................................................................... 797
A.6.2.1.2.1 Random Access Response Reception ............................................................................................ 797
A.6.2.1.2.2 No Random Access Response Reception ...................................................................................... 797
A.6.2.1.2.3 Receiving a NACK on msg3 ......................................................................................................... 797
A.6.2.1.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 798
A.6.2.1.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 798
A.6.2.1.2.6 Contention Resolution Timer expiry ............................................................................................. 798
A.6.2.2 E-UTRAN FDD – Non-Contention Based Random Access Test ............................................................. 798
A.6.2.2.1 Test Purpose and Environment ........................................................................................................... 798
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 26 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.2.2 Test Requirements ............................................................................................................................... 799
A.6.2.2.2.1 Random Access Response Reception ............................................................................................ 800
A.6.2.2.2.2 No Random Access Response Reception ...................................................................................... 800
A.6.2.3 E-UTRAN TDD – Contention Based Random Access Test ..................................................................... 800
A.6.2.3.1 Test Purpose and Environment ........................................................................................................... 800
A.6.2.3.2 Test Requirements ............................................................................................................................... 802
A.6.2.3.2.1 Random Access Response Reception ............................................................................................ 802
A.6.2.3.2.2 No Random Access Response reception ....................................................................................... 802
A.6.2.3.2.3 Receiving a NACK on msg3 ......................................................................................................... 802
A.6.2.3.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 803
A.6.2.3.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 803
A.6.2.3.2.6 Contention Resolution Timer expiry ............................................................................................. 803
A.6.2.4 E-UTRAN TDD – Non-Contention Based Random Access Test............................................................. 803
A.6.2.4.1 Test Purpose and Environment ........................................................................................................... 803
A.6.2.4.2 Test Requirements ............................................................................................................................... 805
A.6.2.4.2.1 Random Access Response Reception ............................................................................................ 805
A.6.2.4.2.2 No Random Access Response Reception ...................................................................................... 805
A.6.2.5 E-UTRAN FDD – Contention Based Random Access Test for 5MHz bandwidth .................................. 805
A.6.2.5.1 Test Purpose and Environment ........................................................................................................... 805
A.6.2.5.2 Test Requirements ............................................................................................................................... 806
A.6.2.6 E-UTRAN FDD – Non-contention Based Random Access Test for 5MHz bandwidth ........................... 806
A.6.2.6.1 Test Purpose and Environment ........................................................................................................... 806
A.6.2.6.2 Test Requirements ............................................................................................................................... 806
A.6.2.7 E-UTRAN FDD – Non-Contention Based Random Access Test For SCell............................................. 807
A.6.2.7.1 Test Purpose and Environment ........................................................................................................... 807
A.6.2.7.2 Test Requirements ............................................................................................................................... 809
A.6.2.7.2.1 Random Access Response Reception ............................................................................................ 809
A.6.2.7.2.2 No Random Access Response Reception ...................................................................................... 809
A.6.2.7.2.3 Stop Preamble transmission if maximum number of preamble transmission counter has been
reached........................................................................................................................................... 809
A.6.2.8 E-UTRAN TDD – Non-Contention Based Random Access Test For SCell ............................................ 810
A.6.2.8.1 Test Purpose and Environment ........................................................................................................... 810
A.6.2.8.2 Test Requirements ............................................................................................................................... 812
A.6.2.8.2.1 Random Access Response Reception ............................................................................................ 812
A.6.2.8.2.2 No Random Access Response Reception ...................................................................................... 812
A.6.2.8.2.3 Stop Preamble transmission if maximum number of preamble transmission counter has been
reached........................................................................................................................................... 812
A.6.2.9 3DL/3UL TDD CA Non-Contention Based Random Access Test for 2 SCells ....................................... 813
A.6.2.9.1 Test Purpose and Environment ........................................................................................................... 813
A.6.2.9.2 Test Requirements ............................................................................................................................... 815
A.6.2.9.2.1 Random Access Response Reception ............................................................................................ 815
A.6.2.9.2.2 No Random Access Response Reception ...................................................................................... 816
A.6.2.9.2.3 Stop Preamble transmission if maximum number of preamble transmission counter has been
reached........................................................................................................................................... 816
A.6.2.10 E-UTRAN FDD Contention Based Random Access Test for Cat-M1 UEs in Normal Coverage ............ 817
A.6.2.10.1 Test Purpose and Environment ........................................................................................................... 817
A.6.2.10.2 Test Requirements ............................................................................................................................... 819
A.6.2.10.2.1 Random Access Response Reception ............................................................................................ 819
A.6.2.10.2.2 No Random Access Response Reception ...................................................................................... 820
A.6.2.10.2.3 Receiving a NACK on msg3 ......................................................................................................... 820
A.6.2.10.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 820
A.6.2.10.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 820
A.6.2.10.2.6 Contention Resolution Timer expiry ............................................................................................. 820
A.6.2.10.2.7 PRACH Resource Selection .......................................................................................................... 821
A.6.2.11 E-UTRAN HD-FDD Contention Based Random Access Test for Cat-M1 UEs in Normal Coverage ..... 821
A.6.2.11.1 Test Purpose and Environment ........................................................................................................... 821
A.6.2.11.2 Test Requirements ............................................................................................................................... 823
A.6.2.11.2.1 Random Access Response Reception ............................................................................................ 823
A.6.2.11.2.2 No Random Access Response Reception ...................................................................................... 824
A.6.2.11.2.3 Receiving a NACK on msg3 ......................................................................................................... 824
A.6.2.11.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 824
A.6.2.11.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 824
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 27 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.11.2.6 Contention Resolution Timer expiry ............................................................................................. 824
A.6.2.11.2.7 PRACH Resource Selection .......................................................................................................... 825
A.6.2.12 E-UTRAN TDD Contention Based Random Access Test for Cat-M1 UEs in Normal Coverage............ 825
A.6.2.12.1 Test Purpose and Environment ........................................................................................................... 825
A.6.2.12.2 Test Requirements ............................................................................................................................... 827
A.6.2.12.2.1 Random Access Response Reception ............................................................................................ 827
A.6.2.12.2.2 No Random Access Response Reception ...................................................................................... 828
A.6.2.12.2.3 Receiving a NACK on msg3 ......................................................................................................... 828
A.6.2.12.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 828
A.6.2.12.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 828
A.6.2.12.2.6 Contention Resolution Timer expiry ............................................................................................. 828
A.6.2.12.2.7 PRACH Resource Selection .......................................................................................................... 829
A.6.2.13 E-UTRAN FDD Contention Based Random Access Test for Cat-M1 UEs in Enhanced Coverage ........ 829
A.6.2.13.1 Test Purpose and Environment ........................................................................................................... 829
A.6.2.13.2 Test Requirements ............................................................................................................................... 831
A.6.2.13.2.1 Random Access Response Reception ............................................................................................ 831
A.6.2.13.2.2 No Random Access Response Reception ...................................................................................... 832
A.6.2.13.2.3 Receiving a NACK on msg3 ......................................................................................................... 832
A.6.2.13.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 832
A.6.2.13.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 832
A.6.2.13.2.6 Contention Resolution Timer expiry ............................................................................................. 832
A.6.2.13.2.7 PRACH Resource Selection .......................................................................................................... 833
A.6.2.14 E-UTRAN HD-FDD Contention Based Random Access Test for Cat-M1 UEs in Enhanced
Coverage ................................................................................................................................................... 833
A.6.2.14.1 Test Purpose and Environment ........................................................................................................... 833
A.6.2.14.2 Test Requirements ............................................................................................................................... 835
A.6.2.14.2.1 Random Access Response Reception ............................................................................................ 835
A.6.2.14.2.2 No Random Access Response Reception ...................................................................................... 836
A.6.2.14.2.3 Receiving a NACK on msg3 ......................................................................................................... 836
A.6.2.14.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 836
A.6.2.14.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 836
A.6.2.14.2.6 Contention Resolution Timer expiry ............................................................................................. 836
A.6.2.14.2.7 PRACH Resource Selection .......................................................................................................... 837
A.6.2.15 E-UTRAN TDD Contention Based Random Access Test for Cat-M1 UEs in Enhanced Coverage ........ 837
A.6.2.15.1 Test Purpose and Environment ........................................................................................................... 837
A.6.2.15.2 Test Requirements ............................................................................................................................... 839
A.6.2.15.2.1 Random Access Response Reception ............................................................................................ 839
A.6.2.15.2.2 No Random Access Response Reception ...................................................................................... 840
A.6.2.15.2.3 Receiving a NACK on msg3 ......................................................................................................... 840
A.6.2.15.2.4 Reception of an Incorrect Message over Temporary C-RNTI....................................................... 840
A.6.2.15.2.5 Reception of a Correct Message over Temporary C-RNTI ........................................................... 840
A.6.2.15.2.6 Contention Resolution Timer expiry ............................................................................................. 840
A.6.2.15.2.7 PRACH Resource Selection .......................................................................................................... 841
A.6.3 RRC Connection Release with Redirection.................................................................................................... 841
A.6.3.1 Redirection from E-UTRAN FDD to UTRAN FDD ................................................................................ 841
A.6.3.1.1 Test Purpose and Environment ........................................................................................................... 841
A.6.3.1.2 Test Requirements ............................................................................................................................... 843
A.6.3.2 Redirection from E-UTRAN TDD to UTRAN FDD ................................................................................ 843
A.6.3.2.1 Test Purpose and Environment ........................................................................................................... 843
A.6.3.2.2 Test Requirements ............................................................................................................................... 846
A.6.3.3 Redirection from E-UTRAN FDD to GERAN when System Information is provided ............................ 846
A.6.3.3.1 Test Purpose and Environment ........................................................................................................... 846
A.6.3.3.2 Test Requirements ............................................................................................................................... 847
A.6.3.4 Redirection from E-UTRAN TDD to GERAN when System Information is provided ............................ 848
A.6.3.4.1 Test Purpose and Environment ........................................................................................................... 848
A.6.3.4.2 Test Requirements ............................................................................................................................... 849
A.6.3.5 E-UTRA TDD RRC connection release redirection to UTRA TDD ........................................................ 850
A.6.3.5.1 Test Purpose and Environment ........................................................................................................... 850
A.6.3.5.2 Test Requirements ............................................................................................................................... 852
A.6.3.6 E-UTRA FDD RRC connection release redirection to UTRA TDD ........................................................ 852
A.6.3.6.1 Test Purpose and Environment ........................................................................................................... 852
A. 6.3.6.2 Test Requirements ............................................................................................................................... 854
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 28 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.3.7 E-UTRA TDD RRC connection release redirection to UTRA TDD without SI provided ....................... 854
A.6.3.7.1 Test Purpose and Environment ........................................................................................................... 854
A.6.3.7.2 Test Requirements ............................................................................................................................... 857
A.6.3.8 E-UTRA FDD RRC connection release redirection to UTRA TDD without SI provided ....................... 857
A.6.3.8.1 Test Purpose and Environment ........................................................................................................... 857
A.6.3.8.2 Test Requirements ............................................................................................................................... 860
A.6.3.9 Redirection from E-UTRAN FDD to UTRAN FDD without System Information .................................. 860
A.6.3.9.1 Test Purpose and Environment ........................................................................................................... 860
A.6.3.9.2 Test Requirements ............................................................................................................................... 862
A.6.3.10 Redirection from E-UTRAN FDD to GERAN when System Information is not provided ...................... 862
A.6.3.10.1 Test Purpose and Environment ........................................................................................................... 862
A.6.3.10.2 Test Requirements ............................................................................................................................... 864
A.6.3.11 Redirection from E-UTRAN TDD to GERAN when System Information is not provided...................... 864
A.6.3.11.1 Test Purpose and Environment ........................................................................................................... 864
A.6.3.11.2 Test Requirements ............................................................................................................................... 866
A.6.3.12 E-UTRAN TDD RRC connection release redirection to UTRAN FDD without SI provided .................. 866
A.6.3.12.1 Test Purpose and Environment ........................................................................................................... 866
A.6.3.12.2 Test Requirements ............................................................................................................................... 869
A.7 Timing and Signalling Characteristics .................................................................................................870
A.7.1 UE Transmit Timing ...................................................................................................................................... 870
A.7.1.1 E-UTRAN FDD – UE Transmit Timing Accuracy Tests ......................................................................... 870
A.7.1.1.1 Test Purpose and Environment ........................................................................................................... 870
A.7.1.1.2 Test Requirements ............................................................................................................................... 871
A.7.1.2 E-UTRAN TDD - UE Transmit Timing Accuracy Tests ......................................................................... 872
A.7.1.2.1 Test Purpose and Environment ........................................................................................................... 872
A.7.1.2.2 Test Requirements ............................................................................................................................... 874
A.7.1.3 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for SCell.......................................................... 875
A.7.1.3.1 Test Purpose and Environment ........................................................................................................... 875
A.7.1.3.2 Test Requirements ............................................................................................................................... 877
A.7.1.4 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell .......................................................... 878
A.7.1.4.1 Test Purpose and Environment ........................................................................................................... 878
A.7.1.4.2 Test Requirements ............................................................................................................................... 880
A.7.1.4A E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell for 20 MHz + 10 MHz ..................... 881
A.7.1.4A.1 Test Purpose and Environment ........................................................................................................... 881
A.7.1.4A.2 Test Requirements ............................................................................................................................... 881
A.7.1.5 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for 5MHz Bandwidth ...................................... 881
A.7.1.5.1 Test Purpose and Environment ........................................................................................................... 881
A.7.1.5.2 Test Requirements ............................................................................................................................... 882
A.7.1.6 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for SCell in sTAG ........................................... 882
A.7.1.6.1 Test Purpose and Environment ........................................................................................................... 882
A.7.1.6.2 Test Requirements ............................................................................................................................... 884
A.7.1.7 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell in sTAG ........................................... 885
A.7.1.7.1 Test Purpose and Environment ........................................................................................................... 885
A.7.1.7.2 Test Requirements ............................................................................................................................... 886
A.7.1.7A E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell in sTAG for 20MHz +20MHz ......... 887
A.7.1.7A.1 Test Purpose and Environment ........................................................................................................... 887
A.7.1.7A.2 Test Requirements ............................................................................................................................... 887
A.7.1.7B E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell in sTAG for 20MHz +10MHz ......... 887
A.7.1.7B.1 Test Purpose and Environment ........................................................................................................... 887
A.7.1.7B.2 Test Requirements ............................................................................................................................... 888
A.7.1.8 Void .......................................................................................................................................................... 888
A.7.1.8.1 Void..................................................................................................................................................... 888
A.7.1.8.2 Void..................................................................................................................................................... 888
A.7.1.9 Void .......................................................................................................................................................... 888
A.7.1.9.1 Void..................................................................................................................................................... 888
A.7.1.9.2 Void..................................................................................................................................................... 888
A.7.1.10 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for Cat-M1 UE in CEModeA ......................... 888
A.7.1.10.1 Test Purpose and Environment ........................................................................................................... 888
A.7.1.10.2 Test Requirements ............................................................................................................................... 890
A.7.1.11 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for Cat-M1 UE in CEModeA .................. 890
A.7.1.11.1 Test Purpose and Environment ........................................................................................................... 890
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 29 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.1.11.2 Test Requirements ............................................................................................................................... 892
A.7.1.12 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for Cat-M1 UE in CEModeA .......................... 892
A.7.1.12.1 Test Purpose and Environment ........................................................................................................... 892
A.7.1.12.2 Test Requirements ............................................................................................................................... 894
A.7.1.13 3DL/3UL TDD CA UE Transmit Timing Accuracy Tests for 2 SCells ................................................... 894
A.7.1.13.1 Test Purpose and Environment ........................................................................................................... 894
A.7.1.13.2 Test Requirements ............................................................................................................................... 896
A.7.1.14 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for Cat-M1 UE in CEModeB .......................... 897
A.7.1.14.1 Test Purpose and Environment ........................................................................................................... 897
A.7.1.14.2 Test Requirements ............................................................................................................................... 898
A.7.1.15 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for Cat-M1 UE in CEModeB................... 898
A.7.1.15.1 Test Purpose and Environment ........................................................................................................... 898
A.7.1.15.2 Test Requirements ............................................................................................................................... 899
A.7.1.16 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for Cat-M1 UE in CEModeB .......................... 900
A.7.1.16.1 Test Purpose and Environment ........................................................................................................... 900
A.7.1.16.2 Test Requirements ............................................................................................................................... 901
A.7.1.17 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for Category NB1 UE In-Band mode
under normal coverage.............................................................................................................................. 902
A.7.1.17.1 Test Purpose and Environment ........................................................................................................... 902
A.7.1.17.2 Test Requirements ............................................................................................................................... 904
A.7.1.18 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for Category NB1 UE In-band mode
under enhanced coverage .......................................................................................................................... 904
A.7.1.18.1 Test Purpose and Environment ........................................................................................................... 904
A.7.1.18.2 Test Requirements ............................................................................................................................... 906
A.7.2 UE Timing Advance ....................................................................................................................................... 906
A.7.2.1 E-UTRAN FDD – UE Timing Advance Adjustment Accuracy Test ....................................................... 906
A.7.2.1.1 Test Purpose and Environment ........................................................................................................... 906
A.7.2.1.2 Test Requirements ............................................................................................................................... 908
A.7.2.2 E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test ....................................................... 908
A.7.2.2.1 Test Purpose and Environment ........................................................................................................... 908
A.7.2.2.2 Test Requirements ............................................................................................................................... 910
A.7.2.3 E-UTRAN FDD – UE Timing Advance Adjustment Accuracy Test for 5MHz ...................................... 910
A.7.2.3.1 Test Purpose and Environment ........................................................................................................... 910
A.7.2.3.2 Test Requirements ............................................................................................................................... 911
A.7.2.4 E-UTRAN FDD – UE Timing Advance Adjustment Accuracy Test for SCell in sTAG ......................... 911
A.7.2.4.1 Test Purpose and Environment ........................................................................................................... 911
A.7.2.4.2 Test Requirements ............................................................................................................................... 913
A.7.2.5 E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test for Scell in sTAG .......................... 913
A.7.2.5.1 Test Purpose and Environment ........................................................................................................... 913
A.7.2.5.2 Test Requirements ............................................................................................................................... 915
A.7.2.5A E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test for Scell in sTAG for 20 MHz
+20 MHz ................................................................................................................................................... 915
A.7.2.5A.1 Test Purpose and Environment ........................................................................................................... 915
A.7.2.5A.2 Test Requirements ............................................................................................................................... 916
A.7.2.5B E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test for Scell in sTAG for 20 MHz
+10 MHz ................................................................................................................................................... 916
A.7.2.5B.1 Test Purpose and Environment ........................................................................................................... 916
A.7.2.5B.2 Test Requirements ............................................................................................................................... 916
A.7.2.6 E-UTRAN FDD Timing Advance Adjustment Accuracy Test for Cat-M1 UE in CEModeA ................. 917
A.7.2.6.1 Test Purpose and Environment ........................................................................................................... 917
A.7.2.6.2 Test Requirements ............................................................................................................................... 919
A.7.2.7 E-UTRAN HD-FDD UE Timing Advance Adjustment Accuracy Test for Cat-M1 UE in CEModeA.... 919
A.7.2.7.1 Test Purpose and Environment ........................................................................................................... 919
A.7.2.7.2 Test Requirements ............................................................................................................................... 921
A.7.2.8 E-UTRAN TDD Timing Advance Adjustment Accuracy Test for Cat-M1 UE in CEModeA ................. 921
A.7.2.8.1 Test Purpose and Environment ........................................................................................................... 921
A.7.2.8.2 Test Requirements ............................................................................................................................... 923
A.7.2.9.2 Test Requirements ............................................................................................................................... 924
A.7.2.10 E-UTRAN FDD UE Timing Advance Adjustment Accuracy Test in CEModeB .................................... 925
A.7.2.10.1 Test Purpose and Environment ........................................................................................................... 925
A.7.2.10.2 Test Requirements ............................................................................................................................... 926
A.7.2.11 E-UTRAN HD-FDD UE Timing Advance Adjustment Accuracy Test in CEModeB ............................. 926
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 30 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.2.11.1 Test Purpose and Environment ........................................................................................................... 926
A.7.2.11.2 Test Requirements ............................................................................................................................... 928
A.7.2.12 E-UTRAN TDD UE Timing Advance Adjustment Accuracy Test in CEModeB .................................... 928
A.7.2.12.1 Test Purpose and Environment ........................................................................................................... 928
A.7.2.12.2 Test Requirements ............................................................................................................................... 930
A.7.3 Radio Link Monitoring ................................................................................................................................... 930
A.7.3.1 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync ................................................................ 931
A.7.3.1.1 Test Purpose and Environment ........................................................................................................... 931
A.7.3.1.2 Test Requirements ............................................................................................................................... 935
A.7.3.2 E-UTRAN FDD Radio Link Monitoring Test for In-sync ....................................................................... 935
A.7.3.2.1 Test Purpose and Environment ........................................................................................................... 935
A.7.3.2.2 Test Requirements ............................................................................................................................... 938
A.7.3.3 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync ................................................................ 938
A.7.3.3.1 Test Purpose and Environment ........................................................................................................... 938
A.7.3.3.2 Test Requirements ............................................................................................................................... 942
A.7.3.4 E-UTRAN TDD Radio Link Monitoring Test for In-sync ....................................................................... 942
A.7.3.4.1 Test Purpose and Environment ........................................................................................................... 942
A.7.3.4.2 Test Requirements ............................................................................................................................... 945
A.7.3.5 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync in DRX ................................................... 945
A.7.3.5.1 Test Purpose and Environment ........................................................................................................... 945
A.7.3.5.2 Test Requirements ............................................................................................................................... 949
A.7.3.6 E-UTRAN FDD Radio Link Monitoring Test for In-sync in DRX .......................................................... 950
A.7.3.6.1 Test Purpose and Environment ........................................................................................................... 950
A.7.3.6.2 Test Requirements ............................................................................................................................... 953
A.7.3.7 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync in DRX .................................................. 953
A.7.3.7.1 Test Purpose and Environment ........................................................................................................... 953
A.7.3.7.2 Test Requirements ............................................................................................................................... 956
A.7.3.8 E-UTRAN TDD Radio Link Monitoring Test for In-sync in DRX .......................................................... 956
A.7.3.8.1 Test Purpose and Environment ........................................................................................................... 956
A.7.3.8.2 Test Requirements ............................................................................................................................... 959
A.7.3.9 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync under Time Domain Measurement Resource
Restriction and Non-MBSFN ABS ........................................................................................................... 959
A.7.3.9.2 Test Requirements ............................................................................................................................... 962
A.7.3.10 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync under Time Domain Measurement
Resource Restriction with Non-MBSFN ABS .......................................................................................... 962
A.7.3.10.1 Test Purpose and Environment ........................................................................................................... 962
A.7.3.11 E-UTRAN FDD Radio Link Monitoring Test for In-sync for Non-MBSFN ABS................................... 965
A.7.3.11.1 Test Purpose and Environment ........................................................................................................... 965
A.7.3.11.2 Test Requirements ............................................................................................................................... 969
A.7.3.12 E-UTRAN TDD Radio Link Monitoring Test for In-sync for Non-MBSFN ABS .................................. 969
A.7.3.12.1 Test Purpose and Environment ........................................................................................................... 969
A.7.3.12.2 Test Requirements ............................................................................................................................... 973
A.7.3.13 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync under Time Domain Measurement
Resource Restriction with MBSFN ABS .................................................................................................. 973
A.7.3.13.1 Test Purpose and Environment ........................................................................................................... 973
A.7.3.13.2 Test Requirements ............................................................................................................................... 976
A.7.3.14 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync under Time Domain Measurement
Resource Restriction with MBSFN ABS .................................................................................................. 976
A.7.3.14.1 Test Purpose and Environment ........................................................................................................... 976
A.7.3.14.2 Test Requirements ............................................................................................................................... 979
A.7.3.15 E-UTRAN FDD Radio Link Monitoring Test for In-sync under Time Domain Measurement
Resource Restriction with MBSFN ABS .................................................................................................. 979
A.7.3.15.1 Test Purpose and Environment ........................................................................................................... 979
A.7.3.15.2 Test Requirements ............................................................................................................................... 982
A.7.3.16 E-UTRAN TDD Radio Link Monitoring Test for In-sync under Time Domain Measurement
Resource Restriction with MBSFN ABS .................................................................................................. 982
A.7.3.16.1 Test Purpose and Environment ........................................................................................................... 982
A.7.3.16.2 Test Requirements ............................................................................................................................... 986
A.7.3.17 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync under Time Domain Measurement
Resource Restriction with CRS Assistance Information and Non-MBSFN ABS .................................... 986
A.7.3.17.1 Test Purpose and Environment ........................................................................................................... 986
A.7.3.17.2 Test Requirements ............................................................................................................................... 989
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 31 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.18 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync under Time Domain Measurement
Resource Restriction with CRS Assistance Information and Non-MBSFN ABS .................................... 989
A.7.3.18.1 Test Purpose and Environment ........................................................................................................... 989
A.7.3.18.2 Test Requirements ............................................................................................................................... 993
A.7.3.19 E-UTRAN FDD Radio Link Monitoring Test for In-sync under Time Domain Measurement
Resouce Restriction with CRS assistance information and Non-MBSFN ABS ....................................... 993
A.7.3.19.1 Test Purpose and Environment ........................................................................................................... 993
A.7.3.19.2 Test Requirements ............................................................................................................................... 997
A.7.3.20 E-UTRAN TDD Radio Link Monitoring Test for In-sync under Time Domain Measurement
Resouce Restriction with CRS assistance information and Non-MBSFN ABS ....................................... 997
A.7.3.20.1 Test Purpose and Environment ........................................................................................................... 997
A.7.3.20.2 Test Requirements ............................................................................................................................. 1001
A.7.3.21 E-UTRAN FDD Radio Link Monitoring Test for In-sync under Time Domain Measurement
Resouce Restriction with CRS assistance information and MBSFN ABS ............................................. 1001
A.7.3.21.1 Test Purpose and Environment ......................................................................................................... 1001
A.7.3.21.2 Test Requirements ............................................................................................................................. 1005
A.7.3.22 E-UTRAN TDD Radio Link Monitoring Test for In-sync under Time Domain Measurement
Resouce Restriction with CRS assistance information and MBSFN ABS ............................................. 1005
A.7.3.22.1 Test Purpose and Environment ......................................................................................................... 1005
A.7.3.22.2 Test Requirements ............................................................................................................................. 1009
A.7.3.23 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync for 5MHz Bandwidth ........................... 1009
A.7.3.23.1 Test Purpose and Environment ......................................................................................................... 1009
A.7.3.23.2 Test Requirements ............................................................................................................................. 1010
A.7.3.24 E-UTRAN FDD Radio Link Monitoring Test for In-sync for 5MHz Bandwidth .................................. 1010
A.7.3.24.1 Test Purpose and Environment ......................................................................................................... 1010
A.7.3.24.2 Test Requirements ............................................................................................................................. 1011
A.7.3.25 E-UTRAN FDD Radio Link Monitoring Test for In-sync in DRX for 5MHz Bandwidth ..................... 1011
A.7.3.25.1 Test Purpose and Environment ......................................................................................................... 1011
A.7.3.25.2 Test Requirements ............................................................................................................................. 1012
A.7.3.26 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync for UE Category 0 ......................... 1012
A.7.3.26.1 Test Purpose and Environment ......................................................................................................... 1012
A.7.3.26.2 Test Requirements ............................................................................................................................. 1015
A.7.3.27 E-UTRAN FD-FDD Radio Link Monitoring Test for In-sync for UE Category 0 ................................. 1015
A.7.3.27.1 Test Purpose and Environment ......................................................................................................... 1015
A.7.3.27.2 Test Requirements ............................................................................................................................. 1018
A.7.3.28 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category 0 ............. 1018
A.7.3.28.1 Test Purpose and Environment ......................................................................................................... 1018
A.7.3.28.2 Test Requirements ............................................................................................................................. 1021
A.7.3.29 E-UTRAN FD-FDD Radio Link Monitoring Test for In-sync in DRX for UE Category 0 ................... 1021
A.7.3.29.1 Test Purpose and Environment ......................................................................................................... 1021
A.7.3.29.2 Test Requirements ............................................................................................................................. 1024
A.7.3.30 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync for UE Category 0 ......................... 1024
A.7.3.30.1 Test Purpose and Environment ......................................................................................................... 1024
A.7.3.30.2 Test Requirements ............................................................................................................................. 1027
A.7.3.31 E-UTRAN HD-FDD Radio Link Monitoring Test for In-sync for UE Category 0 ................................ 1027
A.7.3.31.1 Test Purpose and Environment ......................................................................................................... 1027
A.7.3.31.2 Test Requirements ............................................................................................................................. 1030
A.7.3.32 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category 0 ............ 1030
A.7.3.32.1 Test Purpose and Environment ......................................................................................................... 1030
A.7.3.32.2 Test Requirements ............................................................................................................................. 1033
A.7.3.33 E-UTRAN HD-FDD Radio Link Monitoring Test for In-sync in DRX for UE Category 0................... 1033
A.7.3.33.1 Test Purpose and Environment ......................................................................................................... 1033
A.7.3.33.2 Test Requirements ............................................................................................................................. 1036
A.7.3.34 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync for UE Category 0................................ 1036
A.7.3.34.1 Test Purpose and Environment ......................................................................................................... 1036
A.7.3.34.2 Test Requirements ............................................................................................................................. 1039
A.7.3.35 E-UTRAN TDD Radio Link Monitoring Test for In-sync for UE category 0 ........................................ 1039
A.7.3.35.1 Test Purpose and Environment ......................................................................................................... 1039
A.7.3.35.2 Test Requirements ............................................................................................................................. 1042
A.7.3.36 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category 0 ................... 1042
A.7.3.36.1 Test Purpose and Environment ......................................................................................................... 1042
A.7.3.36.2 Test Requirements ............................................................................................................................. 1045
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 32 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.37 E-UTRAN TDD Radio Link Monitoring Test for In-sync in DRX for UE category 0 .......................... 1045
A.7.3.37.1 Test Purpose and Environment ......................................................................................................... 1045
A.7.3.37.2 Test Requirements ............................................................................................................................. 1048
A.7.3.38 E-UTRAN FDD-FDD DC Radio Link Monitoring Test for Out-of-sync in DRX in synchronous DC . 1048
A.7.3.38.1 Test Purpose and Environment ......................................................................................................... 1048
A.7.3.38.2 Test Requirements ............................................................................................................................. 1051
A.7.3.39 E-UTRAN FDD-FDD DC Radio Link Monitoring Test for Out-of-sync in DRX in asynchronous
DC........................................................................................................................................................... 1051
A.7.3.39.1 Test Purpose and Environment ......................................................................................................... 1051
A.7.3.39.2 Test Requirements ............................................................................................................................. 1054
A.7.3.40 E-UTRAN TDD-TDD DC Radio Link Monitoring Test for Out-of-sync in DRX in synchronous DC . 1055
A.7.3.40.1 Test Purpose and Environment ......................................................................................................... 1055
A.7.3.40.2 Test Requirements ............................................................................................................................. 1057
A.7.3.41 E-UTRAN FDD-FDD Radio Link Monitoring Test for In-sync in DRX in synchronous dual
connectivity............................................................................................................................................. 1058
A.7.3.41.1 Test Purpose and Environment ......................................................................................................... 1058
A.7.3.41.2 Test Requirements ............................................................................................................................. 1061
A.7.3.42 E-UTRAN FDD-FDD DC Radio Link Monitoring Test for In-sync in DRX in asynchronous DC ....... 1061
A.7.3.42.1 Test Purpose and Environment ......................................................................................................... 1061
A.7.3.42.2 Test Requirements ............................................................................................................................. 1064
A.7.3.43 E-UTRAN TDD-TDD Radio Link Monitoring Test for In-sync in DRX in synchronous dual
connectivity............................................................................................................................................. 1064
A.7.3.43.1 Test Purpose and Environment ......................................................................................................... 1064
A.7.3.43.2 Test Requirements ............................................................................................................................. 1067
A.7.3.44 E-UTRAN TDD-FDD DC Radio Link Monitoring Test for Out-of-sync in DRX in synchronous DC
with PCell in FDD .................................................................................................................................. 1068
A.7.3.44.1 Test Purpose and Environment ......................................................................................................... 1068
A.7.3.44.2 Test Requirements ............................................................................................................................. 1070
A.7.3.45 E-UTRAN TDD-FDD DC Radio Link Monitoring Test for Out-of-sync in DRX in synchronous DC
with PCell in TDD .................................................................................................................................. 1071
A.7.3.45.1 Test Purpose and Environment ......................................................................................................... 1071
A.7.3.45.2 Test Requirements ............................................................................................................................. 1073
A.7.3.46 E-UTRAN TDD-FDD Radio Link Monitoring Test for In-sync in DRX for PSCell in synchronous
DC with PCell in FDD ............................................................................................................................ 1074
A.7.3.46.1 Test Purpose and Environment ......................................................................................................... 1074
A.7.3.46.2 Test Requirements ............................................................................................................................. 1077
A.7.3.47 E-UTRAN TDD-FDD Radio Link Monitoring Test for In-sync in DRX for PSCell in synchronous
DC with PCell in TDD............................................................................................................................ 1078
A.7.3.47.1 Test Purpose and Environment ......................................................................................................... 1078
A.7.3.47.2 Test Requirements ............................................................................................................................. 1081
A.7.3.48 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync for Cat-M1 UE in CEMode A ....... 1082
A.7.3.48.1 Test Purpose and Environment ......................................................................................................... 1082
A.7.3.48.2 Test Requirements ............................................................................................................................. 1084
A.7.3.49 E-UTRAN FD-FDD Radio Link Monitoring Test for In-Sync for Cat-M1 UE in CEMode A .............. 1084
A.7.3.49.1 Test Purpose and Environment ......................................................................................................... 1084
A.7.3.49.2 Test Requirements ............................................................................................................................. 1087
A.7.3.50 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category M1
configured in CEMode A ........................................................................................................................ 1087
A.7.3.50.1 Test Purpose and Environment ......................................................................................................... 1087
A.7.3.50.2 Test Requirements ............................................................................................................................. 1090
A.7.3.51 E-UTRAN FD-FDD Radio Link Monitoring Test for In-sync in DRX for UE Category M1
configured in CEMode A ........................................................................................................................ 1090
A.7.3.51.1 Test Purpose and Environment ......................................................................................................... 1090
A.7.3.51.2 Test Requirements ............................................................................................................................. 1093
A.7.3.52 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync for Cat-M1 UE in CEMode A....... 1093
A.7.3.52.1 Test Purpose and Environment ......................................................................................................... 1093
A.7.3.52.2 Test Requirements ............................................................................................................................. 1096
A.7.3.53 E-UTRAN HD-FDD Radio Link Monitoring Test for In-Sync for Cat-M1 UE in CEMode A ............. 1096
A.7.3.53.1 Test Purpose and Environment ......................................................................................................... 1096
A.7.3.53.2 Test Requirements ............................................................................................................................. 1099
A.7.3.54 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category M1
configured in CEMode A ........................................................................................................................ 1099
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 33 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.54.1 Test Purpose and Environment ......................................................................................................... 1099
A.7.3.54.2 Test Requirements ............................................................................................................................. 1102
A.7.3.55 E-UTRAN HD-FDD Radio Link Monitoring Test for In-sync in DRX for UE Category M1
configured in CEMode A ........................................................................................................................ 1102
A.7.3.55.1 Test Purpose and Environment ......................................................................................................... 1102
A.7.3.55.2 Test Requirements ............................................................................................................................. 1105
A.7.3.56 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync for Cat-M1 UE in CEMode A ............. 1105
A.7.3.56.1 Test Purpose and Environment ......................................................................................................... 1105
A.7.3.56.2 Test Requirements ............................................................................................................................. 1108
A.7.3.57 E-UTRAN TDD Radio Link Monitoring Test for In-Sync for Cat-M1 UE in CEMode A .................... 1108
A.7.3.57.1 Test Purpose and Environment ......................................................................................................... 1108
A.7.3.57.2 Test Requirements ............................................................................................................................. 1111
A.7.3.58 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category M1
configured in CEMode A ........................................................................................................................ 1111
A.7.3.58.1 Test Purpose and Environment ......................................................................................................... 1111
A.7.3.58.2 Test Requirements ............................................................................................................................. 1114
A.7.3.59 E-UTRAN TDD Radio Link Monitoring Test for In-sync in DRX for UE Category M1 configured
in CEMode A .......................................................................................................................................... 1114
A.7.3.59.1 Test Purpose and Environment ......................................................................................................... 1114
A.7.3.59.2 Test Requirements ............................................................................................................................. 1117
A.7.3.60 HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category NB1 In-band mode
in normal coverage.................................................................................................................................. 1117
A.7.3.60.1 Test Purpose and Environment ......................................................................................................... 1117
A.7.3.60.2 Test Requirements ............................................................................................................................. 1121
A.7.3.61 HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE category NB1 In-band mode
in enhanced coverage .............................................................................................................................. 1121
A.7.3.61.1 Test Purpose and Environment ......................................................................................................... 1121
A.7.3.61.2 Test Requirements ............................................................................................................................. 1125
A.7.3.62 HD-FDD Radio Link Monitoring Test for In-sync with DRX for UE Category NB1 In-Band mode
in Enhanced Coverage ............................................................................................................................ 1125
A.7.3.62.1 Test Purpose and Environment ......................................................................................................... 1125
A.7.3.62.2 Test Requirements ............................................................................................................................. 1129
A.7.3.63 HD-FDD Radio Link Monitoring Test for In-sync with DRX for UE Category NB1 In-Band mode
in Normal Coverage ................................................................................................................................ 1129
A.7.3.63.1 Test Purpose and Environment ......................................................................................................... 1129
A.7.3.63.2 Test Requirements ............................................................................................................................. 1133
A.7.3.64 HD-FDD Radio Link Monitoring Test for In-sync without DRX for UE Category NB1 In-Band
mode in Normal Coverage ...................................................................................................................... 1133
A.7.3.64.1 Test Purpose and Environment ......................................................................................................... 1133
A.7.3.64.2 Test Requirements ............................................................................................................................. 1136
A.7.3.65 HD-FDD Radio Link Monitoring Test for In-sync without DRX for UE Category NB1 In-Band
mode in Enhanced Coverage .................................................................................................................. 1137
A.7.3.65.1 Test Purpose and Environment ......................................................................................................... 1137
A.7.3.65.2 Test Requirements ............................................................................................................................. 1140
A.7.4 Interruption for Dual Connectivity ............................................................................................................... 1141
A.7.4.1 E-UTRAN FDD-FDD DC interruption at transitions between active and non-active during DRX in
synchronous DC...................................................................................................................................... 1141
A.7.4.1.1 Test Purpose and Environment ......................................................................................................... 1141
A.7.4.1.2 Test Requirements ............................................................................................................................. 1143
A.7.4.2 E-UTRAN TDD-TDD DC interruption at transitions between active and non-active during DRX in
synchronous DC...................................................................................................................................... 1143
A.7.4.2.1 Test Purpose and Environment ......................................................................................................... 1143
A.7.4.2.2 Test Requirements ............................................................................................................................. 1145
A.7.4.3 E-UTRAN FDD-FDD Interruption at transitions between active and non-active during DRX in
asynchronous dual connectivity .............................................................................................................. 1145
A.7.4.3.1 Test Purpose and Environment ......................................................................................................... 1145
A.7.4.3.2 Test Requirements ............................................................................................................................. 1147
A.7.4.4 E-UTRAN FDD-TDD DC interruption at transitions between active and non-active during DRX in
synchronous DC...................................................................................................................................... 1147
A.7.4.4.1 Test Purpose and Environment ......................................................................................................... 1147
A.7.4.4.2 Test Requirements ............................................................................................................................. 1150
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 34 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.4.5 E-UTRAN TDD-FDD DC interruption at transitions between active and non-active during DRX in
synchronous DC...................................................................................................................................... 1150
A.7.4.5.1 Test Purpose and Environment ......................................................................................................... 1150
A.7.4.5.2 Test Requirements ............................................................................................................................. 1152
A.7.5 Proximity-based Services ............................................................................................................................. 1152
A.7.5.1 E-UTRAN FDD – UE ProSe Direct Discovery Transmission Timing Accuracy Test ........................... 1152
A.7.5.1.1 Test Purpose and Environment ......................................................................................................... 1152
A.7.5.1.2 Test Requirements ............................................................................................................................. 1153
A.7.5.2 E-UTRAN TDD – UE ProSe Direct Discovery Transmission Timing Accuracy Test........................... 1154
A.7.5.2.1 Test Purpose and Environment ......................................................................................................... 1154
A.7.5.1.2 Test Requirements ............................................................................................................................. 1155
A.7.5.3 E-UTRAN FDD - Interruptions due to ProSe Direct Discovery............................................................. 1155
A.7.5.3.1 Test Purpose and Environment ......................................................................................................... 1155
A.7.5.3.2 Test Requirements ............................................................................................................................. 1157
A.7.5.4 E-UTRAN FDD – UE ProSe Direct Communication Transmission Timing Accuracy Test.................. 1158
A.7.5.4.1 Test Purpose and Environment ......................................................................................................... 1158
A.7.5.4.2 Test Requirements ............................................................................................................................. 1159
A.7.5.5 E-UTRAN FDD - Interruptions due to ProSe Direct Communication ................................................... 1159
A.7.5.5.1 Test Purpose and Environment ......................................................................................................... 1159
A.7.5.5.2 Test Requirements ............................................................................................................................. 1161
A.7.5.6 E-UTRAN FDD - Interruptions due to ProSe Direct Discovery with discovery period less than
320ms...................................................................................................................................................... 1162
A.7.5.6.1 Test Purpose and Environment ......................................................................................................... 1162
A.7.5.6.2 Test Requirements ............................................................................................................................. 1163
A.7.5.7 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct Discovery ................................................... 1164
A.7.5.7.1 Test Purpose and Environment ......................................................................................................... 1164
A.7.5.7.2 Test Requirements ............................................................................................................................. 1166
A.7.5.8 E-UTRAN FDD-FDD - Cell reselection and timing accuracy for ProSe Direct Discovery
transmission on non-serving frequency .................................................................................................. 1166
A.7.5.8.1 Test Purpose and Environment ......................................................................................................... 1166
A.7.5.8.2 Test Requirements ............................................................................................................................. 1168
A.7.5.9 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct Discovery reception on non-serving
frequency ................................................................................................................................................ 1169
A.7.5.9.1 Test Purpose and Environment ......................................................................................................... 1169
A.7.5.9.2 Test Requirements ............................................................................................................................. 1171
A.7.5.10 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct Discovery transmission on non-serving
frequency ................................................................................................................................................ 1172
A.7.5.10.1 Test Purpose and Environment ......................................................................................................... 1172
A.7.5.10.2 Test Requirements ............................................................................................................................. 1174
A.7.5.11 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct Communication on non-serving frequency 1175
A.7.5.11.1 Test Purpose and Environment ......................................................................................................... 1175
A.7.5.11.2 Test Requirements ............................................................................................................................. 1177
A.7.5.12 E-UTRAN FDD - Selection / Reselection of ProSe relay UE ................................................................ 1177
A.7.5.12.1 Test Purpose and Environment ......................................................................................................... 1177
A.7.5.12.2 Test Requirements ............................................................................................................................. 1181
A.8 UE Measurements Procedures............................................................................................................1182
A.8.1 E-UTRAN FDD Intra-frequency Measurements.......................................................................................... 1182
A.8.1.1 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in asynchronous cells .............................................................................................................................. 1182
A.8.1.1.1 Test Purpose and Environment ......................................................................................................... 1182
A.8.1.1.2 Test Requirements ............................................................................................................................. 1183
A.8.1.2 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells ................................................................................................................................ 1184
A.8.1.2.1 Test Purpose and Environment ......................................................................................................... 1184
A.8.1.2.2 Test Requirements ............................................................................................................................. 1185
A.8.1.3 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells with DRX .............................................................................................................. 1186
A.8.1.3.1 Test Purpose and Environment ......................................................................................................... 1186
A.8.1.3.2 Test Requirements ............................................................................................................................. 1188
A.8.1.4 Void ........................................................................................................................................................ 1188
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 35 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.5 E-UTRAN FDD - FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps .................................................................................................................................... 1188
A.8.1.5.1 Test Purpose and Environment ......................................................................................................... 1188
A.8.1.5.2 Test Requirements ............................................................................................................................. 1190
A.8.1.6 E-UTRAN FDD - FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps with DRX ................................................................................................................... 1190
A.8.1.6.1 Test Purpose and Environment ......................................................................................................... 1190
A.8.1.6.2 Test Requirements ............................................................................................................................. 1192
A.8.1.7 E-UTRAN FDD-FDD Intra-Frequency Event-Triggered Reporting under Time Domain
Measurement Resource Restriction with Non-MBSFN ABS ................................................................. 1193
A.8.1.7.1 Test Purpose and Environment ......................................................................................................... 1193
A.8.1.7.2 Test Requirements ............................................................................................................................. 1195
A.8.1.8 E-UTRAN FDD-FDD Intra-Frequency Event-Triggered Reporting under Time Domain
Measurement Resource Restriction with CRS Assistance Information and Non-MBSFN ABS ............ 1196
A.8.1.8.1 Test Purpose and Environment ......................................................................................................... 1196
A.8.1.8.2 Test Requirements ............................................................................................................................. 1198
A.8.1.9 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in asynchronous cells for 5MHz bandwidth ........................................................................................... 1199
A.8.1.9.1 Test Purpose and Environment ......................................................................................................... 1199
A.8.1.9.2 Test Requirements ............................................................................................................................. 1199
A.8.1.10 E-UTRAN FDD-FDD Intra-Frequency Event Triggered Reporting under Fading Propagation
Conditions in Synchronous Cells with DRX for 5 MHz Bandwidth ...................................................... 1199
A.8.1.10.1 Test Purpose and Environment ......................................................................................................... 1199
A.8.1.10.2 Test Requirements ............................................................................................................................. 1200
A.8.1.11 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in asynchronous cells for UE category 0 ................................................................................................ 1200
A.8.1.11.1 Test Purpose and Environment ......................................................................................................... 1200
A.8.1.11.2 Test Requirements ............................................................................................................................. 1202
A.8.1.12 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells for UE category 0 .................................................................................................. 1203
A.8.1.12.1 Test Purpose and Environment ......................................................................................................... 1203
A.8.1.12.2 Test Requirements ............................................................................................................................. 1204
A.8.1.13 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells with DRX for UE category 0 ................................................................................. 1205
A.8.1.13.1 Test Purpose and Environment ......................................................................................................... 1205
A.8.1.13.2 Test Requirements ............................................................................................................................. 1207
A.8.1.14 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in asynchronous cells for UE category 0 ................................................................................................ 1207
A.8.1.14.1 Test Purpose and Environment ......................................................................................................... 1207
A.8.1.14.2 Test Requirements ............................................................................................................................. 1209
A.8.1.15 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells for UE category 0 .................................................................................................. 1210
A.8.1.15.1 Test Purpose and Environment ......................................................................................................... 1210
A.8.1.15.2 Test Requirements ............................................................................................................................. 1211
A.8.1.16 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells with DRX for UE category 0 ................................................................................. 1212
A.8.1.16.1 Test Purpose and Environment ......................................................................................................... 1212
A.8.1.16.2 Test Requirements ............................................................................................................................. 1214
A.8.1.17 E-UTRAN TDD-TDD intra-frequency event triggered reporting under fading propagation
conditions in synchronous cells .............................................................................................................. 1214
A.8.1.17.1 Test Purpose and Environment ......................................................................................................... 1214
A.8.1.17.2 Test Requirements ............................................................................................................................. 1216
A.8.1.18 E-UTRAN TDD-TDD intra-frequency event triggered reporting under fading propagation
conditions in synchronous cells with DRX ............................................................................................. 1217
A.8.1.18.1 Test Purpose and Environment ......................................................................................................... 1217
A.8.1.18.2 Test Requirements ............................................................................................................................. 1219
A.8.1.19 E-UTRAN FDD-FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps for UE category 0 ....................................................................................................... 1219
A.8.1.19.1 Test Purpose and Environment ......................................................................................................... 1219
A.8.1.19.2 Test Requirements ............................................................................................................................. 1221
A.8.1.20 E-UTRAN FDD - FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps with DRX for UE category 0...................................................................................... 1222
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 36 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.20.1 Test Purpose and Environment ......................................................................................................... 1222
A.8.1.20.2 Test Requirements ............................................................................................................................. 1224
A.8.1.21 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps for UE category 0 ....................................................................................................... 1224
A.8.1.21.1 Test Purpose and Environment ......................................................................................................... 1224
A.8.1.21.2 Test Requirements ............................................................................................................................. 1226
A.8.1.22 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps with DRX for UE category 0...................................................................................... 1227
A.8.1.22.1 Test Purpose and Environment ......................................................................................................... 1227
A.8.1.22.2 Test Requirements ............................................................................................................................. 1229
A.8.1.23 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in asynchronous cells for Cat-M1 UE in CEModeA .............................................................................. 1229
A.8.1.23.1 Test Purpose and Environment ......................................................................................................... 1229
A.8.1.23.2 Test Requirements ............................................................................................................................. 1230
A.8.1.24 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells for Cat-M1 UE in CEModeA ................................................................................ 1231
A.8.1.24.1 Test Purpose and Environment ......................................................................................................... 1231
A.8.1.24.2 Test Requirements ............................................................................................................................. 1232
A.8.1.25 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells for Cat-M1 UE in CEModeA in DRX ................................................................... 1233
A.8.1.25.1 Test Purpose and Environment ......................................................................................................... 1233
A.8.1.25.2 Test Requirements ............................................................................................................................. 1235
A.8.1.26 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in asynchronous cells for Cat-M1 UE in CEModeA .............................................................................. 1235
A.8.1.26.1 Test Purpose and Environment ......................................................................................................... 1235
A.8.1.27 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells for Cat-M1 UE in CEModeA ................................................................................ 1238
A.8.1.27.1 Test Purpose and Environment ......................................................................................................... 1238
A.8.1.27.2 Test Requirements ............................................................................................................................. 1239
A.8.1.28 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells for Cat-M1 UE in CEModeA in DRX ................................................................... 1240
A.8.1.28.1 Test Purpose and Environment ......................................................................................................... 1240
A.8.1.28.2 Test Requirements ............................................................................................................................. 1242
A.8.1.29 E-UTRAN TDD intra-frequency event triggered reporting under fading propagation conditions in
synchronous cells for Cat-M1 UE in CEModeA .................................................................................... 1242
A.8.1.29.1 Test Purpose and Environment ......................................................................................................... 1242
A.8.1.29.2 Test Requirements ............................................................................................................................. 1244
A.8.1.30 E-UTRAN TDD intra-frequency event triggered reporting under fading propagation conditions in
synchronous cells for Cat-M1 UE in CEModeA in DRX ....................................................................... 1245
A.8.1.30.1 Test Purpose and Environment ......................................................................................................... 1245
A.8.1.30.2 Test Requirements ............................................................................................................................. 1247
A.8.1.31 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions in
asynchronous cells for Cat-M1 UE in CEModeB ................................................................................... 1247
A.8.1.31.1 Test Purpose and Environment ......................................................................................................... 1247
A.8.1.31.2 Test Requirements ............................................................................................................................. 1249
A.8.1.32 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions in
synchronous cells for Cat-M1 UE in CEModeB..................................................................................... 1250
A.8.1.32.1 Test Purpose and Environment ......................................................................................................... 1250
A.8.1.32.2 Test Requirements ............................................................................................................................. 1251
A.8.1.33 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in asynchronous cells for Cat-M1 UE in CEModeB ............................................................................... 1252
A.8.1.33.1 Test Purpose and Environment ......................................................................................................... 1252
A.8.1.33.2 Test Requirements ............................................................................................................................. 1253
A.8.1.34 E-UTRAN HD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells for Cat-M1 UE in CEModeB ................................................................................ 1254
A.8.1.34.1 Test Purpose and Environment ......................................................................................................... 1254
A.8.1.34.2 Test Requirements ............................................................................................................................. 1255
A.8.1.35 E-UTRAN TDD intra-frequency event triggered reporting under fading propagation conditions in
synchronous cells for Cat-M1 UE in CEModeB..................................................................................... 1256
A.8.1.35.1 Test Purpose and Environment ......................................................................................................... 1256
A.8.1.35.2 Test Requirements ............................................................................................................................. 1257
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 37 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.36 E-UTRAN FDD Intra-frequency identification of a new CGI of E-UTRA cell using autonomous
gaps for Cat-M1 UE in CEModeB.......................................................................................................... 1258
A.8.1.36.1 Test Purpose and Environment ......................................................................................................... 1258
A.8.1.36.2 Test Requirements ............................................................................................................................. 1259
A.8.1.37 E-UTRAN FDD Intra-frequency identification of a new CGI of E-UTRA cell using autonomous
gaps with DRX for Cat-M1 UE in CEModeB ........................................................................................ 1260
A.8.1.37.1 Test Purpose and Environment ......................................................................................................... 1260
A.8.1.37.2 Test Requirements ............................................................................................................................. 1262
A.8.1.38 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps for Cat-M1 UE in CEModeB ..................................................................................... 1262
A.8.1.38.1 Test Purpose and Environment ......................................................................................................... 1262
A.8.1.38.2 Test Requirements ............................................................................................................................. 1263
A.8.1.39 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps with DRX for Cat-M1 UE in CEModeB .................................................................... 1264
A.8.1.39.1 Test Purpose and Environment ......................................................................................................... 1264
A.8.1.39.2 Test Requirements ............................................................................................................................. 1266
A.8.2 E-UTRAN TDD Intra-frequency Measurements ......................................................................................... 1266
A.8.2.1 E-UTRAN TDD-TDD intra-frequency event triggered reporting under fading propagation
conditions in synchronous cells .............................................................................................................. 1266
A.8.2.1.1 Test Purpose and Environment ......................................................................................................... 1266
A.8.2.1.2 Test Requirements ............................................................................................................................. 1268
A.8.2.2 E-UTRAN TDD-TDD intra-frequency event triggered reporting under fading propagation
conditions in synchronous cells with DRX ............................................................................................. 1269
A.8.2.2.1 Test Purpose and Environment ......................................................................................................... 1269
A.8.2.2.2 Test Requirements ............................................................................................................................. 1271
A.8.2.3 E-UTRAN TDD - TDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps .................................................................................................................................... 1271
A.8.2.3.1 Test Purpose and Environment ......................................................................................................... 1271
A.8.2.3.2 Test Requirements ............................................................................................................................. 1273
A.8.2.4 E-UTRAN TDD - TDD Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps with DRX ................................................................................................................... 1274
A.8.2.4.1 Test Purpose and Environment ......................................................................................................... 1274
A.8.2.4.2 Test Requirements ............................................................................................................................. 1276
A.8.2.5 E-UTRAN TDD-TDD Intra-Frequency Event-Triggered Reporting under Time Domain
Measurement Resource Restriction with Non-MBSFN ABS ................................................................. 1276
A.8.2.5.1 Test Purpose and Environment ......................................................................................................... 1276
A.8.2.5.2 Test Requirements ............................................................................................................................. 1278
A.8.2.6 E-UTRAN TDD-TDD Intra-Frequency Event-Triggered Reporting under Time Domain
Measurement Resource Restriction with CRS Assistance Information and Non-MBSFN ABS ............ 1279
A.8.2.6.1 Test Purpose and Environment ......................................................................................................... 1279
A.8.2.6.2 Test Requirements ............................................................................................................................. 1281
A.8.2.7 E-UTRAN TDD Intra-frequency identification of a new CGI of E-UTRA cell using autonomous
gaps ......................................................................................................................................................... 1282
A.8.2.7.1 Test Purpose and Environment ......................................................................................................... 1282
A.8.2.7.2 Test Requirements ............................................................................................................................. 1283
A.8.2.8 E-UTRAN TDD Intra-frequency identification of a new CGI of E-UTRA cell using autonomous
gaps with DRX ....................................................................................................................................... 1284
A.8.2.8.1 Test Purpose and Environment ......................................................................................................... 1284
A.8.2.8.2 Test Requirements ............................................................................................................................. 1286
A.8.2.9 E-UTRAN TDD Intra-frequency identification of a new CGI of E-UTRA cell using autonomous
gaps for Cat-M1 UE in CEModeB.......................................................................................................... 1286
A.8.2.9.1 Test Purpose and Environment ......................................................................................................... 1286
A.8.2.9.2 Test Requirements ............................................................................................................................. 1288
A.8.2.10 E-UTRAN TDD Intra-frequency identification of a new CGI of E-UTRA cell using autonomous
gaps with DRX for Cat-M1 UE in CEModeB ........................................................................................ 1289
A.8.2.10.1 Test Purpose and Environment ......................................................................................................... 1289
A.8.2.10.2 Test Requirements ............................................................................................................................. 1291
A.8.3 E-UTRAN FDD - FDD Inter-frequency Measurements .............................................................................. 1291
A.8.3.1 E-UTRAN FDD-FDD Inter-frequency event triggered reporting under fading propagation
conditions in asynchronous cells ............................................................................................................ 1291
A.8.3.1.1 Test Purpose and Environment ......................................................................................................... 1291
A.8.3.1.2 Test Requirements ............................................................................................................................. 1293
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 38 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.3.2 E-UTRAN FDD-FDD Inter-frequency event triggered reporting when DRX is used under fading
propagation conditions in asynchronous cells ........................................................................................ 1294
A.8.3.2.1 Test Purpose and Environment ......................................................................................................... 1294
A.8.3.2.2 Test Requirements ............................................................................................................................. 1296
A.8.3.3 E-UTRAN FDD-FDD inter-frequency event triggered reporting under AWGN propagation
conditions in asynchronous cells with DRX when L3 filtering is used .................................................. 1296
A.8.3.3.1 Test Purpose and Environment ......................................................................................................... 1296
A.8.3.3.2 Test Requirements ............................................................................................................................. 1299
A.8.3.4 E-UTRAN FDD - FDD Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps .................................................................................................................................... 1299
A.8.3.4.1 Test Purpose and Environment ......................................................................................................... 1299
A.8.3.4.2 Test Requirements ............................................................................................................................. 1301
A.8.3.5 E-UTRAN FDD - FDD Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps with DRX ................................................................................................................... 1301
A.8.3.5.2 Test Requirements ............................................................................................................................. 1303
A.8.3.6 E-UTRAN FDD-FDD Inter-frequency event triggered reporting without measurement gaps under
AWGN propagation conditions in asynchronous cells ........................................................................... 1303
A.8.3.6.1 Test Purpose and Environment ......................................................................................................... 1303
A.8.3.6.2 Test Requirements ............................................................................................................................. 1305
A.8.3.7 E-UTRAN FDD-FDD Inter-frequency event triggered reporting under fading propagation
conditions in asynchronous cells for Increased Carrier Monitoring without Reduced Performance
Group ...................................................................................................................................................... 1306
A.8.3.7.1 Test Purpose and Environment ......................................................................................................... 1306
A.8.3.7.2 Test Requirements ............................................................................................................................. 1308
A.8.3.8 FDD-FDD Interfrequency correct reporting of measurement events with reduced performance group
configured, non DRX .............................................................................................................................. 1309
A.8.3.8.1 Test Purpose and Environment ......................................................................................................... 1309
A.8.3.8.2 Test Requirements ............................................................................................................................. 1312
A.8.3.9 FDD-FDD Inter-frequency correct reporting of measurement events with reduced performance
group configured, DRX .......................................................................................................................... 1312
A.8.3.9.1 Test Purpose and Environment ......................................................................................................... 1312
A.8.3.9.2 Test Requirements ............................................................................................................................. 1315
A.8.4 E-UTRAN TDD - TDD Inter-frequency Measurements .............................................................................. 1316
A.8.4.1 E-UTRAN TDD-TDD Inter-frequency event triggered reporting under fading propagation
conditions in synchronous cells .............................................................................................................. 1316
A.8.4.1.1 Test Purpose and Environment ......................................................................................................... 1316
A.8.4.1.2 Test Requirements ............................................................................................................................. 1317
A.8.4.2 E-UTRAN TDD-TDD Inter-frequency event triggered reporting when DRX is used under fading
propagation conditions in synchronous cells .......................................................................................... 1318
A.8.4.2.1 Test Purpose and Environment ......................................................................................................... 1318
A.8.4.2.2 Test Requirements ............................................................................................................................. 1320
A.8.4.3 E-UTRAN TDD-TDD inter-frequency event triggered reporting under AWGN propagation
conditions in synchronous cells with DRX when L3 filtering is used .................................................... 1320
A.8.4.3.1 Test Purpose and Environment ......................................................................................................... 1320
A.8.4.3.2 Test Requirements ............................................................................................................................. 1322
A.8.4.4 E-UTRAN TDD - TDD Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps .................................................................................................................................... 1323
A.8.4.4.1 Test Purpose and Environment ......................................................................................................... 1323
A.8.4.4.2 Test Requirements ............................................................................................................................. 1325
A.8.4.5 E-UTRAN TDD - TDD Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps with DRX ................................................................................................................... 1326
A.8.4.5.1 Test Purpose and Environment ......................................................................................................... 1326
A.8.4.5.2 Test Requirements ............................................................................................................................. 1328
A.8.4.6 E-UTRAN TDD-TDD Inter-frequency event triggered reporting for TDD UL/DL configuration 0 ..... 1328
A.8.4.6.1 Test Purpose and Environment ......................................................................................................... 1328
A.8.4.6.2 Test Requirements ............................................................................................................................. 1329
A.8.4.7 E-UTRAN TDD-TDD Inter-frequency event triggered reporting under fading propagation
conditions in synchronous cells for Increased Carrier Monitoring without Reduced Performance
Group ...................................................................................................................................................... 1329
A.8.4.7.1 Test Purpose and Environment ......................................................................................................... 1329
A.8.4.7.2 Test Requirements ............................................................................................................................. 1333
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 39 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.4.8 TDD-TDD Interfrequency correct reporting of measurement events with reduced performance group
configured, non DRX .............................................................................................................................. 1333
A.8.4.8.1 Test Purpose and Environment ......................................................................................................... 1333
A.8.4.8.2 Test Requirements ............................................................................................................................. 1336
A.8.4.9 TDD-TDD Inter-frequency correct reporting of measurement events with reduced performance
group configured, DRX .......................................................................................................................... 1336
A.8.4.9.1 Test Purpose and Environment ......................................................................................................... 1336
A.8.4.9.2 Test Requirements ............................................................................................................................. 1340
A.8.5 E-UTRAN FDD - UTRAN FDD Measurements ......................................................................................... 1341
A.8.5.1 E-UTRAN FDD - UTRAN FDD event triggered reporting under fading propagation conditions ......... 1341
A.8.5.1.1 Test Purpose and Environment ......................................................................................................... 1341
A.8.5.1.2 Test Requirements ............................................................................................................................. 1342
A.8.5.2 E-UTRAN FDD - UTRAN FDD SON ANR cell search reporting under AWGN propagation
conditions ................................................................................................................................................ 1343
A.8.5.2.1 Test Purpose and Environment ......................................................................................................... 1343
A.8.5.2.2 Test Requirements ............................................................................................................................. 1345
A.8.5.3 E-UTRAN FDD-UTRAN FDD event triggered reporting when DRX is used under fading
propagation conditions ............................................................................................................................ 1345
A.8.5.3.1 Test Purpose and Environment ......................................................................................................... 1345
A.8.5.3.2 Test Requirements ............................................................................................................................. 1348
A.8.5.4 E-UTRAN FDD - UTRAN FDD enhanced cell identification under AWGN propagation conditions .. 1348
A.8.5.4.1 Test Purpose and Environment ......................................................................................................... 1348
A.8.5.4.2 Test Requirements ............................................................................................................................. 1351
A.8.5.5 E- UTRAN FDD - UTRAN FDD identification of a new CGI of UTRAN cell using autonomous
gaps ......................................................................................................................................................... 1351
A.8.5.5.1 Test Purpose and Environment ......................................................................................................... 1351
A.8.5.5.2 Test Requirements ............................................................................................................................. 1353
A.8.5.6 E-UTRAN FDD - UTRAN FDD event triggered reporting without measurement gaps under AWGN
propagation conditions ............................................................................................................................ 1353
A.8.5.6.1 Test Purpose and Environment ......................................................................................................... 1353
A.8.5.6.2 Test Requirements ............................................................................................................................. 1354
A.8.5.7 E-UTRAN FDD - UTRAN FDD Event Triggered Reporting under Fading Propagation Conditions
for 5 MHz Bandwidth ............................................................................................................................. 1355
A.8.5.7.1 Test Purpose and Environment ......................................................................................................... 1355
A.8.5.7.2 Test Requirements ............................................................................................................................. 1355
A.8.5.8 E-UTRA FDD InterRAT UTRA FDD correct reporting of measurement events with reduced
performance group configured, non DRX .............................................................................................. 1355
A.8.5.8.1 Test Purpose and Environment ......................................................................................................... 1355
A.8.5.8.2 Test Requirements ............................................................................................................................. 1358
A.8.6 E-UTRAN TDD - UTRAN FDD Measurements ......................................................................................... 1358
A.8.6.1 E-UTRAN TDD - UTRAN FDD event triggered reporting under fading propagation conditions ......... 1358
A.8.6.1.1 Test Purpose and Environment ......................................................................................................... 1358
A.8.6.1.2 Test Requirements ............................................................................................................................. 1360
A.8.6.2 E- UTRAN TDD - UTRAN FDD identification of a new CGI of UTRAN cell using autonomous
gaps ......................................................................................................................................................... 1361
A.8.6.2.1 Test Purpose and Environment ......................................................................................................... 1361
A.8.6.2.2 Test Requirements ............................................................................................................................. 1363
A.8.6.3 E-UTRA TDD InterRAT UTRA FDD correct reporting of measurement events with reduced
performance group configured, non DRX .............................................................................................. 1363
A.8.6.3.1 Test Purpose and Environment ......................................................................................................... 1363
A.8.6.3.2 Test Requirements ............................................................................................................................. 1366
A.8.7 E-UTRAN TDD – UTRAN TDD Measurements ........................................................................................ 1366
A.8.7.1 E-UTRAN TDD to UTRAN TDD cell search under fading propagation conditions ............................. 1366
A.8.7.1.1 Test Purpose and Environment ......................................................................................................... 1366
A.8.7.1.1.1 Void ............................................................................................................................................. 1366
A.8.7.1.1.2 1.28 Mcps TDD option ................................................................................................................ 1366
A.8.7.1.1.3 Void ............................................................................................................................................. 1369
A.8.7.1.2 Test Requirements ............................................................................................................................. 1369
A.8.7.1.2.1 Void ............................................................................................................................................. 1369
A.8.7.1.2.2 1.28 Mcps TDD option ................................................................................................................ 1369
A.8.7.1.2.3 Void ............................................................................................................................................. 1369
A.8.7.2 E-UTRAN TDD-UTRAN TDD cell search when DRX is used under fading propagation conditions .. 1369
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 40 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.7.2.1 Test Purpose and Environment ......................................................................................................... 1369
A.8.7.2.2 Test Requirements ............................................................................................................................. 1372
A.8.7.3 E-UTRAN TDD - UTRAN TDD SON ANR cell search reporting in AWGN propagation conditions . 1373
A.8.7.3.1 Test Purpose and Environment ......................................................................................................... 1373
A.8.7.3.2 Test Parameters ................................................................................................................................. 1373
A.8.7.3.3 Test Requirements ............................................................................................................................. 1374
A.8.7.4 E-UTRAN TDD - UTRAN TDD enhanced cell identification under AWGN propagation conditions .. 1375
A.8.7.4.1 Test Purpose and Environment ......................................................................................................... 1375
A.8.7.4.2 Test Requirements ............................................................................................................................. 1377
A.8.7.5 E-UTRA TDD InterRAT UTRA TDD correct reporting of measurement events with reduced
performance group configured, non DRX .............................................................................................. 1377
A.8.7.5.1 Test Purpose and Environment ......................................................................................................... 1377
A.8.7.5.2 Test Requirements ............................................................................................................................. 1379
A.8.7A TBD .............................................................................................................................................................. 1379
A.8.7A.1 E-UTRA FDD InterRAT UTRA TDD correct reporting of measurement events with reduced
performance group configured, non DRX .............................................................................................. 1379
A.8.7A.1.1 Test Purpose and Environment ......................................................................................................... 1379
A.8.7A.1.2 Test Requirements ............................................................................................................................. 1382
A.8.8 E-UTRAN FDD – GSM Measurements ....................................................................................................... 1382
A.8.8.1 E-UTRAN FDD – GSM event triggered reporting in AWGN ............................................................... 1382
A.8.8.1.1 Test Purpose and Environment ......................................................................................................... 1382
A.8.8.1.2 Test Requirements ............................................................................................................................. 1384
A.8.8.2 E-UTRAN FDD-GSM event triggered reporting when DRX is used in AWGN ................................... 1384
A.8.8.2.1 Test Purpose and Environment ......................................................................................................... 1384
A.8.8.2.2 Test Requirements ............................................................................................................................. 1386
A.8.8.3 E-UTRAN FDD – GSM event triggered reporting in AWGN with enhanced BSIC identification ....... 1387
A.8.8.3.1 Test Purpose and Environment ......................................................................................................... 1387
A.8.8.3.2 Test Requirements ............................................................................................................................. 1388
A.8.9 E-UTRAN FDD - UTRAN TDD measurements.......................................................................................... 1389
A.8.9.1 E-UTRAN FDD - UTRAN TDD event triggered reporting in fading propagation conditions............... 1389
A.8.9.1.1 Test Purpose and Environment ......................................................................................................... 1389
A.8.9.1.2 Test Requirements ............................................................................................................................. 1390
A.8.9.2 E-UTRAN FDD - UTRAN TDD enhanced cell identification under AWGN propagation conditions .. 1391
A.8.9.2.1 Test Purpose and Environment ......................................................................................................... 1391
A.8.9.2.2 Test Requirements ............................................................................................................................. 1393
A.8.10 E-UTRAN TDD – GSM Measurements ................................................................................................. 1393
A.8.10.1 E-UTRAN TDD – GSM event triggered reporting in AWGN ............................................................... 1393
A.8.10.1.1 Test Purpose and Environment ......................................................................................................... 1393
A.8.10.1.2 Test Requirements ............................................................................................................................. 1394
A.8.10.2 E-UTRAN TDD-GSM event triggered reporting when DRX is used in AWGN ................................... 1395
A.8.10.2.1 Test Purpose and Environment ......................................................................................................... 1395
A.8.10.2.2 Test Requirements ............................................................................................................................. 1397
A.8.11 Monitoring of Multiple Layers ..................................................................................................................... 1397
A.8.11.1 Multiple E-UTRAN FDD-FDD Inter-frequency event triggered reporting under fading propagation
conditions ................................................................................................................................................ 1397
A.8.11.1.1 Test Purpose and Environment ......................................................................................................... 1397
A.8.11.1.2 Test Requirements ............................................................................................................................. 1399
A.8.11.2 E-UTRAN TDD – E-UTRAN TDD and E-UTRAN TDD Inter-frequency event triggered reporting
under fading propagation conditions ...................................................................................................... 1400
A.8.11.2.1 Test Purpose and Environment ......................................................................................................... 1400
A.8.11.2.2 Test Requirements ............................................................................................................................. 1401
A.8.11.3 E-UTRAN FDD-FDD Inter-frequency and UTRAN FDD event triggered reporting under fading
propagation conditions ............................................................................................................................ 1402
A.8.11.3.1 Test Purpose and Environment ......................................................................................................... 1402
A.8.11.3.2 Test Requirements ............................................................................................................................. 1404
A.8.11.4 InterRAT E-UTRA TDD to E-UTRA TDD and UTRA TDD cell search test case ............................... 1404
A.8.11.4.1 Test Purpose and Environment ......................................................................................................... 1404
A.8.11.4.2 Test Requirements ............................................................................................................................. 1407
A.8.11.5 Combined E-UTRAN FDD – E-UTRA FDD and GSM cell search. E-UTRA cells in fading; GSM
cell in static propagation conditions........................................................................................................ 1407
A.8.11.5.1 Test Purpose and Environment ......................................................................................................... 1407
A.8.11.5.2 Test Requirements ............................................................................................................................. 1409
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 41 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.11.6 Combined E-UTRAN TDD – E-UTRA TDD and GSM cell search. E-UTRA cells in fading; GSM
cell in static propagation conditions........................................................................................................ 1410
A.8.11.6.1 Test Purpose and Environment ......................................................................................................... 1410
A.8.11.6.2 Test Requirements ............................................................................................................................. 1412
A.8.12 RSTD Intra-frequency Measurements .......................................................................................................... 1413
A.8.12.1 E-UTRAN FDD intra-frequency RSTD measurement reporting delay test case .................................... 1413
A.8.12.1.1 Test Purpose and Environment ......................................................................................................... 1413
A.8.12.1.2 Test Requirements ............................................................................................................................. 1416
A.8.12.2 E-UTRAN TDD intra-frequency RSTD measurement reporting delay test case ................................... 1417
A.8.12.2.1 Test Purpose and Environment ......................................................................................................... 1417
A.8.12.2.2 Test Requirements ............................................................................................................................. 1420
A.8.13 RSTD Inter-frequency Measurements .......................................................................................................... 1421
A.8.13.1 E-UTRAN FDD-FDD inter-frequency RSTD measurement reporting delay test case with the
reference cell on the serving carrier frequency ....................................................................................... 1421
A.8.13.1.1 Test Purpose and Environment ......................................................................................................... 1421
A.8.13.1.2 Test Requirements ............................................................................................................................. 1424
A.8.13.2 E-UTRAN TDD-TDD inter-frequency RSTD measurement reporting delay test case with the
reference cell on the serving carrier frequency ....................................................................................... 1425
A.8.13.2.1 Test Purpose and Environment ......................................................................................................... 1425
A.8.13.2.2 Test Requirements ............................................................................................................................. 1428
A.8.14 E-UTRAN TDD - FDD Inter-frequency Measurements .............................................................................. 1429
A.8.14.1 E-UTRAN TDD-FDD Inter-frequency event triggered reporting under fading propagation
conditions in asynchronous cells ............................................................................................................ 1429
A.8.14.1.1 Test Purpose and Environment ......................................................................................................... 1429
A.8.14.1.2 Test Requirements ............................................................................................................................. 1431
A.8.14.2 E-UTRAN TDD-FDD Inter-frequency event triggered reporting when DRX is used under fading
propagation conditions in asynchronous cells ........................................................................................ 1431
A.8.14.2.1 Test Purpose and Environment ......................................................................................................... 1431
A.8.14.2.2 Test Requirements ............................................................................................................................. 1434
A.8.14.3 E-UTRAN TDD - FDD Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps .................................................................................................................................... 1434
A.8.14.3.1 Test Purpose and Environment ......................................................................................................... 1434
A.8.14.3.2 Test Requirements ............................................................................................................................. 1436
A.8.15 E-UTRAN FDD - TDD Inter-frequency Measurements .............................................................................. 1437
A.8.15.1 E-UTRAN FDD-TDD Inter-frequency event triggered reporting under fading propagation
conditions in asynchronous cells ............................................................................................................ 1437
A.8.15.1.1 Test Purpose and Environment ......................................................................................................... 1437
A.8.15.1.2 Test Requirements ............................................................................................................................. 1438
A.8.15.2 E-UTRAN FDD-TDD Inter-frequency event triggered reporting when DRX is used under fading
propagation conditions in asynchronous cells ........................................................................................ 1438
A.8.15.2.1 Test Purpose and Environment ......................................................................................................... 1438
A.8.15.2.2 Test Requirements ............................................................................................................................. 1441
A.8.15.3 E-UTRAN FDD - TDD Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps .................................................................................................................................... 1441
A.8.15.3.1 Test Purpose and Environment ......................................................................................................... 1441
A.8.15.3.2 Test Requirements ............................................................................................................................. 1443
A.8.16 E-UTRAN Carrier Aggregation Measurements ........................................................................................... 1444
A.8.16.1 E-UTRAN FDD event triggered reporting under deactivated SCell in non-DRX .................................. 1444
A.8.16.1.1 Test Purpose and Environment ......................................................................................................... 1444
A.8.16.1.2 Test Requirements ............................................................................................................................. 1446
A.8.16.2 E-UTRAN TDD event triggered reporting under deactivated SCell in non-DRX.................................. 1447
A.8.16.2.1 Test Purpose and Environment ......................................................................................................... 1447
A.8.16.2.2 Test Requirements ............................................................................................................................. 1449
A.8.16.3 E-UTRAN FDD-FDD Event triggered reporting on deactivated SCell with PCell interruption in
non-DRX ................................................................................................................................................ 1450
A.8.16.3.1 Test Purpose and Environment ......................................................................................................... 1450
A.8.16.3.2 Test Requirements ............................................................................................................................. 1451
A.8.16.4 E-UTRAN TDD-TDD Event triggered reporting on deactivated SCell with PCell interruption in
non-DRX ................................................................................................................................................ 1452
A.8.16.4.1 Test Purpose and Environment ......................................................................................................... 1452
A.8.16.4.2 Test Requirements ............................................................................................................................. 1453
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 42 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.16.5 E-UTRAN FDD event triggered reporting under deactivated SCell in non-DRX for 20 MHz
bandwidth ............................................................................................................................................... 1454
A.8.16.5.1 Test Purpose and Environment ......................................................................................................... 1454
A.8.16.5.2 Test Requirements ............................................................................................................................. 1454
A.8.16.6 E-UTRAN TDD event triggered reporting under deactivated SCell in non-DRX for 20 MHz
bandwidth ............................................................................................................................................... 1455
A.8.16.6.1 Test Purpose and Environment ......................................................................................................... 1455
A.8.16.6.2 Test Requirements ............................................................................................................................. 1455
A.8.16.7 E-UTRA FDD event triggered reporting on deactivated SCell with PCell interruption in non-DRX
for 20 MHz bandwidth ............................................................................................................................ 1455
A.8.16.7.1 Test Purpose and Environment ......................................................................................................... 1455
A.8.16.7.2 Test Requirements ............................................................................................................................. 1456
A.8.16.8 E-UTRA TDD event triggered reporting on deactivated SCell with PCell interruption in non-DRX
for 20 MHz bandwidth ............................................................................................................................ 1456
A.8.16.8.1 Test Purpose and Environment ......................................................................................................... 1456
A.8.16.8.2 Test Requirements ............................................................................................................................. 1457
A.8.16.9 E-UTRAN FDD event triggered reporting under deactivated SCell in non-DRX for 10MHz+5MHz... 1457
A.8.16.9.1 Test Purpose and Environment ......................................................................................................... 1457
A.8.16.9.2 Test Requirements ............................................................................................................................. 1458
A.8.16.10 E-UTRAN TDD event triggered reporting under deactivated SCell in non-DRX for 10MHz+5MHz .. 1458
A.8.16.10.1 Test Purpose and Environment ......................................................................................................... 1458
A.8.16.10.2 Test Requirements ............................................................................................................................. 1459
A.8.16.11 E-UTRAN FDD event triggered reporting on deactivating SCell with PCell interruption in non-DRX
for 10MHz+5MHz .................................................................................................................................. 1459
A.8.16.11.1 Test Purpose and Environment ......................................................................................................... 1459
A.8.16.11.2 Test Requirements ............................................................................................................................. 1460
A.8.16.12 E-UTRAN TDD event triggered reporting on deactivating SCell with PCell interruption in non-
DRX for 10MHz+5MHz......................................................................................................................... 1460
A.8.16.12.1 Test Purpose and Environment ......................................................................................................... 1460
A.8.16.12.2 Test Requirements ............................................................................................................................. 1460
A.8.16.13 E-UTRAN FDD event triggered reporting under deactivated SCell in non-DRX for 5MHz +5 MHz
bandwidth ............................................................................................................................................... 1461
A.8.16.13.1 Test Purpose and Environment ......................................................................................................... 1461
A.8.16.13.2 Test Requirements ............................................................................................................................. 1461
A.8.16.14 E-UTRAN TDD event triggered reporting under deactivated SCell in non-DRX for 5 MHz +5 MHz
bandwidth ............................................................................................................................................... 1461
A.8.16.14.1 Test Purpose and Environment ......................................................................................................... 1461
A.8.16.14.2 Test Requirements ............................................................................................................................. 1462
A.8.16.15 E-UTRA FDD event triggered reporting on deactivated SCell with PCell interruption in non-DRX
for 5 +5 MHz bandwidth ........................................................................................................................ 1462
A.8.16.15.1 Test Purpose and Environment ......................................................................................................... 1462
A.8.16.7.2 Test Requirements ............................................................................................................................. 1463
A.8.16.16 E-UTRA TDD event triggered reporting on deactivated SCell with PCell interruption in non-DRX
for 5+5 MHz bandwidth ......................................................................................................................... 1463
A.8.16.16.1 Test Purpose and Environment ......................................................................................................... 1463
A.8.16.16.2 Test Requirements ............................................................................................................................. 1463
A.8.16.17 E-UTRAN FDD activation and deactivation of known SCell in non-DRX ........................................... 1463
A.8.16.17.1 Test Purpose and Environment ......................................................................................................... 1463
A.8.16.17.2 Test Requirements ............................................................................................................................. 1465
A.8.16.17A E-UTRAN FDD activation and deactivation of known SCell in non-DRX for 20MHz ......................... 1466
A.8.16.17A.1 Test Purpose and Environment ......................................................................................................... 1466
A.8.16.17A.2 Test Requirements ............................................................................................................................. 1466
A.8.16.17B E-UTRAN FDD activation and deactivation of known SCell in non-DRX for 10MHz + 5MHz .......... 1466
A.8.16.17B.1 Test Purpose and Environment ......................................................................................................... 1466
A.8.16.17B.2 Test Requirements ............................................................................................................................. 1467
A.8.16.17C E-UTRAN FDD activation and deactivation of known SCell in non-DRX for 5MHz + 5MHz ............ 1467
A.8.16.17C.1 Test Purpose and Environment ......................................................................................................... 1467
A.8.16.17C.2 Test Requirements ............................................................................................................................. 1467
A.8.16.18 E-UTRAN TDD activation and deactivation of known SCell in non-DRX ........................................... 1467
A.8.16.18.1 Test Purpose and Environment ......................................................................................................... 1467
A.8.16.18.2 Test Requirements ............................................................................................................................. 1469
A.8.16.18A E-UTRAN TDD activation and deactivation of known SCell in non-DRX for 20MHz ........................ 1470
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 43 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.16.18A.1 Test Purpose and Environment ......................................................................................................... 1470
A.8.16.18A.2 Test Requirements ............................................................................................................................. 1470
A.8.16.18B E-UTRAN TDD activation and deactivation of known SCell in non-DRX for 10MHz + 5MHz .......... 1470
A.8.16.18B.1 Test Purpose and Environment ......................................................................................................... 1470
A.8.16.18B.2 Test Requirements ............................................................................................................................. 1471
A.8.16.18C E-UTRAN TDD activation and deactivation of known SCell in non-DRX for 5MHz + 5MHz ............ 1471
A.8.16.18C.1 Test Purpose and Environment ......................................................................................................... 1471
A.8.16.18C.2 Test Requirements ............................................................................................................................. 1471
A.8.16.18D E-UTRAN TDD activation and deactivation of known SCell in non-DRX for 20MHz + 10MHz ........ 1471
A.8.16.18D.1 Test Purpose and Environment ......................................................................................................... 1471
A.8.16.18D.2 Test Requirements ............................................................................................................................. 1472
A.8.16.19 E-UTRAN FDD activation and deactivation of unknown SCell in non-DRX ....................................... 1472
A.8.16.19.1 Test Purpose and Environment ......................................................................................................... 1472
A.8.16.19.2 Test Requirements ............................................................................................................................. 1474
A.8.16.19A E-UTRAN FDD activation and deactivation of unknown SCell in non-DRX for 20MHz ..................... 1474
A.8.16.19A.1 Test Purpose and Environment ......................................................................................................... 1474
A.8.16.19A.2 Test Requirements ............................................................................................................................. 1475
A.8.16.19B E-UTRAN FDD activation and deactivation of unknown SCell in non-DRX for 10MHz + 5MHz ...... 1475
A.8.16.19B.1 Test Purpose and Environment ......................................................................................................... 1475
A.8.16.19B.2 Test Requirements ............................................................................................................................. 1475
A.8.16.19C E-UTRAN FDD activation and deactivation of unknown SCell in non-DRX for 5MHz + 5MHz ........ 1475
A.8.16.19C.1 Test Purpose and Environment ......................................................................................................... 1475
A.8.16.19C.2 Test Requirements ............................................................................................................................. 1476
A.8.16.20 E-UTRAN TDD activation and deactivation of unknown SCell in non-DRX ....................................... 1476
A.8.16.20.1 Test Purpose and Environment ......................................................................................................... 1476
A.8.16.20.2 Test Requirements ............................................................................................................................. 1478
A.8.16.20A E-UTRAN TDD activation and deactivation of unknown SCell in non-DRX for 20MHz .................... 1479
A.8.16.20A.1 Test Purpose and Environment ......................................................................................................... 1479
A.8.16.20A.2 Test Requirements ............................................................................................................................. 1479
A.8.16.20B E-UTRAN TDD activation and deactivation of unknown SCell in non-DRX for 10MHz + 5MHz ...... 1479
A.8.16.20B.1 Test Purpose and Environment ......................................................................................................... 1479
A.8.16.20B.2 Test Requirements ............................................................................................................................. 1480
A.8.16.20C E-UTRAN TDD activation and deactivation of unknown SCell in non-DRX for 5MHz + 5MHz ........ 1480
A.8.16.20C.1 Test Purpose and Environment ......................................................................................................... 1480
A.8.16.20C.2 Test Requirements ............................................................................................................................. 1480
A.8.16.20D E-UTRAN TDD activation and deactivation of unknown SCell in non-DRX for 20MHz + 10MHz .... 1480
A.8.16.20D.1 Test Purpose and Environment ......................................................................................................... 1480
A.8.16.20D.2 Test Requirements ............................................................................................................................. 1481
A.8.16.21 E-UTRAN TDD event triggered reporting under deactivated SCell in non-DRX for 20MHz+10MHz 1481
A.8.16.21.1 Test Purpose and Environment ......................................................................................................... 1481
A.8.16.21.2 Test Requirements ............................................................................................................................. 1483
A.8.16.22 E-UTRAN TDD event triggered reporting on deactivating SCell with PCell interruption in non-
DRX for 20MHz+10MHz....................................................................................................................... 1483
A.8.16.22.1 Test Purpose and Environment ......................................................................................................... 1483
A.8.16.22.2 Test Requirements ............................................................................................................................. 1484
A.8.16.23 E-UTRAN TDD-FDD CA Event Triggered Reporting Under Deactivated SCell in Non-DRX with
PCell in FDD .......................................................................................................................................... 1484
A.8.16.23.1 Test Purpose and Environment ......................................................................................................... 1484
A.8.16.23.2 Test Requirements ............................................................................................................................. 1487
A.8.16.24 E-UTRAN TDD-FDD CA Event Triggered Reporting Under Deactivated SCell in Non-DRX with
PCell in TDD .......................................................................................................................................... 1487
A.8.16.24.1 Test Purpose and Environment ......................................................................................................... 1487
A.8.16.24.2 Test Requirements ............................................................................................................................. 1490
A.8.16.25 E-UTRAN TDD-FDD CA Event triggered reporting on deactivated SCell with PCell interruption in
non-DRX with PCell in FDD .................................................................................................................. 1490
A.8.16.25.1 Test Purpose and Environment ......................................................................................................... 1490
A.8.16.25.2 Test Requirements ............................................................................................................................. 1492
A.8.16.26 E-UTRAN TDD-FDD CA Event triggered reporting on deactivated SCell with PCell interruption in
non-DRX with PCell in TDD ................................................................................................................. 1492
A.8.16.26.1 Test Purpose and Environment ......................................................................................................... 1492
A.8.16.26.2 Test Requirements ............................................................................................................................. 1495
A.8.16.27 3 DL PCell in FDD CA Event Triggered Reporting with 2 Deactivated SCells in Non-DRX ............... 1495
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 44 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.16.27.1 Test Purpose and Environment ......................................................................................................... 1495
A.8.16.27.2 Test Requirements ............................................................................................................................. 1499
A.8.16.28 3 DL PCell in TDD CA Event Triggered Reporting with 2 Deactivated SCells in Non-DRX ............... 1499
A.8.16.28.1 Test Purpose and Environment ......................................................................................................... 1499
A.8.16.28.2 Test Requirements ............................................................................................................................. 1503
A.8.16.29 3 DL FDD CA Event Triggered Reporting under Deactivated SCells in Non-DRX .............................. 1503
A.8.16.29.1 Test Purpose and Environment ......................................................................................................... 1503
A.8.16.29.2 Test Requirements ............................................................................................................................. 1507
A.8.16.30 3 DL TDD CA Event Triggered Reporting under Deactivated SCells in Non-DRX.............................. 1507
A.8.16.30.1 Test Purpose and Environment ......................................................................................................... 1507
A.8.16.30.2 Test Requirements ............................................................................................................................. 1511
A.8.16.31 E-UTRAN TDD-FDD 3 DL CA Event Triggered Reporting on Deactivated SCell with PCell and
SCell Interruptions in Non-DRX and with PCell in FDD ....................................................................... 1511
A.8.16.31.1 Test Purpose and Environment ......................................................................................................... 1511
A.8.16.31.2 Test Requirements ............................................................................................................................. 1515
A.8.16.32 E-UTRAN TDD-FDD 3 DL CA Event Triggered Reporting on Deactivated SCell with PCell and
SCell Interruptions in Non-DRX and with PCell in TDD ...................................................................... 1515
A.8.16.32.1 Test Purpose and Environment ......................................................................................................... 1515
A.8.16.32.2 Test Requirements ............................................................................................................................. 1519
A.8.16.33 E-UTRAN FDD 3 DL CA Event Triggered Reporting on Deactivated SCell with PCell and SCell
Interruptions in Non-DRX ...................................................................................................................... 1519
A.8.16.33.1 Test Purpose and Environment ......................................................................................................... 1519
A.8.16.33.2 Test Requirements ............................................................................................................................. 1523
A.8.16.34 E-UTRAN TDD 3 DL CA Event Triggered Reporting on Deactivated SCell with PCell and SCell
Interruptions in Non-DRX ...................................................................................................................... 1523
A.8.16.34.1 Test Purpose and Environment ......................................................................................................... 1523
A.8.16.34.2 Test Requirements ............................................................................................................................. 1527
A.8.16.35 3 DL PCell in FDD CA Activation and Deactivation of Known SCell in Non-DRX ............................ 1527
A.8.16.35.1 Test Purpose and Environment ......................................................................................................... 1527
A.8.16.35.2 Test Requirements ............................................................................................................................. 1529
A.8.16.36 3 DL PCell in TDD CA Activation and Deactivation of Known SCell in Non-DRX ............................ 1530
A.8.16.36.1 Test Purpose and Environment ......................................................................................................... 1530
A.8.16.36.2 Test Requirements ............................................................................................................................. 1532
A.8.16.37 3 DL FDD CA activation and deactivation of known SCell in non-DRX .............................................. 1533
A.8.16.37.1 Test Purpose and Environment ......................................................................................................... 1533
A.8.16.37.2 Test Requirements ............................................................................................................................. 1535
A.8.16.38 3 DL TDD CA activation and deactivation of known SCell in non-DRX .............................................. 1536
A.8.16.38.1 Test Purpose and Environment ......................................................................................................... 1536
A.8.16.38.2 Test Requirements ............................................................................................................................. 1538
A.8.16.39 E-UTRA TDD-FDD 3DL CA Activation and Deactivation of Unknown SCell in Non-DRX with
PCell in FDD .......................................................................................................................................... 1539
A.8.16.39.1 Test Purpose and Environment ......................................................................................................... 1539
A.8.16.39.2 Test Requirements ............................................................................................................................. 1542
A.8.16.40 E-UTRA TDD-FDD 3DL CA Activation and Deactivation of Unknown SCell in Non-DRX with
PCell in TDD .......................................................................................................................................... 1542
A.8.16.40.1 Test Purpose and Environment ......................................................................................................... 1542
A.8.16.40.2 Test Requirements ............................................................................................................................. 1545
A.8.16.41 3 DL FDD CA activation and deactivation of unknown SCell in non-DRX .......................................... 1545
A.8.16.41.1 Test Purpose and Environment ......................................................................................................... 1545
A.8.16.41.2 Test Requirements ....................................................................................................................... 1547
A.8.16.42 3 DL TDD CA activation and deactivation of unknown SCell in non-DRX .......................................... 1548
A.8.16.42.1 Test Purpose and Environment ......................................................................................................... 1548
A.8.16.42.2 Test Requirements ....................................................................................................................... 1550
A.8.16.43 E-UTRAN TDD-FDD CA activation and deactivation of known SCell in non-DRX with PCell in
FDD ........................................................................................................................................................ 1551
A.8.16.43.1 Test Purpose and Environment ......................................................................................................... 1551
A.8.16.43.2 Test Requirements ............................................................................................................................. 1554
A.8.16.44 E-UTRAN TDD-FDD CA activation and deactivation of unknown SCell in non-DRX with PCell in
FDD ........................................................................................................................................................ 1554
A.8.16.44.1 Test Purpose and Environment ......................................................................................................... 1554
A.8.16.44.2 Test Requirements ............................................................................................................................. 1557
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 45 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.16.45 E-UTRAN TDD-FDD CA activation and deactivation of known SCell in non-DRX with PCell in
TDD ........................................................................................................................................................ 1557
A.8.16.45.1 Test Purpose and Environment ......................................................................................................... 1557
A.8.16.45.2 Test Requirements ............................................................................................................................. 1560
A.8.16.46 E-UTRAN TDD-FDD CA activation and deactivation of unknown SCell in non-DRX with PCell in
TDD ........................................................................................................................................................ 1560
A.8.16.46.1 Test Purpose and Environment ......................................................................................................... 1560
A.8.16.46.2 Test Requirements ............................................................................................................................. 1562
A.8.16.47 2DL/2UL FDD CA activation and deactivation of known PUCCH SCell without valid TA in non-
DRX ........................................................................................................................................................ 1563
A.8.16.47.1 Test Purpose and Environment ......................................................................................................... 1563
A.8.16.47.2 Test Requirements ............................................................................................................................. 1565
A.8.16.48 2DL/2UL TDD CA activation and deactivation of known PUCCH SCell without valid TA in non-
DRX ........................................................................................................................................................ 1566
A.8.16.48.1 Test Purpose and Environment ......................................................................................................... 1566
A.8.16.48.2 Test Requirements ............................................................................................................................. 1568
A.8.16.49 2DL/2UL TDD-FDD CA (FDD PCell) activation and deactivation of known PUCCH SCell without
valid TA in non-DRX ............................................................................................................................. 1569
A.8.16.49.1 Test Purpose and Environment ......................................................................................................... 1569
A.8.16.49.2 Test Requirements ............................................................................................................................. 1572
A.8.16.50 2DL/2UL TDD-FDD CA (TDD PCell) activation and deactivation of known PUCCH SCell without
valid TA in non-DRX ............................................................................................................................. 1572
A.8.16.50.1 Test Purpose and Environment ......................................................................................................... 1572
A.8.16.50.2 Test Requirements ............................................................................................................................. 1574
A.8.16.51 E-UTRAN 4 DL FDD CA Event Triggered Reporting with 3 deactivated SCells in Non-DRX ........... 1575
A.8.16.51.1 Test Purpose and Environment ......................................................................................................... 1575
A.8.16.51.2 Test Requirements ............................................................................................................................. 1579
A.8.16.52 E-UTRAN 4 DL TDD CA Event Triggered Reporting with 3 deactivated SCells in Non-DRX ........... 1579
A.8.16.52.1 Test Purpose and Environment ......................................................................................................... 1579
A.8.16.52.2 Test Requirements ............................................................................................................................. 1583
A.8.16.53 4 DL PCell in FDD CA Event Triggered Reporting with 3 Deactivated SCells in Non-DRX ............... 1583
A.8.16.53.1 Test Purpose and Environment ......................................................................................................... 1583
A.8.16.53.2 Test Requirements ............................................................................................................................. 1587
A.8.16.54 4 DL PCell in TDD CA Event Triggered Reporting with 3 Deactivated SCells in Non-DRX ............... 1587
A.8.16.54.1 Test Purpose and Environment ......................................................................................................... 1587
A.8.16.54.2 Test Requirements ............................................................................................................................. 1591
A.8.16.55 E-UTRAN FDD 4 DL CA Event Triggered Reporting on Deactivated SCell with PCell and SCell
Interruptions in Non-DRX ...................................................................................................................... 1591
A.8.16.55.1 Test Purpose and Environment ......................................................................................................... 1591
A.8.16.55.2 Test Requirements ............................................................................................................................. 1596
A.8.16.56 E-UTRAN TDD 4 DL CA Event Triggered Reporting on Deactivated SCell with PCell and SCell
Interruptions in Non-DRX ...................................................................................................................... 1596
A.8.16.56.1 Test Purpose and Environment ......................................................................................................... 1596
A.8.16.56.2 Test Requirements ............................................................................................................................. 1601
A.8.16.57 E-UTRAN FDD 4DL CA activation and deactivation of know SCell in non-DRX ............................... 1601
A.8.16.57.1 Test Purpose and Environment ......................................................................................................... 1601
A.8.16.57.2 Test Requirements ............................................................................................................................. 1604
A.8.16.58 E-UTRAN TDD 4DL CA activation and deactivation of know SCell in non-DRX .............................. 1604
A.8.16.58.1 Test Purpose and Environment ......................................................................................................... 1604
A.8.16.58.2 Test Requirements ............................................................................................................................. 1606
A.8.16.59 E-UTRAN PCell in FDD FDD-TDD 4 DL CA activation and deactivation of known SCell in non-
DRX ........................................................................................................................................................ 1607
A.8.16.59.1 Test Purpose and Environment ......................................................................................................... 1607
A.8.16.59.2 Test Requirements ............................................................................................................................. 1610
A.8.16.60 E-UTRAN PCell in TDD FDD-TDD 4 DL CA activation and deactivation of known SCell in non-
DRX ........................................................................................................................................................ 1611
A.8.16.60.1 Test Purpose and Environment ......................................................................................................... 1611
A.8.16.60.2 Test Requirements ............................................................................................................................. 1615
A.8.16.61 E-UTRAN FDD 4DL CA activation and deactivation of unknown SCell in non-DRX ......................... 1615
A.8.16.61.1 Test Purpose and Environment ......................................................................................................... 1615
A.8.16.61.2 Test Requirements ............................................................................................................................. 1618
A.8.16.62 E-UTRAN TDD 4DL CA activation and deactivation of unknown SCell in non-DRX ........................ 1618
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 46 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.16.62.1 Test Purpose and Environment ......................................................................................................... 1618
A.8.16.62.2 Test Requirements ............................................................................................................................. 1621
A.8.16.63 E-UTRAN PCell in FDD FDD-TDD 4 DL CA activation and deactivation of unknown SCell in
non-DRX ................................................................................................................................................ 1621
A.8.16.63.1 Test Purpose and Environment ......................................................................................................... 1621
A.8.16.63.2 Test Requirements ............................................................................................................................. 1624
A.8.16.64 E-UTRAN PCell in TDD FDD-TDD 4 DL CA activation and deactivation of unknown SCell in
non-DRX ................................................................................................................................................ 1625
A.8.16.64.1 Test Purpose and Environment ......................................................................................................... 1625
A.8.16.64.2 Test Requirements ............................................................................................................................. 1629
A.8.16.65 5 DL PCell in FDD CA Event Triggered Reporting with 4 Deactivated SCells in Non-DRX ............... 1629
A.8.16.65.1 Test Purpose and Environment ......................................................................................................... 1629
A.8.16.65.2 Test Requirements ............................................................................................................................. 1634
A.8.16.67 5 DL PCell in FDD CA activation and deactivation of Unknown SCell in non-DRX ........................... 1634
A.8.16.67.1 Test Purpose and Environment ......................................................................................................... 1634
A.8.16.67.2 Test Requirements ............................................................................................................................. 1639
A.8.16.68 5 DL PCell in TDD CA activation and deactivation of Unknown SCell in non-DRX ........................... 1639
A.8.16.68.1 Test Purpose and Environment ......................................................................................................... 1639
A.8.16.68.2 Test Requirements ............................................................................................................................. 1644
A.8.16.69 E-UTRAN FDD 5DL CA activation and deactivation of unknown SCell in non-DRX ......................... 1644
A.8.16.69.1 Test Purpose and Environment ......................................................................................................... 1644
A.8.16.69.2 Test Requirements ............................................................................................................................. 1647
A.8.16.70 E-UTRAN TDD 5DL CA activation and deactivation of unknown SCell in non-DRX ........................ 1647
A.8.16.70.1 Test Purpose and Environment ......................................................................................................... 1647
A.8.16.70.2 Test Requirements ............................................................................................................................. 1650
A.8.16.66 5 DL PCell in TDD CA Event Triggered Reporting with 4 Deactivated SCells in Non-DRX ............... 1650
A.8.16.66.1 Test Purpose and Environment ......................................................................................................... 1650
A.8.16.66.2 Test Requirements ............................................................................................................................. 1655
A.8.16.71 5 DL FDD CA Event Triggered Reporting with Deactivated SCells in Non-DRX ................................ 1655
A.8.16.71.1 Test Purpose and Environment ......................................................................................................... 1655
A.8.16.71.2 Test Requirements ............................................................................................................................. 1659
A.8.16.72 E-UTRAN 5 DL TDD CA Event Triggered Reporting with Deactivated SCells in Non-DRX ............. 1659
A.8.16.72.1 Test Purpose and Environment ......................................................................................................... 1659
A.8.16.72.2 Test Requirements ............................................................................................................................. 1663
A.8.16.73 E-UTRAN FDD 5 DL CA Event Triggered Reporting on Deactivated SCell with PCell and SCell
Interruptions in Non-DRX ...................................................................................................................... 1663
A.8.16.73.1 Test Purpose and Environment ......................................................................................................... 1663
A.8.16.73.2 Test Requirements ............................................................................................................................. 1668
A.8.16.74 E-UTRAN TDD 5 DL CA Event Triggered Reporting on Deactivated SCell with PCell and SCell
Interruptions in Non-DRX ...................................................................................................................... 1668
A.8.16.74.1 Test Purpose and Environment ......................................................................................................... 1668
A.8.16.74.2 Test Requirements ............................................................................................................................. 1673
A.8.16.75 5 DL PCell in FDD CA activation and deactivation of known SCell in non-DRX ................................ 1673
A.8.16.75.1 Test Purpose and Environment ......................................................................................................... 1673
A.8.16.75.2 Test Requirements ............................................................................................................................. 1678
A.8.16.76 5 DL PCell in TDD CA activation and deactivation of known SCell in non-DRX ................................ 1678
A.8.16.76.1 Test Purpose and Environment ......................................................................................................... 1678
A.8.16.76.2 Test Requirements ............................................................................................................................. 1683
A.8.16.77 E-UTRAN FDD 5DL CA activation and deactivation of know SCell in non-DRX ............................... 1683
A.8.16.77.1 Test Purpose and Environment ......................................................................................................... 1683
A.8.16.77.2 Test Requirements ............................................................................................................................. 1686
A.8.16.78 E-UTRAN TDD 5DL CA activation and deactivation of know SCell in non-DRX .............................. 1686
A.8.16.78.1 Test Purpose and Environment ......................................................................................................... 1686
A.8.16.78.2 Test Requirements ............................................................................................................................. 1689
A.8.17 RSTD Measurements for E-UTRAN Carrier Aggregation .......................................................................... 1690
A.8.17.1 E-UTRAN FDD RSTD measurement reporting delay test case ............................................................. 1690
A.8.17.1.1 Test Purpose and Environment ......................................................................................................... 1690
A.8.17.1.2 Test Requirements ............................................................................................................................. 1695
A.8.17.2 E-UTRAN TDD RSTD measurement reporting delay test case ............................................................. 1695
A.8.17.2.1 Test Purpose and Environment ......................................................................................................... 1695
A.8.17.2.2 Test Requirements ............................................................................................................................. 1701
A.8.17.3 E-UTRAN FDD RSTD Measurement Reporting Test Case for 20 MHz ............................................... 1701
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 47 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.17.3.1 Test Purpose and Environment ......................................................................................................... 1701
A.8.17.3.2 Test Requirements ............................................................................................................................. 1702
A.8.17.4 E-UTRAN TDD RSTD Measurement Reporting Test Case for 20 MHz ............................................... 1702
A.8.17.4.1 Test Purpose and Environment ......................................................................................................... 1702
A.8.17.4.2 Test Requirements ............................................................................................................................. 1703
A.8.17.5 E-UTRAN FDD RSTD Measurement Reporting Test Case for 10MHz+5MHz.................................... 1703
A.8.17.5.1 Test Purpose and Environment ......................................................................................................... 1703
A.8.17.5.2 Test Requirements ............................................................................................................................. 1704
A.8.17.6 E-UTRAN TDD RSTD Measurement Reporting Test Case for 10MHz+5MHz ................................... 1704
A.8.17.6.1 Test Purpose and Environment ......................................................................................................... 1704
A.8.17.6.2 Test Requirements ............................................................................................................................. 1705
A.8.17.7 E-UTRAN FDD RSTD Measurement Reporting Test Case for 5 + 5 MHz Bandwidth ........................ 1705
A.8.17.7.1 Test Purpose and Environment ......................................................................................................... 1705
A.8.17.7.2 Test Requirements ............................................................................................................................. 1706
A.8.17.8 E-UTRAN TDD RSTD Measurement Reporting Test Case for 5+5 MHz bandwidth ........................... 1706
A.8.17.8.1 Test Purpose and Environment ......................................................................................................... 1706
A.8.17.8.2 Test Requirements ............................................................................................................................. 1707
A.8.17.9 E-UTRAN TDD RSTD Measurement Reporting Test Case for 20MHz+10MHz ................................. 1707
A.8.17.9.1 Test Purpose and Environment ......................................................................................................... 1707
A.8.17.9.2 Test Requirements ............................................................................................................................. 1708
A.8.17.10 E-UTRAN 3 DL FDD CA RSTD Measurement Reporting Delay Test Case ........................................ 1709
A.8.17.10.1 Test Purpose and Environment ......................................................................................................... 1709
A.8.17.10.2 Test Requirements ............................................................................................................................. 1714
A.8.17.11 E-UTRAN 3 DL TDD CA RSTD Measurement Reporting Delay Test Case ........................................ 1715
A.8.17.11.1 Test Purpose and Environment ......................................................................................................... 1715
A.8.17.11.2 Test Requirements ............................................................................................................................. 1721
A.8.18 E-UTRAN TDD – HRPD Measurements .................................................................................................... 1722
A.8.18.1 E-UTRAN TDD-HRPD event triggered reporting under fading propagation conditions ....................... 1722
A.8.18.1.1 Test Purpose and Environment ......................................................................................................... 1722
A.8.18.1.2 Test Requirements ............................................................................................................................. 1725
A.8.19 E-UTRAN TDD – CDMA2000 1X Measurements ..................................................................................... 1725
A.8.19.1 E-UTRAN TDD – CDMA2000 1X event triggered reporting under fading propagation conditions ..... 1725
A.8.19.1.1 Test Purpose and Environment ......................................................................................................... 1725
A.8.19.1.2 Test Requirements ............................................................................................................................. 1727
A.8.20 Inter-frequency/RAT Measurements in CA mode ....................................................................................... 1728
A.8.20.1 E-UTRAN FDD-FDD Inter-frequency event triggered reporting under fading propagation
conditions in asynchronous cells ............................................................................................................ 1728
A.8.20.1.1 Test Purpose and Environment ......................................................................................................... 1728
A.8.20.1.2 Test Requirements ............................................................................................................................. 1729
A.8.20.2 E-UTRAN TDD-TDD Inter-frequency event triggered reporting under fading propagation
conditions in synchronous cells .............................................................................................................. 1730
A.8.20.2.1 Test Purpose and Environment ......................................................................................................... 1730
A.8.20.2.2 Test Requirements ............................................................................................................................. 1731
A.8.20.2A E-UTRAN TDD-TDD Inter-frequency event triggered reporting under fading propagation
conditions in synchronous cells for 20 MHz +20 MHz bandwidth. ....................................................... 1732
A.8.20.2A.1 Test Purpose and Environment ......................................................................................................... 1732
A.8.20.2A.2 Test Requirements ............................................................................................................................. 1732
A.8.20.2B E-UTRAN TDD-TDD Inter-frequency event triggered reporting under fading propagation
conditions in synchronous cells for 20 MHz +10 MHz bandwidth. ....................................................... 1732
A.8.20.2B.1 Test Purpose and Environment ......................................................................................................... 1732
A.8.20.2B.2 Test Requirements ............................................................................................................................. 1735
A.8.20.3 E-UTRAN FDD - UTRAN FDD event triggered reporting under fading propagation conditions ......... 1735
A.8.20.3.1 Test Purpose and Environment ......................................................................................................... 1735
A.8.20.3.2 Test Requirements ............................................................................................................................. 1737
A.8.20.4 E-UTRAN TDD to UTRAN TDD cell search under fading propagation conditions ............................. 1737
A.8.20.4.1 Test Purpose and Environment ......................................................................................................... 1737
A.8.20.4.1.1 1.28 Mcps TDD option ................................................................................................................ 1737
A.8.20.4.2 Test Requirements ............................................................................................................................. 1740
A.8.20.4.2.1 1.28 Mcps TDD option ................................................................................................................ 1740
A.8.20.4A E-UTRAN TDD with 20 MHz +20 MHz bandwidth to UTRAN TDD cell search under fading
propagation conditions ............................................................................................................................ 1740
A.8.20.4A.1 Test Purpose and Environment ......................................................................................................... 1740
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 48 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.20.4A.1.1 1.28 Mcps TDD option ................................................................................................................ 1740
A.8.20.4A.2 Test Requirements ............................................................................................................................. 1740
A.8.20.4A.2.1 1.28 Mcps TDD option ................................................................................................................ 1740
A.8.20.4B E-UTRAN TDD with 20 MHz +10 MHz bandwidth to UTRAN TDD cell search under fading
propagation conditions ............................................................................................................................ 1741
A.8.20.4B.1 Test Purpose and Environment ......................................................................................................... 1741
A.8.20.4B.1.1 1.28 Mcps TDD option ................................................................................................................ 1741
A.8.20.4B.2 Test Requirements ............................................................................................................................. 1743
A.8.20.4B.2.1 1.28 Mcps TDD option ................................................................................................................ 1743
A.8.21 CSG Proximity Indication Testing Case for E-UTRAN FDD – FDD Inter frequency ................................ 1743
A.8.21.1 Test Purpose and Environment ......................................................................................................... 1743
A.8.21.2 Test Requirements .......................................................................................................................................... 1747
A.8.22 E-UTRAN Discovery Signal Measurements ................................................................................................ 1747
A.8.22.1 E-UTRAN FDD-FDD intra-frequency event triggered reporting under fading propagation conditions
in synchronous cells in DRX based on CRS based discovery signal ...................................................... 1747
A.8.22.1.1 Test Purpose and Environment ......................................................................................................... 1747
A.8.22.1.2 Test Requirements ............................................................................................................................. 1750
A.8.22.2 E-UTRAN TDD-TDD intra-frequency event triggered reporting under fading propagation
conditions in synchronous cells in DRX based on CRS based discovery signal .................................... 1750
A.8.22.2.1 Test Purpose and Environment ......................................................................................................... 1750
A.8.22.2.2 Test Requirements ............................................................................................................................. 1753
A.8.22.3 E-UTRAN FDD-FDD inter-frequency event triggered reporting under fading propagation conditions
in DRX based on CRS based discovery signal ....................................................................................... 1753
A.8.22.3.1 Test Purpose and Environment ......................................................................................................... 1753
A.8.22.3.2 Test Requirements ............................................................................................................................. 1756
A.8.22.4 E-UTRAN TDD-TDD inter-frequency event triggered reporting under fading propagation
conditions in DRX based on CRS based discovery signal ...................................................................... 1756
A.8.22.4.1 Test Purpose and Environment ......................................................................................................... 1756
A.8.22.4.2 Test Requirements ............................................................................................................................. 1759
A.8.22.5 E-UTRAN FDD-FDD intra-frequency event triggered reporting in DRX based on CSI-RS based
discovery signal ...................................................................................................................................... 1759
A.8.22.5.1 Test Purpose and Environment ......................................................................................................... 1759
A.8.22.5.2 Test Requirements ............................................................................................................................. 1762
A.8.22.6 E-UTRAN TDD-TDD intra-frequency event triggered reporting in DRX based on CSI-RS based
discovery signal ...................................................................................................................................... 1762
A.8.22.6.1 Test Purpose and Environment ......................................................................................................... 1762
A.8.22.6.2 Test Requirements ............................................................................................................................. 1765
A.8.22.7 E-UTRAN FDD-FDD Inter-frequency event triggered reporting in DRX based on CSI-RS based
discovery signal ...................................................................................................................................... 1765
A.8.22.7.1 Test Purpose and Environment ......................................................................................................... 1765
A.8.22.7.2 Test Requirements ............................................................................................................................. 1768
A.8.22.8 E-UTRAN TDD-TDD inter-frequency event triggered reporting under fading propagation condition
in DRX based on CSI-RS based discovery signal .................................................................................. 1768
A.8.22.8.1 Test Purpose and Environment ......................................................................................................... 1768
A.8.22.8.2 Test Requirements ............................................................................................................................. 1771
A.8.22.9 E-UTRAN FDD event triggered reporting under deactivated SCell in non-DRX based on CRS based
discovery signal ...................................................................................................................................... 1771
A.8.22.9.1 Test Purpose and Environment ......................................................................................................... 1771
A.8.22.9.2 Test Requirements ............................................................................................................................. 1773
A.8.22.10 E-UTRAN TDD event triggered reporting under deactivated SCell in non-DRX based on CRS based
discovery signal ...................................................................................................................................... 1774
A.8.22.10.1 Test Purpose and Environment ......................................................................................................... 1774
A.8.22.10.2 Test Requirements ............................................................................................................................. 1776
A.8.22.11 E-UTRAN FDD event triggered reporting under deactivated SCell in non-DRX based on CSI-RS
based discovery signal ............................................................................................................................ 1777
A.8.22.11.1 Test Purpose and Environment ......................................................................................................... 1777
A.8.22.11.2 Test Requirements ............................................................................................................................. 1779
A.8.22.12 E-UTRAN TDD event triggered reporting under deactivated SCell in non-DRX based on CSI-RS
based discovery signal ............................................................................................................................ 1779
A.8.22.12.1 Test Purpose and Environment ......................................................................................................... 1779
A.8.22.12.2 Test Requirements ............................................................................................................................. 1782
A.8.23 E-UTRAN Dual Connectivity Measurements .............................................................................................. 1782
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 49 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.23.1 E-UTRAN FDD-FDD DC intra-frequency event triggered reporting with DRX in synchronous DC ... 1782
A.8.23.1.1 Test Purpose and Environment ......................................................................................................... 1782
A.8.23.1.2 Test Requirements ............................................................................................................................. 1785
A.8.23.2 E-UTRAN FDD-FDD DC intra-frequency event triggered reporting with DRX in asynchronous DC . 1785
A.8.23.2.1 Test Purpose and Environment ......................................................................................................... 1785
A.8.23.2.2 Test Requirements ............................................................................................................................. 1788
A.8.23.3 E-UTRAN TDD-TDD DC intra-frequency event triggered reporting with DRX in synchronous DC ... 1788
A.8.23.3.1 Test Purpose and Environment ......................................................................................................... 1788
A.8.23.3.2 Test Requirements ............................................................................................................................. 1791
A.8.23.4 E-UTRAN FDD-FDD DC inter-frequency event triggered reporting with DRX in synchronous DC ... 1791
A.8.23.4.1 Test Purpose and Environment ......................................................................................................... 1791
A.8.23.4.2 Test Requirements ............................................................................................................................. 1794
A.8.23.5 E-UTRAN FDD-FDD DC inter-frequency event triggered reporting with DRX in asynchronous DC . 1794
A.8.23.5.1 Test Purpose and Environment ......................................................................................................... 1794
A.8.23.5.2 Test Requirements ............................................................................................................................. 1797
A.8.23.6 E-UTRAN TDD-TDD DC inter-frequency event triggered reporting with DRX in synchronous DC ... 1797
A.8.23.6.1 Test Purpose and Environment ......................................................................................................... 1797
A.8.23.6.2 Test Requirements ............................................................................................................................. 1800
A.8.23.7 E-UTRAN FDD-FDD Addition and Release Delay of known PSCell in Synchronous DC .................. 1800
A.8.23.7.1 Test Purpose and Environment ......................................................................................................... 1800
A.8.23.7.2 Test Requirements ............................................................................................................................. 1803
A.8.23.8 E-UTRAN FDD-FDD Addition and Release Delay of known PSCell in Asynchronous DC ................ 1803
A.8.23.8.1 Test Purpose and Environment ......................................................................................................... 1803
A.8.23.8.2 Test Requirements ............................................................................................................................. 1805
A.8.23.9 E-UTRAN TDD Addition and Release Delay of known PSCell in Synchronous DC............................ 1806
A.8.23.9.1 Test Purpose and Environment ......................................................................................................... 1806
A.8.23.9.2 Test Requirements ............................................................................................................................. 1809
A.8.23.10 E-UTRAN TDD-FDD DC intra-frequency event triggered reporting with DRX in synchronous DC
with PCell in FDD .................................................................................................................................. 1809
A.8.23.10.1 Test Purpose and Environment ......................................................................................................... 1809
A.8.23.10.2 Test Requirements ............................................................................................................................. 1812
A.8.23.11 E-UTRAN TDD-FDD DC intra-frequency event triggered reporting with DRX in synchronous DC
with PCell in TDD .................................................................................................................................. 1812
A.8.23.11.1 Test Purpose and Environment ......................................................................................................... 1812
A.8.23.11.2 Test Requirements ............................................................................................................................. 1815
A.8.23.12 E-UTRAN TDD-FDD DC inter-frequency event triggered reporting with DRX in synchronous DC
with PCell in FDD .................................................................................................................................. 1815
A.8.23.12.1 Test Purpose and Environment ......................................................................................................... 1815
A.8.23.12.2 Test Requirements ............................................................................................................................. 1818
A.8.23.13 E-UTRAN TDD-FDD DC inter-frequency event triggered reporting with DRX in synchronous DC
with PCell in TDD .................................................................................................................................. 1818
A.8.23.13.1 Test Purpose and Environment ......................................................................................................... 1818
A.8.23.13.2 Test Requirements ............................................................................................................................. 1821
A.8.23.14 E-UTRAN TDD-FDD Addition and Release Delay of known PSCell in Synchronous DC with PCell
in FDD .................................................................................................................................................... 1821
A.8.23.14.1 Test Purpose and Environment ......................................................................................................... 1821
A.8.23.14.2 Test Requirements ............................................................................................................................. 1824
A.8.23.15 E-UTRAN TDD-FDD Addition and Release Delay of known PSCell in Synchronous DC with PCell
in TDD .................................................................................................................................................... 1824
A.8.23.15.1 Test Purpose and Environment ......................................................................................................... 1824
A.8.23.15.2 Test Requirements ............................................................................................................................. 1827
A.8.23.16 E-UTRAN FDD-FDD DC SSTD measurement reporting delay with no DRX in asynchronous DC .... 1827
A.8.23.16.1 Test Purpose and Environment ......................................................................................................... 1827
A.8.23.16.2 Test Requirements ............................................................................................................................. 1828
A.8.23.17 E-UTRAN FDD-FDD DC SSTD measurement reporting delay with DRX in asynchronous DC ......... 1829
A.8.23.17.1 Test Purpose and Environment ......................................................................................................... 1829
A.8.23.17.2 Test Requirements ............................................................................................................................. 1831
A.8.23.18 E-UTRAN FDD - FDD DC Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps in synchronous DC ..................................................................................................... 1831
A.8.23.18.1 Test Purpose and Environment ......................................................................................................... 1831
A.8.23.18.2 Test Requirements ............................................................................................................................. 1832
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 50 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.23.19 E-UTRAN FDD - FDD DC Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps in asynchronous DC ................................................................................................... 1833
A.8.23.19.1 Test Purpose and Environment ......................................................................................................... 1833
A.8.23.19.2 Test Requirements ............................................................................................................................. 1834
A.8.23.20 E-UTRAN TDD - TDD DC Intra-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps in synchronous DC ..................................................................................................... 1835
A.8.23.20.1 Test Purpose and Environment ......................................................................................................... 1835
A.8.23.20.2 Test Requirements ............................................................................................................................. 1836
A.8.23.21 E-UTRAN FDD - FDD DC Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps in synchronous DC ..................................................................................................... 1837
A.8.23.21.1 Test Purpose and Environment ......................................................................................................... 1837
A.8.23.21.2 Test Requirements ............................................................................................................................. 1838
A.8.23.22 E-UTRAN FDD - FDD DC Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps in asynchronous DC ................................................................................................... 1839
A.8.23.22.1 Test Purpose and Environment ......................................................................................................... 1839
A.8.23.22.2 Test Requirements ............................................................................................................................. 1840
A.8.23.23 E-UTRAN TDD - TDD DC Inter-frequency identification of a new CGI of E-UTRA cell using
autonomous gaps in synchronous DC ..................................................................................................... 1841
A.8.23.23.1 Test Purpose and Environment ......................................................................................................... 1841
A.8.23.23.2 Test Requirements ............................................................................................................................. 1843
A.8.23.24 E-UTRAN FDD-FDD DC activation and deactivation of known SCell in Non-DRX in synchronous
DC........................................................................................................................................................... 1844
A.8.23.24.1 Test Purpose and Environment ......................................................................................................... 1844
A.8.23.24.2 Test Requirements ............................................................................................................................. 1846
A.8.23.25 E-UTRAN FDD-FDD DC activation and deactivation of known SCell in Non-DRX in asynchronous
DC........................................................................................................................................................... 1847
A.8.23.25.1 Test Purpose and Environment ......................................................................................................... 1847
A.8.23.25.2 Test Requirements ............................................................................................................................. 1849
A.8.23.26 E-UTRAN TDD-TDD DC activation and deactivation of known SCell in Non-DRX in synchronous
DC........................................................................................................................................................... 1850
A.8.23.26.1 Test Purpose and Environment ......................................................................................................... 1850
A.8.23.26.2 Test Requirements ............................................................................................................................. 1852
A.8.23.27 E-UTRAN FDD-FDD DC event triggered reporting under deactivated SCell with PCell and PSCell
interruption in non-DRX in synchronous DC ......................................................................................... 1853
A.8.23.27.1 Test Purpose and Environment ......................................................................................................... 1853
A.8.23.27.2 Test Requirements ............................................................................................................................. 1856
A.8.23.28 E-UTRAN FDD-FDD DC event triggered reporting under deactivated SCell with PCell and PSCell
interruption in non-DRX in asynchronous DC ....................................................................................... 1856
A.8.23.28.1 Test Purpose and Environment ......................................................................................................... 1856
A.8.23.28.2 Test Requirements ............................................................................................................................. 1859
A.8.23.29 E-UTRAN TDD-TDD DC event triggered reporting under deactivated SCell with PCell and PSCell
interruption in non-DRX in synchronous DC ......................................................................................... 1859
A.8.23.29.1 Test Purpose and Environment ......................................................................................................... 1859
A.8.23.29.2 Test Requirements ............................................................................................................................. 1862
A.8.24 Proximity-based Services ............................................................................................................................. 1862
A.8.24.1 E-UTRAN FDD - Initiation/Cease of SLSS Transmission with ProSe Direct Discovery ...................... 1862
A.8.24.1.1 Test Purpose and Environment ......................................................................................................... 1863
A.8.24.1.2 Test Requirements ............................................................................................................................. 1864
A.8.24.2 E-UTRAN TDD - Initiation/Cease of SLSS Transmission with ProSe Direct Discovery...................... 1864
A.8.24.2.1 Test Purpose and Environment ......................................................................................................... 1865
A.8.24.2.2 Test Requirements ............................................................................................................................. 1866
A.8.24.3 E-UTRAN FDD - Initiation/Cease of SLSS Transmission with ProSe Direct Communication............. 1866
A.8.24.3.1 Test Purpose and Environment ......................................................................................................... 1867
A.8.24.3.2 Test Requirements ............................................................................................................................. 1868
A.8.25 E-UTRAN-WLAN Measurements ............................................................................................................... 1869
A.8.25.1 E-UTRAN FDD-WLAN Event Triggered Reporting in non-DRX under AWGN ................................. 1869
A.8.25.1.1 Test Purpose and Environment ......................................................................................................... 1869
A.8.25.1.2 Test Requirements ............................................................................................................................. 1871
A.8.25.2 E-UTRAN TDD-WLAN Event Triggered Reporting in non-DRX under AWGN................................. 1871
A.8.25.2.1 Test Purpose and Environment ......................................................................................................... 1871
A.8.25.2.2 Test Requirements ............................................................................................................................. 1873
A.8.26 1873
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 51 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.26.1 LAA SCell activation and deactivation of known SCell with E-UTRA FDD PCell in non-DRX ......... 1873
A.8.26.1.1 Test Purpose and Environment ......................................................................................................... 1873
A.8.26.1.2 Test Requirements ............................................................................................................................. 1875
A.8.26.2 LAA SCell activation and deactivation of known SCell with E-UTRA TDD PCell in non-DRX ......... 1876
A.8.26.2.1 Test Purpose and Environment ......................................................................................................... 1876
A.8.26.2.2 Test Requirements ............................................................................................................................. 1878
A.8.26.3 Event triggered reporting on LAA deactivated SCell and E-UTRAN FDD PCell interruption in non-
DRX ........................................................................................................................................................ 1879
A.8.26.3.1 Test Purpose and Environment ......................................................................................................... 1879
A.8.26.3.2 Test Requirements ............................................................................................................................. 1882
A.8.26.4 Event triggered reporting on LAA deactivated SCell and E-UTRAN TDD PCell interruption in non-
DRX ........................................................................................................................................................ 1882
A.8.26.4.1 Test Purpose and Environment ......................................................................................................... 1882
A.8.26.4.2 Test Requirements ............................................................................................................................. 1885
A.8.26.5 E-UTRAN FDD-TDD intra-frequency event triggered reporting in non-DRX for CRS based
discovery signal under Operation with Frame Structure 3 ...................................................................... 1885
A.8.26.5.1 Test Purpose and Environment ......................................................................................................... 1885
A.8.26.5.2 Test Requirements ............................................................................................................................. 1888
A.8.26.6 E-UTRAN TDD-TDD intra-frequency event triggered reporting in non-DRX for CRS based
discovery signal under Operation with Frame Structure 3 ...................................................................... 1888
A.8.26.6.1 Test Purpose and Environment ......................................................................................................... 1888
A.8.26.6.2 Test Requirements ............................................................................................................................. 1891
A.8.26.7 E-UTRAN FDD-TDD intra-frequency event triggered reporting in DRX for CRS based discovery
signal under Operation with Frame Structure 3 ...................................................................................... 1891
A.8.26.7.1 Test Purpose and Environment ......................................................................................................... 1891
A.8.26.7.2 Test Requirements ............................................................................................................................. 1894
A.8.26.8 E-UTRAN TDD-TDD intra-frequency event triggered reporting in DRX for CRS based discovery
signal under Operation with Frame Structure 3 ...................................................................................... 1894
A.8.26.8.1 Test Purpose and Environment ......................................................................................................... 1894
A.8.26.8.2 Test Requirements ............................................................................................................................. 1897
A.8.26.9 E-UTRAN FDD-FS3 inter-frequency event triggered reporting under fading propagation conditions
in synchronous cells ................................................................................................................................ 1897
A.8.26.9.1 Test Purpose and Environment ......................................................................................................... 1897
A.8.26.9.2 Test Requirements ............................................................................................................................. 1900
A.8.26.10 E-UTRAN TDD-FS3 inter-frequency event triggered reporting under fading propagation conditions
in synchronous cells ................................................................................................................................ 1900
A.8.26.10.1 Test Purpose and Environment ......................................................................................................... 1900
A.8.26.10.2 Test Requirements ............................................................................................................................. 1903
A.9 Measurement Performance Requirements..........................................................................................1904
A.9.1 RSRP ............................................................................................................................................................ 1904
A.9.1.1 FDD Intra frequency case ....................................................................................................................... 1904
A.9.1.1.1 Test Purpose and Environment ......................................................................................................... 1904
A.9.1.1.2 Test parameters ................................................................................................................................. 1904
A.9.1.1.3 Test Requirements ............................................................................................................................. 1906
A.9.1.2 TDD Intra frequency case ....................................................................................................................... 1906
A.9.1.2.1 Test Purpose and Environment ......................................................................................................... 1906
A.9.1.2.2 Test parameters ................................................................................................................................. 1906
A.9.1.2.3 Test Requirements ............................................................................................................................. 1907
A.9.1.3 FDD—FDD Inter frequency case ........................................................................................................... 1908
A.9.1.3.1 Test Purpose and Environment ......................................................................................................... 1908
A.9.1.3.2 Test parameters ................................................................................................................................. 1908
A.9.1.3.3 Test Requirements ............................................................................................................................. 1910
A.9.1.4 TDD—TDD Inter frequency case ........................................................................................................... 1910
A.9.1.4.1 Test Purpose and Environment ......................................................................................................... 1910
A.9.1.4.2 Test parameters ................................................................................................................................. 1910
A.9.1.4.3 Test Requirements ............................................................................................................................. 1912
A.9.1.5 FDD—TDD Inter frequency case ........................................................................................................... 1913
A.9.1.5.1 Test Purpose and Environment ......................................................................................................... 1913
A.9.1.5.2 Test parameters ................................................................................................................................. 1913
A.9.1.5.3 Test Requirements ............................................................................................................................. 1914
A.9.1.6 FDD RSRP for E-UTRAN Carrier Aggregation .................................................................................... 1915
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 52 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.1.6.1 Test Purpose and Environment ......................................................................................................... 1915
A.9.1.6.2 Test parameters ................................................................................................................................. 1915
A.9.1.6.3 Test Requirements ............................................................................................................................. 1917
A.9.1.7 TDD RSRP for E-UTRAN Carrier Aggregation .................................................................................... 1917
A.9.1.7.1 Test Purpose and Environment ......................................................................................................... 1917
A.9.1.7.2 Test parameters ................................................................................................................................. 1917
A.9.1.7.3 Test Requirements ............................................................................................................................. 1919
A.9.1.8 FDD RSRP under Time-Domain Measurement Resource Restriction with Non-MBSFN ABS ............ 1919
A.9.1.8.1 Test Purpose and Environment ......................................................................................................... 1919
A.9.1.8.2 Test parameters ................................................................................................................................. 1919
A.9.1.8.3 Test Requirements ............................................................................................................................. 1922
A.9.1.9 TDD RSRP under Time-Domain Measurement Resource Restriction with Non-MBSFN ABS............ 1922
A.9.1.9.1 Test Purpose and Environment ......................................................................................................... 1922
A.9.1.9.2 Test parameters ................................................................................................................................. 1922
A.9.1.9.3 Test Requirements ............................................................................................................................. 1925
A.9.1.10 FDD RSRP under Time-Domain Measurement Resource Restriction with MBSFN ABS .................... 1925
A.9.1.10.1 Test Purpose and Environment ......................................................................................................... 1925
A.9.1.10.2 Test parameters ................................................................................................................................. 1925
A.9.1.10.3 Test Requirements ............................................................................................................................. 1927
A.9.1.11 TDD RSRP under Time-Domain Measurement Resource Restriction with MBSFN ABS .................... 1927
A.9.1.11.1 Test Purpose and Environment ......................................................................................................... 1927
A.9.1.11.2 Test parameters ................................................................................................................................. 1927
A.9.1.11.3 Test Requirements ............................................................................................................................. 1930
A.9.1.12 FDD RSRP for E-UTRAN Carrier Aggregation for 20MHz .................................................................. 1930
A.9.1.12.1 Test Purpose and Environment ......................................................................................................... 1930
A.9.1.12.2 Test parameters ................................................................................................................................. 1930
A.9.1.12.3 Test Requirements ............................................................................................................................. 1931
A.9.1.13 TDD RSRP for E-UTRAN Carrier Aggregation for 20MHz ................................................................. 1931
A.9.1.13.1 Test Purpose and Environment ......................................................................................................... 1931
A.9.1.13.2 Test parameters ................................................................................................................................. 1931
A.9.1.13.3 Test Requirements ............................................................................................................................. 1932
A.9.1.14 FDD RSRP under Time-Domain Measurement Resource Restriction with CRS Assistance
Information and Non-MBSFN ABS ....................................................................................................... 1932
A.9.1.14.1 Test Purpose and Environment ......................................................................................................... 1932
A.9.1.14.2 Test parameters ................................................................................................................................. 1932
A.9.1.14.3 Test Requirements ............................................................................................................................. 1935
A.9.1.15 TDD RSRP under Time-Domain Measurement Resource Restriction with CRS Assistance
Information and Non-MBSFN ABS ....................................................................................................... 1935
A.9.1.15.1 Test Purpose and Environment ......................................................................................................... 1935
A.9.1.15.2 Test parameters ................................................................................................................................. 1935
A.9.1.15.3 Test Requirements ............................................................................................................................. 1937
A.9.1.16 FDD Intra frequency case for 5MHz Bandwidth .................................................................................... 1938
A.9.1.16.1 Test Purpose and Environment ......................................................................................................... 1938
A.9.1.16.2 Test parameters ................................................................................................................................. 1938
A.9.1.16.3 Test Requirements ............................................................................................................................. 1939
A.9.1.17 FDD—FDD Inter frequency case for 5MHz Bandwidth ........................................................................ 1940
A.9.1.17.1 Test Purpose and Environment ......................................................................................................... 1940
A.9.1.17.2 Test parameters ................................................................................................................................. 1940
A.9.1.17.3 Test Requirements ............................................................................................................................. 1941
A.9.1.18 FDD RSRP for E-UTRAN Carrier Aggregation for 10MHz + 5MHz ................................................... 1942
A.9.1.18.1 Test Purpose and Environment ......................................................................................................... 1942
A.9.1.18.2 Test parameters ................................................................................................................................. 1942
A.9.1.18.3 Test Requirements ............................................................................................................................. 1943
A.9.1.19 TDD RSRP for E-UTRAN Carrier Aggregation for 10MHz + 5MHz ................................................... 1944
A.9.1.19.1 Test Purpose and Environment ......................................................................................................... 1944
A.9.1.19.2 Test parameters ................................................................................................................................. 1944
A.9.1.19.3 Test Requirements ............................................................................................................................. 1944
A.9.1.20 FDD RSRP for E-UTRAN Carrier Aggregation for 5MHz + 5MHz bandwidth.................................... 1944
A.9.1.20.1 Test Purpose and Environment ......................................................................................................... 1944
A.9.1.20.2 Test parameters ................................................................................................................................. 1944
A.9.1.20.3 Test Requirements ............................................................................................................................. 1945
A.9.1.21 TDD RSRP for E-UTRAN Carrier Aggregation for 5MHz + 5MHz bandwidth ................................... 1946
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 53 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.1.21.1 Test Purpose and Environment ......................................................................................................... 1946
A.9.1.21.2 Test parameters ................................................................................................................................. 1946
A.9.1.21.3 Test Requirements ............................................................................................................................. 1946
A.9.1.22 RSRP for E-UTRAN TDD-FDD Carrier Aggregation with PCell in FDD ............................................ 1946
A.9.1.22.1 Test Purpose and Environment ......................................................................................................... 1946
A.9.1.22.2 Test parameters ................................................................................................................................. 1947
A.9.1.22.3 Test Requirements ............................................................................................................................. 1950
A.9.1.23 RSRP for E-UTRAN TDD-FDD Carrier Aggregation with PCell in TDD.................................................... 1950
A.9.1.23.1 Test Purpose and Environment ......................................................................................................... 1950
A.9.1.23.2 Test parameters ................................................................................................................................. 1950
A.9.1.23.3 Test Requirements ............................................................................................................................. 1952
A.9.1.24 TDD RSRP for E-UTRAN Carrier Aggregation for 20MHz + 10MHz ................................................. 1953
A.9.1.24.1 Test Purpose and Environment ......................................................................................................... 1953
A.9.1.24.2 Test parameters ................................................................................................................................. 1953
A.9.1.24.3 Test Requirements ............................................................................................................................. 1953
A.9.1.25 FDD intra-frequency absolute and relative RSRP accuracies in CRS based discovery signal ............... 1954
A.9.1.25.1 Test Purpose and Environment ......................................................................................................... 1954
A.9.1.25.2 Test parameters ................................................................................................................................. 1954
A.9.1.25.3 Test Requirements ............................................................................................................................. 1956
A.9.1.26 TDD intra-frequency absolute and relative RSRP accuracies in CRS based discovery signal ............... 1956
A.9.1.26.1 Test Purpose and Environment ......................................................................................................... 1956
A.9.1.26.2 Test parameters ................................................................................................................................. 1956
A.9.1.26.3 Test Requirements ............................................................................................................................. 1958
A.9.1.27 FDD—FDD inter-frequency absolute and relative RSRP accuracies in CRS based discovery signal ... 1958
A.9.1.27.1 Test Purpose and Environment ......................................................................................................... 1958
A.9.1.27.2 Test parameters ................................................................................................................................. 1958
A.9.1.27.3 Test Requirements ............................................................................................................................. 1960
A.9.1.28 TDD—TDD inter-frequency absolute and relative RSRP accuracies in CRS based discovery signal .. 1960
A.9.1.28.1 Test Purpose and Environment ......................................................................................................... 1960
A.9.1.28.2 Test parameters ................................................................................................................................. 1960
A.9.1.28.3 Test Requirements ............................................................................................................................. 1962
A.9.1.29 FDD intra frequency absolute and relative CSI-RSRP accuracies in CSI-RS based discovery signal ... 1962
A.9.1.29.1 Test Purpose and Environment ......................................................................................................... 1962
A.9.1.29.2 Test parameters ................................................................................................................................. 1962
A.9.1.29.3 Test Requirements ............................................................................................................................. 1964
A.9.1.30 TDD intra frequency absolute and relative CSI-RSRP accuracies in CSI-RS based discovery signal ... 1964
A.9.1.30.1 Test Purpose and Environment ......................................................................................................... 1964
A.9.1.30.2 Test parameters ................................................................................................................................. 1965
A.9.1.30.3 Test Requirements ............................................................................................................................. 1967
A.9.1.31 FDD—FDD inter-frequency absolute and relative CSI-RSRP accuracies in CSI-RS based discovery
signal ....................................................................................................................................................... 1967
A.9.1.31.1 Test Purpose and Environment ......................................................................................................... 1967
A.9.1.31.2 Test parameters ................................................................................................................................. 1967
A.9.1.31.3 Test Requirements ............................................................................................................................. 1969
A.9.1.32 TDD—TDD inter-frequency absolute and relative CSI-RSRP accuracies in CSI-RS based discovery
signal ....................................................................................................................................................... 1969
A.9.1.32.1 Test Purpose and Environment ......................................................................................................... 1969
A.9.1.32.2 Test parameters ................................................................................................................................. 1970
A.9.1.32.3 Test Requirements ............................................................................................................................. 1972
A.9.1.33 FDD absolute and relative RSRP accuracies for E-UTRAN Carrier Aggregation in CRS based
discovery signal ...................................................................................................................................... 1972
A.9.1.33.1 Test Purpose and Environment ......................................................................................................... 1972
A.9.1.33.2 Test parameters ................................................................................................................................. 1972
A.9.1.33.3 Test Requirements ............................................................................................................................. 1974
A.9.1.34 TDD absolute and relative RSRP accuracies for E-UTRAN Carrier Aggregation in CRS based
discovery signal ...................................................................................................................................... 1974
A.9.1.34.1 Test Purpose and Environment ......................................................................................................... 1974
A.9.1.34.2 Test parameters ................................................................................................................................. 1974
A.9.1.34.3 Test Requirements ............................................................................................................................. 1976
A.9.1.35 FDD absolute and relative CSI-RSRP accuracies for E-UTRAN Carrier Aggregation in CSI-RS
based discovery signal ............................................................................................................................ 1976
A.9.1.35.1 Test Purpose and Environment ......................................................................................................... 1976
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 54 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.1.35.2 Test parameters ................................................................................................................................. 1976
A.9.1.35.3 Test Requirements ............................................................................................................................. 1978
A.9.1.36 TDD absolute and relative CSI-RSRP accuracies for E-UTRAN Carrier Aggregation in CSI-RS
based discovery signal ............................................................................................................................ 1979
A.9.1.36.1 Test Purpose and Environment ......................................................................................................... 1979
A.9.1.36.2 Test parameters ................................................................................................................................. 1979
A.9.1.36.3 Test Requirements ............................................................................................................................. 1981
A.9.1.37 3 DL PCell in FDD RSRP for E-UTRAN in Carrier Aggregation ......................................................... 1981
A.9.1.37.1 Test Purpose and Environment ......................................................................................................... 1981
A.9.1.37.2 Test parameters ................................................................................................................................. 1981
A.9.1.37.3 Test Requirements ............................................................................................................................. 1983
A.9.1.38 3 DL PCell in TDD RSRP for E-UTRAN in Carrier Aggregation ......................................................... 1984
A.9.1.38.1 Test Purpose and Environment ......................................................................................................... 1984
A.9.1.38.2 Test parameters ................................................................................................................................. 1984
A.9.1.38.3 Test Requirements ............................................................................................................................. 1986
A.9.1.39 3 DL FDD RSRP for E-UTRAN in Carrier Aggregation ....................................................................... 1987
A.9.1.39.1 Test Purpose and Environment ......................................................................................................... 1987
A.9.1.39.2 Test parameters ................................................................................................................................. 1987
A.9.1.39.3 Test Requirements ............................................................................................................................. 1991
A.9.1.40 3 DL TDD RSRP for E-UTRAN in Carrier Aggregation ....................................................................... 1991
A.9.1.40.1 Test Purpose and Environment ......................................................................................................... 1991
A.9.1.40.2 Test parameters ................................................................................................................................. 1992
A.9.1.40.3 Test Requirements ............................................................................................................................. 1996
A.9.1.41 FD-FDD RSRP Intra frequency case for UE category 0 ........................................................................ 1996
A.9.1.41.1 Test Purpose and Environment ......................................................................................................... 1996
A.9.1.41.2 Test parameters ................................................................................................................................. 1996
A.9.1.41.3 Test Requirements ............................................................................................................................. 1998
A.9.1.42 HD-FDD RSRP Intra frequency case for UE category 0 ........................................................................ 1998
A.9.1.42.1 Test Purpose and Environment ......................................................................................................... 1998
A.9.1.42.2 Test parameters ................................................................................................................................. 1998
A.9.1.42.3 Test Requirements ............................................................................................................................. 2000
A.9.1.43 TDD RSRP Intra frequency case for UE category 0............................................................................... 2000
A.9.1.43.1 Test Purpose and Environment ......................................................................................................... 2000
A.9.1.43.2 Test parameters ................................................................................................................................. 2000
A.9.1.43.3 Test Requirements ............................................................................................................................. 2001
A.9.1.44 4 DL CA PCell in FDD FDD-TDD RSRP for E-UTRAN in Carrier Aggregation ................................ 2002
A.9.1.44.1 Test Purpose and Environment ......................................................................................................... 2002
A.9.1.44.2 Test parameters ................................................................................................................................. 2002
A.9.1.44.3 Test Requirements ............................................................................................................................. 2006
A.9.1.45 4 DL CA PCell in TDD FDD-TDD RSRP for E-UTRAN in Carrier Aggregation ................................ 2006
A.9.1.45.1 Test Purpose and Environment ......................................................................................................... 2006
A.9.1.45.2 Test parameters ................................................................................................................................. 2006
A.9.1.45.3 Test Requirements ............................................................................................................................. 2010
A.9.1.46 4 DL FDD RSRP for E-UTRAN in Carrier Aggregation ....................................................................... 2010
A.9.1.46.1 Test Purpose and Environment ......................................................................................................... 2010
A.9.1.46.2 Test parameters ................................................................................................................................. 2010
A.9.1.46.3 Test Requirements ............................................................................................................................. 2016
A.9.1.47 4 DL TDD RSRP for E-UTRAN in Carrier Aggregation ....................................................................... 2017
A.9.1.47.1 Test Purpose and Environment ......................................................................................................... 2017
A.9.1.47.2 Test parameters ................................................................................................................................. 2017
A.9.1.47.3 Test Requirements ............................................................................................................................. 2023
A.9.1.48 5 DL PCell in FDD RSRP for E-UTRAN in Carrier Aggregation ......................................................... 2023
A.9.1.48.1 Test Purpose and Environment ......................................................................................................... 2023
A.9.1.48.2 Test parameters ................................................................................................................................. 2024
A.9.1.48.3 Test Requirements ............................................................................................................................. 2031
A.9.1.49 5 DL PCell in TDD RSRP for E-UTRAN in Carrier Aggregation ......................................................... 2032
A.9.1.49.1 Test Purpose and Environment ......................................................................................................... 2032
A.9.1.49.2 Test parameters ................................................................................................................................. 2032
A.9.1.49.3 Test Requirements ............................................................................................................................. 2039
A.9.1.50 5 DL FDD RSRP for E-UTRAN in Carrier Aggregation ....................................................................... 2040
A.9.1.50.1 Test Purpose and Environment ......................................................................................................... 2040
A.9.1.50.2 Test parameters ................................................................................................................................. 2040
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 55 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.1.50.3 Test Requirements ............................................................................................................................. 2044
A.9.1.51 5 DL TDD RSRP for E-UTRAN in Carrier Aggregation ....................................................................... 2045
A.9.1.51.1 Test Purpose and Environment ......................................................................................................... 2045
A.9.1.51.2 Test parameters ................................................................................................................................. 2045
A.9.1.51.3 Test Requirements ............................................................................................................................. 2049
A.9.1.52 FD-FDD RSRP Intra frequency case for Cat-M1 UE in CEModeA ...................................................... 2050
A.9.1.52.1 Test Purpose and Environment ......................................................................................................... 2050
A.9.1.52.2 Test parameters ................................................................................................................................. 2050
A.9.1.52.3 Test Requirements ............................................................................................................................. 2052
A.9.1.52A FD-FDD RSRP Intra frequency case for Cat-M1 UE for 5MHz Bandwidth in CEModeA ................... 2052
A.9.1.52A.1 Test Purpose and Environment ......................................................................................................... 2052
A.9.1.52A.2 Test parameters ................................................................................................................................. 2052
A.9.1.52A.3 Test Requirements ............................................................................................................................. 2053
A.9.1.53 HD-FDD RSRP Intra frequency case for Cat-M1 UE in CEModeA ...................................................... 2053
A.9.1.53.1 Test Purpose and Environment ......................................................................................................... 2053
A.9.1.53.2 Test parameters ................................................................................................................................. 2054
A.9.1.53.3 Test Requirements ............................................................................................................................. 2056
A.9.1.53A HD-FDD RSRP Intra frequency case for Cat-M1 UE for 5MHz Bandwidth in CEModeA ................... 2056
A.9.1.53A.1 Test Purpose and Environment ......................................................................................................... 2056
A.9.1.53A.2 Test parameters ................................................................................................................................. 2056
A.9.1.53A.3 Test Requirements ............................................................................................................................. 2057
A.9.1.54 TDD RSRP Intra frequency case for Cat-M1 UE in CEModeA............................................................. 2057
A.9.1.54.1 Test Purpose and Environment ......................................................................................................... 2057
A.9.1.54.2 Test parameters ................................................................................................................................. 2058
A.9.1.54.3 Test Requirements ............................................................................................................................. 2059
A.9.1.55 FDD intra frequency absolute and relative RSRP accuracies for SCell with frame structure 3 ............. 2059
A.9.1.55.1 Test Purpose and Environment ......................................................................................................... 2059
A.9.1.55.2 Test parameters ................................................................................................................................. 2059
A.9.1.55.3 Test Requirements ............................................................................................................................. 2062
A.9.1.56 TDD intra frequency absolute and relative RSRP accuracies for SCell with frame structure 3 ............. 2062
A.9.1.56.1 Test Purpose and Environment ......................................................................................................... 2062
A.9.1.56.2 Test parameters ................................................................................................................................. 2062
A.9.1.56.3 Test Requirements ............................................................................................................................. 2064
A.9.1.57 FD-FDD RSRP Intra frequency case for Cat-M1 UE in CEModeB ....................................................... 2065
A.9.1.57.1 Test Purpose and Environment ......................................................................................................... 2065
A.9.1.57.2 Test parameters ................................................................................................................................. 2065
A.9.1.57.3 Test Requirements ............................................................................................................................. 2067
A.9.1.57A FD-FDD RSRP Intra frequency case for Cat-M1 UE for 5MHz Bandwidth in CEModeB ................... 2067
A.9.1.57A.1 Test Purpose and Environment ......................................................................................................... 2067
A.9.1.57A.2 Test parameters ................................................................................................................................. 2067
A.9.1.57A.3 Test Requirements ............................................................................................................................. 2068
A.9.1.58 HD-FDD RSRP Intra frequency case for Cat-M1 UE in CEModeB ...................................................... 2068
A.9.1.58.1 Test Purpose and Environment ......................................................................................................... 2068
A.9.1.58.2 Test parameters ................................................................................................................................. 2069
A.9.1.58.3 Test Requirements ............................................................................................................................. 2071
A.9.1.58A HD-FDD RSRP Intra frequency case for Cat-M1 UE for 5MHz Bandwidth in CEModeB ................... 2071
A.9.1.58A.1 Test Purpose and Environment ......................................................................................................... 2071
A.9.1.58A.2 Test parameters ................................................................................................................................. 2071
A.9.1.58A.3 Test Requirements ............................................................................................................................. 2072
A.9.1.59 TDD RSRP Intra frequency case for Cat-M1 UE in CEModeB ............................................................. 2072
A.9.1.59.1 Test Purpose and Environment ......................................................................................................... 2072
A.9.1.59.2 Test parameters ................................................................................................................................. 2073
A.9.1.59.3 Test Requirements ............................................................................................................................. 2074
A.9.1.60 FS3 absolute and relative CSI-RSRP accuracies for E-UTRAN Carrier Aggregation in CSI-RS
based discovery signal with FDD PCell ................................................................................................. 2074
A.9.1.60.1 Test Purpose and Environment ......................................................................................................... 2074
A.9.1.60.2 Test parameters ................................................................................................................................. 2074
A.9.1.60.3 Test Requirements ............................................................................................................................. 2077
A.9.1.61 FS3 absolute and relative CSI-RSRP accuracies for E-UTRAN Carrier Aggregation in CSI-RS
based discovery signal with TDD PCell ................................................................................................. 2077
A.9.1.61.1 Test Purpose and Environment ......................................................................................................... 2077
A.9.1.61.2 Test parameters ................................................................................................................................. 2077
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 56 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.1.61.3 Test Requirements ............................................................................................................................. 2079
A.9.2 RSRQ ........................................................................................................................................................... 2079
A.9.2.1 FDD Intra frequency case ....................................................................................................................... 2079
A.9.2.1.1 Test Purpose and Environment ......................................................................................................... 2079
A.9.2.1.2 Test parameters ................................................................................................................................. 2080
A.9.2.1.3 Test Requirements ............................................................................................................................. 2082
A.9.2.2 TDD Intra frequency case ....................................................................................................................... 2082
A.9.2.2.1 Test Purpose and Environment ......................................................................................................... 2082
A.9.2.2.2 Test parameters ................................................................................................................................. 2082
A.9.2.2.3 Test Requirements ............................................................................................................................. 2084
A.9.2.3 FDD—FDD Inter frequency case ........................................................................................................... 2084
A.9.2.3.1 Test Purpose and Environment ......................................................................................................... 2084
A.9.2.3.2 Test parameters ................................................................................................................................. 2084
A.9.2.3.3 Test Requirements ............................................................................................................................. 2086
A.9.2.4 TDD—TDD Inter frequency case ........................................................................................................... 2086
A.9.2.4.1 Test Purpose and Environment ......................................................................................................... 2086
A.9.2.4.2 Test parameters ................................................................................................................................. 2086
A.9.2.4.3 Test Requirements ............................................................................................................................. 2088
A.9.2.4A FDD—TDD Inter frequency case ........................................................................................................... 2089
A.9.2.4A.1 Test Purpose and Environment ......................................................................................................... 2089
A.9.2.4A.2 Test parameters ................................................................................................................................. 2089
A.9.2.4A.3 Test Requirements ............................................................................................................................. 2091
A.9.2.5 FDD RSRQ for E-UTRA Carrier Aggregation....................................................................................... 2091
A.9.2.5.1 Test Purpose and Environment ......................................................................................................... 2091
A.9.2.5.2 Test parameters ................................................................................................................................. 2092
A.9.2.5.3 Test Requirements ............................................................................................................................. 2094
A.9.2.6 TDD RSRQ for E-UTRA Carrier Aggregation ...................................................................................... 2094
A.9.2.6.1 Test Purpose and Environment ......................................................................................................... 2094
A.9.2.6.2 Test parameters ................................................................................................................................. 2094
A.9.2.6.3 Test Requirements ............................................................................................................................. 2096
A.9.2.7 FDD RSRQ under Time Domain Measurement Resource Restriction with Non-MBSFN ABS............ 2096
A.9.2.7.1 Test Purpose and Environment ......................................................................................................... 2096
A.9.2.7.2 Test parameters ................................................................................................................................. 2096
A.9.2.7.3 Test Requirements ............................................................................................................................. 2099
A.9.2.8 TDD RSRQ under Time Domain Measurement Resource Restriction with Non-MBSFN ABS ........... 2099
A.9.2.8.1 Test Purpose and Environment ......................................................................................................... 2099
A.9.2.8.2 Test parameters ................................................................................................................................. 2099
A.9.2.8.3 Test Requirements ............................................................................................................................. 2102
A.9.2.9 FDD RSRQ under Time Domain Measurement Resource Restriction with MBSFN ABS .................... 2102
A.9.2.9.1 Test Purpose and Environment ......................................................................................................... 2102
A.9.2.9.2 Test parameters ................................................................................................................................. 2102
A.9.2.9.3 Test Requirements ............................................................................................................................. 2105
A.9.2.10 TDD Intra frequency case under time domain measurement resource restriction with MBSFN ABS ... 2105
A.9.2.10.1 Test Purpose and Environment ......................................................................................................... 2105
A.9.2.10.2 Test parameters ................................................................................................................................. 2105
A.9.2.10.3 Test Requirements ............................................................................................................................. 2108
A.9.2.11 FDD RSRQ for E-UTRA Carrier Aggregation (20MHz bandwidth) ..................................................... 2108
A.9.2.11.1 Test Purpose and Environment ......................................................................................................... 2108
A.9.2.11.2 Test parameters ................................................................................................................................. 2108
A.9.2.11.3 Test Requirements ............................................................................................................................. 2109
A.9.2.12 TDD RSRQ for E-UTRA Carrier Aggregation (20MHz bandwidth) ..................................................... 2109
A.9.2.12.1 Test Purpose and Environment ......................................................................................................... 2109
A.9.2.12.2 Test parameters ................................................................................................................................. 2109
A.9.2.12.3 Test Requirements ............................................................................................................................. 2110
A.9.2.13 Void ........................................................................................................................................................ 2111
A.9.2.13.1 Void................................................................................................................................................... 2111
A.9.2.13.2 Void................................................................................................................................................... 2111
A.9.2.13.3 Void................................................................................................................................................... 2111
A.9.2.14 Void ........................................................................................................................................................ 2111
A.9.2.14.1 Void................................................................................................................................................... 2111
A.9.2.14.2 Void................................................................................................................................................... 2111
A.9.2.14.3 Void................................................................................................................................................... 2111
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 57 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.2.15 FDD RSRQ under Time Domain Measurement Resource Restriction with CRS Assistance
Information and Non-MBSFN ABS ....................................................................................................... 2111
A.9.2.15.1 Test Purpose and Environment ......................................................................................................... 2111
A.9.2.15.2 Test parameters ................................................................................................................................. 2111
A.9.2.15.3 Test Requirements ............................................................................................................................. 2114
A.9.2.16 TDD RSRQ under Time Domain Measurement Resource Restriction with CRS Assistance
Information and Non-MBSFN ABS ....................................................................................................... 2114
A.9.2.16.1 Test Purpose and Environment ......................................................................................................... 2114
A.9.2.16.2 Test parameters ................................................................................................................................. 2114
A.9.2.16.3 Test Requirements ............................................................................................................................. 2118
A.9.2.17 FDD Intra frequency case for 5 MHz bandwidth.................................................................................... 2118
A.9.2.17.1 Test Purpose and Environment ......................................................................................................... 2118
A.9.2.17.2 Test parameters ................................................................................................................................. 2118
A.9.2.17.3 Test Requirements ............................................................................................................................. 2120
A.9.2.18 FDD—FDD Inter frequency case for 5MHz bandwidth......................................................................... 2120
A.9.2.18.1 Test Purpose and Environment ......................................................................................................... 2120
A.9.2.18.2 Test parameters ................................................................................................................................. 2120
A.9.2.18.3 Test Requirements ............................................................................................................................. 2122
A.9.2.19 FDD-FDD Inter Frequency WB-RSRQ .................................................................................................. 2122
A.9.2.19.1 Test Purpose and Environment ......................................................................................................... 2122
A.9.2.19.2 Test parameters ................................................................................................................................. 2122
A.9.2.19.3 Test Requirements ............................................................................................................................. 2124
A.9.2.20 TDD—TDD Inter Frequency WB-RSRQ............................................................................................... 2124
A.9.2.20.1 Test Purpose and Environment ......................................................................................................... 2124
A.9.2.20.2 Test parameters ................................................................................................................................. 2124
A.9.2.20.3 Test Requirements ............................................................................................................................. 2126
A.9.2.21 FDD RSRQ for E-UTRAN Carrier Aggregation for 10MHz+5MHz ..................................................... 2126
A.9.2.21.1 Test Purpose and Environment ......................................................................................................... 2126
A.9.2.21.2 Test parameters ................................................................................................................................. 2126
A.9.2.21.3 Test Requirements ............................................................................................................................. 2128
A.9.2.22 TDD RSRQ for E-UTRAN Carrier Aggregation for 10MHz+5MHz .................................................... 2128
A.9.2.22.1 Test Purpose and Environment ......................................................................................................... 2128
A.9.2.22.2 Test parameters ................................................................................................................................. 2128
A.9.2.22.3 Test Requirements ............................................................................................................................. 2129
A.9.2.23 FDD RSRQ for E-UTRA Carrier Aggregation (5MHz + 5MHz bandwidth) ......................................... 2129
A.9.2.23.1 Test Purpose and Environment ......................................................................................................... 2129
A.9.2.23.2 Test parameters ................................................................................................................................. 2129
A.9.2.23.3 Test Requirements ............................................................................................................................. 2131
A.9.2.24 TDD RSRQ for E-UTRA Carrier Aggregation (5MHz + 5MHz bandwidth)......................................... 2131
A.9.2.24.1 Test Purpose and Environment ......................................................................................................... 2131
A.9.2.24.2 Test parameters ................................................................................................................................. 2131
A.9.2.24.3 Test Requirements ............................................................................................................................. 2132
A.9.2.25 RSRQ for E-UTRAN TDD-FDD Carrier Aggregation with PCell in FDD ........................................... 2132
A.9.2.25.1 Test Purpose and Environment ......................................................................................................... 2132
A.9.2.25.2 Test parameters ................................................................................................................................. 2132
A.9.2.25.3 Test Requirements ............................................................................................................................. 2135
A.9.2.26 RSRQ for E-UTRAN TDD-FDD Carrier Aggregation with PCell in TDD ........................................... 2135
A.9.2.26.1 Test Purpose and Environment ......................................................................................................... 2135
A.9.2.26.2 Test parameters ................................................................................................................................. 2135
A.9.2.26.3 Test Requirements ............................................................................................................................. 2138
A.9.2.27 TDD RSRQ for E-UTRAN Carrier Aggregation for 20MHz+10MHz .................................................. 2138
A.9.2.27.1 Test Purpose and Environment ......................................................................................................... 2138
A.9.2.27.2 Test parameters ................................................................................................................................. 2138
A.9.2.27.3 Test Requirements ............................................................................................................................. 2139
A.9.2.28 FDD intra-frequency absolute RSRQ accuracy with CRS based discovery signal ................................. 2139
A.9.2.28.1 Test Purpose and Environment ......................................................................................................... 2139
A.9.2.28.2 Test parameters ................................................................................................................................. 2139
A.9.2.28.3 Test Requirements ............................................................................................................................. 2141
A.9.2.29 TDD intra-frequency absolute RSRQ accuracy with CRS based discovery signal ................................ 2141
A.9.2.29.1 Test Purpose and Environment ......................................................................................................... 2141
A.9.2.29.2 Test parameters ................................................................................................................................. 2141
A.9.2.29.3 Test Requirements ............................................................................................................................. 2143
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 58 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.2.30 FDD-FDD inter-frequency absolute and relative RSRQ accuracies with CRS based discovery signal . 2143
A.9.2.30.1 Test Purpose and Environment ......................................................................................................... 2143
A.9.2.30.2 Test parameters ................................................................................................................................. 2143
A.9.2.30.3 Test Requirements ............................................................................................................................. 2145
A.9.2.31 TDD-TDD inter-frequency absolute and relative RSRQ accuracies with CRS based discovery signal . 2145
A.9.2.31.1 Test Purpose and Environment ......................................................................................................... 2145
A.9.2.31.2 Test parameters ................................................................................................................................. 2145
A.9.2.31.3 Test Requirements ............................................................................................................................. 2147
A.9.2.32 FDD absolute and relative RSRQ accuracy for E-UTRAN Carrier Aggregation in CRS based
discovery signal ...................................................................................................................................... 2147
A.9.2.32.1 Test Purpose and Environment ......................................................................................................... 2147
A.9.2.32.2 Test parameters ................................................................................................................................. 2147
A.9.2.32.3 Test Requirements ............................................................................................................................. 2149
A.9.2.33 TDD absolute and relative RSRQ accuracy for E-UTRAN Carrier Aggregation in CRS based
discovery signal ...................................................................................................................................... 2149
A.9.2.33.1 Test Purpose and Environment ......................................................................................................... 2149
A.9.2.33.2 Test parameters ................................................................................................................................. 2149
A.9.2.33.3 Test Requirements ............................................................................................................................. 2151
A.9.2.34 FDD—FDD Inter frequency new RSRQ ................................................................................................ 2151
A.9.2.34.1 Test Purpose and Environment ......................................................................................................... 2151
A.9.2.34.2 Test parameters ................................................................................................................................. 2151
A.9.2.34.3 Test Requirements ............................................................................................................................. 2153
A.9.2.35 TDD—TDD Inter frequency new RSRQ................................................................................................ 2153
A.9.2.35.1 Test Purpose and Environment ......................................................................................................... 2153
A.9.2.35.2 Test parameters ................................................................................................................................. 2153
A.9.2.35.3 Test Requirements ............................................................................................................................. 2155
A.9.2.36 FDD—FDD Inter frequency RSRQ measured on all OFDM symbols ................................................... 2155
A.9.2.36.1 Test Purpose and Environment ......................................................................................................... 2155
A.9.2.36.2 Test parameters ................................................................................................................................. 2155
A.9.2.36.3 Test Requirements ............................................................................................................................. 2156
A.9.2.37 TDD—TDD Inter frequency RSRQ measurement on all OFDM symbols ............................................ 2157
A.9.2.37.1 Test Purpose and Environment ......................................................................................................... 2157
A.9.2.37.2 Test parameters ................................................................................................................................. 2157
A.9.2.37.3 Test Requirements ............................................................................................................................. 2158
A.9.2.38 3 DL PCell in FDD RSRQ for E-UTRAN in Carrier Aggregation......................................................... 2159
A.9.2.38.1 Test Purpose and Environment ......................................................................................................... 2159
A.9.2.38.2 Test parameters ................................................................................................................................. 2159
A.9.2.38.3 Test Requirements ............................................................................................................................. 2162
A.9.2.39 3 DL PCell in TDD RSRQ for E-UTRAN in Carrier Aggregation ........................................................ 2162
A.9.2.39.1 Test Purpose and Environment ......................................................................................................... 2162
A.9.2.39.2 Test parameters ................................................................................................................................. 2162
A.9.2.39.3 Test Requirements ............................................................................................................................. 2165
A.9.2.40 3 DL FDD RSRQ for E-UTRAN in Carrier Aggregation ...................................................................... 2165
A.9.2.40.1 Test Purpose and Environment ......................................................................................................... 2165
A.9.2.40.2 Test parameters ................................................................................................................................. 2165
A.9.2.40.3 Test Requirements ............................................................................................................................. 2167
A.9.2.41 3 DL TDD RSRQ for E-UTRAN in Carrier Aggregation ...................................................................... 2167
A.9.2.41.1 Test Purpose and Environment ......................................................................................................... 2167
A.9.2.41.2 Test parameters ................................................................................................................................. 2168
A.9.2.41.3 Test Requirements ............................................................................................................................. 2170
A.9.2.42 FD-FDD RSRQ Intra frequency case for UE category 0 ........................................................................ 2170
A.9.2.42.1 Test Purpose and Environment ......................................................................................................... 2170
A.9.2.42.2 Test parameters ................................................................................................................................. 2170
A.9.2.42.3 Test Requirements ............................................................................................................................. 2172
A.9.2.43 HD-FDD RSRQ Intra frequency case for UE category 0 ....................................................................... 2172
A.9.2.43.1 Test Purpose and Environment ......................................................................................................... 2172
A.9.2.43.2 Test parameters ................................................................................................................................. 2172
A.9.2.43.3 Test Requirements ............................................................................................................................. 2174
A.9.2.44 TDD RSRQ Intra frequency case for UE category 0 .............................................................................. 2174
A.9.2.44.1 Test Purpose and Environment ......................................................................................................... 2174
A.9.2.44.2 Test parameters ................................................................................................................................. 2174
A.9.2.44.3 Test Requirements ............................................................................................................................. 2176
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 59 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.2.45 4 DL CA PCell in FDD FDD-TDD RSRQ for E-UTRAN in Carrier Aggregation................................ 2176
A.9.2.45.1 Test Purpose and Environment ......................................................................................................... 2176
A.9.2.45.2 Test parameters ................................................................................................................................. 2176
A.9.2.45.3 Test Requirements ............................................................................................................................. 2179
A.9.2.46 4 DL CA PCell in TDD TDD-FDD RSRQ for E-UTRAN in Carrier Aggregation ............................... 2180
A.9.2.46.1 Test Purpose and Environment ......................................................................................................... 2180
A.9.2.46.2 Test parameters ................................................................................................................................. 2180
A.9.2.46.3 Test Requirements ............................................................................................................................. 2183
A.9.2.47 5 DL PCell in FDD RSRQ for E-UTRAN in Carrier Aggregation......................................................... 2183
A.9.2.47.1 Test Purpose and Environment ......................................................................................................... 2184
A.9.2.47.2 Test parameters ................................................................................................................................. 2184
A.9.2.47.3 Test Requirements ............................................................................................................................. 2187
A.9.2.48 5 DL PCell in TDD RSRQ for E-UTRAN in Carrier Aggregation ........................................................ 2187
A.9.2.48.1 Test Purpose and Environment ......................................................................................................... 2187
A.9.2.48.2 Test parameters ................................................................................................................................. 2187
A.9.2.48.3 Test Requirements ............................................................................................................................. 2190
A.9.2.49 Absolute and relative RSRQ accuracies in 5 DL FDD CA..................................................................... 2190
A.9.2.49.1 Test Purpose and Environment ......................................................................................................... 2190
A.9.2.49.2 Test parameters ................................................................................................................................. 2190
A.9.2.49.3 Test Requirements ............................................................................................................................. 2194
A.9.2.50 Absolute and relative RSRQ accuracies in 5 DL TDD CA .................................................................... 2195
A.9.2.50.1 Test Purpose and Environment ......................................................................................................... 2195
A.9.2.50.2 Test parameters ................................................................................................................................. 2195
A.9.2.50.3 Test Requirements ............................................................................................................................. 2199
A.9.2.51 FDD intra frequency absolute and relative RSRQ accuracies for SCell with frame structure 3 ............. 2199
A.9.2.51.1 Test Purpose and Environment ......................................................................................................... 2199
A.9.2.51.2 Test parameters ................................................................................................................................. 2200
A.9.2.51.3 Test Requirements ............................................................................................................................. 2203
A.9.2.52 TDD intra frequency absolute and relative RSRQ accuracies for SCell with frame structure 3............. 2203
A.9.2.52.1 Test Purpose and Environment ......................................................................................................... 2203
A.9.2.52.2 Test parameters ................................................................................................................................. 2203
A.9.2.52.3 Test Requirements ............................................................................................................................. 2205
A.9.3 UTRAN FDD CPICH RSCP ........................................................................................................................ 2206
A.9.3.1 E-UTRAN FDD ...................................................................................................................................... 2206
A.9.3.1.1 Test Purpose and Environment ......................................................................................................... 2206
A.9.3.1.2 Parameters ......................................................................................................................................... 2206
A.9.3.1.3 Test Requirements ............................................................................................................................. 2208
A.9.3.2 E-UTRAN TDD ............................................................................................................................................... 2208
A.9.3.2.1 Test Purpose and Environment ......................................................................................................... 2208
A.9.3.2.2 Parameters ......................................................................................................................................... 2208
A.9.3.2.3 Test Requirements ............................................................................................................................. 2211
A.9.3.3 E-UTRAN FDD for 5MHz Bandwidth ................................................................................................... 2211
A.9.3.3.1 Test Purpose and Environment ......................................................................................................... 2211
A.9.3.3.2 Parameters ......................................................................................................................................... 2211
A.9.3.3.3 Test Requirements ............................................................................................................................. 2212
A.9.4 UTRAN FDD CPICH Ec/No ....................................................................................................................... 2213
A.9.4.1 E-UTRAN FDD ...................................................................................................................................... 2213
A.9.4.1.1 Test Purpose and Environment ......................................................................................................... 2213
A.9.4.1.2 Parameters ......................................................................................................................................... 2213
A.9.4.1.3 Test Requirements ............................................................................................................................. 2215
A.9.4.2 E-UTRAN TDD...................................................................................................................................... 2216
A.9.4.2.1 Test Purpose and Environment ......................................................................................................... 2216
A.9.4.2.2 Parameters ......................................................................................................................................... 2216
A.9.4.2.3 Test Requirements ............................................................................................................................. 2218
A.9.4.3 E-UTRAN FDD for 5MHz Bandwidth ................................................................................................... 2219
A.9.4.3.1 Test Purpose and Environment ......................................................................................................... 2219
A.9.4.3.2 Parameters ......................................................................................................................................... 2219
A.9.4.3.3 Test Requirements ............................................................................................................................. 2220
A.9.5 UTRAN TDD measurement ......................................................................................................................... 2220
A.9.5.1 P-CCPCH RSCP absolute accuracy for E-UTRAN FDD ....................................................................... 2220
A.9.5.1.1 Test Purpose and Environment ......................................................................................................... 2220
A.9.5.1.2 Test parameters ................................................................................................................................. 2221
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 60 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.5.1.3 Test Requirements ............................................................................................................................. 2222
A.9.5.2 P-CCPCH RSCP absolute accuracy for E-UTRAN TDD ...................................................................... 2223
A.9.5.2.1 Test Purpose and Environment ......................................................................................................... 2223
A.9.5.2.2 Test parameters ................................................................................................................................. 2223
A.9.5.2.3 Test Requirements ............................................................................................................................. 2224
A.9.6 GSM Carrier RSSI........................................................................................................................................ 2225
A.9.6.1 E-UTRAN FDD ...................................................................................................................................... 2225
A.9.6.1.1 Test Purpose and Environment ......................................................................................................... 2225
A.9.6.1.2 Test Requirements ............................................................................................................................. 2226
A.9.6.2 E-UTRAN TDD...................................................................................................................................... 2226
A.9.6.2.1 Test Purpose and Environment ......................................................................................................... 2226
A.9.6.2.2 Test Requirements ............................................................................................................................. 2229
A.9.7 UE Rx – Tx Time Difference ....................................................................................................................... 2229
A.9.7.1 E-UTRAN FDD UE Rx – Tx time difference case................................................................................. 2229
A.9.7.1.1 Test Purpose and Environment ......................................................................................................... 2229
A.9.7.1.2 Test parameters ................................................................................................................................. 2229
A.9.7.1.3 Test Requirements ............................................................................................................................. 2231
A.9.7.2 E-UTRA TDD ........................................................................................................................................ 2231
A.9.7.2.1 Test Purpose and Environment ......................................................................................................... 2231
A.9.7.2.2 Test parameters ................................................................................................................................. 2231
A.9.7.2.3 Test Requirements ............................................................................................................................. 2233
A.9.7.3 E-UTRAN FDD UE Rx–Tx Time Difference under Time-Domain Measurement Resource
Restriction with Non-MBSFN ABS ....................................................................................................... 2233
A.9.7.3.1 Test Purpose and Environment ......................................................................................................... 2233
A.9.7.3.2 Test parameters ................................................................................................................................. 2233
A.9.7.3.3 Test Requirements ............................................................................................................................. 2236
A.9.7.4 E-UTRAN TDD UE Rx-Tx Time Difference under Time-Domain Measurement Resource
Restriction with Non-MBSFN ABS ....................................................................................................... 2236
A.9.7.4.1 Test Purpose and Environment ......................................................................................................... 2236
A.9.7.4.2 Test Parameters ................................................................................................................................. 2236
A.9.7.4.3 Test Requirements ............................................................................................................................. 2239
A.9.7.5 E-UTRAN FDD UE Rx–Tx time difference under Time Domain Measurement Resource Restriction
with CRS Assistance Information and Non-MBSFN ABS ..................................................................... 2239
A.9.7.5.1 Test Purpose and Environment ......................................................................................................... 2239
A.9.7.5.2 Test parameters ................................................................................................................................. 2239
A.9.7.5.3 Test Requirements ............................................................................................................................. 2242
A.9.7.6 E-UTRAN TDD UE Rx-Tx Time Difference under Time-Domain Measurement Resource
Restriction with CRS Assistance Information and Non-MBSFN ABS .................................................. 2242
A.9.7.6.1 Test Purpose and Environment ......................................................................................................... 2242
A.9.7.6.2 Test Parameters ................................................................................................................................. 2242
A.9.7.6.3 Test Requirements ............................................................................................................................. 2245
A.9.8 RSTD............................................................................................................................................................ 2245
A.9.8.1 E-UTRAN FDD RSTD intra frequency case .......................................................................................... 2245
A.9.8.1.1 Test Purpose and Environment ......................................................................................................... 2245
A.9.8.1.2 Test Requirements ............................................................................................................................. 2247
A.9.8.2 E-UTRAN TDD RSTD intra frequency case ......................................................................................... 2247
A.9.8.2.1 Test Purpose and Environment ......................................................................................................... 2247
A.9.8.2.2 Test Requirements ............................................................................................................................. 2250
A.9.8.3 E-UTRAN FDD-FDD RSTD inter frequency case ................................................................................ 2250
A.9.8.3.1 Test Purpose and Environment ......................................................................................................... 2250
A.9.8.3.2 Test Requirements ............................................................................................................................. 2252
A.9.8.4 E-UTRAN TDD-TDD RSTD inter frequency case ................................................................................ 2252
A.9.8.4.1 Test Purpose and Environment ......................................................................................................... 2252
A.9.8.4.2 Test Requirements ............................................................................................................................. 2254
A.9.8.5 E-UTRAN FDD RSTD Measurement Accuracy in Carrier Aggregation ............................................... 2254
A.9.8.5.1 Test Purpose and Environment ......................................................................................................... 2254
A.9.8.5.2 Test Requirements ............................................................................................................................. 2257
A.9.8.6 E-UTRAN TDD RSTD Measurement Accuracy in Carrier Aggregation............................................... 2257
A.9.8.6.1 Test Purpose and Environment ......................................................................................................... 2257
A.9.8.6.2 Test Requirements ............................................................................................................................. 2260
A.9.8.7 E-UTRAN FDD RSTD Measurement Accuracy in Carrier Aggregation for 20MHz bandwidth .......... 2260
A.9.8.7.1 Test Purpose and Environment ......................................................................................................... 2260
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 61 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.8.7.2 Test Requirements ............................................................................................................................. 2261
A.9.8.8 E-UTRAN TDD RSTD Measurement Accuracy in Carrier Aggregation for 20MHz bandwidth .......... 2261
A.9.8.8.1 Test Purpose and Environment ......................................................................................................... 2261
A.9.8.8.2 Test Requirements ............................................................................................................................. 2262
A.9.8.9 E-UTRAN FDD RSTD Measurement Accuracy in Carrier Aggregation for 10MHz+5MHz ................ 2262
A.9.8.9.1 Test Purpose and Environment ......................................................................................................... 2262
A.9.8.9.2 Test Requirements ............................................................................................................................. 2263
A.9.8.10 E-UTRAN TDD RSTD Measurement Accuracy in Carrier Aggregation for 10MHz+5MHz ............... 2263
A.9.8.10.1 Test Purpose and Environment ......................................................................................................... 2263
A.9.8.10.2 Test Requirements ............................................................................................................................. 2264
A.9.8.11 E-UTRAN FDD RSTD Measurement Accuracy in Carrier Aggregation for 5 + 5MHz bandwidth ...... 2264
A.9.8.11.1 Test Purpose and Environment ......................................................................................................... 2264
A.9.8.11.2 Test Requirements ............................................................................................................................. 2265
A.9.8.12 E-UTRAN TDD RSTD Measurement Accuracy in Carrier Aggregation for 5+5MHz bandwidth ........ 2265
A.9.8.12.1 Test Purpose and Environment ......................................................................................................... 2265
A.9.8.12.2 Test Requirements ............................................................................................................................. 2266
A.9.8.13 E-UTRAN TDD RSTD Measurement Accuracy in Carrier Aggregation for 20MHz+10MHz ............. 2266
A.9.8.13.1 Test Purpose and Environment ......................................................................................................... 2266
A.9.8.13.2 Test Requirements ............................................................................................................................. 2267
A.9.8.14 E-UTRAN FDD RSTD Measurement Accuracy in 3DL Carrier Aggregation ...................................... 2267
A.9.8.14.1 Test Purpose and Environment ......................................................................................................... 2267
A.9.8.14.2 Test Requirements ............................................................................................................................. 2272
A.9.8.15 E-UTRAN TDD RSTD Measurement Accuracy in 3DL Carrier Aggregation ...................................... 2272
A.9.8.15.1 Test Purpose and Environment ......................................................................................................... 2272
A.9.8.15.2 Test Requirements ............................................................................................................................. 2276
A.9.9 RSRP and RSRQ on the serving cell ............................................................................................................ 2276
A.9.9.1 FDD Intra frequency serving cell case .................................................................................................... 2276
A.9.9.1.1 Test Purpose and Environment ......................................................................................................... 2276
A.9.9.1.2 Test parameters ................................................................................................................................. 2276
A.9.9.1.3 Test Requirements ............................................................................................................................. 2278
A.9.9.2 TDD Intra frequency serving cell case ................................................................................................... 2278
A.9.9.2.1 Test Purpose and Environment ......................................................................................................... 2278
A.9.9.2.2 Test parameters ................................................................................................................................. 2278
A.9.9.2.3 Test Requirements ............................................................................................................................. 2280
A.9.10 SSTD ............................................................................................................................................................ 2280
A.9.10.1 EUTRAN FDD-FDD SSTD accuracy in asynchronous DC ................................................................... 2280
A.9.10.1.1 Test Purpose and Environment ......................................................................................................... 2280
A.9.10.1.2 Test parameters ................................................................................................................................. 2280
A.9.10.1.3 Test Requirements ............................................................................................................................. 2282
A.9.10.3 FDD—FDD Inter frequency case ........................................................................................................... 2282
A.9.10.3.1 Test Purpose and Environment ......................................................................................................... 2282
A.9.10.3.2 Test parameters ................................................................................................................................. 2282
A.9.10.3.3 Test Requirements ............................................................................................................................. 2286
A.9.10.4 TDD—TDD Inter frequency case ........................................................................................................... 2286
A.9.10.4.1 Test Purpose and Environment ......................................................................................................... 2286
A.9.10.4.2 Test parameters ................................................................................................................................. 2286
A.9.10.4.3 Test Requirements ............................................................................................................................. 2291
A.9.11 RSSI .................................................................................................................................................................. 2291
A.9.11.1 FS3 average RSSI accuracy case (PCell using FDD) ............................................................................. 2291
A.9.11.1.1 Test Purpose and Environment ......................................................................................................... 2291
A.9.11.1.2 Test parameters ................................................................................................................................. 2291
A.9.11.1.3 Test Requirements ............................................................................................................................. 2293
A.9.11.2 FS3 average RSSI accuracy case (PCell using TDD) ............................................................................. 2293
A.9.11.2.1 Test Purpose and Environment ......................................................................................................... 2293
A.9.11.2.2 Test parameters ................................................................................................................................. 2293
A.9.12 Channel occupancy....................................................................................................................................... 2295
A.9.12.1 FS3 channel occupancy test (PCell using FDD) ..................................................................................... 2295
A.9.12.1.1 Test Purpose and Environment ......................................................................................................... 2295
A.9.12.1.2 Test parameters ................................................................................................................................. 2295
A.9.12.1.3 Test Requirements ............................................................................................................................. 2297
A.9.12.2 FS3 channel occupancy test (PCell using TDD) ..................................................................................... 2297
A.9.12.2.1 Test Purpose and Environment ......................................................................................................... 2297
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 62 ETSI TS 136 133 V14.3.0 (2017-04)
A.9.12.2.2 Test parameters ................................................................................................................................. 2297
A.9.13 RS-SINR ...................................................................................................................................................... 2299
A.9.13.1 FDD Intra-Frequency Case ..................................................................................................................... 2299
A.9.13.1.1 Test Purpose and Environment ......................................................................................................... 2299
A.9.13.1.2 Test parameters ................................................................................................................................. 2299
A.9.13.1.3 Test Requirements ............................................................................................................................. 2301
A.9.13.2 TDD Intra-Frequency Case ..................................................................................................................... 2301
A.9.13.2.1 Test Purpose and Environment ......................................................................................................... 2301
A.9.13.2.2 Test parameters ................................................................................................................................. 2301
A.9.13.2.3 Test Requirements ............................................................................................................................. 2304
A.9.13.5 FDD—TDD Inter frequency case ........................................................................................................... 2304
A.9.13.5.1 Test Purpose and Environment ......................................................................................................... 2304
A.9.13.5.2 Test parameters ................................................................................................................................. 2304
A.9.13.5.3 Test Requirements ............................................................................................................................. 2308
A.9.13.6 TDD—FDD Inter frequency case ........................................................................................................... 2308
A.9.13.6.1 Test Purpose and Environment ......................................................................................................... 2308
A.9.13.6.2 Test parameters ................................................................................................................................. 2308
A.9.13.6.3 Test Requirements ............................................................................................................................. 2311
A.10 Proximity-based Services in Any Cell Selection State.......................................................................2311
A.10.1 E-UTRAN FDD – UE ProSe Direct Communication Transmission Timing Accuracy Test ....................... 2311
A.10.1.1 Test Purpose and Environment ............................................................................................................... 2311
A.10.1.2 Test Requirements .................................................................................................................................. 2312
A.10.2 E-UTRAN FDD – Initiation/Cease of SLSS Transmission with ProSe Direct Communication.................. 2313
A.10.2.1 Test Purpose and Environment ............................................................................................................... 2313
A.10.2.2 Test Requirements .................................................................................................................................. 2314
A.10.3 E-UTRAN FDD – SyncRef UE Selection / Reselection Test ...................................................................... 2314
A.10.3.1 Test Purpose and Environment ............................................................................................................... 2314
A.10.3.2 Test Requirements .................................................................................................................................. 2316
A.10.4 E-UTRAN FDD – Cell Identification on downlink frequency associated with ProSe frequency (when
UE is transmitting for ProSe) ....................................................................................................................... 2317
A.10.4.1 Test Purpose and Environment ............................................................................................................... 2317
A.10.4.2 Test Requirements ............................................................................................................................. 2319
A.11 V2V Sidelink Communication for V2V Operation on Dedicated V2V Carrier.................................2319
A.11.1 V2V UE Transmission Timing Accuracy Test ............................................................................................. 2319
A.11.1.1 Test Purpose and Environment ............................................................................................................... 2319
A.11.1.2 Test requirements .................................................................................................................................... 2320
A.11.2 Interruptions due to V2V sidelink communication ................................................................................. 2320
A.11.2.1 Test Purpose and Environment ......................................................................................................... 2320
Annex B (normative): Conditions for RRM requirements applicability for operating bands .2323
B.1 Conditions for E-UTRAN RRC_IDLE state mobility .......................................................................2323
B.1.1 Conditions for measurements of intra-frequency E-UTRAN cells for cell re-selection ............................... 2323
B.1.2 Conditions for measurements of inter-frequency E-UTRAN cells for cell re-selection ............................... 2323
B.1.3 Conditions for measurements of intra-frequency E-UTRAN cells for cell re-selection for UE Category
M1 ................................................................................................................................................................ 2323
B.1.4 Conditions for measurements of intra-frequency NB-IoT cells for cell re-selection for UE Category
NB1 .............................................................................................................................................................. 2325
B.1.5 Conditions for measurements of inter-frequency NB-IoT cells for cell re-selection for UE Category
NB1 .............................................................................................................................................................. 2325
B.2 Conditions for UE Measurements Procedures in RRC_CONNECTED State ...................................2326
B.2.1 Conditions for E-UTRAN intra-frequency measurements ........................................................................... 2326
B.2.2 Conditions for E-UTRAN intra-frequency measurements with autonomous gaps ...................................... 2326
B.2.3 Conditions for E-UTRAN inter-frequency measurements ........................................................................... 2326
B.2.4 Conditions for E-UTRAN inter-frequency measurements with autonomous gaps ...................................... 2327
B.2.5 Conditions for E-UTRAN OTDOA intra-frequency RSTD Measurements ................................................. 2327
B.2.6 Conditions for E-UTRAN OTDOA inter-frequency RSTD Measurements ................................................. 2328
B.2.7 Conditions for Measurements of the secondary component carrier with deactivated SCell ........................ 2328
B.2.8 Conditions for E-UTRAN Intra-Frequency Measurements under Time Domain Measurement Resource
Restriction .................................................................................................................................................... 2329
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 63 ETSI TS 136 133 V14.3.0 (2017-04)
B.2.9 Conditions for E-UTRAN Intra-Frequency Measurements under Time Domain Measurement Resource
Restriction with CRS Assistance Information .............................................................................................. 2329
B.2.10 Conditions for E-UTRAN intra-frequency discovery signal measurements ................................................ 2330
B.2.10.1 Conditions for E-UTRAN intra-frequency CRS-based measurements ................................................... 2330
B.2.10.2 Conditions for E-UTRAN intra-frequency CSI-RS based measurements .............................................. 2330
B.2.11 Conditions for E-UTRAN inter-frequency discovery signal measurements ................................................ 2330
B.2.11.1 Conditions for E-UTRAN inter-frequency CRS-based measurements ................................................... 2330
B.2.11.2 Conditions for E-UTRAN inter-frequency CSI-RS based measurements .............................................. 2331
B.2.12 Conditions for E-UTRAN intra-frequency discovery signal measurements under operation with frame
structure 3 ..................................................................................................................................................... 2331
B.2.13 Conditions for E-UTRAN inter-frequency discovery signal measurements under operation with frame
structure 3 ..................................................................................................................................................... 2332
B.2.13.1 Conditions for E-UTRAN inter-frequency CRS-based measurements ................................................... 2332
B.2.13.2 Conditions for E-UTRAN inter-frequency CSI-RS based measurements .............................................. 2332
B.2.14 Conditions for E-UTRAN intra-frequency measurements by UE Category M1 .......................................... 2332
B.2.15 Conditions for NB-IoT intra-frequency measurements by UE Category NB1 ............................................. 2334
B.3 Conditions for measurements performance requirements for UE ......................................................2334
B.3.1 Conditions for intra-frequency RSRP and RSRQ Accuracy Requirements ................................................. 2334
B.3.2 Void .............................................................................................................................................................. 2335
B.3.3 Conditions for inter-frequency RSRP and RSRQ Accuracy Requirements ................................................. 2335
B.3.4 Conditions for inter-frequency relative RSRP and RSRQ Accuracy Requirements .................................... 2335
B.3.5 Conditions for UE Rx – Tx time difference ................................................................................................. 2335
B.3.6 Conditions for intra-frequency Reference Signal Time Difference (RSTD) measurements ........................ 2335
B.3.7 Conditions for inter-frequency RSTD measurements .................................................................................. 2335
B.3.8 Conditions for Intra-Frequency Relative RSRP Accuracy Requirements .................................................... 2336
B.3.9 Conditions for Intra-Frequency Absolute RSRP and RSRQ Accuracy Requirements under Time
Domain Measurement Resource Restriction ................................................................................................ 2336
B.3.10 Conditions for Intra-Frequency Relative RSRP Accuracy Requirements under Time Domain
Measurement Resource Restriction .............................................................................................................. 2336
B.3.11 Conditions for Intra-Frequency Absolute RSRP and RSRQ Accuracy Requirements under Time
Domain Measurement Resource Restriction with CRS Assistance Information .......................................... 2336
B.3.12 Conditions for Intra-Frequency Relative RSRP Accuracy Requirements under Time Domain
Measurement Resource Restriction with CRS Assistance Information........................................................ 2337
B.3.13 Conditions for UE Rx–Tx Time Difference Measurement under Time Domain Measurement Resource
Restriction with CRS Assistance Information .............................................................................................. 2337
B.3.14 Conditions for Intra-Frequency Absolute Discovery Signal Measurement Accuracy Requirements........... 2337
B.3.14.1 Conditions for Intra-frequency CRS-based measurements ..................................................................... 2337
B.3.14.2 Conditions for Intra-frequency CSI-RS-based measurements ................................................................ 2337
B.3.15 Conditions for Intra-Frequency Relative Discovery Signal Measurement Accuracy Requirements............ 2338
B.3.15.1 Conditions for Intra-frequency CRS-based measurements ..................................................................... 2338
B.3.15.2 Conditions for Intra-frequency CSI-RS-based measurements ................................................................ 2338
B.3.16 Conditions for Inter-Frequency Absolute Discovery Signal Measurement Accuracy Requirements........... 2338
B.3.16.1 Conditions for Inter-frequency CRS-based measurements ..................................................................... 2338
B.3.16.2 Conditions for Inter-frequency CSI-RS-based measurements ................................................................ 2338
B.3.17 Conditions for Inter-Frequency Relative Discovery Signal Measurement Accuracy Requirements............ 2339
B.3.17.1 Conditions for Inter-frequency CRS-based measurements ..................................................................... 2339
B.3.17.2 Conditions for Inter-frequency CSI-RS-based measurements ................................................................ 2339
B.3.18 Conditions for Intra-frequency Absolute RS-SINR Accuracy Requirements .............................................. 2339
B.3.19 Conditions for Inter-frequency Absolute RS-SINR Accuracy Requirements .............................................. 2339
B.3.20 Conditions for Inter-frequency Relative RS-SINR Accuracy Requirements ............................................... 2339
B.3.21 Conditions for Intra-Frequency Absolute Accuracy Requirements for Measurements under Operation
with Frame Structure 3 ................................................................................................................................. 2339
B.3.21.1 Conditions for RSRP measurements ....................................................................................................... 2339
B.3.21.2 Conditions for RSRQ measurements ...................................................................................................... 2340
B.3.21.3 Conditions for CSI-RSRP measurements ............................................................................................... 2340
B.3.22 Conditions for Intra-Frequency Relative Accuracy Requirements for Measurements under Operation
with Frame Structure 3 ................................................................................................................................. 2340
B.3.22.1 Conditions for RSRP measurements ....................................................................................................... 2340
B.3.22.2 Void ........................................................................................................................................................ 2341
B.3.22.3 Conditions for CSI-RSRP measurements ............................................................................................... 2341
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 64 ETSI TS 136 133 V14.3.0 (2017-04)
B.3.23 Conditions for Inter-Frequency Absolute Accuracy Requirements for Measurements under Operation
with Frame Structure 3 ................................................................................................................................. 2341
B.3.23.1 Conditions for RSRP measurements ....................................................................................................... 2341
B.3.23.2 Conditions for RSRQ measurements ...................................................................................................... 2341
B.3.23.3 Conditions for CSI-RSRP measurements ............................................................................................... 2341
B.3.24 Conditions for Inter-Frequency Relative Accuracy Requirements for Measurements under Operation
with Frame Structure 3 ................................................................................................................................. 2341
B.3.24.1 Conditions for RSRP measurements ....................................................................................................... 2341
B.3.24.2 Conditions for RSRQ measurements ...................................................................................................... 2342
B.3.24.3 Conditions for CSI-RSRP measurements ............................................................................................... 2342
B.3.25 Conditions for NB-IoT intra-frequency Absolute NRSRP and NRSRQ Accuracy Requirements for UE
Category NB1 ............................................................................................................................................... 2342
B.3.26 Conditions for NB-IoT inter-frequency Absolute NRSRP and NRSRQ Accuracy Requirements for UE
Category NB1 ............................................................................................................................................... 2342
B.4 RRM Requirements Exceptions .........................................................................................................2342
B.4.1 General ......................................................................................................................................................... 2342
B.4.2 Receiver sensitivity relaxation for UE supporting CA ................................................................................. 2342
B.4.3 Receiver sensitivity relaxation for UE configured with CA ......................................................................... 2343
B.4.3.1 Inter-band carrier aggregation................................................................................................................. 2343
B.4.3.2 Intra-band non-contiguous carrier aggregation ....................................................................................... 2343
B.4.3.3 Inter-band carrier aggregation with operating bands without uplink band ............................................. 2343
B.5 Conditions for Measurement Performance Requirements for ProSe UE ...........................................2343
B.5.1 Conditions for S-RSRP Accuracy Requirements ......................................................................................... 2343
B.5.2 Conditions for Relative S-RSRP Accuracy Requirements ........................................................................... 2344
B.5.3 Conditions for Selection/Reselection to Intra-frequency SyncRef UE ......................................................... 2344
B.5.4 Conditions for SD-RSRP Accuracy Requirements ...................................................................................... 2345
B.5.5 Conditions for Relative SD-RSRP Accuracy Requirements ........................................................................ 2345
B.6 Conditions for V2X ............................................................................................................................2346
B.6.1 Conditions for GNSS Reliability Requirements ........................................................................................... 2346
B.6.2 Conditions for Absolute S-RSRP Accuracy Requirements .......................................................................... 2346
B.6.3 Conditions for Relative S-RSRP Accuracy Requirements ........................................................................... 2346
B.6.4 Conditions for Selection/Reselection to Intra-frequency SyncRef UE ......................................................... 2346
B.6.5 Conditions for Absolute PSSCH-RSRP Accuracy Requirements ................................................................ 2347
Annex C (informative): Change history: ..........................................................................................2348
History ..........................................................................................................................................................2388
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 65 ETSI TS 136 133 V14.3.0 (2017-04)
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.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 66 ETSI TS 136 133 V14.3.0 (2017-04)
1 Scope
The present document specifies requirements for support of Radio Resource Management for the FDD and TDD modes
of Evolved UTRA. These requirements include requirements on measurements in UTRAN and the UE as well as
requirements on node dynamical behaviour and interaction, in terms of delay and response characteristics.
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 TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
procedures in idle mode"
[2] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC) protocol specification".
[3] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures"
[4] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer;
Measurements"
[5] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception"
[6] 3GPP TS 25.302: "Services provided by the Physical Layer".
[7] 3GPP TS 25.331: "RRC Protocol Specification".
[8] 3GPP TS 45.008: "Radio subsystem link control".
[9] 3GPP TS 45.005: "Radio transmission and reception".
[10] 3GPP TS 45.010: "Radio subsystem synchronization".
[11] 3GPP2 C.S0024-B: "cdma2000 High Rate Packet Data Air Interface Specification".
[12] 3GPP2 C.S0002-D: "Physical Layer Standard for cdma2000 Spread Spectrum Systems - Release
A".
[13] 3GPP2 C.S0033-B: "Recommended Minimum Performance Standards for cdma2000 High Rate
Packet Data Access Terminal".
[14] 3GPP2 C.S0011-C: "Recommended Minimum Performance Standards for cdma2000 Spread
Spectrum Mobile Stations".
[15] 3GPP2 C.S0005-D: Upper Layer (Layer 3) Signaling Specification for cdma2000 Spread
Spectrum Systems
[16] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and
Modulation”
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 67 ETSI TS 136 133 V14.3.0 (2017-04)
[17] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification".
[18] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)".
[19] 3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)".
[20] 3GPP TS 25.214: "Physical layer procedures (FDD)".
[21] 3GPP TS 36. 212 "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
channel coding".
[22] 3GPP TS 36.302: "Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by
the physical layer".
[23] 3GPP TS 36.521-3: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment
(UE) conformance specification; Radio transmission and reception; Part 3: Radio Resource
Management conformance testing".
[24] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning
Protocol (LPP)".
[25] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2"
[26] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[27] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial
Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT);
Overall description; Stage 2"
[28] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2
Application Protocol (X2AP)".
[29] 3GPP TS 25.101: "UE Radio transmission and reception (FDD)".
[30] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS)
radio transmission and reception".
[31] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio access capabilities".
[32] IEEE Standard 802.11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications.
[33] 3GPP TS 23.303: "Technical Specification Group Services and System Aspects; Proximity-based
services (ProSe); Stage 2".
[34] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[35] 3GPP TS 36.171: " Requirements for Support of Assisted Global Navigation Satellite System (A-
GNSS)".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [26] 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 [26].
Any Cell Selection state: as defined in TS 36.304 [1]
Asynchronous Dual Connectivity: As defined in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 68 ETSI TS 136 133 V14.3.0 (2017-04)
Carrier aggregation: aggregation of two or more component carriers in order to support wider transmission
bandwidths TS 36.104 [30].
Dual Connectivity: As defined in TS 36.331 [2].
Extended IDLE-mode DRX: extended DRX cycles in IDLE mode as specified in TS 24.008 [34], where one extended
DRX cycle is a time period between two first paging occasions within two consecutive PTWs.
Extended CONNECTED-mode DRX: extended DRX cycles in CONNECTED mode as specified in TS 36.331 [2].
Frame Structure 3: frame structure type 3 as defined in TS 36.211 [16]
High operating band: an operating band with a higher downlink frequency with respect to another, low, operating
band.
Inter-band carrier aggregation: carrier aggregation of component carriers in different operating bands
TS 36.104 [30].
Intra-band contiguous carrier aggregation: contiguous carriers aggregated in the same operating band
TS 36.104 [30].
Intra-band non-contiguous carrier aggregation: non-contiguous carriers aggregated in the same operating band
TS 36.104 [30].
IDC autonomous denial subframes: The maximum number of uplink subframes in which the UE is allowed not to
transmit E-UTRAN signals when configured with IDC autonomous denial (TS 36.331 [2]).
IDC autonomous denial validity: It is the period over which the autonomous denial subframes are counted
(TS 36.331 [2]).
IDC solution: This refers to DRX or IDC autonomous denial configured by eNodeB in response to receiving
InDeviceCoexIndication from the UE (TS 36.331 [2]).
Low operating band: an operating band with a lower downlink frequency with respect to another, high, operating
band.
Master Cell Group: As defined in TS 36.331 [2].
Master eNB: As defined in TS 36.300 [25].MBSFN ABS: ABS configured in MBSFN-configurable subframe.
NB-IoT Cell: A cell for NB-IoT.
NB-IoT: As defined in TS 36.331 [2].
Non-MBSFN ABS: ABS configured in any downlink subframe.
Normal Performance Group: For UE which supports Increased UE carrier monitoring UTRA or E-UTRA the group
of inter-frequency carriers or inter-RAT carriers is divided into two groups. The group which has a better delay
performance compared to the other group is refered to as the normal performance group
Paging Time Window: As defined in TS 24.008 [34].
Primary Cell: As defined in TS 36.331 [2].
ProSe Direct Communication: As defined in TS 23.303 [33]
ProSe Direct Discovery: As defined in TS 23.303 [33]
Primary SCell: As defined in TS 36.331 [2].
Primary Secondary Timing Advance Group: Timing Advance Group containing the PSCell.
Primary Timing Advance Group: Timing Advance Group containing the PCell.
Reduced Performance Group: For UE which supports Increased UE carrier monitoring UTRA or E-UTRA the group
of inter-frequency carriers or inter-RAT carriers is divided into two groups. The group which has worse delay
performance compared to the other group is refered to as the reduced performance group
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 69 ETSI TS 136 133 V14.3.0 (2017-04)
Secondary Cell: As defined in TS 36.331 [2].
Secondary eNB: As defined in TS 36.300 [25].
Serving Cell: As defined in TS 36.331 [2].
Secondary Cell Group: As defined in TS 36.331 [2].
Secondary Timing Advance Group: As defined in TS 36.331 [2].
Synchronous Dual Connectivity: As defined in TS 36.331 [2].
TDD-FDD carrier aggregation: Carrier aggregation of component carriers in E-UTRA TDD and E-UTRA FDD
operating bands TS 36.104 [30].
Timing Advance Group: As defined in TS 36.331 [2].
WLAN RSSI: As defined in TS36.214 [4].
x_RA: x-to-RS EPRE ratio for the channel or physical signal x in all transmitted OFDM symbols not containing RS.
x_RB: x-to-RS EPRE ratio for the channel or physical signal x in all transmitted OFDM symbols containing RS.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
[…] Values included in square bracket must be considered for further studies, because it means that a
decision about that value was not taken.
BWChannel Channel bandwidth, defined in TS 36.101 subclause 3.2
CPICH_Ec Average energy per PN chip for the CPICH
CPICH_Ec/Io The ratio of the received energy per PN chip for the CPICH to the total received power spectral
density at the UE antenna connector.
Ec Average energy per PN chip.
Ês Received energy per RE (power normalized to the subcarrier spacing) during the useful part of the
symbol, i.e. excluding the cyclic prefix, at the UE antenna connector
Io The total received power density, including signal and interference, as measured at the UE antenna
connector.
Ioc The power spectral density (integrated in a noise bandwidth equal to the chip rate and normalized
to the chip rate) of a band limited noise source (simulating interference from cells, which are not
defined in a test procedure) as measured at the UE antenna connector.
Iot The received power spectral density of the total noise and interference for a certain RE (power
integrated over the RE and normalized to the subcarrier spacing) as measured at the UE antenna
connector
NSCH_RP Received (linear) average power of the resource elements that carry Narrowband synchronisation
signal, measured at the UE antenna connector
N oc The power spectral density of a white noise source (average power per RE normalised to the
subcarrier spacing), simulating interference from cells that are not defined in a test procedure, as
measured at the UE antenna connector
N PRS Number of consecutive downlink positioning subframes as defined in clause 6.10.4.3 in TS 36.211
nPRB Physical Resource Block number as defined in clause 3.1 in TS 36.211.
N TA Timing offset between uplink and downlink radio frames at the UE, as defined in clause 3.1 in TS
36.211.
N TA offset Fixed timing advance offset, as defined in clause 3.1 in TS 36.211.
PCMAX Configured UE transmitted power as defined in clause 6.2.5 in TS 36.101.
PCMAX ,c Configured UE transmitted power on a serving cell c as defined in clause 6.2.5A in TS 36.101.
PRP Received (linear) average power of the resource elements that carry E-UTRA PRS, measured at
the UE antenna connector.
S Cell Selection Criterion defined in TS 36.304, subclause 5.2.3.2 for E-UTRAN
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 70 ETSI TS 136 133 V14.3.0 (2017-04)
SCH_Ec/Ior The ratio of the transmit energy per PN chip of the SCH to the total transmit power spectral
density at the UTRA Node B antenna connector
SCH_RP Received (linear) average power of the resource elements that carry E-UTRA synchronisation
signal, measured at the UE antenna connector
Srxlev Cell selection RX level, defined in TS 36.304, subclause 5.2.3.2
Squal Cell selection quality, defined in TS 36.304, subclause 5.2.3.2
Sintersearch Defined in TS 25.304, subclause 5.2.6.1.5
Sintrasearch Defined in TS 25.304, subclause 5.2.6.1.5 for UTRAN and in TS 36.304 , subclause 5.2.4.7 for E-
UTRAN
Snonintrasearch Defined in TS 36.304 , subclause 5.2.4.7
SsearchRAT Defined in TS 25.304, subclause 5.2.6.1.5
Threshx, high Defined in TS 36.304 , subclause 5.2.4.7
Threshx, low Defined in TS 36.304 , subclause 5.2.4.7
Threshserving, low Defined in TS 36.304 , subclause 5.2.4.7
TPRS Cell-specific positioning subframe configuration period as defined in clause 6.10.4.3 in TS 36.211
TRE-ESTABLISH-REQ The RRC Re-establishment delay requirement, the time between the moment when erroneous
CRCs are applied, to when the UE starts to send preambles on the PRACH.
Treselection Defined in TS 25.304, subclause 5.2.6.1.5
TreselectionRAT Defined in TS 36.304 , subclause 5.2.4.7
TreselectionEUTRA Defined in TS 36.304 , subclause 5.2.4.7
TreselectionUTRA Defined in TS 36.304 , subclause 5.2.4.7
TreselectionGERA Defined in TS 36.304 , subclause 5.2.4.7
TS Basic time unit, defined in TS 36.211, clause 4
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [26] 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 [26].
1x RTT CDMA2000 1x Radio Transmission Technology
ABS Almost Blank Subframe
ARQ Automatic Repeat Request
AP Access Point
AWGN Additive White Gaussian Noise
BCCH Broadcast Control Channel
BCH Broadcast Channel
CA Carrier Aggregation
CC Component Carrier
CCCH SDU Common Control Channel SDU
CE Coverage Enhancement
CGI Cell Global Identifier
CPICH Common Pilot Channel
CPICH Ec/No CPICH Received energy per chip divided by the power density in the band
CRS Cell-specific Reference Signals
C-RNTI Cell RNTI
CSI Channel-State Information
CSI-RS CSI Reference Signal
DC Dual Connectivity
DCCH Dedicated Control Channel
DL Downlink
DMTC Discovery signal Measurement Timing Configuration
DRX Discontinuous Reception
DTCH Dedicated Traffic Channel
DUT Device Under Test
E-CID Enhanced Cell-ID (positioning method)
ECGI Evolved CGI
eDRX_IDLE Extended IDLE-mode DRX
eDRX_CONN Extended CONNECTED-mode DRX
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 71 ETSI TS 136 133 V14.3.0 (2017-04)
eNB E-UTRAN NodeB
E-SMLC Enhanced Serving Mobile Location Centre
E-UTRA Evolved UTRA
E-UTRAN Evolved UTRAN
FDD Frequency Division Duplex
FS3 Frame Structure type 3
GERAN GSM EDGE Radio Access Network
GNSS Global Navigational Satellite System
GSM Global System for Mobile communication
HARQ Hybrid Automatic Repeat Request
HD-FDD Half-Duplex FDD
HO Handover
HRPD High Rate Packet Data
IDC In-Device Coexistence
IEEE Institute of Electrical and Electronics Engineers
LBT Listen before talk
LPP LTE Positioning Protocol
LWA LTE-WLAN Aggregation
MAC Medium Access Control
MCG Master Cell Group
MeNB Master eNB
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MBSFN ABS MBSFN Almost Blank Subframe
MDT Minimization of Drive Tests
MGRP Measurement Gap Repetition Period
MIB Master Information Block
MPDCCH MTC Physical Downlink Control Channel
NPBCH Narrowband Physical Broadcast CHannel
NPDCCH Narrowband Physical Downlink Control CHannel
NPDSCH Narrowband Physical Downlink Shared CHannel
NPRACH Narrowband Physical Random Access CHannel
NPUSCH Narrowband Physical Uplink Shared CHannel
NPSS Narrowband Primary Synchronization Signal
NRS Narrowband Refernce Signal
NRSRP Narrowband Reference Signal Received Power
NRSRQ Narrowband Reference Signal Received Quality
NSCH Narrowband Synchronization Channel
NSSS Narrowband Secondary Synchronization Signal
OCNG OFDMA Channel Noise Generator
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
OTDOA Observed Time Difference of Arrival
PBCH Physical Broadcast Channel
P-CCPCH Primary Common Control Physical Channel
PCell Primary Cell
PCFICH Physical Control Format Indicator CHannel
PDCCH Physical Downlink Control CHannel
PDSCH Physical Downlink Shared CHannel
PHICH Physical Hybrid-ARQ Indicator CHannel
PLMN Public Land Mobile Network
PMCH Physical Multicast Channel
PRACH Physical Random Access CHannel
ProSe Proximity-based Services
PRS Positioning Reference Signal
PSBCH Physical Sidelink Broadcast CHannel
PSCCH Physical Sidelink Control Channel
PSCell Primary SCell
PSS Primary Synchronization SignalPSSCH Physical Sidelink Shared CHannel
psTAG Primary Secondary Timing Advance Group
pTAG Primary Timing Advance Group
PTW Paging Time Window
PUCCH Physical Uplink Control CHannel
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 72 ETSI TS 136 133 V14.3.0 (2017-04)
PUSCH Physical Uplink Shared Channel
RS-SINR Reference Signal Signal to Noise and Interference RatioRSCP Received Signal Code Power
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
RSSI Received Signal Strength Indicator
RSTD Reference Signal Time Difference
QAM Quadrature Amplitude Modulation
RACH Random Access Channel
RAT Radio Access Technology
RNC Radio Network Controller
RNTI Radio Network Temporary Identifier
RRC Radio Resource Control
RRM Radio Resource Management
SCE Small Cell Enhancement
SCH Synchronization Channel
SCell Secondary Cell
SCG Secondary Cell GroupSDU Service Data Unit
SeNB Secondary eNB
SFN System Frame Number
SI System Information
SIB System Information Block
SLSS SideLink Synchronization Sequence
SON Self Optimized Network
SRS Sounding Reference Signal
SSS Secondary Synchronization Signal
SSTD SFN and subframe time difference
sTAG Secondary Timing Advance Group
TAG Timing Advance Group
TDD Time Division Duplex
TP Transmission Point
TTI Transmission Time Interval
UE User Equipment
UL Uplink
UMTS Universal Mobile Telecommunication System
UTRA Universal Terrestrial Radio Access
UTRAN Universal Terrestrial Radio Access Network
V2V Vehicle to Vehicle
V2X Vehicle to Everything
WLAN Wireless Local Area Network
WB-RSRQ Wide Bandwith RSRQ
3.4 Test tolerances
The requirements given in the present document make no allowance for measurement uncertainty. The test specification
36.521-3 [23] defines the test tolerances. These test tolerances are individually calculated for each test. The test
tolerances are then added to the limits in this specification to create test limits. The measurement results are compared
against the test limits as defined by the shared risk principle.
Shared Risk is defined in [ETR 273 Part 1 sub-part 2 clause 6.5].
3.5 Additional notation
3.5.1 Groups of bands
The intention with the band grouping below is to increase the readability of the specification.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 73 ETSI TS 136 133 V14.3.0 (2017-04)
Table 3.5.1-1: E-UTRA band groups
Group E-UTRA FDD E-UTRA TDD E-UTRA Frame Structure 3
Band Band group Band group Operating
group Operating bands notation Operating bands notation bands
notation
A FDD_A 1, 4, 6, 10, 11, 18, 19, TDD_A FS3_A -
33, 34, 35, 36, 37,
21, 23, 24, 32 Note 2,
38, 39, 40, 45
67Note 2, 69Note 2, 70Note 7
B FDD_B 65, 66 Note 5 TDD_B - FS3_B -
C FDD_C 9, 30 TDD_C 42, 43, 48 FS3_C -
D FDD_D 28 TDD_D - FS3_D -
E FDD_E 2, 5, 7, 27 TDD_E 41, 44 FS3_E -
F FDD_F 26 Note 3 TDD_F - FS3_F -
G FDD_G 3, 8, 12, 13, 14, 17, 20, TDD_G 47 Note4 FS3_G 46 Note 2
22, 29 Note 2
H FDD_H 25 TDD_H - FS3_H -
I FDD_I - TDD_I - FS3_I -
J FDD_J - TDD_J - FS3_J -
K FDD_K - TDD_K - FS3_K -
L FDD_L - TDD_L - FS3_L -
M FDD_M - TDD_M - FS3_M -
N FDD_N 31 TDD_N - FS3_N -
NOTE 1: The bands within the same group have the same Io conditions in a corresponding requirement in this
specification.
NOTE 2: This band is used only for E-UTRA carrier aggregation with other E-UTRA bands.
NOTE 3: The minimum Io condition for Band 26 is reduced by 0.5 dB when the carrier frequency of the assigned E-
UTRA channel bandwidth is within 865-894 MHz.
NOTE 4: This band is used only for V2V operation.
NOTE 5: The range 2180-2200 MHz of the DL operating band 66 is restricted to E-UTRA operation when carrier
aggregation is configured.
NOTE 6: Void
NOTE 7: The range 2010-2020 MHz of the DL operating band is restricted to E-UTRA operation when carrier
aggregation is configured and TX-RX separation is 300 MHz The range 2005-2020 MHz of the DL operating
band is restricted to E-UTRA operation when carrier aggregation is configured and TX-RX separation is 295
MHz
Table 3.5.1-2: Band groups for NB-IoT
Group E-UTRA FDD E-UTRA TDD
Band Band group
group Operating bands notation Operating bands
notation
A NFDD_A - NTDD_A -
B NFDD_B - NTDD_B -
C NFDD_C - NTDD_C -
D NFDD_D - NTDD_D -
E NFDD_E - NTDD_E -
F NFDD_F - NTDD_F -
G NFDD_G 1, 2, 3, 5, 8, 11, 12, 13, NTDD_G -
17, 18, 19, 20, 25, 26,
28, 31, 66, 70
H NFDD_H - NTDD_H -
I NFDD_I - NTDD_I -
J NFDD_J - NTDD_J -
K NFDD_K - NTDD_K -
L NFDD_L - NTDD_L -
M NFDD_M - NTDD_M -
N NFDD_N - NTDD_N -
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 74 ETSI TS 136 133 V14.3.0 (2017-04)
3.6 General
3.6.1 Applicability of requirements in this specification version
- The requirements for TDD-FDD carrier aggregation are specified for two downlink and one uplink component
carriers. The requirements are specified for both cases when the PCell belongs to TDD or FDD.
- All the requirements for intra-band contiguous and non-contiguous CA apply under the assumption of the same
uplink-downlink and special subframe configurations [16] in the PCell and SCell.
- All the requirements for inter-band CA apply for the same uplink-downlink and special subframe configurations
[16] in the PCell and SCell. Different uplink-downlink and special subframe configurations [16] in the PCell and
SCell are supported for inter-band CA for UEs which:
- do not support simultaneous reception and transmission for inter-band TDD CA specified in TS 36.331 [2], and
- are compliant to the requirements specified in TS 36.101 for inter-band CA with uplink in one E-UTRA band
and without simultaneous Rx/Tx.
- All the inter-frequency requirements and requirements for measurements on deactivated carrier apply for the
same uplink-downlink and special subframe configurations [16] in the PCell and SCell. Different uplink-
downlink and special subframe configurations [16] in the PCell and SCell are supported for inter-frequency for
UEs which:
- do not support simultaneous reception and transmission for inter-band TDD CA specified in TS 36.331 [2],
and are compliant to the requirements specified in TS 36.101 for inter-band CA with uplink in one E-UTRA
band and without simultaneous Rx/Tx.
- Requirements for E-UTRA carrier aggregation are applicable for the CA capable UE which has been configured
with at least one downlink SCell, but:
- up to four downlink CCs and up to two uplink CCs for inter-band carrier aggregation, or
- up to four downlink CCs and up to two uplink CCs for intra-band contiguous carrier aggregation, or
- up to four downlink CCs and one uplink CCs for inter-band carrier aggregation, or
- up to two downlink/uplink CCs intra-band contiguous and one downlink/uplink inter-band carrier
aggregation, or
- up to two downlink CCs intra-band contiguous and one downlink inter-band and up to two uplink CCs for
inter-band carrier aggregation, or
- up to two downlink CCs intra-band non-contiguous and one downlink inter-band and up to two uplink CCs
for inter-band carrier aggregation, or
- up to three downlink CCs intra-band contiguous and one downlink intra-band non-contiguous and up to two
uplink CCs intra-band contiguous for carrier aggregation, or
- two sub-blocks intra-band non-contiguous with two downlink CCs intra-band contiguous per sub-blocks and
up to two uplink CCs intra-band contiguous for carrier aggregation, or
- two downlink CCs intra-band contiguous and three down link CCs inter-band and one uplink CC for carrier
aggregation, or
- two downlink CCs intra-band contiguous and two downlink CCs intra-band contiguous and one downlink CC
inter-band and one uplink CC for carrier aggregation, or
- up to two downlink CCs and up to two uplink CCs for intra-band non-contiguous carrier aggregation, or
- up to two downlink CCs and up to two uplink CCs for inter-band carrier aggregation, or
- up to two downlink CCs intra-band contiguous and one downlink inter-band and one uplink CC for carrier
aggregation, or
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 75 ETSI TS 136 133 V14.3.0 (2017-04)
- up to two downlink CCs intra-band non-contiguous and one downlink inter-band and one uplink CC for
carrier aggregation, or
- up to two downlink CCs and one uplink CC for intra-band non-contiguous carrier aggregation.
- Requirements for E-UTRA carrier aggregation for discovery signal measurements are applicable for CA capable
UE which has been configured with at least one downlink SCell, but:
- up to four downlink CCs and up to two uplink CCs for inter-band carrier aggregation, or
- up to four downlink CCs and up to two uplink CCs for intra-band contiguous carrier aggregation, or
- up to four downlink CCs and up to one uplink CCs for inter-band carrier aggregation, or
- up to two downlink/uplink CCs intra-band contiguous and one downlink/uplink inter-band carrier
aggregation, or
- up to two downlink CCs intra-band contiguous and one downlink inter-band and up to two uplink CCs for
inter-band carrier aggregation, or
- up to two downlink CCs intra-band non-contiguous and one downlink inter-band and up to two uplink CCs
for inter-band carrier aggregation, or
- up to three downlink CCs intra-band contiguous and one downlink intra-band non-contiguous and up to two
uplink CCs intra-band contiguous for carrier aggregation, or
- two sub-blocks intra-band non-contiguous with two downlink CCs intra-band contiguous per sub-blocks and
up to two uplink CCs intra-band contiguous for carrier aggregation, or
- two downlink CCs intra-band contiguous and three down link CCs inter-band and one uplink CC for carrier
aggregation, or
- two downlink CCs intra-band contiguous and two downlink CCs intra-band contiguous and one downlink CC
inter-band and one uplink CC for carrier aggregation, or
- up to two downlink CCs and up to two uplink CCs for intra-band non-contiguous carrier aggregation, or
- up to two downlink CCs and up to two uplink CCs for inter-band carrier aggregation, or
- up to two downlink CCs intra-band contiguous and one downlink inter-band and one uplink CC for carrier
aggregation, or
- up to two downlink CCs intra-band non-contiguous and one downlink inter-band and one uplink CC for
carrier aggregation, or
- up to two downlink CCs and one uplink CC for intra-band non-contiguous carrier aggregation.
- Requirements for E-UTRA carrier aggregation, where the PCell is FDD PCell or TDD PCell and the downlink
SCell(s) follow the frame structure type 3 [16], are applicable for the CA capable UE, which is supporting band
combinations according to 36.101 [5] and which has been configured with at least one downlink SCell but:
- up to five downlink CCs and one uplink CCs for inter-band carrier aggregation.
- The requirements for UE configured with eDRX_CONN cycle do not apply for CA requirements and dual
connectivity requirements.
- The requirements for a UE category 0 are derived assuming UE category 0 [31] and a single antenna receiver.
- The requirements for UE category M1 are derived assuming: DL Category M1 and Uplink Category M1,
operation in any LTE system bandwidth but with a channel bandwidth of 1.4 MHz and transmission bandwidth
of 6 PRBs in downlink and uplink, and a single antenna receiver. DL UE category M1 and UL UE category M1
are defined in [31].
- The requirements for UE category M2 are derived assuming Downlink category M2 and Uplink Category M2,
operation in any LTE system bandwidth but with a channel bandwidth of 1.4 MHz, 5 MHz or 20 MHz and
transmission bandwidth of 6 PRBs, 24 PRBs or 96 PRBs in downlink and uplink, and a single antenna receiver.
DL UE category M2 and UL UE category M2 are defined in [31].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 76 ETSI TS 136 133 V14.3.0 (2017-04)
- The requirements for normal coverage in idle mode shall apply provided the UE category M1 is with the radio
condition that SCH Ês/Iot≥-6 dB and CRS Ês/Iot ≥-6 dB.
- The requirements for enhanced coverage in idle mode shall apply provided the UE category M1 is with the radio
condition that SCH Ês/Iot ≥ -15 dB and CRS Ês/Iot ≥ -15 dB.
- The requirements for CEMode A shall apply provided the UE category M1 is configured with CEMode A, SCH
Ês/Iot ≥ -6 dB and CRS Ês/Iot ≥ -6 dB. The CEMode A and the number of repetition levels for different
physical channels are defined in [3].
- The requirements for CEMode B shall apply provided the UE category M1 is configured with CEMode B, SCH
Ês/Iot ≥ -15 dB and CRS Ês/Iot ≥ -15 dB. The CEMode B and the number of repetition levels for different
physical channels are defined in [3].
- Requirements for E-UTRA ProSe Direct Discovery and E-UTRA ProSe Direct Communication are applicable
for ProSe operation on either the uplink frequency of PCC, or SCC, or a non-serving carrier, but:
- with ProSe operation limited to one carrier on a given subframe.
- Requirements for interruptions due to ProSe Direct Discovery and/or ProSe Direct Communications specified in
clause 7.16.3 apply, but:
- with configured serving carriers of up to two downlink CCs, unless the UE is configured with reception gap
for ProSe operation, and
- with configured serving carriers of up to two uplink CCs, unless the UE is configured with transmission gap
for ProSe operation.
- The requirements for UE category NB1 are derived assuming UE category NB1and a single antenna receiver.
UE category NB1 is defined in [31].
- The requirements for normal coverage in idle mode shall apply provided the UE category NB1 is with the radio
condition that NSCH Ês/Iot ≥ -6 dB and NRS Ês/Iot ≥ -6 dB.
- The requirements for enhanced coverage in idle mode shall apply provided the UE category NB1 is with the
radio condition that NSCH Ês/Iot ≥ -15 dB and NRS Ês/Iot ≥ -15 dB.
- The measurement accuracy requirements in section 9.22 for intra-frequency and inter-frequency absolute
NRSRQ accuracy for UE Category NB1 apply only in idle mode.
- The measurement accuracy requirements in section 9.22 for intra-frequency and inter-frequency absolute
NRSRP accuracy for UE Category NB1 apply also in idle mode.
- The requirements for SRS carrier based switching shall apply when the UE capable of SRS carrier based
switching is configured to perform SRS carrier based switching for transmitting SRS and/or RACH in one or
more CCs in the same or different time resources.
- The requirements for a UE category 1bis are derived assuming UE category 1bis [31] and a single antenna
receiver. Following requirements are applicable to UE category 1bis.
- Cell re-selection requirements in section 4.2.2.1 to 4.2.2.10
- Handover requirements in section 5.1, 5.2, 5.3 and 5.4
- RRC re-establishment requirements in section 6.1
- Random access requirements in section 6.2
- RRC connection release with redirection requirements in section 6.3
- UE transmit timing requirements in section 7.1
- UE timer accuracy requirements in section 7.2
- Timing advance requirements in section 7.3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 77 ETSI TS 136 133 V14.3.0 (2017-04)
- Radio link monitoring requirements in section 7.11
- UE measurement capability in section 8.1.2 (support of 8.1.2.1.1.1a and 8.1.2.1.1a is TBD)
- E-UTRAN intra frequency measurement requirements in section 8.1.2.2.1 and 8.1.2.2.2
- E-UTRAN inter frequency measurement requirements in section 8.1.2.3.1, 8.1.2.3.2, 8.1.2.3.3 and 8.1.2.3.4
- Inter RAT measurement requirements in section 8.1.2.4
- E-UTRAN E-CID measurement requirements in section 8.1.2.7
- CGI reading requirements for UE category 0 in section 8.5.2.1.4 and 8.5.2.1.6
- UE Rx – Tx time difference measurement accuracy requirements in section 9.1.9.1 and 9.1.9.2
4 E-UTRAN RRC_IDLE state mobility
4.1 Cell Selection
After a UE has switched on and a PLMN has been selected, the Cell selection process takes place, as described in
TS36.304. This process allows the UE to select a suitable cell where to camp on in order to access available services. In
this process the UE can use stored information (Stored information cell selection) or not (Initial cell selection).
4.2 Cell Re-selection
4.2.1 Introduction
The cell reselection procedure allows the UE to select a more suitable cell and camp on it.
When the UE is in either Camped Normally state or Camped on Any Cell state on a cell, the UE shall attempt to detect,
synchronise, and monitor intra-frequency, inter-frequency and inter-RAT cells indicated by the serving cell. For intra-
frequency and inter-frequency cells the serving cell may not provide explicit neighbour list but carrier frequency
information and bandwidth information only. UE measurement activity is also controlled by measurement rules defined
in TS36.304, allowing the UE to limit its measurement activity.
If the UE is of category M1 and in normal coverage, it shall attempt to detect, synchronise, and monitor intra-frequency
cells indicated by the serving cell according to the requirements in section 4.2.2, except that UE is not required to
perform RSRQ measurement. The UE category M1 and normal coverage applicability of the requirements is defined in
Section 3.6.
If the UE is in enhanced coverage as defined in section 3.6, the requirements in section 4.2.2.11 apply.
4.2.2 Requirements
The UE shall search every layer of higher priority at least every Thigher_priority_search = (60 * Nlayers) seconds when the UE is
not configured with eDRX_IDLE cycle, and at least every Thigher_priority_search = MAX(60 * Nlayers, one eDRX_IDLE
cycle) when UE is configured with eDRX_IDLE cycle, where Nlayers is the total number of configured higher priority E-
UTRA, UTRA FDD, UTRA TDD, CDMA2000 1x and HRPD carrier frequencies and is additionally increased by one
if one or more groups of GSM frequencies is configured as a higher priority.
In the requirements of Section 4.2.2 for the UE capable of CA, the applicable exceptions for side conditions are
specified in Annex B, Section B.4.2.
For a UE which supports increased carrier monitoring E-UTRA or increased carrier monitoring UTRA, the reselection
performance for different carriers may be configured by higher layers to be either normal or reduced. The following
definitions are used in the requirements:
Kcarrier : Total number of interfrequency carriers in the neighbour cell list
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 78 ETSI TS 136 133 V14.3.0 (2017-04)
Kcarrier,normal =Kcarrier- Kcarrier,reduced: Number of interfrequency carriers to be monitored in the normal performance
group
Kcarrier,normal,FDD : Number of interfrequency FDD carriers to be monitored in the normal performance group
Kcarrier,normal,TDD : Number of interfrequency TDD carriers to be monitored in the normal performance group
Kcarrier,reduced : Number of interfrequency carriers to be monitored in the reduced performance group
NUTRA_carrier: Total number of configured UTRA FDD carriers in the neighbour cell list
NUTRA_carrier,normal= NUTRA_carrier - NUTRA_carrier,reduced: Number of UTRA FDD carriers to be monitored in the normal
performance group
NUTRA_carrier,reduced: Number of UTRA FDD carriers to be monitored in the reduced performance group
NUTRA_carrier_TDD : Total number of configured UTRA TDD carriers in the neighbour cell list
NUTRA_carrier_TDD,normal= NUTRA_carrier_TDD - NUTRA_carrier_TDD,reduced: Number of UTRA TDD carriers to be monitored in
the normal performance grop
NUTRA_carrier_TDD,reduced: Number of UTRA TDD carriers to be monitored in the reduced performance group
The minimum performance requirements for a UE which supports Increased UE carrier monitoring E-UTRA [2, 31] are
calculated as defined in section 4.2.2.4 provided that Kcarrier,normal ≤3 for a UE capable of either FDD E-UTRA carrier
monitoring or TDD E-UTRA carrier monitoring or Kcarrier,normal ≤6 for a UE capable of both FDD and TDD E-UTRA
carrier monitoring provided Kcarrier,normal,FDD ≤3 and Kcarrier,normal,TDD ≤3 and the minimum performance requirements for a
UE which supports Increased UE carrier monitoring UTRA [2, 31] are calculated as defined in section 4.2.2.5 provided
that NUTRA_carrier_normal≤3 and NUTRA_carrier_TDD,normal≤3. In case the limits for the number of normal performance carriers is
exceeded considering the broadcast neighbour cell list and the bands supported by the UE, the UE which supports
Increased UE carrier monitoring E-UTRA shall measure at least 3 interfrequency carriers with normal performance and
the UE which supports Increased UE carrier monitoring UTRA shall measure at least 3 UTRA carriers with normal
performance. For a UE capable of monitoring E-UTRAN FDD and TDD carriers, in case the limits for the number of
normal performance carriers is exceeded considering the broadcast neighbour cell list and the bands supported by the
UE, the UE shall measure at least 3 FDD and 3 TDD E-UTRAN interfrequency carriers with normal performance.
Additionally, reduced performance requirements shall be met for carriers for which the Reduced measurement
performance IE is indicated, up to the UE measurement capability in section 4.2.2.9a.The minimum performance
requirements for a UE which does not support Increased UE carrier monitoring E-UTRA [2,31] are calculated assuming
all E-UTRA carriers required to be monitored for such UE, are having normal performance and are in normal
performance group, i.e. Kcarrier,normal =Kcarrier and Kcarrier,reduced=0. The minimum performance requirements for a UE which
does not support Increased UE carrier monitoring UTRA [2,31] are calculated assuming all UTRA carriers required to
be monitored for such UE, are having normal performance and are in normal performance group, i.e. NUTRA_carrier,normal=
NUTRA_carrier, NUTRA_carrier_TDD,normal= NUTRA_carrier_TDD and NUTRA_carrier,reduced =0 and NUTRA_carrier_TDD,reduced =0. No reduced
performance carrier requirement applies to a UE not supporting Increased UE carrier monitoring E-UTRA or UTRA [2,
31]. Capabilities for number of carriers to monitor for a UE which does not support Increased carrier monitoring E-
UTRA or Increased carrier monitoring UTRA are specified in section 4.2.2.9
4.2.2.1 Measurement and evaluation of serving cell
The UE shall measure the RSRP and RSRQ level of the serving cell and evaluate the cell selection criterion S defined in
[1] for the serving cell at least every DRX cycle.
The UE shall filter the RSRP and RSRQ measurements of the serving 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 DRX cycle/2.
If the UE is not configured with eDRX_IDLE cycle and has evaluated according to Table 4.2.2.1-1 in Nserv consecutive
DRX cycles that the serving cell does not fulfil the cell selection criterion S, the UE shall initiate the measurements of
all neighbour cells indicated by the serving cell, regardless of the measurement rules currently limiting UE
measurement activities. If the UE is configured with eDRX_IDLE cycle and has evaluated according to Table 4.2.2.1-2
in Nserv consecutive DRX cycles within a single PTW that the serving cell does not fulfil the cell selection criterion S,
the UE shall initiate the measurements of all neighbour cells indicated by the serving cell, regardless of the
measurement rules currently limiting UE measurement activities.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 79 ETSI TS 136 133 V14.3.0 (2017-04)
If the UE in RRC_IDLE has not found any new suitable cell based on searches and measurements using the intra-
frequency, inter-frequency and inter-RAT information indicated in the system information during the time T, the UE
shall initiate cell selection procedures for the selected PLMN as defined in [1], where T=10 s if the UE is not configured
with eDRX_IDLE cycle, and T=MAX(10 s, one eDRX_IDLE cycle) if the UE is configured with eDRX_IDLE cycle.
Table 4.2.2.1-1: Nserv
DRX cycle Nserv
length [s] [number of
DRX cycles]
0.32 4
0.64 4
1.28 2
2.56 2
Table 4.2.2.1-2: Nserv for UE configured with eDRX_IDLE cycle
eDRX_IDLE cycle length DRX cycle PTW Nserv
[s] length [s]
length [s] [number of
(number DRX cycles]
of 1.28s
periods)
0.32 ≥1.28 (1) 2
5.12 ≤ eDRX_IDLE cycle 0.64 ≥1.28 (1) 2
length ≤ 2621.44 1.28 ≥2.56 (2) 2
2.56 ≥5.12 (4) 2
NOTE 1: The number of DRX cycles in this table is given for the DRX
cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section
10.5.5.32 of TS 24.008 [34].
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.2.2.2 Void
4.2.2.3 Measurements of intra-frequency E-UTRAN cells
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.3 for Cat-M1 UE
- Annex B.1.1, otherwise
for a corresponding Band.
The UE shall measure RSRP and RSRQ at least every Tmeasure,EUTRAN_Intra 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
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 80 ETSI TS 136 133 V14.3.0 (2017-04)
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, provided that the cell is
- at least 4dB better ranked for Cat-M1 UE
- at least 3 dB better ranked, otherwise
When evaluating cells for reselection, the side conditions for RSRP and SCH apply to both serving and non-serving
intra-frequency cells.
For UE category 1bis, 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, provided that the cell is at least [TBD]dB 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.
For UE neither configured with eDRX_IDLE cycle nor configured with [highSpeedEnhancedMeasFlag],
Tdetect,EUTRAN_Intra, Tmeasure,EUTRAN_Intra and Tevaluate, E-UTRAN_intra are specified in Table 4.2.2.3-1. For UE configured with
eDRX_IDLE cycle, Tdetect,EUTRAN_Intra, Tmeasure,EUTRAN_Intra and Tevaluate, E-UTRAN_intra are specified in Table 4.2.2.3-2, where
the requirements apply provided that the serving cell is configured with eDRX_IDLE and is the same in all PTWs
during any of Tdetect,EUTRAN_Intra, Tmeasure,EUTRAN_Intra and Tevaluate, E-UTRAN_intra when multiple PTWs are used. For UE
configured with [highSpeedEnhancedMeasFlag], Tdetect,EUTRAN_Intra, Tmeasure,EUTRAN_Intra and Tevaluate, E-UTRAN_intra are
specified in Table 4.2.2.3-3.
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)
Table 4.2.2.3-2: Tdetect,EUTRAN_Intra, Tmeasure,EUTRAN_Intra and Tevaluate,E-UTRAN_intra for UE configured with
eDRX_IDLE cycle
eDRX_IDLE DRX PTW Tdetect,EUTRAN_Intra [s] (number of DRX cycles) Tmeasure,EUTRAN_Intra Tevaluate,E-UTRAN_intra
cycle length cycle length [s] (number of [s] (number of
[s] length [s] DRX cycles) DRX cycles)
[s] (number
of 1.28s
periods)
0.32 ≥1.28 ⎡ 23 ⎤ 0.32 (1) 0.64 (2)
(1) eDRX _ cycle _ length × ⎢ ⎥
5.12 ≤ 0.64 ≥1.28 ⎢ ⎡PTW / DRX _ cycle _ length ⎤ ⎥ 0.64 (1) 1.28 (2)
eDRX_IDLE (1) (23)
cycle length 1.28 ≥2.56 1.28 (1) 2.56 (2)
≤ 2621.44 (2)
2.56 ≥5.12 2.56 (1) 5.12 (2)
(4)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section 10.5.5.32 of TS 24.008 [34].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 81 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.2.2.3-3 : Tdetect,EUTRAN_Intra, Tmeasure,EUTRAN_Intra and Tevaluate, E-UTRAN_intra for UE configured with
[highSpeedEnhancedMeasFlag]
DRX cycle Tdetect,EUTRAN_Intra Tmeasure,EUTRAN_Intra Tevaluate,E-UTRAN_intra
length [s] [s] (number of [s] (number of [s] (number of DRX
DRX cycles) DRX cycles) cycles)
0.32 3.2 (10) 0.32(1) 0.96(3)
0.64 6.4 (10) 0.64 (1) 1.92 (3)
1.28 12.8(10) 1.28 (1) 3.84 (3)
2.56 58.88 (23) 2.56 (1) 7.68 (3)
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.2.2.4 Measurements of inter-frequency E-UTRAN cells
The UE shall be able to identify new inter-frequency cells and perform RSRP or RSRQ measurements of identified
inter-frequency cells if carrier frequency information is provided by the serving cell, even if no explicit neighbour list
with physical layer cell identities is provided.
If Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ then the UE shall search for inter-frequency layers of higher priority
at least every Thigher_priority_search where Thigher_priority_search is described in clause 4.2.2.
If Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ then the UE shall search for and measure inter-frequency 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 higher priority layers shall be the same as that defined below.
If the UE is not configured with eDRX_IDLE cycle or configured with an eDRX_IDLE cycle not longer than 20.48 s,
the UE shall be able to evaluate whether a newly detectable inter-frequency cell in normal performance group meets the
reselection criteria defined in TS36.304 within Kcarrier,normal * Tdetect,EUTRAN_Inter, and able to evaluate whether a newly
detectable inter-frequency cell in reduced performance group meets the reselection criteria defined in TS36.304 within 6
* Kcarrier,reduced * 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. If the UE is configured with eDRX_IDLE cycle longer than 20.48 s, the UE shall be able to
evaluate whether a newly detectable inter-frequency cell in normal performance group meets the reselection criteria
defined in TS36.304 within Kcarrier,normal * Tdetect,EUTRAN_Inter, and when Srxlev < 3 dB or Squal < 3 dB and able to evaluate
whether a newly detectable inter-frequency cell in reduced performance group meets the reselection criteria defined in
TS36.304 within 6 * Kcarrier,reduced * 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. An inter-frequency cell is considered to be detectable according
to RSRP, RSRP Ês/Iot, SCH_RP and SCH Ês/Iot defined in Annex B.1.2 for a corresponding Band.
For UE category 1bis, if the UE is not configured with eDRX_IDLE cycle or configured with an eDRX_IDLE cycle not
longer than 20.48 s, the UE shall be able to evaluate whether a newly detectable inter-frequency cell in normal
performance group meets the reselection criteria defined in TS36.304 within Kcarrier,normal * Tdetect,EUTRAN_Inter, and able to
evaluate whether a newly detectable inter-frequency cell in reduced performance group meets the reselection criteria
defined in TS36.304 within 6 * Kcarrier,reduced * 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 [TBD]dB for reselections based on ranking or [TBD]dB for RSRP reselections based on absolute
priorities or [TBD]dB for RSRQ reselections based on absolute priorities. If the UE is configured with eDRX_IDLE
cycle longer than 20.48 s, the UE shall be able to evaluate whether a newly detectable inter-frequency cell in normal
performance group meets the reselection criteria defined in TS36.304 within Kcarrier,normal * Tdetect,EUTRAN_Inter, and when
Srxlev < 3 dB or Squal < 3 dB and able to evaluate whether a newly detectable inter-frequency cell in reduced
performance group meets the reselection criteria defined in TS36.304 within 6 * Kcarrier,reduced * 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 [TBD]dB for reselections based on ranking or
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 82 ETSI TS 136 133 V14.3.0 (2017-04)
[TBD]dB for RSRP reselections based on absolute priorities or [TBD]dB for RSRQ reselections based on absolute
priorities. An inter-frequency cell is considered to be detectable according to RSRP, RSRP Ês/Iot, SCH_RP and SCH
Ês/Iot defined in Annex B.1.2 for a corresponding Band.
When higher priority cells are found by the higher priority search, they shall be measured at least every Tmeasure,E-
UTRAN_Inter . If, after detecting a cell in a higher priority search, it is determined that reselection has not occurred then the
UE is not required to continuously measure the detected cell to evaluate the ongoing possibility of reselection.
However, the minimum measurement filtering requirements specified later in this clause shall still be met by the UE
before it makes any determination that it may stop measuring the cell. If the UE detects on a E-UTRA carrier a cell
whose physical identity is indicated as not allowed for that carrier in the measurement control system information of the
serving cell, the UE is not required to perform measurements on that cell.
If the UE is configured with eDRX_IDLE cycle not longer than 20.48 s, the UE shall measure RSRP or RSRQ at least
every Kcarrier,normal * Tmeasure,EUTRAN_Inter for identified lower or equal priority inter-frequency cells in normal performance
group, and at least every 6 * Kcarrier,reduced * Tmeasure,EUTRAN_Inter for identified lower or equal priority inter-frequency cells
in reduced performance group. If the UE is configured with eDRX_IDLE cycle longer than 20.48 s, the UE shall
measure RSRP or RSRQ at least every Kcarrier,normal * Tmeasure,EUTRAN_Inter for identified lower or equal priority inter-
frequency cells in normal performance group, and when Srxlev < 3 dB or Squal < 3 dB at least every 6 * Kcarrier,reduced *
Tmeasure,EUTRAN_Inter for identified lower or equal priority inter-frequency cells in reduced performance group. If the UE
detects on a E-UTRA carrier a cell whose physical identity is indicated as not allowed for that carrier in the
measurement control system information of the serving cell, the UE is not required to perform measurements on that
cell.
The UE shall filter RSRP or RSRQ measurements of each measured higher, lower and equal priority inter-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_Inter/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.
If the UE is configured with eDRX_IDLE cycle not longer than 20.48 s, for an inter-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 inter-frequency cell in normal performance group has met reselection criterion defined TS 36.304 within
Kcarrier,normal * Tevaluate,E-UTRAN_Inter, and capable of evaluating that the inter-frequency cell in reduced performance group
has met reselection criterion defined TS 36.304 within 6 * Kcarrier,reduced * Tevaluate,E-UTRAN_Inter, 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. If the UE is
configured with eDRX_IDLE cycle longer than 20.48 s, for an inter-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 inter-
frequency cell in normal performance group has met reselection criterion defined TS 36.304 within Kcarrier,normal *
Tevaluate,E-UTRAN_Inter, and when Srxlev < 3 dB or Squal < 3 dB capable of evaluating that the inter-frequency cell in
reduced performance group has met reselection criterion defined TS 36.304 within 6 * Kcarrier,reduced * Tevaluate,E-UTRAN_Inter,
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. When evaluating cells for reselection, the side conditions for RSRP and SCH apply to both serving and inter-
frequency cells.
If Treselection timer has a non zero value and the inter-frequency cell is better ranked than the serving cell, the UE shall
evaluate this inter-frequency cell for the Treselection time. If this cell remains better ranked within this duration, then the
UE shall reselect that cell.
For UE not configured with eDRX_IDLE cycle, Tdetect,EUTRAN_Inter, Tmeasure,EUTRAN_Inter and Tevaluate, E-UTRAN_inter are
specified in Table 4.2.2.4-1. For UE configured with eDRX_IDLE cycle, Tdetect,EUTRAN_Inter, Tmeasure,EUTRAN_Inter and
Tevaluate, E-UTRAN_inter are specified in Table 4.2.2.4-2, where the requirements apply provided that the serving cell is
configured with eDRX_IDLE and is the same in all PTWs during any of Tdetect,EUTRAN_Inter, Tmeasure,EUTRAN_Inter and Tevaluate,
E-UTRAN_inter when multiple PTWs are used.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 83 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.2.2.4-1 : Tdetect,EUTRAN_Inter, Tmeasure,EUTRAN_Inter and Tevaluate,E-UTRAN_Inter
DRX Tdetect,EUTRAN_Inter Tmeasure,EUTRAN_Inter Tevaluate,E-
cycle [s] (number of [s] (number of UTRAN_Inter
length DRX cycles) DRX cycles) [s] (number
[s] of DRX
cycles)
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)
Table 4.2.2.4-2: Tdetect,EUTRAN_Inter, Tmeasure,EUTRAN_Inter and Tevaluate, E-UTRAN_inter for UE configured with
eDRX_IDLE cycle
eDRX_IDLE DRX PTW Tdetect,EUTRAN_Inter [s] (number of DRX cycles) Tmeasure,EUTRAN_Inter Tevaluate,E-
cycle length cycle length [s] (number of UTRAN_inter
[s] length [s] DRX cycles) [s] (number of
[s] (number DRX cycles)
of 1.28s
periods)
5.12 ≤ 0.32 ≥1.28 ⎡ 23 ⎤ 0.32 (1) 0.64 (2)
eDRX_IDLE (1) eDRX _ cycle _ length × ⎢ ⎥
cycle length 0.64 ≥1.28 ⎢ ⎡PTW / DRX _ cycle _ length⎤ ⎥ 0.64 (1) 1.28 (2)
≤ 2621.44 (1) (23)
1.28 ≥2.56 1.28 (1) 2.56 (2)
(2)
2.56 ≥5.12 2.56 (1) 5.12 (2)
(4)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section 10.5.5.32 of TS 24.008 [34].
For higher priority cells, a UE may optionally use a shorter value for TmeasureE-UTRA_Inter ,which shall not be less than
Max(0.64 s, one DRX cycle).
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.2.2.5 Measurements of inter-RAT cells
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 clause 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
search for and measure higher priority inter-RAT layers shall be the same as that defined below for lower priority
RATs.
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 84 ETSI TS 136 133 V14.3.0 (2017-04)
4.2.2.5.1 Measurements of UTRAN FDD cells
When the measurement rules indicate that UTRA FDD cells are to be measured, the UE shall measure CPICH Ec/Io
and CPICH RSCP of detected UTRA FDD cells in the neighbour frequency list at the minimum measurement rate
specified in this section. The UE shall filter CPICH Ec/Io and CPICH RSCP measurements of each measured UTRA
FDD 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 half the minimum specified measurement period.
If the UE is not configured with eDRX_IDLE cycle or configured with eDRX_IDLE cycle not longer than 20.48 s, the
UE shall evaluate whether newly detectable UTRA FDD cells in normal performance group have met the reselection
criteria in TS 36.304 within time NUTRA_carrier,normal * TdetectUTRA_FDD , and evaluate whether newly detectable UTRA FDD
cells in reduced performance group have met the reselection criteria in TS 36.304 within time 6 * NUTRA_carrier,reduced *
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. If the UE is configured with eDRX_IDLE cycle longer than 20.48 s, the UE shall evaluate
whether newly detectable UTRA FDD cells in normal performance group have met the reselection criteria in TS 36.304
within time (NUTRA_carrier,normal) * TdetectUTRA_FDD , and when Srxlev < 3 dB or Squal < 3 dB evaluate whether newly
detectable UTRA FDD cells in reduced performance group have met the reselection criteria in TS 36.304 within time 6
* NUTRA_carrier,reduced * 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.
If the UE is not configured with eDRX_IDLE cycle or configured with eDRX_IDLE cycle not longer than 20.48 s, cells
which have been detected shall be measured at least every NUTRA_carrier,normal * TmeasureUTRA_FDD for the cells in normal
performance group, and at least every 6 * NUTRA_carrier,reduced * TmeasureUTRA_FDD for the cells in reduced performance group
when Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ. If the UE is configured with eDRX_IDLE cycle longer than 20.48
s, cells which have been detected shall be measured at least every (NUTRA_carrier,normal) * TmeasureUTRA_FDD for the cells in
normal performance group, and when Srxlev < 3 dB or Squal < 3 dB at least every 6 * NUTRA_carrier,reduced *
TmeasureUTRA_FDD for the cells in reduced performance group when Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ.
When higher priority UTRA FDD cells are found by the higher priority search, they shall be measured at least every
Tmeasure,UTRA_FDD. If, after detecting a cell in a higher priority search, it is determined that reselection has not occurred
then the UE is not required to continuously measure the detected cell to evaluate the ongoing possibility of reselection.
However, the minimum measurement filtering requirements specified later in this clause shall still be met by the UE
before it makes any determination that it may stop measuring the cell.
If the UE is not configured with eDRX_IDLE cycle or configured with eDRX_IDLE cycle not longer than 20.48 s, 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 TS 36.304 [1]
within NUTRA_carrier,normal * TevaluateUTRA_FDD if the cell is in normal performance group and within 6 * NUTRA_carrier,reduced *
TevaluateUTRA_FDD if the cell is in reduced performance group when Treselection = 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. If the UE is configured with eDRX_IDLE cycle longer than 20.48 s, 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 TS 36.304 [1] within (NUTRA_carrier,normal) *
TevaluateUTRA_FDD if the cell is in normal performance group and when Srxlev < 3 dB or Squal < 3 dB within 6 *
NUTRA_carrier,reduced * TevaluateUTRA_FDD if the cell is in reduced performance group when Treselection = 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.
If Treselection timer has a non zero value and the UTRA FDD cell is satisfied with the reselection criteria which are
defined in [1], the UE shall evaluate this UTRA FDD cell for the Treselection time. If this cell remains satisfied with the
reselection criteria within this duration, then the UE shall reselect that cell.
For UE not configured with eDRX_IDLE cycle, TdetectUTRA_FDD, TmeasureUTRA_FDD and TevaluateUTRA_FDD are specified in
Table 4.2.2.5.1-1. For UE configured with eDRX_IDLE cycle, TdetectUTRA_FDD, TmeasureUTRA_FDD and TevaluateUTRA_FDD are
specified in Table 4.2.2.5.1-2, where the requirements apply provided that the serving cell is configured with
eDRX_IDLE and is the same in all PTWs during any of TdetectUTRA_FDD, TmeasureUTRA_FDD and TevaluateUTRA_FDD when
multiple PTWs are used.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 85 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.2.2.5.1-1: TdetectUTRA_FDD, TmeasureUTRA_FDD, and TevaluateUTRA_FDD
DRX TdetectUTRA_FDD TmeasureUTRA_FDD TevaluateUTRA_FDD
cycle [s] [s] (number of [s] (number of
length DRX cycles) DRX cycles)
[s]
0.32 5.12 (16) 15.36 (48)
0.64 30 5.12 (8) 15.36 (24)
1.28 6.4(5) 19.2 (15)
2.56 60 7.68 (3) 23.04 (9)
Table 4.2.2.5.1-2: TdetectUTRA_FDD, TmeasureUTRA_FDD and TevaluateUTRA_FDD for UE configured with eDRX_IDLE
cycle
eDRX_IDLE DRX cycle PTW length [s] TdetectUTRA_FDD [s] TmeasureUTRA_FDD TevaluateUTRA_FDD
cycle length [s] length [s] (number of (number of DRX [s] (number of [s] (number of
1.28s periods) cycles) DRX cycles) DRX cycles)
5.12 ≤ 0.32 ≥1.28 (1) Note 3 (23) 0.96 (3) Note 3 (9)
eDRX_IDLE 0.64 ≥2.56 (2) 1.92 (3) Note 3 (9)
cycle length ≤ 1.28 ≥3.84 (3) 3.84 (3) Note 3 (9)
2621.44 2.56 ≥7.68 (6) 7.68 (3) Note 3 (9)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section 10.5.5.32 of TS 24.008 [34].
NOTE 3: The time is calculated depending on the number N of DRX cycles as follows:
⎡ N ⎤
eDRX _ cycle _ length × ⎢ ⎥
⎢⎡PTW / DRX _ cycle _ length⎤⎥
For higher priority cells, a UE may optionally use a shorter value for TmeasureUTRA_FDD, which shall not be less than
Max(0.64 s, one DRX cycle).
4.2.2.5.2 Measurements of UTRAN TDD cells
When the measurement rules indicate that UTRA TDD cells are to be measured, the UE shall measure P-CCPCH RSCP
of detected UTRA TDD cells in the neighbour frequency list at the minimum measurement rate specified in this section.
The UE shall filter P-CCPCH RSCP measurements of each measured UTRA TDD 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 half the
minimum specified measurement period. If the UE is not configured with eDRX_IDLE cycle, P-CCPCH RSCP of
UTRAN TDD cells shall not be filtered over a longer period than that specified in table 4.2.2.5.2-1. If the UE is
configured with eDRX_IDLE cycle, P-CCPCH RSCP of UTRAN TDD cells shall not be filtered over a longer period
than that specified in table 4.2.2.5.2-2.
If the UE is not configured with eDRX_IDLE cycle or configured with eDRX_IDLE cycle not longer than 20.48 s, the
UE shall evaluate whether newly detectable UTRA TDD cells in normal performance group have met the reselection
criteria in TS 36.304 within time NUTRA_carrier_TDD,normal * TdetectUTRA_TDD, and evaluate whether newly detectable UTRA
TDD cells in reduced performance group have met the reselection criteria in TS 36.304 within time 6 *
NUTRA_carrier_TDD,reduced * 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. If the UE is configured with eDRX_IDLE cycle longer
than 20.48 s, the UE shall evaluate whether newly detectable UTRA TDD cells in normal performance group have met
the reselection criteria in TS 36.304 within time (NUTRA_carrier_TDD,normal) * TdetectUTRA_TDD, and when Srxlev < 3 dB or
Squal < 3 dB evaluate whether newly detectable UTRA TDD cells in reduced performance group have met the
reselection criteria in TS 36.304 within time 6 * NUTRA_carrier_TDD,reduced * 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.
If the UE is not configured with eDRX_IDLE cycle or configured with eDRX_IDLE cycle not longer than 20.48 s, cells
which have been detected shall be measured at least every NUTRA_carrier_TDD,normal * TmeasureUTRA_TDD for the cells in normal
performance group, and at least every 6 * NUTRA_carrier_TDD,reduced * TmeasureUTRA_TDD for the cells in reduced performance
group, when Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ. If the UE is configured with eDRX_IDLE cycle longer than
20.48 s, cells which have been detected shall be measured at least every (NUTRA_carrier_TDD,normal) * TmeasureUTRA_TDD for the
cells in normal performance group, and when Srxlev < 3 dB or Squal < 3 dB at least every 6 * NUTRA_carrier_TDD,reduced *
TmeasureUTRA_TDD for the cells in reduced performance group, when Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 86 ETSI TS 136 133 V14.3.0 (2017-04)
When higher priority UTRA TDD cells are found by the higher priority search, they shall be measured at least every
Tmeasure,UTRA_TDD. If, after detecting a cell in a higher priority search, it is determined that reselection has not occurred
then the UE is not required to continuously measure the detected cell to evaluate the ongoing possibility of reselection.
However, the minimum measurement filtering requirements specified later in this clause shall still be met by the UE
before it makes any determination that it may stop measuring the cell.
If the UE is not configured with eDRX_IDLE cycle or configured with eDRX_IDLE cycle not longer than 20.48 s, 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,normal *TevaluateUTRA_TDD if the cell is in normal performance group and within 6 * NUTRA_carrier_TDD,reduced *
TevaluateUTRA_TDD if the cell is in reduced performance group when Treselection = 0 provided that the reselection criteria is
met by a margin of at least 6dB. If the UE is configured with eDRX_IDLE cycle longer than 20.48 s, 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,normal *TevaluateUTRA_TDD if the cell is in normal performance group and when Srxlev < 3 dB or Squal < 3
dB within 6 * NUTRA_carrier_TDD,reduced * TevaluateUTRA_TDD if the cell is in reduced performance group when Treselection = 0
provided that the reselection criteria is met by a margin of at least 6dB.
If Treselection timer has a non zero value and the UTRA TDD cell is satisfied with the reselection criteria which are
defined in [1], the UE shall evaluate this UTRA TDD cell for the Treselection time. If this cell remains satisfied with the
reselection criteria within this duration, then the UE shall reselect that cell.
For UE not configured with eDRX_IDLE cycle, TdetectUTRA_TDD, TmeasureUTRA_TDD and TevaluateUTRA_TDD are specified in
Table 4.2.2.5.2-1. For UE configured with eDRX_IDLE cycle, TdetectUTRA_TDD, TmeasureUTRA_TDD and TevaluateUTRA_TDD are
specified in Table 4.2.2.5.2-2, where the requirements apply provided that the serving cell is configured with
eDRX_IDLE and is the same in all PTWs during any of TdetectUTRA_TDD, TmeasureUTRA_TDD and TevaluateUTRA_TDD when
multiple PTWs are used.
Table 4.2.2.5.2-1: TdetectUTRA_TDD, TmeasureUTRA_TDD and TevaluateUTRA_TDD
DRX TdetectUTRA_TDD TmeasureUTRA_TDD TevaluateUTRA_TDD
cycle [s] [s] (number of [s] (number of
length DRX cycles) DRX cycles)
[s]
0.32 5.12 (16) 15.36 (48)
0.64 30 5.12 (8) 15.36 (24)
1.28 6.4(5) 19.2 (15)
2.56 60 7.68 (3) 23.04 (9)
Table 4.2.2.5.2-2: TdetectUTRA_TDD, TmeasureUTRA_TDD and TevaluateUTRA_TDD for UE configured with eDRX_IDLE
cycle
eDRX_IDLE DRX cycle PTW length TdetectUTRA_TDD [s] TmeasureUTRA_TDD TevaluateUTRA_TDD
cycle length [s] length [s] [s] (number of (number of DRX [s] (number of [s] (number of
1.28s periods) cycles) DRX cycles) DRX cycles)
5.12 ≤ 0.32 ≥1.28 (1) Note 3 (23) 0.96 (3) Note 3 (9)
eDRX_IDLE 0.64 ≥2.56 (2) 1.92 (3) Note 3 (9)
cycle length ≤ 1.28 ≥3.84 (3) 3.84 (3) Note 3 (9)
2621.44 2.56 ≥7.68 (6) 7.68 (3) Note 3 (9)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section 10.5.5.32 of TS 24.008 [34].
NOTE 3: The time is calculated depending on the number N of DRX cycles as follows:
⎡ N ⎤
eDRX _ cycle _ length × ⎢ ⎥
⎢ ⎡PTW / DRX _ cycle _ length⎤ ⎥
For higher priority cells, a UE may optionally use a shorter value for TmeasureUTRA_TDD, which shall not be less than
Max(0.64 s, one DRX cycle).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 87 ETSI TS 136 133 V14.3.0 (2017-04)
4.2.2.5.3 Measurements of GSM cells
When the measurement rules defined in [1] indicate that E-UTRAN inter-frequencies or inter-RAT frequency cells are
to be measured, the UE shall measure the signal level of the GSM BCCH carriers if the GSM BCCH carriers are
indicated in the measurement control system information of the serving cell. GSM BCCH carriers of lower priority than
the serving cell shall be measured at least every Tmeasure,GSM.
When higher priority GSM BCCH carriers are found by the higher priority search, they shall be measured at least every
Tmeasure,GSM, and the UE shall decode the BSIC of the GSM BCCH carrier. If, after detecting a cell in a higher priority
search, it is determined that reselection has not occurred then the UE is not required to continuously measure the
detected cell to evaluate the ongoing possibility of reselection, or to continuously verify the BSIC of the GSM BCCH
carrier every 30s. However, the minimum measurement filtering requirements specified later in this clause shall still be
met by the UE before it makes any determination that it may stop measuring the cell.
The UE shall maintain a running average of 4 measurements for each GSM BCCH carrier. The measurement samples
for each cell shall be as far as possible uniformly distributed over the averaging period.
If continuous GSM measurements are required by the measurement rules in [1], the UE shall attempt to verify the BSIC
at least every 30 seconds for each of the 4 strongest GSM BCCH carriers. If a change of BSIC is detected for one GSM
cell then that GSM BCCH carrier shall be treated as a new GSM neighbour cell. If the UE detects on a BCCH carrier a
BSIC which is indicated as not allowed for that carrier in the measurement control system information of the serving
cell, the UE is not required to perform BSIC re-confirmation for that cell.
The UE shall not consider the GSM BCCH carrier in cell reselection, if the UE cannot demodulate the BSIC of that
GSM BCCH carrier. Additionally, the UE shall not consider a GSM neighbour cell in cell reselection, if it is indicated
as not allowed in the measurement control system information of the serving cell.
If Treselection timer has a non zero value and the GSM cell is satisfied with the reselection criteria which are defined in [1],
the UE shall evaluate this GSM cell for the Treselection time. If this cell remains satisfied with the reselection criteria
within this duration, then the UE shall reselect that cell.
For UE not configured with eDRX_IDLE cycle, Tmeasure,GSM is specified in Table 4.2.2.5.3-1. For UE configured with
eDRX_IDLE cycle, Tmeasure,GSM is specified in Table 4.2.2.5.3-2, where the requirements apply provided that the serving
cell is configured with eDRX_IDLE and is the same in all PTWs during Tmeasure,GSM when multiple PTWs are used.
Table 4.2.2.5.3-1: Tmeasure,GSM,
DRX Tmeasure,GSM
cycle [s] (number
length of DRX
[s] cycles)
0.32 5.12 (16)
0.64 5.12 (8)
1.28 6.4(5)
2.56 7.68 (3)
Table 4.2.2.5.3-2: Tmeasure,GSM for UE configured with eDRX_IDLE cycle
eDRX_IDLE DRX PTW length Tmeasure,GSM [s]
cycle cycle [s] (number (number of DRX
length [s] length of 1.28s cycles)
[s] periods)
5.12 ≤ 0.32 ≥1.28 (1) 0.96 (3)
eDRX_IDLE 0.64 ≥2.56 (2) 1.92 (3)
cycle length 1.28 ≥3.84 (3) 3.84 (3)
≤ 2621.44 2.56 ≥7.68 (6) 7.68 (3)
NOTE 1: The number of DRX cycles in this table is given for
the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in
Section 10.5.5.32 of TS 24.008 [34].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 88 ETSI TS 136 133 V14.3.0 (2017-04)
4.2.2.5.4 Measurements of HRPD cells
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 Neighbor 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 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
clause 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 Neighbor 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.
For UE not configured with eDRX_IDLE cycle, Table 4.2.2.5.4-1 gives values of TmeasureHRPD and TevaluateHRPD. For UE
configured with eDRX_IDLE cycle, TmeasureHRPD and TevaluateHRPD are specified in Table 4.2.2.5.4-2, where the
requirements apply provided that the serving cell is configured with eDRX_IDLE and is the same in all PTWs during
any of TmeasureHRPD and TevaluateHRPD when multiple PTWs are used.
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)
Table 4.2.2.5.4-2: TmeasureHRPD and TevaluateHRPD for UE configured with eDRX_IDLE cycle
eDRX_IDLE DRX cycle PTW length TmeasureHRPD TevaluateHRPD
cycle length [s] [s] (number [s] (number [s] (number
length [s] of 1.28s of DRX of DRX
periods) cycles) cycles)
5.12 ≤ 0.32 ≥1.28 (1) 0.96 (3) Note 3 (9)
eDRX_IDLE 0.64 ≥2.56 (2) 1.92 (3) Note 3 (9)
cycle length 1.28 ≥3.84 (3) 3.84 (3) Note 3 (9)
≤ 2621.44 2.56 ≥7.68 (6) 7.68 (3) Note 3 (9)
NOTE 1: The number of DRX cycles in this table is given for the DRX
cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section
10.5.5.32 of TS 24.008 [34].
NOTE 3: The time is calculated depending on the number N of DRX
cycles as follows:
⎡ N ⎤
eDRX _ cycle _ length × ⎢ ⎥
⎢⎡PTW / DRX _ cycle _ length⎤⎥
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.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 89 ETSI TS 136 133 V14.3.0 (2017-04)
4.2.2.5.5 Measurements of cdma2000 1X
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 Neighbor Frequency’, which is transmitted on E-UTRAN BCCH, is the
number of carriers used for all cdma2000 1X cells in the neighbour cell list.
When the E-UTRA serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE shall search for
cdma2000 1X layers of higher priority at least every Thigher_priority_search where Thigher_priority_search is defined in clause 4.2.2.
For CDMA2000 1X cells which have been detected, the UE shall measure CDMA2000 1xRTT Pilot Strength at least
every (Number of CDMA2000 1X Neighbor Frequency)*T measureCDMA2000_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.
For UE not configured with eDRX_IDLE cycle, Table 4.2.2.5.5-1 gives values of TmeasureCDMA2000_1X and
TevaluateCDMA2000_1X. For UE configured with eDRX_IDLE cycle, TmeasureCDMA2000_1X and TevaluateCDMA2000_1X are specified in
Table 4.2.2.5.5-2 where the requirements apply provided that the serving cell is configured with eDRX_IDLE and is the
same in all PTWs during any of TmeasureCDMA2000_1X and TevaluateCDMA2000_1X when multiple PTWs are used.
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)
Table 4.2.2.5.5-2: TmeasureCDMA2000_1X and TevaluateCDMA2000_1X for UE configured with eDRX_IDLE cycle
eDRX_IDLE DRX PTW TmeasureCDMA2000_1X TevaluateCDMA2000_1X
cycle cycle length [s] (number of [s] (number of
length [s] length [s] DRX cycles) DRX cycles)
[s] (number
of 1.28s
periods)
5.12 ≤ 0.32 ≥1.28 (1) 0.96 (3) Note 3 (9)
eDRX_IDLE 0.64 ≥2.56 (2) 1.92 (3) Note 3 (9)
cycle length 1.28 ≥3.84 (3) 3.84 (3) Note 3 (9)
≤ 2621.44 2.56 ≥7.68 (6) 7.68 (3) Note 3 (9)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles
within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section 10.5.5.32
of TS 24.008 [34].
NOTE 3: The time is calculated depending on the number N of DRX cycles
⎡ N ⎤
as follows: eDRX _ cycle _ length ×
⎢ ⎥
⎢⎡PTW / DRX _ cycle _ length⎤⎥
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.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 90 ETSI TS 136 133 V14.3.0 (2017-04)
4.2.2.6 Evaluation of cell re-selection criteria
The UE shall evaluate the intra-frequency, inter-frequency and inter-RAT cell reselection criteria defined in [1] at least
every DRX cycle. When a non zero value of Treselection is used, the UE shall only perform reselection on an evaluation
which occurs simultaneously to, or later than the expiry of the Treselection timer.
For UE configured with eDRX_IDLE cycle, the cell reselection criteria shall be evaluated within at least every DRX
cycle within the PTW.
4.2.2.7 Maximum interruption in paging reception
UE shall perform the cell re-selection with minimum interruption in monitoring downlink channels for paging
reception. When the UE is configured with eDRX_IDLE cycle, the UE shall not miss any paging in a PTW provided
the paging is sent in at least [2] DRX cycles before the end of that PTW.
At intra-frequency and inter-frequency cell re-selection, the UE shall monitor the downlink of serving cell for paging
reception until the UE is capable to start monitoring downlink channels of the target intra-frequency and inter-frequency
cell for paging reception. The interruption time shall not exceed TSI-EUTRA + 50 ms.
At inter-RAT cell re-selection, the UE shall monitor the downlink of serving cell for paging reception until the UE is
capable to start monitoring downlink channels for paging reception of the target inter-RAT cell. For E-UTRAN to
UTRA cell re-selection the interruption time must not exceed TSI-UTRA + 50 ms. For E-UTRAN to GSM cell re-
selection the interruption time must not exceed TBCCH + 50 ms.
TSI-EUTRA is the time required for receiving all the relevant system information data according to the reception procedure
and the RRC procedure delay of system information blocks defined in TS 36.331 [2] for a E-UTRAN cell.
TSI-UTRA is the time required for receiving all the relevant system information data according to the reception procedure
and the RRC procedure delay of system information blocks defined in [7] for a UTRAN cell.
TBCCH is the maximum time allowed to read BCCH data from a GSM cell defined in [8].
These requirements assume sufficient radio conditions, so that decoding of system information can be made without
errors and does not take into account cell re-selection failure.
At cell re-selection to HRPD, the UE shall monitor the downlink of serving cell for paging reception until the UE is
capable of starting to monitor downlink channels for paging reception of the target HRPD cell. For HRPD cell re-
selection the interruption time must not exceed TSI-HRPD + 50 ms.
TSI-HRPD is the time required for receiving all the relevant system information data according to the reception procedure
and the upper layer (Layer 3) procedure delay of system information blocks defined in [11] in for HRPD cell.
At cell re-selection to cdma2000 1X, the UE shall monitor the downlink of serving cell for paging reception until the
UE is capable of starting to monitor downlink channels for paging reception of the target cdma2000 1X cell. For
cdma2000 1X cell re-selection the interruption time must not exceed TSI-cdma2000_1X + 50 ms.
TSI-cdma2000_1X is the time required for receiving all the relevant system information data according to the reception
procedure and the upper layer (Layer 3) procedure delay of system information blocks defined in [15] for cdma2000 1X
cell.
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.2.2.8 void
4.2.2.9 UE measurement capability
For idle mode cell re-selection purposes, the UE shall be capable of monitoring at least:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 91 ETSI TS 136 133 V14.3.0 (2017-04)
- Intra-frequency carrier, and
- Depending on UE capability, 3 FDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 3 TDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 3 FDD UTRA carriers, and
- Depending on UE capability, 3 TDD UTRA carriers, and
- Depending on UE capability, 32 GSM carriers, and
- Depending on UE capability, 3 cdma2000 1x carriers, and
- Depending on UE capability, 3 HRPD carriers.
In addition to the requirements defined above, a UE supporting E-UTRA measurements in RRC_IDLE state shall be
capable of monitoring a total of at least 8 carrier frequency layers, which includes serving layer, comprising of any
above defined combination of E-UTRA FDD, E-UTRA TDD, UTRA FDD, UTRA TDD, GSM (one GSM layer
corresponds to 32 cells), cdma2000 1x and HRPD layers.
4.2.2.9a UE measurement capability (Increased UE carrier monitoring)
UE which support Increased UE carrier monitoring E-UTRA according to the capabilities in [2,31] shall be capable of
monitoring at least
- Depending on UE capability, 8 FDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 8 TDD E-UTRA inter-frequency carriers
UE which support increased UE carrier monitoring UTRA according to the capabilities in [2,31] shall additionally be
capable of monitoring at least
- Depending on UE capability, 6 FDD UTRA carriers, and
- Depending on UE capability, 7 TDD UTRA carriers, and
In addition to the requirements defined above, a UE supporting E-UTRA measurements in RRC_IDLE state and
supporting Increased UE carrier monitoring E-UTRA or increased UE carrier monitoring UTRA according to the
capabilities in [2,31] shall be capable of monitoring a total of at least 13 carrier frequency layers, which includes
serving layer, comprising of any above defined combination of E-UTRA FDD, E-UTRA TDD, UTRA FDD, UTRA
TDD, GSM (one GSM layer corresponds to 32 cells), cdma2000 1x and HRPD layers.
The requirements in this section apply for UE regardless of their capability to support eDRX_IDLE.
4.2.2.10 Reselection to CSG cells
Note: Requirements in this clause are minimum requirements defined to ensure the testability of autonomous
CSG search. Further information on autonomous search times in practical deployments is available in
[25].
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 clause 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.
NOTE: According to [1], the UE autonomous search function, per UE implementation, determines when and/or
where to search for allowed CSG cells.
4.2.2.10.1 Reselection from a non CSG to an inter-frequency CSG cell
The UE shall perform search and reselection to an allowed inter-frequency 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.1-1. There
is no need for statistical testing of this requirement.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 92 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.2.2.10.1-1: Parameters for CSG inter-frequency reselection
Parameter Unit Cell 1 Cell 2
EARFCN Note1 Channel 1 Channel 2
CSG indicator False True
Physical cell identityNote1 1 2
CSG identity Not sent 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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140
N oc dBm/15 kHz Off
RSRP Note2 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
4.2.2.10.2 Reselection from a non CSG to an inter-RAT UTRAN FDD CSG cell
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
3GPP TS 36.133 version 14.3.0 Release 14 93 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.2.2.10.2-1: Parameters for CSG inter-RAT UTRAN FDD reselection
Parameter Unit Cell 1 Cell 2
EARFCN Note1 Channel 1 N/A
UARFCN Note1 N/A Channel 2
CSG indicator False True
Physical cell identityNote1 1 N/A
Primary scrambling code N/A Scrambling
Note1 code 2
CSG identity Not sent 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 N/A
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140
N oc dBm/15 kHz Off
RSRP Note2 dBm/15 KHz -110
CPICH_RSCP Note2 dBm -100
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCCPCH_Ec/Ior dB -12
AICH_Ec/Ior dB N/A -15
SCH_Ec/Ior dB -15
PICH_Ec/Ior dB -15
I oc dBm/3.84 MHz Off
Note 1: For this requirement to be applicable, the EARFCN and physical cell
identity for cell 1 and the UARFCN and scrambling code 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
4.2.2.11 Measurement and evaluation requirements for UE in enhanced
coverage
4.2.2.11.1 Measurement and evaluation of serving cell
The requirements in this subclause apply if UE is in the enhanced coverage area of the serving cell. The UE category
M1 and enhanced coverge applicability of the requirements is defined in section 3.6. The UE is considered to be in
enhanced coverage area of serving cell according to RSRP, RSRP Ês/Iot, SCH_RP and SCH Ês/Iot of the serving cell
defined in Annex B.1.3 for a corresponding Band.
The UE shall measure the RSRP level of the serving cell and evaluate the cell selection criterion S defined in [1] for the
serving cell at least every DRX cycle.
The UE shall filter the RSRP measurements of the serving cell using at least 4 measurements. Within the set of
measurements used for the filtering, at least two measurements shall be spaced by, at least DRX cycle/2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 94 ETSI TS 136 133 V14.3.0 (2017-04)
If the UE is not configured with eDRX_IDLE cycle and has evaluated according to Table 4.2.2.11.1-1 in Nserv_EC
consecutive DRX cycles that the serving cell does not fulfil the cell selection criterion S, the UE shall initiate the
measurements of all neighbour cells indicated by the serving cell, regardless of the measurement rules currently limiting
UE measurement activities.
If the UE is configured with eDRX_IDLE cycle and has evaluated according to Table 4.2.2.11.1-2 in Nserv_EC
consecutive DRX cycles within a single PTW that the serving cell does not fulfil the cell selection criterion S, the UE
shall initiate the measurements of all neighbour cells indicated by the serving cell, regardless of the measurement rules
currently limiting UE measurement activities.
If the UE in RRC_IDLE has not found any new suitable cell based on searches and measurements using the intra-
frequency, inter-frequency and inter-RAT information indicated in the system information during the time T, the UE
shall initiate cell selection procedures for the selected PLMN as defined in [1], where T=20 s if the UE is not configured
with eDRX_IDLE cycle, and T=MAX(20 s, one eDRX_IDLE cycle) if the UE is configured with eDRX_IDLE cycle.
Table 4.2.2.11.1-1: Nserv_EC
DRX cycle Nserv_EC
length [s] [number of
DRX cycles]
0.32 8
0.64 8
1.28 4
2.56 4
Table 4.2.2.11.1-2: Nserv_EC for UE configured with eDRX_IDLE cycle
eDRX_IDLE cycle length DRX cycle
PTW length Nserv
[s] length [s]
[s] (number [number
of 1.28s of DRX
periods) cycles]
0.32 ≥1.28 (1) 4
5.12 ≤ eDRX_IDLE cycle 0.64 ≥2.56 (2) 4
length ≤ 2621.44 1.28 ≥5.12 (4) 4
2.56 ≥10.24(8) 4
NOTE 1: The number of DRX cycles in this table is given for the DRX
cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section
10.5.5.32 of TS 24.008 [34].
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.2.2.11.2 Measurement and evaluation of intra-frequency E-UTRAN cells
The requirements in this subclause apply if UE is in the enhanced coverage area of the neighbor cell. The UE category
M1 and enhanced coverge applicability of the requirements is defined in section 3.6.The UE is considered to be in
enhanced coverage area of neighbor cell according to RSRP, RSRP Ês/Iot, SCH_RP and SCH Ês/Iot of the neighbor
cell defined in Annex B.1.3 for a corresponding Band.
The UE shall be able to identify new intra-frequency cells and perform RSRP measurements of identified intra-
frequency cells without an explicit intra-frequency neighbour list containing physical layer cell identities. The UE shall
not cause any interruption to the paging reception and acquisition of SI while performing measurement on serving or
any neighbor cells.
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_EC when that Treselection= 0 .
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 95 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall measure RSRP at least every Tmeasure,EUTRAN_Intra_EC for intra-frequency cells that are identified and
measured according to the measurement rules.
The UE shall filter RSRP measurements of each measured intra-frequency cell using at least 4 measurements. Within
the set of measurements used for the filtering, at least two measurements shall be spaced by at least
Tmeasure,EUTRAN_Intra_EC/2.
The UE shall not consider an 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_EC when Treselection = 0, provided that the cell is at least 3dB better ranked and additional conditions
Table 4.2.2.11.2-2 are met. 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.
For UE not configured with eDRX_IDLE cycle, Tdetect,EUTRAN_Intra_EC, Tmeasure,EUTRAN_Intra_EC and Tevaluate, E-UTRAN_intra_EC are
specified in Table 4.2.2.11.2-1 provided that additional conditions Table 4.2.2.11.2-2 are met. For UE configured with
eDRX_IDLE cycle, Tdetect,EUTRAN_Intra_EC, Tmeasure,EUTRAN_Intra_EC and Tevaluate, E-UTRAN_intra_EC are specified in Table
4.2.2.11.2-3 provided that additional conditions Table 4.2.2.11.2-2 are met. Additionally, the requirements in Table
4.2.2.11.2-3 apply provided that the serving cell is configured with eDRX_IDLE and is the same in all PTWs during
any of Tdetect,EUTRAN_Intra_EC, Tmeasure,EUTRAN_Intra_EC and Tevaluate, E-UTRAN_intra_EC when multiple PTWs are used.
Table 4.2.2.11.2-1 : Tdetect,EUTRAN_Intra_EC, Tmeasure,EUTRAN_Intra_EC and Tevaluate, E-UTRAN_intra_EC
DRX Tdetect,EUTRAN_Intra_EC Tmeasure,EUTRAN_Intra_EC Tevaluate,E-
cycle [s] (number of [s] (number of DRX UTRAN_intra_EC
length DRX cycles) cycles) [s] (number of
[s] DRX cycles)
0.32 330.24 (1032) 1.28 (4) 10.24 (32)
0.64 330.24 (516) 1.28 (2) 10.24 (16)
1.28 524.8 (410) 1.28 (1) 12.8 (10)
2.56 1039.36 (406) 2.56 (1) 15.36 (6)
Table 4.2.2.11.2-2: Conditions on SCH Ês/Iot of identified and of the neighbour cell
SCH Ês/Iot of already Neighbouring cell SCH Tdetect,EUTRAN_Intra, ca tM1 (s)
identified cell including Ês/Iot: Q2
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in Table Table
4.2.2.11.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 4.2.2
apply
Q1≥ -6 Q2≥-6 Requirements in 4.2.2
apply
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 96 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.2.2.11.2-3: Tdetect,EUTRAN_Intra_EC, Tmeasure,EUTRAN_Intra_EC and Tevaluate, E-UTRAN_intra_EC for UE configured
with eDRX_IDLE cycle
eDRX_IDLE DRX PTW length Tdetect,EUTRAN_Intra_EC [s] (number N of DRX cycles) Tmeasure,EUTRAN_Intra_EC Tevaluate,E-
cycle length cycle [s] (number [s] (number N of UTRAN_intra_EC
[s] length of 1.28s DRX cycles) [s] (number N of
[s] periods) DRX cycles)
5.12 ≤ 0.32 ≥1.28 (1) Note 3 (406) 0.32 (1) Note 3 (6)
eDRX_IDLE 0.64 ≥1.28 (1) 0.64 (1) Note 3 (6)
cycle length 1.28 ≥1.28 (1) 1.28 (1) Note 3 (6)
≤ 2621.44 2.56 ≥2.56 (2) 2.56 (1) Note 3 (6)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section 10.5.5.32 of TS 24.008 [34].
NOTE 3:TThe detection period and the evaluation period depend on the number N of DRX cycles and are calculated
according to the formula below:
⎡ N ⎤
eDRX _ cycle _ length × ⎢ ⎥
.
⎢ ⎡PTW / DRX _ cycle _ length⎤ ⎥
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.2.2.12 Maximum interruption in paging reception for Category M1 UEs in normal
coverage
UE shall perform the cell re-selection with minimum interruption in monitoring downlink channels for paging
reception. When the UE is configured with eDRX_IDLE cycle, the UE shall not miss any paging in a PTW provided
the paging is sent in at least [2] DRX cycles before the end of that PTW.
At intra-frequency cell re-selection, the UE shall monitor the downlink of serving cell for paging reception until the UE
is capable to start monitoring downlink channels of the target intra-frequency cell for paging reception. The interruption
time shall not exceed TSI-EUTRA-M1-NC + 50 ms.
TSI-EUTRA-M1-NC is the time required for receiving all the relevant system information data, which include MIB and
relavant SIB, according to the reception procedure and the RRC procedure delay of system information blocks defined
in TS 36.331 [2] for an E-UTRAN cell.
These requirements assume normal coverage radio conditions and do not take into account cell re-selection failure.
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.2.2.13 Maximum interruption in paging reception for Category M1 UEs in extended
coverage
UE shall perform the cell re-selection with minimum interruption in monitoring downlink channels for paging
reception. When the UE is configured with eDRX_IDLE cycle, the UE shall not miss any paging in a PTW provided
the paging is sent in at least [2] DRX cycles before the end of that PTW.
At intra-frequency cell re-selection, the UE shall monitor the downlink of serving cell for paging reception until the UE
is capable to start monitoring downlink channels of the target intra-frequency cell for paging reception. The interruption
time shall not exceed TSI-EUTRA-M1-EC + 50 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 97 ETSI TS 136 133 V14.3.0 (2017-04)
TSI-EUTRA-M1-EC is the time required for receiving all the relevant system information data, which include MIB and
relavant SIB, according to the reception procedure and the RRC procedure delay of system information blocks defined
in TS 36.331 [2] for an E-UTRAN cell.
These requirements assume extended coverage radio conditions and do not take into account cell re-selection failure.
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.3 Minimization of Drive Tests (MDT)
UE supporting minimisation of drive tests in RRC_IDLE shall be capable of:
- logging measurements in RRC_IDLE, reporting the logged measurements and meeting requirements in this
clause;
- logging of RRC connection establishment failure, reporting the logged failure and meeting requirements in this
clause;
- logging of radio link failure and handover failure, reporting the logged failure and meeting requirements in this
clause.
4.3.1 Introduction
The logged MDT requirements consist of measurement requirements as specified in clause 4.3.2 and relative time
stamp accuracy requirements as specified in clause 4.3.3. Both sets of requirements are applicable for intra-frequency,
inter-frequency and inter-RAT cases in RRC_IDLE state. The MDT procedures are described in [27].
For RRC connection establishment failure logging and reporting, the MDT requirements consist of requirements for
measurements performed and logged in RRC_IDLE state specified in clause 4.3.2 and relative time stamp accuracy
requirement for RRC connection establishment failure log reporting as specified in clause 4.3.4.
4.3.2 Measurements
The requirements specified in this clause apply for the measurements (GSM carrier RSSI, UTRA CPICH RSCP, UTRA
CPICH Ec/Io, P-CCPCH RSCP for UTRA 1.28 TDD, E-UTRA RSRP, E-UTRA RSRQ, MBSFN RSRP, MBSFN
RSRQ, and MCH BLER) performed and logged by the UE for MDT in RRC_IDLE. The requirements apply for the
measurements included in logged MDT reports and RRC connection establishment failure reports.
4.3.2.1 Requirements
The measurement values that are used to meet
- serving cell and reselection requirements as specified in sections 4.2.2.1, 4.2.2.3, 4.2.2.4, 4.2.2.5,
- MBSFN measurement requirements as specified in section 4.4,
shall also apply to values logged for MDT measurements in RRC_IDLE state.
4.3.3 Relative Time Stamp Accuracy
The relative time stamp for a logged measurement is defined as the time from the moment the MDT configuration was
received at the UE until the measurement was logged, see TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 98 ETSI TS 136 133 V14.3.0 (2017-04)
4.3.3.1 Requirements
The accuracy of the relative time stamping is such that the drift of the time stamping shall be not more than ± 2 seconds
per hour.
4.3.4 Relative Time Stamp Accuracy for RRC Connection Establishment
Failure Log Reporting
Relative time stamp for RRC connection establishment failure log reporting is defined as the time elapsed from the last
RRC connection establishment failure to the time when the log is included in the report TS 36.331 [2]. The UE shall
report the RRC connection establishment failure log, while meeting the accuracy requirement specified in
clause 4.3.4.1.
4.3.4.1 Requirements
The accuracy of the relative time stamping for RRC connection establishment failure log reporting is such that the drift
of the time stamping shall not be larger than ± 0.72 seconds per hour and ± 10 seconds over 48 hours. The relative time
stamp accuracy requirements shall apply provided that:
- no power off or detach occurs after the RRC connection establishment failure had been detected and until the log
is time-stamped.
NOTE: This requirement does not need to be tested.
4.3.5 Relative Time Stamp Accuracy for Radio Link Failure and Handover
Failure Log Reporting
The UE shall report the radio link and handover failure log, while meeting the accuracy requirements specified in this
section.
4.3.5.1 Requirements for timeSinceFailure
Relative time stamp accuracy requirements for timeSinceFailure reported for MDT in a radio link failure or handover
failure log are specified in this clause. timeSinceFailure determines the time elapsed from the last radio link failure or
handover failure in E-UTRA to the time when the log is included in the report TS 36.331 [2].
The accuracy of the relative time stamping for timeSinceFailure is such that the drift of the time stamping shall not be
larger than ± 0.72 seconds per hour and ± 10 seconds over 48 hours. These relative time stamp accuracy requirements
shall apply provided that:
- no power off or detach occurs after the RLF or handover failure had been detected and until the log is time-
stamped.
4.4 MBSFN Measurements
4.4.1 Introduction
The requirements specified in Section 4.4 apply for MBSFN measurements (MBSFN RSRP, MBSFN RSRQ, and MCH
BLER defined in [4]), which are performed in RRC_IDLE state and logged for MDT by UEs which are MBMS-capable
and also indicate their MBSFN measurement logging capability [2].
UE shall measure MBSFN RSRP, MBSFN RSRQ and MCH BLER only in subframes and on carriers where UE is
decoding PMCH. The requirements are specified for any carrier where PMCH is received by UE. The requirements
specified in this section apply for any carrier frequency with configured MBSFN subframes with PMCH, which may be
the same as or different from any serving unicast carrier.
The UE receiving PMCH on any non-serving carrier and performing MBSFN measurements shall not cause
interruptions on any serving carrier in the subframes with paging and non-MBSFN multicast transmissions such as
system information.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 99 ETSI TS 136 133 V14.3.0 (2017-04)
4.4.2 MBSFN RSRP measurements
For UE in RRC_IDLE, the physical layer shall be capable of performing the MBSFN RSRP measurement [4] within the
MBSFN RSRP measurement period and log the measurement, while meeting the MBSFN RSRP measurement accuracy
requirements specified in section 9.8.2. The MBSFN RSRP measurement logging shall be according to the MBSFN
RSRP measurement report mapping specified in Section 9.8.2.2.
The MBSFN RSRP measurement period is defined as MAX(640 ms, period during which the UE decodes [5, Section
10] 5 subframes containing PMCH transmissions).
The same requirement applies for UE configured with DRX or eDRX_IDLE.
4.4.3 MBSFN RSRQ measurements
For UE in RRC_IDLE, the physical layer shall be capable of performing the MBSFN RSRQ measurement [4] within
the MBSFN RSRP measurement period and report the measurement, while meeting the MBSFN RSRQ measurement
accuracy requirements specified in section 9.8.3. The MBSFN RSRQ measurement logging shall be according to the
MBSFN RSRQ measurement report mapping specified in Section 9.8.3.2.
The MBSFN RSRQ measurement period is defined as MAX(640 ms, period during which the UE decodes [5, Section
10] 5 subframes containing PMCH transmissions).
The same requirement applies for UE configured with DRX or eDRX_IDLE.
4.4.4 MCH BLER measurements
The UE physical layer shall be capable of performing and logging the MCH BLER measurement [4] within the MCH
BLER measurement period.
The MCH BLER measurement period is equal to the MBSFN logging interval configured by higher layers [2].
The MCH BLER logging shall be according to the MCH BLER measurement report mapping specified in Section 9.8.4.
The same requirement applies for UE configured with DRX or eDRX_IDLE.
4.5 Proximity-based Services
4.5.1 Introduction
This section contains the requirements for the UE capable of ProSe Direct Communication and/or ProSe Direct
Discovery in RRC_IDLE state.
4.5.2 Requirements
When a UE in RRC_IDLE state is participating in transmissions and/or reception for ProSe Direct Discovery and/or
ProSe Direct Communication, the UE shall meet all the requirements of Section 4.
Note: The UE may need to interrupt ProSe operation in order to meet the requirements of Section 4.
4.5.2.1 Interruptions with ProSe Direct Discovery
A UE capable of ProSe direct discovery in RRC_IDLE state shall not cause any interruption for the reception of paging
and system information:
- while switching reception between ProSe Direct Discovery and a serving cell, or
- when receiving ProSe direct discovery signals or
- while switching receiver chain ON/OFF for ProSe Direct Discovery reception if the UE has a dedicated receiver
chain for ProSe Direct Discovery
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 100 ETSI TS 136 133 V14.3.0 (2017-04)
4.5.2.2 Interruptions with ProSe Direct Communication
A UE capable of ProSe direct communication in RRC_IDLE state shall not cause any interruption for the reception of
paging and system information:
- while switching reception between ProSe Direct Communication and a serving cell, or
- when receiving ProSe direct communication signals, or
- while switching receiver chain ON/OFF for ProSe Direct Communications reception.
4.5.2.3 Initiation/Cease of SLSS transmissions with ProSe Direct Discovery
The requirements in this subclause are applicable to a UE capable of ProSe Direct Discovery and SLSS transmission
and reception.
The requirements apply when the conditions for SLSS transmissions specified in [2] are met; networkControlledSyncTx
is not configured; and syncTxThreshIC is included in SystemInformationBlockType19. The UE shall be capable of
measuring the RSRP of the cell used to transmit Prose Direct Discovery announcements and evaluate to initiate/cease
SLSS transmissions within Tevaluate,SLSS as specified in Table 4.5.2.3-1.
Table 4.5.2.3-1: Tevaluate,SLSS with ProSe Direct Discovery
DRX cycle length [s] Tevaluate,SLSS
[s] (number of DRX cycles)
0.32 1.92 (6)
0.64 3.84 (6)
1.28 7.68 (6)
2.56 15.36 (6)
For the cell used to transmit ProSe Direct Discovery announcements:
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 and RSRQ related side conditions given in
Clause 9.1.5.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band are fulfilled.
4.5.2.4 Initiation/Cease of SLSS transmissions with ProSe Direct Communication
The requirements in this subclause are applicable to a UE capable of ProSe Direct Communication.
The requirements apply when the conditions for SLSS transmissions specified in [2] are met; networkControlledSyncTx
is not configured; and syncTxThreshIC is included in SystemInformationBlockType18. The UE shall be capable of
measuring the RSRP of the cell used to transmit ProSe Direct Communication and evaluate to initiate/cease SLSS
transmissions within Tevaluate,SLSS as specified in Table 4.5.2.4-1.
Table 4.5.2.4-1: Tevaluate,SLSS with ProSe Direct Communication
DRX cycle length [s] Tevaluate,SLSS
[s] (number of DRX cycles)
0.32 1.92 (6)
0.64 3.84 (6)
1.28 7.68 (6)
2.56 15.36 (6)
For the cell used to transmit ProSe Direct Communication:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 101 ETSI TS 136 133 V14.3.0 (2017-04)
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 and RSRQ related side conditions given in
Clause 9.1.5.1 for a corresponding Band are fulfilled,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band are fulfilled.
4.6 Cell Selection and Re-selection Requirements for UE
category NB1
The NB-IoT applicability of the requirements in section 4.6 is defined in Section 3.6.1.
4.6.1 Cell Selection
After a UE has switched on and a PLMN has been selected, the Cell selection process takes place, as described in
TS36.304. This process allows the UE to select a suitable cell where to camp on in order to access available services. In
this process the UE can use stored information (Stored information cell selection) or not (Initial cell selection).
4.6.2 Cell Re-selection
The cell reselection procedure allows the UE to select a more suitable cell and camp on it.
When the UE is in either Camped Normally state or Camped on Any Cell state on a cell, the UE shall attempt to detect,
synchronise, and monitor intra-frequency and inter-frequency cells indicated by the serving NB-IoT cell. For intra-
frequency and inter-frequency cells the serving NB-IoT cell may not provide explicit neighbour list but carrier
frequency information and bandwidth information only. UE measurement activity is also controlled by measurement
rules defined in TS36.304, allowing the UE to limit its measurement activity.
4.6.2.1 Measurement and evaluation of serving NB-IoT cell for UE category NB1 in
normal coverage
The UE shall measure the NRSRP and NRSRQ level of the serving NB-IoT cell and evaluate the cell selection criterion
S defined in [1] for the serving NB-IoT cell at least every DRX cycle.
The UE shall filter the NRSRP and NRSRQ measurements of the NB-IoT serving 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 DRX
cycle/2.
If the UE is not configured with eDRX_IDLE cycle and has evaluated according to Table 4.6.2.1-1 in Nserv_NB-IoT-NC
consecutive DRX cycles that the serving NB-IoT cell does not fulfil the cell selection criterion S, the UE shall initiate
the measurements of all neighbour cells indicated by the serving NB-IoT cell, regardless of the measurement rules
currently limiting UE measurement activities. If the UE is configured with eDRX_IDLE cycle and has evaluated
according to Table 4.6.2.1-2 in Nserv_NB-NC consecutive DRX cycles within a single PTW that the serving NB-IoT cell
does not fulfil the cell selection criterion S, the UE shall initiate the measurements of all neighbour cells indicated by
the serving NB-IoT cell, regardless of the measurement rules currently limiting UE measurement activities.
If the UE in RRC_IDLE has not found any new suitable cell based on searches and measurements using the intra-
frequency and inter-frequency information indicated in the system information during the time T, the UE shall initiate
cell selection procedures for the selected PLMN as defined in [1], where T=40 s if the UE is not configured with
eDRX_IDLE cycle, and T=MAX(40 s, one eDRX_IDLE cycle) if the UE is configured with eDRX_IDLE cycle.
Table 4.6.2.1-1: Nserv_NB--NC
DRX cycle Nserv_NB-IoT-
length [s] NC [number
of DRX
cycles]
1.28 2
2.56 2
5.12 2
10.24 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 102 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.6.2.1-2: Nserv_NB-NC for UE configured with eDRX_IDLE cycle
eDRX_IDLE cycle length [s] DRX cycle
PTW length Nserv_NB-IoT-
length [s]
[s] (number NC [number
of 2.56s of DRX
periods) cycles]
1.28 ≥5.12 (2) 2
2.56 ≥7.68 (3) 2
20.48 ≤ eDRX_IDLE cycle length ≤ 10485.76
5.12 ≥12.8 (5) 2
10.24 ≥23.04 (9) 2
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section X of TS 24.008 [34].
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.6.2.2 Measurements of intra-frequency NB-IoT cells for UE category NB1 in normal
coverage
The UE shall be able to identify new intra-frequency cells and perform NRSRP 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,NB_Intra_NC when Treselection= 0 . An intra frequency cell is considered to be detectable
according to NRSRP, NRSRP Ês/Iot, NSCH_RP and NSCH Ês/Iot defined in Annex B.1.4 for a corresponding Band.
The UE shall measure NRSRP at least every Tmeasure,NB_Intra_NC for intra-frequency cells that are identified and measured
according to the measurement rules.
The UE shall filter NRSRP 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,NB_Intra-NC/2
The UE shall not consider an NB-IoT neighbour cell in cell reselection if it is indicated as not allowed in the
measurement control system information of the serving NB-IoT 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,NB_intra-NC when Treselection = 0, provided that the cell is at least XdB better ranked, where ‘X’ is specified in Table
4.6.2.4-3. When evaluating cells for reselection, the side conditions for NRSRP, NRSRP Ês/Iot, NSCH_RP and NSCH
Ês/Iot apply to both serving and non-serving NB-IoT intra-frequency cells.
If Treselection timer has a non zero value and the intra-frequency cell is better ranked than the serving NB-IoT 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.
For UE not configured with eDRX_IDLE cycle, Tdetect,NB_Intra_NC, Tmeasure,NB_Intra_NC and Tevaluate, NB_intra_NC are specified in
Table 4.6.2.2-1. For UE configured with eDRX_IDLE cycle, Tdetect,NB_Intra -NC, Tmeasure,NB_Intra_NC and Tevaluate, NB_intra-NC are
specified in Table 4.6.2.2-2, where the requirements apply provided that the serving NB-IoT cell is configured with
eDRX_IDLE and is the same in all PTWs during any of Tdetect,NB_Intra_NC, Tmeasure,NB_Intra_NC and Tevaluate, NB_intra_NC when
multiple PTWs are used.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 103 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.6.2.2-1 : Tdetect,NB_Intra_NB-IoT-NC, Tmeasure,NB_Intra_NB-IoT-NC and Tevaluate, NB_intra_NB-IoT-NC
DRX cycle length [s] Tdetect,NB_Intra_NC [s] Tmeasure,NB_Intra_NB_NC Tevaluate,NB_intra_NB_NC
(number of DRX [s] (number of DRX [s] (number of DRX
cycles) cycles) cycles)
1.28 51 (40) 1.28 (1) 6.5 (5)
2.56 51 (20) 2.56 (1) 7.68 (3)
5.12 102 (20) 5.12 (1) 10.24 (2)
10.24 102 (10) 10.24 (1) 20.48 (2)
Table 4.6.2.2-2: Tdetect,NB_Intra_NC, Tmeasure,NB_Intra_NC and Tevaluate,NB_intra_NC for UE configured with eDRX_IDLE
cycle
eDRX_IDLE DRX cycle PTW Tdetect,NB_Intra_NB-IoT-NC [s] (number of DRX cycles) Tmeasure,NB_Intra_NC Tevaluate,NB_intra_NC
cycle length length [s] length [s] [s] (number of [s] (number of
[s] (number DRX cycles) DRX cycles)
of 2.56s
periods)
1.28 ≥ 5.12 ⎡ 20 ⎤ 1.28 (1) 2.56 (2)
(2) eDRX _ cycle _ length × ⎢ ⎥
20.48 ≤ 2.56 ≥ 7.68 ⎢ ⎡PTW / DRX _ cycle _ length ⎤ ⎥ 2.56 (1) 5.12 (2)
eDRX_IDLE (3) (20)
cycle length 5.12 ≥ 12.8 5.12 (1) 10.24 (2)
≤ 10485.76 (5)
10.24 ≥ 23.04] 10.24 (1) 20.48 (2)
(9)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section X of TS 24.008 [34].
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.6.2.3 Measurement and evaluation of serving NB-IoT cell for UE category NB1 in
enhanced coverage
The UE shall measure the NRSRP and NRSRQ level of the serving NB-IoT cell and evaluate the cell selection criterion
S defined in [1] for the serving NB-IoT cell at least every DRX cycle.
The UE shall filter the NRSRP and NRSRQ measurements of the serving NB-IoT cell using at least [4] measurements.
Within the set of measurements used for the filtering, at least two measurements shall be spaced by, at least DRX
cycle/2.
If the UE is not configured with eDRX_IDLE cycle and has evaluated according to Table 4.6.2.3-1 in Nserv_NB_EC
consecutive DRX cycles that the serving NB-IoT cell does not fulfil the cell selection criterion S, the UE shall initiate
the measurements of all neighbour cells indicated by the serving NB-IoT cell, regardless of the measurement rules
currently limiting UE measurement activities. If the UE is configured with eDRX_IDLE cycle and has evaluated
according to Table 4.6.2.3-2 in Nserv_NB-IoT-EC consecutive DRX cycles within a single PTW that the serving NB-IoT cell
does not fulfil the cell selection criterion S, the UE shall initiate the measurements of all neighbour cells indicated by
the serving NB-IoT cell, regardless of the measurement rules currently limiting UE measurement activities.
If the UE in RRC_IDLE has not found any new suitable cell based on searches and measurements using the intra-
frequency and inter-frequency information indicated in the system information during the time T, the UE shall initiate
cell selection procedures for the selected PLMN as defined in [1], where T= 80 s if the UE is not configured with
eDRX_IDLE cycle, and T=MAX(80 s, one eDRX_IDLE cycle) if the UE is configured with eDRX_IDLE cycle.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 104 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.6.2.3-1: Nserv_NB_EC
DRX cycle Nserv_NB-IoT-EC
length [s] [number of
DRX cycles]
1.28 4
2.56 4
5.12 4
10.24 4
Table 4.6.2.3-2: Nserv_NB_EC for UE configured with eDRX_IDLE cycle
eDRX_IDLE cycle length [s] DRX cycle
PTW length [s] Nserv_NB_EC
length [s]
(number of [number of
2.56s periods) DRX cycles]
1.28 ≥ 7.68 (3) 4
2.56 ≥ 12.8 (5) 4
20.48 ≤ eDRX_IDLE cycle length ≤ 10485.76
5.12 ≥ 23.04 (9) 4
10.24 ≥ 43.52 (17) 4
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section X of TS 24.008 [34].
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.6.2.4 Measurements of intra-frequency NB-IoT cells for UE category NB1 in
enhanced coverage
The UE shall be able to identify new intra-frequency cells and perform NRSRP 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,NB_Intra_EC when that Treselection= 0 . An intra frequency cell is considered to be detectable
according to NRSRP, NRSRP Ês/Iot, NSCH_RP and NSCH Ês/Iot defined in Annex B.1.4 for a corresponding Band.
The UE shall measure NRSRP at least every Tmeasure,NB_Intra_EC for intra-frequency cells that are identified and measured
according to the measurement rules.
The UE shall filter NRSRP 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,NB_Intra_ EC/2
The UE shall not consider a NB-IoT neighbour cell in cell reselection, if it is indicated as not allowed in the
measurement control system information of the serving NB-IoT 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,NB_intra_EC when Treselection = 0, provided that the cell is at least XdB better ranked, where ‘X’ is specified in Table
4.6.2.4-3. When evaluating cells for reselection, the side conditions for NRSRP, NRSRP Ês/Iot, NSCH_RP and NSCH
Ês/Iot apply to both serving and non-serving NB-IoT intra-frequency cells.
If Treselection timer has a non zero value and the intra-frequency cell is better ranked than the serving NB-IoT 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.
For UE not configured with eDRX_IDLE cycle, Tdetect,NB_Intra_EC, Tmeasure,NB_Intra_EC and Tevaluate, NB_intra_EC are specified in
Table 4.6.2.4-1 provided that additional conditions in Table 4.6.2.4-3 are met. For UE configured with eDRX_IDLE
cycle, Tdetect,NB_Intra_EC, Tmeasure,NB_Intra_EC and Tevaluate, NB_intra_EC are specified in Table 4.6.2.4-2, where the requirements
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 105 ETSI TS 136 133 V14.3.0 (2017-04)
apply provided that the serving NB-IoT cell is configured with eDRX_IDLE and is the same in all PTWs during any of
Tdetect,NB_Intra_EC, Tmeasure,NB_Intra_EC and Tevaluate, NB_intra_EC when multiple PTWs are used.
Table 4.6.2.4-1 : Tdetect,NB_Intra_EC, Tmeasure,NB_Intra_EC and Tevaluate, NB_intra_EC
DRX cycle length [s] Tdetect,NB_Intra_ EC [s] Tmeasure,NB_Intra_ EC [s] Tevaluate,NB_intra_
(number of DRX (number of DRX EC
cycles) cycles) [s] (number
of DRX
cycles)
1.28 532 (415) 1.28 (1) 12.8 (10)
2.56 532 (208) 2.56 (1) 15.36 (6)
5.12 1063 (208) 5.12 (1) 20.48 (4)
10.24 1063 (104) 10.24 (1) 30.72 (3)
Table 4.6.2.4-2: Tdetect,NB_Intra_EC, Tmeasure,NB_Intra_EC and Tevaluate,NB_intra_EC for UE configured with
eDRX_IDLE cycle
eDRX_IDLE DRX PTW length Tdetect,NB_Intra_EC [s] (number of DRX cycles) Tmeasure,NB_Intra_EC Tevaluate,NB_intraEC
cycle length cycle [s] (number [s] (number of [s] (number of
[s] length of 2.56s DRX cycles) DRX cycles)
[s] periods)
1.28 ≥15.36 ⎡ [406] ⎤ 1.28 (1) 12.8 (10)
(6) eDRX _ cycle _ length × ⎢ ⎥
20.48 ≤ 2.56 ≥17.92 ⎢ ⎡PTW / DRX _ cycle _ length ⎤ ⎥ 2.56 (1) 15.36 (6)
eDRX_IDLE (7) (406)
cycle length 5.12 ≥23.04 5.12 (1) 20.48 (4)
≤ 10485.76 (9)
10.24 ≥33.28 10.24 (1) 30.72 (3)
(13)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section X of TS 24.008 [34].
Table 4.6.2.4-3: Conditions on NSCH Ês/Iot of identified and of the neighbour cell
NSCH Ês/Iot of already Neighbouring cell NSCH Tdetect,EUTRAN_Intra, ca tM1 (s)
identified cell including Ês/Iot: Q2
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 Requirements in Table
4.6.2.4-1 apply.
-15≤Q1<-6 Q2≥-6 Requirements in 4.6.2.2
apply
Q1≥ -6 Q2≥-6 Requirements in 4.6.2.2
apply
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.6.2.5 Measurements of inter-frequency NB cells for UE category NB1 in normal
coverage
The UE shall be able to identify new inter-frequency cells and perform NRSRP measurements of identified inter-
frequency cells if carrier frequency information is provided by the serving NB-IoT cell, even if no explicit neighbour
list with physical layer cell identities is provided.
If Srxlev ≤ SnonIntraSearchP then the UE shall search for and measure inter-frequency layers in preparation for possible
reselection.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 106 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall be able to evaluate whether a newly detectable inter-frequency cell meets the reselection criteria defined
in TS36.304 within Pcarrier * Tdetect,NB_Inter_NC, and able to evaluate whether a newly detectable inter-frequency cell meets
the reselection criteria defined in TS36.304 within Nfreq_NB-IoT * Tdetect,NB_Inter_NC if at least carrier frequency information
is provided for inter-frequency neighbour cells by the serving NB-IoT cells when Treselection = 0 provided that the
reselection criteria is met by a margin of at least 5dB for reselections.An inter-frequency cell is considered to be
detectable according to NRSRP, NRSRP Ês/Iot, NB-IoT_SCH_RP and SCH Ês/Iot defined in Annex B.1.5 for a
corresponding Band.
The UE shall filter NRSRP measurements of each measured inter-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,
Inter_NB-IoT_NC/2.
If an inter-frequency cell 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 inter-frequency cell has met reselection criterion defined TS 36.304 within
Pcarrier * Tevaluate,NB_Inter_NC. When evaluating cells for reselection, the side conditions for NRSRP, NRSRP Ês/Iot,
NSCH_RP and NSCH Ês/Iot apply to both serving and inter-frequency cells.
If Treselection timer has a non zero value and the inter-frequency cell is better ranked than the serving NB-IoT cell, the UE
shall evaluate this inter-frequency cell for the Treselection time. If this cell remains better ranked within this duration, then
the UE shall reselect that cell.
For UE not configured with eDRX_IDLE cycle, Tdetect,NB_Inter_NC, Tmeasure,NB_Inter_NC and Tevaluate, NB_inter_NC are specified in
Table 4.6.2.5-1 for the UE in normal coverage. For UE configured with eDRX_IDLE cycle, Tdetect,NB_Inter_NC,
Tmeasure,NB_Inter_NC and Tevaluate, NB_inter_NC are specified in Table 4.6.2.5-2 for the UE in normal coverage, where the
requirements apply provided that the serving NB-IoT cell is configured with eDRX_IDLE and is the same in all PTWs
during any of Tdetect,NB_Inter_NC, Tmeasure,NB_Inter_NC and Tevaluate, NB_inter_NC when multiple PTWs are used.
Table 4.6.2.5-1 : Tdetect,NB_Inter_NC, Tmeasure,NB_Inter_NC and Tevaluate,NB_Inter_NC
DRX cycle length [s] Tdetect,NB_Inter_ NC [s] Tmeasure,NB_Inter_ NC [s] Tevaluate,NB_Inter_ NC
(number of DRX (number of DRX [s] (number of DRX
cycles) cycles) cycles)
1.28 [51] ([40]) 1.28 ([1]) [6.5] ([5])
2.56 [51] ([20]) 2.56 ([1]) [7.68] ([3])
5.12 [102] ([20]) 5.12 ([1]) [10.24] ([2])
10.24 [102] ([10]) 10.24 ([1]) [20.48] ([2])
Table 4.6.2.5-2: Tdetect,NB_Inter_ NC, Tmeasure,NB_Inter_NC and Tevaluate, NB_inter_ NC for UE configured with
eDRX_IDLE cycle
eDRX_IDLE DRX PTW length [s] Tdetect,NB_Inter_NC [s] (number of DRX cycles) Tmeasure,NB_Inter_NC Tevaluate,NB_inter_
cycle length cycle (number of [s] (number of NC
[s] length [s] 2.56s periods) DRX cycles) [s] (number
of DRX
cycles)
20.48 ≤ 1.28 ≥[5.12] ([2])
eDRX _ cycle _ length × ⎢
⎡ [20] ⎤ 1.28 ([1]) [2.56] ([2])
eDRX_IDLE 2.56 ≥[7.68] ([3]) ⎥ 2.56 ([1]) [5.12] ([2])
cycle length 5.12 ≥[12.8] ([5]) ⎢ ⎡PTW / DRX _ cycle _ length ⎤ ⎥ 5.12 ([1]) [10.24] ([2])
≤ 10485.76 10.24 ≥[23.04] ([9]) (20) 10.24 ([1]) [20.48] ([2])
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section X of TS 24.008 [34].
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 107 ETSI TS 136 133 V14.3.0 (2017-04)
4.6.2.6 Measurements of inter-frequency NB-IoT cells for UE category NB1 in
enhanced coverage
The UE shall be able to identify new inter-frequency cells and perform NRSRP measurements of identified inter-
frequency cells if carrier frequency information is provided by the serving NB-IoT cell, even if no explicit neighbour
list with physical layer cell identities is provided.
The UE shall be able to evaluate whether a newly detectable inter-frequency cell meets the reselection criteria defined
in TS36.304 within Pcarrier * Tdetect,NB_Inter_EC. An inter-frequency cell is considered to be detectable according to NRSRP,
NRSRP Ês/Iot, NSCH_RP and NSCH Ês/Iot defined in Annex B.1.5 for a corresponding Band.
The UE shall not cause any interruption to the paging reception and acquisition of SI while performing measurement on
serving or any neighbor cells.
The UE shall filter NRSRP measurements of each measured inter-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,NB_Inter_NB-IoT_EC/2.
If an inter-frequency cell 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 inter-frequency cell has met reselection criterion defined TS 36.304 within
Pcarrier * Tevaluate,NB_Inter_EC. When evaluating cells for reselection, the side conditions for NRSRP, NRSRP Ês/Iot,
NSCH_RP and NSCH Ês/Iot apply to both serving and inter-frequency NB-IoT cells.
If Treselection timer has a non zero value and the inter-frequency cell is better ranked than the serving NB-IoT cell, the UE
shall evaluate this inter-frequency cell for the Treselection time. If this cell remains better ranked within this duration, then
the UE shall reselect that cell.
For a UE not configured with eDRX_IDLE cycle, Tdetect,NB_Inter_EC, Tmeasure,NB_Inter_EC and Tevaluate, NB_inter_EC are specified in
Table 4.6.2.6-1 provided that additional conditions in Table 4.6.2.6-3 are met for the UE in enhanced coverage. For UE
configured with eDRX_IDLE cycle, Tdetect,NB_Inter_EC, Tmeasure,NB_Inter_EC and Tevaluate, NB_inter_EC are specified in Table
4.6.2.6-2 for the UE in enhanced coverage, where the requirements apply provided that the serving NB-IoT cell is
configured with eDRX_IDLE and is the same in all PTWs during any of Tdetect,NB_Inter_EC, Tmeasure,NB_Inter_EC and Tevaluate,
NB_inter_EC when multiple PTWs are used.
Table 4.6.2.6-1 : Tdetect,NB_Inter_EC, Tmeasure,NB_Inter_EC and Tevaluate,NB_Inter_EC
DRX cycle length Tdetect,NB_Inter_ EC [s] Tmeasure,NB_Inter_ EC [s] Tevaluate,NB_Inter_ EC
[s] (number of DRX (number of DRX [s] (number of
cycles) cycles) DRX cycles)
1.28 [532] ([415]) 1.28 ([1]) 12.8 ([10])
2.56 [532] ([208]) 2.56 ([1]) 15.36 ([6])
5.12 [1063] ([208]) 5.12 ([1]) 20.48 ([4])
10.24 [1063] ([104]) 10.24 ([1]) 30.72 ([3])
Table 4.6.2.6-2: Tdetect,NB_Inter_EC, Tmeasure,NB_Inter_EC and Tevaluate, NB_inter_EC for UE configured with
eDRX_IDLE cycle
eDRX_IDLE DRX cycle PTW length [s] Tdetect,NB_Inter_EC [s] (number of DRX cycles) Tmeasure,NB_Inter_EC [s] Tevaluate,NB_interEC
cycle length [s] length [s] (number of 2.56s (number of DRX [s] (number of
periods) cycles) DRX cycles)
1.28 ≥[15.36] ([6]) ⎡ [406] ⎤ 1.28 ([1]) [12.8]
eDRX _ cycle _ length × ⎢ ⎥ ([10])
20.48 ≤ 2.56 ≥[17.92] ([7]) ⎢⎡PTW / DRX _ cycle _ length ⎤⎥ 2.56 ([1]) [15.36]
eDRX_IDLE ([406]) ([6])
cycle length 5.12 ≥[23.04] ([9]) 5.12 ([1]) [20.48]
≤ 10485.76 ([4])
10.24 ≥[33.28] ([13]) 10.24 ([1]) [30.72]
([3])
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section X of TS 24.008 [34].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 108 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.6.2.6-3: Conditions on NSCH Ês/Iot of identified and of the neighbour cell
NSCH Ês/Iot of already Neighbouring cell Tdetect,NB_Inter_EC (s) Cell Reselection Margin
identified cell including NSCH Ês/Iot: Q2 ‘Y’
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in Table 4.6.2.6-1. 8.3+TBD
-15≤Q1<-6 Q2≥-6 Requirements in 4.6.2.5 apply 8.3+TBD
Q1≥ -6 Q2≥-6 Requirements in 4.6.2.5 apply 4+TBD
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.6.2.7 Maximum interruption in paging reception in normal coverage
UE shall perform the cell re-selection with minimum interruption in monitoring downlink channels for paging
reception. When the UE is configured with eDRX_IDLE cycle, the UE shall not miss any paging in a PTW provided
the paging is sent in at least [2] DRX cycles before the end of that PTW.
At intra-frequency and inter-frequency cell re-selection, the UE shall monitor the downlink of serving NB-IoT cell for
paging reception until the UE is capable to start monitoring downlink channels of the target intra-frequency and inter-
frequency cell for paging reception. The interruption time shall not exceed TSI-NB1-NC + 100 ms.
4.6.2.7A Maximum interruption in paging reception in enhanced coverage
UE shall perform the cell re-selection with minimum interruption in monitoring downlink channels for paging
reception. When the UE is configured with eDRX_IDLE cycle, the UE shall not miss any paging in a PTW provided
the paging is sent in at least [2] DRX cycles before the end of that PTW.
At intra-frequency and inter-frequency cell re-selection, the UE shall monitor the downlink of serving NB-IoT cell for
paging reception until the UE is capable to start monitoring downlink channels of the target intra-frequency and inter-
frequency cell for paging reception. The interruption time shall not exceed TSI-NB1-EC + 100 ms.
4.6.2.8 UE measurement capability
For idle mode cell re-selection purposes, the UE shall be capable of monitoring at least:
- Depending on UE capability, an intra-frequency carrier.
- Depending on UE capability, at least 2 inter-frequency carriers.
4.7 Cell Selection and Re-selection Requirements for UE
category M2
The UE category M2 applicability of the requirements in section 4.7 is defined in Section 3.6.1. The requirements in
this subclause apply if UE is in category M2 UE normal and enhanced coverage area of the serving cell. The category
M2 normal and enhanced coverge applicability of the requirements is defined in section 3.6.1. The UE is considered to
be in normal coverage and enhanced coverage of serving cell according to RSRP, RSRP Ês/Iot, SCH_RP and SCH
Ês/Iot of the serving cell defined in Annex B.1.x and Annex B.1.x for a corresponding Band.
4.7.1 Cell Selection
The requirements defined in section 4.1 apply for this section.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 109 ETSI TS 136 133 V14.3.0 (2017-04)
4.7.2 Cell Re-selection
The cell reselection procedure allows the UE to select a more suitable cell and camp on it.
When the UE is in either Camped Normally state or Camped on Any Cell state on a cell, the UE shall attempt to detect,
synchronise, and monitor intra-frequency and inter-frequency cells indicated by the serving cell. For intra-frequency
and inter-frequency cells the serving cell may not provide explicit neighbour list but carrier frequency information and
bandwidth information only. UE measurement activity is also controlled by measurement rules defined in TS36.304,
allowing the UE to limit its measurement activity.
If the UE is in normal coverage as defined in section 3.6.1, the requirements in section 4.7.2.1 apply. If the UE is in
enhanced coverage as defined in section 3.6.1, the requirements in section 4.7.2.2 apply.
4.7.2.1 Cell Re-selection requirements for UE category M2 in normal coverage
4.7.2.1.1 Measurement and evaluation of serving cell for UE category M2 in normal
coverage
Unless otherwise specified, the requirements defined in section 4.2.2.1 apply for this section.
4.7.2.1.2 Measurements of intra-frequency cells for UE category M2 in normal
coverage
Unless otherwise specified, the requirements defined in section 4.2.2.3 apply for this section.
4.7.2.1.3 Measurements of inter-frequency cells for UE category M2 in normal
coverage
Unless otherwise specified, the requirements defined in section 4.2.2.4 apply for this section.
4.7.2.1.4 Maximum allowed layers for multiple monitoring for UE category M2 in
normal coverage
The UE category M2 in normal coverage shall be capable of monitoring at least:
- Depending on UE capability, 2 FDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 2 TDD E-UTRA inter-frequency carriers.
In addition to the requirements defined above, the UE shall be capable of monitoring a total of at least 5 carrier
frequency layers, which include one serving carrier frequency and any of the above defined combination of E-UTRA
FDD inter-frequency and E-UTRA TDD inter-frequency layers.
4.7.2.2 Cell Re-selection requirements for UE category M2 in enhanced coverage
4.7.2.2.1 Measurement and evaluation of serving cell for UE category M2 in
enhanced coverage
The requirements defined in clause 4.2.2.11.1 apply for this section, except that Cat-M2 UE also measures RSRQ.
4.7.2.2.2 Measurements of intra-frequency cells for UE category M2 in enhanced
coverage
The requirements defined in clause 4.2.2.11.2 apply for this section, except that Cat-M2 UE also measures RSRQ.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 110 ETSI TS 136 133 V14.3.0 (2017-04)
4.7.2.2.3 Measurements of inter-frequency cells for UE category M2 in enhanced
coverage
The UE shall be able to identify new inter-frequency cells and perform RSRP or RSRQ measurements of identified
inter-frequency cells if carrier frequency information is provided by the serving cell, even if no explicit neighbour list
with physical layer cell identities is provided. The UE shall not cause any interruption to the paging reception and
acquisition of SI while performing measurement on serving or any neighbor cells.
If Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ then the UE shall search for inter-frequency layers of higher priority
at least every Thigher_priority_search where Thigher_priority_search is described in clause 4.2.2.
If Srxlev ≤ SnonIntraSearchP or Squal ≤ SnonIntraSearchQ then the UE shall search for and measure inter-frequency 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 higher priority layers shall be the same as that defined below.
The UE shall be able to evaluate whether a newly detectable inter-frequency cell meets the reselection criteria defined
in TS36.304 within Tdetect,EUTRAN_Inter_EC, 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 TBDdB for reselections based on ranking or TBDdB for RSRP reselections based on absolute priorities or TBDdB
for RSRQ reselections based on absolute priorities.
When higher priority cells are found by the higher priority search, they shall be measured at least every Tmeasure,E-
UTRAN_Inter_EC . If, after detecting a cell in a higher priority search, it is determined that reselection has not occurred then
the UE is not required to continuously measure the detected cell to evaluate the ongoing possibility of reselection.
However, the minimum measurement filtering requirements specified later in this clause shall still be met by the UE
before it makes any determination that it may stop measuring the cell. If the UE detects on a E-UTRA carrier a cell
whose physical identity is indicated as not allowed for that carrier in the measurement control system information of the
serving cell, the UE is not required to perform measurements on that cell.
The UE shall measure RSRP or RSRQ at least every Tmeasure,EUTRAN_Inter_EC for identified lower or equal priority inter-
frequency cells. If the UE detects on a E-UTRA carrier a cell whose physical identity is indicated as not allowed for that
carrier in the measurement control system information of the serving cell, the UE is not required to perform
measurements on that cell.
The UE shall filter RSRP or RSRQ measurements of each measured higher, lower and equal priority inter-frequency
cell using at least 4 measurements. Within the set of measurements used for the filtering, at least two measurements
shall be spaced by at least Tmeasure,EUTRAN_Inter_EC/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 inter-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 inter-frequency cell has met reselection criterion defined TS 36.304
within Tevaluate,E-UTRAN_Inter_EC, when Treselection = 0 provided that the reselection criteria is met by a margin of at least
TBDdB for reselections based on ranking or TBDdB for RSRP reselections based on absolute priorities or TBDdB for
RSRQ reselections based on absolute priorities, and additional conditions Table 4.7.2.2.3-2 are met. When evaluating
cells for reselection, the side conditions for RSRP and SCH apply to both serving and inter-frequency cells.
If Treselection timer has a non zero value and the inter-frequency cell is better ranked than the serving cell, the UE shall
evaluate this inter-frequency cell for the Treselection time. If this cell remains better ranked within this duration, then the
UE shall reselect that cell.
For UE not configured with eDRX_IDLE cycle, Tdetect,EUTRAN_Inter_EC, Tmeasure,EUTRAN_Inter_EC and Tevaluate, E-UTRAN_inter_EC are
specified in Table 4.7.2.2.3-1 provided that additional conditions Table 4.7.2.2.3-2 are met. For UE configured with
eDRX_IDLE cycle, Tdetect,EUTRAN_Inter_EC, Tmeasure,EUTRAN_Inter_EC and Tevaluate, E-UTRAN_inter_EC are specified in Table 4.2.2.14-
3 provided that additional conditions Table 4.7.2.2.3-2 are met. Additionally, the requirements in Table 4.2.2.14-3 apply
provided that the serving cell is configured with eDRX_IDLE and is the same in all PTWs during any of
Tdetect,EUTRAN_Inter_EC, Tmeasure,EUTRAN_Inter_EC and Tevaluate, E-UTRAN_inter_EC when multiple PTWs are used.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 111 ETSI TS 136 133 V14.3.0 (2017-04)
Table 4.7.2.2.3-1: Tdetect,EUTRAN_Inter_EC, Tmeasure,EUTRAN_Inter_EC and Tevaluate,E-UTRAN_Inter_EC
DRX Tdetect,EUTRAN_Inter_EC Tmeasure,EUTRAN_Inter_EC Tevaluate,E-
cycle [s] (number of [s] (number of DRX UTRAN_Inter_EC
length DRX cycles) cycles) [s]
[s] (number of
DRX
cycles)
0.32 330.24 (1032) 1.28 (4) 10.24 (32)
0.64 330.24 (516) 1.28 (2) 10.24 (16)
1.28 524.8 (410) 1.28 (1) 12.8 (10)
2.56 1039.36 (406) 2.56 (1) 15.36 (6)
Table 4.7.2.2.3-2: Conditions on SCH Ês/Iot of identified and of the neighbour cell
SCH Ês/Iot of already Neighbouring cell SCH Tdetect,EUTRAN_Intra, ca tM1 (s)
identified cell including Ês/Iot: Q2
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in Table Table
4.2.2.14.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 4.2.2
apply
Q1≥ -6 Q2≥-6 Requirements in 4.2.2
apply
Table 4.7.2.2.3-3: Tdetect,EUTRAN_Inter_EC, Tmeasure,EUTRAN_Inter_EC and Tevaluate, E-UTRAN_inter_EC for UE configured
with eDRX_IDLE cycle
eDRX_IDLE DRX PTW Tdetect,EUTRAN_Inter_EC [s] (number of DRX cycles) Tmeasure,EUTRAN_Inter_EC Tevaluate,E-
cycle length cycle length [s] (number of DRX UTRAN_inter_EC
[s] length [s] cycles) [s] (number of
[s] (number DRX cycles)
of 1.28s
periods)
5.12 ≤ 0.32 ≥1.28 (1) 0.32 (1) Note 3 (6)
eDRX_IDLE 0.64 ≥1.28 (1) 0.64 (1) Note 3 (6)
cycle length ≤ 1.28 ≥1.28 (1) Note 3 (406)
1.28 (1) Note 3 (6)
2621.44 2.56 ≥2.56 (2) 2.56 (1) Note 3 (6)
NOTE 1: The number of DRX cycles in this table is given for the DRX cycles within PTWs.
NOTE 2: The eDRX_IDLE cycle lengths are as specified in Section 10.5.5.32 of TS 24.008 [34].
NOTE 3: TThe detection period and the evaluation period depend on the number N of DRX cycles and are calculated
according to the formula below:
⎡ N ⎤
eDRX _ cycle _ length × ⎢ ⎥
.
⎢⎡ PTW / DRX _ cycle _ length ⎤⎥
For higher priority cells, a UE may optionally use a shorter value for Tmeasure,EUTRAN_Inter_EC,which shall not be less than
Max(0.64 s, one DRX cycle).
For any requirement in this section, when the UE transitions between any two states when being configured with
eDRX_IDLE, being configured with eDRX_IDLE cycle, changing eDRX_IDLE cycle length, or changing PTW
configuration, the UE shall meet the transition requirement, which is the less stringent requirement of the two
requirements corresponding to the first state and the second state, during the transition time interval which is the time
corresponding to the transition requirement. After the transition time interval, the UE has to meet the requirement
corresponding to the second state.
4.7.2.2.4 Maximum allowed layers for multiple monitoring for UE category M2 in
enhanced coverage
The UE category M2 in normal coverage shall be capable of monitoring at least:
- Depending on UE capability, 2 FDD E-UTRA inter-frequency carriers, and
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 112 ETSI TS 136 133 V14.3.0 (2017-04)
- Depending on UE capability, 2 TDD E-UTRA inter-frequency carriers.
In addition to the requirements defined above, the UE shall be capable of monitoring a total of at least 5 carrier
frequency layers, which include one serving carrier frequency and any of the above defined combination of E-UTRA
FDD inter-frequency and E-UTRA TDD inter-frequency layers.
5 E-UTRAN RRC_CONNECTED state mobility
Note 1: For the performance requirements specified hereafter, the state when no DRX is used is defined as follows:
- DRX and eDRX_CONN parameters are not configured; or
- DRX or eDRX_CONN parameters are configured and
○ drx-InactivityTimer is running; or
○ drx-RetransmissionTimer is running; or
○ mac-ContentionResolutionTimer is running; or
○ a Scheduling Request sent on PUCCH is pending; 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 signaled preamble (only applicable to
UEs in RRC_CONNECTED).
Otherwise
- It is the state when DRX is used.
Note 2: Unless otherwise stated, the requirements in sections 5.1, 5.2.2.2, 5.2.2.3, 5.2.2.4, 5.3 and 5.4 are also
applicable when a UE is configured with Scell(s) or PSCell.
5.1 E-UTRAN Handover
5.1.1 Introduction
5.1.2 Requirements
5.1.2.1 E-UTRAN FDD – FDD
The requirements in this clause are applicable to both intra-frequency and inter-frequency handovers.
5.1.2.1.1 Handover delay
Procedure delays for all procedures that can command a handover are specified in TS 36.331 [2].
When the UE receives a RRC message implying handover the UE shall be ready to start the transmission of the new
uplink PRACH channel within Dhandover seconds from the end of the last TTI containing the RRC command when UE is
configured with normal or make-before-break handover.
When the UE receives a RRC message implying handover, the UE shall be ready to start the transmission of the new
uplink PUSCH channel within Dhandover seconds from the end of the last TTI containing the RRC command when UE is
configured with RACH-less or combination of RACH-less and make-before-break handover.
Where:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 113 ETSI TS 136 133 V14.3.0 (2017-04)
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.1.2.1.2.1.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.1.2.1.2.2 when UE is configured with RACH-less handover.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.1.2.1.2.1 when UE is configured with make-before-break handover.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.1.2.1.2.2 when UE is configured with combination of make-before-break and RACH-less
handover.
5.1.2.1.2 Interruption time
The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the
time the UE starts transmission of the new PRACH when UE is configured with normal or make-before-break
handover, or the time the UE starts transmission of new PUSCH when UE is configured with RACH-less or
combination of make-before-break and RACH-less handover, excluding the RRC procedure delay. This requirement
applies when UE is not required to perform any synchronisation procedure before transmitting on the new PRACH or
on the new PUSCH.
5.1.2.1.2.1 Interruption time for normal handover
When intra-frequency or inter-frequency handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TIU + 20 ms
Where:
Tsearch is the time required to search the target cell when the target cell is not already known when the handover
command is received by the UE. If the target cell is known, then Tsearch = 0 ms. If the target cell is unknown and
signal quality is sufficient for successful cell detection on the first attempt, then Tsearch = 80 ms. Regardless of
whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
TIU is the interruption uncertainty in acquiring the first available PRACH occasion in the new cell. TIU can be up
to 30 ms.
NOTE: The actual value of TIU shall depend upon the PRACH configuration used in the target cell.
In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement
during the last 5 seconds otherwise it is unknown. Relevant cell identification requirements are described in
Clause 8.1.2.2.1 for intra-frequency handover and Clause 8.1.2.3.1 for inter-frequency handover.
5.1.2.1.2.2 Interruption time for RACH-less handover
When intra-frequency or inter-frequency RACH-less handover is commanded, the interruption time shall be less than
Tinterrupt
Tinterrupt = Tsearch + TIU + 20 ms
Where:
Tsearch is the time required to search the target cell when the target cell is not already known when the handover
command is received by the UE. If the target cell is known, then Tsearch = 0 ms. If the target cell is unknown and
signal quality is sufficient for successful cell detection on the first attempt, then Tsearch = 80 ms. Regardless of
whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
TIU is the interruption uncertainty in acquiring the first PUSCH transmission occasion when UE is configured with
RACH-less handover in the new cell.
- TIU can be up to 10 ms if UL grant is configured in RRC command.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 114 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The actual value of TIU shall depend upon the UL grant configuration in RRC command.
- TIU can be up to TUL_grant if UL grant is not configured in RRC command.
NOTE: TUL_grant is the time required to acquire and process uplink grant from the target Pcell.
In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds otherwise it is unknown. Relevant cell identification requirements are described in Clause 8.1.2.2.1
for intra-frequency handover and Clause 8.1.2.3.1 for inter-frequency handover.
5.1.2.1.2.3 Interruption time for make-before-break handover
When intra-frequency make-before-break handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = 5 ms
NOTE: The same bandwidth of source cell and target cell is assumed.
5.1.2.1.2.4 Interruption time for combination of make-before-break and RACH-less handover
When intra-frequency combination of make-before-break and RACH-less handover is commanded, the interruption
time shall be less than Tinterrupt
Tinterrupt = 5 + TUL_grant ms
Where:
- TUL_grant = 0 ms if UL grant is provided in RRC command.
- TUL_grant is the time required to acquire and process uplink grant from the target Pcell if UL grant is not provided
in RRC command.
NOTE: The same bandwidth of source cell and target cell is assumed.
5.2.2.2 E-UTRAN FDD – TDD
The requirements in this clause are applicable to handover from FDD to TDD. The requirements in this clause shall
apply to UE supporting FDD and TDD.
The requirements in clause 5.2.2.4 apply for this section.
5.2.2.2.1 (Void)
5.2.2.2.2 (Void)
5.2.2.3 E-UTRAN TDD – FDD
The requirements in this clause are applicable to handover from TDD to FDD. The requirements in this clause shall
apply to UE supporting FDD and TDD.
The requirements in clause 5.1.2.1 apply for this section.
5.2.2.3.1 (Void)
5.2.2.3.2 (Void)
5.2.2.4 E-UTRAN TDD – TDD
The requirements in this clause are applicable to both intra-frequency and inter-frequency handovers.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 115 ETSI TS 136 133 V14.3.0 (2017-04)
5.2.2.4.1 Handover delay
Procedure delays for all procedures that can command a handover are specified in TS 36.331 [2].
When the UE receives a RRC message implying handover, the UE shall be ready to start the transmission of the new
uplink PRACH channel within Dhandover seconds from the end of the last TTI containing the RRC command when UE is
configured with normal or make-before-break handover.
When the UE receives a RRC message implying handover, the UE shall be ready to start the transmission of the new
uplink PUSCH channel within Dhandover seconds from the end of the last TTI containing the RRC command when UE is
configured with RACH-less or combination of RACH-less and make-before-break handover.
Where:
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5. 2.2.4.2.1.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.2.2.4.2.2 when UE is configured with RACH-less handover.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.2.2.4.2.1 when UE is configured with make-before-break handover.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.2.2.4.2.2 when UE is configured with combination of make-before-break and RACH-less
handover.
5.2.2.4.2 Interruption time
The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the
time the UE starts transmission of the new PRACH when UE is configured with normal or make-before-break
handover, or the time the UE starts transmission of new PUSCH when UE is configured with RACH-less or
combination of make-before-break and RACH-less handover, excluding the RRC procedure delay. This requirement
applies when UE is not required to perform any synchronisation procedure before transmitting on the new PRACH or
on the new PUSCH.
5.2.2.4.2.1 Interruption time for normal handover
When intra-frequency or inter-frequency handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TIU + 20 ms
Where
Tsearch is the time required to search the target cell when the target cell is not already known when the handover
command is received by the UE. If the target cell is known, then Tsearch = 0 ms. If the target cell is unknown and
signal quality is sufficient for successful cell detection on the first attempt, then Tsearch = 80 ms. Regardless of
whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
TIU is the interruption uncertainty in acquiring the first available PRACH occasion in the new cell. TIU can be up
to 30 ms.
NOTE: The actual value of TIU shall depend upon the PRACH configuration used in the target cell.
In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds otherwise it is unknown. Relevant cell identification requirements are described in Clause 8.1.2.2.2
for intra-frequency handover and Clause 8.1.2.3.4 for inter-frequency handover.
5.2.2.4.2.2 Interruption time for RACH-less handover
When intra-frequency or inter-frequency RACH-less handover is commanded, the interruption time shall be less than
Tinterrupt
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 116 ETSI TS 136 133 V14.3.0 (2017-04)
Tinterrupt = Tsearch + TIU + 20 ms
Where:
Tsearch is the time required to search the target cell when the target cell is not already known when the handover
command is received by the UE. If the target cell is known, then Tsearch = 0 ms. If the target cell is unknown and
signal quality is sufficient for successful cell detection on the first attempt, then Tsearch = 80 ms. Regardless of
whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
TIU is the interruption uncertainty in acquiring the first PUSCH transmission occasion when UE is configured with
RACH-less handover in the new cell.
- TIU can be up to 10 ms if UL grant is configured in RRC command.
NOTE: The actual value of TIU shall depend upon the UL grant configuration in RRC command.
- TIU can be up to TUL_grant if UL grant is not configured in RRC command.
NOTE: TUL_grant is the time required to acquire and process uplink grant from the target Pcell.
In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds otherwise it is unknown. Relevant cell identification requirements are described in Clause 8.1.2.2.2
for intra-frequency handover and Clause 8.1.2.3.2 for inter-frequency handover.
5. 2.2.4.2.3 Interruption time for make-before-break handover
When intra-frequency make-before-break handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = 5 ms
NOTE: The same bandwidth of source cell and target cell is assumed.
5. 2.2.4.2.4 Interruption time for combination of make-before-break and RACH-less handover
When intra-frequency combination of make-before-break and RACH-less handover is commanded, the interruption
time shall be less than Tinterrupt
Tinterrupt = 5 + TUL_grant ms
Where:
- TUL_grant = 0 ms if UL grant is provided in RRC command.
- TUL_grant is the time required to acquire and process uplink grant from the target Pcell if UL grant is not provided
in RRC command.
NOTE: The same bandwidth of source cell and target cell is assumed.
5.2.2.5 E-UTRAN HD–FDD
The requirements in this clause are applicable to intra-frequency handovers.
5.2.2.5.1 Handover delay
Procedure delays for all procedures that can command a handover are specified in TS 36.331 [2].
When the UE receives a RRC message implying handover the UE shall be ready to start the transmission of the new
uplink PRACH channel within Dhandover seconds from the end of the last TTI containing the RRC command when UE is
configured with normal or make-before-break handover.
When the UE receives a RRC message implying handover, the UE shall be ready to start the transmission of the new
uplink PUSCH channel within Dhandover seconds from the end of the last TTI containing the RRC command when UE is
configured with RACH-less or combination of RACH-less and make-before-break handover.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 117 ETSI TS 136 133 V14.3.0 (2017-04)
Where:
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.2.2.5.2.1.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.2.2.5.2.2 when UE is configured with RACH-less handover.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.2.2.5.2.1 when UE is configured with make-before-break handover.
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.2.2.1.5.2 when UE is configured with combination of make-before-break and RACH-less
handover.
5.2.2.5.2 Interruption time
The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the
time the UE starts transmission of the new PRACH when UE is configured with normal or make-before-break
handover, or the time the UE starts transmission of new PUSCH when UE is configured with RACH-less or
combination of make-before-break and RACH-less handover, excluding the RRC procedure delay. This requirement
applies when UE is not required to perform any synchronisation procedure before transmitting on the new PRACH or
on the new PUSCH.
5.2.2.4.2.1 Interruption time for normal handover
When intra-frequency handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TIU + 20 ms
Where:
Tsearch is the time required to search the target cell when the target cell is not already known when the handover
command is received by the UE. If the target cell is known, then Tsearch = 0 ms. If the target cell is unknown and
signal quality is sufficient for successful cell detection on the first attempt, then Tsearch = 80 ms. Regardless of
whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
TIU is the interruption uncertainty in acquiring the first available PRACH occasion in the new cell. TIU can be up
to 30 ms.
NOTE: The actual value of TIU shall depend upon the PRACH configuration used in the target cell.
In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement
during the last 5 seconds otherwise it is unknown. Relevant cell identification requirements are described in
Clause 8.5.2.1.2 for intra-frequency handover.
5.2.2.5.2.2 Interruption time for RACH-less handover
When intra-frequency RACH-less handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TIU + 20 ms
Where:
Tsearch is the time required to search the target cell when the target cell is not already known when the handover
command is received by the UE. If the target cell is known, then Tsearch = 0 ms. If the target cell is unknown and
signal quality is sufficient for successful cell detection on the first attempt, then Tsearch = 80 ms. Regardless of
whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
TIU is the interruption uncertainty in acquiring the first PUSCH transmission occasion when UE is configured with
RACH-less handover in the new cell.
- TIU can be up to 10 ms if UL grant is configured in RRC command.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 118 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The actual value of TIU shall depend upon the UL grant configuration in RRC command.
- TIU can be up to TUL_grant if UL grant is not configured in RRC command.
NOTE: TUL_grant is the time required to acquire and process uplink grant from the target Pcell.
In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds otherwise it is unknown. Relevant cell identification requirements are described in Clause 8.5.2.1.2
for intra-frequency handover.
5. 2.2.5.2.3 Interruption time for make-before-break handover
When intra-frequency make-before-break handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = 5 ms
NOTE: The same bandwidth of source cell and target cell is assumed.
5. 2.2.5.2.4 Interruption time for combination of make-before-break and RACH-less handover
When intra-frequency combination of make-before-break and RACH-less handover is commanded, the interruption
time shall be less than Tinterrupt
Tinterrupt = 5 + TUL_grant ms
Where:
- TUL_grant = 0 ms if UL grant is provided in RRC command.
- TUL_grant is the time required to acquire and process uplink grant from the target Pcell if UL grant is not provided in
RRC command.
NOTE: The same bandwidth of source cell and target cell is assumed.
5.3 Handover to other RATs
5.3.1 E-UTRAN - UTRAN FDD Handover
5.3.1.1 Introduction
The purpose of inter-RAT handover from E-UTRAN to UTRAN FDD is to change the radio access mode from E-
UTRAN to UTRAN FDD. The handover procedure is initiated from E-UTRAN with a RRC message that implies a
hard handover as described in TS 36.331 [2].
5.3.1.1.1 Handover delay
When the UE receives a RRC message implying handover to UTRAN the UE shall be ready to start the transmission of
the new UTRA uplink DPCCH within Dhandover seconds from the end of the last E-UTRAN TTI containing the RRC
MOBILITY FROM E-UTRA command.
where:
- Dhandover equals the RRC procedure delay, which is 50 ms plus the interruption time stated in clause 5.3.1.1.2.
5.3.1.1.2 Interruption time
The interruption time is the time between the end of the last TTI containing the RRC command on the E-UTRAN
PDSCH and the time the UE starts transmission on the uplink DPCCH in UTRAN FDD, excluding the RRC procedure
delay. The interruption time depends on whether the target cell is known to the UE or not.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 119 ETSI TS 136 133 V14.3.0 (2017-04)
The target cell is known if it has been measured by the UE during the last 5 seconds otherwise it is unknown. The UE
shall always perform a UTRA synchronisation procedure as part of the handover procedure.
If the target cell is known the interruption time shall be less than Tinterrupt1
Tinterrupt1 = TIU+Tsync+50+ 10*Fmax + TMC ms
If the target cell is unknown the interruption time shall be less than Tinterrupt2
Tinterrupt2 = TIU+Tsync+150 + 10*Fmax + TMC ms
This requirement shall be met, provided that there is one target cell in the MOBILITY FROM E-UTRA command.
Performance requirements for E-UTRA to UTRA soft handover are not specified. When UE is connected to an E-
UTRA cell, UTRA SFN timing measurements are not reported. This implies that the timing of the DPCH of the UTRA
target cells in the active set cannot be configured by UTRAN to guarantee that all target cells fall within the UE
reception window of T0 +/- 148 chips.
Where:
TIU is the interruption uncertainty when changing the timing from the E-UTRAN to the new UTRAN
cell. TIU can be up to one UTRA frame (10 ms).
Fmax denotes the maximum number of radio frames within the transmission time intervals of all
transport channels that are multiplexed into the same CCTrCH on the UTRA target cell. If HS-
PDSCH is configured in the UTRA target cell, Fmax is 4 radio frames.
Tsync is the time required for measuring the downlink DPCCH channel as stated in TS 25.214 [20],
clause 4.3.1.2. In case higher layers indicate the usage of a post-verification period Tsync=0 ms.
Otherwise Tsync=40 ms.
TMC TMC is 0ms if a single UTRA cell is configured as the handover target, otherwise 20ms if handover
to UTRA with 1, 2 or 3 UTRA carriers with secondary HS-PDSCH is configured.
The phase reference is the primary CPICH.
The requirements in this clause assume that N312 has the smallest possible value i.e. only one insync is required.
5.3.2 E-UTRAN - UTRAN TDD Handover
5.3.2.1 Introduction
The purpose of inter-RAT handover from E-UTRAN to UTRAN TDD is to change the radio access mode from E-
UTRAN to UTRAN TDD. The handover procedure is initiated from E-UTRAN with a RRC message that implies a
hard handover as described in TS 36.331 [2].
5.3.2.2 Requirements
The requirements in this clause shall apply to UE supporting E-UTRAN and UTRAN TDD.
5.3.2.2.1 Handover delay
When the UE receives a RRC message implying E-UTRAN/UTRAN TDD handover the UE shall be ready to start the
transmission of the SYNC-UL within Dhandover seconds from the end of the last TTI containing the RRC MOBILITY
FROM E-UTRA command.
Where:
- Dhandover equals the RRC procedure delay, which is 50 ms plus the interruption time stated in clause 5.3.2.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 120 ETSI TS 136 133 V14.3.0 (2017-04)
5.3.2.2.2 Interruption time
The interruption time is the time between the end of the last TTI containing the RRC command on the E-UTRAN
PDSCH and the time the UE starts transmission on the SYNC-UL in UTRAN TDD, excluding the RRC procedure
delay. The interruption time depends on whether the target cell is known to the UE or not.
The UE shall always perform a UTRA synchronisation procedure as part of the handover procedure.
If the target cell has been measured by the UE during the last 5 seconds, the interruption time shall be less than
Tinterrupt1
Tinterrupt1= Toffset+TUL+30*FSFN+20 ms
If the target cell has not been measured by the UE during the last 5 seconds, the interruption time shall be less than
Tinterrupt2
Tinterrupt2= Toffset+TUL+30*FSFN+180 ms
Where:
Toffset Equal to 10 ms, the frame timing uncertainty between the old cell and the target cell and the time
that can elapse until the appearance of a Beacon channel
TUL Equal to 10 ms, the time that can elapse until the appearance of the UL timeslot in the target cell
FSFN Equal to 1 if SFN decoding is required and equal to 0 otherwise
The interruption time requirements for an unknown target cell shall apply only if the signal quality of the unknown
target cell is sufficient for successful synchronisation with one attempt.
5.3.3 E-UTRAN - GSM Handover
5.3.3.1 Introduction
The purpose of inter-RAT handover from E-UTRAN to GSM is to transfer a connection between the UE and E-
UTRAN to GSM. The handover procedure is initiated from E-UTRAN with a RRC message (MOBILITY FROM E-
UTRA). The procedure is described in in TS 36.331 [2].
5.3.3.2 Requirements
The requirements in this clause shall apply to UE supporting E-UTRAN and GSM.
The requirements given below in Tables 5.3.3.2.1-1 and 5.3.3.2.2-1 for the case where the UE has not synchronised to
the GSM cell before receiving the RRC MOBILITY FROM E-UTRA command are valid when the signal quality of the
GSM cell is sufficient for successful synchronisation with one attempt. If the UE is unable to synchronise to the GSM
cell on the first attempt, it shall continue to search for synchronisation information for up to 800 ms duration. If after
800 ms the UE has not synchronised to the GSM cell it shall follow the handover failure procedure specified in
TS 36.331 [2].
5.3.3.2.1 Handover delay
When the UE receives a RRC MOBILITY FROM E-UTRA command the UE shall be ready to transmit (as specified in
[10]) on the channel of the new RAT within the value in table 5.3.3.2.1-1 from the end of the last TTI containing the
RRC command. The UE shall process the RRC procedures for the MOBILITY FROM E-UTRA command within 50
ms, which is noted as RRC procedure delay.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 121 ETSI TS 136 133 V14.3.0 (2017-04)
Table 5.3.3.2.1-1: E-UTRAN/GSM handover - handover delay
UE synchronisation status handover delay [ms]
The UE has synchronised to the GSM cell before the 90
RRC MOBILITY FROM E-UTRA COMMAND is received
The UE has not synchronised to the GSM cell before 190
the RRC MOBILITY FROM E-UTRA COMMAND is
received
5.3.3.2.2 Interruption time
The interruption time is the time between the end of the last TTI containing the RRC command on the E-UTRAN
PDSCH and the time the UE starts transmission on the uplink channel in GSM, excluding the RRC procedure delay.
The interruption time depends on whether the UE has synchronized to the target GSM cell or not and shall be less than
the value specified in table 5.3.3.2.2-1.
Table 5.3.3.2.2-1: E-UTRAN/GSM handover - interruption time
Synchronisation status Interruption time [ms]
The UE has synchronised to the GSM cell before the 40
RRC MOBILITY FROM E-UTRA COMMAND is received
The UE has not synchronised to the GSM cell before 140
the RRC MOBILITY FROM E-UTRA COMMAND is
received
5.4 Handover to Non-3GPP RATs
5.4.1 E-UTRAN – HRPD Handover
5.4.1.1 Introduction
The handover procedure from E-UTRAN to HRPD is initiated when E-UTRAN sends handover command to the UE
through dedicated RRC signalling.
5.4.1.1.1 Handover delay
The handover delay (Dhandover) is defined as the sum of the RRC procedure delay, which is 50 ms and the interruption
time specified in clause 5.4.1.1.2.
When the UE receives a RRC message implying handover to HRPD, the UE shall be ready to start the transmission of
the new reverse control channel in HRPD within Dhandover from the end of the last E-UTRAN TTI containing the RRC
command.
5.4.1.1.2 Interruption time
The interruption time is the time between the end of the last TTI containing the RRC command on the E-UTRAN
PDSCH and the time the UE starts transmission of the reverse control channel in HRPD, excluding the RRC procedure
delay. The interruption time depends on whether the target cell is known to the UE or not.
An HRPD cell is known if it has been measured by the UE during the last 5 seconds otherwise it is unknown. Under the
reference conditions specified in sub-clause 6.6 of [13], the interruption time shall be less than Tinterrupt
Tinterrupt = TIU + 40 + 10*KC*SWK + 10*OC*SWO ms
Where:
TIU It is the interruption uncertainty when changing the timing from the E-UTRAN to the new HRPD
cell. TIU can be up to one HRPD frame (26.66 ms).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 122 ETSI TS 136 133 V14.3.0 (2017-04)
⎡ srch_win_k ⎤
SWK is SWK = ⎢ ⎥⎥ where srch_win_k is the number of HRPD chips indicated by the
⎢ 60
search window for known target HRPD cells in the message
⎡ srch_win_o ⎤
SWO is SWO = ⎢ ⎥⎥ where srch_win_o is the number of HRPD chips indicated by the
⎢ 60
search window for unknown target HRPD cells in the message
KC It is the number of known target HRPD cells in the message, and
OC It is the number of unknown target HRPD cells in the message.
Note: An additional delay in the interruption time may occur due to the reverse link silence interval [11], which is
specific to HRPD.
5.4.2 E-UTRAN – cdma2000 1X Handover
5.4.2.1 Introduction
The handover procedure from E-UTRAN to cdma2000 1X is initiated when E-UTRAN sends handover command to the
UE through dedicated RRC signalling.
5.4.2.1.1 Handover delay
The handover delay (Dhandover) is defined as the sum of the RRC procedure delay, which is 130 ms and the
interruption time specified in clause 5.4.2.1.2.
When the UE receives a RRC message implying handover to cdma2000 1X, the UE shall be ready to start the
transmission of the new reverse control channel in cdma2000 1X within Dhandover from the end of the last E-UTRAN
TTI containing the RRC command.
5.4.2.1.2 Interruption time
The interruption time is the time between the end of the last TTI containing the RRC command on the E-UTRAN
PDSCH and the time the UE starts transmission of the reverse control channel in cdma2000 1X, excluding the RRC
procedure delay. The interruption time depends on whether the target cell is known to the UE or not.
A cdma2000 1X cell is known if it has been measured by the UE during the last 5 seconds otherwise it is unknown.
Under the reference conditions specified in sub-clause 4.2.1 of [14], the interruption time shall be less than Tinterrupt:
Tinterrupt = TIU + 140 + 10*KC*SWK + 10*OC*SWO ms
Where:
TIU It is the interruption uncertainty when changing the timing from the E-UTRAN to the new
cdma2000 1X cell. TIU can be up to one cdma2000 1X frame (20 ms).
⎡ srch_win_k ⎤
SWK is SWK = ⎢ ⎥⎥ where srch_win_k is the number of cdma2000 1x chips indicated by
⎢ 300
the search window for known target cdma2000 1x cells in the message
⎡ srch_win_o ⎤
SWO is SWO = ⎢ ⎥⎥ where srch_win_o is the number of cdma2000 1x chips indicated by
⎢ 300
the search window for unknown target cdma2000 1x cells in the message
KC It is the number of known target cdma2000 1X cells in the message, and
OC It is the number of unknown target cdma2000 1X cells in the message.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 123 ETSI TS 136 133 V14.3.0 (2017-04)
5.5 E-UTRAN Handover for Cat-M1 UEs in CEModeA
5.5.1 Introduction
This section defines the E-UTRAN intra-frequency handover requirements for Cat-M1 UEs in CEModeA as required
by TS 36.300 [25].
5.5.2 Requirements
5.5.2.1 E-UTRAN FDD – FDD for Cat-M1 FDD UEs
The requirements in this clause are applicable to FDD intra-frequency handovers for a Cat-M1 FDD UE in CEModeA.
5.5.2.1.1 Handover delay
Procedure delays for all procedures that can command a handover are specified in TS 36.331 [2].
When the UE receives a RRC message implying handover the UE shall finish the transmission of all repetitions of the
new uplink PRACH channel within Dhandover seconds from the end of the last TTI containing the RRC command,
Where:
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.5.2.1.2.
5.5.2.1.2 Interruption time
The interruption time is the time between the end of the last TTI containing the RRC command on the old PDSCH and
the moment the UE has transmitted all repetitions of PRACH in the target cell, excluding the RRC procedure delay.
This requirement applies when UE is not required to perform any synchronisation procedure before transmitting on the
new PRACH.
When intra-frequency handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TMIB + TIU + 20 ms
Where:
- Tsearch is the time required to search the target cell when the handover command is received by the UE. If the
target cell is known, then Tsearch = 0 ms. If the target cell is unknown and signal quality is sufficient for
successful cell detection on the first attempt, then Tsearch = 80 ms. Otherwise, Tsearch shall be according to the non-
DRX cell identification requirements specified in Clause 8.13.2.1 for a UE configured with CEModeA.
Regardless of whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
- TMIB is the time required for acquiring the MIB information of the target cell.
- TIU is the time required to complete the transmission of PRACH in the target cell. The actual value of TIU shall
depend upon the uncertainity in acquiring the first available PRACH occasion based on the PRACH
configuration used in the target cell and the PRACH coverage enhancement level used by the UE for sending the
random access preamble to the target cell.
- In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement
for a time duration equal or longer than the time duration required for the cell identification. Otherwise, it is
unknown. The time duration required for the cell identification is specified in relevant intra-frequency cell
identification requirements as described in Clause 8.13.2.1 for CEModeA.
5.5.2.2 E-UTRAN FDD – FDD for Cat-M1 HD – FDD UEs
The requirements defined in clause 5.5.2.1 are applicable to FDD intra-frequency handovers for a Cat-M1 HD-FDD UE
in CEModeA.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 124 ETSI TS 136 133 V14.3.0 (2017-04)
5.5.2.3 E-UTRAN TDD – TDD for Cat-M1 TDD UEs
The requirements in this clause are applicable to TDD intra-frequency handovers for a Cat-M1 UE in CEModeA.
5.5.2.3.1 Handover delay
Procedure delays for all procedures that can command a handover are specified in TS 36.331 [2].
When the UE receives a RRC message implying handover the UE shall finish the transmission of all repetitions of the
new uplink PRACH channel within Dhandover seconds from the end of the last TTI containing the RRC command.
Where:
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.5.2.3.2.
5.5.2.3.2 Interruption time
The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the
moment the UE has transmitted all repetitions of PRACH in the target cell, excluding the RRC procedure delay. This
requirement applies when UE is not required to perform any synchronisation procedure before transmitting on the new
PRACH.
When intra-frequency handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TMIB + TIU + 20 ms
Where
- Tsearch is the time required to search the target cell when the handover command is received by the UE. If the
target cell is known, then Tsearch = 0 ms. If the target cell is unknown and signal quality is sufficient for
successful cell detection on the first attempt, then Tsearch = 80 ms. Otherwise, Tsearch shall be according to the non-
DRX cell identification requirements specified in Clause 8.13.2.1 for a UE configured with CEModeA.
Regardless of whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
- TMIB is the time required for acquiring the MIB information of the target cell.
- TIU is the time required to complete the transmission of PRACH in the target cell. The actual value of TIU shall
depend upon the uncertainity in acquiring the first available PRACH occasion based on the PRACH
configuration used in the target cell and the PRACH coverage enhancement level used by the UE for sending the
random access preamble to the target cell.
- In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement
for a time duration equal or longer than the time duration required for the cell identification. Otherwise, it is
unknown. The time duration required for the cell identification is specified in relevant intra-frequency cell
identification requirements as described in Clause 8.13.2.1 for CEModeA.
5.6 E-UTRAN Handover for Cat-M1 UEs in CEModeB
5.6.1 Introduction
This section defines the E-UTRAN intra-frequency handover requirements for Cat-M1 UEs configured with
CEModeB as required by TS 36.300 [25].
5.6.2 Requirements
5.6.2.1 E-UTRAN FDD – FDD for Cat-M1 FDD UEs
The requirements in this clause are applicable to FDD intra-frequency handovers for a Cat-M1 FDD UE configured
with CEModeB.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 125 ETSI TS 136 133 V14.3.0 (2017-04)
5.6.2.1.1 Handover delay
Procedure delays for all procedures that can command a handover are specified in TS 36.331 [2].
When the UE receives a RRC message implying handover the UE shall finish the transmission of all repetitions of the
new uplink PRACH channel within Dhandover seconds from the end of the last TTI containing the RRC command,
Where:
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.6.2.1.2.
5.6.2.1.2 Interruption time
The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the
time the UE starts transmission of the new PRACH, excluding the RRC procedure delay. This requirement applies
when UE is not required to perform any synchronisation procedure before transmitting on the new PRACH.
When intra-frequency handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TMIB + TIU + 20 ms
Where:
- Tsearch is the time required to search the target cell when the handover command is received by the UE. If the
target cell is known, then Tsearch = 0 ms. If the target cell is unknown and signal quality is sufficient for
successful cell detection on the first attempt, then Tsearch = 80 ms. Otherwise, Tsearch shall be according to the non-
DRX cell identification requirements specified in Clause 8.13.3.1 for a UE configured with CEModeB.
Regardless of whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
- TMIB is the time required for acquiring the MIB information of the target cell.
- TIU is the time required to complete the transmission of PRACH in the target cell. The actual value of TIU shall
depend upon the uncertainity in acquiring the first available PRACH occasion based on the PRACH
configuration used in the target cell and the PRACH coverage enhancement level used by the UE for sending the
random access preamble to the target cell.
- In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement
for a time duration equal or longer than the time duration required for the cell identification. Otherwise, it is
unknown. The time duration required for the cell identification is specified in relevant intra-frequency cell
identification requirements as described in Clause 8.13.3.1 for a UE configured with CEModeB.
5.6.2.2 E-UTRAN FDD – FDD for Cat-M1 HD – FDD UEs
The requirements defined in clause 5.6.2.1 are applicable to FDD intra-frequency handovers for a Cat-M1 HD-FDD UE
configured with CEModeB.
5.6.2.3 E-UTRAN TDD – TDD for Cat-M1 TDD UEs
The requirements in this clause are applicable to TDD intra-frequency handovers for a Cat-M1 UE configured with
CEModeB.
5.6.2.3.1 Handover delay
Procedure delays for all procedures that can command a handover are specified in TS 36.331 [2].
When the UE receives a RRC message implying handover the UE shall finish the transmission of all repetitions of the
new uplink PRACH channel within Dhandover seconds from the end of the last TTI containing the RRC command.
Where:
Dhandover equals the maximum RRC procedure delay to be defined in clause 11.2 in TS 36.331 [2] plus the interruption
time stated in clause 5.6.2.3.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 126 ETSI TS 136 133 V14.3.0 (2017-04)
5.6.2.3.2 Interruption time
The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the
moment the UE has transmitted all repetitions of PRACH in the target cell, excluding the RRC procedure delay. This
requirement applies when UE is not required to perform any synchronisation procedure before transmitting on the new
PRACH.
When intra-frequency handover is commanded, the interruption time shall be less than Tinterrupt
Tinterrupt = Tsearch + TMIB + TIU + 20 ms
Where:
- Tsearch is the time required to search the target cell when the handover command is received by the UE. If the
target cell is known, then Tsearch = 0 ms. If the target cell is unknown and signal quality is sufficient for
successful cell detection on the first attempt, then Tsearch = 80 ms. Otherwise, Tsearch shall be according to the non-
DRX cell identification requirements specified in Clause 8.13.3.1 for a UE configured with CEModeB.
Regardless of whether DRX is in use by the UE, Tsearch shall still be based on non-DRX target cell search times.
- TMIB is the time required for acquiring the MIB information of the target cell.
- TIU is the time required to complete the transmission of PRACH in the target cell. The actual value of TIU shall
depend upon the availability of first available PRACH occasion based on the PRACH configuration used in the
target cell and the PRACH coverage enhancement level used by the UE for sending the random access preamble
to the target cell.
- In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement
for a time duration equal or longer than the time duration required for the cell identification. Otherwise, it is
unknown. The time duration required for the cell identification is specified in relevant intra-frequency cell
identification requirements as described in Clause 8.13.3.1 for a UE configured with CEModeB.
6 RRC Connection Mobility Control
6.1 RRC Re-establishment
The requirements in this clause are applicable to both E-UTRAN FDD and TDD.
6.1.1 Introduction
RRC connection re-establishment is initiated when a UE in RRC connected mode looses RRC connection due to any of
these reasons: radio link failure, handover failure or radio link problem. The RRC es-tablishment procedure is specified
in clause 5.3.7 in TS 36.331 [2].
6.1.2 Requirements
In RRC connected mode the UE shall be capable of sending RRCConnectionReestablishmentRequest message within
Tre-establish_delay seconds from the moment it detects a loss in RRC connection. The total RRC connection delay (Tre-
establish_delay) shall be less than:
Tre-establish_delay = TUL_grant + TUE_re-establish_delay
TUL_grant: It is the time required to acquire and process uplink grant from the target PCell. The uplink grant is required to
transmit RRCConnectionReestablishmentRequest message.
The UE re-establishment delay (TUE_re-establish_delay) is specified in clause 6.1.2.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 127 ETSI TS 136 133 V14.3.0 (2017-04)
6.1.2.1 UE Re-establishment delay requirement
The UE re-establishment delay (TUE_re-establish_delay) is the time between the moments when any of the conditions
requiring RRC re-establishment as defined in clause 5.3.7 in TS 36.331 [2] is detected by the UE to the time when the
UE sends PRACH to the target PCell. The UE re-establishment delay (TUE_re-establish_delay) requirement shall be less than:
TUE-re-establish_delay = 50 ms + Nfreq*Tsearch + TSI + TPRACH
Tsearch: It is the time required by the UE to search the target PCell.
Tsearch = It is 100 ms if the target PCell is known by the UE; the target PCell is known if it has been measured by
the UE in the last 5 seconds.
Tsearch = It is 800 ms if the target PCell is unknown by the UE; the target PCell is unknown if it has not been
measured by the UE in the last 5 seconds.
TSI = It is the time required for receiving all the relevant system information according to the reception procedure
and the RRC procedure delay of system information blocks defined in TS 36.331 [2] for the target PCell.
TPRACH = The additional delay caused by the random access procedure; it will be at least 10 ms due to random
access occasion and there might be additional delay due to ramping procedure.
Nfreq: It is the total number of E-UTRA frequencies to be monitored for RRC re-establishment; Nfreq = 1 if the
target PCell is known.
There is no requirement if the target cell does not contain the UE context.
6.2 Random Access
6.2.1 Introduction
The random access procedure is used when establishing the layer 1 communication between the UE and E-UTRAN.
The random access is specified in clause 6 of TS 36.213[3] and the control of the RACH transmission is specified in
clause 5.1 of TS 36.321[17]. Contention based random access procedures can only be carried out on PCell and PSCell,
while non-contention based random access procedures can be carried out on PCell, one or two activated SCell(s), and
PSCell. For UEs supporting CA with FS3 SCells, the random access procedures can only be carried out on PCell.
6.2.2 Requirements
The UE shall have capability to calculate PRACH transmission power according to the PRACH power formula defined
in TS 36.213[3] and apply this power level at the first preamble or additional preambles. The absolute power applied to
the first preamble shall have an accuracy as specified in table 6.3.5.1.1-1 of TS 36.101[5]. The relative power applied to
additional preambles shall have an accuracy as specified in table 6.3.5.2.1-1 of 36.101[5].
The UE shall indicate a Random Access problem to upper layers if the maximum number of preamble transmission
counter has been reached for the random access procedure on PCell or PSCell as specified in clause 5.1.4 in
TS 36.321 [17].
The UE shall stop preamble transmission if maximum number of preamble transmission counter has been reached for
the random access procedure on an activated Scell as specified in clause 5.1.4 in TS 36.321 [17].
6.2.2.1 Contention based random access
6.2.2.1.1 Correct behaviour when receiving Random Access Response reception
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 128 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
6.2.2.1.2 Correct behaviour when not receiving Random Access Response reception
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window defined in clause 5.1.4 TS 36.321.
6.2.2.1.3 Correct behaviour when receiving a NACK on msg3
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3.
6.2.2.1.4 Void
6.2.2.1.5 Correct behaviour when receiving a message over Temporary C-RNTI
The UE shall send ACK if the Contention Resolution is successful.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
6.2.2.1.6 Correct behaviour when contention Resolution timer expires
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
6.2.2.2 Non-Contention based random access
6.2.2.2.1 Correct behaviour when receiving Random Access Response
The UE may stop monitoring for Random Access Response(s) if the Random Access Response contains a Random
Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-transmit the preamble with the calculated PRACH transmission power if all received Random Access
Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble.
The UE is not allowed to re-transmit the preamble on SCells without PUSCH on the SCCs to which SRS carrier based
switching is performed, even if all received Random Access Responses contain Random Access Preamble identifiers do
not match the transmitted Random Access Preamble, unless the UE receives the corresponding new PDCCH order.
6.2.2.2.2 Correct behaviour when not receiving Random Access Response
The UE shall re-transmit the preamble with the calculated PRACH transmission power.
The UE is not allowed to re-transmit the preamble on SCells without PUSCH on the SCCs to which SRS carrier based
switching is performed, unless the UE receives the corresponding new PDCCH order.
6.2.3 Requirements for Cat-M1 UEs
In addition to the requirements defined in 6.2.1 and 6.2.2, a Cat-M1 UE shall also execute the random access procedure
defined in clause 5.1 in TS 36.321 [17] using the PRACH configuration contained in PRACH-ConfigSIB in TS 36.331
[2]
- Determines the enhanced coverage level based on the RSRP measurement and the configured criterion (RSRP-
ThresholdsPrach [2]) as defined in section 5.1.1, TS 36,321 [17],
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 129 ETSI TS 136 133 V14.3.0 (2017-04)
- Selects PRACH resources [2] configured for the corresponding enhanced coverage level as determined in the
previous step and;
- Transmits or re- transmits PRACH preamble using the selected PRACH resources and PRACH configuration.
6.3 RRC Connection Release with Redirection
6.3.1 Introduction
RRC connection release with redirection is initiated by the UE upon receiving the “RRCConnectionRelease” message
from the E-UTRAN, TS 36.331 [2]. The RRC connection release with redirection procedure is specified in clause 5.3.8
in TS 36.331 [2].
The requirements in this clause are applicable to both E-UTRAN FDD and TDD.
6.3.2 Requirements
6.3.2.1 RRC connection release with redirection to UTRAN FDD
The UE shall be capable of performing the RRC connection release with redirection to the target UTRAN FDD cell
within Tconnection_release_redirect_UTRA FDD.
The time delay (Tconnection_release_redirect_UTRA FDD) is the time between the end of the last TTI containing the RRC command,
“RRCConnectionRelease” (TS 36.331 [2]) on the E-UTRAN PDSCH and the time the UE starts to send random access
to the target UTRA FDD cell. The time delay (Tconnection_release_redirect_UTRA FDD) shall be less than:
Tconnection_release_redirect_UTRA FDD = TRRC_procedure_delay + Tidentify-UTRA FDD + TSI-UTRA FDD + TRA
The target UTRA FDD cell shall be considered detectable when:
- CPICH Ec/Io > -15 dB,
- SCH_Ec/Io > -15 dB for at least one channel tap and SCH_Ec/Ior is equally divided between primary
synchronisation code and secondary synchronisation code.
TRRC_procedure_delay: It is the RRC procedure for processing the received message “RRCConnectionRelease”. It shall be
less than 110 ms.
Tidentify-UTRA FDD: It is the time to identify the target UTRA FDD cell. It shall be less than 500 ms.
TSI-UTRA FDD: It is the time required for acquiring all the relevant system information of the target UTRA FDD cell. This
time depends upon whether the UE is provided with the relevant system information of the target UTRA FDD cell or
not by the E-UTRAN before the RRC connection is released.
TRA: It is the delay caused due to the random access procedure when sending random access to the target UTRA FDD
cell.
6.3.2.2 RRC connection release with redirection to GERAN
The UE shall be capable of performing the RRC connection release with redirection to the target GERAN cell within
Tconnection_release_redirect_GERAN.
The time delay (Tconnection_release_redirect_GERAN) is the time between the end of the last TTI containing the RRC command,
“RRCConnectionRelease” (TS 36.331 [2]) on the E-UTRAN PDSCH and the time the UE starts to send random access
to the target GERAN cell. The time delay (Tconnection_release_redirect_GERAN) shall be less than:
Tconnection_release_redirect_ GERAN = TRRC_procedure_delay + Tidentify-GERAN + TSI-GERAN + TRA
The target GERAN cell shall be considered detectable when the UE receives the GERAN cell at levels down to 10 dB +
the reference sensitivity level or reference interference levels as specified in [9].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 130 ETSI TS 136 133 V14.3.0 (2017-04)
TRRC_procedure_delay: It is the RRC procedure for processing the received message “RRCConnectionRelease”. It shall be
less than 110 ms.
Tidentify-UTRA GERAN: It is the time to identify the BSIC of the target GERAN cell. It shall be less than 1 second.
TSI-UTRA GERAN: It is the time required for acquiring all the relevant system information of the target GERAN cell. This
time depends upon whether the UE is provided with the relevant system information of the target GERAN cell or not by
the E-UTRAN before the RRC connection is released.
TRA: It is the delay caused due to the random access procedure when sending random access burst to the target GERAN
cell.
6.3.2.3 RRC connection release with redirection to UTRAN TDD
The UE shall be capable of performing the RRC connection release with redirection to the target UTRAN TDD cell
within Tconnection_release_redirect_UTRA TDD.
The time delay (Tconnection_release_redirect_UTRA TDD) is the time between the end of the last TTI containing the RRC
command, “RRCConnectionRelease” (TS 36.331 [2]) on the E-UTRAN PDSCH and the time the UE starts to send
random access to the target UTRA TDD cell. The time delay (Tconnection_release_redirect_UTRA TDD) shall be less than:
Tconnection_release_redirect_UTRA TDD = TRRC_procedure_delay + Tidentify-UTRA TDD* Nredirect-UTRA TDD + TSI-UTRA TDD + TRA
The target UTRA TDD cell shall be considered detectable when:
- P-CCPCH Ec/Io > -6 dB,
- DwPCH_Ec/Io > -1 dB.
TRRC_procedure_delay: It is the RRC procedure for processing the received message “RRCConnectionRelease”. It shall be
less than 110 ms.
Tidentify-UTRA TDD: It is the time to identify the target UTRA TDD cell. It shall be less than 500 ms.
TSI-UTRA TDD: It is the time required for acquiring all the relevant system information of the target UTRA TDD cell. This
time depends upon whether the UE is provided with the relevant system information of the target UTRA TDD cell or
not by the E-UTRAN before the RRC connection is released.
TRA: It is the delay caused due to the random access procedure when sending random access to the target UTRA TDD
cell.
Nredirect-UTRA TDD: It is the total number of target UTRA TDD frequencies included in RedirectedCarrierInfo in
“RRCConnectionRelease” message. It can be up to 4 UTRA TDD frequencies.
6.4 CSG Proximity Indication for E-UTRAN and UTRAN
6.4.1 Introduction
The requirements defined in this section are applicable to a UE supporting and configured with CSG proximity
indication and are valid when a UE is entering the proximity of one or more CSG member cell(s) or leaving the
proximity of all CSG member cell(s) on a UTRA or E-UTRA frequency as specified in [2].
The detection of CSG proximity is based on a UE autonomous search function.
6.4.2 Requirements
The UE shall initiate transmission of the ProximityIndication message with “entering” according to [2] within [6]
minutes after entering the proximity of one or more CSG member cell(s) on a UTRA or E-UTRA frequency.
The UE shall initiate transmission of the ProximityIndication message with “leaving” according to [2] within [6]
minutes after leaving the proximity of all CSG member cell(s) on a UTRA or E-UTRA frequency.
There is no need for statistical testing of this requirement.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 131 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: Entering the proximity of one or more CSG member cell(s) means that the UE is near a cell whose CSG
ID is in the UE’s CSG whitelist (as determined based on autonomous search procedures). Leaving the
proximity of one or more CSG member cell(s) means that the UE is no longer near any cell whose CSG
ID is in the UE’s CSG whitelist.
6.5 RRC Re-establishment for NB-IoT UEs
6.5.1 Introduction
RRC connection re-establishment is initiated when a UE in RRC connected mode looses RRC connection due to any of
these reasons: radio link failure or radio link problem. The RRC re-establishment procedure is specified in clause 5.3.7
in TS 36.331 [2].
6.5.2 Requirements
In RRC connected mode the UE shall be capable of sending RRCConnectionReestablishmentRequest message within
Tre-establish_delay_NB-IoT seconds from the moment it detects a loss in RRC connection. The total RRC connection delay (Tre-
establish_delay_NB-IoT) shall be less than:
Tre-establish_delay_NB-IoT = TUL_grant + TUE_re-establish_delay_NB-IoT
TUL_grant: It is the time required to acquire and process uplink grant from the target cell. The uplink grant is required to
transmit RRCConnectionReestablishmentRequest message.
The UE re-establishment delay (TUE_re-establish_delay_NB-IoT) is specified in clause 6.5.2.1 for a UE in normal coverage and in
clause 6.5.2.2 for a UE in enhanced coverage.
6.5.2.1 UE Re-establishment delay requirement in normal coverage
The UE re-establishment delay (TUE_re-establish_delay_NB-IoT) is the time between the moments when any of the conditions
requiring RRC re-establishment as defined in clause 5.3.7 in TS 36.331 [2] is detected by the UE to the time when the
UE sends PRACH preamble to the target cell. The UE re-establishment delay (TUE_re-establish_delay_NB-IoT) requirement shall
be less than:
TUE-re-establish_delay_NB-IoT = 100 ms + NNB-Iot-freq*Tsearch_NB1-NC + TSI_NB1-NC + TPRACH_NB-IoT
Tsearch_NB1-NC: It is the time required by the UE to search the target cell:
If the target cell is known, then Tsearch_NB1-NC = 0 ms. If the target cell is unknown and signal quality is
sufficient for successful cell detection on the first attempt, then Tsearch_NB1-NC = [80] ms. Otherwise, Tsearch_NB1-
NC = [1400] ms.
TSI_NB1-NC: It is the time required for receiving all the relevant system information according to the reception
procedure and the RRC procedure delay of system information blocks defined in TS 36.331 [2] for the target cell
for a UE in normal coverage.
TPRACH_NB-IoT: The additional delay caused by the random access procedure. The actual value of TPRACH_NB-IoT
shall depend upon the NPRACH configuration used in the target cell and the number of repetition used by UE
for sending random access to the target cell. There might be additional delay due to ramping procedure.
NNB-Iot-freq: It is the total number of NB-IoT frequencies to be monitored for RRC re-establishment; NNB-Iot-freq = 1
if the target cell is known.
There is no requirement if the target cell does not contain the UE context.
6.5.2.2 UE Re-establishment delay requirement in enhanced coverage
The UE re-establishment delay (TUE_re-establish_delay_NB-IoT) is the time between the moments when any of the conditions
requiring RRC re-establishment as defined in clause 5.3.7 in TS 36.331 [2] is detected by the UE to the time when the
UE sends PRACH preamble to the target cell. The UE re-establishment delay (TUE_re-establish_delay_NB-IoT) requirement shall
be less than:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 132 ETSI TS 136 133 V14.3.0 (2017-04)
TUE-re-establish_delay_NB-IoT = 100 ms + NNB-Iot-freq*Tsearch_NB1-EC + TSI_NB1-EC + TPRACH_NB-IoT
- Tsearch_NB1-EC: It is the time required by the UE to search the target cell:
- If the target cell is known, then Tsearch_NB1-EC = 0 ms. If the target cell is unknown and signal quality is
sufficient for successful cell detection on the first attempt, then Tsearch_NB1-EC = [80] ms. Otherwise, Tsearch_NB1-
EC = [14800] ms.
- TSI_NB1-EC: It is the time required for receiving all the relevant system information according to the reception
procedure and the RRC procedure delay of system information blocks defined in TS 36.331 [2] for the target cell
for a UE in enhanced coverage.
- TPRACH_NB-IoT: The additional delay caused by the random access procedure. The actual value of TPRACH_NB-IoT
shall depend upon the NPRACH configuration used in the target cell and the number of repetition used by UE
for sending random access to the target cell. There might be additional delay due to ramping procedure.
- NNB-Iot-freq: It is the total number of NB-IoT frequencies to be monitored for RRC re-establishment; NNB-Iot-freq = 1
if the target cell is known.
There is no requirement if the target cell does not contain the UE context.
6.6 Random Access for UE category NB1
6.6.1 Introduction
The random access procedure is used when establishing the layer 1 communication between the UE and NB-IoT. The
random access is specified in clause 6 of TS 36.213[3] and the control of the RACH transmission is specified in
clause 5.1 of TS 36.321[17]. Only contention-based random access is supported for NB-IoT
6.6.2 Requirements
The UE shall have capability to calculate NPRACH transmission power according to the NPRACH power formula
defined in TS 36.213[3] and apply this power level at the first preamble or additional preambles. The absolute power
applied to the first preamble shall have an accuracy as specified in TS 36.101[5]. The relative power applied to
additional preambles shall have an accuracy as specified in 36.101[5].
The UE shall indicate a Random Access problem to upper layers if the maximum number of preamble transmission
counter has been reached for the random access procedure on target cell as specified in clause 5.1.4 in TS 36.321 [17].
6.6.2.1 Correct behaviour when receiving Random Access Response reception
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated NPRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
6.6.2.2 Correct behaviour when not receiving Random Access Response reception
The UE shall re-select a preamble and transmit with the calculated NPRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window defined in clause 5.1.4 TS 36.321.
6.6.2.3 Correct behaviour when receiving a NACK on msg3
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3.
6.6.2.4 Correct behaviour when receiving a message over Temporary C-RNTI
The UE shall send ACK if the Contention Resolution is successful.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 133 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall re-select a preamble and transmit with the calculated NPRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
6.6.2.5 Correct behaviour when contention Resolution timer expires
The UE shall re-select a preamble and transmit with the calculated NPRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
6.6.3 Requirements for NPRACH configuration
In addition to the requirements defined in 6.6.2, UE shall also execute the random access procedure defined in
clause 5.1 in TS 36.321 [17] using the NPRACH configuration contained in NPRACH-ConfigSIB-NB in TS 36.331 [2]
- Determines the enhanced coverage level based on the NRSRP measurement and the configured criterion as
defined in section 5.1.1, TS 36,321 [17],
- Selects NPRACH resources [2] configured for the corresponding enhanced coverage level as determined in the
previous step and;
- Transmits or re-transmits NPRACH preamble using the selected NPRACH resources and NPRACH
configuration.
6.7 RRC Re-establishment for Cat-M1 UEs
6.7.1 Introduction
RRC connection re-establishment is initiated when a Cat-M1 UE either configured with CEModeA or CEModeB in
RRC connected mode looses RRC connection due to any of these reasons: radio link failure or radio link problem. The
RRC re-establishment procedure is specified in clause 5.3.7 in TS 36.331 [2].
6.7.2 Requirements
In RRC connected mode the UE shall be capable of sending RRCConnectionReestablishmentRequest message within
Tre-establish_delay seconds from the moment it detects a loss in RRC connection. The total RRC connection delay (Tre-
establish_delay) shall be less than:
Tre-establish_delay = TUL_grant + TUE_re-establish_delay
TUL_grant: It is the time required to acquire and process uplink grant from the target cell. The uplink grant is required to
transmit RRCConnectionReestablishmentRequest message.
The UE re-establishment delay (TUE_re-establish_delay) is specified in clause 6.7.2.1 for a UE configured with CEModeA and
in clause 6.7.2.2 for a UE configured with CEModeB.
6.7.2.1 UE Re-establishment delay requirement for CEModeA
The UE re-establishment delay (TUE_re-establish_delay) is the time between the moments when any of the conditions
requiring RRC re-establishment as defined in clause 5.3.7 in TS 36.331 [2] is detected by the UE to the moment the UE
has transmitted all repetitions of the PRACH preamble to the target cell. The UE re-establishment delay (TUE_re-
establish_delay) requirement for a UE configured with CEModeA shall be less than:
TUE-re-establish_delay=50 ms + Nfreq*Tsearch + TSI-EUTRA-M1-CEModeA + TPRACH
- Tsearch is the time required by the UE to search the target cell. Tsearch =100 ms if the target cell is known by the
UE. Otherwise, Tsearch is specified in relevant intra-frequency cell identification requirements as described in
Clause 8.13.2.1 for a UE configured with CEModeA. Regardless of whether DRX is in use by the UE, Tsearch
shall still be based on non-DRX target cell search times.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 134 ETSI TS 136 133 V14.3.0 (2017-04)
In the above requirement, a cell is known if it has been meeting the relevant cell identification requirement for a
time duration equal to or longer than the time duration required for the cell identification. Otherwise, it is
unknown.
- TSI: It is the time required for receiving all the relevant system information according to the reception procedure
and the RRC procedure delay of system information blocks defined in TS 36.331 [2] for the target cell for a UE
configured with CEModeA. TSI-EUTRA-M1-CEModeA includes the time to acquire the MIB and all the relevant SIBs of
the target cell.
- TPRACH is the interruption uncertainty in acquiring the first available PRACH occasion in the target cell. The
actual value of TPRACH shall depend upon the PRACH configuration used in the target cell and the PRACH
coverage enhancement level used by the UE for sending the random access to the target cell.
- Nfreq: It is the total number of frequencies to be monitored for RRC re-establishment; Nfreq = 1 if the target cell is
known.
There is no requirement if the target cell does not contain the UE context.
6.7.2.2 UE Re-establishment delay requirement for CEModeB
The UE re-establishment delay (TUE_re-establish_delay) is the time between the moments when any of the conditions
requiring RRC re-establishment as defined in clause 5.3.7 in TS 36.331 [2] is detected by the UE to the moment the UE
has transmitted all repetitions of PRACH preamble to the target cell. The UE re-establishment delay (TUE_re-establish_delay)
requirement for a UE configured with CEModeB shall be less than:
TUE-re-establish_delay = 50 ms + Nfreq*Tsearch + TSI-EUTRA-M1-CEModeB + TPRACH
- Tsearch is the time required by the UE to search the target cell. Tsearch =100 ms if the target cell is known by the
UE. Otherwise, Tsearch is specified in relevant intra-frequency cell identification requirements as described in
Clause 8.13.3.1 for a UE configured with CEModeB. Regardless of whether DRX is in use by the UE, Tsearch
shall still be based on non-DRX target cell search times.
In the above requirement, a cell is known if it has been meeting the relevant cell identification requirement for a
time duration equal to or longer than the time duration required for the cell identification. Otherwise, it is
unknown.
- TSI-EUTRA-M1-CEModeB: It is the time required for receiving all the relevant system information according to the
reception procedure and the RRC procedure delay of system information blocks defined in TS 36.331 [2] for the
target cell for a UE configured with CEModeA; TSI-EUTRA-M1-CEModeB includes the time to acquire the MIB and all
the relevant SIBs of the target cell.
- TPRACH is the interruption uncertainty in acquiring the first available PRACH occasion in the target cell. The
actual value of TPRACH shall depend upon the PRACH configuration used in the target cell and the PRACH
coverage enhancement level used by the UE for sending the random access to the target cell.
- Nfreq: It is the total number of frequencies to be monitored for RRC re-establishment; Nfreq = 1 if the target cell is
known.
There is no requirement if the target cell does not contain the UE context.
6.8 RRC Connection Release with Redirection for Cat-M1 UEs
6.8.1 Introduction
RRC connection release with redirection is initiated by the UE upon receiving the “RRCConnectionRelease” message
from the E-UTRAN, TS 36.331 [2]. The RRC connection release with redirection procedure is specified in clause 5.3.8
in TS 36.331 [2].
The requirements in this clause are applicable for UE caterory M1 capable of E-UTRA FDD, TDD or HD-FDD
operation.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 135 ETSI TS 136 133 V14.3.0 (2017-04)
6.8.2 Requirements
6.8.2.1 RRC connection release with redirection to E-UTRAN with CE Mode A
The UE shall be capable of performing the RRC connection release with redirection to the target E-UTRA cell within
Tconnection_release_redirect_E-UTRA cat-M1.
The time delay (Tconnection_release_redirect_E-UTRA cat-M1) is the time between the end of the last subframe in the repetition
period of PDSCH containing the IE, “RRCConnectionRelease” and the end of the last subframe in the repetition period
of the PRACH transmission to the target E-UTRA cell. The time delay (Tconnection_release_redirect_E-UTRA cat-M1) shall be less
than:
Tconnection_release_redirect_E-UTRA cat-M1 = TRRC_procedure_delay + Tidentify-E-UTRA cat-M1 + TSI-E-UTRA cat-M1 + TRA cat-M1
The target E-UTRA FDD or TDD cell shall be considered detectable for a category M1 UE capable of E-UTRA FDD
or TDD provided that:
- RSRP related side conditions given in Section 9.1.21.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band.
The target E-UTRA FDD cell shall be considered detectable for a category M1 UE capable of E-UTRA HD-FDD
provided that:
- RSRP related side conditions given in Section 9.1.21.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2 for a corresponding Band.
TRRC_procedure_delay: It is the RRC procedure for processing the received message “RRCConnectionRelease”. It shall be
less than 110 ms.
Tidentify-E-UTRA cat-M1: It is the time required to identify the target E-UTRA cell. It shall be less than 960 ms.
TSI-E-UTRA cat-M1: It is the time required for acquiring all the relevant system information (SI) of the target E-UTRA cell.
If old E-UTRA serving cell, before the release of the RRC connection, provides the UE with the SI (including MIB and
all relevant SIBs) of the target E-UTRA cell, then TSI-E-UTRA FDD = 0 ms. The value of TSI-E-UTRA cat-M1 depends on the
repetitions of PBCH and PDSCH used in the target cell.
TRA cat-M1: It is the delay caused due to the random access procedure when sending random access to the target E-UTRA
cell. The value of TRA depends on the PRACH configuration and the repetition used in the target cell.
6.9 RRC Connection Redirection to Non-anchor Carrier in NB-
IoT
6.9.1 Introduction
RRC connection redirection to a non-anchor carrier is initiated by the UE upon receiving the IE,
“CarrierConfigDedicated-NB”, from the E-UTRAN, TS 36.331 [2]. The RRC redirection to procedure is specified in
clause 6.7.3.2 in TS 36.331 [2].
6.9.2 Requirements
The UE shall be capable of performing the RRC connection redirection to the non-anchor carrier within
Tconnection_redirect_non-anchor.
The time delay (Tconnection_redirect_non-anchor) is the time between the end of the last subframe in the repetition period of
NPDSCH containing the IE, “CarrierConfigDedicated-NB” received on the anchor carrier and the end of the last
subframe in the repetition period of NPUSCH transmitted on the target non-anchor carrier. The time delay
(Tconnection_redirect_non-anchor) shall be less than:
Tconnection_redirect_non-anchor = TRRC_procedure_delay + Tperiod_DL_bitmap + TUL_grant + TDL-UL switch + TNPUSCH
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 136 ETSI TS 136 133 V14.3.0 (2017-04)
TRRC_procedure_delay: It is the RRC procedure for processing the received message “CarrierConfigDedicated-NB”. It shall
be less than 110 ms.
Tperiod_DL_bitmap: It is the periodicity of the downlink subframe configuration for downlink transmission on the non-anchor
carrier. It is configured via IE DL-Bitmap-NB [2] and can be 10 ms or 40 ms.
TUL_grant: It is the time required to acquire uplink grant from the non-anchor carrier for transmitting NPUSCH on the
non-anchor carrier. The value of TUL_grant depends on Tperiod_DL_bitmap and the number of repetitions of NPDCCH used in
the non-anchor carrier.
TDL-UL switch: It is the time between the end of the last subframe in the repetition period of NPDCCH received on the non-
anchor carrier and the start of the first subframe in the repetition period of the corresponding NPUSCH transmitted on
the non-anchor carrier. TDL-UL switch is 8 ms.
TNPUSCH: It is the time required to transmit NPUSCH on the non-anchor carrier. The value of TNPUSCH depends on the
number of repetitions of NPUSCH used in the non-anchor carrier.
7 Timing and signalling characteristics
7.1 UE transmit timing
7.1.1 Introduction
The UE shall have capability to follow the frame timing change of the connected eNode B. The uplink frame
transmission takes place ( N TA + N TA offset ) × Ts before the reception of the first detected path (in time) of the
corresponding downlink frame from the reference cell. The UE shall be configured with a pTAG containing the PCell.
The pTAG may also contain up to four SCells, if configured. The UE capable of supporting multiple timing advances
[2] may also be configured with one or two serving cells with uplink in one or two sTAG and pTAG.
The other downlink SCell(s), if configured, will be contained in either the pTAG or the sTAG(s). In pTAG, UE shall
use the PCell as the reference cell for deriving the UE transmit timing for cells in the pTAG. When the UE capable of
supporting multiple timing advance [2] is configured with one or two sTAG(s), the UE shall use an activated SCell
from the sTAG for deriving the UE transmit timing for cells in the sTAG. UE initial transmit timing accuracy,
maximum amount of timing change in one adjustment, minimum and maximum adjustment rate are defined in the
following requirements. The requirements in clause 7 apply to all TAGs.
The UE capable of supporting dual connectivity shall be configured with one pTAG and may also be configured with
one psTAG. The pTAG shall contain the PCell and may also contain one SCell, if configured. The psTAG shall contain
the PSCell and may also contain one SCell, if configured. In pTAG, UE shall use the PCell as the reference cell for
deriving the UE transmit timing for pTAG, and in psTAG, UE shall use the PSCell as the reference cell for deriving the
UE transmit timing for psTAG. UE initial transmit timing accuracy, maximum amount of timing change in one
adjustment, minimum and maximum adjustment rate are defined in the following requirements. The requirements in
clause 7 apply to both TAGs.
The UE supporting carrier aggregation with FS3 SCells shall be configured with one pTAG. The pTAG shall contain
the PCell and may also contain up to four FS3 SCells, if configured. In pTAG, UE shall use the PCell as the reference
cell for deriving the UE transmit timing for FS3 SCells. When the UE capable of supporting multiple timing advance
[2] is configured with one or two sTAG(s) with at least one FS3 SCell in which case the pTAG may or may not contain
any FS3 SCell, the UE shall use an activated SCell from the sTAG for deriving the UE transmit timing for cells in the
sTAG. If an sTAG contains at least one non-FS3 SCell, the UE shall use a non-FS3 SCell as the reference cell for
deriving the UE transmit timing for the cells in the sTAG. UE initial transmit timing accuracy, maximum amount of
timing change in one adjustment, minimum and maximum adjustment rate are defined in the following requirements.
The requirements in clause 7 apply to pTAG.
7.1.2 Requirements
The UE initial transmission timing error shall be less than or equal to ±Te where the timing error limit value Te is
specified in Table 7.1.2-1. This requirement applies when it is the first transmission in a DRX, eDRX_CONN cycle for
PUCCH, PUSCH and SRS or it is the first transmission after RACH-less handover or it is the PRACH transmission.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 137 ETSI TS 136 133 V14.3.0 (2017-04)
The reference point for the UE initial transmit timing control requirement shall be the downlink timing of the reference
cell minus ( N TA_Ref + N TA offset ) × Ts . The downlink timing is defined as the time when the first detected path (in time) of
the corresponding downlink frame is received from the reference cell. NTA_Ref for PRACH is defined as 0.
( N TA_Ref + N TA offset ) (in Ts units) for other channels is the difference between UE transmission timing and the Downlink
timing immediately after when the last timing advance in clause 7.3 was applied. NTA_Ref for other channels is not
changed until next timing advance is received.
Table 7.1.2-1: Te Timing Error Limit
Downlink Bandwidth (MHz) Te_
1.4 24*TS
≥3 12*TS
Note: TS is the basic timing unit defined in TS 36.211
When it is not the first transmission in a DRX or eDRX_CONN cycle or there is no DRX or no eDRX_CONN cycle,
and when it is the transmission for PUCCH, PUSCH and SRS transmission or it is not the first transmission after
RACH-less handover, the UE shall be capable of changing the transmission timing according to the received downlink
frame of the reference cell except when the timing advance in clause 7.3 is applied.
When in a TAG the transmission timing error between the UE and the reference timing exceeds ±Te, or in a sTAG the
UE changes the downlink SCell for deriving the UE transmit timing for cells in the sTAG configured with one or two
uplinks, the UE is required to adjust its timing to within ±Te in that TAG, as long as,
- the UE is configured with a pTAG and one or two sTAG, the transmission timing difference between TAGs does
not exceed the maximum transmission timing difference (i.e., 32.47us) after such adjustment, or
- the UE is configured with synchronous dual connectivity, the transmission timing difference between pTAG and
psTAG does not exceed the maximum transmission timing difference (i.e., 35.21us) after such adjustment.
If the transmission timing difference after such adjustment is bigger than the maximum transmission timing difference
UE may stop adjustment in this TAG. The reference timing shall be ( N TA_Ref + N TA offset ) × Ts before the downlink timing
of the reference cell. All adjustments made to the UE uplink timing under the above mentioned scenarios shall follow
these rules:
1) The maximum amount of the magnitude of the timing change in one adjustment shall be Tq seconds.
2) The minimum aggregate adjustment rate shall be 7*TS per second.
3) The maximum aggregate adjustment rate shall be Tq per 200ms.
where the maximum autonomous time adjustment step Tq is specified in Table 7.1.2-2.
Table 7.1.2-2: Tq Maximum Autonomous Time Adjustment Step
Downlink Bandwidth (MHz) Tq_
1.4 17.5*TS
3 9.5*TS
5 5.5*TS
≥10 3.5*TS
Note: TS is the basic timing unit defined in TS 36.211
7.2 UE timer accuracy
7.2.1 Introduction
UE timers are used in different protocol entities to control the UE behaviour.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 138 ETSI TS 136 133 V14.3.0 (2017-04)
7.2.2 Requirements
For UE timers specified in TS 36.331 [2], UE shall comply with the timer accuracies according to Table 7.2.2-1.
The requirements are only related to the actual timing measurements internally in the UE. They do not include the
following:
- Inaccuracy in the start and stop conditions of a timer (e.g. UE reaction time to detect that start and stop
conditions of a timer is fulfilled), or
- Inaccuracies due to restrictions in observability of start and stop conditions of a UE timer (e.g. TTI alignment
when UE sends messages at timer expiry).
Table 7.2.2-1
Timer value [s] Accuracy
timer value < 4 ± 0.1s
timer value ≥ 4 ± 2.5%
7.3 Timing Advance
7.3.1 Introduction
The timing advance is initiated from E-UTRAN with MAC message that implies and adjustment of the timing advance,
see TS 36.321 [17] clause 5.2.
7.3.2 Requirements
7.3.2.1 Timing Advance adjustment delay
UE shall adjust the timing of its uplink transmission timing at sub-frame n+6 for a timing advance command received in
sub-frame n. The same requirement applies also when the UE is not able to transmit a configured uplink transmission
due to the channel assessment procedure.
7.3.2.2 Timing Advance adjustment accuracy
The UE shall adjust the timing of its transmissions with a relative accuracy better than or equal to ±4* TS seconds to the
signalled timing advance value compared to the timing of preceding uplink transmission. The timing advance command
is expressed in multiples of 16* TS and is relative to the current uplink timing.
7.4 Cell phase synchronization accuracy (TDD)
7.4.1 Definition
Cell phase synchronization accuracy is defined as the maximum absolute deviation in frame start timing between any
pair of cells on the same frequency that have overlapping coverage areas.
7.4.2 Minimum requirements
For Wide Area BS, the cell phase synchronization accuracy measured at BS antenna connectors shall be better than the
requirement specified in table 7.4.2-1. If a cell’s coverage area overlaps with another cell with different cell radius then
the cell phase synchronization accuracy corresponding to the larger of the two cell sizes applies to the overlapping cells
with different radii.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 139 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.4.2-1 Cell phase synchronization requirement for wide area BS (TDD)
Cell Type Cell Radius Requirement
Small cell ≤ 3 km ≤ 3 μs
Large cell > 3 km ≤ 10 μs
For Home BS, the cell phase synchronization accuracy measured at BS antenna connectors shall be better than the
requirement specified in table 7.4.2-2.
Table 7.4.2-2 Cell phase synchronization requirement for Home BS (TDD)
Source Cell Type Propagation Distance Requirement
Small cell ≤ 500 m ≤ 3 μs
Large cell > 500 m ≤1.33 + Tpropagation μs
Note 1: Tpropagation is the propagation delay between the Home BS and the cell selected as the network listening
synchronization source. In terms of the network listening synchronization source selection, the best
accurate synchronization source to GNSS should be selected.
Note 2: If the Home BS obtains synchronization without using network listening, the small cell requirement
applies.
7.5 Synchronization Requirements for E-UTRAN to 1xRTT and
HRPD Handovers
7.5.1 Introduction
This clause contains the synchronization requirements for eNodeB capable of supporting E-UTRAN to CDMA 1xRTT
and HRPD handovers. To facilitate E-UTRAN to CDMA 1xRTT and HRPD handovers, the CDMA System Time
reference needs to be provided to the UE in order for the UE to report the pilot PN phases of the target 1xRTT or HRPD
cells. This is achieved through the SIB8 message broadcasted by the serving eNodeB:
If the eNodeB is synchronized to the GPS time and the LTE system frame is aligned with the start of CDMA
System Time, then the size of CDMA System Time information is 39 bits and the unit is 10 ms based on a
1.2288 Mcps chip rate.
If the eNodeB is not synchronized to the GPS time or if the eNodeB is synchronized to the GPS time but its LTE
system frame not aligned with the start of CDMA System time, then the size of CDMA System Time
information is 49 bits and the unit is 8 CDMA chips based on 1.2288 Mcps chip rate.
The CDMA system time reference provided by the serving eNodeB has to be within a certain level of accuracy in order
to facilitate accurate reporting of the pilot PN phases of the target 1xRTT or HRPD cells and enable reliable handover
to the 1xRTT or HRPD networks.
7.5.2 eNodeB Synchronization Requirements
7.5.2.1 Synchronized E-UTRAN
The eNodeB shall be synchronized to the GPS time. With external source of CDMA System Time disconnected, the
eNodeB shall maintain the timing accuracy within ±10 μs of CDMA System Time for a period of not less than 8 hours.
The timing deviation between the SFN boundary at or immediately after the ending boundary of the SI-window in
which SystemInformationBlockType8 is transmitted and the broadcasted CDMA System Time shall be within 10 μs.
7.5.2.2 Non-Synchronized E-UTRAN
The timing deviation between the SFN boundary at or immediately after the end of the boundary of the SI-window in
which SystemInformationBlockType8 is transmitted and the broadcasted CDMA System Time shall be within 10 μs.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 140 ETSI TS 136 133 V14.3.0 (2017-04)
With external source of CDMA System Time disconnected the SFN boundary at or immediately after the broadcasted
CDMA System Time in the SIB8 message shall maintain the timing accuracy within ±10 μs of CDMA System Time for
a period of not less than 8 hours.
7.6 Radio Link Monitoring
7.6.1 Introduction
The UE shall meet the radio link monitoring requirements specified for PSCell in section 7.6 provided that the UE is
configured with the parameters T313, N313 and N314 defined in [2].
The UE shall monitor the downlink link quality based on the cell-specific reference signal in order to detect the
downlink radio link quality of the PCell and PSCell as specified in [3].
The UE shall estimate the downlink radio link quality and compare it to the thresholds Qout and Qin for the purpose of
monitoring downlink radio link quality of the PCell and PSCell.
The threshold Qout is defined as the level at which the downlink radio link cannot be reliably received and shall
correspond to 10% block error rate of a hypothetical PDCCH transmission taking into account the PCFICH errors with
transmission parameters specified in Table 7.6.1-1.
The threshold Qin is defined as the level at which the downlink radio link quality can be significantly more reliably
received than at Qout and shall correspond to 2% block error rate of a hypothetical PDCCH transmission taking into
account the PCFICH errors with transmission parameters specified in Table 7.6.1-2.
When higher-layer signalling indicates certain subframes for restricted radio link monitoring, the radio link quality shall
be monitored as specified in [3].
The requirements in sections 7.6.2.1, 7.6.2.2 and 7.6.2.3 shall also apply when a time domain measurement resource
restriction pattern for performing radio link monitoring measurements is configured by higher layers (TS 36.331 [2]),
with or without CRS assistance information, provided that also the following additional condition is fulfilled:
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the radio link monitoring measurements,
When the CRS assistance information is provided, the transmission bandwidth [30] in all intra-frequency cells in
the CRS assistance information [2] is the same or larger than the transmission bandwidth of the PCell for which
radio link monitoring is performed.
When the CRS assistance information is provided, the requirements in Section 7.6 shall also be met when the number of
transmit antenna ports [16] of one or more cells whose CRS assistance information is provided [2] is different from the
number of transmit antenna ports of the cell for which radio link monitoring is performed.
NOTE: If the UE is not provided with the CRS assistance information (TS 36.331 [2]) or the CRS assistance data
is not valid throughout the entire evaluation period, then similar Release 8 and 9 requirements apply for
time domain measurements restriction under colliding CRS with ABS configured in non-MBSFN
subframes.
The UE capable of SRS carrier based switching when configured to perform SRS carrier based switching for
transmitting SRS and/or RACH over one or more SCells without PUSCH shall perform radio link monitoring and meet
the requirements defined in Section 7.6 provided the following condition is met:
- at least one downlink subframe is available for doing radio link monitoring at the UE in the PCell;
- at least one downlink subframe is available for doing radio link monitoring at the UE in the PSCell if the UE is
configured with PSCell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 141 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.6.1-1 PDCCH/PCFICH transmission parameters for out-of-sync
Attribute Value
DCI format 1A
Number of control OFDM symbols 2; Bandwidth ≥ 10 MHz
3; 3 MHz ≤ Bandwidth ≤ 10 MHz
4; Bandwidth = 1.4 MHz
Aggregation level (CCE) 4; Bandwidth = 1.4 MHz
8; Bandwidth ≥ 3 MHz
Ratio of PDCCH RE energy to 4 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell or PSCell.
1 dB: when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell or PSCell.
Ratio of PCFICH RE energy to 4 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell or PSCell.
1 dB: when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell or PSCell.
Note 1: DCI format 1A is defined in clause 5.3.3.1.3 in TS 36.212 [21].
Note 2: A hypothetical PCFICH transmission corresponding to the number of
control symbols shall be assumed.
Table 7.6.1-2 PDCCH/PCFICH transmission parameters for in-sync
Attribute Value
DCI format 1C
Number of control OFDM symbols 2; Bandwidth ≥ 10 MHz
3; 3 MHz ≤ Bandwidth ≤ 10 MHz
4; Bandwidth = 1.4 MHz
Aggregation level (CCE) 4
Ratio of PDCCH RE energy to 0 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell or PSCell.
-3 dB; when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell or PSCell.
Ratio of PCFICH RE energy to 4 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell or PSCell.
1 dB: when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell or PSCell.
Note 1: DCI format 1C is defined in clause 5.3.3.1.4 in TS 36.212 [21].
Note 2: A hypothetical PCFICH transmission corresponding to the number of
control symbols shall be assumed.
7.6.2 Requirements
7.6.2.1 Minimum requirement when no DRX is used
When the downlink radio link quality of the PCell or PSCell estimated over the last 200 ms period becomes worse than
the threshold Qout, Layer 1 of the UE shall send an out-of-sync indication for the PCell or PSCell to the higher layers
within 200 ms Qout evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as specified in
TS 36.331 [2].
When the downlink radio link quality of the PCell or PSCell estimated over the last 100 ms period becomes better than
the threshold Qin, Layer 1 of the UE shall send an in-sync indication for the PCell or PSCell to the higher layers within
100 ms Qin evaluation period. A L3 filter shall be applied to the in-sync indications as specified in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 142 ETSI TS 136 133 V14.3.0 (2017-04)
When the UE creates autonomous gaps for identification the CGI of an E-UTRA intra-frequency cell or an E-UTRA
inter-frequency cell and when higher-layer signalling indicates certain subframes for restricted radio link monitoring,
the UE shall also perform radio link monitoring. In this case, the Qout evaluation period (TEvaluate_Qout) is 200 ms, and the
Qin evaluation period (TEvaluate_Qin) is 100 ms Note 1.
Note 1: This RLM requirement does not need to be tested.
The out-of-sync and in-sync evaluations of the PCell or PSCell shall be performed as specified in clause 4.2.1 in [3].
Two successive indications from Layer 1 shall be separated by at least 10 ms.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer and the transmitter power
of PSCell if configured shall be turned off within 40 ms after expiry of T313 timer as specified in clause 5.3.11 in
TS 36.331 [2]. The UE shall not perform LBT procedure on any of FS3 SCell after the expiry of T310.
7.6.2.2 Minimum requirement when DRX is used
When DRX is used the Qout evaluation period (TEvaluate_Qout_DRX) and the Qin evaluation period (TEvaluate_Qin_DRX)
specified in Table 7.6.2.2-1 will be used.
When higher-layer signalling indicates certain subframes for restricted radio link monitoring, the Qout evaluation period
(TEvaluate_Qout_DRX) and the Qin evaluation period (TEvaluate_Qin_DRX) specified in Table 7.6.2.2-2 will be used.
When eDRX_CONN cycle is used, the Qout evaluation period (TEvaluate_Qout_DRX) and the Qin evaluation period
(TEvaluate_Qin_DRX) specified in Table 7.6.2.2-3 will be used.
When the UE creates autonomous gaps for identification the CGI of an E-UTRA intra-frequency cell or an E-UTRA
inter-frequency cell and when higher-layer signalling indicates certain subframes for restricted radio link monitoring,
the UE shall also perform radio link monitoring. In this case, the Qout evaluation period (TEvaluate_Qout_DRX) and the Qin
evaluation period (TEvaluate_Qin_DRX) specified in Table 7.6.2.2-2 will be used Note 1.
Note 1: This RLM requirement does not need to be tested.
When the downlink radio link quality of the PCell or PSCell estimated over the last TEvaluate_Qout_DRX [s] period becomes
worse than the threshold Qout, Layer 1 of the UE shall send out-of-sync indication for the PCell or PSCell to the higher
layers within TEvaluate_Qout_DRX [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as
specified in TS 36.331 [2].
When the downlink radio link quality of the PCell or PSCell estimated over the last TEvaluate_Qin_DRX [s] period becomes
better than the threshold Qin, Layer 1 of the UE shall send in-sync indications for the PCell or PSCell to the higher
layers within TEvaluate_Qin_DRX [s] evaluation period. A L3 filter shall be applied to the in-sync indications as specified in
TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell or PSCell shall be performed as specified in clause 4.2.1 in [3].
When DRX is used, two successive indications from Layer 1 shall be separated by at least max(10 ms,
DRX_cycle_length). When the UE is configured with dual connectivity, then two successive indications from Layer 1
shall be separated by at least max(10 ms, MCG_DRX_cycle_length) for PCell and by at least max(10 ms,
SCG_DRX_cycle_length) for PSCell. When eDRX_CONN is used, two successive indications from Layer 1 shall be
separated by at least max(10 ms, eDRX_CONN cycle length).
Upon start of T310 timer or T313 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link of
PCell or PSCell for recovery using the evaluation period and Layer 1 indication interval corresponding to the non-DRX
mode until the expiry or stop of T310 timer or T313 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer and the transmitter power
of PSCell if configured shall be turned off within 40 ms after expiry of T313 timer as specified in clause 5.3.11 in
TS 36.331 [2]. The UE shall not perform LBT procedure on any of FS3 SCells after the expiry of T310.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 143 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.6.2.2-1: Qout and Qin Evaluation Period in DRX
DRX cycle length (s) TEvaluate_Qout_DRX and
TEvaluate_Qin_DRX (s) (DRX cycles)
≤ 0.01 Non-DRX requirements in
clause 7.6.2.1 are applicable.
0.01 < DRX cycle ≤0.04 Note 1 (20)
0.04 < DRX cycle ≤ 0. 64 Note 1 (10)
0.64 < DRX cycle ≤ 2.56 Note 1 (5)
Note 1: Evaluation period length in time depends on the length of
the DRX cycle in use
Note 2: MCG’s DRX configuration is applied for PCell RLM
evaluation and SCG’s DRX configuration is applied for
PSCell RLM evaluation
Table 7.6.2.2-2: Qout and Qin Evaluation Period in DRX when higher-layer signalling restricted
measurement resource
DRX cycle length (s) TEvaluate_Qout_DRX and
TEvaluate_Qin_DRX (s) (DRX cycles)
≤ 0.01 Non-DRX requirements in
clause 7.6.2.1 are applicable.
0.01 < DRX cycle ≤0.04 Note 1 (40)
0.04 < DRX cycle ≤ 0. 16 Note 1 (20)
0. 16 < DRX cycle ≤ 0.64 Note 1 (10)
0.64 < DRX cycle ≤ 2.56 Note 1 (5)
Note 1: Evaluation period length in time depends on the length of
the DRX cycle in use
Note 2: MCG’s DRX configuration is applied for PCell RLM
evaluation and SCG’s DRX configuration is applied for
PSCell RLM evaluation
Table 7.6.2.2-3: Qout and Qin Evaluation Period when eDRX_CONN cycle is configured
eDRX_CONN cycle length TEvaluate_Qout_DRX and
[s] TEvaluate_Qin_DRX [s] (eDRX_CONN
cycles)
2.56 < eDRX_CONN cycle ≤ Note (5)
10.24
Note: Evaluation period length in time depends on the length of
the eDRX_CONN cycle in use
7.6.2.3 Minimum requirement at transitions
When the UE transitions between any two of DRX, eDRX_CONN and non-DRX or when DRX or eDRX_CONN cycle
periodicity changes, for a duration of time equal to the evaluation period corresponding to the second mode after the
transition occurs, the UE shall use an evaluation period that is no less than the minimum of evaluation periods
corresponding to the first mode and the second mode. Subsequent to this duration, the UE shall use an evaluation period
corresponding to the second mode. This requirement shall be applied to both out-of-sync evaluation and in-sync
evaluation of the PCell and PSCell.
7.6.2.4 Minimum requirement during SI Acquisition with autonomous gaps
For E-UTRAN FDD-UTRAN FDD measurements with autonomous gaps, for identification of the CGI of a UTRA
FDD cell (clause 8.1.2.4.17), the UE shall also perform radio link monitoring. In this case the out-of sync and in-sync
evaluation periods can be longer than those defined in sections 7.6.2.1-7.6.2.3.
For E-UTRAN TDD-UTRAN FDD measurements with autonomous gaps, for identification of the CGI of a UTRA
FDD cell (clause 8.1.2.4.18), the UE shall also perform radio link monitoring. In this case the out-of sync and in-sync
evaluation periods can be longer than those defined in sections 7.6.2.1-7.6.2.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 144 ETSI TS 136 133 V14.3.0 (2017-04)
7.6.2.5 Minimum requirement under IDC Interference
When the UE is provided with IDC solution, the UE shall also perform radio link monitoring and meet the
corresponding requirements in clause 7.6.2.
7.7 SCell Activation and Deactivation Delay for E-UTRA Carrier
Aggregation
7.7.1 Introduction
This section defines requirements for the delay within which the UE shall be able to activate a deactivated SCell and
deactive an activated SCell in E-UTRA carrier aggregation. The requirements are applicable to an E-UTRA carrier
aggregation capable UE which has been configured with up to four downlink SCells.
If multiple downlink SCells are activated or deactivated in the same MAC control element as defined in [17], the
requirements shall apply to each of the SCells in the MAC control element.
7.7.2 SCell Activation Delay Requirement for Deactivated SCell
The requirements in this section shall apply for the UE configured with one downlink SCell. The requirements in this
section are applicable for E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD carrier aggregation.
The delay within which the UE shall be able to activate the deactivated SCell depends upon the specified conditions.
Upon receiving SCell activation command in subframe n, the UE shall be capable to transmit valid CSI report and apply
actions related to the activation command as specified in [17] for the SCell being activated no later than in subframe
n+24 provided the following conditions are met for the SCell:
- During the period equal to max(5 measCycleSCell, 5 DRX cycles) before the reception of the SCell activation
command:
- the UE has sent a valid measurement report for the SCell being activated and
- the SCell being activated remains detectable according to the cell identification conditions specified in
section 8.3.3.2,
- SCell being activated also remains detectable during the SCell activation delay according to the cell
identification conditions specified in section 8.3.3.2.
Otherwise upon receiving the SCell activation command in subframe n, the UE shall be capable to transmit valid CSI
report and apply actions related to the activation command as specified in [17] for the SCell being activated no later
than in subframe n+34 provided the SCell can be successfully detected on the first attempt.
If there is no reference signal received for the CSI measurement over the delay corresponding to the minimum
requirements specified above, then the UE shall report corresponding valid CSI for the activated SCell on the next
available uplink reporting resource after receiving the reference signal.
The SCell activation delay specified in this section can be extended with each SRS carrier based switching to any
carrier occuring during the SCell activation procedure.
If there are no uplink resources for reporting the valid CSI in subframe n+24 or n+34 or uplink transmission is
interrupted due to SRS carrier based switching then the UE shall use the next available uplink resource for reporting the
corresponding valid CSI.
The valid CSI is based on the UE measurement and corresponds to any CQI value specified in [3] with the exception of
CQI index = 0 (out of range) provided:
- the conditions in section 7.7 are met over the entire SCell activation delay and
- the conditions for CQI reporting defined in Section 7.2.3 of [3] are met.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 145 ETSI TS 136 133 V14.3.0 (2017-04)
In addition to CSI reporting defined above, UE shall also apply other actions related to the activation command
specified in [17] for an SCell at the first opportunities for the corresponding actions once the SCell is activated.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+9
when PCell belongs to E-UTRA FDD.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+11
when PCell belongs to E-UTRA TDD.
Starting from the subframe specified in section 4.3 of [3] and until the UE has completed the SCell activation, the UE
shall report CQI index = 0 (out of range) if the UE has available uplink resources to report CQI for the SCell.
7.7.3 SCell Deactivation Delay Requirement for Activated SCell
The requirements in this section shall apply for the UE configured with one downlink SCell. The requirements in this
section are applicable for E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD carrier aggregation.
Upon receiving SCell deactivation command or upon expiry of the sCellDeactivationTimer in subframe n, the UE shall
accomplish the deactivation actions specified in [17] for the SCell being deactivated no later than in subframe n+8.
The SCell deactivation delay specified in this section can be extended with each SRS carrier based switching to any
carrier occuring during the SCell deactivation procedure.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+9
when PCell belongs to E-UTRA FDD.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+11
when PCell belongs to E-UTRA TDD.
7.7.4 SCell Activation Delay Requirement for Deactivated SCell with
Muliple Downlnk SCells
The requirements in this section shall apply for the UE configured with up to four downlink SCells. The requirements in
this section are applicable for E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD carrier aggregation.
While activating a SCell if the UE does not receive any command to activate, deactivate, configure or deconfigure any
other SCell during the SCell activation delay then the UE shall meet the SCell activation delay requirements specified
in section 7.7.2.
While activating a SCell if any other SCell is activated, deactivated, configured or deconfigured by the UE then the UE
shall meet the SCell activation delay requirements (Tactivate_total) according to the following expression:
N −1
Tactivate _ total = Tactivate _ basic + 5 × ∑ K i
i =1
Where:
Tactivate_total is the total time to activate a SCell and is expressed in subframes.
Tactivate_basic is the SCell activation delay specified in section 7.7.2;
Ki (0 ≤ Ki ≤ [3]) is the number of times the other ith SCell is activated, deactivated, configured or deconfigured while the
SCell is being activated.
N (2≤N≤4) is the maximum number of SCells supported by the UE.
While activating a SCell:
- The interruption on the PCell and/or on the activated SCell due to the SCell activation specified in section 7.8.2
shall not occur before subframe n+5 and not occur after subframe n+11 if:
- the PCell and/or the activated SCell being interrupted and the SCell being activated belong to E-UTRA TDD,
or
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 146 ETSI TS 136 133 V14.3.0 (2017-04)
- the activated SCell being interrupted and the SCell being activated belong to E-UTRA FDD and the PCell
belongs to E-UTRA TDD.
- Otherwise, the interruption on PCell and/or on the activated SCell due to the SCell activation specified in section
7.8.2 shall not occur before subframe n+5 and not occur after subframe n+9.
Starting from the subframe specified in section 4.3 of [3] and until the UE has completed the SCell activation, the UE
shall report CQI index = 0 (out of range) if the UE has available uplink resources to report CQI for an SCell.
7.7.5 SCell Deactivation Delay Requirement for Activated SCell with
Multiple Downlink SCells
The requirements in this section shall apply for the UE configured with up to four downlink SCells. The requirements in
this section are applicable for E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD carrier aggregation.
The UE shall deactivate a SCell and meet the SCell deactivation delay requirements specified in section 7.7.3 regardless
of whether any other SCell is activated, deactivated, configured or deconfigured or not by the UE during the SCell
deactivation delay.
While deactivating a SCell:
- The interruption on the PCell and/or on the activated SCell due to the SCell deactivation specified in section
7.8.2 shall not occur before subframe n+5 and not occur after subframe n+11 if:
- the PCell and/or the activated SCell being interrupted and the SCell being deactivated belong to E-UTRA
TDD or
- the activated SCell being interrupted and the SCell being deactivated belong to E-UTRA FDD and the PCell
belongs to E-UTRA TDD.
- Otherwise, the interruption on PCell and/or the activated SCell due to the SCell deactivation specified in section
7.8.2 shall not occur before subframe n+5 and not occur after subframe n+9.
7.7.6 SCell Activation Delay Requirement for Deactivated PUCCH SCell
The requirements in this section shall apply for the UE configured with one downlink SCell and when PUCCH is
configured for the SCell being activated.
If the UE has a valid TA for transmitting on an SCell then the UE shall be able to transmit valid CSI report and apply
actions related to the SCell activation command as specified in [17] for the SCell being activated on the PUCCH SCell
no later than in subframe n+Tactivate_basic:
Where:
- A TA is considered to be valid provided that the TimeAlignmentTimer [2] assocated with the TAG containing the
PUCCH SCell is running.
- Tactivate_basic is the SCell activation delay as defined in section 7.7.2.
If the UE does not have a valid TA for transmitting on an SCell then the UE shall be capable to perform downlink
actions related to the SCell activation command as specified in [17] for the SCell being activated on the PUCCH SCell
no later than in subframe n+Tactivate_basic and shall be capable to perform uplink actions related to the SCell activation
command as specified in [17] for the SCell being activated on the PUCCH SCell no later than in subframe
n+Tdelay_PUCCH SCell and shall transmit valid CSI report for the SCell being activated on the PUCCH SCell no later than in
subframe n+Tdelay_PUCCH SCell, where:
Tdelay_PUCCH SCell = Tactivate_basic + T1 + T2 + T3
Where:
- T1 is the delay uncertainty in acquiring the first available PRACH occasion in the PUCCH SCell. T1 is up to 25
subframes and the actual value of T1 shall depend upon the PRACH configuration used in the PUCCH SCell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 147 ETSI TS 136 133 V14.3.0 (2017-04)
- T2 is the delay for obtaining a valid TA command for the sTAG to which the SCell configured with PUCCH
belongs. T2 is up to 13 subframes.
- T3 is the delay for applying the received TA for upling transmission. T3 is 6 subframes.
The above delay requirement (Tdelay_PUCCH SCell) shall apply provided that:
- The UE has received a PDCCH order to initiate RA procedure on the PUCCH SCell within Tactivate_basic otherwise
additional delay to activate the SCell is expected; and
- The RA on PUCCH SCell is not interrupted by the RA on PCell otherwise additional delay to activate the SCell
is expected; and
- No SRS carrier based switching occurs during the SCell activation procedure otherwise the PUCCH SCell
activation delay (Tdelay_PUCCH SCell) can be extended.
The interruption on the PCell specified in section 7.8.2 shall meet all applicable requirements in clause 7.7.2.
7.7.7 SCell Activation Delay Requirement for Deactivated PUCCH SCell
with Multiple SCells
The requirements in this section shall apply for the UE configured with up to four downlink SCells and when PUCCH
is configured for the SCell being activated.
If the UE has a valid TA for transmitting on a PUCCH SCell then the UE shall be able to transmit valid CSI report and
apply actions related to the SCell activation command as specified in [17] for the SCell being activated on the PUCCH
SCell no later than in subframe n+ Tactivate_total:
Where:
- A TA is considered to be valid provided that the TimeAlignmentTimer [2] assocated with the TAG containing the
PUCCH SCell is running.
- Tactivate_total is the SCell activation delay as defined in section 7.7.4.
If the UE does not have a valid TA for transmitting on an SCell then the UE shall be capable to perform downlink
actions related to the SCell activation command as specified in [17] for the SCell being activated on the PUCCH SCell
no later than in subframe n+Tactivate_basic and shall be capable to perform uplink actions related to the SCell activation
command as specified in [17] for the SCell being activated on the PUCCH SCell no later than in subframe
n+Tdelay_PUCCH_multiple_SCells and shall transmit valid CSI report for the SCell being activated on the PUCCH SCell no later
than in subframe n+Tdelay_PUCCH_multiple_SCells, where:
Tdelay_PUCCH multiple_SCells = Tactivate_total + T1 + T2 + T3
Where:
- T1, T2 and T3 are defined in section 7.7.6
The above delay requirement (Tdelay_PUCCH _multiple_SCells) shall apply provided that:
- The UE has received a PDCCH order to initiate RA procedure on the PUCCH SCell within Tactivate_basic otherwise
additional delay to activate the SCell is expected; and
- The RA on PUCCH SCell is not interrupted by the RA on PCell otherwise additional delay to activate the SCell
is expected; and
- No SRS carrier based switching occurs during the SCell activation procedure otherwise the PUCH SCell
activation delay (Tdelay_PUCCH multiple_SCells) can be extended.
The interruption on the PCell and/or on the activated SCell specified in section 7.8.2 shall meet all applicable
requirements in clause 7.7.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 148 ETSI TS 136 133 V14.3.0 (2017-04)
7.7.8 SCell Deactivation Delay Requirement for Activated PUCCH SCell
The requirements in this section shall apply for the UE configured with one downlink SCell and when PUCCH is
configured for the SCell being activated.
The UE shall deactivate a SCell configured with PUCCH and meet the SCell deactivation delay requirements specified
in section 7.7.3.
The interruption on the PCell specified in section 7.8.2 shall meet all applicable requirements in clause 7.7.3.
7.7.9 SCell Deactivation Delay Requirement for Activated PUCCH SCell
with Multiple SCells
The requirements in this section shall apply for the UE configured with up to four downlink SCells and when PUCCH
is configured for the SCell being deactivated.
The UE shall deactivate a SCell configured with PUCCH and meet the SCell deactivation delay requirements specified
in section 7.7.5.
The interruption on the PCell and/or on the activated SCell specified in section 7.8.2 shall meet all applicable
requirements in clause 7.7.5.
7.7.10 SCell Activation Delay Requirement for Deactivated SCell under
Frame Structure 3
The requirements in this section shall apply for E-UTRA carrier aggregation of one FDD PCell or one TDD PCell and
one SCell following the frame structure type 3 [16].
The delay within which the UE shall be able to activate the deactivated SCell depends upon the specified conditions.
Upon receiving SCell activation command in subframe n, the UE shall be capable to transmit valid CSI report and apply
actions related to the activation command as specified in [17] for the SCell being activated no later than in subframe
n+Tactivate_basic_FS3, provided the following conditions are met for the SCell:
- During the period equal to max(5 measCycleSCell, 5 DRX cycles) before the reception of the SCell activation
command:
- the UE has sent a valid measurement report for the SCell being activated and
- the SCell being activated remains detectable according to the cell identification conditions specified in
section 8.3.3.2,
- SCell being activated also remains detectable during the SCell activation delay according to the cell
identification conditions specified in section 8.3.3.2.
Tactivate_basic_FS3 = 16 ms + TDMTC_duration + (L+2) * TDMTC_periodicity, where
TDMTC_duration =6 ms is the DMTC duration [2],
TDMTC_periodicity is the periodicity of the DMTC [2],
L is the number of times the discovery signal occasion is not available at the UE during the SCell activation time.
Otherwise upon receiving the SCell activation command in subframe n, the UE shall be capable to transmit a valid CSI
report and apply actions related to the activation command as specified in [17] for the SCell being activated no later
than in subframe n+Tactivate_basic_FS3, provided the SCell can be successfully detected on the first attempt. In this case,
Tactivate_basic_FS3 is defined as follows.
Tactivate_basic_FS3 = 16 ms + TDMTC_duration + (L+3) * TDMTC_periodicity, where
TDMTC_duration = 6 ms is the DMTC duration [2],
TDMTC_periodicity is the periodicity of the DMTC [2],
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 149 ETSI TS 136 133 V14.3.0 (2017-04)
L is the number of times the discovery signal occasion is not available at the UE during the SCell activation time.
If there is no reference signal received for the CSI measurement over the delay corresponding to the minimum
requirements specified above, then the UE shall report corresponding valid CSI for the activated SCell on the next
available uplink reporting resource after receiving the reference signal.
If there are no uplink resources for reporting the valid CSI in subframe n+ Tactivate_basic_FS3 then the UE shall use the
next available uplink resource for reporting the corresponding valid CSI.
The valid CSI is based on the UE measurement and corresponds to any CQI value specified in [3] with the exception of
CQI index = 0 (out of range) provided:
- the conditions in section 7.7 are met over the entire SCell activation delay and
- the conditions for CQI reporting defined in Section 7.2.3 of [3] are met.
In addition to CSI reporting defined above, UE shall also apply other actions related to the activation command
specified in [17] for an SCell at the first opportunities for the corresponding actions once the SCell is activated.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+9
when PCell belongs to E-UTRA FDD.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+11
when PCell belongs to E-UTRA TDD.
Starting from the subframe specified in Section 4.3 of [3] and until the UE has completed the SCell activation, the UE
shall send CSI with CQI index = 0 (out of range) if the UE has available uplink resources to report for the SCell.
7.7.11 SCell Deactivation Delay Requirement for Activated SCell under
Frame Structure 3
The requirements in this section shall apply for the UE configured with one downlink SCell. The requirements in this
section shall apply for E-UTRA carrier aggregation of one FDD PCell or one TDD PCell and the SCell following the
frame structure type 3 [16].
Upon receiving SCell deactivation command or upon expiry of the sCellDeactivationTimer in subframe n, the UE shall
accomplish the deactivation actions specified in [17] for the SCell being deactivated no later than in subframe n+8.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+9
when PCell belongs to E-UTRA FDD.
The PCell interruption specified in section 7.8.2 shall not occur before subframe n+5 and not occur after subframe n+11
when PCell belongs to E-UTRA TDD.
7.7.12 SCell Activation Delay Requirement for Deactivated SCell with
Multiple Downlink SCells under Frame Structure 3
The requirements in this section shall apply for the UE configured with two or three downlink SCells. The requirements
in this section shall apply for E-UTRA carrier aggregation of one FDD PCell or one TDD PCell and all the SCells
following the frame structure type 3 [16].
While activating a SCell, if any other SCell is activated, deactivated, configured or deconfigured by the UE, the UE
shall meet the SCell activation delay requirements (Tactivate_total_FS3) according to the following expression:
N −1
Tactivate _ total _ FS 3 = Tactivate _ basic _ FS 3 + TDMTC _ periodicity × ∑ K i
i =1
where
Tactivate_total_FS3 is the total time to activate a SCell and is expressed in subframes,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 150 ETSI TS 136 133 V14.3.0 (2017-04)
Tactivate_basic_FS3_ is the SCell activation delay for the SCell, as specified in section 7.7.10,
TDMTC_periodicity is the periodicity of the DMTC [2],
Ki (0 ≤ Ki ≤ [3]) is the number of times the other ith SCell is activated, deactivated, configured or deconfigured while the
SCell is being activated,
N (2≤N≤3) is the maximum number of SCells supported by the UE.
While activating a SCell:
- The interruption on the PCell and/or on the activated SCell specified in section 7.8.2 shall not occur before
subframe n+5 and not occur after subframe n+9 when PCell belongs to E-UTRA FDD.
- The interruption on the PCell and/or on the activated SCell specified in section 7.8.2 shall not occur before
subframe n+5 and not occur after subframe n+11 when PCell belongs to E-UTRA TDD.
Starting from the subframe specified in section 4.3 of [3] and until the UE has completed the SCell activation, the UE
shall send CSI with CQI index = 0 (out of range) if the UE has available uplink resources to report for the SCell being
activated.
7.7.13 SCell Deactivation Delay Requirement for Activated SCell with
Multiple Downlink SCells under Frame Structure 3
The requirements in this section shall apply for the UE configured with two or three downlink SCells. The requirements
in this section shall apply for E-UTRA carrier aggregation of one FDD PCell or one TDD PCell and all the SCells
following the frame structure type 3 [16].
The UE shall deactivate a SCell and meet the SCell deactivation delay requirements specified in section 7.7.11
regardless of whether any other SCell is activated, deactivated, configured or deconfigured or not by the UE during the
SCell deactivation delay.
While deactivating a SCell:
- The interruption on the PCell and/or on the activated SCell specified in section 7.8.2 shall not occur before
subframe n+5 and not occur after subframe n+9 when PCell belongs to E-UTRA FDD.
- The interruption on the PCell and/or on the activated SCell specified in section 7.8.2 shall not occur before
subframe n+5 and not occur after subframe n+11 when PCell belongs to E-UTRA TDD.
7.8 Interruptions with Carrier Aggregation
7.8.1 Introduction
This section contains the requirements related to the interruptions on PCell and activated SCell if configured, when up
to four SCells are configured, deconfigured, activated or deactivated, or when SRS carrier based switching is performed
between the configured component carriers. Unless explicitly stated otherwise, the requirements in Section 7.8 shall
apply for:
- E-UTRA FDD CA,
- E-UTRA TDD CA,
- E-UTRA TDD-FDD CA,
- inter-band CA where PCell is FDD or TDD and all the SCells are following the frame structure type 3 [16].
Note: interruptions at SCell addition/release, activation/deactivation and during measurements on SCC may not
be required by all UEs.
Note: interruptions during SRS carrier based switching between the configured component carriers may not be
required by all UEs.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 151 ETSI TS 136 133 V14.3.0 (2017-04)
Editor’s Note: The interruptions shall not interrupt RRC signalling or ACK/NACKs related to RRC reconfiguration
procedure [2] for SCell addition/release or MAC control signalling [17] for SCell activation/deactivation
command. How to specify this is FFS.
7.8.2 Requirements
7.8.2.1 Interruptions at SCell addition/release for intra-band CA
When an intra-band SCell is added or released as defined in [2] the UE is allowed an interruption of up to 5 subframes
on PCell during the RRC reconfiguration procedure [2]. This interruption is for both uplink and downlink of PCell.
7.8.2.2 Interruptions at SCell addition/release for inter-band CA
When an inter-band SCell is added or released as defined in [2] the UE that requires interruption is allowed an
interruption of up to 1 subframe on PCell during the RRC reconfiguration procedure [2]. This interruption is for both
uplink and downlink of PCell.
7.8.2.3 Interruptions at SCell activation/deactivation for intra-band CA
When an intra-band SCell is activated or deactivated as defined in [17] the UE is allowed an interruption of up to 5
subframes on PCell during the activation/deactivation delay defined in Section 7.7. This interruption is for both uplink
and downlink of PCell.
7.8.2.4 Interruptions at SCell activation/deactivation for inter-band CA
When an inter-band SCell is activated or deactivated as defined in [17] the UE that requires interruption is allowed an
interruption of up to 1 subframe on PCell during the activation/deactivation delay defined in Section 7.7. This
interruption is for both uplink and downlink of PCell.
7.8.2.5 Interruptions during measurements on SCC for intra-band CA
PCell interruptions due to measurements on SCC when the SCell is deactivated are allowed with up to 0.5% probability
of missed ACK/NACK when the configured measCycleSCell [2] is 640 ms or longer.
If indicated by the network using IE allowInterruptions [2], PCell interruptions due to measurements on SCC when the
SCell is deactivated are allowed with up to 0.5% probability of missed ACK/NACK regardless of the configured
measCycleSCell [2].
Each interruption shall not exceed 5 subframes.
7.8.2.6 Interruptions during measurements on SCC for inter-band CA
PCell interruptions due to measurements on SCC when the SCell is deactivated are allowed with up to 0.5% probability
of missed ACK/NACK when the configured measCycleSCell [2] is 640 ms or longer.
If indicated by the network using IE allowInterruptions [2], PCell interruptions due to measurements on SCC when the
SCell is deactivated are allowed with up to 0.5% probability of missed ACK/NACK regardless of the configured
measCycleSCell [2].
Each interruption shall not exceed 1 subframe.
7.8.2.7 Interruptions at SCell addition/release with multiple downlink SCells
When any number of SCells between one and four is added or released using the same RRCConnectionReconfiguration
message as defined in [2], the UE is allowed an interruption on PCell and on any activated SCell during the RRC
reconfiguration procedure as follows:
- an interruption on PCell:
- of up to 1 subframe, if the PCell is not in the same band as any of the SCells being added or released, or
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 152 ETSI TS 136 133 V14.3.0 (2017-04)
- of up to 5 subframes, if the PCell is in the same band as any of the SCells being added or released;
- an interruption on any activated SCell:
- of up to 1 subframe, if the activated SCell is not in the same band as any of the SCells being added or
released, or
- of up to 5 subframes, if the activated SCell is in the same band as any of the SCells being added or released.
7.8.2.8 Interruptions at SCell activation/deactivation with multiple downlink SCells
When any number of SCells between one and four is activated or deactivated using the same MAC control element as
defined in [17], the UE is allowed an interruption on PCell and on any activated SCell during the SCell
activation/deactivation procedure [17] as follows:
- an interruption on PCell:
- of up to 1 subframe, if the PCell is not in the same band as any of the SCells being activated or deactivated,
or
- of up to 5 subframes, if the PCell is in the same band as any of the SCells being activated or deactivated;
- an interruption on any activated SCell:
- of up to 1 subframe, if the activated SCell is not in the same band as any of the SCells being activated or
deactivated, or
- of up to 5 subframes, if the activated SCell is in the same band as any of the SCells being activated or
deactivated.
7.8.2.9 Interruptions during measurements on SCC with multiple downlink SCells
If one SCell is deactivated, the UE is allowed due to measurements on the SCC with deactivated SCell:
- an interruption on PCell with up to 0.5% probability of missed ACK/NACK when the configured
measCycleSCell [2] for the deactivated SCell is 640 ms or longer.
- an interruption on PCell with up to 0.5% probability of missed ACK/NACK regardless of the configured
measCycleSCell [2] for the deactivated SCell if indicated by the network using IE allowInterruptions [2],
Each interruption shall not exceed:
- 1 subframes if the PCell is not in the same band as the deactivated SCell
- 5 subframes if the PCell is in the same band as the deactivated SCell
- an interruption on any activated SCell with up to 0.5% probability of missed ACK/NACK when the configured
measCycleSCell [2] for the deactivated SCell is 640 ms or longer .
- an interruption on any activated SCell with up to 0.5% probability of missed ACK/NACK regardless of the
configured measCycleSCell [2] for the deactivated SCell if indicated by the network using IE allowInterruptions
[2].
Each interruption shall not exceed:
- 1 subframes if the activated SCell is not in the same band as the deactivated SCell
- 5 subframes if the activated SCell is in the same band as the deactivated SCell
If two, three, or four SCells are deactivated, the UE is allowed due to measurements on the SCCs with deactivated
SCells:
- an interruption on PCell with up to 0.5% probability of missed ACK/NACK when any of the configured
measCycleSCell [2] for the deactivated SCells is 640 ms or longer.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 153 ETSI TS 136 133 V14.3.0 (2017-04)
- an interruption on PCell with up to 0.5% probability of missed ACK/NACK regardless of the configured
measCycleSCell [2] for the deactivated SCells if indicated by the network using IE allowInterruptions [2].
- an interruption on an activated SCell with up to 0.5% probability of missed ACK/NACK when any of the
configured measCycleSCell [2] for the deactivated SCells is 640 ms or longer.
- an interruption on an activated SCell with up to 0.5% probability of missed ACK/NACK regardless of the
configured measCycleSCell [2] for the deactivated SCells if indicated by the network using IE
allowInterruptions [2].
Each interruption on the PCell shall not exceed:
- 1 subframes if the PCell is not in the same band as any of the deactivated SCells
- 5 subframes if the PCell is in the same band as any of the deactivated SCells
Each interruption on the activated Cell shall not exceed:
- 1 subframe if the activated SCell is not in the same band as any of the deactivated SCells
- 5 subframes if the the activated SCell is in the same band as any of the deactivated SCells
7.8.2.10 Interruptions at overlapping addition/release/activation/deactivation of SCells
If a UE is commanded by the network to sequentially add/release/activate/deactivate SCells, and a new procedure of
addition/release/activation/deactivation of SCell(s) takes place before the completion of previous procedure of
addition/release/activation/deactivation of SCell(s), the interruptions on PCell due to sequential
addition/release/activation/deactivation of SCells shall not exceed the sum of the allowed interruptions on the PCell
caused by each of the addition/release/activation/deactivation procedures, and the interruptions on already activated
SCell due to sequential addition/release/activation/deactivation of SCells shall not exceed the sum of the allowed
interruptions on the SCell caused by each of the addition/release/activation/deactivation procedures, as defined in above
sections.
7.8.2.11 Interruptions during RSSI measurements on one SCC under Frame
Structure 3
The requirements in this section apply for inter-band CA where PCell belongs to FDD or TDD and all the configured
SCells belong to the frame structure type 3 [16], and the UE is configured with one SCell.
PCell interruptions due to RSSI measurements on SCC when the SCell is deactivated are allowed with up to 0.5%
probability of missed ACK/NACK when any of the configured rmtc-Period [2] and measCycleSCell [2] is 640 ms or
longer.
Each allowed interruption on the PCell shall not exceed 1 subframe.
7.8.2.12 Interruptions during RSSI measurements on multiple SCCs under Frame
Structure 3
The requirements in this section apply for inter-band CA where PCell belongs to FDD or TDD and all the configured
SCells belong to the frame structure type 3 [16], and the UE is configured with up to four SCells.
If one SCell is deactivated,
- the UE is allowed due to RSSI measurements on the SCC with deactivated SCell:
- an interruption on PCell with up to 0.5% probability of missed ACK/NACK when any of the configured rmtc-
Period [2] and the configured measCycleSCell [2] for the deactivated SCell is 640 ms or longer,
- an interruption on any activated SCell with up to 0.5% probability of missed ACK/NACK when any of the
configured rmtc-Period [2] and the configured measCycleSCell [2] for the deactivated SCell is 640 ms or longer.
- no interruption is allowed if both of the configured rmtc-Period [2] and the configured measCycleSCell [2] for the
deactivated SCell are below 640 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 154 ETSI TS 136 133 V14.3.0 (2017-04)
If two, three, or four SCells are deactivated,
- the UE is allowed due to RSSI measurements on the SCCs with deactivated SCells:
- an interruption on PCell with up to 0.5% probability of missed ACK/NACK when:
any of the configured rmtc-Period [2] and the configured measCycleSCell [2] for the deactivated SCells is 640
ms or longer, or
RSSI windows with the length of measDuration [2] for at least some of the SCCs with the deactivated SCells
within their respective rmtc-Period [2] are not within [20] ms;
- an interruption on an activated SCell with up to 0.5% probability of missed ACK/NACK when:
any of the configured rmtc-Period [2] and the configured and the configured measCycleSCell [2] for the
deactivated SCells is 640 ms or longer, or
RSSI windows with the length of measDuration [2] for at least some of the SCCs with the deactivated SCells
within their respective rmtc-Period [2] are not within [20] ms.
- no interruption is allowed if both of the configured rmtc-Period [2] and the configured measCycleSCell [2] for the
deactivated SCell are below 640 ms and RSSI windows with the length of measDuration [2] for all the SCCs with the
deactivated SCells within their respective rmtc-Period [2] are within [20] ms.
Each allowed interruption shall not exceed:
- 1 subframe on the PCell, and
- 5 subframes on the activated SCell.
7.8.2.13 Interruptions at SRS carrier based switching
A PUSCH-less SCC is a TDD SCC without PUCCH/PUSCH configured. When a UE needs to transmit periodic or
aperiodic SRS [16] and/or non-contention based PRACH on a PUSCH-less SCC, the UE can perform carrier based
switching to one or more PUSCH-less SCCs from a CC with PUSCH or from another PUSCH-less SCC prior to
transmitting SRS and/or PRACH, [provided that:
- switching is from a configured CC to another activated TDD CC;
- the PUSCH-less SCCs to which SRS carrier based switching is performed is indicated by DCI SRS request field
for aperiodic SRS transmission or configured via RRC [2] for periodic SRS transmission or indicated by
PDCCH for PRACH;
- the CC from which SRS carrier based switching is performed is indicated by IdexSwitchingFromCarrierlist [2];
- the SRS switching is not colliding with any other transmission with higher priority defined in [3];
- the SRS switching is not colliding with PDCCH in subframe 0 and 5 as specified in [3];
- for UE, which does not support simultaneous reception and transmission for inter-band TDD CA specified in TS
36.331 [2], and is compliant to the requirements for inter-band CA with uplink in one E-UTRA band and without
simultaneous Rx/Tx specified in TS 36.101 [5], the SRS or RACH transmission are not simultaneously
scheduled with DL subframe #0 or DL subframe #5 on other CCs.
The UE shall not perform SRS carrier based switching if the above conditions cannot be met.
The interruption on PCC and each of the activated SCCs during the switching to the PUSCH-less SCC shall not exceed
2 subframes including the first subframe where SRS transmission is configured on the PUSCH-less SCC.
The interruption on PCC and each of the activated SCCs during the switching from the PUSCH-less SCC shall not
exceed 2 subframes including the last subframe where SRS transmission is configured on the PUSCH-less SCC.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 155 ETSI TS 136 133 V14.3.0 (2017-04)
7.9 Maximum Transmission Timing Difference in Carrier
Aggregation
7.9.1 Introduction
A UE shall be capable of handling a relative received time difference between the PCell and SCell to be aggregated in
inter-band CA and intra-band non-contiguous CA.
7.9.2 Minimum Requirements for Interband Carrier Aggregation
The UE shall be capable of handling at least a relative received time difference between the signals received from the
PCell and the SCell at the UE receiver of up to 30.26 µs when one SCell is configured.
When two, three, or four SCells are configured, the UE shall be capable of handling at least a relative propagation delay
difference between the signals received from any pair of the serving cells (PCell and the SCells) at the UE receiver of
up to 30.26 µs.
The UE shall be capable of handling a maximum uplink transmission timing difference between the pTAG and the
sTAG of at least 32.47µs provided that the UE is:
- configured with inter-band CA and
- configured with the pTAG and the sTAG,
A UE configured with pTAG and sTAG may stop transmitting on the SCell if after timing adjusting due to received TA
command the uplink transmission timing difference between PCell and SCell exceeds the maximum value the UE can
handle as specified above.
The UE shall be capable of handling a maximum uplink transmission timing difference between the pTAG and any of
the two sTAGs or between the two sTAGs of at least 32.47µs provided that the UE is:
- configured with inter-band CA and
- configured with the two sTAGs,
A UE configured with two sTAGs may stop transmitting on the SCell if after timing adjusting due to received TA
command the uplink transmission timing difference between SCell in one sTAG and SCell in other sTAG exceeds the
maximum value the UE can handle as specified above.
7.9.3 Minimum Requirements for Intraband non-contiguous Carrier
Aggregation
The UE shall be capable of handling at least a relative received time difference between the signals received from the
PCell and the SCell at the UE receiver of up to 30.26 µs.
The UE shall be capable of handling a maximum uplink transmission timing difference between the pTAG and the
sTAG of at least 32.47µs provided that the UE is:
- configured with intra-band non-contiguous CA and
- configured with the pTAG and the sTAG,
A UE configured with pTAG and sTAG may stop transmitting on the SCell if after timing adjusting due to received TA
command the uplink transmission timing difference between PCell and SCell exceeds the maximum value the UE can
handle as specified above.
7.9.4 Minimum Requirements for Inter-Band Carrier Aggregation under
Frame Structure 3
The requirements in this section shall apply for E-UTRA inter-band carrier aggregation of one FDD PCell or one TDD
PCell and the SCell(s) following the frame structure type 3 [16].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 156 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall be capable of handling at least a relative received time difference between the signals received from the
PCell and the SCell at the UE receiver of up to 30.26 µs when one SCell is configured.
When two or three SCells are configured, the UE shall be capable of handling at least a relative propagation delay
difference between the signals received from any pair of the serving cells (PCell and the SCells) at the UE receiver of
up to 30.26 µs.
7.10 Interruptions with RSTD Measurements with Carrier
Aggregation
7.10.1 Introduction
This section contains the requirements related to the interruptions on PCell and activated SCell if configured, when
performing RSTD measurements on cells belonging to at least one SCC with deactivated SCell.
Note: Interruptions during RSTD measurements on PCell and activated SCell if configured may not be required by
all UEs.
7.10.2 Requirements
When common DRX is used, no interruption is allowed for all carrier aggregation configurations while the On Duration
timer is running.
The interruption requirement considers only missed ACK/NACK due to reconfiguration of the receiver bandwidth, and
not due to other causes such as RF impairments or channel conditions.
7.10.2.1 Interruptions during RSTD measurements on SCC for intra-band CA with
one downlink SCell
PCell interruptions due to RSTD measurements on SCC when the SCell is deactivated are allowed with up to 0.5%
probability of missed ACK/NACK when the the PRS periodicity
TPRS is 640 ms or longer. Each interruption shall not
exceed 5 subframes.
7.10.2.2 Interruptions during RSTD measurements on SCC for inter-band CA with
one downlink SCell
PCell interruptions due to RSTD measurements on SCC when the SCell is deactivated are allowed with up to 0.5%
probability of missed ACK/NACK when the PRS periodicity
TPRS is 640 ms or longer. Each interruption shall not
exceed 1 subframe.
7.10.2.3 Interruptions during RSTD measurements on SCC with multiple downlink
SCells
If one SCell is activated and the other SCell is deactivated, then due to RSTD measurements on the SCC with
deactivated SCell the UE is allowed:
● an interruption on PCell with up to 0.5% probability of missed ACK/NACK when when the PRS periodicity
TPRS
is 640 ms or longer. Each interruption shall not exceed:
○ 1 subframe if the PCell is not in the same band as the deactivated SCell
○ 5 subframes if the PCell is in the same band as the deactivated SCell
● an interruption on the activated SCell with up to 0.5% probability of missed ACK/NACK when the PRS
TPRS
periodicity is 640 ms or longer. Each interruption shall not exceed:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 157 ETSI TS 136 133 V14.3.0 (2017-04)
○ 1 subframe if the activated SCell is not in the same band as the deactivated SCell
○ 5 subframes if the activated SCell is in the same band as the deactivated SCell
If both SCells are deactivated, then due to RSTD measurements on one or both SCCs with deactivated SCells the UE is
allowed:
● an interruption on PCell with up to 1.0% probability of missed ACK/NACK when the configure PRS
TPRS
periodicity is 640 ms or longer in any of the SCCs. Each interruption shall not exceed:
○ 1 subframe if the PCell is not in the same band as any of the deactivated SCells
○ 5 subframes if the PCell is in the same band as any of the deactivated SCells
7.10.2.4 Interruptions at overlapping RSTD and inter-frequency measurements
If the UE is configured for RSTD measurements on cells belonging to a SCC with deactivated SCell(s) and also with a
measCycleSCell for performing E-UTRA carrier aggregation measurements as defined in Section 8.3 on the same SCC
as configured for the RSTD measurements, then the total allowed interruption on the active serving cell(s) is the
maximum of the interruption due to E-UTRA carrier aggregation measurements specified in Section 7. 8 and the
interruption due to the RSTD measurements on SCC specified in this Section.
7.11 Radio Link Monitoring for UE Category 0
7.11.1 Introduction
The UE category 0 applicability of the requirements for performing radio link monitoring in subclause 7.11 is defined in
Section 3.6.1.
The UE shall monitor the downlink link quality based on the cell-specific reference signal in order to detect the
downlink radio link quality of the PCell as specified in [3].
The UE shall estimate the downlink radio link quality and compare it to the thresholds Qout_Cat0 and Qin_Cat0 for the
purpose of monitoring downlink radio link quality of the PCell.
The threshold Qout_Cat0 is defined as the level at which the downlink radio link cannot be reliably received and shall
correspond to 10% block error rate of a hypothetical PDCCH transmission taking into account the PCFICH errors with
transmission parameters specified in Table 7.11.1-1.
The threshold Qin_Cat0 is defined as the level at which the downlink radio link quality can be significantly more reliably
received than at Qout_Cat0 and shall correspond to 2% block error rate of a hypothetical PDCCH transmission taking into
account the PCFICH errors with transmission parameters specified in Table 7.11.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 158 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.11.1-1 PDCCH/PCFICH transmission parameters for out-of-sync for UE category 0
Attribute Value
DCI format 1A
Number of control OFDM symbols 2; Bandwidth ≥ 10 MHz
3; 3 MHz ≤ Bandwidth < 10 MHz
4; Bandwidth = 1.4 MHz
Aggregation level (CCE) 4; Bandwidth = 1.4 MHz
8; Bandwidth ≥ 3 MHz
Ratio of PDCCH RE energy to 4 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell.
4 dB: when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell.
Ratio of PCFICH RE energy to 4 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell.
1 dB: when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell.
Note 1: DCI format 1A is defined in clause 5.3.3.1.3 in TS 36.212 [21].
Note 2: A hypothetical PCFICH transmission corresponding to the number of
control symbols shall be assumed.
Table 7.11.1-2 PDCCH/PCFICH transmission parameters for in-sync for UE category 0
Attribute Value
DCI format 1C
Number of control OFDM symbols 2; Bandwidth ≥ 10 MHz
3; 3 MHz ≤ Bandwidth < 10 MHz
4; Bandwidth = 1.4 MHz
Aggregation level (CCE) 4
Ratio of PDCCH RE energy to 1 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell.
1 dB; when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell.
Ratio of PCFICH RE energy to 4 dB; when single antenna port is used for cell-
average RS RE energy specific reference signal transmission by the
PCell.
1 dB: when two or four antenna ports are used
for cell-specific reference signal transmission by
the PCell.
Note 1: DCI format 1C is defined in clause 5.3.3.1.4 in TS 36.212 [21].
Note 2: A hypothetical PCFICH transmission corresponding to the number of
control symbols shall be assumed.
7.11.2 Requirements for FD-FDD and TDD
7.11.2.1 Minimum requirement when no DRX is used
When the downlink radio link quality of the PCell estimated over the last 200 ms period becomes worse than the
threshold Qout_Cat0, Layer 1 of the UE shall send an out-of-sync indication for the PCell to the higher layers within
200ms Qout_Cat0 evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as specified in
TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last 100 ms period becomes better than the
threshold Qin_Cat0, Layer 1 of the UE shall send an in-sync indication for the PCell to the higher layers within 100 ms
Qin_Cat0 evaluation period. A L3 filter shall be applied to the in-sync indications as specified in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 159 ETSI TS 136 133 V14.3.0 (2017-04)
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. Two
successive indications from Layer 1 shall be separated by at least 10ms.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
7.11.2.2 Minimum requirement when DRX is used
When DRX is used for FD-FDD and TDD category 0 UEs, the Qout_Cat0 evaluation period (TEvaluate_Qout_DRX_Cat0) and the
Qin_Cat0 evaluation period (TEvaluate_Qin_DRX_Cat0) specified in Table 7.11.2.2-1 will be used.
When eDRX_CONN is used for FD-FDD and TDD category 0 UEs, the Qout_Cat0 evaluation period
(TEvaluate_Qout_DRX_Cat0) and the Qin_Cat0 evaluation period (TEvaluate_Qin_DRX_Cat0) specified in Table 7.11.2.2-2 will be used.
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qout_DRX_Cat0 [s] period becomes worse
than the threshold Qout_Cat0, Layer 1 of the UE shall send out-of-sync indication for the PCell to the higher layers within
TEvaluate_Qout_DRX_Cat0 [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as specified in
TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qin_DRX_Cat0 [s] period becomes better
than the threshold Qin_Cat0, Layer 1 of the UE shall send in-sync indications for the PCell to the higher layers within
TEvaluate_Qin_DRX_Cat0 [s] evaluation period. A L3 filter shall be applied to the in-sync indications as specified in
TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. When DRX
is used, two successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length). When
eDRX_CONN is used, two successive indications from Layer 1 shall be separated by at least max(10ms, eDRX_CONN
cycle length).
Upon start of T310 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link for recovery using
the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of
T310 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
Table 7.11.2.2-1: Qout and Qin Evaluation Period in DRX for FD-FDD and TDD UE category 0
DRX cycle length (s) TEvaluate_Qout_DRX_Cat0 and
TEvaluate_Qin_DRX_Cat0 (s) (DRX
cycles)
≤ 0.01 Non-DRX requirements in
clause 7.11.2.1 are applicable.
0.01 < DRX cycle ≤0.04 Note (20)
0.04 < DRX cycle ≤ 0. 64 Note (10)
0.64 < DRX cycle ≤ 2.56 Note (5)
Note: Evaluation period length in time depends on the length of
the DRX cycle in use
Table 7.11.2.2-2: Qout and Qin Evaluation Period for FD-FDD and TDD UE category 0 when
eDRX_CONN cycle is used
eDRX_CONN cycle length TEvaluate_Qout_DRX_Cat0 and
[s] TEvaluate_Qin_DRX_Cat0 [s]
(eDRX_CONN cycles)
2.56 < eDRX_CONN cycle ≤ Note (5)
10.24
Note: Evaluation period length in time depends on the length of
the eDRX_CONN cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 160 ETSI TS 136 133 V14.3.0 (2017-04)
7.11.2.3 Minimum requirement at transitions
When the UE transitions between any two of DRX, eDRX_CONN, and non-DRX or when DRX or eDRX_CONN
cycle periodicity changes, for a duration of time equal to the evaluation period corresponding to the second mode after
the transition occurs, the UE shall use an evaluation period that is no less than the minimum of evaluation periods
corresponding to the first mode and the second mode. Subsequent to this duration, the UE shall use an evaluation period
corresponding to the second mode. This requirement shall be applied to both out-of-sync evaluation and in-sync
evaluation of the PCell.
7.11.3 Requirements for HD-FDD
7.11.3.1 Minimum requirement when no DRX is used
The HD-FDD category 0 UE shall meet all applicable requirements specified in clause 7.11.2.1 under the following
conditions
- at least 1 DL subframe per radio frame of PCell is available at the UE during Qin_Cat0 and Qout_Cat0 evaluation
periods.
7.11.3.2 Minimum requirement when DRX is used
When DRX is used for HD-FDD category 0 UEs, the Qout evaluation period (TEvaluate_Qout_DRX_Cat0) and the Qin
evaluation period (TEvaluate_Qin_DRX_Cat0) specified in Table 7.11.3.2-1 will be used.
When eDRX_CONN is used for HD-FDD category 0 UEs, the Qout evaluation period (TEvaluate_Qout_DRX_Cat0) and the Qin
evaluation period (TEvaluate_Qin_DRX_Cat0) specified in Table 7.11.3.2-2 will be used.
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qout_DRX_Cat0 [s] period becomes worse
than the threshold Qout_Cat0, Layer 1 of the UE shall send out-of-sync indication for the PCell to the higher layers within
TEvaluate_Qout_DRX_Cat0 [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as specified in
TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qin_DRX_Cat0 [s] period becomes better
than the threshold Qin_Cat0, Layer 1 of the UE shall send in-sync indications for the PCell to the higher layers within
TEvaluate_Qin_DRX_Cat0 [s] evaluation period. A L3 filter shall be applied to the in-sync indications as specified in
TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. When DRX
is used, two successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length). When
eDRX_CONN is used, two successive indications from Layer 1 shall be separated by at least max(10ms, eDRX_CONN
cycle length).
Upon start of T310 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link for recovery using
the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of
T310 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
Table 7.11.3.2-1: Qout and Qin Evaluation Period in DRX for HD-FDD UE category 0
DRX cycle length (s) TEvaluate_Qout_DRX and
TEvaluate_Qin_DRX (s) (DRX cycles)
≤ 0.01 Non-DRX requirements in
clause 7.11.2.1 are applicable.
0.01 < DRX cycle ≤0.04 Note (40)
0.04 < DRX cycle ≤ 0. 16 Note (20)
0. 16 < DRX cycle ≤ 0.64 Note (10)
0.64 < DRX cycle ≤ 2.56 Note (5)
Note: Evaluation period length in time depends on the length of
the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 161 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.11.3.2-2: Qout and Qin Evaluation Period for HD-FDD UE category 0 when eDRX_CONN cycle is
used
eDRX_CONN cycle length TEvaluate_Qout_DRX and
[s] TEvaluate_Qin_DRX [s] (eDRX_CONN
cycles)
2.56 < eDRX_CONN cycle ≤ Note (5)
10.24
Note: Evaluation period length in time depends on the length of
the eDRX_CONN cycle in use
7.11.3.3 Minimum requirement at transitions
The minimum requirements at transitions defined in clause 7.11.2.3 also apply for this section under the following
conditions:
at least 1 DL subframe per radio frame of PCell is available at the UE during Qin_Cat0 and Qout_Cat0 evaluation
periods.
7.12 Interruptions with Dual Connectivity
7.12.1 Introduction
This section contains the requirements related to the interruptions on PCell, PSCell, and SCell, when
PSCell is added or released, or
transitions between active and non-active during DRX, or
transitions from non-DRX to DRX, or
SCell in either MCG or SCG is added or released, or
SCell in either MCG or SCG is activated or deactivated, or
measurements on SCC with deactivated SCell in either MCG or SCG, or
SRS carrier based switching.
The requirements shall apply for E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD dual connectivity.
7.12.2 Requirements
7.12.2.1 Interruptions at PSCell addition/release
When a PSCell is added or released as defined in [2] the UE is allowed an interruption of up to 1 subframe on PCell and
the activated SCell in MCG if configured during the RRC reconfiguration procedure [2] in synchronous dual
connectivity. This interruption is for both uplink and downlink of PCell.
The UE is allowed an interruption of up to 2 subframes on PCell and the activated SCell in MCG if configured during
the RRC reconfiguration procedure [2] in asynchronous dual connectivity. This interruption is for both uplink and
downlink of PCell.
7.12.2.2 Interruptions at transitions between active and non-active during DRX
When PCell is in non-DRX and PSCell is in DRX, interruptions on PCell and the activated SCell in MCG if configured
due to transitions from active to non-active and from non-active to active during PSCell DRX are allowed with up to
1% probability of missed ACK/NACK when the configured PSCell DRX cycle is less than 640 ms, and 0.625%
probability of missed ACK/NACK is allowed when the configured PSCell DRX cycle is 640 ms or longer. Each
interruption shall not exceed 1 subframe.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 162 ETSI TS 136 133 V14.3.0 (2017-04)
When PSCell is in non-DRX and PCell is in DRX, interruptions on PSCell on the activated SCell in SCG if configured
due to transitions from active to non-active and from non-active to active during PCell DRX are allowed with up to 1 %
probability of missed ACK/NACK when the configured PCell DRX cycle is less than 640 ms, and 0.625% probability
of missed ACK/NACK is allowed when the configured PCell DRX cycle is 640 ms or longer. Each interruption shall
not exceed 1 subframe.
When both PCell and PSCell are in DRX, no interruption is allowed.
7.12.2.3 Interruptions at transitions from non-DRX to DRX
Interruption on PCell and the activated SCell in MCG if configured due to PSCell transitions from non-DRX to DRX
when PCell is in non-DRX shall not exceed 1subframe.
Interruption on PSCell and the activated SCell in SCG if configured due to PCell transitions from non-DRX to DRX
when PSCell is in non-DRX shall not exceed 1subframe.
7.12.2.4 Interruptions at SCell addition/release
The requirements in this clause shall apply for the UE configured with PSCell.
In synchronous dual connectivity, when one SCell is added or released as defined in [2]:
- an interruption on PCell shall meet requirements in clause 7.8.2.7,
- an interruption on PSCell shall meet requirements in clause 7.8.2.7, where the term PCell in clause 7.8.2.7 shall
be deemed to be replaced with PSCell.
In asynchronous dual connectivity, when one SCell belonging to MCG is added or released as defined in [2]:
- an interruption on PCell shall meet requirements in clause 7.8.2.7,
- an interruption on PSCell shall meet requirements in clause 7.8.2.7 except for the number of subframe, where the
term PCell in clause 7.8.2.7 shall be deemed to be replaced with PSCell. The UE is allowed an interruption on
PSCell of up to 2 subframes.
In asynchronous dual connectivity, when one SCell belonging to SCG is added or released as defined in [2]:
- an interruption on PCell shall meet requirements in clause 7.8.2.7 except for the number of subframe. The UE is
allowed an interruption on PCell of up to 2 subframes.
- an interruption on PSCell shall meet requirements in clause 7.8.2.7, where the term PCell in clause 7.8.2.7 shall
be deemed to be replaced with PSCell.
7.12.2.5 Interruptions at SCell activation/deactivation
The requirements in this clause shall apply for the UE configured with PSCell and one SCell.
In synchronous dual connectivity, when one SCell is activated or deactivated as defined in [17]:
- an interruption on PCell shall meet requirements in clause 7.8.2.8,
- an interruption on PSCell shall meet requirements in clause 7.8.2.8, where the term PCell in clause 7.8.2.8 shall
be deemed to be replaced with PSCell.
In asynchronous dual connectivity, when one SCell belonging to MCG is activated or deactivated as defined in [17]:
- an interruption on PCell shall meet requirements in clause 7.8.2.8,
- an interruption on PSCell shall meet requirements in clause 7.8.2.8 except for the number of subframe, where the
term PCell in clause 7.8.2.8 shall be deemed to be replaced with PSCell. The UE is allowed an interruption on
PSCell of up to 2 subframes.
In asynchronous dual connectivity, when one SCell belonging to SCG is activated or deactivated as defined in [17]:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 163 ETSI TS 136 133 V14.3.0 (2017-04)
- an interruption on PCell shall meet requirements in clause 7.8.2.8 except for the number of subframe. The UE is
allowed an interruption on PCell of up to 2 subframes,
- an interruption on PSCell shall meet requirements in clause 7.8.2.8, where the term PCell in clause 7.8.2.8 shall
be deemed to be replaced with PSCell.
7.12.2.6 Interruptions during measurements on SCC
The requirements in this clause shall apply for the UE configured with PSCell and one SCell.
In synchronous dual connectivity, when one SCell is deactivated, the UE is allowed due to measurements on the SCC
with the deactivated SCell:
- an interruption on PCell shall meet requirements in clause 7.8.2.9,
- an interruption on PSCell shall meet requirements in clause 7.8.2.9, where the term PCell in clause 7.8.2.8 shall
be deemed to be replaced with PSCell.
In asynchronous dual connectivity, when one SCell belonging to MCG is deactivated, the UE is allowed due to
measurements on the SCC with the deactivated SCell:
- an interruption on PCell shall meet requirements in clause 7.8.2.9,
- an interruption on PSCell shall meet requirements in clause 7.8.2.9 except for the number of subframe, where the
term PCell in clause 7.8.2.9 shall be deemed to be replaced with PSCell. The UE is allowed an interruption on
PSCell of up to 2 subframes.
In asynchronous dual connectivity, when one SCell belonging to SCG is deactivated, the UE is allowed due to
measurements on the SCC with the deactivated SCell:
- an interruption on PCell shall meet requirements in clause 7.8.2.9 except for the number of subframe. The UE is
allowed an interruption on PCell of up to 2 subframes
- an interruption on PSCell shall meet requirements in clause 7.8.2.9, where the term PCell in clause 7.8.2.9 shall
be deemed to be replaced with PSCell.
7.12.2.7 Interruptions at SRS carrier based switching
A PUSCH-less SCC is a TDD SCC without PUCCH/PUSCH configured. When a UE needs to transmit periodic or
aperiodic SRS [16] and/or non-contention based PRACH on a PUSCH-less SCC, the UE can perform carrier based
switching to one or more PUSCH-less SCCs from a CC with PUSCH or from another PUSCH-less SCC prior to
transmitting SRS and/or PRACH, [provided that:
- switching is from a configured CC to another activated TDD CC;
- the PUSCH-less SCCs to which SRS carrier based switching is performed is indicated by DCI SRS request field
for aperiodic SRS transmission or configured via RRC [2] for periodic SRS transmission or indicated by
PDCCH for PRACH;
- the CC from which SRS carrier based switching is performed is indicated by IdexSwitchingFromCarrierlist [2];
- the SRS switching is not colliding with any other transmission with higher priority defined in [3];
- the SRS switching is not colliding with PDCCH in subframe 0 and 5 as specified in [3];
- for UE, which does not support simultaneous reception and transmission for inter-band TDD CA specified in TS
36.331 [2], and is compliant to the requirements for inter-band CA with uplink in one E-UTRA band and without
simultaneous Rx/Tx specified in TS 36.101 [5], the SRS or RACH transmission are not simultaneously
scheduled with DL subframe #0 or DL subframe #5 on other CCs.
The UE shall not perform SRS carrier based switching if the above conditions cannot be met.
The interruption on PCC, PSCC and each of the activated SCCs during the switching to the PUSCH-less SCC shall not
exceed 2 subframes including the first subframe where SRS transmission is configured on the PUSCH-less SCC.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 164 ETSI TS 136 133 V14.3.0 (2017-04)
The interruption on PCC, PSCC and each of the activated SCCs during the switching from the PUSCH-less SCC shall
not exceed 2 subframes including the last subframe where SRS transmission is configured on the PUSCH-less SCC.
7.13 Cell phase synchronization accuracy (Synchronized mode
of dual connectivity)
7.13.1 Definition
Cell phase synchronization accuracy is defined as the maximum absolute timing mismatch between subframes which
are transmitted by MeNB and SeNB and are scheduled for the same UE. The cell phase synchronization accuracy is
defined only for synchronized mode of dual connectivity operation.
7.13.2 Minimum requirements
The cell phase synchronization accuracy shall not exceed the sum of absolute timing accuracy values declared by the
manufacturer(s) for each BS. The cell phase synchronization accuracy requirement is optional.
NOTE: The sum of absolute timing accuracy values in synchronized mode of dual connectivity is assumed to be related
to MRTD according to the following inequality:
TCPSA+TRPTD ≤ MRTD at the UE
Where:
TCPSA is the sum of absolute timing accuracy values declared by the manufacturer(s).
TRPTD is the absolute propagation time difference between MeNB and SeNB, which serve the same UE.
MRTD is the Maximum Received Timing Difference at the UE. MRTD is equal to 33 µs.
7.14 PSCell Addition and Release Delay for E-UTRA Dual
Connectivity
7.14.1 Introduction
This section defines requirements for the delay within which the UE shall be able to configure a PSCell in E-UTRA
dual connectivity. The requirements are applicable to an E-UTRA dual connectivity capable UE. The requirements shall
apply for E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD dual connectivity.
7.14.2 PSCell Addition Delay Requirement
The requirements in this section shall apply for the UE configured with only PCell.
Upon receiving PSCell addition in subframe n, the UE shall be capable to transmit PRACH preamble towards PSCell
no later than in subframe n+ Tconfig_ PSCell:
Where:
Tconfig_PSCell = 20ms + Tactivation_time + 50ms + TPCell_ DU + TPSCell_ DU
Tactivation_time is the PSCell activation delay. If the PSCell is known, then Tactivation_time is 20ms. If the PSCell is
unknown, then Tactivation_time is 30ms provided the PSCell can be successfully detected on the first attempt.
TPCell_ DU is the delay uncertainty due to PCell PRACH preamble transmission. TPCell_ DU is up to 20ms if PSCell
activation is interrupted by a PCell PRACH preamble transmission, otherwise it is 0.
TPSCell_ DU is the delay uncertainty in acquiring the first available PRACH occasion in the PSCell. TPSCell_ DU is up
to 30ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 165 ETSI TS 136 133 V14.3.0 (2017-04)
PSCell is known if it has been meeting the following conditions:
During the last [5] seconds before the reception of the PSCell configuration command:
- the UE has sent a valid measurement report for the PSCell being configured and
- the PSCell being configured remains detectable according to the cell identification conditions specified in
section 8.8,
- PSCell being configured also remains detectable during the PSCell configuration delay according to the cell
identification conditions specified in section 8.8.
otherwise it is unknown.The PCell interruption specified in section 7.12 is allowed only during the RRC reconfiguration
procedure [2].
The PSCell addition delay specified in this section can be extended if SRS carrier based switching occurs during the
PSCell addition procedure.
7.14.3 PSCell Release Delay Requirement
The requirements in this section shall apply for a UE configured with PCell and one PSCell.
Upon receiving PSCell release in subframe n, the UE shall accomplish the release actions specified in [2] no later than
in subframe n+20.
The PCell interruption specified in section 7.12 is allowed only during the RRC reconfiguration procedure [2].
The PSCell release delay specified in this section can be extended if SRS carrier based switching occurs during the
PSCell release procedure.
7.15 Maximum Receive Timing Difference in Dual Connectivity
7.15.1 Introduction
A UE shall be capable of handling a relative receive timing difference between subframe timing boundaries of the PCell
and PSCell to be aggregated for E-UTRA FDD-FDD, E-UTRA-TDD-TDD, E-UTRA TDD-FDD dual connectivity.
7.15.2 Minimum Requirements for Inter-band Dual Connectivity
The UE shall be capable of handling at least a relative receive timing difference between the subframe timing of the
signals received from a cell belonging to the MCG and a cell belonging to the SCG at the UE receiver of up to 33 µs
provided the UE indicates that it is capable of synchronous dual connectivity [2]. The requirements for synchronous
dual connectivity are only applicable for TDD-TDD, FDD-FDD, and TDD-FDD inter-band dual connectivity.
The UE shall be capable of handling at least a relative receive timing difference between the subframe timing of the
signals received from a cell belonging to the MCG and a cell belonging to the SCG at the UE receiver of up of 500 µs
provided the UE indicates that it is capable of asynchronous dual connectivity [2]. The requirements for asynchronous
dual connectivity are only applicable for FDD-FDD inter-band dual connectivity.
The UE shall be capable of handling a relative receive timing difference between the subframe timing of the signals
received from any pair of the serving cells belonging to the same cell group according to the requirements in clause
7.9.2.
7.16 Proximity-based Services
7.16.1 Introduction
The requirements in this clause are applicable for UE performing transmissions and/or reception for ProSe Direct
Discovery and/or ProSe Direct Communication in both RRC_IDLE and RRC_CONNECTED state.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 166 ETSI TS 136 133 V14.3.0 (2017-04)
7.16.2 Requirements
7.16.2.1 ProSe UE transmission timing
For ProSe transmission of sidelink channels and signals, UE shall have the capability to follow the timing change of the
reference synchronization source.
7.16.2.1.1 Serving cell or PCell as timing reference
The requirements in this subclause are applicable when the reference timing used for ProSe transmissions is the serving
cell (RRC_IDLE) or PCell (RRC_CONNECTED). The sidelink transmissions takes place ( N TA, SL + N TA offset ) ⋅ Ts
before the reception of the first detected path (in time) of the corresponding downlink frame from the reference cell,
where N TA offset is specified in Section 8.1 of [16]. The value of N TA,SL differs between sidelink channels and signals,
and is either N TA, SL = N TA or N TA, SL = 0 as specified in Section 9.9 of [16].
7.16.2.1.1.1 Requirements when NTA,SL = 0
For ProSe transmission of sidelink channels and signals employing N TA, SL = 0 , the requirements in Section 7.1 as
specified for PRACH transmissions shall apply.
7.16.2.1.1.2 Requirements when NTA,SL = NTA
For ProSe transmission of sidelink channels and signals while employing N TA, SL = N TA , the requirements in Section
7.1 as specified for PUSCH shall apply.
When it is the first sidelink transmission in a DRX cycle, the requirements in Section 7.1 as specified for the first
PUSCH transmission in a DRX cycle shall apply. The reference point for the UE initial transmit timing control
requirement shall be ( N TA, SL_ref + N TA offset ) ⋅ Ts seconds before the reception of the first detected path (in time) of the
corresponding downlink frame from the reference cell. ( N TA, SL_ref + N TA offset ) (in Ts units) for sidelink transmissions is
the difference between UE transmission timing and the downlink timing immediately after when the last timing advance
in Section 7.3 was applied.
When it is not the first sidelink transmission in a DRX cycle or there is no DRX cycle, the requirements as specified in
Section 7.1 for PUSCH transmissions when the PUSCH transmission is not the first transmissions in a DRX cycle shall
apply.
7.16.2.1.2 SCell or non-serving cell as timing reference
The requirements in this subclause are applicable when the reference timing used for ProSe transmissions is either a
SCell (RRC_CONNECTED) or a non-serving cell selected on a non-serving ProSe carrier (RRC_IDLE or
RRC_CONNECTED).
The transmission timing requirements are as specified in subclause 7.16.2.1.1, with reference cell as either the SCell or
the selected non-serving cell.
7.16.3 Interruptions with ProSe
This section contains the requirements related to the interruptions on PCell and activated SCell(s) due ProSe Direct
Discovery and ProSe Direct Communication. When ProSe is on a serving cell frequency, then the requirements in this
subclause are applicable only to ProSe on E-UTRA FDD bands. When ProSe is on non-serving frequency, then the
requirements are applicable to ProSe on both E-UTRA FDD and TDD bands.
When a UE capable of ProSe Direct Communication and/or ProSe Direct Discovery is configured with DRX and DRX
is in use, interruptions specified in this section are not allowed while the onDurationTimer[17] is running.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 167 ETSI TS 136 133 V14.3.0 (2017-04)
7.16.3.1 Interruptions at ProSe Direct Discovery configuration
A UE capable of ProSe Direct Discovery may indicate its interest (initiation or termination) in ProSe Direct Discovery
to the connected eNodeB using IE SidelinkUEInformation [2].
The UE is allowed an interruption of up to 1 subframe on PCell and on any activated SCell during the RRC
reconfiguration procedure that includes the ProSe Direct Discovery configuration message sl-DiscConfig [2] (setup and
release). This interruption is for both uplink and downlink of PCell and activated SCell(s).
7.16.3.2 Interruptions at ProSe Direct Communication configuration
A UE capable of ProSe Direct Communication may indicate its interest (initiation or termination) in ProSe Direct
Communication to the connected eNodeB using IE SidelinkUEInformation [2].
The UE is allowed an interruption of up to 1 subframe on PCell and on any activated SCell during the RRC
reconfiguration procedure that includes the ProSe Direct Communication configuration message sl-CommConfig [2]
(setup and release). This interruption is for both uplink and downlink of PCell and activated SCell(s).
7.16.3.3 Interruptions during ProSe Direct Discovery
When ProSe Direct Discovery operation is on a serving cell (PCell/SCell) and when no request for transmission and/or
reception gaps are signalled by the ProSe UE, the UE is allowed an interruption of up to 1 subframe that is N subframes
before and after a UL subframe configured for ProSe Direct Discovery by a serving eNodeB. For discovery period less
than 320ms, the allowed interruptions are additionally limited up to 0.625%.
The value of N is ceil(w1 / 1ms) subframes when the parameter discSyncWindow[2] is configured with value w1 in the
sidelink synchronization resource configuration associated with the ProSe Direct Discovery subframe.
The value of N is 1 subframe otherwise.
When ProSe Direct Discovery is on a non-serving carrier, and when no request for transmission and/or reception gaps is
signalled by the UE, interruptions to serving cell(s) is allowed with up to
probability of missed ACK/NACK. Furthermore, when ProSe Direct Discovery is on more than one non-serving carrier,
and no request for transmission and/or reception gaps is signalled by the UE, the aggregate interruptions to serving
⎛ N
⎛ 6 ⎞⎞
cells(s) are allowed with up to min⎜⎜ 2%, ∑ min⎜⎜ 0.5%, × 100% ⎟⎟ ⎟⎟ probability of missed
⎝ i =1 ⎝ discPeriod i (ms ) ⎠⎠
ACK/NACK with N non-serving carriers.
The interruptions are for both uplink and downlink of PCell and any activated SCell. The interruption for the ProSe UE
may occur:
- while switching a receiver chain ON/OFF for ProSe Direct Discovery if the UE has a dedicated receiver chain
for discovery, and/or
- while switching a transmitter chain ON/OFF for ProSe Direct Discovery transmissions on a non-serving carrier,
and if the UE has a dedicated transmitted chain for discovery.
7.16.3.4 Interruptions during ProSe Direct Discovery with discovery gaps
When ProSe Direct Discovery is either on a serving cell (PCell/SCell) or a non-serving frequency, and when discovery
reception and/or transmission gaps are configured by the serving cell, then only the following interruptions to the PCell
and any activated SCell(s) are allowed:
- Uplink interruption is allowed on a subframe configured as downlink reception gap (using discRxGapConfig) if
either the subframe immediately preceding or immediately following that subframe is not configured as
reception gap; and,
- If ProSe Direct Discovery is on a non-serving FDD carrier and that carrier is used for ProSe synchronization,
then uplink interruption is additionally allowed on 1 subframe in a discovery period. The interrupted subframe(s)
shall be within the subframes configured as reception gap using discRxGapConfig; and,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 168 ETSI TS 136 133 V14.3.0 (2017-04)
- If ProSe Direct Discovery transmissions are on carrier that is not configured for uplink, then UE is allowed to
additionally interrupt the serving cell(s) on up to 2 subframes for each discovery/SLSS transmission configured
in a discovery period. The interrupted subframe(s) shall be within the subframes configured as transmission gaps
using discTxGapConfig.
NOTE: The request and grant of discovery gaps is left up to UE and eNodeB implementations, respectively.
When ProSe Direct Discovery is on a non-serving carrier and that carrier is used for ProSe
synchronization, then the UE requested / eNodeB configured gaps may depend if inter-frequency
measurements are additionally configured for that non-serving frequency.
7.16.3.5 Interruptions during ProSe Direct Communication
When ProSe Direct Communication is on a non-serving carrier and the PCell is not broadcasting SIB18, then
interruptions to serving cell(s) is allowed with up to 0.5% probability of missed ACK/NACK. Furthermore, when ProSe
Direct Communication is on more than one non-serving carrier, the aggregate interruptions to serving cell(s) is allowed
with up to min(2%, 0.5%×N) probability of missed ACK/NACK with N non-serving carriers.
The interruptions are for both uplink and downlink of PCell and any activated SCell.
7.16.4 Cell reselection for ProSe Direct Discovery on non-serving
frequency
The requirements in this subclause apply when ProSe Direct Discovery transmissions are configured on a non-serving
carrier and that non-serving carrier is used for downlink synchronziation and measurements for ProSe Direct Discovery
transmission, and provided the parameters required for cell selection / reselection are provided by the serving cell using
discCellSelectionInfo.
NOTE: The requirements do not apply if the UE is required to acquire the cell selection/reselection parameters
that are broadcast from the concerned cell for evaluation.
If the UE signals request for transmission and/or reception gaps, then the requirements apply if the gaps are configured
as requested by the UE.
7.16.4.1 Measurement and evaluation of selected cell
The UE shall measure the RSRP and RSRQ level of the selected reference cell on the non-serving carrier used for
ProSe Direct Discovery synchronization and evaluate the cell selection criterion S defined in [1] for the selected cell at
least every discovery period.
The UE shall filter the RSRP and RSRQ measurements of the selected 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 discPeriod / 2.
7.16.4.2 Measurement of intra-frequency E-UTRAN cells
The UE shall be able to identify new intra-frequency cells on the non-serving carrier used for ProSe Direct Discovery
transmission and perform RSRP and RSRQ measurements of identified intra-frequency cells.
The UE shall be able to evaluate whether a newly detectable intra-frequency cell meets the reselection criteria defined
in TS36.304 [1, 11.4] within Tdetect,EUTRAN_ProSe_Intra when Treselection = 0 (within discCellSelectionInfo). 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_ProSe_Intra (see table 7.16.4.2-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_ProSe_Intra/2
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_ProSe_Intra when Treselection = 0 (within discCellSelectionInfo) as specified in table 7.16.4.2-1 provided that
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 169 ETSI TS 136 133 V14.3.0 (2017-04)
the cell is at least 3dB better ranked. When evaluating cells for reselection, the side conditions for RSRP and SCH apply
to both the non-serving cell that is currently selected and the non-serving cell being reselected to for ProSe Direct
Discovery synchronization.
If Treselection timer (within discCellSelectionInfo) has a non-zero value and the intra-frequency cell being reselected to is
better ranked than the currently selected reference 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.
Table 7.16.4.2-1: Tdetect,EUTRAN_ProSe_Intra, Tmeasure,EUTRAN_ProSe_Intra and Tevaluate, E-UTRAN_ProSe_Intra
Tdetect,EUTRAN_ProSe_Intra Tmeasure,EUTRAN_ProSe_Intra Tevaluate,E-UTRAN_ProSe_Intra
Discovery Period [s] (number of (number of discovery (number of discovery
discovery periods) periods) periods)
Discovery Period≤0.32 Note 1 (36) Note 1 (4) Note 1 (16)
0.32<Discovery Period≤0.64 Note 1 (28) Note 1 (2) Note 1 (8)
0.64<Discovery Period≤1.28 Note 1 (25) Note 1 (1) Note 1 (5)
1.28<Discovery Period≤10.24 Note 1 (23) Note 1 (1) Note 1 (3)
NOTE 1: Time depends upon the configured Discovery period.
7.16.5 Selection / Reselection of ProSe relay UE
This subclause contains the requirements related to selection and reselection of ProSe relay UE if the serving frequency
is used for ProSe Direct Communication via a ProSe relay UE.
For a remote UE configured by upper layer for relay operation, when the RSRP measurement of the serving cell
(RRC_IDLE) or the PCell (RRC_CONNECTED) is below threshHigh (within remoteUE-Config), the remote UE shall
search for candidate relay UEs for selection and/or reselection every discovery period.
If the remote UE has a selected sidelink relay UE, then the remote UE shall measure the SD-RSRP of the selected relay
once in every four discovery periods and evaluate if it meets the relay selection criterion as defined in [TS 36.331,
5.10.11.4].
The remote UE shall measure SD-RSRP of the candidate relay UEs every Tmeasure, ProSe_Relay_Intra for intra-frequency relay
UEs that are detected and measured according to the measurement rules.
For an intra-frequency relay UEs that are detected, but that has not been selected or reselected to, the remote UE shall
be capable of evaluating that the intra-frequency relay UE has met selection or reselection criterion defined in [2,
5.10.11.4] within Tevaluate,ProSe_Relay_Intra as specified in table 7.16.5-1.
The minimum requirements are required to meet when the selected and candidate relay UEs are transmitting relay
discovery message every discovery period.
Table 7.16.5-1: Tmeasure, ProSe_Relay_Intra and Tevaluate, ProSe_Relay_intra
Tmeasure,ProSe_Relay_Intra Tevaluate, ProSe_Relay_intra
Discovery
[s] (number of [s] (number of
Period [s]
discovery periods) discovery periods)
0.04≤Discovery
Note 1 (4) Note 1 (16)
period≤10.24
NOTE 1: Time depends upon the configured Discovery period.
7.17 Maximum Transmission Timing Difference in Dual
Connectivity
7.17.1 Introduction
A UE shall be capable of handling a relative transmission timing difference between subframe timing boundaries of the
PCell and PSCell to be aggregated for E-UTRA FDD-FDD, E-UTRA-TDD-TDD, E-UTRA TDD-FDD dual
connectivity.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 170 ETSI TS 136 133 V14.3.0 (2017-04)
7.17.2 Minimum Requirements for maximum transmission timing difference
Inter-band Dual Connectivity
The UE shall be capable of handling a maximum uplink transmission timing difference between PCell and PSCell of at
least 35.21 µs provided the UE indicates that it is capable of synchronous dual connectivity [2]. The requirements for
synchronous dual connectivity are only applicable for TDD-TDD, FDD-FDD, and TDD-FDD inter-band dual
connectivity.
The UE shall be capable of handling a maximum uplink transmission timing difference between PCell and PSCell of at
least 500 µs provided the UE indicates that it is capable of asynchronous dual connectivity [2]. The requirements for
asynchronous dual connectivity are only applicable for FDD-FDD and inter-band dual connectivity.
If the UE is configured with higher layer parameter powerControlMode<1>, then the UE may stop transmission on the
PSCell if the UL transmission timing difference exceeds 35.21µs. If a UE supports both synchronous and asynchronous
dual connectivity and if the UE is configured with higher layer parameter powerControlMode<2>, then the UE needs to
constitute new subframes pair if the UL transmission timing difference exceeds 500µs.7.18 SCell Activation and
Deactivation Delay for E-UTRA Dual Connectivity
7.18.1 Introduction
This section defines requirements for the delay within which the UE shall be able to activate a deactivated SCell and
deactive an activated SCell in E-UTRA dual connectivity. The requirements are applicable to an E-UTRA dual
connectivity capable UE which has been configured with one SCell in either MCG or SCG and PSCell. In case where
the SCell belongs to SCG, the term PCell in clause 7.7 shall be replaced with PSCell. The requirements shall apply for
E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD dual connectivity.
7.18.2 SCell Activation Delay Requirement for Deactivated SCell
The requirements in this clause shall apply for a UE configured with PSCell and one SCell.
The SCell activation delay shall meet the requirements in clause 7.7.2.
7.18.3 SCell Deactivation Delay Requirement for Activated SCell
The requirements in this clause shall apply for a UE configured with PSCell and one SCell.
The SCell deactivation delay shall meet the requirements in clause 7.7.3.
7.19 Radio Link Monitoring for UE Category M1
7.19.1 Introduction
The UE category M1 applicability of the requirements for performing radio link monitoring in subclause 7.19 is defined
in Section 3.6.
The UE shall monitor the downlink link quality based on the cell-specific reference signal in order to detect the
downlink radio link quality of the PCell as specified in [3].
7.19.2 Requirements for FD-FDD and TDD CE mode A
The requirements defined in this subclause 7.19.2 for performing radio link monitoring are applicable for UE category
M1 defined in Section 3.6.
The UE shall estimate the downlink radio link quality and compare it to the thresholds Qout_Cat M1 and Qin_Cat M1 for the
purpose of monitoring downlink radio link quality of the PCell.
The threshold Qout_Cat M1 is defined as the level at which the downlink radio link cannot be reliably received and shall
correspond to 10% block error rate of a hypothetical MPDCCH transmission with transmission parameters specified in
Table 7.19.2-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 171 ETSI TS 136 133 V14.3.0 (2017-04)
The threshold Qin_Cat M1 is defined as the level at which the downlink radio link quality can be significantly more
reliably received than at Qout_Cat M1 and shall correspond to 2% block error rate of a hypothetical MPDCCH transmission
with transmission parameters specified in Table 7.19.2-1.
Table 7.19.2-1 M-PDCCH transmission parameters for out-of-sync and in-sync for UE category M1
with CE mode A
Attribute Out-of-sync In-sync
DCI format 6-1A 6-1A
Starting OFDM symbols 2; Bandwidth >= 10MHz 2; Bandwidth >= 10MHz
3; 3MHz <= Bandwidth < 10MHz 3; 3MHz <= Bandwidth < 10MHz
4; Bandwidth = 1.4MHz 4; Bandwidth = 1.4MHz
Maximum M-PDCCH repetition level Rmax Note1 Rmax /2 Note1
Aggregation level (ECCE) L’max Note2 L’max-2Note2
M-PDCCH Transmission type Distributed Distributed
NOTE 1: Rmax is determined by the configurable parameter mPDCCH-NumRepetition defined in 36.331 and Rmax>1.
NOTE 2: L’max and L’max-2 is derived from the configurable parameter numberPRB-Pairs defined in 36.331. L’max is 24,
16 and 8, if numberPRB-Pairs is 6, 4 and 2, respectively. L’max-2 is the aggregation level two levels below L’max,
and L’max-2 is 8, 4 and 2, if numberPRB-Pairs is 6, 4 and 2, respectively.
7.19.2.1 Minimum requirement when no DRX is used
When the downlink radio link quality of the PCell estimated over the last 400 ms period becomes worse than the
threshold Qout_CatM1, Layer 1 of the UE shall send an out-of-sync indication for the PCell to the higher layers within 400
ms Qout_CatM1 evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as specified in
TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last 200 ms period becomes better than the
threshold Qin_CatM1, Layer 1 of the UE shall send an in-sync indication for the PCell to the higher layers within 200 ms
Qin_CatM1 evaluation period. A L3 filter shall be applied to the in-sync indications as specified in TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. Two
successive indications from Layer 1 shall be separated by at least 10ms.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
7.19.2.2 Minimum requirement when DRX is used
When DRX is used for FD-FDD and TDD UE category M1 UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.2.2-1 will be
used.
When eDRX_CONN cycle is used for FD-FDD and TDD UE category M1 UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.2.2-2 will be
used.
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qout_DRX_CatM1 [s] period becomes
worse than the threshold Qout_CatM1, Layer 1 of the UE shall send out-of-sync indication for the PCell to the higher layers
within TEvaluate_Qout_DRX_CatM1 [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as
specified in TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qin_DRX_CatM1 [s] period becomes better
than the threshold Qin_CatM1, Layer 1 of the UE shall send in-sync indications for the PCell to the higher layers within
TEvaluate_Qin_DRX_CatM1 [s] evaluation period. A L3 filter shall be applied to the in-sync indications as specified in
TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. When DRX
is used, two successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length). When
eDRX_CONN is used, two successive indications from Layer 1 shall be separated by at least max(10 ms,
eDRX_CONN cycle length).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 172 ETSI TS 136 133 V14.3.0 (2017-04)
Upon start of T310 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link for recovery using
the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of
T310 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
Table 7.19.2.2-1: Qout_CatM1 and Qin_CatM1 Evaluation Period in DRX for FD-FDD and TDD UE category M1
DRX cycle length (s) TEvaluate_Qout_DRX_CatM1 and
TEvaluate_Qin_DRX_CatM1 (s) (DRX
cycles)
≤ 0.01 Non-DRX requirements in
clause 7.19.2.1 are applicable.
0.01 < DRX cycle ≤0.04 Note (20)
0.04 < DRX cycle ≤ 0. 64 Note (10)
0.64 < DRX cycle ≤ 2.56 Note (5)
NOTE: Evaluation period length in time depends on the length of
the DRX cycle in use
Table 7.19.2.2-2: Qout_CatM1 and Qin_CatM1 evaluation period when eDRX_CONN cycle is configured for
FD-FDD and TDD UE category M1
eDRX_CONN cycle length TEvaluate_Qout_DRX_CatM1 and
(s) TEvaluate_Qin_DRX_CatM1 (s)
(eDRX_CONN cycles)
2.56 < eDRX_CONN cycle ≤ Note (5)
10.24
NOTE: Evaluation period length in time depends on the length of
the eDRX_CONN cycle in use
7.19.2.3 Minimum requirement at transitions
When the UE transitions between any two of DRX, eDRX_CONN and non-DRX or when DRX or eDRX_CONN cycle
periodicity changes, for a duration of time equal to the evaluation period corresponding to the second mode after the
transition occurs, the UE shall use an evaluation period that is no less than the minimum of evaluation periods
corresponding to the first mode and the second mode. Subsequent to this duration, the UE shall use an evaluation period
corresponding to the second mode. This requirement shall be applied to both out-of-sync evaluation and in-sync
evaluation of the PCell.
7.19.3 Requirements for HD-FDD with CE mode A
The requirements defined in this subclause 7.19.3 for performing radio link monitoring are applicable for UE category
M1 defined in Section 3.6.
7.19.3.1 Minimum requirement when no DRX is used
The HD-FDD category M1 with CE mode A UE shall meet all applicable requirements specified in clause 7.19.2.1
under the following conditions
- at least 1 DL subframe per radio frame of PCell is available at the UE during Qin_CatM1 and Qout_CatM1 evaluation
periods.
7.19.3.2 Minimum requirement when DRX is used
When DRX is used for HD-FDD category M1 with CE mode A UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.3.2-1 will be
used.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 173 ETSI TS 136 133 V14.3.0 (2017-04)
When eDRX_CONN cycle is used for HD-FDD category M1 with CE mode A UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.3.2-2 will be
used.
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qout_DRX_CatM1 [s] period becomes
worse than the threshold Qout_CatM1, Layer 1 of the UE shall send out-of-sync indication for the PCell to the higher layers
within TEvaluate_Qout_DRX_CatM1 [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as
specified in TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qin_DRX_CatM1 [s] period becomes better
than the threshold Qin_CatM1, Layer 1 of the UE shall send in-sync indications for the PCell to the higher layers within
TEvaluate_Qin_DRX_CatM1 [s] evaluation period. A L3 filter shall be applied to the in-sync indications as specified in
TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. When DRX
is used, two successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length). When
eDRX_CONN is used, two successive indications from Layer 1 shall be separated by at least max(10 ms,
eDRX_CONN cycle length).
Upon start of T310 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link for recovery using
the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of
T310 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
Table 7.19.3.2-1: Qout_CatM1 and Qin_CatM1 Evaluation Period in DRX for HD-FDD UE category M1 with CE
mode A
DRX cycle length (s) TEvaluate_Qout_DRX_CatM1 and
TEvaluate_Qin_DRX_CatM1 (s) (DRX
cycles)
≤ 0.01 Non-DRX requirements in
clause 7.19.3.1 are applicable.
0.01 < DRX cycle ≤0.04 Note (40)
0.04 < DRX cycle ≤ 0. 16 Note (20)
0. 16 < DRX cycle ≤ 0.64 Note (10)
0.64 < DRX cycle ≤ 2.56 Note (5)
Note: Evaluation period length in time depends on the length of
the DRX cycle in use
Table 7.19.3.2-2: Qout_CatM1 and Qin_CatM1 evaluation period when eDRX_CONN cycle is configured for
HD-FDD UE category M1 with CE mode A
eDRX_CONN cycle length TEvaluate_Qout_DRX_CatM1 and
(s) TEvaluate_Qin_DRX_CatM1 (s)
(eDRX_CONN cycles)
2.56 < eDRX_CONN cycle ≤ Note (5)
10.24
NOTE: Evaluation period length in time depends on the length of
the eDRX_CONN cycle in use
7.19.3.3 Minimum requirement at transitions
The minimum requirements at transitions defined in clause 7.19.2.3 also apply for this section under the following
conditions:
- at least 1 DL subframe per radio frame of PCell is available at the UE during Qin_CatM1 and Qout_CatM1 evaluation
periods.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 174 ETSI TS 136 133 V14.3.0 (2017-04)
7.19.4 Requirements for FD-FDD and TDD with CE mode B
The requirements defined in this subclause 7.19.4 for performing radio link monitoring are applicable for UE category
M1 defined in Section 3.6.
The UE shall estimate the downlink radio link quality and compare it to the thresholds Qout_Cat M1 and Qin_Cat M1 for the
purpose of monitoring downlink radio link quality of the PCell.
The threshold Qout_Cat M1 is defined as the level at which the downlink radio link cannot be reliably received and shall
correspond to 10% block error rate of a hypothetical MPDCCH transmission with transmission parameters specified in
Table 7.19.4-1.
The threshold Qin_Cat M1 is defined as the level at which the downlink radio link quality can be significantly more
reliably received than at Qout_Cat M1 and shall correspond to 2% block error rate of a hypothetical MPDCCH transmission
with transmission parameters specified in Table 7.19.4-1.
Table 7.19.4-1 M-PDCCH transmission parameters for out-of-sync and in-sync for UE category M1
with CE mode B
Attribute Out-of-sync In-sync
DCI format 6-1B 6-1B
Starting OFDM symbols 2; Bandwidth >= 10MHz 2; Bandwidth >= 10MHz
3; 3MHz <= Bandwidth < 10MHz 3; 3MHz <= Bandwidth < 10MHz
4; Bandwidth = 1.4MHz 4; Bandwidth = 1.4MHz
Maximum M-PDCCH repetition level RmaxNote1 Rmax/2Note1
Aggregation level (ECCE) L’max Note2 L’max-2 Note2
M-PDCCH Transmission type Distributed Distributed
NOTE 1: Rmax is determined by the configurable parameter mPDCCH-NumRepetition defined in 36.331 and
Rmax>1.
NOTE 2: L’max and L’max-2 is derived from the configurable parameter numberPRB-Pairs defined in 36.331.
L’max is 24, 16 and 8, if numberPRB-Pairs is 6, 4 and 2, respectively. L’max-2 is the aggregation levels
two levels below L’max, and L’max-2 is 8, 4 and 2, if numberPRB-Pairs is 6, 4 and 2, respectively.
7.19.4.1 Minimum requirement when no DRX is used
When the downlink radio link quality of the PCell estimated over the last 4000 ms period becomes worse than the
threshold Qout_CatM1, Layer 1 of the UE shall send an out-of-sync indication for the PCell to the higher layers within
4000 ms Qout_CatM1 evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as specified in
TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last 2000 ms period becomes better than the
threshold Qin_CatM1, Layer 1 of the UE shall send an in-sync indication for the PCell to the higher layers within 2000 ms
Qin_CatM1 evaluation period. A L3 filter shall be applied to the in-sync indications as specified in TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. Two
successive indications from Layer 1 shall be separated by at least 10ms.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
7.19.4.2 Minimum requirement when DRX is used
When DRX is used for FD-FDD and TDD UE category M1 UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.4.2-1 will be
used.
When eDRX_CONN cycle is used for FD-FDD and TDD UE category M1 UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.4.2-2 will be
used.
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qout_DRX_CatM1 [s] period becomes
worse than the threshold Qout_CatM1, Layer 1 of the UE shall send out-of-sync indication for the PCell to the higher layers
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 175 ETSI TS 136 133 V14.3.0 (2017-04)
within TEvaluate_Qout_DRX_CatM1 [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as
specified in TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qin_DRX_CatM1 [s] period becomes better
than the threshold Qin_CatM1, Layer 1 of the UE shall send in-sync indications for the PCell to the higher layers within
TEvaluate_Qin_DRX_CatM1 [s] evaluation period. A L3 filter shall be applied to the in-sync indications as specified in
TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. When DRX
is used, two successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length). When
eDRX_CONN is used, two successive indications from Layer 1 shall be separated by at least max(10 ms,
eDRX_CONN cycle length).
Upon start of T310 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link for recovery using
the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of
T310 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
Table 7.19.4.2-1: Qout_CatM1 and Qin_CatM1 Evaluation Period in DRX for FD-FDD and TDD UE category M1
DRX cycle length (s) TEvaluate_Qout_DRX_CatM1 and
TEvaluate_Qin_DRX_CatM1 (s) (DRX
cycles)
≤ [0.16] Non-DRX requirements in
clause 7.19.4.1 are applicable.
[0.160] < DRX cycle ≤ [0.320] Note (20)
[0.320] < DRX cycle ≤ 0. 64 Note (10)
0.64 < DRX cycle ≤ 2.56 Note (5)
NOTE: Evaluation period length in time depends on the length of
the DRX cycle in use
Table 7.19.4.2-2: Qout_CatM1 and Qin_CatM1 evaluation period when eDRX_CONN cycle is configured for
FD-FDD and TDD UE category M1
eDRX_CONN cycle length TEvaluate_Qout_DRX_CatM1 and
(s) TEvaluate_Qin_DRX_CatM1 (s)
(eDRX_CONN cycles)
2.56 < eDRX_CONN cycle ≤ Note (5)
10.24
NOTE: Evaluation period length in time depends on the length of
the eDRX_CONN cycle in use
7.19.4.3 Minimum requirement at transitions
When the UE transitions between any two of DRX, eDRX_CONN and non-DRX or when DRX or eDRX_CONN cycle
periodicity changes, for a duration of time equal to the evaluation period corresponding to the second mode after the
transition occurs, the UE shall use an evaluation period that is no less than the minimum of evaluation periods
corresponding to the first mode and the second mode. Subsequent to this duration, the UE shall use an evaluation period
corresponding to the second mode. This requirement shall be applied to both out-of-sync evaluation and in-sync
evaluation of the PCell.
7.19.5 Requirements for HD-FDD with CE mode B
The requirements defined in this subclause 7.19.5 for performing radio link monitoring are applicable for UE category
M1 defined in Section 3.6.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 176 ETSI TS 136 133 V14.3.0 (2017-04)
7.19.5.1 Minimum requirement when no DRX is used
The HD-FDD category M1 with CE mode B UE shall meet all applicable requirements specified in clause 7.19.4.1
under the following conditions
- at least 1 DL subframe per radio frame of PCell is available at the UE during Qin_CatM1 and Qout_CatM1 evaluation
periods.
7.19.5.2 Minimum requirement when DRX is used
When DRX is used for HD-FDD category M1 with CE mode B UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.5.2-1 will be
used.
When eDRX_CONN cycle is used for HD-FDD category M1 with CE mode B UEs, the Qout_CatM1 evaluation period
(TEvaluate_Qout_DRX_CatM1) and the Qin_CatM1 evaluation period (TEvaluate_Qin_DRX_CatM1) specified in Table 7.19.5.2-2 will be
used.
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qout_DRX_CatM1 [s] period becomes
worse than the threshold Qout_CatM1, Layer 1 of the UE shall send out-of-sync indication for the PCell to the higher layers
within TEvaluate_Qout_DRX_CatM1 [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync indications as
specified in TS 36.331 [2].
When the downlink radio link quality of the PCell estimated over the last TEvaluate_Qin_DRX_CatM1 [s] period becomes better
than the threshold Qin_CatM1, Layer 1 of the UE shall send in-sync indications for the PCell to the higher layers within
TEvaluate_Qin_DRX_CatM1 [s] evaluation period. A L3 filter shall be applied to the in-sync indications as specified in
TS 36.331 [2].
The out-of-sync and in-sync evaluations of the PCell shall be performed as specified in clause 4.2.1 in [3]. When DRX
is used, two successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length). When
eDRX_CONN is used, two successive indications from Layer 1 shall be separated by at least max(10 ms,
eDRX_CONN cycle length).
Upon start of T310 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link for recovery using
the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of
T310 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in
clause 5.3.11 in TS 36.331 [2].
Table 7.19.5.2-1: Qout_CatM1 and Qin_CatM1 Evaluation Period in DRX for HD-FDD UE category M1 with CE
mode B
DRX cycle length (s) TEvaluate_Qout_DRX_CatM1 and
TEvaluate_Qin_DRX_CatM1 (s) (DRX
cycles)
≤ [0.08] Non-DRX requirements in
clause 7.19.5.1 are applicable.
[0.08]< DRX cycle ≤[0.160] Note (40)
[0.160] < DRX cycle ≤ [0.320] Note (20)
[0.320] < DRX cycle ≤ 0.64 Note (10)
0.64 < DRX cycle ≤ 2.56 Note (5)
NOTE: Evaluation period length in time depends on the length of
the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 177 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.19.5.2-2: Qout_CatM1 and Qin_CatM1 evaluation period when eDRX_CONN cycle is configured for
HD-FDD UE category M1 with CE mode B
eDRX_CONN cycle length TEvaluate_Qout_DRX_CatM1 and
(s) TEvaluate_Qin_DRX_CatM1 (s)
(eDRX_CONN cycles)
2.56 < DRX cycle ≤ 10.24 Note (5)
NOTE: Evaluation period length in time depends on the length of
the eDRX_CONN cycle in use
7.19.5.3 Minimum requirement at transitions
The minimum requirements at transitions defined in clause 7.19.4.3 also apply for this section under the following
conditions:
- at least 1 DL subframe per radio frame of PCell is available at the UE during Qin_CatM1 and Qout_CatM1 evaluation
periods.8 UE Measurements Procedures in RRC_CONNECTED State
7.20 UE transmit timing for NB-IoT
7.20.1 Introduction
The Category NB1 UE shall have capability to follow the frame timing change of the connected eNode B. The uplink
frame transmission takes place ( N TA_Ref + N TA offset ) × Ts before the reception of the first detected path (in time) of the
corresponding downlink frame from the reference NB-IoT cell.
UE shall use the serving NB-IoT cell as the reference cell for deriving the UE transmit timing. UE initial transmit
timing accuracy, maximum amount of timing change in one adjustment, minimum and maximum adjustment rate are
defined in the following requirements.
7.20.2 Requirements
The UE initial transmission timing error shall be less than or equal to ±Te where the timing error limit value Te is
specified in Table 7.20.2-1. This requirement applies when it is the first transmission in a DRX cycle or the first
transmission in a repetition period (R>1) for NPUSCH and NPRACH, the first transmission after an uplink transmission
gap in a repetition period (R>1) for NPUSCH and NPRACH transmission. The reference point for the UE initial
transmit timing control requirement shall be the downlink timing of the serving NB-IoT cell minus
( N TA_Ref + N TA offset ) × Ts . The downlink timing is defined as the time when the first detected path (in time) of the
corresponding downlink frame is received from the serving NB-IoT cell. NTA_Ref for NPRACH is defined as 0.
( N TA_Ref + N TA offset ) (in Ts units) for other channels is the difference between UE transmission timing and the Downlink
timing immediately after when the last timing advance in clause 7.22 was applied. NTA_Ref for other channels is not
changed until next timing advance is received.
Table 7.20.2-1: Te Timing Error Limit
Downlink Bandwidth (MHz) Te_
0.18 [80*TS]
Note 1: TS is the basic timing unit defined in TS 36.211
When it is not the first transmission in a DRX cycle or there is no DRX cycle, and when it is the transmission for
NPUSCH the UE shall, when no repetitions are configured on the uplink or the repetition period is R=1, be capable of
changing the transmission timing according to the received downlink frame of the serving NB-IoT cell except when the
timing advance in clause 7.22 is applied such that the UE transmission timing error shall be less than or equal to ±Te,
where the timing error limit value Te is specified in Table 7.20.2-1.
When no repetition period is configured, or the configured repetition period is R=1, all adjustments made to the UE
uplink timing shall follow these rules:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 178 ETSI TS 136 133 V14.3.0 (2017-04)
1) The maximum amount of the magnitude of the timing change in one adjustment shall be 58.33*TS seconds.
2) The minimum aggregate adjustment rate shall be 7*TS per second.
3) The maximum aggregate adjustment rate shall be 58.33*TS per 200ms.
When a repetition period is configured on the uplink for which R>1, the UE shall not adjust the uplink transmission
timing autonomously during an ongoing repetition period other than at initial transmission as defined above.
7.21 UE timer accuracy for NB-IoT
7.21.1 Introduction
UE timers are used in different protocol entities to control the UE behaviour.
7.21.2 Requirements
For UE timers specified in TS 36.331 [2], UE shall comply with the timer accuracies according to Table 7.21.2-1.
The requirements are only related to the actual timing measurements internally in the UE. They do not include the
following:
- Inaccuracy in the start and stop conditions of a timer (e.g. UE reaction time to detect that start and stop
conditions of a timer is fulfilled), or
- Inaccuracies due to restrictions in observability of start and stop conditions of a UE timer (e.g. TTI alignment
when UE sends messages at timer expiry).
Table 7.21.2-1
Timer value [s] Accuracy
timer value < 4 ± 0.1s
timer value ≥ 4 ± 2.5%
7.22 Timing Advance for NB-IoT
7.22.1 Introduction
The timing advance is initiated from E-UTRAN with MAC message that implies and adjustment of the timing advance,
see TS 36.321 [17] clause 5.2.
7.22.2 Requirements
7.22.2.1 Timing Advance adjustment delay
UE shall adjust the timing of its uplink transmission timing at sub-frame n+12 for a timing advance command received
in sub-frame n. In case repetitions are used on the downlink, sub-frame n refers to the last subframe in the repetition
period in which the message containing the MAC control information was received. The UE shall not apply a TA
command during an uplink repetition period.
7.22.2.2 Timing Advance adjustment accuracy
The UE shall adjust the timing of its transmissions with a relative accuracy better than or equal to ±13.33* TS seconds
to the signalled timing advance value compared to the timing of preceding uplink transmission. The timing advance
command is expressed in multiples of 16* TS and is relative to the current uplink timing.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 179 ETSI TS 136 133 V14.3.0 (2017-04)
7.23 Radio Link Monitoring for Category NB1 UE
7.23.1 Introduction
The applicability of the requirements for performing radio link monitoring for Category NB1 UE in subclause 7.23 is
defined in Section 3.1.
The UE shall monitor the downlink link quality based on the narrowband reference signal in order to detect the
downlink radio link quality of the NB-IoT cell as specified in [3].
7.23.2 Requirements for HD-FDD Category NB1 UE
The requirements defined in this subclause 7.23.2 for performing radio link monitoring are applicable for Category NB1
UE defined in Section 3.1.
The UE shall meet all applicable requirements specified in clause 7.23.2 under the following condition:
- at least 1 DL subframe per radio frame of serving NB-IoT cell is available at the UE during Qout_NB-IoT and
Qin_NB-IoT evaluation periods.
The UE shall estimate the downlink radio link quality and compare it to the thresholds Qout_NB-IoT and Qin_NB-IoT for the
purpose of monitoring downlink radio link quality of the NB-IoT cell.
The threshold Qout_NB-IoT is defined as the level at which the downlink radio link cannot be reliably received and shall
correspond to 10% block error rate of a hypothetical NPDCCH transmission with transmission parameters specified in
Table 7.23.2-1.
The threshold Qin_NB-IoT is defined as the level at which the downlink radio link quality can be significantly more
reliably received than at Qout_NB-IoT and shall correspond to 2% block error rate of a hypothetical NPDCCH transmission
with transmission parameters specified in Table 7.23.2-1.
Table 7.23.2-1 NPDCCH transmission parameters for out-of-sync and in-sync for Category NB1 UE
Attribute Out-of-sync In-sync
DCI format Format N1 Format N1
Number of information bits 23 bits 23 bits
System Bandwidth 200kHz 200kHz
Antenna configuration 2x1 2x1
Maximum NPDCCH Repetition level RmaxNote1 Rmax/4 Note1
Aggregation level 2 2
DRX OFF OFF
Deployment mode In-band In-band
NOTE 1: Rmax is a configurable parameter defined in TS 36.331[2].
7.23.2.1 Minimum requirement when no DRX is used
When the downlink radio link quality of the NB-IoT cell estimated over the last TEvaluate_Qout_NB-IoT period becomes
worse than the threshold Qout_NB-IoT, Layer 1 of the UE shall send an out-of-sync indication for the NB-IoT cell to the
higher layers within TEvaluate_Qout_NB-IoT Qout_NB-IoT evaluation period. A Layer 3 filter shall be applied to the out-of-sync
indications as specified in TS 36.331 [2].
When the downlink radio link quality of the NB-IoT cell estimated over the last TEvaluate_Qin_NB-IoT period becomes better
than the threshold Qin_NB-IoT, Layer 1 of the UE shall send an in-sync indication for the NB-IoT cell to the higher layers
within TEvaluate_Qin_NB-IoT Qin_NB-IoT evaluation period. A L3 filter shall be applied to the in-sync indications as specified
in TS 36.331 [2].
The out-of-sync and in-sync evaluations of the NB-IoT cell shall be performed as specified in clause 4.2.1 in [3]. Two
successive indications from Layer 1 shall be separated by at least 10ms.
The transmitter power of the UE shall be turned off within 40ms after expiry of T310 timer as specified in clause 5.3.11
in TS 36.331 [2]. The following table 7.23.2.1-1 defines the TEvaluate_Qout_NB-IoT and TEvaluate_Qin_NB-IoT.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 180 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.23.2.1-1 Qout and Qin Evaluation Period in non-DRX for HD-FDD Category NB1 UE
Configured TEvaluate_Qout_NB-IoT TEvaluate_Qin_NB-IoT
NPDCCH Rmax
Rmax ≤ 64 400ms 200ms
Rmax> 64 4000ms 2000ms
7.23.2.2 Minimum requirement when DRX is used
When DRX is used for FD-FDD and TDD Category NB1 UE UEs, the Qout_NB-IoT evaluation period
(TEvaluate_Qout_DRX_NB-IoT) and the Qin_NB-IoT evaluation period (TEvaluate_Qin_DRX_NB-IoT) is specified in Table 7.23.2.2-1 will
be used.
When the downlink radio link quality of the NB-IoT cell estimated over the last TEvaluate_Qout_DRX_NB-IoT [s] period
becomes worse than the threshold Qout_NB-IoT, Layer 1 of the UE shall send out-of-sync indication for the NB-IoT cell to
the higher layers within TEvaluate_Qout_DRX_NB-IoT [s] evaluation period. A Layer 3 filter shall be applied to the out-of-sync
indications as specified in TS 36.331 [2].
When the downlink radio link quality of the NB-IoT cell estimated over the last TEvaluate_Qin_DRX_NB-IoT [s] period
becomes better than the threshold Qin_NB-IoT, Layer 1 of the UE shall send in-sync indications for the NB-IoT cell to the
higher layers within TEvaluate_Qin_DRX_NB-IoT [s] evaluation period. A L3 filter shall be applied to the in-sync indications as
specified in TS 36.331 [2].
The out-of-sync and in-sync evaluations of the NB-IoT cell shall be performed as specified in clause 4.2.1 in [3]. Two
successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length).
Upon start of T310 timer as specified in clause 5.3.11 in TS 36.331 [2], the UE shall monitor the link for recovery using
the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of
T310 timer.
The transmitter power of the UE shall be turned off within 40 ms after expiry of T310 timer as specified in clause
5.3.11 in TS 36.331 [2].
Table 7.23.2.2-1: Qout and Qin Evaluation Period in DRX for HD-FDD Category NB1 UE
DRX cycle length (s) TEvaluate_Qout_DRX_NB-IoT and TEvaluate_Qin_DRX_NB-IoT (s)
DRX cycles for Rmax ≤ 64 DRX cycles for Rmax > 64
0.256 < DRX cycle ≤ 1.024 Note 1 (20) Note 1 (40)
1.024 < DRX cycle ≤ 3.072 Note 1 (10) Note 1 (20)
4.096 < DRX cycle ≤ 9.216 Note 1 (5) Note 1 (10)
NOTE 1: Evaluation period length in time depends on the length of the DRX cycle in use
7.23.2.3 Minimum requirement at transitions
The out-of-sync and in-sync evaluations of the NB-IoT cell shall be performed as specified in clause 4.2.1 in [3]. Two
successive indications from Layer 1 shall be separated by at least max(10ms, DRX_cycle_length).
When the UE transitions between DRX and non-DRX or when DRX cycle periodicity changes, for a duration of time
equal to the evaluation period corresponding to the second mode after the transition occurs, the UE shall use an
evaluation period that is no less than the minimum of evaluation periods corresponding to the first mode and the second
mode. Subsequent to this duration, the UE shall use an evaluation period corresponding to the second mode. This
requirement shall be applied to both out-of-sync evaluation and in-sync evaluation of the NB-IoT cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 181 ETSI TS 136 133 V14.3.0 (2017-04)
7.24 UE transmit timing for Category M1
7.24.1 Introduction
The Category M1 UE shall have the capability to follow the frame timing change of the connected eNode B. The uplink
frame transmission takes place ( N TA + N TA offset ) × Ts before the reception of the first detected path (in time) of the
corresponding downlink frame from the reference cell.
The UE shall use the serving cell as the reference cell for deriving the UE transmit timing. UE initial transmit timing
accuracy, maximum amount of timing change in one adjustment, minimum and maximum adjustment rate are defined
in the following requirements.
7.24.2 Requirements
The UE initial transmission timing error shall be less than or equal to ±Te where the timing error limit value Te is
specified in Table 7.24.2-1. This requirement applies when it is the first transmission in a DRX cycle, eDRX_CONN
cycle, or the first transmission in a repetition period (R>1) for PUCCH, PUSCH, and SRS, or the first transmission after
an uplink transmission gap in a repetition period (R>1) for PUCCH or PUSCH, or it is the PRACH transmission. The
reference point for the UE initial transmit timing control requirement shall be the downlink timing of the serving cell
minus ( N TA_Ref + N TA offset ) × Ts . The downlink timing is defined as the time when the first detected path (in time) of the
corresponding downlink frame is received from the serving cell. NTA_Ref for PRACH is defined as 0. ( N TA_Ref + N TA offset )
(in Ts units) for other channels is the difference between UE transmission timing and the Downlink timing immediately
after when the last timing advance in clause 7.3 was applied. NTA_Ref for other channels is not changed until the next
timing advance is received.
Table 7.24.2-1: Te Timing Error Limit
CE Mode Te_
A 24*TS
B 48*Ts
NOTE 1: TS is the basic timing unit defined in TS 36.211.
NOTE 2: This requirement applies regardless of the downlink carrier
bandwidth.
When it is not the first transmission in a DRX or eDRX_CONN cycle or there is no DRX or no eDRX_CONN cycle,
and when it is the transmission for PUCCH, PUSCH and SRS transmission, the UE shall, when no repetitions are
configured on the uplink or the repetition period is R=1, be capable of changing the transmission timing according to
the received downlink frame of the serving cell except when the timing advance in clause 7.3 is applied such that the
UE transmission timing error shall be less than or equal to ±Te where the timing error limit value Te is specified in
Table 7.24.2-1.
When no repetition period is configured, or the configured repetition period is R=1, all adjustments made to the UE
uplink timing shall follow these rules:
1) The maximum amount of the magnitude of the timing change in one adjustment shall be Tq seconds.
2) The minimum aggregate adjustment rate shall be 7*TS per second.
3) The maximum aggregate adjustment rate shall be Tq per 200ms.
where the maximum autonomous time adjustment step Tq is specified in Table 7.24.2-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 182 ETSI TS 136 133 V14.3.0 (2017-04)
Table 7.24.2-2: Tq Maximum Autonomous Time Adjustment Step
CE Mode Tq_
A 17.5*TS
B 17.5*Ts
NOTE 1: TS is the basic timing unit defined in TS 36.211.
NOTE 2: This requirement applies regardless of the downlink carrier
bandwidth.
When a repetition period is configured on the uplink for which R>1, the UE shall not adjust the uplink transmission
timing autonomously during an ongoing repetition period other than at initial transmission as defined above.
7.25 Cell phase synchronization accuracy for MBMS services
(FDD)
7.25.1 Definition
Cell phase synchronization accuracy is defined as the maximum absolute deviation in frame start timing between any
pair of cells that have overlapping coverage areas in the same MBSFN area.
7.25.2 Minimum requirements
For eNodeB capable of supporting MBMS services, the cell phase synchronization accuracy measured at BS antenna
connectors shall be less than or equal to 5µs assuming 16.67µs CP length.
8 UE Measurements Procedures in
RRC_CONNECTED State
8.1 General Measurement Requirements
8.1.1 Introduction
This clause contains requirements on the UE regarding measurement reporting in RRC_CONNECTED state. The
requirements are split in E-UTRA intra frequency, E-UTRA inter frequency, Inter-RAT UTRA FDD, UTRA TDD and
GSM measurements. These measurements may be used by the E-UTRAN, e.g. for handover decisions. The
measurement quantities are defined in [4], the measurement model is defined in [22] and measurement accuracies are
specified in clause 9. Control of measurement reporting is specified in TS 36.331 [2].
When the UE is provided with IDC solution, the UE shall also perform RRM measurements and meet the corresponding
requirements in clause 8.
In the requirements of Section 8.1 for the UE capable of CA and the UE configured with up to four SCells, the
applicable exceptions for side conditions are specified in Annex B, Sections B.4.2 and B.4.3, respectively.
In the requirements of Section 8.1 for the UE capable of DC and the UE configured with one PSCell, the applicable
exceptions for side conditions are specified in Annex B, Sections B.4.2 and B.4.3, respectively.
The requirements in Section 9 are applicable for a UE performing measurements according to Section 8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 183 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2 Requirements
8.1.2.1 UE measurement capability
If the UE requires measurement gaps to identify and measure inter-frequency and/or inter-RAT cells, in order for the
requirements in the following subsections to apply the E-UTRAN must provide a single measurement gap pattern with
constant gap duration for concurrent monitoring of all frequency layers and RATs.
During the measurement gaps the UE:
- shall not transmit any data
- is not expected to tune its receiver on any of the E-UTRAN carrier frequencies of PCell and any SCell.
- is not expected to tune its receiver on any of the E-UTRAN carrier frequencies of PCell, PSCell, and SCell.
If the UE supporting dual connectivity is configured with PSCell, during the total interruption time as shown in Figure
8.1.2.1-1, the UE shall not transmit and receive any data in SCG.
In the uplink subframe occurring immediately after the measurement gap,
- if the following conditions are met then it is up to UE implementation whether or not the UE can transmit data:
- all the serving cells belong to E-UTRAN TDD;
- if the subframe occurring immediately before the measurement gap is an uplink subframe.
- Otherwise the UE shall not transmit any data.
In determining the above UE behaviour in the uplink subframe occurring immediately after the measurement gap the
UE shall treat a special subframe as an uplink subframe if the special subframe occurs immediately before the
measurement gap, Inter-frequency and inter-RAT measurement requirements within this clause rely on the UE being
configured with one measurement gap pattern unless the UE has signaled that it is capable of conducting such
measurements without gaps. UEs shall only support those measurement gap patterns listed in Table 8.1.2.1-1 that are
relevant to its measurement capabilities.
ProSe capable UE is allowed to perform ProSe transmissions during the measurement gaps that are not used for
measurements if the requirements specified in section 8 for inter-frequency and inter-RAT measurements are fulfilled.
Table 8.1.2.1-1: Gap Pattern Configurations supported by the UE
Gap Pattern MeasurementGap Measurement Gap Minimum available time Measurement Purpose
Id Length (MGL, ms) Repetition Period for inter-frequency and
(MGRP, ms) inter-RAT measurements
during 480ms period
(Tinter1, ms)
0 6 40 60 Inter-Frequency E-UTRAN
FDD and TDD, UTRAN
FDD, GERAN, LCR TDD,
HRPD, CDMA2000 1x
1 6 80 30 Inter-Frequency E-UTRAN
FDD and TDD, UTRAN
FDD, GERAN, LCR TDD,
HRPD, CDMA2000 1x
NOTE 1: When inter-frequency RSTD measurements are configured and the UE requires measurement gaps for
performing such measurements, only Gap Pattern 0 can be used. For defining the inter-frequency and
inter-RAT requirements Tinter1=30ms shall be assumed.
NOTE 2: A measurement gap starts at the end of the latest subframe occurring immediately before the
measurement gap among MCG serving cells subframes.
NOTE 3: MGL is the time from start of tuning to end of retuning, which is aligned between MCG and SCG.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 184 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE 4: The total interruption time on SCG is 6 subframes for synchronous dual connectivity, and the total
interruption time on SCG is 7 subframes for asyncrhonous dual connectivity. As shown in Figure 8.1.2.1-
1, MCG subframes from i+1 to i+6 are included in total interruption time together with SCG subframes
from j+1 to j+6 for synchronous dual connectivity and j+1 to j+7 for asyncrhonous dual connectivity.
NOTE 5: For asynchronous dual connectivity as shown in Figure 8.1.2.1-1 (b), subframe j is regarded as the
subframe occurring immediately before the measurement gap for SCG, similarly, subframe j+8 is
regarded as the subframe occurring immediately after the measurement gap for SCG.
Figure 8.1.2.1-1: Measurement GAP and total interruption time on MCG and SCG
A UE that is capable of identifying and measuring inter-frequency and/or inter-RAT cells without gaps shall follow
requirements as if Gap Pattern Id #0 had been used and the minimum available time Tinter1 of 60 ms shall be assumed
for the corresponding requirements.
If the UE supporting E-UTRA carrier aggregation when configured with up to four SCCs is performing measurements
on cells on PCC, inter-frequency measurements, or inter-RAT measurements, and interruption occurs on PCell or any
activated SCell or both due to measurements performed on cells on an SCC with a deactivated SCell according to
section 8.3, then the UE shall meet the requirements specified for each measurement in Section 8 and Section 9.
If the UE supporting E-UTRA dual connectivity when configured with a PSCell is performing measurements on cells
on PCC, inter-frequency measurements, or inter-RAT measurements, then the UE shall meet the requirements specified
for each measurement in Section 8 and Section 9.
A UE which indicate support for Increased UE carrier monitoring E-UTRA according to the capabilities in [2, 31] and
which is capable of identifying and measuring inter-frequency and/or inter-RAT cells without gaps, shall be able to
monitor maximum number of layers as defined in 8.1.2.1.1.1a, and apply the MeasScaleFactor [2] defining the
relaxation to the requirements for the configured carriers according to section 8.1.2.1.1a.
8.1.2.1.1 Monitoring of multiple layers using gaps
When monitoring of multiple inter-frequency E-UTRAN and inter-RAT (UTRAN, GSM) using gaps (or without using
gaps provided the UE supports such capability) is configured, the UE shall be capable of performing one measurement
of the configured measurement type (RSRP, RSRQ, RSTD, UTRAN TDD P-CCPCH RSCP, UTRAN FDD CPICH
measurements, GSM carrier RSSI, etc.) of detected cells on all the layers
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 185 ETSI TS 136 133 V14.3.0 (2017-04)
The effective total number of frequencies excluding the frequencies of the PCell, SCells, and PSCell being monitored is
Nfreq, which is defined as:
Nfreq = Nfreq, E-UTRA + Nfreq, UTRA + Mgsm + Nfreq, cdma2000 + Nfreq, HRPD
where
Nfreq, E-UTRA is the number of E-UTRA carriers being monitored (FDD and TDD)
Nfreq, UTRA is the number of UTRA carriers being monitored (FDD and TDD)
MGSM is an integer which is a function of the number of GSM carriers on which measurements are being performed.
MGSM is equal to 0 if no GSM carrier is being monitored. For a MGRP of 40 ms, MGSM is equal to 1 if cells on up to 32
GSM carriers are being measured. For a MGRP of 80 ms, MGSM is equal to ceil(Ncarriers,GSM /20) where Ncarriers,GSM is the
number of GSM carriers on which cells are being measured.
Nfreq, cdma2000 is the number of cdma2000 1x carriers being monitored.
Nfreq, HRPD is the number of HRPD carriers being monitored.8.1.2.1.1.1 Maximum allowed layers for
multiple monitoring
The UE shall be capable of monitoring at least per RAT group:
- Depending on UE capability, 3 FDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 1 FDD E-UTRA inter-frequency carrier for RSTD measurements, and
- Depending on UE capability, 3 TDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 1 TDD E-UTRA inter-frequency carrier for RSTD measurements, and
- Depending on UE capability, 3 FDD UTRA carriers, and
- Depending on UE capability, 3 TDD UTRA carriers, and
- Depending on UE capability, 32 GSM carriers (one GSM layer corresponds to 32 carriers), and
- Depending on UE capability, 5 cdma2000 1x carriers, and
- Depending on UE capability, 5 HRPD carriers
In addition to the requirements defined above, the UE shall be capable of monitoring a total of at least 7 effective carrier
frequency layers comprising of any above defined combination of E-UTRA FDD, E-UTRA TDD, UTRA FDD, UTRA
TDD, GSM (one GSM layer corresponds to 32 carriers), cdma2000 1x and HRPD layers.
8.1.2.1.1.1a Maximum allowed layers for multiple monitoring (Increased UE carrier monitoring)
UE which indicate support for Increased UE carrier monitoring E-UTRA according to the capabilities in [2,31] shall be
capable of monitoring at least
- Depending on UE capability, 8 FDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 8 TDD E-UTRA inter-frequency carriers
UE which indicate support for increased UE carrier monitoring UTRA according to the capabilities in [2,31] shall be
capable of monitoring at least
- Depending on UE capability, 6 FDD UTRA carriers, and
- Depending on UE capability, 7 TDD UTRA carriers, and
In addition to the requirements defined above, the UE which indicate support for Increased UE carrier monitoring E-
UTRA or increased UE carrier monitoring UTRA according to the capabilities in [2,31]shall be capable of monitoring a
total of at least 12 carrier frequency layers comprising of any above defined combination of E-UTRA FDD, E-UTRA
TDD, UTRA FDD, UTRA TDD, GSM (one GSM layer corresponds to 32 carriers), cdma2000 1x and HRPD layers
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 186 ETSI TS 136 133 V14.3.0 (2017-04)
The minimum performance requirements for a UE which does not indicate support for Increased UE carrier monitoring
E-UTRA [2,31] are calculated assuming all E-UTRA carriers which the UE is required to monitor, are having normal
performance, i.e. Nfreq, E-UTRA,reduced =0. The minimum performance requirements for a UE which does not indicate
support for Increased UE carrier monitoring UTRA [2,31] are calculated assuming all UTRA carriers which the UE is
required to monitor, are having normal performance, i.e. Nfreq, UTRA,reduced =0. Capabilities for number of carriers to
monitor for UE which do not support increased carrier monitoring E-UTRA or increased carrier monitoring UTRA are
specified in section 8.1.2.1.1.1. A UE which do not indicate support for Increased UE carrier monitoring E-UTRA or
UTRAN [2,31] does not have any reduced performance carrier requirements and Kn=1.
8.1.2.1.1a Monitoring of multiple layers using gaps (Increased UE carrier monitoring)
For UE which support increased carrier monitoring E-UTRA or increased carrier monitoring UTRA, the measurement
performance for different carriers may be configured by higher layers to be either normal or reduced performance. A
measurement scaling factor, MeasScaleFactor [2], defining the relaxation to be applied to the requirements for carriers
measured with reduced measurement performance is signalled by higher layers and has the possible settings shown in
table 8.1.2.1.1-1.
Table 8.1.2.1.1-1: Measurement Scaling factor Configurations supported by the UE
MeasScaleFactor Kn Kr
information
element settting
sf-EUTRA-cf1 8 8/7 8
sf-EUTRA-cf2 16 16/15 16
If no reduced performance group carrier is configured, the UE shall consider all carriers to have normal performance
If no MeasScaleFactor is configured, a UE indicating support for increased carrier monitoring E-UTRA or increased
carrier monitoring UTRA shall monitor at least the number of carriers specified in section 8.1.2.1.1.1 and is not required
to monitor the increased number of carriers specified in section 8.1.2.1.1.1a.
The following definitions are used in the performance requirements:
Nfreq =Nfreq,n + Nfreq,r
Where:
Nfreq,n = Nfreq, E-UTRA,normal + Nfreq, UTRA, normal + Mgsm + Nfreq, cdma2000 + Nfreq, HRPD : Total number of interfrequency
carriers to be monitored with normal measurement performance
Nfreq,r = Nfreq, E-UTRA,reduced + Nfreq, UTRA, reduced : Total number of interfrequency carriers to be monitored with reduced
measurement performance
Where :
Nfreq, E-UTRA,normal : Number of interfrequency carriers to be monitored with normal performance
Nfreq, E-UTRA,normal,FDD : Number of interfrequency FDD carriers to be monitored with normal performance
Nfreq, E-UTRA,normal,TDD : Number of interfrequency TDD carriers to be monitored with normal performance
Nfreq, E-UTRA,reduced : Number of interfrequency carriers to be monitored with reduced performance
Nfreq, UTRA,normal : Number of UTRA carriers (FDD and TDD) to be monitored with normal performance
Nfreq, E-UTRA,normal,FDD : Number of interfrequency FDD carriers to be monitored with normal performance
Nfreq, E-UTRA,normal,TDD : Number of interfrequency TDD carriers to be monitored with normal performance
Nfreq, UTRA,reduced : Number of UTRA carriers (FDD and TDD) to be monitored with reduced performance
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 187 ETSI TS 136 133 V14.3.0 (2017-04)
For interfrequency carriers, if Nfreq, E-UTRA,reduced is not equal to zero then Kn and Kr are as shown in table 8.1.2.1.1-1.
Otherwise Kn=1 and all interfrequency layers have normal performance.
For UTRAN carriers, if Nfreq, UTRA,reduced is not equal to zero then Kn and Kr are as shown in table 8.1.2.1.1-1.
Otherwise Kn=1 and all UTRA frequency layers have normal performance.
The minimum performance requirements for a UE which indicates support for Increased UE carrier monitoring E-
UTRA [2, 31] are calculated as defined in sections 8.1.2.3.1 and 8.1.2.3.2 provided that Nfreq, E-UTRA,normal ≤3 for a UE
capable of either FDD E-UTRA carrier monitoring or TDD E-UTRA carrier monitoring or Nfreq, E-UTRA,normal ≤6 for a UE
capable of both FDD and TDD E-UTRA carrier monitoring provided Nfreq, E-UTRA,normal,FDD ≤3 E-UTRA carriers and Nfreq,
E-UTRA,normal,TDD ≤3 TDD E-UTRA carriers or if Nfreq,n= Nfreq. The minimum performance requirements for a UE which
indicates support for Increased UE carrier monitoring UTRA [2, 31] are calculated as defined in sections 8.1.2.4.1,
8.1.2.4.3, 8.1.2.4.7 and 8.1.2.4.13 provided that Nfreq, UTRA,normal ≤3 for UE capable of either FDD UTRA carrier
monitoring or TDD UTRA carrier monitoring or Nfreq, UTRA,normal ≤6 for a UE capable of both FDD and TDD UTRA
carrier monitoring provided Nfreq, UTRA,normal,FDD ≤3 FDD UTRA carriers and Nfreq, UTRA,normal,TDD ≤3 TDD UTRA carriers
or if Nfreq,n= Nfreq. Capabilities for number of carriers to monitor for a UE which supports Increased carrier monitoring
E-UTRA or Increased carrier monitoring UTRA are specified in section 8.1.2.1.1.1a.
8.1.2.2 E-UTRAN intra frequency measurements
The UE shall be able to identify new intra-frequency cells and perform RSRP, RSRQ, and RS-SINR measurements of
identified intra-frequency cells without an explicit intra-frequency neighbour cell list containing physical layer cell
identities. During the RRC_CONNECTED state the UE shall continuously measure identified intra frequency cells and
additionally search for and identify new intra frequency cells.
8.1.2.2.1 E-UTRAN FDD intra frequency measurements
8.1.2.2.1.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
TMeasurement_Period, Intra
Tidentify intra = Tbasic_identify_E -UTRA _ FDD, intra ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_FDD, intra is 800 ms
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.5.1 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Section 9.1.17.2.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band.
TIntra : This is the minimum time that is available for intra frequency measurements, during the measurement period with
an arbitrarily chosen timing. Time is assumed to be available for performing intra frequency measurements whenever
the receiver is guaranteed to be active on the intra frequency carrier.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period Intra. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is 200 ms. When no
measurement gaps are activated, the UE shall be capable of performing RSRP, RSRQ, and RS-SINR measurements for
8 identified-intra-frequency cells, and the UE physical layer shall be capable of reporting measurements to higher layers
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 188 ETSI TS 136 133 V14.3.0 (2017-04)
with the measurement period of 200 ms. When measurement gaps are activated the UE shall be capable of performing
measurements for at least Ymeasurement intra cells , where Ymeasurement intra is defined in the following equation. If the UE has
identified more than Ymeasurement intra cells, the UE shall perform measurements of at least 8 identified intra- frequency
cells but the reporting rate of RSRP, RSRQ, and RS-SINR measurements of cells from UE physical layer to higher
layers may be decreased.
⎧⎪ TIntra ⎫⎪
Ymeasurement intra = Floor ⎨ X basic measurement FDD ⋅ ⎬ cells
⎪⎩ TMeasurement_Period, Intra ⎪⎭
where
Xbasic measurement FDD = 8 (cells),
TMeasurement_Period, Intra = 200 ms is the measurement period for intra frequency RSRP, RSRQ, and RS-SINR
measurements.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.2.1 and 9.1.2.2, the
RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.5.1, and RS-SINR
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.17.2.1.
8.1.2.2.1.1.1 Measurement Reporting Requirements
8.1.2.2.1.1.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
8.1.2.2.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.2.1.1.1.3.
8.1.2.2.1.1.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra defined in
Clause 8.1.2.2.1.1. When L3 filtering is used or IDC autonomous denial is configured or the UE is performing reception
and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra defined in clause 8.1.2.2.1.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period, Intra provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or the UE is performing reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct
Communication, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 189 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.2.1.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra as
shown in table 8.1.2.2.1.2-1. When eDRX_CONN is in use the UE shall be able to identify a new detectable FDD intra
frequency cell within Tidentify_intra as shown in table 8.1.2.2.1.2-1A. When highSpeedEnhancedMeasFlag is configured
the UE shall be able to identify a new detectable FDD intra-frequency cell within Tidentify_intra as shown in table
8.1.2.2.1.2-1B.
Table 8.1.2.2.1.2-1: Requirement to identify a newly detectable FDD intrafrequency cell
DRX cycle Tidentify_intra (s)
length (s) (DRX cycles)
≤0.04 0.8 (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use.
Note2: Time depends upon the
DRX cycle in use.
Table 8.1.2.2.1.2-1A: Requirement to identify a newly detectable FDD intra-frequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note(20)
Note: Time depends upon the eDRX_CONN cycle in use
Table 8.1.2.2.1.2-1B: Requirement to identify a newly detectable FDD intrafrequency cell for UE
configured with highSpeedEnhancedMeasFlag
DRX cycle length (s) Tidentify_intra (s) (DRX
cycles)
≤0.04 0.8 (Note1)
0.04<DRX-cycle≤0.08 Note2(15)
0.08<DRX-cycle≤1.28 Note2(10)
1.28<DRX-cycle≤2.56 Note2(20)
Note1: Number of DRX cycle depends upon
the DRX cycle in use.
Note2: Time depends upon the DRX cycle in
use.
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.5.1 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Section 9.1.17.2.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band.
When DRX is used in the RRC_CONNECTED state the measurement period for intra frequency measurements is
Tmeasure_intra as shown in table 8.1.2.2.1.2-2. When eDRX_CONN is used in the RRC_CONNECTED state the
measurement period for intra frequency measurements is Tmeasure_intra as shown in table 8.1.2.2.1.2-3. When
highSpeedEnhancedMeasFlag is configured in the RRC_CONNECTED state the measurement period for intra
frequency measurements is Tmeasure_intra as shown in table 8.1.2.2.1.2-4. The UE shall be capable of performing RSRP,
RSRQ, and RS-SINR measurements for 8 identified-intra-frequency cells, and the UE physical layer shall be capable of
reporting measurements to higher layers with the measurement period of Tmeasure_intra.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 190 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.2.1.2-2: Requirement to measure FDD intrafrequency cells
DRX cycle Tmeasure_intra (s)
length (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use.
Note2: Time depends upon the
DRX cycle in use.
Table 8.1.2.2.1.2-3: Requirement to measure FDD intra-frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra (s) (eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use
Table 8.1.2.2.1.2-4: Requirement to measure FDD intrafrequency cells for UE configured with
highSpeedEnhancedMeasFlag
DRX cycle length (s) Tmeasure_intra (s) (DRX
cycles)
≤0.04 0.2 (Note1)
0.04<DRX-cycle≤0.08 Note2 (4)
0.08<DRX-cycle≤1.28 Note2 (3)
1.28<DRX-cycle≤2.56 Note2 (5)
Note1: Number of DRX cycle depends upon
the DRX cycle in use.
Note2: Time depends upon the DRX cycle
in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.2.1 and 9.1.2.2, the
RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.5.1, and RS-SINR
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.17.2.1.
8.1.2.2.1.2.1 Measurement Reporting Requirements
8.1.2.2.1.2.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
8.1.2.2.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.2.1.2.1.3.
8.1.2.2.1.2.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 191 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra defined in
Clause 8.1.2.2.1.2. When L3 filtering is used or IDC autonomous denial is configured or the UE is performing reception
and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra defined in clause 8.1.2.2.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra provided the timing to that cell has not changed
more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or the UE is performing reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct
Communication, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.1.2.2.2 E-UTRAN TDD intra frequency measurements
8.1.2.2.2.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
TMeasurement Period, Intra
Tidentify intra = Tbasic identify E −UTRA _ TDD, intra ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_TDD, intra is 800 ms
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.5.1 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Section 9.1.17.2.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band.
TIntra : This is the minimum time that is available for intra frequency measurements, during the measurement period with
an arbitrarily chosen timing. Time is assumed to be available for performing intra frequency measurements whenever
the receiver is guaranteed to be active on the intra frequency carrier.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period Intra. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is 200 ms. When no
measurement gaps are activated, the UE shall be capable of performing RSRP, RSRQ, and RS-SINR measurements for
8 identified-intra-frequency cells, and the UE physical layer shall be capable of reporting measurements to higher layers
with the measurement period of 200 ms. When measurement gaps are activated the UE shall be capable of performing
measurements for at least Ymeasurement intra cells , where Ymeasurement intra is defined in the following equation. If the UE has
identified more than Ymeasurement intra cells, the UE shall perform measurements of at least 8 identified intra-frequency
cells but the reporting rate of RSRP, RSRQ, and RS-SINR measurements of cells from UE physical layer to higher
layers may be decreased.
⎧⎪ TIntra ⎫⎪
Ymeasurement intra = Floor ⎨ X basic measurement TDD ⋅ ⎬ cells
⎪⎩ TMeasurement_Period, Intra ⎪⎭
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 192 ETSI TS 136 133 V14.3.0 (2017-04)
where
Xbasic measurement TDD = 8 (cells),
TMeasurement_Period Intra = 200 ms is the measurement period for intra frequency RSRP, RSRQ, and RS-SINR
measurements.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.2.1 and 9.1.2.2, the
RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.5.1, and RS-SINR
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.17.2.1.
8.1.2.2.2.1.1 Measurement Reporting Requirements
8.1.2.2.2.1.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
8.1.2.2.2.1.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.2.2.1.1.3.
8.1.2.2.2.1.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra defined in
Clause 8.1.2.2.2.1. When L3 filtering is used or IDC autonomous denial is configured or the UE is performing reception
and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra defined in clause 8.1.2.2.2.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period Intra provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or the UE is performing reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct
Communication, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.1.2.2.2.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within Tidentify_intra as
shown in table 8.1.2.2.2.2-1. When eDRX_CONN is in use, the UE shall be able to identify a new detectable TDD intra
frequency cell within Tidentify_intra as shown in table 8.1.2.2.2.2-1A. When highSpeedEnhancedMeasFlag is configured
the UE shall be able to identify a new detectable TDD intra-frequency cell within Tidentify_intra as shown in table
8.1.2.2.2.2-1B.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 193 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.2.2.2-1: Requirement to identify a newly detectable TDD intrafrequency cell
DRX cycle Tidentify_intra (s)
length (s) (DRX cycles)
≤0.04 0.8 (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use.
Note2: Time depends upon the
DRX cycle in use.
Table 8.1.2.2.2.2-1A: Requirement to identify a newly detectable TDD intra-frequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra (s) (eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note(20)
Note: Time depends upon the eDRX_CONN cycle in use
Table 8.1.2.2.2.2-1B: Requirement to identify a newly detectable TDD intrafrequency cell for UE
configured with highSpeedEnhancedMeasFlag
DRX cycle length (s) Tidentify_intra (s)
(DRX cycles)
≤0.04 0.8 (Note1)
0.04<DRX-cycle≤0.08 Note2(15)
0.08<DRX-cycle≤1.28 Note2(10)
1.28<DRX-cycle≤2.56 Note2(20)
Note1: Number of DRX cycle depends
upon the DRX cycle in use.
Note2: Time depends upon the DRX
cycle in use.
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.2.1 and 9.1.2.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.5.1 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Clause 9.1.17.2.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band.
When DRX is in use in the RRC_CONNECTED state the measurement period for intra frequency measurements is
Tmeasure_intra as shown in table 8.1.2.2.2.2-2. When eDRX_CONN is in use in the RRC_CONNECTED state, the
measurement period for intra frequency measurements is Tmeasure_intra as shown in table 8.1.2.2.2.2-3. When
highSpeedEnhancedMeasFlag is configured in the RRC_CONNECTED state the measurement period for intra
frequency measurements is Tmeasure_intra as shown in table 8.1.2.2.2.2-4. The UE shall be capable of performing RSRP,
RSRQ, and RS-SINR measurements for 8 identified intra-frequency cells and the UE physical layer shall be capable of
reporting measurements to higher layers with the measurement period of Tmeasure_intra.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 194 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.2.2.2-2: Requirement to measure TDD intra frequency cells
DRX cycle Tmeasure_intra (s)
length (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use.
Note2: Time depends upon the
DRX cycle in use.
Table 8.1.2.2.2.2-3: Requirement to measure TDD intra-frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra (s) (eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use.
Table 8.1.2.2.2.2-4: Requirement to measure TDD intrafrequency cells for UE configured with
highSpeedEnhancedMeasFlag
DRX cycle length (s) Tmeasure_intra (s)
(DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX-cycle≤0.08 Note2 (4)
0.08<DRX-cycle≤1.28 Note2 (3)
1.28<DRX-cycle≤2.56 Note2 (5)
Note1: Number of DRX cycle depends upon
the DRX cycle in use.
Note2: Time depends upon the DRX cycle
in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.2.1 and 9.1.2.2, the
RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.5.1, and the RS-SINR
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.17.2.1.
8.1.2.2.2.2.1 Measurement Reporting Requirements
8.1.2.2.2.2.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
8.1.2.2.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.2.2.2.1.3.
8.1.2.2.2.2.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.1, 9.1.2.2, 9.1.5.1, and 9.1.17.2.1, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 195 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra defined in
Clause 8.1.2.2.2.2. When L3 filtering is used or IDC autonomous denial is configured or the UE is performing reception
and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra defined in clause 8.1.2.2.2.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra provided the timing to that cell has not changed
more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or the UE is performing reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct
Communication, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.1.2.2.3 E-UTRAN FDD intra frequency measurements with autonomous gaps
8.1.2.2.3.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify
and report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps
in downlink reception and uplink transmission for receiving MIB and SIB1 message according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If
autonomous gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or
eDRX_CONN is used or not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of
E-UTRA cell within:
Tidentify_C GI, intra = Tbasic _ identify_C GI, intra ms
Where
Tbasic_identify_CGI, intra = 150 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has been already
identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.2 for a corresponding Band
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI,.intra is applicable when no DRX is
used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI, intra ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall transmit
at least 60 ACK/NACKs on PCell or each of activated SCell(s), provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 196 ETSI TS 136 133 V14.3.0 (2017-04)
Editor’s note: TBD requirements with SRS carrier based switching.
8.1.2.2.3.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.1.2.2.4 E-UTRAN TDD intra frequency measurements with autonomous gaps
8.1.2.2.4.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps in
downlink reception and uplink transmission for receiving MIB and SIB1 messages according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If autonomous
gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or eDRX_CONN is used or
not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI, intra = Tbasic _ identify_C GI, intra ms
Where
Tbasic_identify_CGI, intra = 150 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has been already
identified by the UE.
A cell shall be considered identifiable when the following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.2 for a corresponding Band
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI, intra is applicable when no DRX is
used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI, intra ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall be able
to transmit at least the number of ACK/NACKs stated in Table 8.1.2.2.4.1-1 on PCell or each of activated SCell(s),
provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 197 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.2.4.1-1: Requirement on minimum number of ACK/NACKs to transmit during
Tbasic_identify_CGI, intra.
UL/DL configuration Minimum number of
transmitted ACK/NACKs
0 (Note 1) 18
1 35
2 43
3 36
4 39
5 42
6 30
Note 1: When a UE is configured with EIMTA-
MainConfigServCell via RRC signalling [2]
only this requirement shall apply.
Editor’s note: TBD requirements with SRS carrier based switching.
8.1.2.2.4.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.1.2.3 E-UTRAN inter frequency measurements
The UE shall be able to identify new inter-frequency cells and perform RSRP, RSRQ, and RS-SINR measurements of
identified inter-frequency cells if carrier frequency information is provided by the PCell, even if no explicit neighbour
list with physical layer cell identities is provided.
The requirements in this section shall also appy, when the UE is configured to perform SRS carrier based switching and
using measurement gaps.
8.1.2.3.1 E-UTRAN FDD – FDD inter frequency measurements
8.1.2.3.1.1 E-UTRAN FDD – FDD inter frequency measurements when no DRX is used
When measurement gaps are scheduled, or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new FDD inter-frequency within TIdentify_Inter according to the following expression:
480
TIdentify_Inter = TBasic_Identify_Inter ⋅ ⋅ N freq , n ⋅ K n ms (normal performance) and
TInter1
480
TIdentify_Inter = TBasic_Identify_Inter ⋅ ⋅ N freq , r ⋅ K r ms (reduced performance)
TInter1
Where:
TBasic_Identify_Inter = 480 ms. It is the time period used in the inter frequency equation where the maximum
allowed time for the UE to identify a new FDD inter-frequency cell is defined.
Nfreq,n Nfreq,r Kn and Kr are defined in clause 8.1.2.1.1 and Tinter1 is defined in clause 8.1.2.1
A cell shall be considered detectable provided following conditions are fulfilled:
- RSRP|dBm and RSRP Ês/Iot according to Annex B.2.3 for a corresponding Band,
- other RSRP related side conditions given in Sections 9.1.3.1 and 9.1.3.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Sections 9.1.6.1 and 9.1.6.2 are fulfilled for a corresponding Band,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 198 ETSI TS 136 133 V14.3.0 (2017-04)
- RS-SINR related side conditions given in Sections 9.1.17.3.1 and 9.1.17.3.2 are fulfilled for a corresponding
Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.3 for a corresponding Band.
When measurement gaps are scheduled for FDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP, RSRQ, and
RS-SINR measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.3.1, 9.1.3.2,
9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively, with measurement period given by table 8.1.2.3.1.1-1.
Table 8.1.2.3.1.1-1: Measurement period and measurement bandwidth
Configuration Physical Layer Measurement Physical Layer Measurement period: Measurement
period: TMeasurement_Period _Inter_FDD TMeasurement_Period _Inter_FDD [ms] bandwidth [RB]
[ms] (normal performance) (reduced performance)
480 x Kn x Nfreq,n 480 x Kr x Nfreq,r 6
0
1 (Note) 240 x Kn x Nfreq,n 240 x Kr x Nfreq,r 50
Note: This configuration is optional
The UE shall be capable of performing RSRP, RSRQ, and RS-SINR measurements of at least 4 inter-frequency cells
per FDD inter-frequency for up to 3 FDD inter-frequencies or 8 FDD interfrequencies if the UE supports Increased UE
carrier monitoring E-UTRA and the UE physical layer shall be capable of reporting RSRP, RSRQ, and RS-SINR
measurements to higher layers with the measurement period defined in Table 8.1.2.3.1.1-1.
8.1.2.3.1.1.1 Measurement Reporting Requirements
8.1.2.3.1.1.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
8.1.2.3.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.3.1.1.1.3.
8.1.2.3.1.1.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH . The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify -inter defined
in clause 8.1.2.3.1.1. When L3 filtering is used or IDC autonomous denial is configured or the UE is performing
reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured
to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter defined in clause 8.1.2.3.1.1 and then triggers
the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period_Inter_FDD defined in clause 8.1.2.3.1.1 provided the timing to that cell has not changed more than ± 50 Ts
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 199 ETSI TS 136 133 V14.3.0 (2017-04)
while measurement gap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct Discovery
and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an additional
delay can be expected.
8.1.2.3.1.2 E-UTRAN FDD – FDD inter frequency measurements when DRX is used
When DRX or eDRX_CONN is in use, either measurement gaps are scheduled or the UE supports capability of
conducting such measurements without gaps, the UE shall be able to identify a new detectable E-UTRAN FDD inter
frequency cell within Tidentify_inter. When DRX is in use, Tidentify_inter is as defined in Table 8.1.2.3.1.2-1, and when
eDRX_CONN is in use, Tidentify_inter is as defined in Table 8.1.2.3.1.2-1A.
Table 8.1.2.3.1.2-1: Requirement to identify a newly detectable FDD interfrequency cell
DRX Tidentify_inter (s) (DRX cycles), normal Tidentify_inter (s) (DRX cycles), reduced
cycle performance performance
length (s) Gap period = Gap period = Gap period = 40 Gap period =
40 ms 80 ms ms 80 ms
≤0.16 Non DRX Non DRX Non DRX Non DRX
Requirements in Requirements in Requirements in Requirements in
clause 8.1.2.3.1.1 clause 8.1.2.3.1.1 clause 8.1.2.3.1.1 clause 8.1.2.3.1.1
are applicable are applicable are applicable are applicable
0.256 5.12*Kn*Nfreq,n 7.68*Kn *Nfreq,n 5.12*Kr*Nfreq,r 7.68*Kr *Nfreq,r
(20*Kn*Nfreq,n) (30*Kn *Nfreq,n) (20*Kr*Nfreq,r) (30*Kr *Nfreq,r)
0.32 6.4*Kn *Nfreq,n 7.68*Kn *Nfreq,nl 6.4*Kr *Nfreq,r 7.68*Kr *Nfreq,r
(20*Kn *Nfreq,n) (24*Kn *Nfreq,n) (20*Kr *Nfreq,r) (24*Kr *Nfreq,r)
0.32< Note (20*Kn Note (20*Kn Note (20*Kr Note (20*Kr
DRX- *Nfreq,n) *Nfreq,n) *Nfreq,r) *Nfreq,r)
cycle≤2.56
Note: Time depends upon the DRX cycle in use
Table 8.1.2.3.1.2-1A: Requirement to identify a newly detectable FDD inter-frequency cell when
eDRX_CONN cycle is used
eDRX_CONN Tidentify_inter (s) (eDRX_CONN cycles), Tidentify_inter (s) (eDRX_CONN cycles),
cycle length normal performance reduced performance
(s) Gap period = 40 Gap period = 80 Gap period = 40 Gap period = 80
ms ms ms ms
2.56< Note (20*Kn Note (20*Kn Note (20*Kr Note (20*Kr
eDRX_CONN *Nfreq,n) *Nfreq,n) *Nfreq,r) *Nfreq,r)
cycle≤10.24
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable provided following conditions are fulfilled:
- RSRP|dBm and RSRP Ês/Iot according to Annex B.2.3 for a corresponding Band,
- other RSRP related side conditions given in Clause 9.1.3.1 and 9.1.3.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Sections 9.1.6.1 and 9.1.6.2 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Sections 9.1.17.3.1 and 9.1.17.3.2 are fulfilled for a corresponding
Band,
- SCH_RP|dBm SCH Ês/Iot according to Annex B.2.3 for a corresponding Band.
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP, RSRQ, and RS-SINR
measurements of at least 4 inter-frequency cells per FDD inter-frequency and the UE physical layer shall be capable of
reporting RSRP, RSRQ, and RS-SINR measurements to higher layers with the measurement period Tmeasure_inter, either
measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps. When
DRX is used, Tmeasure_inter is as defined in Table 8.1.2.3.1.2-2, and when eDRX_CONN is in use, Tmeasure_inter is as defined
in Table 8.1.2.3.1.2-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 200 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.3.1.2-2: Requirement to measure FDD interfrequency cells
DRX cycle Tmeasure_inter (s) Tmeasure_inter (s)
length (s) (DRX cycles) (DRX cycles)
(normal (reduced
performance) performance)
≤0.08 Non DRX Non DRX
Requirements in Requirements in
clause 8.1.2.3.1.1 clause 8.1.2.3.1.1
are applicable are applicable
0.08<DRX- Note (5*Kn*Nfreq,n) Note (5*Kr*Nfreq,r)
cycle≤2.56
Note: Time depends upon the DRX cycle in use
Table 8.1.2.3.1.2-3: Requirement to measure FDD inter-frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_inter (s) Tmeasure_inter (s)
(eDRX_CONN cycles) (eDRX_CONN cycles)
(normal performance) (reduced performance)
2.56<eDRX_CONN cycle≤10.24 Note (5*Kn*Nfreq,n) Note (5*Kr*Nfreq,r)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.3.1 and 9.1.3.2, the
RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.6.1 and 9.1.6.2, and the
RS-SINR measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.17.3.1 and 9.1.17.3.2.
8.1.2.3.1.2.1 Measurement Reporting Requirements
8.1.2.3.1.2.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
8.1.2.3.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.3.1.2.1.3.
8.1.2.3.1.2.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter defined in
clause 8.1.2.3.1.2. When L3 filtering is used or IDC autonomous denial is configured or the UE is performing reception
and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 201 ETSI TS 136 133 V14.3.0 (2017-04)
If a cell which has been detectable at least for the time period Tidentify_inter defined in clause 8.1.2.3.1.2 and then triggers
the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
Tmeasure_inter defined in clause 8.1.2.3.1.2 provided the timing to that cell has not changed more than ± 50 Ts while
measurement gap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct Discovery
and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an additional
delay can be expected.
8.1.2.3.2 E-UTRAN TDD – TDD inter frequency measurements
8.1.2.3.2.1 E-UTRAN TDD – TDD inter frequency measurements when no DRX is used
When measurement gaps are scheduled, or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new TDD inter-frequency within TIdentify_Inter according to the following expression:
- When configuration 0 or configuration 1 in Table 8.1.2.3.2.1-1 is applied,
480
TIdentify_Inter = TBasic_Identify_Inter ⋅ ⋅ N freq ms ,
TInter1
- When configuration 2 or configuration 3 in Table 8.1.2.3.2.1-1 is applied,
480
TIdentify_Inter = TBasic_Identify_Inter ⋅ ⋅ N freq + 240 ⋅ N freq ms ,.
TInter1
TBasic_Identify_Inter = 480 ms. It is the time period used in the inter frequency equation where the maximum allowed
time for the UE to identify a new TDD inter-frequency cell is defined.
Nfreq is defined in clause 8.1.2.1.1 and Tinter1 is defined in clause 8.1.2.1
A cell shall be considered detectable provided following conditions are fulfilled:
- RSRP|dBm and RSRP Ês/Iot according to Annex B.2.3 for a corresponding Band,
- other RSRP related side conditions given in Clause 9.1.3.1 and 9.1.3.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Sections 9.1.6.1 and 9.1.6.2 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Sections 9.1.17.3.1 and 9.1.17.3.2 are fulfilled for a corresponding
Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.3 for a corresponding Band.
When measurement gaps are scheduled for TDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP, RSRQ, and
RS-SINR measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.3.1, 9.1.3.2,
9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively, with measurement period (TMeasurement_Period_TDD_Inter) given by
table 8.1.2.3.2.1-1:
Table 8.1.2.3.2.1-1: TMeasurement_Period_TDD_Inter for different configurations
Configuration Measurement Number of UL/DL sub- DwPTS TMeasurement_Period TMeasurement_Period_T
bandwidth frames per half frame (5 ms) _TDD_Inter [ms] DD_Inter [ms]
[RB] (normal (reduced
performance) performance)
DL UL Normal Extended
CP CP
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 202 ETSI TS 136 133 V14.3.0 (2017-04)
0 6 2 2 19760 ⋅ Ts 20480 ⋅ Ts 480 x Kn x Nfreq,n 480 x Kr x Nfreq,r
1 (Note 1) 50 2 2 19760 ⋅ Ts 20480 ⋅ Ts 240 x Kn x Nfreq,n 240 x Kr x Nfreq,r
2 6 1 3 19760 ⋅ Ts 20480 ⋅ Ts 720 x Kn x Nfreq,n 720 x Kr x Nfreq,r
3 (Note 1) 50 1 3 19760 ⋅ Ts 20480 ⋅ Ts 480 x Kn x Nfreq,n 480 x Kr x Nfreq,r
Note 1: This configuration is optional
Note 2: Ts is defined in TS 36.211 [16]
Note 3: N/A.
The UE shall be capable of performing RSRP, RSRQ, RS-SINR measurements of at least 4 inter-frequency cells per
TDD inter-frequency and the UE physical layer shall be capable of reporting RSRP, RSRQ, and RS-SINR
measurements to higher layers with the measurement period TMeasurement_Period_TDD_Inter.
8.1.2.3.2.1.1 Measurement Reporting Requirements
8.1.2.3.2.1.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
8.1.2.3.2.1.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.3.2.1.1.3.
8.1.2.3.2.1.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than TIdentify_Inter defined in
clause 8.1.2.3.2.1. When L3 filtering is used or IDC autonomous denial or the UE is performing reception and/or
transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to perform SRS
carrier based switching, is configured an additional delay can be expected.
If a cell which has been detectable at least for the time period TIdentify_Inter defined in clause 8.1.2.3.2.1 and then triggers
the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period_TDD_Inter defined in clause 8.1.2.3.2.1 provided the timing to that cell has not changed more than ± 50 Ts
while measurementgap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct Discovery
and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an additional
delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 203 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.3.2.2 E-UTRAN TDD – TDD inter frequency measurements when DRX is used
When DRX or eDRX_CONN is in use, either measurement gaps are scheduled or the UE supports capability of
conducting such measurements without gaps, the UE shall be able to identify a new detectable E-UTRAN TDD inter
frequency cell within Tidentify_inter. When DRX is in use, Tidentify_inter is as defined in Table 8.1.2.3.2.2-1, and when
eDRX_CONN is in use Tidentify_inter is as defined in Table 8.1.2.3.2.2-1A.
Table 8.1.2.3.2.2-1: Requirement to identify a newly detectable TDD interfrequency cell
DRX cycle Tidentify_inter (s) (DRX cycles) (normal Tidentify_inter (s) (DRX cycles)
length (s) performance) (reduced performance)
Gap period = Gap period = Gap period = Gap period =
40 ms 80 ms 40 ms 80 ms
≤0.16 Non DRX Non DRX Non DRX Non DRX
Requirements in Requirements in Requirements in Requirements in
clause 8.1.2.3.2.1 clause 8.1.2.3.2.1 clause 8.1.2.3.2.1 clause 8.1.2.3.2.1
are applicable are applicable are applicable are applicable
0.256 5.12*Kn*Nfreq,n 7.68*Kn *Nfreq,n 5.12*Kr*Nfreq,r 7.68*Kr *Nfreq,r
(20*Kn *Nfreq,n) (30*Kn *Nfreq,n) (20*Kr *Nfreq,r) (30*Kr *Nfreq,r)
0.32 6.4*Kn *Nfreq,n 7.68*Kn *Nfreq,n 6.4*Kr *Nfreq,r 7.68*Kr *Nfreq,r
(20*Kn *Nfreq,n) (24*Kn *Nfreq,n) (20*Kr *Nfreq,r) (24*Kr *Nfreq,r)
0.32<DRX- Note (20*Kn Note (20*Kn Note (20*Kr Note (20*Kr
cycle≤2.56 *Nfreq,n) *Nfreq,n) *Nfreq,r) *Nfreq,r)
Note: Time depends upon the DRX cycle in use
Table 8.1.2.3.2.2-1A: Requirement to identify a newly detectable TDD inter-frequency cell when
eDRX_CONN cycle is used
eDRX_CONN Tidentify_inter (s) (eDRX_CONN Tidentify_inter (s) (eDRX_CONN
cycle length (s) cycles) (normal performance) cycles) (reduced performance)
Gap period = Gap period = Gap period = Gap period =
40 ms 80 ms 40 ms 80 ms
2.56<eDRX_CONN Note (20*Kn Note (20*Kn Note (20*Kr Note (20*Kr
cycle ≤10.24 *Nfreq,n) *Nfreq,n) *Nfreq,r) *Nfreq,r)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable provided following conditions are fulfilled:
- RSRP|dBm and RSRP Ês/Iot according to Annex B.2.3 for a corresponding Band,
- other RSRP related side conditions given in Clause 9.1.3.1 and 9.1.3.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Sections 9.1.6.1 and 9.1.6.2 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Sections 9.1.17.3.1 and 9.1.17.3.2 are fulfilled for a corresponding
Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.3 for a corresponding Band.
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP, RSRQ, and RS-SINR
measurements of at least 4 inter-frequency cells per TDD inter-frequency for up to 3 TDD inter-frequencies and the UE
physical layer shall be capable of reporting RSRP, RSRQ, and RS-SINR measurements to higher layers with the
measurement period Tmeasure_inter, either measurement gaps are scheduled or the UE supports capability of conducting
such measurements without gaps. When DRX is in use, Tmeasure_inter is as defined in Table 8.1.2.3.2.2-2, and when
eDRX_CONN is in use, Tmeasure_inter is as defined in Table 8.1.2.3.2.2-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 204 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.3.2.2-2: Requirement to measure TDD interfrequency cells
DRX cycle Tmeasure_inter (s) Tmeasure_inter (s)
length (s) (DRX cycles) (DRX cycles)
(normal (reduced
requirement) requirement)
≤0.08 Non DRX Non DRX
Requirements in Requirements in
clause 8.1.2.3.2.1 clause 8.1.2.3.2.1
are applicable are applicable
0.128 When configuration When configuration
2 non DRX 2 non DRX
Requirements in Requirements in
clause 8.1.2.3.2.1 clause 8.1.2.3.2.1
are applicable, are applicable,
Otherwise Otherwise
Note (5*Kn*Nfreq,n) Note (5*Kr*Nfreq,r)
0.128<DRX- Note (5*Kn*Nfreq,n) Note (5*Kr*Nfreq,r)
cycle≤2.56
Note: Time depends upon the DRX cycle in use
Table 8.1.2.3.2.2-3: Requirement to measure TDD inter-frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle Tmeasure_inter (s) Tmeasure_inter (s)
length (s) (eDRX_CONN cycles) (eDRX_CONN cycles)
(normal requirement) (reduced requirement)
2.56<eDRX_CONN Note (5*Kn*Nfreq,n) Note (5*Kr*Nfreq,r)
cycle ≤10.24
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.3.1 and 9.1.3.2, the
RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.6.1 and 9.1.6.2, and the
RS-SINR measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.17.3.1 and 9.1.17.3.2.
8.1.2.3.2.2.1 Measurement Reporting Requirements
8.1.2.3.2.2.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the requirements in sections 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
8.1.2.3.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the requirements in clause 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.3.2.2.1.3.
8.1.2.3.2.2.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
requirements in clause 9.1.3.1, 9.1.3.2, 9.1.6.1, 9.1.6.2, 9.1.17.3.1 and 9.1.17.3.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 205 ETSI TS 136 133 V14.3.0 (2017-04)
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than TIdentify_Inter defined in
Clause 8.1.2.3.2.2. When L3 filtering is used or IDC autonomous denial is configured or the UE is performing reception
and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period TIdentify_Inter in clause 8.1.2.3.2.2 and then triggers the
measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than Tmeasure_inter
in clause 8.1.2.3.2.2 provided the timing to that cell has not changed more than ± 50 Ts while measurement gap has not
been available and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is configured or
the UE is performing reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or
the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.1.2.3.3 E-UTRAN TDD – FDD inter frequency measurements
8.1.2.3.3.1 E-UTRAN TDD – FDD inter frequency measurements when no DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.1.2.3.1.1 also apply for this section.
8.1.2.3.3.2 E-UTRAN TDD – FDD inter frequency measurements when DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
When DRX or eDRX_CONN cycle is used, the requirements in clause 8.1.2.3.1.2 shall also apply for this section.
8.1.2.3.4 E-UTRAN FDD – TDD inter frequency measurements
8.1.2.3.4.1 E-UTRAN FDD – TDD inter frequency measurements when no DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.1.2.3.2.1 also apply for this section.
8.1.2.3.4.2 E-UTRAN FDD – TDD inter frequency measurements when DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
When DRX or eDRX_CONN cycle is used, the requirements in clause 8.1.2.3.2.2 shall also apply for this section.
8.1.2.3.5 E-UTRAN FDD-FDD inter frequency measurements with autonomous gaps
8.1.2.3.5.1 Identification of a new CGI of E-UTRA FDD cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose of ‘reportCGI’. The UE may make autonomous gaps in
both downlink reception and uplink transmission for receiving MIB and SIB1 message according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If autonomous
gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or eDRX_CONN is used or
not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI, inter = Tbasic _ identify_C GI, inter ms
Where
Tbasic_identify_CGI, inter = 150 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new CGI of E-UTRA cell is defined, provided that the E-UTRA cell has been already
identified by the UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 206 ETSI TS 136 133 V14.3.0 (2017-04)
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.3 for a corresponding Band.
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI,inter is applicable when no DRX is
used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI, intra ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall transmit
at least 60 ACK/NACKs on PCell or each of activated SCell(s), provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
Editor’s note: TBD requirements with SRS carrier based switching.
8.1.2.3.5.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.1.2.3.6 E-UTRAN TDD-FDD inter frequency measurements using autonomous gaps
The requirements in this clause shall apply to UE supporting FDD and TDD.
8.1.2.3.6.1 Identification of a new CGI of E-UTRA FDD cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose of ‘reportCGI’. The UE may make autonomous gaps in
both downlink reception and uplink transmission for receiving MIB and SIB1 message according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If autonomous
gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or eDRX_CONN is used or
not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI, inter = Tbasic _ identify_C GI, inter ms
Where
Tbasic_identify_CGI, inter = 150 ms. This is the time period used in the above equation where the maximum allowed
time for the UE to identify a new CGI of E-UTRA cell is defined, provided that the E-UTRA cell has been
already identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.4 for a corresponding Band.
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 207 ETSI TS 136 133 V14.3.0 (2017-04)
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI,inter is applicable when no DRX is
used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI, inter ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall be able
to transmit at least the number of ACK/NACKs stated in Table 8.1.2.3.6.1-1 on PCell or each of activated SCell(s),
provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
Table 8.1.2.3.6.1-1: Requirement on minimum number of ACK/NACKs to transmit during
Tbasic_identify_CGI, inter.
TDD UL/DL configuration Minimum number of
for serving cell transmitted ACK/NACKs
0 (Note 1) 18
1 30
Note 1: When a UE is configured with EIMTA-
MainConfigServCell via RRC signalling [2] only
this requirement shall apply.
Note 2: The requirement for other TDD UL/DL
configuration is TBD.
Editor’s note: TBD requirements with SRS carrier based switching.
8.1.2.3.6.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.1.2.3.7 E-UTRAN TDD-TDD inter frequency measurements with autonomous gaps
8.1.2.3.7.1 Identification of a new CGI of E-UTRA TDD cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose of ‘reportCGI’. The UE may make autonomous gaps in
both downlink reception and uplink transmission for receiving MIB and SIB1 message according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If autonomous
gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or eDRX_CONN is used or
not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI, inter = Tbasic _ identify_C GI, inter ms
Where
Tbasic_identify_CGI, inter = 150 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new CGI of E-UTRA cell is defined, provided that the E-UTRA cell has been already
identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 208 ETSI TS 136 133 V14.3.0 (2017-04)
- SCH_RP and SCH Ês/Iot according to Annex B.2.4 for a corresponding Band.
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI,inter is applicable when no DRX is
used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI, inter ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall be able
to transmit at least the number of ACK/NACKs stated in Table 8.1.2.3.7.1-1 on PCell or each of activated SCell(s),
provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
Table 8.1.2.3.7.1-1: Requirement on minimum number of ACK/NACKs to transmit during
Tbasic_identify_CGI, inter.
TDD UL/DL configuration Minimum number of
for serving cell transmitted ACK/NACKs
0 (Note 1) 18
1 30
Note 1: When a UE is configured with EIMTA-
MainConfigServCell via RRC signalling [2] only
this requirement shall apply cell.
Note 2: The requirement for other TDD UL/DL
configuration is TBD.
Editor’s note: TBD requirements with SRS carrier based switching.
8.1.2.3.7.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.1.2.3.8 E-UTRAN FDD-TDD inter frequency measurements using autonomous gaps
The requirements in this clause shall apply to UE supporting FDD and TDD.
8.1.2.3.8.1 Identification of a new CGI of E-UTRA TDD cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose of ‘reportCGI’. The UE may make autonomous gaps in
both downlink reception and uplink transmission for receiving MIB and SIB1 message according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If autonomous
gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or eDRX_CONN is used or
not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI, inter = Tbasic _ identify_C GI, inter ms
Where
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 209 ETSI TS 136 133 V14.3.0 (2017-04)
Tbasic_identify_CGI, inter = 150 ms. This is the time period used in the above equation where the maximum allowed
time for the UE to identify a new CGI of E-UTRA cell is defined, provided that the E-UTRA cell has been
already identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.4 for a corresponding Band.
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI,inter is applicable when no DRX is
used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI, inter ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall have
more than 60 ACK/NACKs transmitted on PCell or each of activated SCell(s), provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
Editor’s note: TBD requirements with SRS carrier based switching.
8.1.2.3.8.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.1.2.4 Inter RAT measurements
The requirements in this section shall also appy, when the UE is configured to perform SRS carrier based switching and
using measurement gaps.
8.1.2.4.1 E-UTRAN FDD – UTRAN FDD measurements
8.1.2.4.1.1 E-UTRAN FDD – UTRAN FDD measurements when no DRX is used
8.1.2.4.1.1.1 Identification of a new UTRA FDD cell
When explicit neighbour list is provided and no DRX is used, either measurement gaps are scheduled or the UE
supports capability of conducting such measurements without gaps, the UE shall be able to identify a new detectable
cell belonging to the monitored set within
480
Tidentify, UTRA_FDD = Tbasic _ identify _ UTRA_FDD ⋅ ⋅ K n ⋅ N freq,n ms (normal performance),
Tinter1
and
480
Tidentify, UTRA_FDD = Tbasic _ identify _ UTRA_FDD ⋅ ⋅ K r ⋅ N freq ,r ms (reduced performance)
Tinter1
A cell shall be considered detectable when
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 210 ETSI TS 136 133 V14.3.0 (2017-04)
- CPICH Ec/Io > -20 dB,
- SCH_Ec/Io > -17 dB for at least one channel tap and SCH_Ec/Ior is equally divided between primary
synchronisation code and secondary synchronisation code. When L3 filtering is used an additional delay can be
expected.
8.1.2.4.1.1.1a Enhanced UTRA FDD cell identification requirements
When explicit neighbour list is provided and no DRX is used or when DRX cycle length ≤ 40 ms, either measurement
gaps are scheduled or the UE supports capability of conducting such measurements without gaps, the UE shall be able
to identify a new detectable cell belonging to the monitored set within Tidentify, enhanced_UTRA_FDD:
480
Tidentify, enhanced_U TRA_FDD = (Tbasic _ identify _ enhanced_UTRA_FDD ⋅ + 480) K n N freq,n ms (normal performance)
Tinter1
and
480
Tidentify, enhanced_U TRA_FDD = (Tbasic _ identify _ enhanced_UTRA_FDD ⋅ + 480) K r N freq,r ms (reduced performance)
Tinter1
A cell shall be considered detectable when:
- CPICH Ec/Io > -15 dB,
- SCH_Ec/Io > -15 dB for at least one channel tap and SCH_Ec/Ior is equally divided between primary
synchronisation code and secondary synchronisation code. When L3 filtering is used an additional delay can be
expected.
8.1.2.4.1.1.2 UE UTRA FDD CPICH measurement capability
When measurement gaps are scheduled for UTRA FDD inter RAT measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting measurements to
higher layers with measurement accuracy as specified in Clause 9.2 with measurement period given by
⎧ 480 ⎫
Tmeasurement _UTRA_FDD = Max ⎨TMeasurement_Period UTRA_FDD , Tbasic _ measurement _ UTRA_FDD ⋅ ⋅ K n ⋅ N freq, n ⎬ms (normal
⎩ Tinter1 ⎭
performance),
and
⎧ 480 ⎫
Tmeasurement _UTRA_FDD = Max ⎨TMeasurement_Period UTRA_FDD , Tbasic _ measurement _ UTRA_FDD ⋅ ⋅ K r ⋅ N freq, r ⎬ms (reduced
⎩ Tinter1 ⎭
performance)
The UE shall be capable of performing UTRA FDD CPICH measurements for Xbasic measurementUTRA_FDD inter-frequency
cells per FDD frequency and the UE physical layer shall be capable of reporting measurements to higher layers with the
measurement period of TMeasurement_ UTRA_FDD.
Xbasic measurement UTRA_FDD = 6
TMeasurement_Period UTRA_FDD = 480 ms. The period used for calculating the measurement period Tmeasurement_UTRA_FDD
for UTRA FDD CPICH measurements.
Tbasic_identify_UTRA_FDD = 300 ms. This is the time period used in the inter RAT equation in clause 8.1.2.4.1.1.1
where the maximum allowed time for the UE to identify a new UTRA FDD cell is defined.
Tbasic_identify_enhanced_UTRA_FDD = 60 ms. This is the time period used in the inter RAT equation in
clause 8.1.2.4.1.1.1a where the maximum allowed time for the UE to identify a new UTRA FDD cell is defined.
Tbasic_measurement_UTRA_FDD = 50 ms. This is the time period used in the equation for defining the measurement
period for inter RAT CPICH measurements.
Nfreq, n, Nfreq,r ,Kn and Kr are defined in clause 8.1.2.1.1 and Tinter1 is defined in clause 8.1.2.1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 211 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.4.1.1.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.
8.1.2.4.1.1.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as the reporting criteria is not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report until
the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that the measurement
report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay
uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is
twice the TTI of the uplink DCCH. This measurement reporting delay excludes a delay which caused by no UL
resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify, UTRA_FDD
defined in Clause 8.1.2.4.1.1.1 for the minimum requirements or Tidentify, enhanced_UTRA_FDD defined in Clause 8.1.2.4.1.1.1a
for the enhanced requirements When L3 filtering is used or IDC autonomous denial or the UE is performing reception
and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify, UTRA_FDD defined in clause 8.1.2.4.1.1.1 for the
minimum requirements or Tidentify, enhanced_UTRA_FDD defined in Clause 8.1.2.4.1.1.1a for the enhanced requirements and
then triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less
than Tmeasurement_UTRA_FDD defined in clause 8.1.2.4.1.1.2 provided the timing to that cell has not changed more than ± 32
chips while measurement gap has not been available and the L3 filter has not been used. When L3 filtering is used or
IDC autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct Discovery
and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an additional
delay can be expected.
8.1.2.4.1.1.5 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.4.1.1.4.
8.1.2.4.1.2 E-UTRAN FDD – UTRAN FDD measurements when DRX is used
When explicit neighbour list is provided and DRX or eDRX_CONN is used, either measurement gaps are scheduled or
the UE supports capability of conducting such measurements without gaps, the UE shall be able to identify a new
detectable cell belonging to the neighbour cell list within Tidentify,UTRA_FDD. When DRX is used, Tidentify,UTRA_FDD is as
defined in table 8.1.2.4.1.2-1, and when eDRX_CONN is used, Tidentify,UTRA_FDD is as defined in table 8.1.2.4.1.2-1A.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 212 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.4.1.2-1: Requirement to identify a newly detectable UTRA FDD cell
DRX Tidentify_UTRA_FDD (s) (DRX cycles) Tidentify_UTRA_FDD (s) (DRX cycles) reduced requirement
normal requirement
cycle
length
(s)
Gap period = Gap period = Gap period = 40 ms Gap period = 80 ms
40 ms 80 ms
≤0.04 Non DRX Non DRX Non DRX Requirements in Non DRX Requirements in
Requirements in Requirements in clause 8.1.2.4.1.1 are clause 8.1.2.4.1.1 are
clause 8.1.2.4.1.1 clause 8.1.2.4.1.1 applicable applicable
are applicable are applicable
0.064 2.56*Kn* Nfreq,n 4.8* Kn* Nfreq,n 2.56*Kr* Nfreq,r (40* Kr* Nffreq,r) 4.8* Kr* Nfreq,r(75* Kr* Nfreq,r)
(40* Nffreq,n) (75* Kn* Nfreq,n)
0.08 3.2* Kn* Nfreq,n 4.8* Kn* Nfreq,n 3.2* Kr* Nfreq,r (40* Kr* Nfreq,r) 4.8* Kr* Nfreq,r (60* Kr* Nfreq,r)
(40* Kn* Nfreq,n) (60* Kn* Nfreq,n)
0.128 3.2* Kn* Nfreq,n 4.8* Kn* Nfreq,n 3.2* Kr* Nfreq,n (25* Kr* Nfreq,r) 4.8* Kr* Nfreq,r (37.5* Kr*
(25* Kn* Nfreq) (37.5* Kn* Nfreq,n) Nfreq,r)
0.16 3.2* Kn* Nfreq,n 4.8* Kn* Nfreq,n 3.2* Kr* Nfreq,n (20* Kr* Nfreq,r) 4.8* Kr* Nfreq,r (30* Kr* Nfreq,r)
(20* Kn* Nfreq,n) (30* Kn* Nfreq,n)
0.16<DRX- Note (20* Kn* Note Note (20* Kr* Nfreq,r) Note
cycle≤2.56 Nfreq,n) (20* Kn* Nfreq,n) (20* Kr* Nfreq,r)
Note: Time depends upon the DRX cycle in use
Table 8.1.2.4.1.2-1A: Requirement to identify a newly detectable UTRA FDD cell when eDRX_CONN
cycle is used
eDRX_CONN Tidentify_UTRA_FDD (s) (eDRX_CONN cycles) Tidentify_UTRA_FDD (s) (eDRX_CONN cycles)
normal requirement reduced requirement
cycle length (s)
Gap period = 40 Gap period = 80 Gap period = 40 Gap period = 80
ms ms ms ms
2.56<eDRX_CONN Note (20* Kn* Nfreq,n) Note (20* Kn* Nfreq,n) Note (20* Kr* Nfreq,r) Note (20* Kr* Nfreq,r)
cycle≤10.24
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable provided following conditions are fulfilled: A cell shall be considered detectable
when
- CPICH Ec/Io > -20 dB,
- SCH_Ec/Io > -17 dB for at least one channel tap and SCH_Ec/Ior is equally divided between primary
synchronisation code and secondary synchronisation code. When L3 filtering is used an additional delay can be
expected.
When DRX or eDRX_CONN is used, the UE shall be capable of performing RSCP and Ec/Io measurements of at least
6 UTRA cells per UTRA FDD carrier for up to 3 UTRA FDD carriers and the UE physical layer shall be capable of
reporting RSCP and Ec/Io measurements to higher layers within the measurement period Tmeasure_ UTRA_FDD, either
measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps. UE
supporting Increased UE carrier monitoring UTRA shall be capable of performing RSCP and Ec/Io measurements of at
least 6 UTRA cells per UTRA FDD carrier for up to 6 UTRA FDD carriers with maximum of 80 cells consisting of at
most 32 cells per frequency layer in the neighbour cell list. When DRX is used, Tmeasure_ UTRA_FDD is defined in Table
8.1.2.3.1.2-2, and when eDRX_CONN cycle is used, Tmeasure_ UTRA_FDD is defined in Table 8.1.2.3.1.2-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 213 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.4.1.2-2: Requirement to measure UTRA FDD cells
DRX cycle Tmeasure_ UTRA_FDD (s) (DRX cycles) Tmeasure_ UTRA_FDD (s) (DRX cycles) normal requirement
length (s) normal requirement
Gap period = Gap period = Gap period = 40 ms Gap period = 80 ms
40 ms 80 ms
≤0.04 Non DRX Non DRX Non DRX Requirements in Non DRX Requirements in
Requirements in Requirements in clause 8.1.2.4.1.1 are clause 8.1.2.4.1.1 are
clause 8.1.2.4.1.1 clause 8.1.2.4.1.1 applicable applicable
are applicable are applicable
0.064 0.48*Kn* Nfreq,n 0.8* Kn* Nfreq,n 0.48* Kr* Nfreq,r (7.5* Kr* Nfreq,r) 0.8* Kr* Nfreq,r
(7.5* Kn* Nfreq,n) (12.5* Kn* Nfreq,n) (12.5* Kr* Nfreq,r)
0.08 0.48* Kn* Nfreq,n 0. 8* Kn* Nfreq,n 0.48* Kr* Nfreq,r 0. 8* Kr* Nfreq,r (10* Kr* Nfreq,r)
(6* Kn* Nfreq,n) (10* Nfreq,n) (6* Kr* Nfreq,r)
0.128 0.64* Kn* Nfreq,n 0. 8* Kn* Nfreq,n 0.64* Kr* Nfreq,r 0. 8* Kr* Nfreq,r (6.25* Nfreq,r)
(5* Kn* Nfreq,n) (6.25* Nfreq,n) (5* Kr* Nfreq,r)
0.128<DRX- Note (5* Kn* Note (5* Kn* Note (5* Kr* Nfreq,r) Note (5* Kr* Nfreq,r)
cycle≤2.56 Nfreq,n) Nfreq,n)
Note: Time depends upon the DRX cycle in use
Table 8.1.2.4.1.2-3: Requirement to measure UTRA FDD cells when eDRX_CONN cycle is used
eDRX_CONN Tmeasure_ UTRA_FDD (s) (eDRX_CONN cycles) Tmeasure_ UTRA_FDD (s) (eDRX_CONN cycles)
cycle length (s) normal requirement normal requirement
Gap period = 40 Gap period = 80 Gap period = 40 Gap period = 80 ms
ms ms ms
2.56<eDRX_CONN Note (5* Kn* Nfreq,n) Note (5* Kn* Nfreq,n) Note (5* Kr* Nfreq,r) Note (5* Kr* Nfreq,r)
cycle≤10.24
Note: Time depends upon the eDRX_CONN cycle in use
The measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.
8.1.2.4.1.2.1 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.
8.1.2.4.1.2.2 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as the reporting criteria is not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report until
the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that the measurement
report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay
uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is
twice the TTI of the uplink DCCH. This measurement reporting delay excludes a delay which caused by no UL
resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify,UTRA_FDD
defined in Clause 8.1.2.4.1.2. When L3 filtering is used or IDC autonomous denial is configured or the UE is
performing reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify, UTRA_FDD defined in clause 8.1.2.4.1.2 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
Tmeasurement_UTRA_FDD defined in clause 8.1.2.4.1.2 provided the timing to that cell has not changed more than ± 32 chips
while measurement gap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct Discovery
and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an additional
delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 214 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.4.1.2.3 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.4.1.2.2.
8.1.2.4.2 E-UTRAN TDD – UTRAN FDD measurements
The requirements in clause 8.1.2.4.1 also apply for this section.
8.1.2.4.2.1 E-UTRAN TDD – UTRAN FDD measurements when no DRX is used
8.1.2.4.2.2 E-UTRAN TDD – UTRAN FDD measurements when DRX is used
8.1.2.4.3 E-UTRAN TDD – UTRAN TDD measurements
8.1.2.4.3.1 E-UTRAN TDD – UTRAN TDD measurements when no DRX is used
8.1.2.4.3.1.1 Identification of a new UTRA TDD cell
When explicit neighbour list is provided and no DRX is used, either measurement gaps are scheduled or the UE
supports capability of conducting such measurements without gaps, the UE shall be able to identify a new detectable
cell belonging to the monitored set within
⎧ 480 ⎫
Tidentify, UTRA_TDD = Max⎨5000, Tbasic identify UTRA_TDD ⋅ ⋅ K n ⋅ N freq , n ⎬ms (normal performance),
⎩ Tinter1 ⎭
and
⎧ 480 ⎫
Tidentify, UTRA_TDD = Max ⎨5000, Tbasic identify UTRA_TDD ⋅ ⋅ K r ⋅ N freq ,r ⎬ms (reduced performance)
⎩ Tinter1 ⎭
A cell shall be considered detectable when
- P-CCPCH Ec/Io > -8 dB,
- DwPCH_Ec/Io > -5 dB.
When L3 filtering is used an additional delay can be expected.
8.1.2.4.3.1.1a Enhanced UTRA TDD cell identification requirements
When explicit neighbour list is provided and no DRX is used or when DRX cycle length ≤ 40 ms, either measurement
gaps are scheduled or the UE supports capability of conducting such measurements without gaps, the UE shall be able
to identify a new detectable cell belonging to the monitored set within Tidentify, enhanced_UTRA_TDD:
480
Tidentify, enhanced_U TRA_TDD = (Tbasic _ identify _ enhanced_U TRA_TDD ⋅ + 480) ⋅ K n ⋅ N freq , n ms (normal performance),
Tinter1
and
480
Tidentify, enhanced_U TRA_TDD = (Tbasic _ identify _ enhanced_U TRA_TDD ⋅ + 480) ⋅ K r ⋅ N freq , r ms (reduced performance)
Tinter1
A cell shall be considered detectable when:
- P-CCPCH_Ec/Io > -6 dB,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 215 ETSI TS 136 133 V14.3.0 (2017-04)
- DwPCH_Ec/Io > -1 dB
When L3 filtering is used an additional delay can be expected.
8.1.2.4.3.1.2 UE UTRA TDD P-CCPCH RSCP measurement capability
When measurement gaps are scheduled for UTRA TDD inter RAT measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting measurements to
higher layers with measurement accuracy as specified in Clause 9.3 with measurement period given by
⎧ 480 ⎫
Tmeasurement UTRA_TDD = Max ⎨TMeasurement_Period UTRA_TDD , Tbasic measurement UTRA_TDD ⋅ ⋅ K n ⋅ N freq, n ⎬ms (normal
⎩ Tinter1 ⎭
performance)
⎧ 480 ⎫
Tmeasurement UTRA_TDD = Max⎨TMeasurement_Period UTRA_TDD , Tbasic measurement UTRA_TDD ⋅ ⋅ K r ⋅ N freq,r ⎬ms (reduced
⎩ Tinter1 ⎭
performance)
The UE shall be capable of performing UTRA TDD P-CCPCH RSCP measurements for Xbasic measurementUTRA_TDD inter-
frequency cells per TDD frequency of the monitored set, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_ UTRA_TDD.
Xbasic measurementUTRA_TDD = 6
TMeasurement_Period UTRA_TDD = 480 ms is the period used for calculating the measurement period Tmeasurement_UTRA_TDD
for UTRA TDD P-CCPCH RSCP measurements.
Tbasic_identify_UTRA_TDD = 800 ms is the time period used in the inter RAT equation in clause 8.1.2.4.3.1.1 where the
maximum allowed time for the UE to identify a new UTRA TDD cell is defined.
Tbasic_identify_enhanced_UTRA_TDD = 80 ms is the time period used in the inter RAT equation in clause 8.1.2.4.3.1.1a
where the maximum allowed time for the UE to identify a new UTRA TDD cell is defined.
Tbasic_measurement_UTRA_TDD = 50 ms is the time period used in the equation for defining the measurement period for
inter RAT P-CCPCH RSCP measurements.
Nfreq,n, Nfreq,r, Kn and Kr are defined in clause 8.1.2.1.1 and Tinter1 is defined in clause 8.1.2.1
8.1.2.4.3.1.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.
8.1.2.4.3.1.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as the reporting criteria is not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report until
the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that the measurement
report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay
uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is
twice the TTI of the uplink DCCH. This measurement reporting delay excludes a delay which caused by no UL
resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify, UTRA_TDD
defined in Clause 8.1.2.4.3.1.1 for the minimum requirements or Tidentify, enhanced_UTRA_TDD defined in Clause 8.1.2.4.3.1.1a
for the enhanced requirements. When L3 filtering is used or IDC autonomous denial is configured or the UE is
performing reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 216 ETSI TS 136 133 V14.3.0 (2017-04)
If a cell which has been detectable at least for the time period Tidentify, UTRA_TDD defined in clause 8.1.2.4.3.1.1 for the
minimum requirements and then triggers the measurement report as per TS 36.331 [2], the event triggered measurement
reporting delay shall be less than Tmeasurement_UTRA_TDD defined in clause 8.1.2.4.3.1.2 provided the timing to that cell has
not changed more than ± 10 chips while measurement gap has not been available and the L3 filter has not been used.
When L3 filtering is used or IDC autonomous denial is configured or the UE is performing reception and/or
transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to perform SRS
carrier based switching, an additional delay can be expected.
8.1.2.4.3.1.5 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.4.3.1.4.
8.1.2.4.3.2 E-UTRAN TDD – UTRAN TDD measurements when DRX is used
When explicit neighbour list is provided and DRX or eDRX_CONN is used, either measurement gaps are scheduled or
the UE supports capability of conducting such measurements without gaps, the UE shall be able to identify a new
detectable cell belonging to the neighbour cell list within Tidentify,UTRA_TDD. When DRX is used, Tidentify,UTRA_TDD is as
defined in table 8.1.2.4.3.2-1, and when eDRX_CONN is used, Tidentify,UTRA_TDD is as defined in table 8.1.2.4.3.2-1A.
Table 8.1.2.4.3.2-1: Requirement to identify a newly detectable UTRA TDD cell
DRX cycle Tidentify_UTRA_TDD (s) (DRX cycles) Tidentify_UTRA_TDD (s) (DRX cycles)
(normal requirement) (reduced requirement)
length (s)
Gap period = 40 Gap period = 80 Gap period = 40 Gap period = 80
ms ms ms ms
≤0.32 Non DRX Non DRX Non DRX Non DRX
Requirements in Requirements in Requirements in Requirements in
clause 8.1.2.4.3.1 clause 8.1.2.4.3.1 clause 8.1.2.4.3.1 clause 8.1.2.4.3.1
are applicable are applicable are applicable are applicable
0.32<DRX- Note (20*Kn* Note (25*Kn * Note (20*Kr* Note (25*Kr *
cycle≤0.512 Nfreq,n) Nfreq,n) Nfreq,r) Nfreq,r)
0.512<DRX- Note (20*Kn * Note Note (20*Kr * Note
cycle≤2.56 Nfreq,n) (20*Kn * Nfreq,n) Nfreq,r) (20*Kr * Nfreq,r)
Note: Time depends upon the DRX cycle in use
Table 8.1.2.4.3.2-1A: Requirement to identify a newly detectable UTRA TDD cell when eDRX_CONN
cycle is used
eDRX_CONN Tidentify_UTRA_TDD (s) (eDRX_CONN cycles) Tidentify_UTRA_TDD (s) (eDRX_CONN cycles)
(normal requirement) (reduced requirement)
cycle length (s)
Gap period = 40 ms Gap period = 80 ms Gap period = 40 ms Gap period = 80 ms
2.56<eDRX_CONN Note (20*Kn * Nfreq,n) Note (20*Kn * Nfreq,n) Note (20*Kr * Nfreq,r) Note (20*Kr * Nfreq,r)
cycle ≤10.24
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable provided following conditions are fulfilled: A cell shall be considered detectable
when
- P-CCPCH Ec/Io > -8 dB,
- DwPCH_Ec/Io > -5 dB.
When L3 filtering is used an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 217 ETSI TS 136 133 V14.3.0 (2017-04)
When DRX or eDRX_CONN is in use, the UE shall be capable of performing UTRA TDD P-CCPCH RSCP
measurements of at least 6 UTRA cells per UTRA TDD carrier for up to 3 UTRA TDD carriers and the UE physical
layer shall be capable of reporting measurements to higher layers with the measurement period Tmeasure_UTRA_TDD, either
measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps. UE
supporting Increased UE carrier monitoring UTRA shall be capable of performing UTRA TDD P-CCPCH RSCP
measurements of at least 6 UTRA cells per UTRA TDD carrier for up to 7 UTRA TDD carriers with maximum of 80
cells consisting of at most 32 cells per frequency layer in the neighbour cell list. When DRX is used, Tmeasure_UTRA_TDD is
as defined in Table 8.1.2.4.3.2-2, and when eDRX_CONN is used, Tmeasure_UTRA_TDD is as defined in Table 8.1.2.4.3.2-3.
Table 8.1.2.4.3.2-2: Requirement to measure UTRA TDD cells
DRX Tmeasure_UTRA_TDD (s) (DRX cycles) Tmeasure_UTRA_TDD (s) (DRX cycles)
cycle (normal requirement) (reduced requirement)
length (s)
Gap period = 40 Gap period = 80 Gap period = 40 Gap period = 80
ms ms ms ms
≤0.04 Non DRX Non DRX Non DRX Non DRX
Requirements in Requirements in Requirements in Requirements in
clause 8.1.2.4.3.1 clause 8.1.2.4.3.1 clause 8.1.2.4.3.1 clause 8.1.2.4.3.1
are applicable are applicable are applicable are applicable
0.064 0.48*Kn*Nfreq,n 0.8*Kn *Nfreq,n 0.48* Kr* Nfreq,r 0.8* Kr* Nfreq,r
(7.5*Kn *Nfreq,n) (12.5*Kn *Nfreq,n) (7.5* Kr* Nfreq,r) (12.5* Kr* Nfreq,r)
0.08 0.48*Kn *Nfreq,n 0. 8*Kn *Nfreq,n 0.48* Kr* Nfreq,r 0. 8* Kr* Nfreq,r
(6*Kn *Nfreq,n) (10*Kn *Nfreq,n) (6* Kr* Nfreq,r) (10* Kr* Nfreq,r)
0.128 0.64*Kn *Nfreq,n 0. 8*Kn *Nfreq,n 0.64* Kr* Nfreq,r 0. 8* Kr* Nfreq,r
(5*Kn *Nfreq,n) (6.25*Kn *Nfreq,n) (5* Kr* Nfreq,r) (6.25* Nfreq,r)
0. Note (5*Kn Note (5*Kn Note (5* Kr* Note (5* Kr*
128<DRX- *Nfreq,n) *Nfreq,n) Nfreq,r) Nfreq,r)
cycle≤2.56
Note: Time depends upon the DRX cycle in use
Table 8.1.2.4.3.2-3: Requirement to measure UTRA TDD cells when eDRX_CONN cycle is used
eDRX_CONN Tmeasure_UTRA_TDD (s) (eDRX_CONN Tmeasure_UTRA_TDD (s) (eDRX_CONN
cycle length (s) cycles) (normal requirement) cycles) (reduced requirement)
Gap period = Gap period = Gap period = Gap period =
40 ms 80 ms 40 ms 80 ms
2.56<eDRX_CONN Note (5*Kn Note (5*Kn Note (5* Kr* Note (5* Kr*
cycle≤10.24 *Nfreq,n) *Nfreq,n) Nfreq,r) Nfreq,r)
Note: Time depends upon the eDRX_CONN cycle in use
The measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.
8.1.2.4.3.2.1 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.
8.1.2.4.3.2.2 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as the reporting criteria is not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report until
the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that the measurement
report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay
uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is
twice the TTI of the uplink DCCH. This measurement reporting delay excludes a delay which caused by no UL
resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify, UTRA_TDD
defined in Clause 8.1.2.4.3.2 When L3 filtering is used or IDC autonomous denial is configured or the UE is performing
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 218 ETSI TS 136 133 V14.3.0 (2017-04)
reception and/or transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured
to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify, UTRA_TDD defined in clause 8.1.2.4.3.2 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
Tmeasurement_UTRA_TDD defined in clause 8.1.2.4.3.2 provided the timing to that cell has not changed more than ± 10 chips
while measurement gap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct Discovery
and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an additional
delay can be expected.
8.1.2.4.3.2.3 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.4.3.2.2.
8.1.2.4.4 E-UTRAN FDD – UTRAN TDD measurements
The requirements in clause 8.1.2.4.3 also apply for this section.
8.1.2.4.5 E-UTRAN FDD – GSM measurements
8.1.2.4.5.1 E-UTRAN FDD – GSM measurements when no DRX is used
The requirements in this clause apply only to UE supporting E-UTRAN FDD and GSM.
Measurements on GSM cells can be requested with BSIC verified.
In RRC_CONNECTED state when a supported measurement gap pattern sequence according to Table 8.1.2.1-1 is
configured by E-UTRAN, or the UE supports capability of conducting such measurements without gaps, the UE
shall continuously measure GSM cells, search for new GSM cells given in the monitored set and re-confirm the
BSIC for already detected cells.
8.1.2.4.5.1.1 GSM carrier RSSI
This measurement shall be based on measurement gaps allocated for GSM carrier RSSI measurement as described in
clause 8.1.2.1. A UE supporting GSM measurements shall measure minimum number of 10 GSM carrier RSSI
measurement samples (NGSM carrier RSSI) per measurement gap. In RRC_CONNECTED state the measurement period,
TMeasurement Period, GSM, for the GSM carrier RSSI measurement is Kn*Nfreq,n *480 ms. The parameters Nfreq,n and Kn are
defined in clause 8.1.2.1.1.
The UE shall meet the measurement accuracy requirements stated for RXLEV in [8], when the given measurement time
allows the UE to take at least 3 GSM carrier RSSI samples per GSM carrier in the monitored set during the
measurement period.
In case the UE is not able to acquire the required number of samples per GSM carrier during one measurement period,
the UE shall measure as many GSM carriers as possible during that measurement period using at least 3 samples per
GSM carrier. The GSM carriers that were not measured during that measurement period shall be measured in the
following measurement periods.
8.1.2.4.5.1.2 BSIC verification
Measurements on a GSM cell can be requested with BSIC verified. The UE shall be able to report the GSM cells with
BSIC verified for those cells where the verification of BSIC has been successful.
The procedure for BSIC verification on a GSM cell can be divided into the following two tasks:
- Initial BSIC identification: Includes searching for the BSIC and decoding the BSIC for the first time when
there is no knowledge about the relative timing between the E-UTRAN FDD and GSM cells. The UE shall
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 219 ETSI TS 136 133 V14.3.0 (2017-04)
trigger the initial BSIC identification within the available measurement gap pattern sequence. The requirements
for BSIC re-confirmation can be found in clause 8.1.2.4.5.1.2.1.
- BSIC re-confirmation: Tracking and decoding the BSIC of a GSM cell after initial BSIC identification is
performed. The UE shall trigger the BSIC re-confirmation within the available measurement gap pattern. The
requirements for BSIC re-confirmation can be found in clause 8.1.2.4.5.1.2.2.
If the network requests measurements on a GSM cell the UE shall behave as follows:
- The UE shall perform GSM carrier RSSI measurements according to clause 8.1.2.4.5.1 when a measurement gap
pattern sequence is activated, or the UE supports capability of conducting such measurements without gaps.
The UE shall perform measurement reporting as defined in TS 36.331 [2].
- The UE shall perform BSIC identification. The UE shall use the most recently available GSM carrier RSSI
measurement results for arranging GSM cells in signal strength order for performing BSIC identification.
- The UE shall perform BSIC re-confirmation on all the GSM cells that have been successfully identified.
- The UE shall perform all configured event evaluation for event-triggered reporting after the BSIC has been
verified for a GSM cell. The UE shall use the most recently available GSM carrier RSSI measurement results in
event evaluation and event-triggered reporting.
- Event-triggered and periodic reports shall be triggered according to TS 36.331 [2].
The BSIC of a GSM cell is considered to be “verified” if the UE has decoded the SCH of the BCCH carrier and
identified the BSIC at least one time (initial BSIC identification). Once a GSM cell has been identified the BSIC shall
be re-confirmed at least once every 8*Tre-confirm,GSM seconds. Otherwise the BSIC of the GSM cell is considered as "non-
verified". If a measurement gap pattern sequence is deactivated by the network after BSIC has been identified or
verified, the UE shall consider the BSIC as non-verified.
Tidentify,GSM indicates the maximum time allowed for the UE to decode the unknown BSIC of the GSM cell in one GSM
BCCH carrier in the initial BSIC identification procedure.
Tre-confirm,GSM indicates the maximum time allowed for the re-confirmation of the BSIC of one GSM cell in the BSIC re-
confirmation procedure.
The UE shall be able to decode a BSIC within a measurement gap when the time difference between the middle of the
received GSM synchronisation burst at the UE and the middle of the effective measurement gap is within the limits
specified in table 8.1.2.4.5.1.2-1.
Table 8.1.2.4.5.1.2-1: The gap length and maximum time difference for BSIC verification
Gap length Maximum time difference [μs]
[ms]
6 ± 2350 µs
The UE shall be able to perform BSIC verification at levels down to the reference sensitivity level or reference
interference levels as specified in [9].
8.1.2.4.5.1.2.1 Initial BSIC identification
This measurement shall be based on the measurement gaps used for Initial BSIC identification as described in
clause 8.1.2.4.5.1.2.
The UE shall continuously attempt to decode the BSIC of SCH on the BCCH carrier of the 8 strongest BCCH carriers
of the GSM cells indicated in the Inter-RAT cell info list. The UE shall give priority for BSIC decoding attempts in
decreasing signal strength order to BCCH carriers with unknown BSIC. The strongest BCCH carrier is defined as the
BCCH carrier having the highest measured GSM carrier RSSI value.
If the BSIC of the GSM BCCH carrier has been successfully decoded the UE shall immediately continue BSIC
identification with the next GSM BCCH carrier, in signal strength order, with unknown BSIC. The GSM cell for which
the BSIC has been successfully identified shall be moved to the BSIC re-confirmation procedure.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 220 ETSI TS 136 133 V14.3.0 (2017-04)
If the UE has not successfully decoded the BSIC of the GSM BCCH carrier within Tidentify,GSM ms, the UE shall abort the
BSIC identification attempts for that GSM BCCH carrier. The UE shall continue to try to perform BSIC identification
of the next GSM BCCH carrier in signal strength order. The GSM BCCH carrier for which the BSIC identification
failed shall not be re-considered for BSIC identification until BSIC identification attempts have been made for all the
rest of the 8 strongest GSM BCCH carriers in the monitored set with unknown BSIC.
Tidentify,GSM values are given for a set of reference gap patterns in table 8.1.2.4.5.1.2.1-1. The requirements in the table
represent the time required to guarantee at least two attempts to decode the BSIC for one GSM BCCH carrier. If inter-
frequency RSTD measurements are configured and the UE requires measurement gaps for performing such
measurements, then Tidentify,GSM shall be based on the 80ms gap configuration.
Table 8.1.2.4.5.1.2.1-1
Tidentify,gsm(ms) Treconfirm,gsm(ms)
ceil(Nfreq,n 40ms gap 80ms gap 40ms gap 80ms gap
* Kn – configuration configuration configuration configuration
Mgsm) (ID 0) (ID 1) (ID 0) (ID 1)
0 2160 5280 1920 5040
1 5280 21760 5040 17280
2 5280 31680 5040 29280
No
3 19440 No requirement 13320 requirement
No
4 31680 No requirement 29280 requirement
No
5 31680 No requirement 29280 requirement
8.1.2.4.5.1.2.2 BSIC re-confirmation
The UE shall maintain the timing information of up to 8 identified GSM cells. Initial timing information is obtained
from the initial BSIC identification. The timing information shall be updated every time the BSIC is decoded.
For each measurement gap used for GSM BSIC reconfirmation as described in clause 8.1.2.4.5.1.2, the UE shall
attempt to decode the BSIC falling within the measurement gap according to table 8.1.2.4.5.1.2.1-1. If more than one
BSIC can be decoded within the same measurement gap, priority shall be given to the least recently decoded BSIC. If
inter-frequency RSTD measurements are configured and the UE requires measurement gaps for performing such
measurements, then Tre-confirm,GSM shall be based on the 80ms gap configuration.
If the UE fails to decode the BSIC after two successive attempts or if the UE has not been able to re-confirm the BSIC
for a GSM cell within Tre-confirm,GSM seconds, the UE shall abort the BSIC re-confirmation attempts for that GSM cell.
The GSM cell shall be treated as a new GSM cell with unidentified BSIC and the GSM cell shall be moved to the initial
BSIC identification procedure, see clause 8.1.2.4.5.1.2.1.
8.1.2.4.5.1.2a Enhanced BSIC verification
In addition to the BSIC verification requirements in clause 8.1.2.4.5.1.2, when the UE receives the GSM cell at levels
down to 10 dB + the reference sensitivity level or reference interference levels as specified in [9] the BSIC
identification requirement in table 8.1.2.4.5.1.2a-1 applies. The BSIC verification requirements in table 8.1.2.4.5.1.2a-1
shall apply when no DRX is used or when DRX cycle length ≤ 40 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 221 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.4.5.1.2a-1
Tenhanced_identify,gsm(ms) Tenhanced_reconfirm,gsm(ms)
40ms gap
40ms gap configuration
configuration when
when interfrequency
interfrequency RSTD
RSTD measurement
measurement is also
is also configured
configured and and the UE
the UE requires requires
measurement measurement
gaps for gaps for
ceil(Nfreq,n 40ms gap performing 40ms gap performing
* Kn – configuration such configuration such
Mgsm) (ID 0) measurements (ID 0) measurements
0 1320 2160 1080 1920
8.1.2.4.5.1.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.
8.1.2.4.5.1.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH.
The event triggered reporting delay requirement is valid when the UE for each GSM carrier in the monitored set can
take the required number of samples during the measurement period TMeasurement Period, GSM (see clause 8.1.2.4.5.1).
The event triggered measurement reporting delay for a GSM cell with verified BSIC , measured without L3 filtering
shall be less than 2*TMeasurement Period, GSM, where TMeasurement Period, GSM is defined in clause 8.1.2.4.5.1. When L3 filtering is
used or IDC autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct
Discovery and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an
additional delay can be expected.
8.1.2.4.5.1.5 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.4.5.1.4.
8.1.2.4.5.2 E-UTRAN FDD – GSM measurements when DRX is used
The requirements in this clause apply only to UE supporting E-UTRAN FDD and GSM.
Measurements on GSM cells can be requested with BSIC verified.
In RRC_CONNECTED state when a supported measurement gap pattern sequence according to Table 8.1.2.1-1 is
configured by E-UTRAN, or the UE supports capability of conducting such measurements without gaps, the UE
shall continuously measure GSM cells, search for new GSM cells given in the monitored set and re-confirm the
BSIC for already detected cells. During DRX or eDRX_CONN periods the UE may use other periods of time
outside the specified measurement gap patterns. The UE is not required to make measurements of GSM cells
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 222 ETSI TS 136 133 V14.3.0 (2017-04)
during DRX or eDRX_CONN periods if a measurement gap pattern has not been configured, unless the UE
supports capability of conducting such measurements without gaps.
8.1.2.4.5.2.1 GSM carrier RSSI
This measurement shall be based on measurement gaps allocated for GSM carrier RSSI measurement as described in
clause 8.1.2.1. A UE supporting GSM measurements shall measure minimum number of 10 GSM carrier RSSI
measurement samples (NGSM carrier RSSI) per DRX or eDRX_CONN cycle. When DRX is used in RRC_CONNECTED
state, the measurement period, TMeasurement Period, GSM, for the GSM carrier RSSI measurement is shown in table
8.1.2.4.5.2.1-1. When eDRX_CONN is used in RRC_CONNECTED state, the measurement period, TMeasurement Period,
GSM, for the GSM carrier RSSI measurement is shown in table 8.1.2.4.5.2.1-2. The parameters Nfreq,n and Kn are defined
in clause 8.1.2.1.1.
Table 8.1.2.4.5.2.1-1: GSM measurement period for large DRX
DRX cycle length (s) Tmeasure,GSM (s) (DRX cycles)
≤0.064 Non DRX Requirements are
applicable
0.064<DRX-cycle≤ Note (6*Kn*Nfreq,n)
0.08
0.08<DRX-cycle≤ 2.56 Note (5*Kn*Nfreq,n)
Note: Time depends upon the DRX cycle in use
Table 8.1.2.4.5.2.1-2: GSM measurement period for large DRX when eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tmeasure,GSM (s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5*Kn*Nfreq,n)
Note: Time depends upon the eDRX_CONN cycle in use
The UE shall meet the measurement accuracy requirements stated for RXLEV in [8], when the given measurement time
allows the UE to take at least 3 GSM carrier RSSI samples per GSM carrier in the monitored set during the
measurement period.
In case the UE is not able to acquire the required number of samples per GSM carrier during one measurement period,
the UE shall measure as many GSM carriers as possible during that measurement period using at least 3 samples per
GSM carrier. The GSM carriers that were not measured during that measurement period shall be measured in the
following measurement periods.
8.1.2.4.5.2.2 BSIC verification
Measurements on a GSM cell can be requested with BSIC verified. The UE shall be able to report the GSM cells with
BSIC verified for those cells where the verification of BSIC has been successful.
The procedure for BSIC verification on a GSM cell can be divided into the following two tasks:
- Initial BSIC identification: Includes searching for the BSIC and decoding the BSIC for the first time when
there is no knowledge about the relative timing between the E-UTRAN FDD and GSM cells.
- BSIC re-confirmation: Tracking and decoding the BSIC of a GSM cell after initial BSIC identification is
performed. The UE shall trigger the BSIC re-confirmation within the available measurement gap pattern
If the network requests measurements on a GSM cell, the UE shall behave as follows:
- The UE shall perform GSM carrier RSSI measurements according to clause 8.1.2.4.5.2.1 when a measurement
gap pattern sequence is activated, or the UE supports capability of conducting such measurements without gaps.
The UE shall perform measurement reporting as defined in TS 36.331 [2].
- The UE shall perform BSIC identification. The UE shall use the most recently available GSM carrier RSSI
measurement results for arranging GSM cells in signal strength order for performing BSIC identification.
- The UE shall perform BSIC re-confirmation on all the GSM cells that have been successfully identified.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 223 ETSI TS 136 133 V14.3.0 (2017-04)
- The UE shall perform all configured event evaluation for event-triggered reporting after the BSIC has been
verified for a GSM cell. The UE shall use the most recently available GSM carrier RSSI measurement results in
event evaluation and event-triggered reporting.
- Event-triggered and periodic reports shall be triggered according to TS 36.331 [2].
The BSIC of a GSM cell is considered to be “verified” if the UE has decoded the SCH of the BCCH carrier and
identified the BSIC at least one time (initial BSIC identification). Once a GSM cell has been identified the BSIC shall
be re-confirmed at least once every 30 seconds. Otherwise the BSIC of the GSM cell is considered as "non-verified".
The UE shall be able to perform BSIC verification at levels down to the reference sensitivity level or reference
interference levels as specified in [9].
8.1.2.4.5.2.2.1 Initial BSIC identification
This measurement shall be made on GSM cells that are requested with BSIC verified.
For DRX cycle length ≤ 40 ms, the initial GSM BSIC identification requirements corresponding to the non DRX
requirements as specified in clause 8.1.2.4.5.1.2.1 shall apply.
For DRX cycle length > 40 ms and any eDRX_CONN cycle, the UE shall make at least one attempt every Kn*Nfreq,n
*30s to decode the BSIC of SCH on the BCCH carrier of the 8 strongest BCCH carriers of the GSM cells indicated in
the Inter-RAT cell info list. If the UE has not successfully decoded the BSIC of the GSM BCCH carrier within
Kn*Nfreq,n *60 s, the UE shall abort the BSIC identification attempts for that GSM BCCH carrier. The UE shall give
priority for BSIC decoding attempts in decreasing signal strength order to BCCH carriers with unknown BSIC. The
strongest BCCH carrier is defined as the BCCH carrier having the highest measured GSM carrier RSSI value. The
parameters Nfreq,n and Kn are defined in clause 8.1.2.1.1.
If the BSIC of the GSM BCCH carrier has been successfully decoded the UE shall continue BSIC identification with
the next GSM BCCH carrier, in signal strength order, with unknown BSIC. The GSM cell for which the BSIC has been
successfully identified shall be moved to the BSIC re-confirmation procedure.
8.1.2.4.5.2.2.2 BSIC re-confirmation
The UE shall maintain the timing information of up to 8 identified GSM cells. Initial timing information is obtained
from the initial BSIC identification. The timing information shall be updated every time the BSIC is decoded.
For DRX cycle length ≤ 40 ms, the GSM BSIC re-conformation requirements corresponding to the non DRX
requirements as specified in clause 8.1.2.4.5.1.2.2 shall apply.
For DRX cycle length > 40 ms and any eDRX_CONN cycle, at least every Kn*Nfreq,n *30 seconds, the UE shall attempt
to decode the BSIC of each identified GSM cell.If the UE fails to decode the BSIC after two successive attempts or if
the UE has not been able to re-confirm the BSIC for a GSM cell within Kn*Nfreq,n *60 seconds, the UE shall abort the
BSIC re-confirmation attempts for that GSM cell. The GSM cell shall be treated as a new GSM cell with unidentified
BSIC and the GSM cell shall be moved to the initial BSIC identification procedure, see clause 8.1.2.4.5.2.2.1. The
parameters Nfreq,n and kn are defined in clause 8.1.2.1.1.
8.1.2.4.5.2.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.
8.1.2.4.5.2.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH.
The event triggered reporting delay requirement is valid when the UE for each GSM carrier in the monitored set can
take the required number of samples during the measurement period TMeasurement Period, GSM (see clause 8.1.2.4.5.2.1).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 224 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay for a GSM cell with verified BSIC , measured without L3 filtering
shall be less than 2*TMeasurement Period, GSM, where TMeasurement Period, GSM is defined in clause 8.1.2.4.5.2.1. When L3 filtering
is used or IDC autonomous denial is configured or the UE is performing reception and/or transmission for ProSe Direct
Discovery and/or ProSe Direct Communication, or the UE is configured to perform SRS carrier based switching, an
additional delay can be expected.
8.1.2.4.5.2.5 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.4.5.2.4.
8.1.2.4.6 E-UTRAN TDD – GSM measurements
The requirements in clause 8.1.2.4.5 also apply for this section.
8.1.2.4.7 E-UTRAN FDD – UTRAN FDD measurements for SON
8.1.2.4.7.1 Identification of a new UTRA FDD cell for SON
No explicit neighbour list is provided to the UE for identifying a UTRA cell for SON. The UE shall identify and report
only the strongest cell when requested by the network for the purpose of SON.
8.1.2.4.7.1.1 Requirements when no DRX is used
When no DRX is used, either measurement gaps are scheduled or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new cell within:
480
Tidentify, UTRA_FDD = Tbasic _ identify _ UTRA_FDD ⋅ ⋅ K n N freq ,n ms (normal performance)
Tinter1
and
480
Tidentify, UTRA_FDD = Tbasic _ identify _ UTRA_FDD ⋅ ⋅ K r N freq ,r ms (reduced performance)
Tinter1
Tbasic_identify_UTRA_FDD = 300 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new UTRA FDD cell is defined.
A cell shall be considered identifiable following conditions are fulfilled:
- CPICH Ec/Io > -20 dB,
- SCH_Ec/Io > -17 dB for at least one channel tap and SCH_Ec/Ior is equally divided between primary
synchronisation code and secondary synchronisation code. When L3 filtering is used an additional delay can be
expected.
If the UE is unable to identify the UTRA cell for SON within 8*Tidentify, UTRA_FDD ms, the UE may stop searching UTRA
cells for SON.
8.1.2.4.7.1.2 Requirements when DRX is used
When DRX or eDRX_CONN is used, either measurement gaps are scheduled or the UE supports capability of
conducting such measurements without gaps, the UE shall be able to identify a new cell within Tidentify, UTRA_FDD. When
DRX is used, Tidentify, UTRA_FDD is as defined in table 8.1.2.4.7.1.2-1, and when eDRX_CONN is used, Tidentify, UTRA_FDD is
as defined in table 8.1.2.4.7.1.2-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 225 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.4.7.1.2-1: Requirement to identify a new UTRA FDD cell for SON
DRX cycle length Tidentify, UTRA_FDD (s) (DRX cycles) (normal Tidentify, UTRA_FDD (s) (DRX cycles) (reduced
(s) requirement) requirement)
Gap period = 40 ms Gap period = 80 ms Gap period = 40 ms Gap period = 80 ms
≤0.04 Non DRX Non DRX Non DRX Non DRX
Requirements in Requirements in Requirements in Requirements in
clause 8.1.2.4.7.1.1are clause 8.1.2.4.7.1.1 clause 8.1.2.4.7.1.1are clause 8.1.2.4.7.1.1
applicable are applicable applicable are applicable
0.04<DRX Note (45*Kn* Nfreq,n) Note (95*Kn * Nfreq,n) Note (45*Kr* Nfreq,r) Note (95*Kr * Nfreq,r)
cycle≤0.08
0.128 3.84*Kn * Nfreq,n (30*Kn 8.0*Kn * Nfreq,n 3.84*Kr * Nfreq,r (30*Kr * 8.0*Kr * Nfreq,r (62.5*Kr
* Nfreq,n) (62.5*Kn * Nfreq,n) Nfreq,r) * Nfreq,r)
0.16 4.0*Kn * Nfreq,n (25*Kn * 8.0*Kn * Nfreq,n (50*Kn 4.0*Kr * Nfreq,r (25*Kr * 8.0*Kr * Nfreq,r (50*Kr *
Nfreq,n) * Nfreq,n) Nfreq,r) Nfreq,r)
0.256 6.4*Kn * Nfreq,n (25*Kn * 8.96*Kn * Nfreq,n 6.4*Kr * Nfreq,r (25*Kr * 8.96*Kr * Nfreq,r (35*Kr
Nfreq,n) (35*Kn * Nfreq,n) Nfreq,r) * Nfreq,r)
0.32 8*Kn * Nfreq,n (25*Kn * 8.96*Kn * Nfreq,n 8*Kr * Nfreq,r (25*Kr * 8.96*Kr * Nfreq,r (28*Kr
Nfreq,n) (28*Kn * Nfreq,n) Nfreq,r) * Nfreq,r)
0.32<DRX Note (25*Kn * Nfreq,n) Note (25*Kn * Nfreq,n) Note (25*Kr * Nfreq,r) Note (25*Kr * Nfreq,r)
cycle≤2.56
Note: Time depends upon the DRX cycle in use
Table 8.1.2.4.7.1.2-2: Requirement to identify a new UTRA FDD cell for SON when eDRX_CONN cycle
is used
eDRX_CONN Tidentify, UTRA_FDD (s) (eDRX_CONN cycles) Tidentify, UTRA_FDD (s) (eDRX_CONN cycles)
cycle length (s) (normal requirement) (reduced requirement)
Gap period = 40 ms Gap period = 80 ms Gap period = 40 ms Gap period = 80 ms
2.56<eDRX_CONN Note (25*Kn * Nfreq,n) Note (25*Kn * Nfreq,n) Note (25*Kr * Nfreq,r) Note (25*Kr * Nfreq,r)
cycle≤10.24
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered identifiable provided following conditions are fulfilled:
- CPICH Ec/Io > -20 dB,
- SCH_Ec/Io > -17 dB for at least one channel tap and SCH_Ec/Ior is equally divided between primary
synchronisation code and secondary synchronisation code. When L3 filtering is used an additional delay can be
expected.
If the UE is unable to identify the UTRA cell for SON within 8*Tidentify, UTRA_FDD seconds, the UE may stop searching
UTRA cells for SON; when DRX is used Tidentify, UTRA_FDD is defined in table 8.1.2.4.7.1.2-1, and when eDRX_CONN is
used Tidentify, UTRA_FDD is defined in table 8.1.2.4.7.1.2-2.
8.1.2.4.7.1.3 Reporting Delay
The UE shall not report the physical cell identity of an identifiable cell for SON as long as the reporting criteria are not
fulfilled.
The reporting delay is defined as the time between the identification of the strongest cell for SON until the UE starts to
transmit its physical cell identity over the Uu interface. This requirement assumes that the reporting of the physical cell
identity is not delayed by other RRC signalling on the DCCH. This reporting delay excludes a delay uncertainty
resulted when inserting the physical cell identity of the strongest cell for SON to the TTI of the uplink DCCH. The
delay uncertainty is twice the TTI of the uplink DCCH. This reporting delay excludes any delay caused by
unavailability of UL resources for UE sending the physical cell identity of the strongest cell for SON.
The reporting delay of the physical cell identity of the strongest cell for SON without L3 filtering shall be less than
Tidentify, UTRA_FDD defined in clause 8.1.2.4.7.1.1 and in clause 8.1.2.4.7.1.2 for non DRX and DRX or eDRX_CONN
cases respectively. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 226 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.4.8 E-UTRAN TDD – UTRAN FDD measurements for SON
The requirements in clause 8.1.2.4.7 also apply for this section.
8.1.2.4.9 E-UTRAN FDD – cdma2000 1xRTT measurements
UE shall perform cdma2000 1xRTT measurements according to the procedure defined in [15] on the cdma2000 1xRTT
neighbor cells indicated by the serving eNode B. If measurement gaps are required, the UE shall perform cdma2000
1xRTT measurements only during the measurement gaps configured by the serving eNode B.
8.1.2.4.9.1A E-UTRAN FDD – cdma2000 1xRTT measurements when no DRX is used
When measurement gaps are scheduled for CDMA2000 1xRTT inter RAT measurements, or the UE supports capability
of conducting such measurements without gaps, the UE physical layer shall be capable of reporting CDMA2000 1xRTT
Pilot Strength measurements to higher layers with measurement accuracy as specified in Clause 9.5, corresponding to a
90% measurement success rate, with measurement period given by
Tmeasurement_CDMA2000_1x = Tbasic _ measurement _ CDMA2000_1x ⋅ N freq, n ⋅ K n ⋅ S gap
where Tbasic_measurement_CDMA2000_1x = 100 ms and the measurement gap specific scale factor Sgap is based on the
measurement gap pattern in use as defined in Table 8.1.2.4.9.1-1. If inter-frequency RSTD measurements are
configured and the UE requires measurement gaps for performing such measurements, then Sgap shall be based to the
Gap Pattern Id 1.
Table 8.1.2.4.9.1-1: Gap Pattern Specific Scale Factor
Gap Pattern Id Sgap
0 32/3
1 64/3
8.1.2.4.9.1 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.
The measurement reporting delay of each periodic report is defined as the time between the end of the last measurement
period and the moment when the UE starts to transmit the measurement report over the Uu interface. This delay shall be
less than T71m defined in [15] for each periodic report. This measurement reporting delay excludes a delay which is
caused by the unavailability of the uplink resources for the UE to send the measurement report.
8.1.2.4.10 E-UTRAN TDD – cdma2000 1xRTT measurements
The requirements in clause 8.1.2.4.9 also apply for this section.
8.1.2.4.11 E-UTRAN FDD – HRPD measurements
UE shall perform HRPD measurements according to the procedure defined in [11] on the HRPD neighbor cells
indicated by the serving eNode B. If measurement gaps are required, the UE shall perform HRPD measurements only
during the measurement gaps configured by the serving eNode B.
8.1.2.4.12 E-UTRAN TDD – HRPD measurements
The requirements in clause 8.1.2.4.11 also apply for this section.
8.1.2.4.13 E-UTRAN TDD – UTRAN TDD measurements for SON
8.1.2.4.13.1 Identification of a new UTRA TDD cell for SON
No explicit neighbour list is provided to the UE for identifying a UTRA TDD cell for SON. The UE shall identify and
report only the strongest cell when requested by the network for the purpose of SON.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 227 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.4.13.1.1 Requirements when no DRX is used
When no DRX is used, either measurement gaps are scheduled or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new cell within:
480
Tidentify, UTRA_TDD = Tbasic _ identify _ UTRA_TDD ⋅ ⋅ K n ⋅ N freq ,n ms (normal performance)
Tinter1
and
480
Tidentify, UTRA_TDD = Tbasic _ identify _ UTRA_TDD ⋅ ⋅ K r ⋅ N freq ,r ms (reduced performance)
Tinter1
Tbasic_identify_UTRA_TDD = 800 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new UTRA TDD cell is defined.
A cell shall be considered identifiable following conditions are fulfilled:
- P-CCPCH Ec/Io > -8 dB,
- DwPCH_Ec/Io > -5 dB.
When L3 filtering is used an additional delay can be expected.
If the UE is unable to identify the UTRA TDD cell for SON within 8*Tidentify, UTRA_TDD ms, the UE may stop searching
UTRA TDD cells for SON.
8.1.2.4.13.1.2 Requirements when DRX is used
When DRX or eDRX_CONN is used, either measurement gaps are scheduled or the UE supports capability of
conducting such measurements without gaps, the UE shall be able to identify a new cell within Tidentify, UTRA_TDD. When
DRX is used, Tidentify, UTRA_TDD is as defined in table 8.1.2.4.13.1.2-1, and when eDRX_CONN is used, Tidentify, UTRA_TDD
is as defined in table 8.1.2.4.13.1.2-2.
Table 8.1.2.4.13.1.2-1: Requirement to identify a new UTRA TDD cell for SON
DRX cycle length Tidentify, UTRA_TDD (s) (DRX cycles) Tidentify, UTRA_TDD (s) Tidentify, UTRA_TDD (s)
(s) (DRX cycles) (DRX cycles)
Gap period = 40 ms Gap period = 80 ms Gap period = 40 ms Gap period = 80 ms
≤0.16 Non DRX Non DRX Non DRX Non DRX
Requirements in Requirements in Requirements in Requirements in
clause 8.1.2.4.3.1 clause 8.1.2.4.3.1 are clause 8.1.2.4.3.1 are clause 8.1.2.4.3.1 are
are applicable applicable applicable applicable
0.16<DRX Note (25*Kn* Nfreq,n) Note (50*Kn * Nfreq,n) Note (25*Kr* Nfreq,r) Note (50*Kr * Nfreq,r)
cycle≤0.256
0.256<DRX Note (25*Kn * Nfreq,n) Note (45*Kn * Nfreq,n) Note (25*Kr * Nfreq,r) Note (45*Kr * Nfreq,r)
cycle≤0.32
0.32<DRX Note (25*Kn * Nfreq,n) Note (25*Kn * Nfreq,n) Note (25*Kr * Nfreq,r) Note (25*Kr * Nfreq,r)
cycle≤2.56
Note: Time depends upon the DRX cycle in use
Table 8.1.2.4.13.1.2-2: Requirement to identify a new UTRA TDD cell for SON when eDRX_CONN cycle
is used
eDRX_CONN Tidentify, UTRA_TDD (s) (eDRX_CONN cycles) Tidentify, UTRA_TDD (s) (eDRX_CONN cycles)
cycle length (s)
Gap period = 40 ms Gap period = 80 ms Gap period = 40 ms Gap period = 80 ms
2.56<eDRX_CONN Note (25*Kn * Nfreq,n) Note (25*Kn * Nfreq,n) Note (25*Kr * Nfreq,r) Note (25*Kr * Nfreq,r)
cycle≤10.24
Note: Time depends upon the eDRX_CONN cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 228 ETSI TS 136 133 V14.3.0 (2017-04)
A cell shall be considered identifiable provided following conditions are fulfilled:
- P-CCPCH Ec/Io > -8 dB,
- DwPCH_Ec/Io > -5 dB.
When L3 filtering is used an additional delay can be expected.
If the UE is unable to identify the UTRA TDD cell for SON within 8*Tidentify, UTRA_TDD seconds, the UE may stop
searching UTRA TDD cells for SON; when DRX is used Tidentify, UTRA_TDD is defined in table 8.1.2.4.13.1.2-1, and when
eDRX_CONN is used Tidentify, UTRA_TDD is defined in table 8.1.2.4.13.1.2-2.
8.1.2.4.13.1.3 Reporting Delay
The UE shall not report the physical cell identity of an identifiable cell for SON as long as the reporting criteria are not
fulfilled.
The reporting delay is defined as the time between the identification of the strongest cell for SON until the UE starts to
transmit its physical cell identity over the Uu interface. This requirement assumes that the reporting of the physical cell
identity is not delayed by other RRC signalling on the DCCH. This reporting delay excludes a delay uncertainty
resulted when inserting the physical cell identity of the strongest cell for SON to the TTI of the uplink DCCH. The
delay uncertainty is twice the TTI of the uplink DCCH. This reporting delay excludes any delay caused by
unavailability of UL resources for UE sending the physical cell identity of the strongest cell for SON.
The reporting delay of the physical cell identity of the strongest cell for SON without L3 filtering shall be less than
Tidentify, UTRA_TDD defined in clause 8.1.2.4.13.1.1 and in clause 8.1.2.4.13.1.2 for non DRX and DRX and eDRX_CONN
cases respectively. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
8.1.2.4.14 E-UTRAN FDD – UTRAN TDD measurements for SON
The requirements in clause 8.1.2.4.13 also apply for this section.
8.1.2.4.15 E-UTRAN FDD – cdma2000 1xRTT measurements for SON ANR
8.1.2.4.15.1 Identification of a new cdma2000 1xRTT cell for SON ANR
No explicit neighbour list is provided to the UE for identifying a cdma2000 1xRTT cell for SON ANR. The UE shall
identify and report only the strongest cell when requested by the network for the purpose of SON ANR.
8.1.2.4.15.1.1 Requirement when no DRX is used
When measurement gaps are scheduled for CDMA2000 1xRTT inter RAT measurements, or the UE supports capability
of conducting such measurements without gaps, the UE physical layer shall be capable of reporting CDMA2000 1xRTT
Pilot Strength measurements to higher layers with measurement accuracy as specified in Clause 9.5, corresponding to a
90% measurement success rate, with measurement period given by
Tmeasurement_CDMA2000_1x = Tbasic _ measurement _ CDMA2000_1x ⋅ N freq, n ⋅ K n ⋅ S gap
where Tbasic_measurement_CDMA2000_1x = 100 ms and the measurement gap specific scale factor Sgap is based on the
measurement gap pattern in use as defined in Table 8.1.2.4.15.1.1-1. If inter-frequency RSTD measurements are
configured and the UE requires measurement gaps for performing such measurements, then Sgap shall be based to the
Gap Pattern Id 1.
Table 8.1.2.4.15.1.1-1: Gap Pattern Specific Scale Factor
Gap Pattern Id Sgap
0 32/3
1 64/3
If the UE is unable to identify the CDMA2000 1xRTT cell for SON ANR within [TBD] ms, the UE may stop searching
CDMA2000 1xRTT cells for SON ANR.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 229 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.4.15.1.2 Reporting Delay
The UE shall not report the physical cell identity of an identifiable cell for SON ANR as long as the reporting criteria
are not fulfilled.
The reporting delay is defined as the time between the identification of the strongest cell for SON ANR until the UE
starts to transmit its physical cell identity over the Uu interface. This delay shall be less than T71m defined in [15]. This
measurement reporting delay excludes a delay which is caused by the unavailability of the uplink resources for the UE
to send the measurement report.
8.1.2.4.16 E-UTRAN TDD – cdma2000 1xRTT measurements for SON ANR
The requirements in clause 8.1.2.4.15 also apply for this section.
8.1.2.4.17 E-UTRAN FDD-UTRAN FDD measurements with autonomous gaps
The requirements in this clause apply only to UE supporting E-UTRA FDD and UTRA FDD.
8.1.2.4.17.1 Identification of a new CGI of UTRA FDD cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of UTRA FDD cell. The UE shall identify
and report the CGI when requested by the network for the purpose of ‘reportCGI’. The UE may make autonomous gaps
in both downlink reception and uplink transmission for decoding SFN and receiving UTRAN MIB and SIB3 messages
according to clause 5.5.3.1 of TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO
is set to false. If autonomous gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether
DRX or eDRX_CONN is used or not, the UE shall be able to identify a new CGI of UTRA FDD cell within:
Tidentify_CGI, UTRAN FDD = 630 + 40*SIB3_REP ms
where SIB3_REP is the repetition period at which the UTRAN cell schedules SIB3 blocks in units of frames specified
in TS 25.331 [7] , provided that the UTRAN cell has been already identified by the UE.
This requirement is applicable for UTRA FDD target cell configurations where the information required to make the SI
report can be determined from the MIB and SIB3 alone, and MIB and SIB3 are not segmented into multiple TTIs.
Additionally, for the requirement to be applicable, the reception conditions shall be such that the system frame number
of the target UTRA FDD cell, the MIB and SIB3 can each be successfully decoded in no more than four attempts.
According to the reception conditions:
A cell shall be considered identifiable following conditions are fulfilled:
- CPICH Ec/Io > -20 dB,
- SCH_Ec/Io > -17 dB for at least one channel tap and SCH_Ec/Ior is equally divided between primary
synchronisation code and secondary synchronisation code. When L3 filtering is used an additional delay can be
expected.The system frame number, the MIB and SIB3 of the target cell shall be considered decodable provided
the BCH demodulation requirements are met according to [29].
The requirement for identifying a new CGI of an UTRA FDD cell within Tidentify_CGI, UTRAN FDD is applicable when no
DRX is used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
8.1.2.4.17.2 CGI Reporting Delay
The CGI reporting delay occurs due to the delay uncertainty when inserting the CGI measurement report to the TTI of
the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the CGI reporting
may be delayed until the next DRX cycle. In case eDRX is used, the CGI reporting may be delayed until the next
eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.1.2.4.18 E-UTRAN TDD-UTRAN FDD measurements with autonomous gaps
The requirements in this clause apply only to UE supporting E-UTRA TDD and UTRA FDD.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 230 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.4.18.1 Identification of a new CGI of UTRA FDD cell with autonomous gaps
The requirements in clause 8.1.2.4.17.1 also apply for this section.
8.1.2.4.18.2 CGI Reporting Delay
The requirements in clause 8.1.2.4.17.2 also apply for this section.
8.1.2.4.19 E-UTRAN FDD – WLAN measurements
8.1.2.4.19.1 Introduction
The requirements in this section shall apply for a UE capable of E-UTRA FDD and LTE-WLAN Aggregation [2].
8.1.2.4.19.2 Requirements
8.1.2.4.19.2.1 E-UTRAN FDD – WLAN measurements when no DRX is used
In the RRC_CONNECTED state when no DRX is used the measurement period for WLAN RSSI shall be TWLAN_RSSI as
defined in table 8.1.2.4.19.2.1-1.
The value of TWLAN_RSSI depends upon whether the WLAN RSSI measurement is performed on the serving access point
(AP) or on a neighbour AP and in case of the neighbour AP whether the neighbour AP is known or unknown to the UE:
- Measurement of known single neighbor AP is time-sensitive and is performed on the AP for which information
about the operating channel is known to the UE; and
- - Measurement of unknown neighbor AP is not time-sensitive and is performed on the AP for which information
about the operating channel is not known to the UE.
The UE shall be capable of performing WLAN RSSI measurements for certain minimum number of APs during
TWLAN_RSSI as defined in table 8.1.2.4.19.2.1-1 provided that the beacon frame of the measured AP is available at the UE
at least once every 102.4 ms. The UE physical layer shall be capable of reporting WLAN RSSI measurements to higher
layers with the measurement period of TWLAN_RSSI.
Table 8.1.2.4.19.2.1-1: WLAN RSSI measurement period
WLAN RSSI measurement configuration TWLAN_RSSI [seconds]
Minimum number of APs
Type of Measurement
measured during TWLAN_RSSI
Measurement of serving AP 1 0.5
Measurement of known neighbor AP on a single
1 5
channel
Measurement of multiple unknown neighbor APs 3 30
The WLAN RSSI measurement accuracy for all measured access points shall be fulfilled according to the accuracy as
specified in the sub-clause 9.7.1.
8.1.2.4.19.2.2 E-UTRAN FDD – WLAN measurements when DRX is used
In the RRC_CONNECTED state when DRX is used the measurement period for WLAN RSSI shall be TRSSI_DRX as
defined in table 8.1.2.4.19.2.2-1.
The value of TWLAN_RSSI_DRX depends upon whether the WLAN RSSI measurement is performed on the serving access
point (AP) or on a neighbour AP and in case of the neighbour AP whether the neighbour AP is known or unknown to
the UE:
- Measurement of known single neighbor AP is time-sensitive and is performed on the AP for which information
about the operating channel is known to the UE; and
- Measurement of unknown neighbor AP is not time-sensitive and is performed on the AP for which information
about the operating channel is not known to the UE
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 231 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall be capable of performing WLAN RSSI measurements for certain minimum number of APs during
TWLAN_RSSI_DRX as defined in table 8.1.2.4.19.2.2-1 provided that the beacon frame of the measured AP is available at the
UE at least once every 102.4 ms. The UE physical layer shall be capable of reporting WLAN RSSI measurements to
higher layers with the measurement period of TWLAN_RSSI_DRX.
Table 8.1.2.4.19.2.2-1: Requirement to measure WLAN RSSI in DRX
WLAN RSSI measurement configuration DRX cycle length (s) TWLAN_RSSI_DRX (s)
Minimum number of
Type of Measurement APs measured
during TWLAN_RSSI
Measurement of serving AP 1 0.002 ≤ DRX-cycle ≤ 0.320 MAX (0.5, 5*LDRX)
Measurement of one known 0.002 ≤ DRX-cycle ≤ 0.320 MAX (5, 25*LDRX)
neighbor AP on a single 1 0.320 < DRX-cycle ≤ 2.56 MAX (5, 20*LDRX)
channel
Measurement of 3 unknown 0.002 ≤ DRX-cycle ≤ 0.320 MAX (30, 150*LDRX)
3
neighbor APs 0.320 < DRX-cycle ≤ 2.56 MAX (30, 120*LDRX)
Note 1: LDRX is the length of DRX cycle in second(s)
The WLAN RSSI measurement accuracy for all measured access points shall be fulfilled according to the accuracy as
specified in the sub-clause 9.7.1.
8.1.2.4.19.2.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in clause 9.7.1.
8.1.2.4.19.2.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in clause 9.7.1.
The UE shall not send any event triggered measurement reports, as long as the reporting criteria is not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report until
the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that the measurement
report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay
uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is
twice the TTI of the uplink DCCH. This measurement reporting delay excludes a delay which caused by no UL
resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than TWLAN_RSSI when no
DRX is used as defined in section 8.1.2.4.19.2.1 and TWLAN_RSSI_DRX when DRX is used as defined in section
8.1.2.4.19.2.2. When L3 filtering is used or IDC autonomous denial or the UE is performing reception and/or
transmission for ProSe Direct Discovery and/or ProSe Direct Communication, or the UE is configured to perform SRS
carrier based switching,an additional delay can be expected.
8.1.2.4.19.2.5 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.7.1.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.4.19.2.3.
8.1.2.4.20 E-UTRAN TDD – WLAN measurements
The requirements in this section shall apply for a UE capable of E-UTRA TDD and LTE-WLAN Aggregation [2].
The requirements in clause 8.1.2.4.19 also apply for this section.
8.1.2.5 E-UTRAN OTDOA Intra-Frequency RSTD Measurements
All intra-frequency RSTD measurement requirements specified in Sections 8.1.2.5.1 and 8.1.2.5.2 shall apply without
DRX as well as for any DRX and eDRX_CONN cycles specified in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 232 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.5.1 E-UTRAN FDD Intra-Frequency OTDOA Measurements
When the physical layer cell identities of neighbour cells together with the OTDOA assistance data are provided, the
UE shall be able to detect and measure intra-frequency RSTD, specified in TS 36.214 [4], for at least n=16 cells,
including the reference cell, on the same carrier frequency f1 as that of the reference cell within
TRSTD IntraFreqFDD, E - UTRAN ms as given below (see also Figure 8.1.2.5.1-1):
TRSTD IntraFreqFDD, E - UTRAN = TPRS ⋅ ( M - 1) + Δ ms ,
where
TRSTD IntraFreqFDD, E - UTRAN is the total time for detecting and measuring at least n cells,
TPRS is the cell-specific positioning subframe configuration period as defined in TS 36.211 [16],
M is the number of PRS positioning occasions as defined in Table 8.1.2.5.1-1, where each PRS positioning occasion
comprises of N PRS (1≤ N PRS ≤6) consecutive downlink positioning subframes defined in TS 36.211 [16], and
⎡n⎤
Δ = 160 ⋅ ⎢ ⎥ ms is the measurement time for a single PRS positioning occasion which includes the sampling time
⎢M ⎥
and the processing time.
Table 8.1.2.5.1-1: Number of PRS positioning occasions within TRSTD IntraFreqFDD, E - UTRAN
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS f1 Note1 f1 and f2 Note2
160 ms 16 32
>160 ms 8 16
Note 1: When only intra-frequency RSTD measurements are performed over cells belonging to the
serving FDD carrier frequency f1.
Note 2: When intra-frequency RSTD and inter-frequency RSTD measurements are performed over cells
belonging to the serving FDD carrier frequency f1 and one inter-frequency carrier frequency f2,
respectively.
The UE physical layer shall be capable of reporting RSTD for the reference cell and all the neighbor cells i out of at
least (n-1) neighbor cells within TRSTD IntraFreqFDD, E - UTRAN provided:
(PRS Ê / Iot ) ≥-6 dB for all Frequency Bands for the reference cell,
s ref
(PRS Ê / Iot ) ≥-13 dB for all Frequency Bands for neighbour cell i,
s i
(PRS Ê / Iot ) and (PRS Ê / Iot ) conditions apply for all subframes of at least L = M2
s ref s i
PRS positioning
occasions,
PRP 1,2|dBm according to Annex B.2.5 for a corresponding Band
PRS Ê s / Iot is defined as the ratio of the average received energy per PRS RE during the useful part of the symbol to
the average received power spectral density of the total noise and interference for this RE, where the ratio is measured
over all REs which carry PRS.
The time TRSTD IntraFreqFDD, E - UTRAN starts from the first subframe of the PRS positioning occasion closest in time after
both the OTDOA-RequestLocationInformation message and the OTDOA assistance data in the OTDOA-
ProvideAssistanceData message as specified in TS 36.355 [24], are delivered to the physical layer of the UE as
illustrated in Figure 8.1.2.5.1-1.
The RSTD measurement accuracy for all measured neighbor cells i shall be fulfilled according to the accuracy as
specified in the sub-clause 9.1.10.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 233 ETSI TS 136 133 V14.3.0 (2017-04)
If the intra-frequency handover occurs while intra-frequency RSTD measurements are being performed then the UE
shall complete the ongoing OTDOA measurement session. The UE shall also meet the intra-frequency OTDOA
measurement and accuracy requirements. However in this case the RSTD measurement period
( TRSTD IntraFreqFDD, E- UTRAN, HO ) shall be according to the following expression:
TRSTD IntraFreqFDD, E - UTRAN, HO = TRSTD IntraFreqFDD, E - UTRAN + K × TPRS + THO ms ,
where:
K is the number of times the intra-frequency handover occurs during TRSTD IntraFreqFDD, E-UTRAN, HO .
THO is the time during which the intra-frequency RSTD measurement may not be possible due to intra-frequency
handover; it can be up to 45 ms.
TRSTDIntraFreqFDD, E-
The last of OTDOA assistance
data and OTDOA Request
Location Information received
by higher layers TPRS Δ
The last of OTDOA assistance
data and OTDOA Request
Location Information received
by physical layer ...
Tim
PRS positioning
Figure 8.1.2.5.1-1. Illustration of the RSTD reporting time requirement in an FDD system.
Furthermore, due to the intra-frequency handover the UE shall meet the RSTD measurement accuracy for a PRS
bandwidth which is not larger than the minimum channel bandwidth of all the PCells during the RSTD measurement
period.
8.1.2.5.1.1 RSTD Measurement Reporting Delay
This requirement assumes that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
8.1.2.5.2 E-UTRAN TDD Intra-Frequency OTDOA Measurements
When the physical layer cell identities of neighbour cells together with the OTDOA assistance data are provided, the
UE shall be able to detect and measure intra-frequency RSTD, specified in TS 36.214 [4], for at least n=16 cells,
including the reference cell, on the same carrier frequency f1 as that of the reference cell within
TRSTD IntraFreqTDD, E - UTRAN ms as given below:
TRSTD IntraFreqTDD, E - UTRAN = TPRS ⋅ ( M - 1) + Δ ms ,
where
TRSTD IntraFreqTDD, E - UTRAN is the total time for detecting and measuring at least n cells,
TPRS is the cell-specific positioning subframe configuration period as defined in TS 36.211 [16],
M is the number of PRS positioning occasions as defined in Table 8.1.2.5.2-1, where a PRS positioning occasion is as
defined in Clause 8.1.2.5.1, and
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 234 ETSI TS 136 133 V14.3.0 (2017-04)
⎡n⎤
Δ = 160 ⋅ ⎢ ⎥ ms is the measurement time for a single PRS positioning occasion which includes the sampling time
⎢M ⎥
and the processing time.
Table 8.1.2.5.2-1: Number of PRS positioning occasions within TRSTD IntraFreqTDD, E - UTRAN
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS f1 Note1 f1 and f2 Note2
160 ms 16 32
>160 ms 8 16
Note 1: When only intra-frequency RSTD measurements are performed over cells belonging to the
serving TDD carrier frequency f1.
Note 2: When intra-frequency RSTD and inter-frequency RSTD measurements are performed over cells
belonging to the serving TDD carrier frequency f1 and one inter-frequency carrier frequency f2
respectively.
The UE physical layer shall be capable of reporting RSTD for the reference cell and all the neighbor cells i out of at
least (n-1) neighbor cells within TRSTD IntraFreqTDD, E - UTRAN provided:
(PRS Ê / Iot ) ≥-6 dB for all Frequency Bands for the reference cell,
s ref
(PRS Ê / Iot ) ≥-13 dB for all Frequency Bands for neighbour cell i,
s i
(PRS Ê / Iot ) and (PRS Ê / Iot ) conditions apply for all subframes of at least L = M2
s ref s i
PRS positioning
occasions,
PRP 1,2|dBm according to Annex B.2.5 for a corresponding Band
PRS Ê s / Iot is as defined in Clause 8.1.2.5.1.
The time TRSTD IntraFreqTDD, E - UTRAN starts from the first subframe of the PRS positioning occasion closest in time after
both the OTDOA-RequestLocationInformation message and the OTDOA assistance data in the OTDOA-
ProvideAssistanceData message as specified in TS 36.355 [24], are delivered to the physical layer of the UE.
The RSTD measurement accuracy for all measured neighbor cells i shall be fulfilled according to the accuracy as
specified in the sub-clause 9.1.10.1.
If the intra-frequency handover occurs while intra-frequency RSTD measurements are being performed then the UE
shall complete the ongoing OTDOA measurement session. The UE shall also meet the intra-frequency OTDOA
measurement and accuracy requirements. However in this case the RSTD measurement period
( TRSTD IntraFreqTDD, E- UTRAN, HO ) shall be according to the following expression:
TRSTD IntraFreqTDD, E - UTRAN, HO = TRSTD IntraFreqTDD, E - UTRAN + K × TPRS + THO ms ,
where:
K is the number of times the intra-frequency handover occurs during TRSTD IntraFreqTDD, E-UTRAN, HO ,
THO is the time during which the intra-frequency RSTD measurement may not be possible due to intra-frequency
handover; it can be up to 45 ms.
Furthermore, due to the intra-frequency handover the UE shall meet the RSTD measurement accuracy for a PRS
bandwidth which is not larger than the minimum channel bandwidth of all the PCells during the RSTD measurement
period.
The intra-frequency requirements in this clause (8.1.2.5.2) shall apply for all TDD special subframe configurations
specified in TS 36.211 [16] and for the TDD uplink-downlink configurations as specified in Table 8.1.2.5.2-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 235 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.5.2-2: TDD uplink-downlink subframe configurations applicable for TDD intra-frequency
requirements
PRS Transmission Bandwidth [RB] Applicable TDD uplink-downlink configurations
6, 15 1, 2, 3, 4 and 5
25, 50, 75, 100 0, 1, 2, 3, 4, 5 and 6
Note: Uplink-downlink configurations are specified in Table 4.2-2 in TS 36.211 [16].
8.1.2.5.2.1 RSTD Measurement Reporting Delay
This requirement assumes that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
8.1.2.6 E-UTRAN Inter-Frequency OTDOA Measurements
All inter-frequency RSTD measurement requirements specified in Sections 8.1.2.6.1-8.1.2.6.4 shall apply, provided that
- the UE is capable of inter-frequency RSTD measurements for OTDOA [24], and
- either the measurement gap pattern ID # 0 specified in Clause 8.1.2.1 is used or the UE supports capability of
conducting inter-frequency measurements without gaps.
All inter-frequency RSTD measurement requirements specified in Sections 8.1.2.6.1-8.1.2.6.4 shall apply without DRX
as well as for any DRX or eDRX_CONN cycles specified in TS 36.331 [2].
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.1.2.6 provided
the following condition is met:
- all positioning subframes indicated in the OTDOA assistance data and specified in Section 9.1.10 are available
for RSTD measurements at the UE in the measured and reference cells.
The requirements in this section shall also appy, when the UE is configured to perform SRS carrier based switching and
using measurement gaps.
8.1.2.6.1 E-UTRAN FDD-FDD Inter-Frequency OTDOA Measurements
When the physical layer cell identities of neighbour cells together with the OTDOA assistance data are provided, the
UE shall be able to detect and measure inter-frequency RSTD, specified in TS 36.214 [4], for at least n=16 cells,
including the reference cell, within TRSTD InterFreqFDD, E - UTRAN ms as given below:
TRSTD InterFreqFDD, E - UTRAN = TPRS ⋅ ( M - 1) + Δ ms ,
where
TRSTD InterFreqFDD, E - UTRAN is the total time for detecting and measuring at least n cells,
TPRS is the the largest value of the cell-specific positioning subframe configuration period, defined in TS 36.211 [16],
among the measured n cells including the reference cell,
M is the number of PRS positioning occasions as defined in Table 8.1.2.6.1-1, where a PRS positioning occasion is as
defined in clause 8.1.2.5.1,
⎡n⎤
Δ = 160 ⋅ ⎢ ⎥ ms is the measurement time for a single PRS positioning occasion which includes the sampling time
⎢M ⎥
and the processing time, and
the n cells are distributed on up to two carrier frequencies including a serving carrier frequency and one inter-frequency
carrier.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 236 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.6.1-1: Number of PRS positioning occasions within TRSTD InterFreqFDD, E - UTRAN
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS f2 Note1 f1 and f2 Note2
160 ms 16 32
>160 ms 8 16
Note 1: When inter-frequency RSTD measurements are performed over the reference cell and neighbour
cells, which belong to the FDD inter-frequency carrier frequency f2.
Note 2: When inter-frequency RSTD measurements are performed over the reference cell and the
neighbour cells, which belong to the serving FDD carrier frequency f1 and the FDD inter-frequency carrier
frequency f2 respectively.
The UE physical layer shall be capable of reporting RSTD for the reference cell and all the neighbor cells i out of at
least (n-1) neighbor cells within TRSTD InterFreqFDD, E - UTRAN provided:
(PRS Ê / Iot ) ≥-6 dB for all Frequency Bands for the reference cell,
s ref
(PRS Ê / Iot ) ≥-13 dB for all Frequency Bands for neighbour cell i,
s i
(PRS Ê / Iot ) and (PRS Ê / Iot ) conditions apply for all subframes of at least L = M2
s ref s i
PRS positioning
occasions,
PRP 1,2|dBm according to Annex B.2.6 for a corresponding Band
PRS Ê s / Iot is as defined in Clause 8.1.2.5.1.
The time TRSTD InterFreqFDD, E - UTRAN starts from the first subframe of the PRS positioning occasion closest in time after
both the OTDOA-RequestLocationInformation message and the OTDOA assistance data in the OTDOA-
ProvideAssistanceData message as specified in TS 36.355 [24], are delivered to the physical layer of the UE.
If the inter-frequency handover occurs while inter-frequency RSTD measurements are being performed, and the inter-
frequency carrier on which RSTD is measured becomes the new serving carrier frequency after the inter-frequency
handover, the UE shall complete the ongoing OTDOA measurement session. The UE shall also meet the inter-
frequency OTDOA measurement and accuracy requirements. However in this case the RSTD measurement period
( TRSTD InterFreqFDD, E-UTRAN, HO ) shall be according to the following expression:
TRSTD InterFreqFDD, E - UTRAN, HO = TRSTD InterFreqFDD, E - UTRAN + K × TPRS + THO ms ,
where:
K is the number of times the inter-frequency handover occurs during TRSTD InterFreqFDD, E-UTRAN, HO ,
THO is the time during which the inter-frequency RSTD measurement may not be possible due to inter-frequency
handover; it can be up to 45 ms.
The RSTD measurement accuracy for all measured neighbor cells i shall be fulfilled according to the accuracy as
specified in the sub-clause 9.1.10.2.
Furthermore, due to the inter-frequency handover the UE shall meet the RSTD measurement accuracy for a PRS
bandwidth which is not larger than the minimum channel bandwidth of those PCells on whose carriers RSTD
measurement is performed during the RSTD measurement period.
8.1.2.6.1.1 RSTD Measurement Reporting Delay
This requirement assumes that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 237 ETSI TS 136 133 V14.3.0 (2017-04)
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
8.1.2.6.2 E-UTRAN TDD-FDD Inter-Frequency OTDOA Measurements
When the physical layer cell identities of neighbour cells together with the OTDOA assistance data are provided, the
UE shall be able to detect and measure inter-frequency RSTD, specified in TS 36.214 [4], for at least n=16 cells,
TRSTD InterFreqT DDFDD, E- UTRAN
including the reference cell, within ms as given below:
TRSTD InterFreqT DDFDD, E - UTRAN = TPRS ⋅ ( M - 1) + Δ ms
,
where
TRSTD InterFreqT DDFDD, E- UTRAN is the total time for detecting and measuring at least n cells,
TPRS is the largest value of the cell-specific positioning subframe configuration period, defined in TS 36.211 [16],
among the measured n cells including the reference cell,
M is the number of PRS positioning occasions as defined in Table 8.1.2.6.2-1, where a PRS positioning occasion is as
defined in clause 8.1.2.5.1,
⎡n⎤
Δ = 160 ⋅ ⎢ ⎥
ms is the measurement time for a single PRS positioning occasion which includes the sampling time
⎢M ⎥
and the processing time, and
the n cells are distributed on up to two carrier frequencies including a serving carrier frequency and one inter-frequency
carrier.
Table 8.1.2.6.2-1: Number of PRS positioning occasions within TRSTD InterFreqT DDFDD, E - UTRAN
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS f2 Note1 f1 and f2 Note2
160 ms 16 32
>160 ms 8 16
NOTE 1: When inter-frequency RSTD measurements are performed over the reference cell and
neighbour cells, which belong to the FDD inter-frequency carrier frequency f2.
NOTE 2: When inter-frequency RSTD measurements are performed over the reference cell and the
neighbour cells, which belong to the serving TDD carrier frequency f1 and the FDD inter-
frequency carrier frequency f2 respectively.
The UE physical layer shall be capable of reporting RSTD for the reference cell and all the neighbor cells i out of at
least (n-1) neighbor cells within TRSTD InterFeqTD DFDD, E - UTRAN , provided:
(PRS Ê / Iot ) ≥-6 dB for all Frequency Bands for the reference cell,
s ref
(PRS Ê / Iot) ≥-13 dB for all Frequency Bands for neighbour cell i,
s i
(PRS Ê s / Iot ) ref
and (PRS Ê / Iot) conditions apply for all subframes of at least L = M2
s i
PRS positioning
occasions,
PRP 1,2|dBm according to Annex B.2.6 for a corresponding Band,
PRS Ê s / Iot is as defined in Clause 8.1.2.5.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 238 ETSI TS 136 133 V14.3.0 (2017-04)
The time TRSTD InterFeqTD DFDD, E - UTRAN starts from the first subframe of the PRS positioning occasion closest in time
after both the OTDOA-RequestLocationInformation message and the OTDOA assistance data in the OTDOA-
ProvideAssistanceData message as specified in TS 36.355 [24], are delivered to the physical layer of the UE.
If the inter-frequency handover occurs while inter-frequency RSTD measurements are being performed, and the inter-
frequency carrier on which RSTD is measured becomes the new serving carrier frequency after the inter-frequency
handover, the UE shall complete the ongoing OTDOA measurement session. The UE shall also meet the inter-
frequency OTDOA measurement and accuracy requirements. However in this case the RSTD measurement period
( TRSTD InterFreqTDDFDD, E - UTRAN, HO ) shall be according to the following expression:
TRSTD InterFreqT DDFDD, E -UTRAN, HO = TRSTD InterFreqT DDFDD, E - UTRAN + K × TPRS + THO ms
,
where:
K is the number of times the inter-frequency handover occurs during TRSTD InterFreqTDDFDD, E - UTRAN, HO ,
THO is the time during which the inter-frequency RSTD measurement may not be possible due to inter-frequency
handover; it can be up to 45 ms.
The RSTD measurement accuracy for all measured neighbor cells i shall be fulfilled according to the accuracy as
specified in the sub-clause 9.1.10.2.
Furthermore, due to the inter-frequency handover the UE shall meet the RSTD measurement accuracy for a PRS
bandwidth which is not larger than the minimum channel bandwidth of those PCells on whose carriers RSTD
measurement is performed during the RSTD measurement period.
The inter-frequency requirements in this clause (8.1.2.6.2) shall apply for all TDD special subframe configurations
specified in TS 36.211 [16] and for the TDD uplink-downlink configurations as specified in Table 8.1.2.6.2-2.
Table 8.1.2.6.2-2: TDD uplink-downlink subframe configurations applicable for TDD-FDD inter-
frequency requirements
PRS Transmission Bandwidth [RB] Applicable TDD uplink-downlink configurations
6, 15 1, 2, 3, 4 and 5
25, 50, 75, 100 0, 1, 2, 3, 4, 5 and 6
NOTE: Uplink-downlink configurations are specified in Table 4.2-2 in TS 36.211 [16].
8.1.2.6.2.1 RSTD Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
8.1.2.6.3 E-UTRAN TDD-TDD Inter-Frequency OTDOA Measurements
When the physical layer cell identities of neighbour cells together with the OTDOA assistance data are provided, the
UE shall be able to detect and measure inter-frequency RSTD, specified in TS 36.214 [4], for at least n=16 cells,
including the reference cell, within TRSTD InterFreqTDD, E - UTRAN ms as given below:
TRSTD InterFreqTDD, E - UTRAN = TPRS ⋅ ( M - 1) + Δ ms ,
where
TRSTD InterFreqTDD, E - UTRAN is the total time for detecting and measuring at least n cells,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 239 ETSI TS 136 133 V14.3.0 (2017-04)
TPRS is the largest value of the cell-specific positioning subframe configuration period, defined in TS 36.211 [16],
among the measured n cells including the reference cell,
M is the number of PRS positioning occasions as defined in Table 8.1.2.6.1-1, where a PRS positioning occasion is as
defined in clause 8.1.2.5.1,
⎡n⎤
Δ = 160 ⋅ ⎢ ⎥ ms is the measurement time for a single PRS positioning occasion which includes the sampling time
⎢M ⎥
and the processing time, and
the n cells are distributed on up to two carrier frequencies including a serving carrier frequency and one inter-frequency
carrier.
Table 8.1.2.6.3-1: Number of PRS positioning occasions within TRSTD InterFreqTDD, E - UTRAN
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS f2 Note1 f1 and f2 Note2
160 ms 16 32
>160 ms 8 16
Note 1: When inter-frequency RSTD measurements are performed over the reference cell and neighbour
cells, which belong to the TDD inter-frequency carrier frequency f2.
Note 2: When inter-frequency RSTD measurements are performed over the reference cell and the
neighbour cells, which belong to the serving TDD carrier frequency f1 and the TDD inter-frequency carrier
frequency f2 respectively.
The inter-frequency requirements in this clause (8.1.2.6.3) shall apply for all TDD special subframe configurations
specified in TS 36.211 [16] and for the TDD uplink-downlink configurations as specified in Table 8.1.2.6.3-2.
Table 8.1.2.6.3-2: TDD uplink-downlink subframe configurations applicable for inter-frequency
requirements
PRS Transmission Bandwidth [RB] Applicable TDD uplink-downlink configurations
6, 15 3, 4 and 5
25 1, 2, 3, 4, 5 and 6
50, 75, 100 0, 1, 2, 3, 4, 5 and 6
Note 1: Uplink-downlink configurations are specified in Table 4.2-2 in TS 36.211 [16].
Note2: For UEs capable of performing inter-frequency measurements without measurement gaps,
TDD uplink-downlink subframe configurations as specified in Table 8.1.2.5.2-2 shall apply.
The UE physical layer shall be capable of reporting RSTD for the reference cell and all the neighbor cells i out of at
least (n-1) neighbor cells within TRSTD InterFreqTDD, E - UTRAN provided:
(PRS Ê / Iot ) ≥-6 dB for all Frequency Bands for the reference cell,
s ref
(PRS Ê / Iot ) ≥-13 dB for all Frequency Bands for neighbour cell i,
s i
(PRS Ê / Iot ) and (PRS Ê / Iot ) conditions apply for all subframes of at least L = M2
s ref s i
PRS positioning
occasions,
PRP 1,2|dBm according to Annex B.2.6 for a corresponding Band
PRS Ê s / Iot is as defined in Clause 8.1.2.5.1.
The time TRSTD InterFreqTDD, E - UTRAN starts from the first subframe of the PRS positioning occasion closest in time after
both the OTDOA-RequestLocationInformation message and the OTDOA assistance data in the OTDOA-
ProvideAssistanceData message as specified in TS 36.355 [24], are delivered to the physical layer of the UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 240 ETSI TS 136 133 V14.3.0 (2017-04)
If the inter-frequency handover occurs while inter-frequency RSTD measurements are being performed, and the inter-
frequency carrier on which RSTD is measured becomes the new serving carrier frequency after the inter-frequency
handover, the UE shall complete the ongoing OTDOA measurement session. The UE shall also meet the inter-
frequency OTDOA measurement and accuracy requirements. However in this case the RSTD measurement period
( TRSTD InterFreqTDD, E- UTRAN, HO ) shall be according to the following expression:
TRSTD InterFreqTDD, E - UTRAN, HO = TRSTD InterFreqTDD, E - UTRAN + K × TPRS + THO ms ,
where:
K is the number of times the inter-frequency handover occurs during TRSTD InterFreqTDD, E-UTRAN, HO ,
THO is the time during which the inter-frequency RSTD measurement may not be possible due to inter-frequency
handover; it can be up to 45 ms.
The RSTD measurement accuracy for all measured neighbor cells i shall be fulfilled according to the accuracy as
specified in the sub-clause 9.1.10.2.
Furthermore, due to the inter-frequency handover the UE shall meet the RSTD measurement accuracy for a PRS
bandwidth which is not larger than the minimum channel bandwidth of those PCells on whose carriers RSTD
measurement is performed during the RSTD measurement period.
8.1.2.6.3.1 RSTD Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
8.1.2.6.4 E-UTRAN FDD-TDD Inter-Frequency OTDOA Measurements
When the physical layer cell identities of neighbour cells together with the OTDOA assistance data are provided, the
UE shall be able to detect and measure inter-frequency RSTD, specified in TS 36.214 [4], for at least n=16 cells,
including the reference cell, within TRSTD InterFeqFDDTDD, E - UTRAN ms as given below:
TRSTD InterFeqFDDTDD, E - UTRAN = TPRS ⋅ ( M − 1) + Δ ms ,
where
TRSTD InterFeqFDDTDD, E - UTRAN is the total time for detecting and measuring at least n cells,
TPRS is the largest value of the cell-specific positioning subframe configuration period, defined in TS 36.211 [16],
among the measured n cells including the reference cell,
M is the number of PRS positioning occasions as defined in Table 8.1.2.6.4-1, where a PRS positioning occasion is as
defined in clause 8.1.2.5.1,
⎡n⎤
Δ = 160 ⋅ ⎢ ⎥
ms is the measurement time for a single PRS positioning occasion which includes the sampling time
⎢M ⎥
and the processing time, and
the n cells are distributed on up to two carrier frequencies including a serving carrier frequency and one inter-frequency
carrier.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 241 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.6.4-1: Number of PRS positioning occasions within TRSTD InterFeqFDDTDD, E - UTRAN
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS f2 Note1 f1 and f2 Note2
160 ms 16 32
>160 ms 8 16
Note 1: When inter-frequency RSTD measurements are performed over the reference cell and
neighbour cells, which belong to the TDD inter-frequency carrier frequency f2.
Note 2: When inter-frequency RSTD measurements are performed over the reference cell and the
neighbour cells, which belong to the serving FDD carrier frequency f1 and the TDD inter-
frequency carrier frequency f2 respectively.
The UE physical layer shall be capable of reporting RSTD for the reference cell and all the neighbor cells i out of at
least (n-1) neighbor cells within TRSTD InterFeqFDDTDD, E - UTRAN , provided:
(PRS Ê / Iot ) ≥-6 dB for all Frequency Bands for the reference cell,
s ref
(PRS Ê / Iot) ≥-13 dB for all Frequency Bands for neighbour cell i,
s i
(PRS Ê s / Iot ) ref
and (PRS Ê / Iot) conditions apply for all subframes of at least L = M2
s i
PRS positioning
occasions,
PRP 1,2|dBm according to Annex B.2.6 for a corresponding Band
PRS Ê s / Iot is as defined in Clause 8.1.2.5.1.
The time TRSTD InterFeqFDDTDD, E - UTRAN starts from the first subframe of the PRS positioning occasion closest in time
after both the OTDOA-RequestLocationInformation message and the OTDOA assistance data in the OTDOA-
ProvideAssistanceData message as specified in TS 36.355 [24], are delivered to the physical layer of the UE.
If the inter-frequency handover occurs while inter-frequency RSTD measurements are being performed, and the inter-
frequency carrier on which RSTD is measured becomes the new serving carrier frequency after the inter-frequency
handover, the UE shall complete the ongoing OTDOA measurement session. The UE shall also meet the inter-
frequency OTDOA measurement and accuracy requirements. However in this case the RSTD measurement period
( TRSTD InterFreqFDDTDD, E - UTRAN, HO ) shall be according to the following expression:
TRSTD InterFreqFDDTDD, E -UTRAN, HO = TRSTD InterFreqFDDTDD, E -UTRAN + K × TPRS + THO ms ,
where:
K is the number of times the inter-frequency handover occurs during TRSTD InterFreqFDDTDD, E -UTRAN, HO ,
THO is the time during which the inter-frequency RSTD measurement may not be possible due to inter-frequency
handover; it can be up to 45 ms.
The RSTD measurement accuracy for all measured neighbor cells i shall be fulfilled according to the accuracy as
specified in the sub-clause 9.1.10.2.
Furthermore, due to the inter-frequency handover the UE shall meet the RSTD measurement accuracy for a PRS
bandwidth which is not larger than the minimum channel bandwidth of those PCells on whose carriers RSTD
measurement is performed during the RSTD measurement period.
The inter-frequency requirements in this clause (8.1.2.6.4) shall apply for all TDD special subframe configurations
specified in TS 36.211 [16] and for the TDD uplink-downlink configurations as specified in Table 8.1.2.6.4-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 242 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.6.4-2: TDD uplink-downlink subframe configurations applicable for inter-frequency
requirements
PRS Transmission Bandwidth [RB] Applicable TDD uplink-downlink configurations
6, 15 3, 4 and 5
25 1, 2, 3, 4, 5 and 6
50, 75, 100 0, 1, 2, 3, 4, 5 and 6
Note 1: Uplink-downlink configurations are specified in Table 4.2-2 in TS 36.211 [16].
Note2: For UEs capable of performing inter-frequency measurements without measurement gaps,
TDD uplink-downlink subframe configurations as specified in Table 8.1.2.5.2-2 shall apply.
8.1.2.6.4.1 RSTD Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
8.1.2.7 E-UTRAN E-CID Measurements
8.1.2.7.1 E-UTRAN FDD UE Rx-Tx Time Difference Measurements
When no DRX is used the physical layer measurement period of the UE Rx-Tx time difference measurement shall be
200 ms.
When DRX is used in RRC_CONNECTED state the physical layer measurement period (Tmeasure_FDD_UE_Rx_Tx1) of the
UE Rx-Tx time difference measurement shall be as specified in table 8.1.2.7.1-1. When eDRX_CONN is used in
RRC_CONNECTED state, the physical layer measurement period (Tmeasure_FDD_UE_Rx_Tx1) of the UE Rx-Tx time
difference measurement shall be as specified in table 8.1.2.7.1-2.
Table 8.1.2.7.1-1: FDD UE Rx-Tx time difference measurement requirement when DRX is used
DRX cycle length (s) Tmeasure_FDD_UE_Rx_Tx1 (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX-cycle≤2.56 Note2 (5)
Note1: Number of DRX cycle depends upon the DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.1.2.7.1-2: FDD UE Rx-Tx time difference measurement requirement when eDRX_CONN is
used
eDRX_CONN cycle length (s) Tmeasure_FDD_UE_Rx_Tx1 (s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use
If the UE is performing UE Rx-Tx time difference measurement while the PCell is changed due to the handover then
the UE shall restart the Rx-Tx measurement on the new cell. In this case the UE shall also meet the UE Rx-Tx time
difference measurement and accuracy requirements. However the physical layer measurement period of the UE Rx-Tx
measurement shall not exceed Tmeasure_FDD_UE_Rx_Tx3 as defined in the following expression:
Tmeasure_FDD_UE_Rx_Tx3 = (K+1)*(Tmeasure_FDD_UE_Rx_Tx1) + K*TPCcell_change_handover
Where:
K is the number of times the PCell is changed over the measurement period (Tmeasure_FDD_UE_Rx_Tx3),
TPCell_change_handover is the time necessary to change the PCell due to handover; it can be up to 45 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 243 ETSI TS 136 133 V14.3.0 (2017-04)
If the UE supporting E-UTRA carrier aggregation when configured with the secondary component carrier(s) is
performing UE Rx-Tx time difference measurement while the PCell is changed regardless whether the primary
component carrier is changed or not then the UE shall restart the Rx-Tx measurement on the new PCell. In this case the
UE shall also meet the UE Rx-Tx time difference measurement and accuracy requirements corresponding to the new
PCell. However the physical layer measurement period of the UE Rx-Tx measurement shall not exceed
Tmeasure_FDD_UE_Rx_Tx2 as defined in the following expression:
Tmeasure_FDD_UE_Rx_Tx2 = (N+1)*(Tmeasure_FDD_UE_Rx_Tx1) + N*TPCell_change_CA
Where:
N is the number of times the PCell is changed over the measurement period (Tmeasure_FDD_UE_Rx_Tx2),
TPCell_change_CA is the time necessary to change the PCell; it can be up to 25 ms.
If IDC autonomous denial is configured then the UE shall also meet the requirements, provided not more than 30 IDC
autonomous denial suframes are configured over an IDC autonomous denial validity period of at least 200 ms.
The UE capable of SRS carrier based switching, when configured to perform SRS carrier based switching for SRS
transmission and/or RACH transmission over one or more SCells without PUSCH, shall perform UE Rx-Tx time
difference measurement and meet the requirements defined in Section 8.1.2.7.1 provided the following condition is met:
- at least one downlink subframe and one uplink subframe per radio frame are available for doing UE Rx-Tx time
difference measurement at the UE in the PCell.
The measurement accuracy for the UE Rx-Tx time difference measurement when DRX or eDRX_CONN is used as
well as when no DRX is used shall be as specified in the sub-clause 9.1.9.
8.1.2.7.1.1 UE Rx-Tx Measurement Reporting Delay
This requirement assumes that the measurement report is not delayed by other RRC or LPP signalling on the DCCH.
This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the
TTI of the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay
caused by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier
based switching, an additional delay can be expected.
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in sub-
clause 9.1.9.
8.1.2.7.2 E-UTRAN TDD UE Rx-Tx Time Difference Measurements
When no DRX is used the physical layer measurement period of the UE Rx-Tx time difference measurement shall be
200 ms.
When DRX is used in RRC_CONNECTED state the physical layer measurement period (Tmeasure_TDD_UE_Rx_Tx1) of the
UE Rx-Tx time difference measurement shall be as specified in table 8.1.2.7.2-1. When eDRX_CONN is used in
RRC_CONNECTED state the physical layer measurement period (Tmeasure_TDD_UE_Rx_Tx1) of the UE Rx-Tx time
difference measurement shall be as specified in table 8.1.2.7.2-2.
Table 8.1.2.7.2-1: TDD UE Rx-Tx time difference measurement requirement when DRX is used
DRX cycle length (s) Tmeasure_TDD_UE_Rx_Tx1 (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX-cycle≤2.56 Note2 (5)
Note1: Number of DRX cycle depends upon the DRX cycle in use
Note2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 244 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.7.2-2: TDD UE Rx-Tx time difference measurement requirement when eDRX_CONN is
used
eDRX_CONN cycle length (s) Tmeasure_TDD_UE_Rx_Tx1 (s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use
If the UE is performing UE Rx-Tx time difference measurement while the PCell is changed due to the handover then
the UE shall restart the Rx-Tx measurement on the new cell. In this case the UE shall also meet the UE Rx-Tx time
difference measurement and accuracy requirements. However the physical layer measurement period of the UE Rx-Tx
measurement shall not exceed Tmeasure_TDD_UE_Rx_Tx3 as defined in the following expression:
Tmeasure_TDD_UE_Rx_Tx3 = (K+1)*(Tmeasure_TDD_UE_Rx_Tx1) + K*TPCell_change_handover
Where:
K is the number of times the PCell is changed over the measurement period (Tmeasure_TDD_UE_Rx_Tx3),
TPCell_change_handover is the time necessary to change the PCell due to handover; it can be up to 45 ms.
If the UE supporting E-UTRA carrier aggregation when configured with the secondary component carrier(s) is
performing UE Rx-Tx time difference measurement while the PCell is changed regardless whether the primary
component carrier is changed or not then the UE shall restart the Rx-Tx measurement on the new PCell. In this case the
UE shall also meet the UE Rx-Tx time difference measurement and accuracy requirements corresponding to the new
PCell. However the physical layer measurement period of the UE Rx-Tx measurement shall not exceed
Tmeasure_TDD_UE_Rx_Tx2 as defined in the following expression:
Tmeasure_TDD_UE_Rx_Tx2 = (N+1)*(Tmeasure_TDD_UE_Rx_Tx1) + N*TPCell_change_CA
Where:
N is the number of times the PCell is changed over the measurement period (Tmeasure_TDD_UE_Rx_Tx2),
TPCell_change_CA is the time necessary to change the PCell; it can be up to 25 ms.
If IDC autonomous denial is configured then the UE shall also meet the requirements, provided not more than 30 IDC
autonomous denial suframes are configured over an IDC autonomous denial validity period of at least 200 ms.
The measurement accuracy for the UE Rx-Tx time difference measurement when DRX or eDRX_CONN is used as
well as when no DRX is used shall be as specified in the sub-clause 9.1.9.
For UE, which does not support simultaneous reception and transmission for inter-band TDD CA specified in TS
36.331 [2], and is compliant to the requirements for inter-band CA with uplink in one E-UTRA band and without
simultaneous Rx/Tx specified in TS 36.101 [5], the UE Rx-Tx time difference measurement requirements in Section
8.1.2.7.2 shall apply also with different TDD UL/DL subframe configurations and/or different special subframe
configurations used in CCs of different bands, under the following additional conditions:
- UE is not simultaneously scheduled in UL and DL on the different CCs, and
- At least one downlink and one uplink subframes per radio frame are available for the UE Rx-Tx time difference
measurement in the measured cell.
The UE capable of SRS carrier based switching, when configured to perform SRS carrier based switching for SRS
transmission and/or RACH transmission over one or more SCells without PUSCH, shall perform UE Rx-Tx time
difference measurement and meet the requirements defined in Section 8.1.2.7.2 provided the following condition is met:
- at least one downlink subframe and one uplink subframe per radio frame are available for doing UE Rx-Tx time
difference measurement at the UE in the PCell.
8.1.2.7.2.1 UE Rx-Tx Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other RRC or LPP signalling on the
DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report
to the TTI of the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 245 ETSI TS 136 133 V14.3.0 (2017-04)
delay caused by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS
carrier based switching, an additional delay can be expected.
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in sub-
clause 9.1.9.
8.1.2.7.3 E-UTRAN FDD Intra-frequency E-CID RSRP and RSRQ Measurements
8.1.2.7.3.1 Introduction
The requirements in section 8.1.2.7.3 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN FDD intra-frequency RSRP and RSRQ
measurements [24].
The UE capable of SRS carrier based switching, when configured to perform SRS carrier based switching for SRS
transmission and/or RACH transmission over one or more SCells without PUSCH, shall perform UE Rx-Tx time
difference measurement and meet the requirements defined in Section 8.1.2.7.3 provided the following condition is met:
- at least one downlink subframe and one uplink subframe per radio frame are available for doing UE Rx-Tx time
difference measurement at the UE in the PCell.
8.1.2.7.3.2 Measurement Requirements
The requirements in section 8.1.2.2.1 and section 8.1.2.8.1 also apply for this section except the measurement reporting
requirements. The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.1.2.7.3.3.
8.1.2.7.3.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.2 and 9.1.5 respectively.
8.1.2.7.4 E-UTRAN TDD Intra-frequency E-CID RSRP and RSRQ Measurements
8.1.2.7.4.1 Introduction
The requirements in section 8.1.2.7.4 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN TDD intra-frequency RSRP and RSRQ
measurements [24].
The UE capable of SRS carrier based switching, when configured to perform SRS carrier based switching for SRS
transmission and/or RACH transmission over one or more SCells without PUSCH, shall perform UE Rx-Tx time
difference measurement and meet the requirements defined in Section 8.1.2.7.4 provided the following condition is met:
- at least one downlink subframe and one uplink subframe per radio frame are available for doing UE Rx-Tx time
difference measurement at the UE in the PCell.
8.1.2.7.4.2 Measurement Requirements
The requirements in section 8.1.2.2.2 and section 8.1.2.8.2 also apply for this section except the measurement reporting
requirements. The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.1.2.7.4.3.
8.1.2.7.4.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 246 ETSI TS 136 133 V14.3.0 (2017-04)
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.2 and 9.1.5 respectively.
8.1.2.8 E-UTRAN intra-frequency measurements under time domain measurement
resource restriction
The requirements in sections 8.1.2.8.1 and 8.1.2.8.2 shall apply for cells for which time domain measurement resource
restriction patterns for performing E-UTRAN FDD intra-frequency measurements and E-UTRAN TDD intra-frequency
measurements, respectively, are configured by higher layers (TS 36.331 [2]), provided that also the following additional
conditions are fulfilled:
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the intra-frequency measurements, and
Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern.
For cells which are not configured for measurements in the subframes indicated by the time-domain measurement
resource restriction pattern, the corresponding requirements specified in Clause 8.1.2.2 apply.
8.1.2.8.1 E-UTRAN FDD intra-frequency measurements
8.1.2.8.1.1 E-UTRAN intra-frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FDD intra-frequency cell within
TMeasurement_Period_eICIC, Intra
Tidentify_ intra_eICIC = Tbasic_identify_E - UTRA _ FDD_eICIC, intra ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_FDD_eICIC, intra is 1000 ms.
TIntra is the minimum time available for intra-frequency measurements, during the measurement period with an
arbitrarily chosen timing. The time is assumed to be available for performing intra-frequency measurements
whenever the receiver is guaranteed to be active on the intra-frequency carrier.
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.2.3 and 9.1.2.4 and RSRQ related side conditions given in
Clause 9.1.5.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.8 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_eICIC, Intra. If higher layer filtering is used, an additional cell identification delay
can be expected.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is 200 ms. When no
measurement gaps are activated, the UE shall be capable of performing RSRP and RSRQ measurements for 8 identified
intra-frequency cells, including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern, and the UE physical layer shall be capable of reporting measurements to
higher layers with the measurement period of 200 ms. When measurement gaps are activated the UE shall be capable of
performing measurements for at least Ymeasurement_intra_eICIC cells , where Ymeasurement_intra_eICIC is defined in the following
equation. If the UE has identified more than Ymeasurement_intra_eICIC cells, the UE shall perform measurements of at least 8
identified intra-frequency cells but the reporting rate of RSRP and RSRQ measurements of cells from UE physical layer
to higher layers may be decreased.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 247 ETSI TS 136 133 V14.3.0 (2017-04)
⎧⎪ TIntra ⎫⎪
Ymeasurement_intra_eICIC = Floor ⎨ X basic _ measurement_FDD_eICIC ⋅ ⎬ cells
⎪⎩ TMeasurement_Period_eICIC, Intra ⎪⎭
where
Xbasic_measurement_FDD_eICIC = 8 (cells)
TMeasurement_Period_eICIC, Intra = 200 ms is the measurement period for intra-frequency RSRP and RSRQ
measurements.
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements shall be as specified in the sub-clauses 9.1.2.3,
9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.1.1.1 Measurement Reporting Requirements
8.1.2.8.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.1.1.1.3.
8.1.2.8.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_eICIC
defined in Clause 8.1.2.8.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_eICIC defined in clause 8.1.2.8.1.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period_eICIC, Intra provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.1.2.8.1.2 E-UTRAN intra-frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra_eICIC
as shown in table 8.1.2.8.1.2-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 248 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.8.1.2-1: Requirement to identify a newly detectable FDD intra-frequency cell
DRX cycle Tidentify_intra_eICIC (s)
length (s) (DRX cycles)
≤0.04 1 (Note1)
0.04<DRX- Note2 (52)
cycle≤0.08
0.128 4.22 (33)
0.128<DRX- Note2 (28)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use
Note2: Time depends upon the
DRX cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.2.3 and 9.1.2.4 and RSRQ related side conditions given in
Clause 9.1.5.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.8 for a corresponding Band.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is Tmeasure_intra_eICIC as shown
in table 8.1.2.8.1.2-2. The UE shall be capable of performing RSRP and RSRQ measurements for 8 identified intra-
frequency cells, including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern, and the UE physical layer shall be capable of reporting measurements to
higher layers with the measurement period of Tmeasure_intra_eICIC.
Table 8.1.2.8.1.2-2: Requirement to measure FDD intra-frequency cells
DRX cycle Tmeasure_intra_eICIC (s)
length (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX- Note2 (7)
cycle≤0.16
0.16<DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use
Note2: Time depends upon the
DRX cycle in use
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements shall be as specified in the sub-clauses 9.1.2.3,
9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.1.2.1 Measurement Reporting Requirements
8.1.2.8.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.1.2.1.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 249 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.8.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_eICIC
defined in Clause 8.1.2.8.1.2. When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_eICIC defined in clause 8.1.2.8.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_eICIC provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.1.2.8.2 E-UTRAN TDD intra-frequency measurements
8.1.2.8.2.1 E-UTRAN intra-frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable TDD intra-frequency cell within
TMeasurement _ Period_eICIC, Intra
Tidentify_ intra_eICIC = Tbasic_identify_E - UTRA _ TDD_eICIC, intra ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_TDD_eICIC, intra is 1000 ms.
TIntra is the minimum time available for intra-frequency measurements, during the measurement period with an
arbitrarily chosen timing. The time is assumed to be available for performing intra-frequency measurements
whenever the receiver is guaranteed to be active on the intra-frequency carrier.
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.2.3 and 9.1.2.4 and RSRQ related side conditions given in
Clause 9.1.5.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.8 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_eICIC, Intra. If higher layer filtering is used, an additional cell identification delay
can be expected.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is 200 ms. When no
measurement gaps are activated, the UE shall be capable of performing RSRP and RSRQ measurements for 8 identified
intra-frequency cells , including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern, and the UE physical layer shall be capable of reporting measurements to
higher layers with the measurement period of 200 ms. When measurement gaps are activated the UE shall be capable of
performing measurements for at least Ymeasurement_intra_eICIC cells , where Ymeasurement_intra_eICIC is defined in the following
equation. If the UE has identified more than Ymeasurement_intra_eICIC cells, the UE shall perform measurements of at least 8
identified intra-frequency cells but the reporting rate of RSRP and RSRQ measurements of cells from UE physical layer
to higher layers may be decreased.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 250 ETSI TS 136 133 V14.3.0 (2017-04)
⎧⎪ TIntra ⎫⎪
Ymeasurement_intra_eICIC = Floor ⎨ X basic _ measurement _ TDD_eICIC ⋅ ⎬ cells
⎪⎩ TMeasurement_Period_eICIC, Intra ⎪⎭
where
Xbasic_measurement_TDD_eICIC = 8 (cells)
TMeasurement_Period_eICIC, Intra = 200 ms is the measurement period for intra-frequency RSRP and RSRQ
measurements.
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements shall be as specified in the sub-clauses 9.1.2.3,
9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.2.1.1 Measurement Reporting Requirements
8.1.2.8.2.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.2.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.2.1.1.3.
8.1.2.8.2.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_eICIC
defined in Clause 8.1.2.8.2.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_eICIC defined in clause 8.1.2.8.2.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period_eICIC, Intra provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.1.2.8.2.2 E-UTRAN intra-frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within Tidentify_intra_eICIC
as shown in table 8.1.2.8.2.2-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 251 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.8.2.2-1: Requirement to identify a newly detectable TDD intra-frequency cell
DRX cycle Tidentify_intra_eICIC (s)
length (s) (DRX cycles)
≤0.04 1 (Note1)
0.04<DRX- Note2 (52)
cycle≤0.08
0.128 4.22 (33)
0.128<DRX- Note2 (28)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use
Note2: Time depends upon the
DRX cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.2.3 and 9.1.2.4 and RSRQ related side conditions given in
Clause 9.1.5.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.8 for a corresponding Band.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_eICIC as shown
in table 8.1.2.8.2.2-2. The UE shall be capable of performing RSRP and RSRQ measurements for 8 identified intra-
frequency cells, including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern, and the UE physical layer shall be capable of reporting measurements to
higher layers with the measurement period of Tmeasure_intra_eICIC.
Table 8.1.2.8.2.2-2: Requirement to measure TDD intra-frequency cells
DRX cycle Tmeasure_intra_eICIC (s)
length (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX- Note2 (7)
cycle≤0.16
0.16<DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX
cycle in use.
Note2: Time depends upon the
DRX cycle in use.
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements shall be as specified in the sub-clauses 9.1.2.3,
9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.2.2.1 Measurement Reporting Requirements
8.1.2.8.2.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
8.1.2.8.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.2.2.1.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 252 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.8.2.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.3, 9.1.2.4, and 9.1.5.2, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_eICIC
defined in Clause 8.1.2.8.2.2. When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_eICIC defined in clause 8.1.2.8.2.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_eICIC provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.1.2.8.3 E-UTRAN FDD intra-frequency measurements with CRS assistance information
The requirements in clause 8.1.2.8.3 shall apply for the UEs supporting the PSS/SSS and common channel interference
handling, and CRS interference handling features. Moreover, the core requirements shall be satisfied provided that the
following additional conditions are fulfilled:
- The UE is provided with the CRS assistance information via higher layers (TS 36.331 [2]),
- The CRS assistance information is valid during the entire measurement period.
The requirements in this section shall also be met when the number of transmit antenna ports [16] of one or more cells
whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
8.1.2.8.3.1 E-UTRAN intra-frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FDD intra-frequency cell within:
TMeasurement_Period_FeICIC, Intra
Tidentify_ intra_FeICIC = Tbasic_identify_E-UTRA _ FDD_FeICIC, intra ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_FDD_FeICIC, intra is 1000 ms.
TIntra is the minimum time available for intra-frequency measurements, during the measurement period with an
arbitrarily chosen timing. The time is assumed to be available for performing intra-frequency measurements
whenever the receiver is guaranteed to be active on the intra-frequency carrier.
A cell shall be considered detectable when:
- RSRP related side conditions given in Sections 9.1.2.5 and 9.1.2.6 and RSRQ related side conditions given in
Section 9.1.5.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B, clause B.2.9 for a corresponding Band (Notes 1, 2).
Note 1: Part of the Iot includes the interference from at least:
- the PCell , or
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 253 ETSI TS 136 133 V14.3.0 (2017-04)
- PCell and one intra-frequency neighbouring cell indicated in the CRS assistance information, or
- One or two intra-frequency neighbouring cells indicated in the CRS assistance information.
CRS assistance information has been provided for the intra-frequency neighbouring cells that generate
interference. UE may use the CRS assistance information to mitigate the interference.
Note 2: An intra-frequency cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_FeICIC, Intra. If higher layer filtering is used, an additional cell identification
delay can be expected.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is 200 ms. When no
measurement gaps are activated, the UE shall be capable of performing RSRP and RSRQ measurements for 8 identified
intra-frequency cells, including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern and the cells indicated in the CRS assistance information, and the UE physical
layer shall be capable of reporting measurements to higher layers with the measurement period of 200 ms. When
measurement gaps are activated the UE shall be capable of performing measurements for at least
Ymeasurement_intra_FeICIC cells , where Ymeasurement_intra_FeICIC is defined in the following equation. If the UE has
identified more than Ymeasurement_intra_FeICIC cells, the UE shall perform measurements of at least 8 identified intra-
frequency cells but the reporting rate of RSRP and RSRQ measurements of cells from UE physical layer to higher
layers may be decreased.
⎧⎪ TIntra ⎫⎪
Ymeasurement_intra_FeICIC = Floor ⎨ X basic _ measurement_FDD_FeICIC ⋅ ⎬ cells
⎩⎪ TMeasurement_Period_FeICIC, Intra ⎭⎪
where
Xbasic_measurement_FDD_FeICIC = 8 (cells).
TMeasurement_Period_FeICIC, Intra = 200 ms is the measurement period for intra-frequency RSRP and RSRQ
measurements.
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements with CRS assistance information shall be as
specified in the sub-clauses 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
8.1.2.8.3.1.1 Measurement Reporting Requirements
8.1.2.8.3.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
8.1.2.8.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.3.1.1.3.
8.1.2.8.3.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 254 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_FeICIC
defined in Clause 8.1.2.8.3.1. When L3 filtering is used or IDC autonomous denial is configured, an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_FeICIC defined in clause 8.1.2.8.3.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period_FeICIC, Intra provided the timing to that cell
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, an additional delay can be expected.
8.1.2.8.3.2 E-UTRAN intra-frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_FeICIC as shown in table 8.1.2.8.3.2-1.
Table 8.1.2.8.3.2-1: Requirement to identify a newly detectable FDD intra-frequency cell
DRX cycle length (s) Tidentify_intra_FeICIC (s)
(DRX cycles)
≤0.04 1 (Note 1)
0.04<DRX-cycle≤0.08 Note 2 (52)
0.128 4.22 (33)
0.128<DRX-cycle≤2.56 Note 2 (28]
NOTE 1: Number of DRX cycle depends upon the DRX cycle in use.
NOTE 2: Time depends upon the DRX cycle in use.
A cell shall be considered detectable when:
- RSRP related side conditions given in Sections 9.1.2.5 and 9.1.2.6 and RSRQ related side conditions given in
Section 9.1.5.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B, clause B.2.9 for a corresponding Band (Notes 1, 2).
Note 1: Part of the Iot includes the interference from at least:
- the PCell , or
- PCell and one intra-frequency neighbouring cell indicated in the CRS assistance information, or
- One or two intra-frequency neighbouring cells indicated in the CRS assistance information.
CRS assistance information has been provided for the intra-frequency neighbouring cells that generate
interference. UE may use the CRS assistance information to mitigate the interference.
Note 2: An intra-frequency cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is Tmeasure_intra_FeICIC as
shown in table 8.1.2.8.3.2-2. The UE shall be capable of performing RSRP and RSRQ measurements for 8 identified
intra-frequency cells, including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern and the cell indicated in CRS assistance information, and the UE physical
layer shall be capable of reporting measurements to higher layers with the measurement period of Tmeasure_intra_FeICIC.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 255 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.8.3.2-2: Requirement to measure FDD intra-frequency cells
DRX cycle length (s) Tidentify_intra_FeICIC (s)
(DRX cycles)
≤0.04 0.2 (Note 1)
0.04<DRX-cycle≤0.16 Note 2 (7)
0.16<DRX-cycle≤2.56 Note 2 (5)
NOTE 1: Number of DRX cycle depends upon the DRX cycle in use.
NOTE 2: Time depends upon the DRX cycle in use.
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements shall be as specified in the sub-clauses 9.1.2.5,
9.1.2.6, and 9.1.5.3, respectively.
8.1.2.8.3.2.1 Measurement Reporting Requirements
8.1.2.8.3.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
8.1.2.8.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.3.2.1.3.
8.1.2.8.3.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_FeICIC
defined in clause 8.1.2.8.3.2. When L3 filtering is used or IDC autonomous denial is configured, an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_FeICIC defined in clause 8.1.2.8.3.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_FeICIC provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.1.2.8.4 E-UTRAN TDD intra-frequency measurements with CRS assistance infromation
The requirements in clause 8.1.2.8.3 shall apply for the UEs upporting the PSS/SSS and common channel interference
handling, and CRS interference handling features. Moreover, the core requirements shall be satisfied provided that the
following additional conditions are fulfilled:
- The UE is provided with the CRS assistance information via higher layers (TS 36.331 [2]),
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 256 ETSI TS 136 133 V14.3.0 (2017-04)
- The CRS assistance information is valid during the entire measurement period.
The requirements in this section shall also be met when the number of transmit antenna ports [16] of one or more cells
whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
8.1.2.8.4.1 E-UTRAN intra-frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable TDD intra-frequency cell within
TMeasurement _ Period_FeICIC, Intra
Tidentify_ intra_FeICIC = Tbasic_identify_E-UTRA _ TDD_FeICIC, intra ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_TDD_eICIC, intra is 1000 ms.
TIntra is the minimum time available for intra-frequency measurements, during the measurement period with an
arbitrarily chosen timing. The time is assumed to be available for performing intra-frequency measurements
whenever the receiver is guaranteed to be active on the intra-frequency carrier.
A cell shall be considered detectable when:
- RSRP related side conditions given in Sections 9.1.2.5 and 9.1.2.6 and RSRQ related side conditions given in
Section 9.1.5.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.9 for a corresponding Band (Notes 1, 2).
Note 1: Part of the Iot includes the interference from at least:
- the PCell , or
- PCell and one intra-frequency neighbouring cell indicated in the CRS assistance information, or
- One or two intra-frequency neighbouring cells indicated in the CRS assistance information
CRS assistance information has been provided for the intra-frequency neighbouring cells that generate
interference. UE may use the CRS assistance information to mitigate the interference.
Note 2: An intra-frequency cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_FeICIC, Intra. If higher layer filtering is used, an additional cell identification
delay can be expected.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is 200 ms. When no
measurement gaps are activated, the UE shall be capable of performing RSRP and RSRQ measurements for 8 identified
intra-frequency cells , including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern and the cells indicated in the CRS assistance information, and the UE physical
layer shall be capable of reporting measurements to higher layers with the measurement period of 200 ms. When
measurement gaps are activated the UE shall be capable of performing measurements for at least
Ymeasurement_intra_FeICIC cells , where Ymeasurement_intra_FeICIC is defined in the following equation. If the UE has
identified more than Ymeasurement_intra_FeICIC cells, the UE shall perform measurements of at least 8 identified intra-
frequency cells but the reporting rate of RSRP and RSRQ measurements of cells from UE physical layer to higher
layers may be decreased.
⎧⎪ TIntra ⎫⎪
Ymeasurement_intra_FeICIC = Floor ⎨ X basic _ measurement _ TDD_FeICIC ⋅ ⎬ cells
⎩⎪ TMeasurement_Period_FeICIC, Intra ⎭⎪
where
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 257 ETSI TS 136 133 V14.3.0 (2017-04)
Xbasic_measurement_TDD_FeICIC = 8 (cells)
TMeasurement_Period_FeICIC, Intra = 200ms is the measurement period for intra-frequency RSRP and RSRQ
measurements.
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements with CRS assistance information shall be as
specified in the sub-clauses 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
8.1.2.8.4.1.1 Measurement Reporting Requirements
8.1.2.8.4.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
8.1.2.8.4.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.4.1.1.3.
8.1.2.8.4.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_FeICIC
defined in clause 8.1.2.8.4.1. When L3 filtering is used or IDC autonomous denial is configured, an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_FeICIC defined in clause 8.1.2.8.4.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period_FeICIC, Intra provided the timing to that cell
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, an additional delay can be expected.
8.1.2.8.4.2 E-UTRAN intra-frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
Tidentify_intra_FeICIC as shown in table 8.1.2.8.4.2-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 258 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.1.2.8.4.2-1: Requirement to identify a newly detectable TDD intra-frequency cell
DRX cycle length (s) Tidentify_intra_FeICIC (s)
(DRX cycles)
≤0.04 1 (Note 1)
0.04<DRX-cycle≤0.08 Note 2 (52)
0.128 4.22 (33)
0.128<DRX-cycle≤2.56 Note 2 (28)
NOTE 1: Number of DRX cycle depends upon the DRX cycle in use.
NOTE 2: Time depends upon the DRX cycle in use.
A cell shall be considered detectable when:
- RSRP related side conditions given in Sections 9.1.2.5 and 9.1.2.6 and RSRQ related side conditions given in
Section 9.1.5.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.9 for a corresponding Band (Notes 1, 2).
Note 1: Part of the Iot includes the interference from at least:
- the PCell , or
- PCell and one intra-frequency neighbouring cell indicated in the CRS assistance information, or
- One or two intra-frequency neighbouring cells indicated in the CRS assistance information.
CRS assistance information has been provided for the intra-frequency neighbouring cells that generate
interference. UE may use the CRS assistance information to mitigate the interference.
Note 2: An intra-frequency cell is known if it has been meeting the relevant cell identification requirement during
the last 5 seconds.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_FeICIC as
shown in table 8.1.2.8.4.2-2. The UE shall be capable of performing RSRP and RSRQ measurements for 8 identified
intra-frequency cells, including also the cells which are not measured in the subframes indicated by the time-domain
measurement resource restriction pattern and the cell indicated in CRS assistance information, and the UE physical
layer shall be capable of reporting measurements to higher layers with the measurement period of Tmeasure_intra_FeICIC.
Table 8.1.2.8.4.2-2: Requirement to measure TDD intra-frequency cells
DRX cycle length (s) Tidentify_intra_FeICIC (s)
(DRX cycles)
≤0.04 0.2 (Note 1)
0.04<DRX-cycle≤0.16 Note 2 (7)
0.16<DRX-cycle≤2.56 Note 2 (5)
NOTE 1: Number of DRX cycle depends upon the DRX cycle in use.
NOTE 2: Time depends upon the DRX cycle in use.
The RSRP and RSRQ measurement accuracy for the measured cells configured with a time-domain measurement
resource restriction pattern for RRM intra-frequency measurements shall be as specified in the sub-clauses 9.1.2.5,
9.1.2.6, and 9.1.5.3, respectively.
8.1.2.8.4.2.1 Measurement Reporting Requirements
8.1.2.8.4.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 259 ETSI TS 136 133 V14.3.0 (2017-04)
8.1.2.8.4.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.1.2.8.2.2.1.3.
8.1.2.8.4.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.2.5, 9.1.2.6, and 9.1.5.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T
identify_intra_FeICIC defined in clause 8.1.2.8.4.2. When L3 filtering is used or IDC autonomous denial is configured,
an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_FeICIC defined in clause 8.1.2.8.4.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_FeICIC provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.1.2.9 E-UTRAN E-CID Measurements when Time Domain Measurement Resource
Restriction Pattern is Configured
8.1.2.9.1 E-UTRAN FDD UE Rx-Tx Time Difference Measurements
The requirements in this clause apply for UE configured with a time-domain measurement resource restriction pattern
for PCell measurements, provided that also the following additional conditions are fulfilled:
- The time domain measurement resource restriction pattern configured for the PCell (TS 36.331 [2]) indicates at
least one subframe per radio frame for performing the PCell measurements, and
- Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern.
When the UE is provided with a time-domain measurement resource restriction pattern for PCell measurements, the UE
Rx-Tx time difference measurement shall meet the measurement requirements specified in Clause 8.1.2.7.1 and
accuracy requirements specified in Clause 9.1.9.3, where the condition Ês/Iot ≥ -3dB in Table 9.1.9.3-1 corresponds to
the CRS Ês/Iot in subframes indicated by the time-domain measurement resource restriction pattern for PCell
measurements (TS 36.331 [2]).
NOTE: It is up to the UE implementation whether the UE Rx-Tx time difference measurement is performed in
any subframe or in subframes indicated by the time-domain measurement resource restriction pattern.
8.1.2.9.2 E-UTRAN TDD UE Rx-Tx Time Difference Measurements
The requirements in this clause apply for UE configured with a time-domain measurement resource restriction pattern
for PCell measurements, provided that also the following additional conditions are fulfilled:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 260 ETSI TS 136 133 V14.3.0 (2017-04)
- The time domain measurement resource restriction pattern configured for the PCell (TS 36.331 [2]) indicates at
least one subframe per radio frame for performing the PCell measurements, and
- Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern.
When the UE is provided with a time-domain measurement resource restriction pattern for PCell measurements, the UE
Rx-Tx time difference measurement shall meet the measurement requirements specified in Clause 8.1.2.7.2 and
accuracy requirements specified in Clause 9.1.9.3, where the condition Ês/Iot ≥ -3dB in Table 9.1.9.3-1 corresponds to
the CRS Ês/Iot in subframes indicated by the time-domain measurement resource restriction pattern for PCell
measurements (TS 36.331 [2]).
NOTE: It is up to the UE implementation whether the UE Rx-Tx time difference measurement is performed in
any subframe or in subframes indicated by the time-domain measurement resource restriction pattern.
8.1.2.9.3 E-UTRAN FDD UE Rx-Tx Time Difference Measurements with CRS Assistance
Information
For UE configured with a time-domain measurement resource restriction pattern for PCell measurements, the
requirements in this section apply under the following conditions:
- The time domain measurement resource restriction pattern configured for the PCell (TS 36.331 [2]) indicates at
least one subframe per radio frame for performing the PCell measurements, and
- Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern, and
- The UE is provided with the CRS assistance information (TS 36.331 [2]) and the CRS assistance information is
valid throughout the entire evaluation period.
When the UE is provided with a time-domain measurement resource restriction pattern for serving cell measurements,
the UE Rx-Tx time difference measurement shall meet the measurement requirements specified in Section 8.1.2.7.1 and
accuracy requirements specified in Section 9.1.9.4.
The requirements in this section shall also be met when the number of transmit antenna ports [16] of one or more cells
whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
NOTE: It is up to the UE implementation whether the UE Rx-Tx time difference measurement is performed in
any subframe or in subframes indicated by the time-domain measurement resource restriction pattern.
8.1.2.9.4 E-UTRAN TDD UE Rx-Tx Time Difference Measurements with CRS Assistance
Information
For UE configured with a time-domain measurement resource restriction pattern for PCell measurements, the
requirements in this section apply under the following conditions:
- The time domain measurement resource restriction pattern configured for the PCell (TS 36.331 [2]) indicates at
least one subframe per radio frame for performing the PCell measurements, and
- Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern, and
- The UE is provided with the CRS assistance information (TS 36.331 [2]) and the CRS assistance information is
valid throughout the entire evaluation period.
When the UE is provided with a time-domain measurement resource restriction pattern for serving cell measurements,
the UE Rx-Tx time difference measurement shall meet the measurement requirements specified in Section 8.1.2.7.2 and
accuracy requirements specified in Section 9.1.9.4.
The requirements in this section shall also be met when the number of transmit antenna ports [16] of one or more cells
whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 261 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: It is up to the UE implementation whether the UE Rx-Tx time difference measurement is performed in
any subframe or in subframes indicated by the time-domain measurement resource restriction pattern.
8.2 Capabilities for Support of Event Triggering and Reporting
Criteria
8.2.1 Introduction
This clause contains requirements on UE capabilities for support of event triggering and reporting criteria. As long as
the measurement configuration does not exceed the requirements stated in clause 8.2.2, the UE shall meet the
performance requirements defined in clause 9.
The UE can be requested to make measurements under different measurement identities defined in TS 36.331 [2]. Each
measurement identity corresponds to either event based reporting, periodic reporting, logged measurement reporting [2]
or no reporting. In case of event based reporting, each measurement identity is associated with an event. In case of
periodic reporting, a measurement identity is associated with one periodic reporting criterion. In case of logged
measurement reporting, a measurement identity is associated with one logged measurement reporting criterion. In case
of no reporting, a measurement identity is associated with one no reporting criterion.
The purpose of this clause is to set some limits on the number of different event, periodic, logged measurement and no
reporting criteria the UE may be requested to track in parallel.
8.2.2 Requirements
In this clause a reporting criterion corresponds to either one event (in the case of event based reporting), or one periodic
reporting criterion (in case of periodic reporting), or one logged measurement reporting criterion (in case of logged
measurement reporting), or one no reporting criterion (in case of no reporting). For event based reporting, each instance
of event, with the same or different event identities, is counted as separate reporting criterion in table 8.2.2-1.
The UE shall be able to support in parallel per category up to Ecat reporting criteria according to table 8.2.2-1. For the
measurement categories belonging to measurements on: E-UTRA intra-frequency cells, E-UTRA inter-frequency cells,
and inter-RAT per supported RAT(i.e. without counting other categories that the UE shall always support in parallel),
the UE need not support more than the total number of reporting criteria as follows:
- 26 reporting criteria in total if the UE is not configured with any SCell or PSCell carrier frequency,
- 35 reporting criteria in total if the UE is configured with one SCell carrier frequency,
- 44 reporting criteria in total if the UE is configured with two SCell carrier frequencies,
- 53 reporting criteria in total if the UE is configured with three SCell carrier frequencies,
- 62 reporting criteria in total if the UE is configured with four SCell carrier frequencies,
- 35 reporting criteria in total if the UE is configured with one PSCell carrier frequency, and
- 44 reporting criteria in total if the UE is configured with one PSCell carrier frequency and one SCell carrier
frequency.
Editor’s note: the total reporting criteria above are to be updated if all UEs will have to support RS-SINR
measurements; the total reporting criteria are to be verified when the UE capabilities related to frame structure 3 are
decided.
A UE supporting increased number of carriers to monitor beyond 3 carriers shall be able to support up to 20 reporting
criteria for inter-frequency measurement category according to table 8.2.2-1. Additionally such UE shall be able to
support in parallel per category up to Ecat reporting criteria according to table 8.2.2-1. For the measurement categories
belonging to measurements on: E-UTRA intra-frequency cells, E-UTRA inter-frequency cells, and inter-RAT per
supported RAT, the UE need not support more than the total number of reporting criteria as follows:
- 39 reporting criteria in total if the UE is not configured with any SCell carrier frequency,
- 48 reporting criteria in total if the UE is configured with one SCell carrier frequency,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 262 ETSI TS 136 133 V14.3.0 (2017-04)
- 57 reporting criteria in total if the UE is configured with two SCell carrier frequencies,
- 48 reporting criteria in total if the UE is configured with one PSCell carrier frequency,
- 57 reporting criteria in total if the UE is configured with one PSCell carrier frequency and one SCell carrier
frequencies,
- 66 reporting criteria in total if the UE is configured with three SCell carrier frequencies, and
- 75 reporting criteria in total if the UE is configured with four SCell carrier frequencies.
Editor’s note: the total reporting criteria above are to be updated if all UEs will have to support RS-SINR
measurements; the total reporting criteria are to be verified when the UE capabilities related to frame structure 3 are
decided.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 263 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.2.2-1: Requirements for reporting criteria per measurement category
Measurement category Ecat Note
Intra-frequency Note 1 10 Events for any one or a combination of intra-
frequency RSRP, RSRQ, and RS-SINRNote4 for
E-UTRA intra-frequency cells
Intra-frequency UE Rx-Tx time difference 2 Intra-frequency UE Rx-Tx time difference
measurements reported to E-UTRAN via RRC
and to positioning server via LPP. Applies for
UE supporting both LPP and UE Rx-Tx time
difference measurement.
Intra-frequency RSTD Note 2 1 Intra-frequency RSTD measurement reporting
for UE supporting OTDOA; 1 report capable of
minimum 16 cell measurements for the intra-
frequency
Intra-frequency RSRP and RSRQ measurements 1 Intra-frequency RSRP and RSRQ
for E-CID measurements for E-CID reported to E-SMLC
via LPP [24]. One report capable of at least in
total 9 intra-frequency RSRP and RSRQ
measurements. Applicable to UE capable of
reporting RSRP and RSRQ to E-SMLC via LPP.
Intra-frequency RSSI and channel occupancy 1 One report capable of one UE RSSI and
measurements under operation with frame structure channel occupancy measurement s per serving
3 carrier frequency. Applicable for UE capable of
performing and reporting UE RSSI and channel
occupancy under operation with frame structure
3.
Inter-frequency 10 / 28 Events for any one or a combination of inter-
frequency RSRP, RSRQ, and RS-SINRNote4 for
E-UTRA inter-frequency cells (see note 3)
Inter-frequency RSTD Note 2 1 Inter-frequency RSTD measurement reporting
for UE supporting OTDOA; 1 report capable of
minimum 16 cell measurements for at least one
inter-frequency. Only applicable as specified in
Section 8.1.2.6.
Inter-frequency RSSI and channel occupancy 1 One report capable of one UE RSSI and
measurements under operation with frame structure channel occupancy measurement s for an inter-
3 frequency. Applicable for UE capable of
performing and reporting UE RSSI and channel
occupancy under operation with frame structure
3.
Inter-RAT (GSM, cdma2000 1 x RTT and HRPD) 5 Only applicable for UE with this (inter-RAT)
capability. This requirement (Ecat = 5) is per
supported RAT.
Inter-RAT (UTRAN FDD, UTRAN TDD) 5 or 11 Only applicable for UE with this (inter-RAT)
capability. This requirement (Ecat = 5 or 11) is
per supported RAT. For UE which indicate
support for Increased UE carrier monitoring
UTRA Ecat = 11.
MBSFN measurements for MDT 1 MBSFN measurement reporting for UE
supporting MBSFN measurements (MBSFN
RSRP, MBSFN RSRQ, and MCH BLER) for
MDT [2]; 1 report capable of minimum 1 MBSFN
RSRP measurement [4], 1 MBSFN RSRQ
measurement [4], and 1 MCH BLER
measurement [4].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 264 ETSI TS 136 133 V14.3.0 (2017-04)
Note 1: When the UE is configured with SCell, PSCell or PCell carrier frequency, Ecat for Intra-frequency is
applied per serving frequency.
Note 2: When the UE is configured with one SCell carrier frequency, the UE shall be capable of supporting at
least 2 reporting criteria for all RSTD measurements configured to be performed on PCell carrier
frequency, SCell carrier frequency and inter-frequency carrier. When the UE is configured with two SCell
carrier frequencies, the UE shall be capable of supporting at least 3 reporting criteria for all RSTD
measurements configured to be performed on PCell carrier frequency, the two SCell carrier frequencies
and inter-frequency carrier. These requirements apply when there is a single on-going LPP OTDOA
location session.
Note 3: Support of Ecat of 28 for Measurement category Inter-frequency is applied for a UE supporting increased
number of carriers to monitor beyond 3.
Note 4: For UEs supporting RS-SINR measurements (Editor’s note: the note is to be removed if the RS-SINR
measurement support is mandatory).
8.3 Measurements for E-UTRA carrier aggregation
8.3.1 Introduction
Requirements in this clause are applicable to UE supporting E-UTRA FDD, E-UTRA TDD and/or E-UTRA TDD-FDD
carrier aggregation.
Non configured frequencies may be measured with measurement gaps or autonomous gaps according to the
requirements in clause 8.1.2.3 (E-UTRAN inter frequency measurements and E-UTRAN inter frequency measurements
with autonomous gaps).
For UE, which does not support simultaneous reception and transmission for inter-band TDD CA specified in TS
36.331, and is compliant to the requirements for inter-band CA with uplink in one E-UTRA band and without
simultaneous Rx/Tx specified in TS 36.101, the inter-band CA requirements in Section 8.3 shall apply also with
different TDD UL/DL subframe configurations and/or different special subframe configurations used in CCs of
different bands, under the following additional conditions:
- UE is not simultaneously scheduled in UL and DL on the different CCs, and
- at least DL subframe #0 or DL subframe #5 are available for measurements in the measured cell.
The UE capable of SRS carrier based switching, when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.3 provided the
following condition is met:
- at least DL subframe #0 or DL subframe #5 per radio frame is available for measurements at the UE in the
measured cell.
8.3.2 Measurements of the primary component carrier
Measurements of cells on the primary component carrier shall meet all applicable requirements (FDD or TDD) in
clause 8.1.2.2 (E-UTRAN intra frequency measurements and E-UTRAN intra frequency measurements with
autonomous gaps)
8.3.3 Measurements of a secondary component carrier
A Secondary component carrier may be activated and deactivated by MAC-CE commands as specified in [17]. The
applicable performance requirements depend on whether the SCell on the corresponding frequency is actived or
deactivated.
8.3.3.1 Measurements of a secondary component carrier with active SCell
When the SCell is activated, measurement performance requirements for the frequency are those given in
clause 8.1.2.2(E-UTRAN intra frequency measurements and E-UTRAN intra frequency measurements with
autonomous gaps). If common DRX is in use, then the requirements for that secondary component carrier are given by
the applicable DRX requirements (FDD or TDD) in clause 8.1.2.2, otherwise the non DRX requirements are applicable.
The applicable measurement accuracy requirements are in clause 9.1.11 (Carrier aggregation measurement accuracy)
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 265 ETSI TS 136 133 V14.3.0 (2017-04)
8.3.3.2 Measurements of a secondary component carrier with deactivated SCell
This clause defines the measurement requirements of a secondary component carrier with deactivated SCell based on
the parameter measCycleSCell defined in TS 36.331 [2].
8.3.3.2.1 E-UTRAN secondary component carrier measurements when no common DRX
is used
When no DRX is in use the UE shall be able to identify a new detectable FDD or TDD cell on a secondary component
carrier within Tidentify_scc, according to the parameter measCycleSCell where Tidentify_scc = 20 measCycleSCell
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Clause 9.1.17.2.1 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.7 for a corresponding Band.
The measurement period for deactivated scell measurements is Tmeasure_scc according to the parameter measCycleSCell
where Tmeasure_scc = 5 measCycleSCell. The UE shall be capable of performing RSRP, RSRQ, and RS-SINR
measurements for 8 identified cells on a secondary component carrier, and the UE physical layer shall be capable of
reporting measurements to higher layers with the measurement period of Tmeasure_scc.
The measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.11 (Carrier aggregation
measurement accuracy)
A UE may reconfigure the receiver bandwidth or turn on/off one of the RF chains when performing measurements on
up to four SCCs with deactivated SCell. This may cause interruptions on PCell or activated SCell(s) or both that are
specified in Section 7.8.
8.3.3.2.1.1 Measurement Reporting Requirements
8.3.3.2.1.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the applicable requirements in clause 9.
8.3.3.2.1.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the applicable requirements in clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.3.3.2.1.1.3.
8.3.3.2.1.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
applicable requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 266 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_scc defined in
Clause 8.3.3.2.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to perform
SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_scc defined in clause 8.3.3.2.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_scc provided the timing to that cell has not changed
more than ± 50 Ts and the L3 filter has not been used. When L3 filtering, or the UE is configured to perform SRS
carrier based switching, is used an additional delay can be expected.
8.3.3.2.2 E-UTRAN secondary component carrier measurements when common DRX is
used
When DRX is in use the UE shall be able to identify a new detectable FDD or TDD cell on a secondary component
carrier within Tidentify_scc, according to the parameter measCycleSCell where Tidentify_scc = max(20 measCycleSCell,
Tidentify_scc1). Tidentify_scc1 is given in table 8.3.3.2.2-1.
Table 8.3.3.2.2-1: Requirement for Tidentify_scc1
DRX cycle Tidentify_scc1 (s) (DRX
length (s) cycles)
≤0.04 0.8 (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
Note1: Number of DRX cycle depends
upon the DRX cycle in use
Note2: Time depends upon the DRX
cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- RS-SINR related side conditions given in Clause 9.1.17.2.1 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.7 for a corresponding Band.
The measurement period for deactivated scell measurements is Tmeasure_scc according to the parameter measCycleSCell
where Tmeasure_scc =max( 5 measCycleSCell, Tmeasure_scc1). The UE shall be capable of performing RSRP, RSRQ, and RS-
SINR measurements for 8 identified cells on a secondary component carrier, and the UE physical layer shall be capable
of reporting measurements to higher layers with the measurement period of Tmeasure_scc. Tmeasure_scc1 is given in table
8.3.3.2.2-2
Table 8.3.3.2.2-2: Requirement for Tmeasure_scc1
DRX cycle Tmeasure_scc1 (s)
length (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX cycle in use
Note2: Time depends upon the DRX
cycle in use
The measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.11 (Carrier aggregation
measurement accuracy).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 267 ETSI TS 136 133 V14.3.0 (2017-04)
A UE may reconfigure receiver bandwidth taking into account the SCell activation/deactivation status, and when
making measurements of cells on up to four SCCs with deactivated SCell. This may cause interruptions (packet drops)
to a PCell or activated SCell(s) or both when the PCell and the SCell belong to the same frequency band. No
interruptions while the On Duration timer is running shall be allowed when common DRX is used. The requirement
considers only interruptions due to reconfiguration of the receiver bandwidth, and not due to other causes such as RF
impairments or channel conditions.
8.3.3.2.2.1 Measurement Reporting Requirements
8.3.3.2.2.1.1 Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in periodically triggered measurement reports shall
meet the applicable requirements in clause 9.
8.3.3.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered periodic measurement reports shall
meet the applicable requirements in clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.3.3.2.2.1.3.
8.3.3.2.2.1.3 Event Triggered Reporting
Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the
applicable requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_scc defined in
Clause 8.3.3.2.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to perform
SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_scc defined in clause 8.3.3.2.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_scc provided the timing to that cell has not changed
more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or the UE is configured to perform
SRS carrier based switching, an additional delay can be expected.
8.4 OTDOA RSTD Measurements for E-UTRAN carrier
aggregation
8.4.1 Introduction
This clause contains RSTD measurement requirements on UE capabilities for support of E-UTRA carrier aggregation.
Requirements in this clause are applicable to all carrier aggregation capable UE which have been configured with one or
two downlink Scell(s). Non-configured frequencies may be measured with measurement gaps according to the
requirements in clause 8.1.2.6, i.e., E-UTRAN inter-frequency RSTD measurement period applies. Requirements in this
clause are applicable for E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD carrier aggregation.
For UE, which does not support simultaneous reception and transmission for inter-band TDD CA specified in TS
36.331 [2], and is compliant to the requirements for inter-band CA with uplink in one E-UTRA band and without
simultaneous Rx/Tx specified in TS 36.101 [5], RSTD requirements in Section 8.4 shall apply also with different TDD
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 268 ETSI TS 136 133 V14.3.0 (2017-04)
UL/DL subframe configurations and/or different special subframe configurations used in CCs of different bands, under
the following additional conditions:
- all positioning subframes indicated in the OTDOA assistance data and specified in Section 9.1.10 are available
for RSTD measurements in the measured and reference cells; and
- UE is not simultaneously scheduled in UL and DL on the different CCs.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.4 provided the
following condition is met:
all positioning subframes indicated in the OTDOA assistance data and specified in Section 9.1.10 are available for
RSTD measurements at the UE in the measured and reference cells.
8.4.2 Measurements on the primary component carrier
The RSTD measurements on cells belonging to the primary component carrier shall meet all applicable requirements
(FDD or TDD) specified in clause 8.1.2.5, i.e., E-UTRAN intra-frequency RSTD measurement period applies.
The RSTD measurement accuracy for all the measurements on the primary component carrier shall be fulfilled
according to the accuracy as specified in the sub-clause 9.1.12.
If the PCell is changed, regardless whether the primary component carrier is changed or not while the RSTD
measurements are being performed on cells belonging to the primary component carrier, then the UE shall complete the
ongoing OTDOA measurement session. In case of change of the primary component carrier, the requirements shall
apply only if the primary component carrier is swapped with any of the currently configured secondary component
carrier(s). The UE shall also meet the OTDOA measurement and accuracy requirements for the primary component
carrier. However in this case the total RSTD measurement period ( TRSTD, E - UTRAN, PCell_change ) shall be according to the
following expression:
TRSTD, E - UTRAN, PCell_change = TRSTD, E - UTRAN + K × TPRS + TPCell_change ms ,
where:
K is the number of times the PCell is changed during TRSTD, E - UTRAN, PCell_change ,
TPRS is defined in clause 8.1.2.5,
TPCell_change is the time during which the RSTD measurement may not be possible due to PCell change; it can be up
to 25 ms,
TRSTD, E - UTRAN corresponds to the E-UTRAN intra-frequency RSTD measurement period as specified in
clause 8.1.2.5.
Furthermore, due to the PCell changing the UE shall meet the RSTD measurement accuracy for a PRS bandwidth which
is not larger than the minimum channel bandwidth of those PCell/SCell(s) on whose carriers RSTD measurement is
performed during the RSTD measurement period.
8.4.3 Measurements on a secondary component carrier
The RSTD measurements when all cells are on a configured secondary component carrier shall meet all applicable
requirements (FDD or TDD) specified in clause 8.1.2.5, i.e., E-UTRAN intra-frequency RSTD measurement period
applies, regardless of whether the Scell on the corresponding frequency is activated or deactivated by the MAC-CE
commands as specified in [17].
The RSTD measurement accuracy for all the measurements on the secondary component carrier shall be fulfilled
according to the accuracy as specified in the sub-clause 9.1.12.
A UE may reconfigure receiver bandwidth taking into account the SCell activation/deactivation status, RACH
transmission over SCell without PUSCH if capable of SRS carrier based switching, and when making RSTD
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 269 ETSI TS 136 133 V14.3.0 (2017-04)
measurements on cells belonging to SCC with deactivated SCell. This may cause interruptions (packet drops) to a PCell
when the PCell and the SCell belong to the adjacent or non-adjacent component carriers in the same frequency band or
to different frequency bands. In this case, the UE shall follow the interruption requirements specified in Section 7.10.
No interruption to the PCell shall be allowed during the PRS positioning occasion on the PCell.
If the PCell is changed, regardless whether the primary component carrier is changed or not while the RSTD
measurements are being performed on cells belonging to the secondary component carrier, then the UE shall complete
the ongoing OTDOA measurement session. In case of change of the primary component carrier, the requirements shall
apply only if the primary component carrier is swapped with any of the currently configured secondary component
carrier(s). The UE shall also meet the OTDOA measurement and accuracy requirements for the secondary component
carrier. However in this case the total RSTD measurement period ( TRSTD, E - UTRAN, PCell_change ) shall be according to the
following expression:
TRSTD, E - UTRAN, PCell_change = TRSTD, E - UTRAN + K × TPRS + TPCell_change ms ,
where:
K is the number of times the PCell is changed during TRSTD, E - UTRAN, PCell_change ,
TPRS is defined in clause 8.1.2.5,
TPCell_change is the time during which the RSTD measurement may not be possible due to PCell change; it can be up
to 25 ms,
TRSTD, E - UTRAN corresponds to the E-UTRAN intra-frequency RSTD measurement period as specified in
clause 8.1.2.5.
Furthermore, due to the PCell changing the UE shall meet the RSTD measurement accuracy for a PRS bandwidth which
is not larger than the minimum channel bandwidth of those PCell/SCell(s) on whose carriers RSTD measurement is
performed during the RSTD measurement period.
8.4.4 Measurements on both primary component carrier and a secondary
component carrier
The RSTD measurements of cells on both primary component carrier and a configured secondary component carrier
shall meet all applicable requirements (FDD-FDD, TDD-TDD, TDD-FDD or FDD-TDD inter-Frequency OTDOA)
specified in clause 8.1.2.6, i.e., E-UTRAN inter-frequency RSTD measurement period applies regardless of whether the
SCell on the corresponding frequency is activated or deactivated by the MAC-CE commands as specified in [17], with
the following exceptions
- the number of PRS positioning occasions is as specified in Table 8.4.4-1 shall apply, and
- TDD uplink-downlink subframes configurations as specified in Clause 8.1.2.5.2, Table 8.1.2.5.2-2 shall apply.
Table 8.4.4-1: Number of PRS positioning occasions within measurement period
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS
160 ms 32
>160 ms 16
The RSTD measurement accuracy for all the measurements on both primary component carrier and the secondary
component carrier shall be fulfilled according to the accuracy as specified in the sub-clause 9.1.12.
A UE may reconfigure its receiver bandwidth taking into account the SCell activation/deactivation status, RACH
transmission over SCell without PUSCH if capable of SRS carrier based switching, and when performing RSTD
measurements on cells belonging to at least SCC with deactivated SCell. This may cause interruptions (packet drops) on
a PCell when the PCell and the SCell belong to the adjacent or non-adjacent component carriers in the same frequency
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 270 ETSI TS 136 133 V14.3.0 (2017-04)
band or to different frequency bands. In this case, the UE shall follow the interruption requirements specified in Section
7.10. No interruption to the PCell shall be allowed during the PRS positioning occasion on the PCell.
If the PCell is changed regardless whether the primary component carrier is changed or not while the RSTD
measurements are being performed on cells belonging to both the primary component carrier and the secondary
component carrier then the UE shall complete the ongoing OTDOA measurement session. In case of change of the
primary component carrier, the requirements shall apply only if the primary component carrier is swapped with any of
the currently configured secondary component carrier(s). The UE shall also meet the OTDOA measurement and
accuracy requirements for the primary and secondary component carrier. However in this case the total RSTD
measurement period ( TRSTD, E - UTRAN, PCell_change ) shall be according to the following expression:
TRSTD, E - UTRAN, PCell_change = TRSTD, E - UTRAN + K × TPRS + TPCell_change ms ,
where:
K is the number of times the PCell is changed during TRSTD, E - UTRAN, PCell_change ,
TPRS is defined in clause 8.1.2.6,
TPCell_change is the time during which the RSTD measurement may not be possible due to PCell change; it can be up
to 25 ms,
TRSTD, E - UTRAN corresponds to the E-UTRAN inter-frequency RSTD measurement period as specified in
clause 8.1.2.6 with the exception that the number of PRS positioning occasions is as specified in Table 8.4.4-1.
Furthermore, due to the PCell changing the UE shall meet the RSTD measurement accuracy for a PRS bandwidth which
is not larger than the minimum channel bandwidth of those PCell/SCell(s) on whose carriers RSTD measurement is
performed during the RSTD measurement period.
8.4.5 Measurements on different secondary component carriers
The RSTD measurements of cells on a configured secondary component carrier and another configured secondary
component carrier shall meet all applicable requirements (FDD-FDD, TDD-TDD, TDD-FDD or FDD-TDD inter-
Frequency OTDOA) specified in clause 8.1.2.6, i.e., E-UTRAN inter-frequency RSTD measurement period applies
regardless of whether the SCell on the corresponding frequency is activated or deactivated by the MAC-CE commands
as specified in [17], with the following exceptions
- the number of PRS positioning occasions is as specified in Table 8.4.4-1 shall apply, and
- TDD uplink-downlink subframes configurations as specified in Clause 8.1.2.5.2, Table 8.1.2.5.2-2 shall apply.
Table 8.4.4-1: Number of PRS positioning occasions within measurement period
Positioning subframe Number of PRS positioning occasions M
configuration period TPRS
160 ms 32
>160 ms 16
The RSTD measurement accuracy for all the measurements on the secondary component carriers shall be fulfilled
according to the accuracy as specified in the sub-clause 9.1.12.
A UE may reconfigure its receiver bandwidth taking into account the SCell activation/deactivation status, RACH
transmission over SCell without PUSCH if capable of SRS carrier based switching, and when performing RSTD
measurements on cells belonging to at least SCC with deactivated SCell. This may cause interruptions (packet drops) on
a PCell when the PCell and the SCell belong to the adjacent or non-adjacent component carriers in the same frequency
band or to different frequency bands. In this case, the UE shall follow the interruption requirements specified in Section
7.10. No interruption to the PCell shall be allowed during the PRS positioning occasion on the PCell. No interruption to
the SCells shall be allowed during the PRS positioning occasion on the SCells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 271 ETSI TS 136 133 V14.3.0 (2017-04)
If the PCell is changed regardless whether the primary component carrier is changed or not while the RSTD
measurements are being performed on cells belonging to the secondary component carriers then the UE shall complete
the ongoing OTDOA measurement session. In case of change of the primary component carrier, the requirements shall
apply only if the primary component carrier is swapped with any of the currently configured secondary component
carrier(s). The UE shall also meet the OTDOA measurement and accuracy requirements for the secondary component
carriers. However in this case the total RSTD measurement period ( TRSTD, E - UTRAN, PCell_change ) shall be according to the
following expression:
TRSTD, E - UTRAN, PCell_change = TRSTD, E - UTRAN + K × TPRS + TPCell_change ms ,
where:
K is the number of times the PCell is changed during TRSTD, E - UTRAN, PCell_change ,
TPRS is defined in clause 8.1.2.6,
TPCell_change is the time during which the RSTD measurement may not be possible due to PCell change; it can be up
to 25 ms,
TRSTD, E - UTRAN corresponds to the E-UTRAN inter-frequency RSTD measurement period as specified in
clause 8.1.2.6 with the exception that the number of PRS positioning occasions is as specified in Table 8.4.4-1.
Furthermore, due to the PCell changing the UE shall meet the RSTD measurement accuracy for a PRS bandwidth which
is not larger than the minimum channel bandwidth of those PCell/SCell(s) on whose carriers RSTD measurement is
performed during the RSTD measurement period.
8.5 Measurements for UE category 0
8.5.1 Introduction
The UE category 0 applicability of the requirements in subclause 8.5 is defined in Section 3.6.1.
This clause contains requirements on the UE regarding measurement reporting in RRC_CONNECTED state. The
requirements are specified for E-UTRA intra frequency measurements. These measurements may be used by the E-
UTRAN, e.g. for handover decisions. The measurement quantities are defined in [4], the measurement model is defined
in [22] and measurement accuracies are specified in clause 9. Control of measurement reporting is specified in
TS 36.331 [2].
When the UE is provided with IDC solution, the UE shall also perform RRM measurements and meet the corresponding
requirements in clause 8.
8.5.2 Requirements
8.5.2.1 E-UTRAN intra frequency measurements
The UE shall be able to identify new intra-frequency cells and perform RSRP measurements of identified intra-
frequency cells without an explicit intra-frequency neighbour cell list containing physical layer cell identities. During
the RRC_CONNECTED state the UE shall continuously measure identified intra frequency cells and additionally
search for and identify new intra frequency cells.
8.5.2.1.1 E-UTRAN FDD intra frequency measurements
8.5.2.1.1.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 272 ETSI TS 136 133 V14.3.0 (2017-04)
TMeasurement_Period_U E cat 0, Intra
Tidentify intra_UE cat 0 = Tbasic_identify_E -UTRA _ FDD_UE cat 0 ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_FDD_UE cat 0, intra is 1000 ms
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.13.1 and 9.1.13.2 and RSRQ related side conditions given in
Clause 9.1.13.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band.
TIntra : This is the minimum time that is available for intra frequency measurements, during the measurement period with
an arbitrarily chosen timing. Time is assumed to be available for performing intra frequency measurements whenever
the receiver is guaranteed to be active on the intra frequency carrier.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_ UE cat 0 Intra. If higher layer filtering is used, an additional cell identification delay
can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is 400 ms. When no
measurement gaps are activated, the low complexity UE shall be capable of performing RSRPand RSRQ measurements
for 8 identified-intra-frequency cells, and the UE physical layer shall be capable of reporting measurements to higher
layers with the measurement period of 400 ms. When measurement gaps are activated the UE shall be capable of
performing measurements for at least Ymeasurement intra_UE cat 0 cells , where Ymeasurement intra_ UE cat 0 is defined in the following
equation. If the UE has identified more than Ymeasurement intra_UE cat 0 cells, the UE shall perform measurements of at least 8
identified intra- frequency cells but the reporting rate of RSRP and RSRQ measurements of cells from UE physical
layer to higher layers may be decreased.
⎧⎪ TIntra ⎫⎪
Ymeasurement_intra_UE cat 0 = Floor ⎨ X basic _ measurement _ FDD_UE cat 0 ⋅ ⎬
⎪⎩ TMeasurement_Period_UE cat 0, Intra ⎪⎭
cells where
Xbasic measurement FDD_UE cat 0 = 8 (cells)
TMeasurement_Period_UE cat 0, Intra = 400 ms. The measurement period for Intra frequency RSRP and RSRQ
measurements.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.13.1 and 9.1.13.2,
and the RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.13.3.
8.5.2.1.1.1.1 Measurement Reporting Requirements
8.5.2.1.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
8.5.2.1.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.5.2.1.1.1.1.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 273 ETSI TS 136 133 V14.3.0 (2017-04)
8.5.2.1.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat 0
defined in Clause 8.5.2.1.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat 0 defined in clause 8.5.2.1.1.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period_UE cat 0, Intra provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.5.2.1.1.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra_UE cat 0
as shown in table 8.5.2.1.1.2-1. When eDRX_CONN is in use the UE shall be able to identify a new detectable FDD
intra-frequency cell within Tidentify_intra_UE cat 0 as shown in table 8.5.2.1.1.2-1A.
Table 8.5.2.1.1.2-1: Requirement to identify a newly detectable FDD intrafrequency cell
DRX cycle Tidentify_intra_UE cat 0
length (s) (s) (DRX cycles)
≤0.04 [1] (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX cycle in use
Note2: Time depends upon the DRX
cycle in use
Table 8.5.2.1.1.2-1A: Requirement to identify a newly detectable FDD intra-frequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat 0 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note(20)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.13.1 and 9.1.13.2 and RSRQ related side conditions given in
Clause 9.1.13.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat 0. When
DRX is used, Tmeasure_intra_UE cat 0 is as defined in table 8.5.2.1.1.2-2, when eDRX_CONN is used, Tmeasure_intra_UE cat 0 is as
defined in table 8.5.2.1.1.2-3. The UE shall be capable of performing RSRP and RSRQ measurements for 8 identified-
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 274 ETSI TS 136 133 V14.3.0 (2017-04)
intra-frequency cells, and the UE physical layer shall be capable of reporting measurements to higher layers with the
measurement period of Tmeasure_intra_UE cat 0.
Table 8.5.2.1.1.2-2: Requirement to measure FDD intrafrequency cells
DRX cycle Tmeasure_intra_UE cat 0
length (s) (s) (DRX cycles)
≤0.08 0.4 (Note1)
0.08<DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX cycle in use
Note2: Time depends upon the DRX
cycle in use
Table 8.5.2.1.1.2-3: Requirement to measure FDD intra-frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat 0 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.13.1 and 9.1.13.2,
and the RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.13.3.
8.5.2.1.1.2.1 Measurement Reporting Requirements
8.5.2.1.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
8.5.2.1.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.5.2.1.1.2.1.3.
8.5.2.1.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra, UE cat 0
defined in Clause 8.5.2.1.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat 0 defined in clause 8.5.2.1.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat 0 provided the timing to that cell has not
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 275 ETSI TS 136 133 V14.3.0 (2017-04)
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.5.2.1.2 E-UTRAN intra frequency measurements for HD-FDD
8.5.2.1.2.1 E-UTRAN intra frequency measurements when no DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.5.2.1.1.1 also apply for this section provided the following conditions are met:
- at least downlink subframe # 0 or downlink subframe # 5 per radio frame of an intra-frequency cell to be
identified by the UE is available at the UE over Tidentify_intra_UE cat 0;
- at least one downlink subframe per radio frame of measured cell is available at the UE for RSRP and RSRQ
measurements assuming measured cell is identified cell over Tmeasure_intra_UE cat 0.
8.5.2.1.2.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra_UE cat 0
as shown in table 8.5.2.1.2.2-1. When eDRX_CONN is in use the UE shall be able to identify a new detectable FDD
intra-frequency cell within Tidentify_intra_UE cat 0 as shown in table 8.5.2.1.2.2-1A.
Table 8.5.2.1.2.2-1: Requirement to identify a newly detectable HD-FDD intrafrequency cell
DRX cycle Tidentify_intra_UE cat 0
length (s) (s) (DRX cycles)
≤0.04 1 (Note1)
0.04<DRX- Note2 (50)
cycle≤0.08
0.128 3.2 (32)
0.128<DRX- Note2(25)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX cycle in use
Note2: Time depends upon the DRX
cycle in use
Table 8.5.2.1.2.2-1A: Requirement to identify a newly detectable HD-FDD intra-frequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat 0 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (25)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.13.1 and 9.1.13.2 and RSRQ related side conditions given in
Clause 9.1.13.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band
When DRX is in use, in the RRC_CONNECTED state the measurement period for intra frequency measurements is
Tmeasure_intra_UE cat 0 as shown in table 8.5.2.1.2.2-2. When eDRX_CONN is in use in the RRC_CONNECTED state, the
measurement period for intra-frequency measurements is Tmeasure_intra_UE cat 0 as shown in table 8.5.2.1.2.2-3. The UE
shall be capable of performing RSRP and RSRQ measurements for 8 identified-intra-frequency cells, and the UE
physical layer shall be capable of reporting measurements to higher layers with the measurement period of
Tmeasure_intra_UE cat 0.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 276 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.5.2.1.2.2-2: Requirement to measure HD-FDD intrafrequency cells
DRX cycle Tmeasure_intra_UE cat 0
length (s) (s) (DRX cycles)
≤0.04 0.4 (Note1)
0.04<DRX- Note2 (7)
cycle≤0.16
0.16<DRX- Note2(5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX cycle in use
Note2: Time depends upon the DRX
cycle in use
Table 8.5.2.1.2.2-3: Requirement to measure HD-FDD intra-frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat 0 (s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.13.1 and 9.1.13.2,
and the RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.13.3.
8.5.2.1.1.2.1 Measurement Reporting Requirements
8.5.2.1.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
8.5.2.1.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.5.2.1.1.2.1.3.
8.5.2.1.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat 0
defined in Clause 8.5.2.1.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat 0 defined in clause 8.5.2.1.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat 0 provided the timing to that cell has not
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 277 ETSI TS 136 133 V14.3.0 (2017-04)
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.5.2.1.3 E-UTRAN TDD intra frequency measurements
8.5.2.1.3.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
TMeasurement Period_UE cat 0, Intra
Tidentify intra_UE cat 0 = Tbasic identify E −UTRA _ TDD_UE cat 0, intra ⋅ ms
TIntra
where
Tbasic_identify_E-UTRA_TDD_UE cat 0, intra is 1000 ms
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.13.1 and 9.1.13.2 and RSRQ related side conditions given in
Clause 9.1.13.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band
TIntra : This is the minimum time that is available for intra frequency measurements, during the measurement period with
an arbitrarily chosen timing. Time is assumed to be available for performing intra frequency measurements whenever
the receiver is guaranteed to be active on the intra frequency carrier.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_UE cat 0 Intra. If higher layer filtering is used, an additional cell identification delay
can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is 400 ms. When no
measurement gaps are activated, the UE shall be capable of performing RSRP and RSRQ measurements for 8
identified-intra-frequency cells, and the UE physical layer shall be capable of reporting measurements to higher layers
with the measurement period of 400 ms. When measurement gaps are activated the UE shall be capable of performing
measurements for at least Ymeasurement intra_UE cat 0 cells , where Ymeasurement intra_UE cat 0 is defined in the following equation. If
the UE has identified more than Ymeasurement ,intra_UE cat 0 cells, the UE shall perform measurements of at least 8 identified
intra-frequency cells but the reporting rate of RSRP and RSRQ measurements of cells from UE physical layer to higher
layers may be decreased.
⎧⎪ TIntra ⎫⎪
Ymeasurement intra_UE cat 0 = Floor ⎨ X basic measurement TDD_UE cat 0 ⋅ ⎬
⎪⎩ TMeasurement_Period_UE cat 0, Intra ⎪⎭
cells where
Xbasic measurement TDD_UE cat 0 = 8 (cells)
TMeasurement_Period intra_UE cat 0 = 400 ms. The measurement period for Intra frequency RSRP and RSRQ
measurements.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.13.1 and 9.1.13.2,
and the RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.13.3.
8.5.2.1.3.1.1 Measurement Reporting Requirements
8.5.2.1.3.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 278 ETSI TS 136 133 V14.3.0 (2017-04)
8.5.2.1.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.5.2.1.3.1.1.3.
8.5.2.1.3.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat 0
defined in Clause 8.5.2.1.3.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat 0 defined in clause 8.5.2.1.3.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period Intra_UE cat 0 provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.5.2.1.3.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within Tidentify_intra_UE cat 0
as shown in table 8.5.2.1.3.2-1. When eDRX_CONN is in use the UE shall be able to identify a new detectable TDD
intra-frequency cell within Tidentify_intra_UE cat 0 as defined in table 8.5.2.1.3.2-1A.
Table 8.5.2.1.3.2-1: Requirement to identify a newly detectable TDD intrafrequency cell
DRX cycle Tidentify_intra_UE cat 0
length (s) (s) (DRX cycles)
≤0.04 1 (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the DRX cycle in use
Note2: Time depends upon the DRX
cycle in use
Table 8.5.2.1.3.2-1A: Requirement to identify a newly detectable TDD intra-frequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat 0 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (20)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 279 ETSI TS 136 133 V14.3.0 (2017-04)
- RSRP related side conditions given in Clause 9.1.13.1 and 9.1.13.2 and RSRQ related side conditions given in
Clause 9.1.13.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band
When DRX is in use in the RRC_CONNECTED state the measurement period for intra frequency measurements is
Tmeasure_intra_UE cat 0 as shown in table 8.5.2.1.3.2-2. When eDRX_CONN in the RRC_CONNECTED state is in use, the
measurement period for intra-frequency measurements is Tmeasure_intra_UE cat 0 as defined in table 8.5.2.1.3.2-3. The UE
shall be capable of performing RSRP and RSRQ measurements for 8 identified intra-frequency cells and the UE
physical layer shall be capable of reporting measurements to higher layers with the measurement period of
Tmeasure_intra_UE cat 0.
Table 8.5.2.1.3.2-2: Requirement to measure TDD intra frequency cells
DRX cycle Tmeasure_intra_UE cat 0
length (s) (s) (DRX cycles)
≤0.08 0.4 (Note1)
0.08<DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle
depends upon the
DRX cycle in use.
Note2: Time depends upon the
DRX cycle in use.
Table 8.5.2.1.3.2-3: Requirement to measure TDD intra-frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat 0 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.13.1 and 9.1.13.2,
and the RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.13.3.
8.5.2.1.3.2.1 Measurement Reporting Requirements
8.5.2.1.3.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
8.5.2.1.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.5.2.1.3.2.1.3.
8.5.2.1.3.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.13.1, 9.1.13.2 and 9.1.13.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 280 ETSI TS 136 133 V14.3.0 (2017-04)
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat 0
defined in Clause 8.5.2.1.3.2. When L3 filtering is used or IDC autonomous denial is configured an additional delay can
be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat 0 defined in clause 8.5.2.1.3.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat 0 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.5.2.1.4 E-UTRAN FDD intra frequency measurements with autonomous gaps for UE
category 0
The requirements defined in this subclause 8.5.2.1.4 apply provided the following condition is met:
- Tx diversity or transmission using multiple antennas are supported in the target cell to be detected.
8.5.2.1.4.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify
and report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps
in downlink reception and uplink transmission for receiving MIB and SIB1 message according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If
autonomous gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or
eDRX_CONN is used or not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of
E-UTRA cell within:
Tidentify_C GI_LC-UE, intra = Tbasic _ identify_C GI_LC-UE, intra ms
Where
Tbasic_identify_CGI_LC-UE, intra = 190 ms. This is the time period used in the above equation where the maximum allowed
time for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has been
already identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.2 for a corresponding Band
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI_LC-UE,.intra is applicable when no
DRX is used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI_LC-UE, intra ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall
transmit at least 92 ACK/NACKs on PCell provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 281 ETSI TS 136 133 V14.3.0 (2017-04)
8.5.2.1.4.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.5.2.1.5 E-UTRAN intra frequency measurements with autonomous gaps for HD-FDD UE
category 0
The requirements in this section are applicable for the UE which supports half duplex FDD operation on one or more
supported frequency bands [2].
The requirements defined in this subclause 8.5.2.1.5 apply provided the following condition is met:
- Tx diversity or transmission using multiple antennas are supported in the target cell to be detected.
8.5.2.1.5.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
All the CGI requirements with the exception of requirement on the number of ACK/NACK transmission on PCell
defined in clause 8.5.2.1.4.1 also apply for this section.
For the UE supporting half duplex FDD operation there is no requirement in terms of number of ACK/NACK
transmission on PCell.
8.5.2.1.5.2 ECGI Reporting Delay
The ECGI reporting delay defined in clause 8.5.2.1.4.2 also apply for this section.
8.5.2.1.6 E-UTRAN TDD intra frequency measurements with autonomous gaps for UE
category 0
The requirements defined in this subclause 8.5.2.1.6 apply provided the following condition is met:
- Tx diversity or transmission using multiple antennas are supported in the target cell to be detected.
8.5.2.1.6.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps in
downlink reception and uplink transmission for receiving MIB and SIB1 messages according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If autonomous
gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or eDRX_CONN is used or
not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI_LC-UE, intra = Tbasic _ identify_C GI_LC-UE, intra ms
Where
Tbasic_identify_CGI_LC-UE, intra = 190 ms. This is the time period used in the above equation where the maximum allowed
time for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has been
already identified by the UE.
A cell shall be considered identifiable when the following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.2 for a corresponding Band
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 282 ETSI TS 136 133 V14.3.0 (2017-04)
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI_LC-UE, intra is applicable when no
DRX is used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI_LC-UE, intra ms , over which the UE identifies the new CGI of E-UTRA cell, the UE shall be
able to transmit at least the number of ACK/NACKs stated in Table 8.5.2.1.6.1-1 on PCell provided that:
- there is continuous DL data allocation,
- no DRX and no eDRX_CONN cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured in the PCell or each of activated SCell(s).
Table 8.5.2.1.6.1-1: Requirement on minimum number of ACK/NACKs to transmit during
Tbasic_identify_CGI_LC-UE, intra.
UL/DL configuration Minimum number of
transmitted ACK/NACKs
0 30
1 54
2 68
3 56
4 61
5 66
6 46
8.5.2.1.6.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.6 Discovery signal measurements
8.6.1 Introduction
This clause contains requirements on the UE for measurement reporting in RRC_CONNECTED state when discovery
signal [16] is configured. The requirements are specified for E-UTRA CRS based discovery signal measurements and
CSI-RS based discovery signal measurements. These measurements may be used by the E-UTRAN, e.g. for handover
decisions. The measurement quantities are defined in [4], the measurement model is defined in [22] and measurement
accuracy requirements are specified in clause 9. Control of measurement reporting is specified in TS 36.331 [2].
The requirements in Section 9 are applicable for a UE performing measurements according to Section 8.6.
8.6.2 Requirements for CRS based discovery signal measurements
8.6.2.1 E-UTRAN intra frequency measurements
The UE shall be able to identify new intra-frequency cells and perform measurements of identified intra-frequency cells
without an explicit intra-frequency neighbour cell list containing physical layer cell identities. During the
RRC_CONNECTED state the UE shall continuously measure identified intra frequency cells and additionally search
for and identify new intra frequency cells.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or PRACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.6.2.1 provided
the following condition is met:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 283 ETSI TS 136 133 V14.3.0 (2017-04)
- minimum number of configured discovery signal occasions containing CRS based discovery signal as specified
in section 8.6.2.1 are available for measurements at the UE in the measurement cell.
8.6.2.1.1 E-UTRAN FDD intra frequency measurements
8.6.2.1.1.1 E-UTRAN FDD intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_SCE,
Tidentify_intra_SCE = 12* TDMTC_periodicity + TMeasurement_Period _intra_FDD_CRS
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.14.2 and RSRQ related side conditions given in
Clause 9.1.14.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
TMeasurement_Period _intra_FDD_CRS is the intra-frequency period for measurements as shown in table 8.6.2.1.1.1-1
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period intra_FDD_CRS when no DRX is used. If higher layer filtering is used, an additional
cell identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is TMeasurement_Period
as shown in table 8.6.2.1.1.1-1, when no DRX is in use. The UE shall be capable of performing RSRP and
_intra_FDD_CRS
RSRQ measurements for 3 identified intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_Period _intra_FDD_ CRS
Table 8.6.2.1.1.1-1: Requirement to measure FDD intra frequency cell
Measurement bandwidth [RB] Discovery signal occasion duration TMeasurement_Period intra_FDD_CRS[ms]
(ds-OccasionDuration) [ms]
≥6 ≥1 5 * TDMTC_periodicity
≥ 25 ≥1 3 * TDMTC_periodicity
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.14.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.14.4.
8.6.2.1.1.1.1 Measurement Reporting Requirements
8.6.2.1.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
8.6.2.1.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.1.1.1.1.3.
8.6.2.1.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 284 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_SCE
defined in Clause 8.6.2.1.1.1. When L3 filtering is used or IDC autonomous denial is configured or the UE is configured
to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_SCE defined in clause 8.6.2.1.1.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period _intra_FDD_CRS provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.6.2.1.1.2 E-UTRAN FDD intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_SCE_DRX.
Tidentify_intra_SCE_DRX = 16* Max { TDMTC_periodicity, DRX cycle length}+ TMeasurement_Period _intra_FDD_CRS_DRX
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.14.2 and RSRQ related side conditions given in
Clause 9.1.14.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
TMeasurement_Period _intra_FDD_CRS_DRX is the intra-frequency period for measurements as shown in table 8.6.2.1.1.2-1
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period intra_FDD_ CRS_DRX when DRX is used. If higher layer filtering is used, an additional
cell identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is TMeasurement_Period
_intra_FDD_CRS_DRX as shown in table 8.6.2.1.1.2-1, when DRX is in use. The UE shall be capable of performing RSRP and
RSRQ measurements for 3 identified intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_Period _intra_FDD_ CRS_DRX.
Table 8.6.2.1.1.2-1: Requirement to measure FDD intra frequency cell
Measurement bandwidth [RB] Discovery signal occasion TMeasurement_Period intra_FDD_CRS_DRX [ms]
duration (ds-OccasionDuration)
[ms]
≥6 ≥1 5 * Max{ TDMTC_periodicity, DRX cycle
length }
≥ 25 ≥1 3 * Max{ TDMTC_periodicity, DRX cycle
length }
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.14.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.14.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 285 ETSI TS 136 133 V14.3.0 (2017-04)
8.6.2.1.1.2.1 Measurement Reporting Requirements
8.6.2.1.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
8.6.2.1.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.1.1.2.1.3.
8.6.2.1.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_SCE_DRX
defined in Clause 8.6.2.1.1.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_SCE_DRX defined in clause 8.6.2.1.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period _intra_FDD_CRS_DRX provided the timing to that cell
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be
expected.
8.6.2.1.2 E-UTRAN TDD intra frequency measurements
8.6.2.1.2.1 E-UTRAN TDD intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
Tidentify_intra_SCE,
Tidentify_intra_SCE = 12* TDMTC_periodicity + TMeasurement_Period _intra_TDD_CRS
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.14.2 and RSRQ related side conditions given in
Clause 9.1.14.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
TMeasurement_Period _intra_TDD_CRS is the intra-frequency period for measurements
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period _intra_TDD_CRS when no DRX is used. If higher layer filtering is used, an additional
cell identification delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 286 ETSI TS 136 133 V14.3.0 (2017-04)
In the RRC_CONNECTED state the measurement period for intra frequency measurements is TMeasurement_Period
_intra_TDD_CRS as shown in table 8.6.2.1.2.1-1, when no DRX is in use. The UE shall be capable of performing RSRP and
RSRQ measurements for 3 identified intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_Period _intra_TDD_ CRS
Table 8.6.2.1.2.1-1: Requirement to measure TDD intra frequency cell
Measurement bandwidth[RB] Discovery signal occasion duration TMeasurement_Period intra_TDD_CRS[ms]
(ds-OccasionDuration) [ms]
≥6 ≥2 5 * TDMTC_periodicity
≥ 25 ≥2 3 * TDMTC_periodicity
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.14.2, and RSRQ
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.14.4.
8.6.2.1.2.1.1 Measurement Reporting Requirements
8.6.2.1.2.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
8.6.2.1.2.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.1.2.1.1.3.
8.6.2.1.2.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_SCE
defined in Clause 8.6.2.1.2.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_SCE defined in clause 8.6.2.1.2.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period _intra_TDD_CRS provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.6.2.1.2.2 E-UTRAN TDD intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
Tidentify_intra_SCE_DRX.
Tidentify_intra_SCE_DRX = 16* max { TDMTC_periodicity, DRX cycle length}+ TMeasurement_Period _intra_TDD_CRS_DRX
A cell shall be considered detectable when
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 287 ETSI TS 136 133 V14.3.0 (2017-04)
- RSRP related side conditions given in Sections 9.1.14.2 and RSRQ related side conditions given in
Clause 9.1.14.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period intra_TDD_ CRS_DRX when DRX is used. If higher layer filtering is used, an
additional cell identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is TMeasurement_Period
_intra_TDD_CRS_DRX as shown in table 8.6.2.1.2.2-1, when DRX is in use. The UE shall be capable of performing RSRP and
RSRQ measurements for 3 identified intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_Period _intra_TDD_ CRS_DRX
Table 8.6.2.1.2.2-1: Requirement to measure TDD intra frequency cell
Measurement bandwidth[RB] Discovery signal occasion TMeasurement_Period intra_TDD_CRS_DRX [ms]
duration (ds-OccasionDuration)
[ms]
≥6 ≥2 5 * Max{ TDMTC_periodicity, DRX cycle
length }
≥ 25 ≥2 3 * Max{ TDMTC_periodicity, DRX cycle
length }
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.14.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.14.4.
8.6.2.1.2.2.1 Measurement Reporting Requirements
8.6.2.1.2.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
8.6.2.1.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.1.2.2.1.3.
8.6.2.1.2.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report. When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_SCE_DRX
defined in Clause 8.6.2.1.2.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 288 ETSI TS 136 133 V14.3.0 (2017-04)
If a cell which has been detectable at least for the time period Tidentify_intra_SCE_DRX defined in clause 8.6.2.1.2.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period _intra_TDD_CRS_DRX provided the timing to that
cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay
can be expected.
8.6.2.2 E-UTRAN inter frequency measurements
The UE shall be able to identify new inter-frequency cells and perform RSRP and RSRQ measurements of identified
inter-frequency cells if carrier frequency information is provided by the PCell, even if no explicit neighbour list with
physical layer cell identities is provided. The discovery signal occasion and the measurement gap should be aligned,
provided that also the following additional conditions are fulfilled:
Entire discovery signal occasion should be contained in the measurement gap.
The subframe contained discovery signal for the measurement is not overlapped with the first 0.5ms period and the last
0.5ms period in every gap.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or PRACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.6.2.2 provided
the following condition is met:
- minimum number of configured discovery signal occasions containing CRS based discovery signal as specified
in section 8.6.2.2 are available for measurements at the UE in the measurement cell.
8.6.2.2.1 E-UTRAN FDD – FDD inter-frequency measurements
8.6.2.2.1.1 E-UTRAN FDD – FDD inter frequency measurements when no DRX is used
When measurement gaps are scheduled, or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new FDD inter-frequency within TIdentify_Inter_SCE according to the following expression:
TIdentify_Inter_SCE =13 * Max {TDMTC_periodicity, MGRP}*Nfreq + TMeasurement_Period_inter_FDD_CRS
A cell shall be considered detectable provided following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1.14.2 and RSRQ related side conditions given in Sections
9.1.14.4 are fulfilled,
- SCH_RP|dBm SCH Ês/Iot according to Annex B.2.11 for a corresponding Band,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
TMeasurement_Period _intra_FDD_CRS is the inter-frequency period for measurements as shown in table 8.6.2.2.1.1-1. Nfreq is
defined in clause 8.1.2.1.1.
When measurement gaps are scheduled for FDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP and RSRQ
measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.14.2 and 9.1.14.4,
respectively, with measurement period given by table 8.6.2.2.1.1-1.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 3 identified inter-frequency cells per
FDD inter-frequency for up to 3 FDD inter-frequencies and the UE physical layer shall be capable of reporting RSRP
and RSRQ measurements to higher layers with the measurement period defined in table 8.6.2.2.1.1-1 when no DRX is
in use, either measurement gaps are scheduled or the UE supports capability of conducting such measurements without
gaps.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 289 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.6.2.2.1.1-1: Requirement to measure FDD inter frequency cell
Measurement Discovery signal occasion TMeasurement_Period inter_FDD_CRS [ms]
bandwidth[RB] duration (ds-OccasionDuration)
[ms]
≥6 ≥1 5 * Max{ TDMTC_periodicity,
MGRP}*Nfreq
≥ 25 ≥1 3 * Max{ TDMTC_periodicity,
MGRP}*Nfreq
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.14.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.14.4.
8.6.2.2.1.1.1 Measurement Reporting Requirements
8.6.2.2.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4,respectively.
8.6.2.2.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.2.1.1.1.3.
8.6.2.2.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than TIdentify_Inter_SCE
defined in Clause 8.6.2.2.1.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period TIdentify_Inter_SCE defined in clause 8.6.2.2.1.1 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period_inter_FDD_CRS provided the timing to that cell has not changed more than ± 50 Ts while measurement gap
has not been available and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.6.2.2.1.2 E-UTRAN FDD – FDD inter frequency measurements when DRX is used
When DRX is in use, either measurement gaps are scheduled or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable E-UTRAN FDD inter frequency cell
within Tidentify_inter_SCE_DRX.
Tidentify_inter_SCE DRX = 17 * Max { TDMTC_periodicity, DRX cycle length, MGRP} *Nfreq +TMeasurement_Period_inter_FDD_CRS_DRX
A cell shall be considered detectable when
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 290 ETSI TS 136 133 V14.3.0 (2017-04)
- RSRP related side conditions given in Sections 9.1.14.2 and RSRQ related side conditions given in
Clause 9.1.14.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.11 for a corresponding Band
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
TMeasurement_Period_inter_FDD_CRS_DRX is the inter-frequency period for measurements as shown in Table 8.6.2.2.1.2-1. Nfreq is
defined in clause 8.1.2.1.1.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_inter_FDD_CRS_DRX when DRX is used. If higher layer filtering is used, an additional
cell identification delay can be expected.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 3 identified inter-frequency cells per
FDD inter-frequency for up to 3 FDD inter-frequencies and the UE physical layer shall be capable of reporting RSRP
and RSRQ measurements to higher layers with the measurement period defined in table 8.6.2.2.1.2-1 when DRX is in
use, either measurement gaps are scheduled or the UE supports capability of conducting such measurements without
gaps.
Table 8.6.2.2.1.2-1: Requirement to measure FDD interfrequency cell
Measurement bandwidth[RB] Discovery signal occasion duration TMeasurement_Period inter_FDD_CRS_DRX
(ds-OccasionDuration) [ms] [ms]
≥6 ≥1 5 * Max{ TDMTC_periodicity, DRX cycle
length,MGRP}*Nfreq
≥ 25 ≥1 3 * Max{ TDMTC_periodicity, DRX cycle
length,MGRP}*Nfreq
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.14.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.14.4.
8.6.2.2.1.2.1 Measurement Reporting Requirements
8.6.2.2.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4 respectively.
8.6.2.2.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2 and 9.1.14.4 respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.2.1.2.1.3.
8.6.2.2.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4 respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 291 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_SCE DRX
defined in Clause 8.6.2.2.1.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_SCE DRX defined in clause 8.6.2.2.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period_inter_FDD_CRS_DRX provided the timing to that cell
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be
expected.
8.6.2.2.2 E-UTRAN TDD – TDD inter frequency measurements
8.6.2.2.2.1 E-UTRAN TDD – TDD inter frequency measurements when no DRX is used
When measurement gaps are scheduled, or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new TDD inter-frequency within TIdentify_Inter_SCE according to the following expression:
Tidentify_inter_SCE =13 * Max { TDMTC_periodicity, MGRP}*Nfreq +TMeasurement_Period_inter_TDD_CRS
A cell shall be considered detectable provided following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1.14.2 and RSRQ related side conditions given in Sections
9.1.14.4 are fulfilled,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.11 for a corresponding Band
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
TMeasurement_Period_inter_TDD_CRS is the inter-frequency period for measurements as shown in Table 8.6.2.2.2.1-1. Nfreq is
defined in clause 8.1.2.1.1.
When measurement gaps are scheduled for TDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP and RSRQ
measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.14.2, and 9.1.14.4,
respectively, with measurement period TMeasurement_Period inter_TDD_CRS given by table 8.6.2.2.2.1-1:
Table 8.6.2.2.2.1-1: Requirement to measure TDD interfrequency cell
Measurement bandwidth[RB] Discovery signal occasion duration TMeasurement_Period inter_TDD_CRS [ms]
(ds-OccasionDuration) [ms]
≥6 ≥2 5 * Max{ TDMTC_periodicity,
MGRP}*Nfreq
≥ 25 ≥2 3 * Max{ TDMTC_periodicity,
MGRP}*Nfreq
The UE shall be capable of performing RSRP and RSRQ measurements of at least 3 identified inter-frequency cells per
TDD inter-frequency for up to 3TDD inter-frequencies and the UE physical layer shall be capable of reporting RSRP
and RSRQ measurements to higher layers with the measurement period defined in table 8.6.2.2.2.1-1 when no DRX is
in use, either measurement gaps are scheduled or the UE supports capability of conducting such measurements without
gaps.
8.6.2.2.2.1.1 Measurement Reporting Requirements
8.6.2.2.2.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4, respectively.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 292 ETSI TS 136 133 V14.3.0 (2017-04)
8.6.2.2.2.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.2.2.1.1.3.
8.6.2.2.2.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than TIdentify_Inter defined in
clause 8.6.2.2.2.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period TIdentify_Inter_SCE defined in clause 8.6.2.2.2.1 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period inter_TDD_CRS defined in clause 8.6.2.2.2.1 provided the timing to that cell has not changed more than ± 50
Ts while measurementgap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay
can be expected.
8.6.2.2.2.2 E-UTRAN TDD – TDD inter frequency measurements when DRX is used
When DRX is in use, either measurement gaps are scheduled or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable E-UTRAN TDD inter frequency cell
within Tidentify_inter_SCE_DRX
Tidentify_inter_SCE_DRX = 17 * Max { TDMTC_periodicity, DRX cycle length, MGRP} *Nfreq +TMeasurement_Period_inter_TDD_CRS_DRX
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.14.2 and RSRQ related side conditions given in Sections
9.1.14.4 are fulfilled,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.11 for a corresponding Band
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
TMeasurement_Period_inter_TDD_CRS_DRX is the inter-frequency period for measurements as shown in Table 8.6.2.2.2.2-1. Nfreq is
defined in clause 8.1.2.1.1.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period intra_TDD_CRS_DRX when DRX is used. If higher layer filtering is used, an additional
cell identification delay can be expected.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 3 identified inter-frequency cells per
TDD inter-frequency for up to 3 TDD inter-frequencies and the UE physical layer shall be capable of reporting RSRP
and RSRQ measurements to higher layers with the measurement period defined in table 8.6.2.2.2.2-1 when DRX is in
use, either measurement gaps are scheduled or the UE supports capability of conducting such measurements without
gaps.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 293 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.6.2.2.2.2-1: Requirement to measure TDD interfrequency cell
Measurement bandwidth[RB] Discovery signal occasion duration TMeasurement_Period inter_TDD_CRS_DRX
(ds-OccasionDuration) [ms] [ms]
≥6 ≥2 5 * Max{ TDMTC_periodicity, DRX cycle
length,MGRP}*Nfreq
≥ 25 ≥2 3 * Max{ TDMTC_periodicity, DRX cycle
length,MGRP}*Nfreq
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.14.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.14.4.
8.6.2.2.2.2.1 Measurement Reporting Requirements
8.6.2.2.2.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4, respectively.
8.6.2.2.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.2.2.2.2.1.3.
8.6.2.2.2.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.14.2, and 9.1.14.4, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than TIdentify_Inter defined in
clause 8.6.2.2.2.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_SCE_DRX defined in clause 8.6.2.2.2.2 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period_inter_TDD_CRS_DRX defined in clause 8.6.2.2.2.2 provided the timing to that cell has not changed more than
± 50 Ts while measurementgap has not been available and the L3 filter has not been used. When L3 filtering is used or
IDC autonomous denial is configured, or the UE is configured to perform SRS carrier based switching, an additional
delay can be expected.
8.6.2.2.3 E-UTRAN TDD – FDD inter frequency measurements
8.6.2.2.3.1 E-UTRAN TDD – FDD inter frequency measurements when no DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.2.2.1.1 also apply for this section.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 294 ETSI TS 136 133 V14.3.0 (2017-04)
8.6.2.2.3.2 E-UTRAN TDD – FDD inter frequency measurements when DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.2.2.1.2 also apply for this section.
8.6.2.2.4 E-UTRAN FDD – TDD inter frequency measurements
8.6.2.2.4.1 E-UTRAN FDD – TDD inter frequency measurements when no DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.2.2.2.1 also apply for this section.
8.6.2.2.4.2 E-UTRAN FDD – TDD inter frequency measurements when DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.2.2.2.2 also apply for this section.
8.6.3 Requirements for CSI-RS based discovery signal measurements
8.6.3.1 E-UTRAN intra frequency measurements
The UE shall be able to identify new intra-frequency TPs and perform CSI-RSRP measurements of intra-frequency TPs
with an explicit intra-frequency TP list containing physical layer cell identities. During the RRC_CONNECTED state
the UE shall continuously measure identified intra frequency TPs and additionally search for and identify new intra
frequency TPs.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.6.3.1 provided
the following condition is met:
- minimum number of configured discovery signal occasions containing CSI-RS based discovery signal as
specified in section 8.6.3.1 is available for measurements at the UE in the measurement cell.
8.6.3.1.1 E-UTRAN FDD intra frequency measurements
8.6.3.1.1.1 E-UTRAN FDD intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FDD intra frequency TP within
Tidentify_intra_TP_SCE,
Tidentify_intra_TP_SCE = Tidentify_intra_SCE + TMeasurement_Period _intra_FDD_CSI-RS
A TP shall be considered detectable when
- CSI-RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
Tidentify_intra_SCE is the intra-frequency period for cell identification in section 8.6.2.1.1.1. TMeasurement_Period _intra_FDD_CSI-RS is
the intra-frequency period for TP measurement as shown in table 8.6.3.1.1.1-1.
Identification of a TP shall include identification of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_intra_FDD_CSI-RS when no DRX is used. If higher layer filtering is used, an
additional TP identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is
TMeasurement_Period_intra_FDD_CSI-RS as shown in table 8.6.3.1.1.1-1, when no DRX is in use. The UE shall be capable of
performing CSI-RSRP measurements for 3 identified intra-frequency TPs, and the UE physical layer shall be capable of
reporting measurements to higher layers with the measurement period of TMeasurement_Period_intra_FDD_CSI-RS
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 295 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.6.3.1.1.1-1: Requirement to measure FDD intra frequency TP
Measurement bandwidth [RB] Discovery signal occasion TMeasurement_Period _intra_FDD_CSI-RS
duration (ds-OccasionDuration) [ms]
[ms]
≥6 ≥1 5* TDMTC_periodicity
≥ 25 ≥1 3* TDMTC_periodicity
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.1.1.1.1 Measurement Reporting Requirements
8.6.3.1.1.1.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3.
8.6.3.1.1.1.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.1.1.1.1.3.
8.6.3.1.1.1.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_TP_SCE
defined in Clause 8.6.3.1.1.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_intra_TP_SCE defined in clause 8.6.3.1.1.1 becomes
undetectable for a period ≤ 5 seconds and then the TP becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period _intra_FDD_CSI-RS provided the timing to that TP
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be
expected.
8.6.3.1.1.2 E-UTRAN FDD intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency TP within
Tidentify_intra_TP_SCE_DRX.
Tidentify_intra_TP_SCE_DRX = Tidentify_intra_SCE_DRX + TMeasurement_Period _intra_FDD_CSI-RS_DRX
A TP shall be considered detectable when
- CSI-RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 296 ETSI TS 136 133 V14.3.0 (2017-04)
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
Tidentify_intra_SCE_DRX is the intra-frequency period for cell identification in section 8.6.2.1.1.2. TMeasurement_Period _intra_FDD_CSI-
RS_DRX is the intra-frequency period for TP measurement as shown in table 8.6.3.1.1.2-1.
Identification of a TP shall include identification of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_intra_FDD_CSI-RS_DRX when DRX is used. If higher layer filtering is used, an
additional TP identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is TMeasurement_Period
_intra_FDD_CSI-RS_DRX as shown in table 8.6.3.1.1.2-1, when DRX is in use. The UE shall be capable of performing CSI-
RSRP measurements for 3 identified intra-frequency TPs, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_Period _intra_FDD_ CSI-RS_DRX.
Table 8.6.3.1.1.2-1: Requirement to measure FDD intra frequency TP
Measurement bandwidth Discovery signal occasion duration TMeasurement_Period intra_FDD_ CSI-RS_DRX
[RB] (ds-OccasionDuration) [ms] [ms]
≥6 ≥1 5*Max{TDMTC_periodicity, DRX cycle length}
≥ 25 ≥1 3*Max{TDMTC_periodicity, DRX cycle length}
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.1.1.2.1 Measurement Reporting Requirements
8.6.3.1.1.2.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3.
8.6.3.1.1.2.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.1.1.2.1.3.
8.6.3.1.1.2.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_TP_SCE_DRX
defined in Clause 8.6.3.1.1.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_intra_TP_SCE_DRX defined in clause 8.6.3.1.1.2
becomes undetectable for a period ≤ 5 seconds and then the TP becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period _intra_FDD_CSI-RS_DRX provided the timing to
that TP has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 297 ETSI TS 136 133 V14.3.0 (2017-04)
autonomous denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay
can be expected.
8.6.3.1.2 E-UTRAN TDD intra frequency measurements
8.6.3.1.2.1 E-UTRAN TDD intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable TDD intra frequency TP within
Tidentify_intra_TP_SCE,
Tidentify_intra_TP_SCE = Tidentify_intra_SCE + TMeasurement_Period _intra_TDD_CSI-RS
A TP shall be considered detectable when
- CSI-RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
Tidentify_intra_SCE is the intra-frequency period for cell identification in section 8.6.2.1.2.1. TMeasurement_Period _intra_TDD_CSI-RS is
the intra-frequency period for TP measurement as shown in table 8.6.3.1.2.1-1.
Identification of a TP shall include identification of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_intra_TDD_CSI-RS when no DRX is used. If higher layer filtering is used, an
additional TP identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is TMeasurement_Period
_intra_TDD_CSI-RS as shown in table 8.6.3.1.2.1-1, when no DRX is in use. The UE shall be capable of performing
measurements for 3 identified intra-frequency TPs, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_Period _intra_TDD_ CSI-RS
Table 8.6.3.1.2.1-1: Requirement to measure TDD intra frequency TP
Measurement bandwidth [RB] Discovery signal occasion duration TMeasurement_Period _intra_TDD_CSI-RS
(ds-OccasionDuration) [ms] [ms]
≥6 ≥2 5* TDMTC_periodicity
≥ 25 ≥2 3* TDMTC_periodicity
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.1.2.1.1 Measurement Reporting Requirements
8.6.3.1.2.1.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3.
8.6.3.1.2.1.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.1.2.1.1.3.
8.6.3.1.2.1.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 298 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report. When L3 filtering is used or IDC autonomous denial is configured or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_TP_SCE
defined in Clause 8.6.3.1.2.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_intra_TP_SCE defined in clause 8.6.3.1.2.1 becomes
undetectable for a period ≤ 5 seconds and then the TP becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period _intra_TDD_CSI-RS provided the timing to that TP
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be
expected.
8.6.3.1.2.2 E-UTRAN TDD intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency TP within
Tidentify_intra_TP_SCE_DRX.
Tidentify_intra_TP_SCE_DRX = Tidentify_intra_SCE_DRX + TMeasurement_Period _intra_TDD_CSI-RS_DRX
A TP shall be considered detectable when
- CSI-RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
Tidentify_intra_SCE_DRX is the intra-frequency period for cell identification as shown in section 8.6.2.1.2.2.
TMeasurement_Period_intra_TDD_CSI-RS_DRX is the intra-frequency period for TP measurement as shown in table 8.6.3.1.2.2-1.
Identification of a TP shall include identification of the cell and additionally performing a single measurement with
measurement period of TMeasurement_Period_intra_TDD_CSI-RS_DRX when DRX is used. If higher layer filtering is used, an
additional TP identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is TMeasurement_Period
_intra_TDD_CSI-RS_DRX as shown in table 8.6.3.1.2.2-1, when DRX is in use. The UE shall be capable of performing CSI-
RSRP measurements for 3 identified intra-frequency TPs, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of TMeasurement_Period _intra_TDD_ CSI-RS_DRX
Table 8.6.3.1.2.2-1: Requirement to measure TDD intrafrequency TP
Measurement bandwidth [RB] Discovery signal occasion TMeasurement_Period intra_TDD_ CSI-RS_DRX
duration (ds-OccasionDuration) [ms]
[ms]
≥6 ≥2 5*Max{TDMTC_periodicity, DRX cycle length}
≥ 25 ≥2 3*Max{TDMTC_periodicity, DRX cycle length}
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.1.2.2.1 Measurement Reporting Requirements
8.6.3.1.2.2.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 299 ETSI TS 136 133 V14.3.0 (2017-04)
8.6.3.1.2.2.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.1.2.2.1.3.
8.6.3.1.2.2.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_TP_SCE_DRX
defined in Clause 8.6.3.1.2.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_intra_TP_SCE_DRX defined in clause 8.6.3.1.2.2
becomes undetectable for a period ≤ 5 seconds and then the TP becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period _intra_TDD_CSI-RS_DRX provided the timing to
that TP has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay
can be expected.
8.6.3.2 E-UTRAN inter frequency measurements
The UE shall be able to identify new inter-frequency TPs and perform CSI-RSRP measurements of inter-frequency TP
with an explicit inter-frequency TP list containing physical layer cell identities. The discovery signal occasion and the
measurement gap should be aligned, provided that also the following additional conditions are fulfilled:
Entire discovery signal occasion should be contained in the measurement gap.
The subframe contained discovery signal for the measurement is not overlapped with the first 0.5ms period and the last
0.5ms period in every gap.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.6.3.2 provided
the following condition is met:
- minimum number of configured discovery signal occasions containing CSI-RS based discovery signal as
specified in section 8.6.3.2 is available for measurements at the UE in the measurement cell.
8.6.3.2.1 E-UTRAN FDD – FDD inter frequency measurements
8.6.3.2.1.1 E-UTRAN FDD – FDD inter frequency measurements when no DRX is used
When measurement gaps are scheduled, or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new FDD inter-frequency TP within Tidentify_inter_TP_SCE according to the following
expression:
Tidentify_inter_TP_SCE = Tidentify_Inter_SCE + TMeasurement_Period _inter_FDD_CSI-RS
A TP shall be considered detectable when
- CSI-RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 300 ETSI TS 136 133 V14.3.0 (2017-04)
- SCH_RP and SCH Ês/Iot according to Annex B.2.11 for a corresponding Band
Tidentify_inter_SCE is the inter-frequency period for cell identification as shown in section 8.6.2.2.1.1. Nfreq is defined in
clause 8.1.2.1.1. TMeasurement_Period _inter_FDD_CSI-RS is the inter-frequency period for TP measurement as shown in table
8.6.3.2.1.1-1.
When measurement gaps are scheduled for FDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.14.3, with measurement
period given by table 8.6.3.2.1.1-1.
The UE shall be capable of performing CSI-RSRP measurements of at least 3 identified inter-frequency TPs per FDD
inter-frequency for up to 3 FDD inter-frequencies and the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with the measurement period defined in table 8.6.3.2.1.1-1 when no DRX is in use,
either measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps.
Table 8.6.3.2.1.1-1: Requirement to measure FDD inter frequency TP
Measurement bandwidth [RB] Discovery signal occasion TMeasurement_Period inter_FDD_ CSI-RS [ms]
duration (ds-OccasionDuration)
[ms]
≥6 ≥1 5*Max{TDMTC_periodicity, MGRP }*Nfreq
≥ 25 ≥1 3*Max{TDMTC_periodicity, MGRP }*Nfreq
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.2.1.1.1 Measurement Reporting Requirements
8.6.3.2.1.1.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3.
8.6.3.2.1.1.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.2.1.1.1.3.
8.6.3.2.1.1.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_TP_SCE
defined in Clause 8.6.3.2.1.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 301 ETSI TS 136 133 V14.3.0 (2017-04)
If a TP which has been detectable at least for the time period Tidentify_inter_TP_SCEdefined in clause 8.6.3.2.1.1 becomes
undetectable for a period ≤ 5 seconds and then the TP becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period _inter_FDD_CSI-RS provided the timing to that TP
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be
expected.
8.6.3.2.1.2 E-UTRAN FDD – FDD inter frequency measurements when DRX is used
When DRX is in use, either measurement gaps are scheduled or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable E-UTRAN FDD inter frequency TP
within Tidentify_inter_TP_SCE_DRX according to the following expression:
Tidentify_inter_TP_SCE_DRX = Tidentify_inter_SCE_DRX + TMeasurement_Period_inter_FDD_CSI-RS_DRX
A TP shall be considered detectable when
- CSI-RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.11 for a corresponding Band
Tidentify_inter_SCE_DRX is the inter-frequency period for cell identification as shown in section 8.6.2.2.1.2. Nfreq is defined in
clause 8.1.2.1.1. TMeasurement_Period_inter_FDD_CSI-RS_DRX is the inter-frequency period for TP measurement as shown in table
8.6.3.2.1.2-1.
When measurement gaps are scheduled for FDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.14.3, with measurement
period given by table 8.6.3.2.1.2-1.
The UE shall be capable of performing CSI-RSRP measurements of at least 3 identified inter-frequency TPs per FDD
inter-frequency for up to 3 FDD inter-frequencies and the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with the measurement period defined in table 8.6.3.2.1.2-1 when DRX is in use, either
measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps.
Table 8.6.3.2.1.2-1: Requirement to measure FDD inter frequency TP
Measurement bandwidth Discovery signal occasion duration TMeasurement_Period inter_FDD_ CSI-RS_DRX
[RB] (ds-OccasionDuration) [ms] [ms]
≥6 ≥1 5*Max{TDMTC_periodicity, DRX cycle
length, MGRP}*Nfreq
≥ 25 ≥1 3*Max{TDMTC_periodicity, DRX cycle
length, MGRP}*Nfreq
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.2.1.2.1 Measurement Reporting Requirements
8.6.3.2.1.2.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3 respectively.
8.6.3.2.1.2.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.2.1.2.1.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 302 ETSI TS 136 133 V14.3.0 (2017-04)
8.6.3.2.1.2.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_TP_SCE_DRX
defined in clause 8.6.3.2.1.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured
to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_inter_TP_SCE_DRX defined in clause 8.6.3.2.1.2 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period_inter_FDD_CSI-RS_DRX provided the timing to that TP has not changed more than ± 50 Ts while measurement
gap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.6.3.2.2 E-UTRAN TDD – TDD inter frequency measurements
8.6.3.2.2.1 E-UTRAN TDD – TDD inter frequency measurements when no DRX is used
When measurement gaps are scheduled, or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new TDD inter-frequency TP within Tidentify_inter_TP_SCE according to the following
expression:
Tidentify_inter_TP_SCE = Tidentify_inter_SCE + TMeasurement_Period _inter_TDD_CSI-RS
A TP shall be considered detectable when
- CSI-RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.11 for a corresponding Band
Tidentify_inter_SCE is the inter-frequency period for cell identification as shown in section 8.6.2.2.2.1. Nfreq is defined in
clause 8.1.2.1.1. TMeasurement_Period _inter_TDD_CSI-RS is the inter-frequency period for TP measurement as shown in table
8.6.3.2.2.1-1.
When measurement gaps are scheduled for TDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP measurements
to higher layers with measurement accuracy as specified in sub-clauses 9.1.14.3, with measurement period given by
table 8.6.3.2.2.1-1.
The UE shall be capable of performing CSI-RSRP measurements of at least 3 identified inter-frequency TP per TDD
inter-frequency for up to 3TDD inter-frequencies and the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with the measurement period defined in table 8.6.3.2.2.1-1 when no DRX is in use,
either measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps.
Table 8.6.3.2.2.1-1: Requirement to measure TDD inter frequency TP
Measurement bandwidth [RB] Discovery signal occasion TMeasurement_Period inter_TDD_ CSI-RS
duration (ds-OccasionDuration) [ms]
[ms]
≥6 ≥2 5*Max{TDMTC_periodicity, MGRP}*Nfreq
≥ 25 ≥2 3*Max{TDMTC_periodicity,
MGRP }*Nfreq
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 303 ETSI TS 136 133 V14.3.0 (2017-04)
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.2.2.1.1 Measurement Reporting Requirements
8.6.3.2.2.1.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3.
8.6.3.2.2.1.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.2.2.1.1.3.
8.6.3.2.2.1.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_TP_SCE
defined in clause 8.6.3.2.2.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured
to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_inter_TP_SCE defined in clause 8.6.3.2.2.1 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period _inter_TDD_CSI-RS provided the timing to that TP has not changed more than ± 50 Ts while measurementgap
has not been available and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, or the UE is configured to perform SRS carrier based switching, an additional delay can be expected.
8.6.3.2.2.2 E-UTRAN CSI-RS based TDD – TDD inter frequency measurements when DRX is
used
When DRX is in use, either measurement gaps are scheduled or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable E-UTRAN TDD inter frequency TP
within Tidentify_inter_TP_SCE_DRX according to the following expression:
Tidentify_inter_TP_SCE_DRX = Tidentify_inter_SCE_DRX + TMeasurement_Period _inter_TDD_CSI-RS_DRX
A TP shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.14.3 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.11 for a corresponding Band
Tidentify_inter_SCE_DRX is the inter-frequency period for cell identification as shown in section 8.6.2.2.2.2. Nfreq is defined in
clause 8.1.2.1.1. TMeasurement_Period _inter_TDD_CSI-RS_DRX is the inter-frequency period for TP measurement as shown in table
8.6.3.2.2.2-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 304 ETSI TS 136 133 V14.3.0 (2017-04)
When measurement gaps are scheduled for TDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.14.3, with measurement
period given by table 8.6.3.2.2.2-1.
The UE shall be capable of performing CSI-RSRP measurements of at least 3 identified inter-frequency TPs per TDD
inter-frequency for up to 3 TDD inter-frequencies and the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with the measurement period defined in table 8.6.3.2.2.2-1 when DRX is in use, either
measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps.
Table 8.6.3.2.2.2-1: Requirement to measure TDD inter frequency TP
Measurement bandwidth Discovery signal occasion duration TMeasurement_Period inter_TDD_ CSI-RS_DRX
[RB] (ds-OccasionDuration) [ms] [ms]
≥6 ≥2 5*Max{TDMTC_periodicity, DRX cycle
length, MGRP}*Nfreq
≥ 25 ≥2 3*Max{TDMTC_periodicity, DRX cycle
length, MGRP}*Nfreq
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in the sub-clauses 9.1.14.3.
8.6.3.2.2.2.1 Measurement Reporting Requirements
8.6.3.2.2.2.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in sections 9.1.14.3.
8.6.3.2.2.2.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.14.3.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.6.3.2.2.2.1.3.
8.6.3.2.2.2.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
sections 9.1.14.3.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_TP_SCE_DRX
defined in Clause 8.6.3.2.2.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is
configured to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_inter_TP_SCE_DRX in clause 8.6.3.2.2.2 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
TMeasurement_Period _inter_TDD_CSI-RS_DRX provided the timing to that TP has not changed more than ± 50 Ts while
measurement gap has not been available and the L3 filter has not been used. When L3 filtering is used or IDC
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 305 ETSI TS 136 133 V14.3.0 (2017-04)
autonomous denial is configured, or the UE is configured to perform SRS carrier based switching, an additional delay
can be expected.
8.6.3.2.3 E-UTRAN TDD – FDD inter frequency measurements
8.6.3.2.3.1 E-UTRAN TDD – FDD inter frequency measurements when no DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.3.2.1.1 also apply for this section.
8.6.3.2.3.2 E-UTRAN TDD – FDD inter frequency measurements when DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.3.2.1.2 also apply for this section.
8.6.3.2.4 E-UTRAN FDD – TDD inter frequency measurements
8.6.3.2.4.1 E-UTRAN FDD – TDD inter frequency measurements when no DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.3.2.2.1 also apply for this section.
8.6.3.2.4.2 E-UTRAN FDD – TDD inter frequency measurements when DRX is used
The requirements in this clause shall apply to UE supporting FDD and TDD.
The requirements in clause 8.6.3.2.2.2 also apply for this section.
8.7 Discovery signal measurements for E-UTRA carrier
aggregation
8.7.1 Introduction
Requirements in this clause are applicable to UE supporting E-UTRA FDD, E-UTRA TDD and/or E-UTRA TDD-FDD
carrier aggregation.
Non configured frequencies may be measured with measurement gaps according to the requirements in clause 8.6.2.2
and clause 8.6.3.2 (E-UTRAN CRS based inter frequency measurements and E-UTRAN CSI-RS based inter frequency
measurements).
8.7.2 Requirements for CRS based discovery signal measurements for E-
UTRA carrier aggregation
8.7.2.1 Measurements of the primary component carrier
CRS based measurements of cells on the primary component carrier shall meet all applicable requirements (FDD or
TDD) in clause 8.6.2.1.
8.7.2.2 Measurements of a secondary component carrier
A Secondary component carrier may be activated and deactivated by MAC-CE commands as specified in [17]. The
applicable performance requirements depend on whether the SCell on the corresponding frequency is actived or
deactivated.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 306 ETSI TS 136 133 V14.3.0 (2017-04)
8.7.2.3 Measurements of a secondary component carrier with active SCell
When the SCell is activated, measurement performance requirements for the frequency are those given in clause 8.6.2.1.
If common DRX is in use, then the requirements for that secondary component carrier are given by the applicable DRX
requirements (FDD or TDD) in clause 8.6.2.1 , otherwise the non DRX requirements are applicable. The applicable
measurement accuracy requirements are in clause 9.1.15.
8.7.2.4 Measurements of a secondary component carrier with deactivated SCell
This clause defines the measurement requirements of a secondary component carrier with deactivated SCell based on
the parameter measCycleSCell defined in TS 36.331 [2].
8.7.2.4.1 E-UTRAN secondary component carrier measurements when no common DRX
is used
When no DRX is in use the UE shall be able to identify a new detectable FDD or TDD cell on a secondary component
carrier within Tidentify_scc_SCE, according to the parameter measCycleSCell where Tidentify_scc_CRS = 13 *measCycleSCell+
Tmeasure_scc_CRS
A cell shall be considered detectable when
- RSRP related side condition given in Clause 9.1.15 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
The measurement period for deactivated scell measurements is Tmeasure_scc_CRS according to the parameter
measCycleSCell shown in Tables 8.7.2.4.1-1 and 8.7.2.4.1-2.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or PRACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.7.2.4.1 provided
the following condition is met:
- minimum number of configured discovery signal occasions containing CRS based discovery signal as specified
in section 8.7.2.4.1 are available for measurements at the UE in the measurement cell.
Table 8.7.2.4.1-1: Requirement to measure intra frequency cell on FDD SCC with deactivated SCell
Measurement bandwidth[RB] Discovery signal occasion duration Tmeasure_scc_CRS [ms]
(ds-OccasionDuration) [ms]
≥6 ≥1 5* measCycleSCell
≥ 25 ≥1 3 * measCycleSCell
Table 8.7.2.4.1-2: Requirement to measure intra frequency cell on TDD SCC with deactivated SCell
Measurement bandwidth [RB] Discovery signal occasion duration Tmeasure_scc_CRS [ms]
(ds-OccasionDuration) [ms]
≥6 ≥2 5* measCycleSCell
≥ 25 ≥2 3 * measCycleSCell
The UE shall be capable of performing RSRP and RSRQ measurements for 3 identified cells on a secondary component
carrier, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement
period of Tmeasure_scc_CRS.
The measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.15.
A UE may reconfigure the receiver bandwidth or turn on/off one of the RF chains when performing measurements on
up to four SCCs with deactivated SCell. This may cause interruptions on PCell or activated SCell(s) or both that are
specified in Section 7.8.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 307 ETSI TS 136 133 V14.3.0 (2017-04)
8.7.2.4.1.1 Measurement Reporting Requirements
8.7.2.4.1.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in
clause 9.
8.7.2.4.1.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic CRS based measurement reporting shall meet the requirements specified in
clause 8.7.2.4.1.1.3.
8.7.2.4.1.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_scc_CRS defined
in Clause 8.7.2.4.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_scc_SCE defined in clause 8.7.2.4.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_scc_CRS provided the timing to that cell has not changed
more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used, or the UE is configured to perform
SRS carrier based switching, an additional delay can be expected.
8.7.2.4.2 E-UTRAN secondary component carrier measurements when common DRX is
used
When DRX is in use the UE shall be able to identify a new detectable FDD or TDD cell on a secondary component
carrier within Tidentify_scc, according to the parameter measCycleSCell where Tidentify_scc_SCE_DRX =
17*Max(measCycleSCell, DRX cycle length)+Tmeasure_scc_CRS_DRX.
A cell shall be considered detectable when
- RSRP related side condition given in Clause 9.1.15 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
The measurement period for deactivated scell measurements is Tmeasure_scc_CRS_DRX according to the parameter
measCycleSCell shown in Tables 8.7.2.4.2-1 and 8.7.2.4.2-2.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or PRACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.7.2.4.2 provided
the following condition is met:
- -minimum number of configured discovery signal occasions containing CRS based discovery signal as specified
in section 8.7.2.4.2 are available for measurements at the UE in the measurement cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 308 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.7.2.4.2-1: Requirement to measure intrafrequency cell on FDD SCC with deactivated SCell
Measurement bandwidth[RB] Discovery signal occasion Tmeasure_scc_CRS_DRX [ms]
duration (ds-OccasionDuration)
[ms]
≥6 ≥1 5* Max{ measCycleSCell, DRX cycle length }
≥ 25 ≥1 3 * Max{ measCycleSCell, DRX cycle length }
Table 8.7.2.4.2-2: Requirement to measure intrafrequency cell on TDD SCC with deactivated SCell
Measurement bandwidth[RB] Discovery signal occasion duration Tmeasure_scc_CRS_DRX [ms]
(ds-OccasionDuration) [ms]
≥6 ≥2 5* Max{ measCycleSCell, DRX cycle length }
≥ 25 ≥2 3 * Max{ measCycleSCell, DRX cycle
length }
The UE shall be capable of performing RSRP and RSRQ measurements for 3 identified cells on a secondary component
carrier, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement
period of Tmeasure_scc_CRS_DRX.
The measurement accuracy for all measured cells shall be as specified in the sub-clause 9.1.15.
A UE may reconfigure receiver bandwidth taking into account the SCell activation/deactivation status, and when
making measurements of cells on up to four SCCs with deactivated SCell. This may cause interruptions (packet drops)
to a PCell or activated SCell(s) or both when the PCell and the SCell belong to the same frequency band. No
interruptions while the On Duration timer is running shall be allowed when common DRX is used. The requirement
considers only interruptions due to reconfiguration of the receiver bandwidth, and not due to other causes such as RF
impairments or channel conditions.
8.7.2.4.2.1 Measurement Reporting Requirements
8.7.2.4.2.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in
clause 9.
8.7.2.4.2.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.7.2.4.2.1.3.
8.7.2.4.2.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered CRS based measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_scc_CRS defined
in Clause 8.7.2.4.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 309 ETSI TS 136 133 V14.3.0 (2017-04)
If a cell which has been detectable at least for the time period Tidentify_scc_SCE_DRX defined in clause 8.7.2.4.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_scc_CRS_DRX provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
8.7.3 Requirements for CSI-RS based discovery signal measurements for
E-UTRA carrier aggregation
8.7.3.1 Measurements of the primary component carrier
Measurements of cells on the primary component carrier shall meet all applicable requirements (FDD or TDD) in
clause 8.6.3.1.
8.7.3.2 Measurements of a secondary component carrier
A Secondary component carrier may be activated and deactivated by MAC-CE commands as specified in [17]. The
applicable performance requirements depend on whether the SCell on the corresponding frequency is actived or
deactivated.
8.7.3.3 Measurements of a secondary component carrier with active SCell
When the SCell is activated, measurement performance requirements for the frequency are those given in clause 8.6.3.1.
If common DRX is in use, then the requirements for that secondary component carrier are given by the applicable DRX
requirements (FDD or TDD) in clause 8.6.3.1 , otherwise the non DRX requirements are applicable. The applicable
measurement accuracy requirements are in clause 9.1.15.
8.7.3.4 Measurements of a secondary component carrier with deactivated SCell
This clause defines the measurement requirements of a secondary component carrier with deactivated SCell based on
the parameter measCycleSCell defined in TS 36.331 [2].
8.7.3.4.1 E-UTRAN secondary component carrier measurements when no common DRX
is used
When no DRX is in use the UE shall be able to identify a new detectable FDD or TDD TP on a secondary component
carrier within Tidentify_scc_TP_SCE, according to the parameter measCycleSCell, where Tidentify_scc_TP_SCE = Tidentify_scc_SCE +
Tmeasure_scc_CSI-RS,
A cell shall be considered detectable when
- CSI-RSRP related side condition given in Clause 9.1.15 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
Tidentify_scc_SCE is the intra-frequency period for cell identification in section 8.7.2.4.1. Tmeasure_scc_CSI-RS is the intra-
frequency period for TP measurement in table 8.7.3.4.1-1.
The measurement period for deactivated scell measurements is Tmeasure_scc_CSI-RS according to the parameter
measCycleSCell as shown in tables 8.7.3.4.1-1 and 8.7.3.4.1-2.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.7.3.4.1 provided
the following condition is met:
- minimum number of configured discovery signal occasions containing CSI-RS based discovery signal as
specified in section 8.7.3.4.1 is available for measurements at the UE in the measurement cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 310 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.7.3.4.1-1: Requirement to measure intra frequency TP on FDD SCC with deactivated SCell
Measurement bandwidth [RB] Discovery signal occasion Tmeasure_scc_CSI-RS [ms]
duration (ds-OccasionDuration)
[ms]
≥6 ≥1 5* measCycleSCell
≥ 25 ≥1 3* measCycleSCell
Table 8.7.3.4.1-2: Requirement to measure intra frequency TP on TDD SCC with deactivated SCell
Measurement bandwidth [RB] Discovery signal occasion Tmeasure_scc_CSI-RS [ms]
duration (ds-OccasionDuration)
[ms]
≥6 ≥2 5* measCycleSCell
≥ 25 ≥2 3* measCycleSCell
The UE shall be capable of performing RSRP measurements for 3 identified TPs on a secondary component carrier, and
the UE physical layer shall be capable of reporting measurements to higher layers with the measurement period of
Tmeasure_scc_CSI-RS.
The measurement accuracy for all measured TPs shall be as specified in the sub-clause 9.1.15.
A UE may reconfigure the receiver bandwidth or turn on/off one of the RF chains when performing measurements on
up to four SCCs with deactivated SCell. This may cause interruptions on PCell or activated SCell(s) or both that are
specified in Section 7.8.
8.7.3.4.1.1 Measurement Reporting Requirements
8.7.3.4.1.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in
clause 9.
8.7.3.4.1.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.7.3.4.1.1.3.
8.7.3.4.1.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_scc_TP_SCE
defined in Clause 8.7.3.4.1. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured
to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_scc_TP_SCE defined in clause 8.7.3.4.1 becomes
undetectable for a period ≤ 5 seconds and then the TP becomes detectable again and triggers an event, the event
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 311 ETSI TS 136 133 V14.3.0 (2017-04)
triggered measurement reporting delay shall be less than Tmeasure_scc_CSI-RS provided the timing to that TP has not changed
more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used, or the UE is configured to perform
SRS carrier based switching, an additional delay can be expected.
8.7.3.4.2 E-UTRAN secondary component carrier measurements when common DRX is
used
When DRX is in use the UE shall be able to identify a new detectable FDD or TDD TP on a secondary component
carrier within Tidentify_scc_TP_SCE_DRX, according to the parameter measCycleSCell, where Tidentify_scc_TP_SC E_DRX =
Tidentify_scc_SCE_DRX + Tmeasure_scc_CSI-RS_DRX,
A cell shall be considered detectable when
- CSI-RSRP related side condition given in Clause 9.1.15 are fulfilled for a corresponding Band,
- SCH_RP|dBm and SCH Ês/Iot according to Annex B.2.10 for a corresponding Band
Tidentify_scc_SCE_DRX is the intra-frequency period for cell identification in section 8.7.2.4.2. Tmeasure_scc_CSI-RS_DRX is the
intra-frequency period for TP measurement in table 8.7.3.4.2-1.
The measurement period for deactivated scell measurements is Tmeasure_scc_CSI-RS_DRX according to the parameter
measCycleSCell as shown in tables 8.7.3.4.2-1 and 8.7.3.4.2-2.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.7.3.4.2 provided
the following condition is met:
- minimum number of configured discovery signal occasions containing CSI-RS based discovery signal as
specified in section 8.7.3.4.2 is available for measurements at the UE in the measurement cell.
Table 8.7.3.4.2-1: Requirement to measure intrafrequency TP on FDD SCC with deactivated SCell
Measurement bandwidth [RB] Discovery signal occasion duration Tmeasure_scc_CSI-RS_DRX [ms]
(ds-OccasionDuration) [ms]
≥6 ≥1 5* max {measCycleSCell, DRX
cycle length }
≥ 25 ≥1 3* max {measCycleSCell, DRX
cycle length }
Table 8.7.3.4.2-2: Requirement to measure intrafrequency TP on TDD SCC with deactivated SCell
Measurement bandwidth [RB] Discovery signal occasion duration Tmeasure_scc_CSI-RS_DRX [ms]
(ds-OccasionDuration) [ms]
≥6 ≥2 5* max {measCycleSCell, DRX cycle length }
≥ 25 ≥2 3* max {measCycleSCell, DRX cycle length }
The UE shall be capable of performing CSI-RSRP measurements for 3 identified TPs on a secondary component
carrier, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement
period of Tmeasure_scc_CSI-RS_DRX.
The measurement accuracy for all measured TPs shall be as specified in the sub-clause 9.1.15.
A UE may reconfigure receiver bandwidth taking into account the SCell activation/deactivation status, and when
making measurements of TPs on up to four SCCs with deactivated SCell. This may cause interruptions (packet drops)
to a PCell or activated SCell(s) or both when the PCell and the SCell belong to the same frequency band. No
interruptions while the On Duration timer is running shall be allowed when common DRX is used. The requirement
considers only interruptions due to reconfiguration of the receiver bandwidth, and not due to other causes such as RF
impairments or channel conditions.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 312 ETSI TS 136 133 V14.3.0 (2017-04)
8.7.3.4.2.1 Measurement Reporting Requirements
8.7.3.4.2.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in
clause 9.
8.7.3.4.2.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
clause 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.7.3.4.2.1.3.
8.7.3.4.2.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in clause 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_scc_TP_SCE_DRX
defined in Clause 8.7.3.4.2. When L3 filtering is used or IDC autonomous denial is configured, or the UE is configured
to perform SRS carrier based switching, an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_scc_TP_SCE_DRX defined in clause 8.7.3.4.2 becomes
undetectable for a period ≤ 5 seconds and then the TP becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_scc_CSI-RS_DRX provided the timing to that TP has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used, or the UE is configured to
perform SRS carrier based switching, an additional delay can be expected.
8.8 Measurements for E-UTRA dual connectivity
8.8.1 Introduction
This clause contains requirements for UE supporting E-UTRA dual connectivity. Requirements in this clause are
applicable to UEs which have been configured with one SCell in either MCG or SCG and one PSCell for inter-band
dual connectivity. Requirements in this clause are applicable to E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD
dual connectivity.
The UE capable of SRS carrier based switching when configured to perform SRS transmission and/or RACH
transmission over one or more SCells without PUSCH shall meet the requirements defined in Section 8.8 provided the
following condition is met:
- at least DL subframe #0 or DL subframe #5 per radio frame is available for measurements at the UE in the
measurement cell.
8.8.2 Intra-frequency measurements requirements on PCell
PCell intra-frequency measurements shall meet all applicable requirements in clause 8.1.2.2. If MCG DRX is in use,
then the PCell intra-frequency requirements for when DRX is in use in clause 8.1.2.2 shall apply and shall depend on
the MCG DRX cycle. Otherwise, the requirements for when DRX is not in use shall apply. The applicable measurement
accuracy requirements are in clause 9.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 313 ETSI TS 136 133 V14.3.0 (2017-04)
8.8.3 Intra-frequency measurements requirements on PSCell
PSCell starts with activated state upon configuration and cannot be deactivated. PSCell intra-frequency measurements
shall meet all applicable requirements in clause 8.1.2.2. If SCG DRX is in use, then the PSCell intra-frequency
requirements for when DRX is in use in clause 8.1.2.2 shall apply and shall depend on the SCG DRX cycle. Otherwise,
the requirements for when DRX is not in use shall apply. The applicable measurement accuracy requirements are in
clause 9.1.
8.8.4 Inter-frequency and inter-RAT measurement requirements
Inter-frequency measurements shall meet all applicable requirements in clause 8.1.2.3. If MCG DRX is in use, then the
inter-frequency requirements for when DRX is in use in clause 8.1.2.3 shall apply and shall depend on the MCG DRX
cycle. Otherwise, the requirements for when DRX is not in use shall apply. The applicable measurement accuracy
requirements are in clause 9.1.
Inter-RAT measurements shall meet all applicable requirements in clause 8.1.2.4. If MCG DRX is in use, then the inter-
RAT requirements for when DRX is in use in clause 8.1.2.4 shall apply and shall depend on the MCG DRX cycle.
Otherwise, the requirements for when DRX is not in use shall apply. The applicable measurement accuracy
requirements are in clause 9.2, 9.3, 9.4 and 9.5.
8.8.5 Intra-frequency measurements with autonomous gaps
8.8.5.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps in
both MCG and SCG in downlink reception and uplink transmission for receiving MIB and SIB1 messages according to
clause 5.5.3.1 of TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to
false. If autonomous gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX is
used or whether the SCell is configured, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI, intra = Tbasic _ identify_C GI, intra ms
where
Tbasic_identify_CGI, intra = 150 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has been already
identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.2 for a corresponding Band
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided that the PBCH
demodulation requirements in [5] are met.
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI,.intra is applicable when no DRX is
used as well as when any of the DRX cycles specified in TS 36.331 [2] is used.
Within the time Tidentify_C GI, intra ms, over which the UE identifies the CGI of a new E-UTRA cell, the UE shall transmit
at least a minimum number of ACK/NACKs on cells in MCG and SCG, respectively, as specified in Table 8.8.5.1-1.
The requirement depends on duplex mode, dual connectivity mode of operation, and whether a cell belongs to MCG or
SCG, and is further conditioned on:
- there is continuous DL data allocation,
- no DRX cycle is used,
- no measurement gaps are configured,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 314 ETSI TS 136 133 V14.3.0 (2017-04)
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured.
Table 8.8.5.1-1: Requirement on minimum number of ACK/NACKs to transmit during Tidentify_CGI, intra.
Serving cell configuration Minimum number of transmitted ACK/NACKs
Synchronous operation Asynchronous operation
MCG SCG MCG SCG
FDD 60 60 49
TDD UL/DL configuration 0 18 N/A N/A
TDD UL/DL configuration 1 35 N/A N/A
TDD UL/DL configuration 2 43 N/A N/A
TDD UL/DL configuration 3 36 N/A N/A
TDD UL/DL configuration 4 39 N/A N/A
TDD UL/DL configuration 5 42 N/A N/A
TDD UL/DL configuration 6 30 N/A N/A
8.8.5.2 ECGI reporting delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. If IDC autonomous denial is configured, an additional delay can be
expected.
8.8.6 Inter-frequency measurements with autonomous gaps
8.8.6.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps in
both MCG and SCG in downlink reception and uplink transmission for receiving MIB and SIB1 messages according to
clause 5.5.3.1 of TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to
false. If autonomous gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX is
used or whether the SCell is configured, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI, inter = Tbasic _ identify_C GI, inter ms
where
Tbasic_identify_CGI, inter = 150 ms. This is the time period used in the above equation where the maximum allowed time
for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has been already
identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.2 for a corresponding Band
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided that the PBCH
demodulation requirements in [5] are met.
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI,.inter is applicable when no DRX is
used as well as when any of the DRX cycles specified in TS 36.331 [2] is used.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 315 ETSI TS 136 133 V14.3.0 (2017-04)
Within the time Tidentify_CGI,inter ms, over which the UE identifies the CGI of a new E-UTRA cell, the UE shall transmit at
least a minimum number of ACK/NACKs on cells in MCG and SCG, respectively, as specified in Table 8.8.6.1-1. The
requirement depends on duplex mode, dual connectivity mode of operation, and whether a cell belongs to MCG or
SCG, and is further conditioned on:
- there is continuous DL data allocation,
- no DRX cycle is used,
- no measurement gaps are configured,
- only one code word is transmitted in each subframe,
- no MBSFN subframes are configured.
Table 8.8.6.1-1: Requirement on minimum number of ACK/NACKs to transmit during Tidentify_CGI, inter.
Serving cell configuration Minimum number of transmitted ACK/NACKs
Synchronous operation Asynchronous operation
MCG SCG MCG SCG
FDD 60 60 49
TDD UL/DL configuration 0 18 N/A N/A
TDD UL/DL configuration 1 30 N/A N/A
8.8.6.2 ECGI reporting delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. If IDC autonomous denial is configured, an additional delay can be
expected.
8.8.7 SSTD Measurements
8.8.7.1 Introduction
This clause contains SSTD measurement requirements on UE capabilities for support of E-UTRA dual connectivity.
8.8.7.2 SSTD Measurement requirements
When no DRX is used the physical layer measurement period of the SSTD measurement shall be Tmeasure_SSTD1 = 200
ms.
When either MCG DRX or SCG DRX is used, or both MCG DRX and SCG DRX are used in RRC_CONNECTED
state the physical layer measurement period (Tmeasure_SSTD1) of the SSTD measurement shall be as specified in table
8.8.7.2-1.
Table 8.8.7.2-1: SSTD measurement requirement when DRX is used
DRX cycle length (s) Tmeasure_SSTD1 (s) (DRX cycles)
≤0.04 0.2 (Note1)
0.04<DRX-cycle≤2.56 Note2 (5)
Note1: Number of DRX cycle depends upon the DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Note3: DRX cycle length in this table refers to the DRX cycle length
configured on the CG in which DRX is used. When DRX is used in
both MCG and SCG, DRX cycle length in this table refers to the longer
DRX cycle length between MCG DRX and SCG DRX.
If PCell is changed without changing PCC, and/or if PSCell is changed without changing a frequency of PSCell or if
both PCell and PSCell are change by swapping the PCC with the frequency of PSCell while the UE is performing
SSTD measurements, then the UE shall also meet the SSTD measurement and accuracy requirements corresponding to
the new PCell and/or PSCell. However in this case the UE shall restart the SSTD measurement. In this case the total
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 316 ETSI TS 136 133 V14.3.0 (2017-04)
physical layer measurement period of the SSTD measurement shall not exceed Tmeasure_SSTD2 as defined in the following
expression:
Tmeasure_SSTD2 = (N+M+1)*(Tmeasure_SSTD1) + N*TPCell_change_DC + M*TPSCell_change_DC
Where:
N is the number of times the PCell is changed over the measurement period (Tmeasure_SSTD2),
M is the number of times the PSCell is changed over the measurement period (Tmeasure_SSTD2),
TPCell_change_DC is the time necessary to change the PCell; it can be up to 25 ms,
TPSCell_change_DC is the time necessary to change the PSCell; it can be up to 25 ms.
The measurement accuracy for the SSTD measurement when DRX is used as well as when no DRX is used shall be as
specified in the sub-clause 9.1.20.
8.8.7.3 SSTD Measurement Reporting Delay
This requirement assumes that the measurement report is not delayed by other RRC signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report. When the UE is configured to perform SRS carrier based
switching, an additional delay can be expected.
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in sub-
clause 9.1.20.
8.8.8 Intra-frequency measurements requirements on SCell
SCell intra-frequency measurements shall meet all applicable requirements in clause 8.3.3. In case where the SCell
belongs to MCG, the term “common DRX” in clause 8.3.3 shall be deemed to be replaced with “MCG DRX”. In case
where the SCell belongs to SCG, the term “common DRX” and PCell in clause 8.3.3 shall be replaced with “SCG
DRX” and PSCell, respectively.
8.9 MBSFN Measurements
8.9.1 Introduction
The requirements specified in Section 8.9 apply for MBSFN measurements (MBSFN RSRP, MBSFN RSRQ, and MCH
BLER defined in [4]), which are performed in RRC_CONNECTED and logged for MDT by UEs which are MBMS-
capable and also indicate their MBSFN measurement logging capability [2].
UE shall measure MBSFN RSRP, MBSFN RSRQ and MCH BLER only in subframes and on carriers where UE is
decoding PMCH. The requirements are specified for any carrier where PMCH is received by UE. The requirements
specified in this section apply for any carrier frequency with configured MBSFN subframes with PMCH, which may be
the same as or different from any serving unicast carrier.
The UE receiving PMCH on any non-serving carrier and performing MBSFN measurements shall not cause
interruptions on any serving carrier in unicast subframes and in the subframes with non-MBSFN multicast
transmissions such as system information.
The requirements in section 8.9 shall also appy, when the UE is configured to perform SRS carrier based switching.
8.9.2 MBSFN RSRP Measurements
The UE physical layer shall be capable of performing the MBSFN RSRP measurement [4] within the MBSFN RSRP
measurement period and report the measurement, while meeting the MBSFN RSRP measurement accuracy
requirements specified in section 9.8.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 317 ETSI TS 136 133 V14.3.0 (2017-04)
The MBSFN RSRP measurement period is defined as the maximum between 640ms and the period during which the
UE decodes [5, Section 10] 5 subframes containing PMCH transmissions.
The MBSFN RSRP measurement period is the same for UE using any DRX cycle, any eDRX_CONN cycle, or no
DRX.
8.9.3 MBSFN RSRQ Measurements
The UE physical layer shall be capable of performing the MBSFN RSRQ measurement [4] within the MBSFN RSRP
measurement period and report the measurement, while meeting the MBSFN RSRQ measurement accuracy
requirements specified in section 9.8.3.
The MBSFN RSRQ measurement period is defined as the maximum between 640ms and the period during which the
UE decodes [5, Section 10] 5 subframes containing PMCH transmissions.
The MBSFN RSRQ measurement period is the same for UE using any DRX cycle, any eDRX_CONN cycle, and no
DRX.
8.9.4 MCH BLER Measurements
The UE physical layer shall be capable of performing and reporting the MCH BLER measurement [4] to higher layers
within the MCH BLER measurement period. The MCH BLER measurement reporting is according to section 9.8.4.
The MCH BLER measurement period is equal to the MBSFN logging interval configured by higher layers [2].
8.10 Proximity-based Services
8.10.1 Introduction
This section contains the requirements for the UE capable of ProSe Direct Communication and/or ProSe Direct
Discovery in RRC_CONNECTED state.
8.10.2 Requirements
When a UE in RRC_CONNECTED state is performing transmissions and/or reception for ProSe Direct Discovery
and/or ProSe Direct Communication, the UE shall meet all the requirements specified in Section 8.
Note: The UE may need to interrupt ProSe operation in order to meet the measurement requirements of Section
8.
8.10.2.1 Initiation/Cease of SLSS transmissions with ProSe Direct Discovery
The requirements in this subclause are applicable to a UE capable of ProSe Direct Discovery and SLSS transmission
and reception.
The requirements apply when the conditions for SLSS transmissions specified in [2] are met; networkControlledSyncTx
is not configured; and syncTxThreshIC is included in SystemInformationBlockType19. The UE shall be capable of
measuring the RSRP of the cell used to transmit Prose Direct Discovery announcements and evaluate to initiate/cease
SLSS transmissions within Tevaluate,SLSS where,
- Tevaluate,SLSS = 0.4 seconds when UE is not configured with DRX, or,
- Tevaluate,SLSS = as specified in Table 8.10.2.1-1 when UE is configured with DRX.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 318 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.10.2.1-1: Tevaluate,SLSS with ProSe Direct Discovery
DRX cycle length [s] Tevaluate,SLSS
[s] (number of DRX cycles)
≤0.04 0.4 (Note 1)
0.04<DRX-cycle≤2.56 Note 2 (6)
Note1: Number of DRX cycles depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycles in use
If higher layer filtering is configured, an additional delay in evaluation to initiate/cease SLSS transmissions can be
expected.
For the cell used to transmit ProSe Direct Discovery announcements:
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 and RSRQ related side conditions given in
Clause 9.1.5.1 for a corresponding Band are fulfilled,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band are fulfilled.
8.10.2.2 Initiation/Cease of SLSS transmissions with ProSe Direct Communication
The requirements in this subclause are applicable to a UE capable of ProSe Direct Communication.
The requirements apply when the conditions for SLSS transmissions specified in [2] are met; networkControlledSyncTx
is not configured; and syncTxThreshIC is included in SystemInformationBlockType18. The UE shall be capable of
measuring the RSRP of the cell used to transmit Prose Direct Communication to evaluate to initiate/cease SLSS
transmissions within Tevaluate,SLSS
where,
- Tevaluate,SLSS = 0.4 seconds when UE is not configured with DRX.
- Tevaluate,SLSS = as specified in Table 8.10.2.2-1 when UE is configured with DRX.
Table 8.10.2.2-1: Tevaluate,SLSS with ProSe Direct Communication
DRX cycle length [s] Tevaluate,SLSS
[s] (number of DRX cycles)
≤0.04 0.4 (Note 1)
0.04<DRX-cycle≤2.56 Note 2 (6)
Note1: Number of DRX cycles depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycles in use
If higher layer filtering is configured, an additional delay in evaluation to initiate/cease SLSS transmissions can be
expected.
For the cell used to transmit ProSe Direct Communication:
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 and RSRQ related side conditions given in
Clause 9.1.5.1 for a corresponding Band are fulfilled,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 319 ETSI TS 136 133 V14.3.0 (2017-04)
8.11 Discovery Signal Measurements under Operation with
Frame Structure 3
8.11.1 Introduction
This section contains requirements on the UE for measurement reporting in RRC_CONNECTED state when discovery
signal [16] is configured. The requirements are specified for E-UTRA CRS based discovery signal measurements and
CSI-RS based discovery signal measurements.
The requirements in Section 8.11.2 shall apply for CRS based discovery signal measurements comprising RSRP and
RSRQ measurements [4]. The requirements in Section 8.11.3 shall apply for CSI-RS based discovery signal
measurements comprising CSI-RSRP measurements [4]. The requirements in Section 8.11.4 shall apply for UE RSSI
measurements [4]. The requirements in Section 8.11.5 shall apply for UE channel occupancy measurements [2].
The measurement quantities are defined in [4], the measurement model is defined in [22] and measurement accuracy
requirements are specified in Section 9. Control of measurement reporting is specified in TS 36.331 [2].
The requirements in this Section shall apply for carrier with E-UTRA operation following the frame structure type 3
[16].
The requirements in Section 9 are applicable for a UE performing measurements according to Section 8.11.
8.11.2 CRS based discovery signal measurements
8.11.2.1 E-UTRAN intra-frequency measurements
NOTE: The requirements in this section are applicable only for measurements on SCC following the frame structure
type 3 [16].
The UE shall be able to identify new intra-frequency FS3 cells and perform measurements of identified intra-frequency
cells without an explicit intra-frequency neighbour cell list containing physical layer cell identities. During the
RRC_CONNECTED state the UE shall continuously measure identified intra-frequency cells and additionally search
for and identify new intra-frequency cells.
8.11.2.1.1 Requirements
8.11.2.1.1.1 Requirements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FS3 intra-frequency cell within the cell
identification time Tidentify_intra_ FS3, where the identification time of a cell shall include detection of the cell and
additionally performing a single measurement with measurement period of Tmeasure_intra_FS3_CRS, where:
Tidentify_intra_FS3 is the intra-frequency cell identification period as specified in Table 8.11.2.1.1.1-1,
Tmeasure_intra_FS3_CRS is the intra-frequency period for measurements as shown in Table 8.11.2.1.1.1-2,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
L is the number of configured discovery signal occasions which are not available during Tidentify_intra_FS3 for cell
identification at the UE due to the absence of the necessary radio signals from the cell or due to the corresponding
downlink subframe being configured as an uplink subframe,
M is the number of configured discovery signal occasions which are not available during Tmeasure_intra_FS3_CRS for the
measurements at the UE due to the absence of the necessary radio signals from the cell or due to the corresponding
downlink subframe being configured as an uplink subframe.
The requirements in this section apply, provided that L and M are such that: the intra-frequency cell identification
period Tidentify_intra_FS3 does not exceed 72*TDMTC_periodicity, and the intra-frequency period Tmeasure_intra_FS3_CRS for
measurements does not exceed 60*TDMTC_periodicity.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 320 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.11.2.1.1.1-1: Intra-frequency cell identification requirement under operation with frame
structure 3
SCH Ês/Iot CRS CRS Ês/Iot Tidentify_intra_FS3 [ms]
measurement
bandwidth [RB]
Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (6+L) * k1*k2* TDMTC_periodicity
-6 ≤ SCH Ês/Iot < 0 <25 (24+L) * k1*k2* TDMTC_periodicity
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (2+L) * k1*k2* TDMTC_periodicity
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (8+L) * k1*k2* TDMTC_periodicity
NOTE 1 : Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
≥
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
NOTE 3: k1=2 when the measurement gaps configured for inter-frequency measurements in DMTC
occasions on a carrier with frame structure 3 overlap with some but not all DMTC occasions
of the measured cell; otherwise, k1=1, e.g., when measurement gaps configured for inter-
frequency measurements on a carrier with frame structure 3 do not overlap with DMTC
occasions of the measured cell or when the UE does not require the measurement gaps for
the inter-frequency measurements. The requirements apply, provided that the inter-
frequency measurement gap pattern does not overlap with all DMTC occasions of the
measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping
⎜ 2
⎝ ⎢ ⎥⎠
with the inter-frequency measurement gaps overlap with DMTC occasions of NFS3_SCC
(NFS3_SCC>0) SCells on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC is 0.
A cell shall be considered detectable when the following conditions are met during the discovery signal occasions
which are available during Tidentify_intra_FS3:
- RSRP related side conditions given in Section 9.1.18.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Section 9.1.18.3 are fulfilled for a corresponding Band,
- SCH_RP is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is according to Table
8.11.2.1.1.1-1.
If higher layer filtering is used, an additional cell identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is Tmeasure_intra_FS3_CRS as
shown in Table 8.11.2.1.1.1-2, when no DRX is in use. The UE shall be capable of performing RSRP and RSRQ
measurements for 3 identified intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers within the measurement period of Tmeasure_intra_FS3_CRS.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 321 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.11.2.1.1.1-2: Intra-frequency measurement requirements under operation with frame structure
3
SCH Ês/Iot CRS measurement CRS Ês/Iot Tmeasure_intra_FS3_CRS [ms]
bandwidth [RB] Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (5+M) * k1*k2* TDMTC_periodicity
-6 ≤ SCH Ês/Iot < 0 <25 (20+M) * k1*k2* TDMTC_periodicity
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (1+M) * k1*k2* TDMTC_periodicity
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M) * k1*k2* TDMTC_periodicity
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
≥
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
NOTE 3: k1=2 when the measurement gaps configured for inter-frequency measurements in DMTC occasions on a
carrier with frame structure 3 overlap with some but not all DMTC occasions of the measured cell; otherwise,
k1=1, e.g., when measurement gaps configured for inter-frequency measurements on a carrier with frame
structure 3 do not overlap with DMTC occasions of the measured cell or when the UE does not require the
measurement gaps for the inter-frequency measurements. The requirements apply, provided that the inter-
frequency measurement gap pattern does not overlap with all DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping with the inter-
⎜ 2
⎝ ⎢ ⎥⎠
frequency measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0) SCells on other FS3
carriers; otherwise, k2=1, e.g., when NFS3_SCC is 0.
The RSRP measurement accuracy for all measured cells shall be as specified in Section 9.1.18.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in Section 9.1.18.3.
8.11.2.1.1.1.1 Measurement Reporting Requirements
8.11.2.1.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in Sections 9.1.18.2 and 9.1.18.3, respectively.
8.11.2.1.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in Sections 9.1.18.2 and 9.1.18.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in Section
8.11.2.1.1.1.1.3.
8.11.2.1.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in Sections 9.1.18.2 and 9.1.18.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for UE to send
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_FS3
defined in Section 8.11.2.1.1.1. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_FS3 defined in Section 8.11.2.1.1.1 becomes
undetectable for a period ≤ 8 seconds and then the cell becomes detectable again and triggers an event, the event
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 322 ETSI TS 136 133 V14.3.0 (2017-04)
triggered measurement reporting delay shall be less than Tidentify_intra_FS3_CRS provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or LBT is performed by the UE on the carrier used for the measurement reporting, an additional delay can be
expected.
8.11.2.1.1.2 Requirements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FS3 intra-frequency cell within the cell
identification time Tidentify_intra_FS3_DRX, where the cell identification time of a cell shall include detection of the cell and
additionally performing a single measurement with measurement period of Tmeasure_intra_FS3_CRS_DRX, where:.
Tidentify_intra_FS3_DRX is the intra-frequency period for cell identification as shown in Table 8.11.2.1.1.2-1,
Tmeasure_intra_FS3_CRS_DRX is the intra-frequency period for measurements as shown in Table 8.11.2.1.1.2-2,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
L is the number of configured discovery signal occasions during ON DURATION and which are not available
during Tidentify_intra_FS3_DRX for cell identification at the UE due to the absence of the necessary radio signals from the
cell or due to the corresponding downlink subframe being configured as an uplink subframe,
M is the number of configured discovery signal occasions during ON DURATION and which are not available
during Tmeasure_intra_FS3_CRS_DRX for the measurements at the UE due to the absence of the necessary radio signals from
the cell or due to the corresponding downlink subframe being configured as an uplink subframe.
The requirements in this section apply, provided that L and M are such that: the intra-frequency cell identification
period Tidentify_intra_FS3_DRX does not exceed 72*Max{TDMTC_periodicity, DRX cycle length}, and the intra-frequency period
Tmeasure_intra_FS3_CRS_DRX for measurements does not exceed 60*Max{TDMTC_periodicity, DRX cycle length}.
Table 8.11.2.1.1.2-1: Intra-frequency cell identification requirements under operation with frame
structure 3
SCH Ês/Iot CRS CRS Ês/Iot Tidentify_intra_FS3_DRX [ms]
measurement
bandwidth [RB]
Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (6+L)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
-6 ≤ SCH Ês/Iot < 0 <25 (24+L)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (2+M)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (8+M)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
≥
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
NOTE 3: k1=2 when the measurement gaps configured for inter-frequency in DMTC occasions
measurements on a carrier with frame structure 3 overlap with some but not all DMTC
occasions of the measured cell during ON DURATION; otherwise, k1=1, e.g., when
measurement gaps configured for inter-frequency measurements on a carrier with frame
structure 3 do not overlap with DMTC occasions of the measured cell during ON DURATION
or when the UE does not require the measurement gaps for the inter-frequency
measurements. The requirements apply, provided that the inter-frequency measurement gap
pattern does not overlap with all DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping
⎜ 2
⎝ ⎢ ⎥⎠
with the inter-frequency measurement gaps measurement gaps overlap with DMTC
occasions of NFS3_SCC (NFS3_SCC>0) SCells during ON DURATION on other FS3 carriers;
otherwise, k2=1, e.g., when NFS3_SCC is 0.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 323 ETSI TS 136 133 V14.3.0 (2017-04)
A cell shall be considered detectable when the following conditions are met during the discovery signal occasions
which are available during Tidentify_intra_FS3_DRX:
- RSRP related side conditions given in Section 9.1.18.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Section 9.1.18.3 are fulfilled for a corresponding Band,
- SCH_RP is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is according to Table
8.11.2.1.1.2-1.
If higher layer filtering is used, an additional cell identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is Tmeasure_ intra_FS3_CRS_DRX as
shown in Table 8.11.2.1.1.2-2, when DRX is in use. The UE shall be capable of p performing RSRP and RSRQ
measurements for 3 identified intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers within the measurement period of Tmeasure_intra_FS3_CRS_DRX.
Table 8.11.2.1.1.2-2: Intra-frequency measurement requirements under operation with frame structure
3
SCH Ês/Iot CRS CRS Ês/Iot Tmeasure_intra_FS3_CRS_DRX [ms]
measurement
bandwidth [RB]
Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (5+M)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
-6 ≤ SCH Ês/Iot < 0 <25 (20+M)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (1+M)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M)*
k1*k2*Max{TDMTC_periodicity, DRX
cycle length}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
≥
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
NOTE 3: k1=2 when the measurement gaps configured for inter-frequency in DMTC occasions
measurements on a carrier with frame structure 3 overlap with some but not all DMTC
occasions of the measured cell during ON DURATION; otherwise, k1=1, e.g., when
measurement gaps configured for inter-frequency measurements on a carrier with frame
structure 3 do not overlap with DMTC occasions of the measured cell during ON DURATION
or when the UE does not require the measurement gaps for the inter-frequency
measurements. The requirements apply, provided that the inter-frequency measurement gap
pattern does not overlap with all DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping
⎜ 2
⎝ ⎢ ⎥⎠
with the inter-frequency measurement gaps measurement gaps overlap with DMTC
occasions of NFS3_SCC (NFS3_SCC>0) SCells during ON DURATION on other FS3 carriers;
otherwise, k2=1, e.g., when NFS3_SCC is 0.
The RSRP measurement accuracy for all measured cells shall be as specified in Section 9.1.18.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in Section 9.1.18.3.
8.11.2.1.1.2.1 Measurement Reporting Requirements
8.11.2.1.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in Sections 9.1.18.2 and 9.1.18.3, respectively.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 324 ETSI TS 136 133 V14.3.0 (2017-04)
8.11.2.1.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in Sections 9.1.18.2 and 9.1.18.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.11.2.1.1.2.1.3.
8.11.2.1.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in Sections 9.1.18.2 and 9.1.18.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for UE to send
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_FS3_DRX
defined in Section 8.11.2.1.1.2. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_FS3_DRX defined in Section 8.11.2.1.1.2
becomes undetectable for a period ≤ 8 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tidentify_intra_FS3_CRS_DRX provided the timing to that cell
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured or LBT is performed by the UE on the carrier used for the measurement reporting, an additional
delay can be expected.
8.11.2.2 E-UTRAN inter-frequency measurements
The UE shall be able to identify new inter-frequency cells and perform RSRP and RSRQ measurements of identified
inter-frequency cells if carrier frequency information is provided by the PCell, even if no explicit neighbour list with
physical layer cell identities is provided. The discovery signal occasion and the measurement gap should be aligned,
provided that also the following additional conditions are fulfilled:
Entire discovery signal occasion should be contained in the measurement gap.
The subframe contained discovery signal for the measurement is not overlapped with the first 0.5 ms period and the
last 0.5 ms period in every gap.
8.11.2.2.1 E-UTRAN FDD-FS3 inter-frequency measurements
8.11.2.2.1.1 E-UTRAN FDD – FS3 inter-frequency measurements when no DRX is used
When measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new detectable FS3 inter-frequency cell within the cell identification time
Tidentify_inter_FS3, which shall include detection of the cell and additionally performing a single measurement within the
measurement period of Tmeasure_inter_FS3_CRS when no DRX is used, where:
Tidentify_inter_FS3 is the inter-frequency period for cell identification as shown in Table 8.11.2.2.1.1-1,
Tmeasure_inter_FS3_CRS is the inter-frequency period for measurements as shown in Table 8.11.2.2.1.1-2,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
Nfreq is defined in Section 8.1.2.1.1,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 325 ETSI TS 136 133 V14.3.0 (2017-04)
N is the number of carriers operating under FS3 and which are subject to the channel assessment prior to
transmissions,
L is the number of configured discovery signal occasions which are not available during the time for cell
identification at the UE during measurement gaps due to the absence of the necessary radio signals from the
measured cell,
M is the number of configured discovery signal occasions which are not available during Tmeasure_inter_FS3_CRS for the
measurements at the UE during measurement gaps due to the absence of the necessary radio signals from the
measured cell.
If higher layer filtering is used, an additional cell identification delay can be expected.
The requirements in this section apply, provided that L and M are such that: the inter-frequency cell identification
period Tidentify_inter_FS3 does not exceed 75 *Nfreq*Max{TDMTC_periodicity, MGRP}, and the inter-frequency period
Tmeasure_inter_FS3_CRS for measurements does not exceed 60* Nfreq *Max{TDMTC_periodicity, MGRP}.
Table 8.11.2.2.1.1-1: Inter-frequency cell identification requirements under operation with frame
structure 3
SCH Ês/Iot CRS measurement CRS Ês/Iot Tidentify_inter_FS3 [ms]
bandwidth Note2
[RB]
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (7*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP}
-6 ≤ SCH Ês/Iot < 0 <25 (25*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (3*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (9*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
Table 8.11.2.2.1.1-2: Inter-frequency measurement requirements under operation with frame structure
3
SCH Ês/Iot CRS measurement CRS Ês/Iot Tmeasure_inter_FS3_CRS [ms]
bandwidth Note2
[RB]
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (5*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP}
-6 ≤ SCH Ês/Iot < 0 <25 (20*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (1*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
A cell shall be considered detectable when the following conditions are met during the discovery signal occasions
which are available during Tidentify_inter_FS3:
- RSRP related side conditions given in Section 9.1.18.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Section 9.1.18.3 are fulfilled for a corresponding Band,
- SCH_RP|dBm is according to Annex B.2.13.1 for a corresponding Band,
- SCH Ês/Iot is according to Table 8.11.2.2.1.1-1.
When measurement gaps are scheduled for FS3 inter-frequency measurements or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP and RSRQ
measurements to higher layers with measurement accuracy as specified in Sections 9.1.18.2 and 9.1.18.3, respectively,
with measurement period given by table 8.11.2.2.1.1-2.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 3 identified inter-frequency cells per
FS3 inter-frequency for up to 3 FS3 inter-frequencies and the UE physical layer shall be capable of reporting RSRP and
RSRQ measurements to higher layers with the measurement period defined in table 8.11.2.2.1.1-2 when no DRX is in
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 326 ETSI TS 136 133 V14.3.0 (2017-04)
use, either measurement gaps are scheduled or the UE supports capability of conducting such measurements without
gaps.
The RSRP measurement accuracy for all measured cells shall be as specified in Section 9.1.18.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in Section 9.1.18.3.
8.11.2.2.1.1.1 Measurement Reporting Requirements
8.11.2.2.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.18.2 and 9.1.18.3, respectively.
8.11.2.2.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.18.2, and 9.1.18.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.11.2.2.1.1.1.3.
8.11.2.2.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.18.2 and 9.1.18.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report or by the LBT procedure performed by the UE in order to determine that the
channel is clear for performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_FS3
defined in Section 8.11.2.2.1.1. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_FS3 defined in Section 8.11.2.2.1.1 and then
triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less than
Tmeasure_inter_FS3_CRS provided the timing to that cell has not changed more than ± 50 Ts while measurement gap has not
been available and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is configured or
LBT is performed by the UE on the carrier used for the measurement reporting, an additional delay can be expected.
8.11.2.2.1.2 E-UTRAN FDD – FS3 inter-frequency measurements when DRX is used
When measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new detectavle FS3 inter-frequency cell within the cell identification time
Tidentify_inter_FS3_DRX, which shall include detection of the cell and additionally performing a single measurement within
the measurement period of Tmeasure_inter_FS3_CRS_DRX when DRX is used, where:
Tidentify_inter_FS3_DRX. is the inter-frequency period for measurements as shown in Table 8.11.2.2.1.2-1,
Tmeasure_inter_FS3_CRS_DRX is the inter-frequency period for measurements as shown in Table 8.11.2.2.1.2-2,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
Nfreq is defined in Section 8.1.2.1.1,
N is the number of carriers operating under FS3 and which are subject to the channel assessment prior to
transmissions,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 327 ETSI TS 136 133 V14.3.0 (2017-04)
L is the number of configured discovery signal occasions which are not available during the time for cell
identification at the UE during measurement gaps due to the absence of the necessary radio signals from the
measured cell,
M is the number of configured discovery signal occasions which are not available during Tmeasure_inter_FS3_CRS_DRX for
the measurements at the UE during measurement gaps due to the absence of the necessary radio signals from the
measured cell.
The requirements in this section apply, provided that L and M are such that: the inter-frequency cell identification
period Tidentify_inter_FS3_DRX does not exceed 75 *Nfreq* Max{TDMTC_periodicity, MGRP, DRX cycle length}, and the inter-
frequency period Tmeasure_inter_FS3_CRS_DRX for measurements does not exceed 60* Nfreq * Max{TDMTC_periodicity, MGRP,
DRX cycle length}.
If higher layer filtering is used, an additional cell identification delay can be expected.
Table 8.11.2.2.1.2-1: Inter-frequency cell identification requirements under operation with frame
structure 3
SCH Ês/Iot CRS measurement CRS Ês/Iot Tidentify_inter_FS3_DRX [ms]
bandwidth Note2
[RB]
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot(7*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP, DRX
cycle length}
-6 ≤ SCH Ês/Iot < 0 <25 (25*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (3*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP, DRX
cycle length}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (9*Nfreq +L*N)*Max{TDMTC_periodicity, MGRP, DRX
cycle length}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
Table 8.11.2.2.1.2-2: Inter-frequency measurement requirements under operation with frame structure
3
SCH Ês/Iot CRS CRS Ês/Iot Tmeasure_inter_FS3_CRS_DRX [ms]
measurement
bandwidth Note2
[RB]
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (5*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 <25 (20*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (1*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
A cell shall be considered detectable when the following conditions are met during the discovery signal occasions
which are available during Tidentify_inter_FS3_DRX:
- RSRP related side conditions given in Section 9.1.18.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Section 9.1.18.3 are fulfilled for a corresponding Band,
- SCH_RP|dBm is according to Annex B.2.13.1 for a corresponding Band,
- SCH Ês/Iot is according to Table 8.11.2.2.1.2-1.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 3 identified inter-frequency cells per
FS3 inter-frequency for up to 3 FS3 inter-frequencies and the UE physical layer shall be capable of reporting RSRP and
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 328 ETSI TS 136 133 V14.3.0 (2017-04)
RSRQ measurements to higher layers with the measurement period defined in table 8.11.2.2.1.2-2 when DRX is in use,
either measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps.
The RSRP measurement accuracy for all measured cells shall be as specified in Section 9.1.18.2, and the RSRQ
measurement accuracy for all measured cells shall be as specified in Section 9.1.18.3.
8.11.2.2.1.2.1 Measurement Reporting Requirements
8.11.2.2.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.18.2 and 9.1.18.3, respectively.
8.11.2.2.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurements contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.18.2 and 9.1.18.3, respectively.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.11.2.2.1.2.1.3.
8.11.2.2.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.18.2, and 9.1.18.3, respectively.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report or by the LBT procedure performed by the UE in order to determine that the
channel is clear for performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_FS3_DRX
defined in Section 8.11.2.2.1.2. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_FS3_DRX defined in Section 8.11.2.2.1.2
becomes undetectable for a period ≤ 8 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tidentify_inter_FS3_CRS_DRX provided the timing to that cell
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured or LBT is performed by the UE on the carrier used for the measurement reporting, an additional
delay can be expected.
8.11.2.2.2 E-UTRAN TDD – FS3 inter-frequency measurements
8.11.2.2.2.1 E-UTRAN TDD – FS3 inter-frequency measurements when no DRX is used
The requirements in this section for UE configured with TDD PCell and no DRX are the same as the requirements in
Section 8.11.2.2.1.1.
8.11.2.2.2.2 E-UTRAN TDD – FS3 inter-frequency measurements when DRX is used
The requirements in this section for UE configured with TDD PCell and DRX are the same as the requirements in
Section 8.11.2.2.1.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 329 ETSI TS 136 133 V14.3.0 (2017-04)
8.11.3 CSI-RS based discovery signal measurements
8.11.3.1 E-UTRAN intra-frequency measurements
The UE shall be able to identify new intra-frequency FS3 TPs and perform CSI-RSRP measurements of intra-frequency
TPs with an explicit intra-frequency TP list containing physical layer cell identities. During the RRC_CONNECTED
state the UE shall continuously measure identified intra-frequency TPs and additionally search for and identify new
intra-frequency TPs.
8.11.3.1.1 Requirements
8.11.3.1.1.1 Requirements when no DRX is used
When no DRX is in use the UE shall be able to identify a new detectable FS3 intra-frequency TP within the
identification period Tidentify_intra_TP_FS3, where identification of a TP shall include cell identification and additionally
performing a single measurement on the TP.
Tidentify_intra_TP_FS3 = Tidentify_intra_FS3 + Tmeasure_intra_FS3_CSI-RS,
where
Tidentify_intra_FS3 is the intra-frequency period for cell identification in Section 8.11.2.1.1.1,
Tmeasure_ intra_FS3_CSI-RS is the intra-frequency period for TP measurement as shown in Table 8.11.3.1.1.1-1,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
M is the number of configured discovery signal occasions which are not available during Tmeasure_ intra_FS3_CSI-RS for
the measurements at the UE due to the absence of the necessary radio signals from the TP or due to the
corresponding downlink subframe being configured as an uplink subframe.
The requirements in this section apply, provided that M is such that: the intra-frequency period for TP measurement
Tmeasure_ intra_FS3_CSI-RS does not exceed 60*TDMTC_periodicity.
During Tidentify_intra_TP_FS3 over multiple discovery signal occasions, the UE may assume the following:
- in all the discovery signal occasions, which are available at the UE, the corresponding necessary cell-specific
discovery signals are always available from the same set of TPs in the measured cell, and
- in all the discovery signal occasions, which are not available at the UE, the corresponding necessary cell-specific
discovery signals are not available from any TP within the same measured cell.
A TP shall be considered detectable when the following conditions are met during the discovery signal occasions which
are available during Tidentify_intra_TP_FS3:
- CSI-RSRP related side conditions given in Section 9.1.18.4 are fulfilled for a corresponding Band,
- SCH_RP is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is according to Section
8.11.2.1.1.1.
Identification of a TP shall include identification of the cell and additionally performing a single measurement on the
TP within the measurement period of Tmeasure_ intra_FS3_CSI-RS when no DRX is used. If higher layer filtering is used, an
additional TP identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra-frequency measurements is Tmeasure_intra_FS3_CSI-RS as
shown in table 8.11.3.1.1.1-1, when no DRX is in use. The UE shall be capable of performing CSI-RSRP measurements
for 3 identified intra-frequency TPs, and the UE physical layer shall be capable of reporting measurements to higher
layers with the measurement period of Tmeasure_intra_FS3_CSI-RS
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 330 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.11.3.1.1.1-1: Intra-frequency TP measurement requirements under operation with frame
structure 3
SCH Ês/Iot CRS measurement CSI-RS Ês/Iot Tmeasure_intra_FS3_CSI-RS [ms]
bandwidth [RB] Note2
0 ≤ SCH Ês/Iot <25 0 ≤ CSI-RS Ês/Iot (5+M) *k1*k2* TDMTC_periodicity
-6 ≤ SCH Ês/Iot < 0 <25 (20+M) *k1*k2* TDMTC_periodicity
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CSI-RS Ês/Iot (1+M) *k1*k2* TDMTC_periodicity
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M) *k1*k2* TDMTC_periodicity
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
≥
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
NOTE 3: k1=2 when the measurement gaps configured for inter-frequency measurements in DMTC occasions on a
carrier with frame structure 3 overlap with some but not all DMTC occasions of the measured TP; otherwise,
k1=1, e.g., when measurement gaps configured for inter-frequency measurements on a carrier with frame
structure 3 do not overlap with DMTC occasions of the measured TP or when the UE does not require the
measurement gaps for the inter-frequency measurements. The requirements apply, provided that the inter-
frequency measurement gap pattern does not overlap with all DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured TP not overlapping with the inter-
⎜ 2
⎝ ⎢ ⎥⎠
frequency measurement gaps measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0)
SCells on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC is 0.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in Section 9.1.18.4.
8.11.3.1.1.1.1 Measurement Reporting Requirements
8.11.3.1.1.1.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in Section 9.1.18.4.
8.11.3.1.1.1.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in Section 9.1.18.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.11.3.1.1.1.1.3.
8.11.3.1.1.1.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
Section 9.1.18.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for UE to send
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_TP_FS3
defined in Section 8.11.3.1.1.1. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_intra_TP_FS3 defined in Section 8.11.3.1.1.1 becomes
undetectable for a period ≤ 8 seconds and then the TP becomes detectable again and triggers an event, the event
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 331 ETSI TS 136 133 V14.3.0 (2017-04)
triggered measurement reporting delay shall be less than Tidentify_intra_FS3_CSI-RS provided the timing to that TP has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or LBT is performed by the UE on the carrier used for the measurement reporting, an additional delay can be
expected.
8.11.3.1.1.2 Requirements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FS3 intra-frequency TP within the identification
period Tidentify_intra_TP_FS3_DRX , where identification of a TP shall include cell identification and additionally performing a
single measurement on the TP.
Tidentify_intra_TP_FS3_DRX = Tidentify_intra_FS3_DRX + Tmeasure_ intra_FS3_CSI-RS_DRX,
where:
Tidentify_intra_FS3_DRX is the intra-frequency period for cell identification in Section 8.11.2.1.1.2.
Tmeasure_ intra_FS3_CSI-RS_DRX is the intra-frequency period for TP measurement as shown in Table 8.11.3.1.1.2-1, where
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
M is the number of configured discovery signal occasions during ON DURATION and which are not available
duting Tmeasure_intra_FS3_CSI-RS_DRX for the measurements at the UE due to the absence of the necessary radio signals
from the TP or due to the corresponding downlink subframe being configured as an uplink subframe.
The requirements in this section apply, provided that M is such that: the intra-frequency period for TP measurement
Tmeasure_ intra_FS3_CSI-RS_DRX does not exceed 60*Max{ TDMTC_periodicity, DRX cycle length}.
During Tidentify_intra_TP_FS3_DRX over multiple discovery signal occasions, the UE may assume the following:
- in all the discovery signal occasions, which are available at the UE, the corresponding necessary cell-specific
discovery signals are always available from the same set of TPs in the measured cell, and
- in all the discovery signal occasions, which are not available at the UE, the corresponding necessary cell-specific
discovery signals are not available from any TP within the same measured cell.
A TP shall be considered detectable when the following conditions are met during the discovery signal occasions which
are available during Tidentify_intra_TP_FS3_DRX:
- CSI-RSRP related side conditions given in Section 9.1.18.4 are fulfilled for a corresponding Band,
- SCH_RP is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is according to Section
8.11.2.1.1.2.
Identification of a TP shall include identification of the cell and additionally performing a single measurement on the
TP within measurement period of Tmeasure_intra_FS3_CSI-RS_DRX when DRX is used. If higher layer filtering is used, an
additional TP identification delay can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_FS3_CSI-RS_DRX
as shown in Table 8.11.3.1.1.2-1, when DRX is in use. The UE shall be capable of performing CSI-RSRP
measurements for 3 identified intra-frequency TPs, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of Tmeasure_intra_FS3_CSI-RS_DRX.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 332 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.11.3.1.1.2-1: Intra-frequency TP measurement requirements under operation with frame
structure 3
SCH Ês/Iot CRS measurement CSI-RS Ês/Iot Tmeasure_intra_FS3_CSI-RS_DRX [ms]
bandwidth [RB] Note2
0 ≤ SCH Ês/Iot <25 0 ≤CSI-RS Ês/Iot (5+M) *k1*k2* Max{ TDMTC_periodicity,
DRX cycle length }
-6 ≤ SCH Ês/Iot < 0 <25 (20+M) *k1*k2* Max{ TDMTC_periodicity,
DRX cycle length }
0 ≤ SCH Ês/Iot ≥ 25 0 ≤CSI-RS Ês/Iot (1+M) *k1*k2* Max{ TDMTC_periodicity,
DRX cycle length }
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M) *k1*k2* Max{ TDMTC_periodicity,
DRX cycle length }
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
≥
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
NOTE 3: k1=2 when the measurement gaps configured for inter-frequency in DMTC occasions measurements on a
carrier with frame structure 3 overlap with some but not all DMTC occasions of the measured TP during ON
DURATION; otherwise, k1=1, e.g., when measurement gaps configured for inter-frequency measurements on
a carrier with frame structure 3 do not overlap with DMTC occasions of the measured TP during ON
DURATION or when the UE does not require the measurement gaps for the inter-frequency measurements.
The requirements apply, provided that the inter-frequency measurement gap pattern does not overlap with all
DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured TP not overlapping with the inter-
⎜ 2
⎝ ⎢ ⎥⎠
frequency measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0) SCells during ON
DURATION on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC=0.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in Section 9.1.18.4.
8.11.3.1.1.2.1 Measurement Reporting Requirements
8.11.3.1.1.2.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in Section 9.1.18.4.
8.11.3.1.1.2.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in Section 9.1.18.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.11.3.1.1.2.1.3.
8.11.3.1.1.2.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
Section 9.1.18.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for UE to send
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 333 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_intra_TP_FS3_DRX
defined in Section 8.11.3.1.1.2. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_intra_TP_FS3_DRX defined in Section 8.11.3.1.1.2
becomes undetectable for a period ≤ 8 seconds and then the TP becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tidentify_intra_FS3_CSI-RS_DRX provided the timing to that TP
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured or LBT is performed by the UE on the carrier used for the measurement reporting, an additional
delay can be expected.
8.11.3.2 E-UTRAN inter-frequency measurements
The UE shall be able to identify new inter-frequency TPs and perform CSI-RSRP measurements of the idenitified inter-
frequency TPs with an explicit inter-frequency TP list containing physical layer cell identities. The discovery signal
occasion and the measurement gap should be aligned, provided that also the following additional conditions are
fulfilled:
Entire discovery signal occasion should be contained in the measurement gap.
The subframe contained discovery signal for the measurement is not overlapped with the first 0.5 ms period and the
last 0.5 ms period in every gap.
8.11.3.2.1 E-UTRAN FDD – FS3 inter-frequency measurements
8.11.3.2.1.1 E-UTRAN FDD – FS3 inter-frequency measurements when no DRX is used
When measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps,
the UE shall be able to identify a new detectable FS3 inter-frequency TP within the TP identification time
Tidentify_inter_TP_FS3 according to the following expression:
Tidentify_inter_TP_FS3 = Tidentify_inter_FS3 + Tmeasure_inter_FS3_CSI-RS,
where
Tidentify_inter_FS3 is the inter-frequency period for cell identification in Section 8.11.2.2.1.1,
Tmeasure_inter_FS3_CSI-RS is the inter-frequency period for TP measurement as shown in Table 8.11.3.2.1.1-1,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
Nfreq is defined in section 8.1.2.1.1,
N is the number of carriers operating under FS3 and which are subject to the channel assessment prior to
transmissions,
M is the number of configured discovery signal occasions which are not available during Tmeasure_inter_FS3_CSI-RS for the
measurements at the UE during measurement gaps due to the absence of the necessary radio signals from the
measured TP.
The requirements in this section apply, provided that M is such that: the inter-frequency period Tmeasure_inter_FS3_CSI-RS for
TP measurements does not exceed 60* Nfreq* Max{TDMTC_periodicity, MGRP }.
During Tidentify_inter_TP_FS3 over multiple discovery signal occasions, the UE may assume the following:
- in all the discovery signal occasions, which are available at the UE, the corresponding necessary cell-specific
discovery signals are always available from the same set of TPs in the measured cell, and
- in all the discovery signal occasions, which are not available at the UE, the corresponding necessary cell-specific
discovery signals are not available from any TP within the same measured cell.
A TP shall be considered detectable when the following conditions are met during the discovery signal occasions which
are available during Tidentify_inter_TP_FS3:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 334 ETSI TS 136 133 V14.3.0 (2017-04)
- CSI-RSRP related side conditions given in Section 9.1.18.4 are fulfilled for a corresponding Band,
- SCH_RP is according to Annex B.2.13.2 for a corresponding Band,
- SCH Ês/Iot is according to Table 8.11.2.2.1.1-1.
When measurement gaps are scheduled for FS3 inter-frequency measurements or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with measurement accuracy as specified in section 9.1.18.4, with measurement period
given by table 8.11.3.2.1.1-1.
The UE shall be capable of performing CSI-RSRP measurements of at least 3 identified inter-frequency TPs per FS3
inter-frequency for up to 3 FS3 inter-frequencies and the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with the measurement period defined in table 8.11.3.2.1.1-1 when no DRX is in use,
either measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps.
Table 8.11.3.2.1.1-1: Requirements to measure FS3 inter-frequency TP
SCH Ês/Iot CSI-RS CSI-RS Ês/Iot Tmeasure_inter_FS3_CSI-RS [ms]
measurement
bandwidth Note2
[RB]
0 ≤ SCH Ês/Iot <25 0 ≤ CSI-RS Ês/Iot (5*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP}
-6 ≤ SCH Ês/Iot < 0 <25 (20*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP }
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CSI-RS Ês/Iot (1*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in section 9.1.18.4.
8.11.3.2.1.1.1 Measurement Reporting Requirements
8.11.3.2.1.1.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in section 9.1.18.4.
8.11.3.2.1.1.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in section 9.1.18.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
section 8.11.3.2.1.1.1.3.
8.11.3.2.1.1.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
section 9.1.18.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report or by the LBT procedure performed by the UE in order to determine that the
channel is clear for performing uplink transmission.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 335 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_TP_FS3
defined in Section 8.11.3.2.1.1. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_inter_TP_FS3 defined in Section 8.11.3.2.1.1 becomes
undetectable for a period ≤ 8 seconds and then the TP becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tidentify_inter_FS3_CSI-RS provided the timing to that TP has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or LBT is performed by the UE on the carrier used for the measurement reporting, an additional delay can be
expected.
8.11.3.2.1.2 E-UTRAN FDD – FS3 inter-frequency measurements when DRX is used
When DRX is in use, either measurement gaps are scheduled or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable FS3 inter-frequency TP within
Tidentify_inter_TP_FS3_DRX according to the following expression:
Tidentify_inter_TP_FS3_DRX = Tidentify_inter_FS3_DRX + Tmeasure_inter_FS3_CSI-RS_DRX ,
where
Tidentify_inter_FS3_DRX is the inter-frequency period for cell identification in Section 8.11.2.2.1.2,
Tmeasure_inter_FS3_CSI-RS_DRX is the inter-frequency period for TP measurement as shown in Table 8.11.3.2.1.2-1,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
Nfreq is defined in section 8.1.2.1.1,
N is the number of carriers operating under FS3 and which are subject to the channel assessment prior to
transmissions,
M is the number of configured discovery signal occasions which are not available during Tmeasure_inter_FS3_CSI-RS_DRX
for the measurements at the UE during measurement gaps due to the absence of the necessary radio signals from
the measured cell.
The requirements in this section apply, provided that M is such that: the inter-frequency period Tmeasure_inter_FS3_CSI-RS_DRX
for TP measurements does not exceed 60* Nfreq * Max{TDMTC_periodicity, MGRP, DRX cycle length}.
During Tidentify_inter_TP_FS3_DRX over multiple discovery signal occasions, the UE may assume the following:
- in all the discovery signal occasions, which are available at the UE, the corresponding necessary cell-specific
discovery signals are always available from the same set of TPs in the measured cell, and
- in all the discovery signal occasions, which are not available at the UE, the corresponding necessary cell-specific
discovery signals are not available from any TP within the same measured cell.
A TP shall be considered detectable when the following conditions are met during the discovery signal occasions which
are available during Tidentify_inter_TP_FS3_DRX:
- CSI-RSRP related side conditions given in Sections 9.1.18.4 are fulfilled for a corresponding Band,
- SCH_RP is according to Annex B.2.13.2 for a corresponding Band,
- SCH Ês/Iot is according to Table 8.11.2.2.1.2-1.
When measurement gaps are scheduled for FS3 inter-frequency measurements or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with measurement accuracy as specified in section 9.1.18.4, with measurement period
given by table 8.11.3.2.1.2-1.
The UE shall be capable of performing CSI-RSRP measurements of at least 3 identified inter-frequency TPs per FS3
inter-frequency for up to 3 FS3 inter-frequencies and the UE physical layer shall be capable of reporting CSI-RSRP
measurements to higher layers with the measurement period defined in table 8.11.3.2.1.2-1 when DRX is in use, either
measurement gaps are scheduled or the UE supports capability of conducting such measurements without gaps.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 336 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.11.3.2.1.2-1: Requirements to measure FS3 inter-frequency TP
SCH Ês/Iot CSI-RS CSI-RS Ês/Iot Tmeasure_inter_FS3_CSI-RS_DRX [ms]
measurement
bandwidth Note2
[RB]
0 ≤ SCH Ês/Iot <25 0 ≤ CSI-RS Ês/Iot (5*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 <25 (20*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CSI-RS Ês/Iot (1*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4*Nfreq +M*N)*Max{TDMTC_periodicity, MGRP,
DRX cycle length}
NOTE 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
NOTE 2: The requirements for measurement bandwidth 25 RB are optional.
The CSI-RSRP measurement accuracy for all measured TPs shall be as specified in section 9.1.18.4.
8.11.3.2.1.2.1 Measurement Reporting Requirements
8.11.3.2.1.2.1.1 Periodic Reporting
Reported CSI-RSRP measurements contained in periodically triggered measurement reports shall meet the requirements
in section 9.1.18.4.
8.11.3.2.1.2.1.2 Event-triggered Periodic Reporting
Reported CSI-RSRP measurements contained in event triggered periodic measurement reports shall meet the
requirements in section 9.1.18.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
section 8.11.3.2.1.2.1.3.
8.11.3.2.1.2.1.3 Event Triggered Reporting
Reported CSI-RSRP measurements contained in event triggered measurement reports shall meet the requirements in
section 9.1.18.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report. When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_inter_TP_FS3_DRX
defined in section 8.11.3.2.1.2. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_inter_TP_SCE_DRX defined in clause 8.11.3.2.1.2 and
then triggers the measurement report as per TS 36.331 [2], the event triggered measurement reporting delay shall be less
than Tmeasure_inter_FS3_CSI-RS_DRX provided the timing to that TP has not changed more than ± 50 Ts while measurement gap
has not been available and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured or LBT is performed by the UE on the carrier used for the measurement reporting, an additional delay can be
expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 337 ETSI TS 136 133 V14.3.0 (2017-04)
8.11.3.2.2 E-UTRAN TDD – FS3 inter-frequency measurements
8.11.3.2.2.1 E-UTRAN TDD – FS3 inter-frequency measurements when no DRX is used
The requirements in this section for UE configured with TDD PCell and no DRX are the same as the requirements in
Section 8.11.3.2.1.1.
8.11.3.2.2.2 E-UTRAN TDD – FS3 inter-frequency measurements when DRX is used
The requirements in this section for UE configured with TDD PCell and DRX are the same as the requirements in
Section 8.11.3.2.1.2.
8.11.4 RSSI measurements
8.11.4.1 E-UTRAN intra-frequency measurements
NOTE: The requirements in this section are applicable only for measurements on SCC following the frame structure
type 3 [16].
The UE physical layer shall be capable of performing the RSSI measurements [4] on one or more serving carriers
operating under frame structure type 3 [16], if the carrier(s) are indicated by higher layers [2], and reporting the RSSI
measurements to higher layers. The UE physical layer shall provide to higher layers a single RSSI sample for each
OFDM symbol within each configured RSSI measurement duration [2] occurring with a configured RSSI measurement
timing configuration periodicity [2]. The RSSI measurement period corresponds to max(reportInterval, rmtc-Period),
where reportInterval and rmtc-Period [2] are configured for the RSSI measurement by higher layers.
The RSSI measurement performed and reported according to this section shall meet the RSSI measurement accuracy
requirement in Section 9.1.18.5.2.
8.11.4.2 E-UTRAN inter-frequency measurements
The UE physical layer shall be capable of performing the RSSI measurements [4] on one or more inter-frequency
carriers operating under frame structure type 3 [16], if the carrier(s) are indicated by higher layers [2], and reporting the
RSSI measurements to higher layers. The UE physical layer shall provide to higher layers a single RSSI sample for
each OFDM symbol within each configured RSSI measurement duration [2] occurring with a configured RSSI
measurement timing configuration periodicity [2]. The RSSI measurement period corresponds to max(reportInterval,
rmtc-Period* Nfreq, MGRP*Nfreq), where reportInterval and rmtc-Period [2] are configured for the RSSI measurement
by higher layers, and Nfreq is defined in clause 8.1.2.1.1.
If the UE requires measurement gaps to perform inter-frequency measurements, a single measurement gap pattern is
used for all concurrent inter-frequency measurements, including inter-frequency RSSI measurements.
The RSSI measurement performed and reported according to this section shall meet the RSSI measurement accuracy
requirement in Section 9.1.18.5.3.
8.11.5 Channel occupancy measurements
8.11.5.1 E-UTRAN intra-frequency channel occupancy measurements
NOTE: The requirements in this section are applicable only for measurements on SCC following the frame structure
type 3 [16].
The UE shall be capable of estimating the channel occupancy on one or more serving carrier frequencies indicated by
higher layers [2], based on RSSI samples provided by the physical layer. The channel occupancy measurement period
corresponds to max(reportInterval, rmtc-Period), where reportInterval and rmtc-Period [2] are configured for the
channel occupancy measurement by higher layers.
The channel occupancy measurement performed and reported according to this section shall meet the channel
occupancy measurement accuracy requirements in Section 9.1.18.6.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 338 ETSI TS 136 133 V14.3.0 (2017-04)
8.11.5.2 E-UTRAN inter-frequency channel occupancy measurements
The UE shall be capable of estimating the channel occupancy on one or more carrier frequencies indicated by higher
layers [2], based on RSSI samples provided by the physical layer. The channel occupancy measurement period
corresponds to max(reportInterval, rmtc-Period*Nfreq, MGRP*Nfreq), where reportInterval and rmtc-Period [2] are
configured for the channel occupany measurement by higher layers, and Nfreq is defined in clause 8.1.2.1.1.
If the UE requires measurement gaps to perform inter-frequency measurements, a single measurement gap pattern is
used for all concurrent inter-frequency measurements, including inter-frequency channel occupancy measurements.
The channel occupancy measurement performed and reported according to this section shall meet the channel
occupancy measurement accuracy requirements in Section 9.1.18.6.2.
8.12 Discovery Signal Measurements for E-UTRA Carrier
Aggregation under Operation with Frame Structure 3
8.12.1 Introduction
This section contains requirements on UE capabilities for support of E-UTRA carrier aggregation under operation with
frame structure 3.
Non configured frequencies may be measured with measurement gaps according to the requirements in Section 8.11.2.2
and Section 8.11.3.2.
The requirements in Section 8.12 shall apply for E-UTRA carrier aggregation of one FDD PCell or one TDD PCell and
SCell on one SCC, where the SCC is following the frame structure type 3 [16].
8.12.2 CRS based discovery signal measurements for E-UTRA carrier
aggregation
8.12.2.1 Introduction
The requirements in Section 8.12.2 shall apply for CRS based discovery signal measurements comprising RSRP and
RSRQ measurements [4].
8.12.2.2 Measurements of a secondary component carrier
A secondary component carrier may be activated and deactivated by MAC-CE commands as specified in [17]. The
applicable performance requirements depend on whether the SCell on the corresponding frequency is actived or
deactivated.
8.12.2.3 Measurements of a secondary component carrier with active SCell
When the SCell is activated, measurement performance requirements for the frequency are those given in
Section 8.11.2.1. If common DRX is in use, then the requirements for that secondary component carrier are given by the
DRX requirements in Section 8.11.2.1.1.2, otherwise the non-DRX requirements are applicable. The applicable
measurement accuracy requirements are in Section 9.1.19.
8.12.2.4 Measurements of a secondary component carrier with deactivated SCell
This section defines the measurement requirements of a secondary component carrier with deactivated SCell based on
the parameter measCycleSCell defined in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 339 ETSI TS 136 133 V14.3.0 (2017-04)
8.12.2.4.1 E-UTRAN secondary component carrier measurements when no common DRX
is used
When no DRX is in use the UE shall be able to identify a new detectable cell on a secondary component carrier within
the cell identification time Tidentify_SCC_FS3, where the cell identification of a cell shall include detection of the cell and
additionally performing a single measurement with measurement period of Tmeasure_SCC_FS3_CRS.
Tidentify_SCC_FS3 is the time period for cell identification as specified in Table 8.12.2.4.1-1,
Tmeasure_SCC_FS3_CRS is thetime period for measurements as shown in Table 8.12.2.4.1-2,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
L is the number of configured discovery signal occasions which are not available during Tidentify_SCC_FS3 for cell
identification at the UE due to the absence of the necessary radio signals from the cell,
M is the number of configured discovery signal occasions which are not available during Tmeasure_SCC_FS3_CRS for the
measurements at the UE due to the absence of the necessary radio signals from the cell.
The requirements in this section apply, provided that L and M are such that: the cell identification period Tidentify_SCC_FS3
does not exceed 75*measCycleSCell, and the time period Tmeasure_SCC_FS3_CRS for measurements does not exceed
60*measCycleSCell.
Table 8.12.2.4.1-1: Cell identification with deactivated SCell on SCC under operation with frame
structure 3
SCH Ês/Iot CRS CRS Ês/Iot Tidentify_SCC_FS3 [ms]
measurement
bandwidth [RB]
Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (7+L)*k1*k2*measCycleSCell
-6 ≤ SCH Ês/Iot < 0 <25 (25+L)*k1*k2*measCycleSCell
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (3+L)*k1*k2*measCycleSCell
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (9+L)*k1*k2*measCycleSCell
Note 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
Note 2: The requirements for measurement bandwidth ≥ 25 RB are optional.
NOTE 3: k1=2 when the measurement gaps configured for inter-frequency measurements in DMTC
occasions on a carrier with frame structure 3 overlap with some but not all DMTC occasions of
the measured cell; otherwise, k1=1, e.g., when measurement gaps configured for inter-frequency
measurements on a carrier with frame structure 3 do not overlap with DMTC occasions of the
measured cell or when the UE does not require the measurement gaps for the inter-frequency
measurements. The requirements apply, provided that the inter-frequency measurement gap
pattern does not overlap with all DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping with
⎜ 2
⎝ ⎢ ⎥⎠
the inter-frequency measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0)
SCells on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC=0.
A cell shall be considered detectable when the following conditions are met during the discovery signal occasions
which are available during Tidentify_SCC_FS3:
- RSRP related side condition given in Section 9.1.19 are fulfilled for a corresponding Band,
- SCH_RP|dBm is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is according to Table
8.12.2.4.1-1.
The measurement period for deactivated SCell measurements is Tmeasure_SCC_FS3_CRS according to the parameter
measCycleSCell shown in Table 8.12.2.4.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 340 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.12.2.4.1-2: Measurement requirements on SCC with deactivated SCell under operation with
frame structure 3 with deactivated SCell
SCH Ês/Iot CRS CRS Ês/Iot Tmeasure_SCC_FS3_CRS [ms]
measurement
bandwidth [RB]
Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (5+M)*k1*k2*measCycleSCell
-6 ≤ SCH Ês/Iot < 0 <25 (20+M)*k1*k2*measCycleSCell
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (1+M)*k1*k2*measCycleSCell
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M)*k1*k2*measCycleSCell
Note 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
Note 2: The requirements for measurement bandwidth ≥ 25 RB are optional.
Note 3: k1=2 when the measurement gaps configured for inter-frequency measurements in DMTC
occasions on a carrier with frame structure 3 overlap with some but not all DMTC occasions of
the measured cell; otherwise, k1=1, e.g., when measurement gaps configured for inter-frequency
measurements on a carrier with frame structure 3 do not overlap with DMTC occasions of the
measured cell or when the UE does not require the measurement gaps for the inter-frequency
measurements. The requirements apply, provided that the inter-frequency measurement gap
pattern does not overlap with all DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping with
⎜ 2
⎝ ⎢ ⎥⎠
the inter-frequency measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0)
SCells on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC=0.
The UE shall be capable of performing RSRP and RSRQ measurements for 3 identified cells on a secondary component
carrier, and the UE physical layer shall be capable of reporting measurements to higher layers within the measurement
period of Tmeasure_SCC_FS3_CRS.
The measurement accuracy for all measured cells shall be as specified in Section 9.1.19.
A UE may reconfigure the receiver bandwidth or turn on/off one of the RF chains when performing measurements on
one SCC with deactivated SCell. This may cause interruptions on PCell that are specified in Section 7.8.
8.12.2.4.1.1 Measurement Reporting Requirements
8.12.2.4.1.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in
Section 9.
8.12.2.4.1.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
Section 9.
The first report in event triggered periodic CRS based measurement reporting shall meet the requirements specified in
Section 8.12.2.4.1.1.3.
8.12.2.4.1.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in Section 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 341 ETSI TS 136 133 V14.3.0 (2017-04)
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_SCC_FS3
defined in Section 8.12.2.4.1. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_SCC_FS3 defined in Section 8.12.2.4.1 becomes
undetectable for a period ≤ 8 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tidentify_SCC_FS3_CRS provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or LBT is performed by the
UE on the carrier used for the measurement reporting an additional delay can be expected.
8.12.2.4.2 E-UTRAN secondary component carrier measurements when common DRX is
used
When DRX is in use the UE shall be able to identify a new detectable FS3 cell on a secondary component carrier within
the cell identification time Tidentify_SCC_FS3_DRX, according to the parameter measCycleSCell , where the cell identification
time of a cell shall include detection of the cell and additionally performing a single measurement with measurement
period of Tmeasure_SCC_FS3_CRS_DRX.
Tidentify_SCC_FS3_DRX is the time period for cell identification as shown in Table 8.12.2.4.2-1,
Tmeasure_SCC_FS3_CRS_DRX is the time period for measurements as shown in Table 8.12.2.4.2-2,
TDMTC_periodicity is the discovery signal measurement timing configuration periodicity of higher layer,
L is the number of configured discovery signal occasions during ON DURATION and which are not available during
Tidentify_SCC_FS3_DRX for cell identification at the UE due to the absence of the necessary radio signals from the cell,
M is the number of configured discovery signal occasions during ON DURATION and which are not available during
Tmeasure_SCC_FS3_CRS_DRX for the measurements at the UE due to the absence of the necessary radio signals from the cell.
The requirements in this section apply, provided that L and M are such that: the cell identification period
Tidentify_SCC_FS3_DRX does not exceed 75*Max{ measCycleSCell, DRX cycle length}, and the time period
Tmeasure_SCC_FS3_CRS_DRX for measurements does not exceed 60*Max{ measCycleSCell, DRX cycle length}.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 342 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.12.2.4.2-1: Cell identification on SCC with deactivated SCell under operation with frame
structure 3
SCH Ês/Iot CRS CRS Ês/Iot Tidentify_SCC_FS3_DRX [ms]
measurement
bandwidth [RB]
Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (7+L)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 <25 (25+L)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (3+L)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (9+L)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
Note 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
Note 2: The requirements for measurement bandwidth ≥ 25 RB are optional.
Note 3: k1=2 when the measurement gaps configured for inter-frequency in DMTC occasions
measurements on a carrier with frame structure 3 overlap with some but not all DMTC occasions
of the measured cell during ON DURATION; otherwise, k1=1, e.g., when measurement gaps
configured for inter-frequency measurements on a carrier with frame structure 3 do not overlap
with DMTC occasions of the measured cell during ON DURATION or when the UE does not
require the measurement gaps for the inter-frequency measurements. The requirements apply,
provided that the inter-frequency measurement gap pattern does not overlap with all DMTC
occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping with
⎜ 2
⎝ ⎢ ⎥⎠
the inter-frequency measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0)
SCells during ON DURATION on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC=0.
A cell shall be considered detectable when the following conditions are met during the discovery signal occasions
which are available during Tidentify_SCC_FS3_DRX:
- RSRP related side condition given in Section 9.1.19 are fulfilled for a corresponding Band,
- SCH_RP|dBm is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is according to Table
8.12.2.4.2-1.
The measurement period for deactivated scell measurements is Tmeasure_SCC_FS3_CRS_DRX according to the parameter
measCycleSCell shown in Table 8.12.2.4.2-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 343 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.12.2.4.2-2: Measurement requirements on SCC with deactivated SCell under operation with
frame structure 3
SCH Ês/Iot CRS CRS Ês/Iot Tmeasure_SCC_FS3_CRS_DRX [ms]
measurement
bandwidth [RB]
Note2
0 ≤ SCH Ês/Iot <25 -6 ≤ CRS Ês/Iot (5 +M)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 <25 (20+M)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CRS Ês/Iot (1+M)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M)* k1*k2*Max{ measCycleSCell,
DRX cycle length}
Note 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
Note 2: The requirements for measurement bandwidth ≥ 25 RB are optional.
Note 3: k1=2 when the measurement gaps configured for inter-frequency in DMTC occasions
measurements on a carrier with frame structure 3 overlap with some but not all DMTC occasions
of the measured cell during ON DURATION; otherwise, k1=1, e.g., when measurement gaps
configured for inter-frequency measurements on a carrier with frame structure 3 do not overlap
with DMTC occasions of the measured cell during ON DURATION or when the UE does not
require the measurement gaps for the inter-frequency measurements. The requirements apply,
provided that the inter-frequency measurement gap pattern does not overlap with all DMTC
occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured cell not overlapping with
⎜ 2
⎝ ⎢ ⎥⎠
the inter-frequeny measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0)
SCells during ON DURATION on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC=0.
The UE shall be capable of performing RSRP and RSRQ measurements for 3 identified cells on a secondary component
carrier, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement
period of Tmeasure_SCC_FS3_CRS_DRX.
The measurement accuracy for all measured cells shall be as specified in Section 9.1.19.
A UE may reconfigure receiver bandwidth taking into account the SCell activation/deactivation status, and when
making measurements of cells on one SCC with deactivated SCell. This may cause interruptions (packet drops) to a
PCell. No interruptions while the On Duration timer is running shall be allowed when common DRX is used. The
requirement considers only interruptions due to reconfiguration of the receiver bandwidth, and not due to other causes
such as RF impairments or channel conditions.
8.12.2.4.2.1 Measurement Reporting Requirements
8.12.2.4.2.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in Section
9.
8.12.2.4.2.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
Section 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.12.2.4.2.1.3.
8.12.2.4.2.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in Section 9.
The UE shall not send any event triggered CRS based measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 344 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_SCC_FS3
defined in Section 8.12.2.4.2. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_SCC_FS3_DRX defined in Section 8.12.2.4.2 becomes
undetectable for a period ≤ 8 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tidentify_SCC_FS3_CRS_DRX provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or LBT is performed by the
UE on the carrier used for the measurement reporting an additional delay can be expected.
8.12.3 Requirements for CSI-RS based discovery signal measurements for
E-UTRA carrier aggregation
8.12.3.1 Introduction
The requirements in Section 8.12.3 shall apply for CSI-RS based discovery signal measurements comprising CSI-RSRP
measurements [4].
8.12.3.2 Measurements of a secondary component carrier
A Secondary component carrier may be activated and deactivated by MAC-CE commands as specified in [17]. The
applicable performance requirements depend on whether the SCell on the corresponding frequency is actived or
deactivated.
8.12.3.3 Measurements of a secondary component carrier with active SCell
When the SCell is activated, measurement performance requirements for the frequency are those given in Section
8.11.3.1. If common DRX is in use, then the requirements for that secondary component carrier are given by the DRX
requirements in Section 8.11.3.1.1.2, otherwise the non DRX requirements are applicable. The applicable measurement
accuracy requirements are in Section 9.1.19.
8.12.3.4 Measurements of a secondary component carrier with deactivated SCell
This section defines the measurement requirements of a secondary component carrier with deactivated SCell based on
the parameter measCycleSCell defined in TS 36.331 [2].
8.12.3.4.1 E-UTRAN secondary component carrier measurements when no common DRX
is used
When no DRX is in use the UE shall be able to identify a new detectable FS3 TP on a secondary component carrier
within the cell identification time Tidentify_SCC_TP_FS3, where the identification of a TP shall include cell identification and
a single measurement on the TP within the measurement period Tmeasure_SCC_FS3_CSI-RS.
Tidentify_SCC_TP_FS3 = Tidentify_SCC_FS3 + Tmeasure_SCC_FS3_CSI-RS,
where:
Tidentify_SCC_FS3 is the time period for cell identification in Section 8.12.2.4.1,
Tmeasure_SCC_FS3_CSI-RS is the time period for TP measurement in Table 8.12.3.4.1-1,
M is the number of configured discovery signal occasions which are not available for the measurements at the UE
during Tmeasure_SCC_FS3_CSI-RS due to the absence of the necessary radio signals from the cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 345 ETSI TS 136 133 V14.3.0 (2017-04)
The requirements in this section apply, provided that M is such that: the time period Tmeasure_SCC_FS3_CSI-RS for TP
measurement does not exceed 60* measCycleSCell.
During Tidentify_SCC_TP_FS3 over multiple discovery signal occasions, the UE may assume the following:
- in all the discovery signal occasions, which are available at the UE, the corresponding necessary cell-specific
discovery signals are always available from the same set of TPs in the measured cell, and
- in all the discovery signal occasions, which are not available at the UE, the corresponding necessary cell-
specific discovery signals are not available from any TP within the same measured cell.
Table 8.12.3.4.1-1: Measurement requirements for a TP on SCC with deactivated SCell under
operation with frame structure 3
SCH Ês/Iot CSI-RS CSI-RS Ês/Iot Tmeasure_SCC_FS3_CSI-RS [ms]
measurement
bandwidth [RB] Note2
0 ≤ SCH Ês/Iot <25 0 ≤ CSI-RS Ês/Iot (5+M) * k1*k2* measCycleSCell
-6 ≤ SCH Ês/Iot < 0 <25 (20+M) * k1*k2* measCycleSCell
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CSI-RS Ês/Iot (1+M) * k1*k2* measCycleSCell
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M) * k1*k2* measCycleSCell
Note 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
Note 2: The requirements for measurement bandwidth ≥ 25 RB are optional.
Note 3: k1=2 when the measurement gaps configured for inter-frequency measurements in DMTC occasions on a
carrier with frame structure 3 overlap with some but not all DMTC occasions of the measured TP; otherwise,
k1=1, e.g., when measurement gaps configured for inter-frequency measurements on a carrier with frame
structure 3 do not overlap with DMTC occasions of the measured TP or when the UE does not require the
measurement gaps for the inter-frequency measurements. The requirements apply, provided that the inter-
frequency measurement gap pattern does not overlap with all DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured TP not overlapping with the inter-
⎜ 2
⎝ ⎢ ⎥⎠
frequency measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0) SCells on other FS3
carriers; otherwise, k2=1, e.g., when NFS3_SCC=0.
A TP shall be considered detectable when the following conditions are met during the discovery signal occasions which
are available during Tidentify_SCC_TP_FS3:
- CSI-RSRP related side condition given in Section 9.1.19 are fulfilled for a corresponding Band,
- SCH_RP|dBm is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is accordin g to Table
8.12.2.4.1-1.
The UE shall be capable of performing RSRP measurements for 3 identified TPs on a secondary component carrier, and
the UE physical layer shall be capable of reporting measurements to higher layers with the measurement period of
Tmeasure_SCC_FS3_CSI-RS.
The measurement accuracy for all measured TPs shall be as specified in Section 9.1.19.
A UE may reconfigure the receiver bandwidth or turn on/off one of the RF chains when performing measurements on
one SCC with deactivated SCell. This may cause interruptions on PCell that are specified in Section 7.8.
8.12.3.4.1.1 Measurement Reporting Requirements
8.12.3.4.1.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in
Section 9.
8.12.3.4.1.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
Section 9.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 346 ETSI TS 136 133 V14.3.0 (2017-04)
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.12.3.4.1.1.3.
8.12.3.4.1.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in Section 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_SCC_TP_FS3
defined in Section 8.12.3.4.1. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_SCC_TP_FS3 defined in Section 8.12.3.4.1 becomes
undetectable for a period ≤ [8] seconds and then the TP becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tidentify_SCC_FS3_CSI-RS provided the timing to that TP has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or LBT is performed by the
UE on the carrier used for the measurement reporting an additional delay can be expected.
8.12.3.4.2 E-UTRAN secondary component carrier measurements when common DRX is
used
When DRX is in use the UE shall be able to identify a new detectable FS3 TP on a secondary component carrier within
Tidentify_SCC_TP_FS3_DRX, according to the parameter measCycleSCell, where the identification of a TP shall include cell
identification and a single measurement on the TP within the measurement period Tmeasure_SCC_FS3_CSI-RS_DRX.
Tidentify_SCC_TP_FS3_DRX = Tidentify_SCC_FS3_DRX + Tmeasure_SCC_FS3_CSI-RS_DRX,
where:
Tidentify_SCC_FS3_DRX is the time period for cell identification in Section 8.12.2.4.2,
Tmeasure_SCC_FS3_CSI-RS_DRX is the time period for TP measurement in Table 8.12.3.4.2-1,
M is the number of configured discovery signal occasions during ON DURATION and which are not available during
Tmeasure_SCC_FS3_CSI-RS_DRX for the measurements at the UE due to the absence of the necessary radio signals from the cell.
The requirements in this section apply, provided that M is such that: the time period Tmeasure_SCC_FS3_CSI-RS_DRX for TP
measurement does not exceed 60*Max{ measCycleSCell, DRX cycle length}.
During Tidentify_SCC_TP_FS3_DRX over multiple discovery signal occasions, the UE may assume the following:
- in all the discovery signal occasions, which are available at the UE, the corresponding necessary cell-specific
discovery signals are always available from the same set of TPs in the measured cell, and
- in all the discovery signal occasions, which are not available at the UE, the corresponding necessary cell-
specific discovery signals are not available from any TP within the same measured cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 347 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.12.3.4.2-1: Measurement requirements for a TP on SCC with deactivated SCell under
operation with frame structure 3
SCH Ês/Iot CSI-RS CSI-RS Ês/Iot Tmeasure_SCC_FS3_CSI-RS_DRX [ms]
measurement
bandwidth [RB] Note2
0 ≤ SCH Ês/Iot <25 0 ≤ CSI-RS Ês/Iot (5+M) *
k1*k2*Max{ measCycleSCell, DRX
cycle length }
-6 ≤ SCH Ês/Iot < 0 <25 (20+M) *
k1*k2*Max{ measCycleSCell, DRX
cycle length }
0 ≤ SCH Ês/Iot ≥ 25 0 ≤ CSI-RS Ês/Iot (1+M) *
k1*k2*Max{ measCycleSCell, DRX
cycle length }
-6 ≤ SCH Ês/Iot < 0 ≥ 25 (4+M) *
k1*k2*Max{ measCycleSCell, DRX
cycle length }
Note 1: Discovery signal occasion duration (ds-OccasionDuration) is 1 ms.
Note 2: The requirements for measurement bandwidth ≥ 25 RB are optional.
Note 3: k1=2 when the measurement gaps configured for inter-frequency in DMTC occasions measurements on a
carrier with frame structure 3 overlap with some but not all DMTC occasions of the measured TP during ON
DURATION; otherwise, k1=1, e.g., when measurement gaps configured for inter-frequency measurements on
a carrier with frame structure 3 do not overlap with DMTC occasions of the measured TP during ON
DURATION or when the UE does not require the measurement gaps for the inter-frequency measurements.
The requirements apply, provided that the inter-frequency measurement gap pattern does not overlap with all
DMTC occasions of the measured cell.
⎛ ⎡ N FS 3 _ SCC ⎤ ⎞
k2= max⎜ 2, ⎢ ⎥ ⎟⎟ when DMTC occasions in the measured TP not overlapping with the inter-
⎜ 2
⎝ ⎢ ⎥⎠
frequency measurement gaps overlap with DMTC occasions of NFS3_SCC (NFS3_SCC>0) SCells during ON
DURATION on other FS3 carriers; otherwise, k2=1, e.g., when NFS3_SCC=0.
A TP shall be considered detectable when the following conditions are met during the discovery signal occasions which
are available during Tidentify_SCC_TP_FS3_DRX:
- CSI-RSRP related side condition given in Section 9.1.19 are fulfilled for a corresponding Band,
- SCH_RP|dBm is according to Annex B.2.12 for a corresponding Band and SCH Ês/Iot is according to Table
8.12.2.4.2-1.
The UE shall be capable of performing CSI-RSRP measurements for 3 identified TPs on a secondary component
carrier, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement
period of Tmeasure_SCC_FS3_CSI-RS_DRX.
The measurement accuracy for all measured TPs shall be as specified in Section 9.1.19.
A UE may reconfigure receiver bandwidth taking into account the SCell activation/deactivation status, and when
making measurements of TPs on one SCC with deactivated SCell. This may cause interruptions (packet drops) to a
PCell. No interruptions while the On Duration timer is running shall be allowed when common DRX is used. The
requirement considers only interruptions due to reconfiguration of the receiver bandwidth, and not due to other causes
such as RF impairments or channel conditions.
8.12.3.4.2.1 Measurement Reporting Requirements
8.12.3.4.2.1.1 Periodic Reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in
Section 9.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 348 ETSI TS 136 133 V14.3.0 (2017-04)
8.12.3.4.2.1.2 Event-triggered Periodic Reporting
Reported measurements contained in event triggered periodic measurement reports shall meet the requirements in
Section 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
Section 8.12.3.4.2.1.3.
8.12.3.4.2.1.3 Event Triggered Reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in Section 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which is caused by no UL resources for UE to send
the measurement report or by the LBT procedure performed by the UE in order to determine that the channel is clear for
performing uplink transmission.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify_SCC_TP_FS3_DRX
defined in Section 8.12.3.4.2. When L3 filtering is used or IDC autonomous denial is configured or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
If a TP which has been detectable at least for the time period Tidentify_SCC_TP_FS3_DRX defined in Section 8.12.3.4.2
becomes undetectable for a period ≤ 8 seconds and then the TP becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tidentify_SCC_FS3_CSI-RS_DRX provided the timing to that TP
has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or LBT is performed
by the UE on the carrier used for the measurement reporting an additional delay can be expected.
8.13 Measurements for UE Category M1
8.13.1 Introduction
The UE category M1 applicability of the requirements in subclause 8.13 is defined in Section 3.6.
This clause contains requirements on the UE regarding measurement reporting in RRC_CONNECTED state. The
requirements are specified for E-UTRA intra frequency measurements. These measurements may be used by the E-
UTRAN, e.g. for handover decisions. The measurement quantities are defined in [4], the measurement model is defined
in [22] and measurement accuracies are specified in clause 9. Control of measurement reporting is specified in
TS 36.331 [2].
When the UE is provided with IDC solution, the UE shall also perform RRM measurements and meet the corresponding
requirements in clause 8.
8.13.2 Requirements for UE category M1 with CE mode A
The UE category M1 applicability of the requirements in subclause 8.13.2 is defined in Section 3.6. The requirements
defined in clause 8.13.2 apply provided the following conditions are met:
- UE is configured with measurement gap according to any of gap patterns defined in Table 8.1.2.1-1.
8.13.2.1 E-UTRAN intra frequency measurements by UE category M1 with CE mode
A
The UE shall be able to identify new intra-frequency cells and perform RSRP measurements of identified intra-
frequency cells without an explicit intra-frequency neighbour cell list containing physical layer cell identities. During
the RRC_CONNECTED state the UE shall continuously measure identified intra frequency cells and additionally
search for and identify new intra frequency cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 349 ETSI TS 136 133 V14.3.0 (2017-04)
8.13.2.1.1 E-UTRAN FDD intra frequency measurements
8.13.2.1.1.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify and measure a new detectable FDD intra frequency cell
according to requirements in Table 8.13.2.1.1.1-1 when SCH Ês/Iot >= -6 dB
Table 8.13.2.1.1.1-1: Requirement on cell identification delay and measurement delay for FDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M1) Measurement delay (Tmeasure_intra_UE cat M1)
0 1.44 seconds 480 ms
1 2.88 seconds 960 ms
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.1 and 9.1.21.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M1. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.13.2.1.1.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP
measurement of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.1 and 9.1.21.2.
8.13.2.1.1.1.1 Measurement Reporting Requirements
8.13.2.1.1.1.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
8.13.2.1.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.2.1.1.1.1.3.
8.13.2.1.1.1.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.1 and 9.1.21.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send
the measurement report.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 350 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.2.1.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.2.1.1.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.2.1.1.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra_UE cat
as shown in table 8.13.2.1.1.2-1.
M1
When eDRX_CONN is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.2.1.1.2-1A.
Table 8.13.2.1.1.2-1: Requirement to identify a newly detectable FDD intrafrequency cell
Gap pattern DRX cycle Tidentify_intra_UE cat M1
ID length (s) (s) (DRX cycles)
0 ≤0.04 1.44 (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
1 <0.128 2.88 (Note1)
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
Note1: Number of DRX cycle depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.13.2.1.1.2-1A: Requirement to identify a newly detectable FDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (20)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.1 and 9.1.21.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.14-1 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M1.
When DRX is used, Tmeasure_intra_UE cat M1 is as specified in table 8.13.2.1.1.2-2. When eDRX_CONN is used,
Tmeasure_intra_UE cat M1 is as specified in table 8.13.2.1.1.2-3. The UE shall be capable of performing RSRP measurements
for 6 identified-intra-frequency cells, and the UE physical layer shall be capable of reporting measurements to higher
layers with the measurement period of Tmeasure_intra_UE cat M1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 351 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.13.2.1.1.2-2: Requirement to measure FDD intrafrequency cells
Gap pattern DRX cycle Tmeasure_intra_UE cat M1
ID length (s) (s) (DRX cycles)
0 <0.128 0.48 (Note1)
0.128≤DRX- Note2 (5)
cycle≤2.56
1 <0.256 0.96 (Note1)
0.256≤DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.13.2.1.1.2-3: Requirement to measure FDD intrafrequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
NOTE: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.1 and 9.1.21.2.
8.13.2.1.1.2.1 Measurement Reporting Requirements
8.13.2.1.1.2.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
8.13.2.1.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.2.1.1.2.1.3.
8.13.2.1.1.2.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.1 and 9.1.21.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.2.1.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.2.1.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 352 ETSI TS 136 133 V14.3.0 (2017-04)
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.2.1.2 E-UTRAN intra frequency measurements for HD-FDD
8.13.2.1.2.1 E-UTRAN intra frequency measurements when no DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.13.2.1.1.1 also apply for this section provided the following conditions are met:
- at least downlink subframe # 0 or downlink subframe # 5 per radio frame of an intra-frequency cell to be
identified by the UE is available at the UE over Tidentify_intra_UE cat M1;
- at least one downlink subframe per radio frame of measured cell is available at the UE for RSRP measurement
assuming measured cell is identified cell over Tmeasure_intra_UE cat M1.
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2 for a corresponding Band
8.13.2.1.2.2 E-UTRAN intra frequency measurements when DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
When DRX is in use the UE shall be able to identify a new detectable HD-FDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.2.1.2.2-1.
When eDRX_CONN is in use, the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.2.1.2.2-1A.
Table 8.13.2.1.2.2-1: Requirement to identify a newly detectable HD-FDD intrafrequency cell
Gap pattern DRX cycle Tidentify_intra_UE cat M1
ID length (s) (s) (DRX cycles)
0 ≤0.04 1.44 (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (32)
0.128<DRX- Note2(25)
cycle≤2.56
1 ≤0.08 2.88 (Note1)
0.128 3.2 (32)
0.128<DRX- Note2(25)
cycle≤2.56
Note1: Number of DRX cycle depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.13.2.1.2.2-1A: Requirement to identify a newly detectable HD-FDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (25)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.1 and 9.1.21.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 353 ETSI TS 136 133 V14.3.0 (2017-04)
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M1.
When DRX is used, Tmeasure_intra_UE cat M1 is as specified in table 8.13.2.1.2.2-2. When eDRX_CONN is used,
Tmeasure_intra_UE cat M1 is as specified in table 8.13.2.1.2.2-3. The UE shall be capable of performing RSRP measurements
for 6 identified-intra-frequency cells, and the UE physical layer shall be capable of reporting measurements to higher
layers with the measurement period of Tmeasure_intra_UE cat M1.
Table 8.13.2.1.2.2-2: Requirement to measure HD-FDD intrafrequency cells
Gap pattern DRX cycle Tidentify_intra_UE cat M1
ID length (s) (s) (DRX cycles)
0 <0.08 0.48 (Note1)
0.08≤DRX- Note2 (7)
cycle≤0.16
0.16<DRX- Note2(5)
cycle≤2.56
1 <0.16 0.96 (Note1)
DRX- 1.12 (7)
cycle=0.16
0.16<DRX- Note2(5)
cycle≤2.56
Note1: Number of DRX cycle depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.13.2.1.2.2-3: Requirement to measure HD-FDD intrafrequency cells when eDRX_CONN cycle
is used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
NOTE: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.1 and 9.1.21.2.
8.13.2.1.2.2.1 Measurement Reporting Requirements
8.13.2.1.2.2.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
8.13.2.1.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.2.1.2.2.1.3.
8.13.2.1.2.2.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.1 and 9.1.21.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 354 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.2.1.2.2 When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.2.1.2.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.2.1.3 E-UTRAN TDD intra frequency measurements
8.13.2.1.3.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use, the UE shall be able to identify and measure a new detectable TDD intra frequency cell
according to requirements in Table 8.13.2.1.3.1-1 when SCH Ês/Iot >= -6 dB
Table 8.13.2.1.3.1-1: Requirement on cell identification delay and measurement delay for TDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M1) Measurement delay (Tmeasure_intra_UE cat M1)
0 1.44 seconds 480 ms
1 2.88 seconds 960 ms
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.1 and 9.1.21.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M1. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.13.2.1.3.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP
measurements of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.1 and 9.1.21.2.
8.13.2.1.3.1.1 Measurement Reporting Requirements
8.13.2.1.3.1.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
8.13.2.1.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.2.1.3.1.1.3.
8.13.2.1.3.1.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.1 and 9.1.21.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 355 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat M1
defined in Clause 8.13.2.1.3.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.2.1.3.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than TMeasurement_Period Intra_UE cat M1 provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.13.2.1.3.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within Tidentify_intra_UE
catM1 as shown in table 8.13.2.1.3.2-1.
When eDRX_CONN is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.2.1.3.2-1A.
Table 8.13.2.1.3.2-1: Requirement to identify a newly detectable TDD intrafrequency cell
Gap pattern DRX cycle Tidentify_intra_UE cat M1
ID length (s) (s) (DRX cycles)
0 ≤0.04 1.44 (Note1)
0.04<DRX- Note2 (40)
cycle≤0.08
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
1 <0.128 2.88 (Note1)
0.128 3.2 (25)
0.128<DRX- Note2(20)
cycle≤2.56
Note1: Number of DRX cycle depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.13.2.1.3.2-1A: Requirement to identify a newly detectable TDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (20)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.21.1 and 9.1.21.2 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M1.
When DRX is used, Tmeasure_intra_UE cat M1 is as specified in table 8.13.2.1.3.2-2. When eDRX_CONN is used,
Tmeasure_intra_UE cat M1 is as specified in table 8.13.2.1.3.2-3. The UE shall be capable of performing RSRP measurements
for 6 identified intra-frequency cells and the UE physical layer shall be capable of reporting measurements to higher
layers with the measurement period of Tmeasure_intra_UE cat M1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 356 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.13.2.1.3.2-2: Requirement to measure TDD intra frequency cells
Gap pattern DRX cycle Tmeasure_intra_UE cat M1
ID length (s) (s) (DRX cycles)
0 <0.128 0.48 (Note1)
0.128≤DRX- Note2 (5)
cycle≤2.56
1 <0.256 0.96 (Note1)
0.256≤DRX- Note2 (5)
cycle≤2.56
Note1: Number of DRX cycle depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.13.2.1.3.2-3: Requirement to measure TDD intra frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
NOTE: Time depends upon the eDRX_CONN cycle in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.1 and 9.1.21.2.
8.13.2.1.3.2.1 Measurement Reporting Requirements
8.13.2.1.3.2.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
8.13.2.1.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.1 and 9.1.21.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.2.1.3.2.1.3.
8.13.2.1.3.2.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.1 and 9.1.21.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.2.1.3.2. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.2.1.3.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 357 ETSI TS 136 133 V14.3.0 (2017-04)
8.13.2.2 E-UTRAN E-CID Measurements Requirements for UE category M1 with CE
mode A
8.13.2.2.1 E-UTRAN FDD Intra-frequency E-CID RSRP Measurements
8.13.2.2.1.1 Introduction
The requirements in section 8.13.2.2.1 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN FDD intra-frequency RSRP
measurements [24].
8.13.2.2.1.2 Measurement Requirements
The requirements in section 8.13.2.1.1 also apply for this section except the measurement reporting requirements. The
measurement reporting requirements for E-CID RSRP are defined in section 8.13.2.2.1.3.
8.13.2.2.1.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP measurements contained in periodically triggered measurement reports shall meet the requirements in
section 9.1.21.1.
8.13.2.2.2 E-UTRAN HD-FDD Intra-frequency E-CID RSRP Measurements
8.13.2.2.2.1 Introduction
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.13.2.2.1.1 also apply for this section provided the following conditions are met:
- at least downlink subframe # 0 and downlink subframe # 5 per radio frame of an intra-frequency cell to be
identified by the UE is available at the UE over Tidentify_intra_UE cat M1;
- at least two consecutive downlink subframe per radio frame of measured cell is available at the UE for RSRP
measurements assuming measured cell is identified cell over Tmeasure_intra_UE cat M1.
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2
8.13.2.2.2.2 Measurement Requirements
The requirements in section 8.13.2.1.2 also apply for this section except the measurement reporting requirements. The
measurement reporting requirements for E-CID RSRP are defined in section 8.13.2.2.2.3.
8.13.2.2.2.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP measurements contained in periodically triggered measurement reports shall meet the requirements in
section 9.1.21.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 358 ETSI TS 136 133 V14.3.0 (2017-04)
8.13.2.2.3 E-UTRAN TDD Intra-frequency E-CID RSRP Measurements
8.13.2.2.3.1 Introduction
The requirements in section 8.13.2.2.3 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN TDD intra-frequency RSRP
measurements [24].
8.13.2.2.3.2 Measurement Requirements
The requirements in section 8.13.2.1.3 also apply for this section except the measurement reporting requirements. The
measurement reporting requirements for E-CID RSRP are defined in section 8.13.2.2.3.3.
8.13.2.2.3.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP measurements contained in periodically triggered measurement reports shall meet the requirements in
section 9.1.21.1.
8.13.3 Requirements for UE category M1 with CE mode B
The UE category M1 applicability of the requirements in subclause 8.13.3 is defined in Section 3.6. The requirements
defined in clause 8.13.3 apply provided the following conditions are met:
- UE is configured with measurement gap according to any of gap patterns defined in Table 8.1.2.1-1.
8.13.3.1 E-UTRAN intra frequency measurements by UE category M1 with CE mode
B
The UE shall be able to identify new intra-frequency cells and perform RSRP measurements of identified intra-
frequency cells without an explicit intra-frequency neighbour cell list containing physical layer cell identities. During
the RRC_CONNECTED state the UE shall continuously measure identified intra frequency cells and additionally
search for and identify new intra frequency cells.
8.13.3.1.1 E-UTRAN FDD intra frequency measurements
8.13.3.1.1.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify and measure a new detectable FDD intra frequency cell
according to requirements in Table 8.13.3.1.1.1-1 provided that additional conditions table 8.13.3.1.1.1-2 is met.
Table 8.13.3.1.1.1-1: Requirement on cell identification delay and measurement delay for FDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M1) Measurement delay (Tmeasure_intra_UE cat M1)
0 320.8 s 800 ms
1 321.6 s 1600ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 359 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.13.3.1.1.1-2: Conditions on SCH Ês/Iot for cell identification delay and measurement delay for
FDD intrafrequency cell
SCH Ês/Iot of already Neighouring cell SCH Cell identification delay Measurement delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M1) (Tmeasure_intra_UE cat M1)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table As defined in table
8.13.3.1.1.1-1 8.13.3.1.1.1-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2 Requirements in 8.13.2
apply apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2 Requirements in 8.13.2
apply apply
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.3 and 9.1.21.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M1. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.13.3.1.1.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP
measurements of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.3 and 9.1.21.4.
8.13.3.1.1.1.1 Measurement Reporting Requirements
8.13.3.1.1.1.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.17.3 and 9.1.21.4.
8.13.3.1.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.3.1.1.1.1.3.
8.13.3.1.1.1.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.3 and 9.1.21.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: pusch-maxNumRepetitionCEmodeB x TTIDCCH, where pusch-maxNumRepetitionCEmodeB [2] is the maximum
number of PUSCH repetitions configured for the UE in CE Mode B provided that pusch-
maxNumRepetitionCEmodeB >1, othwerwise uncertainty is defined as 2 x TTIDCCH. This measurement reporting delay
excludes a delay which caused by no UL resoureces for UE to send the measurement report.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 360 ETSI TS 136 133 V14.3.0 (2017-04)
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.3.1.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.3.1.1.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.3.1.1.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra_UE cat
as shown in table 8.13.3.1.1.2-1 provided that additional conditions Table 8.13.3.1.1.2-1A is met.
M1
When eDRX_CONN is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.3.1.1.2-1B.
Table 8.13.3.1.1.2-1: Requirement to identify a newly detectable FDD intrafrequency cell
Gap pattern ID DRX cycle Tidentify_intra_UE cat M1 (s)
length (s) (DRX cycles)
0 ≤0.64 320.8 (Note1)
0.64< DRX- Note2(400)
cycle≤2.56
1 DRX-cycle ≤ 321.6 (Note1)
0.640
0.64< DRX- Note2(400)
cycle≤2.56
Note1: Number of DRX cycle depends upon the DRX cycle in
use
Note2: Time depends upon the DRX cycle in use
Table 8.13.3.1.1.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable FDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M1)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.13.3.1.1.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2
apply
Table 8.13.3.1.1.2-1B: Requirement to identify a newly detectable FDD intrafrequency cell when
eDRX_CONN is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.3 and 9.1.21.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M1.
When DRX is used, Tmeasure_intra_UE cat M1 is as specified in table 8.13.3.1.1.2-2 provided that additional conditions table
8.13.3.1.1.2-3 is met. When eDRX_CONN is used, Tmeasure_intra_UE cat M1 is as specified in table 8.13.3.1.1.2-4. The UE
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 361 ETSI TS 136 133 V14.3.0 (2017-04)
shall be capable of performing RSRP measurements for 6 identified-intra-frequency cells, and the UE physical layer
shall be capable of reporting measurements to higher layers with the measurement period of Tmeasure_intra_UE cat M1.
Table 8.13.3.1.1.2-2: Requirement to measure FDD intrafrequency cells
Gap pattern DRX cycle Tmeasure_intra_UE cat M1
ID length (s) (s) (DRX cycles)
0 ≤0.16 0.8 (Note1)
0.16<DRX- Note2(5)
cycle≤2.56
1 ≤0.32 1.6 (Note1)
0.32<DRX- Note2(5)
cycle≤2.56
Note1: Number of DRX cycle depends upon the DRX
cycle in use
Note2: Time depends upon the DRX cycle in use
Table 8.13.3.1.1.2-3: Conditions on SCH Ês/Iot to measure FDD intrafrequency cell
SCH Ês/Iot of serving Target cell SCH Ês/Iot: Q2 Measurement delay
cell: Q1 (Tmeasure_intra_UE cat M1)
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.13.3.1.1.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2
apply
Table 8.13.3.1.1.2-4: Requirement to measure FDD intrafrequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
NOTE: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.3 and 9.1.21.4.
8.13.3.1.1.2.1 Measurement Reporting Requirements
8.13.3.1.1.2.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
8.13.3.1.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.3.1.1.2.1.3.
8.13.3.1.1.2.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.3 and 9.1.21.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 362 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.3.1.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.3.1.1.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.3.1.2 E-UTRAN intra frequency measurements for HD-FDD
8.13.3.1.2.1 E-UTRAN intra frequency measurements when no DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.13.3.1.1.1 also apply for this section provided the following conditions are met:
- at least downlink subframe # 0 and downlink subframe # 5 per radio frame of an intra-frequency cell to be
identified by the UE is available at the UE over Tidentify_intra_UE cat M1;
- at least two consecutive downlink subframe per radio frame of measured cell is available at the UE for RSRP
measurements assuming measured cell is identified cell over Tmeasure_intra_UE cat M1.
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-4
8.13.3.1.2.2 E-UTRAN intra frequency measurements when DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
When DRX is in use the UE shall be able to identify a new detectable HD-FDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.3.1.2.2-1 provided that additional conditions table 8.13.3.1.2.2-1A is met.
When eDRX_CONN is in use, the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.3.1.2.2-1B.
Table 8.13.3.1.2.2-1: Requirement to identify a newly detectable HD-FDD intrafrequency cell
Gap pattern ID DRX cycle Tidentify_intra_UE cat M1 (s)
length (s) (DRX cycles)
0 ≤0.64 320.8 (Note1)
0.64<DRX- Note2(400)
cycle≤2.56
1 <0.64 321.6 (Note1)
0.64≤DRX- Note2(400)
cycle≤2.56
Note1: Number of DRX cycle depends upon the DRX cycle in
use
Note2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 363 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.13.3.1.2.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable HD-FDD intrafrequency
cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M1)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.13.3.1.2.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2
apply
Table 8.13.3.1.2.2-1B: Requirement to identify a newly detectable HD-FDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.3 and 9.1.21.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-4 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M1.
When DRX is used, Tmeasure_intra_UE cat M1 is as specified in table 8.13.3.1.2.2-2 provided that additional conditions Table
8.13.3.1.2.2-3 is met. When eDRX_CONN cycle is used, Tmeasure_intra_UE cat M1 is as specified in table 8.13.3.1.2.2-4. The
UE shall be capable of performing RSRP measurements for 6 identified-intra-frequency cells, and the UE physical layer
shall be capable of reporting measurements to higher layers with the measurement period of Tmeasure_intra_UE cat M1.
Table 8.13.3.1.2.2-2: Requirement to measure HD-FDD intrafrequency cells
Gap pattern ID DRX cycle Tmeasure_intra_UE cat M1 (s)
length (s) (DRX cycles)
0 <0.128 0.8 (Note1)
0.128≤DRX- Note2 (7)
cycle≤0.16
0.16<DRX- Note2(5)
cycle≤2.56
1 ≤0.32 1.6 (Note1)
0.32<DRX- Note2(5)
cycle≤2.56
Note1: Number of DRX cycle depends upon the DRX cycle in
use
Note2: Time depends upon the DRX cycle in use
Table 8.13.3.1.2.2-3: Conditions on SCH Ês/Iot to measure HD-FDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Measurement delay
identified cell including Ês/Iot: Q2 (Tmeasure_intra_UE cat M1)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.13.3.1.2.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2
apply
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 364 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.13.3.1.2.2-4: Requirement to measure HD-FDD intrafrequency cells when eDRX_CONN cycle
is used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
NOTE: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.3 and 9.1.21.4.
8.13.3.1.2.2.1 Measurement Reporting Requirements
8.13.3.1.2.2.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
8.13.3.1.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.3.1.2.2.1.3.
8.13.3.1.2.2.1.3 Event Triggered Reporting
Reported RSRP measurements contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.3 and 9.1.21.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: pusch-maxNumRepetitionCEmodeB x TTIDCCH, where pusch-maxNumRepetitionCEmodeB [2] is the
maximum number of PUSCH repetitions configured for the UE in CE Mode B provided that pusch-
maxNumRepetitionCEmodeB >1, othwerwise uncertainty is defined as 2 x TTIDCCH. This measurement reporting delay
excludes a delay which caused by no UL resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.3.1.2.2 When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.3.1.2.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.3.1.3 E-UTRAN TDD intra frequency measurements
8.13.3.1.3.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify and measure a new detectable TDD intra frequency cell
according to requirements in Table 8.13.3.1.3.1-1provided that additional conditions Table 8.13.3.1.3.1-2 is met.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 365 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.13.3.1.3.1-1: Requirement on cell identification delay and measurement delay for TDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M1) Measurement delay (Tmeasure_intra_UE cat M1)
0 320.8 s 800 ms Note1
[1600 ms] Note2
1 321.6 s 1600 ms Note1
[3200 ms] Note2
Note1: Under TDD UL/DL configuration other than 0.
Note2: Under TDD UL/DL configuration 0.
Table 8.13.3.1.3.1-2: Conditions on SCH Ês/Iot for cell identification delay and measurement delay for
TDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay Measurement delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M1) (Tmeasure_intra_UE cat M1)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table As defined in table
8.13.3.1.3.1-1 8.13.3.1.3.1-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2 Requirements in 8.13.2
apply apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2 Requirements in 8.13.2
apply apply
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.21.3 and 9.1.21.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M1. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.13.3.1.3.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP
measurements of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.3 and 9.1.21.4.
8.13.3.1.3.1.1 Measurement Reporting Requirements
8.13.3.1.3.1.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
8.13.3.1.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.3.1.3.1.1.3.
8.13.3.1.3.1.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.3 and 9.1.21.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 366 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: pusch-maxNumRepetitionCEmodeB consecutive uplink TTIDCCH, where pusch-
maxNumRepetitionCEmodeB [2] is the maximum number of PUSCH repetitions configured for the UE in CE Mode B
provided that pusch-maxNumRepetitionCEmodeB >1, othwerwise uncertainty is defined as 2 x TTIDCCH.This
measurement reporting delay excludes a delay which caused by no UL resources for UE to send the measurement
report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat M1
defined in Clause 8.13.3.1.3.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.3.1.3.1 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.3.1.3.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within Tidentify_intra_ UE cat
M1 as shown in table 8.13.3.1.3.2-1 provided that additional conditions table 8.13.3.1.3.2-1A is met.
When eDRX_CONN is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
Tidentify_intra_UE cat M1 as shown in table 8.13.3.1.3.2-1B.
Table 8.13.3.1.3.2-1: Requirement to identify a newly detectable TDD intrafrequency cell
Gap pattern ID DRX cycle Tidentify_intra_UE cat M1 (s)
length (s) (DRX cycles)
0 DRX-cycle ≤ 0.64 320.8 (Note1)
0.64<DRX- Note2(400)
cycle≤2.56
1 DRX-cycle ≤ 0.64 321.6 (Note1)
0.64<DRX- Note2(400)
cycle≤2.56
Note1: Number of DRX cycle depends upon the DRX cycle in
use
Note2: Time depends upon the DRX cycle in use
Table 8.13.3.1.3.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable TDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M1)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.13.3.1.3.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2
apply
Table 8.13.3.1.3.2-1B: Requirement to identify a newly detectable TDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400)
NOTE: Time depends upon the eDRX_CONN cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 367 ETSI TS 136 133 V14.3.0 (2017-04)
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.21.3 and 9.1.21.4 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M1.
When DRX is used, Tmeasure_intra_UE cat M1 is as shown in table 8.13.3.1.3.2-2 provided that additional conditions Table
8.13.3.1.3.2-3 is met. When eDRX_CONN is used, Tmeasure_intra_UE cat M1 is as shown in table 8.13.3.1.3.2-4. The UE shall
be capable of performing RSRP measurement for 6 identified intra-frequency cells and the UE physical layer shall be
capable of reporting measurements to higher layers with the measurement period of Tmeasure_intra_UE cat M1.
Table 8.13.3.1.3.2-2: Requirement to measure TDD intra frequency cells
TDD Uplink- Gap pattern ID DRX cycle Tmeasure_intra_UE cat M1 (s)
downlink length (s) (DRX cycles)
configuration
Other than 0 0 ≤0.16 0.8 (Note1)
0.16<DRX- Note2(5)
cycle≤2.56
1 ≤0.32 1.6 (Note1)
0.32<DRX- Note2(5)
cycle≤2.56
0 0 ≤0.32 [1.6] (Note1)
0.32<DRX- Note2(5)
cycle≤2.56
1 ≤0.64 [3.2] (Note1)
0.64<DRX- Note2(5)
cycle≤2.56
Note1: Number of DRX cycle depends upon the DRX cycle in use.
Note2: Time depends upon the DRX cycle in use.
Table 8.13.3.1.3.2-3: Conditions on SCH Ês/Iot to measure TDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Measurement delay
identified cell including Ês/Iot: Q2 (Tmeasure_intra_UE cat M1)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.13.3.1.3.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.13.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.13.2
apply
Table 8.13.3.1.3.2-4: Requirement to measure TDD intra frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M1 (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
NOTE: Time depends upon the eDRX_CONN cycle in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.21.3 and 9.1.21.4.
8.13.3.1.3.2.1 Measurement Reporting Requirements
8.13.3.1.3.2.1.1 Periodic Reporting
Reported RSRP measurement contained in periodically triggered measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 368 ETSI TS 136 133 V14.3.0 (2017-04)
8.13.3.1.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP measurement contained in event triggered periodic measurement reports shall meet the requirements in
sections 9.1.21.3 and 9.1.21.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.13.3.1.3.2.1.3.
8.13.3.1.3.2.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.21.3 and 9.1.21.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat M1
defined in Clause 8.13.3.1.3.2. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M1 defined in clause 8.13.3.1.3.2 becomes
undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M1 provided the timing to that cell has not
changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial is
configured, an additional delay can be expected.
8.13.3.1.4 E-UTRAN FDD intra frequency measurements with autonomous gaps for UE
category M1 with CE mode B
The requirements defined in this subclause 8.13.3.1.4 apply provided the following condition is met:
- Tx diversity or transmission using multiple antennas are supported in the target cell to be detected.
- Repetitions of MIB/SIB1-BRare supported in the target cell to be detected.
8.13.3.1.4.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify
and report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps
in downlink reception and uplink transmission for receiving MIB and SIB1-BRmessage according to clause 5.5.3.1
of TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If
autonomous gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or
eDRX_CONN is used or not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of
E-UTRA cell within:
Tidentify_C GI_Cat M1, intra = Tbasic _ identify_C GI_Cat M1, intra ms
Where
Tbasic_identify_CGI_Cat M1, intra = 5120 ms. This is the time period used in the above equation where the maximum
allowed time for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has
been already identified by the UE.
A cell shall be considered identifiable following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.14 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 369 ETSI TS 136 133 V14.3.0 (2017-04)
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI_Cat M1,.intra is applicable when no
DRX is used as well as when any of DRX and eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI_Cat M1, intra ms , over which the UE identifies the new CGI of E-UTRA cell, the PBCH
repetition and SIB1-BR repetition level in the target cell shall be as specified in Table 8.13.3.1.4.1-1.
Table 8.13.3.1.4.1-1: Conditions in target cell during Tbasic_identify_CGI_Cat M1, intra.
Target cell
Ês/Iot [dB] PBCH repetition SIB1-BR repetition level
≥ -15 Configured as specified in TS 36.211 [16] 16
8.13.3.1.4.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.13.3.1.5 E-UTRAN intra frequency measurements with autonomous gaps for HD-FDD UE
category M1 with CE mode B
The requirements in this section are applicable for the UE which supports half duplex FDD operation on one or more
supported frequency bands [2].
The requirements defined in this subclause 8.13.3.1.5 apply provided the following condition is met:
- Tx diversity or transmission using multiple antennas are supported in the target cell to be detected.
- Repetitions of MIB/SIB1-BR are supported in the target cell to be detected.
8.13.3.1.5.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
The CGI requirements defined in clause 8.13.3.1.4.1 also apply for this section.
8.13.3.1.5.2 ECGI Reporting Delay
The ECGI reporting delay defined in clause 8.13.3.1.5.2 also apply for this section
8.13.3.1.6 E-UTRAN TDD intra frequency measurements with autonomous gaps for UE
category M1 with CE mode B
The requirements defined in this subclause 8.13.3.1.6 apply provided the following condition is met:
- Tx diversity or transmission using multiple antennas are supported in the target cell to be detected.
- Repetitions of MIB/SIB1-BR are supported in the target cell to be detected.
8.13.3.1.6.1 Identification of a new CGI of E-UTRA cell with autonomous gaps
No explicit neighbour list is provided to the UE for identifying a new CGI of E-UTRA cell. The UE shall identify and
report the CGI when requested by the network for the purpose ‘reportCGI’. The UE may make autonomous gaps in
downlink reception and uplink transmission for receiving MIB and SIB1-BR messages according to clause 5.5.3.1 of
TS 36.331 [2]. Note that a UE is not required to use autonomous gap if si-RequestForHO is set to false. If autonomous
gaps are used for measurement with the purpose of ‘reportCGI’, regardless of whether DRX or eDRX_CONN is used or
not, or whether SCell(s) are configured or not, the UE shall be able to identify a new CGI of E-UTRA cell within:
Tidentify_C GI_Cat M1, intra = Tbasic _ identify_C GI_Cat M1, intra ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 370 ETSI TS 136 133 V14.3.0 (2017-04)
Where
Tbasic_identify_CGI_Cat M1, intra = 5120 ms. This is the time period used in the above equation where the maximum
allowed time for the UE to identify a new CGI of an E-UTRA cell is defined, provided that the E-UTRA cell has
been already identified by the UE.
A cell shall be considered identifiable when the following conditions are fulfilled:
- RSRP related side conditions given in Clause 9.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.14 for a corresponding Band
The MIB of an E-UTRA cell whose CGI is identified shall be considered decodable by the UE provided the PBCH
demodulation requirements are met according to [5].
The requirement for identifying a new CGI of an E-UTRA cell within Tbasic_identify_CGI_Cat M1, intra is applicable when no
DRX is used as well as when any of the DRX or eDRX_CONN cycles specified in TS 36.331 [2] is used.
Within the time, Tidentify_C GI_Cat M1, intra ms , over which the UE identifies the new CGI of E-UTRA cell, the PBCH
repetition and SIB1-BR repetition level in the target cell shall be as specified Table 8.13.3.1.6.1-2.
Table 8.13.3.1.6.1-1: Conditions in target cell during Tbasic_identify_CGI_Cat M1, intra.
Target cell
Ês/Iot [dB] PBCH repetition level SIB1-BR repetition level
≥ -15 Configured with repetition, as specified in TS 36.211 [16] 16
8.13.3.1.6.2 ECGI Reporting Delay
The ECGI reporting delay occurs due to the delay uncertainty when inserting the ECGI measurement report to the TTI
of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. In case DRX is used, the ECGI
reporting may be delayed until the next DRX cycle. In case eDRX_CONN is used, the ECGI reporting may be delayed
until the next eDRX_CONN cycle. If IDC autonomous denial is configured, an additional delay can be expected.
8.13.3.2 E-UTRAN E-CID Measurements Requirements for UE category M1 with CE
mode B
8.13.3.2.1 E-UTRAN FDD Intra-frequency E-CID RSRP Measurements
8.13.3.2.1.1 Introduction
The requirements in section 8.13.3.2.1 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN FDD intra-frequency RSRP
measurements [24].
8.13.3.2.1.2 Measurement Requirements
The requirements in section 8.13.3.1.1 also apply for this section except the measurement reporting requirements. The
measurement reporting requirements for E-CID RSRP are defined in section 8.13.3.2.1.3.
8.13.3.2.1.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP measurements contained in periodically triggered measurement reports shall meet the requirements in
section 9.1.17.3 and 9.1.17.4 respectively.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 371 ETSI TS 136 133 V14.3.0 (2017-04)
8.13.3.2.2 E-UTRAN HD-FDD Intra-frequency E-CID RSRP Measurements
8.13.3.2.2.1 Introduction
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.13.3.2.1.1 also apply for this section provided the following conditions are met:
- at least downlink subframe # 0 and downlink subframe # 5 per radio frame of an intra-frequency cell to be
identified by the UE is available at the UE over Tidentify_intra_UE cat M1;
- at least two consecutive downlink subframe per radio frame of measured cell is available at the UE for RSRP
measurements assuming measured cell is identified cell over Tmeasure_intra_UE cat M1.
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-4
8.13.3.2.2.2 Measurement Requirements
The requirements in section 8.13.3.1.2 also apply for this section except the measurement reporting requirements. The
measurement reporting requirements for E-CID RSRP are defined in section 8.13.3.2.2.3.
8.13.3.2.2.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP measurements contained in periodically triggered measurement reports shall meet the requirements in
section 9.1.17.3 and 9.1.17.4 respectively.
8.13.3.2.3 E-UTRAN TDD Intra-frequency E-CID RSRP Measurements
8.13.3.2.3.1 Introduction
The requirements in section 8.13.3.2.3 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN TDD intra-frequency RSRP
measurements [24].
8.13.3.2.3.2 Measurement Requirements
The requirements in section 8.13.3.1.3 also apply for this section except the measurement reporting requirements. The
measurement reporting requirements for E-CID RSRP are defined in section 8.13.3.2.3.3.
8.13.3.2.3.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP measurements contained in periodically triggered measurement reports shall meet the requirements in
section 9.1.17.3 and 9.1.17.4 respectively.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 372 ETSI TS 136 133 V14.3.0 (2017-04)
8.14 Measurements for UE category NB1
8.14.1 Introduction
This clause contains requirements on the UE category NB1 regarding measurement in RRC_CONNECTED state. The
requirements are specified for NB-IoT intra frequency measurements for serving NB-IoT cell. These measurements
may be used by the NB-IoT for uplink power control. The measurement quantities are defined in [4], the measurement
model is defined in [22] and measurement accuracies are specified in clause 9. During the RRC_CONNECTED state
the UE shall continuously measure serving NB-IoT cell.
The UE shall meet all applicable requirements specified in clause 8.14 under the following conditions:
- at least 1 DL subframe per radio frame of serving NB-IoT cell is available at the UE during measurement period.
8.14.2 NB-IoT intra frequency measurements under normal coverage
8.14.2.1 NB-IoT intra frequency measurements when no DRX is used
In the RRC_CONNECTED state the measurement period for intra frequency measurements is 800ms. The NRSRP
measurement accuracy shall be as specified in the sub-clauses 9.1.22.1.
8.14.2.2 NB-IoT intra frequency measurements when DRX is used
When DRX is used in the RRC_CONNECTED state the measurement period for intra frequency measurements is
Tmeasure_intra as shown in table 8.14.2.2-1.
Table 8.14.2.2-1: Requirement for intrafrequency measurement
DRX cycle length (s) Tmeasure_intra (s) (DRX cycles)
0.256<DRX-cycle≤9.216 Note1 ([5])
Note1: Time depends upon the DRX cycle in use
The NRSRP measurement accuracy shall be as specified in the sub-clauses 9.1.22.1
8.14.3 NB-IoT intra frequency measurements under enhanced coverage
8.14.3.1 NB-IoT intra frequency measurements when no DRX is used
In the RRC_CONNECTED state the measurement period for intra frequency measurements is 1600ms. The NRSRP
measurement accuracy shall be as specified in the sub-clauses 9.1.22.1.
8.14.3.2 NB-IoT intra frequency measurements when DRX is used
When DRX is used in the RRC_CONNECTED state the measurement period for intra frequency measurements is
Tmeasure_intra as shown in table 8.14.3.2-1.
Table 8.14.3.2-1: Requirement for intrafrequency measurement
DRX cycle length (s) Tmeasure_intra (s)
(DRX cycles)
0.256<DRX-cycle≤9.216 Note1 ([5])
Note1: Time depends upon the DRX cycle in use
The NRSRP measurement accuracy shall be as specified in the sub-clauses 9.1.22.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 373 ETSI TS 136 133 V14.3.0 (2017-04)
8.15 Measurements for UE Category M2
8.15.1 Introduction
The UE category M2 applicability of the requirements in subclause 8.15 is defined in Section 3.6.
This clause contains requirements on the UE regarding measurement reporting in RRC_CONNECTED state. The
requirements are specified for E-UTRA intra frequency measurements. These measurements may be used by the E-
UTRAN, e.g. for handover decisions. The measurement quantities are defined in [4], the measurement model is defined
in [22] and measurement accuracies are specified in clause 9. Control of measurement reporting is specified in
TS 36.331 [2].
When the UE is provided with IDC solution, the UE shall also perform RRM measurements and meet the corresponding
requirements in clause 8.
8.15.2 Requirements for UE category M2 with CE mode A
The UE category M2 applicability of the requirements in subclause 8.15.2 is defined in Section 3.6. The requirements in
this section are applicable for UE category M2 configured with CE mode A. The requirements defined in clause 8.15.2
apply provided the following conditions are met:
- UE is configured with measurement gap according to any of gap patterns defined in Table 8.1.2.1-1.
8.15.2.1 Maximum allowed layers for multiple monitoring for UE category M2 with CE
mode A
The UE UE category M2 configured with CE mode A shall be capable of monitoring at least:
- Depending on UE capability, 2 FDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 2 TDD E-UTRA carriers.
In addition to the requirements defined above, the UE shall be capable of monitoring a total of at least 5 carrier
frequency layers, which include one serving carrier frequency and any of the above defined combination of E-UTRA
FDD inter-frequency and E-UTRA TDD inter-frequency layers.
8.15.2.2 E-UTRAN intra frequency measurements by UE category M2 with CE mode
A
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 cell list containing physical layer cell identities.
During the RRC_CONNECTED state the UE shall continuously measure identified intra frequency cells and
additionally search for and identify new intra frequency cells.
8.15.2.2.1 E-UTRAN FDD intra frequency measurements
8.15.2.2.1.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify and measure a new detectable FDD intra frequency cell
according to requirements in Table 8.15.2.2.1.1-1 when SCH Ês/Iot >= -6 dB
Table 8.15.2.2.1.1-1: Requirement on cell identification delay and measurement delay for FDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M2) Measurement delay (Tmeasure_intra_UE cat M2)
0 1.44 * Kintra_M2_NC seconds 480 * Kintra_M2_NC ms
1 2.88 * Kintra_M2_NC seconds 960 * Kintra_M2_NC ms
Kintra_M2_NC = 1 / X * 100 where X is a signalled RRC parameter TBD [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 374 ETSI TS 136 133 V14.3.0 (2017-04)
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M2. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.15.2.2.1.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP and
RSRQ measurement of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.2.1.1.1 Measurement Reporting Requirements
8.15.2.2.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.2.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.2.1.1.1.3.
8.15.2.2.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat M2_NC
defined in Clause 8.15.2.2.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_NC defined in clause 8.15.2.2.1.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period_UE cat M2, Intra provided the timing to that
cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.2.2.1.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra_UE cat
M2_NC as shown in table 8.15.2.2.1.2-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 375 ETSI TS 136 133 V14.3.0 (2017-04)
When eDRX_CONN is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M2_NC as shown in table 8.15.2.2.1.2-1A.
Table 8.15.2.2.1.2-1: Requirement to identify a newly detectable FDD intrafrequency cell
Gap pattern DRX cycle Tidentify_intra_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 ≤0.04 1.44 * Kintra_M2_NC
(Note 1)
0.04<DRX- Note 2 (40 *
cycle≤0.08 Kintra_M2_NC)
0.128 3.2 (25 *
Kintra_M2_NC)
0.128<DRX- Note 2(20 *
cycle≤2.56 Kintra_M2_NC)
1 <0.128 2.88 * Kintra_M2_NC
(Note 1)
0.128 3.2 * Kintra_M2_NC (25)
0.128<DRX- Note 2(20 *
cycle≤2.56 Kintra_M2_NC)
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.2.1.2-1A: Requirement to identify a newly detectable FDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (20 * Kintra_M2_NC)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.14-1 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M2.
When DRX is used, Tmeasure_intra_UE cat M2_NC is as specified in table 8.15.2.2.1.2-2. When eDRX_CONN is used,
Tmeasure_intra_UE cat M2_NC is as specified in table 8.15.2.2.1.2-3. The UE shall be capable of performing RSRP and RSRQ
measurements for 6 identified-intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of Tmeasure_intra_UE cat M2.
Table 8.15.2.2.1.2-2: Requirement to measure FDD intrafrequency cells
Gap pattern DRX cycle Tmeasure_intra_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 <0.128 0.48 * Kintra_M2_NC
(Note1)
0.128≤DRX- Note 2 (5 *
cycle≤2.56 Kintra_M2_NC)
1 <0.256 0.960 * Kintra_M2_NC
(Note 1)
0.256≤DRX- Note 2 (*Kintra_M2_NC)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 376 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.2.2.1.2-3: Requirement to measure FDD intrafrequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M2_NC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kintra_M2_NC)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.2.1.2.1 Measurement Reporting Requirements
8.15.2.2.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.2.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.2.1.2.1.3.
8.15.2.2.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra, UE cat M2
defined in Clause 8.15.2.2.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_NC defined in clause 8.15.2.2.1.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M2_NC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.2.2.2 E-UTRAN intra frequency measurements for HD-FDD
8.15.2.2.2.1 E-UTRAN intra frequency measurements when no DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.15.2.2.1.1 also apply for this section provided the following conditions are met:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 377 ETSI TS 136 133 V14.3.0 (2017-04)
- at least downlink subframe # 0 or downlink subframe # 5 per radio frame of an intra-frequency cell to be
identified by the UE is available at the UE over Tidentify_intra_UE cat M2;
- at least one downlink subframe per radio frame of measured cell is available at the UE for RSRP measurement
assuming measured cell is identified cell over Tmeasure_intra_UE cat M2.
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2 for a corresponding Band
8.15.2.2.2.2 E-UTRAN intra frequency measurements when DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
When DRX is in use the UE shall be able to identify a new detectable HD-FDD intra frequency cell within
Tidentify_intra_UE cat M2_NC as shown in table 8.15.2.2.2.2-1.
When eDRX_CONN is in use, the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M2_NC as shown in table 8.15.2.2.2.2-1A.
Table 8.15.2.2.2.2-1: Requirement to identify a newly detectable HD-FDD intrafrequency cell
Gap pattern DRX cycle Tidentify_intra_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 ≤0.04 1.44 * Kintra_M2_NC
(Note 1)
0.04<DRX- Note 2 (40 *
cycle≤0.08 Kintra_M2_NC)
0.128 3.2 (32 *
Kintra_M2_NC)
0.128<DRX- Note 2(25 *
cycle≤2.56 Kintra_M2_NC)
1 ≤0.08 2.88 * Kintra_M2_NC
(Note 1)
0.128 3.2 (32 *
Kintra_M2_NC)
0.128<DRX- Note 2(25 *
cycle≤2.56 Kintra_M2_NC)
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.2.2.2-1A: Requirement to identify a newly detectable HD-FDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (25 * Kintra_M2_NC)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M2.
When DRX is used, Tmeasure_intra_UE cat M2_NC is as specified in table 8.15.2.2.2.2-2. When eDRX_CONN is used,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 378 ETSI TS 136 133 V14.3.0 (2017-04)
Tmeasure_intra_UE cat M2_NC is as specified in table 8.15.2.2.2.2-3. The UE shall be capable of performing RSRP and RSRQ
measurements for 6 identified-intra-frequency cells, and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of Tmeasure_intra_UE cat M2.
Table 8.15.2.2.2.2-2: Requirement to measure HD-FDD intrafrequency cells
Gap pattern DRX cycle Tmeasure_intra_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 <0.08 0.48 * Kintra_M2_NC
(Note 1)
0.08≤DRX- Note 2 (7 *
cycle≤0.16 Kintra_M2_NC)
0.16<DRX- Note 2(5 *
cycle≤2.56 Kintra_M2_NC)
1 <0.16 0.96 * Kintra_M2_NC
(Note 1)
DRX- 1.12 * Kintra_M2_NC (7
cycle=0.16 * Kintra_M2_NC)
0.16<DRX- Note 2(5 *
cycle≤2.56 Kintra_M2_NC)
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.2.2.2-3: Requirement to measure HD-FDD intrafrequency cells when eDRX_CONN cycle
is used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kintra_M2_NC)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.2.2.2.1 Measurement Reporting Requirements
8.15.2.2.2.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.2.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.2.2.2.1.3.
8.15.2.2.2.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 379 ETSI TS 136 133 V14.3.0 (2017-04)
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat
M2_NC defined in Clause 8.15.2.2.2.2 When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_NC defined in clause 8.15.2.2.2.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M2_NC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.2.2.3 E-UTRAN TDD intra frequency measurements
8.15.2.2.3.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use, the UE shall be able to identify and measure a new detectable TDD intra frequency cell
according to requirements in Table 8.15.2.2.3.1-1 when SCH Ês/Iot >= -6 dB
Table 8.15.2.2.3.1-1: Requirement on cell identification delay and measurement delay for TDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M2) Measurement delay (Tmeasure_intra_UE cat M2)
0 1.44 * Kintra seconds 480 * Kintra_M2_NC ms
1 2.88 * Kintra seconds 960 * Kintra_M2_NC ms
Kintra = 1 / X * 100 where X is a signalled RRC parameter TBD [2].
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M2. If higher layer filtering is used, an additional cell identification delay can be
expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.15.2.2.3.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP and
RSRQ measurements of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQmeasurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.2.3.1.1 Measurement Reporting Requirements
8.15.2.2.3.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.2.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 380 ETSI TS 136 133 V14.3.0 (2017-04)
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.2.3.1.1.3.
8.15.2.2.3.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat M2_NC
defined in Clause 8.15.2.2.3.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_NC defined in clause 8.15.2.2.3.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period Intra_UE cat M2_NC provided the timing to that
cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.2.2.3.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within Tidentify_intra_ UE
catM2 as shown in table 8.15.2.2.3.2-1.
When eDRX_CONN is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
Tidentify_intra_UE cat M2_NC as shown in table 8.15.2.2.3.2-1A.
Table 8.15.2.2.3.2-1: Requirement to identify a newly detectable TDD intrafrequency cell
Gap pattern DRX cycle Tidentify_intra_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 ≤0.04 1.44 * Kintra_M2_NC
(Note 1)
0.04<DRX- Note 2 (40 *
cycle≤0.08 Kintra_M2_NC)
0.128 3.2 * Kintra_M2_NC (25
* Kintra_M2_NC)
0.128<DRX- Note 2(20 *
cycle≤2.56 Kintra_M2_NC)
1 <0.128 2.88 * Kintra_M2_NC
(Note 1)
0.128 3.2 * Kintra_M2_NC (25
* Kintra_M2_NC)
0.128<DRX- Note 2(20 *
cycle≤2.56 Kintra_M2_NC)
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 381 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.2.2.3.2-1A: Requirement to identify a newly detectable TDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (20 * Kintra_M2_NC)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M2.
When DRX is used, Tmeasure_intra_UE cat M2_NC is as specified in table 8.15.2.2.3.2-2. When eDRX_CONN is used,
Tmeasure_intra_UE cat M2_NC is as specified in table 8.15.2.2.3.2-3. The UE shall be capable of performing RSRP and RSRQ
measurements for 6 identified intra-frequency cells and the UE physical layer shall be capable of reporting
measurements to higher layers with the measurement period of Tmeasure_intra_UE cat M2.
Table 8.15.2.2.3.2-2: Requirement to measure TDD intra frequency cells
Gap pattern DRX cycle Tmeasure_intra_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 <0.128 0.48 * Kintra_M2_NC
(Note 1)
0.128≤DRX- Note 2 (5 *
cycle≤2.56 Kintra_M2_NC)
1 <0.256 0.96 * Kintra_M2_NC
(Note 1)
0.256≤DRX- Note 2 (5 *
cycle≤2.56 Kintra_M2_NC)
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.2.3.2-3: Requirement to measure TDD intra frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kintra_M2_NC)
Note: Time depends upon the eDRX_CONN cycle in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.2.3.2.1 Measurement Reporting Requirements
8.15.2.2.3.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.2.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 382 ETSI TS 136 133 V14.3.0 (2017-04)
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.2.3.2.1.3.
8.15.2.2.3.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat
M2_NC defined in Clause 8.15.2.2.3.2. When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_NC defined in clause 8.15.2.2.3.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M2_NC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.2.3 E-UTRAN inter frequency measurements by UE category M2 with CE mode
A
The UE shall be able to identify new inter-frequency cells and perform RSRP and RSRQ measurements of identified
inter-frequency cells if carrier frequency information is provided by the PCell, even if no explicit neighbour list with
physical layer cell identities is provided. During the RRC_CONNECTED state the UE shall continuously measure
identified inter frequency cells and additionally search for and identify new inter frequency cells.
8.15.2.3.1 E-UTRAN FDD - FDD inter frequency measurements
8.15.2.3.1.1 E-UTRAN FDD - FDD inter frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify and measure a new detectable FDD inter-frequency cell
according to requirements in Table 8.15.2.3.1.1-1 when SCH Ês/Iot >= -6 dB
Table 8.15.2.3.1.1-1: Requirement on cell identification delay and measurement delay for FDD
interfrequency cell
Gap pattern ID Cell identification delay (Tidentify_inter_UE cat M2_NC) Measurement delay (Tmeasure_inter_UE cat M2_NC_NC)
0 1.44 * Kinter_M2 seconds 480 * Kinter_M2 ms
1 2.88 * Kinter_M2 seconds 960 * Kinter_M2 ms
N freq *100
K Inter_M2 =
(100 - X)
where X is signalled by the RRC parameter TBD [2].
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 383 ETSI TS 136 133 V14.3.0 (2017-04)
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_inter_UE cat M2_NC. If higher layer filtering is used, an additional cell identification delay can
be expected.
In the RRC_CONNECTED state the measurement period for inter frequency measurements is according to Table
8.15.2.3.1.1-1. When measurement gaps are scheduled for FDD inter frequency measurements, or the UE supports
capability of conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP
and RSRQ measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.x.1 and 9.1.x.2.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 4 inter-frequency cells per FDD
inter-frequency for up to 2 FDD inter-frequencies and the UE physical layer shall be capable of reporting RSRP and
RSRQ measurements to higher layers with the measurement period defined in Table 8.15.2.3.1.1-1.
8.15.2.3.1.1.1 Measurement Reporting Requirements
8.15.2.3.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.3.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.3.1.1.1.3.
8.15.2.3.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify inter_UE cat M2_NC
defined in Clause 8.15.2.3.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_NC defined in clause 8.15.2.3.1.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period_UE cat M2_NC, Inter provided the timing to
that cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.2.3.1.2 E-UTRAN inter frequency measurements when DRX is used
When DRX is in use and when measurement gaps are scheduled, or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_NC as shown in table 8.15.2.3.1.2-1.
When eDRX_CONN is in use and when measurement gaps are scheduled, or the UE supports capability of conducting
such measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_NC as shown in table 8.15.2.3.1.2-1A.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 384 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.2.3.1.2-1: Requirement to identify a newly detectable FDD interfrequency cell
Gap pattern DRX cycle Tidentify_inter_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 ≤0.04 1.44 * Kinter_M2 (Note
1)
0.04<DRX- Note 2 (40 *
cycle≤0.08 Kinter_M2)
0.128 3.2 * Kinter_M2 (25 *
Kinter_M2)
0.128<DRX- Note 2(20 *
cycle≤2.56 Kinter_M2)
1 <0.128 2.88 * Kinter_M2 (Note
1)
0.128 3.2 * Kinter_M2 (25 *
Kinter_M2)
0.128<DRX- Note 2(20 *
cycle≤2.56 Kinter_M2)
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.3.1.2-1A: Requirement to identify a newly detectable FDD interfrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_inter_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (20 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.14-1 for a corresponding Band
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP and RSRQ measurements of at
least 4 inter-frequency cells per FDD inter-frequency and the UE physical layer shall be capable of reporting RSRP and
RSRQ to higher layers with the measurement period Tmeasure_inter_UE cat M2_NC, either measurement gaps are scheduled or
the UE supports capability of conducting such measurements without gaps. When DRX is used, Tmeasure_inter_UE cat M2_NC is
as defined in Table 8.15.2.3.1.2-2, and when eDRX_CONN is in use, Tmeasure_inter_UE cat M2_NC is as defined in Table
8.15.2.3.1.2-3.
Table 8.15.2.3.1.2-2: Requirement to measure FDD interfrequency cells
Gap pattern DRX cycle Tmeasure_inter_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 <0.128 0.48 * Kinter_M2 cat
M2_NC (Note 1)
0.128≤DRX- Note 2 (5 * Kinter_M2)
cycle≤2.56
1 <0.256 0.960 * Kinter_M2 cat
M2_NC (Note 1)
0.256≤DRX- Note 2 (5 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 385 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.2.3.1.2-3: Requirement to measure FDD interfrequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_inter_UE cat M2_NC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.3.1.2.1 Measurement Reporting Requirements
8.15.2.3.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.3.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.3.1.2.1.3.
8.15.2.3.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_inter, UE cat
M2_NC defined in Clause 8.15.2.3.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_NC defined in clause 8.15.2.3.1.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_inter_UE cat M2_NC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.2.3.2 E-UTRAN inter-frequency measurements for HD-FDD
8.15.2.3.2.1 E-UTRAN inter-frequency measurements when no DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.15.2.3.1.1 also apply for this section provided the following conditions are met:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 386 ETSI TS 136 133 V14.3.0 (2017-04)
- at least downlink subframe # 0 or downlink subframe # 5 per radio frame of an inter-frequency cell to be
identified by the UE is available at the UE over Tidentify_inter_UE cat M2_NC;
- at least one downlink subframe per radio frame of measured cell is available at the UE for RSRP measurement
assuming measured cell is identified cell over Tmeasure_inter_UE cat M2_NC.
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2 for a corresponding Band
8.15.2.3.2.2 E-UTRAN inter frequency measurements when DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
When DRX is in use and when measurement gaps are scheduled, or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_NC as shown in table 8.15.2.3.2.2-1.
When eDRX_CONN is in use and when measurement gaps are scheduled, or the UE supports capability of conducting
such measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_NC as shown in table 8.15.2.3.2.2-1A.
Table 8.15.2.3.2.2-1: Requirement to identify a newly detectable HD-FDD interfrequency cell
Gap pattern DRX cycle Tidentify_inter_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 ≤0.04 1.44 * Kinter_M2
(Note1)
0.04<DRX- Note 2 (40 *
cycle≤0.08 Kinter_M2)
0.128 3.2 * Kinter_M2 (32 *
Kinter_M2)
0.128<DRX- Note 2(25 *
cycle≤2.56 Kinter_M2)
1 ≤0.08 2.88 * Kinter_M2
(Note1)
0.128 3.2 * Kinter_M2 (32 *
Kinter_M2)
0.128<DRX- Note 2(25 *
cycle≤2.56 Kinter_M2)
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.3.2.2-1A: Requirement to identify a newly detectable HD-FDD interfrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_inter_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (25 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-2 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 387 ETSI TS 136 133 V14.3.0 (2017-04)
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP and RSRQ measurements of at
least 4 inter-frequency cells per FDD inter-frequency and the UE physical layer shall be capable of reporting RSRP and
RSRQ to higher layers with the measurement period Tmeasure_inter_UE cat M2_NC, either measurement gaps are scheduled or
the UE supports capability of conducting such measurements without gaps. When DRX is used, Tmeasure_inter_UE cat M2_NC is
as defined in Table 8.15.2.3.2.2-2, and when eDRX_CONN is in use, Tmeasure_inter_UE cat M2_NC is as defined in Table
8.15.2.3.2.2-3.
Table 8.15.2.3.2.2-2: Requirement to measure HD-FDD interfrequency cells
Gap pattern DRX cycle Tmeasure_inter_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 <0.08 0.48 * Kinter_M2
(Note 1)
0.08≤DRX- Note 2 (7 * Kinter_M2)
cycle≤0.16
0.16<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
1 <0.16 0.96 * Kinter_M2
(Note 1)
DRX- 1.12 * Kinter_M2 (7 *
cycle=0.16 Kinter_M2)
0.16<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.3.2.2-3: Requirement to measure HD-FDD interfrequency cells when eDRX_CONN cycle
is used
eDRX_CONN cycle length (s) Tmeasure_inter_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.3.2.2.1 Measurement Reporting Requirements
8.15.2.3.2.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.2.3.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.3.2.2.1.3.
8.15.2.3.2.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 388 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_inter_UE cat
M2_NC defined in Clause 8.15.2.3.2.2 When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_NC defined in clause 8.15.2.3.2.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_inter_UE cat M2_NC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.2.3.3 E-UTRAN TDD inter frequency measurements
8.15.2.3.3.1 E-UTRAN inter frequency measurements when no DRX is used
When no DRX is in use and when measurement gaps are scheduled, or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify and measure a new detectable TDD inter frequency cell
according to requirements in Table 8.15.2.3.3.1-1 when SCH Ês/Iot >= -6 dB
Table 8.15.2.3.3.1-1: Requirement on cell identification delay and measurement delay for TDD
interfrequency cell
Gap pattern ID Cell identification delay (Tidentify_inter_UE cat M2_NC) Measurement delay (Tmeasure_inter_UE cat M2_NC)
0 1.44* Kinter_M2 seconds 480* Kinter_M2 ms
1 2.88* Kinter_M2 seconds 960* Kinter_M2 ms
N freq *100
K Inter_M2 =
(100 - X)
where X is signalled by the RRC parameter TBD [2].
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band.
When measurement gaps are scheduled for TDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP and RSRQ to
higher layers with measurement accuracy as specified in sub-clauses 9.1.x.1 and 9.1.x.2with measurement period
(Tmeasure_inter_UE cat M2_NC) given by table 8.15.2.3.3.1-1:
The UE shall be capable of performing RSRP and RSRQ measurements of at least 4 inter-frequency cells per TDD
inter-frequency and the UE physical layer shall be capable of reporting RSRP and RSRQ measurements to higher layers
with the measurement period Tmeasure_inter_UE cat M2_NC.
8.15.2.3.3.1.1 Measurement Reporting Requirements
8.15.2.3.3.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 389 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.2.3.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.3.3.1.1.3.
8.15.2.3.3.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify inter_UE cat M2_NC
defined in Clause 8.15.2.3.3.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_NC defined in clause 8.15.2.3.3.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period Inter_UE cat M2_NC provided the timing to that
cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.2.3.3.2 E-UTRAN inter frequency measurements when DRX is used
When DRX is in use and when DRX or eDRX_CONN is in use, either measurement gaps are scheduled or the UE
supports capability of conducting such measurements without gaps, the UE shall be able to identify a new detectable
TDD inter frequency cell within Tidentify_inter_ UE catM2 as shown in table 8.15.2.3.3.2-1.
When eDRX_CONN is in use the UE shall be able to identify a new detectable TDD inter frequency cell within
Tidentify_inter_UE cat M2_NC as shown in table 8.15.2.3.3.2-1A.
Table 8.15.2.3.3.2-1: Requirement to identify a newly detectable TDD interfrequency cell
Gap pattern DRX cycle Tidentify_inter_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 ≤0.04 1.44* Kinter_M2 (Note
1)
0.04<DRX- Note 2 (40*
cycle≤0.08 Kinter_M2)
0.128 3.2* Kinter_M2 (25*
Kinter_M2)
0.128<DRX- Note 2(20* Kinter_M2)
cycle≤2.56
1 <0.128 2.88* Kinter_M2 (Note
1)
0.128 3.2* Kinter_M2 (25*
Kinter_M2)
0.128<DRX- Note 2(20* Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 390 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.2.3.3.2-1A: Requirement to identify a newly detectable TDD interfrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_inter_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (20* Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-1 for a corresponding Band
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP and RSRQ measurements of at
least 4 inter-frequency cells per TDD inter-frequency for up to 3 TDD inter-frequencies and the UE physical layer shall
be capable of reporting RSRP and RSRQ measurements to higher layers with the measurement period Tmeasure_inter_UE cat
M2_NC, either measurement gaps are scheduled or the UE supports capability of conducting such measurements without
gaps. When DRX is in use, Tmeasure_inter_UE cat M2_NC is as defined in Table 8.15.2.3.3.2-2, and when eDRX_CONN is in
use, Tmeasure_inter_UE cat M2_NC is as defined in Table 8.15.2.3.3.2-3.
Table 8.15.2.3.3.2-2: Requirement to measure TDD inter frequency cells
Gap pattern DRX cycle Tmeasure_inter_UE cat
ID length (s) M2_NC (s) (DRX
cycles)
0 <0.128 0.48* Kinter_M2 (Note
1)
0.128≤DRX- Note 2 (5* Kinter_M2)
cycle≤2.56
1 <0.256 0.96* Kinter_M2 (Note
1)
0.256≤DRX- Note 2 (5* Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the
DRX cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.2.3.3.2-3: Requirement to measure TDD inter frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_inter_UE cat M2_NC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5* Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.2.3.3.2.1 Measurement Reporting Requirements
8.15.2.3.3.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 391 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.2.3.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.2.3.3.2.1.3.
8.15.2.3.3.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_inter_UE cat
M2_NC defined in Clause 8.15.2.3.3.2. When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_NC defined in clause 8.15.2.3.3.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_inter_UE cat M2_NC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.2.4 E-UTRAN E-CID Measurements Requirements for UE category M2 with CE
mode A
8.15.2.4.1 Intra-frequency FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeA
8.15.2.4.1.1 Introduction
The requirements in section 8.15.2.4.1 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN FDD intra-frequency RSRP and RSRQ
measurements [24].
8.15.2.4.1.2 Measurement Requirements
The requirements in section 8.15.a1.b1.1 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.2.4.1.3.
8.15.2.4.1.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.1 and 9.1.x.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 392 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.2.4.2 Intra-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE
in CEModeA
8.15.2.4.2.1 Introduction
The requirements in section 8.15.2.4.2 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN HD-FDD intra-frequency RSRP and
RSRQ measurements [24].
8.15.2.4.2.2 Measurement Requirements
The requirements in section 8.15.a1.b1.2 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.2.4.2.3.
8.15.2.4.2.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.1 and 9.1.x.2.
8.15.2.4.3 Intra-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeA
8.15.2.4.3.1 Introduction
The requirements in section 8.15.2.4.3 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN TDD intra-frequency RSRP and RSRQ
measurements [24].
8.15.2.4.3.2 Measurement Requirements
The requirements in section 8.15.a1.b1.3 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.2.4.3.3.
8.15.2.4.3.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.1 and 9.1.x.2.
8.15.2.4.4 Inter-frequency FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeA
8.15.2.4.4.1 Introduction
The requirements in section 8.15.2.4.4 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN FDD inter-frequency RSRP and RSRQ
measurements [24].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 393 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.2.4.4.2 Measurement Requirements
The requirements in section 8.15.a2.b2.1 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.2.4.4.3.
8.15.2.4.4.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.1 and 9.1.x.2.
8.15.2.4.5 Inter-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE
in CEModeA
8.15.2.4.5.1 Introduction
The requirements in section 8.15.2.4.5 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN HD-FDD inter-frequency RSRP and
RSRQ measurements [24].
8.15.2.4.5.2 Measurement Requirements
The requirements in section 8.15.a2.b2.2 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.2.4.5.3.
8.15.2.4.5.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.1 and 9.1.x.2.
8.15.2.4.6 Inter-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeA
8.15.2.4.6.1 Introduction
The requirements in section 8.15.2.4.6 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN TDD inter-frequency RSRP and RSRQ
measurements [24].
8.15.2.4.6.2 Measurement Requirements
The requirements in section 8.15.a2.b2.3 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.2.4.6.3.
8.15.2.4.6.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 394 ETSI TS 136 133 V14.3.0 (2017-04)
Reported RSRP and RSRQ measurements contained in periodically triggered
measurement reports shall meet the requirements in section 9.1.x.1
and 9.1.x.2.8.15.3 Requirements for UE category M2 with CE
mode B
The UE category M2 applicability of the requirements in subclause 8.15.3 is defined in Section 3.6. The requirements in
this section are applicable for UE category M2 configured with CE mode B. The requirements defined in clause 8.15.3
apply provided the following conditions are met:
- UE is configured with measurement gap according to any of gap patterns defined in Table 8.1.2.1-1.
8.15.3.1 Maximum allowed layers for multiple monitoring for UE category M2 with CE
mode B
The UE UE category M2 configured with CE mode A shall be capable of monitoring at least:
- Depending on UE capability, 2 FDD E-UTRA inter-frequency carriers, and
- Depending on UE capability, 2 TDD E-UTRA carriers.
In addition to the requirements defined above, the UE shall be capable of monitoring a total of at least 5 carrier
frequency layers, which include one serving carrier frequency and any of the above defined combination of E-UTRA
FDD inter-frequency and E-UTRA TDD inter-frequency layers.
8.15.3.2 E-UTRAN intra frequency measurements by UE category M2 with CE mode
B
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 cell list containing physical layer cell identities.
During the RRC_CONNECTED state the UE shall continuously measure identified intra frequency cells and
additionally search for and identify new intra frequency cells.
8.15.3.2.1 E-UTRAN FDD intra frequency measurements
8.15.3.2.1.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify and measure a new detectable FDD intra frequency cell
according to requirements in Table 8.15.3.2.1.1-1 provided that additional conditions table 8.15.3.2.1.1-2 is met.
Table 8.15.3.2.1.1-1: Requirement on cell identification delay and measurement delay for FDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M2_EC) Measurement delay (Tmeasure_intra_UE cat M2_EC)
0 320.8 * Kintra_M2 s 800 * Kintra_M2 ms
1 321.6 * Kintra_M2 s 1600 * Kintra_M2 ms
Table 8.15.3.2.1.1-2: Conditions on SCH Ês/Iot for cell identification delay and measurement delay for
FDD intrafrequency cell
SCH Ês/Iot of already Neighouring cell SCH Cell identification delay Measurement delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M2_EC) (Tmeasure_intra_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table As defined in table
8.15.3.2.1.1-1 8.15.3.2.1.1-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
Q1≥-6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 395 ETSI TS 136 133 V14.3.0 (2017-04)
Kintra_M2 = 1 / X * 100 where X is signalled by the RRC parameter TBD [2].A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.3 and 9.1.x.4 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M2_EC. If higher layer filtering is used, an additional cell identification delay can
be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.15.3.2.1.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP and
RSRQ measurements of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3 and 9.1.x.4.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.5.
8.15.3.2.1.1.1 Measurement Reporting Requirements
8.15.3.2.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1. 17.3 and 9.1.x.4.
8.15.3.2.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in clause
8.15.3.2.1.1.1.3.
8.15.3.2.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.3 and 9.1.x.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat M2_EC
defined in Clause 8.15.3.2.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_EC defined in clause 8.15.3.2.1.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period_UE cat M2_EC, Intra provided the timing to
that cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.3.2.1.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable FDD intra frequency cell within Tidentify_intra_UE cat
as shown in table 8.15.3.2.1.2-1 provided that additional conditions Table 8.15.3.2.1.2-1A is met.
M2_EC
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 396 ETSI TS 136 133 V14.3.0 (2017-04)
When eDRX_CONN is in use the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M2_EC as shown in table 8.15.3.2.1.2-1B.
Table 8.15.3.2.1.2-1: Requirement to identify a newly detectable FDD intrafrequency cell
Gap pattern ID DRX cycle Tidentify_intra_UE cat M2_EC
length (s) (s) (DRX cycles)
0 ≤0.64 320.8 * Kintra_M2 (Note 1)
0.64< DRX- Note 2(400 * Kintra_M2)
cycle≤2.56
1 DRX-cycle ≤ 321.6 * Kintra_M2 (Note
0.640 1)
0.64< DRX- Note 2(400 * Kintra_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.3.2.1.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable FDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.2.1.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.2.1.2-1B: Requirement to identify a newly detectable FDD intrafrequency cell when
eDRX_CONN is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400 * Kintra_M2)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.3 and 9.1.x.4 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M2_EC.
When DRX is used, Tmeasure_intra_UE cat M2_EC is as specified in table 8.15.3.2.1.2-2 provided that additional conditions table
8.15.3.2.1.2-3 is met. When eDRX_CONN is used, Tmeasure_intra_UE cat M2_EC is as specified in table 8.15.3.2.1.2-4. The UE
shall be capable of performing RSRP and RSRQ measurements for 6 identified-intra-frequency cells, and the UE
physical layer shall be capable of reporting measurements to higher layers with the measurement period of
Tmeasure_intra_UE cat M2_EC.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 397 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.2.1.2-2: Requirement to measure FDD intrafrequency cells
Gap pattern DRX cycle Tmeasure_intra_UE cat
ID length (s) M2_EC (s) (DRX
cycles)
0 ≤0.16 0.8 * Kintra_M2 (Note
1)
0.16<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
1 ≤0.32 1.6 * Kintra_M2 (Note
1)
0.32<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX
cycle in use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.3.2.1.2-3: Conditions on SCH Ês/Iot to measure FDD intrafrequency cell
SCH Ês/Iot of serving Target cell SCH Ês/Iot: Q2 Measurement delay
cell: Q1 (Tmeasure_intra_UE cat M2_EC)
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.2.1.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.2.1.2-4: Requirement to measure FDD intrafrequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kintra_M2)
NOTE: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3 and 9.1.x.4.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.5.
8.15.3.2.1.2.1 Measurement Reporting Requirements
8.15.3.2.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
8.15.3.2.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in clause
8.15.3.2.1.2.1.3.
8.15.3.2.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.3 and 9.1.x.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 398 ETSI TS 136 133 V14.3.0 (2017-04)
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra, UE cat
M2_EC defined in Clause 8.15.3.2.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_EC defined in clause 8.15.3.2.1.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M2_EC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.3.2.2 E-UTRAN intra frequency measurements for HD-FDD
8.15.3.2.2.1 E-UTRAN intra frequency measurements when no DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.15.3.2.1.1 also apply for this section provided the following conditions are met:
- at least downlink subframe # 0 and downlink subframe # 5 per radio frame of an intra-frequency cell to be
identified by the UE is available at the UE over Tidentify_intra_UE cat M2_EC;
- at least two consecutive downlink subframe per radio frame of measured cell is available at the UE for RSRP
measurements assuming measured cell is identified cell over Tmeasure_intra_UE cat M2_EC.
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-4
8.15.3.2.2.2 E-UTRAN intra frequency measurements when DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
When DRX is in use the UE shall be able to identify a new detectable HD-FDD intra frequency cell within
Tidentify_intra_UE cat M2_EC as shown in table 8.15.3.2.2.2-1 provided that additional conditions table 8.15.3.2.2.2-1A is met.
When eDRX_CONN is in use, the UE shall be able to identify a new detectable FDD intra frequency cell within
Tidentify_intra_UE cat M2_EC as shown in table 8.15.3.2.2.2-1B.
Table 8.15.3.2.2.2-1: Requirement to identify a newly detectable HD-FDD intrafrequency cell
Gap pattern ID DRX cycle Tidentify_intra_UE cat M2_EC (s)
length (s) (DRX cycles)
0 ≤0.64 320.8 * Kintra_M2 (Note1)
0.64<DRX- Note2(400 * Kintra_M2)
cycle≤2.56
1 <0.64 321.6 * Kintra_M2 (Note1)
0.64≤DRX- Note2(400 * Kintra_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 399 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.2.2.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable HD-FDD intrafrequency
cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.2.2.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥-6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.2.2.2-1B: Requirement to identify a newly detectable HD-FDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400 * Kintra_M2)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.3 and 9.1.x.4 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-4 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M2_EC.
When DRX is used, Tmeasure_intra_UE cat M2_EC is as specified in table 8.15.3.2.2.2-2 provided that additional conditions
Table 8.15.3.2.2.2-3 is met. When eDRX_CONN cycle is used, Tmeasure_intra_UE cat M2_EC is as specified in table
8.15.3.2.2.2-4. The UE shall be capable of performing RSRP and RSRQ measurements for 6 identified-intra-frequency
cells, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement
period of Tmeasure_intra_UE cat M2_EC.
Table 8.15.3.2.2.2-2: Requirement to measure HD-FDD intrafrequency cells
Gap pattern ID DRX cycle Tmeasure_intra_UE cat M2_EC
length (s) (s) (DRX cycles)
0 <0.128 0.8 * Kintra (Note 1)
0.128≤DRX- Note 2 (7 * Kintra_M2)
cycle≤0.16
0.16<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
1 ≤0.32 1.6 * Kintra (Note1)
0.32<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 400 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.2.2.2-3: Conditions on SCH Ês/Iot to measure HD-FDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Measurement delay
identified cell including Ês/Iot: Q2 (Tmeasure_intra_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.2.2.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.2.2.2-4: Requirement to measure HD-FDD intrafrequency cells when eDRX_CONN cycle
is used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M2_EC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kintra_M2)
NOTE: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3 and 9.1.x.4.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.5.
8.15.3.2.2.2.1 Measurement Reporting Requirements
8.15.3.2.2.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
8.15.3.2.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in clause
8.15.3.2.2.2.1.3.
8.15.3.2.2.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurements contained in event triggered measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat
M2_EC defined in Clause 8.15.3.2.2.2 When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_EC defined in clause 8.15.3.2.2.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M2_EC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 401 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.2.3 E-UTRAN TDD intra frequency measurements
8.15.3.2.3.1 E-UTRAN intra frequency measurements when no DRX is used
When no DRX is in use the UE shall be able to identify and measure a new detectable TDD intra frequency cell
according to requirements in Table 8.15.3.2.3.1-1provided that additional conditions Table 8.15.3.2.3.1-2 is met.
Table 8.15.3.2.3.1-1: Requirement on cell identification delay and measurement delay for TDD
intrafrequency cell
Gap pattern ID Cell identification delay (Tidentify_intra_UE cat M2_EC) Measurement delay (Tmeasure_intra_UE cat M2_EC)
0 320.8 * Kintra_M2 s 800 * Kintra_M2 ms Note1
[1600 * Kintra_M2 ms] Note2
1 321.6 * Kintra_M2 s 1600 * Kintra_M2 msNote1
[3200 * Kintra_M2 ms] Note2
Note 1: Under TDD UL/DL configuration other than 0.
Note 2: Under TDD UL/DL configuration 0.
Kintra_M2 = 1 / X * 100 where X is signalled by the RRC parameter TBD [2].
Table 8.15.3.2.3.1-2: Conditions on SCH Ês/Iot for cell identification delay and measurement delay for
TDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay Measurement delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M2_EC) (Tmeasure_intra_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table As defined in table
8.15.3.2.3.1-1 8.15.3.2.3.1-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.3 and 9.1.x.4 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_intra_UE cat M2_EC. If higher layer filtering is used, an additional cell identification delay
can be expected.
In the RRC_CONNECTED state the measurement period for intra frequency measurements is according to Table
8.15.3.2.3.1-1. When measurement gaps are activated the UE shall be capable of performing measurements for at least 6
cells. If the UE has identified more than 6 cells, the UE shall perform measurements but the reporting rate of RSRP and
RSRQ measurements of cells from UE physical layer to higher layers may be decreased.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3 and 9.1.x.4.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.5.
8.15.3.2.3.1.1 Measurement Reporting Requirements
8.15.3.2.3.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 402 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.2.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in clause
8.15.3.2.3.1.1.3.
8.15.3.2.3.1.1.3 Event Triggered Reporting
Reported RSRP measurement contained in event triggered measurement reports shall meet the requirements in sections
9.1.x.3 and 9.1.x.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify intra_UE cat M2_EC
defined in Clause 8.15.3.2.3.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_EC defined in clause 8.15.3.2.3.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period Intra_UE cat M2_EC provided the timing to that
cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.3.2.3.2 E-UTRAN intra frequency measurements when DRX is used
When DRX is in use the UE shall be able to identify a new detectable TDD intra frequency cell within Tidentify_intra_ UE cat
M2_EC as shown in table 8.15.3.2.3.2-1 provided that additional conditions table 8.15.3.2.3.2-1A is met.
When eDRX_CONN is in use the UE shall be able to identify a new detectable TDD intra frequency cell within
Tidentify_intra_UE cat M2_EC as shown in table 8.15.3.2.3.2-1B.
Table 8.15.3.2.3.2-1: Requirement to identify a newly detectable TDD intrafrequency cell
Gap pattern ID DRX cycle Tidentify_intra_UE cat M2_EC (s)
length (s) (DRX cycles)
0 DRX-cycle ≤ 0.64 320.8 * Kintra_M2 (Note 1)
0.64<DRX- Note 2(400 * Kintra_M2)
cycle≤2.56
1 DRX-cycle ≤ 0.64 321.6 * Kintra_M2 (Note 1)
0.64<DRX- Note 2(400 * Kintra_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 403 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.2.3.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable TDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_intra_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 <-6 As defined in table
8.15.3.2.3.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥-6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.2.3.2-1B: Requirement to identify a newly detectable TDD intrafrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_intra_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400 * Kintra_M2)
NOTE: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.x.3 and 9.1.x.4 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.14-3 for a corresponding Band
In the RRC_CONNECTED state the measurement period for intra frequency measurements is Tmeasure_intra_UE cat M2_EC.
When DRX is used, Tmeasure_intra_UE cat M2_EC is as shown in table 8.15.3.2.3.2-2 provided that additional conditions Table
8.15.3.2.3.2-3 is met. When eDRX_CONN is used, Tmeasure_intra_UE cat M2_EC is as shown in table 8.15.3.2.3.2-4. The UE
shall be capable of performing RSRP and RSRQ measurement for 6 identified intra-frequency cells and the UE physical
layer shall be capable of reporting measurements to higher layers with the measurement period of Tmeasure_intra_UE cat M2_EC.
Table 8.15.3.2.3.2-2: Requirement to measure TDD intra frequency cells
TDD Uplink- Gap pattern ID DRX cycle Tmeasure_intra_UE cat M2_EC
downlink length (s) (s) (DRX cycles)
configuration
Other than 0 0 ≤0.16 0.8 * Kintra_M2 (Note 1)
0.16<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
1 ≤0.32 1.6 * Kintra_M2 c (Note 1)
0.32<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
0 0 ≤0.32 [1.6] * Kintra_M2 cat (Note
1)
0.32<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
1 ≤0.64 [3.2] * Kintra_M2 (Note 1)
0.64<DRX- Note 2(5 * Kintra_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in use.
Note 2: Time depends upon the DRX cycle in use.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 404 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.2.3.2-3: Conditions on SCH Ês/Iot to measure TDD intrafrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Measurement delay
identified cell including Ês/Iot: Q2 (Tmeasure_intra_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.2.3.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.2.3.2-4: Requirement to measure TDD intra frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_intra_UE cat M2_EC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kintra_M2)
NOTE: Time depends upon the eDRX_CONN cycle in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3 and 9.1.x.4.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.5.
8.15.3.2.3.2.1 Measurement Reporting Requirements
8.15.3.2.3.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
8.15.3.2.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.3 and 9.1.x.4.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in clause
8.15.3.2.3.2.1.3.
8.15.3.2.3.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.3 and 9.1.x.4.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_intra_UE cat
M2_EC defined in Clause 8.15.3.2.3.2. When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_intra_UE cat M2_EC defined in clause 8.15.3.2.3.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_intra_UE cat M2_EC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 405 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.3 E-UTRAN inter frequency measurements by UE category M2 with CE Mode
B
The UE shall be able to identify new inter-frequency cells and perform RSRP and RSRQ measurements of identified
inter-frequency cells if carrier frequency information is provided by the PCell, even if no explicit neighbour list with
physical layer cell identities is provided. During the RRC_CONNECTED state the UE shall continuously measure
identified inter frequency cells and additionally search for and identify new inter frequency cells.
8.15.3.3.1 E-UTRAN FDD - FDD inter frequency measurements
8.15.3.3.1.1 E-UTRAN FDD - FDDinter frequency measurements when no DRX is used
When no DRX is in use and when measurement gaps are scheduled, or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify and measure a new detectable FDD inter-frequency cell
according to requirements in Table 8.15.3.3.1.1-1 when additional condition in Table 8.15.3.3.1.1-2 is met.
Table 8.15.3.3.1.1-1: Requirement on cell identification delay and measurement delay for FDD
interfrequency cell
Gap pattern ID Cell identification delay (Tidentify_inter_UE cat M2_EC) Measurement delay (Tmeasure_inter_UE cat M2_EC)
0 320.8 * Kinter_M2 s 800 * Kinter_M2 ms
1 321.6 * Kinter_M2 s 1600 * Kinter_M2 ms
N freq *100
K Inter_M2 =
(100 - X)
where X is signalled by the RRC parameter TBD [2].
Table 8.15.3.3.1.1-2: Conditions on SCH Ês/Iot for cell identification delay and measurement delay for
FDD interfrequency cell
SCH Ês/Iot of already Neighouring cell SCH Cell identification delay Measurement delay
identified cell including Ês/Iot: Q2 (Tidentify_inter_UE cat M2_EC) (Tmeasure_inter_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table As defined in table
8.15.3.1.1.1-1 8.15.3.1.1.1-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.x-1 for a corresponding Band.
Identification of a cell shall include detection of the cell and additionally performing a single measurement with
measurement period of Tmeasure_inter_UE cat M2_EC. If higher layer filtering is used, an additional cell identification delay can
be expected.
In the RRC_CONNECTED state the measurement period for inter frequency measurements is according to Table
8.15.3.3.1.1-1. When measurement gaps are scheduled for FDD inter frequency measurements, or the UE supports
capability of conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP
and RSRQ measurements to higher layers with measurement accuracy as specified in sub-clauses 9.1.x.1 and 9.1.x.2.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 4 inter-frequency cells per FDD
inter-frequency for up to 3 FDD inter-frequencies and the UE physical layer shall be capable of reporting RSRP and
RSRQ measurements to higher layers with the measurement period defined in Table 8.15.3.3.1.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 406 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.3.1.1.1 Measurement Reporting Requirements
8.15.3.3.1.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.3.3.1.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.3.3.1.1.1.3.
8.15.3.3.1.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the
measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a
delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty
is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send
the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify inter_UE cat M2_EC
defined in Clause 8.15.3.3.1.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_EC defined in clause 8.15.3.3.1.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period_UE cat M2_EC, Inter provided the timing to
that cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.3.3.1.2 E-UTRAN inter frequency measurements when DRX is used
When DRX is in use and when measurement gaps are scheduled, or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_EC as shown in table 8.15.3.3.1.2-1.
When eDRX_CONN is in use and when measurement gaps are scheduled, or the UE supports capability of conducting
such measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_EC as shown in table 8.15.3.3.1.2-1A.
Table 8.15.3.3.1.2-1: Requirement to identify a newly detectable FDD interfrequency cell
Gap pattern ID DRX cycle Tidentify_inter_UE cat M2_EC
length (s) (s) (DRX cycles)
0 ≤0.64 320.8 * Kinter_M2 (Note 1)
0.64< DRX- Note 2(400 * Kinter_M2)
cycle≤2.56
1 DRX-cycle ≤ 321.6 * Kinter_M2 (Note 1)
0.640
0.64< DRX- Note 2(400 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 407 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.3.1.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable FDD interfrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_inter_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.1.1.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.3.1.2-1B: Requirement to identify a newly detectable FDD interfrequency cell when
eDRX_CONN is used
eDRX_CONN cycle length (s) Tidentify_inter_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400 * Kinter)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex B.2.x-1 for a corresponding Band
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP and RSRQ measurements of at
least 4 inter-frequency cells per FDD inter-frequency and the UE physical layer shall be capable of reporting RSRP and
RSRQ to higher layers with the measurement period Tmeasure_inter_UE cat M2_EC, either measurement gaps are scheduled or
the UE supports capability of conducting such measurements without gaps. When DRX is used, Tmeasure_inter_UE cat M2_EC is
as defined in Table 8.15.3.3.1.2-2, and when eDRX_CONN is in use, Tmeasure_inter_UE cat M2_EC is as defined in Table
8.15.3.3.1.2-3.
Table 8.15.3.3.1.2-2: Requirement to measure FDD interfrequency cells
Gap pattern DRX cycle Tmeasure_inter_UE cat
ID length (s) M2_EC (s) (DRX
cycles)
0 ≤0.16 0.8 * Kinter_M2 (Note
1)
0.16<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
1 ≤0.32 1.6 * Kinter_M2 (Note
1)
0.32<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX
cycle in use
Note 2: Time depends upon the DRX cycle in use
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 408 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.3.1.2-3: Conditions on SCH Ês/Iot to measure FDD interfrequency cell
SCH Ês/Iot of serving Target cell SCH Ês/Iot: Q2 Measurement delay
cell: Q1 (Tmeasure_inter_UE cat M2_EC)
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.3.1.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.3.1.2-4: Requirement to measure FDD interfrequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_inter_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.3.3.1.2.1 Measurement Reporting Requirements
8.15.3.3.1.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.3.3.1.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.3.3.1.2.1.3.
8.15.3.3.1.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_inter, UE cat
M2_EC defined in Clause 8.15.3.3.1.2 When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_EC defined in clause 8.15.3.3.1.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_inter_UE cat M2_EC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 409 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.3.2 E-UTRAN inter-frequency measurements for HD-FDD
8.15.3.3.2.1 E-UTRAN inter-frequency measurements when no DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
The requirements defined in clause 8.15.3.3.1.1 also apply for this section provided the following conditions are met:
- at least downlink subframe # 0 or downlink subframe # 5 per radio frame of an inter-frequency cell to be
identified by the UE is available at the UE over Tidentify_inter_UE cat M2_EC;
- at least one downlink subframe per radio frame of measured cell is available at the UE for RSRP measurement
assuming measured cell is identified cell over Tmeasure_inter_UE cat M2_EC.
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.x-2 for a corresponding Band
8.15.3.3.2.2 E-UTRAN inter frequency measurements when DRX is used
The requirements in this section are applicable for the UE which supports half duplex operation on one or more
supported frequency bands [2].
When DRX is in use and when measurement gaps are scheduled, or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_EC as shown in table 8.15.3.3.2.2-1.
When eDRX_CONN is in use and when measurement gaps are scheduled, or the UE supports capability of conducting
such measurements without gaps, the UE shall be able to identify a new detectable FDD inter-frequency cell within
Tidentify_inter_UE cat M2_EC as shown in table 8.15.3.3.2.2-1A.
Table 8.15.3.3.2.2-1: Requirement to identify a newly detectable HD-FDD interfrequency cell
Gap pattern ID DRX cycle Tidentify_inter_UE cat M2_EC (s)
length (s) (DRX cycles)
0 ≤0.64 320.8 * Kinter_M2 (Note 1)
0.64<DRX- Note 2(400 * Kinter_M2)
cycle≤2.56
1 <0.64 321.6 * Kinter_M2 (Note 1)
0.64≤DRX- Note 2(400 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.3.3.2.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable HD-FDD interfrequency
cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_inter_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.3.2.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 410 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.3.2.2-1B: Requirement to identify a newly detectable HD-FDD interfrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_inter_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.x-2 for a corresponding Band
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP and RSRQ measurements of at
least 4 inter-frequency cells per FDD inter-frequency and the UE physical layer shall be capable of reporting RSRP and
RSRQ to higher layers with the measurement period Tmeasure_inter_UE cat M2_EC, either measurement gaps are scheduled or
the UE supports capability of conducting such measurements without gaps. When DRX is used, Tmeasure_inter_UE cat M2_EC is
as defined in Table 8.15.3.3.2.2-2, and when eDRX_CONN is in use, Tmeasure_inter_UE cat M2_EC is as defined in Table
8.15.3.3.2.2-3.
Table 8.15.3.3.2.2-2: Requirement to measure HD-FDD interfrequency cells
Gap pattern ID DRX cycle Tmeasure_inter_UE cat M2_EC
length (s) (s) (DRX cycles)
0 <0.128 0.8 * Kinter (Note 1)
0.128≤DRX- Note 2 (7 * Kinter_M2)
cycle≤0.16
0.16<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
1 ≤0.32 1.6 * Kinter (Note 1)
0.32<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.3.3.2.2-3: Conditions on SCH Ês/Iot to measure HD-FDD interfrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Measurement delay
identified cell including Ês/Iot: Q2 (Tmeasure_inter_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.3.2.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.3.2.2-4: Requirement to measure HD-FDD interfrequency cells when eDRX_CONN cycle
is used
eDRX_CONN cycle length (s) Tmeasure_inter_UE cat M2_EC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 411 ETSI TS 136 133 V14.3.0 (2017-04)
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.3.3.2.2.1 Measurement Reporting Requirements
8.15.3.3.2.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.3.3.2.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.3.3.2.2.1.3.
8.15.3.3.2.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_inter_UE cat
M2_EC defined in Clause 8.15.3.3.2.2 When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_EC defined in clause 8.15.3.3.2.2
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than Tmeasure_inter_UE cat M2_EC provided the timing to that cell has
not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC autonomous denial
is configured, an additional delay can be expected.
8.15.3.3.3 E-UTRAN TDD inter frequency measurements
8.15.3.3.3.1 E-UTRAN inter frequency measurements when no DRX is used
When no DRX is in use and when measurement gaps are scheduled, or the UE supports capability of conducting such
measurements without gaps, the UE shall be able to identify and measure a new detectable TDD inter frequency cell
according to requirements in Table 8.15.3.3.3.1-1 when additional condition in Table 8.15.3.3.3.1-2 is met.
Table 8.15.3.3.3.1-1: Requirement on cell identification delay and measurement delay for TDD
interfrequency cell
Gap pattern ID Cell identification delay (Tidentify_inter_UE cat M2_EC) Measurement delay (Tmeasure_inter_UE cat M2_EC)
0 320.8 * Kinter s 800 * Kinter_M2 ms
1 321.6 * Kinter s 1600 * Kinter_M2 ms
N freq *100
K Inter_M2 =
(100 - X)
where X is signalled by the RRC parameter TBD [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 412 ETSI TS 136 133 V14.3.0 (2017-04)
Table 8.15.3.3.3.1-2: Conditions on SCH Ês/Iot for cell identification delay and measurement delay for
TDD interfrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay Measurement delay
identified cell including Ês/Iot: Q2 (Tidentify_inter_UE cat M2_EC) (Tmeasure_inter_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table As defined in table
8.15.3.1.3.1-1 8.15.3.1.3.1-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2 Requirements in 8.15.2
apply apply
A cell shall be considered detectable when
- RSRP related side conditions given in Sections 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.x-1 for a corresponding Band.
When measurement gaps are scheduled for TDD inter frequency measurements, or the UE supports capability of
conducting such measurements without gaps, the UE physical layer shall be capable of reporting RSRP and RSRQ to
higher layers with measurement accuracy as specified in sub-clauses 9.1.x.1 and 9.1.x.2with measurement period
(Tmeasure_inter_UE cat M2_EC) given by table 8.15.3.3.3.1-1:
The UE shall be capable of performing RSRP and RSRQ measurements of at least 4 inter-frequency cells per TDD
inter-frequency and the UE physical layer shall be capable of reporting RSRP and RSRQ measurements to higher layers
with the measurement period Tmeasure_inter_UE cat M2_EC.
8.15.3.3.3.1.1 Measurement Reporting Requirements
8.15.3.3.3.1.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.3.3.3.1.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.3.3.3.1.1.3.
8.15.3.3.3.1.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify inter_UE cat M2_EC
defined in Clause 8.15.3.3.3.1. When L3 filtering is used or IDC autonomous denial is configured an additional delay
can be expected.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 413 ETSI TS 136 133 V14.3.0 (2017-04)
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_EC defined in clause 8.15.3.3.3.1
becomes undetectable for a period ≤ 5 seconds and then the cell becomes detectable again and triggers an event, the
event triggered measurement reporting delay shall be less than TMeasurement_Period Inter_UE cat M2_EC provided the timing to that
cell has not changed more than ± 50 Ts and the L3 filter has not been used. When L3 filtering is used or IDC
autonomous denial is configured, an additional delay can be expected.
8.15.3.3.3.2 E-UTRAN inter frequency measurements when DRX is used
When DRX is in use and when DRX or eDRX_CONN is in use, either measurement gaps are scheduled or the UE
supports capability of conducting such measurements without gaps, the UE shall be able to identify a new detectable
TDD inter frequency cell within Tidentify_inter_ UE catM2 as shown in table 8.15.3.3.3.2-1.
When eDRX_CONN is in use the UE shall be able to identify a new detectable TDD inter frequency cell within
Tidentify_inter_UE cat M2_EC as shown in table 8.15.3.3.3.2-1A.
Table 8.15.3.3.3.2-1: Requirement to identify a newly detectable TDD interfrequency cell
Gap pattern ID DRX cycle Tidentify_inter_UE cat M2_EC (s)
length (s) (DRX cycles)
0 DRX-cycle ≤ 0.64 320.8 * Kinter_M2 (Note 1)
0.64<DRX- Note 2(400 * Kinter_M2)
cycle≤2.56
1 DRX-cycle ≤ 0.64 321.6 * Kinter_M2 (Note 1)
0.64<DRX- Note 2(400 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in
use
Note 2: Time depends upon the DRX cycle in use
Table 8.15.3.3.3.2-1A: Conditions on SCH Ês/Iot to identify a newly detectable TDD interfrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Cell identification delay
identified cell including Ês/Iot: Q2 (Tidentify_inter_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.3.3.2-1
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.3.3.2-1B: Requirement to identify a newly detectable TDD interfrequency cell when
eDRX_CONN cycle is used
eDRX_CONN cycle length (s) Tidentify_inter_UE cat M2_EC
(s) (eDRX_CONN
cycles)
2.56<eDRX_CONN cycle≤10.24 Note (400 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use
A cell shall be considered detectable when
- RSRP related side conditions given in Clause 9.1.x.1 and 9.1.x.2 are fulfilled for a corresponding Band,
- RSRQ related side conditions given in Clause 9.1.x.1 are fulfilled for a corresponding Band,
- SCH_RP and SCH Ês/Iot according to Annex Table B.2.x-1 for a corresponding Band
When DRX or eDRX_CONN is in use, the UE shall be capable of performing RSRP and RSRQ measurements of at
least 4 inter-frequency cells per TDD inter-frequency for up to 3 TDD inter-frequencies and the UE physical layer shall
be capable of reporting RSRP and RSRQ measurements to higher layers with the measurement period Tmeasure_inter_UE cat
M2_EC, either measurement gaps are scheduled or the UE supports capability of conducting such measurements without
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 414 ETSI TS 136 133 V14.3.0 (2017-04)
gaps. When DRX is in use, Tmeasure_inter_UE cat M2_EC is as defined in Table 8.15.3.3.3.2-2, and when eDRX_CONN is in
use, Tmeasure_inter_UE cat M2_EC is as defined in Table 8.15.3.3.3.2-3.
Table 8.15.3.3.3.2-2: Requirement to measure TDD inter frequency cells
TDD Uplink- Gap pattern ID DRX cycle Tmeasure_inter_UE cat M2_EC
downlink length (s) (s) (DRX cycles)
configuration
Other than 0 0 ≤0.16 0.8 * Kinter_M2 (Note 1)
0.16<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
1 ≤0.32 1.6 * Kinter_M2 (Note 1)
0.32<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
0 0 ≤0.32 [1.6] * Kinter_M2 (Note 1)
0.32<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
1 ≤0.64 [3.2] * Kinter_M2 (Note 1)
0.64<DRX- Note 2(5 * Kinter_M2)
cycle≤2.56
Note 1: Number of DRX cycle depends upon the DRX cycle in use.
Note 2: Time depends upon the DRX cycle in use.
Table 8.15.3.3.3.2-3: Conditions on SCH Ês/Iot to measure TDD interfrequency cell
SCH Ês/Iot of already Neighbouring cell SCH Measurement delay
identified cell including Ês/Iot: Q2 (Tmeasure_inter_UE cat M2_EC)
serving cell: Q1
-15≤Q1<-6 -15≤ Q2 < -6 As defined in table
8.15.3.3.3.2-2
-15≤Q1<-6 Q2≥-6 Requirements in 8.15.2
apply
Q1≥ -6 Q2≥-6 Requirements in 8.15.2
apply
Table 8.15.3.3.3.2-4: Requirement to measure TDD inter frequency cells when eDRX_CONN cycle is
used
eDRX_CONN cycle length (s) Tmeasure_inter_UE cat M2_EC (s)
(eDRX_CONN cycles)
2.56<eDRX_CONN cycle≤10.24 Note (5 * Kinter_M2)
Note: Time depends upon the eDRX_CONN cycle in use.
The RSRP measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.1 and 9.1.x.2.
The RSRQ measurement accuracy for all measured cells shall be as specified in the sub-clauses 9.1.x.3.
8.15.3.3.3.2.1 Measurement Reporting Requirements
8.15.3.3.3.2.1.1 Periodic Reporting
Reported RSRP and RSRQ measurement contained in periodically triggered measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
8.15.3.3.3.2.1.2 Event-triggered Periodic Reporting
Reported RSRP and RSRQ measurement contained in event triggered periodic measurement reports shall meet the
requirements in sections 9.1.x.1 and 9.1.x.2.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in
clause 8.15.3.3.3.2.1.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 415 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.3.3.2.1.3 Event Triggered Reporting
Reported RSRP and RSRQ measurement contained in event triggered measurement reports shall meet the requirements
in sections 9.1.x.1 and 9.1.x.2.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the
point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that
the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay
excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay
uncertainty is: 2 x TTIDCCH.This measurement reporting delay excludes a delay which caused by no UL resources for
UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify_inter_UE cat
M2_EC defined in Clause 8.15.3.3.3.2. When L3 filtering is used or IDC autonomous denial is configured an additional
delay can be expected.
If a cell which has been detectable at least for the time period Tidentify_inter_UE cat M2_EC defined
in clause 8.15.3.3.3.2 becomes undetectable for a period ≤ 5 seconds and
then the cell becomes detectable again and triggers an event, the event
triggered measurement reporting delay shall be less than Tmeasure_inter_UE cat
M2_EC provided the timing to that cell has not changed more than ± 50 Ts and
the L3 filter has not been used. When L3 filtering is used or IDC autonomous
denial is configured, an additional delay can be expected.8.15.3.4 E-
UTRAN E-CID Measurements Requirements for UE category M2 with CE
mode B
8.15.3.4.1 Intra-frequency E-CID FDD RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeB
8.15.3.4.1.1 Introduction
The requirements in section 8.15.3.4.1 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN FDD intra-frequency RSRP and RSRQ
measurements [24].
8.15.3.4.1.2 Measurement Requirements
The requirements in section 8.15.a3.b3.1 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.3.4.1.3.
8.15.3.4.1.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.3 and 9.1.x.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 416 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.4.2 Intra-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE
in CEModeB
8.15.3.4.2.1 Introduction
The requirements in section 8.15.3.4.2 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN HD-FDD intra-frequency RSRP and
RSRQ measurements [24].
8.15.3.4.2.2 Measurement Requirements
The requirements in section 8.15.a3.b3.2 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.3.4.2.3.
8.15.3.4.2.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.3 and 9.1.x.4.
8.15.3.4.3 Intra-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeB
8.15.3.4.3.1 Introduction
The requirements in section 8.15.3.4.3 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN TDD intra-frequency RSRP and RSRQ
measurements [24].
8.15.3.4.3.2 Measurement Requirements
The requirements in section 8.15.a3.b3.3 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.3.4.3.3.
8.15.3.4.3.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.3 and 9.1.x.4.
8.15.3.4.4 Inter-frequency E-CID FDD RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeB
8.15.3.4.4.1 Introduction
The requirements in section 8.15.3.4.4 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN FDD inter-frequency RSRP and RSRQ
measurements [24].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 417 ETSI TS 136 133 V14.3.0 (2017-04)
8.15.3.4.4.2 Measurement Requirements
The requirements in section 8.15.a4.b4.1 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.3.4.4.3.
8.15.3.4.4.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.22.2.
8.15.3.4.5 Inter-frequency HD-FDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE
in CEModeB
8.15.3.4.5.1 Introduction
The requirements in section 8.15.3.4.5 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN HD-FDD inter-frequency RSRP and
RSRQ measurements [24].
8.15.3.4.5.2 Measurement Requirements
The requirements in section 8.15.a4.b4.2 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.3.4.5.3.
8.15.3.4.5.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.3 and 9.1.x.4.
8.15.3.4.6 Inter-frequency TDD E-CID RSRP and RSRQ Measurements for Cat-M2 UE in
CEModeB
8.15.3.4.6.1 Introduction
The requirements in section 8.15.3.4.6 shall apply provided the UE has received ECID-RequestLocationInformation
message from E-SMLC via LPP requesting the UE to report E-CID E-UTRAN TDD inter-frequency RSRP and RSRQ
measurements [24].
8.15.3.4.6.2 Measurement Requirements
The requirements in section 8.15.a4.b4.3 also apply for this section except the measurement reporting requirements.
The measurement reporting requirements for E-CID RSRP and RSRQ are defined in section 8.15.3.4.6.3.
8.15.3.4.6.3 Measurement Reporting Delay
This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This
measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of
the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH. This measurement reporting delay excludes any delay caused
by no UL resources for UE to send the measurement report.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 418 ETSI TS 136 133 V14.3.0 (2017-04)
Reported RSRP and RSRQ measurements contained in periodically triggered measurement reports shall meet the
requirements in section 9.1.x.3 and 9.1.x.4.
9 Measurements performance requirements for UE
One of the key services provided by the physical layer is the measurements used to trigger or perform a multitude of
functions. Both the UE and the E-UTRAN are required to perform measurements. The physical layer measurement
model and a complete list of measurements are specified in [25] and [22] respectively. The physical layer measurements
are described and defined in [4]. In this clause for each measurement the relevant requirements on the measurement
period, reporting range, granularity and performance in terms of accuracy are specified.
Since the UE reference sensitivity requirements are different depending on supported band, this is noted in each case
with definition of the range Io for each frequency band. Definitions of each frequency bands can be found in [5].
Except for requirements in sections 9.1.2A, 9.1.3A, 9.1.5A and 9.1.6A, the accuracy requirements in this clause are
applicable for AWGN radio propagation conditions and assume independent interference (noise) at each receiver
antenna port.
9.1 E-UTRAN measurements
9.1.1 Introduction
The requirements in this clause are applicable for a UE:
- in state RRC_CONNECTED
- performing measurements with appropriate measurement gaps as defined in Clause 8.1.2.1.
- that is synchronised to the cell that is measured.
The reported measurement result after layer 1 filtering shall be an estimate of the average value of the measured
quantity over the measurement period. The reference point for the measurement result after layer 1 filtering is referred
to as point B in the measurement model described in [25].
The accuracy requirements in this clause are valid for the reported measurement result after layer 1 filtering. The
accuracy requirements are verified from the measurement report at point D in the measurement model having the higher
layer filtering disabled.
In the requirements of Section 9 for the UE capable of CA and the UEs configured with up to four downlink SCell(s),
the applicable exceptions for side conditions are specified in Annex B, Sections B.4.2 and B.4.3, respectively.
9.1.2 Intra-frequency RSRP Accuracy Requirements
9.1.2.1 Absolute RSRP Accuracy
Unless otherwise specified, the requirements for absolute accuracy of RSRP in this clause apply to a cell on the same
frequency as that of the serving cell.
The accuracy requirements in Table 9.1.2.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 419 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.2.1-1: RSRP Intra frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±4.5 ±9 ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±8 ±11 ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.2.2 Relative Accuracy of RSRP
The relative accuracy of RSRP is defined as the RSRP measured from one cell compared to the RSRP measured from
another cell on the same frequency.
The accuracy requirements in Table 9.1.2.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.8 for a corresponding Band.
Table 9.1.2.2-1: RSRP Intra frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2 ±3 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3 ±3 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 420 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.2.3 Absolute RSRP Accuracy under Time Domain Measurement Resource
Restriction
The requirements for absolute accuracy of RSRP in this clause shall apply to a cell on the same frequency as that of the
serving cell when a time domain measurement resource restriction pattern for performing RSRP measurements on this
cell is configured by higher layers (TS 36.331 [2]).
The accuracy requirements in Table 9.1.2.3-1 are valid under the following conditions:
Cell specific reference signals in the measured cell are transmitted either from one, two or four antenna ports,
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled,
RSRP|dBm according to Annex B.3.9 for a corresponding Band,
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the RSRP measurement,
Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern.
Table 9.1.2.3-1: RSRP Intra frequency absolute accuracy under time domain measurement resource
restriction
Accuracy Conditions
Io Note 2 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dBm/
dB dB dBm/BWChannel dBm/BWChannel
15kHz Note 1, 3
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±4.5 ±9 ≥-4 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±8 ±11 ≥-4 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: This minimum Io condition is expressed as the average Io per RE over all REs in that symbol.
NOTE 2: Io is defined in subframes indicated by the time domain measurement resource restriction pattern configured for
performing RSRP measurements of this cell. The Io range defined by the minimum and the maximum Io levels
applies to CRS and non-CRS symbols. Io may be different in different symbols within a subframe.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
For time domain measurements restriction under colliding CRS with ABS configured in non-MBSFN subframes,
requirements in Section 9.1.2.1 apply.
9.1.2.4 Relative Accuracy of RSRP under Time Domain Measurement Resource
Restriction
The requirements for relative accuracy of RSRP in this clause shall apply to a cell on the same frequency as that of the
serving cell when a time domain measurement resource restriction pattern for performing RSRP measurements for this
cell is configured by higher layers (TS 36.331 [2]).
The accuracy requirements in Table 9.1.2.4-1 are valid under the following conditions:
Cell specific reference signals in the measured cell are transmitted either from one, two or four antenna ports,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 421 ETSI TS 136 133 V14.3.0 (2017-04)
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled,
RSRP1,2|dBm according to Annex B.3.10 for a corresponding Band,
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the RSRP measurement,
Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern.
Table 9.1.2.4-1: RSRP Intra frequency relative accuracy under time domain measurement resource
restriction
Accuracy Conditions
Io Note 3 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 6
dB dBm/
dB dB dBm/BWChannel
15kHz Note 1, 5
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2 ±3 ≥-2 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3 ±3 ≥-4 dB Note 4 Note 4 Note 4
NOTE 1: This minimum Io condition is expressed as the average Io per RE over all REs in that symbol.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: Io is defined in subframes indicated by the time domain measurement resource restriction pattern
configured for performing RSRP measurements of this cell. The Io range defined by the minimum and
the maximum Io levels applies to CRS and non-CRS symbols. Io may be different in different symbols
within a subframe.
NOTE 4: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: E-UTRA operating band groups are as defined in Section 3.5.
For time domain measurements restriction under colliding CRS with ABS configured in non-MBSFN subframes,
requirements in Section 9.1.2.2 apply.
9.1.2.5 Absolute RSRP Accuracy under Time Domain Measurement Resource
Restriction with CRS assistance information
The requirements for absolute accuracy of RSRP in this clause shall apply to a cell on the same frequency as that of the
serving cell when a time domain measurement resource restriction pattern for performing RSRP measurements on this
cell is configured by higher layers (TS 36.331 [2]) and the CRS assistance information is provided. The requirements
apply for UEs supporting CRS interference handling.
The accuracy requirements in Table 9.1.2.5-1 are valid under the following conditions:
Cell specific reference signals in the measured cell are transmitted either from one, two or four antenna ports,
Conditions defined in 36.101 Secion 7.3 for reference sensitivity are fulfilled,
RSRP|dBm according to Annex B.3.11 for a corresponding Band,
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the RSRP measurement,
Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 422 ETSI TS 136 133 V14.3.0 (2017-04)
The UE is provided with the CRS assistance information (TS 36.331 [2]) and the CRS assistance information is
valid throughout the entire evaluation period.
The requirements in this section shall also be met when the number of transmit antenna ports [16] of one or more cells
whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
Table 9.1.2.5-1: RSRP Intra frequency absolute accuracy under Time Domain Measurement Resource
Restriction with CRS assistance information
Accuracy Conditions
Io Note 2 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dBm/15kHz Note
dB dB 1, 3 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±4.5 ±9 ≥-9.46 FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±8 ±11 ≥-9.46 N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: This Io condition is expressed as the average Io per RE over all REs in an OFDM symbol.
NOTE 2: Io is defined in subframes indicated by the time domain measurement resource restriction pattern configured for
performing RSRP measurements of this cell. The specified Io range applies to CRS and non-CRS symbols. Io
may be different in different symbols within a subframe.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.2.6 Relative Accuracy of RSRP under Time Domain Measurement Resource
Restriction with CRS assistance information
The requirements for relative accuracy of RSRP in this clause shall apply to a cell on the same frequency as that of the
serving cell when a time domain measurement resource restriction pattern for performing RSRP measurements for this
cell is configured by higher layers (TS 36.331 [2]) and the CRS assistance information is provided. The requirements
apply for UEs supporting CRS interference handling.
The accuracy requirements in Table 9.1.2.6-1 are valid under the following conditions:
Cell specific reference signals in the measured cell are transmitted either from one, two or four antenna ports,
Conditions defined in 36.101 Section 7.3 for reference sensitivity are fulfilled,
RSRP1,2|dBm according to Annex B.3.12 for a corresponding Band,
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the RSRP measurement,
Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern,
The UE is provided with the CRS assistance information (TS 36.331 [2]) and the CRS assistance information is
valid throughout the entire evaluation period.
The requirements in this section shall also be met also when the number of transmit antenna ports [16] of one or more
cells whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 423 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.2.6-1: RSRP Intra frequency relative accuracy under Time Domain Measurement Resource
Restriction with CRS assistance information
Accuracy Conditions
Io Note 3 range
Normal Extreme Ês/Iot Note
2, 6 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 7
Note 1, 5
dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2 ±3 ≥-6.96 FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3 ±3 ≥-9.46 Note 4 Note 4 Note 4
NOTE 1: This Io condition is expressed as the average Io per RE over all REs in an OFDM symbol.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: Io is defined in subframes indicated by the time domain measurement resource restriction pattern
configured for performing RSRP measurements of this cell. The specified Io range applies to CRS
and non-CRS symbols. Io may be different in different symbols within a subframe.
NOTE 4: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: The gap between the Es/Iot level in table 9.1.2.6-1 and 9.1.2.4-1 is due to the interference from either
PCell or at least one neighbour cell indicated within the CRS assistance information.
NOTE 7: E-UTRA operating band groups are as defined in Section 3.5.
9.1.2.7 Absolute RSRP Accuracy for UE Category 1bis
Unless otherwise specified, the requirements for absolute accuracy of RSRP in this clause apply to a cell on the same
frequency as that of the serving cell.
The accuracy requirements in Table 9.1.2.7-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 424 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.2.7-1: RSRP Intra frequency absolute accuracy for UE category 1bis
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
[±5.5] [±10] ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
[±9] [±12] ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.2.8 Relative Accuracy of RSRP for UE Category 1bis
The relative accuracy of RSRP is defined as the RSRP measured from one cell compared to the RSRP measured from
another cell on the same frequency.
The accuracy requirements in Table 9.1.2.8-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.8 for a corresponding Band.
Table 9.1.2.8-1: RSRP Intra frequency relative accuracy for UE category 1bis
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
[±3] [±4] ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
[±4] [±4] ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 425 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.2A Intra-frequency RSRP Accuracy Requirements in High Doppler
Conditions
The accuracy requirements in this clause are applicable for [EVA300 and EVA600] propagation conditions and assume
independent interference (noise) at each receiver antenna port. The accuracy requirements in this clause are also
applicable for [EVA875 and HST875] propagation conditions when highSpeedEnhancedMeasFlag is configured and
assume independent interference (noise) at each receiver antenna port.
9.1.2A.1 Absolute RSRP Accuracy in high Doppler conditions
The requirements for absolute accuracy of RSRP in this clause apply to a cell on the same frequency as that of the
serving cell.
The accuracy requirements in Table 9.1.2A.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
Table 9.1.2A1-1: RSRP Intra frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±6 ±10.5 ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±9.5 ±12.5 ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.2A.2 Relative Accuracy of RSRP in high Doppler conditions
The relative accuracy of RSRP is defined as the RSRP measured from one cell compared to the RSRP measured from
another cell on the same frequency.
The accuracy requirements in Table 9.1.2A.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.8 for a corresponding Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 426 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.2A.2-1: RSRP Intra frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±3.3 ±4.3 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±4.3 ±4.3 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.3 Inter-frequency RSRP Accuracy Requirements
9.1.3.1 Absolute RSRP Accuracy
The requirements for absolute accuracy of RSRP in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.3.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.3 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 427 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.3.1-1: RSRP Inter frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz Note
dB dB 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±4.5 ±9 ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±8 ±11 ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.3.2 Relative Accuracy of RSRP
The relative accuracy of RSRP in inter frequency case is defined as the RSRP measured from one cell compared to the
RSRP measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.3.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
Table 9.1.3.2-1: RSRP Inter frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
Note 3
dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±4.5 ±6 ≥-6 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 428 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.3.3 Absolute RSRP Accuracy for UE Category 1bis
The requirements for absolute accuracy of RSRP in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.3.3-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.3 for a corresponding Band
Table 9.1.3.3-1: RSRP Inter frequency absolute accuracy for UE category 1bis
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz Note
dB dB 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
[±5.5] [±10] ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
[±9] [±12] ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.3.4 Relative Accuracy of RSRP for UE Category 1bis
The relative accuracy of RSRP in inter frequency case is defined as the RSRP measured from one cell compared to the
RSRP measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.3.4-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 429 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.3.4-1: RSRP Inter frequency relative accuracy for UE category 1bis
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
[±5.5] [±7] ≥-6 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.3A Inter-frequency RSRP Accuracy Requirements in High Doppler
Conditions
The accuracy requirements in this clause are applicable for [EVA300 and EVA600] propagation conditions and assume
independent interference (noise) at each receiver antenna port.
9.1.3A.1 Absolute RSRP Accuracy in high Doppler conditions
The requirements for absolute accuracy of RSRP in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.3A.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.3 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 430 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.3A.1-1: RSRP Inter frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz Note
dB dB 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±6 ±10.5 ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±9.5 ±12.5 ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.3A.2 Relative Accuracy of RSRP in high Doppler conditions
The relative accuracy of RSRP in inter frequency case is defined as the RSRP measured from one cell compared to the
RSRP measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.3A.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 431 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.3A.2-1: RSRP Inter frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±5.8 ±7.3 ≥-6 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.4 RSRP Measurement Report Mapping
The reporting range of RSRP is defined from -140 dBm to -44 dBm with 1 dB resolution.
The mapping of measured quantity is defined in Table 9.1.4-1. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 9.1.4-1: RSRP measurement report mapping
Reported value Measured quantity value Unit
RSRP_00 RSRP < -140 dBm
RSRP_01 -140 ≤ RSRP < -139 dBm
RSRP_02 -139 ≤ RSRP < -138 dBm
… … …
RSRP_95 -46 ≤ RSRP < -45 dBm
RSRP_96 -45 ≤ RSRP < -44 dBm
RSRP_97 -44 ≤ RSRP dBm
9.1.5 Intra-frequency RSRQ Accuracy Requirements
9.1.5.1 Absolute RSRQ Accuracy
The requirements for absolute accuracy of RSRQ in this clause apply to a cell on the same frequency as that of the
serving cell.
The accuracy requirements in Table 9.1.5.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 432 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.5.1-1: RSRQ Intra frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2.5 ±4 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.5.2 Absolute RSRQ Accuracy under Time Domain Measurement Resource
Restriction
The requirements for absolute accuracy of RSRQ in this clause shall apply to a cell on the same frequency as that of the
serving cell when a time domain measurement resource restriction pattern for performing RSRQ measurements of this
cell is configured by higher layers (TS 36.331 [2]).
The accuracy requirements in Table 9.1.5.2-1 are valid under the following conditions:
Cell specific reference signals in the measured cell are transmitted either from one, two or four antenna ports,
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled,
RSRP|dBm according to Annex B.3.9 for a corresponding Band,
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the RSRQ measurement,
The RSRQ measurement is not performed in any subframe other than those indicated by the time domain
measurement resource restriction pattern configured for the measured cell,
Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 433 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.5.2-1: RSRQ Intra frequency absolute accuracy under time domain measurement resource
restriction
Accuracy Conditions
Io Note 2 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dBm/
dB dB dBm/BWChannel
15kHz Note 1, 4
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2.5 ±4 ≥-2 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-4 dB Note 3 Note 3 Note 3
NOTE 1: This minimum Io condition is expressed as the average Io per RE over all REs in that symbol.
NOTE 2: Io is defined in subframes indicated by the time domain measurement resource restriction pattern
configured for performing RSRQ measurements of this cell. The Io range defined by the minimum and
the maximum Io levels applies to CRS and non-CRS symbols. Io may be different in different symbols
within a subframe.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
For time domain measurements restriction under colliding CRS with ABS configured in non-MBSFN subframes,
requirements in Section 9.1.5.1 apply.
9.1.5.3 Absolute RSRQ Accuracy under Time Domain Measurement Resource
Restriction with CRS assistance information
The requirements for absolute accuracy of RSRQ in this section shall apply to a cell on the same frequency as that of
the serving cell when a time domain measurement resource restriction pattern for performing RSRQ measurements of
this cell is configured by higher layers (TS 36.331 [2]) and the CRS assistance information is provided. The
requirements apply for UEs supporting CRS interference handling.
The accuracy requirements in Table 9.1.5.3-1 are valid under the following conditions:
Cell specific reference signals in the measured cell are transmitted either from one, two or four antenna ports,
Conditions defined in 36.101 Section 7.3 for reference sensitivity are fulfilled,
RSRP|dBm according to Annex B.3.11 for a corresponding Band,
The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the RSRQ measurement,
The RSRQ measurement is not performed in any subframe other than those indicated by the time domain
measurement resource restriction pattern configured for the measured cell,
Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern,
The UE is provided with the CRS assistance information (TS 36.331 [2]) and the CRS assistance information is
valid throughout the entire evaluation period.
The requirements in this section shall also be met when the number of transmit antenna ports [16] of one or more cells
whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 434 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.5.3-1: RSRQ Intra frequency absolute accuracy under Time Domain Measurement Resource
Restriction with CRS assistance information
Accuracy Conditions
Io Note 2 range
Normal Extreme Note 5
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 6
Note 1, 4
dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2.5 ±4 ≥-6.96 FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-9.46 Note 3 Note 3 Note 3
NOTE 1: This Io condition is expressed as the average Io per RE over all REs in that symbol.
NOTE 2: Io is defined in subframes indicated by the time domain measurement resource restriction pattern
configured for performing RSRQ measurements of this cell. The specified Io range applies to CRS
and non-CRS symbols. Io may be different in different symbols within a subframe.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: The gap between the Es/Iot level in table 9.1.5.3-1 and 9.1.5.2-1 is due to the interference from either
PCell or at least one neighbour cell indicated within the CRS assistance information.
NOTE 6: E-UTRA operating band groups are as defined in Section 3.5.
9.1.5.4 Absolute WB-RSRQ Accuracy
The requirements in this section shall apply when the measurement configuration message received by the UE contains
widebandRSRQ-Meas parameter in TS 36.331 [2]. The WB-RSRQ accuracy figures in Table 9.1.5.4-1are relative to
the value that would be obtained by using the AllowedMeasBandwidth in TS 36.331 [2].
The accuracy requirements in Table 9.1.5.4-1 are valid under the following conditions:
The value of the parameter, AllowedMeasBandwidth in TS 36.331 [2], is 50 resource blocks or larger
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in TS 36.101 [5] Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 435 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.5.4-1: WB-RSRQ Intra frequency absolute accuracy
Accuracy Conditions
Io1-Io2 Io range Note 1
Normal Extreme Ês/Iot Note 2
Note 3 E-UTRA operating band
condition condition Minimum Io Note 5 Maximum Io
groups Note 6
dB dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2.5 ±4 ≥-3 dB 0 ≤Io1- FDD_E, TDD_E -119 -50
Io2 FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-6 dB Note 4 Note 4 Note 4
NOTE 1: Io is the average across all the resource blocks within the AllowedMeasBandwidth in TS 36.331 [2].
NOTE 2: Io1 is the Io level in the resource blocks other than central 6 resource blocks within the
AllowedMeasBandwidth in TS 36.331 [2] and Io2 is the Io level in central 6 resource blocks. The Io1 and Io2
have the same range as defined for Io.
NOTE 3: Iot is the received power spectrum density of total interference and noise for all the resource blocks, other
than central 6 resource blocks.
NOTE 4: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
highest accuracy requirement.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: E-UTRA operating band groups are as defined in Section 3.5.
9.1.5.5 Absolute RSRQ Accuracy for UE Category 1bis
The requirements for absolute accuracy of RSRQ in this clause apply to a cell on the same frequency as that of the
serving cell.
The accuracy requirements in Table 9.1.5.5-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
Table 9.1.5.5-1: RSRQ Intra frequency absolute accuracy for UE category 1bis
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
Note 3
dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
[±3.5] [±5] ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
[±4.5] [±5] ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 436 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.5A Intra-frequency RSRQ Accuracy Requirements in High Doppler
Conditions
The accuracy requirements in this clause are applicable for [EVA300 and EVA600] propagation conditions and assume
independent interference (noise) at each receiver antenna port.
9.1.5A.1 Absolute RSRQ Accuracy in high Doppler conditions
The requirements for absolute accuracy of RSRQ in this clause apply to a cell on the same frequency as that of the
serving cell.
The accuracy requirements in Table 9.1.5A.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
Table 9.1.5A.1-1: RSRQ Intra frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
Note 3
dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±4 ±5.5 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±5 ±5.5 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6 Inter-frequency RSRQ Accuracy Requirements
9.1.6.1 Absolute RSRQ Accuracy
The requirements for absolute accuracy of RSRQ in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.6.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.3 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 437 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6.1-1: RSRQ Inter frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2.5 ±4 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6.2 Relative Accuracy of RSRQ
The relative accuracy of RSRQ in inter frequency case is defined as the RSRQ measured from one cell compared to the
RSRQ measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.6.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 438 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6.2-1: RSRQ Inter frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±3 ±4 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±4 ±4 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6.3 Absolute WB-RSRQ Accuracy
The requirements in this section shall apply when the measurement configuration message received by the UE contains
widebandRSRQ-Meas parameter in TS 36.331 [2]. The WB-RSRQ accuracy figures in Table 9.1.6.3-1are relative to
the value that would be obtained by using the AllowedMeasBandwidth in TS 36.331 [2].
The accuracy requirements in Table 9.1.6.3-1 are valid under the following conditions:
The value of the parameter, AllowedMeasBandwidth in TS 36.331 [2], is 50 resource blocks or larger
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in TS 36.101 [5] Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 439 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6.3-1: WB-RSRQ Inter frequency absolute accuracy
Accuracy Conditions
Io1-Io2 Io range Note 1
Normal Extreme Ês/Iot Note 2
Note 3 E-UTRA operating band Minimum Io
condition condition Maximum Io
groups Note 6 Note 5
dB dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2.5 ±4 ≥-3 dB 0 ≤Io1- FDD_E, TDD_E -119 -50
Io2 FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-6 dB Note 4 Note 4 Note 4
NOTE 1: Io is the average across all the resource blocks within the AllowedMeasBandwidth in TS 36.331 [2].
NOTE 2: Io1 is the Io level in the resource blocks other than central 6 resource blocks within the
AllowedMeasBandwidth in TS 36.331 [2] and Io2 is the Io level in central 6 resource blocks. The Io1 and Io2
have the same range as defined for Io.
NOTE 3: Iot is the received power spectrum density of total interference and noise for all the resource blocks, other
than central 6 resource blocks.
NOTE 4: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
highest accuracy requirement.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6.4 Relative WB-RSRQ Accuracy
The requirements in this section shall apply when the measurement configuration message received by the UE contains
widebandRSRQ-Meas parameter in TS 36.331 [2]. The WB-RSRQ accuracy figures in Table 9.1.6.4-1are relative to
the value that would be obtained by using the AllowedMeasBandwidth in TS 36.331 [2].
The accuracy requirements in Table 9.1.6.4-1 are valid under the following conditions:
The value of the parameter, AllowedMeasBandwidth in TS 36.331 [2], is 50 resource blocks or larger for the
measured cells from different frequencies
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in TS 36.101 [5] Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 440 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6.4-1: WB-RSRQ Inter frequency relative accuracy
Accuracy Conditions
Io1-Io2 Io range Note 1
Normal Extreme Ês/Iot Note 2
Note 3 E-UTRA operating band Minimum Io
condition condition Maximum Io
groups Note 6 Note 5
dB dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±3 ±4 ≥-3 dB 0 ≤Io1- FDD_E, TDD_E -119 -50
Io2 FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±4 ±4 ≥-6 dB Note 4 Note 4 Note 4
NOTE 1: Io is the average across all the resource blocks within the AllowedMeasBandwidth in TS 36.331 [2].
NOTE 2: Io1 is the Io level in the resource blocks other than central 6 resource blocks within the
AllowedMeasBandwidth in TS 36.331 [2] and Io2 is the Io level in central 6 resource blocks. The Io1 and Io2
have the same range as defined for Io.
NOTE 3: Iot is the received power spectrum density of total interference and noise for all the resource blocks, other
than central 6 resource blocks. The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the
requirement applies
NOTE 4: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
highest accuracy requirement.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6.5 Absolute RSRQ Accuracy for UE Category 1bis
The requirements for absolute accuracy of RSRQ in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.6.5-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.3 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 441 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6.5-1: RSRQ Inter frequency absolute accuracy for UE category 1bis
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
[±3.5] [±5] ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
[±4.5] [±5] ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6.6 Relative Accuracy of RSRQ for UE Category 1bis
The relative accuracy of RSRQ in inter frequency case is defined as the RSRQ measured from one cell compared to the
RSRQ measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.6.6-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 442 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6.6-1: RSRQ Inter frequency relative accuracy for UE category 1bis
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
[±4] [±5] ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
[±5] [±5] ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6A Inter-frequency RSRQ Accuracy Requirements in High Doppler
Conditions
The accuracy requirements in this clause are applicable for [EVA300 and EVA600] propagation conditions and assume
independent interference (noise) at each receiver antenna port.
9.1.6A.1 Absolute RSRQ Accuracy in high Doppler conditions
The requirements for absolute accuracy of RSRQ in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.6A.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.3 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 443 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6A.1-1: RSRQ Inter frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±4 ±5.5 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±5 ±5.5 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.6A.2 Relative Accuracy of RSRQ in high Doppler conditions
The relative accuracy of RSRQ in inter frequency case is defined as the RSRQ measured from one cell compared to the
RSRQ measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.6A.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 444 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.6A.2-1: RSRQ Inter frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±3.5 ±5.0 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±4.5 ±5.0 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.7 RSRQ Measurement Report Mapping
The reporting range of RSRQ is defined from -34 dB to 2.5 dB with 0.5 dB resolution.
The mapping of measured quantity is defined in table 9.1.7-1. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 9.1.7-1: RSRQ measurement report mapping
Reported value Measured quantity value Unit
RSRQ_-30 RSRQ < -34 dB
RSRQ_-29 -34 ≤ RSRQ < -33.5 dB
… … …
RSRQ_-02 -20.5 ≤ RSRQ < -20 dB
RSRQ_-01 -20 ≤ RSRQ < -19.5 dB
RSRQ_00 RSRQ < -19.5 dB
RSRQ_01 -19.5 ≤ RSRQ < -19 dB
RSRQ_02 -19 ≤ RSRQ < -18.5 dB
… … …
RSRQ_32 -4 ≤ RSRQ < -3.5 dB
RSRQ_33 -3.5 ≤ RSRQ < -3 dB
RSRQ_34 -3 ≤ RSRQ dB
RSRQ_35 -3 ≤ RSRQ < -2.5 dB
RSRQ_36 -2.5 ≤ RSRQ < -2 dB
… … …
RSRQ_45 2 ≤ RSRQ < 2.5 dB
RSRQ_46 2.5 ≤ RSRQ dB
Note: The ranges from RSRQ_-30 to RSRQ_-01 and from RSRQ_35 to RSRQ_46 apply for the UE who can
support extended RSRQ range in [31].
9.1.8 Power Headroom
The requirements in this clause shall apply for power headroom Type 1 and for power headroom Type 2, which are
specified in clause 5.1.1.2 in [3].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 445 ETSI TS 136 133 V14.3.0 (2017-04)
For a UE not configured with a secondary cell, the power headroom provides the serving eNB with information about
the differences between the UE configured maximum output power (PCMAX,) defined in TS 36.101 [5] and the estimated
power for UL-SCH transmission of the serving cell [3]. In this case the UE shall meet requirements for power
headroom Type 1.
For a UE configured with a secondary cell, the power headroom provides the serving eNB with information about the
differences between the UE configured maximum output power (PCMAX,c) defined in TS 36.101[5] and the estimated
power for UL-SCH transmission per activated serving cell c, or the estimated power for simultaneous PUSCH and
PUCCH transmission on PCell [3]. In this case the UE shall meet requirements for both power headroom Type 1 and
Type 2.
9.1.8.1 Period
The reported power headroom shall be estimated over 1 subframe.
When extendedPHR is not configured [17], the Type 1 power headroom shall be estimated for the primary serving cell
as defined in clause 5.1.1.2 in TS 36.213 [3].
When extendedPHR is configured [17], the Type 1 and Type 2 power headroom shall be estimated for each activated
serving cell with configured uplink as defined in clause 5.1.1.2 in TS 36.213 [3].
9.1.8.2 Reporting Delay
The power headroom reporting delay is defined as the time between the beginning of the power headroom reference
period and the time when the UE starts transmitting the power headroom over the radio interface. The reporting delay of
the power headroom shall be 0 ms, which is applicable for all configured triggering mechanisms for power headroom
reporting.
9.1.8.3 Void
9.1.8.4 Report Mapping
The power headroom reporting range is from -23 ...+40 dB. Table 9.1.8.4-1 defines the report mapping.
Table 9.1.8.4-1: Power headroom report mapping
Reported value Measured quantity value (dB)
POWER_HEADROOM_0 -23 ≤ PH < -22
POWER_HEADROOM_1 -22 ≤ PH < -21
POWER_HEADROOM_2 -21 ≤ PH < -20
POWER_HEADROOM_3 -20 ≤ PH < -19
POWER_HEADROOM_4 -19 ≤ PH < -18
POWER_HEADROOM_5 -18 ≤ PH < -17
… …
POWER_HEADROOM_57 34 ≤ PH < 35
POWER_HEADROOM_58 35 ≤ PH < 36
POWER_HEADROOM_59 36 ≤ PH < 37
POWER_HEADROOM_60 37 ≤ PH < 38
POWER_HEADROOM_61 38 ≤ PH < 39
POWER_HEADROOM_62 39 ≤ PH < 40
POWER_HEADROOM_63 PH ≥ 40
9.1.9 UE Rx – Tx time difference
9.1.9.1 Measurement Requirement
The UE RX-TX time difference is measured from the PCell.
The accuracy requirements in Table 9.1.9.1-1 are valid under the following conditions:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 446 ETSI TS 136 133 V14.3.0 (2017-04)
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
No changes to the uplink transmission timing are applied during the measurement period.
RSRP|dBm according to Annex B.3.5 for a corresponding Band
Table 9.1.9.1-1: UE Rx – Tx time difference measurement accuracy
Conditions
Downlink Io Note 1 range
Accuracy transmission
Ês/Iot E-UTRA operating band
bandwidth of Minimum Io Maximum Io
groups Note 6
PCell
Ts Note 2 dB MHz dBm/15kHz Note 5 dBm/BWChannel
Note 7,
FDD_A TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±20 ≥-3 dB ≥1.4 MHz FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G Note 4 -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±14 ≥-3 dB ≥ 3 MHz Note 3 Note 3 Note 3
±10 ≥-3 dB ≥ 5 MHz Note 3 Note 3 Note 3
±7 ≥-3 dB ≥10 MHz Note 3 Note 3 Note 3
NOTE 1: When in dBm/15kHz, the minimum Io condition is expressed as the average Io per RE over all REs in
that symbol. Io may be different in different symbols within a subframe.
NOTE 2: Ts is the basic timing unit defined in TS 36.211.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding requirement with downlink bandwidth ≥1.4 MHz.
NOTE 4: Except Band 29.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: E-UTRA operating band groups are as defined in Section 3.5.
NOTE 7: Except Band 32.
9.1.9.2 Measurement Report mapping
The reporting range of UE Rx - Tx time difference is defined from 0 to 20472Ts with 2Ts resolution for UE Rx - Tx
time difference less than 4096Ts and 8Ts for UE Rx - Tx time difference equal to or greater than 4096Ts.
The mapping of measured quantity is defined in Table 9.1.9.2-1.
Table 9.1.9.2-1: UE Rx - Tx time difference measurement report mapping
Reported value Measured quantity value Unit
RX-TX_TIME_DIFFERENCE_0000 TUE Rx-Tx < 2 Ts
RX-TX_TIME_DIFFERENCE_0001 2 ≤ TUE Rx-Tx < 4 Ts
RX-TX_TIME_DIFFERENCE_0002 4 ≤ TUE Rx-Tx < 6 Ts
… … …
RX-TX_TIME_DIFFERENCE_2046 4092 ≤ TUE Rx-Tx < 4094 Ts
RX-TX_TIME_DIFFERENCE_2047 4094 ≤ TUE Rx-Tx < 4096 Ts
RX-TX_TIME_DIFFERENCE_2048 4096 ≤ TUE Rx-Tx < 4104 Ts
RX-TX_TIME_DIFFERENCE_2049 4104 ≤ TUE Rx-Tx < 4112 Ts
… … …
RX-TX_TIME_DIFFERENCE_4093 20456 ≤ TUE Rx-Tx < 20464 Ts
RX-TX_TIME_DIFFERENCE_4094 20464 ≤ TUE Rx-Tx < 20472 Ts
RX-TX_TIME_DIFFERENCE_4095 20472 ≤ TUE Rx-Tx Ts
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 447 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.9.3 Measurement Requirement under Time Domain Measurement Resource
Restriction
The requirements in this section apply for UE configured with a time-domain measurement resource restriction pattern
for PCell measurements. The UE Rx-Tx time difference is measured from the Pcell.
The accuracy requirements in Table 9.1.9.3-1 are valid under the following conditions:
- Cell specific reference signals are transmitted either from one, two or four antenna ports,
- Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled,
- No changes to the uplink transmission timing are applied during the measurement period,
RSRP|dBm according to Annex B.3.5 for a corresponding Band,
- The time domain measurement resource restriction pattern configured for the PCell indicates at least one
subframe per radio frame for performing the PCell measurements [2],
- Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern.
Table 9.1.9.3-1: UE Rx–Tx time difference measurement accuracy under time domain measurement
resource restriction
Conditions
Downlink Io Note 1, 5 range
Accuracy transmission
Ês/Iot Note 6 E-UTRA operating band
bandwidth of Minimum Io Maximum Io
groups Note 8
PCell
Ts Note 2 dB MHz dBm/15kHz Note 7 dBm/BWChannel
Note 9,
FDD_A TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±20 ≥-3 dB ≤ 3 MHz FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G Note 4 -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±10 ≥-3 dB ≥ 5 MHz Note 3 Note 3 Note 3
NOTE 1: When in dBm/15kHz, the minimum Io condition is expressed as the average Io per RE over all REs in
that symbol. Io may be different in different symbols within a subframe.
NOTE 2: Ts is the basic timing unit defined in TS 36.211.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding requirement with downlink bandwidth ≤ 3 MHz.
NOTE 4: Except Band 29.
NOTE 5: Io is defined for the subframes indicated by the time-domain measurement resource restriction
pattern for serving cell measurements. The specified Io range applies to CRS and non-CRS symbols.
Io may be different in different symbols within a subframe.
NOTE 6: CRS Ês/Iot is in subframes indicated for PCell measurements by the time-domain measurement
resource restriction pattern.
NOTE 7: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 8: E-UTRA operating band groups are as defined in Section 3.5.
NOTE 9: Except Band 32.
NOTE: It is up to the UE implementation whether the UE Rx-Tx time difference measurement is performed in
any subframe or in subframes indicated by the time-domain measurement resource restriction pattern.
9.1.9.4 Measurement Requirement when Time Domain Measurement Resource
Restriction Pattern is Configured with CRS Assistance Information
The UE Rx-Tx time difference measurement is performed for the PCell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 448 ETSI TS 136 133 V14.3.0 (2017-04)
For UE configured with a time-domain measurement resource restriction pattern for PCell measurements, the accuracy
requirements in Table 9.1.9.4-1 apply provided that the following conditions are met for the PCell:
- PCell cell specific reference signals are transmitted from one, two or four antenna ports,
- Conditions defined in 36.101 Section 7.3 for reference sensitivity are fulfilled,
- No changes to the uplink transmission timing are applied during the measurement period,
- RSRP|dBm according to Annex B.3.13 for a corresponding Band,
- The time domain measurement resource restriction pattern configured for the measured cell indicates at least one
subframe per radio frame for performing the RSRP measurement,
- Four symbols containing CRS are available in all subframes indicated by the time domain measurement resource
restriction pattern, and
- The UE is provided via PCell with the CRS assistance information (TS 36.331 [2]) and the CRS assistance
information is valid throughout the entire evaluation period.
The requirements in this section shall also be met when the number of transmit antenna ports [16] of one or more cells
whose CRS assistance information is provided [2] is different from the number of transmit antenna ports of the
measured cell.
When the CRS assistance information is provided, the transmission bandwidth [30] in all intra-frequency cells in the
CRS assistance information [2] is the same or larger than the transmission bandwidth of the PCell for which
measurement is performed.
Table 9.1.9.4-1: UE Rx–Tx time difference measurement accuracy
Conditions
Downlink Io range Note 5
Accuracy CRS transmission
E-UTRA operating band Minimum Maximum
Ês/Iot Note 6 bandwidth of
groups Note 8 Io Note 1, 7 Io
PCell
Ts Note 2 dB MHz dBm/15kHz Note 7 dBm/BWChannel
Note 9,
FDD_A TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±20 ≥-7.76 ≤ 3 MHz FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G Note 4 -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±10 ≥-7.76 ≥ 5 MHz Note 3 Note 3 Note 3
NOTE 1: This Io condition is expressed as the average Io per RE over all REs in an OFDM symbol.
NOTE 2: Ts is the basic timing unit defined in TS 36.211.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding requirement with downlink bandwidth ≤ 3 MHz.
NOTE 4: Except Band 29.
NOTE 5: Io is defined in subframes indicated for PCell measurements by the time domain measurement
resource restriction pattern. The specified Io range applies to CRS and non-CRS symbols. Io may be
different in different symbols within a subframe.
NOTE 6: CRS Ês/Iot is in subframes indicated for PCell measurements by the time-domain measurement
resource restriction pattern.
NOTE 7: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 8: E-UTRA operating band groups are as defined in Section 3.5.
NOTE 9: Except Band 32.
NOTE: It is up to the UE implementation whether the UE Rx-Tx time difference measurement is performed in
any subframe or in subframes indicated by the time-domain measurement resource restriction pattern.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 449 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.10 Reference Signal Time Difference (RSTD)
NOTE: This measurement is used for UE positioning purposes.
9.1.10.1 Intra-Frequency Accuracy Requirement
The accuracy requirements in Table 9.1.10.1-1 are valid under the following conditions:
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
PRP 1,2|dBm according to Annex B.3.6 for a corresponding Band
There are no measurement gaps overlapping with the PRS subframes of the measured serving cell.
The parameter expectedRSTDUncertainty signalled over LPP by E-SMLC as defined in TS 36.355 [24] is less
than 5 µs.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 450 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.10.1-1: RSTD measurement accuracy
Conditions
Minimum Io Note 7 range
PRS
bandwidth,
which is
minimum of Minimum
serving cell number of
channel available
bandwidth measurement
Accuracy subframes
PRS Ês/Iot and the E-UTRA operating band Minimum Maximum
among the
PRS groups Note 8 Io Note 1 Io
reference cell
bandwidths and the
of the measured
reference neighbour cell i
cell and the
measured
neighbour
cell i Note 5
dB dBm/15kHz dBm/BWChanne
Ts Note 2 RB Note 6
l
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
(PRS Ês/Iot)ref ≥-6dB FDD_D -119.5 -50
±15 and ≥6 6 FDD_E, TDD_E -119 -50
(PRS Ês/Iot)i ≥-13dB FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
(PRS Ês/Iot)ref ≥-
6dB
±10 ≥ 15 6 Note 4 Note 4 Note 4
and
(PRS Ês/Iot)i ≥-13dB
(PRS Ês/Iot)ref ≥-
6dB
±6 ≥ 25 ≥2 Note 4 Note 4 Note 4
and
(PRS Ês/Iot)i ≥-13dB
(PRS Ês/Iot)ref ≥-
6dB
±5 ≥ 50 ≥1 Note 4 Note 4 Note 4
and
(PRS Ês/Iot)i ≥-13dB
(PRS Ês/Iot)ref ≥-
6dB
±4 ≥ 75 ≥1 Note 4 Note 4 Note 4
and
(PRS Ês/Iot)i ≥-13dB
NOTE 1: This minimum Io condition is expressed as the average Io per RE over all REs in an OFDM symbol.
NOTE 2: Ts is the basic timing unit defined in TS 36.211 [16].
NOTE 3: PRS bandwidth is as indicated in prs-Bandwidth in the OTDOA assistance data defined in [24].
NOTE 4: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
requirement with the PRS bandwidth ≥ 6 RB.
NOTE 5: The serving cell, the reference cell, and the measured neighbour cell i are on the same carrier frequency.
NOTE 6: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 7: The Io is defined in PRS positioning subframes. The same Io range applies to PRS and non-PRS symbols. Io
levels are different in PRS and non-PRS symbols within the same subframe.
NOTE 8: E-UTRA operating band groups are as defined in Section 3.5.
9.1.10.2 Inter-Frequency Accuracy Requirement
The accuracy requirements in Table 9.1.10.2-1 are valid under the following conditions:
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
PRP 1,2|dBm according to Annex B.3.7 for a corresponding Band
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 451 ETSI TS 136 133 V14.3.0 (2017-04)
There are no measurement gaps overlapping with the PRS subframes in cells belonging to the serving carrier
frequency.
The parameter expectedRSTDUncertainty signalled over LPP by E-SMLC as defined in TS 36.355 [24] is less
than 5 µs.
Table 9.1.10.2-1: RSTD measurement accuracy
Conditions
Minimum Io Note 6 range
PRS
bandwidth
which is Minimum
minimum of number of
serving cell available
channel measurement
Accuracy bandwidthNote subframes
PRS Ês/Iot 7 and the PRS E-UTRA operating Minimum Maximum
among the
band groups Note 8 Io Note 1 Io
bandwidths reference cell
of the and the
reference cell measured
and the neighbour cell i
measured
neighbour
cell i
dB dBm/15kHz dBm/BWChan
Ts Note 2 RB Note 5
nel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
(PRS Ês/Iot)ref ≥-6dB FDD_D -119.5 -50
±21 and ≥6 4 FDD_E, TDD_E -119 -50
(PRS Ês/Iot)i ≥-13dB FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
(PRS Ês/Iot)ref ≥-6dB
±16 and ≥ 15 4 Note 4 Note 4 Note 4
(PRS Ês/Iot)i ≥-13dB
(PRS Ês/Iot)ref ≥-6dB
±10 and ≥ 25 ≥2 Note 4 Note 4 Note 4
(PRS Ês/Iot)i ≥-13dB
(PRS Ês/Iot)ref ≥-6dB
±9 and ≥ 50 ≥1 Note 4 Note 4 Note 4
(PRS Ês/Iot)i ≥-13dB
(PRS Ês/Iot)ref ≥-6dB
±8 and ≥ 75 ≥1 Note 4 Note 4 Note 4
(PRS Ês/Iot)i ≥-13dB
NOTE 1: This minimum Io condition is expressed as the average Io per RE over all REs in an OFDM symbol.
NOTE 2: Ts is the basic timing unit defined in TS 36.211 [16].
NOTE 3: PRS bandwidth is as indicated in prs-Bandwidth in the OTDOA assistance data defined in [24].
NOTE 4: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
requirement with the PRS bandwidth ≥ 6 RB.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: The Io is defined in PRS positioning subframes. The same Io range applies to PRS and non-PRS symbols. Io levels are
different in PRS and non-PRS symbols within the same subframe.
NOTE 7: If a CA capable UE is configured with one or two SCell(s), the serving cell channel bandwidth is the minimum of the
serving cell channel bandwidths in the component carriers involved in the RSTD measurement. If any of the serving
cells is not involved in this RSTD measurement for CA, the channel bandwidth of that serving cell is not included in the
determination of the minimum PRS bandwidth.
NOTE 8: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 452 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.10.3 RSTD Measurement Report Mapping
The reporting range of RSTD is defined from -15391Ts to 15391Ts with 1Ts resolution for absolute value of RSTD less
or equal to 4096Ts and 5Ts for absolute value of RSTD greater than 4096Ts.
The mapping of measured quantity is defined in Table 9.1.10.3-1.
Table 9.1.10.3-1: RSTD report mapping
Reported Value Measured Quantity Value Unit
RSTD_0000 -15391 > RSTD Ts
RSTD_0001 -15391 ≤ RSTD < -15386 Ts
… … …
RSTD_2258 -4106 ≤ RSTD < -4101 Ts
RSTD_2259 -4101 ≤ RSTD < -4096 Ts
RSTD_2260 -4096 ≤ RSTD < -4095 Ts
RSTD_2261 -4095 ≤ RSTD < -4094 Ts
… … …
RSTD_6353 -3 ≤ RSTD < -2 Ts
RSTD_6354 -2 ≤ RSTD < -1 Ts
RSTD_6355 -1 ≤ RSTD ≤ 0 Ts
RSTD_6356 0 < RSTD ≤ 1 Ts
RSTD_6357 1 < RSTD ≤ 2 Ts
RSTD_6358 2 < RSTD ≤ 3 Ts
… … …
RSTD_10450 4094 < RSTD ≤ 4095 Ts
RSTD_10451 4095 < RSTD ≤ 4096 Ts
RSTD_10452 4096 < RSTD ≤ 4101 Ts
RSTD_10453 4101 < RSTD ≤ 4106 Ts
… … …
RSTD_12709 15381 < RSTD ≤ 15386 Ts
RSTD_12710 15386 < RSTD ≤ 15391 Ts
RSTD_12711 15391 < RSTD Ts
9.1.10.4 Higher-Resolution RSTD Measurement Report Mapping
The reporting range of higher-resolution RSTD is defined from -15391 Ts to 15391 Ts with 0.5 Ts resolution.
The UE shall report a reference quantity based on Table 9.1.10.3-1 and a relative quantity Δ RSTD defined in Table
9.1.10.4-1, so that the difference between the measured RSTD quantity and the lower bound of the corresponding range
from Table 9.1.10.3-1 is between Δ RSTD and Δ RSTD + resolutionStep.
RSTD_delta_0 or RSTD_delta_1 specified in Table 9.1.10.4-1 can be reported together with any value from Table
9.1.10.3-1 in the range from RSTD_2260 to RSTD_10451. In this case, resolutionStep is 0.5.
Any relative quantity value from Table 9.1.10.4-1, except RSTD_delta_1, can be reported together with any value from
Table 9.1.10.3-1 in the range from RSTD_0000 to RSTD_2259 or in the range from RSTD_10452 to RSTD_12711. In
this case, resolutionStep is 1.0.
Table 9.1.10.4-1: Relative quantity mapping for higher-resolution RSTD measurement reporting
Reported Relative Quantity Value Measured Relative Quantity Value, Δ RSTD Unit
RSTD_delta_0 0 Ts
RSTD_delta_1 0.5 Ts
RSTD_delta_2 1.0 Ts
RSTD_delta_3 2.0 Ts
RSTD_delta_4 3.0 Ts
RSTD_delta_5 4.0 Ts
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 453 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.11 Carrier aggregation measurement accuracy
This clause contains requirements on UE capabilities for support of E-UTRA FDD, TDD and TDD-FDD carrier
aggregation. Requirements in this clause are applicable to all carrier aggregation capable UEs which have been
configured with up to four downlink SCell(s). Note: This clause covers measurement accuracy requirements for
frequencies corresponding to those used for the PCell and SCell(s); measurements of any other frequency are
considered to be inter-frequency measurements covered by the accuracy requirements in clause 9.1.3 for inter-frequency
RSRP, clause 9.1.6 for inter-frequency RSRQ, and clause 9.1.17.3 for inter-frequency RS-SINR.
The requirements in this clause apply for bandwidths defined in the bandwidth combination set for the CA
configurations supported by the UE [5].
9.1.11.1 Primary component carrier accuracy requirement
RSRP measurements of cells on the primary component carrier shall meet the intra-frequency absolute accuracy
requirements in section 9.1.2.1.
RSRQ measurements of cells on the primary component carrier shall meet the intra-frequency absolute accuracy
requirements in section 9.1.5.1.
RS-SINR measurements of cells on the primary component carrier shall meet the intra-frequency absolute accuracy
requirements in section 9.1.17.2.1.
Comparisons between RSRP of cells on the primary component carrier shall also meet the intra-frequency relative
accuracy requirements in sections 9.1.2.2.
9.1.11.2 Secondary component carrier accuracy requirement
RSRP measurements of cells on any of the secondary component carrier(s) shall meet the intra-frequency absolute
accuracy requirements in section 9.1.2.1.
RSRQ measurements of cells on any of the secondary component carrier(s) shall meet the intra-frequency absolute
accuracy requirements in section 9.1.5.1.
RS-SINR measurements of cells on any of the secondary component carrier(s) shall meet the intra-frequency absolute
accuracy requirements in section 9.1.17.2.1.
Comparisons between RSRP of cells on the same secondary component carrier shall meet the intra-frequency relative
accuracy requirements in sections 9.1.2.2
9.1.11.3 Primary and secondary component carrier relative accuracy requirement
When measurements of cells on the primary component carrier are compared with measurements of cells on any of the
secondary component carrier(s), the applicable relative accuracy requirements are:
RSRP inter-frequency accuracy requirements in section 9.1.3.2,
RSRQinter-frequency accuracy requirements in section 9.1.6.2,
RS-SINR inter-frequency accuracy requirements in section 9.1.17.3.2.
9.1.11.4 Secondary component carrier relative accuracy requirement
When measurements of cells on any of the secondary component carrier(s) are compared with measurements of cells on
the other secondary component carrier, the applicable relative accuracy requirements are:
RSRP inter-frequency accuracy requirements in section 9.1.3.2,
RSRQ inter-frequency accuracy requirements in section 9.1.6.2,
RS-SINR inter-frequency accuracy requirements in section 9.1.17.3.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 454 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.12 Reference Signal Time Difference (RSTD) Measurement Accuracy
Requirements for Carrier Aggregation
This clause contains requirements for E-UTRA FDD, TDD and TDD-FDD carrier aggregation. This clause contains
RSTD measurement accuracy requirements for a UE configured with one or two downlink SCell(s). The UE may
operate in one of the E-UTRA carrier aggregations listed in clause 8.3.1. The requirements in this clause shall apply
regardless whether the configured downlink secondary cell is activated or deactivated by the MAC-CE command [17].
The requirements apply for bandwidths defined in the bandwidth combination set for the CA configurations supported
by the UE [5].
The RSTD measurements, which are obtained when both the reference cell and neighbouring cell belong to the primary
component carrier, shall meet the intra-frequency RSTD accuracy requirements defined in clause 9.1.10.1.
The RSTD measurements, which are obtained when both the reference cell and neighbouring cell belong to the same
secondary component carrier, shall meet the intra-frequency RSTD accuracy requirements defined in clause 9.1.10.1.
The RSTD measurements, which are obtained when the reference cell and neighbouring cell do not belong to the same
carrier, shall meet the inter-frequency RSTD accuracy requirements defined in clause 9.1.10.2.
9.1.13 Measurement accuracy for UE category 0
9.1.13.1 Intra-frequency Absolute RSRP Accuracy for UE category 0
The requirements for absolute accuracy of RSRP in this clause apply to a cell on the same frequency as that of the
serving cell for UE category 0.
The accuracy requirements in Table 9.1.13.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for RSRP measurement assuming
measured cell is identified cell.
Table 9.1.13.1-1: RSRP Intra frequency absolute accuracy for UE category 0
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±7 ±10 ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±9 ±12 ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 455 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.13.2 Intra-frequency Relative Accuracy of RSRP for UE category 0
The relative accuracy of RSRP is defined as the RSRP measured from one cell compared to the RSRP measured from
another cell on the same frequency for category 0 UE.
The accuracy requirements in Table 9.1.13.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.8 for a corresponding Band.
At least 1 DL subframe per radio frame of measured cell is available at the UE for RSRP measurement assuming
measured cell is identified cell.
Table 9.1.13.2-1: RSRP Intra frequency relative accuracy for UE category 0
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±3 ±4 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±4 ±4 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.13.3 Intra-frequency Absolute RSRQ Accuracy for UE category 0
The requirements for absolute accuracy of RSRQ in this clause apply to a cell on the same frequency as that of the
serving cell for category 0 UE.
The accuracy requirements in Table 9.1.13.3-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for RSRQ measurement assuming
measured cell is identified cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 456 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.13.3-1: RSRQ Intra frequency absolute accuracy for UE category 0
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±3.5 ±5 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±4.5 ±5 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.14 Accuracy requirements for Discovery Signal Measurements
9.1.14.1 Introduction
Discovery signal measurements are performed when higher layers indicate measurements based on discovery signals
according to DMTC configuration [2]. The discovery measurement accuracy requirements are defined for the following
physical layer measurements performed in discovery signal occasions [16],
RSRP measured in subframes of the configured discovery signal occasions as specified in [4],
CSI-RSRP measurements specified in [4],
RSRQ measured in subframes of the configured discovery signal occasions as specified in [4].
9.1.14.2 RSRP measurements in discovery signal occasions
Intra-frequency absolute RSRP measurement accuracy requirements in discovery signal occasions are the same as
specified in Section 9.1.2.1.
Intra-frequency relative RSRP measurement accuracy requirements in discovery signal occasions are the same as
specified in Section 9.1.2.2.
Inter-frequency absolute RSRP measurement accuracy requirements in discovery signal occasions are the same as
specified in Section 9.1.3.1.
Inter-frequency relative RSRP measurement accuracy requirements in discovery signal occasions are the same as
specified in Section 9.1.3.2.
Measurement report mapping for RSRP measurements in discovery signal occasions are the same as specified in
Section 9.1.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 457 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.14.3 CSI-RSRP measurements in discovery signal occasions
9.1.14.3.1 Intra-frequency CSI-RSRP measurements
9.1.14.3.1.1 Absolute CSI-RSRP measurement requirements
In this clause, absolute CSI-RSRP measurement accuracy requirements in discovery signal occasions apply to a cell or
TP on the same frequency as that of the serving cell.
The accuracy requirements in Table 9.1.14.3.1.1-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP,
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is specified in Annex B.3.14 for a corresponding Band.
Table 9.1.14.3.1.1-1: Intra-frequency absolute CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
E-UTRA operating band
condition condition Ês/Iot Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±4.5 ±9 ≥ 0 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±8 ±11 ≥0 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.14.3.1.2 Relative CSI-RSRP measurement requirements
In this section, the relative CSI-RSRP measurement is defined as the CSI-RSRP measured from one cell or TP
compared to the CSI-RSRP measured on the same frequency from another cell or from another TP. If two TPs are
compared, they may belong to the same or different cells.
The accuracy requirements in Table 9.1.14.3.1.2-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is specified in Annex B.3.15 for a corresponding Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 458 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.14.3.1.2-1: Intra-frequency relative CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
Note 2 E-UTRA operating band
condition condition Ês/Iot Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2 ±3 ≥0 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter CSI Ês/Iot is the minimum CSI Ês/Iot of the pair of cells or TPs to which the
requirement applies.
NOTE 3: Void
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.14.3.2 Inter-frequency CSI-RSRP measurements
9.1.14.3.2.1 Absolute CSI-RSRP measurement requirements
In this clause, absolute CSI-RSRP measurement accuracy requirements for discovery signal measurements apply to a
cell or TP on a different carrier frequency from that of the serving cell.
The accuracy requirements in Table 9.1.14.3.2.1-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is specified in Annex B.3.16 for a corresponding Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 459 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.14.3.2.1-1: Inter-frequency absolute CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
E-UTRA operating band
condition condition Ês/Iot Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz Note
dB dB 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±4.5 ±9 ≥0 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±8 ±11 ≥0 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.14.3.2.2 Relative CSI-RSRP measurement requirements
In this section, the relative CSI-RSRP measurement is defined as the CSI-RSRP measured from one cell or TP
compared to the CSI-RSRP measured on a different frequency from another cell or from another TP.
The accuracy requirements in Table 9.1.14.3.2.2-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is specified in Annex B.3.17 for a corresponding Band.
CSI _ RSRP1 dBm − CSI _ RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
Table 9.1.14.3.2.2-1: Inter-frequency relative CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
E-UTRA operating band
condition condition Ês/Iot Note 2 Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±4.5 ±6 ≥0 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter CSI Ês/Iot is the minimum CSI Ês/Iot of the pair of cells or TPs to which the
requirement applies.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 460 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.14.3.3 CSI-RSRP measurement report mapping
The reporting range of CSI-RSRP is defined from -140 dBm to -44 dBm with 1 dB resolution.
The mapping of measured quantity is defined in Table 9.1.14.3.3-1. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 9.1.14.3.3-1: CSI-RSRP measurement report mapping
Reported value Measured quantity value Unit
CSI_RSRP_00 CSI_RSRP < -140 dBm
CSI_RSRP _01 -140 ≤ CSI_RSRP < -139 dBm
CSI_RSRP _02 -139 ≤ CSI_RSRP < -138 dBm
… … …
CSI_RSRP _95 -46 ≤ CSI_RSRP < -45 dBm
CSI_RSRP _96 -45 ≤ CSI_RSRP < -44 dBm
CSI_RSRP _97 -44 ≤ CSI_RSRP dBm
9.1.14.4 RSRQ measurements in discovery signal occasions
Intra-frequency absolute RSRQ measurement accuracy requirements in discovery signal occasions are the same as
specified in Section 9.1.5.1.
Inter-frequency absolute RSRQ measurement accuracy requirements in discovery signal occasions are the same as
specified in Section 9.1.6.1.
Inter-frequency relative RSRQ measurement accuracy requirements in discovery signal occasions are the same as
specified in Section 9.1.6.2.
Measurement report mapping for RSRQ measurements in discovery signal occasions are the same as specified in
Section 9.1.7.
9.1.15 Discovery signal measurements accuracy for E-UTRAN carrier
aggregation
This clause contains requirements on UE capabilities for support of E-UTRA FDD, TDD and TDD-FDD carrier
aggregation when discovery signal [16] is configured. Requirements in this clause are applicable to all carrier
aggregation capable UEs which have been configured with up to four downlink SCell(s). Note : This clause covers
measurement accuracy requirements for frequencies corresponding to those used for the PCell and SCell(s).
Measurements of any other frequency are considered to be inter-frequency measurements covered by the accuracy
requirements in clause 9.1.14.
The requirements in this clause apply for bandwidths defined in the bandwidth combination set for the CA
configurations supported by the UE [5].
9.1.15.1 Requirements for CRS based discovery signal measurements accuracy for
E-UTRAN carrier aggregation
9.1.15.1.1 Primary component carrier accuracy requirement
RSRP and RSRQ measurements of cells on the primary component carrier shall meet the intrafrequency absolute
accuracy requirements in sections 9.1.14.2 and 9.1.14.4. Comparisons between RSRP of cells on the primary
component carrier shall also meet the intra-frequency relative accuracy requirements in sections 9.1.14.2.
9.1.15.1.2 Secondary component carrier accuracy requirement
RSRP and RSRQ measurements of cells on any of the secondary component carrier(s) shall meet the intrafrequency
absolute accuracy requirements in sections 9.1.14.2 and 9.1.14.4. Comparisons between RSRP of cells on the same
secondary component carrier shall meet the intra-frequency relative accuracy requirements in sections 9.1.14.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 461 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.15.1.3 Primary and secondary component carrier relative accuracy requirement
When measurements of cells on the primary component carrier are compared with measurements of cells on any of the
secondary component carrier(s), the applicable relative accuracy requirements are the RSRP and RSRQ inter-frequency
accuracy requirements in sections 9.1.14.2 and 9.1.14.4.
9.1.15.1.4 Secondary component carrier relative accuracy requirement
When measurements of cells on any of the secondary component carrier(s) are compared with measurements of cells on
the other secondary component carrier, the applicable relative accuracy requirements are the RSRP and RSRQ inter-
frequency accuracy requirements in sections 9.1.14.2 and 9.1.14.4.
9.1.15.2 Requirements for CSI-RS based discovery signal measurements accuracy
for E-UTRAN carrier aggregation
9.1.15.2.1 Primary component carrier accuracy requirement
RSRP measurements of cells on the primary component carrier shall meet the intrafrequency absolute accuracy
requirements in sections 9.1.14.3.1.1. Comparisons between RSRP of cells on the primary component carrier shall also
meet the intra-frequency relative accuracy requirements in sections 9.1.14.3.1.2.
9.1.15.2.2 Secondary component carrier accuracy requirement
RSRP measurements of cells on any of the secondary component carrier(s) shall meet the intrafrequency absolute
accuracy requirements in sections 9.1.14.3.1.1. Comparisons between RSRP of cells on the same secondary component
carrier shall meet the intra-frequency relative accuracy requirements in sections 9.1.14.3.1.2.
9.1.15.2.3 Primary and secondary component carrier relative accuracy requirement
When measurements of cells on the primary component carrier are compared with measurements of cells on any of the
secondary component carrier(s), the applicable relative accuracy requirements are the RSRP inter-frequency accuracy
requirements in sections 9.1.14.3.2.2.
9.1.15.2.4 Secondary component carrier relative accuracy requirement
When measurements of cells on any of the secondary component carrier(s) are compared with measurements of cells on
the other secondary component carrier, the applicable relative accuracy requirements are the RSRP inter-frequency
accuracy requirements in sections 9.1.14.3.2.2.
9.1.16 Accuracy requirements for RSRQ measurement on all OFDM
symbols
This clause contains requirements for RSRQ measurement when measurement configuration message received by the
UE contains measRSRQ-OnAllSymbols-r12 parameter in TS 36.331 [2].
Intra-frequency absolute RSRQ measurement accuracy requirements when measured on all OFDM symbols are the
same as specified in Section 9.1.5.1.
Inter-frequency absolute RSRQ measurement accuracy requirements when measured on all OFDM symbols are the
same as specified in Section 9.1.6.1.
Inter-frequency relative RSRQ measurement accuracy requirements when measured on all OFDM symbols are the same
as specified in Section 9.1.6.2.
NOTE: The minimum Io condition in Table 9.1.5.1-1, Table 9.1.6.1-1 and Table 9.1.6.2-1 is expressed as the
average Io per RE over all REs in that symbol.
NOTE: The Io range defined by the minimum and the maximum Io levels in Table 9.1.5.1-1, Table 9.1.6.1-1 and
Table 9.1.6.2-1applies to CRS and non-CRS symbols. Io may be different in different symbols within a
subframe.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 462 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: Iot in Table 9.1.5.1-1, Table 9.1.6.1-1 and Table 9.1.6.2-1 is the received power spectrum density of total
interference and noise averaged over CRS REs.
Intra-frequency absolute WB-RSRQ measurement accuracy requirements when measured on all OFDM symbols are the
same as specified in Section 9.1.5.4.
Inter-frequency absolute WB-RSRQ measurement accuracy requirements when measured on all OFDM symbols are the
same as specified in Section 9.1.6.3.
Inter-frequency relative WB-RSRQ measurement accuracy requirements when measured on all OFDM symbols are the
same as specified in Section 9.1.6.4.
NOTE: The minimum Io condition in Table 9.1.5.4-1, Table 9.1.6.3-1 and Table 9.1.6.4-1 is expressed as the
average Io per RE over all REs in that symbol across all the resource blocks within the
AllowedMeasBandwidth in TS 36.331 [2].
NOTE: The Io1, Io2 and Io range defined by the minimum and the maximum Io levels in Table 9.1.5.4-1, Table
9.1.6.3-1 and Table 9.1.6.4-1 applies to CRS and non-CRS symbols. Io1, Io2 and Io may be different in
different symbols within a subframe.
NOTE: Iot in Table 9.1.5.4-1, Table 9.1.6.3-1 and Table 9.1.6.4-1 is the received power spectrum density of total
interference and noise averaged over CRS REs.
9.1.17 RS-SINR Measurements
9.1.17.1 Measurement Report Mapping
The reporting range of RS-SINR measurement is defined from -23 dB to 40 dB with 0.5 dB resolution.
The mapping of the measured quantity is defined in table 9.1.17.1 -1. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 9.1.17.1-1: RS-SINR measurement report mapping
Reported Value Measured Quantity Value Unit
RS-SINR_000 RS-SINR < -23 dB
RS-SINR_001 -23 ≤ RS-SINR < -22.5 dB
… … …
RS-SINR_126 39.5 ≤ RS-SINR < 40 dB
RS-SINR_127 40 ≤ RS-SINR dB
9.1.17.2 Intra-frequency RS-SINR Measurement Accuracy Requirements
9.1.17.2.1 Absolute RS-SINR Measurement Accuracy Requirements
The requirements for absolute accuracy of intra-frequency RS-SINR in this clause apply to a cell on the same frequency
as that of the serving cell.
The accuracy requirements in Table 9.1.17.2.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.18 for a corresponding Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 463 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.17.2.1-1: Intra-frequency RS-SINR absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
≥-3 dB Note FDD_E, TDD_E -119 -50
±3.0 ±4 5 FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
NOTE 5: The requirements apply for Ês/Iot ≤ 25 dB.
9.1.17.3 Inter-frequency RS-SINR Measurement Accuracy Requirements
9.1.17.3.1 Absolute RS-SINR Measurement Accuracy Requirements
The requirements for absolute accuracy of inter-frequency RS-SINR in this clause apply to a cell that has different
carrier frequency from the serving cell.
The accuracy requirements in Table 9.1.17.3-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.19 for a corresponding Band.
Table 9.1.17.3.1-1: Inter-frequency RS-SINR absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
≥-3 dB Note FDD_E, TDD_E -119 -50
±3.0 ±4 5 FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
NOTE 5: The requirements apply for Ês/Iot ≤ 25 dB.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 464 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.17.3.2 Relative RS-SINR Measurement Accuracy Requirements
The relative accuracy of inter-frequency RS-SINR in this clause is defined as the RS-SINR measured from one cell
compared to the RS-SINR measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.17.3.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.20 for a corresponding Band.
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io - Channel 2_Io | ≤ 20 dB
Table 9.1.17.3.2-1: Inter-frequency RS-SINR relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
Note 4
dB dB dB dBm/15kHz dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
≥-3 dB Note FDD_E, TDD_E -119 -50
±3.5 ±4 6
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±4.0 ±4 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
NOTE 6: The requirements apply for Ês/Iot ≤ 25 dB.
9.1.18 Accuracy Requirements for Measurements under Operation with
Frame Structure 3
9.1.18.1 Introduction
The accuracy requirements in this section are defined for the following physical layer measurements: RSRP, RSRQ,
CSI-RSRP, and RSSI, where the measurements are performed on cells of E-UTRA carriers during the configured
DMTC occasion [2] under operation with frame structure 3 [16].
9.1.18.2 RSRP measurements
9.1.18.2.1 RSRP measurement report mapping
The measurement report mapping for RSRP measurements is as defined in Section 9.1.4.
9.1.18.2.2 Inter-frequency absolute RSRP measurement accuracy requirements
The requirements for absolute accuracy of RSRP in this clause apply to a cell that has a different carrier frequency from
the serving cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 465 ETSI TS 136 133 V14.3.0 (2017-04)
The accuracy requirements in Table 9.1.18.2.2-2 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.23.1 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least four CRS symbols
over two adjacent slots.
Table 9.1.18.2.2-1: RSRP inter-frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz Note
dB dB 2 dBm/BWChannel dBm/BWChannel
±4.5 ±9 ≥-6 dB FS3_G -118 N/A -70
±8 ±11 ≥-6 dB FS3_G N/A -70 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.2.3 Inter-frequency relative RSRP measurement accuracy requirements
The relative accuracy of inter-frequency RSRP measurement is defined as the RSRP measured from one cell compared
to the RSRP measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.18.2.3-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.4 for a corresponding Band
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
The discovery signal occasion does not contain any MBSFN subframe and contains at least four CRS symbols
over two adjacent slots.
Table 9.1.18.2.3-1: RSRP inter-frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
±4.5 ±6 ≥-6 dB FS3_G -118 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.2.4 Intra-frequency absolute RSRP measurement accuracy requirements
NOTE: These requirements are applicable only for CA under operation with frame structure 3 [16].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 466 ETSI TS 136 133 V14.3.0 (2017-04)
The requirements for absolute accuracy of RSRP in this clause apply to a cell on a serving carrier frequency.
The accuracy requirements in Table 9.1.18.2.4-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.21.1 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least four CRS symbols
over two adjacent slots.
Table 9.1.18.2.4-1: RSRP intra frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dBm/15kHz
dB dB dB Note 2 dBm/BWChannel dBm/BWChannel
±4.5 ±9 ≥-6 dB FS3_G -118 N/A -70
±8 ±11 ≥-6 dB FS3_G N/A -70 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.2.5 Intra-frequency relative RSRP measurement accuracy requirements
NOTE: These requirements are applicable only for CA under operation with frame structure 3 [16].
The relative accuracy of RSRP is defined as the RSRP measured from one cell compared to the RSRP measured from
another cell on the same carrier frequency.
The accuracy requirements in Table 9.1.18.2.5-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.22.1 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least four CRS symbols
over two adjacent slots.
Table 9.1.18.2.5-1: RSRP intra frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
Note 4
dB dB dB dBm/15kHz dBm/BWChannel
±2 ±3 ≥-3 dB FS3_G -118 -50
±3 ±3 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 467 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.18.3 RSRQ measurements
9.1.18.3.1 RSRQ measurement report mapping
The measurement report mapping for RSRQ measurements is as defined in Section 9.1.7.
9.1.18.3.2 Inter-frequency absolute RSRQ measurement accuracy requirements
The requirements for absolute accuracy of RSRQ in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.18.3.2-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.23.2 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least four CRS symbols
over two adjacent slots.
Table 9.1.18.3.2-1: RSRQ inter-frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
±2.5 ±4 ≥-3 dB FS3_G -118 -50
±3.5 ±4 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.3.3 Inter-frequency relative RSRQ measurement accuracy requirements
The relative accuracy of RSRQ in inter frequency case is defined as the RSRQ measured from one cell compared to the
RSRQ measured from another cell on a different frequency.
The accuracy requirements in Table 9.1.18.3.3-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.24.2 for a corresponding Band.
RSRP1 dBm − RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
The discovery signal occasion does not contain any MBSFN subframe and contains at least four CRS symbols
over two adjacent slots.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 468 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.18.3.3-1: RSRQ inter-frequency relative accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
±3 ±4 ≥-3 dB FS3_G -118 -50
±4 ±4 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.3.4 Intra-frequency absolute RSRQ measurement accuracy requirements
NOTE: These requirements are applicable only for CA under operation with frame structure 3 [16].
The requirements for absolute accuracy of RSRQ in this clause apply to a cell on a serving carrier frequency.
The accuracy requirements in Table 9.1.18.3.4-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.21.2 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least four CRS symbols
over two adjacent slots.
Table 9.1.18.3.4-1: RSRQ intra frequency absolute accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
±2.5 ±4 ≥-3 dB FS3_G -118 -50
±3.5 ±4 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.4 CSI-RSRP measurements
9.1.18.4.1 CSI-RSRP measurement report mapping
The measurement report mapping for CSI-RSRP measurements is as defined in Section 9.1.14.3.3.
9.1.18.4.2 Inter-frequency absolute CSI-RSRP measurement accuracy requirements
In this clause, absolute CSI-RSRP measurement accuracy requirements for discovery signal measurements apply to a
cell or TP operating under frame structure 3 [3] on a different carrier frequency from that of the serving cell.
The accuracy requirements in Table 9.1.18.4.2-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 469 ETSI TS 136 133 V14.3.0 (2017-04)
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is as specified in Annex B.3.23.3 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least two CSI REs per
resource block within the measured bandwidth in two adjacent slots.
Table 9.1.18.4.2-1: Inter-frequency absolute CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
E-UTRA operating band
condition condition Ês/Iot Minimum Io Maximum Io
groups Note 3
dB dB dB dBm/15kHz Note 2 dBm/BWChannel dBm/BWChannel
±4.5 ±9 ≥0 dB FS3_G -118 N/A -70
±8 ±11 ≥0 dB FS3_G N/A -70 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.4.3 Inter-frequency relative CSI-RSRP measurement accuracy requirements
In this section, the relative CSI-RSRP measurement is defined as the CSI-RSRP measured from one cell or TP
compared to the CSI-RSRP measured on a different frequency from another cell or from another TP, where at least one
measured cell or TP is operating under frame structure 3 [3].
The accuracy requirements in Table 9.1.18.4.3-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is as specified in Annex B.3.24.3 for a corresponding Band.
CSI _ RSRP1 dBm − CSI _ RSRP 2 dBm ≤ 27 dB
| Channel 1_Io -Channel 2_Io | ≤ 20 dB
The discovery signal occasion does not contain any MBSFN subframe and contains at least two CSI REs per
resource block within the measured bandwidth in two adjacent slots.
Table 9.1.18.4.3-1: Inter-frequency relative CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
E-UTRA operating band
condition condition Ês/Iot Note 2 Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
±4.5 ±6 ≥0 dB FS3_G -118 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter CSI Ês/Iot is the minimum CSI Ês/Iot of the pair of cells or TPs to which the
requirement applies.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.4.4 Intra-frequency absolute CSI-RSRP measurement accuracy requirements
NOTE: These requirements are applicable only for CA under operation with frame structure 3 [16].
In this clause, absolute CSI-RSRP measurement accuracy requirements in discovery signal occasions apply to a cell or
TP on a serving carrier frequency operating under frame structure 3 [3].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 470 ETSI TS 136 133 V14.3.0 (2017-04)
The accuracy requirements in Table 9.1.18.4.4-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP,
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is as specified in Annex B.3.21.3 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least two CSI REs per
resource block within the measured bandwidth in two adjacent slots of the same subframe or different subframes.
Table 9.1.18.4.4-1: Intra-frequency absolute CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
E-UTRA operating band
condition condition Ês/Iot Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
±4.5 ±9 ≥0 dB FS3_G -118 N/A -70
±8 ±11 ≥0 dB FS3_G N/A -70 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.4.5 Intra-frequency relative CSI-RSRP measurement accuracy requirements
NOTE: These requirements are applicable only for CA under operation with frame structure 3 [16].
In this section, the relative CSI-RSRP measurement is defined as the CSI-RSRP measured from one cell or TP
compared to the CSI-RSRP measured on the same frequency from another cell or from another TP operating under
frame structure 3 [16]. If two TPs are compared, they may belong to the same or different cells.
The accuracy requirements in Table 9.1.18.4.5-1 are valid under the following conditions:
CSI reference signals in discovery signal occasions are transmitted on one antenna port only from each TP.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
CSI-RSRP is as specified in Annex B.3.22.3 for a corresponding Band.
The discovery signal occasion does not contain any MBSFN subframe and contains at least two CSI REs per
resource block within the measured bandwidth in two adjacent slots of the same subframe or different subframes.
Table 9.1.18.4.5-1: Intra-frequency relative CSI-RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme CSI
E-UTRA operating band
condition condition Ês/Iot Note 2 Minimum Io Maximum Io
groups Note 5
Note 4
dB dB dB dBm/15kHz dBm/BWChannel
±2 ±3 ≥ 0 dB FS3_G -118 -50
±3 ±3 ≥ 0 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter CSI Ês/Iot is the minimum CSI Ês/Iot of the pair of cells or TPs to which the
requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 471 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.18.5 RSSI measurements
9.1.18.5.1 RSSI measurement report mapping
The reporting range of RSSI measurement is defined from -100 dBm to -25 dBm with 1 dBm resolution.
The mapping of the measured quantity is defined in table 9.1.18.5.1-1. The range in the signalling may be larger than
the guaranteed accuracy range.
Table 9.1.18.5.1-1: RSSI measurement report mapping
Reported value Measured quantity value Unit
RSSI_00 RSSI < -100 dBm
RSSI_01 -100 ≤ RSSI < -99 dBm
RSSI_02 -99 ≤ RSSI < -98 dBm
… … …
RSSI_74 -27 ≤ RSSI < -26 dBm
RSSI_75 -26 ≤ RSSI < -25 dBm
RSSI_76 -25 ≤ RSSI dBm
9.1.18.5.2 Intra-frequency absolute RSSI measurement accuracy requirements
NOTE: These requirements are applicable only for CA under operation with frame structure 3 [16].
The intra-frequency RSSI requirements are specified in Table 9.1.18.5.2-1. The requirements apply for any configured
RSSI measDuration [2], provided that:
- All symbols duing each RSSI measurement duration are available for RSSI sampling within the same reporting
interval.
Table 9.1.18.5.2-1: Intra-frequency RSSI accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dBm/15kHz Note 3 dBm/BWChannel
±2.5 ±5.5 FS3_G -118 -50
±4.5 ±7.5 Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as
for the corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections
B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.1.18.5.3 Inter-frequency absolute RSSI measurement accuracy requirements
The inter-frequency RSSI requirements are the same as specified in Section 9.1.18.5.2.
9.1.18.6 Channel occupancy measurements
9.1.18.6.1 Intra-frequency channel occupancy measurement accuracy requirements
NOTE: These requirements are applicable only for CA under operation with frame structure 3 [16].
The UE shall be able to correctly evaluate the intra-frequency channel occupancy configured according to 36.331 [2],
provided that the following conditions are met:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 472 ETSI TS 136 133 V14.3.0 (2017-04)
- All symbols during each RSSI measurement duration are available for RSSI sampling within the same reporting
interval,
- RSSI at the UE receiver meets the following condition with respect to the configured
channelOccupancyThreshold [2]:
RSSI at the UE receiver is below channelOccupancyThreshold- Δ RSSI , or
RSSI at the UE receiver is above channelOccupancyThreshold+ Δ RSSI ,
where Δ RSSI is the applicable RSSI measurement accuracy value from the RSSI measurement accuracy
requirements specified in Section 9.1.18.5.2.
9.1.18.6.2 Inter-frequency channel occupancy measurement accuracy requirements
The UE shall be able to correctly evaluate the inter-frequency channel occupancy configured according to 36.331 [2],
provided that the following conditions are met:
- All symbols during each RSSI measurement duration are available for RSSI sampling within the same reporting
interval,
- RSSI at the UE receiver meets the following condition with respect to the configured
channelOccupancyThreshold [2]:
RSSI at the UE receiver is below channelOccupancyThreshold- Δ RSSI , or
RSSI at the UE receiver is above channelOccupancyThreshold+ Δ RSSI ,
where Δ RSSI is the applicable RSSI measurement accuracy value from the RSSI measurement accuracy
requirements specified in Section 9.1.18.5.3.
9.1.19 Accuracy Requirements for Carrier Aggregation for Measurements
under Operation with Frame Structure 3
9.1.19.1 Introduction
The accuracy requirements in this section are defined for the following physical layer measurements: RSRP, RSRQ,
CSI-RSRP, and RSSI, where the measurements are performed on cells of E-UTRA carriers during the configured
DMTC occasion [2] under operation with frame structure 3 [16].
9.1.19.2 Accuracy requirements for measurements on SCC
The requirements in this section are for the measurements on cells of E-UTRA carriers operated under frame structure 3
on one SCC.
Absolute RSRP measurements of cells on SCC shall meet the intra-frequency absolute accuracy requirements in Section
9.1.18.2.4.
Comparisons between RSRP measurements of cells on the same SCC shall meet the intra-frequency relative accuracy
requirements in Section 9.1.18.2.5.
Absolute RSRQ measurements of cells on SCC shall meet the intra-frequency absolute accuracy requirements in
Section 9.1.18.3.4.
CSI-RSRP measurements of cells on SCC shall meet the intra-frequency absolute accuracy requirements in Section
9.1.18.4.4.
Comparisons between CSI-RSRP measurements of cells on the same SCC shall meet the intra-frequency relative
accuracy requirements in Section 9.1.18.4.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 473 ETSI TS 136 133 V14.3.0 (2017-04)
RSSI measurements on SCC shall meet the intra-frequency absolute accuracy requirements in Section 9.1.18.5.3.
9.1.19.3 Relative accuracy requirements for measurements on different SCCs
The requirements in this section are for the measurements on cells of E-UTRA carriers operated under frame structure 3
on two different SCCs.
When RSRP measurements of cells on any of the SCC are compared with RSRP measurements of cells on the other
SCC, the applicable relative accuracy requirements are the inter-frequency relative RSRP measurement accuracy
requirements in Section 9.1.18.2.3.
When RSRQ measurements of cells on any of the SCC are compared with RSRQ measurements of cells on the other
SCC, the applicable relative accuracy requirements are the inter-frequency relative RSRQ measurement accuracy
requirements in Section 9.1.18.3.3.
When CSI-RSRP measurements of cells on any of the SCC are compared with CSI-RSRP measurements of cells on the
other SCC, the applicable relative accuracy requirements are the inter-frequency relative CSI-RSRP measurement
accuracy requirements in Section 9.1.18.4.3.
9.1.20 SFN and Subframe Time Difference (SSTD)
9.1.20.1 SSTD Accuracy Requirement
The SFN and subframe time difference (SSTD) is measured between MeNB and SeNB.
The accuracy requirements in Table 9.1.20.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
No changes to the uplink transmission timing are applied during the measurement period.
RSRP|dBm according to Annex B.3.5 for a corresponding Band
Table 9.1.20.1-1: SFN and subframe time difference measurement accuracy
Conditions
MIN(PCell downlink Io Note 1 range
transmission
Accuracy
Ês/Iot Bandwidth, PSCell E-UTRA operating
Minimum Io Maximum Io
downlink transmission band groups Note 6
Bandwidth)
Ts Note 2 dB MHz dBm/15kHz Note 5 dBm/BWChannel
Note 7,
FDD_A
-121 -50
TDD_A
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±52 ≥-3 dB ≥1.4 MHz FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G Note 4 -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±40 ≥-3 dB ≥ 3 MHz Note 3 Note 3 Note 3
NOTE 1: When in dBm/15kHz, the minimum Io condition is expressed as the average Io per RE over all REs in
that symbol. Io may be different in different symbols within a subframe.
NOTE 2: Ts is the basic timing unit defined in TS 36.211.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding requirement with downlink bandwidth ≥1.4 MHz.
NOTE 4: Except Band 29.
NOTE 5: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 6: E-UTRA operating band groups are as defined in Section 3.5.
NOTE 7: Except Band 32.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 474 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.20.2 SSTD Measurement Report Mapping
SFN and subframe timing difference (SSTD) measurement report comprises 3 elements:
SFN offset between MeNB and SeNB (ΔX)
Reporting range of ΔX is between frame number # 0 to frame number # 1023 as defined in TS 36.331 [2].
Frame boundary offset between MeNB and SeNB (ΔY)
Reporting range of ΔY is between subfrane number #-5 and subframe number# 4 as defined in TS 36.331 [2].
Subframe boundary offset between MeNB and SeNB (ΔZ)
The reporting range of value of ΔZ is within [-1320Ts, -700Ts] and [700Ts, 1320Ts] with reporting granularity
of 10Ts.
The mapping of measured Subframe boundary offset (ΔZ) is defined in Table 9.1.20.2-1.
Table 9.1.20.2-1: SSTD report mapping
Reported Value Measured Quantity Value Unit
SUBFRAME_BOUNDARY_OFFSET_00 ΔZ ≤ -1320 Ts
SUBFRAME_BOUNDARY_OFFSET_01 -1320 < ΔZ ≤ -1310 Ts
SUBFRAME_BOUNDARY_OFFSET_02 -1310 < ΔZ ≤ -1300 Ts
… … …
SUBFRAME_BOUNDARY_OFFSET_62 -710 < ΔZ ≤ -700 Ts
SUBFRAME_BOUNDARY_OFFSET_63 -700 < ΔZ ≤ 0 Ts
SUBFRAME_BOUNDARY_OFFSET_64 0 < ΔZ ≤ 700 Ts
SUBFRAME_BOUNDARY_OFFSET_65 700 < ΔZ ≤ 710 Ts
… … …
SUBFRAME_BOUNDARY_OFFSET_125 1300 < ΔZ ≤ 1310 Ts
SUBFRAME_BOUNDARY_OFFSET_126 1310 < ΔZ ≤ 1320 Ts
SUBFRAME_BOUNDARY_OFFSET_127 1320 < ΔZ Ts
9.1.21 Measurement accuracy for UE category M1
9.1.21.1 Intra-frequency Absolute RSRP Accuracy for UE category M1 with CE mode
A
The requirements for absolute accuracy of RSRP in this clause apply to a cell on the same frequency as that of the
serving cell for UE category M1.
The accuracy requirements in Table 9.1.21.1-1 and Table 9.1.21.1-2 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for RSRP measurement assuming
measured cell is identified cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 475 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.21.1-1: RSRP Intra frequency absolute accuracy for UE category M1 with CE mode A for
FDD and TDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_D -119.5 N/A -70
FDD_E, TDD_E -119 N/A -70
±7 ±10 ≥-6 dB
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD_D,
±9 ±12 ≥-6 dB FDD_E, TDD_E, FDD_F, N/A -70 -50
FDD_G, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
Table 9.1.21.1-2: RSRP Intra frequency absolute accuracy for UE category M1 with CE mode A for
HD-FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A -121 N/A -70
FDD_D -119.5 N/A -70
FDD_E -119 N/A -70
±7 ±10 ≥-6 dB
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_N -114.5 N/A -70
FDD_A, FDD_D, FDD_E,
±9 ±12 ≥-6 dB N/A -70 -50
FDD_F, FDD_G, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.21.2 Intra-frequency Relative Accuracy of RSRP for UE category M1 with CE
mode A
The relative accuracy of RSRP is defined as the RSRP measured from one cell compared to the RSRP measured from
another cell on the same frequency for category M1 UE.
The accuracy requirements in Table 9.1. 21.2-1 and Table 9.1. 21.2-2 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.8 for a corresponding Band.
At least 1 DL subframe per radio frame of measured cell is available at the UE for RSRP measurement assuming
measured cell is identified cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 476 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.21.2-1: RSRP Intra frequency relative accuracy for UE category M1 with CE mode A for FDD
and TDD
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_D -119.5 -50
FDD_E, TDD_E -119 -50
±3 ±4 ≥-3 dB
FDD_F -118.5 -50
FDD_G -118 -50
FDD_N -114.5 -50
±4 ±4 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
Table 9.1.21.2-2: RSRP Intra frequency relative accuracy for UE category M1 with CE mode A for HD-
FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
Note 4
dB dB dB dBm/15kHz dBm/BWChannel
FDD_A -121 -50
FDD_D -119.5 -50
FDD_E -119 -50
±3 ±4 ≥-3 dB
FDD_F -118.5 -50
FDD_G -118 -50
FDD_N -114.5 -50
±4 ±4 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.21.3 Intra-frequency Absolute RSRP Accuracy for UE category M1 with CE mode
B
The requirements for absolute accuracy of RSRP in this clause apply to a cell on the same frequency as that of the
serving cell for UE category M1.
The accuracy requirements in Table 9.1.21.3-1 and Table 9.1.21.3-2 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP|dBm according to Annex B.3.1 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for RSRP measurement assuming
measured cell is identified cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 477 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.21.3-1: RSRP Intra frequency absolute accuracy for UE category M1 with CE mode B for
FDD and TDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
- FDD_A, TDD_A -121 N/A -70
±8 ±11 15≤Ês/Iot≤- FDD_D -119.5 N/A -70
12 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
±7 ±10 ≥-12 dB FDD_G -118 N/A -70
FDD_N -114.5 N/A -70
-
±10 ±13 15≤Ês/Iot≤- FDD_A, TDD_A, FDD_D,
12 dB FDD_E, TDD_E, FDD_F, N/A -70 -50
FDD_G, FDD_N
±9 ±12 ≥-12 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
Table 9.1.21.3-2: RSRP Intra frequency absolute accuracy for UE category M1 with CE mode B for
HD-FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
- FDD_A -121 N/A -70
±8 ±11 15≤Ês/Iot≤- FDD_D -119.5 N/A -70
12 dB FDD_E -119 N/A -70
FDD_F -118.5 N/A -70
±7 ±10 ≥-12 dB FDD_G -118 N/A -70
FDD_N -114.5 N/A -70
-
±10 ±13 15≤Ês/Iot≤- FDD_A, FDD_D, FDD_E,
N/A -70 -50
12 dB FDD_F, FDD_G, FDD_N
±9 ±12 ≥-12 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.21.4 Intra-frequency Relative Accuracy of RSRP for UE category M1 with CE
mode B
The relative accuracy of RSRP is defined as the RSRP measured from one cell compared to the RSRP measured from
another cell on the same frequency for category M1 UE.
The accuracy requirements in Table 9.1.21.4-1 and Table 9.1.21.4-2 are valid under the following conditions:
Cell specific reference signals are transmitted either from one, two or four antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
RSRP1,2|dBm according to Annex B.3.8 for a corresponding Band.
At least 1 DL subframe per radio frame of measured cell is available at the UE for RSRP measurement assuming
measured cell is identified cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 478 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.21.4-1: RSRP Intra frequency relative accuracy for UE category M1 with CE mode B for FDD
and TDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot Note 2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_D -119.5 -50
FDD_E, TDD_E -119 -50
±4 ±4 ≥-12 dB
FDD_F -118.5 -50
FDD_G -118 -50
FDD_N -114.5 -50
-
±5 ±5 15≤Ês/Iot≤- Note 3 Note 3 Note 3
12 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
Table 9.1.21.4-2: RSRP Intra frequency relative accuracy for UE category M1 with CE mode B for HD-
FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot Note 2 E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A -121 -50
FDD_D -119.5 -50
FDD_E -119 -50
±4 ±4 ≥-12 dB
FDD_F -118.5 -50
FDD_G -118 -50
FDD_N -114.5 -50
-
±5 ±5 15≤Ês/Iot≤- Note 3 Note 3 Note 3
12 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of cells to which the requirement applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA operating band groups are as defined in Section 3.5.
9.1.21.5 RSRP Measurement Report Mapping
The reporting range of RSRP is the same as defined in section 9.1.4.
9.1.22 Measurement accuracy for UE Category NB1
9.1.22.1 Intra-frequency Absolute NRSRP Accuracy for UE Category NB1
The requirements for absolute accuracy of NRSRP in this clause apply to a cell on the same frequency as that of the
serving cell for UE Category NB1 for stand-alone, guard-band and in-band deployments.
The accuracy requirements in Table 9.1.22.1-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one or two ports.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 479 ETSI TS 136 133 V14.3.0 (2017-04)
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
NRSRP|dBm according to Annex B.3.X1 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for NRSRP measurement
assuming measured cell is identified cell.
Table 9.1.22.1-1: NRSRP Intra frequency absolute accuracy for UE Category NB1 for HD-FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 2
dB dB dB dBm/15kHz dBm/BWChannel dBm/BWChannel
±6 ±9 ≥-6 dB NFDD_G [-118] N/A [-70]
±8 ±11 ≥-6 dB NFDD_G N/A [-70] [-50]
≥-15
±10.3 ±13.3 Ês/Iot NFDD_G [-118] N/A [-70]
≥-6 dB
≥-15
±12.3 ±15.3 Ês/Iot NFDD_G N/A [-70] [-50]
≥-6 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: E-UTRA operating band groups are as defined in Section 3.5.
9.1.22.2 Void
9.1.22.3 Intra-frequency Absolute NRSRQ Accuracy for UE Category NB1 in Normal
Mode
The requirements for absolute accuracy of NRSRQ in this clause apply to a cell on the same frequency as that of the
serving cell for NB-IoT UE for stand-alone, guard-band and in-band deployments.
The accuracy requirements in Table 9.1.22.3-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one or two antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
NRSRP|dBm according to Annex B.3.1 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for NRSRQ measurement
assuming measured cell is identified cell.
Table 9.1.22.3-1: NRSRQ Intra frequency absolute accuracy for UE Category NB1 for HD-FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band groups
condition condition Note 3 Minimum Io Maximum Io
dB dB dB dBm/15kHz dBm/BWChannel
±5.2 ±8.2 ≥-3 dB NFDD_G [-118] [-70]
±7.2 ±10.2 ≥-6 dB Note 2 Note 2 Note 2
≥-15 Ês/Iot
±9.5 ±12.5 NFDD_G [-118] [-70]
≥-6 dB
≥-15 Ês/Iot
±11.5 ±14.5 Note 2 Note 2 Note 2
≥-6 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
highest accuracy requirement.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 480 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.22.4 Void
9.1.22.5 Inter-frequency Absolute NRSRP Accuracy for UE Category NB1
The requirements for absolute accuracy of NRSRP in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.22.5-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one or two antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
NRSRP|dBm according to Annex B.3.3 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for NRSRP measurement
assuming measured cell is identified cell.
Table 9.1.22.5-1: NRSRP Inter frequency absolute accuracy for UE Category NB1 for HD-FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 2
dB dB dB dBm/15kHz dBm/BWChannel dBm/BWChannel
±6 ±9 ≥-6 dB NFDD_G [-118] N/A [-70]
±8 ±11 ≥-6 dB NFDD_G N/A [-70] [-50]
≥-15
±10.3 ±13.3 Ês/Iot NFDD_G [-118] N/A [-70]
≥-6 dB
≥-15
±12.3 ±15.3 Ês/Iot NFDD_G N/A [-70] [-50]
≥-6 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: E-UTRA operating band groups are as defined in Section 3.5.
9.1.22.6 Void
9.1.22.7 Inter-frequency Absolute NRSRQ Accuracy for UE Category NB1
The requirements for absolute accuracy of NRSRQ in this clause apply to a cell that has different carrier frequency from
the serving cell.
The accuracy requirements in Table 9.1.22.7-1 are valid under the following conditions:
Cell specific reference signals are transmitted either from one or two antenna ports.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
NRSRP|dBm according to Annex B.3.26 for a corresponding Band
At least 1 DL subframe per radio frame of measured cell is available at the UE for NRSRQ measurement
assuming measured cell is identified cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 481 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.1.22.7-1: NRSRQ Inter frequency absolute accuracy for UE Category NB1 for HD-FDD
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band groups
condition condition Note 3 Minimum Io Maximum Io
dB dB dB dBm/15kHz dBm/BWChannel
±5.2 ±8.2 ≥-3 dB NFDD_G [TBD] [TBD]
±7.2 ±10.2 ≥-6 dB Note 2 Note 2 Note 2
≥-15 Ês/Iot
±9.5 ±12.5 NFDD_G [-118] [-70]
≥-6 dB
≥-15 Ês/Iot
±11.5 ±14.5 Note 2 Note 2 Note 2
≥-6 dB
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
highest accuracy requirement.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.1.22.8 Void
9.1.23 Power Headroom for UE Category NB1
The requirements in this clause shall apply for power headroom for UE Category NB1 as defined in [31].
The power headroom provides the serving eNB with information about the differences between the UE configured
maximum output power (PCMAX,) defined in TS 36.101 [5] and the estimated power for UL-NSCH transmission of the
serving cell [3].
9.1.23.1 Period
The reported power headroom shall be estimated over 1 slot of NPUSCH transmissions.
9.1.23.2 Reporting Delay
The power headroom reporting delay is defined as the time between the beginning of the power headroom reference
period and the time when the UE starts transmitting the power headroom over the radio interface. The reporting delay of
the power headroom shall be 0 ms, which is applicable for all configured triggering mechanisms for power headroom
reporting.
9.1.23.3 Report Mapping for UE Category NB1
9.1.23.3.1 Report Mapping for UE Category NB1 in normal coverage
The power headroom reporting range is from -23 ...+11 dB for UE category NB1 in normal coverage. Table 9.1.23.3.1-
1 defines the report mapping which is applicable when the enhanced coverage level 0 is selected during random access
procedure [17].
Table 9.1.23.3-1: Power headroom report mapping for UE category NB1 in normal coverage
Reported value Measured quantity value (dB)
POWER_HEADROOM_0 -23 ≤ PH < 5
POWER_HEADROOM_1 5 ≤ PH < 8
POWER_HEADROOM_2 8 ≤ PH < 11
POWER_HEADROOM_3 PH ≥ 11
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 482 ETSI TS 136 133 V14.3.0 (2017-04)
9.1.23.3.2 Report Mapping for UE Category NB1 in enhanced coverage
The power headroom reporting range is from -23 ...+6 dB for UE category NB1 in enhanced coverage. Table
9.1.23.3.2-1 defines the report mapping which is applicable when the enhanced coverage level other than 0 is selected
during random access procedure [17].
Table 9.1.23.3.2-1: NB-IOT power headroom report mapping in enhanced coverage
Reported value Measured quantity value (dB)
POWER_HEADROOM_0 -23 ≤ PH < -10
POWER_HEADROOM_1 -10 ≤ PH < -2
POWER_HEADROOM_2 -2 ≤ PH < 6
POWER_HEADROOM_3 PH ≥ 6
9.2 UTRAN FDD Measurements
The requirements in this clause are applicable for a UE:
- in state RRC_CONNECTED
- performing measurements according to clause 8.1.2.4 with appropriate measurement gaps
- that is synchronised to the cell that is measured.
The reported measurement result after layer 1 filtering shall be an estimate of the average value of the measured
quantity over the measurement period. The reference point for the measurement result after layer 1 filtering is referred
to as point B in the measurement model described in TS 25.302 [6].
The accuracy requirements in this clause are valid for the reported measurement result after layer 1 filtering. The
accuracy requirements are verified from the measurement report at point D in the measurement model having the layer
3 filtering disabled.
9.2.1 UTRAN FDD CPICH RSCP
NOTE: This measurement is for handover between E-UTRAN and UTRAN FDD and for SON.
The requirements in this clause are valid for terminals supporting this capability.
The measurement period for RRC_CONNECTED state is specified in clauses 8.1.2.4.1 and 8.1.2.4.2.
In RRC_CONNECTED state the accuracy requirements shall meet the absolute accuracy requirements in table 9.2.1-1,
under the following conditions:
- CPICH Ec/Io condition for a detectable cell is as specified in clauses 8.1.2.4.1, 8.1.2.4.2, 8.1.2.4.7, 8.1.2.4.8;
- SCH_Ec/Io condition for a detectable cell is as specified in clauses 8.1.2.4.1, 8.1.2.4.2, 8.1.2.4.7, 8.1.2.4.8.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 483 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.2.1-1: UTRAN FDD CPICH_RSCP absolute accuracy
Accuracy Conditions
Normal Extreme Io range
condition condition UTRA operating bands Minimum Io Maximum Io
dB dB dBm/3.84 MHz dBm/3.84 MHz
Band I, IV, VI, X XI, XIX and XXI -94 -70
Band IX -93 -70
Band II, V and VII -92 -70
±6 ±9
Band III, VIII, XII, XIII, XIV , XX and
-91 -70
XXII
Band XXV, XXVI Note 1 -90.5 -70
±8 ±11 Note 2 -70 -50
NOTE 1: For Band XXVI, the condition has the minimum Io of -92 dBm/3.84 MHz when the carrier
frequency of the assigned UTRA channel is within 869-894 MHz for the UE which supports both
Band V and Band XXVI operating frequencies.
NOTE 2: The same bands apply for this requirement as for the corresponding highest accuracy
requirement.
If the UE, in RRC_CONNECTED state, needs measurement gaps to perform UTRAN FDD measurements, the relevant
UTRAN FDD measurement procedure and measurement gap pattern stated in clause 8.1.2.4 shall apply.
The reporting range and mapping specified for FDD CPICH RSCP in TS 25.133 [18] shall apply.
9.2.2 Void
9.2.3 UTRAN FDD CPICH Ec/No
NOTE: This measurement is for handover between E-UTRAN and UTRAN FDD and for SON.
The requirements in this clause are valid for terminals supporting this capability.
The measurement period for RRC_CONNECTED state is specified in clauses 8.1.2.4.1 and 8.1.2.4.2.
In RRC_CONNECTED state the accuracy requirements shall be the same as the inter-frequency measurement accuracy
requirements for FDD CPICH Ec/No in TS 25.133 [18].
If the UE, in RRC_CONNECTED state, needs measurement gaps to perform UTRAN FDD measurements, the UTRAN
FDD measurement procedure and measurement gap pattern stated in clause 8.1.2.4.1 shall apply.
The reporting range and mapping specified for FDD CPICH Ec/No in TS 25.133 [18] shall apply.
9.3 UTRAN TDD Measurements
The requirements in this clause are applicable for a UE:
- in state RRC_CONNECTED
- performing measurements according to clause 8.1.2.4 with appropriate measurement gaps
- that is synchronised to the cell that is measured.
The reported measurement result after layer 1 filtering shall be an estimate of the average value of the measured
quantity over the measurement period. The reference point for the measurement result after layer 1 filtering is referred
to as point B in the measurement model described in TS 25.302 [6].
The accuracy requirements in this clause are valid for the reported measurement result after layer 1 filtering. The
accuracy requirements are verified from the measurement report at point D in the measurement model having the layer
3 filtering disabled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 484 ETSI TS 136 133 V14.3.0 (2017-04)
9.3.1 UTRAN TDD P-CCPCH RSCP
NOTE: This measurement is for handover between E-UTRAN and UTRAN TDD and for SON.
The requirements in this clause are valid for terminals supporting this capability.
The measurement period for RRC_CONNECTED state is specified in clauses 8.1.2.4.3 and 8.1.2.4.4.
In RRC_CONNECTED state the accuracy requirements shall be the same as the inter-frequency measurement accuracy
requirements for TDD P-CCPCH in TS 25.123 [19].
If the UE, in RRC_CONNECTED state, needs measurement gaps to perform UTRAN TDD measurements, the relevant
UTRAN TDD measurement procedure and measurement gap pattern stated in clause 8.1.2.4 shall apply.
The reporting range and mapping specified for TDD P-CCPCH RSCP in TS 25.123 [19] shall apply.
9.3.2 Void
9.3.3 Void
9.4 GSM Measurements
The requirements in this clause are applicable for a UE:
- in state RRC_CONNECTED
- performing measurements according to clause 8.1.2.4.5 with appropriate measurement gaps
- that is synchronised to the cell that is measured.
The reported measurement result after layer 1 filtering shall be an estimate of the average value of the measured
quantity over the measurement period. The reference point for the measurement result after layer 1 filtering is referred
to as point B in the measurement model described in TS 25.302 [6].
The accuracy requirements in this clause are valid for the reported measurement result after layer 1 filtering. The
accuracy requirements are verified from the measurement report at point D in the measurement model having the layer
3 filtering disabled.
9.4.1 GSM carrier RSSI
NOTE: This measurement is for handover between E-UTRAN and GSM.
The requirements in this clause are valid for terminals supporting this capability.
The measurement period for RRC_CONNECTED state is specified in clause 8.1.2.4.5.
In RRC_CONNECTED state the measurement accuracy requirements for RXLEV in TS 45.008 [8] shall apply.
If the UE, in RRC_CONNECED state, needs measurement gaps to perform GSM measurements, the GSM
measurement procedure and measurement gap pattern stated in clause 8.1.2.4.5 shall apply.
The reporting range and mapping specified for RXLEV in TS 45.008 [8] shall apply.
9.5 CDMA2000 1x RTT Measurements
The requirements in this clause are applicable for a UE:
- in RRC_CONNECTED state.
- synchronised to the cell that is measured.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 485 ETSI TS 136 133 V14.3.0 (2017-04)
9.5.1 CDMA2000 1x RTT Pilot Strength
NOTE: This measurement is for handover between E-UTRAN and cdma2000 1 x RTT.
The requirements in this clause are valid for terminals supporting this capability.
CDMA2000 1xRTT Pilot Strength defined in sub-clause 5.1.10 of [4] shall meet the performance requirement defined
in sub-clause 3.2.4 of [14] on the cdma2000 1xRTT neighbour cells indicated by the serving eNode B.
9.6 PCMAX,c
For a UE configured with a secondary cell, the UE is required to report the UE configured maximum output power
(PCMAX,c) together with the power headroom. This clause defines the requirements for the PCMAX,c reporting.
9.6.1 Report Mapping
The PCMAX,c reporting range is defined from -29dBm to 33 dBm with 1 dB resolution. Table 9.6.1-1 defines the
reporting mapping.
Table 9.6.1-1 Mapping of PCMAX,c
Reported value Measured quantity value Unit
PCMAX_C_00 PCMAX,c < -29 dBm
PCMAX_C_01 -29 ≤ PCMAX,c < -28 dBm
PCMAX_C_02 -28 ≤ PCMAX,c < -27 dBm
… … …
PCMAX_C_61 31 ≤ PCMAX,c < 32 dBm
PCMAX_C_62 32 ≤ PCMAX,c < 33 dBm
PCMAX_C_63 33 ≤ PCMAX,c dBm
9.6.2 Estimation Period
When extendedPHR is configured and UE is required to include PCMAX,c in Extended PHR MAC control element as
defined in subclause 5.4.6 in [17], the UE shall calculate the PCMAX,c per activated serving cell c for UL-SCH
transmission according to subclause 6.2.5A of TS 36.101 [5] over 1 subframe.
9.6.3 Reporting Delay
The PCMAX,c reporting delay is defined as the time between the beginning of the PCMAX,c reference period and the time
when the UE starts transmitting PCMAX,c over the radio interface. The reporting delay of the PCMAX,c shall be 0 ms, which
is applicable for all configured triggering mechanisms for PCMAX,c reporting.
9.7 IEEE802.11 Measurements
The requirements in this clause are applicable for a UE:
- in RRC_CONNECTED state.
- synchronised to the IEEE 802.11 access point that is measured.
9.7.1 WLAN RSSI
NOTE: This measurement is for access network selection and traffic steering between E-UTRAN and WLAN.
The requirements in this clause are valid for terminals supporting this capability.
WLAN RSSI defined in sub-clause 5.1.16 of [4] shall meet the performance requirement defined in [32].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 486 ETSI TS 136 133 V14.3.0 (2017-04)
9.7.2 WLAN RSSI Measurement Report Mapping
This sub-clause 9.7.2 doesn’t apply to LPP WLAN-MeasurementInformation. The WLAN RSSI measurement report
mapping is defined in [32] for LPP WLAN-MeasurementInformation.
The reporting range of WLAN RSSI is defined from -100 dBm to 40 dBm with 1 dB resolution.
The mapping of measured quantity is defined in Table 9.7.2-1. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 9.7.2-1: WLAN RSSI measurement report mapping
Reported value Measured quantity value Unit
WLAN RSSI_00 WLAN RSSI < -100 dBm
WLAN RSSI_01 -100 ≤ WLAN RSSI < -99 dBm
WLAN RSSI_02 -99 ≤ WLAN RSSI < -98 dBm
… … …
WLAN RSSI_139 38 ≤ WLAN RSSI < 39 dBm
WLAN RSSI_140 39 ≤ WLAN RSSI < 40 dBm
WLAN RSSI_141 40 ≤ WLAN RSSI dBm
9.8 MBSFN Measurements
9.8.1 Introduction
MBSFN measurements include MBSFN RSRP, MBSFN RSRQ, and MCH BLER, which are defined in [4]. The
measurements are used for MDT.
9.8.2 MBSFN RSRP
9.8.2.1 Absolute MBSFN RSRP measurement accuracy requirements
The requirements for absolute accuracy of MBSFN RSRP in this clause apply to any carrier, which may be the same as
or different from any serving unicast carrier, where PMCH is received while meeting performance requirements in
Section 10 of [5].
The accuracy requirements in Table 9.8.2.1-1 are valid under the following conditions:
MBSFN RS are transmitted from antenna port 4 in the MBSFN subframes where PMCH is received.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
MBSFN RSRP|dBm/15kHz is the same as RSRP|dBm/15kHz specified in Annex B.3.1 for each corresponding
Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 487 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.8.2.1-1: Absolute MBSFN RSRP measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A, TDD_A -121 N/A -70
FDD_B -120.5 N/A -70
FDD_C, TDD_C -120 N/A -70
FDD_D -119.5 N/A -70
±4.5 ±9 ≥-6 dB FDD_E, TDD_E -119 N/A -70
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_H -117.5 N/A -70
FDD_N -114.5 N/A -70
FDD_A, TDD_A, FDD B,
FDD_C, TDD_C, FDD_D,
±8 ±11 ≥-6 dB N/A -70 -50
FDD_E, TDD_E, FDD_F,
FDD_G, FDD_H, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA operating band groups are as defined in Section 3.5.
9.8.2.2 MBSFN RSRP measurement report mapping
The reporting range of MBSFN RSRP is defined from -140 dBm to -44 dBm with 1 dB resolution.
The mapping of measured quantity is defined in Table 9.8.2.2-1. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 9.8.2.2-1: MBSFN RSRP measurement report mapping
Reported value Measured quantity value Unit
MBSFN_RSRP_00 MBSFN_RSRP < -140 dBm
MBSFN_RSRP_01 -140 ≤ MBSFN_RSRP < -139 dBm
MBSFN_RSRP_02 -139 ≤ MBSFN_RSRP < -138 dBm
… … …
MBSFN_RSRP_95 -46 ≤ MBSFN_RSRP < -45 dBm
MBSFN_RSRP_96 -45 ≤ MBSFN_RSRP < -44 dBm
MBSFN_RSRP_97 -44 ≤ MBSFN_RSRP dBm
9.8.3 MBSFN RSRQ
9.8.3.1 Absolute MBSFN RSRQ measurement accuracy requirements
The requirements for absolute accuracy of MBSFN RSRQ in this clause apply to any carrier, which may be the same as
or different from a serving unicast carrier, where PMCH is received while meeting performance requirements in Section
10 of [5].
The accuracy requirements in Table 9.8.3.1-1 are valid under the following conditions:
MBSFN RS are transmitted from antenna port 4 in the MBSFN subframes where PMCH is received.
Conditions defined in 36.101 Clause 7.3 for reference sensitivity are fulfilled.
MBSFN RSRP|dBm/15kHz is the same as RSRP|dBm/15kHz specified in Annex B.3.1 for each corresponding
Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 488 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.8.3.1-1: Absolute MBSFN RSRQ measurement accuracy
Accuracy Conditions
Io Note 1 range
Normal Extreme
Ês/Iot E-UTRA operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dB dBm/15kHz Note 3 dBm/BWChannel
FDD_A, TDD_A -121 -50
FDD_B -120.5 -50
FDD_C, TDD_C -120 -50
FDD_D -119.5 -50
±2.5 ±4 ≥-3 dB FDD_E, TDD_E -119 -50
FDD_F -118.5 -50
FDD_G -118 -50
FDD_H -117.5 -50
FDD_N -114.5 -50
±3.5 ±4 ≥-6 dB Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for the corresponding
highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 4: E-UTRA operating band groups are as defined in Section 3.5.
9.8.3.2 MBSFN RSRQ measurement report mapping
The reporting range of MBSFN RSRQ is defined from -23 dB to -7.5 dB with 0.5 dB resolution.
The mapping of measured quantity is defined in Table 9.8.3.2-1. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 9.8.3.2-1: MBSFN RSRQ measurement report mapping
Reported value Measured quantity value Unit
MBSFN_RSRQ_00 MBSFN_RSRQ < -23 dB
MBSFN_RSRQ_01 -23 ≤ MBSFN_RSRQ < -22.5 dB
MBSFN_RSRQ_02 -22.5 ≤ MBSFN_RSRQ < -22 dB
… … …
MBSFN_RSRQ_30 -8.5 ≤ MBSFN_RSRQ < -8 dB
MBSFN_RSRQ_31 -8 ≤ MBSFN_RSRQ dB
9.8.4 MCH BLER
MCH BLER shall be measured as defined in [4].
9.8.4.1 Measurement report mapping for MCH BLER
The UE shall report MCH BLER together with the corresponding total number of MCH blocks, which were received by
the UE during the MCH BLER measurement period and used for calculating the reported MCH BLER.
The reporting range of MCH BLER is defined from 0.1% to 50% with uniform quantization in log domain.
The mapping of measured quantity is defined in Table 9.8.4.1-1. The range in the signalling may be larger than the
range specified in the table below.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 489 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.8.4.1-1: MCH BLER measurement report mapping
Reported value Measured quantity value Unit
MCH BLER_00 MCH BLER < 0.1 %
MCH BLER_01 0.1≤ MCH BLER < 0.123 %
MCH BLER_02 0.123≤ MCH BLER < 0.151 %
MCH BLER_03 0.151≤ MCH BLER <0.186 %
MCH BLER_04 0.186≤ MCH BLER <0.229 %
MCH BLER_05 0.229≤ MCH BLER <0.282 %
MCH BLER_06 0. 282≤ MCH BLER <0.347 %
MCH BLER_07 0. 347≤ MCH BLER <0.426 %
MCH BLER_08 0. 426≤ MCH BLER <0.525 %
MCH BLER_09 0. 525≤ MCH BLER <0.645 %
MCH BLER_10 0. 645≤ MCH BLER <0.794 %
MCH BLER_11 0. 794≤ MCH BLER <0.976 %
MCH BLER_12 0. 976≤ MCH BLER <1.201 %
MCH BLER_13 1. 201≤ MCH BLER <1.478 %
MCH BLER_14 1. 478≤ MCH BLER <1.818 %
MCH BLER_15 1. 818≤ MCH BLER <2.236 %
MCH BLER_16 2. 236≤ MCH BLER <2.751 %
MCH BLER_17 2. 751≤ MCH BLER <3.384 %
MCH BLER_18 3. 384≤ MCH BLER <4.163 %
MCH BLER_19 4.163≤ MCH BLER <5.121 %
MCH BLER_20 5.121≤ MCH BLER <6.300 %
MCH BLER_21 6.300≤ MCH BLER <7.750 %
MCH BLER_22 7.750≤ MCH BLER <9.533 %
MCH BLER_23 9.533≤ MCH BLER <11.728 %
MCH BLER_24 11.728≤ MCH BLER <14.427 %
MCH BLER_25 14.427≤ MCH BLER <17.478 %
MCH BLER_26 17.478≤ MCH BLER <21.833 %
MCH BLER_27 21.833≤ MCH BLER <26.858 %
MCH BLER_28 26.858≤ MCH BLER <33.040 %
MCH BLER_29 33.040≤ MCH BLER <40.645 %
MCH BLER_30 40.645≤ MCH BLER < 50 %
MCH BLER_31 50 ≤ MCH BLER %
9.8.4.2 Measurement report mapping for MCH Block Number
The reporting range of the total number of received MCH blocks during the measurement period is defined from 0 to
65152. The total number of received MCH blocks is quantized to two values n and m with the mappings defined in
Table 9.8.4.2-1 and Table 9.8.4.2-2, respectively.
The range in the signalling may be larger than the range specified in the table below.
NR in Table 9.8.4.2-1 and Table 9.8.4.2-2 represents the total number of received MCH blocks. f(NR) is a function of NR
N R − ( 2n − 1) × 28
with the definition that f ( NR ) = , from where the quantized total number of MCH blocks is
2n
found as (2 n
− 1) × 28 + m × 2n .
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 490 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.8.4.2-1: Number of received MCH blocks mapping to n
Reported value, n Number of received MCH blocks
MCH_NR_N_00 0 ≤ NR < 256
MCH_NR_N_01 256≤ NR < 768
MCH_NR_N_02 768≤ NR < 1792
MCH_NR_N_03 1792≤ NR < 3840
MCH_NR_N_04 3840≤ NR < 7936
MCH_NR_N_05 7936≤ NR <16128
MCH_NR_N_06 16128≤ NR < 32512
MCH_NR_N_07 32512≤ NR
Table 9.8.4.2-2: Number of received MCH blocks mapping to m
Reported value, m f(NR)
MCH_NR_M_00 0 ≤ f(NR) < 1
MCH_NR_M_01 1≤ f(NR) < 2
MCH_NR_M_02 2≤ f(NR) < 3
… …
MCH_NR_M_253 253 ≤ f(NR) < 254
MCH_NR_M_254 254≤ f(NR) < 255
MCH_NR_M_255 255≤ f(NR)
9.9 ProSe Measurements
9.9.1 Introduction
The requirements in this section are applicable for a UE capable of ProSe Direct Communication and/or ProSe Direct
Discovery.
The reported measurement result after layer 1 filtering shall be an estimate of the average value of the measured
quantity over the measurement period. The reference point for the measurement result after layer 1 filtering is referred
to as point B in the measurement model described in [25].
The accuracy requirements in this clause are:
- applicable for AWGN radio propagation conditions,
- assume independent interference (noise) at each receiver antenna port.
- valid for the reported measurement result after layer 1 filtering,
- are verified from the measurement report at point D in the measurement model having the higher layer filtering
disabled.
9.9.2 Intra-Frequency S-RSRP Measurement Accuracy Requirements
9.9.2.1 Absolute S-RSRP Accuracy
The requirements for absolute accuracy of S-RSRP in this clause apply to a ProSe synchronization source on the same
frequency as that of the own ProSe UE performing the measurement.
The accuracy requirements in Table 9.9.2.1-1 are valid under the following conditions:
- Demodulation reference signals are transmitted from one port.
- Conditions defined in 36.101 Clause 7.3D for reference sensitivity are fulfilled.
- S-RSRP|dBm according to Annex B.5.1 for a corresponding Band are fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 491 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.9.2.1-1: Intra-frequency S-RSRP absolute accuracy for UE capable of ProSe Direct
Communication and/or ProSe Direct Discovery
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot
Note 4 E-UTRA ProSe operating
condition condition Minimum Io Maximum Io
band groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_A -121 N/A -70
FDD_D -119.5 N/A -70
FDD_E, TDD_E -119 N/A -70
±4.5 ±9 ≥-6 dB
FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_N -114.5 N/A -70
FDD_A, FDD_D, FDD_E,
±8 ±11 ≥-6 dB TDD_E, FDD_F, FDD_G, N/A -70 -50
FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA ProSe operating band groups are as defined in Section 3.5 for the corresponding E-UTRA operating
bands.
NOTE 4: Ês/Iot for a SyncRef UE is the minimum of the Ês/Iot of PSSS/PSBCH and the Ês/Iot of SSSS
9.9.2.2 Relative Accuracy of S-RSRP
The relative accuracy of S-RSRP is defined as the S-RSRP measured from one ProSe synchronization source compared
to the S-RSRP measured from another ProSe synchronization source on the same frequency.
The accuracy requirements in Table 9.9.2.2-1 are valid under the following conditions:
- Demodulation reference signals are transmitted from one port.
- Conditions defined in 36.101 Clause 7.3D for reference sensitivity are fulfilled.
- S-RSRP1,2|dBm according to Annex B.5.2 for a corresponding Band.
Table 9.9.2.2-1: S-RSRP Intra frequency relative accuracy for UE capable of ProSe direct
communication and/or ProSe Direct Discovery
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2, 6 E-UTRA ProSe operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_A -121 -50
FDD_D -119.5 -50
FDD_E, TDD_E -119 -50
±2 ±3 ≥-3 dB
FDD_F -118.5 -50
FDD_G -118 -50
FDD_N -114.5 -50
±3 ±3 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of SyncRef UEs to which the requirement
applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA ProSe operating band groups are as defined in Section 3.5 for the corresponding E-UTRA
operating bands.
NOTE 6: Ês/Iot for a SyncRef UE is the minimum of the Ês/Iot of PSSS/PSBCH and the Ês/Iot of SSSS
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 492 ETSI TS 136 133 V14.3.0 (2017-04)
9.9.3 Intra-Frequency SD-RSRP Measurement Accuracy Requirements
The requirements in this clause are applicable for a remote ProSe UE:
- in state RRC_IDLE or RRC_CONNECTED if the frequency used for ProSe is the serving frequency, or
- is out of coverage on the frequency used for ProSe, and
- that is synchronised to the ProSe relay UE that is measured.
9.9.3.1 Absolute SD-RSRP Accuracy
The requirements for absolute accuracy of SD-RSRP in this clause apply to a ProSe UE performing SD-RSRP
measurements on the same frequency as used by the ProSe relay UE transmitting the relay Discovery message.
The accuracy requirements in Table 9.9.3.1-1 are valid under the following conditions:
- Demodulation reference signals are transmitted from one port.
- Conditions defined in 36.101 Clause 7.3D for reference sensitivity are fulfilled.
- SD-RSRP|dBm according to Annex B.5.4 for a corresponding Band are fulfilled.
- numReTx is configured as 3 for the relay Discovery transmissions. For numReTx < 3, the minimum Ês/Noc at
which the accuracy requirements are fulfilled is expected to be higher than as specified for numReTx=3.
Table 9.9.3.1-1: Intra-frequency SD-RSRP absolute accuracy for remote UE [2] capable of ProSe
Direct Communication and ProSe Direct Discovery and configured by upper layers for relay
operation.
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Noc
Note 4 E-UTRA ProSe operating
condition condition Minimum Io Maximum Io
band groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
FDD_D -119.5 N/A -70
FDD_E -119 N/A -70
±4.5 ±9 ≥-1.5 dB FDD_F -118.5 N/A -70
FDD_G -118 N/A -70
FDD_N -114.5 N/A -70
FDD_D, FDD_E, FDD_F,
±8 ±11 ≥-1.5 dB N/A -70 -50
FDD_G, FDD_N
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA ProSe operating band groups are as defined in Section 3.5 for the corresponding E-UTRA operating
bands.
NOTE 4: When numReTx is configured as 3 for the relay Discovery transmissions. For numReTx < 3, the minimum Ês/Noc
at which the accuracy requirements are fulfilled is expected to be higher than as specified for numReTx=3.
NOTE 5: Layer 1 filtering for SD-RSRP is performed using PSDCH (re)transmissions within a discovery period.
9.9.3.2 Relative Accuracy of SD-RSRP
The relative accuracy of SD-RSRP in this clause apply to a ProSe UE performing SD-RSRP measurements on the same
frequency as used by the ProSe relay UE transmitting the relay Discovery message.
The accuracy requirements in Table 9.9.3.2-1 are valid under the following conditions:
- Demodulation reference signals are transmitted from one port.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 493 ETSI TS 136 133 V14.3.0 (2017-04)
- Conditions defined in 36.101 Clause 7.3D for reference sensitivity are fulfilled.
- SD-RSRP|dBm according to Annex B.5.5 for a corresponding Band are fulfilled.
- numReTx is configured as 3 for the relay Discovery transmissions. For numReTx < 3, the minimum Ês/Noc at
which the accuracy requirements are fulfilled is expected to be higher than as specified for numReTx=3.
Table 9.9.3.2-1: Intra-frequency SD-RSRP relative accuracy for remote UE [2] capable of ProSe Direct
Communication and ProSe Direct Discovery and configured by upper layers for relay operation.
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Noc Note
6 E-UTRA ProSe operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
FDD_D -119.5 -50
FDD_E -119 -50
±2 ±3 ≥-1.5 dB FDD_F -118.5 -50
FDD_G -118 -50
FDD_N -114.5 -50
±3 ±3 ≥-1.5 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Noc is the minimum Ês/Noc of the pair of ProSe Relay UEs to which the requirement
applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA ProSe operating band groups are as defined in Section 3.5 for the corresponding E-UTRA
operating bands.
NOTE 6: When numReTx is configured as 3 for the relay Discovery transmissions. For numReTx < 3, the
minimum Ês/Noc at which the accuracy requirements are fulfilled is expected to be higher than as
specified for numReTx=3.
NOTE 7: Layer 1 filtering for SD-RSRP is performed using PSDCH (re)transmissions within a discovery period.
9.10 V2X Measurements
9.10.1 Introduction
The requirements in this section are applicable for a UE capable of V2X sidelink communication.
The reported measurement result after layer 1 filtering shall be an estimate of the average value of the measured
quantity over the measurement period. The reference point for the measurement result after layer 1 filtering is referred
to as point B in the measurement model described in [25].
The accuracy requirements in this clause are:
- applicable for AWGN radio propagation conditions,
- assume independent interference (noise) at each receiver antenna port.
- valid for the reported measurement result after layer 1 filtering,
- are verified from the measurement report at point D in the measurement model having the higher layer filtering
disabled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 494 ETSI TS 136 133 V14.3.0 (2017-04)
9.10.2 Intra-Frequency S-RSRP Measurement Accuracy Requirements
9.10.2.1 Absolute S-RSRP Accuracy
The requirements for absolute accuracy of S-RSRP in this clause apply to a V2X synchronization source on the same
frequency as that of the own V2X UE performing the measurement.
The accuracy requirements in Table 9.10.2.1-1 are valid under the following conditions:
- Demodulation reference signals are transmitted from one port.
- Conditions defined in 36.101 Clause 7.3.1G for reference sensitivity are fulfilled.
- S-RSRP|dBm according to Annex B.6.2 for a corresponding Band are fulfilled.
Table 9.10.2.1-1: Intra-frequency S-RSRP absolute accuracy for UE capable of V2X sidelink
communication
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot
Note 4 E-UTRA V2X operating band
condition condition Minimum Io Maximum Io
groups Note 3
dB dBm/15kHz
dB dB Note 2 dBm/BWChannel dBm/BWChannel
±4.5 ±9 ≥-6 dB TDD_G -118 N/A -70
±8 ±11 ≥-6 dB TDD_G N/A -70 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA V2X operating band groups are as defined in Section 3.5 for the corresponding E-UTRA operating
bands.
NOTE 4: Ês/Iot for a SyncRef UE is the minimum of the Ês/Iot of PSSS/PSBCH and the Ês/Iot of SSSS
9.10.2.2 Relative Accuracy of S-RSRP
The relative accuracy of S-RSRP is defined as the S-RSRP measured from one V2X synchronization source compared
to the S-RSRP measured from another V2X synchronization source on the same frequency.
The accuracy requirements in Table 9.10.2.2-1 are valid under the following conditions:
- Demodulation reference signals are transmitted from one port.
- Conditions defined in 36.101 Clause 7.3.1G for reference sensitivity are fulfilled.
- S-RSRP1,2|dBm according to Annex B.6.3 for a corresponding Band.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 495 ETSI TS 136 133 V14.3.0 (2017-04)
Table 9.10.2.2-1: S-RSRP Intra frequency relative accuracy for UE capable of V2X sidelink
communication
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot Note
2, 6 E-UTRA V2X operating band
condition condition Minimum Io Maximum Io
groups Note 5
dB dB dB dBm/15kHz Note 4 dBm/BWChannel
±2 ±3 ≥-3 dB TDD_G -118 -50
±3 ±3 ≥-6 dB Note 3 Note 3 Note 3
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The parameter Ês/Iot is the minimum Ês/Iot of the pair of SyncRef UEs to which the requirement
applies.
NOTE 3: The same bands and the same Io conditions for each band apply for this requirement as for the
corresponding highest accuracy requirement.
NOTE 4: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 5: E-UTRA V2X operating band groups are as defined in Section 3.5 for the corresponding E-UTRA
operating bands.
NOTE 6: Ês/Iot for a SyncRef UE is the minimum of the Ês/Iot of PSSS/PSBCH and the Ês/Iot of SSSS
9.10.3 PSSCH-RSRP Measurement Accuracy Requirements
9.10.3.1 Intra-frequency Absolute PSSCH-RSRP Accuracy
The requirements for absolute accuracy of PSSCH-RSRP in this clause apply to a UE performing PSSCH-RSRP
measurements on the same frequency as used by operating V2X sidelink communication.
The accuracy requirements in this clause are:
- applicable for AWGN radio propagation conditions,
- assume independent interference (noise) at each receiver antenna port.
The accuracy requirements in Table 9.10.3.1-1 are valid under the following conditions:
- Demodulation reference signals are transmitted from one port.
- Conditions defined in 36.101 Clause 7.3.1G for reference sensitivity are fulfilled.
- PSSCH-RSRP|dBm according to Annex B.6.5 for a corresponding Band are fulfilled.
Table 9.10.3.1-1: Intra-frequency PSSCH-RSRP absolute accuracy for UE capable of V2X sidelink
communication
Accuracy Conditions
Io Note 1 range
Normal Extreme Ês/Iot
Note 4 E-UTRA V2X operating band
condition condition Minimum Io Maximum Io
groups Note 3
dBm/15kHz
dB dB dB Note 2 dBm/BWChannel dBm/BWChannel
±[5] ±[9.5] ≥[0]dB TDD_G -118 N/A -70
±[8.5] ±[11.5] ≥[0] dB TDD_G N/A -70 -50
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and B.4.3.
NOTE 3: E-UTRA V2X operating band groups are as defined in Section 3.5 for the corresponding E-UTRA operating
bands.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 496 ETSI TS 136 133 V14.3.0 (2017-04)
9.10.4 S-RSSI Measurement Accuracy Requirements
9.10.4.1 Intra-frequency absolute S-RSSI measurement accuracy requirements
The intra-frequency S-RSSI requirements are specified in Table 9.10.4.1-1. The requirements apply for measurement
period of 1subframe (1ms) and for any configured measurement bandwidth larger than 5RBs (0.9MHz), provided that:
- All symbols duing each RSSI measurement duration are available for RSSI sampling within the same
measurement interval.
Table 9.10.4.1-1: Intra-frequency S-RSSI absolute accuracy
Accuracy Conditions
Normal Extreme
E-UTRA V2X operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dBm/15kHz Note 3 dBm/BWChannel
±2.5 ±5.5 TDD_G -118 -50
±4.5 ±7.5 Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for
the corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and
B.4.3.
NOTE 4: E-UTRA V2X operating band groups are as defined in Section 3.5.
9.10.4.2 Intra-frequency relative S-RSSI measurement accuracy requirements
The relative accuracy of S-RSSI is defined as the RSRP measured on one configured measurement bandwidth
compared to the S-RSSI measured on another configured measurement bandwidth.The intra-frequency S-RSSI relative
requirements are specified in Table 9.10.4.2-1. The requirements apply for measurement period of 1000subframe (1s),
for any configured measurement bandwidth larger than 5RBs (0.9MHz), and for sampling interval of 20ms,50ms and
100ms, provided that:
- All symbols duing each RSSI measurement duration are available for RSSI sampling within the same
measurement interval.
Table 9.10.4.2-1: Intra-frequency S-RSSI relative accuracy
Accuracy Conditions
Normal Extreme
E-UTRA V2X operating band
condition condition Minimum Io Maximum Io
groups Note 4
dB dB dBm/15kHz Note 3 dBm/BWChannel
±2.5 ±5.5 TDD_G -118 -50
±4.5 ±7.5 Note 2 Note 2 Note 2
NOTE 1: Io is assumed to have constant EPRE across the bandwidth.
NOTE 2: The same bands and the same Io conditions for each band apply for this requirement as for
the corresponding highest accuracy requirement.
NOTE 3: The condition level is increased by ∆>0, when applicable, as described in Sections B.4.2 and
B.4.3.
NOTE 4: E-UTRA V2X operating band groups are as defined in Section 3.5.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 497 ETSI TS 136 133 V14.3.0 (2017-04)
10 Measurements Performance Requirements for E-
UTRAN
10.1 Received Interference Power
The measurement period shall be 100 ms.
10.1.1 Absolute accuracy requirement
Table 10.1.1-1: Received Interference Power absolute accuracy
Parameter Unit Accuracy Conditions
[dB] Iob [dBm/180 kHz]
Iob dBm/180 kHz ±4 -117 ... -96
10.1.2 Relative accuracy requirement
The relative accuracy is defined as the Received Interference Power measured at one frequency compared to the
Received Interference Power measured from the same frequency at a different time.
Table 10.1.2-1: Received Interference Power relative accuracy
Parameter Unit Accuracy Conditions
[dB] Iob [dBm/180 kHz]
Iob dBm/180 kHz ± 0.5 -117 ... -96
AND for changes ≤ ±9.0 dB
10.1.3 Received Interference Power measurement report mapping
The reporting range for Received Interference Power (RIP) is from -126 ... -75 dBm.
In table 10.2.3-1 the mapping of measured quantity is defined. The range in the signalling may be larger than the
guaranteed accuracy range.
Table 10.1.3-1: Received Interference Power measurement reporting range
Reported value Measured quantity value Unit
RTWP_LEV _000 RIP < -126.0 dBm
RTWP_LEV _001 -126.0 ≤ RIP < -125.9 dBm
RTWP_LEV _002 -125.9 ≤ RIP < -125.8 dBm
… … …
RTWP_LEV _509 -75.2 ≤ RIP < -75.1 dBm
RTWP_LEV _510 -75.1 ≤ RIP < -75.0 dBm
RTWP_LEV _511 -75.0 ≤ RIP dBm
10.2 Angle of Arrival (AOA)
10.2.1 Range/mapping
The reporting range for AOA measurement is from 0 to 360 degree, with resolution of 0.5 degree.
The mapping of the measured quantity is defined in table 10.2.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 498 ETSI TS 136 133 V14.3.0 (2017-04)
Table 10.2.1-1: AOA measurement report mapping
Reported value Measured quantity value Unit
AOA_ANGLE _000 0 ≤ AOA_ANGLE < 0.5 degree
AOA_ANGLE _001 0.5 ≤ AOA_ANGLE < 1 degree
AOA_ANGLE _002 1 ≤ AOA_ANGLE < 1.5 degree
… … …
AOA_ANGLE _717 358.5 ≤ AOA_ANGLE < 359 degree
AOA_ANGLE _718 359 ≤ AOA_ANGLE < 359.5 degree
AOA_ANGLE _719 359.5 ≤ AOA_ANGLE < 360 degree
10.3 Timing Advance (TADV)
10.3.1 Report mapping
The reporting range of TADV is defined from 0 to 49232Ts with 2Ts resolution for timing advance less or equal to 4096Ts
and 8Ts for timing advance greater than 4096Ts.
The mapping of measured quantity is defined in Table 10.3.1-1.
Table 10.3.1-1: TADV measurement report mapping
Reported value Measured quantity value Unit
TIME_ADVANCE_00 TADV < 2 Ts
TIME_ADVANCE_01 2 ≤ TADV < 4 Ts
TIME_ADVANCE_02 4 ≤ TADV < 6 Ts
… … …
TIME_ADVANCE_2046 4092 ≤ TADV < 4094 Ts
TIME_ADVANCE_2047 4094 ≤ TADV < 4096 Ts
TIME_ADVANCE_2048 4096 ≤ TADV < 4104 Ts
TIME_ADVANCE_2049 4104 ≤ TADV < 4112 Ts
… … …
TIME_ADVANCE_7688 49216 ≤ TADV < 49224 Ts
TIME_ADVANCE_7689 49224 ≤ TADV < 49232 Ts
TIME_ADVANCE_7690 49232 ≤ TADV Ts
NOTE: For report mapping of type2 TADV for TDD, the TADV equal to (eNB Rx – Tx time difference) + 624Ts.
11 ProSe Requirements in Any Cell Selection state
11.1 Introduction
This section contains the requirements for the UE capable of ProSe Direct Communication and/or ProSe Direct
Discovery when the UE is out of coverage on the carrier used for ProSe operation, as defined in [1]. The ProSe
requirements shall apply provided that the sidelink used by the UE for ProSe Direct Communication and/or ProSe
Direct Discovery is on the carrier that is preconfigured in the ProSe UE for out-of-coverage operation. The requirement
apply when the UE is:
- in any cell selection state, or,
- out of coverage on the ProSe carrier and is associated with a serving cell on a non-ProSe carrier.
Note: Any cell selection state refers to a UE that is out of network coverage and is not associated with a serving
cell on any carrier [1].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 499 ETSI TS 136 133 V14.3.0 (2017-04)
11.2 UE Transmit Timing for ProSe in Any Cell Selection State
11.2.1 Introduction
This clause contains requirements on the UE capable of ProSe Direct Communication and/or ProSe Direct Discovery
regarding transmit timing if the UE is out of coverage on the carrier used for ProSe operation.
11.2.2 ProSe UE transmission timing
The requirements in this subclause are applicable when the reference timing used for deriving ProSe transmission is
from another ProSe UE transmitting sidelink synchronization signals.
The sidelink transmissions takes place ( N TA, SL + N TA offset ) ⋅ Ts before the reception of the first detected path (in time)
of the corresponding timing reference frame from the UE, with N TA offset = 0 and N TA,SL = 0 [16]. The transmission
timing error for sidelink transmissions shall be less than or equal to ±Te where the timing error limit value Te is
specified in Table 11.2.2-1.
Table 11.2.2-1: Te Timing Error Limit
Sidelink Bandwidth (MHz) Te
≥1.4 24*TS
Note: TS is the basic timing unit defined in TS 36.211
11.3 Initiation/Cease of SLSS Transmissions
11.3.1 Introduction
The requirements in this subclause apply when the conditions for SLSS transmissions specified in [2] are met and if
syncTxThreshOoC is included in the preconfigured ProSe parameters.
11.3.2 Requirements
The UE shall be capable of measuring the S-RSRP of the selected SyncRef UE used to derive transmission timing for
Prose Direct Communication and/or ProSe Direct Discovery and evaluate it to initiate/cease SLSS transmissions within
Tevaluate,SLSS = 0.8 seconds.
If higher layer filtering for S-RSRP measurements is pre-configured, an additional delay in evaluation to initiate/cease
SLSS transmissions can be expected.
For the selected SyncRef UE [2] used to derive transmission timing for ProSe Direct Communication and/or ProSe
Direct Discovery:
- S-RSRP related side conditions given in Section 11.5 for a corresponding Band are fulfilled,
- ProSe SCH_RP and SCH Ês/Iot according to Annex B.5.1 for a corresponding Band are fulfilled.
11.4 Measurements for ProSe in Any Cell Selection State
11.4.1 Introduction
This clause contains requirements for E-UTRA cell identification for the UE capable of ProSe Direct Communication
and/or ProSe Direct Discovery if the UE is out of coverage on the carrier used for ProSe operation.
The UE can be preconfigured with ProSe resources for out of coverage ProSe operation.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 500 ETSI TS 136 133 V14.3.0 (2017-04)
The requirements in this section are applicable for the ProSe if the UE is out of coverage on the carrier used for ProSe
operation using the preconfigured ProSe resources. The ProSe UE shall:
- continuously search for any detectable E-UTRA cell on the donwlink carrier frequency associated with the
preconfigured ProSe carrier frequency for out of coverage ProSe operation, and
- if in any cell selection state, then search cells also on other carriers and perform cell selection according to the
procedure specified in section 4.1.
11.4.2 Requirements
11.4.2.1 E-UTRA FDD
The requirements in this subclause are applicable when the preconfigured ProSe carrier is FDD (parameter tdd-
ConfigSL is configured as none).
The UE capable of ProSe Direct Communication and/or ProSe Direct Discovery immediately upon being out of
coverage on the ProSe carrier shall search for any detectable cell on the carrier preconfigured with ProSe resources.
The UE shall be able to identify a newly detectable E-UTRA FDD cell on the downlink carrier frequency associated
with the preconfigured with ProSe carrier frequency:
- within Tbasic_identify_OoC_ProSe Tx_ON if the UE is performing ProSe transmissions on the sidelink, or
- within Tbasic_identify_OoC_ProSe Tx_OFF if the UE is not performing ProSe transmissions on the sidelink.
where,
Tbasic_identify_OoC_ProSe Tx_ON = 6.4 seconds, and
Tbasic_identify_OoC_ProSe Tx_OFF = 32 seconds.
An E-UTRA cell is considered detectable provided it meets the intra-frequency cell identification conditions specified
in section 8.1.2.2.
11.4.2.2 E-UTRA TDD
The requirements in this subclause are applicable when the preconfigured ProSe carrier is configured as TDD.
The UE capable of ProSe Direct Discovery immediately upon being out of coverage on the ProSe carrier shall search
for any detectable cell on the carrier preconfigured with ProSe resources.
The UE shall be able to identify a newly detectable E-UTRA TDD cell on TDD carrier frequency preconfigured for
ProSe operation:
- within Tbasic_identify_OoC_ProSe Tx_ON if the UE is performing ProSe transmissions on the sidelink, or
- within Tbasic_identify_OoC_ProSe Tx_OFF if the UE is not performing ProSe transmissions on the sidelink.
where,
Tbasic_identify_OoC_ProSe Tx_ON = 6.4 seconds, and
Tbasic_identify_OoC_ProSe Tx_OFF = 32 seconds.
An E-UTRA cell is considered detectable provided it meets the intra-frequency cell identification conditions specified
in section 8.1.2.2.
The UE shall be allowed to interrupt ProSe Direct Discovery operation in order to meet the requirements in this
subclause.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 501 ETSI TS 136 133 V14.3.0 (2017-04)
11.5 Selection / Reselection of ProSe Synchronization
Reference
11.5.1 Introduction
This clause contains requirements for the measurements performed by the UE capable of ProSe Direct Communication
and/or ProSe Direct Discovery if the UE is out of coverage on the carrier used for ProSe operation.
11.5.2 Selection/Reselection to intra-frequency SyncRef UE
11.5.2.1 Introduction
This clause contains requirements for the measurement for the ProSe synchronization on the UE capable of ProSe
Direct Communication and/or ProSe Direct Discovery if the UE is out of coverage on the carrier used for ProSe
operation.
11.5.2.2 Requirements
The UE shall be able to identify newly detectable SyncRef UE within Tdetect,SyncRef UE seconds if SyncRef UE meets the
selection / reselection criterion defined in TS 36.331 [2].
ProSe synchronization source, SyncRef UE, is defined as a ProSe synchronization source which is capable to transmit
ProSe synchronization signals.
A SyncRef UE is considered to be detectable when
- S-RSRP related side conditions given in Section 9.9.2 are fulfilled for a corresponding Band,
- ProSe SCH_RP and SCH Ês/Iot are fulfilled according to Annex B.5.3 for a corresponding Band.
Tdetect,SyncRef UE is defined as 20 seconds at SCH Es/Iot ≥ -4 dB, provided that the ProSe UE is allowed to drop a
maximum of 2% of its ProSe Direct Communication and ProSe Direct Discovery transmissions at the physical layer for
the purpose of SyncRef UE selection / reselection.
The UE capable of ProSe Direct Communication and/or ProSe Direct Discovery shall be capable of performing S-
RSRP measurements for 6 identified ProSe synchronization sources with the measurement period of 400 ms. It is
assumed that the ProSe synchronization sources do not drop or delay more than one SLSS transmission within the
measurement period. Otherwise, the measurement period may be extended.
11.6 Void
11.7 Selection / Reselection of ProSe relay UE
11.7.1 Introduction
This section contains the requirements related to selection and reselection of ProSe relay UE when the remote UE is out
of coverage on the frequency used for ProSe Direct Communication.
The requirements apply for the selection and reselection of candidate relay UEs that are transmitting relay discovery
signals within the discovery resource pool as configured for the remote UE, and follow a synchronization source that
either the same or is synchronized to the one use by remote UE.
11.7.2 Selection / Reselection of intra-frequency ProSe relay UE
For a remote UE configured by upper layer for relay operation, the remote UE shall search for candidate relay UEs for
selection and/or reselection every discovery period.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 502 ETSI TS 136 133 V14.3.0 (2017-04)
If the remote UE has a selected sidelink relay UE, then the remote UE shall measure the SD-RSRP of the selected relay
once in every four discovery periods and evaluate if it meets the relay selection criterion as defined in [TS 36.331,
5.10.11.4].
The remote UE shall measure SD-RSRP of the candidate relay UEs every Tmeasure, ProSe_Relay_Intra for intra-frequency relay
UEs that are detected and measured according to the measurement rules.
For an intra-frequency relay UEs that are detected, but that has not been selected or reselected to, the remote UE shall
be capable of evaluating that the intra-frequency relay UE has met selection or reselection criterion defined in [2,
5.10.11.4] within Tevaluate,ProSe_Relay_Intra as specified in table 11.7.2-1.
The minimum requirements are required to meet when the selected and candidate relay UEs are transmitting relay
discovery message every discovery period.
Table 11.7.2-1: Tmeasure, ProSe_Relay_Intra and Tevaluate, ProSe_Relay_intra
Tmeasure,ProSe_Relay_Intra Tevaluate, ProSe_Relay_intra
Discovery
[s] (number of [s] (number of
Period [s]
discovery periods) discovery periods)
0.04≤Discovery
Note 1 (4) Note 1 (16)
period≤10.24
NOTE 1: Time depends upon the configured Discovery period.
12 V2V Sidelink Communication Requirements for V2V
Operation on Dedicated V2V Carrier
12.1 Introduction
This section contains the requirements for the UE capable of V2V sidelink communication under the following
conditions:
- no cell operates on the carrier used for the V2V sidelink communcation and
- no configuration related to V2V communication is received by the UE from the serving cell.
12.2 Transmit Timing
This clause contains requirements regarding transmit timing for the UE capable of V2V sidelink communication under
the following additional condition:
- the UE is pre-configured with parameters for enabling the UE to acquire timing synchronization.
12.2.1 GNSS as timing reference
The requirements in this subclause are applicable when the reference timing used by the UE for V2V communication is
derived from GNSS signals.
The sidelink transmissions takes place ( N TA, SL + N TA offset ) ⋅ Ts before the subframe starting boundary derived from
the absolute UTC time as defined in [2], where N TA offset = 0 and N TA,SL = 0 . The transmission timing error for
sidelink transmissions shall be less than or equal to ±Te where the timing error limit value Te is specified as 12*Ts and
Ts is the basic timing unit defined in TS 36.211.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 503 ETSI TS 136 133 V14.3.0 (2017-04)
12.3 Interruption
This clause contains interruption requirements for the UE capable of V2V sidelink communication under the following
additional conditions:
- the UE is pre-configured with parameters for enabling the UE to acquire timing synchronization
- the UE has dedicated transmitter chain and dedicated receiver chain for the V2V operation.
The UE shall not cause any interruption on the serving cell when receiving or transmitting V2V sidelink communication
signals.
12.4 Reliability of GNSS signal
This clause contains requirements regarding reliability of GNSS signal for the UE capable of V2V sidelink
communication under the following additional condition:
- the UE is pre-configured with parameters for enabling the UE to acquire the GNSS synchronization.
GNSS is considered as a reliable synchronization reference if the UE meets timing accuracy requirement as specified in
12.2 and frequency accuracy requirement as specified in 6.5.1G of TS36.101.
GNSS shall be reliable at least when
- GNSS related side conditions given in Sections B.6.1 are fulfilled.
13 V2X Requirements
13.1 Introduction
This section contains the requirements for the UE capable of V2X sidelink communication when the UE is out of
coverage on the carrier used for V2X sidelink operation, as defined in [1]. The V2X requirements shall apply provided
that the sidelink used by the UE for V2X sidelink communication is on the carrier that is preconfigured in the UE for
out-of-coverage operation. The requirements apply when the UE is:
- in any cell selection state, or,
- out of coverage on the V2X sidelink carrier and is associated with a serving cell on a non-V2X sidelink carrier.
Note: Any cell selection state refers to a UE that is out of network coverage and is not associated with a serving cell
on any carrier [1].
13.2 UE Transmit Timing
13.2.1 Introduction
This clause contains requirements of transmission timing for V2X sidelink communication when the timing reference
is:
- GNSS as timing reference
- eNB as timing reference
- SyncRef UE as timing reference
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 504 ETSI TS 136 133 V14.3.0 (2017-04)
13.2.2 GNSS as timing reference
The requirements in this subclause are applicable when the reference timing used by the UE for V2X sidelink
communication is derived from GNSS signals.
The sidelink transmissions takes place ( N TA, SL + N TA offset ) ⋅ Ts before the subframe starting boundary derived from
the absolute UTC time, where N TA offset = 0 and N TA,SL = 0 .
The transmission timing error requirements for sidelink transmissions in Section 12.2 as specified for V2V Sidelink
Communication shall apply.
13.2.3 eNB as timing reference
The requirements in this subclause are applicable when the reference timing used for Sidelink transmissions is the
serving cell (RRC_IDLE) or PCell (RRC_CONNECTED) on a non-V2X sidelink carrier.
The sidelink transmissions takes place ( N TA, SL + N TA offset ) ⋅ Ts before the reception of the first detected path (in time)
of the corresponding downlink frame from the reference cell, where N TA offset = 0 and N TA,SL = 0 .
The requirements in Section 7.1 as specified for PRACH transmissions shall apply.
13.2.4 SyncRef UE as timing reference
The requirements in this subclause are applicable when the reference timing used for deriving sidelink transmission is
from SyncRef UE transmitting sidelink synchronization signals.
The sidelink transmissions takes place ( N TA, SL + N TA offset ) ⋅ Ts before the reception of the first detected path (in time)
of the corresponding timing reference frame from the SyncRef UE, where N TA offset = 0 and N TA,SL = 0 .
The requirements in Section 11.2 as specified for ProSe in Any Cell Selection State shall apply.
13.3 Initiation/Cease of SLSS Transmissions
13.3.1 Introduction
The requirements in this subclause are applicable to the UE capable of V2X sidelink communication when the timing
reference is:
- GNSS as timing reference
- eNB as timing reference
- SyncRef UE as timing reference
13.3.1.1 Initiation/Cease of SLSS transmissions with eNB as timing reference
The requirements apply when the timing reference is eNB and when the UE is
- out of coverage on the V2X sidelink carrier and in-coverage with a serving cell on a non-V2X sidelink carrier,
and when the conditions for SLSS transmissions specified in [2] are met; networkControlledSyncTx is not configured;
and syncTxThreshIC is included in SystemInformationBlockType21. The UE shall be capable of measuring the RSRP of
the cell used to transmit V2X sidelink communication to evaluate to initiate/cease SLSS transmissions within
Tevaluate,SLSS
where,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 505 ETSI TS 136 133 V14.3.0 (2017-04)
- Tevaluate,SLSS = 0.4 seconds when UE is not configured with DRX.
- Tevaluate,SLSS = as specified in Table 13.3.1.1-1 when UE is configured with DRX.
Table 13.3.1.1-1: Tevaluate,SLSS with V2X sidelink communication
DRX cycle length [s] Tevaluate,SLSS
[s] (number of DRX cycles)
≤0.04 0.4 (Note 1)
0.04<DRX-cycle≤2.56 Note 2 (6)
Note1: Number of DRX cycles depends upon the
DRX cycle in use
Note2: Time depends upon the DRX cycles in use
If higher layer filtering is configured, an additional delay in evaluation to initiate/cease SLSS transmissions can be
expected.
For the cell used to transmit V2X sidelink communication:
- RSRP related side conditions given in Sections 9.1.2.1 and 9.1.2.2 and RSRQ related side conditions given in
Clause 9.1.5.1 for a corresponding Band are fulfilled,
- SCH_RP and SCH Ês/Iot according to Annex B.2.1 for a corresponding Band are fulfilled.
13.3.1.2 Initiation/Cease of SLSS transmissions with GNSS as timing reference
The requirements apply when the timing reference is GNSS and when the UE is
- out of coverage on the V2X sidelink carrier and in-coverage with a serving cell on a non-V2X sidelink carrier,
and when the conditions for SLSS transmissions specified in [2] are met; networkControlledSyncTx is not configured;
and syncTxThreshIC is included in SystemInformationBlockType21.
The requirements in Section 13.3.1.1 shall apply.
13.3.1.3 Initiation/Cease of SLSS transmissions with SyncRef UE as timing reference
The requirements apply when the timing reference is SyncRef UE and when the UE is
- in any cell selection state, or
- out of coverage on the V2X sidelink carrier and is associated with a serving cell on a non-V2X sidelink carrier,
and when the conditions for SLSS transmissions specified in [2] are met and when SyncRef UE is timing reference and
if syncTxThreshOoC is included in the preconfigured V2X parameters.
The UE shall be capable of measuring the S-RSRP of the selected SyncRef UE used to derive transmission timing for
V2X sidelink communication and evaluate it to initiate/cease SLSS transmissions within Tevaluate,SLSS = 0.64 seconds.
If higher layer filtering for S-RSRP measurements is pre-configured, an additional delay in evaluation to initiate/cease
SLSS transmissions can be expected.
For the selected SyncRef UE [2] used to derive transmission timing for V2X sidelink communication:
- S-RSRP related side conditions given in Section 13.4 for a corresponding Band are fulfilled,
- V2X SCH_RP and SCH Ês/Iot according to Annex B.6.4 for a corresponding Band are fulfilled.
13.4 Selection / Reselection of V2X Synchronization Reference
The requirements defined in section 13.4 don’t apply to the P-UE and V-UE that does not support
transmission/reception of SLSS.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 506 ETSI TS 136 133 V14.3.0 (2017-04)
When GNSS is configured as the highest priority and
- UE is synchronized to GNSS directly,
- UE shall not drop any V2X SLSS and data transimission for the purpose of selection/reselection to the
SyncRef UE.
- UE is synchronized to a SyncRef UE that is synchronized to GNSS directly or in-directly,
- UE shall not drop any V2X data transimission for the purpose of selection/reselection to the SyncRef UE.
The UE shall be able to identify newly detectable intra-frequency V2X SyncRef UE within Tdetect,SyncRef
UE_V2X seconds if the V2X SyncRef UE meets the selection / reselection criterion defined in TS 36.331
[2]. Tdetect,SyncRef UE_V2X is defined as [1.6] seconds at SCH Es/Iot ≥[0] dB, provided that the UE is
allowed to drop a maximum of [30]% of its SLSS transmissions during Tdetect,SyncRef UE_V2X for the
purpose of selection / reselection to the SyncRef UE.
- in other case
- The UE shall be able to identify newly detectable intra-frequency V2X SyncRef UE within Tdetect,SyncRef
UE_V2X seconds if the SyncRef UE meets the selection / reselection criterion defined in TS 36.331 [2].
Tdetect,SyncRef UE_V2X is defined as [8] seconds at SCH Es/Iot ≥[0] dB, provided that the UE is allowed
to drop a maximum of [6]% of its V2X data and SLSS transmissions during Tdetect,SyncRef UE_V2X for
the purpose of selection / reselection to the SyncRef UE.
When eNB is configured as the highest priority,
- UE shall be able to identify newly detectable intra-frequency V2X SyncRef UE within Tdetect,SyncRef
UE_V2X seconds if the SyncRef UE meets the selection / reselection criterion defined in TS 36.331 [2].
Tdetect,SyncRef UE_V2X is defined as [8] seconds at SCH Es/Iot ≥ [0] dB, provided that the V2X UE is
allowed to drop a maximum of [6]% of its V2X data and SLSS transmissions for the purpose of selection /
reselection to the SyncRef UE.
V-UE shall be capable of performing S-RSRP measurements for [3] identified intra-frequency SLSS.
When UE is synchronized to GNSS directly, UE shall evaluate the GNSS for at least [TBD] seconds for the purpose of
deciding whether to perform selection / reselection of the new synchronization source.
Note : Above the value of evalution period will be finalize in performance part.
13.5 Autonomous Resource Selection/Reselection
measurements
13.5.1 Introduction
This section contains the requirements related to autonomous resource selection/reseletion of the UE capable of V2X
sidelink communication.
13.5.2 PSSCH-RSRP measurements
The UE physical layer shall be capable of performing the PSSCH-RSRP measurements [4] on the carrier operating V2X
sidelink communication for determining the subset of resources to be excluded in PSSCH resource selection in sidelink
transmission mode 4. The PSSCH-RSRP measurement period corresponds to one sub-frame and the measurement shall
meet the PSSCH-RSRP measurement accuracy requirement in Section 9.10.
13.5.3 S-RSSI measurements
The UE physical layer shall be capable of performing the S-RSSI measurements [4] on the carrier operating V2X
sidelink communication for determining the subset of resources to be excluded in PSSCH resource selection in sidelink
transmission mode 4. The S-RSSI measurement period corresponds to 1 second and the filtered measurement shall meet
the S-RSSI measurement accuracy requirement in Section 9.10.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 507 ETSI TS 136 133 V14.3.0 (2017-04)
13.6 Congestion Control measurements
The UE shall be capable of estimating the channel busy ratio for one or more transmission pools indicated by higher
layers [2], based on S-RSSI measurements provided by the physical layer.
When no transmissions occur, the UE physical layer shall perform a single-shot S-RSSI measurement for each sub-
channel included in all the subframes configured as transmission pools.
The S-RSSI measurement performed according to this section shall meet the S-RSSI measurement accuracy
requirements defined in Section 9.10.4.
The UE shall perform channel busy ratio measurement based on S-RSSI measurements observed within 100ms.
The channel busy ratio measurement performed and reported according to this section shall meet the channel busy ratio
measurement accuracy requirements defined in Section 9.10.5.
13.7 Interruption
13.7.1 Interruptions to WAN due to V2X Sidelink Communication
This sub-clause contains the requirements related to the interruptions on the serving cell(s) due to V2X sidelink
communication.
A UE capable of V2X sidelink communication may indicate its interest (initiation or termination) in V2X sidelink
communication to the connected eNodeB using IE SidelinkUEInformation [2].
The UE is allowed an interruption of up to 1 subframe on the serving cell(s) during the RRC reconfiguration procedure
that includes the V2X sidelink communication configuration message sl-V2X-ConfigDedicated [2] (setup and release).
This interruption is for both uplink and downlink of the serving cell(s).
13.7.2 V2X Sidelink Communication Dropping due to synchronization
source change
This sub-clause contains the requirements related to the interruptions on the V2X sidelink communication due to
synchronization source change.
When synchronization source is changed from GNSS or SyncRef UE that is synchronized to GNSS directly or in-
directly to SyncRef UE that is not synchronized to GNSS directly or in-directly or eNB, UE is allowed to drop V2V SL
TX/RX for up to [1] subframe.
When synchronization source is changed from SyncRef UE that is not synchronized to GNSS directly or in-directly or
eNB, toGNSS or SyncRef UE that is synchronized to GNSS directly or in-directly, UE is allowed to drop V2V SL
TX/RX for up to [1] subframe.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 508 ETSI TS 136 133 V14.3.0 (2017-04)
Annex A (normative):
Test Cases
A.1 Purpose of annex
This Annex specifies test specific parameters for some of the functional requirements in sections 4 to 9. The tests
provide additional information to how the requirements should be interpreted for the purpose of conformance testing.
The tests in this Annex are described such that one functional requirement may be tested in one or several test and one
test may verify several requirements. Some requirements may lack a test.
The conformance tests are specified in TS 36.521-3 [23]. Statistical interpretation of the requirements is described in
Annex A.2.
A.2 Requirement classification for statistical testing
Requirements in this specification are either expressed as absolute requirements with a single value stating the
requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the
parameter is tested.
Annex A outlines the tests in more detail and lists the test parameters needed. The test will result in an outcome of a test
variable value for the device under test (DUT) inside or outside the test limit. Overall, the probability of a "good" DUT
being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as
possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is
accounted for.
The statistical nature depends on the type of requirement. Some have large statistical variations, while others are not
statistical in nature at all. When testing a parameter with a statistical nature, a confidence level is set. This establishes
the probability that a DUT passing the test actually meets the requirements and determines how many times a test has to
be repeated and what the pass and fail criteria are. Those aspects are not covered by TS 36.133. The details of the tests
on how many times to run it and how to establish confidence in the tests are described in TS 36.521-3 [23]. This Annex
establishes the variable to be used in the test and whether it can be viewed as statistical in nature or not.
A.2.1 Types of requirements in TS 36.133
A.2.1.1 Time and delay requirements on UE higher layer actions
A very large part of the RRM requirements are delay requirements:
- In E-UTRAN RRC_IDLE state mobility (clause A.4) there is cell re-selection delay.
- In E-UTRAN RRC_CONNECTED state mobility (clauses A.5 and A.8) there is handover delay, cell search
delay and measurement reporting delay.
- In RRC Connection Control (clause A.6) there is RRC re-establishment delay.
All have in common that the UE is required to perform an action observable in higher layers (e.g. camp on the correct
cell) within a certain time after a specific event (e.g. when a new strong pilot or reference signal appears). The delay
time is statistical in nature for several reasons, among others that several of the measurements are performed by the UE
in a fading radio environment.
The variations make a strict limit unsuitable for a test. Instead there is a condition set for a correct action by the UE, e.g.
that the UE shall camp on the correct cell within X seconds. Then the rate of correct events is observed during repeated
tests and a limit is set on the rate of correct events, usually 90% correct events are required. How the limit is applied in
the test depends on the confidence required, further detailed are in TS 36.521-3 [23].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 509 ETSI TS 136 133 V14.3.0 (2017-04)
A.2.1.2 Measurements of power levels, relative powers and time
A very large number of requirements are on measurements that the UE performs:
- In E-UTRAN RRC_CONNECTED state mobility (clause A.5) there are measurement reports.
- In Measurement Performance Requirements (clause A.9) there are requirements for all type of measurements.
The accuracy requirements on measurements are expressed in this specification as a fixed limit (e.g. +/-X dB), but the
measurement error will have a distribution that is not easily confined in fixed limits. Assuming a Gaussian distribution
of the error, the limits will have to be set at +/-3.29σ if the probability of failing a "good DUT" in a single test is to be
kept at 0.1%. It is more reasonable to set the limit tighter and test the DUT by counting the rate of measurements that
are within the limits, in a way similar to the requirements on delay.
A.2.1.3 Implementation requirements
A few requirements are strict actions the UE should take or capabilities the UE should have, without any allowance for
deviations. These requirements are absolute and should be tested as such. Examples are:
- "Event triggered report rate" in E-UTRAN RRC_CONNECTED state mobility (clauses A.5 and A.8)
- "Correct behaviour at time-out" in RRC connection control (clause A.6)
A.2.1.4 Physical layer timing requirements
There are requirements on Timing and Signaling Characteristics (clauses A.7). There are both absolute and relative
limits on timing accuracy depending upon the type of requirement. Examples are:
- Initial Transmit Timing (clause A.7.1) has an absolute limit on timing accuracy.
- Timing Advance (clause A.7.2) has a relative limit on timing accuracy.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 510 ETSI TS 136 133 V14.3.0 (2017-04)
A.3 RRM test configurations
A.3.1 Reference Measurement Channels
A.3.1.1 PDSCH
A.3.1.1.1 FDD
Table A.3.1.1.1-1: PDSCH Reference Measurement Channels for FDD
Parameter Unit Value
Reference channel R.2 R.5 R.7 R.0 R.1 R.3 R.4 R.6
FDD FDD FDD FDD FDD FDD FDD FDD
Channel bandwidth MHz 1.4 3 5 5 10 10 10 20 20
Number of transmitter antennas 1 1 1 1 2 1 1 1
Allocated resource blocks (Note 4) 2 11 11 24 24 24 24 24
Allocated subframes per Radio Frame 10 10 10 10 10 10 10 10
Modulation QPS QPS QPS QPS QPS QPS QPS QPS
K K K K K K K K
Target Coding Rate 1/3 1/3 1/3 1/3 1/3 1/3 1/3 1/3
Information Bit Payload
For Sub-Frames 4, 9 Bits 120 968 968 2088 2088 2088 2088 2088
For Sub-Frame 5 Bits 104 776 776 2088 1736 2088 2088 2088
For Sub-Frame 0 Bits 32 616 616 1736 1736 1736 1736 1736
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 0 0 968 0 0 2088 0 2088
Number of Code Blocks per Sub-Frame
(Note 5)
For Sub-Frames 4, 9 1 1 1 1 1 1 1 1
For Sub-Frame 5 1 1 1 1 1 1 1 1
For Sub-Frame 0 1 1 1 1 1 1 1 1
For Sub-Frame 1, 2, 3, 6, 7, 8 0 0 1 0 0 1 0 1
Binary Channel Bits Per Sub-Frame
For Sub-Frames 4, 9 Bits 456 2772 2772 6624 6336 6624 6624 6624
For Sub-Frame 5 Bits 360 2484 2484 6336 6048 6336 6336 6336
For Sub-Frame 0 Bits 176 1932 1932 5784 5520 5784 5784 5784
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 0 0 2772 0 0 6624 0 6624
Max. Throughput averaged over 1 kbps 37.6 332.8 913.6 800 765 2053 800 2053
frame
Note 1: 2 symbols allocated to PDCCH for 10 MHz channel BW. 4 symbols allocated to PDCCH for 1.4 MHz channel BW. 3
OFDM symbols allocated to PDCCH for 5 MHz channel BW.
Note 2: Reference signal, synchronization signals and PBCH allocated as defined in 3GPP TS 36.211 [16].
Note 3: If necessary the information bit payload size can be adjusted to facilitate the test implementation. The payload sizes
are defined in 3GPP TS 36.213 [3].
Note 4: Allocation is located in the middle of bandwidth.
Note 5: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block
(otherwise L = 0 Bit)
Note 6: PDSCH allocation applies only to subframes not configured as PRS subframes.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 511 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.1.2 TDD
Table A.3.1.1.2-1: PDSCH Reference Measurement Channels for TDD UL/DL configuration1
Parameter Unit Value
Reference channel R.2 R.4 R.0 R.1 R.3
TDD TDD TDD TDD TDD
Channel bandwidth MHz 1.4 3 5 10 10 20
Number of transmitter antennas 1 1 1 2 1
Allocated resource blocks (Note 4) 2 11 24 24 24
Uplink-Downlink Configuration (Note 5) 1 1 1 1 1
Special Subframe Configuration (Note 6) 6 6 6 6 6
Allocated subframes per Radio Frame 6 6 6 6 6
Modulation QPSK QPSK QPSK QPSK QPSK
Target Coding Rate 1/3 1/3 1/3 1/3 1/3
Information Bit Payload
For Sub-Frames 4,9 Bits 120 968 2088 2088 2088
For Sub-Frame 5 Bits 104 968 2088 2088 2088
For Sub-Frame 0 Bits 56 616 2088 1736 2088
For Sub-Frame 1, 6 (DwPTS) Bits 56 552 1032 1032 1032
Number of Code Blocks per Sub-Frame 1 1 1 1 1
(Note 7)
For Sub-Frames 4,9 1 1 1 1 1
For Sub-Frame 5 1 1 1 1 1
For Sub-Frame 0 1 1 1 1 1
For Sub-Frame 1, 6 (DwPTS) 1 1 1 1 1
Binary Channel Bits Per Sub-Frame
For Sub-Frames 4,9 Bits 456 2772 6624 6336 6624
For Sub-Frame 5 Bits 408 2628 6480 6192 6480
For Sub-Frame 0 Bits 224 2076 5928 5664 5928
For Sub-Frame 1, 6 (DwPTS) Bits 272 1616 3696 3504 3696
Max. Throughput averaged over 1 frame Mbps 0.051 0.462 1.041 1.006 1.0416
2 4 6 4
Note 1: 2 symbols allocated to PDCCH for 10 MHz channel BW. 3 OFDM symbols allocated to PDCCH for
5MHz channel BW. 4 symbols allocated to PDCCH for 1.4 MHz channel BW. For special subframe (1
& 6) only 2 OFDM symbols are allocated to PDCCH for all bandwidths.
Note 2: Reference signal, synchronization signals and PBCH allocated as defined in TS 36.211 [16].
Note 3: If necessary the information bit payload size can be adjusted to facilitate the test implementation. The
payload sizes are defined in TS 36.213 [3].
Note 4: Allocation is located in the middle of bandwidth.
Note 5: As per Table 4.2-2 in TS 36.211 [16]
Note 6: As per Table 4.2-1 in TS 36.211 [16]
Note 7: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to
each Code Block (otherwise L = 0 Bit)
Note 8: PDSCH allocation applies only to subframes not configured as PRS subframes.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 512 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.1.1.2-2: PDSCH Reference Measurement Channels for TDD UL/DL configuration0
Parameter Unit Value
Reference channel R.5
TDD
Channel bandwidth MHz 1.4 3 5 10 10 20
Number of transmitter antennas 1
Allocated resource blocks (Note 4) 24
Uplink-Downlink Configuration (Note 5) 0
Special Subframe Configuration (Note 6) 6
Allocated subframes per Radio Frame 4
Modulation QPSK
Target Coding Rate 1/3
Information Bit Payload
For Sub-Frames 4,9 Bits N/A
For Sub-Frame 5 Bits 2088
For Sub-Frame 0 Bits 2088
For Sub-Frame 1, 6 (DwPTS) Bits 1032
Number of Code Blocks per Sub-Frame 1
(Note 7)
For Sub-Frames 4,9 N/A
For Sub-Frame 5 1
For Sub-Frame 0 1
For Sub-Frame 1, 6 (DwPTS) 1
Binary Channel Bits Per Sub-Frame
For Sub-Frames 4,9 Bits N/A
For Sub-Frame 5 Bits 6480
For Sub-Frame 0 Bits 5928
For Sub-Frame 1, 6 (DwPTS) Bits 3696
Max. Throughput averaged over 1 frame Mbps 0.624
Note 1: 2 symbols allocated to PDCCH for 10 MHz channel BW. 3 OFDM symbols allocated to PDCCH for
5MHz channel BW. 4 symbols allocated to PDCCH for 1.4 MHz channel BW. For special subframe (1
& 6) only 2 OFDM symbols are allocated to PDCCH for all bandwidths.
Note 2: Reference signal, synchronization signals and PBCH allocated as defined in TS 36.211 [16].
Note 3: If necessary the information bit payload size can be adjusted to facilitate the test implementation. The
payload sizes are defined in TS 36.213 [3].
Note 4: Allocation is located in the middle of bandwidth.
Note 5: As per Table 4.2-2 in TS 36.211 [16]
Note 6: As per Table 4.2-1 in TS 36.211 [16]
Note 7: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to
each Code Block (otherwise L = 0 Bit)
Note 8: PDSCH allocation applies only to subframes not configured as PRS subframes.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 513 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.1.3 FDD for UE category 0
Table A.3.1.1.3-1: PDSCH Reference Measurement Channels for FDD
Parameter Unit Value
Reference channel R.13 FDD R.14 FDD R.15 FDD
Channel bandwidth MHz 10 10 10
Number of transmitter antennas 1 2 2
Allocated resource blocks (Note 4) 24 24 24
Allocated subframes per Radio Frame 10 10 10
Modulation QPSK QPSK QPSK
Target Coding Rate 1/10 1/10 1/10
Information Bit Payload
For Sub-Frames 4, 9 Bits 648 648 648
For Sub-Frame 5 Bits 648 648 648
For Sub-Frame 0 Bits 648 648 648
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 0 0 648
Number of Code Blocks per Sub-Frame
(Note 5)
For Sub-Frames 4, 9 1 1 1
For Sub-Frame 5 1 1 1
For Sub-Frame 0 1 1 1
For Sub-Frame 1, 2, 3, 6, 7, 8 0 0 1
Binary Channel Bits Per Sub-Frame
For Sub-Frames 4, 9 Bits 6624 6336 6636
For Sub-Frame 5 Bits 6336 6048 6408
For Sub-Frame 0 Bits 5784 5520 5520
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 0 0 6636
Max. Throughput averaged over 1 frame kbps 259.2 259.2 648
Note 1: 2 symbols allocated to PDCCH for 10 MHz channel BW. 4 symbols allocated to PDCCH for 1.4 MHz channel
BW. 3 OFDM symbols allocated to PDCCH for 5 MHz channel BW.
Note 2: Reference signal, synchronization signals and PBCH allocated as defined in 3GPP TS 36.211 [16].
Note 3: If necessary the information bit payload size can be adjusted to facilitate the test implementation. The payload
sizes are defined in 3GPP TS 36.213 [3].
Note 4: Allocation is located in the middle of bandwidth.
Note 5: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code
Block (otherwise L = 0 Bit)
Note 6: PDSCH allocation applies only to subframes not configured as PRS subframes.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 514 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.1.4 HD-FDD for UE category 0
Table A.3.1.1.4-1: PDSCH Reference Measurement Channels for HD-FDD
Parameter Unit Value
Reference channel R.1 HD-FDD R.2 HD-FDD
Channel bandwidth MHz 10 10
Number of transmitter antennas 1 2
Allocated resource blocks (Note 4) 24 24
Allocated subframes per Radio Frame 10 10
Modulation QPSK QPSK
Target Coding Rate 1/10 1/10
Information Bit Payload
For Sub-Frames 4, 9, Bits 0 0
For Sub-Frame 5 (Note 7) Bits 424 424
For Sub-Frame 0 (Note 7) Bits 648 648
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 0 0
Number of Code Blocks per Sub-Frame
(Note 5)
For Sub-Frames 4, 9 0 0
For Sub-Frame 5 1 1
For Sub-Frame 0 1 1
For Sub-Frame 1, 2, 3, 6, 7, 8 0 0
Binary Channel Bits Per Sub-Frame
For Sub-Frames 4, 9 Bits 0 0
For Sub-Frame 5 Bits 6336 6048
For Sub-Frame 0 Bits 5784 5520
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 0 0
Max. Throughput averaged over 1 frame kbps - -
Note 1: 2 symbols allocated to PDCCH for 10 MHz channel BW. 4 symbols allocated to PDCCH for 1.4 MHz channel
BW. 3 OFDM symbols allocated to PDCCH for 5 MHz channel BW.
Note 2: Reference signal, synchronization signals and PBCH allocated as defined in 3GPP TS 36.211 [16].
Note 3: If necessary the information bit payload size can be adjusted to facilitate the test implementation. The payload
sizes are defined in 3GPP TS 36.213 [3].
Note 4: Allocation is located in the middle of bandwidth.
Note 5: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code
Block (otherwise L = 0 Bit)
Note 6: PDSCH allocation applies only to subframes not configured as PRS subframes.
Note 7: Sub-frame 0 or sub-frame 5 is randomly scheduled in downlink.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 515 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.1.5 TDD for UE category 0
Table A.3.1.1.5-1: PDSCH Reference Measurement Channels for TDD UL/DL configuration1
Parameter Unit Value
Reference channel R.12 TDD R.13 TDD
Channel bandwidth MHz 10 10
Number of transmitter antennas 1 2
Allocated resource blocks (Note 4) 24 24
Uplink-Downlink Configuration (Note 5) 1 1
Special Subframe Configuration (Note 6) 6 6
Allocated subframes per Radio Frame 6 6
Modulation QPSK QPSK
Target Coding Rate 1/10 1/10
Information Bit Payload
For Sub-Frames 4,9 Bits 648 648
For Sub-Frame 5 Bits 648 648
For Sub-Frame 0 Bits 648 648
For Sub-Frame 1, 6 (DwPTS) Bits 488 488
Number of Code Blocks per Sub-Frame 1 1
(Note 7)
For Sub-Frames 4,9 1 1
For Sub-Frame 5 1 1
For Sub-Frame 0 1 1
For Sub-Frame 1, 6 (DwPTS) 1 1
Binary Channel Bits Per Sub-Frame
For Sub-Frames 4,9 Bits 6624 6336
For Sub-Frame 5 Bits 6580 6192
For Sub-Frame 0 Bits 5928 5664
For Sub-Frame 1, 6 (DwPTS) Bits 3696 3408
Max. Throughput averaged over 1 frame Mbps 0.3552 0.3552
Note 1: 2 symbols allocated to PDCCH for 10 MHz channel BW. 3 OFDM symbols allocated to PDCCH for 5MHz
channel BW. 4 symbols allocated to PDCCH for 1.4 MHz channel BW. For special subframe (1 & 6) only 2
OFDM symbols are allocated to PDCCH for all bandwidths.
Note 2: Reference signal, synchronization signals and PBCH allocated as defined in TS 36.211 [16].
Note 3: If necessary the information bit payload size can be adjusted to facilitate the test implementation. The payload
sizes are defined in TS 36.213 [3].
Note 4: Allocation is located in the middle of bandwidth.
Note 5: As per Table 4.2-2 in TS 36.211 [16]
Note 6: As per Table 4.2-1 in TS 36.211 [16]
Note 7: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code
Block (otherwise L = 0 Bit)
Note 8: PDSCH allocation applies only to subframes not configured as PRS subframes.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 516 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.1.6 Frame Structure 3
Table A.3.1.1.6-1: PDSCH Reference Measurement Channels for FS 3
Parameter Unit Value
Reference channel R.0 FS3
Channel bandwidth MHz 20
Number of transmitter antennas 1
Allocated resource blocks (Note 4) 24
Allocated subframes per Radio Frame 10
Modulation QPSK
Target Coding Rate 1/3
Information Bit Payload
For Sub-Frames 4, 9 Bits 2088
For Sub-Frame 5 Bits 2088
For Sub-Frame 0 Bits 2088
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 2088
Number of Code Blocks per Sub-Frame
(Note 5)
For Sub-Frames 4, 9 1
For Sub-Frame 5 1
For Sub-Frame 0 1
For Sub-Frame 1, 2, 3, 6, 7, 8 1
Binary Channel Bits Per Sub-Frame
For Sub-Frames 4, 9 Bits 6624
For Sub-Frame 5 Bits 6336
For Sub-Frame 0 Bits 6336
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 6624
Max. Throughput averaged over 1 frame kbps 2088
Note 1: 2 symbols allocated to PDCCH for 20 MHz channel BW.
Note 2: Reference signal, synchronization signals allocated as defined in 3GPP TS 36.211 [16].
Note 3: If necessary the information bit payload size can be adjusted to facilitate the test implementation. The
payload sizes are defined in 3GPP TS 36.213 [3].
Note 4: Allocation is located in the middle of bandwidth.
Note 5: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to
each Code Block (otherwise L = 0 Bit)
Note 6: PDSCH allocation applies only to subframes not configured as PRS subframes.
Note 7: PDSCH allocation applies only to subframes where there is no DRS transmission
Note 8: PDSCH is not transmitted in subframes where it is determined that transmission should not occur
according to the listen before talk (LBT model).
Note 9: Max throughput averaged over 1 frame does not account for missed PDSCH transmission due to LBT
or DRS transmission
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 517 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.2 PCFICH/PDCCH/PHICH
A.3.1.2.1 FDD
Table A.3.1.2.1-1: PCFICH/PDCCH/PHICH Reference Channel for FDD
Parameter Unit Value
Reference channel R.8 FDD R.14 R.11 R.12 R.10 R.13 R.6 R.7 R.9
FDD FDD FDD FDD FDD FDD FDD FDD
Channel bandwidth MHz 1.4 1.4 5 5 20 20 10 10 10
Number of transmitter antennas 1 1 1 2 1 2 1 2 2
Control region OFDM symbols 4 3 3 3 2 2 2 2 3
symbolsNote1
Aggregation level CCE 2 2 8 8 8 8 8 8 8
(Note 6) (Note 6)
DCI Format Note 3 Note 3 Note 3 Note 3 Note 3 Note 3 Note 3 Note 3 Note 3
Cell ID Note 4 Note 4 Note 4 Note 4 Note 4 Note 4 Note 4 Note 4 Note 4
Payload (without CRC) Bits Note 5 Note 5 Note 5 Note 5 Note 5 Note 5 Note 5 Note 5 Note 5
Note 1: The control region consists of PCFICH, PHICH and PDCCH.
Note 2: DCI formats are defined in TS 36.212.
Note 3: DCI format shall depend upon the test configuration.
Note 4: Cell ID shall depend upon the test configuration.
Note 5: Payload size shall depend upon the test configuration.
Note 6: For PDCCH using SI/RA/P-RNTI, Aggregation level 4 is used.
A.3.1.2.2 TDD
Table A.3.1.2.2-1: PCFICH/PDCCH/PHICH Reference Channel for TDD
Parameter Unit Value
Reference channel R.8 TDD R.14 R.11 R.12 R.10 R.13 R.6 R.7 R.9
TDD TDD TDD TDD TDD TDD TDD TDD
Channel bandwidth MHz 1.4 1.4 5 5 20 20 10 10 10
Number of transmitter antennas 1 1 1 2 1 2 1 2 2
Control region OFDM symbolsNote1 symbols 4 3 3 3 2 2 2 2 3
(Note 6) (Note 6)
Aggregation level CCE 2 2 8 8 8 8 8 8 8
(Note 7) (Note 7)
DCI Format Note 3 Note 3 Note 3 Note 3 Note 3 Note 3 Note 3 Note 3 Note 3
Cell ID Note 4 Note 4 Note 4 Note 4 Note 4 Note 4 Note 4 Note 4 Note 4
Payload (without CRC) Bits Note 5 Note 5 Note 5 Note 5 Note 5 Note 5 Note 5 Note 5 Note 5
Note 1: The control region consists of PCFICH, PHICH and PDCCH.
Note 2: DCI formats are defined in TS 36.212.
Note 3: DCI format shall depend upon the test configuration.
Note 4: Cell ID shall depend upon the test configuration.
Note 5: Payload size shall depend upon the test configuration.
Note 6: Only 2 OFDM symbols for special subframes 1 and 6.
Note 7: For PDCCH using SI/RA/P-RNTI, Aggregation level 4 is used.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 518 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.2.3 HD-FDD for UE category 0
Table A.3.1.2.3-1: PCFICH/PDCCH/PHICH Reference Channel for HD-FDD
Parameter Unit Value
Reference channel R.3 HD-FDD R.4 HD-FDD R.5 HD-FDD
Channel bandwidth MHz 10 10 10
Number of transmitter antennas 1 2 2
Control region OFDM symbolsNote1 symbols 2 2 3
Aggregation level CCE 8 8 8
DCI Format Note 3 Note 3 Note 3
Cell ID Note 4 Note 4 Note 4
Payload (without CRC) Bits Note 5 Note 5 Note 5
Note 1: The control region consists of PCFICH, PHICH and PDCCH.
Note 2: DCI formats are defined in TS 36.212.
Note 3: DCI format shall depend upon the test configuration.
Note 4: Cell ID shall depend upon the test configuration.
Note 5: Payload size shall depend upon the test configuration.
Note 6: For PDCCH using SI/RA/P-RNTI, Aggregation level 4 is used.
Note 7: Sub-frame 0 or sub-frame 5 is randomly scheduled in downlink.
A.3.1.2.4 FS 3
Table A.3.1.2.4-1: PCFICH/PDCCH/PHICH Reference Channel for FS 3
Parameter Unit Value
Reference channel R.0
FS3
Channel bandwidth MHz 10 10 1020
Number of transmitter antennas 1
Control region OFDM symbolsNote1 symbols 2
Aggregation level CCE 8
DCI Format Note 3
Cell ID Note 4
Payload (without CRC) Bits Note 5
Note 1: The control region consists of PCFICH, PHICH and PDCCH.
Note 2: DCI formats are defined in TS 36.212.
Note 3: DCI format shall depend upon the test configuration.
Note 4: Cell ID shall depend upon the test configuration.
Note 5: Payload size shall depend upon the test configuration.
Note 6: For PDCCH using SI/RA/P-RNTI, Aggregation level 4 is used.
Note 7: PCFICH/PDCCH/PHICH allocation applies only to subframes where there is no DRS
transmission
Note 8: PCFICH/PDCCH/PHICH are not transmitted in subframes where it is determined that
transmission should not occur according to the listen before talk (LBT model).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 519 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.3 MPDCCH Reference Channels for Cat-M1 UEs
A.3.1.3.1 FDD in CEModeA
Table A.3.1.3.1-1: MPDCCH Reference Channel for Cat-M1 FDD UEs in CEModeA
Parameter Unit Value
MPDCCH Reference channel - R.16 FDD R.17 FDD R.24 FDD R.25 FDD
Carrier bandwidth MHz 10 10 5 5
Number of transmitter - 1 2 1 2
antennas
DCI Format - 6-1A 6-1A 6-1A 6-1A
Transmission Type - Distributed Distributed Distributed Distributed
Number of PRB pairs per M- - 4 4 4 4
PDCCH set
Aggregation level ECCE 16 16 16 16
Maximum number of - 8 8 8 8
repetitions
Frequency hopping - ON ON ON ON
Number of narrowbands - 2 2 2 2
MPDCCH Narrowband - 1st 1st 1st 1st
Frequency HoppingOffset narrowbands 7 7 3 3
MPDCCH start subframe subframes 1 1 1 1
MPDCCH start symbol symbols 2 2 2 2
Frequency hopping interval subframes 4 4 4 4
Payload (without CRC) Bits Note 1 Note 1 Note 1 Note 1
Cell ID - Note 2 Note 2 Note 2 Note 2
Note 1: Payload size shall depend upon the test configuration.
Note 2: Cell ID shall depend upon the test configuration.
A.3.1.3.2 HD-FDD in CEModeA
Table A.3.1.3.2-1: MPDCCH Reference Channel for Cat-M1 HD-FDD UEs in CEModeA
Parameter Unit Value
MPDCCH Reference channel - R.6 HD-FDD R.7 HD-FDD R.14 HD-FDD R.15 HD-FDD
Carrier bandwidth MHz 10 10 5 5
Number of transmitter antennas - 1 2 1 2
DCI Format - 6-1A 6-1A 6-1A 6-1A
Transmission Type - Distributed Distributed Distributed Distributed
Number of PRB pairs per M- - 4 4 4 4
PDCCH set
Aggregation level ECCE 16 16 16 16
Maximum number of repetitions - 8 8 8 8
Frequency hopping - ON ON ON ON
Number of narrowbands - 2 2 2 2
MPDCCH Narrowband - 1st 1st 1st 1st
Frequency HoppingOffset narrowbands 7 7 3 3
MPDCCH start subframe subframes 1 1 1 1
MPDCCH start symbol symbols 2 2 2 2
Frequency hopping interval subframes 4 4 4 4
Payload (without CRC) Bits Note 1 Note 1 Note 1 Note 1
Cell ID - Note 2 Note 2 Note 2 Note 2
Note 1: Payload size shall depend upon the test configuration.
Note 2: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 520 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.3.3 TDD in CEModeA
Table A.3.1.3.3-1: MPDCCH Reference Channel for Cat-M1 TDD UEs in CEModeA
Parameter Unit Value
MPDCCH Reference channel - R.14 TDD R.15 TDD
Carrier bandwidth MHz 10 10
Number of transmitter antennas - 1 2
DCI Format - 6-1A 6-1A
Transmission Type - Distributed Distributed
Number of PRB pairs per M-PDCCH - 4 4
set
Aggregation level ECCE 16 16
Maximum number of repetitions - 8 8
Frequency hopping - ON ON
Number of narrowbands - 2 2
MPDCCH Narrowband - 1st 1st
Frequency HoppingOffset narrowbands 7 7
MPDCCH start subframe subframes 1 1
MPDCCH start symbol symbols 2 2
Frequency hopping interval subframes 10 10
Payload (without CRC) Bits Note 1 Note 1
Cell ID - Note 2 Note 2
Note 1: Payload size shall depend upon the test configuration.
Note 2: Cell ID shall depend upon the test configuration.
A.3.1.3.4 FDD in CEModeB
Table A.3.1.3.4-1: MPDCCH Reference Channel for Cat-M1 FDD UEs in CEModeB
Parameter Unit Value
MPDCCH Reference channel - R.18 FDD R.19 FDD R.26 FDD R.27 FDD
Carrier bandwidth MHz 10 10 5 5
Number of transmitter - 1 2 1 2
antennas
DCI Format - 6-1B 6-1B 6-1B 6-1B
Transmission Type - Distributed Distributed Distributed Distributed
Number of PRB pairs per M- - 6 6 6 6
PDCCH set
Aggregation level ECCE 24 24 24 24
Maximum number of - 128 128 128 128
repetitions
Frequency hopping - ON ON ON ON
Number of narrowbands - 2 2 2 2
MPDCCH Narrowband - 1st 1st 1st 1st
Frequency HoppingOffset narrowbands 7 7 3 3
MPDCCH start subframe subframes 1 1 1 1
MPDCCH start symbol symbols 2 2 2 2
Frequency hopping interval subframes 8 8 8 8
Payload (without CRC) Bits 18 18 17 17
Cell ID - Note 1 Note 1 Note 1 Note 1
Note 1: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 521 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.3.5 HD-FDD in CEModeB
Table A.3.1.3.5-1: MPDCCH Reference Channel for Cat-M1 HD-FDD UEs in CEModeB
Parameter Unit Value
MPDCCH Reference channel - R.8 HD-FDD R.9 HD-FDD R.16 HD-FDD R.17 HD-FDD
Carrier bandwidth MHz 10 10 5 5
Number of transmitter - 1 2 1 2
antennas
DCI Format - 6-1B 6-1B 6-1B 6-1B
Transmission Type - Distributed Distributed Distributed Distributed
Number of PRB pairs per M- - 6 6 6 6
PDCCH set
Aggregation level ECCE 24 24 24 24
Maximum number of - 128 128 128 128
repetitions
Frequency hopping - ON ON ON ON
Number of narrowbands - 2 2 2 2
MPDCCH Narrowband - 1st 1st 1st 1st
Frequency HoppingOffset narrowbands 7 7 3 3
MPDCCH start subframe subframes 1 1 1 1
MPDCCH start symbol symbols 2 2 2 2
Frequency hopping interval subframes 8 8 8 8
Payload (without CRC) Bits 18 18 17 17
Cell ID - Note 1 Note 1 Note 1 Note 1
Note 1: Cell ID shall depend upon the test configuration.
A.3.1.3.6 TDD in CEModeB
Table A.3.1.3.6-1: MPDCCH Reference Channel for Cat-M1 TDD UEs in CEModeB
Parameter Unit Value
MPDCCH Reference channel - R.16 TDD R.17 TDD
Carrier bandwidth MHz 10 10
Number of transmitter - 1 2
antennas
DCI Format - 6-1B 6-1B
Transmission Type - Distributed Distributed
Number of PRB pairs per M- - 6 6
PDCCH set
Aggregation level ECCE 24 24
Maximum number of - 128 128
repetitions
Frequency hopping - ON ON
Number of narrowbands - 2 2
MPDCCH Narrowband - 1st 1st
Frequency HoppingOffset narrowbands 7 7
MPDCCH start subframe subframes 1 1
MPDCCH start symbol symbols 2 2
Frequency hopping interval subframes 20 20
Payload (without CRC) Bits 18 18
Cell ID - Note 1 Note 1
Note 1: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 522 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.4 PDSCH Reference Channel for Cat-M1 UEs
A.3.1.4.1 FDD in CEModeA
Table A.3.1.4.1-1: PDSCH Reference Channel for Cat-M1 FDD in CEModeA
Parameter Unit Value
PDSCH Reference R.20 FDD R.21 FDD R.28 FDD R.29 FDD
channel
Carrier bandwidth MHz 10 10 5 5
Number of transmitter 1 2 1 2
antennas
Allocated resource PRBs 2 2 2 2
blocksNote1
Allocated subframes per subframes 10 10 10 10
Radio Frame
Modulation QPSK QPSK QPSK QPSK
Target coding rate 1/3 1/3 1/3 1/3
Information Bit Payload
Sub-Frames 0 ~ 9 Bits 32 32 32 32
Number of Code Blocks
per Sub-Frame
Sub-Frames 0 ~ 9 1 1 1 1
Maximum number of 16 16 16 16
repetitions
Frequency hopping ON ON ON ON
Number of narrowbands narrowbands 2 2 2 2
for frequency hopping
PDSCH Narrowband 2nd 2nd 2nd 2nd
Frequency narrowbands 7 7 3 3
HoppingOffset
PDSCH start symbol symbols 2 2 2 2
Frequency hopping subframes 4 4 4 4
interval
Max. Throughput kbps TBD TBD TBD TBD
averaged over 1 frame
Cell ID Note 2 Note 2 Note 2 Note 2
Note 1: Allocation is located in the middle of narrowband.
Note 2: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 523 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.4.2 HD-FDD in CEModeA
Table A.3.1.4.2-1: PDSCH Reference Channel for Cat-M1 HD-FDD in CEModeA
Parameter Unit Value
PDSCH Reference channel R.10 HD-FDD R.11 HD-FDD R.18 HD-FDD R.19 HD-FDD
Carrier bandwidth MHz 10 10 5 5
Number of transmitter 1 2 1 2
antennas
Allocated resource blocksNote1 PRBs 2 2 2 2
Allocated subframes per Radio subframes 10 10 10 10
Frame
Modulation QPSK QPSK QPSK QPSK
Target coding rate 1/3 1/3 1/3 1/3
Information Bit Payload
Sub-Frames 0 ~ 9 Bits 32 32 32 32
Number of Code Blocks per
Sub-Frame
Sub-Frames 0 ~ 9 1 1 1 1
Maximum number of 16 16 16 16
repetitions
Frequency hopping ON ON ON ON
Number of narrowbands for narrowbands 2 2 2 2
frequency hopping
PDSCH Narrowband 1st 1st 1st 1st
Frequency HoppingOffset narrowbands 7 7 3 3
PDSCH start symbol symbols 2 2 2 2
Frequency hopping interval subframes 4 4 4 4
Max. Throughput averaged kbps TBD TBD TBD TBD
over 1 frame
Cell ID Note 2 Note 2 Note 2 Note 2
Note 1: Allocation is located in the middle of narrowband.
Note 2: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 524 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.4.3 TDD in CEModeA
Table A.3.1.4.3-1: PDSCH Reference Channel for Cat-M1 TDD in CEModeA
Parameter Unit Value
PDSCH Reference channel R.16 TDD R.17 TDD
Carrier bandwidth MHz 10 10
Number of transmitter antennas 1 2
Allocated resource blocksNote1 PRBs 2 2
Allocated subframes per Radio Frame 4 4
TDD Uplink-Downlink Configuration 0 0
TDD Special Subframe Configuration 6 6
Modulation QPSK QPSK
Target coding rate 1/3 1/3
Information Bit Payload
All Sub-Frames except 1, 6 (TDD) Bits 32 32
All Sub-Frames except 1, 6 (TDD - 0 0
DwPTS)
Number of Code Blocks per Sub-Frame 1 1
All Sub-Frames except 1, 6 (TDD) 1 1
All Sub-Frames except 1, 6 (TDD 0 0
DwPTS)
Maximum number of repetitions 16 16
Frequency hopping ON ON
Number of narrowbands for frequency 2 2
hopping
PDSCH Narrowband 2nd 2nd
Frequency HoppingOffset narrowbands 7 7
PDSCH start symbol symbols 2 2
Frequency hopping interval subframes 10 10
Max. Throughput averaged over 1 frame kbps TBD TBD
Cell ID Note 2 Note 2
Note 1: Allocation is located in the middle of narrowband.
Note 2: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 525 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.4.4 FDD in CEModeB
Table A.3.1.4.4-1: PDSCH Reference Channel for Cat-M1 FDD in CEModeB
Parameter Unit Value
PDSCH Reference R.22 FDD R.23 FDD R.30 FDD R.31 FDD
channel
Carrier bandwidth MHz 10 10 5 5
Number of transmitter 1 2 1 2
antennas
Allocated resource 2 2 2 2
blocksNote1
Allocated subframes per - 10 10 10 10
Radio Frame
Modulation - QPSK QPSK QPSK QPSK
Target coding rate - 1/3 1/3 1/3 1/3
Information Bit Payload
Sub-Frames 0 ~ 9 Bits 32 32 32 32
Number of Code Blocks
per Sub-Frame
Sub-Frames 0 ~ 9 - 1 1 1 1
Maximum number of - 192 192 192 192
repetitions
Frequency hopping - ON ON ON ON
Number of narrowbands narrowbands 2 2 2 2
for frequency hopping
PDSCH Narrowband - 2nd 2nd 2nd 2nd
Frequency narrowbands 7 7 3 3
HoppingOffset
PDSCH start symbol symbols 2 2 2 2
Frequency hopping subframes 8 8 8 8
interval
Max. Throughput kbps TBD TBD TBD TBD
averaged over 1 frame
Cell ID Note 2 Note 2 Note 2 Note 2
Note 1: Allocation is located in the middle of narrowband.
Note 2: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 526 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.4.5 HD-FDD in CEModeB
Table A.3.1.4.5-1: PDSCH Reference Channel for Cat-M1 HD-FDD in CEModeB
Parameter Unit Value
PDSCH Reference channel R.12 HD-FDD R.13 HD-FDD R.20 HD-FDD R.21 HD-FDD
Carrier bandwidth MHz 10 10 5 5
Number of transmitter antennas 1 2 1 2
Allocated resource blocksNote1 PRBs 2 2 2 2
Allocated subframes per Radio subframes 10 10 10 10
Frame
Modulation QPSK QPSK QPSK QPSK
Target coding rate 1/3 1/3 1/3 1/3
Information Bit Payload
Sub-Frames 0 ~ 9 Bits 32 32 32 32
Number of Code Blocks per Sub-
Frame
Sub-Frames 0 ~ 9 1 1 1 1
Maximum number of repetitions 192 192 192 192
Frequency hopping ON ON ON ON
Number of narrowbands for narrowbands 2 2 2 2
frequency hopping
PDSCH Narrowband 1st 1st 1st 1st
Frequency HoppingOffset narrowbands 7 7 3 3
PDSCH start symbol symbols 2 2 2 2
Frequency hopping interval subframes 8 8 8 8
Max. Throughput averaged over kbps TBD TBD TBD TBD
1 frame
Cell ID Note 2 Note 2 Note 2 Note 2
Note 1: Allocation is located in the middle of narrowband.
Note 2: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 527 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.4.6 TDD in CEModeB
Table A.3.1.4.6-1: PDSCH Reference Channel for Cat-M1 TDD in CEModeB
Parameter Unit Value
PDSCH Reference channel R.18 TDD R.19 TDD
Carrier bandwidth MHz 10 10
Number of transmitter antennas 1 2
Allocated resource blocksNote1 PRBs 2 2
Allocated subframes per Radio Frame 4 4
TDD Uplink-Downlink Configuration 0 0
TDD Special Subframe Configuration 6 6
Modulation QPSK QPSK
Target coding rate 1/3 1/3
Information Bit Payload
All Sub-Frames except 1, 6 (TDD) Bits 32 32
All Sub-Frames except 1, 6 (TDD - 0 0
DwPTS)
Number of Code Blocks per Sub-Frame 1 1
All Sub-Frames except 1, 6 (TDD) 1 1
All Sub-Frames except 1, 6 (TDD 0 0
DwPTS)
Maximum number of repetitions 192 192
Frequency hopping ON ON
Number of narrowbands for frequency 2 2
hopping
PDSCH Narrowband 2nd 2nd
Frequency HoppingOffset narrowbands 7 7
PDSCH start symbol symbols 2 2
Frequency hopping interval subframes 20 20
Max. Throughput averaged over 1 frame kbps TBD TBD
Cell ID Note 2 Note 2
Note 1: Allocation is located in the middle of narrowband.
Note 2: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 528 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.5 NPDSCH Reference Channel for UE category NB1
A.3.1.5.1 HD-FDD in-band operation
Table A.3.1.5.1-1: NPDSCH Reference Channel for UE category NB1 for in-band operation
Parameter Unit Value
NPDSCH Reference channel - R.14 HD-FDD R.15 HD-FDD
LTE Carrier bandwidth MHz 10 10
Allocated resource blocks PRB 1 1
Number of transmitter antennas - 1 2
Allocated subframes per Radio subframes Note 1 Note 1
Frame
Modulation QPSK QPSK
Target coding rate 1/3 1/3
Information Bit Payload
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 40 Note 2 40 Note 2
For Sub-Frame 4, 9 Bits Note 3 Note 3
For Sub-Frame 0, 5 Bits 0 0
Number of Code Blocks per Sub-
Frame
For Sub-Frame 1, 2, 3, 6, 7, 8 1 Note 4 1 Note 4
For Sub-Frame 4, 9 Note 5 Note 5
For Sub-Frame 0, 5 0 0
Maximum number of repetitions - Note 6 Note 6
NPDCCH start symbol symbols 3 3
Cell ID - Note 7 Note 7
Note 1: Shall depend upon the NPDSCH scheduling.
Note 2: Only apply for subframes scheduled with NPDSCH.
Note 3: 40 for subframes scheduled with NPDSCH when nf mod 2 ≠ 0. Otherwise 0.
Note 4: Only apply for subframes scheduled with NPDSCH.
Note 5: 1 for subframes scheduled with NPDSCH when nf mod 2 ≠ 0. Otherwise 0.
Note 6: Maximum number of repetitions shall depend upon the test configuration.
Note 7: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 529 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.5.2 Void
A.3.1.5.3 HD-FDD standalone operation
Table A.3.1.5.3-1: NPDSCH Reference Channel for UE category NB1 for standalone operation
Parameter Unit Value
NPDSCH Reference channel - R.18 HD-FDD R.19 HD-FDD
Channel bandwidth KHz 200 200
Number of transmitter antennas - 1 2
Allocated subframes per Radio subframes Note 1 Note 1
Frame
Modulation QPSK QPSK
Target coding rate 1/3 1/3
Information Bit Payload
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 72 Note 2 72 Note 2
For Sub-Frame 4, 9 Bits Note 3 Note 3
For Sub-Frame 0, 5 Bits 0 0
Number of Code Blocks per Sub-
Frame
For Sub-Frame 1, 2, 3, 6, 7, 8 1 Note 4 1 Note 4
For Sub-Frame 4, 9 Note 5 Note 5
For Sub-Frame 0, 5 0 0
Maximum number of repetitions - Note 6 Note 6
Cell ID - Note 7 Note 7
Note 1: Shall depend upon the NPDSCH scheduling
Note 2: Only apply for subframes scheduled with NPDSCH.
Note 3: 72 for subframes scheduled with NPDSCH when nf mod 2 ≠ 0. Otherwise 0.
Note 4: only apply for subframes scheduled with NPDSCH..
Note 5: 1 for subframes scheduled with NPDSCH when nf mod 2 ≠ 0. Otherwise 0.
Note 6: Maximum number of repetitions shall depend upon the test configuration.
Note 7: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 530 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.5.4 Void
A.3.1.5.5 HD-FDD guard band operation
Table A.3.1.5.5-1: NPDSCH Reference Channel for UE category NB1 for guard band operation
Parameter Unit Value
NPDSCH Reference channel - R.22 HD-FDD R.23 HD-FDD
LTE Carrier bandwidth MHz 10 10
Allocated resource blocks for NB- PRB 1 1
IoT
Number of transmitter antennas - 1 2
Allocated subframes per Radio subframes Note 1 Note 1
Frame
Modulation QPSK QPSK
Target coding rate 1/3 1/3
Information Bit Payload
For Sub-Frame 1, 2, 3, 6, 7, 8 Bits 72 Note 2 72 Note 2
For Sub-Frame 4, 9 Bits Note 3 Note 3
For Sub-Frame 0, 5 Bits 0 0
Number of Code Blocks per Sub-
Frame
For Sub-Frame 1, 2, 3, 6, 7, 8 1 Note 4 1 Note 4
For Sub-Frame 4, 9 Note 5 Note 5
For Sub-Frame 0, 5 0 0
Maximum number of repetitions - Note 6 Note 6
Cell ID - Note 7 Note 7
Note 1: Shall depend upon the NPDSCH scheduling.
Note 2: Only apply for subframes scheduled with NPDSCH.
Note 3: 72 for subframes scheduled with NPDSCH when nf mod 2 ≠ 0. Otherwise 0.
Note 4: Only apply for subframes scheduled with NPDSCH.
Note 5: 1 for subframes scheduled with NPDSCH when nf mod 2 ≠ 0. Otherwise 0.
Note 6: Maximum number of repetitions shall depend upon the test configuration.
Note 7: Cell ID shall depend upon the test configuration.
A.3.1.5.6 Void
A.3.1.6 NPDCCH Reference Channel for UE category NB1
A.3.1.6.1 HD-FDD in-band operation
Table A.3.1.6.1-1: NPDCCH Reference Channel for UE category NB1 for in-band operation
Parameter Unit Value
NPDCCH Reference channel - R.26 HD-FDD R.27 HD-FDD
LTE Carrier bandwidth MHz 10 10
Allocated resource blocks Note1 PRB 1 1
Number of transmitter antennas - 1 2
DCI Format - N1 N1
Aggregation level NCCE 2 2
Maximum number of repetitions - Note 2 Note 2
NPDCCH start symbol symbols 3 3
Payload (without CRC) Bits Note 3 Note 3
Cell ID - Note 4 Note 4
Note 1: Allocation is located in the middle of narrowband.
Note 2: Maximum number of repetitions shall depend upon the test configuration.
Note 3: Payload size shall depend upon the test configuration.
Note 4: Cell ID shall depend upon the test configuration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 531 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.1.6.2 Void
A.3.1.6.3 HD-FDD standalone operation
Table A.3.1.6.3-1: NPDCCH Reference Channel for UE category NB1 for standalone operation
Parameter Unit Value
NPDCCH Reference channel - R.30 HD-FDD R.31 HD-FDD
Channel bandwidth KHz 200 200
Number of transmitter antennas - 1 2
DCI Format - N1 N1
Aggregation level NCCE 2 2
Maximum number of repetitions - Note 2 Note 2
Payload (without CRC) Bits Note 3 Note 3
Cell ID - Note 4 Note 4
Note 1: Allocation is located in the middle of narrowband.
Note 2: Maximum number of repetitions shall depend upon the test configuration.
Note 3: Payload size shall depend upon the test configuration.
Note 4: Cell ID shall depend upon the test configuration.
A.3.1.6.4 Void
A.3.1.6.5 HD-FDD guard band operation
Table A.3.1.6.5-1: NPDCCH Reference Channel for UE category NB1 for guard band operation
Parameter Unit Value
NPDCCH Reference channel - R.34 HD-FDD R.35 HD-FDD
LTE Carrier bandwidth MHz 10 10
Allocated resource blocks for NB- PRB 1 1
ioTNote1
Number of transmitter antennas - 1 2
DCI Format - N1 N1
Aggregation level NCCE 2 2
Maximum number of repetitions - Note 2 Note 2
Payload (without CRC) Bits Note 3 Note 3
Cell ID - Note 4 Note 4
Note 1: Allocation is located in the middle of narrowband.
Note 2: Maximum number of repetitions shall depend upon the test configuration.
Note 3: Payload size shall depend upon the test configuration.
Note 4: Cell ID shall depend upon the test configuration.
A.3.1.6.6 Void
A.3.2 OFDMA Channel Noise Generator (OCNG)
A.3.2.1 OCNG Patterns for FDD
The following OCNG patterns are used for modelling allocations to virtual UEs (which are not under test) and/or
allocations used for MBSFN. The OCNG pattern for each sub frame specifies the allocations that shall be filled with
OCNG, and furthermore, the relative power level of each such allocation.
In each test case the OCNG is expressed by parameters OCNG_RA and OCNG_RB which together with a relative
power level ( γ ) specifies the PDSCH EPRE-to-RS EPRE ratios in OFDM symbols without and with reference symbols,
respectively. The relative power, which is used for modelling boosting per virtual UE allocation, is expressed by:
γ i = PDSCH i _ RA / OCNG _ RA = PDSCH i _ RB / OCNG _ RB,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 532 ETSI TS 136 133 V14.3.0 (2017-04)
where γi denotes the relative power level of the i:th virtual UE. The parameter settings of OCNG_RA, OCNG_RB,
and the set of relative power levels γ are chosen such that when also taking allocations to the UE under test into
account, as given by a PDSCH reference channel, a constant transmitted power spectral density that is constant on an
OFDM symbol basis is targeted.
Moreover the OCNG pattern is accompanied by a PCFICH/PDCCH/PHICH reference channel which specifies the
control region. The number of PDCCH OFDM symbols in the non-MBSFN subframes is the same as specified in the
RMC used in the test. The number of PDCCH OFDM symbols in the MBSFN subframe is the maximal allowed
according to TS 36.213 [16]. For any aggregation and PHICH allocation, the PDCCH and any unused PHICH groups
are padded with resource element groups with a power level given by PDCCH_RA/RB and PHICH_RA/RB as
specified in the test case such that a total power spectral density in the control region that is constant on an OFDM
symbol basis is targeted.
For subframes configured as PRS subframes the PDSCH allocation defined in the OCNG pattern does not apply.
For subframes configured as ABS subframes the PDSCH and PMCH allocation defined in the OCNG pattern does not
apply.
The system information is scheduled in the allocations reserved for the OCNG patterns, in the subframes not configured
for MBSFN. For this purpose the number of the RB-s allocated with PDSCH defined in the OCNG pattern can be
reduced as necessary.
A.3.2.1.1 OCNG FDD pattern 1: outer resource blocks allocation in 10 MHz
Table A.3.2.1.1-1: OP.1 FDD: OCNG FDD Pattern 1
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4,9 1-3, 6-8
0 – 12 0 0 0 N/A
Note 1 N/A
37 – 49 0 0 0 N/A
0-49 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated. The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH symbols shall not
contain cell-specific Reference Signals. PMCH subframes shall contain cell-specific
Reference Signals only in the first symbol of the first time slot. The parameter γ PRB is
used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in clause 7.1 in TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 533 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.2 OCNG FDD pattern 2: full bandwidth allocation in 10 MHz
Table A.3.2.1.2-1: OP.2 FDD: OCNG FDD Pattern 2
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4, 9 1 – 3, 6 – 8
0 – 49 0 0 0 N/A Note 1 N/A
0 – 49 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated. The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH subframes shall
contain cell-specific Reference Signals only in the first symbol of the first time slot.
The parameter γ PRB is used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in clause 7.1 in TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 534 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.3 OCNG FDD pattern 3: outer resource blocks allocation in 1.4 MHz
Table A.3.2.1.3-1: OP.3 FDD: OCNG FDD Pattern 3
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4,9 1-3, 6-8
0–1 0 0 0 N/A
Note 1 N/A
4–5 0 0 0 N/A
0–5 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated. The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH symbols shall not
contain cell-specific Reference Signals. PMCH subframes shall contain cell-specific
Reference Signals only in the first symbol of the first time slot. The parameter γ PRB is
used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in clause 7.1 in TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
A.3.2.1.4 OCNG FDD pattern 4: full bandwidth allocation in 1.4 MHz
Table A.3.2.1.4-1: OP.4 FDD: OCNG FDD Pattern 4
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4, 9 1 – 3, 6 – 8
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 535 ETSI TS 136 133 V14.3.0 (2017-04)
0–5 0 0 0 N/A Note 1 N/A
0–5 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated.The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH subframes shall
contain cell-specific Reference Signals only in the first symbol of the first time slot.
The parameter γ PRB is used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in clause 7.1 in TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
A.3.2.1.5 OCNG FDD pattern 5: outer resource blocks allocation in 10 MHz (without
MBSFN)
Table A.3.2.1.5-1: OP.5 FDD: OCNG FDD Pattern 5
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4,9 1-3, 6-8
0 – 12 0 0 0 N/A
37 – 49 0 0 0 N/A Note 2
0 – 49 N/A N/A N/A 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the
subframes not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
γ
QPSK modulated. The parameter PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH
part of OCNG shall be transmitted to the virtual users by all the transmit
antennas with CRS and according to the antenna transmission mode 2.
γ
The parameter PRB applies to each antenna port separately, so the
transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in clause 7.1 in TS 36.213.
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 536 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.6 OCNG FDD pattern 6: full bandwidth allocation in 10 MHz (without MBSFN)
Table A.3.2.1.6-1: OP.6 FDD: OCNG FDD Pattern 6
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4, 9 1 – 3, 6 – 8
0 – 49 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the
subframes not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
QPSK modulated. The parameter γ PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the
PDSCH part of OCNG shall be transmitted to the virtual users by all the
transmit antennas with CRS and according to the antenna transmission
mode 2. The parameter γ PRB applies to each antenna port separately, so
the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in clause 7.1 in TS 36.213.
N/A: Not Applicable
A.3.2.1.7 OCNG FDD pattern 7: full bandwidth allocation in 1.4 MHz (without MBSFN)
Table A.3.2.1.8-1: OP.7 FDD: OCNG FDD Pattern 7
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4, 9 1 – 3, 6 – 8
0–5 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the
subframes not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
QPSK modulated. The parameter γ PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the
PDSCH part of OCNG shall be transmitted to the virtual users by all the
transmit antennas with CRS and according to the antenna transmission
mode 2. The parameter γ PRB applies to each antenna port separately, so
the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in clause 7.1 in TS 36.213.
N/A: Not Applicable
A.3.2.1.8 OCNG FDD pattern 8: outer resource blocks allocation in 10 MHz for MBSFN
ABS
Table A.3.2.1.8-1: OP.8 FDD: OCNG FDD Pattern 8
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 537 ETSI TS 136 133 V14.3.0 (2017-04)
0 5 4,9 (1-3, 6-8)Note4
0 – 12 0 0 0 N/A
37 – 49 0 0 0 N/A Note 2
0 – 49 N/A N/A N/A 0
Note 1: PDSCH allocation does not apply to subframes configured as PRS
subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
γ
QPSK modulated. The parameter PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH
part of OCNG shall be transmitted to the virtual users by all the transmit
antennas with CRS and according to the antenna transmission mode 2.
γ
The parameter PRB applies to each antenna port separately, so the
transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in clause 7.1 in TS 36.213.
Note 4: The subframe(s) configured as MBSFN ABS in a test shall not contain any
PMCH data and shall contain CRS only in the first symbol of the first time
slot. The subframe(s) configured as MBSFN ABS depend upon the
MBSFN ABS pattern used in the test.
N/A: Not Applicable
A.3.2.1.9 OCNG FDD pattern 9: full bandwidth allocation in 10 MHz for MBSFN ABS
Table A.3.2.1.9-1: OP.9 FDD: OCNG FDD Pattern 9
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4, 9 (1-3, 6-8)Note4
0 – 49 0 0 0 0 Note 2
Note 1: PDSCH allocation applies only to subframes not configured as PRS
subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
QPSK modulated. The parameter γ PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the
PDSCH part of OCNG shall be transmitted to the virtual users by all the
transmit antennas with CRS and according to the antenna transmission
mode 2. The parameter γ PRB applies to each antenna port separately, so
the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in clause 7.1 in TS 36.213.
Note 4: The subframe(s) configured as MBSFN ABS in a test shall not contain any
PMCH data and shall contain CRS only in the first symbol of the first time
slot. The subframe(s) configured as MBSFN ABS depend upon the
MBSFN ABS pattern used in the test.
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 538 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.10 OCNG FDD pattern 10: outer resource blocks allocation in 10 MHz with user
data in every subframe (without MBSFN)
Table A.3.2.1.10-1: OP.10 FDD: OCNG FDD Pattern 10
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 4, 9 1 - 3, 6 - 8
0 - 12 0 0 0 0
Note 2
37 - 49 0 0 0 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes
not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual
UEs with one PDSCH per virtual UE; the data transmitted over the OCNG
PDSCHs shall be uncorrelated pseudo random data, which is QPSK modulated.
γ
The parameter PRB is used to scale the power of PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part
of OCNG shall be transmitted to the virtual users by all the transmit antennas
with CRS and according to the antenna transmission mode 2. The parameter
γ PRB applies to each antenna port separately, so the transmit power of the
PDSCH part of OCNG is equal between all the transmit antennas with CRS used
in the test. The antenna transmission modes are specified in section 7.1 in 3GPP
TS 36.213.
N/A: Not Applicable
A.3.2.1.11 OCNG FDD pattern 11: outer resource blocks allocation in 20 MHz
Table A.3.2.1.11-1: OP.11 FDD: OCNG FDD Pattern 11
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4,9 1-3, 6-8
0 – 37 0 0 0 N/A
Note 1 N/A
62 – 99 0 0 0 N/A
0-99 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated. The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH symbols shall not
contain cell-specific Reference Signals. PMCH subframes shall contain cell-specific
Reference Signals only in the first symbol of the first time slot. The parameter γ PRB is
used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in section 7.1 in 3GPP TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 539 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.12 OCNG FDD pattern 12: full bandwidth allocation in 20 MHz
Table A.3.2.1.12-1: OP.12 FDD: OCNG FDD Pattern 12
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4, 9 1 – 3, 6 – 8
0 – 99 0 0 0 N/A Note 1 N/A
0 – 99 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated. The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH subframes shall
contain cell-specific Reference Signals only in the first symbol of the first time slot.
The parameter γ PRB is used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in section 7.1 in 3GPP TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 540 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.13 OCNG FDD pattern 13: outer resource blocks allocation in 20 MHz (without
MBSFN)
Table A.3.2.1.13-1: OP.13 FDD: OCNG FDD Pattern 13
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4,9 1-3, 6-8
0 – 37 0 0 0 N/A
62 – 99 0 0 0 N/A Note 2
0 – 99 N/A N/A N/A 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the
subframes not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
γ
QPSK modulated. The parameter PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the
PDSCH part of OCNG shall be transmitted to the virtual users by all the
transmit antennas with CRS and according to the antenna transmission
γ
mode 2. The parameter PRB applies to each antenna port separately, so
the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in section 7.1 in 3GPP TS 36.213.
N/A: Not Applicable
A.3.2.1.14 OCNG FDD pattern 14: full bandwidth allocation in 20 MHz (without MBSFN)
Table A.3.2.1.14-1: OP.14 FDD: OCNG FDD Pattern 14
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4, 9 1 – 3, 6 – 8
0 – 99 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the
subframes not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
QPSK modulated. The parameter γ PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the
PDSCH part of OCNG shall be transmitted to the virtual users by all the
transmit antennas with CRS and according to the antenna transmission
mode 2. The parameter γ PRB applies to each antenna port separately, so
the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in section 7.1 in 3GPP TS 36.213.
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 541 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.15 OCNG FDD pattern 15: outer resource blocks allocation in 5 MHz
Table A.3.2.1.15-1: OP.15 FDD: OCNG FDD Pattern 15
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4,9 1-3, 6-8
0–6 0 0 0 N/A
Note 1 N/A
18 – 24 0 0 0 N/A
0-24 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated. The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH symbols shall not
contain cell-specific Reference Signals. PMCH subframes shall contain cell-specific
Reference Signals only in the first symbol of the first time slot. The parameter γ PRB is
used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in section 7.1 in 3GPP TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 542 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.16 OCNG FDD pattern 16: full bandwidth allocation in 5 MHz
Table A.3.2.1.16-1: OP.16 FDD: OCNG FDD Pattern 16
Allocation Relative power level γ PRB [dB] PDSCH PMCH
n PRB Data Data
Subframe
0 5 4, 9 1 – 3, 6 – 8
0 – 24 0 0 0 N/A Note 1 N/A
0 – 24 N/A N/A N/A Note 4 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs
with one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall
be uncorrelated pseudo random data, which is QPSK modulated. The parameter
γ PRB is used to scale the power of PDSCH.
Note 2: Each physical resource block (PRB) is assigned to MBSFN transmission. The data in
each PRB shall be uncorrelated with data in other PRBs over the period of any
measurement. The MBSFN data shall be QPSK modulated. PMCH subframes shall
contain cell-specific Reference Signals only in the first symbol of the first time slot.
The parameter γ PRB is used to scale the power of PMCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part of
OCNG shall be transmitted to the virtual users by all the transmit antennas with CRS
and according to the antenna transmission mode 2. The parameter γ PRB applies to
each antenna port separately, so the transmit power of the PDSCH part of OCNG is
equal between all the transmit antennas with CRS used in the test. The antenna
transmission modes are specified in section 7.1 in 3GPP TS 36.213.
Note 4: 0dB for 1 transmit antenna with CRS, +3dB for 2 transmit antennas with CRS
N/A: Not Applicable
A.3.2.1.17 OCNG FDD pattern 17: outer resource blocks allocation in 20 MHz with user
data in every subframe (without MBSFN)
Table A.3.2.1.17-1: OP.17 FDD: OCNG FDD Pattern 17
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 4, 9 1 - 3, 6 - 8
0 - 37 0 0 0 0
Note 2
62 - 99 0 0 0 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes
not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual
UEs with one PDSCH per virtual UE; the data transmitted over the OCNG
PDSCHs shall be uncorrelated pseudo random data, which is QPSK modulated.
γ
The parameter PRB is used to scale the power of PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part
of OCNG shall be transmitted to the virtual users by all the transmit antennas
with CRS and according to the antenna transmission mode 2. The parameter
γ PRB applies to each antenna port separately, so the transmit power of the
PDSCH part of OCNG is equal between all the transmit antennas with CRS used
in the test. The antenna transmission modes are specified in section 7.1 in 3GPP
TS 36.213.
N/A: Not Applicable.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 543 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.18 OCNG FDD pattern 18: outer resource blocks allocation in 5 MHz (without
MBSFN)
Table A.3.2.1.18-1: OP.18 FDD: OCNG FDD Pattern 18
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4,9 1-3, 6-8
0–6 0 0 0 N/A
18 – 24 0 0 0 N/A Note 2
0 – 24 N/A N/A N/A 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the
subframes not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
γ
QPSK modulated. The parameter PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the
PDSCH part of OCNG shall be transmitted to the virtual users by all the
transmit antennas with CRS and according to the antenna transmission
γ
mode 2. The parameter PRB applies to each antenna port separately, so
the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in section 7.1 in 3GPP TS 36.213.
N/A: Not Applicable
A.3.2.1.19 OCNG FDD pattern 19: full bandwidth allocation in 5 MHz (without MBSFN)
Table A.3.2.1.19-1: OP.19 FDD: OCNG FDD Pattern 19
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 4, 9 1 – 3, 6 – 8
0 – 24 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the
subframes not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of
virtual UEs with one PDSCH per virtual UE; the data transmitted over the
OCNG PDSCHs shall be uncorrelated pseudo random data, which is
QPSK modulated. The parameter γ PRB is used to scale the power of
PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the
PDSCH part of OCNG shall be transmitted to the virtual users by all the
transmit antennas with CRS and according to the antenna transmission
mode 2. The parameter γ PRB applies to each antenna port separately, so
the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission
modes are specified in section 7.1 in 3GPP TS 36.213.
N/A: Not Applicable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 544 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.20 OCNG FDD pattern 20: outer resource blocks allocation in 5 MHz with user
data in every subframe (without MBSFN)
Table A.3.2.1.20-1: OP.20 FDD: OCNG FDD Pattern 20
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 4, 9 1 - 3, 6 - 8
0-6 0 0 0 0
Note 2
18 - 24 0 0 0 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes
not configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual
UEs with one PDSCH per virtual UE; the data transmitted over the OCNG
PDSCHs shall be uncorrelated pseudo random data, which is QPSK modulated.
γ
The parameter PRB is used to scale the power of PDSCH.
Note 3: If two or more transmit antennas with CRS are used in the test, the PDSCH part
of OCNG shall be transmitted to the virtual users by all the transmit antennas
with CRS and according to the antenna transmission mode 2. The parameter
γ PRB applies to each antenna port separately, so the transmit power of the
PDSCH part of OCNG is equal between all the transmit antennas with CRS used
in the test. The antenna transmission modes are specified in section 7.1 in 3GPP
TS 36.213.
N/A: Not Applicable.
A.3.2.1.21 OCNG FDD pattern 21: Generic resource blocks allocation (without MBSFN)
Table A.3.2.1.21-1: OP.21 FDD: OCNG FDD Pattern 21
OCNG Bandwidth Allocation Relative power level γ PRB [dB] PDSCH
Pattern (MHz) n PRB Data
Name
Subframe
0 5 4, 9 1 – 3, 6 – 8
OP.21 FDD 10 0– 49Note 1,2
0 0 0 0 Note 3
Note 1: The OCNG pattern is used only for a serving cell of the UE under test.
Note 2: The OCNG allocation applied to all downlink physical resource bloacks (PRBs) except the REs that
are allocated for the PDSCH for the UE under test.
Note 3: OCNG PRBs are assigned to an arbitrary number of virtual UEs with one PDSCH per virtual UE; the
data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which is QPSK
modulated. The parameter γ PRB is used to scale the power of PDSCH.
Note 4: If two or more transmit antennas with CRS are used in the test, the PDSCH part of OCNG shall be
transmitted to the virtual users by all the transmit antennas with CRS and according to the antenna
transmission mode 2. The parameter γ PRB applies to each antenna port separately, so the transmit
power of the PDSCH part of OCNG is equal between all the transmit antennas with CRS used in the
test. The antenna transmission modes are specified in clause 7.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 545 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.1.22 OCNG FDD pattern 22: Generic resource blocks allocation in 5MHz (without
MBSFN)
Table A.3.2.1.22-1: OP.22 FDD: OCNG FDD Pattern 22
OCNG Bandwidth Allocation Relative power level γ PRB [dB] PDSCH
Pattern (MHz) n PRB Data
Name
Subframe
0 5 4, 9 1 – 3, 6 – 8
OP.22 FDD 5 0– 24Note 1,2
0 0 0 0 Note 3
Note 1: The OCNG pattern is used only for a serving cell of the UE under test.
Note 2: The OCNG allocation applied to all downlink physical resource bloacks (PRBs) except the REs that
are allocated for the PDSCH for the UE under test.
Note 3: OCNG PRBs are assigned to an arbitrary number of virtual UEs with one PDSCH per virtual UE; the
data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which is QPSK
modulated. The parameter γ PRB is used to scale the power of PDSCH.
Note 4: If two or more transmit antennas with CRS are used in the test, the PDSCH part of OCNG shall be
transmitted to the virtual users by all the transmit antennas with CRS and according to the antenna
transmission mode 2. The parameter γ PRB applies to each antenna port separately, so the transmit
power of the PDSCH part of OCNG is equal between all the transmit antennas with CRS used in the
test. The antenna transmission modes are specified in clause 7.1 in TS 36.213.
A.3.2.2 OCNG Patterns for TDD
The following OCNG patterns are used for modelling allocations to virtual UEs (which are not under test). The OCNG
pattern for each sub frame specifies the allocations that shall be filled with OCNG, and furthermore, the relative power
level of each such allocation.
In each test case the OCNG is expressed by parameters OCNG_RA and OCNG_RB which together with a relative
power level ( γ ) specifies the PDSCH EPRE-to-RS EPRE ratios in OFDM symbols without and with reference symbols,
respectively. The relative power, which is used for modelling boosting per virtual UE allocation, is expressed by:
γ i = PDSCH i _ RA / OCNG _ RA = PDSCH i _ RB / OCNG _ RB,
where γi denotes the relative power level of the i:th virtual UE. The parameter settings of OCNG_RA, OCNG_RB,
and the set of relative power levels γ are chosen such that when also taking allocations to the UE under test into
account, as given by a PDSCH reference channel, a transmitted power spectral density that is constant on an OFDM
symbol basis is targeted.
Moreover the OCNG pattern is accompanied by a PCFICH/PDCCH/PHICH reference channel which specifies the
control region. The number of PDCCH OFDM symbols in the non-MBSFN subframes is the same as specified in the
RMC used in the test. The number of PDCCH OFDM symbols in the MBSFN subframe is the maximal allowed
according to TS 36.213 [16]. For any aggregation and PHICH allocation, the PDCCH and any unused PHICH groups
are padded with resource element groups with a power level given by PDCCH_RA/RB and PHICH_RA/RB as
specified in the test case such that a total power spectral density in the control region that is constant on an OFDM
symbol basis is targeted.
For subframes configured as PRS subframes the PDSCH allocation defined in the OCNG pattern does not apply.
For subframes configured as ABS subframes the PDSCH and PMCH allocation defined in the OCNG pattern does not
apply.
The system information is scheduled in the allocations reserved for the OCNG patterns, in the subframes not configured
for MBSFN. For this purpose the number of the RB-s allocated with PDSCH defined in the OCNG pattern can be
reduced as necessary.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 546 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.2.1 OCNG TDD pattern 1: outer resource blocks allocation in 10 MHz
Table A.3.2.2.1-1: OP.1 TDD: OCNG TDD Pattern 1 for 5ms downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 1 and 6 (as
(as normal special
subframe) Note 3 subframe)
Note 3
0 – 12
0 0 0
Table
Note 2
37 – 49 A.3.2.2.1-2
0 0 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not configured as PRS
subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per
virtual UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which
is QPSK modulated The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration defined in Table
4.2-2 in TS 36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the
virtual users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in clause 7.1
in TS 36.213.
Table A.3.2.2.1-2: OP.1 TDD: OCNG TDD Pattern 1 for special subframe configuration with 5ms
downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB]
n PRB Special subframe configuration
0 1 2 3 4 5 6 7 8
Control region OFDM symbols
1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2
0 0
0 – 12 0 0 0 0 0 0 0
0 0
37 – 49 0 0 0 0 0 0 0
Note 1: Special subframe configurations are defined in Table 4.2-1 in TS 36.211 [16].
A.3.2.2.2 OCNG TDD pattern 2: full bandwidth allocation in 10 MHz
Table A.3.2.2.2-1: OP.2 TDD: OCNG TDD Pattern 2 for 5ms downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 (as 1 and 6 (as
normal special
subframe)Note 3 subframe)
Note 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 547 ETSI TS 136 133 V14.3.0 (2017-04)
0 – 49 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not configured as PRS
subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per virtual
UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which is QPSK
modulated. The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration in Table 4.2-2 in TS
36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the virtual
users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in clause 7.1 in
TS 36.213.
A.3.2.2.3 OCNG TDD pattern 3: outer resource blocks allocation in 1.4 MHz
Table A.3.2.2.3-1: OP.3 TDD: OCNG TDD Pattern 3 for 5 ms downlink-to-uplink switch-point
periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 1 and 6 (as
(as normal special
subframe) Note 3 subframe)
Note 3
0–1 0 0 0 0
0 Note 2
4–5 0 0 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not configured as PRS
subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per
virtual UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which
is QPSK modulated.The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration defined in Table
4.2-2 in TS 36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the
virtual users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in clause 7.1
in TS 36.213.
A.3.2.2.4 OCNG TDD pattern 4: full bandwidth allocation in 1.4 MHz
Table A.3.2.2.4-1: OP.4 TDD: OCNG TDD Pattern 4 for 5 ms downlink-to-uplink switch-point
periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 (as 1 and 6 (as
normal subframe) special
Note 3
subframe)
Note 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 548 ETSI TS 136 133 V14.3.0 (2017-04)
0–5 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not configured as PRS
subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per virtual
UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which is QPSK
modulated.The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration in Table 4.2-2 in TS
36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the virtual
users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in clause 7.1 in
TS 36.213.
A.3.2.2.5 OCNG TDD pattern 5: outer resource blocks allocation in 10 MHz for MBSFN
ABS
Table A.3.2.2.5-1: OP.5 TDD: OCNG TDD Pattern 5 for 5ms downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 1 and 6 (as
(as normal special
subframe) Note 3 subframe)
Note 3
0 – 12
0 0 0
Table
Note 2
37 – 49 A.3.2.2.1-2
0 0 0
Note 1: PDSCH allocation does not apply to subframes configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per
virtual UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which
is QPSK modulated The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration defined in Table
4.2-2 in TS 36.211 [16]. Any of the subframes 3, 4, 8 and 9 configured as MBSFN ABS in a test shall not
contain any PMCH data and shall contain CRS only in the first symbol of the first time slot. The
subframe(s) configured as MBSFN ABS depend upon the MBSFN ABS pattern used in the test.
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the
virtual users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in clause 7.1
in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 549 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.2.2.5-2: OP.5 TDD: OCNG TDD Pattern 5 for special subframe configuration with 5ms
downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB]
n PRB Special subframe configuration
0 1 2 3 4 5 6 7 8
Control region OFDM symbols
1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2
0 0
0 – 12 0 0 0 0 0 0 0
0 0
37 – 49 0 0 0 0 0 0 0
Note 1: Special subframe configurations are defined in Table 4.2-1 in TS 36.211 [16].
A.3.2.2.6 OCNG TDD pattern 6: full bandwidth allocation in 10 MHz for MBSFN ABS
Table A.3.2.2.6-1: OP.6 TDD: OCNG TDD Pattern 6 for 5ms downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 (as 1 and 6 (as
normal special
subframe)Note 3 subframe)
Note 3
0 – 49 0 0 0 0 Note 2
Note 1: PDSCH allocation does not apply to subframes configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per virtual
UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which is QPSK
modulated. The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration in Table 4.2-2 in TS
36.211 [16]. Any of the subframes 3, 4, 8 and 9 configured as MBSFN ABS in a test shall not contain any
PMCH data and shall contain CRS only in the first symbol of the first time slot. The subframe(s) configured as
MBSFN ABS depend upon the MBSFN ABS pattern used in the test.
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the virtual
users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in clause 7.1 in
TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 550 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.2.7 OCNG TDD pattern 7: outer resource blocks allocation in 20 MHz
Table A.3.2.2.7-1: OP.7 TDD: OCNG TDD Pattern 7 for 5ms downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 1 and 6 (as
(as normal special
subframe) Note 3 subframe)
Note 3
0 – 37 0 0 0
Table
Note 2
A.3.2.1.7-2
62 – 99 0 0 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not configured as PRS
subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per
virtual UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which
is QPSK modulated The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration defined in Table
4.2-2 in 3GPP TS 36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the
virtual users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in section 7.1
in 3GPP TS 36.213.
Table A.3.2.2.7-2: OP.7 TDD: OCNG TDD Pattern 7 for special subframe configuration with 5ms
downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB]
CP length
n PRB Special subframe configuration
0 1 2 3 4 5 6 7 8
Control region OFDM symbols
1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2
N 0 0
0 – 37 0 0 0 0 0 0 0
N 0 0
62 – 99 0 0 0 0 0 0 0
Note 1: Special subframe configurations are defined in Table 4.2-1 in TS 36.211 [16].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 551 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.2.8 OCNG TDD pattern 8: full bandwidth allocation in 20 MHz
Table A.3.2.2.8-1: OP.8 TDD: OCNG TDD Pattern 8 for 5ms downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB] PDSCH Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 (as 1 and 6 (as
normal special
subframe)Note 3 subframe)
Note 3
0 – 99 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not configured as PRS
subframes
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one PDSCH per virtual
UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which is QPSK
modulated. The parameter γ PRB is used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration in Table 4.2-2 in 3GPP
TS 36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted to the virtual
users by all the transmit antennas with CRS and according to the antenna transmission mode 2. The
parameter γ PRB applies to each antenna port separately, so the transmit power is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified in section 7.1 in
3GPP TS 36.213.
A.3.2.2.9 OCNG TDD pattern 9: outer resource blocks allocation in 5 MHz
Table A.3.2.2.9-1: OP.9 TDD: OCNG TDD Pattern 9 for 5ms downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB] PDSCH
n PRB Data
Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 1 and 6 (as
(as normal special
subframe) Note 3 subframe) Note 3
0–6 0 0 0
Table A.3.2.1.7-
Note 2
2
18 – 24 0 0 0
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not
configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with
one PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall be
uncorrelated pseudo random data, which is QPSK modulated The parameter γ PRB is
used to scale the power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration
defined in Table 4.2-2 in 3GPP TS 36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be
transmitted to the virtual users by all the transmit antennas with CRS and according to
the antenna transmission mode 2. The parameter γ PRB applies to each antenna port
separately, so the transmit power is equal between all the transmit antennas with CRS
used in the test. The antenna transmission modes are specified in section 7.1 in 3GPP
TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 552 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.2.2.9-2: OP.9 TDD: OCNG TDD Pattern 9 for special subframe configuration with 5ms
downlink-to-uplink switch-point periodicity
Allocation Relative power level γ PRB [dB]
CP length
n PRB Special subframe configuration
0 1 2 3 4 5 6 7 8
Control region OFDM symbols
1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2
N 0 0
0–6 0 0 0 0 0 0 0
N 0 0
18 – 24 0 0 0 0 0 0 0
Note 1: Special subframe configurations are defined in Table 4.2-1 in TS 36.211 [16].
A.3.2.2.10 OCNG TDD pattern 10: full bandwidth allocation in 5 MHz
Table A.3.2.2.10-1: OP.10 TDD: OCNG TDD Pattern 10 for 5ms downlink-to-uplink switch-point
periodicity
Allocation Relative power level γ PRB [dB] PDSCH
Data
n PRB Subframe (Note 1)
0 5 3 , 4, 8, 9 and 6 (as 1 and 6 (as
normal special subframe)
subframe)Note 3 Note 3
0 – 24 0 0 0 0 Note 2
Note 1: The allocation of any PDSCH with or without SIB1 applies only to the subframes not
configured as PRS subframes.
Note 2: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one
PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated
pseudo random data, which is QPSK modulated. The parameter γ PRB is used to scale the
power of PDSCH.
Note 3: Subframes available for DL transmission depends on the Uplink-Downlink configuration in
Table 4.2-2 in 3GPP TS 36.211 [16].
Note 4: If two or more transmit antennas with CRS are used in the test, the OCNG shall be transmitted
to the virtual users by all the transmit antennas with CRS and according to the antenna
transmission mode 2. The parameter γ PRB applies to each antenna port separately, so the
transmit power is equal between all the transmit antennas with CRS used in the test. The
antenna transmission modes are specified in section 7.1 in 3GPP TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 553 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.2.11 OCNG TDD pattern 11: Generic resource blocks allocation (without MBSFN)
Table A.3.2.2.11-1: OP.11 TDD: OCNG TDD Pattern 11
OCNG Bandwidth Allocation Relative power level γ PRB [dB] PDSCH
Pattern (MHz) n PRB Data
Name
Subframe
0 5 3 , 4, 8, 9 1 and 6 (as
and 6 (as special subframe)
Note 5
normal
subframe)
Note 5
OP.11 TDD 10 0 – 49Note 1,2 0 0 0 0 Note 3
Note 1: The OCNG pattern is used only for a serving cell of the UE under test.
Note 2: The OCNG allocation applied to all downlink physical resource bloacks (PRBs) except the REs that
are allocated for the PDSCH for the UE under test.
Note 3: OCNG PRBs are assigned to an arbitrary number of virtual UEs with one PDSCH per virtual UE; the
data transmitted over the OCNG PDSCHs shall be uncorrelated pseudo random data, which is QPSK
modulated. The parameter γ PRB is used to scale the power of PDSCH.
Note 4: If two or more transmit antennas with CRS are used in the test, the PDSCH part of OCNG shall be
transmitted to the virtual users by all the transmit antennas with CRS and according to the antenna
transmission mode 2. The parameter γ PRB applies to each antenna port separately, so the transmit
power of the PDSCH part of OCNG is equal between all the transmit antennas with CRS used in the
test. The antenna transmission modes are specified in clause 7.1 in TS 36.213.
Note 5: Subframes available for DL transmission depends on the Uplink-Downlink configuration in Table 4.2-
2 in TS 36.211 [16].
A.3.2.3 OCNG Patterns for Narrowband IoT
The following Narrowband OCNG patterns (NOCNG) are used for modelling allocations to UEs not under test in a
Narrowband IoT cell. Depending on scenario, allocations may be for UEs of category NB1only, or for UEs of category
NB1 as well as of other categories. The former is applicable to guard-band and stand-alone deployments of Narrowband
IoT, whereas the latter is applicable to in-band deployment. In order to allow different power levels for the LTE cell and
the Narrowband IoT cell, a distinction is made between OCNG and NOCNG where the latter is used for category NB1
UEs and the former is used for other UE categories.
OCNG in the LTE cell is expressed by parameters OCNG_RA and OCNG_RB which together with a relative power
level ( γ ) specifies the PDSCH-to-RS EPRE ratio in OFDM symbols with and without LTE cell-specific reference
symbols, respectively. The relative power, which is used for modelling boosting per virtual LTE UE allocation, is
expressed by:
γ i = PDSCHi _ RA / OCNG _ RA = PDSCHi _ RB / OCNG _ RB,
where γi denotes the relative power level of the i:th virtual LTE UE.
Moreover in each test case NOCNG is expressed by parameters NOCNG_RA and NOCNG_RB which together with a
relative power level ( γ ) specifies the <channel>-to-RS EPRE ratio in OFDM symbols with and without Narrowband
reference symbols (NB-RS), respectively. The relative power, which is used for modelling boosting per virtual UE
category NB1 allocation, is expressed by:
γk =< channel>k _ RA/ NOCNG_ RA=< channel>k _ RB/ NOCNG_ RB,
where γk denotes the relative power level of the k:th virtual NB-IoT UE, and channel may be either of NPDCCH and
NPDSCH.
The parameter settings of OCNG_RA, OCNG_RB, NOCNG_RA, NOCNG_RB and the set of relative power levels
γ are chosen such that when also taking allocations to the UE category NB1 under test into account, as given by a
NPDCCH and NPDSCH reference channels, a transmitted power spectral density that is constant on an OFDM symbol
basis is targeted.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 554 ETSI TS 136 133 V14.3.0 (2017-04)
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 555 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.2.3.1 Narrowband IoT OCNG FDD pattern 1: In-band NB-IoT in 10 MHz EUTRAN
cell
Table A.3.2.3.1-1: NOP.1 FDD: OCNG FDD Pattern 1
Allocation Relative power level γ PRB [dB] PDSCH NPDCCH
n PRB Data and
Subframe NPDSCH
0, 4 5, 9 1-3, 6-8 Data
0 – 29, 35 – 49 0 0 0 Note 1 N/A
30 – 34 0 (Note 3) 0 (Note 3) N/A N/A Note 2
30 – 34 N/A N/A 0 Note 1 N/A
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one
PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated
QPSK modulated pseudo random data. The parameter γ PRB is used to scale the power of
PDSCH.
If two or more transmit antennas with CRS are used in the test, the PDSCH part of OCNG
shall be transmitted to the virtual users by all the transmit antennas with CRS and according
to the antenna transmission mode 2. The parameter γ PRB applies to each antenna port
separately, so the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified
in clause 7.1 in TS 36.213.
Note 2: This physical resource block is assigned to a virtual UE for transmission of NPDCCH or
NPDSCH; the data transmitted over the NOCNG NPDCCH or NPDSCH shall be
uncorrelated QPSK modulated pseudo random data. The parameter γ PRB is used to scale
the power of NPDCCH and NPDSCH.
If two transmit antennas with NBRS are used in the test, the NPDCCH and NPDSCH parts of
NOCNG shall be transmitted to the virtual users by both transmit antennas with NBRS and
according to the antenna transmission mode 2. The parameter γ PRB applies to each antenna
port separately, so the transmit power of the NPDCCH and NPDSCH parts of NOCNG is
equal between both the transmit antennas with NBRS used in the test. The antenna
transmission modes are specified in clause 7.1 in TS 36.213.
Note 3: Value of γ PRB is applicable to PRBs not used for transmission of NPSS, NSSS, and NPBCH
in anchor cell ( n PRB = 30).
Note 4: SI transmissions, and NPDCCH and NPDSCH for the UE under test, have precedence over
OCNG and NOCNG.
N/A: Not Applicable
A.3.2.3.2 Narrowband IoT OCNG FDD pattern 2: guard band NB-IoT in 10 MHz
EUTRAN cell
Table A.3.2.3.1-1: NOP.2 FDD: OCNG FDD Pattern 2
Allocation Relative power level γ PRB [dB] PDSCH NPDCCH
n PRB Data and
Subframe NPDSCH
0, 4 5, 9 1-3, 6-8 Data
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 556 ETSI TS 136 133 V14.3.0 (2017-04)
0-49 0 0 0 Note 1 N/A
50-52 0 0 (Note 3) 0 N/A Note 2
Note 1: These physical resource blocks are assigned to an arbitrary number of virtual UEs with one
PDSCH per virtual UE; the data transmitted over the OCNG PDSCHs shall be uncorrelated
QPSK modulated pseudo random data. The parameter γ PRB is used to scale the power of
PDSCH.
If two or more transmit antennas with CRS are used in the test, the PDSCH part of OCNG
shall be transmitted to the virtual users by all the transmit antennas with CRS and according
to the antenna transmission mode 2. The parameter γ PRB applies to each antenna port
separately, so the transmit power of the PDSCH part of OCNG is equal between all the
transmit antennas with CRS used in the test. The antenna transmission modes are specified
in clause 7.1 in TS 36.213.
Note 2: This physical resource block is assigned to a virtual UE for transmission of NPDCCH or
NPDSCH; the data transmitted over the NOCNG NPDCCH or NPDSCH shall be
uncorrelated QPSK modulated pseudo random data. The parameter γ PRB is used to scale
the power of NPDCCH and NPDSCH.
If two transmit antennas with NBRS are used in the test, the NPDCCH and NPDSCH parts of
NOCNG shall be transmitted to the virtual users by both transmit antennas with NBRS and
according to the antenna transmission mode 2. The parameter γ PRB applies to each antenna
port separately, so the transmit power of the NPDCCH and NPDSCH parts of NOCNG is
equal between both the transmit antennas with NBRS used in the test. The antenna
transmission modes are specified in clause 7.1 in TS 36.213.
Note 3: Value of γ PRB is applicable to PRBs not used for transmission of NPSS, NSSS and PBCH in
anchor cell ( n PRB = 50).
Note 4: SI transmissions, and NPDCCH and NPDSCH for the UE under test, have precedence over
OCNG and NOCNG.
N/A: Not Applicable
A.3.2.3.3 Narrowband IoT OCNG FDD pattern 3: standalone NB-IoT
Table A.3.2.3.3-1: NOP.3 FDD: OCNG FDD Pattern 3
Allocation Relative power level γ PRB [dB] NPDCCH
n PRB and
Subframe NPDSCH
0, 4 5, 9 1-3, 6-8 Data
0–5 0 (Note 1) 0 (Note 1) 0 Note 2
Note 1: This physical resource block is assigned to a virtual UE for transmission of
NPDCCH or NPDSCH; the data transmitted over the NOCNG NPDCCH or
NPDSCH shall be uncorrelated QPSK modulated pseudo random data. The
parameter γ PRB is used to scale the power of NPDCCH and NPDSCH.
If two transmit antennas with NBRS are used in the test, the NPDCCH and
NPDSCH parts of NOCNG shall be transmitted to the virtual users by both
transmit antennas with NBRS and according to the antenna transmission
mode 2. The parameter γ PRB applies to each antenna port separately, so the
transmit power of the NPDCCH and NPDSCH parts of NOCNG is equal
between both the transmit antennas with NBRS used in the test. The antenna
transmission modes are specified in clause 7.1 in TS 36.213.
Note 2: Value of γ PRB is applicable to PRBs not used for transmission of NPSS, NSSS
and PBCH in anchor cell ( n PRB = 0).
Note 3: SI transmissions, and NPDCCH and NPDSCH for the UE under test, have
precedence over NOCNG.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 557 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.3 Reference DRX Configurations
Table A.3.3-1: Reference DRX Configurations
Parameter Value Comments
Reference configuration DRX_S DRX_L As defined in 4.8.2.1.5 in TS 36.508
onDurationTimer psf2 psf6
drx-InactivityTimer psf100 psf1920
drx-RetransmissionTimer psf16 psf16
longDRX-CycleStartOffset sf40, 0 sf1280, 0
shortDRX disabled disabled
Note: For further information see clause 6.3.2 in TS 36.331.
A.3.4 ABS Transmission Configurations
A.3.4.1 Non-MBSFN ABS Transmission Configurations
A.3.4.1.1 Non-MBSFN ABS Transmission, 1x2 antenna with PBCH
Table A.3.4.1.1-1: Transmission configuration with non-MBSFN ABS, 1x2 with PBCH
Physical Parameters EPRE, [dB]
Channels and Non-ABS ABS
Signals
PBCH_RA 0 0
PBCH
PBCH_RB 0 0
PSS PSS_RA 0 0
SSS SSS_RA 0 0
PCFICH PCFICH_RB 0 0 Note 1
PHICH_RA 0 -Inf
PHICH
PHICH_RB 0 -Inf
PDCCH_RA 0 0 Note 1
PDCCH
PDCCH_RB 0 0 Note 1
PDSCH_RA 0 0 Note 1
PDSCH
PDSCH_RB 0 0 Note 1
OCNG_RA 0 -Inf
OCNG
OCNG_RB 0 -Inf
NOTE 1: Only used for SIB1, otherwise EPRE is –Inf
NOTE 2: 1x2 antenna configuration is assumed
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 558 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.4.1.2 Non-MBSFN ABS Transmission, 2x2 antenna without PBCH
Table A.3.4.1.2-1: Transmission configuration #1 with non-MBSFN ABS, 2x2 without PBCH
Physical EPRE, [dB]
Channels and Parameters
Non-ABS ABS
Signals
PBCH_RA -3 -Inf
PBCH
PBCH_RB -3 -Inf
PSS PSS_RA -3 -3
SSS SSS_RA -3 -3
PCFICH PCFICH_RB 1 -Inf
PHICH_RA -3 -Inf
PHICH
PHICH_RB -3 -Inf
PDCCH_RA 1 -Inf
PDCCH
PDCCH_RB 1 -Inf
PDSCH_RA -3 -Inf
PDSCH
PDSCH_RB -3 -Inf
OCNG_RA -3 -Inf
OCNG
OCNG_RB -3 -Inf
NOTE: 2x2 antenna configuration is assumed
Table A.3.4.1.2-2: Transmission configuration #2 with non-MBSFN ABS, 2x2 without PBCH
Physical EPRE, [dB]
Channels and Parameters
Non-ABS ABS
Signals
PBCH_RA -3 -Inf
PBCH
PBCH_RB -3 -Inf
PSS PSS_RA -3 -3
SSS SSS_RA -3 -3
PCFICH PCFICH_RB 1 -Inf
PHICH_RA -3 -Inf
PHICH
PHICH_RB -3 -Inf
PDCCH_RA -3 -Inf
PDCCH
PDCCH_RB -3 -Inf
PDSCH_RA -3 -Inf
PDSCH
PDSCH_RB -3 -Inf
OCNG_RA -3 -Inf
OCNG
OCNG_RB -3 -Inf
NOTE: 2x2 antenna configuration is assumed
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 559 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.4.2 MBSFN ABS Transmission Configurations
A.3.4.2.1 MBSFN ABS Transmission, 1x2 antenna
Table A.3.4.2.1-1: Transmission configuration with MBSFN ABS, 1x2
Physical EPRE, [dB]
Channels and Parameters
Non-ABS ABS
Signals
PBCH_RA 0 N/A
PBCH
PBCH_RB 0 N/A
PSS PSS_RA 0 N/A
SSS SSS_RA 0 N/A
PCFICH PCFICH_RB 0 -Inf
PHICH_RA 0 -Inf
PHICH
PHICH_RB 0 -Inf
PDCCH_RA 0 -Inf
PDCCH
PDCCH_RB 0 -Inf
PDSCH_RA 0 -Inf
PDSCH
PDSCH_RB 0 -Inf
PMCH_RA 0 -Inf
PMCH
PMCH_RB 0 -Inf
OCNG_RA 0 -Inf
OCNG
OCNG_RB 0 -Inf
NOTE: 1x2 antenna configuration is assumed
A.3.4.2.2 MBSFN ABS Transmission, 2x2 antenna
Table A.3.4.2.2-1: Transmission configuration #1 with MBSFN ABS, 2x2
Physical EPRE, [dB]
Channels and Parameters
Non-ABS ABS
Signals
PBCH_RA -3 N/A
PBCH
PBCH_RB -3 N/A
PSS PSS_RA -3 N/A
SSS SSS_RA -3 N/A
PCFICH PCFICH_RB 1 -Inf
PHICH_RA -3 -Inf
PHICH
PHICH_RB -3 -Inf
PDCCH_RA 1 -Inf
PDCCH
PDCCH_RB 1 -Inf
PDSCH_RA -3 -Inf
PDSCH
PDSCH_RB -3 -Inf
PMCH_RA -3 -Inf
PMCH
PMCH_RB -3 -Inf
OCNG_RA -3 -Inf
OCNG
OCNG_RB -3 -Inf
NOTE: 2x2 antenna configuration is assumed
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 560 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.4.2.2-2: Transmission configuration # 2 with MBSFN ABS, 2x2
Physical EPRE, [dB]
Channels and Parameters
Non-ABS ABS
Signals
PBCH_RA -3 N/A
PBCH
PBCH_RB -3 N/A
PSS PSS_RA -3 N/A
SSS SSS_RA -3 N/A
PCFICH PCFICH_RB 1 -Inf
PHICH_RA -3 -Inf
PHICH
PHICH_RB -3 -Inf
PDCCH_RA -3 -Inf
PDCCH
PDCCH_RB -3 -Inf
PDSCH_RA -3 -Inf
PDSCH
PDSCH_RB -3 -Inf
PMCH_RA -3 -Inf
PMCH
PMCH_RB -3 -Inf
OCNG_RA -3 -Inf
OCNG
OCNG_RB -3 -Inf
NOTE: 2x2 antenna configuration is assumed
A.3.5 Impact of Reference Sensitivity Degradation with Carrier
Aggregation on Test Cases
A.3.5.1 Impact of Reference Sensitivity Degradation due to Insertion Loss
For a UE supporting inter-band carrier aggregation configuration with uplink in one E-UTRA band, if there is a
relaxation of receiver sensitivity ΔRIB,c>0 dB as defined in TS 36.101 [5], 7.3.1-1A, there is no adjustment of test
parameters in the tests specified in TS 36.133 when ΔRIB,c ≤ 1 dB.
A.3.6 Carrier Aggregation Test Cases with Different Channel
Bandwidth Combinations
A.3.6.1 Introduction
In Annex A carrier aggregation test cases may be defined with different channel bandwidth combinations to verify the
same RRM requirement.
If multiple carrier aggregation test cases with different channel bandwidth combinations are defined to verify the same
RRM requirement that is channel bandwidth independent, then the UE needs to be tested only with one bandwidth
combination out of the bandwidth combination sets supported by that UE.
A.3.7 Test Cases with Different Channel Bandwidths
A.3.7.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for single carrier
operation.
A.3.7.2 Principle of testing
Test cases defined for 5MHz channel bandwidth that reference this clause are applicable to UEs that support only Band
31.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 561 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.8 Antenna Configuration
Unless otherwise specified, E-UTRA FDD or E-UTRA TDD cells in all RRM Test cases in AWGN propagation
condition are configured with Antenna Configuration 1x2.
A.3.8.1 Antenna connection for 4 Rx capable UEs
A.3.8.1.1 Introduction
All tests in sections A.4 to A.9 are specified for UEs supporting either category 0 (1RX) or 2RX. In this section, the
antenna connection method for applying 2RX tests to UEs supporting 4RX antenna ports is specified. No tests are
currently specified in section A.4-A.9 which are applicable only to 4RX antenna ports, so 4RX capable UEs are always
tested by reusing tests which were originally specified for 2RX UEs.
A.3.8.1.2 Principle of testing
A.3.8.1.2.1 Single carrier tests
For 4RX capable UEs supporting at least one 2RX band, the, all single carrier tests specified in section A.4 to A.8 shall
be tested on any band where 2RX is supported with the antenna connection specified in A.8.3.1.2.3. For single carrier
tests specified in section A.9, all tests shall be tested with the antenna connction specified in A.3.8.1.2.3 for bands
where 2RX is supported, and the antenna connction specified in A.3.8.1.2.4 for bands where 4RX is supported.
For 4RX capable UEs which do not support any 2RX band, all tests specified in sections A.4 to A.9 shall be tested
using the antenna connection specified in section A.3.8.1.2.4. For radio link monitoring tests, the SNR levels are
modified according to table A.3.8.1.2.1-1 and table A.3.8.1.2.1-2.
Table A.3.8.1.2.1-1 Modified parameters for RLM out of sync testing with 4 RX antenna connection
Test case SNR during T3 (dB)
Test 1 Test 2 Test 3 Test 4
A.7.3.1 -17 -17 -15 -15.7
A.7.3.3 -16.6 -16.7 -14.8 -15.4
A.7.3.5 -15.7 -17 N/A N/A
A.7.3.7 -15.4 -16.6 N/A N/A
A.7.3.9 (cell 1) Note 1 N/A N/A N/A
A.7.3.10 (cell 1) Note 1 N/A N/A N/A
A.7.3.13 (cell 1) Note 1 N/A N/A N/A
A.7.3.14 (cell 1) Note 1 N/A N/A N/A
A.7.3.17 (cell 1) Note 1 N/A N/A N/A
A.7.3.18 (cell 1) Note 1 N/A N/A N/A
A.7.3.23 -15.7 N/A N/A N/A
Note 1: For 4Rx capable UEs without any 2Rx supported RF bands,this test can be skipped.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 562 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.8.1.2.1-1 Modified parameters for RLM out of sync single carrier testing with 4 RX antenna
connection
Test case SNR during T3 (dB) SNR during T4 (dB)
Test 1 Test 2 Test 1 Test 2
A.7.3.2 -14 -15.7 -9.9 -10.8
A.7.3.4 -14.8 -15.4 -9.9 -10.8
A.7.3.6 -17 N/A -12.2 N/A
A.7.3.8 -16.6 N/A -12.6 N/A
A.7.3.11 (cell 1) Note 1 N/A Note 1 N/A
A.7.3.12 (cell 1) Note 1 N/A Note 1 N/A
A.7.3.15 (cell 1) Note 1 N/A Note 1 N/A
A.7.3.16 (cell 1) Note 1 N/A Note 1 N/A
A.7.3.19 (cell 1) Note 1 N/A Note 1 N/A
A.7.3.20 (cell 1) Note 1 N/A Note 1 N/A
A.7.3.21(cell 1) Note 1 N/A Note 1 N/A
A.7.3.22 (cell 1) Note 1 N/A Note 1 N/A
A.7.3.24 -15.7 N/A -10.8 N/A
A.7.3.25 -15.7 N/A -10.8 N/A
Note 1: For 4Rx capable UEs without any 2Rx supported RF bands,this test can be skipped.
A.3.8.1.2.2 Carrier aggregation and Dual connectivity tests
All carrier aggregation and dual connectivity tests are performed using the antenna connection in section A.3.8.1.2.3 for
the PCell antenna connection if the PCell is on a band where 2RX is supported or the antenna connection in A.3.8.1.2.4
for the PCell antenna connection if the PCell is on a band where 4RX is supported.
All carrier aggregation and dual connectivity tests are performed using the antenna connection in section A.3.8.1.2.3 for
the SCell or PSCell antenna connection if an SCell or PSCell is on band where 2RX is supported or the testing
procedure in A.3.8.1.2.4 for the SCell or PSCell antenna connection if an SCell or PSCell is on a band where 4RX is
supported.
For dual connectivity radio link monitoring tests with the PSCell on a band where 4RX is supported, the PSCell SNR
levels are modified according to table A.3.8.1.2.2 -1 and table A.3.8.1.2.2 -2.
Tabke A.3.8.1.2.1-1 Modified parameters for dual connectivity RLM out of sync testing with 4 RX
antenna connection
Test case SNR during T3 (dB)
A.7.3.38 (cell 2) -15.7 (5MHz)
-15.7 (10MHz)
-16.3 (20 MHz)
A.7.3.39 (cell 2) -15.7 (5MHz)
-15.7 (10MHz)
-16.3 (20 MHz)
A.7.3.40 (cell 2) -15.4 (5MHz)
-15.4 (10MHz)
-16.1 (20MHz)
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 563 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.8.1.2.1-1 Modified parameters for RLM out of sync testing with 4 RX antenna connection
Test case SNR during T3 (dB) SNR during T4 (dB)
A.7.3.41 (cell 2) -15.7 (5 Mhz) -10.8 (5MHz)
-17.0 (10 Mhz) -12.2 (10MHz)
-17.0 (20 Mhz) -12.2 (20 MHz)
A.7.3.42 (cell 2) -15.7 (5 Mhz) -10.8 (5MHz)
-17.0 (10 Mhz) -12.2 (10MHz)
-17.0 (20 Mhz) -12.2 (20 MHz)
A.7.3.43 (cell 2) -16.6 (5MHz) -12.6 (5MHz)
-16.6 (10 MHz) -12.6 (10 MHz)
-16.6 (20 MHz) -12.6 (20 MHz)
A.3.8.1.2.3 Antenna connection for bands where 2RX is supported
For bands where 2RX is supported, it is left to the UE declaration and AP configuration to decide which 2 of the 4 Rx
ports are connected with data source from system simulator. The remaning 2 Rx ports shall be connected with zero
input. No test parameters or requirements are modified.
A.3.8.1.2.4 Antenna connection for bands where 4RX is supported
For bands where 4RX is supporetd, all 4 Rx are connected with data source from system simulator. The system
simulator shall provide independent noise and fading (low correlation) for each antenna port. Except for the
modifications to radio link monitoring theresholds described in sections A.3.8.1.2.1 and A.3.8.1.2.2, no test parameters
or requirements are modified.
A.3.9 Carrier Aggregation Test Cases with Different Duplex
Modes
A.3.9.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for carrier aggregation.
A.3.9.2 Principle of testing
In Annex A carrier aggregation test cases may be defined for different duplex modes or combination of duplex modes
(E-UTRA FDD, E-UTRA TDD and E-UTRA TDD-FDD) to verify the same RRM requirement.
If multiple carrier aggregation test cases are defined for different duplex modes (E-UTRA FDD or E-UTRA TDD) or
for combination of duplex modes (E-UTRA TDD-FDD) to verify the same RRM requirement which is independent of
the duplex mode and is identical for different duplex modes or combination of duplex modes, then from UE the
performance point of view the test coverage can be considered fulfilled by executing only the corresponding test case(s)
with one of the duplex modes supported by the UE.
A.3.10 Carrier Aggregation Test Cases with Different CA
Configurations
A.3.10.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for carrier aggregation.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 564 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.10.2 Principle of testing
In Annex A carrier aggregation test cases may be defined for two CCs as well as for more than two CCs to verify the
same RRM requirement.
If multiple carrier aggregation test cases are defined for two CCs as well as for more than two CCs to verify the same
RRM requirement, then from the UE performance point of view the test coverage can be considered fulfilled by
executing only the test cases with the maximum number of CCs supported by the UE.
Editor’s note: whether it is sufficient to test for any one of the band combinations supported by the UE is FFS.
A.3.11 Test Cases for Synchronous and Asynchronous Dual
Connectivity
A.3.11.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for dual connectivity (DC)
operation in synchronous and asynchronous scenarios.
A.3.11.2 Principle of Testing
In Annex A test cases may be defined in both synchronous DC and asynchronous DC scenarios to verify the same RRM
requirement.
If test cases are defined in both synchronous and asynchronous DC scenarios to verify the same RRM requirement then
the UE capable of both synchronous and asynchronous DC operations needs to be tested with one of the tests in either
synchronous or asynchronous DC scenarios.
A.3.12 Proximity-based Services
A.3.12.1 Introduction
This clause also defines the principle and the reference configurations that are applicable to test cases verifying RRM
core requirements for ProSe Direct Discovery and ProSe Direct Communication.
A.3.12.2 Reference DRX configurations for ProSe tests
Table A.3.12.2-1: Reference DRX Configurations
Parameter Value
Reference configuration DRX_P1
onDurationTimer psf1
drx-InactivityTimer psf1
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf320, 0
shortDRX Disabled
Note: For further information see clause 6.3.2 in TS 36.331.
A.3.12.3 Test Cases with Different Channel Bandwidths
A.3.12.3.1 Introduction
This clause defines a principle which is applicable to test cases verifying ProSe RRM requirements with different
channel bandwidths.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 565 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.12.3.2 Principle of testing
Some ProSe test cases are defined for different channel bandwidths to verify the same RRM requirement.
If test cases with different channel bandwidth are defined to verify the same RRM requirement then the UE is required
to pass the test cases only with one of the channel bandiwdths.
A.3.12.4 Reference resource pool configurations for ProSe Direct Discovery
Table A.3.12.4-1: ProSe Direct Discovery configuration for E-UTRA FDD (Configuration #1)
Information Element Value
discRxPool cp-Len Normal
discPeriod rf32
numRetx 0
numRepetition 1
tf-ResourceConfig prb-Num 12
prb-Start 0
prb-End 23
offsetIndicator 160
subframeBitmap 11000000
00000000
00000000
00000000
00000000
txParameters not present
rxParameters not present
discTxPoolCommon/ cp-Len Normal
discTxPoolDedicated
discPeriod rf32
numRetx 0
numRepetition 1
tf-ResourceConfig prb-Num 2
prb-Start 3
prb-End 5
offsetIndicator 160
subframeBitmap 10000000
00000000
00000000
00000000
00000000
txParameters txParametersGeneral alpha al0
p0 31
ue- poolSelection random
SelectedResourceConfig
txProbability p100
rxParameters not present
discTxPowerInfo discMaxTxPower 23
SL-SyncConfig syncCP-Len Normal
syncOffsetIndicator 35 (155
mod 40)
slssid 30
txParameters txParametersGeneral alpha al0
p0 31
syncTxThreshIC 0 (-infinity)
rxParamsNCell not present
discInterFreqList not present
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 566 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.12.4-2: ProSe Direct Discovery configuration for E-UTRA FDD (Configuration #2)
Information Element Value
discRxPool cp-Len Normal
discPeriod rf32
numRetx 0
numRepetition 1
tf-ResourceConfig prb-Num 12
prb-Start 0
prb-End 23
offsetIndicator 160
subframeBitmap 11000000
00000000
00000000
00000000
00000000
txParameters not present
rxParameters tdd-Config not present
syncConfigIndex 0
discTxPoolCommon/ not present
discTxPoolDedicated
discTxPowerInfo discMaxTxPower 23
SL-SyncConfig syncCP-Len Normal
syncOffsetIndicator 20 (140
mod 40)
slssid 30
txParameters not present
rxParamsNCell physCellId 1
discSyncWindow w1
discInterFreqLis not present
Table A.3.12.4-3: ProSe Direct Discovery configuration for E-UTRA TDD Config 0 (Configuration #3)
Information Element Value
discRxPool cp-Len Normal
discPeriod rf32
numRetx 0
numRepetition 1
tf-ResourceConfig prb-Num 12
prb-Start 0
prb-End 23
offsetIndicator 163
subframeBitmap 11000000
00000000
00000000
00000000
00000000
00
txParameters not present
rxParameters not present
discTxPoolCommon/ cp-Len Normal
discTxPoolDedicated
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 567 ETSI TS 136 133 V14.3.0 (2017-04)
discPeriod rf32
numRetx 0
numRepetition 1
tf-ResourceConfig prb-Num 2
prb-Start 3
prb-End 5
offsetIndicator 163
subframeBitmap 10000000
00000000
00000000
00000000
00000000
00
txParameters txParametersGeneral alpha al0
p0 31
ue- poolSelection random
SelectedResourceConfig
txProbability p100
rxParameters not present
discTxPowerInfo discMaxTxPower 23
SL-SyncConfig syncCP-Len Normal
syncOffsetIndicator 38 (158
mod 40)
slssid 30
txParameters txParametersGeneral alpha al0
p0 31
syncTxThreshIC 0 (-infinity)
rxParamsNCell not present
discInterFreqList not present
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 568 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.12.4-4: ProSe Direct Discovery configuration for E-UTRA FDD for PS discovery
(Configuration #4)
Information Element Value
discConfig not present
discInterFreqList not present
discConfig-v1310 not present
discConfigPS discRxPoolPS cp-Len Normal
discPeriod-v1310 rf4
numRetx 0
numRepetition 1
tf-ResourceConfig prb-Num 12
prb-Start 0
prb-End 23
offsetIndicator 20
subframeBitmap 11000000
00000000
00000000
00000000
00000000
txParameters not present
rxParameters tdd-Config not present
syncConfigIndex 0
discTxPoolPS- not present
Common/
discTxPoolPS-
Dedicated
discConfigRelay relayUE-Config threshHigh not present
threshLow not present
hystMax not present
hystMin not present
remoteUE-Config threshHigh 0
(-130dBm)
hystMax dB0
reselectionInfoIC q-RxLevMin (-94dBm)
filterCoefficient fc0
minHyst dB3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 569 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.12.4-5: ProSe Direct Discovery configuration for E-UTRA FDD for inter-frequency discovery
(Configuration #5)
Information Element Value
discConfig not present
discInterFreqList carrierFreq Note 1
plmn-IdentityList not present
discConfig-v1310
discInterFreqList-v1310
discResourcesNonPS discRxResourcesInterFreq cp-Len Normal
discPeriod rf32
numRetx 0
numRepetition 1
tf-ResourceConfig
prb-Num 12
prb-Start 0
prb-End 23
offsetIndicator 160
subframeBitmap 11000000
00000000
00000000
00000000
00000000
txParameters not present
rxParameters not present
rxParamsAddNeighFreq
physCellId Note 1
discTxResourcesInterFreq discTxPoolCommon
cp-Len Normal
discPeriod rf32
numRetx 0
numRepetition 1
tf-ResourceConfig
prb-Num 2
prb-Start 3
prb-End 5
offsetIndicator 160
subframeBitmap 10000000
00000000
00000000
00000000
00000000
txParameters
txParametersGeneral
alpha al0
p0 31
ue-SelectedResourceConfig
poolSelection
txProbability p100
rxParameters not present
rxParamsAddNeighFreq not present
txParamsAddNeighFreq
physCellId Note 1
p-Max 23
tdd-Config not present
tdd-Config-v1130 not present
freqInfo
ul-CarrierFreq Note 1
ul-Bandwidth n25
additionalSpectrumEmission NS_01
referenceSignalPower Note 2
syncConfigIndex not present
discResourcesPS not present
discConfigOther txPowerInfo discMaxTxPower 23
refCarrierCommon not present
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 570 ETSI TS 136 133 V14.3.0 (2017-04)
discSyncConfig not present
discCellSelectionInfo q-RxLevMin -70
(-140dBm)
q-RxLevMinOffset not present
q-Hyst dB0
q-RxLevMinReselection -70
(-140dBm)
t-ReselectionEUTRA 0
gapRequestsAllowedCommon True
discConfigRelay not present
discConfigPS not present
NOTE 1: As specified in the test.
NOTE 2: As configured by the test system.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 571 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.12.5 Reference resource pool configurations for ProSe Direct
Communication
Table A.3.12.5-1: ProSe Direct Communication configuration for E-UTRA FDD (Configuration #1)
Value Value
Information Element
(5MHz) (10MHz)
commRxPool sc-CP-Len Normal
sc-Period sf40
sc-TF-ResourceConfig prb-Num 12 25
prb-Start 0 0
prb-End 23 49
offsetIndicator 0
00011000
00000000
subframeBitmap 00000000
00000000
00000000
data-CP-Len Normal
dataHoppingConfig hoppingParameter 0
numSubbands ns1
rb-Offset 0
ue- data-TF-
prb-Num 12 25
SelectedResourceConfig ResourceConfig
prb-Start 0 0
prb-End 23 49
offsetIndicator 0
00000000
11111111
subframeBitmap 11111111
11111111
11111111
trpt-Subset-r12 001
rxParametersNCell not present
txParameters not present
commTxPoolNormalCommon/
sc-CP-Len Normal
commTxPoolNormalDedicated
sc-Period sf40
sc-TF-ResourceConfig prb-Num 12 25
prb-Start 0 0
prb-End 24 49
offsetIndicator 0
00011000
00000000
subframeBitmap 00000000
00000000
00000000
data-CP-Len Normal
dataHoppingConfig hoppingParameter 0
numSubbands ns1
rb-Offset 0
ue- data-TF-
prb-Num 12 25
SelectedResourceConfig ResourceConfig
prb-Start 0 0
prb-End 23 49
offsetIndicator 0
00000000
11111111
subframeBitmap 11111111
11111111
11111111
trpt-Subset-r12 001
rxParametersNCell not present
txParameters sc-TxParameters alpha al0
p0 31
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 572 ETSI TS 136 133 V14.3.0 (2017-04)
dataTxParameters alpha al0
p0 31
SL-SyncConfig syncCP-Len Normal
syncOffsetIndicator 2
slssid 30
txParameters txParametersGeneral alpha al0
p0 31
syncTxThreshIC 0 (-infinity)
rxParamsNCell not present
Table A.3.12.5-2: ProSe Direct Communication pre-configuration for E-UTRAN FDD for out-of-network
coverage operation (Configuration #2)
Value Value
Information Element
(5MHz) (10MHz)
preconfigSync syncCP-Len-r12 Normal
syncOffsetIndicator1 2
syncOffsetIndicator2 1
syncTxParameters 31
0
syncTxThreshOoC (-110dBm /
15kHz)
filterCoefficient fc0
syncRefMinHyst dB0
syncRefDiffHyst dB0
preconfigComm sc-CP-Len Normal
sc-Period sf40
sc-TF-ResourceConfig prb-Num 12 25
prb-Start 0 0
prb-End 23 49
offsetIndicator 0
00011000
00000000
subframeBitmap 00000000
00000000
00000000
data-CP-Len Normal
dataHoppingConfig hoppingParameter 0
numSubbands ns1
rb-Offset 0
ue- data-TF-
prb-Num 12 25
SelectedResourceConfig ResourceConfig
prb-Start 0 0
prb-End 23 49
offsetIndicator 0
00000000
11111111
subframeBitmap 11111111
11111111
11111111
trpt-Subset-r12 001
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 573 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.12.6 Reference Measurement Channels for ProSe Direct Discovery
A.3.12.6.1 FDD
Table A.3.12.6-1: PSDCH Reference Measurement Channels for FDD
Parameter Unit Value
Reference channel D.1 FDD
Channel bandwidth MHz 5
Allocated resource blocks 2
Subcarriers per resource block 12
Allocated subframes per Discovery period 1
DFT-OFDM Symbols per subframe (see 11
note)
Modulation QPSK
Information Bit Payload 232
Transport block CRC Bits 24
Maximum number of HARQ transmissions 1
Binary Channel Bits (see note) Bits 528
NOTE1: PSDCH transmissions are rate-matched for 12 DFT-OFDM
symbols per subframe, and the last symbol shall be
punctured as per TS 36.211.
A.3.12.7 Reference measurement channels for ProSe Direct Communication
A.3.12.7.1 FDD
Table A.3.12.7-1: PSCCH Reference Measurement Channels for FDD
Parameter Unit Value
Reference channel CC.1 FDD CC.2 FDD
Channel bandwidth MHz 5 10
Allocated resource blocks 1 1
Subcarriers per resource block 12 12
DFT-OFDM Symbols per subframe 11 11
(see Note 1)
Modulation QPSK QPSK
Information Bit Payload Bits 41 43
Frequency hopping flag 0
Set as per PSSCH RB
RB assignment
allocation specific in the test
Information Time resource pattern (ITRP) 0 (Note 2)
bits Modulation and coding Set as the PSSCH MCS
scheme specified in the test
Timing advance indication 0
Group destination ID As set by higher layers
Transport block CRC Bits 16 16
Maximum number of HARQ transmissions 2 2
Binary Channel Bits (see Note 1) Bits 264 264
NOTE1: PSCCH transmissions are rate-matched for 12 DFT-OFDM symbols per
subframe, and the last symbol shall be punctured as per TS 36.211.
NOTE 2: For NTRP = 8 (FDD) and trpt-Subset = 001, ITRP = 0 corresponds to a time
repetition pattern of (1,0,0,0,0,0,0,0) as per TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 574 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.12.7-1: PSSCH Reference Measurement Channels for FDD
Parameter Unit Value
Reference channel CD.1 FDD CD.2 FDD
Channel bandwidth MHz 5 10
Allocated resource blocks 2 3
Subcarriers per resource block 12 12
DFT-OFDM Symbols per subframe
11 11
(see Note 1)
Modulation QPSK QPSK
Target Code Rate 1/3 1/3
Information Bit Payload 176 256
Transport block CRC Bits 24 24
Maximum number of HARQ transmissions 3 3
Binary Channel Bits (see note) Bits 528 1056
NOTE1: PSDCH transmissions are rate-matched for 12 DFT-OFDM symbols per
subframe, and the last symbol shall be punctured as per TS 36.211.
A.3.12.8 ProSe Receive Traffic Generator
This clause defines the configuration for active Sidelink UEs used to generate receive traffic in ProSe RRM tests.
A.3.12.8.1 ProSe Direct Communication Receive Traffic Generator for FDD
Table A.3.12.8.1-1: Active Sidelink UE configuration for ProSe Direct Communication
Configuration PCP.1.FDD
Channel BW MHz 5 or 10
5 MHz: 12
Number of Active Sidelink UEs per sc-period
10 MHz: 16
PSCCH RMC 5 MHz: CC.1 FDD
(defined in A.3.12.7) 10 MHz: CC.2 FDD
5MHz: [2i:2i], for Sidelink UE i=0,..,11
PSCCH resource allocation
10MHz:[3i:3i], for Sidelink UE i = 0, .., 15
Active Sidelink PSSCH RMC 5 MHz: CD.1 FDD
UEs (defined in A.3.12.7) 10 MHz: CD.2 FDD
Non-overlapping RBs
PSSCH resource allocation 5MHz: [2i:2i+1], for Sidelink UE i = 0, .., 11
10MHz:[3i:3i+2], for Sidelink UE i = 0, .., 15
RSRP dBm/15kHz -98
A.3.12.8.2 ProSe Direct Discovery Receive Traffic Generator for FDD
Table A.3.12.8.2-1: Active Sidelink UE configuration for ProSe Direct Discovery
Configuration PDP.1.FDD PDP.2.FDD
Channel BW MHz 5
Number of Active Sidelink UEs per Discovery
12
subframe
PSDCH
(RMC D.1 FDD)
Sidelink UE PSDCH
+
Active Sidelink Transmissions (RMC D.1 FDD)
SLSS on synchronization
UEs
subframe
Resource allocation Non overlapping RBs in a subframe
RSRP dBm/15kHz -95
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 575 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.13 Time Offset between Cells
A.3.13.1 Introduction
In Annex A in some test cases a parameter called, ‘time offset between cells’ is used. The meaning of this parameter is
defined in this clause.
A.3.13.2 Definition
Unless explicitly stated otherwise, the time offset between cells for a pair of cells is defined as the difference between
radio frame start timings of the pair of cells.
A.3.14 Carrier Aggregation under operation with Frame Structure 3
Test Cases with Different Duplex Modes
A.3.14.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for carrier aggregation
with at least one Scell under operation with Frame Structure 3.
A.3.14.2 Principle of testing
In Annex A, tests for carrier aggregation with at least one Scell under operation with frame structure 3are specified with
both an FDD and a TDD Pell to verify the same RRM requirement. If both types of tests are relevant to a UE
considering supported CA bands, the test coverage can be considered fulfilled by executing either the tests with FDD
PCell or the tests with TDD PCell and the UE is not required to pass both tests.
A.3.15 Dual connectivity test cases with different combination of
duplex mode
A.3.15.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for dual connectivity (DC)
operation with different combination of duplex modes.
A.3.15.2 Principle of testing
If multiple dual connectivity test cases are defined for different combination of duplex modes (E-UTRA FDD-FDD, E-
UTRA TDD-TDD and E-UTRA TDD-FDD) to verify the same RRM requirement which is independent of the
combination of duplex modes and is identical for different combination of duplex modes, then from UE the
performance point of view the test coverage can be considered fulfilled by executing only the corresponding test case(s)
with one of the combination of duplex modes supported by the UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 576 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.16 Reference PRACH Configurations
Table A.3.16-1: PRACH configuration parameters
Parameter Value Comments
Reference configuration PRACH_2CE PRACH_3CE PRACH_4CE
{-107, -99} {-107, -99, -
Rsrp-ThresholdsPRACH {-99} dBm As defined in TS36.331
dBm 92} dBm
Up to 4 CE levels, each
CE level 0: Configured Configured Configured corrsesonding to a PRACH
configuration
：
FDD 4 ：
FDD 4 FDD 4：
Prach Configation Index:
：
TDD 53 ：
TDD 53 ：
TDD 53
See TS 36.211 section 5.7.1
Number of PRACH repetitions
numRepetitionPerPreambleAttempt: 1 1 1 per attempt for each CE level,
See TS 36.211
Coverage level specific
prach-HoppingConfig: off off off frequency hopping configuration
for PRACH
Up to 4 CE levels, each
CE level 1: Configured Configured Configured corrsesonding to a PRACH
configuration
：
FDD 4 ：
FDD 4 FDD 4：
Prach Configation Index:
：
TDD 53 ：
TDD 53 ：
TDD 53
see TS 36.211 section 5.7.1
Number of PRACH repetitions
numRepetitionPerPreambleAttempt: 128 64 32 per attempt for each CE level,
See TS 36.211
Coverage level specific
prach-HoppingConfig: off off off frequency hopping configuration
for PRACH
Up to 4 CE levels, each
Not
CE level 2: Configured Configured corrsesonding to a PRACH
Configured
configuration
：
FDD 4 FDD 4：
Prach Configation Index: -
：
TDD 53 ：
TDD 53
see TS 36.211 section 5.7.1
Number of PRACH repetitions
numRepetitionPerPreambleAttempt: - 128 64 per attempt for each CE level,
See TS 36.211
Coverage level specific
prach-HoppingConfig: - off off frequency hopping configuration
for PRACH
Up to 4 CE levels, each
Not Not
CE level 3: Configured corrsesonding to a PRACH
Configured Configured
configuration
FDD 4：
Prach Configation Index: - -
：
TDD 53
see TS 36.211 section 5.7.1
Number of PRACH repetitions
numRepetitionPerPreambleAttempt: - - 128 per attempt for each CE level,
See TS 36.211
Coverage level specific
prach-HoppingConfig: - - off frequency hopping configuration
for PRACH
A.3.17 Listen before talk model
A.3.17.1 Introduction
In some RRM test cases for FS3, a listen before talk (LBT) model is specified. The intention of the LBT model is to
emulate using test equipment the behaviour of an FS3 eNB which performs channel measurement to check that the
channel is clear prior to performing downlink transmission.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 577 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.17.2 Definition
Prior to each DMTC window, the test equipment shall determine whether to transmit a discovery reference signal
(DRS) during the DMTC window with probability P=[0.75]. In many cases the test requirement depends on the number
of configured discovery signal occasions which are not available during the test, so the test equipment shall track how
many DRS are not transmitted during the test period. If the test equipment determines that it shall transmit a DRS, then
the timing of the DRS transmission within the DMTC window is randomly selected from the set of possible DRS
transmission signal timings, such that there is an equal probability of any valid DRS timing.
For non DRS downlink transmission bursts, if transmission occurred in the previous subframe, transmission is muted
for a duration of one subframe. Additionaly, if the start time of the candidate transmission burst is within [8] subframes
of the start of the DMTC window, transmission is not performed. Otherwise
The length of the transmission burst in subframes is defined as N. The burst transmission format is determined
according to the steps below:
1. Select N randomly from a given set of the number of subframes S1={1,3,5,8} with equal probability as the total
length of burst transmission format.
2. A uniform random variable from [0, 1] is generated. If the random variable is less than P=[0.75], a burst of N
fully occupied subframes is transmitted. Otherwise, the burst transmission is muted and the muting duration is
the same as the number N of subframes for determined burst format.
A.3.18 Reference NPRACH Configurations
Table A.3.18-1 defines the reference NB-IoT PRACH configurations for a NB-IoT RRM test case where the UE is
required to transmit NPRACH during the testing procedure, but the testing purpose of the RRM test case does not
include testing NPRACH performance.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 578 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.3.18-1: NPRACH.R-1: Reference NPRACH Configuration
Field Value Comment
Parameters not per NPRACH coverage level
rsrp-ThresholdsPrach {rsrp1, rsrp2} The values of NPRACH
RSRP thresholds for will
be set according the
requirement of
individual test cases
nprach-CP-Length us66dot7 NPRACH format 0
Parameters per NPRACH coverage Level
CE Level Level 0 Level 1 Level 2 Valid values as
defined in TS 36.331
nprach-Periodicity ms40 ms40 ms40 {ms40, ms80, ms160,
ms240, ms320, ms640,
ms1280, ms2560}
nprach-StartTime ms8 ms8 ms8 {ms8, ms16, ms32,
ms64, ms128, ms256,
ms512, ms1024}
nprach-SubcarrierOffset n0 n0 n0 {n0, n12, n24, n36, n2,
n18, n34}
nprach-NumSubcarriers n12 n12 n12 {n12, n24, n36, n48}
nprach-SubcarrierMSG3- {one} {one} {one} {zero, oneThird,
RangeStart twoThird, one}
maxNumPreambleAttemptCE n3 n5 n7 {n3, n4, n5, n6, n7, n8,
n10}
numRepetitionsPerPreambleA n1 n8 n32 {n1, n2, n4, n8, n16,
ttempt n32, n64, n128}
npdcch-NumRepetitions-RA r1 r8 n32 {r1, r2, r4, r8, r16, r32,
r64, r128, r256, r512,
r1024, r2048}
npdcch-StartSF-CSS-RA v2 v2 v2 {v1dot5, v2, v4, v8, v16,
v32, v48, v64}
npdcch-Offset-RA zero zero zero {zero, oneEighth,
oneFourth, threeEighth}
Note 1: See Clause 6.3.2 in TS 36.331 for further information on the parameters in this table.
A.3.19 Dual connectivity test cases with different bandwidth
combinations
A.3.19.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for dual connectivity (DC)
operation with different bandwidth combinations.
A.3.19.2 Principle of testing
If multiple dual connectivity test cases with different channel bandwidth combinations are defined to verify the same
RRM requirement that is channel bandwidth independent, then the UE needs to be tested only with one bandwidth
combination out of the bandwidth combination sets supported by that UE.
A.3.20 Category M1 UE Test Cases
A.3.20.1 Introduction
This clause defines a principle which is applicable to test cases verifying RRM requirements for Category M1 UE in
both CEModeA and CEModeB.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 579 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.20.2 Principle of Cat-M1 UE Testing
In Annex A Cat-M1 UE test cases may be defined for both CEModeA and CEModeB to verify the same type of RRM
requirement.
If test cases are defined in both CEModeA and CEmodeB in order to verify the same type of RRM requirement then the
UE capable of CEModeB needs to be tested for the corresponding test(s) defined in CEModeA and/or in CEModeB
according to the applicability rules defined in Table A.3.20.2-1.
The UE which is not capable of CEModeB shall be tested for all CEModeA test cases defined in Annex A.
Table A.3.20.2-1: Test case applicability rules for category M1 UE in CEModeA and CEModeB
Type of Test Cases Coverage mode(s) Applicable for Testing
CEModeA CEModeB
A.4 E-UTRAN RRC IDLE State: Intra-frequency Cell Re-Selection Tests X X
for Category M1 UE
A.5 E-UTRAN RRC CONNECTED Mode Mobility: E-UTRAN Intra- X
frequency Handover Tests for Category M1 UE
A.5 RRC Connection Control: E-UTRAN Intra-frequency RRC Re- X
Restablishment Tests for Category M1 UE
A.6 E-UTRAN Contention Based Random Access Tests for Cat-M1 UE X
A.7 Timing and Signalling Characteristics: E-UTRAN UE Transmit Timing X
Timing Accuracy Tests for Category M1 UE
A.7 Timing and Signalling Characteristics: E-UTRAN Timing Advance X
Adjustment Accuracy Tests for Cat-M1 UE
A.7.3 Radio Link Monitoring: E-UTRAN Radio Link Monitoring Tests for X
Category M1 UE
A.8 Measurements Procedures: E-UTRAN Intra-frequency Event X X
Triggered Reporting under Fading Propagation Conditions Tests for
Category M1 UE
A.8 Measurements Procedures: E-UTRAN Intra-frequency Identification N/A X
of a New CGI of E-UTRA cell using Autonomous Gaps Tests for
Category M1 UE
A.9 Measurement Performance Requirements: RSRP Intra-Frequency X X
Measurement Accuracy Tests for Category M1 UE
A.3.21 V2V Sidelink Communication on Dedicated V2V Carrier
A.3.21.1 Introduction
This clause also defines the principle and the reference configurations that are applicable to test cases verifying RRM
core requirements for V2V sidelink communication on dedicated V2V carrier.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 580 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.21.2 Reference resource pool configurations for V2V Sidelink
Communication
Table A.3.21.2-1: Pre-configuration for V2V Sidelink Communication
Derivation Path: TS 36.331 [3] clause 9.3.2, SL-V2X-Preconfiguration
Information Element Value/remark Comment Condition
SL-V2X-PreconfigCommPool-
r14 ::= SEQUENCE {
Indicates the offset of the first subframe of
a resource pool within a SFN cycle. If
sl-OffsetIndicator-r14 0
absent, the resource pool starts from first
subframe of SFN=0.
10000000000000000000
Indicates the bitmap of the TX resource
10000000000000000000
sl-Subframe-r14 included in SL- pool, which is defined by repeating the
10000000000000000000
PreconfigV2X-TxPoolList bitmap within a SFN cycle (see TS 36.213
10000000000000000000
[23])
10000000000000000000
11111111111111111111
Indicates the bitmap of the RX resource
11111111111111111111
sl-Subframe-r14 included in SL- pool, which is defined by repeating the
11111111111111111111
PreconfigV2X-RxPoolList bitmap within a SFN cycle (see TS 36.213
11111111111111111111
[23])
11111111111111111111
Adjacent: TURE
adjacencyPSCCH-PSSCH-r14 True
Non-adjacent: FALSE
5 Minimum bandwidth of subchannel for
sizeSubchannel-r14
adjacent transmission
startRB-Subchannel-r14 0 Indicates the lowest RB index of the
subchannel with the lowest index.
startRB-PSCCH-Pool-r14 0 Indicates the lowest RB index of the
PSCCH pool
}
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 581 ETSI TS 136 133 V14.3.0 (2017-04)
A.3.21.3 Reference measurement channels for V2V Sidelink Communication
Table A.3.21.3-1: PSCCH Reference Measurement Channels
Parameter Unit Value
Reference channel CC.1
Channel bandwidth MHz 10
Allocated resource blocks 2
Subcarriers per resource block 12
DFT-OFDM Symbols per subframe 9
(see Note 1)
Modulation QPSK
Information Bit Payload Bits 48
Priority As set by higher layers
Resource reservation 0
Modulation and coding Set as the PSSCH MCS
scheme specified in the test
Retransmission index 0
Information Time gap between initial
Bit transmission and 0 (Note 2)
retransmission
Frequency resource location
Set as per PSSCH RB
of the initial transmission
allocation specific in the test
and retransmission
Reserved bits Set all these bits to 0
Transport block CRC Bits 16
Binary Channel Bits (see Note 1) Bits 264
Note 1: PSCCH transmissions are rate-matched for 10 DFT-OFDM symbols per
subframe, and the last symbol shall be punctured as per TS 36.211.
Note 2: SFgap is the value indicated by "Time gap between initial transmission and
retransmission" field in the configured sidelink grant, and SFgap =0 means
no retransmission of the associated TB as per TS 36.213.
Table A.3.21.3-2: PSSCH Reference Measurement Channels
Parameter Unit Value
Reference channel CD.1
Channel bandwidth MHz 10
Allocated resource blocks 3
Subcarriers per resource block 12
DFT-OFDM Symbols per subframe
9
(see Note 1)
Modulation QPSK
Target Code Rate 1/3
Information Bit Payload Bits 208
Transport block CRC Bits 24
Binary Channel Bits (see Note 1) Bits 648
Note1: PSSCH transmissions are rate-matched for 10 DFT-OFDM symbols per
subframe, and the last symbol shall be punctured as per TS 36.211.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 582 ETSI TS 136 133 V14.3.0 (2017-04)
A.4 E-UTRAN RRC_IDLE state
A.4.2 Cell Re-Selection
A.4.2.1 E-UTRAN FDD – FDD Intra frequency case
A.4.2.1.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD intra frequency cell reselection requirements specified in
clause 4.2.2.3.
The test scenario comprises of 1 E-UTRA FDD carrier and 2 cells as given in tables A.4.2.1.1-1 and A.4.2.1.1-2. The
test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Only Cell 1 is already
identified by the UE prior to the start of the test, i.e. Cell 2 is not identified by the UE prior to the start of the test. Cell 1
and Cell 2 belong to different tracking areas. Furthermore, UE has not registered with network for the tracking area
containing Cell 2.
Table A.4.2.1.1-1: General test parameters for FDD intra frequency cell reselection test case
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is used.
Channel Bandwidth (BW channel) MHz 10
Time offset between cells 3 ms Asynchronous cells
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
DRX cycle length s 1.28 The value shall be used for all cells in the
test.
T1 s >7 During T1, Cell 2 shall be powered off, and
during the off time the physical cell identity
shall be changed, The intention is to
ensure that Cell 2 has not been detected
by the UE prior to the start of period T2
T2 s 40 T2 need to be defined so that cell re-
selection reaction time is taken into
account.
T3 s 15 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 583 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.1.1-2: Cell specific test parameters for FDD intra frequency cell reselection test case in
AWGN
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns
defined in A.3.2.1.2 OP.2 FDD OP.2 FDD
(OP.2 FDD)
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_
reselection_quality_ RSRP RSRP
measurement
dB 16 -3.11 2.79 -infinity 2.79 -3.11
Ê s I ot
N oc Note2 dBm/15 kHz -98
dB 16 13 16 -infinity 16 13
Ês N oc
RSRP Note3 dBm/15 kHz -82 -85 -82 -infinity -82 -85
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation AWGN
Condition
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.4.2.1.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 34 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on Cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 1.
The cell re-selection delay to an already detected cell shall be less than 8 s.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 584 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI, and to
an already detected cell can be expressed as: TevaluateFDD,intra + TSI,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.3-1 in clause 4.2.2.3
TevaluateFDD,intra See Table 4.2.2.3-1 in clause 4.2.2.3
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 33.28 s, allow 34 s for the cell re-selection delay to a newly detectable cell and 7.68 s, allow 8 s for
the cell re-selection delay to an already detected cell in the test case.
A.4.2.2 E-UTRAN TDD – TDD Intra frequency case
A.4.2.2.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD intra frequency cell reselection requirements specified in
clause 4.2.2.3.
The test scenario comprises of 1 E-UTRA TDD carrier and 2 cells as given in tables A.4.2.2.1-1 and A.4.2.2.1-2. The
test consists of three successive time periods, with time duration of T1, T2, and T3 respectively. Only cell 1 is already
identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to different tracking areas. Furthermore, UE
has not registered with network for the tracking area containing cell 2.
Table A.4.2.2.1-1: General test parameters for TDD intra frequency cell re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is used.
Channel Bandwidth (BW channel) MHz 10
Time offset between cells μs 3 Synchronous cells
Access Barring Information - Not Sent No additional delays in random access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS 36.211
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s >7 During T1, Cell 2 shall be powered off, and during
the off time the physical cell identity shall be
changed, The intention is to ensure that Cell 2 has
not been detected by the UE prior to the start of
period T2
T2 s 40 T2 need to be defined so that cell re-selection
reaction time is taken into account.
T3 s 15 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 585 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.2.1-2: Cell specific test parameters for TDD intra frequency cell re-selection test case in
AWGN
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Pattern
defined in A.3.2.2.2 OP.2 TDD OP.2 TDD
(OP.2 TDD)
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
Qrxlevmin dBm -140 -140
Pcompensation dB 0 0
Qhysts dB 0 0
Qoffsets, n dB 0 0
Cell_selection_and_
reselection_quality_ RSRP RSRP
measurement
dB 16 -3.11 2.79 -infinity 2.79 -3.11
Ê s I ot
N oc Note2 dBm/15 kHz -98
dB 16 13 16 -infinity 16 13
Ês N oc
RSRP Note3 dBm/15 kHz -82 -85 -82 -infinity -82 -85
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation AWGN
Condition
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to
be constant over subcarriers and time and shall be modelled as AWGN of appropriate
N
power for oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They
are not settable parameters themselves.
A.4.2.2.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 34 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on cell 1.
The cell re-selection delay shall be less than 8 s.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 586 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI-EUTRA,
and to an already detected cell can be expressed as: Tevaluate, E-UTRAN_ intra + TSI-EUTRA,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.3-1 in clause 4.2.2.3
Tevaluate,E-UTRAN_ intra See Table 4.2.2.3-1 in clause 4.2.2.3
TSI-EUTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 33.28 s, allow 34 s for the cell re-selection delay to a newly detectable cell and 7.68 s, allow 8 s for
the cell re-selection delay to an already detected cell in the test case.
A.4.2.3 E-UTRAN FDD – FDD Inter frequency case
A.4.2.3.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD inter-frequency cell reselection requirements specified in
clause 4.2.2.4.
The test scenario comprises of 2 E-UTRA FDD cells on 2 different carriers as given in tables A.4.2.3.1-1 and A.4.2.3.1-
2. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Both cell 1 and
cell 2 are already identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to different tracking areas
and cell 2 is of higher priority than cell 1. Furthermore, UE has not registered with network for the tracking area
containing cell 2.
Table A.4.2.3.1-1: General test parameters for FDD-FDD inter frequency cell re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell2 UE shall be forced to cell 2 in the initialisation
condition phase, so that reselection to cell 1 occurs during
the first T1 phase
T1 end Active cell Cell1 UE shall perform reselection to cell 1 during T1
condition Neighbour cell Cell2
Final Active cell Cell2 UE shall perform reselection to cell 2 during T3
condition
E-UTRA RF Channel Number 1, 2 Two FDD carrier frequencies are used.
Time offset between cells 3 ms Asynchronous cells
PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 15 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s >7 During T2, cell 2 shall be powered off, and
during the off time the physical cell identity shall
be changed, The intention is to ensure that cell 2
has not been detected by the UE prior to the
start of period T3.
T3 s 75 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 587 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.3.1-2: Cell specific test parameters for FDD-FDD inter-frequency cell reselection test case
in AWGN
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
number
BW channel MHz 10 10
OCNG Patterns defined in
A.3.2.1.2 (OP.2 FDD) OP.2 FDD OP.2 FDD
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 KHz -84 -84 -84 -102 -infinity -86
dB 14 14 14 -4 -infinity 12
Ê s I ot
dB 14 14 14 -4 -infinity 12
Ês N oc
TreselectionEUTRAN s 0 0
Snonintrasearch dB 50 Not sent
Threshx, high dB 48 48
Threshserving, low dB 44 44
Threshx, low dB 50 50
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
A.4.2.3.2 Test Requirements
The cell reselection delay to higher priority is defined as the time from the beginning of time period T3, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to higher priority shall be less than 68 s.
The cell reselection delay to lower priority is defined as the time from the beginning of time period T1, to the moment
when the UE camps on cell 1, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on cell 1.
The cell re-selection delay to lower priority shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to higher priority cell can be expressed as: Thigher_priority_search + TevaluateFDD,inter +
TSI , and to lower priority cell can be expressed as: TevaluateFDD,inter + TSI,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 588 ETSI TS 136 133 V14.3.0 (2017-04)
Where:
Thigher_priority_search See clause 4.2.2
TevaluateFDD,inter See Table 4.2.2.4-1 in clause 4.2.2.4
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 67.68 s for higher priority cell search and 7.68 s for lower priority cell search, allow 68 s for higher
priority cell and 8 s for lower priority cell in the test case.
A.4.2.4 E-UTRAN FDD – TDD Inter frequency case
A.4.2.4.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-TDD inter-frequency cell reselection requirements specified in
clause 4.2.2.4.
The test scenario comprises of 1 E-UTRA FDD cell and 1 E-UTRA TDD cell as given in tables A.4.2.4.1-1 and
A.4.2.4.1-2. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Both
cell 1 and cell 2 are already identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to different
tracking areas and cell 2 is of higher priority than cell 1. Furthermore, UE has not registered with network for the
tracking area containing cell 2.
Table A.4.2.4.1-1: General test parameters for FDD-TDD inter frequency cell re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell2 UE shall be forced to cell 2 in the initialisation
condition phase, so that reselection to cell 1 occurs during
the first T1 phase
T1 end Active cell Cell1 UE shall perform reselection to cell 1 during T1
condition Neighbour cell Cell2
Final Active cell Cell2 UE shall perform reselection to cell 2 during T3
condition
Cell 1 E-UTRA RF Channel 1 One FDD carrier frequency is used. And Cell 1 is
Number on RF channel number 1.
Cell 2 E-UTRA RF Channel 2 One TDD carrier frequencies is used. And Cell 2
Number is on RF channel number 2.
Time offset between cells 3 ms Asynchronous cells
E-UTRA FDD PRACH 4 As specified in table 5.7.1-2 in TS 36.211
configuration
E-UTRA TDD PRACH 53 As specified in table 5.7.1-3 in TS 36.211
configuration
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
E-UTRA FDD Access Barring - Not Sent No additional delays in random access
Information procedure.
E-UTRA TDD Access Barring - Not Sent No additional delays in random access
Information procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 15 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s >7 During T2, cell 2 shall be powered off, and
during the off time the physical cell identity shall
be changed, The intention is to ensure that cell 2
has not been detected by the UE prior to the
start of period T3.
T3 s 75 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 589 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.4.1-2: Cell specific test parameters for FDD-TDD inter-frequency cell reselection test case
in AWGN
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
number
BW channel MHz 10 10
OCNG Patterns defined in
A.3.2.1.2 (OP.2 FDD) and OP.2 FDD OP.2 TDD
A.3.2.2.2 (OP.2 TDD)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 KHz -84 -84 -84 -102 -infinity -86
dB 14 14 14 -4 -infinity 12
Ê s I ot
dB 14 14 14 -4 -infinity 12
Ês N oc
TreselectionEUTRAN s 0 0
Snonintrasearch dB 50 Not sent
Threshx, high dB 48 48
Threshserving, low dB 44 44
Threshx, low dB 50 50
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
A.4.2.4.2 Test Requirements
The cell reselection delay to higher priority is defined as the time from the beginning of time period T3, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on cell 2.
The cell re-selection delay to higher priority shall be less than 68 s.
The cell reselection delay to lower priority is defined as the time from the beginning of time period T1, to the moment
when the UE camps on cell 1, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on cell 1.
The cell re-selection delay to lower priority shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to higher priority cell can be expressed as: Thigher_priority_search + Tevaluate,E-
UTRAN_inter+ TSI-EUTRA , and to lower priority cell can be expressed as: Tevaluate,E-UTRAN_inter + TSI-EUTRA,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 590 ETSI TS 136 133 V14.3.0 (2017-04)
Where:
Thigher_priority_search See clause 4.2.2
Tevaluate,E-UTRAN_inter See Table 4.2.2.4-1 in clause 4.2.2.4
TSI-EUTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 67.68 s for higher priority cell search and 7.68 s for lower priority cell search, allow 68 s for higher
priority cell and 8 s for lower priority cell in the test case.
A.4.2.5 E-UTRAN TDD – FDD Inter frequency case
A.4.2.5.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-FDD inter-frequency cell reselection requirements specified in
clause 4.2.2.4.
The test scenario comprises of 1 E-UTRA TDD cell and 1 E-UTRA FDD cell as given in tables A.4.2.5.1-1 and
A.4.2.5.1-2. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Both
cell 1 and cell 2 are already identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to different
tracking areas and cell 2 is of higher priority than cell 1. Furthermore, UE has not registered with network for the
tracking area containing cell 2.
Table A.4.2.5.1-1: General test parameters for TDD-FDD inter frequency cell re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell2 UE shall be forced to cell 2 in the initialisation
condition phase, so that reselection to cell 1 occurs during
the first T1 phase
T1 end Active cell Cell1 UE shall perform reselection to cell 1 during T1
condition Neighbour cell Cell2
Final Active cell Cell2 UE shall perform reselection to cell 2 during T3
condition
Cell 1 E-UTRA RF Channel 1 One TDD carrier frequency is used. And Cell 1 is
Number on RF channel number 1.
Cell 2 E-UTRA RF Channel 2 One FDD carrier frequencies is used. And Cell 2
Number is on RF channel number 2.
Time offset between cells 3 ms Asynchronous cells
E-UTRA TDD PRACH 53 As specified in table 5.7.1-3 in TS 36.211
configuration
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
E-UTRA FDD PRACH 4 As specified in table 5.7.1-2 in TS 36.211
configuration
E-UTRA FDD Access Barring - Not Sent No additional delays in random access
Information procedure.
E-UTRA TDD Access Barring - Not Sent No additional delays in random access
Information procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 15 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s >7 During T2, cell 2 shall be powered off, and
during the off time the physical cell identity shall
be changed, The intention is to ensure that cell 2
has not been detected by the UE prior to the
start of period T3.
T3 s 75 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 591 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.5.1-2: Cell specific test parameters for TDD-FDD inter-frequency cell reselection test case
in AWGN
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
number
BW channel MHz 10 10
OCNG Patterns defined in
A.3.2.1.2 (OP.2 FDD) and OP.2 TDD OP.2 FDD
A.3.2.2.2 (OP.2 TDD)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 KHz -84 -84 -84 -102 -infinity -86
dB 14 14 14 -4 -infinity 12
Ê s I ot
dB 14 14 14 -4 -infinity 12
Ês N oc
TreselectionEUTRAN s 0 0
Snonintrasearch dB 50 Not sent
Threshx, high dB 48 48
Threshserving, low dB 44 44
Threshx, low dB 50 50
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
A.4.2.5.2 Test Requirements
The cell reselection delay to higher priority is defined as the time from the beginning of time period T3, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on cell 2.
The cell re-selection delay to higher priority shall be less than 68 s.
The cell reselection delay to lower priority is defined as the time from the beginning of time period T1, to the moment
when the UE camps on cell 1, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on cell 1.
The cell re-selection delay to lower priority shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to higher priority cell can be expressed as: Thigher_priority_search + Tevaluate,E-
UTRAN_inter+ TSI-EUTRA , and to lower priority cell can be expressed as: Tevaluate,E-UTRAN_inter + TSI-EUTRA,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 592 ETSI TS 136 133 V14.3.0 (2017-04)
Where:
Thigher_priority_search See clause 4.2.2
Tevaluate,E-UTRAN_inter See Table 4.2.2.4-1 in clause 4.2.2.4
TSI-EUTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 67.68 s for higher priority cell search and 7.68 s for lower priority cell search, allow 68 s for higher
priority cell and 8 s for lower priority cell in the test case.
A.4.2.6 E-UTRAN TDD – TDD: Inter frequency case
A.4.2.6.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD inter-frequency cell reselection requirements specified in
clause 4.2.2.4.
The test scenario comprises of 2 E-UTRA TDD cells on 2 different carriers as given in tables A.4.2.6.1-1 and A.4.2.6.1-
2. The test consists of three successive time periods, with time duration of T1, T2, and T2 respectively. Both cell 1 and
cell 2 are already identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to different tracking areas
and cell 2 is of higher priority than cell 1. Furthermore, UE has not registered with network for the tracking area
containing cell 2.
Table A.4.2.6.1-1: General test parameters for TDD-TDD inter frequency cell reselection test case
Parameter Unit Value Comment
Initial Active cell Cell2 UE shall be forced to cell 2 in the initialisation
condition phase, so that reselection to cell 1 occurs during
the first T1 phase
T1 end Active cells Cell1 UE shall perform reselection to cell 1 during T1
condition Neighbour cell Cell2
Final Active cell Cell2 UE shall perform reselection to cell 2 during T3
condition
E-UTRA RF Channel Number 1, 2 Two TDD carrier frequencies are used.
Time offset between cells 3 μs Synchronous cells
Access Barring Information - Not Sent No additional delays in random access
procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS 36.211
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 15 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s >7 During T2, cell 2 shall be powered off, and
during the off time the physical cell identity shall
be changed, The intention is to ensure that cell 2
has not been detected by the UE prior to the
start of period T3.
T3 s 75 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 593 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.6.1-2: Cell specific test parameters for TDD-TDD inter-frequency cell reselection test case
in AWGN
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
number
BW channel MHz 10 10
OCNG Pattern defined in
A.3.2.2.2 (OP.2 TDD) OP.2 TDD OP.2 TDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 KHz -84 -84 -84 -102 -infinity -86
dB 14 14 14 -4 -infinity 12
Ê s I ot
dB 14 14 14 -4 -infinity 12
Ês N oc
TreselectionEUTRAN S 0 0
Snonintrasearch dB 50 Not sent
Threshx, high dB 48 48
Threshserving, low dB 44 44
Threshx, low dB 50 50
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
A.4.2.6.2 Test Requirements
The cell reselection delay to higher priority is defined as the time from the beginning of time period T3, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on cell 2.
The cell re-selection delay to higher priority shall be less than 68 s.
The cell reselection delay to lower priority is defined as the time from the beginning of time period T1, to the moment
when the UE camps on cell 1, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on cell 1.
The cell re-selection delay to lower priority shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to higher priority cell can be expressed as: Thigher_priority_search + Tevaluate,E-
UTRAN_inter+ TSI-EUTRA , and to lower priority cell can be expressed as: Tevaluate,E-UTRAN_inter + TSI-EUTRA,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 594 ETSI TS 136 133 V14.3.0 (2017-04)
Where:
Thigher_priority_search See clause 4.2.2
Tevaluate,E-UTRAN_inter See Table 4.2.2.4-1 in clause 4.2.2.4
TSI-EUTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 67.68 s for higher priority cell search and 7.68 s for lower priority cell search, allow 68 s for higher
priority cell and 8 s for lower priority cell in the test case.
A.4.2.7 E-UTRAN FDD – FDD Inter frequency case in the existence of non-
allowed CSG cell
A.4.2.7.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD inter-frequency cell reselection requirements specified in
clause 4.2.2.4 when there is the interference from non-allowed CSG cell and the layers have equal priority.
The test scenario comprises of 2 E-UTRA FDD cells on 2 different carriers and 1 non-allowed E-UTRA FDD CSG cell
as given in tables A.4.2.7.1-1 and A.4.2.7.1-2. The test consists of three successive time periods, with time duration of
T1, T2 and T3 respectively. Cell 1 is already identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to
different tracking areas and cell 3 is a non-allowed CSG cell. Furthermore, UE has not registered with network for the
tracking area containing cell 2.
Table A.4.2.7.1-1: General test parameters for FDD-FDD inter frequency cell re-selection test case
with non-allowed CSG cell
Parameter Unit Value Comment
Initial Active cell Cell1 UE shall be forced to cell 1 in the initialisation
condition phase
Final Active cell Cell2 UE shall perform reselection to cell 2 during T2
condition
E-UTRA RF Channel Number 1, 2 Two FDD carrier frequencies are used.
Time offset between cells 3 ms Asynchronous cells
PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 15 T1 need to be defined so that the non-allowed
CSG cell is identified.
T2 s 40 T2 need to be defined so that cell re-selection
reaction time is taken into account.
T3 s 15 T3 need to be defined so that whether cell re-
selection would not occur is insured.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 595 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.7.1-2: Cell specific test parameters for FDD-FDD inter frequency cell re-selection test
case with non-allowed CSG cell
Parameter Unit Cell 1 Cell 2 Cell 3(Non-allowed CSG
cell)
T1 T2 T3 T1 T2 T3 T1 T2 T3
E-UTRA RF 1 2 1
Channel Number
BW channel MHz 10 10 10
OCNG Patterns
defined in A.3.2.1.2
(OP.2 FDD) OP.2 FDD OP.2 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
0 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
dB
OCNG_RBNote 1
Qrxlevmin dBm -140 -140 -140
Qqualmin dB -20
N oc Note 2 dBm/15 -98
kHz
RSRP Note 3 dBm/15 -90 -90 -85 -Infinity -85 -90 -90 -85 -60
kHz
RSRQ Note 3 dB -14.1 -17.1 -35.8 -14.1 -12.1 -10.8
dB -0.64 -5.21 -25 -Infinity 13 8 -0.64 4.36 24.8
Ê s I ot
dB 8 8 13 -Infinity 13 8 8 13 38
Ês N oc
Treselection s 0 0 0
Snonintrasearch dB -10 Not sent Not sent
Propagation AWGN
Condition
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and RSRQ levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
A.4.2.7.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 34 s.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 596 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
The probability of reselection from Cell 2 to Cell 1 during T3 observed during testing shall be less than 10%.
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Inter + TSI,
Where:
Tdetect,EUTRAN_Inter See Table 4.2.2.4-1 in clause 4.2.2.4
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE to camp on a
cell; 1280 ms is assumed in this test case.
This gives a total of 33.28 s, allow 34 s for the cell re-selection delay to a newly detectable cell in the test case.
A.4.2.8 E-UTRAN TDD – TDD Inter frequency case in the existence of non-
allowed CSG cell
A.4.2.8.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD inter-frequency cell reselection requirements specified in
clause 4.2.2.4 when there is the interference from non-allowed CSG cell and the layers have equal priority.
The test scenario comprises of 2 E-UTRA TDD cells on 2 different carriers and 1 non-allowed E-UTRA TDD CSG cell
as given in tables A.4.2.8.1-1 and A.4.2.8.1-2. The test consists of three successive time periods, with time duration of
T1, T2 and T3 respectively. Cell 1 is already identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to
different tracking areas and cell 3 is a non-allowed CSG cell. Furthermore, UE has not registered with network for the
tracking area containing cell 2.
Table A.4.2.8.1-1: General test parameters for TDD-TDD inter frequency cell re-selection test case
with non-allowed CSG cell
Parameter Unit Value Comment
Initial Active cell Cell1 UE shall be forced to cell 1 in the initialisation
condition phase
Final Active cell Cell2 UE shall perform reselection to cell 2 during T2
condition
E-UTRA RF Channel Number 1, 2 Two TDD carrier frequencies are used.
Time offset between cells μs 3 Synchronous cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
PRACH configuration 53 As specified in table 5.7.1-3 in TS 36.211
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 15 T1 need to be defined so that the non-allowed
CSG cell is identified.
T2 s 40 T2 need to be defined so that cell re-selection
reaction time is taken into account.
T3 s 15 T3 need to be defined so that whether cell re-
selection would not occur is insured.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 597 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.8.1-2: Cell specific test parameters for TDD-TDD inter frequency cell re-selection test
case with non-allowed CSG cell
Parameter Unit Cell 1 Cell 2 Cell 3
(Non-allowed CSG cell)
T1 T2 T3 T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2 1
Number
BW channel MHz 10 10 10
OCNG Pattern defined in
OP.2 TDD OP.2 TDD OP.2 TDD
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140
Qqualmin dB -20
N oc Note 2 dBm/ -98
15kHz
RSRP Note 3 dBm/ -90 -90 -85 -Infinity -85 -90 -90 -85 -60
15kHz
RSRQ Note 3 dB -14.1 -17.1 -35.8 -14.1 -12.1 -10.8
Ê s I ot dB -0.64 -5.21 -25 -Infinity 13 8 -0.64 4.36 24.8
Ê s N oc dB 8 8 13 -Infinity 13 8 8 13 38
Treselection S 0 0 0
Snonintrasearch dB -10 Not sent Not sent
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP and RSRQ levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
A.4.2.8.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 34 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
The probability of reselection from Cell 2 to Cell 1 during T3 observed during testing shall be less than 10%.
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Inter + TSI,
Where:
Tdetect,EUTRAN_Inter See Table 4.2.2.4-1 in clause 4.2.2.4
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 598 ETSI TS 136 133 V14.3.0 (2017-04)
This gives a total of 33.28 s, allow 34 s for the cell re-selection delay to a newly detectable cell in the test case.
A.4.2.9 E-UTRAN FDD – FDD Intra frequency case for 5MHz bandwidth
A.4.2.9.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.4.2.1.1.
The parameters of this test are the same as defined in Subclause A.4.2.1.1 except that the values of the parameters in the
Table A.4.2.9.1-1 will replace the values of the corresponding parameters in A.4.2.1.1-1, and the values of the
parameters in the Table A.4.2.9.1-2 will replace the values of the corresponding parameters in A.4.2.1.1-2.
Table A.4.2.9.1-1: General test parameters for FDD intra frequency cell reselection test case for 5MHz
bandwidth
Parameter Unit Value Comment
Channel Bandwidth (BW channel) MHz 5
Note 1: See Table A.4.2.1.1-1 for the other parameters.
Note 2: This is according to the principle defined in section A.3.7.2.
Table A.4.2.9.1-2: Cell specific test parameters for FDD intra frequency cell reselection test case in
AWGN for 5MHz
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
BW channel MHz 5 5
OCNG Patterns
defined in A.3.2.1.16 OP.16 FDD OP.16 FDD
(OP.16 FDD)
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: See Table A.4.2.1.1-2 for the other parameters.
A.4.2.9.2 Test Requirements
The test requirements defined in section A.4.2.1.2 shall apply to this test case.
A.4.2.10 E-UTRAN FDD – FDD reselection using an increased number of
carriers
A.4.2.10.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD inter-frequency cell reselection requirements for increased UE
carrier monitoring specified in clause 4.2.2.4.
The test scenario comprises of indicating 8 E-UTRA FDD interfrequency cells on 8 different carriers in the neighbour
list of cell 1 as given in tables A.4.2.10.1-1 and A.4.2.10.1-2. Each repetition of the test consists of five successive time
periods, with time duration of T0, T1, T2, T3 and T4 respectively. In the initialisation phase and at the start of each
repetition of T0, the test equipment provides signals for cell 1 (serving cell), and selects frequencies for cells 2, 3 and 4
which are chosen from the 8 intefrequency layers which are configured in the UE neighbour cell list as described in
general and cell specific parameters. The neighbour lists of cells 2, 3 and 4 shall include the frequency of cell 1 in the
normal performance group as well as the other frequencies configured to the UE in the test.
Cell 1, 2, 3 and 4 are identified by the UE during time phase T0. Cell 1, cell 2, cell 3 and cell 4 all belong to different
tracking areas. Furthermore, UE has not registered with network for the tracking area containing cell 2, 3 or 4. Cells 1,
2, 3 and 4 all have equal absolute priority.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 599 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.10.1-1: General test parameters for FDD-FDD inter frequency cell re-selection test case
Parameter Unit Value Comment
T0 Active cell Cell1 T0 is repeated on each repetition of the test.
In T0 the test equipment selects frequencies
for cell 2, 3, 4 and then time is allowed for
the UE to identify the neighbour cells. See
cell specific parameters for detailed settings.
T1 start condition Active cell Cell 1
T1 end condition Active cell Cell 2 UE shall perform reselection to cell 2 during
T1
Neighbour cell Cell 1, cell 3, cell 4
T2 end condition Active cell Cell 3 UE shall perform reselection to cell 3 during
T2
Neighbour cell Cell 1, cell 2, cell 4
T3 end condition Active cell Cell 4 UE shall perform reselection to cell 4 during
T3
Neighbour cell Cell 1, cell 2, cell 3
Active cell Cell 1 UE shall perform reselection to cell 1 during
T4 end condition
T4
Neighbour cell Cell 2, cell 3, cell 4
UE configured E-UTRA RF 1, 2,3,4,5,6,7,8,9 Serving cell and eight xDD carrier
Channel Number frequencies are used in the UE neighbour
cell list. Frequencies 5,6,7,8 and 9 are
indicated to have reduced performance
Test eqipment configuration Cell 1 uses UTRA RF
channel number 1
Cells 2,3,4 are
randomly selected to
use different
frequencies selected
from frequencies
2,3,4,5,6,7,8,9
PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
[16]
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the
test.
T0 s (Test equipment T0 is defined so that the Test equipment
frequency selection selects frequencies and configures the cells,
and configuration time) then the UE cell detection time is taken into
+ 960 account.
T1 s 25 T1 need to be defined so that cell re-
selection reaction time is taken into account.
T2 s 200 T2 need to be defined so that cell re-
selection reaction time is taken into account
T3 s 200 T3 need to be defined so that cell re-
selection reaction time is taken into account.
T4 s 25 T4 need to be defined so that cell re-
selection reaction time is taken into account
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 600 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.10.1-2: Cell specific test parameters for FDD-FDD inter-frequency cell reselection test case in AWGN
Parameter Unit Cell 1 Cell 2 Cell 3 Cell 4
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4 T0 T1 T2 T3 T4 T0 T1 T2
E-UTRA RF Channel 1 Randomly selected from 2,3,4 Randomly selected from Randomly selected from
number such that cell 2 is in the normal 5,6,7,8,9 such that cell 3 5,6,7,8,9 such that cell 4
performance group is in the reduced is in the reduced
performance group performance group
BW channel MHz 5MHz: NRB = 25 5MHz: NRB,= 25 5MHz: NRB = 25 5MHz: NRB= 25
10MHz: NRB = 50 10MHz: NRB,= 50 10MHz: NRB = 50 10MHz: NRB, = 50
OCNG patterns OP.16 FDD (5MHz) OP.16 FDD (5MHz) OP.16 FDD (5MHz) OP.16 FDD (5MHz)
OP.2 FDD (10MHz) OP.2 FDD (10MHz) OP.2 FDD (10MHz) OP.2 FDD (10MHz)
PBCH_RA dB 0 0 0 0
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140
N oc Note 2 dBm/15 -98 -98 -98 -98
kHz
Ê s N oc dB 14 8 8 8 14 8 14 8 8 8 8 8 14 8 8 8 8 8
Ê s I ot dB 14 8 8 8 14 8 14 8 8 8 8 8 14 8 8 8 8 8
RSRP Note 3 dBm/15 -84 -90 -90 -90 -84 -90 -84 -90 -90 -90 -90 -90 -84 -90 -90 -90 -90 -90
kHz
TreselectionEUTRAN s 0 0 0 0
Snonintrasearch dB 62 62 62 62
Propagation Condition AWGN AWGN AWGN AWGN
Antenna Configuration 1x2 1x2 1x2 1x2
Timing offset to Cell 1 - 3ms 3ms 3ms
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as
AWGN of appropriate power for to be fulfilled.
Note 3: Es/Iot and RSRP levels have been derived from other parameters for information purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 601 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.2.10.2 Test Requirements
The cell reselection delay is defined as the time from the beginning of a relevant time period, to the moment when the
UE camps on the target cell, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on the target cell.
The reselection delays shall meet the requirements in table A.4.2.10.2-1.
Table A.4.2.10.2-1 : Reselection delay requirements
Time phase Target cell Requirement for reselection delay (seconds)
T1 Cell 2 (normal performance group) 20.5
T2 Cell 3 (reduced performance group) 193.3
T3 Cell 4 (reduced performance group) 193.3
T4 Cell 1 (normal performance group) 20.5
NOTE: The cell re-selection delay to a normal performance group cell can be expressed as: Kcarrier,normal *
Tevaluate,E-UTRAN_Inter, + TSI , and to a reduced performance group cell can be expressed as: 6* Kcarrier,reduced *
Tevaluate,E-UTRAN_Inter, + TSI,
This gives a total of 20.48 s for normal performance group reselection and 193.28 s for reduced performance group
reselection, allow 20.5 s for normal performance group and 193.3 s for reduced performance group in the test case. At
least 90% of reselections to the reduced performance group shall be within the required time, and at least 90% of
reselections to the normal performance group shall be within the required time, with a successful reselection counted if
it is within the required time regardless of the carrier frequencies involved.
A.4.2.11 E-UTRAN TDD – TDD reselection using an increased number of
carriers
A.4.2.11.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD inter-frequency cell reselection requirements for increased UE
carrier monitoring specified in clause 4.2.2.4.
The test scenario comprises of indicating 8 E-UTRA TDD interfrequency cells on 8 different carriers in the neighbour
list of cell 1 as given in tables A.4.2.11.1-1 and A.4.2.11.1-2. Each repetition of the test consists of five successive time
periods, with time duration of T0, T1, T2, T3 and T4 respectively. In the initialisation phase and at the start of each
repetition of T0, the test equipment provides signals for cell 1 (serving cell), and selects frequencies for cells 2, 3 and 4
which are chosen from the 8 intefrequency layers which are configured in the UE neighbour cell list as described in
general and cell specific parameters. The neighbour lists of cells 2, 3 and 4 shall include the frequency of cell 1 in the
normal performance group as well as the other frequencies configured to the UE in the test.
Cell 1, 2, 3 and 4 are identified by the UE during time phase T0. Cell 1, cell 2, cell 3 and cell 4 all belong to different
tracking areas. Furthermore, UE has not registered with network for the tracking area containing cell 2, 3 or 4. Cells 1,
2, 3 and 4 all have equal absolute priority.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 602 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.11.1-1: General test parameters for TDD-TDD inter frequency cell re-selection test case
Parameter Unit Value Comment
T0 Active cell Cell1 T0 is repeated on each repetition of the
test. In T0 the test equipment selects
frequencies for cell 2,3,4 and then time
is allowed for the UE to identify the
neighbour cells. See cell specific
parameters for detailed settings.
T1 start condition Active cell Cell 1
T1 end condition Active cell Cell 2 UE shall perform reselection to cell 2
during T1
Neighbour cell Cell 1, cell 3, cell 4
T2 end condition Active cell Cell 3 UE shall perform reselection to cell 3
during T2
Neighbour cell Cell 1, cell 2, cell 4
T3 end condition Active cell Cell4 UE shall perform reselection to cell 4
during T3
Neighbour cell Cell 1, cell 2, cell 3
Active cell Cell1 UE shall perform reselection to cell 1
T4 end condition
during T4
Neighbour cell Cell 2, cell 3, cell 4
UE configured E-UTRA RF Channel 1, 2,3,4,5,6,7,8,9 Serving cell and eight xDD carrier
Number frequencies are used in the UE
neighbour cell list. Frequencies 5,6,7,8
and 9 are indicated to have reduced
performance
Test eqipment configuration Cell 1 uses UTRA
RF channel
number 1
Cells 2,3,4 are
randomly selected
to use different
frequencies
selected from
frequencies
2,3,4,5,6,7,8,9
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211 [16]
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in
the test.
T0 s (Test equipment T0 is defined so that the Test
frequency equipment selects frequencies and
selection and configures the cells, then the UE cell
configuration time) detection time is taken into account.
+ 960
T1 s 25 T1 need to be defined so that cell re-
selection reaction time is taken into
account.
T2 s 200 T2 need to be defined so that cell re-
selection reaction time is taken into
account
T3 s 200 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
T4 s 25 T4 need to be defined so that cell re-
selection reaction time is taken into
account
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 603 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.11.1-2: Cell specific test parameters for TDD-TDD inter-frequency cell reselection test case in AWGN
Parameter Unit Cell 1 Cell 2 Cell 3 Cell 4
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4 T0 T1 T2 T3 T4 T0 T1 T2
E-UTRA RF Channel 1 Randomly selected from 2,3,4 such that Randomly selected from 5,6,7,8,9 Randomly selected from 5,6,7,8,9
number cell 2 is in the normal performance group such that cell 3 is in the reduced such that cell 4 is in the reduced
performance group performance group
BW channel MHz 5MHz: NRB = 25 5MHz: NRB,= 25 5MHz: NRB = 25 5MHz: NRB= 25
10MHz: NRB = 50 10MHz: NRB,= 50 10MHz: NRB = 50 10MHz: NRB, = 50
OCNG Patterns 5MHz: OP.10 TDD 5MHz: OP.10 TDD 5MHz: OP.10 TDD 5MHz: OP.10 TDD
10MHz: OP.2 TDD 10MHz: OP.2 TDD 10MHz: OP.2 TDD 10MHz: OP.2 TDD
PBCH_RA dB 0 0 0 0
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140
N oc Note 2 dBm15 -98 -98 -98 -98
kHz
Ê s N oc dB 14 8 8 8 14 8 14 8 8 8 8 8 14 8 8 8 8 8
Ê s I ot dB 14 8 8 8 14 8 14 8 8 8 8 8 14 8 8 8 8 8
RSRP Note 3 dBm/15 -84 -90 -90 -90 -84 -90 -84 -90 -90 -90 -90 -90 -84 -90 -90 -90 -90 -90
kHz
TreselectionEUTRAN s 0 0 0 0
Snonintrasearch dB 62 62 62 62
Propagation Condition AWGN AWGN AWGN AWGN
Antenna Configuration 1x2 1x2 1x2 1x2
Timing offset to Cell 1 - 3ms 3ms 3ms
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power
for to be fulfilled.
Note 3: Es/Iot and RSRP levels have been derived from other parameters for information purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 604 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.2.11.2 Test Requirements
The cell reselection delay is defined as the time from the beginning of a relevant time period, to the moment when the
UE camps on the target cell, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on the target cell.
The reselection delays shall meet the requirements in table A.4.2.11.2-1
Table A.4.2.11.2-1 : Reselection delay requirements
Time phase Target cell Requirement for reselection delay (seconds)
T1 Cell 2 (normal performance group) 20.5
T2 Cell 3 (reduced performance group) 193.3
T3 Cell 4 (reduced performance group) 193.3
T4 Cell 1 (normal performance group) 20.5
NOTE: The cell re-selection delay to a normal performance group cell can be expressed as: Kcarrier,normal *
Tevaluate,E-UTRAN_Inter, + TSI , and to a reduced performance group cell can be expressed as: 6* Kcarrier,reduced *
Tevaluate,E-UTRAN_Inter, + TSI,
This gives a total of 20.48 s for normal performance group reselection and 193.28 s for reduced performance group
reselection, allow 20.5 s for normal performance group and 193.3 s for reduced performance group in the test case. At
least 90% of reselections to the reduced performance group shall be within the required time, and at least 90% of
reselections to the normal performance group shall be within the required time, with a successful reselection counted if
it is within the required time regardless of the carrier frequencies involved.
A.4.2.12 E-UTRAN FDD – FDD Intra frequency case for Cat-M1 UE in normal
coverage
A.4.2.12.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD intra frequency cell reselection requirements for category M1
UE in normal coverage specified in clause 4.2.2.3.
The test scenario comprises of 1 E-UTRA FDD carrier and 2 cells as given in tables A.4.2.12.1-1 and A.4.2.12.1-2. The
test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Only Cell 1 is already
identified by the UE prior to the start of the test, i.e. Cell 2 is not identified by the UE prior to the start of the test. Cell 1
and Cell 2 belong to different tracking areas. Furthermore, UE has not registered with network for the tracking area
containing Cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 605 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.12.1-1: General test parameters for FDD intra frequency cell reselection test case for Cat-
M1 UE in normal coverage
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is used.
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH Configuration PRACH_2CE Refer to A.3.16
DRX cycle length s 1.28 The value shall be used for all cells in the
test.
T1 s >7 During T1, Cell 2 shall be powered off, and
during the off time the physical cell identity
shall be changed, The intention is to
ensure that Cell 2 has not been detected
by the UE prior to the start of period T2
T2 s 40 T2 need to be defined so that cell re-
selection reaction time is taken into
account.
T3 s 15 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 606 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.12.1-2: Cell specific test parameters for FDD intra frequency cell reselection test case for
Cat-M1 UE in normal coverage
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Patterns OP.2 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_
reselection_quality_me RSRP RSRP
asurement
N oc Note2 dBm/15 kHz -98
dB 16 12 16 -infinity 16 12
Ês N oc
dB 16 -4.11 2.79 -infinity 2.79 -4.11
Ê s I ot
RSRP Note3 dBm/15 kHz -82 -86 -82 -infinity -82 -86
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.4.2.12.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 34 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on Cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 1.
The cell re-selection delay to an already detected cell shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 607 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI-EUTRA-M1-
NC, and to an already detected cell can be expressed as: Tevaluate,EUTRAN_Intra + TSI-EUTRA-M1-NC,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.3-1 in clause 4.2.2.3
Tevaluate,EUTRAN_Intra See Table 4.2.2.3-1 in clause 4.2.2.3
TSI-EUTRA-M1-NC Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 33.28 s, allow 34 s for the cell re-selection delay to a newly detectable cell and 7.68 s, allow 8 s for
the cell re-selection delay to an already detected cell in the test case.
A.4.2.13 E-UTRAN HD – FDD Intra frequency case for Cat-M1 UE in normal
coverage
A.4.2.13.1 Test Purpose and Environment
This test is to verify the requirement for the HD-FDD intra frequency cell reselection requirements for Cat-M1 UE
specified in clause 4.2.2.3.
The test scenario comprises of 1 E-UTRA carrier and 2 cells as given in tables A.4.2.13.1-1 and A.4.2.13.1-2. The test
consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Only Cell 1 is already
identified by the UE prior to the start of the test, i.e. Cell 2 is not identified by the UE prior to the start of the test. Cell 1
and Cell 2 belong to different tracking areas. Furthermore, UE has not registered with network for the tracking area
containing Cell 2.
Table A.4.2.13.1-1: General test parameters for HD-FDD intra frequency cell reselection test case for
Cat-M1 UE in normal coverage
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one carrier frequency is used.
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH Configuration PRACH_2CE Refer to A.3.16
DRX cycle length s 1.28 The value shall be used for all cells in the
test.
T1 s >7 During T1, Cell 2 shall be powered off, and
during the off time the physical cell identity
shall be changed, The intention is to
ensure that Cell 2 has not been detected
by the UE prior to the start of period T2
T2 s 40 T2 need to be defined so that cell re-
selection reaction time is taken into
account.
T3 s 15 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 608 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.13.1-2: Cell specific test parameters for HD-FDD intra frequency cell reselection test case
for Cat-M1 UE in normal coverage
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Patterns OP.2 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_
reselection_quality_me RSRP RSRP
asurement
N oc Note2 dBm/15 kHz -98
dB 16 12 16 -infinity 16 12
Ês N oc
dB 16 -4.11 2.79 -infinity 2.79 -4.11
Ê s I ot
RSRP Note3 dBm/15 kHz -82 -86 -82 -infinity -82 -85
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.4.2.13.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 34 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on Cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 1.
The cell re-selection delay to an already detected cell shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 609 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI-EUTRA-M1-
NC, and to an already detected cell can be expressed as: Tevaluate,EUTRAN_Intra + TSI-EUTRA-M1-NC,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.3-1 in clause 4.2.2.3
Tevaluate,EUTRAN_Intra See Table 4.2.2.3-1 in clause 4.2.2.3
TSI-EUTRA-M1-NC Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 33.28 s, allow 34 s for the cell re-selection delay to a newly detectable cell and 7.68 s, allow 8 s for
the cell re-selection delay to an already detected cell in the test case.
A.4.2.14 E-UTRAN TDD – TDD Intra frequency case for Cat-M1 UE in normal
coverage
A.4.2.14.1 Test Purpose and Environment
This test is to verify the requirement for the TDD intra frequency cell reselection requirements for Cat-M1 UE specified
in clause 4.2.2.3.
The test scenario comprises of 1 E-UTRA TDD carrier and 2 cells as given in tables A.4.2.14.1-1 and A.4.2.14.1-2. The
test consists of three successive time periods, with time duration of T1, T2, and T3 respectively. Only cell 1 is already
identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to different tracking areas. Furthermore, UE
has not registered with network for the tracking area containing cell 2.
Table A.4.2.14.1-1: General test parameters for TDD intra frequency cell re-selection test case for Cat-
M1 UE
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is used.
Access Barring Information - Not Sent No additional delays in random access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
PRACH Configuration PRACH_2CE Refer to A.3.16
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s >7 During T1, Cell 2 shall be powered off, and during
the off time the physical cell identity shall be
changed, The intention is to ensure that Cell 2 has
not been detected by the UE prior to the start of
period T2
T2 s 40 T2 need to be defined so that cell re-selection
reaction time is taken into account.
T3 s 15 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 610 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.14.1-2: Cell specific test parameters for TDD intra frequency cell re-selection test case for
Cat-M1 UE in AWGN in normal coverage
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Patterns OP.2 TDD OP.2 TDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_
reselection_quality_me RSRP RSRP
asurement
N oc Note2 dBm/15 kHz -98
dB 16 12 16 -infinity 16 12
Ês N oc
dB 16 -4.11 2.79 -infinity 2.79 -4.11
Ê s I ot
RSRP Note3 dBm/15 kHz -82 -86 -82 -infinity -82 -86
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.4.2.14.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 34 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on cell 1.
The cell re-selection delay shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 611 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI-EUTRA-M1-
NC, and to an already detected cell can be expressed as: Tevaluate, E-UTRAN_ intra + TSI-EUTRA-M1-NC,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.3-1 in clause 4.2.2.3
Tevaluate,EUTRAN_ intra See Table 4.2.2.3-1 in clause 4.2.2.3
TSI-EUTRA-M1-NC Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 33.28 s, allow 34 s for the cell re-selection delay to a newly detectable cell and 7.68 s, allow 8 s for
the cell re-selection delay to an already detected cell in the test case.
A.4.2.15 E-UTRAN FDD – FDD Intra frequency case for Cat-M1 UE in
enhanced coverage
A.4.2.15.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD intra frequency cell reselection requirements for category M1
UE in enhanced coverage specified in clause 4.2.2.11.
The test scenario comprises of 1 E-UTRA FDD carrier and 2 cells as given in tables A.4.2.15.1-1 and A.4.2.15.1-2. The
test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Only Cell 1 is already
identified by the UE prior to the start of the test, i.e. Cell 2 is not identified by the UE prior to the start of the test. Cell 1
and Cell 2 belong to different tracking areas. Furthermore, UE has not registered with network for the tracking area
containing Cell 2.
Table A.4.2.15.1-1: General test parameters for FDD intra frequency cell reselection test case for Cat-
M1 UE in enhanced coverage
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is used.
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH Parameters PRACH_4CE Refer to A.3.16
DRX cycle length s 0.64 The value shall be used for all cells in the
test.
T1 s >7 During T1, Cell 2 shall be powered off, and
during the off time the physical cell identity
shall be changed, The intention is to
ensure that Cell 2 has not been detected
by the UE prior to the start of period T2
T2 s ≤340 T2 need to be defined so that cell re-
selection reaction time is taken into
account.
T3 s 20 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 612 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.15.1-2: Cell specific test parameters for FDD intra frequency cell reselection test case for
Cat-M1 UE in enhanced coverage
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Patterns OP.2 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_
reselection_quality_me RSRP RSRP
asurement
N oc Note2 dBm/15 kHz -98
dB -7 -12 -7 -infinity -7 -12
Ês N oc
dB -7 -12.79 -7.27 -infinity -7.27 -12.79
Ê s I ot
RSRP Note3 dBm/15 kHz -105 -110 -105 -infinity -105 -110
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.4.2.15.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 338 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on Cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 1.
The cell re-selection delay to an already detected cell shall be less than 18 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 613 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI, and to
an already detected cell can be expressed as: Tevaluate,EUTRAN_Intra + TSI,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.11-1 in clause 4.2.2.11
Tevaluate,EUTRAN_Intra See Table 4.2.2.11-1 in clause 4.2.2.11
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 6400 ms is assumed in this test case.
This gives a total of 337.36 s, allow 338 s for the cell re-selection delay to a newly detectable cell and 17.36 s, allow 18
s for the cell re-selection delay to an already detected cell in the test case.
A.4.2.16 E-UTRAN HD – FDD Intra frequency case for Cat-M1 UE in
enhanced coverage
A.4.2.16.1 Test Purpose and Environment
This test is to verify the requirement for the HD-FDD intra frequency cell reselection requirements for Cat-M1 UE
specified in clause 4.2.2.11.
The test scenario comprises of 1 E-UTRA carrier and 2 cells as given in tables A.4.2.16.1-1 and A.4.2.16.1-2. The test
consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Only Cell 1 is already
identified by the UE prior to the start of the test, i.e. Cell 2 is not identified by the UE prior to the start of the test. Cell 1
and Cell 2 belong to different tracking areas. Furthermore, UE has not registered with network for the tracking area
containing Cell 2.
Table A.4.2.16.1-1: General test parameters for HD-FDD intra frequency cell reselection test case for
Cat-M1 UE in enhanced coverage
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one carrier frequency is used.
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH Parameters PRACH_4CE Refer to A.3.16
DRX cycle length s 0.64 The value shall be used for all cells in the
test.
T1 s >7 During T1, Cell 2 shall be powered off, and
during the off time the physical cell identity
shall be changed, The intention is to
ensure that Cell 2 has not been detected
by the UE prior to the start of period T2
T2 s ≤340 T2 need to be defined so that cell re-
selection reaction time is taken into
account.
T3 s ≤20 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 614 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.16.1-2: Cell specific test parameters for HD-FDD intra frequency cell reselection test case
for Cat-M1 UE in enhanced coverage
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Patterns OP.2 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_
reselection_quality_me RSRP RSRP
asurement
N oc Note2 dBm/15 kHz -98
dB -7 -12 -7 -infinity -7 -12
Ês N oc
dB -7 -12.79 -7.27 -infinity -7.27 -12.79
Ê s I ot
RSRP Note3 dBm/15 kHz -105 -110 -105 -infinity -105 -110
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.4.2.16.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 338 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on Cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 1.
The cell re-selection delay to an already detected cell shall be less than 18 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 615 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI, and to
an already detected cell can be expressed as: Tevaluate,EUTRAN_Intra + TSI,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.11-1 in clause 4.2.2.11
Tevaluate,EUTRAN_Intra See Table 4.2.2.11-1 in clause 4.2.2.11
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 6400 ms is assumed in this test case.
This gives a total of 337.36 s, allow 338 s for the cell re-selection delay to a newly detectable cell and 17.36 s, allow 18
s for the cell re-selection delay to an already detected cell in the test case.
A.4.2.17 E-UTRAN TDD – TDD Intra frequency case for Cat-M1 UE in
enhanced coverage
A.4.2.17.1 Test Purpose and Environment
This test is to verify the requirement for the TDD intra frequency cell reselection requirements for Cat-M1 UE specified
in clause 4.2.2.11.
The test scenario comprises of 1 E-UTRA TDD carrier and 2 cells as given in tables A.4.2.17.1-1 and A.4.2.17.1-2. The
test consists of three successive time periods, with time duration of T1, T2, and T3 respectively. Only cell 1 is already
identified by the UE prior to the start of the test. Cell 1 and cell 2 belong to different tracking areas. Furthermore, UE
has not registered with network for the tracking area containing cell 2.
Table A.4.2.17.1-1: General test parameters for TDD intra frequency cell re-selection test case for Cat-
M1 UE
Parameter Unit Value Comment
Initial Active cell Cell1
condition Neighbour cells Cell2
T2 end Active cell Cell2
condition Neighbour cells Cell1
Final Visited cell Cell1
condition
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is used.
Access Barring Information - Not Sent No additional delays in random access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
PRACH Parameters PRACH_4CE Refer to A.3.16
DRX cycle length s 0.64 The value shall be used for all cells in the test.
T1 s >7 During T1, Cell 2 shall be powered off, and during
the off time the physical cell identity shall be
changed, The intention is to ensure that Cell 2 has
not been detected by the UE prior to the start of
period T2
T2 s ≤340 T2 need to be defined so that cell re-selection
reaction time is taken into account.
T3 s ≤20 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 616 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.17.1-2: Cell specific test parameters for TDD intra frequency cell re-selection test case for
Cat-M1 UE in AWGN in enhanced coverage
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Patterns OP.2 TDD OP.2 TDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_
reselection_quality_me RSRP RSRP
asurement
N oc Note2 dBm/15 kHz -98
dB -7 -12 -7 -infinity -7 -12
Ês N oc
dB -7 -12.79 -7.27 -infinity -7.27 -12.79
Ê s I ot
RSRP Note3 dBm/15 kHz -105 -110 -105 -infinity -105 -110
Treselection s 0 0 0 0 0 0
Sintrasearch dB Not sent Not sent
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.4.2.17.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 2.
The cell re-selection delay to a newly detectable cell shall be less than 338 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on Cell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on Cell 1.
The cell re-selection delay to an already detected cell shall be less than 18 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 617 ETSI TS 136 133 V14.3.0 (2017-04)
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,EUTRAN_Intra + TSI, and to
an already detected cell can be expressed as: Tevaluate,EUTRAN_Intra + TSI,
Where:
Tdetect,EUTRAN_Intra See Table 4.2.2.11-1 in clause 4.2.2.11
Tevaluate,EUTRAN_Intra See Table 4.2.2.11-1 in clause 4.2.2.11
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 6400 ms is assumed in this test case.
This gives a total of 337.36 s, allow 338 s for the cell re-selection delay to a newly detectable cell and 17.36 s, allow 18
s for the cell re-selection delay to an already detected cell in the test case.
A.4.2.18 HD – FDD Intra frequency case for UE Category NB1 In-Band mode
in normal coverage
A.4.2.18.1 Test Purpose and Environment
This test is to verify the requirement for the HD-FDD intra frequency cell reselection requirements for Cat-NB1 UE
specified in clause 4.6.2.2.
The test scenario comprises of 1 E-UTRA carrier with one ecell and one NB-IoT carrier with 2 ncells of different
physical cell ID, as given in tables A.4.2.18.1-1, A.4.2.18.1-2 and A.4.2.18.1-3. The test consists of three successive
time periods, with time duration of T1, T2 and T3 respectively. Only nCell1 is already identified by the UE prior to the
start of the test, i.e. nCell 2 is not identified. nCell 1 and nCell 2 belong to different tracking areas. Furthermore, UE has
not registered with network for the tracking area containing nCell 2.
Table A.4.2.18.1-1: General test parameters for HD-FDD intra frequency cell reselection test case for
Cat-NB1 UE in normal coverage
Parameter Unit Value Comment
NB-IOT operational mode In-band
Initial Active cell nCell1
condition Neighbour cells eCell1, nCell2
T2 end Active cell nCell2
condition Neighbour cells eCell1, nCell1
Final Visited cell nCell1
condition
E-UTRA RF Channel Number 1 One carrier frequency is used for eCell.
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH Configuration 1 Refer to A.3.17
DRX cycle length s 1.28 The value shall be used for all cells in the
test.
T1 s >7 During T1, nCell2 shall be powered off, and
during the off time the physical cell identity
shall be changed. The intention is to
ensure that nCell2 has not been detected
by the UE prior to the start of period T2
T2 s 60 T2 is defined so that cell re-selection time
is taken into account.
T3 s 15 T3 is defined so that cell re-selection time
is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 618 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.18.1-2: nCell 1, nCell 2 specific test parameters for HD-FDD intra frequency cell reselection
test case for Cat-NB1 UE in normal coverage
Parameter Unit nCell 1 nCell 2
T1 T2 T3 T1 T2 T3
BW channel kHz 180 180
PRB location within eCell - 30 30
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB
NSSS_RA dB
NPDCCH_RA dB
-3 -3
NPDCCH_RB dB
NPDSCH_RA dB
NPDSCH_RB dB
NOCNG_RANote 1 dB
NOCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140 -140 -140 -140
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_ NRSRP NRSRP
reselection_quality_meas
urement
N oc dBm/15 kHz Specified in Table A.4.2.18.1-3
Ê s N oc dB 17 13 17 -infinity 17 13
Ê s I ot Note2 dB 17 -4.09 3.79 -infinity 3.79 -4.09
NRSRP Note2 dBm/15 kHz -81 -85 -81 -infinity -81 -85
Treselection s 0 0 0 0 0 0
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to nCell 1 ms - 3
Note 1: NOCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Es/Iot and NRSRP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 619 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.18.1-3: eCell 1 specific test parameters for HD-FDD intra frequency cell reselection test
case for Cat-NB1 UE in normal coverage
Parameter Unit eCell 1
T1 T2 T3
BW channel MHz 10
NOCNG Pattern - NOP.1 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PDCCH_RA dB
0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140
Pcompensation dB 0 0 0
Qhysts dB 0 0 0
Qoffsets, n dB 0 0 0
N oc Note2 dBm/15 kHz -98
Ê s N oc dB 3 3 3
Treselection s 0 0 0
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N oc .
subcarriers and time and shall be modelled as AWGN of appropriate power
Note 3: Void
A.4.2.18.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on nCell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on nCell 2.
The cell re-selection delay to a newly detectable cell shall be less than 56.12 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on nCell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on nCell 1.
The cell re-selection delay to an already detected cell shall be less than 11.62 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,NB_Intra_NB-IoT-NC + TSI, and
to an already detected cell can be expressed as: Tevaluate, NB_intra_NB-IoT-NC + TSI,
Where:
Tdetect,NB_Intra_NB-IoT-NC See Table 4.6.2.2-1 in clause 4.6.2.2
Tevaluate, NB_intra_NB-IoT-NC See Table 4.6.2.2-1 in clause 4.6.2.2
TSI Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 5120 ms is assumed in this test case.
This gives a total of 56.12s for the cell re-selection delay to a newly detectable cell and 11.62 s for the cell re-selection
delay to an already detected cell in the test case.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 620 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.2.19 HD – FDD Intra frequency case for UE Category NB1 In-Band mode
in enhanced coverage
A.4.2.19.1 Test Purpose and Environment
This test is to verify the requirement for the HD-FDD intra frequency cell reselection requirements for Cat-NB1 UE
specified in clause 4.6.2.2.
The test scenario comprises of 1 E-UTRA carrier and a total of 3 cells as given in tables A.4.2.19.1-1, A.4.2.19.1-2 and
A.4.2.19.1-3. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Only
nCell1 is already identified by the UE prior to the start of the test, i.e. nCell 2 is not identified. nCell 1 and nCell 2
belong to different tracking areas. Furthermore, UE has not registered with network for the tracking area containing
nCell 2.
Table A.4.2.19.1-1: General test parameters for HD-FDD intra frequency cell reselection test case for
Cat-NB1 UE in enhanced coverage
Parameter Unit Value Comment
NB-IOT operational mode In-band
Initial Active cell nCell1
condition Neighbour cells eCell1, nCell2
T2 end Active cell nCell2
condition Neighbour cells eCell1, nCell2
Final Visited cell nCell1
condition
E-UTRA RF Channel Number 1 One carrier frequency is used for eCell.
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH Configuration 1 Refer to A.3.17
DRX cycle length s 1.28 The value shall be used for all cells in the
test.
T1 s >7 During T1, nCell2 shall be powered off, and
during the off time the physical cell identity
shall be changed. The intention is to
ensure that nCell2 has not been detected
by the UE prior to the start of period T2
T2 s ≤534 T2 is defined so that cell re-selection time
is taken into account.
T3 s ≤15 T3 is defined so that cell re-selection time
is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 621 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.19.1-2: nCell 1, nCell 2 specific test parameters for HD-FDD intra frequency cell reselection
test case for Cat-NB1 UE in enhanced coverage
nCell 1 nCell 2
T1 T2 T3 T1 T2 T3
BW channel kHz 180 180
PRB location within eCell - 30 30
NOCNG Patterns - NOP.1 FDD NOP.1 FDD
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB
NSSS_RA dB
NPDCCH_RA dB
-3 -3
NPDCCH_RB dB
NPDSCH_RA dB
NPDSCH_RB dB
NOCNG_RANote 1 dB
NOCNG_RBNote 1 dB
Qrxlevmin dBm -156 -156 -156 -156 -156 -156
Pcompensation dB 0 0 0 0 0 0
Qhysts dB 0 0 0 0 0 0
Qoffsets, n dB 0 0 0 0 0 0
Cell_selection_and_ NRSRP NRSRP
reselection_quality_meas
urement
N oc dBm/15 kHz Specified in Table A.4.2.19.1-3
Ê s N oc dB -9 -9 -0.7 -infinity -0.7 -9
Ê s I ot Note2 dB -9 -11.67 -1.21 -infinity -1.21 -11.67
NRSRP Note2 dBm/15 kHz -107 -107 -98.7 -infinity -98.7 -107
Treselection s 0 0 0 0 0 0
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to nCell 1 ms - 3
Note 1: NOCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Es/Iot and NRSRP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 622 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.2.19.1-3: eCell 1 specific test parameters for HD-FDD intra frequency cell reselection test
case for Cat-NB1 UE in enhanced coverage
eCell 1
T1 T2 T3
BW channel MHz 10
OCNG Pattern - **
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PDCCH_RA dB
-3
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140 -140 -140
Pcompensation dB 0 0 0
Qhysts dB 0 0 0
Qoffsets, n dB 0 0 0
N oc dBm/15 kHz -98
Ê s N oc dB 3 3 3
Treselection s 0 0 0
Propagation Condition AWGN
Antenna Configuration 2x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N oc .
subcarriers and time and shall be modelled as AWGN of appropriate power
Note 3: Void
A.4.2.19.2 Test Requirements
The cell reselection delay to a newly detectable cell is defined as the time from the beginning of time period T2, to the
moment when the UE camps on nCell 2, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on nCell 2.
The cell re-selection delay to a newly detectable cell shall be less than 534 s.
The cell reselection delay to an already detected cell is defined as the time from the beginning of time period T3, to the
moment when the UE camps on nCell 1, and starts to send preambles on the PRACH for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on nCell 1.
The cell re-selection delay to an already detected cell shall be less than 8 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to a newly detectable cell can be expressed as: Tdetect,NB_Intra_NB-IoT-NC + TSI, and to an
already detected cell can be expressed as: Tevaluate, NB_intra_NB-IoT-NC + TSI,
Where:
Tdetect,NB_Intra_NB-IoT-NC See Table 4.6.2.2-1 in clause 4.6.2.2
Tevaluate, NB_intra_NB-IoT-NC See Table 4.6.2.2-1 in clause 4.6.2.2
TSI Maximum repetition period of relevant system info blocks that needs to be received
by the UE to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 533.28 s, allow 534 s for the cell re-selection delay to a newly detectable cell and 7.78 s, allow 8 s
for the cell re-selection delay to an already detected cell in the test case.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 623 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3 E-UTRAN to UTRAN Cell Re-Selection
A.4.3.1 E-UTRAN FDD – UTRAN FDD:
A.4.3.1.1 EUTRA FDD-UTRA FDD cell reselection: UTRA FDD is of higher priority
A.4.3.1.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRA FDD- UTRA FDD inter-RAT cell reselection requirements
specified in clause 4.2.2.5 when the UTRA cell is of higher priority.
The test scenario comprises of one E-UTRA FDD and one UTRA FDD cells as given in tables A.4.3.1.1.1-1,
A.4.3.1.1.1-2 and A.4.3.1.1.1-3. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively. E-UTRA cell 1 is already identified by the UE prior to the start of the test. Cell 2 is of higher priority than
cell 1.
Table A.4.3.1.1.1-1: General test parameters for E-UTRA FDD- higher priority UTRA FDD inter RAT
cell re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell 1 UE is on cell 1 in the initialisation phase, so that
condition reselection to cell 2 occurs during T2
T2 end Active cell Cell 2 UE shall perform reselection to cell 2 during T2
condition Neighbour cell Cell 1
T3 end Active cell Cell 1 UE shall perform reselection to cell 1 during T3
condition Neighbour cell Cell 2
E-UTRA PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
E_UTRA Access Barring - Not Sent No additional delays in random access
Information procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s >20 During T1, cell 2 shall be powered off, and
during the off time the primary scrambling code
shall be changed. The intention is to ensure that
cell 2 has not been detected by the UE prior to
the start of period T2.
T2 s 85 T2 needs to be defined so that cell re-selection
reaction time is taken into account.
T3 s 25 T3 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 624 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.1.1-2: Cell specific test parameters for cell 1(E-UTRA)
Parameter Unit Cell 1
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in
A.3.2.1.2 (OP.2 FDD) OP.2 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qqualmin for UTRA
dB -20
neighbour cell
Qrxlevmin for UTRA
dBm -115
neighbour cell
Qrxlevmin dBm -140
N oc dBm/15 kHz -98
RSRP dBm/15 KHz -84 -84 -84
dB 14 14 14
Ê s I ot
dB 14 14 14
Ês N oc
TreselectionEUTRAN S 0
Snonintrasearch dB 50
Threshx, high (Note 2) dB 40
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated
and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: This refers to the value of Threshx, high which is included in E-
UTRA system information, and is a threshold for the UTRA
target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 625 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.1.1-3: Cell specific test parameters for cell 2(UTRA)
Parameter Unit Cell 2 (UTRA)
T1 T2 T3
UTRA RF Channel Number Channel 2
CPICH_Ec/Ior dB -10
dB
PCCPCH_Ec/Ior -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
OCNS_Ec/Ior dB -0.941
Iˆor I oc dB -Infinity 11 -5
dBm/3,84
I oc MHz
-70
CPICH_Ec/Io dB -Infinity -10.33 -16.19
CPICH_RSCP dBm -Infinity -69 -85
Propagation Condition AWGN
Qqualmin dB -20
Qrxlevmin dBm -115
QrxlevminEUTRA dBm -140
UE_TXPWR_MAX_RACH dBm 21
Treselection s 0
Sprioritysearch1 dB 62
Sprioritysearch2 dB 0
Threshserving, low dB 36
Threshx, low (Note 1) dB 50
Note 1 : his refers to the value of Threshx, low which is included in UTRA
system information, and is a threshold for the E-UTRA target
cell
A.4.3.1.1.2 Test Requirements
The cell reselection delay to higher priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message on cell 2.
The cell re-selection delay to higher priority shall be less than 81 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to higher priority cell can be expressed as: Thigher_priority_search +TevaluateUTRA_FDD +
TSI-UTRA
Where:
Thigher_priority_search See clause 4.2.2; 60s is assumed in this test case
TevaluateUTRA-FDD See Table 4.2.2.5.1-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 80.48 s for higher priority cell search, allow 81 s for higher priority cell reselection in the test case.
A.4.3.1.2 EUTRA FDD-UTRA FDD cell reselection: UTRA FDD is of lower priority
A.4.3.1.2.1 Test Purpose and Environment
This test is to verify the requirement for the EUTRA FDD- UTRA FDD inter-RAT cell reselection requirements
specified in clause 4.2.2.5.1 when the UTRA cell is of lower priority.
The test scenario comprises of one UTRA FDD and one E-UTRA FDD cells as given in tables A.4.3.1.2.1-1,
A.4.3.1.2.1-2 and A.4.3.1.2.1-3. The test consists of two successive time periods, with time duration of T1 and T2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 626 ETSI TS 136 133 V14.3.0 (2017-04)
respectively. Both E-UTRA cell 1 and UTRA cell 2 are already identified by the UE prior to the start of the test. Cell 2
is of lower priority than cell 1.
Table A.4.3.1.2.1-1: General test parameters for EUTRA FDD- lower priority UTRA FDD inter RAT cell
re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell1 E-UTRAN cell
condition
T1 end Active cells Cell1 UE shall perform reselection to cell 1 during T1
condition for subsequent iterations of the test
Neighbour cell Cell2
T2 end Active cell Cell2 UE shall perform reselection to cell 2 during T2
condition Neighbour cell Cell1
E-UTRA PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
E_UTRA Access Barring - Not Sent No additional delays in random access
Information procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 85 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s 25 T2 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 627 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.2.1-2: Cell specific test parameters for cell 1 (E-UTRA)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in
A.3.2.1.2 (OP.2 FDD) OP.2 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qqualmin for UTRA
dB -20
neighbour cell
Qrxlevmin for UTRA
dBm -115
neighbour cell
Qrxlevmin dBm -140
N oc dBm/15 kHz -98
RSRP dBm/15 KHz -86 -102
dB 12 -4
Ê s I ot
dB 12 -4
Ês N oc
TreselectionEUTRAN s 0
Snonintrasearch dB Not sent
Threshserving, low dB 44
Threshx, low (Note 2) dB 42
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated
and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2 : This refers to the value of Threshx, low which is included in E-
UTRA system information, and is a threshold for the UTRA
target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 628 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.2.1-3: Cell specific test parameters for cell 2 (UTRA)
Parameter Unit Cell 2 (UTRA)
T1 T2
UTRA RF Channel Number Channel 2
CPICH_Ec/Ior dB -10
dB
PCCPCH_Ec/Ior -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
OCNS_Ec/Ior dB -0.941
Iˆor I oc dB 13 13
dBm/3,84
I oc MHz
-70
CPICH_Ec/Io dB -10.21 -10.21
CPICH_RSCP dBm -67 -67
Propagation Condition AWGN
Qqualmin dB -20
Qrxlevmin dBm -115
QrxlevminEUTRA dBm -140
UE_TXPWR_MAX_RACH dBm 21
Treselection s 0
Sprioritysearch1 dB 42
Sprioritysearch2 dB 0
Threshx, high (Note 1) dB 48
Note 1 : This refers to the value of Threshx, high which is included
in UTRA system information, and is a threshold for the
E-UTRA target cell
A.4.3.1.2.2 Test Requirements
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message on cell 2.
The cell re-selection delay to lower priority shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateUTRA_FDD + TSI-UTRA
Where:
TevaluateUTRA-FDD See Table 4.2.2.5.1-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for lower priority cell reselection, allow 21 s.
A.4.3.1.3 EUTRA FDD-UTRA FDD cell reselection in fading propagation conditions:
UTRA FDD is of lower priority
A.4.3.1.3.1 Test Purpose and Environment
This test is to verify the requirement for the EUTRA FDD- UTRA FDD inter-RAT cell reselection requirements
specified in clause 4.2.2.5.1 when the UTRA cell is of lower priority, and to verify the robustness of the UE
measurement filtering in a fading environment. The E-UTRA cell is in fading propagation conditions and the UTRA
cell is in AWGN propagation conditions.
The test scenario comprises of one UTRA FDD and one E-UTRA FDD cells as given in tables A.4.3.1.3.1-1,
A.4.3.1.3.1-2 and A.4.3.1.3.1-3. The test consists of four successive time periods, with time duration of T1 T2, T3 and
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 629 ETSI TS 136 133 V14.3.0 (2017-04)
T4 respectively. Both E-UTRA cell 1 and UTRA cell 2 are already identified by the UE prior to the start of the test. Cell
2 is of lower priority than cell 1.
Table A.4.3.1.3.1-1: General test parameters for EUTRA FDD- lower priority UTRA FDD inter RAT cell
re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell1 E-UTRAN cell
condition
T1 end Active cells Cell1 UE shall perform reselection to cell 1 during T1
condition for subsequent iterations of the test
Neighbour cell Cell2
T3 end Active cell Cell2 UE shall perform reselection to cell 2 during T3
condition Neighbour cell Cell1
E-UTRA PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
E_UTRA Access Barring - Not Sent No additional delays in random access
Information procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s <85 T1 need to be defined so that cell re-selection
reaction time is taken into account. T1 is
terminated when the UE starts to send
preambles to cell 1
T2 s 64 The start of T2 is defined as the time when the
UE starts to send PRACH preambles to cell 1
T3 s <25 T3 need to be defined so that cell re-selection
reaction time is taken into account. T3 is
terminated when the UE starts to send
preambles to cell 2
T4 s 64 The start of T4 is defined as the time when the
UE starts to send PRACH preambles to cell 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 630 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.3.1-2: Cell specific test parameters for cell 1 (E-UTRA)
Parameter Unit Cell 1
T1 T2 T3 T4
E-UTRA RF Channel number 1
BW channel MHz 10
Correlation Matrix and Antenna 1x2 Low
Configuration
OCNG Patterns defined in
A.3.2.1.2 (OP.2 FDD) OP.2 FDD
PSS_RA dB 0
SSS_RA dB 0
PCFICH_RB dB 0
PHICH_RA dB 0
PHICH_RB dB 0
PDCCH_RA dB 0
PDCCH_RB dB 0
PDSCH_RA dB 0
PDSCH_RB dB 0
OCNG_RANote 1 dB 0
OCNG_RBNote 1 dB 0
Qqualmin for UTRA neighbour
dB -20
cell
Qrxlevmin for UTRA neighbour
dBm -115
cell
Qrxlevmin dBm -140
N oc dBm/15 -104
kHz
RSRP dBm/15 -82 -82 -107 -107
KHz
dB 22 22 -3 -3
Ê s I ot
dB 22 22 -3 -3
Ês N oc
TreselectionEUTRAN s 0
Snonintrasearch dB Not sent
Threshserving, low dB 44
Threshx, low (Note 2) dB 42
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: This refers to the value of Threshx, low which is included in E-UTRA system
information, and is a threshold for the UTRA target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 631 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.3.1-3: Cell specific test parameters for cell 2 (UTRA)
Parameter Unit Cell 2 (UTRA)
T1 T2 T3 T4
UTRA RF Channel Number Channel 2
CPICH_Ec/Ior dB -10
dB
PCCPCH_Ec/Ior -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
OCNS_Ec/Ior dB -0.941
Iˆor I oc dB 13 13 13 13
dBm/3,84
I oc MHz
-70
CPICH_Ec/Io dB -10.21 -10.21 -10.21 -10.21
CPICH_RSCP dBm -67 -67 -67 -67
Propagation Condition AWGN
Qqualmin dB -20
Qrxlevmin dBm -115
QrxlevminEUTRA dBm -140
UE_TXPWR_MAX_RACH dBm 21
Treselection s 0
Sprioritysearch1 dB 42
Sprioritysearch2 dB 0
Threshx, high (Note 1) dB 44
Note 1 : This refers to the value of Threshx, high which is included in UTRA system
information, and is a threshold for the E-UTRA target cell
A.4.3.1.3.2 Test Requirements
The probability of reselection from cell 1to cell 2 during T2 observed during testing shall be less than 10%
The probability of reselection from cell 2 to cell 1 during T4 observed during testing shall be less than 10%
The cell reselection delay to lower priority is defined as the time from the beginning of time period T3, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message on cell 2. In order to evaluate reselection delay, the system simulator first needs to verify that the
UE is camped on cell 1 at the start of T3
The cell re-selection delay to lower priority shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateUTRA_FDD + TSI-UTRA
Where:
TevaluateUTRA-FDD See Table 4.2.2.5.1-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for lower priority cell reselection, allow 21 s.
A.4.3.1.4 EUTRA FDD-UTRA FDD cell reselection: UTRA FDD is of lower priority for
5MHz bandwidth
A.4.3.1.4.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.4.3.1.2.1
The parameters of this test are the same as defined in Subclause A.4.3.1.2.1 except that the values of the parameters in
the Table A.4.3.1.4.1-2 will replace the values of the corresponding parameters in A.4.3.1.2.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 632 ETSI TS 136 133 V14.3.0 (2017-04)
This is according to the principle defined in section A.3.7.2.
Table A.4.3.1.4.1-2: Cell specific test parameters for cell 1 (E-UTRA) for 5MHz bandwidth
Parameter Unit Cell 1
T1 T2
BW channel MHz 5
OCNG Patterns defined in OP.16 FDD
A.3.2.1.16 (OP.16 FDD)
Note 1: See Table A.4.3.1.2.1-2 for the other parameters.
A.4.3.1.4.2 Test Requirements
The test requirements defined in section A.4.3.1.2.1 shall apply to this test case.
A.4.3.1.5 Idle mode FDD to UTRA FDD interRAT reselection
A.4.3.1.5.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRA FDD-UTRA FDD inter-RAT cell reselection requirements for
increased UE carrier monitoring specified in clause 4.2.2.4.
The test scenario comprises of indicating 8 UTRA FDD interfrequency cells on 6 different carriers in the neighbour list
of cell 1 as given in table A.4.3.1.5-1 and cells 2 and 3 as given in table A.4.3.1.5-2. Each repetition of the test consists
of five successive time periods, with time duration of T0, T1, T2, T3 and T4 respectively. In the initialisation phase and
at the start of each repetition of T0, the test equipment provides signals for cell 1 (serving cell), and selects frequencies
for cells 2 and 3 which are chosen from the 6 inter-RAT layers which are configured in the UE neighbour cell list as
described in general and cell specific parameters. The neighbour lists of cells 2 and 3 shall include the frequency of cell
1 in the normal performance group as well as the other frequencies configured to the UE in the test.
Cell 1, 2 and 3 are identified by the UE during time period T0. Cell 1, cell 2 and cell 3 all belong to different tracking
areas. Furthermore, UE has not registered with network for the tracking area containing cell 2 or 3. Cells 2 and 3 all
have lower absolute priority than cell 1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 633 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.5-1: General test parameters for E-UTRAN FDD- UTRAN FDD inter frequency cell re-
selection test case
Parameter Unit Value Comment
T0 Active cell Cell 1 T0 is repeated on each repetition of the
test. In T0 the test equipment selects
frequencies for cell 2 and 3, and then
time is allowed for the UE to identify the
neighbour cells. See cell specific
parameters for detailed settings.
T1 start condition Active cell Cell 1
T1 end condition Active cell Cell 2 UE shall perform reselection to cell 2
during T1
Neighbour cell Cell 1, cell 3
T2 end condition Active cell Cell 1 UE shall perform reselection to cell 1
during T2
Neighbour cell Cell 2, cell 3
T3 end condition Active cell Cell 3 UE shall perform reselection to cell 3
during T3
Neighbour cell Cell 1, cell 2
Active cell Cell 1 UE shall perform reselection to cell 1
T4 end condition
during T4
Neighbour cell Cell 2, cell 3
UE configured E-UTRA RF Channel 1 Serving cell and six UTRA FDD carrier
Number frequencies are used in the UE
neighbour cell list. Frequencies 5,6 and
7 are indicated to have reduced
performance
UE configured UTRA RF Channel 2,3,4,5,6,7
Number
Test eqipment configuration Cell 1 uses E-
UTRA RF
channel number
1
Cells 2,3,4 are
randomly
selected to use
different
frequencies
selected from
frequencies
2,3,4,5,6,7
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in
the test.
T0 s (test equipment Initialisation time need to be defined so
frequency that cell detection time is taken into
selection and account.
configuration
time) + 960
T1 s 25 T1 need to be defined so that cell re-
selection reaction time is taken into
account.
T2 s 25 T2 need to be defined so that cell re-
selection reaction time is taken into
account
T3 s 200 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
T4 s 25 T4 need to be defined so that cell re-
selection reaction time is taken into
account
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 634 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.5-2: Cell specific test parameters for E-UTRAN FDD- UTRAN FDD inter-RAT cell
reselection test case in AWGN cell 1 (E-UTRAN)
Parameter Unit Cell 1
T0 T1 T2 T3 T4
E-UTRA RF Channel 1
number
BW channel MHz 5MHz: NRB = 25
10MHz: NRB = 50
Io dBm/4. 59.0 64.5 59.0 64.5 59.0
5MHz(2 6 9 6 9 6
5RB)
dBm/9 56.0 61.5 56.0 61.5 56.0
Mhz 5 8 5 8 5
(50RB)
PDSCH parameters: OP.16 FDD (5MHz)
DL Reference OP.2 FDD (10MHz)
Measurement
Channel OP.10 TDD(5MHz)
OP.2 TDD (10MHz)
Time offset with 0
respect to cell1
PBCH RA dB 0
PBCH RB dB
PSS RA dB
SSS RA dB
PCFICH RB dB
PHICH RA dB
PHICH RB dB
PDCCH RA dB
PDCCH RB dB
PDSCH RA dB
PDSCH RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140
N oc dBm -98
Note 2
RSRP Note 3 dBm -84 -90 -84 -90 -84
Ê s I ot dB 14 8 14 8 14
Ê s N oc dB 14 8 14 8 14
TreselectionEUTRAN s 0
Snonintrasearch dB 62
Propagation AWGN
Condition
Note 1: OCNG shall be used such that the cell is fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: Interference from other cells and noise sources not specified
in the test is assumed to be constant over subcarriers and time and
shall be modelled as AWGN of appropriate power for to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 635 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.1.5-3: Cell specific test parameters for cells 2 and 3 (UTRA)
Cell 2 Cell 3
Parameter Unit
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
Randomly selected from 1, 2, 3 such Randomly selected from 4, 5, 6 such
UTRA RF Channel Number that cell 2 is in the normal that cell 3 is in the reduced
performance group performance group
CPICH_Ec/Ior dB -10 -10
dB -12 -12
PCCPCH_Ec/Ior
SCH_Ec/Ior dB -12 -12
PICH_Ec/Ior dB -15 -15
OCNS_Ec/Ior dB -0.941 0.941
Iˆor I oc dB -11 -5 -11 -11 -11 -11 -11 -11 -5 -11
dBm/3,84 -70 -70
I oc MHz
- - - - - - - - - -
CPICH_Ec/Io dB 10.3 16.1 10.3 10.3 10.3 10.3 10.3 10.3 16.1 10.3
3 9 3 3 3 3 3 3 9 3
CPICH_RSCP dBm -69 -85 -69 -69 -69 -69 -69 -69 -85 -69
Propagation Condition AWGN AWGN
Qqualmin dB -20 -20
Qrxlevmin dBm -115 -115
QrxlevminEUTRA dBm -140 -140
UE_TXPWR_MAX_RACH dBm 21 21
Treselection s 0 0
Sprioritysearch1 dB 62 62
Sprioritysearch2 dB 0 0
Threshserving, low dB 36 36
Threshx, low (Note 1) dB 50 50
A.4.3.1.5.2 Test Requirements
The cell reselection delay is defined as the time from the beginning of a relevant time period, to the moment when the
UE camps on the target cell, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on the target cell.
The reselection delays shall meet the requirements in table A.4.3.1.5.2-1
Table A.4.3.1.5.2-1
Time phase Target cell Requirement for reselection delay (seconds)
T0 Cell 1
T1 Cell 2 (normal performance group) 21
T2 Cell 1 (normal performance group) 8
T3 Cell 3 (reduced performance group) 148
T4 Cell 1 (normal performance group) 8
NOTE: The cell re-selection delay to a normal performance group cell can be expressed as: (NUTRA_carrier,normal) *
TevaluateUTRA_FDD + TSI-UTRA and to a reduced performance group cell can be expressed as: 6 *
NUTRA_carrier,reduced * TevaluateUTRA_FDD + TSI-UTRA.
Where:
TevaluateUTRA-FDD See Table 4.2.2.5.1-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for normal performance group reselection, allow 21 s, and gives a total of 147.6 s for
reduced performance group reselection, allow 148 s for reduced performance group in the test case. For reselections
back to cell 1 since only one frequency is configured, the requirement is Tevaluate,E-UTRAN_Inter, + TSI = 7.68s, allow 8s.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 636 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.2 E-UTRAN FDD – UTRAN TDD:
A.4.3.2.1 Test Purpose and Environment
A.4.3.2.1.1 Void
A.4.3.2.1.2 1.28Mcps TDD option
This test is to verify the requirement for the E-UTRA FDD to UTRA TDD inter-RAT cell reselection requirements
specified in clause 4.2.2.5.2 when the UTRA cell is of lower priority.
This test scenario comprised of 1 E-UTRA FDD serving cell (Cell 1), and 1 UTRA TDD cell (Cell 2) to be re-selected.
Test parameters are given in table A.4.3.2.1.2-1, A.4.3.2.1.2-2, and A.4.3.2.1.2-3. The test consists of two successive
time periods, with time duration of T1 and T2 respectively. Cell 2 is of lower priority than cell 1.
The ranking of the cells shall be made according to the cell reselection criteria specified in TS36.304.
Table A.4.3.2.1.2-1: General test parameters for E-UTRA FDD to UTRA (1.28 Mcps TDD OPTION) Cell
Re-selection
Parameter Unit Value Comment
Initial Active cell Cell1 E-UTRAN cell
condition
T1 end Active cell Cell1 UE shall perform reselection to cell 1 during T1 for
condition subsequent iterations of the test
Neighbour Cell2 1.28 Mcps TDD OPTION cell
cell
T2 end Active cell Cell2 UE shall perform reselection to cell 2 during T2
condition Neighbour Cell1 E-UTRA FDD cell
cell
CP length of cell 1 normal
E-UTRA PRACH 4 As specified in table 5.7.1-2 in TS 36.211
configuration
Time offset between cells 3 ms Asynchronous cells
Access Barring Information - Not No additional delays in random access procedure.
sent
Treselection s 0
DRX cycle length s 1,28
HCS Not
used
T1 s 85 T1 need to be defined so that cell re-selection reaction time
is taken into account.
T2 s 25
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 637 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.2.1.2-2: Cell specific test parameters for cell re-selection E-UTRA FDD to UTRA TDD test
case (cell 1)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
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
OCNG_RANote1 dB
OCNG_RBNote1 dB
Qrxlevmin dBm/15kHz -140 -140
N oc dBm/15kHz -98
RSRP dBm/15kHz -87 -101
Ê s I ot dB 11 -3
Snonintrasearch dB Not sent
Threshserving, low dB 46 (-94dBm)
Threshx, low (Note2) dB 24 (-79dBm)
Propagation Condition AWGN
Note 1: OCNG shall be used such that cell is fully allocated and a
constant total transmitted power spectral density is achieved
for all OFDM symbols.
Note2: This refers to the value of Threshx, low which is included in E-
UTRA system information, and is a threshold for the UTRA
TDD target cell
Table A.4.3.2.1.2-3: Cell specific test parameters for cell re-selection E-UTRA FDD to UTRA TDD test
case (cell 2)
Parameter Unit Cell 2 (UTRA)
Timeslot Number 0 DwPTS
T1 T2 T1 T2
UTRA RF Channel
Channel 2
Number (Note1)
PCCPCH_Ec/Ior dB -3 -3
DwPCH_Ec/Ior dB 0 0
OCNS_Ec/Ior dB -3 -3
Iˆor I oc dB 11 11 11 11
dBm/1.28
I oc MHz
-80
PCCPCH RSCP dBm -72 -72 n.a. n.a.
Propagation
AWGN
Condition
Qrxlevmin dBm -103
Qoffset1s,n dB C1, C2: 0
Qhyst1s dB 0
Threshx, high (Note2) dB 46 (-94dBm)
Note1: In the case of multi-frequency cell, the UTRA RF Channel
Number is the primary frequency’s channel number.
Note2: This refers to the value of Threshx, high which is included in
UTRA system information, and is a threshold for the E-
UTRA target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 638 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.2.1.3 Void
A.4.3.2.2 Test Requirements
A.4.3.2.2.1 1.28Mcps TDD option
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2, and starts to send the SYNCH-UL sequence in the UpPTS for sending the RRC
CONNECTION REQUEST message on cell 2.
The cell re-selection delay to lower priority shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateUTRA_TDD + TSI-UTRA
Where:
TevaluateUTRA_TDD 19.2s, See table table 4.2.2.5.2-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s, allow 21 s for lower priority cell reselection in the test case.
A.4.3.2.2.2.3 Void
A.4.3.2A E-UTRA FDD to UTRA TDD cell re-selection for IncMon
A.4.3.2A.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRA FDD to UTRA TDD inter-RAT cell reselection requirements for
increased UE carrier monitoring specified in clause 4.2.2.4. UTRA TDD cells are of lower priority than E-UTRA
serving cell.
The test scenario comprises of indicating 7 UTRA TDD inter-RAT cells on 7 different carriers in the neighbour list of
cell 1 as given in tables A.4.3.2A.1-1, A.4.3.2A.1-2 and A.4.3.2A.1-3. Each repetition of the test consists of five
successive time periods, with time duration of T0, T1, T2, T3, and T4 respectively. In the initialisation phase and at the
start of each repetition of T0, the test equipment provides signals for cell 1 (E-UTRA serving cell), and selects
frequencies for cells 2 and 3 which are chosen from the 7 inter-RAT layers which are configured in the UE neighbour
cell list as described in general and cell specific parameters. The neighbour lists of cells 2 and 3 shall include the
frequency of cell 1 in the normal performance group as well as the other UTRA TDD frequencies configured to the UE
in the test.
Cell 1, 2 and 3 are identified by the UE during time phase T0. Cell 1, cell 2 and cell 3 belong to different tracking areas.
Furthermore, UE has not registered with network for the tracking area containing cell 2 or 3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 639 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.2A.1-1: General test parameters for E-UTRA FDD to UTRA TDD inter-RAT cell re-selection
test case
Parameter Unit Value Comment
T0 Active cell Cell1 T0 is repeated on each repetition of the test. In T0 the
test equipment selects frequencies for cell 2, 3 and then
time is allowed for the UE to identify the neighbour cells.
See cell specific parameters for detailed settings.
T1 start Active cell Cell 1
condition
T1 end Active cell Cell2 UE shall perform reselection to cell 2 during T1
condition Neighbour cell Cell1
T2 end Active cell Cell1 UE shall perform reselection to cell 1 during T2
condition
T3 end Active cell Cell3 UE shall perform reselection to cell 3 during T3
condition Neighbour cell Cell1
T4 end Active cell Cell1 UE shall perform reselection to cell 1 in T4 so that next
condition repetition of test can start from T0
UE configured UTRA RF 1, 2, 3, 4, 5, 6, 7 Seven UTRA TDD carrier frequencies are used in the
Channel Number UE neighbour cell list. Frequencies 4, 5, 6, and 7 are
indicated to have reduced performance
Test eqipment Cell 1, 2, 3 Cell 1 uses E-UTRA RF channel number 1
configuration Cells 2 is randomly selected to use different frequencies
selected from UTRA frequencies 1, 2, 3.
Cells 3 is randomly selected to use different frequencies
selected from UTRA frequencies 4, 5, 6, 7.
CP length of cell 1 normal
PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211 [16]
Access Barring - Not Sent No additional delays in random access procedure.
Information
Treselection s 0
HCS Not used
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T0 s (Test equipment T0 is defined so that the Test equipment selects
frequency selection frequencies and configures the cells, then the UE cell
and configuration detection time is taken into account.
time) + 960
T1 s 60 T1 need to be defined so that cell re-selection reaction
time is taken into account.
T2 s 25 T2 need to be defined so that cell re-selection reaction
time is taken into account
T3 s 500 T3 need to be defined so that cell re-selection reaction
time is taken into account.
T4 s 25 T4 need to be defined so that cell re-selection reaction
time is taken into account
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 640 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.2A.1-2: E-UTRA Cell specific test parameters for E-UTRA FDD to UTRA TDD inter-RAT cell
reselection test case in AWGN
Parameter Unit Cell 1
T0 T1 T2 T3 T4
E-UTRA RF Channel number 1
BW channel MHz 5MHz: NRB = 25
10MHz: NRB = 50
OCNG Patterns 5MHz: OP.16 FDD
10MHz: OP.2 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA NOTE 1 dB
OCNG_RB NOTE 1 dB
N oc NOTE 2 dBm/15kHz -98
Ê s N oc dB 11 -3 11 -3 11
Ê s I ot NOTE 3 dB 11 -3 11 -3 11
RSRP NOTE 3 dBm/15kHz -87 -101 -87 -101 -87
Qrxlevmin dBm/15kHz -140
Snonintrasearch dB Not sent
Threshserving, low dB 46 (-94dBm)
Threshx, low NOTE 4 dB 24 (-79dBm)
Propagation Condition AWGN
Antenna Configuration 1x2
NOTE 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
NOTE 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled.
NOTE 3: Es/Iot and RSRP levels have been derived from other parameters for information purposes. They
are not settable parameters themselves.
NOTE 4: This refers to the value of Threshx, low which is included in E-UTRA system information, and is a
threshold for the UTRA TDD target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 641 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.2A.1-3: UTRA TDD Cell specific test parameters for E-UTRA FDD to UTRA TDD inter-RAT
cell reselection test case in AWGN
Parameter Unit Cell 2 (UTRA TDD)
Timeslot Number 0 DwPTS
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
UTRA RF Channel
Randomly selected from 1, 2, 3 such that cell 2 is in the normal performance group
Number NOTE 1
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
dBm/
I oc 1.28 MHz
-80
Iˆor I oc dB -3 11 -3 -3 -3 -3 11 -3 -3 -3
PCCPCH RSCP dBm -86 -72 -86 -86 -86 n.a.
Propagation
AWGN
Condition
Qrxlevmin dBm -103
Qoffset1s,n dB C1, C2: 0
Qhyst1s dB 0
Sprioritysearch1 dB 24 (-79dBm)
Sprioritysearch2 dB 0
Threshx, high NOTE 2 dB 46 (-94dBm)
SsearchE-UTRA dB Not send
Time offset to cell1 ms 3
NOTE 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary frequency’s channel number.
NOTE 2: This refers to the value of Threshx, high which is included in UTRA system information, and is a threshold for the
E-UTRA target cell
Table A.4.3.2A.1-4:
Parameter Unit Cell 3 (UTRA TDD)
Timeslot Number 0 DwPTS
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
UTRA RF Channel Randomly selected from 4, 5, 6, 7 such that cell 3 is in the reduced performance
Number NOTE 1 group
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
dBm/
I oc 1.28 MHz
-80
Iˆor I oc dB -3 -3 -3 11 -3 -3 -3 -3 11 -3
PCCPCH RSCP dBm -86 -86 -86 -72 -86 n.a.
Propagation
AWGN
Condition
Qrxlevmin dBm -103
Qoffset1s,n dB C1, C2: 0
Qhyst1s dB 0
Sprioritysearch1 dB 24 (-79dBm)
Sprioritysearch2 dB 0
Threshx, high NOTE 2 dB 46 (-94dBm)
SsearchE-UTRA dB Not send
Time offset to cell1 ms 3
Time offset to cell2 μs 3
NOTE 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary frequency’s channel number.
NOTE 2: This refers to the value of Threshx, high which is included in UTRA system information, and is a threshold for the
E-UTRA target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 642 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.2A.2 Test Requirements
The cell reselection delay is defined as the time from the beginning of a relevant time period, to the moment when the
UE camps on the target cell, and starts to send the SYNCH-UL sequence in the UpPTS on cell 2, 3 for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on the target cell.
The reselection delays shall meet the requirements in table A.4.3.2A.2-1
Table A.4.3.2A.2-1: Test requirements for E-UTRA FDD to UTRA TDD inter-RAT cell reselection
Time phase Target cell Requirement for reselection delay (seconds)
T1 Cell 2 (normal performance group) 58.9
T3 Cell 3 (reduced performance group) 462.1
The rate of correct cell reselections observed during repeated tests shall be at least 90%, with a successful reselection
counted if it is within the required time regardless of the carrier frequencies involved. At least 90% of reselections to the
reduced performance group shall be within the required time, and at least 90% of reselections to the normal
performance group shall be within the required time.
NOTE: The cell re-selection delay to a normal performance group cell can be expressed as: NUTRA_carrier_TDD,normal
*TevaluateUTRA_TDD + TSI_UTRA, and to a reduced performance group cell can be expressed as: 6 *
NUTRA_carrier_TDD,reduced * TevaluateUTRA_TDD + TSI_UTRA,
Where:
TevaluateUTRA_TDD 19.2s, See Table 4.2.2.5.2-1
TSI_UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 3 * 19.2 + 1.28 = 58.88 s for normal performance group reselection and 6 * 4 * 19.2 + 1.28 =
462.08s for reduced performance group reselection, allow 58.9s for normal performance group and 462.1s for reduced
performance group in the test case.
Since only one E-UTRA frequency is configured and signal level of UTRA cell is lower than threshold of Sprioritysearch,
the UE shall select back to cell 1 (E-UTRA cell) within Kcarrier * TevaluateEUTRA + TSI = 19.2 + 1.28 = 20.48s.
A.4.3.3 E-UTRAN TDD – UTRAN FDD:
A.4.3.3.1 Test Purpose and Environment
This test is to verify the requirement for the EUTRA TDD- UTRA FDD inter-RAT cell reselection requirements
specified in clause 4.2.2.5.1 when the UTRA cell is of lower priority.
The test scenario comprises of one UTRA FDD and one E-UTRA TDD cells as given in tables A.4.3.3.1-1, A.4.3.3.1-2
and A.4.3.3.1-3. The test consists of two successive time periods, with time duration of T1 andT2 respectively. Both E-
UTRA cell 1 and UTRA cell 2 are already identified by the UE prior to the start of the test. Cell 2 is of lower priority
than cell 1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 643 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.3.1-1: General test parameters for EUTRA TDD- lower priority UTRA FDD inter RAT cell re-
selection test case
Parameter Unit Value Comment
Initial Active cell Cell1 E-UTRAN cell
condition
T1 end Active cells Cell1 UE shall perform reselection to cell 1 during T1
condition for subsequent iterations of the test
Neighbour cell Cell2
T2 end Active cell Cell2 UE shall perform reselection to cell 2 during T2
condition Neighbour cell Cell1
E-UTRA PRACH configuration 53 As specified in table 5.7.1-3 in TS 36.211
Uplink-downlink configuration of 1 As specified in table 4.2.2 in TS 36.211
cell 1
Special subframe configuration of 6 As specified in table 4.2.1 in TS 36.211
cell 1
E_UTRA Access Barring - Not Sent No additional delays in random access
Information procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 85 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s 25 T2 need to be defined so that cell re-selection
reaction time is taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 644 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.3.1-2: Cell specific test parameters for cell 1(E-UTRA)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in
A.3.2.2.2 (OP.2 TDD) OP.2 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANOTE 1 dB
OCNG_RBNOTE 1 dB
Qqualmin for UTRA
dB -20
neighbour cell
Qrxlevmin for UTRA
dBm -115
neighbour cell
Qrxlevmin dBm -140
N oc dBm/15 kHz -98
RSRP dBm/15 KHz -86 -102
dB 12 -4
Ê s I ot
dB 12 -4
Ês N oc
TreselectionEUTRAN s 0
Snonintrasearch dB Not sent
Threshserving, low dB 44
Threshx, low (NOTE 2) dB 42
Propagation Condition AWGN
NOTE 1: OCNG shall be used such that both cells are fully allocated
and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
NOTE 2 : This refers to the value of Threshx, low which is included in E-
UTRA system information, and is a threshold for the UTRA
target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 645 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.3.1-3: Cell specific test parameters for cell 2 (UTRA)
Parameter Unit Cell 2 (UTRA)
T1 T2
UTRA RF Channel Number Channel 2
CPICH_Ec/Ior dB -10
dB
PCCPCH_Ec/Ior -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
OCNS_Ec/Ior dB -0.941
Iˆor I oc dB 13 13
dBm/3,84
I oc MHz
-70
CPICH_Ec/Io dB -10.21 -10.21
CPICH_RSCP dBm -67 -67
Propagation Condition AWGN
Qqualmin dB -20
Qrxlevmin dBm -115
QrxlevminEUTRA dBm -140
UE_TXPWR_MAX_RACH dBm 21
Treselection s 0
Sprioritysearch1 dB 42
Sprioritysearch2 dB 0
Threshx, high (NOTE 1) dB 48
NOTE 1 : This refers to the value of Threshx, high which is included
in UTRA system information, and is a threshold for the
E-UTRA target cell
A.4.3.3.2 Test Requirements
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message on cell 2.
The cell re-selection delay to lower priority shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateUTRA_FDD + TSI-UTRA
Where:
TevaluateUTRA-FDD See Table 4.2.2.5.1-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for lower priority cell reselection, allow 21 s.
A.4.3.3A Idle mode TDD to UTRA FDD interRAT reselection
A.4.3.3A.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRA TDD-UTRA FDD inter-RAT cell reselection requirements for
increased UE carrier monitoring specified in clause 4.2.2.4.
The test scenario comprises of indicating 8 UTRA FDD interfrequency cells on 6 different carriers in the neighbour list
of cell 1 as given in table A.4.3.3A.1-2 and table A.4.3.3A.1-3 and cells 2 and 3 as given in table A.4.3.3A.1-4. Each
repetition of the test consists of five successive time periods, with time duration of T0, T1, T2, T3 and T4 respectively.
In the initialisation phase and at the start of each repetition of T0, the test equipment provides signals for cell 1 (serving
cell), and selects frequencies for cells 2 and 3 which are chosen from the 6 inter-RAT layers which are configured in the
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 646 ETSI TS 136 133 V14.3.0 (2017-04)
UE neighbour cell list as described in general and cell specific parameters. The neighbour lists of cells 2 and 3 shall
include the frequency of cell 1 in the normal performance group as well as the other frequencies configured to the UE in
the test.
Cell 1, 2 and 3 4 are identified by the UE during time period T0. Cell 1, cell 2 and cell 3 belong to different tracking
areas. Furthermore, UE has not registered with network for the tracking area containing cell 2 or 3. Cells 1, 2 and 3 4 all
have lower absolute priority than cell 1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 647 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.3A.1-1: General test parameters for E-UTRAN TDD- UTRAN FDD inter frequency cell re-
selection test case
Parameter Unit Value Comment
T0 Active cell Cell 1 T0 is repeated on each repetition of the
test. In T0 the test equipment selects
frequencies for cell 2, 3 and then time
is allowed for the UE to identify the
neighbour cells. See cell specific
parameters for detailed settings.
T1 start condition Active cell Cell 1
T1 end condition Active cell Cell 2 UE shall perform reselection to cell 2
during T1
Neighbour cell Cell 1, cell 3
T2 end condition Active cell Cell 1 UE shall perform reselection to cell 1
during T2
Neighbour cell Cell 2, cell 3
T3 end condition Active cell Cell 3 UE shall perform reselection to cell 3
during T3
Neighbour cell Cell 1, cell 2
Active cell Cell 1 UE shall perform reselection to cell 1
T4 end condition
during T4
Neighbour cell Cell 2, cell 3
UE configured E-UTRA RF Channel Number 1 Serving cell and six UTRA FDD carrier
frequencies are used in the UE
neighbour cell list. Frequencies 5,6 and
7 are indicated to have reduced
performance
UE configured UTRA RF Channel Number 2,3,4,5,6,7
Test eqipment configuration Cell 1 uses E-
UTRA RF
channel number
1
Cells 2,3,4 are
randomly
selected to use
different
frequencies
selected from
frequencies
2,3,4,5,6,7
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in
the test.
T0 s (test equipment Initialisation time need to be defined so
frequency that cell detection time is taken into
selection and account.
configuration
time) + 960
T1 s 25 T1 need to be defined so that cell re-
selection reaction time is taken into
account.
T2 s 25 T2 need to be defined so that cell re-
selection reaction time is taken into
account
T3 s 200 T3 need to be defined so that cell re-
selection reaction time is taken into
account.
T4 s 25 T4 need to be defined so that cell re-
selection reaction time is taken into
account
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 648 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.3A.1-2: General test parameters for EUTRA TDD- UTRA FDD inter RAT cell re-selection
test case
Parameter Unit Value Comment
Uplink-downlink configuration of cell 1 1 As specified in table 4.2.2 in TS 36.211
Special subframe configuration of cell 1 6 As specified in table 4.2.1 in TS 36.211
Table A.4.3.3A.1-3: Cell specific test parameters for E-UTRAN TDD- UTRAN FDD inter-RAT cell
reselection test case in AWGN cell 1 (E-UTRAN)
Parameter Unit Cell 1
T0 T1 T2 T3 T4
E-UTRA RF Channel 1
number
BW channel MHz 5MHz: NRB = 25
10MHz: NRB = 50
Io dBm/4. 59.0 64.5 59.0 64.5 59.0
5MHz(2 6 9 6 9 6
5RB)
dBm/9 56.0 61.5 56.0 61.5 56.0
Mhz 5 8 5 8 5
(50RB)
PDSCH parameters: OP.16 FDD (5MHz)
DL Reference OP.2 FDD (10MHz)
Measurement
Channel OP.10 TDD(5MHz)
OP.2 TDD (10MHz)
Time offset with 0
respect to cell1
PBCH RA dB 0
PBCH RB dB
PSS RA dB
SSS RA dB
PCFICH RB dB
PHICH RA dB
PHICH RB dB
PDCCH RA dB
PDCCH RB dB
PDSCH RA dB
PDSCH RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140
N oc dBm -98
Note 2
RSRP Note 3 dBm -84 -90 -90 -90 -84
Ê s I ot dB 14 8 8 8 14
Ê s N oc dB 14 8 8 8 14
TreselectionEUTRAN s 0
Snonintrasearch dB 62
Propagation AWGN
Condition
Note 1: OCNG shall be used such that the cell is fully allocated and
a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified
in the test is assumed to be constant over subcarriers and
time and shall be modelled as AWGN of appropriate power
for to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for
information purposes. They are not settable parameters
themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 649 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.3A.1-4: Cell specific test parameters for cells 2 and 3 (UTRA)
Cell 2 Cell 3
Parameter Unit
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
Randomly selected from 1, 2, 3 such Randomly selected from 4, 5, 6 such
UTRA RF Channel Number that cell 2 is in the normal that cell 3 is in the reduced
performance group performance group
CPICH_Ec/Ior dB -10 -10
dB -12 -12
PCCPCH_Ec/Ior
SCH_Ec/Ior dB -12 -12
PICH_Ec/Ior dB -15 -15
OCNS_Ec/Ior dB -0.941 0.941
Iˆor I oc dB -11 -5 -11 -11 -11 -11 -11 -11 -5 -11
dBm/3,84 -70 -70
I oc MHz
- - - - - - - - - -
CPICH_Ec/Io dB 10.3 16.1 10.3 10.3 10.3 10.3 10.3 10.3 16.1 10.3
3 9 3 3 3 3 3 6 9 3
CPICH_RSCP dBm -69 -85 -69 -69 -69 -69 -69 -69 -85 -69
Propagation Condition AWGN AWGN
Qqualmin dB -20 -20
Qrxlevmin dBm -115 -115
QrxlevminEUTRA dBm -140 -140
UE_TXPWR_MAX_RACH dBm 21 21
Treselection s 0 0
Sprioritysearch1 dB 62 62
Sprioritysearch2 dB 0 0
Threshserving, low dB 36 36
Threshx, low (Note 1) dB 50 50
A.4.3.3A.2 Test Requirements
The cell reselection delay is defined as the time from the beginning of a relevant time period, to the moment when the
UE camps on the target cell, and starts to send preambles on the PRACH for sending the RRC CONNECTION
REQUEST message to perform a Tracking Area Update procedure on the target cell.
The reselection delays shall meet the requirements in table A.4.3.1.5-1
Table A.4.3.3A.2-1
Time phase Target cell Requirement for reselection delay (seconds)
T0 Cell 1
T1 Cell 2 (normal performance group) 21
T2 Cell 1 (normal performance group) 8
T3 Cell 3 (reduced performance group) 148
T4 Cell 1 (normal performance group) 8
NOTE: The cell re-selection delay to a normal performance group cell can be expressed as: (NUTRA_carrier,normal) *
TevaluateUTRA_FDD + TSI-UTRA and to a reduced performance group cell can be expressed as: 6 *
NUTRA_carrier,reduced * TevaluateUTRA_FDD + TSI-UTRA.
Where:
TevaluateUTRA-FDD See Table 4.2.2.5.1-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE to
camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for normal performance group reselection, allow 21 s, and gives a total of 147.6 s for
reduced performance group reselection, allow 148 s for reduced performance group in the test case. For reselections
back to cell 1 since only one frequency is configured, the requirement is Tevaluate,E-UTRAN_Inter, + TSI = 7.68s, allow 8s.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 650 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.4 E-UTRAN TDD – UTRAN TDD:
A.4.3.4.1 E-UTRA to UTRA TDD cell re-selection: UTRA is of higher priority
A.4.3.4.1.1 Test Purpose and Environment
A.4.3.4.1.1.1 Void
A.4.3.4.1.1.2 1.28 Mcps TDD option
This test is to verify the requirement for the E-UTRA TDD to UTRA TDD inter-RAT cell re-selection requirements
specified in clause 4.2.2.5 when the UTRA cell is of higher priority.
This test scenario comprised of 1 E-UTRA TDD serving cell, and 1 UTRA TDD cell to be re-selected. Test parameters
are given in table A.4.3.4.1.1.2-1, A.4.3.4.1.1.2-2, and A.4.3.4.1.1.2-3. The test consists of three successive time
periods, with time duration of T1, T2 and T3 respectively. E-UTRA cell 1 is already identified by the UE prior to the
start of the test. Cell 2 is of higher priority than cell 1.
The ranking of the cells shall be made according to the cell reselection criteria specified in TS36.304.
Table A.4.3.4.1.1.2-1: General test parameters for E-UTRAN to UTRAN (1.28 Mcps TDD OPTION) Cell
Re-selection
Parameter Unit Value Comment
Initial Active cell Cell 1 UE is on cell 1 in the initialisation phase, so that reselection to
condition cell 2 occurs during T2
T2 end Active cell Cell 2 UE shall perform reselection to cell 2 during T2
condition Neighbour Cell 1
cell
T3 end Active cell Cell 1 UE shall perform reselection to cell 1 during T3
condition Neighbour Cell 2
cell
Uplink-downlink 1 As specified in table 4.2.2 in TS 36.211
configuration of cell 1
Special subframe 6 As specified in table 4.2.1 in TS 36.211
configuration of cell 1
PRACH configuration of 53 As specified in table 4.7.1-3 in TS 36.211
cell 1
CP length of cell 1 Normal
Time offset between cells 3 ms Asynchronous cells
Access Barring - Not No additional delays in random access procedure.
Information sent
Treselection s 0
DRX cycle length s 1,28
HCS Not
used
T1 s >20 During T1, cell 2 shall be powered off, and during the off time
the primary scrambling code shall be changed, The intention is
to ensure that cell 2 has not been detected by the UE prior to
the start of period T2.
T2 s 85 T2 needs to be defined so that cell re-selection reaction time is
taken into account.
T3 s 25 T3 needs to be defined so that cell re-selection reaction time is
taken into account.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 651 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.4.1.1.2-2: Cell specific test parameters for cell re-selection E-UTRA TDD to UTRA TDD test
case (cell 1)
Parameter Unit Cell 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANOTE 1 dB
OCNG_RBNOTE 1 dB
Qrxlevmin dBm/15kHz -140 -140 -140
N oc dBm/15kHz -98
RSRP dBm/15kHz -87 -87 -87
Ê s I ot dB 11 11 11
Threshx, high (NOTE 2) dB 24(-79dBm)
Snonintrasearch dB 46
Propagation Condition AWGN
NOTE 1: OCNG shall be used such that cell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
NOTE 2: This refers to the value of Threshx, high which is included in E-
UTRA system information, and is a threshold for the UTRA
target cell
Table A.4.3.4.1.1.2-3: Cell specific test parameters for cell re-selection E-UTRA TDD to UTRA TDD test
case (cell 2)
Parameter Unit Cell 2 (UTRA)
Timeslot Number 0 DwPTS
T1 T2 T3 T1 T2 T3
UTRA RF Channel
Channel 2
Number (NOTE 1)
PCCPCH_Ec/Ior dB -3 -3 -3
DwPCH_Ec/Ior dB 0 0 0
OCNS_Ec/Ior dB -3 -3 -3
Iˆor I oc dB -inf 11 -3 -inf 11 -3
dBm/1.28
I oc MHz
-80
PCCPCH RSCP dBm -inf -72 -86 n.a.
Propagation
AWGN
Condition
Qrxlevmin dBm -103
Qoffset1s,n dB C1, C2: 0
Qhyst1s dB 0
Snonintrasearch dB Not sent
Threshserving, low dB 24 (-79dBm)
Threshx, low (NOTE 2) dB 46 (-94dBm)
NOTE 1: In the case of multi-frequency cell, the UTRA RF Channel Number
is the primary frequency’s channel number.
NOTE 2: This refers to the value of Threshx, low which is included in UTRA
system information, and is a threshold for the E-UTRA target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 652 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.4.1.1.3 Void
A.4.3.4.1.2 Test Requirements
A.4.3.4.1.2.1 Void
A.4.3.4.1.2.2 1.28 Mpcs TDD option
The cell reselection delay to higher priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2, and starts to send the SYNCH-UL sequence in the UpPTS for sending the RRC
CONNECTION REQUEST message on cell 2.
The cell re-selection delay to higher priority shall be less than 81 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to higher priority cell can be expressed as: Thigher_priority_search + TevaluateUTRA_TDD
+ TSI_UTRA,
Where:
Thigher_priority_search 60s, See clause 4.2.2
TevaluateUTRA_TDD 19.2s, See Table 4.2.2.5.2-1
TSI_UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 80.48 s, allow 81 s for higher priority cell reselection in the test case.
A.4.3.4.1.2.3 Void
A.4.3.4.2 E-UTRA to UTRA TDD cell re-selection: UTRA is of lower priority
A.4.3.4.2.1 Test Purpose and Environment
A.4.3.4.2.1.1 Void
A.4.3.4.2.1.2 1.28 Mcps TDD option
This test is to verify the requirement for the E-UTRA TDD to UTRA TDD inter-RAT cell re-selection requirements
specified in clause 4.2.2.5 when the UTRA cell is of lower priority.
This test scenario comprised of 1 E-UTRA TDD serving cell (Cell 1), and 1 UTRA TDD cell (Cell 2) to be re-selected.
Test parameters are given in table A.4.3.4.2.1.2-1, A.4.3.4.2.1.2-2, and A.4.3.4.2.1.2-3. The test consists of two
successive time periods, with time duration of T1 and T2 respectively. Cell 2 is of lower priority than cell 1.
The ranking of the cells shall be made according to the cell reselection criteria specified in TS36.304.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 653 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.4.2.1.2-1: General test parameters for E-UTRAN to UTRAN (1.28 Mcps TDD OPTION) Cell
Re-selection
Parameter Unit Value Comment
Initial condition Active cell Cell 1 E-UTRAN cell
T1 end Active cell Cell1 UE shall perform reselection to cell 1 during T1 for
condition subsequent iterations of the test
Neighbour cell Cell2 1.28 Mcps TDD OPTION cell
T2 end Active cell Cell2 UE shall perform reselection to cell 2 during T2
condition Neighbour cell Cell1 E-UTRA TDD cell
Uplink-downlink configuration of 1 As specified in table 4.2.2 in TS 36.211
cell 1
Special subframe configuration 6 As specified in table 4.2.1 in TS 36.211
of cell 1
PRACH configuration of cell 1 53 As specified in table 4.7.1-3 in TS 36.211
CP length of cell 1 Normal
Time offset between cells 3 ms Asynchronous cells
Access Barring Information - Not No additional delays in random access procedure.
sent
Treselection s 0
DRX cycle length s 1,28
HCS Not
used
T1 s 85
T2 s 25
Table A.4.3.4.2.1.2-2: Cell specific test parameters for cell re-selection E-UTRA TDD to UTRA TDD test
case (cell 1)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
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
OCNG_RANote1 dB
OCNG_RBNote1 dB
Qrxlevmin dBm/15kHz -140 -140
N oc dBm/15kHz -98
RSRP dBm/15kHz -87 -101
Ê s I ot dB 11 -3
Snonintrasearch dB Not sent
Threshserving, low dB 46 (-94dBm)
Threshx, low (Note2) dB 24 (-79dBm)
Propagation Condition AWGN
Note1: OCNG shall be used such that cell is fully allocated and a
constant total transmitted power spectral density is achieved
for all OFDM symbols.
Note2: This refers to the value of Threshx, low which is included in E-
UTRA system information, and is a threshold for the UTRA
target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 654 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.4.2.1.2-3: Cell specific test parameters for cell re-selection E-UTRA TDD to UTRA TDD test
case (cell 2)
Parameter Unit Cell 2 (UTRA)
Timeslot Number 0 DwPTS
T1 T2 T1 T2
UTRA RF Channel
Channel 2
Number (Note1)
PCCPCH_Ec/Ior dB -3 -3
DwPCH_Ec/Ior dB 0 0
OCNS_Ec/Ior dB -3 -3
Iˆor I oc dB 11 11 11 11
dBm/1.28
I oc MHz
-80
PCCPCH RSCP dBm -72 -72 n.a. n.a.
Propagation
AWGN
Condition
Qrxlevmin dBm -103
Qoffset1s,n dB C1, C2: 0
Qhyst1s dB 0
Threshx, high (Note2) dB 46 (-94dBm)
Note1: In the case of multi-frequency cell, the UTRA RF Channel
Number is the primary frequency’s channel number.
Note2: This refers to the value of Threshx, high which is included in
UTRA system information, and is a threshold for the E-
UTRA target cell
A.4.3.4.2.1.3 Void
A.4.3.4.2.2 Test Requirements
A.4.3.4.2.2.1 Void
A.4.3.4.2.2.2 1.28 Mpcs TDD option
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2, and starts to send the SYNCH-UL sequence in the UpPTS for sending the RRC
CONNECTION REQUEST message on cell 2.
The cell re-selection delay to lower priority shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateUTRA_TDD + TSI_UTRA,
Where:
TevaluateUTRA_TDD 19.2s, See Table 4.2.2.5.2-1
TSI_UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s, allow 21 s for lower priority cell reselection in the test case.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 655 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.4.2.2.3 Void
A.4.3.4.3 EUTRA TDD-UTRA TDD cell reselection in fading propagation conditions:
UTRA TDD is of lower priority
A.4.3.4.3.1 Test Purpose and Environment
This test is to verify the requirement for the EUTRA TDD- UTRA TDD inter-RAT cell reselection requirements
specified in clause 4.2.2.5.2 when the UTRA cell is of lower priority, and to verify the robustness of the UE
measurement filtering in a fading environment. The E-UTRA cell is in fading propagation conditions and the UTRA
cell is in AWGN propagation conditions.
The test scenario comprises of one UTRA TDD and one E-UTRA TDD cells as given in tables A.4.3.4.3.1-1,
A.4.3.4.3.1-2 and A.4.3.4.3.1-3. The test consists of four successive time periods, with time duration of T1 T2, T3 and
T4 respectively. Both E-UTRA cell 1 and UTRA cell 2 are already identified by the UE prior to the start of the test. Cell
2 is of lower priority than cell 1.
Table A.4.3.4.3.1-1: General test parameters for EUTRA TDD- lower priority UTRA TDD inter RAT cell
re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell1 E-UTRAN cell
condition
T1 end Active cells Cell1 UE shall perform reselection to cell 1 during T1
condition for subsequent iterations of the test
Neighbour cell Cell2
T3 end Active cell Cell2 UE shall perform reselection to cell 2 during T3
condition Neighbour cell Cell1
E-UTRA PRACH configuration 53 As specified in table 5.7.1-3 in TS 36.211
Uplink-downlink configuration of 1 As specified in table 4.2.2 in TS 36.211
cell 1
Special subframe configuration of 6 As specified in table 4.2.1 in TS 36.211
cell 1
E_UTRA Access Barring - Not Sent No additional delays in random access
Information procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s <85 T1 need to be defined so that cell re-selection
reaction time is taken into account. T1 is
terminated when the UE starts to send
preambles to cell 1
T2 s 64 The start of T2 is defined as the time when the
UE starts to send PRACH preambles to cell 1
T3 s <25 T3 need to be defined so that cell re-selection
reaction time is taken into account. T3 is
terminated when the UE starts to send PRACH
preambles to cell 2
T4 s 64 The start of T4 is defined as the time when the
UE starts to send PRACH preambles to cell 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 656 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.4.3.1-2: Cell specific test parameters for cell 1 (E-UTRA)
Parameter Unit Cell 1
T1 T2 T3 T4
E-UTRA RF Channel 1
number
BW channel MHz 10
Correlation Matrix and 1x2 Low
Antenna Configuration
OCNG Patterns defined in OP.2 TDD
A.3.2.2.2 (OP.2 TDD)
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin for UTRA dBm -103
neighbour cell
Qrxlevmin dBm -140
N oc dBm/15 kHz -104
RSRP dBm/15 KHz -82 -82 -107 -107
dB 22 22 -3 -3
Ê s I ot
dB 22 22 -3 -3
Ês N oc
TreselectionEUTRAN s 0
Snonintrasearch dB Not sent
Threshserving, low dB 44
Threshx, low (Note 2) dB 24
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: This refers to the value of Threshx, low which is included in E-UTRA system
information, and is a threshold for the UTRA target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 657 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.4.3.1-3: Cell specific test parameters for cell 2 (UTRA)
Parameter Unit Cell 2 (UTRA)
Timeslot Number 0 DwPTS
T1 T2 T3 T4 T1 T2 T3 T4
UTRA RF Channel Number (Note1) Channel 2
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
Iˆor I oc dB 13 13 13 13 13 13 13 13
I oc dBm/1.28 MHz -80
PCCPCH RSCP dBm -70 -70 -70 -70 n.a. n.a. n.a. n.a.
Propagation Condition AWGN
Qrxlevmin dBm -103
QrxlevminEUTRA dBm -140
UE_TXPWR_MAX_RACH dBm 21
Treselection s 0
Threshx, high (Note2) dB 44
Note1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary frequency’s
channel number.
Note2: This refers to the value of Threshx, high which is included in UTRA system information, and is a
threshold for the E-UTRA target cell
A.4.3.4.3.2 Test Requirements
The probability of reselection from cell 1 to cell 2 during T2 observed during testing shall be less than 10%
The probability of reselection from cell 2 to cell 1 during T4 observed during testing shall be less than 10%
The cell reselection delay to lower priority is defined as the time from the beginning of time period T3, to the moment
when the UE camps on cell 2, and starts to send the SYNCH-UL sequene in the UpPTS for sending the RRC
CONNECTION REQUEST message on cell 2. In order to evaluate reselection delay, the system simulator first needs to
verify that the UE is camped on cell 1 at the start of T3
The cell re-selection delay to lower priority shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateUTRA_TDD + TSI-UTRA
Where:
TevaluateUTRA_TDD 19.2s, See Table 4.2.2.5.2-1
TSI-UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for lower priority cell reselection, allow 21 s.
A.4.3.4.4 E-UTRA TDD to UTRA TDD cell re-selection for IncMon
A.4.3.4.4.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRA TDD to UTRA TDD inter-RAT cell reselection requirements for
increased UE carrier monitoring specified in clause 4.2.2.4. UTRA TDD cells are of lower priority than E-UTRA
serving cell.
The test scenario comprises of indicating 7 UTRA TDD inter-RAT cells on 7 different carriers in the neighbour list of
cell 1 as given in tables A.4.3.4.4.1-1, A.4.3.4.4.1-2 and A.4.3.4.4.1-3. Each repetition of the test consists of five
successive time periods, with time duration of T0, T1, T2, T3, and T4 respectively. In the initialisation phase and at the
start of each repetition of T0, the test equipment provides signals for cell 1 (E-UTRA serving cell), and selects
frequencies for cells 2 and 3 which are chosen from the 7 inter-RAT layers which are configured in the UE neighbour
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 658 ETSI TS 136 133 V14.3.0 (2017-04)
cell list as described in general and cell specific parameters. The neighbour lists of cells 2 and 3 shall include the
frequency of cell 1 in the normal performance group as well as the other UTRA TDD frequencies configured to the UE
in the test.
Cell 1, 2, and 3 are identified by the UE during time phase T0. Cell 1, cell 2, and cell 3 belong to different tracking
areas. Furthermore, UE has not registered with network for the tracking area containing cell 2 or 3.
Table A.4.3.4.4.1-1: General test parameters for E-UTRA TDD to UTRA TDD inter-RAT cell re-selection
test case
Parameter Unit Value Comment
T0 Active cell Cell1 T0 is repeated on each repetition of the test. In T0 the
test equipment selects frequencies for cell 2, 3 and then
time is allowed for the UE to identify the neighbour cells.
See cell specific parameters for detailed settings.
T1 start Active cell Cell 1
condition
T1 end Active cell Cell2 UE shall perform reselection to cell 2 during T1
condition Neighbour cell Cell1
T2 end Active cell UE shall perform reselection to cell 1 during T2
Cell1
condition
T3 end Active cell Cell3 UE shall perform reselection to cell 3 during T3
condition Neighbour cell Cell1
T4 end Active cell UE shall perform reselection to cell 1 in T4 so that next
Cell1
condition repetition of test can start from T0
UE configured UTRA RF Seven UTRA TDD carrier frequencies are used in the
Channel Number 1, 2, 3, 4, 5, 6, 7 UE neighbour cell list. Frequencies 4, 5, 6, and 7 are
indicated to have reduced performance
Test eqipment Cell 1 uses E-UTRA RF channel number 1
configuration Cells 2 is randomly selected to use different frequencies
Cell 1, 2, 3 selected from UTRA frequencies 1, 2, 3.
Cells 3 is randomly selected to use different frequencies
selected from UTRA frequencies 4, 5, 6, 7.
Uplink-downlink 1 As specified in table 4.2.2 in TS 36.211 [16]
configuration of cell 1
Special subframe 6 As specified in table 4.2.1 in TS 36.211 [16]
configuration of cell 1
CP length of cell 1 normal
PRACH configuration 53 As specified in table 5.7.1-3 in TS 36.211 [16]
Access Barring - No additional delays in random access procedure.
Not Sent
Information
Treselection s 0
HCS Not used
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T0 s (Test equipment T0 is defined so that the Test equipment selects
frequency selection frequencies and configures the cells, then the UE cell
and configuration detection time is taken into account.
time) + 960
T1 s T1 need to be defined so that cell re-selection reaction
60
time is taken into account.
T2 s T2 need to be defined so that cell re-selection reaction
25
time is taken into account
T3 s T3 need to be defined so that cell re-selection reaction
500
time is taken into account.
T4 s T4 need to be defined so that cell re-selection reaction
25
time is taken into account
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 659 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.4.4.1-2: E-UTRA Cell specific test parameters for E-UTRA TDD to UTRA TDD inter-RAT
cell reselection test case in AWGN
Parameter Unit Cell 1
T0 T1 T2 T3 T4
E-UTRA RF Channel number 1
BW channel MHz 5MHz: NRB = 25
10MHz: NRB = 50
OCNG Patterns 5MHz: OP.10 TDD
10MHz: OP.2 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc Note 2 dBm/15kHz -98
Ê s N oc dB 11 -3 11 -3 11
Ê s I ot Note 3 dB 11 -3 11 -3 11
RSRP Note 3 dBm/15kHz -87 -101 -87 -101 -87
Qrxlevmin dBm/15kHz -140
Snonintrasearch dB Not sent
Threshserving, low dB 46 (-94dBm)
Threshx, low Note 4 dB 24 (-79dBm)
Propagation Condition AWGN
Antenna Configuration 1x2
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled.
Note 3: Es/Iot and RSRP levels have been derived from other parameters for information purposes. They
are not settable parameters themselves.
Note 4: This refers to the value of Threshx, low which is included in E-UTRA system information, and is a
threshold for the UTRA TDD target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 660 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.3.4.4.1-3: UTRA TDD Cell specific test parameters for E-UTRA TDD to UTRA TDD inter-RAT
cell reselection test case in AWGN
Parameter Unit Cell 2 (UTRA TDD)
Timeslot Number 0 DwPTS
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
UTRA RF Channel
Randomly selected from 1, 2, 3 such that cell 2 is in the normal performance group
Number Note1
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
dBm/
I oc 1.28 MHz
-80
Iˆor I oc dB -3 11 -3 -3 -3 -3 11 -3 -3 -3
PCCPCH RSCP dBm -86 -72 -86 -86 -86 n.a.
Propagation
AWGN
Condition
Qrxlevmin dBm -103
Qoffset1s,n dB C1, C2: 0
Qhyst1s dB 0
Sprioritysearch1 dB 24 (-79dBm)
Sprioritysearch2 dB 0
Threshx, low Note2 dB 46 (-94dBm)
SsearchE-UTRA dB Not send
Time offset to cell1 ms 3
Note1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary frequency’s channel number.
Note2: This refers to the value of Threshx, low which is included in UTRA system information, and is a threshold for the
E-UTRA target cell
Table A.4.3.4.4.1-4:
Parameter Unit Cell 3 (UTRA TDD)
Timeslot Number 0 DwPTS
T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
UTRA RF Channel Randomly selected from 4, 5, 6, 7 such that cell 3 is in the reduced performance
Number Note1 group
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
dBm/
I oc 1.28 MHz
-80
Iˆor I oc dB -3 -3 -3 11 -3 -3 -3 -3 11 -3
PCCPCH RSCP dBm -86 -86 -86 -72 -86 n.a.
Propagation
AWGN
Condition
Qrxlevmin dBm -103
Qoffset1s,n dB C1, C2: 0
Qhyst1s dB 0
Sprioritysearch1 dB 24 (-79dBm)
Sprioritysearch2 dB 0
Threshx, high Note2 dB 46 (-94dBm)
SsearchE-UTRA dB Not send
Time offset to cell1 ms 3
Time offset to cell2 μs 3
Note1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary frequency’s channel number.
Note2: This refers to the value of Threshx, high which is included in UTRA system information, and is a threshold for the
E-UTRA target cell
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 661 ETSI TS 136 133 V14.3.0 (2017-04)
A.4.3.4.4.2 Test Requirements
The cell reselection delay is defined as the time from the beginning of a relevant time period, to the moment when the
UE camps on the target cell, and starts to send the SYNCH-UL sequence in the UpPTS on cell 2, 3 for sending the RRC
CONNECTION REQUEST message to perform a Tracking Area Update procedure on the target cell.
The reselection delays shall meet the requirements in table A.4.3.4.4.2-1
Table A.4.3.4.4.2-1: Test requirements for E-UTRA TDD to UTRA TDD inter-RAT cell reselection
Time phase Target cell Requirement for reselection delay (seconds)
T1 Cell 2 (normal performance group) 58.9
T3 Cell 3 (reduced performance group) 462.1
The rate of correct cell reselections observed during repeated tests shall be at least 90%, with a successful reselection
counted if it is within the required time regardless of the carrier frequencies involved. At least 90% of reselections to the
reduced performance group shall be within the required time, and at least 90% of reselections to the normal
performance group shall be within the required time.
NOTE: The cell re-selection delay to a normal performance group cell can be expressed as: NUTRA_carrier_TDD,normal
*TevaluateUTRA_TDD + TSI_UTRA, and to a reduced performance group cell can be expressed as: 6 *
NUTRA_carrier_TDD,reduced * TevaluateUTRA_TDD + TSI_UTRA,
Where:
TevaluateUTRA_TDD 19.2s, See Table 4.2.2.5.2-1
TSI_UTRA Maximum repetition period of relevant system info blocks that needs to be received by the UE
to camp on a cell; 1280 ms is assumed in this test case.
This gives a total of 3 * 19.2 + 1.28 = 58.88 s for normal performance group reselection and 6 * 4 * 19.2 + 1.28 =
462.08s for reduced performance group reselection, allow 58.9s for normal performance group and 462.1s for reduced
performance group in the test case.
Since only one E-UTRA frequency is configured and signal level of UTRA cell is lower than threshold of Sprioritysearch,
the UE shall select back to cell 1 (E-UTRA cell) within Kcarrier * TevaluateEUTRA + TSI = 19.2 + 1.28 = 20.48s.
A.4.4 E-UTRAN to GSM Cell Re-Selection
A.4.4.1 E-UTRAN FDD – GSM:
A.4.4.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to GSM cell re-selection delay reported in clause 4.2.2.5.
This scenario implies the presence of 1 E-UTRAN serving cell, and 1 GSM cell to be re-selected. The UE is requested
to monitor neighbouring cells on 1 E-UTRA carrier and 12 GSM cells. Test parameters are given in Table, A.4.4.1-1,
A.4.4.1-2, A.4.4.1-3. E-UTRA FDD cell (Cell 1) and GSM cell (cell 2) shall belong to different Location Areas. The
test comprises two successive time periods, T1 and T2. During initialization before the start of the test, the UE is
camped on cell 1. By the end of T1, the UE has identified BSIC on the GSM BCCH carrier of cell 2 but the signal
levels do not meet the reselection criterion during T1. At the start of T2, the signal levels change such that cell 2
satisfies reselection criterion. The GSM layer is configured at a lower priority than the serving E-UTRA FDD layer.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 662 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.4.1-1: General test parameters for E-UTRA FDD GSM cell re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell1 UE shall be forced to cell 1 in the initialisation
condition phase and shall be able to detect and monitor
the 4 strongest GSM BCCH carriers in T1 . Cell
1 is an E-UTRA FDD cell.
Final Neighbour cell Cell2 UE shall perform reselection to cell 2 during T2.
condition Cell 2 is a GSM cell.
E-UTRA RF Channel Number 1 1 E-UTRA FDD carrier frequency
GSM ARFCN 1 12 GSM BCCH carriers are used
PRACH configuration 4 As specified in table 5.7.1-2 in TS 36.211
Access Barring Information - Not Sent No additional delays in random access
procedure.
CP length of cell 1 Normal
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 35 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s 35 T2 need to be defined so that the higher layer
search periodicity and cell re-selection reaction
time are taken into account.
Propagation channel AWGN
Table A.4.4.1-2: Cell-specific test parameters for Cell 1 – E-UTRA FDD cell
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in
A.3.2.1.2 (OP.2 FDD) OP.2 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140
N oc dBm/15 kHz -98
RSRP dBm/15 KHz -89 -102
Ê s Iot dB 9 -4
dB 9 -4
Ês N oc
TreselectionEUTRAN s 0
Snonintrasearch dB Not sent
Threshserving, low dB 44
Threshx, low (Note 2) dB 24
Note 1: OCNG shall be used such that both cells are fully allocated and
a constant total transmitted power spectral density is achieved
for all OFDM symbols.
Note 2: This refers to Threshx, low which is included in E-UTRA system
information, and is a threshold for GSM target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 663 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.4.1-3: Cell-specific test parameters for Cell 2 – GSM cell
Cell 2 (GSM)
Parameter Unit
T1 T2
Absolute RF Channel
ARFCN 1
Number
RXLEV dBm -90 -75
RXLEV_ACCESS_MIN dBm -105
MS_TXPWR_MAX_CCH dBm 24
A.4.4.1.2 Test Requirements
The cell re-selection delay is defined as the time from the beginning of time period T2, to the moment when the UE
camps on Cell 2, and starts to send the RR Channel Request message for location update to Cell 2.
The cell re-selection delay shall be less than 26 s + TBCCH, where TBCCH is the maximum time allowed to read BCCH
data from GSM cell [8].
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay can be expressed as: 4* TmeasureGSM + TBCCH, where:
TmeasureGSM See Table 4.2.2.5.3-1 in clause 4.2.2.5.3.
TBCCH Maximum time allowed to read BCCH data from GSM cell [8].
According to [8], the maximum time allowed to read the BCCH data, when being synchronized to
a BCCH carrier, is 1.9 s.
This gives a total of 25.6 s + TBCCH, allow 26 s + TBCCH in the test case.
A.4.4.2 E-UTRAN TDD – GSM:
A.4.4.2.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN TDD to GSM cell re-selection delay reported in clause 4.2.2.5.
This scenario implies the presence of 1 E-UTRAN serving cell, and 1 GSM cell to be re-selected. The UE is requested
to monitor neighbouring cells on 1 E-UTRA carrier and 12 GSM cells. Test parameters are given in Table, A.4.4.2-1,
A.4.4.2-2, A.4.4.2-3. E-UTRA TDD cell (Cell 1) and GSM cell (cell 2) shall belong to different Location Areas. The
test comprises two successive time periods, T1 and T2. During initialization before the start of the test, the UE is
camped on cell 1. By the end of T1, the UE has identified BSIC on the GSM BCCH carrier of cell 2 but the signal
levels do not meet the reselection criterion during T1. At the start of T2, the signal levels change such that cell 2
satisfies reselection criterion. The GSM layer is configured at a lower priority than the serving E-UTRA TDD layer.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 664 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.4.2-1: General test parameters for E-UTRA TDD GSM cell re-selection test case
Parameter Unit Value Comment
Initial Active cell Cell1 UE shall be forced to cell 1 in the initialisation
condition phase and shall be able to detect and monitor
the 4 strongest GSM BCCH carriers in T1. Cell 1
is an E-UTRA TDD cell.
Final Neighbour cell Cell2 UE shall perform reselection to cell 2 during T2.
condition Cell 2 is a GSM cell.
E-UTRA RF Channel Number 1 1 E-UTRA TDD carrier frequency
GSM ARFCN 1 12 GSM BCCH carriers are used
Uplink-downlink configuration of 1 As specified in table 4.2.2 in TS 36.211
cell 1
Special subframe configuration 6 As specified in table 4.2.1 in TS 36.211
for cell 1
PRACH configuration for cell 1 53 As specified in table 5.7.1-3 in TS 36.211
CP length of cell 1 Normal
Access Barring Information - Not Sent No additional delays in random access
procedure.
DRX cycle length s 1.28 The value shall be used for all cells in the test.
T1 s 35 T1 need to be defined so that cell re-selection
reaction time is taken into account.
T2 s 35 T2 need to be defined so that the higher layer
search periodicity and cell re-selection reaction
time are taken into account.
Propagation channel AWGN
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 665 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.4.2-2: Cell-specific test parameters for Cell 1 – E-UTRA TDD cell
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in
A.3.2.2.2 (OP.2 TDD) OP.2 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Qrxlevmin dBm -140
N oc dBm/15 kHz -98
RSRP dBm/15 KHz -89 -102
Ê s Iot dB 9 -4
dB 9 -4
Ês N oc
TreselectionEUTRAN s 0
Snonintrasearch dB Not sent
Threshserving, low dB 44
Threshx, low (Note 2) dB 24
Note 1: OCNG shall be used such that both cells are fully allocated and
a constant total transmitted power spectral density is achieved
for all OFDM symbols.
Note 2: This refers to Threshx, low which is included in E-UTRA system
information, and is a threshold for GSM target cell.
Table A.4.4.2-3: Cell-specific test parameters for Cell 2 – GSM cell
Cell 2 (GSM)
Parameter Unit
T1 T2
Absolute RF Channel
ARFCN 1
Number
RXLEV dBm -90 -75
RXLEV_ACCESS_MIN dBm -105
MS_TXPWR_MAX_CCH dBm 24
A.4.4.2.2 Test Requirements
The cell re-selection delay is defined as the time from the beginning of time period T2, to the moment when the UE
camps on Cell 2, and starts to send the RR Channel Request message for location update to Cell 2.
The cell re-selection delay shall be less than 26 s + TBCCH, where TBCCH is the maximum time allowed to read BCCH
data from GSM cell [8].
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay can be expressed as: 4* TmeasureGSM + TBCCH, where:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 666 ETSI TS 136 133 V14.3.0 (2017-04)
TmeasureGSM See Table 4.2.2.5.3-1 in clause 4.2.2.5.3.
TBCCH Maximum time allowed to read BCCH data from GSM cell [8].
According to [8], the maximum time allowed to read the BCCH data, when being synchronized to
a BCCH carrier, is 1.9 s.
This gives a total of 25.6 s + TBCCH, allow 26 s + TBCCH in the test case.
A.4.5 E-UTRAN to HRPD Cell Re-Selection
A.4.5.1 E-UTRAN FDD – HRPD
A.4.5.1.1 E-UTRAN FDD – HRPD Cell Reselection: HRPD is of Lower Priority
A.4.5.1.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD- HRPD inter-RAT cell reselection requirements specified
in clause 4.2.2.5.4 when the HRPD cell is of lower priority.
The test scenario comprises of one HRPD and one E-UTRAN FDD cells as given in tables A.4.5.1.1.1-1, A.4.5.1.1.1-2
and A.4.5.1.1.1-3.
The test consists of two successive time periods, with time duration of T1 and T2 respectively. Both E-UTRAN FDD
cell 1 and HRPD cell 2 are already identified by the UE prior to the start of the test. At T1 the UE is camped on to cell
1. Cell 2 is of lower priority than cell 1. Cell 1 and cell 2 shall belong to different tracking areas.
Table A.4.5.1.1.1-1: General Test Parameters for E-UTRAN FDD - lower priority HRPD Cell Re-
selection
Parameter Unit Value Comment
Initial condition Active cell Cell 1 E-UTRAN FDD cell
Neighbour cell Cell 2 HRPD cell
Final condition Active cell Cell 2 HRPD cell is selecting during T2
DRX cycle length s 1.28
E-UTRA FDD RF Channel Number 1 Only one FDD carrier frequency
is used.
E-UTRA FDD Channel Bandwidth (BW channel) MHz 10
HRPD RF Channel Number 1 Only one HRPD carrier
frequency is used.
E-UTRA FDD PRACH configuration 4 As specified in table 5.7.1-2 in
TS 36.211
E_UTRA FDD Access Barring Information - Not Sent No additional delays in random
access procedure.
T1 s 30
T2 s 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 667 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.5.1.1.1-2: Cell Specific Test Parameters for E-UTRAN FDD (Cell # 1)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel number 1
BW channel MHz 10
OCNG Patterns defined in A.3.2.1.2
(OP.2 FDD) OP.2 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 kHz -98
RSRP dBm/15 KHz -89 -102
dB 9 -4
Ê s I ot
dB 9 -4
Ês N oc
TreselectionEUTRAN S 0
Snonintrasearch dB Not sent
cellReselectionPriority - 1
Qrxlevmin dBm -140
Qrxlevminoffset dB 0
Pcompensation dB 0
SServingCell dB 51 38
Threshserving, low dB 44
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 668 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.5.1.1.1-3: Cell Specific Test Parameters for HRPD (cell # 2)
Parameter Unit Cell 2
T1 T2
HRPD RF Channel Number 1
Control E b (38.4 kbps)
dB 21
Nt
Control E b (76.8 kbps)
dB 18
Nt
Iˆor I oc dB 0 0
dBm/ 1.2288
I oc MHz
-55
CDMA2000 HRPD Pilot Strength dB -3 -3
Propagation Condition AWGN
SnonServingCell,x -6
Treselection s 0
hrpd-CellReselectionPriority - 0
Threshx, low -14
A.4.5.1.1.2 Test Requirements
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2 and starts to send access probe preambles on the Access Channel on cell 2.
The cell re-selection delay to the lower priority cell 2 shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateHRPD + TSI-HRPD
Where:
TevaluatHRPD See Table 4.2.2.5.4-1
TSI-HRPD Maximum repetition period of relevant system information blocks that need to be received by
the UE to camp on cell 2; 1704 ms is assumed in this test case.
This gives a total of 20.904 s for the lower priority cell reselection, allow 21 s in the test case.
A.4.5.2 E-UTRAN TDD – HRPD
A.4.5.2.1 E-UTRAN TDD – HRPD Cell Reselection: HRPD is of Lower Priority
A.4.5.2.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN TDD- HRPD inter-RAT cell reselection requirements specified
in clause 4.2.2.5.4 when the HRPD cell is of lower priority.
The test scenario comprises of one HRPD and one E-UTRAN TDD cells as given in tables A.4.5.2.1.1-1, A.4.5.2.1.1-2
and A.4.5.2.1.1-3.
The test consists of two successive time periods, with time duration of T1 and T2 respectively. Both E-UTRAN TDD
cell 1 and HRPD cell 2 are already identified by the UE prior to the start of the test. At T1 the UE is camped on to cell
1. Cell 2 is of lower priority than cell 1. Cell 1 and cell 2 shall belong to different tracking areas.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 669 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.5.2.1.1-1: General Test Parameters for E-UTRAN TDD - lower priority HRPD Cell Re-
selection
Parameter Unit Value Comment
Initial condition Active cell Cell 1 E-UTRAN TDD cell
Neighbour cell Cell 2 HRPD cell
Final condition Active cell Cell 2 HRPD cell is selecting during T2
Uplink-downlink configuration of cell 1 1 As specified in table 4.2.2 in TS
36.211
Special subframe configuration of cell 1 6 As specified in table 4.2.1 in TS
36.211
CP length of cell 1 Normal
DRX cycle length s 1.28
E-UTRA TDD RF Channel Number 1 Only one TDD carrier frequency
is used.
E-UTRA TDD Channel Bandwidth (BWchannel) MHz 10
HRPD RF Channel Number 1 Only one HRPD carrier
frequency is used.
E-UTRA TDD PRACH configuration of cell 1 53 As specified in table 4.7.1-3 in
TS 36.211
E_UTRA TDD Access Barring Information - Not Sent No additional delays in random
access procedure.
T1 s 30
T2 s 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 670 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.5.2.1.1-2: Cell Specific Test Parameters for E-UTRAN TDD (Cell # 1)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel number 1
BW channel MHz 10
OCNG Patterns defined in A.3.2.2.2
(OP.2 TDD) OP.2 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 kHz -98
RSRP dBm/15 KHz -89 -102
dB 9 -4
Ê s I ot
dB 9 -4
Ês N oc
TreselectionEUTRAN S 0
Snonintrasearch dB Not sent
cellReselectionPriority - 1
Qrxlevmin dBm -140
Qrxlevminoffset dB 0
Pcompensation dB 0
SServingCell dB 51 38
Threshserving, low dB 44
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 671 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.5.2.1.1-3: Cell Specific Test Parameters for HRPD (cell # 2)
Parameter Unit Cell 2
T1 T2
HRPD RF Channel Number 1
Control E b (38.4 kbps)
dB 21
Nt
Control E b (76.8 kbps)
dB 18
Nt
Iˆor I oc dB 0 0
dBm/ 1.2288
I oc MHz
-55
CDMA2000 HRPD Pilot Strength dB -3 -3
Propagation Condition AWGN
SnonServingCell,x -6
Treselection s 0
hrpd-CellReselectionPriority - 0
Threshx, low -14
A.4.5.2.1.2 Test Requirements
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2 and starts to send access probe preambles on the Access Channel on cell 2.
The cell re-selection delay to the lower priority cell 2 shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: TevaluateHRPD + TSI-HRPD
Where:
TevaluatHRPD See Table 4.2.2.5.4-1
TSI-HRPD Maximum repetition period of relevant system information blocks that need to be received by the UE
to camp on cell 2; 1704 ms is assumed in this test case.
This gives a total of 20.904 s for the lower priority cell reselection, allow 21 s in the test case.
A.4.6 E-UTRAN to cdma2000 1X Cell Re-Selection
A.4.6.1 E-UTRAN FDD – cdma2000 1X
A.4.6.1.1 E-UTRAN FDD – cdma2000 1X Cell Reselection: cdma2000 1X is of Lower
Priority
A.4.6.1.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD- cdma2000 1X inter-RAT cell reselection requirements
specified in clause 4.2.2.5.5 when the cdma2000 1X cell is of lower priority.
The test scenario comprises of one cdma2000 1X and one E-UTRAN FDD cells as given in tables A.4.6.1.1.1-1,
A.4.6.1.1.1-2 and A.4.6.1.1.1-3.
The test consists of two successive time periods, with time duration of T1 and T2 respectively. Both E-UTRAN FDD
cell 1 and cdma2000 1X cell 2 are already identified by the UE prior to the start of the test. At T1 the UE is camped on
to cell 1. Cell 2 is of lower priority than cell 1. Cell 1 and cell 2 shall belong to different tracking areas.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 672 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.6.1.1.1-1: General Test Parameters for E-UTRAN FDD - lower priority cdma2000 1X Cell Re-
selection
Parameter Unit Value Comment
Initial condition Active cell Cell 1 E-UTRAN FDD cell
Neighbour cell Cell 2 cdma2000 1X cell
Final condition Active cell Cell 2 cdma2000 1X cell is selecting
during T2
DRX cycle length s 1.28
E-UTRA FDD RF Channel Number 1 Only one FDD carrier frequency
is used.
E-UTRA FDD Channel Bandwidth (BW channel) MHz 10
cdma2000 1X RF Channel Number 1 Only one cdma2000 1X carrier
frequency is used.
E-UTRA FDD PRACH configuration 4 As specified in table 5.7.1-2 in
TS 36.211
E_UTRA FDD Access Barring Information - Not Sent No additional delays in random
access procedure.
T1 s 30
T2 s 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 673 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.6.1.1.1-2: Cell Specific Test Parameters for E-UTRAN FDD (Cell # 1)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel number 1
BW channel MHz 10
OCNG Patterns defined in A.3.2.1.2
(OP.2 FDD) OP.2 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 KHz -89 -102
dB 9 -4
Ê s I ot
dB 9 -4
Ês N oc
TreselectionEUTRAN S 0
Snonintrasearch dB Not sent
cellReselectionPriority - 1
Qrxlevmin dBm -140
Qrxlevminoffset dB 0
Pcompensation dB 0
SServingCell dB 51 38
Threshserving, low dB 44
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 674 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.6.1.1.1-3: Cell Specific Test Parameters for cdma2000 1X (cell # 2)
Parameter Unit Cell 2
T1 T2
cdma2000 1X RF Channel Number 1
Pilot E c
dB -7
I or
Sync E c
dB -16
I or
Paging E c (4.8 kbps)
dB -12
I or
Iˆor I oc dB 0 0
dBm/ 1.2288
I oc MHz
-55
CDMA2000 1xRTT Pilot Strength dB -10 -10
Propagation Condition AWGN
SnonServingCell,x -20
Treselection s 0
oneXRTT-CellReselectionPriority - 0
Threshx, low -28
A.4.6.1.1.2 Test Requirements
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2 and starts to send access probe preambles on the Access Channel on cell 2.
The cell re-selection delay to the lower priority cell 2 shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: Tevaluatecdma2000 1X + TSI-cdma2000 1X
Where:
Tevaluatcdma2000 1X See Table 4.2.2.5.5-1
TSI-cdma2000 1X Maximum repetition period of relevant system information blocks that need to be received by
the UE to camp on cell 2; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for the lower priority cell reselection, allow 21 s in the test case.
A.4.6.2 E-UTRAN TDD – cdma2000 1X
A.4.6.2.1 E-UTRAN TDD –cdma2000 1X Cell Reselection: cdma2000 1X is of Lower
Priority
A.4.6.2.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN TDD- cdma2000 1X inter-RAT cell reselection requirements
specified in clause 4.2.2.5.5 when the cdma2000 1X cell is of lower priority.
The test scenario comprises of one cdma2000 1X and one E-UTRAN TDD cells as given in tables A.4.6.2.1.1-1,
A.4.6.2.1.1-2 and A.4.6.2.1.1-3.
The test consists of two successive time periods, with time duration of T1 and T2 respectively. Both E-UTRAN TDD
cell 1 and cdma2000 1X cell 2 are already identified by the UE prior to the start of the test. At T1 the UE is camped on
to cell 1. Cell 2 is of lower priority than cell 1. Cell 1 and cell 2 shall belong to different tracking areas.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 675 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.6.2.1.1-1: General Test Parameters for E-UTRAN TDD - lower priority cdma2000 1X Cell Re-
selection
Parameter Unit Value Comment
Initial condition Active cell Cell 1 E-UTRAN TDD cell
Neighbour cell Cell 2 cdma2000 1X cell
Final condition Active cell Cell 2 cdma2000 1X cell is selecting
during T2
DRX cycle length s 1.28
E-UTRA TDD RF Channel Number 1 Only one TDD carrier frequency
is used.
E-UTRA TDD Channel Bandwidth (BW channel) MHz 10
cdma2000 1X RF Channel Number 1 Only one cdma2000 1X carrier
frequency is used.
E-UTRA TDD PRACH configuration 53 As specified in table 5.7.1-3 in
TS 36.211
Uplink-downlink configuration of cell 1 1 As specified in table 4.2.2 in TS
36.211
Special subframe configuration of cell 1 6 As specified in table 4.2.1 in TS
36.211
E_UTRA TDD Access Barring Information - Not Sent No additional delays in random
access procedure.
T1 s 30
T2 s 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 676 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.6.2.1.1-2: Cell Specific Test Parameters for E-UTRAN TDD (Cell # 1)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel number 1
BW channel MHz 10
OCNG Patterns defined in A.3.2.2.2
(OP.2 TDD) OP.2 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 KHz -89 -102
dB 9 -4
Ê s I ot
dB 9 -4
Ês N oc
TreselectionEUTRAN S 0
Snonintrasearch dB Not sent
cellReselectionPriority - 1
Qrxlevmin dBm -140
Qrxlevminoffset dB 0
Pcompensation dB 0
SServingCell dB 51 38
Threshserving, low dB 44
Propagation Condition AWGN
Note 1: CNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Iterference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: SRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 677 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.4.6.2.1.1-3: Cell Specific Test Parameters for cdma2000 1X (cell # 2)
Parameter Unit Cell 2
T1 T2
cdma2000 1X RF Channel Number 1
Pilot E c
dB -7
I or
Sync E c
dB -16
I or
Paging E c (4.8 kbps)
dB -12
I or
Iˆor I oc dB 0 0
dBm/ 1.2288
I oc MHz
-55
CDMA2000 1xRTT Pilot Strength dB -10 -10
Propagation Condition AWGN
SnonServingCell,x -20
Treselection s 0
oneXRTT-CellReselectionPriority - 0
Threshx, low -28
A.4.6.2.1.2 Test Requirements
The cell reselection delay to lower priority is defined as the time from the beginning of time period T2, to the moment
when the UE camps on cell 2 and starts to send access probe preambles on the Access Channel on cell 2.
The cell re-selection delay to the lower priority cell 2 shall be less than 21 s.
The rate of correct cell reselections observed during repeated tests shall be at least 90%.
NOTE: The cell re-selection delay to lower priority cell can be expressed as: Tevaluatecdma2000 1X + TSI-cdma2000 1X
Where:
Tevaluatcdma2000 1X See Table 4.2.2.5.5-1
TSI-cdma2000 1X Maximum repetition period of relevant system information blocks that need to be received by the UE
to camp on cell 2; 1280 ms is assumed in this test case.
This gives a total of 20.48 s for the lower priority cell reselection, allow 21 s in the test case.
A.5 E-UTRAN RRC CONNECTED Mode Mobility
A.5.1 E-UTRAN Handover
A.5.1.1 E-UTRAN FDD - FDD Intra frequency handover
A.5.1.1.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD intra frequency handover requirements specified in
clause 5.1.2.1.
The test scenario comprises of 1 E-UTRA FDD carrier and 2 cells as given in tables A.5.1.1.1-1 and A.5.1.1.1-2. The
test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 678 ETSI TS 136 133 V14.3.0 (2017-04)
E-UTRAN shall send a RRC message implying handover to cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
Table A.5.1.1.1-1: General test parameters for E-UTRAN FDD-FDD intra frequency handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells 3 ms Asynchronous cells
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 679 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.1.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra frequency handover test
case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 - Infinity 11 11
Ês N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 - Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.1.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.1.2.1.2.
This gives a total of 50 ms.
A.5.1.2 E-UTRAN TDD - TDD Intra frequency handover
A.5.1.2.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD intra frequency handover requirements specified in
clause 5.2.2.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 680 ETSI TS 136 133 V14.3.0 (2017-04)
The test scenario comprises of 1 E-UTRA TDD carrier and 2 cells as given in tables A.5.1.2.1-1 and A.5.1.2.1-2. The
test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of cell 2.
E-UTRAN shall send a RRC message implying handover to cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
Table A.5.1.2.1-1: General test parameters for E-UTRAN TDD-TDD Intra frequency handover test case
Parameter Unit Value Comment
DL Reference Measurement
PDSCH parameters Channel R.0 TDD As specified in clause A.3.1.1.2
DL Reference Measurement
PCFICH/PDCCHPHICH parameters Channel R.6 TDD As specified in clause A.3.1.2.2
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 681 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.2.1-2: Cell specific test parameters for E-UTRAN TDD-TDD Intra frequency handover test
case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 TDD OP.2 TDD OP.1 TDD
defined in A.3.2.2.1 TDD TDD TDD
(OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ês N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 - Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.2.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.2.2.4.2.
This gives a total of 50 ms.
A.5.1.3 E-UTRAN FDD – FDD Inter frequency handover
A.5.1.3.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD inter-frequency handover requirements specified in
clause 5.1.2.1.
The test scenario comprises of two E-UTRA FDD carriers and one cell on each carrier as given in tables A.5.1.3.1-1
and A.5.1.3.1-2. PDCCHs indicating new transmissions shall be sent continuously to ensure that the UE would not enter
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 682 ETSI TS 136 133 V14.3.0 (2017-04)
the DRX state. The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At
the start of time duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2 becomes
detectable and the UE is expected to detect and send a measurement report. Gap pattern configuration with id #0 as
specified in Table 8.1.2.1-1 is configured before T2 begins to enable inter-frequency monitoring.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event A3. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE.
Table A.5.1.3.1-1: General test parameters for E-UTRAN FDD-FDD Inter frequency handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditions Active cell Cell 1 Cell 1 is on RF channel number 1
Neighbouring cell Cell 2 Cell 2 is on RF channel number 2
Final condition Active cell Cell 2
E-UTRA RF channel number 1, 2 Two FDD carriers are used
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -4
Hysteresis dB 0
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX DRX_L As specified in clause A.3.3
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
Access Barring Information - Not sent No additional delays in random
access procedure
Time offset between cells 3 ms Asynchronous cells
Gap pattern configuration Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 683 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.3.1-2: Cell specific test parameters for E-UTRAN FDD-FDD Inter frequency handover test
case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 FDD OP.2 OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4 4 -Infinity 7 7
Ês I ot
N oc Note 2 dBm/15 kHz -98
dB 4 4 4 -Infinity 7 7
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -94 -94 -Infinity -91 -91
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.3.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.1.2.1.2.
This gives a total of 50 ms.
A.5.1.4 E-UTRAN TDD – TDD Inter frequency handover
A.5.1.4.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD inter frequency handover requirements specified in
clause 5.2.2.4.
The test scenario comprises of two E-UTRA TDD carriers and one cell on each carrier as given in tables Table
A.5.1.4.1-1 and Table A.5.1.4.1-2. PDCCHs indicating new transmissions shall be sent continuously to ensure that the
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 684 ETSI TS 136 133 V14.3.0 (2017-04)
UE would not enter the DRX state. The test consists of three successive time periods, with time durations of T1, T2 and
T3 respectively. At the start of time duration T1, the UE may not have any timing information of cell 2.
E-UTRAN shall send a RRC message implying handover to cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3.
Table A.5.1.4.1-1: General test parameters for E-UTRAN TDD-TDD Inter frequency handover test case
Parameter Unit Value Comment
DL Reference Measurement
PDSCH parameters Channel R.0 TDD As specified in clause A.3.1.1.2
DL Reference Measurement
PCFICH/PDCCH/PHICH Channel R.6 TDD As specified in clause A.3.1.2.2
parameters
Gap Pattern Id 1 As specified in TS 36.133
clause 8.1.2.1.
Initial conditions Active cell Cell 1
Neighbour cell Cell 2
Final conditions Active cell Cell 2
E-UTRA RF channel number 1, 2 Two TDD carriers are used
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -4
Hysteresis dB 0
Time to Trigger ms 0
Filter coefficient 0
DRX DRX_L As specified in clause A.3.3
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 685 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.4.1-2: Cell specific test parameters for E-UTRAN TDD-TDD Inter frequency handover test
case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 FDD OP.2 OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Ioc dB 4 4 4 -Infinity 7 7
N oc Note 2
dBm/15 kHz -98
dB 4 4 4 -Infinity 7 7
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -94 -94 -infinity -91 -91
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.4.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.2.2.4.2.
This gives a total of 50 ms.
A.5.1.5 E-UTRAN FDD – FDD Inter frequency handover: unknown target
cell
A.5.1.5.1 Test Purpose and Environment
This test is to verify the FDD-FDD inter-frequency handover requirements for the case when the target cell is unknown
as specified in clause 5.1.2.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 686 ETSI TS 136 133 V14.3.0 (2017-04)
The test scenario comprises of two E-UTRA FDD carriers and one cell on each carrier as given in tables A.5.1.5.1-1
and A.5.1.5.1-2. No gap patterns are configured in the test case. The test consists of two successive time periods, with
time durations of T1 and T2 respectively. At the start of time duration T1, the UE does not have any timing information
of cell 2. Starting T2, cell 2 becomes detectable and the UE is expected to detect and start to transmit the PRACH to
Cell 2.
A RRC message implying handover shall be sent to the UE during period T1. The start of T2 is the instant when the last
TTI containing the RRC message implying handover is sent to the UE.
Table A.5.1.5.1-1: General test parameters for the E-UTRAN FDD-FDD Inter frequency handover test
case when the target cell is unknown
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditionsActive cell Cell 1 Cell 1 is on RF channel number 1
Neighbouring cell Cell 2 Cell 2 is on RF channel number 2
Final condition Active cell Cell 2
E-UTRA RF channel number 1, 2 Two FDD carriers are used
Channel Bandwidth (BW channel) MHz 10
DRX OFF Non-DRX test
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
Access Barring Information - Not sent No additional delays in random
access procedure
Time offset between cells 3 ms Asynchronous cells
T1 s ≤5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 687 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.5.1-2: Cell specific test parameters for the E-UTRAN FDD-FDD Inter frequency handover
test case when the target cell is unknown
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 2
number
BW channel MHz 10 10
OCNG Patterns OP.1 FDD OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4 -Infinity 7
Ês I ot
N oc Note 2 dBm/15 kHz -98
dB 4 4 -Infinity 7
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -91
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
N
oc to be fulfilled.
subcarriers and time and shall be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.5.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 130 ms from the beginning of time period T2.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms, which is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 115 ms in the test. See clause 5.1.2.1.2
This gives a total of 130 ms.
A.5.1.6 E-UTRAN TDD – TDD Inter frequency handover; unknown Target
Cell
A.5.1.6.1 Test Purpose and Environment
This test is to verify the TDD-TDD inter-frequency handover requirements for the case when the target cell is unknown
as specified in clause 5.2.2.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 688 ETSI TS 136 133 V14.3.0 (2017-04)
The test scenario comprises of two E-UTRA TDD carriers and one cell on each carrier as given in tables A.5.1.6.1-1
and A.5.1.6.1-2. No gap patterns are configured in the test case. The test consists of two successive time periods, with
time durations of T1, T2 respectively. At the start of time duration T1, the UE does not have any timing information of
cell 2. Starting T2, cell 2 becomes detectable and the UE receives a RRC handover command from the network. The
start of T2 is the instant when the last TTI containing the RRC message implying handover is sent to the UE.
Table A.5.1.6.1-1: General test parameters for the E-UTRAN TDD-TDD Inter-Frequency handover test
case when the target cell is unknown
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
DL Reference Measurement As specified in clause A.3.1.2.2
PCFICH/PDCCH/PHICH parameters Channel R.6 TDD
Initial conditions Active cell Cell 1 Cell 1 is on RF channel number 1
Neighbouring cell Cell 2 Cell 2 is on RF channel number 2
Final condition Active cell Cell 2
E-UTRA RF channel number 1, 2 Two TDD carriers
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells 3 μs Synchronous cells
Gap pattern configuration - No gap pattern configured
T1 s ≤5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 689 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.6.1-2: Cell specific test parameters for the E-UTRAN TDD-TDD Inter frequency handover
test case when the target cell is unknown
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 2
Number
BW channel MHz 10 10
OCNG Patterns OP.1 TDD OP.2 TDD OP.2 TDD OP.1 TDD
defined in A.3.2.2.1
(OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 3 dBm/15 kHz -98
RSRP Note 4 dBm/15 kHz -94 -94 -Infinity -93
dB 4 4 -Infinity 5
Ê s I ot
SCH_RP Note 4 dBm/15 kHz -94 -94 -Infinity -93
dB 4 4 -Infinity 5
Ês N oc
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.5.1.6.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 130 ms from the beginning of time period T2.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms, which is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 115 ms in the test. See clause 5.2.2.4.2
This gives a total of 130 ms.
A.5.1.7 E-UTRAN FDD – TDD Inter frequency handover
A.5.1.7.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-TDD inter frequency handover requirements specified in
clause 5.2.2.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 690 ETSI TS 136 133 V14.3.0 (2017-04)
The test scenario comprises of one E-UTRA FDD cell and one E-UTRA TDD cell as given in tables Table A.5.1.7.1-1 ,
Table A.5.1.7.1-2 and Table A.5.1.7.1-3. PDCCHs indicating new transmissions shall be sent continuously to ensure
that the UE would not enter the DRX state. The test consists of three successive time periods, with time durations of T1,
T2 and T3 respectively. At the start of time duration T1, the UE does not have any timing information of cell 2.
E-UTRAN shall send a RRC message implying handover to cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3.
Table A.5.1.7.1-1: General test parameters for E-UTRAN FDD-TDD Inter frequency handover test case
Parameter Unit Value Comment
Cell 1 PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
Cell 1 PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
DL Reference Measurement
Cell 2 PDSCH parameters Channel R.0 TDD As specified in clause A.3.1.1.2
DL Reference Measurement
Cell 2 PCFICH/PDCCH/PHICH Channel R.6 TDD As specified in clause A.3.1.2.2
parameters
Gap Pattern Id 0 As specified in TS 36.133
clause 8.1.2.1.
Initial conditions Active cell Cell 1
Neighbour cell Cell 2
Final conditions Active cell Cell 2
Cell 1 E-UTRA RF channel number 1 One FDD carrier is used
Cell 2 E-UTRA RF channel number 2 One TDD carrier is used
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -4
Hysteresis dB 0
Time to Trigger ms 0
Filter coefficient 0
DRX DRX_L As specified in clause A.3.3
CP length Normal
E-UTRA TDD Access Barring - Not Sent No additional delays in random
Information access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211. Applicable to cell 2.
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211. Applicable to cell 2
E-UTRA TDD PRACH configuration 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells 3 ms Asynchronous cells
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 691 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.7.1-2: Cell specific test parameters for E-UTRAN FDD (cell #1) in E-UTRAN FDD-TDD Inter
frequency handover test case
Parameter Unit Cell 1
T1 T2 T3
E-UTRA RF Channel number 1
BW channel MHz 10
OCNG Patterns defined in OP.1 FDD OP.1 FDD OP.2 FDD
A.3.2.1.1 (OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4 4
Ês I ot
N oc Note 2 dBm/15 kHz -98
dB 4 4 4
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power
for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They
are not settable parameter themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 692 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.7.1-3: Cell specific test parameters for E-UTRAN TDD (cell #2) in E-UTRAN FDD-TDD Inter
frequency handover test case
Parameter Unit Cell 2
T1 T2 T3
E-UTRA RF Channel number 2
BW channel MHz 10
OCNG Patterns defined in OP.2 TDD OP.2 TDD OP.1 TDD
A.3.2.2.1 (OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB -Infinity 7 7
Ês I ot
N oc Note 2 dBm/15 kHz -98
dB -Infinity 7 7
Ês N oc
RSRP Note 3 dBm/15 KHz -Infinity -91 -91
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power
for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They
are not settable parameter themselves.
A.5.1.7.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.2.2.4.2.
This gives a total of 50 ms.
A.5.1.8 E-UTRAN TDD – FDD Inter frequency handover
A.5.1.8.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-FDD inter-frequency handover requirements specified in
clause 5.2.2.3.
The test scenario comprises of one E-UTRA TDD cell and one E-UTRA FDD cell as given in tables Table A.5.1.8.1-1,
Table A.5.1.8.1-2 and Table A.5.1.8.1-3. PDCCHs indicating new transmissions should be sent continuously to ensure
that the UE would not enter the DRX state. The test consists of three successive time periods, with time durations of T1,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 693 ETSI TS 136 133 V14.3.0 (2017-04)
T2 and T3 respectively. At the start of time duration T1, the UE does not have any timing information of cell 2. Starting
T2, cell 2 becomes detectable and the UE is expected to detect and send a measurement report. Gap pattern
configuration with id #0 as specified in Table 8.1.2.1-1 is configured before T2 begins to enable inter-frequency
monitoring.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event A3. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE.
Table A.5.1.8.1-1: General test parameters for E-UTRAN TDD-FDD Inter frequency handover test case
Parameter Unit Value Comment
Cell 1 PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
Cell 1 PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2
parameters Channel R.6 TDD
Cell 2 PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
Cell 2 PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Initial conditions Active cell Cell 1 Cell 1 is on RF channel number 1
Neighbouring cell Cell 2 Cell 2 is on RF channel number 2
Final condition Active cell Cell 2
Cell 1 E-UTRA RF channel number 1 One TDD carrier is used
Cell 2 E-UTRA RF channel number 2 One FDD carrier is used
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -4
Hysteresis dB 0
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX DRX_L As specified in clause A.3.3
E-UTRA FDD PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
E-UTRA FDD Access Barring - Not sent No additional delays in random
Information access procedure
Time offset between cells 3 ms Asynchronous cells
Gap pattern configuration Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 694 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.8.1-2: Cell specific test parameters for E-UTRAN TDD (cell #1) in E-UTRAN TDD-FDD Inter
frequency handover test case
Parameter Unit Cell 1
T1 T2 T3
E-UTRA RF Channel number 1
BW channel MHz 10
OCNG Patterns defined in OP.1 TDD OP.1 TDD OP.2 TDD
A.3.2.2.1 (OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4 4
Ês I ot
N oc Note 2 dBm/15 kHz -98
dB 4 4 4
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power
for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They
are not settable parameter themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 695 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.8.1-3: Cell specific test parameters for E-UTRAN FDD (cell #2) in E-UTRAN TDD-FDD Inter
frequency handover test case
Parameter Unit Cell 2
T1 T2 T3
E-UTRA RF Channel number 2
BW channel MHz 10
OCNG Patterns defined in OP.2 FDD OP.2 FDD OP.1 FDD
A.3.2.1.1 (OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB -Infinity 7 7
Ês I ot
N oc Note 2 dBm/15 kHz -98
dB -Infinity 7 7
Ês N oc
RSRP Note 3 dBm/15 KHz -Infinity -91 -91
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power
for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They
are not settable parameter themselves.
A.5.1.8.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.1.2.1.2.
This gives a total of 50 ms.
A.5.1.9 E-UTRAN FDD - FDD Intra frequency handover for 5MHz bandwidth
A.5.1.9.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.5.1.1. The test parameters are the same
except those described in the following section. The listed parameter values in Tables A.5.1.9.1-1 and A.5.1.9.1-2 will
replace the values of corresponding parameters in Tables A.5.1.1.1-1 and A.5.1.1.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 696 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.9.1-1: General test parameters for E-UTRAN FDD-FDD intra frequency handover test case,
5MHz
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.5 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.11 FDD
Channel Bandwidth (BW channel) MHz 5
Note 1: See Table A.5.1.1.1-1 for other general test parameters.
Note 2: This test is performed according to the principle defined in section A.3.7.2
Table A.5.1.9.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra frequency handover test
case, 5MHz
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
BW channel MHz 5 5
OCNG Patterns OP.15 OP.15 OP.16 OP.16 FDD OP.16 FDD OP.15 FDD
defined in A.3.2.1.15 FDD FDD FDD
(OP.15 FDD) and in
A.3.2.1.16 (OP.16
FDD)
Note 1: See Table A.5.1.1.1-2 for other cell-specific test parameters.
A.5.1.9.2 Test Requirements
The requirements defined in section A.5.1.1.2 shall apply to this test case.
A.5.1.10 E-UTRAN FDD - FDD Intra frequency handover for UE category 0
A.5.1.10.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD intra frequency handover requirements specified in
clause 5.1.2.1.
The test scenario comprises of 1 E-UTRA FDD carrier and 2 cells as given in tables A.5.1.10.1-1 and A.5.1.10.1-2. The
test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of cell 2.
E-UTRAN shall send a RRC message implying handover to cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 697 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.10.1-1: General test parameters for E-UTRAN FDD-FDD intra frequency handover test
case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.3
Channel R.13 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells 3 ms Asynchronous cells
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 698 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.10.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra frequency handover test
case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s I ot dB 8 -3.3 -3.3 -Infinity 2.36 2.36
N oc Note 2 dBm/15 KHz -98
Ê s N oc dB 8 8 8 - Infinity 11 11
RSRP Note 3 dBm/15 KHz -90 -90 -90 - Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.10.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.1.2.1.2.
This gives a total of 50 ms.
A.5.1.11 E-UTRAN HD - FDD Intra frequency handover for UE category 0
A.5.1.11.1 Test Purpose and Environment
This test is to verify the requirement for the HD-FDD intra frequency handover requirements specified in clause 5.2.2.5.
The test scenario comprises of 1 E-UTRA FDD carrier and 2 cells as given in tables A.5.1.11.1-1 and A.5.1.11.1-2. The
test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 699 ETSI TS 136 133 V14.3.0 (2017-04)
E-UTRAN shall send a RRC message implying handover to cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
Table A.5.1.11.1-1: General test parameters for E-UTRAN HD-FDD intra frequency handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.4
Channel R.1 HD-FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.3
Channel R.3 HD-FDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells 3 ms Asynchronous cells
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 700 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.11.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra frequency handover test
case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s I ot dB 8 -3.3 -3.3 -Infinity 2.36 2.36
N oc Note 2 dBm/15 KHz -98
Ê s N oc dB 8 8 8 - Infinity 11 11
RSRP Note 3 dBm/15 KHz -90 -90 -90 - Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.11.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.2.2.5.2.
This gives a total of 50 ms.
A.5.1.12 E-UTRAN TDD - TDD Intra frequency handover for UE category 0
A.5.1.12.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD intra frequency handover requirements specified in
clause 5.2.2.4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 701 ETSI TS 136 133 V14.3.0 (2017-04)
The test scenario comprises of 1 E-UTRA TDD carrier and 2 cells as given in tables A.5.1.12.1-1 and A.5.1.12.1-2. The
test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of cell 2.
E-UTRAN shall send a RRC message implying handover to cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
Table A.5.1.12.1-1: General test parameters for E-UTRAN TDD-TDD Intra frequency handover test
case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.5
Channel R.12 TDD
PCFICH/PDCCHPHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 702 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.12.1-2: Cell specific test parameters for E-UTRAN TDD-TDD Intra frequency handover test
case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 TDD OP.2 TDD OP.1 TDD
defined in A.3.2.2.1 TDD TDD TDD
(OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s I ot dB 8 -3.3 -3.3 -Infinity 2.36 2.36
N oc Note 2 dBm/15 KHz -98
Ê s N oc dB 8 8 8 -Infinity 11 11
RSRP Note 3 dBm/15 KHz -90 -90 -90 - Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.5.1.12.2 Test Requirements
The UE shall start to transmit the PRACH to Cell 2 less than 50 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
Tinterrupt = 35 ms in the test; Tinterrupt is defined in clause 5.2.2.4.2.
This gives a total of 50 ms.
A.5.1.13 E-UTRAN FDD-FDD Intra frequency handover for Cat-M1 UEs in
CEModeA
A.5.1.13.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD intra frequency handover requirements specified in
clause 5.5.2.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 703 ETSI TS 136 133 V14.3.0 (2017-04)
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.5.1.13.1-1 and A.5.1.13.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of Cell 2.
E-UTRAN shall send a RRC message implying handover to Cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
During the test, UE is configured with measurement gap for cell search, because the narrowband of the PDSCH
Reference Measurement Channel does not overlap with the centre 6 PRBs of the carrier bandwidth.
Table A.5.1.13.1-1: General test parameters for E-UTRAN FDD-FDD intra frequency handover for Cat-
M1 UEs in CEModeA test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration PRACH_4CE As specified in A.3.16
PRACH initial CE level 0 Specified in the handover
message
T1 s 5
T2 s ≤5
T3 s 1
Gap pattern ID 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 704 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.13.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra frequency handover for
Cat-M1 UEs in CEModeA test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH Reference R.21 FDD -
Measurement Channel
in clause A.3.1.4.1
MPDCCH Reference R.17 FDD R.17 FDD
Channel in
clause A.3.1.3.1
PCFICH/PDCCH/PHIC R.7 FDD R.7 FDD
H Reference Channel
in clause A.3.1.2.1
OCNG Patterns OP.21 FDD OP.21 FDD
defined in A.3.2.1.21
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB -3 -3
PDCCH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
Ê s N oc dB 8 8 8 -Infinity 12 12
dB 8 -4.27 -4.27 -Infinity 3.36 3.36
Ê s Iot Note 3
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -86 -86
Io Note 3 dBm/9MHz -61.58 - 56.57 - 56.57 Specified in columns for Cell 1
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Asynchronous cells
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for information purpose. They are not
settable parameters themselves.
A.5.1.13.2 Test Requirements
The UE shall finish the transmission of all repetitions of the PRACH to Cell 2 less than 170 ms from the beginning of
time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 705 ETSI TS 136 133 V14.3.0 (2017-04)
Tinterrupt = 120 + 35 ms in the test; Tinterrupt is defined in clause 5.5.2.1.2.
This gives a total of 170 ms.
A.5.1.14 E-UTRAN HD-FDD Intra frequency handover for Cat-M1 UEs in
CEModeA
A.5.1.14.1 Test Purpose and Environment
This test is to verify the requirement for the HD-FDD intra frequency handover requirements specified in clause 5.5.2.2.
The test scenario comprises of 1 E-UTRA FDD carrier and 2 cells as given in tables A.5.1.14.1-1 and A.5.1.14.1-2. The
test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of Cell 2.
E-UTRAN shall send a RRC message implying handover to Cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
During the test, UE is configured with measurement gap for cell search, because the narrowband of the PDSCH
Reference Measurement Channel does not overlap with the centre 6 PRBs of the carrier bandwidth.
Table A.5.1.14.1-1: General test parameters for E-UTRAN HD-FDD intra frequency handover for Cat-
M1 UEs in CEModeA test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration PRACH_4CE As specified in A.3.16
PRACH initial CE level 0 Specified in the handover
message
T1 s 5
T2 s ≤5
T3 s 1
Gap pattern ID 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 706 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.14.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra frequency handover for
Cat-M1 UEs in CEModeA test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH Reference R.11 HD-FDD -
Measurement Channel
in clause A.3.1.4.2
MPDCCH Reference R.7 HD-FDD R.7 HD-FDD
Channel in
clause A.3.1.3.2
PCFICH/PDCCH/PHIC R.4 HD-FDD R.4 HD-FDD
H Reference Channel
in clause A.3.1.2.3
OCNG Patterns OP.21 FDD OP.21 FDD
defined in A.3.2.1.21
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB -3 -3
PDCCH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
Ê s N oc Note 3 dB 8 8 8 -Infinity 12 12
dB 8 -4.27 -4.27 -Infinity 3.36 3.36
Ê s Iot
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -86 -86
Io Note 3 dBm/9MHz -61.58 - 56.57 - 56.57 Specified in columns for Cell 1
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Asynchronous cells
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for information purpose. They are not
settable parameters themselves
A.5.1.14.2 Test Requirements
The UE shall finish the transmission of all the repetitions of the PRACH to Cell 2 less than 170 ms from the beginning
of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 707 ETSI TS 136 133 V14.3.0 (2017-04)
Tinterrupt = 120 + 35 ms in the test; Tinterrupt is defined in clause 5.5.2.1.2.
This gives a total of 170 ms.
A.5.1.15 E-UTRAN TDD Intra frequency handover for Cat-M1 UEs in
CEModeA
A.5.1.15.1 Test Purpose and Environment
This test is to verify the requirement for the TDD intra frequency handover requirements specified in clause 5.5.2.3.
The test scenario comprises of 1 E-UTRA TDD carrier and 2 cells as given in tables A.5.1.15.1-1 and A.5.1.15.1-2. The
test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of Cell 2.
E-UTRAN shall send a RRC message implying handover to Cell 2. The RRC message implying handover shall be sent
to the UE during period T2, after the UE has reported Event A3. T3 is defined as the end of the last TTI containing the
RRC message implying handover.
During the test, UE is configured with measurement gap for cell search, because the narrowband of the PDSCH
Reference Measurement Channel does not overlap with the centre 6 PRBs of the carrier bandwidth.
Table A.5.1.15.1-1: General test parameters for E-UTRAN TDD Intra frequency handover for Cat-M1
UEs in CEModeA test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index PRACH_4CE As specified in A.3.16
PRACH initial CE level 0 Specified in the handover
message
T1 s 5
T2 s ≤5
T3 s 1
Gap pattern ID 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 708 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.15.1-2: Cell specific test parameters for E-UTRAN TDD Intra frequency handover for Cat-
M1 UEs in CEModeA test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH Reference R.17 TDD -
Measurement Channel
in clause A.3.1.4.3
MPDCCH Reference R.15 TDD R.15 TDD
Channel in
clause A.3.1.3.3
PCFICH/PDCCH/PHIC R.7 TDD R.7 TDD
H Reference Channel
in clause A.3.1.2.2
OCNG Patterns OP.11 TDD OP.11 TDD
defined in A.3.2.2.11
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB -3 -3
PDCCH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
Ê s N oc dB 8 8 8 -Infinity 12 12
dB 8 -4.27 -4.27 -Infinity 3.36 3.36
Ê s Iot Note 3
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -86 -86
Io Note 3 dBm/9MHz -61.58 -56.57 -56.57 Specified in columns for Cell 1
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 μs - 3
Synchronous cells
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for information purpose. They are not
settable parameters themselves
A.5.1.15.2 Test Requirements
The UE shall finish the transmission of all the repetitions of the PRACH to Cell 2 less than 170 ms from the beginning
of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 709 ETSI TS 136 133 V14.3.0 (2017-04)
Tinterrupt = 120 + 35 ms in the test; Tinterrupt is defined in clause 5.5.2.3.2.
This gives a total of 170 ms.
A.5.1.16 E-UTRAN FDD-FDD Intra frequency handover for Cat-M1 UEs in
CEModeB
A.5.1.16.1 Test Purpose and Environment
This test is to verify the requirement for the FDD-FDD intra frequency handover requirements specified in
clause 5.6.2.1.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.5.1.16.1-1 and A.5.1.16.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of Cell 2.
During period T2, the UE should report Event A3, and afterwards E-UTRAN shall send a RRC message to the UE
implying handover to Cell 2. T3 is defined as the end of the last TTI containing the RRC message from UE implying
handover.
During the test, the UE is configured with measurement gap for cell search, because the narrowband of the PDSCH
Reference Measurement Channel does not overlap with the centre 6 PRBs of the carrier bandwidth.
Table A.5.1.16.1-1: General test parameters for E-UTRAN FDD-FDD intra frequency handover for Cat-
M1 UEs in CEModeB test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration PRACH_4CE As specified in A.3.16
PRACH initial CE level 0 Specified in handover message
T1 s 5
T2 s ≤5
T3 s 5
Gap pattern ID 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 710 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.16.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra frequency handover for
Cat-M1 UEs in CEModeB test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH Reference R.23 FDD
Measurement Channel
in A.3.1.4.4
MPDCCH Reference R.19 FDD R.19 FDD
Channel in A.3.1.3.4
PCFICH/PDCCH/PHIC R.7 FDD R.7 FDD
H Reference Channel
in clause A.3.1.2.1
OCNG Patterns OP.21 FDD OP.21 FDD
defined in A.3.2.3
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB -3 -3
PDCCH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
Ê s N oc dB -12 -12 -12 -Infinity -7 -7
dB -12 -12.79 -12.79 -Infinity -7.27 -7.27
Ê s Iot Note 3
RSRP Note 3 dBm/15 KHz -110 -110 -110 -Infinity -105 -105
Io Note 3 dBm/9MHz -69.95 -69.21 -69.21 Specified in columns for Cell 1
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Asynchronous cells
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for information purpose. They are not
settable parameters themselves.
A.5.1.16.2 Test Requirements
The UE shall finish transmission of all repetitions of the PRACH to Cell 2 less than 2610ms from the beginning of time
period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 711 ETSI TS 136 133 V14.3.0 (2017-04)
Tinterrupt = 2560ms + 35ms = 2595ms is defined in clause 5.6.2.1.2.
This gives a total of 2610ms.
A.5.1.17 E-UTRAN HD-FDD Intra frequency handover for Cat-M1 UEs in
CEModeB
A.5.1.17.1 Test Purpose and Environment
This test is to verify the requirement for the HD-FDD intra frequency handover requirements specified in clause 5.6.2.2.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.5.1.17.1-1 and A.5.1.17.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of Cell 2.
During period T2, the UE should report Event A3, and afterwards E-UTRAN shall send a RRC message to the UE
implying handover to Cell 2. During T3 is defined as the end of the last TTI containing the RRC message from UE
implying handover.
During the test, UE is configured with measurement gap for cell search, because the narrowband of the PDSCH
Reference Measurement Channel does not overlap with the centre 6 PRBs of the carrier bandwidth.
Table A.5.1.17.1-1: General test parameters for E-UTRAN HD-FDD intra frequency handover for Cat-
M1 UEs in CEModeB test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration PRACH_4CE As specified in clause A.3.16
PRACH initial CE level 0 Specified in handover message
T1 s 5
T2 s ≤5
T3 s 5
Gap pattern ID 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 712 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.17.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra frequency handover for
Cat-M1 UEs in CEModeA test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH Reference R.13 HD-FDD -
Measurement Channel
in clause A.3.1.4.5
MPDCCH Reference R.9 HD-FDD R.9 HD-FDD
Channel in
clause A.3.1.3.5
PCFICH/PDCCH/PHIC R.4 HD-FDD R.4 HD-FDD
H Reference Channel
in clause A.3.1.2.3
OCNG Patterns OP.21 FDD OP.21 FDD
defined in A.3.2.3
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB -3 -3
PDCCH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
Ê s N oc Note 3 dB -12 -12 -12 -Infinity -7 -7
dB -12 -12.79 -12.79 -Infinity -7.27 -7.27
Ê s Iot
RSRP Note 3 dBm/15 KHz -110 -110 -110 -Infinity -105 -105
Io Note 3 dBm/9MHz -69.95 -69.21 -69.21 Specified in columns for Cell 1
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
Asynchronous cells
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for information purpose. They are not
settable parameters themselves.
A.5.1.17.2 Test Requirements
The UE shall finish the transmission of all repetitions of the PRACH to Cell 2 less than 2610 ms from the beginning of
time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 713 ETSI TS 136 133 V14.3.0 (2017-04)
Tinterrupt = 2560ms + 35ms = 2595ms is defined in clause 5.6.2.1.2.
This gives a total of 2610ms.
A.5.1.18 E-UTRAN TDD Intra frequency handover for Cat-M1 UEs in
CEModeB
A.5.1.18.1 Test Purpose and Environment
This test is to verify the requirement for the TDD-TDD intra frequency handover requirements specified in
clause 5.6.2.3.
The test scenario comprises of one E-UTRA TDD carrier and two cells as given in tables A.5.1.18.1-1 and A.5.1.18.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE may not have any timing information of Cell 2.
During period T2, the UE should report Event A3, and afterwards E-UTRAN shall send a RRC message to the UE
implying handover to Cell 2. During T3 is defined as the end of the last TTI containing the RRC message from UE
implying handover.
During the test, the UE is configured with measurement gap for cell search, because the narrowband of the PDSCH
Reference Measurement Channel does not overlap with the centre 6 PRBs of the carrier bandwidth.
Table A.5.1.18.1-1: General test parameters for E-UTRAN TDD Intra frequency handover for Cat-M1
UEs in CEModeB test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
A3-Offset dB 0
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration PRACH_4CE As specified in clause A.3.16
PRACH initial CE level 0 Specified in handover message
T1 s 5
T2 s ≤5
T3 s 5
Gap pattern ID 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 714 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.1.18.1-2: Cell specific test parameters for E-UTRAN TDD Intra frequency handover test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH Reference R.19 TDD -
Measurement Channel
in clause A.3.1.4.6
MPDCCH Reference R.17 TDD R.17 TDD
Channel in
clause A.3.1.3.6
PCFICH/PDCCH/PHIC R.7 TDD R.7 TDD
H Reference Channel
in clause A.3.1.2.2
OCNG Patterns OP.11 TDD OP.11 TDD
defined in A.3.2.4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB -3 -3
PDCCH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
Ê s N oc dB -12 -12 -12 -Infinity -7 -7
dB -12 -12.79 -12.79 -Infinity -7.27 -7.27
Ê s Iot Note 3
RSRP Note 3 dBm/15 KHz -110 -110 -110 -Infinity -105 -105
Io Note 3 dBm/9MHz -69.95 -69.21 -69.21 Specified in columns for Cell 1
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 μs - 3
Synchronous cells
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for information purpose. They are not
settable parameters themselves.
A.5.1.18.2 Test Requirements
The UE shall finish the transmission of all repetitions of the PRACH to Cell 2 less than 2610 ms from the beginning of
time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 15 ms and is specified in clause 11.2 in TS 36.331 [2].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 715 ETSI TS 136 133 V14.3.0 (2017-04)
Tinterrupt = 2560ms + 35ms = 2595ms is defined in clause 5.6.2.1.2.
This gives a total of 2610 ms.
A.5.2 E-UTRAN Handover to other RATs
A.5.2.1 E-UTRAN FDD – UTRAN FDD Handover
A.5.2.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to UTRAN FDD handover requirements specified in
clause 5.3.1.
The test parameters are given in Tables A.5.2.1.1-1, A.5.2.1.1-2 and A.5.2.1.1-3. The test consists of three successive
time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have
any timing information of Cell 2. Starting T2, Cell 2 becomes detectable and the UE is expected to detect and send a
measurement report. Gap pattern configuration with id #0 as specified in Table 8.1.2.1-1 is configured before T2 begins
to enable inter-RAT frequency monitoring.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event B2. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE. The
handover message shall contain cell 2 as the target cell.
Table A.5.2.1.1-1: General test parameters for E-UTRAN FDD to UTRAN FDD handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditionsActive cell Cell 1 E-UTRAN cell
Neighbouring cell Cell 2 UTRAN cell
Final condition Active cell Cell 2 UTRAN cell
Channel Bandwidth (BW channel) MHz 10
Gap Pattern Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
E-UTRAN FDD measurement quantity RSRP
Inter-RAT (UTRAN FDD) measurement CPICH Ec/N0
quantity
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP
threshold for event B2
b2-Threshold2-UTRA dB -18 Absolute UTRAN CPICH Ec/Io
threshold for event B2
Hysteresis dB 0
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
UTRA RF Channel Number 1 One UTRA FDD carrier frequency
is used.
Monitored UTRA FDD cell list size 12 UTRA cells on UTRA RF channel
1 provided in the cell before T2.
Post-verification period False
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 716 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.1.1-2: Cell specific test parameters for E-UTRAN FDD to UTRAN FDD handover test case
(cell 1)
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns OP.1 OP.1 OP.2
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 0 0 0
Ês I ot
N oc dBm/15 kHz -98
dB 0 0 0
Ê s N oc
RSRP Note 2 dBm/15 KHz -98 -98 -98
Io Note 2 dBm/9 MHz -67.21 -67.21 -67.21
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: RSRP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Table A.5.2.1.1-3: Cell specific test parameters for E-UTRAN FDD to UTRAN FDD handover test case
(cell 2)
Parameter Unit Cell 2 (UTRA)
T1 T2 T3
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
DCH_Ec/Ior dB N/A N/A Note 1
OCNS_Ec/Ior dB -0.941 0.941 Note 2
Iˆor I oc dB -infinity -1.8 -1.8
dBm/3,84
I oc MHz
-70 -70 -70
CPICH_Ec/Io dB -infinity -14 -14
Propagation Condition AWGN
Note 1: The DPCH level is controlled by the power control loop
Note 2: The power of the OCNS channel that is added shall make
the total power from the cell to be equal to Ior .
A.5.2.1.2 Test Requirements
The UE shall start to transmit the UL DPCCH to Cell 2 less than 190 ms from the beginning of time period T3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 717 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.3.1.1.1.
Tinterrupt = 140 ms in the test; Tinterrupt is defined in clause 5.3.1.1.2.
This gives a total of 190 ms.
A.5.2.2 E-UTRAN TDD - UTRAN FDD Handover
A.5.2.2.1 Test Purpose and Environment
This test is to verify the E-UTRAN TDD – UTRAN FDD handover requirements specified in clause 5.3.1.
The test scenario comprises of one E-UTRAN TDD cell and one UTRAN FDD cell as given in the tables A.5.2.2.1-1,
A5.2.2.1-2 and A.5.2.2.1-3. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively. At start of time duration T1, the UE does not have any timing information of cell 2. Gap pattern
configuration with id #0 as specified in Table 8.1.2.1-1 is configured before the start of T2 to enable the monitoring of
UTRAN FDD. A neighbouring cell list, including the UTRAN cell (cell2), shall be sent to the UE before T2 starts.
During the time T2 cell 2 becomes detectable and the UE is expected to detect and send the measurement report. A
RRC message implying handover shall be sent to the UE during T2, after the UE has reported event B2. The start of T3
is the instant when the last TTI containing the RRC message implying handover is sent to the UE. The handover
message shall contain cell 2 as the target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 718 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.2.1-1: General test parameters for E-UTRAN TDD-UTRAN FDD handover
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN TDD) DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
(E-UTRAN TDD) Channel R.6 TDD
Initial conditions Active cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel
number 1.
Final conditions Active cell Cell 2
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211. Applicable to cell 1.
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211. Applicable to cell 1
E-UTRAN TDD measurement quantity RSRP
Inter-RAT (UTRA FDD) measurement CPICH Ec/Io
quantity
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP threshold
for event B2
b2-Threshold2-UTRA dB -18 UTRAN FDD CPICH Ec/Io threshold
for event B2
Hysteresis dB 0
DRX OFF No DRX configured.
Time to Trigger ms 0
Filter coefficient 0
CP length Normal Applicable to cell 1
Gap pattern configuration Id 0 As specified in Table 8.1.2.1-1; to
start before T2 starts
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency
is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
UTRA RF Channel Number 1 One UTRA FDD carrier frequency is
used.
Monitored UTRA FDD cell list size 12 UTRA cells on UTRA RF channel 1
provided in the cell list before T2.
Post-verification period False Post verification is not used.
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 719 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.2.1-2: Cell specific test parameters for E-UTRAN TDD (cell 1) for handover to UTRAN FDD
(cell # 2)
Parameter Unit Cell 1 (E-UTRAN)
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Pattern defined
in A.3.2.2.1 (OP.1 TDD)
OP.1 TDD OP.2 TDD
and in A.3.2.2.2 (OP.2
TDD)
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
RSRP dBm/15 kHz -98 -98 -98
Ê s Iot dB 0 0 0
dB 0 0 0
Ê s N oc
N oc dBm/15 kHz -98
Io Note 2 dBm/9 MHz -67.21 -67.21 -67.21
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: RSRP and Io levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Table A.5.2.2.1-3: Cell specific test parameters for UTRAN FDD (cell # 2) for handover from E-UTRAN
TDD cell (cell #1)
Parameter Unit Cell 1 (UTRA)
T1 T2 T3
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
DPCH_Ec/Ior dB N/A N/A Note 1
OCNS dB -0.941 -0.941 Note 2
Iˆor I oc dB -infinity -1.8 -1.8
dBm/3.84
I oc MHz
-70
CPICH_Ec/Io dB -infinity -14 -14
Propagation
AWGN
Condition
Note 1: The DPCH level is controlled by the power control loop
Note 2: The power of the OCNS channel that is added shall make
the total power from the cell to be equal to Ior .
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 720 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.2.2.2 Test Requirements
The UE shall start to transmit the UL DPCCH to Cell 2 less than 190 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.1.1.1.1.
Tinterrupt = 140 ms in the test; Tinterrupt is defined in clause 5.3.1.1.2.
This gives a total of 190 ms.
A.5.2.3 E-UTRAN FDD- GSM Handover
A.5.2.3.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN to GSM cell handover delay specified in clause 5.3.3.
The test parameters are given in Table A.5.2.3.1 -1, A.5.2.3.1 -2 and A.5.2.3.1 -3 below. In the measurement control
information it is indicated to the UE that event-triggered reporting with Event B1 shall be used. The test consists of
three successive time periods, with time duration of T1, T2 and T3 respectively. At the start of time duration T1, the UE
may not have any timing information of cell 2.
The RRC message implying handover to cell 2 shall be sent to the UE during period T2, after the UE has reported Event
B1. The start of T3 is defined as the end of last E-UTRAN TTI containing the RRC message implying handover.
The requirements are also applicable for a UE not requiring measurement gap, in which case no measurement gap
pattern should be sent for the parameters specified in Table A.5.2.3.1-1.
Table A.5.2.3.1 -1: General test parameters for E-UTRAN FDD-GSM handover
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Gap Pattern Id 1 As specified in TS 36.133
section8.1.2.1.
Initial conditionsActive cell Cell 1
Neighbour cell Cell 2
Final conditions Active cell Cell 2
Inter-RAT measurement quantity GSM Carrier RSSI
Threshold other system dBm -80 Absolute GSM carrier RSSI
threshold for event B1.
Hysteresis dB 0
Time to Trigger ms 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
T1 s 20
T2 s 7
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 721 ETSI TS 136 133 V14.3.0 (2017-04)
Table A. A.5.2.3.1 - 2: Cell Specific Parameters for Handover from E- UTRAN FDD to GSM cell case
(cell 1)
Parameter Unit Cell 1
T1, T2 T3
BW channel MHz 10
OCNG Patterns
defined in A.3.2.1.1
(OP.1 FDD) and in OP.1 FDD OP.2 FDD
A.3.2.1.2 (OP.2
FDD)
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
PDSCH_ RA dB
PDSCH_ RB dB
OCNG_ RA Note1 dB
OCNG_ RB Note1 dB
Ê s I ot dB 4
dBm/15
N oc Note 2
kHz
-98 (AWGN)
dB
Ê s N oc 4
dBm/15kH
RSRP Note 3 -94
z
Propagation
AWGN
Condition
Note 1: OCNG shall be used such that cell 1 is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is
assumed to be constant over subcarriers and time and shall be modelled as
Noc to be fulfilled.
AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Table A.5.2.3.1 - 3: Cell Specific Parameters for Handover from E-UTRAN FDD to GSM cell case (cell
2)
Cell 2 (GSM)
Parameter Unit
T1 T2, T3
Absolute RF Channel
ARFCN 1
Number
RXLEV dBm -85 -75
A.5.2.3.2 Test Requirements
The UE shall begin to send access bursts on the new DCCH of the target cell less than 100 ms from the beginning of
time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The test requirement in this test case is expressed as:
THandover delay = 90 ms (Table 5.3.3.2.1-1) + Toffset + TUL
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 722 ETSI TS 136 133 V14.3.0 (2017-04)
Toffset : Equal to 4.65 ms, GSM timing uncertainty between the time from when the UE is ready to transmit until
the start of the next timeslot in GSM 26 multiframe structure
TUL: Equal to 4.65 ms, the time the UE has to wait in case the next timeslot is an idle frame or a SACCH
frame.
This gives a total of 99.3 ms, allow 100 ms in the test case.
A.5.2.4 E-UTRAN TDD - UTRAN TDD Handover
A.5.2.4.1 Test Purpose and Environment
A.5.2.4.1.1 Void
A.5.2.4.1.2 1.28 Mcps TDD option
This test is to verify the requirement for E-UTRAN TDD to UTRAN TDD handover requirements specified in
clause 5.3.2.
The test scenario comprises of 1 E-UTRA TDD cell and 1 UTRA TDD cell as given in tables Table A.5.2.4.1.2-1,
Table A.5.2.4.1.2-2, and Table A.5.2.4.1.2-3. Gap pattern configuration #0 as defined in table 8.1.2.1-1 is provided.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively.
E-UTRAN shall send a RRC message implying handover to UE. The RRC message implying handover shall be sent to
the UE during period T2, after the UE has reported Event B2. The end of the last TTI containing handover message is
begin of T3 duration.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 723 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.4.1.2-1: General test parameters for E-UTRA TDD to UTRA(1.28 Mcps TDD OPTION)
handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2
parameters Channel R.6 TDD
Initial Active cell Cell 1 E-UTRA TDD cell
conditions Neighbour Cell 2 UTRA 1.28Mcps TDD Cell
cell
Final Active cell Cell 2
conditions
Gap Pattern Id 0 As specified in TS 36.133
clause 8.1.2.1.
Uplink-downlink configuration 1 As specified in table 4.2.2 in TS
of cell 1 36.211
Special subframe configuration 6 As specified in table 4.2.1 in TS
of cell 1 36.211
CP length of cell 1 Normal
Time offset between cells 3 ms Asynchronous cells
Access Barring Information Not Sent No additional delays in random
access procedure.
Assigned Sub-Channel 1 No additional delays in random
Number access procedure due to ASC.
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Ofn dB 0
Thresh1 dBm -93 E-UTRA event B2 threshold
Thresh2 dBm -80 UTRA event B2 threshold
T1 s 5
T2 s ≤10
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 724 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.4.1.2-2: Cell specific test parameters for E-UTRA TDD to UTRA TDD handover test case
(cell 1)
Parameter Unit Cell 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Pattern defined in
A.3.2.2.1 (OP.1 TDD) OP.2
OP.1 TDD
and in A.3.2.1.2 (OP.2 TDD
TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s I ot dB 13 -3 -3
dB 13 -3 -3
Ê s N oc
N oc dBm/15kHz -98
RSRP Note 2 dBm/15kHz -85 -101 -101
SCH_RP Note 2 dBm/15 kHz -85 -101 -101
Io Note 2 dBm/9MHz -57.01 -68.45 -68.45
Propagation Condition AWGN
Note 1: OCNG shall be used such that cell is fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM
symbols.
Note 2: RSRP, SCH_RP and Io levels have been derived from other
parameters for information purposes. They are not settable
parameters themselves
Table A.5.2.4.1.2-3: Cell specific test parameters for cell search E-UTRA to UTRA case (cell 2)
Parameter Unit Cell 2 (UTRA)
Timeslot Number 0 DwPTS
T1 T2 T3 T1 T2 T3
UTRA RF Channel
Channel 2
Number Note 21
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
Iˆor I oc dB -3 11 11 -3 11 11
I oc dBm/1.28 MHz -80
Note 2
PCCPCH RSCP dBm -86 -72 -72 n.a.
Io Note 2 dBm/1.28 MHz -78.24 -68.67 -68.67
Propagation
AWGN
Condition
Note 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary
frequency’s channel number.
Note 2: PCCPCH_RSCP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 725 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.2.4.1.3 Void
A.5.2.4.2 Test Requirements
A.5.2.4.2.1 Void
A.5.2.4.2.2 1.28 Mcps TDD option
The UE shall start to transmit the SYNCH-UL sequence in the UpPTS to Cell 2 less than 120 ms from the beginning of
time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.3.2.2.1.
Tinterrupt is defined in clause 5.3.2.2.2. Tinterrupt = 70 ms in the test as following:
Tinterrupt1= Toffset+TUL+30*FSFN+20 ms
Toffset = 10 ms; TUL = 10 ms; and FSFN = 1 for UE decoding SFN.
This gives a total of 120 ms.
A.5.2.4.2.3 Void
A.5.2.5 E-UTRAN FDD – UTRAN TDD Handover
A.5.2.5.1 Test Purpose and Environment
A.5.2.5.1.1 Void
A.5.2.5.1.2 1.28 Mcps TDD option
This test is to verify the requirement for the E-UTRAN FDD to UTRAN TDD handover requirements specified in
clause 5.3.2.
The test scenario comprises of two cells, E-UTRA TDD cell1 and UTRA TDD cell2. The test consists of three
successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE
does not have any timing information of Cell 2. Starting T2, Cell 2 becomes detectable and the UE is expected to detect
and send a measurement report. Gap pattern configuration with id #1 as specified in Table 8.1.2.1-1 is configured
before T2 begins to enable inter-RAT frequency monitoring. The test parameters are given in Tables A.5.2.5.1-1,
A.5.2.5.1-2 and A.5.2.5.1-3.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event B2. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE. The
handover message shall contain cell 2 as the target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 726 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.5.1.2-1: General test parameters for E-UTRA FDD to UTRA (1.28 Mcps TDD option)
handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference As specified in clause A.3.1.1.1
Measurement Channel R.0
FDD
PCFICH/PDCCH/PHICH DL Reference As specified in clause A.3.1.2.1
parameters Measurement Channel R.6
FDD
Initial Active cell Cell 1 E-UTRA FDD cell
conditions Neighbour cell Cell 2 UTRA 1.28Mcps TDD Cell
Final conditions Active cell Cell 2
Gap Pattern Id 1 As specified in TS 36.133
clause 8.1.2.1.
E-UTRAN FDD measurement RSRP
quantity
UTRAN TDD measurement RSCP
quantity
CP length of cell 1 Normal
Access Barring Information Not Sent No additional delays in random
access procedure.
Assigned Sub-Channel Number 1 No additional delays in random
access procedure due to ASC.
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Ofn dB 0
Thresh1 dBm -93 Absolute E-UTRAN RSRP threshold
for event B2
Thresh2 dBm -80S Absolute UTRAN RSCP threshold
for event B2
T1 s 5
T2 s ≤ 10
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 727 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.5.1.2-2: Cell specific test parameters for E-UTRAN FDD to UTRAN (1.28 Mcps TDD option)
handover test case (cell 1)
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns OP.1 FDD OP.1 FDD OP.2
defined in A.3.2.1.1 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s N oc dB 13 -3 -3
N oc dBm/15 kHz -98
Ê s I ot dB 13 -3 -3
RSRP Note 2 dBm/15 KHz -85 -101 -101
Io Note 2 dBm/9MHz -57.01 -68.45 -68.45
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: RSRP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves
Table A.5.2.5.1.2-3: Cell specific test parameters for E-UTRAN FDD to UTRAN (1.28 Mcps TDD option)
handover test case (cell 2)
Parameter Unit Cell 2 (UTRA)
Timeslot Number 0 DwPTS
T1 T2 T3 T1 T2 T3
UTRA RF Channel
Channel 2
Number Note 21
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
Iˆor I oc dB -3 11 11 -3 11 11
I oc dBm/1.28 MHz -80
PCCPCH RSCP Note 2 dBm -86 -72 -72 n.a.
Io Note 2 dBm/1.28 MHz -78.24 -68.67 -68.67
Propagation
AWGN
Condition
Note 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary
frequency’s channel number.
Note 2: PCCPCH_RSCP and Io levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 728 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.2.5.1.3 Void
A.5.2.5.2 Test Requirements
A.5.2.5.2.1 Void
A.5.2.5.2.2 1.28 Mcps TDD option
The UE shall start to transmit the SYNCH-UL sequence in the UpPTS to Cell 2 less than 120 ms from the beginning of
time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.3.2.2.1.
Tinterrupt is defined in clause 5.3.2.2.2. Tinterrupt = 70 ms in the test as following:
Tinterrupt1= Toffset+TUL+30*FSFN+20 ms
Toffset = 10 ms; TUL = 10 ms; and FSFN = 1 for UE decoding SFN.
This gives a total of 120 ms.
A.5.2.5.2.3 Void
A.5.2.6 E-UTRAN TDD - GSM Handover
A.5.2.6.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN to GSM cell handover delay specified in clause 5.3.3.
The test parameters are given in Table A.5.2.6.1-1, A.5.2.6.1-2 and A.5.2.6.1-3 below. In the measurement control
information it is indicated to the UE that event-triggered reporting with Event B1 shall be used. The test consists of
three successive time periods, with time duration of T1, T2 and T3 respectively. At the start of time duration T1, the UE
may not have any timing information of cell 2.
The RRC message implying handover to cell 2 shall be sent to the UE during period T2, after the UE has reported Event
B1. The start of T3 is defined as the end of last E-UTRAN TTI containing the RRC message implying handover.
The requirements are also applicable for a UE not requiring measurement gap, in which case no measurement gap
pattern should be sent for the parameters specified in Table A.5.2.6.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 729 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.6.1-1: General test parameters for E-UTRAN TDD toGSM neighbours handover test case
in AWGN propagation condition
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Gap Pattern Id 1 As specified in TS 36.133
clause 8.1.2.1.
Initial conditionsActive cell Cell 1
Neighbour cell Cell 2
Final conditions Active cell Cell 2
Uplink-downlink configuration of cell 1 1 As specified in table 4.2.2 in TS
36.211
Special subframe configuration of cell 1 6 As specified in table 4.2.1 in TS
36.211
CP length of cell 1 Normal
Inter-RAT measurement quantity GSM Carrier RSSI
E-UTRA RF Channel Number 1 E-UTRA RF Channel Number
E-UTRA Channel Bandwidth MHz 10 E-UTRA Channel Bandwidth
(BW channel) (BW channel)
Threshold other system dBm -80 Absolute GSM carrier RSSI threshold
for event B1.
Hysteresis dB 0
Time to Trigger ms 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
T1 s 20
T2 s 7
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 730 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.6.1-2: Cell Specific Parameters for Handover E- UTRAN TDD to GSM handover test case
Parameter Unit Cell 1
T1, T2 T3
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Patterns defined in
A.3.2.2.1 (OP.1 TDD) and in OP.1 TDD OP.2 TDD
A.3.2.2.2 (OP.2 TDD)
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
PDSCH_ RA dB
PDSCH_ RB dB
OCNG_ RA Note1 dB
OCNG_ RB Note1 dB
Ê s N oc dB 4
N oc Note 2 dBm/15 kHz -98 (AWGN)
Ê s I ot dB 4
RSRP Note 3 dBm/15kHz -94
Propagation Condition AWGN
NOTE 1: OCNG shall be used such that cell 1 is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
NOTE 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
NOTE 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.5.2.6.1-3: Cell Specific Parameters for Handover E-UTRAN to GSM cell case (cell 2)
Cell 2 (GSM)
Parameter Unit
T1 T2, T3
Absolute RF Channel
ARFCN 1
Number
RXLEV dBm -85 -75
A.5.2.6.2 Test Requirements
The UE shall begin to send access bursts on the new DCCH of the target cell less than 100 ms from the beginning of
time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The test requirement in this test case is expressed as:
THandover delay = 90 ms (Table 5.3.3.2.1-1) + Toffset + TUL
Toffset: Equal to 4.65 ms, GSM timing uncertainty between the time from when the UE is ready to transmit until
the start of the next timeslot in GSM 26 multiframe structure
TUL: Equal to 4.65 ms, the time the UE has to wait in case the next timeslot is an idle frame or a SACCH
frame.
This gives a total of 99.3 ms, allow 100 ms in the test case.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 731 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.2.7 E-UTRAN FDD – UTRAN FDD Handover; Unknown Target Cell
A.5.2.7.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to UTRAN FDD handover requirements for the case when
the target cell is unknown as specified in clause 5.3.1.
The test parameters are given in Tables A.5.2.7.1-1, A.5.2.7.1-2 and A.5.2.7.1-3. The test consists of two successive
time periods, with time durations of T1, T2. At the start of time duration T1, the UE does not have any timing
information of Cell 2. Starting T2, cell 2 becomes detectable and the UE receives a RRC handover command from the
network. The start of T2 is the instant when the last TTI containing the RRC message implying handover is sent to the
UE. No Gap pattern configuration shall be used.
Table A.5.2.7.1-1: General test parameters for E-UTRAN FDD to UTRAN FDD handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditionsActive cell Cell 1 E-UTRAN cell
Neighbouring cell Cell 2 UTRAN cell
Final condition Active cell Cell 2 UTRAN cell
Channel Bandwidth (BW channel) MHz 10
E-UTRAN FDD measurement quantity RSRP
Inter-RAT (UTRAN FDD) measurement CPICH Ec/N0
quantity
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
UTRA RF Channel Number 1 One UTRA FDD carrier frequency
is used.
Monitored UTRA FDD cell list size 12 UTRA cells on UTRA RF channel
1 provided in the cell before T2.
Post-verification period False
T1 s ≤5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 732 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.7.1-2: Cell specific test parameters for E-UTRAN FDD to UTRAN FDD handover test case
(cell 1)
Parameter Unit Cell 1 (E-UTRA)
T1 T2
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in OP.1 FDD OP.2 FDD
A.3.2.1.1 (OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 0 0
Ês I ot
N oc Note 2 dBm/15 kHz -98
dB 0 0
Ê s N oc
RSRP Note 3 dBm/15 KHz -98 -98
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and
a constant total transmitted power spectral density is achieved
for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time
N oc
and shall be modelled as AWGN of appropriate power for
to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for
information purposes. They are not settable parameters
themselves.
Table A.5.2.7.1-3: Cell specific test parameters for E-UTRAN FDD to UTRAN FDD handover test case
(cell 2)
Parameter Unit Cell 2 (UTRA)
T1 T2
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
DCH_Ec/Ior dB Note 1
OCNS_Ec/Ior dB Note 2
Iˆor I oc dB -infinity -1.8
dBm/3,84
I oc MHz
-70 -70
CPICH_Ec/Io dB -infinity -14
Propagation
AWGN
Condition
Note 1: The DPCH level is controlled by the power control loop
Note 2: The power of the OCNS channel that is added shall make
the total power from the cell to be equal to Ior .
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 733 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.2.7.2 Test Requirements
The UE shall start to transmit the UL DPCCH to Cell 2 less than 290 ms from the beginning of time period T2.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay is 50ms. See clause 5.3.1.1.1.
Tinterrupt is 240ms. See clause 5.3.1.1.2.
This gives a total of 290ms in the test case.
A.5.2.8 E-UTRAN FDD - GSM Handover; Unknown Target Cell
A.5.2.8.1 Test Purpose and Environment
This test is to verify the E-UTRAN FDD to GSM handover requirements for the case when the target GSM cell is
unknown as specified in clause 5.3.3.
The test parameters are given in Table A.5.2.8.1-1, A.5.2.8.1-2 and A.5.2.8.1-3 below. The test consists of two
successive time periods, with time duration of T1, T2 respectively. At the start of time duration T1, the UE will not
have any timing information of cell 2. Starting T2, cell 2 becomes detectable and the UE receives a RRC handover
command from the network. The start of T2 is the instant when the last TTI containing the RRC message implying
handover is sent to the UE. No Gap pattern configuration shall be used.
Table A.5.2.8.1-1: General test parameters for E-UTRAN FDD to GSM handover test case; unknown
target cell
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Gap Pattern Id None No measurement gaps shall be
provided.
Initial conditions Active cell Cell 1
Neighbour cell Cell 2
Final conditions Active cell Cell 2
DRX OFF No DRX configured
T1 s 7
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 734 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.8.1 - 2: Cell specific parameters for cell # 1 in E-UTRAN FDD to GSM handover test case;
unknown target cell
Parameter Unit Cell 1
T1 T2
BW channel MHz 10
OCNG Patterns
defined in A.3.2.1.1
(OP.1 FDD) and in OP.1 FDD OP.2 FDD
A.3.2.1.2 (OP.2
FDD)
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
PDSCH_ RA dB
PDSCH_ RB dB
OCNG_ RA Note1 dB
OCNG_ RB Note1 dB
Ê s I ot dB 4
N oc Note 2
dBm/15 kHz -98
dB
Ê s N oc 4
RSRP Note 3 dBm/15 kHz -94
Propagation
AWGN
Condition
Note 1: OCNG shall be used such that cell 1 is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is
assumed to be constant over subcarriers and time and shall be modelled as
N oc to be fulfilled.
AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Table A.5.2.8.1-3: Cell specific parameters for cell # 2 in E-UTRAN FDD to GSM handover test case;
unknown target cell
Cell 2 (GSM)
Parameter Unit
T1 T2
Absolute RF Channel
ARFCN 1
Number
RXLEV dBm -Infinity -75
A.5.2.8.2 Test Requirements
The UE shall begin to send access bursts on the new DCCH of the target cell less than 200 ms from the beginning of
time period T2.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The test requirement in this test case is expressed as:
THandover delay = 190 ms (Table 5.3.3.2.1-1) + Toffset + TUL
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 735 ETSI TS 136 133 V14.3.0 (2017-04)
Toffset: Equal to 4.65 ms is the GSM timing uncertainty from the time when the UE is ready to transmit until the start
of the next timeslot in GSM 26 multiframe structure
TUL: Equal to 4.65 ms is the time the UE has to wait in case the next timeslot is an idle frame or a SACCH frame.
This gives a total of 199.3 ms, allow 200 ms in the test case.
A.5.2.9 E-UTRAN TDD - GSM Handover; Unknown Target Cell
A.5.2.9.1 Test Purpose and Environment
This test is to verify the E-UTRAN TDD to GSM handover requirements for the case when the target GSM cell is
unknown as specified in clause 5.3.3.
The test parameters are given in Table A.5.2.9.1 -1, A.5.2.9.1 -2 and A.5.2.9.1 -3 below. The test consists of two
successive time periods, with time duration of T1, T2 respectively. At the start of time duration T1, the UE will not
have any timing information of cell 2. Starting T2, cell 2 becomes detectable and the UE receives a RRC handover
command from the network. The start of T2 is the instant when the last TTI containing the RRC message implying
handover is sent to the UE. No Gap pattern configuration shall be used.
Table A.5.2.9.1-1: General test parameters for E-UTRAN TDD to GSM handover test case; unknown
target cell
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2
parameters Channel R.6 TDD
Gap Pattern Id None No measurement gaps shall be
provided.
Initial conditions Active cell Cell 1
Neighbour cell Cell 2
Final conditions Active cell Cell 2
DRX OFF No DRX configured
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
T1 s 7
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 736 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.9.1 - 2: Cell specific parameters for cell # 1 in E-UTRAN TDD to GSM handover test case;
unknown target cell
Parameter Unit Cell 1
T1 T2
BW channel MHz 10
OCNG Patterns
defined in A.3.2.2.1
(OP.1 TDD) and in OP.1 TDD OP.2 TDD
A.3.2.2.2 (OP.2
TDD)
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
PDSCH_ RA dB
PDSCH_ RB dB
OCNG_ RA Note1 dB
OCNG_ RB Note1 dB
Ê s I ot dB 4
N oc Note 2
dBm/15 kHz -98
dB
Ê s N oc 4
RSRP Note 3 dBm/15 kHz -94
Propagation
AWGN
Condition
Note 1: OCNG shall be used such that cell 1 is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is
assumed to be constant over subcarriers and time and shall be modelled as
N oc to be fulfilled.
AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Table A.5.2.9.1 - 3: Cell specific parameters for cell # 2 in E-UTRAN TDD to GSM handover test case;
unknown target cell
Cell 2 (GSM)
Parameter Unit
T1 T2
Absolute RF Channel
ARFCN 1
Number
RXLEV dBm -Infinity -75
A.5.2.9.2 Test Requirements
The UE shall begin to send access bursts on the new DCCH of the target cell less than 200 ms from the beginning of
time period T2.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The test requirement in this test case is expressed as:
THandover delay = 190 ms (Table 5.3.3.2.1-1) + Toffset + TUL
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 737 ETSI TS 136 133 V14.3.0 (2017-04)
Toffset: Equal to 4.65 ms is the GSM timing uncertainty from the time when the UE is ready to transmit until the start
of the next timeslot in GSM 26 multiframe structure
TUL: Equal to 4.65 ms is the time the UE has to wait in case the next timeslot is an idle frame or a SACCH frame.
This gives a total of 199.3 ms, allow 200 ms in the test case.
A.5.2.10 E-UTRAN TDD to UTRAN TDD handover: unknown target cell
A.5.2.10.1 Test Purpose and Environment
This test is to verify the requirement for E-UTRAN TDD to UTRAN TDD handover requirements specified in
clause 5.3.2 when the target UTRAN TDD cell is unknown.
The test scenario comprises of 1 E-UTRAN TDD cell and 1 UTRAN TDD cell as given in tables A.5.2.10.1-1,
A.5.2.10.1-2, and A.5.2.10.1-3. No gap pattern is configured in the test case.
The test consists of two successive time periods, with time durations of T1 and T2 respectively. During time duration
T1, a RRC message implying handover to UTRA 1.28Mcps TDD cell shall be sent to the UE. The end of the last TTI
containing handover message is the beginning of T2 duration.
Table A.5.2.10.1-1: General test parameters for E-UTRAN TDD to unknown UTRAN TDD cell handover
test case
Parameter Unit Value Comment
PDSCH parameters DL Reference As specified in clause A.3.1.1.2
Measurement Channel
R.0 TDD
PCFICH/PDCCH/PHICH DL Reference As specified in clause A.3.1.2.2
parameters Measurement Channel
R.6 TDD
Initial Active cell Cell 1 E-UTRAN TDD cell
conditions Neighbour Cell 2 UTRA 1.28Mcps TDD cell
cell
Final Active cell Cell 2 UTRA 1.28Mcps TDD cell
conditions
CP length of cell 1 Normal
Uplink-downlink 1 As specified in table 4.2.2 in TS 36.211
configuration of cell 1
Special subframe 6 As specified in table 4.2.1 in TS 36.211
configuration of cell 1
Time offset between cells 3 ms Asynchronous cells
Access Barring Information Not Sent No additional delays in random access
procedure.
Assigned Sub-Channel 1 No additional delays in random access
Number procedure due to ASC.
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
T1 s 5 During T1, cell 2 shall be powered off, and
during the off time the physical layer cell
identity shall be changed.
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 738 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.10.1-2: Cell specific test parameters for E-UTRAN TDD to unknown UTRAN TDD cell
handover test case (cell 1)
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel 1
Number
BWchannel MHz 10
OCNG Patterns defined in OP.1 TDD OP.2 TDD
TS36.133 A.3.2.2.1 (OP.1
TDD) and in A.3.2.2.2
(OP.2 TDD)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 3 3
Ês I ot
dB 3 3
Ê s N oc
N oc dBm/15kHz -98
RSRP dBm/15kHz -95 -95
SCH_RP dBm/15 kHz -95 -95
Propagation Condition AWGN
Note 1: OCNG shall be used such that cell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: RSRP and SCH_RP levels have been derived from other
parameters for information purposes. They are not settable
parameters themselves.
Table A.5.2.10.1-3: Cell specific test parameters for E-UTRAN TDD to unknown UTRAN TDD cell test
case (cell 2)
Parameter Unit Cell 2 (UTRA)
Timeslot Number 0 DwPTS
T1 T2 T1 T2
UTRA RF Channel
Channel 2
NumberNote1
PCCPCH_Ec/Ior dB -3
DwPCH_Ec/Ior dB 0
OCNS_Ec/Ior dB -3
Iˆor I oc dB -infinity 13 -infinity 13
I oc dBm/1.28 MHz -80
PCCPCH RSCP dBm -infinity -70 n.a.
Propagation Condition AWGN
Note1: In the case of multi-frequency cell, the UTRA RF Channel Number is the
primary frequency’s channel number.
Note2: P-CCPCH RSCP levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 739 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.2.10.2 Test Requirements
The UE shall start to transmit the SYNCH-UL sequence in the UpPTS to Cell 2 less than 280 ms from the beginning of
time period T2.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.3.2.2.1.
Tinterrupt is defined in clause 5.3.2.2.2. Tinterrupt = 230 ms in the test as following:
Tinterrupt1= Toffset+TUL+30*FSFN+180 ms
Toffset = 10 ms; TUL = 10 ms; and FSFN = 1 for UE decoding SFN.
This gives a total of 280 ms.
A.5.2.10A E-UTRAN FDD – UTRAN FDD Multicarrier Handover with two
target cells
A.5.2.10A.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to UTRAN FDD handover requirements specified in
clause 5.3.1 in a 2 cell multicarrier configuration. It is applicable to UEs that support DC-HSDPA, DB-DC-HSDPA and
which do not support 3C-HSDPA or 4C-HSDPA.
The test parameters are given in Tables A.5.2.10A.1-1, A.5.2.10A.1-2 and A.5.2.10A.1-3. The test consists of three
successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE
does not have any timing information of Cell 2. Starting T2, Cell 2 and cell 3 become detectable and the UE is expected
to detect and send a measurement report. Gap pattern configuration with id #0 as specified in Table 8.1.2.1-1 is
configured before T2 begins to enable inter-RAT frequency monitoring.
A RRC message implying handover to cell 2 and cell 3 shall be sent to the UE during period T2, after the UE has
reported Event B2. The start of T3 is the instant when the last TTI containing the RRC message implying handover is
sent to the UE. The handover message shall contain cell 2 as the target Primary Serving HS-DSCH cell and cell 3 as the
target Secondary Serving HS-DSCH cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 740 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.10A.1-1: General test parameters for E-UTRAN FDD to UTRAN FDD handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditionsActive cell Cell 1 E-UTRAN cell
Neighbouring cell Cell 2 UTRAN cell
Final condition Active cell Cell 2 and cell 3 UTRAN cell
Channel Bandwidth (BW channel) MHz 10
Gap Pattern Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
E-UTRAN FDD measurement quantity RSRP
Inter-RAT (UTRAN FDD) measurement CPICH Ec/Io
quantity
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP
threshold for event B2
b2-Threshold2-UTRA dB -18 Absolute UTRAN CPICH Ec/Io
threshold for event B2
Hysteresis dB 0
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
UTRA RF Channel Number 1 One UTRA FDD carrier frequency
is used.
Monitored UTRA FDD cell list size 12 UTRA cells on UTRA RF channel
1 provided in the cell before T2.
Post-verification period False
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 741 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.10A.1-2: Cell specific test parameters for E-UTRAN FDD to UTRAN FDD handover test
case (cell 1)
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns OP.1 OP.1 OP.2
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 0 0 0
Ês I ot
N oc dBm/15 kHz -98
dB 0 0 0
Ê s N oc
RSRP Note 2 dBm/15 KHz -98 -98 -98
Io Note 2 dBm/9 MHz -67.21 -67.21 -67.21
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: RSRP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 742 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.10A.1-3: Cell specific test parameters for E-UTRAN FDD to UTRAN FDD multi carrier
handover test case (cell 2 and cell 3)
Cell 2 Cell 3
T1 T2 T3 T1 T2 T3
UTRA RF Channel Number Channel 1 Channel 2
Primary Serving HS-DSCH Secondary Serving HS-DSCH
Cell type
Cell Cell
CPICH_Ec/Ior dB -10 -10
PCCPCH_Ec/Ior dB -12 -12
SCH_Ec/Ior dB -12 -12
PICH_Ec/Ior dB -15 -15
HS-SCCH_Ec/Ior dB -13 -13
HS_DPDCH_Ec/Ior dB -10 -10
DPCH_Ec/Ior dB Note 1 N/A
OCNS Note 2 -2.02
Iˆor I oc dB -Inf -1.8 -1.8 -Inf -1.8 -1.8
I oc dBm/3.84
-70
MHz
Propagation Condition AWGN AWGN
Note 1: The DPCH level is controlled by the power control loop
Note 2: The power of the OCNS channel that is added shall make the total power from the cell to be equal to Ior
Note 3: The UE shall be scheduled continuously with HS-DSCH data during T3 using both cell 2 and cell
3
A.5.2.10A.2 Test Requirements
The UE shall start to transmit the UL DPCCH to Cell 2 less than 210 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.3.1.1.1.
Tinterrupt = 160 ms in the test; Tinterrupt is defined in clause 5.3.1.1.2.
This gives a total of 210 ms.
A.5.2.10B E-UTRAN TDD – UTRAN FDD Multicarrier Handover with two
target cells
A.5.2.10B.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN TDD to UTRAN FDD handover requirements specified in
clause 5.3.1 in a 2 cell multicarrier configuration. It is applicable to UEs that support DC-HSDPA, DB-DC-HSDPA and
which do not support 3C-HSDPA or 4C-HSDPA.
The test parameters are given in Tables A.5.2.10B.1-1, A.5.2.10B.1-2 and A.5.2.10B.1-3. The test consists of three
successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE
does not have any timing information of Cell 2. Starting T2, Cell 2 and cell 3 become detectable and the UE is expected
to detect and send a measurement report. Gap pattern configuration with id #0 as specified in Table 8.1.2.1-1 is
configured before T2 begins to enable inter-RAT frequency monitoring.
A RRC message implying handover to cell 2 and cell 3 shall be sent to the UE during period T2, after the UE has
reported Event B2. The start of T3 is the instant when the last TTI containing the RRC message implying handover is
sent to the UE. The handover message shall contain cell 2 as the target Primary Serving HS-DSCH cell and cell 3 as the
target Secondary Serving HS-DSCH cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 743 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.10B.1-1: General test parameters for E-UTRAN TDD to UTRAN FDD handover test case
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN TDD) DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
(E-UTRAN TDD) Channel R.6 TDD
Initial conditions Active cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel
number 1.
Final conditions Active cell Cell 2 and cell 3
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211. Applicable to cell 1.
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211. Applicable to cell 1
E-UTRAN TDD measurement quantity RSRP
Inter-RAT (UTRA FDD) measurement CPICH Ec/Io
quantity
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP threshold
for event B2
b2-Threshold2-UTRA dB -18 UTRAN FDD CPICH Ec/Io threshold
for event B2
Hysteresis dB 0
DRX OFF No DRX configured.
Time to Trigger ms 0
Filter coefficient 0
CP length Normal Applicable to cell 1
Gap pattern configuration Id 0 As specified in Table 8.1.2.1-1; to
start before T2 starts
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency
is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
UTRA RF Channel Number 1 One UTRA FDD carrier frequency is
used.
Monitored UTRA FDD cell list size 12 UTRA cells on UTRA RF channel 1
provided in the cell list before T2.
Post-verification period False Post verification is not used.
T1 s 5
T2 s ≤5
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 744 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.10B.1-2: Cell specific test parameters for E-UTRAN TDD to UTRAN FDD handover test
case (cell 1)
Parameter Unit Cell 1 (E-UTRAN)
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
OCNG Pattern defined
in A.3.2.2.1 (OP.1 TDD)
OP.1 TDD OP.2 TDD
and in A.3.2.2.2 (OP.2
TDD)
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
RSRP dBm/15 kHz -98 -98 -98
Ê s Iot dB 0 0 0
dB 0 0 0
Ê s N oc
N oc dBm/15 kHz -98
Io Note 2 dBm/9 MHz -67.21 -67.21 -67.21
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: RSRP and Io levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 745 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.10B.1-3: Cell specific test parameters for E-UTRAN TDD to UTRAN FDD multi carrier
handover test case (cell 2 and cell 3)
Cell 2 Cell 3
T1 T2 T3 T1 T2 T3
UTRA RF Channel Number Channel 1 Channel 2
Primary Serving HS-DSCH Secondary Serving HS-DSCH
Cell type
Cell Cell
CPICH_Ec/Ior dB -10 -10
PCCPCH_Ec/Ior dB -12 -12
SCH_Ec/Ior dB -12 -12
PICH_Ec/Ior dB -15 -15
HS-SCCH_Ec/Ior dB -13 -13
HS_DPDCH_Ec/Ior dB -10 -10
DPCH_Ec/Ior dB Note 1 N/A
OCNS Note 2 -2.02
Iˆor I oc dB -Inf -1.8 -1.8 -Inf -1.8 -1.8
I oc dBm/3.84
-70
MHz
Propagation Condition AWGN AWGN
Note 1: The DPCH level is controlled by the power control loop
Note 2: The power of the OCNS channel that is added shall make the total power from the cell to be equal to Ior
Note 3: The UE shall be scheduled continuously with HS-DSCH data during T3 using both cell 2 and cell
3
A.5.2.10B.2 Test Requirements
The UE shall start to transmit the UL DPCCH to Cell 2 less than 210 ms from the beginning of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.3.1.1.1.
Tinterrupt = 160 ms in the test; Tinterrupt is defined in clause 5.3.1.1.2.
This gives a total of 210 ms.
A.5.2.11 E-UTRAN FDD – UTRAN FDD Handover for 5MHz Bandwidth
A.5.2.11.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.5.2.1.1.
The parameters of this test are the same as defined in Subclause A.5.2.1.1 except that the values of the parameters in the
Table A.5.2.11.1-1 will replace the values of the corresponding parameters in A.5.2.1.1-1, and the values of the
parameters in the Table A.5.2.11.1-2 will replace the values of the corresponding parameters in A.5.2.1.1-2.
Table A.5.2.11.1-1: General test parameters for E-UTRAN FDD to UTRAN FDD handover test case for
5MHz bandwidth
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.5 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.11 FDD
E-UTRA Channel Bandwidth MHz 5
(BWchannel)
Note 1: See Table A.5.2.1.1-1 for other general test parameters.
Note 2: This test is according to the principle defined in section A.3.7.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 746 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.2.11.1-2: Cell specific test parameters for E-UTRAN FDD to UTRAN FDD handover test case
(cell 1)
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
BW channel MHz 5
OCNG Patterns OP.15 OP.15 OP.16
defined in A.3.2.1.15 FDD FDD FDD
(OP.15 FDD) and in
A.3.2.1.16 (OP.16
FDD)
Io Note 2 dBm/4.5 MHz -70.22 -70.22 -70.22
Note 1: OCNG shall be used such that both cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: RSRP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Note 3: See Table A.5.2.1.1-2 for other cell specific test parameters.
A.5.2.11.2 Test Requirements
The test requirements defined in section A.5.2.1.2 shall apply to this test case.
A.5.3 E-UTRAN Handover to Non-3GPP RATs
A.5.3.1 E-UTRAN FDD – HRPD Handover
A.5.3.1.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to HRPD handover requirements specified in clause 5.4.1.
The test parameters are given in Tables A.5.3.1.1-1, A.5.3.1.1-2 and A.5.3.1.1-3. The test consists of three successive
time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have
any timing information of Cell 2. Starting T2, Cell 2 becomes detectable and the UE is expected to detect and send a
measurement report. Gap pattern configuration with id #0 as specified in Table 8.1.2.1-1 is configured before T2 begins
to enable inter-RAT frequency monitoring.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event B2. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE. The
handover message shall contain cell 2 as the target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 747 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.1.1-1: General test parameters for E-UTRAN FDD to HRPD handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditionsActive cell Cell 1 E-UTRAN FDD cell
Neighbouring cell Cell 2 HRPD cell
Final condition Active cell Cell 2 HRPD cell
Channel Bandwidth (BW channel) MHz 10
Gap Pattern Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
E-UTRAN FDD measurement quantity RSRP
Inter-RAT (HRPD) measurement CDMA2000 HRPD Pilot
quantity Strength
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP
threshold for event B2
b2-Threshold2-CDMA2000 dB -7 Absolute ‘CDMA2000 HRPD Pilot
Strength’ threshold for event B2
Hysteresis dB 0
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
HRPD RF Channel Number 1 One HRPD carrier frequency is
used.
HRPD neighbour cell list size 8 HRPD cells on HRPD RF channel
1 provided in the cell list before
T2.
cdma2000-SearchWindowSize 8 (60 PN chips) Search window size as defined in
clause 6.3.5 in TS 36.331
T1 s 5
T2 s ≤10
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 748 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.1.1-2: Cell specific test parameters for E-UTRAN FDD cell#1 for handover to HRPD cell # 2
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in OP.1 FDD OP.2
A.3.2.1.1 (OP.1 FDD) and FDD
in A.3.2.1.2 (OP.2 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 -98
kHz
RSRP Note 3 dBm/15 -98 -98 -98
KHz
dB 0 0 0
Ê s N oc
dB 0 0 0
Ês I ot
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test
is assumed to be constant over subcarriers and time and shall be
modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 749 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.1.1-3: Cell specific test parameters for HRPD (cell # 2) for handover from E-UTRAN FDD
cell (cell #1)
Parameter Unit Cell 2 (HRPD)
T1 T2 T3
Control E b (38.4 kbps) 21
dB
Nt
Control E b (76.8 kbps) 18
dB
Nt
Iˆor I oc dB -infinity 0 0
dBm/1.2288
I oc MHz
-55
CDMA2000 HRPD Pilot -infinity -3 -3
dB
Strength
Propagation Condition AWGN
A.5.3.1.2 Test Requirements
The UE shall start transmission of the reverse control channel in HRPD to Cell 2 less than 127 ms from the beginning
of time period T3.
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.4.1.1.1.
Tinterrupt = 76.66 ms in the test; Tinterrupt is defined in clause 5.4.1.1.2.
This gives a total of 126.66 ms, allow 127 ms in the test.
A.5.3.2 E-UTRAN FDD – cdma2000 1X Handover
A.5.3.2.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to cdma2000 1X handover requirements specified in
clause 5.4.2.
The test parameters are given in Tables A.5.3.2.1-1, A.5.3.2.1-2 and A.5.3.2.1-3. The test consists of three successive
time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have
any timing information of Cell 2. Starting T2, Cell 2 becomes detectable and the UE is expected to detect and send a
measurement report. Gap pattern configuration with id #0 as specified in Table 8.1.2.1-1 is configured before T2 begins
to enable inter-RAT frequency monitoring.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event B2. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE. The
handover message shall contain cell 2 as the target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 750 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.2.1-1: General test parameters for E-UTRAN FDD to cdma2000 1X handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditionsActive cell Cell 1 E-UTRAN FDD cell
Neighbouring cell Cell 2 cdma2000 1X cell
Final condition Active cell Cell 2 cdma2000 1X cell
Channel Bandwidth (BW channel) MHz 10
Gap Pattern Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
E-UTRAN FDD measurement quantity RSRP
Inter-RAT (cdma2000 1X) measurement CDMA2000 1xRTT Pilot
quantity Strength
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP
threshold for event B2
b2-Threshold2-CDMA2000 dB -14 Absolute ‘CDMA2000 1xRTT Pilot
Strength’ threshold for event B2
Hysteresis dB 0
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
cdma2000 1X RF Channel Number 1 One HRPD carrier frequency is
used.
cdma2000 1X neighbour cell list size 8 cdma2000 1X cells on cdma2000
1X RF channel 1 provided in the
cell list before T2.
cdma2000-SearchWindowSize 8 (60 PN chips) Search window size as defined in
clause 6.3.5 in TS 36.331
T1 s 5
T2 s ≤10
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 751 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.2.1-2: Cell specific test parameters for E-UTRAN FDD cell#1 for handover to cdma2000 1X
cell # 2
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in OP.1 FDD OP.2
A.3.2.1.1 (OP.1 FDD) and FDD
in A.3.2.1.2 (OP.2 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 -98
kHz
RSRP Note 3 dBm/15 -98 -98 -98
KHz
dB 0 0 0
Ê s N oc
dB 0 0 0
Ês I ot
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the
test is assumed to be constant over subcarriers and time and shall
N
oc to be fulfilled.
be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 752 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.2.1-3: Cell specific test parameters for cdma2000 1X (cell # 2) for handover from E-UTRAN
FDD cell (cell #1)
Parameter Unit Cell 2 (cdma2000 1X)
T1 T2 T3
Pilot E c
dB -7
I or
Sync E c
dB -16
I or
Paging E c (4.8 kbps)
dB -12
I or
Iˆor I oc dB -infinity 0 0
dBm/1.2288
I oc MHz
-55
CDMA2000 1xRTT Pilot -infinity -10 -10
dB
Strength
Propagation Condition AWGN
A.5.3.2.2 Test Requirements
The UE shall start transmission of the reverse control channel in cdma2000 1X to Cell 2 less than 300 ms from the
beginning of time period T3.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 130 ms, which is specified in clause 5.4.2.1.1.
Tinterrupt = 170 ms in the test; Tinterrupt is defined in clause 5.4.2.1.2.
This gives a total of 300 ms.
A.5.3.3 E-UTRAN FDD – HRPD Handover; Unknown Target Cell
A.5.3.3.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to HRPD handover requirements for the case when the
target HRPD cell is unknown as specified in clause 5.4.1.
The test parameters are given in Tables A.5.3.3.1-1, A.5.3.3.1-2 and A.5.3.3.1-3. The test consists of two successive
time periods, with time durations of T1 and T2 respectively. At the start of time duration T1, the UE does not have any
timing information of cell 2. During time period T1, message containing Information Element systemTimeInfo as
defined in clause 6.3.1 of TS 36.331 [2] shall be sent by the System Simulator (SS). No gap patterns are configured in
the test case. No HRPD neighbour cell list shall be provided to the UE.
A RRC message implying handover to the unknown HRPD cell shall be sent to the UE towards the end of the time
period T1. The start of T2 is the instant when the last TTI containing the RRC message implying handover is sent to the
UE. The handover message shall contain cell 2 as the target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 753 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.3.1-1: General test parameters for E-UTRAN FDD to HRPD handover test case; unknown
target HRPD cell
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditions Active cell Cell 1 E-UTRAN FDD cell
Neighbouring cell Cell 2 HRPD cell
Final condition Active cell Cell 2 HRPD cell
Channel Bandwidth (BW channel) MHz 10
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
HRPD RF Channel Number 1 One HRPD carrier frequency is
used.
cdma2000-SearchWindowSize 8 (60 PN chips) Search window size as defined in
clause 6.3.5 in TS 36.331
T1 s ≤5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 754 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.3.1-2: Cell specific test parameters for E-UTRAN FDD cell#1 for handover to unknown
HRPD cell # 2
Parameter Unit Cell 1 (E-UTRAN FDD)
T1 T2
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in OP.1 FDD
A.3.2.1.1 (OP.1 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 kHz -98 -98
dB 0 0
Ê s N oc
dB 0 0
Ês I ot
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.5.3.3.1-3: Cell specific test parameters for unknown HRPD (cell # 2) for handover from E-
UTRAN FDD cell (cell #1)
Parameter Unit Cell 2 (HRPD)
T1 T2
Control E b (38.4 21
Nt dB
kbps)
Control E b (76.8 18
Nt dB
kbps)
Iˆor I oc dB -infinity 0
dBm/1.22
I oc 88 MHz
-55
CDMA2000 HRPD -infinity -3
dB
Pilot Strength
Propagation Condition AWGN
A.5.3.3.2 Test Requirements
The UE shall start transmission of the reverse control channel in HRPD to Cell 2 less than 127 ms from the beginning
of time period T2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 755 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay is expressed as: RRC procedure delay + Tinterrupt, where:
Tinterrupt also includes time to detect HRPD cell; see clause 5.4.1.1.2
This gives a total of 126.66 ms, allow 127 ms in the test case.
A.5.3.4 E-UTRAN FDD – cdma2000 1X Handover; Unknown Target cell
A.5.3.4.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN FDD to cdma2000 1X handover requirements for the case when
the target cdma2000 1X cell is unknown as specified in clause 5.4.2.
The test parameters are given in Tables A.5.3.4.1-1, A.5.3.4.1-2 and A.5.3.4.1-3. The test consists of two successive
time periods, with time durations of T1 and T2 respectively. At the start of time duration T1, the UE does not have any
timing information of cell 2. During time period T1, message containing Information Element systemTimeInfo as
defined in clause 6.3.1 of TS 36.331 [2] shall be sent by the System Simulator (SS). No gap patterns are configured in
the test case. No cdma2000 1X neighbour cell list shall be provided to the UE.
A RRC message implying handover to the unknown cdma2000 1X cell shall be sent to the UE towards the end of the
time period T1. The start of T2 is the instant when the last TTI containing the RRC message implying handover is sent
to the UE. The handover message shall contain cell 2 as the target cell.
Table A.5.3.2.1-1: General test parameters for E-UTRAN FDD to cdma2000 1X handover test case;
unknown target cdma2000 1X cell
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditions Active cell Cell 1 E-UTRAN FDD cell
Neighbouring cell Cell 2 cdma2000 1X cell
Final condition Active cell Cell 2 cdma2000 1X cell
Channel Bandwidth (BW channel) MHz 10
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
cdma2000 1X RF Channel Number 1 One HRPD carrier frequency is
used.
cdma2000-SearchWindowSize 8 (60 PN chips) Search window size as defined in
clause 6.3.5 in TS 36.331
T1 s ≤5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 756 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.2.1-2: Cell specific test parameters for E-UTRAN FDD cell#1 for handover to unknown
cdma2000 1X cell # 2
Parameter Unit Cell 1 (E-UTRAN FDD)
T1 T2
E-UTRA RF Channel number 1
BW channel MHz 10
OCNG Patterns defined in OP.1 FDD
A.3.2.1.1 (OP.1 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 kHz -98 -98
dB 0 0
Ê s N oc
dB 0 0
Ês I ot
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
Table A.5.3.2.1-3: Cell specific test parameters for unknown cdma2000 1X (cell # 2) for handover from
E-UTRAN FDD cell (cell #1)
Parameter Unit Cell 2 (cdma2000 1X)
T1 T2
Pilot E c
dB -7
I or
Sync E c
dB -16
I or
Paging E c (4.8 kbps)
dB -12
I or
Iˆor I oc dB -infinity 0
dBm/1.22
I oc 88 MHz
-55
CDMA2000 1xRTT -infinity -10
dB
Pilot Strength
Propagation Condition AWGN
A.5.3.4.2 Test Requirements
The UE shall start transmission of the reverse control channel in cdma2000 1X to Cell 2 less than 300 ms from the
beginning of time period T2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 757 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay is expressed as: RRC procedure delay + Tinterrupt, where:
Tinterrupt also includes time to detect cdma2000 1X cell; see clause 5.4.2.1.2
This gives a total of 300 ms.
A.5.3.5 E-UTRAN TDD – HRPD Handover
A.5.3.5.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN TDD to HRPD handover requirements specified in clause 5.4.1.
The test parameters are given in Tables A.5.3.5.1-1, A.5.3.5.1-2 and A.5.3.5.1-3. The test consists of three successive
time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have
any timing information of Cell 2. Starting T2, Cell 2 becomes detectable and the UE is expected to detect and send a
measurement report. Gap pattern configuration with id #0 as specified in Table 8.1.2.1-1 is configured before T2 begins
to enable inter-RAT frequency monitoring.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event B2. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE. The
handover message shall contain cell 2 as the target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 758 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.5.1-1: General test parameters for E-UTRAN TDD to HRPD handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Initial conditionsActive cell Cell 1 E-UTRAN TDD cell
Neighbouring cell Cell 2 HRPD cell
Final condition Active cell Cell 2 HRPD cell
Channel Bandwidth (BW channel) MHz 10
Gap Pattern Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
E-UTRAN TDD measurement quantity RSRP
Inter-RAT (HRPD) measurement CDMA2000 HRPD Pilot
quantity Strength
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP
threshold for event B2
b2-Threshold2-CDMA2000 dB -7 Absolute ‘CDMA2000 HRPD Pilot
Strength’ threshold for event B2
Hysteresis dB 0
TimeToTrigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
Uplink-downlink configuration of cell 1 1 As specified in table 4.2.2 in TS
36.211
Special subframe configuration of cell 1 6 As specified in table 4.2.1 in TS
36.211
HRPD RF Channel Number 1 One HRPD carrier frequency is
used.
HRPD neighbour cell list size 8 HRPD cells on HRPD RF channel
1 provided in the cell list before
T2.
cdma2000-SearchWindowSize 8 (60 PN chips) Search window size as defined in
clause 6.3.5 in TS 36.331
T1 s 5
T2 s ≤10
T3 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 759 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.5.1-2: Cell specific test parameters for E-UTRAN TDD cell#1 for handover to HRPD cell # 2
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in OP.1 TDD OP.2
TS36.133 A.3.2.2.1 (OP.1 TDD
TDD) and in A.3.2.2.2
(OP.2 TDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 -98
kHz
RSRP Note 3 dBm/15 -98 -98 -98
KHz
dB 0 0 0
Ê s N oc
dB 0 0 0
Ês I ot
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the
test is assumed to be constant over subcarriers and time and shall
be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Table A.5.3.5.1-3: Cell specific test parameters for HRPD (cell # 2) for handover from E-UTRAN TDD
cell (cell #1)
Parameter Unit Cell 2 (HRPD)
T1 T2 T3
Control E b (38.4 kbps) 21
dB
Nt
Control E b (76.8 kbps) 18
dB
Nt
Iˆor I oc dB -infinity 0 0
dBm/1.2288
I oc MHz
-55
CDMA2000 HRPD Pilot -infinity -3 -3
dB
Strength
Propagation Condition AWGN
A.5.3.5.2 Test Requirements
The UE shall start transmission of the reverse control channel in HRPD to Cell 2 less than 127 ms from the beginning
of time period T3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 760 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct handovers observed during repeated tests shall be at least 90%.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 50 ms, which is specified in clause 5.4.1.1.1.
Tinterrupt = 76.66 ms in the test; Tinterrupt is defined in clause 5.4.1.1.2.
This gives a total of 126.66 ms, allow 127 ms in the test.
A.5.3.6 E-UTRAN TDD – cdma2000 1X Handover
A.5.3.6.1 Test Purpose and Environment
This test is to verify the requirement for the E-UTRAN TDD to cdma2000 1X handover requirements specified in
clause 5.4.2.
The test parameters are given in Tables A.5.3.6.1-1, A.5.3.6.1-2 and A.5.3.6.1-3. The test consists of three successive
time periods, with time durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have
any timing information of Cell 2. Starting T2, Cell 2 becomes detectable and the UE is expected to detect and send a
measurement report. Gap pattern configuration with id #0 as specified in Table 8.1.2.1-1 is configured before T2 begins
to enable inter-RAT frequency monitoring.
A RRC message implying handover shall be sent to the UE during period T2, after the UE has reported Event B2. The
start of T3 is the instant when the last TTI containing the RRC message implying handover is sent to the UE. The
handover message shall contain cell 2 as the target cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 761 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.6.1-1: General test parameters for E-UTRAN TDD to cdma2000 1X handover test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Initial conditionsActive cell Cell 1 E-UTRAN TDD cell
Neighbouring cell Cell 2 cdma2000 1X cell
Final condition Active cell Cell 2 cdma2000 1X cell
Channel Bandwidth (BW channel) MHz 10
Gap Pattern Id 0 As specified in Table 8.1.2.1-1
started before T2 starts
E-UTRAN TDD measurement quantity RSRP
Inter-RAT (cdma2000 1X) measurement CDMA2000 1xRTT Pilot
quantity Strength
b2-Threshold1 dBm -90 Absolute E-UTRAN RSRP
threshold for event B2
b2-Threshold2-CDMA2000 dB -14 Absolute ‘CDMA2000 1xRTT Pilot
Strength’ threshold for event B2
Hysteresis dB 0
TimeToTrigger S 0
Filter coefficient 0 L3 filtering is not used
DRX OFF Non-DRX test
Access Barring Information - Not sent No additional delays in random
access procedure
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
cdma2000 1X RF Channel Number 1 One cdma2000 1X carrier
frequency is used.
cdma2000 1X neighbour cell list size 8 cdma2000 1X cells on cdma2000
1X RF channel 1 provided in the
cell list before T2.
cdma2000-SearchWindowSize 8 (60 PN chips) Search window size as defined in
clause 6.3.5 in TS 36.331
T1 S 5
T2 S ≤10
T3 S 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 762 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.5.3.6.1-2: Cell specific test parameters for E-UTRAN TDD cell#1 for handover to cdma2000 1X
cell # 2
Parameter Unit Cell 1 (E-UTRA)
T1 T2 T3
E-UTRA RF Channel 1
number
BW channel MHz 10
OCNG Patterns defined in OP.1 TDD OP.2
A.3.2.2.1 (OP.1 TDD) and TDD
in A.3.2.2.2 (OP.2 TDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 -98
kHz
RSRP Note 3 dBm/15 -98 -98 -98
KHz
dB 0 0 0
Ê s N oc
dB 0 0 0
Ês I ot
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the
test is assumed to be constant over subcarriers and time and shall
N
oc to be fulfilled.
be modelled as AWGN of appropriate power for
Note 3: RSRP levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Table A.5.3.6.1-3: Cell specific test parameters for cdma2000 1X (cell # 2) for handover from E-UTRAN
TDD cell (cell #1)
Parameter Unit Cell 2 (cdma2000 1X)
T1 T2 T3
Pilot E c
dB -7
I or
Sync E c
dB -16
I or
Paging E c (4.8 kbps)
dB -12
I or
Iˆor I oc dB -infinity 0 0
dBm/1.2288
I oc MHz
-55
CDMA2000 1xRTT Pilot -infinity -10 -10
dB
Strength
Propagation Condition AWGN
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 763 ETSI TS 136 133 V14.3.0 (2017-04)
A.5.3.6.2 Test Requirements
The UE shall start transmission of the reverse control channel in cdma2000 1X to Cell 2 less than 300 ms from the
beginning of time period T3.
NOTE: The handover delay can be expressed as: RRC procedure delay + Tinterrupt, where:
RRC procedure delay = 130 ms, which is specified in clause 5.4.2.1.1.
Tinterrupt = 170 ms in the test; Tinterrupt is defined in clause 5.4.2.1.2.
This gives a total of 300 ms.
A.6 RRC Connection Control
A.6.1 RRC Re-establishment
A.6.1.1 E-UTRAN FDD Intra-frequency RRC Re-establishment
A.6.1.1.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.1.2.
The test parameters are given in table A.6.1.1.1-1 and table A.6.1.1.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.1.1-1: General test parameters for E-UTRAN FDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 ms 200
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 764 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.1.1-2: Cell specific test parameters for E-UTRAN FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 1.54 -Infinity -Infinity -3.79 4 4
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 7 -Infinity -Infinity 4 4 4
Ês N oc
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.1.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA FDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI + TPRACH
Nfreq = 1
Tsearch = 100 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 765 ETSI TS 136 133 V14.3.0 (2017-04)
TSI = 1280 ms; it is the time required for receiving all the relevant system information as defined in TS 36.331
for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1445 ms, allow 1.5 s in the test case.
A.6.1.2 E-UTRAN FDD Inter-frequency RRC Re-establishment
A.6.1.2.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD inter-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.1.2.
The test parameters are given in table A.6.1.1.2-1 and table A.6.1.1.2-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of radio link failure. At the start of time period T3, cell 2,
which is the neighbour cell, is activated.
Table A.6.1.2.1-1: General test parameters for E-UTRAN FDD inter-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditionsActive cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number (cell 1) 1
E-UTRA RF Channel Number (cell 2) 2
E-UTRA FDD inter-frequency carrier list 1 2 E-UTRA FDD carrier
size frequencies in total: 1 intra-
frequency and 1 inter-frequency
Channel Bandwidth (BW channel) MHz 10
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 5000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 ms 200
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 766 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.2.1-2: Cell specific test parameters for E-UTRAN FDD inter-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 -Infinity -Infinity -Infinity -Infinity 7
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 4 -Infinity -Infinity - Infinity - Infinity 7
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -Infinity -Infinity - Infinity -Infinity -91
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.2.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to an unknown E-UTRA FDD inter frequency cell shall be less than 3 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI + TPRACH
Nfreq = 2
Tsearch = 800 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 767 ETSI TS 136 133 V14.3.0 (2017-04)
TSI = 1280 ms; it is the time required for receiving all the relevant system information as defined in TS 36.331
for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 2945 ms, allow 3 s in the test case.
A.6.1.3 E-UTRAN TDD Intra-frequency RRC Re-establishment
A.6.1.3.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA TDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.1.2.
The test parameters are given in table A.6.1.3.1-1 and table A.6.1.3.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.3.1-1: General test parameters for E-UTRAN TDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells μs 3 Synchronous cells
T1 s 5
T2 ms 200
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 768 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.3.1-2: Cell specific test parameters for E-UTRAN TDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 TDD OP.2 TDD OP.1 TDD
defined in A.3.2.2.1 TDD TDD TDD
(OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 1.54 -Infinity -Infinity -3.79 4 4
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 7 -Infinity -Infinity 4 4 4
Ês N oc
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.3.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA TDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI + TPRACH
Nfreq = 1
Tsearch = 100 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 769 ETSI TS 136 133 V14.3.0 (2017-04)
TSI = 1280 ms; it is the time required for receiving all the relevant system information as defined in TS 36.331
for the target E-UTRAN TDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1445 ms, allow 1.5 s in the test case.
A.6.1.4 E-UTRAN TDD Inter-frequency RRC Re-establishment
A.6.1.4.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA TDD inter-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.1.2.
The test parameters are given in table A.6.1.4.1-1 and table A.6.1.4.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of radio link failure. At the start of time period T3, cell 2,
which is the neighbour cell, is activated.
Table A.6.1.4.1-1: General test parameters for E-UTRAN TDD inter-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Initial conditionsActive cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number (cell 1) 1
E-UTRA RF Channel Number (cell 2) 2
E-UTRA TDD inter-frequency carrier list 1 2 E-UTRA TDD carrier
size frequencies in total: 1 intra-
frequency and 1 inter-frequency
Channel Bandwidth (BW channel) MHz 10
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 5000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells μs 3 Synchronous cells
T1 s 5
T2 ms 200
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 770 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.4.1-2: Cell specific test parameters for E-UTRAN TDD inter-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 TDD OP.2 TDD OP.1 TDD
defined in A.3.2.2.1 TDD TDD TDD
(OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 -Infinity -Infinity -Infinity -Infinity 7
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 4 -Infinity -Infinity - Infinity - Infinity 7
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -Infinity -Infinity - Infinity -Infinity -91
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.4.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to an unknown E-UTRA TDD inter frequency cell shall be less than 3 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI + TPRACH
Nfreq = 2
Tsearch = 800 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 771 ETSI TS 136 133 V14.3.0 (2017-04)
TSI = 1280 ms; it is the time required for receiving all the relevant system information as defined in TS 36.331
for the target E-UTRAN TDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 2945 ms, allow 3 s in the test case.
A.6.1.5 E-UTRAN FDD Intra-frequency RRC Re-establishment for 5MHz
bandwidth
A.6.1.5.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.6.1.1.1.
The parameters of this test are the same as defined in Subclause A.6.1.1.1 except that the values of the parameters in the
Table A.6.1.5.1-1 will replace the values of the corresponding parameters in A.6.1.1.1-1, and the values of the
parameters in the Table A.6.1.5.1-2 will replace the values of the corresponding parameters in A.6.1.1.1-2.
Table A.6.1.5.1-1: General test parameters for E-UTRAN FDD intra-frequency RRC Re-establishment
test case for 5MHz bandwidth
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.5 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.11 FDD
Channel Bandwidth (BW channel) MHz 5
Note 1: See Table A.6.1.1.1-1 for the other parameters.
Note 2: This test is according to the principle defined in section A.3.7.2.
Table A.6.1.5.1-2: Cell specific test parameters for E-UTRAN FDD intra-frequency RRC Re-
establishment test case for 5MHz bandwidth
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
BW channel MHz 5 5
OCNG Patterns OP.15 OP.15 OP.16 OP.16 FDD OP.16 FDD OP.15 FDD
defined in A.3.2.1.15 FDD FDD FDD
(OP.15 FDD) and
A.3.2.1.16 (OP.16
FDD)
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: See Table A.6.1.5.1-2 for the other parameters.
A.6.1.5.2 Test Requirements
The test requirements defined in section A.6.1.1.2 shall apply to this test case.
A.6.1.6 E-UTRAN FD-FDD Intra-frequency RRC Re-establishment for UE
category 0
A.6.1.6.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.1.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 772 ETSI TS 136 133 V14.3.0 (2017-04)
The test parameters are given in table A.6.1.6.1-1 and table A.6.1.6.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.6.1-1: General test parameters for E-UTRAN FDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.3
Channel R.13 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 ms 200
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 773 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.6.1-2: Cell specific test parameters for E-UTRAN FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -Infinity -Infinity -3.79 4 4
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 7 -Infinity -Infinity 4 4 4
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.6.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA FDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI + TPRACH
Nfreq = 1
Tsearch = 100 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 774 ETSI TS 136 133 V14.3.0 (2017-04)
TSI = 1280 ms; it is the time required for receiving all the relevant system information as defined in TS 36.331
for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1445 ms, allow 1.5 s in the test case.
A.6.1.7 E-UTRAN HD-FDD Intra-frequency RRC Re-establishment for UE
category 0
A.6.1.7.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.1.2.
The test parameters are given in table A.6.1.7.1-1 and table A.6.1.7.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.7.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.4
Channel R.1 HD-FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.3
Channel R.3 HD-FDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 ms 200
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 775 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.7.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 FDD OP.2 FDD OP.1 FDD
defined in A.3.2.1.1 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -Infinity -Infinity -3.79 4 4
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 7 -Infinity -Infinity 4 4 4
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.7.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA FDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI + TPRACH
Nfreq = 1
Tsearch = 100 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 776 ETSI TS 136 133 V14.3.0 (2017-04)
TSI = 1280 ms; it is the time required for receiving all the relevant system information as defined in TS 36.331
for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1445 ms, allow 1.5 s in the test case.
A.6.1.8 E-UTRAN TDD Intra-frequency RRC Re-establishment for UE
category 0
A.6.1.8.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA TDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.1.2.
The test parameters are given in table A.6.1.8.1-1 and table A.6.1.8.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.8.1-1: General test parameters for E-UTRAN TDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.5
Channel R.12 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Initial conditions
Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells μs 3 Synchronous cells
T1 s 5
T2 ms 200
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 777 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.8.1-2: Cell specific test parameters for E-UTRAN TDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns OP.1 OP.1 OP.2 OP.2 TDD OP.2 TDD OP.1 TDD
defined in A.3.2.2.1 TDD TDD TDD
(OP.1 TDD) and in
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -Infinity -Infinity -3.79 4 4
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 7 -Infinity -Infinity 4 4 4
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.8.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA TDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI + TPRACH
Nfreq = 1
Tsearch = 100 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 778 ETSI TS 136 133 V14.3.0 (2017-04)
TSI = 1280 ms; it is the time required for receiving all the relevant system information as defined in TS 36.331
for the target E-UTRAN TDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1445 ms, allow 1.5 s in the test case.
A.6.1.9 E-UTRAN FD-FDD Intra-frequency RRC Re-establishment for Cat-
M1 UE in CEModeA
A.6.1.9.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.7.2.
The test parameters are given in table A.6.1.9.1-1 and table A.6.1.9.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.9.1-1: General test parameters for E-UTRAN FDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
PRACH Configuration PRACH_2CE As specified in A.3.16
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 ms 400
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 779 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.9.1-2: Cell specific test parameters for E-UTRAN FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.4.1
Channel R.21 FDD
MPDCCH parameters DL Reference Measurement As specified in clause A.3.1.3.1
Channel R.17 FDD
OCNG Patterns OP.21 OP.21 OP.6 OP.6 FDD OP.6 FDD OP.21 FDD
defined in A.3.2.1.21 FDD FDD FDD
(OP.21 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
-3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -Infinity -Infinity -3.79 4 4
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 7 -Infinity -Infinity 4 4 4
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.9.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA FDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI-EUTRA-M1-CEModeA + TPRACH
Nfreq = 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 780 ETSI TS 136 133 V14.3.0 (2017-04)
Tsearch = 0 ms
TSI-EUTRA-M1-CEModeA = 1280 ms; it is the time required for receiving all the relevant system information as defined
in TS 36.331 for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1345 ms, allow 1.5 s in the test case.
A.6.1.10 E-UTRAN HD-FDD Intra-frequency RRC Re-establishment for Cat-
M1 UE in CEModeA
A.6.1.10.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.7.2.
The test parameters are given in table A.6.1.10.1-1 and table A.6.1.10.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.10.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
PRACH Configuration PRACH_2CE As specified in A.3.16
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 ms 400
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 781 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.10.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.4.2
Channel R.11 HD-FDD
MPDCCH parameters DL Reference Measurement As specified in clause A.3.1.3.2
Channel R.7 HD-FDD
OCNG Patterns OP.21 OP.21 OP.6 OP.6 FDD OP.6 FDD OP.21 FDD
defined in A.3.2.1.21 FDD FDD FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
-3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -Infinity -Infinity -3.79 4 4
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 7 -Infinity -Infinity 4 4 4
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.10.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA FDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI-EUTRA-M1-CEModeA + TPRACH
Nfreq = 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 782 ETSI TS 136 133 V14.3.0 (2017-04)
Tsearch = 0 ms
TSI-EUTRA-M1-CEModeA = 1280 ms; it is the time required for receiving all the relevant system information as defined
in TS 36.331 for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1345 ms, allow 1.5 s in the test case.
A.6.1.11 E-UTRAN TDD Intra-frequency RRC Re-establishment for Cat-M1
UE in CEModeA
A.6.1.11.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA TDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.7.2.
The test parameters are given in table A.6.1.11.1-1 and table A.6.1.11.1-2 below. The test consists of 3 successive time
periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell,
is deactivated. The time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.11.1-1: General test parameters for E-UTRAN TDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
PRACH Configuration PRACH_2CE As specified in A.3.16
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells μs 3 Synchronous cells
T1 s 5
T2 ms 400
T3 s 3
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 783 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.11.1-2: Cell specific test parameters for E-UTRAN TDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.4.3
Channel R.17 TDD
MPDCCH parameters DL Reference Measurement As specified in clause A.3.1.3.3
Channel R.15 TDD
OCNG Patterns OP.11 OP.11 OP.2 OP.2 TDD OP.2 TDD OP.11 TDD
defined in A.3.2.2.11 TDD TDD TDD
(OP.11 TDD) and in
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
-3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -Infinity -Infinity -3.79 4 4
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 7 -Infinity -Infinity 4 4 4
RSRP Note 3 dBm/15 KHz -91 -Infinity -Infinity -94 -94 -94
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.11.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA TDD intra frequency cell shall be less than 1.5 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI-EUTRA-M1-CEModeA + TPRACH
Nfreq = 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 784 ETSI TS 136 133 V14.3.0 (2017-04)
Tsearch = 0 ms
TSI-EUTRA-M1-CEModeA = 1280 ms; it is the time required for receiving all the relevant system information as defined
in TS 36.331 for the target E-UTRAN TDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 1345 ms, allow 1.5 s in the test case.
A.6.1.12 E-UTRAN FD-FDD Intra-frequency RRC Re-establishment for Cat-
M1 UE in CEModeB
A.6.1.12.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.7.2.
The test parameters are given in table A.6.1.12.1-1 and table A.6.1.12.1-2 below. The test consists of 4 successive time
periods, with time duration of T1, T2, T3 and T4 respectively. During T1, both cell 1 and cell 2 are in CEModeA. At
the start of time period T3, cell 1, which is the active cell, is deactivated. The time period T4 starts after the occurrence
of the radio link failure.
Table A.6.1.12.1-1: General test parameters for E-UTRAN FDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
PRACH Configuration PRACH_3CE As specified in A.3.16
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 s 5
T3 ms 4000
T4 s 9
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 785 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.12.1-2: Cell specific test parameters for E-UTRAN FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T4 T1 T2 T3 T4
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH parameters DL Reference Measurement Channel R.23 FDD
MPDCCH parameters DL Reference Measurement Channel R.19 FDD
OCNG Patterns defined in OP.21 OP.21 OP.21 OP.6 OP.6 OP.6 OP.6 OP.21
A.3.2.1.21 (OP.21 FDD) and FDD FDD FDD FDD FDD FDD FDD FDD
in A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
-3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -12.14 -Infinity -Infinity -3.79 -12.14 -12 -12
N oc Note 2 dBm/15 -98
KHz
Ês N oc dB 7 -15 -Infinity -Infinity 4 -12 -12 -12
RSRP Note 3 dBm/15 -91 -113 -Infinity -Infinity -94 -110 -110 -110
KHz
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density
is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.12.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T4, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA FDD intra frequency cell shall be less than 7 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI-EUTRA-M1-CEModeB + TPRACH
Nfreq = 1
Tsearch = 0 ms
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 786 ETSI TS 136 133 V14.3.0 (2017-04)
TSI-EUTRA-M1-CEModeB = 6400 ms; it is the time required for receiving all the relevant system information as defined
in TS 36.331 for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 6485 ms, allow 7 s in the test case.
A.6.1.13 E-UTRAN HD-FDD Intra-frequency RRC Re-establishment for Cat-
M1 UE in CEModeB
A.6.1.13.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.7.2.
The test parameters are given in table A.6.1.13.1-1 and table A.6.1.13.1-2 below. The test consists of 4 successive time
periods, with time duration of T1, T2, T3 and T4 respectively. During T1, both cell 1 and cell 2 are in CEModeA. At
the start of time period T3, cell 1, which is the active cell, is deactivated. The time period T4 starts after the occurrence
of the radio link failure.
Table A.6.1.13.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
PRACH Configuration PRACH_3CE As specified in A.3.16
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
PRACH configuration index 4 As specified in table 5.7.1-2 in TS
36.211
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 s 5
T3 ms 4000
T4 s 9
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 787 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.13.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T4 T1 T2 T3 T4
E-UTRA RF 1 1
Channel Number
BW channel MHz 10 10
PDSCH parameters DL Reference Measurement Channel As specified in clause A.3.1.4.5
R.13 HD-FDD
MPDCCH DL Reference Measurement Channel As specified in clause A.3.1.3.5
parameters R.9 HD-FDD
OCNG Patterns OP.21 OP.21 OP.21 OP.6 OP.6 OP.6 OP.6 OP.21
defined in FDD FDD FDD FDD FDD FDD FDD FDD
A.3.2.1.21 (OP.1
FDD) and in
A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
-3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -15.27 -Infinity -Infinity -3.79 -12.14 -12 -12
N oc Note 2 dBm/15 -98
KHz
Ês N oc dB 7 -15 -Infinity -Infinity 4 -12 -12 -12
RSRP Note 3 dBm/15 -91 -113 -Infinity -Infinity -94 -110 -110 -110
KHz
Propagation AWGN
Condition
Antenna 2x1 2x1
Configuration
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.13.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T4, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA FDD intra frequency cell shall be less than 7 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 788 ETSI TS 136 133 V14.3.0 (2017-04)
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI-EUTRA-M1-CEModeB + TPRACH
Nfreq = 1
Tsearch = 0 ms
TSI-EUTRA-M1-CEModeB = 6400 ms; it is the time required for receiving all the relevant system information as defined
in TS 36.331 for the target E-UTRAN FDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 6465 ms, allow 7 s in the test case.
A.6.1.14 E-UTRAN TDD Intra-frequency RRC Re-establishment for Cat-M1
UE in CEModeB
A.6.1.14.1 Test Purpose and Environment
The purpose is to verify that the E-UTRA TDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements in clause 6.7.2.
The test parameters are given in table A.6.1.14.1-1 and table A.6.1.14.1-2 below. The test consists of 4 successive time
periods, with time duration of T1, T2, T3 and T4 respectively. During T1, both cell 1 and cell 2 are in CEModeA. At
the start of time period T3, cell 1, which is the active cell, is deactivated. The time period T4 starts after the occurrence
of the radio link failure.
Table A.6.1.14.1-1: General test parameters for E-UTRAN TDD intra-frequency RRC Re-establishment
test case
Parameter Unit Value Comment
Initial conditions Active cell Cell 1
Neighbouring cell Cell 2
Final condition Active cell Cell 2
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
PRACH Configuration PRACH_3CE As specified in A.3.16
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync
indications from lower layers
T310 ms 0 Radio link failure timer; T310 is
disabled
T311 ms 3000 RRC re-establishment timer
DRX OFF
CP length Normal
Access Barring Information - Not Sent No additional delays in random
access procedure.
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211
PRACH configuration index 53 As specified in table 5.7.1-3 in TS
36.211
Time offset between cells μs 3 Synchronous cells
T1 s 5
T2 s 5
T3 ms 4000
T4 s 9
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 789 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.14.1-2: Cell specific test parameters for E-UTRAN TDD intra-frequency RRC Re-
establishment test case
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T4 T1 T2 T3 T4
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH parameters DL Reference Measurement Channel As specified in clause A.3.1.4.6
R.19 TDD
MPDCCH parameters DL Reference Measurement Channel As specified in clause A.3.1.3.6
R.17 TDD
OCNG Patterns OP.11 OP.11 OP.11 OP.2 OP.2 OP.2 OP.2T OP.11
defined in A.3.2.2.11 TDD TDD TDD TDD TDD TDD DD TDD
(OP.11 TDD) and in
A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB 0 0
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 1.54 -15.27 -Infinity -Infinity -3.79 -12.14 -12 -12
N oc Note 2 dBm/15 -98
KHz
Ês N oc dB 7 -15 -Infinity -Infinity 4 -12 -12 -12
RSRP Note 3 dBm/15 -91 -113 -Infinity -Infinity -94 -110 -110 -110
KHz
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.6.1.14.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send PRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to a known E-UTRA TDD intra frequency cell shall be less than 7 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE_re-establish_delay.
Where:
TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
TUE_re-establish_delay = 50 ms + Nfreq* Tsearch + TSI-EUTRA-M1-CEModeB + TPRACH
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 790 ETSI TS 136 133 V14.3.0 (2017-04)
Nfreq = 1
Tsearch = 0 ms
TSI-EUTRA-M1-CEModeB = 6400 ms; it is the time required for receiving all the relevant system information as defined
in TS 36.331 for the target E-UTRAN TDD cell.
TPRACH = 15 ms; it is the additional delay caused by the random access procedure.
This gives a total of 6465 ms, allow 7s in the test case.
A.6.1.15 HD-FDD Intra-frequency RRC Re-establishment for UE category
NB1 in In-Band mode under enhanced coverage
A.6.1.15.1 Test Purpose and Environment
The purpose is to verify that the NB-IoT FDD intra-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements for Cat-NB1 UE in clause 6.5.
The test parameters are given in table A.6.1.15.1-1 and table A.6.1.15.1-2 below. nCell1 and nCell2 are NB-IoT cells
with different physical cell ID on the same frequency carrier. The test consists of 3 successive time periods, with time
duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell, is deactivated. The
time period T3 starts after the occurrence of the radio link failure.
Table A.6.1.15.1-1: General test parameters for HD-FDD Intra-frequency RRC Re-establishment for UE
category NB1 in In-Band mode under enhanced coverage
Parameter Unit Value Comment
NB-IOT operational mode In-band
Initial Active cell nCell1
condition Neighbour cells eCell1, nCell2
Final Active cell nCell2
condition
E-UTRA RF Channel Number 1 One carrier frequency is used for eCell.
Access Barring Information - Not Sent No additional delays in random access
procedure.
NPRACH Configuration 1 Refer to A.3.18
NPDCCH repetition level 16 NPDCCH Rmax
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync indications
from lower layers
T310 Ms 0 Radio link failure timer; T310 is disabled
T311 Ms [80000] RRC re-establishment timer
DRX OFF
T1 S 5
T2 Ms 400
T3 S [80]
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 791 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.15.1-2: nCell 1, nCell 2 specific test parameters for HD-FDD Intra-frequency RRC Re-
establishment for UE category NB1 in In-Band mode under enhanced coverage
Parameter Unit nCell 1 nCell 2
T1 T2 T3 T1 T2 T3
BW channel kHz 200 200
PRB location within eCell - 30 30
NPDSCH parameters R.14 HD-FDD R.14 HD-FDD
NPDCCH parameters R.26 HD-FDD R.26 HD-FDD
NOCNG Patterns - NOP.1 FDD NOP.1 FDD
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB
NSSS_RA dB
NPDCCH_RA dB
0 0
NPDCCH_RB dB
NPDSCH_RA dB
NPDSCH_RB dB
NOCNG_RANote 1 dB
NOCNG_RBNote 1 dB
N oc dBm/15 kHz Specified in Table A.6.1.15.1-3
dB 7 -Infinity -Infinity -Infinity -12.6 -12.6
Ê s N oc
dB 1.54 -Infinity -Infinity -Infinity -12.6 -12.6
Ê s I ot Note2
NRSRP Note2 dBm/15 kHz -91 -Infinity -Infinity -Infinity -110.6 -110.6
Propagation Condition AWGN AWGN
Antenna Configuration 1x1 1x1
Timing offset to nCell 1 ms - 3
Note 1: NOCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Es/Iot and NRSRP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 792 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.15.1-3: eCell 1 specific test parameters for HD-FDD Intra-frequency RRC Re-establishment
for UE category NB1 in In-Band mode under enhanced coverage
Parameter Unit eCell 1
T1 T2 T3
BW channel MHz 10
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
[PCFICH_RB] dB 0
[PDCCH_RA] dB
[PDCCH_RB] dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 kHz -98
dB -12.6 -12.6 -12.6
Ê s N oc
dB -12.6 -12.6 -12.6
Ê s I ot Note2
RSRP Note2 dBm/15 kHz -110.6 -110.6 -110.6
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N
shall be modelled as AWGN of appropriate power oc .
Note 3: Es/Iot and RSRP levels have been derived from other
parameters for information purposes. They are not settable
parameters themselves.
A.6.1.15.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send NPRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to an unknown NB-IoT FDD intra frequency cell shall be less than 58 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE-re-establish_delay_NB-IoT.
Where:
- TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The NPRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
- TUE-re-establish_delay_NB-IoT = 100 ms + NNB-Iot-freq*Tsearch_NB-IoT + TSI_NB-IoT + TPRACH_NB-IoT
- NNB-Iot-freq = 1
- Tsearch_NB-IoT = 14800 ms
- TSI_NB-IoT = 41560 ms; it is the time required for receiving all the relevant system information as defined in TS
36.331 for the target NB-IoT FDD cell.
- TPRACH_NB-IoT = 1280 ms; it is the additional delay caused by the random access procedure.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 793 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.1.16 HD-FDD Inter-frequency RRC Re-establishment for UE category
NB1 in In-Band mode under normal coverage
A.6.1.16.1 Test Purpose and Environment
The purpose is to verify that the NB-IoT FDD inter-frequency RRC re-establishment delay is within the specified
limits. These tests will verify the requirements for Cat-NB1 UE in clause 6.5.
The test parameters are given in table A.6.1.16.1-1 and table A.6.1.16.1-2 below. nCell1 and nCell2 are NB-IoT cells on
different frequency carriers. The test consists of 3 successive time periods, with time duration of T1, T2 and T3
respectively. At the start of time period T2, cell 1, which is the active cell, is deactivated. The time period T3 starts after
the occurrence of the radio link failure.
Table A.6.1.16.1-1: General test parameters for HD-FDD Inter-frequency RRC Re-establishment for UE
category NB1 in In-Band mode under normal coverage
Parameter Unit Value Comment
NB-IOT operational mode In-band
Initial Active cell nCell1
condition Neighbour cells eCell1, nCell2
Final Active cell nCell2
condition
E-UTRA RF Channel Number 1 One carrier frequency is used for eCell.
Access Barring Information - Not Sent No additional delays in random access
procedure.
PRACH Configuration 1 Refer to [A.3.18]
NPDCCH repetition level 16 NPDCCH Rmax
N310 - 1 Maximum consecutive out-of-sync
indications from lower layers
N311 - 1 Minimum consecutive in-sync indications
from lower layers
T310 Ms 0 Radio link failure timer; T310 is disabled
T311 Ms 15000 RRC re-establishment timer
DRX OFF
T1 S 5
T2 Ms 400
T3 S 15
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 794 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.16.1-2: nCell 1, nCell 2 specific test parameters for HD-FDD Inter-frequency RRC Re-
establishment for UE category NB1 in In-Band mode under normal coverage
Parameter Unit nCell 1 nCell 2
T1 T2 T3 T1 T2 T3
BW channel kHz 200 200
PRB location within eCell - 30 35
NPDSCH parameters R.14 HD-FDD R.14 HD-FDD
NPDCCH parameters R.26 HD-FDD R.26 HD-FDD
NOCNG Patterns - NOP.1 FDD NOP.1 FDD
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB
NSSS_RA dB
NPDCCH_RA dB
0 0
NPDCCH_RB dB
NPDSCH_RA dB
NPDSCH_RB dB
NOCNG_RANote 1 dB
NOCNG_RBNote 1 dB
N oc dBm/15 kHz Specified in Table A.6.1.16.1-3
dB 7 -Infinity -Infinity -Infinity 4 4
Ê s N oc
dB 1.54 -Infinity -Infinity -Infinity 4 4
Ê s I ot Note2
NRSRP Note2 dBm/15 kHz -91 -Infinity -Infinity -Infinity -94 -94
Propagation Condition AWGN AWGN
Antenna Configuration 1x1 1x1
Timing offset to nCell 1 ms - 3
Note 1: NOCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Es/Iot and NRSRP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 795 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.1.16.1-3: eCell 1 specific test parameters for HD-FDD Inter-frequency RRC Re-establishment
for UE category NB1 in In-Band mode under normal coverage
Parameter Unit eCell 1
T1 T2 T3
BW channel MHz 10
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
[PCFICH_RB] dB 0
[PDCCH_RA] dB
[PDCCH_RB] dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 kHz -98
dB 4 4 4
Ê s N oc
dB 4 4 4
Ê s I ot Note2
RSRP Note2 dBm/15 kHz -94 -94 -94
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N
shall be modelled as AWGN of appropriate power oc .
Note 3: Es/Iot and RSRP levels have been derived from other
parameters for information purposes. They are not settable
parameters themselves.
A.6.1.16.2 Test Requirements
The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the UE
starts to send NPRACH preambles to cell 2 for sending the RRCConnectionReestablishmentRequest message to cell 2.
The RRC re-establishment delay to an unknown NB-IoT FDD inter frequency cell shall be less than 12 s.
The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%.
NOTE: The RRC re-establishment delay in the test is derived from the following expression:
Tre-establish_delay= TUL_grant + TUE-re-establish_delay_NB-IoT.
Where:
- TUL_grant = It is the time required to acquire and process uplink grant from the target cell. The NPRACH reception
at the system simulator is used as a trigger for the completion of the test; hence TUL_grant is not used.
- TUE-re-establish_delay_NB-IoT = 100 ms + NNB-Iot-freq*Tsearch_NB-IoT + TSI_NB-IoT + TPRACH_NB-IoT
- NNB-Iot-freq = 2
- Tsearch_NB-IoT = 1400 ms
- TSI_NB-IoT = 8320 ms; it is the time required for receiving all the relevant system information as defined in TS
36.331 for the target NB-IoT FDD cell.
- TPRACH_NB-IoT = 80 ms; it is the additional delay caused by the random access procedure.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 796 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2 Random Access
A.6.2.1 E-UTRAN FDD – Contention Based Random Access Test
A.6.2.1.1 Test Purpose and Environment
The purpose of this test is to verify that the behavior of the random access procedure is according to the requirements
and that the PRACH power settings and timing are within specified limits. This test will verify the requirements in
Clause 6.2.2 and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.1.1-1 and A.6.2.1.1-2.
Table A.6.2.1.1-1: General test parameters for FDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern Note 1 OP.1/2 FDD Note 1 As defined in A.3.2.1.1/2.
PDSCH parameters Note 4 DL Reference Measurement As defined in A.3.1.1.1.
Channel R.0 FDD Note 4
PCFICH/PDCCH/PHICH DL Reference Measurement As defined in A.3.1.2.1.
parameters Channel R.6 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
dB 3
Ê s I ot
N oc dBm/15 KHz -98
dB 3
Ês N oc
Io Note 2 dBm/9 MHz -65.5
RSRP Note 3 dBm/15 KHz -95
dBm/15 KHz -5 As defined in clause 6.3.2
referenceSignalPower
in TS 36.331.
Configured UE transmitted dBm 23 As defined in clause 6.2.5
power ( PCMAX ) in TS 36.101.
PRACH Configuration Index - 4 As defined in table 5.7.1-2
in TS 36.211.
Backoff Parameter Index - 2 As defined in table 7.2-1
in TS 36.321.
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols. The OCNG pattern is chosen during the test
according to the presence of a DL reference measurement channel.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 3: RSRP level has been derived from other parameters for information purposes. It is not a
settable parameter.
Note 4: The DL PDSCH reference measurement channel is used in the test only when a downlink
transmission dedicated to the UE under test is required.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 797 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.1.1-2: RACH-Configuration parameters for FDD contention based random access test
Field Value Comment
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
ra-ResponseWindowSize sf10 10 sub-frames
mac-ContentionResolutionTimer sf48 48 sub-frames
maxHARQ-Msg3Tx 4
Note: For further information see Clause 6.3.2 in TS 36.331.
A.6.2.1.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.1.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.1.1 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. In response to the first 4 preambles, the System
Simulator shall transmit a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm. The power of the first preamble shall be -30 dBm with an accuracy
specified in clause 6.3.5.1.1 of TS 36.101 [5]. The relative power applied to additional preambles shall have an
accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.1.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.1.2 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. The System Simulator shall not respond to the first 4
preambles.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.1.2.3 Receiving a NACK on msg3
To test the UE behavior specified in subclause 6.2.2.1.3 the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 798 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.1.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5 the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.1.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5 the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.1.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6 the System Simulator shall not send a response to a msg3.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
A.6.2.2 E-UTRAN FDD – Non-Contention Based Random Access Test
A.6.2.2.1 Test Purpose and Environment
The purpose of this test is to verify that the behavior of the random access procedure is according to the requirements
and that the PRACH power settings and timing are within specified limits. This test will verify the requirements in
Clause 6.2.2 and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.2.1-1 and A.6.2.2.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 799 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.2.1-1: General test parameters for FDD non-contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern OP.1 FDD As defined in A.3.2.1.1.
PDSCH parameters DL Reference Measurement As defined in A.3.1.1.1.
Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As defined in A.3.1.2.1.
parameters Channel R.6 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
dB 3
Ê s I ot
N oc dBm/15 KHz -98
dB 3
Ês N oc
Io Note 2 dBm/9 MHz -65.5
RSRP Note 3 dBm/15 KHz -95
dBm/15 KHz -5 As defined in clause 6.3.2
referenceSignalPower
in TS 36.331.
Configured UE transmitted dBm 23 As defined in clause 6.2.5
power ( PCMAX ) in TS 36.101.
PRACH Configuration Index - 4 As defined in table 5.7.1-2
in TS 36.211.
Backoff Parameter Index - 2 As defined in table 7.2-1
in TS 36.321.
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 3: RSRP level has been derived from other parameters for information purposes. It is not a
settable parameter.
Table A.6.2.2.1-2: RACH-Configuration parameters for FDD non-contention based random access test
Field Value Comment
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
ra-ResponseWindowSize sf10 10 sub-frames
Note: For further information see Clause 6.3.2 in TS 36.331.
A.6.2.2.2 Test Requirements
Non-Contention based random access is triggered by explicitly assigning a random access preamble via dedicated
signalling in the downlink.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 800 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.2.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.2.1 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. In response to the first 4 preambles, the System
Simulator shall transmit a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) if the Random Access Response contains a Random
Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-transmit the preamble with the calculated PRACH transmission power if all received Random Access
Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.2.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.2.2 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. The System Simulator shall not respond to the first 4
preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.3 E-UTRAN TDD – Contention Based Random Access Test
A.6.2.3.1 Test Purpose and Environment
The purpose of this test is to verify that the behavior of the random access procedure is according to the requirements
and that the PRACH power settings and timing are within specified limits. This test will verify the requirements in
Clause 6.2.2 and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.3.1-1 and A.6.2.3.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 801 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.3.1-1: General test parameters for TDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number - 1
BW channel MHz 10
OCNG Pattern Note 1 - OP.1/2 TDD Note 1 As defined in A.3.2.2.1/2.
PDSCH parameters Note 4 - DL Reference Measurement As defined in A.3.1.1.2.
Channel R.0 TDD Note 4
PCFICH/PDCCH/PHICH - DL Reference Measurement As defined in A.3.1.2.2.
parameters Channel R.6 TDD
Special subframe - 6 As specified in table 4.2-1
configuration in TS 36.211.
Uplink-downlink configuration - 1 As specified in table 4.2-2
in TS 36.211.
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
dB 3
Ê s I ot
N oc dBm/15 KHz -98
dB 3
Ês N oc
Io Note 2 dBm/9 MHz -65.5
RSRP Note 3 dBm/15 KHz -95
dBm/15 KHz -5 As defined in clause 6.3.2
referenceSignalPower
in TS 36.331.
Configured UE transmitted dBm 23 As defined in clause 6.2.5
power ( PCMAX ) in TS 36.101.
PRACH Configuration Index - 53 As defined in table 5.7.1-3
in TS 36.211.
Backoff Parameter Index - 2 As defined in table 7.2-1
in TS 36.321.
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols. The OCNG pattern is chosen during the test
according to the presence of a DL reference measurement channel.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 3: RSRP level has been derived from other parameters for information purposes. It is not a
settable parameter.
Note 4: The DL PDSCH reference measurement channel is used in the test only when a downlink
transmission dedicated to the UE under test is required.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 802 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.3.1-2: RACH-Configuration parameters for TDD contention based random access test
Field Value Comment
numberOfRA-Preambles n52
sizeOfRA-PreamblesGroupA n52 No group B.
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
ra-ResponseWindowSize sf10 10 sub-frames
mac-ContentionResolutionTimer sf48 48 sub-frames
maxHARQ-Msg3Tx 4
Note: For further information see Clause 6.3.2 in TS 36.331.
A.6.2.3.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.3.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.1.1 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. In response to the first 4 preambles, the System
Simulator shall transmit a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.3.2.2 No Random Access Response reception
To test the UE behavior specified in Subclause 6.2.2.1.2 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. The System Simulator shall not respond to the first 4
preambles.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.3.2.3 Receiving a NACK on msg3
To test the UE behavior specified in Subclause 6.2.2.1.3 the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 803 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.3.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5 the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.3.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5 the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.3.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6 the System Simulator shall not send a response to a msg3.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
A.6.2.4 E-UTRAN TDD – Non-Contention Based Random Access Test
A.6.2.4.1 Test Purpose and Environment
The purpose of this test is to verify that the behavior of the random access procedure is according to the requirements
and that the PRACH power settings and timing are within specified limits. This test will verify the requirements in
Clause 6.2.2 and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.4.1-1 and A.6.2.4.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 804 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.4.1-1: General test parameters for TDD non-contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number - 1
BW channel MHz 10
OCNG Pattern - OP.1 TDD As defined in A.3.2.2.1.
PDSCH parameters - DL Reference Measurement As defined in A.3.1.1.2.
Channel R.0 TDD
PCFICH/PDCCH/PHICH - DL Reference Measurement As defined in A.3.1.2.2.
parameters Channel R.6 TDD
Special subframe - 6 As specified in table 4.2-1
configuration in TS 36.211.
Uplink-downlink configuration - 1 As specified in table 4.2-2
in TS 36.211.
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
dB 3
Ê s I ot
N oc dBm/15 KHz -98
dB 3
Ês N oc
Io Note 2 dBm/9 MHz -65.5
RSRP Note 3 dBm/15 KHz -95
dBm/15 KHz -5 As defined in clause 6.3.2
referenceSignalPower
in TS 36.331.
Configured UE transmitted dBm 23 As defined in clause 6.2.5
power ( PCMAX ) in TS 36.101.
PRACH Configuration Index - 53 As defined in table 5.7.1-3
in TS 36.211.
Backoff Parameter Index - 2 As defined in table 7.2-1
in TS 36.321.
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 3: RSRP level has been derived from other parameters for information purposes. It is not a
settable parameter.
Table A.6.2.4.1-2: RACH-Configuration parameters for TDD non-contention based random access test
Field Value Comment
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
ra-ResponseWindowSize sf10 10 sub-frames
Note: For further information see Clause 6.3.2 in TS 36.331.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 805 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.4.2 Test Requirements
Non-Contention based random access is triggered by explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.4.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.2.1 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. In response to the first 4 preambles, the System
Simulator shall transmit a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) if the Random Access Response contains a Random
Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-transmit the preamble with the calculated PRACH transmission power if all received Random Access
Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.4.2.2 No Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.2.2 the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preambles have been received by the System Simulator. The System Simulator shall not respond to the first 4
preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.5 E-UTRAN FDD – Contention Based Random Access Test for 5MHz
bandwidth
A.6.2.5.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.6.2.1.1.
The parameters of this test are the same as defined in Subclause A.6.2.1.1 except that the values of the parameters in the
Table A.6.2.5.1-1 will replace the values of the corresponding parameters in A.6.2.1.1-1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 806 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.5.1-1: General test parameters for FDD contention based random access test for 5MHz
bandwidth
Parameter Unit Value Comments
BW channel MHz 5
OCNG Pattern Note 1 OP.15/16 FDD Note 1 As defined in
A.3.2.1.15/16.
PDSCH parameters Note 2 DL Reference Measurement As defined in A.3.1.1.1.
Channel R.5 FDD Note 2
PCFICH/PDCCH/PHICH DL Reference Measurement As defined in A.3.1.2.1.
parameters Channel R.11 FDD
dBm/4.5 -68.5
Io Note 2
MHz
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols. The OCNG pattern is chosen during the test
according to the presence of a DL reference measurement channel.
Note 2: The DL PDSCH reference measurement channel is used in the test only when a downlink
transmission dedicated to the UE under test is required.
Note 3: See Table A.6.2.1.1-1 for the other parameters.
Note 4: This test is according to the principle defined in section A.3.7.2.
A.6.2.5.2 Test Requirements
The test requirements defined in section A.6.2.1.2 shall apply to this test case.
A.6.2.6 E-UTRAN FDD – Non-contention Based Random Access Test for
5MHz bandwidth
A.6.2.6.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.6.2.2.1.
The parameters of this test are the same as defined in Subclause A.6.2.2.1except that the values of the parameters in the
Table A.6.2.6.1-1will replace the values of the corresponding parameters in A.6.2.2.1-1
Table A.6.2.6.1-1: General test parameters for FDD non-contention based random access test for
5MHz bandwidth
Parameter Unit Value Comments
BW channel MHz 5
OCNG Pattern Note 1 OP.15 FDD Note 1 As defined in A.3.2.1.15.
PDSCH parameters Note 2 DL Reference Measurement As defined in A.3.1.1.1.
Channel R.5 FDD Note 2
PCFICH/PDCCH/PHICH DL Reference Measurement As defined in A.3.1.2.1.
parameters Channel R.11 FDD
dBm/4.5 -68.5
Io Note 2
MHz
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter
Note 3: See Table A.6.2.2.1-1 for the other parameters.
Note 4: This test is according to the principle defined in section A.3.7.2.
A.6.2.6.2 Test Requirements
The test requirements defined in section A.6.2.2.2 shall apply to this test case.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 807 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.7 E-UTRAN FDD – Non-Contention Based Random Access Test For
SCell
A.6.2.7.1 Test Purpose and Environment
The purpose of this test is to verify that the behavior of the random access procedure, for the SCell, is according to the
requirements and that the PRACH power settings and timing, for the SCell, are within specified limits. This test will
verify the requirements in Clause 6.2.2 and Clause 7.1.2 in an AWGN model.
For this test two cells are used. Cell 1 is PCell and Cell 2 is SCell. PCell and SCell are different timing advance group.
Cell 1 is in the primary Timing Advance Group (pTAG) and Cell 2 is in the secondary Timing Advance Group (sTAG).
The purpose of the PCell is to allow the SCell to be configured and to handle the Random Access Response which takes
place on PCell. The test parameters are given in tables A.6.2.7.1-1 and A.6.2.7.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 808 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.7.1-1: General test parameters for FDD non-contention based random access test
Parameter Unit Cell 1 Cell 2 Comments
E-UTRA RF Channel Number 1 2
BW channel MHz 10 10
Active PCell Cell 1 Primary cell of RF
channel number 1.
Active SCell Cell 2 Secondary cell of RF
channel number 2.
TAG configuration pTAG sTAG pTAG+sTAG
configures Cell 1 and
Cell 2 to separate
TAGs
OCNG Pattern OP.1 FDD OP.1 FDD As defined in
A.3.2.1.11.
PDSCH parameters DL Reference DL Reference As defined in A.3.1.1.1.
Measurement Channel Measurement
R.0 FDD Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference DL Reference As defined in A.3.1.2.1.
parameters Measurement Channel Measurement
R.6 FDD Channel R.6 FDD
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
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
dB 3 3
Ê s I ot
N oc dBm/15 KHz -98 -98
dB 3 3
Ês N oc
Io Note 2 dBm/9 MHz -65.5 -65.5
RSRP Note 3 dBm/15 KHz -95 -95
dBm/15 KHz -5 -5 As defined in clause
referenceSignalPower
6.3.2 in TS 36.331.
Configured UE transmitted dBm 23 23 As defined in clause
power ( PCMAX,c ) 6.2.5 in TS 36.101.
PRACH Configuration Index - 4 4 As defined in table
5.7.1-2 in TS 36.211.
Backoff Parameter Index - 2 2 As defined in table 7.2-
1 in TS 36.321.
Propagation Condition - AWGN AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power spectral density
is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 3: RSRP level has been derived from other parameters for information purposes. It is not a settable parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 809 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.7.1-2: RACH-Configuration parameters for FDD non-contention based random access test
Field Value Comment
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
ra-ResponseWindowSize sf10 10 sub-frames
Note: For further information see Clause 6.3.2 in TS 36.331.
A.6.2.7.2 Test Requirements
Non-Contention based random access is triggered by explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.7.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.2.1 the System Simulator shall transmit, on Cell 1, the PCell, a
Random Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random
Access Preamble after 5 preambles have been received by the System Simulator, on Cell 2. In response to the first 4
preambles, the System Simulator shall transmit a Random Access Response not corresponding to the transmitted
Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) if the Random Access Response contains a Random
Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-transmit the preamble with the calculated PRACH transmission power if all received Random Access
Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.7.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.2.2 the System Simulator shall transmit, on Cell 1, the PCell, a
Random Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random
Access Preamble after 5 preambles have been received by the System Simulator on Cell 2. The System Simulator shall
not respond to the first 4 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.7.2.3 Stop Preamble transmission if maximum number of preamble transmission
counter has been reached
To test the UE behavior specified in Subclause 6.2.2 the System Simulator shall transmit, in response to the first 6
preambles, a Random Access Response not corresponding to the transmitted Random Access Preamble on Cell 1, the
PCell. The UE shall stop transmitting preambles after 6 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 810 ETSI TS 136 133 V14.3.0 (2017-04)
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.8 E-UTRAN TDD – Non-Contention Based Random Access Test For
SCell
A.6.2.8.1 Test Purpose and Environment
This test is applicable for UE supporting the optional capability of Multiple Timing Advance.
The purpose of this test is to verify that the behavior of the random access procedure, for the SCell, is according to the
requirements and that the PRACH power settings and timing, for the SCell, are within specified limits. This test will
verify the requirements in Clause 6.2.2 and Clause 7.1.2 in an AWGN model.
For this test two cells are used. Cell 1 is PCell and Cell 2 is SCell. PCell and SCell are different timing advance group.
Cell 1 is in the primary Timing Advance Group (pTAG) and Cell 2 is in the secondary Timing Advance Group (sTAG).
The purpose of the PCell is to allow the SCell to be configured and to handle the Random Access Response which takes
place on PCell. The test parameters are given in tables A.6.2.8.1-1 and A.6.2.8.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 811 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.8.1-1: General test parameters for TDD non-contention based random access test
Parameter Unit Cell 1 Cell 2 Comments
E-UTRA RF Channel Number - 1 1
BW channel MHz 10 10
Active PCell Primary cell of RF
Cell 1
channel number 1.
Active SCell Secondary cell of RF
Cell 2
channel number 2.
TAG configuration pTAG sTAG pTAG+sTAG
configures Cell 1 and
Cell 2 to separate
TAGs
OCNG Pattern - OP.1 TDD OP.1 TDD As defined in
A.3.2.2.1.
PDSCH parameters - DL Reference DL Reference As defined in
Measurement Measurement A.3.1.1.2.
Channel R.0 TDD Channel R.0 TDD
PCFICH/PDCCH/PHICH - DL Reference DL Reference As defined in
parameters Measurement Measurement A.3.1.2.2.
Channel R.6 TDD Channel R.6 TDD
Special subframe - 6 6 As specified in table
configuration 4.2-1 in TS 36.211.
Uplink-downlink configuration - 1 1 As specified in table
4.2-2 in TS 36.211.
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
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
dB 3 3
Ê s I ot
N oc dBm/15 KHz -98 -98
dB 3 3
Ês N oc
Io Note 2 dBm/9 MHz -65.5 -65.5
RSRP Note 3 dBm/15 KHz -95 -95
dBm/15 KHz -5 -5 As defined in clause
referenceSignalPower
6.3.2 in TS 36.331.
Configured UE transmitted dBm 23 23 As defined in clause
power ( PCMAX,c ) 6.2.5 in TS 36.101.
PRACH Configuration Index - 53 53 As defined in table
5.7.1-3 in TS 36.211.
Backoff Parameter Index - 2 2 As defined in table
7.2-1 in TS 36.321.
Propagation Condition - AWGN AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 3: RSRP level has been derived from other parameters for information purposes. It is not a settable parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 812 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.8.1-2: RACH-Configuration parameters for TDD non-contention based random access test
Field Value Comment
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
ra-ResponseWindowSize sf10 10 sub-frames
Note: For further information see Clause 6.3.2 in TS 36.331.
A.6.2.8.2 Test Requirements
Non-Contention based random access is triggered by explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.8.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.2.1 the System Simulator shall transmit, on Cell 1, the PCell, a
Random Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random
Access Preamble after 5 preambles have been received by the System Simulator, on Cell 2. In response to the first 4
preambles, the System Simulator shall transmit a Random Access Response not corresponding to the transmitted
Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) if the Random Access Response contains a Random
Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-transmit the preamble with the calculated PRACH transmission power if all received Random Access
Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.8.2.2 No Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2.2.2 the System Simulator shall transmit, on Cell 1, the PCell, a
Random Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random
Access Preamble after 5 preambles have been received by the System Simulator, on Cell 2. The System Simulator shall
not respond to the first 4 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.8.2.3 Stop Preamble transmission if maximum number of preamble transmission
counter has been reached
To test the UE behavior specified in Subclause 6.2.2 the System Simulator shall transmit, in response to the first 6
preambles, a Random Access Response not corresponding to the transmitted Random Access Preamble on Cell 1, the
PCell. The UE shall stop transmitting preambles after 6 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 813 ETSI TS 136 133 V14.3.0 (2017-04)
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.9 3DL/3UL TDD CA Non-Contention Based Random Access Test for
2 SCells
A.6.2.9.1 Test Purpose and Environment
This test is applicable for UE supporting the optional capability of Multiple Timing Advance.
The purpose of this test is to verify that the behavior of the random access procedure, for the two SCells, is according to
the requirements and that the PRACH power settings and timing, for the SCell, are within specified limits. This test will
verify the requirements in Clause 6.2.2 and Clause 7.1.2 in an AWGN model.
For this test three cells are used. Cell 1 is PCell, Cell 2 is SCell1 and Cell 3 is SCell2. Cell 1 and Cell 2/Cell 3 belong to
different timing advance groups. Cell 1 is in the primary Timing Advance Group (pTAG). Cell 2 and Cell3 are in the
same secondary Timing Advance Group (sTAG). The purpose of the Cell 1 is to allow Cell 2 and Cell 3 to be
configured and to handle the Random Access Response which takes place on Cell 1. The test parameters are given in
tables A.6.2.9.1-1 and A.6.2.9.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 814 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.9.1-1: General test parameters for 3DL/3UL TDD CA non-contention based random access
test
Parameter Unit Cell 1 Cell 2 Cell 3 Comments
E-UTRA RF Channel - 1 2 3
Number
BW channel - 5MHz: NRB,c = 25 5MHz: NRB,c = 25 5MHz: NRB,c = 25
10MHz: NRB,c = 50 10MHz: NRB,c = 50 10MHz: NRB,c = 50
20MHz: NRB,c = 20MHz: NRB,c = 20MHz: NRB,c =
100 100 100
TAG configuration - pTAG sTAG sTAG Cell 2 and Cell
3 are in the
same sTAG
PDSCH parameters: - 5MHz: R.4 TDD 5MHz: R.4 TDD 5MHz: R.4 TDD As defined in
DL Reference 10MHz: R.0 TDD 10MHz: R.0 TDD 10MHz: R.0 TDD A.3.1.1.2.
Measurement 20MHz: R.3 TDD 20MHz: R.3 TDD 20MHz: R.3 TDD
Channel
PCFICH/PDCCH/PHI - 5MHz: R.11 TDD 5MHz: R.11 TDD 5MHz: R.11 TDD As defined in
CH parameters: 10MHz: R.6 TDD 10MHz: R.6 TDD 10MHz: R.6 TDD A.3.1.2.2.
DL Reference 20MHz: R.10 TDD 20MHz: R.10 TDD 20MHz: R.10 TDD
Measurement
Channel
OCNG Patterns - 5MHz: OP.9 TDD 5MHz: OP.9 TDD 5MHz: OP.9 TDD As defined in
10MHz: OP.1 TDD 10MHz: OP.1 TDD 10MHz: OP.1 TDD A.3.2.2.
20MHz: OP.7 TDD 20MHz: OP.7 TDD 20MHz: OP.7 TDD
Special subframe - 6 6 6 As specified in
configuration table 4.2-1 in
TS 36.211.
Uplink-downlink - 1 1 1 As specified in
configuration table 4.2-2 in
TS 36.211.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
dB 3 3 3
Ê s I ot
N oc dBm/15 -98 -98 -98
KHz
dB 3 3 3
Ês N oc
dBm/ -65.5+10log -65.5+10log -65.5+10log
Io Note 2
BW channel (NRB,c /50) (NRB,c /50) (NRB,c /50)
dBm/15 -95 -95 -95
RSRP Note 3
KHz
dBm/15 -5 -5 -5 As defined in
referenceSignalPower KHz clause 6.3.2 in
TS 36.331.
Configured UE dBm 23 23 23 As defined in
transmitted power clause 6.2.5 in
( PCMAX,c ) TS 36.101.
PRACH Configuration - 53 53 53 As defined in
Index table 5.7.1-3 in
TS 36.211.
Backoff Parameter - 2 2 2 As defined in
Index table 7.2-1 in
TS 36.321.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 815 ETSI TS 136 133 V14.3.0 (2017-04)
Propagation - AWGN AWGN AWGN
Condition
Antenna 1x2 1x2 1x2
Configuration
Timing offset to Cell 1 μs - 0 0
Time alignment error μs - ≤ TAE ≤ TAE
relative to cell 1 Note 4
Time alignment error μs - - ≤ TAE
relative to cell 2 Note 4
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power spectral density
is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 3: RSRP level has been derived from other parameters for information purposes. It is not a settable parameter.
Note 4: The time alignment error (TAE) between two cells specified in TS36.104 [30] clause 6.5.3.1 (value depends
upon the type of carrier aggregation).
Note 5: This test verifies the RRM requirement which is independent of channel bandwidth and is performed according
to the principle defined in section A.3.6.1.
Table A.6.2.9.1-2: RACH-Configuration parameters for cell2 and cell3 for 3DL/3UL TDD CA non-
contention based random access test
Field Value Comment
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
ra-ResponseWindowSize sf10 10 sub-frames
Note 1: For further information see Clause 6.3.2 in TS 36.331.
A.6.2.9.2 Test Requirements
Non-Contention based random access is triggered by explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.9.2.1 Random Access Response Reception
A.6.2.9.2.1.1 Test Requirements for Cell 2
To test the UE behavior specified in Subclause 6.2.2.2.1 the System Simulator shall transmit, on cell 1 a Random
Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access
Preamble after 5 preambles have been received by the System Simulator, on cell 2. In response to the first 4 preambles,
the System Simulator shall transmit a Random Access Response not corresponding to the transmitted Random Access
Preamble.
The UE may stop monitoring for Random Access Response(s) if the Random Access Response contains a Random
Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-transmit the preamble with the calculated PRACH transmission power if all received Random Access
Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions on cell 2 shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.9.2.1.2 Test Requirements for Cell 3
To test the UE behavior specified in Subclause 6.2.2.2.1 the System Simulator shall transmit, on cell 1 a Random
Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access
Preamble after 5 preambles have been received by the System Simulator, on cell 3. In response to the first 4 preambles,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 816 ETSI TS 136 133 V14.3.0 (2017-04)
the System Simulator shall transmit a Random Access Response not corresponding to the transmitted Random Access
Preamble.
The UE may stop monitoring for Random Access Response(s) if the Random Access Response contains a Random
Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-transmit the preamble with the calculated PRACH transmission power if all received Random Access
Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions on cell 3 shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.9.2.2 No Random Access Response Reception
A.6.2.9.2.2.1 Test Requirements for Cell 2
To test the UE behavior specified in Subclause 6.2.2.2.2 the System Simulator shall transmit, on cell 1, a Random
Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access
Preamble after 5 preambles have been received by the System Simulator, on cell 2. The System Simulator shall not
respond to the first 4 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power on cell 2.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions on cell 2 shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.9.2.2.2 Test Requirements for Cell 3
To test the UE behavior specified in Subclause 6.2.2.2.2 the System Simulator shall transmit, on cell 1, a Random
Access Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access
Preamble after 5 preambles have been received by the System Simulator, on cell 3. The System Simulator shall not
respond to the first 4 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power on cell 3.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions on cell 3 shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.9.2.3 Stop Preamble transmission if maximum number of preamble transmission
counter has been reached
A.6.2.9.2.3.1 Test Requirements for Cell 2
To test the UE behavior specified in Subclause 6.2.2 the System Simulator shall transmit, in response to the first 6
preambles, a Random Access Response not corresponding to the transmitted Random Access Preamble on cell 1. The
UE shall stop transmitting preambles after 6 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power on cell 2.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions on cell 2 shall be within the accuracy specified in Subclause 7.1.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 817 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.9.2.3.2 Test Requirements for Cell 3
To test the UE behavior specified in Subclause 6.2.2 the System Simulator shall transmit, in response to the first 6
preambles, a Random Access Response not corresponding to the transmitted Random Access Preamble on cell 1. The
UE shall stop transmitting preambles after 6 preambles.
The UE shall re-transmit the preamble with the calculated PRACH transmission power on cell 3.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -22 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions on cell 3 shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.10 E-UTRAN FDD Contention Based Random Access Test for Cat-M1
UEs in Normal Coverage
A.6.2.10.1 Test Purpose and Environment
The purpose of this test is to verify whether the behavior of the random access procedure of a Cat-M1 UE in Normal
Coverage is according to the requirements, whether the PRACH power settings and timing are within specified limits,
and whether the UE determines properly the enhanced coverage level based on the RSRP measurement and the
configured criterion in RSRP-ThresholdsPrach [2]. This test will verify the requirements in Clause 6.2.2, Clause 6.2.3
and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.10.1-1 and A.6.2.10.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 818 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.10.1-1: General test parameters for FDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern Note 1 OP.21 FDD As defined in A.
A.3.2.1.21.
PDSCH parameters Note 2 R.20 FDD As defined in
A.3.1.4.1
MPDCCH parameters Note 2 R.16 FDD As defined in
A.3.1.3.1
PCFICH/PDCCH/PHICH DL Reference As defined in
parameters Measurement A.3.1.2.1
Channel R.6
FDD
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
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc dBm/15 KHz -98
dB 3
Ês Noc
dB 3
Ês Iot Note 3
RSRP Note 3 dBm/15 KHz -95
Io Note 3 dBm/9 MHz -65.5
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols. The
OCNG pattern is chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The PDSCH and MPDCCH reference measurement channels are used in
the test only when a downlink transmission dedicated to the UE under test is
required.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for
information purpose. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 819 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.10.1-2: RACH-Configuration parameters for FDD contention based random access test
Field Value Comment
Parameters not per CE Levels
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
maxHARQ-Msg3Tx 4
rar-HoppingConfig Off
Parameters per CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
ra-ResponseWindowSize (per CE) sf20 sf80 sf180 sf320
mac-ContentionResolutionTimer (per CE) sf80 sf120 sf200 sf480
PreambleMappingInfo {0, 9} {10,19} {20,29} {30,39}
{firstPreamble, lastPreamble}
Note: For further information see Clause 6.3.2 in TS 36.331.
Table A.6.2.10.1-3: PRACH-Configuration parameters for FDD contention based random access test
Field Value Comment
Parameters not per CE Levels
rsrp-ThresholdsPrach {24, 31, 38} Corresponding to {-116,
-109, -102} dBm as
defined in Section
9.1.21.5
mpdcch-startSF-CSS-RA v1
referenceSignalPower -5 dBm/15 KHz As defined in clause
6.3.2 in TS 36.331.
maxHARQ-Msg3Tx 4 As defined in table
5.7.1-2 in TS 36.211
Backoff Parameter Index 2 As defined in table 7.2-1
in TS 36.321
Configured UE transmitted 23 dBm As defined in clause
power ( PCMAX ) 6.2.5 in TS 36.101
Parameters per PRACH CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
prach-ConfigIndex 4 4 4 4 As defined in table
5.7.1-2 in TS 36.211
prach-FreqOffset 0 0 0 0
prach-StartingSubframe sf2 sf4 sf16 sf64
maxNumPreambleAttempt n3 n5 n7 n10
numRepetitionPerPreambleAtt n1 n4 n16 n64
empt
mpdcch- 2 2 2 2
NarrowbandsToMonitor
mpdcch-NumRepetition-RA r8 r8 r128 r128
prach-HoppingConfig Off Off Off Off
Note 1: See Clause 6.3.2 in TS 36.331 for further information on the parameters in this table.
A.6.2.10.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.10.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2, the System Simulator shall transmit a Random Access Response
containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble after [5]
preamble transmission attempts (the preamble may be transmitted multiple times in each attempt) have been received
by the System Simulator. In response to the first [4] preamble transmission attempts, the System Simulator shall
transmit a Random Access Response not corresponding to the transmitted Random Access Preamble.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 820 ETSI TS 136 133 V14.3.0 (2017-04)
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm. The power of the first preamble shall be -30 dBm with an accuracy
specified in clause 6.3.5.1.1 of TS 36.101 [5]. The relative power applied to additional preambles shall have an
accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.10.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.1.2, the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after [5] preamble transmission attempts have been received by the System Simulator. The System Simulator shall not
respond to the first [4] preamble transmission attempts.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.10.2.3 Receiving a NACK on msg3
To test the UE behavior specified in subclause 6.2.2.1.3, the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
A.6.2.10.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.10.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.10.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6, the System Simulator shall not send a response to a msg3.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 821 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.10.2.7 PRACH Resource Selection
The UE shall select PRACH resources and transmits or re- transmits PRACH preambles using the PRACH resources
and PRACH configuration corresponding to the coverage enhancement level 0.
Note: The PRACH Resource Selection requirement is already assumed for testing the other PRACH requirements.
A.6.2.11 E-UTRAN HD-FDD Contention Based Random Access Test for Cat-
M1 UEs in Normal Coverage
A.6.2.11.1 Test Purpose and Environment
The purpose of this test is to verify whether the behavior of the random access procedure of a Cat-M1 UE in Normal
Coverage is according to the requirements, whether the PRACH power settings and timing are within specified limits,
and whether the UE determines properly the enhanced coverage level based on the RSRP measurement and the
configured criterion in RSRP-ThresholdsPrach [2]. This test will verify the requirements in Clause 6.2.2, Clause 6.2.3
and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.11.1-1 and A.6.2.11.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 822 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.11.1-1: General test parameters for HD-FDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern Note 1 OP.21 FDD As defined in
A.3.2.1.21.
PDSCH parameters Note 2 R.10 HD-FDD As defined in
A.3.1.4.2
MPDCCH parameters Note 2 R.6 HD-FDD As defined in
A.3.1.3.2
PCFICH/PDCCH/PHICH DL Reference As defined in
parameters Measurement A.3.1.2.3
Channel R.3
HD-FDD
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
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc dBm/15 KHz -98
dB 3
Ês Noc
dB 3
Ês Iot Note 3
RSRP Note 3 dBm/15 KHz -95
Io Note 3 dBm/9 MHz -65.5
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols. The
OCNG pattern is chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The PDSCH and MPDCCH reference measurement channels are used in
the test only when a downlink transmission dedicated to the UE under test is
required.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for
information purpose. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 823 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.11.1-2: RACH-Configuration parameters for HD-FDD contention based random access
test
Field Value Comment
Parameters not per CE Levels
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
maxHARQ-Msg3Tx 4
rar-HoppingConfig Off
Parameters per CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
ra-ResponseWindowSize (per CE) sf20 sf80 sf180 sf320
mac-ContentionResolutionTimer (per CE) sf80 sf120 sf200 sf480
PreambleMappingInfo {0, 9} {10,19} {20,29} {30,39}
{firstPreamble, lastPreamble}
Note: For further information see Clause 6.3.2 in TS 36.331.
Table A.6.2.11.1-3: PRACH-Configuration parameters for HD-FDD contention based random access
test
Field Value Comment
Parameters not per CE Levels
rsrp-ThresholdsPrach {24, 31, 38} Corresponding to {-116,
-109, -102} dBm as
defined in Section
9.1.21.5
mpdcch-startSF-CSS-RA v1
referenceSignalPower -5 dBm/15 KHz As defined in clause
6.3.2 in TS 36.331.
maxHARQ-Msg3Tx 4 As defined in table
5.7.1-2 in TS 36.211
Backoff Parameter Index 2 As defined in table 7.2-1
in TS 36.321
Configured UE transmitted 23 dBm As defined in clause
power ( PCMAX ) 6.2.5 in TS 36.101
Parameters per PRACH CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
prach-ConfigIndex 4 4 4 4 As defined in table
5.7.1-2 in TS 36.211
prach-FreqOffset 0 0 0 0
prach-StartingSubframe sf2 sf4 sf16 sf64
maxNumPreambleAttempt n3 n5 n7 n10
numRepetitionPerPreambleAtt n1 n4 n16 n64
empt
mpdcch- 2 2 2 2
NarrowbandsToMonitor
mpdcch-NumRepetition-RA r8 r8 r128 r128
prach-HoppingConfig Off Off Off Off
Note 1: See Clause 6.3.2 in TS 36.331 for further information on the parameters in this table.
A.6.2.11.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.11.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2, the System Simulator shall transmit a Random Access Response
containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble after [5]
preamble transmission attempts (the preamble may be transmitted multiple times in each attempt) have been received
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 824 ETSI TS 136 133 V14.3.0 (2017-04)
by the System Simulator. In response to the first [4] preamble transmission attempts, the System Simulator shall
transmit a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm. The power of the first preamble shall be -30 dBm with an accuracy
specified in clause 6.3.5.1.1 of TS 36.101 [5]. The relative power applied to additional preambles shall have an
accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.11.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.1.2, the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after [5] preamble transmission attempts have been received by the System Simulator. The System Simulator shall not
respond to the first [4] preamble transmission attempts.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.11.2.3 Receiving a NACK on msg3
To test the UE behavior specified in subclause 6.2.2.1.3, the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
A.6.2.11.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.11.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.11.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6, the System Simulator shall not send a response to a msg3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 825 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
A.6.2.11.2.7 PRACH Resource Selection
The UE shall select PRACH resources and transmits or re- transmits PRACH preambles using the PRACH resources
and PRACH configuration corresponding to the coverage enhancement level 0.
Note: The PRACH Resource Selection requirement is already assumed for testing the other PRACH requirements.
A.6.2.12 E-UTRAN TDD Contention Based Random Access Test for Cat-M1
UEs in Normal Coverage
A.6.2.12.1 Test Purpose and Environment
The purpose of this test is to verify whether the behavior of the random access procedure of a Cat-M1 UE in Normal
Coverage is according to the requirements, whether the PRACH power settings and timing are within specified limits,
and whether the UE determines properly the enhanced coverage level based on the RSRP measurement and the
configured criterion in RSRP-ThresholdsPrach [2]. This test will verify the requirements in Clause 6.2.2, Clause 6.2.3
and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.12.1-1 and A.6.2.12.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 826 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.12.1-1: General test parameters for TDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern Note 1 OP.11 TDD As defined in
A.3.2.2.11.
PDSCH parameters Note 2 R.16 TDD As defined in
A.3.1.4.3
MPDCCH parameters Note 2 R.14 TDD As defined in
A.3.1.3.3
PCFICH/PDCCH/PHICH DL Reference As defined in
parameters Measurement A.3.1.2.2
Channel R.6
TDD
Special subframe - 6 As specified in
configuration table 4.2-1 in TS
36.211.
Uplink-downlink configuration - 1 As specified in
table 4.2-2 in TS
36.211.
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
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc dBm/15 KHz -98
dB 3
Ês Noc
dB 3
Ês Iot Note 3
RSRP Note 3 dBm/15 KHz -95
Io Note 3 dBm/9 MHz -65.5
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols. The
OCNG pattern is chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The PDSCH and MPDCCH reference measurement channels are used in
the test only when a downlink transmission dedicated to the UE under test is
required.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for
information purpose. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 827 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.12.1-2: RACH-Configuration parameters for TDD contention based random access test
Field Value Comment
Parameters not per CE Levels
numberOfRA-Preambles n52
sizeOfRA-PreamblesGroupA n52 No group B.
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
maxHARQ-Msg3Tx 4
rar-HoppingConfig Off
Parameters per CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
ra-ResponseWindowSize (per CE) sf20 sf80 sf180 sf320
mac-ContentionResolutionTimer (per CE) sf80 sf120 sf200 sf480
PreambleMappingInfo {0, 9} {10,19} {20,29} {30,39}
{firstPreamble, lastPreamble}
Note 1: For further information see Clause 6.3.2 in TS 36.331.
Table A.6.2.12.1-3: PRACH-Configuration parameters for TDD contention based random access test
Field Value Comment
Parameters not per CE Levels
rsrp-ThresholdsPrach {24, 31, 38} Corresponding to {-116,
-109, -102} dBm as
defined in Section
9.1.21.5
mpdcch-startSF-CSS-RA v1
referenceSignalPower -5 dBm/15 KHz As defined in clause
6.3.2 in TS 36.331.
maxHARQ-Msg3Tx 4 As defined in table
5.7.1-2 in TS 36.211
Backoff Parameter Index 2 As defined in table 7.2-1
in TS 36.321
Configured UE transmitted 23 dBm As defined in clause
power ( PCMAX ) 6.2.5 in TS 36.101
Parameters per PRACH CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
prach-ConfigIndex 53 53 53 53 As defined in table
5.7.1-2 in TS 36.211
prach-FreqOffset 0 0 0 0
prach-StartingSubframe sf2 sf4 Sf8 sf16
maxNumPreambleAttempt n3 n5 n7 n10
numRepetitionPerPreambleAtt n1 n4 n16 n64
empt
mpdcch- 2 2 2 2
NarrowbandsToMonitor
mpdcch-NumRepetition-RA r8 r8 r128 r128
prach-HoppingConfig Off Off Off Off
Note 1: See Clause 6.3.2 in TS 36.331 for further information on the parameters in this table.
A.6.2.12.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.12.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2, the System Simulator shall transmit a Random Access Response
containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble after [5]
preamble transmission attempts (the preamble may be transmitted multiple times in each attempt) have been received
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 828 ETSI TS 136 133 V14.3.0 (2017-04)
by the System Simulator. In response to the first [4] preamble transmission attempts, the System Simulator shall
transmit a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm. The power of the first preamble shall be -30 dBm with an accuracy
specified in clause 6.3.5.1.1 of TS 36.101 [5]. The relative power applied to additional preambles shall have an
accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.12.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.1.2, the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after [5] preamble transmission attempts have been received by the System Simulator. The System Simulator shall not
respond to the first [4] preamble transmission attempts.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -30 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.1.2.
A.6.2.12.2.3 Receiving a NACK on msg3
To test the UE behavior specified in subclause 6.2.2.1.3, the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
A.6.2.12.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.12.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.12.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6, the System Simulator shall not send a response to a msg3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 829 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
A.6.2.12.2.7 PRACH Resource Selection
The UE shall select PRACH resources and transmits or re- transmits PRACH preambles using the PRACH resources
and PRACH configuration corresponding to the coverage enhancement level 0.
A.6.2.13 E-UTRAN FDD Contention Based Random Access Test for Cat-M1
UEs in Enhanced Coverage
A.6.2.13.1 Test Purpose and Environment
The purpose of this test is to verify whether the behavior of the random access procedure of a Cat-M1 UE in Enhanced
Coverage is according to the requirements, whether the PRACH power settings and timing are within specified limits,
and whether the UE determines properly the enhanced coverage level based on the RSRP measurement and the
configured criterion in RSRP-ThresholdsPrach [2]. This test will verify the requirements in Clause 7.24.2, Clause 6.2.3
and Clause 7.1.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.13.1-1 and A.6.2.13.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 830 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.13.1-1: General test parameters for FDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern Note 1 OP.21 FDD As defined in
A.3.2.1.21.
PDSCH parameters Note 2 R.22 FDD As defined in
A.3.1.4.4
MPDCCH parameters Note 2 R.18 FDD As defined in
A.3.1.3.4
PCFICH/PDCCH/PHICH DL Reference As defined in
parameters Measurement A.3.1.2.1
Channel R.6
FDD
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
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc dBm/15 KHz -98
dB -12
Ês Noc
dB -12
Ês Iot Note 3
RSRP Note 3 dBm/15 KHz -110
Io Note 3 dBm/9 MHz -70
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols. The
OCNG pattern is chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The PDSCH and MPDCCH reference measurement channels are used in
the test only when a downlink transmission dedicated to the UE under test is
required.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for
information purpose. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 831 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.13.1-2: RACH-Configuration parameters for FDD contention based random access test
Field Value Comment
Parameters not per CE Levels
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
maxHARQ-Msg3Tx 4
rar-HoppingConfig Off
Parameters per CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
ra-ResponseWindowSize (per CE) sf20 sf80 sf180 sf320
mac-ContentionResolutionTimer (per CE) sf80 sf120 sf200 sf480
PreambleMappingInfo {0, 9} {10,19} {20,29} {30,39}
{firstPreamble, lastPreamble}
Note: For further information see Clause 6.3.2 in TS 36.331.
Table A.6.2.13.1-3: PRACH-Configuration parameters for FDD contention based random access test
Field Value Comment
Parameters not per CE Levels
rsrp-ThresholdsPrach {23,37,47} Corresponding to {-117,
-103, -93} dBm as
defined in Section
9.1.21.5
mpdcch-startSF-CSS-RA v1
referenceSignalPower -5 dBm/15 KHz As defined in clause
6.3.2 in TS 36.331.
maxHARQ-Msg3Tx 4 As defined in table
5.7.1-2 in TS 36.211
Backoff Parameter Index 2 As defined in table 7.2-1
in TS 36.321
Configured UE transmitted Maximum value allowed by the applicable UE As defined in clause
power ( PCMAX ) power class 6.2.5 in TS 36.101
Parameters per PRACH CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
prach-ConfigIndex 4 4 4 4 As defined in table
5.7.1-2 in TS 36.211
prach-FreqOffset 0 0 0 0
prach-StartingSubframe sf2 sf4 Sf8 sf16
maxNumPreambleAttempt n3 n5 n7 n10
numRepetitionPerPreambleAtt n1 n4 n16 n64
empt
mpdcch- 2 2 2 2
NarrowbandsToMonitor
mpdcch-NumRepetition-RA r8 r8 r128 r128
prach-HoppingConfig Off Off Off Off
Note 1: See Clause 6.3.2 in TS 36.331 for further information on the parameters in this table.
A.6.2.13.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.13.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2, the System Simulator shall transmit a Random Access Response
containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble after 5
preamble transmission attempts (the preamble may be transmitted multiple times in each attempt) have been received
by the System Simulator. In response to the first 4 preamble transmission attempts, the System Simulator shall transmit
a Random Access Response not corresponding to the transmitted Random Access Preamble.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 832 ETSI TS 136 133 V14.3.0 (2017-04)
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -27 dBm. The power of the first preamble shall be -27 dBm with an accuracy
specified in clause 6.3.5.1.1 of TS 36.101 [5]. The relative power applied to additional preambles shall have an
accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause7.24.2.
A.6.2.13.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.1.2, the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preamble transmission attempts have been received by the System Simulator. The System Simulator shall not
respond to the first 4 preamble transmission attempts.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -27 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.24.2.
A.6.2.13.2.3 Receiving a NACK on msg3
To test the UE behavior specified in subclause 6.2.2.1.3, the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
A.6.2.13.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.13.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.13.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6, the System Simulator shall not send a response to a msg3.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 833 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.2.13.2.7 PRACH Resource Selection
The UE shall select PRACH resources and transmits or re- transmits PRACH preambles using the PRACH resources
and PRACH configuration corresponding to the coverage enhancement level 2.
A.6.2.14 E-UTRAN HD-FDD Contention Based Random Access Test for Cat-
M1 UEs in Enhanced Coverage
A.6.2.14.1 Test Purpose and Environment
The purpose of this test is to verify whether the behavior of the random access procedure of a Cat-M1 UE in Enhanced
Coverage is according to the requirements, whether the PRACH power settings and timing are within specified limits,
and whether the UE determines properly the enhanced coverage level based on the RSRP measurement and the
configured criterion in RSRP-ThresholdsPrach [2]. This test will verify the requirements in Clause 6.2.2, Clause 6.2.3
and Clause 7.24.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.14.1-1 and A.6.2.14.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 834 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.14.1-1: General test parameters for HD-FDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern Note 1 OP.21 FDD As defined in
A.3.2.1.21.
PDSCH parameters Note 2 R.12 HD-FDD As defined in
A.3.1.4.5
MPDCCH parameters Note 2 R.8 HD-FDD As defined in
A.3.1.3.5
PCFICH/PDCCH/PHICH DL Reference As defined in
parameters Measurement A.3.1.2.3
Channel R.3
HD-FDD
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
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc dBm/15 KHz -98
dB -12
Ês Noc
dB -12
Ês Iot Note 3
RSRP Note 3 dBm/15 KHz -110
Io Note 3 dBm/9 MHz -70
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols. The
OCNG pattern is chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The PDSCH and MPDCCH reference measurement channels are used in
the test only when a downlink transmission dedicated to the UE under test is
required.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for
information purpose. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 835 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.14.1-2: RACH-Configuration parameters for HD-FDD contention based random access
test
Field Value Comment
Parameters not per CE Levels
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
maxHARQ-Msg3Tx 4
rar-HoppingConfig Off
Parameters per CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
ra-ResponseWindowSize (per CE) sf20 sf80 sf180 sf320
mac-ContentionResolutionTimer (per CE) sf80 sf120 sf200 sf480
PreambleMappingInfo {0, 9} {10,19} {20,29} {30,39}
{firstPreamble, lastPreamble}
Note: For further information see Clause 6.3.2 in TS 36.331.
Table A.6.2.14.1-3: PRACH-Configuration parameters for HD-FDD contention based random access
test
Field Value Comment
Parameters not per CE Levels
rsrp-ThresholdsPrach {23,37,47} Corresponding {-117, -
103, -93} dBm as
defined in Section
9.1.21.5
mpdcch-startSF-CSS-RA v1
referenceSignalPower -5 dBm/15 KHz As defined in clause
6.3.2 in TS 36.331.
maxHARQ-Msg3Tx 4 As defined in table
5.7.1-2 in TS 36.211
Backoff Parameter Index 2 As defined in table 7.2-1
in TS 36.321
Configured UE transmitted Maximum value allowed by the applicable UE As defined in clause
power ( PCMAX ) power class 6.2.5 in TS 36.101
Parameters per PRACH CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
prach-ConfigIndex 4 4 4 4 As defined in table
5.7.1-2 in TS 36.211
prach-FreqOffset 0 0 0 0
prach-StartingSubframe sf2 sf4 Sf8 sf16
maxNumPreambleAttempt n3 n5 n7 n10
numRepetitionPerPreambleAtt n1 n4 n16 n64
empt
mpdcch- 2 2 2 2
NarrowbandsToMonitor
mpdcch-NumRepetition-RA r8 r8 r128 r128
prach-HoppingConfig Off Off Off Off
Note 1: See Clause 6.3.2 in TS 36.331 for further information on the parameters in this table.
A.6.2.14.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.14.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2, the System Simulator shall transmit a Random Access Response
containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble after 5
preamble transmission attempts (the preamble may be transmitted multiple times in each attempt) have been received
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 836 ETSI TS 136 133 V14.3.0 (2017-04)
by the System Simulator. In response to the first 4 preamble transmission attempts, the System Simulator shall transmit
a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -27 dBm. The power of the first preamble shall be -27 dBm with an accuracy
specified in clause 6.3.5.1.1 of TS 36.101 [5]. The relative power applied to additional preambles shall have an
accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.24.2.
A.6.2.14.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.1.2, the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preamble transmission attempts have been received by the System Simulator. The System Simulator shall not
respond to the first 4 preamble transmission attempts.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -27 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.24.2.
A.6.2.14.2.3 Receiving a NACK on msg3
To test the UE behavior specified in subclause 6.2.2.1.3, the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
A.6.2.14.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.14.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.14.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6, the System Simulator shall not send a response to a msg3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 837 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
A.6.2.14.2.7 PRACH Resource Selection
The UE shall select PRACH resources and transmits or re- transmits PRACH preambles using the PRACH resources
and PRACH configuration corresponding to the coverage enhancement level 2.
A.6.2.15 E-UTRAN TDD Contention Based Random Access Test for Cat-M1
UEs in Enhanced Coverage
A.6.2.15.1 Test Purpose and Environment
The purpose of this test is to verify whether the behavior of the random access procedure of a Cat-M1 UE in Enhanced
Coverage is according to the requirements, whether the PRACH power settings and timing are within specified limits,
and whether the UE determines properly the enhanced coverage level based on the RSRP measurement and the
configured criterion in RSRP-ThresholdsPrach [2]. This test will verify the requirements in Clause 6.2.2, Clause 6.2.3
and Clause 7.24.2 in an AWGN model.
For this test a single cell is used. The test parameters are given in tables A.6.2.15.1-1 and A.6.2.15.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 838 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.15.1-1: General test parameters for TDD contention based random access test
Parameter Unit Value Comments
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern Note 1 OP.11 TDD As defined in
A.3.2.2.11.
PDSCH parameters Note 2 R.18 TDD As defined in
A.3.1.4.6
MPDCCH parameters Note 2 R.16 TDD As defined in
A.3.1.3.6
PCFICH/PDCCH/PHICH DL Reference As defined in
parameters Measurement A.3.1.2.2
Channel R.6
TDD
Special subframe - 6 As specified in
configuration table 4.2-1 in TS
36.211.
Uplink-downlink configuration - 1 As specified in
table 4.2-2 in TS
36.211.
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
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA Note 1 dB
OCNG_RB Note 1 dB
N oc dBm/15 KHz -98
dB -12
Ês Noc
dB -12
Ês Iot Note 3
RSRP Note 3 dBm/15 KHz -110
Io Note 3 dBm/9 MHz -70
Propagation Condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols. The
OCNG pattern is chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The PDSCH and MPDCCH reference measurement channels are used in
the test only when a downlink transmission dedicated to the UE under test is
required.
Note 3: Es/Iot, RSRP and Io level has been derived from other parameters for
information purpose. They are not settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 839 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.2.15.1-2: RACH-Configuration parameters for TDD contention based random access test
Field Value Comment
Parameters not per CE Levels
numberOfRA-Preambles n52
sizeOfRA-PreamblesGroupA n52 No group B.
powerRampingStep dB2
preambleInitialReceivedTargetPower dBm-120
preambleTransMax n6
maxHARQ-Msg3Tx 4
rar-HoppingConfig Off
Parameters per CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
ra-ResponseWindowSize (per CE) sf20 sf80 sf180 sf320
mac-ContentionResolutionTimer (per CE) sf80 sf120 sf200 sf480
PreambleMappingInfo {0, 9} {10,19} {20,29} {30,39}
{firstPreamble, lastPreamble}
Note: For further information see Clause 6.3.2 in TS 36.331.
Table A.6.2.15.1-3: PRACH-Configuration parameters for TDD contention based random access test
Field Value Comment
Parameters not per CE Levels
rsrp-ThresholdsPrach {23,37,47} Corresponding to {-117,
-103, -93} dBm as
defined in Section
9.1.21.5
mpdcch-startSF-CSS-RA v1
referenceSignalPower -5 dBm/15 KHz As defined in clause
6.3.2 in TS 36.331.
maxHARQ-Msg3Tx 4 As defined in table
5.7.1-2 in TS 36.211
Backoff Parameter Index 2 As defined in table 7.2-1
in TS 36.321
Configured UE transmitted Maximum value allowed by the applicable UE As defined in clause
power ( PCMAX ) power class 6.2.5 in TS 36.101
Parameters per PRACH CE Levels
CE Level Level 0 Level 1 Level 2 Level 3
prach-ConfigIndex 53 53 53 53 As defined in table
5.7.1-2 in TS 36.211
prach-FreqOffset 0 0 0 0
prach-StartingSubframe sf2 sf4 Sf8 sf16
maxNumPreambleAttempt n3 n5 n7 n10
numRepetitionPerPreambleAtt n1 n4 n16 n64
empt
mpdcch- 2 2 2 2
NarrowbandsToMonitor
mpdcch-NumRepetition-RA r8 r8 r128 r128
prach-HoppingConfig Off Off Off Off
Note 1: See Clause 6.3.2 in TS 36.331 for further information on the parameters in this table.
A.6.2.15.2 Test Requirements
Contention based random access is triggered by not explicitly assigning a random access preamble via dedicated
signalling in the downlink.
A.6.2.15.2.1 Random Access Response Reception
To test the UE behavior specified in Subclause 6.2.2, the System Simulator shall transmit a Random Access Response
containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble after 5
preamble transmission attempts (the preamble may be transmitted multiple times in each attempt) have been received
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 840 ETSI TS 136 133 V14.3.0 (2017-04)
by the System Simulator. In response to the first 4 preamble transmission attempts, the System Simulator shall transmit
a Random Access Response not corresponding to the transmitted Random Access Preamble.
The UE may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access
Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the
transmitted Random Access Preamble.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -27 dBm. The power of the first preamble shall be -27 dBm with an accuracy
specified in clause 6.3.5.1.1 of TS 36.101 [5]. The relative power applied to additional preambles shall have an
accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.24.2.
A.6.2.15.2.2 No Random Access Response Reception
To test the UE behavior specified in subclause 6.2.2.1.2, the System Simulator shall transmit a Random Access
Response containing a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble
after 5 preamble transmission attempts have been received by the System Simulator. The System Simulator shall not
respond to the first 4 preamble transmission attempts.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if no Random Access Response is received within the RA Response window.
In addition, the power applied to all preambles shall be in accordance with what is specified in Subclause 6.2.2. The
power of the first preamble shall be -27 dBm with an accuracy specified in clause 6.3.5.1.1 of TS 36.101 [5]. The
relative power applied to additional preambles shall have an accuracy specified in clause 6.3.5.2.1 of TS 36.101 [5].
The transmit timing of all PRACH transmissions shall be within the accuracy specified in Subclause 7.24.2.
A.6.2.15.2.3 Receiving a NACK on msg3
To test the UE behavior specified in subclause 6.2.2.1.3, the System Simulator shall NACK all UE msg3 following a
successful Random Access Response.
The UE shall re-transmit the msg3 upon the reception of a NACK on msg3 until the maximum number of HARQ re-
transmissions is reached.
A.6.2.15.2.4 Reception of an Incorrect Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element not matching the
CCCH SDU transmitted in msg3 uplink message.
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires unless the received message includes a UE Contention Resolution Identity MAC control element and the UE
Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink
message.
A.6.2.15.2.5 Reception of a Correct Message over Temporary C-RNTI
To test the UE behavior specified in Subclause 6.2.2.1.5, the System Simulator shall send a message addressed to the
temporary C-RNTI with a UE Contention Resolution Identity included in the MAC control element matching the
CCCH SDU transmitted in the msg3 uplink message.
The UE shall send ACK if the Contention Resolution is successful.
A.6.2.15.2.6 Contention Resolution Timer expiry
To test the UE behavior specified in Subclause 6.2.2.1.6, the System Simulator shall not send a response to a msg3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 841 ETSI TS 136 133 V14.3.0 (2017-04)
The UE shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time
expires if the Contention Resolution Timer expires.
A.6.2.15.2.7 PRACH Resource Selection
The UE shall select PRACH resources and transmits or re- transmits PRACH preambles using the PRACH resources
and PRACH configuration corresponding to the coverage enhancement level 2.
A.6.3 RRC Connection Release with Redirection
A.6.3.1 Redirection from E-UTRAN FDD to UTRAN FDD
A.6.3.1.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct performing the RRC connection release with redirection
to the target UTRAN FDD cell. This test will partly verify the RRC connection release with redirection to UTRAN
FDD cell requirements in clause 6.3.2.1.
The test parameters are given in Tables A.6.3.1.1-1, A.6.3.1.1-2 and A.6.3.1.1-3 below. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. The “RRCConnectionRelease” message
containing the relevant system information of Cell 2 shall be sent to the UE during period T1 and the start of T2 is the
instant when the last TTI containing the RRC message is sent to the UE. Prior to time duration T2, the UE shall not
have any timing information of Cell 2. Cell 2 is powered up at the beginning of the T2.
Table A.6.3.1.1-1: General test parameters for RRC Connection Release with Redirection from E-
UTRAN FDD to UTRAN FDD under AWGN propagation conditions
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN FDD) DL Reference Measurement As specified in clause A.3.1.1.1.
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1.
(E-UTRAN FDD) Channel R.6 FDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number 1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel number 1.
CP length Normal Applicable to cell 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
UTRA RF Channel Number 1 One UTRA FDD carrier frequency is used.
Inter-RAT (UTRA FDD) CPICH Ec/Io
measurement quantity
Filter coefficient 0 L3 filtering is not used.
DRX OFF
UTRA FDD cell list size 16 UTRA cells on UTRA RF channel 1 provided
in the “RRCConnectionRelease” message
from the E-UTRAN
T1 s ≤5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 842 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.1.1-2: Cell specific test parameters for cell #1 E-UTRAN FDD to UTRAN FDD RRC release
with redirection under AWGN propagation conditions
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.1.1 (OP.1 FDD) OP.1 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.6.3.1.1-3: Cell specific test parameters for cell #2 E-UTRAN FDD to UTRAN FDD RRC release
with redirection under AWGN propagation conditions
Parameter Unit Cell 2
T1 T1
UTRA RF Channel Number 1
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
DPCH_Ec/Ior dB N/A
OCNS -0.941
Iˆor I oc dB -∞ 0.02
I oc dBm/3.84
-70
MHz
CPICH_Ec/IoNote 3 dB -∞ -13
Propagation Condition AWGN
Note 1: The DPCH level is controlled by the power control loop.
Note 2: The power of the OCNS channel that is added shall make the total power from the cell to be equal
to Ior.
Note 3: This gives an SCH Ec/Io of -15dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 843 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.3.1.2 Test Requirements
The UE shall start to transmit random access to Cell 2 less than 650 ms from the beginning of time period T2.
The rate of correct RRC connection release redirection to UTRAN FDD observed during repeated tests shall be at least
90%.
NOTE: The Re-establishment delay in this case can be expressed as
Tconnection_release_redirect_UTRA FDD = TRRC_procedure_delay + Tidentify-UTRA FDD + TSI-UTRA FDD + TRA
where
TRRC_procedure_delay = 110 ms
Tidentify-UTRA FDD = 500 ms
TSI-UTRA FDD = the time required for acquiring all the relevant system information of the target UTRA FDD cell.
This time depends upon whether the UE is provided with the relevant system information of the target UTRA
FDD cell or not by the E-UTRAN before the RRC connection is released. 0 ms is assumed in this test case.
TRA = The additional delay caused by the random access procedure. 40 ms is assumed in this test case.
This gives a total of 650 ms.
A.6.3.2 Redirection from E-UTRAN TDD to UTRAN FDD
A.6.3.2.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct performing the RRC connection release with redirection
to the target UTRAN FDD cell. This test will partly verify the RRC connection release with redirection to UTRAN
FDD cell requirements in clause 6.3.2.1.
The test parameters are given in Tables A.6.3.2.1-1, A.6.3.2.1-2 and A.6.3.2.1-3 below. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. The “RRCConnectionRelease” message
containing the relevant system information of Cell 2 shall be sent to the UE during period T1 and the start of T2 is the
instant when the last TTI containing the RRC message is sent to the UE. Prior to time duration T2, the UE shall not
have any timing information of cell 2. Cell 2 is powered up at the beginning of the T2,
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 844 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.2.1-1: General test parameters for RRC Connection Release with Redirection from E-
UTRAN TDD to UTRAN FDD under AWGN propagation conditions
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN TDD) DL Reference Measurement As specified in clause A.3.1.1.2.
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2.
(E-UTRAN TDD) Channel R.6 TDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number 1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel number 1.
CP length Normal Applicable to cell 1
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211
UTRA RF Channel Number 1 One UTRA FDD carrier frequency is used.
Inter-RAT (UTRA FDD) CPICH Ec/Io
measurement quantity
Filter coefficient 0 L3 filtering is not used.
DRX OFF
UTRA FDD cell list size 16 UTRA cells on UTRA RF channel 1 provided
in the “RRCConnectionRelease” message
from the E-UTRAN
T1 s ≤5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 845 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.2.1-2: Cell specific test parameters for cell #1 E-UTRAN TDD to UTRAN FDD RRC release
with redirection under AWGN propagation conditions
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.2.1 (OP.1 TDD) OP.1 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.6.3.2.1-3: Cell specific test parameters for cell #2 E-UTRAN TDD to UTRAN FDD RRC release
with redirection under AWGN propagation conditions
Parameter Unit Cell 2
T1 T2
UTRA RF Channel Number 1
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
DPCH_Ec/Ior dB N/A
OCNS -0.941
Iˆor I oc dB -∞ 0.02
I oc dBm/3.84
-70
MHz
CPICH_Ec/IoNote 3 dB -∞ -13
Propagation Condition AWGN
Note 1: The DPCH level is controlled by the power control loop.
Note 2: The power of the OCNS channel that is added shall make the total power from the cell to be equal
to Ior.
Note 3: This gives an SCH Ec/Io of -15dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 846 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.3.2.2 Test Requirements
The UE shall start to transmit random access to Cell 2 less than 650 ms from the beginning of time period T2.
The rate of correct RRC connection release redirection to UTRA FDD observed during repeated tests shall be at least
90%.
NOTE: The Re-establishment delay in this case can be expressed as
Tconnection_release_redirect_UTRA FDD = TRRC_procedure_delay + Tidentify-UTRA FDD + TSI-UTRA FDD + TRA
where
TRRC_procedure_delay = 110 ms
Tidentify-UTRA FDD = 500 ms
TSI-UTRA FDD = the time required for acquiring all the relevant system information of the target UTRA FDD cell.
This time depends upon whether the UE is provided with the relevant system information of the target UTRA
FDD cell or not by the E-UTRAN before the RRC connection is released. 0 ms is assumed in this test case.
TRA = The additional delay caused by the random access procedure. 40 ms is assumed in this test case.
This gives a total of 650 ms.
A.6.3.3 Redirection from E-UTRAN FDD to GERAN when System
Information is provided
A.6.3.3.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA FDD to the target GERAN cell within Tconnection_release_redirect_GERAN. This test will partly verify the RRC
connection release with redirection to GERAN requirements in clause 6.3.2.2.
The test parameters are given in Tables A.6.3.3.1-1, A.6.3.3.1-2 and A.6.3.3.1-3 below. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The start of T2 is the instant when the last TTI
containing the RRC message, “RRCConnectionRelease”, is received by the UE from cell 1. The
“RRCConnectionRelease” message shall contain all the relevant system information of cell 2.
Table A.6.3.3.1-1: General test parameters for RRC connection release with redirection from E-
UTRAN FDD to GERAN in AWGN
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN FDD) DL Reference Measurement As specified in clause A.3.1.1.1.
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1.
(E-UTRAN FDD) Channel R.6 FDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number 1.
Neighbour cell Cell 2 Cell 2 is on Absolute RF Channel Number 1
(GSM cell)
CP length Normal Applicable to cell 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
DRX OFF
Monitored GSM cell list size 6 GSM neighbour including GSM cells are provided in the
ARFCN 1 “RRCConnectionRelease” message.
T1 s 5
T2 s 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 847 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.3.1-2: Cell specific test parameters for E-UTRA FDD cell (cell #1) for RRC connection
release with redirection from E-UTRAN FDD to GERAN in AWGN
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BWchannel MHz 10
OCNG Pattern defined in
A.3.2.1.1 (OP.1 FDD) OP.1 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
dB 4 4
Ê s N oc
N oc dBm/15 kHz -98
RSRP dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.6.3.3.1-3: Cell specific test parameters for GERAN cell (cell #2) for RRC connection release
with redirection from E-UTRAN FDD to GERAN in AWGN
Parameter Unit Cell 2
T1 T2
Absolute RF Channel Number ARFNC 1
RXLEV dBm -Infinity -75
GSM BSIC N/A Valid
A.6.3.3.2 Test Requirements
The UE shall begin to send access bursts on RACH of the target GERAN cell (cell #2) less than 1120 ms from the
beginning of time period T2.
The rate of correct “RRC connection release with redirection to GERAN” observed during repeated tests shall be at
least 90%.
NOTE: The test requirement in this test case is expressed as:
Tconnection_release_redirect_ GERAN = TRRC_procedure_delay + Tidentify-GERAN + TSI-GERAN + TRA
TRRC_procedure_delay = 110 ms, which is the time for processing the received message “RRCConnectionRelease.
Tidentify-GERAN = 1000 ms, which is the time for identifying the target GERAN cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 848 ETSI TS 136 133 V14.3.0 (2017-04)
TSI-GERAN = 0; UE does not have to read the system information of the GERAN cell since all relevant SI is provided
to the UE in the “RRCConnectionRelease” message.
TRA = 10 ms, which is about 2 GSM frames (2*4.65 ms) to account for the GSM timing uncertainty.
A.6.3.4 Redirection from E-UTRAN TDD to GERAN when System
Information is provided
A.6.3.4.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA TDD to the target GERAN cell within Tconnection_release_redirect_GERAN. This test will partly verify the RRC
connection release with redirection to GERAN requirements in clause 6.3.2.2.
The test parameters are given in Tables A.6.3.4.1-1, A.6.3.4.1-2 and A.6.3.4.1-3 below. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The start of T2 is the instant when the last TTI
containing the RRC message, “RRCConnectionRelease”, is received by the UE from cell 1. The
“RRCConnectionRelease” message shall contain all the relevant system information of cell 2.
Table A.6.3.4.1-1: General test parameters for RRC connection release with redirection from E-
UTRAN TDD to GERAN in AWGN
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN TDD) DL Reference Measurement As specified in clause A.3.1.1.2.
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2.
(E-UTRAN TDD) Channel R.6 TDD
Active Cell 1 Cell 1 is on E-UTRA RF channel number 1.
Neighbour cell Cell 2 Cell 2 is on Absolute RF Channel Number 1
(GSM cell)
CP length Normal Applicable to cell 1
Special subframe configuration As specified in table 4.2.1 in TS 36.211. The
6
same configuration applies to all cells.
Uplink-downlink configuration 1
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
DRX OFF
Monitored GSM cell list size 6 GSM neighbour including GSM cells provided in the
ARFCN 1 “RRCConnectionRelease” message.
T1 s 5
T2 s 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 849 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.4.1-2: Cell specific test parameters for E-UTRA TDD cell (cell #1) for RRC connection
release with redirection from E-UTRAN TDD to GERAN in AWGN
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.2.1 (OP.1 TDD) OP.1 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
dB 4 4
Ê s N oc
N oc dBm/15 kHz -98
RSRP dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.6.3.4.1-3: Cell specific test parameters for GERAN cell (cell #2) for RRC connection release
with redirection from E-UTRAN TDD to GERAN in AWGN
Parameter Unit Cell 2
T1 T2
Absolute RF Channel Number ARFNC 1
RXLEV dBm -Infinity -75
GSM BSIC N/A Valid
A.6.3.4.2 Test Requirements
The UE shall begin to send access bursts on RACH of the target GERAN cell (cell #2) less than 1120 ms from the
beginning of time period T2.
The rate of correct “RRC connection release with redirection to GERAN” observed during repeated tests shall be at
least 90%.
NOTE: The test requirement in this test case is expressed as:
Tconnection_release_redirect_ GERAN = TRRC_procedure_delay + Tidentify-GERAN + TSI-GERAN + TRA
TRRC_procedure_delay = 110 ms, which is the time for processing the received message “RRCConnectionRelease.
Tidentify-GERAN = 1000 ms, which is the time for identifying the target GERAN cell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 850 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.3.5 E-UTRA TDD RRC connection release redirection to UTRA TDD
A.6.3.5.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA TDD to the target UTRA TDD cell within Tconnection_release_redirect_UTRA TDD. This test will partly verify the RRC
connection release with redirection to UTRA TDD requirements in clause 6.3.2.3.
The test parameters are given in table A.6.3.5.1-1, table A.6.3.5.1-2, and table A.6.3.5.1-3. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The “RRCConnectionRelease” message containing
the relevant system information of Cell 2 shall be sent to the UE during period T1 and the start of T2 is the instant when
the last TTI containing the RRC message, “RRCConnectionRelease”, is received by the UE from cell 1. The
“RRCConnectionRelease” message shall contain all the relevant system information of Cell 2.
Table A.6.3.5.1-1: General test parameters for E-UTRA TDD RRC connection release redirection to
UTRA TDD
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN DL Reference Measurement As specified in clause A.3.1.1.2.
TDD) Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2.
parameters (E-UTRAN TDD) Channel R.6 TDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number
1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel number 1.
Time offset between cells ms 3 Asynchronous cells
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal Applicable to cell 1
Special subframe configuration of 6 As specified in table 4.2.1 in TS 36.211
cell 1
Uplink-downlink configuration of 1 As specified in table 4.2-2 in TS 36.211
cell 1
UTRA RF Channel Number 1 One UTRA TDD carrier frequency is
used.
UTRA RF Channel Number 1 One UTRA TDD carrier frequency is
used.
Filter coefficient 0 L3 filtering is not used.
DRX OFF
Monitored UTRA TDD cell list size 16 UTRA cells on UTRA RF channel 1
provided in the “RRCConnectionRelease”
message from the E-UTRAN
T1 s 5
T2 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 851 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.5.1-2: Cell specific test parameters for cell 1 in E-UTRA TDD RRC connection release
redirection to UTRA TDD test
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.2.1 (OP.1 TDD) OP.1 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 852 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.5.1-3: Cell specific test parameters for cell 2 in E-UTRA TDD RRC connection release
redirection to UTRA TDD test
Parameter Unit Cell 2 (UTRA TDD)
Timeslot Number 0 DwPTS
T1 T2 T1 T2
UTRA RF Channel NumberNote1 Channel 1
PCCPCH_Ec/Ior dB -4.77 -4.77
DwPCH_Ec/Ior dB 0 0
OCNS_Ec/IorNote2 dB -1.76 -1.76
Iˆor I oc dB -inf 8 -inf 8
dBm/1.28
I oc MHz
-80
PCCPCH RSCP Note3 dBm -inf -76.77 n.a. n.a.
PCCPCH_Ec/Io Note3 dB -inf -5.41 n.a. n.a.
DwPCH_Ec/Io Note3 dB n.a. n.a. -inf -0.64
Propagation Condition AWGN
Note 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary
frequency’s channel number.
Note 2: The power of the OCNS channel that is added shall make the total power from the
cell to be equal to Ior.
Note 3: P-CCPCH RSRP, PCCPCH_Ec/Io and DwPCH_Ec/Io levels have been derived from
other parameters for information purposes. They are not settable parameters
themselves.
A.6.3.5.2 Test Requirements
The UE shall start to transmit the SYNCH-UL sequence in the UpPTS to Cell 2 less than 650 ms from the beginning of
time period T2.
The rate of correct RRC connection release redirection to UTRA TDD observed during repeated tests shall be at least
90%.
NOTE: The time delay can be expressed as: TRRC_procedure_delay + Tidentify-UTRA TDD + TSI-UTRA TDD + TRA, where:
TRRC_procedure_delay = 110 ms, which is specified in clause 6.3.2.3.
Tidentify-UTRA TDD = 500 ms; which is defined in clause 6.3.2.3.
TSI-UTRA TDD = 0 ms, UE does not have to read the system information of the UTRAN TDD since all relevant SI is
provided to the UE in the “RRCConnectionRelease” message.
TRA = 40ms. This is the additional delay caused by the random access procedure
It gives a total delay of 650 ms.
A.6.3.6 E-UTRA FDD RRC connection release redirection to UTRA TDD
A.6.3.6.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA FDD to the target UTRA TDD cell within Tconnection_release_redirect_UTRA TDD. This test will partly verify the RRC
connection release with redirection to UTRA TDD requirements in clause 6.3.2.3.
The test parameters are given in table A.6.3.6.1-1, table A.6.3.6.1-2, and table A.6.3.6.1-3. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The “RRCConnectionRelease” message containing
the relevant system information of Cell 2 shall be sent to the UE during period T1 and the start of T2 is the instant when
the last TTI containing the RRC message, “RRCConnectionRelease”, is received by the UE from cell 1. The
“RRCConnectionRelease” message shall contain all the relevant system information of Cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 853 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.6.1-1: General test parameters for E-UTRA FDD RRC connection release redirection to
UTRA TDD
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN DL Reference Measurement As specified in clause A.3.1.1.1.
FDD) Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1.
parameters (E-UTRAN FDD) Channel R.6 FDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number
1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel number 1.
CP length Normal Applicable to cell 1
Time offset between cells ms 3 Asynchronous cells
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Filter coefficient 0 L3 filtering is not used.
DRX OFF
Monitored UTRA TDD cell list size 16 UTRA cells on UTRA RF channel 1
provided in the “RRCConnectionRelease”
message from the E-UTRAN
T1 s 5
T2 s 1
Table A.6.3.6.1-2: Cell specific test parameters for cell 1 in E-UTRA FDD RRC connection release
redirection to UTRA TDD test
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Patterns defined in
OP.1 FDD
A.3.2.1.1 (OP.1 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 854 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.6.1-3: Cell specific test parameters for cell 2 in E-UTRA FDD RRC connection release
redirection to UTRA TDD test
Parameter Unit Cell 2 (UTRA TDD)
Timeslot Number 0 DwPTS
T1 T2 T1 T2
UTRA RF Channel NumberNote1 Channel 1
PCCPCH_Ec/Ior dB -4.77 -4.77
DwPCH_Ec/Ior dB 0 0
OCNS_Ec/IorNote2 dB -1.76 -1.76
Iˆor I oc dB -inf 8 -inf 8
dBm/1.28
I oc MHz
-80
PCCPCH RSCP Note3 dBm -inf -76.77 n.a. n.a.
PCCPCH_Ec/Io Note3 dB -inf -5.41 n.a. n.a.
DwPCH_Ec/Io Note3 dB n.a. n.a. -inf -0.64
Propagation Condition AWGN
Note 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary
frequency’s channel number.
Note 2: The power of the OCNS channel that is added shall make the total power from the
cell to be equal to Ior.
Note 3: P-CCPCH RSRP, PCCPCH_Ec/Io and DwPCH_Ec/Io levels have been derived from
other parameters for information purposes. They are not settable parameters
themselves.
A. 6.3.6.2 Test Requirements
The UE shall start to transmit the SYNCH-UL sequence in the UpPTS to Cell 2 less than 650 ms from the beginning of
time period T2.
The rate of correct RRC connection release redirection to UTRA TDD observed during repeated tests shall be at least
90%.
NOTE: The time delay can be expressed as: TRRC_procedure_delay + Tidentify-UTRA TDD + TSI-UTRA TDD + TRA, where:
TRRC_procedure_delay = 110 ms, which is specified in clause 6.3.2.3.
Tidentify-UTRA TDD = 500 ms; which is defined in clause 6.3.2.3.
TSI-UTRA TDD = 0 ms, UE does not have to read the system information of the UTRAN TDD since all relevant SI is
provided to the UE in the “RRCConnectionRelease” message.
TRA = 40ms. This is the additional delay caused by the random access procedure.
This gives a total delay of 650 ms.
A.6.3.7 E-UTRA TDD RRC connection release redirection to UTRA TDD
without SI provided
A.6.3.7.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA TDD to the target UTRA TDD cell within Tconnection_release_redirect_UTRA TDD. This test will partly verify the RRC
connection release with redirection to UTRA TDD requirements in clause 6.3.2.3.
The test parameters are given in table A.6.3.7.1-1, table A.6.3.7.1-2, and table A.6.3.7.1-3. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The “RRCConnectionRelease” message not
containing the relevant system information of Cell 2 shall be sent to the UE during period T1 and the start of T2 is the
instant when the last TTI containing the RRC message, “RRCConnectionRelease”, is received by the UE from Cell 1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 855 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.7.1-1: General test parameters for E-UTRA TDD RRC connection release redirection to
UTRA TDD without SI provided
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN DL Reference Measurement As specified in clause A.3.1.1.2.
TDD) Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2.
parameters (E-UTRAN TDD) Channel R.6 TDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number
1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel number 1.
Time offset between cells ms 3 Asynchronous cells
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal Applicable to cell 1
Uplink-downlink configuration of 1 As specified in table 4.2.2 in TS 36.211
cell 1
Special subframe configuration of 6 As specified in table 4.2.1 in TS 36.211
cell 1
UTRA RF Channel Number 1 One UTRA TDD carrier frequency is
used.
Filter coefficient 0 L3 filtering is not used.
DRX OFF
Monitored UTRA TDD cell list size none No explicit neighbour list is provided to
the UE
T1 s 5
T2 s 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 856 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.7.1-2: Cell specific test parameters for cell 1 in E-UTRA TDD RRC connection release
redirection to UTRA TDD test without SI provided
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.2.1 (OP.1 TDD) OP.1 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 857 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.7.1-3: Cell specific test parameters for cell 2 in E-UTRA TDD RRC connection release
redirection to UTRA TDD test without SI provided
Parameter Unit Cell 2 (UTRA TDD)
Timeslot Number 0 DwPTS
T1 T2 T1 T2
UTRA RF Channel NumberNote1 Channel 1
PCCPCH_Ec/Ior dB -4.77 -4.77
DwPCH_Ec/Ior dB 0 0
OCNS_Ec/IorNote2 dB -1.76 -1.76
Iˆor I oc dB -inf 8 -inf 8
dBm/1.28
I oc MHz
-80
PCCPCH RSCP Note3 dBm -inf -76.77 n.a. n.a.
PCCPCH_Ec/Io Note3 dB -inf -5.41 n.a. n.a.
DwPCH_Ec/Io Note3 dB n.a. n.a. -inf -0.64
Propagation Condition AWGN
Note 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary
frequency’s channel number.
Note 2: The power of the OCNS channel that is added shall make the total power from the
cell to be equal to Ior.
Note 3: P-CCPCH RSRP, PCCPCH_Ec/Io and DwPCH_Ec/Io levels have been derived from
other parameters for information purposes. They are not settable parameters
themselves.
A.6.3.7.2 Test Requirements
The UE shall start to transmit the SYNCH-UL sequence in the UpPTS to Cell 2 less than 1930 ms from the beginning
of time period T2.
The rate of correct RRC connection release redirection to UTRA TDD observed during repeated tests shall be at least
90%.
NOTE: The time delay can be expressed as: TRRC_procedure_delay + Tidentify-UTRA TDD + TSI-UTRA TDD + TRA, where:
TRRC_procedure_delay = 110 ms, which is specified in clause 6.3.2.3.
Tidentify-UTRA TDD = 500 ms; which is defined in clause 6.3.2.3.
TSI-UTRA TDD: Maximum repetition period of relevant system info blocks that need to be received by the UE during
RRC connection release redirection to UTRA TDD cell. 1280 ms is assumed in this test case.
TRA = 40ms, this is the additional delay caused by the random access procedure.
This gives a total delay of 1930 ms.
A.6.3.8 E-UTRA FDD RRC connection release redirection to UTRA TDD
without SI provided
A.6.3.8.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA FDD to the target UTRA TDD cell within Tconnection_release_redirect_UTRA TDD. This test will partly verify the RRC
connection release with redirection to UTRA TDD requirements in clause 6.3.2.3.
The test parameters are given in table A.6.3.8.1-1, table A.6.3.8.1-2, and table A.6.3.8.1-3. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The “RRCConnectionRelease” message not
containing the relevant system information of Cell 2 shall be sent to the UE during period T1 and the start of T2 is the
instant when the last TTI containing the RRC message, “RRCConnectionRelease”, is received by the UE from Cell 1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 858 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.8.1-1: General test parameters for E-UTRA FDD RRC connection release redirection to
UTRA TDD without SI provided
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN DL Reference Measurement As specified in clause A.3.1.1.1.
FDD) Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1.
parameters (E-UTRAN FDD) Channel R.6 FDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number
1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel number 1.
Time offset between cells ms 3 Asynchronous cells
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal Applicable to cell 1
UTRA RF Channel Number 1 One UTRA TDD carrier frequency is
used.
Filter coefficient 0 L3 filtering is not used.
DRX OFF
Monitored UTRA TDD cell list size none No explicit neighbour list is provided to
the UE
T1 S 5
T2 S 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 859 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.8.1-2: Cell specific test parameters for cell 1 in E-UTRA FDD RRC connection release
redirection to UTRA TDD test without SI provided
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Patterns defined in OP.1 FDD
A.3.2.1.1 (OP.1 FDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 860 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.8.1-3: Cell specific test parameters for cell 2 in E-UTRA FDD RRC connection release
redirection to UTRA TDD test without SI provided
Parameter Unit Cell 2 (UTRA TDD)
Timeslot Number 0 DwPTS
T1 T2 T1 T2
UTRA RF Channel NumberNote1 Channel 1
PCCPCH_Ec/Ior dB -4.77 -4.77
DwPCH_Ec/Ior dB 0 0
OCNS_Ec/IorNote2 dB -1.76 -1.76
Iˆor I oc dB -inf 8 -inf 8
dBm/1.28
I oc MHz
-80
PCCPCH RSCP Note3 dBm -inf -76.77 n.a. n.a.
PCCPCH_Ec/Io Note3 dB -inf -5.41 n.a. n.a.
DwPCH_Ec/Io Note3 dB n.a. n.a. -inf -0.64
Propagation Condition AWGN
Note 1: In the case of multi-frequency cell, the UTRA RF Channel Number is the primary
frequency’s channel number.
Note 2: The power of the OCNS channel that is added shall make the total power from the
cell to be equal to Ior.
Note 3: P-CCPCH RSRP, PCCPCH_Ec/Io and DwPCH_Ec/Io levels have been derived from
other parameters for information purposes. They are not settable parameters
themselves.
A.6.3.8.2 Test Requirements
The UE shall start to transmit the SYNCH-UL sequence in the UpPTS to Cell 2 less than 1930 ms from the beginning
of time period T2.
The rate of correct RRC connection release redirection to UTRA TDD observed during repeated tests shall be at least
90%.
NOTE: The time delay can be expressed as: TRRC_procedure_delay + Tidentify-UTRA TDD + TSI-UTRA TDD + TRA, where:
TRRC_procedure_delay = 110 ms, which is specified in clause 6.3.2.3.
Tidentify-UTRA TDD = 500 ms; which is defined in clause 6.3.2.3.
TSI-UTRA TDD: Maximum repetition period of relevant system info blocks that need to be received by the UE during
RRC connection release redirection to UTRA TDD cell. 1280 ms is assumed in this test case.
TRA = 40ms, this is the additional delay caused by the random access procedure.
This gives a total delay of 1930 ms.
A.6.3.9 Redirection from E-UTRAN FDD to UTRAN FDD without System
Information
A.6.3.9.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct performing the RRC connection release with redirection
to the target UTRAN FDD cell. This test will partly verify the RRC connection release with redirection to UTRAN
FDD cell requirements in clause 6.3.2.1.
The test parameters are given in Tables A.6.3.9.1-1, A.6.3.9.1-2 and A.6.3.9.1-3 below. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. The “RRCConnectionRelease” message not
containing any system information of Cell 2 shall be sent to the UE during period T1. The start of T2 is the instant when
the last TTI containing the RRC message is sent to the UE. Prior to time duration T2, the UE shall not have any timing
information of Cell 2. Cell 2 is powered up at the beginning of the T2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 861 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.9.1-1: General test parameters for RRC Connection Release with Redirection from E-
UTRAN FDD to UTRAN FDD under AWGN propagation conditions
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN FDD) DL Reference Measurement As specified in clause A.3.1.1.1.
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1.
(E-UTRAN FDD) Channel R.6 FDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number 1.
Neighbour cell Cell 2 Cell 2 is on UTRA RF channel number 1.
CP length Normal Applicable to cell 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
UTRA RF Channel Number 1 One UTRA FDD carrier frequency is used.
Inter-RAT (UTRA FDD) CPICH Ec/Io
measurement quantity
Filter coefficient 0 L3 filtering is not used.
DRX OFF
UTRA FDD cell list size None No explicit neighbour list is provided to the UE
T1 s ≤5
T2 s 2
Table A.6.3.9.1-2: Cell specific test parameters for cell #1 E-UTRAN FDD to UTRAN FDD RRC release
with redirection under AWGN propagation conditions
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.1.1 (OP.1 FDD) OP.1 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 862 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.9.1-3: Cell specific test parameters for cell #2 E-UTRAN FDD to UTRAN FDD RRC release
with redirection under AWGN propagation conditions
Parameter Unit Cell 2
T1 T1
UTRA RF Channel Number 1
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
DPCH_Ec/Ior dB N/A
OCNS -0.941
Iˆor I oc dB -∞ 0.02
I oc dBm/3.84
-70
MHz
CPICH_Ec/IoNote 3 dB -∞ -13
Propagation Condition AWGN
Note 1: The DPCH level is controlled by the power control loop.
Note 2: The power of the OCNS channel that is added shall make the total power from the cell to be equal
to Ior.
Note 3: This gives an SCH Ec/Io of -15dB
A.6.3.9.2 Test Requirements
The UE shall start to send random access to the target UTRA FDD cell (Cell 2) less than 1930 ms from the beginning of
time period T2.
The rate of correct “RRC connection release with redirection to UTRAN” observed during repeated tests shall be at
least 90%.
NOTE: The test requirement in this case can be expressed as
Tconnection_release_redirect_UTRA FDD = TRRC_procedure_delay + Tidentify-UTRA FDD + TSI-UTRA FDD + TRA
where
TRRC_procedure_delay = 110 ms
Tidentify-UTRA FDD = 500 ms
TSI-UTRA FDD = the time required for acquiring all the relevant system information of the target UTRA FDD
cell. This time depends upon whether the UE is provided with the relevant system information of the
target UTRA FDD cell or not by the E-UTRAN before the RRC connection is released. Since no SI is
provided, 1280 ms is assumed in this test case.
TRA = The additional delay caused by the random access procedure. 40 ms is assumed in this test case.
This gives a total of 1930 ms.
A.6.3.10 Redirection from E-UTRAN FDD to GERAN when System
Information is not provided
A.6.3.10.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA FDD to the target GERAN cell within Tconnection_release_redirect_GERAN. This test will partly verify the RRC
connection release with redirection to GERAN requirements in clause 6.3.2.2.
The test parameters are given in Tables A.6.3.10.1-1, A.6.3.10.1-2 and A.6.3.10.1-3 below. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The start of T2 is the instant when the last TTI
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 863 ETSI TS 136 133 V14.3.0 (2017-04)
containing the RRC message, “RRCConnectionRelease”, is received by the UE from cell 1. The
“RRCConnectionRelease” message shall not contain any system information of cell 2.
Table A.6.3.10.1-1: General test parameters for RRC connection release with redirection from E-
UTRAN FDD to GERAN in AWGN
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN FDD) DL Reference Measurement As specified in clause A.3.1.1.1.
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1.
(E-UTRAN FDD) Channel R.6 FDD
Active cell Cell 1 Cell 1 is on E-UTRA RF channel number 1.
Neighbour cell Cell 2 Cell 2 is on Absolute RF Channel Number 1
(GSM cell)
CP length Normal Applicable to cell 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
DRX OFF
Monitored GSM cell list size 6 GSM neighbour including Only the list of GERAN carrier frequencies is
ARFCN 1 provided in the “RRCConnectionRelease”
message.
T1 s ≤5
T2 s 4
Table A.6.3.10.1-2: Cell specific test parameters for E-UTRA FDD cell (cell #1) for RRC connection
release with redirection from E-UTRAN FDD to GERAN in AWGN
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.1.1 (OP.1 FDD) OP.1 FDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
dB 4 4
Ê s N oc
N oc dBm/15 kHz -98
RSRP dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 864 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.10.1-3: Cell specific test parameters for GERAN cell (cell #2) for RRC connection release
with redirection from E-UTRAN FDD to GERAN in AWGN
Parameter Unit Cell 2
T1 T2
Absolute RF Channel Number ARFNC 1
RXLEV dBm -Infinity -75
GSM BSIC N/A Valid
A.6.3.10.2 Test Requirements
The UE shall begin to send access bursts on RACH of the target GERAN cell (cell #2) less than 3020 ms from the
beginning of time period T2.
The rate of correct “RRC connection release with redirection to GERAN” observed during repeated tests shall be at
least 90%.
NOTE: The test requirement in this test case is expressed as:
Tconnection_release_redirect_ GERAN = TRRC_procedure_delay + Tidentify-GERAN + TSI-GERAN + TRA
TRRC_procedure_delay = 110 ms, which is the time for processing the received message “RRCConnectionRelease.
Tidentify-GERAN = 1000 ms, which is the time for identifying the target GERAN cell.
TSI-GERAN = 1900 ms, which is the maximum time allowed to read BCCH data from the target GERAN cell.
TRA = 10 ms, which is about 2 GSM frames (2*4.65 ms) to account for the GSM timing uncertainty.
A.6.3.11 Redirection from E-UTRAN TDD to GERAN when System
Information is not provided
A.6.3.11.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRA TDD to the target GERAN cell within Tconnection_release_redirect_GERAN. This test will partly verify the RRC
connection release with redirection to GERAN requirements in clause 6.3.2.2.
The test parameters are given in Tables A.6.3.11.1-1, A.6.3.11.1-2 and A.6.3.11.1-3 below. No measurement gaps are
configured. The test consists of two successive time periods, with time duration of T1, and T2 respectively. During time
duration T1, the UE shall not have any timing information of cell 2. The start of T2 is the instant when the last TTI
containing the RRC message, “RRCConnectionRelease”, is received by the UE from cell 1. The
“RRCConnectionRelease” message shall not contain any system information of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 865 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.11.1-1: General test parameters for RRC connection release with redirection from E-
UTRAN TDD to GERAN in AWGN
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN TDD) DL Reference Measurement As specified in clause A.3.1.1.2.
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2.
(E-UTRAN TDD) Channel R.6 TDD
Active Cell 1 Cell 1 is on E-UTRA RF channel number 1.
Neighbour cell Cell 2 Cell 2 is on Absolute RF Channel Number 1
(GSM cell)
CP length Normal Applicable to cell 1
Special subframe configuration As specified in table 4.2.1 in TS 36.211. The
6
same configuration applies to all cells.
Uplink-downlink configuration 1
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
DRX OFF
Monitored GSM cell list size 6 GSM neighbour including Only the list of GERAN carrier frequencies is
ARFCN 1 provided in the “RRCConnectionRelease”
message.
T1 s ≤5
T2 s 4
Table A.6.3.11.1-2: Cell specific test parameters for E-UTRA TDD cell (cell #1) for RRC connection
release with redirection from E-UTRAN TDD to GERAN in AWGN
Parameter Unit Cell 1
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Pattern defined in
A.3.2.2.1 (OP.1 TDD) OP.1 TDD
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
dB 4 4
Ê s N oc
N oc dBm/15 kHz -98
RSRP dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 866 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.11.1-3: Cell specific test parameters for GERAN cell (cell #2) for RRC connection release
with redirection from E-UTRAN TDD to GERAN in AWGN
Parameter Unit Cell 2
T1 T2
Absolute RF Channel Number ARFNC 1
RXLEV dBm -Infinity -75
GSM BSIC N/A Valid
A.6.3.11.2 Test Requirements
The UE shall begin to send access bursts on RACH of the target GERAN cell (cell #2) less than 3020 ms from the
beginning of time period T2.
The rate of correct “RRC connection release with redirection to GERAN” observed during repeated tests shall be at
least 90%.
NOTE: The test requirement in this test case is expressed as:
Tconnection_release_redirect_ GERAN = TRRC_procedure_delay + Tidentify-GERAN + TSI-GERAN + TRA
TRRC_procedure_delay = 110 ms, which is the time for processing the received message “RRCConnectionRelease.
Tidentify-GERAN = 1000 ms, which is the time for identifying the target GERAN cell.
TSI-GERAN = 1900 ms, which is the maximum time allowed to read BCCH data from the target GERAN cell.
TRA = 10 ms, which is about 2 GSM frames (2*4.65 ms) to account for the GSM timing uncertainty.
A.6.3.12 E-UTRAN TDD RRC connection release redirection to UTRAN FDD
without SI provided
A.6.3.12.1 Test Purpose and Environment
The purpose of this test is to verify that the UE performs the RRC connection release with redirection from the E-
UTRAN TDD to the target UTRAN FDD cell within Tconnection_release_redirect_UTRAN FDD. This test will partly verify the RRC
connection release with redirection to UTRAN FDD requirements in clause 6.3.2.1.
The test parameters are given in table A.6.3.12.1-1, table A.6.3.12.1-2, and table A.6.3.12.1-3. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have
any timing information of cell 2. The “RRCConnectionRelease” message not containing any system information of Cell
2 shall be sent to the UE during period T1. The start of T2 is the instant when the last TTI containing the RRC message,
“RRCConnectionRelease”, is received by the UE from Cell 1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 867 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.12.1-1: General test parameters for E-UTRAN TDD RRC connection release redirection to
UTRAN FDD without SI provided
Parameter Unit Value Comment
PDSCH parameters (E-UTRAN DL Reference Measurement As specified in clause A.3.1.1.2.
TDD) Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2.
parameters (E-UTRAN TDD) Channel R.6 TDD
Active cell Cell 1 Cell 1 is on E-UTRAN RF channel
number 1.
Neighbour cell Cell 2 Cell 2 is on UTRAN RF channel number
1.
E-UTRAN RF Channel Number 1 One E-UTRAN TDD carrier frequency is
used.
E-UTRAN Channel Bandwidth MHz 10
(BW channel)
Uplink-downlink configuration of 1 As specified in table 4.2.2 in TS 36.211
cell 1
Special subframe configuration of 6 As specified in table 4.2.1 in TS 36.211
cell 1
CP length Normal Applicable to cell 1
UTRAN RF Channel Number 1 One UTRAN TDD carrier frequency is
used.
Filter coefficient 0 L3 filtering is not used.
DRX OFF
Monitored UTRAN FDD cell list None No explicit neighbour list is provided to
size the UE
T1 s ≤5
T2 s 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 868 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.6.3.12.1-2: Cell specific test parameters for cell 1 in E-UTRAN TDD RRC connection release
redirection to UTRAN FDD test without SI provided
Parameter Unit Cell 1
T1 T2
E-UTRAN RF Channel 1
Number
BW channel MHz 10
OCNG Pattern defined in
OP.1 TDD
A.3.2.2.1 (OP.1 TDD)
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
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 4
Ê s I ot
N oc Note 3 dBm/15 kHz -98
dB 4 4
Ê s N oc
RSRP Note 4 dBm/15 kHz -94 -94
SCH_RP dBm/15 kHz -94 -94
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.6.3.12.1-3: Cell specific test parameters for cell 2 in E-UTRAN TDD RRC connection release
redirection to UTRAN FDD test without SI provided
Parameter Unit Cell 2
T1 T1
UTRAN RF Channel Number 1
CPICH_Ec/Ior dB -10
PCCPCH_Ec/Ior dB -12
SCH_Ec/Ior dB -12
PICH_Ec/Ior dB -15
DPCH_Ec/Ior dB N/A
OCNS -0.941
Iˆor I oc dB -∞ 0.02
I oc dBm/3.84
-70
MHz
CPICH_Ec/IoNote 3 dB -∞ -13
Propagation Condition AWGN
Note 1: The DPCH level is controlled by the power control loop.
Note 2: The power of the OCNS channel that is added shall make the total power from the cell to be equal
to Ior.
Note 3: This gives an SCH Ec/Io of -15dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 869 ETSI TS 136 133 V14.3.0 (2017-04)
A.6.3.12.2 Test Requirements
The UE shall start to send random access to the target UTRAN FDD cell (Cell 2) less than 1930 ms from the beginning
of time period T2.
The rate of correct RRC connection release redirection to UTRAN FDD observed during repeated tests shall be at least
90%.
NOTE: The time delay can be expressed as: TRRC_procedure_delay + Tidentify-UTRAN FDD + TSI-UTRAN FDD + TRA, where:
TRRC_procedure_delay = 110 ms, which is specified in clause 6.3.2.1.
Tidentify-UTRAN FDD = 500 ms; which is defined in clause 6.3.2.1.
TSI-UTRAN FDD: Maximum repetition period of relevant system info blocks that need to be received by the UE during
RRC connection release redirection to UTRAN FDD cell. 1280 ms is assumed in this test case.
TRA = 40ms, this is the additional delay caused by the random access procedure.
This gives a total delay of 1930 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 870 ETSI TS 136 133 V14.3.0 (2017-04)
A.7 Timing and Signalling Characteristics
A.7.1 UE Transmit Timing
A.7.1.1 E-UTRAN FDD – UE Transmit Timing Accuracy Tests
A.7.1.1.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected
eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment,
minimum and maximum adjustment rate are within the specified limits. This test will verify the requirements in
clause 7.1.2.
For this test a single cell is used. Table A.7.1.1.1-1 defines the strength of the transmitted signals and the propagation
condition. The transmit timing is verified by the UE transmitting SRS using the configuration defined in Table
A.7.1.1.1-2.
Table A.7.1.1.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN FDD
Value
Parameter Unit
Test 1 Test 2 Test 3 Test 4
E-UTRA RF Channel Number 1 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 1.4 10
DRX cycle ms N/A 80Note5 N/A 640Note5
PDCCH/PCFICH/PHICH
Reference measurement R.6 FDD R.6 FDD R.8 FDD R.6 FDD
channelNote1
OCNG PatternNote2 OP.2 FDD OP.2 FDD OP.4 FDD OP.2 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0 0 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote3
OCNG_RBNote3
dBm/15
N oc kHz
-98 -98 -98 -98
Ê s I ot dB 3 3 3 3
Ês N oc dB 3 3 3 3
dBm/9
-65.5 -65.5 N/A -65.5
MHz
IoNote4
dBm/1.08
N/A N/A -74.7 N/A
MHz
Propagation condition - AWGN AWGN AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 5: DRX related parameters are defined in Table A.7.1.1.1-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 871 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.1.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for E-UTRAN FDD
Value
Field Comment
Test 1 Test 2 Test 3 Test 4
srsBandwidthConfiguration bw5 bw5 bw7 bw5
srsSubframeConfiguration sc1 sc3 sc1 sc3
ackNackSrsSimultaneousTransmission FALSE FALSE FALSE FALSE
Not applicable for
srsMaxUpPTS N/A N/A N/A N/A
FDD
srsBandwidth 0 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0 0
duration TRUE TRUE TRUE TRUE Indefinite duration
SRS periodicity of
2ms, 80 ms and
Srs-ConfigurationIndex 0 77 0 317 320ms for Test 1,
2 and 4,
respectively.
transmissionComb 0 0 0 0
cyclicShift cs0 cs0 cs0 cs0 No cyclic shift
SRS-AntennaPort an1 Number of
antenna ports
used for SRS
transmission
Note: For further information see clause 6.3.2 in TS 36.331.
Table A.7.1.1.1-3: drx-Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 4 for
E-UTRAN FDD
Value Comment
Field
Test 2 Test 4
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 sf640
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.1.2 Test Requirements
For parameters specified in Tables A.7.1.1.1-1 and A.7.1.1.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 4, respectively):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
NTA×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 4) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within NTA×TS ± 12×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for Test 2 and Test 4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 872 ETSI TS 136 133 V14.3.0 (2017-04)
d) The test system shall verify that the UE transmit timing offset stays within NTA×TS ± 12×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 4 the UE transmit
timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
For the 1.4MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for non-DRX (Test
3):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
NTA×TS ± 24×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +128×TS (approximately +4µs) compared to
that in (a).
c) The test system shall verify that the adjustment step size and the adjustment rate shall be according to the
requirements in clause 7.1.2 until the UE transmit timing offset is within NTA×TS ± 24×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1.
d) The test system shall verify that the UE transmit timing offset stays within NTA×TS ± 24×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1.
A.7.1.2 E-UTRAN TDD - UE Transmit Timing Accuracy Tests
A.7.1.2.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected
eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment,
minimum and maximum adjustment rate are within the specified limits. This test will verify the requirements in
clause 7.1.2.
For this test a single cell is used. Table A.7.1.2.1-1 defines the strength of the transmitted signals and the propagation
condition. The transmit timing is verified by the UE transmitting SRS using the configuration defined in Table
A.7.1.2.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 873 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.2.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN TDD
Value
Parameter Unit
Test 1 Test 2 Test 3 Test 4
E-UTRA RF Channel Number 1 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 1.4 10
Special subframe 6 6 6 6
configurationNote1
Uplink-downlink configurationNote2 1 1 1 1
DRX cycle ms N/A 80Note7 N/A 640Note7
PDCCH/PCFICH/PHICH
Reference measurement R.6 TDD R.6 TDD R.8 TDD R.6 TDD
channelNote3
OCNG PatternNote4 OP.2 TDD OP.2 TDD OP.4 TDD OP.2 TDD
PBCH_RA dB 0 0 0 0
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
0 0 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote5
OCNG_RBNote5
dBm/15
N oc kHz
-98 -98 -98 -98
Ê s I ot dB 3 3 3 3
Ês N oc dB 3 3 3 3
dBm/9
-65.5 -65.5 N/A -65.5
MHz
IoNote6
dBm/1.
N/A N/A -74.7 N/A
08 MHz
Propagation condition - AWGN AWGN AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: For the reference measurement channels, see clause A.3.1.
Note 4: For the OCNG pattern, see clause A.3.2.
Note 5: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 6: Io level has been derived from other parameters for information purpose. It is not a
settable parameter.
Note 7: DRX related parameters are defined in Table A.7.1.2.1-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 874 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.2.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for E-UTRAN TDD
Value
Field Comment
Test 1 Test 2 Test 3 Test 4
srsBandwidthConfiguration bw5 bw5 bw7 bw5
srsSubframeConfiguration sc3 sc3 sc3 sc3 Once every 5 subframes
ackNackSrsSimultaneousTr
FALSE FALSE FALSE FALSE
ansmission
srsMaxUpPTS FALSE FALSE FALSE FALSE
srsBandwidth 0 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0 0
duration TRUE TRUE TRUE TRUE Indefinite duration
SRS periodicity of 10, 80,
Srs-ConfigurationIndex 15 85 15 325 10 and 320 ms for Test 1,
2, 3 and 4 respectively.
transmissionComb 0 0 0 0
cyclicShift cs0 cs0 cs0 cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports
used for SRS
transmission
Note: For further information see clause 6.3.2 in TS 36.331.
Table A.7.1.2.1-3: DRX Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 4
for E-UTRAN TDD
Value Comment
Field
Test 2 Test 4
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 Sf640
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.2.2 Test Requirements
For parameters specified in Tables A.7.1.2.1-1 and A.7.1.2.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 4, respectively):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
(NTA + 624)×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of
cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 4) compared to that in (a).
c) The test system shall verify that for test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within (NTA + 624)×TS ± 12×TS with
respect to the first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for test 2
and test 4.
d) The test system shall verify that the UE transmit timing offset stays within (NTA + 624)×TS ± 12×TS with respect
to the first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 4 the UE
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 875 ETSI TS 136 133 V14.3.0 (2017-04)
transmit timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
For the 1.4MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for non-DRX (Test
3):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
(NTA +624)×TS ± 24×TS with respect to the first detected path (in time) of the corresponding downlink frame of
cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +128×TS (approximately +4µs) compared to
that in (a).
c) The test system shall verify that the adjustment step size and the adjustment rate shall be according to the
requirements in clause 7.1.2 until the UE transmit timing offset is within (NTA +624)×TS ± 24×TS with respect to
the first detected path (in time) of the corresponding downlink frame of cell 1.
d) The test system shall verify that the UE transmit timing offset stays within (NTA +624)×TS ± 24×TS with respect
to the first detected path (in time) of the corresponding downlink frame of cell 1.
A.7.1.3 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for SCell
A.7.1.3.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected
eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment,
minimum and maximum adjustment rate are within the specified limits. This test will verify the requirements in
clause 7.1.2.
For this test two cells are used. Cell 1 is PCell and Cell 2 is SCell. Both PCell and SCell are in the primary Timing
Advance Group (pTAG). Table A.7.1.3.1-1 defines the strength of the transmitted signals and the propagation
condition. The transmit timing is verified by the UE transmitting SRS using the configuration defined in Table
A.7.1.3.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 876 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.3.1-1: General test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN FDD
Cell 1 Cell 2
Parameter Unit
Test 1 Test 2 Test 3 Test 1 Test 2 Test 3
E-UTRA RF Channel
1 1 1 2 2 2
Number
Channel Bandwidth
MHz 20 20 20 20 20 20
(BW channel)
Active PCell Cell 1 Cell 1 Cell 1
Active SCell Cell 2 Cell 2 Cell 2
TAG configuration pTAG pTAG pTAG pTAG pTAG pTAG
DRX cycle ms N/A 80Note5 640Note5 N/A 80Note5 640Note5
PDCCH/PCFICH/PHICH
Reference measurement R.10 FDD R.10 FDD R.10 FDD R.10 FDD R.10 FDD R.10 FDD
channelNote1
OP.12 OP.12 OP.12 OP.12 OP.12 OP.12
OCNG PatternNote2
FDD FDD FDD FDD FDD FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0 0 0 0 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote3
OCNG_RBNote3
dBm/15
N oc kHz
-98 -98 -98 -98 -98 -98
Ê s I ot dB 3 3 3 3 3 3
Ês N oc dB 3 3 3 3 3 3
dBm/18
IoNote4 -62.5 -62.5 -62.5 -62.5 -62.5 -62.5
MHz
Propagation condition - AWGN AWGN AWGN AWGN AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 5: DRX related parameters are defined in Table A.7.1.3.1-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 877 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.3.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for E-UTRAN FDD
Cell 1 Cell 2
Field Comment
Test 1 Test 2 Test 3 Test 1 Test 2 Test 3
srsBandwidthConfiguratio
bw5 bw5 bw5 bw5 bw5 bw5
n
srsSubframeConfiguration sc1 sc3 sc3 sc1 sc3 sc3
ackNackSrsSimultaneous
FALSE FALSE FALSE FALSE FALSE FALSE
Transmission
Not applicable for
srsMaxUpPTS N/A N/A N/A N/A N/A N/A
FDD
srsBandwidth 0 0 0 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0 hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0 0 0 0
duration TRUE TRUE TRUE TRUE TRUE TRUE Indefinite duration
SRS periodicity of
2ms, 80 ms and
Srs-ConfigurationIndex 0 77 317 0 77 317 320ms for Test 1,
2 and 3,
respectively.
transmissionComb 0 0 0 0 0 0
cyclicShift cs0 cs0 cs0 cs0 cs0 cs0 No cyclic shift
Number of SRS
srsAntennaPort an1 an1 an1 an1 an1 an1
antenna ports
NOTE: For further information see clause 6.3.2 in TS 36.331.
Table A.7.1.3.1-3: drx-Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3 for
E-UTRAN FDD
Field Test 2 Test 3 Comment
Cell 1 Cell 2 Cell 1 Cell 2
onDurationTimer psf1 psf1 psf1 psf1
drx-InactivityTimer psf1 psf1 psf1 psf1
drx-RetransmissionTimer psf1 psf1 psf1 psf1
longDRX-CycleStartOffset sf80 sf80 Sf640 Sf640
shortDRX disable disable disable Disable
NOTE: For further information see clause 6.3.2 in TS 36.331.
A.7.1.3.2 Test Requirements
For parameters specified in Tables A.7.1.3.1-1, and A.7.1.3.1-2 the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
The test sequence shall be carried out in RRC_CONNECTED for both non-DRX (for Test 1) and DRX with a cycle
length of 80 ms or a cycle length of 640 mss(Test 2 and 3, respectively):
a) After the SCell (Cell 2) is activated, the test system shall verify that the UE transmit timing offsets of both PCell
and SCell are within NTA×TS ± 12×TS with respect to the first detected path (in time) of the corresponding
downlink frame of PCell (Cell 1).
b) The test system adjusts the downlink transmit timing for the PCell (Cell 1) by +64×TS (for Test 1 and Test 2) or
+32×TS (for Test 3) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offsets of both PCell and SCell are within NTA×TS
± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of PCell (Cell 1).
Skip this step for Test 2 and Test 3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 878 ETSI TS 136 133 V14.3.0 (2017-04)
d) The test system shall verify that the UE transmit timing offsets of both PCell and SCell stay within NTA×TS ±
12×TS with respect to the first detected path (in time) of the corresponding downlink frame of PCell (Cell 1). For
test 2 and test 3 the UE transmit timing offset shall be verified for the first transmission in the DRX cycle
immediately after DL timing adjustment.
A.7.1.4 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell
A.7.1.4.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected
eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment,
minimum and maximum adjustment rate are within the specified limits. This test will verify the requirements in
clause 7.1.2.
For this test two cells are used. Cell 1 is PCell and Cell 2 is SCell. Both PCell and SCell are in the primary Timing
Advance Group (pTAG). Table A.7.1.4.1-1 defines the strength of the transmitted signals and the propagation
condition. The transmit timing is verified by the UE transmitting SRS using the configuration defined in Table
A.7.1.4.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 879 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.4.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN TDD
Cell 1 Cell 2
Parameter Unit
Test 1 Test 2 Test 3 Test 1 Test 2 Test 3
E-UTRA RF Channel Number 1 1 1 2 2 2
Channel Bandwidth (BW channel) MHz 20 20 20 20 20 20
E-UTRA RF Channel Number 1 1 1 2 2 2
Active PCell Cell 1 Cell 1 Cell 1
Active SCell Cell 2 Cell 2 Cell 2
TAG configuration pTAG pTAG pTAG pTAG pTAG pTAG
Special subframe 6 6 6 6 6 6
configurationNote1
Uplink-downlink configurationNote2 1 1 1 1 1 1
DRX cycle ms OFF 80Note7 640Note7 OFF 80Note7 640Note7
PDCCH/PCFICH/PHICH
R.10 R.10 R.10 R.10 R.10 R.10
Reference measurement
TDD TDD TDD TDD TDD TDD
channelNote3
OP.8 OP.8 OP.8 OP.8 OP.8 OP.8
OCNG PatternNote4
TDD TDD TDD TDD TDD TDD
PBCH_RA dB 0 0 0 0 0 0
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
0 0 0 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote5
OCNG_RBNote5
dBm/15
N oc kHz
-98 -98 -98 -98 -98 -98
Ê s I ot dB 3 3 3 3 3 3
Ês N oc dB 3 3 3 3 3 3
dBm/18
IoNote6 -62.5 -62.5 -62.5 -62.5 -62.5 -62.5
MHz
Propagation condition - AWGN AWGN AWGN AWGN AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: For the reference measurement channels, see clause A.3.1.
Note 4: For the OCNG pattern, see clause A.3.2.
Note 5: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 6: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 7: DRX related parameters are defined in Table A.7.1.4.1-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 880 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.4.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for E-UTRAN TDD
Comment
Cell 1 Cell 2
Field
Test 1 Test
Test1 1 Test 2 Test 3 Test 1 Test 2 Test 3 Tset3 Tset3
srsBandwidthConfiguration bw5 bw5 bw5 bw5 bw5 bw5
Once every 5
srsSubframeConfiguration sc3 sc3 sc3 sc3 sc3 sc3
subframes
ackNackSrsSimultaneous
FALSE FALSE FALSE FALSE FALSE FALSE
Transmission
srsMaxUpPTS FALSE FALSE FALSE FALSE FALSE FALSE
srsBandwidth 0 0 0 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0 hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0 0 0 0
Indefinite
duration TRUE TRUE TRUE TRUE TRUE TRUE
duration
SRS periodicity
of 10, 80 ms
Srs-ConfigurationIndex 15 85 325 15 85 325 and 320ms for
Test 1, 2 and 3,
respectively.
transmissionComb 0 0 0 0 0 0
cyclicShift cs0 cs0 cs0 cs0 cs0 cs0 No cyclic shift
Number of SRS
srsAntennaPort an1 an1 an1 an1 an1 an1
antenna ports
Note: For further information see clause 6.3.2 in TS 36.331.
Table A.7.1.4.1-3: DRX Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3
for E-UTRAN TDD
Test 2 Test 3 Comment
Field
Cell 1 Cell 2 Cell 1 Cell 2
onDurationTimer psf1 psf1 psf1 psf1
drx-InactivityTimer psf1 psf1 psf1 psf1
drx-RetransmissionTimer psf1 psf1 psf1 psf1
longDRX-CycleStartOffset sf80 sf80 Sf640 Sf640
shortDRX disable disable disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.4.2 Test Requirements
For parameters specified in Tables A.7.1.4.1-1 and A.7.1.4.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
The test sequence shall be carried out in RRC_CONNECTED for both non-DRX (for Test 1) and DRX with a cycle
length of 80 ms or a cycle length of 640 ms (Test 2 and 3, respectively):
a) After the SCell (Cell 2) is activated, the test system shall verify that the UE transmit timing offsets of both PCell
and SCell are within (NTA + 624)×TS ± 12×TS with respect to the first detected path (in time) of the
corresponding downlink frame of PCell (Cell 1).
b) The test system adjusts the downlink transmit timing for the PCell (Cell 1) by +64×TS (for Test 1 and Test 2) or
+32×TS (for Test 3) compared to that in (a).
c) The test system shall verify that for test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offsets of both PCell and SCell are within (NTA +
624)×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of PCell
(Cell 1). Skip this step for test 2 and test 3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 881 ETSI TS 136 133 V14.3.0 (2017-04)
d) The test system shall verify that the UE transmit timing offsets of both PCell and SCell stay within (NTA +
624)×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of PCell
(Cell 1). For test 2 and test 3 the UE transmit timing offset shall be verified for the first transmission in the DRX
cycle immediately after DL timing adjustment.
A.7.1.4A E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell for
20 MHz + 10 MHz
A.7.1.4A.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.1.4.1.
The parameters of this test are the same as defined in Subclause A.7.1.4.1 except that the values of the parameters in the
Table A.7.1.4A.1-1 will replace the values of the corresponding parameters in A.7.1.4.1-1. Parameters used for the
sounding reference symbol configuration and DRX configuration are unchanged from table A.7.1.4.1-2 and table
A.7.1.4.1-3.
Table A.7.1.4A.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN TDD for 20
MHz +10 MHz
Cell 1 Cell 2
Parameter Unit
Test 1 Test 2 Test 3 Test 1 Test 2 Test 3
Channel Bandwidth (BW channel) MHz 20 20 20 10 10 10
PDCCH/PCFICH/PHICH
R.10 R.10 R.10 R.6
Reference measurement R.6 TDD R.6 TDD
TDD TDD TDD TDD
channelNote3
OP.8 OP.8 OP.8 OP.2 OP.2 OP.2
OCNG PatternNote4
TDD TDD TDD TDD TDD TDD
dBm/18
-62.5 -62.5 -62.5 N/A N/A N/A
MHz
IoNote6
dBm/9
N/A N/A N/A -65.5 -65.5 -65.5
MHz
A.7.1.4A.2 Test Requirements
The test requirements defined in section A.7.1.4.2 shall apply to this test case.
A.7.1.5 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for 5MHz
Bandwidth
A.7.1.5.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.1.1.1.
The parameters of this test are the same as defined in Subclause A.7.1.1.1 except that the values of the parameters in
Test 1 in the Table A.7.1.5.1-1 will replace the values of the corresponding parameters in A.7.1.1.1-1. Only Test 1 is
defined for the 5MHz bandwidth.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 882 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.5.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN FDD for
5MHz bandwidth
Value
Parameter Unit
Test 1
Channel Bandwidth (BW channel) MHz 5
PDCCH/PCFICH/PHICH
Reference measurement R.11 FDD
channelNote1
OCNG PatternNote2 OP.16 FDD
dBm/4.5
IoNote4 -68.5
MHz
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: See Table A.7.1.1.1-1 for the other parameters.
Note 4: This test is according to the principle defined in section A.3.7.2.
A.7.1.5.2 Test Requirements
The test requirements defined in section A.7.1.1.2 shall apply to this test case.
A.7.1.6 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for SCell in
sTAG
A.7.1.6.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected eNode
B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment, minimum
and maximum adjustment rate are within the specified limits for SCell in sTAG. This test will verify the requirements
in clause 7.1.2.
For this test two cells are used. Cell 1 is PCell and Cell 2 is SCell. PCell is in the Primary Timing Advance Group
(pTAG) and Scell is in the secondary Timing Advance Group (sTAG). Table A.7.1.6.1-1 defines the strength of the
transmitted signals and the propagation condition. The transmit timing for Scell in sTAG is verified by the UE
transmitting SRS using the configuration defined in Table A.7.1.6.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 883 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.6.1-1: General test Parameters for UE Transmit Timing Accuracy Tests for Scell in sTAG
for E-UTRAN FDD
Cell 1 Cell 2
Parameter Unit
Test 1 Test 2 Test 1 Test 2
E-UTRA RF Channel
1 1 2 2
Number
Channel Bandwidth
MHz 10 10 10 10
(BW channel)
Active PCell Cell 1 Cell 1
Active SCell Cell 2 Cell 2
TAG configuration pTAG pTAG sTAG sTAG
DRX cycle ms OFF 80Note5 OFF 80Note5
PDCCH/PCFICH/PHICH
Reference measurement R.6 FDD R.6 FDD R.6 FDD R.6 FDD
channelNote1
OCNG PatternNote2 OP.2 FDD OP.2 FDD OP.2 FDD OP.2 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0 0 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote3
OCNG_RBNote3
dBm/15
N oc kHz
-98 -98 -98 -98
Ê s I ot dB 3 3 3 3
Ês N oc dB 3 3 3 3
dBm/9
IoNote4 -65.5 -65.5 -65.5 -65.5
MHz
Propagation condition - AWGN AWGN AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 5: DRX related parameters are defined in Table A.7.1.6.1-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 884 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.6.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for Scell in sTAG for E-UTRAN FDD
Cell 1 Cell 2 Comment
Field
Test 1 Test 2 Test 1 Test 2
srsBandwidthConfiguratio
bw5 bw5 bw5 bw5
n
Once every 5
srsSubframeConfiguration sc3 sc3 sc3 sc3
subframes
ackNackSrsSimultaneous
FALSE FALSE FALSE FALSE
Transmission
srsMaxUpPTS FALSE FALSE FALSE FALSE
srsBandwidth 0 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0 0
duration TRUE TRUE TRUE TRUE Indefinite duration
SRS periodicity of
10 and 80 ms for
Srs-ConfigurationIndex 15 85 15 85
Test 1 and 2,
respectively.
transmissionComb 0 0 0 0
cyclicShift cs0 cs0 cs0 cs0 No cyclic shift
Number of SRS
srsAntennaPort an1 an1 an1 an1
antenna ports
Note: For further information see clause 6.3.2 in TS 36.331.
Table A.7.1.6.1-3: drx-Configuration to be used in Test 2 of UE Transmit Timing Accuracy for SCell in
sTAG for E-UTRAN FDD
Field Cell 1 Cell 2 Comment
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 sf80
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.6.2 Test Requirements
For parameters specified in Tables A.7.1.6.1-1, and A.7.1.6.1-2 the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate for Scell in sTAG shall be
within the limits defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For Test1 and Test2, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX and DRX with a
cycle length of 80 ms:
a) After the SCell (Cell 2) is activated, the test system shall verify that the UE transmit timing offsets for SCell in
sTAG are within NTA×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink
frame of the activated Scell.
b) The test system adjusts the downlink transmit timing for the activated Scell (Cell 2) by +64×TS (approximately
+2µs) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate for Scell in sTAG
shall be according to the requirements in clause 7.1.2 until the UE transmit timing offsets of SCell within
NTA×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of the
activated SCell (Cell 2). Skip this step for Test 2.
d) The test system shall verify that the UE transmit timing offsets of the SCell in sTAG stay within NTA×TS ±
12×TS with respect to the first detected path (in time) of the corresponding downlink frame of the activated
SCell (Cell 2).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 885 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.1.7 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell in
sTAG
A.7.1.7.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected eNode
B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment, minimum
and maximum adjustment rate are within the specified limits for SCell in sTAG. This test will verify the requirements
in clause 7.1.2.
For this test two cells are used. Cell 1 is PCell and Cell 2 is SCell. PCell is in the Primary Timing Advance Group
(pTAG) and Scell is in the secondary Timing Advance Group (sTAG). Table A.7.1.7.1-1 defines the strength of the
transmitted signals and the propagation condition. The transmit timing for Scell in sTAG is verified by the UE
transmitting SRS using the configuration defined in Table A.7.1.7.1-2.
Table A.7.1.7.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for Scell in sTAG for E-
UTRAN TDD
Unit Cell 1 Cell 2
Parameter
Test 1 Test 2 Test 1 Test 2
E-UTRA RF Channel Number 1 1 2 2
Channel Bandwidth (BW channel) MHz 10 10 10 10
E-UTRA RF Channel Number 1 1 2 2
Active PCell Cell 1 Cell 1
Active SCell Cell 2 Cell 2
TAG configuration pTAG pTAG sTAG sTAG
Special subframe 6 6 6 6
configurationNote1
Uplink-downlink configurationNote2 1 1 1 1
DRX cycle ms OFF 80Note7 OFF 80Note7
PDCCH/PCFICH/PHICH
Reference measurement R.6 TDD R.6 TDD R.6 TDD R.6 TDD
channelNote3
OCNG PatternNote4 OP.2 TDD OP.2 TDD OP.2 TDD OP.2 TDD
PBCH_RA dB 0 0 0 0
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
0 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote5
OCNG_RBNote5
dBm/15
N oc kHz
-98 -98 -98 -98
Ê s I ot dB 3 3 3 3
Ês N oc dB 3 3 3 3
dBm/9
IoNote6 --65.5 --65.5 --65.5 --65.5
MHz
Propagation condition - AWGN AWGN AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: For the reference measurement channels, see clause A.3.1.
Note 4: For the OCNG pattern, see clause A.3.2.
Note 5: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 6: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 7: DRX related parameters are defined in Table A.7.1.7.1-3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 886 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.7.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for Scell in sTAG for E-UTRAN TDD
Comment
Cell 1 Cell 2
Field
Test 1 Test 2 Test 1 Test 2
srsBandwidthConfiguratio
bw5 bw5 bw5 bw5
n
Once every 5
srsSubframeConfiguration sc3 sc3 sc3 sc3
subframes
ackNackSrsSimultaneous
FALSE FALSE FALSE FALSE
Transmission
srsMaxUpPTS FALSE FALSE FALSE FALSE
srsBandwidth 0 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0 0
duration TRUE TRUE TRUE TRUE Indefinite duration
SRS periodicity of
10 and 80 ms for
Srs-ConfigurationIndex 15 85 15 85
Test 1 and 2,
respectively.
transmissionComb 0 0 0 0
cyclicShift cs0 cs0 cs0 cs0 No cyclic shift
Number of SRS
srsAntennaPort an1 an1 an1 an1
antenna ports
Note: For further information see clause 6.3.2 in TS 36.331.
Table A.7.1.7.1-3: DRX Configuration to be used in Test 2 of UE Transmit Timing Accuracy for SCell
in sTAG for E-UTRAN TDD
Field Cell 1 Cell 2 Comment
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 sf80
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.7.2 Test Requirements
For parameters specified in Tables A.7.1.7.1-1 and A.7.1.7.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate for Scell in sTAG shall be
within the limits defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For Test 1 and Test 2, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX and DRX with a
cycle length of 80 ms:
a) After the SCell (Cell 2) is activated, the test system shall verify that the UE transmit timing offsets for Scell in
sTAG are within (NTA + 624)×TS ± 12×TS with respect to the first detected path (in time) of the corresponding
downlink frame of the activated SCell (Cell 2).
b) The test system adjusts the downlink transmit timing for the activated Scell (Cell 2) by +64×TS (approximately
+2µs) compared to that in (a).
c) The test system shall verify that for test 1 the adjustment step size and the adjustment rate for Scell in sTAG
shall be according to the requirements in clause 7.1.2 until the UE transmit timing offsets of SCell are within
(NTA + 624)×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of
the activated SCell(Cell 2). Skip this step for test 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 887 ETSI TS 136 133 V14.3.0 (2017-04)
d) The test system shall verify that the UE transmit timing offsets of the SCell in sTAG stay within (NTA + 624)×TS
± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of the activated
Scell (Cell 2).
A.7.1.7A E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell in
sTAG for 20MHz +20MHz
A.7.1.7A.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.1.7. The test parameters are the same
except those described in the following section. The listed parameter values in Tables A.7.1.7B.1.1-1 will replace the
values of corresponding parameters in Tables A.7.1.7.1-1.
Table A.7.1.7A.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for Scell in sTAG for E-
UTRAN TDD with 20MHz +20MHz bandwidth
Cell 1 Cell 2
Parameter Unit
Test 1 Test 2 Test 1 Test 2
E-UTRA RF Channel Number 1 1 2 2
Channel Bandwidth (BW channel) MHz 20 20 20 20
PDCCH/PCFICH/PHICH
Reference measurement channel R.10 TDD R.10 TDD R.10 TDD R.10 TDD
defined in A.3.1.2.2
OCNG Pattern defined in A.3.2.2 OP.8 TDD OP.8 TDD OP.8 TDD OP.8 TDD
dBm/18
IoNote1 -62.5 -62.5 -62.5 -62.5
MHz
Note 1: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
A.7.1.7A.2 Test Requirements
The test requirements defined in section A.7.1.7.2 shall apply to these test cases.
A.7.1.7B E-UTRAN TDD - UE Transmit Timing Accuracy Tests for SCell in
sTAG for 20MHz +10MHz
A.7.1.7B.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.1.7. The test parameters are the same
except those described in the following section. The listed parameter values in Tables A.7.1.7B.1-1 will replace the
values of corresponding parameters in Tables A.7.1.7.1-1.
Table A.7.1.7B.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for Scell in sTAG for E-
UTRAN TDD with 20MHz +10MHz bandwidth
Cell 1 Cell 2
Parameter Unit
Test 1 Test 2 Test 1 Test 2
E-UTRA RF Channel Number 1 1 2 2
Channel Bandwidth (BW channel) MHz 20 20 10 10
PDCCH/PCFICH/PHICH
Reference measurement channel R.10 TDD R.10 TDD R.6 TDD R.6 TDD
defined in A.3.1.2.2
OCNG Pattern defined in A.3.2.2 OP.8 TDD OP.8 TDD OP.2 TDD OP.2 TDD
dBm/18
-62.5 -62.5 - -
MHz
IoNote1
dBm/9
- - -65.5 -65.5
MHz
Note 1: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 888 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.1.7B.2 Test Requirements
The test requirements defined in section A.7.1.7.2 shall apply to these test cases.
A.7.1.8 Void
A.7.1.8.1 Void
Table A.7.1.8.1-1: Void
A.7.1.8.2 Void
A.7.1.9 Void
A.7.1.9.1 Void
Table A.7.1.9.1-1: Void
A.7.1.9.2 Void
A.7.1.10 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for Cat-M1
UE in CEModeA
A.7.1.10.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE in CEModeA is capable of following the frame timing change
of the connected eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one
adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify the
requirements in clause 7.1.2.
For this test a single cell is used. Table A.7.1.10.1-1 defines the strength of the transmitted signals and the propagation
condition. The transmit timing is verified by the UE transmitting SRS using the configuration defined in Table
A.7.1.10.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 889 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.10.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN FDD Cat-M1
UE under CEModeA
Value
Parameter Unit
Test 1 Test 2 Test 3
E-UTRA RF Channel Number 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 10
DRX cycle ms N/A 80Note5 640Note5
PRACH Configuration PRACH_4CE As specified in A.3.16
MPCCH Reference measurement channelNote1 R.16 FDD R.16 FDD R.16 FDD
OCNG PatternNote2 OP.21 FDD OP.21 FDD OP.21 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PHICH_RA
dB 0 0 0
PHICH_RB
MPDCCH_RA
MPDCCH_RB
OCNG_RANote3
OCNG_RBNote3
N oc dBm/15 kHz -98 -98 -98
Ê s I ot dB 3 3 3
Ês N oc dB 3 3 3
dBm/9 MHz -65.5 -65.5 -65.5
IoNote4
dBm/1.08 MHz N/A N/A N/A
Propagation condition - AWGN AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 5: DRX related parameters are defined in Table A.7.1.10.1-3.
Table A.7.1.10.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for E-UTRAN FDD Cat-M1 UE under CEModeA
Value Comment
Field
Test 1 Test 2 Test 3
srsBandwidthConfiguration bw5 bw5 bw5
srsSubframeConfiguration sc1 sc3 sc3
ackNackSrsSimultaneousTransmission FALSE FALSE FALSE
srsMaxUpPTS N/A N/A N/A Not applicable for FDD
srsBandwidth 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0
duration TRUE TRUE TRUE Indefinite duration
SRS periodicity of 2ms, 80 ms and 320ms for
Srs-ConfigurationIndex 0 77 317
Test 1, 2 and 4, respectively.
transmissionComb 0 0 0
cyclicShift cs0 cs0 cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note 1: For further information see clause 6.3.2 in TS 36.331.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 890 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.10.1-3: drx-Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3
for E-UTRAN FDD Cat-M1 UE under CEModeA
Value Comment
Field
Test 2 Test 3
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 sf640
shortDRX disable disable
Note 1: For further information see clause 6.3.2 in TS 36.331.
A.7.1.10.2 Test Requirements
For parameters specified in Tables A.7.1.10.1-1 and A.7.1.10.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 4, respectively):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
NTA×TS ± 24×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 3) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within NTA×TS ± 24×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for Test 2 and Test 3.
d) The test system shall verify that the UE transmit timing offset stays within NTA×TS ± 24×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 3 the UE transmit
timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
A.7.1.11 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for Cat-
M1 UE in CEModeA
A.7.1.11.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE in CEModeA is capable of following the frame timing change
of the connected eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one
adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify the
requirements in clause 7.1.2.
For this test a single cell is used. Table A.7.1.11.1-1 defines the strength of the transmitted signals and the propagation
condition. The transmit timing is verified by the UE transmitting SRS using the configuration defined in Table
A.7.1.11.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 891 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.11.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN HD-FDD
Cat-M1 UE under CEModeA
Value
Parameter Unit
Test 1 Test 2 Test 3
E-UTRA RF Channel Number 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 10
DRX cycle ms N/A 80Note5 640Note5
PRACH configuration PRACH_4CE As specified in A.3.16
MPCCH Reference measurement channelNote1 R.6 HD-FDD R.6 HD-FDD R. 6 HD-FDD
OCNG PatternNote2 OP.21 FDD OP.21 FDD OP.21 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PHICH_RA
dB 0 0 0
PHICH_RB
MPDCCH_RA
MPDCCH_RB
OCNG_RANote3
OCNG_RBNote3
N oc dBm/15 kHz -98 -98 -98
Ê s I ot dB 3 3 3
Ês N oc dB 3 3 3
dBm/9 MHz -65.5 -65.5 -65.5
IoNote4
dBm/1.08 MHz N/A N/A N/A
Propagation condition - AWGN AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 5: DRX related parameters are defined in Table A.7.1.11.1-3.
Table A.7.1.11.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for E-UTRAN HD-FDD Cat-M1 UE under CEModeA
Value Comment
Field
Test 1 Test 2 Test 3
srsBandwidthConfiguration bw5 bw5 bw5
srsSubframeConfiguration sc1 sc3 sc3
ackNackSrsSimultaneousTransmission FALSE FALSE FALSE
srsMaxUpPTS N/A N/A N/A Not applicable for FDD
srsBandwidth 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0
duration TRUE TRUE TRUE Indefinite duration
SRS periodicity of 2ms, 80 ms and 320ms for
Srs-ConfigurationIndex 0 77 317
Test 1, 2 and 4, respectively.
transmissionComb 0 0 0
cyclicShift cs0 cs0 cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note 1: For further information see clause 6.3.2 in TS 36.331.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 892 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.11.1-3: drx-Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3
for E-UTRAN HD-FDD Cat-M1 UE under CEModeA
Value Comment
Field
Test 2 Test 3
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 sf640
shortDRX disable disable
Note 1: For further information see clause 6.3.2 in TS 36.331.
A.7.1.11.2 Test Requirements
For parameters specified in Tables A.7.1.11.1-1 and A.7.1.11.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 4, respectively):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
NTA×TS ± 24×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 3) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within NTA×TS ± 24×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for Test 2 and Test 3.
d) The test system shall verify that the UE transmit timing offset stays within NTA×TS ± 24×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 3 the UE transmit
timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
A.7.1.12 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for Cat-M1 UE
in CEModeA
A.7.1.12.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected
eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment,
minimum and maximum adjustment rate are within the specified limits. This test will verify the requirements in
clause 7.1.2.
For this test a single cell is used. Table A.7.1.12.1-1 defines the strength of the transmitted signals and the propagation
condition. The transmit timing is verified by the UE transmitting SRS using the configuration defined in Table
A.7.1.12.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 893 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.12.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN TDD Cat-M1
UE under CEModeA
Value
Parameter Unit
Test 1 Test 2 Test 3
E-UTRA RF Channel Number 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 10
Special subframe configurationNote1 6 6 6
Uplink-downlink configurationNote2 1 1 1
DRX cycle ms N/A 80Note7 640Note7
PRACH configuration PRACH_4CE As specified in A.3.16
MPDCCH Reference measurement channelNote3 R.14 TDD R.14 TDD R.14 TDD
OCNG PatternNote4 OP.11 TDD OP.11 TDD OP.11 TDD
PBCH_RA dB 0 0 0
PBCH_RB
PSS_RA
SSS_RA
PHICH_RA
PHICH_RB 0 0 0
MPDCCH_RA
MPDCCH_RB
OCNG_RANote5
OCNG_RBNote5
N oc dBm/15 kHz -98 -98 -98
Ê s I ot dB 3 3 3
Ês N oc dB 3 3 3
dBm/9 MHz -65.5 -65.5 -65.5
IoNote6
dBm/1.08 MHz N/A N/A N/A
Propagation condition - AWGN AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: For the reference measurement channels, see clause A.3.1.
Note 4: For the OCNG pattern, see clause A.3.2.
Note 5: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 6: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Note 7: DRX related parameters are defined in Table A.7.1.12.1-3.
Table A.7.1.12.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for E-UTRAN TDD Cat-M1 UE under CEModeA
Values Comment
Field
Test 1 Test 2 Test 3
srsBandwidthConfiguration bw5 bw5 Bw5
srsSubframeConfiguration sc3 sc3 sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE FALSE FALSE
srsMaxUpPTS FALSE FALSE FALSE
srsBandwidth 0 0 0 No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0
Duration TRUE TRUE TRUE Indefinite duration
SRS periodicity of 10, 80, 10 and 320 ms for Test
Srs-ConfigurationIndex 15 85 325
1, 2, 3 and 4 respectively.
transmissionComb 0 0 0
cyclicShift cs0 cs0 cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 894 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.12.1-3: DRX Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3
for E-UTRAN TDD Cat-M1 UE under CEModeA
Value Comment
Field
Test 2 Test 3
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 Sf640
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.12.2 Test Requirements
For parameters specified in Tables A.7.1.12.1-1 and A.7.1.12.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 4, respectively):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
(NTA + 624)×TS ± 24×TS with respect to the first detected path (in time) of the corresponding downlink frame of
cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 3) compared to that in (a).
c) The test system shall verify that for test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within (NTA + 624)×TS ± 24×TS with
respect to the first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for test 2
and test 3.
d) The test system shall verify that the UE transmit timing offset stays within (NTA + 624)×TS ± 24×TS with respect
to the first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 3 the UE
transmit timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
A.7.1.13 3DL/3UL TDD CA UE Transmit Timing Accuracy Tests for 2 SCells
A.7.1.13.1 Test Purpose and Environment
The purpose of this test is to verify that the UE is capable of following the frame timing change of the connected eNode
B and that the UE initial transmit timing accuracy, maximum amount of timing change in one adjustment, minimum
and maximum adjustment rate are within the specified limits for SCell in sTAG. This test will verify the requirements
in clause 7.1.2.
For this test three cells are used. Cell 1 is PCell, Cell 2 is SCell1 and Cell 3 is SCell2. PCell is in the Primary Timing
Advance Group (pTAG) and SCell1 and SCell2 are in the secondary Timing Advance Group (sTAG). Table A.7.1.13.1-
1 defines the strength of the transmitted signals and the propagation condition. The transmit timing for SCell1 and
SCell2 in sTAG is verified by the UE transmitting SRS using the configuration defined in Table A.7.1.13.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 895 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.13.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for SCell1 and SCell2 in
sTAG for 3DL/3UL TDD CAE-UTRAN TDD
Unit Cell 1 Cell 2 Cell 3
Parameter
Test 1 Test 2 Test 1 Test 2 Test 1 Test 2
E-UTRA RF Channel
1 1 2 2 3 3
Number
Channel Bandwidth
MHz 5, 10, 20 5, 10, 20 5, 10, 20 5, 10, 20 5, 10, 20 5, 10, 20
(BW channel)
Active PCell Cell 1 Cell 1
Active SCell Cell 2 Cell 2 Cell 3 Cell 3
TAG configuration pTAG pTAG sTAG sTAG sTAG sTAG
Special subframe 6 6 6 6 6 6
configurationNote1
Uplink-downlink 1 1 1 1 1 1
configurationNote2
DRX cycle ms OFF 80Note7 OFF 80Note7 OFF 80Note7
R.11 R.11 R.11 R.11 R.11 R.11
PDCCH/PCFICH/PHICH
TDD , R.6 TDD , R.6 TDD , R.6 TDD , R.6 TDD , R.6 TDD , R.6
Reference measurement
TDD, R.10 TDD, R.10 TDD, R.10 TDD, R.10 TDD, R.10 TDD, R.10
channelNote3
TDD TDD TDD TDD TDD TDD
OP.10 OP.10 OP.10 OP.10 OP.10 OP.10
TDD , TDD , TDD , TDD , TDD , TDD ,
OCNG PatternNote4
OP.2 TDD, OP.2 TDD, OP.2 TDD, OP.2 TDD, OP.2 TDD, OP.2 TDD,
OP.8 TDD OP.8 TDD OP.8 TDD OP.8 TDD OP.8 TDD OP.8 TDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0 0 0 0 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote5
OCNG_RBNote5
dBm/
N oc 15 kHz
-98 -98 -98 -98 -98 -98
Ê s I ot dB 3 3 3 3 3 3
Ês N oc dB 3 3 3 3 3 3
dBm/
-68.5 -68.5 -68.5 -68.5 -68.5 -68.5
4.5 MHz
dBm/
IoNote6 --65.5 --65.5 --65.5 --65.5 --65.5 --65.5
9 MHz
dBm/
-62.4 -62.4 -62.4 -62.4 -62.4 -62.4
18MHz
Timing offset to Cell 1 μs - 0 0
Time alignment error
μs - ≤ TAE ≤ TAE
relative to cell 1 Note 8
Propagation condition - AWGN AWGN AWGN AWGN AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: For the reference measurement channels, see clause A.3.1.
Note 4: For the OCNG pattern, see clause A.3.2.
Note 5: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 6: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 7: DRX related parameters are defined in Table A.7.1.x.1-3.
Note 8: Time alignment error (TAE) as specified in TS 36.104 [30] clause 6.5.3.1. The TAE value depends upon the
type of carrier aggregation.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 896 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.13.1-2: Sounding Reference Symbol Configuration to be used in UE Transmit Timing
Accuracy Tests for SCell1 and SCell2 in sTAG for 3DL/3UL TDD CA
Cell 1 Cell 2 Cell 3 Comment
Field
Test 1 Test 2 Test 1 Test 2 Test 1 Test 2
srsBandwidthConfiguration bw5 bw5 bw5 bw5 bw5 bw5
Once every 5
srsSubframeConfiguration sc3 sc3 sc3 sc3 sc3 sc3
subframes
ackNackSrsSimultaneousT
FALSE FALSE FALSE FALSE FALSE FALSE
ransmission
srsMaxUpPTS FALSE FALSE FALSE FALSE FALSE FALSE
srsBandwidth 0 0 0 0 0 0
No hopping
srsHoppingBandwidth hbw0 hbw0 hbw0 hbw0 hbw0 hbw0
frequencyDomainPosition 0 0 0 0 0 0
duration TRUE TRUE TRUE TRUE TRUE TRUE Indefinite duration
SRS periodicity of 10
Srs-ConfigurationIndex 15 85 15 85 15 85 and 80 ms for Test 1
and 2, respectively.
transmissionComb 0 0 0 0 0 0
cyclicShift cs0 cs0 cs0 cs0 cs0 cs0 No cyclic shift
Number of SRS
srsAntennaPort an1 an1 an1 an1 an1 an1
antenna ports
Note 1: For further information see clause 6.3.2 in TS 36.331.
Table A.7.1.13.1-3: DRX Configuration to be used in Test 2 of UE Transmit Timing Accuracy for
SCell1 and SCell2 in sTAG for 3DL/3UL TDD CA
Field Cell 1 Cell 2 Cell 3 Comment
onDurationTimer psf1 psf1 psf1
drx-InactivityTimer psf1 psf1 psf1
drx-RetransmissionTimer psf1 psf1 psf1
longDRX-CycleStartOffset sf80 sf80 sf80
shortDRX disable disable Disable
Note 1: For further information see clause 6.3.2 in TS 36.331.
A.7.1.13.2 Test Requirements
For parameters specified in Tables A.7.1.13.1-1, 7.1.8.1-2 and A.7.1.13.1-3, the initial transmit timing accuracy, the
maximum amount of timing change in one adjustment, the minimum and the maximum adjustment rate for Scell1 and
SCell2 in sTAG shall be within the limits defined in clause 7.1.2.
The following sequence of events shall be used to verify that the requirements are met.
For Test 1 and Test 2, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX and DRX with a
cycle length of 80 ms:
a) After the SCell1 (Cell 2) and SCell2 (Cell3) are activated, the test system shall verify that the UE transmit timing
offsets for SCell1 and SCell2 in sTAG are within (NTA + 624) ×TS ± 12×TS with respect to the first detected path
(in time) of the corresponding downlink frame of the activated SCell1 (Cell 2) or SCell2 (Cell3).
b) The test system adjusts the downlink transmit timing for the activated SCell1 (Cell 2) and SCell2 (Cell3) by
+64×TS (approximately +2µs) compared to that in (a).
c) The test system shall verify that for test 1 the adjustment step size and the adjustment rate for SCell1 and SCell2
in sTAG shall be according to the requirements in clause 7.1.2 until the UE transmit timing offsets of SCell1 and
SCell2 are within (NTA + 624) ×TS ± 12×TS with respect to the first detected path (in time) of the corresponding
downlink frame of the activated SCell1 (Cell 2) or SCell2 (Cell3). Skip this step for test 2.
d) The test system shall verify that the UE transmit timing offsets of the SCell1 and SCell2 in sTAG stay within
(NTA + 624) ×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of
the activated SCell1 (Cell 2) or SCell2 (Cell3).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 897 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.1.14 E-UTRAN FDD – UE Transmit Timing Accuracy Tests for Cat-M1
UE in CEModeB
A.7.1.14.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE in CEModeB is capable of following the frame timing change
of the connected eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one
adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify the
requirements in clause 7.1.2.
As specified in Clause 7.1.2 the UE adjusts its uplink timing at the end of of repetition period when configured with
repetitions. By measuring the reception of the MPUSCH, the transmit timing accuracy can be measured and the
requirements can be verified. For this test a single cell is used. Table A.7.1.14.1-1 defines the strength of the transmitted
signals and the propagation condition.
Table A.7.1.14.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN FDD Cat-M1
UE under CEModeB
Value
Parameter Unit
Test 1 Test 2 Test 3
E-UTRA RF Channel Number 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 10
DRX cycle ms N/A 80Note5 640Note5
MPCCH Reference measurement channelNote1 R.18 FDD R.18 FDD R.18 FDD
OCNG PatternNote2 OP.21 FDD OP.21 FDD OP.21 FDD
MPDCCH 128
Number of repetitions
MPUSCH 32
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PHICH_RA
dB 0 0 0
PHICH_RB
MPDCCH_RA
MPDCCH_RB
OCNG_RANote3
OCNG_RBNote3
N oc dBm/15 kHz -98 -98 -98
Ê s I ot dB -12 -12 -12
Ês N oc dB -12 -12 -12
dBm/9 MHz -86.4 -86.4 -86.4
IoNote4
dBm/1.08 MHz N/A N/A N/A
Propagation condition - AWGN AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 5: DRX related parameters are defined in Table A.7.1.14.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 898 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.14.1-2: drx-Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3
for E-UTRAN FDD Cat-M1 UE under CEModeB
Value Comment
Field
Test 2 Test 3
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 sf640
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.14.2 Test Requirements
For parameters specified in Tables A.7.1.14.1-1 and A.7.1.14.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2. The UE shall not adjust the the transmission timing autonomously during an ongoing repetition
period. Adjustments can only be done at the end of a last subframe in a repetition period.
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 3, respectively):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
NTA×TS ± 48×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 3) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within NTA×TS ± 48×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for Test 2 and Test 3.
d) The test system shall verify that the UE transmit timing offset stays within NTA×TS ± 48×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 3 the UE transmit
timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
A.7.1.15 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for Cat-
M1 UE in CEModeB
A.7.1.15.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE in CEModeB is capable of following the frame timing change
of the connected eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one
adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify the
requirements in clause 7.1.2.
As specified in Clause 7.1.2 the UE adjusts its uplink timing at the end of of repetition period when configured with
repetitions. By measuring the reception of the MPUSCH, the transmit timing accuracy can be measured and the
requirements can be verified. For this test a single cell is used. Table A.7.1.15.1-1 defines the strength of the transmitted
signals and the propagation condition.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 899 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.15.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN HD-FDD
Cat-M1 UE under CEModeB
Value
Parameter Unit
Test 1 Test 2 Test 3
E-UTRA RF Channel Number 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 10
DRX cycle ms N/A 80Note5 640Note5
MPCCH Reference measurement channelNote1 R.6 HD-FDD R.6 HD-FDD R. 6 HD-FDD
OCNG PatternNote2 OP.21 FDD OP.21 FDD OP.21 FDD
MPDDCH 128
Number of repetitions
MPUSCH 32
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PHICH_RA
dB 0 0 0
PHICH_RB
MPDCCH_RA
MPDCCH_RB
OCNG_RANote3
OCNG_RBNote3
N oc dBm/15 kHz -98 -98 -98
Ê s I ot dB -12 -12 -12
Ês N oc dB -12 -12 -12
dBm/9 MHz -86.4 -86.4 -86.4
IoNote4
dBm/1.08 MHz N/A N/A N/A
Propagation condition - AWGN AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 5: DRX related parameters are defined in Table A.7.1.15.1-2.
Table A.7.1.15.1-2: drx-Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3
for E-UTRAN HD-FDD Cat-M1 UE under CEModeB
Value Comment
Field
Test 2 Test 3
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 sf640
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.15.2 Test Requirements
For parameters specified in Tables A.7.1.15.1-1 and A.7.1.15.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2. The UE shall not adjust the the transmission timing autonomously during an ongoing repetition
period. Adjustments can only be done at the end of a last subframe in a repetition period.
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 3, respectively):
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 900 ETSI TS 136 133 V14.3.0 (2017-04)
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
NTA×TS ± 48×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 3) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within NTA×TS ± 48×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for Test 2 and Test 3.
d) The test system shall verify that the UE transmit timing offset stays within NTA×TS ± 48×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 3 the UE transmit
timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
A.7.1.16 E-UTRAN TDD - UE Transmit Timing Accuracy Tests for Cat-M1 UE
in CEModeB
A.7.1.16.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE in CEModeB is capable of following the frame timing change
of the connected eNode B and that the UE initial transmit timing accuracy, maximum amount of timing change in one
adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify the
requirements in clause 7.1.2.
As specified in Clause 7.1.2 the UE adjusts its uplink timing at the end of of repetition period when configured with
repetitions. By measuring the reception of the MPUSCH, the transmit timing accuracy can be measured and the
requirements can be verified. For this test a single cell is used. Table A.7.1.16.1-1 defines the strength of the transmitted
signals and the propagation condition.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 901 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.16.1-1: Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN TDD Cat-M1
UE under CEModeB
Value
Parameter Unit
Test 1 Test 2 Test 3
E-UTRA RF Channel Number 1 1 1
Channel Bandwidth (BW channel) MHz 10 10 10
Special subframe configurationNote1 6 6 6
Uplink-downlink configurationNote2 1 1 1
DRX cycle ms N/A 80Note7 640Note7
MPDCCH Reference measurement channelNote3 R.14 TDD R.14 TDD R.14 TDD
OCNG PatternNote4 OP.11 TDD OP.11 TDD OP.11 TDD
PBCH_RA dB 0 0 0
MPDCCH 128
Number of repetitions
MPUSCH 32
PBCH_RB
PSS_RA
SSS_RA
PHICH_RA
PHICH_RB 0 0 0
MPDCCH_RA
MPDCCH_RB
OCNG_RANote5
OCNG_RBNote5
N oc dBm/15 kHz -98 -98 -98
Ê s I ot dB -12 -12 -12
Ês N oc dB -12 -12 -12
dBm/9 MHz -86.4 -86.4 -86.4
IoNote6
dBm/1.08 MHz N/A N/A N/A
Propagation condition - AWGN AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: For the reference measurement channels, see clause A.3.1.
Note 4: For the OCNG pattern, see clause A.3.2.
Note 5: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 6: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
Note 7: DRX related parameters are defined in Table A.7.1.16.1-2.
Table A.7.1.16.1-2: DRX Configuration to be used in UE Transmit Timing Accuracy Test 2 and Test 3
for E-UTRAN TDD Cat-M1 UE under CEModeB
Value Comment
Field
Test 2 Test 3
onDurationTimer psf1 psf1
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 Sf640
shortDRX disable disable
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.1.16.2 Test Requirements
For parameters specified in Tables A.7.1.16.1-1 and A.7.1.16.1-2, the initial transmit timing accuracy, the maximum
amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within the limits
defined in clause 7.1.2. The UE shall not adjust the the transmission timing autonomously during an ongoing repetition
period. Adjustments can only be done at the end of a last subframe in a repetition period.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 902 ETSI TS 136 133 V14.3.0 (2017-04)
The following sequence of events shall be used to verify that the requirements are met.
For the 10MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED for both non-DRX
(for Test1) and DRX with a cycle length of 80 ms or a cycle length of 640 ms (Tests 2 and 3, respectively):
a) After a connection is set up with the cell, the test system shall verify that the UE transmit timing offset is within
NTA×TS ± 48×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS (for Test 1 and Test 2) or +32×TS
(for Test 3) compared to that in (a).
c) The test system shall verify that for Test 1 the adjustment step size and the adjustment rate shall be according to
the requirements in clause 7.1.2 until the UE transmit timing offset is within NTA×TS ± 48×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. Skip this step for Test 2 and Test 3.
d) The test system shall verify that the UE transmit timing offset stays within NTA×TS ± 48×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1. For test 2 and test 3 the UE transmit
timing offset shall be verified for the first transmission in the DRX cycle immediately after DL timing
adjustment.
A.7.1.17 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for
Category NB1 UE In-Band mode under normal coverage
A.7.1.17.1 Test Purpose and Environment
The purpose of this test is to verify that the Category NB1 UE under normal coverage is capable of following the frame
timing change of the connected eNode B and that the UE initial transmit timing accuracy, maximum amount of timing
change in one adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify
the requirements in clause 7.20.
For this test a single NB-IoT cell and a single LTE cell are used. Test parameters are given in Table A.7.1.17.1-1, Table
A.7.1.17.1-2, and Table A.7.1.17.1-3. The transmit timing is verified by the UE transmitting NPUSCH.
Table A.7.1.17.1-1: General Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN
HD-FDD Category NB1 UE in In-Band mode under normal coverage
Value
Parameter Unit
Test 1
NB-IoT Operation mode In-band
DRX OFF
NPRACH configuration As specified in A.3.17
NPDCCH repetition level 1
NPUSCH repetition level 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 903 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.17.1-2: nCell specific Test Parameters for UE Transmit Timing Accuracy Tests for E-
UTRAN HD-FDD Category NB1 UE in In-Band mode under normal coverage
Value
Parameter Unit
Test 1
RF Channel Number 1
BW channel kHz 200
PRB location within eCell 30
NPDSCH parameter R.15 HD-FDD
NPDCCH parameter R.27 HD-FDD
NOCNG Pattern NOP.1 FDD
NPBCH_RA
NPBCH_RB
NPSS_RA
NSSS_RA
NPDCCH_RA
dB 0
NPDCCH_RB
NPDSCH_RA
NPDSCH_RB
NOCNG_RA Note1
NOCNG_RB Note1
N oc dBm/15 kHz Specified in Table A.7.1.x.1-3
Ê s I ot dB 4
Ês N oc dB 4
Antenna Configuration 2x1
Propagation condition - AWGN
Note 1 NOCNG shall be used such that the cell is fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Table A.7.1.17.1-3: eCell specific Test Parameters for UE Transmit Timing Accuracy Tests for E-
UTRAN HD-FDD Category NB1 UE in In-Band mode under normal coverage
Value
Parameter Unit
Test 1
E-UTRA RF Channel Number 1
BW channel MHz 10
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote1
OCNG_RBNote1
N oc dBm/15 kHz -98
Ê s I ot dB 4
Ês N oc dB 4
Antenna configuration 2x1
Propagation condition - AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 904 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.1.17.2 Test Requirements
For parameters specified in Tables A.7.1.17.1-1, A.7.1.17.1-2, and A.7.1.17.1-3, the initial transmit timing accuracy, the
maximum amount of timing change in one adjustment, the minimum and the maximum adjustment rate shall be within
the limits defined in clause 7.20.2.
The following sequence of events shall be used to verify that the requirements are met.
The test sequence shall be carried out in RRC_CONNECTED:
a) After a connection is set up with the cell, the test system sends NPDCCH including uplink grant for NPUSCH
transmission and the test system shall verify that the UE transmit timing offset is within NTA×TS ± 80×TS with
respect to the first detected path (in time) of the corresponding downlink frame of NB-IoT cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +64×TS compared to that in (a).
c) Immediately after (b), the test system sends NPDCCH including uplink grant for NPUSCH transmission and
immediately after receiving NPUSCH the test system repeatedly sends NPDCCH including uplink grant for
NPUSCH transmission until the UE transmit timing offset is within NTA×TS ± 80×TS with respect to the first
detected path (in time) of the corresponding downlink frame of cell 1. The test system shall verify that the
adjustment step size and the adjustment rate shall be according to the requirements in clause 7.20.2 until the UE
transmit timing offset is within NTA×TS ± 12×TS with respect to the first detected path (in time) of the
corresponding downlink frame of cell 1.
d) The test system the test system sends NPDCCH including uplink grant for NPUSCH transmission and shall
verify that the UE transmit timing offset stays within NTA×TS ± 80×TS with respect to the first detected path (in
time) of the corresponding downlink frame of NB-IoT cell 1.
A.7.1.18 E-UTRAN HD-FDD – UE Transmit Timing Accuracy Tests for
Category NB1 UE In-band mode under enhanced coverage
A.7.1.18.1 Test Purpose and Environment
The purpose of this test is to verify that the Category NB1 UE under enhanced coverage is capable of following the
frame timing change of the connected eNode B, that the UE initial transmit timing accuracy is within the specified
limits and that the UE shall not adjust the uplink transmission timing autonomously during an ongoing repetition period
other than at initial transmission. This test will verify the requirements in clause 7.20.
For this test a single NB-IoT cell and a single LTE cell are used. Test parameters are given in Table A.7.1.18.1-1, Table
A.7.1.18.1-2, Table A.7.1.18.1-3, and Table A.7.1.18.1-4. The transmit timing is verified by the UE transmitting
NPUSCH.
Table A.7.1.18.1-1: General Test Parameters for UE Transmit Timing Accuracy Tests for E-UTRAN
HD-FDD Category NB1 UE in In-Band mode under enhanced coverage
Value
Parameter Unit
Test 1 Test 2
NB-IoT Operation mode In-band In-band
DRX OFF ON
NPRACH configuration As specified in A.3.17
NPDCCH repetition level 128 128
NPUSCH repetition level 32 32
Note 1: DRX related parameters are defined in Table A.7.1.18.1-4.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 905 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.18.1-2: nCell specific Test Parameters for UE Transmit Timing Accuracy Tests for E-
UTRAN HD-FDD Category NB1 UE in In-Band mode under enhanced coverage
Value
Parameter Unit
Test 1 Test 2
RF Channel Number 1 1
BW channel kHz 200 200
PRB location within eCell 30 30
NPDSCH parameter R.17 HD-FDD R.17 HD-FDD
NPDCCH parameter R.29 HD-FDD R.29 HD-FDD
NOCNG Pattern NOP.1 FDD NOP.1 FDD
NPBCH_RA
NPBCH_RB
NPSS_RA
NSSS_RA
NPDCCH_RA
dB 0 0
NPDCCH_RB
NPDSCH_RA
NPDSCH_RB
NOCNG_RA Note1
NOCNG_RB Note1
Specified in Table Specified in Table
N oc dBm/15 kHz
A.7.1.18.1-3 A.7.1.18.1-3
Ê s I ot dB -12 -12
Ês N oc dB -12 -12
Antenna Configuration 2x1 2x1
Propagation condition - AWGN AWGN
Note 1 NOCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Table A.7.1.18.1-3: eCell specific Test Parameters for UE Transmit Timing Accuracy Tests for E-
UTRAN HD-FDD Category NB1 UE in In-Band mode under enhanced coverage
Value
Parameter Unit
Test 1 Test 2
E-UTRA RF Channel Number 1 1
BW channel MHz 10 10
PRB location within eCell 30 30
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote1
OCNG_RBNote1
N oc dBm/15 kHz -98 -98
Ê s I ot dB -12 -12
Ês N oc dB -12 -12
Antenna Configuration 2x1 2x1
Propagation condition - AWGN AWGN
Note 1 OCNG shall be used such that the cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 906 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.1.18.1-4: drx-Configuration to be used in UE Transmit Timing Accuracy Test 2 for E-UTRAN
HD-FDD Category NB1 UE In-band mode under enhanced coverage
Value Comment
Field
Test 2
onDurationTimer pp1
drx-InactivityTimer pp0
drx-RetransmissionTimer pp0
longDRX-CycleStartOffset sf2048
shortDRX disable
Note 1: For further information see clause 6.7.3 in TS 36.331.
A.7.1.18.2 Test Requirements
For parameters specified in Tables A.7.1.18.1-1, Tables A.7.1.18.1-2, Tables A.7.1.18.1-3 and Tables A.7.1.18.1-4, the
initial transmit timing accuracy shall be within the limits defined in clause 7.20.2 and the UE shall not adjust the uplink
transmission timing autonomously during an ongoing repetition period other than at initial transmission.
The following sequence of events shall be used to verify that the requirements are met.
The test sequence shall be carried out in RRC_CONNECTED for both non-DRX (for Test1) and DRX with a cycle
length of 2048 ms (Tests 2):
a) After a connection is set up with the cell, the test system sends NPDCCH including uplink grant for NPUSCH
transmission and the test system shall verify that the UE transmit timing offset is within NTA×TS ± 80×TS with
respect to the first detected path (in time) of the corresponding downlink frame of NB-IoT cell 1.
b) After 16ms from the initial transmission in (a), the test system adjusts the downlink transmit timing for the cell
by +200×TS compared to that in (a).
c) The test system shall verify that for Test 1 the UE shall not adjust the uplink transmission timing autonomously
during an ongoing repetition period. Skip this step for Test 2.
d) The test system sends NPDCCH including uplink grant for NPUSCH transmission and shall verify that the UE
transmit timing offset stays within NTA×TS ± 80×TS with respect to the first detected path (in time) of the
corresponding downlink frame of NB-IoT cell 1. For test 2 the UE transmit timing offset shall be verified for the
first transmission in the DRX cycle immediately after DL timing adjustment.
A.7.2 UE Timing Advance
A.7.2.1 E-UTRAN FDD – UE Timing Advance Adjustment Accuracy Test
A.7.2.1.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN FDD Timing Advance adjustment accuracy requirements, defined in
clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.1.1-1, A.7.2.1.1-2, and A.7.2.1.1-3. The test consists of two successive
time periods, with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to
the UE and Sounding Reference Signals (SRS), as specified in table A.7.2.1.1-3, are sent from the UE and received by
the test equipment. By measuring the reception of the SRS, the transmit timing, and hence the timing advance
adjustment accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.1.1-2. This value shall result in
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 907 ETSI TS 136 133 V14.3.0 (2017-04)
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using the SRS
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via the SRS sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
Table A.7.2.1.1-1: General Test Parameters for E-UTRAN FDD Timing Advance Accuracy Test
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement Channel As specified in clause A.3.1.1.1
R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement Channel As specified in clause A.3.1.2.1
parameters R.6 FDD
Timing Advance Command 31 NTA = 0 for the purpose of establishing
(TA) value during T1 a reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
DRX OFF
T1 s 5
T2 s 5
Table A.7.2.1.1-2: Cell specific Test Parameters for E-UTRAN FDD Timing Advance Accuracy Test
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
OCNG Patterns defined in A.3.2.1.1 OP.1 FDD
(OP.1 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
Timing Advance Command (TA) 31 39
dB 3
Ê s I ot
N oc dBm/15 KHz -98
dB 3
Ês N oc
IoNote2 dBm/9 MHz -65.5
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 908 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.1.1-3: Sounding Reference Symbol Configuration for E-UTRAN FDD Transmit Timing
Accuracy Test
Field Value Comment
srsBandwidthConfiguration bw5
srsSubframeConfiguration sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE
srsMaxUpPTS N/A Not applicable for E-UTRAN FDD
srsBandwidth 0 No hopping
srsHoppingBandwidth hbw0
frequencyDomainPosition 0
Duration TRUE Indefinite duration
Srs-ConfigurationIndex 7 SRS periodicity of 10.
transmissionComb 0
cyclicShift cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.2.1.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
A.7.2.2 E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test
A.7.2.2.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN TDD Timing Advance adjustment accuracy requirements, defined in
clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.2.1-1, A.7.2.2.1-2, and A.7.2.2.1-3. The test consists of two successive
time periods, with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to
the UE and Sounding Reference Signals (SRS), as specified in table A.7.2.2.1-3, are sent from the UE and received by
the test equipment. By measuring the reception of the SRS, the transmit timing, and hence the timing advance
adjustment accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.1.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using the SRS
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via the SRS sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 909 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.2.1-1: General Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2
parameters Channel R.6 TDD
Timing Advance Command 31 NTA = 0 for the purpose of establishing a
(TA) value during T1 reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
DRX OFF
T1 s 5
T2 s 5
Table A.7.2.2.1-2: Cell specific Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
Special subframe configurationNote1 6
Uplink-downlink configurationNote2 1
OCNG Patterns defined in A.3.2.2.1 OP.1 TDD
(OP.1 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
Timing Advance Command (TA) 31 39
dB 3
Ê s I ot
N oc dBm/15 KHz -98
dB 3
Ês N oc
IoNote4 dBm/9 MHz -65.5
Propagation Condition AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 910 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.2.1-3: Sounding Reference Symbol Configuration for E-UTRAN TDD Transmit Timing
Accuracy Test
Field Value Comment
srsBandwidthConfiguration bw5
srsSubframeConfiguration sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE
srsMaxUpPTS N/A
srsBandwidth bw0 No hopping
srsHoppingBandwidth hbw0
frequencyDomainPosition 0
Duration TRUE Indefinite duration
Srs-ConfigurationIndex 15 SRS periodicity of 10ms.
transmissionComb 0
cyclicShift cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.2.2.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
A.7.2.3 E-UTRAN FDD – UE Timing Advance Adjustment Accuracy Test for
5MHz
A.7.2.3.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.2.1.1.
The parameters of this test are the same as defined in Subclause A.7.2.1.1 except that the values of the parameters in the
Table A.7.2.3.1-1 will replace the values of the corresponding parameters in A.7.2.1.1-1, table A.7.2.3.1-2 will replace
the values of the corresponding parameters in A.7.2.1.1-2. Parameters used for the sounding reference symbol
configuration are unchanged from table A.7.2.1.1-3.
Table A.7.2.3.1-1: General Test Parameters for E-UTRAN FDD Timing Advance Accuracy Test for
5MHz bandwidth
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement Channel As specified in clause A.3.1.1.1
R.5 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement Channel As specified in clause A.3.1.2.1
parameters R.11 FDD
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: See Table A.7.2.1.1-1 for the other parameters.
Note 3: This test is according to the principle defined in section A.3.7.2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 911 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.3.1-2: Cell specific Test Parameters for E-UTRAN FDD Timing Advance Accuracy Test for
5MHz bandwidth
Parameter Unit Value
T1 T2
BW channel MHz 5
OCNG Patterns defined in OP.15 FDD
A.3.2.1.15 (OP.15 FDD)
dBm/4.5 -68.5
IoNote2
MHz
Note 1: For the reference measurement channels, see clause A.3.2.
Note 2: See Table A.7.2.1.1-2 for the other parameters.
A.7.2.3.2 Test Requirements
The test requirements defined in section A.7.2.1.2 shall apply to this test case.
A.7.2.4 E-UTRAN FDD – UE Timing Advance Adjustment Accuracy Test for
SCell in sTAG
A.7.2.4.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN FDD Timing Advance adjustment accuracy requirements, defined in
clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.4.1-1, A.7.2.4.1-2, and A.7.2.4.1-3. For this test two cells are used. Cell 1
is PCell and Cell 2 is SCell. PCell is in the primary Timing Advance Group (pTAG) and SCell is in the secondary
Timing Advance Group (sTAG). The test consists of two successive time periods, with time duration of T1 and T2
respectively. In each time period, timing advance commands for sTAG are sent to the UE and Sounding Reference
Signals (SRS), as specified in table A.7.2.4.1-3, are sent from the UE and received by the test equipment. By measuring
the reception of the SRS, the transmit timing, and hence the timing advance adjustment accuracy, can be measured for
SCell in sTAG.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element for sTAG, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31,
which according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a
reference value for the timing advance for sTAG used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements for sTAG, with Timing Advance Command value specified in table A.7.2.4.1-2. This value shall
result in changes of the timing advance for sTAG used by the UE, and the accuracy of the change shall then be
measured, using the SRS sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via the SRS sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 912 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.4.1-1: General Test Parameters for E-UTRAN FDD Timing Advance Accuracy Test for
SCell in sTAG
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement Channel As specified in clause A.3.1.1.1
R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement Channel As specified in clause A.3.1.2.1
parameters R.6 FDD
Timing Advance Command 31 NTA = 0 for the purpose of establishing
(TA) value during T1 a reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
DRX OFF
T1 s 5
T2 s 5
Table A.7.2.4.1-2: Cell specific Test Parameters for E-UTRAN FDD Timing Advance Accuracy Test for
SCell in sTAG
Parameter Unit Value
Cell1 Cell2
T1 T2 T1 T2
E-UTRA RF Channel 1 2
Number
BW channel MHz 10 10
Active PCell Cell1 Cell1
Active SCell Cell2 Cell2
TAG configuration pTAG pTAG sTAG sTAG
OCNG Patterns defined OP.1 FDD OP.1 FDD
in A.3.2.1.1 (OP.1 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
Timing Advance / / 31 39
Command (TA)
dB 3 3
Ê s I ot
N oc dBm/15 -98 -98
KHz
dB 3 3
Ês N oc
dBm/9 -65.5 -65.5
IoNote2
MHz
Propagation Condition AWGN AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 913 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.4.1-3: Sounding Reference Symbol Configuration for E-UTRAN FDD Transmit Timing
Accuracy Test for SCell in sTAG
Field Value Comment
srsBandwidthConfiguration bw5
srsSubframeConfiguration sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE
srsMaxUpPTS N/A Not applicable for E-UTRAN FDD
srsBandwidth 0 No hopping
srsHoppingBandwidth hbw0
frequencyDomainPosition 0
Duration TRUE Indefinite duration
Srs-ConfigurationIndex 7 SRS periodicity of 10.
transmissionComb 0
cyclicShift cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.2.4.2 Test Requirements
The UE shall apply the signalled Timing Advance value for SCell in sTAG to the transmission timing at the designated
activation time i.e. 6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy for SCell in STAG shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
A.7.2.5 E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test for
Scell in sTAG
A.7.2.5.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN TDD Timing Advance adjustment accuracy requirements, defined in
clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.5.1-1, A.7.2.5.1-2, and A.7.2.5.1-3. For this test two cells are used. Cell 1
is PCell and Cell 2 is SCell. PCell is in the primary Timing Advance Group (pTAG) and SCell is in the secondary
Timing Advance Group (sTAG). The test consists of two successive time periods, with time duration of T1 and T2
respectively. In each time period, timing advance commands for sTAG are sent to the UE and Sounding Reference
Signals (SRS), as specified in table A.7.2.5.1-3, are sent from the UE and received by the test equipment, but only for
SCell. By measuring the reception of the SRS, the transmit timing, and hence the timing advance adjustment accuracy,
can be measured for SCell in sTAG.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element for sTAG, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31,
which according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a
reference value for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements for sTAG, with Timing Advance Command value specified in table A.7.2.5.1-2. This value shall
result in changes of the timing advance on SCell used by the UE, and the accuracy of the change shall then be
measured, using the SRS sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via the SRS sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 914 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.5.1-1: General Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test for
SCell in sTAG
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2
parameters Channel R.6 TDD
Timing Advance Command 31 NTA = 0 for the purpose of establishing a
(TA) value during T1 reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
DRX OFF
T1 s 5
T2 s 5
Table A.7.2.5.1-2: Cell specific Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test for
SCell in sTAG
Parameter Unit Value
Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel Number 1 2
BW channel MHz 10 10
Active PCell Cell1
Active SCell Cell2
TAG configuration pTAG sTAG
Special subframe configurationNote1 6 6
Uplink-downlink configurationNote2 1 1
OCNG Patterns defined in A.3.2.2.1
OP.1 TDD OP.1 TDD
(OP.1 TDD)
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
OCNG_RANote3 dB
OCNG_RBNote3 dB
Timing Advance Command (TA) 31 39
dB 3 3
Ê s I ot
N oc dBm/15 KHz -98 -98
dB 3 3
Ês N oc
IoNote4 dBm/9 MHz -65.5 -65.5
Propagation Condition AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 915 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.5.1-3: Sounding Reference Symbol Configuration for E-UTRAN TDD Transmit Timing
Accuracy Test for SCell in sTAG
Field Value Comment
srsBandwidthConfiguration bw5
srsSubframeConfiguration sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE
srsMaxUpPTS N/A
srsBandwidth bw0 No hopping
srsHoppingBandwidth hbw0
frequencyDomainPosition 0
Duration TRUE Indefinite duration
Srs-ConfigurationIndex 15 SRS periodicity of 10ms.
transmissionComb 0
cyclicShift cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note: For further information see clause 6.3.2 in TS 36.331.
A.7.2.5.2 Test Requirements
The UE shall apply the signalled Timing Advance value for SCell in sTAG to the transmission timing at the designated
activation time i.e. 6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy for SCell in sTAG shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
A.7.2.5A E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test for
Scell in sTAG for 20 MHz +20 MHz
A.7.2.5A.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.2.5.1.
The parameters of this test are the same as defined in Subclause A.7.2.5.1 except that the values of the parameters in the
Table A.7.2.5A.1-1 will replace the values of the corresponding parameters in A.7.2.5.1-1, table A.7.2.5A.1-2 will
replace the values of the corresponding parameters in A.7.2.5.1-2. Parameters used for the sounding reference symbol
configuration are unchanged from table A.7.2.5.1-3.
Table A.7.2.5A.1-1: General Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test for
SCell in sTAG for 20 MHz +20 MHz
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.3 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2
parameters Channel R.10 TDD
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 916 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.5A.1-2: Cell specific Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test
for SCell in sTAG for 20 MHz +20 MHz
Parameter Unit Value
Cell 1 Cell 2
T1 T2 T1 T2
BW channel MHz 20 20
OCNG Patterns defined in A.3.2.2 OP.7 TDD OP.7 TDD
IoNote4 dBm/18 MHz -62.5 -62.5
A.7.2.5A.2 Test Requirements
The test requirements defined in section A.7.2.5.2 shall apply to this test case.
A.7.2.5B E-UTRAN TDD – UE Timing Advance Adjustment Accuracy Test for
Scell in sTAG for 20 MHz +10 MHz
A.7.2.5B.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.2.5.1.
The parameters of this test are the same as defined in Subclause A.7.2.5.1 except that the values of the parameters in the
Table A.7.2.5B.1-1 will replace the values of the corresponding parameters in A.7.2.5.1-1, table A.7.2.5B.1-2 will
replace the values of the corresponding parameters in A.7.2.5.1-2. Parameters used for the sounding reference symbol
configuration are unchanged from table A.7.2.5.1-3.
Table A.7.2.5B.1-1: General Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test for
SCell in sTAG for 20 MHz +10 MHz
Parameter Unit Value Comment
PDSCH parameters For Cell 1: DL Reference As specified in clause A.3.1.1.2
Measurement Channel R.3 TDD
For Cell 2: DL Reference
Measurement Channel R.0 TDD
PCFICH/PDCCH/PHICH For Cell 1: DL Reference As specified in clause A.3.1.2.2
parameters Measurement Channel R.10 TDD
For Cell 2: DL Reference
Measurement Channel R.6 TDD
Table A.7.2.5B.1-2: Cell specific Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test
for SCell in sTAG for 20 MHz +10 MHz
Parameter Unit Value
Cell 1 Cell 2
T1 T2 T1 T2
BW channel MHz 20 10
OCNG Patterns defined in A.3.2.2 OP.7 TDD OP.1 TDD
dBm/18 MHz -62.5 N/A
IoNote4
dBm/9 MHz N/A -65.5
A.7.2.5B.2 Test Requirements
The test requirements defined in section A.7.2.5.2 shall apply to this test case.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 917 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.2.6 E-UTRAN FDD Timing Advance Adjustment Accuracy Test for Cat-
M1 UE in CEModeA
A.7.2.6.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN FDD Timing Advance adjustment accuracy requirements for Cat-M1 UE
configured with CEModeA, defined in clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.6.1-1, A.7.2.6.1-2, and A.7.2.6.1-3. The test consists of two successive
time periods, with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to
the UE and Sounding Reference Signals (SRS), as specified in table A.7.2.1.1-3, are sent from the UE and received by
the test equipment. By measuring the reception of the SRS, the transmit timing, and hence the timing advance
adjustment accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.6.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using the SRS
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via the SRS sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
Table A.7.2.6.1-1: General Test Parameters for E-UTRAN FDD Timing Advance Accuracy Test for Cat-
M1 UE in CEModeA
Parameter Unit Value Comment
PDSCH parameters: R.20 FDD As specified in clause A.3.1.4.1
DL Reference Measurement
Channel
MPDCCH parameters: R.16 FDD As specified in clause A.3.1.3.1
DL Reference Measurement
Channel
Timing Advance Command 31 NTA = 0 for the purpose of establishing
(TA) value during T1 a reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
DRX OFF
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 918 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.6.1-2: Cell specific Test Parameters for E-UTRAN FDD UE Timing Advance Accuracy Test
for Cat-M1 UE in CEModeA
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
PDSCH parameters: R.20 FDD
DL Reference Measurement
Channel
MPDCCH parameters: R.16 FDD
DL Reference Measurement
Channel
OCNG Patterns defined in OP.21 FDD
A.3.2.1.21
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
MPDCCH_RA dB 0
MPDCCH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
Timing Advance Command (TA) 31 39
Ê s I ot dB 3
N oc dBm/15 KHz -98
Ê s N oc dB 3
IoNote2 dBm/9 MHz -65.5
Propagation Condition AWGN
Note 1: OCNG shall be used such that cells is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Table A.7.2.6.1-3: Sounding Reference Symbol Configuration for E-UTRAN FDD UE Transmit Timing
Accuracy Test for Cat-M1 UE in CEModeA
Field Value Comment
srsBandwidthConfiguration Bw5
srsSubframeConfiguration sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE
srsMaxUpPTS N/A Not applicable for E-UTRAN FDD
srsBandwidth 0 No hopping
srsHoppingBandwidth hbw0
frequencyDomainPosition 0
Duration TRUE Indefinite duration
Srs-ConfigurationIndex 7 SRS periodicity of 10.
transmissionComb 0
cyclicShift cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note 1: For further information see clause 6.3.2 in TS 36.331.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 919 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.2.6.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
A.7.2.7 E-UTRAN HD-FDD UE Timing Advance Adjustment Accuracy Test
for Cat-M1 UE in CEModeA
A.7.2.7.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN HD-FDD Timing Advance adjustment accuracy requirements for Cat-M1
UE configured with CEModeA, defined in clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.7.1-1, A.7.2.7.1-2, and A.7.2.7.1-3. The test consists of two successive
time periods, with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to
the UE and Sounding Reference Signals (SRS), as specified in table A.7.2.7.1-3, are sent from the UE and received by
the test equipment. By measuring the reception of the SRS, the transmit timing, and hence the timing advance
adjustment accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.7.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using the SRS
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via the SRS sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
Table A.7.2.7.1-1: General Test Parameters for E-UTRAN HD-FDD Timing Advance Accuracy Test for
Cat-M1 UE in CEModeA
Parameter Unit Value Comment
PDSCH parameters: R.10 HD-FDD As specified in clause A.3.1.4.2
DL Reference Measurement
Channel
MPDCCH parameters: R.6 HD-FDD As specified in clause A.3.1.3.2
DL Reference Measurement
Channel
Timing Advance Command 31 NTA = 0 for the purpose of establishing
(TA) value during T1 a reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
DRX OFF
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 920 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.7.1-2: Cell specific Test Parameters for E-UTRAN HD-FDD Timing Advance Accuracy Test
for Cat-M1 UE in CEModeA
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
PDSCH parameters: R.10 HD-FDD
DL Reference Measurement
Channel
MPDCCH parameters: R.6 HD-FDD
DL Reference Measurement
Channel
OCNG Patterns defined in OP.21 FDD
A.3.2.1.21
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
MPDCCH_RA dB 0
MPDCCH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
Timing Advance Command (TA) 31 39
Ê s I ot dB 3
N oc dBm/15 KHz -98
Ê s N oc dB 3
IoNote2 dBm/9 MHz -65.5
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
Table A.7.2.7.1-3: Sounding Reference Symbol Configuration for E-UTRAN HD-FDD Transmit Timing
Accuracy Test for Cat-M1 UE in CEModeA
Field Value Comment
srsBandwidthConfiguration Bw5
srsSubframeConfiguration sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE
srsMaxUpPTS N/A
srsBandwidth 0 No hopping
srsHoppingBandwidth hbw0
frequencyDomainPosition 0
Duration TRUE Indefinite duration
Srs-ConfigurationIndex 7 SRS periodicity of 10.
transmissionComb 0
cyclicShift cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note 1: For further information see clause 6.3.2 in TS 36.331.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 921 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.2.7.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
A.7.2.8 E-UTRAN TDD Timing Advance Adjustment Accuracy Test for Cat-
M1 UE in CEModeA
A.7.2.8.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN TDD Timing Advance adjustment accuracy requirements for Cat-M1 UE
configured with CEModeA, defined in clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.8.1-1, A.7.2.8.1-2, and A.7.2.8-3. The test consists of two successive time
periods, with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to the
UE and Sounding Reference Signals (SRS), as specified in table A.7.2.8.1-3, are sent from the UE and received by the
test equipment. By measuring the reception of the SRS, the transmit timing, and hence the timing advance adjustment
accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.8.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using the SRS
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via the SRS sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
Table A.7.2.8.1-1: General Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test for Cat-
M1 UE in CEModeA
Parameter Unit Value Comment
PDSCH parameters: R.16 TDD As specified in clause A.3.1.4.3
DL Reference Measurement
Channel
MPDCCH parameters: R.14 TDD As specified in clause A.3.1.3.3
DL Reference Measurement
Channel
Timing Advance Command 31 NTA = 0 for the purpose of establishing a
(TA) value during T1 reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
DRX OFF
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 922 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.8.1-2: Cell specific Test Parameters for E-UTRAN TDD Timing Advance Accuracy Test for
Cat-M1 UE in CEModeA
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
PDSCH parameters: R.16 TDD
DL Reference Measurement
Channel
MPDCCH parameters: R.14 TDD
DL Reference Measurement
Channel
Special subframe configurationNote1 6
Uplink-downlink configurationNote2 1
OCNG Patterns defined in OP.11 TDD
A.3.2.2.11
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
MPDCCH_RA dB 0
MPDCCH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
Timing Advance Command (TA) 31 39
Ê s I ot dB 3
N oc dBm/15 KHz -98
Ê s N oc dB 3
IoNote4 dBm/9 MHz -65.5
Propagation Condition AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 4: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 923 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.8.1-3: Sounding Reference Symbol Configuration for E-UTRAN TDD Transmit Timing
Accuracy Test for Cat-M1 UE in CEModeA
Field Value Comment
srsBandwidthConfiguration Bw5
srsSubframeConfiguration sc3 Once every 5 subframes
ackNackSrsSimultaneousTransmission FALSE
srsMaxUpPTS N/A
srsBandwidth bw0 No hopping
srsHoppingBandwidth hbw0
frequencyDomainPosition 0
Duration TRUE Indefinite duration
Srs-ConfigurationIndex 15 SRS periodicity of 10ms.
transmissionComb 0
cyclicShift cs0 No cyclic shift
SRS-AntennaPort an1 Number of antenna ports used for SRS
transmission
Note 1: For further information see clause 6.3.2 in TS 36.331.
A.7.2.8.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
A.7.2.9 HD-FDD UE Timing Advance Adjustment Accuracy Test for UE
Category NB1 in Standalone Mode under Enhance Coverage
A.7.2.9.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN Timing Advance adjustment accuracy requirements for UE category NB1
in enhanced coverage, defined in clause 7.22.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.9.1-1 and A.7.2.9.1-2. The test consists of two successive time periods,
with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to the UE and the
UE is scheduled in every uplink subframe to transmit NPUSCH, which is received by the test equipment. By measuring
the reception of the NPUSCH, the transmit timing, and hence the timing advance adjustment accuracy, can be
measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 16.1.2 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference
value for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.9.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using the
NPUSCH sent from the UE.
As specified in Clause 7.22.2.1, the UE adjusts its uplink timing at sub-frame n+12 for a timing advance command
received in sub-frame n, where sub-frame n refers to the last subframe in the repetition period in which the MAC
control element containing timing advance command was received. In addition, the UE shall not apply a TA command
during an uplink repetition period. In the test the NPUSCH repetition period is equal to 32 subframes. This delay must
be taken into account when measuring the timing advance adjustment accuracy, via the NPUSCH sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 924 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.9.1-1: General Test Parameters for E-UTRAN Timing Advance Accuracy Test for UE
Category NB1 in Standalone Mode under Enhanced Coverage
Parameter Unit Value Comment
NB-IoT operational mode Standalone
CP Length Normal
Timing Advance Command 31 NTA = 0 for the purpose of establishing
(TA) value during T1 a reference value from which the timing
advance adjustment accuracy can be
measured during T2
Timing Advance Command 39 NTA = 128
(TA) value during T2
Number of NPDCCH 128
repetitons NPUSCH 32
DRX OFF
T1 s 5
T2 s 5
Table A.7.2.9.1-2: Cell specific Test Parameters for E-UTRAN Timing Advance Accuracy Test for UE
Category NB1 in Standalone Mode under Enhanced Coverage
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel KHz 200
NPDSCH parameters: R.20 HD-FDD
DL Reference Measurement
Channel defined in A.3.1.5.4
NPDCCH parameters: R.32 HD-FDD
DL Reference Measurement
Channel defined in A.3.1.6.4
NOCNG Patterns defined in NOP.3 FDD
A.3.2.3.3
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB
NSSS_RA dB
NPDCCH_RA dB
NPDCCH_RB dB
NPDSCH_RA dB
0
NPDSCH_RB dB
NOCNG_RANote1 dB
NOCNG_RBNote1 dB
Timing Advance Command (TA) 31 39
Ê s I ot dB -12
N oc dBm/15 KHz -88
Ê s N oc dB -12
IoNote2 dBm/ 180 KHz -76.9
Antenna Configuration 1x1
Propagation Condition AWGN
Note 1: OCNG shall be used such that the cell is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Io level has been derived from other parameters for information purpose. It is not a settable
parameter.
A.7.2.9.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at subframe n+40, where subframe n
is the last subframe in the repetition period of NPDCCH in which the timing advance command is received by the UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 925 ETSI TS 136 133 V14.3.0 (2017-04)
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.22.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
NOTE: In the test requirement the timing advance adjustment delay of 40 subfames include:
- NPUSCH repetition period equal to 32 subframes and
- Uplink delay of 8 subframes. This is the time between the last subframe in the repetition period of NPDCCH and
the first subframe in the repetition period of the corresponding NPUSCH.
A.7.2.10 E-UTRAN FDD UE Timing Advance Adjustment Accuracy Test in
CEModeB
A.7.2.10.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN FDD Timing Advance adjustment accuracy requirements for Cat-M1 UE
configured with CEModeB, defined in clause 7.3.2.2, in an AWGN model.
The test parameters are given in tables A.7.2.10.1-1and A.7.2.10.1-2. The test consists of two successive time periods,
with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to the UE and
MPUSCH are sent from the UE and received by the test equipment. By measuring the reception of the MPUSCH, the
transmit timing, and hence the timing advance adjustment accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.10.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using MPUSCH
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via MPUSCH sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
Table A.7.2.10.1-1: General Test Parameters for E-UTRAN FDD UE Timing Advance Adjustment
Accuracy Test in CEModeB
Parameter Unit Value Comment
Timing Advance Command (TA) value 31 NTA = 0 for the purpose of establishing a reference value
during T1 from which the timing advance adjustment accuracy can
be measured during T2
Timing Advance Command (TA) value 39 NTA = 128
during T2
DRX OFF
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 926 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.10.1-2: Cell specific Test Parameters for E-UTRAN FDD UE Timing Advance Adjustment
Accuracy Test in CEModeB
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
PDSCH Reference Measurement Channel R.22 FDD
in clause A.3.1.4.4
MPDCCH Reference Measurement R.18 FDD
Channel in clause A.3.1.3.4
OCNG Patterns defined in A.3.2.1.21 OP.21 FDD
MPDCCH 128
Number of repetitions
MPUSCH 32
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
0
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
Timing Advance Command (TA) 31 39
N oc dBm/15 KHz -98
Ês N oc dB -12
Ê s I ot Note2 dB -12
RSRP Note2 dBm/15 KHz -110
Io Note2 dBm/9 MHz -69.95
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that cells is fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Ê s I ot , RSRP, Io level has been derived from other parameters for information purpose. It is
not a settable parameter.
A.7.2.10.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 subframes after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
When a repetition period is configured on the uplink, the UE shall not adjust the uplink transmission timing
autonomously during an ongoing repetition period for which R>1.
A.7.2.11 E-UTRAN HD-FDD UE Timing Advance Adjustment Accuracy Test
in CEModeB
A.7.2.11.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN HD-FDD Timing Advance adjustment accuracy requirements for Cat-M1
UE configured with CEModeB, defined in clause 7.3.2.2, in an AWGN model.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 927 ETSI TS 136 133 V14.3.0 (2017-04)
The test parameters are given in tables A.7.2.11.1-1and A.7.2.11.1-2. The test consists of two successive time periods,
with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to the UE and
MPUSCH are sent from the UE and received by the test equipment. By measuring the reception of the MPUSCH, the
transmit timing, and hence the timing advance adjustment accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.11.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using MPUSCH
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via MPUSCH sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
Table A.7.2.11.1-1: General Test Parameters for E-UTRAN HD-FDD UE Timing Advance Adjustment
Accuracy Test in CEModeB
Parameter Unit Value Comment
Timing Advance Command (TA) value 31 NTA = 0 for the purpose of establishing a reference
during T1 value from which the timing advance adjustment
accuracy can be measured during T2
Timing Advance Command (TA) value 39 NTA = 128
during T2
DRX OFF
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 928 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.11.1-2: Cell specific Test Parameters for E-UTRAN HD-FDD UE Timing Advance
Adjustment Accuracy Test in CEModeB
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
PDSCH Reference Measurement R.12 HD-FDD
Channel in clause A.3.1.4.5
MPDCCH Reference Measurement R.8 HD-FDD
Channel in clause A.3.1.3.5
OCNG Patterns defined in A.3.2.1.21 OP.21 FDD
MPDCCH 128
Number of repetitions
MPUSCH 32
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
Timing Advance Command (TA) 31 39
N oc dBm/15 KHz -98
Ês N oc dB -12
Ê s I ot Note2 dB -12
RSRP Note2 dBm/15 KHz -110
IoNote2 dBm/9 MHz -69.95
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Ê s I ot , RSRP, Io level has been derived from other parameters for information purpose. It is
not a settable parameter.
A.7.2.11.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
When a repetition period is configured on the uplink, the UE shall not adjust the uplink transmission timing
autonomously during an ongoing repetition period for which R>1.
A.7.2.12 E-UTRAN TDD UE Timing Advance Adjustment Accuracy Test in
CEModeB
A.7.2.12.1 Test Purpose and Environment
The purpose of the test is to verify E-UTRAN TDD Timing Advance adjustment accuracy requirements for Cat-M1 UE
configured with CEModeB, defined in clause 7.3.2.2, in an AWGN model.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 929 ETSI TS 136 133 V14.3.0 (2017-04)
The test parameters are given in tables A.7.2.12.1-1and A.7.2.12.1-2. The test consists of two successive time periods,
with time duration of T1 and T2 respectively. In each time period, timing advance commands are sent to the UE and
MPUSCH are sent from the UE and received by the test equipment. By measuring the reception of the MPUSCH, the
transmit timing, and hence the timing advance adjustment accuracy, can be measured.
During time period T1, the test equipment shall send one message with a Timing Advance Command MAC Control
Element, as specified in Clause 6.1.3.5 in TS 36.321. The Timing Advance Command value shall be set to 31, which
according to Clause 4.2.3 in TS 36.213 results in zero adjustment of the Timing Advance. In this way, a reference value
for the timing advance used by the UE is established.
During time period T2, the test equipment shall send a sequence of messages with Timing Advance Command MAC
Control Elements, with Timing Advance Command value specified in table A.7.2.12.1-2. This value shall result in
changes of the timing advance used by the UE, and the accuracy of the change shall then be measured, using MPUSCH
sent from the UE.
As specified in Clause 7.3.2.1, the UE adjusts its uplink timing at sub-frame n+6 for a timing advance command
received in sub-frame n. This delay must be taken into account when measuring the timing advance adjustment
accuracy, via MPUSCH sent from the UE.
The UE Time Alignment Timer, described in Clause 5.2 in TS 36.321, shall be configured so that it does not expire in
the duration of the test.
Table A.7.2.12.1-1: General Test Parameters for E-UTRAN TDD UE Timing Advance Adjustment
Accuracy Test in CEModeB
Parameter Unit Value Comment
Timing Advance Command (TA) value 31 NTA = 0 for the purpose of establishing a reference value
during T1 from which the timing advance adjustment accuracy can
be measured during T2
Timing Advance Command (TA) value 39 NTA = 128
during T2
DRX OFF
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 930 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.2.12.1-2: Cell specific Test Parameters for E-UTRAN TDD UE Timing Advance Adjustment
Accuracy Test in CEModeB
Parameter Unit Value
T1 T2
E-UTRA RF Channel Number 1
BW channel MHz 10
PDSCH Reference Measurement R.18 TDD
Channel in clause A.3.1.4.6
MPDCCH Reference Measurement R.16 TDD
Channel in clause A.3.1.3.6
Special subframe configurationNote1 6
Uplink-downlink configurationNote2 1
OCNG Patterns defined in A.3.2.2.11 OP.11 TDD
Number of MPDCCH 128
repetitions MPUSCH 32
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
Timing Advance Command (TA) 31 39
N oc dBm/15 KHz -98
Ês N oc dB -12
Ê s I ot Note4 dB -12
RSRP Note4 dBm/15 KHz -110
IoNote4 dBm/9 MHz -69.95
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 4: Ê s I ot , RSRP, Io level has been derived from other parameters for information purpose. It is
not a settable parameter.
A.7.2.12.2 Test Requirements
The UE shall apply the signalled Timing Advance value to the transmission timing at the designated activation time i.e.
6 sub frames after the reception of the timing advance command.
The Timing Advance adjustment accuracy shall be within the limits specified in clause 7.3.2.2.
The rate of correct Timing Advance adjustments observed during repeated tests shall be at least 90%.
When a repetition period is configured on the uplink, the UE shall not adjust the uplink transmission timing
autonomously during an ongoing repetition period for which R>1.
A.7.3 Radio Link Monitoring
In the following section, any uplink signal transmitted by the UE is used for detecting the In-/Out-of-Sync state of the
UE. In terms of measurement, the uplink signal is verified on the basis of the UE output power:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 931 ETSI TS 136 133 V14.3.0 (2017-04)
For intra-band contiguous carrier aggregation, transmit OFF power is measured as the mean power per component
carrier.
For UE with multiple transmit antennas, transmit OFF power is measured as the mean power at each transmit
connector.
- UE output power higher than Transmit OFF power -50 dBm (as defined in TS 36.101 [5]) means uplink signal
- UE output power equal to or less than Transmit OFF power -50 dBm (as defined in TS 36.101 [5]) means no
uplink signal.
A.7.3.1 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync
A.7.3.1.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN FDD radio link
monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.1.1-1, A.7.3.1.1-2 and A.7.3.1.1-3 below. There is one cell (cell 1), which
is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively. Figure A.7.3.1.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and
in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 932 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.1.1-1: General test parameters for E-UTRAN FDD out-of-sync testing
Parameter Unit Value Comment
Test 1 Test 2 Test 3 Test 4
PCFICH/PDCCH/PHICH R.6 FDD R.7 FDD R.6 FDD R.7 FDD As specified in
parameters section A.3.1.2.1.
None of the PDCCH
are intended for the
UE under test
OCNG parameters OP.2 FDD OP.2 FDD OP.2 FDD OP.2 FDD As specified in
section A.3.2.1.2.
Active cell Cell 1 Cell 1 Cell 1 Cell 1 Cell 1 is on E-UTRA
RF channel number 1
CP length Normal Normal Normal Normal
E-UTRA RF Channel Number 1 1 1 1 One E-UTRA FDD
carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10 10 10 10
(BW channel)
Correlation Matrix and Antenna 1x2 2x2 1x2 Low 2x2 Low Correlation Matrix
Configuration and Antenna
Configuration are
defined in TS 36.101
[5] Annex B.2.3.2
DCI format 1A 1A 1A 1A As defined in section
5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 2 2 2 Out of sync threshold
parameters Control OFDM Qout and the
(Note 1) symbols corresponding
Aggregation CCE 8 8 8 8 hypothetical
level PDCCH/PCFICH
ρA, ρB 0 -3 0 -3 transmission
Ratio of PDCCH dB 4 1 4 1 parameters are as
to RS EPRE specified in section
Ratio of PCFICH dB 4 1 4 1 7.6.1 and Table
to RS EPRE 7.6.1-1 respectively.
DRX OFF OFF OFF OFF
Layer 3 filtering Enabled Enabled Enabled Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 0 0 0 T310 is disabled
T311 timer ms 1000 1000 1000 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 PUCCH 1-0 PUCCH 1-0 PUCCH 1-0 As defined in table
7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 2 2 2 Minimum CQI
reporting periodicity
Propagation channel AWGN AWGN ETU 70 Hz ETU 70 Hz .
T1 s 1 1 1 1
T2 s 0.4 0.4 0.4 0.4
T3 s 0.5 0.5 0.5 0.5
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 933 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.1.1-2: Cell specific test parameters for E-UTRAN FDD (cell # 1) for out-of-sync radio link
monitoring tests # 1 and # 2
Parameter Unit Test 1 Test 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Antenna 1x2 2x2
Configuration
OCNG Pattern
defined in A.3.2.1 OP.2 FDD OP.2 FDD
(FDD)
ρA, ρB 0 -3
PCFICH_RB dB 4 1
PDCCH_RA dB 4 1
PDCCH_RB dB 4 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
SNR Note 6,7 dB -4.7 -9.5 -13.5 -4.7 -9.5 -13.5
N oc dBm/15 -98 -98
kHz
Propagation condition AWGN AWGN
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3
respectively in figure A.7.3.1.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 934 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.1.1-3: Cell specific test parameters for E-UTRAN FDD (cell # 1) for out-of-sync radio link
monitoring tests # 3 and # 4
Parameter Unit Test 3 Test 4
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 1x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.1 OP.2 FDD OP.2 FDD
(FDD)
ρA, ρB 0 -3
PCFICH_RB dB 4 1
PDCCH_RA dB 4 1
PDCCH_RB dB 4 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
SNR Note 6,7 dB -1.4 -5.5 -11.5 -2.3 -6.2 -12.2
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 70 Hz ETU 70 Hz
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3
respectively in figure A.7.3.1.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 935 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.1.1-1 SNR variation for out-of-sync testing
A.7.3.1.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.2 E-UTRAN FDD Radio Link Monitoring Test for In-sync
A.7.3.2.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN FDD radio link
monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.2.1-1 and A.7.3.2.1-2 below. There is one cell (cell 1), which is the active
cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5
respectively. Figure A.7.3.2.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and
in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 936 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.2.1-1: General test parameters for E-UTRAN FDD in-sync testing
Parameter Unit Value Comment
Test 1 Test 2
PCFICH/PDCCH/PHICH R.6 FDD R.7 FDD As specified in
parameters clause A.3.1.2.1.
None of the PDCCH
are intended for the UE
under test
OCNG parameters OP.2 FDD OP.2 FDD As specified in
clause A.3.2.1.2.
Active cell Cell 1 Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal Normal
E-UTRA RF Channel Number 1 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10
(BWchannel)
Correlation Matrix and Antenna 1x2 Low 2x2 Low Correlation Matrix and
Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
DCI format 1C 1C As defined in
clause 5.3.3.1.4 in TS
In sync 36.212
transmissio
n Number of Control 2 2 In sync threshold Qin and
parameters OFDM symbols the corresponding
(Note 1) hypothetical
Aggregation level CCE 4 4 PDCCH/PCFICH
transmission parameters
are as specified in
ρA, ρB 0 -3 clause and Table 7.6.1-2
respectively.
Ratio of PDCCH 0 -3
to RS EPRE
Ratio of PCFICH 4 1
to RS EPRE
DCI format 1A 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmissio
n Number of Control 2 2 Out of sync threshold Qout
parameters OFDM symbols and the corresponding
(Note 1) hypothetical
Aggregation level CCE 8 8 PDCCH/PCFICH
transmission parameters
are as specified in
ρA, ρB 0 -3 clause 7.6.1 and Table
7.6.1-1 respectively.
Ratio of PDCCH dB 4 1
to RS EPRE
Ratio of PCFICH dB 4 1
to RS EPRE
DRX OFF OFF
Layer 3 filtering Enabled Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 2000 T310 is enabled
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 937 ETSI TS 136 133 V14.3.0 (2017-04)
T311 timer ms 1000 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 PUCCH 1-0 As defined in table 7.2.2-1
in TS 36.213.
CQI reporting periodicity ms 2 2 Minimum CQI reporting
periodicity
Propagation channel ETU 70 Hz ETU 70 Hz
T1 s 0.5 0.5
T2 s 0.4 0.4
T3 s 1.46 1.46
T4 s 0.4 0.4
T5 s 1 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
Table A.7.3.2.1-2: Cell specific test parameters for E-UTRAN FDD (cell # 1) for in-sync radio link
monitoring tests # 1 and # 2
Parameter Unit Test 1 Test 2
T1 T2 T3 T4 T5 T1 T2 T3 T4 T5
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 1x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.1 OP.2 FDD OP.2 FDD
(FDD)
ρA, ρB 0 -3
PCFICH_RB dB 4 1
PDCCH_RA dB 0 -3
PDCCH_RB dB 0 -3
PBCH_RA dB `
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 938 ETSI TS 136 133 V14.3.0 (2017-04)
SNR Note 6,7 dB -1.4 -5.5 -11.5 -6.4 -1.4 -2.3 -6.2 -12.2 -7.3 -2.3
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 70 Hz ETU 70 Hz
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5
respectively in figure A.7.3.2.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a UE
which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section A.3.8.1.
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.2.1-1 SNR variation for in-sync testing
A.7.3.2.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.3 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync
A.7.3.3.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN TDD radio link
monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.3.1-1, A.7.3.3.1-2 and A.7.3.3.1-3 below. There is one cell (cell 1), which
is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively. Figure A.7.3.3.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and
in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 939 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.3.1-1: General test parameters for E-UTRAN TDD out-of-sync testing
Parameter Unit Value Comment
Test 1 Test 2 Test 3 Test 4
PCFICH/PDCCH/PHICH R.6 TDD R.7 TDD R.6 TDD R.7 TDD As specified in
parameters clause A.3.1.2.2.
None of the PDCCH
are intended for the UE
under test
OCNG parameters OP.2 TDD OP.2 TDD OP.2 TDD OP.2 TDD As specified in
clause A.3.2.2.2.
Active cell Cell 1 Cell 1 Cell 1 Cell 1 Cell 1 is on E-UTRA
RF channel number 1
CP length Normal Normal Normal Normal
E-UTRA RF Channel Number 1 1 1 1 One E-UTRA TDD
carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10 10 10 10
(BW channel)
Correlation Matrix and Antenna 1x2 2x2 1x2 Low 2x2 Low Correlation Matrix and
Configuration Antenna Configuration
are defined in TS
36.101 [5] Annex
B.2.3.2
DCI format 1A 1A 1A 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmissio Number of 2 2 2 2 Out of sync threshold
n Control OFDM Qout and the
parameters symbols corresponding
(Note 1) Aggregation CCE 8 8 8 8 hypothetical
level PDCCH/PCFICH
ρA, ρB 0 -3 0 -3 transmission
Ratio of PDCCH dB 4 1 4 1 parameters are as
to RS EPRE specified in
Ratio of dB 4 1 4 1 clause 7.6.1 and Table
PCFICH to RS 7.6.1-1 respectively.
EPRE
DRX OFF OFF OFF OFF
Layer 3 filtering Enabled Enabled Enabled Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 0 0 0 T310 is disabled
T311 timer ms 1000 1000 1000 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 PUCCH 1-0 PUCCH 1-0 PUCCH 1-0 As defined in table
7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 1 1 1 Minimum CQI reporting
periodicity
Propagation channel AWGN AWGN ETU 70 Hz ETU 70 Hz .
T1 s 1 1 1 1
T2 s 0.4 0.4 0.4 0.4
T3 s 0.5 0.5 0.5 0.5
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 940 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.3.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for out-of-sync radio link
monitoring tests # 1 and # 2
Parameter Unit Test 1 Test 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Antenna 1x2 2x2
Configuration
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB 0 -3
PCFICH_RB dB 4 1
PDCCH_RA dB 4 1
PDCCH_RB dB 4 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 3 dB
OCNG_RBNote 3 dB
SNR Note 8,9 dB -5.1 -9.1 -13.1 -5.2 -9.2 -13.2
N oc dBm/15 -98 -98
kHz
Propagation condition AWGN AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 8: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3 respectively in figure
A.7.3.3.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 941 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.3.1-3: Cell specific test parameters for E-UTRAN TDD (cell # 1) for out-of-sync radio link
monitoring tests # 3 and # 4
Parameter Unit Test 3 Test 4
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 1x2 Low 2x2 Low
and Antenna
Configuration
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB 0 -3
PCFICH_RB dB 4 1
PDCCH_RA dB 4 1
PDCCH_RB dB 4 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 3 dB
OCNG_RBNote 3 dB
SNR Note 8 dB -1.4 -5.3 -11.3 -2.3 -5.9 -11.9
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 70 Hz ETU 70 Hz
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 8: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3 respectively in figure
A.7.3.3.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 942 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.3.1-1. SNR variation for out-of-sync testing
A.7.3.3.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all uplink subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of the time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.4 E-UTRAN TDD Radio Link Monitoring Test for In-sync
A.7.3.4.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN TDD radio link
monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.4.1-1 and A.7.3.4.1-2 below. There is one cell (cell 1), which is the active
cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5
respectively. Figure A.7.3.4.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and
in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 943 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.4.1-1: General test parameters for E-UTRAN TDD in-sync testing
Parameter Unit Value Comment
Test 1 Test 2
PCFICH/PDCCH/PHICH R.6 TDD R.7 TDD As specified in
parameters clause A.3.1.2.2.
None of the PDCCH
are intended for the UE
under test
OCNG parameters OP.2 TDD OP.2 TDD As specified in
clause A.3.2.2.2.
Active cell Cell 1 Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal Normal
E-UTRA RF Channel Number 1 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10
(BWchannel)
Correlation Matrix and Antenna 1x2 Low 2x2 Low Correlation Matrix and
Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
DCI format 1C 1C As defined in
clause 5.3.3.1.4 in TS
In sync 36.212
transmissio
n Number of Control 2 2 In sync threshold Qin and
parameters OFDM symbols the corresponding
(Note 1) hypothetical
Aggregation level CCE 4 4 PDCCH/PCFICH
transmission parameters
are as specified in
ρA, ρB 0 -3 clause and Table 7.6.1-2
respectively.
Ratio of PDCCH 0 -3
to RS EPRE
Ratio of PCFICH 4 1
to RS EPRE
DCI format 1A 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmissio
n Number of Control 2 2 Out of sync threshold Qout
parameters OFDM symbols and the corresponding
(Note 1) hypothetical
Aggregation level CCE 8 8 PDCCH/PCFICH
transmission parameters
are as specified in
ρA, ρB 0 -3 clause 7.6.1 and Table
7.6.1-1 respectively.
Ratio of PDCCH dB 4 1
to RS EPRE
Ratio of PCFICH dB 4 1
to RS EPRE
DRX OFF OFF
Layer 3 filtering Enabled Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 2000 T310 is enabled
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 944 ETSI TS 136 133 V14.3.0 (2017-04)
T311 timer ms 1000 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 PUCCH 1-0 As defined in table 7.2.2-1
in TS 36.213.
CQI reporting periodicity ms 1 1 Minimum CQI reporting
periodicity
Propagation channel ETU 70 Hz ETU 70 Hz
T1 s 0.5 0.5
T2 s 0.4 0.4
T3 s 1.46 1.46
T4 s 0.4 0.4
T5 s 1 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
Table A.7.3.4.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for in-sync radio link
monitoring tests # 1 and # 2
Parameter Unit Test 1 Test 2
T1 T2 T3 T4 T5 T1 T2 T3 T4 T5
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 1x2 Low 2x2 Low
and Antenna
Configuration
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB 0 -3
PCFICH_RB dB 4 1
PDCCH_RA dB 0 -3
PDCCH_RB dB 0 -3
PBCH_RA dB `
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 3 dB
OCNG_RBNote 3 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 945 ETSI TS 136 133 V14.3.0 (2017-04)
SNR Note 8,9 dB -1.4 -5.3 -11.3 -6.4 -1.4 -2.3 -5.9 -11.9 -7.3 -2.3
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 70 Hz ETU 70 Hz
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5
respectively in figure A.7.3.4.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a UE
which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section A.3.8.1.
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.4.1-1. SNR variation for in-sync testing
A.7.3.4.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all uplink subframes configured for CQI transmission according to the configured CQI mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.5 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync in DRX
A.7.3.5.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-UTRAN FDD
radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.5.1-1, A.7.3.5.1-2, A.7.3.5.1-3 and A.7.3.5.1-4. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.5.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms. In the test, DRX
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 946 ETSI TS 136 133 V14.3.0 (2017-04)
configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and to send
periodic CQI during the period when On-duration timer is running. Time alignment timers shall be set to “infinity” so
that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 947 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.5.1-1: General test parameters for E-UTRAN FDD out-of-sync tests in DRX
Parameter Unit Value Comment
Test 1 Test 2
PCFICH/PDCCH/PHICH R.7 FDD R.6 FDD As specified in
parameters clause A.3.1.2.1.
None of the PDCCH are
intended for the UE under
test
OCNG parameters OP.2 FDD OP.2 FDD As specified in
clause A.3.2.1.2.
Active cell Cell 1 Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal Normal
E-UTRA RF Channel Number 1 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10
(BWchannel)
Correlation Matrix and 2x2 Low 1x2 Correlation Matrix and
Antenna Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
DCI format 1A 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 2 Out of sync threshold Qout
parameters Control OFDM and the corresponding
(Note 1) symbols hypothetical
Aggregation CCE 8 8 PDCCH/PCFICH
level transmission parameters
ρA, ρB -3 0 are as specified in
Ratio of dB 1 4 clause 7.6.1 and Table
PDCCH to RS 7.6.1-1 respectively.
EPRE
Ratio of dB 1 4
PCFICH to RS
EPRE
DRX cycle ms 40 1280 See Table A.7.3.5.1-3
Layer 3 filtering Enabled Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 0 T310 is disabled
T311 timer ms 1000 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 PUCCH 1- As defined in table 7.2.2-1
0 in TS 36.213.
CQI reporting periodicity ms 2 2 Minimum CQI reporting
periodicity
Propagation channel ETU 70 Hz AWGN .
T1 s 4 32
T2 s 1.6 12.8
T3 s 1.8 13
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not
be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 948 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.5.1-2: Cell specific test parameters for E-UTRAN FDD (cell # 1) for out-of-sync radio link
monitoring tests # 1 and # 2 in DRX
Parameter Unit Test 1 Test 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 1x2
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.1 OP.2 FDD OP.2 FDD
(FDD)
ρA, ρB -3 0
PCFICH_RB dB 1 4
PDCCH_RA dB 1 4
PDCCH_RB dB 1 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
-3 0
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,7 dB -2.3 -6.2 -12.2 -4.7 -9.5 -13.5
dBm/15 kHz -98 -98
N oc
Propagation condition ETU 70 Hz AWGN
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3
respectively in figure A.7.3.5.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
Table A.7.3.5.1-3: DRX-Configuration for E-UTRAN FDD out-of-sync tests
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf2 psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 949 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.5.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD out-of-sync testing
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity infinity
36.331
For further information see clause 6.3.2
sr-ConfigIndex 0 0 in TS 36.331 and section10.1 in TS
36.213.
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.5.1-1 SNR variation for out-of-sync testing in DRX
A.7.3.5.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
In test 1 and test 2 during the period from time point A to time point B the UE shall transmit uplink signal at least once
every DRX cycle, in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode
(PUCCH 1-0).
In test 1 the UE shall stop transmitting uplink signal no later than time point C (duration D1 = 900 ms after the start of
time duration T3).
In test 2 the UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6500 ms after the start of
time duration T3.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 950 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.6 E-UTRAN FDD Radio Link Monitoring Test for In-sync in DRX
A.7.3.6.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-UTRAN FDD
radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.6.1-1, A.7.3.6.1-2, A.7.3.6.1-3 and A.7.3.6.1-4. There is one cell (cell 1),
which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3,
T4 and T5 respectively. Figure A.7.3.6.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The
UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms. In the test,
DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and
to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be set to
“infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 951 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.6.1-1: General test parameters for E-UTRAN FDD in-sync test in DRX
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH parameters R.6 FDD As specified in clause A.3.1.2.1.
None of the PDCCH are
intended for the UE under test
OCNG parameters OP.2 FDD As specified in clause A.3.2.1.2.
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Antenna Configuration 1x2
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of 2 In sync threshold Qin and the
transmission Control OFDM corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CC 4 parameters are as specified in
level E clause and Table 7.6.1-2
ρA, ρB 0 respectively.
Ratio of PDCCH 0
to RS EPRE
Ratio of 4
PCFICH to RS
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of sync Number of 2 Out of sync threshold Qout and
transmission Control OFDM the corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CC 8 parameters are as specified in
level E clause 7.6.1 and Table 7.6.1-1
ρA, ρB 0 respectively.
Ratio of PDCCH dB 4
to RS EPRE
Ratio of dB 4
PCFICH to RS
EPRE
DRX cycle ms 40 See Table A.7.3.6.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table 7.2.2-1 in
0 TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
Propagation channel AWGN
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 952 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.6.1-2: Cell specific test parameters for E-UTRAN FDD (cell # 1) for in-sync radio link
monitoring test # 1 in DRX
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
Antenna Configuration 1x2
OCNG Pattern defined in
A.3.2.1 (FDD) OP.2 FDD
ρA, ρB 0
PCFICH_RB dB 4
PDCCH_RA dB 0
PDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,7 dB -4.7 -9.5 -13.5 -8.7 -4.7
N oc dBm/15 -98
kHz
Propagation condition AWGN
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.6.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For
testing of a UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as
specified in section A.3.8.1.
Table A.7.3.6.1-3: DRX-Configuration for E-UTRAN FDD out-of-sync tests
Comment
Field Value
onDurationTimer psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
Table A.7.3.6.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD out-of-sync testing
Comment
Field Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see clause 6.3.2
sr-ConfigIndex 0 in TS 36.331 and section10.1 in TS
36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 953 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.6.1-1 SNR variation for in-sync testing in DRX
A.7.3.6.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.7 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync in DRX
A.7.3.7.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-UTRAN TDD
radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.7.1-1, A.7.3.7.1-2, A.7.3.7.1-3 and A.7.3.7.1-4. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.7.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms. In the test, DRX
configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and to send
periodic CQI during the period when On-duration timer is running. Time alignment timers shall be set to “infinity” so
that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 954 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.7.1-1: General test parameters for E-UTRAN TDD out-of-sync tests in DRX
Parameter Unit Value Comment
Test 1 Test 2
PCFICH/PDCCH/PHICH R.7 TDD R.6 TDD As specified in
parameters clause A.3.1.2.2.
None of the PDCCH are
intended for the UE under
test
OCNG parameters OP.2 TDD OP.2 TDD As specified in
clause A.3.2.2.2.
Active cell Cell 1 Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal Normal
E-UTRA RF Channel Number 1 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10
(BWchannel)
Correlation Matrix and 2x2 Low 1x2 Correlation Matrix and
Antenna Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
DCI format 1A 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 2 Out of sync threshold Qout
parameters Control OFDM and the corresponding
(Note 1) symbols hypothetical
Aggregation CCE 8 8 PDCCH/PCFICH
level transmission parameters
ρA, ρB -3 0 are as specified in
Ratio of dB 1 4 clause 7.6.1 and Table
PDCCH to RS 7.6.1-1 respectively.
EPRE
Ratio of dB 1 4
PCFICH to RS
EPRE
DRX cycle ms 40 1280 See Table A.7.3.7.1-3
Layer 3 filtering Enabled Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 0 T310 is disabled
T311 timer ms 1000 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 PUCCH 1- As defined in table 7.2.2-1
0 in TS 36.213.
CQI reporting periodicity ms 1 1 Minimum CQI reporting
periodicity
Propagation channel ETU 70 Hz AWGN .
T1 s 4 32
T2 s 1.6 12.8
T3 s 1.8 13
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not
be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 955 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.7.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for out-of-sync radio link
monitoring tests # 1 and # 2 in DRX
Parameter Unit Test 1 Test 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 1x2
and Antenna
Configuration
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB -3 0
PCFICH_RB dB 1 4
PDCCH_RA dB 1 4
PDCCH_RB dB 1 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
SNR Note 8,9 dB -2.3 -5.9 -11.9 -5.1 -9.1 -13.1
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 70 Hz AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 8: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3
respectively in figure A.7.3.7.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
Table A.7.3.7.1-3: DRX-Configuration for E-UTRAN TDD out-of-sync tests
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf2 psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 956 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.7.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD out-of-sync testing
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity infinity
36.331
For further information see clause 6.3.2
sr-ConfigIndex 2 2 in TS 36.331 and section10.1 in TS
36.213.
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.7.1-1 SNR variation for out-of-sync testing in DRX
A.7.3.7.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
In test 1 and test 2 during the period from time point A to time point B the UE shall transmit uplink signal at least once
every DRX cycle, in the On-duration part of the cycle in the uplink subframe according to the configured CQI reporting
mode (PUCCH 1-0).
In test 1 the UE shall stop transmitting uplink signal no later than time point C (D1 = 900 ms after the start of time
duration T3).
In test 2 the UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6500 ms after the start of
time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.8 E-UTRAN TDD Radio Link Monitoring Test for In-sync in DRX
A.7.3.8.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-UTRAN TDD
radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.8.1-1, A.7.3.8.1-2, A.7.3.8.1-3 and A.7.3.8.1-4. There is one cell (cell 1),
which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3,
T4 and T5 respectively. Figure A.7.3.8.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The
UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms. In the test,
DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 957 ETSI TS 136 133 V14.3.0 (2017-04)
to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be set to
“infinity” so that UL timing alignment is maintained during the test.
Table A.7.3.8.1-1: General test parameters for E-UTRAN TDD in-sync test in DRX
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH parameters R.6 TDD As specified in clause A.3.1.2.2.
None of the PDCCH are
intended for the UE under test
OCNG parameters OP.2 TDD As specified in clause A.3.2.2.2.
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Antenna Configuration 1x2
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of 2 In sync threshold Qin and the
transmission Control OFDM corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CCE 4 parameters are as specified in
level clause and Table 7.6.1-2
ρA, ρB 0 respectively.
Ratio of PDCCH 0
to RS EPRE
Ratio of 4
PCFICH to RS
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of sync Number of 2 Out of sync threshold Qout and
transmission Control OFDM the corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CCE 8 parameters are as specified in
level clause 7.6.1 and Table 7.6.1-1
ρA, ρB 0 respectively.
Ratio of PDCCH dB 4
to RS EPRE
Ratio of dB 4
PCFICH to RS
EPRE
DRX cycle ms 40 See Table A.7.3.8.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
Propagation channel AWGN
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 958 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.8.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for in-sync radio link
monitoring test # 1 in DRX
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
Antenna Configuration 1x2
Special subframe 6
configurationNote1
Uplink-downlink 1
configurationNote2
OCNG Pattern defined in
A.3.2.2 (TDD) OP.2 TDD
ρA, ρB 0
PCFICH_RB dB 4
PDCCH_RA dB 0
PDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
SNR Note 8,9 dB -5.1 -9.1 -13.1 -9.1 -5.1
N oc dBm/15 -98
kHz
Propagation condition AWGN
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.8.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For
testing of a UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as
specified in section A.3.8.1.
Table A.7.3.8.1-3: DRX-Configuration for E-UTRAN TDD out-of-sync tests
Comment
Field Value
onDurationTimer psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 959 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.8.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD out-of-sync testing
Comment
Field Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see clause 6.3.2
sr-ConfigIndex 2 in TS 36.331 and section10.1 in TS
36.213.
Figure A.7.3.8.1-1 SNR variation for in-sync testing in DRX
A.7.3.8.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the uplink subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.9 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync under
Time Domain Measurement Resource Restriction and Non-MBSFN
ABS
A.7.3.9.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN FDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.9.1-1 and A.7.3.9.1-2 below. The test consists of three successive time
periods, with time duration of T1, T2 and T3 respectively. Figure A.7.3.9.1-1 shows the variation of the downlink SNR
in the active cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be
fully synchronized to cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a
reporting periodicity of 2 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 960 ETSI TS 136 133 V14.3.0 (2017-04)
Non-MBSFN ABS pattern is configured in the aggressor Cell 2 in this test. The UE is configured by higher layers with
a time domain measurement restriction pattern for performing serving cell measurements. The patterns shall be
configured prior to the start of T1.
Table A.7.3.9.1-1: General test parameters for E-UTRAN FDD out-of-sync testing under time domain
measurement resource restriction with non-MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.9.FDD As specified in clause A.3.1.2.1.
parameters None of the PDCCH are intended for the UE
under test
OCNG parameters OP.6 FDD As specified in clause A.3.2.1.6.
Serving cell (PCell) Cell 1 Cell 1 is on E-UTRA RF channel number 1
Neighbor cell Cell 2 Aggressor cell on E-UTRA RF channel number
1
Neighbor cell ABS Non-MBSFN ABS As defined in Table A.3.4.1.2-1
configuration
CP length Normal
E-UTRA RF Channel 1 One E-UTRA FDD carrier frequency is used.
Number
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Correlation Matrix and 2x2 Low Correlation Matrix and Antenna Configuration
Antenna Configuration are defined in TS 36.101 [5] Annex B.2.3.2
Out of sync DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
transmission Number of 3 Out of sync threshold Qout and the
parameters Control corresponding hypothetical PDCCH/PCFICH
(Note 1) OFDM transmission parameters are as specified in
symbols clause 7.6.1 and Table 7.6.1-1 respectively.
Aggregation CCE 8
level
ρA, ρB -3
Ratio of dB 1
PDCCH to
RS EPRE
Ratio of dB 1
PCFICH to
RS EPRE
DRX OFF
Layer 3 filtering Enabled Counters:: N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
Time offset between cells 3 μs Synchronous cells
T1 s 1
T2 s 0.4
T3 s 0.5
Physical cell ID PCI (PCIcell1-PCIcell2 )mod3 !=
Cell IDs are chosen such that CRS from cells 1
0 and 2 do not overlap in frequency
ABS pattern ‘10000000100000001000 FDD ABS Pattern Info IE, as defined in TS
00001000000010000000’ 36.423 [28], clause 9.2.54. Configured in Cell 2.
The first/leftmost bit corresponds to the PCell
subframe #0 of the radio frame satisfying SFN
mod x = 0, where x is the size of the bit string
(40) divided by 10. No MBSFN subframes are
cofigured in the ABS subframes.
Time domain measurement ‘10000000100000001000 Time domain measurement resource restriction
resource restriction pattern 00001000000010000000’ pattern for serving cell measurement signalled
to the UE in message
measSubframePatternPCell-r10 as defined in
TS 36.331, clause 6.3.2.
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 961 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.9.1-2: Cell specific test parameters for E-UTRAN FDD for out-of-sync radio link
monitoring under time domain measurement resource restriction with non-MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.1.6 OP.6 FDD OP.6 FDD
(FDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB 1 channel powers defined in
PDCCH_RB dB 1 Table A.3.4.1.2-1.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,7 dB -1.3 -5.4 -12.4 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 30 Hz ETU 30 Hz
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal quality, signal-to-interference-plus-noise ratio, on the
CRS REs.
Note 6: The SNR in the restricted measurement subframes during time periods T1, T2 and T3 is
denoted as SNR1, SNR2 and SNR3 respectively in figure A.7.3. 9.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 962 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.9.1-1 SNR variation for out-of-sync testing
A.7.3.9.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.10 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync under
Time Domain Measurement Resource Restriction with Non-MBSFN
ABS
A.7.3.10.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN TDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.10.1-1 and A.7.3.10.1-2 below. There are two cells, cell 1 is the serving
cell and cell 2 is the neigbhor aggressor cell. The test consists of three successive time periods, with time duration of
T1, T2 and T3 respectively. Figure A.7.3.10.1-1 shows the variation of the downlink SNR in the active cell to emulate
out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1.
The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
Non-MBSFN ABS pattern is configured in Cell 2 in this test. The UE is configured by higher layers with a time domain
measurement restriction pattern for performing serving cell measurements. The patterns shall be configured prior to the
start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 963 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.10.1-1: General test parameters for E-UTRAN TDD out-of-sync testing under time domain
measurement resource restriction with non-MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.9 TDD As specified in clause A.3.1.2.2.
parameters None of the PDCCH are intended for the
UE under test
OCNG parameters OP.2 TDD As specified in clause A.3.2.2.2.
Serving cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
Neighbor cell Cell 2 Cell 2 is the aggressor cell on E-UTRA
RF channel number 1
Neighbor cell ABS Non-MBSFN ABS As defined in Table A.3.4.1.2-1
configuration
CP length Normal
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Correlation Matrix and 2x2 Low Correlation Matrix and Antenna
Antenna Configuration Configuration are defined in TS 36.101
[5] Annex B.2.3.2
DCI format 1A As defined in clause 5.3.3.1.3 in TS
36.212
Out of sync Number of 3 Out of sync threshold Qout and the
transmission Control OFDM corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CCE 8 parameters are as specified in
level clause 7.6.1 and Table 7.6.1-1
ρA, ρB -3 respectively.
Ratio of dB 1
PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
Physical cell ID PCI (PCIcell1-PCIcell2 )mod3 != Cell IDs are chosen such that CRS from
0 cells 1 and 2 do not overalp in
frequency.
ABS pattern 10000000001000000000 TDD ABS Pattern Info IE is configured
in Cell 2 as defined in clause 9.2.54 in
TS 36.423 [28].
The first/leftmost bit corresponds to the
subframe #0 of the radio frame
satisfying SFN mod x = 0, where x is the
size of the bit string (20) divided by 10.
No MBSFN subframes are cofigured in
the ABS subframes.
Time domain measurement 10000000001000000000 MeasSubframePattern IE is configured
resource restriction pattern in UE for serving cell measurement as
defined in clause 6.3.6 in TS 36.331.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting periodicity
Time offset between cells μs 3
Propagation channel ETU30
T1 s 1
T2 s 0.4
T3 s 0.5
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in
the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 964 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.10.1-2: Cell specific test parameters for E-UTRAN TDD for out-of-sync radio link
monitoring under time domain measurement resource restriction with non-MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB 1 channel powers defined in
PDCCH_RB dB 1 Table A.3.4.1.2-1.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 3 dB
OCNG_RBNote 3 dB
SNR Note 8,9 dB -1.3 -5.4 -12.4 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU30 ETU30
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 8: The SNR in time periods T1, T2 and T3 of active cell is denoted as SNR1, SNR2 and
SNR3 respectively in figure A.7.3.10.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 965 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.10.1-1 SNR variation in active cell for out-of-sync testing under time domain
measurement resource restriction with non-MBSFN ABS
A.7.3.10.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all uplink subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of the time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.11 E-UTRAN FDD Radio Link Monitoring Test for In-sync for Non-
MBSFN ABS
A.7.3.11.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN FDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.11.1-1 and A.7.3.11.1-2 below. There are two cells in the test: Cell 1 is
the Active cell and Cell 2 is the Neighbor cell. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.11.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms.
Non-MBSFN ABS pattern is configured in Cell 2 in this test. The UE is configured by higher layers with a time domain
measurement restriction pattern for performing serving cell measurements. The patterns shall be configured prior to the
start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 966 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.11.1-1: General test parameters for E-UTRAN FDD in-sync testing under time domain
measurement resource restriction
Parameter Uni Value Comment
t
PCFICH/PDCCH/PHICH R.9 FDD As specified in clause A.3.1.2.1.
parameters None of the PDCCH are
intended for the UE under test
OCNG parameters OP.6 FDD As specified in clause A.3.2.1.6.
Active cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
Neighbor cell Cell 2 Cell 2 is on E-UTRA RF channel
number 1; Cell 2 generates
interference over restricted
resources.
Neighbor cell ABS Non- As defined in Table A.3.4.1.2-2
configuration MBSFN
ABS
CP length Normal
E-UTRA RF Channel 1 One E-UTRA FDD carrier
Number frequency is used.
E-UTRA Channel Bandwidth MH 10
(BWchannel) z
Correlation Matrix and 2x2 Low Correlation Matrix and Antenna
Antenna Configuration Configuration are defined in TS
36.101 [5] Annex B.2.3.2
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of 3 In sync threshold Qin and the
transmissi Control OFDM corresponding hypothetical
on symbols PDCCH/PCFICH transmission
parameter Aggregation CC 4 parameters are as specified in
s for the level E clause and Table 7.6.1-2
active cell ρA, ρB -3 respectively.
(Note 1) Ratio of dB -3
PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of Number of 3 Out of sync threshold Qout and
sync Control OFDM the corresponding hypothetical
transmissi symbols PDCCH/PCFICH transmission
on Aggregation CC 8 parameters are as specified in
parameter level E clause 7.6.1 and Table 7.6.1-1
s for active ρA, ρB -3 respectively.
cell (Note Ratio of dB 1
1) PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table 7.2.2-1 in TS
0 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
Time offset between cells μs 3
Propagation channel ETU30
T1 s 0.5
T2 s 0.4
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 967 ETSI TS 136 133 V14.3.0 (2017-04)
T3 s 1.46
T4 s 0.4
T5 s 1
Physical cell ID PCI (PCIcell1- Cell IDs are chosen such that
PCIcell2 CRS from cells 1 and 2 do not
)mod3 != 0 overalp in frequency
ABS pattern ‘100000001 FDD ABS Pattern Info IE, as
000000010 defined in TS 36.423 [28],
000000100 clause 9.2.54. Configured in Cell
000001000 2.
0000’ The first/leftmost bit corresponds
to the PCell subframe #0 of the
radio frame satisfying SFN mod
x = 0, where x is the size of the
bit string (40) divided by 10.
No MBSFN subframes are
cofigured in the ABS subframes.
Time domain measurement ‘100000001 Time domain measurement
resource restriction pattern 000000010 resource restriction pattern for
000000100 serving cell measurement
000001000 signalled to the UE in message
0000’ measSubframePatternPCell-r10
as defined in TS 36.331, clause
6.3.2.
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync
transmission parameters need not be included in the Reference
Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 968 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.11.1-2: Cell specific test parameters for E-UTRAN FDD for in-sync radio link monitoring
under time domain measurement resource restriction
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T4 T5 T1 T2 T3 T4 T5
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
PCFICH/PDCCH/PHI R.9 FDD R.9 FDD
CH parameters
Number of Control 3 3
OFDM symbols
OCNG Pattern
defined in A.3.2.1.6 OP.6 FDD OP.6 FDD
(FDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB -3 channel powers defined in Table
PDCCH_RB dB -3 A.3.4.1.2-2.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
SNR Note 6,7 dB -1.3 -5.4 -12.4 -7.3 -1.3 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU30 ETU30
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 of the active cell is denoted as SNR1, SNR2, SNR3, SNR4
and SNR5 respectively in figure A.7.3.11.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a
UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 969 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.11.1-1 SNR variation in the active cell for in-sync testing under time domain
measurement resource restriction
A.7.3.11.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.12 E-UTRAN TDD Radio Link Monitoring Test for In-sync for Non-
MBSFN ABS
A.7.3.12.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN TDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.12.1-1 and A.7.3.12.1-2 below. There are two cells in the test: Cell 1 is
the Active cell and Cell 2 is the Neighbor cell. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.12.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
Non-MBSFN ABS pattern is configured in the aggressor Cell 2 in this test. The UE is configured by higher layers with
a time domain measurement restriction pattern for performing serving cell measurements. The patterns shall be
configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 970 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.12.1-1: General test parameters for E-UTRAN TDD in-sync testing under time domain
measurement resource restriction
Parameter Uni Value Comment
t
PCFICH/PDCCH/PHICH R.9 TDD As specified in
parameters clause A.3.1.2.2.
None of the PDCCH are
intended for the UE under test
OCNG parameters OP.2 TDD As specified in
clause A.3.2.2.2.
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
Neighbor cell Cell 2 Cell 2 is on E-UTRA RF
channel number 1; Cell 2
generates interference over
restricted resources.
Neighbor cell ABS Non-MBSFN As defined in Table A.3.4.1.2-
configuration ABS 2
CP length Normal
E-UTRA RF Channel 1 One E-UTRA TDD carrier
Number frequency is used.
E-UTRA Channel Bandwidth MH 10
(BWchannel) z
Correlation Matrix and 2x2 Low Correlation Matrix and
Antenna Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
DCI format 1C As defined in clause 5.3.3.1.4
in TS 36.212
In sync Number of 3 In sync threshold Qin and the
transmissi Control OFDM corresponding hypothetical
on symbols PDCCH/PCFICH transmission
parameter Aggregation CC 4 parameters are as specified in
s for the level E clause and Table 7.6.1-2
active cell ρA, ρB -3 respectively.
(Note 1) Ratio of dB -3
PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
DCI format 1A As defined in clause 5.3.3.1.3
in TS 36.212
Out of Number of 3 Out of sync threshold Qout
sync Control OFDM and the corresponding
transmissi symbols hypothetical PDCCH/PCFICH
on Aggregation CC 8 transmission parameters are
parameter level E as specified in clause 7.6.1
s for active ρA, ρB -3 and Table 7.6.1-1
cell (Note Ratio of dB 1 respectively.
1) PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
Time offset between cells μs 3
Propagation channel ETU30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 971 ETSI TS 136 133 V14.3.0 (2017-04)
T1 s 0.5
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Physical cell ID PCI (PCIcell1- Cell IDs are chosen such that
PCIcell2 CRS from cells 1 and 2 do not
)mod3 != 0 overalp in frequency
ABS pattern 1000000000 TDD ABS Pattern Info IE, as
1000000000 defined in TS 36.423 [28],
clause 9.2.54. Configured in
Cell 2. The first/leftmost bit
corresponds to the subframe
#0 of the radio frame
satisfying SFN mod x = 0,
where x is the size of the bit
string (20) divided by 10.
No MBSFN subframes are
cofigured in the ABS
subframes.
Time domain measurement 1000000000 Time domain measurement
resource restriction pattern 1000000000 resource restriction pattern for
serving cell measurement
signalled to the UE in
message
measSubframePatternPCell-
r10 as defined in TS 36.331,
clause 6.3.2. Configured in
Cell 1.
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync
transmission parameters need not be included in the Reference
Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 972 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.12.1-2: Cell specific test parameters for E-UTRAN TDD for in-sync radio link monitoring
under time domain measurement resource restriction
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T4 T5 T1 T2 T3 T4 T5
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
PCFICH/PDCCH/PHI R.9 TDD R.9 TDD
CH parameters
Number of Control 3 3
OFDM symbols
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB -3 channel powers defined in Table
PDCCH_RB dB -3 A.3.4.1.2-2.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 3 dB
OCNG_RBNote 3 dB
SNR Note 8,9 dB -1.3 -5.4 -12.4 -7.3 -1.3 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU30 ETU30
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2, T3, T4 and T5 of active cell is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.12.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a
UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 973 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.12.1-1 SNR variation in active cell for in-sync testing under time domain measurement
resource restriction
A.7.3.12.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all uplink subframes configured for CQI transmission according to the configured CQI mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.13 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync under
Time Domain Measurement Resource Restriction with MBSFN ABS
A.7.3.13.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN FDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.13.1-1 and A.7.3.13.1-2 below. The test consists of three successive time
periods, with time duration of T1, T2 and T3 respectively. Figure A.7.3.13.1-1 shows the variation of the downlink
SNR in the active cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall
be fully synchronized to Cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a
reporting periodicity of 2 ms.
MBSFN ABS pattern is configured in the aggressor Cell 2 in this test. The UE is configured by higher layers with a
time domain measurement restriction pattern for performing serving cell measurements. The patterns shall be
configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 974 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.13.1-1: General test parameters for E-UTRAN FDD out-of-sync testing under time domain
measurement resource restriction with MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.9.FDD As specified in clause A.3.1.2.1.
parameters None of the PDCCH are intended for the UE
under test
OCNG parameters OP.6 FDD for the serving As specified in clause A.3.2.1.6 and A.3.2.1.9
cell (Cell 1) respectively
OP.9 FDD for the
neighbour cell (Cell 2)
Serving cell (PCell) Cell 1 Cell 1 is on E-UTRA RF channel number 1
Neighbor cell Cell 2 Aggressor cell on E-UTRA RF channel number
1
Neighbor cell ABS MBSFN ABS As defined in Table A.3.4.2.2-1
configuration
CP length Normal
E-UTRA RF Channel 1 One E-UTRA FDD carrier frequency is used.
Number
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Correlation Matrix and 2x2 Low Correlation Matrix and Antenna Configuration
Antenna Configuration are defined in TS 36.101 [5] Annex B.2.3.2
Out of sync DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
transmission Number of 3 Out of sync threshold Qout and the
parameters Control corresponding hypothetical PDCCH/PCFICH
(Note 1) OFDM transmission parameters are as specified in
symbols clause 7.6.1 and Table 7.6.1-1 respectively.
Aggregation CCE 8
level
ρA, ρB -3
Ratio of dB 1
PDCCH to
RS EPRE
Ratio of dB 1
PCFICH to
RS EPRE
DRX OFF
Layer 3 filtering Enabled Counters:: N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
Time offset between cells 3 μs Synchronous cells
T1 s 1
T2 s 0.4
T3 s 0.5
Physical cell ID PCI (PCIcell1-PCIcell2 ) mod 3 = Cell IDs are chosen such that CRS from cells 1
0, PCIcell1 not equal to and 2 overlap in frequency
PCIcell2
ABS pattern ‘01000000100000001000 FDD ABS Pattern Info IE, as defined in TS
00000010000001000000’ 36.423 [28], clause 9.2.54. Configured in Cell 2.
The first/leftmost bit corresponds to the PCell
subframe #0 of the radio frame satisfying SFN
mod x = 0, where x is the size of the bit string
(40) divided by 10. MBSFN subframes are
cofigured in the ABS subframes.
Time domain measurement ‘01000000100000001000 Time domain measurement resource restriction
resource restriction pattern 00000010000001000000’ pattern for serving cell measurement signalled
to the UE in message measSubframePattern-
Serv-r10 as defined in TS 36.331, clause 6.3.2.
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 975 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.13.1-2: Cell specific test parameters for E-UTRAN FDD for out-of-sync radio link
monitoring under time domain measurement resource restriction with MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.1 OP.6 FDD OP.9 FDD
(FDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB 1 channel powers defined in
PDCCH_RB dB 1 Table A.3.4.2.2-1.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,7 dB -1.3 -5.4 -12.4 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 30 Hz ETU 30 Hz
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal quality, signal-to-interference-plus-noise ratio, on the
CRS REs.
Note 6: The SNR in the restricted measurement subframes during time periods T1, T2 and T3 is
denoted as SNR1, SNR2 and SNR3 respectively in figure A.7.3.13.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 976 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.13.1-1 SNR variation for out-of-sync testing
A.7.3.13.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.14 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync under
Time Domain Measurement Resource Restriction with MBSFN ABS
A.7.3.14.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN TDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.14.1-1 and A.7.3.14.1-2 below. The test consists of three successive time
periods, with time duration of T1, T2 and T3 respectively. Figure A.7.3.14.1-1 shows the variation of the downlink
SNR in the active cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall
be fully synchronized to Cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a
reporting periodicity of 2 ms.
MBSFN ABS pattern is configured in the aggressor Cell 2 in this test. The UE is configured by higher layers with a
time domain measurement restriction pattern for performing serving cell measurements. The patterns shall be
configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 977 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.14.1-1: General test parameters for E-UTRAN TDD out-of-sync testing under time domain
measurement resource restriction with MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.9.TDD As specified in clause A.3.1.2.1.
parameters None of the PDCCH are intended for the UE
under test
OCNG parameters OP.2 TDD for the serving As specified in clause A.3.2.2.2 and A.3.2.2.6
cell (Cell 1) respectively
OP.6 TDD for the
neighbour cell (Cell 2)
Serving cell (PCell) Cell 1 Cell 1 is on E-UTRA RF channel number 1
Neighbor cell Cell 2 Aggressor cell on E-UTRA RF channel number
1
Neighbor cell ABS MBSFN ABS As defined in Table A.3.4.2.2-1
configuration
CP length Normal
E-UTRA RF Channel 1 One E-UTRA FDD carrier frequency is used.
Number
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Correlation Matrix and 2x2 Low Correlation Matrix and Antenna Configuration
Antenna Configuration are defined in TS 36.101 [5] Annex B.2.3.2
Out of sync DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
transmission Number of 3 Out of sync threshold Qout and the
parameters Control corresponding hypothetical PDCCH/PCFICH
(Note 1) OFDM transmission parameters are as specified in
symbols clause 7.6.1 and Table 7.6.1-1 respectively.
Aggregation CCE 8
level
ρA, ρB -3
Ratio of dB 1
PDCCH to
RS EPRE
Ratio of dB 1
PCFICH to
RS EPRE
DRX OFF
Layer 3 filtering Enabled Counters:: N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting periodicity
Time offset between cells 3 μs Synchronous cells
T1 s 1
T2 s 0.4
T3 s 0.5
Physical cell ID PCI (PCIcell1-PCIcell2 ) mod 3 = Cell IDs are chosen such that CRS from cells 1
0, PCIcell1 not equal to and 2 overlap in frequency
PCIcell2
ABS pattern ‘00001000000000100000’ MBSFN ABS. TDD ABS Pattern Info IE, as
defined in TS 36.423 [28], clause 9.2.54.
Configured in Cell 2.
The first/leftmost bit corresponds to the PCell
subframe #0 of the radio frame satisfying SFN
mod x = 0, where x is the size of the bit string
(20) divided by 10. All ABS subframes are
MBSFN subframes.
Time domain measurement ‘00001000000000100000’ Time-domain measurement resource restriction
resource restriction pattern pattern for serving cell measurements signalled
to the UE in message measSubframePattern-
Serv-r10 as defined in TS 36.331, clause 6.3.2.
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 978 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.14.1-2: Cell specific test parameters for E-UTRAN TDD for out-of-sync radio link
monitoring under time domain measurement resource restriction with MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.6 TDD
(TDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB 1 channel powers defined in
PDCCH_RB dB 1 Table A.3.4.2.2-1.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
SNR Note 7,8,9 dB -1.3 -5.4 -12.4 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU 30 Hz ETU 30 Hz
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink subframe configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal quality, signal-to-interference-plus-noise ratio, on the
CRS REs.
Note 8: The SNR in the restricted measurement subframes during time periods T1, T2 and T3 is
denoted as SNR1, SNR2 and SNR3 respectively in Figure A.7.3.14.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band.
For testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as
specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 979 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.14.1-1 SNR variation for out-of-sync testing
A.7.3.14.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.15 E-UTRAN FDD Radio Link Monitoring Test for In-sync under Time
Domain Measurement Resource Restriction with MBSFN ABS
A.7.3.15.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN FDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.15.1-1 and A.7.3.15.1-2 below. There are two cells, cell 1 is the serving
cell and cell 2 is the neighbour aggressor cell. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.15.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms.
MBSFN ABS pattern is configured in Cell 2 in this test. The UE is configured by higher layers with a time domain
measurement restriction pattern for performing serving cell measurements. The patterns shall be configured prior to the
start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 980 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.15.1-1: General test parameters for E-UTRAN FDD in-sync testing under time domain
measurement resource restriction with MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.9 FDD As specified in clause A.3.1.2.1.
parameters None of the PDCCH are intended
for the UE under test
Serving cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
Neighbour cell Cell 2 Cell 2 is the aggressor cell on E-
UTRA RF channel number 1
Neighbour cell ABS MBSFN ABS As defined in Table A.3.4.2.2-2
configuration
OCNG parameters for Cell 1 OP.6 FDD As specified in clause A.3.2.1.6.
OCNG parameters for Cell 2 OP.9 FDD As specified in clause A.3.2.1.9.
CP length Normal
Neighbor cell ABS MBSFN ABS
configuration
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
Correlation Matrix and Antenna 2x2 Low Correlation Matrix and Antenna
Configuration Configuration are defined in TS
36.101 [5] Annex B.2.3.2
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of 3 In sync threshold Qin and the
transmission Control OFDM corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CCE 4 parameters are as specified in
level clause and Table 7.6.1-2
ρA, ρB -3 respectively.
Ratio of dB -3
PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of sync Number of 3 Out of sync threshold Qout and the
transmission Control OFDM corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CCE 8 parameters are as specified in
level clause 7.6.1 and Table 7.6.1-1
ρA, ρB -3 respectively.
Ratio of dB 1
PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
Physical cell ID PCI (PCIcell1-PCIcell2 ) mod 3 = Cell IDs are chosen such that CRS
0, PCIcell1 not equal to from cells 1 and 2 overlap in
PCIcell2 frequency.
ABS pattern 010000001000000010000 FDD ABS Pattern Info IE is
0000010000001000000 configured in Cell 2 as defined in
clause 9.2.54 in TS 36.423 [28].
The first/leftmost bit corresponds to
the subframe #0 of the radio frame
satisfying SFN mod x = 0, where x
is the size of the bit string (40)
divided by 10.
All ABS subframes are MBSFN
subframes.
Time domain measurement 010000001000000010000 MeasSubframePattern IE is
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 981 ETSI TS 136 133 V14.3.0 (2017-04)
resource restriction pattern 0000010000001000000 configured in UE for serving cell
measurement as defined in
clause 6.3.6 in TS 36.331.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS
36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
Time offset between cells μs 3
Propagation channel ETU30
T1 s 0.5
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
Table A.7.3.15.1-2: Cell specific test parameters for E-UTRAN FDD for in-sync radio link monitoring
under time domain measurement resource restriction with MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T4 T5 T1 T2 T3 T4 T5
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.1 OP.6 FDD OP.9 FDD
(FDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB -3 channel powers defined in Table
PDCCH_RB dB -3 A.3.4.2.2-2.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
SNR Note 6,7 dB -1.3 -5.4 -12.4 -7.3 -1.3 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU30 ETU30
Note 1: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 of the active cell is denoted as SNR1, SNR2, SNR3, SNR4
and SNR5 respectively in figure A.7.3.15.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a
UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 982 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.15.1-1 SNR variation in the active cell for in-sync testing under time domain
measurement resource restriction with MBSFN ABS
A.7.3.15.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.16 E-UTRAN TDD Radio Link Monitoring Test for In-sync under Time
Domain Measurement Resource Restriction with MBSFN ABS
A.7.3.16.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction when
CRS assistance information is not provided. This test will partly verify the E-UTRAN TDD radio link monitoring
requirements in clause 7.6.
The test parameters are given in Tables A.7.3.16.1-1 and A.7.3.16.1-2 below. There are two cells, cell 1 is the serving
cell and cell 2 is the neighbour aggressor cell. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.15.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
MBSFN ABS pattern is configured in Cell 2 in this test. The UE is configured by higher layers with a time domain
measurement restriction pattern for performing serving cell measurements. The patterns shall be configured prior to the
start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 983 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.16.1-1: General test parameters for E-UTRAN TDD in-sync testing under time domain
measurement resource restriction with MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.9 TDD As specified in clause A.3.1.2.2.
parameters None of the PDCCH are intended
for the UE under test
Serving cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
Neighbour cell Cell 2 Cell 2 is the aggressor cell on E-
UTRA RF channel number 1
Neighbour cell ABS MBSFN ABS As defined in Table A.3.4.2.2-2
configuration
OCNG parameters for Cell 1 OP.2 TDD As specified in clause A.3.2.2.2.
OCNG parameters for Cell 2 OP.6 TDD As specified in clause A.3.2.2.6.
CP length Normal
Neighbor cell ABS MBSFN ABS
configuration
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
Correlation Matrix and Antenna 2x2 Low Correlation Matrix and Antenna
Configuration Configuration are defined in TS
36.101 [5] Annex B.2.3.2
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of 3 In sync threshold Qin and the
transmission Control OFDM corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CCE 4 parameters are as specified in
level clause and Table 7.6.1-2
ρA, ρB -3 respectively.
Ratio of dB -3
PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of sync Number of 3 Out of sync threshold Qout and the
transmission Control OFDM corresponding hypothetical
parameters symbols PDCCH/PCFICH transmission
(Note 1) Aggregation CCE 8 parameters are as specified in
level clause 7.6.1 and Table 7.6.1-1
ρA, ρB -3 respectively.
Ratio of dB 1
PDCCH to RS
EPRE
Ratio of dB 1
PCFICH to RS
EPRE
Physical cell ID PCI (PCIcell1-PCIcell2 ) mod 3 = Cell IDs are chosen such that CRS
0, PCIcell1 not equal to from cells 1 and 2 overlap in
PCIcell2 frequency.
ABS pattern 00001000000000100000 TDD ABS Pattern Info IE is
configured in Cell 2 as defined in
clause 9.2.54 in TS 36.423 [28].
The first/leftmost bit corresponds to
the subframe #0 of the radio frame
satisfying SFN mod x = 0, where x
is the size of the bit string (20)
divided by 10.
All ABS subframes are MBSFN
subframes.
Time domain measurement 00001000000000100000 MeasSubframePattern IE is
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 984 ETSI TS 136 133 V14.3.0 (2017-04)
resource restriction pattern configured in UE for serving cell
measurement as defined in
clause 6.3.6 in TS 36.331.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS
36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting periodicity
Time offset between cells μs 3
Propagation channel ETU30
T1 s 0.5
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 985 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.16.1-2: Cell specific test parameters for E-UTRAN TDD for in-sync radio link monitoring
under time domain measurement resource restriction with MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T4 T5 T1 T2 T3 T4 T5
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
Special subframe 6 6
configurationNote1
Uplink-downlink 1 1
configurationNote2
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.6 TDD
(TDD)
ρA, ρB -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB -3 channel powers defined in Table
PDCCH_RB dB -3 A.3.4.2.2-2.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
SNR Note 8,9 dB -1.3 -5.4 -12.4 -7.3 -1.3 5
N oc dBm/15 -98 -98
kHz
Propagation condition ETU30 ETU30
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2, T3, T4 and T5 of the active cell is denoted as SNR1, SNR2, SNR3, SNR4
and SNR5 respectively in figure A.7.3.16.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a
UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 986 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.16.1-1 SNR variation in the active cell for in-sync testing under time domain
measurement resource restriction with MBSFN ABS
A.7.3.16.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.17 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync under
Time Domain Measurement Resource Restriction with CRS
Assistance Information and Non-MBSFN ABS
A.7.3.17.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell under time domain measurement resource restriction with CRS
assistance information. This test will partly verify the E-UTRAN FDD radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.17.1-1 and A.7.3.17.1-2 below. There are three active cells in the test:
Cell 1 is the PCell cell and Cell 2 and 3 are the neighbour cells. The test consists of three successive time periods, with
time duration of T1, T2 and T3 respectively. Figure A.7.3.17.1-1 shows the variation of the downlink SNR in the active
cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully
synchronized to cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms.
Non-MBSFN ABS pattern is configured in both Cell 2 and Cell 3 in this test. The UE is configured by higher layers
with a time domain measurement restriction pattern for performing Pcell measurements. The UE is also provided via
higher layers with the CRS assistance information for Cell 2 and Cell 3, which shall be valid during T1, T2 and T3 in
this test. The non-MBSFN ABS pattern, the time domain measurement resource restriction pattern and the CRS
assistance information shall be configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 987 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.17.1-1: General test parameters for E-UTRAN FDD out-of-sync testing under time domain
measurement resource restriction with CRS Assistance Information and Non-MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.7 FDD As specified in clause A.3.1.2.1.
parameters None of the PDCCH are intended for the UE
under test
OCNG parameters OP.6 FDD As specified in section A.3.2.1.6.
PCell Cell 1 Cell 1 is on E-UTRA RF channel number 1
Neighbor cells Cell 2 and Cell 3 Both of aggressor cells on E-UTRA RF channel
number 1
Neighbor cell ABS Non-MBSFN ABS As defined in Table A.3.4.1.2-1
configuration
CP length Normal
E-UTRA RF Channel 1 One E-UTRA FDD carrier frequency is used.
Number
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Correlation Matrix and 2x2 Low Correlation Matrix and Antenna Configuration
Antenna Configuration are defined in TS 36.101 [5] Annex B.2.3.2
Out of sync DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
transmission Number of 2 Out of sync threshold Qout and the
parameters Control corresponding hypothetical PDCCH/PCFICH
(Note 1) OFDM transmission parameters are as specified in
symbols clause 7.6.1 and Table 7.6.1-1 respectively.
Aggregation CCE 8
level
ρA, ρB -3
Ratio of dB 1
PDCCH to
RS EPRE
Ratio of dB 1
PCFICH to
RS EPRE
DRX OFF
Layer 3 filtering Enabled Counters:: N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
Time offset between cells μs Cell 2 time offset with Three synchronous cells
respect to Cell 1: 3
Cell 3 time offset with
respect to Cell 1: 2
Frequency shift between Hz Cell 2 frequency shift with
cells respect to Cell 1: 300
Cell 3 frequency shift with
respect to Cell 1: -100
T1 s 1
T2 s 0.4
T3 s 0.5
(PCIcell1-PCIcell2 )mod3 = 0 Cell PCIs are selected so that all conditions are
(PCIcell1-PCIcell3 )mod3!= 0 met
Physical cell IDs
PCIcell1 not equal to
PCIcell2
ABS pattern ‘10000000100000001000 FDD ABS Pattern Info IE, as defined in TS
00001000000010000000’ 36.423 [28], clause 9.2.54. The first/leftmost bit
corresponds to the PCell subframe #0 of the
radio frame satisfying SFN mod x = 0, where x
is the size of the bit string (40) divided by 10. No
MBSFN subframes are configured in the ABS
subframes.
Configured in both Cell 2 and Cell 3 prior to the
start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 988 ETSI TS 136 133 V14.3.0 (2017-04)
Time domain measurement ‘10000000100000001000 Time domain measurement resource restriction
resource restriction pattern 00001000000010000000’ pattern for serving cell measurement signalled
to the UE in message
measSubframePatternPCell-r10 as defined in
TS 36.331, clause 6.3.2.
CRS physCellId see PCI conditions above The CRS assistance information is provided for
assistance antennaPort Cell 2 and Cell 3 in CRS-AssistanceInfo. It
information an2 includes a single MBSFN-SubframeConfig
sCount
mbsfn- element with subframe allocation
SubframeCo oneFrame = ‘000000’ oneFrame=’000000’
nfigList
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel
Table A.7.3.17.1-2: Cell specific test parameters for E-UTRAN FDD for out-of-sync radio link
monitoring under time domain measurement resource restriction with CRS Assistance Information
and Non-MBSFN ABS
Parameter Unit Cell 1 Cell 2 Cell 3
T1 T2 T3 T1-T3 T1-T3
E-UTRA RF Channel 1 1 1
Number
BW channel MHz 10 10 10
Correlation Matrix 2x2 Low 2x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.1.6 OP.6 FDD OP.6 FDD OP.6 FDD
(FDD)
ρA, ρB -3 -3 -3
PCFICH_RB dB 1 Non-ABS and Non-ABS and
PDCCH_RA dB 1 ABS subframe ABS subframe
PDCCH_RB dB 1 channel powers channel powers
PBCH_RA dB defined in Table defined in Table
PBCH_RB dB A.3.4.1.2-1. A.3.4.1.2-1.
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,7 dB -1.5 -5.2 -13.7 4 2
N oc dBm/15 -98 -98 -98
kHz
Propagation condition ETU 30 Hz ETU 30 Hz ETU 30 Hz
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal quality, signal-to-interference-plus-noise ratio, on the CRS
REs.
Note 6: The SNR in the restricted measurement subframes during time periods T1, T2 and T3 is denoted
as SNR1, SNR2 and SNR3 respectively in figure A.7.3.17.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For
testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as specified in
section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 989 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.17.1-1 SNR variation for out-of-sync testing
A.7.3.17.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.18 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync under
Time Domain Measurement Resource Restriction with CRS
Assistance Information and Non-MBSFN ABS
A.7.3.18.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the serving cell under time domain measurement resource restriction with
CRS assistance information. This test will partly verify the E-UTRAN TDD radio link monitoring requirements in
clause 7.6.
The test parameters are given in Tables A.7.3.18.1-1 and A.7.3.18.1-2 below. There are three active cells in the test:
Cell 1 is the PCell cell and Cell 2 and 3 are the neighbour cells. The test consists of three successive time periods, with
time duration of T1, T2 and T3 respectively. Figure A.7.3.18.1-1 shows the variation of the downlink SNR in the active
cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully
synchronized to cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms.
Non-MBSFN ABS pattern is configured in both Cell 2 and Cell 3 in this test. The UE is configured by higher layers
with a time domain measurement restriction pattern for performing Pcell measurements. The UE is also provided via
higher layers with the CRS assistance information for Cell 2 and Cell 3, which shall be valid during T1, T2 and T3 in
this test. The non-MBSFN ABS pattern, the time domain measurement resource restriction pattern and the CRS
assistance information shall be configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 990 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.18.1-1: General test parameters for E-UTRAN TDD out-of-sync testing under time domain
measurement resource restriction with CRS Assistance Information and Non-MBSFN ABS
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.7.TDD As specified in clause A.3.1.2.2.
parameters None of the PDCCH are intended for the UE
under test
OCNG parameters OP.2 TDD As specified in clause A.3.2.2.2
PCell Cell 1 Cell 1 is on E-UTRA RF channel number 1
Neighbor cells Cell 2 and Cell 3 Both of aggressor cells on E-UTRA RF channel
number 1
Neighbor cell ABS Non-MBSFN ABS As defined in Table A.3.4.1.2-1
configuration
CP length Normal
E-UTRA RF Channel 1 One E-UTRA TDD carrier frequency is used.
Number
E-UTRA Channel Bandwidth MHz 10
(BW channel)
Correlation Matrix and 2x2 Low Correlation Matrix and Antenna Configuration
Antenna Configuration are defined in TS 36.101 [5] Annex B.2.3.2
Out of sync DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
transmission Number of 2 Out of sync threshold Qout and the
parameters Control corresponding hypothetical PDCCH/PCFICH
(Note 1) OFDM transmission parameters are as specified in
symbols clause 7.6.1 and Table 7.6.1-1 respectively.
Aggregation CCE 8
level
ρA, ρB -3
Ratio of dB 1
PDCCH to
RS EPRE
Ratio of dB 1
PCFICH to
RS EPRE
DRX OFF
Layer 3 filtering Enabled Counters:: N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting periodicity
Time offset between cells μs Cell 2 time offset with Three synchronous cells
respect to Cell 1: 3
Cell 3 time offset with
respect to Cell 1: 2
Frequency shift between Hz Cell 2 frequency shift with
cells respect to Cell 1: 300
Cell 3 frequency shift with
respect to Cell 1: -100
T1 s 1
T2 s 0.4
T3 s 0.5
(PCIcell1-PCIcell2 )mod3 = 0 Cell PCIs are selected so that all conditions are
(PCIcell1-PCIcell3 )mod3!= 0 met
Physical cell IDs
PCIcell1 not equal to
PCIcell2
ABS pattern ‘00001000000000100000’ TDD ABS Pattern Info IE, as defined in TS
36.423 [28], clause 9.2.54. The first/leftmost bit
corresponds to the PCell subframe #0 of the
radio frame satisfying SFN mod x = 0, where x
is the size of the bit string (20) divided by 10. No
MBSFN subframes are configured in the ABS
subframes.
Configured in both Cell 2 and Cell 3 prior to the
start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 991 ETSI TS 136 133 V14.3.0 (2017-04)
Time domain measurement ‘00001000000000100000’ Time domain measurement resource restriction
resource restriction pattern pattern for serving cell measurement signalled
to the UE in message
measSubframePatternPCell-r10 as defined in
TS 36.331, clause 6.3.2.
CRS physCellId see PCI conditions above The CRS assistance information is provided for
assistance antennaPort Cell 2 only in CRS-AssistanceInfo. It includes a
information an2 single MBSFN-SubframeConfig element with
sCount
mbsfn- subframe allocation oneFrame=’000000’
SubframeCo oneFrame = ‘000000’
nfigList
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 992 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.18.1-2: Cell specific test parameters for E-UTRAN TDD for out-of-sync radio link
monitoring under time domain measurement resource restriction with CRS Assistance Information
and Non-MBSFN ABS
Parameter Unit Cell 1 Cell 2 Cell 3
T1 T2 T3 T1-T3 T1-T3
E-UTRA RF Channel 1 1 1
Number
BW channel MHz 10 10 10
Special subframe 6 6 6
configurationNote1
Uplink-downlink 1 1 1
configurationNote2
Correlation Matrix 2x2 Low 2x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern
defined in A.3.2.2.2 OP.2 TDD OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB -3 -3 -3
PCFICH_RB dB 1 Non-ABS and Non-ABS and
PDCCH_RA dB 1 ABS subframe ABS subframe
PDCCH_RB dB 1 channel powers channel powers
PBCH_RA dB defined in Table defined in Table
PBCH_RB dB A.3.4.1.2-1. A.3.4.1.2-1.
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,9 dB -1.5 -5.2 -13.7 4 2
N oc dBm/15 -98 -98 -98
kHz
Propagation condition ETU 30 Hz ETU 30 Hz ETU 30 Hz
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink subframe configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal quality, signal-to-interference-plus-noise ratio, on the CRS
REs.
Note 8: The SNR in the restricted measurement subframes during time periods T1, T2 and T3 is denoted
as SNR1, SNR2 and SNR3 respectively in Figure A.7.3.18.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For
testing of a UE which supports 4RX on all bands, the SNR during T3 is modified as specified in
section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 993 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.18.1-1 SNR variation for out-of-sync testing
A.7.3.18.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.19 E-UTRAN FDD Radio Link Monitoring Test for In-sync under Time
Domain Measurement Resouce Restriction with CRS assistance
information and Non-MBSFN ABS
A.7.3.19.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell under time domain measurement resource restriction with CRS
assistance information. This test will partly verify the E-UTRAN FDD radio link monitoring requirements in section
7.6.
The test parameters are given in Tables A.7.3.19.1-1 and A.7.3.19.1-2 below. There are three active cells in the test:
Cell 1 is the PCell cell and Cell 2 and 3 are the neighbour cells. The test consists of five successive time periods, with
time duration of T1, T2, T3, T4 and T5 respectively. Figure A.7.3.19.1-1 shows the variation of the downlink SNR in
the active cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully
synchronized to cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms.
Non-MBSFN ABS pattern is configured in both Cell 2 and Cell 3 in this test. The UE is configured by higher layers
with a time domain measurement restriction pattern for performing PCell measurements. The UE is also provided via
higher layers with the CRS assistance information for Cell 2 and Cell 3, which shall be valid during T1, T2, T3, T4 and
T5 in this test. The Non-MBSFN ABS pattern, the time domain measurement resource restriction pattern and the CRS
assistance information shall be configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 994 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.19.1-1: General test parameters for E-UTRAN FDD in-sync radio link monitoring test
Parameter Unit Value Comment
Test 1
Cell 1 Cell 2 Cell 3
PCFICH/PDCCH/PHICH R.9 FDD R.9 FDD R.9 FDD As specified in section
parameters A.3.1.2.1.
None of the PDCCH are
intended for the UE under
test
OCNG parameters OP.6 FDD OP.6 FDD OP.6 FDD As specified in section
A.3.2.1.6.
Active cell PCell Neighbor Neighbor Cell 1, Cell 2 and Cell 3
Cell Cell are on E-UTRA RF
channel number 1
CP length Normal Normal Normal
E-UTRA RF Channel Number 1 1 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10 10
(BW channel)
Correlation Matrix and 2x2 Low 2x2 Low 2x2 Low Correlation Matrix and
Antenna Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
Neighbor Cell ABS N/A Non-MBSFN ABS As defined in Table
configuration A.3.4.1.2-2
ABS Pattern N/A '100000001 '100000001 FDD ABS Pattern Info IE,
0000000100 0000000100 as defined in TS 36.423
0 0 [28], clause 9.2.54.
0000100000 0000100000 The first/leftmost bit
0010000000 0010000000 corresponds to the Pcell
’ ’ subframe #0 of the radio
frame satisfying SFN mod
x = 0, where x is the size
of the bit string (40)
divided by 10. No MBSFN
subframes are cofigured in
the ABS subframes.
Configured in both Cell 2
and Cell 3 prior to the start
of T1.
Time domain measurement ‘100000001 N/A N/A Time domain
resource restriction pattern 0000000100 measurement resource
0000010000 restriction pattern for
0001000000 serving cell measurement
0’ signalled to the UE in
message
measSubframePatternPCe
ll-r10 as defined in TS
36.331, clause 6.3.2.
CRS physCellld N/A see PCI see PCI The CRS assistance
assistant conditions conditions information is provided for
information below below Cell 2 and Cell 3 in CRS-
antennaPorts an2 an2 AssistanceInfo. It includes
Count a single MBSFN-
mbsfn- oneFrame = oneFrame = SubframeConfig element
SubframeCo ‘000000’ ‘000000’ with subframe allocation
nfigList oneFrame=’000000’
Time offset between cells us 0 3 2
(With respect to Cell 1)
Frequency shift between cells Hz 0 300 -100
(With respect to Cell 1)
Physical Cell ID PCIcell1 (PCIcell1- (PCIcell1- Cell PCIs are selected so
PCIcell2) PCIcell3) that all conditions are met
mod3 = 0, mod3! = 0
PCIcell1 not
equal to
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 995 ETSI TS 136 133 V14.3.0 (2017-04)
PCIcell2
In sync transmission DCI 1C 1C 1C
parameters (Note 1) format
Number of 3 3 3 As defined in section
Control 5.3.3.1.4 in TS 36.212
In sync OFDM
transmission symbols
parameters Aggregatio CCE 4 4 4 In sync threshold Qin and
(Note 1) n level the corresponding
ρA, ρB -3 -3 -3 hypothetical
Ratio of -3 Non-ABS and ABS PDCCH/PCFICH
PDCCH to subframe channel powers transmission parameters
RS EPRE defined in Table A.3.4.1.2-2. are as specified in section
Ratio of 1 and Table 7.6.1-2
PCFICH to respectively.
RS EPRE
DCI format 1A 1A 1A
Number of 3 3 3 As defined in section
Out of sync Control 5.3.3.1.3 in TS 36.212
transmission OFDM
parameters symbols
(Note 1) Aggregatio CCE 8 8 8 Out of sync threshold Qout
n level and the corresponding
ρA, ρB -3 -3 -3 hypothetical
Ratio of dB 1 Non-ABS and ABS PDCCH/PCFICH
PDCCH to subframe channel powers transmission parameters
RS EPRE defined in Table A.3.4.1.2-2. are as specified in section
Ratio of dB 1 7.6.1 and Table 7.6.1-1
PCFICH to respectively.
RS EPRE
DRX OFF OFF OFF
Layer 3 filtering Enabled Disable Disable Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 N/A T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1
in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 0.5 N/A
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 996 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.19.1-2: Cell specific test parameters for E-UTRAN FDD in-sync radio link monitoring test
Parameter Unit Test 1
Cell1 Cell2 Cell3
T1 T2 T3 T4 T5 T1-T5 T1-T5
E-UTRA RF Channel 1 1 1
Number
BW channel MHz 10 10 10
Correlation Matrix 2x2 Low 2x2 Low 2x2 Low
and Antenna
Configuration
PCFICH/PDCCH/PHI R.9 FDD R.9 FDD R.9 FDD
CH parameters
OCNG Pattern
defined in A.3.2.1 OP.6 FDD OP.6 FDD OP.6 FDD
(FDD)
ρA, ρB -3 -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB channel powers defined in
PDCCH_RB dB Table A.3.4.1.2-2.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
SNR Note 6,7 dB -1.5 -5.2 -13.7 -8.6 -1.5 4 2
N oc dBm/15 -98 -98 -98
kHz
Propagation condition Hz ETU 30 ETU 30 ETU 30
Note 1: OCNG shall be used such that the resources in cell 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5
respectively in figure A.7.3.19.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of
a UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section
A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 997 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.19.1-1 SNR variation for in-sync testing
A.7.3.19.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.20 E-UTRAN TDD Radio Link Monitoring Test for In-sync under Time
Domain Measurement Resouce Restriction with CRS assistance
information and Non-MBSFN ABS
A.7.3.20.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell under time domain measurement resource restriction with CRS
assistance information. This test will partly verify the E-UTRAN TDD radio link monitoring requirements in section
7.6.
The test parameters are given in Tables A.7.3.20.1-1 and A.7.3.20.1-2 below. There are three active cells in the test:
Cell 1 is the PCell and Cell 2 and 3 are the Neighbor cells. The test consists of five successive time periods, with time
duration of T1, T2, T3, T4 and T5 respectively. Figure A.7.3.20.1-1 shows the variation of the downlink SNR in the
PCell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully
synchronized to cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms.
Non-MBSFN ABS pattern is configured in both Cell 2 and Cell 3 in this test. The UE is configured by higher layers
with a time domain measurement restriction pattern for performing PCell measurements. The UE is also provided via
higher layers with the CRS assistance information for Cell 2 and Cell 3, which shall be valid during T1, T2, T3, T4 and
T5 in this test. The Non-MBSFN ABS pattern, the time domain measurement resource restriction pattern and the CRS
assistance information shall be configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 998 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.20.1-1: General test parameters for E-UTRAN TDD in-sync radio link monitoring test
Parameter Unit Value Comment
Test 1
Cell 1 Cell 2 Cell 3
PCFICH/PDCCH/PHICH R.9 TDD R.9 TDD R.9 TDD As specified in section
parameters A.3.1.2.2.
None of the PDCCH are
intended for the UE under
test
OCNG parameters OP.2 TDD OP.2 TDD OP.2 TDD As specified in section
A.3.2.2.2.
Active cell PCell Neighbor Neighbor Cell 1, Cell 2 and Cell 3
Cell Cell are on E-UTRA RF
channel number 1
CP length Normal Normal Normal
E-UTRA RF Channel Number 1 1 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10 10
(BW channel)
Correlation Matrix and 2x2 Low 2x2 Low 2x2 Low Correlation Matrix and
Antenna Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
Neighbor Cell ABS N/A Non-MBSFN ABS
configuration As defined in Table
A.3.4.1.2-1
ABS Pattern N/A ‘000010000 ‘000010000 TDD ABS Pattern Info IE,
0000010000 0000010000 as defined in TS 36.423
0’ 0’ [28], clause 9.2.54.
Configured in Cell 2 and
Cell 3.
The first/leftmost bit
corresponds to the Pcell
subframe #0 of the radio
frame satisfying SFN mod
x = 0, where x is the size
of the bit string (20)
divided by 10. No MBSFN
subframes are configured
in the ABS subframes.
Time domain measurement ‘000010000 N/A N/A Time domain
resource restriction pattern 0000010000 measurement resource
0’ restriction pattern for
serving cell measurement
signalled to the UE in
message
measSubframePatternPCe
ll-r10 as defined in TS
36.331, clause 6.3.2.
CRS physCellld N/A see PCI see PCI The CRS assistance
assistant conditions conditions information is provided for
information below below Cell 2 and Cell 3 in CRS-
antennaPorts an2 an2 AssistanceInfo. It includes
Count a single MBSFN-
mbsfn- oneFrame = oneFrame = SubframeConfig element
SubframeCo ‘000000’ ‘000000’ with subframe allocation
nfigList oneFrame=’000000’
Time offset from Cell 1 us 0 3 2
Frequency offset Hz 0 300 -100
Physical Cell ID PCIcell1 (PCIcell1- (PCIcell1- Cell PCIs are selected so
PCIcell2 ) PCIcell3 ) that all conditions are met
mod3 = 0, mod3! = 0
PCIcell1 not
equal to
PCIcell2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 999 ETSI TS 136 133 V14.3.0 (2017-04)
DCI format 1C 1C 1C As defined in section
5.3.3.1.4 in TS 36.212
Number of 3 3 3 In sync threshold Qin and
In sync Control the corresponding
transmission OFDM hypothetical
parameters symbols PDCCH/PCFICH
(Note 1) Aggregatio CCE 4 4 4 transmission parameters
n level are as specified in section
ρA, ρB -3 -3 -3 and Table 7.6.1-2
Ratio of -3 Non-ABS and ABS respectively.
PDCCH to subframe channel powers
RS EPRE defined in Table A.3.4.1.2-2.
Ratio of 1
PCFICH to
RS EPRE
DCI format 1A 1A 1A As defined in section
5.3.3.1.3 in TS 36.212
Out of sync Number of 3 3 3 Out of sync threshold Qout
transmission Control and the corresponding
parameters OFDM hypothetical
(Note 1) symbols PDCCH/PCFICH
Aggregatio CCE 8 8 8 transmission parameters
n level are as specified in section
ρA, ρB -3 -3 -3 7.6.1 and Table 7.6.1-1
Ratio of dB 1 Non-ABS and ABS respectively.
PDCCH to subframe channel powers
RS EPRE defined in Table A.3.4.1.2-2.
Ratio of dB 1
PCFICH to
RS EPRE
DRX OFF OFF OFF
Layer 3 filtering Enabled Disable Disable Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 N/A T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1
in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
T1 s 0.5 N/A
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1000 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.20.1-2: Cell specific test parameters for E-UTRAN TDD in-sync radio link monitoring test
Parameter Unit Test 1
Cell1 Cell2 Cell3
T1 T2 T3 T4 T5 T1-T5 T1-T5
E-UTRA RF Channel 1 1 1
Number
BW channel MHz 10 10 10
Correlation Matrix 2x2 Low 2x2 Low 2x2 Low
and Antenna
Configuration
Special subframe 6 6 6
configuration Note 1
Uplink-downlink 1 1 1
configuration Note 2
PCFICH/PDCCH/PHI R.9 TDD R.9 TDD R.9 TDD
CH parameters
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.2 TDD OP.2 TDD
(TDD)
ρA, ρB -3 -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB channel powers defined in
PDCCH_RB dB Table A.3.4.1.2-2.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 3 dB
OCNG_RBNote 3 dB
SNR Note 8,9 dB -1.5 -5.2 -13.7 -8.6 -1.5 4 2
N oc dBm/15 -98 -98 -98
kHz
Propagation condition Hz ETU 30 ETU 30 ETU 30
Note 1: For the special subframe configuration see table 4.2-1 in 3GPP TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in 3GPP TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2, T3, T4 and T5 of active cell is denoted as SNR1, SNR2, SNR3,
SNR4 and SNR5 respectively in figure A.7.3.20.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of
a UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section
A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1001 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.20.1-1 SNR variation for in-sync testing
A.7.3.20.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.21 E-UTRAN FDD Radio Link Monitoring Test for In-sync under Time
Domain Measurement Resouce Restriction with CRS assistance
information and MBSFN ABS
A.7.3.21.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell under time domain measurement resource restriction with CRS
assistance information and MBSFN ABS. This test will partly verify the E-UTRAN FDD radio link monitoring
requirements in section 7.6.
The test parameters are given in Tables A.7.3.21.1-1 and A.7.3.21.1-2 below. There are three active cells in the test:
Cell 1 is the PCell cell and Cell 2 and 3 are the neighbour cells. The test consists of five successive time periods, with
time duration of T1, T2, T3, T4 and T5 respectively. Figure A.7.3.21.1-1 shows the variation of the downlink SNR in
the active cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully
synchronized to cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms.
MBSFN ABS pattern is configured in both Cell 2 and Cell 3 in this test. The UE is configured by higher layers with a
time domain measurement restriction pattern for performing PCell measurements. The UE is also provided via higher
layers with the CRS assistance information for Cell 2 and Cell 3, which shall be valid during T1, T2, T3, T4 and T5 in
this test. The MBSFN ABS pattern, the time domain measurement resource restriction pattern and the CRS assistance
information shall be configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1002 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.21.1-1: General test parameters for E-UTRAN FDD in-sync radio link monitoring test
Parameter Unit Value Comment
Test 1
Cell 1 Cell 2 Cell 3
PCFICH/PDCCH/PHICH R.9 FDD R.9 FDD R.9 FDD As specified in section
parameters A.3.1.2.1.
None of the PDCCH are
intended for the UE under
test
OCNG parameters OP.6 FDD OP.9 FDD OP.9 FDD As specified in section
A.3.2.1.
Active cell PCell Neighbor Neighbor Cell 1, Cell 2 and Cell 3
Cell Cell are on E-UTRA RF
channel number 1
CP length Normal Normal Normal
E-UTRA RF Channel Number 1 1 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10 10
(BW channel)
Correlation Matrix and 2x2 Low 2x2 Low 2x2 Low Correlation Matrix and
Antenna Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
Neighbor Cell ABS N/A MBSFN ABS As defined in Table
configuration A.3.4.2.2-2
ABS Pattern N/A '010000001 '010000001 FDD ABS Pattern Info IE,
0000000100 0000000100 as defined in TS 36.423
0000000100 0000000100 [28], clause 9.2.54.
0000100000 0000100000 The first/leftmost bit
0' 0' corresponds to the Pcell
subframe #0 of the radio
frame satisfying SFN mod
x = 0, where x is the size
of the bit string (40)
divided by 10. MBSFN
subframes are cofigured in
the ABS subframes
configured in Cell 2 and
Cell 3 prior to the start of
T1.
Time domain measurement ‘010000001 N/A N/A Time domain
resource restriction pattern 0000000100 measurement resource
0000000100 restriction pattern for
0000100000 serving cell measurement
0’ signalled to the UE in
message
measSubframePatternPCe
ll-r10 as defined in TS
36.331, clause 6.3.2.
CRS physCellld N/A see PCI see PCI The CRS assistance
assistance conditions conditions information is provided for
information below below Cell 2 and Cell 3 in CRS-
antennaPorts an2 an2 AssistanceInfo. It includes
Count a single MBSFN-
mbsfn- fourFrames fourFrames SubframeConfig element
SubframeCo = = with subframe allocation
nfigList ‘100001000 ‘100001000 fourFrames =
1000001000 1000001000 ‘100001000100000100001
01000’ 01000’ 000’
Time offset between cells us 0 3 2
(With respect to Cell 1)
Frequency shift between cells Hz 0 300 -100
(With respect to Cell 1)
Physical Cell ID PCIcell1 (PCIcell1- (PCIcell1- Cell PCIs are selected so
PCIcell2) PCIcell3) that all conditions are met
mod3 = 0, mod3 != 0
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1003 ETSI TS 136 133 V14.3.0 (2017-04)
PCIcell1 not
equal to
PCIcell2
In sync transmission DCI 1C 1C 1C
parameters (Note 1) format
Number of 3 3 3 As defined in section
Control 5.3.3.1.4 in TS 36.212
In sync OFDM
transmission symbols
parameters Aggregatio CCE 4 4 4 In sync threshold Qin and
(Note 1) n level the corresponding
ρA, ρB -3 -3 -3 hypothetical
Ratio of -3 Non-ABS and ABS PDCCH/PCFICH
PDCCH to subframe channel powers transmission parameters
RS EPRE defined in Table A.3.4.2.2-2. are as specified in section
Ratio of 1 and Table 7.6.1-2
PCFICH to respectively.
RS EPRE
DCI format 1A 1A 1A
Number of 3 3 3 As defined in section
Out of sync Control 5.3.3.1.3 in TS 36.212
transmission OFDM
parameters symbols
(Note 1) Aggregatio CCE 8 8 8 Out of sync threshold Qout
n level and the corresponding
ρA, ρB -3 -3 -3 hypothetical
Ratio of dB 1 Non-ABS and ABS PDCCH/PCFICH
PDCCH to subframe channel powers transmission parameters
RS EPRE defined in Table A.3.4.2.2-2. are as specified in section
Ratio of dB 1 7.6.1 and Table 7.6.1-1
PCFICH to respectively.
RS EPRE
DRX OFF OFF OFF
Layer 3 filtering Enabled Disable Disable Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 N/A T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1
in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 0.5 N/A
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1004 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.21.1-2: Cell specific test parameters for E-UTRAN FDD in-sync radio link monitoring test
Parameter Unit Test 1
Cell1 Cell2 Cell3
T1 T2 T3 T4 T5 T1-T5 T1-T5
E-UTRA RF Channel 1 1 1
Number
BW channel MHz 10 10 10
Correlation Matrix 2x2 Low 2x2 Low 2x2 Low
and Antenna
Configuration
PCFICH/PDCCH/PHI R.9 FDD R.9 FDD R.9 FDD
CH parameters
OCNG Pattern
defined in A.3.2.1 OP.6 FDD OP.9 FDD OP.9 FDD
(FDD)
ρA, ρB -3 -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB channel powers defined in
PDCCH_RB dB Table A.3.4.2.2-2.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
SNR Note 6,7 dB -1.5 -5.2 -13.7 -8.6 -1.5 4 2
N oc dBm/15 -98 -98 -98
kHz
Propagation condition Hz ETU 30 ETU 30 ETU 30
Note 1: OCNG shall be used such that the resources in cell 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5
respectively in figure A.7.3.21.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of
a UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section
A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1005 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.21.1-1 SNR variation for in-sync testing
A.7.3.21.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.22 E-UTRAN TDD Radio Link Monitoring Test for In-sync under Time
Domain Measurement Resouce Restriction with CRS assistance
information and MBSFN ABS
A.7.3.22.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PCell under time domain measurement resource restriction with CRS
assistance information. This test will partly verify the E-UTRAN TDD radio link monitoring requirements in section
7.6.
The test parameters are given in Tables A.7.3.22.1-1 and A.7.3.22.1-2 below. There are three active cells in the test:
Cell 1 is the PCell and Cell 2 and 3 are the Neighbor cells. The test consists of five successive time periods, with time
duration of T1, T2, T3, T4 and T5 respectively. Figure A.7.3.22.1-1 shows the variation of the downlink SNR in the
PCell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully
synchronized to cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms.
MBSFN ABS pattern is configured in both Cell 2 and Cell 3 in this test. The UE is configured by higher layers with a
time domain measurement restriction pattern for performing PCell measurements. The UE is also provided via higher
layers with the CRS assistance information for Cell 2 and Cell 3, which shall be valid during T1, T2, T3, T4 and T5 in
this test. The MBSFN ABS pattern, the time domain measurement resource restriction pattern and the CRS assistance
information shall be configured prior to the start of T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1006 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.22.1-1: General test parameters for E-UTRAN TDD in-sync radio link monitoring test
Parameter Unit Value Comment
Test 1
Cell 1 Cell 2 Cell 3
PCFICH/PDCCH/PHICH R.9 TDD R.9 TDD R.9 TDD As specified in section
parameters A.3.1.2.2.
None of the PDCCH are
intended for the UE under
test
OCNG parameters OP.2 TDD OP.6 TDD OP.6 TDD As specified in section
A.3.2.2.
Active cell PCell Neighbor Neighbor Cell 1, Cell 2 and Cell 3
Cell Cell are on E-UTRA RF
channel number 1
CP length Normal Normal Normal
E-UTRA RF Channel Number 1 1 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10 10 10
(BW channel)
Correlation Matrix and 2x2 Low 2x2 Low 2x2 Low Correlation Matrix and
Antenna Configuration Antenna Configuration are
defined in TS 36.101 [5]
Annex B.2.3.2
Neighbor Cell ABS N/A MBSFN ABS As defined in Table
configuration A.3.4.2.2-1
ABS Pattern N/A '000010000 '000010000 TDD ABS Pattern Info IE,
0000010000 0000010000 as defined in TS 36.423
0' 0' [28], clause 9.2.54.
Configured in Cell 2 and
Cell 3
The first/leftmost bit
corresponds to the
subframe #0 of the radio
frame satisfying SFN mod
20 = 0, where x is the size
of the bit string (20)
divided by 10. MBSFN
subframes are configured
in the ABS subframes.
Time domain measurement ‘000010000 N/A N/A Time domain
resource restriction pattern 0000010000 measurement resource
0’ restriction pattern for
serving cell measurement
signalled to the UE in
message
measSubframePatternPCe
ll-r10 as defined in TS
36.331, clause 6.3.2.
CRS physCellld N/A see PCI see PCI The CRS assistance
assistance conditions conditions information is provided for
information below below Cell 2 and Cell 3 in CRS-
antennaPorts an2 an2 AssistanceInfo. It includes
Count a single MBSFN-
mbsfn- fourFrames fourFrames SubframeConfig element
SubframeCo = = with subframe allocation
nfigList ‘010000100 ‘010000100 fourFrames =
0010000100 0010000100 ‘010000100001000010000
00000’ 00000’ 000’
Time offset from Cell 1 us 0 3 2
Frequency offset Hz 0 300 -100
Physical Cell ID PCIcell1 (PCIcell1- (PCIcell1- Cell PCIs are selected so
PCIcell2 ) PCIcell3 ) that all conditions are met
mod3 = 0, mod3 != 0
PCIcell1 not
equal to
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1007 ETSI TS 136 133 V14.3.0 (2017-04)
PCIcell2
DCI format 1C 1C 1C As defined in section
5.3.3.1.4 in TS 36.212
Number of 2 2 2 In sync threshold Qin and
In sync Control the corresponding
transmission OFDM hypothetical
parameters symbols PDCCH/PCFICH
(Note 1) Aggregatio CCE 4 4 4 transmission parameters
n level are as specified in section
ρA, ρB -3 -3 -3 and Table 7.6.1-2
Ratio of -3 Non-ABS and ABS respectively.
PDCCH to subframe channel powers
RS EPRE defined in Table A.3.4.1.2-2.
Ratio of 1
PCFICH to
RS EPRE
DCI format 1A 1A 1A As defined in section
5.3.3.1.3 in TS 36.212
Out of sync Number of 2 2 2 Out of sync threshold Qout
transmission Control and the corresponding
parameters OFDM hypothetical
(Note 1) symbols PDCCH/PCFICH
Aggregatio CCE 8 8 8 transmission parameters
n level are as specified in section
ρA, ρB -3 -3 -3 7.6.1 and Table 7.6.1-1
Ratio of dB 1 Non-ABS and ABS respectively.
PDCCH to subframe channel powers
RS EPRE defined in Table A.3.4.1.2-2.
Ratio of dB 1
PCFICH to
RS EPRE
DRX OFF OFF OFF
Layer 3 filtering Enabled Disable Disable Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 N/A T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1
in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
T1 s 0.5 N/A
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1008 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.22.1-2: Cell specific test parameters for E-UTRAN TDD in-sync radio link monitoring test
Parameter Unit Test 1
Cell1 Cell2 Cell3
T1 T2 T3 T4 T5 T1-T5 T1-T5
E-UTRA RF Channel 1 1 1
Number
BW channel MHz 10 10 10
Correlation Matrix 2x2 Low 2x2 Low 2x2 Low
and Antenna
Configuration
Special subframe 6 6 6
configuration Note 1
Uplink-downlink 1 1 1
configuration Note 2
PCFICH/PDCCH/PHI R.9 TDD R.9 TDD R.9 TDD
CH parameters
OCNG Pattern
defined in A.3.2.2 OP.2 TDD OP.6 TDD OP.6 TDD
(TDD)
ρA, ρB -3 -3 -3
PCFICH_RB dB 1 Non-ABS and ABS subframe
PDCCH_RA dB channel powers defined in
PDCCH_RB dB Table A.3.4.2.2-1.
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 3 dB
OCNG_RBNote 3 dB
SNR Note 8,9 dB -1.5 -5.2 -13.7 -8.6 -1.5 4 2
N oc dBm/15 -98 -98 -98
kHz
Propagation condition Hz ETU 30 ETU 30 ETU 30
Note 1: For the special subframe configuration see table 4.2-1 in 3GPP TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in 3GPP TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2, T3, T4 and T5 of active cell is denoted as SNR1, SNR2, SNR3,
SNR4 and SNR5 respectively in figure A.7.3.22.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of
a UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section
A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1009 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.22.1-1 SNR variation for in-sync testing
A.7.3.22.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.23 E-UTRAN FDD Radio Link Monitoring Test for Out-of-sync for 5MHz
Bandwidth
A.7.3.23.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.7.3.1. The test parameters are the same
except those described in the following section. The listed parameter values in Tables A.7.3.23.1-1 and A.7.3.23.1-2
will replace the values of corresponding parameters in Test 4 in Tables A.7.3.1.1-1 and A.7.3.1.1-2. Only Test 4 is
defined for the 5MHz bandwidth.
Table A.7.3.23.1-1: General test parameters for E-UTRAN FDD out-of-sync testing under 5MHz
Bandwidth
Parameter Unit Value Comment
Test 4
PCFICH/PDCCH/PHICH R.12 FDD As specified in clause A.3.1.2.1.
parameters None of the PDCCH are intended for the
UE under test
OCNG parameters OP.16 FDD As specified in clause A.3.2.1.16.
E-UTRA Channel Bandwidth MHz 5
(BW channel)
Out of sync threshold Qout and the
corresponding hypothetical
Out of sync Number of
PDCCH/PCFICH transmission
transmission Control OFDM 3
parameters are as specified in
parameters Symbols
clause 7.6.1 and Table 7.6.1-1
(Note 1)
respectively.
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in
the Reference Measurement Channel.
Note 2: See Table A.7.3.1.1-1 for other general test parameters.
Note 3: This test is according to the principle defined in section A.3.7.2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1010 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.23.1-2: Cell specific test parameters for E-UTRAN FDD for out-of-sync radio link
monitoring test #4 under 5MHz Bandwidth
Parameter Unit Test 4
T1 T2 T3
BW channel MHz 5
OCNG Pattern
defined in A.3.2.1.16 OP.16 FDD
(FDD)
SNR Note 1,2 dB -2.3 -5.7 -12.2
Note 1: See Table A.7.3.1.1-2 for other cell specific test
parameters.
Note 2: The SNR values are specifed for testing a UE which
supports 2RX on at least one band. For testing of a UE
which supports 4RX on all bands, the SNR during T3 is
modified as specified in section A.3.8.1.
A.7.3.23.2 Test Requirements
The requirements defined in section A.7.3.1.2 shall apply to this test case.
A.7.3.24 E-UTRAN FDD Radio Link Monitoring Test for In-sync for 5MHz
Bandwidth
A.7.3.24.1 Test Purpose and Environment
The purpose of this test case is the same as for the Test 2 defined in subclause A.7.3.2. The test parameters are the same
except those described in the following section. The listed parameter values in Tables A.7.3.24.1-1 and A.7.3.24.1-2
will replace the values of corresponding parameters in Tables A.7.3.2.1-1 and A.7.3.2.1-2.
Table A.7.3.24.1-1: General test parameters for E-UTRAN FDD in-sync testing
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.12 FDD As specified in
parameters clause A.3.1.2.1.
None of the PDCCH
are intended for the UE
under test
E-UTRA Channel Bandwidth MHz 5
(BW channel)
In sync Number of 3 In sync threshold Qin
transmission Control OFDM and the corresponding
parameters symbols hypothetical
(Note 1) PDCCH/PCFICH
transmission
parameters are as
specified in clause and
Table 7.6.1-2
respectively.
Out of sync Number of 3 Out of sync threshold
transmission Control OFDM Qout and the
parameters symbols corresponding
(Note 1) hypothetical
PDCCH/PCFICH
transmission
parameters are as
specified in
clause 7.6.1 and Table
7.6.1-1 respectively.
Note 1: See Table A.7.3.2.1-1 for other general test parameters.
Note 2: This test is performed according to the principle defined in section A.3.7.2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1011 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.24.1-2: Cell specific test parameters for E-UTRAN FDD (cell # 1) for in-sync radio link
monitoring test
Parameter Unit T1 T2 T3 T4 T5
BW channel MHz 5
OCNG Pattern
defined in A.3.2.1.16 OP.16 FDD
(FDD)
SNR Note 1,2 dB -2.3 -5.7 -12.2 -7.3 -2.3
Propagation condition ETU 70 Hz
Note 1: See Table A.7.3.2.1-2 for other general test parameters.
Note 2: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a
UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section
A.3.8.1.
A.7.3.24.2 Test Requirements
The requirements defined in section A.7.3.2.2 shall apply to this test case.
A.7.3.25 E-UTRAN FDD Radio Link Monitoring Test for In-sync in DRX for
5MHz Bandwidth
A.7.3.25.1 Test Purpose and Environment
The purpose of this test case is the same as for the Test 2 defined in subclause A.7.3.6. The test parameters are the same
except those described in the following section. The listed parameter values in Tables A.7.3.25.1-1 and A.7.3.25.1-2
will replace the values of corresponding parameters in Tables A.7.3.6.1-1 and A.7.3.6.1-2.
Table A.7.3.25.1-1: General test parameters for E-UTRAN FDD in-sync testing
Parameter Unit Value Comment
PCFICH/PDCCH/PHICH R.12 FDD As specified in
parameters clause A.3.1.2.1.
None of the PDCCH
are intended for the UE
under test
E-UTRA Channel Bandwidth MHz 5
(BW channel)
In sync Number of 3 In sync threshold Qin
transmissio Control OFDM and the corresponding
n symbols hypothetical
parameters PDCCH/PCFICH
(Note 1) transmission
parameters are as
specified in clause and
Table 7.6.1-2
respectively.
Out of sync Number of 3 Out of sync threshold
transmissio Control OFDM Qout and the
n symbols corresponding
parameters hypothetical
(Note 1) PDCCH/PCFICH
transmission
parameters are as
specified in
clause 7.6.1 and Table
7.6.1-1 respectively.
Note 1: See Table A.7.3.6.1-1 for other general test parameters.
Note 2: This test is performed according to the principle defined in section A.3.7.2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1012 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.25.1-2: Cell specific test parameters for E-UTRAN FDD (cell # 1) for in-sync radio link
monitoring test
Parameter Unit T1 T2 T3 T4 T5
BW channel MHz 5
OCNG Pattern
defined in A.3.2.1.16 OP.16 FDD
(FDD)
SNR Note 1,2 dB -2.3 -5.7 -12.2 -7.3 -2.3
Propagation condition AWGN
Note 1: See Table A.7.3.6.1-2 for other general test parameters.
Note 2: The SNR values are specifed for testing a UE which supports 2RX on at least one band. For testing of a
UE which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in section
A.3.8.1.
A.7.3.25.2 Test Requirements
The requirements defined in section A.7.3.6.2 shall apply to this test case.
A.7.3.26 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync for
UE Category 0
A.7.3.26.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN FDD radio
link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.26.1-1, A.7.3.26.1-2 and A.7.3.26.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.26.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1013 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.26.1-1: General test parameters for E-UTRAN FD-FDD out-of-sync testing for UE Category
0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA
RF channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD
carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1A As defined in section
5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 Out of sync threshold
parameters Control OFDM Qout and the
(Note 1) symbols corresponding
Aggregation CCE 8 hypothetical
level PDCCH/PCFICH
ρA, ρB -3 transmission
Ratio of PDCCH dB 4 parameters are as
to RS EPRE specified in section
Ratio of PCFICH dB 1 7.11.1 and Table
to RS EPRE 7.11.1-1 respectively.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table
0 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI
reporting periodicity
T1 s 1
T2 s 0.4
T3 s 0.5
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission
parameters need not be included in the Reference Measurement
Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1014 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.26.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for out-of-sync radio
link monitoring tests for UE Category 0
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PCFICH/PDCCH/PHIC R.7 FDD
H parameters defined
in A.3.1.2.1
OCNG Pattern defined OP.2 FDD
in A.3.2.1 (FDD)
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 4
PDCCH_RB dB 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB -2.1 -6.9 -12.9
Propagation condition ETU 70Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure
A.7.3.26.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1015 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.26.1-1: SNR variation for out-of-sync testing
A.7.3.26.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.27 E-UTRAN FD-FDD Radio Link Monitoring Test for In-sync for UE
Category 0
A.7.3.27.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN FD-FDD
radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.27.1-1 and A.7.3.27.1-2 below. There is one cell (cell 1), which is the
active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5
respectively. Figure A.7.3.27.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and
in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1016 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.27.1-1: General test parameters for E-UTRAN FD-FDD in-sync testing for UE Category 0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1C As defined in
clause 5.3.3.1.4 in TS
In sync 36.212
transmissio Number of 2 In sync threshold Qin and
n Control OFDM the corresponding
parameters symbols hypothetical
(Note 1) Aggregation CCE 4 PDCCH/PCFICH
level transmission parameters
ρA, ρB -3 are as specified in clause
Ratio of PDCCH dB 1 7.11.1 and Table 7.11.1-2
to RS EPRE respectively.
Ratio of dB 1
PCFICH to RS
EPRE
DCI format 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmissio Number of 2 Out of sync threshold Qout
n Control OFDM and the corresponding
parameters symbols hypothetical
(Note 1) Aggregation CCE 8 PDCCH/PCFICH
level transmission parameters
ρA, ρB -3 are as specified in
Ratio of PDCCH dB 4 clause 7.11.1 and Table
to RS EPRE 7.11.1-1 respectively.
Ratio of dB 1
PCFICH to RS
EPRE
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1
in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 0.5
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1017 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.27.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for in-sync radio link
monitoring test for UE Category 0
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel 1
Number
BW channel MHz 10
PCFICH/PDCCH/PHICH R.7 FDD
parameters defined in
clause A.3.1.2.1
OCNG Pattern defined in OP.2 FDD
A.3.2.1 (FDD)
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 1
PDCCH_RB dB 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 kHz -98
SNR Note 6 dB -2.1 -6.9 -12.9 -7.1 -2.1
Propagation condition ETU 70Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated
and a constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the
start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to
the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as
part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific
reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1,
SNR2, SNR3, SNR4 and SNR5 respectively in figure A.7.3.27.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1018 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.27.1-1: SNR variation for in-sync testing
A.7.3.27.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.28 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync in
DRX for UE category 0
A.7.3.28.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-
UTRAN FD-FDD radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.28.1-1, A.7.3.28.1-2, A.7.3.28.1-3 and A.7.3.28.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1,
T2 and T3 respectively. Figure A.7.3.28.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The
UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms. In the test,
DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and
to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be set to
“infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1019 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.28.1-1: General test parameters for E-UTRAN FD-FDD out-of-sync tests in DRX for UE
category 0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD
carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
CP length Normal
DCI format 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 Out of sync threshold
parameters Control OFDM Qout and the
(Note 1) symbols corresponding
Aggregation CCE 8 hypothetical
level PDCCH/PCFICH
ρA, ρB -3 transmission parameters
Ratio of dB 4 are as specified in
PDCCH to RS clause 7.11.1 and Table
EPRE 7.11.1-1 respectively.
Ratio of dB 1
PCFICH to RS
EPRE
DRX cycle ms 1280 See Table A.7.3.28.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table 7.2.2-
0 1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 32
T2 s 12.8
T3 s 13
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission
parameters need not be included in the Reference Measurement
Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1020 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.28.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for out-of-sync radio
link monitoring tests in DRX for UE category 0
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PCFICH/PDCCH/PHICH R.7 FDD
parameters defined in
clause A.3.1.2.1
OCNG Pattern defined in OP.2 FDD
A.3.2.1 (FDD)
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 4
PDCCH_RB dB 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB -6.1 -10.0 -14.0
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.28.1-1.
Table A.7.3.28.1-3: DRX-Configuration for E-UTRAN FD-FDD out-of-sync tests for UE category 0
Field Value Comment
onDurationTimer psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1021 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.28.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FD-FDD out-of-sync testing for
UE category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.28.1-1: SNR variation for out-of-sync testing in DRX
A.7.3.28.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6500 ms after the start of time
duration T3.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.29 E-UTRAN FD-FDD Radio Link Monitoring Test for In-sync in DRX
for UE Category 0
A.7.3.29.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-
UTRAN FD-FDD radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.29.1-1, A.7.3.29.1-2, A.7.3.29.1-3 and A.7.3.29.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1,
T2, T3, T4 and T5 respectively. Figure A.7.3.29.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms.
In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode
PDCCH and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be
set to “infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1022 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.29.1-1: General test parameters for E-UTRAN FD-FDD in-sync test in DRX for UE category
0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4
in TS 36.212
In sync Number of Control 2 In sync threshold Qin and the
transmission OFDM symbols corresponding hypothetical
parameters Aggregation level CCE 4 PDCCH/PCFICH
(Note 1) ρA, ρB -3 transmission parameters are
Ratio of PDCCH to 1 as specified in clause 7.11.1
RS EPRE and Table 7.11.1-2
Ratio of PCFICH to 1 respectively.
RS EPRE
DCI format 1A As defined in clause 5.3.3.1.3
in TS 36.212
Out of sync Number of Control 2 Out of sync threshold Qout
transmission OFDM symbols and the corresponding
parameters Aggregation level CCE 8 hypothetical PDCCH/PCFICH
(Note 1) ρA, ρB -3 transmission parameters are
Ratio of PDCCH to dB 4 as specified in clause 7.11.1
RS EPRE and Table 7.11.1-1
Ratio of PCFICH to dB 1 respectively.
RS EPRE
DRX cycle ms 40 See Table 7.3.29.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1023 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.29.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for in-sync radio link
monitoring test in DRX for UE category 0
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
PCFICH/PDCCH/PHICH R.7 FDD
parameters defined in
clause A.3.1.2.1
OCNG Pattern defined in
A.3.2.1 (FDD) OP.2 FDD
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 1
PDCCH_RB dB 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 8 dB -6.1 -10.0 -14.0 -10.1 -6.1
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.29.1-1.
Table A.7.3.29.1-3: DRX-Configuration for E-UTRAN FD-FDD out-of-sync tests for UE category 0
Field Value Comment
onDurationTimer psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
Table A.7.3.29.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FD-FDD out-of-sync testing for
UE category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1024 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.29.1-1: SNR variation for in-sync testing in DRX
A.7.3.29.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.30 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync for
UE Category 0
A.7.3.30.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN HD-FDD
radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.30.1-1, A.7.3.30.1-2 and A.7.3.30.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.30.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 10 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1025 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.30.1-1: General test parameters for E-UTRAN HD-FDD out-of-sync testing for UE Category
0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA
RF channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD
carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1A As defined in section
5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 Out of sync threshold
parameters Control OFDM Qout and the
(Note 1) symbols corresponding
Aggregation level CCE 8 hypothetical
ρA, ρB -3 PDCCH/PCFICH
Ratio of PDCCH dB 4 transmission
to RS EPRE parameters are as
Ratio of PCFICH dB 1 specified in section
to RS EPRE 7.11.1 and Table
7.11.1-1 respectively.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table
7.2.2-1 in TS 36.213.
CQI reporting periodicity ms [10] Minimum CQI
reporting periodicity
T1 s 1
T2 s 0.4
T3 s 0.5
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission
parameters need not be included in the Reference Measurement
Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1026 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.30.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for out-of-sync radio
link monitoring for UE Category 0
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PCFICH/PDCCH/PHIC R.4 HD-FDD
H parameters defined
in section A.3.1.2.3
OCNG Pattern defined
in A.3.2.1 (FDD) OP.2 FDD
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 4
PDCCH_RB dB 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB -1.2 -6.0 -12.0
Propagation condition ETU 70Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.30.1-
1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1027 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.30.1-1: SNR variation for out-of-sync testing
A.7.3.30.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.31 E-UTRAN HD-FDD Radio Link Monitoring Test for In-sync for UE
Category 0
A.7.3.31.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN HD-FDD
radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.31.1-1 and A.7.3.31.1-2 below. There is one cell (cell 1), which is the
active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5
respectively. Figure A.7.3.31.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and
in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 10 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1028 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.31.1-1: General test parameters for E-UTRAN HD-FDD in-sync testing
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4
in TS 36.212
In sync Number of Control 2 In sync threshold Qin and the
transmissio OFDM symbols corresponding hypothetical
n Aggregation level CCE 4 PDCCH/PCFICH transmission
parameters ρA, ρB -3 parameters are as specified in
(Note 1) Ratio of PDCCH dB 1 clause 7.11.1 and Table
to RS EPRE 7.11.1-2 respectively.
Ratio of PCFICH dB 1
to RS EPRE
DCI format 1A As defined in clause 5.3.3.1.3
in TS 36.212
Out of sync Number of Control 2 Out of sync threshold Qout and
transmissio OFDM symbols the corresponding
n Aggregation level CCE 8 hypothetical PDCCH/PCFICH
parameters ρA, ρB -3 transmission parameters are
(Note 1) Ratio of PDCCH dB 4 as specified in clause 7.11.1
to RS EPRE and Table 7.11.1-1
Ratio of PCFICH dB 1 respectively.
to RS EPRE
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms [10] Minimum CQI reporting
periodicity
T1 s 0.5
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1029 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.31.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for in-sync radio link
monitoring test for UE category 0
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
PCFICH/PDCCH/PHICH R.4 HD-FDD
parameters defined in
clause A.3.1.2.3
OCNG Pattern defined in
A.3.2.1 (FDD) OP.2 FDD
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 1
PDCCH_RB dB 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB -1.2 -6.0 -12.0 -6.2 -1.2
Propagation condition ETU 70Hz
Correlation Matrix and 2x1 low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.31.1-1.
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.31.1-1: SNR variation for in-sync testing
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1030 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.31.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.32 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync in
DRX for UE category 0
A.7.3.32.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-
UTRAN HD-FDD radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.32.1-1, A.7.3.32.1-2, A.7.3.32.1-3 and A.7.3.32.1-4. There
is one cell (cell 1), which is the active cell, in the test. The test consists of three successive time
periods, with time duration of T1, T2 and T3 respectively. Figure A.7.3.32.1-1 shows the variation of
the downlink SNR in the active cell to emulate out-of-sync and in-sync states. Prior to the start of the
time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be configured for periodic
CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 5ms. In the test, DRX configuration
is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and to
send periodic CQI during the period when On-duration timer is running. Time alignment timers shall
be set to “infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1031 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.32.1-1: General test parameters for E-UTRAN HD-FDD out-of-sync tests in DRX for UE
category 0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
CP length Normal
DCI format 1A As defined in clause 5.3.3.1.3
in TS 36.212
Out of sync Number of Control 2 Out of sync threshold Qout
transmission OFDM symbols and the corresponding
parameters Aggregation level CCE 8 hypothetical PDCCH/PCFICH
(Note 1) ρA, ρB -3 transmission parameters are
Ratio of PDCCH to dB 4 as specified in clause 7.11.1
RS EPRE and Table 7.11.1-1
Ratio of PCFICH to dB 1 respectively.
RS EPRE
DRX cycle ms 1280 See Table A.7.3.32.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 5 Minimum CQI reporting
periodicity
T1 s 32
T2 s 12.8
T3 s 13
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need
not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1032 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.32.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for out-of-sync radio
link monitoring tests in DRX for UE category 0
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PCFICH/PDCCH/PHICH R.4 HD-FDD
parameters specified in
clause A.3.1.2.3
OCNG Pattern defined in OP.2 FDD
A.3.2.1 (FDD)
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 4
PDCCH_RB dB 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB -5.4 -9.5 -13.5
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.32.1-
1.
Table A.7.3.32.1-3: DRX-Configuration for E-UTRAN HD-FDD out-of-sync test for UE category 0
Field Value Comment
onDurationTimer psf5 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1033 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.32.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.32.1-1: SNR variation for out-of-sync testing in DRX
A.7.3.32.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6500 ms after the start of time
duration T3.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.33 E-UTRAN HD-FDD Radio Link Monitoring Test for In-sync in DRX
for UE Category 0
A.7.3.33.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-
UTRAN HD-FDD radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.33.1-1, A.7.3.33.1-2, A.7.3.33.1-3 and A.7.3.33.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1,
T2, T3, T4 and T5 respectively. Figure A.7.3.33.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 5 ms.
In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode
PDCCH and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be
set to “infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1034 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.33.1-1: General test parameters for E-UTRAN HD-FDD in-sync test in DRX for UE category
0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
E-UTRA RF Channel Number 1 One E-UTRA FDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of Control In sync threshold Qin and the
2
transmission OFDM symbols corresponding hypothetical
parameters Aggregation level CCE PDCCH/PCFICH transmission
(Note 1) 4
parameters are as specified in
clause7.11.1 and Table 7.11.1-
ρA, ρB -3 2 respectively.
Ratio of PDCCH dB 1
to RS EPRE
Ratio of PCFICH dB 1
to RS EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of sync Number of Control Out of sync threshold Qout and
2
transmission OFDM symbols the corresponding hypothetical
parameters Aggregation level CCE PDCCH/PCFICH transmission
(Note 1) 8
parameters are as specified in
clause 7.11.1 and Table 7.11.1-
ρA, ρB -3 1 respectively.
Ratio of PDCCH dB 4
to RS EPRE
Ratio of PCFICH dB 1
to RS EPRE
DRX cycle ms 40 See Table A.7.3.33.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 5 Minimum CQI reporting
periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1035 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.33.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for in-sync radio link
monitoring test in DRX for UE category 0
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
PCFICH/PDCCH/PHICH R.4 HD-FDD
parameters specified in
clause A.3.1.2.3
OCNG Pattern defined in OP.2 FDD
A.3.2.1 (FDD)
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 1
PDCCH_RB dB 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB -5.4 -9.5 -13.5 -9.4 -5.4
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.33.1-1.
Table A.7.3.33.1-3: DRX-Configuration for E-UTRAN HD-FDD out-of-sync test for UE category 0
Field Value Comment
onDurationTimer psf5 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
Table A.7.3.33.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1036 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.33.1-1: SNR variation for in-sync testing in DRX
A.7.3.33.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.34 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync for UE
Category 0
A.7.3.34.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN TDD radio
link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.34.1-1, A.7.3.34.1-2 and A.7.3.34.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.34.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1037 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.34.1-1: General test parameters for E-UTRAN TDD out-of-sync testing for UE Category 0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA
RF channel number
1
E-UTRA RF Channel Number 1 One E-UTRA TDD
carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1A As defined in
section 5.3.3.1.3 in
Out of sync TS 36.212
transmission Number of 2 Out of sync
parameters Control OFDM threshold Qout and
(Note 1) symbols the corresponding
Aggregation CCE 8 hypothetical
level PDCCH/PCFICH
ρA, ρB -3 transmission
Ratio of PDCCH dB 4 parameters are as
to RS EPRE specified in section
Ratio of PCFICH dB 1 7.11.1 and Table
to RS EPRE 7.11.1-1
respectively.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table
7.2.2-1 in TS
36.213.
CQI reporting periodicity ms 1 Minimum CQI
reporting periodicity
T1 s 1
T2 s 0.4
T3 s 0.5
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission
parameters need not be included in the Reference Measurement
Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1038 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.34.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for out-of-sync radio link
monitoring for UE Category 0
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
Special subframe 6
configuration Note 1
Uplink-downlink 1
configuration Note 1
PCFICH/PDCCH/PHIC R.7 TDD
H parameters defined
in section A.3.1.2.2
OCNG Pattern defined
in A.3.2.2 (TDD) OP.2 TDD
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 4
PDCCH_RB dB 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 2 dB
OCNG_RBNote 2 dB
N oc dBm/15 -98
kHz
SNR Note 7 dB -1.6 -5.9 -11.9
Propagation condition ETU 70Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: For special subframe and uplink-downlink configurations
see Tables 4.2-1 and 4.2-2 in TS 36.211.
Note 2: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 3: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 4: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 5: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 6: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 7: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.34.1-
1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1039 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.34.1-1: SNR variation for out-of-sync testing
A.7.3.34.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all uplink subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (240 ms after the start of the time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.35 E-UTRAN TDD Radio Link Monitoring Test for In-sync for UE
category 0
A.7.3.35.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the E-UTRAN TDD radio
link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.35.1-1 and A.7.3.35.1-2 below. There is one cell (cell 1), which is the
active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5
respectively. Figure A.7.3.35.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and
in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1040 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.35.1-1: General test parameters for E-UTRAN TDD in-sync testing
Parameter Unit Value Comment
Test 1
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1C As defined in
clause 5.3.3.1.4 in TS
In sync 36.212
transmission Number of Control 2 In sync threshold Qin and
parameters OFDM symbols the corresponding
(Note 1) Aggregation level CCE 4 hypothetical
ρA, ρB -3 PDCCH/PCFICH
Ratio of PDCCH dB 1 transmission parameters are
to RS EPRE as specified in clause 7.11.1
Ratio of PCFICH dB 1 and Table 7.11.1-2
to RS EPRE respectively.
DCI format 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of Control 2 Out of sync threshold Qout
parameters OFDM symbols and the corresponding
(Note 1) Aggregation level CCE 8 hypothetical
ρA, ρB -3 PDCCH/PCFICH
Ratio of PDCCH dB 4 transmission parameters are
to RS EPRE as specified in clause 7.11.1
Ratio of PCFICH dB 1 and Table 7.11.1-1
to RS EPRE respectively.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
T1 s 0.5
T2 s 0.4
T3 s 1.46
T4 s 0.4
T5 s 1
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1041 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.35.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for in-sync radio link
monitoring test
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
Special subframe 6
configuration Note 1
Uplink-downlink configuration 1
Note 1
PCFICH/PDCCH/PHICH R.7 TDD
parameters defined in section
A.3.1.2.2
OCNG Pattern defined in
A.3.2.2 (TDD) OP.2 TDD
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 1
PDCCH_RB dB 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 2 dB
OCNG_RBNote 2 dB
N oc dBm/15 -98
kHz
SNR Note 7 dB -1.6 -5.9 -11.9 -6.6 -1.6
Propagation condition ETU 70Hz
Correlation Matrix and 2x1 low
Antenna Configuration
Note 1: For special subframe and uplink-downlink configurations see Tables 4.2-1 and 4.2-2 in TS 36.211.
Note 2: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 3: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 4: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 5: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 6: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 7: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.35.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1042 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[380+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.35.1-1: SNR variation for in-sync testing
A.7.3.35.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (420 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.36 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync in DRX
for UE category 0
A.7.3.36.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-
UTRAN TDD radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.36.1-1, A.7.3.36.1-2, A.7.3.36.1-3 and A.7.3.36.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1,
T2 and T3 respectively. Figure A.7.3.36.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The
UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms. In the test,
DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and
to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be set to
“infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1043 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.36.1-1: General test parameters for E-UTRAN TDD out-of-sync test in DRX for UE
category 0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA
RF channel number 1
E-UTRA RF Channel Number 1 One E-UTRA TDD
carrier frequency is
used.
E-UTRA Channel Bandwidth MHz 10
(BWchannel)
CP length Normal
DCI format 1A As defined in
clause 5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 Out of sync threshold
parameters Control OFDM Qout and the
(Note 1) symbols corresponding
Aggregation CCE 8 hypothetical
level PDCCH/PCFICH
ρA, ρB -3 transmission
Ratio of dB 4 parameters are as
PDCCH to RS specified in
EPRE clause 7.11.1 and
Ratio of dB 1 Table 7.11.1-1
PCFICH to RS respectively.
EPRE
DRX cycle ms 1280 See Table A.7.3.36.1-
3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table
7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI
reporting periodicity
T1 s 32
T2 s 12.8
T3 s 13
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission
parameters need not be included in the Reference Measurement
Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1044 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.36.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for out-of-sync radio link
monitoring test in DRX for UE category 0
Parameter Unit Test 2
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
Special subframe 6
configuration Note 1
Uplink-downlink 1
configuration Note 1
PCFICH/PDCCH/PHICH R.7 TDD
parameters defined in
section A.3.1.2.2
OCNG Pattern defined in OP.2 TDD
A.3.2.2 (TDD)
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 4
PDCCH_RB dB 4
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote2 dB
OCNG_RBNote2 dB
N oc dBm/15 -98
kHz
SNR Note 7 dB -5.6 -9.6 -13.6
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: For special subframe and uplink-downlink configurations
see Tables 4.2-1 and 4.2-2 in TS 36.211.
Note 2: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 3: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 4: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 5: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 6: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 7: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.36.1-
1.
Table A.7.3.36.1-3: DRX-Configuration for E-UTRAN TDD out-of-sync test for UE category 0
Field Value Comment
onDurationTimer psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1045 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.36.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD out-of-sync testing for UE
category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 2 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.36.1-1: SNR variation for out-of-sync testing in DRX
A.7.3.36.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the uplink subframe according to the configured CQI reporting mode (PUCCH 1-
0).
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6500 ms after the start of time
duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.37 E-UTRAN TDD Radio Link Monitoring Test for In-sync in DRX for
UE category 0
A.7.3.37.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD category 0 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly verify the E-
UTRAN TDD radio link monitoring requirements in clause 7.11.
The test parameters are given in Tables A.7.3.37.1-1, A.7.3.37.1-2, A.7.3.37.1-3 and A.7.3.37.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1,
T2, T3, T4 and T5 respectively. Figure A.7.3.37.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode
PDCCH and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be
set to “infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1046 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.37.1-1: General test parameters for E-UTRAN TDD in-sync test in DRX for UE category 0
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
E-UTRA RF Channel Number 1 One E-UTRA TDD carrier
frequency is used.
E-UTRA Channel Bandwidth MHz 10
(BW channel)
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of Control 2 In sync threshold Qin and the
transmission OFDM symbols corresponding hypothetical
parameters Aggregation level CCE 4 PDCCH/PCFICH transmission
(Note 1) ρA, ρB -3 parameters are as specified in
Ratio of PDCCH dB 1 clause 7.11.1 and Table 7.11.1-
to RS EPRE 2 respectively.
Ratio of PCFICH dB 1
to RS EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of sync Number of Control 2 Out of sync threshold Qout and
transmission OFDM symbols the corresponding hypothetical
parameters Aggregation level CCE 8 PDCCH/PCFICH transmission
(Note 1) ρA, ρB -3 parameters are as specified in
Ratio of PDCCH dB 4 clause 7.11.1 and Table 7.11.1-
to RS EPRE 1 respectively.
Ratio of PCFICH dB 1
to RS EPRE
DRX cycle ms 40 See Table A.7.3.37.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS
36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1047 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.37.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for in-sync radio link
monitoring test in DRX for UE category 0
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
Special subframe 6
configuration Note 1
Uplink-downlink configuration 1
Note 1
PCFICH/PDCCH/PHICH R.7 TDD
parameters defined in section
A.3.1.2.2
OCNG Pattern defined in
A.3.2.2 (TDD) OP.2 TDD
ρA, ρB -3
PCFICH_RB dB 1
PDCCH_RA dB 1
PDCCH_RB dB 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote2 dB
OCNG_RBNote2 dB
N oc dBm/15 -98
kHz
SNR Note 7 dB -5.6 -9.6 -13.6 -9.6 -5.6
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: For special subframe and uplink-downlink configurations see Tables 4.2-1 and 4.2-2 in TS 36.211.
Note 2: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 3: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 4: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 5: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 6: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 7: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.37.1-1.
Table A.7.3.37.1-3: DRX-Configuration for E-UTRAN TDD out-of-sync test for UE category 0
Field Value Comment
onDurationTimer psf2 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1048 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.37.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD out-of-sync testing for UE
category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 2 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
Figure A.7.3.37.1-1: SNR variation for in-sync testing in DRX
A.7.3.37.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the uplink subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.38 E-UTRAN FDD-FDD DC Radio Link Monitoring Test for Out-of-sync
in DRX in synchronous DC
A.7.3.38.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync for the purpose of monitoring downlink
radio link quality of the PSCell when DRX is used. This test will partly verify the E-UTRAN FDD radio link
monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.38.1-1, A.7.3.38.1-2, A.7.3.38.1-3, and A.7.3.38.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of three successive time periods with time duration of
T1, T2 and T3 respectively. Figure A.7.3.38.1-1 shows the variation of the downlink SNR in the PCell and PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms. In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e.
UE tries to decode PDCCH and to send periodic CQI during the period when On-duration timer is running. Time
alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1049 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.38.1-1: General test parameters for E-UTRAN FDD out-of-sync tests in DRX in
synchronous dual connectivity
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is PCell on E-UTRA RF channel number 1, and
Cell 2 cell 2 is PSCell on E-UTRA RF channel number 2
CP length Normal
E-UTRA RF Channel Number 1, 2 Two E-UTRA FDD carrier frequencies are used.
E-UTRA Channel Bandwidth MHz 5, 10, 20
(BWchannel)
Correlation Matrix and Antenna 2x2 Low Correlation Matrix and Antenna Configuration are
Configuration defined in TS 36.101 [5] Annex B.2.3.2
DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
Number of Control 5MHz: 3 Out of sync threshold Qout and the corresponding
OFDM symbols 10MHz: 2 hypothetical PDCCH/PCFICH transmission parameters
Out of sync 20MHz: 2 are as specified in clause 7.6.1 and Table 7.6.1-1
transmission Aggregation level CCE 8 respectively.
parameters ρA, ρB -3
(Note 1) Ratio of PDCCH dB 1
to RS EPRE
Ratio of PCFICH dB 1
to RS EPRE
DRX cycle on cell 1 ms 640 See Table A.7.3.38.1-3
DRX cycle on cell 2 ms 40 See Table A.7.3.38.1-3
Timing offset between cell 1 and μs 33 For synchronous dual connectivity
cell 2
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1; N313 = 1; N314 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 0 T313 is disabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
T1 s 4
T2 s 1.6
T3 s 1.8
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1050 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.38.1-2: Cell specific test parameters for E-UTRAN FDD out-of-sync radio link monitoring
in DRX in synchronous dual connectivity
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel Number 1 2
BW channel MHz 5, 10, 20 5, 10, 20
Correlation Matrix and
2x2 Low 2x2 Low
Antenna Configuration
PCFICH/PDCCH/PHICH
5MHz: R.12 FDD 5MHz: R.12 FDD
parameters
10MHz: R.7 FDD 10MHz: R.7 FDD
None of the PDCCH are
20MHz: R.13 FDD 20MHz: R.13 FDD
intended for the UE under test
OCNG Pattern 5MHz: OP.16 FDD 5MHz: OP.16 FDD
10MHz: OP.2 FDD 10MHz: OP.2 FDD
20MHz: OP.12 FDD 20MHz: OP.12 FDD
ρA, ρB -3 -3
PCFICH_RB dB 1 1
PDCCH_RA dB 1 1
PDCCH_RB dB 1 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
-3 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,7 (5MHz bandwidth) dB -2.3 -2.3 -2.3 -2.3 -5.7 -12.2
SNR Note 6,7 (10MHz dB
-2.3 -2.3 -2.3 -2.3 -6.2 -12.2
bandwidth)
SNR Note 6,7 (20MHz dB
-2.9 -2.9 -2.9 -2.9 -6.8 -12.8
bandwidth)
N oc dBm/15 kHz -98 -98
Propagation condition ETU 70 Hz ETU 70 Hz
Time offset to cell1 μs - 33
Note 1: OCNG shall be used such that the resources in cell 1 and cell 2 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, and T3 are denoted as SNR1, SNR2 and SNR3 respectively in figure
A.7.3.38.1-1.
Note 7: The SNR values are specifed for testing a UE which supports 2RX on the PSCell frequency. For testing of a
UE which only supports 4RX on the PSCell frequency, the SNR during T3 is modified as specified in section
A.3.8.1.
Table A.7.3.38.1-3: DRX-Configuration for E-UTRAN FDD out-of-sync tests in synchronous dual
connectivity
Value
Field Comment
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in clause 6.3.2 in TS 36.331
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset Sf640 Sf40
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1051 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.38.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD out-of-sync testing in
synchronous dual connectivity
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS 36.331 and
sr-ConfigIndex 0
section 10.1 in TS 36.213.
SNR level Cell 1 SNR level
SNR 1
Qin
SNR 2
Qout
SNR 3
Cell 2 SNR level
A B C
D1 ms
T1 T2 T3
Figure A.7.3.38.1-1 SNR variation for out-of-sync testing in DRX
A.7.3.38.2 Test Requirements
The UE behaviour during time durations T1, T2, and T3 shall be as follows:
During time durations T1, T2 and T3, the UE shall transmit uplink signal at least in all subframes configured for CQI
transmission on Cell1.
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the uplink subframe on Cell2.
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 900 ms after the start of time
duration T3) on PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.39 E-UTRAN FDD-FDD DC Radio Link Monitoring Test for Out-of-sync
in DRX in asynchronous DC
A.7.3.39.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PSCell when DRX is used in asynchronous dual connectivity. This test
will partly verify the E-UTRAN FDD radio link monitoring requirements in section 7.6.
The test parameters are given in Tables A.7.3.39.1-1, A.7.3.39.1-2, A.7.3.39.1-3 and A.7.3.39.1-4. There are two cells
in the test. Cell 1 is PCell in MCG and cell 2 is PSCell in SCG. Before the test starts the UE is connected to cell 1 on
radio channel 1 and to cell 2 on radio channel 2. The test consists of three successive time periods, with time duration of
T1, T2 and T3 respectively. The downlink SNR in cell 1 keeps constant in the test. Figure A.7.3.39.1-1 shows the
variation of the downlink SNR in the cell 2 to emulate out-of-sync and in-sync states. Prior to the start of the time
duration T1, the UE shall be fully synchronized to cell 1 and cell 2 in asynchronous dual connectivity. For both cells,
the UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms. In the
test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1052 ETSI TS 136 133 V14.3.0 (2017-04)
and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be set to
“infinity” so that UL timing alignment is maintained during the test.
Table A.7.3.39.1-1: General test parameters for E-UTRAN FDD out-of-sync in DRX
Parameter Unit Value Comment
Active cells Cell 1 and Cell 1 (PCell) is on E-UTRA RF
cell 2 channel number 1 and cell 2
(PSCell) is on E-UTRA RF channel
number 2
CP length Normal
Correlation Matrix and Antenna 2x2 Low Correlation Matrix and Antenna
Configuration Configuration are defined in TS
36.101 [5] Annex B.2.3.2
DCI format 1A As defined in section 5.3.3.1.3 in
TS 36.212
Out of sync Number of Control 5MHz: 3 Out of sync threshold Qout and the
transmission OFDM symbols 10MHz: 2 corresponding hypothetical
parameters 20MHz: 2 PDCCH/PCFICH transmission
(Note 1) Aggregation level CCE 8 parameters are as specified in
ρA, ρB -3 section 7.6.1 and Table 7.6.1-1
Ratio of PDCCH to dB 1 respectively.
RS EPRE
Ratio of PCFICH to dB 1
RS EPRE
DRX cycle in cell 1 ms 640 See Table A.7.3.39.1-3
DRX cycle in cell 2 ms 40 See Table A.7.3.39.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1;
N313 = 1; N314 = 1;
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 0 T313 is disabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS
36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
T1 s 4
T2 s 1.6
T3 s 1.8
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be
included in the Reference Measurement Channel.
Note 2: The test parameters in the table apply to both cell 1 and cell 2 unless specified otherwise.
Note 3: Even a UE capable of both synchronous and asynchronous DC operations is required to pass
this test case in accordance with the principle defined in section A.3.6.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1053 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.39.1-2: Cell specific test parameters for E-UTRAN FDD for out-of-sync radio link
monitoring in DRX
Parameter Unit Cell 1 (PCell) Cell 2 (PSCell)
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 2
Number
E-UTRA Channel MHz 5, 10, 20 5, 10, 20
Bandwidth (BW channel)
PCFICH/PDCCH/PHI 5MHz: R.12 FDD 5MHz: R.12 FDD
CH parameters. 10MHz: R.7 FDD 10MHz: R.7 FDD
None of the PDCCH 20MHz: R.13 FDD 20MHz: R.13 FDD
are intended for the
UE under test.
Correlation Matrix 2x2 Low 2x2 Low
and Antenna
Configuration
OCNG Pattern 5MHz: OP.16 FDD
defined in A.3.2.1 10MHz: OP.2 FDD 5MHz: OP.16 FDD
(FDD) 20MHz: OP.12 FDD 10MHz: OP.2 FDD
20MHz: OP.12 FDD
ρA, ρB -3 -3
PCFICH_RB dB 1 1
PDCCH_RA dB 1 1
PDCCH_RB dB 1 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB -3 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 5MHz dB -2.3 -2.3 -2.3 -2.3 -5.7 -12.2
6,8 BW channel
10MHz dB -2.3 -2.3 -2.3 -2.3 -6.2 -12.2
BW channel
20MHz dB -2.9 -2.9 -2.9 -2.9 -6.8 -12.8
BW channel
N oc dBm/15 -98
kHz -98
Propagation condition ETU 70 Hz ETU 70 Hz
Receive time offset to μs - 500
cell1 Note 7
Note 1: OCNG shall be used such that the resources in Cell 1 and Cell 2 are fully allocated and a
constant total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time
period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time
period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal
REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3
respectively in figure A.7.3.39.1-1.
Note 7: Receive time difference between subframe boundaries of signals received from the two
cells at the UE antenna connector including time alignment error between the two cells.
Note 8: The SNR values are specifed for testing a UE which supports 2RX on the PSCell
frequency. For testing of a UE which only supports 4RX on the PSCell frequency, the
SNR during T3 is modified as specified in section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1054 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.39.1-3: DRX-Configuration for E-UTRAN FDD out-of-sync tests
Value Comment
Field
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in
drx-InactivityTimer psf1 psf1 section 6.3.2 in
drx-RetransmissionTimer psf1 psf1 3GPP TS 36.331
longDRX-CycleStartOffset sf640 sf40
shortDRX disable disable
Table A.7.3.39.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD out-of-sync testing
Field Value Comment
As specified in section 6.3.2 in
TimeAlignmentTimer infinity
3GPP TS 36.331
For further information see section
sr-ConfigIndex 0 6.3.2 in 3GPP TS 36.331 and
section10.1 in 3GPP TS 36.213.
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.39.1-1 SNR variation for out-of-sync test in DRX
A.7.3.39.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
In the test, during time durations T1, T2 and T3, the UE shall transmit uplink signal on cell 1 at least once every DRX
cycle, in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode (PUCCH 1-
0).
In the test, during the period from time point A to time point B the UE shall transmit uplink signal on cell 2 at least once
every DRX cycle, in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode
(PUCCH 1-0).
In the test, the UE shall stop transmitting uplink signal on cell 2 no later than time point C (duration D1 = 900 ms after
the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1055 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.40 E-UTRAN TDD-TDD DC Radio Link Monitoring Test for Out-of-sync
in DRX in synchronous DC
A.7.3.40.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync for the purpose of monitoring downlink
radio link quality of the PSCell when DRX is used. This test will partly verify the E-UTRAN TDD radio link
monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.40.1-1, A.7.3.40.1-2, A.7.3.40.1-3, and A.7.3.40.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of three successive time periods with time duration of
T1, T2 and T3 respectively. Figure A.7.3.40.1-1 shows the variation of the downlink SNR in the PCell and PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 1 ms. In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e.
UE tries to decode PDCCH and to send periodic CQI during the period when On-duration timer is running. Time
alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the test.
Table A.7.3.40.1-1: General test parameters for E-UTRAN TDD out-of-sync tests in DRX in
synchronous dual connectivity
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is PCell on E-UTRA RF channel number 1, and
Cell 2 cell 2 is PSCell on E-UTRA RF channel number 2
CP length Normal
E-UTRA RF Channel Number 1, 2 Two E-UTRA TDD carrier frequencies are used.
E-UTRA Channel Bandwidth MHz 5, 10, 20
(BWchannel)
Correlation Matrix and Antenna 2x2 Low Correlation Matrix and Antenna Configuration are
Configuration defined in TS 36.101 [5] Annex B.2.3.2
DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
Number of Control 5MHz: 3 Out of sync threshold Qout and the corresponding
OFDM symbols 10MHz: 2 hypothetical PDCCH/PCFICH transmission parameters
Out of sync 20MHz: 2 are as specified in clause 7.6.1 and Table 7.6.1-1
transmission Aggregation level CCE 8 respectively.
parameters ρA, ρB -3
(Note 1) Ratio of PDCCH dB 1
to RS EPRE
Ratio of PCFICH dB 1
to RS EPRE
DRX cycle on cell 1 ms 640 See Table A.7.3.40.1-3
DRX cycle on cell 2 ms 40 See Table A.7.3.40.1-3
Timing offset between cell 1 and μs 33 For synchronous dual connectivity
cell 2
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1; N313 = 1; N314 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 0 T313 is disabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting periodicity
T1 s 4
T2 s 1.6
T3 s 1.8
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1056 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.40.1-2: Cell specific test parameters for E-UTRAN TDD out-of-sync radio link monitoring
in DRX in synchronous dual connectivity
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel Number 1 2
BW channel MHz 5, 10, 20 5, 10, 20
Correlation Matrix and
2x2 Low 2x2 Low
Antenna Configuration
Special subframe
6 6
configurationNote1
Uplink-downlink
1 1
configurationNote2
PCFICH/PDCCH/PHICH
5MHz: R.12 TDD 5MHz: R.12 TDD
parameters
10MHz: R.7 TDD 10MHz: R.7 TDD
None of the PDCCH are
20MHz: R.13 TDD 20MHz: R.13 TDD
intended for the UE under test
OCNG Pattern 5MHz: OP.10 TDD 5MHz: OP.10 TDD
10MHz: OP.2 TDD 10MHz: OP.2 TDD
20MHz: OP.8 TDD 20MHz: OP.8 TDD
ρA, ρB -3 -3
PCFICH_RB dB 1 1
PDCCH_RA dB 1 1
PDCCH_RB dB 1 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
-3 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
SNR Note 8,9 (5MHz bandwidth) dB -1.6 -1.6 -1.6 -1.6 -5.2 -11.9
SNR Note 8,9 (10MHz dB
-2.3 -2.3 -2.3 -2.3 -5.9 -11.9
bandwidth)
SNR Note 8,9 (20MHz dB -3.0 -3.0 -3.0 -3.0
-6.6 -12.6
bandwidth)
N oc dBm/15 kHz -98 -98
Propagation condition ETU 70 Hz ETU 70 Hz
Time offset to cell1 μs - 33
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3 respectively in figure
A.7.3.40.1-1.
Note 9: The SNR values are specifed for testing a UE which supports 2RX on the PSCell frequency. For testing of a
UE which only supports 4RX on the PSCell frequency, the SNR during T3 is modified as specified in section
A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1057 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.40.1-3: DRX-Configuration for E-UTRAN TDD out-of-sync tests in synchronous dual
connectivity
Value
Field Comment
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in clause 6.3.2 in TS 36.331
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset Sf640 Sf40
shortDRX disable disable
Table A.7.3.26.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD out-of-sync testing in
synchronous dual connectivity
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS 36.331 and
sr-ConfigIndex 0
section 10.1 in TS 36.213.
SNR level Cell 1 SNR level
SNR 1
Qin
SNR 2
Qout
SNR 3
Cell 2 SNR level
A B C
D1 ms
T1 T2 T3
Figure A.7.3.40.1-1 SNR variation for out-of-sync testing in DRX
A.7.3.40.2 Test Requirements
The UE behaviour during time durations T1, T2, and T3 shall be as follows:
During time durations T1, T2 and T3, the UE shall transmit uplink signal at least in all subframes configured for CQI
transmission on Cell1.
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the uplink subframe on Cell2.
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 900 ms after the start of time
duration T3) on PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1058 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.41 E-UTRAN FDD-FDD Radio Link Monitoring Test for In-sync in DRX
in synchronous dual connectivity
A.7.3.41.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PSCell when DRX is used in dual connectivity. This test will partly verify
the E-UTRAN FDD radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.41.1-1, A.7.3.41.1-2, A.7.3.41.1-3 and A.7.3.41.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.41.1-1 shows the variation of the downlink SNR in the PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms. In the test, DRX configuration for PCell and PSCell is enabled and DRX inactivity timer has
already been expired, i.e. UE tries to decode PDCCH and to send periodic CQI during the period when On-duration
timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the
test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1059 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.41.1-1: General test parameters for E-UTRAN FDD-FDD Radio Link Monitoring Test for In-
sync in DRX in synchronous dual connectivity
Parameter Unit Value Comment
E-UTRA RF Channel Number 1, 2 Two E-UTRA FDD carrier frequency are
used.
Active cell Cell 1, Cell 2 Cell 1 is PCell on E-UTRA RF channel
number 1, and cell 2 is PSCell on E-UTRA
RF channel number 2
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4 in TS
36.212
In sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 4 In sync threshold Qin and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS 0 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-2 respectively.
Ratio of PCFICH to RS 4
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in TS
36.212
Out of sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 8 Out of sync threshold Qout and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS dB 4 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-1 respectively.
Ratio of PCFICH to RS dB 4
EPRE
DRX cycle on Cell 1 ms 640 See Table A.7.3.41.1-3
DRX cycle on Cell 2 ms 40 See Table A.7.3.41.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1, N313 = 1, N314 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 2000 T313 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
Note 2: Even a UE capable of both synchronous and asynchronous DC operations is required to pass this test
case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1060 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.41.1-2: Cell specific test parameters for E-UTRAN FDD-FDD Radio Link Monitoring Test
for In-sync in DRX in synchronous dual connectivity
Cell 1(PCell) Cell 2 (PSCell)
Parameter Unit
T1 ~ T5 T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1 2
BW channel MHz 5: NRB,c = 25 5: NRB,c = 25
10: NRB,c = 50 10: NRB,c = 50
20: NRB,c = 100 20: NRB,c = 100
PCFICH/PDCCH/PHICH 5MHz: R.11 FDD 5MHz: R.11 FDD
parameters defined in A.3.1.2.1 10MHz: R.6 FDD 10MHz: R.6 FDD
20MHz: R.10 FDD 20MHz: R.10 FDD
OCNG Pattern defined in A.3.2.1 5MHz: OP.16 FDD 5MHz: OP.16 FDD
(FDD) 10MHz: OP.2 FDD 10MHz: OP.2 FDD
20MHz: OP.12 FDD 20MHz: OP.12 FDD
ρA, ρB 0 0
PCFICH_RB dB 4 4
PDCCH_RA dB 0 0
PDCCH_RB dB 0 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
0 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,8 5MHz BW channel -2.3 -2.3 -5.7 -12.2 -7.3 -2.3
10MHz dB -4.7 -4.7 -9.5 -13.5 -8.7 -4.7
BW channel
20MHz -4.7 -4.7 -9.5 -13.5 -8.7 -4.7
BW channel
N oc dBm/15 -98
kHz
Propagation condition AWGN AWGN
Correlation Matrix and Antenna 1x2 1x2
Configuration
Receive time offset to cell1 Note 7 μs - 33
Note 1: OCNG shall be used such that the resources in cell 1 and cell 2 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR of cell 2 in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.41.1-1.
Note 7: Receive time difference between subframe boundaries of signals received from the two cells at the UE
antenna connector including time alignment error between the two cells.
Note 8: The SNR values are specifed for testing a UE which supports 2RX on the PSCell frequency. For testing of a
UE which only supports 4RX on the PSCell frequency, the SNR during T3 and T4 is modified as specified in
section A.3.8.1.
Table A.7.3.41.1-3: DRX-Configuration for E-UTRAN FDD-FDD Radio Link Monitoring Test for In-sync
in DRX in synchronous dual connectivity
Value Comment
Field
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in
drx-InactivityTimer psf1 psf1 section 6.3.2 in
drx-RetransmissionTimer psf1 psf1 3GPP TS 36.331
longDRX-CycleStartOffset sf640 sf40
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1061 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.41.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD-FDD Radio Link Monitoring
Test for In-sync in DRX in synchronous dual connectivity
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS
sr-ConfigIndex 0
36.331 and section10.1 in TS 36.213.
Figure A.7.3.41.1-1 SNR variation of cell 2 (PSCell) for in-sync testing in DRX
A.7.3.41.2 Test Requirements
The UE behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0) on PCell and PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.42 E-UTRAN FDD-FDD DC Radio Link Monitoring Test for In-sync in
DRX in asynchronous DC
A.7.3.42.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PSCell when DRX is used in asynchronous dual connectivity. This test
will partly verify the E-UTRAN FDD radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.42.1-1, A.7.3.42.1-2, A.7.3.42.1-3 and A.7.3.42.1-4. There are two cells
in the test. Cell 1 is PCell in MCG and cell 2 is PSCell in SCG. Before the test starts the UE is connected to cell 1 on
radio channel 1 and to cell 2 on radio channel 2. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. The downlink SNR in cell 1 keeps constant in the test. Figure A.7.3.42.1-1 shows
the variation of the downlink SNR in cell 2 to emulate out-of-sync and in-sync states. Prior to the start of the time
duration T1, the UE shall be fully synchronized to cell 1 and cell 2 in asynchronous dual connectivity. For both cell 1
and cell 2, the UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2
ms. In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode
PDCCH and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall be
set to “infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1062 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.42.1-1: General test parameters for E-UTRAN FDD in-sync test in DRX
Parameter Unit Value Comment
Active cells Cell 1 and Cell 1 (PCell) is on E-UTRA RF
cell 2 channel number 1 and cell 2
(PSCell) is on E-UTRA RF
channel number 2
CP length Normal
Antenna Configuration 1x2
DCI format 1C As defined in clause 5.3.3.1.4 in
TS 36.212
In sync Number of Control 5MHz: 3 In sync threshold Qin and the
transmissio OFDM symbols 10MHz: 2 corresponding hypothetical
n 20MHz: 2 PDCCH/PCFICH transmission
parameters Aggregation level CCE 4 parameters are as specified in
(Note 1) ρA, ρB 0 clause and Table 7.6.1-2
Ratio of PDCCH to 0 respectively.
RS EPRE
Ratio of PCFICH to 4
RS EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in
TS 36.212
Out of sync Number of Control 2 Out of sync threshold Qout and
transmissio OFDM symbols the corresponding hypothetical
n Aggregation level CCE 8 PDCCH/PCFICH transmission
parameters ρA, ρB 0 parameters are as specified in
(Note 1) Ratio of PDCCH to dB 4 clause 7.6.1 and Table 7.6.1-1
RS EPRE respectively.
Ratio of PCFICH to dB 4
RS EPRE
DRX cycle in cell 1 ms 640 See Table A.7.3.42.1-3
DRX cycle in cell 2 ms 40 See Table A.7.3.42.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1;
N313 = 1; N314 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 2000 T313 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table 7.2.2-1 in
0 TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission
parameters need not be included in the Reference Measurement Channel.
Note 2: The parameters in the table apply to both cell 1 and cell 2 unless defined otherwise.
Note 3: Even a UE capable of both synchronous and asynchronous DC operations is
required to pass this test case in accordance with the principle defined in section
A.3.6.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1063 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.42.1-2: Cell specific test parameters for E-UTRAN FDD for in-sync radio link monitoring in
DRX
Cell 1 (PCell) Cell 2 (PSCell)
Parameter Unit
T1 ~ T5 T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1 2
E-UTRA Channel Bandwidth MHz 5, 10, 20 5, 10, 20
(BW channel)
PCFICH/PDCCH/PHICH 5MHz: R.11 5MHz: R.11 FDD
parameters. FDD 10MHz: R.6 FDD
None of the PDCCH are intended 10MHz: R.6 20MHz: R.10 FDD
for the UE under test. FDD
20MHz: R.10
FDD
OCNG Pattern 5MHz: OP.16
FDD
5MHz: OP.16 FDD
10MHz: OP.2
10MHz: OP.2 FDD
FDD
20MHz: OP.12 FDD
20MHz: OP.12
FDD
ρA, ρB 0 0
PCFICH_RB dB 4 4
PDCCH_RA dB 0 0
PDCCH_RB dB 0 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
0 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,8 5MHz BW channel dB -2.3 -2.3 -5.7 -12.2 -7.3 -2.3
10MHz BW channel dB -4.7 -4.7 -9.5 -13.5 -8.7 -4.7
20MHz BW channel dB -4.7 -4.7 -9.5 -13.5 -8.7 -4.7
N oc dBm/15 -98
kHz
Propagation condition AWGN
Receive time offset to cell1 Note 7 μs - 500
Note 1: OCNG shall be used such that the resources in cell 1 and cell 2 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR of cell 2 in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.6.1-1.
Note 7: Receive time difference between subframe boundaries of signals received from the two cells at the UE
antenna connector including time alignment error between the two cells.
Note 8: The SNR values are specifed for testing a UE which supports 2RX on the PSCell frequency. For testing of a
UE which only supports 4RX on the PSCell frequency, the SNR during T3 and T4 is modified as specified in
section A.3.8.1.
Table A.7.3.42.1-3: DRX-Configuration for E-UTRAN FDD out-of-sync tests
Field Cell 1 Cell 2 Comment
onDurationTimer psf2 psf2 As specified in clause 6.3.2 in
drx-InactivityTimer psf1 psf1 TS 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf640 sf40
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1064 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.42.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD out-of-sync testing
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see clause 6.3.2
sr-ConfigIndex 0 in TS 36.331 and section10.1 in TS
36.213.
Figure A.7.3.42.1-1 Cell 2 SNR variation for in-sync testing in DRX
A.7.3.42.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal on cell 2 at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to
the configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.43 E-UTRAN TDD-TDD Radio Link Monitoring Test for In-sync in DRX
in synchronous dual connectivity
A.7.3.43.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PSCell when DRX is used in dual connectivity. This test will partly verify
the E-UTRAN TDD radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.43.1-1, A.7.3.43.1-2, A.7.3.43.1-3 and A.7.3.43.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.43.1-1 shows the variation of the downlink SNR in the PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 1 ms. In the test, DRX configuration for PCell and PSCell is enabled and DRX inactivity timer has
already been expired, i.e. UE tries to decode PDCCH and to send periodic CQI during the period when On-duration
timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the
test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1065 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.43.1-1: General test parameters for E-UTRAN TDD-TDD Radio Link Monitoring Test for In-
sync in DRX in synchronous dual connectivity
Parameter Unit Value Comment
E-UTRA RF Channel Number 1, 2 Two E-UTRA TDD carrier frequency are
used.
Active cell Cell 1, Cell 2 Cell 1 is PCell on E-UTRA RF channel
number 1, and cell 2 is PSCell on E-UTRA
RF channel number 2
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4 in TS
36.212
In sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 4 In sync threshold Qin and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS 0 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-2 respectively.
Ratio of PCFICH to RS 4
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in TS
36.212
Out of sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 8 Out of sync threshold Qout and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS dB 4 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-1 respectively.
Ratio of PCFICH to RS dB 4
EPRE
DRX cycle on Cell 1 ms 640 See Table A.7.3.43.1-3
DRX cycle on Cell 2 ms 40 See Table A.7.3.43.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1, N313 = 1, N314 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 2000 T313 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
Note 2: Even a UE capable of both synchronous and asynchronous DC operations is required to pass this test
case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1066 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.43.1-2: Cell specific test parameters for E-UTRAN TDD-TDD Radio Link Monitoring Test
for In-sync in DRX in synchronous dual connectivity
Cell 1(PCell) Cell 2 (PSCell)
Parameter Unit
T1 ~ T5 T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1 2
BW channel MHz 5: NRB,c = 25 5: NRB,c = 25
10: NRB,c = 50 10: NRB,c = 50
20: NRB,c = 100 20: NRB,c = 100
Special subframe 6 6
configurationNote1
Uplink-downlink configurationNote2 1 1
PCFICH/PDCCH/PHICH 5MHz: R.11 TDD 5MHz: R.11 TDD
parameters defined in A.3.1.2.1 10MHz: R.6 TDD 10MHz: R.6 TDD
20MHz: R.10 TDD 20MHz: R.10 TDD
OCNG Pattern defined in A.3.2.1 5MHz: OP.10 TDD
5MHz: OP.10 TDD
(FDD) 10MHz: OP.2 TDD
10MHz: OP.2 TDD
20MHz: OP.8 TDD
20MHz: OP.8 TDD
ρA, ρB 0 0
PCFICH_RB dB 4 4
PDCCH_RA dB 0 0
PDCCH_RB dB 0 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
0 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6,10 5MHz BW channel -5.1 -5.1 -9.1 -13.1 -9.1 -5.1
10MHz dB -5.1 -5.1 -9.1 -13.1 -9.1 -5.1
BW channel
20MHz -5.1 -5.1 -9.1 -13.1 -9.1 -5.1
BW channel
N oc dBm/15 -98
kHz
Propagation condition AWGN AWGN
Correlation Matrix and Antenna 1x2 1x2
Configuration
Receive time offset to cell1 Note 9 μs - 33
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5
respectively in figure A.7.3.43.1-1.
Note 9: Receive time difference between subframe boundaries of signals received from the two cells at the UE
antenna connector including time alignment error between the two cells.
Note 10: The SNR values are specifed for testing a UE which supports 2RX on the PSCell frequency. For testing of a
UE which only supports 4RX on the PSCell frequency, the SNR during T3 and T4 is modified as specified in
section A.3.8.1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1067 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.43.1-3: DRX-Configuration for E-UTRAN TDD-TDD Radio Link Monitoring Test for In-sync
in DRX in synchronous dual connectivity
Value Comment
Field
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in
drx-InactivityTimer psf1 psf1 section 6.3.2 in
drx-RetransmissionTimer psf1 psf1 3GPP TS 36.331
longDRX-CycleStartOffset sf640 sf40
shortDRX disable disable
Table A.7.3.43.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD-TDD Radio Link Monitoring
Test for In-sync in DRX in synchronous dual connectivity
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS
sr-ConfigIndex 0
36.331 and section10.1 in TS 36.213.
Figure A.7.3.43.1-1 SNR variation of cell 2 (PSCell) for in-sync testing in DRX
A.7.3.43.2 Test Requirements
The UE behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0) on PCell and PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1068 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.44 E-UTRAN TDD-FDD DC Radio Link Monitoring Test for Out-of-sync
in DRX in synchronous DC with PCell in FDD
A.7.3.44.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync for the purpose of monitoring downlink
radio link quality of the PSCell when DRX is used. This test will partly verify the radio link monitoring requirements in
clause 7.6.
The test parameters are given in Tables A.7.3.44.1-1, A.7.3.44.1-2, A.7.3.44.1-3, and A.7.3.44.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of three successive time periods with time duration of
T1, T2 and T3 respectively. Figure A.7.3.44.1-1 shows the variation of the downlink SNR in the PCell and PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2ms on cell 1 and 1ms on cell 2, respectively. In the test, DRX configuration is enabled and DRX
inactivity timer has already been expired, i.e. UE tries to decode PDCCH and to send periodic CQI during the period
when On-duration timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment is
maintained during the test.
Table A.7.3.44.1-1: General test parameters for E-UTRAN TDD-FDD DC out-of-sync tests in DRX in
synchronous dual connectivity with PCell in FDD
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is PCell on E-UTRA FDD RF channel number 1,
Cell 2 and cell 2 is PSCell on E-UTRA TDD RF channel
number 2
CP length Normal
E-UTRA RF Channel Number 1, 2 One E-UTRA FDD carrier frequency and one E-UTRA
TDD carrier frequency are used.
E-UTRA Channel Bandwidth MHz 5, 10, 20
(BWchannel)
Correlation Matrix and Antenna 2x2 Low Correlation Matrix and Antenna Configuration are
Configuration defined in TS 36.101 [5] Annex B.2.3.2
DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
Number of Control 2 Out of sync threshold Qout and the corresponding
OFDM symbols hypothetical PDCCH/PCFICH transmission parameters
Out of sync Aggregation level CCE 8 are as specified in clause 7.6.1 and Table 7.6.1-1
transmission respectively.
parameters ρA, ρB -3
(Note 1) Ratio of PDCCH dB 1
to RS EPRE
Ratio of PCFICH dB 1
to RS EPRE
DRX cycle on cell 1 ms 640 See Table A.7.3.38.1-3
DRX cycle on cell 2 ms 40 See Table A.7.3.38.1-3
Timing offset between cell 1 and μs 33 For synchronous dual connectivity
cell 2
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1; N313 = 1; N314 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 0 T313 is disabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
T1 s 4
T2 s 1.6
T3 s 1.8
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1069 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.44.1-2: Cell specific test parameters for E-UTRAN TDD-FDD DC out-of-sync radio link
monitoring in DRX in synchronous dual connectivity with PCell in FDD
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel Number 1 2
BW channel MHz 5, 10, 20 5, 10, 20
Correlation Matrix and
2x2 Low 2x2 Low
Antenna Configuration
Special subframe
- 6
configurationNote7
Uplink-downlink
- 1
configurationNote8
PCFICH/PDCCH/PHICH
5MHz: R.12 FDD 5MHz: R.12 TDD
parameters
10MHz: R.7 FDD 10MHz: R.7 TDD
None of the PDCCH are
20MHz: R.13 FDD 20MHz: R.13 TDD
intended for the UE under test
OCNG Pattern 5MHz: OP.16 FDD 5MHz: OP.10 TDD
10MHz: OP.2 FDD 10MHz: OP.2 TDD
20MHz: OP.12 FDD 20MHz: OP.8 TDD
ρA, ρB -3 -3
PCFICH_RB dB 1 1
PDCCH_RA dB 1 1
PDCCH_RB dB 1 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
-3 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
SNR Note 6 (5MHz bandwidth) dB -2.3 -2.3 -2.3 -1.6 -5.2 -11.9
SNR Note 6 (10MHz bandwidth) dB -2.3 -2.3 -2.3 -2.3 -5.9 -11.9
SNR Note 6 (20MHz bandwidth) dB -2.9 -2.9 -2.9 -3.0 -6.6 -12.6
N oc dBm/15 kHz -98 -98
Propagation condition ETU 70 Hz ETU 70 Hz
Time offset to cell1 Note 9 μs - 33
CQI reporting periodicity ms 2 1
Note 1: OCNG shall be used such that the resources in cell 1 and cell 2 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, and T3 are denoted as SNR1, SNR2 and SNR3 respectively in figure
A.7.3.38.1-1.
Note 7: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 8: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 9: Receive time difference between subframe boundaries of signals received from the two cells at the UE
antenna connector including time alignment error between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1070 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.44.1-3: DRX-Configuration for E-UTRAN TDD-FDD DC out-of-sync tests in synchronous
dual connectivity with PCell in FDD
Value
Field Comment
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in clause 6.3.2 in TS 36.331
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset Sf640 Sf40
shortDRX disable disable
Table A.7.3.44.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD-FDD DC out-of-sync
testing in synchronous dual connectivity with PCell in FDD
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS 36.331 and
sr-ConfigIndex 0
section 10.1 in TS 36.213.
SNR level Cell 1 SNR level
SNR 1
Qin
SNR 2
Qout
SNR 3
Cell 2 SNR level
A B C
D1 ms
T1 T2 T3
Figure A.7.3.44.1-1 SNR variation for out-of-sync testing in DRX
A.7.3.44.2 Test Requirements
The UE behaviour during time durations T1, T2, and T3 shall be as follows:
During time durations T1, T2 and T3, the UE shall transmit uplink signal at least in all subframes configured for CQI
transmission on Cell1.
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the uplink subframe on Cell2.
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 900 ms after the start of time
duration T3) on PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1071 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.45 E-UTRAN TDD-FDD DC Radio Link Monitoring Test for Out-of-sync
in DRX in synchronous DC with PCell in TDD
A.7.3.45.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync for the purpose of monitoring downlink
radio link quality of the PSCell when DRX is used. This test will partly verify the radio link monitoring requirements in
clause 7.6.
The test parameters are given in Tables A.7.3.45.1-1, A.7.3.45.1-2, A.7.3.45.1-3, and A.7.3.45.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of three successive time periods with time duration of
T1, T2 and T3 respectively. Figure A.7.3.45.1-1 shows the variation of the downlink SNR in the PCell and PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 1ms on cell 1 and 2ms on cell 2, respectively. In the test, DRX configuration is enabled and DRX
inactivity timer has already been expired, i.e. UE tries to decode PDCCH and to send periodic CQI during the period
when On-duration timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment is
maintained during the test.
Table A.7.3.45.1-1: General test parameters for E-UTRAN TDD-FDD DC out-of-sync tests in DRX in
synchronous dual connectivity with PCell in TDD
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is PCell on E-UTRA TDD RF channel number 1,
Cell 2 and cell 2 is PSCell on E-UTRA FDD RF channel
number 2
CP length Normal
E-UTRA RF Channel Number 1, 2 One E-UTRA TDD carrier frequencies and one E-UTRA
FDD carrier frequencies are used.
E-UTRA Channel Bandwidth MHz 5, 10, 20
(BWchannel)
Correlation Matrix and Antenna 2x2 Low Correlation Matrix and Antenna Configuration are
Configuration defined in TS 36.101 [5] Annex B.2.3.2
DCI format 1A As defined in clause 5.3.3.1.3 in TS 36.212
Number of Control 2 Out of sync threshold Qout and the corresponding
OFDM symbols hypothetical PDCCH/PCFICH transmission parameters
Out of sync Aggregation level CCE 8 are as specified in clause 7.6.1 and Table 7.6.1-1
transmission respectively.
parameters ρA, ρB -3
(Note 1) Ratio of PDCCH dB 1
to RS EPRE
Ratio of PCFICH dB 1
to RS EPRE
DRX cycle on cell 1 ms 640 See Table A.7.3.40.1-3
DRX cycle on cell 2 ms 40 See Table A.7.3.40.1-3
Timing offset between cell 1 and μs 33 For synchronous dual connectivity
cell 2
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1; N313 = 1; N314 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 0 T313 is disabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
T1 s 4
T2 s 1.6
T3 s 1.8
Note 1: PDCCH/PCFICH corresponding to the out of sync transmission parameters need not be included in the
Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1072 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.45.1-2: Cell specific test parameters for E-UTRAN TDD-FDD DC out-of-sync radio link
monitoring in DRX in synchronous dual connectivity with PCell in TDD
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel Number 1 2
BW channel MHz 5, 10, 20 5, 10, 20
Correlation Matrix and
2x2 Low 2x2 Low
Antenna Configuration
Special subframe
6 -
configurationNote1
Uplink-downlink
1 -
configurationNote2
PCFICH/PDCCH/PHICH
5MHz: R.12 TDD 5MHz: R.12 FDD
parameters
10MHz: R.7 TDD 10MHz: R.7 FDD
None of the PDCCH are
20MHz: R.13 TDD 20MHz: R.13 FDD
intended for the UE under test
OCNG Pattern 5MHz: OP.10 TDD 5MHz: OP.16 FDD
10MHz: OP.2 TDD 10MHz: OP.2 FDD
20MHz: OP.8 TDD 20MHz: OP.12 FDD
ρA, ρB -3 -3
PCFICH_RB dB 1 1
PDCCH_RA dB 1 1
PDCCH_RB dB 1 1
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
-3 -3
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
SNR Note 8 (5MHz bandwidth) dB -1.6 -1.6 -1.6 -2.3 -5.7 -12.2
SNR Note 8 (10MHz bandwidth) dB -2.3 -2.3 -2.3 -2.3 -6.2 -12.2
SNR Note 8 (20MHz bandwidth) dB -3.0 -3.0 -3.0 -2.9 -6.8 -12.8
N oc dBm/15 kHz -98 -98
Propagation condition ETU 70 Hz ETU 70 Hz
Time offset to cell1 Note 9 μs - 33
CQI reporting periodicity ms 1 2
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3 respectively in figure
A.7.3.40.1-1.
Note 9: Receive time difference between subframe boundaries of signals received from the two cells at the UE
antenna connector including time alignment error between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1073 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.45.1-3: DRX-Configuration for E-UTRAN TDD-FDD DC out-of-sync tests in synchronous
dual connectivity with PCell in TDD
Value
Field Comment
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in clause 6.3.2 in TS 36.331
drx-InactivityTimer psf1 psf1
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset Sf640 Sf40
shortDRX disable disable
Table A.7.3.45.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD-FDD CA out-of-sync
testing in synchronous dual connectivity with PCell in TDD
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS 36.331 and
sr-ConfigIndex 0
section 10.1 in TS 36.213.
SNR level Cell 1 SNR level
SNR 1
Qin
SNR 2
Qout
SNR 3
Cell 2 SNR level
A B C
D1 ms
T1 T2 T3
Figure A.7.3.45.1-1 SNR variation for out-of-sync testing in DRX
A.7.3.45.2 Test Requirements
The UE behaviour during time durations T1, T2, and T3 shall be as follows:
During time durations T1, T2 and T3, the UE shall transmit uplink signal at least in all subframes configured for CQI
transmission on Cell1.
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the uplink subframe on Cell2.
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 900 ms after the start of time
duration T3) on PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1074 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.46 E-UTRAN TDD-FDD Radio Link Monitoring Test for In-sync in DRX
for PSCell in synchronous DC with PCell in FDD
A.7.3.46.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PSCell when DRX is used in dual connectivity. This test will partly verify
the E-UTRAN FDD and TDD radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.46.1-1, A.7.3.46.1-2, A.7.3.46.1-3 and A.7.3.46.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.46.1-1 shows the variation of the downlink SNR in the PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 2 ms on PCell and 1ms on PSCell. In the test, DRX configuration for PCell and PSCell is enabled and
DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and to send periodic CQI during the
period when On-duration timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment
is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1075 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.46.1-1: General test parameters for E-UTRAN TDD-FDD Radio Link Monitoring Test for In-
sync in DRX for PSCell in synchronous DC with PCell in FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1, 2 One E-UTRA FDD carrier frequency and
One E-UTRA TDD carrier frequency are
used.
Active cell Cell 1, Cell 2 Cell 1 is PCell on E-UTRA FDD RF
channel number 1, and cell 2 is PSCell on
E-UTRA TDD RF channel number 2
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4 in TS
36.212
In sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 4 In sync threshold Qin and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS 0 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-2 respectively.
Ratio of PCFICH to RS 4
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in TS
36.212
Out of sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 8 Out of sync threshold Qout and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS dB 4 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-1 respectively.
Ratio of PCFICH to RS dB 4
EPRE
DRX cycle on Cell 1 ms 640 See Table A.7.3.41.1-3
DRX cycle on Cell 2 ms 40 See Table A.7.3.41.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1, N313 = 1, N314 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 2000 T313 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
Note 2: Even a UE capable of both synchronous and asynchronous DC operations is required to pass this test
case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1076 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.46.1-2: Cell specific test parameters for E-UTRAN TDD-FDD Radio Link Monitoring Test
for In-sync in DRX for PSCell in synchronous DC with PCell in FDD
Cell 1(PCell) Cell 2 (PSCell)
Parameter Unit
T1 ~ T5 T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1 2
BW channel MHz 5: NRB,c = 25 5: NRB,c = 25
10: NRB,c = 50 10: NRB,c = 50
20: NRB,c = 100 20: NRB,c = 100
Special subframe configuration Note1 - 6
Uplink-downlink configuration Note2 - 1
PCFICH/PDCCH/PHICH 5MHz: R.11 FDD 5MHz: R.11 TDD
parameters defined in A.3.1.2.1 and 10MHz: R.6 FDD 10MHz: R.6 TDD
A.3.1.2.2 20MHz: R.10 FDD 20MHz: R.10 TDD
OCNG Pattern defined in A.3.2.1 5MHz: OP.16 FDD 5MHz: OP.10 TDD
(FDD) and A.3.2.2 (TDD) 10MHz: OP.2 FDD 10MHz: OP.2 TDD
20MHz: OP.12 FDD 20MHz: OP.8 TDD
ρA, ρB 0 0
PCFICH_RB dB 4 4
PDCCH_RA dB 0 0
PDCCH_RB dB 0 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
0 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote3 dB
OCNG_RBNote3 dB
5MHz BW channel -2.3 -5.1 -9.1 -13.1 -9.1 -5.1
SNR Note 8 10MHz BW channel dB -4.7 -5.1 -9.1 -13.1 -9.1 -5.1
20MHz BW channel -4.7 -5.1 -9.1 -13.1 -9.1 -5.1
N oc dBm/15 -98
kHz
Propagation condition AWGN AWGN
Correlation Matrix and Antenna 1x2 1x2
Configuration
Receive time offset to cell1 Note 9 μs - 33
CQI reporting periodicity ms 2 1
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell 1 and cell 2 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR of Cell 2 in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.46.1-1.
Note 9: Receive time difference between subframe boundaries of signals received from the two cells at the UE
antenna connector including time alignment error between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1077 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.46.1-3: DRX-Configuration for E-UTRAN TDD-FDD Radio Link Monitoring Test for In-sync
in DRX for PSCell in synchronous DC with PCell in FDD
Value Comment
Field
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in
drx-InactivityTimer psf1 psf1 section 6.3.2 in
drx-RetransmissionTimer psf1 psf1 3GPP TS 36.331
longDRX-CycleStartOffset sf640 sf40
shortDRX disable disable
Table A.7.3.46.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD-FDD Radio Link Monitoring
Test for In-sync in DRX for PSCell in synchronous DC with PCell in FDD
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS
sr-ConfigIndex 0
36.331 and section 10.1 in TS 36.213.
Figure A.7.3.46.1-1 SNR variation of cell 2 (PSCell) for in-sync testing in DRX
A.7.3.46.2 Test Requirements
The UE behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0) on PCell and PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1078 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.47 E-UTRAN TDD-FDD Radio Link Monitoring Test for In-sync in DRX
for PSCell in synchronous DC with PCell in TDD
A.7.3.47.1 Test Purpose and Environment
The purpose of this test is to verify that the UE properly detects the out of sync and in sync for the purpose of
monitoring downlink radio link quality of the PSCell when DRX is used in dual connectivity. This test will partly verify
the E-UTRAN FDD and TDD radio link monitoring requirements in clause 7.6.
The test parameters are given in Tables A.7.3.47.1-1, A.7.3.47.1-2, A.7.3.47.1-3 and A.7.3.47.1-4. There are two cells,
cell 1 is PCell and cell 2 is PSCell, in the test. The test consists of five successive time periods, with time duration of
T1, T2, T3, T4 and T5 respectively. Figure A.7.3.47.1-1 shows the variation of the downlink SNR in the PSCell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1 and cell 2. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting
periodicity of 1ms on PCell and 2ms on PSCell. In the test, DRX configuration for PCell and PSCell is enabled and
DRX inactivity timer has already been expired, i.e. UE tries to decode PDCCH and to send periodic CQI during the
period when On-duration timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment
is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1079 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.47.1-1: General test parameters for E-UTRAN TDD-FDD Radio Link Monitoring Test for In-
sync in DRX for PSCell in synchronous DC with PCell in TDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1, 2 One E-UTRA TDD carrier frequency and
One E-UTRA FDD carrier frequency are
used.
Active cell Cell 1, Cell 2 Cell 1 is PCell on E-UTRA TDD RF
channel number 1, and cell 2 is PSCell on
E-UTRA FDD RF channel number 2
CP length Normal
DCI format 1C As defined in clause 5.3.3.1.4 in TS
36.212
In sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 4 In sync threshold Qin and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS 0 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-2 respectively.
Ratio of PCFICH to RS 4
EPRE
DCI format 1A As defined in clause 5.3.3.1.3 in TS
36.212
Out of sync Number of Control 2 For 10MHz and 20MHz channel BW
transmission OFDM symbols
parameters Number of Control 3 For 5MHz channel BW
(Note 1) OFDM symbols
Aggregation level CCE 8 Out of sync threshold Qout and the
corresponding hypothetical
ρA, ρB 0 PDCCH/PCFICH transmission parameters
Ratio of PDCCH to RS dB 4 are as specified in clause 7.6.1 and Table
EPRE 7.6.1-1 respectively.
Ratio of PCFICH to RS dB 4
EPRE
DRX cycle on Cell 1 ms 640 See Table A.7.3.43.1-3
DRX cycle on Cell 2 ms 40 See Table A.7.3.43.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1, N313 = 1, N314 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T313 timer ms 2000 T313 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in TS 36.213.
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: PDCCH/PCFICH corresponding to the in-sync and out of sync transmission parameters need not be
included in the Reference Measurement Channel.
Note 2: Even a UE capable of both synchronous and asynchronous DC operations is required to pass this test
case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1080 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.47.1-2: Cell specific test parameters for E-UTRAN TDD-FDD Radio Link Monitoring Test
for In-sync in DRX for PSCell in synchronous DC with PCell in TDD
Cell 1(PCell) Cell 2 (PSCell)
Parameter Unit
T1 ~ T5 T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1 2
BW channel MHz 5: NRB,c = 25 5: NRB,c = 25
10: NRB,c = 50 10: NRB,c = 50
20: NRB,c = 100 20: NRB,c = 100
Special subframe configurationNote1 6 -
Uplink-downlink configurationNote2 1 -
PCFICH/PDCCH/PHICH 5MHz: R.11 TDD 5MHz: R.11 FDD
parameters defined in A.3.1.2.1 and 10MHz: R.6 TDD 10MHz: R.6 FDD
A.3.1.2.2 20MHz: R.10 TDD 20MHz: R.10 FDD
OCNG Pattern defined in A.3.2.1 5MHz: OP.10 TDD 5MHz: OP.16 FDD
(FDD) and A.3.2.2 (TDD) 10MHz: OP.2 TDD 10MHz: OP.2 FDD
20MHz: OP.8 TDD 20MHz: OP.12 FDD
ρA, ρB 0 0
PCFICH_RB dB 4 4
PDCCH_RA dB 0 0
PDCCH_RB dB 0 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
0 0
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
5MHz BW channel -5.1 -2.3 -5.7 -12.2 -7.3 -2.3
SNR Note 6 10MHz BW channel dB -5.1 -4.7 -9.5 -13.5 -8.7 -4.7
20MHz BW channel -5.1 -4.7 -9.5 -13.5 -8.7 -4.7
N oc dBm/15 -98
kHz
Propagation condition AWGN AWGN
Correlation Matrix and Antenna 1x2 1x2
Configuration
Receive time offset to cell1 Note 9 μs - 33
CQI reporting periodicity ms 1 2
Note 1: For the special subframe configuration see table 4.2-1 in TS 36.211.
Note 2: For the uplink-downlink configuration see table 4.2-2 in TS 36.211.
Note 3: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1.
Note 6: The signal contains PDCCH for UEs other than the device under test as part of OCNG.
Note 7: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 8: The SNR of Cell 2 in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.47.1-1.
Note 9: Receive time difference between subframe boundaries of signals received from the two cells at the UE
antenna connector including time alignment error between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1081 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.47.1-3: DRX-Configuration for E-UTRAN TDD-FDD Radio Link Monitoring Test for In-sync
in DRX for PSCell in synchronous DC with PCell in TDD
Value Comment
Field
Cell 1 Cell 2
onDurationTimer psf2 psf2 As specified in
drx-InactivityTimer psf1 psf1 section 6.3.2 in
drx-RetransmissionTimer psf1 psf1 3GPP TS 36.331
longDRX-CycleStartOffset sf640 sf40
shortDRX disable disable
Table A.7.3.47.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD-TDD Radio Link Monitoring
Test for In-sync in DRX for PSCell in synchronous DC with PCell in TDD
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS
sr-ConfigIndex 0
36.331 and section10.1 in TS 36.213.
Figure A.7.3.47.1-1 SNR variation of cell 2 (PSCell) for in-sync testing in DRX
A.7.3.47.2 Test Requirements
The UE behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0) on PCell and PSCell.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1082 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.48 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync for
Cat-M1 UE in CEMode A
A.7.3.48.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD Cat-M1 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell in CEModeA. This test will partly verify the E-UTRAN
FDD radio link monitoring requirements for Cat-M1 UE defined in clause 7.19.
The test parameters are given in Tables A.7.3.48.1-1, A.7.3.48.1-2 and A.7.3.48.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.48.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode without repetition with a reporting periodicity of 2 ms.
In the test, the RRC parameter numberPRB-Pairs is set to 6 and the RRC parameter mPDCCH-NumRepetition is set to
8. UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
Table A.7.3.48.1-1: General test parameters for E-UTRAN FD-FDD out-of-sync testing for UE Cat-M1 in
CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA
RF channel number
1
CP length Normal
DCI format 6-1A As defined in
section 5.3.3.1.3 in
Out of sync TS 36.212
transmission Number of 2 Out of sync
parameters OFDM symbols threshold Qout and
(Note 1) for legacy the corresponding
control hypothetical
channels MPDCCH
M-PDCCH eCCE 24 transmission
aggregation parameters are as
level specified in section
M-PDCCH 8 7.19.2 and Table
repetition level 7.19.2-1
ρA, ρB -3 respectively.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table
7.2.2-1 in TS
36.213.
CQI reporting periodicity ms 2 Minimum CQI
reporting periodicity
T1 s 2
T2 s 0.8
T3 s 1.8
Note 1: MPDCCH corresponding to the out of sync transmission
parameters need not be included in the Reference Measurement
Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1083 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.48.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for out-of-sync radio
link monitoring tests for Cat-M1 in CEMode A
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
MPDCCH parameters R.17 FDD
as defined in A.3.1.3.1
OCNG Pattern defined OP.21 FDD
in A.3.2.1.21 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote 1 dB -3
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB 0.1 -6.8 -15.8
Propagation condition ETU 30Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure
A.7.3.48.1-1.
Figure A.7.3.48.1-1: SNR variation for out-of-sync testing
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1084 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.48.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (440 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.49 E-UTRAN FD-FDD Radio Link Monitoring Test for In-Sync for Cat-
M1 UE in CEMode A
A.7.3.49.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD Cat-M1 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell in CEModeA. This test will partly verify the E-UTRAN
FDD radio link monitoring requirements for Cat-M1 UE defined in clause 7.19.
The test parameters are given in Tables A.7.3.49.1-1, A.7.3.49.1-2 and A.7.3.49.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3,
T4 and T5 respectively. Figure A.7.3.49.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The
UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode without repetition with a reporting periodicity
of 2 ms.
In the test, the RRC parameter numberPRB-Pairs is set to 4 and the RRC parameter mPDCCH-NumRepetition is set to
4. UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1085 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.49.1-1: General test parameters for E-UTRAN FD-FDD in-sync testing for UE Cat-M1 in
CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
CP length Normal
DCI format 6-1A As defined in section 5.3.3.1.3 in
TS 36.212
In sync Number of 2 In sync threshold Qin and the
transmission OFDM symbols corresponding hypothetical
parameters for legacy MPDCCH transmission parameters
(Note 1) control channels are as specified in section 7.19.2
M-PDCCH eCCE 4 and Table 7.19.2-1 respectively.
aggregation
level
M-PDCCH 2
repetition level
ρA, ρB -3
DCI format 6-1A As defined in section 5.3.3.1.3 in
TS 36.212
Out of sync Number of 2 Out of sync threshold Qout and the
transmission OFDM symbols corresponding hypothetical
parameters for legacy MPDCCH transmission parameters
(Note 1) control channels are as specified in section 7.19.2
M-PDCCH eCCE 16 and Table 7.19.2-1 respectively.
aggregation
level
M-PDCCH 4
repetition level
ρA, ρB -3
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table 7.2.2-1 in TS
0 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting periodicity
T1 s 2
T2 s 0.8
T3 s 1.36
T4 s 0.4
T5 s 2
Note 1: MPDCCH corresponding to the out of sync transmission parameters need not be
included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1086 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.49.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for in-sync radio link
monitoring tests for Cat-M1 in CEMode A
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel 1
Number
BW channel MHz 10
MPDCCH parameters R.17 FDD
as defined in A.3.1.3.1
OCNG Pattern defined OP.21 FDD
in A.3.2.1.21 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote 1 dB -3
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB 5.4 -3.8 - -1.6 5.4
12.8
Propagation condition ETU 30Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are
fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE
prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device
under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the
cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as
SNR1, SNR2, SNR3, SNR4 and SNR5 respectively in figure
A.7.3.49.1-1.
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[680+40] ms
T1 T2 T3 T4 T5
Figure A.7.3.49.1-1: SNR variation for in-sync testing
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1087 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.49.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (720 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.50 E-UTRAN FD-FDD Radio Link Monitoring Test for Out-of-sync in
DRX for UE category M1 configured in CEMode A
A.7.3.50.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD category M1 UE configured in CEMode A properly detects the out
of sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly
verify the E-UTRAN FD-FDD radio link monitoring requirements in clause 7.19.
The test parameters are given in Tables A.7.3.50.1-1, A.7.3.50.1-2, A.7.3.50.1-3 and A.7.3.50.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1,
T2 and T3 respectively. Figure A.7.3.50.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms without repetition. In
the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode
MPDCCH and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall
be set to “infinity” so that UL timing alignment is maintained during the test.
In the test, the RRC parameter numberPRB-Pairs is set to 4 and the RRC parameter mPDCCH-NumRepetition is set 4.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1088 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.50.1-1: General test parameters for E-UTRAN FD-FDD out-of-sync tests in DRX for UE
category M1 configured in CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
DCI format 6-1A As defined in TS 36.212
Number of 2 Out of sync threshold
Out of sync OFDM Qout, Cat M1 and the
transmission symbols for corresponding
parameters legacy control hypothetical MPDCCH
(Note 1) channels transmission parameters
MPDCCH eCCE 16 are as specified in
aggregation clause 7.19.2 and Table
level 7.19.2-1 respectively.
MPDCCH 4
repetition level
Ratio of
MPDCCH to 0
RS EPRE
ρA, ρB -3
DRX cycle ms 1280 See Table A.7.3.50.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table
0 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 32
T2 s 12.8
T3 s 13
Note 1: MPDCCH corresponding to the out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1089 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.50.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for out-of-sync radio
link monitoring tests in DRX for UE category M1 configured in CEMode A
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
MPDCCH parameters R.17 FDD
defined in A.3.1.3
OCNG Pattern defined in OP.21 FDD
A.3.2.1 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote1 dB -3
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB 0.37 -6.98 -14.98
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains MPDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.50.1-
1.
Table A.7.3.50.1-3: DRX-Configuration for E-UTRAN FD-FDD out-of-sync tests for UE category M1
configured in CEMode A
Field Value Comment
onDurationTimer psf10 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
Table A.7.3.50.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FD-FDD out-of-sync testing for
UE category M1 configured in CEMode A
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1090 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.50.1-1: SNR variation for out-of-sync testing in DRX
A.7.3.50.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6500 ms after the start of time
duration T3.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.51 E-UTRAN FD-FDD Radio Link Monitoring Test for In-sync in DRX
for UE Category M1 configured in CEMode A
A.7.3.51.1 Test Purpose and Environment
The purpose of this test is to verify that the FD-FDD category M1 UE configured in CEMode A properly detects the out
of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test
will partly verify the E-UTRAN FD-FDD radio link monitoring requirements in clause 7.19.
The test parameters are given in Tables A.7.3.51.1-1, A.7.3.51.1-2, A.7.3.51.1-3 and A.7.3.51.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1,
T2, T3, T4 and T5 respectively. Figure A.7.3.51.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 2 ms
without repetition. In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE
tries to decode MPDCCH and to send periodic CQI during the period when On-duration timer is running. Time
alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the test.
In the test, the RRC parameter numberPRB-Pairs is set to 6 and the RRC parameter mPDCCH-NumRepetition is set 8.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1091 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.51.1-1: General test parameters for E-UTRAN FD-FDD in-sync test in DRX for UE category
M1 configured in CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
DCI format 6-1A As defined in TS 36.212
Number of OFDM 2 In sync threshold Qin, Cat M1
In sync symbols for legacy and the corresponding
transmission control channels hypothetical MPDCCH
parameters MPDCCH eCCE 8 transmission parameters are
(Note 1) aggregation level as specified in clause 7.19.2
MPDCCH repetition 4 and Table 7.19.2-1
level respectively.
ρA, ρB -3
Ratio of MPDCCH 0
to RS EPRE
DCI format 6-1A As defined in TS 36.212
Number of OFDM 2 Out of sync threshold Qout, Cat
Out of sync symbols for legacy M1 and the corresponding
transmission control channels hypothetical MPDCCH
parameters MPDCCH eCCE 24 transmission parameters are
(Note 1) aggregation level as specified in clause 7.19.2
MPDCCH repetition 8 and Table 7.19.2-1
level respectively.
ρA, ρB -3
Ratio of MPDCCH dB 0
to RS EPRE
DRX cycle ms 40 See Table A.7.3.51.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 2 Minimum CQI reporting
periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: MPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1092 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.51.1-2: Cell specific test parameters for E-UTRAN FD-FDD (cell # 1) for in-sync radio link
monitoring test in DRX for UE category M1 configured in CEMode A
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
MPDCCH parameters R.17 FDD
defined in A.3.1.3
OCNG Pattern defined in OP.21 FDD
A.3.2.1 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote1 dB -3
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 8 dB -4.58 -10 -18 -10.58 -4.58
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains MPDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.51.1-1.
Table A.7.3.51.1-3: DRX-Configuration for E-UTRAN FD-FDD out-of-sync tests for UE category M1
configured in CEMode A
Field Value Comment
onDurationTimer psf10 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
Table A.7.3.51.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FD-FDD out-of-sync testing for
UE category M1 configured in CEMode A
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1093 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.51.1-1: SNR variation for in-sync testing in DRX
A.7.3.51.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.52 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync for
Cat-M1 UE in CEMode A
A.7.3.52.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD Cat-M1 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell in CEModeA. This test will partly verify the E-UTRAN
FDD radio link monitoring requirements for Cat-M1 UE defined in clause 7.19.
The test parameters are given in Tables A.7.3.52.1-1, A.7.3.52.1-2 and A.7.3.52.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.52.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode without repetition with a reporting periodicity of 20 ms.
In the test, the RRC parameter numberPRB-Pairs is set to 6 and the RRC parameter mPDCCH-NumRepetition is set to
8. UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1094 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.52.1-1: General test parameters for E-UTRAN HD-FDD out-of-sync testing for UE Cat-M1
in CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA
RF channel number
1
CP length Normal
DCI format 6-1A As defined in section
5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 Out of sync
parameters OFDM symbols threshold Qout and
(Note 1) for legacy the corresponding
control hypothetical
channels MPDCCH
M-PDCCH eCCE 24 transmission
aggregation parameters are as
level specified in section
M-PDCCH 8 7.19.2 and Table
repetition level 7.19.2-1
ρA, ρB -3 respectively.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table
7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 20 Minimum CQI
reporting periodicity
T1 s 2
T2 s 0.8
T3 s 1.8
Note 1: MPDCCH transmission parameters corresponding to the in-sync
and out of sync transmission need not be included in the Reference
Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1095 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.52.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for out-of-sync radio
link monitoring tests for Cat-M1 in CEMode A
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
MPDCCH parameters R.7 HD-FDD
as defined in A.3.1.3.1
OCNG Pattern defined OP.21 FDD
in A.3.2.1.21 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB 0.1 -6.8 -15.8
Propagation condition ETU 30Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.x5.1-
1.
Figure A.7.3.52.1-1: SNR variation for out-of-sync testing
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1096 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.52.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (440 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.53 E-UTRAN HD-FDD Radio Link Monitoring Test for In-Sync for Cat-
M1 UE in CEMode A
A.7.3.53.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD Cat-M1 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell in CEModeA. This test will partly verify the E-UTRAN
FDD radio link monitoring requirements for Cat-M1 UE defined in clause 7.19.
The test parameters are given in Tables A.7.3.53.1-1, A.7.3.53.1-2 and A.7.3.53.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3,
T4 and T5 respectively. Figure A.7.3.53.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The
UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode without repetition with a reporting periodicity
of 20 ms.
In the test, the RRC parameter numberPRB-Pairs is set to 4 and the RRC parameter mPDCCH-NumRepetition is set to
4. UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1097 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.53.1-1: General test parameters for E-UTRAN HD-FDD in-sync testing for UE Cat-M1 in
CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
CP length Normal
DCI format 6-1A As defined in section 5.3.3.1.3 in TS
36.212
In sync Number of 2 In sync threshold Qin and the
transmission OFDM symbols corresponding hypothetical MPDCCH
parameters for legacy transmission parameters are as
(Note 1) control channels specified in section 7.19.2 and Table
M-PDCCH eCCE 4 7.19.2-1 respectively.
aggregation
level
M-PDCCH 2
repetition level
ρA, ρB -3
DCI format 6-1A As defined in section 5.3.3.1.3 in TS
36.212
Out of sync Number of 2 Out of sync threshold Qout and the
transmission OFDM symbols corresponding hypothetical MPDCCH
parameters for legacy transmission parameters are as
(Note 1) control channels specified in section 7.19.2 and Table
M-PDCCH eCCE 16 7.19.2-1 respectively.
aggregation
level
M-PDCCH 4
repetition level
ρA, ρB -3
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table 7.2.2-1 in TS
0 36.213.
CQI reporting periodicity ms 20 Minimum CQI reporting periodicity
T1 s 2
T2 s 0.8
T3 s 1.36
T4 s 0.4
T5 s 2
Note 1: MPDCCH corresponding to the out of sync transmission parameters need not be
included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1098 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.53.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for in-sync radio link
monitoring tests for Cat-M1 in CEMode A
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel 1
Number
BW channel MHz 10
MPDCCH parameters R.7 HD-FDD
as defined in A.3.1.3.1
OCNG Pattern defined OP.21 FDD
in A.3.2.1.21 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3
SSS_RA dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB 5.4 -3.8 - -1.6 5.4
12.8
Propagation condition ETU 30Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are
fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE
prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains PDCCH for UEs other than the device
under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the
cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as
SNR1, SNR2, SNR3, SNR4 and SNR5 respectively in figure
A.7.3.53.1-1.
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[680+40+20] ms
T1 T2 T3 T4 T5
Figure
A.7.3.53.1-1: SNR variation for in-sync testing
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1099 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.3.53.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (740 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.54 E-UTRAN HD-FDD Radio Link Monitoring Test for Out-of-sync in
DRX for UE category M1 configured in CEMode A
A.7.3.54.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category M1 UE configured in CEMode A properly detects the
out of sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will
partly verify the E-UTRAN HD-FDD radio link monitoring requirements in clause 7.19.
The test parameters are given in Tables A.7.3.54.1-1, A.7.3.54.1-2, A.7.3.54.1-3 and A.7.3.54.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1,
T2 and T3 respectively. Figure A.7.3.54.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 20 ms without repetition. In
the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode
MPDCCH and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall
be set to “infinity” so that UL timing alignment is maintained during the test.
In the test, the RRC parameter numberPRB-Pairs is set to 4 and the RRC parameter mPDCCH-NumRepetition is set 4.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1100 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.54.1-1: General test parameters for E-UTRAN HD-FDD out-of-sync tests in DRX for UE
category M1 configured in CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
DCI format 6-1A As defined in TS 36.212
Number of 2 Out of sync threshold
Out of sync OFDM Qout, Cat M1 and the
transmission symbols for corresponding
parameters legacy control hypothetical MPDCCH
(Note 1) channels transmission parameters
MPDCCH eCCE 16 are as specified in
aggregation clause 7.19.2 and Table
level 7.19.2-1 respectively.
MPDCCH 4
repetition level
ρA, ρB -3
Ratio of dB 0
PDCCH to RS
EPRE
DRX cycle ms 1280 See Table A.7.3.54.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table
0 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 20
T1 s 32
T2 s 12.8
T3 s 13
Note 1: MPDCCH corresponding to the out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1101 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.54.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for out-of-sync radio
link monitoring tests in DRX for UE category M1 configured in CEMode A
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
MPDCCH parameters R.7 HD-FDD
defined in A.3.1.3
OCNG Pattern defined in OP.21 FDD
A.3.2.1 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote1 dB -3
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB 0.37 -6.98 -14.98
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains MPDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.54.1-
1.
Table A.7.3.54.1-3: DRX-Configuration for E-UTRAN HD-FDD out-of-sync tests for UE category M1
configured in CEMode A
Field Value Comment
onDurationTimer psf20 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
Table A.7.3.54.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category M1 configured in CEMode A
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1102 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.54.1-1: SNR variation for out-of-sync testing in DRX
A.7.3.54.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6520 ms after the start of time
duration T3.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.55 E-UTRAN HD-FDD Radio Link Monitoring Test for In-sync in DRX
for UE Category M1 configured in CEMode A
A.7.3.55.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category M1 UE configured in CEMode A properly detects the
out of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is used. This
test will partly verify the E-UTRAN HD-FDD radio link monitoring requirements in clause 7.19.
The test parameters are given in Tables A.7.3.55.1-1, A.7.3.55.1-2, A.7.3.55.1-3 and A.7.3.55.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1,
T2, T3, T4 and T5 respectively. Figure A.7.3.55.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 20
ms without repetition. In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e.
UE tries to decode MPDCCH and to send periodic CQI during the period when On-duration timer is running. Time
alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the test.
In the test, the RRC parameter numberPRB-Pairs is set to 6 and the RRC parameter mPDCCH-NumRepetition is set 8.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1103 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.55.1-1: General test parameters for E-UTRAN HD-FDD in-sync test in DRX for UE category
M1 configured in CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
DCI format 6-1A As defined in TS 36.212
Number of OFDM 2 In sync threshold Qin, Cat M1
In sync symbols for legacy and the corresponding
transmission control channels hypothetical MPDCCH
parameters MPDCCH eCCE 8 transmission parameters are
(Note 1) aggregation level as specified in clause 7.19.2
MPDCCH repetition 4 and Table 7.19.2-1
level respectively.
ρA, ρB -3
Ratio of MPDCCH 0
to RS EPRE
DCI format 6-1A As defined in TS 36.212
Number of OFDM 2 Out of sync threshold Qout, Cat
Out of sync symbols for legacy M1 and the corresponding
transmission control channels hypothetical MPDCCH
parameters MPDCCH eCCE 24 transmission parameters are
(Note 1) aggregation level as specified in clause 7.19.2
MPDCCH repetition 8 and Table 7.19.2-1
level respectively.
ρA, ρB -3
Ratio of MPDCCH dB 0
to RS EPRE
DRX cycle ms 40 See Table A.7.3.55.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 20
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: MPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1104 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.55.1-2: Cell specific test parameters for E-UTRAN HD-FDD (cell # 1) for in-sync radio link
monitoring test in DRX for UE category M1 configured in CEMode A
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
MPDCCH parameters R.7 HD-FDD
defined in A.3.1.3
OCNG Pattern defined in OP.21 FDD
A.3.2.1 (FDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote1 dB -3
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 8 dB -4.58 -10 -18 -10.58 -4.58
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains MPDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.55.1-1.
Table A.7.3.55.1-3: DRX-Configuration for E-UTRAN HD-FDD out-of-sync tests for UE category M1
configured in CEMode A
Field Value Comment
onDurationTimer psf20 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
Table A.7.3.55.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category M1 configured in CEMode A
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1105 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.55.1-1: SNR variation for in-sync testing in DRX
A.7.3.55.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1140 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.56 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync for Cat-
M1 UE in CEMode A
A.7.3.56.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD Cat-M1 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell in CEModeA. This test will partly verify the E-UTRAN
TDD radio link monitoring requirements for Cat-M1 UE defined in clause 7.19.
The test parameters are given in Tables A.7.3.56.1-1, A.7.3.56.1-2 and A.7.3.56.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and
T3 respectively. Figure A.7.3.56.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync
and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall
be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms.
In the test, the RRC parameter numberPRB-Pairs is set to 6 and the RRC parameter mPDCCH-NumRepetition is set to
8. UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1106 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.56.1-1: General test parameters for E-UTRAN TDD out-of-sync testing for UE Cat-M1 in
CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA
RF channel number
1
CP length Normal
DCI format 6-1A As defined in section
5.3.3.1.3 in TS
Out of sync 36.212
transmission Number of 2 Out of sync
parameters OFDM symbols threshold Qout and
(Note 1) for legacy the corresponding
control hypothetical
channels MPDCCH
M-PDCCH eCCE 24 transmission
aggregation parameters are as
level specified in section
M-PDCCH 8 7.19.2 and Table
repetition level 7.19.2-1
ρA, ρB -3 respectively.
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table
7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI
reporting periodicity
T1 s 2
T2 s 0.8
T3 s 1.8
Note 1: MPDCCH corresponding to the out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1107 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.56.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for out-of-sync radio link
monitoring tests for Cat-M1 in CEMode A
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
Special subframe 6
configuration Note 1
Uplink-downlink 1
configuration Note 1
MPDCCH parameters R.15 TDD Note 8
as defined in A.3.1.3.1
OCNG Pattern defined OP.11 TDD
in A.3.2.2.11 (TDD)
ρA, ρB -3
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote 1 dB -3
OCNG_RBNote 1 dB
N oc dBm/15 -98
kHz
SNR Note 7 dB -0.3 -7.1 -16.1
Propagation condition ETU 30Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: For special subframe and uplink-downlink configurations
see Tables 4.2-1 and 4.2-2 in TS 36.211.
Note 2: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 3: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 4: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 5: The signal contains PDCCH for UEs other than the
device under test as part of OCNG.
Note 6: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 7: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure
A.7.3.56.1-1.
Note 8: Aggregation level and repetition levels specified in
A.7.3.56.1-1 are used for this test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1108 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.56.1-1: SNR variation for out-of-sync testing
A.7.3.56.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least in all subframes
configured for CQI transmission according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (440 ms after the start of time duration T3).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.57 E-UTRAN TDD Radio Link Monitoring Test for In-Sync for Cat-M1
UE in CEMode A
A.7.3.57.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD Cat-M1 UE properly detects the out of sync and in sync for the
purpose of monitoring downlink radio link quality of the PCell in CEModeA. This test will partly verify the E-UTRAN
TDD radio link monitoring requirements for Cat-M1 UE defined in clause 7.19.
The test parameters are given in Tables A.7.3.57.1-1, A.7.3.57.1-2 and A.7.3.57.1-3 below. There is one cell (cell 1),
which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3,
T4 and T5 respectively. Figure A.7.3.57.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The
UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode without repetition with a reporting periodicity
of 1 ms.
In the test, the RRC parameter numberPRB-Pairs is set to 4 and the RRC parameter mPDCCH-NumRepetition is set to
4. UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1109 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.57.1-1: General test parameters for E-UTRAN TDD in-sync testing for UE Cat-M1 in
CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF channel
number 1
CP length Normal
DCI format 6-1A As defined in section 5.3.3.1.3 in
TS 36.212
In sync Number of 2 In sync threshold Qin and the
transmission OFDM symbols corresponding hypothetical
parameters for legacy MPDCCH transmission parameters
(Note 1) control channels are as specified in section 7.19.2
M-PDCCH eCCE 4 and Table 7.19.2-1 respectively.
aggregation
level
M-PDCCH 2
repetition level
ρA, ρB -3
DCI format 6-1A As defined in section 5.3.3.1.3 in
TS 36.212
Out of sync Number of 2 Out of sync threshold Qout and the
transmission OFDM symbols corresponding hypothetical
parameters for legacy MPDCCH transmission parameters
(Note 1) control channels are as specified in section 7.19.2
M-PDCCH eCCE 16 and Table 7.19.2-1 respectively.
aggregation
level
M-PDCCH 4
repetition level
ρA, ρB -3
DRX OFF
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table 7.2.2-1 in TS
0 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting periodicity
T1 s 2
T2 s 0.8
T3 s 1.36
T4 s 0.4
T5 s 2
Note 1: MPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1110 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.57.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for in-sync radio link
monitoring tests for Cat-M1 in CEMode A
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel 1
Number
BW channel MHz 10
Special subframe 6
configuration Note 1
Uplink-downlink 1
configuration Note 1
MPDCCH parameters R.15 TDD
as defined in A.3.1.3.1
OCNG Pattern defined OP.11 TDD
in A.3.2.2.11 (TDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote 2 dB -3
OCNG_RBNote 2 dB
N oc dBm/15 -98
kHz
SNR dB 5.1 -3.8 - -1.9 5.1
12.8
Propagation condition ETU 30Hz
Correlation Matrix and 2x1 Low
Antenna Configuration
Note 1: For special subframe and uplink-downlink configurations see
Tables 4.2-1 and 4.2-2 in TS 36.211.
Note 2: OCNG shall be used such that the resources in cell # 1 are
fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 3: The uplink resources for CQI reporting are assigned to the UE
prior to the start of time period T1.
Note 4: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 5: The signal contains PDCCH for UEs other than the device
under test as part of OCNG.
Note 6: SNR levels correspond to the signal to noise ratio over the
cell-specific reference signal REs.
Note 7: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as
SNR1, SNR2, SNR3, SNR4 and SNR5 respectively in figure
A.7.3.57.1-1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1111 ETSI TS 136 133 V14.3.0 (2017-04)
SNR level
SNR1
SNR5
Qin
SNR2 SNR4
Qout
SNR3
A B C D E F
[680+40] ms
T1 T2 T3 T4 T5
Figure
A.7.3.57.1-1: SNR variation for in-sync testing
A.7.3.57.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (720 ms after the start of time duration T5) the UE shall transmit
uplink signal at least in all subframes configured for CQI transmission according to the configured CQI reporting mode
(PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.58 E-UTRAN TDD Radio Link Monitoring Test for Out-of-sync in DRX
for UE category M1 configured in CEMode A
A.7.3.58.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD category M1 UE configured in CEMode A properly detects the out of
sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test will partly
verify the E-UTRAN TDD radio link monitoring requirements in clause 7.19.
The test parameters are given in Tables A.7.3.58.1-1, A.7.3.58.1-2, A.7.3.58.1-3 and A.7.3.58.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of three successive time periods, with time duration of T1,
T2 and T3 respectively. Figure A.7.3.58.1-1 shows the variation of the downlink SNR in the active cell to emulate out-
of-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to cell 1. The UE shall be
configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms without repetition. In
the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode
MPDCCH and to send periodic CQI during the period when On-duration timer is running. Time alignment timers shall
be set to “infinity” so that UL timing alignment is maintained during the test.
In the test, the RRC parameter numberPRB-Pairs is set to 4 and the RRC parameter mPDCCH-NumRepetition is set 4.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1112 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.58.1-1: General test parameters for E-UTRAN TDD out-of-sync tests in DRX for UE
category M1 configured in CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
DCI format 6-1A As defined in TS 36.212
Number of 2 Out of sync threshold
Out of sync OFDM Qout, Cat M1 and the
transmission symbols for corresponding
parameters legacy control hypothetical MPDCCH
(Note 1) channels transmission parameters
MPDCCH eCCE 16 are as specified in
aggregation clause 7.19.2 and Table
level 7.19.2-1 respectively.
MPDCCH 4
repetition level
ρA, ρB -3
Ratio of dB 0
MPDCCH to
RS EPRE
DRX cycle ms 1280 See Table A.7.3.58.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 0 T310 is disabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1- As defined in table
0 7.2.2-1 in TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
T1 s 32
T2 s 12.8
T3 s 13
Note 1: MPDCCH corresponding to the out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1113 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.58.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for out-of-sync radio link
monitoring tests in DRX for UE category M1 configured in CEMode A
Parameter Unit Test 1
T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
Special subframe 6
configuration
Uplink-downlink 1
configuration
MPDCCH parameters R.15 TDD
defined in A.3.1.3
OCNG Pattern defined in OP.11 TDD
A.3.2.2 (TDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote1 dB -3
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 6 dB 0.55 -6.88 -14.88
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1
are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to
the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are
configured prior to the start of time period T1.
Note 4: The signal contains MPDCCH for UEs other than the
device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as
SNR1, SNR2 and SNR3 respectively in figure A.7.3.58.1-
1.
Table A.7.3.58.1-3: DRX-Configuration for E-UTRAN TDD out-of-sync tests for UE category M1
configured in CEMode A
Field Value Comment
onDurationTimer psf10 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1114 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.58.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD out-of-sync testing for UE
category M1 configured in CEMode A
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
SNR level
SNR1
Qin
SNR2
Qout
SNR3
A B C
D1 ms
T1 T2 T3
Figure A.7.3.58.1-1: SNR variation for out-of-sync testing in DRX
A.7.3.58.2 Test Requirements
The UE behaviour in each test during time durations T1, T2 and T3 shall be as follows:
During the period from time point A to time point B the UE shall transmit uplink signal at least once every DRX cycle,
in the On-duration part of the cycle in the subframe according to the configured CQI reporting mode (PUCCH 1-0).
The UE shall stop transmitting uplink signal no later than time point C (duration D1 = 6500 ms after the start of time
duration T3.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.59 E-UTRAN TDD Radio Link Monitoring Test for In-sync in DRX for
UE Category M1 configured in CEMode A
A.7.3.59.1 Test Purpose and Environment
The purpose of this test is to verify that the TDD category M1 UE configured in CEMode A properly detects the out of
sync and in sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is used. This test
will partly verify the E-UTRAN TDD radio link monitoring requirements in clause 7.19.
The test parameters are given in Tables A.7.3.59.1-1, A.7.3.59.1-2, A.7.3.59.1-3 and A.7.3.59.1-4. There is one cell
(cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1,
T2, T3, T4 and T5 respectively. Figure A.7.3.59.1-1 shows the variation of the downlink SNR in the active cell to
emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the UE shall be fully synchronized to
cell 1. The UE shall be configured for periodic CQI reporting in PUCCH 1-0 mode with a reporting periodicity of 1 ms
without repetition. In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE
tries to decode MPDCCH and to send periodic CQI during the period when On-duration timer is running. Time
alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the test.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1115 ETSI TS 136 133 V14.3.0 (2017-04)
In the test, the RRC parameter numberPRB-Pairs is set to 6 and the RRC parameter mPDCCH-NumRepetition is set 8.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
Table A.7.3.59.1-1: General test parameters for E-UTRAN TDD in-sync test in DRX for UE category M1
configured in CEMode A
Parameter Unit Value Comment
Active cell Cell 1 Cell 1 is on E-UTRA RF
channel number 1
CP length Normal
DCI format 6-1A As defined in TS 36.212
Number of OFDM 2 In sync threshold Qin, Cat M1
In sync symbols for legacy and the corresponding
transmission control channels hypothetical MPDCCH
parameters MPDCCH eCCE 8 transmission parameters are
(Note 1) aggregation level as specified in clause 7.19.2
MPDCCH repetition 4 and Table 7.19.2-1
level respectively.
ρA, ρB -3
Ratio of MPDCCH 0
to RS EPRE
DCI format 6-1A As defined in TS 36.212
Number of OFDM 2 Out of sync threshold Qout, Cat
Out of sync symbols for legacy M1 and the corresponding
transmission control channels hypothetical MPDCCH
parameters MPDCCH eCCE 24 transmission parameters are
(Note 1) aggregation level as specified in clause 7.19.2
MPDCCH repetition 8 and Table 7.19.2-1
level respectively.
ρA, ρB -3
Ratio of MPDCCH dB 0
to RS EPRE
DRX cycle ms 40 See Table A.7.3.59.1-3
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
Periodic CQI reporting mode PUCCH 1-0 As defined in table 7.2.2-1 in
TS 36.213.
CQI reporting periodicity ms 1 Minimum CQI reporting
periodicity
T1 s 4
T2 s 1.6
T3 s 1.46
T4 s 0.4
T5 s 4
Note 1: MPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1116 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.59.1-2: Cell specific test parameters for E-UTRAN TDD (cell # 1) for in-sync radio link
monitoring test in DRX for UE category M1 configured in CEMode A
Parameter Unit Test 1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
BW channel MHz 10
Special subframe 6
configuration
Uplink-downlink configuration 1
MPDCCH parameters R.15 TDD
defined in A.3.1.3
OCNG Pattern defined in OP.11 TDD
A.3.2.2 (TDD)
ρA, ρB -3
MPDCCH_RA dB 0
MPDCCH_RB dB 0
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
OCNG_RANote1 dB -3
OCNG_RBNote1 dB
N oc dBm/15 -98
kHz
SNR Note 8 dB -4.5 -9.93 -17.93 -11.5 -4.5
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in cell # 1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains MPDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and
SNR5 respectively in figure A.7.3.59.1-1.
Table A.7.3.59.1-3: DRX-Configuration for E-UTRAN TDD out-of-sync tests for UE category M1
configured in CEMode A
Field Value Comment
onDurationTimer psf10 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf40
shortDRX disable
Table A.7.3.59.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD out-of-sync testing for UE
category M1 configured in CEMode A
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1117 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.59.1-1: SNR variation for in-sync testing in DRX
A.7.3.59.2 Test Requirements
The UE behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows:
During the period from time point A to time point F (1120 ms after the start of time duration T5) the UE shall transmit
uplink signal at least once every DRX cycle, in the On-duration part of the cycle in the subframe according to the
configured CQI reporting mode (PUCCH 1-0).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.60 HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE
category NB1 In-band mode in normal coverage
A.7.3.60.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category NB1 UE properly detects the out of sync for the purpose
of monitoring downlink radio link quality of the NB-IoT Cell. This test will partly verify the NB-IoT HD-FDD radio
link monitoring requirements in clause 7.23.
The test parameters are given in Tables A.7.3.60.1-1, A.7.3.60.1-2, A.7.3.60.1-2a, A.7.3.60.1-3 and A.7.3.60.1-4. nCell
1 is the active NB-IoT cell in the test. The test consists of four successive time periods with time duration of T1, T2, T3
and T4 respectively, excluding the transition time duration dT, where the SNR increases or decreases gradually in small
steps. Figure A.7.3.60.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync state with
the following testing procedure:
- Prior to the start of the time duration T1, the UE shall be fully synchronized to nCell1
- Starting at point A, the SNR is decreased in small steps from SNR1 to SNR2 within dT
- At the start of the time duration T2, the UE is provided with a UL grant with NPDCCH
Note: The UE is expected to decode the NPDCCH and complete the UL transmission during T2 according to
the UL grant.
- Starting at point B, the SNR is decreased in small steps from SNR2 to SNR3 within dT
- During T3, the SNR is kept as SNR3
Note: The UE is expected to detect OOS and declare RLF during T3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1118 ETSI TS 136 133 V14.3.0 (2017-04)
- Starting at point C, the SNR is increased in small steps from SNR3 to SNR1 with dT
- At the start of the time period T4, the UE will be provided with another UL grant with NPDCCH
Note: The UE is not expected to decode the UL grant and conduct any UL transmission during T4, since the
UE is expected to declare RLF during T3.
In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode the
NPDCCH and complete the UL transmission when On-duration timer is running. Time alignment timers shall be set to
“infinity” so that UL timing alignment is maintained during the test.
Table A.7.3.60.1-1: General test parameters for HD-FDD Radio Link Monitoring Test for Out-of-sync in
DRX for UE category NB1 In-band mode in normal coverage
Parameter Unit Value Comment
Active cell nCell 1
Neighbour cell eCell 1
CP length Normal
Deployment Mode In-band
NPDCCH transmission 8 Other NPDCCH
parameters Rmax parameters are
defined in “ out-of-
sync” column in
Table 7.23.2-1
DRX cycle ms 256 See Table
A.7.3.60.1-3
Layer 3 filtering Note 2,3 Enabled Counters:
N310 = 1
N311 = 1
T310 timer Note 2,3 ms 0 T310 is disabled
T311 timer Note 2,3 ms 100 T311 is enabled
T1 s 5.12
T2 s 10.24
T3 s 5.12
T4 s 5.12
dT ms 1000
Note 1: NPDCCH corresponding to the out of sync transmission parameters
need not be included in the Reference Measurement Channel.
Note 2: N310, N311, T310 and T311 are defined in TS 36.331.
Note 3: The timers and layer 3 filtering related parameters are configured prior
to the start of time period T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1119 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.60.1-2: nCell specific test parameters for HD-FDD Radio Link Monitoring Test for Out-of-
sync in DRX for UE category NB1 In-band mode in normal coverage
Parameter Unit Test 1
T1 T2 T3 T4
NB-IoT RF Channel 1
Number
LTE Carrier bandwidth MHz 10
BW channel KHz 180
OCNG Pattern as defined NOP.1 FDD
in A.3.2.3.1 Note 1
NPDSCH parameters as R.15 HD-FDD
defined in A.3.1.5.1 Note 2
NPDCCH parameters as R.27 HD-FDD
defined in A.3.1.6.1 Note 2
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB
NSSS_RA dB
NPDCCH_RA dB
-3
NPDCCH_RB dB
NPDSCH_RA dB
NPDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 3 dBm/15 -98
kHz
SNR Note 4, 5 dB -3.1 -9.1 -14.1 -3.1
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the cell is fully allocated
and a constant total transmitted power spectral density is
achieved for all OFDM symbols. The OCNG pattern is
chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The NPDSCH and NPDCCH reference measurement
channels are used in the test only when a downlink
transmission dedicated to the UE under test is required.
Note 3: Es/Iot, NRSRP and Io level has been derived from other
parameters for information purpose. They are not settable
parameters themselves.
Note 4: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 5: The SNRs in time periods T1, T2, T3 and T4 are denoted
as SNR1, SNR2, SNR3 and SNR1 respectively in figure
A.7.3.60.1-1.
Note 6: During dT between the defined Time Intervals, the Test
system shall gradually increase or decrease the SNR in
steps of ≤1 dB every 0.1 seconds until the target SNR is
achieved.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1120 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.60.1-2a: eCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test
with DRX for UE category NB1 in enhanced coverage
Parameter Unit eCell 1
T1-T4
BW channel MHz 10
NOCNG Pattern - NOP.1 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note2 dBm/15 kHz -98
dB -12
Ês N oc
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N oc .
shall be modelled as AWGN of appropriate power
Table A.7.3.60.1-3: DRX-Configuration for HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX
for UE category NB1 In-band mode in normal coverage
Field Value Comment
onDurationTimer pp1 As specified in clause 6.7.3 in TS
drx-InactivityTimer pp0 36.331
drx-RetransmissionTimer pp0
drx-StartOffset 0
Table A.7.3.60.1-4: TimeAlignmentTimer -Configuration for NB-IoT HD-FDD out-of-sync testing for UE
category NB1 configured under normal coverage
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1121 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.60.1-1: SNR variation for out-of-sync testing in DRX for NB-IoT HD-FDD out-of-sync
testing for UE category NB1 configured under normal coverage
A.7.3.60.2 Test Requirements
The UE behaviors in each test shall be as follows:
- The UE shall complete the NPUSCH transmission during T2 according to the received UL grant;
- The UE shall not conduct any NPUSCH transmission during T4
A correct event is defined as UE behaves correctly in all above steps. The correct events observed during repeated tests
shall be at least 90%.
A.7.3.61 HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for UE
category NB1 In-band mode in enhanced coverage
A.7.3.61.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category NB1 UE properly detects the out of sync for the purpose
of monitoring downlink radio link quality of the NB-IoT Cell. This test will partly verify the NB-IoT HD-FDD radio
link monitoring requirements in clause 7.23.
The test parameters are given in Tables A.7.3.61.1-1, A.7.3.61.1-2, A.7.3.61.1-2a, A.7.3.61.1-3 and A.7.3.61.1-4:. nCell
1 is the active NB-IoT cell in the test. The test consists of four successive time periods with time duration of T1, T2, T3
and T4 respectively, excluding the transition time duration dT, where the SNR increases or decreases gradually in small
steps. Figure A.7.3.61.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync state with
the following testing procedure:
- Prior to the start of the time duration T1, the UE shall be fully synchronized to nCell1
- Starting at point A, the SNR is decreased in small steps from SNR1 to SNR2 within dT
- At the start of the time duration T2, the UE is provided with a UL grant with NPDCCH
Note: The UE is expected to decode the NPDCCH and complete the UL transmission during T2 according to
the UL grant.
- Starting at point B, the SNR is decreased in small steps from SNR2 to SNR3 within dT
- During T3, the SNR is kept as SNR3
Note: The UE is expected to detect OOS and declare RLF during T3.
- Starting at point C, the SNR is increased in small steps from SNR3 to SNR1 with dT
- At the start of the time period T4, the UE will be provided with another UL grant with NPDCCH
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1122 ETSI TS 136 133 V14.3.0 (2017-04)
Note: The UE is not expected to decode the UL grant and conduct any UL transmission during T4, since the
UE is expected to declare RLF during T3.
In the test, DRX configuration is enabled and DRX inactivity timer has already been expired, i.e. UE tries to decode the
NPDCCH and complete the UL transmission when On-duration timer is running. Time alignment timers shall be set to
“infinity” so that UL timing alignment is maintained during the test.
Table A.7.3.61.1-1: General test parameters for HD-FDD Radio Link Monitoring Test for Out-of-sync in
DRX for UE category NB1 In-band mode in enhanced coverage
Parameter Unit Value Comment
Active cell nCell 1
Neighbour cell eCell 1
CP length Normal
Deployment Mode In-band
NPDCCH transmission 16 Other NPDCCH
parameters Rmax parameters are
defined in “ out-of-
sync” column in
Table 7.23.2-1
DRX cycle ms 256 See Table
A.7.3.61.1-3
Layer 3 filtering Note 2,3 Enabled Counters:
N310 = 1
N311 = 1
T310 timer Note 2,3 ms 0 T310 is disabled
T311 timer Note 2,3 ms 100 T311 is enabled
T1 s 5.12
T2 s 10.24
T3 s 5.12
T4 s 5.12
dT ms 1000
Note 1: NPDCCH corresponding to the out of sync transmission parameters
need not be included in the Reference Measurement Channel.
Note 2: N310, N311, T310 and T311 are defined in TS 36.331.
Note 3: The timers and layer 3 filtering related parameters are configured prior
to the start of time period T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1123 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.61.1-2: nCell specific test parameters for HD-FDD Radio Link Monitoring Test for Out-of-
sync in DRX for UE category NB1 In-band mode in enhanced coverage
Parameter Unit Test 1
T1 T2 T3 T4
NB-IoT RF Channel 1
Number
LTE Carrier bandwidth MHz 10
BW channel KHz 180
OCNG Pattern as defined NOP.1 FDD
in A.3.2.3.1 Note 1
NPDSCH parameters as R.15 HD-FDD
defined in A.3.1.5.1 Note 2
NPDCCH parameters as R.27 HD-FDD
defined in A.3.1.6.1 Note 2
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB
NSSS_RA dB
NPDCCH_RA dB
-3
NPDCCH_RB dB
NPDSCH_RA dB
NPDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 3 dBm/15 -98
kHz
SNR Note 4, 5 dB -6.3 -11.4 -17.4 -6.3
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the cell is fully allocated
and a constant total transmitted power spectral density is
achieved for all OFDM symbols. The OCNG pattern is
chosen during the test according to the presence of a DL
reference measurement channel.
Note 2: The NPDSCH and NPDCCH reference measurement
channels are used in the test only when a downlink
transmission dedicated to the UE under test is required.
Note 3: Es/Iot, NRSRP and Io level has been derived from other
parameters for information purpose. They are not settable
parameters themselves.
Note 4: SNR levels correspond to the signal to noise ratio over
the cell-specific reference signal REs.
Note 5: The SNRs in time periods T1, T2, T3 and T4 are denoted
as SNR1, SNR2, SNR3 and SNR1 respectively in figure
A.7.3.61.1-1.
Note 6: During dT between the defined Time Intervals, the Test
system shall gradually increase or decrease the SNR in
steps of ≤1 dB every 0.1 seconds until the target SNR is
achieved.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1124 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.61.1-2a: eCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test
with DRX for UE category NB1 in enhanced coverage
Parameter Unit eCell 1
T1-T4
BW channel MHz 10
NOCNG Pattern - NOP.1 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note2 dBm/15 kHz -98
dB -12
Ês N oc
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N oc .
shall be modelled as AWGN of appropriate power
Table A.7.3.61.1-3: DRX-Configuration for HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX
for UE category NB1 In-band mode in enhanced coverage
Field Value Comment
onDurationTimer pp1 As specified in clause 6.7.3 in TS
drx-InactivityTimer pp0 36.331
drx-RetransmissionTimer pp0
drx-StartOffset 0
Table A.7.3.61.1-4: TimeAlignmentTimer -Configuration for HD-FDD Radio Link Monitoring Test for
Out-of-sync in DRX for UE category NB1 In-band mode in enhanced coverage
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1125 ETSI TS 136 133 V14.3.0 (2017-04)
Figure A.7.3.61.1-1: SNR variation for HD-FDD Radio Link Monitoring Test for Out-of-sync in DRX for
UE category NB1 In-band mode in enhanced coverage
A.7.3.61.2 Test Requirements
The UE behaviors in each test shall be as follows:
- The UE shall complete the NPUSCH transmission during T2 according to the received UL grant;
- The UE shall not conduct any NPUSCH transmission during T4.
A correct event is defined as UE behaves correctly in all above steps. The correct events observed during repeated tests
shall be at least 90%.
A.7.3.62 HD-FDD Radio Link Monitoring Test for In-sync with DRX for UE
Category NB1 In-Band mode in Enhanced Coverage
A.7.3.62.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category NB1 UE configured in enhanced coverage properly
detects the out of sync and in sync for the purpose of monitoring downlink radio link quality of the NB-IoT Cell when
DRX is used. This test will partly verify the HD-FDD radio link monitoring requirements in clause 7.23.
The test parameters are given in Tables A.7.3.62.1-1, A.7.3.62.1-2, A.7.3.62.1-3, A.7.3.62.1-4 and A.7.3.62.1-5. nCell 1
is the active cell in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively, excluding the transition time duration dT, where the SNR increases or decreases gradually in small steps.
Figure A.7.3.62.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync
states.
Prior to the start of the time duration T1, the UE shall be fully be synchronized to nCell 1. The UE is scheduled in every
uplink subframe to transmit NPUSCH, which is received by the test equipment. By measuring the reception of the
NPUSCH, detection of out of sync and in sync requirements can be measured. In the test, DRX configuration is enabled
and DRX inactivity timer has already been expired, i.e. UE tries to decode NPDCCH and to send NPUSCH during the
period when On-duration timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment
is maintained during the test.
The test setup in each test during time durations T1, T2 and T3 shall be as follows:
- During the period from time point A to time point B, the SNR is decreasing linearly from SNR1 to SNR2.
- During the period from time point C to time point D, the SNR is increasing linearly from SNR2 to SNR3.
- During the period T3, the test system shall send the UE a grant to transmit in uplink. UE under test is expected to
decode the uplink grant and switch to uplink and complete the uplink transmission.
- Thereafter UE switches back to downlink.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1126 ETSI TS 136 133 V14.3.0 (2017-04)
In each run of the test, the test equipment selects NPDCCH repetition level, and sends the RRC configuration to the UE.
NPDCCH repetition level is determined by RRC parameter npdcch-NumRepetitions [3]. UE shall successfully complete
the RRC reconfiguration accordingly prior to the start of time duration T1.
Table A.7.3.62.1-1: General test parameters for HD-FDD in-sync test with DRX for UE category NB1 in
enhanced coverage
Parameter Unit Value Comment
NB-IoT operational mode In-band
Active cell nCell 1 NB-IOT cell nCell1 is within
E-UTRA cell eCell1
CP length Normal
DCI format Format N1 As defined in TS 36.212[21]
Number of OFDM 3 In sync threshold Qin_NB-IoT
symbols for legacy and the corresponding
control channels hypothetical NPDCCH
In sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 4 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH 0
to NRS EPRE
DCI format Format N1 As defined in TS 36.212 [21]
Number of OFDM 3 Out of sync threshold Qout_NB-
symbols for legacy IoT and the corresponding
control channels hypothetical NPDCCH
Out of sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 16 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH dB 0
to RS EPRE
DRX cycle ms 256 See Table A.7.3.62.1-4
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T1 s 4
dT s 2
T2 s 13
dT s 2
T3 s 4
Note 1: NPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1127 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.62.1-2: nCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test with
DRX for UE category NB1 in enhanced coverage
Parameter Unit nCell 1
T1 dT T2 dT T3
BW channel kHz 180
PRB location within eCell - 30
NPDCCH parameters defined R.27 HD-FDD
in A.3.1.6.1
Ratio of NPDSCH to NRS -3
EPRE
NPDCCH_RA dB -3
NPDCCH_RB dB -3
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB -3
NSSS_RA dB
NOCNG_RANote1 dB
NOCNG_RBNote1 dB
N oc dBm/15 Specified in Table A.7.3.62.1-3
kHz
SNR Note 5, Note 6 dB [-6.3] Note 7 [-17.4] Note 8 [-6.3]
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in ncell1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains NPDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2, and SNR3 respectively in
figure A.7.3.62.1-1.
Note 7: The Test system shall gradually reduce its transmit power in steps of 1 dB every 0.1 seconds till
SNR2 can be ensured at the end of the first dT.
Note 8: The Test system shall gradually increase its transmit power in steps of 1 dB every 0.1 seconds till
SNR3 can be ensured at the end of the second dT.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1128 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.62.1-3: eCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test with
DRX for UE category NB1 in enhanced coverage
Parameter Unit eCell 1
T1-T3
BW channel MHz 10
NOCNG Pattern - NOP.1 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note2 dBm/15 kHz -98
dB -12
Ês N oc
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N oc .
shall be modelled as AWGN of appropriate power
Table A.7.3.62.1-4: DRX-Configuration for E-UTRAN HD-FDD out-of-sync tests for UE category NB1
configured in enhanced coverage
Field Value Comment
onDurationTimer psf10 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset Sf256
shortDRX disable
Table A.7.3.62.1-5: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category NB1 configured in enhanced coverage
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1129 ETSI TS 136 133 V14.3.0 (2017-04)
SNR1
SNR2
Figure A.7.3.62.1-1: SNR variation for in-sync testing with DRX
A.7.3.62.2 Test Requirements
The UE behaviour in each test shall be as follows:
During T3, the UE under test shall decode the uplink grant and complete the uplink transmission.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.63 HD-FDD Radio Link Monitoring Test for In-sync with DRX for UE
Category NB1 In-Band mode in Normal Coverage
A.7.3.63.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category NB1 UE configured in normal coverage properly detects
the out of sync and in sync for the purpose of monitoring downlink radio link quality of the NB-IoT Cell when DRX is
used. This test will partly verify the HD-FDD radio link monitoring requirements in clause 7.23.
The test parameters are given in Tables A.7.3.63.1-1, A.7.3.63.1-2, A.7.3.63.1-3, A.7.3.63.1-4 and A.7.3.63.1-5. nCell 1
is the active cell in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively, excluding the transition time duration dT, where the SNR increases or decreases gradually in small steps.
Figure A.7.3.63.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync
states.
Prior to the start of the time duration T1, the UE shall be fully be synchronized to nCell 1. The UE is scheduled in every
uplink subframe to transmit NPUSCH, which is received by the test equipment. By measuring the reception of the
NPUSCH, detection of out of sync and in sync requirements can be measured. In the test, DRX configuration is enabled
and DRX inactivity timer has already been expired, i.e. UE tries to decode NPDCCH and to send NPUSCH during the
period when On-duration timer is running. Time alignment timers shall be set to “infinity” so that UL timing alignment
is maintained during the test.
The test setup in each test during time durations T1, T2 and T3 are as follows:
- During the period from time point A to time point B, the SNR is decreasing linearly from SNR1 to SNR2.
- During the period from time point C to time point D, the SNR is increasing linearly from SNR2 to SNR3.
- During the period T3, the test system shall send the UE a grant to transmit in uplink. UE under test is expected to
decode the uplink grant and switch to uplink and complete the uplink transmission.
- Thereafter UE switches back to downlink.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1130 ETSI TS 136 133 V14.3.0 (2017-04)
In each run of the test, the test equipment selects NPDCCH repetition level, and sends the RRC configuration to the UE.
NPDCCH repetition level is determined by RRC parameter npdcch-NumRepetitions [2]. UE shall successfully complete
the RRC reconfiguration accordingly prior to the start of time duration T1.
Table A.7.3.63.1-1: General test parameters for HD-FDD in-sync test with DRX for UE category NB1 in
normal coverage
Parameter Unit Value Comment
NB-IoT operational mode In-band
Active cell nCell 1 NB-IOT cell nCell1 is within
E-UTRA cell eCell1
CP length Normal
DCI format Format N1 As defined in TS 36.212 [21]
Number of OFDM 3 In sync threshold Qin_NB-IoT
symbols for legacy and the corresponding
control channels hypothetical NPDCCH
In sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 2 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH 0
to NRS EPRE
DCI format Format N1 As defined in TS 36.212[21]
Number of OFDM 3 Out of sync threshold Qout_NB-
symbols for legacy IoT and the corresponding
control channels hypothetical NPDCCH
Out of sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 8 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH dB 0
to RS EPRE
DRX cycle ms 256 See Table A.7.3.63.1-4
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T1 s 4
dT s 2
T2 s 13
dT s 2
T3 s 4
Note 1: NPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1131 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.63.1-2: nCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test with
DRX for UE category NB1 in normal coverage
Parameter Unit nCell 1
T1 dT T2 dT T3
BW channel kHz 180
PRB location within eCell - 30
NPDCCH parameters defined R.27 HD-FDD
in A.3.1.6.1
Ratio of NPDSCH to NRS -3
EPRE
NPDCCH_RA dB -3
NPDCCH_RB dB -3
NPBCH_RA dB
NPBCH_RB dB
NPSS_RA dB -3
NSSS_RA dB
NOCNG_RANote1 dB
NOCNG_RBNote1 dB
N oc dBm/15 Specified in Table A.7.3.63.1-3
kHz
SNR Note 5, Note 6 dB [-3.1] Note 7 [-14.1] Note 8 [-3.1]
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in ncell1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains NPDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2, and SNR3 respectively in
figure A.7.3.63.1-1.
Note 7: The Test system shall gradually reduce its transmit power in steps of 1 dB every 0.1 second till
SNR2 can be ensured at the end of the first dT.
Note 8: The Test system shall gradually increase its transmit power in steps of 1 dB every 0.1 second till
SNR3 can be ensured at the end of the second dT.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1132 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.63.1-3: eCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test with
DRX for UE category NB1 in normal coverage
Parameter Unit eCell 1
T1-T3
BW channel MHz 10
NOCNG Pattern - NOP.1 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note2 dBm/15 kHz -98
dB 4
Ês N oc
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N oc .
shall be modelled as AWGN of appropriate power
Table A.7.3.63.1-4: DRX-Configuration for E-UTRAN HD-FDD out-of-sync tests for UE category NB1
configured in normal coverage
Field Value Comment
onDurationTimer psf10 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset Sf256
shortDRX disable
Table A.7.3.63.1-5: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category NB1 configured in normal coverage
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section 10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1133 ETSI TS 136 133 V14.3.0 (2017-04)
SNR1
SNR2
Figure A.7.3.63.1-1: SNR variation for in-sync testing with DRX
A.7.3.63.2 Test Requirements
The UE behaviour in each test shall be as follows:
During the period T3, the UE under test is expected to decode the uplink grant and switch to uplink and complete the
uplink transmission. This is considered a correct event.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.64 HD-FDD Radio Link Monitoring Test for In-sync without DRX for UE
Category NB1 In-Band mode in Normal Coverage
A.7.3.64.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category NB1 UE configured in normal coverage properly detects
the out of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is used.
This test will partly verify the HD-FDD radio link monitoring requirements in clause 7.23.
The test parameters are given in Tables A.7.3.64.1-1, A.7.3.64.1-2, A.7.3.64.1-3, A.7.3.64.1-4 and A.7.3.64.1-5. nCell 1
is the active cell in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively, excluding the transition time duration dT, where the SNR increases or decreases gradually in small steps.
Figure A.7.3.64.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync
states.
Prior to the start of the time duration T1, the UE shall be fully be synchronized to nCell 1. The UE is scheduled in every
uplink subframe to transmit NPUSCH, which is received by the test equipment. By measuring the reception of the
NPUSCH, detection of out of sync and in sync requirements can be measured. In the test, DRX configuration is
disabled, i.e. UE tries to decode NPDCCH and to send NPUSCH during the period when On-duration timer is running.
Time alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the test.
The test setup in each test during time durations T1, T2, dT and T3 shall be as follows:
- During the period from time point A to time point B, the SNR is decreasing linearly from SNR1 to SNR2.
- During the period from time point C to time point D, the SNR is increasing linearly from SNR2 to SNR3.
- During the period T3, the test system shall send the UE a grant to transmit in uplink. UE under test is expected to
decode the uplink grant and switch to uplink and complete the uplink transmission.
- Thereafter UE switches back to downlink.
In each run of the test, the test equipment selects NPDCCH repetition level, and sends the RRC configuration to the UE.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1134 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.64.1-1: General test parameters for HD-FDD in-sync test without DRX for UE category
NB1 in normal coverage
Parameter Unit Value Comment
NB-IoT operational mode In-band
Active cell nCell 1 NB-IOT cell nCell1 is within
E-UTRA cell eCell1
CP length Normal
DCI format Format N1 As defined in TS 36.212 [21]
Number of OFDM 3 In sync threshold Qin_NB-IoT
symbols for legacy and the corresponding
control channels hypothetical NPDCCH
In sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 2 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH 0
to NRS EPRE
DCI format Format N1 As defined in TS 36.212[21]
Number of OFDM 3 Out of sync threshold Qout_NB-
symbols for legacy IoT and the corresponding
control channels hypothetical NPDCCH
Out of sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 8 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH dB 0
to RS EPRE
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T1 s 4
dT s 2
T2 s 13
dT s 2
T3 s 4
Note 1: NPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1135 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.64.1-2: nCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test
without DRX for UE category NB1 in normal coverage
Parameter Unit nCell 1
T1 dT T2 dT T3
BW channel kHz 200
PRB location within eCell - 30
NPDCCH parameters defined R.27 HD-FDD
in A.3.1.6.1
OCNG Pattern defined in NOP.1 FDD
A.3.2.3
NPDSCH_RA -3
NPDSCH_RB -3
NPDCCH_RA dB -3
NPDCCH_RB dB -3
NPBCH_RA dB
NPBCH_RB dB -3
NPSS_RA dB
NSSS_RA dB
NOCNG_RANote1 dB
NOCNG_RBNote1 dB
N oc dBm/15 Specified in Table A.7.3.64.1-3
kHz
SNR Note 5, Note 6 dB [-3.1] Note 7 [-14.1] Note 8 [-3.1]
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in ncell1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains NPDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2, and SNR3 respectively in
figure A.7.3.64.1-1.
Note 7: The Test system shall gradually reduce its transmit power in steps of ≤1dB every 0.1 seconds till
SNR2 can be ensured at the end of the first dT.
Note 8: The Test system shall gradually increase its transmit power in steps of ≤1dB every 0.1 seconds till
SNR1 can be ensured at the end of the second dT.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1136 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.64.1-3: eCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test
without DRX for UE category NB1 in normal coverage
Parameter Unit eCell 1
T1-T3
BW channel MHz 10
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note2 dBm/15 kHz -98
dB 6
Ês N oc
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N oc .
shall be modelled as AWGN of appropriate power
Table A.7.3.64.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category NB1 configured in normal coverage
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS
sr-ConfigIndex 0
36.331 and section 10.1 in TS 36.213.
SNR1
SNR2
Figure A.7.3.64.1-1: SNR variation for in-sync testing without DRX
A.7.3.64.2 Test Requirements
During the period from T3, the UE behaviors in each test shall be as follows:
UE under test is expected to decode the uplink grant and switch to uplink and complete the uplink transmission. This is
considered a correct event.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1137 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.3.65 HD-FDD Radio Link Monitoring Test for In-sync without DRX for UE
Category NB1 In-Band mode in Enhanced Coverage
A.7.3.65.1 Test Purpose and Environment
The purpose of this test is to verify that the HD-FDD category NB1 UE configured in enhanced coverage properly
detects the out of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell when DRX is
used. This test will partly verify the HD-FDD radio link monitoring requirements in clause 7.23.
The test parameters are given in Tables A.7.3.65.1-1, A.7.3.65.1-2, A.7.3.65.1-3, A.7.3.65.1-4 and A.7.3.65.1-5. nCell 1
is the active cell in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3
respectively, excluding the transition time duration dT, where the SNR increases or decreases gradually in small steps.
Figure A.7.3.65.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync
states.
Prior to the start of the time duration T1, the UE shall be fully be synchronized to nCell 1. The UE is scheduled in every
uplink subframe to transmit NPUSCH, which is received by the test equipment. By measuring the reception of the
NPUSCH, detection of out of sync and in sync requirements can be measured. In the test, DRX configuration is
disabled, i.e. UE tries to decode NPDCCH and to send NPUSCH during the period when On-duration timer is running.
Time alignment timers shall be set to “infinity” so that UL timing alignment is maintained during the test.
The test setup in each test during time durations T1, T2, dT and T3 shall be as follows:
- During the period from time point A to time point B, the SNR is decreasing linearly from SNR1 to SNR2.
- During the period from time point C to time point D, the SNR is increasing linearly from SNR2 to SNR3.
- During the period T3, the test system shall send the UE a grant to transmit in uplink. UE under test is expected to
decode the uplink grant and switch to uplink and complete the uplink transmission.
- Thereafter UE switches back to downlink.
In each run of the test, the test equipment selects NPDCCH repetition level, and sends the RRC configuration to the UE.
UE shall successfully complete the RRC reconfiguration accordingly prior to the start of time duration T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1138 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.65.1-1: General test parameters for HD-FDD in-sync test without DRX for UE category
NB1 in enhanced coverage
Parameter Unit Value Comment
NB-IoT operational mode In-band
Active cell nCell 1 NB-IOT cell nCell1 is within
E-UTRA cell eCell1
CP length Normal
DCI format Format N1 As defined in TS 36.212[21]
Number of OFDM 3 In sync threshold Qin_NB-IoT
symbols for legacy and the corresponding
control channels hypothetical NPDCCH
In sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 4 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH 0
to NRS EPRE
DCI format Format N1 As defined in TS 36.212[21]
Number of OFDM 3 Out of sync threshold Qout_NB-
symbols for legacy IoT and the corresponding
control channels hypothetical NPDCCH
Out of sync NPDCCH eCCE 2 transmission parameters are
transmission aggregation level as specified in clause 7.23.2
parameters NPDCCH repetition 16 and Table 7.23.2-1
(Note 1) level respectively.
Ratio of NPDSCH 0
to NRS EPRE
Ratio of NPDCCH dB 0
to RS EPRE
Layer 3 filtering Enabled Counters:
N310 = 1; N311 = 1
T310 timer ms 2000 T310 is enabled
T311 timer ms 1000 T311 is enabled
T1 s 4
dT s 2
T2 s 13
dT s 2
T3 s 4
Note 1: NPDCCH corresponding to the in-sync and out of sync transmission parameters
need not be included in the Reference Measurement Channel.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1139 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.65.1-2: nCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test
without DRX for UE category NB1 in enhanced coverage
Parameter Unit nCell 1
T1 dT T2 dT T3
BW channel kHz 200
PRB location within eCell - 30
NPDCCH parameters defined R.27 HD-FDD
in A.3.1.6.1
OCNG Pattern defined in NOP.1 FDD
A.3.2.3
NPDSCH_RA -3
NPDSCH_RB -3
NPDCCH_RA dB -3
NPDCCH_RB dB -3
NPBCH_RA dB
NPBCH_RB dB -3
NPSS_RA dB
NSSS_RA dB
NOCNG_RANote1 dB
NOCNG_RBNote1 dB
N oc dBm/15 Specified in Table A.7.3.65.1-3
kHz
SNR Note 5, Note 6 dB [-6.3] Note 7 [-17.4] Note 8 [-6.3]
Propagation condition AWGN
Correlation Matrix and 2x1
Antenna Configuration
Note 1: OCNG shall be used such that the resources in ncell1 are fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The uplink resources for CQI reporting are assigned to the UE prior to the start of time period T1.
Note 3: The timers and layer 3 filtering related parameters are configured prior to the start of time period
T1.
Note 4: The signal contains NPDCCH for UEs other than the device under test as part of OCNG.
Note 5: SNR levels correspond to the signal to noise ratio over the cell-specific reference signal REs.
Note 6: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2, and SNR3 respectively in
figure A.7.3.65.1-1.
Note 7: The Test system shall gradually reduce its transmit power in steps of ≤1dB every 0.1 seconds till
SNR2 can be ensured at the end of the first dT.
Note 8: The Test system shall gradually increase its transmit power in steps of ≤1dB every 0.1 seconds till
SNR1 can be ensured at the end of the second dT.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1140 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.3.65.1-3: eCell 1 specific test parameters for HD-FDD in-sync radio link monitoring test
without DRX for UE category NB1 in enhanced coverage
Parameter Unit eCell 1
T1-T3
BW channel MHz 10
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note2 dBm/15 kHz -98
dB 0
Ês N oc
Propagation Condition AWGN
Antenna Configuration 1x1
Note 1: OCNG shall be used such that the eCell is fully allocated and a
constant total transmitted power spectral density is achieved for
all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in
the test is assumed to be constant over subcarriers and time and
N oc .
shall be modelled as AWGN of appropriate power
Table A.7.3.65.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD out-of-sync testing for
UE category NB1 configured in enhanced coverage
Field Value Comment
TimeAlignmentTimer infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS
sr-ConfigIndex 0
36.331 and section 10.1 in TS 36.213.
SNR1
SNR2
Figure A.7.3.65.1-1: SNR variation for in-sync testing without DRX
A.7.3.65.2 Test Requirements
During the period T3, the UE behaviors in each test shall be as follows:
UE under test is expected to decode the uplink grant and switch to uplink and complete the uplink transmission. This is
considered a correct event.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1141 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.4 Interruption for Dual Connectivity
A.7.4.1 E-UTRAN FDD-FDD DC interruption at transitions between active
and non-active during DRX in synchronous DC
A.7.4.1.1 Test Purpose and Environment
The purpose of this test is to verify that when PCell is in non-DRX and PSCell is in DRX, PCell interruptions due to
transitions from active to non-active and from non-active to active during PSCell DRX the UE missed ACK/NACK
does not exceed the limits. This test will verify the missed ACK/NACK rate for FDD PCell in dual connectivity
requirements in clause 7.12.2.
The test parameters are given in Table A.7.4.1.1-1, A.7.4.1.1-2 and A.7.4.1.1-3 below. In the test there are two cells:
Cell1 and Cell2. Cell1 is PCell and Cell2 is PSCell. PCell is continuously scheduled in DL while PSCell is not
scheduled and has DRX configured. The test consists of one time period, with duration of T1. Prior to the start of the
time duration T1, the UE shall be fully synchronized to Cell1 and Cell2. Cell1 shall be configured as PCell and Cell2
shall be configured as PSCell. Prior to start of T1 the DRX inactivity timer for the PSCell have already expired. During
T1 the UE shall be continuously scheduled on PCell while not scheduled on PSCell.
Table A.7.4.1.1-1: General test parameters for E-UTRAN FDD-FDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Value Comment
E-UTRA RF Channel Two radio channels are used for this test.
1, 2
Number
Active PCell Cell1 PCell on RF channel number 1.
Configured PSCell Cell2 PSCell on RF channel number 2.
CP length Normal
DRX DRX related parameters are defined in
ON
Table A.8.23.4.1-3
Measurement gap pattern
OFF
Id
T1 s 10
Note 1: This test verifies the RRM requirement which is independent of channel bandwidth and is
performed according to the principle defined in section A.3.6.1.
Note 2: A UE capable of both synchronous and asynchronous DC operations is only required to pass
this test case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1142 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.1.1-2: Cell specific test parameters for E-UTRAN FDD-FDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Cell1 Cell2
T1 T1
E-UTRA RF Channel
1 2
Number
BW channel MHz 5MHz: NRB,c = 25 5MHz: NRB,c = 25
10MHz: NRB,c = 50 10MHz: NRB,c = 50
20MHz: NRB,c = 100 20MHz: NRB,c = 100
PDSCH parameters: 5MHz: R.7 FDD
DL Reference 10MHz: R.3 FDD -
Measurement Channel 20MHz: R.6 FDD
PCFICH/PDCCH/PHICH
5MHz: R.11 FDD 5MHz: R.11 FDD
parameters:
10MHz: R.6 FDD 10MHz: R.6 FDD
DL Reference
20MHz: R.10 FDD 20MHz: R.10 FDD
Measurement Channel
OCNG Patterns 5MHz: OP.20 FDD 5MHz: OP.16 FDD
10MHz: OP.10 FDD 10MHz: OP.2 FDD
20MHz: OP.17 FDD 20MHz: OP.12 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_PB dB 0 0
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15
-101 -101
KHz
dB
Ês N oc 19 19
dB
Ê s I ot 19 19
RSRP Note 3 dBm/15
-82 -82
KHz
SCH_RP Note 3 dBm/15
-82 -82
KHz
Note 3 dBm/Ch
Io -54.16 -54.16
BW +10log +10log
(NRB,c /50) (NRB,c /50)
Propagation Condition AWGN AWGN
Correlation Matrix and
1x2 Low 1x2 Low
Antenna Configuration
Time offset to cell1 Note 4
μs - 33
Note 1: OCNG shall be used such that both cells are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is
assumed to be constant over subcarriers and time and shall be modelled as
AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP, SCH_RP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Note 4: Receive time difference between subframe boundaries of signals received
from the two cells at the UE antenna connector including time alignment error
between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1143 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.1.1-3: DRX-Configuration for E-UTRAN FDD-FDD DC interruption at transitions between
active and non-active during DRX in synchronous DC
Cell1 Cell2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimerNote 1 psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 Sf160
shortDRX disable disable
Note 1: UE is continuously scheduled in PCell
A.7.4.1.2 Test Requirements
The UE shall be continuously scheduled in PCell during the entire length of T1. UE shall not be scheduled in PSCell
during T1. During the time duration T1 the UE shall transmit at leat 99% of ACK/NACK on PCell.
The UE shall not miss transmitting two consequtive ACK/NACK.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.4.2 E-UTRAN TDD-TDD DC interruption at transitions between active
and non-active during DRX in synchronous DC
A.7.4.2.1 Test Purpose and Environment
The purpose of this test is to verify that when PCell is in non-DRX and PSCell is in DRX, PCell interruptions due to
transitions from active to non-active and from non-active to active during PSCell DRX the UE missed ACK/NACK
does not exceed the limits. This test will verify the missed ACK/NACK rate for TDD PCell in dual connectivity
requirements in clause 7.12.2.
The test parameters are given in Table A.7.4.2.1-1, A.7.4.2.1-2 and A.7.4.2.1-3 below. In the test there are two cells:
Cell1 and Cell2. Cell1 is PCell and Cell2 is PSCell. PCell is continuously scheduled in DL while PSCell is not
scheduled and has DRX configured. The test consists of one time period, with duration of T1. Prior to the start of the
time duration T1, the UE shall be fully synchronized to Cell1 and Cell2. Cell1 shall be configured as PCell and Cell2
shall be configured as PSCell. Prior to start of T1 the DRX inactivity timer for the PSCell have already expired. During
T1 the UE shall be continuously scheduled on PCell while not scheduled on PSCell.
Table A.7.4.2.1-1: General test parameters for E-UTRAN TDD-TDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Value Comment
E-UTRA RF Channel Two radio channels are used for this test.
1, 2
Number
Active PCell Cell1 PCell on RF channel number 1.
Configured PSCell Cell2 PSCell on RF channel number 2.
Special subframe 6 As specified in table 4.2-1 in TS 36.211.
configuration Applicable to cell 1
Uplink-downlink 1 As specified in table 4.2-1 in TS 36.211.
configuration Applicable to Cell1
CP length Normal As specified in table 4.2-2 in TS 36.211.
Applicable to Cell1
DRX DRX related parameters are defined in
ON
Table A.8.23.4.1-3
Measurement gap pattern
OFF
Id
T1 s 10
Note 1: This test verifies the RRM requirement which is independent of channel bandwidth and is
performed according to the principle defined in section A.3.6.1.
Note 2: A UE capable of both synchronous and asynchronous DC operations is only required to pass
this test case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1144 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.2.1-2: Cell specific test parameters for E-UTRAN TDD-TDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Cell1 Cell2
T1 T1
E-UTRA RF Channel
1 2
Number
BW channel MHz 5MHz: NRB,c = 25 5MHz: NRB,c = 25
10MHz: NRB,c = 50 10MHz: NRB,c = 50
20MHz: NRB,c = 100 20MHz: NRB,c = 100
PDSCH parameters: 5MHz: R.4 TDD
DL Reference 10MHz: R.0 TDD -
Measurement Channel 20MHz: R.3 TDD
PCFICH/PDCCH/PHICH
5MHz: R.11 TDD 5MHz: R.11 TDD
parameters:
10MHz: R.6 TDD 10MHz: R.6 TDD
DL Reference
20MHz: R.10 TDD 20MHz: R.10 TDD
Measurement Channel
OCNG Patterns 5MHz: OP.9 TDD 5MHz: OP.10 TDD
10MHz: OP.1 TDD 10MHz: OP.2 TDD
20MHz: OP.7 TDD 20MHz: OP.7 TDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_PB dB 0 0
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15
-101 -101
KHz
dB
Ês N oc 19 19
dB
Ê s I ot 19 19
RSRP Note 3 dBm/15
-82 -82
KHz
SCH_RP Note 3 dBm/15
-82 -82
KHz
Note 3 dBm/Ch
Io -54.16 -54.16
BW +10log +10log
(NRB,c /50) (NRB,c /50)
Propagation Condition AWGN AWGN
Correlation Matrix and
1x2 Low 1x2 Low
Antenna Configuration
Time offset to cell1 Note 4
μs - 33
Note 1: OCNG shall be used such that both cells are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is
assumed to be constant over subcarriers and time and shall be modelled as
AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP, SCH_RP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Note 4: Receive time difference between subframe boundaries of signals received
from the two cells at the UE antenna connector including time alignment error
between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1145 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.2.1-3: DRX-Configuration for E-UTRAN TDD-TDD DC interruption at transitions between
active and non-active during DRX in synchronous DC
Cell1 Cell2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimerNote 1 psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 Sf160
shortDRX disable disable
Note 1: UE is continuously scheduled in PCell
A.7.4.2.2 Test Requirements
The UE shall be continuously scheduled in PCell during the entire length of T1. UE shall not be scheduled in PSCell
during T1. During the time duration T1 the UE shall transmit at leat 99% of ACK/NACK on PCell.
The UE shall not miss transmitting two consequtive ACK/NACK.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.4.3 E-UTRAN FDD-FDD Interruption at transitions between active and
non-active during DRX in asynchronous dual connectivity
A.7.4.3.1 Test Purpose and Environment
The purpose of this test is to verify that the UE fulfils the requirement on interruptions on PCell at transitions between
active and non-active during DRX in TS36.133 section 7.12.2.
The test parameters are given in Table A.7.4.3.1-1, Table A.7.4.3.1-2and Table A.7.4.3.1-3 below. In the test there are
two cells: Cell 1 and Cell 2. Cell 1 is PCell on the FDD primary component (RF channel 1). Cell 2 is PSCell on the
FDD secondary component (RF channel 2). The test consists of 1 time period, with time duration of T1. PDCCH
indicating a new transmission on PCell shall be sent continuously during the whole time duration to ensure UE would
not enter DRX state on PCell. PSCell is in DRX state with 320ms DRX cycle.
Table A.7.4.3.1-1: General test parameters for E-UTRAN FDD-FDD Interruption at transitions between
active and non-active during DRX in asynchronous dual connectivity
Parameter Unit Value Comment
E-UTRA RF Channel Two radio channels are used for this test
1, 2
Number
Active Cell Cell 1 is PCell on E-UTRA RF channel
Cell 1, Cell 2 number 1, and cell 2 is PSCell on E-UTRA
RF channel number 2
CP length Normal
DRX on Cell1 OFF
DRX on Cell2 ms 320
Filter coefficient 0 L3 filtering is not used
T1 s 5
Note 1: Even a UE capable of both synchronous and asynchronous DC operations is required to pass
this test case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1146 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.3.1-2: Cell specific test parameters for E-UTRAN FDD-FDD Interruption at transitions
between active and non-active during DRX in asynchronous dual connectivity
Parameter Unit Cell 1 Cell 2
T1 T1
E-UTRA RF Channel 1 2
Number
BW channel MHz 5: NRB,c = 25 5: NRB,c = 25
10: NRB,c = 50 10: NRB,c = 50
20: NRB,c = 100 20: NRB,c = 100
PDSCH parameters 5MHz: R.7 FDD -
10MHz: R.3 FDD
20MHz: R.6 FDD
PCFICH/PDCCH/PHIC 5MHz: R.11 FDD 5MHz: R.11 FDD
H parameters 10MHz: R.6 FDD 10MHz: R.6 FDD
20MHz: R.10 FDD 20MHz: R.10 FDD
OCNG Patterns 5MHz: OP.20 FDD 5MHz: OP.16 FDD
defined in A.3.2.1 10MHz: OP.10 FDD 10MHz: OP.2 FDD
20MHz: OP.17 FDD 20MHz: OP.12 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_PB dB
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2
dBm/15 KHz -101 -101
dB 19 19
Ês N oc
dB 19 19
Ê s I ot
RSRP Note 3 dBm/15 KHz -82 -82
SCH_RP Note 3 dBm/15 KHz -82 -82
Io Note 3 dBm/Ch BW -54.16+10log -54.16+10log
(NRB,c /50) (NRB,c /50)
Propagation Condition AWGN AWGN
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
Receive timing offset to μs 500
-
Cell1 Note 4
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 3: RSRP, SCH_RP and Io levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: Receive time difference between subframe boundaries of signals received from the two cells at
the UE antenna connector including time alignment error between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1147 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.3.1-3: DRX-Configuration for E-UTRAN FDD-FDD Interruption at transitions between
active and non-active during DRX in asynchronous dual connectivity
PSCell Comment
Field
Value
onDurationTimer psf1
drx-InactivityTimer psf1
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf320
shortDRX disable
Note: For further information see clause 6.3.2 in TS 36.331.
Table A.7.4.3.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD-FDD Interruption at
transitions between active and non-active during DRX in asynchronous dual connectivity
PSCell Comment
Field
Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.7.4.3.2 Test Requirements
The UE shall be scheduled on PCell continuously during the whole time duration T1. During time durations T1, at least
99% of all expected ACK/NACKs shall be transmitted on PCell by the UE.
Each interruption shall not exceed 1 subframe.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.4.4 E-UTRAN FDD-TDD DC interruption at transitions between active
and non-active during DRX in synchronous DC
A.7.4.4.1 Test Purpose and Environment
The purpose of this test is to verify that when PCell is in non-DRX and PSCell is in DRX, PCell interruptions due to
transitions from active to non-active and from non-active to active during PSCell DRX the UE missed ACK/NACK
does not exceed the limits. This test will verify the missed ACK/NACK rate for FDD PCell in dual connectivity
requirements in clause 7.12.2.
The test parameters are given in Table A.7.4.4.1-1, A.7.4.4.1-2 and A.7.4.4.1-3 below. In the test there are two cells:
Cell1 and Cell2. Cell1 is PCell and Cell2 is PSCell. PCell is continuously scheduled in DL while PSCell is not
scheduled and has DRX configured. The test consists of one time period, with duration of T1. Prior to the start of the
time duration T1, the UE shall be fully synchronized to Cell1 and Cell2. Cell1 shall be configured as PCell and Cell2
shall be configured as PSCell. Prior to start of T1 the DRX inactivity timer for the PSCell have already expired. During
T1 the UE shall be continuously scheduled on PCell while not scheduled on PSCell.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1148 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.4.1-1: General test parameters for E-UTRAN FDD-TDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Value Comment
E-UTRA RF Channel Two radio channels are used for this test.
1, 2
Number
Active PCell Cell1 PCell on RF channel number 1.
Configured PSCell Cell2 PSCell on RF channel number 2.
CP length Normal
DRX DRX related parameters are defined in
ON
Table A.8.23.4.1-3
Measurement gap pattern
OFF
Id
T1 s 10
Note 1: This test verifies the RRM requirement which is independent of channel bandwidth and is
performed according to the principle defined in section A.3.6.1.
Note 2: A UE capable of both synchronous and asynchronous DC operations is only required to pass
this test case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1149 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.4.1-2: Cell specific test parameters for E-UTRAN FDD-TDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Cell1 Cell2
T1 T1
E-UTRA RF Channel
1 2
Number
BW channel MHz 5MHz: NRB,c = 25 5MHz: NRB,c = 25
10MHz: NRB,c = 50 10MHz: NRB,c = 50
20MHz: NRB,c = 100 20MHz: NRB,c = 100
PDSCH parameters: 5MHz: R.7 FDD
DL Reference 10MHz: R.3 FDD -
Measurement Channel 20MHz: R.6 FDD
PCFICH/PDCCH/PHICH
5MHz: R.11 FDD 5MHz: R.11 TDD
parameters:
10MHz: R.6 FDD 10MHz: R.6 TDD
DL Reference
20MHz: R.10 FDD 20MHz: R.10 TDD
Measurement Channel
OCNG Patterns 5MHz: OP.20 FDD 5MHz: OP.10 TDD
10MHz: OP.10 FDD 10MHz: OP.2 TDD
20MHz: OP.17 FDD 20MHz: OP.8 TDD
Special subframe
Not applicable 6
configuration
Uplink-downlink
Not applicable 1
configuration
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_PB dB 0 0
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15
-101 -101
KHz
dB
Ês N oc 19 19
dB
Ê s I ot 19 19
Note 3
RSRP dBm/15
-82 -82
KHz
SCH_RP Note 3 dBm/15
-82 -82
KHz
Io Note 3 dBm/Ch -54.16 -54.16
BW +10log +10log
(NRB,c /50) (NRB,c /50)
Propagation Condition AWGN AWGN
Correlation Matrix and
1x2 Low 1x2 Low
Antenna Configuration
Time offset to cell1 Note 4
μs - 33
Note 1: OCNG shall be used such that both cells are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is
assumed to be constant over subcarriers and time and shall be modelled as
AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP, SCH_RP and Io levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Note 4: Receive time difference between subframe boundaries of signals received
from the two cells at the UE antenna connector including time alignment error
between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1150 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.4.1-3: DRX-Configuration for E-UTRAN FDD-TDD DC interruption at transitions between
active and non-active during DRX in synchronous DC
Cell1 Cell2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimerNote 1 psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 Sf160
shortDRX disable disable
Note 1: UE is continuously scheduled in PCell
A.7.4.4.2 Test Requirements
The UE shall be continuously scheduled in PCell during the entire length of T1. UE shall not be scheduled in PSCell
during T1. During the time duration T1 the UE shall transmit at leat 99% of ACK/NACK on PCell.
The UE shall not miss transmitting two consequtive ACK/NACK.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.4.5 E-UTRAN TDD-FDD DC interruption at transitions between active
and non-active during DRX in synchronous DC
A.7.4.5.1 Test Purpose and Environment
The purpose of this test is to verify that when PCell is in non-DRX and PSCell is in DRX, PCell interruptions due to
transitions from active to non-active and from non-active to active during PSCell DRX the UE missed ACK/NACK
does not exceed the limits. This test will verify the missed ACK/NACK rate for TDD PCell in dual connectivity
requirements in clause 7.12.2.
The test parameters are given in Table A.7.4.5.1-1, A.7.4.5.1-2 and A.7.4.5.1-3 below. In the test there are two cells:
Cell1 and Cell2. Cell1 is PCell and Cell2 is PSCell. PCell is continuously scheduled in DL while PSCell is not
scheduled and has DRX configured. The test consists of one time period, with duration of T1. Prior to the start of the
time duration T1, the UE shall be fully synchronized to Cell1 and Cell2. Cell1 shall be configured as PCell and Cell2
shall be configured as PSCell. Prior to start of T1 the DRX inactivity timer for the PSCell have already expired. During
T1 the UE shall be continuously scheduled on PCell while not scheduled on PSCell.
Table A.7.4.5.1-1: General test parameters for E-UTRAN TDD-FDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Value Comment
E-UTRA RF Channel Two radio channels are used for this test.
1, 2
Number
Active PCell Cell1 PCell on RF channel number 1.
Configured PSCell Cell2 PSCell on RF channel number 2.
Special subframe 6 As specified in table 4.2-1 in TS 36.211.
configuration Applicable to cell 1
Uplink-downlink 1 As specified in table 4.2-1 in TS 36.211.
configuration Applicable to Cell1
CP length Normal As specified in table 4.2-2 in TS 36.211.
Applicable to Cell1
DRX DRX related parameters are defined in
ON
Table A.8.23.4.1-3
Measurement gap pattern
OFF
Id
T1 s 10
Note 1: This test verifies the RRM requirement which is independent of channel bandwidth and is
performed according to the principle defined in section A.3.6.1.
Note 2: A UE capable of both synchronous and asynchronous DC operations is only required to
pass this test case in accordance with the principle defined in section A.3.11.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1151 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.5.1-2: Cell specific test parameters for E-UTRAN TDD-FDD DC interruption at transitions
between active and non-active during DRX in synchronous DC
Parameter Unit Cell1 Cell2
T1 T1
E-UTRA RF Channel
1 2
Number
BW channel MHz 5MHz: NRB,c = 25 5MHz: NRB,c = 25
10MHz: NRB,c = 50 10MHz: NRB,c = 50
20MHz: NRB,c = 100 20MHz: NRB,c = 100
PDSCH parameters: 5MHz: R.4 TDD
DL Reference 10MHz: R.0 TDD -
Measurement Channel 20MHz: R.3 TDD
PCFICH/PDCCH/PHICH
5MHz: R.11 TDD 5MHz: R.11 FDD
parameters:
10MHz: R.6 TDD 10MHz: R.6 FDD
DL Reference
20MHz: R.10 TDD 20MHz: R.10 FDD
Measurement Channel
OCNG Patterns 5MHz: OP.9 TDD 5MHz: OP.16 FDD
10MHz: OP.1 TDD 10MHz: OP.2 FDD
20MHz: OP.7 TDD 20MHz: OP.12 FDD
Special subframe
6 Not applicable
configuration
Uplink-downlink
1 Not applicable
configuration
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_PB dB 0 0
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15
-101 -101
KHz
dB
Ês N oc 19 19
dB
Ê s I ot 19 19
Note 3
RSRP dBm/15
-82 -82
KHz
SCH_RP Note 3 dBm/15
-82 -82
KHz
Io Note 3 dBm/Ch -54.16 -54.16
BW +10log +10log
(NRB,c /50) (NRB,c /50)
Propagation Condition AWGN AWGN
Correlation Matrix and
1x2 Low 1x2 Low
Antenna Configuration
Time offset to cell1 Note 4
μs - 33
Note 1: OCNG shall be used such that both cells are fully allocated and a constant
total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is
assumed to be constant over subcarriers and time and shall be modelled as
AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Note 4: Receive time difference between subframe boundaries of signals received
from the two cells at the UE antenna connector including time alignment error
between the two cells.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1152 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.4.5.1-3: DRX-Configuration for E-UTRAN TDD-FDD DC interruption at transitions between
active and non-active during DRX in synchronous DC
Cell1 Cell2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimerNote 1 psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf80 Sf160
shortDRX disable disable
Note 1: UE is continuously scheduled in PCell
A.7.4.5.2 Test Requirements
The UE shall be continuously scheduled in PCell during the entire length of T1. UE shall not be scheduled in PSCell
during T1. During the time duration T1 the UE shall transmit at leat 99% of ACK/NACK on PCell.
The UE shall not miss transmitting two consequtive ACK/NACK.
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.5 Proximity-based Services
A.7.5.1 E-UTRAN FDD – UE ProSe Direct Discovery Transmission Timing
Accuracy Test
A.7.5.1.1 Test Purpose and Environment
The purpose of this test is to verify the timing requirements for ProSe Direct Discovery transmissions when PCell
downlink timing is used as a reference with N TA, SL = 0 . This test will verify the requirements in clause 7.16.2.1.1.1
ProSe Direct Discovery transmissions. In the test the UE under test is configured for ProSe operation only on PCell and
also the UE is configured only for PCell for WAN.
For this test, the UE is triggered by the test loop function or the upper layers to announce ProSe Direct Discovery.
The test parameters are given in Table A.7.5.1.1-1 below. There is one active cell (PCell) in this test. The transmit
timing is verified using the transmission timing of PSDCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1153 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.1.1-1: Test parameters for ProSe Transmission Timing Accuracy test for E-UTRAN FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1
Channel Bandwidth (BW channel) MHz 5
E-UTRA FDD Cell1 on RF
Active cell Cell 1
channel number 1
CP length of Cell 1 Normal
As specified in Table A.3.12.2-
drx-Configuration DRX_P1
1
ProSe Direct Discovery resource pool As specified in IE values unless specified
configuration Table A.3.12.4-1 otherwise in this test.
(Configuration #1)
PDCCH/PCFICH/PHICH Reference
R.11 FDD
measurement channelNote1
OCNG PatternNote2 OP.16 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote3
OCNG_RBNote3
Noc dBm/15 kHz -98
Ês Noc dB 3
RSRP Note4 dBm/15 kHz -95
SCH_RP Note 4 dBm/15 kHz -95
Propagation condition AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.7.5.1.2 Test Requirements
For parameters specified in Tables A.7.5.1.1-1, the timing accuracy for ProSe Direct Discvoery transmissions shall be
within the limits defined in clause 7.16.2.
The following sequence of events shall be used to verify that the requirements are met.
For the 5MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED DRX with a cycle
length of 320ms:
a) After a connection is set up with the cell, the test system shall verify that the ProSe UE transmit timing offset is
within ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +32×TS (approximately +1µs) compared to
that in (a). The test system shall wait for at least one discovery period (320ms) before verifying the requirement
again in (c).
c) The test system shall verify that the UE transmit timing offset stays within ± 12×TS with respect to the first
detected path (in time) of the corresponding downlink frame of cell 1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1154 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.5.2 E-UTRAN TDD – UE ProSe Direct Discovery Transmission Timing
Accuracy Test
A.7.5.2.1 Test Purpose and Environment
The purpose of this test is to verify the timing requirements for ProSe Direct Discovery transmissions when PCell
downlink timing is used as a reference with N TA, SL = 0 . This test will verify the requirements in clause 7.16.2.1.1.1 for
ProSe Direct Discovery transmissions. In the test the UE under test is configured for ProSe operation only on PCell and
also the UE is configured only for PCell for WAN.
For this test, the UE is triggered by the test loop function or the upper layers to announce ProSe Direct Discovery.
The test parameters are given in Table A.7.5.2.1-1 below. There is one active cell (PCell) in this test. The transmit
timing is verified using the transmission timing of PSDCH.
Table A.7.5.2.1-1: Test parameters for ProSe Transmission Timing Accuracy test for E-UTRAN TDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1
Channel Bandwidth (BW channel) MHz 5
E-UTRA FDD Cell1 on RF
Active cell Cell 1
channel number 1
Uplink/Downlink Configuration Config 0
Special Subframe Configuration 6
CP length of Cell 1 Normal
As specified in Table A.3.12.2-
drx-Configuration DRX_P1
1
ProSe Direct Discovery resource pool As specified in IE values unless specified
configuration Table A.3.12.4-3 otherwise in this test.
(Configuration #3)
PDCCH/PCFICH/PHICH Reference
R.11 TDD
measurement channelNote1
OCNG PatternNote2 OP.10 TDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote3
OCNG_RBNote3
Noc dBm/15 kHz -98
Ês Noc dB 3
RSRP Note4 dBm/15 kHz -95
SCH_RP Note 4 dBm/15 kHz -95
Propagation condition AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1155 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.5.1.2 Test Requirements
For parameters specified in Tables A.7.5.2.1-1, the timing accuracy for ProSe Direct Discvoery transmissions shall be
within the limits defined in clause 7.16.2.
The following sequence of events shall be used to verify that the requirements are met.
For the 5MHz channel bandwidth, the test sequence shall be carried out in RRC_CONNECTED DRX with a cycle
length of 320ms:
a) After a connection is set up with the cell, the test system shall verify that the ProSe UE transmit timing offset is
within 624×TS ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of
cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +32×TS (approximately +1µs) compared to
that in (a). The test system shall wait for at least one discovery period (320ms) before verifying the requirement
again in (c).
c) The test system shall verify that the UE transmit timing offset stays within 624×TS ± 12×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1.
A.7.5.3 E-UTRAN FDD - Interruptions due to ProSe Direct Discovery
A.7.5.3.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to the allowed PCell interruptions due to ProSe Direct
Discovery defined in clause 7.16.3.1 and clause 7.16.3.3. In the test the UE under test is configured for ProSe operation
only on PCell and also the UE is configured only for PCell for WAN.
For this test, the UE is triggered by the test loop function or the upper layers to monitor ProSe Direct Discovery.
The test parameters are given in Table A.7.5.3.1-1 and Table A.7.5.3.1-2 below. There is one active cell (PCell) in this
test and 24 active Sidelink transmissions in this test (with 12 active Sidelink UEs per configured discovery subframe).
Two tests (Test 1 and Test 2) are defined to verify interruptions due to synchronous (Test 1) and asynchronous (Test 2)
ProSe Direct Discovery.
The tests consist of three successive time periods, with time duration of T1, T2 and T3 respectively.
During T1, the UE is in RRC_IDLE and monitoring the ProSe Direct Discovery announcements from other active
Sidelink UEs on the ProSe Direct Discvoery resources.
During T2, the test system establishes a RRC connection with the UE. No PDSCH traffic is scheduled for UE during
T2, and the UE is expected to transmit SidelinkUEInformation indicating discRxInterest during T2. On reception of
SidelinkUEInformation, the test system shall RRC reconfiguration message to the UE and wait for the UE to respond
with RRC reconfiguration complete message before transitioning to T3. If the UE does not transmit
SidelinkUEInformation for up to [2] sec, the test system shall transition to T3.
During T3, the UE is scheduled with PDSCH traffic on PCell downlink. The test system will count the missed
ACK/NACKs during T3 to verify the allowed interruptions during ProSe Direct Discovery.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1156 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.3.1-1: Test parameters for interruption due to ProSe Direct Discovery tests
Value
Parameter Unit Comment
Test 1 Test 2
E-UTRA RF Channel Number 1
Channel Bandwidth (BW channel) MHz 5
E-UTRA FDD Cell1
Active cell Cell 1 on RF channel
number 1
CP length of Cell 1 Normal
T1 s 5.12
Up to receiving RRC reconfiguration setup
complete from the UE, or up to [2] sec if UE
T2 s
does not transmit SidelinkUEInformation
during this period.
T3 s 10.24
Table A.7.5.3.1-2: ProSe Direct Discovery configuration for interruption due to ProSe Direct
Discovery tests
Value
Parameter Unit Comment
Test 1 Test 2
E-UTRA RF Channel Number 1 UL carrier frequency
Channel Bandwidth
MHz 5
(BW channel)
ProSe Direct Discovery As specified in Table As specified in Table IE values unless
resource pool configuration A.3.12.4-1 A.3.12.4-2 specified otherwise
(Configuration #1) (Configuration #2) in this test.
Transmitting ProSe
PDP.1.FDD PDP.2.FDD
Active Sidelink UEs Direct Discovery
As specified in Table As specified in Table
Configuration (Test 1 and 2) and
A.3.12.8.2-1 A.3.12.8.2-1
SLSS (for Test 2)
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1157 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.3.1-3: Cell specific test parameters for interruption due to ProSe Direct Discovery tests
Cell 1
Parameter Unit
T1 T2 T3
E-UTRA RF Channel Number 1
BW channel MHz 5
UE RRC state IDLE CONNECTED
defaultPagingCycle rf256
Paging configuration N/A
nB T / 32
DRX N/A OFF
PDSCH Reference measurement channel
N/A None R.5 FDD
defined in A.3.1.1.1Note1
PDCCH/PCFICH/PHICH Reference
R.11 FDD
measurement channel defined in A.3.1.2.1Note1
OCNG Pattern OP.16 FDD OP.15 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
Noc Note2 dBm/15 kHz -98
Ês N oc dB 16
RSRP Note3 dBm/15 kHz -82
SCH_RP Note 3 dBm/15 kHz -82
Propagation Condition AWGN
Note 1: OCNG shall be used such that cell is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.7.5.3.2 Test Requirements
The UE shall be scheduled on PCell continuously during T3.
In Test 1, at least 98.75% of all expected ACK/NACKs during T3 shall be transmitted by the ProSe UE. The missed
ACK/NACKs can occur only on subframe ‘n’, if either n±1 subframe is a discovery subframe, or if n-3, or n-5 is a
discovery subframe.
NOTE: For the test configuration in Table A.7.5.3.1-1 and Table A.7.5.3.1-2, the specific subframes where
missed ACK/NACKs are allowed are when (subframe mod 320) = 159, 163, 162, 166, corresponding to
allowed interruptions on subframe 159 and 162.
In Test 2, at least 97.5% of all expected ACK/NACKs during T3 shall be transmitted by the ProSe UE. The missed
ACK/NACK can occur only on subframe ‘n’, if either n±5 subframe is a discovery or SLSS subframe, or if n+1, or n-9
is a discovery or SLSS subframe.
NOTE: For the test configuration in Table A.7.5.3.1-1 and Table A.7.5.3.1-2, the specific subframes where
missed ACK/NACKs are allowed are when (subframe mod 320) = 135, 139, 145, 149, 155, 159, 166,
170, corresponding to allowed interruptions on subframes 135, 145, 155 and 166.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1158 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.5.4 E-UTRAN FDD – UE ProSe Direct Communication Transmission
Timing Accuracy Test
A.7.5.4.1 Test Purpose and Environment
The purpose of this test is to verify the timing requirements for ProSe Direct Communication transmissions when PCell
downlink timing is used as a reference with N TA, SL = 0 . This test will verify the requirements in clause 7.16.2.1.1.1 for
ProSe Direct Communication transmissions. In the test the UE under test is configured for ProSe operation only on
PCell and also the UE is configured only for PCell for WAN.
For this test, the UE is triggered by the test loop function or the upper layers to transmit for ProSe Direct
Communication.
The test parameters are given in Table A.7.5.4.1-1 below. There is one active cell (PCell) in this test. The test system
will configure the ProSe UE to transmit SLSS in each period (40ms) by configuring networkControlledSyncTx as ON
via dedicated RRC signaling. The transmit timing is verified using the transmission timing of SLSS transmissions.
Table A.7.5.4.1-1: Test parameters for ProSe Transmission Timig Accuracy test for E-UTRAN FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1
Channel Bandwidth (BW channel) MHz 5 or 10 Note 5
E-UTRA FDD Cell1 on RF
Active cell Cell 1
channel number 1
CP length of Cell 1 Normal
As specified in Table
drx-Configuration DRX_P1
A.3.12.2-1
ProSe Direct Communication configuration As specified in Table IE values unless specified
A.3.12.5-1 otherwise in this test.
(Configuration #1)
networkControlledSyncTx ON Configured
PDCCH/PCFICH/PHICH Reference 5 MHz: R.11 FDD
measurement channelNote1 10 MHz: R.6 FDD
5 MHz: OP.16 FDD
OCNG PatternNote2
10 MHz: OP.2 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA dB 0
PHICH_RB
PDCCH_RA
PDCCH_RB
OCNG_RANote3
OCNG_RBNote3
Noc dBm/15 kHz -98
Ês Noc dB 3
RSRP Note4 dBm/15 kHz -95
SCH_RP Note 4 dBm/15 kHz -95
Propagation condition AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 4: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
Note 5: This test is according to the principle defined in section A.3.12.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1159 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.5.4.2 Test Requirements
For parameters specified in Tables A.7.5.4.1-1, the timing accuracy for ProSe Direct Communication transmissions
shall be within the limits defined in clause 7.16.2. The timing accuracy is verified using SLSS transmissions.
The following sequence of events shall be used to verify that the requirements are met.
For 5MHz or 10MHz channel bandwith, the test sequence shall be carried out in RRC_CONNECTED DRX with a
cycle length of 320ms:
a) After a connection is set up with the cell, the test system shall verify that the ProSe UE SLSS transmission
timing offset is within ± 12×TS with respect to the first detected path (in time) of the corresponding downlink
frame of cell 1.
b) The test system adjusts the downlink transmit timing for the cell by +32×TS (approximately +1µs) compared to
that in (a). The test system shall wait for at least one SLSS period (40ms) before verifying the requirement again
in (c).
c) The test system shall verify that the UE SLSS transmissiontiming offset stays within ± 12×TS with respect to the
first detected path (in time) of the corresponding downlink frame of cell 1.
A.7.5.5 E-UTRAN FDD - Interruptions due to ProSe Direct Communication
A.7.5.5.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to PCell interruptions due to ProSe Direct Communication
defined in clause 7.16.3. In the test the UE under test is configured for ProSe operation only on PCell and also the UE is
configured only for PCell for WAN.
For this test, the UE is triggered by the test loop function or the upper layers to monitor ProSe Direct Communication.
The test parameters are given in Table A.7.5.5.1-1, Table A.7.5.5.1-2 and Table A.7.5.5.1-3 below. There is one active
cell (PCell) in this test and 12 (5MHz) or 16 (10 MHz) active Sidelink UEs in this test transmitting ProSe Direct
Communication.
The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively.
During T1, the UE is in RRC_IDLE and monitoring the ProSe Direct Communication transmission from other active
Sidelink UEs on the ProSe Direct Communication resoruces.
During T2, the test system establishes a RRC connection with the UE. No PDSCH traffic is scheduled for UE during
T2, and the UE is expected to transmit SidelinkUEInformation indicating commRxInterestedFreq during T2. On
reception of SidelinkUEInformation, the test system shall RRC reconfiguration message to the UE and wait for the UE
to repond with RRC reconfiguration complete message before transitioning to T3. If the UE does not transmit
SidelinkUEInformation for up to [2] sec, the test system shall transition to T3.
During T3, the UE is scheduled with PDSCH traffic on PCell downlink. The test system will count the missed
ACK/NACKs during T3 to verify the allowed interruptions during ProSe Direct Communication (no missed
ACK/NACKs are allowed).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1160 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.5.1-1: Test parameters for interruption due to ProSe Direct Communication tests
Parameter Unit Value Comment
E-UTRA RF Channel Number 1
According to principle
Channel Bandwidth (BW channel) MHz 5 or 10 defined in clause
A.3.12.3
E-UTRA FDD Cell1
Active cell Cell 1 on RF channel
number 1
CP length of Cell 1 Normal
T1 s 5.12
Up to receiving RRC reconfiguration setup
complete from the UE, or up to [2] sec if UE
T2 s
does not transmit SidelinkUEInformation
during this period.
T3 s 10.24
Note 1: This test is according to the principle defined in section A.3.12.3.
Table A.7.5.5.1-2: ProSe Direct Communication specific configuration for interruption due to ProSe
Direct Communication tests
Parameter Unit Value Comment
E-UTRA RF Channel Number 1 UL carrier frequency
According to principle
Channel Bandwidth (BW channel) MHz 5 or 10 defined in clause
A.3.12.3
IE values unless
ProSe Direct Communication As specified in Table A.3.12.5-1
specified otherwise in
configuration (Configuration #1)
this test.
Transmitting ProSe
PCP.1.FDD Direct
Active Sidelink UEs ConfigurationNote 1
As specified in Table A.3.12.8.1-1 Communication
(PSCCH + PSSCH)
Note 1: This test is according to the principle defined in section A.3.12.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1161 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.5.1-2: Cell specific test parameters for interruption due to ProSe Direct Communication
tests
Cell 1
Parameter Unit
T1 T2 T3
E-UTRA RF Channel Number 1
BW channel Note 4 MHz 5 or 10
UE RRC state IDLE CONNECTED
defaultPagingCycle rf256
Paging configuration N/A
nB T / 32
DRX N/A OFF
R.7 FDD
(5MHz)
or
PDSCH Reference measurement channel R.3 FDD
N/A None
defined in A.3.1.1.1Note1, Note 4 (10MHz)
(Note 5
applies)
PDCCH/PCFICH/PHICH Reference
5 MHz: R.11 FDD
measurement channel defined in A.3.1.2.1Note1,
Note 4 10 MHz: R.6 FDD
OP.20 FDD
(5MHz)
5 MHz: OP.19 FDD
OCNG Pattern Note 4 or
10 MHz: OP.6 FDD
OP.10 FDD
(10MHz)
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
Noc Note2 dBm/15 kHz -98
Ês N oc dB 16
RSRP Note3 dBm/15 kHz -82
SCH_RP Note 3 dBm/15 kHz -82
Propagation Condition AWGN
Note 1: OCNG shall be used such that cell is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
Note 4: This test is according to the principle defined in section A.3.12.3.
Note 5: The PDSCH scheduled subframes for R.7 FDD (5MHz) / R.3 FDD (10MHz) is changed as per the
following bitmap that repeats every 40ms.
PDSCH scheduled subframe bitmap: {01110111 11110111 11110111 11110111 11110110}.
A.7.5.5.2 Test Requirements
The UE shall be scheduled on PCell continuously during T3. During T3, 100% of all expected ACK/NACKs shall be
transmitted by the ProSe UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1162 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.5.6 E-UTRAN FDD - Interruptions due to ProSe Direct Discovery with
discovery period less than 320ms
A.7.5.6.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to the allowed PCell interruptions due to ProSe Direct
Discovery defined in clause 7.16.3.3 when the discovery period less than 320ms. In the test the UE under test is
configured only with PCell with the ProSe operation on uplink carrier of the PCell.
This test is applicable to ProSe Direct Discovery capable UEs that support discovery periods of less than 320ms.
For this test, the UE is triggered by the test loop function or the upper layers to monitor ProSe Direct Discovery.
The test parameters are given in Table A.7.5.6.1-1, Table A.7.5.6.1-2, and Table A.7.5.6.1-3 below. There is one active
cell (PCell) in this test and 24 active Sidelink transmissions in this test (with 12 active Sidelink UEs per configured
discovery subframe).
The tests consist of three successive time periods, with time duration of T1, T2 and T3 respectively.
During T1, the UE is in RRC_IDLE and monitoring the ProSe Direct Discovery announcements from other active
Sidelink UEs on the ProSe Direct Discovery resources.
During T2, the test system establishes a RRC connection with the UE. No PDSCH traffic is scheduled for UE during
T2, and the UE is expected to transmit SidelinkUEInformation indicating discRxInterest during T2. On reception of
SidelinkUEInformation, the test system shall RRC reconfiguration message to the UE and wait for the UE to respond
with RRC reconfiguration complete message before transitioning to T3. If the UE does not transmit
SidelinkUEInformation for up to [2] sec, the test system shall transition to T3.
During T3, the UE is scheduled with PDSCH traffic on PCell downlink. The test system will count the missed
ACK/NACKs during T3 to verify the allowed interruptions during ProSe Direct Discovery.
Table A.7.5.6.1-1: Test parameters for interruption due to ProSe Direct Discovery test with discovery
period less than 320ms for E-UTRAN FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1
Channel Bandwidth (BW channel) MHz 5
E-UTRA FDD Cell1
Active cell Cell 1 on RF channel
number 1
CP length of Cell 1 Normal
T1 s 0.64
Up to receiving RRC reconfiguration setup
complete from the UE, or up to [2] sec if UE
T2 s
does not transmit SidelinkUEInformation
during this period.
T3 s 1.28
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1163 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.6.1-2: ProSe Direct Discovery configuration for interruption test due to ProSe Direct
Discovery with discovery period less than 320ms for E-UTRAN FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1 UL carrier frequency
Channel Bandwidth
MHz 5
(BW channel)
ProSe Direct Discovery As specified in Table A.3.12.4-4 IE values unless
resource pool configuration (Configuration #4) specified otherwise
in this test.
Active Sidelink UEs PDP.1.FDD Transmitting ProSe
Configuration As specified in Table A.3.12.8.2-1 Direct Discovery
Table A.7.5.6.1-3: Cell specific test parameters for interruption due to ProSe Direct Discovery test
with discovery period less than 320ms for E-UTRAN FDD
Cell 1
Parameter Unit
T1 T2 T3
E-UTRA RF Channel Number 1
BW channel MHz 5
UE RRC state IDLE CONNECTED
defaultPagingCycle rf256
Paging configuration N/A
nB T / 32
DRX N/A OFF
PDSCH Reference measurement channel
N/A None R.5 FDD
defined in A.3.1.1.1Note1
PDCCH/PCFICH/PHICH Reference
R.11 FDD
measurement channel defined in A.3.1.2.1Note1
OCNG Pattern OP.16 FDD OP.15 FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
Noc Note2 dBm/15 kHz -98
Ês N oc dB 16
RSRP Note3 dBm/15 kHz -82
SCH_RP Note 3 dBm/15 kHz -82
Propagation Condition AWGN
Note 1: OCNG shall be used such that cell is fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.7.5.6.2 Test Requirements
The UE shall be scheduled on PCell continuously during T3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1164 ETSI TS 136 133 V14.3.0 (2017-04)
The test system shall verify that at least 98.75% of all expected ACK/NACKs during T3 shall be transmitted by the
ProSe UE. The missed ACK/NACKs can occur only on subframe ‘n’, if either n±1 subframe is a discovery subframe, or
if n-3, or n-5 is a discovery subframe.
NOTE: For the test configuration in Table A.7.5.6.1-1 and Table A.7.5.6.1-2, the specific subframes where
missed ACK/NACKs are allowed are when (subframe mod 40) = 19, 23, 22, 26, corresponding to
allowed interruptions on subframe (subframe mod 40) = 19 and 22.
A.7.5.7 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct Discovery
A.7.5.7.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to the allowed PCell interruptions due to ProSe Direct
Discovery defined in clause 7.16.3.1 and clause 7.16.3.3. In the test the UE under test is configured with PCell and one
SCell, with ProSe operation configured on the PCell.
A UE that meets the requirements of this clause is not required to be tested for the requirements of clause 7.5.3.
For this test, the UE is triggered by the test loop function or the upper layers to monitor ProSe Direct Discovery.
The test parameters are given in Table A.7.5.7.1-1, Table A.7.5.7.1-2, and Table A.7.5.7.1-3 below. There are two
configured component carriers: PCC and SCC, and two active cells: Cell 1 and Cell2. Cell1 is the PCell on PCC, and
Cell 2 is the SCell on SCC. Sidelink operation is configured on the PCC UL. There are 24 active Sidelink transmissions
in this test (with 12 active Sidelink UEs per configured discovery subframe). Two tests (Test 1 and Test 2) are defined
to verify interruptions due to synchronous (Test 1) and asynchronous (Test 2) ProSe Direct Discovery.
The tests consist of three successive time periods, with time duration of T1, T2 and T3 respectively.
During T1, the UE is in RRC_IDLE and monitoring the ProSe Direct Discovery announcements from other active
Sidelink UEs on the ProSe Direct Discovery resources.
During T2, the test system establishes a RRC connection with the UE. The test system shall configure the UE with the
SCC. No PDSCH traffic is scheduled for UE during T2, and the UE is expected to transmit SidelinkUEInformation
indicating discRxInterest during T2. On reception of SidelinkUEInformation, the test system shall RRC reconfiguration
message to the UE and wait for the UE to respond with RRC reconfiguration complete message before transitioning to
T3. If the UE does not transmit SidelinkUEInformation for up to [2] sec, the test system shall transition to T3.
During T3, the UE is scheduled with PDSCH traffic on both PCell and SCell downlink. The test system will count the
missed ACK/NACKs during T3 to verify the allowed interruptions during ProSe Direct Discovery.
Table A.7.5.7.1-1: Test parameters for interruption due to ProSe Direct Discovery tests
Value
Parameter Unit Comment
Test 1 Test 2
E-UTRA RF Channel Number 1
Channel Bandwidth (BW channel) MHz 5
E-UTRA FDD Cell1
and Cell 2 on RF
Active cell Cell 1, Cell 2
channel number 1
and 2, respectively
CP length of Cell 1, Cell 2 Normal
T1 s 5.12
Up to receiving RRC reconfiguration setup
complete from the UE, or up to [2] sec if UE
T2 s
does not transmit SidelinkUEInformation
during this period.
T3 s 10.24
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1165 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.7.1-2: ProSe Direct Discovery configuration for interruption due to ProSe Direct
Discovery tests
Value
Parameter Unit Comment
Test 1 Test 2
E-UTRA RF Channel Number 1 UL carrier frequency
Channel Bandwidth
MHz 5
(BW channel)
ProSe Direct Discovery As specified in Table As specified in Table IE values unless
resource pool configuration A.3.12.4-1 A.3.12.4-2 specified otherwise
(Configuration #1) (Configuration #2) in this test.
Transmitting ProSe
PDP.1.FDD PDP.2.FDD
Active Sidelink UEs Direct Discovery
As specified in Table As specified in Table
Configuration (Test 1 and 2) and
A.3.12.8.2-1 A.3.12.8.2-1
SLSS (for Test 2)
Table A.7.5.7.1-3: Cell specific test parameters for interruption due to ProSe Direct Discovery tests
Cell 1 Cell 2
Parameter Unit
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel Number 1 2
BW channel MHz 5 5
UE RRC state IDLE CONNECTED N/A
defaultPaging
rf256
Paging configuration Cycle N/A N/A
nB T / 32
DRX N/A OFF N/A OFF
PDSCH Reference measurement R.5 R.5
N/A None N/A None
channel defined in A.3.1.1.1Note1 FDD FDD
PDCCH/PCFICH/PHICH Reference
measurement channel defined in R.11 FDD R.11 FDD
A.3.1.2.1Note1
OP.15 OP.15
OCNG Pattern OP.16 FDD OP.16 FDD
FDD FDD
PBCH_RA
PBCH_RB
PSS_RA
SSS_RA
PCFICH_RB
PHICH_RA
PHICH_RB dB 0 0
PDCCH_RA
PDCCH_RB
PDSCH_RA
PDSCH_RB
OCNG_RANote 1
OCNG_RBNote 1
dBm/15
Noc Note2 kHz
-98 -98
Ês N oc dB 16 16
dBm/15
RSRP Note3 -82 -82
kHz
dBm/15
SCH_RP Note 3 -82 -82
kHz
Propagation Condition AWGN AWGN
Note 1: OCNG shall be used such that cell is fully allocated and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for Noc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1166 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.5.7.2 Test Requirements
The UE shall be scheduled on PCell and SCell downlink continuously during T3.
In Test 1, at least 98.75% of all expected ACK/NACKs during T3 shall be transmitted by the ProSe UE. The missed
ACK/NACKs can occur only on subframe ‘n’, if either n±1 subframe is a discovery subframe, or if n-3, or n-5 is a
discovery subframe.
NOTE: For the test configuration in Table A.7.5.12.1-1 and Table A.7.5.12.1-2, the specific subframes where
missed ACK/NACKs are allowed are when (subframe mod 320) = 159, 163, 162, 166, corresponding to
allowed interruptions on subframe 159 and 162.
In Test 2, at least 97.5% of all expected ACK/NACKs during T3 shall be transmitted by the ProSe UE. The missed
ACK/NACK can occur only on subframe ‘n’, if either n±5 subframe is a discovery or SLSS subframe, or if n+1, or n-9
is a discovery or SLSS subframe.
NOTE: For the test configuration in Table A.7.5.7.1-1 and Table A.7.5.7.1-2, the specific subframes where
missed ACK/NACKs are allowed are when (subframe mod 320) = 135, 139, 145, 149, 155, 159, 166,
170, corresponding to allowed interruptions on subframes 135, 145, 155 and 166.
A.7.5.8 E-UTRAN FDD-FDD - Cell reselection and timing accuracy for
ProSe Direct Discovery transmission on non-serving frequency
A.7.5.8.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to cell reselection and timing accuracy for ProSe Direct
Discovery transmissions on a non-serving frequency defined in clauses 7.16.4 and 7.16.2.1.2, respectively. In the test
the UE under test is configured with PCell on a serving frequency, and the PCell provides the ProSe Direct Discovery
resources for a non-serving frequency.
This test is applicable for ProSe Direct Discovery capable UEs that support concurrent inter-band E-UTRAN and E-
UTRAN ProSe operation, and indicates the support of inter-frequency discovery transmission using discInterFreqTx.
For this test, the UE is triggered by the test loop function or the upper layers to announce ProSe Direct Discovery.
The test parameters are given in Table A.7.5.8.1-1, Table A.7.5.8.1-2, and Table A.7.5.8.1-3 below. The test consists of
one active serving cell (cell 1) on the serving RF channel 1, and two active non-serving cells (cell 2 and cell3) on the
non-serving discovery RF channel 2.
The tests consist of three successive time periods, with time duration of T1, T2 and T3 respectively.
The serving cell (cell 1 on RF channel 1) is active during the entire test duration (T1, T2, T3) without any changes to
cell 1 RSRP. Prior to start of the test, the test system shall verify that the UE is transmitting ProSe Direct Discovery
transmissions on the non-serving RF channel 2.
During T1, only one non-serving cell (cell 2 on RF channel 2) is active. The UE is expected to be following the timing
of cell 2 for its discovery transmissions on RF channel 2. During T2, cell 3 on the non-serving RF channel 2 is also
turned ON and is configured to be better ranked than cell 2. The UE is expected to reselect to cell 3 for discovery
transmit timing. During T3, RSRP of cell 2 is increased so that it becomes better ranked than cell 3. The UE is supposed
to reselect back to cell 2 and follow its timing for discovery transmissions.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1167 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.8.1-1: Test parameters for cell reselection and timing accuracy for ProSe Direct Discovery
transmission on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
RF channel 1 is
serving
E-UTRA RF Channel Number 1, 2
RF channel 2 is non-
serving
Channel Bandwidth (BW channel) MHz 5
Serving E-UTRA
Active cell Cell 1 FDD cell on RF
channel number 1
Non-serving E-UTRA
Non-serving cell Cell 2, Cell 3 FDD cells on RF
channel number 2
CP length of Cell 1, 2, 3 Normal
T1 s 2
T2 s 14
T3 s 5
Table A.7.5.8.1-2: ProSe Direct Discovery configuration for cell reselection and timing accuracy for
ProSe Direct Discovery transmission on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 2 UL carrier frequency
Channel Bandwidth (BW channel) MHz 5
IE values unless
specified otherwise
in this test.
ProSe Direct Discovery resource pool As specified in Table A.3.12.4-5
configuration (Configuration #5)
Broadcasted in
SIB19 by Cell 1 on
RF channel 1
discInterFreqList/ carrierFreq RF channel 2 (UL frequency)
freqInfo/ul-CarrierFreq RF channel 2 (UL frequency)
rxParamsAddNeighFreq/physCellId {phyCellId of Cell 2, phyCellId of Cell 3}
txParamsAddNeighFreq/physCellId {phyCellId of Cell 2, phyCellId of Cell 3}
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1168 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.8.1-3: Cell specific test parameters for cell reselection and timing accuracy for ProSe
Direct Discovery transmission on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Cell 1 Cell 2 Cell 3
T1 T2 T3 T1 T2 T3 T1 T2 T3
E-UTRA RF
Channel Number 1 2 2
Serving / Non-
Serving Non-serving Non-serving
serving
BW channel MHz 5 5 5
DRX_P1
drx-Configuration As specified in Table N/A N/A
A.3.12.2-1
OCNG Patterns
OP.16 FDD OP.19 FDD OP.19 FDD
defined in A.3.2.1.2
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
0 0 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
dB
OCNG_RBNote 1
Timing offset us 0 0 2
dBm/15
Noc Note 2
kHz
-98
dBm/15
RSRP Note 3 -82 -82 -85 -82 -infinity -82 -85
kHz
Ê s I ot dB 16 16 -3.11 2.79 -infinity 2.79 -3.11
Ê s N oc dB 16 16 13 16 -infinity 13 16
dBm/15
SCH_RP Note 3 -82 -82 -85 -82 -infinity -82 -85
kHz
Propagation
AWGN AWGN AWGN
Condition
Note 1: OCNG shall be used such that cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for Noc to be fulfilled.
Note 3: RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
A.7.5.8.2 Test Requirements
During T1, the test system shall verify that the transmit timing offset of discovery transmission on RF channel 2 is
within ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 2.
During T2, the UE is expected to reselect to cell 3 for discovery timing synchronization after cell reselection delay to a
newly detectable cell from start of T2. After the period of cell reselection delay to a newly detectable cell from the start
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1169 ETSI TS 136 133 V14.3.0 (2017-04)
of T2, the test system shall verify that the transmit timing offset of discovery transmission on RF channel 2 are within ±
12×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 3.
The cell reselection delay to a newly detectable cell for discovery transmission on non-serving carrier shall be 10.56s.
NOTE: The cell reselection delay to a newly detectable cell for discovery transmission on non-serving carrier can
be expressed as (Tdetect,EUTRAN_ProSe_Intra + 1 discovery period).
During T3, the UE is expected to reselect back to cell 2 for discovery timing synchronization after cell reselection delay
to an already detected cell from start of T3. After the period of cell reselection delay to a newly detectable cell from the
start of T3, the test system shall verify that the transmit timing offset of discovery transmission on RF channel 2 are
within ± 12×TS with respect to the first detected path (in time) of the corresponding downlink frame of cell 2.
The cell reselection delay to an already detected cell for discovery transmission on non-serving carrier shall be 5.44s.
NOTE: The cell reselection delay to an already detected cell for discovery transmission on non-serving carrier
can be expressed as (Tevaluate, E-UTRAN_ProSe_Intra + 1 discovery period).
The rate of correct events observed during repeated tests shall be at least 90%.
A.7.5.9 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct Discovery
reception on non-serving frequency
A.7.5.9.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to interruptions due to ProSe Direct Discovery reception on
a non-serving frequency as defined in clause 7.16.3.3 and 7.16.3.4. In the test the UE under test is configured with PCell
on a serving frequency, and the PCell provides the ProSe Direct Discovery resources for a non-serving frequency.
This test is applicable for ProSe Direct Discovery capable UEs that support concurrent inter-band E-UTRAN and E-
UTRAN ProSe operation.
For this test, the UE is triggered by the test loop function or the upper layers to monitor ProSe Direct Discovery.
The test parameters are given in Table A.7.5.9.1-1, Table A.7.5.9.1-2, and Table A.7.5.9.1-3 below. The test consists of
one active serving cell (cell 1) on the serving RF channel 1, and one active non-serving cells (cell 2) on the non-serving
discovery RF channel 2. There are 96 active Sidelink transmissions in this test (with 12 active Sidelink UEs per
configured discovery subframe) on RF channel 2.
After the test system establishes a RRC connection with the UE, the UE is expected to transmit SidelinkUEInformation
indicating discRxInterest. On reception of SidelinkUEInformation, the test system shall RRC reconfiguration message to
the UE and wait for the UE to respond with RRC reconfiguration complete message before start of the test. Further,
depending on UE implementation, the UE may request for discovery reception gaps (using discRxGapReq) for the
ProSe Direct Discovery reception operation on the non-serving frequency. If gaps are requested, the test system shall
configure the gaps as requested and modify the PDSCH scheduling on cell 1 for this UE such that the UE is not
scheduled on the DL on the subframes configured as reception gaps.
The test shall start after the completion of the RRC reconfiguration is complete following the SidelinkUEInformation
message transmission from the UE. The test system shall then continuously schedule the UE on DL of cell 1 (apart from
any subframes that are configured as discovery gaps).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1170 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.9.1-1: Test parameters for interruptions due to ProSe Direct Discovery reception on non-
serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
RF channel 1 is
serving
E-UTRA RF Channel Number 1, 2
RF channel 2 is non-
serving
Channel Bandwidth (BW channel) MHz 5
Serving E-UTRA
Active cell Cell 1 FDD cell on RF
channel number 1
Non-serving E-UTRA
Non-serving cell Cell 2 FDD cell on RF
channel number 2
CP length of Cell 1, 2 Normal
Table A.7.5.9.1-2: ProSe Direct Discovery configuration for interruptions due to ProSe Direct
Discovery reception on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 2 UL carrier frequency
Channel Bandwidth (BW channel) MHz 5
IE values unless
specified otherwise
in this test.
ProSe Direct Discovery resource pool As specified in Table A.3.12.4-5
configuration (Configuration #5)
Broadcasted in
SIB19 by Cell 1 on
RF channel 1
discInterFreqList/carrierFreq RF channel 2 (UL frequency)
freqInfo/ul-CarrierFreq RF channel 2 (UL frequency)
rxParamsAddNeighFreq/physCellId {phyCellId of Cell 2}
txParamsAddNeighFreq/physCellId {phyCellId of Cell 2}
11111111
discResourcesNonPS/
00000000
discRxResourcesInterFreq/
00000000
tf-ResourceConfig/
00000000
subframeBitmap
00000000
Transmitting ProSe
PDP.1.FDD
Active Sidelink UEs Configuration Direct Discovery on
As specified in Table A.3.12.8.2-1
RF channel 2
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1171 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.9.1-3: Cell specific test parameters for interruptions due to ProSe Direct Discovery
reception on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Cell 1 Cell 2
E-UTRA RF Channel
1 2
Number
Serving/Non-serving Serving Non-serving
BW channel MHz 5 5
Correlation Matrix
and Antenna 1x2 Low 1x2 Low
Configuration
drx-Configuration None N/A
PDCCH/PCFICH/PHI
CH Reference
R.11 FDD R.11 FDD
measurement
channelNote1
PDSCH Reference
measurement R.7 FDD
N/A
channel defined in (NOTE 5 applies)
A.3.1.1.1Note1
OCNG Pattern
OP.20 FDD OP.19 FDD
defined in A.3.2.1
PCFICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB 0 0
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
dB
Ês Noc 16 16
Noc dBm/15
-98 -98
kHz
dBm/15
RSRP Note4 -82 -82
kHz
dBm/15
SCH_RP Note 4 -82 -82
kHz
Propagation condition AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 5: Scheduling pattern for PDSCH modified to omit the subframes configured as Discovery
Gaps in the test.
A.7.5.9.2 Test Requirements
The test system shall verity the allowed interruptions for ProSe Direct Discovery reception on non-serving frequency,
and depends on the discovery gap configuration for the UE.
If no discovery gaps are configured, the test system shall verify that the total number of missed ACK/NACKs on the
serving cell are less than 0.5%.
If discovery gaps are configured as requested by the UE, then test system shall verify that the missed ACK/NACKs, if
any, correspond to locations as specified in subclause 7.16.3.4:
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1172 ETSI TS 136 133 V14.3.0 (2017-04)
- Missed ACK/NACKs is allowed on a subframe n, if subframe n is configured as downlink reception gap (using
discRxGapConfig) and either the subframe immediately preceding or immediately following that subframe is not
configured as reception gap, and
- One additional missed ACK/NACK per discovery period is allowed on a subframe m, such that the subframe m
is configured as reception gap.
A.7.5.10 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct Discovery
transmission on non-serving frequency
A.7.5.10.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to interruptions due to ProSe Direct Discovery reception on
a non-serving frequency as defined in clause 7.16.3.3 and 7.16.3.4. In the test the UE under test is configured with PCell
on a serving frequency, and the PCell provides the ProSe Direct Discovery resources for a non-serving frequency.
This test is applicable for ProSe Direct Discovery capable UEs that support concurrent inter-band E-UTRAN and E-
UTRAN ProSe operation, and indicates the support of inter-frequency discovery transmission using discInterFreqTx.
For this test, the UE is triggered by the test loop function or the upper layers to announce ProSe Direct Discovery.
The test parameters are given in Table A.7.5.10.1-1, Table A.7.5.10.1-2, and Table A.7.5.10.1-3 below. The test
consists of one active serving cell (cell 1) on the serving RF channel 1, and one active non-serving cells (cell 2) on the
non-serving discovery RF channel 2.
After the test system establishes a RRC connection with the UE, the UE is expected to transmit SidelinkUEInformation.
On reception of SidelinkUEInformation, the test system shall RRC reconfiguration message to the UE and wait for the
UE to respond with RRC reconfiguration complete message before start of the test. Further, depending on UE
implementation, the UE may request for discovery transmission and/or reception gaps (using discTxGapReq and/or
discRxGapReq) for the ProSe Direct Discovery transmission operation on the non-serving frequency. If transmission
gap is requested, the test system shall configure the transmission gap as requested. The test system shall not configure
any reception gap for the UE for the purpose of this test.
The test shall start after the completion of the RRC reconfiguration is complete following the SidelinkUEInformation
message transmission from the UE. The test system shall then continuously schedule the UE on DL of cell 1.
Table A.7.5.10.1-1: Test parameters for interruptions due to ProSe Direct Discovery transmission on
non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
RF channel 1 is
serving
E-UTRA RF Channel Number 1, 2
RF channel 2 is non-
serving
Channel Bandwidth (BW channel) MHz 5
Serving E-UTRA
Active cell Cell 1 FDD cell on RF
channel number 1
Non-serving E-UTRA
Non-serving cell Cell 2 FDD cell on RF
channel number 2
CP length of Cell 1, 2 Normal
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1173 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.10.1-2: ProSe Direct Discovery configuration for interruptions due to ProSe Direct
Discovery transmission on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 2 UL carrier frequency
Channel Bandwidth (BW channel) MHz 5
IE values unless
specified otherwise
in this test.
ProSe Direct Discovery resource pool As specified in Table A.3.12.4-5
configuration (Configuration #5)
Broadcasted in
SIB19 by Cell 1 on
RF channel 1
discInterFreqList/carrierFreq RF channel 2 (UL frequency)
freqInfo/ul-CarrierFreq RF channel 2 (UL frequency)
txParamsAddNeighFreq/physCellId {phyCellId of Cell 2}
Configure UE to use
pCell as reference
for synchronization
discConfigOther/
pCell and measurements
refCarrierCommon
for discovery
transmission on
non-serving carrier
discResourcesNonPS/
Not configured
discRxResourcesInterFreq
11111111
discResourcesNonPS/
00000000
discTxResourcesInterFreq/
00000000
tf-ResourceConfig/
00000000
subframeBitmap
00000000
Within SL-
DiscConfig in RRC
discRxGapConfig Not configured
reconfiguration
message
Within SL-
DiscConfig in RRC
Configured as requested by UE in
discTxGapConfig connection
discTxGapReq
reconfiguration
message
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1174 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.10.1-3: Cell specific test parameters for interruptions due to ProSe Direct Discovery
transmission on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Cell 1 Cell 2
E-UTRA RF Channel
1 2
Number
Serving/Non-serving Serving Non-serving
BW channel MHz 5 5
Correlation Matrix
and Antenna 1x2 Low 1x2 Low
Configuration
drx-Configuration None N/A
PDCCH/PCFICH/PHI
CH Reference
R.11 FDD R.11 FDD
measurement
channelNote1
PDSCH Reference
measurement
R.7 FDD N/A
channel defined in
A.3.1.1.1Note1
OCNG Pattern
OP.20 FDD OP.19 FDD
defined in A.3.2.1
PCFICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB 0 0
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
dB
Ês Noc 16 16
Noc dBm/15
-98 -98
kHz
dBm/15
RSRP Note4 -82 -82
kHz
dBm/15
SCH_RP Note 4 -82 -82
kHz
Propagation condition AWGN AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
A.7.5.10.2 Test Requirements
The test system shall verity the allowed interruptions for ProSe Direct Discovery trannsmission on non-serving
frequency.
If no discovery transmission gaps are configured, the test system shall verify that the total number of missed
ACK/NACKs on the serving cell are less than 0.5%.
If discovery transmission gaps are configured as requested by the UE, the test system shall verify that the number of
missed ACK/NACKs are less than or equal to 5 missed ACK/NACKs during a discovery period (configured as 320ms
in this test). Corresponding to discovery transmission on s subframe n (with respect to PCell) on the non-serving carrier,
the missed ACK/NACKs are allowed only on subframes (n-1), n, (n+1), (n+3), (n+5).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1175 ETSI TS 136 133 V14.3.0 (2017-04)
A.7.5.11 E-UTRAN FDD-FDD - Interruptions due to ProSe Direct
Communication on non-serving frequency
A.7.5.11.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to interruptions due to ProSe Direct Communication on a
non-serving frequency as defined in clause 7.16.3.5. In the test the UE under test is configured with PCell on a serving
frequency, and is pre-configured with ProSe Direct Communication resources for a non-serving frequency.
This test is applicable for ProSe Direct Communication capable UEs that support concurrent inter-band E-UTRAN and
E-UTRAN ProSe operation.
For this test, the UE is triggered by the test loop function or the upper layers to receive ProSe Direct Communication.
The test parameters are given in Table A.7.5.11.1-1, Table A.7.5.11.1-2, Table A.7.5.11.1-3 and Table A.7.5.11.1-4
below. The test consists of one active serving cell (cell 1) on the serving RF channel 1, and there are no active cells on
RF channel 2. On RF channel 2, the test consists of one active SyncRef UE (SyncRef UE 1) transmitting
synchronization signals and channels, and 12 (5MHz) or 16 (10 MHz) active Sidelink UEs in this test transmitting
ProSe Direct Communication.
The serving cell (cell 1) on RF channel 1 is not broadcasting SIB18, and the UE is expected to use its preconfigured
parameters for ProSe Direct Communication operation on RF channel 2.
The UE is continuously scheduled with PDSCH traffic on PCell downlink in RF channel 1.
Table A.7.5.11.1-1: Test parameters for interruptions due to ProSe Direct Communication on non-
serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
RF channel 1 is serving
E-UTRA RF Channel Number 1, 2
RF channel 2 is non-serving
According to principle defined
Channel Bandwidth (BW channel) MHz 5 or 10
in clause A.3.12.3
Serving E-UTRA FDD cell on
Active cell Cell 1 RF channel number 1
(Not broadcasting SIB18)
Transmitting SLSS+MIB-SL on
Active SyncRef UEs SyncRef UE 1
uplink of RF channel number 2
CP length of Cell 1 Normal
Table A.7.5.11.1-2: ProSe Direct Communication configuration for interruptions due to ProSe Direct
Communication on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 2 UL carrier frequency
According to principle
Channel Bandwidth (BW channel) MHz 5 or 10
defined in clause A.3.12.3
IE values unless specified
ProSe Direct Communication resource As specified in Table A.3.12.5-2
otherwise in this test.
pool configuration (Configuration #2)
(Preconfigured)
Transmitting ProSe Direct
Communication
PCP.1.FDD (PSCCH + PSSCH)
Active Sidelink UEs ConfigurationNote 1
As specified in Table A.3.12.8.1-1
Using SyncRef UE1 as
synchronization source
Note 1: This test is according to the principle defined in section A.3.12.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1176 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.11.1-3: SyncRef UE specific test parameters for interruptions due to ProSe Direct
Communication on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit SyncRef UE 1
E-UTRA RF Channel Number 2
BW channelNote 4 MHz 5 or 10
As specified in Table A.3.12.5-1
ProSe Direct Communication resource pool (Configuration #1)
configuration Note resource pool is same as Configuration
#2 used by ProSe UE.
Set same as syncOffsetIndicator1 in ProSe
syncOffsetIndicator
Direct Communication preconfiguration
slssid 30
inCoverage TRUE
networkControlledSyncTx ON
Noc Note1 dBm/15 kHz -98
Ês Noc dB 16
S-RSRP Note2, Note3 dBm/15 kHz -82
Propagation Condition AWGN
Note 1: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled.
Note 2: S-RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
Note 3: SSSS Es/Iot is set the same as PSSS/PSBCH Es/Iot.
Note 4: This test is according to the principle defined in section A.3.12.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1177 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.11.1-4: Cell specific test parameters for interruptions due to ProSe Direct Communication
on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Cell1
E-UTRA RF Channel Number 1
E-UTRA RF Channel Number 1
Serving/Non-serving Serving
BW channel Note 5 MHz 5 or 10
Correlation Matrix and Antenna
1x2 Low
Configuration
drx-Configuration None
PDCCH/PCFICH/PHICH Reference 5 MHz: R.11 FDD
measurement channelNote1, Note 5 10 MHz: R.6 FDD
PDSCH Reference measurement channel 5MHz: R.7 FDD
defined in A.3.1.1.1Note1, Note 5 10MHz: R.3 FDD
OCNG Pattern defined in A.3.2.1 5 MHz: OP.20 FDD
10 MHz: OP.10 FDD
PCFICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB 0
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
dB
Ês Noc 16
Noc dBm/15 kHz -98
RSRP Note4 dBm/15 kHz -82
SCH_RP Note 4 dBm/15 kHz -82
Propagation condition AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that cell is fully allocated and a constant total
transmitted power spectral density is achieved for all OFDM symbols.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for
information purposes. They are not settable parameters themselves.
Note 5: This test is according to the principle defined in section A.3.12.3.
A.7.5.11.2 Test Requirements
The test system shall verify that the total number of missed ACK/NACKs on the serving cell on RF channel 1 are less
than 0.5%.
A.7.5.12 E-UTRAN FDD - Selection / Reselection of ProSe relay UE
A.7.5.12.1 Test Purpose and Environment
The purpose of this test is to verify the requirements related to selection / reselection of ProSe relay UE defined in
clauses 7.16.5. In the test the UE under test is configured with PCell and is configured with ProSe Direct Discovery and
ProSe Direct Communication resources as required for remote UE operation.
This test is applicable to UEs capable of ProSe Direct Discovery and ProSe Direct Communication, and further support
the optional feature of sidelink remote UE operation.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1178 ETSI TS 136 133 V14.3.0 (2017-04)
The test parameters are given in Table A.7.5.12.1-1, Table A.7.5.12.1-2, Table A.7.5.12.1-3, Table A.7.5.12.1-4, and
Table A.7.5.12.1-5 below. The test consists of one active serving cell (cell 1), and two active Sidelink relay UEs
(Sidelink Relay UE 1, Sidelink Relay UE 2). The Sidelink relay UEs are configured to be transmitting relay discovery
messages every discovery period.
The test system shall ensure that the remote UE under test has transmitted SidelinkUEInformation message and has been
configured with the ProSe Direct Discovery resources for relay operation prior to the start of the test.
The tests consist of five successive time periods, with time duration of T1, T2, T3, and T4 respectively.
During T1, RSRP of cell 1 is kept higher than threshHigh (within remoteUE-Config), and the remote UE is not required
to perform relay UE selection.
During T2, RSRP of cell 1 is configured to be lower than threshHigh. The UE is expected to start looking for relay UE
and request the serving cell for ProSe Direct Communication resources for communicating with a candidate Sidelink
Relay UE. The test system shall ensure that the UE under test transmits the SidelinkUEInformation message (requesting
the ProSe Direct Communication resources) and has been configured the resource pool prior to end of T2 duration.
During T2, the SD-RSRP of Sidelink Relay UE 1 and Sidelink Relay UE 2 is configured to be lower than the detection
threshold and no relay UE will be available for the remote UE under test.
During T3, the SD-RSRP of Sidelink Relay UE 1 is raised above the detection threshold and the UE is expected to
perform relay selection to Sidelink Relay 1. The test system can determine that the remote UE has selected a relay by
monitoring the configured ProSe Direct Communication resource for the direct communication setup message to the
relay UE.
During T4, the UE is expected to complete the direct communication setup with the relay UE. Note that the RSRP of
the serving cell (cell 1) and the SD-RSRP of sidelink relay UEs is kept unchanged during T3. The period T3 ends when
Sidelink Relay UE1 sends the direct communication accept message back to the remote UE.
During T5, SD-RSRP of Sidelink Relay UEs are modified such that the remote UE is expected to reselect to Sidelink
Relay UE2.
Table A.7.5.12.1-1: Test parameters for selection / reselection of ProSe relay UE test for E-UTRAN
FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1
Channel Bandwidth (BW channel) MHz 5
Serving E-UTRA FDD cell on
RF channel number 1
Active cell Cell 1
(Broadcasting SIB18 and
SIB19)
Transmitting relay discovery
Active Relay UEs Relay UE 1, Relay UE 2
message
CP length of Cell 1 Normal
T1 ms 100
T2 s Up to receiving RRC
reconfiguration setup complete
from the UE, or up to [1] sec if UE
does not transmit
SidelinkUEInformation during this
period.
T3 s 1
T4 s [2]
T5 s 1
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1179 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.12.1-2: ProSe Direct Discovery configuration for selection / reselection of ProSe relay UE
test for E-UTRAN FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1 UL carrier frequency
Channel Bandwidth (BW channel) MHz 5
ProSe Direct Discovery resource pool As specified in Table A.3.12.4-4 IE values unless specified
configuration (Configuration #4) otherwise in this test.
discRxPoolPS/numRetx 3
discRxPoolPS/ To align with
tf-ResourceConfig/ 0 communications resource
offsetIndicator pool offset
00111100
To avoid collision with
discRxPoolPS/ 00000000
communication resource
tf-ResourceConfig/ 00000000
pool, and allow for 4
subframeBitmap 00000000
retransmissions
00000000
remoteUE-Config/threshHigh -91dBm
Note 1: This test is according to the principle defined in section A.3.12.3.
Table A.7.5.12.1-3: ProSe Direct Communication configuration for selection / reselection of ProSe
relay UE test for E-UTRAN FDD
Parameter Unit Value Comment
E-UTRA RF Channel Number 1 UL carrier frequency
Channel Bandwidth (BW channel) MHz 5
ProSe Direct Communication resource As specified in Table A.3.12.5-1 IE values unless specified
pool configuration (Configuration #1) otherwise in this test.
00000011
commRxPool/ 00000000
sc-TFResourceConfig/ 00000000
subframeBitmap 00000000
00000000 To avoid collision with
00000011 discovery resource pool
commTxPoolNormalCommon/ 00000000
sc-TFResourceConfig/ 00000000
subframeBitmap 00000000
00000000
commTxAllowRelayCommon true Configured in SIB18
Note 1: This test is according to the principle defined in section A.3.12.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1180 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.12.1-4: Sidelink Relay UE specific test parameters for selection / reselection of ProSe
relay UE test for E-UTRAN FDD
Relay UE 1 Relay UE 2
Parameter Unit
T1 T2 T3 T4 T5 T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1 (UL frequency)
BW channel Note 4 MHz 5
ProSe Direct Discovery
As specified in Table A.7.5.12.1-2
resource pool configuration
Transmission frequency Every discovery period (40ms) with 3 retransmissions per period
Resource allocation Non-overlapping PRBs
dBm/15
Noc Note1 kHz
-97
Ês N oc dB -inf -inf 10.5 10.5 -1.5 -inf -inf -inf -inf 10.5
dBm/15
SD-RSRP Note2, Note 3 -inf -inf -86.5 -86.5 -98.5 -inf -inf -inf -inf -86.5
kHz
Propagation Condition AWGN
Note 1: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers
and time and shall be modelled as AWGN of appropriate power for Noc to be fulfilled.
Note 2: SD-RSRP levels have been derived from other parameters for information purposes. They are not settable
parameters themselves.
Note 3: SSSS Es/Iot is set the same as PSSS/PSBCH Es/Iot.
Note 4: This test is according to the principle defined in section A.3.12.3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1181 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.7.5.12.1-5: Cell specific test parameters for interruptions due to ProSe Direct Communication
on non-serving frequency test for E-UTRAN FDD-FDD
Parameter Unit Cell1
T1 T2 T3 T4 T5
E-UTRA RF Channel Number 1
Serving/Non-serving Serving
BW channel Note 5 MHz 5
Correlation Matrix and Antenna
1x2 Low
Configuration
drx-Configuration DRX_P1
As specified in Table A.3.12.2-1
PDCCH/PCFICH/PHICH Reference
R.11 FDD
measurement channelNote1, Note 5
OCNG Pattern defined in A.3.2.1 OP.16 FDD
PCFICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PHICH_RA dB
PHICH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote1 dB
OCNG_RBNote1 dB
Noc dBm/15 kHz -97
10.
Ês Noc dB
5
1.5 1.5 1.5 1.5
- -
RSRP Note4 dBm/15 kHz 86. -95.5 -95.5 -95.5 95.
5 5
Propagation condition AWGN
Note 1: For the reference measurement channels, see clause A.3.1.
Note 2: For the OCNG pattern, see clause A.3.2.
Note 3: OCNG shall be used such that cell is fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 4: RSRP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Note 5: This test is according to the principle defined in section A.3.12.3.
A.7.5.12.2 Test Requirements
Sidelink relay UE selection delay is defined as the time from the beginning of time period T3 to the moment when the
UE selects the Sidelink Relay UE1 and transmits the PC5-SP direct communication setup message using ProSe Direct
Communications.
The test system shall verify that the sidelink relay UE selection delay is less than 680ms.
NOTE: The sidelink relay UE selection delay can be expressed as (Tevaluate, ProSe_Relay_intra + 1 sc-period).
Sidelink relay UE reselection time is defined as the time from the beginning of time period T5 to the moment when the
UE reselects to Sidelink relay UE2 and transmits the direct communication setup message using ProSe Direct
Communications.
The test system shall verify that the sidelink relay UE reselection delay is less than 800ms.
NOTE: The sidelink relay UE reselection delay can be expressed as (Tmeasure,ProSe_Relay_Intra + Tevaluate, ProSe_Relay_intra +
1 sc-period).
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1182 ETSI TS 136 133 V14.3.0 (2017-04)
A.8 UE Measurements Procedures
The reference channels in this clause assume transmission of PDSCH with a maximum number of 5 HARQ
transmissions unless otherwise specified.
A.8.1 E-UTRAN FDD Intra-frequency Measurements
A.8.1.1 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells
A.8.1.1.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the FDD
intra-frequency cell search requirements in clause 8.1.2.2.1.1.
The test parameters are given in Table A.8.1.1.1-1 and A.8.1.1.1-2 below. In the measurement control information it is
indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2.
Table A.8.1.1.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Time offset between cells 3 ms Asynchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1183 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.1.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_PB dB
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 -1.46 -Infinity -1.46
Ê s I ot
N oc Note 3 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ês N oc
RSRP Note 4 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 4 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.1.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 800 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1184 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.2 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells
A.8.1.2.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the FDD
intra-frequency cell search requirements in clause 8.1.2.2.1.1
The test parameters are given in Table A.8.1.2.1-1 and A.8.1.2.1-2 below. In the measurement control information it is
indicated to the UE that event-triggered reporting with Event A3 is used. PDCCHs indicating new transmissions or
retransmissions shall be sent continuously to ensure that the UE would not enter the DRX state. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have
any timing information of cell 2.
Table A.8.1.2.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX DRX_L As specified in clause A.3.3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1185 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.2.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 -1.46 -Infinity -1.46
Ê s I ot
N oc Note 3 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ês N oc
RSRP Note 4 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 4 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.2.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 800 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1186 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.3 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells with DRX
A.8.1.3.1 Test Purpose and Environment
The purpose of the two tests is to verify that the UE makes correct reporting of an event in DRX. The tests will partly
verify the FDD-FDD intra-frequency cell search in DRX requirements in clause 8.1.2.2.1.2.
The test parameters are given in Tables A.8.1.3.1-1, A.8.1.3.1-2, A.8.1.3.1-3 and A.8.1.3.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furhtermore UE is allocated with
PUSCH resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.1.3.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Value Comment
Test 1 Test 2
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are defined in
Table A.8.1.3.1-3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1187 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.3.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 4 -1.46 -Infinity -1.46
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ês N oc
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They
are not settable parameters themselves.
Table A.8.1.3.1-3: DRX-Configuration for E-UTRAN FDD-FDD intra-frequency event triggered
reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1188 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.3.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD-FDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 0 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.3.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
800 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
25600 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request
(SR) to obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE 1: The actual overall delays measured in the test may be up to one DRX cycle higher than the
measurement reporting delays above because UE is allowed to delay the initiation of the measurement
reporting procedure to the next until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has received
correct Event A3 measurement report.
A.8.1.4 Void
A.8.1.5 E-UTRAN FDD - FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps
A.8.1.5.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.1.2.2.3.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.5.1-1 and A.8.1.5.1-2.
PDCCHs indicating new transmissions shall be sent continuously to ensure that the UE would have ACK/NACK
sending during identifying a new CGI of E-UTRAN cell. The test consists of three successive time periods, with time
durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have any timing information
of cell 2. Starting T2, cell 2 becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1189 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.5.1-1: General test parameters for E-UTRAN FDD - FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.3 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 s ≤10
T3 s 5
Table A.8.1.5.1-2: Cell specific test parameters for E-UTRAN FDD - FDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns defined in OP.10 OP.10 OP.10 OP.2 OP.2 OP.2
A.3.2.1.10 (OP.10 FDD) FDD FDD FDD FDD FDD FDD
and in A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_PB dB
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1190 ETSI TS 136 133 V14.3.0 (2017-04)
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ês N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
A.8.1.5.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 170 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI, intra + reporting delay
= 15 + 150 + 2ms from the start of T3
= 167 ms, allow 170 ms.
The UE shall be scheduled continuously throughout the test, and from the start of T3 until 170 ms at least 80
ACK/NACK shall be detected as being transmitted by the UE.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The overall 80 ACK/NACK number is caused by two parts. Firstly, at least 60 ACK/NACK shall be sent
during identifying the cell global identifier of cell 2 according to the requirement in Clause 8.1.2.2.3.1.
Secondly, given that continuous DL data allocation, additional 20 ACK/NACK shall be sent from the
start of T3 until 170 ms excludes 150 ms for identifying the cell global identifier of cell 2.
A.8.1.6 E-UTRAN FDD - FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps with DRX
A.8.1.6.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.1.2.2.3. The requirement is verified in a DRX configuration.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.6.1-1, A.8.1.6.1-2,
A.8.1.6.1-3 and A.8.1.6.1-4. The test consists of three successive time periods, with time durations of T1, T2 and T3
respectively. At the start of time duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2
becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
In the test UE needs to be provided at least once every 1280ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furthermore UE sends scheduling
request (SR) to obtain allocation to send the measurement report on PUSCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1191 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.6.1-1: General test parameters for E-UTRAN FDD - FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps with DRX
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are
defined in Table A.8.1.6.1-3
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
Time offset between cells ms 3 Asynchronous cells
T1 s 5
T2 s ≤30 UE shall report cell within 25.6s
(20 DRX cycles)
T3 s 5
Table A.8.1.6.1-2: Cell specific test parameters for E-UTRAN FDD - FDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps with DRX
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns defined in OP.1 OP.1 OP.1 OP.2 OP.2 OP.2
A.3.2.1.1 (OP.1 FDD) and FDD FDD FDD FDD FDD FDD
in A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_PB dB
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1192 ETSI TS 136 133 V14.3.0 (2017-04)
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ês N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are not
settable parameters themselves.
Table A.8.1.6.1-3: DRX configuration for E-UTRAN FDD - FDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps with DRX
Field Value Comment
onDurationTimer psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
Table A.8.1.6.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD - FDD Intra-frequency
identification of a new CGI of E-UTRA cell using autonomous gaps with DRX
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer Infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.6.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 170 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI, intra + reporting delay
= 15 + 150 + 2ms from the start of T3
= 167 ms, allow 170 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1193 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.7 E-UTRAN FDD-FDD Intra-Frequency Event-Triggered Reporting
under Time Domain Measurement Resource Restriction with Non-
MBSFN ABS
A.8.1.7.1 Test Purpose and Environment
The purpose of this test is to verify that the UE correctly detects and reports Event A3 (Neighbour becomes offset better
than PCell) defined in TS 36.331 [2] within the requirements specified in Clause 8.1.2.8.1.1 under a time domain
measurement resource restriction and non-MBSFN ABS configured in the aggressor cell.
The test parameters are given in Tables A.8.1.7.1-1 and A.8.1.7.1-2 below. It is indicated to the UE in the measurement
control information that event-triggered reporting with Event A3 is used. In the test there are two synchronous cells,
Cell 1 and Cell 2, on the same RF channel. Cell 1 is the PCell, and it is also the aggressor cell to Cell 2. Cell 2 is the cell
to be identified. The test consists of two successive time periods with time duration of T1 and T2, respectively. During
time duration T1, the UE shall not have any timing information on Cell 2.
Non-MBSFN ABS pattern is configured for Cell 1 during the test. The UE is configured by higher layers via Cell 1
with a time domain measurement resource restriction pattern for performing E-UTRAN FDD intra-frequency
measurements on neighbour cells. The UE is also configured with a time domain measurement resource restriction
pattern for the PCell measurements. The information for both measurement patterns shall be provided to the UE via
higher layers during T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1194 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.7.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under time domain measurement resource restriction with non-MBSFN ABS
Parameter Unit Value Comment
PDSCH parameters DL Reference As specified in clause A.3.1.1.1
Measurement Channel
R.0 FDD
PCFICH/PDCCH/PHICH DL Reference As specified in clause A.3.1.2.1
parameters Measurement Channel
R.6 FDD
PCell Cell 1 Also the aggressor cell. Active in T1 and T2
Neighbour cell Cell 2 Cell to be identified. Active only in T2.
PCell ABS configuration Non-MBSFN ABS As defined in Table A.3.4.1.1-1
E-UTRA RF Channel Number 1 One FDD carrier frequency is used
Channel Bandwidth (BW channel) MHz 10 For all cells in the test
A3-Offset dB -11
Event A3 measurement quantity RSRP
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5
Physical cell ID PCI (PCIcell1 - PCIcell2 )mod6 Cell PCIs are selected so that the condition is
!=0 met
ABS pattern FDD ABS Pattern Info IE, as defined in TS
‘10000000100000001000 36.423 [28], clause 9.2.54. Configured in Cell 1
00001000000010000000’ during T1.
The first/leftmost bit corresponds to the
subframe #0 of the radio frame satisfying SFN
mod x = 0, where x is the size of the bit string
(40) divided by 10. No MBSFN subframes are
cofigured in the ABS subframes.
Time domain measurement Time domain measurement resource restriction
resource restriction pattern for ‘10000000100000001000 pattern for neighbor cell measurement signalled
neighbour cell measurements on 00001000000010000000’ to the UE in measSubframePattern-Neigh IE in
RF Channel 1 measSubframePatternConfig-Neigh, as defined
in TS 36.331, clause 6.3.5.
Configured during T1 for Cell 2 measurements.
Time domain measurement ‘01000000010000000100 Configured during T1 for Cell 1 measurements
resource restriction pattern for 00000100000001000000’
PCell measurements
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1195 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.7.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under time domain measurement resource restriction with non-MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.5 OP.5 FDD OP.6 FDD
(OP.5 FDD) and in
A.3.2.1.6 (OP.6 FDD)
PBCH_RA dB Non-ABS and ABS subframe
PBCH_RB dB channel powers defined in
PSS_RA dB Table A.3.4.1.1-1.
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 3 dBm/15 kHz -98
dB 1 1 -Infinity -4
( Eˆ s / N oc ) meas Note 5
dB 1 1 N/A N/A
( Ês N oc )ABS
RSRP Note 4,5 dBm/15 kHz -97 -97 -Infinity -102
SCH_RP Note 4 dBm/15 kHz -97 -97 -Infinity -102
dB 1 -0.5 -Infinity -4
CRS Ê s I ot
dB 1 -0.5 -Infinity -7.5
SCH Ê s I ot
Propagation Condition ETU30
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled. Applies to all subframes.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Note 5: RSPP is estimated for Cell 2 during the restricted measurement subframes for neighbour cells.
RSPP is estimated for Cell 1 during the PCell restricted subframes.
A.8.1.7.2 Test Requirements
The UE shall send one Event A3 triggered measurement report for Cell 2, with a measurement reporting delay less than
1000 ms from the beginning of time period T2.
The UE shall not send event-triggered measurement reports as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90% for the tested Event A3.
NOTE: The actual overall delays measured in the tests may be up to 2×TTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1196 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.8 E-UTRAN FDD-FDD Intra-Frequency Event-Triggered Reporting
under Time Domain Measurement Resource Restriction with CRS
Assistance Information and Non-MBSFN ABS
A.8.1.8.1 Test Purpose and Environment
The purpose of this test is to verify that the UE correctly detects and reports Event A3 (neighbour becomes offset better
than PCell) defined in TS 36.331 [2] within the requirements specified in Clause 8.1.2.8.3, when the UE is provided
with a time-domain measurement resource restriction pattern and CRS assistance information, and when non-MBSFN
ABS configured in the interfering cells.
The test parameters are given in Tables A.8.1.8.1-1 and A.8.1.8.1-2 below. It is indicated to the UE in the measurement
control information that event-triggered reporting with Event A3 is used. In the test, there are three synchronous cells,
Cell 1, Cell 2, and Cell 3, on the same RF channel. Cell 1 is the PCell. Cell 3 is the cell to be identified. A non-MBSFN
ABS pattern is configured in each of the Cell 1 and Cell 2 during the entire test.The test consists of two successive time
periods with time duration of T1 and T2, respectively. During time duration T1, the UE shall not have any timing
information on Cell 3.
The UE is configured by higher layers with a time domain measurement resource restriction pattern for performing E-
UTRAN FDD intra-frequency measurements on neighbour cells, nsamely Cell 3 measurements. The UE is also
provided via higher layers with the CRS assistance information for Cell 2. The information for both measurement
patterns and the CRS assistance information shall be provided via RRC to the UE during T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1197 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.8.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under time domain measurement resource restriction with CRS assistance information and
non-MBSFN ABS
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.0 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
PCell Cell 1 Also a first interfering cell to Cell 3.
Active in T1 and T2.
Neighbour cells Cell 2 and Cell 3 Cell 2 is a second interfering cell; Cell 2
is active in T1 and T2.
Cell 3 is the cell to be identified; Cell 3
is active only in T2.
ABS transmission configuration Non-MBSFN ABS As defined in Table A.3.4.1.1-1
E-UTRA RF Channel Number 1 One FDD carrier frequency is used
Channel Bandwidth (BW channel) MHz 10 For all cells in the test
A3-Offset dB -14
Event A3 measurement quantity RSRP
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Time offset between cells μs Cell 2 offset with respect to Three synchronous cells
Cell 1: 0
Cell 3 offset with respect to
Cell 1: -2.5
T1 S 5
T2 S 5
(PCIcell1 - PCIcell3 )mod6 = 0 Cell PCIs are selected so that all
Physical cell IDs (PCIcell2 - PCIcell3 )mod6 != 0 conditions are met
PCIcell1 not equal to PCIcell3
FDD ABS Pattern Info IE, as defined in
TS 36.423 [28], clause 9.2.54.
The first/leftmost bit corresponds to the
Pcell subframe #0 of the radio frame
‘1000000010000000100000
satisfying SFN mod x = 0, where x is
ABS pattern 001000000010000000’
the size of the bit string (40) divided by
10. No MBSFN subframes are
configured in the ABS subframes.
Configured in Cell 1 and Cell 2 during
T1.
Time domain measurement resource
restriction pattern for neighbor cell
measurement signalled to the UE in
Time domain measurement measSubframePatternNeigh IE in
resource restriction pattern for ‘1000000010000000100000 measSubframePatternConfigNeigh, as
neighbour cell measurements on 001000000010000000’ defined in TS 36.331, clause 6.3.5.
RF Channel 1 Configured during T1 for Cell 3
measurements. The cell list in
measSubframeCellList IE shall contain
Cell 3 but not Cell 2.
Time domain measurement Configured during T1 for Cell 1
‘0100000001000000010000
resource restriction pattern for measurements
000100000001000000’
PCell measurements
physCellId see PCI conditions above The CRS assistance information is
antennaPortsC provided for Cell 2 only in CRS-
CRS 1
ount AssistanceInfo. It includes a single
assistance
mbsfn- MBSFN-SubframeConfig element with
information
SubframeConfi oneFrame = ‘000000’ subframe allocation one
gList Frame=’000000’.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1198 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.8.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under time domain measurement resource restriction with CRS assistance information and
non-MBSFN ABS
Cell 1 Cell 2 Cell 3
Parameter Unit
T1 T2 T1 T2 T1 T2
E-UTRA RF Channel
1 1 1
Number
BW channel MHz 10 10 10
Correlation Matrix and
1x2 Low 1x2 Low 1x2 Low
Antenna Configuration
OCNG Patterns defined in
OP.6
A.3.2.1.5 (OP.5 FDD) and OP.5 FDD OP.6 FDD N/A
FDD
in A.3.2.1.6 (OP.6 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
Non-ABS and ABS Non-ABS and ABS
PHICH_RA dB
subframe channel subframe channel
PHICH_RB dB N/A 0
powers defined in powers defined in
PDCCH_RA dB
Table A.3.4.1.1-1. Table A.3.4.1.1-1.
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dBm/15
N oc Note 3
kHz
-98
( Eˆ s / N oc ) dB 4 4 2 2 -Infinity -4
dBm/15
RSRP Note 4 -94 -94 -96 -96 -Infinity -102
kHz
dBm/15
SCH_RP Note 4 -94 -94 -96 -96 -Infinity -102
kHz
CRS Ê s I ot Note 5 dB 4 2.54 2 0.54 -Infinity -9.46
SCH Ê s I ot dB -0.12 -0.75 -3.45 -3.92 -Infinity -11.07
Propagation Condition ETU30 ETU30 ETU30
NOTE 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
NOTE 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
NOTE 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled. Applies to all subframes.
NOTE 4: RSRP, SCH_RP, and Ê s I ot levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
NOTE 5: Applies during the restricted measurement subframes configured for neighbour cell (Cell 3)
measurements.
A.8.1.8.2 Test Requirements
The UE shall send one Event A3 triggered measurement report for Cell 3, with a measurement reporting delay less than
1000 ms from the beginning of time period T2.
The UE shall not send event-triggered measurement reports as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90% for the tested Event A3.
NOTE: The actual overall delays measured in the tests may be up to 2×TTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1199 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.9 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells for 5MHz
bandwidth
A.8.1.9.1 Test Purpose and Environment
The purpose of this test case is the same as for the test defined in subclause A.8.1.1.1.
The parameters of this test are the same as defined in Subclause A.8.1.1.1 except that the values of the parameters in the
Table A.8.1.9.1-1 will replace the values of the corresponding parameters in A.8.1.1.1-1, and the values of the
parameters in the Table A.8.1.9.1-2 will replace the values of the corresponding parameters in A.8.1.1.1-2.
Table A.8.1.9.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for 5MHz bandwidth
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.5 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.11 FDD
Note 1: See Table A.8.1.1.1-1 for the other parameters.
Note 2: This test is according to the principle defined in section A.3.7.2.
Table A.8.1.9.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for 5MHz
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
BW channel MHz 5 5
OCNG Patterns
defined in A.3.2.1.15
(OP.15 FDD) and OP.15 FDD OP.16 FDD
A.3.2.1.16 (OP.16
FDD)
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: See Table A.8.1.1.1-2 for the other parameters.
A.8.1.9.2 Test Requirements
The test requirements defined in section A.8.1.1.2 shall apply to this test case.
A.8.1.10 E-UTRAN FDD-FDD Intra-Frequency Event Triggered Reporting
under Fading Propagation Conditions in Synchronous Cells with
DRX for 5 MHz Bandwidth
A.8.1.10.1 Test Purpose and Environment
The purpose of the two tests is to verify that the UE makes correct reporting of an event in DRX. The tests will partly
verify the FDD-FDD intra-frequency cell search in DRX requirements in clause 8.1.2.2.1.2.
The parameters of this test are the same as defined in Section A.8.1.3.1 except that the values of the parameters in the
Table A.8.1.10.1-1 will replace the values of the corresponding parameters in A.8.1.3.1-1, and the values of the
parameters in the Table A.8.1.10.1-2 will replace the values of the corresponding parameters in A.8.1.3.1-2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1200 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.10.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Value Comment
Test 1 Test 2
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.1
Channel R.5 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.11 FDD
Channel Bandwidth MHz 5
(BW channel)
NOTE 1: See Table A.8.1.3.1-1 for the other parameters.
NOTE 2: This test is according to the principle defined in Section A.3.7.2.
Table A.8.1.10.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
BW channel MHz 5 5
OCNG Patterns
defined in A.3.2.1.15 OP.15 FDD OP.16 FDD
(OP.15 FDD) and in
A.3.2.1.16 (OP.16
FDD)
NOTE 1: See Table A.8.1.3.1-2 for the other parameters.
A.8.1.10.2 Test Requirements
The test requirements defined in Section A.8.1.3 shall apply to this test case.
A.8.1.11 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells for UE category
0
A.8.1.11.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the FDD
intra-frequency cell search requirements in clause 8.5.2.1.1.
The test parameters are given in Table A.8.1.11.1-1 and A.8.1.11.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1201 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.11.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.3
Channel R.13 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Time offset between cells 3 ms Asynchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1202 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.11.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions in asynchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_PB dB
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 4 -1.46 -Infinity -1.46
N oc Note 3 dBm/15 KHz -98
Ê s N oc dB 4 4 -Infinity 4
RSRP Note 4 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 4 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.11.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 1000 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1203 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.12 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for UE category
0
A.8.1.12.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the FDD
intra-frequency cell search requirements in clause 8.5.2.1.1
The test parameters are given in Table A.8.1.12.1-1 and A.8.1.12.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. PDCCHs indicating new transmissions or
retransmissions should be sent continuously to ensure that the UE would not enter the DRX state. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
Table A.8.1.12.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.3
Channel R.13 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX DRX_L As specified in clause A.3.3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1204 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.12.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions in synchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 4 -1.46 -Infinity -1.46
N oc Note 3 dBm/15 KHz -98
Ês N oc dB 4 4 -Infinity 4
RSRP Note 4 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 4 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.12.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 1000 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1205 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.13 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells with DRX for UE
category 0
A.8.1.13.1 Test Purpose and Environment
The purpose of the two tests is to verify that the UE makes correct reporting of an event in DRX. The tests will partly
verify the FDD-FDD intra-frequency cell search in DRX requirements in clause 8.5.2.1.1.2.
The test parameters are given in Tables A.8.1.13.1-1, A.8.1.13.1-2, A.8.1.13.1-3 and A.8.1.13.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furhtermore UE is allocated with
PUSCH resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.1.13.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Value Comment
Test 1 Test 2
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.3
Channel R.13 FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.1
parameters Channel R.6 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are defined in
Table A.8.1.13.1-3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1206 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.13.11-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 4 -1.46 -Infinity -1.46
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 4 4 -Infinity 4
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Table A.8.1.13.1-3: DRX-Configuration for E-UTRAN FDD-FDD intra-frequency event triggered
reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1207 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.13.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD-FDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 0 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.13.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
1000 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
25600 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request
(SR) to obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE 1: The actual overall delays measured in the test may be up to one DRX cycle higher than the measurement
reporting delays above because UE is allowed to delay the initiation of the measurement reporting
procedure to the next until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has received correct
Event A3 measurement report.
A.8.1.14 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells for UE category
0
A.8.1.14.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the FDD
intra-frequency cell search requirements in clause 8.5.2.1.2.1.
The test parameters are given in Table A.8.1.14.1-1 and A.8.1.14.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1208 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.14.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.4
Channel R.2 HD-FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.3
parameters Channel R.4 HD-FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Time offset between cells 3 ms Asynchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1209 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.14.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_PB dB
PDCCH_RA dB
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 4 -1.46 -Infinity -1.46
N oc Note 3 dBm/15 KHz -98
Ês N oc dB 4 4 -Infinity 4
RSRP Note 4 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 4 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
N oc to be fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.14.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 1000 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1210 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.15 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for UE category
0
A.8.1.15.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the FDD
intra-frequency cell search requirements in clause 8.5.2.1.2.1
The test parameters are given in Table A.8.1.15.1-1 and A.8.1.15.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. PDCCHs indicating new transmissions or
retransmissions should be sent continuously to ensure that the UE would not enter the DRX state. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
Table A.8.1.15.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.4
Channel R.2 HD-FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.3
parameters Channel R.4 HD-FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX DRX_L As specified in clause A.3.3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1211 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.15.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 4 -1.46 -Infinity -1.46
N oc Note 3 dBm/15 KHz -98
Ês N oc dB 4 4 -Infinity 4
RSRP Note 4 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 4 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.15.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 1000 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1212 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.16 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells with DRX for UE
category 0
A.8.1.16.1 Test Purpose and Environment
The purpose of the two tests is to verify that the UE makes correct reporting of an event in DRX. The tests will partly
verify the FDD-FDD intra-frequency cell search in DRX requirements in clause 8.5.2.1.2.2.
The test parameters are given in Tables A.8.1.16.1-1, A.8.1.16.1-2, A.8.1.16.1-3 and A.8.1.16.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furhtermore UE is allocated with
PUSCH resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.1.16.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Value Comment
Test 1 Test 2
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.4
Channel R.2 HD-FDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.3
parameters Channel R.4 HD-FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel 1 One FDD carrier frequency is used.
Number
Channel Bandwidth MHz 10
(BW channel)
A3-Offset dB -6
CP length Normal
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are defined in
Table A.8.1.16.1-3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1213 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.16.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns
defined in A.3.2.1.1 OP.1 FDD OP.2 FDD
(OP.1 FDD) and in
A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
Ê s Iot dB 4 -1.46 -Infinity -1.46
N oc Note 2 dBm/15 KHz -98
Ês N oc dB 4 4 -Infinity 4
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They
are not settable parameters themselves.
Table A.8.1.16.1-3: DRX-Configuration for E-UTRAN HD-FDD intra-frequency event triggered
reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1214 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.16.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 0 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.16.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
1000 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
25600 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request
(SR) to obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE 1: The actual overall delays measured in the test may be up to one DRX cycle higher than the measurement
reporting delays above because UE is allowed to delay the initiation of the measurement reporting
procedure to the next until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has received correct
Event A3 measurement report.
A.8.1.17 E-UTRAN TDD-TDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells
A.8.1.17.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the TDD
intra-frequency cell search requirements in clause 8.5.2.1.3.1.
The test parameters are given in Table A.8.1.17.1-1 and A.8.1.17.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. PDCCHs indicating new transmissions or
retransmissions should be sent continuously to ensure that the UE would not enter the DRX state. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1215 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.17.1-1: General test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Value Comment
DL Reference Measurement
PDSCH parameters Channel R.13 TDD As specified in clause A.3.1.1.5
DL Reference Measurement
PCFICH/PDCCH/PHICH Channel R.7 TDD As specified in clause A.3.1.2.2
parameters
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 One TDD carrier frequency is used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -6
CP length Normal
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211.
The same configuration in both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211.
The same configuration in both cells
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX DRX_L As specified in clause A.3.3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1216 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.17.1-2: Cell specific test parameters for E-UTRAN TDD-TDD intra-frequency event
triggered reporting under fading propagation conditions in synchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Pattern defined
in A.3.2.2.1 (OP.1 OP.1 TDD OP.2 TDD
TDD) and in A.3.2.2.2
(OP.2)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 3 dBm/15 kHz -98
RSRP Note 4 dBm/15 kHz -94 -94 -Infinity -94
Ê s Iot dB 4 -1.46 -Infinity -1.46
SCH_RP Note 4 dBm/15 kHz -94 -94 -Infinity -94
Ês N oc dB 4 4 -Infinity 4
Propagation Condition ETU70
Note 1 OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.17.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 1000 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1217 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.18 E-UTRAN TDD-TDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells with DRX
A.8.1.18.1 Test Purpose and Environment
The purpose of the two tests is to verify that the UE makes correct reporting of an event in DRX. The tests will partly
verify the TDD-TDD intra-frequency cell search in DRX requirements in clause 8.5.2.1.3.2.
The test parameters are given in Tables A.8.1.18.1-1, A.8.1.18.1-2, A.8.1.18.1-3 and A.8.1.18.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time aligment timer to keep UE uplink time alignment. Furhtermore UE is allocated with PUSCH
resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.1.18.1-1: General test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Value Comment
Test 1 Test 2
DL Reference Measurement
PDSCH parameters Channel R.13 TDD As specified in clause A.3.1.1.5
DL Reference Measurement
PCFICH/PDCCH/PHICH Channel R.7 TDD As specified in clause A.3.1.2.2
parameters
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 One TDD carrier frequency is used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -6
CP length Normal
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211.
The same configuration in both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211.
The same configuration in both cells
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are defined in
Table A.8.1.18.1-3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1218 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.18.1-2: Cell specific test parameters for E-UTRAN TDD-TDD intra-frequency event
triggered reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Pattern defined
in A.3.2.2.1 (OP.1 OP.1 TDD OP.2 TDD
TDD) and in A.3.2.2.2
(OP.2)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 kHz -94 -94 -Infinity -94
Ê s Iot dB 4 -1.46 -Infinity -1.46
SCH_RP Note 3 dBm/15 kHz -94 -94 -Infinity -94
Ês N oc dB 4 4 -Infinity 4
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Table A.8.1.18.1-3: DRX-Configuration for E-UTRAN TDD-TDD intra-frequency event triggered
reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1219 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.18.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD-TDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 2 2 clause 6.3.2 in TS 36.331 and
clause 10.1 in TS 36.213.
A.8.1.18.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
1000 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
25600 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request
(SR) to obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE 1: The actual overall delays measured in the test may be up to one DRX cycle higher than the measurement
reporting delays above because UE is allowed to delay the initiation of the measurement reporting
procedure to the next until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has received correct
Event A3 measurement report.
A.8.1.19 E-UTRAN FDD-FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps for UE category 0
A.8.1.19.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.5.2.1.4.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.19.1-1 and A.8.1.19.1-2.
PDCCHs indicating new transmissions should be sent continuously to ensure that the UE would have ACK/NACK
sending during identifying a new CGI of E-UTRAN cell. The test consists of three successive time periods, with time
durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have any timing information
of cell 2. Starting T2, cell 2 becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1220 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.19.1-1: General test parameters for E-UTRAN FDD - FDD Intra-frequency identification of
a new CGI of E-UTRA cell using autonomous gaps for UE category 0
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.3
Channel R.15 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.7 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤10
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1221 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.19.1-2: Cell specific test parameters for E-UTRAN FDD - FDD Intra-frequency
identification of a new CGI of E-UTRA cell using autonomous gaps for UE category 0
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns defined in OP.10 OP.10 OP.10 OP.2 OP.2 OP.2
A.3.2.1.10 (OP.10 FDD) FDD FDD FDD FDD FDD FDD
and in A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PCFICH_RB dB 0 0
PHICH_RA dB -3 -3
PHICH_PB dB
PDCCH_RA dB 0 0
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ê s N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
A.8.1.19.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 210 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_LC- UE, intra + reporting delay
= 15 + 190 + 2ms from the start of T3
= 207 ms, allow 210 ms.
The UE shall be scheduled continuously throughout the test, and from the start of T3 until 210 ms at least 112
ACK/NACK shall be detected as being transmitted by the UE.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The overall 112 ACK/NACK number is caused by two parts. Firstly, at least 92 ACK/NACK shall be
sent during identifying the cell global identifier of cell 2 according to the requirement in Clause 8.5.2.1.4.
Secondly, given that continuous DL data allocation, additional 20 ACK/NACK shall be sent from the
start of T3 until 210 ms excludes 190 ms for identifying the cell global identifier of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1222 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.20 E-UTRAN FDD - FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps with DRX for UE category 0
A.8.1.20.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in clause
8.5.2.1.4. The requirement is verified in a DRX configuration.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.20.1-1, A.8.1.20.1-2,
A.8.1.20.1-3 and A.8.1.20.1-4. The test consists of three successive time periods, with time durations of T1, T2 and T3
respectively. At the start of time duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2
becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
In the test UE needs to be provided at least once every 1280ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furthermore UE sends scheduling
request (SR) to obtain allocation to send the measurement report on PUSCH.
Table A.8.1.20.1-1: General test parameters for E-UTRAN FDD - FDD Intra-frequency identification of
a new CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.3
Channel R.15 FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.1
Channel R.7 FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are
defined in Table A.8.1.6.1-3
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤30 UE should report cell within 25.6s
(20 DRX cycles)
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1223 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.20.1-2: Cell specific test parameters for E-UTRAN FDD - FDD Intra-frequency
identification of a new CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns defined in OP.1 OP.1 OP.1 OP.2 OP.2 OP.2
A.3.2.1.1 (OP.1 FDD) and FDD FDD FDD FDD FDD FDD
in A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PCFICH_RB dB 0 0
PHICH_RA dB -3 -3
PHICH_PB dB
PDCCH_RA dB 0 0
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ê s N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
Table A.8.1.20.1-3: DRX configuration for E-UTRAN FDD - FDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Field Value Comment
onDurationTimer psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1224 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.20.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD - FDD Intra-frequency
identification of a new CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer Infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.20.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 210 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_LC- UE, intra + reporting delay
= 15 + 190 + 2ms from the start of T3
= 207 ms, allow 210 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
A.8.1.21 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps for UE category 0
A.8.1.21.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.5.2.1.5.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.21.1-1 and A.8.1.21.1-2.
PDCCHs indicating new transmissions should be sent continuously to ensure that the UE would have ACK/NACK
sending during identifying a new CGI of E-UTRAN cell. The test consists of three successive time periods, with time
durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have any timing information
of cell 2. Starting T2, cell 2 becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1225 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.21.1-1: General test parameters for E-UTRAN HD - FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps for UE category 0
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.4
Channel R.2 HD-FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.3
Channel R.4 HD-FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤10
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1226 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.21.1-2: Cell specific test parameters for E-UTRAN HD - FDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps for UE category 0
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns defined in OP.10 OP.10 OP.10 OP.2 OP.2 OP.2
A.3.2.1.10 (OP.10 FDD) FDD FDD FDD FDD FDD FDD
and in A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PCFICH_RB dB 0 0
PHICH_RA dB -3 -3
PHICH_PB dB
PDCCH_RA dB 0 0
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ê s N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
A.8.1.21.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 210 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_LC- UE, intra + reporting delay
= 15 + 190 + 2ms from the start of T3
= 207 ms, allow 210 ms.
The UE shall be scheduled continuously throughout the test, and from the start of T3 until 210 ms at least 112
ACK/NACK shall be detected as being transmitted by the UE.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The overall 112 ACK/NACK number is caused by two parts. Firstly, at least 92 ACK/NACK shall be
sent during identifying the cell global identifier of cell 2 according to the requirement in Clause 8.5.2.1.5.
Secondly, given that continuous DL data allocation, additional 20 ACK/NACK shall be sent from the
start of T3 until 210 ms excludes 190 ms for identifying the cell global identifier of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1227 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.22 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps with DRX for UE category 0
A.8.1.22.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.5.2.1.5. The requirement is verified in a DRX configuration.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.22.1-1, A.8.1.22.1-2,
A.8.1.22.1-3 and A.8.1.22.1-4. The test consists of three successive time periods, with time durations of T1, T2 and T3
respectively. At the start of time duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2
becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
In the test UE needs to be provided at least once every 1280ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furthermore UE sends scheduling
request (SR) to obtain allocation to send the measurement report on PUSCH.
Table A.8.1.22.1-1: General test parameters for E-UTRAN HD - FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.4
Channel R.2 HD-FDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.3
Channel R.4 HD-FDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one FDD carrier frequency is
used.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are
defined in Table A.8.1.6.1-3
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤30 UE should report cell within 25.6s
(20 DRX cycles)
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1228 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.22.1-2: Cell specific test parameters for E-UTRAN HD - FDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns defined in OP.1 OP.1 OP.1 OP.2 OP.2 OP.2
A.3.2.1.1 (OP.1 FDD) and FDD FDD FDD FDD FDD FDD
in A.3.2.1.2 (OP.2 FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PCFICH_RB dB 0 0
PHICH_RA dB -3 -3
PHICH_PB dB
PDCCH_RA dB 0 0
PDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ê s N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
Table A.8.1.22.1-3: DRX configuration for E-UTRAN HD - FDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Field Value Comment
onDurationTimer psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1229 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.22.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD - FDD Intra-frequency
identification of a new CGI of E-UTRA cell using autonomous gaps with DRX for UE category 0
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer Infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.22.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 210 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_LC- UE, intra + reporting delay
= 15 + 190 + 2ms from the start of T3
= 207 ms, allow 210 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
A.8.1.23 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells for Cat-M1 UE
in CEModeA
A.8.1.23.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the FDD intra-frequency cell search requirements for Cat-M1 UE in clause 8.13.2.1.1.1.
The test parameters are given in Table A.8.1.23.1-1 and A.8.1.23.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
Table A.8.1.23.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used.
Number
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX OFF
A3 Offset dB -6
Hysteresis dB 0
Time To Trigger S 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 1
T1 S 5
T2 S 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1230 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.23.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in
CEModeA
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.21 FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.17 FDD R.17 FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ê s N oc
dB 4 -1.46 -Infinity -1.46
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Io Note 3 dBm/9MHz -64.76 -62.42 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
A.8.1.23.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 2.88s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1231 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.24 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA
A.8.1.24.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the FDD intra-frequency cell search requirements in clause 8.13.2.1.1.1.
The test parameters are given in Table A.8.1.24.1-1 and A.8.1.24.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. MPDCCHs indicating new transmissions or
retransmissions shall be sent continuously to ensure that the UE would not enter the DRX state. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have
any timing information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level
as for cell 1, and due to usage of an offset this shall result in reporting of Event A3.
Table A.8.1.24.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used.
Number
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX OFF
A3 Offset dB -6
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 1
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1232 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.24.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions for Cat-M1 UE in synchronous cells in
CEModeA
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.21 FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.17 FDD R.17 FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ê s N oc
dB 4 -1.46 -Infinity -1.46
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Io Note 3 dBm/9MHz -64.76 -62.42 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
A.8.1.24.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 2.88 s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1233 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.25 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA in DRX
A.8.1.25.1 Test Purpose and Environment
The purpose of the two tests is to verify that the Cat-M1 UE makes correct reporting of an event in DRX. The tests will
partly verify the FDD intra-frequency cell search in DRX requirements in clause 8.13.2.1.1.2.
The test parameters are given in Tables A.8.1.25.1-1, A.8.1.25.1-2, A.8.1.25.1-3 and A.8.1.25.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same
level as for cell 1, and due to usage of an offset this shall result in reporting of Event A3.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furhtermore UE is allocated with
PUSCH resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.1.25.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE when DRX is used
Parameter Unit Value Comment
Test1 Test2
E-UTRA RF Channel 1 1 One radio channel is used.
Number
Active cell Cell 1 Cell 1
Neighbour cell Cell 2 Cell 2 Cell to be identified.
CP length Normal Normal
DRX ON ON DRX related parameters are defined in
Table A.8.1.25.1-3
A3 Offset dB -6 -6
Hysteresis dB 0 0
Time To Trigger s 0 0
Filter coefficient 0 0 L3 filtering is not used
Gap pattern ID 0 0
T1 s 5 5
T2 s 5 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1234 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.25.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions in synchronous cells for Cat-M1 UE when
DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.21 FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.17 FDD R.17 FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ê s N oc
dB 4 -1.46 -Infinity -1.46
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Io Note 3 dBm/9MHz -64.76 -62.42 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
Table A.8.1.25.1-3: DRX-Configuration for E-UTRAN FDD-FDD intra-frequency event triggered
reporting in DRX under fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1235 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.25.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD-FDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells for Cat-M1 UE
in CEModeA
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 0 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.25.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
1.44 s from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
25600 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request
(SR) to obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE 1: The actual overall delays measured in the test may be up to one DRX cycle higher than the
measurement reporting delays above because UE is allowed to delay the initiation of the measurement reporting
procedure to the next until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has received
correct Event A3 measurement report.
A.8.1.26 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells for Cat-M1 UE
in CEModeA
A.8.1.26.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the HD-FDD intra-frequency cell search requirements in clause 8.13.2.1.2.1.
The test parameters are given in Table A.8.1.26.1-1 and A.8.1.26.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1 and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1236 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.26.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used for this test
Number
Active Cell Cell 1
Neighbour cell Cell 2 Cell to be identified
CP length Normal
DRX OFF
A3 Offset dB -6
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 1
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1237 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.26.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.11 HD-FDD -
DL Reference
Measurement
Channel
MPDCCH parameters: R.7 HD-FDD R.7 HD-FDD
DL Reference
Measurement
Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
NocNote 2 dBm/15 kHz -98
Ês/Noc dB 4 4 -infinity 4
Ês/Iot Note 3 dB 4 -1.46 -infinity -1.46
RSRP Note 3 dBm/15 kHz -94 -94 -infinity -94
SCH_RP Note 3 dBm/15 kHz -94 -94 -infinity -94
Io Note 3 dBm/9MHz -64.76 -62.42 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and
2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the
test is assumed to be constant over subcarriers and time and shall be
modelled as AWGN of appropriate power for Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other
parameters for information purposes. They are not settable
parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to
the start of time period T2.
A.8.1.26.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 2.88s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the tests may be up to 2×TTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1238 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.27 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA
A.8.1.27.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the HD-FDD intra-frequency cell search requirements in clause 8.13.2.1.2.1.
The test parameters are given in Table A.8.1.27.1-1 and A.8.1.27.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1 and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
Table A.8.1.27.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used for this test
Number
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX DRX_L As specified in clause A.3.3
A3 Offset dB -6
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 1 As specified in TS 36.133 clause 8.1.2.1.
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1239 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.27.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.11 HD-FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.7 HD-FDD R.7 HD-FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ê s N oc
dB 4 -1.46 -Infinity -1.46
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Io Note 3 dBm/9MHz -64.76 -62.42 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
A.8.1.27.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 2.88s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1240 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.28 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA in DRX
A.8.1.28.1 Test Purpose and Environment
The purpose of the two tests is to verify that the Cat-M1 UE makes correct reporting of an event in DRX. The tests will
partly verify the HD-FDD intra-frequency cell search in DRX requirements in clause 8.13.2.1.2.2.
The test parameters are given in Tables A.8.1.28.1-1, A.8.1.28.1-2, A.8.1.28.1-3 and A.8.1.28.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furhtermore UE is allocated with
PUSCH resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.1.28.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeA
when DRX is used
Parameter Unit Value Comment
Test1 Test2
E-UTRA RF Channel Number 1 1 One radio channel is used for this test
Active cell Cell 1 Cell1
Neighbour cell Cell 2 Cell2 Cell to be identified.
CP length Normal Normal
DRX ON ON DRX related parameters are defined in Table A.8.1.28.1-3
A3 Offset dB -6 -6
Hysteresis dB 0 0
Time To Trigger s 0 0
Filter coefficient 0 0 L3 filtering is not used
Gap pattern ID 0 0 As specified in TS 36.133 clause 8.1.2.1.
T1 s 5 5
T2 s 5 35
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1241 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.28.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeA
when DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.11 HD-FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.7 HD-FDD R.7 HD-FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB 4 4 -Infinity 4
Ê s N oc
dB 4 -1.46 -Infinity -1.46
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 KHz -94 -94 -Infinity -94
Io Note 3 dBm/9MHz -64.76 -62.42 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
Table A.8.1.28.1-3: DRX-Configuration for E-UTRAN HD-FDD intra-frequency event triggered
reporting in DRX under fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1242 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.28.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD-FDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells for Cat-M1 UE
in CEModeA
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 0 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.28.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
1.44 s from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
32 s from the beginning of time period T2. The measurement reporting delay is defined as the time from the beginning
of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request (SR) to
obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE 1: The actual overall delays measured in the test may be up to one DRX cycle higher than the measurement
reporting delays above because UE is allowed to delay the initiation of the measurement reporting
procedure to the next until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has
received correct Event A3 measurement report.
A.8.1.29 E-UTRAN TDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA
A.8.1.29.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE in CEModeA makes correct reporting of an event. This test will
partly verify the TDD intra-frequency cell search requirements in clause 8.13.2.1.3.1.
The test parameters are given in Table A.8.1.29.1-1 and A.8.1.29.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1 and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1243 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.29.1-1: General test parameters for E-UTRAN TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Value Comments
E-UTRA RF Channel Number 1 One radio channel is used for this test.
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX OFF
Offset dB -6
A3 Hysteresis dB 0
Time To Trigger s 0
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211.
The same configuration in both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211.
The same configuration in both cells
Filter coefficient 0 L3 filtering is not used
Gap Pattern Id 1
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1244 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.29.1-2: Cell specific test parameters for E-UTRAN TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeA
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel
1
Number
BW channel MHz 10
PDSCH parameters:
DL Reference R.17 TDD -
Measurement Channel
MPDCCH parameters:
DL Reference R.15 TDD R.15 TDD
Measurement Channel
OCNG Patterns OP.11 TDD OP.2 TDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
NocNote 2 dBm/15 kHz -98
Ês/Noc dB 4 4 -Infinity 4
Ês/Iot Note 3 dB 4 -1.46 -Infinity -1.46
RSRP Note 3 dBm/15 kHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 kHz -94 -94 -Infinity -94
Io Note 3 dBm/9 MHz -64.76 -62.42 -64.76 -62.42
Propagation Condition ETU30 ETU30
Correlation Matrix and
2x1 Low 2x1 Low
Antenna Configuration
Time offset to Cell 1 μs - 3
Note 1 OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for Noc to be
fulfilled.
Note 3: Ês/Iot, RSRP, SCH_RP and Io levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
A.8.1.29.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 2.88
second from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1245 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.30 E-UTRAN TDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeA in DRX
A.8.1.30.1 Test Purpose and Environment
The purpose of the two tests is to verify that the Cat-M1 UE in CEModeA makes correct reporting of an event in DRX.
The tests will partly verify the TDD intra-frequency cell search in DRX requirements in clause 8.13.2.1.3.2.
The test parameters are given in Tables A.8.1.30.1-1, A.8.1.30.1-2, A.8.1.30.1-3 and A.8.1.30.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same
level as for cell 1, and due to usage of an offset this shall result in reporting of Event A3.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time aligment timer to keep UE uplink time alignment. Furhtermore UE is allocated with PUSCH
resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.1.30.1-1: General test parameters for E-UTRAN TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used for Cat-M1 UE
in CEModeA
Parameter Unit Value Comments
Test 1 Test 2
E-UTRA RF Channel Number 1 One radio channel is used for both
tests.
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX ON DRX related parameters are defined in
Table A.8.1.30.1-3
Offset dB -6
A3 Hysteresis dB 0
Time To Trigger s 0
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211.
The same configuration in both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211.
The same configuration in both cells
Filter coefficient 0 L3 filtering is not used
Gap Pattern Id 0
T1 s 5
T2 s 5 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1246 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.30.1-2: Cell specific test parameters for E-UTRAN TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used for Cat-M1 UE
in CEModeA
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel
1
Number
BW channel MHz 10
PDSCH parameters:
DL Reference R.17 TDD -
Measurement Channel
MPDCCH parameters:
DL Reference R.15 TDD R.15 TDD
Measurement Channel
OCNG Patterns OP.11 TDD OP.2 TDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
NocNote 2 dBm/15 kHz -98
Ês/Noc dB 4 4 -Infinity 4
Ês/Iot Note 3 dB 4 -1.46 -Infinity -1.46
RSRP Note 3 dBm/15 kHz -94 -94 -Infinity -94
SCH_RP Note 3 dBm/15 kHz -94 -94 -Infinity -94
Io Note 3 dBm/9 MHz -64.76 -62.42 -64.76 -62.42
Propagation Condition ETU30 ETU30
Correlation Matrix and
2x1 Low 2x1 Low
Antenna Configuration
Time offset to Cell 1 μs - 3
Note 1 OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for Noc to be
fulfilled.
Note 3: Ês/Iot, RSRP, SCH_RP and Io levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Table A.8.1.30.1-3: DRX-Configuration for E-UTRAN TDD intra-frequency event triggered reporting in
DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1247 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.30.1-4: TimeAlignmentTimer-Configuration for E-UTRAN TDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 2 2 clause 6.3.2 in TS 36.331 and
clause 10.1 in TS 36.213.
A.8.1.30.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
1.44 second from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
25.6 second from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request
(SR) to obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE 1: The actual overall delays measured in the test may be up to one DRX cycle higher than the measurement
reporting delays above because UE is allowed to delay the initiation of the measurement reporting
procedure to the next until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has received correct
Event A3 measurement report.
A.8.1.31 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells for Cat-M1 UE
in CEModeB
A.8.1.31.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the FDD intra-frequency cell search requirements for Cat-M1 UE in clause 8.13.3.1.1.1.
The test parameters are given in Table A.8.1.31.1-1 and A.8.1.31.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1248 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.31.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used.
Number
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX OFF
A3 Offset dB -8
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 0
T1 s 5
T2 s ≤325
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1249 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.31.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in
CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.23 FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.11 FDD R.19 FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB -12 -12 -Infinity -12
Ê s N oc
dB -12 -12.27 -Infinity -12.27
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -110 -110 -Infinity -110
SCH_RP Note 3 dBm/15 KHz -110 -110 -Infinity -110
Io Note 3 dBm/9MHz -69.95 -69.70 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
A.8.1.31.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 320.8 s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1250 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.32 E-UTRAN FDD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeB
A.8.1.32.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the FDD intra-frequency cell search requirements in clause 8.13.3.1.1.1.
The test parameters are given in Table A.8.1.32.1-1 and A.8.1.32.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. MPDCCHs indicating new transmissions or
retransmissions shall be sent continuously to ensure that the UE would not enter the DRX state. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have
any timing information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level
as for cell 1, and due to usage of an offset this shall result in reporting of Event A3.
Table A.8.1.32.1-1: General test parameters for E-UTRAN FDD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used.
Number
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX OFF
A3 Offset dB -8
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 0
T1 s 5
T2 s ≤325
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1251 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.32.1-2: Cell specific test parameters for E-UTRAN FDD-FDD intra-frequency event
triggered reporting under fading propagation conditions for Cat-M1 UE in synchronous cells in
CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.23 FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.19 FDD R.19 FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB -12 -12 -Infinity -12
Ê s N oc
dB -12 -12.27 -Infinity -12.27
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -110 -110 -Infinity -110
SCH_RP Note 3 dBm/15 KHz -110 -110 -Infinity -110
Io Note 3 dBm/9MHz -69.95 -69.70 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
A.8.1.32.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 320.8 s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1252 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.33 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in asynchronous cells for Cat-M1 UE
in CEModeB
A.8.1.33.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the HD-FDD intra-frequency cell search requirements in clause 8.13.3.1.2.1.
The test parameters are given in Table A.8.1.33.1-1 and A.8.1.33.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1 and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
Table A.8.1.33.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used for this test
Number
Active Cell Cell 1
Neighbour cell Cell 2 Cell to be identified
CP length Normal
DRX OFF
A3 Offset dB -8
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 0
T1 s 5
T2 s ≤325
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1253 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.33.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in asynchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.13 HD-FDD -
DL Reference
Measurement
Channel
MPDCCH parameters: R.9 HD-FDD R.9HD-FDD
DL Reference
Measurement
Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
NocNote 2 dBm/15 kHz -98
Ês/Noc dB -12 -12 -infinity -12
Ês/Iot Note 3 dB -12 -12.27 -infinity -12.27
RSRP Note 3 dBm/15 kHz -110 -110 -infinity -110
SCH_RP Note 3 dBm/15 kHz -110 -110 -infinity -110
Io Note 3 dBm/9MHz -69.95 -69.70 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and
2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 ms - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a
constant total transmitted power spectral density is achieved for all
OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the
test is assumed to be constant over subcarriers and time and shall be
modelled as AWGN of appropriate power for Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other
parameters for information purposes. They are not settable
parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to
the start of time period T2.
A.8.1.33.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 320.8s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the tests may be up to 2×TTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1254 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.34 E-UTRAN HD-FDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeB
A.8.1.34.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE makes correct reporting of an event. This test will partly verify
the HD-FDD intra-frequency cell search requirements in clause 8.13.3.1.2.1.
The test parameters are given in Table A.8.1.34.1-1 and A.8.1.34.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1 and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
Table A.8.1.34.1-1: General test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
E-UTRA RF Channel 1 One radio channel is used for this test
Number
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX OFF
A3 Offset dB -8
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
Gap pattern ID 0 As specified in TS 36.133 clause 8.1.2.1.
T1 s 5
T2 s ≤325
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1255 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.34.1-2: Cell specific test parameters for E-UTRAN HD-FDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH parameters: R.13 HD-FDD -
DL Reference
Measurement Channel
MPDCCH parameters: R.9 HD-FDD R.9 HD-FDD
DL Reference
Measurement Channel
OCNG Patterns OP.21 FDD OP.2 FDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB -3 -3
PHICH_RB dB
MPDCCH_RA dB
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB -12 -12 -infinity -12
Ê s N oc
dB -12 -12.27 -infinity -12.27
Ê s I ot Note 3
RSRP Note 3 dBm/15 KHz -110 -110 -infinity -110
SCH_RP Note 3 dBm/15 KHz -110 -110 -infinity -110
Io Note 3 dBm/9MHz -69.95 -69.70 Specified in
Cell 1 columns
Propagation Condition ETU30 ETU30
Correlation Matrix and 2x1 Low 2x1 Low
Antenna Configuration
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted
power spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be
constant over subcarriers and time and shall be modelled as AWGN of appropriate power for
Noc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period
T2.
A.8.1.34.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 320.8s
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1256 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.35 E-UTRAN TDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells for Cat-M1 UE in
CEModeB
A.8.1.35.1 Test Purpose and Environment
The purpose of this test is to verify that the Cat-M1 UE in CEModeB makes correct reporting of an event. This test will
partly verify the TDD intra-frequency cell search requirements in clause 8.13.3.1.3.1.
The test parameters are given in Table A.8.1.35.1-1 and A.8.1.35.1-2 below. In the measurement control information it
is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of two successive time
periods, with time duration of T1 and T2 respectively. During time duration T1, the UE shall not have any timing
information of cell 2. At the beginning of T2 the transmission power of cell 2 is increased to the same level as for cell 1,
and due to usage of an offset this shall result in reporting of Event A3.
Table A.8.1.35.1-1: General test parameters for E-UTRAN TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Value Comments
E-UTRA RF Channel Number 1 One radio channel is used for this test.
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
DRX OFF
Offset dB -8
A3 Hysteresis dB 0
Time To Trigger s 0
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211.
The same configuration in both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211.
The same configuration in both cells
Filter coefficient 0 L3 filtering is not used
Gap Pattern Id 0
T1 s 5
T2 s ≤325
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1257 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.35.1-2: Cell specific test parameters for E-UTRAN TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells for Cat-M1 UE in CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel
1
Number
BW channel MHz 10
PDSCH parameters:
DL Reference R.19 TDD -
Measurement Channel
MPDCCH parameters:
DL Reference R.17 TDD R.17 TDD
Measurement Channel
OCNG Patterns OP.11 TDD OP.2 TDD
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB -3 -3
MPDCCH_RA dB
MPDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
NocNote 2 dBm/15 kHz -98
Ês/Noc dB -12 -12 -Infinity -12
Ês/Iot Note 3 dB -12 -12.27 -Infinity -12.27
RSRP Note 3 dBm/15 kHz -110 -110 -Infinity -110
SCH_RP Note 3 dBm/15 kHz -110 -110 -Infinity -110
Io Note 3 dBm/9 MHz -69.95 -69.70 Specified in Specified in
Cell 1 Cell 1
columns columns
Propagation Condition ETU30 ETU30
Correlation Matrix and
2x1 Low 2x1 Low
Antenna Configuration
Time offset to Cell 1 μs - 3
Note 1 OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for Noc to be
fulfilled.
Note 3: Ês/Iot, RSRP, SCH_RP and Io levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
Note 4: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
A.8.1.35.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 323.2
seconds from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1258 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.36 E-UTRAN FDD Intra-frequency identification of a new CGI of E-
UTRA cell using autonomous gaps for Cat-M1 UE in CEModeB
A.8.1.36.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.13.3.1.4.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.36.1-1 and A.8.1.36.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2 becomes detectable and the UE
is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
Table A.8.1.36.1-1: General test parameters for E-UTRAN FDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
CP length Normal
A3-Offset dB -16
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤ 325
T3 s 7
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1259 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.36.1-2: Cell specific test parameters for E-UTRAN FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps for Cat-M1 UE in CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH Reference R.23 FDD N/A
Channel in clause
A.3.1.4.4
MPDCCH Reference R.19 FDD N/A
Channel in
clause A.3.1.3.4
OCNG Patterns defined in OP.21 FDD OP.2 FDD
A.3.2.1.21 (OP.21 FDD)
and in A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PHICH_RA dB -3 -3
PHICH_PB dB
MPDCCH_RA dB 0 0
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity -3 -3
Ê s N oc
8 6.24 6.24 -Infinity -11.64 -11.64
Ê s I ot
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
Io Note 3 dBm/9MHz -61.58 -61.29 -61.29 Specified in columns for Cell 1
Propagation Condition AWGN AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
PBCH repetition Configured as specified in TS
36.211 [16]
SIB1-BR repetition level - 16
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.36.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 5137 ms from the start
of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_Cat M1, intra + reporting delay
= 15 + 5120 + 2ms from the start of T3
= 5137 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1260 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.37 E-UTRAN FDD Intra-frequency identification of a new CGI of E-
UTRA cell using autonomous gaps with DRX for Cat-M1 UE in
CEModeB
A.8.1.37.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.13.3.1.4. The requirement is verified in a DRX configuration.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.37.1-1 and A.8.1.37.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2 becomes detectable and the UE
is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
In the test UE needs to be provided at least once every 1280ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furthermore UE sends scheduling
request (SR) to obtain allocation to send the measurement report on NPUSCH.
Table A.8.1.37.1-1: General test parameters for E-UTRAN FDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -16
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are
defined in Table A.8.1.37.1-3
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤325
T3 s 7
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1261 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.37.1-2: Cell specific test parameters for E-UTRAN FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1
Number
BW channel MHz 10
PDSCH Reference R.23 FDD N/A
Channel in clause
A.3.1.4.4
MPDCCH Reference R.19 FDD N/A
Channel in
clause A.3.1.3.4
OCNG Patterns defined in OP.21 FDD OP.2 FDD
A.3.2.1.10 (OP.10 FDD)
and in A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PHICH_RA dB -3 -3
PHICH_PB dB
MPDCCH_RA dB 0 0
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 -98
dB 8 8 8 -Infinity -3 -3
Ê s N oc
dB 8 6.24 6.24 -Infinity -11.64 -11.64
Ê s I ot
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
Io Note 3 dBm/9MHz -61.58 -61.29
-61.29 Specified in columns for Cell 1
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
PBCH repetition Configured as specified in TS
36.211 [16]
SIB1-BR repetition level - 16
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Table A.8.1.37.1-3: DRX configuration for E-UTRAN FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in CEModeB
Field Value Comment
onDurationTimer psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1262 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.37.1-4: TimeAlignmentTimer -Configuration for E-UTRAN FDD Intra-frequency
identification of a new CGI of E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in
CeModeB
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer Infinity
36.331
For further information see
sr-ConfigIndex 0 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
A.8.1.37.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 5120 ms from the start
of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_Cat M1, intra + reporting delay
= 15 + 5120 + 2ms from the start of T3
= 5137 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
A.8.1.38 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps for Cat-M1 UE in CEModeB
A.8.1.38.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.13.3.1.5.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.38.1-1 and A.8.1.38.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2 becomes detectable and the UE
is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
Table A.8.1.38.1-1: General test parameters for E-UTRAN HD - FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -16
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤325
T3 s 7
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1263 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.38.1-2: Cell specific test parameters for E-UTRAN HD - FDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps for Cat-M1 UE in CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH Reference R.13 HD-FDD N/A
Channel in clause
A.3.1.4.5
MPDCCH Reference R.9 HD-FDD N/A
Channel in
clause A.3.1.3.5
OCNG Patterns defined in OP.21 OP.21 OP.21 OP.2 OP.2 OP.2
A.3.2.1.10 (OP.10 FDD) FDD FDD FDD FDD FDD FDD
and in A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PHICH_RA dB -3 -3
PHICH_PB dB
MPDCCH_RA dB 0 0
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 -98
dB 8 8 8 -Infinity -3 -3
Ê s N oc
dB 8 6.24 6.24 -Infinity -11.64 -11.64
Ê s I ot
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
Io Note 3 dBm/9MHz -61.58 -61.29
-61.29 Specified in columns for Cell 1
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
PBCH repetition Configured as specified in TS
36.211 [16]
SIB1-BR repetition level 16
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.1.38.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 5137 ms from the start
of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_Cat M1, intra + reporting delay
= 15 + 5120 + 2ms from the start of T3
= 5137 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1264 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.1.39 E-UTRAN HD - FDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in
CEModeB
A.8.1.39.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.13.3.1.5. The requirement is verified in a DRX configuration.
The test scenario comprises of one E-UTRA FDD carrier and two cells as given in tables A.8.1.39.1-1 and A.8.1.39.1-2.
The test consists of three successive time periods, with time durations of T1, T2 and T3 respectively. At the start of time
duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2 becomes detectable and the UE
is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
In the test UE needs to be provided at least once every 1280ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furthermore UE sends scheduling
request (SR) to obtain allocation to send the measurement report on NPUSCH.
Table A.8.1.39.1-1: General test parameters for E-UTRAN HD - FDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in CEModeB
Parameter Unit Value Comment
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
Channel Bandwidth (BW channel) MHz 10
CP length Normal
A3-Offset dB -16
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are
defined in Table A.8.1.39.1-3
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤325
T3 s 7
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1265 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.39.1-2: Cell specific test parameters for E-UTRAN HD - FDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in CEModeB
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
PDSCH Reference DL Reference Measurement N/A
Channel as specified in Channel R.13 HD-FDD
clause A.3.1.4.5
MPDCCH Reference DL Reference Measurement N/A
Channel as specified in Channel R.9 HD-FDD
clause A.3.1.3.5
OCNG Patterns defined in OP.21 OP.21 OP.21 OP.2 OP.2 OP.2
A.3.2.1.10 (OP.10 FDD) FDD FDD FDD FDD FDD FDD
and in A.3.2.1.2 (OP.2
FDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PHICH_RA dB -3 -3
PHICH_PB dB
MPDCCH_RA dB 0 0
MPDCCH_PB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity -3 -3
Ê s N oc
dB 8 6.24 6.24 -Infinity -11.64 -11.64
Ê s I ot
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -101 -101
Io Note 3 dBm/9MHz -61.58 -61.29
-61.29 Specified in columns for Cell 1
Propagation Condition AWGN
Antenna Configuration 2x1 2x1
Timing offset to Cell 1 ms - 3
PBCH repetition - Configured as specified in TS
36.211 [16]
SIB1-BR repetition level - 16
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: Es/Iot, RSRP, SCH_RP and Io levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Table A.8.1.39.1-3: DRX configuration for E-UTRAN HD - FDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in CEModeB
Field Value Comment
onDurationTimer psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1266 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.1.39.1-4: TimeAlignmentTimer -Configuration for E-UTRAN HD - FDD Intra-frequency
identification of a new CGI of E-UTRA cell using autonomous gaps with DRX for Cat-M1 UE in
CEModeB
Field Value Comment
TimeAlignmentTimer Infinity As specified in clause 6.3.2 in TS 36.331
For further information see clause 6.3.2 in TS 36.331 and
sr-ConfigIndex 0
section10.1 in TS 36.213.
A.8.1.39.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 5137 ms from the start
of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI_Cat M1, intra + reporting delay
= 15 + 5120 + 2ms from the start of T3
= 5137 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
A.8.2 E-UTRAN TDD Intra-frequency Measurements
A.8.2.1 E-UTRAN TDD-TDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells
A.8.2.1.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event. This test will partly verify the TDD
intra-frequency cell search requirements in clause 8.1.2.2.2.1.
The test parameters are given in Table A.8.2.1.1-1 and A.8.2.1.1-2 below. In the measurement control information it is
indicated to the UE that event-triggered reporting with Event A3 is used. PDCCHs indicating new transmissions or
retransmissions shall be sent continuously to ensure that the UE would not enter the DRX state. The test consists of two
successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not have
any timing information of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1267 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.1.1-1: General test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Value Comment
DL Reference Measurement
PDSCH parameters Channel R.0 TDD As specified in clause A.3.1.1.2
DL Reference Measurement
PCFICH/PDCCH/PHICH Channel R.6 TDD As specified in clause A.3.1.2.2
parameters
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 One TDD carrier frequency is used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -6
CP length Normal
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211.
The same configuration in both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211.
The same configuration in both cells
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX DRX_L As specified in clause A.3.3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1268 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.1.1-2: Cell specific test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
OCNG Pattern defined
in A.3.2.2.1 (OP.1 OP.1 TDD OP.2 TDD
TDD) and in A.3.2.2.2
(OP.2)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 3 dBm/15 kHz -98
RSRP Note 4 dBm/15 kHz -94 -94 -Infinity -94
dB 4 -1.46 -Infinity -1.46
Ê s I ot
SCH_RP Note 4 dBm/15 kHz -94 -94 -Infinity -94
dB 4 4 -Infinity 4
Ê s N oc
Propagation Condition ETU70
Note 1 OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
A.8.2.1.2 Test Requirements
The UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than 800 ms
from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to 2xTTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1269 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.2.2 E-UTRAN TDD-TDD intra-frequency event triggered reporting under
fading propagation conditions in synchronous cells with DRX
A.8.2.2.1 Test Purpose and Environment
The purpose of the two tests is to verify that the UE makes correct reporting of an event in DRX. The tests will partly
verify the TDD-TDD intra-frequency cell search in DRX requirements in clause 8.1.2.2.1.2.
The test parameters are given in Tables A.8.1.3.1-1, A.8.1.3.1-2, A.8.1.3.1-3 and A.8.1.3.1-4. In the measurement
control information, it is indicated to the UE that event-triggered reporting with Event A3 is used. The test consists of
two successive time periods, with time duration of T1, and T2 respectively. During time duration T1, the UE shall not
have any timing information of cell 2.
In Test 1 UE needs to be provided at least once every 500ms with new Timing Advance Command MAC control
element to restart the Time aligment timer to keep UE uplink time alignment. Furhtermore UE is allocated with PUSCH
resource at every DRX cycle.
In Test 2 the uplink time aligment is not maintained and UE needs to use RACH to obtain UL allocation for
measurement reporting.
Table A.8.2.2.1-1: General test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Value Comment
Test 1 Test 2
DL Reference Measurement
PDSCH parameters Channel R.0 TDD As specified in clause A.3.1.1.2
DL Reference Measurement
PCFICH/PDCCH/PHICH Channel R.6 TDD As specified in clause A.3.1.2.2
parameters
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 One TDD carrier frequency is used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -6
CP length Normal
Special subframe configuration 6 As specified in table 4.2-1 in TS 36.211.
The same configuration in both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS 36.211.
The same configuration in both cells
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are defined in
Table A.8.2.2.1-3
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5 30
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1270 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.2.1-2: Cell specific test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under fading propagation conditions in synchronous cells when DRX is used
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
OCNG Pattern defined
in A.3.2.2.1 (OP.1 OP.1 TDD OP.2 TDD
TDD) and in A.3.2.2.2
(OP.2)
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
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 2 dBm/15 kHz -98
RSRP Note 3 dBm/15 kHz -94 -94 -Infinity -94
dB 4 -1.46 -Infinity -1.46
Ê s I ot
SCH_RP Note 3 dBm/15 kHz -94 -94 -Infinity -94
dB 4 4 -Infinity 4
Ê s N oc
Propagation Condition ETU70
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is
achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They
are not settable parameters themselves.
Table A.8.2.2.1-3: DRX-Configuration for E-UTRAN TDD-TDD intra-frequency event triggered
reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
onDurationTimer psf1 psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 psf1 36.331
drx-RetransmissionTimer psf1 psf1
longDRX-CycleStartOffset sf40 sf1280
shortDRX disable disable
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1271 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.2.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD-TDD intra-frequency event
triggered reporting in DRX under fading propagation conditions in synchronous cells
Test1 Test2 Comment
Field
Value Value
As specified in clause 6.3.2 in TS
TimeAlignmentTimer sf500 sf500
36.331
For further information see
sr-ConfigIndex 2 2 clause 6.3.2 in TS 36.331 and
clause 10.1 in TS 36.213.
A.8.2.2.2 Test Requirements
In Test 1, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
800 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE send the measurement report on PUSCH.
In Test 2, the UE shall send one Event A3 triggered measurement report, with a measurement reporting delay less than
25600 ms from the beginning of time period T2. The measurement reporting delay is defined as the time from the
beginning of time period T2 to the moment when the UE starts to send preambles on the PRACH for scheduling request
(SR) to obtain allocation to send the measurement report on PUSCH.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The actual overall delays measured in the test may be up to one DRX cycle higher than the measurement
reporting delays above because UE is allowed to delay the initiation of the measurement reporting procedure to the next
until the Active Time.
NOTE 2: In order to calculate the rate of correct events the system simulator shall verify that it has received correct
Event A3 measurement report.
A.8.2.3 E-UTRAN TDD - TDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps
A.8.2.3.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.1.2.2.4.
The test scenario comprises of one E-UTRA TDD carrier and two cells as given in tables A.8.2.3.1-1 and A.8.2.3.1-2.
PDCCHs indicating new transmissions shall be sent continuously to ensure that the UE would have ACK/NACK
sending during identifying a new CGI of E-UTRAN cell. The test consists of three successive time periods, with time
durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have any timing information
of cell 2. Starting T2, cell 2 becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1272 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.3.1-1: General test parameters for E-UTRAN TDD - TDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BWchannel) MHz 10
CP length Normal
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211. The same configuration in
both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211. The same configuration in
both cells
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
Time offset between cells μs 3 Synchronous cells
T1 s 5
T2 s ≤10
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1273 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.3.1-2: Cell specific test parameters for E-UTRAN TDD - TDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns defined in OP.1 OP.1 OP.1 OP.2 OP.2 OP.2
A.3.2.2.1 (OP.1 TDD) and TDD TDD TDD TDD TDD TDD
in A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ê s N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
A.8.2.3.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 170 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI, intra + reporting delay
= 15 + 150 + 2ms from the start of T3
= 167 ms, allow 170 ms.
The UE shall be scheduled continuously throughout the test, and from the start of T3 until 170 ms at least 47
ACK/NACK shall be detected as being transmitted by the UE.
The rate of correct events observed during repeated tests shall be at least 90%.
NOTE: The overall 47 ACK/NACK number is caused by two parts. Firstly, at least 35 ACK/NACK shall be sent
during identifying the cell global identifier of cell 2 according to the requirement for UL/DL
configuration #1 in Table 8.1.2.2.4.1-1 of Clause 8.1.2.2.4.1. Secondly, given that continuous DL data
allocation, additional 12 ACK/NACK shall be sent from the start of T3 until 170 ms excludes 150 ms for
identifying the cell global identifier of cell 2.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1274 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.2.4 E-UTRAN TDD - TDD Intra-frequency identification of a new CGI of
E-UTRA cell using autonomous gaps with DRX
A.8.2.4.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.1.2.2.4. The requirement is verified in a DRX configuration.
The test scenario comprises of one E-UTRA TDD carrier and two cells as given in tables A.8.2.4.1-1, A.8.2.4.1-2,
A.8.2.4.1-3 and A.8.2.4.1-4. The test consists of three successive time periods, with time durations of T1, T2 and T3
respectively. At the start of time duration T1, the UE does not have any timing information of cell 2. Starting T2, cell 2
becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
In the test UE needs to be provided at least once every 1280ms with new Timing Advance Command MAC control
element to restart the Time alignment timer to keep UE uplink time alignment. Furthermore UE sends scheduling
request (SR) to obtain allocation to send the measurement report on PUSCH.
Table A.8.2.4.1-1: General test parameters for E-UTRAN TDD - TDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps with DRX
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.6 TDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BWchannel) MHz 10
CP length Normal
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211. The same configuration in
both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211. The same configuration in
both cells
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX ON DRX related parameters are
defined in Table A.8.2.4.1-3
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
Time offset between cells μs 3 Synchronous cells
T1 s 5
T2 s ≤30 UE shall report cell within 25.6s
(20 DRX cycles)
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1275 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.4.1-2: Cell specific test parameters for E-UTRAN TDD - TDD Intra-frequency identification
of a new CGI of E-UTRA cell using autonomous gaps with DRX
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
OCNG Patterns defined in OP.1 OP.1 OP.1 OP.2 OP.2 OP.2
A.3.2.2.1 (OP.1 TDD) and TDD TDD TDD TDD TDD TDD
in A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB 0 0
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ê s N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
Table A.8.2.4.1-3: DRX configuration for E-UTRAN TDD - TDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps with DRX
Field Value Comment
onDurationTimer psf1 As specified in clause 6.3.2 in TS
drx-InactivityTimer psf1 36.331
drx-RetransmissionTimer psf1
longDRX-CycleStartOffset sf1280
shortDRX disable
Table A.8.2.4.1-4: TimeAlignmentTimer -Configuration for E-UTRAN TDD - TDD Intra frequency
identification of a new CGI of E-UTRA cell using autonomous gaps with DRX
Field Value Comment
As specified in clause 6.3.2 in TS
TimeAlignmentTimer Infinity
36.331
For further information see
sr-ConfigIndex 2 clause 6.3.2 in TS 36.331 and
section10.1 in TS 36.213.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1276 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.2.4.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 170 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tidentify_C GI, intra + reporting delay
= 15 + 150 + 2ms from the start of T3
= 167 ms, allow 170 ms.
The rate of correct events observed during repeated tests shall be at least 90%.
A.8.2.5 E-UTRAN TDD-TDD Intra-Frequency Event-Triggered Reporting
under Time Domain Measurement Resource Restriction with Non-
MBSFN ABS
A.8.2.5.1 Test Purpose and Environment
The purpose of this test is to verify that the UE correctly detects and reports Event A3 (Neighbour becomes offset better
than PCell) defined in TS 36.331 [2] within the requirements specified in Clause 8.1.2.8.2.1 under a time domain
measurement resource restriction and non-MBSFN ABS configured in the aggressor cell.
The test parameters are given in Tables A.8.2.5.1-1 and A.8.2.5.1-2 below. It is indicated to the UE in the measurement
control information that event-triggered reporting with Event A3 is used. In the test there are two synchronous cells,
Cell 1 and Cell 2, on the same RF channel. Cell 1 is the PCell, and it is also the aggressor cell to Cell 2. Cell 2 is the cell
to be identified. The test consists of two successive time periods with time duration of T1 and T2, respectively. During
time duration T1, the UE shall not have any timing information on Cell 2.
Non-MBSFN ABS pattern is configured for Cell 1 during the test. The UE is configured by higher layers via Cell 1
with a time domain measurement resource restriction pattern for performing E-UTRAN TDD intra-frequency
measurements on neighbour cells. The UE is also configured with a time domain measurement resource restriction
pattern for the PCell measurements. The information for both measurement patterns shall be provided to the UE via
higher layers during T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1277 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.5.1-1: General test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under time domain measurement resource restriction with non-MBSFN ABS
Parameter Unit Value Comment
DL Reference Measurement
PDSCH parameters Channel R.0 TDD As specified in clause A.3.1.1.2
DL Reference Measurement
PCFICH/PDCCH/PHICH Channel R.6 TDD As specified in clause A.3.1.2.2
parameters
PCell Cell 1 Also the aggressor cell. Active in T1 and T2
Neighbour cell Cell 2 Cell to be identified. Active only in T2.
PCell ABS configuration Non-MBSFN ABS As defined in Table A.3.4.1.1-1
E-UTRA RF Channel Number 1 One TDD carrier frequency is used.
Channel Bandwidth (BW channel) MHz 10
A3-Offset dB -11
Event A3 measurement quantity RSRP
CP length Normal
Special subframe configuration 6 As specified in Table 4.2-1 in TS 36.211. The
same configuration in both cells
Uplink-downlink configuration 1 As specified in Table 4.2-2 in TS 36.211. The
same configuration in both cells
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Time offset between cells 3 μs Synchronous cells
T1 s 5
T2 s 5
Physical cell ID PCI (PCIcell1 - PCIcell2 )mod6 != 0 Cell PCIs are selected so that the condition
is met
ABS pattern TDD ABS Pattern Info IE, as defined in TS
‘00000000010000000001’ 36.423 [28], clause 9.2.54. Configured in Cell
1 during T1.
The first/leftmost bit corresponds to the
subframe #0 of the radio frame satisfying
SFN mod x = 0, where x is the size of the bit
string (20) divided by 10. No MBSFN
subframes are cofigured in the ABS
subframes.
Time domain measurement Time domain measurement resource
resource restriction pattern for ‘00000000010000000001’ restriction pattern for neighbor cell
neighbour cell measurements measurement signalled to the UE in
on RF Channel 1 measSubframePattern-Neigh IE in
measSubframePatternConfig-Neigh, as
defined in TS 36.331, clause 6.3.5.
Configured during T1 for Cell 2
measurements.
Time domain measurement Configured during T1 for Cell 1
resource restriction pattern for ‘10000000001000000000’ measurements
PCell measurements
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1278 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.5.1-2: Cell specific test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under time domain measurement resource restriction with non-MBSFN ABS
Parameter Unit Cell 1 Cell 2
T1 T2 T1 T2
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 1x2 Low 1x2 Low
Antenna Configuration
OCNG Pattern defined
in A.3.2.2.1 (OP.1 OP.1 TDD OP.2 TDD
TDD) and in A.3.2.2.2
(OP.2)
PBCH_RA dB Non-ABS and ABS subframe
PBCH_RB dB channel powers defined in
PSS_RA dB Table A.3.4.1.1-1.
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB 0
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
N oc Note 3 dBm/15 kHz -98
dB 1 1 -Infinity -4
( Eˆ s / N oc ) meas Note 5
dB 1 1 N/A N/A
( Ês N oc )ABS
RSRP Note 4,5 dBm/15 kHz -97 -97 -Infinity -102
SCH_RP Note 4 dBm/15 kHz -97 -97 -Infinity -102
dB 1 -0.5 -Infinity -4
CRS Ê s I ot
dB 1 -0.5 -Infinity -7.5
SCH Ê s I ot
Propagation Condition ETU30
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
Note 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled. Applies to all subframes.
Note 4: RSRP and SCH_RP levels have been derived from other parameters for information purposes.
They are not settable parameters themselves.
Note 5: RSPP is estimated for Cell 2 during the restricted measurement subframes for neighbour cells.
RSPP is estimated for Cell 1 during the PCell restricted subframes.
A.8.2.5.2 Test Requirements
The UE shall send one Event A3 triggered measurement report for Cell 2, with a measurement reporting delay less than
1000 ms from the beginning of time period T2.
The UE shall not send event-triggered measurement reports as long as the reporting criteria are not fulfilled.
The rate of correct events observed during repeated tests shall be at least 90% for the tested Event A3.
NOTE: The actual overall delays measured in the tests may be up to 2×TTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1279 ETSI TS 136 133 V14.3.0 (2017-04)
A.8.2.6 E-UTRAN TDD-TDD Intra-Frequency Event-Triggered Reporting
under Time Domain Measurement Resource Restriction with CRS
Assistance Information and Non-MBSFN ABS
A.8.2.6.1 Test Purpose and Environment
The purpose of this test is to verify that the UE correctly detects and reports Event A3 (neighbour becomes offset better
than PCell) defined in TS 36.331 [2] within the requirements specified in Clause 8.1.2.8.4, when the UE is provided
with a time-domain measurement resource restriction pattern and CRS assistance information, and when non-MBSFN
ABS configured in the interfering cells.
The test parameters are given in Tables A.8.2.6.1-1 and A.8.2.6.1-2 below. It is indicated to the UE in the measurement
control information that event-triggered reporting with Event A3 is used. In the test, there are three synchronous cells,
Cell 1, Cell 2, and Cell 3, on the same RF channel. Cell 1 is the PCell. Cell 3 is the cell to be identified. A non-MBSFN
ABS pattern is configured in each of the Cell 1 and Cell 2 during the entire test.The test consists of two successive time
periods with time duration of T1 and T2, respectively. During time duration T1, the UE shall not have any timing
information on Cell 3.
The UE is configured by higher layers with a time domain measurement resource restriction pattern for performing E-
UTRAN TDD intra-frequency measurements on neighbour cells, nsamely Cell 3 measurements. The UE is also
provided via higher layers with the CRS assistance information for Cell 2. The information for both measurement
patterns and the CRS assistance information shall be provided via RRC to the UE during T1.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1280 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.6.1-1: General test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under time domain measurement resource restriction with CRS assistance information and
non-MBSFN ABS
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.2
Channel R.0 TDD
PCFICH/PDCCH/PHICH DL Reference Measurement As specified in clause A.3.1.2.2
parameters Channel R.6 TDD
PCell Cell 1 Also a first interfering cell to Cell 3.
Active in T1 and T2.
Neighbour cells Cell 2 and Cell 3 Cell 2 is a second interfering cell; Cell 2
is active in T1 and T2.
Cell 3 is the cell to be identified; Cell 3
is active only in T2.
ABS transmission configuration Non-MBSFN ABS As defined in Table A.3.4.1.1-1
E-UTRA RF Channel Number 1 One TDD carrier frequency is used
Channel Bandwidth (BW channel) MHz 10 For all cells in the test
A3-Offset dB -14
Event A3 measurement quantity RSRP
CP length Normal
Special subframe configuration 6 As specified in Table 4.2-1 in TS
36.211. The same configuration in both
cells
Uplink-downlink configuration 1 As specified in Table 4.2-2 in TS
36.211. The same configuration in both
cells
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
Time offset between cells μs Cell 2 offset with respect to Three synchronous cells
Cell 1: 0
Cell 3 offset with respect to
Cell 1: -2.5
T1 s 5
T2 s 5
(PCIcell1 - PCIcell3 )mod6 = 0 Cell PCIs are selected so that all
Physical cell IDs (PCIcell2 - PCIcell3 )mod6 != 0 conditions are met
PCIcell1 not equal to PCIcell3
TDD ABS Pattern Info IE, as defined in
TS 36.423 [28], clause 9.2.54.
The first/leftmost bit corresponds to the
Pcell subframe #0 of the radio frame
‘00000000010000000001’ satisfying SFN mod x = 0, where x is
ABS pattern
the size of the bit string (20) divided by
10. No MBSFN subframes are
configured in the ABS subframes.
Provided fto the UE for Cell 1 and Cell
2 during T1.
Time domain measurement resource
restriction pattern for neighbor cell
measurement signalled to the UE in
Time domain measurement measSubframePatternNeigh IE in
resource restriction pattern for measSubframePatternConfigNeigh, as
‘00000000010000000001’
neighbour cell measurements on defined in TS 36.331, clause 6.3.5.
RF Channel 1 Provided to the UE during T1 for Cell 3
measurements. The cell list in
measSubframeCellList IE shall contain
Cell 3 but not Cell 2.
Time domain measurement Configured during T1 for Cell 1
resource restriction pattern for ‘10000000001000000000’ measurements
PCell measurements
CRS physCellId see PCI conditions above The CRS assistance information is
assistance antennaPortsC provided for Cell 2 only in CRS-
information 1 AssistanceInfo. It includes a single
ount
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1281 ETSI TS 136 133 V14.3.0 (2017-04)
mbsfn- MBSFN-SubframeConfig element with
SubframeConfi oneFrame = ‘000000’ subframe allocation one
gList Frame=’000000’.
Table A.8.2.6.1-2: Cell specific test parameters for E-UTRAN TDD-TDD intra-frequency event triggered
reporting under time domain measurement resource restriction with CRS assistance information and
non-MBSFN ABS
Cell 1 Cell 2 Cell 3
Parameter Unit
T1 T2 T1 T2 T1 T2
E-UTRA RF Channel
1 1 1
Number
BW channel MHz 10 10 10
Correlation Matrix and 1x2 Low 1x2 Low 1x2 Low
Antenna Configuration
OCNG Patterns defined in
OP.2
A.3.2.2.1 (OP.1 TDD) and OP.1 TDD OP.2 TDD N/A
TDD
in A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
Non-ABS and ABS Non-ABS and ABS
PHICH_RA dB
subframe channel subframe channel
PHICH_RB dB N/A 0
powers defined in powers defined in
PDCCH_RA dB
Table A.3.4.1.1-1. Table A.3.4.1.1-1.
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dBm/15
N oc Note 3
kHz
-98
( Eˆ s / N oc ) dB 4 4 2 2 -Infinity -4
dBm/15
RSRP Note 4 -94 -94 -96 -96 -Infinity -102
kHz
dBm/15
SCH_RP Note 4 -94 -94 -96 -96 -Infinity -102
kHz
CRS Ê s I ot Note 5 dB 4 2.54 2 0.54 -Infinity -9.46
SCH Ê s I ot dB -0.12 -0.75 -3.45 -3.92 -Infinity -11.07
Propagation Condition ETU30 ETU30 ETU30
NOTE 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted power
spectral density is achieved for all OFDM symbols.
NOTE 2: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.
NOTE 3: Interference from other cells and noise sources not specified in the test is assumed to be constant
over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be
fulfilled. Applies to all subframes.
NOTE 4: RSRP, SCH_RP, and Ê s I ot levels have been derived from other parameters for information
purposes. They are not settable parameters themselves.
NOTE 5: Applies during the restricted measurement subframes configured for neighbour cell (Cell 3)
measurements.
A.8.2.6.2 Test Requirements
The UE shall send one Event A3 triggered measurement report for Cell 3, with a measurement reporting delay less than
1000 ms from the beginning of time period T2.
The UE shall not send event-triggered measurement reports as long as the reporting criteria are not fulfilled.
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1282 ETSI TS 136 133 V14.3.0 (2017-04)
The rate of correct events observed during repeated tests shall be at least 90% for the tested Event A3.
NOTE: The actual overall delays measured in the tests may be up to 2×TTIDCCH higher than the measurement
reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
A.8.2.7 E-UTRAN TDD Intra-frequency identification of a new CGI of E-
UTRA cell using autonomous gaps
A.8.2.7.1 Test Purpose and Environment
This test is to verify the requirement for identification of a new CGI of E-UTRA cell with autonomous gaps in
clause 8.5.2.1.6.
The test scenario comprises of one E-UTRA TDD carrier and two cells as given in tables A.8.2.7.1-1 and A.8.2.7.1-2.
PDCCHs indicating new transmissions should be sent continuously to ensure that the UE would have ACK/NACK
sending during identifying a new CGI of E-UTRAN cell. The test consists of three successive time periods, with time
durations of T1, T2 and T3 respectively. At the start of time duration T1, the UE does not have any timing information
of cell 2. Starting T2, cell 2 becomes detectable and the UE is expected to detect and send a measurement report.
A RRC message implying SI reading shall be sent to the UE during period T2, after the UE has reported Event A3. The
RRC message shall create a measurement report configuration with purpose reportCGI and si-RequestForHO set to
TRUE. The start of T3 is the instant when the last TTI containing the RRC message implying SI reading is sent to the
UE.
Table A.8.2.7.1-1: General test parameters for E-UTRAN TDD Intra-frequency identification of a new
CGI of E-UTRA cell using autonomous gaps
Parameter Unit Value Comment
PDSCH parameters DL Reference Measurement As specified in clause A.3.1.1.5
Channel R.13 TDD
PCFICH/PDCCH/PHICH parameters DL Reference Measurement As specified in clause A.3.1.2.2
Channel R.7 TDD
Active cell Cell 1
Neighbour cell Cell 2 Cell to be identified.
E-UTRA RF Channel Number 1 Only one TDD carrier frequency is
used.
Channel Bandwidth (BWchannel) MHz 10
CP length Normal
Special subframe configuration 6 As specified in table 4.2-1 in TS
36.211. The same configuration in
both cells
Uplink-downlink configuration 1 As specified in table 4.2-2 in TS
36.211. The same configuration in
both cells
A3-Offset dB -3
Hysteresis dB 0
Time To Trigger s 0
Filter coefficient 0 L3 filtering is not used
DRX OFF
si-RequestForHO TRUE As specified in clause 5.5.3.1 in
TS 36.331.
T1 s 5
T2 s ≤10
T3 s 5
ETSI
3GPP TS 36.133 version 14.3.0 Release 14 1283 ETSI TS 136 133 V14.3.0 (2017-04)
Table A.8.2.7.1-2: Cell specific test parameters for E-UTRAN TDD Intra-frequency identification of a
new CGI of E-UTRA cell using autonomous gaps
Parameter Unit Cell 1 Cell 2
T1 T2 T3 T1 T2 T3
E-UTRA RF Channel 1 1
Number
BW channel MHz 10 10
Correlation Matrix and 2x1 2x1
Antenna Configuration
OCNG Patterns defined in OP.1 OP.1 OP.1 OP.2 OP.2 OP.2
A.3.2.2.1 (OP.1 TDD) and TDD TDD TDD TDD TDD TDD
in A.3.2.2.2 (OP.2 TDD)
PBCH_RA dB
PBCH_RB dB
PSS_RA dB -3 -3
SSS_RA dB
PCFICH_RB dB 0 0
PHICH_RA dB -3 -3
PHICH_RB dB
PDCCH_RA dB 0 0
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB -3 -3
OCNG_RANote 1 dB
OCNG_RBNote 1 dB
dB 8 -3.3 -3.3 -Infinity 2.36 2.36
Ê s I ot
N oc Note 2 dBm/15 KHz -98
dB 8 8 8 -Infinity 11 11
Ê s N oc
RSRP Note 3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
SCH_RP Note3 dBm/15 KHz -90 -90 -90 -Infinity -87 -87
Propagation Condition AWGN
Timing offset to Cell 1 μs - 3
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral
density is achieved for all OFDM symbols.
Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over
subcarriers and time and shall be modelled as AWGN of appropriate power for N oc to be fulfilled.
Note 3: RSRP and SCH_RP levels have been derived from other parameters for information purposes. They are
not settable parameters themselves.
A.8.2.7.2 Test Requirements
The UE shall transmit a measurement report containing the cell global identifier of cell 2 within 210 milliseconds from
the start of T3.
Test requirement = RRC Procedure delay + Tide
You might also like
- Computer and Network Technology: BCS Level 4 Certificate in IT study guideFrom EverandComputer and Network Technology: BCS Level 4 Certificate in IT study guideNo ratings yet
- Etsi Ts 1 136 410: Technical Specification IONNo ratings yetEtsi Ts 1 136 410: Technical Specification ION17 pages
- TS 36.211 LTE Physical Channels and ModulationNo ratings yetTS 36.211 LTE Physical Channels and Modulation138 pages
- LTE Evolved Universal Terrestrial Radio Access E UTRA Physical Channels and Modulation 3GPP TS 36 211 Version 13 0 0 Release 13No ratings yetLTE Evolved Universal Terrestrial Radio Access E UTRA Physical Channels and Modulation 3GPP TS 36 211 Version 13 0 0 Release 1313 pages
- Ts - 136304v120200p - User Equipment (UE) Procedures in Idle Mode - 2014No ratings yetTs - 136304v120200p - User Equipment (UE) Procedures in Idle Mode - 201439 pages
- 3gpp Ts 24.301 Version 13.8.0 Release 13 Nas Protocol For EpsNo ratings yet3gpp Ts 24.301 Version 13.8.0 Release 13 Nas Protocol For Eps444 pages
- BTS 426 L1 Electrical Characteristics: Parameter and Conditions Symbol Values UnitNo ratings yetBTS 426 L1 Electrical Characteristics: Parameter and Conditions Symbol Values Unit1 page
- CCIE Data Center Nexus Switching: Overlay Transport Virtualization (OTV)0% (1)CCIE Data Center Nexus Switching: Overlay Transport Virtualization (OTV)6 pages
- NERC CIP Comparison Guide - ID vs. PassiveNo ratings yetNERC CIP Comparison Guide - ID vs. Passive3 pages
- Math - Cs - Students Study - Plan - G12 CS BOARD STUDY PLAN - 2025No ratings yetMath - Cs - Students Study - Plan - G12 CS BOARD STUDY PLAN - 20254 pages
- Which Amplifier Is Used To Provide Increased BandwidthNo ratings yetWhich Amplifier Is Used To Provide Increased Bandwidth10 pages
- 180-AIS Em-Trak A200 InstOper Manual 29-1-2018No ratings yet180-AIS Em-Trak A200 InstOper Manual 29-1-2018104 pages
- HCIE-Transmission V2.0 Version InstructionNo ratings yetHCIE-Transmission V2.0 Version Instruction3 pages
- S - R - Module - 1 Basic Device Configuration and Switching ConceptsNo ratings yetS - R - Module - 1 Basic Device Configuration and Switching Concepts77 pages
- Radar and Sensor Data Transport SolutionsNo ratings yetRadar and Sensor Data Transport Solutions24 pages