Fd Rl20 Desc

(1)

LTE Radio Access, Rel.

FDD-LTE 16A, Operating

Documentation, Issue 02

LTE RL20, Feature

Descriptions

DN0978033

Issue 02N

Approval Date 2016-06-29

(2)

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.

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.

(3)

Summary of changes... 23 1 RL20 Features - not supported by Flexi Zone Micro... 24 2 Radio resource management and telecom features... 25 2.1 LTE2: S1 Flex...25 2.1.1 Introduction to the feature... 25 2.1.2 Benefits... 25 2.1.3 Requirements... 25 2.1.3.1 Software requirements... 25 2.1.3.2 Hardware requirements...25 2.1.4 Functional description... 26 2.1.4.1 S1 interface... 26 2.1.4.2 MME selection...26 2.1.4.2.1 Load balancing... 27 2.1.5 Sales information... 27 2.1.6 User interface... 28 2.1.6.1 Parameters...28 2.1.6.2 Alarms... 28 2.1.6.3 Measurements and counters...28 2.1.7 Activating and configuring the feature...28 2.1.8 Abbreviations... 28 2.1.8.1 0 – Z... 28 2.2 LTE4: RAN Sharing... 29 2.2.1 Introduction to the feature... 29 2.2.2 Benefits... 29 2.2.3 Requirements... 29 2.2.3.1 Interdependencies between features... 29 2.2.3.2 Software requirements... 29 2.2.3.3 Hardware requirements...30 2.2.4 Requirements... 30 2.2.4.1 Interdependencies between features... 30 2.2.4.2 Software requirements... 30 2.2.4.3 Hardware requirements...30 2.2.5 Functional description... 30 2.2.5.1 Functional overview... 31 2.2.5.2 Feature activation...31 2.2.6 System impact...31 2.2.6.1 Interdependencies between features... 31 2.2.7 LTE4: RAN Sharing management data... 31 2.2.7.1 Alarms... 31 2.2.7.2 Measurements and counters...31

(4)

2.3.3.1 Software Requirements...32 2.3.3.2 Hardware Requirements... 33 2.3.4 Functional Description...33 2.3.5 System Impacts...38 2.3.6 Sales Information... 38 2.3.7 User Interface...38 2.3.7.1 Parameters...38 2.3.7.2 Measurements and Counters... 39 2.4 LTE9: Service Differentiation...42 2.4.1 Introduction to the feature... 42 2.4.2 Benefits... 42 2.4.3 Requirements... 42 2.4.3.1 Software requirements... 42 2.4.3.2 Hardware requirements...42 2.4.4 Functional description... 42 2.4.5 System impacts... 44 2.4.6 Sales information... 44 2.4.7 User interface... 44 2.4.7.1 Parameters...44 2.4.7.2 Alarms... 60 2.4.7.3 Measurements and counters...60 2.4.8 Activating the feature... 61 2.5 LTE10: EPS Bearers for Conversational Voice... 61 2.5.1 Introduction to the feature... 61 2.5.2 Benefits... 62 2.5.3 Requirements... 62 2.5.3.1 Software requirements... 62 2.5.3.2 Hardware requirements...62 2.5.4 Functional description... 63 2.5.4.1 Delay based scheduling in DL and in UL for bearers with QCI=1.... 63 2.5.4.2 Outer loop delay target control in DL... 64 2.5.4.3 HOL packet delay estimation in UL... 64 2.5.4.4 Consideration of GBR bearer in MAC multiplexing in DL...64 2.5.4.5 New scheduler type: exhaustive FD scheduler... 65 2.5.4.6 Packet aggregation in UL/DL... 65 2.5.4.7 Bearer establishment... 65 2.5.4.8 Radio admission control thresholds... 66 2.5.5 System impacts... 66

(5)

2.5.7.2 Measurements and counters...72 2.5.8 Activating the feature... 72 2.6 LTE11: Robust header compression... 73 2.6.1 Introduction To The Feature... 73 2.6.2 Benefits... 73 2.6.3 Requirements... 73 2.6.3.1 Software Requirements...73 2.6.3.2 Hardware Requirements... 74 2.6.4 Functional Description...74 2.6.4.1 Short Description of ROHC... 74 2.6.4.2 Bearer Establishment... 75 2.6.4.3 PDCP Adaptation for ROHC... 78 2.6.5 System Impacts...79 2.6.6 Sales Information... 79 2.6.7 User Interface...79 2.6.7.1 Parameters...79 2.6.8 Activating the Feature... 79 2.7 LTE13: Rate Capping (UL/DL)... 80 2.7.1 Introduction to the feature... 80 2.7.2 Benefits... 80 2.7.3 Requirements... 80 2.7.3.1 Software requirements... 80 2.7.3.2 Hardware requirements...80 2.7.4 Functional description... 80 2.7.5 System impacts... 82 2.7.6 Sales information... 82 2.7.7 User interface... 82 2.7.7.1 Parameters...82 2.7.7.2 Alarms... 83 2.7.7.3 Measurements and counters...83 2.7.8 Activating the feature... 83 2.8 LTE22: Emergency Call Handling... 83 2.8.1 Introduction to the Feature... 83 2.8.2 Benefits... 84 2.8.3 Requirements... 84 2.8.3.1 Software Requirements...84 2.8.3.2 Hardware Requirements... 84 2.8.4 Functional Description...84 2.8.4.1 Functional Overview/Details...84 2.8.4.2 Emergency Call Handling...85 2.8.4.3 Emergency Call Support... 85 2.8.4.3.1 Emergency Call trigger...85 2.8.4.3.2 Initiation of CS Fallback with Redirect due to Emergency Call.... 86

(6)

2.8.4.5 Radio Network Layer (RNL) support for Emergency Call via Redirection... 88 2.8.5 System Impacts...88 2.8.5.1 Dependencies Between Features... 88 2.8.5.2 Impacts on Interfaces... 88 2.8.5.2.1 External Interfaces... 88 2.8.5.3 Impacts on Network and Network Element Management tools... 88 2.8.5.4 Impacts on System Performance and Capacity... 88 2.8.5.4.1 System Performance...88 2.8.5.4.2 System Capacity... 89 2.8.6 Sales Information... 89 2.8.7 User Interface...89 2.8.7.1 Parameters...89 2.8.7.2 Measurements and Counters... 90 2.8.8 Activating the Feature... 90 2.9 LTE54: Intra-LTE handover via S1... 91 2.9.1 Introduction to the Feature... 91 2.9.2 Benefits... 91 2.9.3 Requirements... 91 2.9.3.1 Software Requirements...91 2.9.3.2 Hardware Requirements... 91 2.9.4 LTE54: Intra-LTE Handover via S1...92 2.9.4.1 Functional Overview/Details...92 2.9.4.2 Handover trigger ... 92 2.9.4.3 Handover Target and Mode Selection...93 2.9.4.3.1 Handover Mode selection for S1 based handover... 93 2.9.4.4 Handover over S1 interface... 93 2.9.4.4.1 Handover decision... 94 2.9.4.4.2 Handover preparation... 94 2.9.4.4.3 Handover execution ... 94 2.9.4.4.4 Handover completion... 94 2.9.4.5 Data forwarding ... 94 2.9.4.5.1 Support of indirect data forwarding... 94 2.9.4.5.2 Determination of which bearers are subject to data forwarding at source eNB on HO via S1... 95 2.9.4.5.3 Resource Allocation at Target eNB... 95 2.9.4.6 Performance Counters... 95 2.9.5 System Impact... 95

(7)

2.9.5.3 Impact on Network and Network Element Management tools... 96 2.9.5.4 Impact on System Performance and Capacity... 96 2.9.5.4.1 System Performance...96 2.9.5.4.2 System Capacity... 96 2.9.6 Sales Information... 97 2.9.7 User Interface...97 2.9.7.1 Parameters...97 2.9.7.2 Measurements and Counters... 98 2.10 LTE55: Inter-frequency handover...100 2.10.1 Introduction to the Feature... 100 2.10.2 Benefits... 100 2.10.3 Requirements... 100 2.10.3.1 Software Requirements...100 2.10.3.2 Hardware Requirements... 101 2.10.4 Functional Description...101 2.10.4.1 Functional Overview/Details...101 2.10.4.2 Inter-frequency Handover Variants...101 2.10.4.2.1 RSRP for A3 event (Better Cell HO)... 102 2.10.4.2.2 RSRQ for A3 event (Better Cell HO)... 103 2.10.4.2.3 RSRP for A5 event (Coverage HO)... 103 2.10.4.2.4 Th2a for deactivation of A3 and A5 events... 103 2.10.4.3 Handover trigger... 103 2.10.4.4 Performance counters... 104 2.10.5 System Impact... 104 2.10.5.1 Dependencies Between Features... 104 2.10.5.2 Impact on Interfaces...104 2.10.5.3 Impact on Network and Network Element Management tools... 104 2.10.5.4 Impact on System Performance and Capacity... 104 2.10.6 Sales Information... 105 2.10.7 User Interface...105 2.10.7.1 Parameters...105 2.10.7.2 Measurements and Counters... 110 2.10.8 Activating the Feature...110 2.11 LTE703: DL adaptive closed loop MIMO for two antennas ...111 2.11.1 Introduction to the feature...111 2.11.2 Benefits...111 2.11.3 Requirements... 111 2.11.3.1 Software Requirements... 111 2.11.3.2 Hardware Requirements...111 2.11.4 Functional description...112 2.11.5 System impacts... 112 2.11.5.1 Dependencies between features... 112 2.11.6 Sales information...113

(8)

2.12.3 Requirements... 115 2.12.3.1 Software Requirements... 115 2.12.3.2 Hardware Requirements...116 2.12.4 Functional description...116 2.12.4.1 Functional overview...116 2.12.4.2 Selection of target RAT...117 2.12.5 System impacts... 118 2.12.5.1 Impacts on system performance and capacity... 118 2.12.6 Sales information...118 2.12.7 User interface... 118 2.12.7.1 Parameters... 118 2.12.7.2 Alarms... 119 2.12.7.3 Measurements and counters... 119 2.12.8 Activating the feature... 120 2.13 LTE819: DL Inter-cell Interference Generation...120 2.13.1 Introduction To The Feature... 120 2.13.2 Benefits... 120 2.13.3 Requirements... 120 2.13.3.1 Software Requirements...121 2.13.3.2 Hardware Requirements... 121 2.13.4 Functional Description...121 2.13.4.1 Feature Scope...121 2.13.4.2 User Scenarios...121 2.13.5 System Impacts...122 2.13.5.1 Dependencies Between Features... 122 2.13.5.2 Impacts on Network and Network Element Management tools. 122 2.13.5.3 Impacts on System Performance and Capacity... 122 2.13.5.3.1 System Performance...122 2.13.5.3.2 System Capacity... 122 2.13.6 Sales Information... 122 2.13.7 User Interface...122 2.13.7.1 Parameters...122 2.13.7.2 Alarms... 123 2.13.7.3 Measurements and Counters... 123 2.13.8 Activating the Feature... 123 2.14 LTE870: Idle Mode Mobility from LTE to CDMA/eHRPD...123 2.14.1 Introduction to the Feature... 123 2.14.2 Benefits... 124 2.14.2.1 End User Benefits... 124

(9)

2.14.3.2 Hardware Requirements... 124 2.14.4 Functional Description...124 2.14.5 Sales Information... 125 2.14.6 User Interface...125 2.14.6.1 Managed Objects... 125 2.14.6.2 Parameters...125 2.14.6.3 Alarms... 126 2.14.6.4 Measurements and counters...126 2.14.7 System Impacts...126 2.14.7.1 Impacts on Telecom control plane...126 2.14.8 Activating the Feature... 126 2.15 LTE914: Graceful cell shutdown...127 2.15.1 Description of LTE914: Graceful Cell Shutdown... 127 2.15.1.1 Benefits... 127 2.15.1.2 Requirements... 127 2.15.1.3 Functional description... 127 2.15.1.4 System impact...130 2.15.1.5 LTE914: Graceful cell shutdown management data... 130 2.15.1.6 Sales information... 131 2.15.2 Activating LTE914: Graceful Cell Shutdown...131 2.15.3 Deactivating LTE914: Graceful Cell Shutdown... 132 3 Transport and Transmission Features...133 3.1 LTE140: Ethernet OAM... 133 3.1.1 Introduction to the feature... 133 3.1.2 Benefits... 133 3.1.2.1 End user benefits... 133 3.1.2.2 Operator benefits... 133 3.1.3 Requirements... 133 3.1.3.1 Software requirements... 133 3.1.3.2 Hardware requirements...134 3.1.4 Functional description... 134 3.1.4.1 Link Layer OAM... 134 3.1.4.2 Service OAM... 135 3.1.4.2.1 Ethernet Continuity Check and Ethernet Remote Defect Indication ... 137 3.1.4.2.2 Ethernet Alarm Indication Signal... 137 3.1.4.2.3 Ethernet Loopback... 138 3.1.4.2.4 Ethernet Link Trace... 139 3.1.5 Sales information... 139 3.1.6 User interface... 139 3.1.6.1 Parameters...139 3.1.6.2 Alarms... 143

(10)

3.2.3 Requirements... 146 3.2.3.1 Software requirements... 146 3.2.3.2 Hardware requirements...146 3.2.4 Functional description... 146 3.2.4.1 FPR management uses FPR Payload Channel...147 3.2.4.2 FPR management uses separate Radio Channel...148 3.2.5 Sales information... 148 3.2.6 User interface... 148 3.2.6.1 Parameters...149 3.2.6.2 Alarms... 149 3.2.6.3 Measurements and counters...149 3.2.7 Activating and Configuring the Feature...149 3.2.8 Abbreviations... 149 3.2.8.1 0 – Z... 149 3.3 LTE564: IPsec on FTIB... 150 3.3.1 Introduction to the feature... 150 3.3.2 Benefits... 150 3.3.3 Requirements... 150 3.3.3.1 Interdependencies between features... 150 3.3.3.2 Software requirements... 150 3.3.3.3 Hardware requirements...150 3.3.4 Functional description... 150 3.3.5 Sales information... 151 3.3.6 User interface... 151 3.3.6.1 Parameters...151 3.3.6.2 Alarms... 151 3.3.6.3 Measurements and counters...151 3.3.7 Abbreviations... 151 3.3.7.1 0 – Z... 151 3.4 LTE592: Link Supervision with BFD... 151 3.4.1 Introduction to the feature... 151 3.4.2 Benefits... 151 3.4.3 Requirements... 151 3.4.3.1 Software requirements... 152 3.4.3.2 Hardware requirements...152 3.4.4 Functional description... 152 3.4.5 Sales information... 153 3.4.6 User interface... 153 3.4.6.1 Parameters...153

(11)

3.4.8 Abbreviations... 158 3.4.8.1 0 – Z... 158 3.5 LTE649: QoS Aware Ethernet Switching...159 3.5.1 Introduction to the feature... 159 3.5.2 Benefits... 159 3.5.3 Requirements... 159 3.5.3.1 Interdependencies between features... 159 3.5.3.2 Software requirements... 160 3.5.3.3 Hardware requirements...160 3.5.4 Functional description... 161 3.5.4.1 VLAN aware switching... 162 3.5.4.2 VLAN unaware switching... 163 3.5.4.3 Scheduling and shaping for Ethernet QoS switching... 163 3.5.5 Sales information... 166 3.5.6 User interface... 166 3.5.6.1 Parameters...166 3.5.6.2 Alarms... 175 3.5.6.3 Measurements and counters...175 3.5.7 Activating and Configuring the Feature...176 3.5.8 Abbreviations... 176 3.5.8.1 0 – Z... 176 3.6 LTE775: SCTP Multi-homing (MME)... 177 3.6.1 Introduction to the feature... 177 3.6.2 Benefits... 177 3.6.3 Requirements... 178 3.6.3.1 Software requirements... 178 3.6.3.2 Hardware requirements...178 3.6.4 Functional description... 178 3.6.5 Sales information... 179 3.6.6 User interface... 179 3.6.6.1 Parameters...179 3.6.6.2 Alarms... 180 3.6.6.3 Measurements and counters...180 3.6.7 Abbreviations... 180 3.6.7.1 0 – Z... 180 4 Operability features... 181 4.1 LTE163: Subscriber and Equipment Trace... 181 4.1.1 Benefits... 181 4.1.2 Requirements... 181 4.1.3 Functional description... 181 4.1.4 System impact...186 4.1.5 Sales information... 186

(12)

4.2.4 Functional description... 188 4.2.4.1 LTE upgrade use cases...190 4.2.5 System impacts... 196 4.2.5.1 Impacts on interfaces... 196 4.2.5.2 Impact on network elements... 197 4.2.6 Sales information... 197 4.2.7 User interface... 197 4.2.7.1 Parameters...197 4.2.7.2 Alarms... 197 4.2.7.3 Measurements and counters...197 4.2.8 System responses to failures... 197 4.2.9 Activating and configuring the feature...198 4.3 LTE433: Cell Trace...199 4.3.1 Benefits... 199 4.3.2 Requirements... 199 4.3.3 Functional description... 199 4.3.4 System impact...204 4.3.5 Sales information... 204 4.3.6 User interface... 204 4.4 LTE475: Automatic iOMS Resiliency...206 4.4.1 LTE475: Automatic iOMS Resiliency - introduction...206 4.4.2 Benefits... 207 4.4.3 Functional Description...207 4.4.4 System Impacts...209 4.4.4.1 Interdependencies between Features...209 4.4.5 Managed Objects... 209 4.4.5.1 Parameters...209 4.5 LTE521: Security on Ethernet ports on FCM/FSM2... 210 4.5.1 Benefits... 210 4.5.2 Requirements... 211 4.5.3 Functional description...211 4.5.4 System impact...212 4.5.5 LTE521: Security for Ethernet ports on FCM/FSM2 management data... 213 4.5.6 Sales information... 213 4.6 LTE492: ANR... 213 4.6.1 LTE492: ANR... 213 4.6.1.1 Benefits... 214 4.6.1.2 Requirements... 214

(13)

4.6.1.3.1 Prerequisites... 215 4.6.1.3.2 Functional overview/details... 215 4.6.1.3.2.1 X2 link management... 217 4.6.1.3.2.2 NetAct Optimizer: Neighbor evaluation procedure...219 4.6.1.3.2.3 NetAct Configurator: automated neighbor site IP connectivity configuration completion... 220 4.6.1.3.2.4 Use cases... 221 4.6.1.4 System Impacts...221 4.6.1.4.1 Interdependencies between Features...221 4.6.1.5 Sales Information... 223 4.6.1.6 User Interface...223 4.6.1.6.1 Parameters...223 4.6.1.6.2 Alarms... 225 4.6.1.6.3 Measurements and Counters... 225 4.6.1.7 Activating and Configuring the Feature...226 4.7 LTE550: Radio Parameter Online Changeable... 226 4.7.1 Benefits... 226 4.7.2 Requirements... 226 4.7.3 System impact...226 4.7.4 LTE550: Radio Parameter Online Changeable management data.. 227 4.7.5 Sales information... 227 4.8 LTE559: SW Monitoring Module for LTE... 228 4.8.1 Introduction to the feature... 228 4.8.2 Benefits... 228 4.8.2.1 End user benefits... 228 4.8.2.2 Operator benefits... 228 4.8.3 Requirements... 228 4.8.3.1 Software requirements... 228 4.8.3.2 Hardware requirements...229 4.8.4 Functional description... 229 4.8.4.1 Functional overview/details... 229 4.8.5 System impacts... 230 4.8.5.1 Interdependencies between features... 230 4.8.5.2 Impacts on interfaces... 230 4.8.5.3 Impacts on network and network element management tools... 230 4.8.5.4 Impacts on system performance and capacity... 230 4.8.6 Sales information... 230 4.8.7 User interface... 230 4.8.7.1 Parameters...230 4.8.8 Activating and configuring the feature...230 4.9 LTE667: LTE User Event Log Management...230 4.9.1 Introduction to the feature... 230

(14)

4.10.1 Introduction to the Feature... 232 4.10.2 Benefits... 232 4.10.3 Requirements... 232 4.10.3.1 Software Requirements...232 4.10.4 Functional Description...232 4.10.5 System Impacts...232 4.10.5.1 Interdependencies between Features...233 4.10.6 Sales Information... 233 4.11 LTE830: LTE Automatic Lock... 233 4.11.1 Introduction to the Feature... 233 4.11.2 Benefits... 233 4.11.3 Requirements... 233 4.11.3.1 Software Requirements...233 4.11.4 Functional Description...233 4.11.5 Parameters...235 5 Performance Monitoring Features in RL20... 236 5.1 LTE805: PM Counter Capacity I...236 5.1.1 Benefits... 236 5.1.2 Requirements... 236 5.1.3 Functional description... 236 5.1.4 System impact...237 5.1.5 Sales information... 237 5.1.6 User interface... 237 6 Flexi Multiradio BTS LTE Site Solution features...240 6.1 LTE87: Flexi 3-sector RF Module 850...240 6.1.1 Introduction to the feature... 240 6.1.2 Benefits... 240 6.1.3 Requirements... 240 6.1.3.1 Software requirements... 240 6.1.4 Functional description... 241 6.1.5 Sales information... 241 6.1.6 User interface... 241 6.1.6.1 Parameters...241 6.1.7 Activating the feature ... 242 6.2 LTE101: Flexi 3-sector RF Module 1800...242 6.2.1 Introduction to the feature... 242 6.2.2 Benefits... 242

(15)

6.2.5 Sales information... 243 6.2.6 Activating the feature ... 244 6.3 LTE103: Flexi RRH 2TX 730... 244 6.3.1 Introduction to the feature... 244 6.3.2 Benefits... 244 6.3.3 Requirements... 244 6.3.3.1 Software requirements... 244 6.3.4 Functional description... 244 6.3.5 Sales information... 245 6.3.6 User interface... 245 6.3.6.1 Parameters...245 6.3.7 Activating the feature ... 245 6.4 LTE104: Flexi RRH 2TX 1800... 245 6.4.1 Introduction to the feature... 245 6.4.2 Benefits... 246 6.4.3 Requirements... 246 6.4.3.1 Software requirements... 246 6.4.4 Functional description... 246 6.4.5 Sales information... 247 6.4.6 Activating the feature ... 247 6.5 LTE113: Cell Bandwidth - 15 MHz...247 6.5.1 Introduction to the feature... 247 6.5.2 Benefits... 247 6.5.3 Requirements... 247 6.5.3.1 Software requirements... 247 6.5.3.2 Hardware requirements...248 6.5.4 Functional description... 248 6.5.5 Sales information... 248 6.5.6 User interface... 248 6.5.7 Activating the feature... 249 6.6 LTE447: SW support for RF sharing GSM-LTE ...249 6.6.1 Introduction to the feature... 249 6.6.2 Benefits... 249 6.6.3 Requirements... 249 6.6.3.1 Software requirements... 249 6.6.3.2 Hardware requirements...250 6.6.4 Functional description... 250 6.6.5 Sales information... 251 6.6.6 Activating the feature... 251 6.7 LTE1102: FFCC TRS External Filter for FXCA... 252 6.7.1 Benefits... 252 6.7.2 Requirements... 252 6.7.3 Functional description... 252

(16)

(17)

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

(18)

(19)

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

(20)

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

(21)

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

(22)

(23)

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: • LTE2: S1 Flex

(24)

The following features are not supported by Flexi Zone Micro: Table 1 RL20 Features - not supported by Flexi Zone Micro Features 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

(25)

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

2.1.3.2 Hardware requirements

This feature requires Flexi System modules which support LTE.

(26)

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

(27)

Figure 1 MME selection procedure RRCConnectionSetupComplete DeriveselectedPLMNidentity, S-TMSIandregisteredMME MMEselected SearchforselectedPLMNidentityinsetof servedPLMNidentitiesofallactiveMMEs MMEselected

MMEselected MMEselected MMEselected ReleaseRRCConnection

PerformLoadbalancing SearchforMMECodeofS-TMSI insetofMMECsofLTERAT SearchforregisteredMMEinsetof servedGUMMEIsofallactiveMMEs S-TMSIpresent registeredMMEnotinmessage registeredMMEinRRCmessage MMEnotfound MMEfoundinset SeveralMMEfound SelectedPLMNnot servedbyMME SelectedPLMNservedbyMME S-TMSInotpresent MMEnotfound MMEfoundinset MMEfoundinset

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

