NSN-RL70 Feature Candidate Document
Short Description
Download NSN-RL70 Feature Candidate Document...
Description
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
1/68
Doc number
LTE RAN Release RL70 Feature Candidate Document
Version 1.0
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
2/68
Doc number
Version 1.0
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 2013. All rights reserved.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
3/68
Doc number
Version 1.0
Table of Contents 1 2 3
4
5
6
7
Introduction .................................................................................................................... 4 History ........................................................................................................................... 5 BTS Site Solution ........................................................................................................... 6 3.1 Site level RF Sharing between WCDMA-GSM-LTE ................................................ 6 3.2 FXED Flexi RF Module 6TX 1800 ........................................................................... 7 3.3 FWEA Flexi Zone BTS 1800 (Band 3)..................................................................... 9 3.4 Up to 12 optical RF ports for high capacity BTS configurations ............................. 11 3.5 LTE extended configurations up to 6 frequency bands .......................................... 13 Transmission ............................................................................................................... 15 4.1 User Layer TCP MSS clamping ............................................................................ 15 4.2 Sync Hub Direct Forward ...................................................................................... 16 4.3 Timing over Packet Resilience .............................................................................. 19 4.4 SCTP Multi-homing ............................................................................................... 20 Radio Resource Management and Telecom ................................................................ 22 5.1 LTE:Mobility .......................................................................................................... 22 5.1.1 Service based mobility trigger ........................................................................ 22 5.1.2 Intra-frequency load balancing ....................................................................... 23 5.1.3 RLF triggered handover ................................................................................. 25 5.1.4 Serving PLMN ID change during X2 based handover .................................... 27 5.2 LTE:Coverage, capacity and peak rates ............................................................... 28 5.2.1 eICIC - macro ................................................................................................ 28 5.2.2 eICIC - micro.................................................................................................. 30 5.2.3 Uplink intra eNode B CoMP 4RX ................................................................... 32 5.2.4 Liquid Cell ...................................................................................................... 34 5.2.5 Downlink interference shaping ....................................................................... 36 5.3 LTE:QoS, services and end user experience ........................................................ 37 5.3.1 Nominal Bitrate for non-GBR bearers ............................................................ 37 5.3.2 Extended VoLTE talk time.............................................................................. 39 5.3.3 Carrier aggregation for multi-carrier eNode Bs ............................................... 40 5.4 LTE:Basic LTE call handling and interworking ...................................................... 41 5.4.1 MORAN for two operators .............................................................................. 41 Operability.................................................................................................................... 42 6.1 Network Monitoring and Maintenance ................................................................... 42 6.1.1 MDT - UE measurement logs ......................................................................... 42 6.1.2 Remote RF-diagnostics for Flexi Multiradio BTS ............................................ 44 6.2 Configuration Management ................................................................................... 47 6.2.1 Neighbor Relation Robustness ...................................................................... 47 6.2.2 MRO Ping Pong ............................................................................................. 49 6.2.3 Neighbor Detection Optimization for HetNet .................................................. 51 6.2.4 PCI Assignment Optimization for HetNet ....................................................... 52 6.2.5 Neighbor Prioritization Optimization for HetNet .............................................. 53 6.2.6 System Upgrade to RL70 ............................................................................... 55 6.2.7 Automatic Configuration support for CA for multi-carrier eNBs ....................... 59 Performance Monitoring ............................................................................................... 60 7.1 Real-time KPI-monitoring with Traffica .................................................................. 60 7.2 PM Counters enhancement for RAB-modification/context/TM7 ............................. 67
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
4/68
Doc number
Version 1.0
1 Introduction This document provides the list of feature candidates for the LTE Radio Access System Release RL70. The scope of the document includes evolved NodeB (eNB) and Transmission. The LTE is managed with the NetAct Operations Support System (OSS) and its interfaces with Packet Switched (PS) Core Networks (CN) over the S1 interface. Operation Mediation Subsystem (OMS) is used to aggregate O&M traffic and mediate data format towards the NetAct. OMS is usually located at the NetAct. The LTE Flexi Multiradio BTS functionality is implemented in compliance with the 3GPP interface specification baseline 3GPP Rel-11 March 2013. There may be changes to the final solutions due to the final release definition process and 3GPP's standardization changes. This document covers only Nokia Solutions and Networks LTE RAN level issues and the high level dependencies for the Core Network, WCDMA, GSM system and Mobile Station support. The Flexi Multiradio BTS functionality may not work if the support in one or multiple other network elements, e.g. eNode Bs, UEs, MME, S-GW, eSMLC, MSC, BTS, Node B etc is not provided. The UE dependency is outlined in the SW dependencies field ‘UE’. The other RAT dependencies are outlined in the field ‘dependencies to other RATs’. The core network dependencies to EPC are outlined in the fields ‘MME’ and ‘S-GW’. In the fields ‘BTS Flexi’ for FSMD/E and ‘BTS Flexi 10’ for FSMF family the support of the feature is indicated with release name; blank means not supported. In the field ‘HW requirements’ it will be indicated if the feature requires additionally a specific HW in RAN LTE portfolio. It is left blank if the feature describes a HW item itself or has no specific requirements. The Flexi Multiradio BTS functionality may rely on the activation of other eNode B features. This feature interdependency is outlined in the field ‘interdependencies between Features’. IOTs with other network elements, e.g. eNode Bs, MME, S-GW, eSMLC, MSC, BTS, Node B etc., UEs or applications have to be conducted well in advance in order to ensure the interoperability with other network elements on protocol level. Such testing need to be agreed with NSN IOT department according IOT standard process. 3GPP has not defined the interworking of algorithms, i.e. KPI may depend on multi-vendor scenarios. The actual performance of the feature in field will depend on several external factors e.g. radio condition, antenna configuration, UE location, UE speed, cell load, transport network dimensioning, etc. In ‘SW Sales Information’ the optional Sales Items are indicated with ‘ASW’ (Application SW). ‘ASW NetAct’ refer to Sales Items defined within NetAct. Basic SW items are indicated with ‘BSW’. LTE RAN SW is using SW Asset Monitoring as licensing approach. This document is NON BINDING.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
5/68
Doc number
2 History Summary of changes Version 1.0
Date 2013-11-29
Author LTE PLM
Features added versus last - none -
Features removed versus last - none -
Version 1.0
Changes First Feature Candidate Document version
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
6/68
Doc number
Version 1.0
3 BTS Site Solution 3.1 Site level RF Sharing between WCDMA-GSM-LTE Unique ID: 1556 Short Description: Site level RF Sharing between GSM-WCDMA-LTE. GSM, WCDMA and LTE systems are in the same BTS Site. RF Sharing between GSM-WCDMA and GSM-LTE. No system sharing, own System modules for GSM, WCDMA and LTE. One GSM System module can be used with GSM-WCDMA and GSM-LTE RF sharing. RP3 Synchronization is required between all the system modules. Supported Configurations: LTE FSMF-WCDMA FSME-GSM ESMB/C LTE FSMF-WCDMA FSMF-GSM FSMF Benefits for the Customer: Benefits from Single GSM SM instead of 2 GSM SM GSM System module capacity is 18 or 36 TRX Only one GSM System module is needed for capacity point of view only one system to control from BSC/Netact only one transmission interface towards BSC Smaller site Less power consumption
HW Requirements: Flexi release 3 system Module Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro -
NetAct
-
Licence Control in Network Element Pool license
OMS
MME
SAE GW
-
-
UE
Licence Control Attributes Long-term ON/OFF BTS license
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
7/68
Doc number
Version 1.0
3.2 FXED Flexi RF Module 6TX 1800 Unique ID: 1719 Short Description: FXED Flexi Multiradio RF Module 6TX 1800 MHz has 6 Power Amplifiers enabling it to support one, two or three sectors with up to 60+60 W LTE 2TX MIMO output power at the BTS antenna connectors. HW supports also RF sharing with GSM, and GSM only configurations. Size and visual outlook is similar to the existing Flexi RF Modules. The environmental protection class is IP65. From HW point of view it can be used as powerful one sector RRH with max 4x60 W with 4TX MIMO and 4RX. 4TX MIMO and 4RX are separate SW features. Benefits for the Customer: 6TX 60 W RF Module general benefits: • the most cost and size and weight optimized 3-sector 2TX MIMO BTS site • industry leading RF integration level • 3 sector 2TX MIMO RF in one outdoor IP65 box o ambient temperature -35... +55 C • Smallest size and weight • Smallest power consumption and OPEX • Can be used as feederless site as well with one DC and 1...2 optical cables • 3-sector 2TX div and 2TX MIMO BTS can be build using only one 3-sector RF Module • one 3-sector Module is more cost effective than 3 x RF Head in feederless installations´ • Less weight • Less wind load • 1/3 of DC and 2/3 of optical cabling compared to 3-sector site with Remote RF Heads (RRH) • easier installation • less visual impact • HW prepared to support one sector 4x60 W 4TX MIMO with 4RX Functional Description: FXED supports 3GGP band 3 1800 MHz. With 6 x 60 W output Flexi RF Module, IP65. * iBW minimum of 40MHz DL, and up to 60MHz UL for LTE * iBW minimum of 35MHz DL, and up to 60MHz UL for GSM/Multimode * DL iBW up to 2xpipe iBW for sector, when 2-pipes used for sector · 3 U high with Flexi platform mechanics. Basic LTE Configurations: · 1, 1+1 or 1+1+1 LTE cells @ max 20 MHz LTE bandwidth and 2TX MIMO / 2RX · 8, 20, 40 or 60W 1TX mode per sector (by branch activation SW licenses) · 8+8, 20+20, 40+40 or 60+60 W 2TX mode per sector (by branch activation and MIMO SW licenses) · 1, 2 or 3 sectors max 60 + 60 W 2TX MIMO/2RX · HW prepared for 1 sector 4x60 W 4TX MIMO/4RX
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
8/68
Doc number
Version 1.0
LTE + GSM RF Sharing configurations: * up to 20MHz LTE + 4xGSM per pipe * up to 20MHz LTE 2TX MIMO + 8xGSM (4+4) per sector from 2-pipes GSM Only configurations: * up to 4xGSM per pipe
* up to 8xGSM (4+4) per sector from 2-pipes · At constant ambient temperatures +40C ... +55C and at constant high traffic load, the output power level might be limited to minimum of 40W per TX FXED can be used in Feederless site (optical and DC cable up to 200 m). HW Requirements: no specific HW requirements Interdependencies between Features: . Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW BSW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
-
Licence Control in Network Element -
MME
SAE GW
UE
-
-
3GPP R8 UE capabilities
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
9/68
Doc number
Version 1.0
3.3 FWEA Flexi Zone BTS 1800 (Band 3) Unique ID: 1728 Short Description: A 2x5W Flexi Micro FD-LTE 1800MHz (Band 3) all-in-one access point that supports deployment temperatures from -40C to +55C Benefits for the Customer: A small "zone ready" LTE access point that can be easily deployed within an operators existing network, whether NSN or another vendor's network. Functional Description: This feature request is basically a band spin from the initial Flexi Zone Micro at 2100MHz (BC1) and covered in RA LTE_FC_1659 A 2x5W Flexi Micro LTE all-in-one access point that supports 1800MHz (BC3) Key features include: Technology: LTE / LTE-A Frequency: 1800MHz (BC3) Output Power: 2x5W per Tx path Size: 6.5L / 6.5kg is current +55C 2100MHz Micro so parity would be initial goal until impacts known due to filtering, and/or customer specific requirements. Carrier bandwidth support: Up to 20MHz Carrier support: up to 2C (20Mhz total bandwidth)(future) Antenna Configuration: 2Tx / 2Rx Antenna Options: OMNI stick, support for remote antenna Design should not preclude potential future front mounted sector panel antenna (driven by separate feature once prioritized) VSWR and Tx Monitoring Support Retain same X-y dimension of existing 2600FD solution to reduce impact for future integrated antenna feature TX/RX Filtering: Full Band 3 (co-location requirements may require an externall narrowband filter) Environmental: Outdoor
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
10/68
Doc number
Version 1.0
Synchronization: 1588v2 Freq, (Phase - future), RF-GPS, support for remote antenna Applicable Market Regulatory. China AND Korea are priority Need to be Zone ready for future support Maximum SW reuse from Macro platform HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release RL70 SW Sales Information: BSW/ASW BSW
Flexi Zone Micro LBTS7.0
NetAct
OMS
-
Licence Control in Network Element -
MME
SAE GW
-
-
UE
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
11/68
Doc number
Version 1.0
3.4 Up to 12 optical RF ports for high capacity BTS configurations Unique ID: 1745 Short Description: With this feature all the 4 RF optical ports of the Flexi Multiradio System 10 extension module FBBC become usable for direct connection of RFMs and RRHs. This means that up to 12 optical RF ports can be used to directly connect RFMs or RRHs to the System Module (8 ports if only one FBBC extension module is equipped) Benefits for the Customer: With the availability of up to 12 optical RF interfaces, more radio modules or radio heads can be directly connected to the Flexi Multiradio 10 system module thus avoiding chaining,. This increases the resiliency of BTS configuration and increases the flexibility of the operator in connecting the RF modules to the system module. This is specifically useful in scenarios: •
when RF port is needed to synchronize with other RAT system module for RF sharing
•
when legacy RFMs or RRHs with 3Gbit/s RF ports are used with high bandwidth (15/20MHz).
•
when FSMF shared RP3 / Ethernet port is needed for optical GE transport
Functional Description: The maximum capacity of a BTS is limited by processing performance of the Flexi Multiradio System 10 Module and by the number of radio modules that can be connected to it. The processing performance is described in features LTE1644 and LTE1508. This feature increases the number of optical ports for direct connection of radio modules from 6 to 12 (resp. from 5 to 8 in case only one FBBC is in use): Following connectivity is provided: • • •
FSMF + FBBC: 8 ports (two FSPs) or FSMF + FBBC + FBBC: 12 ports (three FSPs) o Each Flexi System processing module (FSP) provides 4 optical ports o All LTE cells are processed locally on the FSP (FSFM or FBBC) to which the RF modules carrying these cells are connected.
•
FSMF + FBBA/C + FBBC: 9 ports (pooled dual FSP + single FSP) o FSMF + FBBA/C processing capacity is pooled and it provides per default 5 ports for connecting RF modules that are processed on this pool of two FSPs.
Prepared by
Nokia Solutions and Networks LTE RAN o o
Approved by
Date
Page
29.11.2013
12/68
Doc number
Version 1.0
The 2nd FBBC provides additional per default 4 ports. Cells on radio modules connected to them are processed locally on this FBBC. In case the 5 ports are not sufficient for connecting all needed radio modules to the pooled two FSP, one port of 2nd FBBC is switched to that pool. Consequently only 3 ports are left for 2nd FBBC
Please note that for support of RF sharing, one RF port has to be connected to other system module and cannot be used for connection of a radio module. This feature is the base to also additional new BTS configurations. Such new configuration are described in feature LTE1746.
HW Requirements: FSMF plus at least one FBBC Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW BSW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
-
Licence Control in Network Element -
MME
SAE GW
UE
-
-
n/a
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
13/68
Doc number
Version 1.0
3.5 LTE extended configurations up to 6 frequency bands Unique ID: 1746 Short Description:
This feature provides additional LTE configurations utilizing the increased connectivity for radio modules. Up to six frequency bands can be supported by a single BTS and up to 12 radio units can be directly connected to the System Module (with extension modules equipped) Benefits for the Customer: Support of large configurations with up to 6 frequency bands in single BTS and more flexible configurations with regard to cell bandwidth and MIMO type. Functional Description: This feature provides new large BTS configurations. Up to 6 different frequency bands (in a 3 sector 10MHz configuration) are supported. With this feature it also becomes possible to use different MIMO or Rx diversity schemes on different frequency bands. Two different basic modes are available, that will be automatically selected by the System Module based on the cell configuration: • Triple FSP local cell set: • In this mode the System Module is configured as 3 (in case only one FBBC is installed 2) independent processing units. • Each of these processing unit provided 4 RF interface ports and can serve following cell configurations: • o max 6 cells, up to 10MHz with 2Tx/2Rx o single band (up to 6 sectors) or dual band / dual carrier (up to 3 sectors) is supported.
• •
o o
max 3 cells, up to 20 MHz with 2Tx/2Rx single band in up to 3 sectors
o o
max 3 cells, up to 10 MHz with 2Tx/4Rx single band in up to 3 sectors
o o
max 3 cells, up to 10 MHz with 4Tx/4Rx single band in up to 3 sectors
o o
max 4 cells, dual band, dual sector in 2Tx/2Rx 2 * up to 20MHz plus 2 * up to 10MHz
Pooled dual FSP: In this mode, two processing modules on the System Module are pooled. The 2nd FBBC (if equipped) supports additionaly one configuration of FSP local cell set as
Prepared by
Nokia Solutions and Networks LTE RAN
•
Approved by
Date
Page
29.11.2013
14/68
Doc number
Version 1.0
listed above. The pooled dual FSP set provides 6 or 5 RF interface ports (see LTE1745) and supports following cell configurations: o o
max 12 cells, up to 10 MHz, 2Tx/2Rx these can be in up to 4 differend frequency bands
o o
max 6 cells, up to 20 MHz, 2Tx/2Rx single band (up to 6 sectors) or dual band / dual carrier (up to 3 sectors) is supported
o o
max 3 cells, up to 20 MHz with 2Tx/4Rx single band in up to 3 sectors
o o
max 3 cells, up to 20 MHz with 4Tx/4Rx single band in up to 3 sectors
The details regarding supported RFM and RRH types, in different bandwidth, MIMO and Rx diversity combinations are defined in document: Flexi Multiradio and Multiradio 10 BTS LTE Supported Configurations
HW Requirements: Flexi MR10 BTS Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW BSW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
-
Licence Control in Network Element -
MME
SAE GW
UE
-
-
n/a
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
15/68
Doc number
Version 1.0
4 Transmission 4.1 User Layer TCP MSS clamping Unique ID: 1240 Short Description: This feature supports TCP clamping in the user IP layer to prevent IP layer fragmentation and reassembly for TCP sessions. Benefits for the Customer: IP fragmentation AND reassembly in the transport IP layer will be avoided which would have a negative impact on throughput performance otherwise. Functional Description: During the TCP session establishment, UEs negotiate a maximum TCP payload (segment) size (MSS) with their peers for each TCP session. If this value is selected too large, the additional TNL encapsulation (GTP-U/UDP/IP, optionally IPsec) may lead to fragmentation in the transport network. With the TCP MSS Clamping function the eNB modifies the MSS value used in the user TCP session establishment (SYN Packets) according to the configured MTU size of the backhaul link, thus preventing fragmentation in the transport network. This feature does not impact any non-TCP traffic, thus fragmented packets may still be observed in the network, for instance in case of UDP based applications.
HW Requirements: Flexi Release 2 and 3 HW Interdependencies between Features: no feature interdependencies
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
16/68
Doc number
Version 1.0
Dependency to other RATs: RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro LBTS7.0
NetAct
OMS
-
Licence Control in Network Element SW Asset Monitoring
MME
SAE GW
-
-
UE
Licence Control Attributes -
4.2 Sync Hub Direct Forward Unique ID: 1710 Short Description: An improvement in synchronization transfer of 1PPS&ToD signal to provide extremely high accuracy phase and Time synchronization between BTSs at the same site via 1PPS&ToD signal which improve the whole RF sharing solution and other related sync applications. Allow support of Phase and Time synchronization for features like LTE-A eICIC, LTE-A Inter eNB CoMP, DFCA, etc in combination with RF sharing solution. Benefits for the Customer: Operators can get lowest TCO site solution with RF sharing and at the same time be able to exploit the great benefits of following features DFCA OTDOA LTE-A eICIC, Inter eNB CoMP
Operators have the option to use ToP with Phase sync either at GSM or LTE to obtain Phase and Time synchronization for those features Operators get full flexibility in deploying the RF sharing solution, i.e sync role can be differentiated from Radio role,allowing to e.g. use TOP with Phase at a LTE eNB as sync reference even though the eNB is radio slave at the RF sharing.
Better reliability as holdover capability at a Sync Slave is introduced, enabling that a slave module can keep up service with the shared and dedicated RF resources it is using. Functional Description:
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
17/68
Doc number
Version 1.0
Sync Hub Direct Forward mechanism: High Phase and time accuracy between system modules can be provided by SyncOut/SyncIn connection instead of RP3-01 conneciton. Any sync sources could be used as sync input to Sync Hub Master (with exception of sync from RP3-01/CPRI). The Sync Hub Master provides 1PPS&ToD as output to Sync Hub Slaves. If there are multiple Sync Hub Slaves, each sync Hub slave will directly forward 1PPS&ToD to next Sync Hub Slaves in the chain without modification/regeneration. In the event that SyncHub slave lose synchronization input (e.g. fail of SyncHub Master), SyncHub slave can rely on its own holdover tuning algorithm and still stay operational. Sync Hub Direct Foward with RF Sharing: Decoupling of Synchronization function from inter-SMs RP3-01 connection and use Sync Hub Direct Forward as means to provide synchronization for RF sharing Inter SMs RP3-01 connection remains in use for RF sharing topology, communication between system modules, between RF sharing slave and shared RFM. A BTS could have for e.g. both Sync Hub Master role but Radio Slave role. Sync Slave Recovery with RF sharing: Better reliability of Sync Hub Slave thanks to holdover functionality of Sync Hub Slave which was not provided with RP3-01 based RF sharing solution A Radio slave can become a temporary Radio master when the actual Radio master fails LTE specific: In Sync Hub Direct Forward with RF sharing, LTE can support Phase and Time synchronization features such as OTDOA, LTE-A eICIC, CoMP, etc. LTE is recommended to be used as Sync Hub Master for both WCDMA-LTE and LTE-GSM RF sharing solution. The Radio roles however remain the same, i.e. Radio Slave in case of WCDMA-LTE RF sharing and Radio master in case of LTE-GSM RF sharing. In the case of LTE-GSM RF sharing, GSM is able to use DFCA.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
18/68
Doc number
Version 1.0
HW Requirements: FSMF as Synchronization master or slave FSME/D only as Synchronization slave Interdependencies between Features: no feature interdependencies Dependency to other RATs:UTRAN, GSM RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
-
Licence Control in Network Element Trust based
MME
SAE GW
-
-
UE
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
19/68
Doc number
Version 1.0
4.3 Timing over Packet Resilience Unique ID: 610 Short Description: ToP Sync resilience to allow that each ToP Slave can be connected to more than one ToP Master for the sake or reduncdancy. Benefits for the Customer: With this feature, the ToP Slave embedded in the eNodeB will be able to support more than one ToP Master. The alternative ToP Master is selected when the connection to the original ToP Master fails, thus, increasing the reliability of the ToP mechanism as synchronization source. Functional Description: The ToP Slave embedded in NSN eNB supports more than one IP address to be connected to several ToP Masters. The IEEE1588-2008 allows to configure a list of several ToP Master IP addresses. Depending on the priorities configured, the ToP Slave selects the ToP Master with the best Clock to be used. Upon failure of the selected ToP Master, the ToP Slaves connect to the next candiate in the list. This feature is applies only to the frequency synchronization application of Timing over Packet.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
20/68
Doc number
Version 1.0
HW Requirements: no specific HW requirements Interdependencies between Features: LTE134 "Timing over Packet" required. Dependency to other RATs:
RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
LBTS7.0
SW Sales Information: BSW/ASW ASW
Flexi Zone Micro LBTS7.0
NetAct
OMS
-
Licence Control in Network Element SW Asset Monitoring
MME
SAE GW
UE
-
-
n/a
Licence Control Attributes -
4.4 SCTP Multi-homing Unique ID: 648 Short Description: The eNB supports additional functionality with respect to SCTP multi-homing according to RFC4960 for C-plane resilience. Benefits for the Customer: High reliability of C-plane by for example: using different transport path for the associations. High reliability of the C-plane by using multi-homed associations between eNB and MME (using two IP addresses in each end point and so e.g. different transport path). Functional Description: Multi-homed nodes can be reached under several IP addresses. With this feature, the eNB can be configured with two IP addresses for S1/X2 C-plane termination. The feature extends LTE775 "SCTP Multi-homing (MME)" which supports two IP addresses at the MME for S1 Cplane. SCTP (RFC4960) specifies multi-homing for failover (not for load-sharing). C-plane associations become more tolerant against physical interface and network failures if multiple IP addresses are used. Path status and reachability is monitored via SCTP heartbeats.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
21/68
Doc number
Version 1.0
HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:
RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW BSW
Flexi NetAct Zone Micro LBTS7.0 LBTS7.0 -
Licence Control in Network Element -
OMS
MME
SAE GW
-
-
UE
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
22/68
Doc number
Version 1.0
5 Radio Resource Management and Telecom 5.1 LTE:Mobility 5.1.1 Service based mobility trigger Unique ID: 1127 Short Description: The feature allows for a service triggered inter-frequency handover. Benefits for the Customer: VoLTE traffic steering schemes can be deployed with this feature Functional Description: The Flexi Multiradio BTS supports a service based mobility trigger. The operator can configure for VoLTE services target frequency layers either within the default profile or if enabled within the mobility profile for inter-frequency handovers. The establishment of a bearer with QCI1 triggers the UE measurements (event A4) for the pre-defined target layers taking the UE capabilities into account. UEs enter a cell via a handover or RRC connection re-establishment are considered as well for a service based handover. UEs with ongoing measurements for coverage based mobility or load based handovers are not considered for a service based handover. The UE measurements are aborted if the UE does not provide a measurement report within a predefined time. A target cell for a handover preparation is only selected if the UE measurements are above an operator configurable RSRP and RSRQ threshold and the cell is not blacklisted. The cause value 'resource optimization handover' is used for the handover preparation. The target cell uses radio admission control thresholds for new calls in order to decide whether to admit or reject a resource optimization handover request. Periodic handover retries are performed in case that the UE has not provided a A4 measurement report. The retry timer is operator configurable. The following performance counters are supported, e.g. • •
Number of inter frequency resource optimization based handover attempts Number of successful inter-frequency resource optimization based handover completions • Number of inter-frequency resource optimization based handover failures per failure cause • Number of inter frequency resource optimization based handover attempts per neighbor cell relation • Number of successful inter-frequency resource optimization based handover completions per neighbor cell relation • Number of inter-frequency resource optimization based handover failures per failure cause per neighbor cell relation The feature can be enabled / disabled per eNode B and its subordinated cells by O AND M setting.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
23/68
Doc number
Version 1.0
HW Requirements: no specific HW requirements Interdependencies between Features: LTE55 needs to be enabled. LTE1060 needs to be enabled if a FDD/TDD handover is needed. Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE Zone GW Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x 3GPP R8 UE capabilities SW Sales Information: BSW/ASW ASW
Licence Control in Network Element SW Asset Monitoring
Licence Control Attributes -
5.1.2 Intra-frequency load balancing Unique ID: 1140 Short Description: Load balancing for cell deployed on the same frequency layer. Benefits for the Customer: Avoiding of overload situations for specific cells by steering the traffic into less loaded cells at same frequency layer. Functional Description: The Flexi Multiradio BTS supports intra-frequency load balancing. The pair wise load balancing is supported for the following cell scenarios: • • •
macro - macro, macro - micro/pico (non eICIC operation) or macro/pico - micro/pico
The related cells can be located either in the same eNode B or in different eNode B connected via X2. The load balancing is based on the downlink composite available capacity (CAC). There are two modes for the downlink CAC calculation are supported: • •
only non GBR load non GBR, GBR and PDCCH load
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
24/68
Doc number
Version 1.0
The procedure starts once the downlink CAC in a cell is below an operator configurable threshold. The X2AP: Resource Status Request message with periodic reporting is sent to all eNode Bs hosting neighbor cells contained in a load balancing white list. The load balancing white list is dynamically updated by the eNode B based on an outgoing handover statistic. The maximum allowed number of neighbor cells considered for load balancing as well as the reporting period of the resource status response is operator configurable in order to control the X2 signaling load. The requested eNode Bs send the information on the downlink CAC with the X2AP: Resource Status Update message. eNode B internal messages are used for neighbor cells located in the same eNode B as the source cell. The source cell uses the reported CAC, the own CAC, the current delta CIO settings and the outbound handover success rate in order to select suitable neighbor cells to offload the traffic by shrinking the source cell. A new delta CIOs is calculated by the source cell and proposed to the selected neighbor cell via the X2AP: Mobility Change Request message. Once the mobility change procedure has been successfully finished the new delta CIO is applied for • • • •
new UEs entering the RRC Connected state, UEs enter the cell via a handover, UEs after a successful RRC Connection Reestablishment and UEs in RRC Connected UEs via a bulk RRC Connection Reconfiguration
The chosen downlink CAC calculation mode is as well considered when informing UEs, i.e. the new delta is used • •
only UEs with established non GBR bearers or all UEs.
The load balancing is stopped once the downlink CAC is above an operator configurable threshold. The following performance counters are supported, e.g. • • •
histogram of composite available capacity per cell, intra-frequency handover subcounters for UEs with a delta CIO 0 and RLF subcounters for UEs with a delta CIO 0.
The feature can be enabled / disabled per eNode B by O&M settings. HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE Zone GW Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x 3GPP R8 mandatory
Prepared by
Nokia Solutions and Networks LTE RAN
SW Sales Information: BSW/ASW ASW
Approved by
Date
Page
29.11.2013
25/68
Doc number
Version 1.0
Licence Control in Network Element SW Asset Monitoring
Licence Control Attributes -
5.1.3 RLF triggered handover Unique ID: 1617 Short Description: An additional intra LTE handover trigger is introduced. Benefits for the Customer: The RRC connection re-establishment success rate is improved which leads to a reduced VoLTE call drop rate. Functional Description: The Flexi Multiradio BTS supports a radio link failure triggered intra LTE handover. The procedure is triggered by an RRC:RRC Connection Re-establishment Request message at an unprepared cell for UEs entering the cell with its serving/source UE-Identity. The following unprepared cell scenarios are supported: • unprepared cell in an unprepared X2 connected eNode B • unprepared cell in a X2 connected target eNode B • unprepared cell in a source/serving eNode B In case of requesting an unprepared cell in an unprepared eNode B or the target eNode B: The requested eNode B sends an X2AP:RLF Indication message to the serving/source eNode B and waits a certain time for a X2AP:Handover Request. In case that the requested eNode B receives the X2AP:Handover Request message in time, it treats this as a normal handover, becomes a target eNode B, and applies admission control for a timecritical handover. If the handover preparation was admitted, the eNode B resumes the pending RRC Connection reestablishment procedures like a usual (LTE735) RRC connection reestablishment to target e Node B during X2 handover with source UE-Identity (including data forwarding). If the requested eNode B does not receive an X2AP:Handover Request message in time or in case that admission control rejects the handover, a RRC:RRC Connection Reestablishment Rejection is send back to the UE. The X2AP:RLF Indication message is used at the serving eNode B as an additional trigger to start an intra-LTE handover, if possible (in particular the current state of the UE context may inhibit a handover). Ongoing handovers are cancelled according to the reported UE identity. The information contained in RLF Indication message is used to select the UE, the target eNode and the target cell for the handover. The handover preparation is initiated after the
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
26/68
Doc number
Version 1.0
normal handover checks have been performed and the serving eNode B becomes source eNode B. There is no RRC signalling initiated at the source eNode B for this type of handover. The requested eNodeB immediately rejects the RRC connection reestablishment request and the serving/source eNodeB does not trigger a handover preparation, if the reestablishmentCause is set to Reconfiguration Failure. The operator may enable/disable the requested eNode B part and the failure eNode B part independently. This is possible with respect to each neighbour eNode B. In case of requesting an unprepared cell in a source/serving eNodeB: The RRC Connection reestablishment request is accepted, if an according intra eNode B handover to the requested cell would be admitted. It happens like a usual (LTE735) RRC connection reestablishment to target cell during intra eNode B handover with source UEIdentity (including data forwarding). This functionallity is always enabled. The following performance counters are introduced for this functionality, e.g. • number of handover preparations due to RLF (at source/serving cell • number of handover successful handover preparations due to RLF • number of RRC successful connection re-establishments in unprepared cells HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE GW Zone Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x x 3GPP R8 mandatory SW Sales Information: BSW/ASW ASW
Licence Control in Network Element SW Asset Monitoring
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
27/68
Doc number
Version 1.0
5.1.4 Serving PLMN ID change during X2 based handover Unique ID: 1731 Short Description: Change of the serving PLMN ID during X2 handover. Benefits for the Customer: Inter PLMN mobility with HRL in X2 handover Functional Description: The Flexi Multiradio BTS supports following Handover Restriction List (HRL) functionalities in X2 handover. if HRL was available in eNodeB during X2 handover, the eNodeB shall determine if a target cell allowed for handover or not with HRL information, which contains the serving PLMN, equivalent PLMNs, and roaming area or access restrictions. In case of the UE serving PLMN ID is not supported in the selected target cell of the handover, source eNodeB shall exchange the 'serving PLMN' in the Handover Restriction List IE with the PLMN ID from the 'equivalent PLMNs' list which is supported in the target cell, before including it into the X2AP: HANDOVER REQUEST message. If the target eNodeB receives a HANDOVER REQUEST message containing the Handover Restriction List IE, target eNodeB selects the IE "serving PLMN" within the Handover Restriction List as the UE serving PLMN ID. If the UE serving PLMN ID is supported by the target cell the handover continues. If the UE serving PLMN ID is not supported by the target cell, the eNodeB rejects the procedure using the HANDOVER PREPARATION FAILURE message. A Handover Restriction List is stored in eNodeB when it is included in initially received or updated messages of S1AP INITIAL CONTEXT SETUP, S1AP NAS DOWNLINK TRANSPORT, S1AP HANDOVER REQUESTor X2AP HANDOVER REQUEST of a previous handover. If the eNB receives the Handover Restriction List, it shall overwrite previously received HRL information. eNodeB shall not change serving PLMN ID during X2 handover if no HRL was available. HW Requirements: no specific HW requirements Interdependencies between Features: Related X2 mobility functionality needs to be enabled, e.g. LTE53, LTE55 or LTE1060. Dependency to other RATs:No dependency RL Software Dependencies: LTE BTS BTS Flexi Flexi 10 Release
RL70
-
LBTS7.0
Flexi Zone Micro LBTS7.0
NetAct
x
OMS
MME
SAE GW
UE
-
-
3GPP R8 mandatory
Prepared by
Nokia Solutions and Networks LTE RAN
SW Sales Information: BSW/ASW BSW
Approved by
Date
Page
29.11.2013
28/68
Doc number
Version 1.0
Licence Control in Network Element -
Licence Control Attributes -
5.2 LTE:Coverage, capacity and peak rates 5.2.1 eICIC - macro Unique ID: 1113 Short Description: Time domain eICIC is introduced in order to improve the interference handling in co-channel deployment scenarios. Benefits for the Customer: Advanced interference handling allowing to improve end-user experience in macro micro/pico network deployments. Functional Description: The Flexi Multiradio BTS supports eICIC and FeICIC for macro - micro/pico co-channel deployments. The basic idea of the feature is to reduced the inter-cell interference from macro cells to micro cells by introducing so-called 'almost blank subframes' (ABS) in the macro cell. The amount of ABS is dynamically adapted by the macro cell based on the load condition. The macro cell provides further on a dynamic control of the cell range extension (CRE) for the different micro/pico cells. The feature takes non-eICIC, eICIC and FeICIC capable UEs into account. The following channels/signals are transmitted from the macro eNode B also in ABS TTIs: • • • • • • • • •
common reference symbols (CRS), positioning reference symbols (PRS), if configured, primary synchronisation channel (PSS), secondary synchronisation channel (SSS), PCFICH, PHICH, SIB1 on PDSCH, PDCCH in case SIB1 is transmitted and PBCH,
but no user data related transmission on PDCCH and PDSCH.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
29/68
Doc number
Version 1.0
Pre-condition for the eICIC/FeICIC operation is that the macro cell and the related micro/pico cells are SFN aligned. The SFN alignment is based on a common starting point for SFN=0 at GPS epoch. Two eICIC operating modes are supported: • •
Non GBR mode Non GBR + GBR mode
The eICIC/FeICIC partnership establishment between a macro and a micro/pico cell is done by using X2AP:Load Information messages. The periodic reporting of the CAC, PRB usage and ABS status from eICIC/FeICIC partners using the Radio Status Resource procedure is initiated once at least one eICIC/FeICIC partnerships is established and stopped if no eICIC/FeICIC partnerships exist. An X2 outage or X2 setup will as well lead to a release of the eICIC/FeICIC partnership. The macro cell uses its own CAC as well as the reported CAC and the reported ABS status from the eICIC/FeICIC partners to decide about the increase/decrease of the ABS and about the increase/decrease of the cell range extension for individual eICIC/FeICIC partner cells. The dynamic cell range extension can be enabled/disabled by the operator. The macro cell informs all eICIC/FeICIC partner cells via X2AP:Load Information message about the applied ABS pattern. The ABS patterns are pre-configured. The frequency of ABS changes is controlled by an operator configurable prohibit timer. The applied ABS pattern is considered for the CAC calculation as well by radio admission control of the macro cell. The macro cell controls as well the cell range extension for each eICIC/FeICIC partner by dynamically changing the CIO values via the Mobility Change procedure. The maximum allowed delta CIO is operator configurable. Different offsets are applied in addition to the delta CIO for non eICIC UE, eICIC UEs and FeICIC UEs. The delta CIOs are only applied for UEs of the related operating mode, i.e. only UEs with established non GBR bearers or all UEs with established bearers, with a dedicated RRC connection re-configuration message or with the next regular RRC connection reconfiguration message. The establishment or release of a GBR bearer may lead to the change of the applied CIOs in the non GBR operating mode. The applied ABS pattern is considered by • •
the CAC calculation and radio admission control.
The following performance counters are provided, e.g. • • •
ABS distribution delta CIO distribution per neighbor cell dedicated intra-frequency mobility counters for UEs with a delta CIO
The feature can be enabled per eNode B by O&M setting. HW Requirements: no specific HW requirements Interdependencies between Features: eICIC is not supported in combination with
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
30/68
Doc number
Version 1.0
LTE116 3 MHz cell bandwidth LTE117 1.4 MHz cell bandwidth LTE1382 Cell Resource Groups LTE80 or LTE891 needs to be enabled.
Dependency to other RATs RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE Zone GW Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x 3GPP R10 UE capabilities 3GPP R11 UE capabilities SW Sales Information: BSW/ASW ASW
Licence Control in Network Element Pool license
Licence Control Attributes Long-term ON/OFF BTS license
5.2.2 eICIC - micro Unique ID: 1496 Short Description: Time domain eICIC is introduced in order to improve the interference handling in co-channel deployment scenarios Benefits for the Customer: Advanced interference handling allowing to improve end-user experience in macro micro/pico network deployments. Functional Description: The FlexiZone Micro BTS supports eICIC and FeICIC for macro - micro/pico co-channel deployments. The basic idea of the feature is to reduced the inter-cell interference from macro cells to micro cells by introducing so-called 'almost blank subframes' (ABS) in the macro cell. The amount of ABS is dynamically adapted by the macro cell based on the load condition. The macro cell provides further on a dynamic control of the cell range extension (CRE) for the
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
31/68
Doc number
Version 1.0
different micro/pico cells. The feature takes non-eICIC, eICIC and FeICIC capable UEs into account. Pre-condition for the eICIC/FeICIC operation is that the macro cell and the related micro/pico cells are SFN aligned. The SFN alignment is based on a common starting point for SFN=0 at GPS epoch. Two eICIC/FeICIC operating modes are supported: • •
Non GBR mode Non GBR + GBR mode
The eICIC/FeICIC partnership establishment between a macro and a micro/pico cell is done by using X2AP:Load Information messages. Only one partnership is established per micro/pico cell. The micro/pico cell supports a periodic reporting of the CAC, PRB usage and ABS status towards the eICIC/FeICIC partner macro cell with the X2AP:Resource Status Update message. The information about the applied ABS pattern in the macro eNode B is signaled to the micro/pico eNode B via the X2AP:Load Information message. The ABS pattern is used for the scheduling within the micro/pico eNode B. Cell edge users are preferably scheduled in ABS subframes. The micro/pico cell supports dedicated control loops for • • • •
PUSCH link adaptation, PDCCH link adaptation, PDSCH link adaptation and MIMO control
for ABS and non-ABS subframes. Dedicated periodic CQI/PMI reporting patterns are applied for eICIC/FeICIC capable UEs. The micro/pico cell supports as well the mobility change procedure initiated by the eICIC/FeICIC partner macro cell in order to dynamically change the cell range extension. The maximum allowed delta CIO is operator configurable. Different offsets are applied in addition to the delta CIO for non eICIC UE, eICIC UEs and FeICIC UEs. The delta CIOs are only applied for UEs of the related operating mode, i.e. only UEs with established non GBR bearers or all UEs with established bearers, with a dedicated RRC connection reconfiguration message or with the next regular RRC connection reconfiguration message. The establishment or release of a GBR bearer may lead to the change of the applied CIOs in the non GBR operating mode. The following performance counters are provided, e.g. • • • •
UL/DL PRB usage in ABS subframes, UL/DL PRB usage in non-ABS subframes and CAC distribution dedicated intra-frequency mobility counters for UEs with a delta CIO
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
32/68
Doc number
Version 1.0
The feature can be enabled/disabled per cell by O&M setting.
HW Requirements: no specific HW requirements Interdependencies between Features: eICIC is not supported in combination with the following features: LTE116 3 MHZ cell bandwidth and LTE117 1.4 MHz cell bandwidth. LTE1382 Cell resource groups LTE907 TTI bundling LTE616 Dynamic PDCCH adaptationLTE80 or LTE891 need to be enabled.
Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release RL70 -
SW Sales Information: BSW/ASW ASW
Flexi Zone Micro LBTS7.0
NetAct
OMS
x
Licence Control in Network Element SW Asset Monitoring
MME
SAE GW
UE
-
-
3GPP R10 UE capabilities 3GPP R11 UE capabilities
Licence Control Attributes -
5.2.3 Uplink intra eNode B CoMP 4RX Unique ID: 1691 Short Description: The uplink intra eNode B CoMP (Co-ordinated Multipoint) functionality improves the cell capacity and the cell edge performance by taking uplink information from neighbor cells into account. Benefits for the Customer: The uplink intra eNode B CoMP provides up to 20% cell edge improvement compared to a 4RX MRC receiver. Functional Description:
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
33/68
Doc number
Version 1.0
The Flexi Multiradio BTS supports uplink intra eNode B CoMP. The uplink intra eNode B CoMP functionality is applied for cells with 4RX paths. The eNode B selects automatically per UE and per TTI the most suitable neighbor cell out of the CoMP candidate set. The selection of the neighbor cell for the joint reception is based on uplink SINR measurement before combining. The joint reception is applied for the PUSCH. The CoMP candidate set, i.e. which neighbor cell shall be considered for the selection, is operator configurable. The feature can be enabled / disabled per eNode B by O AND M setting.
HW Requirements: no specific HW requirements Interdependencies between Features: LTE980 IRC for 4 RX paths needs to be enabled. The feature is not supported in combination with LTE614 distributed sites in case the RRHs / RF modules more than 1km away from each other, LTE48 High speed users, LTE117 Cell bandwidth: 1.4 MHz, LTE116 Cell bandwidth: 3 MHz LTE115 Cell bandwidth: 5 MHz (TD LTE) LTE114 Cell bandwdith: 10 MHz (TD LTE) LTE112 Cell bandwidth: 15 MHz (TD LTE) LTE1542 FDD Supercell. LTE993 Cell combining (TD LTE specific)
Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
x
Licence Control in Network Element SW Asset Monitoring
MME
SAE GW
UE
-
-
3GPP R8 mandatory
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
34/68
Doc number
Version 1.0
5.2.4 Liquid Cell Unique ID: 1709 Short Description: The Liquid Cell functionality allows for a higher downlink air interface resource utilisation, Benefits for the Customer: The Liquid Cell functionality allows to re-use same PRBs in downlink for different UEs. Functional Description: The Flexi Multiradio BTS supports Liquid Cell configurations. The Liquid Cell is an extension of the Super Cell concept for TM9 (Transmission Mode) capable UEs. Two spatially separated 2TX/2RX transmission/reception points are used to build a Liquid Cell. The Liquid Cell functionality allows to flexibly select the downlink antenna transmission point serving a TM9 capable UE. The UE is configured with the TM9 once the UE capabilites are known to the eNode B via a RRC Connection Reconfiguration message. Liquid Cell is only applied on the PCell is case of Carrier Aggregation. The TM9 UE might be served by single transmission point or by two transmission points. The selection is based on filtered uplink eNode B measurements. The selection thresholds are operator configurable. The change of the transmission point is signaled to a UE via a RRC Connection Reconfiguration message. Only the selected transmission point provides dedicated reference symbols in addition to the common control signals for the UE whereas the other transmission points provide only common signals. Downlink multi-user MIMO is applied for UEs assigned to different transmission points. The double usage of PRBs resources in case of multi-user MIMO is considered by the radio admission control as well as by the CAC calculation. The following performance counters are supported to track the performance: • average number of TM9 capable UEs served by one transmission point • average number of TM9 capable UEs served by two transmission points • average number of double assigned downlink PRBs The functionality can be enabled / disabled per eNode B.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
35/68
Doc number
Version 1.0
HW Requirements: LTE1709 works only with 2TX RRHs. FSMF and FSMF+FBBA system module setups are supported. Interdependencies between Features: LTE1542 needs to be enabled. The same feature dependencies as for LTE1542 are applied. The following features can not be enabled together with this functionality: LTE115 5 MHz cell bandwidth LTE116 3 MHz cell bandwidth LTE117 1.4 MHz cell bandwidth LTE1402 UL CoMP LTE1691 Uplink Intra eNode B CoMP 4RX Liquid Cells must be enabled on the PCell and the SCell in case of Carrier Aggregation. Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
x
Licence Control in Network Element SW Asset Monitoring
MME
SAE GW
UE
-
-
3GPP R10 UE capabilities
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
36/68
Doc number
Version 1.0
5.2.5 Downlink interference shaping Unique ID: 1800 Short Description: The downlink interference shaping functionality enforces a more stable intercell interference. Benefits for the Customer: Improved downlink performance in unbalanced cell load scenarios. Functional Description: The Flexi Multiradio BTS supports a downlink intercell interference shaping functionality for fractionally loaded cells. The eNode B assigns all UE specific PDSCH resources to preferred RBGs (resource block group). Downlink channel aware scheduling is applied for the resource assignment. The number of the preferred RBGs is adapted based on the cell load. An optional minimum number of non-preferred RBGs can be configured, for example in micro cells to leave clear spectrum for macros. The location of the preferred RBGs is co-ordinated between cells (intra and inter eNode B cells) without the need of a X2 interface. The algorithm is automatically enabled / disabled depending on the system load. The following performance counter is supported, e.g. • number of TTIs where downlink traffic shaping is applied. The functionality can be enabled / disabled per cell by O AND M settings. HW Requirements: no specific HW requirements Interdependencies between Features: The feature is not supported in combination with LTE116 - Cell bandwidth: 3 MHz LTE117 - Cell bandwidth: 1.4 MHz LTE1705 - PDSCH blanking LTE1382 - Cell resource groups Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE Zone GW Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x 3GPP R8 mandatory SW Sales Information: BSW/ASW ASW
Licence Control in Network Element SW Asset Monitoring
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
37/68
Doc number
Version 1.0
5.3 LTE:QoS, services and end user experience 5.3.1 Nominal Bitrate for non-GBR bearers Unique ID: 1042 Short Description: Introduction of a Nominal Bitrate for non GBR bearers Benefits for the Customer: Enhanced QoS control for best effort services.
Functional Description: The Flexi Multiradio BTS supports an additional operator configurable QoS parameter 'Nominal Bitrate' for the scheduling of non-GBR radio bearers. Separate settings in uplink and downlink can be configured per each non-GBR QCI. A UE Nominal Bitrate is derived by taking the sum of the NBR values of the UE bearers. The NBR range is up to 2 Mbps. Nominal Bitrate is not considered at admission control while GBR is. The scheduler always tries to fulfill any GBR commitments first. Any remaining capacity is used to satisfy the requested NBR bearers. If there is still capacity left, it is distributed among all bearers (including GBR and NBR bearers) according to scheduling weights. Bearers can therefore also exceed their GBR or NBR values. If the scheduler is not able to fulfill all of the NBR requests due to overload, the lowest priority QCI bearer(s) will not get the requested NBR, while all other bearers still get full NBR. After fulfilling the NBR requests for all bearers with the high QCI priorities, if the scheduler is able to fulfill the NBR requests for some but not all bearers in the lower QCI priority, the bearer consuming most PRB resources will not get the requested NBR. In the uplink direction, strict enforcement of bearer prioritization rules in overload is not applied since UE requests for uplink data transmissions are at a granularity of an LCG as opposed to a bearer. Unlike GBR bearers, NBR bearers will not be torn down when the NBR cannot be met. Note that in the uplink, a UE with a high priority NBR bearer may be power limited and therefore may not be able to achieve its NBR. Whereas a UE with a lower priority NBR bearer may not be power limited and may be able to achieve its NBR with the resources remaining after the power limited UE is scheduled. In addition, TTI bundled UEs are not considered for NBR allocations. Operator configurable parameter sets a maximum value for the total GBR and NBR resources allocated in the cell. The bearer specific split of the uplink resources for an individual UE is controlled by the QCI priority and the prioritized bitrate values which will be set equal to the uplink QCI NBR values. The bearer specific downlink resource split for an individual bearer follows the QCI priority and the downlink QCI NBR. The cell throughput might be degraded with the introduction of the Nominal Bitrate as the scheduler needs to fulfill the NBR constrains. The higher the GBR and NBR values used, the
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
38/68
Doc number
Version 1.0
higher the cell throughput degradation that is possible. The following performance counters are supported: • • • •
Average number of EPS bearers with configured NBR in DL Average number of EPS bearers with configured NBR in UL Average number of EPS bearers not reaching NBR in DL due to overload Average number of EPS bearers not reaching NBR in UL due to overload
The counters are calculated based on regularly taken samples. The feature can be activated / deactivated per cell by O&M setting. HW Requirements: no specific HW requirements Interdependencies between Features: LTE9 needs to be enabled. LTE496 needs to be enabled. Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE Zone GW Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x 3GPP R8 mandatory SW Sales Information: BSW/ASW ASW
Licence Control in Network Element SW Asset Monitoring
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
39/68
Doc number
Version 1.0
5.3.2 Extended VoLTE talk time Unique ID: 1406 Short Description: The UE power consumption for VoLTE calls is improved by aligning the DRX on duration time with the scheduling request timing Benefits for the Customer: The UE power consumption during VoLTE calls is reduced. Functional Description: The Flexi Multiradio BTS applies automatically the following changes with the establishment of a bearer with QCI 1: • SRS is deconfigured (FDD only), • the Scell for carrier aggregation is deconfigured and • an alignment of the scheduling request (SR) timing with the DRX 'ON' timing is applied in case that sufficient PUCCH resources are available. Dedicated uplink and downlink target BLERs as well as dedicated number of uplink and downlink HARQ retransmissions are applied in case that GBR bearers (QCI=1 only) are established. The feature can be enabled / disabled per cell by O AND M. HW Requirements: no specific HW requirements Interdependencies between Features: LTE42 and LTE10 need to be enabled. LTE46 needs to be enabled for SRS support. LTE1089 or LTE1332 needs to be eanbled for carrier aggregation support. Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE Zone GW Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x 3GPP R8 UE capabilities SW Sales Information: BSW/ASW ASW
Licence Control in Network Element SW Asset Monitoring
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
40/68
Doc number
Version 1.0
5.3.3 Carrier aggregation for multi-carrier eNode Bs Unique ID: 1562 Short Description: Multiple overlapping 2 cell carrier aggregation combinations are supported simultaneously per sector. Benefits for the Customer: A flexible selection of a Scell out of a Scell candidate set is supported. Functional Description: The Flexi Multiradio BTS supports a carrier aggregation cell pool size of three. The following carrier aggregation cell pools (always 2RX/2TX if not stated otherwise) can be configured: • 3 x 5/10 MHz cells • 2 x 5/10 MHz cells + 1 x 15/20 MHz cell • 1 x 5/10 MHz cell + 2 x 15/20 MHz cells • 3 x 15/20 MHz cells Instead of a 15/20 MHz 2RX cell a 5/10 MHz 4 RX cell can be configured. The configuration of a Scell out of the carrier aggregation pool is done per UE considering the UE capabilites and the load of the Scell. The functionality can be enabled / disabled per eNode B by O AND M settings. HW Requirements: no specific HW requirements Interdependencies between Features: Basic carrier aggregation functionality needs to be enabled: FDD LTE: LTE1089 or LTE1089 + LTE1332. TDD LTE: LTE1558+LTE1830 Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro -
Net Act
OMS
x
Licence Control in Network Element SW Asset Monitoring
MME
SAE GW
UE
-
-
3GPP R10 UE capabilities 3GPP R11 UE capabilities 3GPP R12 UE capabilities
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
41/68
Doc number
Version 1.0
5.4 LTE:Basic LTE call handling and interworking 5.4.1 MORAN for two operators Unique ID: 1126 Short Description: The Flexi Multiradio BTS can be connected to the Evolved Packet Core (EPC) of two different operators. Benefits for the Customer: Two operators are able to share the resources of one Flexi Multiradio BTS. Functional Description: The Flexi Multiradio BTS supports Multi-Operator Radio Access Network (MORAN) for two operators. The eNode B needs to be configured with sufficient cells, e.g. 6 cells in order to support 3 cells per operator. The RF modules might be shared if the two cells fit into the supported bandwidth of a RF module otherwise dedicated RF modules per operator are needed. The system module is shared by the two operators. The PLMN IDs of each operator are broadcasted with the SIB1 in the cells belonging to the operator. All features enabled on a eNode B level are available for both operators. The eNode B provides one M-interface towards iOMS / NetAct. The MORAN functionality can be enabled / disabled per eNode B by O&M settings. HW Requirements: The eNode B needs to be configured with 6 cells. Interdependencies between Features: LTE505 needs to be enabled. Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
x
Licence Control in Network Element SW Asset Monitoring
MME
SAE GW
UE
-
-
3GPP R8 mandatory
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
42/68
Doc number
Version 1.0
6 Operability 6.1 Network Monitoring and Maintenance 6.1.1 MDT - UE measurement logs Unique ID: 1049 Short Description: The eNode B supports the configuration and the retrieval of UE measurement logs. Benefits for the Customer: The UE measurement log function can be used to minimize the drive test effort. Functional Description: The Flexi Multiradio BTS supports the handling of UE measurement logs. The feature comprises of • •
configuration of UE measurement logs and retrieval of UE measurement logs.
Content of UE measurement log: The UE measurement logs contain the following information: • • • • •
location info (GNSS information is optional for the UE) time stamp serving cell ID serving cell measurements (RSRP, RSRQ) neighbor cell measurements (RSRP, RSRQ, RSCP, Ec/N0, RxLev,...)
The UE collects the measurement data during RRC IDLE and stores is up to 48 hours. The maximum log size is 520 entries. The support of this functionality is optional for 3GPP R10 UEs. The configuration of UE measurement logs and the retrieval of measurement logs is applied only for UEs with related UE capabilities and with according settings of the IE 'Management based MDT allowed' in case of cell trace or UEs selected by the MME in case of subscriber trace. The IE 'Management based MDT allowed' is received either via S1 and X2, e.g. at initial UE context setup or during handover. The IE is forwarded during X2 handover. Configuration of UE measurement logs UE measurement logs are configured for UEs in RRC CONNECTED via a dedicated RRC:LoggedMeasurementsConfiguration message. The configuration of UE measurement logs is done either
Prepared by
Nokia Solutions and Networks LTE RAN • •
Approved by
Date
Page
29.11.2013
43/68
Doc number
Version 1.0
for UEs with the related capabilities or can be restricted to only those UEs supporting location information in case of cell trace.
The area scope for which logged MDT in combination with cell trace shall be applied can be either, e.g. : • • • • •
a list of up to 8 TACs, a list of up to 32 cells, all cells, no cell (switch off) or all neighbor cells.
The logging duration and interval for logged MDT is operator configurable per cell in case of cell trace. Configuration parameters provided via the S1AP interface are used instead in case of subscriber trace. Retrieval of UE measurement logs The Flexi Multiradio BTS retrieves the UE measurement logs automatically once the UE changes from RRC IDLE to RRC CONNECTED with the RRC:UEInformationRequest message. The eNode B considers for this procedure only those UEs which are traced and which have indicated with the • • • •
RRC:RRCConnectionSetupComplete, RRC:RRCReestablishmentComplete, RRC:RRCReconfigurationResponse or RRC:UEInformationResponse
message that measurement data is available. The retrieved information are included to the trace records for cell trace or subscriber trace. The feature can be activated per eNode B by O&M setting.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
44/68
Doc number
Version 1.0
HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs: RL Software Dependencies: BTS LTE BTS Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
-
Licence Control in Network Element Pool license
MME
SAE GW
UE
-
-
3GPP R10 UE capabilities
Licence Control Attributes Long-term ON/OFF BTS license
6.1.2 Remote RF-diagnostics for Flexi Multiradio BTS Unique ID: 1634 Short Description: This feature introduces dedicated test procedures for testing a RF-unit (RF-module, Remote Radio Head) that can be triggered by Network Management System (NetAct, BTS Site Manager) The following test measurements are supported: Downlink measurements •
Total Tx Transmit Power (power that is transmitted on the antenna connector)
•
Expected Transmit Power (based on Digital Input Power and gain)
•
VSWR - Need actual VSWR Ratio
Uplink measurements •
Received Total Wideband Power
•
Need value in mW absolute value that is corrected via calibration factor for each given AxC
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
45/68
Doc number
Version 1.0
Benefits for the Customer: Improved testability of RF-equipment without requiring site visit. Functional Description: The following test measurements are implemented at NetAct and BTS Site Manager (BTSSM) for testing a RF-unit. Downlink Test Requirements for each antenna: • •
Total Transmit Tx Power Read the actual power being transmitted out of the antenna with accuracy requirements
• • ±2.0 dB -30C to +50C • ±1.5 dB 15C to 35C • • Expected Transmit Power - Based on Digital Input power and set gain • • VSWR - Need actual VSWR Ratio Uplink Test Requirements: • Received Total Wideband Power - Need value in mW absolute value that is corrected via calibration factor for each given AxC An operator is able to trigger those test measurements on demand. Use case: The operator (NetAct operator or site technician) is able to define parameters/criterias in order to judge if a test passes or fails the required critera. After triggering the test measurements at NetAct/BTSSM, Flexi Multiradio BTS performs automatically these measurements and replies back with the test results including passed/fail status for each triggered test. The tests might be modeled as objects comparable to 3GPP TS32.322 ("test object"). The operator is able to set some parameters of these test objects to manage the tests, i.e. to set parameters of the test(s), to start the execution of the tests, and in future maybe even to schedule the execution of the test(s) within the Flexi Multiradio BTS. The Flexi Multiradio BTS will report the results of the test(s) in "set-by-system" parameters of these test objects. These test objects shall be handled by the CM fragment like any other object. The operator has to prepare, download, and activate a corresponding plan to trigger the tests. The operator shall have the possibility to schedule at NetAct the activation of these plans. Once the Flexi Multiradio BTS has performed the tests, the Flexi Multiradio BTS shall fill the corresponding parameters of the test object with the results. The Flexi Multiradio BTS will send the results as CCN to NetAct/BTSSM. A later upload of the configuration to NetAct/BTSSM will contain the corresponding parameter values of the test objects too. If, due to its size a result of a test must be reported as file, the Flexi Multiradio BTS shall set a file reference into a parameter of the test object. Flexi Multiradio BTS shall provide the file
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
46/68
Doc number
Version 1.0
that NetAct/BTSSM shall upload by re-using existing mechanisms (e.g. from LTE1099 or PM data).
HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW ASW
LBTS7.0
Flexi Zone Micro LBTS7.0
NetAct
-
Licence Control in Network Element Pool license
OMS
MME
SAE GW
UE
-
-
n/a
Licence Control Attributes Long-term ON/OFF BTS license
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
47/68
Doc number
Version 1.0
6.2 Configuration Management 6.2.1 Neighbor Relation Robustness Unique ID: 1685 Short Description: This feature offers enhancements for the maintenance of the LTE neighbor relations with 1) PCI re-validation and 2) Autonomous Neighbor Relation Removal Benefits for the Customer: Neighbor relations learned autonomously in the network might not be valid anymore after some time, as they were at the time of new learning. The network setup might have changed, so that other relations are used more often. With the enhancements in this feature the neighbor relations are maintained autonomously without the need of manual operator intervention.
Functional Description: Following features are added for the neighbor relation management which offer a more robust handling of the neighbor relations resp. support the maintainance of those.
1) PCI re-validation A PCI at a given carrier frequency is considered to be valid when the identity (ECGI) could be proven via UE measurements. As networks do evolve over the time, PCIs and carrier frequencies of resolved neighbor relations might get invalid in a way that other cells with same PCI and carrier frequency, but different ECGI are valid neighbors to the eNB cell.
PCI re-validation helps to handle "failure" situations in the network * in which the operator was changing PCI values of cells and this information was somehow not provided to their neighbors. * in which PCIs with different ECGI can still be seen from one cell e.g. due to network extensions. The re-validation of PCI checks and re-confirms if the known ECGI value still applies to the PCI and carrier frequency of a given neighbor relation.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
48/68
Doc number
Version 1.0
If the value can be confirmed, the PCI, as well as the corresponding neighbor relation, is judged as re-validated. If the newly measured value is different to the one before the eNB updates the ECGI value associated with this PCI.
The PCI re-validation will be triggered when several consecutive handover failures for a PCI is detected in eNB. A frequent toggling of PCI re-assignments is avoided. The PCI re-validation function can be steered by operator via appropriate parameter settings, as e.g. number of consecutive handover failure, validation timing, ... The PCI re-validation will not solve PCI collisions or confusions, but operator will be able to detect this situation and to take corresponding actions. The re-validation information is included in the change notification and, if available, in the SON Report. In NetAct Configuration management there is an easy way of retrieving the information about the PCI changes. PM counter indicate the amount of newly learned information by PCI re-validation. 2) Autonomous Neighbor Relation Removal With the automatic neighbor relation removal, neighbor relations are deleted in case they are not seen as important neighbor, based on their recent history anymore. The deletions are triggered inside eNB. The complete deletion of a neighbor relation is done in steps, to allow a wait time in between which helps to prevent toggling of object deletions and re-creations in the network. · 1st step: Deletion of LNRELs, marked as not important anymore · 2nd step: Close X2-link if for certain time no outgoing handover over this X2 link is observed. Note: The X2 links may be re-established from other eNB as X2 setup request. · 3rd step: Remove associated objects as LNADJ/LNADJLs if X2-link is not available for a certain time and no outgoing handover happened to the eNB associated with LNADJ for a certain time. The time between the steps are considered as long term, as e.g. one day. They are operator configurable. Also the time to determine that the neighbor relation is considered to be not important anymore can be adjusted by operator.
The changes done with automatic deletion are reported using SON Reports.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
49/68
Doc number
Version 1.0
HW Requirements: no specific HW requirements Interdependencies between Features:
Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW BSW
LBTS7.0
Flexi Zone Micro LBTS7.0
NetAct
OMS
x
Licence Control in Network Element -
MME
SAE GW
-
-
UE
Licence Control Attributes -
6.2.2 MRO Ping Pong Unique ID: 1768 Short Description: This feature extends the existing Mobility Robustness functionality (MRO) to consider as well the radio handover situation that produces Ping Pongs between two cells. Intra/inter-frequency use cases for LTE are included. MRO will propose new settings for cell individual offset to prevent Ping Pongs happening. This feature is an extension of LTE533 Mobility Robustness. Benefits for the Customer: With this feature the following scenario in the network is considered in MRO: * Ping Pong The following use cases are already covered with existing feature LTE533: *
Too early handover
*
Too late handover
*
Handover to wrong cell (as part of too early handover)
All listed scenarios will be considered in MRO and the handover situation is going to be improved in the network.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
50/68
Doc number
Version 1.0
The feature is applicable for LTE macro and also to HetNet scenarios. In both cases the ping pong rates are going to be reduced heavily.
Functional Description: Mobility Robustness (MRO) considers as well the radio handover situations which produce Ping Pongs between two cells. This feature is an extension of LTE533 Mobility Robustness. Intra/inter-frequency use cases for LTE are included. The feature is applicable for LTE macro and also to HetNet scenarios. In both cases the Ping Pong rates are going to be reduced heavily. For the HetNet scenarios MRO may help for radio link failures with overshooting small cells, as e.g. by preventing terminals to go to small cells at all in problematic cases. The Flexi Multiradio BTS is * collecting new counter information for Ping Pong situation and provides it to NetAct Optimizer for analysis. *
providing the UE history information with outgoing handover.
MRO will propose new settings for cell individual offset to prevent Ping Pongs. All MRO use cases are addressed together in the MRO evaluation in Optimizer. So improvements for too early (including wrong cell), too late and ping pong will be addressed at the same time. The operator interface in Optimizer is re-used from LTT533 MRO with the needed extensions. HW Requirements: no specific HW requirements Interdependencies between Features: LTE533 MRO will be substituted by this feature LTE1768 Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10
Flexi NetAct OMS MME SAE UE Zone GW Micro Release RL70 LBTS7.0 LBTS7.0 LBTS7.0 x OMS7.0 3GPP R9 (RL70) UE capabilities SW Sales Information: BSW/ASW ASW NetAct
Licence Control in Network Element NetAct
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
51/68
Doc number
Version 1.0
6.2.3 Neighbor Detection Optimization for HetNet Unique ID: 1821 Short Description: This feature enhances LTE neighbor detection in a multi-layer HetNet environment by identifying and utilizing site specific neighbor distances relative to both the source and all potential target cells. Benefits for the Customer: This feature optimizes the initial neighborlist generated during pre-planning or auto configuration in order to better utilize fixed resources such as neighbor relationships and X2 links. In addition, this reduces the number of neighbors to be prioritized and allows for more optimal PCI assignment in a complex, multi-layer HetNet environment. Functional Description: Background The current Central ANR functionality treats all sites identically, regardless of type, size, and deployment setting, identifying all cells within an operator defined distance of the source as neighbor candidates. By not treating each site uniquely based on its site-specific characteristics, the potential for adding unnecessary cells to the neighborlist that the source will in reality never hand off to increases significantly. As operators migrate from a traditional macro-only LTE network to a more complex multilayer HetNet environment with a high number of small cells offloading capacity from macro eNBs, the number of neighbor relationships between cells and X2 links between eNB will increase significantly. A more optimized approach will be required to better manage the fixed number of resources. Overview This feature enhances Central ANR LTE neighbor detection in a multi-layer HetNet environment by identifying and utilizing site specific neighbor distances relative to both the source and all potential target cells. This allows eNB of varying sizes and configurations to be treated uniquely, benefiting both macro eNB and small cells. Proposed Solution A site-specific neighbor radius will be calculated for each eNB based on site-specific deployment characteristics such as eNB type and transmit power and stored as a derived database attribute for later use. For a specific source cell / target cell relationship, Central ANR will calculate the distance between the source cell and target cell. If the sum of the source cell neighbor radius and the target cell neighbor radius is greater than the actual distance between the cells, then cell will be identified as a neighbor candidate. If the sum is less than the actual distance between the cells, then the cell will not be a neighbor candidate. Pictorially, if the radius of the source cell
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
52/68
Doc number
Version 1.0
and target cell intersect and overlap, then the target cell is identified as a neighbor candidate. If they do not intersect and overlap, then it is not a neighbor candidate. HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release RL70 -
SW Sales Information: BSW/ASW BSW
Flexi Zone Micro -
NetAct
OMS
MME
SAE GW
NetAct8 EP2
OMS7.0 (RL70)
-
-
Licence Control in Network Element -
UE
Licence Control Attributes -
6.2.4 PCI Assignment Optimization for HetNet Unique ID: 1822 Short Description: This feature enhances PCI assignment in a multi-layer HetNet environment by utilizing cell specific neighbor relationships, allowing for more efficient use of PCI values. Benefits for the Customer: With the introduction of small cells in a multi-layer LTE HetNet enviornment, the number of PCI values assigned in a given geographical area will increase significantly, requiring a more optimized PCI assignment method to allow for greater PCI re-use. Functional Description: Multi-layer LTE HetNet deployments will see in increase in cell density as multiple small cells will be deployed under existing macro cells, resulting in an increase in PCI density. With more PCI values deployed in a given geographic region, more precise PCI assignment is needed. This feature utilizes a more granular identification of neighbor relationships to improve PCI assignment in a HetNet environment. Optimizer will utilize the neighbor relations identified with LTE1821 and LTE1823 in identifying the cell specicific forbidden list. This cell-specific identification will replace the existing distance re-use check which will be disabled. This method accomplishes the same function with greater cell level precision. In the event that all PCI values are found to be forbidden, the Bin 3, as defined in LTE1823, neighbors' neighbor cell's PCI values will be released and assignment re-attempted followed by releasing Bin 3 neighbor cell's PCI values.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
53/68
Doc number
Version 1.0
HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release RL70 -
SW Sales Information: BSW/ASW BSW
Flexi Zone Micro -
NetAct
OMS
MME
SAE GW
NetAct8 EP2
OMS7.0 (RL70)
-
-
Licence Control in Network Element -
UE
Licence Control Attributes -
6.2.5 Neighbor Prioritization Optimization for HetNet Unique ID: 1823 Short Description: This feature enhances LTE neighbor prioritization in a multi-layer HetNet environment by utilizing site specific neighbor distances relative to both the source and all target cells to provide a more accurate priority of neighbor cells. Benefits for the Customer: This feature optimizes the prioritization of neighbor cells generated during pre-planning or auto configuration in order to better utilize the fixed resources such as neighbor relationships and X2 links. In addition, this allows for more optimal PCI assignment in a complex, multilayer HetNet environment, especially in the case where all available PCI values have been blacklisted and neighbor priority is required for the initial PCI assignment. Functional Description: Background The current Central ANR functionality treats all cells identically, regardless of type, size, and deployment setting when prioritizing neighbor candidates of a source cell. By not treating each site uniquely based on its site-specific characteristics, the potential for mis-prioritizing target cells within the neighborlist increases significantly and as a result if more than the predefined number of neighbors have been identified, legitimate neighbors could be prevented from being added to the initial neighborlist. As operators migrate from a traditional macro-only LTE network to a more complex multilayer HetNet environment with a high number of small cells offloading capacity from macro eNBs, the number of neighbor relationships between cells and X2 links between eNB will increase significantly. A more optimized approach will be required to better manage the fixed number of resources and ensure that the proper neighbors are identified. Overview : This feature enhances Central ANR LTE neighbor prioritization in a multi-layer HetNet environment by identifying and utilizing site specific neighbor distances relative to
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
54/68
Doc number
Version 1.0
both the source and all potential target cells. This allows eNB of varying sizes and configurations to be treated uniquely, benefiting both macro eNB and small cells. Proposed Solution Prioritization will occur in two step process. In the first step, all neighbor candidate cells identified by the new functionality introduced in LTE1821 will be categorized in to one of three bins in decreasing priority as follows: • Bin 1: All neighbor candidate cells whose physical location falls within the coverage area of the source cell. This ensures that all cells within the coverage of the source, be it a small cell under a source macro, or the macro overlaying a source small cell, will be prioritized first. • Bin 2: All neighbor candidate cells whose physical location falls outside of the coverage area of the source cell but whose coverage at least partially overlaps or extends to the coverage area of the source cell. • Bin 3: All neighbor candidate cells whose physical location falls outside of the coverage area of the source cell and whose coverage falls entirely outside of the coverage area of the source cell. In the second step, target cells will be prioritized within the various bins. • Cells in Bin 1 will be prioritized based on the ratio of transmit power to distance from the source cell. This ensures that neighbors are prioritized based on perceived strength relative to the source rather than simply on location as a larger cell that is further away could be a stronger neighbor candidate than a smaller cell that is closer. • Cells in Bin 2 will be prioritized in a similar manor as they are today, based on distance from the source cell and relative angle, however also adding in a transmit power component that accounts for the relative size of the target cell. • Cells in Bin 3 will be prioritized in the same manor as cells in Bin 1. In the event that more target neighbor cells have been identified than the maximum number allowed by the operator, the lowest priority neighbors will be removed from the neighborlist. HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release RL70 -
SW Sales Information: BSW/ASW BSW
Flexi Zone Micro -
NetAct
OMS
MME
SAE GW
NetAct8 EP2
OMS7.0 (RL70)
-
-
Licence Control in Network Element -
UE
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
55/68
Doc number
Version 1.0
6.2.6 System Upgrade to RL70 Unique ID: 1854 Short Description: This feature enables first time smooth upgrade from major release (RLxx) N-2 to release N in the overall network. LTE releases are recently scheduled with half year release cycles. With N-2 system release upgrade support NSN enables that operator has not necessarily to follow each half year release, but can consider to do only one system upgrade during one year, but still have full smooth upgrade support. The upgrade is supported from Rl50 (OSS5.x) to Rl70 (NetAct8 EP2) or from Rl60 (NetAct8 EP1) to Rl70 (NetAct EP2). Additional upgrade path from FlexiZone release RL50FZ EP1 to RL70 as common worldmarket release supported. (RL50FZ EP1 with NetAct8 EP1)
Benefits for the Customer: Smooth remote upgrade path from major release N-2 to release N. Functional Description: Following functionality is supported with this system upgrade feature support: 1) 2)
N-2 release upgrade support Dedicated new functionality coming with RL70 upgrade feature
3) General feature support as general part of system upgrade feature setup, but with this feature now 1st time with N-2 support
2) Dedicated new functionality coming with RL70 upgrade feature Additional feature support introduced with RL70 upgrade: 1) First time N-2 release upgrade support. This feature enables first time smooth upgrade from major release (RLxx) N-2 to release N in the overall network. LTE releases are recently scheduled with half year release cycles. With N-2 system release upgrade support NSN enables that operator has not necessarily to follow each half year release, but can consider to do only one system upgrade during one year, but still have full smooth upgrade support. The upgrade is supported from Rl50 (OSS5.x) to Rl70 (NetAct8 EP2) or from Rl60 (NetAct8 EP1) to Rl70 (NetAct EP2). 2) Additional upgrade path from FlexiZone release RL50FZEP1 to RL70 as common worldmarket release supported.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
56/68
Doc number
Version 1.0
3) OMS remote MAJOR SW management support applied for first time in system upgrade setup This remote upgrade is possible for upgrade form RL60 to RL70. Whereas the upgrade from RL50 to RL70 is done in traditional way.
4) Rollback execution in eNB (FSMr3) The rollback execution in eNB is using the former SW version used in the eNB and the former used configuration set as it was before SW upgrade for the complete eNB setup. The rollback in that way is executed for system module, transport and RF modules.
5) Rollback command for operator trigger The operator can trigger the rollback to the former existing SW version and former used configuration data in complete eNB (including system module, transport and RF modules). 2)
General feature support as general part of system upgrade feature setup
1) The upgrade from release N-2 or N-1 to release N is possible in one step. No intermediate SW versions are necessary to be installed. The impacted NEs are the Flexi Multiradio BTS, NetAct with all LTE relevant applications including Optimizer, Trace Viewer, the Northbound interfaces, the iOMS, Traffica and Layer3 Data Collector with its applications, as L3 data analyser. 2) The upgrade paths have to consider both Flexi Multiradio platforms FSMr2 and FSMr3 in following way: · FSMr2 to FSMr2 This is valid for configurations which can be fulfilled with FSMr2 configurations in N-2 or N-1. · FSMr3 to FSMr3 This is valid for configurations which can be fulfilled with FSMr3 configurations in N-2 or N-1. 3) All operator-configured data is maintained in the system. If necessary, configuration data is converted into new format. This implies that the data from the previous release can be re-used after the upgrade. No manual intervention is required. This data includes: · Most obvious all configuration data of the Flexi Multiradio BTS, iOMS, NetAct, L3DC and Traffica · Adaptations made by operator for different (graphical) presentations in BTS SM or NetAct are for example: top level user interface: topology view, as for example: · PM configuration 4) System data will need to be stored before system upgrade. A user-friendly backup concept is in place. The data will be available after upgrade. This data includes for example:
Prepared by
Nokia Solutions and Networks LTE RAN ·
Approved by
Date
Page
29.11.2013
57/68
Doc number
Version 1.0
Measurements, as PM data
PM data which is not yet uploaded to NetAct before System Upgrade activation in Flexi Multiradio BTS will be lost. · User security, as data like user accounts/passwords, log files, ... · Network security, as data like certificates, keys, ... 5) Command line/script execution In case there are used command line or scripts, they need to be backward compatible or a converter must be in place for the upgrade support from release N-2 or N-1 to release N. 6) NetAct is prepared to handle both NE releases (release N-2 or N-1, release N) with release N timeframe. A mixed configuration support is ensured. But in the network at same time there are only 2 releases same time operational, so either N-2 and N or N-1 and N.
7) iOMS is prepared to handle both NE releases (release N-2 or N-1, release N) with release N timeframe. A mixed configuration support is ensured. But in the network at same time there are only 2 releases same time operational, so either N-2 and N or N-1 and N. 8) BTS SM is prepared to handle both NE (N-2 and N or N-1 and N) releases, at least as coexisting versions of BTS SM with release N. 9) Layer3 Data Collector is prepared to handle both NE (N-2 and N or N-1 and N) releases. 10) Traffica is prepared to handle both NE releases (N-2 and N or N-1 and N). 11) If a conversion of the data is required, the related converter Software is available either in online or offline mode. 12) An LTE system wide top-down upgrade sequence is defined. 13) The downtime of a network entity during the system upgrade is reduced to the activation of the new software. The switch to the new release (activation of the software) will be performed on operator's request from NetAct or BTS SM. Traffica and L3DC are supporting local SW management, no remote handling. 14) In case of an upgrade failure, an automatic fallback to the original release takes place. In case of minor failures no SW rollback is initiated, but still the error information will be indicated. The failures are logged. The log files include detailed information about the reasons and the information is logged into non-volatile memory. In addition the fallback can be initiated from the operator on command. For L3DC and Traffica a manual rollback can be initiated by operator. The fallback has to consider both the correct CM database and the consistency between them needs to be ensured. The automatic fallback is available for Flexi Multiradio BTS.
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
58/68
Doc number
Version 1.0
15) A delta description lists all differences to the old version as part of the customer documentation. This is valid for all data. 16) This feature does not include the upgrade of any HW. 17) RF sharing cases In RF sharing setups the master/slave roles are considered. Only the master can upgrade the RF modules.
HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS LTE BTS Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW BSW
LBTS7.0
Flexi Zone Micro LBTS7.0
NetAct
OMS
MME
SAE GW
NetAct8 EP2
OMS7.0 (RL70)
-
-
Licence Control in Network Element -
UE
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
59/68
Doc number
Version 1.0
6.2.7 Automatic Configuration support for CA for multi-carrier eNBs Unique ID: 1951 Short Description: Automatic Configuration support for Carrier Aggregation (CA) for multi-carrier eNBs will support operator to automatically assign the needed cell selection. Benefits for the Customer: With this feature no manual planning is needed. NetAct SON Solution will automatically propose the needed configuration for Carrier Aggregation for multi-carrier eNBs. Functional Description: NetAct SON Solution is offering an automatic assignment of the cells for the usage of LTE1562 Carrier aggregation for multi-carrier eNode Bs. The constraints of supported configurations with LTE1562 are considered. The changes are included to SON reports. HW Requirements: no specific HW requirements Interdependencies between Features: LTE1562 Automatic Configuration support for CA for multi-carrier eNBs Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW ASW NetAct
LBTS7.0
Flexi Zone Micro LBTS7.0
NetAct
OMS
x
Licence Control in Network Element NetAct
MME
SAE GW
-
-
UE
Licence Control Attributes -
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
60/68
Doc number
Version 1.0
7 Performance Monitoring 7.1 Real-time KPI-monitoring with Traffica Unique ID: 1053 Short Description: Real-time KPI-monitoring with Traffica provides real-time performance monitoring for the LTE Flexi Multiradio BTS. Benefits for the Customer: Real-time KPI-monitoring with Traffica helps the operators to improve revenue due to reduced problems in the network and provide consequently more effective networks; an OPEX saving is also expected considering the expensive alternative solution based on 3rd parties probes tools available for the same use case.
Functional Description: Real-time KPI-monitoring with Traffica provides real-time performance monitoring for the Flexi Multiradio BTS. Traffica is connected directly to Flexi Multiradio BTS using a new real-time data interface. This real-time data interface contains the results of ongoing performance measurements (PM-counter values) in "real-time", sent every minute. Activation/de-activation of Flexi Multiradio BTS real-time data interface for real-time KPImonitoring is handled via NetAct Configuration Management (CM) for each cell to be monitored. The receiver of real-time KPI-data (Collection Entity) is configured via NetAct CM by providing the IP-address of the data receiver, in this case Traffica, to Flexi Multiradio BTS. NOTE Only NSN-products like Traffica are allowed to receive real-time KPI-data from Flexi Multiradio BTS (use case is not supported with 3rd-party vendor applications). This is ensured by proper mechanisms, implemented at Flexi Multiradio BTS and/or Traffica. Traffica receives the real-time data stream and creates KPIs based on the received data and visualizes them in Traffica real-time graphs.
The following procedures are monitored by Traffica.
RRC-monitoring: • RRC-connection establishment • RRC-connection release (normal/abnormal cause) • RRC-re-establishment • RRC-re-configuration
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
61/68
Doc number
Version 1.0
• Paging performance Radio Bearer Management monitoring • E-RAB setup • E-RAB release (normal/abnormal release) Mobility Management monitoring • Intra-LTE Handover (successful/non-successful intra-eNB/ Inter-eNB X2/Inter-eNB S1 handover), neigbour-cell related • Inter-System Handover (successful/non-successful WCDMA/GSM handover), neigbhour-cell related • Too early/Too late handovers (according to MRO) BTS-load and throughput monitoring • Number of users • Data throughput UL/DL • Physical resource block (PRB) usage Power and QoS monitoring • Packet delay • Received signal strength indicator (RSSI) for PUSCH/PUCCH NOTES: • Any PM-counter will be covered by LTE1053 except the transport (backhaul) related performance measurements • • The number of PM-counters may still vary because new raw PM-counters may be added to the release where LTE1053 will be implemented via other features or change requests • • Any new performance measurement coming in future releases are automatically covered by LTE1053 (except transport-related performance measurements) • • The performance measurements that are reported in real-time are pre-defined and fixed. No configuration/administration of performance measurements to be reported is supported • Based on the received data Traffica will provide the following KPI-graphs. NOTES: • The numbers at the beginning of the KPI-title are the NSN KPI-Ids, according to KPI-specification. • The list of KPIs maybe not complete since still new performance measurements may be added to the release where LTE1053 will be implemented E-RAB related KPIs: • • • • • •
LTE_5017a E-RAB Setup Success Ratio LTE_5112b Initial E-RAB Setup Success Ratio LTE_5113b Additional E-RAB Setup Success Ratio LTE_5060e Initial E-RAB Accessibility LTE_5574a Additional E-RAB Accessibility LTE_5118a E-RAB Setup Attempts
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
62/68
Doc number
Version 1.0
• • • • • • • • • • • • •
LTE_5205a E-RAB Setup Attempts, QCI1 LTE_5550a E-RAB Setup Attempts, QCI2 LTE_5551a E-RAB Setup Attempts, QCI3 LTE_5552a E-RAB Setup Attempts, QCI4 LTE_5206b E-RAB Setup Attempts, non GBR LTE_5204a E-RAB Setup Success Ratio, QCI1 LTE_5553a E-RAB Setup Success Ratio, QCI2 LTE_5554a E-RAB Setup Success Ratio, QCI3 LTE_5555a E-RAB Setup Success Ratio, QCI4 LTE_5217b E-RAB Setup Success Ratio, non- GBR LTE_5201a Additional E-RAB Setup Attempts for IMS Emergency Sessions LTE_5202a Additional E-RAB Setup Success Ratio for IMS Emergency Sessions LTE_5086a, LTE_5087a, LTE_5088a, LTE_5089a E-RAB Setup Failure Ratio per Cause • LTE_5203a Additional E-RAB Setup Failures for IMS Emergency Sessions • LTE_5023d E-RAB Normal Release Ratio, User perspective • LTE_5209a E-RAB QCI1 Normal Release Ratio, User perspective • LTE_5024d E-RAB Normal Release Ratio, RAN View • LTE_5025d E-RAB Drop Ratio, RAN View (pre-emptions excluded) • LTE_5572a E-RAB QCI1 Drop Ratio, RAN View • LTE_5090b, LTE_5091b, LTE_5092c, LTE_5237b, LTE_5238b, LTE_5570c, LTE_5571b E-RAB Drop Ratio per Cause • LTE_5119c E-RAB Drop Ratio, User Perspective (eNB pre-emptions excluded) • LTE_5812a E-RAB Drops per PDCP SDU volume, User Perspective • LTE_5581a E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost • LTE_5582a QCI1 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost • LTE_5583a QCI2 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost • LTE_5584a QCI3 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost • LTE_5585a QCI4 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost • LTE_5586a non GBR E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost • LTE_5575a Total E-RAB Active Time • LTE_5576a E-RAB Active Time QCI1 • LTE_5577a E-RAB Active Time QCI2 • LTE_5578a E-RAB Active Time QCI3 • LTE_5579a E-RAB Active Time QCI4 • LTE_5580a E-RAB Active Time nonGBR • LTE_5220b UE Transaction to ECM-IDLE State Success Ratio • LTE_5587b E-RAB Release ratio due to Radio resources not available S1AP related KPIs: • • • • •
LTE_5009a S1 Initial Context Setup Success Ratio LTE_5120a S1 Initial Context Setup Attempts LTE_5093a, LTE_5094a, LTE_5095a, LTE_5096a S1 Initial Context Setup Failure Ratio per Cause LTE_5014a S1 Setup Success Ratio LTE_5121a S1 Setup Attempts
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
63/68
Doc number
Version 1.0
• LTE_5097a, LTE_5098a S1 Setup Failure Ratio per Cause • LTE_5147a, LTE_5148a S1 Partial Reset Distribution Rate Radio Bearer related KPIs: • • • •
LTE_5116a Data Radio Bearer Setup Attempts LTE_5003a Data Radio Bearer Setup Success Ratio LTE_5004a Radio Bearer Drop Ratio LTE_5117a Radio Bearer Success Ratio
RRC Signaling related KPIs: •
LTE_5232a, LTE_5233a, LTE_5234a, LTE_5235a, LTE5228a RRC Connection Setup Attempts • LTE_5218c RRC Connection Setup Success Ratio • LTE_5227a RRC Connection Setup Success Ratio for emergency Calls • LTE_5229b, LTE_5230b, LTE_5231b RRC Connection Setup Failure Ratio per Cause • LTE_5141a, LTE_5142a RRC Connection Re-establishment Attempts • LTE_5143a RRC Connection Re-establishment Success Ratio • LTE_5144a RRC Connection Re-establishment Rejection Ratio • LTE_5145a RRC Connection Re-establishment Failure Ratio • LTE_5031b RRC Paging Discard Ratio • LTE_5122b RRC Paging Records • LTE_5301a Number of requested CGI reports for UTRAN • LTE_5302a CGI reports for UTRAN Success Ratio • LTE_5303a CGI reports for UTRAN Failure Ratio • LTE_5323a SCell Configuration Success Ratio Handover related KPIs: • • • • • • • • • • • • • • •
LTE_5036a HO Preparation Success Ratio, intra eNB LTE_5123a HO Preparations, intra eNB LTE_5104a, LTE5105a HO Preparation Failure Ratio per Cause, intra eNB LTE_5035a HO Success Ratio, intra eNB LTE_5124a HO Attempts, intra eNB LTE_5040b HO Failure Ratio, intra eNB LTE_5043a Total HO Success Ratio, intra eNB LTE_5049b HO Preparation Success Ratio, inter eNB LTE_5126a HO Preparations, inter eNB X2 based LTE_5078a HO Preparation Success Ratio, inter eNB S1 based LTE_5127a HO Preparations, inter eNB S1 based LTE_5106a, LTE_5107a, LTE5108a HO Preparation Failure Ratio per Cause, inter eNB X2 based LTE_5079a, LTE_5080a, LTE_5081a HO Preparation Failure Ratio per Cause, inter eNB S1 based LTE_5048b HO Success Ratio, inter eNB X2 based LTE_5125a HO Attempts, inter eNB X2 based
Prepared by
Nokia Solutions and Networks LTE RAN • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
Approved by
Date
Page
29.11.2013
64/68
Doc number
LTE_5082a HO Success Ratio, inter eNB S1 based LTE_5240a HO Attempts, inter eNB S1 based LTE_5055b HO Failure Ratio, inter eNB X2 based LTE_5083a HO Failure Ratio, inter eNB S1 based LTE_5058b Total HO Success Ratio, inter eNB X2 based LTE_5084a Total HO Success Ratio, inter eNB S1 based LTE_5109a, LTE_5110a, LTE_5111a CS Fallback Attempts with Redirection via RRC Connection Release Distribution Rate LTE_5190a Inter RAT HO Preparations LTE_5191a Inter RAT HO Preparation Success Ratio LTE_5192a, LTE_5193a, LTE_5194a Inter RAT HO Preparation Failure Ratio per Cause LTE_5195a Inter RAT HO Success Ratio LTE_5196a Inter RAT HO Attempts LTE_5197a Inter RAT HO Failure Ratio LTE_5198a Total Inter RAT HO Success Ratio LTE_5562a Inter RAT HO Attempts to UTRAN with SRVCC LTE_5563a Inter RAT HO to UTRAN with SRVCC Failure Ratio LTE_5564a Inter RAT HO to UTRAN with SRVCC Success Ratio LTE_5565a Inter RAT HO Attempts to GERAN with SRVCC LTE_5566a Inter RAT HO to GERAN with SRVCC Failure Ratio LTE_5567a Inter RAT HO to GERAN with SRVCC Success Ratio LTE_5114a Inter-Frequency HO Success Ratio LTE_5115a Inter-Frequency HO Success Ratio - Measurement Gap assisted LTE_5568a Intra-Frequency HO Success Ratio LTE_5174a Number of Late HO Events LTE_5175a Number of Type 1 Early HO Events LTE_5176a Number of Type 2 Early HO Events LTE_5177a HO Attempts for UEs running in DRX mode LTE_5178a HO Success Ratio for Ues running in DRX mode LTE_5179a Number of NACCAttempts from LTE to GSM LTE_5152a HO Preparations for IMS emergency sessions LTE_5155a HO Preparation Success Ratio for IMS emergency Sessions LTE_5158a HO Attempts for IMS emergency Sessions LTE_5161a HO Success Ratio for IMS emergency Sessions LTE_5164a Total HO Success Ratio for IMS emergency Sessions LTE_5316a Number of Load Balancing HO Attempts LTE_5317a Load Balancing HO Success Ratio LTE_5300a Redirect to Home eNB
Capacity related KPIs: • • • • •
Version 1.0
LTE_5800c Average Active UEs with data in the buffer DL LTE_5805c Average Active UEs with data in the buffer for DRBs of QCI1 DL LTE_5559b Average Active UEs with data in the buffer for DRBs of QCI2 DL LTE_5560b Average Active UEs with data in the buffer for DRBs of QCI3 DL LTE_5561b Average Active UEs with data in the buffer for DRBs of QCI4 DL
Prepared by
Nokia Solutions and Networks LTE RAN • • • • • • • • • • • • •
Approved by
Date
Page
29.11.2013
65/68
Doc number
LTE_5806c Average Active UEs with data in the buffer for non-GBR DRBs (QCI5..9) DL LTE_5801c Average Active UEs with data in the buffer UL LTE_5807b Average Active UEs with data in the buffer for QCI1 DRBs per cell UL LTE_5808c Average Active UEs with data in the buffer for non-GBR DRBs UL LTE_5802a Maximum Active UEs with data in the buffer per cell DL LTE_5803a Maximum Active UEs with data in the buffer per cell UL LTE_5804b Average Active Connected UEs LTE_5214a Maximum of Average Active Connected UEs LTE_5318a Average CA Capable UEs in DL LTE_5319a Average UEs with a Configured SCell in DL LTE_5320a Average UEs with an Activated SCell in DL LTE_5321a Penetration of the CA Capable UEs into the Network LTE_5326a Average UEs configured for TTI Bundling Mode
Throughput related KPIs: • LTE_5292c Average PDCP Layer Active Cell Throughput DL • LTE_5293c Average PDCP Layer Active Cell Throughput DL for QCI1 DRBs • LTE_5289c Average PDCP Layer Active Cell Throughput UL • LTE_5294c Average PDCP Layer Active Cell Throughput UL for QCI1 DRBs • LTE_5284b Average RLC Layer Cell Throughput DL • LTE_5283b Average RLC Layer Cell Throughput UL • LTE_5212a PDCP SDU Volume DL • LTE_5213a PDCP SDU Volume UL • LTE_5211a RLC PDU Volume DL • LTE_5324a RLC PDU Volume DL via SCell • LTE_5810a RLC PDU Volume UL • LTE_5064b Average incoming Signaling Throughput on X2 • LTE_5065b Average outgoing Signaling Throughput on X2 • LTE_5068a Average incoming Data Throughput on X2 • LTE_5069a Average outgoing Data Throughput on X2 Cell Resource related KPIs: • LTE_5276b Average PRB usage per TTI Downlink • LTE_5273b Average PRB usage per TTI Uplink • LTE_5750a Cell Availability Ratio • LTE_5751a Planned Cell Unavailability Ratio • LTE_5752a Unplanned Cell Unavailability Ratio • LTE_5239a Cell Availability, excluding blocked by user state (BLU) Power and Quality related KPIs: • • • • • •
Version 1.0
LTE_5134a Average Latency Downlink LTE_5138a Average Latency Downlink for QCI1 DRBs LTE_5556a Average Latency Downlink for QCI2 DRBs LTE_5557a Average Latency Downlink for QCI3 DRBs LTE_5558a Average Latency Downlink for QCI4 DRBs LTE_5139a Average Latency Downlink for non GBR DRBs
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
66/68
Doc number
• LTE_5137a Average Latency Uplink • LTE_5208a RLC PDU Re-transmission Ratio Downlink • LTE_5207b RLC PDU Re-transmission Ratio Uplink • LTE_5216a MAC PDU Re-transmission Ratio Downlink • LTE_5441b Average RSSI for PUCCH • LTE_5444b Average RSSI for PUSCH • LTE_5541b Average SINR for PUCCH • LTE_5544b Average SINR for PUSCH • LTE_5427a Average CQI • LTE_5432b Average CQI Offset • LTE_5304a PDCP SDU Loss Ratio in the DL • LTE_5305a PDCP SDU Loss Ratio in the DL, QCI1 • LTE_5306a PDCP SDU Loss Ratio in the DL, QCI2 • LTE_5307a PDCP SDU Loss Ratio in the DL, QCI3 • LTE_5308a PDCP SDU Loss Ratio in the DL, QCI4 • LTE_5309a PDCP SDU Loss Ratio in the DL, nonGBR • LTE_5310a PDCP SDU Loss Ratio in the UL • LTE_5311a PDCP SDU Loss Ratio in the UL, QCI1 • LTE_5312a PDCP SDU Loss Ratio in the UL, QCI2 • LTE_5313a PDCP SDU Loss Ratio in the UL, QCI3 • LTE_5314a PDCP SDU Loss Ratio in the UL, QCI4 • LTE_5315a PDCP SDU Loss Ratio in the UL, nonGBR Contention Free Random Access Procedure related KPIs: • • •
LTE_5167a, LTE_5168a PDCCH Order Attempts LTE_5169a, LTE_5170a PDCCH Order Attempts Success Ratio LTE_5171a, LTE_5172a, LTE_5173a Unavailability of dedicated preamble
Miscellaneous KPIs: • • •
LTE_5077a UE Context Modification Failure Rate LTE_5150a, LTE_5151a Graceful Cell Shutdown Drop Rate LTE_5569a RACH Setup Completion Success Rate
Traffica is required to store the collected data at least 48 hours.
HW Requirements: no specific HW requirements
Version 1.0
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
67/68
Doc number
Version 1.0
Interdependencies between Features: NetAct Traffica required Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
LBTS7.0
SW Sales Information: BSW/ASW ASW
Flexi NetAct Zone Micro LBTS7.0 LBTS7.0 NetAct8 EP2
OMS
Licence Control in Network Element Pool license
MME
SAE GW
UE
-
-
n/a
Licence Control Attributes -
7.2 PM Counters enhancement for RAB-modification/context/TM7 Unique ID: 1740 Short Description: PM counters extension Benefits for the Customer: Counters enhancements, according to customer requirements Functional Description: Following PM-counters are implemented: 1) E-RAB modification - E-RabModReq_Qci: number of E-RABs per QCI in S1AP: E-RAB Modify Request message - E-RabModSucc_Qci: number of successful E-RABs per QCI in S1AP: E-RAB Modify Response message - E-RabModfailed_Cause: number of failed E-RABs in S1AP: E-RAB Modify Response message (based of causes) Required causes: a. Failure in the Radio Interface Procedure b. Radio Network Layer cause -unspecified c. Not supported QCI value Use case: Provide the executing result for E-RAB Modify Request 2) Context related counters based of cell - Context.AttInitalSetup : number of initial context setup attempts
Prepared by
Nokia Solutions and Networks LTE RAN
Approved by
Date
Page
29.11.2013
68/68
Doc number
Version 1.0
- Context.AttInitalSetup.CSFB : number of initial context setup attempts by CSFB - Context.SuccInitalSetup: number of successful initial setup attempts - Context.SuccInitalSetup.CSFB: number of successful initial context setup attemps for CSFB - Context. failInitalSetup_Cause: number of failed initial context setup attempts based of cause: Required causes: - Radio Network Layer cause - Transport Layer cause - Resource reasons - Context.AttMod: number of context modifications - Context.AttMod.CSFB: number of context modification attempts for CSFB - Context.SuccMod: number of successful context modifications - Context.SuccMod.CSFB: number of successful context modifications for CSFB Use case: Provide context setup /modify successful rates per cell 3) TM7 related counters - Number of times when PDSCH transmission mode is beamforming in TM7 User case: For TM7 performance analysis 4) Number of failed E-RABs by outgoing HO - ERABHoFail (Sum) - ERABHoFailPerQCI (#1/#2/#3/#4) Use case: To provide feedback for monitoring the network performance.
HW Requirements: no specific HW requirements Interdependencies between Features: no feature interdependencies Dependency to other RATs:No dependency RL Software Dependencies: BTS BTS LTE Flexi Flexi 10 Release
RL70
-
SW Sales Information: BSW/ASW BSW
LBTS7.0
Flexi Zone Micro -
NetAct
OMS
-
Licence Control in Network Element -
MME
SAE GW
-
-
UE
Licence Control Attributes -
View more...
Comments
