Nokia LTE RL10 Features
Short Description
RL10 Feature...
Description
LTE Radio Access, Rel. RL60, Operating Documentation, Issue 03 Feature Descriptions RL10 DN0978045 Issue 02B Approval Date 2012-09-30
Feature Descriptions RL10
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR 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. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Solutions and Networks 2012. 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 Solutions and Networks 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 Solutions and Networks for any additional information.
2
DN0978045
Issue: 02B
Feature Descriptions RL10
Table of Contents This document has 131 pages
Summary of Changes.................................................................. 15
1 1.1
Feature Descriptions RL10.......................................................... 16 Radio resource management and telecom features from previous releases for RL20.........................................................................16 LTE28: Closed loop UL power control..........................................16 Introduction to the feature............................................................ 16 Benefits........................................................................................ 16 End user benefits......................................................................... 16 Operator benefits......................................................................... 16 Requirements...............................................................................17 Software requirements................................................................. 17 Hardware requirements................................................................17 Functional description.................................................................. 17 Functional details......................................................................... 17 Messages and information elements........................................... 19 System impacts............................................................................ 20 Interdependencies between features........................................... 20 Impacts on interfaces................................................................... 20 Impacts on performance and capacity......................................... 20 User interface...............................................................................20 Parameters...................................................................................20 Measurements and counters........................................................23 Activating The Feature................................................................. 24 Abbreviations............................................................................... 24 0 – Z............................................................................................. 24 LTE30: CQI adaption (DL)............................................................24 Introduction to the feature............................................................ 24 Benefits........................................................................................ 25 Requirements...............................................................................25 Software requirements................................................................. 25 Hardware requirements................................................................25 Functional description.................................................................. 25 Functional details......................................................................... 25 System impacts............................................................................ 26 Interdependencies between features........................................... 26 User interface...............................................................................26 Parameters...................................................................................26 Activating The Feature................................................................. 27 LTE37: Ciphering and LTE38: Integrity protection........................27 Introduction to the feature............................................................ 27 Benefits........................................................................................ 28
1.1.1 1.1.1.1 1.1.1.2 1.1.1.2.1 1.1.1.2.2 1.1.1.3 1.1.1.3.1 1.1.1.3.2 1.1.1.4 1.1.1.4.1 1.1.1.4.1.1 1.1.1.5 1.1.1.5.1 1.1.1.5.2 1.1.1.5.3 1.1.1.6 1.1.1.6.1 1.1.1.6.2 1.1.1.7 1.1.1.8 1.1.1.8.1 1.1.2 1.1.2.1 1.1.2.2 1.1.2.3 1.1.2.3.1 1.1.2.3.2 1.1.2.4 1.1.2.4.1 1.1.2.5 1.1.2.5.1 1.1.2.6 1.1.2.6.1 1.1.2.7 1.1.3 1.1.3.1 1.1.3.2
Issue: 02B
DN0978045
3
Feature Descriptions RL10
1.1.3.3 1.1.3.3.1 1.1.3.3.2 1.1.3.4 1.1.3.4.1 1.1.3.4.2 1.1.3.4.3 1.1.3.5 1.1.3.5.1 1.1.3.5.2 1.1.3.5.3 1.1.3.6 1.1.3.6.1 1.1.3.7 1.1.4 1.1.4.1 1.1.4.2 1.1.4.3 1.1.4.3.1 1.1.4.3.2 1.1.4.4 1.1.4.4.1 1.1.4.5 1.1.4.5.1 1.1.4.6 1.1.4.7 1.1.4.7.1 1.1.4.7.2 1.1.4.7.3 1.1.4.8 1.1.4.9 1.1.4.9.1 1.1.5 1.1.5.1 1.1.5.2 1.1.5.2.1 1.1.5.2.2 1.1.5.3 1.1.5.3.1 1.1.5.3.2 1.1.5.4 1.1.5.4.1 1.1.5.4.2 1.1.5.4.2.1
4
Requirements...............................................................................28 Software requirements................................................................. 28 Hardware requirements................................................................28 Functional description.................................................................. 29 Functional overview..................................................................... 29 Security keys................................................................................30 Messages and information elements........................................... 33 System impacts............................................................................ 35 Interdependencies between features........................................... 35 Impacts on network elements...................................................... 35 Impacts on system performance and capacity.............................35 User interface...............................................................................35 Parameters...................................................................................35 Activating The Feature................................................................. 36 LTE43: Support of 64 QAM in DL, LTE788: Support of 16 QAM (UL), LTE793: Support of 16 QAM (DL)....................................... 36 Introduction to the feature............................................................ 36 Benefits........................................................................................ 36 Requirements...............................................................................37 Software requirements................................................................. 37 Hardware requirements................................................................37 Functional description.................................................................. 38 Functional details......................................................................... 38 System impacts............................................................................ 38 Interdependencies between features........................................... 38 Sales information......................................................................... 38 User interface...............................................................................39 Managed objects..........................................................................39 Parameters...................................................................................39 Measurements and counters........................................................39 Activating The Features............................................................... 41 Abbreviations............................................................................... 41 0 – Z............................................................................................. 41 LTE69: Transmit diversity for two antennas and LTE70: Downlink adaptive open loop MIMO for two antennas................................ 43 Introduction to the feature............................................................ 43 Benefits........................................................................................ 43 End user benefits......................................................................... 43 Operator benefits......................................................................... 43 Requirements...............................................................................43 Software requirements................................................................. 44 Hardware requirements................................................................44 Functional description.................................................................. 44 Functional overview..................................................................... 44 Downlink adaptive open loop MIMO for two antennas.................44 Receive diversity.......................................................................... 46
DN0978045
Issue: 02B
Feature Descriptions RL10
1.1.5.4.2.2 1.1.5.4.2.3 1.1.5.4.3 1.1.5.4.4 1.1.5.5 1.1.5.5.1 1.1.5.5.2 1.1.5.5.3 1.1.5.5.4 1.1.5.6 1.1.5.7 1.1.5.7.1 1.1.5.7.2 1.1.5.7.3 1.1.5.7.4 1.1.5.8 1.2 1.2.1 1.2.1.1 1.2.1.2 1.2.1.3 1.2.1.3.1 1.2.1.3.2 1.2.1.4 1.2.1.4.1 1.2.1.5 1.2.1.6 1.2.1.6.1 1.2.1.6.2 1.2.1.6.3 1.2.1.7 1.2.2 1.2.2.1 1.2.2.2 1.2.2.3 1.2.2.3.1 1.2.2.3.2 1.2.2.4 1.2.2.4.1 1.2.2.4.1.1 1.2.2.4.2 1.2.2.4.3 1.2.2.5
Issue: 02B
Transmit diversity......................................................................... 46 Downlink open loop MIMO........................................................... 47 Transmit diversity for two antennas..............................................48 Open loop spatial multiplexing..................................................... 48 System impacts............................................................................ 49 Interdependencies between features........................................... 49 Impacts on interfaces................................................................... 49 Impacts on network and network element management tools..... 49 Impacts on system performance and capacity.............................49 Sales information......................................................................... 49 User interface...............................................................................49 Managed Objects......................................................................... 50 Parameters...................................................................................50 Alarms.......................................................................................... 51 Measurements and counters........................................................51 Activating the Feature.................................................................. 51 Transport and transmission features from previous releases for RL20.............................................................................................51 LTE713: Synchronous Ethernet................................................... 51 Introduction to the Feature........................................................... 51 Benefits........................................................................................ 51 Requirements...............................................................................51 Software Requirements................................................................51 Hardware Requirements.............................................................. 52 Functional Description..................................................................52 Synchronization Status Messages (SSM)....................................52 Sales Information......................................................................... 53 User Interface...............................................................................53 Parameters...................................................................................53 Alarms.......................................................................................... 54 Measurements and Counters.......................................................54 Activating and Configuring the Feature........................................54 LTE132: VLAN based traffic differentiation ................................. 54 Introduction to the Feature........................................................... 54 Benefits........................................................................................ 54 Requirements...............................................................................55 Software Requirements................................................................55 Hardware Requirements.............................................................. 55 Functional Description..................................................................55 Network Scenarios with VLAN based Traffic Differentiation.........56 X2 interface via IPsec Star Configuration.................................... 57 VLAN based Traffic Differentiation: Mapping of DL Packets in the Security Gateway......................................................................... 58 VLAN based Traffic Differentiation: Mapping of DL Packets in the VLAN Gateway.............................................................................59 Sales Information......................................................................... 59
DN0978045
5
Feature Descriptions RL10
1.2.2.6 1.2.2.6.1 1.2.2.6.2 1.2.2.6.3 1.2.2.7 1.2.3 1.2.3.1 1.2.3.1.1 1.2.3.1.2 1.2.3.1.3 1.2.3.1.3.1 1.2.3.1.3.2 1.2.3.1.3.3 1.2.3.1.4 1.2.3.1.5 1.2.3.1.6 1.3 1.3.1 1.3.1.1 1.3.1.2 1.3.1.3 1.3.1.3.1 1.3.1.3.2 1.3.1.4 1.3.1.4.1 1.3.1.5 1.3.1.5.1 1.3.1.5.2 1.3.1.5.3 1.3.1.5.4 1.3.1.6 1.3.1.7 1.3.1.8 1.3.2 1.3.2.1 1.3.2.2 1.3.2.3 1.3.2.3.1 1.3.2.3.2 1.3.2.3.3 1.3.2.4 1.3.2.4.1 1.3.2.4.1.1
6
User Interface...............................................................................59 Parameters...................................................................................59 Alarms.......................................................................................... 60 Measurements and Counters.......................................................60 Activating and Configuring the Feature........................................61 LTE134: Timing over packet.........................................................61 LTE134: Timing over Packet........................................................ 61 Benefits........................................................................................ 61 Requirements...............................................................................61 Functional Description..................................................................62 ToP Master................................................................................... 62 ToP Slave..................................................................................... 62 Support of IEEE 1588 Event Messages.......................................63 Management data........................................................................ 64 Sales information......................................................................... 65 Activating and configuring the feature..........................................65 Operability features from previous releases for RL20..................65 LTE150: LTE OAM Transport Layer Security (TLS) Support........65 Introduction to the feature............................................................ 65 Benefits........................................................................................ 65 Requirements...............................................................................66 Software requirements................................................................. 66 Hardware requirements................................................................66 Functional description for LTE OAM Transport Layer Security (TLS) Support...............................................................................66 Secure BTS Site Manager connection......................................... 69 System impact..............................................................................69 Interdependencies between features........................................... 69 Impact on interfaces.....................................................................69 Impact on network and network element management tools.......69 Impact on system performance and capacity...............................69 Sales information......................................................................... 69 Parameters for LTE150: LTE OAM Transport Layer Security (TLS) Support.........................................................................................70 Alarms for LTE150: LTE OAM Transport Layer Security (TLS) Support.........................................................................................70 LTE432: Cell Outage Detection....................................................71 Introduction.................................................................................. 71 Benefits........................................................................................ 71 Requirements...............................................................................71 Software Requirements for LTE432............................................. 71 Software Requirements for LTE502............................................. 71 Hardware Requirements.............................................................. 71 Functional Description..................................................................72 LTE432: Cell Outage Detection....................................................72 Failure Scenarios......................................................................... 72
DN0978045
Issue: 02B
Feature Descriptions RL10
1.3.2.4.1.2 1.3.2.4.2 1.3.2.5 1.3.2.5.1 1.3.2.6 1.3.2.7 1.3.2.7.1 1.3.2.7.1.1 1.3.2.7.2 1.3.2.7.2.1 1.3.2.7.3 1.3.2.8 1.3.2.9 1.3.2.10 1.3.2.10.1 1.3.3 1.3.3.1 1.3.3.2 1.3.3.2.1 1.3.3.3 1.3.3.3.1 1.3.3.3.2 1.3.3.4 1.3.3.4.1 1.3.3.4.1.1 1.3.3.4.1.2 1.3.3.4.1.3 1.3.3.5 1.3.3.5.1 1.3.3.6 1.3.3.7 1.3.3.8 1.3.3.8.1 1.3.4 1.3.4.1 1.3.4.1.1 1.3.4.1.2 1.3.4.2 1.3.4.2.1 1.3.4.2.2 1.3.4.3 1.3.4.3.1
Issue: 02B
Alarm Generation......................................................................... 73 LTE502: Cell outage triggered reset.............................................73 System Impacts............................................................................74 Interdependencies between Features..........................................74 Sales Information......................................................................... 74 User Interface...............................................................................74 Parameters for LTE432: Cell outage detection............................ 74 LTE502: Cell outage triggered reset.............................................75 Alarms for LTE432: Cell outage detection....................................75 Alarms for LTE502: Cell outage triggered reset........................... 76 Measurements and Counters for LTE432: Cell outage detection.... 76 System Responses to Failures.................................................... 77 Activating the Feature.................................................................. 77 Abbreviations............................................................................... 77 0 – Z............................................................................................. 77 LTE539: Central ANR...................................................................78 Introduction.................................................................................. 78 Benefits........................................................................................ 78 Operator Benefits......................................................................... 78 Requirements...............................................................................78 Software Requirements................................................................78 Hardware Requirements.............................................................. 79 LTE539: Central ANR...................................................................79 Functional Overview/Details.........................................................79 NetAct Optimizer.......................................................................... 79 NetAct Configurator......................................................................83 Integration in the Auto configuration Workflow.............................84 System Impacts............................................................................84 Interdependencies Between Features......................................... 84 Sales Information......................................................................... 85 Activating and Configuring the Feature........................................85 Abbreviations............................................................................... 85 0 – Z............................................................................................. 85 LTE665:Certificate Management and LTE685:Infrastructures for Certification Authority (CA) and Registration Authority (RA)........86 Introduction to the feature............................................................ 86 LTE665: LTE Certificate Management......................................... 86 LTE685: Infrastructures for Certification Authority (CA) and Registration Authority (RA) ......................................................... 86 Benefits........................................................................................ 86 LTE665: LTE Certificate Management......................................... 86 LTE685: Infrastructures for Certification Authority (CA) and Registration Authority (RA).......................................................... 86 Requirements...............................................................................86 Software requirements................................................................. 86
DN0978045
7
Feature Descriptions RL10
1.3.4.3.2 1.3.4.4 1.3.4.4.1 1.3.4.4.2 1.3.4.5 1.3.4.6 1.3.4.7 1.3.4.7.1 1.3.4.7.2 1.3.4.8 1.3.5 1.3.5.1 1.3.5.2 1.3.5.3 1.3.5.3.1 1.3.5.3.2 1.3.5.4 1.3.5.4.1 1.3.5.4.2 1.3.5.4.3 1.3.5.4.3.1 1.3.5.4.4 1.3.5.5 1.3.5.6 1.3.5.7 1.3.5.7.1 1.3.5.7.2 1.3.5.8 1.3.6 1.3.6.1 1.3.6.2 1.3.6.3 1.3.6.3.1 1.3.6.3.2 1.3.6.4 1.3.6.5 1.3.6.6 1.3.6.7 1.3.6.7.1 1.3.6.8 1.3.7 1.3.7.1 1.3.7.2
8
Hardware requirements................................................................87 Functional description for certificate management.......................87 LTE665: LTE Certificate Management......................................... 87 LTE685: Infrastructures for Certification Authority (CA) and Registration Authority (RA).......................................................... 91 System impacts............................................................................ 93 Sales information......................................................................... 93 User interface...............................................................................93 Parameters for LTE665: LTE Certificate Management.................93 Alarms for LTE665: LTE Certificate Management........................ 94 Activating and configuring the feature..........................................95 LTE666: LTE User Account Management.................................... 95 Introduction to the feature............................................................ 95 Benefits........................................................................................ 95 Requirements...............................................................................96 Software Requirements................................................................96 Hardware Requirements.............................................................. 96 Functional description for user security........................................96 Authentication and authorization..................................................96 Disabling user accounts in NetAct............................................... 97 User management........................................................................97 Mass updating of eNB local user accounts.................................. 97 Audit trail...................................................................................... 97 System impacts............................................................................ 98 Sales information......................................................................... 98 User interface...............................................................................99 Parameters for LTE666: LTE User Account Management........... 99 Alarms for LTE666: LTE User Account Management...................99 Activating and configuring the feature........................................100 LTE679: LTE Local User Account Management........................ 100 Introduction to the feature.......................................................... 100 Benefits...................................................................................... 100 Requirements.............................................................................100 Software requirements............................................................... 100 Hardware requirements..............................................................101 Functional description for LTE Local User Account Management... 101 System impacts..........................................................................101 Sales information....................................................................... 101 User interface.............................................................................101 Parameters for LTE679: LTE Local User Account Management...... 101 Activating the feature................................................................. 101 LTE689: LTE IPsec Support....................................................... 101 Introduction to the feature.......................................................... 101 Benefits...................................................................................... 102
DN0978045
Issue: 02B
Feature Descriptions RL10
1.3.7.3 1.3.7.3.1 1.3.7.3.2 1.3.7.4 1.3.7.4.1 1.3.7.5 1.3.7.6 1.3.7.7 1.3.7.7.1 1.3.7.7.2 1.3.7.7.3 1.3.7.8 1.3.8 1.3.8.1 1.3.8.2 1.3.8.3 1.3.8.3.1 1.3.8.3.2 1.3.8.4 1.3.8.4.1 1.3.8.4.2 1.3.8.4.3 1.3.8.5 1.3.8.6 1.3.8.7 1.3.8.7.1 1.3.8.7.2 1.3.8.8 1.3.9 1.3.9.1 1.3.9.2 1.3.9.3 1.3.9.3.1 1.3.9.3.2 1.3.9.4 1.3.9.5 1.3.9.6 1.3.9.7 1.3.9.7.1 1.3.9.8 1.3.10 1.3.10.1 1.3.10.2 1.3.10.3
Issue: 02B
Requirements.............................................................................102 Software requirements............................................................... 102 Hardware requirements..............................................................102 Functional description for IPsec Support................................... 103 Transport security.......................................................................104 System impacts..........................................................................104 Sales information....................................................................... 104 User interface.............................................................................105 Parameters for LTE689: LTE IPsec Support.............................. 105 Alarms for LTE689: LTE IPsec Support......................................108 Counters for LTE689: LTE IPsec Support.................................. 109 Activating and configuring the feature........................................109 LTE692: LTE Firewall Support....................................................110 Introduction to the feature...........................................................110 Benefits.......................................................................................110 Requirements............................................................................. 110 Software requirements............................................................... 110 Hardware requirements.............................................................. 110 Functional description for LTE Firewall Support......................... 110 Firewall functionality................................................................... 111 Firewall filter............................................................................... 113 Logging.......................................................................................113 System impacts.......................................................................... 114 Sales information........................................................................114 User interface............................................................................. 114 Parameters for LTE692: LTE Firewall Support........................... 114 Counters for LTE692: LTE Firewall Support............................... 114 Activating and configuring the feature........................................ 115 LTE746: IP based filtering for BTS Site Support Equipment...... 115 Introduction to the feature...........................................................115 Benefits.......................................................................................115 Requirements............................................................................. 115 Software requirements............................................................... 115 Hardware requirements.............................................................. 116 Functional description for IP based filtering for BTS Site Support Equipment.................................................................................. 116 System impacts.......................................................................... 116 Sales information........................................................................116 User interface............................................................................. 116 Parameters for LTE746: IP based filtering for BTS Site Support Equipment.................................................................................. 116 Activating the feature..................................................................118 LTE913: LTE NEBS compliant OMS.......................................... 118 Introduction to the Feature......................................................... 118 Benefits.......................................................................................118 Functional Description................................................................ 118
DN0978045
9
Feature Descriptions RL10
1.3.10.4 1.4 1.4.1 1.4.2 1.4.2.1 1.4.2.1.1 1.4.2.1.2 1.4.2.1.3 1.4.2.1.4 1.4.2.2 1.4.2.2.1 1.4.2.2.2 1.4.2.2.3 1.4.2.2.4 1.4.3 1.4.3.1 1.4.3.1.1 1.4.3.1.2 1.4.3.1.3 1.4.3.2 1.4.3.2.1 1.4.3.2.2 1.4.3.2.3 1.4.3.2.4 1.4.3.2.5 1.4.3.3 1.4.3.3.1 1.4.3.3.2 1.4.3.3.3 1.4.4 1.4.4.1 1.4.4.2 1.4.4.3 1.4.4.4 1.4.4.5 1.4.4.6 1.4.4.6.1 1.4.4.6.2 1.4.4.6.3 1.4.5 1.4.5.1 1.4.6 1.4.6.1 1.4.6.1.1 1.4.6.1.2
10
Requirements............................................................................. 119 Flexi Multiradio BTS LTE Site Solution features from previous releases for RL20....................................................................... 119 Introduction to the Flexi Multiradio BTS Site Solution features.. 119 Cell-related features...................................................................120 LTE cell bandwidth features: LTE112,LTE114, and LTE115....... 120 Introduction................................................................................ 120 Functional description................................................................ 120 Benefits...................................................................................... 120 Activating the feature................................................................. 120 LTE97: Cell radius max 77 km................................................... 120 Introduction................................................................................ 120 Benefits...................................................................................... 120 Functional description................................................................ 120 Activating the feature................................................................. 121 Antenna line features................................................................. 121 LTE71: 2-way RX diversity (MRC)..............................................121 Introduction................................................................................ 121 Benefits...................................................................................... 121 Functional description................................................................ 121 LTE160: Flexi Multiradio BTS 3GPP antenna tilt support.......... 121 Introduction................................................................................ 121 Benefits...................................................................................... 121 Functional description................................................................ 122 Management data...................................................................... 122 Activating the feature................................................................. 123 LTE94: Feederless site...............................................................123 Introduction................................................................................ 123 Benefits...................................................................................... 123 Functional description................................................................ 123 Flexi Multiradio BTS RF Modules...............................................124 Introduction................................................................................ 124 Benefits...................................................................................... 124 LTE85: Flexi 3-sector RF Module 2600 (FRHA).........................124 LTE99: Flexi 3-sector RF Module 1.7/2.1 (FRIE)....................... 124 LTE437: Flexi 3-sector RF Module 800EU.................................124 LTE96: MIMO 2TX configuration with 3-sector RF Module........ 125 Introduction................................................................................ 125 Benefits...................................................................................... 125 Functional description................................................................ 125 Flexi Multiradio BTS Remote Radio Heads................................125 Benefits...................................................................................... 125 Cabinets and other Flexi Multiradio BTS hardware....................125 LTE79: Flexi Indoor (FCIA) and Outdoor (FCOA) Cabinets....... 125 Introduction................................................................................ 125 Benefits...................................................................................... 125
DN0978045
Issue: 02B
Feature Descriptions RL10
1.4.6.1.3 1.4.6.2 1.4.6.2.1 1.4.6.2.2 1.4.6.2.3 1.4.6.3 1.4.6.3.1 1.4.6.3.2 1.4.6.3.3 1.4.7 1.4.7.1 1.4.7.2 1.4.7.3 1.4.8 1.4.8.1 1.4.8.1.1 1.4.8.1.2 1.4.8.1.3 1.4.8.2 1.4.8.2.1 1.4.8.2.2 1.4.8.2.3 1.4.8.3 1.4.8.3.1 1.4.8.3.2 1.4.8.3.3 1.4.8.4 1.4.8.4.1 1.4.8.4.2 1.4.8.4.3
Issue: 02B
Functional description................................................................ 126 LTE78: Flexi AC/DC with Battery Power Module (FPMA).......... 127 Introduction................................................................................ 127 Benefits...................................................................................... 127 Functional description................................................................ 127 LTE82: High-capacity Flexi System Module (FSME)................. 127 Introduction................................................................................ 127 Benefits...................................................................................... 128 Functional description................................................................ 128 LTE80: GPS synchronization..................................................... 128 Introduction................................................................................ 128 Benefits...................................................................................... 128 Functional description................................................................ 128 Power support features.............................................................. 129 LTE900: Flexi Multiradio BTS 40 W power support....................129 Introduction................................................................................ 129 Benefits...................................................................................... 129 Functional description................................................................ 129 LTE901: Flexi Multiradio BTS 8 W power support......................129 Introduction................................................................................ 129 Benefits...................................................................................... 129 Functional description................................................................ 130 LTE903: Flexi Multiradio BTS 60 W power support....................130 Introduction................................................................................ 130 Benefits...................................................................................... 130 Functional description................................................................ 130 LTE904: Flexi LTE BTS Branch Activation................................. 131 Introduction................................................................................ 131 Benefits...................................................................................... 131 Functional description................................................................ 131
DN0978045
11
Feature Descriptions RL10
List of Figures
12
Figure 1
Power control decision matrix.............................................................18
Figure 2
Principle of CQI adaptation.................................................................26
Figure 3
C-plane security..................................................................................29
Figure 4
U-plane security..................................................................................29
Figure 5
Security key hierarchy........................................................................ 31
Figure 6
Throughput for different modulation schemes.................................... 37
Figure 7
QAM modulation.................................................................................38
Figure 8
2x2 MIMO configuration..................................................................... 47
Figure 9
Multipoint-to-multipoint VLAN............................................................. 56
Figure 10
Point-to-Point VLAN........................................................................... 57
Figure 11
IPsec star configuration...................................................................... 58
Figure 12
LTE432 “Thresholder and Profiler” in NetAct......................................72
Figure 13
Transport protocol stack overview.................................................... 104
DN0978045
Issue: 02B
Feature Descriptions RL10
List of Tables
Issue: 02B
Table 1
Software requirements for different network elements....................... 17
Table 2
Parameters for closed loop UL power control.................................... 21
Table 3
Parameters common for open and closed loop UL power control......22
Table 4
New and modified counters................................................................ 23
Table 5
Software requirements for different network elements....................... 25
Table 6
Software requirements for different network elements....................... 28
Table 7
Security related messages and information elements........................33
Table 8
Parameters for ciphering and integrity protection...............................35
Table 9
Software requirements for different network elements....................... 37
Table 10
Parameters for LTE43: Support of 64QAM in DL............................... 39
Table 11
Counters for LTE43............................................................................ 39
Table 12
Multi antenna options in LTE.............................................................. 46
Table 13
Parameters for “LTE70: Downlink adaptive open loop MIMO for two antennas”............................................................................................50
Table 14
Software requirements for different network elements....................... 52
Table 15
Parameters related to the LTE713: Synchronous Ethernet feature....53
Table 16
Software requirements for different network elements....................... 55
Table 17
Supported numbers of VLANs............................................................55
Table 18
Sales Information................................................................................59
Table 19
Parameters related to the LTE132: VLAN based traffic differentiation... 59
Table 20
Counters for the LTE132: VLAN based traffic differentiation.............. 60
Table 21
Software requirements for different network elements....................... 62
Table 22
Parameters related to the LTE134: Timing over packet feature......... 64
Table 23
Sales information................................................................................65
Table 24
Software requirements for different network elements....................... 66
Table 25
Parameters for LTE150: LTE OAM Transport Layer Security (TLS) Support............................................................................................... 70
Table 26
Alarms for LTE150: LTE OAM Transport Layer Security (TLS) Support ............................................................................................................70
Table 27
Software requirements for different network elements....................... 71
Table 28
Interdependencies between features................................................. 74
Table 29
Parameters for the LTE432: Cell Outage Detection........................... 74
Table 30
Alarms for the LTE432: Cell outage detection.................................... 75
Table 31
Alarms for the LTE502: Cell outage triggered reset........................... 76
Table 32
Counters for the LTE432: Cell outage detection.................................76
Table 33
Error codes......................................................................................... 77
Table 34
Software requirements for different network elements....................... 78
Table 35
Interdependencies between features................................................. 84
Table 36
Software requirements for different network elements....................... 86
DN0978045
13
Feature Descriptions RL10
14
Table 37
Parameters for LTE665: LTE Certificate Management....................... 94
Table 38
Alarms for LTE665: LTE certificate management............................... 94
Table 39
Software requirements for different network elements....................... 96
Table 40
Parameters for LTE666: LTE User Account Management..................99
Table 41
Parameters for LTE666: LTE User Account Management - BTSSM.. 99
Table 42
Alarms for LTE666: LTE User Account Management......................... 99
Table 43
Software requirements for different network elements..................... 100
Table 44
Parameters for LTE679: LTE Local User Account Management...... 101
Table 45
Software requirements for different network elements..................... 102
Table 46
Hardware requirements for different network elements....................102
Table 47
Sales information..............................................................................104
Table 48
Parameters for LTE689: LTE IPsec Support.....................................105
Table 49
Alarms for LTE689: LTE IPsec Support............................................ 108
Table 50
Counters for LTE689: LTE IPsec Support.........................................109
Table 51
Software requirements for different network elements..................... 110
Table 52
Messages..........................................................................................111
Table 53
Parameters for LTE692: LTE Firewall Support................................. 114
Table 54
Counters for LTE692: LTE Firewall Support..................................... 115
Table 55
Software requirements for different network elements..................... 115
Table 56
Parameters for LTE746: IP based filtering for BTS Site Support Equipment.........................................................................................117
Table 57
Parameter for configuring MTU size................................................. 118
Table 58
The parameters related to LTE160: Flexi Multiradio BTS 3GPP antenna tilt support........................................................................... 122
DN0978045
Issue: 02B
Feature Descriptions RL10
Summary of Changes
Summary of Changes Changes between version 02B (2012-09-30, RL30) and 02C (2013-07-22, RL30) The following feature description has been updated: •
LTE665:Certificate Management
The following feature activation has been updated: •
Activating LTE665: Certificate Management
Changes between version 02A (2012-04-26, RL30) and 02B (2012-09-30, RL30) The following feature descriptions have been updated: •
LTE665:Certificate Management and LTE685:Infrastructures for Certification Authority (CA) and Registration Authority (RA)
Changes between version 02 (2011-09-26, RL20) and 02A (2012-04-10, RL30) The following feature descriptions have been updated: • • •
LTE97: Cell Radius Max 77 km LTE432: Cell Outage Detection LTE746: IP Based Filtering for BTS Site Support Equipment
Changes between version 01B (2011-03-24, RL20) and 02 (2011-09-26, RL30) The following feature descriptions have been updated: •
LTE665:Certificate Management and LTE685:Infrastructures for Certification Authority (CA) and Registration Authority (RA):: Functional description section has been updated.
Changes between version 01A (2010-12-17, RL20) and 01B (2011-03-24,RL20) The following feature descriptions have been updated: •
LTE870: Idle Mode Mobility From LTE To CDMA/eHRPD: Parameters section has been updated.
Changes between version 01A (2010-12-17, RL20) and 01 (2010-10-29, RL20) LTE665: Certificate Management and LTE685: Infrastructures for Certification Authority (CA) and Registration Authority (RA) • • •
Issue: 02B
Vendor Certificate revocation section has been added Identity management server solution section has been updated Factory trust anchor section has been updated.
DN0978045
15
Feature Descriptions RL10
Feature Descriptions RL10
1 Feature Descriptions RL10 1.1 Radio resource management and telecom features from previous releases for RL20 1.1.1 LTE28: Closed loop UL power control 1.1.1.1
Introduction to the feature Closed loop UL power control complements the basic open loop UL power control (see chapter “Power control” in the “Link control” functional area description; UL: uplink). It is based on eNodeB’s measurements of UL signal level and quality. Of the measurement data the eNodeB determines an UL power increase or decrease step and commands the UE (user equipment) to increase or decrease the current UL transmit power by this step. Open loop power control is based on pathloss estimations of the UE and mainly static system and O&M parameters; it compensates long-term variations of the radio conditions, but typically suffers from errors in pathloss estimations. The closed loop power control strongly improves the pathloss estimations and allows optimized UL power adaption. Hence, the UE is enabled to operate with optimum power levels under varying propagation and interference conditions. Actually, open loop UL power control and closed loop UL power control are combined and one formula is used to calculate the UE’s transmit power taking into account both open and closed loop power control components. Separate UL power adjustments are calculated for different PUCCH formats, SRSs (sounding reference symbols) and specific UL allocations on PUSCH. Closed loop UL power commands are sent on PDCCH. The operator enables/disables and configures closed loop power control by O&M setting. The general cell specific parameters are delivered via system information broadcasting and the UE specific parameters are delivered via RRC signalling. The Flexi Multiradio BTS supports slow closed loop uplink power control.
1.1.1.2 1.1.1.2.1
Benefits End user benefits The UE power consumption is reduced. The reduction of interference by operation with closed loop UL power control optimizes the transmission conditions within the cell in terms of speech quality and/or data rates.
1.1.1.2.2
Operator benefits Closed loop UL power control reduces intra-cell, inter-cell and inter-system interference. The results are improved cell edge behavior and a relaxation of requirements on intracell orthogonality.
16
DN0978045
Issue: 02B
Feature Descriptions RL10
1.1.1.3 1.1.1.3.1
Feature Descriptions RL10
Requirements Software requirements Table 1
1.1.1.3.2
Software requirements for different network elements
Network element
Required software release
System release
RL10
eNodeB
LBTS1.0
MME
–
SAE GW
–
UE
3GPP release 8
NetAct
–
Hardware requirements This feature does not require any additional hardware.
1.1.1.4 1.1.1.4.1
Functional description Functional details Closed loop UL power control is done as follows: 1. The eNodeB measures every TTI (transmission time interval) for every PRB (physical resource block) and for all UEs, whose signals are received, the signal level (RSSI, received signal strength indicator) and quality (SINR, signal-tointerference plus noise ratio) from PUCCH and/or PUSCH depending on the O&M configuration. 2. The eNodeB processes the measurement data by • • • •
transforming it into a transport format independent format, clipping the measurement data (a limitation of each value in a certain range between a O&M defined minimum and maximum threshold), weighting the measurement data, filtering the measurement data (averaging filters).
3. After that, the eNodeB makes a decision about PUCCH and/or PUSCH commands by using a decision matrix with a target window for signal quality and level configured by an operator. For example, if the signal quality and level is below the lower thresholds, a power increase is initiated. 4. The new UL power is calculated. 5. PUCCH/PUSCH/SRS power commands are then signalled to the UE via PDCCH. The command contains the power adjustments (e.g. +3 dB for PUSCH).
Issue: 02B
DN0978045
17
Feature Descriptions RL10
Feature Descriptions RL10
The UE uses the closed loop power correction values as additive term to the open loop component for the calculation of its total uplink transmit power. The described UL power control scheme is applied separately for the physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH) and sounding reference symbols (SRSs) with different parameter sets. The UL power control is performed independently for each particular UE in a cell.
Measurements The eNodeB measures: • • •
RSSI (received signal strength indicator) of received signals for every UE transmitting on PUCCH or PUSCH or transmitting SRS Interference for every received PUCCH/PUSCH/SRS physical resource block (PRB) Interference for every UE transmitting via PUCCH or PUSCH
The eNodeB then calculates the related SINR values for the cell and for each UE.
Power adjustment decision and determination of the power adjustment value Separate UL power control windows for the power adjustment decision are defined for the PUSCH, SRS and PUCCH components. The UL power control window is defined by upper and lower quality and level thresholds (in a two-dimensional quality-level space the thresholds define the fields of a decision matrix). Figure 1: Power control decision matrix schematically shows the UL power control decision matrix for PUSCH and for PUCCH. The required power adjustment step to be sent to the UE is given in the fields of the matrix and is called δPUSCH or δPUCCH. Figure 1
Power control decision matrix
good
+ 1 dB or + 3 dB
- 1 dB
- 1 dB
medium
+ 1 dB or + 3 dB
0 dB
- 1 dB
poor
SINR
+ 1 dB or + 3 dB
+ 1 dB or + 3 dB
+ 1 dB or + 3 dB
medium
high
high_qual_thresh
low_qual_thresh
low
low_lev_thresh
18
DN0978045
RSSI
high_lev_thresh
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
In the formula for the UE’s calculation of the UL transmission power, δPUSCH is an additive component. The UL transmission power for subframe i, PPUSCH(i), uses the power adaption value δPUSCH(i – 4) which was signalled via PDCCH 4 subframes before (according to 3GPP 36.213: δPUSCH(i – KPUSCH), and for FDD mode: KPUSCH = 4). δ is given as the current contribution to an accumulated power correction summand. In this case the summand is given by f(i) = f(i – 1) + δPUSCH/PUCCH(i – 4). Another possibility (described in 3GPP 36.213) would be to give δ as an absolute (standalone) power correction value. The eNodeB takes care that successive δ power up or power down commands do not exceed an upper and a lower absolute power limit. Since closed loop UL power control takes into account the SINR conditions, SINR is not considered in open loop UL power control.
Transmit power control commands The UL power adjustment value δPUSCH for PUSCH is carried within the transmit power control (TPC) command which is sent to the UE in combination with the uplink scheduling grant: Whenever a UE is scheduled, it gets a TPC command together with being informed which resources and transport format is assigned. The TPC command is included in the PDCCH with DCI format 0. Another possibility of conveying the TPC information – not implemented in the current solution – would be to use the TPC-PUSCH format, which is a special PDCCH payload and contains jointly coded UL TPC commands for a set of up to N users. In this case DCI format 3/3A would be used whose CRC parity bits are scrambled with TPC-PUSCH-RNTI. Correspondingly, the UL power adjustment value δPUCCH for PUCCH is carried within the transmit power control (TPC) command which is also sent to the UE in combination with the uplink scheduling grant. Possible values for δPUSCH/PUCCH in the accumulation case are -1 dB, 0 dB, 1 dB, 3 dB. The UE attempts to decode a PDCCH of DCI format 0 with the UE's C-RNTI or SPS CRNTI and a PDCCH of DCI format 3/3A with this UE's TPC-PUSCH-RNTI in every subframe except when in DRX mode. If DCI format 0 and DCI format 3/3A are both detected in the same subframe, then the UE uses the power value provided in DCI format 0. 1.1.1.4.1.1
Messages and information elements
Messages UL UE specific power control parameters are included in the RRC: CONNECTION RECONFIGURATION message. It contains information elements described below.
Information elements The IE “UplinkPowerControlCommon” and IE “UplinkPowerControlDedicated” are used to specify parameters for uplink power control in the system information and in the dedicated signalling, respectively; see 3GPP TS 36.331. For example, the IE “UplinkPowerControlDedicated” is included in the “physicalConfigDedicated” IE which is included in the “radioResourceConfigDedicated” IE. The last one is a part of the RRC: CONNECTION RECONFIGURATION message.
Issue: 02B
DN0978045
19
Feature Descriptions RL10
Feature Descriptions RL10
The “physicalConfigDedicated” IE also contains the “TPC-PDCCH-Config” IE which is used to specify the RNTIs and indexes for PUCCH and PUSCH power control. The power control function can either be setup or released with the IE.
1.1.1.5 1.1.1.5.1
System impacts Interdependencies between features “Closed loop UL power control” complements the feature “Open loop UL power control and DL power setting”, see chapter “Power control” in the “Link control” functional area description. “Closed loop UL power control” has effects on the packet scheduler (see the “Packet scheduler” functional area description): The combining of power control and resource allocation allows interference coordination to further enhance cell edge performance and allows higher overall spectral efficiency. For example, UEs with comparable pathloss in adjacent cells can be directed to transmit in the same time-frequency resource. On average, such a grouping of UEs with a similar channel quality in adjacent cells results in the best cell edge performance, because it avoids strong interference from UEs close to the eNodeB in adjacent cells. Vice versa, aligning UEs with different channel quality between cells results in a good channel quality for these UEs, hence the peak data rates and the average cell throughput can be increased.
1.1.1.5.2
Impacts on interfaces Regarding the radio interface, the communication between eNodeB and UE is done via RRC signalling. Cell specific UL power control parameters are included in the system information block type 1 (SIB1). General power control parameters are sent to the UE during the Initial Context Setup Request procedure. UL UE specific power control parameters are included in the RRC: CONNECTION RECONFIGURATION message (includes the “radioResourceConfigDedicated” IE which includes the “physicalConfigDedicated” IE; the last one includes the”uplinkPowerControlDedicated” IE).
1.1.1.5.3
Impacts on performance and capacity Since “Closed loop UL power control” is related to interference, the feature – combined with allocation of resources (by the packet scheduler) – improves the performance at cell edge and allows a higher overall spectral efficiency.
1.1.1.6 1.1.1.6.1
User interface Parameters The following table shows the parameters implemented for the feature. Parameters common for closed loop and open loop uplink power control are shown in the second table.
20
DN0978045
Issue: 02B
Feature Descriptions RL10
Table 2
Feature Descriptions RL10
Parameters for closed loop UL power control
Name
Object
Description
Range
Default value
Enable Closed Loop Uplink Power Control
LNCEL
This parameter allows to enable/disable closed loop uplink power control.
0 (false)
0
Including or excluding of RSSI and SINR measurements from PUCCH in the closed loop PC component.
0 (false)
Including or excluding of RSSI and SINR measurements from PUSCH in the closed loop PC component.
0 (false)
Lower threshold of the power control window for the RSSI (signal level) for PUCCH component.
-127...0 dBm
Lower threshold of the power control window for the RSSI (signal level) for PUSCH/SRS component.
-127...0 dBm
Lower threshold of the power control window for the SINR (signal quality) for PUCCH component.
-47...80 dB
Lower threshold of the power control window for the SINR (signal quality) for PUSCH/SRS component.
-47...80 dB
Upper threshold of the power control window for the RSSI (signal level) for PUCCH component.
-127...0 dBm
Upper threshold of the power control window for the RSSI (signal level) for PUSCH/SRS component.
-127...0 dBm
1 (true)
(ulpcEnable) Include PUCCH LNCEL Measurements In CL Power Control
1
1 (true)
(ulpcPucchEn) Include PUSCH LNCEL Measurements In CL Power Control
1
1 (true)
(ulpcPuschEn) Lower RSSI Threshold For PUCCH Power Command Decision
LNCEL
-103 dBM
step 1 dBm
(ulpcLowlevCch) Lower RSSI Threshold For PUSCH Power Command Decision
LNCEL
-103 dBM
step 1 dBm
(ulpcLowlevSch) Lower SINR Threshold For PUCCH Power Command Decision
LNCEL
1 dB
step 1 dB
(ulpcLowqualCch) Lower SINR Threshold For PUSCH Power Command Decision
LNCEL
8 dB
step 1 dB
(ulpcLowqualSch) Upper RSSI Threshold For PUCCH Power Command Decision
LNCEL
-98 dBM
step 1 dBm
(ulpcUplevCch) Upper RSSI Threshold For PUSCH Power Command Decision
LNCEL
-98 dBm
step 1 dBm
(ulpcUplevSch)
Issue: 02B
DN0978045
21
Feature Descriptions RL10
Table 2
Feature Descriptions RL10
Parameters for closed loop UL power control (Cont.)
Name
Object
Description
Range
Default value
Upper SINR Threshold For PUCCH Power Command Decision
LNCEL
Upper threshold of the power control window for the SINR (signal quality) for PUCCH component.
-47...80 dB
4 dB
Upper threshold of the power control window for the SINR (signal quality) for PUSCH/SRS component.
-47...80 dB
Time interval for sending averaged RSSI and SINR values to the decision matrix to determine power corrections in closed loop uplink power control.
10...2000 ms
step 1 dB
(ulpcUpqualCch) Upper SINR Threshold For PUSCH Power Command Decision
LNCEL
11 dB
step 1 dB
(ulpcUpqualSch) Time Interval For Power Command Decisions
LNCEL
(ulpcReadPeriod)
Table 3
50 ms
step 10 ms
Parameters common for open and closed loop UL power control
Name
Object
Description
Enabled TB Size Impact To UE PUSCH Power Calculation
LNCEL
This parameter enables/disables a transport 0 (false), format dependent offset on a per UE basis. In 1 (true) case that this parameter is enabled, PUSCH power calculation in UE uplink power control equation (P1) takes the transport block size in account during power calculation.
1
LNCEL
This parameter parameter defines the deltaF PUCCH Format 1.
1
(deltaTfEnabled)
DeltaF PUCCH Format 1 (dFpucchF1)
Range
0 (-2),
Default value
1 (0), 2 (2)
DeltaF PUCCH Format 1b
LNCEL
(dFpucchF1b)
This parameter parameter defines the deltaF PUCCH Format 1b.
0 (1),
0
1 (3), 2 (5)
DeltaF PUCCH Format 2
LNCEL
(dFpucchF2)
This parameter parameter defines the deltaF PUCCH Format 2.
0 (-2),
1
1 (0), 2 (1), 3 (2)
DeltaF PUCCH Format 2a (dFpucchF2a)
LNCEL
This parameter parameter defines the deltaF PUCCH Format 2a.
0 (-2),
1
1 (0), 2 (2)
22
DN0978045
Issue: 02B
Feature Descriptions RL10
Table 3
Feature Descriptions RL10
Parameters common for open and closed loop UL power control (Cont.)
Name
Object
Description
Range
Default value
DeltaF PUCCH Format 2b
LNCEL
This parameter parameter defines the deltaF PUCCH Format 2b.
0 (-2),
1
(dFpucchF2b)
1 (0), 2 (2)
Filter Coefficient
LNCEL
(filterCoeff)
This parameter specifies the filtering coefficient used for RSRP (3GPP: TS 36.331)
0 (fc0),
4
1 (fc1), 2 (fc2), 3 (fc3), 4 (fc4), 5 (fc5), 6 (fc6), 7 (fc7), 8 (fc8), 9 (fc9), 10 (fc11), 11 (fc13), 12 (fc15), 13 (fc17), 14 (fc19)
1.1.1.6.2
Measurements and counters
Counters for: LTE CELL LOAD MEASUREMENT Table 4
New and modified counters
Counter
Number
TPC -1dB for PUCCH
M8001CR Number of sent TPC -1 dB values for PUCCH. D900 Updated when Closed Loop UL power command for PUCCH with value -1 dB is sent on PDCCH to UE.
TPC -0dB for PUCCH
M8001CR Number of sent TPC 0 dB values for PUCCH. D901 Updated when Closed Loop UL power command for PUCCH with value 0 dB is sent on PDCCH to UE.
TPC +1dB for PUCCH
M8001CR Number of sent TPC +1 dB values for PUCCH. D902
Issue: 02B
Description
DN0978045
23
Feature Descriptions RL10
Table 4
Feature Descriptions RL10
New and modified counters (Cont.)
Counter
Number
Description Updated when Closed Loop UL power command for PUCCH with value +1 dB is sent on PDCCH to UE.
TPC +3dB for PUCCH
M8001CR Number of sent TPC +3 dB values for PUCCH. D903 Updated when Closed Loop UL power command for PUCCH with value +3 dB is sent on PDCCH to UE.
TPC -1dB for PUSCH
M8001CR Number of sent TPC -1 dB values for PUSCH. D904 Updated when Closed Loop UL power command for PUSCH with value -1 dB is sent on PDCCH to UE.
TPC -0dB for PUSCH
M8001CR Number of sent TPC 0 dB values for PUSCH. D905 Updated when Closed Loop UL power command for PUSCH with value 0 dB is sent on PDCCH to UE.
TPC +1dB for PUSCH
M8001CR Number of sent TPC +1 dB values for PUSCH. D906 Updated when Closed Loop UL power command for PUSCH with value +1 dB is sent on PDCCH to UE.
TPC +3dB for PUSCH
M8001CR Number of sent TPC +3 dB values for PUSCH. D907 Updated when Closed Loop UL power command for PUSCH with value +3 dB is sent on PDCCH to UE.
1.1.1.7
Activating The Feature This feature needs activation. For instructions see Activating the LTE28:Closed loop UL power control.
1.1.1.8 1.1.1.8.1
Abbreviations 0–Z A xxx
1.1.2 LTE30: CQI adaption (DL) 1.1.2.1
Introduction to the feature CQI (channel quality indicator) is an indicator of the current downlink channel conditions as seen by the UE. In LTE, the user equipment (UE) reports CQIs to assist the eNodeB in selecting an appropriate modulation and coding scheme (MCS) to be used for the downlink transmission. A high CQI value is indicative of a channel with high quality. The UE determines the CQI value from the downlink received signal quality, typically based on measurements of the downlink reference signals.
24
DN0978045
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
A CQI value reported from the UE may not be reliable enough for the eNodeB selecting a modulation and coding scheme to achieve a certain (low) block error rate (BLER) for downlink data transmission. Therefore the eNodeB adjusts the reported CQI value by taking into account ACK/NACK (acknowledged / not acknowledged) reports from the UE for received downlink data blocks (e.g. NACK is sent if the UE could not successfully decode a received data block). This process is called CQI adaptation. The adjusted CQI value is used by the AMC (adaptive modulation and coding) algorithm, which is a component of the link adaptation functionality within the eNodeB, to select the optimum MCS for the following downlink data transmission.
1.1.2.2
Benefits CQI adaptation compensates user equipment measurement errors (yielding to suboptimal CQI values reported to the eNodeB) and allows to achieve a configurable DL target block error rate (BLER).
1.1.2.3 1.1.2.3.1
Requirements Software requirements Table 5
1.1.2.3.2
Software requirements for different network elements
Network element
Required software release
System release
RL09
eNodeB
LBTS0.5
MME
–
SAE GW
–
UE
3GPP release 8
NetAct
–
Hardware requirements This feature does not require any additional hardware.
1.1.2.4 1.1.2.4.1
Functional description Functional details CQI adaptation is the adjustment of the reported CQI value in the eNodeB with an adapted offset before link adaptation by AMC (adaptive modulation and coding) is applied in downlink direction. Figure 2: Principle of CQI adaptation shows how the offset value ΔCQI is calculated and applied. CQI adaptation is also called outer loop quality control (OLQC): An UL ACK/NACK report and the following DL transmission, whose MCS is influenced by the previous ACK/NACK report and which determines the next UL ACK/NACK report, form a loop.
Issue: 02B
DN0978045
25
Feature Descriptions RL10
Figure 2
Feature Descriptions RL10
Principle of CQI adaptation
Data blocks Packet scheduler
DL link adaptation: Select MCS
(PDSCH) Evaluate reference signals
CQI adaptation
CQI report
CQIreported
(PUCCH/PUSCH) Decode transport blocks
ACK ACK/NACK (PUCCH/PUSCH)
1st DL transport block transmissions
NACK
UE
CQIreported + ΔCQI = CQIcorrected
ΔCQI(t-1) + CQIstepup = ΔCQI(t) ΔCQI(t-1) + CQIstepdown = ΔCQI(t)
Additionally: ΔCQI between CQImax and CQImin
eNodeB
The CQI offset is determined in the eNodeB with the help of the incoming ACK/NACK responses from the UE (via L1/L2 control signaling) for the initial transmission of each transport block in DL direction. For a correct received transport block the offset value ΔCQI is increased by a step CQIstepup whereas for an incorrect transport block the value is decreased by CQIstepdown. No change is done when no ACK/NACK is available or in case of a retransmission of the corresponding transport block (there are some other specific conditions where ΔCQI is not changed). The parameters CQIstepup and CQIstepdown are chosen in a way that a certain block error rate target value (BLERtarget) is reached. The offset value ΔCQI lies between a maximum and minimum value.
1.1.2.5 1.1.2.5.1
System impacts Interdependencies between features CQI adaptation is closely related to the feature LTE31 “Link adaptation by AMC (UL/DL)”: The selection of the appropriate modulation and coding scheme for DL transmission by the AMC (adaptive modulation and coding) algorithm is based on the adjusted CQI value. For more information, see the functional area description “Link control”.
1.1.2.6 1.1.2.6.1
User interface Parameters The following table shows the parameters implemented for the feature “LTE30: CQI adaption (DL)”.
26
DN0978045
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
Name
Object
Description
Range
Default value
dlOlqcEnable
LNCEL
This parameter allows to enable/disable CQI adaption (i.e. downlink outer loop link quality control).
false (0)
true (1)
Other parameters for this feature are internal or vendor-specific.
1.1.2.7
Activating The Feature This feature requires activation. For instructions see Activating the LTE30:CQI Adaption.
1.1.3 LTE37: Ciphering and LTE38: Integrity protection 1.1.3.1
Introduction to the feature Security for the eNodeB (as a network element) is at first time specified by 3GPP for LTE. This means:LTE is here the leading radio standard. It is needed to protect the confidentiality of the user and mitigate the effects of attacks on the network. In this document, the security for the radio access network is described (in other words:The air link security). This feature description LTE37: Ciphering and LTE38: Integrity protection consists user data security between UE and eNodeB for radio layer 2 (u-plane data) and radio layer 3 (RRC, control plane data). Two functions are provided for the maintenance of security: Ciphering and integrity protection. •
•
Ciphering is applied on both control plane data (RRC signalling) and user plane data and it is used in order to protect the data streams from being eavesdropped by a third party. Part of Ciphering is also the key derivation function (SHA-256 in RL 3 protocol) Integrity protection is applied on control plane data only and allows the receiver to detect packet insertion or replacement.
Ciphering and integrity protection within the access stratum is performed in the PDCP layer. The Flexi Multiradio BTS supports ciphering for the user plane PDUs and the RRC PDUs according to the 3GPP specifications TS 36.300, TS 36.323, TS36.331 and TS36.401. The keys used for ciphering and integrity protection of traffic (data / control signalling) are established when a connection between UE and the eNodeB/network is built up and they are discarded after a session has been closed (sometimes keys can change within a session); UE and eNodeB establish the same keys. The keys have 128 bits length and are derived from superior keys which are organized in a hierarchical structure. The last joint key KASME used for derivation of AS keys is calculated in the Home Subscriber Server (HSS) and stored and used in the MME and in a secure part of the Universal Subscriber Identity Module (USIM) in the UE. The eNode supports the following ciphering / integrity protection algorithms (EEA: EPS encryption algorithm; EIA: EPS integrity algorithm): •
Issue: 02B
Null algorithm (EEA0/EIA0 – providing no security)
DN0978045
27
Feature Descriptions RL10
Feature Descriptions RL10
SNOW 3G (EEA1/EIA1) AES (EEA2/EIA2)
• •
A ciphering algorithm uses a ciphering key (and other parameters) as input to create a key stream which is combined with the plaintext stream. The resulting ciphered data stream is transmitted and the receiver gets the plaintext back by applying the same key stream on the ciphered data stream in the same way as done during ciphering. Ciphering is an optional feature. If a customer decides not to buy a license for this feature, he can use a NULL-algorithminstead. An integrity protection algorithm uses an integrity protection key (and other parameters) as input to create a message authentication code added to the message to be sent. The integrity protection is a mandatory feature. From3GPPview no integrity protection NULLalgorithm is available. But in extension to 3GPP- completely explained by the LTSI-forum there a IP-NULL-algorithm is implemented. This extension can only be used if the MME is configured to do so, such it can not be used by accident.
1.1.3.2
Benefits Ciphering and integrity protection in the access stratum (AS) provides security of the air interface and protects against attacks and eavesdropper.
1.1.3.3 1.1.3.3.1
Requirements Software requirements Table 6
1.1.3.3.2
Software requirements for different network elements
Network element
Required software release
System release
RL10
eNodeB
LBTS1.0
MME
NS10 CD2
SAE GW
–
UE
3GPP release 8
NetAct
–
Hardware requirements This feature does not require any additional hardware.
28
DN0978045
Issue: 02B
Feature Descriptions RL10
1.1.3.4 1.1.3.4.1
Feature Descriptions RL10
Functional description Functional overview Figure 3: C-plane security and Figure 4: U-plane security show the overall security concept within LTE. The security architecture is different for user plane traffic and control plane traffic. Here and in following sections, security aspects for the non-access stratum (NAS) are also included in order to show relations between NAS and AS security and for comprehensibility. Figure 3
C-plane security integrity protected, ciphered
NAS
RRC
integrity protected ciphered
RRC
NAS
integrity protected
S1AP/X2AP
L3
ciphered
AP
PDCP
L4
...
...
SCTP
SCTP
PDCP
L2
S1AP
IPv4/IPsec
IPv4/IPsec L3
...
eNB
UE
MME
...
integrity protected, ciphered
RRC eNB
Figure 4
X2AP
...
...
AP: Application Layer L2, L3, ...: Layer 2, Layer 3, ...
U-plane security
Data stream
PDCP ...
Data stream
ciphered
PDCP L2
integrity protected
GTP-U AP
...
GTP-U
ciphered
UDP
UDP
integrity protected ciphered
GTP-U UDP
L4
IPv4/IPsec L3 ... UE
eNB
IPv4/IPsec ... S-GW
IPv4/IPsec ... P-GW
integrity protected, ciphered
PDCP
GTP-U
...
...
eNB
AP: Application Layer L2, L3, ...: Layer 2, Layer 3, ...
C-plane security includes the following characteristics: • • •
• •
Issue: 02B
NAS signalling protection is transparent for the eNodeB. NAS signalling is ciphered and integrity protected between UE and MME. RRC integrity protection and ciphering is applied to NAS messages carried by RRC messages in addition to the NAS signalling security between MME and UE. This results in double protection of NAS signalling. RRC signalling is always integrity protected by PDCP in the eNodeB and in the UE. RRC signalling is ciphered between UE and eNodeB by PDCP.
DN0978045
29
Feature Descriptions RL10
•
•
Feature Descriptions RL10
S1AP signalling is ciphered and integrity protected between eNodeB and MME by an underlying transport security mechanism. This is an seperate feature (LTE689) and describedt into FAD: IPsec operation. It is an optional feature. X2AP signalling is protected in the same way as S1AP signalling.
The security described by LTE:37/LTE38 is always between UE and eNodeB. If there is data forwarding from an source-eNodeB to a target eNodeB there will be transport security activated.
1.1.3.4.2
Security keys Various security keys are used for ciphering and integrity protection of traffic depending on the type of traffic (user data / control signalling) and the related stratum (NAS/AS). For the NAS (non access stratum) these are: •
KNASenc for encryption of NAS messages between UE and MME
•
KNASint for integrity protection of NAS messages between UE and MME
For the AS (access stratum; transmission between UE and eNodeB) the following security keys are used: •
KUPenc for encryption of user plane traffic
•
KRRCenc for encryption of control plane traffic (which is RRC signalling)
•
KRRCint for integrity protection of control plane traffic
The keys are derived from superior keys organized in a hierarchical structure. The AS keys KUPenc, KRRCenc and KRRCint are derived from KeNB which is related to a certain eNodeB and which itself is derived from the superior key KASME. The NAS keys KNASenc and KNASint are also derived from KASME. Figure 5: Security key hierarchy shows the LTE security key hierarchy and key distribution concept. KASME is available in the Authentication Center (AuC) which resides in the Home Subscriber Server (HSS) and in a secure part of the Universal Subscriber Identity Module (USIM) in the UE; UE and eNodeB use the same KASME for deriving their security keys. ASME is the Access Security Management Entity of the EPS (evolved packet system) and is located in the MME. The key K which is the origin of all other keys and the keys CK (cipher key) and IK (integrity key) have no direct effect on RRM and are mentionened just for completeness. Other keys or structures for ciphering / integrity protection such as KeNB* and NH are described in the related chapters.
30
DN0978045
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
Figure 5
Security key hierarchy
UE
HSS K
CK
K
IK
CK
IK
MME KASME
KASME
KNASint KNASenc
KNASint KNASenc
Keys for NAS signalling
KASME
NAS area AS area
KeNB
KeNB
KeNB
eNB KUPenc KRRCint KRRCenc
AS keys for C-plane and U-plane traffic
KUPenc KRRCint KRRCenc
Lifetime of security keys The existence of a key depends on the EMM/RRC state of a UE in respect of connection establishment (EMM: EPS mobility management; ECM: EPS connection management): • •
•
K exists always; it is the only permanent key. The NAS keys KASME, KNASenc, KNASint and CK, IK exist while the EMMREGISTERED state is ongoing. The AS keys KeNB, KUPenc, KRRCint, and KRRCenc are created on RRC-IDLE to RRCCONNECTED transitions (correlated with ECM-IDLE to ECM-CONNECTED transitions) when in EMM-REGISTERED state (as the UE is in EMM-REGISTERED state, an EPS security context already exists in the UE and the MME) and they exist during RRC-CONNECTED state. The eNodeB deletes the keys after receiving the S1AP: UE CONTEXT RELEASE COMMAND message.
Key establishment and key distribution The different security keys are established during specific key establishment procedures: •
Issue: 02B
Authentication and Key Agreement (AKA): This procedure is performed when a UE initially attaches to the network. The MME authenticates the subscriber, and the keys CK, IK, and KASME are established, once in the USIM/UE, and in the same way in the AuC/HSS. KASME is derived from CK, IK and the PLMN ID; the HSS transfers KASME to the MME. AKA is a NAS procedure and does not have any prerequisite besides the permanent key K.
DN0978045
31
Feature Descriptions RL10
•
•
•
Feature Descriptions RL10
NAS Security Mode Command (NAS SMC) procedure: This procedure is performed when the UE has successfully been authenticated. MME and UE generate the NAS keys KNASenc and KNASint for NAS signalling security. NAS SMC needs a valid KASME as prerequisite. In addition, NAS SMC activates the NAS security mechanisms. KeNB establishment: The procedure applied is specific for different cases: –
For a change of state to RRC-CONNECTED, KeNB is derived in the UE and in the MME from KASME and the eNodeB ID. The MME transmits KeNB to the eNodeB by the S1AP: INITIAL CONTEXT SETUP REQUEST message. MME and UE also derive the next hop (NH) parameter from the KASME.
–
For an intra-LTE intra-frequency handover, the source eNodeB creates KeNB*, a transport security key, which is transferred via X2 interface to the target eNodeB where the KeNB to be used is derived from the KeNB* (for more information, see below).
AS Security Mode Command (AS SMC) procedure: The eNodeB selects the security parameters required for deriving the AS security keys. These parameters are transferred to the UE via the SECURITY MODE COMMAND message. Then the UE and eNodeB derive the AS keys KUPenc, KRRCint, and KRRCenc from KeNB. These keys are needed for user plane encryption and RRC integrity protection and encryption. AS SMC needs a valid KeNB as prerequisite. In addition, AS SMC activates the AS security mechanisms.
Key set identifier and key change indicator At initial context setup AS and NAS security start with a common KASME key. Later, several KASME may be known by network and UE. For example, while the RRCCONNECTED state is still ongoing, NAS may apply a new KASME (by executing another NAS security mode command). In this case there is the old KASME, from which NAS and AS keys are still derived, and the new KASME, from which fresh NAS and AS keys shall be derived. Therefore, a specific parameter identifies a particular KASME. Subsequently to a NAS change of KASME (while the AS KASME is still used), AS follows the NAS change which includes a handover. The parameter identifying a particular KASME is KSI (key set identifier). KSI is generated together with KASME during the Authentication and Key Agreement procedure. All keys derived from a KASME inherit this KSI (this is why KSI is called a "set" identifier). The KSI is signalled at NAS level only, i.e. during the Authentication and Key Agreement procedure and NAS security mode command procedure. At AS level the KSI is not signalled. Instead, implicit dependencies between NAS and AS procedures keep the AS keys synchronous in the network and the UE: At beginning of AS procedures for an RRC connection, the AS uses the same KASME as the NAS, and AS does not change this KASME during usual AS key changes. Only in combination of an intra-cell handover AS may change the KASME. In this case the KASME change is signalled by a flag called KCI (key change indicator).
32
DN0978045
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
Key handling in case of handover The target eNodeB gets its KeNB to be used for generating its U-plane and C-plane keys as follows: The source eNodeB determines a transport security key KeNB* and transmits this key via X2 interface to the target eNodeB. Then the target eNodeB derives K eNBfrom KeNB*. One possibility to determine KeNB* is to have it derived directly from the currently active KeNB. This direct derivation of KeNB* uses a cryptographic hash function, so it is not feasible to reconstruct the source KeNB from the new target KeNB. Therefore a target eNodeB does not expose the security of the source eNodeB; in other words: backward security is guaranteed. However, there is no forward security which means that the target eNodeB keys are no secret for the source eNodeB. The second possibility to determine KeNB* is to have it derived from the NH (next hop) parameter which was calculated from the KASME. Since the source eNodeB cannot recalculate KeNB* from KeNB, forward security is achieved. In case of a S1 handover, NH is transported from the MME by the S1AP: HANDOVER REQUEST message and is immediately available for the handover (forward security after one hop). In case of X2 handover, NH is transported by the S1AP: PATH SWITCH ACKNOWLEDGEMENT message and is not availabe for the current handover (because the new keys are already determined at this point in time) but for the next one. Therefore, forward security is reached at next handover (forward security after two hops). Subsequent handovers with each transport KeNB* derived directly from the previous KeNB form a chain with backward security only. A handover where the transport KeNB* is derived via NH is the starting point for another chain with backward security only. These chains are counted and identified with the NCC (next hop chaining counter) parameter signalled by the MME; NCC has the value 0 at the initial security context setup.
1.1.3.4.3
Messages and information elements The following table shows the messages which include relevant security information and their security related content:
Table 7
Security related messages and information elements
Message
Information element
IE includes
“securityConfigSMC”
“securityAlgorithmConfig” IE
RRC messages SECURITY MODE COMMAND
(“cipheringAlgorithm” and “integrityProtAlgorithm”) RRC CONNECTION REESTABLISHMENT REQUEST
“ue-Identity”
shortMAC-I
RRC CONNECTION RECONFIGURATION
“securityConfigHO”
“keyChangeIndicator” (not processed by the eNodeB) “nextHopChainingCount”
Issue: 02B
DN0978045
33
Feature Descriptions RL10
Table 7
Feature Descriptions RL10
Security related messages and information elements (Cont.)
Message
Information element
IE includes “securityAlgorithmConfig” (“cipheringAlgorithm” and “integrityProtAlgorithm”; only necessary in case of algorithm changes)
RRC MOBILITY FROM EUTRA COMMAND
“nasSecurityParamFromEUTR A”
S1AP messages INITIAL CONTEXT SETUP REQUEST
“UE Security Capabilities” “Security Key”
“HandoverPreparationinformation” IE such as ciphering and integrity protection information of the serving cell and the “targetCellShortMAC-I” Initial security key KeNB
HANDOVER REQUIRED
“RRC Context”
“HandoverPreparationinformation” IE such as ciphering and integrity protection information of the serving cell and the “targetCellShortMAC-I”
HANDOVER REQUEST
“RRC Context”
(see above)
“UE Security Capabilities”
(see below)
“SecurityContext”
NH parameter NCC related to NH.
HANDOVER COMMAND
“NAS Security Parameters “HandoverPreparationinformation” such from E-UTRAN” as ciphering and integrity protection information of the serving cell and the “targetCellShortMAC-I”
PATH SWITCH REQUEST
“UE Security Capabilities”
Supported encryption and integrity protection algorithms in two 2-bit representations.
PATH SWITCH REQUEST ACKNOWLEDGEMENT
“SecurityContext”
NH parameter NCC related to NH.
X2AP messages HANDOVER REQUEST
“UE Context Information”
“RRC Context” “UE Security Capabilities” “AS Security Information” (transition key KeNB* and NCC)
34
DN0978045
Issue: 02B
Feature Descriptions RL10
1.1.3.5 1.1.3.5.1
Feature Descriptions RL10
System impacts Interdependencies between features An additional security feature is the optional LTE689 “LTE IPsec support” which allows secure eNodeB control and secure bulk data communication between eNodeBs as well as between eNodeBs and core nodes. IPsec is related to transport and application protocols. Supported IPsec capabilities are data integrity protection, origin authentication and anti-replay protection.
1.1.3.5.2
Impacts on network elements A secure environment is required in the network elements storing security keys. The Flexi Multiradio BTS provides such a secure environment.
1.1.3.5.3
Impacts on system performance and capacity Security mechanisms are associated with processing effort and additional control data according to common laws.
1.1.3.6 1.1.3.6.1 Table 8
User interface Parameters
Parameters for ciphering and integrity protection
Full name (Short name)
Object
Description
Range / Step
Default value
Ciphering Algorithm Activation
LNBTS
This parameter allows to enable/disable the optional ciphering algorithms.
false (0), true (1)
true (1)
LNBTS
A list of supported AS ciphering algorithms. The algorithm is identified by the parameter name, and the assigned value determines the algorithm preference.
–
–
LNBTS
A list of supported AS integrity protection algorithms. The algorithm is identified by the parameter name, and the assigned value determines the algorithm preference.
–
–
LNBTS
This parameter defines a threshold for PDCP COUNT supervision. If the remaining COUNT space becomes less than this threshold, the eNodeB key hierarchy will be refreshed.
0 ... 4 294 96 7 295,
50 000
(actCiphering) Ciphering Algorithm Preference List (cipherPrefL)
Integrity Protection Algorithm Preference List (integrityPrefL)
Key Refresh Margin (keyRefrMarg)
Issue: 02B
DN0978045
step 1
35
Feature Descriptions RL10
Table 8
Feature Descriptions RL10
Parameters for ciphering and integrity protection (Cont.)
Full name (Short name)
Object
Description
Range / Step
Default value
Null Ciphering Algorithm Fallback
LNBTS
This parameter determines if a fallback to Null ciphering caused by eNodeB limitations is accepted (true) or not (false).
false (0), true (1)
true (1)
(nullFallback)
1.1.3.7
Activating The Feature The feature LTE37: ciphering requires activation. For instructions see Activating the LTE37:Ciphering.
1.1.4 LTE43: Support of 64 QAM in DL, LTE788: Support of 16 QAM (UL), LTE793: Support of 16 QAM (DL) 1.1.4.1
Introduction to the feature The original bit streams in the eNodeB and in the UE are digital. To send them via radio antenna they must be converted to analogous waveform. This is done by modulation. The basic modulation method is QPSK for robust transmission on PUSCH and PDSCH. On top there are higher order modulations with QAM (quadrature amplitude modulation) - which are the content of this feature description. This feature description comprises the following features: • • •
1.1.4.2
LTE793:”Support of 16QAM (DL)” LTE788:”Support of 16QAM (UL)” LTE43:”Support of 64QAM in DL”
Benefits The benefits of the features are: 16QAM: Increase of the peak rate by 100% compared to QSPK, around 70% increased spectral efficiency. 64QAM(DL) : Increase of the DL peak rate by 50% as compared to 16QAM scenario. Figure 6: Throughput for different modulation schemes gives a short overview of the throughput of different modulation schemes. The figure is valid for a bandwidth of 20Mhz.
36
DN0978045
Issue: 02B
Feature Descriptions RL10
Figure 6
1.1.4.3 1.1.4.3.1
Feature Descriptions RL10
Throughput for different modulation schemes
Requirements Software requirements The following software is required for these features: Table 9
1.1.4.3.2
Software requirements for different network elements
Network element
Required software release
System release
RL09
eNodeB
64QAM: LBTS0.5, 16QAM: –
UE
3GPP release 8
Hardware requirements This feature does not require any new or additional hardware.
Issue: 02B
DN0978045
37
Feature Descriptions RL10
1.1.4.4 1.1.4.4.1
Feature Descriptions RL10
Functional description Functional details Quadrature amplitude modulation (QAM) is one of the widely used modulation schemes, which changes (modulates) the amplitude of two othogonal sinusoidal carrier waves depending on the input bits as follows
where I(t) and Q(t) are the modulating signal amplitudes, f is the carrier frequency. In a graphical representation (I-Q-plane) the I- and Q- amplitudes are arranged in a square grid with equal vertical and horizontal spacing. 16QAM consists of a 4 x 4 grid of (I,Q)-points, 64QAM consists of a 8 x 8 grid. Figure 7
QAM modulation 16QAM 4 bits/symbol
64QAM 6 bits/symbol
Q
Q
I
I
In case of downlink direction the QAM (both 16QAM and 64QAM) is used by link adaption and coding for PDSCH (physical downlink shared channel), in case of uplink direction the 16QAM is used by adaptive modulation for PUSCH (physical uplink shared channel).
1.1.4.5 1.1.4.5.1
System impacts Interdependencies between features LTE31:” Link adaptation by AMC” describes how QAM is deployed by link adaption.
1.1.4.6
Sales information These features are optional.
38
DN0978045
Issue: 02B
Feature Descriptions RL10
1.1.4.7 1.1.4.7.1
Feature Descriptions RL10
User interface Managed objects The managed object class LNCEL is used. Attribute of it is the parameter dl64QamEnable. Parent of LNCEL is LNBTS.
1.1.4.7.2 Table 10
Parameters
Parameters for LTE43: Support of 64QAM in DL
Name
Object
Description
Range
Default value
dl64QamEnable
LNCEL
Enables/disables downlink 64 QAM modulation for link adaptation use in PDSCH.
false, true
–
1.1.4.7.3
Measurements and counters The following counters are defined for the feature LTE43:”Support of 64QAM in DL” Table 11
Issue: 02B
Counters for LTE43
Network element name
Database ID
Description
HarqAck16QAM_Dl
47244
Downlink HARQ Acks received.
HarqOkRetr1_16QAM_Dl
47247
DL-SCH TBs acknowledged at the 1st retransmission.
HarqOkRetr2_16QAM_Dl
47251
DL-SCH TBs acknowledged at the 2nd retransmission.
HarqOkRetr3_16QAM_Dl
47255
DL-SCH TBs acknowledged at the 3rd retransmission or later.
HarqSizeOrig16QAM_Dl
47261
Total size of original transmissions of DLSCH TBs.
HarqSizeRetr16QAM_Dl
47264
Total size of retransmissions of DL-SCH TBs.
HarqSizeOk16QAM_Dl
47258
Total size of acknowledged DL-SCH TBs.
TbSchOrig16QAM_Dl
47270
Number of original HARQ transmissions of transport blocks on DL-SCH.
TbSchRetr16QAM_Dl
47273
Number of HARQ retransmissions of transport blocks on DL-SCH.
DN0978045
39
Feature Descriptions RL10
Table 11
40
Feature Descriptions RL10
Counters for LTE43 (Cont.)
Network element name
Database ID
Description
TbSchNoHarq16QAM_Dl
47267
Number of transmitted transport blocks on DL-SCH without HARQ. For these blocks, the HARQ counters shall not be updated.
HarqAck64QAM_Dl
47245
Downlink HARQ Acks received.
HarqOkRetr1_64QAM_Dl
47248
DL-SCH TBs acknowledged at the 1st retransmission.
HarqOkRetr2_64QAM_Dl
47250
DL-SCH TBs acknowledged at the 2nd retransmission.
HarqOkRetr3_64QAM_Dl
47253
DL-SCH TBs acknowledged at the 3rd retransmission or later.
HarqSizeOrig64QAM_Dl
47259
Total size of original transmissions of DLSCH TBs.
HarqSizeRetr64QAM_Dl
47262
Total size of retransmissions of DL-SCH TBs.
HarqSizeOk64QAM_Dl
47256
Total size of acknowledged DL-SCH TBs.
TbSchOrig64QAM_Dl
47268
Number of original HARQ transmissions of transport blocks on DL-SCH.
TbSchRetr64QAM_Dl
47271
Number of HARQ retransmissions of transport blocks on DL-SCH.
TbSchNoHarq64QAM_Dl
47265
Number of transmitted transport blocks on DL-SCH without HARQ. For these blocks, the HARQ counters shall not be updated.
HarqAckQPSK_Dl
47246
Downlink HARQ Acks received.
HarqOkRetr1QPSK_Dl
47249
DL-SCH TBs acknowledged at the 1st retransmission.
HarqOkRetr2QPSK_Dl
47252
DL-SCH TBs acknowledged at the 2nd retransmission.
HarqOkRetr3QPSK_Dl
47254
DL-SCH TBs acknowledged at the 3rd retransmission or later.
HarqSizeOrigQPSK_Dl
47260
Total size of original transmissions of DLSCH TBs.
HarqSizeRetrQPSK_Dl
47263
Total size of retransmissions of DL-SCH TBs.
DN0978045
Issue: 02B
Feature Descriptions RL10
Table 11
1.1.4.8
Feature Descriptions RL10
Counters for LTE43 (Cont.)
Network element name
Database ID
Description
HarqSizeOkQPSK_Dl
47257
Total size of acknowledged DL-SCH TBs.
TbSchOrigQPSK_Dl
47269
Number of original HARQ transmissions of transport blocks on DL-SCH.
TbSchRetrQPSK_Dl
47272
Number of HARQ retransmissions of transport blocks on DL-SCH.
TbSchNoHarqQPSK_Dl
47266
Number of transmitted transport blocks on DL-SCH without HARQ. For these blocks, the HARQ counters shall not be updated.
Activating The Features Thess features require activation. For instructions see Activating the LTE793: Support of 16QAM (DL), Activating the LTE788: Support of 16QAM (UL), Activating the LTE43: Support of 64QAM in DL.
1.1.4.9 1.1.4.9.1
Abbreviations 0–Z 3GPP third generation partnership project
AMC adaptive modulation and coding
CQI channel quality indicator
DL downlink
HARQ hybrid automatic repeat request
LBTS land based test side
Issue: 02B
DN0978045
41
Feature Descriptions RL10
Feature Descriptions RL10
LTE long term evolution
MCS modulation and coding scheme
MIMO multiple input multiple output
PDSCH physical downlink shared channel
PUSCH physical uplink shared channel
QAM quadrature amplitude modulation
QPSK quadrature phase shift keying
Rc Rate code for channel coding
UE user equipment
UL uplink
SCH synchronization channel
SNIR signal to noise and interference ratio
TB transport block
42
DN0978045
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
TTI transmission time interval
1.1.5 LTE69: Transmit diversity for two antennas and LTE70: Downlink adaptive open loop MIMO for two antennas 1.1.5.1
Introduction to the feature The following features offer solutions related to multi-path downlink transmissions. As MIMO (Multiple Inputs Multiple Outputs) is one of the key features of LTE, techniques for “downlink adaptive open loop MIMO” and “transmission diversity” are presented. By applying the feature LTE70: Downlink adaptive open loop MIMO for two antennas, the eNodeB selects dynamically between “Space Frequency Block Coding (SFBC) transmit diversity” and “Open Loop Spatial Multiplexing” with “Large-delay Cyclic Delay Diversity” (“Large-delay CDD”). When using the feature LTE69: Transmit diversity for two antennas, the eNodeB transmits each data stream via 2 TX diversity paths, and the “Space Frequency Block Code” mode is applied. Diversity methods are complementing the basic feature LTE187: Single TX path mode, where the TX signal is transmitted via a single TX antenna per cell, either due to HW configuration or in semi-static mode selected by O&M for HW configurations with two TX paths per cell.
1.1.5.2
Benefits In the following section, benefits for operators and end users are summarized with regard to the following features: • •
1.1.5.2.1
LTE69: Transmit diversity for two antennas LTE70: Downlink adaptive open loop MIMO for two antennas
End user benefits The mentioned features support radio links, offering high data rates and signal quality.
1.1.5.2.2
Operator benefits By the feature LTE69: Transmit diversity for two antenna, cell coverage and capacity are enhanced by the transmit diversity of two antennas. The feature LTE70: Downlink adaptive open loop MIMO for two antennas provides high peak rates (using two code words) and good cell edge performance (using a single code word) by the adaptive algorithm. Furthermore, “double stream 2x2 MIMO spatial multiplexing (open loop)” can be used for small cells with low load if the UE capabilities are sufficient.
1.1.5.3
Requirements For the features LTE70: Downlink adaptive open loop MIMO for two antennas and LTE69: Transmit diversity for two antennas, the following hardware and software requirements have to be met.
Issue: 02B
DN0978045
43
Feature Descriptions RL10
1.1.5.3.1
Feature Descriptions RL10
Software requirements The features LTE69 and LTE70 require RL09 software.
1.1.5.3.2
Hardware requirements The features LTE70 and LTE69 require particular hardware to support radio diversity techniques: • •
For LTE70: Downlink adaptive open loop MIMO for two antennas, the eNodeB and the UE support MIMO. UEs which are not MIMO capable shall use dlMimoMode=1. For LTE69: Transmit diversity for two antennas, the eNodeB has to be equipped with two antennas at least.
UEs as defined in 3GPP release 8 comply with these requirements.
1.1.5.4 1.1.5.4.1
Functional description Functional overview By means of the feature LTE70: Downlink adaptive open loop MIMO for two antennas, the eNodeB is able to select dynamically between “Space Frequency Block Coding (SFBC) Transmit Diversity” and “Open Loop Spatial Multiplexing” with “Large-delay Cyclic Delay Diversity” (“Large-delay CDD”). Open loop spatial multiplexing is offered with two code words with “Large-delay CDD” for the PDSCH (Physical Downlink Shared Channel) on UE basis. Using the feature LTE69: Transmit diversity for two antennas, the eNodeB transmits single data streams via 2 TX diversity paths. Furthermore, each data stream is transmitted by two diversity antennas per sector, and “Space Frequency Block Coding (SFBC) Transmit Diversity” is applied. Diversity methods complement the basic feature LTE187: Single TX path mode.
1.1.5.4.2
Downlink adaptive open loop MIMO for two antennas By means of the feature LTE70: Downlink adaptive open loop MIMO for two antennas, the eNodeB is able to select dynamically between “Space Frequency Block Coding (SFBC) Transmit Diversity” and “Open Loop Spatial Multiplexing” with “Large-delay Cyclic Delay Diversity” (“Large-delay CDD”). Open loop spatial multiplexing is offered with two code words with “Large-delay CDD” for the PDSCH on UE basis. The open loop dynamic MIMO switch functionality can be enabled and disabled on cell level by means of O&M. When the dynamic MIMO switch is disabled, either static multiplexing or static transmit diversity can be selected for the whole cell (all UEs). The dynamic switch takes into account the UE’s specific link quality and rank information. Furthermore, the UE radio capabilities are considered and additional offsets for CQI reporting compensation are provided with regard to the dynamic MIMO switching functionality. MIMO is a key technology in achieving the ambitious requirements for throughput and spectral efficiency for the LTE air interface. MIMO refers to the use of multiple antennas at the transmitter and at the receiver. For the LTE downlink, a 2x2 configuration for MIMO is assumed as baseline configuration, i.e. two transmit antennas at the base station and two receive antennas at the terminal side. Configurations with four transmit or receive antennas are also supported by LTE Rel-8. Different gains can be achieved depending on the MIMO mode that is used.
44
DN0978045
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
Table 12: Multi antenna options in LTE gives an overview on the typical LTE multi antenna configurations:
Issue: 02B
DN0978045
45
Feature Descriptions RL10
Table 12
Feature Descriptions RL10
Multi antenna options in LTE
DL
UL
BS
UE
TX
RX
1x2
1
2
2x2
2
2
Gain to smaller configuration
+ 4 .. 5 dB DL link budget
Configuration type
UE
BS
Gain to smaller configuration
TX
RX
1x2
1
2
minimum
1x2
1
2
standard
+ 100% peak data rate + user experience + 10% spectrum efficiency
The “standard” configuration of the LTE base station provides in addition to 2 RX antennas (RX diversity) 2 TX chains, which has the advantage in that no extra antenna and feeder cost is necessary compared to the minimum 1 TX chain. In a “high performance” scenario, 4 RX antennas at the LTE base station substantially enhance the LTE uplink path but require additional antenna and feeder effort and costs. Typically, the LTE UE is equipped with 2 RX antennas and 1 TX chain. 1.1.5.4.2.1
Receive diversity NSN supports 2-branch and plans to support 4-branch receive diversity based on MRC (Maximum Ratio Combining). MRC aims at combining the 2 (or 4) receive signals in such a way that the wanted signal's power is maximized compared to the interference and the noise power, i.e. the SINR (Signal to Interferer and Noise Ratio) is enhanced. Compared to a single receive branch, 2-branch receive diversity allows for: • • •
coherence link budget gain of 3 dB additional diversity link budget gain of some dB depending on many conditions including velocity, fading channel and carrier bandwidth link budget gain from MRC at about 10% Block Error Rate (BLER) may reach up to 6 dB (as shown in simulations)
Correspondingly, 4-branch receive diversity will show a coherence link budget gain of 6 dB plus some dB additional diversity link budget gain. Receive diversity with two receive branches requires two uncorrelated receive antennas using a single cross-polar antenna or two vertically polarized spatially separated antennas; 4-branch receive diversity requires four uncorrelated receive antennas using e.g. 2 spatially separated cross-polar antennas. Receive diversity complies with LTE Rel-8 terminals and is supported on all uplink channels. 1.1.5.4.2.2
Transmit diversity NSN supports 2-branch and plans to support 4-branch transmit diversity.
46
DN0978045
Issue: 02B
Feature Descriptions RL10
Feature Descriptions RL10
If the total eNodeB transmit power keeps the transmit power per transmit branch as high as for the single transmit antenna case, the link budget is increased by 3 dB for two branches and by 6 dB for four branches. This implies coverage and capacity enhancements. If the total eNodeB transmit power is constant (compared to the single transmit branch case), transmit diversity leads to more robust links at the cell edge while slightly reducing cell capacity. However, for DRX (Discontinuous Reception) VoIP users, transmit diversity slightly enhances cell capacity by approximately 5% for two transmit branches. Transmit diversity may be semi-statically configured per cell, while for non-MIMO UEs, dlMimoMode=1 for PDSCH is automatically selected. 1.1.5.4.2.3
Downlink open loop MIMO The typical MIMO configuration encompassing “dual code word 2x2 DL SU (Single-User) MIMO Spatial Multiplexing” is illustrated in the figure below. This MIMO scheme targets a duplication of the downlink peak user data rate by means of two independent parallel data streams to a single UE. This is also called “Spatial Multiplexing”. The two base station transmit signals, two UE receive signals, and four channels form (for each subcarrier) a system of two equations with two unknown transmit signals. The two unknown transmit signals can be achieved by channel estimation, possible transmit alphabet(s), and the two receive signals. Figure 8
2x2 MIMO configuration
Transmission of 2 independent data streams transmitted at the same time depends on the channels’ signal quality and the decorrelation of both channels. Correlation of the channels is determined by the antenna characteristics. For example antennas are uncorrelated if they: • • •
are spatially separated by about 10 or more wavelengths, or use orthogonal polarization planes (cross-polarity), or are located in a diffuse environment.
By uncorrelated antennas diversity and spatial multiplexing gains can be achieved, and coherence gains to some extent. For example antenna elements are correlated if they: • • •
Issue: 02B
are phased by ½ wavelength spacing, have a low angular spread, and are located in a non-diffuse environment (e.g. on the rooftop).
DN0978045
47
Feature Descriptions RL10
Feature Descriptions RL10
Correlated antennas easily provide robust coherence gains (the classical beamforming gain), but no spatial multiplexing or diversity gain. For Open Loop SU-MIMO Spatial Multiplexing, UE feedback, like PMI and RI is required. Mapping of data to the transmit antenna ports is fixed and the system cannot be influenced. If the conditions for “Spatial Multiplexing” not good enough, however, the UE may request to lower the transmission rank and ultimately falls back to dlMimoMode=1. For interoperability reasons, the “Open Loop SU-MIMO” scheme has to be based on the “Large-delay Cyclic Delay Diversity” (“Large-delay CDD”) precoding. The optimum unitary precoding matrix is selected by means of a predefined codebook which is known at eNodeB and UE side, and by the UE’s radio channel estimate. Operators may (statically) configure whether a cell supports “Transmit Diversity”, or “MIMO Spatial Multiplexing”, or allows for an adaptive mode. In the adaptive mode, the “Open Loop 2x2 SU-MIMO” fallback is “Space Frequency Block Coding (SFBC) Transmit Diversity”. In ideal situations, 2x2 SU-MIMO duplicates the peak user data rate. For realistic conditions, 2x2 SU-MIMO enhances cell capacity by 10% for macro-cellular and by 40% for micro-cellular deployment scenarios. The current eNodeB hardware meets the phase noise or the minimum jitter requirements (
View more...
Comments