(28)

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

(29)

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

System release RL40

Flexi Multiradio BTS LBTS2.0 Flexi Multiradio 10 BTS LBTS4.0

(30)

SAE GW – UE 3GPP release 8 NetAct –

2.2.3.3 Hardware requirements

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.

System release RL40 Flexi Multiradio BTS LBTS2.0 Flexi Multiradio 10 BTS LBTS4.0 MME – SAE GW – UE 3GPP release 8 NetAct –

2.2.4.3 Hardware requirements

2.2.5 Functional description

(31)

2.2.5.1 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

(32)

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

System release RL20 eNodeB LBTS2.0 MME NS20 SAE GW NG20 UE 3GPP release 8 NetAct –

(33)

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

(34)

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

(35)

Figure 3 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: • 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.

(36)

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 S1AP:E-RABRELEASECOMMAND S1AP:RABRELEASERESPONSE RRC:RRCConnectionReconfigurationComplete RRRC:RCConnectionReconfiguration DRBRelease TriggeringofEPSBearerdeactivation RRC: ULInformationTransfer

S1AP: UL NAS TRANSPORT

Postprocessing

(37)

• 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 description 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: – 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.

(38)

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 RLC-AM DRBs.

0...1000 ms, step 1 ms

10 ms

End-Tag maximum UM tagMaxUM LNBTS The maximum bound for tag timer calculation valid for RLC-UM DRBs.

0...1000 ms, step 1 ms

10 ms

Activate Multiple Bearers actMultBearers LNBTS This parameter activates the support of multiple EPS Bearers. true UL Scheduler FD Type ulsFdPrbAssignAl g LNCEL 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 RoundRobinF D (0), ExhaustiveFD (1) ExhaustiveF D (1)

(39)

Table 9 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 Counter long name (short name) Description M8000C17 E-RAB setup completions (E_RAB_SETUP_SUCC) The number of successful E-RAB Setup Completions M8000C18 E-RAB setup failures due to radio network layer problems (E_RAB_SETUP_FAIL_RNL) The number of successful E-RAB Setup Failures due to radio network layer problems M8000C19 E-RAB setup failures due to transport layer problems (E_RAB_SETUP_FAIL_TRAN SPORT) The number of successful E-RAB Setup Failures due to transport layer problems M8000C20 E-RAB setup failures due to resource problems (E_RAB_SETUP_FAIL_RES OURCE) The number of successful E-RAB Setup Failures due to resource problems M8000C21 E-RAB setup failures due to other reasons (E_RAB_SETUP_FAIL_OTHE R) The number of successful E-RAB Setup Failures due to other reasons 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.

(40)

name) 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 E-RAB 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 E-RAB 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 E-RAB 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 E-RAB 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 E-RAB to be Released List IE is counted.

(41)

Table 10 Counters for LTE7: Support of multiple EPS bearer (Cont.)

PI ID 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 E-UTRAN generated reason or RNL Inter-RAT Redirection )

(42)

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

System release RL20 eNodeB LBTS2.0 MME NS20 SAE GW NG20 UE 3GPP release 8 NetAct –

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

(43)

• 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

(44)

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

(45)

Table 12 Parameters for the LTE9: Service Differentiation

Name Short name Object Description Range / Step Default value Activate NonGBR Service Differentiation actNonGbrService Diff LNBTS This parameter activates the Service Differentiation for non-GBR Bearers. true Prioritized Bit Rate NonGBR pbrNonGbr LNBTS Prioritized Bit Rate for non-GBR bearersThis prioritized bit rate is used by UE for the UL scheduling algorithm according [36.321]. 0kbps (0), 8kbps (1), 16kbps (2), 32kbps (3), 64kbps (4), 128kpbs (5), 256kbps (6) 16kbps (2) Table 13 Parameters for AM RLC Poll Byte structure

Name 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)

(46)

value

1250kB (10), 1500kB (11), 2000kB (12), 3000kB (13), Infinity (14)