LTE Guidelines

November 22, 2017 | Author: Thanh Thao Nguyen | Category: Trademark, Radio Technology, Network Protocols, Telecommunications, Telecommunications Engineering
Share Embed Donate


Short Description

Good...

Description

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

LTE Parameter Setting Guidelines 80-W3835-1 Rev. A January 2013

Confidential and Proprietary – Qualcomm Global Services, Inc. Restricted Distribution: Not to be distributed to anyone who is not an employee of either Qualcomm or its subsidiaries without the express approval of Qualcomm’s Configuration Management. Not to be used, copied, reproduced, or modified in whole or in part, nor its contents revealed in any manner to others without the express written permission of Qualcomm Global Services, Inc. Qualcomm is a trademark of QUALCOMM Incorporated, registered in the United States and other countries. All QUALCOMM Incorporated trademarks are used with permission. Other product and brand names may be trademarks or registered trademarks of their respective owners. This technical data may be subject to U.S. and international export, re-export or transfer (“export”) laws. Diversion contrary to U.S. and international law is strictly prohibited. Qualcomm Technologies, Inc. 5775 Morehouse Drive San Diego, CA 92121 U.S.A.

© 2013 Qualcomm Technologies, Inc. All rights reserved.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Revision history Date

A

January 2013

Description Initial release

Released - For Current Employee/Consultant Use Only

Revision

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

2

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

Contents

1 Introduction .............................................................................................................. 11 1.1 1.2 1.3

Purpose .......................................................................................................................12 Outline .........................................................................................................................12 General Overview ........................................................................................................12 1.3.1 Band Classes ...................................................................................................13 1.3.2 Operating Bandwidth ........................................................................................14 1.4 Notation .......................................................................................................................15 1.5 Applicable Documents .................................................................................................17 1.5.1 Qualcomm Documents .....................................................................................17 1.5.2 External Specifications .....................................................................................17

2 Random Access Parameters ................................................................................... 18 2.1 2.2

Introduction ..................................................................................................................19 Physical Layer Parameters ..........................................................................................19 2.2.1 prach-FreqOffset ..............................................................................................19 2.2.2 prach-ConfigIndex ............................................................................................21 2.2.3 rootSequenceIndex ..........................................................................................23 2.2.4 NCS configuration (zeroCorrelationZoneConfig) ................................................ 24 2.2.5 highSpeedFlag .................................................................................................25 2.3 MAC Layer Parameters................................................................................................26 2.3.1 ra-PreambleIndex .............................................................................................26 2.3.2 numberOfRA-Preambles ..................................................................................27 2.3.3 sizeOfRA-PreamblesGroupA ............................................................................28 2.3.4 messageSizeGroupA........................................................................................30 2.3.5 messagePowerOffsetGroupB ...........................................................................31 2.3.6 ra-PRACH-MaskIndex ......................................................................................32 2.3.7 preambleInitialReceivedTargetPower ...............................................................33 2.3.8 powerRampingStep ..........................................................................................34 2.3.9 preambleTransMax...........................................................................................35 2.3.10 ra-ResponseWindowSize .................................................................................36 2.3.11 mac-ContentionResolutionTimer ......................................................................37 2.3.12 maxHARQ-Msg3Tx ..........................................................................................38

3 Cell Reselection Parameter Settings ....................................................................... 39 3.1

Intra-frequency Cell Reselection ..................................................................................42 3.1.1 Introduction ......................................................................................................42 3.1.2 Qrxlevmin ..............................................................................................................44 3.1.3 Sintrasearch ...........................................................................................................45 3.1.4 QHyst ..................................................................................................................46 3.1.5 Qoffsets,n...........................................................................................................47

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

3

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

3.2

3.3

3.4

3.5

3.6

3.7

3.8

3.9

Contents

3.1.6 TreselectionEUTRAN ............................................................................................48 Inter-frequency and Inter-RAT Cell Reselection Common Parameters ......................... 49 3.2.1 Cell Reselection Priority ...................................................................................49 3.2.2 Snonintrasearch ........................................................................................................50 3.2.3 Threshserving, low ..................................................................................................51 Inter-frequency Cell Reselection ..................................................................................52 3.3.1 TreselectionEUTRAN ............................................................................................52 3.3.2 Equal Priority Neighbor Inter-Frequency Reselection ....................................... 53 3.3.3 Higher Priority Neighbor Inter-Frequency Reselection ...................................... 56 3.3.4 Lower Priority Neighbor Inter-Frequency Reselection ....................................... 58 Inter-RAT Cell Reselection to UTRAN ..........................................................................60 3.4.1 Qqualmin ..............................................................................................................61 3.4.2 Qrxlevmin ..............................................................................................................62 3.4.3 TreselectionUTRA................................................................................................63 3.4.4 Higher Priority UTRAN Neighbor ......................................................................64 3.4.5 Lower Priority UTRAN Neighbor .......................................................................65 Inter-RAT Cell Reselection from UTRAN......................................................................66 3.5.1 Spriorityserach1 ........................................................................................................66 3.5.2 Spriorityserach2 ........................................................................................................67 3.5.3 QrxlevminEUTRA .............................................................................................68 3.5.4 Treselection ......................................................................................................69 3.5.5 Inter-RAT Scaling Factor for Treselection .........................................................70 3.5.6 Higher Priority E-UTRAN Neighbor...................................................................71 3.5.7 Lower Priority E-UTRAN Neighbor ...................................................................72 Inter-RAT Cell Reselection to GERAN .........................................................................74 3.6.1 Qrxlevmin ..............................................................................................................74 3.6.2 TreselectionGERA ...............................................................................................75 3.6.3 Higher Priority GERAN Neighbor ......................................................................76 3.6.4 Lower Priority GERAN Neighbor.......................................................................77 Inter-RAT Reselection from GERAN ............................................................................78 3.7.1 E-UTRAN_QRXLEVMIN...................................................................................78 3.7.2 T_reselection ....................................................................................................79 3.7.3 Higher Priority E-UTRAN Neighbor...................................................................80 3.7.4 Lower Priority E-UTRAN Neighbor ...................................................................81 Inter-RAT Cell Reselection to CDMA2000 ....................................................................84 3.8.1 Higher Priority CDMA2000 Neighbor ................................................................84 3.8.2 Lower Priority CDMA2000 Neighbor .................................................................85 Reselection Mobility States ..........................................................................................87 3.9.1 TCRmax ...............................................................................................................88 3.9.2 TCRmaxHyst ...........................................................................................................89 3.9.3 NCR_M ................................................................................................................90 3.9.4 NCR_H ................................................................................................................91 3.9.5 Qhyst Speed Dependant Scaling Factor: sf-High ................................................92 3.9.6 Qhyst Speed Dependant Scaling Factor: sf-Medium ........................................... 93 3.9.7 Treselection Speed Dependant Scaling Factor: sf-High .................................... 94 3.9.8 Treselection Speed Dependant Scaling Factor: sf-Medium .............................. 95

4 PHY DL Shared Channel Operation ........................................................................ 96 4.1

Antenna Info ................................................................................................................98

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

4

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Contents

4.1.1 AntennaPortsCount ..........................................................................................98 4.1.2 TransmissionMode ...........................................................................................99 4.1.3 CodebookSubsetRestriction ........................................................................... 101 4.2 PDSCH Configuration ................................................................................................103 4.2.1 ReferenceSignalPower ...................................................................................103 4.2.2 p-b ..................................................................................................................104 4.2.3 p-a ..................................................................................................................105

5 DL Scheduling Support – CQI/PMI/RI .................................................................... 106 5.1

Aperiodic CQI/PMI/RI Reporting on PUSCH .............................................................. 109 5.1.1 Cqi-ReportModeAperiodic .............................................................................. 109 5.2 Periodic CQI/PMI/RI Reporting on PUCCH ................................................................ 111 5.2.1 Introduction ....................................................................................................111 5.2.2 cqi-PUCCH-ResouceIndex ( 𝒏𝑷𝑼𝑪𝑪𝑯𝟐 ) ....................................................... 112 5.2.3 cqi-pmi-ConfigIndex (𝑵𝒑 and 𝑵𝑶𝑭𝑭𝑺𝑬𝑻, 𝑪𝑸𝑰)................................................ 113 5.2.4 cqi-FormatIndicatorPeriodic ............................................................................ 115 5.2.5 ri-ConfigIndex (𝑴𝑹𝑰 and 𝑵𝑶𝑭𝑭𝑺𝑬𝑻, 𝑹𝑰) ......................................................... 117 5.2.6 simultaneousAckNackAndCQI ........................................................................ 118 5.3 Others ........................................................................................................................119 5.3.1 nomPDSCH-RS-EPRE-Offset (𝚫𝑶𝒇𝒇𝒔𝒆𝒕) ....................................................... 119

6 Physical Uplink Shared Channel (PUSCH) ............................................................ 120 6.1

PUSCH frequency hopping ........................................................................................121 6.1.1 n-SB ...............................................................................................................122 6.1.2 hoppingMode..................................................................................................123 6.1.3 Pusch-HoppingOffset .....................................................................................124 6.2 PUSCH Modulation ....................................................................................................125 6.2.1 enable64QAM ................................................................................................127 6.3 PUSCH Demodulation Reference Signal ................................................................... 128 6.3.1 GroupHoppingEnabled ...................................................................................129 6.3.2 GroupAssignmentPUSCH (𝚫𝒔𝒔) ..................................................................... 131 6.3.3 SequenceHoppingEnabled .............................................................................132 6.3.4 CyclicShift ......................................................................................................133 6.4 Transmission of Control Signaling on PUSCH............................................................ 135 6.4.1 betaOffset-ACK-Index ....................................................................................135 6.4.2 betaOffset-RI-Index ........................................................................................137 6.4.3 betaOffset-CQI-Index .....................................................................................139

7 PUCCH, Uplink scheduling support SRS/SR & SPS ............................................. 141 7.1

Physical Uplink Control Channel (PUCCH) allocation ................................................ 142 7.1.1 deltaPUCCH-Shift (𝚫𝒔𝒉𝒊𝒇𝒕𝑷𝑼𝑪𝑪𝑯)................................................................ 145 7.1.2 nRB-CQI (𝑵𝑹𝑩(𝟐)) ........................................................................................146 7.1.3 nCS-AN (𝑵𝒄𝒔𝟏) ..............................................................................................147 7.1.4 n1-PUCCH-AN (𝑵𝑷𝑼𝑪𝑪𝑯𝟏) ........................................................................... 148 7.1.5 repetitionFactor (𝑵𝑨𝑵𝑹𝒆𝒑) ............................................................................. 150 7.1.6 n1Pucch-AN-Rep (𝒏𝑷𝑼𝑪𝑪𝑯, 𝑨𝑵𝑹𝒆𝒑𝟏) ........................................................... 151 7.2 Sounding Reference Signal........................................................................................152 7.2.1 srs-BandwidthConfig ......................................................................................152

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

5

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Contents

7.2.2 SRS-SubframeConfig .....................................................................................155 7.2.3 ackNackSRS-SimultaneousTransmission....................................................... 157 7.2.4 srs-Bandwidth.................................................................................................158 7.2.5 srs-HoppingBandwidth ...................................................................................159 7.2.6 freqDomainPosition ........................................................................................161 7.2.7 duration ..........................................................................................................162 7.2.8 srs-ConfigIndex ..............................................................................................163 7.2.9 transmissionComb ..........................................................................................165 7.2.10 cyclicShift .......................................................................................................166 7.3 Scheduling Request ...................................................................................................167 7.3.1 Sr-ConfigIndex ...............................................................................................167 7.3.2 Sr-PUCCH-ResourceIndex ............................................................................. 169 7.3.3 dsr-TransMax .................................................................................................170

8 Uplink Power Control Paramenter Settings............................................................ 171 8.1

PUSCH and SRS Power Control ................................................................................173 8.1.1 Introduction ....................................................................................................173 8.1.2 p0-NominalPUSCH (PO_NOMINAL_PUSCH(1)) ........................................................ 176 8.1.3 p0-NominalPUSCH-Persistent (𝑷𝑶_𝑵𝑶𝑴𝑰𝑵𝑨𝑳_𝑷𝑼𝑺𝑪𝑯(𝟎)) ........................... 177 8.1.4 alpha ..............................................................................................................178 8.1.5 p0-UE-PUSCH (PO_UE_PUSCH(1)) ...................................................................... 179 8.1.6 p0-UE-PUSCH-Persistent (𝑷𝑶_𝑼𝑬_𝑷𝑼𝑺𝑪𝑯(𝟎)) .............................................. 180 8.1.7 deltaPreambleMsg3 ( Δ PREAMBLE_Msg3 ) .............................................................. 181

8.1.8 deltaMCS-Enabled (Ks) .................................................................................. 182 8.1.9 accumulationEnabled .....................................................................................183 8.1.10 filterCoefficient................................................................................................185 8.1.11 pSRS-Offset (PSRS_OFFSET) ...............................................................................186 8.2 PUCCH Power Control...............................................................................................187 8.2.1 Introduction ....................................................................................................187 8.2.2 p0-NominalPUCCH (PO_NOMINAL_PUCCH) ............................................................ 188 8.2.3 p0-UE-PUCCH (PO_UE_PUCCH) .......................................................................... 189 8.2.4 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯𝑭 - Format 1)............................................ 190 8.2.5 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯𝑭 - Format 1b).......................................... 191 8.2.6 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯𝑭 - Format 2)............................................ 192 8.2.7 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯𝑭 - Format 2a).......................................... 193 8.2.8 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯𝑭 - Format 2b).......................................... 194

9 Handover Parameter Settings ................................................................................ 195 9.1

Handover Measurement Trigger ................................................................................199 9.1.1 S-Measure ......................................................................................................199 9.2 Intra-EUTRA Handover ..............................................................................................200 9.2.1 Intra-Frequency Handover .............................................................................. 200 9.2.2 Inter-Frequency Handover .............................................................................. 215 9.3 Inter-RAT Handover ...................................................................................................229 9.3.1 triggerType (Measurement Report Type) ....................................................... 230 9.3.2 Purpose ..........................................................................................................231 9.3.3 Gap Configuration ..........................................................................................232 9.3.4 Event A2.........................................................................................................233

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

6

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

9.3.5 9.3.6 9.3.7

Contents

Handover to UTRAN.......................................................................................239 Handover to GERAN ......................................................................................247 Handover to CDMA2000 ................................................................................254

Released - For Current Employee/Consultant Use Only

10 MAC Parameters ................................................................................................... 261 10.1 Introduction ................................................................................................................263 10.2 RACH Related MAC Layer Parameters ..................................................................... 264 10.2.1 ra-PreambleIndex (PRACH Preamble Index).................................................. 264 10.3 Logical Channel Related MAC Layer Parameters ...................................................... 265 10.3.1 Priority ............................................................................................................265 10.3.2 prioritisedBitRate ............................................................................................266 10.3.3 bucketSizeDuration ........................................................................................267 10.3.4 logicalChannelGroup ......................................................................................268 10.4 HARQ Related MAC Layer Parameter ....................................................................... 269 10.4.1 MaxHARQ-Tx .................................................................................................269 10.5 BSR Related MAC Layer Parameters ........................................................................ 270 10.5.1 periodicBSR-Timer .........................................................................................270 10.5.2 retxBSR-Timer................................................................................................271 10.6 PHR Related MAC Layer Parameters ........................................................................ 272 10.6.1 phr-Configuration ............................................................................................272 10.6.2 periodicPHR-Timer .........................................................................................273 10.6.3 prohibitPHR-Timer ..........................................................................................274 10.6.4 dl-PathLossChange ........................................................................................275 10.7 Connected State DRX Related MAC Parameters....................................................... 276 10.7.1 DRX-Config ....................................................................................................276 10.7.2 DRX-InactivityTimer........................................................................................277 10.7.3 onDurationTimer.............................................................................................278 10.7.4 drx-RetransmissionTimer................................................................................279 10.7.5 longDRX-CycleStartOffset ..............................................................................280 10.7.6 shortDRX........................................................................................................282 10.7.7 shortDRX-Cycle ..............................................................................................283 10.7.8 drxShortCycleTimer ........................................................................................284 10.8 Semi Persistent Scheduling .......................................................................................285 10.8.1 semiPersistSchedC-RNTI ...............................................................................286 10.8.2 semiPersistSchedIntervalDL ........................................................................... 287 10.8.3 numberOfConfSPS-Processes ....................................................................... 288 10.8.4 n1-PUCCH-AN-PersistentList ......................................................................... 289 10.8.5 semiPersistSchedIntervalUL ........................................................................... 290 10.8.6 implicitReleaseAfter ........................................................................................291 10.9 Other MAC Layer Parameters ....................................................................................292 10.9.1 ttiBundling ......................................................................................................292 10.9.2 timeAlignmentTimerDedicated ........................................................................ 293

11 Radio Link Control (RLC) Parameter Settings ....................................................... 294 11.1 Acknowledged Mode (AM) .........................................................................................295 11.1.1 t-PollRetransmit ..............................................................................................296 11.1.2 pollPDU ..........................................................................................................297 11.1.3 pollByte ..........................................................................................................298 11.1.4 maxRetxThreshold .........................................................................................299 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

7

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Contents

Released - For Current Employee/Consultant Use Only

11.1.5 t-Reordering(RLC-AM) ...................................................................................300 11.1.6 t-StatusProhibit ...............................................................................................301 11.2 Unacknowledged Mode (UM) .....................................................................................302 11.2.1 sn-FieldLength (UL-UM-RLC/DL-UM-RLC) .................................................... 302 11.2.2 t-Reordering (DL-UM-RLC).............................................................................304

12 Packet Data Convergence Protocol (PDCP) Parameter Settings .......................... 305 12.1 Reliable and In Sequence Delivery ............................................................................ 306 12.1.1 discardTimer...................................................................................................307 12.1.2 statusReportRequired.....................................................................................308 12.1.3 pdcp-SN-Size .................................................................................................309 12.2 Robust Header Compression .....................................................................................310 12.2.1 maxCID ..........................................................................................................310 12.2.2 profile0x0001 ..................................................................................................311 12.2.3 profile0x0002 ..................................................................................................312 12.2.4 profile0x0003 ..................................................................................................313 12.2.5 profile0x0004 ..................................................................................................314 12.2.6 profile0x0006 ..................................................................................................315 12.2.7 profile0x0101 ..................................................................................................316 12.2.8 profile0x0102 ..................................................................................................317 12.2.9 profile0x0103 ..................................................................................................318 12.2.10 profile0x0104 ..................................................................................................319 12.3 Security algorithm ......................................................................................................320 12.3.1 cipheringAlgorithm ..........................................................................................320 12.3.2 integrityProtAlgorithm .....................................................................................321

13 RRC Timers and Parameters ................................................................................. 322 13.1 Paging Timers ............................................................................................................323 13.1.1 defaultPagingCycle.........................................................................................323 13.1.2 nB...................................................................................................................324 13.2 RRC Connection Establishment Related Timers ........................................................ 326 13.2.1 T300 ...............................................................................................................326 13.2.2 T301 ...............................................................................................................327 13.3 RLF Related Timers ...................................................................................................328 13.3.1 T310 ...............................................................................................................329 13.3.2 N310 ..............................................................................................................330 13.3.3 N311 ..............................................................................................................332 13.3.4 T311 ...............................................................................................................333 13.4 Access Barring Related Timers and Parameters ........................................................ 334 13.4.1 T302 ...............................................................................................................334 13.4.2 T303 ...............................................................................................................335 13.4.3 T305 ...............................................................................................................335 13.4.4 ac-BarringTime ...............................................................................................336 13.4.5 ac-BarringFactor.............................................................................................337 13.4.6 ac-BarringForSpecialAC .................................................................................338 13.5 Cell Reselection and Handover Related Timers ......................................................... 339 13.5.1 T304 ...............................................................................................................339 13.5.2 T320 ...............................................................................................................340 13.5.3 T321 ...............................................................................................................341 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

8

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Contents

Released - For Current Employee/Consultant Use Only

Figures Figure 3-1 Intra-Frequency Cell Reselection Example............................................................................... 43 Figure 3-2 Inter-Frequency Reselection Example (equal priority neighbor) .............................................. 53 Figure 3-3 Inter-Frequency (or Inter-RAT) Reselection Example (Higher Priority Neighbor).................. 56 Figure 3-4 Inter-Frequency (or Inter-RAT) Reselection Example (Lower Priority Neighbor) .................. 58 Figure 6-1 A two-layered hopping/shifting pattern generation method.................................................... 129 Figure 6-2 Allocation examples of two-layered frequency hopping/shifting patterns.............................. 130 Figure 7-1. PUCCH .................................................................................................................................. 142 Figure 7-2. Mapping of PUCCH formats to PUCCH regions. ................................................................. 143 Figure 7-3. CQI channel structure for PUCCH format 2/2a/2b with normal CP for one slot................... 143 Figure 7-4. Channel structure for HARQ ACK/NACK formats 1a/1b. More RS (Reference Signals) are used to improve coherent detection. ......................................................................................................... 144 Figure 9-1 Event A3 entering and leaving conditions (assuming Ofn, Ocn, Ofs, Ocs = 0). .......... 207 Figure 13-1 RRC Recovery after Radio Link Failure is declared ............................................................. 328

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

9

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Contents

Released - For Current Employee/Consultant Use Only

Tables Table 1-1. Band Classes for LTE ................................................................................................................ 14 Table 1-2. Operating Bandwidths for LTE ................................................................................................. 14 Table 5-1 CQI and PMI Feedback Types for PUSCH reporting Modes .................................................. 110 Table 5-2 Mapping of cqi-pmi-ConfigIndex to NP and NOFFSET,CQI for FDD. ............................................ 114 Table 5-3 CQI and PMI Feedback Types for PUCCH reporting Modes .................................................. 116 Table 5-4 Mapping of ri-ConfigIndex to MRI and NOFFSET,RI. .................................................................... 117 Table 6-1 Modulation, TBS index and redundancy version table for PUSCH ......................................... 126 ( 2) Table 6-2 Mapping of Cyclic Shift Field in DCI format 0 to n DMRS Values. ........................................... 134

Table 6-3 Mapping of cyclicShift to n (1) Values. .................................................................................. 134 DMRS Table 6-4 Mapping of HARQ-ACK offset values and the index signaled by higher layers..................... 136 Table 6-5 Mapping of RI offset values and the index signalled by higher layers..................................... 138 Table 6-6 Mapping of CQI offset values and the index signalled by higher layers .................................. 140 Table 7-1. UCI formats for PUCCH...................................................................................................... 143 Table 7-2. Value of TPC command for PUCCH ..................................................................................... 149 UL Table 7-3. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 6 ≤ N RB ≤ 40 . ................. 153 UL Table 7-4. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 40 < N RB ≤ 60 . ....... 153

UL Table 7-5. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 60 < N RB ≤ 80 . ........ 154 UL Table 7-6. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 80 < N RB ≤ 110 . ...... 154

Table 7-7. FDD sounding reference signal subframe configuration ......................................................... 156 Table 7-8. UE Specific SRS Periodicity TSRS and Subframe Offset Configuration Toffset ........................ 164 Table 7-9. UE-specific SR periodicity and subframe offset configuration ............................................... 168 Table 8-1 Mapping of TPC Command Field in DCI format 0/3 to absolute and accumulated δ PUSCH values. ....................................................................................................................................................... 184 Table 8-2 Mapping of TPC Command Field in DCI format 3A to δ PUSCH values.................................... 184

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

10

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

1 Introduction

2

Chapter 1: Table of Contents

3

1.1 Purpose .................................................................................................................................................... 12

4

1.2 Outline ..................................................................................................................................................... 12

5

1.3 General Overview .................................................................................................................................. 12

6

1.3.1 Band Classes ........................................................................................................................................ 13

7

1.3.2 Operating Bandwidth......................................................................................................................... 14

8

1.4 Notation................................................................................................................................................... 15

9

1.5 Applicable Documents .......................................................................................................................... 17

10

1.5.1 Qualcomm Documents....................................................................................................................... 17

11

1.5.2 External Specifications ....................................................................................................................... 17

12 13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

11

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

1.1 Purpose

6

This document provides guidelines and recommendations for setting key LTE parameters. Most of these parameters are signaled to the UE either via the system information blocks, or via dedicated channel signaling. The emphasis is on parameters which impact system performance and therefore require optimization during trials, pre-commercial testing, and possibly during commercial operation. E-UTRAN implementation-specific parameters are not covered.

7

The Appendix includes a list of abbreviations and definitions.

8

This document is based upon 3GPP Release 8 E-UTRA specifications.

9

1.2 Outline

2 3 4

Released - For Current Employee/Consultant Use Only

Introduction

5

10

A standard template is used for each parameter, or information element, as follows:

11

Definition: Brief explanation of the purpose of the parameter IE Value

12 13 14 15 16 17 18 19

Engineering Units

Allowed Range

Permitted range of parameter as determined by the standard, incl. step size if applicable

Permitted range in regular engineering units (e.g. dB), incl. step size if applicable

Recommended

See note below

See note below

Recommended Setting: A reasonably narrow range of values beyond which the parameter should not normally be set. This range is the set of values over which this parameter should be optimized. The range can be a single value, in which case optimization is not needed or recommended. The recommended setting is given in implementation units as given in the standard and in engineering units. Setting Tradeoff: A brief description of the tradeoffs involved in the setting of this parameter, providing an explanation of the effects of setting it “too high” and “too low”, beyond the recommended range.

21

Dependencies/constraints: When applicable, an explicit reference is made to other information elements whose setting may affect the setting of this parameter.

22

Traceability: List of all applicable standards, with reference to specific section number.

20

24

RRC Message Structure: The Information Elements (IE) and RRC messages containing the parameter.

25

Notes: Any other comments and additional information about the parameter.

26

1.3 General Overview

23

27 28 29 30 31

In an LTE network, parameters are communicated to the UE over the air via System Information Block (SIBs) and dedicated messages. Upon system acquisition, which provides the UE with symbol/sub-frame and frame timing information as well as physical Cell ID, the UE gathers key configuration information contained in the Master Information Block (MIB) which is broadcasted on the Physical Broadcast channel (PBCH) 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

12

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3 4

Released - For Current Employee/Consultant Use Only

5 6 7

Introduction

with a 40ms periodicity. After decoding PBCH/MIB, UE has knowledge about cell’s System Frame Number, Cell’s DL transmission bandwidth, PHICH configuration and, indirectly, Number of transmission antennas available for that cell. With this information, UE decodes PCFICH UE to identify the control region used for Physical Downlink Control Channel (PDCCH) so that scheduling transmissions for the Physical Downlink Shared Channel (PDSCH) can be monitored. This enables the UE to read the complete System Information Blocks (SIB1 through SIB11) which, will rule UE behavior while operating in the LTE network.

19

SIB1 brings information required by the UE to camp in a specific cell and the scheduling information for the remaining SIBs. These are broadcast in System Information (SI) messages, each of which can contain multiple SIBs. Whereas the scheduling of the MIB and SIB1 transmissions is fixed at 40 ms and 80ms, respectively, the scheduling of any additional system broadcast can vary and is specified in the SIB1 message along with how different SIB are multiplexed within each SI. SIBs 2 and 3 contain general parameters related to access and reselection and define the configuration of the LTE cell on which the UE is camped and when the UE should search for other cells for reselection. SIBs 4, 5, 6, 7 and 8 contain information related to neighbor cells. Information for intra- and inter-frequency neighbor cells is defined in SIBs 4 and 5, respectively whilst Inter-RAT neighbor information is contained in SIBs 6, 7, and 8 for UTRA, GERAN, and CDMA2000, respectively. SIB9 contains information enabling the support of Home eNB, and SIBs 10 and 11 contain information related to Earthquake and Tsunami warnings, as defined by 23.041 and 36.413.

20

1.3.1

8 9 10 11 12 13 14 15 16 17 18

21 22

Band Classes

The band classes for LTE are given in Table 1-1. The raster is 100 kHz. A LTE UE may support operation in one or more band classes.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

13

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

Table 1-1. Band Classes for LTE E-UTRA Band

Released - For Current Employee/Consultant Use Only

Introduction

Uplink (UL) BS receive UE transmit FUL_low – FUL_high 1920 MHz – 1980 MHz 1850 MHz – 1910 MHz 1710 MHz – 1785 MHz 1710 MHz – 1755 MHz 824 MHz – 849 MHz 830 MHz – 840 MHz 2500 MHz – 2570 MHz 880 MHz – 915 MHz 1749.9 MHz – 1784.9 MHz 1710 MHz – 1770 MHz 1427.9 MHz – 1452.9 MHz 698 MHz – 716 MHz 777 MHz – 787 MHz 788 MHz – 798 MHz

1 2 3 4 5 6 7 8 9 10 11 12 13 14 … 17 ... 33 34 35 36 37 38 39 40

704 MHz 1900 2010 1850 1930 1910 2570 1880 2300

MHz MHz MHz MHz MHz MHz MHz MHz



716 MHz

– – – – – – – –

1920 2025 1910 1990 1930 2620 1920 2400

MHz MHz MHz MHz MHz MHz MHz MHz

Downlink (DL) BS transmit UE receive FDL_low – FDL_high 2110 MHz – 2170 MHz 1930 MHz – 1990 MHz 1805 MHz – 1880 MHz 2110 MHz – 2155 MHz 869 MHz – 894 MHz 875 MHz – 885 MHz 2620 MHz – 2690 MHz 925 MHz – 960 MHz 1844.9MHz – 1879.9 MHz 2110 MHz – 2170 MHz 1475.9MHz – 1500.9 MHz 728 MHz – 746 MHz 746 MHz – 756 MHz 758 MHz – 768 MHz 734 MHz 1900 2010 1850 1930 1910 2570 1880 2300

MHz MHz MHz MHz MHz MHz MHz MHz

Duplex Mode FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD



746 MHz

FDD

– – – – – – – –

1920 2025 1910 1990 1930 2620 1920 2400

TDD TDD TDD TDD TDD TDD TDD TDD

MHz MHz MHz MHz MHz MHz MHz MHz

2

3

1.3.2

Operating Bandwidth

5

Note that LTE can operate with different bandwidths on the UL and DL. Table 1-2 lists the signaling variables that determine the operating bandwidths for LTE.

6

Table 1-2. Operating Bandwidths for LTE

4

Parameter Downlink bandwidth Uplink bandwidth

DL N RB

UL N RB

Size [bits]

Where Sent

Rate of Change

Neighbor Cell

4

Broadcast (MIB)

Low

Typically same

4

Broadcast (SIB)

Low

Typically same

7 8

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

14

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

1.4 Notation (k , l )

3

Released - For Current Employee/Consultant Use Only

Introduction

Resource element with frequency-domain index k and time-domain index l Value of resource element (k , l ) [for antenna port p ]

4

a k( ,pl )

5

D

6

DRA

Matrix for supporting cyclic delay diversity Density of random access opportunities per radio frame

7

f0

Carrier frequency

8

f RA

14

(q) M bit

PRACH resource frequency index within the considered time domain location Scheduled bandwidth for uplink transmission, expressed as a number of subcarriers Scheduled bandwidth for uplink transmission, expressed as a number of resource blocks Number of coded bits to transmit on a physical channel [for code word q ]

15

(q) M symb

Number of modulation symbols to transmit on a physical channel [for

9 10

M scPUSCH

11 12

PUSCH M RB

13

code word q ]

16 17

layer M symb

Number of modulation symbols to transmit per layer for a physical

ap M symb

channel Number of modulation symbols to transmit per antenna port for a

N N CP ,l

physical channel A constant equal to 2048 for ∆f = 15 kHz and 4096 for ∆f = 7.5 kHz Downlink cyclic prefix length for OFDM symbol l in a slot

18 19 20 21 22 23

N cs(1)

24 25

(2) N RB

Number of cyclic shifts used for PUCCH formats 1/1a/1b in a resource block with a mix of formats 1/1a/1b and 2/2a/2b Bandwidth reserved for PUCCH formats 2/2a/2b, expressed in multiples of N scRB

26

29

cell N ID

Number of resource blocks in a slot used for PUCCH transmission (set by higher layers) Physical layer cell identity

30

MBSFN N ID

MBSFN area identity

DL N RB min, DL N RB

Downlink bandwidth configuration, expressed in multiples of N scRB

27

PUCCH N RB

28

31 32

Smallest downlink bandwidth configuration, expressed in multiples of RB N sc

33 34

max, DL N RB

Largest downlink bandwidth configuration, expressed in multiples of N scRB

35

UL N RB

Uplink bandwidth configuration, expressed in multiples of N scRB

36

min, UL N RB

Smallest uplink bandwidth configuration, expressed in multiples of N scRB

37

max, UL N RB

Largest uplink bandwidth configuration, expressed in multiples of N scRB

38

DL N symb

Number of OFDM symbols in a downlink slot

39

UL N symb

Number of SC-FDMA symbols in an uplink slot

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

15

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

3

N SP

Resource block size in the frequency domain, expressed as a number of subcarriers Number of downlink to uplink switch points within the radio frame

4

PUCCH N RS

Number of reference symbols per slot for PUCCH

5

N TA

Timing offset between uplink and downlink radio frames at the UE,

7

N TA offset

expressed in units of Ts Fixed timing advance offset, expressed in units of Ts

8

(1) nPUCCH

Resource index for PUCCH formats 1/1a/1b

9

( 2) nPUCCH

Resource index for PUCCH formats 2/2a/2b

10

nPDCCH

Number of PDCCHs present in a subframe

11

nPRB

Physical resource block number

1

RB N sc

2

Released - For Current Employee/Consultant Use Only

Introduction

6

12 13 14 15 16 17 18 19 20 21 22 23 24

n n

RA PRB RA PRB offset

nVRB nRNTI nf ns P p q

rRA

Qm

sl( p ) (t )

27 28

t t t

0 RA 1 RA 2 RA

29 30 31 32 33 34 35 36 37 38 39 40

First physical resource block available for PRACH Virtual resource block number Radio network temporary identifier System frame number Slot number within a radio frame Number of cell-specific antenna ports Antenna port number Code word number Index for PRACH versions with same preamble format and PRACH density Modulation order: 2 for QPSK, 4 for 16QAM and 6 for 64QAM transmissions Time-continuous baseband signal for antenna port p and OFDM symbol l in a slot

25 26

First physical resource block occupied by PRACH resource considered

Tf Ts Tslot W

β PRACH β PUCCH β PUSCH β SRS ∆f ∆f RA

υ

Radio frame indicator index of PRACH opportunity Half frame index of PRACH opportunity within the radio frame Uplink subframe number for start of PRACH opportunity within the half frame Radio frame duration Basic time unit Slot duration Precoding matrix for downlink spatial multiplexing Amplitude scaling for PRACH Amplitude scaling for PUCCH Amplitude scaling for PUSCH Amplitude scaling for sounding reference symbols Subcarrier spacing Subcarrier spacing for the random access preamble Number of transmission layers

41

42

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

16

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Introduction

1

1.5 Applicable Documents

2

1.5.1

Qualcomm Documents

3

1.5.2

External Specifications

4 5

[1] 36.211 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation

7

[2] 36.212 Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding

8

[3] 36.213 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures

6

9 10 11 12 13 14 15 16 17 18

[4] 36.321 Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification [5] 36.322 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification [6] 36.323 Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification [7] 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification [8] 36.304 Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

17

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

2 Random Access Parameters

2

Chapter 2: Table of Contents

3

2.1 Introduction ............................................................................................................................................ 19

4

2.2 Physical Layer Parameters.................................................................................................................... 19

5

2.2.1 prach-FreqOffset ................................................................................................................................. 19

6

2.2.2 prach-ConfigIndex .............................................................................................................................. 21

7

2.2.3 rootSequenceIndex.............................................................................................................................. 23

8

2.2.4 NCS configuration (zeroCorrelationZoneConfig).......................................................................... 24

9

2.2.5 highSpeedFlag ..................................................................................................................................... 25

10

2.3 MAC Layer Parameters ......................................................................................................................... 26

11

2.3.1 ra-PreambleIndex................................................................................................................................ 26

12

2.3.2 numberOfRA-Preambles ................................................................................................................... 27

13

2.3.3 sizeOfRA-PreamblesGroupA ............................................................................................................ 28

14

2.3.4 messageSizeGroupA........................................................................................................................... 30

15

2.3.5 messagePowerOffsetGroupB ............................................................................................................ 31

16

2.3.6 ra-PRACH-MaskIndex ....................................................................................................................... 32

17

2.3.7 preambleInitialReceivedTargetPower ............................................................................................. 33

18

2.3.8 powerRampingStep ............................................................................................................................ 34

19

2.3.9 preambleTransMax ............................................................................................................................. 35

20

2.3.10 ra-ResponseWindowSize ................................................................................................................. 36

21

2.3.11 mac-ContentionResolutionTimer ................................................................................................... 37

22

2.3.12 maxHARQ-Msg3Tx .......................................................................................................................... 38

23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

18

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2.1 Introduction

2

The random access procedure is initiated by the UE in the following scenarios: -

At initial network access (UE wants to access the network in order to establish RRC Connection)

-

To send a scheduling request (in case there is no dedicated PUCCH resource configured for scheduling request)

-

To establish uplink synchronization when uplink or downlink data arrives in RRC connected state and the uplink is not yet synchronized

9

-

At handover (so the target eNB can measure uplink timing)

10

-

After radio link failure (so the radio link can be re-established)

3 4

Released - For Current Employee/Consultant Use Only

Random Access Parameters

5 6 7 8

14

The random access procedure is triggered by the RRC layer. It involves MAC and physical layer procedures and makes use of the RACH uplink transport channel mapped to the PRACH uplink physical channel. Since the random access procedure carries only limited control information, there is no logical channel associated to this procedure.

15

2.2 Physical Layer Parameters

11 12 13

17

The physical layer procedure consists of transmitting a random access preamble (msg1) on the PRACH uplink channel, and receiving a random access response (msg2) on PDCCH/PDSCH.

18

On the physical layer, the PRACH uplink channel is used to send the random access preamble.

16

19 20 21 22 23 24 25 26 27 28 29 30 31

In the frequency domain, PRACH has 6 PRBs allocated (regardless of the system bandwidth) with a position depending on the system configuration (prach-FreqOffset). In the time domain, PRACH can be allocated to one or more sub-frames which depends on the system configuration (prachConfigIndex). Note that the eNB is not prohibited to schedule PUSCH in the time-frequency resources allocated for PRACH. The random access preamble is a Zadoff-Chu sequence which makes it possible for the eNB to differentiate between UEs and calculate uplink timing. Each LTE cell has a set of 64 available sequences derived from the cell specific root sequence(s) (rootSequenceIndex) via cyclic shifting. A group of the sequences may be reserved for contention free procedure; the rest can be used for contention based random access. The contention based subset can actually be divided into two groups A and B. Letting the UE chose one preamble from either group based on UL granting requirements to hint the eNB about its next UL transmission requirements.

33

The random access preamble has a cyclic prefix appended. Duration of the cyclic prefix and of the random access sequence is configurable.

34

2.2.1

35

Definition: Index of the first physical resource block (PRB) allocated for PRACH

32

prach-FreqOffset

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

19

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

IE Value

Allowed Range

Released - For Current Employee/Consultant Use Only

Recommended

1

Engineering Units

𝑈𝐿 0 … 𝑁𝑅𝐵 -6

𝑈𝐿 0 … 𝑁𝑅𝐵 - 6 physical resource blocks

1 (5 MHz)

1 RB (5 MHz)

2-3 (10 MHz)

2-3 RB (10 MHz)

Setting Tradeoff: n/a

3

Dependencies/Constraints: Parameter is restricted by the UL system bandwidth and PUCCH configuration.

4

Traceability: TS36.211 Sect. 5.7.1

5

RRC Message Structure:

2

6 7 8 9 10

SIB2  RadioResourceConfigCommon  PRACH-Config  PRACH-ConfigInfoprachFreqOffset. Notes: In the frequency domain PRACH has always 6 PRBs allocated, regardless of the UL system bandwidth (𝑁𝑈𝐿 𝑅𝐵 , which is the UL system bandwidth expressed in RBs).

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

20

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

2.2.2

Random Access Parameters

prach-ConfigIndex

Definition: Determines preamble format: a) Prach cyclic prefix duration, b) preamble sequence length. It also defines PRACH resource allocation in the time domain (system frame(s) and subframe(s)) IE Value

[0 … 63]

Engineering Units

For mapping see TS36.211 Table 5.7.1-2 Preamble format: Format 0, 1, 2 or 3

Allowed Range

System frame: Even or Any Subframe: 1, 2, 3 or 5 selected subframes or 10 subframes

Recommended 5

6

-

Preamble format: use of PRACH long cyclic prefix duration is beneficial for large cells (where larger delay spreads are expected), but it may cause un-necessary overhead for a small cell size deployments. Use of long preamble sequence makes access preamble reception transmission more robust but occupies certain part of the consecutive subframe.

-

PRACH resource allocation - the time domain: If too few time resources are allocated, random access occasions will be infrequent, causing delays in starting the random access procedure. This will result in longer call set up times and handover execution times. If too many time resources are allocated then there will be more chances that the PRACH may collide with PUSCH, and it may lead to lower throughput.

-

Set the PRACH Configuration Index to 3,4,5 for three cells of any site to minimize PRACH to PRACH interference. The implicit corresponding preamble format is Format 0.

8 9

11 12 13 14 15

16 17

3, 4, 5

Setting Tradeoff (see notes also notes):

7

10

3, 4, 5

18

Dependencies/Constraints: None.

19

Traceability: TS36.211 Sect. 5.7.1

20

RRC Message Structure:

21 22

SIB2  RadioResourceConfigCommon  PRACH-Config  PRACH-ConfigInfoprachConfigIndex.

23 24 25

Notes: The random access preamble is composed of a cyclic prefix and a sequence part. Preamble format is defining the length of each part, as described in TS36.211 Sect. 5.7.1:

26

80-W3835-1 Rev. A

Cyclic prefix

Sequence

TCP

TSEQ

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

21

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

Released - For Current Employee/Consultant Use Only

1

2 3 4 5 6

Preamble Format

TCP

TSEQ

0

3168 TS

24576 TS

1

21024 TS

24576 TS

2

6240 TS

2x24576 TS

3

21024 TS

2x24576 TS

Where Ts = 1/(15000 x 2048) seconds is the basic time unit. Note that for formats 1, 2 and 3 TCP+TSEQ > 1 ms resulting the preamble ending out of the sub-frame. Also, due to propagating delay the preamble may end out of the sub-frame even for format 0 which is shorter than 1 ms. It is up to the eNB implementation to handle this either via not scheduling PUSCH in the consecutive subframe or to schedule PUSCH and to cope with the interference.

7 8

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

22

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.2.3

rootSequenceIndex

2

Definition: Index of the physical Zadoff-Chu root sequence to be used for PRACH in the cell

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

[0 … 837]

Recommended

Variable (Each cell should have individual root sequence(s).

Engineering Units

For mapping see TS36.211 Table 5.7.2-4

3

Setting Tradeoff: n/a

4

Dependencies/Constraints: None.

5

Traceability: TS36.211 Sect. 5.7.2

6

RRC Message Structure:

7

SIB2  RadioResourceConfigCommon  PRACH-Config  rootSequenceIndex

8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

Notes: The RACH Root Sequence (sometimes also referred to as Logical Root Sequence Index or Logical Root Sequence Number) is mapped to a Physical Root Sequence Number. Each LTE cell has one root sequence assigned. In order to differentiate UEs sending random access preambles at the same time, there are 64 different preamble sequences available in the cell. The 64 preamble sequences are derived as cyclic shifts of the Zadoff-Chu root sequence assigned to the cell. In case the 64 preambles can not be generated from a single root sequence due to larger zero correlation zone setting (see parameter zeroCorrelationZoneConfig), further sequences will be generated as cyclic shifts of the next root sequence. The degree of orthogonalitly of preamble sequences obtained from different root sequences is deteriorated. The algorithm for performing the cyclic shifting is described in TS36.211 Sect. 5.7.2. It is making use of two configuration parameters: Ncs and the High-Speed-Flag (for explanation of these parameters see the respective section). Each cell should have individual root sequence value to use the Zadoff-Chu cross-correlation properties.

23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

23

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.2.4

NCS configuration (zeroCorrelationZoneConfig)

2

Definition: Parameter used to calculate cyclic shifts of the root Zadoff-Chu sequence in the cell

Released - For Current Employee/Consultant Use Only

IE Value

3 4 5 6 7 8 9 10 11 12 13

Allowed Range

[0 … 15]

Recommended

12*

Engineering Units

For mapping see TS36.211 Table 5.7.2-2

Setting Tradeoff: For large Ncs settings, a larger cyclic shift of the ZC sequence is expected. This is efficient for larger coverage and larger delay spreads, but reduces the total number of available preamble sequences available in a cell and hence enforces the use of additional root sequence(s) which result in the loss of degree of the orthogonality between the root sequence families. The other way around, i.e the smaller Ncs, will have the contrary effect as the one described above. Dependencies/Constraints: *The corresponding recommended 𝑁𝐶𝑆 value 𝑁𝐶𝑆 = 119 for unrestricted set is based on a 15 km cell size that determines propagation delay and a maximum delay spread. As results, ⌊839/119⌋ = 7 preambles per root sequence can be generated and 10 root sequences are needed to produce 64 preambles. For restricted set, the corresponding recommended value 𝑁𝐶𝑆 = 119 = 158. ⌊839/158⌋ = 5 preambles per root sequence can be generated and 13 root sequences are needed to produce 64 preambles.

14 15

Traceability: TS36.211 Sect. 5.7.2

16

RRC Message Structure:

17 18 19 20 21

SIB2  RadioResourceConfigCommon  PRACH-Config  PRACH-ConfigInfo  zeroCorrelationZoneConfig Notes: The Zero Correlation Zone Config (NCS configuration) value is an index, which maps to an NCS value. The mapping is different for restricted and unrestricted set (see the parameter High Speed Flag).

24

The Ncs value is used to calculate the cyclic shift (CV) to generate the Zadoff-Chu preamble sequence. The cyclic shift to be applied is CV = v*NCS where v = 0 … 63 describes the preamble index (see description under PRACH Preamble Index).

25

Note that NCS value has an impact of the cell size.

22 23

26

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

24

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

2.2.5

Random Access Parameters

highSpeedFlag

Definition: Defines the use of restricted sets of cyclic shifts of the Zadoff-Chu root sequence used for high speed moving UEs. IE Value

Allowed Range Recommended

4 5 6 7

Engineering Units

BOOLEAN

TRUE, FALSE

TRUE if in high-speed mobility,

TRUE if in high-speed mobility,

FALSE otherwise

FALSE otherwise

Setting Tradeoff: If the parameter is set to FALSE, the unrestricted set will be used. The UE can use all the sequence available every integer multiple of Ncs. However, some sequences are not optimized for high Doppler shift due to high-speed mobility, and the correlation peak at eNB will reflect the wrong sequence, hence the false detection cannot be avoided.

10

If the parameter is set to TRUE, the restricted set will be used. The UE can only use the specific sequences which are designed for high-speed mobility. The correlation peak at eNB will be able to reflect the correct sequence.

11

Dependencies/Constraints: None.

12

Traceability: TS36.211 Sect. 5.7.2

13

RRC Message Structure:

8 9

14 15

SIB2  RadioResourceConfigCommon  PRACH-Config  PRACH-ConfigInfo  highSpeedFlag

18

Notes: Setting this parameter to TRUE will result in the use of restricted sets when calculating cyclic shifted sequences. The use of restricted set is optimized for high speed mobility cases with relatively large Doppler shift.

19

If the parameter is set to FALSE, unrestricted set will be used. Also please note that

16 17

20

-

21 22 23 24

-

For unrestricted set, the UE basically can use the any sequence every integer multiples of Ncs. For restricted set, the UE can only use some specific sequences which can compensate the high Doppler shit in high-speed mobility wireless channel. Otherwise, the correlation peak will reflect the wrong sequence and hence a false detection will happen.

25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

25

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3 MAC Layer Parameters

2

In general, the MAC layer is the one controlling the random access procedure.

3

There are two types of random access procedures: contention based and contention free.

7

In the contention based case the UE is using a randomly chosen preamble index; hence there is a possible collision situation when multiple UEs attempt to use the same index at the same time (i.e. in the same sub-frame). When this occurs, it needs to be resolved by the so called contention resolution procedure.

8

In the contention free case the UE gets a preamble ID assigned by the network.

4 5 6

10

The contention based procedure is used in all cases except handover, where the contention free procedure may be used instead.

11

2.3.1

9

12 13

ra-PreambleIndex

Definition: PRACH preamble index value, optionally signaled to the UE at handover for contention free random access to target eNB IE Value

14 15 16 17

Allowed Range

[0 … 63]

Recommended

Recommended for contention-free handover.

Engineering Units

0 … 63

Setting Tradeoff: The parameter value has no significance. However, using it is recommended in order to have shorter interruption at handover when contention-free procedure is enabled. Please note that a number of preamble indexes from the 64 possible are reserved for contention free or dedicated access.

19

Dependencies/Constraints: The value 0 shall not be used (TS36.321 Sect. 5.1.2). Value has to be larger than numberOfRA-Preambles (i.e. out of the non-dedicated preambles pool).

20

Traceability: TS36.321 Sect. 5.1.1 and 5.1.2; TS36.331 Sect. 6.3.2

21

RRC Message Structure:

18

22 23 24 25 26

RRCConnectionReconfiguration  MobilityControlInfo  rach-ConfigDedicated  raPreambleIndex Notes: When triggering handover the network may signal to the UE the PRACH preamble index and the PRACH mask index. In this case the UE MAC layer will trigger a contention free random access procedure using the received preamble index and mask.

29

If the preamble index or the mask index is absent (or the preamble index is 0), a contention based procedure is initiated (which requires more time to complete). For this case the UE MAC will randomly choose a preamble index from a given pool and will set the mask index to zero.

30

[See also notes numberOfRA-Preambles sizeOfRA-PreamblesGroupA and messageSizeGroupA]

27 28

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

26

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.2

numberOfRA-Preambles

2

Definition: Number of contention-based random access preambles available in the cell

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

3 4 5

6 7 8 9

Engineering Units

[n4, n8, n12, … n64]

4, 8, 12 … 64

64 if only Contention-Based RACH supported

64 if only Contention-Based RACH supported 40 – 56 if Contention-Free RACH supported

40 – 56 if Contention-Free RACH supported

Setting Tradeoff: Too small setting results in low number of contention-based preambles and increases the collision probability for contention based procedure, resulting in longer random access procedure duration. Too high setting results in low number of contention-free preambles and hence may delay handovers into the cell. Dependencies/Constraints: Parameter cannot be set to 64 if contention free random access procedure is used in the network

10

numberOfRA-Preambles shall not be smaller than sizeOfRA-PreamblesGroupA

11

Traceability: TS36.321 Sect. 5.1.1; 36.331 Sect. 6.3.2

12

RRC Message Structure:

13 14 15 16 17 18

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon preambleInfo  numberOfRA-Preambles Notes: This parameter defines how many out of the 64 available preambles are non-dedicated. One out of these non-dedicated preambles shall be randomly chosen by the UE MAC layer in case of contention-based random access procedure (i.e. when Random Access Preamble Index is not provided by the network).

20

The remaining preambles (if any) are the dedicated ones which are used for contention free procedure (i.e. they could be explicitly assigned by the network).

21

[See notes under sizeOfRA-PreamblesGroupA]

19

22 23 24

Please note that If contention-free handover is supported, this value should be function of handover traffic and can be started with 56 (8 for contention-free handover) and moving lower to 40 based on handover load.

25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

27

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.3

sizeOfRA-PreamblesGroupA

2

Definition: Number of preambles in random access preambles group A

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

[n4, n8, n12, … n60]

Engineering Units

4, 8, 12, … 60

Implementation dependent.

Recommended

- If the uplink resource allocation after PRACH is to be optimized, then we need to configure this parameter. - It depends on the statistic of the first TB size after the successful RACH procedure.

3 4

5 6

Setting Tradeoff: If this parameter is not configured, then eNodeB does not have enough information for uplink resource allocation after successful RACH. So a general uplink grant is allocated. If this parameter is configured, then eNodeB will be able to distinguish the size of the uplink grant requested by the UE after the successful RACH procedure.

8

Dependencies/Constraints: sizeOfRA-PreamblesGroupA shall be smaller than numberOfRAPreambles

9

Traceability: TS36.321 Sect. 5.1.1; 36.331 Sect. 6.3.2

7

10

RRC Message Structure:

11

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon 

12

preambleInfo  preamblesGroupAConfig  sizeOfRA-PreamblesGroupA

13

Notes:

14 15 16 17 18 19

This parameter should be optimized together with messageSizeGroupA and messagePowerOffsetGroupB. This Parameter is optional. If it is not signaled, then sizeOfRA-PreamblesGroupA is equal to numberOfRA-Preambles Contention-based random access preambles (see numberOfRA-Preambles) are divided into two groups: group A and B as illustrated below:

20 21 22 23 24 25 26

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

28

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

Non-dedicated preambles

Released - For Current Employee/Consultant Use Only

Preambles group A Preamble Index

Dedicated preambles

Preambles group B

0 1 2…

… 63

sizeOfRAPreamblesGroupA numberOfRA-Preambles

2

Note that if sizeOfRA-PreamblesGroupA is equal to numberOfRA-Preambles then there is no preambles group B.

3

If numberOfRA-Preambles is set to 64 then there are no dedicated preambles.

4

Regarding the selection between groups A and B see notes under messageSizeGroupA

5

[See also notes under Number of Random Access Preambles].

1

6

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

29

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.4

messageSizeGroupA

2

Definition: Maximum message size when preambles group A shall be used

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

b56, b144, b208, b256

Engineering Units

56 bits, 144 bits, 208 bits, 256 bits

Implementation dependent.

Recommended

- If the uplink resource allocation after PRACH is to be optimized, then we need to configure this parameter. - It depends on the statistic of the first TB size after the successful RACH procedure.

5

Setting Tradeoff: Too small setting results in selecting group B, and hence allocating un-necessary large grant even for small msg3. Too high setting will result in selecting group A, and hence allocating small grant for large msg3.

6

Dependencies/Constraints: The sizeOfRA-PreamblesGroupA has to be also present

7

Traceability: TS36.321 Sect. 5.1.2; 36.331 Sect. 6.3.2

8

RRC Message Structure:

9

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon 

3 4

10

preambleInfo  preamblesGroupAConfig  messageSizeGroupA

11

Notes:

12 13

This parameter should be optimized together with sizeOfRA-PreamblesGroupA and messagePowerOffsetGroupB.

18

The parameter messageSizeGroupA together with messagePowerOffsetGroupB defines the threshold for preambles group selection. Preambles group A always exists. Preambles group B is optional, and it shall be used by UEs which intend to send larger size msg3 (RRC Connection Request). This separation gives the possibility to the eNB to assign different grant for msg3 transmission depending on the expected msg3 size.

19

The selection rules are the following:

14 15 16 17

20 21 22 23 24 25 26 27 28 29

Preambles group B shall be used by the UE if: 1.) Preambles group B exists and 2.) msg3 size (including data + MAC header + eventual MAC control elements) is greater than messageSizeGroupA and 3.) If messagePowerOffsetGroupB < PCMAX – preambleInitialReceivedTargetPower – deltaPreambleMsg3 – PL (i.e. messagePowerOffsetGroupB < power headroom for msg3 transmission) Otherwise preambles group A shall be used. 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

30

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.5

messagePowerOffsetGroupB

2

Definition: Minimum UE power headroom where preambles group B may be used

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18

Engineering Units

-∞, 0dB, 5dB, 8dB, …

Implementation dependent.

Recommended

- If the uplink resource allocation after PRACH is to be optimized, then we need to configure this parameter. - It depends on the statistic of the first TB size after the successful RACH procedure.

3 4 5 6 7 8 9

Setting Tradeoff: If parameter is too low then a UE with small power headroom (i.e. in far cell scenario) may still select group B and hence gets un-necessary large grant (which may not be able to use anyway) If parameter is set to too high then a UE may be un-necessary prevented from selecting group B and hence it has to work with smaller grant. Dependencies/Constraints: Values of preambleInitialReceivedTargetPower and deltaPreambleMsg3 has to be taken into account

10

Traceability: TS36.321 Sect. 5.1.1; 36.331 Sect. 6.3.2

11

RRC Message Structure:

12

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon 

13

preambleInfo  preamblesGroupAConfig  messagePowerOffsetGroupB

14 15

Notes: Parameter defines the threshold for preambles group selection. See notes under messageSizeGroupA.

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

31

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

2.3.6

Random Access Parameters

ra-PRACH-MaskIndex

Definition: PRACH mask index defines the allowed preamble transmission occasions out of the ones available in the system. It is optionally signaled to the UE at handover or by PDCCH order. IE Value

[0 … 15]

Engineering Units

PRACH Resource Index: -

Allowed Range

All 0 1 2 … 9 Every Even Every Odd

(For mapping see TS36.321 Table 7.3-1) Set it to nonzero if access load is high Recommended

8

Setting Tradeoff: If the parameter is set to non-zero value, the eNodeB will apply the additional constraint in which subframe the UE can send the PRACH during the handover or through PDCCH order. This additional constraint is applied based on the subframes defined by prach-ConfigIndex. As such the chances of collision can be reduced in loaded network. If the parameter is set to zero, there is no additional constraint for PRACH.

9

Dependencies/Constraints:

4 5 6 7

10

-

Values 13 and above are “reserved”

11

-

PRACH Resource Index shall not be greater than the number of preamble occasions configured in the system (see PRACH Configuration Index)

12 13

Traceability: TS36.211 Sect. 5.7.1; TS36.321 Sect. 5.1.1; TS36.331 Sect. 6.3.2

14

RRC Message Structure:

16

RRCConnectionReconfiguration  MobilityControlInfo  RACH-ConfigDedicated  ra-PRACHMaskIndex

17

Notes: The PRACH mask index maps to a PRACH resource index as per TS36.321 Table 7.3-1.

15

18 19 20 21 22

The PRACH resource index is a mask to select a sub-set of the PRACH occasions available in the system. E.g. let’s assume that sub-frames 1, 4 and 7 are configured in the system as PRACH resources (PRACH configuration index = 9). If PRACH mask index = 3 is signaled, this maps to PRACH resource index 2 (see table above), which selects the 3rd PRACH occasion, i.e. sub-frame 7. Hence in this example the UE has to use sub-frame 7 for PRACH preamble transmission. 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

32

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.7

preambleInitialReceivedTargetPower

2

Definition: Expected received power at the eNB for the first random access preamble

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range Recommended

3 4 5

Engineering Units

[dBm-120, dBm-118, … dBm-90]

-120dBm, -118dBm, … -90 dBm

dBm-104 to dBm-108

-104.. -108 dBm

(eNodeB implementation dependent)

Setting Tradeoff: Too low setting may result in missed preamble reception(s) and hence longer duration of the random access procedure. Too high setting creates un-necessary interference for eventual PUSCH resources overlapping with PRACH resources.

7

Dependencies/Constraints: Has to be set according to eNB receiver characteristics (sensitivity, dynamic range)

8

Traceability: TS36.213 Sect. 6.1; 36.331 Sect. 6.3.2

9

RRC Message Structure:

6

11

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon  powerRampingParameters  preambleInitialReceivedTargetPower

12

Notes: Transmit power for the initial preamble will be calculated the following way:

13

PPRACH [dBm] = min {PCMAX, preambleInitialReceivedTargetPower + PL}

14

where

10

15

PCMAX is the configured maximum UE transmit power (TS36.101 Sec. 6.2.5) in dBm

16

preambleInitialReceivedTargetPower is in dBm

17

PL is the calculated downlink path loss estimate in dB

18 19 20 21

Also please note that Ideally, the value of preambleInitialReceivedTargetPower should be derived as 174 + 10Log(RACH BW) + eNodeB NF + RACH C/I. The eNodeB NF and RACH C/I may depend on eNodeB implementation. The current recommended value may need to be revisited if a large number of Preambles are sent by UE at cell edge.

22

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

33

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.8

powerRampingStep

2

Definition: Step to increase transmit power for preamble transmission repetitions

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Units

Allowed Range

[dB0, dB2, dB4, dB6]

0dB, 2dB, 4dB, 6dB

Recommended

dB2

2 dB

5

Setting Tradeoff: Too small value results in higher number of PRACH retransmissions hence in longer network access time. Too high value results in un-necessarily high preamble transmit power causing un-necessary interference.

6

Dependencies/Constraints: None.

7

Traceability: TS36.213 Sect. 6.1; 36.331 Sect. 6.3.2

8

RRC Message Structure:

3 4

9 10

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon  powerRampingParameters  powerRampingStep

14

Notes: If no response received to a PRACH preamble within the designated window (see under Random Access Response Window Size), or if none of the received responses contains a preamble identifier matching the transmission, the UE has to repeat the preamble transmission with increased power.

15

Power of the nth preamble is calculated as the following:

16

Pn = PPRACH + (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep

11 12 13

17

where

18

PPRACH is the transmit power of the initial preamble in dBm

20

PREAMBLE_TRANSMISSION_COUNTER is set to 1 at the initial transmission and increased by one for each further transmission

21

powerRampingStep is expressed in dB

19

23

The preamble retransmission procedure is repeated until a response is received or until the configured maximum number of attempts is reached (see under Maximum Number of Preamble Transmission).

24

Regarding the timing of retransmissions see TS36.213 Sect. 6.1.1

22

25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

34

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.9

preambleTransMax

2

Definition: Maximum number of preamble transmissions if no response is received

Released - For Current Employee/Consultant Use Only

IE Value

3 4

5 6 7 8 9

Engineering Units

Allowed Range

[n3, n4 … n8, n10, n20, n50, n100, n200]

3, 4, … 8, 10, 20, 50, 100, 200

Recommended

n10

10

Setting Tradeoff: Too small value results in un-successful random access procedure due to not enough power ramping, due to temporary RF degradation, or due to temporary overload on the eNB. Too high setting results in un-necessary overload of the PRACH resources on the air interface and on the eNB in the cases when eNB does not respond due to overload situation or service outage. Dependencies/Constraints: Has to be aligned with timers for RRC Connection (re-)establishment (T300 and T301), also considering the value of preambleTransMax and macContentionResolutionTimer

10

Traceability: TS36.321 Sect. 5.1.4; 36.331 Sect. 6.3.2

11

RRC Message Structure:

12

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon 

13

ra-SupervisionInfo  preambleTransMax

14 15 16 17 18

Notes: This parameter does not limit number of RACH attempts for initial RRC Connection or HO. However it does limit the number of RACH in certain RRC Connected mode cases (lack of UL grant, TA expiry). Although the recommended value is in the range of 10 to 20, in a well optimized network, it is expected that the RACH procedure should be successful within the first 1-3 attempts. Larger number of RACH attempts needs to be investigated.

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

35

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.10 ra-ResponseWindowSize

2

Definition: Number of subframes to be monitored for random access response(s)

Released - For Current Employee/Consultant Use Only

IE Value

3 4

Engineering Units

Allowed Range

[sf2, sf3, sf4, sf5, sf6, sf7, sf8, sf10]

UNIT: subframe

Recommended

sf4-5

4-5 subframes

RANGE: 2, 3, … 10

Setting Tradeoff: Too high setting will cause long wait time before retrying in case of non-responded preamble. Too low setting may not give enough time to the eNB to respond.

7

Dependencies/Constraints: Has to be aligned with timers for RRC Connection (re-)establishment (T300 and T301), also considering the value of ra-ResponseWindowSize and macContentionResolutionTimer

8

Traceability: TS36.321 Sect. 5.4.1; 36.331 Sect. 6.3.2

9

RRC Message Structure:

5 6

10

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon 

11

ra-SupervisionInfo  ra-ResponseWindowSize

12 13 14 15 16 17 18 19 20 21 22 23 24 25

Notes: After transmitting the PRACH preamble the UE has to monitor PDCCH for random access responses. The PDCCH monitoring has to be started in the 3rd subframe after the preamble’s end and should be continued for ra-ResponseWindowSize subframes. As an example let’s assume that random access preamble was transmitted in subframe 1 with format 0 and random access response window size is set as 4. With format 0 the preamble “fits” into one subframe (see notes at PRACH Configuration Index), i.e. it will end in subframe 1. Hence PDCCH has to be monitored in subframes 4, 5, 6 and 7. The identity addressing the UE for random access response is the RA-RNTI calculated the following way: RA-RNTI=1+t_id where t_id is the index to the subframe used for the prach preamble transmission. Continuing the example above and assuming that PRACH configuration index = 6: the possible PRACH occasions are subframes 1 and 6, out of them subframe one was used, which has the index 0. Hence RA_RNTI=1+0=1 will address the UE. Note that at this point in the procedure there is no way to differentiate between UEs using the same preamble index in the same sub-frame.

26 27

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

36

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.11 mac-ContentionResolutionTimer

2

Definition: Timer to check the completion on contention resolution procedure

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Units

Allowed Range

sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64

UNIT: subframe

Recommended

sf56

56 subframes

RANGE: 8, 16, …

6

Setting Tradeoff: If the value is too small, the eNB may not have enough time to process Msg3 and schedule Contention Resolution message on PDCCH/PDSCH. If the value is set too high, it will introduce the delay to the access procedure in case multiple access attempts are required (due to bad channel condition).

7

Dependencies/Constraints: None.

8

Traceability: TS36.321 Sect. 5.1.5; 36.331 Sect. 6.3.2

9

RRC Message Structure:

3 4 5

10

SIB2  RadioResourceConfigCommon  RACH-ConfigCommon 

11

ra-SupervisionInfo  mac-ContentionResolutionTimer

12 13

Notes: The contention resolution timer is started at msg3 transmission (and shall be restarted at eventual related HARQ retransmissions).

14 15 16 17 18 19 20 21 22

The contention resolution procedure is designed to separate UEs which are accidentally using identical preamble index in the same subframe. Contention resolution is achieved via comparing CRNTI (if available) or UE Contention Resolution Identity (the SAE temporary mobile subscriber identity S-TMSI or a random number) sent by the UE in MSG3. and received from the eNB in the response (MSG4). In case of a match the contention resolution procedure is successful and the contention resolution timer is stopped. In the case the timer expires, the UE shall consider contention resolution as unsuccessful and proceed with a preamble retransmission (unless the maximum number of transmissions is reached).

23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

37

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Random Access Parameters

1

2.3.12 maxHARQ-Msg3Tx

2

Definition: Maximum allowed number of Msg3 PDU HARQ transmissions

Released - For Current Employee/Consultant Use Only

IE Value

3 4 5 6

Engineering Units

Allowed Range

[1 … 8]

1 … 8 transmissions

Recommended

4

4 transmissions

Setting Tradeoff: Too small value may result in un-successful msg3 transmission in case of momentarily radio link degradations. Too high value causes un-necessary signaling in the case if eNB does not respond due to overload or temporary outage.

10

A smaller value will allow lesser soft-combining opportunity for Msg3 while a much larger value may introduce additional delay with limited benefit beyond a certain number of HARQ attempts. Recommend using 4 UL HARQ transmissions since there is expected to be limited soft combining gain beyond 4 transmissions.

11

Dependencies/Constraints: None.

12

Traceability: TS36.321 Sect. 5.1.5; 36.331 Sect. 6.3.2

7 8 9

14

RRC Message Structure: SIB2  RadioResourceConfigCommon  RACH-ConfigCommon  maxHARQ-Msg3Tx

15

Notes:

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

38

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

3 Cell Reselection Parameter Settings

2

Chapter 3: Table of Contents

3

3.1 Intra-frequency Cell Reselection .......................................................................................................... 42

4

3.1.1 Introduction ......................................................................................................................................... 42

5

3.1.2 Qrxlevmin ............................................................................................................................................ 44

6

3.1.3 Sintrasearch.......................................................................................................................................... 45

7

3.1.4 QHyst .................................................................................................................................................... 46

8

3.1.5 Qoffsets,n ............................................................................................................................................... 47

9

3.1.6 TreselectionEUTRAN ......................................................................................................................... 48

10

3.2 Inter-frequency and Inter-RAT Cell Reselection Common Parameters ......................................... 49

11

3.2.1 Cell Reselection Priority ..................................................................................................................... 49

12

3.2.2 Snonintrasearch ................................................................................................................................... 50

13

3.2.3 Threshserving, low ................................................................................................................................ 51

14

3.3 Inter-frequency Cell Reselection .......................................................................................................... 52

15

3.3.1 TreselectionEUTRAN ......................................................................................................................... 52

16

3.3.2 Equal Priority Neighbor Inter-Frequency Reselection .................................................................. 53

17

3.3.2.1 Qoffsets,n ............................................................................................................................................ 54

18

3.3.2.2 Qoffsetfrequency .............................................................................................................................. 55

19

3.3.3 Higher Priority Neighbor Inter-Frequency Reselection ................................................................ 56

20

3.3.3.1 Threshx,high ........................................................................................................................................ 57

21

3.3.4 Lower Priority Neighbor Inter-Frequency Reselection ................................................................. 58

22

Lower Priority Neighbor Inter-Frequency Reselection .......................................................................... 58

23

3.3.4.1 Threshx,low ......................................................................................................................................... 59

24

3.4 Inter-RAT Cell Reselection to UTRAN ............................................................................................... 60

25

3.4.1 Qqualmin ............................................................................................................................................. 61

26

3.4.2 Qrxlevmin ............................................................................................................................................ 62

27

3.4.3 TreselectionUTRA ............................................................................................................................... 63 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

39

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.4.4 Higher Priority UTRAN Neighbor ................................................................................................... 64

2

3.4.4.1 Threshx,high ........................................................................................................................................ 64

3

3.4.5 Lower Priority UTRAN Neighbor .................................................................................................... 65

4

3.4.5.1 Threshx,low ......................................................................................................................................... 65

5

3.5 Inter-RAT Cell Reselection from UTRAN .......................................................................................... 66

6

3.5.1 Spriorityserach1 .................................................................................................................................. 66

7

3.5.2 Spriorityserach2 .................................................................................................................................. 67

8

3.5.3 QrxlevminEUTRA............................................................................................................................... 68

9

3.5.4 Treselection .......................................................................................................................................... 69

10

3.5.5 Inter-RAT Scaling Factor for Treselection ....................................................................................... 70

11

3.5.6 Higher Priority E-UTRAN Neighbor ............................................................................................... 71

12

3.5.6.1 Threshx,high ........................................................................................................................................ 71

13

3.5.7 Lower Priority E-UTRAN Neighbor ................................................................................................ 72

14

3.5.7.1 Threshx,low ......................................................................................................................................... 72

15

3.5.7.2 Threshserving,low .............................................................................................................................. 73

16

3.6 Inter-RAT Cell Reselection to GERAN ............................................................................................... 74

17

3.6.1 Qrxlevmin ............................................................................................................................................ 74

18

3.6.2 TreselectionGERA ............................................................................................................................... 75

19

3.6.3 Higher Priority GERAN Neighbor ................................................................................................... 76

20

3.6.3.1 Threshx,high ........................................................................................................................................ 76

21

3.6.4 Lower Priority GERAN Neighbor .................................................................................................... 77

22

3.6.4.1 Threshx, low......................................................................................................................................... 77

23

3.7 Inter-RAT Reselection from GERAN .................................................................................................. 78

24

3.7.1 E-UTRAN_QRXLEVMIN .................................................................................................................. 78

25

3.7.2 T_reselection ........................................................................................................................................ 79

26

3.7.3 Higher Priority E-UTRAN Neighbor ............................................................................................... 80

27

3.7.3.1 THRESH_E-UTRAN_high .............................................................................................................. 80

28

3.7.4 Lower Priority E-UTRAN Neighbor ................................................................................................ 81

29

3.7.4.1 THRESH_E-UTRAN_low ............................................................................................................... 81

30

3.7.4.2 THRESH_GSM_low......................................................................................................................... 82

31

3.7.4.3 H_PRIO ............................................................................................................................................. 83

32

3.8 Inter-RAT Cell Reselection to CDMA2000 ......................................................................................... 84

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

40

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.8.1 Higher Priority CDMA2000 Neighbor............................................................................................. 84

2

3.8.1.1 Threshx,high ........................................................................................................................................ 84

3

3.8.2 Lower Priority CDMA2000 Neighbor .............................................................................................. 85

4

3.8.2.1 Threshx, low......................................................................................................................................... 85

5

3.8.2.2 TreselectionCDMA_HRPD / TreselectionCDMA_1xRTT ................................................................... 86

6

3.9 Reselection Mobility States ................................................................................................................... 87

7

3.9.1 TCRmax ................................................................................................................................................ 88

8

3.9.2 TCRmaxHyst ....................................................................................................................................... 89

9

3.9.3 NCR_M ................................................................................................................................................... 90

10

3.9.4 NCR_H ................................................................................................................................................... 91

11

3.9.5 Qhyst Speed Dependant Scaling Factor: sf-High ............................................................................ 92

12

3.9.6 Qhyst Speed Dependant Scaling Factor: sf-Medium ....................................................................... 93

13

3.9.7 Treselection Speed Dependant Scaling Factor: sf-High .................................................................. 94

14

3.9.8 Treselection Speed Dependant Scaling Factor: sf-Medium ............................................................ 95

15 16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

41

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3 4

Cell Reselection is the process by which a UE in the RRC idle state autonomously selects a different cell from the one that it is currently camped on. It bases the reselection on parameters provided to it by the network. Depending on the configuration, the UE can reselect to intra- and inter-frequency EUTRA cells as well as inter-RAT cells, which can be UTRAN, GERAN or CDMA2000.

12

Parameters contained in the System Information Blocks (SIBs) control the cell reselection process. SIB3 contains general reselection parameters that control how and when the UE searches for neighboring cells. SIBs 4 and 5 contain information related to intra- and inter- E-UTRA cells respectively whilst SIBs 6, 7 and 8 contain information related to UTRAN, GERAN and CDMA2000 neighbors respectively. In the case of non intra-frequency neighbors, LTE allows the definition of priorities between neighboring cells of different networks. The relative priority of a detected cell then impacts the manner in which it is assessed for reselection. Inter-RAT neighbors must always be either higher or lower priority than the current camped LTE network.

13

3.1 Intra-frequency Cell Reselection

14

3.1.1

15

For any cell to be considered for selection it must be suitable. A cell is considered suitable when:

5

Released - For Current Employee/Consultant Use Only

Cell Reselection Parameter Settings

6 7 8 9 10 11

Srxlev > 0

16 17

where Srxlev = Qmeas – (Qrxlevmin + Qrxlevminoffset) – Pcompensation

18 19

and Pcompensation = max(PEMAX-PUMAX, 0)

20 21 22 23 24 25 26 27

where Qrxlevmin is the minimum required RSRP, Qrxlevminoffset is an offset that is applied uniquely to the calculation of Srxlev when the UE searches for a higher priority PLMN while camped in a VPLMN. Pcompensation is an offset associated with the maximum power that the UE will be allowed to transmit such that PEMAX is the maximum allowed UE transmit power and PUMAX is the maximum UE transmit power. For intra-frequency cell reselection, the UE evaluates the relative ranking of the serving and neighbor cells Rs and Rn respectively such that Rs = Qmeas,s + QHyst

28 29 30 31 32 33 34 35

Introduction

and Rn = Qmeas,n – Qoffset where Qmeas is the measured RSRP of the serving (s) or neighbor (n) cell, QHyst is the serving cell hysteresis and Qoffset is the neighbor cell offset. The cell with the largest R value is considered to be ranked the highest. Once a cell other than the serving cell in ranked highest, the timer Treselection is started and continues whilst this condition is satisfied. Reselection to the new cell occurs when the timer expires.

36 37 38 39

Figure 3-1 shows an example of how this mechanism works with a UE moving from A to B. The UE is initially camped on the cell with Physical Cell ID 1. At point 1, SServingCell < Sintrasearch and the UE begins to search for intra-frequency neighbors. At point 2, Cell 3 (Physical Cell ID 100)’s strength is 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

42

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3 4

Released - For Current Employee/Consultant Use Only

5

Cell Reselection Parameter Settings

higher than serving Cell 1 and the reselection timer for Cell 3 is started. At point 3, Cell 2 (Physical Cell ID 50)’s strength is higher than serving Cell 1 too and the reselection timer for Cell 2 is started too. However, before expiration of the reselection timer, cell 3 (Physical Cell ID 50) becomes worse than serving Cell 1 at point 4 and the reselection timer for Cell 3 is stopped. At point 5 the reselection timer for Cell 2 expires and the UE therefore now camps on cell 2.

6 7

Figure 3-1 Intra-Frequency Cell Reselection Example

8

S

Qoffset = 1 dB QHyst = 2 dB Cell 1 (Phy Cell ID: 1)

Cell 3 (Phy Cell ID: 100)

Sintrasearch = 1 sec Cell 2 (Phy Cell ID: 50)

Qoffset = 0 dB

< 1 sec 1

80-W3835-1 Rev. A

2

3

4

5

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Time

43

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.1.2

Qrxlevmin

2

Definition: Minimum received signal level in terms of RSRP.

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Units

Allowed Range

Integer (-70…-22)

-140…-44 dBm, in steps of 2 dB

Recommended

-60

-120 dBm

3

6

Setting Tradeoff: If set too low, the UE may camp on a cell with low quality and may not be able to receive reliable service. If set too high, the UE may prematurely declare a cell unsuitable and may unnecessarily select another PLMN.

7

Dependencies/Constraints:

8

Traceability: TS 36.304 Sect. 5.2.3, TS 36.331 Sect. 6.3.4

9

RRC Message Structure: SIB1  CellSelectionInfo  q-RxLevMin,

4 5

10 11 12 13 14 15 16 17 18 19

SIB3  intraFreCellReselectionInfo  q-RxLevMin Notes: The Qrxlevmin IE affects cell selection criteria. A necessary (but not sufficient) condition for cell selection is that: Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) – Pcompensation > 0 With Pcompensation = max (PEMAX_H – PPowerClass, 0) Where, Qrxlevmeas is the measured RSRP, Qrxlevminoffset is an offset applied when a UE is searching for a higher priority PLMN when camped on a VPLM, PPowerClass is the maximum UE transmit power, and PEMAX_H is the maximum allowed uplink transmit power. It should be noted that the value defined in SIB1 will be used for initial acquisition and camping whilst the value defined in SIB3 will be applied to assess the suitability of intra-frequency neighbors.

20

21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

44

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.1.3

Sintrasearch

2

Definition: Srxlev threshold to trigger intra-frequency measurements. IE Value

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

20

40 dB

7

Setting Tradeoff: If the parameter is too small, the UE will not perform intra-frequency measurements and may miss the opportunity to perform cell reselection. If parameter is too large, the UE will perform intra-frequency measurements, although the likelihood that the neighboring cells will meet the cell reselection criteria is negligible, thereby wasting idle mode current and decreasing stand-by time.

8

Traceability: TS36.304 Sect. 5.2.4.2, TS36.331 Sect. 6.3.1.

9

RRC Message Structure: SIB3  intraFreqCellReslectionInfo  s-IntraSearch

3 4 5 6

10

Notes:

12

As battery life is less of a concern for data cards, the device mix of the network can be considered when setting this parameter.

13

The UE always searches if this parameter is not broadcast by the network.

14

Above recommendation assumes that Qrxlevmin = -120dBm

11

15

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

45

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.1.4

QHyst

2

Definition: Hysteresis value for the serving cell used in the ranking criteria for cell reselection IE Value

3 4 5 6

Engineering Units

Allowed Range

dB0, dB1, dB2, dB3, dB4, dB5, dB6, 0 dB, 1 dB, 2 dB … 20 dB, 22 dB 24 dB8, dB10,dB12, dB14, dB16, dB18, dB dB20, dB22, dB24

Recommended

dB4

4 dB

Setting Tradeoff: If parameter is too small, the UE may perform frequent cell reselection to cells only marginally better than the current serving cell, which may lead to excessive battery consumption. If parameter is too large, the UE may stay camped on a relatively weak cell even though a significantly better cell is available.

8

Dependencies/Constraints: This IE should be set in conjunction with Qoffset since they jointly affect cell ranking.

9

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

7

10

RRC Message Structure: SIB3  CellReselectionInfoCommon  q-Hyst

11

Notes:

12

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

46

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.1.5

Qoffsets,n

2

Definition: Offset applied to a neighbor cell in the cell ranking criteria for cell reselection. IE Value

3 4 5 6 7 8 9 10 11 12

Engineering Units

-24 dB, -22 dB, -20 dB, -18dB, 16dB … 20 dB, 22 dB, 24 dB

Allowed Range

dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3,2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24

Recommended

dB0 (Depends on deployment strategy)

0 dB (Depends on deployment strategy)

-

Setting Tradeoff: A positive value of Qoffset deters the UE from reselecting to that cell. If the parameter is set too low, reselection may be triggered even though the neighboring cell is only marginally better than the current cell. If parameter is set too high, the UE may not reselect to the cell even though the cell significantly better than the current cell. The parameter should be set to avoid potential ping-ponging whilst maintaining the UE in a cell with sufficient quality. Dependencies/Constraints: Qoffset should be set in conjunction with QHyst since they jointly affect cell ranking criterion. Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1 RRC Message Structure: SIB4  IntraFreqNeighCellList  IntraFreqNeighCelInfo  qOffsetCell

13 14 15 16 17

Notes: A larger value of this parameter is recommended for cells situated at Tracking Area borders. This increased reselection deterrent is a tradeoff between the increased signaling associated with the Tracking Area Update procedure and staying camped on a cell that is not the best.

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

47

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3 4

3.1.6

Cell Reselection Parameter Settings

TreselectionEUTRAN

Definition: Intra-frequency cell reselection timer. This timer is started when the conditions required for cell reselection have been met. Reselection takes places if the conditions remain throughout the duration of the timer. IE Value

5 6 7 8 9

Engineering Units

Allowed Range

Integer (0…7)

0 … 7 seconds

Recommended

2

2 seconds

Setting Tradeoff: If this parameter is too large, the UE may stay camped on a relatively weak cell even though a significantly better cell is available. This has the potential to impact performance or cause an outage. Is set too low, the UE may frequently and unnecessarily reselect another cell. Dependencies/Constraints: Unique reselection thresholds are possible for each EUTRA carrier frequency as well as for each other RAT that may be present.

10

Traceability: TS36.304 Sect. 5.2.4.7, TS36.331 Sect. 6.3.1.

11

RRC Message Structure: SIB3  intraFreqCellReselectionInfo  t-ReselectionEUTRA

12

Notes:

13

Cell Reselection is also prohibited if a previous reselection has occurred within 1 second.

14 15

This setting also depends on the defaultDRXCycle. The above recommended settings assume that defaultDRXCycle = 1.28s.

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

48

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

3.2 Inter-frequency and Inter-RAT Cell Reselection Common Parameters

6

Reselection for inter-frequency and inter-RAT neighbors is controlled by a set of parameters and priorities. Depending on whether the non-serving cell has equal, lower or higher priority will govern the reselection behavior. Inter-frequency neighbor cells can be defined with equal, lower or higher priority whilst inter-RAT cell can have only lower or higher priority.

7

3.2.1

3 4

Released - For Current Employee/Consultant Use Only

Cell Reselection Parameter Settings

5

8 9

Cell Reselection Priority

Definition: This parameter defines the absolute priority of a carrier frequency (or set of carrier frequencies for GERAN) and is used to determine the cell reselection behaviour of the UE. IE Value

Allowed Range Recommended

Engineering Units

Integer[0…7]

0...7

Depends on deployment strategy

0=lowest priority…7=highest priority

15

Setting Tradeoff: The setting of this parameter depends on deployment strategy. Various scenarios exist governed by the number of LTE carriers an operator has and how he chooses to distribute UEs in idle mode. For example, an operator could choose to prefer that all idle UEs remain on one specific carrier frequency but be moved between different carriers in connected mode based on load conditions or specific applications. Additionally, any other system of a different RAT belong to the operator will also impact how priorities are defined.

16

Traceability: TS36.304 Sect 5.2.4.1, TS36.331 Sect 6.3.1

17

RRC Message Structure: SIB3  cellReselectionServingFreqInfo  cellReselectionPriority,

18

SIB5 interFreqCarrierFreqList  interFreqCarrierFreqInfo cellReselectionPriority,

19

SIB6 CarrierFreqListUTRA-FDD CarrierFreqUTRA-FDD cellReselectionPriority

20

SIB7 CarrierFreqInfoListGERAN carrierFreqs  commonInfoCellReselectionPriority

10 11 12 13 14

21 22 23 24 25

SIB8 CellReselctionParamtersCDMA2000  BandClassListCDAM2000  CellReselectionPriority Notes: A value of 0 corresponds to the lowest priority whilst a value of 7 corresponds to the highest priority. Neighbor information defined in each of the SIBs that are broadcast by a network can have different priorities.

26

27

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

49

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.2.2

Cell Reselection Parameter Settings

Snonintrasearch

Definition: Srxlev threshold below which inter-frequency and inter-RAT measurements are performed for equal or lower priority neighbors. IE Value

4 5 6 7 8

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

5 (3 for inter-RAT)

10 dB (6 dB for inter-RAT)

Setting Tradeoff: If the parameter is set too small, the UE will not perform inter-frequency (nor inter-RAT) measurements and may miss the opportunity to perform reselection to another viable frequency assignment or technology. If the parameter is too large, the UE will perform unnecessary inter-frequency (and inter-RAT) measurements, most likely leading to inter-frequency and inter-RAT reselection, even while the current cell is of acceptable quality, thereby decreasing stand-by time.

11

Dependencies/Constraints: Snonintrasearch needs to be chosen in accordance with Sintrasearch and to avoid a situation where the UE performs an inter-frequency (and inter-RAT) search but no intra-frequency search. Preferably the values are chosen such that Sintrasearch > Snonintrasearch.

12

Traceability: TS36.304 Sect. 5.2.4.2, TS36.331 Sect. 6.3.1

13

RRC Message Structure: SIB3  cellReselectionServingFreqInfo  s-NonIntraSearch

14

Notes: This parameter is common for all inter-frequency and inter-RAT neighbors

9 10

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

50

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.2.3

Cell Reselection Parameter Settings

Threshserving, low

Definition: Absolute threshold of Sxrlev of a serving cell below which one of the two conditions for reselection to a lower priority inter-frequency (or inter-RAT) neighbor cell are met. IE Value

4 5 6 7 8 9

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

2 (1 for inter-RAT)

4 dB (2 dB for inter-RAT)

Setting Tradeoff: A high value of this parameter causes reselection to a (inter-frequency or interRAT) cell of a lower priority when the current cell is of adequate signal strength. A low value of this parameter may delay reselection from a weak cell to a stronger more suitable (inter-frequency or inter-RAT) cell of a lower priority. Dependencies/Constraints: Threshserving,low should be set in conjunction with Threshx,low and Qrxlevmin of the inter-frequency or inter-RAT neighbor.

10

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

11

RRC Message Structure: SIB3  cellReselectionServingFreqInfo  threshServingLow

12 13 14 15 16 17 18 19

Notes: This is a common parameter that is used to assess during the reselection decision for both inter-frequency and inter-RAT neighbors. For pre-R8 UTRAN/GERAN, once UE reselects to UTRAN/GERAN it would reselect back to LTE based only on OOS in UTRAN/GERAN. Set it to lower range (i.e., 2 dB) for pre-R8 UTRAN/GERAN. For inter-frequency reselection, the bandwidth of source and target cells should be taken into consideration.

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

51

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.3 Inter-frequency Cell Reselection

2

3.3.1

3 4 5

TreselectionEUTRAN

Definition: Inter-frequency cell reselection timer. This timer is started when the conditions required for cell reselection have been met. Reselection takes places if the conditions remain throughout the duration of the timer. IE Value

Allowed Range Recommended

6 7 8

Engineering Units

Integer (0…7)

0 … 7 seconds

1 (2 for same priority neighbor)

1 second (2 seconds for same priority neighbor)

Setting Tradeoff: If this parameter is too large, the UE may stay camped on a relatively weak cell even though a significantly better cell is available. This has the potential to impact performance or cause an outage. Is set too low, the UE may frequently and unnecessarily reselect another cell.

10

Dependencies/Constraints: Unique reselection thresholds are possible for each EUTRA carrier frequency as well as for each other RAT that may be present

11

Traceability: TS36.304 Sect. 5.2.4.7, TS36.331 Sect. 6.3.1.

12

RRC Message Structure: SIB5  interFreqCellReselectionInfo  t-ReselectionEUTRA

13

Notes: This timer applies regardless of the relative priorities of the serving and neighbor cells.

9

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

52

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3 4

3.3.2

Rs = Qmeas,s + QHyst and Rn = Qmeas,n – Qoffset

7 8 9 10 11 12 13 14 15 16 17 18 19 20

Equal Priority Neighbor Inter-Frequency Reselection

For inter-frequency cell reselection to a frequency that has equal priority to the serving cell frequency, the UE evaluates the relative ranking of the serving and neighbor cells Rs and Rn respectively such that

5 6

Cell Reselection Parameter Settings

where Qmeas is the measured RSRP of the serving (s) or neighbor (n) cell, QHyst is the serving cell hysteresis and Qoffset is the neighbor cell offset (the sum of an individual cell Qoffsets,n plus the Qoffsetfrequencythat applies equally to all cells of that frequency) The cell with the largest R value is considered to be ranked the highest. Once a cell other than the serving cell in ranked highest, the timer Treselection is started and continues whilst this condition is satisfied. Reselection to the new cell occurs when the timer expires. Figure 3-2 shows an example of a UE initially camped on the f1 cell with Physical Cell ID 1. The only other neighbor defined is the f2 cell with Physical cell ID 50. The priorities of the two frequencies f1 and f2 are defined as the same. At point 1, SServingcell < Snonintrasearch and the UE begins to search for inter-frequency neighbor. The f2 cell is detected and is ranked the highest at Point 2 due to the fact that its received level is (Qhyst+Qoffset) better than that of the serving f1 cell. The reselection timer (2 sec) associated with f2 is started and as the cell remains the highest ranked for the period of the timer, the UE reselects to this cell when the timer expires (Point 3).

S QHyst = 2 dB

Qoffset = 2 dB

Cell 1 (f1, Phy Cell ID: 1)

Snonintrasearch

Reselection

Cell 2 (f2, Phy Cell ID: 50)

= 2 sec 1

2

3

21 22

Time

Figure 3-2 Inter-Frequency Reselection Example (equal priority neighbor)

23

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

53

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.3.2.1 Qoffsets,n

2

Definition: Offset applied to a neighbor cell in the cell ranking criteria for cell reselection.

Released - For Current Employee/Consultant Use Only

IE Value

3 4 5 6 7

Engineering Units

-24 dB, -22 dB, -20 dB, -18dB, 16dB … 20 dB, 22 dB, 24 dB

Allowed Range

dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3,2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24

Recommended

dB0 (Depends on deployment strategy)

0 dB (Depends on deployment strategy)

-

Setting Tradeoff: A positive value of Qoffset deters the UE from reselecting to that cell. If the parameter is set too low, reselection may be triggered even though the neighboring cell is only marginally better than the current cell. If parameter is set too high, the UE may not reselect to the cell even though the cell significantly better than the current cell. The parameter should be set to avoid potential ping-ponging whilst maintaining the UE on a cell with sufficient quality.

11

Dependencies/Constraints: Qoffset should be set in conjunction with Qhyst and Qoffsetfrequency since they jointly affect cell ranking criterion. The total offset applied to a neighbor is the sum of Qoffset and Qoffsetfrequency. Whereas Qoffset can be set on a per cell basis, Qoffsetfrequency applies equally to all the neighbor cells of a defined frequency carrier.

12

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

13

RRC Message Structure: SIB5  InterFreqNeighCellInfo  q-OffsetCell

8 9 10

14 15

Notes:

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

54

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Cell Reselection Parameter Settings

3.3.2.2 Qoffsetfrequency Definition: Offset applied to all cells of a specific frequency in the cell ranking criteria for cell reselection. IE Value

4 5 6 7 8

Engineering Units

-24 dB, -22 dB, -20 dB, -18dB, 16dB … 20 dB, 22 dB, 24 dB

Allowed Range

dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3,2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24

Recommended

Depends on deployment strategy

TBD

-

Setting Tradeoff: A positive value of Qoffset deters the UE from reselecting to that cell. If the parameter is set too low, reselection may be triggered even though the neighboring cell is only marginally better than the current cell. If parameter is set too high, the UE may not reselect to the cell even though the cell significantly better than the current cell. The parameter should be set to avoid potential ping-ponging whilst maintaining the UE on a cell with sufficient quality.

12

Dependencies/Constraints: Qoffsetfrequency should be set in conjunction with Qhyst and Qoffset since they jointly affect cell ranking criterion. The total offset applied to a neighbor is the sum of Qoffset and Qoffsetfrequency. Whereas Qoffset can be set on a per cell basis, Qoffsetfrequency applies equally to all the neighbor cells of a frequency.

13

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

14

RRC Message Structure: SIB5  InterFreqCarrierFreqInfo  q-OffsetFreq

9 10 11

15 16

Notes:

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

55

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9 10 11

3.3.3

Cell Reselection Parameter Settings

Higher Priority Neighbor Inter-Frequency Reselection

Reselection from a lower priority serving cell to a higher priority cell does not consider the signal strength or quality of the serving cell. If a higher priority EUTRAN frequency (or RAT) is specified in a broadcasted SIB to the UE, measurements are always made on the neighbor frequency (or RAT). Figure 3-3 shows an example of a UE that is initially camped on an f1 cell with Physical Cell ID 1. Assuming that no intra-frequency neighbors are detected, the only other neighbor defined is the f2 cell with Physical cell ID 50. The priorities of the two frequencies f1 and f2 are defined such that f1 has a lower priority than f2. At Point 1, the UE detects that f2 cell becomes greater than the value of Threshx,high transmitted in SIB5. The Treselction timer (2 sec) associated with f2 is started at this time and as the triggering condition is met for the period of the timer, the UE reselects to this cell when the timer expires.

S Cell 1 (f1, Phy Cell ID: 1) Cell 2 (f2, Phy Cell ID: 50)

Threshx,high Reselection

2 sec 1

2

12 13 14

Time

Figure 3-3 Inter-Frequency (or Inter-RAT) Reselection Example (Higher Priority Neighbor)

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

56

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Cell Reselection Parameter Settings

3.3.3.1 Threshx,high Definition: Absolute threshold of Sxrlev of an inter-frequency neighbor cell above which the reselection process to that cell is initiated. IE Value

4 5 6 7 8 9

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

3

6 dB

Setting Tradeoff: A high value of this parameter causes delay of the reselection to a cell (and frequency) that is a higher priority than the current cell (and frequency). A low value of this parameter may cause reselection to cell that is significantly weaker (and possibly poorer quality) than the current cell. Dependencies/Constraints: Threshx,high should be set in conjunction with Qrxlevmin of the neighboring frequency as this parameter is used in the definition of Srxlev.

10

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

11

RRC Message Structure: SIB5  InterFreqCarrierFreqInfo  threshX-High

12 13

Notes:

14

Above recommendation assumes that Qrxlevmin = -120 dBm.

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

57

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9 10 11 12 13 14 15 16 17

3.3.4

Cell Reselection Parameter Settings

Lower Priority Neighbor Inter-Frequency Reselection

Reselection from a higher priority cell to a lower priority cell considers the signal strength of both serving cell and neighbor cell. As in the equal priority case described in Section 3.3.2, inter-frequency measurements of lower priority neighbors are started when Srxlev of the serving cell is less than Snonintrasearch . Reselection to a lower priority neighbor is triggered when Srxlev of the neighbor is higher than Threshx,low and the Srxlev of the serving cell is lower than Threshserving,low. This condition must be maintained for the duration of the reselection timer Treselction. Figure 3-4 shows an example where a UE is initially camped on the f1 cell with Physical Cell ID 1. Assuming that no intra-frequency neighbors are detected, the only other neighbor defined is the f2 cell with Physical cell ID 50. The priorities of the two frequencies f1 and f2 are defined such that f1 has a higher priority than f2. At point 1, SServingcell < Snonintrasearch and the UE begins to search for the inter-frequency neighbor. Two independent conditions must be met for reselection to occur. The first of these is met at Point 2 when the received level of the f2 cell becomes greater than the value of Threshx,low transmitted in SIB5. The second condition is met at Point 3 when the received level of the serving f1 cell becomes lower than Threshserving,low transmitted in SIB3. The Treselction timer associated with f2 is started at this time and as this condition is met for the period of the timer, the UE reselects to this cell when the timer expires.

18

S Cell 1 (f1, Phy Cell ID: 1) Cell 2 (f2, Phy Cell ID: 50)

Snonintrasearch Reselection

Threshx,low

Threshserving,low

2 sec 1

2

3

19 20 21

4

Time

Figure 3-4 Inter-Frequency (or Inter-RAT) Reselection Example (Lower Priority Neighbor)

22 23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

58

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Cell Reselection Parameter Settings

3.3.4.1 Threshx,low Definition: Absolute threshold of Sxrlev of a lower priority inter-frequency neighbor cell above which one of the two conditions for reselection that cell are met. IE Value

4 5 6 7 8 9

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

4

8 dB

Setting Tradeoff: A high value of this parameter delays reselection even though the signal strength of the current serving cell is relatively weak. A low value of this parameter may cause premature reselection to lower priority cell even though its signal strength is not significantly higher than the current serving higher priority cell. Dependencies/Constraints: Threshx,low should be set in conjunction with Threshserving,low and Qrxlevmin of the serving and neighbor frequencies.

10

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

11

RRC Message Structure: SIB5  InterFreqCarrierFreqInfo  threshX-Low

12 13

Notes:

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

59

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9 10 11 12 13 14 15

Cell Reselection Parameter Settings

3.4 Inter-RAT Cell Reselection to UTRAN Reselection from LTE to a different access technology is always based on the comparative priority of the other RAT. LTE and any other RAT cannot be defined to have the same priority, and other RATs will not be considered for reselection unless a priority (as described in 3.2.1) is specified. Based on this value, the UE will use the RAT-specific value of either Threshx,high or Threshx,low (and Threshserving,low of the serving LTE frequency), as described in 0 and 0 , to decide if reselection takes place. Additionally, each RAT will have an associated value for Treselection as well as optional mobility state related parameters. For cell reselection to UTRAN, both UMTS FDD and TDD neighbors can be specified on up to 16 different carrier frequencies. For the UTARN cell, CPICH Received Signal Code Power (RSCP) is used as the measurement quantity for each neighbor cell that triggers reselection. The cell must also however be suitable, in terms of both RSCP and Ec/No. There is no direct comparison made between RSCP and any LTE measurement quantity (RSRP or RSRQ). Additionally, neighbor information broadcast in SIB6 is common per carrier frequency and no discrimination can be made on a per cell basis.

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

60

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.4.1

Cell Reselection Parameter Settings

Qqualmin

Definition: Minimum quality level of a UTRAN FDD cell expressed in terms of CPICH EC/N0 for it to be considered suitable for reselection. IE Value

4 5 6 7 8 9

Engineering Units

Allowed Range

Integer (-24…0)

-24 … 0 dB

Recommended

-18

-18 dB

Setting Tradeoff: If parameter is too small, the UE may consider a UTRAN cell for reselection that is camp on a cell that has very low quality and may not be able to receive reliable service. If the parameter is too large, the UE will ignore cells that are suitable for reselection and exhibit better quality than the current E-UTRAN cell. Dependencies/Constraints: Qqualmin broadcast by E-UTRAN should be set in conjunction with the value specified in the target UTRAN network.

10

Traceability: TS25.304 Sect. 5.2.3, TS36.331 Sect. 6.3.1

11

RRC Message Structure:

12

SIB6  CarrierFreqListUTRA-FDD  CarrierFreqUTRA-FDD  q-QualMin

13

Notes:

14

The minimum suitability calculation for CPICH Ec/No is based on the following assumptions: a) b) c) d) e)

15 16 17 18 19 20

21 22 23

The UE receives equal power from 3 cells The signal strength of the desired cell at the cell edge is equal to the noise power The power allocated of the CPICH is 10 % of the total Node B power (EC/Ior = -10 dB) The noise figure of the UE, NfUE, is 8 dB Interference from the 2nd tier cells =1.8 Pj

For EC/N0 at the edge of coverage we find:

Pj  EC   EC   1  1 = 10 log  + 10 log  = −10 − 8 = −18dB   =  ⋅  1 + 5.3   10   N 0   I or  kT ⋅ W ⋅ NfUE + 3 ⋅1.8 ⋅ Pj where, EC/N0 is the received energy per chip divided by the power density in the band.

25

EC/Ior is the ratio of the average CPICH transmit energy per chip to the total transmit power spectral density at the Node B.

26

kT is the thermal noise power density Nth

27

W is the effective bandwidth (3.84 106 Hz)

28

Pj is the total RF power in Watt transmitted by cell j.

24

29

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

61

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.4.2

Cell Reselection Parameter Settings

Qrxlevmin

Definition: Minimum quality level of a UTRAN cell expressed in terms of CPICH RSCP utilized to calculate Sxrlev. IE Value

Allowed Range Recommended 4 5 6

Integer (-60…-13)

Engineering Units

-119…-25 dBm, in steps of 2 dB (Value = IE *2 +1)

-57

-113 dBm

Setting Tradeoff: If set too low, the UE may consider a cell of low quality for reselection. If set too high, the UE will not consider a cell that is suitable for reselection even though the cell that the UE is camped on is of poor quality.

8

Dependencies/Constraints: Qrxlevmin broadcast by E-UTRAN should be set in conjunction with the value specified in the target UTRAN network.

9

Traceability: TS 25.304 Sect. 5.2.3, TS 36.331 Sect. 6.3.1.

7

10

RRC Message Structure:

11

SIB6  CarrierFreqListUTRA-FDD CarrierFreqUTRA-FDD  q-RxLevMin

12

SIB6  CarrierFreqListUTRA-TDD CarrierFreqUTRA-FDD  q-RxLevMin

13 14 15 16 17

Notes: For a UTRAN cell, Qrxlevmin is used to determine the Srxlev such that: Srxlev = Qrxlevmeas – Qrxlevmin – Pcompensation With Pcompensation = max (UE_TX_PWR_MAXRACH – P_MAX, 0) where, Qrxlevmeas is the measured RSCP, P_MAX is the maximum UE transmit power, and UE_TX_PWR_MAXRACH is the maximum allowed transmit power on the PRACH.

19

Using the same definitions and assumptions as for the calculation of Qqualmin in Section 3.4.1, Qrxlevmin can be determined as follows:

20

RSSI

18

21 22 23 24

= UE total received power = noise + signal + interference = kTW⋅ NfUE + 3⋅N0 = kTW⋅ NfUE ⋅ [1 + 3⋅N0 / (kTW⋅NfUE)] = -108.16 dBm + 8 dB + 10⋅log(1+3) = -94.14 dBm

25

RSCP = EC/N0 ⋅ RSSI

26

For EC/N0 = -18 dB, the CPICH RSCP at the edge of coverage amounts to

27

RSCP [dBm]

= EC/N0 [dB] + RSSI [dBm] = -18 dB – 94.11 dBm = -112.11 dBm

28 29 30 31 32

Notes: The recommendation applies for a nominal CPICH transmit power of 10 % of the total Node B power (EC/Ior = -10 dB). Qrxlevmin increases dB per dB with increasing nominal CPICH power allocation. The 3GPP standard requires Qrxlevmin to be an odd number, resulting in a recommended value of -113dBm.

33

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

62

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

3.4.3

Cell Reselection Parameter Settings

TreselectionUTRA

Definition: Inter-RAT cell reselection timer for a UTRAN neighbor cell. This timer is started when the conditions required for cell reselection have been met. Reselection takes places if the conditions remain throughout the duration of the timer. IE Value

5 6 7 8

Engineering Units

Allowed Range

Integer (0…7)

0 … 7 seconds

Recommended

1

1 second

Setting Tradeoff: If this parameter is too large, the UE may stay camped on a relatively weak cell even though a significantly better cell is available. This has the potential to impact performance or cause an outage. If set too low, the UE may frequently and unnecessarily reselect to another cell and RAT.

10

Dependencies/Constraints: A single value of Treselection is applied across all specified UTRAN carriers

11

Traceability: TS36.304 Sect. 5.2.4.7, TS36.331 Sect. 6.3.1.

12

RRC Message Structure: SIB6  t-ReselectionUTRA

13

Notes: This timer applies regardless of the relative priorities of the serving and neighbor cells.

9

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

63

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.4.4

2

3.4.4.1 Threshx,high

Released - For Current Employee/Consultant Use Only

3 4

Cell Reselection Parameter Settings

Higher Priority UTRAN Neighbor

Definition: Absolute threshold of Sxrlev of an inter-RAT UTRAN neighbor cell above which the reselection process to that cell is initiated when the neighbor cell is of a higher priority. IE Value

5 6 7 8 9

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

N/A

N/A

Setting Tradeoff: A high value of this parameter causes delay of the reselection to a cell (and RAT) that is a higher priority than the current E-UTRA cell. A low value of this parameter may cause reselection to cell that is significantly weaker (and possibly poorer quality) than the current cell. Dependencies/Constraints: Threshx,high should be set in conjunction with Qrxlevmin of the UTRAN cell.

10

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

11

RRC Message Structure:

12

SIB6  carrierFreqListUTRA-FDD  CarrierFreqUTRA-FDD  threshX-High

13 14

Notes:

15

It is assumed that LTE will always be higher priority than UTRAN.

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

64

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.4.5

2

3.4.5.1 Threshx,low

Released - For Current Employee/Consultant Use Only

3 4

Cell Reselection Parameter Settings

Lower Priority UTRAN Neighbor

Definition: Absolute threshold of Sxrlev of a lower priority inter-RAT UTRAN neighbor cell above which one of the two conditions for reselection to that cell are met. IE Value

5 6 7 8

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

2

4 dB

Setting Tradeoff: A high value of this parameter delays reselection even though the signal strength of the current serving E-UTRAN cell is relatively weak. A low value of this parameter may cause premature reselection to a lower priority cell even though its signal strength is not significantly higher than the current serving higher priority cell.

10

Dependencies/Constraints: Threshx,low should be set in conjunction with Threshserving,low (of the EUTRAN cell) and Qrxlevmin (of the UTRAN cell).

11

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

12

RRC Message Structure:

13

SIB6  carrierFreqListUTRA-FDD  CarrierFreqUTRA-FDD  threshX-Low

14

SIB6  carrierFreqListUTRA-TDD  CarrierFreqUTRA-TDD  threshX-Low

9

15 16

Notes:

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

65

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.5 Inter-RAT Cell Reselection from UTRAN

2

3.5.1

3

Released - For Current Employee/Consultant Use Only

Cell Reselection Parameter Settings

4 5 6

Spriorityserach1

Definition: Serving UTRAN cell threshold of Srxlev above which, searches for higher priority interRAT neighbors are limited to rate of at least every 60*Nlayers seconds, where Nlayers is the number of IRAT layers. For Srxlev below this threshold both higher and lower priority inter-RAT neighbor searches are carried out at a more frequent rate defined by the DRX cycle. IE Value

7 8 9 10

Engineering Units

Allowed Range

Integer (0…31)

0 … 62 dB in steps of 2 dB

Recommended

3

6 dB

Setting Tradeoff: Setting this parameter too low will limit the rate at which searches for inter-RAT neighbors are made, even though the signal strength of the UTRAN cell is weak. Setting this parameter too high will result in unnecessary frequent searches for inter-RAT neighbors even though the signal strength of the UTRAN cell is adequate.

12

Dependencies/Constraints: Srxlev > Spriorityserach1 is one of two conditions that must be met to limit the rate of higher priority searches. The other condition is Squal > Spriorityserach2.

13

Traceability: TS25.304 Sect. 5.2.6.1.2a, TS25.331 Sect. 8.6.7.3a

11

15

RRC Message Structure: SysInfoType19  UTRA-PriorityInfoList  utra-ServingCell  sPrioritySearch1

16

Notes:

14

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

66

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5

3.5.2

Cell Reselection Parameter Settings

Spriorityserach2

Definition: Serving UTRAN cell threshold of Squal above which, searches for higher priority interRAT neighbors are limited to rate of at least every 60*Nlayers seconds, where Nlayers is the number of IRAT layers. For Squal below this threshold both higher and lower priority inter-RAT neighbor searches are carried out at a more frequent rate defined by the DRX cycle. IE Value

6 7 8 9

Engineering Units

Allowed Range

Integer (0…7)

0 … 7 dB

Recommended

4

4 dB

Setting Tradeoff: Setting this parameter too low will limit the rate at which searches for inter-RAT neighbors are made, even though the signal quality of the UTRAN cell is poor. Setting this parameter too high will result in unnecessary frequent searches for inter-RAT neighbors even though the signal qulaity of the UTRAN cell is adequate.

11

Dependencies/Constraints: Squal > Spriorityserach2 is one of two conditions that must be met to limit the rate of higher priority searches. The other condition is Srxlev > Spriorityserach1.

12

Traceability: TS25.304 Sect. 5.2.6.1.2a, TS25.331 Sect. 8.6.7.3a

10

14

RRC Message Structure: SysInfoType19  UTRA-PriorityInfoList  utra-ServingCell  sPrioritySearch2

15

Notes:

13

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

67

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.5.3

QrxlevminEUTRA

2

Definition: Minimum E-UTRAN neighbor cell received signal level in terms of RSRP.

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Units

Allowed Range

Integer (-70…-22)

-140…-44 dBm, in steps of 2 dB

Recommended

-60

-120 dBm

3 4 5 6

Setting Tradeoff: If set too low, the UE may reselect to an E-UTRAN cell with low quality and may not be able to receive reliable service. If set too high, the UE may stay camped on a weak UTRAN cell even though a viable E-UTRAN cell is available.

8

Dependencies/Constraints: This should be set to the same value as Qrxlevmin broadcast in SIB1 of the target EUTRAN system.

9

Traceability: TS 25.304 Sect. 5.2.6.1.4, TS 25.331 Sect. 10.3.7.115

7

11

RRC Message Structure: SysInfoType19  EUTRA-FrequencyAndPriorityInfoList  EUTRA-FrequencyAndPriorityInfo  qRxLevMinEUTRA

12

Notes:

10

13 14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

68

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

3.5.4

Cell Reselection Parameter Settings

Treselection

Definition: UTRAN cell reselection timer. This timer is started when the conditions required for cell reselection have been met. Reselection from UTRAN takes places if the conditions remain met throughout the duration of the timer. IE Value

5 6 7 8

Engineering Units

Allowed Range

Integer (0…31)

0 … 31 seconds

Recommended

1

1 second

Setting Tradeoff: If this parameter is too large, the UE may stay camped on a relatively weak UTRAN cell even though a significantly better E-UTRAN cell is available. This has the potential to impact performance or cause an outage. Is set too low, the UE may frequently and unnecessarily reselect another cell.

10

Dependencies/Constraints: In UTRAN, the same value for the reselection timer applies to all RATs but with scaling possible using the Inter-RAT Scaling Factor

11

Traceability: TS25.304 Sect. 5.2.6.1.4, TS25.331 Sect. 10.3.2.3.

9

13

RRC Message Structure: SysInfoType3  cellSelectReselectInfo  CellSelectReselectInfoSIB3-4  T-Reselection-S

14

Notes:

12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

69

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.5.5

Cell Reselection Parameter Settings

Inter-RAT Scaling Factor for Treselection

Definition: Scaling factor for Treselection applied by UTRAN for reselection to inter-RAT neighbors. IE Value

Engineering Units

Allowed Range

Integer (4..19)

0 … 4.75 in steps of 0.25

Recommended

4

1

8

Setting Tradeoff: If this parameter to unity, inter-RAT reselection is subject to the same parameters as UTRAN intra-frequency reselection. If this parameter is set to a large value, inter-RAT reselection will be delayed even though a good quality inter-RAT neighbor is available. This has the potential to impact performance or cause an outage. The relative priority of the other available RATs compared to UTRAN should also be considered in setting this parameter.

9

Dependencies/Constraints: This parameter applies equally to all RATs.

4 5 6 7

10

Traceability: TS25.304 Sect. 5.2.6.1.4, TS25.331 Sect. 10.3.2.3.

14

RRC Message Structure: SysInfoType4  v4b0NonCriticalExtensions  v590NonCriticalExtension  SysInfoType4-v5c0ext-IEs  sysInfoType4-v590ext CellSelectReselectInfoTreselectionScaling-v5c0ext  interRATTreselectionScalingFactor  TreselectionScalingFactor

15

Notes:

11 12 13

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

70

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.5.6

2

3.5.6.1 Threshx,high

Released - For Current Employee/Consultant Use Only

3 4

Cell Reselection Parameter Settings

Higher Priority E-UTRAN Neighbor

Definition: Absolute threshold of Sxrlev of a higher priority LTE neighbor cell above which the reselection process to that cell from UTRAN is initiated. IE Value

5 6 7 8

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

2

4 dB

Setting Tradeoff: A high value of this parameter will delay reselection to a cell that is a higher priority than the current cell and is of adequate RSRP. A low value of this parameter may cause reselection to cell that is relatively weak in terms of RSRP (and possibly poorer quality) than the current cell.

10

Dependencies/Constraints: Threshx,high should be set in conjunction with Qrxlevmin of the E-UTRAN network as this parameter is used in the definition of Srxlev.

11

Traceability: TS25.304 Sect. 5.2.4.6, TS25.331 Sect. 6.3.1

9

13

RRC Message Structure: SysInfoType19  EUTRA-FrequencyAndPriorityInfoList  EUTRA-FrequencyAndPriorityInfo  threshXhigh

14

Notes:

12

15

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

71

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.5.7

2

3.5.7.1 Threshx,low

Released - For Current Employee/Consultant Use Only

3 4

Cell Reselection Parameter Settings

Lower Priority E-UTRAN Neighbor

Definition: Absolute threshold of Sxrlev of a lower priority inter-RAT E-UTRAN neighbor cell above which one of the two conditions for reselection to that cell are met. IE Value

5 6 7 8

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

N/A

N/A

Setting Tradeoff: A high value of this parameter delays reselection even though the signal strength of the current serving UTRAN cell is relatively weak. A low value of this parameter may cause premature reselection to a lower priority cell even though its signal strength is not significantly higher than the current serving higher priority cell.

10

Dependencies/Constraints: Threshx,low should be set in conjunction with Threshserving,low (of the UTRAN cell) and Qrxlevmin (of the E-UTRAN cell).

11

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

9

12 13 14 15

RRC Message Structure: SysInfoType19  EUTRA-FrequencyAndPriorityInfoList  EUTRA-FrequencyAndPriorityInfo  threshXlow Notes: It is assumed that E-UTRAN will be higher priority than UTRAN and therefore no recommended value is defined for this parameter.

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

72

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Cell Reselection Parameter Settings

3.5.7.2 Threshserving,low Definition: Absolute threshold of Sxrlev of a serving UTRAN cell below which one of the two conditions for reselection to a lower priority inter--RAT E-UTRAN neighbor cell are met. IE Value

4 5 6

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

N/A

N/A

Setting Tradeoff: A high value of this parameter causes reselection to an inter-RAT cell of a lower priority when the current cell is of adequate signal strength. A low value of this parameter may delay reselection from a weak cell to a stronger more suitable inter-RAT cell of a lower priority.

8

Dependencies/Constraints: Threshserving,low should be set in conjunction with Threshx,low and Qrxlevmin of the UTRAN cell.

9

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

7

10 11

RRC Message Structure: SysInfoType19  UTRA-PriorityInfoList  utra-ServingCell  threshServingLow

12 13

Notes:

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

73

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.6 Inter-RAT Cell Reselection to GERAN

3

For GERAN, neighboring carrier frequencies are organized into groups. Common reselection parameters can be defined for up to 16 groups and are specified in SIB7.

4

3.6.1

2

Released - For Current Employee/Consultant Use Only

Cell Reselection Parameter Settings

5 6

Qrxlevmin

Definition: Minimum quality level of a GERAN cell expressed in terms of RSSI utilized to calculate Sxrlev. IE Value

Allowed Range Recommended

Integer (0…45)

Engineering Units

-115…-25 dBm, in steps of 2 dB (Value= (IE *2 ) – 115)

6

-103 dBm

7 8 9 10

Setting Tradeoff: If set too low, the UE may consider a cell of low quality for reselection. If set too high, the UE will not consider a cell that is suitable for reselection even though the cell that the UE is camped on is of poor quality.

13

Dependencies/Constraints: This parameter is equivalent to the RXLEV_ACCESS_MIN parameter defined in 44.018 and 45.008 as the minimum received signal level at the MS required for access to the system (Range is [Integer 0..63]: -110 to -48 dBm).

14

Traceability: TS 36.331 Sect. 6.3.1.

15

RRC Message Structure:

11 12

16 17 18 19

SIB7  carrierFreqsInfoList  CarrierFreqsInfoListGERAN  carrierFreqs  commonInfo q-RxLevMin Notes: This should be set to the same value as the target network

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

74

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

3.6.2

Cell Reselection Parameter Settings

TreselectionGERA

Definition: Inter-RAT cell reselection timer for a GERAN neighbor cell. This timer is started when the conditions required for cell reselection have been met. Reselection takes places if the conditions remain throughout the duration of the timer. IE Value

Allowed Range Recommended

5 6 7 8

Engineering Units

Integer (0…7)

0 … 7 seconds

6 (1 if UTRAN not available)

6 seconds (1 second if UTRAN not available)

Setting Tradeoff: If this parameter is too large, the UE may stay camped on a relatively weak cell even though a significantly better cell is available. This has the potential to impact performance or cause an outage. Is set too low, the UE may frequently and unnecessarily reselect another cell and RAT.

10

Dependencies/Constraints: Unique reselection thresholds are possible for each EUTRA carrier frequency as well as for each other RAT that may be present

11

Traceability: TS36.304 Sect. 5.2.4.7, TS36.331 Sect. 6.3.1.

12

RRC Message Structure: SIB7  t-ReselectionGERAN

13

Notes: This timer applies regardless of the relative priorities of the serving and neighbor cells.

9

14 15 16 17

If both lower priority UTRAN and GERAN suitable networks area available, a larger value of this parameter is recommended for GERAN to encourage the UE to reselect to UTRAN rather than GERAN. The relative priority of the UTRAN and GERAN network is not considered in the reselection decision if both are lower priority than LTE.

18 19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

75

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.6.3

2

3.6.3.1 Threshx,high

Released - For Current Employee/Consultant Use Only

3 4

Cell Reselection Parameter Settings

Higher Priority GERAN Neighbor

Definition: Absolute threshold of Sxrlev of an inter-RAT GERAN neighbor cell above which the reselection process to that cell is initiated when the neighbor cell is of a higher priority. IE Value

5 6 7 8 9

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

N/A

N/A

Setting Tradeoff: A high value of this parameter causes delay of the reselection to a cell (and RAT) that is a higher priority than the current E-UTRA cell. A low value of this parameter may cause reselection to cell that is significantly weaker (and possibly poorer quality) than the current cell. Dependencies/Constraints: Threshx,high should be set in conjunction with Qrxlevmin of the GERAN cell.

10

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

11

RRC Message Structure:

12 13

Engineering Units

SIB7  carrierFreqsInfoList  CarrierFreqsInfoListGERAN  carrierFreqs  commonInfo  threshX-High

14 15 16

Notes: It is assumed that LTE will be higher priority than GERAN and no parameter recommendation is therefore made.

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

76

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.6.4

2

3.6.4.1 Threshx, low

Released - For Current Employee/Consultant Use Only

3 4

Cell Reselection Parameter Settings

Lower Priority GERAN Neighbor

Definition: Absolute threshold of Sxrlev of a lower priority inter-RAT GERAN neighbor cell above which one of the two conditions for reselection to that cell are met. IE Value

5 6 7 8

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

2

4 dB

Setting Tradeoff: A high value of this parameter delays reselection even though the signal strength of the current serving E-UTRAN cell is relatively weak. A low value of this parameter may cause premature reselection to a lower priority cell even though its signal strength is not significantly higher than the current serving higher priority cell.

10

Dependencies/Constraints: Threshx,low should be set in conjunction with Threshserving,low (of the EUTRAN cell) and Qrxlevmin (of the GERAN cell).

11

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

12

RRC Message Structure:

9

13 14

SIB7  carrierFreqsInfoList  CarrierFreqsInfoListGERAN  carrierFreqs  commonInfo  threshX-Low

15 16

Notes:

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

77

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.7 Inter-RAT Reselection from GERAN

2

3.7.1

3

Definition: Minimum RSRP for a neighbor E-UTRAN cell to be considered suitable for reselection.

E-UTRAN_QRXLEVMIN IE Value

Engineering Units

Allowed Range

Integer (0..31)

-140…-78 dBm, in steps of 2 dB

Recommended

10

-120 dBm

4 5 6 7 8 9 10

Setting Tradeoff: If set too low, the UE may reselect to a cell with low quality and may not be able to receive reliable service. If set too high, the UE may delay reselection to an E-UTRAN cell of adequate quality and remain on GERAN. Dependencies/Constraints: This parameter should be set to the same value of the SIB1 broadcasted Qrxlevmin of the target E-UTRAN network. Traceability: TS 44.018 Sect. 10.5.2.33b, TS 45.008 Sect. 6.6.6

12

RRC Message Structure: SI 2quater  SI 2quater Rest Octets  Repeated E-UTRAN Neighbour Cells struct  E-UTRAN_QRXLEVMIN

13

Notes:

11

14 15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

78

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

3.7.2

Cell Reselection Parameter Settings

T_reselection

Definition: Cell reselection timer for reselection from a GERAN cell. This timer is started when the conditions required for cell reselection have been met. Reselection takes places if the triggering conditions remain throughout the duration of the timer. IE Value

Allowed Range Recommended

Engineering Units

Integer (0…3).

0 = 5 sec, 1 = 10 sec, 2 = 15 sec, 3 = 20 sec

0

5 seconds

8

Setting Tradeoff: If this parameter is too large, the UE may stay camped on a relatively weak cell even though a significantly better cell is available. This has the potential to impact performance or cause an outage. Is set too low, the UE may frequently and unnecessarily reselect another cell and RAT.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 44.018 Sect. 10.5.2.33b, TS 45.008 Sect. 6.6.6

12

RRC Message Structure: SI 2quater  SI 2quater Rest Octets  Serving Cell Priority Parameters Description struct  T_Reselection

13

Notes:

11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

79

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.7.3

2

3.7.3.1 THRESH_E-UTRAN_high

3

Released - For Current Employee/Consultant Use Only

Cell Reselection Parameter Settings

4

Higher Priority E-UTRAN Neighbor

Definition: Absolute threshold of Sxrlev of an E-UTRAN neighbor cell above which the reselection process to that cell is initiated. IE Value

5 6 7 8 9 10

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

2

4 dB

Setting Tradeoff: A high value of this parameter causes delay of the reselection to an E-UTRAN cell that is a higher priority than the current GERAN cell. A low value of this parameter may cause reselection to cell that is relatively weak (and possibly poorer quality) than the current cell. Dependencies/Constraints: THRESH_E-UTRAN_high should be set in conjunction with EUTRAN_QRXLEVMIN as both are used in the definition of Srxlev. Traceability: TS 44.018 Sect. 10.5.2.33b, TS 45.008 Sect. 6.6.6

12

RRC Message Structure: SI 2quater  SI 2quater Rest Octets  Repeated E-UTRAN Neighbour Cells struct  THRESH_E-UTRAN_high

13

Notes:

11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

80

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.7.4

2

3.7.4.1 THRESH_E-UTRAN_low

3

Released - For Current Employee/Consultant Use Only

Cell Reselection Parameter Settings

4

Lower Priority E-UTRAN Neighbor

Definition: Absolute threshold of Sxrlev of a lower priority E-UTRAN neighbor cell above which one of the two conditions for reselection that cell are met. IE Value

5 6 7 8

Engineering Units

Allowed Range

Integer[0 … 31]

0 … 62 dB, in steps of 2 dB

Recommended

N/A

N/A

Setting Tradeoff: A high value of this parameter delays reselection even though the signal strength of the current serving cell is relatively weak. A low value of this parameter may cause premature reselection to lower priority cell even though its signal strength is not significantly higher than the current serving higher priority cell.

10

Dependencies/Constraints: THRESH_E-UTRAN_low should be set in conjunction with EUTRAN_QRXLEVMIN and THRESH_GSM_low.

11

Traceability: TS36 TS 44.018 Sect. 10.5.2.33b, TS 45.008 Sect. 6.6.6

9

12 13

RRC Message Structure: SI 2quater  SI 2quater Rest Octets  Repeated E-UTRAN Neighbour Cells struct  THRESH_E-UTRAN_low

14 15

Notes:

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

81

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Cell Reselection Parameter Settings

3.7.4.2 THRESH_GSM_low Definition: Absolute threshold of S_GSM of a serving GSM cell below which one of the two conditions for reselection to a lower priority inter-RAT neighbor cell are met. IE Value

Allowed Range Recommended

Integer[0 … 15]

Engineering Units

0 … 28 dB, in steps of 2 dB (An IE of 15 corresponds to always)

N/A

N/A

6

Setting Tradeoff: A high value of this parameter causes reselection to a an inter-RAT neighbor cell of a lower priority when the current cell is of adequate signal strength. A low value of this parameter may delay reselection from a weak cell to a stronger more suitable inter-RAT cell of a lower priority.

7

Dependencies/Constraints:

8

Traceability: TS36 TS 44.018 Sect. 10.5.2.33b, TS 45.008 Sect. 6.6.6

4 5

9 10 11 12

RRC Message Structure: SI 2quater  SI 2quater Rest Octets  Serving Cell Priority Parameters Description struct  THRESH_GSM_low Notes: S_GSM is equivalent to the C1 criterion specified (in 45.008) and represents the difference between RLA_C and RXLEV_ACCESS_MIN.

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

82

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4 5

Cell Reselection Parameter Settings

3.7.4.3 H_PRIO Definition: Relative threshold above S_GSM that the Srxlev of a lower priority neighbor inter-RAT cell must be to trigger reselection to that cell. This is an additional mechanism that is applicable only if the criterion for reselection utilizing THRESH_E-UTRAN_low and THRESh_GSM_low are not met. IE Value

Integer[0 … 3]

0 = rule disabled, 1 = 5 dB, 2 = 4 dB, 3 = 3 dB

N/A

N/A

Allowed Range

Recommended

Engineering Units

6

Setting Tradeoff: None

7

Dependencies/Constraints:

8

Traceability: TS36 TS 44.018 Sect. 10.5.2.33b, TS 45.008 Sect. 6.6.6

9 10

RRC Message Structure: SI 2quater  SI 2quater Rest Octets  Serving Cell Priority Parameters Description struct  H_PRIO

11 12

Notes:

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

83

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.8 Inter-RAT Cell Reselection to CDMA2000

4

For CDMA2000 both 1xRTT and HRPD reselections are supported with the parameters specified in SIB8. Neighbors from up to a maximum of 32 band classes can be supported, with up to 16 neighbors per band class.

5

The Srxlev value of a CDMA2000 cell is defined as:

2 3

Released - For Current Employee/Consultant Use Only

Cell Reselection Parameter Settings

Srxlev = -FLOOR(-20*log(Ec/Io))

6

7

in units of 0.5dB where Ec/Io refers to the measured pilot strength.

8

3.8.1

9

3.8.1.1 Threshx,high

10 11

Higher Priority CDMA2000 Neighbor

Definition: Absolute threshold of Sxrlev of an inter-RAT CDMA2000 neighbor cell above which the reselection process to that cell is initiated when the neighbor cell is of a higher priority. IE Value

Integer[0 … 31] Allowed Range

Engineering Units

0, -0.5, -1 … -15.5 dB, in steps of 0.5 dB (Value = IE*-0.5)

Recommended

N/A

N/A

14

Setting Tradeoff: A high value of this parameter causes delay of the reselection to a cell that is a higher priority than the current E-UTRAN cell. A low value of this parameter may cause reselection to cell that is relatively weaker (and possibly poorer quality) than the current cell.

15

Dependencies/Constraints:

16

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

17

RRC Message Structure:

12 13

18 19

SIB8  parametersHRPD  cellReselectionParametersHRPD  bandClassList  threshXHigh

21

SIB8  parameters1XRTT  cellReselectionParameters1XRTT  bandClassList  threshXHigh

22

Notes:

20

23 24

Its is assumed that LTE will be higher priority than eHRPD and no parameter recommendation is therefore made.

25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

84

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

3.8.2

2

3.8.2.1 Threshx, low

Released - For Current Employee/Consultant Use Only

3 4

Cell Reselection Parameter Settings

Lower Priority CDMA2000 Neighbor

Definition: Absolute threshold of Sxrlev of a lower priority inter-RAT CDMA2000 neighbor cell above which one of the two conditions for reselection to that cell are met. IE Value

Integer[0 … 31] Allowed Range

Engineering Units

0, -0.5, -1 … -15.5 dB, in steps of 0.5 dB (Value = IE/-2)

Recommended 5 6 7 8

14 - 16 (eHRPD)

-7 to -8 dB (eHRPD)

Setting Tradeoff: A high value of this parameter delays reselection even though the signal strength of the current serving E-UTRAN cell is relatively weak. A low value of this parameter may cause premature reselection to a lower priority cell even though its signal strength is not significantly higher than the current serving higher priority cell.

10

Dependencies/Constraints: Threshx,low should be set in conjunction with Threshserving,low (of the EUTRAN cell).

11

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

12

RRC Message Structure:

9

13 14

15 16

SIB8  parametersHRPD  cellReselectionParametersHRPD  bandClassList  threshXLow SIB8  parameters1XRTT  cellReselectionParameters1XRTT  bandClassList  threshXLow

17 18

Notes:

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

85

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Cell Reselection Parameter Settings

3.8.2.2 TreselectionCDMA_HRPD / TreselectionCDMA_1xRTT Definition: Inter-RAT cell reselection timer for a CDMA2000 neighbor cell. This timer is started when the conditions required for cell reselection have been met. Reselection takes places if the triggering conditions remain throughout the duration of the timer. IE Value

Engineering Units

Allowed Range

Integer (0…7)

0 … 7 seconds

Recommended

1

1 second

8

Setting Tradeoff: If this parameter is too large, the UE may stay camped on a relatively weak cell even though a significantly better cell is available. This has the potential to impact performance or cause an outage. Is set too low, the UE may frequently and unnecessarily reselect another cell and RAT.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS36.304 Sect. 5.2.4.7, TS36.331 Sect. 6.3.1.

11

RRC Message Structure:

12

SIB8  parametersHRPD  cellReselectionParametersHRPD  t-ReselectionCDMA2000

13

SIB8  parameters1XRTT  cellReselectionParameters1XRTT  t-ReselectionCDMA2000

14 15

Notes: This timer applies regardless of the relative priorities of the serving and neighbor cells.

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

86

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9 10

Cell Reselection Parameter Settings

3.9 Reselection Mobility States High and medium mobility states are optional features in LTE whereby reselection parameters can be modified from those associated with the normal, non-mobility state. If configured in SIB3, the UE will count the number of reselections that occur within a defined time TCRmax. The UE will then enter the medium or high mobility state if the number of reselections is greater than NCR_M or NCR_H (8 or 16), respectively, within this evaluation period. Upon entering either of the mobility states, the Qhyst of the serving cell is adjusted by the values signaled by sf-Medium and sf-High. Similarly, the value of Treselection is scaled by signaled values of sf-Medium and sf-High. A UE will return from the high or medium mobility states to the normal state if the number of reselections to support high or medium mobility is not detected for a time specified by TCRmaxHyst.

11

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

87

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.9.1

Cell Reselection Parameter Settings

TCRmax

Definition: Evaluation period utilized by the UE to measure the number of reselections to trigger entry into the medium- or high-mobility states. IE Value

4 5 6 7 8 9

Allowed Range

s30, s60, s120, s180, s240

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

Engineering Units

30, 60, 120, 180, 240 seconds

Setting Tradeoff: A high value for this parameter, corresponding to a long evaluation period, may delay the entry into the higher mobility states which may limit the UE’s sensitivity to a rapidly changing radio environment. A low value for this parameter, corresponding to a short evaluation period, may cause the UE to prematurely enter a higher mobility state, or ping pong between normal and higher-mobility states. This increase in unnecessary reselections can negatively impact battery life.

11

Dependencies/Constraints: TCRmax should be set in conjunction with NCR_M and NCR_H as these jointly trigger the entry into medium- and high-mobility states.

12

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

10

13 14

RRC Message Structure: SIB3  cellReselectionInfoCommon  speedStateReselectionPars  mobilityStateParameters  t-Evaluation

15 16

Notes:

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

88

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

3.9.2

Cell Reselection Parameter Settings

TCRmaxHyst

Definition: Evaluation period utilized by the UE to trigger a return to the normal-mobility state from either the medium- or high-mobility states. If the criteria for either medium or high mobility are not maintained during the evaluation period, the UE returns to the normal-mobility state. IE Value

5 6 7 8 9

Allowed Range

s30, s60, s120, s180, s240

30, 60, 120, 180, 240 seconds

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

TBD

Setting Tradeoff: A high value for this parameter, corresponding to a long evaluation period, may delay the return of the UE to the normal mobility state, unnecessarily increasing the number of reselections which impacts battery life. A low value for this parameter, corresponding to a short evaluation period, may cause the UE to prematurely return to the normal-mobility state even resulting in the UE remaining camped on a weaker cell when a stringer cell is available.

10

Dependencies/Constraints:

11

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

12 13

Engineering Units

RRC Message Structure: SIB3  cellReselectionInfoCommon  speedStateReselectionPars  mobilityStateParameters  t-HystNormal

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

89

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.9.3

Cell Reselection Parameter Settings

NCR_M

Definition: The minimum number of reselections that the UE must exceed during the evaluation period TCRmax to enter the medium-mobility state. IE Value

4 5 6 7

Allowed Range

Integer[1 … 16]

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

Engineering Units

1...16 reselections

Setting Tradeoff: A high value for this parameter may delay the entry of the UE to the medium mobility state causing the UE to remain in the normal state even though mobile. A low value for this parameter may cause the UE to prematurely enter the medium mobility state, unnecessarily increasing the number of reselections which impacts battery life.

10

Dependencies/Constraints: NCR_M should be set in conjunction with NCR_M and TCRmax as these jointly impact entry into medium- and high-mobility states. Additionally, NCR_M should be set to a value lower than NCR_H.

11

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

8 9

12 13

RRC Message Structure: SIB3  cellReselectionInfoCommon  speedStateReselectionPars  mobilityStateParameters  n-CellChangeMedium

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

90

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.9.4

Cell Reselection Parameter Settings

NCR_H

Definition: The minimum number of reselections that the UE must exceed during the evaluation period TCRmax to enter the high-mobility state. IE Value

4 5 6 7

Allowed Range

Integer[1 … 16]

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

Engineering Units

1...16 reselections

Setting Tradeoff: A high value for this parameter may delay the entry of the UE to the high mobility state causing the UE to remain in the normal state even though mobile. A low value for this parameter may cause the UE to prematurely enter the high mobility state unnecessarily increasing the number of reselections which impacts battery life.

10

Dependencies/Constraints: NCR_H should be set in conjunction with NCR_M and TCRmax as these jointly impact entry into medium- and high-mobility states. Additionally, NCR_M should be set to a value lower than NCR_H.

11

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

8 9

12 13

RRC Message Structure: SIB3  cellReselectionInfoCommon  speedStateReselectionPars  mobilityStateParameters  n-CellChangeHigh

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

91

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.9.5

Qhyst Speed Dependant Scaling Factor: sf-High

2

Definition: Value added to Qhyst for reselection evaluation when the UE is in the high-mobility state.

Released - For Current Employee/Consultant Use Only

IE Value

3 4 5 6 7 8 9 10

11 12

Allowed Range

dB-6, dBd-4, dB-2, dB0

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

Engineering Units

-6, -4, -2, 0 dB

Setting Tradeoff: A smaller (more negative) value of this parameter reduces the overall hysteresis applied to the serving cell, increasing the number of reselections. The impact on battery life of an increased number of reselections versus the UE remaining on a cell which is not the best in terms of signal strength must be considered when setting this parameter. A value of 0 dB leaves the hysteresis unchanged compared to the normal-mobility state. Dependencies/Constraints: This parameter should be set in conjunction with the reselection timer scaling factor for the high mobility state as these jointly impact the reselection. Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1 RRC Message Structure: SIB3  cellReselectionInfoCommon  speedStateReselectionPars  mobilityStateParameters  q-HystSF  sf-High

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

92

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

3.9.6

Cell Reselection Parameter Settings

Qhyst Speed Dependant Scaling Factor: sf-Medium

Definition: Value added to Qhyst for reselection evaluation when the UE is in the medium-mobility state. IE Value

4 5 6 7 8 9 10

Allowed Range

dB-6, dBd-4, dB-2, dB0

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

Engineering Units

-6, -4, -2, 0 dB

Setting Tradeoff: A smaller (more negative) value of this parameter reduces the overall hysteresis applied to the serving cell, increasing the number of reselections. The impact on battery life of an increased number of reselections versus the UE remaining on a cell which is not the best in terms of signal strength must be considered when setting this parameter. A value of 0 dB leaves the hysteresis unchanged compared to the normal-mobility state. Dependencies/Constraints: This parameter should be set in conjunction with the reselection timer scaling factor for the medium mobility state as these jointly impact the reselection.

11 12

13 14

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1 RRC Message Structure: SIB3  cellReselectionInfoCommon  speedStateReselectionPars  mobilityStateParameters  q-HystSF  sf-Medium

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

93

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.9.7

Treselection Speed Dependant Scaling Factor: sf-High

2

Definition: Scaling factor for Treselection when the UE is in the high-mobility state.

Released - For Current Employee/Consultant Use Only

IE Value

3 4 5 6 7 8 9 10

Allowed Range

oDot25, oDot5, oDot75 1Dot0

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

Engineering Units

0.25, 0.5, 0.75, 1

Setting Tradeoff: A small value of this parameter reduces the value of the reselection timer when the UE is in the high-mobility state resulting in faster and more frequent reselections. The impact on battery life of an increased number of reselections versus the UE remaining on a cell which is not the best in terms of signal strength must be considered when setting this parameter. A value of 1 leaves the reselection timer unchanged compared to the normal-mobility state. Dependencies/Constraints: This parameter should be set in conjunction with the QHyst speed dependant scaling factor for the high mobility state as these jointly impact the reselection rate. Separate scaling factors can be set on a per-RAT basis.

11 12

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

13

RRC Message Structure:

14 15

SIB3  intraFreqCellReselectionInfo  t-ReselectionEUTRA-SF  SpeedStateScaleFactors  sf-High

17

SIB5  InterFreqCarrierFreqInfo  t-ReselectionEUTRA-SF  SpeedStateScaleFactors  sfHigh

18

SIB6 t-ReselectionUTRA-SF  SpeedStateScaleFactors  sf-High

19

SIB7  t-ReselectionGERAN-SF  SpeedStateScaleFactors  sf-High

16

20 21

22 23

SIB8  parametersHRPD  cellReselectionParametersHRPD  t-ReselectionCDMA2000-SF  sf-High SIB8  parameters1XRTT  cellReselectionParametersHRPD  t-ReselectionCDMA2000SF  sf-High

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

94

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Cell Reselection Parameter Settings

1

3.9.8

Treselection Speed Dependant Scaling Factor: sf-Medium

2

Definition: Scaling factor for Treselection when the UE is in the high-mobility state.

Released - For Current Employee/Consultant Use Only

IE Value

3 4 5 6 7 8 9 10

Allowed Range

oDot25, oDot5, oDot75 1Dot0

Recommended

Depends on particular deployment band (cell radius) and mobile speed.

Engineering Units

0.25, 0.5, 0.75, 1

Setting Tradeoff: A small value of this parameter reduces the value of the reselection timer when the UE is in the medium-mobility state resulting in faster and more frequent reselections. The impact on battery life of an increased number of reselections versus the UE remaining on a cell which is not the best in terms of signal strength must be considered when setting this parameter. A value of 1 leaves the reselection timer unchanged compared to the normal-mobility state. Dependencies/Constraints: This parameter should be set in conjunction with the QHyst speed dependant scaling factor for the medium mobility state as these jointly impact the reselection rate. Separate scaling factors can be set on a per-RAT basis.

11 12

Traceability: TS36.304 Sect. 5.2.4.6, TS36.331 Sect. 6.3.1

13

RRC Message Structure:

14 15

SIB3  intraFreqCellReselectionInfo  t-ReselectionEUTRA-SF  SpeedStateScaleFactors  Medium

17

SIB5  InterFreqCarrierFreqInfo  t-ReselectionEUTRA-SF  SpeedStateScaleFactors  Medium

18

SIB6 t-ReselectionUTRA-SF  SpeedStateScaleFactors  Medium

19

SIB7  t-ReselectionGERAN-SF  SpeedStateScaleFactors  Medium

16

20 21

22 23

SIB8  parametersHRPD  cellReselectionParametersHRPD  t-ReselectionCDMA2000-SF  Medium SIB8  parameters1XRTT  cellReselectionParametersHRPD  t-ReselectionCDMA2000SF  sf-Medium

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

95

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

4 PHY DL Shared Channel Operation

2

Chapter 4: Table of Contents

3

4.1 Antenna Info ........................................................................................................................................... 98

4

4.1.1 AntennaPortsCount ............................................................................................................................ 98

5

4.1.2 TransmissionMode ............................................................................................................................. 99

6

4.1.3 CodebookSubsetRestriction............................................................................................................... 101

7

4.2 PDSCH Configuration........................................................................................................................... 103

8

4.2.1 ReferenceSignalPower ........................................................................................................................ 103

9

4.2.2 p-b ......................................................................................................................................................... 104

10

4.2.3 p-a.......................................................................................................................................................... 105

11 12

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

96

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

3

The physical downlink shared channel (PDSCH) is the main bearer for all user data, as well as for broadcast system information which is not carried on the PBCH, and for paging messages, and for random access response messages.

4

When used for user data, the following transmission mode can be employed:

1 2

Released - For Current Employee/Consultant Use Only

PHY DL Shared Channel Operation

5

1. Transmission Mode 1: Transmission from a single antenna port

6

2. Transmission Mode 2: Transmission diversity

7

3. Transmission Mode 3: Open loop spatial multiplexing

8

4. Transmission Mode 4: Close loop spatial multiplexing

9

5. Transmission Mode 5: Multi-user multi-input multi-output (MU-MIMO)

10

6. Transmission Mode 6: Close loop rank-1 precoding

11

7. Transmission Mode 7: Transmission using UE-specific RS with a single spatial layer

12

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

97

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

4.1 Antenna Info

3

The antenna info includes the AntennaInfoCommon and AntennaInfoDedicated, which are used to specify the common and the UE specific antenna configuration respectively.

4

4.1.1

5

Definition: Number of cell-specific antenna ports used by the eNodeB

2

Released - For Current Employee/Consultant Use Only

PHY DL Shared Channel Operation

AntennaPortsCount IE Value

Allowed Range

Recommended

6 7 8 9 10 11 12 13

Engineering Units

ENUMERATED

Unit:

(an1, an2, an4, spare1)

Range: 1,2,4

Depends on the number of physical antennas at the eNB.

Setting Tradeoff: The larger number of cell-specific antenna ports can provide additional benefits related to gains from diversity, array and spatial multiplexing. With 2 or 4 antennas, LTE DL control channels (PBCH/PCFICH/PDCCH) can be transmitted using Transmit diversity (SFBC or SFBC+FSTD depending on number of antennas) while the data channels can be transmitted using Transmit diversity or MIMO (single or multi-user based techniques) or beamforming. These can improve control channel detection performance and significantly boost DL data rates in certain sections of the deployed network, also depending on user equipment (UE) location and mobility patterns essentially being dependent on channel conditions seen by the UE receiver (such as rank).

16

Larger numbers of cell-specific antenna ports also means deploying 2 or 4 antennas per cell and that may increase site and installation costs as well as may require careful antenna placement and network planning to realize maximum benefits.

17

Dependencies/Constraints:

14 15

18



The parameter transmissionMode should be optimized jointly.

19

Traceability: TS36.331 Sect. 6.3.2

20

RRC Message Structure:

21



22 23 24 25 26

RRCConnectionReconfiguration  MobilityControlInfo RadioResourceConfigCommon AntennaInfoCommon antennaPortsCount

Notes: Consideration of both indoor vs. outdoor/macro deployments for the multiple antennas may need to be done. To realize the maximum benefit with 4 eNodeB transmit antennas it should also be determined if user equipment is available with 4 antennas.

27

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

98

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PHY DL Shared Channel Operation

1

4.1.2

TransmissionMode

2

Definition: Identifies a specific DL transmission mode used by the eNodeB and UE

Released - For Current Employee/Consultant Use Only

IE Value Allowed Range

Engineering Units

ENUMERATED

Unit:

(tm1, tm2, tm3, tm4, tm5, tm6, tm7, spare1)

Range: 1,2,3…7

The best value should consider

Recommended

3

4 5

6 7 8 9

10 11 12

13 14 15 16 17 18

19 20 21 22 23 24

-

Number of antennas at the eNB and UE, and,

-

Specific features that eNB scheduling supports, and,

-

RF channel quality and rank

Setting Tradeoff: Different DL transmission modes are possible and their usage is dependent on the infrastructure deployment consideration such as number of antennas and specific feature support. Transmission Mode 1 which is essentially requiring only a single eNodeB antenna has the benefits of simplicity in network deployment and possibly lower cost but will not be able to achieve the peak throughputs that can be supported with transmission modes including MIMO. TM1 is not recommended. Transmission Mode 2 can be supported with 2 or 4 antennas at the eNodeB and can provide better LTE control and data channel performance owing to transmit diversity as compared to Transmission mode 1. However peak throughput rates will be same as mode 1 and lower than mode 3, 4. Transmission Mode 3 (Open-Loop Spatial multiplexing) which supports CDD SU-MIMO without requiring the UE to report PMI allows support for two code-words and peak throughput in most suitable channel conditions (two or more times that of mode 1 or 2). This technique may be more suitable for high mobility scenarios where the overhead of reporting PMI is not worthwhile. This mode does require the UE to report RI. However this technique requires static selection of codebook index by the eNodeB without any UE feedback. Transmission Mode 4 (Closed-Loop Spatial multiplexing) which supports SU-MIMO can allow for 2 code-words and corresponding peak throughput in most suitable channel conditions (such as high rank) and in low mobility/stationary conditions. However in cases where the UE is moving quickly and channel changes very quickly, the PMI reports from the UE may change very quickly and eNodeB may not always be able to condition the MIMO transmission ideally to provide the required benefit.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

99

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

3

Released - For Current Employee/Consultant Use Only

4 5

6 7 8 9

PHY DL Shared Channel Operation

Transmission mode 5 which supports MU-MIMO allows for the eNodeB to serve up to 2 users with the same resources thus improving the cell-throughput. Transmission mode 6 (Close-loop rank-1 precoding) does not require RI reports and allows the implementation of single code word MIMO, reducing the implementation complexities at both transmitter and receiver ends while sacrificing MIMO gain. Transmission mode 7 (Transmission using UE-specific RSs with a single spatial layer). UE-specific reference signals are transmitted only on the RBs where PDSCH is scheduled. This allows for a reduction of Pilot overheads and facilitates the implementation of beam forming, but provides fewer frequency domain opportunities for channel quality estimation.

10 11 12

Dependencies/Constraints: •

The parameter antennaPortsCount should be optimized jointly.

13

Traceability: TS36.331 Sect. 6.3.2

14

RRC Message Structure:

15



RRCConnectionReconfiguration  RadioResourceConfigDedicated PhysicalConfigDedicated AntennaInfoDedicated transmissionMode



RRCConnectionReestablishment  RadioResourceConfigDedicated PhysicalConfigDedicated AntennaInfoDedicated transmissionMode



RRCConnectionSetup  RadioResourceConfigDedicated PhysicalConfigDedicated AntennaInfoDedicated transmissionMode

16 17 18 19 20 21 22 23 24

Notes: Consideration of both indoor vs. outdoor/macro deployments for the multiple antennas may need to be done. To realize the maximum benefit with 4 eNodeB transmit antennas it should also be determined if user equipment is available with 4 antennas

25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

100

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7

8 9 10

11 12

13 14

4.1.3

PHY DL Shared Channel Operation

CodebookSubsetRestriction

Definition: Restricts the UE to report PMI and RI within a predefined code-book subset. This parameter is defined for different transmission modes – 3,4,5,6. The parameter is specified as a bitmap where each bit specifies whether a PMI/RI is allowed to correspond to codebook index associated with that bit. A value of 1 in the bitmap indicates that a specific rank/codebook index is allowed and value of 0 indicates that it is not allowed. The mapping of the bits in the bitmap to specific rank and codebook indices depends on position of bit from MSB to LSB. In case of Transmission Mode 3, depending on number of eNodeB antennas specified in IE, the parameter corresponds to a restriction on the rank that UE may report and thus corresponding specific codebook indices tied to rank. In case of Transmission Mode 4, depending on number of eNodeB antennas specified in IE, the parameter corresponds to a restriction on combination of rank and specific codebook index. In case of Transmission Mode 5 and 6, depending on the number of eNodeB antennas specified in IE, the parameter corresponds to rank=1 and specific codebook index. IE Value

Allowed Range

n2TxAntenna-tm3

BIT STRING (SIZE (2)),

n4TxAntenna-tm3

BIT STRING (SIZE (4)),

n2TxAntenna-tm4

BIT STRING (SIZE (6)),

n4TxAntenna-tm4

BIT STRING (SIZE (64)),

n2TxAntenna-tm5

BIT STRING (SIZE (4)),

n4TxAntenna-tm5

BIT STRING (SIZE (16)),

n2TxAntenna-tm6

BIT STRING (SIZE (4)),

n4TxAntenna-tm6

BIT STRING (SIZE (16))

Engineering Units

The best value should consider Recommended

15 16 17

-

Channel conditions

-

eNB and UE antenna configurations

Setting Tradeoff: In specific channel conditions (correlated fading scenarios) or eNodeB antenna configurations, the eNodeB may choose to restrict the UE from reporting certain rank and codebook indices. This may be effective in avoiding UE from reporting codebook indices that are not useful.

22

Apriori determination/selection of this codebook restriction may not always be suitable and given changing channel conditions experienced by the UE at different areas of the cell may not always be advantageous. Hence understanding of the network deployment configuration, radio channel conditions within the cell and areas where majority of UEs may be expected may need to be considered while defining the codebook subset restriction.

23

Dependencies/Constraints:

18 19 20 21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

101

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines



1

The parameters antennaPortsCount, transmissionMode should be optimized jointly.

3

Traceability: TS36.331 Sect. 6.3.2, TS 36.211 Sect. 6.3.4.2.1 and Sect. 6.3.4.2.2 , TS 36.213 Sect. 7.2

4

RRC Message Structure:

2

Released - For Current Employee/Consultant Use Only

PHY DL Shared Channel Operation

5



RRCConnectionReconfiguration  RadioResourceConfigDedicated PhysicalConfigDedicated AntennaInfoDedicated codebookSubsetRestriction



RRCConnectionReestablishment  RadioResourceConfigDedicated PhysicalConfigDedicated AntennaInfoDedicated codebookSubsetRestriction



RRCConnectionSetup  RadioResourceConfigDedicated PhysicalConfigDedicated AntennaInfoDedicated codebookSubsetRestriction

6 7 8 9 10 11

Notes:

12

Transmission Mode 3:

13 14 15 16 17

In a 2 transmit antenna scenario, the 2 bit, bitmap may indicate rank 2 (codebook index 0) or rank 1 (codebook index for transmit diversity) respectively. In a 4 transmit antenna scenario, bitmap may indicate rank 2,3,4 (codebook index selected from within indices 12,13,14,15 based on rank) or rank 1 (codebook index for transmit diversity). The bitmap from MSB to LSB indicates highest to lowest rank.

19

For example, if the codebookSubsetRestriction is set to ‘10’ for Transmission Mode 3 with two antennas, it means

20

-

the precoder in Table 6.3.4.2.3-1 of TS36.213 corresponding to 2 layers and codebook index 0 is available

-

the precoder for 2 antenna ports in Section 6.3.4.3 of TS36.213 is not available.

18

21 22 23 24

Transmission Mode 4:

28

In a 2 or 4 transmit antenna scenario, the corresponding 6 or 64 bit, bitmap indicates a combination of rank and codebook index. For the 6 bit case, bitmap mapping to rank/codebook index see TS 36.213 Table 7.2-1c. For the 64 bit case , bitmap the MSB 16 bits correspond to codebook indices 15 through 0 for rank=4 , the next 16 bits for codebook indices 15 through 0 for rank=3 and so on.

29

Transmission Mode 5 and 6:

25 26 27

30 31 32 33 34 35 36 37 38 39

In a 2 or 4 transmit antenna scenario, the corresponding 4 or 16 bit, bitmap indicates a rank=1 and specific codebook index. For the 4 bit case, MSB of bitmap corresponds to codebook index 3 and the LSB to codebook index 0. For the 16 bit case, MSB of bitmap corresponds to codebook index 15 and the LSB to codebook index 0. For more details related to specific rank and codebook indices for above transmission mode codebook subset restriction, see TS 36.213 Sect. 7.2 and TS36.211 - Table 6.3.4.2.3-1 and Table 6.3.4.2.3-2 in for 2 and 4 eNodeB antenna scenarios respectively. It should also be noted that in the 4 eNodeB transmit antenna case, the maximum rank may be limited to 2 and only corresponding codebook indices are relevant if the UE only supports 2 receive antennas (only Category 5 LTE UE supports 4 receive antennas).

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

102

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

4.2 PDSCH Configuration

2

4.2.1

3

Released - For Current Employee/Consultant Use Only

PHY DL Shared Channel Operation

4

ReferenceSignalPower

Definition: This parameter provides downlink reference-signal transmit power which is used to derive downlink reference-signal EPRE. The actual value is in dBm. IE Value

Engineering Units

Allowed Range

INTEGER (-60...50)

-60…50 dBm

Recommended

18-21

18-21 dBm

5

6 7 8 9

Setting Tradeoff: If the parameter is set too low, the reference signal quality at the UE may be unacceptable and negatively impact the channel estimation. This may deteriorate the demodulation performance of the various LTE channels such as PBCH, PDCCH, PDSCH which can ultimately reduce DL throughput and also UL throughput due to loss of UL grants.

11

If set too high, it will increase the interference to neighbor cells. At the same time this may reduce the power available for other LTE channels and negatively impact DL and UL throughput performance

12

Dependencies/Constraints: N/A

13

Traceability: TS 36.213 [23, 5.2]

10

14 15

16 17 18

RRC Message Structure: SIB2  RadioResourceConfigCommon  PDSCH-ConfigCommon  referenceSignalPower Notes: The downlink reference-signal transmit power is defined as the linear average over the power contributions (in [W]) of all resource elements that carry cell-specific reference signals within the operating system bandwidth.

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

103

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7

4.2.2

PHY DL Shared Channel Operation

p-b

Definition: This cell specific parameter signaled by higher layers along with number of configured eNodeB cell specific antenna ports defines cell-specific ratio ρ B / ρ A . ρ A and ρ B are the ratio of PDSCH Energy Per Resource Element (EPRE) to cell-specific Reference Signal (RS) EPRE in OFDM symbols not containing the RS and OFDM symbols containing RS respectively. As a result, this parameter effectively defines the relationship of the PDSCH EPRE in the OFDM symbols containing RS and OFDM symbols not containing RS. IE Value Allowed Range

Engineering Units

INTEGER (0, 1, 2, 3)

See the table below

0 for 1 antenna port

Recommended

1 for 2 or 4 antenna ports

8

9 10

11 12 13

Setting Tradeoff: A setting of 1 of this parameter indicates the traffic to pilot ratio is the same for OFDM symbols containing RS and not containing RS. The higher value of this parameter means the OFDM symbols containing RS get lower power than OFDM symbols not containing RS. Saving power on OFDM symbols containing RS is at the expense of the decreased demodulation performance.

15

Dependencies/Constraints: The parameter p-a and ReferenceSignalPower should be jointly optimized

16

Traceability: TS 36.213 [23, Table 5.2-1]

17

RRC Message Structure:

18

SIB2  RadioResourceConfigCommon  PDSCH-ConfigCommon  p-b

14

19 20

Notes: Based on p-b, the cell-specific ratio ρ B / ρ A for 1, 2 or 4 cell specific antenna ports is given in the below table, PB

0 1 2 3

ρB / ρA One Antenna Port 1 4/5 3/5 2/5

Two and Four Antenna Ports 5/4 1 3/4 1/2

21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

104

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

4.2.3

PHY DL Shared Channel Operation

p-a

Definition: This is a UE specific parameter provided by higher layers and is used in defining the ratio of PDSCH EPRE to cell-specific RS EPRE in the OFDM symbols without RS. IE Value Allowed Range

Recommended

4 5 6

7 8 9

Engineering Units

ENUMERATED {dB-6, dB-4dot77, dB-3, dB-1dot77,dB0, dB1, dB2, dB3 }

ENUMERATED {-6 dB, -4.77 dB, -3 dB, -1.77 dB, 0 dB, 1 dB, 2 dB, 3 dB}

dB-3 for 2 Tx

-3 dB for 2 Tx

db-6 for 4 Tx

-6 dB for 4 Tx

Setting Tradeoff: If the parameter is set high, the high PDSCH EPRE will be transmitted. The UE may have the high received PDSCH power to combat the channel fading. However, it may inject high interference to the adjacent cells. If the parameter is set low, the low PDSCH EPRE will be transmitted. The UE may have the low received PDSCH power to combat the channel fading. And it will inject less interference to the adjacent cells.

11

Dependencies/Constraints: The parameter p-b and ReferenceSignalPower should be jointly optimized

12

Traceability: TS 36.213 [23, 5.2]

13

RRC Message Structure:

10

14 15

16 17

18 19

20 21

22 23

24

25 26 27

RRCConnectionSetup RadioResourceConfigDedicated  PhysicalConfigDedicated  PDSCHConfigDedicated  p-a RRCConnectionReconfigurationRadioResourceConfigDedicated  PhysicalConfigDedicated  PDSCH-ConfigDedicated  p-a RRCConnectionReestablishmentRadioResourceConfigDedicated  PhysicalConfigDedicated  PDSCH-ConfigDedicated  p-a Notes: The UE may assume that for 16 QAM, 64 QAM, spatial multiplexing with more than one layer or for PDSCH transmissions associated with the multi-user MIMO transmission scheme,

ρ A is equal to δ power-offset + PA + 10 log10 (2) [dB] when the UE receives a PDSCH data transmission using precoding for transmit diversity with 4 cell-specific antenna ports

ρ A is equal to δ power-offset + PA [dB] otherwise Where δ power -offset is 0 dB for all PDSCH transmission schemes except multi-user MIMO, PA is a UE specific parameter provided by higher layers and ρ A is the ratio of PDSCH EPRE to cell-specific RS EPRE. 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

105

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

5 DL Scheduling Support – CQI/PMI/RI

2

Chapter 5: Table of Contents

3

5.1 Aperiodic CQI/PMI/RI Reporting on PUSCH ................................................................................. 109

4

5.1.1 Cqi-ReportModeAperiodic ................................................................................................................ 109

5

5.2 Periodic CQI/PMI/RI Reporting on PUCCH ................................................................................... 111

6

5.2.1 Introduction ......................................................................................................................................... 111

7

8

9 10

11 12 13

14

(𝟐)

5.2.2 cqi-PUCCH-ResouceIndex ( 𝒏𝑷𝑼𝑪𝑪𝑯 ) .............................................................................................. 112 5.2.3 cqi-pmi-ConfigIndex (𝑵𝒑 and 𝑵𝑶𝑭𝑭𝑺𝑬𝑻,𝑪𝑸𝑰 ) ..................................................................................... 113 5.2.4 cqi-FormatIndicatorPeriodic ............................................................................................................. 115

5.2.5 ri-ConfigIndex (𝑴𝑹𝑰 and 𝑵𝑶𝑭𝑭𝑺𝑬𝑻,𝑹𝑰) ............................................................................................... 117 5.2.6 simultaneousAckNackAndCQI ........................................................................................................ 118 5.3 Others ...................................................................................................................................................... 119 5.3.1 nomPDSCH-RS-EPRE-Offset (𝚫𝑶𝒇𝒇𝒔𝒆𝒕 ) ............................................................................................ 119

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

106

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3 4

Released - For Current Employee/Consultant Use Only

5 6 7 8

DL Scheduling Support – CQI/PMI/RI

For the downlink data scheduling and transmission in LTE, the eNB typically selects the modulation scheme, code rate, precoding matrix depending on a prediction of the downlink channel conditions. The important inputs to this scheduling and selection process are the Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI) and Rank Indicator (RI) feedback transmitted by UE in the uplink. The time and frequency resources that can be used by the UE to report CQI, PMI, and RI are controlled by the eNB. In the time domain, both periodic and aperiodic CQI/PMI/RI reporting is supported. The periodic reporting is transmitted on PUCCH, and the aperiodic reporting is on PUSCH.

9

10

CQI Reporting

13

CQI is an indication of the modulation scheme and code rate which can be supported by the channel, taking into account the channel quality (i.e., SINR) and the characteristics of the UE’s receiver. Three types of CQI reporting are supported in LTE:

14



15

A single CQI value is obtained over the entire bandwidth, and can be reported in PUSCH or PUCCH.

16



11 12

Wideband CQI: Higher Layer Configured Subband CQI:

18

A wideband CQI value for the entire bandwidth and a CQI value for each subband are obtained, and can be reported in PUSCH.

19



17

20 21 22 23 24 25 26

27 28 29 30 31

UE Selected Subband CQI o PUSCH Reports The UE selects M preferred subbands within the sebband set S. One wideband CQI and one CQI value reflecting the average of the M selected subbands are reported. o PUCCH Reports The UE selects the preferred subband within the set of Nj subbands in each of J bandwidth parts (BPs). One wideband CQI value and one CQI value reflecting transmission only over the selected subband of a BP are reported.

PMI Reporting For transmission modes 4, 5, and 6, precoding feedback is used for channel dependent codebook based precoding and relies on UEs reporting precoding matrix indicator (PMI). The precoding matrix, whose index constitutes the PMI report, is the precoder than maximizes the aggregate number of data bits which could be receiced across all layers.

34

The same subband definitions for CQI reporting hold for PMI reporting. The number (and positions) of frequency-resources that a single UE PMI report represent is directly associated to the configured wideband or subband CQI report type.

35

UE PMI reports can be of the following types

32 33

36

-

PUSCH Reports: no-PMI/single-PMI/multiple-PMI

37

-

PUCCH Reports: no-PMI/single-PMI

38 39

The eNB may restrict the set of precoders which the UE may evaluate and report. This is known as Codebook Subset Restriction.

40 41

RI Reporting

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

107

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

DL Scheduling Support – CQI/PMI/RI

The channel rank (or the number of useful transmission layers) can be reported by the UE via Rank Indicator (RI), which is calculated to maximize the capacity over the entire bandwidth with jointly selected the PMI.

Released - For Current Employee/Consultant Use Only

4

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

108

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

5.1 Aperiodic CQI/PMI/RI Reporting on PUSCH

3

Upon receiving a DCI format 0 or a Random Access Response Grant and its respective CQI request field is set to 1, the UE shall report the aperiodic CQI, PMI and RI using the PUSCH.

4

5.1.1

5

Definition: The aperiodic CQI/PMI/RI reporting mode.

2

Released - For Current Employee/Consultant Use Only

DL Scheduling Support – CQI/PMI/RI

Cqi-ReportModeAperiodic IE Value

Allowed Range

Recommended

Engineering Units

rm12, rm20, rm22, rm30, rm31

Mode 1-2. Mode 2-0, Mode 2-2, Mode 3-0, Mode 3-1

- The best value should consider the transmission mode and scheduling capability of eNB.

TBD

- To make better use of available resources, it is suggested to configure frequency-selective scheduling.

6 7

Setting Tradeoff:

8

CQI

9 10 11 12 13 14 15 16 17

If the parameter is set to wideband feedback type, a single CQI is reported for the entire bandwidth. The lower feedback overhead is in the uplink. However, the CQI may not well reflect the channel quality of each subband. If the parameter is set to Higher Layer configured subband, a wideband CQI for the entire bandwidth and a subband CQI for each subband are reported. This gives eNB more flexibility for scheduling but with more uplink overhead. If the parameter is set to UE selected subband feedback type, a wideband CQI for the entire bandwidth and a subband CQI for each UE selected subband are reported. This gives eNB less flexibility for scheduling than Higher Layer configured subband, but with less uplink overhead.

19

Both the Higher layer configured subband and UE selected subband can provide the additional gain than the Wideband CQI.

20

PMI

21

For transmission mode 1, 2, 3 and 7, no PMI is required.

18

22 23 24 25 26

If the parameter is set to the Single PMI, a single PMI is selected from the codebook subset assuming transmission on the entire bandwidth. This may not give the best PMI selection for each subband, but with lower uplink overhead. If the parameter is set to the Multiple PMI, a selected PMI on each subband is reported. This gives the best PMI selection for each subband, but with more uplink overhead.

27 28

Dependencies/Constraints: 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

109

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

Traceability: TS 36.213 Sect. 7.2.1

3

RRC Message Structure: RRC Connectionsetup/RRC ConnectionReconfiguration physicalConfigDedicated  cqi-ReportConfig  cqi-ReportModeAperiodic

4

Notes:

2

5 6 7

A UE is semi-statically configured by higher layers to feed back CQI and PMI and corresponding RI on the same PUSCH using one of the following reporting modes given in Table 5-1 and described below.

8 9

Table 5-1 CQI and PMI Feedback Types for PUSCH reporting Modes PMI Feedback Type Single Multiple No PMI PMI PMI Wideband (wideband CQI)

PUSCH CQI Feedback Type

Released - For Current Employee/Consultant Use Only

DL Scheduling Support – CQI/PMI/RI

UE Selected (subband CQI) Higher Layerconfigured (subband CQI)

Mode 1-2

Mode 2-0

Mode 3-0

Mode 2-2

Mode 3-1

10 11

For each of the transmission modes, the following reporting modes are supported on PUSCH:

12

Transmission mode 1

: Modes 2-0, 3-0

13

Transmission mode 2

: Modes 2-0, 3-0

14

Transmission mode 3

: Modes 2-0, 3-0

15

Transmission mode 4

: Modes 1-2, 2-2, 3-1

16

Transmission mode 5

: Mode 3-1

17

Transmission mode 6

: Modes 1-2, 2-2, 3-1

18

Transmission mode 7

: Modes 2-0, 3-0

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

110

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

5.2 Periodic CQI/PMI/RI Reporting on PUCCH

2

5.2.1

3

Released - For Current Employee/Consultant Use Only

DL Scheduling Support – CQI/PMI/RI

4

Introduction

The UE can be semi-statically configured by eNB to periodically feedback the CQI/PMI/RI on the PUCCH. Only wideband and UE-selected subband feedback is available.

5 6 7 8 9 10 11

Wideband CQI/PMI Reporting: The wideband CQI/PMI reporting instance is sent every NP sub-frames. The initial subframe position within a frame for this report is controlled by NOFFSET,CQI (in subframes) The RI reporting instance is sent every an integer multiple MRI of wideband CQI/PMI period NP (in subframes). And NOFFSET,RI is the corresponding relative RI offset to the wideband CQI/PMI reporting offset (in subframes).

12 13

Both Wideband CQI/PMI & Subband CQI Reporting:

15

The Subband CQI reporting instance is sent every NP sub-frames with a NOFFSET,CQI. The Wideband CQI reporting instances is sent every H*NP sub-frames with a NOFFSET,CQI

16

The RI reporting instances is sent every MRI *H*NP sub-frames with a NOFFSET,RI.

14

17 18 19 20

The parameters NP, K, MRI, NOFFSET,RI are configured by higher layers. H=J·K where J is the number of Bandwidth Parts and the parameter K is selected from the set {1, 2, 3, 4}, and the parameter NOFFSET,RI is selected from the set {0, -1, …,-( NP -1), - NP }.

21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

111

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

5.2.2

DL Scheduling Support – CQI/PMI/RI

(𝟐)

cqi-PUCCH-ResouceIndex ( 𝒏𝑷𝑼𝑪𝑪𝑯 )

Definition: The parameter defines which resource block for transmission of PUCCH Format 2 (CQI/PMI/RI). IE Value

Allowed Range

0.. 1185

Recommended

No recommendation needed since eNB may assign different position according to the number of users.

Engineering Units

0.. 1185

4

6

Setting Tradeoff: If this parameter is set high, it allows more users to report CQI/PMI/RI and ACK/NACK in a subframe, but at the expense of available PUSCH resource.

7

Dependencies/Constraints:

8

Traceability: TS 36.213 Sect. 7.2.

5

11

RRC Message Structure: RRC Connectionsetup/RRC ConnectionReconfiguration physicalConfigDedicated  cqi-ReportConfig  cqi-ReportPeriodic setup  cqi-PUCCHResourceIndex

12

Notes: None.

9 10

13 14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

112

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

5.2.3

DL Scheduling Support – CQI/PMI/RI

cqi-pmi-ConfigIndex (𝑵𝒑 and 𝑵𝑶𝑭𝑭𝑺𝑬𝑻,𝑪𝑸𝑰 )

Definition: The parameter defines the periodicity and offset configuration for the transmission of CQI/PMI.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

Engineering Units

0.. 1023

0.. 1023

-

The appropriate value depends on the type of services, expected scheduling rate to guarantee the required QoS, and the mobility.

-

Anything below 5ms is meaningless because of the delay between reporting and scheduling (In general, 10ms below is not recommended.)

4 5 6 7 8 9 10 11 12

13 14 15

Setting Tradeoff: If the parameter is set too low (i.e., small 𝑁𝑝 ), the UE reports the CQI/PMI more frequently. This gives the eNB more accurate channel state information and better reflects the changes of channel quality. However, it leads to higher feedback overhead in the uplink. If the parameter is set too high (i.e., large 𝑁𝑝 ), the UE reports the CQI/PMI less frequently. This gives the lower feedback overhead in the uplink. However, the eNB may have less accurate channel state information and the reports may not well reflect the changes of channel quality. For BE full-buffer traffic, to make sure that eNodeB can track the change of fading channel, the CQI/PMI reporting periodicity should be less than or equal to the coherent time 𝑇𝑐 of the channel, i.e., 𝑁𝑝 (𝑚𝑠) ≤ 𝑇𝑐 ≅

9𝑐 16𝜋𝑣𝑓𝑐

where c is the light speed, v is the mobile speed and 𝑓𝑐 is the carrier frequency. For example, if the carrier frequency 𝑓𝑐 = 700 MHz, the relation between coherent time 𝑇𝑐 and mobile speed v is given by Tc (ms) 1 2 5 10 20 32 40 64 80 128 160

80-W3835-1 Rev. A

v (km/h) 276.2 138.1 55.2 27.6 13.8 8.6 6.9 4.3 3.5 2.2 1.7

v (mph) 172.7 86.3 34.5 17.3 8.6 5.4 4.3 2.7 2.2 1.3 1.1

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

113

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

DL Scheduling Support – CQI/PMI/RI

For other QoS traffic, the characteristics of the QoS should be taken into consideration. For instance, for BE traffic, if mobile speed ≤ 8.6 mph, 𝑁𝑝 can be set to 20 subframes (or 20ms).

4

Dependencies/Constraints:

5

Traceability: TS 36.213 Sect. 7.2.

7

RRC Message Structure: RRC Connectionsetup/RRC ConnectionReconfiguration physicalConfigDedicated  cqi-ReportConfig  cqi-ReportPeriodic setup  cqi-pmi-ConfigIndex

8

Notes:

9

Table 5-2 Mapping of cqi-pmi-ConfigIndex to NP and NOFFSET,CQI for FDD.

6

cqi-pmi-ConfigIndex = ICQI/PMI

Value of NP

Value of NOFFSET,CQI

0 ≤ ICQI/PMI ≤ 1

2

ICQI/PMI

2 ≤ ICQI/PMI ≤ 6

5

ICQI/PMI – 2

7 ≤ ICQI/PMI ≤ 16

10

ICQI/PMI – 7

17 ≤ ICQI/PMI ≤ 36

20

ICQI/PMI – 17

37 ≤ ICQI/PMI ≤ 76

40

ICQI/PMI – 37

77 ≤ ICQI/PMI ≤ 156

80

ICQI/PMI – 77

157 ≤ ICQI/PMI ≤ 316

160

ICQI/PMI – 157

ICQI/PMI = 317 318 ≤ ICQI/PMI ≤ 349

Reserved 32

ICQI/PMI – 318

350 ≤ ICQI/PMI ≤ 413

64

ICQI/PMI – 350

414 ≤ ICQI/PMI ≤ 541

128

ICQI/PMI – 414

542 ≤ ICQI/PMI ≤ 1023

Reserved

10 11

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

114

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

DL Scheduling Support – CQI/PMI/RI

1

5.2.4

cqi-FormatIndicatorPeriodic

2

Definition: The parameter defines PUCCH CQI feedback type.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

Engineering Units

{WidebandCQI: NULL,

{WidebandCQI: Null,

SubbandCQI: SEQUENCE{

SubbandCQI: SEQUENCE{

k, (1..4)} *

k, (1..4)}

}

}

- The best value should consider the transmission mode and scheduling capability of eNB. - To make better use of available resources, it is suggested to configure frequency-selective scheduling.

3 4 5 6 7 8 9 10

Setting Tradeoff: If the parameter is set to WidebandCQI, a single CQI/PMI is reported for the entire bandwidth. The lower feedback overhead is in the uplink. However, the CQI/PMI may not well reflect the channel quality of each bandwidth part. If the parameter is set to SubbandCQI, a Wideband CQI/PMI for the entire bandwidth and a subband CQI/PMI for the selected subband within a bandwidth part are reported. This gives the eNB the better knowledge of most favorite frequency bands the UE expects. The higher feedback overhead is transmitted in the uplink for this type.

12

For the PMI feedback type, it will be implicitly indicated by the transmission mode and CQI reporting type.

13

Dependencies/Constraints:

14

Traceability: TS 36.213 Sect. 7.2.

11

17

RRC Message Structure: RRC Connectionsetup/RRC ConnectionReconfiguration physicalConfigDedicated  cqi-ReportConfig  cqi-ReportPeriodic setup  cqiFormatIndicatorPeriodic

18

Notes:

19

* k (or K) is the repeat cycle for subband CQI reporting.

15 16

20 21

A UE is semi-statically configured by higher layers to periodically feedback different CQI, PMI, and RI on the PUCCH using the reporting modes given in Table 5-3 and described below.

22 23 24 25 26

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

115

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

DL Scheduling Support – CQI/PMI/RI

Table 5-3 CQI and PMI Feedback Types for PUCCH reporting Modes

PUCCH CQI Feedback Type

Released - For Current Employee/Consultant Use Only

PMI Feedback Type

Wideband

No PMI

Single PMI

Mode 1-0

Mode 1-1

Mode 2-0

Mode 2-1

(wideband CQI)

UE Selected (subband CQI)

2

For each of the transmission modes, the following reporting modes are supported on PUCCH:

3

Transmission mode 1

: Modes 1-0, 2-0

4

Transmission mode 2

: Modes 1-0, 2-0

5

Transmission mode 3

: Modes 1-0, 2-0

6

Transmission mode 4

: Modes 1-1, 2-1

7

Transmission mode 5

: Modes 1-1, 2-1

8

Transmission mode 6

: Modes 1-1, 2-1

9

Transmission mode 7

: Modes 1-0, 2-0

10 11

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

116

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

DL Scheduling Support – CQI/PMI/RI

ri-ConfigIndex (𝑴𝑹𝑰 and 𝑵𝑶𝑭𝑭𝑺𝑬𝑻,𝑹𝑰 )

1

5.2.5

2

Definition: The parameter defines the periodicity and offset configuration for the transmission of RI.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range Recommended

Engineering Units

0.. 1023

0.. 1023

322-482 if Np = 20ms

322

161-321 if Np = 40ms

3 4 5 6 7 8 9

Setting Tradeoff: If the parameter is set too low, the UE reports the RI more frequently. This gives the eNB more frequent channel rank information and better reflects the changes of channel rank. However, it leads to higher feedback overhead in the uplink. If the parameter is set too high, the UE reports the RI less frequently. The eNB may have less frequent channel rank information and the reports may not well reflect the changes of channel rank. But his gives the lower feedback overhead in the uplink.

10

Dependencies/Constraints:

11

Traceability: TS 36.213 Sect. 7.2

13

RRC Message Structure: RRC Connectionsetup/RRC ConnectionReconfiguration physicalConfigDedicated  cqi-ReportConfig  cqi-ReportPeriodic setup  ri-ConfigIndex

14

Notes:

15

Table 5-4 Mapping of ri-ConfigIndex to MRI and NOFFSET,RI.

12

ri-ConfigIndex = IRI

Value of MRI

Value of NOFFSET,RI

0 ≤ IRI ≤ 160

1

−IRI

161 ≤ IRI ≤ 321

2

− (IRI – 161)

322 ≤ IRI ≤ 482

4

− (IRI – 322)

483 ≤ IRI ≤ 643

8

− (IRI – 483)

644 ≤ IRI ≤ 804

16

− (IRI – 644)

805 ≤ IRI ≤ 965

32

− (IRI – 805)

966 ≤ IRI ≤ 1023

Reserved

16

17 18 19

The RI will be reported every 𝑀𝑅𝐼 ∙ 𝐻 ∙ 𝑁𝑝 subframes where 𝐻 = 𝐽 ⋅ 𝐾, 𝐽 is the number of bandwidth parts and 𝐾 is signaled by higher layer; 𝑁𝑝 is defined by cqi-pmi-ConfigIndex. Industry common accepted setting for this parameter is 4.

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

117

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

5.2.6

DL Scheduling Support – CQI/PMI/RI

simultaneousAckNackAndCQI

Definition: The parameter defines whether the simultaneous transmission of ACK/NACK and CQI is allowed.

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Units

Allowed Range

Boolean

Boolean

Recommended

FALSE

FALSE

4 5 6 7 8 9

Setting Tradeoff: If the parameter is set to TRUE, the simultaneous transmission of ACK/NACK and CQI/PMI/RI is allowed, but the reliability of ACK/NACK decreases. If the parameter is set to FALSE, the simultaneous transmission of ACK/NACK and CQI/PMI/RI is not allowed. In case of need of simultaneous transmission of CQI/PMI/RI and ACK/NACK in a same subframe, CQI/PMI/RI is dropped. The reliability of ACK/NACK increases.

10 11

Dependencies/Constraints:

12

Traceability: TS 36.213 Sect. 7.2

15

RRC Message Structure: RRC Connectionsetup/RRC ConnectionReconfiguration physicalConfigDedicated  cqi-ReportConfig  cqi-ReportPeriodic setup  simultaneousAckNackAndCQI

16

Notes: None.

13 14

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

118

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

DL Scheduling Support – CQI/PMI/RI

1

5.3 Others

2

5.3.1

3

Definition: The parameter affects the ratio of PDSCH EPRE to cell-specific EPRE.

nomPDSCH-RS-EPRE-Offset (𝚫𝑶𝒇𝒇𝒔𝒆𝒕 ) IE Value

Engineering Units

Allowed Range

-1..6

(-1..6)*2dB

Recommended

0 except MU MIMO

0 except MU MIMO

4 5 6 7 8

Setting Tradeoff: This parameter should be set to 0 except MU MIMO as defined in TS 36.213. For MU MIMO, if the parameter is set to too low, the UE may not be able to decode the PDSCH due to the low power of PDSCH RE. If the parameter is set to too high, it may generate high inter-cell interference.

9 10

Dependencies/Constraints:

11

Traceability: TS 36.213 Sect. 7.2.3

13

RRC Message Structure: RRC Connectionsetup/RRC ConnectionReconfiguration physicalConfigDedicated  cqi-ReportConfig  nomPDSCH-RS-EPRE-Offset

14

Notes: None

12

15 16 17 18 19

In the case of MU-MIMO, the total available power will typically be divided between the transmissions to the different UEs, with less PDSCH power available for each transmission. However, the UEs are unaware of the presence of parallel transmissions to other UEs and are thus not aware of any PDSCH power reduction. Therefore, for MU MIMO (transmission mode 5), the explicit signaling of power offset is needed.

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

119

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

2

6 Physical Uplink Shared Channel (PUSCH)

3

Chapter 6: Table of Contents

4

6.1 PUSCH frequency hopping .................................................................................................................. 121

5

6.1.1 n-SB ....................................................................................................................................................... 122

6

6.1.2 hoppingMode ...................................................................................................................................... 123

7

6.1.3 Pusch-HoppingOffset ......................................................................................................................... 124

8

6.2 PUSCH Modulation ............................................................................................................................... 125

9

6.2.1 enable64QAM ...................................................................................................................................... 127

10

6.3 PUSCH Demodulation Reference Signal ............................................................................................ 128

11

6.3.1 GroupHoppingEnabled ..................................................................................................................... 129

12 13

6.3.2 GroupAssignmentPUSCH (𝚫𝒔𝒔 ) ....................................................................................................... 131 6.3.3 SequenceHoppingEnabled ................................................................................................................ 132

14

6.3.4 CyclicShift ............................................................................................................................................ 133

15

6.4 Transmission of Control Signaling on PUSCH .................................................................................. 135

16

6.4.1 betaOffset-ACK-Index ........................................................................................................................ 135

17

6.4.2 betaOffset-RI-Index............................................................................................................................. 137

18

6.4.3 betaOffset-CQI-Index ......................................................................................................................... 139

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

120

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

5

Physical Uplink Shared Channel (PUSCH) is used to carry on the uplink user data. Control fields can also be multiplexed with uplink data. QPSK, 16QAM and 64QAM are the modulation schemes supported on PUSCH. PUSCH is mapped to physical resource blocks in different ways depending on whether uplink frequency hopping is enabled or not. The mapping also differs for different types of hopping if uplink frequency hopping is enabled.

6

6.1 PUSCH frequency hopping

1 2 3 4

Released - For Current Employee/Consultant Use Only

Physical Uplink Shared Channel (PUSCH)

7 8 9 10

Hopping in frequency can be performed on PUSCH (Physical Uplink Shared Channel). 3GPP specifies two types of frequency hopping for the LTE uplink, Type 1 PUSCH Hopping and Type 2 PUSCH Hopping.

11 12 13 14 15 16

DCI format 0 is used to transport scheduling information for the uplink. It has a 1 bit hopping flag to indicate whether PUSCH frequency hopping is enabled or not. Thus a UE with a scheduling grant performs frequency hopping if this hopping flag is set to 1. Depending on the system bandwidth, 1 or 2 bits are included from the resource allocation field in DCI format 0 as shown in Table 8.1-1 in case of hopping.

17 18

Table 8.1-1: Number of Hopping Bits NUL_hop vs. System Bandwidth System BW

N UL RB 6-49 50-110

#Hopping bits for 2nd slot RA (NUL_hop) 1 2

19 20 21 22 23 24 25 26 27 28 29 30 31 32

Type 1 PUSCH Hopping – Simpler hopping patterns (two or four possible hopping positions based on hopping bits) The hopping bits sent on the PDCCH specify the hopping distance. For large bandwidths 00, 01, 10 specify different hopping positions corresponding to ¼, -¼ and ½ of UL bandwidth. The hoping bits only specify the position of the 2nd slot with respect to the 1st. Hence, if three consecutive subframes have 00, 01,10 assigned respectively with same UL RB resources, in all subframes the first slot is at the same position but the 2nd slot is at a different position corresponding to either 00, 01, or 10. The number of UL contiguous RBs allowed in the hopping case is limited and is a function of the UL system bandwidth. Type 2 PUSCH Hopping – More complex hopping patterns (mirroring within sub-bands or pseudorandom sequence based hopping positions). The hopping bandwidth is virtually divided into a certain n-SB number of sub-bands of equal width. A UE cannot be allocated on RBs that are in different sub-bands.

33 34 35 36

In each type of PUSCH hopping, there is a possibility to hop in frequency between subframes, inter-subframe hopping, or within a subframe, intra-subframe hopping depending on single bit information provided from higher layers in the hoppingMode parameter.

37 38

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

121

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Physical Uplink Shared Channel (PUSCH)

1

6.1.1

n-SB

2

Definition: number of sub-bands defined in type 2 PUSCH hopping

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Engineering Units

INTEGER

INTEGER

(1, 2, 3, 4)

(1, 2, 3, 4)

If peak throughput is a concern, set it to 1 to disable hopping.

Recommended

If SRS is enabled, recommend to use the best portion of the channel instead of hopping (i.e., set it to 1 to disable hopping). Set it to larger value (>1) to mitigate the inter-cell interference and combat the deep fading in consecutive transmission. (see notes)

6

Setting Tradeoff: Higher value increase frequency diversity in terms of frequency hopping zones but shorten the length of contiguous RBs that can be allocated for a single user. Lower values reduce the frequency diversity in terms of frequency hopping zones but widen the length of contiguous RBs that can be allocated for a single user.

7

Dependencies/Constraints: none

8

Traceability: TS36.331 Sect. 6.3.2, and TS36.211 Sect. 5.3.4

9

RRC Message Structure:

3 4 5

11

SystemInformationBlockType2  radioResourceConfigCommon  pusch-ConfigCommon puschConfigBasic n-SB

12

Notes:

10

13 14 15 16 17

Since a UE cannot be allocated on RBs that are in different sub-bands even though there are free RBs, there is a limitation in the UL scheduler when multiple sub-bands are assigned. However, in this case, HARQ transmissions also perform hopping in frequency from one transmission attempt to the other, thus, the probability of hitting a deep fade in a fading mobile radio channel in consecutive slots is very less. As a result a hopping user experiences better frequency diversity than a non-hopping user.

21

On the other hand, in the hopping with Nsb = 1 and non-hopping cases, HARQ transmissions are transmitted on the same resource blocks as in the previous transmission attempt and hence there is a chance of being in deep fades in consecutive transmission attempts unless the channel changes in between, which may be unlikely especially for slowly moving UEs.

22

If peak throughput is a concern, recommend to set it to 1 to disable the frequency hopping.

18 19 20

23 24

If SRS is enabled, to maximize the scheduling efficiency and throughput, it is recommend to set it to 1 to disable the frequency hopping.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

122

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

6.1.2

Physical Uplink Shared Channel (PUSCH)

hoppingMode

Definition: hoppingMode indicates the hopping mode of the PUSCH, whether hopping is “intersubframe” or “intra and inter-subframe”. IE Value

Engineering Units

ENUMERATED

ENUMERATED

Allowed Range

(interSubFrame, intraAndInterSubFrame)

(interSubFrame, intraAndInterSubFrame)

Recommended

interSubFrame

6

Setting Tradeoff: Intra-subframe hopping provides frequency diversity within a codeword (i.e. within a single transmission of transport block) while inter-subframe hopping provides frequency diversity between HARQ retransmissions of a transport block.

7

Dependencies/Constraints: none

8

Traceability: TS36.331 Sect. 6.3.2, and TS36.211 Sect. 5.3.4

9

RRC Message Structure:

4 5

11

SystemInformationBlockType2  radioResourceConfigCommon  pusch-ConfigCommon puschConfigBasic  hoppingMode

12

Notes:

10

13 14

Frequency hopping is used to provide frequency diversity when no or limited frequency-specific channel quality information is available (e.g. high Doppler conditions, SRS overhead constraints).

15 16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

123

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

6.1.3

Physical Uplink Shared Channel (PUSCH)

Pusch-HoppingOffset

Definition: The offset used for PUSCH frequency hopping, expressed in number of resource blocks (set by higher layers). It indirectly limits the number of resource blocks reserved for PUCCH when PUSCH hopping is enabled. IE Value

5 6 7 8

Allowed Range

INTEGER (0..98)

Recommended

A positive number (see notes) if PUSCH hopping is enabled.

Engineering Units

INTEGER (0..98)

Setting Tradeoff: If this parameter is set too high, there will be fewer resources left for PUSCH which will impact the total data throughput in the uplink. If it is too low, there may be PUCCH congestion which can impact user performance by not allowing the UE to report HARQ ACK/NACK, CQI or Scheduling Requests.

11

Dependencies/Constraints: When PUSCH hopping is enabled, this parameter should be optimized (2) (1) together with deltaPUCCH-Shift( ∆PUCCH ), nRB-CQI ( N RB ), nCS-An( N cs(1) ), n1Pucch-AN ( N PUCCH shift ).

12

Traceability: TS36.331 Sect. 6.3.2; TS36.211 Sect. 5.3.4

13

RRC Message Structure:

9 10

15

SystemInformationBlockType2  PhysicalConfigDedicated  PUSCH-ConfigCommon  puschConfigBasic  pusch-HoppingOffset

16

Notes:

14

17 18 19 20 21 22

When PUSCH hopping is enabled, this parameter should be set greater than the number of RBs reserved for PUCCH format 1/1a/1b and 2/2a/2b by a set of PUCCH parameters deltaPUCCH-Shift( (1) (2) (1) ), nRB-CQI ( N RB ), nCS-An( N cs(1) ), n1Pucch-AN ( N PUCCH ). For instance, if 𝑁𝑃𝑈𝐶𝐶𝐻 = ∆PUCCH shift (2)

𝑈𝐿 6, 𝑁𝑁𝐵 = 2, Δ𝑃𝑈𝐶𝐶𝐻 𝑠ℎ𝑖𝑓𝑡 = 2, 𝑁 𝑁𝐵 = 50 for normal CP, then total 6 RBS per PUCCH region (3 RBs per 𝐻𝑂 slot) have been reserved for PUCCH. Therefore, PUSCH hopping ofsset (𝑁𝑅𝐵 ) should be set 6.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

124

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

6.2 PUSCH Modulation

2

For 0 ≤ I MCS ≤ 28 , the modulation order ( Q m ) is determined as follows:

3 4

Released - For Current Employee/Consultant Use Only

Physical Uplink Shared Channel (PUSCH)

5 6 7

8 9

10 11 12 13 14 15 16

17 18

− If the UE is capable of supporting 64QAM in PUSCH and has not been configured by higher layers to transmit only QPSK and 16QAM, the modulation order is given by Q m' in Table 6-1. − If the UE is not capable of supporting 64QAM in PUSCH or has been configured by higher layers to transmit only QPSK and 16QAM, Q m' is first read from Table 8.2.-1. The modulation order is set to Qm = min(4, Qm' ) . − If the parameter ttiBundling provided by higher layers is set to TRUE, then the resource allocation size is restricted to N PRB ≤ 3 and the modulation order is set to Q m = 2 . For 29 ≤ I MCS ≤ 31 , if I MCS = 29 , the “CQI request” bit in DCI format 0 is set to 1 and N PRB ≤ 4 , the modulation order is set to Qm = 2 . Otherwise, the modulation order shall be determined from the DCI transported in the latest PDCCH with DCI format 0 for the same transport block using 0 ≤ I MCS ≤ 28 . If there is no PDCCH with DCI format 0 for the same transport block using 0 ≤ I MCS ≤ 28 , the modulation order shall be determined from − the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport block is semi-persistently scheduled, or, − the random access response grant for the same transport block, when the PUSCH is initiated by the random access response grant.

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

125

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

1

Physical Uplink Shared Channel (PUSCH)

Table 6-1 Modulation, TBS index and redundancy version table for PUSCH MCS Index

Modulation Order

TBS Index

I MCS

Q m'

I TBS

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

2 2 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 4 6 6 6 6 6 6 6 6

0 1 2 3 4 5 6 7 8 9 10 10 11 12 13 14 15 16 17 18 19 19 20 21 22 23 24 25 26 reserved

Redundancy Version rvidx 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 2 3

2 3

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

126

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Physical Uplink Shared Channel (PUSCH)

1

6.2.1

enable64QAM

2

Definition: Indicates whether 64QAM is allowed in uplink (TRUE) or not allowed (FALSE).

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Engineering Units

BOOLEAN

BOOLEAN

(TRUE, FALSE)

(TRUE, FALSE)

Dependent on UE category: Recommended

FALSE for category 4 and below TRUE for category 5

5

Setting Tradeoff: If enabled and UE is cat 5 it permits UE to select 64QAM in uplink. If enabled and UE is lower than cat 5 it permits to send transport blocks with higher size but with 16QAM modulation. If it is disabled, it prevents UE from using MCS higher than 20.

6

Dependencies/Constraints: none

7

Traceability: TS36.331 Sect. 6.3.2, and TS36.213 Sect. 8.6.1

8

RRC Message Structure:

3 4

10

SystemInformationBlockType2  radioResourceConfigCommon  pusch-ConfigCommon  enable64QAM

11

Notes:

9

12 13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

127

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

6.3 PUSCH Demodulation Reference Signal

2

1. Group Hopping

4

The sequence-group number u in slot ns is defined by a group hopping pattern fgh (ns ) and a sequenceshift pattern fss according to

5

u=

3

Released - For Current Employee/Consultant Use Only

Physical Uplink Shared Channel (PUSCH)

6 7 8 9 10

(fgh (ns ) + fss )mod 30

There are 17 different hopping patterns and 30 different sequence-shift patterns. Sequence-group hopping can be enabled or disabled by means of parameter groupHoppingEnabled. PUCCH and PUSCH have the same hopping pattern but may have different sequence-shift patterns. The difference between the sequence-shift pattern for PUCCH f ssPUCCH and the sequence-shift pattern for PUSCH

f ssPUSCH modulo 30 is configured by parameter groupAssignmentPUSCH.

11 12 13 14 15 16

17 18

19

20

2. Sequnece hopping The parameter Sequence-hopping-enabled determines if sequence hopping is enabled or not. Sequence hopping only applies for reference-signals of length M scRS ≥ 6N scRB . For reference-signals of length M scRS < 6N scRB , the base sequence number v within the base sequence group is given by v=0. For reference-signals of length M scRS ≥ 6N scRB , the base sequence number v within the base sequence group in slot ns is defined by

c(n ) if group hopping is disabled and sequence hopping is enabled v= s otherwise 0 where c(i ) is the pseudo-random sequence.

21 22

23

24

3. Zadoff sequence For DMRS, the Zadoff sequence ru(,αv ) (n ) is used, where the cyclic shift α in a slot ns is given as α = 2π ncs /12 with

ncs =

25

26

27

(n

(1) DMRS

)

(2) + nDMRS + nPRS (ns ) mod12

where the values of n (1) is calculated according to the parameter cyclicShift provided by higher DMRS layers.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

128

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Physical Uplink Shared Channel (PUSCH)

1

6.3.1

GroupHoppingEnabled

2

Definition: Enable (TRUE) or disable (FALSE) the sequence-group hopping

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range Recommended

Engineering Units

BOOLEAN

BOOLEAN

(TRUE, FALSE)

(TRUE, FALSE)

TRUE

TRUE

7

Setting Tradeoff: Setting the value to TRUE will imply that the hopping of sequence groups is enabled, which permits interference randomization between different cells. Setting the value to FALSE will imply that the same sequence-group number is used in all slots of a radio frame and is obtained from the sequence group shift offset. This setting can be used to perform a sequence-group planning with up to 30-sequence-group plan groupHoppingEnabled.

8

Dependencies/Constraints: none

9

Traceability: TS36.331 Sect. 6.3.2, and TS36.211 Sect. 5.5.1.4.

3 4 5 6

10

RRC Message Structure:

12

SystemInformationBlockType2  radioResourceConfigCommon  pusch-ConfigCommon  UL-ReferenceSignalsPUSCH  groupHoppingEnabled

13

Notes:

11

14 15

A two-layered hopping/shifting pattern generation method with 17 root hopping patterns and 30 sequence shifts as illustrated in Figure 6-1 has been defined.

16

17 root hopping patterns Hopping #1 Hopping #2 (= no hopping)

Hopping #17

30 sequence shifts

Generated 510 hopping/shifting patterns

Shifts #1 ~ #30 Shifts #1 ~ #30

Shifts #1 ~ #30

#1 ~

~ #510

17 18

19 20 21 22 23

Figure 6-1 A two-layered hopping/shifting pattern generation method These sequence shifted version of the same root hopping pattern can be allocated to the cells belonging to a coordinated cell cluster, i.e., planning, as shown in Figure 6-2(b). Therefore, between the cells within the coordinated cell cluster, the inter-cell interference of the RS is minimized thanks to a lack of RS sequence collisions due to sequence shifting. Meanwhile, between the cell clusters, the RS sequence collisions are randomized using different root hopping patterns.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

129

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Physical Uplink Shared Channel (PUSCH)

Cell cluster 1  Use root hopping pattern 1 Shift 1

Shift 6

Released - For Current Employee/Consultant Use Only

Shift 3 Shift 7

Shift 6

Shift 3 Shift 7 Shift 9

Shift 9

Shift 1

Shift 5

Shift 10

Shift 2

Shift 4

Shift 8

Shift 5

Shift 10

Shift 2

Shift 4

Shift 8

Shift 11

Shift 12

Shift 11

Shift 12

Cell cluster 1  Use root hopping pattern 1 Cell cluster 2  Use root hopping pattern 2

1

Shift 1

Shift 6

Shift 3 Shift 7

Shift 6

Shift 3 Shift 7 Shift 9

Shift 9

Shift 1

Shift 5

Shift 10

Shift 2

Shift 4

Shift 8

Shift 5

Shift 10

Shift 2

Shift 4

Shift 8

Shift 11

Shift 12

Shift 11

Shift 12

Cell cluster 1  Use root hopping pattern 1 2 3 4

5

(a) Pure planning (b) Planning and hopping Figure 6-2 Allocation examples of two-layered frequency hopping/shifting patterns (Number of sequence shifts is limited up to 12 for illustration purposes)

6

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

130

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

6.3.2

Physical Uplink Shared Channel (PUSCH)

GroupAssignmentPUSCH (𝚫𝒔𝒔 )

Definition: The difference between the sequence-shift pattern for PUSCH and the sequence-shift pattern for PUCCH. IE Value

Allowed Range Recommended

Engineering Units

INTEGER

INTEGER

[0 .. 29]

[0 .. 29]

0 for general uplink operation

6

Setting Tradeoff: If set to zero sequence patterns for PUCCH and PUSCH are the same. If the value of the parameter is low a small shift is added between PUSCH and PUCCH sequences while if the value is high a bigger shift is added.

7

Dependencies/Constraints: none

8

Traceability: TS36.331 Sect. 6.3.2, and TS36.211 Sect. 5.5.1.3

9

RRC Message Structure:

4 5

11

SystemInformationBlockType2radioResourceConfigCommonRadioResourceConfigCommonSI B PUSCH-ConfigCommon UL-ReferenceSignalsPUSCH  GroupAssignmentPUSCH

12

Notes:

10

13 14

PUCCH and PUSCH have the same group hopping pattern but may have different sequence-shift patterns if GroupAssignement is different from 0.

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

131

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

6.3.3

Physical Uplink Shared Channel (PUSCH)

SequenceHoppingEnabled

Definition: Enable (TRUE) or disable (FALSE) sequence hopping. It is only applicable if group hopping is disabled IE Value

Allowed Range

Recommended

Engineering Units

BOOLEAN

BOOLEAN

(TRUE, FALSE)

(TRUE, FALSE)

FALSE if GroupHoppingEnabled is set to TRUE; TRUE otherwise.

6

Setting Tradeoff: Setting the value to TRUE will imply that sequence hopping within the same sequence group between the two slots of a subframe is enabled. This can be used in sequence-group pure planning to achieve interference randomization.

7

Dependencies/Constraints:

4 5

8 9

Sequence hopping can be performed only if GroupHoppingEnabled is set to FALSE and SequenceHoppingEnabled is set to TRUE.

10

Traceability: TS36.331 Sect. 6.3.2, and TS36.211 Sect. 5.5.1.4

11

RRC Message Structure:

13

SystemInformationBlockType2radioResourceConfigCommonRadioResourceConfigCommonSI B PUSCH-ConfigCommon UL-ReferenceSignalsPUSCH  SequenceHoppingEnabled

14

Notes:

15

Sequence hopping only applies for reference signals of length M scRS ≥ 6N scRB .

12

16 17

For reference-signals of length M scRS ≥ 6N scRB , the base sequence number v within the base sequence group in slot ns is defined by

18

c(n ) if group hopping is disabled and sequence hopping is enabled v= s otherwise 0

19

where c(i ) is a pseudo-random sequence.

20 21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

132

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Physical Uplink Shared Channel (PUSCH)

1

6.3.4

CyclicShift

2

(1) Definition: A 3-bit cell specific broadcast cyclic shift offset parameter that maps to nDMRS

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

Engineering Units

INTEGER

INTEGER

(0… 7)

(0… 7)

Nonzero if GroupHoppingEnabled is set to FALSE

6

Setting Tradeoff: By setting different cyclic time shifts in adjacent cells with the same sequence group (e.g. the cells of the same eNodeB) permits to support orthogonal RS transmissions from UEs in different cells. If the value of the parameter is low a small shift is added to that specific cell. If the value is high a bigger cyclic time shift is added. Larger cell size is supported.

7

Dependencies/Constraints:

8

Traceability: TS36.331 Sect. 6.3.2, and TS36.211 Sect. 5.5.1.4

9

RRC Message Structure:

3 4 5

10 11

12

SystemInformationBlockType2radioResourceConfigCommon PUSCH-ConfigCommon ULReferenceSignalsPUSCH CyclicShift Notes: The cyclic shift α in a slot ns is given as α = 2π ncs /12 with

(

14

)

(1) ( 2) ncs = nDMRS + nDMRS + nPRS (ns ) mod 12

13

where the values of n (1) is given by Table 6-3 according to the parameter cyclicShift provided by DMRS ( 2)

15 16 17

18

higher layers, n DMRS is given by the cyclic shift for DMRS field in most recent DCI format 0 [3] for the( 2 )transport block associated with the corresponding PUSCH transmission where the values of nDMRS is given in Table 6-2. ( 2) nDMRS shall be set to zero, if there is no PDCCH with DCI format 0 for the same transport block, and

19



if the initial PUSCH for the same transport block is semi-persistently scheduled, or,

20



if the initial PUSCH for the same transport block is scheduled by the random access response grant

21

22

n PRS (n s ) is given by

n PRS (n s ) =

23



7

i =0

UL c(8 N symb ⋅ n s + i) ⋅ 2 i

24

where the pseudo-random sequence c(i ) is defined by section 7.2. The application of c(i ) is cell-

25

 N cell  c init =  ID  ⋅ 2 5 + f ssPUSCH  30  specific. The pseudo-random sequence generator shall be initialized with

26

at the beginning of each radio frame. 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

133

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

1

Physical Uplink Shared Channel (PUSCH)

( 2) Table 6-2 Mapping of Cyclic Shift Field in DCI format 0 to n DMRS Values.

Cyclic Shift Field in DCI format 0 [3]

( 2) nDMRS

000 001 010 011 100 101 110 111

0 6 3 4 2 8 10 9

2

3

Table 6-3 Mapping of cyclicShift to n (1) Values. DMRS cyclicShift

(1) nDMRS

0 1 2 3 4 5 6 7

0 2 3 4 6 8 9 10

4 5

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

134

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

6.4 Transmission of Control Signaling on PUSCH

7

Control data arrives at the coding unit in the form of channel quality information (CQI), HARQ-ACK and rank indicator. Different coding rates for the control information are achieved by allocating different number of coded symbols for its transmission. The number of resource elements for each of CQI/PMI, ACK/NACK and RI is based on the MCS assigned for PUSCH and an offset parameter, RI CQI HARQ − ACK β offset , β offset , or β offset , which is configured by higher-layer signaling. This allows different code rates to be used for the control signaling.

8

6.4.1

2 3 4

Released - For Current Employee/Consultant Use Only

Physical Uplink Shared Channel (PUSCH)

5 6

9 10

betaOffset-ACK-Index

Definition: Index used to determine the offset value added in the calculation of the number of resources and code rates for ACK/NACK control signaling transmitted on the PUSCH. IE Value

Allowed Range

Recommended

11 12 13 14 15 16

Engineering Units

INTEGER

INTEGER

(0… 15)

(0… 15)

Set to high (i.e., 10 or higher) if observed number of unnecessary downlink retransmission in cell edge is high.

Setting Tradeoff: If this parameter is set too high, large number of coded symbols will be allocated for the transmission of HARQ-ACK bits then increasing the robustness of control signaling transmission but reducing the number of resources allocated for data. If this parameter is set too low, small number of coded symbols will be allocated for the transmission of HARQ-ACK bits then reducing the robustness of control signaling transmission but reducing the number of resources allocated for data.

17 18

Dependencies/Constraints:

19

Traceability: TS36.331 Sect. 6.3.2, TS36.213 Sect. 8.6.3, and TS36.212 Sect. 5.2.2.6

20

RRC Message Structure:

21 22

SystemInformationBlockType2radioResourceConfigCommon PUSCH-ConfigDedicated betaOffset-ACK-Index

23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

135

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3 4

Released - For Current Employee/Consultant Use Only

5

Physical Uplink Shared Channel (PUSCH)

Notes: Following table shows the mapping of HARQ-ACK offset values and the index signaled by higher layers. Table 6-4 Mapping of HARQ-ACK offset values and the index signaled by higher layers HARQ − ACK I offset

HARQ − ACK β offset

0

2.000

1

2.500

2

3.125

3

4.000

4

5.000

5

6.250

6

8.000

7

10.000

8

12.625

9

15.875

10

20.000

11

31.000

12

50.000

13

80.000

14

126.000

15

reserved

6 7

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

136

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

6.4.2

Physical Uplink Shared Channel (PUSCH)

betaOffset-RI-Index

Definition: Index used to determine the offset value added in the calculation of the number of resources and code rates for RI control signaling transmitted on the PUSCH. IE Value

Allowed Range

Recommended

Engineering Units

INTEGER

INTEGER

(0… 15)

(0… 15)

Set to the middle range (i.e., 5-10) for better RI detection.

8

Setting Tradeoff: If this parameter is set too high, a large number of coded symbols will be allocated for the transmission of RI bits then increasing the robustness of control signaling transmission but reducing the number of resources allocated for data. If this parameter is set too low, small number of coded symbols will be allocated for the transmission of RI bits then reducing the robustness of control signaling transmission but reducing the number of resources allocated for data.

9

Dependencies/Constraints:

4 5 6 7

10

Traceability: TS36.331 Sect. 6.3.2, TS36.213 Sect. 8.6.3, and TS36.212 Sect. 5.2.2.6

11

RRC Message Structure:

12 13

SystemInformationBlockType2radioResourceConfigCommon PUSCH-ConfigDedicated betaOffset-RI-Index

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

137

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Physical Uplink Shared Channel (PUSCH)

Notes: Following table shows the mapping of RI offset values and the index signaled by higher layers. Table 6-5 Mapping of RI offset values and the index signalled by higher layers RI I offset

RI β offset

0

1.250

1

1.625

2

2.000

3

2.500

4

3.125

5

4.000

6

5.000

7

6.250

8

8.000

9

10.000

10

12.625

11

15.875

12

20.000

13

Reserved

14

Reserved

15

Reserved

4 5

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

138

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

6.4.3

Physical Uplink Shared Channel (PUSCH)

betaOffset-CQI-Index

Definition: Index used to determine the offset value added in the calculation of the number of resources and code rates for CQI control signaling transmitted on the PUSCH. IE Value

Allowed Range

Recommended

Engineering Units

INTEGER

INTEGER

(0… 15)

(0… 15)

Set to high (i.e., 10 or higher) to improve the CQI detection at eNodeB.

8

Setting Tradeoff: If this parameter is set too high, large number of coded symbols will be allocated for the transmission of CQI bits then increasing the robustness of control signaling transmission but reducing the number of resources allocated for data. If this parameter is set too low, small number of coded symbols will be allocated for the transmission of CQI bits then reducing the robustness of control signaling transmission but reducing the number of resources allocated for data.

9

Dependencies/Constraints:

4 5 6 7

10

Traceability: TS36.331 Sect. 6.3.2, TS36.213 Sect. 8.6.3, and TS36.212 Sect. 5.2.2.6

11

RRC Message Structure:

12 13

SystemInformationBlockType2radioResourceConfigCommon PUSCH-ConfigDedicated betaOffset-CQI-Index

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

139

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Physical Uplink Shared Channel (PUSCH)

Notes: Following table shows the mapping of CQI offset values and the index signalled by higher layers. Table 6-6 Mapping of CQI offset values and the index signalled by higher layers CQI I offset

CQI β offset

0

reserved

1

reserved

2

1.125

3

1.250

4

1.375

5

1.625

6

1.750

7

2.000

8

2.250

9

2.500

10

2.875

11

3.125

12

3.500

13

4.000

14

5.000

15

6.250

4

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

140

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

2

7 PUCCH, Uplink scheduling support SRS/SR & SPS

3

Chapter 7: Table of Contents

4

7.1 Physical Uplink Control Channel (PUCCH) allocation.................................................................... 142

5

6

7

8

7.1.1 deltaPUCCH-Shift (𝚫𝑷𝑼𝑪𝑪𝑯 𝒔𝒉𝒊𝒇𝒕 ) .............................................................................................................. 145 (𝟐)

7.1.2 nRB-CQI (𝑵𝑹𝑩 ) .................................................................................................................................... 146 (𝟏)

7.1.3 nCS-AN (𝑵𝒄𝒔 ) ..................................................................................................................................... 147 (𝟏)

7.1.4 n1-PUCCH-AN (𝑵𝑷𝑼𝑪𝑪𝑯)................................................................................................................... 148

10

7.1.5 repetitionFactor (𝑵𝑨𝑵𝑹𝒆𝒑 ) ................................................................................................................... 150

11

7.1.6 n1Pucch-AN-Rep (𝒏𝑷𝑼𝑪𝑪𝑯,𝑨𝑵𝑹𝒆𝒑) ...................................................................................................... 151

7.2 Sounding Reference Signal ................................................................................................................... 152

12

7.2.1 srs-BandwidthConfig ......................................................................................................................... 152

13

7.2.2 SRS-SubframeConfig .......................................................................................................................... 155

14

7.2.3 ackNackSRS-SimultaneousTransmission ........................................................................................ 157

15

7.2.4 srs-Bandwidth ..................................................................................................................................... 158

16

7.2.5 srs-HoppingBandwidth ..................................................................................................................... 159

17

7.2.6 freqDomainPosition............................................................................................................................ 161

18

7.2.7 duration ................................................................................................................................................ 162

19

7.2.8 srs-ConfigIndex ................................................................................................................................... 163

20

7.2.9 transmissionComb .............................................................................................................................. 165

21

7.2.10 cyclicShift ........................................................................................................................................... 166

22

7.3 Scheduling Request ............................................................................................................................... 167

23

7.3.1 Sr-ConfigIndex .................................................................................................................................... 167

24

7.3.2 Sr-PUCCH-ResourceIndex ................................................................................................................ 169

25

7.3.3 dsr-TransMax ...................................................................................................................................... 170

9

(𝟏)

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

141

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9 10 11 12 13

PUCCH, Uplink scheduling support SRS/SR & SPS

7.1 Physical Uplink Control Channel (PUCCH) allocation In LTE, the eNode B is in full control of the uplink transmission parameters. Therefore only data nonassociated control signaling is necessary. Examples of such control signaling are the HARQ Acknowledgments (ACK/NACK) for downlink data packets, Channel Quality Indicators (CQI), and MIMO feedback (Rank Indicator – RI – and Precoding Matrix Indicator – PMI). Scheduling Requests (SRs) also fall into this category. When simultaneous PUSCH data and control signaling is scheduled for a UE, the control signaling is multiplexed with the data in order to preserve the low Cubic Metric property of the uplink transmission. So the PUCCH channel is only used by the UE when there is no RB allocated to PUSCH transmission. The PUCCH is allocated in the edges of the bandwidth. The UE transmission on the first slot is followed by a transmission in the second slot at or near the opposite edge of the system bandwidth, as exemplified in Figure 7-1:

14

Tw o RB´s assigned to PUCCH

PUCCH UE#1 PUCCH UE#2

PUCCH UE#3 PUCCH UE#4

PUSCH Region (all remaining RBs)

PUCCH UE#4 PUCCH UE#3

PUCCH UE#2 PUCCH UE#1

0.5ms Slot

0.5ms Slot 1ms Subframe

15 16

17 18

Tw o RB´s assigned to PUCCH

Figure 7-1. PUCCH In this picture four Resource Blocks (RBs) are assigned for PUCCH, in the edges of the bandwidth. The UE transmits at a different RB per slot, in opposite sides of the bandwidth.

19 20 21 22 23 24 25

The advantages of this configuration include the following: - The frequency diversity thru frequency hopping (approximately 2dB) is maximized. - Out-Of-Band (OOB) emissions are minimized if a UE transmits on a single RB when compared to multiple RBs. Coexistence with different systems is improved. - This maximizes the achievable PUSCH data rate, as the entire central portion can be allocated to one UE.

26 27

Cyclic Shifts and Orthogonal Codes

28 29 30 31

Another characteristic of the PUCCH channel is that several UE´s can share the same Resource Block – RB, via cyclic shifts and orthogonal codes. In one RB, up to 12 cyclic shifts of a sequence with suitable properties, such as the Zadoff-Chu sequences, can be used to multiplex UE´s into the same

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

142

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

PUCCH, Uplink scheduling support SRS/SR & SPS

radio resources. Orthogonal codes, in a manner much like what is used in UMTS, also provide a method of distinguishing UE´s transmissions that are sharing the same resource blocks.

3

Released - For Current Employee/Consultant Use Only

4

Uplink Control Information (UCI) allowed formats

5 6 7

There are seven UCI – Uplink Control Information – formats supported on PUCCH, as per table 9.1: Table 7-1. UCI formats for PUCCH PUCCH Form at Format 1 Format 1a Format 1b Format 2 Format 2 Format 2a Format 2b

8

Uplink Control Inform ation (UCI) Scheduling request (SR) (unmodulated w aveform) 1-bit HARQ ACK/NACK w ith/w ithout SR 2-bit HARQ ACK/NACK w ith/w ithout SR CQI (20 coded bits) CQI and 1- or 2-bit HARQ ACK/NACK (20 bits) for extended CP CQI and 1-bit HARQ ACK/NACK (20 + 1 coded bits) CQI and 2-bit HARQ ACK/NACK (20 + 2 coded bits)

9 10

And the physical mapping of PUCCH formats to PUCCH RBs (or regions) looks like:

11

2/2a/2b #1 (m=1) 1/1a/1b #0 (m=3) 1/1a/1b #2 (m=5)

2/2a/2b #0 (m=0) 1/1a/1b + 2/2a/2b (m=2) 1/1a/1b #1 (m=4)

PUSCH Region (all remaining RBs)

1/1a/1b #1 (m=4) 1/1a/1b + 2/2a/2b (m=2) 2/2a/2b #0 (m=0)

1/1a/1b #2 (m=5) 1/1a/1b #0 (m=3) 2/2a/2b #1 (m=1)

0.5ms Slot

0.5ms Slot 1ms Subframe

12 13

Figure 7-2. Mapping of PUCCH formats to PUCCH regions.

14 15

Codeword structure for CQI and ACK/NACK messages

16 17 18

For the transmission of the 10-bit CQI, a ½ rate Reed-Muller code is used, resulting in 20 coded bits. Using QPSK this becomes 10 symbols of modulated data, that can be sent in one subframe:

19 20 21 22

CP

LB#0

CP

RS

CP

LB#2

CP

LB#3

CP

LB#4

CP

RS

CP

LB#6

Figure 7-3. CQI channel structure for PUCCH format 2/2a/2b with normal CP for one slot

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

143

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

1 2

Each LB# can transmit two bits of the CQI. A second slot is necessary to complete the subframe.

3

Released - For Current Employee/Consultant Use Only

4 5 6 7

For the transmission of ACK/NACK in conjunction with CQI (formats 2a/2b), the second RS symbol (SC-FDMA symbol 5) is used. In the case of extended CP, with only one RS per symbol, the ACK/NACK data is jointly encoded with CQI in the (20,kCQI+kACK/NACK) Reed-Muller code, resulting in 20 coded bits (5 symbols of data and 1 symbol for RS per 6-symbol 0.5ms slot).

8 9

The following structure is used for the transmission of HARQ ACK/NACK using formats 1a/1b:

10 11 12 13

CP

LB#0

CP

LB#1

CP

RS

CP

RS

CP

RS

CP

LB#5

CP

LB#6

Figure 7-4. Channel structure for HARQ ACK/NACK formats 1a/1b. More RS (Reference Signals) are used to improve coherent detection.

14 15 16 17

In this transmission format, both cyclic shifts and orthogonal codes can be used to multiplex UE´s in the same Resource Block. For example, in the case of 6 cyclic shifts and three orthogonal time spreading codes, 18 UE´s can be multiplexed within one PUCCH RB.

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

144

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

7.1.1

PUCCH, Uplink scheduling support SRS/SR & SPS

deltaPUCCH-Shift (𝚫𝑷𝑼𝑪𝑪𝑯 𝒔𝒉𝒊𝒇𝒕 )

Definition: DeltaPUCCH-Shift indicates the cyclic time shift to be used when calculating the UE specific time shift of the ZC-Sequence to apply to the PUCCH transmission. IE Value

Allowed Range Recommended

Engineering Units

ENUMERATED

ENUMERATED

(ds1, ds2, ds3)

(1, 2, 3)

ds2

2

6

Setting Tradeoff: If set too high, it will reduce the number of UEs which can be multiplexed on the same resource block. If set too low, the number of UEs which can be multiplexed on the same resource block increases, but it may not be very robust to frequency selectivity of radio environment.

7

Dependencies/Constraints:

8

The parameters deltaPUCCH-Shift( ∆PUCCH ), nRB-CQI ( N RB ), nCS-An( N cs(1) ), n1Pucch-AN ( shift

4 5

(2)

9

(1) ) should be optimized jointly. N PUCCH

nCS-An( N cs(1) ) is an integer multiple of deltaPUCCH-Shift( ∆ shift

PUCCH

10

11

Traceability: TS36.331 Sect. 6.3.2; TS36.221 Sect. 5.4.1

12

RRC Message Structure:

)

14

SystemInformationBlockType2  radioResourceConfigCommon  pucch-ConfigCommon deltaPUCCH-Shift

15

Notes:

16

Typically up to six phase shifts rotation (i.e., ds2) are considered usable in a cell.

13

17 18 19

As the PUCCH is used by all the UEs without an assigned grant, this parameter shall be optimized considering the expected number of UEs in such a condition and the available PUCCH RBs defined per subframe. deltaPUCCH-Shift

Available resource indices for Format 1/1a/1b

1

36

2

18

3

12

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

145

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

7.1.2

PUCCH, Uplink scheduling support SRS/SR & SPS

(𝟐)

nRB-CQI (𝑵𝑹𝑩 )

Definition: Determine the bandwidth in terms or resource blocks that are available for use by PUCCH formats 2/2a/2b transmissions in each slot. IE Value

Allowed Range

Recommended

Engineering Units

INTEGER

INTEGER

(0, 1, … 98) 2 to guarantee enough resource for PUCCH format 2/2a/2b transmission. Change this value as a function of the number of simultaneous active UEs per cell.

(0, 1, … 98)

6

Setting Tradeoff: If set too high PUSCH UL resources are wasted, as there are not enough UEs without grant that need to report format 2 (CQI) and HARQ ACK/NACK If set too low, the number of possible UEs can use PUCCH format 2 may be limited.

7

Dependencies/Constraints:

8

The parameters deltaPUCCH-Shift( ∆PUCCH ), nRB-CQI ( N RB ), nCS-An( N cs(1) ), n1Pucch-AN ( shift

4 5

(2)

9

(1) ) should be optimized jointly. N PUCCH

10

Traceability: TS36.331 Sect. 6.3.2; TS36.221 Sect. 5.4

11

RRC Message Structure:

13

SystemInformationBlockType2  radioResourceConfigCommon  pucch-ConfigCommon  nRBCQI

14

Notes:

15

PUCCH format 2/2a/2b is transmitted at the edge of the RB allocated for PUCCH.

12

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

146

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

7.1.3

PUCCH, Uplink scheduling support SRS/SR & SPS

(𝟏)

nCS-AN (𝑵𝒄𝒔 )

Definition: Provides the number of cyclic shift in a RB used for PUCCH format 1/1a/1b in a RB used for a mix of formats 1/1a/1b and 2/2a/2b. IE Value

Allowed Range

Recommended

4

Engineering Units

INTEGER

INTEGER

(0, 1, … 7) 0 to avoid the operation of mixed format 1/1a/1b and 2/2a/2b in the same RB; Nonzero otherwise.

(0, 1, … 7)

Setting Tradeoff:

8

If set too high, a large number of cyclic shifts are reserved for format 1/1a/1b in a mixed RB, but the resources available for format 2/2a/2b in a mixed RB could be insufficient. If set too low, a large number of cyclic shifts are reserved for format 2/2a/2b in a mixed RB, the resources available for format 1/1a/1b in a mixed RB could be insufficient

9

Dependencies/Constraints:

5 6 7

The parameters deltaPUCCH-Shift( ∆PUCCH ), nRB-CQI ( N RB ), nCS-AN( N cs(1) ), n1Pucch-AN ( shift (2)

10 11

(1) ) should be optimized jointly. N PUCCH

12

nCS-AN( N cs(1) ) is an integer multiple of deltaPUCCH-Shift( ∆PUCCH ) shift

13

Traceability: TS36.331 Sect. 6.3.2; TS36.221 Sect. 5.4

14

RRC Message Structure:

16

SystemInformationBlockType2  radioResourceConfigCommon  pucch-ConfigCommon  nCSAn

17

Notes:

15

18 19

Multiplexing of formats in PUCCH RBs in general simplifies the system, but increases overhead (i.e. introduction of guard cyclic shifts), which might be an issue for small bandwidth deployment.

20 21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

147

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

(𝟏)

1

7.1.4

n1-PUCCH-AN (𝑵𝑷𝑼𝑪𝑪𝑯 )

2

Definition: Defines the PUCCH resource to be used to report HARQ-ACK information.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Engineering Units

INTEGER

INTEGER

(0, 1, … 2047)

(0, 1, … 2047)

cell specific

Recommended 3

Setting Tradeoff: Cell specific configuration.

4

Dependencies/Constraints:

5

The parameters deltaPUCCH-Shift( ∆ shift

PUCCH

6

(2)

(1)

), nRB-CQI ( N RB ), nCS-AN( N cs ), n1Pucch-AN (

(1) ) should be optimized jointly. N PUCCH

7

Traceability: TS36.331 [xxx] Sect. 6.3.2; TS36.213 [xxx] Sect. 10.1

8

RRC Message Structure:

10

SystemInformationBlockType2  radioResourceConfigCommon  pucch-ConfigCommon  n1PUCCH-AN

11

Notes:

12

For FDD, the UE shall use PUCCH resource nPUCCH for transmission of HARQ-ACK in

13

subframe n , where

9

(1)

15

for a PDSCH transmission indicated by the detection of a corresponding PDCCH in subframe n − 4 , or for a PDCCH indicating downlink SPS release (defined in TS 36.213 Section 9.2) in

16

subframe

17

first CCE used for transmission of the corresponding DCI assignment and

18

configured by higher layers.

14

19 20 21

-

-

(1) (1) = nCCE + N PUCCH n − 4 , the UE shall use nPUCCH , where nCCE is the number of the

(1) N PUCCH

is

for a PDSCH transmission where there is not a corresponding PDCCH detected in subframe (1) n − 4 , the value of nPUCCH is determined according to higher layer configuration and Table

below.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

148

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

PUCCH, Uplink scheduling support SRS/SR & SPS

Table 7-2. Value of TPC command for PUCCH

Released - For Current Employee/Consultant Use Only

Value of ‘TPC command for PUCCH’ ‘00’ ‘01’ ‘10’ ‘11’ 2

(1) nPUCCH

The first PUCCH resource index configured by the higher layers The second PUCCH resource index configured by the higher layers The third PUCCH resource index configured by the higher layers The fourth PUCCH resource index configured by the higher layers

Value of TPC command for PUCCH

3 4

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

149

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

7.1.5

PUCCH, Uplink scheduling support SRS/SR & SPS

repetitionFactor (𝑵𝑨𝑵𝑹𝒆𝒑 )

Definition: Provide the amount of repetition to be used for the ACK/NACK transmissions for all transmissions with no PDCCH associated. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: number

(n2, n4, n6, spare1)

Range: 2, 4, 6, spare

Enable only if large number of ACK/NACK erasures is detected in eNB.

6

Setting Tradeoff: If set too high will reduce maximum available throughput (as not every subframe can be used for DL transmission). If set too low the probability of ACK/NACK misdetection might be increased.

7

Dependencies/Constraints:

4 5

8 9

(𝟏)

The parameters repetitionFactor (𝑵𝑨𝑵𝑹𝒆𝒑 )and n1Pucch-AN-Rep (𝒏𝑷𝑼𝑪𝑪𝑯,𝑨𝑵𝑹𝒆𝒑) shall be jointly considered during optimization.

10

Traceability: TS36.331 [xxx] Sect. 6.3.2; TS36.213 [xxx] Sect. 10.1

11

RRC Message Structure:

12 13 14 15 16 17 18 19 20 21 22 23 24

25

SystemInformationBlockType2  PhysicalConfigDedicated  PUCCH-ConfigDedicated  ackNackRepetition  Setup  repetitionFactor Notes: ACK/NACK repetition is enabled or disabled by a UE specific parameter ackNackRepetition configured by higher layers. Once enabled, the UE shall repeat any ACK/NACK transmission with a repetition factor N ANRep , where N ANRep is provided by higher layers and includs the initial ACK/NACK transmission, until ACK/NACK repetition is disabled by higher layers. For a PDSCH transmission without a corresponding PDCCH detected, the UE shall transmit the corresponding (1) ACK/NACK response N ANRep times using PUCCH resource nPUCCH configured by higher layers. For a PDSCH transmission with a corresponding PDCCH detected, or for a PDCCH indicating downlink SPS release, the UE shall first transmit the corresponding ACK/NACK response once using PUCCH resource derived from the corresponding PDCCH CCE index (as described in Section 10.1), and repeat the transmission of the corresponding ACK/NACK response N ANRep − 1 times always using (1) (1) PUCCH resource nPUCCH, ANRep , where nPUCCH, ANRep is configured by higher layers.

26

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

150

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

7.1.6

PUCCH, Uplink scheduling support SRS/SR & SPS

(𝟏)

n1Pucch-AN-Rep (𝒏𝑷𝑼𝑪𝑪𝑯,𝑨𝑵𝑹𝒆𝒑 )

Definition: Provided the resource index to be used for the repetitions of the ACK/NACK transmissions. IE Value

Allowed Range Recommended

INTEGER

Unit: number

(0 .. 2047)

Range: 0 .. 2047

cell specific

4

Setting Tradeoff: cell specific.

5

Dependencies/Constraints:

6 7

Engineering Units

(𝟏)

The parameters repetitionFactor (𝑵𝑨𝑵𝑹𝒆𝒑 )and n1Pucch-AN-Rep (𝒏𝑷𝑼𝑪𝑪𝑯,𝑨𝑵𝑹𝒆𝒑) shall be jointly considered during optimization.

8 9 10

Traceability: TS36.331 [xxx] Sect. 6.3.2; TS36.213 [xxx] Sect. 10.1 RRC Message Structure:

12

SystemInformationBlockType2  PhysicalConfigDedicated  PUCCH-ConfigDedicated  ackNackRepetition  Setup  n1Pucch-AN-Rep

13

Notes: Please see notes in 7.1.5.

11

14 15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

151

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

7.2 Sounding Reference Signal

4

The SRS, which are not associated with uplink data and/or control transmission, is primarily used for channel quality estimation to enable frequency-selective scheduling on the uplink. SRS bandwidths are multiples of 4 RBs.

5

7.2.1

2 3

Released - For Current Employee/Consultant Use Only

PUCCH, Uplink scheduling support SRS/SR & SPS

6 7

srs-BandwidthConfig

Definition: Cell specific SRS bandwidth configuration index. It defines the cell specific numbers of RBs over which SRS is transmitted within a cell. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

ENUMERATED

(bw0, bw1, bw2, bw3, bw4, bw5, bw6, bw7)

(0, 1, 2, 3, 4, 5, 6, 7)

Set it to different than NULL if frequency-selective uplink scheduling is desired. Set it to lower range for low uplink load.

8 9 10 11 12 13 14

Setting Tradeoff: Typically SRS transmissions should not extend into the frequency reserved for PUCCH. If index is too low, the SRS bandwidth set may occupy larger bandwidth, depending on srsBandwidth setting. on. This provides better channel information but limits the number of simultaneous UEs whose channels can be sounded, due to the limited number of cyclic time shifts. If index is high, SRS bandwidth set available for the cell has small length thus smaller bandwidth transmission of SRS is permitted. This may reduce the frequency range for uplink sounding, but increase the number of UEs that can simultaneously send SRS.

16

Dependencies/Constraints: This parameter should be properly configured together with srsBandwidth.

17

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

18

RRC Message Structure:

15

20

SystemInformationBlockType2radioResourceConfigCommonSoundingRS-UL-ConfigCommon  srs-BandwidthConfig

21

Notes:

19

22

23

This parameter is 𝐶𝑆𝑅𝑆 defined in TS36.211.

RS M sc, b is the length of the sounding reference signal sequence defined as

RS RB M sc, 2 b = mSRS,b N sc

24

25

UL where b = BSRS and mSRS, b is given by following tables for each uplink bandwidth N RB .

26

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

152

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

1

PUCCH, Uplink scheduling support SRS/SR & SPS

UL Table 7-3. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 6 ≤ N RB ≤ 40 .

SRS bandwidth configuration CSRS

0 1 2 3 4 5 6 7

SRSBandwidth BSRS = 0 mSRS, 0 N0 36 32 24 20 16 12 8 4

1 1 1 1 1 1 1 1

SRSBandwidth BSRS = 1

SRSBandwidth BSRS = 2

SRSBandwidth BSRS = 3

mSRS,1

N1

mSRS, 2

N2

mSRS, 3

N3

12 16 4 4 4 4 4 4

3 2 6 5 4 3 2 1

4 8 4 4 4 4 4 4

3 2 1 1 1 1 1 1

4 4 4 4 4 4 4 4

1 2 1 1 1 1 1 1

2 3

UL Table 7-4. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 40 < N RB ≤ 60 .

SRS bandwidth configuration CSRS

0 1 2 3 4 5 6 7

SRSBandwidth BSRS = 0 mSRS, 0 N0 48 48 40 36 32 24 20 16

1 1 1 1 1 1 1 1

SRSBandwidth BSRS = 1

SRSBandwidth BSRS = 2

SRSBandwidth BSRS = 3

mSRS,1

N1

mSRS, 2

N2

mSRS, 3

N3

24 16 20 12 16 4 4 4

2 3 2 3 2 6 5 4

12 8 4 4 8 4 4 4

2 2 5 3 2 1 1 1

4 4 4 4 4 4 4 4

3 2 1 1 2 1 1 1

4

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

153

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

1

PUCCH, Uplink scheduling support SRS/SR & SPS

UL Table 7-5. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 60 < N RB ≤ 80 .

SRS bandwidth configuration CSRS

0 1 2 3 4 5 6 7

SRSBandwidth BSRS = 0 mSRS, 0 N0 72 64 60 48 48 40 36 32

1 1 1 1 1 1 1 1

SRSBandwidth BSRS = 1

SRSBandwidth BSRS = 2

SRSBandwidth BSRS = 3

mSRS,1

N1

mSRS, 2

N2

mSRS, 3

N3

24 32 20 24 16 20 12 16

3 2 3 2 3 2 3 2

12 16 4 12 8 4 4 8

2 2 5 2 2 5 3 2

4 4 4 4 4 4 4 4

3 4 1 3 2 1 1 2

2 3

UL Table 7-6. mSRS, b and N b , b = 0,1,2,3 , values for the uplink bandwidth of 80 < N RB ≤ 110 .

SRS bandwidth configuration CSRS

0 1 2 3 4 5 6 7

SRSBandwidth BSRS = 0 mSRS, 0 N0 96 96 80 72 64 60 48 48

1 1 1 1 1 1 1 1

SRSBandwidth BSRS = 1

SRSBandwidth BSRS = 2

SRSBandwidth BSRS = 3

mSRS,1

N1

mSRS, 2

N2

mSRS, 3

N3

48 32 40 24 32 20 24 16

2 3 2 3 2 3 2 3

24 16 20 12 16 4 12 8

2 2 2 2 2 5 2 2

4 4 4 4 4 4 4 4

6 4 5 3 4 1 3 2

4 5

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

154

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

1

7.2.2

SRS-SubframeConfig

2

Definition: Sets of subframes in which SRS may be transmitted within the cell by any UE

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

ENUMERATED

(sc0, sc1, sc2, sc3, …,sc15)

(0, 1, 2, 3, …, 15)

If SRS transmission is enabled, set it as a function of uplink loading (sc0 for loaded cell).

7

Setting Tradeoff: If configuration index is high, SRS can be transmitted in the cell by any UE less often, thus eNode uplink scheduler will have less info about uplink channel quality of UEs within the cell. If configuration index is low, SRS can be transmitted in the cell by any UE very often, thus SRS overhead increases but better uplink channel quality estimation enables more precise uplink frequency-selective scheduling.

8

Dependencies/Constraints:

9

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

3 4 5 6

10

RRC Message Structure:

12

SystemInformationBlockType2radioResourceConfigCommon SoundingRS-ULConfigCommon  srs-SubframeConfig

13

Notes:

11

14 15 16 17 18

The srsSubframeConfiguration index determines TSFC the cell specific configuration period and ∆ SFC the cell specific subframe offset as shown in Table. This configurability provides flexibility in adjusting the SRS overhead depending on the deployment scenario. The 16th configuration switches the SRS off completely in the cell, which may for example be appropriate for a cell serving primarily high-speed UEs.

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

155

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

1

PUCCH, Uplink scheduling support SRS/SR & SPS

Table 7-7. FDD sounding reference signal subframe configuration

srsSubframeConfiguration

Binary

Configuration Period TSFC (subframes)

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111

1 2 2 5 5 5 5 5 5 10 10 10 10 10 10 reserved

Transmission offset ∆ SFC (subframes) {0} {0} {1} {0} {1} {2} {3} {0,1} {2,3} {0} {1} {2} {3} {0,1,2,3,4,6,8} {0,1,2,3,4,5,6,8} reserved

2 3

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

156

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

7.2.3

PUCCH, Uplink scheduling support SRS/SR & SPS

ackNackSRS-SimultaneousTransmission

Definition: Determines if a UE is configured to support the transmission of ACK/NACK on PUCCH and SRS in one subframe.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

4 5 6 7 8 9

Engineering Units

BOOLEAN

BOOLEAN

(TRUE, FALSE)

(TRUE, FALSE)

TRUE If SRS-subframeConfig results in a large percentage of SRS subframes per frame; FALSE otherwise.

Setting Tradeoff: If TRUE, then in the cell-specific SRS subframes UE sends ACK/NACK and SR using shortened PUCCH format, where the ACK/NACK or the SR symbol corresponding to the SRS location is punctured. This shortened PUCCH format shall be used in a cell specific SRS subframe even if the UE does not transmit SRS in that subframe. If FALSE, UE shall not transmit SRS whenever SRS transmission and PUCCH transmission carrying ACK/NACK and/or positive SR happen to coincide in the same subframeDependencies/Constraints:

10

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

11

RRC Message Structure:

13

SystemInformationBlockType2radioResourceConfigCommonSoundingRS-UL-ConfigCommon  ackNackSRS-SimultaneousTransmission

14

Notes:

12

15 16

A UE shall not transmit SRS whenever SRS and PUCCH format 2/2a/2b transmissions happen to coincide in the same subframe.

17 18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

157

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

1

7.2.4

srs-Bandwidth

2

Definition: Sets SRS transmission bandwidth for a UE.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

ENUMERATED

(bw0, bw1, bw2, bw3)

(0, 1, 2, 3)

Set it to different than NULL if frequency-selective uplink scheduling is desired.

TBD

Set it to lower range for low uplink load. 3 4 5 6 7 8 9

Setting Tradeoff: If parameter is high, UE will be configured with a small sounding bandwidth, which it is favorable for power-limited UEs, and allows a large number of UEs that can transmit SRS simultaneouslyIf parameter is low, UE will be set with a large sounding bandwidth, which provides the better channel information but reduces the number of UEs that can transmit SRS simultaneously. Dependencies/Constraints: This parameter should be configured together with srsHoppingBandwidth. The actually SRS transmitted bandwidth is a function of srs-BandwidthConfig and srs-Bandwidth.

10

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

11

RRC Message Structure:

12 13

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  srs-Bandwidth

15

RRCConnectionReconfiguration Rad ioResou rceCon figDed icated PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  srs-Bandwidth

16

Notes:

14

17 18 19 20 21

This parameter is 𝐵𝑆𝑅𝑆 defined in TS36.211. The smallest sounding bandwidth supported is 4 RBs. Two different approaches are possible:

1) Full bandwidth SRS Allows better channel quality information but at the expense of UE power consumption. It requires less frequent SRS scheduling.

22 23 24 25

2) Narrow bandwidth SRS + hopping Allows better UE power utilization, but reduces the channel quality information across the band. It requires hopping and more frequent SRS scheduling.

26

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

158

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

1

7.2.5

srs-HoppingBandwidth

2

Definition: Frequency hop size of the sounding reference signal

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

ENUMERATED

(hbw0, hbw1, hbw2, hbw3)

(0, 1, 2, 3)

Set it to the value < srs-Bandwidth to enable hopping when the configured SRS bandwidth (defined by srsBandwidthConfig and srs-Bandwidth) is smaller than system bandwidth.

4

Setting Tradeoff: Enabling SRS frequency hopping let eNodeB combat more efficiently frequency selective channel behavior and inter-cell interference.

5

Dependencies/Constraints: This parameter should be configured together with srs-bandwidth.

6

If bhop ≥ BSRS frequency hopping of the sounding reference signal is not enabled,

7

If bhop < BSRS frequency hopping of the sounding reference signal is enabled,

8

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

9

RRC Message Structure:

3

10 11

12 13

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  srs- HoppingBandwidth RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  srs- HoppingBandwidth

14 15 16 17

Notes: The frequency hopping of the sounding reference signal is configured by the parameter srsHoppingBandwidth, bhop ∈ {0,1,2,3} , provided by higher layers. If frequency hopping of the

18

sounding reference signal is not enabled (i.e., bhop ≥ BSRS ), the frequency position index nb remains

19

constant (unless re-configured) and is defined by nb = 4nRRC mSRS,b  mod N b where the parameter

20

freqDomainPosition n RRC is given by higher layers for the UE. If frequency hopping of the sounding

21

reference signal is enabled (i.e., bhop < BSRS ), the frequency position indexes nb are defined by

 4nRRC mSRS,b  mod N b nb =  {Fb (n SRS ) + 4n RRC mSRS,b }mod N b

22

23 24

b ≤ bhop otherwise

where N b is given by Table 5.5.3.2-1 through Table 5.5.3.2-4 in TS36.211 for each uplink bandwidth UL N RB

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

159

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

  n SRS mod Π bb '=bhop N b '   n SRS mod Π bb '=bhop N b '  ( N b / 2)   if N b even + Fb (n SRS ) =  Π bb '−=1bhop N b ' 2Π bb '−=1bhop N b '      b −1 if N b odd N b / 2 n SRS / Π b '=bhop N b ' 

1

Released - For Current Employee/Consultant Use Only





2

where N bhop = 1 regardless of the N b value on Table 5.5.3.2-1 through Table 5.5.3.2-4 in TS36.211,

3

and

4

nSRS

  n   Toffset  2 N SP n f + 2( N SP − 1) s  +  , =  10   Toffset _ max   (n f ×10 + n s / 2) / TSRS ,

for 2ms SRS periodicity of frame structure 2 otherwise

5

counts the number of UE-specific SRS transmissions, where TSRS is UE-specific periodicity of SRS

6

transmission defined in section 8.2 of in TS36.213, Toffset is SRS subframe offset defined in Table 8.2-

7

2 of in TS36.213 and Toffset _ max is the maximum value of Toffset for a certain configuration of SRS

8

subframe offset.

9 10 11

SRS transmission can hop in frequency. This is particularly beneficial for the terminals on the cell edge, which cannot support wideband SRS transmission.

12 13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

160

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

1

7.2.6

freqDomainPosition

2

Definition: Sets frequency domain position

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range Recommended

INTEGER

INTEGER

(0, 1, …, 23)

(0, 1, …, 23)

UE / Scheduler dependent

3

Setting Tradeoff: NA

4

Dependencies/Constraints:

5

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

6

RRC Message Structure:

7 8

Engineering Units

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  freqDomainPosition

10

RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  freqDomainPosition

11

Notes:

9

12 13

This is the parameter 𝑛𝑅𝑅𝐶 defined in TS36.211.

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

161

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

1

7.2.7

duration

2

Definition: Specifies whether the requested SRS transmission is single or periodic

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

BOOLEAN

Engineering Units

(indefinite, single)

(TRUE, FALSE) Recommended

TRUE if SRS is enabled

Indefinite (periodic) if SRS is enabled

7

Setting Tradeoff: If the requested SRS transmission from eNodeB is single, uplink channel quality estimation feedback is provided to the uplink scheduler only upon request of eNodeB, thus signaling loading is reduced but uplink channel quality cannot be supervised all the time. If the requested SRS transmission is periodic, uplink channel quality estimation can be collected all the time but the uplink signaling load increases.

8

Dependencies/Constraints: none

9

Traceability: TS36.331 Sect. 6.3.2, TS36.213 Sect. 8.2

3 4 5 6

10

11 12

RRC Message Structure: RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  duration

14

RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  duration

15

Notes:

13

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

162

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

7.2.8

PUCCH, Uplink scheduling support SRS/SR & SPS

srs-ConfigIndex

Definition: Defines the index associated to specific SRS periodicity and SRS subframe offset within the period in which the UE should transmist its SRS in case periodic SRS transmissions are configured. IE Value

Allowed Range

Recommended

Engineering Units

INTEGER

INTEGER

(0,…, 1023)

(0,…, 1023)

Set it to large number (i.e., 17 – 36) if high uplink load; Set it to small number (i.e., 2 – 6) otherwise.

8

Setting Tradeoff: If index is too low SRS period is short, thus higher amount of signaling is added in uplink but uplink scheduler can be more precise since uplink channel estimation input is more frequent. If index is too high, SRS period is high thus uplink channel quality can be estimated less frequently. Lower signaling load is added in uplink but uplink scheduler is less precise.

9

Dependencies/Constraints: duration should be set to

5 6 7

10

Traceability: TS36.331 Sect. 6.3.2, TS36.213 Sect. 8.2

11

RRC Message Structure:

12 13

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  srs-ConfigIndex

15

RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  srs-ConfigIndex

16

Notes:

17

The UE specific SRS configuration for SRS periodicity, TSRS , and SRS subframe offset, Toffset , is

14

18 19

defined in Table 8.5.10-1. The periodicity TSRS of the SRS transmission is selected from the set {2, 5, 10, 20, 40, 80, 160, 320} ms or subframes.

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

163

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

1

PUCCH, Uplink scheduling support SRS/SR & SPS

Table 7-8. UE Specific SRS Periodicity TSRS and Subframe Offset Configuration Toffset SRS Configuration Index ISRS 0–1 2–6 7 – 16 17 – 36 37 – 76 77 – 156 157 – 316 317 – 636 637 – 1023

SRS Periodicity TSRS (ms) 2 5 10 20 40 80 160 320 reserved

SRS Subframe Offset Toffset ISRS ISRS – 2 ISRS – 7 ISRS – 17 ISRS – 37 ISRS – 77 ISRS – 157 ISRS – 317 reserved

2 3

Note:

4

There are two different approaches for srs-Bandwidth, and srs-ConfigIndex should be set accordingly:

5 6 7

1) Full bandwidth SRS Allows better channel quality information but at the expense of UE power consumption. It requires less frequent SRS scheduling.

8 9 10 11

2) Narrow bandwidth SRS + hopping Allows better UE power utilization, but reduces the channel quality information across the band. It requires hopping and more frequent SRS scheduling.

12 13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

164

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

PUCCH, Uplink scheduling support SRS/SR & SPS

1

7.2.9

transmissionComb

2

Definition: transmission comb offset applied to frequency-domain starting position.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range Recommended

INTEGER

INTEGER

(0, 1)

(0, 1)

NA

NA

3

Setting Tradeoff: NA.

4

Dependencies/Constraints:

5

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

6

RRC Message Structure:

7 8

9 10

Engineering Units

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  transmissionComb RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  transmissionComb

12

SystemInformationBlockType2radioResourceConfigCommonSoundingRS-UL-ConfigDedicated  transmissionComb

13

Notes:

11

14 15

SRS signal has a comb like structure. Contrary to cyclic shifts, transmission comb does not require that the multiplexed signals occupy the same bandwidth.

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

165

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

7.2.10 cyclicShift

2

Definition: cyclic shift

PUCCH, Uplink scheduling support SRS/SR & SPS

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

ENUMERATED

(cs0, cs1, cs2, cs3,…, cs7)

(0, 1, 2, 3,…, 7)

Variable (depends on UL scheduling implementation)

variable

3

Setting Tradeoff:

4

The different UE can be configured to a different cyclic shift.

5

Dependencies/Constraints:

6

Traceability: TS36.331 Sect. 6.3.2, TS36.211 Sect. 5.5.3

7

RRC Message Structure:

8 9

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  cyclicShift

11

RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  SoundingRS-UL-ConfigDedicated  cyclicShift

12

Notes:

13

The cyclic shift α of the sounding reference signal is given as

10

α = 2π

14

15

16 17 18 19

cs n SRS , 8

cs cs where n SRS is configured for each UE by higher layers and n SRS = 0, 1, 2, 3, 4, 5, 6, 7 .

Multiple UEs may be configured to transmit SRS using the same RBs and same comb-offset and there are up to 8 different cyclic shifts of the SRS sequence possible to achieve orthogonal separation. The cyclic shift multiplexed signals, however, need to have the same bandwidth to maintain orthogonality.

20 21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

166

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

7.3 Scheduling Request

4

The UE indicates the need for an uplink resource by a Scheduling Request Indicator (SRI). The SRI is transmitted using PUCCH Format 1. On-off keying based signaling is applied with SRI, i.e. only positive SRI is transmitted.

5

7.3.1

6

Definition: SR configuration index I SR determines SR transmission periodicity and subframe offset.

2 3

Released - For Current Employee/Consultant Use Only

PUCCH, Uplink scheduling support SRS/SR & SPS

Sr-ConfigIndex

IE Value

Allowed Range

Recommended

Engineering Units

INTEGER

INTEGER

(0,…, 155)

(0,…, 155)

Set it to 0-14 for low uplink load; Set it to large value for high uplink load but subject to latency limits.

10

Setting Tradeoff: If a low index is configured, SR periodicity is short, thus scheduling request can be performed more often but with an increase of overhead. If an high index is configured SR transmission periodicity is long, thus UE can request scheduling less often and lower overhead is introduced, but increases the latency.

11

Dependencies/Constraints:

12

Traceability: TS36.331 Sect. 6.3.2, TS36.213 Sect. 10.1

13

RRC Message Structure:

7 8 9

14 15

RRCConnectionSetup radioResourceConfigDedicated physicalConfigDedicated scheduli ngRequestConfig Sr-ConfigIndex

17

RRCConnectionReconfiguration radioResourceConfigDedicated physicalConfigDedicated schedulingRequestConfig Sr-ConfigIndex

18

Notes:

16

19 20

21 22 23 24

The SR configuration for SR transmission periodicity and subframe offset is defined by SR configuration index I SR in Table 10.1-5. SR transmission instances are the subframes satisfying 10 × n f + ns / 2 − N OFFSET , SR mod SRPeriodicity = 0 , where n f is the system frame number, and ns

(

)

= {0,1,…, 19} is the slot index within the frame, and NOFFSET,SR is the SR subframe offset defined in Table 10.1-5 and SRPeriodicity is the SR periodicity defined in Table 7-9. .

25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

167

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Released - For Current Employee/Consultant Use Only

1

PUCCH, Uplink scheduling support SRS/SR & SPS

Table 7-9. UE-specific SR periodicity and subframe offset configuration SR configuration Index I SR

SR periodicity (ms)

0–4 5 – 14 15 – 34 35 – 74 75 – 154 155

5 10 20 40 80

SR subframe offset I SR I SR − 5 I SR − 15 I SR − 35 I SR − 75

Reserved

2 3

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

168

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

7.3.2

PUCCH, Uplink scheduling support SRS/SR & SPS

Sr-PUCCH-ResourceIndex

Definition: Defines the PUCCH resource to be used to report persistent scheduling request information. IE Value

Allowed Range Recommended

INTEGER

INTEGER

(0,…, 2047)

(0,…, 2047)

UE specific

4

Setting Tradeoff: UE specific configuration.

5

Dependencies/Constraints:

6

Traceability: TS36.331 Sect. 6.3.2, TS36.213 Sect. 5.5.3

7

RRC Message Structure:

8 9 10 11

Engineering Units

RRCConnectionSetup radioResourceConfigDedicated physicalConfigDedicated scheduli ngRequestConfig Sr-PUCCH-ResourceIndex RRCConnectionReconfiguration radioResourceConfigDedicated physicalConfigDedicated schedulingRequestConfig Sr-PUCCH-ResourceIndex

12 13

Notes:

14

(1) (1) The scheduling request (SR) shall be transmitted on the PUCCH resource nPUCCH = nPUCCH,SRI , where

15

(1) nPUCCH, SRI is UE specific and configured by higher layers.

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

169

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

7.3.3

PUCCH, Uplink scheduling support SRS/SR & SPS

dsr-TransMax

Definition: configures the maximum number of unanswered Scheduling Requests (SR) before notifying RRC of the SR release, initiating a Random Access procedure and cancelling all pending SRs. IE Value

Allowed Range Recommended

Engineering Units

ENUMERATED

ENUMERATED

(n4, n8, n16, n32, n64)

(4, 8, 16, 32, 64)

64

8

Setting Tradeoff: If a high value is configured, UE can keep sending unanswered SRs for longer time, postponing the initiation of Random Access procedure thus trying to ask for allocation of resources for a longer time. If a small value is set, UE starts Random Access procedure and cancel all pending SRs earlier.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS36.331 Sect. 6.3.2, TS36.321 Sect. 5.4.4

11

RRC Message Structure:

12 13

RRCConnectionSetup radioResourceConfigDedicated physicalConfigDedicated scheduli ngRequestConfig dsr-TransMax

15

RRCConnectionReconfiguration radioResourceConfigDedicated physicalConfigDedicated schedulingRequestConfig dsr-TransMax

16

Notes:

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

170

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

2

8 Uplink Power Control Paramenter Settings

3

Chapter 8: Table of Contents

4

8.1 PUSCH and SRS Power Control .......................................................................................................... 173

5

8.1.1 Introduction ......................................................................................................................................... 173

6

8.1.2 p0-NominalPUSCH (PO_NOMINAL_PUSCH(1)) ........................................................................ 176

7

8 9

8.1.3 p0-NominalPUSCH-Persistent (𝑷𝑶_𝑵𝑶𝑴𝑰𝑵𝑨𝑳_𝑷𝑼𝑺𝑪𝑯 (𝟎)) ................................................................. 177

8.1.4 alpha ..................................................................................................................................................... 178 8.1.5 p0-UE-PUSCH (PO_UE_PUSCH(1)) ................................................................................................ 179

11

8.1.6 p0-UE-PUSCH-Persistent (𝑷𝑶_𝑼𝑬_𝑷𝑼𝑺𝑪𝑯 (𝟎)) .................................................................................... 180

12

8.1.8 deltaMCS-Enabled (Ks) ...................................................................................................................... 182

13

8.1.9 accumulationEnabled ......................................................................................................................... 183

14

8.1.10 filterCoefficient .................................................................................................................................. 185

15

8.1.11 pSRS-Offset (PSRS_OFFSET) ........................................................................................................... 186

16

8.2 PUCCH Power Control ......................................................................................................................... 187

17

8.2.1 Introduction ......................................................................................................................................... 187

18

8.2.2 p0-NominalPUCCH (PO_NOMINAL_PUCCH) ........................................................................... 188

19

8.2.3 p0-UE-PUCCH (PO_UE_PUCCH) ............................................................................................................. 189

20

p0-UE-PUCCH (PO_UE_PUCCH) ............................................................................................................ 189

10

21

22

23

24

25

8.1.7 deltaPreambleMsg3 (

Δ PREAMBLE_Msg3

) ................................................................................................ 181

8.2.4 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 1) ............................................................................. 190 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 1)...................................................................................... 190 8.2.5 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 1b) ........................................................................... 191

8.2.6 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 2) ............................................................................. 192 8.2.7 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 2a) ........................................................................... 193 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

171

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

8.2.8 deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 2b) ........................................................................... 194

Released - For Current Employee/Consultant Use Only

2

Uplink Power Control Paramenter Settings

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

172

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3 4

Released - For Current Employee/Consultant Use Only

5 6 7 8 9 10 11 12 13 14 15

Uplink Power Control Paramenter Settings

This chapter discusses the parameters that play an integral role in the power control of the following LTE UL channels – PUSCH, PUCCH and SRS. The UL power control in LTE attempts to compensate for radio propagation variations such as shadowing, fading and overcoming interference between other users from neighboring cells in order to achieve a desired Signal to Interference/Noise Ratio (SINR) at the eNodeB to match QoS/data rate requirements for a UE. In some extremely loaded PUCCH cases, power control may be used to manage intra-cell interference on PUCCH. Power control in LTE is a combination of open-loop and closed-loop power control. The open-loop component aims at setting a desired UE transmit power level based on path-loss estimates from the UE (to compensate for free-space propagation loss and shadowing)in conjunction with cell-specific and UE-specific static power offset parameters. The closed-loop component attempts to combat fast fading, inaccuracies in UE’s pathloss estimation or transmit power settings, varying interference from neighbor cells, varying UL data rate requirements. It adjusting UL power based on power control commands from the eNodeB and changes in UL assignment (RBs and MCS) If UL power control parameters are not set appropriately some of the following negative impacts may be seen:

16

-

Lower UL cell capacity due to increased UL interference from in neighbor cells

17

-

Lower UL data rates achievable especially for UEs at cell-edge

18

-

Higher mis-detection of control information such as ACK/NAK and CQI/RI possibly resulting in slightly lower DL throughput and increased latency

-

Higher PUSCH BLER – during/immediately after call-setup, after handovers to a new LTE cell and after periods of inactivity during which UL PC are not received

-

Slightly increased call-setup delay due to increased UL HARQ retransmissions and time taken for UL PC to increase UE transmit power

19 20 21 22 23

24

8.1 PUSCH and SRS Power Control

25

8.1.1

Introduction

27

The power control of the PUSCH and SRS are closely related with only some differences in power offsets and bandwidth.

28

In general, the PUSCH, SRS power consists

26

29

-

A basic open-loop power: P0 +alpha*Path-loss (SRS specific offset may also be included)

30

-

Dynamic Offset: Delta_TF(MCS dependant) +TPC command

31

-

Bandwidth factor: Function of the number of RBs for PUSCH or SRS

32 33 34 35 36 37 38 39

The power control formula allows the entire range of UE power to be covered (~-50dBm to +23dBm). The use of alpha allows varying the degree to which pathloss impacts UL Power Spectral Density (PSD). Such fractional power control can improve UL cell-capacity while minimizing degradation of cell-edge user data rates. The MCS dependant component can be used to adjust the PUSCH power based on different UL transport formats. The TPC commands for PUSCH/SRS are carried in PDCCH DCI format 0 or DCI format 3/3a and allow fine adjustment of the UE power to combat signal fading, UL interference or UE transmit power inaccuracies.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

173

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9 10 11 12

Uplink Power Control Paramenter Settings

The bandwidth factor adjusts the transmission power based on the number of RBs of the PUSCH or SRS respectively. Two options exist for PUSCH/SRS power control – Accumulative or Absolute PC modes (set semistatically via RRC signaling). In case of Accumulative PC which we recommend be the default mode of operation, the TPC commands are relative to the prior command and this scheme is particularly suited to cases where UE is receiving TPC commands on a fairly continuous basis. The range of PC adjustment via this scheme is large and only limited by the maximum and minimum UE transmit power. In case of Absolute PC the TPC commands only allow adjustment of the UE power with respect to the semi-static operating point, albeit with a slightly larger range for the TPC command. This scheme is suited to cases where UEs may not receive TPC commands often and may need a large adjustment immediately after certain transmission gaps.

13 14

15

16

The transmit power of the PUSCH in subframe i is defined by

PPUSCH (i ) = min{PCMAX ,10 log10 ( M PUSCH (i )) + PO_PUSCH + α ⋅ PL + ∆ TF (i ) + f (i )} [dBm] where

18

PCMAX is the maximum transmit power of the UE and depends on UE Power Class. For power class 3 currently defined for LTE UEs, PCMAX is 23 dBm (see 3GPP TS 36.101, sec 6.2.2).

19

MPUSCH is the bandwidth of the PUSCH in number of RBs in subframe i

17

20 21 22 23 24 25

PO_PUSCH is a parameter composed the sum of the cell-specific parameter PO_NOMINAL_PUSCH and UEspecific parameter PO_UE_PUSCH. PO_NOMINAL_PUSCH is the base PUSCH transmission power common for all UEs within the cell . PO_UE_PUSCH is a UE-specific offset to the P0_NOMINAL_PUSCH allowing UEspecific adjustment to the base PUSCH power. Both these parameters are signaled to the UE via RRC messages. When PUSCH is sent in response to Random Access Response (RAR), P0_NOMINAL_PUSCH = P0_PRE+ Delta_PREAMBLEMSG3 and P0_UE_PUSCH =0

30

𝛼 is the path-loss compensation factor allowing for the UE transmit power to be adjusted based on the path-loss experienced by the UE. It can alsobe used for interference management when set to a value lower than 1, allows for lesser compensation of path-loss and hence reduces the rate at which UE transmit power increases as a function of path-loss. Alpha is set to a specific value of 1 (full path-loss compensation) when PUSCH is sent in response to RAR

31

PL is the UE estimated pathloss based on filtered RSRP measurements

26 27 28 29

33

Delta_TF is the MCS dependant offset to the PUSCH power. This offset can be enabled or disabled based on Ks (deltaMCS-Enabled) which is signaled via RRC message

34

f(i) is the PUSCH power control command to be applied in this subframe i.

32

35 36

37

38

The transmit power of the SRS in subframe i is defined by

PSRS (i ) = min{PCMAX , PSRS_OFFSET + 10 log10 ( M SRS ) + PO_PUSCH + α ⋅ PL + f (i )} [dBm] where

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

174

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

5

Uplink Power Control Paramenter Settings

PSRS_OFFSET is a UE specific parameter semi-statically configured by RRC message which takes final

value depending on whether Ks=0 or 1.25. This is an SRS specific offset to the base PUSCH power which is composed of P0_NOMINAL_PUSCH and P0_UE_PUSCH as detailed above. M SRS is the bandwidth of the SRS transmission in subframe i expressed in number of resource blocks.

For other common parameter definitions see PUSCH power control section above.

6

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

175

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

8.1.2

Uplink Power Control Paramenter Settings

p0-NominalPUSCH (PO_NOMINAL_PUSCH(1))

Definition: Indicates the cell specific nominal component of PUSCH P0, which is used in the UL power control procedure for non-persistent scheduling. This parameter sets a common base PUSCH transmit power for all UEs within the cell. IE Value

Allowed Range

Integer (-126…24)

Engineering Units

-126…24 dBm, in steps of 1 dB

Set it above the eNB PUSCH sensitivity level. Recommended

Ideally, p0-NominalPUSCH = -174 + 10*log(PUSCH BW) + eNB NF + C/I (function of minimum MCS) + PUSCH RoT

5 6 7 8 9 10 11 12 13 14 15

Setting Tradeoff: Higher setting will improve PUSCH reception, but will also drive higher UE transmit power leading to interference to neighboring cells resulting in lower overall cell-throughput in loaded condition and subsequent PC commands will be needed to adjust UE transmit power. Higher settings will be needed if alpha is set to a very low value so that the base PUSCH power can be increased when there is lack of path-loss compensation. Lower setting may result in UE transmit power starting at a low value during call-setup/after HO causing higher initial PUSCH BLER, increased UL HARQ retransmissions and possibly slower callsetup and lower initial UL data rates until PC commands adjust UE power upwards to required level. The UL power could be increased significantly over a certain time-duration using Accumulated PC commands.

18

Dependencies/Constraints: PO_NOMINAL_PUSCH should be set in combination with PO_UE_ PUSCH, a UE specific component of Po_PUSCH . This parameter should also be set in combination with path loss compensation and interference management factor alpha.

19

This parameter is applicable for non-persistent scheduling only.

20

Traceability: TS 36.213, Sect. 5.1.1.1, TS36.331, Sect 6.3.2

16 17

21 22 23

RRC Message Structure: SIB2  RadioResourceConfigCommon  RadioResourceConfigCommonSIB  UplinkPowerControl  UplinkPowerControlCommon  p0NominalPUSCH

29

Notes: The range of the PO_NOMINAL_PUSCH is designed to cover the full range of target SINR values for different degrees of path-loss compensation, transmission bandwidths and interference levels. The highest value of PO_NOMINAL_PUSCH, +23 dBm, corresponds to the maximum transmission power and would typically only be used if the path-loss compensation alpha was not being used at all. The lowest value of PO_NOMINAL_PUSCH, -126 dBm, is relevant to a case when full path-loss compensation is used and the uplink transmission and reception conditions are optimal

30

Ideally the value should be derived from the equation:

24 25 26 27 28

31 32

p0-NominalPUSCH = -174 + 10*log(PUSCH BW) + eNB NF + C/I (function of minimum MCS) + PUSCH RoT

33

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

176

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

8.1.3

Uplink Power Control Paramenter Settings

p0-NominalPUSCH-Persistent (𝑷𝑶_𝑵𝑶𝑴𝑰𝑵𝑨𝑳_𝑷𝑼𝑺𝑪𝑯 (𝟎))

Definition: Determines the cell specific parameter 𝑷𝑶_𝑵𝑶𝑴𝑰𝑵𝑨𝑳_𝑷𝑼𝑺𝑪𝑯 (𝟎) that is used for PUSCH power control for semi-persistent scheduling.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Integer (-126…24)

Recommended

see 8.1.2

Engineering Units

-126…24 dBm, in steps of 1 dB

4 5

Setting Tradeoff: see 8.1.2.

6

Dependencies/Constraints: This parameter is applicable for semi-persistent scheduling only.

7

Traceability: TS 36.213, Sect. 5.1.1.1, TS 36.321 Sect 5.10, TS36.331, Sect 6.3.2

8

RRC Message Structure:

10

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  sps-ConfigUL  p0Persistent  p0-NominalPUSCH-Persistent

11

Notes: None.

9

12

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

177

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Uplink Power Control Paramenter Settings

1

8.1.4

alpha

2

Definition: A cell specific parameter that indicates path loss compensation factor

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Units

Allowed Range

Enumerated {al0, al04, al05, al06, al07,al08, al09, al1}

0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1

Recommended

al08

0.8

7

Setting Tradeoff: Full path loss compensation (alpha close to 1) permits higher cell edge data rate maximizing fairness for cell edge UEs but determines lower total uplink capacity. Lower path-loss compensation can increase the total system capacity in the uplink, as less UL power resources are spent ensuring the success of transmissions from cell edge UEs and less inter-cell interference is caused to neighboring cells. However, cell-edge data rate is degraded.

8

Dependencies/Constraints: Alpha should be set in combination with P0,NOMINAL_PUSCH.

9

Traceability: TS 36.213, Sect. 5.1.1.1, TS36.331, Sect 6.3.2

3 4 5 6

11

RRC Message Structure: SIB2  RadioResourceConfigCommon  UplinkPowerControl  UplinkPowerControlCommon  alpha

12

Notes:

10

13 14 15 16 17 18 19

Setting alpha to 0 disables the PL compensation and gives the eNB full control of UE Tx power. Setting alpha to 1 means full PL compensation. Setting alpha in the range {0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1} corresponds to a partial compensation of the PL. There are performance simulation studies suggesting that path-loss compensation factors around 0.70.8 could give a close-to-maximal uplink system capacity without causing significant degradation to the cell-edge data rate that can be achieved. The overall power utilization is roughlythe same using the closed loop power control with full and fractional compensation set to 0.8.

20 21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

178

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

8.1.5

Uplink Power Control Paramenter Settings

p0-UE-PUSCH (PO_UE_PUSCH(1))

Definition: UE specific parameter that is used for PUSCH power control for non-persistent scheduling. This is used in addition to the cell-specific parameter PO_NOMINAL_PUSCH IE Value

Integer (-8..7)

Allowed Range Recommended 4 5 6 7

8 9 10 11 12

0

Engineering Units

-8, -7 … 7 dB (steps of 1 dB) 0 dB

Setting Tradeoff: If parameter is too small, the UE may take longer to ramp-up up to desired level resulting in PUSCH BLER and and lower initial UL throughput especially at cell-edge. If set too high the UE may cause undesired interference to neighboring cells (especially near edge of serving cell) and in some cases saturate the eNodeB receiver (when very close to the serving cell) Typically this UE-specific parameter should be set carefully based on analysis and if it is seen that certain UEs have specific errors in either pathloss estimation or transmit power accuracy. Given that the PO_NOMINAL_PUSCH can allow setting of the initial desired operating point, this UE-specific parameter which can be set to 0, may only need to be set differently for certain UE types to either positively/negatively offset PO_NOMINAL_PUSCH .

14

Dependencies/Constraints: This parameter value should be jointly considered with the alpha and PO_NOMINAL_PUSCH parameter values.

15

This parameter is applicable for non-persistent scheduling only.

16

Traceability: TS 36.213, Sect. 5.1.1.1, TS36.331, Sect 6.3.2

17

RRC Message Structure:

13

18 19 20 21

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  p0-UE-PUSCH RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  p0-UE-PUSCH

23

RRCConnectionReestablishment  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  p0-UE-PUSCH

24

Notes:

22

25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

179

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

8.1.6

Uplink Power Control Paramenter Settings

p0-UE-PUSCH-Persistent (𝑷𝑶_𝑼𝑬_𝑷𝑼𝑺𝑪𝑯 (𝟎))

Definition: Determines the UE specific parameter 𝑷𝑶_𝑼𝑬_𝑷𝑼𝑺𝑪𝑯 (𝟎) that is used in PUSCH power control for semi-persistent scheduling.

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Units

Allowed Range

Integer (-8…7)

-8, -7 … 7 dB (steps of 1 dB)

Recommended

0

0 dB

4 5

Setting Tradeoff: see 8.1.5.

6

Dependencies/Constraints: This parameter is applicable for semi-persistent scheduling only.

7

Traceability: TS 36.213, Sect. 5.1.1.1, TS 36.321 Sect 5.10, TS36.331, Sect 6.3.2

8

RRC Message Structure:

10

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  sps-ConfigUL  p0Persistent  p0-UE-PUSCH-Persistent

11

Notes: None.

9

12

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

180

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

8.1.7

Uplink Power Control Paramenter Settings

deltaPreambleMsg3 ( Δ PREAMBLE_Msg3 )

Definition: Nominal offset between PRACH power and PUSCH Msg3 transmit power. Note that the PRACH power is the final power at which PRACH was transmitted and received a successful RAR, following which PUSCH Msg3 is being sent. IE Value

Allowed Range Recommended 5 6 7 8 9 10

Engineering Units

Integer (-1..6)

-2 dB, 0 dB, 2 dB, 4dB, 6dB, 8 dB, 10 dB, 12 dB

1-2

2-4 dB

Setting Tradeoff: If this parameter is too large it could boost the nominal Msg3 transmit power significantly above the PRACH power that may aid in detection of the Msg3 for UEs at cell-edge while causing undesired interference to neighbor cells. If this parameter is set too low, it may set the nominal Msg3 power almost same or lower than PRACH power that may result in Msg3 failures for cell-edge UEs and require Msg3 retransmissions and slight delays to complete Contention Resolution procedure while avoiding any undesired UL interference to neighboring cells.

13

Dependencies/Constraints: This parameter should be set in conjunction with the parameter preambleInitialReceivedTargetPower that defines the open-loop power of the PRACH, especially since this is an offset to the PRACH nominal power

14

Traceability: TS 36.213, Sect. 5.1.1.1, TS36.331, Sect 6.3.2

11 12

15 16 17 18

RRC Message Structure: SIB2  RadioResourceConfigCommon  UplinkPowerControl  UplinkPowerControlCommon  deltaPreambleMsg3 Notes: The parameter allows setting of the initial preamble power flexibly as the Msg3 power can be offset to the preamble power using this parameter.

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

181

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3 4

8.1.8

Uplink Power Control Paramenter Settings

deltaMCS-Enabled (Ks)

Definition: A UE-specific parameter that enables or disables the MCS dependent component of the PUSCH power control. When enabled, this parameter allows eNodeB to scale the PUSCH transmit power based on the UL MCS scheduled via the PDCCH for a specific UE. IE Value

Engineering Units

Allowed Range

Enumerated {en0, en1}

0 (disabled), 1.25 (enabled)

Recommended

en1

enabled

8

Setting Tradeoff: If this parameter is disabled, the PUSCH transmit power cannot be varied based implicitly on the MCS and frequent UL power control commands combined with UL HARQ is recommended to ensure appropriate UL power spectral density and good UL performance. If this parameter is enabled, the UL power will be scaled based on MCS

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 36.213, Sect. 5.1.1.1, TS36.331, Sect 6.3.2

11

RRC Message Structure:

12 13 14 15

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  deltaMCS-Enabled RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  deltaMCS-Enabled

17

RRCConnectionReestablishment  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  deltaMCS-Enabled

18

Notes:

16

19 20 21 22 23

Enabling this parameter can allow frequency dependent power control by enabling low rate MCS by eNodeB in specific parts of UL frequency band to control UL interference – this will require some coordination between eNodeBs to indicate over-load/interference. This parameter can also be used to reduce UL power in cases where the number of UL RBs is not matched to the SIR/target data rate.

24 25

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

182

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

8.1.9

Uplink Power Control Paramenter Settings

accumulationEnabled

Definition: This parameter allows selection between use of Accumulative Power control (when set to TRUE) and Absolute Power control (when set to False) for the PUSCH IE Value

Boolean Allowed Range

Recommended 4 5 6 7 8 9 10

Engineering Units

TRUE (enabled) – Accumulative power control FALSE (disabled) – Absolute power control

TRUE

Accumulative

Setting Tradeoff: When Accumulative PC is enabled, the UE power is changed with steps in a range of +3dB to -1dB (see Notes) with relationship to the prior TPC command received. This allows UE power to change over a very large range but in steps within the maximum UE power limit and also the provision of a 0 dB step allows power to be maintained constant. However, in some cases to adjust the UE power to the desired level quickly it may require multiple PC commands to be received resulting in slightly degraded UL performance in cases where a large increase/decrease is needed suddenly and also slightly higher UL interference where UE Tx power needs to be reduced suddenly.

14

When Absolute PC is used, the UE power is adjusted with steps of +4 to -4dB without any consideration of prior TPC commands. This allows UE power to be increased or decreased suddenly by an absolute amount relative to nominal PUSCH power though a large range of increase/decrease of PUSCH power is not possible with Absolute TPC command.

15

Dependencies/Constraints:

16

Traceability: TS 36.213, Sect. 5.1.1.1, TS36.331, Sect 6.3.2

17

RRC Message Structure:

11 12 13

18 19 20 21 22 23

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  accumulationEnabled RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  accumulationEnabled RRCConnectionReestablishment  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  accumulationEnabled

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

183

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7

Uplink Power Control Paramenter Settings

Notes: Absolute TPC may be used when UE is transitioning out of an idle state (when eNodeB does not have an exact idea of the UE’s channel conditions) by setting accordingly in RRCConnectionSetup message – this may allow eNodeB to achieve a certain target SINR faster by adjusting UE transmit power in fewer steps. Once the UE is in connected/active state and the eNodeB has a good UL channel estimate for the UE, it may be reconfigured to Accumulative mode using the RRCConnectionReconfiguration.

8 9 10 11 12

The TPC command received in DCI format 0/3/3a is mapped to the actual power control step in dB. From TS36.213 Section 5.1.1.1 Table 8-1 Mapping of TPC Command Field in DCI format 0/3 to absolute and accumulated δ PUSCH values.

13

TPC Command Field in DCI format 0/3 0 1 2 3

Accumulated δ PUSCH [dB] -1 0 1 3

Absolute δ PUSCH [dB] only DCI format 0 -4 -1 1 4

14 15

Table 8-2 Mapping of TPC Command Field in DCI format 3A to δ PUSCH values.

16

TPC Command Field in DCI format 3A 0 1

δ PUSCH [dB]

-1 1

17 18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

184

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Uplink Power Control Paramenter Settings

8.1.10 filterCoefficient Definition: This parameter defines the filtering coefficient for RSRP measurements used to calculate path loss. These filtered RSRP measurements and computed pathloss are used to determine the openloop component of the PUSCH, PUCCH and SRS transmit power IE Value

Allowed Range

Enumerated {fc0, fc1, fc2, fc3, fc4, fc5,fc6, fc7, fc8, fc9, fc11, fc13, fc15, fc17, fc19, spare1, ...}

Engineering Units

k = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19

Default: fc4 Recommended 5 6 7 8

fc4 (Default)

Setting Tradeoff: If this parameter is too large, the filtered RSRP measurements may converge too slowly resulting in a slowly changing pathloss. As a result the UE transmit power may not adjust fast enough to suitably track shadowing, requiring larger power control command changes from the eNodeB and potentially some degraded PUSCH/PUCCH/SRS detection performance.

12

If this parameter is set too small, the filtering of the RSRP measurements is minimal and may result in large computed path-loss variations. As a result the open-loop component of the PUSCH/PUCCH/SRS power may change very quickly making it more difficult for the eNodeB to control UE transmit power via power control commands and negatively impacting UL performance

13

Dependencies/Constraints:

14

Traceability: TS 36.213, Sect. 5.1.1.1, TS36.331, Sect 6.3.2

15

RRC Message Structure:

9 10 11

16 17 18 19

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  filterCoefficient RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  filterCoefficient

21

RRCConnectionReestablishment  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  filterCoefficient

22

Notes:

20

23 24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

185

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Uplink Power Control Paramenter Settings

8.1.11 pSRS-Offset (PSRS_OFFSET) Definition: SRS power offset applied on top of the nominal pathloss and SRS bandwidth dependant component of the SRS power. This parameter is UE-specific and is an offset to the computed PUSCH transmit power with similar bandwidth. IE Value

Integer (0..15) Allowed Range

Recommended

5 6 7 8 9 10

Engineering Units

For Ks=en1 (1.25), pSRS-Offset = IE value – 3 For Ks=en0 (0), pSRS-Offset = -10.5 + 1.5*IE value

7 for Ks = 0

0 dB

3 for Ks = 1.25

Setting Tradeoff: If this parameter is too large, the UE SRS transmit power may be too high and cause UL interference to neighboring cells. If this is set too low, SRS power received (and resulting SINR) at the eNodeB may be insufficient which may negatively impact some/all of the following UL channel estimation, link adaptation, power control and frequency selective scheduling decisions made by the eNodeB based on the SRS. Typically larger the SRS configured bandwidth, the lower this parameter can be set.

12

Dependencies/Constraints: Parameter value is dependent on whether KS(delta_mcs) is enabled or not

13

Traceability: TS 36.213, Sect. 5.1.3.1, TS36.331, Sect 6.3.2

14

RRC Message Structure:

11

15 16 17 18

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  pSRS-Offset RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  pSRS-Offset

20

RRCConnectionReestablishment  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  pSRS-Offset

21

Notes:

22

For K S = 1.25 , PSRS_OFFSET is a 4-bit UE specific parameter semi-statically configured by

19

23 24

25 26 27

higher layers with 1dB step size in the range [-3, 12] dB. The actual value is pSRS-Offset value – 3. For K S = 0 , PSRS_OFFSET is a 4-bit UE specific parameter semi-statically configured by higher layers with 1.5 dB step size in the range [-10.5,12] dB. The actual parameter value is -10.5 + 1.5*pSRS-Offset value.

28

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

186

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

8.2 PUCCH Power Control

2

8.2.1

3

Released - For Current Employee/Consultant Use Only

Uplink Power Control Paramenter Settings

4 5 6 7

Introduction

PUCCH power control differs from PUSCH/SRS power control given that there is no path-loss compensation factor alpha. Given that multiple users may be code-division multiplexed on the same PUCCH resource and thus control interference between users only full path-loss compensation is allowed. A different base power level dependent on PO_PUCCH allows setting of specific UL operating point for the PUCCH.

8 9

The transmit power of the PUCCH in subframe i is defined by

PPUCCH (i ) = min{PCMAX , PO_PUCCH + PL + h(nCQI , n HARQ ) + ∆ F_PUCCH (F ) + g (i )} [dBm]

10

11

where

12

PCMAX is the maximum transmit power of the UE which is function of UE class

13

14

∆ F_PUCCH ( F ) is a power offset for each PUCCH format 1, 1b, 2, 2a, 2b relative to PUCCH format 1a h(n ) is a PUCCH format dependent value, where nCQI corresponds to the number information bits for

15

the channel quality information and n HARQ is the number of HARQ bits. This compensates for the

16

PUCCH power based on the number of control bits being carried on the PUCCH

17 18

PO_PUCCH is a parameter composed of the sum of a cell specific parameter PO_NOMINAL_ PUCCH and a UE

specific component PO_UE_PUCCH

21

δ PUCCH is a UE specific TPC command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2 or sent jointly coded with other UE specific PUCCH correction values on a PDCCH with DCI format 3/3A whose CRC parity bits are scrambled with TPC-PUCCH-RNTI.

22

For other common parameter definitions see PUSCH power control section.

19 20

23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

187

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

8.2.2

Uplink Power Control Paramenter Settings

p0-NominalPUCCH (PO_NOMINAL_PUCCH)

Definition: Indicates the cell specific nominal component of PUCCH P0, which is used in the UL power control procedure.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Integer (-127..-96)

Engineering Units

-127…-96 dBm, in steps of 1 dB

Set it above the eNB PUCCH sensitivity level. Recommended

4 5

Ideally, p0- NominalPUCCH = -174 + 10*log(PUCCH BW) + eNB NF + PUCCH C/I + PUCCH RoT

Setting Tradeoff: Higher settings will improve PUCCH reception, but will also drive higher UE Tx power leading to interference to neighboring cells, and vice versa.

7

Dependencies/Constraints: PO_NOMINAL_PUCCH should be set in combination with PO_UE_PUCCH, a UE specific component of PUCCH P0.

8

Traceability: TS 36.213, Sect. 5.1.2.1, TS36.331, Sect 6.3.2

6

11

RRC Message Structure: SIB2  RadioResourceConfigCommon  RadioResourceConfigCommonSIB  UplinkPowerControl  UplinkPowerControlCommon  p0NominalPUCCH

12

Notes:

13

Ideally the value should be derived from the equation:

14

p0- NominalPUCCH = -174 + 10*log(PUCCH BW) + eNB NF + PUCCH C/I + PUCCH RoT.

9 10

15 16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

188

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Uplink Power Control Paramenter Settings

p0-UE-PUCCH (PO_UE_PUCCH)

1

8.2.3

2

Definition: UE-specific parameter that impacts PUCCH power control (open-loop component).

Released - For Current Employee/Consultant Use Only

IE Value

3 4 5

Engineering Units

Allowed Range

Integer (-8..7)

-8 … 7 dB, in steps of 1 dB

Recommended

0

0 dB

Setting Tradeoff: If PO_UE_PUCCH is set too large for a specific UE, the PUCCH transmit power may be increased significantly causing interference to other users PUCCH transmissions in the same cell that are CDM on same PUCCH resource as well as to neighboring cells.

11

If the parameter is set too small, the PUCCH transmit power may be decreased significantly resulting in possible mis-detection of ACK/NAK/CQI/RI which can result in duplicate DL PDSCH transmissions, incorrect DL link/rate adaptation and lower DL throughput. The eNodeB could use TPC commands to subsequent increase the PUCCH power but a very low parameter setting could potentially impact initial PUCCH transmit power as well as periods where there are no DL grants carrying TPC for PUCCH.

12

Dependencies/Constraints:

13

Traceability: TS 36.213, Sect. 5.1.2.1, TS36.331, Sect 6.3.2

14

RRC Message Structure:

6 7 8 9 10

15 16 17 18 19 20 21 22 23 24 25 26

RRCConnectionSetup  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  p0-UE-PUCCH RRCConnectionReconfiguration  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  p0-UE-PUCCH RRCConnectionReestablishment  RadioResourceConfigDedicated  PhysicalConfigDedicated  UplinkPowerControlDedicated  p0-UE-PUCCH Notes: This parameter may be used by the eNodeB to compensate for any systematic UE errors in UE’s pathloss estimation or absolute transmit power setting. This parameter may be semi-statically configured to a higher value when eNodeB detects that there is no Ul data from the UE for a while. At that time since there is no UL traffic to carry ACK/NAK/CQI multiplexed with data on PUSCH, this parameter could be set higher to ensure that when ACK/NAK/CQI are sent on PUCCH they are received accurately at the eNodeB.

27 28

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

189

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

8.2.4

Uplink Power Control Paramenter Settings

deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 1)

Definition: Denotes the delta value (power offset) applied in uplink power control when PUCCH format type 1 (Scheduling Request) is transmitted, relative to PUCCH format type 1a. IE Value

4 5 6 7 8 9

Engineering Units

Allowed Range

Enumerated {deltaF-2, deltaF0, deltaF2}

-2 dB, 0 dB, 2dB

Recommended

deltaF2

2dB

Setting Tradeoff: If this parameter is too large, the PUCCH SR may be sent at higher than required power and in some cases may cause excessive interference to other users PUCCH transmissions with different formats as well as additional interference to neighboring cells in these PUCCH RBs. If set too low, the probability of missing PUCCH SR at eNodeB may be greater due to lower operating point and this could result in the UE taking longer to receive UL grants until SR is finally detected or RACH is sent and RAR received

10

Dependencies/Constraints:

11

Traceability: TS 36.213, Sect. 5.1.2, TS36.331, Sect 6.3.2

14

RRC Message Structure: SIB2  RadioResourceConfigCommon  RadioResourceConfigCommonSIB  UplinkPowerControl  UplinkPowerControlCommon  deltaFList-PUCCH  deltaF-PUCCH-Format1

15

Notes:

12 13

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

190

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

8.2.5

Uplink Power Control Paramenter Settings

deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 1b)

Definition: Denotes the power offset applied in uplink power control when PUCCH format type 1b (2 bit ACK/NAK) is transmitted. IE Value

4 5 6 7 8 9

Allowed Range

Enumerated {deltaF1, deltaF3, deltaF5}

1 dB, 3dB, 5dB

Recommended

deltaF3

3 dB

Setting Tradeoff: If this parameter is too large, the PUCCH Format 1b may be sent at higher than required power and in some cases may cause excessive interference to other users PUCCH transmissions with different formats as well as additional interference to neighboring cells in these PUCCH RBs. If set too low, the ACK/NAK bits carried on PUCCH may be mis-detected resulting in either duplicate DL transmissions(ACK->NAK) which reduce useful DL throughput or premature termination of HARQ (NAK->ACK) which increases delays and could reduce DL throughput.

10

Dependencies/Constraints:

11

Traceability: TS 36.213, Sect. 5.1.2, TS36.331, Sect 6.3.2

12 13 14 15 16 17 18 19 20

Engineering Units

RRC Message Structure: SIB2  RadioResourceConfigCommon  RadioResourceConfigCommonSIB  UplinkPowerControl  UplinkPowerControlCommon  deltaFList-PUCCH  deltaF-PUCCH-Format1b Notes: The entire range of this parameter is already higher than format 1 by 3dB owing to the 2 bit ACK/NAK payload on PUCCH format 1b compared to 1 bit ACK/NAK on PUCCH format 1a. This parameter may be set higher than the offset for PUCCH format 2 (carrying CQI) to ensure that ACK/NAK is always detected accurately Setting this parameter may be based on target error rate (probability of miss, DTX->ACK) for ACK/NAK on UL.

21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

191

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

8.2.6

Uplink Power Control Paramenter Settings

deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 2)

Definition: Denotes the power offset applied in uplink power control when PUCCH format type 2 is transmitted. IE Value

4 5 6 7 8 9

Engineering Units

Allowed Range

Enumerated {deltaF-2, deltaF0, deltaF1, deltaF2}

-2 dB, 0 dB, 1 dB, 2 dB

Recommended

deltaF0

0 dB

Setting Tradeoff: If this parameter is too large, the PUCCH Format 2 carrying CQI may be sent at higher than required power and in some cases may cause excesive interference to other users PUCCH transmissions with different formats as well as additional interference to neighboring cells in these PUCCH RBs. If set too low, the CQI bits carried on PUCCH may be detected incorrectly which could negatively impact DL link adaptation (imperfect eNodeB scheduling decisions) and reduce DL throughput.

10

Dependencies/Constraints:

11

Traceability: TS 36.213, Sect. 5.1.2, TS36.331, Sect 6.3.2

14

RRC Message Structure: SIB2  RadioResourceConfigCommon  RadioResourceConfigCommonSIB  UplinkPowerControl  UplinkPowerControlCommon  deltaFList-PUCCH  deltaF-PUCCH-Format2

15

Notes:

12 13

16 17 18

In general, this parameter could be set lower to reduce interference since PUCCH format 2 carries CQI only while other PUCCH format offsets that carry ACK/NACK bits could be set higher, given that ACK/NAK accurate detection may be more important than CQI.

21

In the PUCCH PC equation the additional factor h(nCQI, nHARQ) automatically accounts for PUCCH power adjustment based on number of CQI bits and HARQ ACK/NAK bits for PUCCH format 2, 2a, 2b

22

From TS 36.213 sec 5.1.2.1

19 20

23

o

(

h nCQI , n HARQ

24

25

o

)

  nCQI 10 log10  =  4 0 

  if nCQI ≥ 4   otherwise

For PUCCH format 2 and extended cyclic prefix

(

h nCQI , n HARQ

26

27

For PUCCH format 2, 2a, 2b and normal cyclic prefix

)

  nCQI + n HARQ 10 log10  = 4  0 

  if nCQI + n HARQ ≥ 4   otherwise

Setting this parameter may be based on target error rate (probability of block error) for CQI on UL.

28

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

192

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

8.2.7

Uplink Power Control Paramenter Settings

deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 2a)

Definition: Denotes the power offset applied in uplink power control relative to PUCCH format type 1a when PUCCH format type 2a (CQI+1bit ACK/NAK) is transmitted. IE Value

Engineering Units

Allowed Range

Enumerated {deltaF-2, deltaF0, deltaF2}

-2 dB, 0 dB, 2 dB

Recommended

deltaF2

2 dB

10

Setting Tradeoff: If this parameter is too large, the PUCCH Format 2a carrying CQI, 1 bit ACK/NAK may be sent at higher than required power and in some cases may cause excesive interference to other users PUCCH transmissions with different formats as well as additional interference to neighboring cells in these PUCCH RBs. If set too low, the CQI, ACK bits carried on PUCCH may be detected incorrectly which may negatively impact DL link adaptation (imperfect eNodeB scheduling decisions), cause duplicate DL transmissions/premature HARQ termination and reduce DL throughput.

11

Dependencies/Constraints:

12

Traceability: TS 36.213, Sect. 5.1.2, TS36.331, Sect 6.3.2

4 5 6 7 8 9

15

RRC Message Structure: SIB2  RadioResourceConfigCommon  RadioResourceConfigCommonSIB  UplinkPowerControl  UplinkPowerControlCommon  deltaFList-PUCCH  deltaF-PUCCH-Format2a

16

Notes: See notes for

17

set based on target CQI BLER.

13 14

18 19

∆ F_PUCCH ( F ) -format 2 related to h(nCQI, nHARQ). This parameter may be

This parameter may be set higher than the offset for PUCCH format 2 (carrying CQI only, no ACK/NAK) to ensure that ACK/NAK is always detected accurately.

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

193

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

8.2.8

Uplink Power Control Paramenter Settings

deltaF-PUCCH-Format (𝚫𝑭𝑷𝑼𝑪𝑪𝑯 (𝑭) - Format 2b)

Definition: Denotes the power offset applied in uplink power control when PUCCH format type 2b (CQI+2bit ACK/NAK) is transmitted. IE Value

Engineering Units

Allowed Range

Enumerated {deltaF-2, deltaF0, deltaF2}

-2 dB, 0 dB, 2 dB

Recommended

deltaF2

2 dB

10

Setting Tradeoff: If this parameter is too large, the PUCCH Format 2b carrying CQI, 2 bit ACK/NAK may be sent at higher than required power and in some cases may cause excesive interference to other users PUCCH transmissions with different formats as well as additional interference to neighboring cells in these PUCCH RBs. If set too low, the CQI, ACK bits carried on PUCCH may be detected incorrectly which may negatively impact DL link adaptation (imperfect eNodeB scheduling decisions), cause duplicate DL transmissions/premature HARQ termination and reduce DL throughput.

11

Dependencies/Constraints:

12

Traceability: TS 36.213, Sect. 5.1.2, TS36.331, Sect 6.3.2

4 5 6 7 8 9

15

RRC Message Structure: SIB2  RadioResourceConfigCommon  RadioResourceConfigCommonSIB  UplinkPowerControl  UplinkPowerControlCommon  deltaFList-PUCCH  deltaF-PUCCH-Format2b

16

Notes: See notes for

17

set based on target CQI BLER.

13 14

18 19

∆ F_PUCCH ( F ) -format 2 related to h(nCQI, nHARQ). This parameter may be

This parameter may be set higher than the offset for PUCCH format 2 (carrying CQI only) to ensure that ACK/NAK is always detected accurately.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

194

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

9 Handover Parameter Settings

2

Chapter 9: Table of Contents

3

9.1 Handover Measurement Trigger ......................................................................................................... 199

4

9.1.1 S-Measure ............................................................................................................................................. 199

5

9.2 Intra-EUTRA Handover ........................................................................................................................ 200

6

9.2.1 Intra-Frequency Handover ................................................................................................................ 200

7

9.2.1.1 triggerType (Measurement Report Trigger Type) ...................................................................... 200

8

9.2.1.2 purpose (Measurement Purpose) .................................................................................................. 201

9

9.2.1.3 triggerQuantity (Measurement Trigger Quantity) ...................................................................... 202

10

9.2.1.4 reportQuantity (Measurement Report Quantity) ........................................................................ 203

11

9.2.1.5 Filter Coefficient ............................................................................................................................... 204

12

9.2.1.5.1 filtercoefficientRSRP (Filter Coefficient RSRP) ......................................................................... 204

13

9.2.1.5.2 filtercoefficientRSRQ (Filter Coefficient RSRQ)........................................................................ 205

14

9.2.1.6 Event A3 ............................................................................................................................................ 206

15

9.2.1.6.1 a3-Offset (Event A3 Offset) .......................................................................................................... 208

16

9.2.1.6.2 timeToTrigger (Event A Time to Trigger) ................................................................................. 209

17

9.2.1.6.3 hysteresis (Event A3 Hysteresis) ................................................................................................ 210

18

9.2.1.6.4 reportOnLeave (Event A3 Report on Leave)............................................................................. 211

19

9.2.1.6.5 maxReportCells (Event A3 Maximum Number of Reported Cells) ...................................... 212

20

9.2.1.6.6 reportInterval (Event A3 Reporting Interval) ........................................................................... 213

21

9.2.1.6.7 reportAmount (Event A3 Number of Reports)......................................................................... 214

22

9.2.1.7 Event A5 ............................................................................................................................................ 214

23

9.2.2 Inter-Frequency Handover ................................................................................................................ 215

24

9.2.2.1 triggerType (Measurement Report Trigger Type) ...................................................................... 215

25

9.2.2.2 Purpose .............................................................................................................................................. 216

26

9.2.2.3 triggerQuantity (Measurement Trigger Quantity) ...................................................................... 217

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

195

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.2.2.4 reportQuantity (Measurement Report Quantity) ........................................................................ 218

2

9.2.2.5 Filter Coefficient ............................................................................................................................... 219

3

9.2.2.5.1 filtercoefficientRSRP (Filter Coefficient RSRP) ......................................................................... 219

4

9.2.2.5.2 filtercoefficientRSRQ (Filter Coefficient RSRQ)........................................................................ 220

5

9.2.2.6 gapOffset (Measurement Gap Configuration)............................................................................. 221

6

9.2.2.7 Event A3 ............................................................................................................................................ 222

7

9.2.2.7.1 a3-Offset (Event A3 Offset) .......................................................................................................... 222

8

9.2.2.7.2 timeToTrigger (Event A3 Time to Trigger) ............................................................................... 223

9

9.2.2.7.3 hysteresis (Event A3 Hysteresis) ................................................................................................ 224

10

9.2.2.7.4 reportOnLeave (Event A3 Report on Leave)............................................................................. 225

11

9.2.2.7.5 maxReportcells (Event A3 Maximum Number of Reported Cells) ....................................... 226

12

9.2.2.7.6 reportInterval (Event A3 Reporting Interval) ........................................................................... 227

13

9.2.2.7.7 reportAmount (Event A3 Number of Reports)......................................................................... 228

14

9.2.2.8 Event A5 ............................................................................................................................................ 228

15

9.3 Inter-RAT Handover ............................................................................................................................. 229

16

9.3.1 triggerType (Measurement Report Type)........................................................................................ 230

17

9.3.2 Purpose ................................................................................................................................................. 231

18

9.3.3 Gap Configuration .............................................................................................................................. 232

19

9.3.4 Event A2 ............................................................................................................................................... 233

20

9.3.4.1 a2-Threshold ..................................................................................................................................... 233

21

9.3.4.2 Hysteresis .......................................................................................................................................... 234

22

9.3.4.3 timeToTrigger ................................................................................................................................... 235

23

9.3.4.4 maxReportcells ................................................................................................................................. 236

24

9.3.4.5 reportInterval.................................................................................................................................... 237

25

9.3.4.6 reportAmount................................................................................................................................... 238

26

9.3.5 Handover to UTRAN ......................................................................................................................... 239

27

9.3.5.1 Event B2 ............................................................................................................................................. 239

28

9.3.5.1.1 ThresholdEUTRA (Event B2 Triggering Threshold for Serving Cell ................................... 239

29

9.3.5.1.2 triggerQuantity (Measurement Quantity for UTRAN) ........................................................... 240

30

9.3.5.1.3 ThresholdUTRA (Event B2 Triggering Threshold for UTRAN Cell...................................... 241

31

9.3.5.1.4 hysteresis (Event B2 Hysteresis) ................................................................................................. 242

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

196

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.3.5.1.5 timeToTrigger (Event B2 Time to Trigger) ................................................................................ 243

2

9.3.5.1.6 maxReportcells (Event B2 Maximum Number of Reported Cells) ........................................ 244

3

9.3.5.1.7 reportInterval (Event B2 Reporting Interval) ............................................................................ 245

4

9.3.5.1.8 reportAmount (Event B2 Number of Reports) ......................................................................... 246

5

9.3.6 Handover to GERAN ......................................................................................................................... 247

6

9.3.6.1 Event B2 ............................................................................................................................................. 247

7

9.3.6.1.1 Event B2 Triggering Threshold for Serving Cell ...................................................................... 247

8

9.3.6.1.2 Event B2 Triggering Threshold for GERAN Cell ..................................................................... 248

9

9.3.6.1.3 hysteresis (Event B2 Hysteresis) ................................................................................................. 249

10

9.3.6.1.4 timeToTrigger (Event B2 Time to Trigger) ................................................................................ 250

11

9.3.6.1.5 maxReportcells (Event B2 Maximum Number of Reported Cells) ........................................ 251

12

9.3.6.1.6 reportInterval (Event B2 Reporting Interval) ............................................................................ 252

13

9.3.6.1.7reportAmount (Event B2 Number of Reports) .......................................................................... 253

14

9.3.7Handover to CDMA2000 .................................................................................................................... 254

15

9.3.7.1Event B2 .............................................................................................................................................. 254

16

9.3.7.1.1Event B2 Triggering Threshold for Serving Cell ....................................................................... 254

17

9.3.7.1.2Event B2 Triggering Threshold for CDMA2000 Cell ................................................................ 255

18

9.3.7.1.3hysteresis (Event B2 Hysteresis) .................................................................................................. 256

19

9.3.7.1.4timeToTrigger (Event B2 Time to Trigger) ................................................................................. 257

20

9.3.7.1.5maxReportcells (Event B2 Maximum Number of Reported Cells) ......................................... 258

21

9.3.7.1.6reportInterval (Event B2 Reporting Interval) ............................................................................. 259

22

9.3.7.1.7reportAmount (Event B2 Number of Reports) .......................................................................... 260

23 24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

197

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3 4

Released - For Current Employee/Consultant Use Only

5 6

Handover Parameter Settings

In RRC_CONNECTED mode, E-UTRAN controls UE mobility and decides when the UE will move to another cell through the handover process. E-UTRAN can configure the UE to perform measurements and generate reports to support handover based on radio conditions. Such measurement reporting can be either periodic or event-triggered. E-UTRAN may also initiate blind handover without having received measurement reports from the UE, basing the decision on loading, for example.

7 8 9 10

The Information elements necessary for the configuration of measurements are signaled to the UE via the RRCConnectionReconfiguration message. Measurements are configured using the following elements:

11

12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39

1. Measurement Objects. These are the objects on which the UE shall perform the measurements. For LTE, a measurement object corresponds to a single E-UTRA carrier frequency (intra- or inter-frequency). Associated with this carrier frequency, E-UTRAN can configure a list of cell-specific offsets and a list of ‘blacklisted’ cells. Blacklisted cells are not considered in event evaluation or measurement reporting. For inter-RAT, a measurement object is defined as follows: • UTRAN: a single UTRA carrier frequency with a list of Primary Scrambling Codes (PSCs) • GERAN: a set of GERAN carrier frequencies (ARFCNs) • CDMA2000: a set of cells, defined by PN offsets and search window size, on a single (HRPD (Ev-DO) or 1xRTT) carrier frequency. As for non-IRAT neighbors, E-UTRAN can configure a list of cell-specific offsets and a list of ‘blacklisted’ cells. 2. Reporting Configuration. A reporting configuration consists of the (periodic or event-triggered) criteria which cause the UE to send a measurement report, as well as the details of what information the UE is expected to report (e.g. the quantities, such as Received Signal Code Power (RSCP) for UMTS or Reference Signal Received Power (RSRP) for LTE, and the number of cells to report measurements). 3. Measurement Identity. This is a unique identifier linking a specific measurement object with a specific reporting configuration. In this manner, a reporting configuration can be applied to multiple measurement objects. 4. Quantity Configuration. The quantity configuration defines the filtering to be used on each measurement. A single filter coefficient can be defined for each RAT. 5. Measurement Gap Configuration. Measurement gaps define time periods when no uplink or downlink transmissions will be scheduled, so that the UE may perform the measurements other than intra-frequency. These are necessary in the absence of a dual receiver when a UE needs to make measurements on a different frequency and/or RAT. The measurement gaps are common for all gap-assisted measurements.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

198

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.1 Handover Measurement Trigger

2

9.1.1

3 4

S-Measure

Definition: RSRP threshold below which, the UE make measurements for both periodic and event driven handovers. IE Value

Allowed Range Recommended

Integer (0..97)

Engineering Unit

(IE Value -140) dBm See Table 9.1.4-1 in TS 36.133

0

5

10

Setting Tradeoff: If set too high, the UE makes measurements of other cells unnecessarily when it is already connected to a cell with adequate RSRP. If set too low, the UE does not make measurements event though the RSRP of the serving cell is at a relatively weak level. The setting of this parameter is a tradeoff between faster detection of neighbor cells versus the impact to battery life. A high value of this parameter has negligible impact to data cards.

11

Dependencies/Constraints: None

12

Traceability: TS 36.331 Sect. 6.3.4

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  s-Measure

14

Notes: None

6 7 8 9

15 16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

199

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

9.2 Intra-EUTRA Handover

2

For Intra-EUTRA handover, the following event-triggered reporting criteria are specified:

3

Released - For Current Employee/Consultant Use Only

Handover Parameter Settings

4 5 6 7

• • • • •

8

Event A1: Serving cell becomes better than an absolute threshold. Event A2: Serving cell becomes worse than an absolute threshold. Event A3: Neighbor cell becomes an offset better than the serving cell. Event A4: Neighbor cell becomes better than absolute threshold. Event A5: Serving cell becomes worse than one absolute threshold and neighbor cell becomes better than another absolute threshold.

12

It is expected that Event A3 and, less commonly, Event A5 will be used to trigger handover, since they take into account UE measurements from both serving cell and neighboring cells. Other combinations of multiple events could be configured to produce the same triggering conditions as A3 and A5 but are not discussed here.

13

9.2.1

14

9.2.1.1 triggerType (Measurement Report Trigger Type)

9 10 11

15 16

Intra-Frequency Handover

Definition: This parameter defines if the UE sends measurement reports periodically or if it waits for a specific criteria (triggering of an event) to start sending measurement reports. IE Value

Engineering Unit

Allowed Range

Enumerated{event, periodical}

Event, Periodical

Recommended

event

Event

17

24

Setting Tradeoff: Periodic triggering generates a higher signaling load as measurement reports are sent continuously regardless of radio conditions. Event based measurement reports ensures that signaling is limited to specific, network defined RF conditions. Although there are some scenarios where the network would benefit form continuously updated measurement reports (e.g. SON), event driven is recommended for a typical deployment to limit signaling load. Additionally, periodic reporting of a triggered event is supported whereby the UE will send additional reports (with a configurable number and frequency) whilst the triggering conditions are maintained.

25

Dependencies/Constraints: None

26

Traceability: TS 36.331 Sect. 6.3.5

18 19 20 21 22 23

29

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  triggerType

30

Notes: None

27 28

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

200

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.2 purpose (Measurement Purpose) Definition: This parameter defines the purpose of the periodical reporting, specifying if the UE reports the physical cell ID of the neighbor cells or attempts to identify the Cell Global ID. IE Value

Engineering Unit

Allowed Range

Enumerated {reportStrongestCells, reportCGI}

reportStrongestCells, reportCGI

Recommended

N/A

N/A

4

Setting Tradeoff: The setting of this parameter depends of the purpose of the measurement.

5

Dependencies/Constraints:

6

Traceability: TS 36.331 Sect. 6.3.5

7 8 9 10

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  periodical  purpose Notes: None

11

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

201

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.2.1.3 triggerQuantity (Measurement Trigger Quantity) Definition: The parameter defines the metric used for measurement report triggering evaluation. The options are Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ). IE Value

5 6 7 8 9

Allowed Range

Enum {RSRP, RSRQ}

RSRP, RSRQ

Recommended

RSRP

RSRP

Setting Tradeoff: If RSRP is used as the trigger quantity then the impact of loading will not be considered in handover decisions, whereas if RSRQ is utilized, the impact of loading will be considered in handover decisions. With RSRP, handovers will be triggered in the same location regardless of load whereas with RSRQ, the handover locations will move depending on the loading of each of the surrounding cells.

10

Dependencies/Constraints: None

11

Traceability: TS 36.331 Sect. 6.3.5

12 13 14 15 16 17 18 19 20 21 22 23

Engineering Unit

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  triggerQuantity Notes: RSRP based triggering condition is based on cell-specific signal strength metric. It considers the average received power over the resource elements that carry cell-specific reference signals within certain frequency bandwidth. RSRQ based triggering condition is based on a cell-specific signal quality metric. It is defined as (N*RSRP)/(E-UTRA Carrier RSSI), where N makes sure the nominator and denominator are measured over the same frequency bandwidth; the carrier RSSI measures the average total received power observed only in OFDM symbols containing reference symbols for antenna port 0 (i.e., OFDM symbol 0 & 4 in a slot) in the measurement bandwidth over N resource blocks. The total received power of the carrier RSSI includes the power from co-channel serving & non-serving cells, adjacent channel interference, thermal noise, etc.

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

202

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.4 reportQuantity (Measurement Report Quantity) Definition: Measurement quantities to be included in the measurement report. The value "both" means that both the RSRP and RSRQ quantities are to be included in the measurement report. IE Value

Engineering Unit

Allowed Range

Enum {sameAsTriggerQuantity, both}

Same As the Trigger Quantity, Both

Recommended

sameAsTriggerQuantity

Same As the Trigger Quantity

4

8

Setting Tradeoff: A measurement report always contains both the RSRP and RSRQ of the serving cell. Setting this parameter to both means that RSRP and RSRQ of all reported cells are included in the report. Otherwise, only the same quantity which triggered the report is included reducing marginally the size of the measurement report.

9

Dependencies/Constraints: None

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportQuantity

14

Notes: None

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

203

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.2.1.5 Filter Coefficient

2

Layer 3 measurements (RSRP and RSRQ) are filtered before reporting by the UE following:

Released - For Current Employee/Consultant Use Only

3

Fn = (1-a) Fn-1 + aMn

4

7

where Mn is the latest received measurement result from the physical layer, Fn is the updated filtered measurement result and Fn-1 is the old filtered measurement result. For the first measurement result from the physical layer F0 is set to M1.

8

Additionally,

5 6

a = 1/2(k/4)

9 10

where k is the filter Coefficient for the corresponding measurement quantity.

11

9.2.1.5.1 filtercoefficientRSRP (Filter Coefficient RSRP)

12

Definition: Filtering coefficient used for RSRP measurements IE Value

Allowed Range

Recommended

Engineering Unit

Enum{ fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15,fc17, fc19}

k= 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19

fc8-11

k=8-11

15

Setting Tradeoff: If this value is set too low, measurement reports could be triggered by rapid, temporary, short term fluctuations in RSRP. If this is set too large, then the generation of measurements reports will be delayed even though a more suitable cell is available.

16

Dependencies/Constraints:

17

Traceability: TS 36.331 Sect. 5..5.3.2, 6.3.5

13 14

18 19 20 21

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  QuantityConfig  QuantityConfigEUTRA  filtercoefficientRSRP Notes: If this parameter is not configured (absent) then the default RRC value (fc4) is used by the eNB and signaled to the UE. A value of k=0 corresponds to no filtering.

22 23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

204

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.2.1.5.2 filtercoefficientRSRQ (Filter Coefficient RSRQ)

2

Definition: Filtering coefficient used for RSRQ

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Unit

Allowed Range

Enum{ fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15,fc17, fc19}

k= 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19

Recommended

fc8-11

k=8-11

5

Setting Tradeoff: If this value is set too low, measurement reports could be triggered by rapid, temporary, short term fluctuations in RSRQ. If this is set too large, then the generation of measurements reports will be delayed even though a more suitable cell is available.

6

Dependencies/Constraints:

7

Traceability: TS 36.331 Sect. 6.3.5

3 4

8 9 10 11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  QuantityConfig  QuantityConfigEUTRA  filtercoefficientRSRQ Notes: If this parameter is not configured (absent) then the default RRC value (fc4) is used by the eNB and signalled to the UE.

12

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

205

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.2.1.6 Event A3

2

UE enters the Event A3 Triggering condition when the following condition is met:

3

Inequality A3-1 (Entering condition)

4

Mn + Ofn + Ocn − Hys > Ms + Ofs + Ocs + Off

5

UE leaves the Event A3 triggering condition when the following condition is met:

6

Inequality A3-2 (Leaving condition)

7

Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off

8

The variables in the formula are defined as follows:

9

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

10 11

Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).

14

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

15

Ms is the measurement result of the serving cell, not taking into account any offsets.

12 13

16 17 18 19 20 21 22

Ofs is the frequency specific offset of the serving frequency (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the serving frequency). Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the serving frequency), and is set to zero if not configured for the serving cell. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

24

Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA for this event).

25

Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.

26

Ofn, Ocn, Ofs, Ocs, Hys, Off are expressed in dB.

23

27

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

206

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Handover Parameter Settings

M

Number of reports

Hyst

Offset

Released - For Current Employee/Consultant Use Only

Cell 1

S-measure Event A3

Reporting interval

Time to Trigger

Cell 2

1

2

3

1

Time

2

3

Figure 9-1 Event A3 entering and leaving conditions (assuming Ofn, Ocn, Ofs, Ocs = 0).

4

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

207

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.6.1 a3-Offset (Event A3 Offset) Definition: This offset is used in the formulas that specify the entering and leaving conditions for event A3 (5.1.1.6). IE Value

4 5 6 7 8 9 10

Engineering Unit

Allowed Range

Integer [-30..30]

IE value * 0.5 dB

Recommended

6 or adjust by deployment needs

3 dB or adjust by deployment needs

Setting Tradeoff: The smallest the offset, the sooner the UE will trigger an event A3, possibly while the source cell is still acceptable. On the other hand, a large offset will delay the triggering of event A3, affecting the performance of the connection on the source cell while the target cell is a better candidate. Dependencies/Constraints: This parameter should be jointly optimized with hysteresis per deployment needs. Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  eventA3  a3-Offset

14

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

208

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.6.2 timeToTrigger (Event A Time to Trigger) Definition: Time during which the measurement report triggering condition for an event must be met in order to trigger an event A3. IE Value

Engineering Unit

UNIT: ms

Allowed Range

Enum{ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120}

Recommended

ms128

128ms

RANGE: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560, 5120

6

Setting Tradeoff: Rapid, temporary, short term fluctuations can initiate an event A3 if the parameter Time to Trigger is too small. On the contrary, a too large setting will delay the event triggering, possibly causing service degradation on the source cell.

7

Dependencies/Constraints:

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  timeToTrigger

12

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

209

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.6.3 hysteresis (Event A3 Hysteresis) Definition: This hysteresis is used in the formulas that specify the entering and leaving conditions for event A3 (5.1.1.6). IE Value

Engineering Unit

Allowed Range

Integer (0..30)

IE value * 0.5 dB

Recommended

4

2 dB

7

Setting Tradeoff: The smallest the hysteresis, the sooner the UE will trigger an event A3, possibly while the source cell is still acceptable. On the other hand, a large hysteresis will delay the triggering of event A3, affecting the performance of the connection on the source cell while the target cell is a better candidate.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  hysteresis

13

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

210

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.6.4 reportOnLeave (Event A3 Report on Leave) Definition: This parameter indicates if the UE should report measurements for a cell in cellsTriggeredList when that cell meets the criteria to leave event A3. IE Value

Engineering Unit

Allowed Range

Boolean{True, Flase}

True, False

Recommended

FALSE

FALSE

6

Setting Tradeoff: If this parameter is set to True, the UE will continue reporting measurements for a cell that meets the event A3 leaving criteria (a cell that is not suitable for handover). If it is set to False, the UE will not report measurements for a cell that meets the event A3 leaving criteria.

7

Dependencies/Constraints:

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  eventA3  reportOnLeave

12

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

211

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.6.5 maxReportCells (Event A3 Maximum Number of Reported Cells) Definition: Maximum number of cells, excluding the serving cell, that can be included in a measurement report. IE Value

Engineering Unit

Allowed Range

Integer [1..8]

1, 2, .., 8

Recommended

4-6

4-6

7

Setting Tradeoff: If the parameter is too low, only few neighbor cells are reported, saving UE processing, while not providing the eNodeB with many options in case a handover to a target cell fails (due to lack of resources for example). If it is too high, more cells are reported, requiring higher UE processing while giving the eNodeB more choices of target cells.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  maxReportcells

13

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

212

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.2.1.6.6 reportInterval (Event A3 Reporting Interval) Definition: This parameter indicates the interval between measurement reports sent by the UE. It is applicable for trigger type ‘event’ or ‘periodical’, when the parameter ‘reportAmount’ (5.1.1.6.7) is greater than 1. IE Value

Allowed Range

Recommended

Engineering Unit

Enum{ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60 }

120, 240, 480, 640, 1024, 2048, 5120 , 10240 ms

ms480

480 ms

1, 6, 12, 30, 60 min

8

Setting Tradeoff: If this parameter is set too low, the UE will transmit an unnecessarily large number of measurement reports, consuming processing power in the E-UTRAN. On the other hand, if it is too large, the reporting will not be updated frequently enough as to accurately reflect the UE´s environment.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportInterval

14

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

213

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.1.6.7 reportAmount (Event A3 Number of Reports) Definition: Number of times a measurement report is sent. It is applicable for TriggerType ‘event’ as well as for TriggerType ‘periodical’. In case purpose is set to ‘reportCGI’ only value 1 applies. IE Value

Engineering Unit

Allowed Range

{r1, r2, r4, r8, r16, r32, r64, infinity}

1, 2, 4, 8, 16, 32, 64, infinity

Recommended

infinity

infinity

7

Setting Tradeoff: If the parameter is set too low, the UE will prematurely stop sending measurement reports which could potentially delay a handover in case the previous messages are not received by the eNodeB. If it is too high, the UE may be sending an unnecessarily large number of measurement reports to the eNodeB, wasting EUTRAN resources.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportAmount

13

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

10 11

14

15

9.2.1.7 Event A5

16

TBD.

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

214

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

9.2.2

2

9.2.2.1 triggerType (Measurement Report Trigger Type)

3

Released - For Current Employee/Consultant Use Only

Handover Parameter Settings

4

Inter-Frequency Handover

Definition: This parameter defines if the UE sends measurement reports periodically or if it waits for a specific criteria (triggering of an event) to start sending measurement reports. IE Value

Engineering Unit

Allowed Range

Enumerated{event, periodical}

Event, Periodical

Recommended

event

Event

5

11

Setting Tradeoff: Periodic triggering generates a higher signaling as measurement reports are sent continuously regardless of radio conditions. Event based measurement reports ensures that signaling is limited to specific, network defined RF conditions. Although there are some scenarios where the network would benefit form continuously updated measurement reports (e.g. SON), event driven is recommended for a typical deployment to limit signaling load.

12

Dependencies/Constraints: None

13

Traceability: TS 36.331 Sect. 6.3.5

6 7 8 9 10

16

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  triggerType

17

Notes: None

14 15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

215

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.2.2 Purpose Definition: This parameter defines the purpose of the periodical reporting, specifying if the UE reports the physical cell ID of the neighbor cells or attempts to identify the Cell Global ID. IE Value

Engineering Unit

Allowed Range

Enumerated {reportStrongestCells, reportCGI}

reportStrongestCells, reportCGI

Recommended

NA

NA

4

Setting Tradeoff: The setting of this parameter depends of the purpose of the measurement.

5

Dependencies/Constraints:

6

Traceability: TS 36.331 Sect. 6.3.5

7 8 9 10

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  periodical  purpose Notes: None

11

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

216

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.2.2.3 triggerQuantity (Measurement Trigger Quantity) Definition: The parameter defines the metric used for measurement report triggering evaluation. The options are Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ). IE Value

5 6 7 8 9

Allowed Range

Enum {RSRP, RSRQ}

RSRP, RSRQ

Recommended

RSRP

RSRP

Setting Tradeoff: If RSRP is used as the trigger quantity then the impact of loading will not be considered in handover decisions, whereas if RSRQ is utilized, the impact of loading will be considered in handover decisions. With RSRP, handovers will be triggered in the same location regardless of load whereas with RSRQ, the handover locations will move depending on the loading of each of the surrounding cells.

10

Dependencies/Constraints: None

11

Traceability: TS 36.331 Sect. 6.3.5

12 13 14 15 16 17 18 19 20 21 22 23

Engineering Unit

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  triggerQuantity Notes: RSRP based triggering condition is based on cell-specific signal strength metric. It considers the average received power over the resource elements that carry cell-specific reference signals within certain frequency bandwidth. RSRQ based triggering condition is based on a cell-specific signal quality metric. It is defined as (N*RSRP)/(E-UTRA Carrier RSSI), where N makes sure the nominator and denominator are measured over the same frequency bandwidth; the carrier RSSI measures the average total received power observed only in OFDM symbols containing reference symbols for antenna port 0 (i.e., OFDM symbol 0 & 4 in a slot) in the measurement bandwidth over N resource blocks. The total received power of the carrier RSSI includes the power from co-channel serving & non-serving cells, adjacent channel interference, thermal noise, etc.

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

217

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.2.4 reportQuantity (Measurement Report Quantity) Definition: Measurement quantities to be included in the measurement report. The value "both" means that both the RSRP and RSRQ quantities are to be included in the measurement report. IE Value

Engineering Unit

Allowed Range

Enum {sameAsTriggerQuantity, both}

Same As the Trigger Quantity, Both

Recommended

sameAsTriggerQuantity

Same As the Trigger Quantity

4

8

Setting Tradeoff: A measurement report always contains both the RSRP and RSRQ of the serving cell. Setting this parameter to both means that RSRP and RSRQ of all reported cells are included in the report. Otherwise, only the same quantity which triggered the report is included reducing marginally the size of the measurement report.

9

Dependencies/Constraints: None

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportQuantity

14

Notes: None

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

218

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.2.2.5 Filter Coefficient

2

Layer 3 measurements (RSRP and RSRQ) are filtered before reporting by the UE following:

Released - For Current Employee/Consultant Use Only

3

Fn = (1-a) Fn-1 + aMn

4

7

where Mn is the latest received measurement result from the physical layer, Fn is the updated filtered measurement result and Fn-1 is the old filtered measurement result. For the first measurement result from the physical layer F0 is set to M1.

8

Additionally,

5 6

a = 1/2(k/4)

9 10

where k is the filter Coefficient for the corresponding measurement quantity.

11

12

9.2.2.5.1 filtercoefficientRSRP (Filter Coefficient RSRP)

13

Definition: Filtering coefficient used for RSRP measurements IE Value

Engineering Unit

Allowed Range

Enum{ fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15,fc17, fc19}

k= 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19

Recommended

fc8-11

k=8-11

16

Setting Tradeoff: If this value is set too low, measurement reports could be triggered by rapid, temporary, short term fluctuations in RSRP. If this is set too large, then the generation of measurements reports will be delayed even though a more suitable cell is available.

17

Dependencies/Constraints:

18

Traceability: TS 36.331 Sect. 6.3.5

14 15

19 20 21 22

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  QuantityConfig  QuantityConfigEUTRA  filtercoefficientRSRP Notes: If this parameter is not configured (absent) then the default RRC value (fc4) is used by the eNB and signaled to the UE. A value of k=0 corresponds to no filtering.

23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

219

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.2.2.5.2 filtercoefficientRSRQ (Filter Coefficient RSRQ)

2

Definition: Filtering coefficient used for RSRQ

Released - For Current Employee/Consultant Use Only

IE Value

Engineering Unit

Allowed Range

Enum{ fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15,fc17, fc19}

k= 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19

Recommended

fc8-11

k=8-11

5

Setting Tradeoff: If this value is set too low, measurement reports could be triggered by rapid, temporary, short term fluctuations in RSRQ. If this is set too large, then the generation of measurements reports will be delayed even though a more suitable cell is available.

6

Dependencies/Constraints:

7

Traceability: TS 36.331 Sect. 6.3.5

3 4

8 9 10 11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  QuantityConfig  QuantityConfigEUTRA  filtercoefficientRSRQ Notes: If this parameter is not configured (absent) then the default RRC value (fc4) is used by the eNB and signalled to the UE.

12

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

220

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.2.2.6 gapOffset (Measurement Gap Configuration) Definition: This parameter defines the gap configuration used for inter-frequency measurements, as the UE cannot measure another frequency while its transceiver is switched on. Each gap starts at an SFN and subframe meeting the following condition:

5

SFN mod T = FLOOR(gapOffset/10);

6

subframe = gapOffset mod 10;

7 8

with T = MGRP/10 (MGRP can take two values, 40ms and 80ms, for the two possible Measurement Gap Repetition Periods). IE Value

Allowed Range

Recommended

Integer (0..39) for gp0

Engineering Unit

Same as IE value

Integer (0..79) for gp1 gp0 with dynamic offset if MeasGapConfig is setup

gp0

9

12

Setting Tradeoff: A smaller MGRP will create more frequent gaps so the inter-frequency (or interRAT) measurements will be collected quicker, while the service in the EUTRAN will be interrupted more frequently as well.

13

Dependencies/Constraints: None

14

Traceability: TS 36.331 Sect. 6.3.5

10 11

16

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  MeasGapConfig  setup  gapOffset  gp0 or gp1

17

Notes: None

15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

221

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

9.2.2.7 Event A3

2

9.2.2.7.1 a3-Offset (Event A3 Offset)

3

Released - For Current Employee/Consultant Use Only

Handover Parameter Settings

4

Definition: This offset is used in the formulas that specify the entering and leaving conditions for event A3 (5.1.1.6). IE Value

Allowed Range Recommended

Engineering Unit

Integer [-30..30]

IE value * 0.5 dB

6 or adjust by deployment needs

3 dB or adjust by deployment needs

8

Setting Tradeoff: The smallest the offset, the sooner the UE will trigger an event A3, possibly while the source cell is still acceptable. On the other hand, a large offset will delay the triggering of event A3, affecting the performance of the connection on the source cell while the target cell is a better candidate.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  eventA3  a3-Offset

14

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

222

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.2.7.2 timeToTrigger (Event A3 Time to Trigger) Definition: Time during which the measurement report triggering condition for an event must be met in order to trigger an event A3. IE Value

Engineering Unit

UNIT: ms

Allowed Range

Enum{ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120}

Recommended

ms256

256 ms

Range: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560, 5120

6

Setting Tradeoff: Rapid, temporary, short term fluctuations can initiate an event A3 if the parameter Time to Trigger is too small. On the contrary, a too large setting will delay the event triggering, possibly causing service degradation on the source cell.

7

Dependencies/Constraints:

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  timeToTrigger

12

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

223

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.2.7.3 hysteresis (Event A3 Hysteresis) Definition: This hysteresis is used in the formulas that specify the entering and leaving conditions for event A3 (5.1.1.6). IE Value

Engineering Unit

Allowed Range

Integer (0..30)

IE value * 0.5 dB

Recommended

4

2 dB

7

Setting Tradeoff: The smallest the hysteresis, the sooner the UE will trigger an event A3, possibly while the source cell is still acceptable. On the other hand, a large hysteresis will delay the triggering of event A3, affecting the performance of the connection on the source cell while the target cell is a better candidate.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  hysteresis

13

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

224

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.2.7.4 reportOnLeave (Event A3 Report on Leave) Definition: This parameter indicates if the UE should report measurements for a cell in cellsTriggeredList when that cell meets the criteria to leave event A3. IE Value

Engineering Unit

Allowed Range

Boolean{True, Flase}

True, False

Recommended

FALSE

FALSE

6

Setting Tradeoff: If this parameter is set to True, the UE will continue reporting measurements for a cell that meets the event A3 leaving criteria (a cell that is not suitable for handover). If it is set to False, the UE will not report measurements for a cells that meets the event A3 leaving criteria.

7

Dependencies/Constraints:

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  eventA3  reportOnLeave

12

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

225

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.2.7.5 maxReportcells (Event A3 Maximum Number of Reported Cells) Definition: Maximum number of cells, excluding the serving cell, that can be included in a measurement report. IE Value

Engineering Unit

Allowed Range

Integer [1..8]

1, 2, .., 8

Recommended

4-6

4-6

7

Setting Tradeoff: If the parameter is too low, only few neighbor cells are reported, saving UE processing, while not providing the eNodeB with many options in case a handover to a target cell fails (due to lack of resources for example). If it is too high, more cells are reported, requiring higher UE processing while giving the eNodeB more choices of target cells.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  maxReportcells

13

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

226

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.2.2.7.6 reportInterval (Event A3 Reporting Interval) Definition: This parameter indicates the interval between measurement reports sent by the UE. It is applicable for trigger type ‘event’ or ‘periodical’, when the parameter ‘reportAmount’ (5.1.2.7.7) is greater than 1. IE Value

Allowed Range

Recommended

Engineering Unit

Enum{ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60, }

120, 240, 480, 640, 1024, 2048, 5120 , 10240 ms

ms480

480 ms

1, 6, 12, 30, 60 min

8

Setting Tradeoff: If this parameter is set too low, the UE will transmit an unnecessarily large number of measurement reports, consuming processing power in the E-UTRAN. On the other hand, if it is too large, the reporting will not be updated frequently enough as to accurately reflect the UE´s environment.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportInterval

14

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

227

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.2.2.7.7 reportAmount (Event A3 Number of Reports) Definition: Number of times a measurement report is sent. It is applicable for TriggerType ‘event’ as well as for TriggerType ‘periodical’. In case purpose is set to ‘reportCGI’ only value 1 applies. IE Value

Engineering Unit

Allowed Range

{r1, r2, r4, r8, r16, r32, r64, infinity}

1, 2, 4, 8, 16, 32, 64, infinity

Recommended

infinity

infinity

7

Setting Tradeoff: If the parameter is set too low, the UE will prematurely stop sending measurement reports which could potentially delay a handover in case the previous messages are not received by the eNodeB. If it is too high, the UE may be sending an unnecessarily large number of measurement reports to the eNodeB, wasting EUTRAN resources.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportAmount

13

Notes: this parameter applies to all intra and inter-frequency EUTRAN handovers.

10 11

14

15

9.2.2.8 Event A5

16

TBD

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

228

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9

Handover Parameter Settings

9.3 Inter-RAT Handover It is possible to perform IRAT handovers from E-UTRAN to GERAN, UTRAN and CDMA2000 Neighbor cells. When the UE is in RRC_CONNECTED state, EUTRAN provides measurement configuration information by using dedicated signalling i.e RRCConnectionReconfiguration Message. UE reports IRAT measurement information in accordance with the measurement configuration provided by the E-UTRAN. UE sends measurement reports either periodically or triggered by events. Event B2 is used for IRAT handover measurement report triggering from E-UTRAN to GERAN, UTRAN and CDMA2000. UE enters the Event B2 Triggering condition when both the following conditions 1 and 2 are met.

10

Inequality B2-1 (Entering condition 1)

11

Ms + Hys < Thresh1

12

Inequality B2-2 (Entering condition 2)

13

Mn + Ofn − Hys > Thresh 2

14

UE leaves the Event B2 triggering condition when either condition 3 or 4 are met.

15

Inequality B2-3 (Leaving condition 1)

16

Ms − Hys > Thresh1

17

Inequality B2-4 (Leaving condition 2)

18

Mn + Ofn + Hys < Thresh 2

19

Ms is the measurement result of the E-UTRAN serving cell, not taking into account any offsets.

20

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.

21

Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell .

22

Hys is the hysteresis parameter for this event

23 24 25 26

Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRAT for this event). Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2 as defined within reportConfigInterRAT for this event).

27

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

229

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

9.3.1

Handover Parameter Settings

triggerType (Measurement Report Type)

Definition: This parameter defines if the UE sends measurement reports periodically or if it waits for a specific criteria (triggering of an event) to start sending measurement reports. IE Value

Engineering Unit

Allowed Range

Enumerated{event, periodical}

Event, Periodical

Recommended

event

Event

4

10

Setting Tradeoff: Periodic triggering generates a higher signaling as measurement reports are sent continuously regardless of radio conditions. Event based measurement reports ensures that signaling is limited to specific, network defined RF conditions. Although there are some scenarios where the network would benefit form continuously updated measurement reports (e.g. SON), event driven is recommended for a typical deployment to limit signaling load.

11

Dependencies/Constraints: None

12

Traceability: TS 36.331 Sect. 6.3.5

5 6 7 8 9

15

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  triggerType

16

Notes: None

13 14

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

230

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

9.3.2

Handover Parameter Settings

Purpose

Definition: This parameter defines the purpose of the periodical reporting, specifying if the UE reports the physical cell ID of the neighbor cells or attempts to identify the Cell Global ID. IE Value

Engineering Unit

Allowed Range

Enumerated {reportStrongestCells, reportCGI}

reportStrongestCells, reportCGI

Recommended

NA

NA

4

Setting Tradeoff: The setting of this parameter depends of the purpose of the measurement.

5

Dependencies/Constraints:

6

Traceability: TS 36.331 Sect. 6.3.5

7 8 9 10

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  periodical  purpose Notes: None

11

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

231

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

9.3.3

Handover Parameter Settings

Gap Configuration

Definition: This parameter defines the gap configuration used for inter-frequency measurements, as the UE can not measure another frequency while its transceiver is switched on. Each gap starts at an SFN and subframe meeting the following condition:

5

SFN mod T = FLOOR(gapOffset/10);

6

subframe = gapOffset mod 10;

7 8

with T = MGRP/10 (MGRP can take two values, 40ms and 80ms, for the two possible Measurement Gap Repetition Periods). IE Value

Allowed Range

Recommended

Integer (0..39) for gp0

Engineering Unit

Same as IE value

Integer (0..79) for gp1 gp0 with dynamic offset if MeasGapConfig is setup

gp0 with dynamic offset if MeasGapConfig is setup

9

12

Setting Tradeoff: A smaller MGRP will create more frequent gaps so the inter-frequence (or interRAT) measurements will be collected quicker, while the service in the EUTRAN will be interrupted more frequently as well.

13

Dependencies/Constraints: None

14

Traceability: TS 36.331 Sect. 6.3.5

10 11

16

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  MeasGapConfig  setup  gapOffset  gp0 or gp1

17

Notes: None

15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

232

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

9.3.4

2

9.3.4.1 a2-Threshold

Released - For Current Employee/Consultant Use Only

3 4 5

Handover Parameter Settings

Event A2

Definition: This is the threshold used by the Serving E-UTRAN Cell (LTE Cell) in order to evaluate the event A2. This threshold is a choice of RSRP or RSRQ and it uses a table mapping reference given in 36.133 sections 9.1.4 or 9.1.7, for RSRP and RSRQ respectively.

6

IE Value

Allowed Range Recommended 7 8 9

Engineering Units

RSRP Integer [0..97]

RSRP

(IE value – 140dBm)

RSRQ

RSRQ

(IE value – 40)/2

Integer [0..34]

27 (RSRP)

-113 dBm

Setting Tradeoff: If the parameter is set too low (meaning low dBm or dB), it will delay the event triggering, possibly with service degradation in the EUTRA cell. If the parameter is set too high, the event will be triggered too early while the quality of the EUTRA cell is still acceptable.

10

Dependencies/Constraints: NA.

11

Traceability: TS 33.331 Sect. 6.3.5

12

RRC Message Structure:

15

RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  eventA2  a2-Threshold  ThresholdEUTRA  threshold-RSRP

16

Notes:

13 14

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

233

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Handover Parameter Settings

9.3.4.2 Hysteresis Definition: This hysteresis is used in the formulas that specify the entering and leaving conditions for event A2.

Released - For Current Employee/Consultant Use Only

4

IE Value

Engineering Units

Allowed Range

Integer (0..30)

IE value * 0.5 dB

Recommended

4

2 dB

8

Setting Tradeoff: The smallest the hysteresis, the sooner the UE will trigger an event A2, possibly while the source cell is still acceptable. On the other hand, a large hysteresis will delay the triggering of event A2, affecting the performance of the connection on the source cell while the target cell is a better candidate.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 33.331 Sect. 6.3.5

11

RRC Message Structure:

13

RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  hysteresis

14

Notes:

12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

234

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Handover Parameter Settings

9.3.4.3 timeToTrigger Definition: Time during which the measurement report triggering condition for an event must be met in order to trigger an event A2.

Released - For Current Employee/Consultant Use Only

4

IE Value

Engineering Units

UNIT: ms

Allowed Range

Enum{ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120}

Recommended

ms480

480 ms

RANGE: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560, 5120

7

Setting Tradeoff: Rapid, temporary, short term fluctuations can initiate an event A2 if the parameter Time to Trigger is too small. On the contrary, a too large setting will delay the event triggering, possibly causing service degradation on the source cell..

8

Dependencies/Constraints:

9

Traceability: TS 33.331 Sect. 6.3.5

5 6

10

RRC Message Structure:

13

RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  event  timeToTrigger

14

Notes:

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

235

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.4.4 maxReportcells Definition: Maximum number of cells, excluding the serving cell, that can be included in a measurement report. IE Value

Engineering Unit

Allowed Range

Integer [1..8]

1, 2, .., 8

Recommended

4-6

4-6

7

Setting Tradeoff: If the parameter is too low, only few neighbor cells are reported, saving UE processing. The drawback is that the eNodeB won´t have many options in case a handover to a target cell fails, due to lack of resources for example. If it is too high, more cells are reported, requiring higher UE processing while giving the eNodeB more choices of target cells.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  maxReportcells

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

236

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.3.4.5 reportInterval Definition: This parameter indicates the interval between measurement reports sent by the UE. It is applicable for trigger type ‘event’ or ‘periodical’, when the parameter ‘reportAmount’ is greater than 1. IE Value

Allowed Range

Recommended

Engineering Unit

Enum{ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60, spare3, spare2, spare1}

120, 240, 480, 640, 1024, 2048, 5120 , 10240 ms

ms480

480ms

1, 6, 12, 30, 60 min

7

Setting Tradeoff: If the parameter is too low, the UE will transmit an unnecessarily large number of measurement reports, consuming processing power in the E-UTRAN. If the parameter is too high, the reporting might not be quick enough to accurately reflect the UE´s environment.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportInterval

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

237

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.4.6 reportAmount Definition: Number of times a measurement report is sent. It is applicable for TriggerType ‘event’ as well as for TriggerType ‘periodical’. In case purpose is set to ‘reportCGI’ only value 1 applies. IE Value

Engineering Unit

Allowed Range

{r1, r2, r4, r8, r16, r32, r64, infinity}

1, 2, 4, 8, 16, 32, 64, infinity

Recommended

Infinity

infinity

7

Setting Tradeoff: If the parameter is set too low, the UE will prematurely stop sending measurement reports which could potentially delay a handover in case the previous messages are not received by the eNodeB. If it is too high, the UE may be sending an unnecessarily large number of measurement reports to the eNodeB, wasting EUTRAN resources.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigEUTRA  reportAmount

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

238

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.3.5

2

9.3.5.1 Event B2

3

9.3.5.1.1 ThresholdEUTRA (Event B2 Triggering Threshold for Serving Cell)

4 5 6

Handover to UTRAN

Definition: This is the threshold used by the Serving E-UTRAN Cell (LTE Cell) in order to evaluate the event B2. This threshold is a choice of RSRP or RSRQ and it uses a table mapping reference given in 36.133 sections 9.1.4 or 9.1.7, for RSRP and RSRQ respectively.

7

IE Value

Allowed Range Recommended 8 9 10

Engineering Units

RSRP Integer [0..97]

RSRP

(IE value – 140dBm)

RSRQ

RSRQ

(IE value – 40)/2

Integer [0..34]

RSRP 27

RSRP -113 dBm

Setting Tradeoff: If the parameter is set too low (meaning low dBm or dB), it will delay the event triggering, possibly with service degradation in the EUTRA cell. If the parameter is set too high, the event will be triggered too early while the quality of the EUTRA cell is still acceptable.

12

Dependencies/Constraints: B2-Threshold1 of E-UTRAN serving cell should be set in conjunction with B2-Threshold2 of the Inter-RAT cell.

13

Traceability: TS 33.331 Sect. 6.3.5

14

RRC Message Structure:

11

16

RRC Connection Reconfiguration  MeasConfig  ReportConfigtoaddmod  ReportConfig  ReportConfigInterRAT  B2-Threshold1  ThresholdEUTRA

17

Notes:

15

18 19 20

An appropriate setting of RSRP for event B2 triggering threshold should be set in such a way that the throughput degradation between LTE and HSPA after IRAT completes is not significant. The LTE deployment bandwidth also has impact on the decision of how aggressive the threshold would be.

21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

239

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.5.1.2 triggerQuantity (Measurement Quantity for UTRAN) Definition: The parameter defines the metric used for measurement report triggering for the target UTRAN cell. IE Value

Allowed Range

Recommended

Engineering Unit

FDD Enum{cpich-RSCP, cpichEcN0}

cpich-RSCP or cpich-EcN0 for UTRAFDD

TDD Enum {pccpch-RSCP}

pccpch-RSCP for UTRA-TDD

cpich-RSCP for FDD

cpich-RSCP for FDD

6

Setting Tradeoff: If the parameter is set to RSCP, the UE will consider signal strength measurements for event triggering. The quality metric EcN0, however, is a better indicator of the expected performance and load in the target UTRA cell.

7

Dependencies/Constraints: None

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  triggerQuantity

12

Notes: None

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

240

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.5.1.3 ThresholdUTRA (Event B2 Triggering Threshold for UTRAN Cell) Definition: This is the threshold used by the Target UTRAN Cell (UMTS Cell) in order to evaluate the event B2. This threshold is a choice of RSCP or EcN0.

4

IE Value

Allowed Range Recommended 5 6 7 8 9 10

Engineering Units

utra-RSCP

integer[-5..91]

RSCP (-116 + IE value)

utra-EcN0

integer[0..49]

EcN0 (IE value – 49)/2

utra-RSCP 16

utra-RSCP -100 dBm

Setting Tradeoff: If the parameter is set too low, the UTRA cell might be considered for a handover while the signal or quality is still not acceptable. If the parameter is set too high, it will delay the event triggering which can cause service degradation in the EUTRA cell. Dependencies/Constraints: B2-Threshold1 of E-UTRAN serving cell should be set in conjunction with B2-Threshold2 of the Inter-RAT cell. Traceability: TS 33.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigtoaddmod  ReportConfig  ReportConfigInterRAT  b2-Threshold2  b2Threshold2UTRA  ThresholdUTRA

14

Notes:

15

Table mapping reference given in 25.133 sections 9.1.1.3 or 9.1.7, for RSCP and EcN0 respectively.

11 12

16 17

An appropriate setting of RSCP for event B2 triggering threshold should be set in such a way that the throughput degradation between LTE and HSPA after IRAT completes is not significant.

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

241

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.5.1.4 hysteresis (Event B2 Hysteresis) Definition: This hysteresis is used in the formulas that specify the entering and leaving conditions for event B2 (5.2). IE Value

Engineering Unit

Allowed Range

Integer (0..30)

IE value * 0.5 dB

Recommended

6

3 dB

7

Setting Tradeoff: The smallest the hysteresis, the sooner the UE will trigger an event B2, possibly while the source cell is still acceptable. On the other hand, a large hysteresis will delay the triggering of event B2, affecting the performance of the connection on the source cell while the target cell is a better candidate.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  event  hysteresis

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

242

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.5.1.5 timeToTrigger (Event B2 Time to Trigger) Definition: Time during which the measurement report triggering condition for an event must be met in order to trigger an event B2. IE Value

Engineering Unit

UNIT: ms

Allowed Range

Enum{ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120}

Recommended

ms480

480 ms

RANGE: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560, 5120

6

Setting Tradeoff: Rapid, temporary, short term fluctuations can initiate an event B2 if the parameter Time to Trigger is too small. On the contrary, a too large setting will delay the event triggering, possibly causing service degradation on the source cell.

7

Dependencies/Constraints:

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  event  timeToTrigger

12

Notes:

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

243

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.5.1.6 maxReportcells (Event B2 Maximum Number of Reported Cells) Definition: Maximum number of cells, excluding the serving cell, that can be included in a measurement report. IE Value

Engineering Unit

Allowed Range

Integer [1..8]

1, 2, .., 8

Recommended

4-6

4-6

7

Setting Tradeoff: If the parameter is too low, only few neighbor cells are reported, saving UE processing, while not providing the eNodeB with many options in case a handover to a target cell fails (due to lack of resources for example). If it is too high, more cells are reported, requiring higher UE processing while giving the eNodeB more choices of target cells.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  maxReportcells

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

244

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.3.5.1.7 reportInterval (Event B2 Reporting Interval) Definition: This parameter indicates the interval between measurement reports sent by the UE. It is applicable for trigger type ‘event’ or ‘periodical’, when the parameter ‘reportAmount’ (5.2.4.8) is greater than 1. IE Value

Engineering Unit

Allowed Range

Enum{ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60, spare3, spare2, spare1}

120, 240, 480, 640, 1024, 2048, 5120 , 10240 ms 1, 6, 12, 30, 60 min

Recommended

ms480

480 ms

8

Setting Tradeoff: If this parameter is set too low, the UE will transmit an unnecessarily large number of measurement reports, consuming processing power in the E-UTRAN. On the other hand, if it is too large, the reporting will not be updated frequently enough as to accurately reflect the UE´s environment.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  reportInterval

14

Notes:

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

245

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.5.1.8 reportAmount (Event B2 Number of Reports) Definition: Number of times a measurement report is sent. It is applicable for TriggerType ‘event’ as well as for TriggerType ‘periodical’. In case purpose is set to ‘reportCGI’ only value 1 applies. IE Value

Engineering Unit

Allowed Range

{r1, r2, r4, r8, r16, r32, r64, infinity}

1, 2, 4, 8, 16, 32, 64, infinity

Recommended

infinity

infinity

7

Setting Tradeoff: If the parameter is set too low, the UE will prematurely stop sending measurement reports which could potentially delay a handover in case the previous messages are not received by the eNodeB. If it is too high, the UE may be sending an unnecessarily large number of measurement reports to the eNodeB, wasting EUTRAN resources.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  reportAmount

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

246

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.3.6

2

9.3.6.1 Event B2

3

9.3.6.1.1 Event B2 Triggering Threshold for Serving Cell

4 5 6

Handover to GERAN

Definition: This is the threshold used by the Serving E-UTRAN Cell (LTE Cell) in order to evaluate the event B2. This threshold is a choice of RSRP or RSRQ and it uses a table mapping reference given in 36.133 sections 9.1.4 or 9.1.7, for RSRP and RSRQ respectively.

7

IE Value

Allowed Range Recommended 8 9 10

Engineering Units

RSRP Integer [0..97]

RSRP

(IE value – 140dBm)

RSRQ

RSRQ

(IE value – 40)/2

Integer [0..34]

RSRP 22-24

RSRP -116 to -118 dBm

Setting Tradeoff: If the parameter is set too low (meaning low dBm or dB), it will delay the event triggering, possibly with service degradation in the EUTRA cell. If the parameter is set too high, the event will be triggered too early while the quality of the EUTRA cell is still acceptable.

12

Dependencies/Constraints: B2-Threshold1 of E-UTRAN serving cell should be set in conjunction with B2-Threshold2 of the Inter-RAT cell.

13

Traceability: TS 33.331 Sect. 6.3.5

14

RRC Message Structure:

11

16

RRC Connection Reconfiguration  MeasConfig  ReportConfigtoaddmod  ReportConfig  ReportConfigInterRAT  B2-Threshold1  ThresholdEUTRA

17

Notes:

15

18 19 20 21

An appropriate setting of RSRP for event B2 triggering threshold should be set in such a way that the throughput degradation between LTE and GPRS/EDGE after IRAT completes is not significant. The LTE deployment bandwidth also has impact on the decision of how aggressive the threshold would be.

22

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

247

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Handover Parameter Settings

9.3.6.1.2 Event B2 Triggering Threshold for GERAN Cell Definition: This is the threshold used by the Target GERAN Cell (GSM Cell) in order to evaluate the event B2.

Released - For Current Employee/Consultant Use Only

4

IE Value

5 6 7 8 9

Engineering Units

Allowed Range

ThresholdGERAN Integer[0..63]

IE value – 110 dBm

Recommended

4

-96 dBm

Setting Tradeoff: If the parameter is set too low, the GERAN cell might be considered for a handover while the signal is still not acceptable. If the parameter is set too high, it will delay the event triggering which can cause service degradation in the EUTRA cell. Dependencies/Constraints: B2-Threshold1 of E-UTRAN serving cell should be set in conjunction with B2-Threshold2 of the Inter-RAT cell.

10

Traceability: TS 33.331 Sect. 6.3.5

11

RRC Message Structure:

13

RRC Connection Reconfiguration  MeasConfig  ReportConfigtoaddmod  ReportConfig  ReportConfigInterRAT  b2-Threshold2  b2-Threshold2GERAN  ThresholdGERAN

14

Notes:

12

15 16

This threshold is based on RSSI (RXLEV) and it uses a table mapping reference given in 45.008 sections 8.1.4.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

248

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.6.1.3 hysteresis (Event B2 Hysteresis) Definition: This hysteresis is used in the formulas that specify the entering and leaving conditions for event B2 (5.2). IE Value

Engineering Unit

Allowed Range

Integer (0..30)

IE value * 0.5 dB

Recommended

4

2 dB

7

Setting Tradeoff: The smallest the hysteresis, the sooner the UE will trigger an event B2, possibly while the source cell is still acceptable. On the other hand, a large hysteresis will delay the triggering of event B2, affecting the performance of the connection on the source cell while the target cell is a better candidate.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  event  hysteresis

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

249

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.6.1.4 timeToTrigger (Event B2 Time to Trigger) Definition: Time during which the measurement report triggering condition for an event must be met in order to trigger an event B2. IE Value

Engineering Unit

UNIT: ms

Allowed Range

Enum{ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120}

Recommended

ms256 (ms640 if UTRAN available)

256 ms (640 ms if UTRAN available)

RANGE: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560, 5120

6

Setting Tradeoff: Rapid, temporary, short term fluctuations can initiate an event B2 if the parameter Time to Trigger is too small. On the contrary, a too large setting will delay the event triggering, possibly causing service degradation on the source cell.

7

Dependencies/Constraints:

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  event  timeToTrigger

12

Notes:

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

250

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.6.1.5 maxReportcells (Event B2 Maximum Number of Reported Cells) Definition: Maximum number of cells, excluding the serving cell, that can be included in a measurement report. IE Value

Engineering Unit

Allowed Range

Integer [1..8]

1, 2, .., 8

Recommended

4-6

4-6

7

Setting Tradeoff: If the parameter is too low, only few neighbor cells are reported, saving UE processing, while not providing the eNodeB with many options in case a handover to a target cell fails (due to lack of resources for example). If it is too high, more cells are reported, requiring higher UE processing while giving the eNodeB more choices of target cells.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  maxReportcells

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

251

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.3.6.1.6 reportInterval (Event B2 Reporting Interval) Definition: This parameter indicates the interval between measurement reports sent by the UE. It is applicable for trigger type ‘event’ or ‘periodical’, when the parameter ‘reportAmount’ (5.2.5.7) is greater than 1. IE Value

Allowed Range

Recommended

Engineering Unit

Enum{ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60, spare3, spare2, spare1}

120, 240, 480, 640, 1024, 2048, 5120 , 10240 ms

ms480

480 ms

1, 6, 12, 30, 60 min

8

Setting Tradeoff: If this parameter is set too low, the UE will transmit an unnecessarily large number of measurement reports, consuming processing power in the E-UTRAN. On the other hand, if it is too large, the reporting will not be updated frequently enough as to accurately reflect the UE´s environment.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  reportInterval

14

Notes:

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

252

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.6.1.7 reportAmount (Event B2 Number of Reports) Definition: Number of times a measurement report is sent. It is applicable for TriggerType ‘event’ as well as for TriggerType ‘periodical’. In case purpose is set to ‘reportCGI’ only value 1 applies. IE Value

Engineering Unit

Allowed Range

{r1, r2, r4, r8, r16, r32, r64, infinity}

1, 2, 4, 8, 16, 32, 64, infinity

Recommended

infinity

infinity

7

Setting Tradeoff: If the parameter is set too low, the UE will prematurely stop sending measurement reports which could potentially delay a handover in case the previous messages are not received by the eNodeB. If it is too high, the UE may be sending an unnecessarily large number of measurement reports to the eNodeB, wasting EUTRAN resources.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  reportAmount

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

253

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

Handover Parameter Settings

1

9.3.7

2

9.3.7.1 Event B2

3

9.3.7.1.1 Event B2 Triggering Threshold for Serving Cell

4 5 6

Handover to CDMA2000

Definition: This is the threshold used by the Serving E-UTRAN Cell (LTE Cell) in order to evaluate the event B2. This threshold is a choice of RSRP or RSRQ and it uses a table mapping reference given in 36.133 sections 9.1.4 or 9.1.7, for RSRP and RSRQ respectively.

7

IE Value

Allowed Range Recommended 8 9 10

Engineering Units

RSRP Integer [0..97]

RSRP

(IE value – 140dBm)

RSRQ

RSRQ

(IE value – 40)/2

Integer [0..34]

RSRP 25

RSRP -115 dBm

Setting Tradeoff: If the parameter is set too low (meaning low dBm or dB), it will delay the event triggering, possibly with service degradation in the EUTRA cell. If the parameter is set too high, the event will be triggered too early while the quality of the EUTRA cell is still acceptable.

12

Dependencies/Constraints: B2-Threshold1 of E-UTRAN serving cell should be set in conjunction with B2-Threshold2 of the Inter-RAT cell.

13

Traceability: TS 33.331 Sect. 6.3.5

14

RRC Message Structure:

11

16

RRC Connection Reconfiguration  MeasConfig  ReportConfigtoaddmod  ReportConfig  ReportConfigInterRAT  B2-Threshold1  ThresholdEUTRA

17

Notes:

15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

254

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Handover Parameter Settings

9.3.7.1.2 Event B2 Triggering Threshold for CDMA2000 Cell Definition: This is the threshold used by the Target CDMA2000 Cell in order to evaluate the event B2. This threshold is a choice of Pilot Strength or PN Phase plus Pilot Strength.

Released - For Current Employee/Consultant Use Only

4

IE Value

5 6 7 8 9 10

Engineering Units

Allowed Range

pilotStrength Integer[0..63]

IE value/(-2)

Recommended

14

-7 dB

Setting Tradeoff: If the parameter is set too low, the CDMA cell might be considered for a handover while the signal or quality is still not acceptable. If the parameter is set too high, it will delay the event triggering which can cause service degradation in the EUTRA cell. Dependencies/Constraints: B2-Threshold1 of E-UTRAN serving cell should be set in conjunction with B2-Threshold2 of the Inter-RAT cell. Traceability: TS 33.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigtoaddmod  ReportConfig  ReportConfigInterRAT  b2-Threshold2  b2Threshold2CDMA2000  ThresholdCDMA2000

14

Notes:

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

255

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.7.1.3 hysteresis (Event B2 Hysteresis) Definition: This hysteresis is used in the formulas that specify the entering and leaving conditions for event B2 (5.2). IE Value

Engineering Unit

Allowed Range

Integer (0..30)

IE value * 0.5 dB

Recommended

4

2 dB

7

Setting Tradeoff: The smallest the hysteresis, the sooner the UE will trigger an event B2, possibly while the source cell is still acceptable. On the other hand, a large hysteresis will delay the triggering of event B2, affecting the performance of the connection on the source cell while the target cell is a better candidate.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  event  hysteresis

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

256

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.7.1.4 timeToTrigger (Event B2 Time to Trigger) Definition: Time during which the measurement report triggering condition for an event must be met in order to trigger an event B2. IE Value

Engineering Unit

UNIT: ms

Allowed Range

Enum{ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120}

Recommended

ms480

480 ms

RANGE: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560, 5120

6

Setting Tradeoff: Rapid, temporary, short term fluctuations can initiate an event B2 if the parameter Time to Trigger is too small. On the contrary, a too large setting will delay the event triggering, possibly causing service degradation on the source cell.

7

Dependencies/Constraints:

8

Traceability: TS 36.331 Sect. 6.3.5

4 5

11

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  event  timeToTrigger

12

Notes:

9 10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

257

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.7.1.5 maxReportcells (Event B2 Maximum Number of Reported Cells) Definition: Maximum number of cells, excluding the serving cell, that can be included in a measurement report. IE Value

Engineering Unit

Allowed Range

Integer [1..8]

1, 2, .., 8

Recommended

4-6

4-6

7

Setting Tradeoff: If the parameter is too low, only few neighbor cells are reported, saving UE processing, while not providing the eNodeB with many options in case a handover to a target cell fails (due to lack of resources for example). If it is too high, more cells are reported, requiring higher UE processing while giving the eNodeB more choices of target cells.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  maxReportcells

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

258

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4

Handover Parameter Settings

9.3.7.1.6 reportInterval (Event B2 Reporting Interval) Definition: This parameter indicates the interval between measurement reports sent by the UE. It is applicable for trigger type ‘event’ or ‘periodical’, when the parameter ‘reportAmount’ (5.2.6.7) is greater than 1. IE Value

Engineering Unit

Allowed Range

Enum{ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60, spare3, spare2, spare1}

120, 240, 480, 640, 1024, 2048, 5120 , 10240 ms 1, 6, 12, 30, 60 min

Recommended

ms480

480 ms

8

Setting Tradeoff: If this parameter is set too low, the UE will transmit an unnecessarily large number of measurement reports, consuming processing power in the E-UTRAN. On the other hand, if it is too large, the reporting will not be updated frequently enough as to accurately reflect the UE´s environment.

9

Dependencies/Constraints:

5 6 7

10

Traceability: TS 36.331 Sect. 6.3.5

13

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  reportInterval

14

Notes:

11 12

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

259

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2

Released - For Current Employee/Consultant Use Only

3

Handover Parameter Settings

9.3.7.1.7 reportAmount (Event B2 Number of Reports) Definition: Number of times a measurement report is sent. It is applicable for TriggerType ‘event’ as well as for TriggerType ‘periodical’. In case purpose is set to ‘reportCGI’ only value 1 applies. IE Value

Engineering Unit

Allowed Range

{r1, r2, r4, r8, r16, r32, r64, infinity}

1, 2, 4, 8, 16, 32, 64, infinity

Recommended

infinity

infinity

7

Setting Tradeoff: If the parameter is set too low, the UE will prematurely stop sending measurement reports which could potentially delay a handover in case the previous messages are not received by the eNodeB. If it is too high, the UE may be sending an unnecessarily large number of measurement reports to the eNodeB, wasting EUTRAN resources.

8

Dependencies/Constraints:

9

Traceability: TS 36.331 Sect. 6.3.5

4 5 6

12

RRC Message Structure: RRC Connection Reconfiguration  MeasConfig  ReportConfigToAddModList  ReportConfigToAddMod  reportConfig  ReportConfigInterRAT  reportAmount

13

Notes:

10 11

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

260

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

10 MAC Parameters

2

Chapter 10: Table of Contents

3

10.1 Introduction .......................................................................................................................................... 263

4

10.2 RACH Related MAC Layer Parameters ........................................................................................... 264

5

10.2.1 ra-PreambleIndex (PRACH Preamble Index) ............................................................................... 264

6

10.3 Logical Channel Related MAC Layer Parameters........................................................................... 265

7

10.3.1 Priority ................................................................................................................................................ 265

8

10.3.2 prioritisedBitRate .............................................................................................................................. 266

9

10.3.3 bucketSizeDuration .......................................................................................................................... 267

10

10.3.4 logicalChannelGroup ....................................................................................................................... 268

11

10.4 HARQ Related MAC Layer Parameter ............................................................................................. 269

12

10.4.1 MaxHARQ-Tx ................................................................................................................................... 269

13

10.5BSR Related MAC Layer Parameters ................................................................................................. 270

14

10.5.1 periodicBSR-Timer............................................................................................................................ 270

15

10.5.2 retxBSR-Timer ................................................................................................................................... 271

16

10.6 PHR Related MAC Layer Parameters ............................................................................................... 272

17

10.6.1 phr-Configuration ............................................................................................................................. 272

18

10.6.2 periodicPHR-Timer .......................................................................................................................... 273

19

10.6.3 prohibitPHR-Timer ........................................................................................................................... 274

20

10.6.4 dl-PathLossChange ........................................................................................................................... 275

21

10.7 Connected State DRX Related MAC Parameters ............................................................................ 276

22

10.7.1 DRX-Config........................................................................................................................................ 276

23

10.7.2 DRX-InactivityTimer ........................................................................................................................ 277

24

10.7.3 onDurationTimer .............................................................................................................................. 278

25

10.7.4 drx-RetransmissionTimer ................................................................................................................ 279

26

10.7.5 longDRX-CycleStartOffset ............................................................................................................... 280

27

10.7.6 shortDRX ............................................................................................................................................ 282 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

261

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

MAC Parameters

1

10.7.7 shortDRX-Cycle................................................................................................................................. 283

2

10.7.8 drxShortCycleTimer ......................................................................................................................... 284

3

10.8 Semi Persistent Scheduling................................................................................................................. 285

4

10.9.1 ttiBundling ......................................................................................................................................... 292

5

10.9.2 timeAlignmentTimerDedicated ...................................................................................................... 293

6

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

262

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

MAC Parameters

10.1 Introduction E-UTRA defines two MAC entities; one in the UE and one in the E-UTRAN. These MAC entities handle the following transport channels:

4

- Broadcast Channel (BCH);

5

- Downlink Shared Channel (DL-SCH);

6

- Paging Channel (PCH);

7

- Uplink Shared Channel (UL-SCH);

8

- Random Access Channel(s) (RACH).

9

10

11 12

The following functions are supported by MAC sublayer: - mapping between logical channels and transport channels; - multiplexing of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels;

14

- demultiplexing of MAC SDUs from one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels;

15

- scheduling information reporting;

16

- error correction through HARQ;

17

- priority handling between UEs by means of dynamic scheduling;

18

- priority handling between logical channels of one UE;

19

- Logical Channel prioritisation;

20

- transport format selection.

13

21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

263

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

MAC Parameters

1

10.2 RACH Related MAC Layer Parameters

2

10.2.1 ra-PreambleIndex (PRACH Preamble Index)

3

Definition: PRACH preamble index value, optionally signaled to the UE at handover IE Value Allowed Range

Recommended

4 5

[0 … 63]

Engineering Units UNIT: INTEGER RANGE: 0 … 63

Use it if the contention-free handover is supported

Setting Tradeoff: Use this parameter only if the contention-free handover is supported. The specific value has no significance. .

7

Dependencies/Constraints: The value 0 shall not be used (TS36.321 Sect. 5.1.2). Value has to be larger than numberOfRA-Preambles (i.e. out of the non-dedicated preambles pool)

8

Traceability: TS36.321 Sect. 5.1.1 and 5.1.2; TS36.331 Sect. 6.3.2

9

RRC Message Structure:

6

10 11 12 13

RRCConnectionReconfiguration  MobilityControlInfo  RACH-Config-Common Notes: When triggering handover the network may signal to the UE the PRACH preamble index and the PRACH mask index. In this case the UE MAC layer will trigger a contention free random access procedure using the received preamble index and mask.

16

If the preamble index or the mask index is absent (or the preamble index is 0), a contention based procedure is initiated (which requires more time to complete). For this case the UE MAC will randomly choose a preamble index from a given pool and will set the mask index to zero.

17

[See also notes numberOfRA-Preambles sizeOfRA-PreamblesGroupA and messageSizeGroupA]

14 15

18 19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

264

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.3 Logical Channel Related MAC Layer Parameters

2

10.3.1 Priority

3

Released - For Current Employee/Consultant Use Only

MAC Parameters

4 5

Definition: Determines the priority of the UL logical channels (Signaling Radio Bearers and Default/Dedicated Radio Bearers), where a higher priority value indicates a lower priority level. This parameter is configured per Radio Bearer basis. IE Value Allowed Range

Recommended

[1 … 16]

Engineering Units UNIT: INTEGER RANGE: 1 … 16

Set it in such a way that SRB priority > DRB priority For priority among DRBs, set it according to the QoS requirements.

8

Setting Tradeoff: When value is set to high, the Radio Bearer might get deprived from UL allocations if the remaining Radio Bearers have higher priority level. When set to low, the RB will have a higher priority in obtaining grant to transmit on the UL.

9

Dependencies/Constraints: None.

6 7

10

Traceability: TS 36.321 Sect 5.4.3, TS36.331 Sect 6.3.2

11

RRC Message Structure:

12 13

rrcConnectionSetup  radioResourceConfigDedicated  srb-ToAddModList  logicalChannelConfig explicitValue  priority

15

RRCConnectionReconfiguration  radioResourceConfigDedicated  drb-ToAddModList  logicalChannelConfig explicitValue  priority

16

Notes: None.

14

17 18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

265

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

MAC Parameters

10.3.2 prioritisedBitRate Definition: The token bucket level increasing rate. In other words, it is the token size in bytes added to the bucket during each TTI. This parameter is configured per Radio Bearer basis. IE Value Allowed Range

Engineering Units

ENUMERATED {

UNIT: kBps

kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, infinity}

RANGE: 0, 8, 16, 32, 64, 128, 256, infinity

Depends on the QoS requirement per radio bearer. In general, set it to infinity. If want to prioritize the relative bit rate, we can consider setting it to different values for different traffic -

set it to Infinity for BE traffic (if only one default bearer)

-

if we have 3 bearers: BE, Voice, Video:

Recommended

voice, QCI2, lower QCI ones -> infinity BE -> non-infinity -

For example, QCI 7,8,9, set is to non-infinity.

-

If set it to infinity, it will be always high class, and no rate control.

8

Setting Tradeoff: When set too high (∞), the bucket level is always considered to be positive -> will be served by a portion or the entire grant whenever UE receives an UL allocation. When set too low (zero), the RB will only be served with a grant upon the reception of an UL allocation, and the remaining RBs have the bucket level in negative. In the middle range, this parameter defines the size in bytes allocated to the RB bucket.

9

Dependencies/Constraints: None.

4 5 6 7

10 11 12

Traceability: TS 36.321 Sect 5.4.3, TS36.331 Sect 6.3.2RRC Message Structure: rrcConnectionSetup  radioResourceConfigDedicated  srb-ToAddModList  logicalChannelConfig explicitValue  prioritizedBitRate

14

RRCConnectionReconfiguration  radioResourceConfigDedicated  drb-ToAddModList  logicalChannelConfig explicitValue  prioritizedBitRate

15

Notes: Infinity is the only applicable value for SRB1 and SRB2.

13

16

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

266

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.3.3 bucketSizeDuration

4

Definition: Time needed for a bucket to reach its max level with the assumption that no withdraws of tokens during this time. This parameter is configured per Radio Bearer basis. Hence the bucket size can be derived from the product of the Bucket Size Duration and the Prioritization Bit Rate.

5

Bucket size = PBR x BSD

2 3

Released - For Current Employee/Consultant Use Only

MAC Parameters

IE Value ENUMERATED { Allowed Range ms50, ms100, ms150, ms300, ms500, ms1000 } Recommended

Engineering Units UNIT: ms RANGE: 50, 100, 150, 300, 500, 1000

Depends on QoS requirement per radio bearer, set it to 50 ms for BE traffic.

10

Setting Tradeoff: assuming we have the same PBR: when set to high -> larger bucket size -> larger amount of data can be transmitted on the UL (form the buffer) before the Bucket level is depleted. When set too low -> smaller bucket size -> less data can be transmitted on the UL (from the buffer) before the bucket level hit the negative level -> no more grant or portion of a grant can be allocated to this Radio Bearer if the remaining Bearers have positive bucket level.

11

Dependencies/Constraints: None.

12

Traceability: TS 36.321 Sect 5.4.3, TS36.331 Sect 6.3.2

6 7 8 9

13 14 15 16

RRC Message Structure: rrcConnectionSetup  radioResourceConfigDedicated  srb-ToAddModList  logicalChannelConfig explicitValue  bucketSizeDuration

18

RRCConnectionReconfiguration  radioResourceConfigDedicated  drb-ToAddModList  logicalChannelConfig explicitValue  bucketSizeDuration

19

Notes: None.

17

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

267

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

MAC Parameters

10.3.4 logicalChannelGroup Definition: A group of logical channels (DRBs/SRBs) identified by a unique 2-bit LCG ID. Logical Channels that belong to the same LCG will have their buffer sizes reported collectively to eNB when sending the BSR. The mapping of logical channels to LCG is set up during RRC configuration. IE Value Allowed Range

Recommended

5 6 7 8 9

[0 … 3]

Engineering Units UNIT: INTEGER RANGE: 0 … 3

QoS and eNB scheduler implementation dependent.

Setting Tradeoff: When all the LCID are assigned to the one LCG, the UE will be reporting the buffer size as a short BSR (2 bytes) -> smaller overhead; however the buffer size granularity per logical channel is lost. When all the LCG have been assigned, finer granularity of the logical channel(s) buffer size is provided, however UE will be reporting the buffer size as a long BSR (4 bytes) -> larger overhead.

10

Dependencies/Constraints: None.

11

Traceability: TS 36.321 Sect 5.4.3, TS36.331 Sect 6.3.2RRC Message Structure:

12 13

rrcConnectionSetup  radioResourceConfigDedicated  srb-ToAddModList  logicalChannelConfig explicitValue  logicalChannelGroup

15

RRCConnectionReconfiguration  radioResourceConfigDedicated  drb-ToAddModList  logicalChannelConfig explicitValue  logicalChannelGroup

16

Notes: None.

14

17 18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

268

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.4 HARQ Related MAC Layer Parameter

2

10.4.1 MaxHARQ-Tx

3

Released - For Current Employee/Consultant Use Only

MAC Parameters

4

Definition: Maximum number of HARQ transmissions on all HARQ processes and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer. IE Value ENUMERATED { Allowed Range n1, n2, n3, n4, n5, n6, n7, n8, n10, n12, n16, n20, n24, n28,}

Engineering Units UNIT: INTEGER RANGE: 1, 2, 3, 4, 5, 6, 7, 8, 10, 12, 16, 20, 24, 28

n4 Recommended

Trade off end-to-end delay and capacity. For volte, strongly recommend it to n4, for BE, it can be relaxed.

8

Setting Tradeoff: If the parameter is set too high, it provides higher reliability for the air interface; in addition it provides the UE more time to recover from a bad channel condition before declaring/detecting an RL hence it takes more time to detect an RLF if it exists. If the parameter is set too low,it provides less reliable air-interface but faster detection of an RLF if it exists.

9

Dependencies/Constraints: None.

5 6 7

10 11 12

Traceability: TS 36.321 Sect 5.4.2, TS36.331 Sect 6.3.2RRC Message Structure: rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig ul-SCH-Config maxHARQ-Tx

14

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig ul-SCHConfig maxHARQ-Tx

15

Notes: For Msg3 see parameter maxHARQ-Msg3Tx

13

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

269

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.5 BSR Related MAC Layer Parameters

2

10.5.1 periodicBSR-Timer

3

Released - For Current Employee/Consultant Use Only

MAC Parameters

4

Definition: PeriodicBSR-Timer will be started / restarted after the transmission of any BSR. Upon expiry, UE sends a Buffer Status Report (Periodic BSR) to eNB. IE Value

5 6 7 8 9

Engineering Units

ENUMERATED {

UNIT: ms

Allowed Range

sf5, sf10, sf16, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf320, sf640, sf1280, sf2560, infinity}

RANGE: 5, 10, 16, 20, 32, 40, 64, 80, 128, 160, 320, 640, 1280, 2560, infinity

Recommended

sf5

5 ms

Setting Tradeoff: If the parameter is set too high, the UE sends the BSR less frequently. Less insight is provided to the eNB about the Logical Channels buffer level; on the other hand, less overhead is expected. If the parameter is set too low, the UE sends the BSR more frequently. The eNB is more aware about the buffer levels, but this will come with the price of more overheads (2 bytes for S-BSR, 4 Bytes for L-BSR) with each transmission.

10

Dependencies/Constraints: None.

11

Traceability: TS 36.321 Sect 5.4.5, TS36.331 Sect 6.3.2RRC Message Structure:

12 13

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig ul-SCH-Config  periodicBSR-Timer

15

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig ul-SCHConfig  periodicBSR-Timer

16

Notes: None.

14

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

270

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

MAC Parameters

10.5.2 retxBSR-Timer Definition: RetxBSR-Timer will be started / restarted after the transmission of any type of BSR, or upon the reception of an UL allocation. When expired, it will trigger a Regular BSR if data exist in the buffer. IE Value

Engineering Units

ENUMERATED {

UNIT: ms

Allowed Range

sf320, sf640, sf1280, sf2560, sf5120, sf10240}

RANGE: 320, 640, 1280, 2560, 5120, 10240

Recommended

sf320

320 ms

7

Setting Tradeoff: If the parameter is set too high, the data received on a LC may stay in the buffer for a long time before an SR is triggered requesting an UL allocation. If the parameter is set too low, the SR will be triggered immediately if UE has data available for transmission.

8

Dependencies/Constraints: None.

9

Traceability: TS 36.321 Sect 5.4.5, TS36.331 Sect 6.3.2RRC Message Structure:

5 6

10 11

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig ul-SCH-Config  retxBSR-Timer

13

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig ul-SCHConfig  retxBSR-Timer

14

Notes:

12

15 16

If max number of SR is reached and no UL allocation was assigned to the UE , it will trigger the RACH process.

17 18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

271

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.6 PHR Related MAC Layer Parameters

2

10.6.1 phr-Configuration

3

Released - For Current Employee/Consultant Use Only

MAC Parameters

4 5

Definition: If enabled, The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. IE Value

6 7 8 9

Allowed Range

Release, Setup

Recommended

Setup

Engineering Units Release (disabled), Setup (enabled)

Setting Tradeoff: if enabled, the eNB will have more insight about the power headroom at the UE, which will allow the eNB to customize the size of the UL allocation. The price is more overhead (2 bytes for every transmission). If disabled, eNB might serve the UE with UL allocation beyond its power capability then a transmission opportunity may be wasted.

10

Dependencies/Constraints: None.

11

Traceability: TS 36.321 Sect 5.4.6, TS36.331 Sect 6.3.2

12

RRC Message Structure:

13

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  phr-Config

15

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  phrConfig

16

Notes: None.

14

17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

272

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

MAC Parameters

10.6.2 periodicPHR-Timer Definition: A power headroom report (PHR) will be triggered upon the expiry of this timer. The timer will be started/restarted after every transmission of the PHR. IE Value Allowed Range

Engineering Units

ENUMERATED {sf10, sf20, sf50, sf100, sf200, sf500, sf1000, infinity}

UNIT: ms

sf50 – sf200

50 – 200 ms

RANGE: 10, 20, 50, 100, 200, 500, 1000, infinity, subframes

Depends on device mobility Recommended

-

For high mobility, set it to lower value.

-

If stationary, sf1000 is fine.

6

Setting Tradeoff: the higher the value of the timer, the less frequent the UE will transmit a PHR. if is set to infinity, it indicates no PHR transmission. The lower the value of the timer, UE more frequently transmits the PHR. The price of transmitting a PHR is 2 bytes overhead

7

Dependencies/Constraints: None.

8

Traceability: TS 36.321 Sect 5.4.6, TS36.331 Sect 6.3.h2

9

RRC Message Structure:

4 5

10 11

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  phr-Config  periodicPHR-Timer

13

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  phrConfig  periodicPHR-Timer

14

Notes:

12

15 16 17

There are performance simulation studies suggesting that the setting of 50ms gives close-to-ideal performance in terms of uplink capacity. A setting of 200ms will reduce the PHR overhead, but may slightly reduce the uplink capacity.

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

273

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5

MAC Parameters

10.6.3 prohibitPHR-Timer Definition: This timer will be restarted every time the UE sends a PHR (regardless of the trigger). This timer will prevent an excessive transmission of the PHR in a fast fading radio channel where the dl-PathLoassChange goes beyond the threshold value frequently during a period of time shorter than the “ProhibitPHR-Timer”. IE Value Allowed Range

Engineering Units

ENUMERATED {sf0, sf10, sf20, sf50, sf100,sf200, sf500, sf1000}

UNIT: ms

sf50-sf200

50 – 200 ms

RANGE: 0, 10, 20, 50, 100, 200, 500, 1000

Depends on device mobility Recommended

6 7 8

-

For high mobility, set it to lower value.

-

If stationary, sf1000 is fine.

Setting Tradeoff: If the parameter is set too high, less frequent PHR transmission will be sent, even if the Delta DL path loss goes beyond the configured threshold value. If the parameter is set too low, more frequent PHR transmission.

10

If it is set to 0, this timer is disabled.if the Delta DL path loss goes beyond the threshold value at any time, the PHR will be transmitted (basically no restriction any more).

11

Dependencies/Constraints: None.

12

Traceability: TS 36.321 Sect 5.4.6, TS36.331 Sect 6.3.2

13

RRC Message Structure:

9

14 15

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  phr-Config  prohibitPHR-Timer

17

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  phrConfig  prohibitPHR-Timer

18

Notes:

16

19 20

Typically set this parameter lower than periodicPHR-Timer. For instance, if periodicPHR-timer is set to 200ms, then an appropriate setting for prohibitPHR-Timer could be 100ms.

21 22

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

274

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

MAC Parameters

10.6.4 dl-PathLossChange Definition: The change in measured downlink path loss. If the change goes beyond the threshold value provided in the table below, a PHR will be triggered given that the prohibitPHR-Timer had expired. IE Value

Engineering Units

Allowed Range

ENUMERATED {dB1, dB3, dB6, infinity}

UNIT: dB

Recommended

dB3

3 dB

RANGE: 1dB, 3dB, 6dB, infinity

7

Setting Tradeoff: the higher the value of the parameter, the less frequent the UE will transmit a PHR. If is set to infinity, it indicates that this field is diabled. The lower the value of the parameter, more frequently the UE will transmit a PHR (given the prohibitPHR-Timer had expired).

8

Dependencies/Constraints: None.

9

Traceability: TS 36.321 Sect 5.4.6, TS36.331 Sect 6.3.2

5 6

10

RRC Message Structure:

11

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  phr-Config 

12

dl-PathLossChange

14

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  phrConfig  dl-PathLossChange

15

Notes:

13

16 17 18

There are performance simulation studies suggesting dB1 setting to have close-to-ideal performance in terms of uplink capacity in the absence of periodic PHR reporting and prohibitPHR-Timer disabled.

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

275

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.7 Connected State DRX Related MAC Parameters

2

10.7.1 DRX-Config

3

Released - For Current Employee/Consultant Use Only

MAC Parameters

4 5 6

Definition: DRX stands for discontinuous reception, where the UE will turn off its receiver and stop monitoring the PDCCH. If enabled, the UE is going through DRX cycles (one cycle = DRX ON period followed by DRX OFF period). If DRX is disabled, the UE is monitoring the PDCCH in each sub-frame. IE Value Allowed Range

Release, Setup

Recommended

Setup

Engineering Units Release (disabled), Setup (enabled)

11

Setting Tradeoff: If DRX is disabled, the UE will be monitoring each PDCCH. The UE will have the faster response to the network commands (page, PDCCH order…). However this will minimize the battery life. When DRX is enabled, this will extend the battery life, however the network commands might take longer before being delivered to the UE (e.g. before sending the page, the eNB need to ensure that the UE is in its ON-Duration period).

12

Dependencies/Constraints: None.

13

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

14

RRC Message Structure:

15

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config

16

rrcConnectionReconfiguratio  radioResourceConfigDedicated  mac-MainConfig  drx-Config

17

Notes: None.

7 8 9 10

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

276

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

MAC Parameters

10.7.2 DRX-InactivityTimer Definition: Specify the number of subframes for which a UE continues to monitor the Downlink for an absence of activity that will trigger the UE to enter DRX mode. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED {psf1, psf2, psf3, psf4, psf5, psf6, psf8, psf10, psf20, psf30, psf40, psf50, psf60, psf80, psf100, psf200, psf300, psf500, psf750, psf1280, psf1920, psf2560}

UNIT: ms

psf200 for burst BE traffic

200 ms for burst BE traffic

psf2 for streaming/voice traffic

2 ms for streaming/voice traffic

RANGE: 1, 2, 3, 4, 5, 6, 8, 10, 20, 30, 40, 50, 60, 80, 100, 200, 300, 500, 750, 1280, 1920, 2560

6

Setting Tradeoff: If the parameter is set too high, the UE is less probable to go into a DRX mode; in addition it will delay the start of the DRX cycle. If the parameter is set too low, the UE is more probable to go into a DRX mode with a prompt start of the DRX cycle.

7

Dependencies/Constraints: None.

8

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

9

RRC Message Structure:

4 5

10 11

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config  onDurationTimer

13

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  drxConfig  onDurationTimer

14

Notes:

12

15 16 17 18

For applications that have short and fast busts of data with lower frequency (e.g. web-browsing), it is recommended to configure longer inactivity timer. For applications with smaller more frequent bursts of data (e.g. video streaming or voice over IP), it is recommended to configure shorter inactivity timer.

19 20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

277

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

MAC Parameters

10.7.3 onDurationTimer Definition: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle. In other words, it is the period of the DRX cycle where the UE monitors the PDCCH. Afterward, the UE will goes into the DRX Off for a duration of DRX_CYCLE – OnDurationTimer. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED {psf1, psf2, psf3, psf4, psf5, psf6, psf8, psf10, psf20, psf30, psf40, psf50, psf60, psf80, psf100, psf200}

Unit: ms

psf10 for burst BE traffic

10 ms for burst BE traffic

psf2 for streaming/voice traffic

2 ms for streaming/voice traffic

RANGE: 1, 2, 3, 4, 5, 6, 8, 10, 20, 30, 40, 50, 60, 80, 100, 200

8

Setting Tradeoff: If the parameter is set too high, the network command may be received promptly (e.g. take less time to page the UE); however the handset battery life is shorter. If the parameter is set too low, more time may be needed to transmit the network command (e.g. take more time to page the UE); however the handset battery life is longer.

9

Dependencies/Constraints: SPS parameter settings.

5 6 7

10

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

11

RRC Message Structure:

12 13

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config  onDurationTimer

15

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  drxConfig  onDurationTimer

16

Notes:

14

17 18 19 20

For applications that have short and fast busts of data with lower frequency (e.g. web-browsing), it is recommended to configure longer onDurationTimer. For applications with smaller more frequent bursts of data (e.g. video streaming or voice over IP), it is recommended to configure shorter onDurationTimer.

21 22

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

278

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5

MAC Parameters

10.7.4 drx-RetransmissionTimer Definition: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL retransmission is expected by the UE, hence it is configured per “DL HARQ process” basis. In other words, it serves as a time guard for a specific DL HARQ process when a HARQ retransmission is expected for this HARQ process (due to a HARQ failure), to delay the start of the DRX cycle. IE Value Allowed Range

Recommended

6 7 8 9

ENUMERATED {psf1, psf2, psf4, psf6, psf8, psf16, psf24, psf33}

RANGE: 1, 2, 4, 6, 8, 16, 24, 33

Setting Tradeoff: if the parameter is set too high, it will elongate the delay to start the DRX cycle, however it may allow the UE to recover the lost PDU through HARQ if retransmission occurs. If the parameter is set too low, it will minimize the delay to start the DRX cycle, however it might cause the UE not to decode the HARQ retransmission if it occurred since UE is in DRX. Dependencies/Constraints: None.

11

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

12

RRC Message Structure:

14

UNIT: ms

Set it to lower value for power consumption perspective.

10

13

Engineering Units

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config  drxRetransmissionTimer

16

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  drxConfig  drx-RetransmissionTimer

17

Notes: None

15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

279

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.7.5 longDRX-CycleStartOffset

2

Definition: This parameter specifies the value of two parameters:

3

Released - For Current Employee/Consultant Use Only

MAC Parameters



The duration of the longDRX-Cycle: a periodic repetition of the On-Duration followed by a possible period of inactivity for the long DRX cycle.



The drxStartOffset value: specifies the subframe where the DRX Cycle starts.

4

5

IE Value

Allowed Range

Engineering Units

CHOICE {

longDRX-Cycle

sf10

INTEGER(0..9),

10 subframes

(0..9) subframes,

sf20

INTEGER(0..19),

20 subframes

(0..19) subframes,

sf32

INTEGER(0..31),

32 subframes

(0..31) subframes,

sf40

INTEGER(0..39),

40 subframes

(0..39) subframes,

sf64

INTEGER(0..63),

64 subframes

(0..63) subframes,

sf80

INTEGER(0..79),

80 subframes

(0..79) subframes,

sf128

INTEGER(0..127),

128 subframes (0..127) subframes,

sf160

INTEGER(0..159),

160 subframes (0..159) subframes,

sf256

INTEGER(0..255),

256 subframes (0..255) subframes,

sf320

INTEGER(0..319),

320 subframes (0..319) subframes,

sf512

INTEGER(0..511),

512 subframes (0..511) subframes,

sf640

INTEGER(0..639),

640 subframes (0..639) subframes,

drxStartOffset

sf1024 INTEGER(0..1023),

1024 subframes

(0..1023) subframes,

sf1280 INTEGER(0..1279),

1280 subframes

(0..1279) subframes,

sf2048 INTEGER(0..2047),

2048 subframes

(0..2047) subframes,

sf2560 INTEGER(0..2559)

2560 subframes

(0..2559) subframes

}

Recommended

sf320 with short-cycle disabled for burst BE traffic

320 ms with short-cycle disabled for burst BE traffic

sf320 with short-cycle enabled for streaming/voice traffic

320 ms with short-cycle enabled for streaming/voice traffic

10

Setting Tradeoff: If the longDRX-Cycle is set too high, more time may be needed to transmit the network command/information (e.g., take more time to page the UE); but the UE battery life improves. If the longDRX-Cycle is set too low, the UE may receive the network command/information promptly (e.g., take less time to page the UE); but the UE battery life may reduce.

11

Dependencies/Constraints: None.

6 7 8 9

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

280

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

2

RRC Message Structure:

3 4

Released - For Current Employee/Consultant Use Only

MAC Parameters

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config  longDRX-CycleStartOffset

6

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  drxConfig  longDRX-CycleStartOffset

7

Notes:

5

8 9

Alternatively instead of using long DRX cycle only, it can be added a shortDRX-Cycle of 20ms with drxShortCycleTimer of 1 as a substitute for not configuring short DRX cycle.

10

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

281

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

MAC Parameters

10.7.6 shortDRX Definition: Optional configuration, if included, UE supports the ShortDRX cycles and LongDRX cycle, otherwise the UE only supports LongDRX cycles for the DRX mode. IE Value

Engineering Units

Allowed Range Recommended

Disable for burst BE traffic Enabled for streaming/voice traffic

5

Setting Tradeoff: if configured, it will allow a smooth transition into the DRX mode from the short DRX cycle to the long DRX cycle. Otherwise, the UE only supports the long DRX cycle.

6

Dependencies/Constraints: None.

7

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

8

RRC Message Structure:

4

9 10

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config  shortDRX

12

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  drxConfig  shortDRX

13

Notes:

11

14 15

Alternatively instead of using long DRX cycle only, it can be added a shortDRX-Cycle of 20ms with drxShortCycleTimer of 1 as a substitute for not configuring short DRX cycle.

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

282

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

MAC Parameters

1

10.7.7 shortDRX-Cycle

2

Definition: Specifies the DRX Cycle duration for ShortDRX mode.

3

ShortDRXCycle = OnDuration + DRXOpportunity

4

OnDuration: UE is monitoring the PDCCH in every subframe.

5

DRXOpportunity: UE is not monitoring the PDCCH. IE Value

Allowed Range

Recommended

6 7 8 9

Engineering Units

ENUMERATED

UNIT: ms

{sf2, sf5, sf8, sf10, sf16, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf256, sf320, sf512, sf640}

RANGE: 2, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640

Disable for burst BE traffic

Disable for burst BE traffic

sf40 for streaming/voice traffic

40 ms for streaming/voice traffic

Setting Tradeoff: For the same OnDuration value, if the ShortDRXCycle is configured too short the network command/information can be delivered faster to the UE but it may short the batter life. If the shortDRX-Cycle is set too long, the UE can receive the network command/information less promptly but with a longer battery life.

10

Dependencies/Constraints: This parameter should be optimized together with drxShortCycletimer.

11

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

12

RRC Message Structure:

13 14

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config  shortDRX  shortDRX-Cycle

16

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  drxConfig  shortDRX  shortDRX-Cycle

17

Notes:

15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

283

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

MAC Parameters

10.7.8 drxShortCycleTimer Definition: Specifies the number of ShortDRX Cycles that need to be achieved before starting the LongDRX-Cycle. IE Value Allowed Range

Recommended

[1 … 16]

Engineering Units UNIT: INTEGER RANGE: 1 … 16

Disable for burst BE traffic

Disable for burst BE traffic

8 for streaming/voice traffic

8 for streaming/voice traffic

8

Setting Tradeoff: : if the parameter is set too low, it gives the UE the quicker transition from the short cycle to long cycle, which will cause low power consumption at the UE, however it might delay the information delivery to the UE. If the parameter is set too high it gives the UE the slower transition from the short to long cycle, which will cause more power consumption but with faster information delivery to the UE.

9

Dependencies/Constraints: This parameter should be optimized together with shortDRX-Cycle.

4 5 6 7

10

Traceability: TS 36.321 Sect 5.7, TS36.331 Sect 6.3.2

11

RRC Message Structure:

12 13

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  drx-Config  shortDRX  drxShortCycleTimer

15

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  drxConfig  shortDRX  drxShortCycleTimer

16

Notes: None.

14

17 18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

284

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

10.8 Semi Persistent Scheduling

2

When Semi-Persistent Scheduling is enabled by RRC, the following information is provided:

3

Released - For Current Employee/Consultant Use Only

MAC Parameters

4

-

5 6 7 8 9 10 11 12 13 14 15

-

Semi-Persistent Scheduling C-RNTI; Downlink Semi-Persistent Scheduling interval semiPersistSchedIntervalDL and number of configured HARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is enabled for the downlink; Uplink Semi-Persistent Scheduling interval semiPersistSchedIntervalUL and number of empty transmissions before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the uplink;

When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or configured assignment shall be discarded. RRCConnectionSetup message is used to configure downlink/uplink Semi-Persistent Scheduling while RRCConnectionReconfiguration message can be used to modify the configuration in case for example codec rate of scheduled application has changed.

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

285

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

MAC Parameters

1

10.8.1 semiPersistSchedC-RNTI

2

Definition: It specifies which UE the eNB will start the semi-persistent scheduling for.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

C-RNTI

Recommended

NA

Engineering Units

C-RNTI

3

Setting Tradeoff: None.

4

Dependencies/Constraints: None.

5

Traceability: TS 36.321 Sect 5.10, TS36.331 Sect 6.3.2

6

RRC Message Structure:

7

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  semiPersistSchedC-RNTI

8

Notes: None.

9 10

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

286

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5

MAC Parameters

10.8.2 semiPersistSchedIntervalDL Definition: It is the semi-persistent scheduling interval in downlink. After a Semi-Persistent downlink assignment is configured, the UE will consider that the DL assignment recurs with an interval equal to semiPersistSchedIntervalDL. On other words, it is is the periodicity of semi-persistent scheduling signaled via RRC. IE Value

Allowed Range

Recommended

ENUMERATED {sf10, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf320, sf640}

Engineering Units

Unit: Subframe 10, 20, 32, 40, 64, 80, 128, 160, 320, 640

Appropriate setting depends on the QoS requirements during the SPS scheduling; for instance, set it to 20-40ms for VoLTE.

10

Setting Tradeoff: it is based on the upper layer application needs. If the configuration of this parameter is aggressive (interval is smaller than the application needs), then the DL resources are wasted. If the configuration was conservative (interval is larger than the applicaion needs), then it incurs the delay for data transmission on the DL and eventually data might be dropped from the buffer.

11

Dependencies/Constraints: CDRX Settings.

12

Traceability: TS 36.321 Sect 5.10, TS36.331 Sect 6.3.2

13

RRC Message Structure:

6 7 8 9

14 15

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  sps-ConfigDL  semiPersistSchedIntervalDL

17

RRCConnectionReconfiguration radioResourceConfigDedicated ConfigDL semiPersistentSchedIntervalDL

18

Notes:

16

19 20

21 22

23 24

SPS-Config SPS-

After a Semi-Persistent downlink assignment is configured, the UE shall consider that the assignment recurs in each subframe for which: - (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * semiPersistSchedIntervalDL] modulo 10240, for all N>0. Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the configured downlink assignment were (re-)initialised.

25 26

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

287

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

MAC Parameters

1

10.8.3 numberOfConfSPS-Processes

2

Definition: The number of configured downlink HARQ processes for Semi-Persistent Scheduling.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

Recommended

INTEGER (1..8)

Engineering Units

Unit: INTEGER 1..8

Appropriate setting depends on the QoS requirements during the SPS scheduling. For VoLTE, set it to 1-4.

5

Setting Tradeoff: A larger number of HARQ processes determines higher throughput during semipersistent scheduling but higher UE memory processing. A smaller number of HARQ processes reduce UE memory requirements at the expense of throughput during semi persistent scheduling.

6

Dependencies/Constraints: CDRX Settings.

7

Traceability: TS 36.321 Sect 5.10, TS36.331 Sect 6.3.2

8

RRC Message Structure:

3 4

9 10 11 12

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  sps-ConfigDL  numberOfConfSPS-Processes RRCConnectionReconfiguration radioResourceConfigDedicated SPS-Config SPSConfigDL numberOfConfSPS-Processes

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

288

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

MAC Parameters

10.8.4 n1-PUCCH-AN-PersistentList (1)

Definition: Determines the value of 𝑛𝑃𝑈𝐶𝐶𝐻 , the resource index to be used for reporting the ACK/NACK.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range Recommended

SEQUENCE (SIZE (1..4)) OF INTEGER (0..2047)

Unit: INTEGER

UE specific configuration

TBD

4

Setting Tradeoff: UE specific configuration.

5

Dependencies/Constraints: CDRX Settings.

6

Traceability: TS 36.321 Sect 5.10, TS36.331 Sect 6.3.2

7

RRC Message Structure:

8 9

Engineering Units

Range: 0 .. 2047

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  sps-ConfigDL  n1PUCCH-AN-PersistentList

11

RRCConnectionReconfiguration  radioResourceConfigDedicated  SPS-Config  sps-ConfigDL  n1-PUCCH-AN-PersistentList

12

Notes: None.

10

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

289

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

MAC Parameters

10.8.5 semiPersistSchedIntervalUL Definition: Uplink Semi-Persistent Scheduling interval. The UE considers the grant recurs with periodicity equal to the semiPersistSchedIntervalUL. IE Value

Allowed Range

ENUMERATED {sf10, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf320, sf640}

Recommended

Appropriate setting depends on the QoS requirements during the SPS scheduling; for instance, set it to 2040ms for VoLTE.

Engineering Units

Unit: Subframe 10, 20, 32, 40, 64, 80, 128, 160, 320, 640

8

Setting Tradeoff: It is based on the upper layer application needs. If the configuration of this parameter is aggressive (interval is smaller than the application needs), then the UL resources are wasted. If the configuration was conservative (interval is larger than the applicaion needs), then it incurs the delay for data transmission on the UL and eventually data might be dropped from the buffer.

9

Dependencies/Constraints: CDRX Settings.

4 5 6 7

10

Traceability: TS 36.321 Sect 5.10, TS36.331 Sect 6.3.2

11

RRC Message Structure:

12 13

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  sps-ConfigUL  semiPersistSchedIntervalUL

15

RRCConnectionReconfiguration radioResourceConfigDedicated SPS-Config SPSConfigUL semiPersistentSchedIntervalUL

16

Notes:

17

After a Semi-Persistent Scheduling uplink grant is configured, the UE shall:

14

18

19 20 21

22 23

-

consider that the grant recurs in each subframe for which:

- (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * semiPersistSchedIntervalUL + Subframe_Offset * (N modulo 2)] modulo 10240, for all N>0. Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the configured uplink grant were (re-)initialised.

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

290

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

MAC Parameters

10.8.6 implicitReleaseAfter Definition: When UE is in UL SPS, the implicitReleaseAfter is the number of consecutive new MAC PDUs each containing zero MAC SDUs from the Multiplexing and Assembly entity of the UE on the Semi-Persistent Scheduling resource before an immediate clear of the uplink grant. IE Value

Allowed Range

ENUMERATED {e2, e3, e4, e8}

Recommended

Appropriate setting depends on the silent interval for the application using SPS. For instance, set it to e8 for VoLTE

Engineering Units

2, 3, 4, 8 transmissions

8

Setting Tradeoff: If the parameter is set too low, it might trigger a false alarm to clear the UL grant ahead of time. In other words, this may cause the UE to release the SPS resource when it is not supposed to. If the parameter is set too high, it could reduce the efficiency on the uplink, since too many UL allocations are wasted every time SPS resource is scheduled.

9

Dependencies/Constraints: CDRX Settings.

5 6 7

10

Traceability: TS 36.321 Sect 5.10, TS36.331 Sect 6.3.2

11

RRC Message Structure:

12 13

rrcConnectionSetup  radioResourceConfigDedicated  SPS-Config  sps-ConfigUL  implicitReleaseAfter

15

RRCConnectionReconfiguration radioResourceConfigDedicated SPS-Config SPSConfigUL implicitReleaseAfter

16

Notes:

14

17 18 19

The UE shall clear the configured uplink grant immediately after implicitReleaseAfter number of consecutive new MAC PDUs each containing zero MAC SDUs have been provided by the Multiplexing and Assembly entity, on the Semi-Persistent Scheduling resource.

20 21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

291

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

LTE Parameter Setting Guidelines

MAC Parameters

1

10.9 Other MAC Layer Parameters

2

10.9.1 ttiBundling

3

Definition: Determine if the TTI bundling is enabled or disabled. IE Value Allowed Range

Recommended

Engineering Units

BOOLEAN

TRUE - enabled, FALSE – disabled

Default is FALSE

enabled

Enable it if close to cell edge for VOLTE call.

7

Setting Tradeoff: If the parameter is set to TRUE, the TTI bundling is enabled. The reception of Uplink transmissions in coverage limited scenarios can be improved. If the parameter is set to FALSE, the TTI bundling is disabled. The reception of Uplink transmissions in coverage limited scenarios may be affected.

8

Dependencies/Constraints: None.

9

Traceability: TS 36.321 Sect 5.4.2, TS36.331 Sect 6.3.2

4 5 6

10 11 12

RRC Message Structure: rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig ul-SCH-Config  ttiBundling

14

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig ul-SCHConfig  ttiBundling

15

Notes: None.

13

16 17

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

292

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5

MAC Parameters

10.9.2 timeAlignmentTimerDedicated Definition: It is a configurable timer (by eNB) used by the UE to determine how long it’s considered uplink time aligned. The timer will be restarted every time the UE receives a timing advance command from eNB. If timer expires, the UE is considered out of sync on the UL, hence UE is prohibited from transmitting on the UL. IE Value

Engineering Units Unit: ms

Allowed Range

ENUMERATED {sf500, sf750, sf1280, sf1920, sf2560, sf5120, sf10240, infinity}

Recommended

sf2560 – sf5120

2560 - 5120 ms

RANGE: 500, 750, 1280, 1920, 2560, 5120, 10240, infinity

11

Setting Tradeoff: if the parameter is set too low, the UE has to be synchronized frequently (every 500 ms) otherwise it is considered out of sync. This leads to the higher overhead on the DL due to excessive transmission of Timing Advance command to the UE. However UE is more accurately synchronized on the uplink. If the parameter is set too high, it leads to the less overhead on the DL, but UE will be less accurately synchronized, and UE transmission on the UL may not be decoded properly.

12

Dependencies/Constraints: None.

13

Traceability: TS 36.321 Sect 5.2, TS36.331 Sect 6.3.2

14

RRC Message Structure:

6 7 8 9 10

15 16

rrcConnectionSetup  radioResourceConfigDedicated  mac-MainConfig  timeAlignmentTimerDedicated

18

RRCConnectionReconfiguration  radioResourceConfigDedicated  mac-MainConfig  timeAlignmentTimerDedicated

19

Notes:

17

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

293

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

2

11 Radio Link Control (RLC) Parameter Settings

3

Chapter 11: Table of Contents

4

11.1 Acknowledged Mode (AM)................................................................................................................ 295

5

11.1.1 t-PollRetransmit ................................................................................................................................ 296

6

11.1.2 pollPDU .............................................................................................................................................. 297

7

11.1.3 pollByte............................................................................................................................................... 298

8

11.1.4 maxRetxThreshold ............................................................................................................................ 299

9

11.1.5 t-Reordering(RLC-AM) .................................................................................................................... 300

10

11.1.6t-StatusProhibit................................................................................................................................... 301

11

11.2 Unacknowledged Mode (UM) ........................................................................................................... 302

12

11.2.1sn-FieldLength (UL-UM-RLC/DL-UM-RLC)................................................................................ 302

13

11.2.2 t-Reordering (DL-UM-RLC) ............................................................................................................ 304

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

294

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

2

The Radio Link Control (RLC) parameters provide a set of timers and constants to support the AM (Acknowledged Mode) which can detect the lost PDU and request the re-transmission.

3

Besides, UM (Un Acknowledged Mode) is supported for delivering the PDUs in sequence.

1

4

Released - For Current Employee/Consultant Use Only

Radio Link Control (RLC) Parameter Settings

5 6 7 8

The TM (Transparent Mode) is supported as transparent pass through between the PDCP and the MAC layers. That is, there is no RLC header added and purely data is transferred through the RLC layer. RLC parameters, particularly for the AM and UM modes, are configured by the network through dedicated RRC messages during radio bearer setup procedure.

9

10

11.1 Acknowledged Mode (AM)

11

The AM mode can provide the following functions:

12 13 14 15 16

1)

Polling that allows the sender to request the status report (i.e. STATUS PDU) from the receiver.

2) Status report that allows the receiver to acknowledge the received RLC PDU and report the missing RLC PDU or part of the PDU. 3) Retransmission in which the sender can retransmit the missing RLC PDU or part of the RLC PDU upon receiving the STATUS PDU.

18

4) In sequence delivery by buffering and reordering the received PDUs which may be out of the order in receiving.

19

5)

17

Segmentation that allows the RLC SDU to be fragmented in multiple RLC PDUs.

21

6) Re-segmentation that allows the RLC SDU to be retransmitted in new segmentation (i.e. different bytes from the original RLC PDU) according to the received STATUS PDU.

22

7)

20

23

Concatenation that allows one RLC PDU to carry multiple RLC SDUs.

This AM is mainly used for error sensitive and delay tolerant service.

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

295

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Radio Link Control (RLC) Parameter Settings

11.1.1 t-PollRetransmit Definition: This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll if there is no STATUS report received. That is, only upon expiry of t-PollRetransmit, the transmitting side of an AM RLC entity can include a poll in a RLC data PDU. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: ms

{ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms105, ms110, ms115, ms120, ms125, ms130, ms135, ms140, ms145, ms150, ms155, ms160, ms165, ms170, ms175, ms180, ms185, ms190, ms195, ms200, ms205, ms210, ms215, ms220, ms225, ms230, ms235, ms240, ms245, ms250, ms300, ms350, ms400, ms450, ms500}

Range: 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 105, 110, 115, 120, 125, 130, 135, 140, 145, 150, 155, 160, 165, 170, 175, 180, 185, 190, 195, 200, 205, 210, 215, 220, 225, 230, 235, 240, 245, 250, 300, 350, 400, 450, 500

8*( max number of HARQ retransmissions -1) + 10ms margin

8

Setting Tradeoff: If the parameter is set too large, the delay to retransmit a poll (and recovery the lost RLC PDU) can be slow, therefore it may affect the latency of data delivery. If the parameter is set too low, it can retransmit unnecessary poll (and STATUS report) and consume more air interface bandwidth for retransmitting the poll or processing at the RLC receiving entity.

9

Dependencies/Constraints: None.

5 6 7

10

Traceability: TS36.322 Sect. 5.2.2.3, TS36.331 Sect. 6.3.2

11

RRC Message Structure:

12



RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am ul-AM-RLC  t-PollRetransmit



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config  am ul-AM-RLC  t-PollRetransmit



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am ul-AM-RLC  t-PollRetransmit

13 14 15 16 17 18

Notes:

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

296

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Radio Link Control (RLC) Parameter Settings

11.1.2 pollPDU Definition: This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollPDU PDUs. IE Value

Engineering Units

ENUMERATED

Unit: PDU

Allowed Range

(p4, p8, p16, p32, p64, p128, p256, pInfinity)

Range: 4, 8, 16, 32, 64, 128, 256, Infinity

Recommended

32 for SRB and DRB

32 PDUs

6

Setting Tradeoff: If the parameter is set too large, the delay to transmit a poll and recover the lost RLC PDU can be slow, thereby it may affect the latency of data delivery. If the parameter is set too small, it can transmit poll too frequently and waste the bandwidth or processing.

7

Dependencies/Constraints: pollByte, t-Reordering (RLC-AM)

8

Traceability: TS36.322 Sect. 5.2.2, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

4 5

10



RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am ul-AM-RLC  pollPDU



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config  am ul-AM-RLC  pollPDU



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am ul-AM-RLC  pollPDU

11 12 13 14 15 16

Notes:

17

A setting of Infinity deactivates triggering a poll due to the number of PDUs.

18 19 20

Assume that the air-interface has 1% error rate with HARQ, and therefore there can be one lost PDU per 100 PDUs, which requires a poll. The pollPDU parameter can be set to 32 to allow more polls or higher error rate.

21

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

297

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Radio Link Control (RLC) Parameter Settings

11.1.3 pollByte Definition: This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollByte bytes. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: KBytes

(kB25, kB50, kB75, kB100, kB125, kB250, kB375, kB500, kB750, kB1000, kB1250, kB1500, kB2000, kB3000, kBinfinity)

Range: 25, 50, 75, 100, 125, 250, 375, 500, 750, 1000, 1250, 1500, 2000, 3000, kBinfinity

kBinfinity if pollPDU is enabled 32*RLC PDU Size otherwise

7

Setting Tradeoff: If the parameter is set too large, the delay to transmit a poll and recover the lost RLC PDU can be slow, thereby it may affect the latency of data delivery. If the parameter is set too small, it can transmit poll (and STATUS report) too frequently and waste the bandwidth or processing.

8

Dependencies/Constraints: None.

9

Traceability: TS36.322 Sect. 5.2.2, TS36.331 Sect. 6.3.2

4 5 6

10 11

RRC Message Structure: •

RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am ul-AM-RLC  pollBytes



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config  am ul-AM-RLC  pollBytes



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am ul-AM-RLC  pollBytes

12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

Notes: A setting of Infinity deactivates triggering a poll due to the number of bytes in the transmitting PDUs. Typically, poll triggered by number of PDUs (i.e. pollPDU) can provide proper trigger of retransmission. However, if the RLC PDU size is large (and small bandwidth allocated by eNB, high transmission error), then poll triggered by the number of bytes can be very useful. It can allow faster response time in retransmission by reacting to the number of bytes being sent especially when the large-size PDU can be re-segmented, which requires a few transmissions to complete sending a whole PDU in retransmission. Assume that the MAC layer has 1% error rate (including HARQ), then there can be one lost PDU per 100 PDUs, which requires a poll. Therefore pollByte can be set to 32 multiplied by the PDU packet size to trigger a poll.

28

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

298

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Radio Link Control (RLC) Parameter Settings

11.1.4 maxRetxThreshold Definition: This parameter is used by the transmitting side of each AM RLC entity to limit the number of retransmissions of an AM PDU. IE Value

Allowed Range

Engineering Units

ENUMERATED

Unit: Number of retransmissions

(t1, t2, t3, t4, t6, t8, t16, t32)

Range: 1, 2, 3, 4, 6, 8, 16, 32

16 for DRB BE traffic. Recommended

32 for DRB IMS signaling 32 for SRB

6

Setting Tradeoff: If the parameter is set too low, the AM RLC transmitting entity cannot recover the error on the over the air transmission. If the parameter is set too high, the AM RLC transmitting entity can continue to retransmit and create more air interface bandwidth overhead.

7

Dependencies/Constraints: None.

8

Traceability: TS36.322 Sect. 5.2.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

4 5

10



RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config am ul-AM-RLC  maxRetxThreshold



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config  am or um--Bi-Directional ul-AM-RLC  maxRetxThreshold



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am or um--Bi-Directional ul-AM-RLC  maxRetxThreshold

11 12 13 14 15 16 17

Notes:

21

Assume that HARQ can allow for 1~5% packet error rate. Then, 3 retransmissions can achieve very low packet error rate in case of independent transmission error. Doubling the number of retransmissions can account for additional margin when the packet transmission error is correlated and the RLC PDU re-segmented for retransmission.

22

For SRB, set it to higher allowed number of retransmissions can give SRB more protections.

18 19 20

23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

299

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Radio Link Control (RLC) Parameter Settings

11.1.5 t-Reordering(RLC-AM) Definition: This timer is used by the receiving side of an AM RLC entity in order to detect loss of RLC PDUs in the lower layer. The timer starts when there is a higher sequence PDU received than the expected sequence number. When the timer expires, it can trigger STATUS report in AM RLC. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: ms

(ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms110, ms120, ms130, ms140, ms150, ms160, ms170, ms180, ms190, ms200)

Range: 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200

8*( max number of HARQ retransmissions -1) + 10ms margin

7

Setting Tradeoff: If the parameter is set too large, the delay to recover the out of sequence PDU can be slow due to slowly sending the STATUS report. If the parameter is set too small, the air interface bandwidth for STATUS PDU and processing for receiving STATUS report can be too high.

8

Dependencies/Constraints: None.

9

Traceability: TS36.322 Sect. 5.1.2.2, 5.1.3.2, TS36.331 Sect. 6.3.2

5 6

10 11

RRC Message Structure: •

RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config am dl-AM-RLC  t-Reordering



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config  am dl-AM-RLC t-Reordering



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am dl-AM-RLC t-Reordering

12 13 14 15 16 17

Notes:

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

300

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Radio Link Control (RLC) Parameter Settings

11.1.6 t-StatusProhibit Definition: This timer is used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU. That is, at most one STATUS PDU per t-StatusProhibit time duration. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: ms

(ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms105, ms110, ms115, ms120, ms125, ms130, ms135, ms140, ms145, ms150, ms155, ms160, ms165, ms170, ms175, ms180, ms185, ms190, ms195, ms200, ms205, ms210, ms215, ms220, ms225, ms230, ms235, ms240, ms245, ms250, ms300, ms350, ms400, ms450, ms500)

Range: 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 105, 110, 115, 120, 125, 130, 135, 140, 145, 150, 155, 160, 165, 170, 175, 180, 185, 190, 195, 200, 205, 210, 215, 220, 225, 230, 235, 240, 245, 250, 300, 350, 400, 450, 500

DRB: ms10 SRB: ms0

7

Setting Tradeoff: If the parameter is set too large, the delay to retransmit the lost PDU or out of sequence PDU can be large. If the parameter is set too small, the bandwidth for STATUS PDU processing for receiving STATUS PDU can be too high.

8

Dependencies/Constraints:

5 6

9



10

The parameters t-StatusProhibit and t-PollRetransmit in RLC layer should be set jointly such that if t-StatusProhibit can be smaller or equal to t-PollRetransmit.

11

Traceability: TS36.322 Sect. 5.2.3, TS36.331 Sect. 6.3.2

12

RRC Message Structure:

13



RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config am dl-AM-RLC  t-StatusProhibit



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config  am dl-AM-RLC  t-StatusProhibit



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  am dl-AM-RLC t-StatusProhibit

14 15 16 17 18 19

Notes:

20

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

301

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

11.2 Unacknowledged Mode (UM)

2

The UM mode can provide the following functions:

4

1) In sequence delivery by buffering and reordering the received PDUs which may be out of the order in receiving.

5

2)

Segmentation that allows the RLC SDU to be fragmented in multiple RLC PDUs.

6

3)

Concatenation that allows one RLC PDU to carry multiple RLC SDUs.

3

Released - For Current Employee/Consultant Use Only

Radio Link Control (RLC) Parameter Settings

7 8

The UM mode does not support retransmission (ARQ) as in the AM mode. The UM mode is mainly used for delay sensitive and error tolerant service (but still requires in sequence delivery).

9

10

11.2.1 sn-FieldLength (UL-UM-RLC/DL-UM-RLC)

11

Definition: This parameter gives the UL/DL UM SN field size in bits. IE Value

Allowed Range

ENUMERATED

Engineering Units

Range: 5, 10

(size5, size10) Recommended

size5 for voice traffic size10 for video and BE traffic

15

Setting Tradeoff: If the parameter is set to size10, the bandwidth overhead for sending the sequence number in the PDU is higher. If the parameter is set to size5, it may create the sequence wrap around problem and may cause the valid PDUs to drop due to outside the low end of the current SN window if the packet rate is very large.

16

Dependencies/Constraints:

17

Traceability: TS36.322 Sect. 7.2, TS36.331 Sect. 6.3.2

18

RRC Message Structure:

12 13 14

19



RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config um-Bi-Directional, um-Uni-Directional-UL or um-Uni-Directional-DLul-AM-RLC  sn-FieldLength



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config um-Bi-Directional, um-Uni-Directional-UL or um-UniDirectional-DLul-AM-RLC or dl-AM-RLC  sn-FieldLength



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config um-Bi-Directional, um-Uni-Directional-UL, um-Uni-Directional-DLulAM-RLC or dl-AM-RLC  sn-FieldLength

20 21 22 23 24 25 26 27 28 29 30

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

302

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

2 3

Released - For Current Employee/Consultant Use Only

4 5

Radio Link Control (RLC) Parameter Settings

Notes: The formula RLC_PDU_rate (UL or DL RLC PDU Rate) * STT (UL or DL Single Trip Time from the UE to the eNB, measured in 99 percentile, including HARQ process) can be the number of out of order PDUs being received due to HARQ. Since the UM window size for size5 is 16, the threshold equal to 8 can provide some margin.

6

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

303

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5

Radio Link Control (RLC) Parameter Settings

11.2.2 t-Reordering (DL-UM-RLC) Definition: This timer is used by the receiving side of an UM RLC entity in order to detect loss of RLC PDUs in the lower layer. The timer starts when there is a higher sequence PDU received than the expected sequence number. When the timer expires, it can deliver received PDUs to the higher layer in UM RLC. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: ms

(ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms110, ms120, ms130, ms140, ms150, ms160, ms170, ms180, ms190, ms200)

Range: 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200

8*( max number of HARQ retransmissions -1) + 10ms margin

8

Setting Tradeoff: If the parameter is set too large, the delay to delivery the received RLC SDU to the higher layer is large. If the parameter is set too low, out of sequence RLC SDUs can be more likely delivered to the higher layer.

9

Dependencies/Constraints: None.

6 7

10

Traceability: TS36.322 Sect. 5.1.2.2, 5.1.3.2, TS36.331 Sect. 6.3.2

11

RRC Message Structure:

12



RRCConnectionSetup RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config  um-Bi-Directional dl-UM-RLC  t-Reordering



RRCConnectionReconfiguration RadioResourceConfigDedicated  SRB-ToAddMod or DRB-ToAddMod RLC-Config um-Bi-Directional ul-UM-RLC  t-Reordering



RRCConnectionReestablishment RadioResourceConfigDedicated  SRB-ToAddMod RLC-Config um-Bi-Directional ul-UM-RLC  t-Reordering

13 14 15 16 17 18

Notes:

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

304

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

1

2

12 Packet Data Convergence Protocol (PDCP) Parameter Settings

3

Chapter 12: Table of Contents

4

12.1 Reliable and In Sequence Delivery .................................................................................................... 306

5

12.1.1 discardTimer...................................................................................................................................... 307

6

12.1.2 statusReportRequired ....................................................................................................................... 308

7

12.1.3 pdcp-SN-Size ..................................................................................................................................... 309

8

12.2 Robust Header Compression ............................................................................................................. 310

9

12.2.1 maxCID............................................................................................................................................... 310

10

12.2.2 profile0x0001...................................................................................................................................... 311

11

12.2.3 profile0x0002...................................................................................................................................... 312

12

12.2.4 profile0x0003...................................................................................................................................... 313

13

12.2.5 profile0x0004...................................................................................................................................... 314

14

12.2.6 profile0x0006...................................................................................................................................... 315

15

12.2.7 profile0x0101...................................................................................................................................... 316

16

12.2.8 profile0x0102...................................................................................................................................... 317

17

12.2.9 profile0x0103...................................................................................................................................... 318

18

12.2.10 profile0x0104.................................................................................................................................... 319

19

12.3 Security algorithm ............................................................................................................................... 320

20

12.3.1 cipheringAlgorithm .......................................................................................................................... 320

21

12.3.2 integrityProtAlgorithm .................................................................................................................... 321

22 23

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

305

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

2

The Packet Data Convergence Protocol (PDCP) parameters provide a set of timers and constants to allow the reliable and in sequence delivery in handover and RLF restablishment.

3

Besides, they support a set of constants for ROHC (Robust Header Compression).

1

5

Finally, the security functions performed in the PDCP layer rely on some configuration parameters to select the algorithms.

6

Parameters are configured by the network in the dedicated RRC messages.

7

12.1 Reliable and In Sequence Delivery

4

Released - For Current Employee/Consultant Use Only

Packet Data Convergence Protocol (PDCP) Parameter Settings

8 9 10 11 12 13 14 15 16 17 18

The PDCP can provide the reliable and in sequence delivery between two cells, in handover or radio link failure (RLF) re-establishment cases. This is different from the RLC layers reliable and in sequence delivery which is mainly supported within a particular cell. Therefore, after changing cell, a new RLC state machine is created on the new cell although the PDCP state still continues. This function has been supported by the RNC in UTRAN on the RLC layer in the old 3GPP releases. However, it becomes the PDCP layer function at the eNB in E-UTRAN. The reliable and in sequence delivery in PDCP is achieved by using a sequence number of each PDCP PDU. The transmitting side always buffers a PDCP PDU for some time duration, i.e. discardTimer, to allow that a local copy is retained long enough to support retransmission. When there is handover or RLF re-establishment, the receiving side should send the PDCP status report to request the eNB to retransmit the whole PDCP PDU or part of the PDCP PDU.

19

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

306

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.1.1 discardTimer Definition: This parameter is used in the transmitter to start a new timer upon reception of an SDU from upper layer. When the discardTimer expires for a PDCP SDU or the successful delivery of a PDCP SDU is confirmed by PDCP status report, the UE shall discard the PDCP SDU along with the corresponding PDCP PDU. This timer will not be restarted upon re-establishement. IE Value Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: ms

(ms50, ms100, ms150, ms300, ms500,ms750, ms1500, infinity)

Range: 50, 100, 150, 300, 500, 750, 1500, infinity

Delay budget for specific QCI + 50ms margin

8

Setting Tradeoff: If the parameter is set too large, the transmit buffer to store the PDCP PDUs can be large. If the parameter is set too small, the retransmission for the lost PDCP PDU in handover or radio link failure cannot succeed.

9

Dependencies/Constraints: None.

6 7

10

Traceability: TS36.323 Sect. 7.2, TS36.331 Sect. 6.3.2

11

RRC Message Structure:

12 13 14 15 16 17 18 19 20 21 22 23



RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod pdcp-ConfigdiscardTimer

Notes: The discard timer should be at least the delay for handover (D_HO) and Radio Link Failure recovery (D_RLF). Besides, it requires additional RTT/2 for the STATUS report to be transmitted. Up to 200% margin can be added. D_HO can be measured from the time UE receiving the RRCConnectionReconfiguration to the time UE sending RRCConnectionReconfigurationComplete message. D_RLF can be measured from the time UE detecting the N310 consecutive out of sync indications from the lower layer until the time UE sending the RRCConnectionReestablishmentComplete message. If buffering PDCP PDU in eNB is of concern, then set the discardTimer to [1~2] * [max{D_HO, D_RLF} + RTT/2].

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

307

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.1.2 statusReportRequired Definition: This parameter indicates whether or not the UE or the eNB shall send a PDCP Status Report upon re-establishment of the PDCP entity with RLC-AM configuration. IE Value

Allowed Range

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range: 1 – TRUE; 0 - FALSE

Set to TRUE if the higher layer service requires reliable data delivery and can tolerate delay.

Same as left

Otherwise, set to FALSE. Recommended

Depend on whether it supports X2 forwarding: -

TRUE - if X2 forwarding is supported FALSE if X2 forwarding is not supported

6

Setting Tradeoff: If the parameter is set to TRUE, the PDCP Status Report may incur bandwidth overhead. If the parameter is set to FALSE, it may not recover the lost packet in handover or radio link failure.

7

Dependencies/Constraints:

8

Traceability: TS36.323 [TBD3] Sect. 5.3.1, TS36.331 [TBD2] Sect. 6.3.2

9

RRC Message Structure:

4 5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod pdcp-Configrlc-AMstatusReportRequired

12

Notes:

13

The PDCP Status Report is sent once during the PDCP reestablishment. It is a new PDU.

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

308

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.1.3 pdcp-SN-Size Definition: This parameter indicates the PDCP Sequence Number length in bits, with RLC-UM DRB configuration. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit:bits

(len7bits, len12bits)

Range: 7, 12

len7bits for QCI 1 len12bits otherwise

6

Setting Tradeoff: If the parameter is set to len12bits the bandwidth overhead for sending the sequence number in is higher. If the parameter is set to len7bits, it may create the sequence wrap around problem in case of large rate of packets or long delay in handover or RLF reestablishment.

7

Dependencies/Constraints:

4 5

8



9

The parameters pdcp-SN-Size and sn-FieldLength in RLC layer should be set jointly such that if sn-FieldLength is 10 bits, then pdcp-SN-Size should be 12 bits.

10

Traceability: TS36.323 [TBD3] Sect. 6.3.2, TS36.331 [TBD2] Sect. 6.3.2

11

RRC Message Structure:

12



13 14

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod pdcp-Configrlc-UMpdcp-SN-Size

Notes:

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

309

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4 5 6 7 8 9

10 11 12 13 14

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2 Robust Header Compression The purpose of Robust Header Compression (ROHC) is to reduce the IP packet header overhead. The large IP packet header is especially a problem for the small IP packet size. For example, the overhead of IP, UDP, and RTP is 40 bytes for IPv4 or 60 bytes for IPv6. For VoIP this corresponds to more than 60% of the total amount of data sent. Such large overheads are problematic for wireless systems with limited bandwidth. ROHC compresses these 40 bytes or 60 bytes of overhead typically into only 1 or 3 bytes by placing a compressor before the link, and a decompressor after that link. The compressor converts the large overhead to only a few bytes, while the decompressor does the opposite.

12.2.1 maxCID Definition: This parameter indicates the value of the MAX_CID parameter for the ROHC channel as defined in RFC 4995. That is, maxCID indicate the highest CID (Context Identifier) number to be used by the compressor and this value represents an agreement by the decompressor to provide sufficient memory resources to host at least MAX_CID+1 contexts. IE Value

Allowed Range Recommended

Engineering Units

INTEGER

Unit: CIDs

(1..16383)

Range: 1, …, 16383

15

17

Setting Tradeoff: If the parameter is set too large, the transmit buffer to store the ROHC context can be large. If the parameter is set too small, it cannot support required number of IP flows of header compression.

18

Dependencies/Constraints: None.

19

Traceability: TS36.323 [Sect. 5.5.3, TS36.331 Sect. 6.3.2

20

RRC Message Structure:

15 16

21 22 23



RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompressionrohcmaxCID

Notes: None.

24

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

310

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.2 profile0x0001 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0001, i.e. header compression algorithm RTP/UDP/IP specified in RFC 3095, RFC 4815, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

Set to TRUE if higher layer is VoIP service and capacity is concerned;

Same as left.

Otherwise, set to FALSE.

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is high. If the parameter is set to FALSE, then ROHC profile 0x0001 is not supported and IP overhead can be large.

7

Dependencies/Constraints: None.

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0001

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

14

If both profile0x0001 and profile0x0101 are supported, then only profile0x0101 is supported.

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

311

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.3 profile0x0002 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0002, i.e. header compression algorithm UDP/IP specified in RFC 3095, RFC 4815, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

Set to TRUE if higher layer is VoIP service and capacity is concerned

Same as left

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is high. If the parameter is set to FALSE, then ROHC profile 0x0002 is not supported and IP overhead can be large.

7

Dependencies/Constraints: None

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0001

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

14

If both profile0x0002 and profile0x0102 are supported, then only profile0x0102 is supported.

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

312

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.4 profile0x0003 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0003, i.e. header compression algorithm ESP/IP specified in RFC 3095, RFC 4815, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

FALSE unless there are large amount of small size of ESP/IP packets and capacity is concerned.

Same as left

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is higher. If the parameter is set to FALSE, then ROHC profile 0x0003 is not supported and IP overhead can be large.

7

Dependencies/Constraints:

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 [] Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0003

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

14

If both profile0x0003 and profile0x0103 are supported, then only profile0x0103 is supported.

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

313

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.5 profile0x0004 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0004, i.e. header compression algorithm IP specified in RFC 3095, RFC 4815, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

FALSE unless there are large amount of small size of IP packets and capacity is concerned.

Same as left

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is higher. If the parameter is set to FALSE, then ROHC profile 0x0004 is not supported and IP overhead can be large.

7

Dependencies/Constraints:

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0004

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

14

If both profile0x0004 and profile0x0104 are supported, then only profile0x0104 is supported.

15

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

314

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.6 profile0x0006 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0006, i.e. header compression algorithm TCP/IP specified in RFC 4996, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

FALSE unless there are large amount of small size of TCP/IP packets and capacity is concerned.

Same as left

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is higher. If the parameter is set to FALSE, then ROHC profile 0x0006 is not supported and IP overhead can be large.

7

Dependencies/Constraints:

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0006

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

14

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

315

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.7 profile0x0101 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0101, i.e. header compression algorithm RTP/UDP/IP specified in RFC 5225, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

FALSE

Same as left.

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is high. If the parameter is set to FALSE, then ROHC profile 0x0101 is not supported and IP overhead can be large.

7

Dependencies/Constraints:

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0001

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

16

ROHC 0x0101 is an improved version of ROHC 0x0001, such as in tolerance of reordering, compressing an arbitrary number of levels of IP headers, etc. while achieving the compression efficiency at least equivalent to ROHC 0x0001.

17

If both profile0x0001 and profile0x0101 are supported, then only profile0x0101 is supported.

14 15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

316

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.8 profile0x0102 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0102, i.e. header compression algorithm UDP/IP specified in RFC 5225, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

FALSE unless there are large amount of small size of UDP/IP packets and capacity is concerned.

Same as left

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is high. If the parameter is set to FALSE, then ROHC profile 0x0102 is not supported and IP overhead can be large.

7

Dependencies/Constraints:

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0001

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

16

ROHC 0x0102 is an improved version of ROHC 0x0002, such as in tolerance of reordering, compressing an arbitrary number of levels of IP headers, etc. while achieving the compression efficiency at least equivalent to ROHC 0x0002.

17

If both profile0x0002 and profile0x0102 are supported, then only profile0x0102 is supported.

14 15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

317

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.9 profile0x0103 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0103, i.e. header compression algorithm ESP/IP specified in RFC 5225, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

FALSE unless there are large amount of small size of ESP/IP packets and capacity is concerned.

Same as left

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is higher. If the parameter is set to FALSE, then ROHC profile 0x0103 is not supported and IP overhead can be large.

7

Dependencies/Constraints:

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0003

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

16

ROHC 0x0103 is an improved version of ROHC 0x0003, such as in tolerance of reordering, compressing an arbitrary number of levels of IP headers, etc. while achieving the compression efficiency at least equivalent to ROHC 0x0003.

17

If both profile0x0003 and profile0x0103 are supported, then only profile0x0103 is supported.

14 15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

318

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2 3

Released - For Current Employee/Consultant Use Only

4

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.2.10 profile0x0104 Definition: This parameter is used by both compressor and decompressor in both UE and E-UTRAN. The field indicates whether or not the ROHC profile 0x0104, i.e. header compression algorithm IP specified in RFC 5225, is supported. IE Value

Engineering Units

BOOLEAN

Unit:

(0, 1)

Range:

Allowed Range

1-TRUE indicates that the profile is supported; 0-FALSE

Recommended

FALSE unless there are large amount of small size of IP packets and capacity is concerned.

Same as left

6

Setting Tradeoff: If the parameter is set to TRUE, the processing is higher. If the parameter is set to FALSE, then ROHC profile 0x0104 is not supported and IP overhead can be large.

7

Dependencies/Constraints:

8

Traceability: TS36.323 Sect. 5.5.1, TS36.331 Sect. 6.3.2

9

RRC Message Structure:

5

10



11

RRCConnectionReconfigurationRadioResourceConfigDedicatedDRB-ToAddMod PDCP-ConfigheaderCompression rohcprofilesprofile0x0004

12

Notes:

13

Note that profile0x0000 - no compression is always supported.

16

ROHC 0x0104 is an improved version of ROHC 0x0004, such as in tolerance of reordering, compressing an arbitrary number of levels of IP headers, etc. while achieving the compression efficiency at least equivalent to ROHC 0x0004.

17

If both profile0x0004 and profile0x0104 are supported, then only profile0x0104 is supported.

14 15

18

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

319

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1

12.3 Security algorithm

2

12.3.1 cipheringAlgorithm

3

Released - For Current Employee/Consultant Use Only

Packet Data Convergence Protocol (PDCP) Parameter Settings

4

Definition: This parameter is used by the network to configure the ciphering algorithm used in the PDCP layer to support higher layer including UP (User Plane) and RRC, on a per-UE basis. IE Value

Engineering Units

ENUMERATED

Unit:

(eea0, eea1, eea2)

Range:

Allowed Range

eea0: null ciphering eea1: SNOW 3G based algorithm eea2: AES based algorithm

Recommended

eea1 or eea2.

Same as left

6

Setting Tradeoff: If the parameter is set to eea0, the processing is reduced but the packet is not ciphered. If the parameter is set to eea1 or eea2, the packet is ciphered but the processing is incurred.

7

Dependencies/Constraints: None.

8

Traceability: TS36.331 [TBD2] Sect. 6.3.3

9

RRC Message Structure:

5

10 11 12



SecurityModeCommand securityModeCommand-r8  securityConfigSMC  securityAlgorithmConfig  cipheringAlgorithm

Notes: None.

13

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

320

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

1 2

Released - For Current Employee/Consultant Use Only

3

Packet Data Convergence Protocol (PDCP) Parameter Settings

12.3.2 integrityProtAlgorithm Definition: This parameter is used by the network to configure the integrity protection algorithm used in the PDCP layer to support higher layer including RRC, on a per-UE basis. IE Value

Allowed Range

Engineering Units

ENUMERATED

Unit:

(eia1, eia2)

Range: eea1: SNOW 3G based algorithm eea2: AES based algorithm

Recommended

eia1 or eia2.

4

Setting Tradeoff: None.

5

Dependencies/Constraints: None.

6

Traceability: TS36.331 [TBD2] Sect. 6.3.3

7

RRC Message Structure:

8 9 10



Same as left

SecurityModeCommand securityModeCommand-r8  securityConfigSMC  securityAlgorithmConfig  integrityProtAlgorithm

Notes: None.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

321

Confidential and Proprietary – Qualcomm Global Services, Inc.

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT

Released - For Current Employee/Consultant Use Only

13 RRC Timers and Parameters

Chapter 13: Table of Contents 13.1 Paging Timers ....................................................................................................................................... 323 13.1.1 defaultPagingCycle ........................................................................................................................... 323 13.1.2 nB ......................................................................................................................................................... 324 13.2 RRC Connection Establishment Related Timers ............................................................................. 326 13.2.1 T300 ..................................................................................................................................................... 326 13.2.2 T301 ..................................................................................................................................................... 327 13.3 RLF Related Timers ............................................................................................................................. 328 13.3.1 T310 ..................................................................................................................................................... 329 13.3.2 N310 .................................................................................................................................................... 330 13.3.3 N311 .................................................................................................................................................... 332 13.3.4 T311 ..................................................................................................................................................... 333 13.4 Access Barring Related Timers and Parameters .............................................................................. 334 13.4.1 T302 ..................................................................................................................................................... 334 13.4.2 T303 ..................................................................................................................................................... 335 13.4.3 T305 ..................................................................................................................................................... 335 13.4.4 ac-BarringTime .................................................................................................................................. 336 13.4.5 ac-BarringFactor ................................................................................................................................ 337 13.4.6 ac-BarringForSpecialAC ................................................................................................................... 338 13.5 Cell Reselection and Handover Related Timers .............................................................................. 339 13.5.1 T304 ..................................................................................................................................................... 339 13.5.2 T320 ..................................................................................................................................................... 340 13.5.3 T321 ..................................................................................................................................................... 341

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

322

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.1 Paging Timers

Released - For Current Employee/Consultant Use Only

13.1.1 defaultPagingCycle Definition: Defines periodicity of the paging occasion for a UE in idle state. IE Value Allowed Range

Recommended

ENUMERATED (rf32, rf64, rf128, rf256)

Engineering Units Unit: ms Range: 320, 640, 1280, 2560

CSFB – rf128 (or match the paging cycle of CS serving RAT) rf256 (if UE is capable of triggering to request lower paging cycle)

Setting Tradeoff: If the parameter is set too low, UE stand-by time decreases. If the parameter is set too high, mobile-terminated call-setup latency increases. Initially LTE networks will not support voice over LTE services. Setting large defaultpagingcycle value will improve battery life performance. Delays introduced by longer paging cycle will not be perceived by users. If CSFB is supported lower setting of 1.28s is recommended. Dependencies/Constraints: The parameter nB should be optimized jointly. Traceability: TS36.304 Sect 7, TS36.331 Sect 6.3.2 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonPCCH Config  defaultPagingCycle rrcConnectionReconfiguration  mobilityControlInfoRadioResourceConfigCommonPCCH Config defaultPagingCycle Notes: The DRX periodicity in idle state is determined by the shortest of the UE specific DRX value, if allocated by upper layers, and a defaultPagingCycle broadcast in system information. If UE specific DRX is not configured by upper layers, the defaultPagingCycle value is applied.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

323

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.1.2 nB Definition: Defines paging frame (PF) and paging occasion (PO).

Released - For Current Employee/Consultant Use Only

IE Value Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: ms

(fourT, twoT, oneT, halfT, quarterT, oneEighthT, oneSixteenthT,oneThirtySecondT)

Range: Multiple of defaultPaging cycle

oneT to allow every system frame within the paging cycle as possible paging frame. For high load, set it to large value.

Setting Tradeoff: If the parameter is set too low (< oneT), fewer system frames within the paging cycle can be used as a paging frame. Also the number of subframes available for page occasion within the paging frame decreases. If the cell is heavily loaded probability of paging occasion collision would increase. eNodeB processing may increase due to paging retransmission. If the parameter is set too high (>= oneT), every system frame within the paging cycle will be available as a paging frame. Also the number of subframes within the paging frame used for the page occasion increases. It reduces the possibility of page collision and reduces eNodeB proccessing. Dependencies/Constraints: The parameter defaultpagingCycle to be optimized jointly. Traceability: TS36.304 Sect 7, TS36.331 Sect 6.3.2 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonPCCH Config nB rrcConnectionReconfiguration  mobilityControlInfoRadioResourceConfigCommonPCCH Config  nB Notes: When UE enters the DRX state, the UE needs to monitor only one paging occasion (PO) per DRX cycle. The paging frame (PF) and the PO that UE needs to monitor are function of the IMSI, paging cycle and parameter nB. PF is given by following equation: SFN mod T= (T div N)*(UE_ID mod N) -

T: paging cycle

- nB: 4T, 2T, T, T/2, T/4, T/8, T/16, T/32. - N: min(T,nB) - UE_ID: IMSI mod 1024. 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

324

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

Index i_s pointing to PO from subframe pattern will be derived from following calculation:

Released - For Current Employee/Consultant Use Only

i_s = floor(UE_ID/N) mod Ns - Ns: max(1,nB/T) Subframe that carry PO for possible values of Ns are given in table below Ns 1 2 4

80-W3835-1 Rev. A

PO when i_s=0 9 4 0

PO when i_s=1 N/A 9 4

PO when i_s=2 N/A N/A 5

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

PO when i_s=3 N/A N/A 9

325

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.2 RRC Connection Establishment Related Timers

Released - For Current Employee/Consultant Use Only

13.2.1 T300 Definition: Maximum time from transmission of RRC Connection Request message to reception of RRC Connection Setup message. IE Value

Engineering Units

ENUMERATED

Unit: ms

Allowed Range

(ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}

Range: 100, 200, 300, 400, 600, 1000, 1500, 2000

Recommended

ms600

600 ms

Setting Tradeoff: This timer defines the duration that the UE should wait for an RRC Connection Setup/Reject. If set too low, the UE may stop prematurely and there may not be sufficient time to complete Contention Resolution. If set too high, the UE may be waiting too long to start re-try mechanism leading to longer call setup duration. Dependencies/Constraints: None. Traceability: TS 36.331 Sect 5.3, Sect 7.3 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonUE-TimersAndconstants t300 Notes: UE starts t300 timer at the transmission of RRCConnectionRequest. The timer is stopped at the reception of RRCConnectionSetup or RRCConnectionReject message. The timer is also stopped if cell reselection takes place or connection establishment is aborted. At the expiration of this timer UE resets MAC, releases the MAC configuration and re-establishes RLC for all RBs that are established. Lower values such as 400ms may be considered once CSFB load increases if RACH performance is adequate.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

326

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.2.2 T301

Released - For Current Employee/Consultant Use Only

Definition: Maximum time from transmission of RRC Connection Reestablishment Request message to reception of corresponding response message. IE Value

Engineering Units

ENUMERATED

Unit: ms

Allowed Range

(ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}

Range: 100, 200, 300, 400, 600, 1000, 1500, 2000

Recommended

ms1000

Setting Tradeoff: t301 should be set long enough for eNodeB to send response to RRCConnectionReestablishmnetRequest message and for UE to receive it. If the parameter is set too short UE may miss the response message. If the parameter is set too long, it will delay re-try mechanism leading to longer call setup duration. Dependencies/Constraints: None. Traceability: TS 36.331 Sect 5.3, Sect 7.3 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonUE-TimersAndconstants t301 Notes: UE starts t301 timer at the transmission of RRCConnectionReestablishmentRequest. The timer is stopped at the reception of RRCConnectionRestablishment or RRCConnectionReestablishmentReject message. The timer is also stopped if cell becomes unsuitable. At the expiration of this timer UE transitions to idle state.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

327

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

Released - For Current Employee/Consultant Use Only

13.3 RLF Related Timers Physical Layer problems are detected by monitoring the cell-specific Reference Signal (RS) and estimating the theoretical PDCCH BLER % for specific configurations defined in 36.133. In-Sync and Out-of-Sync indicators are generated based on the DRX cycle (if configured) and the thresholds Qout(10%) and Qin (2%). If the UE does not use DRX, and the Downlink radio link quality estimated during the last 200 ms period becomes worse than Qout, Layer 1 of the UE sends an Out-of-Sync indication to the higher layers within the 200 ms. When the Downlink radio link quality estimated over the last 100 ms period becomes better than the threshold Qin, Layer 1 of the UE sends an In-Sync indication to the higher layers within the 100 ms.Two successive indications from Layer 1 will be separated by at least 10 ms. If the UE does use DRX, the evaluation period for Qoutand Qindepends on DRX configuration is shown in the table below. In this case, two successive In-Sync or Out-of-Sync indications will be separated by at least a maximum of either 10 ms or the DRX cycle length. Upon receiving N310 consecutive "out-of-sync" indications from lower layers, the T310 timer starts. At the expiry of the T310 timer and in the absence of N311 in-sync indication, radio link failure is declared. The transmitter power shall be turned off within 40 ms after the T310 timer expires. The UE could recover before the declaration of a Radio Link Failure. As stated above, T310 is started following N310 Out-of-Sync indicators. However, if N311 In-Sync indicators (PDCCH BLER< 2%) are received before the expiration of T310. A Radio Link Failure is not declared. Once an RLF has been declared, UE will initiate the RRC connection re-establishment procedure. This is only possible if AS security was activated prior to the RLF. Upon the initiation of the procedure, the timer T311 is started and UE attempts cell reselection. If cell reselection is unsuccessful before the expiration of T311, the UE transits to idle mode. If successful, the UE begins the connection reestablishment with the selected cell. Please see Figure 13-1 for the RRC recovery/connection reestablishment example after radio link failure is declared.

Figure 13-1 RRC Recovery after Radio Link Failure is declared

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

328

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.3.1 T310

Released - For Current Employee/Consultant Use Only

Definition: Maximum time allowed by the UE to recover from physical layer problems before Radio Link Failure is declared.

Allowed Range

Recommended

IE Value

Engineering Units

ENUMERATED

Unit: ms

(ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}

Range: 100, 200, 300, 400, 600, 1000, 1500, 2000

ms1000 for BE

1000 ms Lower value for VoLTE

Lower value for VoLTE

Setting Tradeoff: If the parameter is set too low, UE may not get a chance to receive N311 ‘in sync’ indications leading to declaration of Radio link Failure prematurely. If the parameter is set too long, UE will take too long to declare Radio link Failure leading to degraded user experience. Dependencies/Constraints: Parameter N310 and N311 should be optimized jointly. Traceability: TS 36.331 Sect 5.3, Sect 7.3 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonUE-TimersAndconstants t310 Notes: UE starts t310 timer when problems at physical layer are detected, which is done upon receiving N310 consecutive out-of-sync indications form the physical layer. T310 timer is stopped upon receiving N311 consecutive in-sync indications from physical layer. The timer is also stopped upon triggering of handover procedure or upon initiating connection re-establishment procedure.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

329

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.3.2 N310 Definition: Successive number of ‘out-of-Sync’ conditions to start T310 timer.

Released - For Current Employee/Consultant Use Only

IE Value Allowed Range

Engineering Units

ENUMERATED

Unit:

(n1, n2, n3, n4, n5, n6, n8, n10, n20}

Range: 1, 2, 3, 4, 5, 6, 8, 10, 20

n10 Lower value for VoLTE

10

Recommended

Setting Tradeoff: If the parameter is set too low, UE may start T310 timer too soon. Depending on setting of T310 and N311 this may lead to declaration of radio link failure prematurely. If the parameter is set too long, UE will take too long to start T310 timer in turn taking too long to declare Radio link Failure leading to degraded user experience. Dependencies/Constraints: Parameter N310 and N311 should be optimized jointly. Traceability: TS 36.331 Sect 5.3, Sect 7.3, TS36.133 Sect 7.6 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonUE-TimersAndconstants N310 Notes: UE starts t310 timer when problems at physical layer are detected, which is done upon receiving N310 consecutive out-of-sync indications form the physical layer. UE estimates the radio link quality and compares it to thresholds Qout & Qin for the purpose of monitoring radio link quality of the serving cell. The threshold Qout is defined as the level at which the downlink radio link cannot be reliably received and corresponds to 10% block error rate of a hypothetical PDCCH transmission taking into account the PCFICH errors. Transmission parameters assumed for this computation are specified in Table 7.6.1-1 in [36.133]. 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. The transmission parameters are specified in Table 7.6.1-2 in [36.133]. When the downlink radio link quality estimated over the last 200 ms period becomes worse than the threshold Qout, Layer 1 of the UE sends an out-of-sync indication to the higher layers within 200 ms Qout evaluation period. When the downlink radio link quality estimated over the last 100 ms period becomes better than the threshold Qin, Layer 1 of the UE sends an in-sync indication to the higher layers within 100 ms Qin evaluation period. When DRX is used the Qout evaluation period (TEvaluate_Qout_DRX) and the Qin evaluation period (TEvaluate_Qin_DRX) is specified in Table 7.6.2.2-1 in [36.133] will be used. Two successive indications from Layer 1 shall be separated by at least max(10 ms, DRX_cycle_length). 80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

330

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

Released - For Current Employee/Consultant Use Only

The out-of-sync and in-sync evaluations are performed every frame evaluated over previous time period defined for evaluation. Two successive indications from Layer 1 shall be separated by at least 10 ms.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

331

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.3.3 N311 Definition: Successive number of ‘in-Sync’ conditions required to stop T310 timer.

Released - For Current Employee/Consultant Use Only

IE Value Allowed Range Recommended

Engineering Units

ENUMERATED

Unit:

(n1, n2, n3, n4, n5, n6, n8, n10}

Range: 1, 2, 3, 4, 5, 6, 8, 10

n1

1

Setting Tradeoff: If the parameter is set too low, the UE may stop T310 timer too early only because the physical layer problem improves just temporarily. The UE may take too long to declare Radio link Failure leading to degraded user experience. If the parameter is set too high, the UE will be unable to stop the T310 timer while the physical layer already becomes better, and the UE may declare the RLF unnecessarily. Dependencies/Constraints: Parameter N310 and N311 to be optimized jointly. Traceability: TS 36.331 Sect 5.3, Sect 7.3, TS36.133 Sect 7.6 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonUE-TimersAndconstants N311 Notes: UE starts t310 timer when problems at physical layer are detected, which is done upon receiving N310 consecutive out-of-sync indications form the physical layer. This timer is stopped upon detection of N311 in-sync conditions.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

332

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.3.4 T311

Released - For Current Employee/Consultant Use Only

Definition: Maximum time allowed for the UE to find a suitable E-UTRA cell or a cell using another RAT after radio link failure is declared. IE Value

Allowed Range

Recommended

Engineering Units

ENUMERATED

Unit: ms

(ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000}

Range: 1000, 3000, 5000, 10000, 15000, 20000, 3000

ms3000

3000 ms

Setting Tradeoff: If the parameter is set too low, probability of timer expiring before cell selection can be completed is high. This will not allow the RRC recovery to complete successfully, which leads to degraed user experience. If set too high, it gives more chance for UE to find the suitable cell for RRC recovery, but it may reduce the battery life and stretch unnecessarily RRC recovery time, which prevents state transition to idle state. Dependencies/Constraints: Parameter. Traceability: TS 36.331 Sect 5.3, Sect 7.3 RRC Message Structure: SystemInformationBlockType2RadioResourceConfigCommonUE-TimersAndconstants t311 Notes: UE starts T311 timer upon initiation of RRC connection reestablishment procedure. The timer is stopped when UE selects a suitable cell. At the expiration of T311 timer UE transitions to idle state with cause ‘RRC Connection Failure’.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

333

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.4 Access Barring Related Timers and Parameters

Released - For Current Employee/Consultant Use Only

13.4.1 T302 Definition: The maximum duration for which the UE is barred after it receives the RRCConnectionReject. The value of this timer is set to the waitTime in RRCConnectionReject message the UE receives. IE Value

Engineering Units

Allowed Range

INTEGER (1..16)

Unit: secs Range: 1..16

Recommended

5 to 10

5 to 10 seconds

Setting Tradeoff: If the parameter (i.e., waitTime) is set too low, the UE will be alleviated from barring early. However the UE may still get the RRCConnectionRejection even it tries the RRC connection since the network situation may not change too much in a short time. If the parameter (i.e., waitTime) is set too high, the UE will be barred for too long. This will delay the RRC connection for either mobile originating call or mobile terminated call. Dependencies/Constraints: It depends on the value of waitTime in RRCConnectionReject message. Traceability: TS 36.331 Sect 5.3, Sect 7.3 RRC Message Structure: RRCConnectionReject  waitTime (T302 will be set by this value) Notes: UE starts the T302 timers upon it receives the RRCConnectionRejection, and the value is set to the waitTime in RRCConnectionRejection message. The timer will stop if the UE enters RRC_CONNECTED or starts the cell reselection. At the timer expiration, the UE shall inform the upper layers about barring alleviation.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

334

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.4.2 T303

Released - For Current Employee/Consultant Use Only

Definition: The maximum duration for which the UE is barred while performing RRC connection establishment for mobile originating data calls if the UE belongs to access class 11 to 15. The value of this timer is determined by ac-BarringTime. Dependencies/Constraints: It is calculated based on the ac-BarringTime included in acBarringForMO-Data in SystemInformationBlockType2. Traceability: TS 36.331 Sect 5.3, Sect 7.3 Notes: T303= (0.7+ 0.6 * rand) * ac-BarringTime, where rand is a uniformly distributed random number in the range of 0 ≤ rand < 1. The UE access class 11 to 15 are defined as follows Class 15 - PLMN Staff; Class 14 - Emergency Services; Class 13 - Public Utilities (e.g. water/gas suppliers); Class 12 - Security Services; Class 11 - For PLMN Use.

13.4.3 T305 Definition: The maximum duration for which the UE is barred while performing RRC connection establishment for mobile originating signaling calls if the UE belongs to access class 11 to 15. The value of this timer is determined by ac-BarringTime. Dependencies/Constraints: It is calculated based on the ac-BarringTime included in acBarringForMO-Signalling in SystemInformationBlockType2. Traceability: TS 36.331 Sect 5.3, Sect 7.3 Notes: T305= (0.7+ 0.6 * rand) * ac-BarringTime, where rand is a uniformly distributed random number in the range of 0 ≤ rand < 1.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

335

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.4.4 ac-BarringTime

Released - For Current Employee/Consultant Use Only

Definition: Determines the mean access barring time for Access Class 11 to 15. IE Value

Engineering Units

Allowed Range

ENUMERATED {s4, s8, s16, s32, s64, s128, s256, s512},

Unit: Seconds

Recommended

Dependent on the operator’s specific need for UE access class 11 to 15

Range: 4, 8, 16, 32, 64, 128, 256, 512

Setting Tradeoff: If the parameter is set too low, the mean of access barring timer T303 and T305 will be small. Statistically, the UE in access class 11 to 15 may be alleviated from barring early, but the UE may still get RRC connection rejections upon next try because the network situation may not change too much in a short time. If the parameter is set too high, the mean of access barring timer T303 and T305 will be large. Statistically, the UE in access class 11 to 15 may be barred too long, and this will delay the RRC connection for either mobile originating data call or mobile originating signaling call. Dependencies/Constraints: None. Traceability: TS 36.331 Sect 5.3, Sect 6.3 RRC Message Structure: SystemInformationBlockType2  ac-BarringInfo  ac-BarringForMO-Signalling  ac-BarringTime SystemInformationBlockType2  ac-BarringInfo  ac-BarringForMO-Data  ac-BarringTime Notes: This parameter determines the value of T303 and T305 timers.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

336

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.4.5 ac-BarringFactor Definition: Determines whether the UE in access class 11 to 15 is barred or not.

Released - For Current Employee/Consultant Use Only

IE Value

Allowed Range

ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40, p50, p60, p70, p75, p80, p85, p90, p95}

Recommended

Dependent on the operator’s specific need for UE access class 11 to 15

Engineering Units Unit: None Range: 0, 0.05, 0.10, 0.15, 0.20, 0.25, 0.30, 0.40, 0.50, 0.60, 0.70, 0.75, 0.80, 0.90, 0.95

Setting Tradeoff: If the parameter is set too low, the UE in access class 11 to 15 with the corresponding bits being set in ac-BarringForSpecialAC will be more easily barred for the mobile originated data/signaling calls. If the parameter is set too high, the UE in access class 11 to 15 with the corresponding bits being set in ac-BarringForSpecialAC will be less likely barred for the mobile originated data/signaling calls. Dependencies/Constraints: It depends on the setting of ac-BarringForEmergency, acBarringForSpecialAC in ac-BarringForMO-Data or ac-BarringForMO-Signaling. Traceability: TS 36.331 Sect 5.3, Sect 6.3 RRC Message Structure: SystemInformationBlockType2  ac-BarringInfo  ac-BarringForMO-Signalling  ac-BarringFactor SystemInformationBlockType2  ac-BarringInfo  ac-BarringForMO-Data  ac-BarringFactor Notes: If SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data/acBarringForMO-Signaling is present, If the UE in at least one or more Access Classes with its corresponding bit in the acBarringForSpecialAC in ac-BarringForMO-Data or ac-BarringForMO-Signaling is set to zero, Consider access to the cell as not barred. Else draw a random number 'rand' uniformly distributed in the range: 0 ≤ rand < 1; if 'rand' is lower than the value indicated by ac-BarringFactor included in acBarringForMO-Data: consider access to the cell as not barred; else: consider access to the cell as barred; else: consider access to the cell as not barred.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

337

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.4.6 ac-BarringForSpecialAC

Released - For Current Employee/Consultant Use Only

Definition: Defines which access class (from 11 to 15) can be barred. IE Value

Engineering Units

Allowed Range

BIT STRING (SIZE(5))

Unit: None Range: BIT STRING (SIZE(5))

Recommended

NA

Setting Tradeoff: NA. Dependencies/Constraints: NA. Traceability: TS 36.331 Sect 5.3, Sect 6.3 RRC Message Structure: SystemInformationBlockType2  ac-BarringInfo  ac-BarringForMO-Signalling  acBarringForSpecialAC SystemInformationBlockType2  ac-BarringInfo  ac-BarringForMO-Data  ac-BarringForSpecialAC Notes: The first/ leftmost bit is for AC 11, the second bit is for AC 12, and so on.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

338

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.5 Cell Reselection and Handover Related Timers

Released - For Current Employee/Consultant Use Only

13.5.1 T304 Definition: Maximum duration from the reception of RRCConnectionReconfiguration message till the criterion for successful completion of handover to EUTRA or cell change order is met. IE Value

Engineering Units

Allowed Range

ENUMERATED {ms100, ms200, ms500, ms1000, ms2000, ms4000, ms8000, spare1}

Unit: ms Range: 100, 200, 500, 1000, 2000, 4000, 8000

Recommended

ms1000

1000 ms

Setting Tradeoff: If the parameter is set too low, it may result in some failed HOs in case there is insufficient time to complete the HO (preparation, target cell RACH/contention resolution). If the parameter is set too high, it may result in the UE waiting too long for HO to complete when it may be suitable to trigger RLF and re-establishment. Dependencies/Constraints: None. Traceability: TS 36.331 Sect 5.3, Sect 6.3 RRC Message Structure: RRCConnectionReconfiguration  mobilityControlInfo  t304 Notes: The UE starts the T304 timer when the UE receives RRCConnectionReconfiguration message including the MobilityControl Info or reception of MobilityFromEUTRACommand message including CellChangeOrder. The UE stops the T304 timer upon successful completion of handover to EUTRA or cell change order. At the expiry of T304 timer, in case of cell change order from E-UTRA or intra EUTRA handover, the UE will declare radio link failure and initiate the RRC connection re-establishment procedure. In case of handover to E-UTRA, the UE will perform the actions defined in the specifications applicable for the source RAT.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

339

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

13.5.2 T320

Released - For Current Employee/Consultant Use Only

Definition: Maximum duration for which the cell reselection priority provided by the dedicated signaling is valid

Allowed Range Recommended

IE Value

Engineering Units

ENUMERATED (min5, min10, min20, min30, min60, min120, min180}

Unit: minutes Range: 5, 10, 20, 30, 60, 120, 180

min5-10

5 - 10 mins

Setting Tradeoff: If the parameter is set too low, the UE may stop using the dedicated cell reselection priorities too early. If the parameter is set too high, the UE may stay with the dedicated cell reselection priorities too long if those cell reselections fail, as a result the UE will be delayed to use the common cell reselection priorities. This may degrade the user experience. Dependencies/Constraints: Traceability: TS 36.331 Sect 5.3, Sect 7.3 RRC Message Structure: RRCConnectionReleaseIdleModeMobilityControlInfo T320 Notes: UE starts T320 when RRCConnectionRelease includes it. The timer is received as part of idleMobilityControlInfo. UE is configured with this timer when dedicated signaling is used to configure the cell reselection priorities. The timer is stopped upon entering RRC_CONNECTED, when PLMN selection is performed on request by NAS, or upon cell (re)selection to another RAT (in which case the timer is carried on to the other RAT). At the expiry of the timer UE discards the cell reselection priorities configured using dedicated signaling. UE will revert back to the cell reselection priorities broadcast over common channel.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

340

Released - For Current Employee/Consultant Use Only

Chavarria, Adriana (achavarr) - 07/26/2013 02:22:27 PM PDT LTE Parameter Setting Guidelines

RRC Timers and Parameters

Released - For Current Employee/Consultant Use Only

13.5.3 T321 Definition: Maximum duration from receiving measConfig including a reportConfig with the purpose set to reportCGI to the time acquiring the information needed to set all fields of cellGlobalId for the requested cell, or upon receiving measConfig that includes removal of the reportConfig with the purpose set to reportCGI. IE Value

Engineering Units

Allowed Range

1 second for EUTRA 8 seconds otherwise

1 second for EUTRA 8 seconds otherwise

Recommended

Fixed in Standard

Setting Tradeoff: NA. Dependencies/Constraints: NA. Traceability: TS 36.331 Sect 5.3, Sect 7.3 RRC Message Structure: NA. Notes: This timer is only applicable to periodic measurement report.

80-W3835-1 Rev. A

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Confidential and Proprietary – Qualcomm Global Services, Inc.

341

Released - For Current Employee/Consultant Use Only

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF