Fd Rl20 Desc
Short Description
Fd Rl20 Desc...
Description
Nokia
LTE Radio Access, Rel. FDDLTE 16A, Operating Documentation, Issue 02 LTE RL20, Feature Descriptions DN0978033 Issue 02N Approval Date 2016-06-29
LTE RL20, Feature Descriptions
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners. Copyright © 2016 Nokia. All rights reserved.
f
Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.
2
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table of Contents This document has 255 pages
Summary of changes................................................................... 23
1
RL20 Features - not supported by Flexi Zone Micro....................24
2 2.1 2.1.1 2.1.2 2.1.3 2.1.3.1 2.1.3.2 2.1.4 2.1.4.1 2.1.4.2 2.1.4.2.1 2.1.5 2.1.6 2.1.6.1 2.1.6.2 2.1.6.3 2.1.7 2.1.8 2.1.8.1 2.2 2.2.1 2.2.2 2.2.3 2.2.3.1 2.2.3.2 2.2.3.3 2.2.4 2.2.4.1 2.2.4.2 2.2.4.3 2.2.5 2.2.5.1 2.2.5.2 2.2.6 2.2.6.1 2.2.7 2.2.7.1 2.2.7.2
Radio resource management and telecom features.................... 25 LTE2: S1 Flex...............................................................................25 Introduction to the feature............................................................ 25 Benefits........................................................................................ 25 Requirements...............................................................................25 Software requirements................................................................. 25 Hardware requirements................................................................25 Functional description.................................................................. 26 S1 interface.................................................................................. 26 MME selection..............................................................................26 Load balancing.............................................................................27 Sales information......................................................................... 27 User interface...............................................................................28 Parameters...................................................................................28 Alarms.......................................................................................... 28 Measurements and counters........................................................28 Activating and configuring the feature..........................................28 Abbreviations............................................................................... 28 0 – Z............................................................................................. 28 LTE4: RAN Sharing...................................................................... 29 Introduction to the feature............................................................ 29 Benefits........................................................................................ 29 Requirements...............................................................................29 Interdependencies between features........................................... 29 Software requirements................................................................. 29 Hardware requirements................................................................30 Requirements...............................................................................30 Interdependencies between features........................................... 30 Software requirements................................................................. 30 Hardware requirements................................................................30 Functional description.................................................................. 30 Functional overview..................................................................... 31 Feature activation.........................................................................31 System impact..............................................................................31 Interdependencies between features........................................... 31 LTE4: RAN Sharing management data........................................ 31 Alarms.......................................................................................... 31 Measurements and counters........................................................31
DN0978033 Issue: 02N
© 2016 Nokia
3
LTE RL20, Feature Descriptions
2.2.7.3 2.2.7.4 2.2.7.5 2.3 2.3.1 2.3.2 2.3.3 2.3.3.1 2.3.3.2 2.3.4 2.3.5 2.3.6 2.3.7 2.3.7.1 2.3.7.2 2.4 2.4.1 2.4.2 2.4.3 2.4.3.1 2.4.3.2 2.4.4 2.4.5 2.4.6 2.4.7 2.4.7.1 2.4.7.2 2.4.7.3 2.4.8 2.5 2.5.1 2.5.2 2.5.3 2.5.3.1 2.5.3.2 2.5.4 2.5.4.1 2.5.4.2 2.5.4.3 2.5.4.4 2.5.4.5 2.5.4.6 2.5.4.7 2.5.4.8 2.5.5
4
Key performance indicators......................................................... 31 Parameters...................................................................................31 Sales information......................................................................... 32 LTE7: Support of multiple EPS bearer......................................... 32 Introduction To The Feature......................................................... 32 Benefits........................................................................................ 32 Requirements...............................................................................32 Software Requirements................................................................32 Hardware Requirements.............................................................. 33 Functional Description..................................................................33 System Impacts............................................................................38 Sales Information......................................................................... 38 User Interface...............................................................................38 Parameters...................................................................................38 Measurements and Counters.......................................................39 LTE9: Service Differentiation........................................................42 Introduction to the feature............................................................ 42 Benefits........................................................................................ 42 Requirements...............................................................................42 Software requirements................................................................. 42 Hardware requirements................................................................42 Functional description.................................................................. 42 System impacts............................................................................ 44 Sales information......................................................................... 44 User interface...............................................................................44 Parameters...................................................................................44 Alarms.......................................................................................... 60 Measurements and counters........................................................60 Activating the feature................................................................... 61 LTE10: EPS Bearers for Conversational Voice............................ 61 Introduction to the feature............................................................ 61 Benefits........................................................................................ 62 Requirements...............................................................................62 Software requirements................................................................. 62 Hardware requirements................................................................62 Functional description.................................................................. 63 Delay based scheduling in DL and in UL for bearers with QCI=1.... 63 Outer loop delay target control in DL........................................... 64 HOL packet delay estimation in UL..............................................64 Consideration of GBR bearer in MAC multiplexing in DL.............64 New scheduler type: exhaustive FD scheduler............................ 65 Packet aggregation in UL/DL....................................................... 65 Bearer establishment................................................................... 65 Radio admission control thresholds............................................. 66 System impacts............................................................................ 66
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.5.6 2.5.7 2.5.7.1 2.5.7.2 2.5.8 2.6 2.6.1 2.6.2 2.6.3 2.6.3.1 2.6.3.2 2.6.4 2.6.4.1 2.6.4.2 2.6.4.3 2.6.5 2.6.6 2.6.7 2.6.7.1 2.6.8 2.7 2.7.1 2.7.2 2.7.3 2.7.3.1 2.7.3.2 2.7.4 2.7.5 2.7.6 2.7.7 2.7.7.1 2.7.7.2 2.7.7.3 2.7.8 2.8 2.8.1 2.8.2 2.8.3 2.8.3.1 2.8.3.2 2.8.4 2.8.4.1 2.8.4.2 2.8.4.3 2.8.4.3.1 2.8.4.3.2
DN0978033 Issue: 02N
Sales information......................................................................... 67 User interface...............................................................................67 Parameters...................................................................................67 Measurements and counters........................................................72 Activating the feature................................................................... 72 LTE11: Robust header compression............................................ 73 Introduction To The Feature......................................................... 73 Benefits........................................................................................ 73 Requirements...............................................................................73 Software Requirements................................................................73 Hardware Requirements.............................................................. 74 Functional Description..................................................................74 Short Description of ROHC.......................................................... 74 Bearer Establishment...................................................................75 PDCP Adaptation for ROHC........................................................ 78 System Impacts............................................................................79 Sales Information......................................................................... 79 User Interface...............................................................................79 Parameters...................................................................................79 Activating the Feature.................................................................. 79 LTE13: Rate Capping (UL/DL)..................................................... 80 Introduction to the feature............................................................ 80 Benefits........................................................................................ 80 Requirements...............................................................................80 Software requirements................................................................. 80 Hardware requirements................................................................80 Functional description.................................................................. 80 System impacts............................................................................ 82 Sales information......................................................................... 82 User interface...............................................................................82 Parameters...................................................................................82 Alarms.......................................................................................... 83 Measurements and counters........................................................83 Activating the feature................................................................... 83 LTE22: Emergency Call Handling................................................ 83 Introduction to the Feature........................................................... 83 Benefits........................................................................................ 84 Requirements...............................................................................84 Software Requirements................................................................84 Hardware Requirements.............................................................. 84 Functional Description..................................................................84 Functional Overview/Details.........................................................84 Emergency Call Handling.............................................................85 Emergency Call Support.............................................................. 85 Emergency Call trigger.................................................................85 Initiation of CS Fallback with Redirect due to Emergency Call.... 86
© 2016 Nokia
5
LTE RL20, Feature Descriptions
2.8.4.3.3 2.8.4.3.4 2.8.4.3.5 2.8.4.4 2.8.4.4.1 2.8.4.4.2 2.8.4.5 2.8.5 2.8.5.1 2.8.5.2 2.8.5.2.1 2.8.5.3 2.8.5.4 2.8.5.4.1 2.8.5.4.2 2.8.6 2.8.7 2.8.7.1 2.8.7.2 2.8.8 2.9 2.9.1 2.9.2 2.9.3 2.9.3.1 2.9.3.2 2.9.4 2.9.4.1 2.9.4.2 2.9.4.3 2.9.4.3.1 2.9.4.4 2.9.4.4.1 2.9.4.4.2 2.9.4.4.3 2.9.4.4.4 2.9.4.5 2.9.4.5.1 2.9.4.5.2 2.9.4.5.3 2.9.4.6 2.9.5
6
Selection of target Radio Access Technology for Emergency Call.. 86 Initiating UE Context Release ..................................................... 86 Emergency Call - Unsuccessful Procedure..................................86 Radio Admission Control (RAC)...................................................87 RAC introduces a new Threshold for Emergency Call Handling...... 87 Admission of emergency calls with higher threshold value..........87 Radio Network Layer (RNL) support for Emergency Call via Redirection................................................................................... 88 System Impacts............................................................................88 Dependencies Between Features................................................ 88 Impacts on Interfaces...................................................................88 External Interfaces....................................................................... 88 Impacts on Network and Network Element Management tools... 88 Impacts on System Performance and Capacity........................... 88 System Performance....................................................................88 System Capacity.......................................................................... 89 Sales Information......................................................................... 89 User Interface...............................................................................89 Parameters...................................................................................89 Measurements and Counters.......................................................90 Activating the Feature.................................................................. 90 LTE54: Intra-LTE handover via S1............................................... 91 Introduction to the Feature........................................................... 91 Benefits........................................................................................ 91 Requirements...............................................................................91 Software Requirements................................................................91 Hardware Requirements.............................................................. 91 LTE54: Intra-LTE Handover via S1...............................................92 Functional Overview/Details.........................................................92 Handover trigger ......................................................................... 92 Handover Target and Mode Selection..........................................93 Handover Mode selection for S1 based handover....................... 93 Handover over S1 interface......................................................... 93 Handover decision....................................................................... 94 Handover preparation.................................................................. 94 Handover execution .................................................................... 94 Handover completion................................................................... 94 Data forwarding ...........................................................................94 Support of indirect data forwarding.............................................. 94 Determination of which bearers are subject to data forwarding at source eNB on HO via S1............................................................ 95 Resource Allocation at Target eNB.............................................. 95 Performance Counters................................................................. 95 System Impact............................................................................. 95
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.9.5.1 2.9.5.2 2.9.5.2.1 2.9.5.3 2.9.5.4 2.9.5.4.1 2.9.5.4.2 2.9.6 2.9.7 2.9.7.1 2.9.7.2 2.10 2.10.1 2.10.2 2.10.3 2.10.3.1 2.10.3.2 2.10.4 2.10.4.1 2.10.4.2 2.10.4.2.1 2.10.4.2.2 2.10.4.2.3 2.10.4.2.4 2.10.4.3 2.10.4.4 2.10.5 2.10.5.1 2.10.5.2 2.10.5.3 2.10.5.4 2.10.6 2.10.7 2.10.7.1 2.10.7.2 2.10.8 2.11 2.11.1 2.11.2 2.11.3 2.11.3.1 2.11.3.2 2.11.4 2.11.5 2.11.5.1 2.11.6
DN0978033 Issue: 02N
Dependencies Between Features................................................ 95 Impact on Interfaces.....................................................................96 External Interfaces....................................................................... 96 Impact on Network and Network Element Management tools..... 96 Impact on System Performance and Capacity.............................96 System Performance....................................................................96 System Capacity.......................................................................... 96 Sales Information......................................................................... 97 User Interface...............................................................................97 Parameters...................................................................................97 Measurements and Counters.......................................................98 LTE55: Inter-frequency handover...............................................100 Introduction to the Feature......................................................... 100 Benefits...................................................................................... 100 Requirements.............................................................................100 Software Requirements..............................................................100 Hardware Requirements............................................................ 101 Functional Description................................................................101 Functional Overview/Details.......................................................101 Inter-frequency Handover Variants.............................................101 RSRP for A3 event (Better Cell HO).......................................... 102 RSRQ for A3 event (Better Cell HO)..........................................103 RSRP for A5 event (Coverage HO)........................................... 103 Th2a for deactivation of A3 and A5 events................................ 103 Handover trigger........................................................................ 103 Performance counters................................................................104 System Impact........................................................................... 104 Dependencies Between Features.............................................. 104 Impact on Interfaces...................................................................104 Impact on Network and Network Element Management tools... 104 Impact on System Performance and Capacity...........................104 Sales Information....................................................................... 105 User Interface.............................................................................105 Parameters.................................................................................105 Measurements and Counters..................................................... 110 Activating the Feature.................................................................110 LTE703: DL adaptive closed loop MIMO for two antennas ........111 Introduction to the feature...........................................................111 Benefits.......................................................................................111 Requirements............................................................................. 111 Software Requirements.............................................................. 111 Hardware Requirements.............................................................111 Functional description.................................................................112 System impacts.......................................................................... 112 Dependencies between features................................................ 112 Sales information........................................................................113
© 2016 Nokia
7
LTE RL20, Feature Descriptions
2.11.7 2.11.7.1 2.11.7.2 2.11.8 2.12 2.12.1 2.12.2 2.12.3 2.12.3.1 2.12.3.2 2.12.4 2.12.4.1 2.12.4.2 2.12.5 2.12.5.1 2.12.6 2.12.7 2.12.7.1 2.12.7.2 2.12.7.3 2.12.8 2.13 2.13.1 2.13.2 2.13.3 2.13.3.1 2.13.3.2 2.13.4 2.13.4.1 2.13.4.2 2.13.5 2.13.5.1 2.13.5.2 2.13.5.3 2.13.5.3.1 2.13.5.3.2 2.13.6 2.13.7 2.13.7.1 2.13.7.2 2.13.7.3 2.13.8 2.14 2.14.1 2.14.2 2.14.2.1
8
User interface............................................................................. 113 Parameters................................................................................. 113 Measurements and counters...................................................... 114 Activating and configuring the feature........................................ 115 LTE562: CSFB to UTRAN or GSM via redirect.......................... 115 Introduction to the feature...........................................................115 Benefits.......................................................................................115 Requirements............................................................................. 115 Software Requirements.............................................................. 115 Hardware Requirements.............................................................116 Functional description.................................................................116 Functional overview....................................................................116 Selection of target RAT...............................................................117 System impacts.......................................................................... 118 Impacts on system performance and capacity........................... 118 Sales information........................................................................118 User interface............................................................................. 118 Parameters................................................................................. 118 Alarms........................................................................................ 119 Measurements and counters...................................................... 119 Activating the feature................................................................. 120 LTE819: DL Inter-cell Interference Generation...........................120 Introduction To The Feature....................................................... 120 Benefits...................................................................................... 120 Requirements.............................................................................120 Software Requirements..............................................................121 Hardware Requirements............................................................ 121 Functional Description................................................................121 Feature Scope............................................................................121 User Scenarios...........................................................................121 System Impacts..........................................................................122 Dependencies Between Features.............................................. 122 Impacts on Network and Network Element Management tools. 122 Impacts on System Performance and Capacity......................... 122 System Performance..................................................................122 System Capacity........................................................................ 122 Sales Information....................................................................... 122 User Interface.............................................................................122 Parameters.................................................................................122 Alarms........................................................................................ 123 Measurements and Counters.....................................................123 Activating the Feature................................................................ 123 LTE870: Idle Mode Mobility from LTE to CDMA/eHRPD............123 Introduction to the Feature......................................................... 123 Benefits...................................................................................... 124 End User Benefits...................................................................... 124
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.14.2.2 2.14.3 2.14.3.1 2.14.3.2 2.14.4 2.14.5 2.14.6 2.14.6.1 2.14.6.2 2.14.6.3 2.14.6.4 2.14.7 2.14.7.1 2.14.8 2.15 2.15.1 2.15.1.1 2.15.1.2 2.15.1.3 2.15.1.4 2.15.1.5 2.15.1.6 2.15.2 2.15.3
Operator Benefits....................................................................... 124 Requirements.............................................................................124 Software Requirements..............................................................124 Hardware Requirements............................................................ 124 Functional Description................................................................124 Sales Information....................................................................... 125 User Interface.............................................................................125 Managed Objects....................................................................... 125 Parameters.................................................................................125 Alarms........................................................................................ 126 Measurements and counters......................................................126 System Impacts..........................................................................126 Impacts on Telecom control plane..............................................126 Activating the Feature................................................................ 126 LTE914: Graceful cell shutdown.................................................127 Description of LTE914: Graceful Cell Shutdown........................ 127 Benefits...................................................................................... 127 Requirements.............................................................................127 Functional description................................................................ 127 System impact............................................................................130 LTE914: Graceful cell shutdown management data.................. 130 Sales information....................................................................... 131 Activating LTE914: Graceful Cell Shutdown...............................131 Deactivating LTE914: Graceful Cell Shutdown.......................... 132
3 3.1 3.1.1 3.1.2 3.1.2.1 3.1.2.2 3.1.3 3.1.3.1 3.1.3.2 3.1.4 3.1.4.1 3.1.4.2 3.1.4.2.1
Transport and Transmission Features........................................133 LTE140: Ethernet OAM.............................................................. 133 Introduction to the feature.......................................................... 133 Benefits...................................................................................... 133 End user benefits....................................................................... 133 Operator benefits....................................................................... 133 Requirements.............................................................................133 Software requirements............................................................... 133 Hardware requirements..............................................................134 Functional description................................................................ 134 Link Layer OAM......................................................................... 134 Service OAM.............................................................................. 135 Ethernet Continuity Check and Ethernet Remote Defect Indication ................................................................................................... 137 Ethernet Alarm Indication Signal................................................137 Ethernet Loopback..................................................................... 138 Ethernet Link Trace.................................................................... 139 Sales information....................................................................... 139 User interface.............................................................................139 Parameters.................................................................................139 Alarms........................................................................................ 143
3.1.4.2.2 3.1.4.2.3 3.1.4.2.4 3.1.5 3.1.6 3.1.6.1 3.1.6.2
DN0978033 Issue: 02N
© 2016 Nokia
9
LTE RL20, Feature Descriptions
3.1.6.3 3.1.7 3.1.8 3.1.8.1 3.2 3.2.1 3.2.2 3.2.3 3.2.3.1 3.2.3.2 3.2.4 3.2.4.1 3.2.4.2 3.2.5 3.2.6 3.2.6.1 3.2.6.2 3.2.6.3 3.2.7 3.2.8 3.2.8.1 3.3 3.3.1 3.3.2 3.3.3 3.3.3.1 3.3.3.2 3.3.3.3 3.3.4 3.3.5 3.3.6 3.3.6.1 3.3.6.2 3.3.6.3 3.3.7 3.3.7.1 3.4 3.4.1 3.4.2 3.4.3 3.4.3.1 3.4.3.2 3.4.4 3.4.5 3.4.6 3.4.6.1
10
Measurements and counters......................................................144 Activating and configuring the feature........................................144 Abbreviations............................................................................. 144 0 – Z........................................................................................... 144 LTE491: FlexiPacket Radio Connectivity................................... 145 Introduction to the feature.......................................................... 145 Benefits...................................................................................... 146 Requirements.............................................................................146 Software requirements............................................................... 146 Hardware requirements..............................................................146 Functional description................................................................ 146 FPR management uses FPR Payload Channel.........................147 FPR management uses separate Radio Channel......................148 Sales information....................................................................... 148 User interface.............................................................................148 Parameters.................................................................................149 Alarms........................................................................................ 149 Measurements and counters......................................................149 Activating and Configuring the Feature......................................149 Abbreviations............................................................................. 149 0 – Z........................................................................................... 149 LTE564: IPsec on FTIB.............................................................. 150 Introduction to the feature.......................................................... 150 Benefits...................................................................................... 150 Requirements.............................................................................150 Interdependencies between features......................................... 150 Software requirements............................................................... 150 Hardware requirements..............................................................150 Functional description................................................................ 150 Sales information....................................................................... 151 User interface.............................................................................151 Parameters.................................................................................151 Alarms........................................................................................ 151 Measurements and counters......................................................151 Abbreviations............................................................................. 151 0 – Z........................................................................................... 151 LTE592: Link Supervision with BFD........................................... 151 Introduction to the feature.......................................................... 151 Benefits...................................................................................... 151 Requirements.............................................................................151 Software requirements............................................................... 152 Hardware requirements..............................................................152 Functional description................................................................ 152 Sales information....................................................................... 153 User interface.............................................................................153 Parameters.................................................................................153
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
3.4.6.2 3.4.6.3 3.4.7 3.4.8 3.4.8.1 3.5 3.5.1 3.5.2 3.5.3 3.5.3.1 3.5.3.2 3.5.3.3 3.5.4 3.5.4.1 3.5.4.2 3.5.4.3 3.5.5 3.5.6 3.5.6.1 3.5.6.2 3.5.6.3 3.5.7 3.5.8 3.5.8.1 3.6 3.6.1 3.6.2 3.6.3 3.6.3.1 3.6.3.2 3.6.4 3.6.5 3.6.6 3.6.6.1 3.6.6.2 3.6.6.3 3.6.7 3.6.7.1
Alarms........................................................................................ 158 Measurements and counters......................................................158 Activating and Configuring the Feature......................................158 Abbreviations............................................................................. 158 0 – Z........................................................................................... 158 LTE649: QoS Aware Ethernet Switching....................................159 Introduction to the feature.......................................................... 159 Benefits...................................................................................... 159 Requirements.............................................................................159 Interdependencies between features......................................... 159 Software requirements............................................................... 160 Hardware requirements..............................................................160 Functional description................................................................ 161 VLAN aware switching............................................................... 162 VLAN unaware switching........................................................... 163 Scheduling and shaping for Ethernet QoS switching................. 163 Sales information....................................................................... 166 User interface.............................................................................166 Parameters.................................................................................166 Alarms........................................................................................ 175 Measurements and counters......................................................175 Activating and Configuring the Feature......................................176 Abbreviations............................................................................. 176 0 – Z........................................................................................... 176 LTE775: SCTP Multi-homing (MME).......................................... 177 Introduction to the feature.......................................................... 177 Benefits...................................................................................... 177 Requirements.............................................................................178 Software requirements............................................................... 178 Hardware requirements..............................................................178 Functional description................................................................ 178 Sales information....................................................................... 179 User interface.............................................................................179 Parameters.................................................................................179 Alarms........................................................................................ 180 Measurements and counters......................................................180 Abbreviations............................................................................. 180 0 – Z........................................................................................... 180
4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5
Operability features.................................................................... 181 LTE163: Subscriber and Equipment Trace................................ 181 Benefits...................................................................................... 181 Requirements.............................................................................181 Functional description................................................................ 181 System impact............................................................................186 Sales information....................................................................... 186
DN0978033 Issue: 02N
© 2016 Nokia
11
LTE RL20, Feature Descriptions
4.1.6 4.2 4.2.1 4.2.2 4.2.3 4.2.3.1 4.2.3.2 4.2.4 4.2.4.1 4.2.5 4.2.5.1 4.2.5.2 4.2.6 4.2.7 4.2.7.1 4.2.7.2 4.2.7.3 4.2.8 4.2.9 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.3.6 4.4 4.4.1 4.4.2 4.4.3 4.4.4 4.4.4.1 4.4.5 4.4.5.1 4.5 4.5.1 4.5.2 4.5.3 4.5.4 4.5.5 4.5.6 4.6 4.6.1 4.6.1.1 4.6.1.2
12
User interface.............................................................................186 LTE185: System Upgrade.......................................................... 187 Introduction to the feature.......................................................... 187 Benefits...................................................................................... 188 Requirements.............................................................................188 Software requirements............................................................... 188 Hardware requirements..............................................................188 Functional description................................................................ 188 LTE upgrade use cases..............................................................190 System impacts..........................................................................196 Impacts on interfaces................................................................. 196 Impact on network elements...................................................... 197 Sales information....................................................................... 197 User interface.............................................................................197 Parameters.................................................................................197 Alarms........................................................................................ 197 Measurements and counters......................................................197 System responses to failures..................................................... 197 Activating and configuring the feature........................................198 LTE433: Cell Trace.....................................................................199 Benefits...................................................................................... 199 Requirements.............................................................................199 Functional description................................................................ 199 System impact............................................................................204 Sales information....................................................................... 204 User interface.............................................................................204 LTE475: Automatic iOMS Resiliency..........................................206 LTE475: Automatic iOMS Resiliency - introduction....................206 Benefits...................................................................................... 207 Functional Description................................................................207 System Impacts..........................................................................209 Interdependencies between Features........................................209 Managed Objects....................................................................... 209 Parameters.................................................................................209 LTE521: Security on Ethernet ports on FCM/FSM2................... 210 Benefits...................................................................................... 210 Requirements............................................................................. 211 Functional description.................................................................211 System impact............................................................................212 LTE521: Security for Ethernet ports on FCM/FSM2 management data............................................................................................ 213 Sales information....................................................................... 213 LTE492: ANR............................................................................. 213 LTE492: ANR............................................................................. 213 Benefits...................................................................................... 214 Requirements.............................................................................214
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
4.6.1.2.1 4.6.1.2.2 4.6.1.3 4.6.1.3.1 4.6.1.3.2 4.6.1.3.2.1 4.6.1.3.2.2 4.6.1.3.2.3 4.6.1.3.2.4 4.6.1.4 4.6.1.4.1 4.6.1.5 4.6.1.6 4.6.1.6.1 4.6.1.6.2 4.6.1.6.3 4.6.1.7 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5 4.8 4.8.1 4.8.2 4.8.2.1 4.8.2.2 4.8.3 4.8.3.1 4.8.3.2 4.8.4 4.8.4.1 4.8.5 4.8.5.1 4.8.5.2 4.8.5.3 4.8.5.4 4.8.6 4.8.7 4.8.7.1 4.8.8 4.9 4.9.1
DN0978033 Issue: 02N
Software Requirements..............................................................214 Hardware Requirements............................................................ 214 LTE492: Automatic Neighbor Relation (ANR)............................ 215 Prerequisites.............................................................................. 215 Functional overview/details........................................................ 215 X2 link management.................................................................. 217 NetAct Optimizer: Neighbor evaluation procedure.....................219 NetAct Configurator: automated neighbor site IP connectivity configuration completion............................................................ 220 Use cases.................................................................................. 221 System Impacts..........................................................................221 Interdependencies between Features........................................221 Sales Information....................................................................... 223 User Interface.............................................................................223 Parameters.................................................................................223 Alarms........................................................................................ 225 Measurements and Counters.....................................................225 Activating and Configuring the Feature......................................226 LTE550: Radio Parameter Online Changeable.......................... 226 Benefits...................................................................................... 226 Requirements.............................................................................226 System impact............................................................................226 LTE550: Radio Parameter Online Changeable management data.. 227 Sales information....................................................................... 227 LTE559: SW Monitoring Module for LTE.................................... 228 Introduction to the feature.......................................................... 228 Benefits...................................................................................... 228 End user benefits....................................................................... 228 Operator benefits....................................................................... 228 Requirements.............................................................................228 Software requirements............................................................... 228 Hardware requirements..............................................................229 Functional description................................................................ 229 Functional overview/details........................................................ 229 System impacts..........................................................................230 Interdependencies between features......................................... 230 Impacts on interfaces................................................................. 230 Impacts on network and network element management tools... 230 Impacts on system performance and capacity...........................230 Sales information....................................................................... 230 User interface.............................................................................230 Parameters.................................................................................230 Activating and configuring the feature........................................230 LTE667: LTE User Event Log Management...............................230 Introduction to the feature.......................................................... 230
© 2016 Nokia
13
LTE RL20, Feature Descriptions
14
4.9.2 4.9.3 4.9.5 4.9.6 4.9.7 4.9.8 4.10 4.10.1 4.10.2 4.10.3 4.10.3.1 4.10.4 4.10.5 4.10.5.1 4.10.6 4.11 4.11.1 4.11.2 4.11.3 4.11.3.1 4.11.4 4.11.5
Benefits...................................................................................... 231 Requirements.............................................................................231 System impact............................................................................231 Sales information....................................................................... 231 LTE667: LTE User Event Log Management management data.231 Activating the feature................................................................. 232 LTE796: iOMS Connectivity Increase.........................................232 Introduction to the Feature......................................................... 232 Benefits...................................................................................... 232 Requirements.............................................................................232 Software Requirements..............................................................232 Functional Description................................................................232 System Impacts..........................................................................232 Interdependencies between Features........................................233 Sales Information....................................................................... 233 LTE830: LTE Automatic Lock..................................................... 233 Introduction to the Feature......................................................... 233 Benefits...................................................................................... 233 Requirements.............................................................................233 Software Requirements..............................................................233 Functional Description................................................................233 Parameters.................................................................................235
5 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.1.5 5.1.6
Performance Monitoring Features in RL20................................ 236 LTE805: PM Counter Capacity I.................................................236 Benefits...................................................................................... 236 Requirements.............................................................................236 Functional description................................................................ 236 System impact............................................................................237 Sales information....................................................................... 237 User interface.............................................................................237
6 6.1 6.1.1 6.1.2 6.1.3 6.1.3.1 6.1.4 6.1.5 6.1.6 6.1.6.1 6.1.7 6.2 6.2.1 6.2.2
Flexi Multiradio BTS LTE Site Solution features.........................240 LTE87: Flexi 3-sector RF Module 850........................................240 Introduction to the feature.......................................................... 240 Benefits...................................................................................... 240 Requirements.............................................................................240 Software requirements............................................................... 240 Functional description................................................................ 241 Sales information....................................................................... 241 User interface.............................................................................241 Parameters.................................................................................241 Activating the feature ................................................................ 242 LTE101: Flexi 3-sector RF Module 1800....................................242 Introduction to the feature.......................................................... 242 Benefits...................................................................................... 242
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
6.2.3 6.2.3.1 6.2.4 6.2.5 6.2.6 6.3 6.3.1 6.3.2 6.3.3 6.3.3.1 6.3.4 6.3.5 6.3.6 6.3.6.1 6.3.7 6.4 6.4.1 6.4.2 6.4.3 6.4.3.1 6.4.4 6.4.5 6.4.6 6.5 6.5.1 6.5.2 6.5.3 6.5.3.1 6.5.3.2 6.5.4 6.5.5 6.5.6 6.5.7 6.6 6.6.1 6.6.2 6.6.3 6.6.3.1 6.6.3.2 6.6.4 6.6.5 6.6.6 6.7 6.7.1 6.7.2 6.7.3
DN0978033 Issue: 02N
Requirements.............................................................................242 Software requirements............................................................... 242 Functional description................................................................ 243 Sales information....................................................................... 243 Activating the feature ................................................................ 244 LTE103: Flexi RRH 2TX 730...................................................... 244 Introduction to the feature.......................................................... 244 Benefits...................................................................................... 244 Requirements.............................................................................244 Software requirements............................................................... 244 Functional description................................................................ 244 Sales information....................................................................... 245 User interface.............................................................................245 Parameters.................................................................................245 Activating the feature ................................................................ 245 LTE104: Flexi RRH 2TX 1800.................................................... 245 Introduction to the feature.......................................................... 245 Benefits...................................................................................... 246 Requirements.............................................................................246 Software requirements............................................................... 246 Functional description................................................................ 246 Sales information....................................................................... 247 Activating the feature ................................................................ 247 LTE113: Cell Bandwidth - 15 MHz..............................................247 Introduction to the feature.......................................................... 247 Benefits...................................................................................... 247 Requirements.............................................................................247 Software requirements............................................................... 247 Hardware requirements..............................................................248 Functional description................................................................ 248 Sales information....................................................................... 248 User interface.............................................................................248 Activating the feature................................................................. 249 LTE447: SW support for RF sharing GSM-LTE .........................249 Introduction to the feature.......................................................... 249 Benefits...................................................................................... 249 Requirements.............................................................................249 Software requirements............................................................... 249 Hardware requirements..............................................................250 Functional description................................................................ 250 Sales information....................................................................... 251 Activating the feature................................................................. 251 LTE1102: FFCC TRS External Filter for FXCA.......................... 252 Benefits...................................................................................... 252 Requirements.............................................................................252 Functional description................................................................ 252
© 2016 Nokia
15
LTE RL20, Feature Descriptions
6.7.4 6.7.5 6.7.6
16
System impacts..........................................................................254 LTE1102: FFCC TRS External Filter for FXCA management data.. 254 Sales information....................................................................... 255
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
List of Figures Figure 1
MME selection procedure...................................................................27
Figure 2
EPS bearer establishment by S1AP: Initial context setup procedure (Attach)............................................................................................... 34
Figure 3
EPS bearer establishment by S1AP: Initial context setup procedure (Service)............................................................................................. 35
Figure 4
EPS bearer establishment by S1AP:E-RAB setup request................ 36
Figure 5
EPS bearer release procedure by S1AP:E-RAB release procedure...... 36
Figure 6
EPS bearer establishment by S1AP: E-RAB setup request............... 66
Figure 7
Principle of ROHC.............................................................................. 74
Figure 8
Compressor States.............................................................................75
Figure 9
Decompressor States......................................................................... 75
Figure 10
EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Attach)............................................................................. 76
Figure 11
EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Service Request)............................................................. 77
Figure 12
EPS Bearer Establishment Procedure by S1AP: E-RAB Setup Procedure........................................................................................... 78
Figure 13
UE-AMBR Modification Procedure..................................................... 82
Figure 14
Message sequence and time delay during CSFB redirection........... 117
Figure 15
Tx power levels during graceful cell shutdown................................. 129
Figure 16
Service OAM overview..................................................................... 136
Figure 17
Ethernet Continuity Check and Ethernet Remote Defect Indication.137
Figure 18
Ethernet Alarm Indication Signal...................................................... 138
Figure 19
Ethernet Loopback........................................................................... 139
Figure 20
Ethernet Link Trace.......................................................................... 139
Figure 21
FlexiPacket Radio Connectivity solution...........................................147
Figure 22
FPR management data forwarding...................................................148
Figure 23
QoS aware Ethernet switching......................................................... 161
Figure 24
Chaining concept..............................................................................162
Figure 25
The Ethernet scheduling and shaping.............................................. 164
Figure 26
QoS scheduling for switched Ethernet transport interfaces-example for FTLB and FTIB................................................................................. 165
Figure 27
Signalling transport stack for multi-homed MME S1 interface..........178
Figure 28
Multi-homed MME............................................................................ 179
Figure 29
Subscribe trace general architecture................................................183
Figure 30
Trace files transfer between NetAct and iOMS.................................185
Figure 31
Top down upgrade approach............................................................ 189
Figure 32
Cell trace architecture.......................................................................201
Figure 33
Trace files transfer between NetAct and iOMS.................................203
DN0978033 Issue: 02N
© 2016 Nokia
17
LTE RL20, Feature Descriptions
18
Figure 34
LTE492: ANR....................................................................................215
Figure 35
Feature monitoring for LTE............................................................... 229
Figure 36
Concept of GSM and LTE concurrent mode.....................................250
Figure 37
Isometric view of the FFCC.............................................................. 253
Figure 38
Front view of the FFCC.................................................................... 254
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
List of Tables Table 1
RL20 Features - not supported by Flexi Zone Micro.......................... 24
Table 2
Software requirements for different network elements....................... 25
Table 3
Parameters for LTE2: S1 Flex............................................................ 28
Table 4
Software requirements for different network elements....................... 29
Table 5
Software requirements for different network elements....................... 30
Table 6
Sales information................................................................................32
Table 7
Software requirements for different network elements....................... 32
Table 8
Counters maintained by RAC............................................................. 37
Table 9
Parameters for the LTE7:Support of multiple EPS bearer.................. 38
Table 10
Counters for LTE7: Support of multiple EPS bearer........................... 39
Table 11
Software requirements for different network elements....................... 42
Table 12
Parameters for the LTE9: Service Differentiation............................... 45
Table 13
Parameters for AM RLC Poll Byte structure....................................... 45
Table 14
Parameters for QCI Translation Table structure................................. 47
Table 15
Parameters for profiles of RLC........................................................... 54
Table 16
Parameters for profiles of PDCP........................................................ 58
Table 17
Counters for the LTE9: Service differentiation.................................... 60
Table 18
Software requirements for different network elements....................... 62
Table 19
Parameters for the LTE10: EPS bearers for conversational voice feature................................................................................................ 67
Table 20
Counters for the LTE10: EPS bearers for conversational voice feature. 72
Table 21
Software requirements for different network elements....................... 73
Table 22
Modes of ROHC................................................................................. 75
Table 23
Parameters for the LTE11: Robust Header Compression.................. 79
Table 24
Software requirements for different network elements....................... 80
Table 25
Parameters for the LTE13: Rate Capping UL..................................... 82
Table 26
Parameters for the LTE13: Rate Capping DL..................................... 83
Table 27
Software requirements for different network elements....................... 84
Table 28
Hardware requirements for different network elements......................84
Table 29
Sales information................................................................................89
Table 30
Parameters for the LTE22: Emergency Call Handling........................ 89
Table 31
Counters for the LTE22: Emergency Call Handling............................ 90
Table 32
Software requirements for different network elements....................... 91
Table 33
Hardware requirements for different network elements......................91
Table 34
Sales information................................................................................97
Table 35
Parameters for the LTE54: Intra LTE Handover via S1...................... 97
Table 36
Counters for LTE 54: Intra LTE Handover via S1............................... 98
Table 37
Software requirements for different network elements..................... 100
DN0978033 Issue: 02N
© 2016 Nokia
19
LTE RL20, Feature Descriptions
20
Table 38
Hardware requirements for different network elements....................101
Table 39
Th1 and Th2 InterFreq are thresholds set by O&M.......................... 102
Table 40
Th2a InterFreq threshold set by O&M.............................................. 103
Table 41
Sales information..............................................................................105
Table 42
Parameters for the LTE55: LTE Inter-frequency Handover.............. 105
Table 43
Counters for the LTE55: LTE Inter-frequency Handover...................110
Table 44
Software requirements for different network elements......................111
Table 45
Hardware requirements for different network elements.................... 112
Table 46
Sales information.............................................................................. 113
Table 47
Parameters for the LTE703: DL adaptive closed loop MIMO for two antennas........................................................................................... 113
Table 48
Counters for the LTE703: DL adaptive closed loop MIMO for two antennas........................................................................................... 114
Table 49
Software requirements for different network elements..................... 115
Table 50
Parameters for the LTE562: CSFB to UTRAN or GSM via redirect....... 118
Table 51
Counters for the LTE562:CSFB to UTRAN or GSM via redirect...... 120
Table 52
Software requirements for different network elements..................... 121
Table 53
Parameters for the LTE819 Downlink Inter-cell Interference generation ..........................................................................................................123
Table 54
Software requirements for different network elements..................... 124
Table 55
Parameters for LTE870: Idle Mode Mobility from LTE to CDMA/eHRPD..................................................................................125
Table 56
Software requirements..................................................................... 127
Table 57
Configuration of parameters for the graceful cell shutdown procedure.. 128
Table 58
Minimum output power values for various radio units...................... 129
Table 59
Related existing parameters.............................................................131
Table 60
Sales information..............................................................................131
Table 61
Software requirements for different network elements..................... 134
Table 62
L-OAM capabilities........................................................................... 134
Table 63
Parameters for LTE140: Ethernet OAM............................................140
Table 64
Alarms for LTE140: Ethernet OAM................................................... 143
Table 65
Software requirements for different network elements..................... 146
Table 66
Software requirements for different network elements..................... 150
Table 67
Software requirements for different network elements..................... 152
Table 68
Parameters for LTE592: Link Supervision with BFD........................ 153
Table 69
Alarms for LTE592: Link Supervision with BFD................................ 158
Table 70
Software requirements for different network elements..................... 160
Table 71
Parameters for LTE649: QoS Aware Switching................................166
Table 72
Mesurement and counters for LTE649: QoS Aware Switching.........176
Table 73
Software requirements for different network elements..................... 178
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 74
Parameters for LTE775: SCTP Multi-Homing...................................180
Table 75
Alarms for LTE775: SCTP Multi-Homing.......................................... 180
Table 76
Software requirements..................................................................... 181
Table 77
Sales information..............................................................................186
Table 78
Related alarms................................................................................. 186
Table 79
New parameters............................................................................... 187
Table 80
Software requirements for different network elements..................... 188
Table 81
Alarms for the LTE185: System Upgrade feature............................. 197
Table 82
Software requirements..................................................................... 199
Table 83
Sales information..............................................................................204
Table 84
Related alarms................................................................................. 205
Table 85
New parameters............................................................................... 205
Table 86
Parameters for the LTE475: Automatic iOMS Resiliency................. 209
Table 87
Software requirements......................................................................211
Table 88
New parameters............................................................................... 213
Table 89
Sales information..............................................................................213
Table 90
Software requirements for different network elements..................... 214
Table 91
Interdependencies between features............................................... 221
Table 92
Sales information..............................................................................223
Table 93
Parameters for LTE492: Automatic Neighbor Relation.....................223
Table 94
Software requirements..................................................................... 226
Table 95
Sales information..............................................................................227
Table 96
Software requirements for different network elements..................... 228
Table 97
Software requirements for different network elements..................... 231
Table 98
Software requirements..................................................................... 232
Table 99
Software requirements..................................................................... 233
Table 100
Parameters for the LTE830: LTE Automatic Lock feature................ 235
Table 101
Software requirements..................................................................... 236
Table 102
Sales information..............................................................................237
Table 103
New counters....................................................................................237
Table 104
Software requirements for different network elements..................... 240
Table 105
Sales information..............................................................................241
Table 106
Parameters for LTE87: FXCA Flexi 3-sector RF Module 850...........241
Table 107
Software requirements for different network elements..................... 242
Table 108
Sales information..............................................................................243
Table 109
Software requirements for different network elements..................... 244
Table 110
Sales information..............................................................................245
Table 111
Parameters for LTE103: Flexi RRH 2TX 730................................... 245
Table 112
Software requirements for different network elements..................... 246
Table 113
Sales information..............................................................................247
DN0978033 Issue: 02N
© 2016 Nokia
21
LTE RL20, Feature Descriptions
22
Table 114
Software requirements for different network elements..................... 247
Table 115
Sales information..............................................................................248
Table 116
Existing parameters related to LTE113.............................................248
Table 117
Software requirements for different network elements..................... 250
Table 118
Sales information..............................................................................251
Table 119
Software requirements..................................................................... 252
Table 120
Sales information..............................................................................255
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Summary of changes
Summary of changes Changes between 02M (2016-05-23, RL30) and 02N (2016-06-29, FDD-LTE16A) The following feature description has been updated: •
LTE492: ANR
Changes between 02L (2016-01-26, RL30) and 02M (2016-05-23, RL70) The following feature description has been updated: •
LTE7: Support of multiple EPS bearer
Changes between 02K (2015-06-19, RL30) and 02L (2016-01-26, RL30) The following feature description has been updated: •
DN0978033 Issue: 02N
LTE2: S1 Flex
© 2016 Nokia
23
RL20 Features - not supported by Flexi Zone Micro
LTE RL20, Feature Descriptions
1 RL20 Features - not supported by Flexi Zone Micro The following features are not supported by Flexi Zone Micro: Table 1
RL20 Features - not supported by Flexi Zone Micro Features
24
Category
LTE87: FXCA Flexi 3-sector RF Module 850
BTS
LTE101: FXEA Flexi 3-sector RF Module 1800
BTS
LTE103: FRLB Flexi RRH 2TX 730
BTS
LTE104: FHEA Flexi RRH 2TX 1800
BTS
LTE185: System Upgrade
Operability
LTE447: SW support for RF sharing GSM-LTE
BTS
LTE491: FlexiPacket Radio Connectivity
Transport
LTE521: Security for Ethernet ports on FCM/FSM2
Operabiliy
LTE564: IPSec on FTIB
Operabiliy
LTE677: FRNA_B Flexi 1600 MHz RF solution
BTS
LTE1102: FFCC TRS External Filter for FXCA
BTS
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
2 Radio resource management and telecom features 2.1 LTE2: S1 Flex 2.1.1 Introduction to the feature The S1 Flex allows the eNB to establish multiple S1 links. The Flexi Multiradio BTS can be connected to a maximum of 16 MMEs. A load balancing algorithm is used to balance the load between the MMEs. UEs entering the MME pool are distributed to the different MMEs.
2.1.2 Benefits The S1 Flex feature provides network redundancy and traffic load sharing. With S1 Flex the eNB is allowed to connect to a maximum of 16 MMEs. The operator can increase the overall network availability.
2.1.3 Requirements 2.1.3.1
Software requirements The following software is required for this feature. Table 2
Software requirements for different network elements
Network element
2.1.3.2
Required software release
System release
RL20; RL15TD
eNodeB
LBTS2.0; TD-LBTS1.0
MME
NS10 CD2; NS10 CD4
SAE GW
NG10 CD4
UE
3GPP release 8
NetAct
–
Hardware requirements This feature requires Flexi System modules which support LTE.
DN0978033 Issue: 02N
© 2016 Nokia
25
Radio resource management and telecom features
LTE RL20, Feature Descriptions
2.1.4 Functional description The eNB supports multiple S1 links when feature S1 Flex is activated.
2.1.4.1
S1 interface With S1 Flex support, the eNB may be connected to a maximum of 16 MMEs. When an associated IP address for the MME is available, the eNB considers that specific MME as allowed. If an additional MME becomes configured, eNB performs the S1 link activation procedure for this MME. When the MME is removed from the set of configured MMEs, the eNB performs the S1 link deactivation procedure for this MME. An S1 interface modification occurs each time when the set of available MMEs changes. If the S1 Flex feature is deactivated, the eNB performs the S1 link deactivation procedure for each MME except for the MME that is considered as the main MME. The main MME is configured in LNMME-0. SCTP associations The eNB starts/terminates all associations towards any MME at one eNB SCTP endpoint. That means that the eNB supports at one S1-MME SCTP endpoint up to 16 SCTP associations towards peer MMEs (one SCTP association for each MME). Each MME peer endpoint is identified with the peer MME primary IP address. When the S1 Flex is deactivated, the eNB keeps only the SCTP association towards the main MME. For more information on SCTP, see subchapter SCTP layer in LTE Datapath Management.
2.1.4.2
MME selection During the UE connection establishment, eNB selects MME from the set of active MMEs. The choice is based on: • • •
PLMN IDs (MME support of PLMNs, which UE wants to connect to) registeredMME value (available if the UE has already registered with a MME) SAE Temporary Mobile Subscriber Identity (S-TMSI)
Value of registeredMME parameter is provided by one of the following messages: • •
RRC CONNECTION SETUP COMPLETE RRC CONNECTION REQUEST, within the optional S-TMSI
The Figure 1: MME selection procedure provides an overview of MME selection procedure after the RRC connection setup is completed.
26
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Figure 1
Radio resource management and telecom features
MME selection procedure
RRCConnectionSetupComplete
DeriveselectedPLMNidentity, S-TMSIandregisteredMME
S-TMSIpresent
SearchforMMECodeofS-TMSI insetofMMECsofLTERAT
S-TMSInotpresent registeredMMEnotinmessage
SearchforselectedPLMNidentityinsetof servedPLMNidentitiesofallactiveMMEs
SearchforregisteredMMEinsetof servedGUMMEIsofallactiveMMEs MMEnotfound
SeveralMMEfound registeredMMEinRRCmessage
MMEfoundinset MMEfoundinset MMEfoundinset
SelectedPLMNnot servedbyMME
MMEnotfound
PerformLoadbalancing SelectedPLMNservedbyMME MMEselected MMEselected
2.1.4.2.1
MMEselected
MMEselected
ReleaseRRCConnection
Load balancing A load-balancing algorithm balances the load between MMEs. UEs entering the MME pool are distributed to different MMEs with probabilities that correspond to the assigned weights. The eNB performs the S1 connection setup load-balancing among the MMEs. Only active MMEs for which the PLMN ID is one of the served PLMNs are considered. Selection is based on weighting information provided by each MME during the S1 setup. Relative MME capacity is included in S1AP: S1 SETUP RESPONSE message. Algorithm is re-initialized by the following triggers: • • •
successful S1 setup S1 reset S1- MME failure
2.1.5 Sales information This feature belongs to the Application Software (ASW) product structure class.
DN0978033 Issue: 02N
© 2016 Nokia
27
Radio resource management and telecom features
LTE RL20, Feature Descriptions
2.1.6 User interface 2.1.6.1
Parameters The following table shows the parameters implemented for the feature LTE2: S1 Flex.
Table 3
Parameters for LTE2: S1 Flex
Name
Object
Description
Range
Default
actS1Flex
LNBTS
Feature activation flag for LTE2: S1 Flex.
disabled (0) enabled (1)
1
ipAddrPrim
LNMME
Transport network IPv4/v6 address of the Mobility Management Entity (MME) primary interface
7...45 characters
-
administrativeState
LNMME
Administrative state of the LNMME S1 link
unlocked (1) locked (3)
unlocked
lnMmeId
LNMME
Setting of LTE mobility management identifier
0...31
-
transportNwId
LNMME
Setting of Transport network identifier
0...1
-
2.1.6.2
Alarms There are no Alarms related to this feature.
2.1.6.3
Measurements and counters There are no measurements and counters related to this feature.
2.1.7 Activating and configuring the feature Note that feature activation flag for LTE2: S1 Flex, activates also LTE4: Multi-Operator Core Network feature. For activating and configuring the feature, see Feature Activation Documentation
2.1.8 Abbreviations 2.1.8.1
0–Z
GUMMEI Global Unique Mobility Management Entity Identifier
28
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
PLMN Public Land Mobile Network
RAT Radio Access Technology
S-TMSI SAE Temporary Mobile Subscriber Identity
2.2 LTE4: RAN Sharing 2.2.1 Introduction to the feature The Flexi Multiradio BTS can be connected simultaneously to the EPCs of six different operators . This means that the LTE E-UTRAN can be shared between mobile network operators. Different core networks can be connected to the common shared eNBs.
2.2.2 Benefits The operators are able to share the resources of one Flexi Multiradio BTS.
2.2.3 Requirements 2.2.3.1
Interdependencies between features Feature LTE2: S1 Flex needs to be activated.
2.2.3.2
Software requirements The following software is required for this feature. Table 4
Software requirements for different network elements
Network element
DN0978033 Issue: 02N
Required software release
System release
RL40
Flexi Multiradio BTS
LBTS2.0
Flexi Multiradio 10 BTS
LBTS4.0
MME
–
© 2016 Nokia
29
Radio resource management and telecom features
Table 4
LTE RL20, Feature Descriptions
Software requirements for different network elements (Cont.)
Network element
2.2.3.3
Required software release
SAE GW
–
UE
3GPP release 8
NetAct
–
Hardware requirements This feature requires Flexi System modules which support LTE.
2.2.4 Requirements 2.2.4.1
Interdependencies between features Feature LTE2: S1 Flex needs to be activated.
2.2.4.2
Software requirements The following software is required for this feature. Table 5
Software requirements for different network elements
Network element
2.2.4.3
Required software release
System release
RL40
Flexi Multiradio BTS
LBTS2.0
Flexi Multiradio 10 BTS
LBTS4.0
MME
–
SAE GW
–
UE
3GPP release 8
NetAct
–
Hardware requirements This feature requires Flexi System modules which support LTE.
2.2.5 Functional description
30
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.2.5.1
Radio resource management and telecom features
Functional overview The Flexi Multiradio BTS can be connected simultaneously to the EPCs of six different operators - Public Land Mobile Networks (PLMNs). This is done via the S1 Flex mechanism which allows BTS to establish multiple S1 links. The operators are sharing the entire Flexi Multiradio BTS as well as the OSS and the transport. The assignment of PLMN IDs to the shared cells is done via SIB1 configuration. The primary PLMN ID needs to be configured commonly for all cells. Individual PLMN IDs can be set to 'reserved for operator use' in order support MORAN solutions. The PLMN information provided by the S1 setup is used to select the correct S1 interface for the S1AP:INITIAL UE message. All enabled BTS features are available for all operators. All O&M settings, including neighbor cells lists, are common for operators in case of shared cells. The same IPsec is applied on the transport for all operators.
2.2.5.2
Feature activation The LTE4: RAN Sharing feature is activated, when the LTE2: S1 Flex is active. Use activation instructions for LTE2: S1 Flex feature. See, Feature Activation Documentation.
2.2.6 System impact 2.2.6.1
Interdependencies between features The feature LTE2: S1 Flex needs to be enabled.
2.2.7 LTE4: RAN Sharing management data 2.2.7.1
Alarms There are no alarms related to this feature.
2.2.7.2
Measurements and counters There are no measurements and counters related to this feature.
2.2.7.3
Key performance indicators There are no key performance indicators related to this feature.
2.2.7.4
Parameters There are no parameters related to this feature.
DN0978033 Issue: 02N
© 2016 Nokia
31
Radio resource management and telecom features
2.2.7.5
LTE RL20, Feature Descriptions
Sales information Table 6
Sales information
BSW/ASW
License control in network element
License control attributes
ASW
-
-
2.3 LTE7: Support of multiple EPS bearer 2.3.1 Introduction To The Feature The eNB supports a number of bearer combinations. The operator can offer and the customer can use a combination of different services for one UE. With this feature “LTE7: Support of multiple EPS bearer” it is possible to support of up to 4 AM DRB (acknowledged mode data radio bearer) bearers per UE. Furthermore there can be two signaling bearers (SRB) combined. Each combinations of SRB1, SRB2 and up to the 4 AM DRBs are allowed.
2.3.2 Benefits The operator can offer attractive service combinations as multiple services, that can be used at one UE.
2.3.3 Requirements 2.3.3.1
Software Requirements The following software is needed: Table 7
Software requirements for different network elements
Network element
32
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
NS20
SAE GW
NG20
UE
3GPP release 8
NetAct
–
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.3.3.2
Radio resource management and telecom features
Hardware Requirements This feature does not require any new or additonal hardware.
2.3.4 Functional Description An EPS-bearer (Evolved packet system bearer) is an information transmission path of defined capacity , delay and bit error rate. It is used between MME, eNB and the UE. LTE distinguishes between two types of bearers: •
•
default bearer One default bearer is established when the UE connects to the MME (and the backbone PDN (packet data network)) and remains established throughout the lifetime of the connection to provide the UE with always-on IP connectivity to that PDN. dedicated bearer Any additional EPS bearer that is established for the same packet data network connection is referred to as dedicated bearer.
Multiple DRBs (data radio bearers) can be either multiple default EPS bearers or a combination of default and dedicated bearers. The type of the bearer is transparent to the eNB. The radio admission is extended by additional check of the total number of DRB per cell and maximum number of DRB per UE. The different bearers per UE can have the same or different QCIs (Quality of Service Class identifiers). The QCI is an index that idenitifies the QoS attributes: priority, delay and loss rate. The eNB supports the following scenarios for establishing and releasing EPS bearers: • • • •
establish individual EPS bearers, release individual EPS bearers, add multiple EPS bearers to existing EPS bearers, release multiple EPS bearers from existing EPS bearers.
There is one restriction regarding bearers having the same QCI, i.e. there can only be one bearer of a certain QCI per PDN; multiple traffic flows requiring the same QCI are already merged into a single bearer in EPC. Bearers of the same QCI can exist to different bearers. The downlink scheduler provides prioritization among multiple non-GBR (non Guaranteed Bit Rate) EPS-bearers in order to avoid starvation of downlink traffic. The single or multiple EPS bearers are established or released by the according S1AP procedure. In Figure 2: EPS bearer establishment by S1AP: Initial context setup procedure (Attach) a message flow is shown for the establishing of one or more EPS bearers with the S1AP: Initial Context Setup Request (Attach). This procedure is taken for the first action. The operator can establish one default + optional additional bearers. This message can contain UE context data (e. g. UE radio capabilities, security information).
DN0978033 Issue: 02N
© 2016 Nokia
33
Radio resource management and telecom features
Figure 2
LTE RL20, Feature Descriptions
EPS bearer establishment by S1AP: Initial context setup procedure (Attach)
The message flow for an EPS bearer establishment with the S1AP: Initial Context Setup Request (Service Request).is shown in Figure 3: EPS bearer establishment by S1AP: Initial context setup procedure (Service).
34
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Figure 3
Radio resource management and telecom features
EPS bearer establishment by S1AP: Initial context setup procedure (Service)
The message flow for the establishment of an additional single or multiple EPS bearer with the S1AP: E-RAB setup request (E-RAB: E-UTRAN Radio ACCESS) is shown in Figure 4: EPS bearer establishment by S1AP:E-RAB setup request. The E-RAB Setup procedure supports: • • • •
DN0978033 Issue: 02N
Check of activation of the multi-bearer feature. Check of the support of the new bearer configuration. Reconfiguration of the rate capping function, if a new UE-AMBR (aggregated maximum bit rate) has been provided by MME. Setup of an additional single or multiple DRBs by the RRC Connection Reconfiguration procedure.
© 2016 Nokia
35
Radio resource management and telecom features
Figure 4
LTE RL20, Feature Descriptions
EPS bearer establishment by S1AP:E-RAB setup request
In Figure 5: EPS bearer release procedure by S1AP:E-RAB release procedure another message sequence chart is shown: The release of a bearer with the S1AP: E-RAB release procedure. This S1AP: E-RAB release procedure supports the release of a single or multiple EPS bearers. This includes: • • •
Check, whether at least one non-GBRremains. Reconfiguration of the rate capping functions if a new UE-AMBR(aggregated maximum bitrate) has been provided by MME, Release of a single or multiple DBRs by the RRC Connection Reconfiguration procedure.
Figure 5
EPS bearer release procedure by S1AP:E-RAB release procedure
UE
eNB
MME
TriggeringofEPSBearerdeactivation
RRRC:RCConnectionReconfiguration
S1AP:E-RABRELEASECOMMAND
DRBRelease
RRC:RRCConnectionReconfigurationComplete
RRC: ULInformationTransfer
S1AP: RABRELEASERESPONSE
S1AP: UL NAS TRANSPORT Postprocessing
This feature has influence on different functions as listed below:
36
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
•
Radio resource management and telecom features
Radio Admission Control (RAC) RAC checks the threshold maxNumActDrb per cell. Therefore the counter NumActDrb counts the total number of DRBs. The RAC will be involved when DRBs are setup, when setups are aborted, when DRBs are released or UEs leave the cell. Each admission request is processed within RAC according to the “all or nothing” principle, e.g. if n (n > 1) DRBs shall be admitted and at least one DRB cannot be admitted, the complete request is rejected. To meet the right decisons RAC must maintain counters from Table 8: Counters maintained by RAC and must compare them to system internal thresholds. Table 8
Counters maintained by RAC
counter
•
NumRRC
counter for SRB1 connected UEs
NumActUE
counter for active UEs (having signalling connection and a default DRB)
NumActDrb
counter for all user DRBs (QCI independant) in the cell
The above mentioned threshold maxNumActDrb (and others like maxNumActUe, maxNumRrc..) are retrieved from the OAM database at system setup. UL / DL Scheduler The UL / DL Scheduler is extended by the followíng functions: – – – –
• •
•
•
•
DN0978033 Issue: 02N
description
The UL / DL Scheduler considers up to four DRBs (GBR or not-GBR) per UE. DRBs of one UE can have the same or different QCI. The UL/ DL Scheduler supports proportional fair treatment of different UEs depending on data availability of (multiple) radio bearers (inter UE fairness). The UL / DL Scheduler suppports proportional fair treatment of different UEs depending on radio channel quality.
AS (Access Stratum) Security Ciphering and integrity protection for multiple DRBs are supported. Initial Context Setup Procedure The eNB supports the establishment of multiple EPS bearers at the Initial Context Setup - Procedure (see Figure 2: EPS bearer establishment by S1AP: Initial context setup procedure (Attach) and Figure 3: EPS bearer establishment by S1AP: Initial context setup procedure (Service)). E-RAB Setup and E-RAB Release The eNB supports the establishment and release of additional single or multiple EPS bearers (see Figure 4: EPS bearer establishment by S1AP:E-RAB setup request and Figure 5: EPS bearer release procedure by S1AP:E-RAB release procedure). Handover The handover procedures ( intra eNB and inter eNB) support the handover for multiple non GBR bearers. If the decision is made to perform an intra eNB handover while a bearer management procedure (i.e. bearer setup or release) is ongoing, the bearer management continues. The intra eNB - handover is delayed and will be started after the completion of the bearer management procedure. PDCP functionality The new timer S1 retard timer is introduced.
© 2016 Nokia
37
Radio resource management and telecom features
•
LTE RL20, Feature Descriptions
MAC Multiplexing The eNB supports the multiplexing of data of multiple logical channels (corresponding to data radio bearers as well as to signalling radio bearers) into a single MAC PDU in DL direction. In UL direction the eNB supports the reception and demultiplexing of MAC PDUs containing multiplexed data from multiple logical channels.
2.3.5 System Impacts This feature is precondition for the feature LTE10: EPS bearers for conversational voice.
2.3.6 Sales Information This feature is optional.
2.3.7 User Interface 2.3.7.1
Parameters Table 9: Parameters for the LTE7:Support of multiple EPS bearer shows the parameters implemented for the feature LTE7: Support of multiple EPS bearers.
Table 9
Parameters for the LTE7:Support of multiple EPS bearer
Name
Short name
Object
Description
Range / Step
Default value
End-Tag maximum AM
tagMaxAM
LNBTS
The maximum bound for tag timer calculation valid for RLCAM DRBs.
0...1000 ms, step 1 ms
10 ms
End-Tag maximum UM
tagMaxUM
LNBTS
The maximum bound for tag timer calculation valid for RLCUM DRBs.
0...1000 ms, step 1 ms
10 ms
Activate Multiple Bearers
actMultBearers
LNBTS
This parameter activates the support of multiple EPS Bearers.
UL Scheduler FD Type
ulsFdPrbAssignAl LNCEL g
Scheduler Type for Frequency Domain (FD) schedulerDefines the scheduling method which shall be applied in frequency domain for the UL scheduler- the Round Robin FD scheduler assigns the physical resources equally fair to the UEs selected by the TD scheduler until the PRBs are sufficient for the service or the physical resources of the cell are exhaust- the FD Exhaustive FD scheduler assigns in the priority sequence defined by the TD scheduler as
38
© 2016 Nokia
true
RoundRobinF ExhaustiveF D (0), D (1) ExhaustiveFD (1)
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 9
Radio resource management and telecom features
Parameters for the LTE7:Support of multiple EPS bearer (Cont.)
Name
Short name
Object
Description
Range / Step
Default value
many physical resources as possible to the UEs until the number of PRBs are sufficient for the service or the resources of the cell are exhaust
2.3.7.2
Measurements and Counters Table 10: Counters for LTE7: Support of multiple EPS bearer shows the counters for LTE7: Support of multiple EPS bearer Table 10
Counters for LTE7: Support of multiple EPS bearer
PI ID
DN0978033 Issue: 02N
Counter long name (short name)
Description
M8000C17
E-RAB setup completions (E_RAB_SETUP_SUCC)
The number of successful ERAB Setup Completions
M8000C18
E-RAB setup failures due to radio network layer problems (E_RAB_SETUP_FAIL_RNL)
The number of successful ERAB Setup Failures due to radio network layer problems
M8000C19
E-RAB setup failures due to The number of successful Etransport layer problems RAB Setup Failures due to (E_RAB_SETUP_FAIL_TRAN transport layer problems SPORT)
M8000C20
E-RAB setup failures due to resource problems (E_RAB_SETUP_FAIL_RES OURCE)
M8000C21
E-RAB setup failures due to The number of successful Eother reasons RAB Setup Failures due to (E_RAB_SETUP_FAIL_OTHE other reasons R)
M8000C22
E-RAB setup requests (E_RAB_SETUP_ATT)
The number of E-RAB Setup Requests
M8006C16
EPS Bearer setup failures due to Pending Handover (EPS_BEARER_SETUP_FAI L_HO)
The number of EPS bearer setup failures due to Handover Pending reason. Each bearer of the E-RAB Failed to Setup List IE is counted.
© 2016 Nokia
The number of successful ERAB Setup Failures due to resource problems
39
Radio resource management and telecom features
Table 10
Counters for LTE7: Support of multiple EPS bearer (Cont.)
PI ID
40
LTE RL20, Feature Descriptions
Counter long name (short name)
Description
M8006C17
Initial EPS Bearer setup attempts for QCI1 (EPS_BEARER_STP_ATT_IN I_QCI_1)
The number of initial EPS bearer setup attempts per QCI1. Each bearer of the ERAB to Be Setup List IE is counted.
M8006C18
Initial EPS Bearer setup attempts for non-GBR (EPS_BEAR_STP_ATT_INI_ NON_GBR)
The number of initial EPS bearer setup attempts per non-GBR. Each bearer of the E-RAB to Be Setup List IE is counted.
M8006C26
Additional EPS Bearer setup attempts for QCI1 (EPS_BEARER_STP_ATT_A DD_QCI_1)
The number of additional EPS bearer setup attempts per QCI1. Each bearer of the ERAB to Be Setup List IE is counted.
M8006C35
Initial EPS Bearer setup completions for QCI1 (EPS_BEARER_STP_COM_I NI_QCI1)
The number of initial EPS bearer setup completions per QCI1. Each bearer of the ERAB Setup List IE is counted.
M8006C36
Initial EPS Bearer setup completions for non-GBR (EPS_BEAR_STP_COM_INI_ NON_GBR)
The number of initial EPS bearer setup completions per non-GBR. Each bearer of the E-RAB Setup List IE is counted.
M8006C44
Additional EPS Bearer setup completions for QCI1 (EPS_BEAR_SET_COM_AD DIT_QCI1)
The number of additional EPS bearer setup completions for QCI1. Each bearer of the ERAB Setup List IE is counted.
M8006C89
EPC initiated EPS Bearer Release requests for QCI1 due to Normal release by UE(EPC_EPS_BEAR_REL_R EQ_N_QCI1)
The number of EPC-initiated EPS Bearer Release requests for QCI1 due to normal release by UE. Each bearer of the E-RAB to be Released List IE is counted.
M8006C98
EPC initiated EPS Bearer Release requests for QCI1 due to Detach procedure by UE or MME (EPC_EPS_BEAR_REL_REQ _D_QCI1)
The number of EPC-initiated EPS Bearer Release requests for QCI1 due to the Detach procedure by the UE or the MME. Each bearer of the ERAB to be Released List IE is counted.
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 10
Radio resource management and telecom features
Counters for LTE7: Support of multiple EPS bearer (Cont.)
PI ID
DN0978033 Issue: 02N
Counter long name (short name)
Description
M8006C107
EPC initiated EPS Bearer Release requests per QCI1 due to Radio Network Layer cause (EPC_EPS_BEAR_REL_REQ _R_QCI1)
The number of EPC-initiated EPS Bearer Release requests for QCI1 due to the Radio Network Layer cause. Each bearer of the E-RAB to be Released List IE is counted.
M8006C116
EPC initiated EPS Bearer Release requests for QCI1 due to Other causes (EPC_EPS_BEAR_REL_REQ _O_QCI1)
The number of EPC-initiated EPS Bearer Release requests for QCI1 due to Other causes. Each bearer of the E-RAB to be Released List IE is counted.
M8006C125
eNB initiated EPS Bearer Release requests for QCI1 due to normal release (ENB_EPS_BEAR_REL_REQ _N_QCI1)
The number of eNB-initiated EPS Bearer Release requests for QCI1 due to the Normal release. In case of a UE context release request, all the established EPS Bearers are counted.
M8006C134
eNB initiated EPS Bearer Release requests for QCI1 due to Radio Network Layer cause (ENB_EPS_BEAR_REL_REQ _R_QCI1)
The number of eNB-initiated EPS Bearer Release requests for QCI1 due to Radio Network Layer cause. In case of a UE context release request, all the established EPS Bearers are counted.
M8006C143
eNB initiated EPS Bearer Release requests for QCI1 due to Other causes (ENB_EPS_BEAR_REL_REQ _O_QCI1)
The number of eNB-initiated EPS Bearer Release requests for QCI1 due to Other causes . In case of a UE context release request, all the established EPS Bearers are counted.
M8006C152
eNB initiated EPS Bearer Release requests for QCI1 due to Transport Layer Cause (ENB_EPS_BEAR_REL_REQ _T_QCI1)
The number of eNB-initiated EPS Bearer Release requests for QCI1 due Transport Layer Cause - Transport Resource UnavailableCause.
M8006C161
eNB initiated EPS Bearer Release requests for QCI1 due to Radio Network Layer cause Redirect (ENB_EPS_BEAR_REL_REQ _RD_QCI1)
The number of eNB-initiated EPS Bearer Release requests for QCI1 due Redirect (release due to RNL EUTRAN generated reason or RNL Inter-RAT Redirection )
© 2016 Nokia
41
Radio resource management and telecom features
LTE RL20, Feature Descriptions
2.4 LTE9: Service Differentiation 2.4.1 Introduction to the feature This feature introduces differentiation of five different non Guaranteed Bit Rate (GBR) QoS Class Indicator (QCI) classes with relative scheduling weights.
2.4.2 Benefits Different non-GBR QoS classes can be efficiently supported.
2.4.3 Requirements 2.4.3.1
Software requirements Table 11
Software requirements for different network elements
Network element
2.4.3.2
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
NS20
SAE GW
NG20
UE
3GPP release 8
NetAct
–
Hardware requirements This feature requires no new or additional hardware.
2.4.4 Functional description With the Flexi Multiradio BTS service differentiation functionality, it is possible to assign relative scheduling weights for each non GBR QCI on BTS level. The relative weight will be considered by the uplink and the downlink scheduler. It also brings in the possibility to define three different Radio Link Control (RLC) / Packet Data Convergence Protocol (PDCP) profiles per BTS which can be assigned to different QCIs. The operator can enable/disable the support of individual QCIs. The LTE9: Service Differentiation feature is one of the Quality of Service features. It depends on the framework that comes with the support of multiple bearers, see LTE7: Support of multiple EPS bearer. Service differentiation of non-GBR bearers supports the following functionalities:
42
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
• • •
Radio resource management and telecom features
Configurable weight values per QCI Consideration of weight values in UL and DL scheduling Consideration of weight values in MAC multiplexing in DL
Feature characteristics Characteristics for the QoS features are mainly determined by the network deployment scenarios of features and UE mobility. With LTE9: Service Differentiation feature, the differentiation of non-GRB bearers with QCI from {5, 6, 7, 8, 9} via configurable weight values is introduced. Support of each QCI can be enabled and disabled by O&M. If the feature is not activated, all bearers are considered with the same default value. The default values are taken from the parameter set of QCI9. Characteristics of the feature are described below: •
•
•
•
Non-GBR service differentiation for different UEs Several UEs become active in one cell under identical radio conditions such that the cell is under load. Each UE has a single (or multiple) non-GBR bearer established but the QCI(s) of the single (or the multiple) bearer(s) is different between different UEs. There are no limitations to the traffic arrival for the established bearers. Service differentiation between UEs is performed by considering scheduling weights in schedulers (uplink and downlink). Non-GBR service differentiation in downlink for a single UE In a cell under load, multiple bearers with different QCIs are established for a UE. Service differentiation is performed by using a weighted round robin approach in logical channel prioritization in DL (logical channel prioritization in UL is defined by 3GPP standard and UE responsibility, prioritized bit rate setting, is used to prevent bearer starvation). There are no limitations to the traffic arrival for the established bearers. Establishment of a bearer when specific QCI is disabled Service requests for QCI which are disabled are rejected. EPC requests for a connected UE establishment of a bearer with a specific QCI different from the default QCI. Modification of QCI specific weight values A set of QCI specific weight values is configured in the eNodeB. Bearers of the same or of different UEs are served according to the configured weight values. The specific weight value for one or several QCIs is/are modified to a different value via the management tool (NetAct). Weight values for already established bearers remain unchanged. Modified QCI specific weight values are applied for new UEs in the cell or for establishment of new bearers for existing UEs.
UL Scheduler and DL Scheduler The UL Scheduler and DL Scheduler introduce service dependent weights being used in the scheduling metric to differentiate between different UEs or different bearers of the same UE. The eNodeB supports service differentiation for non-GBR data radio bearers in UL and DL scheduling: • •
UL/DL scheduler considers (configurable) QCI-specific relative weight values as provided by the control plane in scheduling UL/DL scheduler supports relative fair treatment of different UEs depending on weight values and data availability of a single or multiple data radio bearer
MAC Multiplexing
DN0978033 Issue: 02N
© 2016 Nokia
43
Radio resource management and telecom features
LTE RL20, Feature Descriptions
The eNodeB supports multiplexing of data of multiple logical channels (corresponding to data radio bearers as well as to signalling radio bearers) into a single MAC PDU in DL. The eNodeB supports service differentiation for Non-GBR data radio bearers in MAC multiplexing and logical channel prioritization in DL: •
•
For multiple bearers for one UE, MAC multiplexing and logical channel prioritization in DL considers (configurable) QCI-specific relative weight values as being provided by control plane Logical channel prioritization in DL supports long term relative fair treatment of multiple bearers of one UE depending on bearers data availability (intra-UE fairness)
Priority handling between logical channels of one UE The priority handling between logical channels of a UE is performed in a subframe in which the UE is allocated resources for a new transmission. The following input parameters are required: • •
QCI weight (or scheduling weight) for logical channels of Non-GBR type The transport block size (TBS) in bits allocated to the UE. TBS is determined by the number of PRBs/RBGs allocated to the UE and MCS used.
The scheduling procedure of logical channels of a UE is initialized as soon as a UE is admitted and a bearer is established in a cell. Allocate resources to Non-GBR bearers of the UE according to scheduling weights All the Non-GBR logical channels (QCI6-9, or QCI5 with schedulType=”NON-GBR”) are served according to a weighted round robin (WRR) method. A scheduling sequence is generated of all the established Non-GBR logical channels according to the QCI weights of each non-GBR logical channel of UE using WRR method. The WRR method determines which bearer to select for filling the transport block, whereas the amount of data taken from one bearers is not limited which in turn leads to a WRR like allocation of resources to bearers (given same traffic arrival behaviour for the bearers) in averge in the long term.
2.4.5 System impacts The feature has no additional impacts on the system.
2.4.6 Sales information The LTE9: Service Differentiation feature belongs to the Application Software (ASW) product structure class.
2.4.7 User interface 2.4.7.1
Parameters The following tables shows the implemented parameters for LTE9: Service Differentiation.
44
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 12
Name
Radio resource management and telecom features
Parameters for the LTE9: Service Differentiation
Short name
Object
Description
Activate actNonGbrService LNBTS NonGBR Diff Service Differentiation
This parameter activates the Service Differentiation for nonGBR Bearers.
Prioritized Bit Rate NonGBR
Prioritized Bit Rate for nonGBR bearersThis prioritized bit rate is used by UE for the UL scheduling algorithm according [36.321].
Table 13
Name
pbrNonGbr
LNBTS
Range / Step
Default value true
0kbps (0), 8kbps (1), 16kbps (2), 32kbps (3), 64kbps (4), 128kpbs (5), 256kbps (6)
16kbps (2)
Parameters for AM RLC Poll Byte structure
Short name
Object
Description
Range / Step
Default value
AM RLC Poll Byte Table 1
amRlcPBTab1
LNBTS
AM RLC Poll Byte Table for UE Category 1. It is used to obtain the UL pollByte and DL pollByte values for UE category 1.
DL Poll Byte
dlPollByte
LNBTS
AM RLC Poll Byte value in DL direction for UE category 1.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
25kB (0)
UE Category
ueCategory
LNBTS
Category of UE.
1...1, step 1
1
UL Poll Byte
ulPollByte
LNBTS
AM RLC Poll Byte value in UL direction for UE category 1.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
25kB (0)
AM RLC Poll Byte Table 2
amRlcPBTab2
LNBTS
AM RLC Poll Byte Table for UE Category 2. It is used to obtain the UL pollByte and DL pollByte values for UE category 2.
DL Poll Byte
dlPollByte
LNBTS
AM RLC Poll Byte value in DL direction for UE category 2.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9),
25kB (0)
DN0978033 Issue: 02N
© 2016 Nokia
45
Radio resource management and telecom features
Table 13
Name
LTE RL20, Feature Descriptions
Parameters for AM RLC Poll Byte structure (Cont.)
Short name
Object
Description
Range / Step
Default value
1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14) UE Category
ueCategory
LNBTS
Category of UE.
2...2, step 1
2
UL Poll Byte
ulPollByte
LNBTS
AM RLC Poll Byte value in UL direction for UE category 2.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
25kB (0)
AM RLC Poll Byte Table 3
amRlcPBTab3
LNBTS
AM RLC Poll Byte Table for UE Category 3. It is used to obtain the UL pollByte and DL pollByte values for UE category 3.
DL Poll Byte
dlPollByte
LNBTS
AM RLC Poll Byte value in DL direction for UE category 3.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
50kB (1)
UE Category
ueCategory
LNBTS
Category of UE.
3...3, step 1
3
UL Poll Byte
ulPollByte
LNBTS
AM RLC Poll Byte value in UL direction for UE category 3.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
25kB (0)
AM RLC Poll Byte Table 4
amRlcPBTab4
LNBTS
AM RLC Poll Byte Table for UE Category 4. It is used to obtain the UL pollByte and DL pollByte values for UE category 4.
DL Poll Byte
dlPollByte
LNBTS
AM RLC Poll Byte value in DL direction for UE category 4.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
75kB (2)
46
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 13
Name
Radio resource management and telecom features
Parameters for AM RLC Poll Byte structure (Cont.)
Short name
Object
Description
Range / Step
Default value
UE Category
ueCategory
LNBTS
Category of UE.
4...4, step 1
4
UL Poll Byte
ulPollByte
LNBTS
AM RLC Poll Byte value in UL direction for UE category 4.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
25kB (0)
AM RLC Poll Byte Table 5
amRlcPBTab5
LNBTS
AM RLC Poll Byte Table for UE Category 5. It is used to obtain the UL pollByte and DL pollByte values for UE category 5.
DL Poll Byte
dlPollByte
LNBTS
AM RLC Poll Byte value in DL direction for UE category 5.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
125kB (4)
UE Category
ueCategory
LNBTS
Category of UE.
5...5, step 1
5
UL Poll Byte
ulPollByte
LNBTS
AM RLC Poll Byte value in UL direction for UE category 5.
25kB (0), 50kB (1), 75kB (2), 100kB (3), 125kB (4), 250kB (5), 375kB (6), 500kB (7), 750kB (8), 1000kB (9), 1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)
50kB (1)
Table 14
Name
Parameters for QCI Translation Table structure
Short name
Object
Description
Range / Step
QCI Translation Table QCI 5
qciTab5
LNBTS
Table to translate the S1AP parameter QCI 5 into QCI characteristics
DSCP
dscp
LNBTS
This parameter configures the DSCP 0...63, step 1 (Differentiated Services Code Point) value associated with the QCI. The DSCP value will be set in each IP packet sent for the related bearer to S-GW or target eNB. List of IETF based DSCP values (numerical values in decimal): BE (=0), AF11 (=10),
DN0978033 Issue: 02N
© 2016 Nokia
Default value
34
47
Radio resource management and telecom features
Table 14
Name
LTE RL20, Feature Descriptions
Parameters for QCI Translation Table structure (Cont.)
Short name
Object
Description
Range / Step
Default value
AF12 (=12), AF13 (=14), AF21 (=18), AF22 (=20), AF23 (=22), AF31 (=26), AF32 (=28), AF33 (=30), AF41 (=34), AF42 (=36), AF43 (=38), EF (=46) Logical Channel Group Identifier
lcgid
LNBTS
Logical Channel Group Identifier for buffer 0 (0), 2 (2), 3 (3) status reporting This parameter is used for configuration of the buffer status reports of UE according [36.321]
2 (2)
PDCP Profile Index
pdcpProfIdx
LNBTS
This parameter specifies the ID of the corresponding PDCP profile.
1...3, step 1
1
Priority
prio
LNBTS
This parameter gives the priority of the EPS bearer according to TS23.203.
1...1, step 1
1
QCI
qci
LNBTS
QoS Class Identifier
5...5, step 1
5
QCI Support
qciSupp
LNBTS
This parameter indicates whether the given QCI is supported and enabled
DISABLE (0), ENABLE (1)
ENABLE (1)
Resource Type
resType
LNBTS
The Resource Type indicates whether nonGBR (1) bearer is a GBR or NON-GBR bearer. The Resource Type determines if dedicated network resources related to a service or bearer level Guaranteed Bit Rate (GBR) value are permanently allocated.
nonGBR (1)
RLC Mode
rlcMode
LNBTS
This parameter configures the RLC Mode of the data radio bearer
RLC_AM (0)
RLC_AM (0)
RLC Profile Index
rlcProfIdx
LNBTS
This parameter specifies the ID of the corresponding RLC profile
1...3, step 1
1
Scheduling Bucket Size Duration
schedulBSD
LNBTS
This parameter is used to configure the Bucket Size Duration (BSD) of the UL scheduler The BSD is sent to UE for the UL scheduling algorithm according [36.321]. The UE calculates the bucket size of a logical channel by PBR * BSD.
50ms (0), 100ms (1), 150ms (2), 300ms (3), 500ms (4), 1000ms (5)
100ms (1)
Scheduling Priority
schedulPrio
LNBTS
Logical Channel Priority for the UE scheduler This priority is sent to UE for the UL scheduling algorithm according for DRB [36.321]. Increasing priority values indicate lower priority.
2...16, step 1
9
Scheduling Type
schedulType
LNBTS
This parameter specifies how the EPS SIGNALLING (0), bearer with QCI 5 is scheduled. For the NON-GBR (1) scheduling type “SIGNALLING” the bearer
48
© 2016 Nokia
NON-GBR (1)
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 14
Name
Radio resource management and telecom features
Parameters for QCI Translation Table structure (Cont.)
Short name
Object
Description
Range / Step
Default value
is handled like SRBs. The MAC LCGID shall be set to 0 and schedulPrio is used for UL and DL scheduling. For the scheduling type “NON-GBR” the bearer is handled like other non-GBR bearers. The MAC LCGID shall not be to 0 and the schedulWeight is used for DL scheduling. Scheduling Weight
schedulWeigh LNBTS t
This parameter specifies the scheduling 1...100, step 1 weight for eNB schedulers The scheduling weight is used for MAC scheduling (UL and DL), and MAC logical channel priority handling and multiplexing in DL
QCI Translation Table QCI 6
qciTab6
LNBTS
Table to translate the S1AP parameter QCI 6 into QCI characteristics
DSCP
dscp
LNBTS
This parameter configures the DSCP 0...63, step 1 (Differentiated Services Code Point) value associated with the QCI. The DSCP value will be set in each IP packet sent for the related bearer to S-GW or target eNB. List of IETF based DSCP values (numerical values in decimal): BE (=0), AF11 (=10), AF12 (=12), AF13 (=14), AF21 (=18), AF22 (=20), AF23 (=22), AF31 (=26), AF32 (=28), AF33 (=30), AF41 (=34), AF42 (=36), AF43 (=38), EF (=46)
18
Logical Channel Group Identifier
lcgid
LNBTS
Logical Channel Group Identifier for buffer 2 (2), 3 (3) status reporting This parameter is used for configuration of the buffer status reports of UE according [36.321]
3 (3)
PDCP Profile Index
pdcpProfIdx
LNBTS
This parameter specifies the ID of the corresponding PDCP profile.
1...3, step 1
2
Priority
prio
LNBTS
This parameter gives the priority of the EPS bearer according TS23.203.
6...6, step 1
6
QCI
qci
LNBTS
QoS Class Identifier
6...6, step 1
6
QCI Support
qciSupp
LNBTS
This parameter indicates whether the given QCI is supported and enabled
DISABLE (0), ENABLE (1)
ENABLE (1)
Resource Type
resType
LNBTS
The Resource Type indicates whether nonGBR (1) bearer is a GBR or NON-GBR bearer. The Resource Type determines if dedicated
DN0978033 Issue: 02N
© 2016 Nokia
40
nonGBR (1)
49
Radio resource management and telecom features
Table 14
Name
LTE RL20, Feature Descriptions
Parameters for QCI Translation Table structure (Cont.)
Short name
Object
Description
Range / Step
Default value
network resources related to a service or bearer level Guaranteed Bit Rate (GBR) value are permanently allocated. RLC Mode
rlcMode
LNBTS
This parameter configures the RLC Mode of the data radio bearer
RLC_AM (0)
RLC_AM (0)
RLC Profile Index
rlcProfIdx
LNBTS
This parameter specifies the ID of the corresponding RLC profile
1...3, step 1
2
Scheduling Bucket Size Duration
schedulBSD
LNBTS
This parameter is used to configure the Bucket Size Duration (BSD) of the UL scheduler The BSD is sent to UE for the UL scheduling algorithm according [36.321]. The UE calculates the bucket size of a logical channel by PBR * BSD.
50ms (0), 100ms (1), 150ms (2), 300ms (3), 500ms (4), 1000ms (5)
300ms (3)
Scheduling Priority
schedulPrio
LNBTS
Logical Channel Priority for the UE scheduler This priority is sent to UE for the UL scheduling algorithm according for DRB [36.321]. Increasing priority values indicate lower priority.
9...16, step 1
9
Scheduling Weight
schedulWeigh LNBTS t
This parameter specifies the scheduling 1...100, step 1 weight for eNB schedulers The scheduling weight is used for MAC scheduling (UL and DL), and MAC logical channel priority handling and multiplexing in DL
QCI Translation Table QCI 7
qciTab7
LNBTS
Table to translate the S1AP parameter QCI 7 into QCI characteristics
DSCP
dscp
LNBTS
This parameter configures the DSCP 0...63, step 1 (Differentiated Services Code Point) value associated with the QCI. The DSCP value will be set in each IP packet sent for the related bearer to S-GW or target eNB. List of IETF based DSCP values (numerical values in decimal): BE (=0), AF11 (=10), AF12 (=12), AF13 (=14), AF21 (=18), AF22 (=20), AF23 (=22), AF31 (=26), AF32 (=28), AF33 (=30), AF41 (=34), AF42 (=36), AF43 (=38), EF (=46)
20
Logical Channel Group Identifier
lcgid
LNBTS
Logical Channel Group Identifier for buffer 2 (2), 3 (3) status reporting This parameter is used for configuration of the buffer status reports of UE according [36.321]
2 (2)
50
© 2016 Nokia
20
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 14
Name
Radio resource management and telecom features
Parameters for QCI Translation Table structure (Cont.)
Short name
Object
Description
Range / Step
Default value
PDCP Profile Index
pdcpProfIdx
LNBTS
This parameter specifies the ID of the corresponding PDCP profile.
1...3, step 1
1
Priority
prio
LNBTS
This parameter gives the priority of the EPS bearer according TS23.203.
7...7, step 1
7
QCI
qci
LNBTS
QoS Class Identifier
7...7, step 1
7
QCI Support
qciSupp
LNBTS
This parameter indicates whether the given QCI is supported and enabled
DISABLE (0), ENABLE (1)
ENABLE (1)
Resource Type
resType
LNBTS
The Resource Type indicates whether nonGBR (1) bearer is a GBR or NON-GBR bearer. The Resource Type determines if dedicated network resources related to a service or bearer level Guaranteed Bit Rate (GBR) value are permanently allocated.
nonGBR (1)
RLC Mode
rlcMode
LNBTS
This parameter configures the RLC Mode of the data radio bearer
RLC_AM (0)
RLC_AM (0)
RLC Profile Index
rlcProfIdx
LNBTS
This parameter specifies the ID of the corresponding RLC profile
1...3, step 1
2
Scheduling Bucket Size Duration
schedulBSD
LNBTS
This parameter is used to configure the Bucket Size Duration (BSD) of the UL scheduler The BSD is sent to UE for the UL scheduling algorithm according [36.321]. The UE calculates the bucket size of a logical channel by PBR * BSD.
50ms (0), 100ms (1), 150ms (2), 300ms (3), 500ms (4), 1000ms (5)
100ms (1)
Scheduling Priority
schedulPrio
LNBTS
Logical Channel Priority for the UE scheduler This priority is sent to UE for the UL scheduling algorithm according for DRB [36.321]. Increasing priority values indicate lower priority.
9...16, step 1
10
Scheduling Weight
schedulWeigh LNBTS t
This parameter specifies the scheduling 1...100, step 1 weight for eNB schedulers The scheduling weight is used for MAC scheduling (UL and DL), and MAC logical channel priority handling and multiplexing in DL
QCI Translation Table QCI 8
qciTab8
LNBTS
Table to translate the S1AP parameter QCI 8 into QCI characteristics
DSCP
dscp
LNBTS
This parameter configures the DSCP 0...63, step 1 (Differentiated Services Code Point) value associated with the QCI. The DSCP value
DN0978033 Issue: 02N
© 2016 Nokia
10
10
51
Radio resource management and telecom features
Table 14
Name
LTE RL20, Feature Descriptions
Parameters for QCI Translation Table structure (Cont.)
Short name
Object
Description
Range / Step
Default value
will be set in each IP packet sent for the related bearer to S-GW or target eNB. List of IETF based DSCP values (numerical values in decimal): BE (=0), AF11 (=10), AF12 (=12), AF13 (=14), AF21 (=18), AF22 (=20), AF23 (=22), AF31 (=26), AF32 (=28), AF33 (=30), AF41 (=34), AF42 (=36), AF43 (=38), EF (=46) Logical Channel Group Identifier
lcgid
LNBTS
Logical Channel Group Identifier for buffer 2 (2), 3 (3) status reporting. This parameter is used for configuration of the buffer status reports of UE according [36.321]
3 (3)
PDCP Profile Index
pdcpProfIdx
LNBTS
This parameter specifies the ID of the corresponding PDCP profile.
1...3, step 1
2
Priority
prio
LNBTS
This parameter gives the priority of the EPS bearer according TS23.203.
8...8, step 1
8
QCI
qci
LNBTS
QoS Class Identifier
8...8, step 1
8
QCI Support
qciSupp
LNBTS
This parameter indicates whether the given QCI is supported and enabled
DISABLE (0), ENABLE (1)
ENABLE (1)
Resource Type
resType
LNBTS
The Resource Type indicates whether nonGBR (1) bearer is a GBR or NON-GBR bearer. The Resource Type determines if dedicated network resources related to a service or bearer level Guaranteed Bit Rate (GBR) value are permanently allocated.
nonGBR (1)
RLC Mode
rlcMode
LNBTS
This parameter configures the RLC Mode of the data radio bearer
RLC_AM (0)
RLC_AM (0)
RLC Profile Index
rlcProfIdx
LNBTS
This parameter specifies the ID of the corresponding RLC profile
1...3, step 1
2
Scheduling Bucket Size Duration
schedulBSD
LNBTS
This parameter is used to configure the Bucket Size Duration (BSD) of the UL scheduler The BSD is sent to UE for the UL scheduling algorithm according [36.321]. The UE calculates the bucket size of a logical channel by PBR * BSD.
50ms (0), 100ms (1), 150ms (2), 300ms (3), 500ms (4), 1000ms (5)
300ms (3)
Scheduling Priority
schedulPrio
LNBTS
Logical Channel Priority for the UE scheduler This priority is sent to UE for the UL scheduling algorithm according for DRB [36.321]. Increasing priority values indicate lower priority.
9...16, step 1
11
52
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 14
Name
Radio resource management and telecom features
Parameters for QCI Translation Table structure (Cont.)
Short name
Object
Description
Range / Step
Default value
Scheduling Weight
schedulWeigh LNBTS t
This parameter specifies the scheduling 1...100, step 1 weight for eNB schedulers The scheduling weight is used for MAC scheduling (UL and DL), and MAC logical channel priority handling and multiplexing in DL
QCI Translation Table QCI 9
qciTab9
LNBTS
Table to translate the S1AP parameter QCI 9 into QCI characteristics
DSCP
dscp
LNBTS
This parameter configures the DSCP 0...63, step 1 (Differentiated Services Code Point) value associated with the QCI. The DSCP value will be set in each IP packet sent for the related bearer to S-GW or target eNB. List of IETF based DSCP values (numerical values in decimal): BE (=0), AF11 (=10), AF12 (=12), AF13 (=14), AF21 (=18), AF22 (=20), AF23 (=22), AF31 (=26), AF32 (=28), AF33 (=30), AF41 (=34), AF42 (=36), AF43 (=38), EF (=46)
0
Logical Channel Group Identifier
lcgid
LNBTS
Logical Channel Group Identifier for buffer 2 (2), 3 (3) status reporting This parameter is used for configuration of the buffer status reports of UE according [36.321]
3 (3)
PDCP Profile Index
pdcpProfIdx
LNBTS
This parameter specifies the ID of the corresponding PDCP profile.
1...3, step 1
2
Priority
prio
LNBTS
This parameter gives the priority of the EPS bearer according TS23.203.
9...9, step 1
9
QCI
qci
LNBTS
QoS Class Identifier
9...9, step 1
9
QCI Support
qciSupp
LNBTS
This parameter indicates whether the given QCI is supported and enabled
DISABLE (0), ENABLE (1)
ENABLE (1)
Resource Type
resType
LNBTS
The Resource Type indicates whether nonGBR (1) bearer is a GBR or NON-GBR bearer. The Resource Type determines if dedicated network resources related to a service or bearer level Guaranteed Bit Rate (GBR) value are permanently allocated.
nonGBR (1)
RLC Mode
rlcMode
LNBTS
This parameter configures the RLC Mode of the data radio bearer
RLC_AM (0)
RLC_AM (0)
RLC Profile Index
rlcProfIdx
LNBTS
This parameter specifies the ID of the corresponding RLC profile
1...3, step 1
2
DN0978033 Issue: 02N
© 2016 Nokia
5
53
Radio resource management and telecom features
Table 14
Name
LTE RL20, Feature Descriptions
Parameters for QCI Translation Table structure (Cont.)
Short name
Object
Description
Range / Step
Default value
Scheduling Bucket Size Duration
schedulBSD
LNBTS
This parameter is used to configure the Bucket Size Duration (BSD) of the UL scheduler The BSD is sent to UE for the UL scheduling algorithm according [36.321]. The UE calculates the bucket size of a logical channel by PBR * BSD.
50ms (0), 100ms (1), 150ms (2), 300ms (3), 500ms (4), 1000ms (5)
300ms (3)
Scheduling Priority
schedulPrio
LNBTS
Logical Channel Priority for the UE scheduler This priority is sent to UE for the UL scheduling algorithm according for DRB [36.321]. Increasing priority values indicate lower priority.
9...16, step 1
12
Scheduling Weight
schedulWeigh LNBTS t
Table 15
Name
This parameter specifies the scheduling 1...100, step 1 weight for eNB schedulers The scheduling weight is used for MAC scheduling (UL and DL), and MAC logical channel priority handling and multiplexing in DL
1
Parameters for profiles of RLC
Short name
Object
Description
Range / Step
Default value
Profile 1 of RLC Parameters
rlcProf1
LNBTS
Profile 1 of RLC parameters for DRBs in RLC AM mode
Poll PDU
pollPdu
LNBTS
This parameter specifies the parameter pollPDU of [36.331] The parameter Poll PDU defines the number of RLC PDUs that are sent on a logical channel before the RLC polling bit is set.
4 (0), 8 (1), 16 (2), 32 (3), 64 (4), 128 infinity (7) (5), 256 (6), infinity (7)
RLC Profile Id rlcProfileId
LNBTS
Identity of the RLC profile
1...1, step 1
Timer Poll Retransmit
LNBTS
This parameter specifies the parameter t-pollRetransmit of [36.331] This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll. The used minimum value of the timer shall be larger than the calculated round-trip time with considerations of HARQ retransmissions and out-of-
5ms (0), 10ms (1), 15ms (2), 20ms 120ms (23) (3), 25ms (4), 30ms (5), 35ms (6), 40ms (7), 45ms (8), 50ms (9), 55ms (10), 60ms (11), 65ms (12), 70ms (13), 75ms (14), 80ms (15), 85ms (16), 90ms (17), 95ms (18), 100ms (19), 105ms (20), 110ms (21), 115ms (22), 120ms (23), 125ms (24), 130ms (25), 135ms (26), 140ms (27), 145ms (28), 150ms (29), 155ms (30), 160ms (31), 165ms (32), 170ms (33), 175ms
54
tPollRetr
© 2016 Nokia
1
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 15
Name
Radio resource management and telecom features
Parameters for profiles of RLC (Cont.)
Short name
Object
Description
Range / Step
sequence arrival. The value of the timer shall be larger than twice of the timerReorder.
(34), 180ms (35), 185ms (36), 190ms (37), 195ms (38), 200ms (39), 205ms (40), 210ms (41), 215ms (42), 220ms (43), 225ms (44), 230ms (45), 235ms (46), 240ms (47), 245ms (48), 250ms (49), 300ms (50), 350ms (51), 400ms (52), 450ms (53), 500ms (54)
Default value
Timer Status Prohibit
tProhib
LNBTS
This parameter specifies the parameter t-StatusProhibit of [36.331] This timer is used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU
0ms (0), 5ms (1), 10ms (2), 15ms 50ms (10) (3), 20ms (4), 25ms (5), 30ms (6), 35ms (7), 40ms (8), 45ms (9), 50ms (10), 55ms (11), 60ms (12), 65ms (13), 70ms (14), 75ms (15), 80ms (16), 85ms (17), 90ms (18), 95ms (19), 100ms (20), 105ms (21), 110ms (22), 115ms (23), 120ms (24), 125ms (25), 130ms (26), 135ms (27), 140ms (28), 145ms (29), 150ms (30), 155ms (31), 160ms (32), 165ms (33), 170ms (34), 175ms (35), 180ms (36), 185ms (37), 190ms (38), 195ms (39), 200ms (40), 205ms (41), 210ms (42), 215ms (43), 220ms (44), 225ms (45), 230ms (46), 235ms (47), 240ms (48), 245ms (49), 250ms (50), 300ms (51), 350ms (52), 400ms (53), 450ms (54), 500ms (55)
Timer Reordering
tReord
LNBTS
This parameter specifies the parameter t-Reordering of [36.331] This timer is used by the receiving side of an AM RLC entity for reordering, PDU loss detection and delay of STATUS PDU transmission. This timer depends on HARQ RTT and number of HARQ retransmissions.
0ms (0), 5ms (1), 10ms (2), 15ms 50ms (10) (3), 20ms (4), 25ms (5), 30ms (6), 35ms (7), 40ms (8), 45ms (9), 50ms (10), 55ms (11), 60ms (12), 65ms (13), 70ms (14), 75ms (15), 80ms (16), 85ms (17), 90ms (18), 95ms (19), 100ms (20), 110ms (21), 120ms (22), 130ms (23), 140ms (24), 150ms (25), 160ms (26), 170ms (27), 180ms (28), 190ms (29), 200ms (30)
Profile 2 of RLC Parameters
rlcProf2
LNBTS
Profile 2 of RLC parameters for DRBs in RLC AM mode
Poll PDU
pollPdu
LNBTS
This parameter specifies the parameter pollPDU of [36.331] The parameter Poll PDU defines the number of RLC PDUs that are sent on a logical channel before the RLC polling bit is set.
DN0978033 Issue: 02N
© 2016 Nokia
4 (0), 8 (1), 16 (2), 32 (3), 64 (4), 128 64 (4) (5), 256 (6), infinity (7)
55
Radio resource management and telecom features
Table 15
Name
LTE RL20, Feature Descriptions
Parameters for profiles of RLC (Cont.)
Short name
Object
Description
Range / Step
Default value
RLC Profile Id rlcProfileId
LNBTS
Identity of the RLC profile
2...2, step 1
Timer Poll Retransmit
tPollRetr
LNBTS
This parameter specifies the parameter t-pollRetransmit of [36.331] This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll. The used minimum value of the timer shall be larger than the calculated round-trip time with considerations of HARQ retransmissions and out-ofsequence arrival. The value of the timer shall be larger than twice of the timerReorder.
5ms (0), 10ms (1), 15ms (2), 20ms 120ms (23) (3), 25ms (4), 30ms (5), 35ms (6), 40ms (7), 45ms (8), 50ms (9), 55ms (10), 60ms (11), 65ms (12), 70ms (13), 75ms (14), 80ms (15), 85ms (16), 90ms (17), 95ms (18), 100ms (19), 105ms (20), 110ms (21), 115ms (22), 120ms (23), 125ms (24), 130ms (25), 135ms (26), 140ms (27), 145ms (28), 150ms (29), 155ms (30), 160ms (31), 165ms (32), 170ms (33), 175ms (34), 180ms (35), 185ms (36), 190ms (37), 195ms (38), 200ms (39), 205ms (40), 210ms (41), 215ms (42), 220ms (43), 225ms (44), 230ms (45), 235ms (46), 240ms (47), 245ms (48), 250ms (49), 300ms (50), 350ms (51), 400ms (52), 450ms (53), 500ms (54)
Timer Status Prohibit
tProhib
LNBTS
This parameter specifies the parameter t-StatusProhibit of [36.331] This timer is used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU
0ms (0), 5ms (1), 10ms (2), 15ms 50ms (10) (3), 20ms (4), 25ms (5), 30ms (6), 35ms (7), 40ms (8), 45ms (9), 50ms (10), 55ms (11), 60ms (12), 65ms (13), 70ms (14), 75ms (15), 80ms (16), 85ms (17), 90ms (18), 95ms (19), 100ms (20), 105ms (21), 110ms (22), 115ms (23), 120ms (24), 125ms (25), 130ms (26), 135ms (27), 140ms (28), 145ms (29), 150ms (30), 155ms (31), 160ms (32), 165ms (33), 170ms (34), 175ms (35), 180ms (36), 185ms (37), 190ms (38), 195ms (39), 200ms (40), 205ms (41), 210ms (42), 215ms (43), 220ms (44), 225ms (45), 230ms (46), 235ms (47), 240ms (48), 245ms (49), 250ms (50), 300ms (51), 350ms (52), 400ms (53), 450ms (54), 500ms (55)
Timer Reordering
tReord
LNBTS
This parameter specifies the parameter t-Reordering of [36.331] This timer is used by the receiving side of an AM RLC entity for reordering, PDU loss detection and delay of STATUS PDU transmission.
0ms (0), 5ms (1), 10ms (2), 15ms 50ms (10) (3), 20ms (4), 25ms (5), 30ms (6), 35ms (7), 40ms (8), 45ms (9), 50ms (10), 55ms (11), 60ms (12), 65ms (13), 70ms (14), 75ms (15), 80ms (16), 85ms (17), 90ms (18), 95ms (19), 100ms (20), 110ms (21), 120ms (22), 130ms (23), 140ms (24), 150ms (25), 160ms (26), 170ms (27), 180ms (28), 190ms (29), 200ms (30)
56
© 2016 Nokia
2
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 15
Name
Radio resource management and telecom features
Parameters for profiles of RLC (Cont.)
Short name
Object
Description
Range / Step
Default value
This timer depends on HARQ RTT and number of HARQ retransmissions. Profile 3 of RLC Parameters
rlcProf3
LNBTS
Profile 3 of RLC parameters for DRBs in RLC AM mode
Poll PDU
pollPdu
LNBTS
This parameter specifies the parameter pollPDU of [36.331] The parameter Poll PDU defines the number of RLC PDUs that are sent on a logical channel before the RLC polling bit is set.
4 (0), 8 (1), 16 (2), 32 (3), 64 (4), 128 64 (4) (5), 256 (6), infinity (7)
RLC Profile Id rlcProfileId
LNBTS
Identity of the RLC profile
3...3, step 1
Timer Poll Retransmit
tPollRetr
LNBTS
This parameter specifies the parameter t-pollRetransmit of [36.331] This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll. The used minimum value of the timer shall be larger than the calculated round-trip time with considerations of HARQ retransmissions and out-ofsequence arrival. The value of the timer shall be larger than twice of the timerReorder.
5ms (0), 10ms (1), 15ms (2), 20ms 120ms (23) (3), 25ms (4), 30ms (5), 35ms (6), 40ms (7), 45ms (8), 50ms (9), 55ms (10), 60ms (11), 65ms (12), 70ms (13), 75ms (14), 80ms (15), 85ms (16), 90ms (17), 95ms (18), 100ms (19), 105ms (20), 110ms (21), 115ms (22), 120ms (23), 125ms (24), 130ms (25), 135ms (26), 140ms (27), 145ms (28), 150ms (29), 155ms (30), 160ms (31), 165ms (32), 170ms (33), 175ms (34), 180ms (35), 185ms (36), 190ms (37), 195ms (38), 200ms (39), 205ms (40), 210ms (41), 215ms (42), 220ms (43), 225ms (44), 230ms (45), 235ms (46), 240ms (47), 245ms (48), 250ms (49), 300ms (50), 350ms (51), 400ms (52), 450ms (53), 500ms (54)
Timer Status Prohibit
tProhib
LNBTS
This parameter specifies the parameter t-StatusProhibit of [36.331] This timer is used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU
0ms (0), 5ms (1), 10ms (2), 15ms 50ms (10) (3), 20ms (4), 25ms (5), 30ms (6), 35ms (7), 40ms (8), 45ms (9), 50ms (10), 55ms (11), 60ms (12), 65ms (13), 70ms (14), 75ms (15), 80ms (16), 85ms (17), 90ms (18), 95ms (19), 100ms (20), 105ms (21), 110ms (22), 115ms (23), 120ms (24), 125ms (25), 130ms (26), 135ms (27), 140ms (28), 145ms (29), 150ms (30), 155ms (31), 160ms (32), 165ms (33), 170ms (34), 175ms (35), 180ms (36), 185ms (37), 190ms (38), 195ms (39), 200ms (40), 205ms (41), 210ms (42), 215ms
DN0978033 Issue: 02N
© 2016 Nokia
3
57
Radio resource management and telecom features
Table 15
Name
LTE RL20, Feature Descriptions
Parameters for profiles of RLC (Cont.)
Short name
Object
Description
Range / Step
Default value
(43), 220ms (44), 225ms (45), 230ms (46), 235ms (47), 240ms (48), 245ms (49), 250ms (50), 300ms (51), 350ms (52), 400ms (53), 450ms (54), 500ms (55) Timer Reordering
Table 16
Name
tReord
LNBTS
This parameter specifies the parameter t-Reordering of [36.331] This timer is used by the receiving side of an AM RLC entity for reordering, PDU loss detection and delay of STATUS PDU transmission. This timer depends on HARQ RTT and number of HARQ retransmissions.
0ms (0), 5ms (1), 10ms (2), 15ms 50ms (10) (3), 20ms (4), 25ms (5), 30ms (6), 35ms (7), 40ms (8), 45ms (9), 50ms (10), 55ms (11), 60ms (12), 65ms (13), 70ms (14), 75ms (15), 80ms (16), 85ms (17), 90ms (18), 95ms (19), 100ms (20), 110ms (21), 120ms (22), 130ms (23), 140ms (24), 150ms (25), 160ms (26), 170ms (27), 180ms (28), 190ms (29), 200ms (30)
Parameters for profiles of PDCP
Short name
Object
Description
Range / Step
Default value
Profile 1 of PDCP parameters
pdcpProf1
LNBTS
Profile 1 of PDCP parameters Structure {pdcpProfileId,tDiscard,statusR eportReq}.
PDCP profile ID
pdcpProfileId
LNBTS
Identity of the PDCP profile; 0 specifies an invalid dummy profile.
1...1, step 1
1
Status report required
statusRepReq
LNBTS
This parameter determines whether a PDCP status report is sent from PDCP receiver to PDCP transmitter. The PDCP status report may be sent from eNB to UE (eNB PDCP status report) or from UE to eNB (UE PDCP status report). Possible settings: 00: no status report 01: eNB status report 10: UE status report 11: eNB and UE status report
Bit 0: eNB Status Report, Bit 1: UE Status Report,
0
58
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 16
Name
Radio resource management and telecom features
Parameters for profiles of PDCP (Cont.)
Short name
Object
Description
Range / Step
Default value
Timer discard
tDiscard
LNBTS
This parameter indicates the delay before a PDCP PDU along with the corresponding PDCP SDU is discarded from the buffer. This timer should be set in a way that the packet delay defined by the QCI characteristics is kept. The timer can be disabled by setting the parameter to disabled.
Profile 2 of PDCP parameters
pdcpProf2
LNBTS
Profile 2 of PDCP parameters for RLC AM data radio bearers
PDCP profile ID
pdcpProfileId
LNBTS
Identity of the PDCP profile
Status report required
statusRepReq
LNBTS
This parameter determines Bit 0: eNB Status Report, Bit whether a PDCP Status Report 1: UE Status Report, is sent from PDCP receiver to PDCP transmitter. The PDCP Status Report may be sent from eNB to UE (eNB PDCP Status Report) or from UE to eNB (UE PDCP Status Report). Possible settings: 00 - no Status Report 01 - eNB Status Report 10 - UE Status Report 11 - eNB and UE Status Report
Timer discard
tDiscard
LNBTS
This parameter specifies the 300ms (0), 500ms (1), 750ms 750ms (2) parameter discardTimer of (2), 1500ms (3), infinity (4) [36.331] This parameter indicates the delay before a PDCP PDU along with the corresponding PDCP SDU is discarded from the buffer. This timer shall be set in a way that the packet delay defined by the QCI characteristics is kept. The timer can be disabled by setting the parameter to infinity.
Profile 3 of PDCP parameters
pdcpProf3
LNBTS
Profile 3 of PDCP parameters for RLC AM data radio bearers
PDCP profile ID
pdcpProfileId
LNBTS
Identity of the PDCP profile
DN0978033 Issue: 02N
© 2016 Nokia
50ms (0), 100ms (1), 150ms (2), 300ms (3), 500ms (4), 750ms (5), 1500ms (6), infinity (7)
300ms (3)
2...2, step 1
2
3...3, step 1
0
3
59
Radio resource management and telecom features
Table 16
LTE RL20, Feature Descriptions
Parameters for profiles of PDCP (Cont.)
Name
Short name
Object
Description
Range / Step
Default value
Status report required
statusRepReq
LNBTS
This parameter determines Bit 0: eNB Status Report, Bit whether a PDCP Status Report 1: UE Status Report, is sent from PDCP receiver to PDCP transmitter. The PDCP Status Report may be sent from eNB to UE (eNB PDCP Status Report) or from UE to eNB (UE PDCP Status Report). Possible settings: 00 - no Status Report 01 - eNB Status Report 10 - UE Status Report 11 - eNB and UE Status Report
Timer discard
tDiscard
LNBTS
This parameter specifies the 300ms (0), 500ms (1), 750ms 750ms (2) parameter discardTimer of (2), 1500ms (3), infinity (4) [36.331] This parameter indicates the delay before a PDCP PDU along with the corresponding PDCP SDU is discarded from the buffer. This timer shall be set in a way that the packet delay defined by the QCI characteristics is kept. The timer can be disabled by setting the parameter to infinity.
2.4.7.2
0
Alarms There are no alarms for this feature defined in this release
2.4.7.3
Measurements and counters Table 17: Counters for the LTE9: Service differentiation shows the counters for the feature.
Table 17
PI ID
Counters for the LTE9: Service differentiation
Counter long name (short name)
Description
M8001C270
Mean PDCP SDU delay on DL DTCH for non-GBR DRB
Mean retention delay for a PDCP SDU (DL) inside eNB non-GBR data radio bearers
M8001C420
UEs with buffered UL data for non-GBR DRB
The average number of UEs with buffered data in UL per logical channel group id mapped to non-GBR bearers (QCI5..9)
60
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 17
PI ID
Radio resource management and telecom features
Counters for the LTE9: Service differentiation (Cont.)
Counter long name (short name)
Description
M8006C18
Initial EPS Bearer setup attempts for non-GBR
The number of initial EPS bearer setup attempts per non-GBR. Each bearer of the E-RAB to Be Setup List IE is counted.
M8006C36
Initial EPS Bearer setup completions for non-GBR
The number of initial EPS bearer setup completions per non-GBR. Each bearer of the E-RAB Setup List IE is counted.
Additional counters can be derived from the existing counters: • • • •
Additional EPS Bearer setup attempts for non-GBR Additional EPS Bearer setup completions for non-GBR EPC initiated EPS Bearer Release requests for non-GBR per cause eNB initiated EPS Bearer Release requests for non-GBR per cause
2.4.8 Activating the feature This feature requires activation.
2.5 LTE10: EPS Bearers for Conversational Voice 2.5.1 Introduction to the feature The LTE10: EPS bearers for conversational voice feature allows to introduce high-quality managed IMS-based conversational voice services in LTE. A service is a bi-directional traffic stream, or equivalently, a set of several associated traffic streams between a UE and a remote endpoint. This creates the need to support multiple data radio bearers (as provided by the LTE7: Support of multiple EPS bearer feature), and to support appropriate data radio bearer combinations per UE. For IMS-based conversational voice, this bearer combination consists of one UM DRB which carries the voice data, and one AM DRB which carries the associated IMS signaling. The following radio bearer combinations per UE are supported by the evolved Node B (eNB) in LTE10: • • • •
SRB1 + SRB2 + 1 x AM DRB + 1 x UM DRB SRB1 + SRB2 + 2 x AM DRB + 1 x UM DRB SRB1 + SRB2 + 3 x AM DRB + 1 x UM DRB SRB1 + SRB2 + 4 x AM DRB + 1 x UM DRB
Thus it is possible to use simultaneously two signaling radio bearers (SRBs), up to four AM DRBs and additionally one UM DRB. Conversational voice service support is restricted to dynamic scheduling. Dynamic scheduling for UL/DL in the user plane considers QoS requirements and performs proper prioritization to meet them, which might result in some downgrading of the service for non-GBR bearers.
DN0978033 Issue: 02N
© 2016 Nokia
61
Radio resource management and telecom features
LTE RL20, Feature Descriptions
Conversational voice is assigned the QoS Class Indicator (QCI) =1. The requirements associated with this QCI are met by assigning a GBR bearer to the voice data stream. Therefore, the eNodeB evaluates corresponding UE capabilities and the requested bit rate value, as indicated via S1AP procedures, and admits GBR bearers if neither the supported maximum GBR for QCI=1, nor the specific admission limits for GBR bearers are exceeded. Any other traffic that is also mapped to QCI=1 will experience the same QoS, while the traffic handling is still optimized for conversational voice traffic. To fully account for the prioritization requirements of conversational traffic, the associated IMS signaling packet stream has to be assigned a data radio bearer with an appropriate QCI. QCI=5 is expected to provide sufficient properties. The eNodeB assumes that a DRB of sufficient properties is already established when it receives the request for establishing the conversational voice service. The eNodeB does not perform any checks in this respect. The upper throughput limit of the GBR service in downlink direction is enforced by the PDN gateway. In uplink the eNodeB assumes that the GBR throughput limit is enforced in the UE.
2.5.2 Benefits This feature enables the operator to offer conversational voice over LTE.
2.5.3 Requirements 2.5.3.1
Software requirements The following software is needed: Table 18
Software requirements for different network elements
Network element
2.5.3.2
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
NS20
SAE GW
NG20
UE
3GPP release 8
NetAct
–
Hardware requirements This feature requires no new or additional hardware.
62
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
2.5.4 Functional description The LTE10: EPS bearers for conversational voice feature introduces a range of new functions to user-plane radio resource management: • • • • • •
Delay-based scheduling in DL and in UL for bearers with QCI=1 Outer loop delay target control in DL Head of Line (HOL) estimation in UL Consideration of GBR bearer in MAC multiplexing in DL New scheduler type: exhaustive UL Frequency Domain scheduler Packet aggregation in UL/DL
Admission Control in the eNodeB ensures that a configurable number of active GBRDRBs in a radio cell is not exceeded. An incoming handover is rejected if this number would be exceeded by a new UE entering a radio cell.
2.5.4.1
Delay based scheduling in DL and in UL for bearers with QCI=1 The PDCP layer in the eNodeB provides all IP packets received via S1 with a timestamp that is taken from the local (system) time of the eNodeB. All IP packets received from a source node are provided with a timestamp constructed from the local time of the target eNodeB, reduced by a configurable correction value. These timestamps are forwarded to the MAC layer and taken into account by the scheduler, in order to meet QoS requirements with respect to maximum packet delay. In uplink, the scheduler: • •
•
assumes that conversational voice traffic is identified by QCI=1 performs prioritization of conversational voice data, based on the (configurable) packet delay budget as provided by control plane, and on the experienced waiting time in UE, provides specific treatment of the separate data radio bearer that carries IMS signaling and is associated with the QCI=1 bearer. This specific treatment requires that QCI=5 is set for the bearer.
In downlink, the scheduler: • • •
•
•
DN0978033 Issue: 02N
provides specific treatment of the separate data radio bearer that carries IMS signaling. This specific treatment requires that QCI=5 is set for the bearer. assumes that the maximum admitted guaranteed data rate for conversational voice service is limited to 250 kbit/s per UE. assumes that the guaranteed data rate of admitted bearers with QCI=1 is already enforced in the EPC, and that timely transmission of corresponding data packets is sufficient. handles traffic with QCI=5 either with priority corresponding to signaling data or as regular non-GBR data radio bearers (with corresponding relative weight, if applicable) depending on indication from the control plane. considers GBR in addition to UE AMBR when determining the maximum resource allocation for a UE.
© 2016 Nokia
63
Radio resource management and telecom features
2.5.4.2
LTE RL20, Feature Descriptions
Outer loop delay target control in DL Delay-based prioritization does not explicitly control the probability of packets being received correctly within a given delay target value. Therefore, a mechanism called Outer Loop Delay Target Control (OLDTC) or Outer Loop Delay Budget Control (OLDBC) is provided. This mechanism can be activated using the dlsOldtcEnable parameter. OLDTC modifies the delay-based prioritization values in dependence of the delay target excess rate, on a per-UE basis. So, if packets belonging to a bearer with QCI=1 established towards a UE are transferred correctly within the delay target, the prioritization values are decreased by a small amount. Conversely, if the packets exceed the delay target, the prioritization value is increased.
2.5.4.3
HOL packet delay estimation in UL The head of line (HOL) packet represents the oldest packet that has arrived in a transmission buffer of the UE. The delay experienced by this HOL packet is estimated by the eNodeB, in order to maintain the required QoS and also to find an estimation of the data volume in the UE buffer that might be transmitted together using packet aggregation. In the UE, in UL direction, the arrival of a packet in a higher priority logical channel triggers a scheduling request (SR) if no UL grant from eNodeB is available, whereas if an UL grant is available, a “Regular BSR” (Buffer Status Report) is sent. The eNodeB evaluates the BSRs that are related to the logical channel groups (LGC) to which the bearer with QCI is mapped. The estimated HOL packet delay is based on a set of data which includes: • •
•
The UL TTI in which a BSR (related to the LGC of interest) was transmitted. This instance of time is calculated from the value found in the BSR, and the GBR. The UL TTI in which an uplink transmission is made which contains data from the UE's VoIP transmission buffer. This value is estimated from the last UL grant which contains a GBR portion. This estimate is corrected as soon as the expected packet is correctly received by the eNodeB. The UL TTI in which an SR is transmitted by the UE. Receiving such an SR immediately after a BSR with filling value 0 indicates that the last received packet represented the head of line. Other relations between SR transmission, BSR, and UL packet transmission yield further indication about the situation of the current HOL packet in the UE's transmission buffer.
The derived value for HOL packet delay in the UE's transmission buffer is taken into account by the UL scheduler in the eNodeB.
2.5.4.4
Consideration of GBR bearer in MAC multiplexing in DL The MAC layer in the eNodeB is updated to support service differentiation for bearers with QCI=1 in DL, and to provide multiplexing of data from multiple logical channels into single MAC DL PDUs. Depending on the configuration, data from the bearer with QCI=5 is either interpreted as being control data or as being regular non-GBR data. This combined data takes second priority, after control elements, data from signaling bearers and other control data, and before data originating from non-GBR bearers, assuming that GBR bearers always have higher priority. Data originating from non-GBR bearers gets the residual capacity that is left unused by GBR bearers.
64
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.5.4.5
Radio resource management and telecom features
New scheduler type: exhaustive FD scheduler In uplink, an alternative to the Round Robin scheduler is introduced, which is the exhaustive UL Frequency Domain scheduler. The round-robin scheduler uses a two-step approach to create a list of UEs, which are candidates for being assigned UL resources in a TTI. From this list, the scheduler assigns PRBs to the UEs, starting with the entry of highest priority and walking through the list in round-robin fashion for as long as resources are available, as determined by the fast adaptive transmission bandwidth (fast ATB) function. The Round Robin scheduler allocates resources in a fixed size of one PRB per allocation, which means its packet allocation size is fixed to 1. Since the Round Robin scheduler may assign resources to a large number of UEs, it might run into a shortage of PDCCH space that is required to carry the associated signaling data. The exhaustive Frequency Domain Scheduler selects a small number of UEs (fewer than are specified by the Max_#_UE_UL parameter) and assigns them all available PRBs for the TTI under consideration. This method creates less signaling load and therefore can avoid congestion on PDCCH. To take the full benefit of this, the exhaustive FD Scheduler allows the aggregation of transport blocks carrying VoIP samples. The type of the uplink scheduler can be selected by the ulsFdPrbAssignAlg parameter.
2.5.4.6
Packet aggregation in UL/DL Packet aggregation means that VoIP packets are collected in a buffer and then transmitted together. Packet aggregation therefore introduces some additional delay in the transmission of VoIP packets. Packet aggregation in uplink requires that the exhaustive Frequency Domain Scheduler is chosen. UEs with established bearer with QCI=1 are prioritized in scheduling such that data belonging to the QCI=1 bearer do not experience more delay than is specified in a configurable delay target. The quality experienced by non-GBR traffic may be reduced due to this prioritization. Prioritization is applied to all kinds of traffic mapped to QCI=1. No additional rate control of the GBR traffic is applied in eNodeB.
2.5.4.7
Bearer establishment The voice service on the GBR EPS bearer with QCI=1 (QoS class indicator) is mapped to a DRB that works on RLC in unacknowledged mode. Figure 6: EPS bearer establishment by S1AP: E-RAB setup request shows a message flow for creating this bearer. The evolved Node B (eNodeB) takes the GBR (guaranteed bit rate) into account, which is signaled on the S1 interface, for example in an S1AP: ERAB SETUP REQUEST message.
DN0978033 Issue: 02N
© 2016 Nokia
65
Radio resource management and telecom features
Figure 6
LTE RL20, Feature Descriptions
EPS bearer establishment by S1AP: E-RAB setup request
The S1AP: E-RAB SETUP REQUEST message has to contain: •
•
•
2.5.4.8
QCI (separately for each EPS bearer) QCI is defined in the E-RAB Level QoS Parameters IE and is used for QCI interpretation. GBR (separately for each EPS bearer and each direction) If the GBR QoS Information IE is missing for a GBR bearer, the setup of this EPS bearer is rejected. Setup of any remaining bearers is continued. ARP (allocation and retention priority) ARP is stored in the eNodeB for later transfer to a target eNodeB during handover.
Radio admission control thresholds Two new thresholds are introduced by radio admission control: • •
GBR threshold for new calls GBR threshold for incoming calls.
These additional radio admission thresholds for GBR bearers can be configured by the operator on cell basis. The uplink and downlink schedulers use the GBR delay budget for their scheduling decisions. The delay budget can be configured by the operator. Non-GBR data transmission might be reduced to achieve the GBR for voice users. Dynamic scheduling is applied for EPS bearers with QCI=1. The support of EPS bearers with QCI=1 can be enabled/disabled per eNodeB via OAM.
2.5.5 System impacts This feature needs the LTE7: Support of multiple EPS bearerfeature to be enabled.
66
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
2.5.6 Sales information This feature is optional.
2.5.7 User interface 2.5.7.1
Parameters Table 19: Parameters for the LTE10: EPS bearers for conversational voice feature shows the parameters implemented for the LTE10: EPS bearers for conversational voice feature.
Table 19
Parameters for the LTE10: EPS bearers for conversational voice feature
Name
Max Number QCI1 DRBs (GBRs)
Short name
Object
maxNumQci1D LNCEL rb
Description
Threshold for the maximum number of established QCI1-GBR-DRBs in the cell. QCI1-DRBs are additional data radio bearers in the cell and are also checked against the threshold maxNumActDrb.
Range / Step
Default value
0..200, step 100 (for 1 10 MHz BW)
The maximum additional margin depends on the bandwidth of the cell. The following values are allowed: 5 MHz bandwidth 0 .. 150 10 MHz bandwidth 0 .. 200 15 MHz bandwidth 0 .. 200 20 MHz bandwidth 0 .. 200 Please note that the default value is not suitable for all bandwidths. The recommended values are: 5 MHz bandwidth 75 10 MHz bandwidth 100 15 MHz bandwidth 100 20 MHz bandwidth 100 Dependencies: maxNumQci1Drb + max( addNumQci1DrbRadioReasHo, addNumQci1DrbTimeCriticalHo) must be less than the margin values for the used bandwidth (see values above (150,200))
DN0978033 Issue: 02N
© 2016 Nokia
67
Radio resource management and telecom features
Table 19
LTE RL20, Feature Descriptions
Parameters for the LTE10: EPS bearers for conversational voice feature (Cont.)
Name
Add Number QCI1 DRB for RadioReasHo
Short name
Object
addNumQci1Dr LNCEL bRadioReasHo
Description
Range / Step
Additional margin for the maximum number of active GBRs in the cell accessing the cell via hand over with HO-cause: "HO desirable for radio reasons". This margin is added to the threasold maxNumQci1Drb.
Default value
0..200, step 15 (for 10 1 MHz BW)
Hand over traffic shall have some preference against new upcoming traffic in the cell. The maximum additional margin depends on the bandwidth of the cell. The following values are allowed: 5 MHz bandwidth 0 .. 150 10 MHz bandwidth 0 .. 200 15 MHz bandwidth 0 .. 200 20 MHz bandwidth 0 .. 200 Please note that the default value is not suitable for all bandwidths. The recommended values are: 5 MHz bandwidth 15 10 MHz bandwidth 15 15 MHz bandwidth 30 20 MHz bandwidth 40 Dependencies: maxNumQci1Drb + max( addNumQci1DrbRadioReasHo, addNumQci1DrbTimeCriticalHo) must be less than the margin values for the used bandwidth (see values above (150,200)) Add Number Drb TimeCriticalHo
addNumDrbTi meCriticalHo
LNCEL
Additional margin for the maximum number of active DRBs in the cell accessing the cell via HO with HO-cause: "Time Critical HO". This margin is added to the threshold maxNumActDrb.
0..4200, step 1
60 (for 10 MHz BW)
Hand over traffic shall have some preference against new upcoming traffic in the cell. The maximum additional margin depends on the bandwidth of the cell. The following values are allowed: 5 MHz bandwidth 0 .. 2400 10 MHz bandwidth 0 .. 2400
68
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 19
Radio resource management and telecom features
Parameters for the LTE10: EPS bearers for conversational voice feature (Cont.)
Name
Short name
Object
Description
Range / Step
Default value
15 MHz bandwidth 0 .. 4200 20 MHz bandwidth 0 .. 4200 Please note that the default value is not suitable for all bandwidths. The recommended values are: 5 MHz bandwidth 60 10 MHz bandwidth 60 15 MHz bandwidth 120 20 MHz bandwidth 150 Dependencies: maxNumActDrb + max( addNumDrbRadioReasHo, addNumDrbTimeCriticalHo) must be less than the margin values for the used bandwidth (see values above (2400,4200)) QCI Tab 1
QCITab1
LNBTS
Table to translate the S1AP parameter QCI 1 to QCI characteristics. This is a structure including the parameters: delayTarget, dscp, lcgiD, prio, qci, qciSupp, ScheduleBSD, SchedulePrio
delayTarget
delayTarget
Differentiated DSCP Services code point
LNBTS
DelayTarget is the maximum packet delay used by the eNB MAC scheduling algorithm. Part of the structure QCITab1.
0 (50ms) 1 (60ms) 2 (70ms) 3 (80ms) 4 (90ms) 5 (100ms)
3
LNBTS
Differentiated Services code point value associated with the QCI. Possible values based on the IETF. This parameter is part of the QCITab1 Structure.
0..63, step1 46
Allowed values: BE (0), AF11 (10), AF12 (12), AF13 (14), AF21 (18), AF22 (20), AF23 (22), AF31 (26), AF32 (28), AF33 (30), AF41 (34), AF42 (36), AF43 (38), EF (46) Logical channel group identifier
lcgid
DN0978033 Issue: 02N
LNBTS
Logical channel group identifier for buffer status reporting. This parameter is used for configuration of the buffer status reports of the UE according [36.321]. This parameter is part of the QCITab1 Structure
© 2016 Nokia
1
1
69
Radio resource management and telecom features
Table 19
LTE RL20, Feature Descriptions
Parameters for the LTE10: EPS bearers for conversational voice feature (Cont.)
Name
Short name
Object
Description
Range / Step
Default value
Priority
prio
LNBTS
This parameter gives the priority of the EPS bearer according TS23.203.This parameter is part of the QCITab1 Structure
2
2
QoS Class Identifier
qci
LNBTS
QoS Class Identifier. This parameter is part of the QCITab1 Structure
1
1
QCI support
qciSupp
LNBTS
This parameter indicates whether the given QCI is supported and enabled. This parameter is part of the QCITab1 Structure
disabled (0), enabled (1)
1
Scheduling Bucket Size Duration
scheduleBSD
LNBTS
This parameter is used to configure the Bucket Size Duration (BSD) of the UL-scheduler. For GBR bearers scheduleBSD is used by the eNB and UE for the UL scheduling algorithm according [36.321]. The bucket size of a logical channel is calculated by PBR* BSD. This parameter is part of the QCITab1 Structure.
0 (50ms), 1 1 (100ms) 2 (150ms) 3 (300ms) 4 (500ms) 5 (1000ms)
Scheduling Priority
schedulePrio
LNBTS
This parameter is the logical channel priority 2..16, step for the MAC scheduler. For GBR bearers 1 schedulePrio is used by the enB for the scheduling algorithm and by the UE for the UL scheduling algorithm. Increasing priority values indicate lower priorities. This parameter is part of the QCITab1 Structure.
5
Scheduling Type
scheduleType
LNBTS
This parameter specifies how the EPS bearer with QCI5 is scheduled.
1
For the scheduling type “SIGNALLING” the bearer is handled like SRBs. The MAC lcgid is set to 0 and schedulePrio is used for UL and DL-scheduling.
0 (SIGNALLI NG), 1 (NONGBR)
For the scheduling type “NON-GBR” the bearer is handled like other non-GBR bearers. The MAC lcgid is set to unequal 0 and the scheduleweight is used for DL scheduling. Profile101 of PDCP pdcpProf101 paramters
LNBTS
Profile 1 of parameters for RLC UM data radio bearers. This is a structure including the parameters: rohcMaxCid, SnSize, tDiscard
ROHC Maximum CID
LNBTS
This parameter configures the maximum number of ROHC contexts used for a data radio bearer in one direction.The maximum number of ROHC contexts is also restricted by the UE capabilities.
70
rohcMaxCid
© 2016 Nokia
1..16, step1 4
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 19
Radio resource management and telecom features
Parameters for the LTE10: EPS bearers for conversational voice feature (Cont.)
Name
Short name
Object
Description
Range / Step
Default value
This parameter is part of the pdcpProf101 structure. Sequence Number Size
SnSize
LNBTS
This parameter configures the size of the SN field in the PDCP header.If UE does not support the value “7bit”, the value “12bit” will be used.
0 (7bit), 1 (12bit)
0
This parameter is part of the pdcpProf101 structure. Timer Discard
tDiscard
LNBTS
This parameter specifies the parameter discardTimer of [36.331]This parameter indicates the delay before a PDCP PDU along with the corresponding PDCP SDU is discarded from the buffer. This timer shall be set in a way that the packet delay defined by the QCI characteristics is kept. The timer can be disabled by setting the parameter to infinity.
0 (100ms), 0 1 (150ms), 2 (300ms), 3 (500ms), 4 (750ms), 5 (1500ms), 6 (infinity)
This parameter is part of the pdcpProf101 structure. Profile 101 of RLC Parameters
rlcProf101
LNBTS
Profile 1 of RLC paremeters for DRBs in RLC UM mode. This is a structure including the parameters: snFieldLengthDL, snFieldLengthUL, tReord.
SN Field Length Downlink
snFieldLength DL
LNBTS
This parameter configures the length of the SN 0 (5 bit), field for RLC UM procedures in downlink 1 (10bit) direction.If UE does not support the value “5bit”, the value “10bit” is used.
0
This parameter is part of the rlcProf101 structure. SN Field Length Uplink
snFieldLength UL
LNBTS
This parameter configures the length of the SN 0 (5 bit), field for RLC UM procedures in uplink 1 (10bit) direction.If UE does not support the value “5bit”, the value “10bit” is used.
0
This parameter is part of the rlcProf101 structure. Timer Reordering
tReord
DN0978033 Issue: 02N
LNBTS
This parameter specifies the parameter tReordering of [36.331]This timer is used by the receiving side of an UM RLC entity for reordering and PDU loss detection. This timer depends on HARQ RTT and number of HARQ retransmissions.
© 2016 Nokia
0 (0ms), 1 (5ms), 2 (10ms), 3 (15ms), 4 (20ms), 5 (25ms), 6 (30ms), 7
10
71
Radio resource management and telecom features
Table 19
LTE RL20, Feature Descriptions
Parameters for the LTE10: EPS bearers for conversational voice feature (Cont.)
Name
Short name
Object
Description
Range / Step
This parameter is part of the rlcProf101 structure.
2.5.7.2
Default value
(35ms), 8 (40ms), 9 (45ms) 10 (50ms) 11 (55ms) 12 (60ms) 13 (65ms) 14 (70ms) 15 (75ms) 16 (80ms) 17 (85ms) 18 (90ms) 19 (95ms) 20 (100ms), 21 (110ms), 22 (120ms), 23 (130ms), 24 (140ms), 25 (150ms), 26 (160ms), 27 (170ms), 28 (180ms), 29 (190ms), 30 (200ms)
Measurements and counters Table 20: Counters for the LTE10: EPS bearers for conversational voice feature shows the counters for the LTE10: EPS bearers for conversational voice feature.
Table 20
Counters for the LTE10: EPS bearers for conversational voice feature
PI ID
Counter long name (short name)
M8001C419
M8001C420
Description
UEs with buffered UL data for DRB with QCI 1
Average number of UEs with buffered data in UL per logical channel group id mapped to VoIP (QCI1)
UEs with buffered UL data for non-GBR DRB
Average number of UEs with buffered data in UL per logical channel group id mapped to non-GBR bearers (QCI5..9)
2.5.8 Activating the feature This feature requires activation. For instructions see Activating LTE Features.
72
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
2.6 LTE11: Robust header compression 2.6.1 Introduction To The Feature The feature ” LTE11: Robust header compression” introduces the ROHC for EPS bearers with QCI = 1, these are bearers for voice over IP. For those bearers the payload of the IP packets is almost of the same size or even smaller than the header. Over the end-to-end connection, comprised of multiple hops, these protocol headers are extremely important, but over just one link (hop-to-hop) these headers will be compressed (and decompressed at the other end of the link). Application of ROHC over the air link is possible because IP/UDP/RTP header information is not required for relaying data over the air interface to the receiving UE. This feature supports ROHC( Robust header compression) for IP/UDP and IP/UDP/RTP headers. It is described in the RFC 3095 and RFC4815. The IP overhead of the IPv4 or IPv6 is 40 respective 60 bytes. ROHC reduces these values to 2..5 bytes (this is a typical average value).
2.6.2 Benefits The main benefit for operator and customer is a considerable reduction of the overhead being transmitted over the air interface in UL/DL in addition to the voice data, i.e., the IP(v4/v6))/RTP/UDP headers
2.6.3 Requirements 2.6.3.1
Software Requirements The following software is needed: Table 21
Software requirements for different network elements
Network element
DN0978033 Issue: 02N
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
–
SAE GW
–
UE
3GPP release 8
NetAct
–
© 2016 Nokia
73
Radio resource management and telecom features
2.6.3.2
LTE RL20, Feature Descriptions
Hardware Requirements This feature does not require any new or additional hardware.
2.6.4 Functional Description 2.6.4.1
Short Description of ROHC The ROHC algorithm establishes a common context at the compressor and decompressor by transmitting full header and then gradually transition to higher level of compression. ROHC is designed to be flexible to support several protocol stacks and each protocol stack defines a profile within the ROHC framework. The following ROHC profiles are supported by this feature: • • •
ROHC uncompressed (RFC 4995), ROHC RTP (RFC 3095, RFC 4815), ROHC UDP (RFC 3095, RFC 4815)..
The protocol headers are compressed due to redundancy in the header fields of consecutive packets of the same packet stream. A packet classifier can identify different packet streams by the combination of parameters like protocol headers being carried in the packet, the source and destination addresses etc. Initially, a few packets are sent uncompressed and are used to establish the context on both sides of the link.The context comprises information about static fields, dynamic fields and their change pattern in protocol headers . This information is used by the compressor to compress the packet as efficiently as possible and then by the decompressor to decompress the packet to its original state (see Figure 7: Principle of ROHC) Figure 7
Principle of ROHC
Theconceptofflowcontextinheadercompression:
Packetflow
UE
eNB
Compressedpackets
Packetflowin Downloaddirection
Header Compression
feedback
Context
Header Compression
Context
Figure 7: Principle of ROHC shows the download direction, there is also ROHC in the upload direction.
74
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
The ROHC compressor operates in 3 states: Initialization and Refresh (IR), First Order (FO) and Second Order (SO). The states describe the increasing level of confidence about the correctness of the context at the decompressor side. The confidence is reflected in the increasing compression of packet headers. In case of error conditions, as indicated by the decompressor using feedback packets, the compressor can move to a lower state to send packets that carry enough information to fix the error in the context of the decompressor. The compressor always starts in the IR state. In this state, it sends uncompressed packets to establish the context at the decompressor side. Once it gains confidence that the decompressor has the context information, it moves to higher states of operation, either via FO state to SO state or directly to SO state, Figure 8: Compressor States. Figure 8
Compressor States
The decompressor states are shown in the following figure, Figure 9: Decompressor States Figure 9
Decompressor States
ROHC can run in the following Modes: Table 22
Modes of ROHC
Mode
2.6.4.2
Description
U-Mode
In Unidirectional mode, packets are sent in one direction, from the compressor to the decompressor. In cases where the return path of the reserve channels are not available it requires periodic refresh.
O-Mode
In Bidirectional Optimistic mode, a feedback channel is utilized. It does not require periodic refresh.
R-Mode
In Bidirectional Reliable mode, it issues feadback for all context updates.
Bearer Establishment The next figures (Figure 10: EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Attach) and Figure 11: EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Service Request) ) show the EPS Bearer Establishment procedure triggered by the S1AP message INITIAL CONTEXT SETUP REQUEST according 3GPP:
DN0978033 Issue: 02N
© 2016 Nokia
75
Radio resource management and telecom features
• •
LTE RL20, Feature Descriptions
Attach procedure, without included UE radio capabilities (Figure 10: EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Attach)), Service request, with included UE radio capabilities (Figure 11: EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Service Request))
The Initial Context Setup procedure supports the ROHC configuration for the conversational voice GBR EPS bearer. This includes: • • • •
Check of the activation of the robust header compression feature, Check of the ROHC by the UE, Configuration of the ROHC based on the UE capabilities and the PDCP profile for conversational voice if a DRB shall be set up for conversational voice, Configuration of ROHC by the RRC: Connection Reconfiguration procedure, if a DRB shall be set up for conversational voice.
Figure 10
76
EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Attach)
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Figure 11
Radio resource management and telecom features
EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure (Service Request)
In Figure 12: EPS Bearer Establishment Procedure by S1AP: E-RAB Setup Procedure the establishment of a bearer by the S1AP E-RAB Setup procedure is shown. This procedure is initiated in the following cases: • • •
•
The PDN GW request the addition of a new dedicated EPS bearer ([3GPP 23.401), e.g.: the setup of a voice call by IMS The UE requests a resource modification that causes the addition of a new dedicated EPS bearer ([3GPP 24.301]: The UE requests the addition of a new PDN connection including a new default EPS bearer ([3GPP 23.401]), e.g. : start of an IMS based VoIP application or connecting a laptop to a mobile phone. Additionally to the UE requested PDN connectivity, PDN GW might request the addition of new dedicated EPS bearers in combination with the UE requested PDN connectivity procedure ([3GPP 23.401]
The E-RAB Setup procedure supports the ROHC configuration for the conversational voice GBR EPS bearer to be established. This includes • • • •
DN0978033 Issue: 02N
Check of the activation of the robust header compression feature, Check of the support of conversational voice by the UE, Configuration of the ROHC based on the UE capabilities and the PDCP profile for conversational voice Configuration of ROHC by the RRC Connection Reconfiguration procedure.
© 2016 Nokia
77
Radio resource management and telecom features
Figure 12
2.6.4.3
LTE RL20, Feature Descriptions
EPS Bearer Establishment Procedure by S1AP: E-RAB Setup Procedure
PDCP Adaptation for ROHC The eNB supports PDCP Control PDU for interspersed RoHC feedback packets. The ROHC feedback packet exchange is only needed for VoIP services which are subject of header compression profiles. The compressor has the following attributes: • • • • •
It is configurable by the layer 3, It starts in U-mode operation, It transits between the different modes according to the feedback provided by the decompressor (UE side), It interprets and reacts according to information provided through feedback packets received by the decompressor (UE side), It transits (upward/downward) between compressor states, i.e. IR-/ FO-/ SO-state.
Furthermore the eNB supports a feedback channel for the ROHC. This channel is mandatory in O- mode or R - mode of operation. The Header Refresh feature is a further attribute of the compressor: • •
header refreshes according to RFC2507, considering the number of packets in one period and the number of transmitted full headers. the header refreshes apply for FO-state and SO-state (i.e. in IR-state full-headers are anyway transmitted).
The eNB supports timer based downward transition from SO-state to FO-state as well as timer based downward transition from SO-/FO-state to IR-state. The eNB supports a header decompressor for UL data transfer: • •
78
it is configurable by layer L3, it starts with U-mode of operation,
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
• •
Radio resource management and telecom features
it provides feedback (if applicable) which are relavant for the compressor on UE side (e.g. mode changes etc.), it transits (upward/downward) between decompressor states, i.e. no context, static context and full context.
The eNB supports the decompressor states: • • • •
The no-context, static-context and full-context states,. The decompressor starts with the no-context and transits to higher states (no restriction for any kind of transit), The decompressor decides autonomously about any state transition, The decompressor can transit all the way to full-context once it has sucessfully decompressed a header.
2.6.5 System Impacts The following features must be enabled: • •
LTE7: Support of multiple EPS bearer, LTE10: EPS bearers for conversational voice..
2.6.6 Sales Information This feature is optional.
2.6.7 User Interface 2.6.7.1
Parameters Table 23: Parameters for the LTE11: Robust Header Compression shows the parameters implemented for the feature LTE11: Robust Header Compression.
Table 23
Parameters for the LTE11: Robust Header Compression
Name
Short name
Activate PDCP Robust Header Compression
actPdcpRohc
ROHC Maximum CID
rohcMaxCid
Object
LNBTS
LNBTS
Description
Range / Step
This parameter activates the usage of the PDCP Robust Header Compression.
0 (false),
This parameter configures the maximum number of ROHC contexts used for a data radio bearer in one direction. It is part of the structure pdcpProf101.
1..16, step 1
Default value 0
1 (true) 4
2.6.8 Activating the Feature This feature requires activation. For instructions see the Feature Activation Manual: Activation of LTE11.
DN0978033 Issue: 02N
© 2016 Nokia
79
Radio resource management and telecom features
LTE RL20, Feature Descriptions
2.7 LTE13: Rate Capping (UL/DL) 2.7.1 Introduction to the feature With the feature LTE13: Rate Capping (UL/DL) it is possible to restrict the maximum aggregated non GBR throughput in uplink and downlink. The LTE13: Rate Capping (UL/DL) feature introduces throughput measurement filters in UL Scheduler (UL-S) and DL Scheduler (DL-S). UL-S and DL-S control the UE throughput according to the UE available aggregated maximum bit rate (UE-AMBR) values.
2.7.2 Benefits DSL like charging models can be applied with LTE.
2.7.3 Requirements 2.7.3.1
Software requirements Table 24
Software requirements for different network elements
Network element
2.7.3.2
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
NS10 CD2
SAE GW
–
UE
3GPP release 8
NetAct
–
Hardware requirements This feature requires no new or additional hardware.
2.7.4 Functional description The Flexi Multiradio BTS uses the parameter UE Aggregated Maximum Bit Rate (UEAMBR) which is initially sent from the MME via the S1AP: INITIAL CONTEXT SETUP REQUEST message for its bit rate management. The UE-AMBR parameter is stored in the subscriber profile in the HSS.
80
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
The Flexi Multiradio BTS limits the uplink and downlink bit rate of all non-GBR EPS bearers per UE to the level of the signaled UE-AMBR. The Flexi Multiradio BTS considers the aggregated throughput as averaged over one second period. The initially assigned QoS parameter UE-AMBR can be as well changed. It can be increased or decreased by the MME. The Flexi Multiradio BTS supports the following S1AP messages for this: • • •
UE context modification request UE context modification response UE context modification failure
The MME may also change the UE-AMBR parameter at the following procedures (which are not in the scope of this document): • • •
E-RAB SETUP REQUEST E-RAB RELEASE REQUEST PATH SWITCH REQUEST
The following performance counters are supported in order to track the functionality: • • •
number of UE context modification request number of successful modification request number of unsuccessful modifications per cause
The change of the UE-AMBR parameter triggers a re-initialization of the UE-AMBR calculation procedure. The operator can enable/disable the functionality on cell basis by O&M settings. eNB supports rate capping in UL and DL scheduling Uplink and downlink scheduler is able to limit the bit rate of all non-GBR EPS bearers per UE to the level of the signaled UE-AMBR. The aggregate throughput of all non-GBR EPS bearers is averaged over time for comparison to UE-AMBR. As soon as the average aggregate bit rate of all non-GBR bearers exceeds the signaled UE-AMBR, the maximum rate as scheduled to a UE is limited on a per-subframe basis until the average aggregate bit rate drops again below the value of the UE-AMBR. Changes of the UE-AMBR resulting from changes to the bearer combination of a UE or from UE context modification are indicated to the rate capping functionality in schedulers immediately and considered accordingly. UE-AMBR Modification by S1AP UE CONTEXT MODIFICATION REQUEST The Figure 13: UE-AMBR Modification Procedure shows the UE-AMBR Modification procedure trigged by the S1AP message UE CONTEXT MODIFICATION REQUEST.
DN0978033 Issue: 02N
© 2016 Nokia
81
Radio resource management and telecom features
Figure 13
LTE RL20, Feature Descriptions
UE-AMBR Modification Procedure
UE
eNB
MME TriggerfromHSS: InsertSubscriberData
S1AP:UECONTEXTMODIFICATIONREQEST UE-AMBR CheckofUE-AMBR modification
Reconfigurationof UE-AMBRratecapping S1AP:UECONTEXTMODIFICATIONRESPONSE UpdateBearer
The procedure for UE-AMBR modification is triggered by “Insert Subscriber Data” from HSS to MME. MME receives a new “Subscribed UE-AMBR”. The procedure starts in eNB when the eNB receives the S1AP message UE CONTEXT MODIFICATION REQUEST from the MME and the information element “UE Aggregate Maximum Bit Rate” is included. First eNB checks whether the feature “UE-AMBR modification” is activated and then informs the rate capping function of UL and DL schedulers about the modified UE-AMBR. The eNB sends a S1AP acknowledgement UE CONTEXT MODIFICATION RESPONSE to the MME. The MME may start an Update Bearer procedure towards the Serving Gateway or PDN Gateway.
2.7.5 System impacts The LTE13: Rate Capping (UL/DL) feature has no additional impact on the system.
2.7.6 Sales information This feature belongs to the Application Software (ASW) product structure class.
2.7.7 User interface 2.7.7.1
Parameters Table 25: Parameters for the LTE13: Rate Capping UL shows the MME parameters required by UL rate capping feature in Uplink Scheduler UL-S. Table 25 Name Enable rate capping in uplink
82
Parameters for the LTE13: Rate Capping UL Short name rcEnableUl
Object LNCEL
Description Enabling/disabling of rate capping in uplink.
© 2016 Nokia
Range / Step 0 (false), 1 (true)
Default value false
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 25
Radio resource management and telecom features
Parameters for the LTE13: Rate Capping UL (Cont.)
Name
Short name
Object
Rate capping AMBR margin in uplink
rcAmbrMgnUl
LNCEL
Description
Range / Step
Margin factor for the 1.00..1.50, comparison of the measured step 0.01 AMBR and the UE AMBR in uplink.
Default value 1.02
Table 26: Parameters for the LTE13: Rate Capping DL shows the MME parameters required for rate capping functionality in Downlink Scheduler DL-S. Table 26 Name
2.7.7.2
Parameters for the LTE13: Rate Capping DL Short name
Object
Description
Range / Step
Default value
Enable DL rate capping
rcEnableDl
LNCEL
Enabling/disabling of rate capping in DL.
0 (false), 1 (true)
false
DL rate capping AMBR margin
rcAmbrMgnDl
LNCEL
Factor to calculate margin for AMBR to account for overhead of PDCP and RLC.
1.00..1.50, step 0.01
1.03
Alarms There are no alarms related to this feature.
2.7.7.3
Measurements and counters There are no measerements and counters related to this feature.
2.7.8 Activating the feature This feature requires activation. For more information on the activation, see Activating LTE RL10 Features
2.8 LTE22: Emergency Call Handling 2.8.1 Introduction to the Feature The feature “LTE22: Emergency Call Handling” re-uses LTE562 to provide regulatory requirements in initial phase of LTE implementation. To grant proper handling of emergency call UE will be redirected from LTE to another CS capable RAT (WCDMA or GSM). This action is triggered by MME sending CS Fallback High Priority indication to eNB. As a consequence UE will be redirected to another RAT by reusing LTE562 solution (but with a separately configurable UE priorities dependent RedirectedCarrierInfo IE). In addition, one separate admission threshold is used for UEs sending RRC CONNECTION REQUEST message with establishmentCause set to 'emergency'. This feature can be switched on/off by operator.
DN0978033 Issue: 02N
© 2016 Nokia
83
Radio resource management and telecom features
LTE RL20, Feature Descriptions
2.8.2 Benefits Fulfillment of regulatory requirements.
2.8.3 Requirements 2.8.3.1
Software Requirements Table 27
Software requirements for different network elements
Network element
2.8.3.2
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
NS20
SAE GW
–
UE
3GPP release 8
NetAct
–
Hardware Requirements Table 28
Hardware requirements for different network elements
Network element
Required hardware
MME
...
eNodeB
FSM R2 or FSM R3
UE
...
2.8.4 Functional Description 2.8.4.1
Functional Overview/Details Emergency call is handled through CS fallback procedure to GSM or to WCDMA. The redirection is applied as the inter-RAT mobility mechanism. The Flexi Multiradio BTS supports emergency call handling when RRC connected or RRC idle in advance to emergency call setup: •
84
The MME notifies the eNB about the emergency call by CS Fallback High Priority indication by initial context setup or by UE context modification procedures.
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
•
Radio resource management and telecom features
The eNB evaluates the RRC connection establishment cause in the RRC connection request message in order to identify emergency calls when the call setup starts from the idle state. Separate emergency admission control thresholds will be applied by the establishment of emergency call related RRC connection. Capacity license shall not reject processing of emergency call.
The emergency call handling reuses the feature LTE000562: CS fallback by redirection to WCDMA or GSM. The separate priority for emergency purpose per layer is operator configurable. The applicable target layers for emergency purpose must have seamless coverage over the coverage of the source LTE cell. Thus for example full set of reused BCCH carriers is recommended in the case of GSM target layer. The emergency call feature supports 3GPP defined UE behavior for scoping unsuccessful redirection scenario for emergency purpose. The following counters are provided on cell level: • • • •
Number of Signalling Connection Establishment attempts for emergency calls Number of Signalling Connection Establishment completions for emergency calls Number of Signalling Connection Establishment failures for emergency calls due to missing RB (Radio Bearer) resources Number of CS Fallback attempts for emergency call with redirection via RRC Connection Release
The feature can be enabled / disabled via O&M.
2.8.4.2
Emergency Call Handling This feature is very similar to CS Fallback with redirection, described in LTE562. Significant differences are: • • • •
2.8.4.3
Feature LTE22 is enabled and properly configured in eNB Operator may configure different redirect targets (or different target priorities) than for LTE562 MME uses CS Fallback High Priority indication in case of Emergency Call In case UE is in idle mode, eNB checks the RRC Connection Request for call establishment cause and in case it is 'Emergency', then a separate admission threshold is used and calls will not be rejected due to capacity license limitations
Emergency Call Support eNodeB supports CS-Fallback procedure using RRC Connection Release with redirection to an operator specifiable RAT & frequency if UE or MME initiates an emergency call.
2.8.4.3.1
Emergency Call trigger Emergency call trigger for eNB: •
DN0978033 Issue: 02N
MME is sending CS Fallback Indicator IE with value 'CS Fallback High Priority'
© 2016 Nokia
85
Radio resource management and telecom features
LTE RL20, Feature Descriptions
In case UE is idle mode, eNB checks RRC Connection Request for call establishment cause and in case it is 'Emergency', then a separate admission threshold is used and calls will not be rejected due to capacity license limitations.
2.8.4.3.2
Initiation of CS Fallback with Redirect due to Emergency Call CS Fallback with Redirect will be initiated by the eNB when CS Fallback Indicator with value 'CS Fallback High Priority' will be received from MME.
2.8.4.3.3
Selection of target Radio Access Technology for Emergency Call eNB shall check O&M parameters provided in MOC REDRT and choose target RAT according to emerCallPrio and redirRAT parameters. First, parameter with highest priority of emerCallPrio will be taken to consideration, where value 1 means highest priority and higher values lower priority. When this parameter is set to 'not used', such RAT target will not be used for CS Fallback with redirection. eNB builts a list of redirection target RAT definitions starting with lowest values of emerCallPrio parameter, which has unique values, so that list can be build in unambiguous way. Target RATs that are not available in UE Capabilities information will be excluded from that list. Each element on the list will be an instance of MOC REDRT and RedirectedCarrierInfo IE will be built according to redirRAT parameter. If redirRAT = geran eNodeB builds the IE RedirectedCarrierInfo using same mechanism as for UE Context Release with redirection. eNodeB contructs CarrierFreqsGERAN from O&M parameters redirGStartingARFCN, redirGBandIndicator and redirGARFCNValue. For this eNodeB checks whether the selected carrierFreqs are within an SupportedBandGERAN listed in the UE-Capabilities. This is done by checking whether the ARFCN-ValueGERAN included in CarrierFreqsGERAN is within one of the SupportedBandGERAN listed in the IRAT-ParametersGERAN in UE-Capabilities. If the selected carrierFreqs are supported by the UE eNodeB builds the IE RedirectedCarrierInfo. Otherwise eNodeB retries with the secondary target. If redirRAT = utra-FDD eNodeB builds the IE RedirectedCarrierInfo using same mechanism as for UE Context Release with redirection. eNodeB uses ARFCNValueUTRA from redirFreqUtra. For this the eNodeB checks whether the selected ARFCN-ValueUTRA is within an SupportedBandListUTRA-FDD listed in the UECapabilities. If the selected ARFCN is supported by the UE eNodeB builds the IE RedirectedCarrierInfo. Otherwise eNodeB retries with the secondary target.
2.8.4.3.4
Initiating UE Context Release After selection of the redirection target, eNodeB initiates UE Context Release Procedure. In RRC Connection Release Request, ReleaseCause is set to "other" and redirectedCarrierInfo is set. IdleModeMobilityControlInformation is not be present. In S1AP UE Context Release Request the Cause values are set to Radio Network Layer (CS Fallback Triggered).
2.8.4.3.5
Emergency Call - Unsuccessful Procedure RRC Connection Request is not accepted by eNB when UE makes Initial Access in idle mode situation - if RAC rejects an emergency call, there is no difference to the subsequent steps compared to the case, that RAC rejects a normal RRC connection
86
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.8.4.4
Radio resource management and telecom features
Radio Admission Control (RAC) RAC is adapted to give emergency calls a higher connectivity prospective (LTE22). RAC introduces a new (higher) threshold for emergency call handling in order to give emergency calls a higher chance to be successfully established. These emergency calls are handed over as soon as possible to another RAT using the CS fallback, for example the emergency call is only for a short time frame hosted in the LTE system.
2.8.4.4.1
RAC introduces a new Threshold for Emergency Call Handling For emergency calls RAC uses a new threshold, which is near to the system limits in order to allow as much emergency calls as possible, but low enough to prevent the system from overload in bursty situations. The following threshold is used for emergency calls in case of event SRB Setup. This threshold is retrieved from Q&M database at startup and is considered only if the feature LTE22 is enabled: •
2.8.4.4.2
maxNumRrcEmergency - threshold for new SRB1 requests with establishment cause "emergency".
Admission of emergency calls with higher threshold value The admission control function is expanded for LTE22 "Emergency Call Handling" by the following components: • • • • •
•
RAC will receive a new "emergency session active" indication in the event SRB setup from UE State Handling RAC will define a new threshold "maxNumRrcEmergency". This threshold is configured by operator (new O&M-parameter) near to the max. possible system limit. Emergency sessions are counted as additional RRC-Connections. The new threshold used for emergency calls can cause a higher counter value for maxNumRrc than it would be possible for normal SRB Setups respective HO cases. The check on the enabled feature LTE22 is done by UE State Handling. RAC must only reflect on the indication emergency session active. After handover to an other RAT (GSM or WCDMA) the UE is released with the event UE Release and RAC will decrement the RRC-counter.
Emergency Call Handling is an optional feature. When enabled, it is be activated for the whole eNodeB. If the feature is enabled, eNB uses separate Admission threshold for incoming Emergency Calls and will use CS Fallback with redirection procedure for UE to redirect emergency call to UTRAN or GERAN. In this case capacity license availability will not be checked. If deactivated, eNB will not use separate Admission threshold for incoming Emergency Calls and capacity license check will be performed, so it will be handled as normal call and CS Fallback usage will depend on LTE562 feature activation. This is not checked by RAC.
DN0978033 Issue: 02N
© 2016 Nokia
87
Radio resource management and telecom features
2.8.4.5
LTE RL20, Feature Descriptions
Radio Network Layer (RNL) support for Emergency Call via Redirection RNL provides new parameters for: • • • •
feature enabling definition of additional dedicated redirection targets prioritisation of redirection targets a separate admission control threshold for emergency calls
2.8.5 System Impacts 2.8.5.1
Dependencies Between Features There is no real feature dependency in the sense that other feature must be activated, however LTE22 feature is reusing implementation of feature LTE562 CS Fallback with redirection. There is an impact on the feature LTE423 because the target priority is no longer derived from the instance number but from new priority parameters within REDRT.
2.8.5.2 2.8.5.2.1
Impacts on Interfaces External Interfaces New messages on S1AP are supported: • • •
UE Context Modification UE Context Modification Response UE Context Modification Failure
New messages on RRC are supported: No new or modified messages. RRC:RRC Connection Release with IE redirectedCarrierInfo is used already in RL10 for LTE423.
2.8.5.3
Impacts on Network and Network Element Management tools The feature introduces the following additional O&M parameters: • •
2.8.5.4 2.8.5.4.1
Feature activation flag enableEmerCallRedir on BTS level Additional Performance Counter
Impacts on System Performance and Capacity System Performance CS Fallback with redirect needs longer than the direct call setup in UTRAN or GERAN as the UE has to leave the LTE cell and reconnect to the target network first before setting up the call as usual.
88
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
The bulk of the additional delay (2.0 s) is related to the UE cell leave and reconnection procedure after the UE received the connection release request. eNB or other components on the LTE side do not contribute to this delay. In total the CSFB with redirect additional delay for a mobile terminated call is less than 2.15 s, where the additional delay is defined as the time from the RRC Connection Request in the LTE network to the Paging Response in the target network.
2.8.5.4.2
System Capacity System capacity is not impacted by CSFB
2.8.6 Sales Information Table 29
Sales information
BSW/ASW
License control in network element
License control attributes
ASW
-
-
2.8.7 User Interface 2.8.7.1
Parameters Table 30: Parameters for the LTE22: Emergency Call Handling shows the parameters implemented for the feature LTE22: Emergency Call handling.
Table 30
Parameters for the LTE22: Emergency Call Handling
Name
Short name
Redirection Priority for Emergency Call
emerCallPrio
Max Number RRC Emergency
Enable Emergency Call Via Redirection
DN0978033 Issue: 02N
Object
REDRT
Description
Range / Step
Default value
This parameter defines priority for target RAT in selection of redirection target during Emergency Call handling procedure.
1..6
maxNumRrcEmer LNCEL gency
Threshold for the maximum number of UEs in the cell which may establish a RRCconnection for an emergency call
0,1,2,...,840
enableEmerCallR LNBTS edir
The parameter enables the feature 'Emergency Call Via Redirection'. The feature can be only created if at least one redirection target for UTRAN or GSM has been created before.
ENUMERATE disabled D (enabled, disabled)
© 2016 Nokia
440
89
Radio resource management and telecom features
Table 30
LTE RL20, Feature Descriptions
Parameters for the LTE22: Emergency Call Handling (Cont.)
Name
Short name
Object
Description
Range / Step
Activate Emergency Call Via Redirection
actEmerCallRedir LNBTS
The parameter activates the feature 'Emergency Call Via Redirection'.The feature can be only activated if at least one redirection target for UTRAN or GSM has been created before.
0 (Disabled), 1 (Enabled)
Naming Attribute Of MOC REDRT
redrtld
This parameter is the naming attribute of the MOC REDRT.
0..5, step 1
2.8.7.2
REDRT
Default value 0
Measurements and Counters Table 31: Counters for the LTE22: Emergency Call Handling shows the counters for Emergency Call Handling
Table 31
Counters for the LTE22: Emergency Call Handling
PI ID
Counter long name (short name)
M8013C21
Number of Signalling Connection Establishment attempts for emergency calls
Number of Signalling Connection Establishment attempts for emergency calls
M8013C22
Number of Signalling Connection Establishment completions for emergency calls
Number of Signalling Connection Establishment completions for emergency calls
M8013C23
Number of Signalling Connection Establishment failures for emergency calls due to missing RB (Radio Bearer) resources
Number of Signalling Connection Establishment failures for emergency calls due to missing RB (Radio Bearer) resources
CS Fallback attempts for emergency call reason with redirection via RRC Connection Release
The number of CS Fallback attempts for emergency call reason with redirection via the RRC Connection Release
M8016C13
Description
2.8.8 Activating the Feature The feature ‘Emergency Call handling’ needs to be activated with the parameter actEmerCallRedir. If activated it applies for the whole eNB. For instructions see Activating LTE Features.
90
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
2.9 LTE54: Intra-LTE handover via S1 2.9.1 Introduction to the Feature The feature LTE54: Intra-LTE handover via S1 supports inter eNB intra-LTE handover over S1. With S1-based handover, a UE can be handed over from one LTE cell to another LTE cell (of another eNB) without the usage of the X2 interface. X2 interface between Source and Target eNB may be non-existent, not operable or its use for handover may be forbidden by O&M. Unlike the X2-based handover,the S1-based handover is routed via the Core Network and therefore provides the possibility to the Core to change the serving MME and/or the serving S-GW.
2.9.2 Benefits This feature supports MME and S-GW relocation scenarios.
2.9.3 Requirements 2.9.3.1
Software Requirements Table 32
Software requirements for different network elements
Network element
2.9.3.2
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
NS20
SAE GW
NG20
UE
3GPP release 8
NetAct
-
Hardware Requirements Table 33
Hardware requirements for different network elements
Network element
DN0978033 Issue: 02N
Required hardware
MME
-
eNodeB
FSM R2 or FSM R3
© 2016 Nokia
91
Radio resource management and telecom features
Table 33
LTE RL20, Feature Descriptions
Hardware requirements for different network elements (Cont.)
Network element UE
Required hardware -
2.9.4 LTE54: Intra-LTE Handover via S1 2.9.4.1
Functional Overview/Details The following S1 based intra-LTE handover scenarios are supported by the Flexi Multiradio BTS: • • •
inter-eNB, intra-MME and intra-S-GW inter-eNB, inter-MME and intra-S-GW inter-eNB, inter-MME and inter-S-GW
S1 based handover is an alternative handover mechanism to the X2 based handover which is used if X2 interface is not available or cannot be used because Core Network Nodes need to be relocated. Source eNodeB will decide whether a handover is executed via the X2-Interface or via S1-interface. Core Network is not capable of influencing this decision. However, the operator can force an S1-based handover by blacklisting neighbour-cells for X2-based handover via O&M Configuration. X2-handover mechanisms are reused as much as possible. Especially on the Air interface no difference exists at all. S1 based handover is applicable to the intra frequency handover as well as to the inter frequency handover. For the UE it is even transparent for S1handover additions whether the handover is inter frequency or intra frequency. For a S1- handover 1. one instance of LNADJ (under LNBTS) for each neighbored eNB must be installed. 2. one instance of LNADJL (under LNADJ) for each neighbored eNB must be installed.
2.9.4.2
Handover trigger In general, the Handover trigger for all LTE Handover variants (S1,X2 and intra eNB) is the same. The handover is triggered either via LTE intra-frequency measurements or via LTE inter-frequency measurements (if the feature is enabled). The source eNB initiates the S1-handover after receiving a measurement report form the UE by sending a S1AP:HANDOVER REQUIRED message to the MME. The MME prepares the resources at the target eNB via the S1AP:HANDOVER REQUEST message. The S1AP: HANDOVER CANCEL message shall be sent by the source eNB to the MME once the source eNB decides to cancel an ongoing S1 handover. Receipt of the S1AP: HANDOVER CANCEL ACKNOWLEDGE indicates that the MME is ready to take part in a new handover procedure. Upon receiving the S1AP: HANDOVER CANCEL ACKNOWLEDGE message at the source eNB, the source eNB shall retry the handover towards another handover target cell. Handover retries are based on the same logic for S1, X2 and intra eNB handovers.
92
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.9.4.3
Radio resource management and telecom features
Handover Target and Mode Selection Several types of handover procedures can be applied in LTE depending on the selected HO target cell.To select the applicable procedure it needs to be considered whether: • • •
target cell is an LTE cell or a cell of another RAT (for example UTRAN, GERAN,...) target cell is served by own eNodeB or another LTE eNodeB X2 connection to Target eNodeB exists
Handover Target selection is executed in two steps. The first step gives the trigger that a HO shall be executed, defines the urgency of the HO and identifies a prioritized list of HO target cells. This is based on measurement reports from the UE but does not consider network internal aspects as for example X2 connectivity or the possibility to perform data forwarding. In the second step, the final HO target decision and, if needed, the retry of HO with another cell after HO preparation failure is performed. Furthermore a new handover preparation is not initiated before a former HO preparation has been finalized (successfully or unsuccessfully).
2.9.4.3.1
Handover Mode selection for S1 based handover With the new introduced feature LTE54 a HO via S1 is possible now. Dependent on the output from RRM Handover Algorithm, the eNB selects the handover target cell and derive the handover mode from the selected target cell. Possible HO Modes are: • • •
Intra enB HO Intra LTE inter eNB HO via X2 Intra LTE inter eNB HO via S1
Cells can be excluded as candidates for HO target cells for several reasons: - cells are blacklisted for handover - cells according to the HO restriction list provided by MME - barred intra eNB cells eNodeB checks whether the Target cell is a known LTE Target Cell but no X2 Handover is possible. If this is fulfilled, Inter eNodeB Handover via S1 is executed. This check is not neccessary for intra eNodeB Target cells. For intra eNodeB Target cells always intra eNodeB handover is applied.X2 handover is considered as impossible if: • • • •
2.9.4.4
No connection to the target eNodeB exists (related X2-link status is unavailble). The target cell is listed in the handover blacklist with attribute "Blacklisted Topologies" set to "onlyX2". LTE neighbor relation identifier (LNREL) exists for the target cell where handoverAllowed parameter is set to "onlyS1" or "forbidden" value. The UE serving PLMN-ID is not supported in the target cell.
Handover over S1 interface Successful Inter eNB Handovers over the S1 interface are composed of the same four phases as X2- based handover •
DN0978033 Issue: 02N
Handover decision
© 2016 Nokia
93
Radio resource management and telecom features
• • •
2.9.4.4.1
LTE RL20, Feature Descriptions
Handover preparation Handover execution Handover completion
Handover decision Handover decision is made based on evaluation of measurements report within source eNB.
2.9.4.4.2
Handover preparation Send S1AP: HANDOVER REQUIRED message to source MME. When the decision has been made to handover the UE to another eNodeB via S1 or to another RAT, the source eNB shall send an S1AP: HANDOVER REQUIRED message to source MME over the S1interface. During the handover preparation phase MME sends an S1AP: HANDOVER REQUEST message to the target eNodeB containing the needed parameters. Upon receiving this message, the target eNB shall initiate the Handover Preparation phase. With the S1AP: HANDOVER COMMAND the preparation phase is finished. The handover execution is initiated by the MME with the S1AP:HANDOVER COMMAND message to the source eNB.
2.9.4.4.3
Handover execution After reception of the handover command source eNB sends a RRC:RRCConnectionReconfiguration message to the UE. This RRC message forces the UE to the new cell. The target eNB sends a S1AP:HANDOVER NOTIFY message in case of a successful handover to the MME.
2.9.4.4.4
Handover completion After the RRC CONNECTION RECONFIGURATION COMPLETE message is received in the target eNB, the source eNB releases the radio resource associated with the UE in the source cell after receving S1AP: UE CONTEXT RELEASE COMMAND. Also the RRM of source cell is informed that the UE has been handed over to another cell. The switch from source cell to target cell is seamless for S1 data. In particular, it may neither loose nor destroy any GTP-U PDU.
2.9.4.5 2.9.4.5.1
Data forwarding Support of indirect data forwarding eNodeB supports indirect data forwarding of DL data from Source eNodeB to Target eNodeB via the S1-interface
94
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.9.4.5.2
Radio resource management and telecom features
Determination of which bearers are subject to data forwarding at source eNB on HO via S1 Before configuring the parameters for the S1AP:HANDOVER REQUIRED message, the source eNB shall determine which bearers are subject to data forwarding.
2.9.4.5.3
Resource Allocation at Target eNB Resource allocation at the target eNB involves the following steps: • • • • • • • • • •
2.9.4.6
configuring S1 bearer(s) at the target eNB and the S-GW configuring SRBs and DRB(s) for the UE in the target cell configuring measurements for the UE in the target cell storing AMBR information storing UE Capability Information configuring AS security for the UE configuring a fast method to allow the UE to synchronise with the target cell compare source and target cell configurations to generate a delta configuration generating an RRC: RRC CONNECTION RECONFIGURATION message to be sent to the UE via the source eNB configuring S1 bearer(s) at the target eNB for DL data forwarding from the source eNB
Performance Counters Performance counters are supported per cell in order to track the performance of the S1 intra-LTE handover via S1, for example: • • • • •
Number of Inter eNB S1-based Handover preparations Number of failed Inter eNB S1-based Handover preparations per cause Number of Inter eNB S1-based Handover attempts Number of successful Inter eNB S1-based Handover completions Number of Inter eNB S1-based Handover failures per cause
Performance counters related to neighbor cell related measurement are: • • • •
Number of failed Inter eNB Handover preparations per cause per neighbour cell relationship Number of Inter eNB Handover attempts per neighbour cell relationship Number of successful Inter eNB Handover completions per neighbour cell relationship Number of Inter eNB Handover failures per neighbour cell relationship
2.9.5 System Impact The feature has no additional impacts on the system.
2.9.5.1
Dependencies Between Features There are interdepedencies between the following features:
DN0978033 Issue: 02N
© 2016 Nokia
95
Radio resource management and telecom features
•
2.9.5.2
LTE RL20, Feature Descriptions
LTE492: Automated neighbor relation (ANR)
Impact on Interfaces The feature has no additional impacts on interfaces.
2.9.5.2.1
External Interfaces New S1 messages • • • • • • • • • • •
2.9.5.3
S1AP: HANDOVER REQUIRED S1AP: HANDOVER REQUEST S1AP: HANDOVER REQUEST ACKNOWLEDGE S1AP: HANDOVER COMMAND S1AP: eNB STATUS TRANSFER S1AP: MME STATUS TRANSFER S1AP: HANDOVER NOTIFY S1AP:HANDOVER CANCEL S1AP: HANDOVER CANCEL ACKNOWLEDGE S1AP: HANDOVER FAILURE S1AP:HANDOVER PREPARATION FAILURE
Impact on Network and Network Element Management tools The feature introduces the following additional O&M parameters: • • • • •
2.9.5.4 2.9.5.4.1
Feature Activation Flag Priority indicator between X2-HO & S1-HO Interface specific blacklists need to set theme by autoconfiguration and/or configuration by Netact Additional Performance Counters
Impact on System Performance and Capacity System Performance C-plane procedure time (also called C-plane latency) and U-plane interruption during a S1 handover are the same as for X2 handover. Any additional delay in the overall sequence occurs either before or after the critical time window, which starts when the source eNB receives the HO command and ends when the target eNB receives RRC Connection Reconfiguration Complete and resumes data transmission to the UE. Background activity (for example the status transfer or S-GW change) via S1 which takes longer than in X2 handover is executed in parallel while the UE leaves the initial cell and attaches to the target eNB. Therefore, these differences between X2 and S1 handover do not have impact on C-plane latency or U-plane interruption.
2.9.5.4.2
System Capacity The feature has no additional impacts on System Capacity.
96
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Radio resource management and telecom features
2.9.6 Sales Information Table 34
Sales information
BSW/ASW
License control in network element
License control attributes
ASW
-
-
2.9.7 User Interface 2.9.7.1
Parameters Table 35: Parameters for the LTE54: Intra LTE Handover via S1 shows the parameters implemented for the feature LTE 54: Intra LTE Handover via S1.
Table 35
Parameters for the LTE54: Intra LTE Handover via S1 Structure
Name
Short name
Object
Description
Range / Step
Default value
Activate intra LTE S1based handover
actLTES1Ho
LNBTS
This parameter enables the enabled, feature Intra LTE Inter eNodeB disabled Handover via S1
disabled
Handover Topology Priority
prioTopoHO
LNBTS
This parameter is used to define priorities between the 3 topology options for intra LTE handover
all equal
all equal, intra>inter,intr a>X2>S1,low prio S1
1) Intra eNB HO 2) HO via X2 3) HO via S1 Supervision Timer For The Preparation For Intra LTE Handover
tS1RelPrepL
LNBTS
Guard against failure of the 50, 100, ... MME to respond in preparation 2000 ms phase of intra LTE S1 handover
Blacklisted cell for intra and inter freq HO list
blacklistHoL
LNCEL
This is a list of blacklisted intrafrequency neighbouring cells for active mode mobility. Cells are identified by their PCI.
LNCEL
"This parameter is introduced allEqual (0), to allow blacklisting for X2onlyX2 (1) Handover only other HO variants are still allowed If set to ""all"" the respective entry in blacklistHoL is valid for all kinds of Handover Topology. If set to ""onlyX2"", handover to
Blacklisted topologies blacklistTopo
DN0978033 Issue: 02N
© 2016 Nokia
500 ms
allEqual (0)
blacklistHoL
97
Radio resource management and telecom features
Table 35
LTE RL20, Feature Descriptions
Parameters for the LTE54: Intra LTE Handover via S1 (Cont.) Structure
Name
Short name
Object
Description
Range / Step
Default value
the respective entry in blacklistHoL shall only be excluded as targets for X2based handover but may still be used as target for S1 based handover. This parameter is only evaluated for inter eNodeB target cells which can be used as target for X2Handover as well as for S1Handover" eUTRA carrier frequency
freqEutra
LNCEL
This parameter must be 0...65535, configured for an interstep 1 frequency cell. It will be taken as an intra-frequency cell if this parameter is set to ownCarrierFreq
Range of physical cell id range
phyCellIdRange
LNCEL
Indicates the number of PCIs in the range (including startPCI). If Parameter rangePCI is only one, PCI (startPCI) is specified.
n4 (0), n8 (1), n12 (2), n16 (3), n24 (4), n32 (5), n48 (6), n64 (7), n84 (8), n96 (9), n128 (10), n168 (11), n252 (12), n504 (13), noRange (14)
blacklistHoL
Start of physical cell id range
phyCellIdStart
LNCEL
Indicates the lowest PCI in the range
0...503, step 1 -
blacklistHoL
2.9.7.2
65536
blacklistHoL
Measurements and Counters Table 36: Counters for LTE 54: Intra LTE Handover via S1. shows the counters for LTE54
Table 36
PI ID
Counters for LTE 54: Intra LTE Handover via S1.
Counter long name (short name)
Description
M8014C14
Inter eNB S1-Handover preparations
Number of Inter eNB S1-based Handover preparations
M8014C15
Failed Inter eNB S1-Handover preparations due to timer
Number of failed Inter eNB S1-based Handover preparations due to expiry of the guarding timer TS1RELOCprep.
98
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
Table 36
PI ID
Radio resource management and telecom features
Counters for LTE 54: Intra LTE Handover via S1. (Cont.)
Counter long name (short name)
Description
M8014C16
Failed Inter eNB S1-Handover preparations due to target eNB admission control
Number of failed Inter eNB S1-based Handover preparations with cause "No Radio Resources Available in Target Cell".
M8014C17
Failed Inter eNB S1-Handover preparations due to other reason
Number of failed Inter eNB S1-based Handover preparations due to reception of the S1AP: HANDOVER PREPARATION FAILURE message with a cause other than "No Radio Resources Available in Target Cell."
M8014C18
Attempted inter eNB S1-HO
Number of Inter eNB S1-based Handover attempts
M8014C19
Successful inter eNB S1-HO
Number of successful Inter eNB S1-based Handover completions
M8014C20
Inter eNB S1-HO failures due to timer
Number of Inter eNB S1-based Handover failures
M8015C5
Number of failed Inter eNB Handover preparations per neighbour cell relationship
The number of failed Inter eNB Handover preparations per cause per neighbour cell relationship. Note: Parts of the Handover preparation will be executed in the target eNB.
M8015C6
Number of failed Inter eNB Handover preparations per neighbour cell relationship due to expiration of guarding timer TX2RELOCprep
The number of failed Inter eNB Handover preparations per neighbour cell relationship due to expiration of the respective guarding timer. Note: Parts of the Handover preparation will be executed in the target eNB.
M8015C7
Number of failed Inter eNB Handover preparations per neighbour cell relationship due to admission control in the target eNB
The number of failed Inter eNB Handover preparations per neighbour cell relationship due to failures in the HO preparation on the target side, for example caused by "No Radio Resource Available in Target cell". Note: Parts of the Handover preparation will be executed in the target eNB.
M8015C8
Number of Inter eNB Handover attempts per neighbour cell relationship
The number of Inter eNB Handover attempts per neighbour cell relationship
M8015C9
Number of successful Inter eNB Handover completions per neighbour cell relationship
The number of successful Inter eNB Handover completions per neighbour cell relationship
Number of Inter eNB Handover failures per cause per neighbour cell relationship
The number of Inter eNB Handover failures per cause per neighbour cell relationship
M8015C10
DN0978033 Issue: 02N
© 2016 Nokia
99
Radio resource management and telecom features
LTE RL20, Feature Descriptions
2.10 LTE55: Inter-frequency handover 2.10.1 Introduction to the Feature The feature LTE55: Support of inter-frequency handover supports several inter-frequency handover scenarios. eNB supports inter-frequency handover in which handover decision is based on RSRP or RSRQ (DLmeasurement). Triggers can be "coverage HO" and "Better Cell HO". Typically, the UE requires measurement gaps for performing inter-frequency measurements, depending on the UE capability. UE performance measurements are done while data transmission between the UE and the source eNB still continues. Therefore, KPIs like U-plane break duration or C-plane break duration do not depend on these UE performance measurements, and the system performance of inter-frequency HO is expected to be the same as for intra-frequency HO.
2.10.2 Benefits Inter-frequency handover allows service continuity for LTE deployment in different frequency bands as well as for LTE deployments within one frequency band but with different center frequencies. These center frequencies can also cover cases with different bandwidths, for example 5 MHz and 10 MHz.
2.10.3 Requirements 2.10.3.1
Software Requirements Table 37
Software requirements for different network elements
Network element
100
Required software release
System release
RL20
eNodeB
LBTS2.0
MME
NS20
SAE GW
NG20
UE
3GPP release 8
NetAct
–
© 2016 Nokia
DN0978033 Issue: 02N
LTE RL20, Feature Descriptions
2.10.3.2
Radio resource management and telecom features
Hardware Requirements Table 38
Hardware requirements for different network elements
Network element
Required hardware
MME
...
eNodeB
FSM R2 or FSM R3
UE
...
2.10.4 Functional Description 2.10.4.1
Functional Overview/Details The following inter-frequency handover scenarios are supported by the Flexi Multiradio BTS: • • • • • •
2.10.4.2
intra-eNB, inter-frequency band intra-eNB, intra-frequency band with different center frequency inter-eNB, inter-frequency band via X2 inter-eNB, intra-frequency band with different center frequency via X2 inter-eNB, inter-frequency band via S1 (if enabled) inter-eNB, intra-frequency band with different center frequency via S1 (if enabled)
Inter-frequency Handover Variants As long as RSRP of the serving cell is above s-measure, a UE in RRC_Connected only monitors RSRP of the serving cell. Below s-measure, the UE performs measurements as configured by the eNB. To ensures mobility to neighbor cells in the same frequency , eNB configures intra-frequency RSRP measurement reporting for neighbour cells in the same frequency. When the level of the serving cell becomes worse and there is no neighbour cell in the same frequency that is received by the UE with proper quality, then inter-frequency measurements are configured in the UE in order to find a proper interfrequency neighbour cell. eNB supports inter-frequency handover in which the handover decision is based on RSRP and/or RSRQ (DL measurement). Triggers can be "Coverage HO" (A5) and "Better Cell HO" (A3) whereas A3 events are implemented for both, RSRP and RSRQ. Inter-frequency measurements may need Measurement Gaps, depending on the UE capability. The parameter measQuantInterFreq defines which quantity to use for Event A3 measurements towards this frequency set in QuantityConfigEUTRA. The quantities used to evaluate the triggering condition for the Event A3 is configurable (RSRP, RSRQ or both). The values RSRP and RSRQ correspond to Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ). This parameter refers to event A3. If set to "both", two A3 events will be configured when measuring this carrier, one per specific measurement quantity.
DN0978033 Issue: 02N
© 2016 Nokia
101
Radio resource management and telecom features
2.10.4.2.1
LTE RL20, Feature Descriptions
RSRP for A3 event (Better Cell HO) RSRP Definition: portion of energy in a received signal created by the inclusion of a reference pattern. Reference symbol received power can be used to estimate the ability of a receiver to obtain and decode information signals that a carrier signal transports. The UE measures its neighbor cell environment in a stepwise manner, such that unnecessary measurements are avoided. The measurement is based on the Reference Symbol Received Power (RSRP) and only if the RSRP value of serving cell falls below certain thresholds additional measurements are activated. In best case if RSRP of serving cell is higher than RSRP-Threshold-1, only the serving cell is measured, and if RSRP of serving cell falls below RSRP-Threshold-1 all intra frequency cells are measured as well. This measurement is easy to provide. s-measure is the 3GPP notation for RSRP-Threshold-1. Nevertheless, the measurement of other frequencies is difficult to provide and should be avoided if not necessary. Therefore, inter-frequency measurements are activated when RSRP of the serving cell falls below a still lower threshold than RSRP-Threshold-2. Table 39
Th1 and Th2 InterFreq are thresholds set by O&M
RSRP of serving cell
Measurement activities in UE
rsrp(s) > RSRP-Threshold-1
no measurement except serving cell
RSRP-Threshold-1
intra-frequency measurement
> rsrp(s) > RSRP-Threshold-2 rsrp(s)
View more...
Comments
