Vous êtes sur la page 1sur 83

Prepared by Date Page

16.12.2013 1/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

LTE RAN Release RL60


Feature under Development
Prepared by Date Page
16.12.2013 2/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.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 Date Page
16.12.2013 3/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Table of Contents
1 Introduction ......................................................................................................................... 5
2 History ................................................................................................................................ 6
3 BTS Site Solution ................................................................................................................ 7
3.1 FXFC Flexi RF Module 3TX 1900 ................................................................................ 7
3.2 FBBC Flexi Capacity Extension Sub-Module ............................................................... 9
3.3 Multiradio System Module full LTE configurations .......................................................10
3.4 Multiradio System Module extended LTE configurations with FBBC ...........................12
3.5 FXFB Flexi 3-sector RF Module 1900 .........................................................................13
3.6 FXCB Flexi RF Module 850 ........................................................................................15
3.7 LTE-GSM and LTE-WCDMA RF sharing for dual band and 4Rx configurations..........16
4 Transmission .....................................................................................................................19
4.1 IPv6 for U/C-Plane ......................................................................................................19
4.2 IPSec Emergency Bypass...........................................................................................21
4.3 Measurement based TAC ...........................................................................................23
4.4 Local and Remote IP Traffic Capturing .......................................................................25
4.5 Timing over Packet with phase synchronization ..........................................................27
5 Radio Resource Management and Telecom ......................................................................30
5.1 LTE: Mobility ...............................................................................................................30
5.1.1 RSRQ triggered mobility ......................................................................................30
5.1.2 Extended RNC ID ................................................................................................31
5.1.3 Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) ............................................32
5.1.4 Inter-frequency load balancing extension .............................................................35
5.1.5 Multiple Frequency Band Indicator .......................................................................36
5.1.6 Idle mode mobility balancing extensions ..............................................................37
5.1.7 RAN Information Management for GSM...............................................................38
5.1.8 Inter RAT handover from UTRAN ........................................................................39
5.1.9 Inter RAT handover to eHRPD/3GPP2 ................................................................40
5.1.10 CSFB to CDMA/1xRTT for dual RX UEs ..............................................................43
5.2 LTE: Coverage, capacity and peak rates ....................................................................45
5.2.1 Downlink carrier aggregation - 40 MHz ................................................................45
5.2.2 Interference aware UL power control ...................................................................47
5.2.3 Uplink intra eNode B CoMP .................................................................................48
5.2.4 Fast uplink link adaptation....................................................................................49
5.2.5 PUSCH masking ..................................................................................................50
5.3 LTE: QoS, services and end user experience .............................................................51
5.3.1 Multimedia priority services ..................................................................................51
5.3.2 Operator specific GBR QCIs ................................................................................52
5.3.3 Cell resource groups ............................................................................................53
5.3.4 LPPa support for OTDOA ....................................................................................55
5.3.5 Multiple emergency areas per cell........................................................................56
5.3.6 8 EPS bearers per UE .........................................................................................57
5.4 LTE: Supplementary RRM functions ...........................................................................59
5.4.1 Control plane overload handling ..........................................................................59
5.4.2 Group hopping for UL reference signal ................................................................60
Prepared by Date Page
16.12.2013 4/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

6 Operability..........................................................................................................................62
6.1 Network Monitoring and Maintenance .........................................................................62
6.1.1 BTS Diagnostics Toolkit used by operator ...........................................................62
6.1.2 S1 lock/unlock......................................................................................................64
6.2 Configuration Management .........................................................................................65
6.2.1 Parameter Categorization ....................................................................................65
6.2.2 System Upgrade to RL60 .....................................................................................67
6.2.3 Support for Multi-antenna RET device .................................................................70
6.2.4 Extend maximum number of X2 links ...................................................................72
6.2.5 ANR Intra-LTE, Inter-frequency - UE based .........................................................73
6.2.6 Intelligent configuration synchronization...............................................................76
6.3 O&M Security..............................................................................................................78
6.3.1 Revocation management .....................................................................................78
7 Performance Monitoring .....................................................................................................82
7.1 Additional QoS performance measurements ...............................................................82
Prepared by Date Page
16.12.2013 5/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

1 Introduction
This document provides the list of feature under development for the LTE Radio Access System
Release RL60.

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 Date Page
16.12.2013 6/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

2 History
First version 14.06.2013
Version 1.1 02.10.2013 Update to new NSN template; LTE1434 removed; LTE 1198 and
LTE1755 added
Version 1.2 14.11.2013 Real time KPI LTE1053 removed, LTE1657 and LTE 1361 added
Version 1.3 10.12.2013 LTE449 RACH overload handling removed
Version 2.0 16.12.2013 First version of Feature Under Development (FUD)
Prepared by Date Page
16.12.2013 7/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

3 BTS Site Solution


3.1 FXFC Flexi RF Module 3TX 1900
Unique ID: 1440

Short Description:

Flexi Multiradio RF Module FXFC for 1900 MHz band 2 is introduced. FXFC has 3*80W power
at the antenna connector. The supported Tx bandwidth is 35 MHz and Rx bandwidth is 60 MHz

Benefits for the Customer:


New high power 3-sector Flexi Multiradio RF Module introduces industry leading RF integration
level and smallest power consumption combined with flexible GSM-WCDMA-LTE site evolution.
Full support for Multi-Operator sites with high output power and wide RF bandwidth.
Operator is freely able to allocate carriers in the wider band compared to FXFA/B and utilize
increased output RF power.

FXFB Flexi 3-sector RF Module 80 W 1900 MHz has 35 MHz RF bandwidth support at 3GPP
band 2.

3-sector 3x 80 W RF Module general benefits:


• the most cost and size and weight optimized 3-sector BTS site
• industry leading RF integration level
• SW configurable radio: the same RF Module for LTE, HSPA+ and WCDMA and
GSM/EDGE
• 3 sector RF in one outdoor IP65 box
• Widest ambient temperature range -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
• TX div and MIMO 2TX can be build using two 3-sector RF Modules
o RF redundancy option comes as side bonus

3-sector Module is more cost effective than 3 x RF Head in feederless installations due to
• Less weight
• Less wind load
• typically 1/3 of DC and optical cabling compared to site with Remote RF Heads (RRH)
• easier installation
• less visual impact
• RF Module can be used as powerful one sector RRH : 80 + 80 W 2TX MIMO with HW
prepared for 4RX
Prepared by Date Page
16.12.2013 8/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Functional Description:
Flexi Multiradio RF Module 1900 HW supports GSM, WCDMA or LTE in dedicated or
concurrent mode.
Flexi Multiradio RF Module provides 3*80 W output power at the antenna connector.
Maximum capacity of one Flexi Multiradio RF Module for GSM is up to 6 TRXs, for WCDMA is
up to 4 carriers and up to 20 MHz LTE carrier.

TX supports 35 MHz instantaneous bandwidth. RX supports 60 MHz instantaneous bandwidth.

• 3x 80 W output Flexi RF Module, IP65.


• 3GPP band 2 supported.
• U high with Flexi platform mechanics.

Basic LTE Configurations:


• 1, 1+1 or 1+1+1 LTE cells @ max 20 MHz LTE bandwidth and 1TX/2RX
• 8, 20, 40, 60, 80 W mode per sector (by SW licenses)
• 1 sector max 80 + 80 W 2TX/2RX MIMO
• HW prepared for 1 sector max 80 + 80 W 2TX/4RX MIMO
• 6 Gbps optical link support (OBSAI)
• RET connector

Can be used in Feederless (DC up to 200 m) BTS sites.

WCDMA and GSM/EDGE configurations are described in GSM/EDGE and WCDMA release
documents.

HW Requirements:

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 - - - 3GPP R8
UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 9/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

3.2 FBBC Flexi Capacity Extension Sub-Module


Unique ID: 1444

Short Description:

The FBBC is a high capacity baseband extension sub-module for the FSMF System Module
with improved RF unit connectivity.

Benefits for the Customer:


The Flexi Multiradio System Module baseband capacity and RF unit connectivity can be flexibly
expanded. It provides four RP3-01 connections from System Module to Radio Units. FSMF
equipped with two FBBC sub-modules can support up to twelve RP3-01 optical 6 Gbits/s links
towards RF Units.

Functional Description:
FBBC is an optional outdoor high capacity extension sub-module, which improves the Multiradio
System Module performance by adding control and baseband processing as well as four optical
RF connections.
There can be two FBBC sub-modules in one 3U FSMF outdoor casing.
Compared to FBBA, FBBC improves the RF connectivity by additional optical SFP RF ports
which can be connected to RF Modules or RRHs.
FBBC HW has the same capacity performance as FBBA: it supports LTE capacity of 3 x 20
MHz with 2TX MIMO enabling 450 Mbps downlink and 150 Mbps uplink data speeds.

FBBC sub-module has the following external interfaces:


• one -48VDC input
• one baseband extension interface towards the FSMF core module
• up to four optical OBSAI RP3-01 interfaces with up to 6 Gbit/s to RF units
• one of the four RP3 ports is dual mode combo port: it can be configured to operate as
RP3 port or SRIO (Serial Rapid Input/Output) interface for an external baseband
extension, e.g. additional System Module
FBBC is IP65 ingress protected. The operating temperature range is -35° to +55°C.
Prepared by Date Page
16.12.2013 10/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements: FSMF core System Module needed.

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 - LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

3.3 Multiradio System Module full LTE configurations


Unique ID: 1508

Short Description:

Full extended LTE configurations with Flexi Multiradio System Module FSMF with two optional
capacity extension sub-modules (two FBBCs or FBBA and FBBC).

Benefits for the Customer:


Full extended System capacity Flexi Multiradio System Module configurations (System Module
FSMF with two optional capacity extension sub-modules, two FBBCs or FBBA and FBBC) can
support bigger cell and sector configurations and downlink and uplink performance
enhancement features like 4TX MIMO and 4RX diversity.
Prepared by Date Page
16.12.2013 11/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Functional Description:
FSMF + two FBBC (or FBBA + FBBC) basic supported configurations:

Supported RF Modules and RRHs and detailed configurations are listed in separate LTE RL
release user documentation
• max 9 cells at 15/20 MHz 2TX 2RX, or
• max 18 cells at 5/10 MHz 2TX 2RX, or
• (3x20 and 12x10) OR (6x20 and 6x10 2TX 2RX), or
• 3x20 4TX AND (6x10 or 3x20 2TX), or
• 6x10 4TX AND (6x10 or 3x20 2TX)

Number of extra new RF units that can be connected with 2nd FBBC (when one link available
from FSMF or 1st FBBA/C and one link from 2nd FBBC):

Configuration RFM 3TX RRH 2TX RRH 4TX RFM 6TX


3 * 15/20 MHz 2TX 2RX 2 3c n/a 1
6 * 5/10 MHz 2TX 2RX n/a 6c n/a 2
3 * 5/10 MHz 4TX 4RX n/a n/a 3c 2

• c =RRHs chained with 2 links/chains


• one additional RF band for 2nd FBBC, or
• 2nd FBBC adds cells to existing RF bands
• max six 6 Gbps links for all RF units with 2nd FBBC
o 4 links by FSMF + 2 with two FBBCs
• for six RRHs at 10 MHz 2TX 2RX two 6 Gbps links chained

HW Requirements: Flexi MR10 BTS

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 - LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 12/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

3.4 Multiradio System Module extended LTE configurations with


FBBC
Unique ID: 1644

Short Description:

Extended LTE configurations with Flexi Multiradio System Module FSMF with one optional
capacity extension sub-module FBBC.

FBBC provides the same baseband capacity as FBBA but FBBC HW has four 6 Gbps optical
RP3 OBSAI links to RF units.

Benefits for the Customer:


Extended System capacity Flexi Multiradio System Module configurations (System Module
FSMF with one optional capacity extension sub-module FBBC) can support bigger cell and
sector configurations and downlink and uplink performance enhancement features like 4TX
MIMO and 4RX diversity.
FBBC provides the same baseband capacity as FBBA but FBBC HW has four 6 Gbps optical
RP3 OBSAI links to RF units.

Functional Description:
The following LTE FDD cell configurations are supported with one Flexi Multiradio System
Module FSMF with one optional capacity extension sub-module FBBC:
• Supported RF Modules and RRHs and detailed configurations are listed in separate LTE
RL release user documentation

HW configuration: FSMF + one FBBC


• 5 RP3 optical port in use (4 in FSMF + 1 in FBBC)
• maximum 6-cell configurations with maximum 20 MHz cell bandwidth with 2TX MIMO
and 2RX diversity
o 6 cell/6 sector configuration with one RF band
o two 3 sector BTS configurations with two different RF bands (dual band LTE
configuration)
OR
• maximum 3-cells one RF band configurations with 15 or 20 MHz cell bandwidth with 4TX
MIMO and/or 4 RX diversity
o LTE569 'DL adaptive closed loop MIMO 4x2' SW feature is needed in for
downlink capacity improvement
o LTE980 'IRC for 4 RX paths' or LTE72 '4-way RX diversity (MRC)' SW feature is
needed for uplink performance improvement
OR
• maximum 12-cell configuration with 10 MHz cell bandwidth with 2TX MIMO and 2RX
diversity
o two 6 sector/cell BTS configurations with two different RF bands (dual band) LTE
configuration
o up to 12 one cell RRH in 3 chains, max. 4 RRHs per chain
Prepared by Date Page
16.12.2013 13/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements: Flexi MR10 BTS

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 - LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

3.5 FXFB Flexi 3-sector RF Module 1900


Unique ID: 1665

Short Description:

Flexi Multiradio RF Module version for 1900 MHz supporting three sectors with 60 W output
power at the BTS antenna connector. It can be used as one sector powerful RRH with 60 W +
60 W 2TX MIMO.

Size and visual outlook is similar to the existing rel1 Dual and Single Flexi RF Modules. The
environmental protection class is IP65.

FXFB has external RET connector compared to FXFA.

Benefits for the Customer:


FXFB Flexi 3-sector RF Module 60 W 1900 MHz has 20 MHz LTE bandwidth support at 3GPP
band 2.
3-sector 3x 60 W RF Module general benefits:
• the most cost and size and weight optimized 3-sector BTS site
• industry leading RF integration level
• SW configurable radio: the same RF Module for LTE, HSPA+ and WCDMA and
GSM/EDGE
• 3 sector RF in one outdoor IP65 box
• Widest ambient temperature range -35... +55 C
• Smallest size and weight
• Smallest power consumption and OPEX
Prepared by Date Page
16.12.2013 14/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

• Can be used as feederless site as well with one DC and 1...2 optical cables
• TX div and MIMO 2TX can be build using two 3-sector RF Modules
o RF redundancy option comes as side bonus
• 0ne 3-sector Module always more cost effective than 3 x RF Head in feederless
installations because:
• Less weight
• Less wind load
• typically 1/3 of DC and optical cabling compared to site with Remote RF Heads (RRH)
• easier installation
• less visual impact
• RF Module can be used as powerful one sector RRH : 60 + 60 W 2TX MIMO with HW
prepared for 4RX

Functional Description:
3x 60 W output Flexi RF Module, IP65.
3GPP band 2 supported. 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 1TX/2RX
• 8, 20, 40 or 60 W mode per sector (by SW licenses)
• 1 sector max 60 + 60 W 2TX/2RX MIMO
• HW prepared for 1 sector max 60 + 60 W 2TX/4RX MIMO
• separate RET connector

Can be used in Feederless (DC up to 200 m) and Distributed (SM fiber up to 20 km, capacity
and number of optical cables TDB) BTS sites.
WCDMA and GSM/EDGE configurations are described in GSM/EDGE and WCDMA release
documents.

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 - - - 3GPP R8
mandatory

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 15/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

3.6 FXCB Flexi RF Module 850


Unique ID: 1695

Short Description:

Flexi Multiradio RF Module version for 850 MHz supporting three sectors with 80 W output
power at the BTS antenna connector. It can be used as one sector powerful RRH with 80 W +
80 W 2TX MIMO.

The environmental protection class is IP65.

Benefits for the Customer:


FXCB Flexi 3-sector RF Module 80 W 850 MHz has 25 MHz RF bandwidth support at 3GPP
band 5. HW supports Japanese 3GPP bands 5 and 19.
3-sector 3x 80 W RF Module general benefits:
• the most cost and size and weight optimized 3-sector BTS site
• industry leading RF integration level
• SW configurable radio: the same RF Module for LTE, HSPA+ and WCDMA and
GSM/EDGE
• 3 sector RF in one outdoor IP65 box
• Widest ambient temperature range -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
• TX div and MIMO 2TX can be build using two 3-sector RF Modules
o RF redundancy option comes as side bonus
• 0ne 3-sector Module always more cost effective than 3 x RF Head in feederless
installations -Less weight
• Less wind load
• typically 1/3 of DC and optical cabling compared to site with Remote RF Heads (RRH)
• easier installation
• less visual impact
• RF Module can be used as powerful one sector RRH : 80 + 80 W 2TX MIMO with HW
prepared for 4RX

Functional Description:
3x 60 W output Flexi RF Module, IP65.
3GPP band 5 supported. 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 1TX/2RX
o LTE BW support is limited by UE capability to max 10 MHz at Band 5 in 3GPP
• 8, 20, 40, 60, 80 W mode per sector (by SW licenses)
Prepared by Date Page
16.12.2013 16/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

• 1 sector max 80 + 80 W 2TX/2RX MIMO


• HW prepared for 1 sector max 80 + 80 W 2TX/4RX MIMO

Can be used in Feederless (DC up to 200 m) BTS sites.

WCDMA and GSM/EDGE configurations are described in GSM/EDGE and WCDMA release
documents.

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 - - - 3GPP R8
UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

3.7 LTE-GSM and LTE-WCDMA RF sharing for dual band and 4Rx
configurations
Unique ID: 1895

Short Description: This feature extends the existing functionality for LTE-WCDMA and LTE-
GSM RF sharing to scenarios with LTE dual band configurations and adds RF sharing
functionality for 4Rx receiver configurations. Additionally it adds the support of band 2
(1900MHz) for LTE-GSM sharing.

Benefits for the Customer:


This feature benefits the operator as follows:
• Easy and future proof BTS site evolution from WCDMA or GSM to multiband multi RAT
technology by using shared same Flexi Multiradio RF modules.
• Significant OPEX saving for the operator by shared usage of RF HW.
• No additional external combiners are required and multiple RA technologies can share
the same feeders and antennas in the same band.
• This feature helps the operator to allocate and share BTS RF resources between
WCDMA and LTE in a flexible way.
Prepared by Date Page
16.12.2013 17/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

This feature benefits the operator as follows:


• Easy and future proof BTS site evolution from WCDMA or GSM to multiband multi RAT
technology by using shared same Flexi Multiradio RF modules.
• Significant OPEX saving for the operator by shared usage of RF HW.
• No additional external combiners are required and multiple RA technologies can share
the same feeders and antennas in the same band.
• This feature helps the operator to allocate and share BTS RF resources between
WCDMA and LTE in a flexible way.

Functional Description:
In former releases the features LTE447 for RF sharing GSM and LTE435 for RF sharing
WCDMA-LTE were introduced.

This feature adds the support of LTE dual band configurations for RF sharing. On top of these
dual band configurations also LTE carrier aggregation might be configured if specific band
combination is supported by existing features (LTE1089 and LTE1332). Following shared dual
band configurations will be possible:

Band A: shared LTE-GSM + Band B dedicated LTE


Band A: shared LTE-WCDMA + Band B dedicated LTE
Feature LTE72 4-way RX diversity excludes the concurrent usage of RF-sharing and 4Rx
diversity. With this feature that restriction becomes obsolete and following 4Rx scenarios will be
supported by the LTE BTS:
• single band RF sharing with shared band in 4Rx mode
• dedicated LTE band is configured for 4Rx, shared band is in 2Rx mode

The primary links of shared RF units can be connected to RF ports 1..3 at the FSMF module.
The synchronization link to the peer system module is connected to port 6. The secondary links
to shared RF units are connected to any remaining port on FSMF or FBBA resp. FBBC.

The details regarding supported RFM and RRH types, bandwidth / power combinations are
defined in document: Flexi Multiradio BTS RF Sharing Released Configurations

HW Requirements: no specific HW requirements

Interdependencies between Features: One of the basic RF sharing features LTE435 or


LTE447 must be enabled

For dual band RF sharing with WCDMA WN8.0 3.0 is needed

For dual band RF sharing with GSM EX5.1.1.0.0 is needed (with SWCR 2279 implemented)

Dependency to other RATs: UTRAN, GSM

RL Software Dependencies:
Prepared by Date Page
16.12.2013 18/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

LTE BTS BTS NetAct OMS MME SAE UE


Flexi Flexi 10 GW
Release RL60 not LBTS6.0 - - -
supported

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 19/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

4 Transmission
4.1 IPv6 for U/C-Plane
Unique ID: 125

Short Description:

The eNB supports IPv6 for User-and Control- Plane The Management- and Synchronization-
Plane and also Site Support Equipment (SSE) remain with IPv4. The eNB supports IPv4 for the
IPSec tunnel layer.

Benefits for the Customer:


This feature supports migration of the mobile operator networks and IP transport networks from
IPv4 to IPv6.

Functional Description:
LTE application IP layer:
The eNB supports termination of user and control plane transport on IPv6 addresses. When
activated, it applies to all user and control plane addresses, i.e. only exclusive use of either IPv4
or IPv6 is supported (This means, there is no dual stack support for the application IP layer with
this feature).
Management-, synchronization application and SSE remain with IPv4 support only.

Note: Consequently the auto-connection procedure remains with IPv4 and uses DHCPv4.
LTE transport network layer: The eNB supports dual stack IPv4/IPv6 network interfaces. Both IP
versions can be used simultaneously.

Transport network requirements:

IPSec in use:
• IPv6 can be used solely at the application layer (thus not requiring IPv6 in the transport
network).
• Each IPSec tunnel pair between the eNB and the Security Gateway is using IPv4 in both
directions.

IPSec not in use:


• A dual stack transport network is required (IPv4 still required for management and
synchronization traffic).
In addition to the existing IPv4 host functions, the eNB supports the functions of an IPv6 host as
described in the following specifications:
• RFC 2460 Internet Protocol Version 6 (IPv6) Specification: Support of all IPv6 header
fields (except Flow Label), support of extension headers for Fragmentation,
Prepared by Date Page
16.12.2013 20/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Encapsulating Security Payload (acc. to RFC4303), hop-by-hop (router alert) and No


Next header
• RFC 4861 Neighbor Discovery for IP Version 6 (IPv6)
• RFC 4443 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version
6 (IPv6). Support of the following messages: neighbor solicitation/advertisement,
destination unreachable, time exceeded, parameter problem, echo request/reply (router
solicitation and advertisement are not supported)
• RFC 2464 Transmission of IPv6 Packets over Ethernet Networks
• RFC3810 Multicast Listener Discovery Version 2 (MLDv2) for IPv6
• RFC4862 IPv6 Stateless Address Autoconfiguration (for link-local addresses only), incl.

Duplicate Address Detection

The following limitations apply:


• IPv6 is not supported for management and synchronization plane termination,
• IPSec tunnels are not supported over IPv6,
• Path MTU Discovery (PMTUD) and ICMPv6 Redirects are not supported,
• Supported global unicast address prefix: 2000::/3..127
• Supported unique local unicast prefix: FC00::/7..127
• SLAAC (RFC4862) functionality is limited to generation of link-local addresses (no
further global addresses will be generated, as eNB does not process Router
Advertisement messages),
• Handovers between eNBs with different IP version in use are limited to S1-based
handovers with indirect forwarding.
Prepared by Date Page
16.12.2013 21/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements: FSME: Transport sub-module FTIB and FTLB is a future study item

FSMF with and without FTIF supported

Interdependencies between Features: N/A

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 future LBTS6.0 NetAct8 x x n/a
study EP1
item

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

4.2 IPSec Emergency Bypass


Unique ID: 1390

Short Description:

In case BTS detects a severe IPSec failure, IPSec at the BTS can be switched off in an operator
controlled way, not requiring any site visit. Switching back from IPSec Emergency bypass mode
to IPSec mode is exclusively controlled by operator.

Benefits for the Customer:


Feature allows limiting the network outage time in case of a severe IPSec cluster failure to a
minimum
• Once introduced, IPSec become a severe point of failure which can't be circumvented
• Security Gateway resilience is broadly implemented by operating a pair of GWs in a HA
(high availability) cluster, one GW being active, one being standby, with stateful failover
• Even the best resilience solution still poses the potential risk that unexpected failures
happen, which are thus not covered by the solution and might affect the whole HA
cluster
• If whole Security Gateway HA cluster fails larger area will go out of service
• In failure case it is not possible to deactivate IPSec in the BTS as BTS is managed
through the IPSec tunnel, thus BTS remains from O&M perspective not reachable
• In extreme, depending on duration of Security Gateway HA cluster failure situation, even
site visit would be required
Prepared by Date Page
16.12.2013 22/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Functional Description:
BTS supervises the status of the configured IPSec tunnels.
In case it cannot establish an IPSec tunnel or an established one becomes non-operational it
enters IPSec Emergency Bypass "probing state". During probing state the BTS
• continuously retries establishment of non-operational IPSec tunnels as specified in IPSec
standards
• periodically accesses an operator controlled server to check allowance for switching off
IPSec

The IP address of the Control Server and the timer that controls in what interval BTS accesses
the Control Server is configurable in BTS.
Entering "probing" state after failure occurrence will not take more than 5 minutes. Actual
duration depends on nature of the failure, IKE version and timer configuration with respect to

Dead Peer Detection.


In case BTS in "probing" state succeeds with its re-establishment attempts for all failed IPSec
tunnels, it will exit the "probing" state, stops accessing the Control Server and ignores return
messages from it.
IPSec Emergency Bypass state transition from "probing" to "active" happens if the Control
Server is reachable and provides the valid return message. Reach ability of this server is
controlled by the operator and in this sense is used as "switch" to allow the BTS to enter active
state. After having concluded a severe IPSec failure, the operator typically makes the Control
Server accessible by reconfiguration of the core network edge router and/or Security Gateway
in order to accept unprotected traffic.

When entering IPSec Emergency Bypass "active state" all traffic is sent unprotected to same
peers, using same VLAN ID, interface IP address, application IP addresses, default gateway
and firewall rules as before. Consequently only unprotected traffic is accepted in receive
direction.

"Active state" will last until it is either exited by an operator command via BTS management
interface or BTS reboot occurs. When leaving this state IPSec is operational again and BTS
tries to establish all IPSec tunnels as per configuration.

The feature does not support to switch off IPSec selective per tunnel endpoint, but switches off
IPSec completely. Thus it is not suited for scenarios where multiple Security Gateways are
connected to the BTS, e.g. in combination with feature LTE505 "Transport Separation for RAN
Sharing".
Prepared by Date Page
16.12.2013 23/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements:

Interdependencies between Features: Feature can only be applied in conjunction with


LTE689 LTE IPSec Support

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

4.3 Measurement based TAC


Unique ID: 1401

Short Description:

The Measurement Based Transport Admission Control (MBTAC) grants or rejects requests
based on measurement of the actually used transport bandwidth.

It is a functional enhancement of the feature LTE144 Transport Admission Control which is


based on book-keeping of estimated transport bearer bandwidths
Prepared by Date Page
16.12.2013 24/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Benefits for the Customer:


OPEX reductions due to the following:
• Simplified and less configuration work (preventing misconfiguration)
• No estimation on Traffic profiles and traffic mixes are needed for configuration of the
eNB
• Optimal e2e performance due to adaptive TAC behavior (in line with RAC).
• Best utilization of backhaul bandwidth with fully automatic adaption to changing traffic
profiles over the time (e.g. week or day).
• No manual optimizations needed in case of changing user traffic patterns, e.g. when
using new voice or video codec’s

Functional Description:
The measurement based TAC (MBTAC) is continuously measuring the actual traffic in DL and
UL. New calls (GBR services) are accepted or rejected, depending on the transport load
situation.

The following functional principles are used:


• Direct measurement of the actual outgoing (UL) and incoming (DL) GBR traffic rate at
the transport interface. GBR traffic is identified by the DSCP values of the IP packet.
Only the selected DSCP values are included in the measurement.
• The decision for acceptance or rejection of a new connection request is based on a
statistical evaluation of these measurements
• The traffic measurement carried out by MBTAC distinguishes the traffic by DSCP values.
Different sets of DSCP values are assigned to GBR and non-GBR services, such that
these can be distinguished unambiguously. With this guideline, any traffic type mixture of
GBR and non-GBR can be handled.
• Some of the parameters used for the currently used book-keeping algorithm will not be
needed anymore (e.g. average packet sizes, activity factors for QCI=1,2,3,4)
• In contrast to LTE144, MBTAC relies on measured user traffic, and not on traffic
estimations
• MBTAC avoids any assumptions about codec types (for voice or video)
• When using transport separation for RAN sharing (LTE505), one instance of TAC is
supported per operator. There is a configurable list of VLANs for each operator, defining
which VLANs are included into the measurements.
• PM counters e.g. for total number of connection requests, number of accepted and
rejected requests.

HW Requirements: N/A

Interdependencies between Features: Solution replaces LTE144 Transport Admission


Control

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Prepared by Date Page
16.12.2013 25/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

4.4 Local and Remote IP Traffic Capturing


Unique ID: 1460

Short Description:

• Capture ingress and egress IP traffic such as C-plane, U-plane, M-plane or S-plane
traffic

• Web interface for configuration and capture file retrieval, Layer 3 internal measurement
points can be selected and U-plane can be excluded to maximize capturing duration.

• For local use, trace is streamed to configurable TRS port or LMP. For remote use lipcap
file is create, compressed and downloaded by user.

• Feature ensure at least ~ 60s (for remote application) for highest capacity BTS IP traffic
for single UE use case and stores captured traffic in compressed Libcap file.

• IPv6 capturing is supported once available

Benefits for the Customer:


Operator User stories:
• As a maintenance engineer I want to capture the transport IP traffic related to a single
UE at a BTS/eNB in the field to calculate the KPIs, prove correct BTS/eNB behavior and
evaluate actual network performance. As an operator I want faults to be analyzed and
solved by the vendor as quickly as possible so that consequences are as minimal as
possible
• As a maintenance engineer I want to capture BTS/eNB traffic when being connected
remotely in order to investigate unexpected BTS/eNB behavior.
• As an engineer I want to locally capture BTS/eNB traffic over a period of up to several
days in order to investigate unexpected BTS/eNB behavior, support bug fixing and
customer trials.
• As a maintenance engineer I want to avoid extra site visits to retrieve transport capture
files so that I can save time, cost and effort.
Prepared by Date Page
16.12.2013 26/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

• As Technical Support engineer I want to have the transport capture files as often as
possible included to the ticket so that I can significantly reduce the ticket resolving times.
• As Technical Support engineer I want local unlimited IP traffic capturing including U-
plane headers so that I can cover all possible faults and use cases that require transport
traces
• As a maintenance engineer I want a robust and simple configuration interface so that I
configure the IP traffic capturing even in fault or congestion situations

Other benefits:
• In many fault scenarios mirrored or monitored traffic is required
• If IPSec is in use, unencrypted traffic trace is required
• To avoid site visits by customer or NSN service (which leads to reduced root analysis
times) remote monitoring is beneficial.
• Similar functionality is used very often in FSMr2
• With FSMr3 customer and our support expects at least same level of functionality
• FSMr3 is new HW and new SW and likely to contain faults

Functional Description:

• Web-gui for configuration for high reliability (BTS SM not acceptable) to select
measurement point and protocols Configure output port (local) or initiate file transfer
• capability to mirror into a libpcap file and fetch it compressed and password
protected via remote connection
• capability to mirror to other BTS/eNB port apart from LMP (if available)
• IPv6 support (if available in target release)
• mirroring of user plane header information (as configuration option)
• Mirroring duration minimum of 60s for single UE drive test incl. U-plane headers in
RL50/60 timeframe using IPv4 leads to requirement of 200MB RAM allocation (160 for
ring buffer, 40MB for libcap storage)
• Reserving a higher amount of memory should be possible at least for R and D
debugging purposes by e.g. starting the eNB SW with different parameters.
• The feature is designed to be RAT agnostic by adding a configurable cutting point inside
the packets. Default value should be behind LTE UE TCP header.
• Output only, creates no add. security leak e.g. through filtering or post-decryption
Prepared by Date Page
16.12.2013 27/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 not LBTS6.0 - - - n/a
supported

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

4.5 Timing over Packet with phase synchronization


Unique ID: 891

Short Description:

This feature provides phase synchronization of BTS through the packet network based on IEEE
1588-2008.

Phase synchronization is needed for TD LTE mode and optionally for GSM with frame
synchronization requirements to support the system features DFCA and OSC.

Benefits for the Customer:


Prepared by Date Page
16.12.2013 28/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The Timing over Packet (ToP) feature provides CAPEX/OPEX savings as separate TDM links
or GPS are not needed for providing a synchronization reference for the BTS with phase
synchronization, assuming that the Ethernet/packet network quality is sufficient.

Functional Description:
The Timing over Packet (ToP) solution consists of a Timing Master at the core site and Timing
Slaves implemented in the eNB's. The master and slaves communicate through the IEEE 1588-
2008 PTPv2 protocol. Accordingly, the master sends synchronization messages via the
Ethernet/packet network to the slaves. Bydirectional messaging operation is used:
• Sync messages in the direction from ToP Master to ToP Slave
• Delay Request/Delay Responses in the direction from ToP Slave to ToP Master.

Regarding the protocol stack and the Multicast/Unicast modes, the following two options can be
selected:
• PTPv2/Ethernet with Multicast operation. This mode is recommended for the network
scenario with IEEE1588 full on-path support: ToP Slave is directly connected to
IEEE1588 Boundary Clock.
• PTPv2/UDP/IP/Ethernet with Unicast operation. This mode is recommended for the
network scenario with only partial on-path support: ToP Slave is not directly connected
to an IEEE1588 Boundary Clock (BC). There are intermediate nodes which do not
support BC.

Used transport networks shall support IEEE1588v2 boundary clocks in either full on-path
support or partial on-path support.

HW Requirements: FSMF with and without FTIF transport sub-module

FSME (FTIB/FTLB) - future study item

Interdependencies between Features: Improves gain of LTE979 "IRC for 2 RX paths"

Mandatory for LTE426 System time broadcast for SIB8 and LTE495 OTDOA in case GPS is not
utilized and phase accuracy requirements are met.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 future LBTS6.0 NetAct8 - - n/a
study EP1
item
Prepared by Date Page
16.12.2013 29/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -
Prepared by Date Page
16.12.2013 30/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

5 Radio Resource Management and Telecom


5.1 LTE: Mobility
5.1.1 RSRQ triggered mobility
Unique ID: 1198

Short Description:

Inter-frequency and inter-RAT mobility based on RSRQ triggers.

Benefits for the Customer:


The RSRQ measurement trigger allows to better coping with high inter-cell interference
scenarios, e.g. due to missing neighbor cell relations or tight site re-use scheme in re-farming
scenarios.

Functional Description:
The Flexi Multiradio BTS supports beside the A2 RSRP trigger a parallel A2 RSRQ trigger in
order to start inter-frequency and IRAT measurements.
The termination of the inter-frequency and the inter-RAT measurements is extended in such a
way that the RSRP triggered A1 measurement report contains also a RSRQ measurement
which is compared with an operator configurable threshold. The report amount for the A1 event
is set to infinity.
The related inter-frequency or IRAT measurement events (e.g. A3, A5 or B2) remain
unchanged.
The functionality can be enabled / disabled per eNode B by O&M settings.

HW Requirements: no specific HW requirements

Interdependencies between Features: The related inter-frequency or inter-RAT mobility


features to need be enabled, e.g. LTE55 LTE56 LTE872 LTE1060 LTE60 LTE442 LTE873
LTE898

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 UE
capabilities
Prepared by Date Page
16.12.2013 31/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.2 Extended RNC ID


Unique ID: 1342

Short Description:

Support of extended RNC IDs

Benefits for the Customer:


Interworking with UTRAN networks using extended RNC IDs.

Functional Description:
The Flexi Multiradio BTS supports the extended RNC IDs for I-HSPA interworking.
The extended RNC ID IE is used within the S1AP:HandoverRequired message in case that the
RNC ID has a value larger than 4095.
A mix of extended and 'normal' RNC IDs per carrier frequency is not supported.
The UTRAN cell ID must be in this case in the range of 1...4095.

HW Requirements: Flexi MR10 BTS

Interdependencies between Features: The extended RNC IDs are applied for the following
features: PS HO to WCDMA (LTE56) CSFB to UTRAN (LTE736) SRVCC to UTRAN (LTE872)
ANR Inter-RAT UTRAN - fully UE based (LTE908)

Dependency to other RATs:

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 - LBTS6.0 - x - n/a

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 32/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

5.1.3 Enhanced CS fallback to CDMA/1xRTT (e1xCSFB)


Unique ID: 1441

Short Description:

Enhanced CS fallback to 1xRTT for CS services without concurrent PS handover

Benefits for the Customer:


CS fallback to 1xRTT with reduced service interruption time

Functional Description:
The Flexi Multiradio BTS supports an enhanced CS fallback to 1xRTT without concurrent PS
handover (Rel-9, e1xCSFB).
The network advertises its support for enhanced 1xCSFB by broadcasting 1xRTT pre-
registration and longCodeState1xRTT parameters in system information (SIB8) which is passed
on to CDMA upper layer in the UE. UE Capabilities are checked if UE supports enhanced CS
fallback to 1xRTT (e-CSFB-1XRTT-r9).

On receiving S1AP message(UE Context Modification or Initial UE Context Setup), the eNodeB
solicits 1xRTT measurements from the UE for e1xCSFB to 1xRTT, then eNodeB sends UE a
Handover From EUTRA Preparation Request message with an indication that concurrent HRPD
handover preparation is not required. This triggers the UE to send UL Handover Preparation
Transfer message containing 1xRTT dedicated information for CS fallback.
The response from the 1xRTT network triggers the eNodeB to send mobility from EUTRA
Command message to the UE with indication that this is for enhanced 1x CS Fallback operation
received over the S102 tunnels. Without concurrent PS HO enabled, E-UTRAN sends an S1 UE
Context Release Request (Cause: Redirection towards 1xRTT) message to the MME.
UE retunes to the 1xRTT radio access network and performs 1xchannel acquisition with the
1xRTT CS access.

1xRTT CS Pre-Registration
• A 1xCSFB capable terminal may pre-register in the 1xRTT network via the E-UTRAN in
order to establish CS services (e.g. originating and terminating voice calls) in the 1xRTT
network.
• The UE determines whether pre-registration is needed based on 1xRTT pre-registration
parameters broadcast in system information (SIB8). Before performing a 1xRTT pre-
registration, the UE requests from the eNodeB the necessary information to perform the
1xRTT pre-registration using the CDMA2000 CSFB Parameters Request message. The
eNodeB provides the necessary parameters in the CDMA2000 CSFB Parameters Response
message. These necessary parameters (RAND, MobilityParameters) are O&M pre-
configured in the eNodeB and are transparent to E-UTRAN.
• The UE is responsible for maintaining the 1xRTT context, e.g. by performing re-registrations
if needed. The management of the pre-registration and re-registration is handled by the
1xRTT upper layer in the UE.
Prepared by Date Page
16.12.2013 33/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The eNodeB supports the following messages for enhanced CS fallback to 1xRTT:
• The RRC:CSFBParametersRequestCDMA2000 message and
• the RRC:CSFBParametersResponseCDMA2000 message are supported between the
UE and the eNodeB.
• the RRC:ULInformationTranfer message and
• the RRC:DLInformationTransfer message are supported between the UE and the
eNodeB.
• the RRC:HandoverFromEUTRAPreparationRequest message and
• the RRC:ULHandoverPreparationTransfer message are supported between the UE and
the eNodeB.
• the RRC: MobilityfromEUTRACommand message is supported from eNodeB to UE
• the S1AP:DownlinkS1CDMA2000Tunneling message and
• the S1AP:UplinkS1CDMA2000Tunneling are supported between the eNodeB and the
MME.

The eNodeB supports the following message for redirection based basic CS fallback to 1xRTT:
• The RRC: RRCConnectionRelease message is supported from eNodeB to UE.

The following scenarios are supported:


• Mobile originated CSFB with a UE in RRC_IDLE
• Mobile originated CSFB with a UE in RRC_CONNECTED
• Mobile terminated CSFB with a UE in RRC_IDLE
• Mobile terminated CSFB with a UE in RRC_CONNECTED
• Emergency Calls
• Priority calls
• Mobile originating SMS
• Mobile terminating SMS

The MO/MT SMS are tunneled over S102 and does not trigger any CS Fallback to 1xRTT, and
does not require LTE coverage overlapped by CDMA 1xRTT coverage (assumes UE has
already pre-registered with 1xRTT in an area of LTE and 1xRTT overlap).

As prerequisite, the EPC must support CS inter-working for mobility management and paging.
The eNodeB forwards the 1xRTT CS paging request to the UE for mobile terminated CS
fallback. The MME triggers in all above cases the CS Fallback procedure at the eNodeB by
sending the IE CS Fallback Indicator within the S1AP:UE Context Modification Request or Initial
UE Context Request message to the eNodeB. when eNodeB receives a CS fallback priority
indication from MME in S1AP messages with CS Fallback High Priority, eNodeB will handle call
as Emergency Call(that means, priority call will also be taken as emergency call during
e1xCSFB procedure), otherwise it will be handled as a normal call.
The eNodeB solicits an IRAT reportstrongestcells measurement report from the UE with 1xRTT
frequency and transfer to 1xRTT network to assist the target 1xRTT channel assignment for CS
fallback to 1xRTT.

In the measurement configuration, reportAmount shall be set to one. QuantityConfig shall be set
as pilotPnPhaseAndPilotStrength. The following parameters (CarrierFreq, searchWindowSize,
Prepared by Date Page
16.12.2013 34/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

physCellId (whitelisting)) in measurement object are O&M configurable. Each measurement will
be guarded by a supervision timer. If no measurement report received before timer expiry,
redirection will be used for CS fallback to 1xRTT/CDMA.
For UEs not support enhanced CS fallback to 1xRTT, the network will use 1xCSFB via RRC
connection release with redirection without measurement.

The following performance counters are supported, e.g.:


• UE Context modification attempts
• UE Context modification failures
• CS Fallback attempts with MobilityFromEUTRACommand(UE in idle mode, UE in
connected mode)
• CS Fallback attempts for emergency call(including priority call) with
MobilityFromEUTRACommand(UE in idle mode, UE in connected mode)
• CS Fallback attempts with RRC Connection Release (UE in idle mode, UE in connected
mode)
• CS Fallback attempts for emergency call with RRC Connection Release (UE in idle
mode, UE in connected mode)

Enhanced CS fallback to 1xRTT (Rel-9, e1xCSFB) or basic CS fallback to 1xRTT (Rel-8,


Redirection based without measurement) could be configured by O&M for CS Fallback to
1xRTT/CDMA.
The operator can enable / disable the functionality per eNode B by O&M setting.

HW Requirements: Not supported for FSMD/FSME

Interdependencies between Features: LTE807 Idle mode mobility LTE to cdma /1xRTT needs
to be enabled.
Prepared by Date Page
16.12.2013 35/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Only EUTRAN and CDMA target layer will be supported, and all other RATs(GSM/WCDMA/TD-
SCDMA) are excluded.

Dependency to other RATs: CDMA

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 - LBTS6.0 NetAct8 x - 3GPP R9
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.4 Inter-frequency load balancing extension


Unique ID: 1531

Short Description:

The scope of UEs considered for load balancing is increased.

Benefits for the Customer:


The number of UEs considered for load balancing is increased which leads to a higher
likelihood for off-loading a cell.

Functional Description:
The feature introduces the following two extensions for LTE1387 and/or LTE1170:
A periodic retry of load balancing for RRC connected users is applied in case that
• the load balancing handover was not successful,
• the load balancing handover preparation was not successful or
• the UE has not provided an A4 measurement report.
The retries are performed as long as the source cell is at high load. The retry timer is operator
configurable.
UEs enter a cell via a handover are considered as well for inter-frequency load balancing.

HW Requirements: no specific HW requirements

Interdependencies between Features: The feature is enabled together with LTE1387 or


LTE1170.

Dependency to other RATs:


Prepared by Date Page
16.12.2013 36/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 mandatory

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.5 Multiple Frequency Band Indicator


Unique ID: 1534

Short Description:

Intra-LTE MFBI functionality is introduced.

Benefits for the Customer:


The functionality allows to handle UEs with overlapping bands in one network.

Functional Description:
The Flexi Multiradio BTS supports Multiple Frequency Band Indicators (MFBIs) for UEs in RRC
IDLE and UEs in RRC CONNECTED. The MFBI functionality is supported
for homogenous network deployments, i.e. the same MFBI configuration is applied to all eNode
Bs.
All MFBI related parameters are configured via O&M.
MFBI support for UE in RRC IDLE

The following SIBs are supported for the MFBI:


• SIB 1,
• SIB 2 and
• SIB 5.

One band can be configured for the different multiBandInfo list information elements.

MFBI support for UEs in RRC CONNECTED


UEs supporting MFBI and an overlapping RF band in the RF parameter information element of
the UE capabilities are considered for the following functions (if enabled)
• RRC connected mobility (inter-frequency handover, RRC connection release with
redirect and RRC connection release with dedicated priorities)
• ANR (intra-frequency ANR, inter-frequency ANR)
• Carrier Aggregation
The eNode B uses in the above cases the EARFCN which matches to the UE capabilities.
Prepared by Date Page
16.12.2013 37/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The functionality can be enabled / disabled per eNode B by O and M settings.

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.6 Idle mode mobility balancing extensions


Unique ID: 1677

Short Description:

A weighted round robin scheme is introduced for the idle mode mobility balancing target
selection.

Benefits for the Customer:


A multi-frequency balancing scheme for RRC IDLE UEs is introduced.

Functional Description:
The Flexi Multiradio BTS supports for the default and the mobility profiles the following
extensions for LTE487:
A weighted round robin scheme to select the target layer to which a UE shall be released with
dedicated cell re-selection priorities is replacing the LTE487 scheme. The ratio of UEs for which
the IDLE load balancing is applied is controlled by O&M settings.
A weighting factor is introduced for each configured intra LTE and inter-RAT cell re-selection
target.

The eNode B sends all transmitted SIBs with the RRC: RRC Connection Release message. The
highest priority is automatically assigned to the target frequency. The hierarchy of all other cell
re-selection priorities is maintained.
The functionality is enabled together with LTE487.
Prepared by Date Page
16.12.2013 38/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements: no specific HW requirements

Interdependencies between Features: The feature is enabled together with LTE487 Idle
mode mobility load balancing.

Mobility profiles can be used only if LTE490 Subscriber profile based mobility has been enabled.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.7 RAN Information Management for GSM


Unique ID: 498

Short Description:

RAN information management (RIM) allows to transfer information between the source and
target cell via the core network. This mechanism allows for a reduction of parameter setting.

Benefits for the Customer:


The operator needs to configure less parameter for the network assisted cell change or the
RRC connection release with redirect and SIB.

Functional Description:
The Flexi Multiradio BTS supports the RAN information management (RIM) for NACC to GSM.
The eNode B acts always as a controller.
The RIM function enables the eNode B to retrieve system information from a target GSM cell:
• if a PBCCH is allocated in the cell, PSI1, PSI2, PSI14
• if no PBCCH is allocated in the cell, SI1, SI3, SI13
The RIM protocol is encapsulated in the S1AP.MME DIRECT INFORMATION TRANSFER and
the S1AP:ENB DIRECT INFORMATION TRANSFER messages.
The retrieved information is used to automatically fill and update the related SIB attributes for
the features:
• eNACC to GSM or
• RRC Connection Release with redirect and SIB.
Prepared by Date Page
16.12.2013 39/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The following RIM procedures are supported:


• RAN Information Request/Multiple Report procedure
• RAN Information Request/Stop procedure
• RAN Information Send procedure
• RAN Information Application Error procedure
• RAN Information Error procedure
The functionality can be enabled / disabled per eNode B by O&M setting.

HW Requirements:

Interdependencies between Features: The feature LTE42 DRX in RRC Connected Mode or
LTE984 GSM Redirect with System Infoneeds to be enabled.

Dependency to other RATs: GSM

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - 3GPP R8
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.8 Inter RAT handover from UTRAN


Unique ID: 57

Short Description:

Active mode mobility from UTRAN to LTE

Benefits for the Customer:


The end user may experience better service quality, e.g. peak rates and latency, in LTE as in
UTRAN.

Functional Description:
The Flexi Multiradio BTS supports incoming PS handovers from UTRAN to LTE.
The handover procedure is initiated by the RNC.
The Flexi Multiradio BTS gets during the handover preparation phase a S1AP:HANDOVER
REQUEST message from the MME.
Prepared by Date Page
16.12.2013 40/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The Flexi Multiradio BTS applies the same admission control thresholds for the handover
request as for other incoming mobility handovers, e.g. intra LTE handovers, and either
acknowledges or rejects the handover request.
The RNC issues after a successful handover preparation phase a handover command to the UE
with embedded RRCConnectionReconfiguration information.
The UE performs an access to LTE and finalizes the handover with a
RRC:RRCConnectionReconfigurationComplete message to the eNode B.
The Flexi Multiradio BTS sends afterwards a S1AP:HandoverNotify message to the MME.
The handover is performed without data forwarding.
The MME may trigger after a successful handover a security key update via the
S1AP:ContextModificationRequest message. The eNode B performs the security key update via
an intra-cell handover.
The feature can be enabled/disabled per BTS by O&M settings.

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: UTRAN

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x x 3GPP R8
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.9 Inter RAT handover to eHRPD/3GPP2


Unique ID: 60

Short Description:

Coverage based prepared inter RAT handover from LTE to CDMA2000 eHRPD

Benefits for the Customer:


Reduced service interruption time
Prepared by Date Page
16.12.2013 41/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Functional Description:
The LTE to eHRPD optimized handover functionality of the Flexi Multiradio BTS allows for a
service continuity of data services with minimal interruption time when changing from a LTE cell
to a CDMA2000 eHRPD cell.
The functionality is only applicable for multimode devices supporting both LTE and CDMA2000
eHRPD for the according frequency band and the according feature support.
Pre-registration

The UE initiates the pre-registration to the CDMA2000 eHRPD Access.


The eNode B provides up to three operator configurable Zone ID for the pre-registration either in
SIB8 for RRC Idle UEs or in the measurement configuration IE for RRC Connected UEs. The
three Zone IDs (Primary Zone ID and two Secondary Zone IDs) are operator configurable per
cell. The same Zone IDs are applied for SIB 8 and the measurement configuration. However
different preRegistrationAllowed flags can be configured for SIB8 and the measurement
configuration.
The eNode B supports the following messages for the pre-registration:
• the RRC:ULInformationTranfer message and
• the RRC:DLInformationTransfer message are supported between the UE and the eNode
B.
• the S1AP:DownlinkS1CDMA2000Tunneling message and
• the S1AP:UplinkS1CDMA2000Tunneling are supported between the eNode B and the
MME.
The eNode B adds during the pre-registration procedure a CDMA2000 Sector ID to the
S1AP:UplinkS1CDMA2000Tunneling message.
The sector ID for the pre-registration is selected with a weighted round robin mechanism out of
an operator configurable pool of sector IDs.

Handover trigger
The handover is a network controlled handover with support of the UE.
The following measurement events are used:
• A1 - deactivate IRAT/IF measurements (RSRP)
• A2 - activate IRAT eHRPD measurements (RSRP)
• B2 - IRAT eHRPD measurements
The operator configurable measurements events A2 and A1 are used to start and stop IRAT
measurements.
The UE capabilities are considered for the IRAT measurements, e.g. UE support of
measurement gaps and UE support of the target cell frequency band. The measurement gap
gp0 is used.
The target cells for the IRAT measurements are operator configurable. The operator can select
whether cells shall be considered for IRAT measurement or not. A target cell load balancing
between different frequency layers is applied for the initial target frequency considering operator
configurable weights. The selection valid as long as the UE is RRC CONNECTED in the same
cell.
The B2 measurement configuration of the source cell thresholds (RSRP), target cell threshold
(pilotStrength), hysteresis (specific to eHRPD), time to trigger (specific to eHRPD) and speed
dependent scaling are operator configurable on a per eHRPD carrier basis.
Prepared by Date Page
16.12.2013 42/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Handover
The Flexi Multiradio BTS initiates the optimized eHRPD handover after receiving a B2
measurement report from the UE.
Upon receiving a B2 measurement report, the eNode B takes the first target cell indicated by the
UE measurements for the handover to eHRPD.
The handover comprise of the following steps:
• A RRC:HandoverFromEUTRAPreparationRequest message is send to the selected UE.
• The content of the response message from the UE
(RRC:ULHandoverPreparationTransfer) is forwarded with the
S1AP:UplinkS1CDMA2000Tunneling message via the MME to the CDMA2000 HRPD
Access. The CDMA2000 Sector ID is set to the first target indicated by the UE
measurement report. The S1AP:UplinkS1CDMA2000Tunneling message also contains
the EUtran Round Trip Delay Estimation IE.
• The CDMA200 HRPD Access provides the respones via the
S1AP:DownlinkS1CDMA2000Tunneling message.
• The eNode B sends in case of a positive handover preparation response a
RRC:MobilityFromEUTRA message to the UE. The UE leaves LTE and starts to
establish a traffic channel to CDMA2000 HRPD Access.
• The eNode B receives in case of a successful handover a
S1AP:UEContextReleaseCommand message.
A non optimized handover to eHRPD is performed in case that the UE does not support an
optimized handover to eHRPD.
The Flexi Multiradio BTS supports the following counters per cell in order to track the
performance:
• Inter System Handover preparations
• Failed Inter System Handover preparations per cause
• Inter System Handover attempts
• Successful Inter System Handover completions
• Failed Inter System Handover per cause
• Number of B2 measurement configurations
• Number of received B2 measurement reports
The handover functionality can be enabled or disabled per eNode B by O&M settings.

HW Requirements: Future study item for FSMD/FSME

Interdependencies between Features: The feature requires the support of GPS time retrieval.

LTE426 System time broadcast for SIB8 and LTE870 Idle mode mobility from LTE to
CDMA/eHRPD needs to be enabled

WCDMA and GSM mobility cannot be enabled in parallel with this functionality (LTE56, LTE872,
LTE873, LTE442, and LTE736).

Mobility profiles LTE490 are not supported for this feature.

Dependency to other RATs: CDMA


Prepared by Date Page
16.12.2013 43/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 future LBTS6.0 NetAct8 x x 3GPP R8
study EP1 UE
item capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.1.10 CSFB to CDMA/1xRTT for dual RX UEs


Unique ID: 874

Short Description:

Service continuity for CS voice.

Benefits for the Customer:


Redirected call setup for voice calls

Functional Description:
The Flexi Multiradio BTS supports a redirect based CS fallback (CSFB) to CDMA/1xRTT for
dual receiver multimode UEs.
The eNode B indicates with the SIB 8 the related capabilities to the UE.
The following scenarios are supported:
• Mobile originated CSFB with a UE in RRC CONNECTED
• Mobile terminated CSFB with a UE in RRC CONNECTED
The MME triggers in both cases the CSFB procedure at the eNode B by sending the IE CSFB
with the S1AP:UE Context Modification Request message to the eNode B.
The eNode B performs upon the CSFB trigger a RRC connection release without redirect
information for UEs.
There is no need for redirect information or measurements as the UE is already attached to
CDMA/1xRTT.

The following performance counters are supported, e.g.:


• UE Context modification attempts
• UE Context modification failures UE Context modification attempts due to CS Fallback
• CS Fallback attempts with RRC Connection Release
• CS Fallback attempts (UE in Connected Mode) with RRC Connection Release

The operator can enable / disable the functionality per cell by O&M setting.
Prepared by Date Page
16.12.2013 44/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements: no specific HW requirements

Interdependencies between Features: LTE807 or LTE870 needs to be enabled for SIB 8


transmission.

Dependency to other RATs:

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - 3GPP R9
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW Pool license Long-term ON/OFF BTS
license
Prepared by Date Page
16.12.2013 45/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

5.2 LTE: Coverage, capacity and peak rates


5.2.1 Downlink carrier aggregation - 40 MHz
Unique ID: 1332

Short Description:

Enabling downlink peak rates of up to 300 Mbit/s.

Benefits for the Customer:


Increase downlink peak rates of up to 300 Mbit/s.

Functional Description:
The Flexi Multiradio BTS supports carrier aggregation in downlink for two component carriers
(CC) of up to 20 MHz cell bandwidth each and two non aggregated uplink cells as an extension
to LTE1089. A mix of non carrier aggregation UEs and carrier aggregation UEs is supported in
downlink. The maximum aggregated downlink bandwidth is 40 MHz
The additional band combinations for the deployment scenario 1 and 2 described by 3GPP TS
36.300 are:
• band 2 + band 4
• band 2 + band 5
• band 2 + band 17
• band 3 + band 3 (non contiguous, contiguous)
• band 3 + band 7
• band 3 + band 20
• band 4 + band 4 (non contiguous, contiguous)
• band 7 + band 20
• band 4 + band 12
• band 4 + band 17
• band 3 + band 28
• band 4 + band 7
• band 5 + band 12
• band 7 + band 7

The additional cell bandwidth combinations are supported (as well for cell bandwidth
combinations introduced by LTE1089):
• 5 MHz + 15 MHz
• 5 MHz + 20 MHz
• 10 MHz + 15 MHz
• 10 MHz + 20 MHz
• 15 MHz + 15 MHz
• 15 MHz + 20 MHz
• 20 MHz + 20 MHz
Prepared by Date Page
16.12.2013 46/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Please note that only 3GPP defined cell band and cell bandwidth combinations are tested and
released.
The two component carriers can have different MIMO settings, e.g.
• 2x2 MIMO + 2x2 MIMO
• 4x2 MIMO + 2x2 MIMO
• 4x2 MIMO + 4x2 MIMO
The functionality can be enabled or disabled per eNode B by O&M setting.

HW Requirements: Not supported for FSMD/ FSME

Interdependencies between Features: The feature is enabled together with LTE1089 DL


Carrier Aggregation - 20 MHz

In RL50 the following features are excluded from the interworking in parallel with LTE1089
carrier aggregation LTE4 MOCN, LTE568 MIMO 4x2, LTE72 4RX diversity and LTE1542
Supercell. In RL60 these restrictions are removed for LTE1089 and LTE1332.

The parallel use of LTE1089/1332 and LTE1542 Supercell is possible in RL60 under the
following conditions:

• Baseband HW platform is Flexi MR 10 BTS

• LTE1542 is enabled on both aggregated supercells.

• Both aggregated supercells have 10 MHz bandwidth.

• Both Supercells have overlapping coverage

(This will not been verified by Optimizer)

A mixed configuration i.e. a Supercell on one frequency layer and a normal cell or a RIU
configuration on the other frequency layer is not supported.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 - LBTS6.0 NetAct8 - - 3GPP R10
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -
Prepared by Date Page
16.12.2013 47/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

5.2.2 Interference aware UL power control


Unique ID: 1336

Short Description:

Improved uplink cell capacity and cell edge performance through interference aware closed loop
uplink power control.

Benefits for the Customer:


A higher uplink cell capacity and improved cell edge throughput can be used for providing
additional services and better service coverage.

Functional Description:
The Flexi Multiradio BTS supports interference aware uplink power control algorithm for
PUSCH.

The eNode B controls the UE specific transmit power such that the tradeoff between the
throughput achieved in the own cell and the uplink interference injected to neighbor cells is
optimized. The eNode B uses UE as well as eNode B measurements as input for the algorithm.

The functionality can be enabled or disabled per cell by O&M setting.

HW Requirements: no specific HW requirements

Interdependencies between Features: LTE28 Closed loop UL power control needs to be


enabled for SRS and PUCCH power control. The feature replaces the PUSCH power control.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 mandatory

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -
Prepared by Date Page
16.12.2013 48/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

5.2.3 Uplink intra eNode B CoMP


Unique ID: 1402

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 50% cell edge improvement compared to a 2RX
receiver.

Functional Description:
The Flexi Multiradio BTS supports uplink intra eNode B CoMP. The uplink intra eNode B CoMP
functionality is applied for cells with 2RX 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 or disabled per eNode B by O&M setting.

HW Requirements: Not supported on FSMD/FSME

Interdependencies between Features: LTE979 IRC for 2 RX paths (FDD) or LTE936 IRC for
2 RX paths (TDD)needs to be enabled.

The feature is not supported in combination with

LTE614 distributed sites, LTE48 High speed users, LTE117 1.4 MHz, LTE116 3 MHz, LTE72 4-
way RX diversity, LTE980 IRC for 4 RX paths, LTE993 TDD Supercell and LTE1542 FDD
Supercell.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 - LBTS6.0 NetAct8 - - 3GPP R8
EP1 mandatory
Prepared by Date Page
16.12.2013 49/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.2.4 Fast uplink link adaptation


Unique ID: 1495

Short Description:

Improved uplink performance due to faster link adaptation

Benefits for the Customer:


Beside the Link Adapation being generally faster and thus providing better throughput, an
important side effect is an early reliable assessment of the UL Modulation and Coding Scheme,
which is beneficial especially at handover.

Functional Description:
The Flexi Multiradio BTS introduces with this feature a fast inner loop uplink link adaption
algorithm for the PUSCH in addition to the slow outer loop link adaption (LTE1034). The fast
inner loop link adapation uses sounding reference signal (SRS) information, when configured for
the UE, as well as channel state information derived from regular PUSCH transmission in order
to perform a fast upgrade of the selected modulation and coding scheme (MCS).

The feature can be enabled or disabled per cell by O&M settings.

HW Requirements: no specific HW requirements

Interdependencies between Features: LTE1034 Extended Uplink Link Adaptation needs to be


enabled

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 mandatory
Prepared by Date Page
16.12.2013 50/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.2.5 PUSCH masking


Unique ID: 944

Short Description:

Mask PRBs which should not be used for scheduling

Benefits for the Customer:


PUSCH masking provides a flexible tool to handle uplink interference problems, e.g. static re-
use schemes.

Functional Description:
The Flexi Multiradio BTS supports O&M based masking of PRBs for PUSCH in the frequency
domain scheduler. The PRB mask is treated by the uplink scheduler as permanent virtual users
blocking certain PRBs.
The PRB mask itself is operator configurable per cell.
The PRB mask cannot be used in combination with SRS.
PRACH regions cannot be masked.

The usage of the PRB mask may lead to a


• decreased peak rate for 'normal' users
• less frequency diversity for 'normal' users as the uplink scheduler is restricted in random
hopping
• less fair resource assignment
The feature can be enabled or disabled per cell by O&M settings.

HW Requirements: no specific HW requirements

Interdependencies between Features: LTE46 and LTE1495 can be enabled together with this
feature but only PUSCH information will be used. SRS will not be used.

The following feature are not supported in combination with this feature: LTE117 1.4 MHz cell
bandwidth LTE116 3 MHz cell bandwidth LTE115 5 MHz cell bandwidth

Dependency to other RATs: No dependency

RL Software Dependencies:
Prepared by Date Page
16.12.2013 51/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

LTE BTS BTS NetAct OMS MME SAE UE


Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.3 LTE: QoS, services and end user experience


5.3.1 Multimedia priority services
Unique ID: 1074

Short Description:

Priority controlled admission and paging priority handling.

Benefits for the Customer:


Access prioritization for emergency calls and high priority users

Functional Description:
The Flexi Multiradio BTS supports admission control for high priority calls and paging
prioritization. The paging priority handling considers the paging priority provided by the
S1AP:paging message. UEs with a higher paging priority are preferred over UEs with a lower
priority for the assignment of paging resources. A subsequent RRC connection request from an
UE which has been paged with a paging priority is admitted like an emergency RRC connection
request. High priority access UEs are identified either by the RRC connection establishment
cause value 'High Priority Access' or by a dedicated operator configurable high priority ARP
value range associated to a data radio bearer. High priority calls are treated as emergency calls
during admission control in serving cell and in target cell. They are treated as normal calls at
handover target selection.
The following PM counters are supported per cell, e.g.:
• Number of signaling connection establishment attempts for high priority calls
• Signaling connection establishment completions for high priority calls
• E-RAB setup requests for high priority calls
• E-RAB setup completions for high priority calls
The functionality can be enabled / disabled per eNode B with its subordinated cells by O&M
setting.

HW Requirements: no specific HW requirements


Prepared by Date Page
16.12.2013 52/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Interdependencies between Features: The following features need to be enabled:

LTE572 IMS Emergency Session

LTE534 ARP based Admission Control

LTE496 Support of QCI 2,3,4

LTE497 Smart Admission Control

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - 3GPP R8
EP1 mandatory

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.3.2 Operator specific GBR QCIs


Unique ID: 1231

Short Description:

The operator can define its own QoS profiles for GRB EPS bearers.

Benefits for the Customer:


The operator specific QCIs allow for better user and service differentiation of GBR services.

Functional Description:
Up to 21 operator specific QCIs for GBR EPS bearers are supported per eNode B.
The QCI value for each QCI is operator configurable in the range from 128 to 254.
Each operator specific QCI is defined by at least the following set of parameters:
• QCI value
• RLC profile
• PDCP profile
• DRX profile (DRX functionality needs to be enabled)
• Delay target
• Priority
• logical channel group ID
• DSCP
Prepared by Date Page
16.12.2013 53/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

• scheduling priority
• BSD (bucket size duration)
• TTI bundling enforcement (TTI bundling needs to be enabled)

The PM counter groups for non GBR QCIs are applied as well to operator specific GBR QCIs.
Operator specific GBR bearers are treated by admission control as standard GBR bearers.
Robust header compression is not applied for operator specific GBR QCIs.
The support of operator specific GBR QCIs can be enabled / disabled per eNode B by O&M
settings.

HW Requirements: no specific HW requirements

Interdependencies between Features: The following features need to be enabled: LTE496


Support of QCI 2, 3 and 4 LTE497 Smart admission control LTE534 ARP based admission
control for E-RABs

Dependency to other RATs:

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - 3GPP R8
EP1 mandatory

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.3.3 Cell resource groups


Unique ID: 1382

Short Description:

The cell resource groups allow to virtually split the cell resources.

Benefits for the Customer:


The operator is able to pre-define resource shares in case of MOCN or national roaming.

Functional Description:
The Flexi Multiradio BTS provides a resource split control function for up to four resource
groups. A resource group can be assigned to a single or multiple PLMN IDs configured per cell

The total cell capacity is divided up according to an operator configurable share of the resource
groups with a 1% step size granularity, e.g. 30% - 40% - 30% in case of three resource groups.
Prepared by Date Page
16.12.2013 54/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The resource split can be configured on cell level. O&M consistency check ensures a share
configuration to 100%. Not assigned PLMN-IDs will be mapped to a default CRG.

The resource group share is applied to


• admission control thresholds (exception: RRC connection requests),
• TTI assignments for PDSCH and PUSCH and
• Congestion control for GBR traffic

The uplink resource split can be disabled via O&M. The resource split affects the admitted GBR
rates. The pre-emption functionality at the radio admission control considers the resource group,
i.e. pre-emption is done within the resource group (LTE534 needs to be enabled). Congestion
handling is as well done per resource group. The resource shares are as well applied for
emergency sessions. Emergency sessions without a resource group assignment are mapped to
a default resource group. TTIs not used by a resource group are automatically reused by other
resource groups. Almost empty TTIs might be deferred in scheduling as long as the timing
constrains are met.

The following performance counters are provided in order to track the performance per resource
group, e.g.
• number of used TTIs per direction and resource group,
• number of available TTIs in UL and DL in total per measurement interval.

The functionality can be enabled / disabled per cell by O&M setting.

HW Requirements: Future study item for Flexi MR10K BTS

Interdependencies between Features: The interworking with the following features is not
supported:

LTE1387 / LTE1170 - Inter-frequency load balancing LTE115 - Cell bandwidth - 5 MHz LTE116
- Cell bandwidth - 3 MHz LTE117 - Cell bandwidth - 1.4 MHz LTE616 - Usage based PDCCH
adaptation LTE907 - TTI bundling in combination with cell resource groups in uplink Asymmetric
TD LTE frame configurations with cell resource groups in uplink The following features needs to
be enabled:

LTE 496 Support of QCI 2,3 and 4 LTE 497 Smart admission control LTE 534 ARP based
admission control

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 mandatory
Prepared by Date Page
16.12.2013 55/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.3.4 LPPa support for OTDOA


Unique ID: 1433

Short Description:

The eNode B signals OTDOA related settings via the S1AP to the eSMLC.

Benefits for the Customer:


The functions allows the eSMLC to automatically retrieve OTDOA related parameters from the
eNode B.

Functional Description:
The Flexi Multiradio BTS supports the LPPa OTDOA information request procedure via the
S1AP.

The LPPa protocol is encapsulated in the S1AP:Downlink Non UE Associated LPPa Transport
rsp. S1AP:Uplink Non UE Associated LPPa Transport message.

The following LLPa messages are supported:


• OTDOA Information Request
• OTDOA Information Response
• OTDOA Information Failure
The following OTDOA cell information elements are supported:
• PCI
• Cell ID
• TAC
• EARFCN
• PRS Bandwidth
• PRS Configuration Index
• CP Length
• Number of DL Frames
• Number of Antenna Ports
• SFN Initialization Time
• EUTRAN Access Point Position (O&M configured)
• PRS Muting Configuration
The functionality can be enabled / disabled per eNode B by O&M setting.

HW Requirements: no specific HW requirements


Prepared by Date Page
16.12.2013 56/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Interdependencies between Features: LTE495 OTDOA needs to be enabled.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - 3GPP R9
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.3.5 Multiple emergency areas per cell


Unique ID: 1755

Short Description:

Support of multiple emergency area IDs per cell.

Benefits for the Customer:


Support of multiple emergency area IDs per cell.

Functional Description:
The Flexi Multiradio BTS allows to configure up to 15 emergency area IDs per cell for CMAS or
ETWS. The emergency area IDs are used to check if emergency messages need to be
broadcasted in a cell.

The emergency area IDs can be different for different cells.

HW Requirements: no specific HW requirements

Interdependencies between Features: LTE843 or LTE494 needs to enable.

Dependency to other RATs: No dependency


Prepared by Date Page
16.12.2013 57/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - 3GPP R8
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

5.3.6 8 EPS bearers per UE


Unique ID: 520

Short Description:

Up to eight EPS bearers can be established per UE.

Benefits for the Customer:


The operator is able to offer an always-on service with multiple concurrent sessions.

Functional Description:
The Flexi Multiradio BTS supports up to eight EPS bearers for multiple-bearer capable UEs.
The UE indicates its capabilities with a feature bit in the UE capabilities.

The following radio bearer combinations per UE are supported by the Flexi Multiradio BTS:
• SRB1 + SRB2 + 6 x AM DRB
• SRB1 + SRB2 + 7 x AM DRB
• SRB1 + SRB2 + 8 x AM DRB
• SRB1 + SRB2 + 5 x AM DRB + 2 x UM DRB
• SRB1 + SRB2 + 5 x AM DRB + 3 x UM DRB

Multiple DRB (data radio bearers) can be either multiple default EPS bearers or a combination
of default and dedicated EPS bearers.
The Flexi Multiradio BTS provides checks for the total number of DRB per cell and maximum
number of DRB per UE.
The Flexi Multiradio BTS applies for intra LTE handovers an all-or-nothing approach.
The Flexi Multiradio BTS supports the following scenarios for establishing and releasing EPS
bearers:
• establish individual EPS bearers
• release individual EPS bearers
• add multiple EPS bearers to existing EPS bearers
• release multiple EPS bearers from existing EPS bearers
Prepared by Date Page
16.12.2013 58/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The different EPS bearers per UE can have the same or a different QCI.
The feature can be enabled / disabled via O&M per eNode B.

HW Requirements: no specific HW requirements

Interdependencies between Features: The feature LTE7 Support of Multiple EPS bearer must
be enabled.

The feature LTE10 EPS Bearer for Conversational Voice must be enabled for the support UM
DRBs.

The feature LTE587 Multiple GBR EPS Bearer per UE must be enabled for the support of
multiple GBR DRBs.

This features LTE534, LTE496 and LTE497 need to be enabled.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x x 3GPP R8
EP1 UE
capabilities

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -
Prepared by Date Page
16.12.2013 59/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

5.4 LTE: Supplementary RRM functions


5.4.1 Control plane overload handling
Unique ID: 1047

Short Description:

The eNode B provides a control plane overload detection mechanism and related counter
actions.

Benefits for the Customer:


The eNode B ensures with this feature a high control plane throughput is achieved at a high
offered load.

Functional Description:
The Flexi Multiradio BTS supports an overload handling for the control plane covering the UU,
X2 and S1 interface.

The control plane overload functionality on eNode B level comprises of


• an overload management function and
• a set of triggered overload actions on application level.

Control plane overload management

A control plane overload is detected by evaluating a certain overload level metrics (queue length
and/or queuing time and/or CPU load). The control plane load is characterized by three states
depending on the metrics:
• overload level 0 (normal operation)
• overload level 1 (for graceful overload handling)
• overload level 2 (preserving stability, self-defense)
The overload detection mechanism allows to differentiate peak load scenario from sustained
traffic increase. The overload management function realizes overall the load control loop(s)
including timeout/hysteresis values for the different load levels and the corresponding overload
actions (activation/deactivation).

Control plane overload counter actions

The eNode B performs the following counter actions in case of overload level 1:
• Reject of low priority RRC connection requests(Establishment Cause set to
'delayTolerantAccess', 'mo-data' or 'mo-signalling'
• Rejection of incoming non emergency HO without GBR bearer in combination and HO
cause other than Time Critical Handover or Handover Desirable For Radio Reasons
The eNodeB performs the following counter actions in case of overload level 2:
• Reject of low priority RRC connection requests as defined in overload level 1
Prepared by Date Page
16.12.2013 60/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

• Reject all non emergency HO

The following performance counters are provided to monitor the control plane overload
functionality for the affected cells, e.g.
• time period of overload level 1
• time period of overload level 2
• number of rejected RRC connection requests due to overload handling

The functionality can be enabled / disabled per eNode B with its subordinated cells by O&M
setting.

HW Requirements: no specific HW requirements

Interdependencies between Features: LTE534 ARP based admission control for E-RABs
needs to be enabled

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 mandatory

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

5.4.2 Group hopping for UL reference signal


Unique ID: 801

Short Description:

Randomizing the reference signal of PUCCH and PUSCH.

Benefits for the Customer:


No need for reference signal planning / configuration.

Functional Description:
The sequence group number of the base sequence which is used to derive the reference signal
sequence for the PUCCH and the PUSCH is automatically generated.
The sequence group number itself is defined by a combination of 17 group hopping patterns
and 30 sequence-shift patterns.
Prepared by Date Page
16.12.2013 61/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The same group hopping pattern is used for the PUCCH and the PUSCH.
A different sequence shift pattern is used for the PUCCH and the PUSCH.
Both patterns are derived from the physical cell ID based on an algorithm defined by 3GPP.
The Flexi Multiradio BTS signals via the DCI format 2 whether group hopping is switched on or
off.
Group hopping can be enabled / disabled on cell basis via O&M.

HW Requirements: no specific HW requirements

Interdependencies between Features: none

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - 3GPP R8
EP1 mandatory

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -
Prepared by Date Page
16.12.2013 62/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

6 Operability
6.1 Network Monitoring and Maintenance
6.1.1 BTS Diagnostics Toolkit used by operator
Unique ID: 1909

Short Description:

The BTS Diagnostics Toolkit is supporting operator and technical support and NSN
development with efficient data collection from eNB. The data set, as e.g. trace data, BTS
snapshot data, .. is send from operator to NSN with tool support. It will allow resolving an error
at first occurrence as all necessary information is available for detailed analysis. The toolkit is

• Supervising the eNBs via cell tracing T

• Triggering the BTS Snapshot creation in time based on trigger events in cell trace
content

• Comes along with LTE SW

• Is easy to install and use

Benefits for the Customer:


This feature will improve the trouble shooting situation with the "PRESS ONE BUTTON" support
for data collection. This leads to reduction of OPEX and time for error solving with a high
correction hit rate. Additionally the pressure is minimized
• to reproduce faults,
• and extensively train engineers on site.

Functional Description:

Diagnostics Toolkit Setup

The Diagnostics Toolkit based on L3DC can be connected to a relevant bundle (up to 200) of
eNB via TCP based connection.

Those eNBs can be chosen by operator according to strategic relevance, occurrence of high
load, or suspicion of malfunction.

The configuration data for the connection settings can be imported via xls to the toolkit easily,
and can be changed at any time.
Prepared by Date Page
16.12.2013 63/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

The L3DC is installed on a PC or server with Windows OS, and needs to be "placed" inside
customer secured IP area.

Monitoring of eNBs

After connection with selected eNBs the cell traces are captured online and all time (no user
plane data).
The cell trace content will be made visible to operator by decoding the messages relevant for
him.

Detection of critical situation in eNB and snapshot is triggered

A cell trace message contains certain trigger events in case of malfunction. These are used as
the trigger to invoke a snapshot on that specific eNB.

Those events can be chosen by operator, and mapped to snapshot severity via definition file.

The delay between trigger event detection and snapshot trigger is maximal 10ms.

The snapshot itself takes about 10 minutes currently, and has a size of ca. 10MB. The data is
stored at local directory in Flexi Multiradio BTS and is then going to be uploaded to BTS
Diagnostics Toolkit.
The snapshot file is after that available to be delivered to NSN for further analysis.

HW Requirements: L3DC required

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 - - - n/a

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 64/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

6.1.2 S1 lock/unlock
Unique ID: 1910

Short Description:

S1 Lock/Unlock offers an operator a possibility to lock and unlock the eNB S1 link to a target
MME via eNodeB O&M.

Benefits for the Customer:


Benefits for the Customer Cells of the eNodeB can be kept in service during e.g. MME re-
homing if LTE2 S1 Flex is in use allowing several MMEs per eNodeB.

Functional Description:
Functional Description Operator is able to lock and unlock a eNB S1_MME link. The target
MME can be any operator's MME in case of RAN sharing is in use.

When S1_MME is locked, eNodeB will release all the UEs in RRC connected mode supported
by the locked S1. RRC release is made with cause code "other". For UL driven cases, UE will
initiate new RRC connection setup and will be directed to another MME if present. For DL data
driven cases the UE will be paged from an available MME connected to the eNodeB. Calls of
the eNodeB connected to potential other MMEs are unaffected by the lock procedure. Locked
MME is not considered in any MME selection procedures in the eNodeB. SCTP association of
the eNodeB to the MME is terminated.

NetAct Monitor Property Window shows the S1_MME administrative state as "unlocked" or
"locked" and separately operational state as "available" or "unavailable" to make distinction
between locked and faulty link. No alarm is raised when operator sets S1_MME as "locked".

When S1 is unlocked, eNodeB establishes the SCTP association to the MME and handles the
scenario in the same way as MME link recovery.
The feature is controlled with a new O&M parameter per MME, with default value "unlocked".

HW Requirements: None

Interdependencies between Features: LTE2 S1 Flex is required to get the most benefits of S1
lock/unlock feature, but is not mandatory.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - n/a
EP1
Prepared by Date Page
16.12.2013 65/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

6.2 Configuration Management


6.2.1 Parameter Categorization
Unique ID: 1486

Short Description:

In LTE, WCDMA and GSM we are facing a high and still growing number of parameters per
Network Element.

• Parameterization and optimization becomes more and more complex due to the high
number of interdependent parameters.

• The customer feedback is:

o too many parameters

o difficult to understand their role

o complex parameterization and optimization

o poor Customer Documentation for parameters

• Challenges of Parameter Management

o high AND growing number of parameters per network element

o complex, error prone, time consuming network parameterization/optimization

o some parameters most probably will never be touched

o some have very minor impact on network operations

o others very risky to be tuned (default not recommended to be changed)

o incorrectly set parameters may lead to serious performance issues and trigger
RESOLVEs/PRONTOs

In order to improve/ease the challenges of Parameter Management it is proposed to introduce a


categorization of parameters by,
Prepared by Date Page
16.12.2013 66/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

• limiting parameters to be set mandatorily

• definition of parameters to be touched only when advanced optimization really needed

• improve O&M tools handling related to parameter settings e.g. network element
configuration, network configuration and optimization, wizards for feature activation,
advanced parameters visible only when necessary

Benefits for the Customer:


By simplification of the plan file and limitation of the number of parameters to be managed
customer expenses (OPEX) is reduced.
• Simplified network parameterization
• Faster product rollouts and less effort for competence development

Functional Description:
The following two new parameter categories are introduced:

• Basic (operator configurable)


o Configuration parameters like NE ids, IP address etc.
o Planning parameters like neighbor definitions, frequency plan, scrambling code
plan, PCI plan, RA preamble plan etc
o Output from dimensioning (parameters defining amount of resources)
o Parameters defining operators' strategy, e.g. traffic steering, thresholds for power
control, handovers, cell resections, high level parameters defining feature
behavior, etc.
o Parameters are visible in Network Element Manager, MML and NetAct,
contained in CuDo and explained in NEI's

• Advanced (Configurable by NSN Service and/or Operator Advanced Staff)


o Network optimization and fine tuning parameters
o Decent network performance should be achieved without tuning of these
parameters
o Universal defaults ensuring decent network performance need to be defined for
all parameters in this category (if this is not possible for given parameter this
must be put in Basic parameters Category)
o Advanced parameters that require detailed system knowledge and broad
experience should be put in this category unless rules for Basic category are
violated
o All parameters (even with no defaults) that are related to advanced features like
DFCA, IUO, tracing etc are to be defined in Advanced Parameters category

There is another, existing parameter category, not visible to customers.


• Restricted (Accessible only with special guidance from R AND D (and NetEng)

Prepared by Date Page
16.12.2013 67/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

o this parameter category is already reflected by existing vendor parameters which


will be not modified/changed by this feature request
o

There are different existing tools/applications involved in parameter handling and which are
affected by a parameter categorization.
This feature requests to start introduction of parameter categories at NetAct CM-editor since this
NetAct-application is used at almost all operator use cases, requiring the management of
parameters.

For implementation of parameter categories, changes at CM-editor as well as Parameter


Dictionary (PDDB) are required.

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

6.2.2 System Upgrade to RL60


Unique ID: 1560

Short Description:

This feature enables smooth upgrade from major release (RLxx) N-1 to release N in the overall
network.

Benefits for the Customer:


Smooth remote upgrade path from major release N-1 to release N.
In this case from RL50 to RL60.

Functional Description:
Following functionality is supported with the upgrade from release N-1 to release N:
Prepared by Date Page
16.12.2013 68/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

1) The upgrade from release 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 analyzer.

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

• FSMr3 to FSMr3
This is valid for configurations which can be fulfilled with FSMr3 configurations in 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:


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


Prepared by Date Page
16.12.2013 69/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

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-1 to release N.

6) NetAct is prepared to handle both NE releases (release N-1, release N) with release N
timeframe. A mixed configuration support is ensured.

7) BTS SM is prepared to handle both NE releases, at least as co-existing versions of BTS SM


with release N.

8) Layer3 Data Collector is prepared to handle both NE releases.

9) Traffica is prepared to handle both NE releases.

10) If a conversion of the data is required, the related converter Software is available either in
online or offline mode.

11) An LTE system wide top-down upgrade sequence is defined.

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

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

14) A delta description lists all differences to the old version as part of the customer
documentation. This is valid for all data.

15) This feature does not include the upgrade of any HW.

16) RF sharing cases


Prepared by Date Page
16.12.2013 70/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

In RF sharing setups the master/slave roles are considered. Only the master can upgrade the
RF modules.
RL60 release-specific

Additional requests introduced with RL60 upgrade:


1) automatic CM upload of eNBs to NetAct for CM consistency after SW upgrade
2) OMS remote MAJOR SW management support
3) NetAct8 introduction with RL60
Even with the new NetAct8 introduction in RL60 the backward compatibility with N-1 is ensured.

HW Requirements:

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 OMS6.0 - - n/a
EP1 (RL60)

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

6.2.3 Support for Multi-antenna RET device


Unique ID: 1657

Short Description:

This feature introduces support for Multi-antenna RET devices to Flexi Multiradio BTS,
according to Iuant-interface specification, as described in 3GPP TS25.466.

An antenna may support transmission/reception on different frequency bands within one


physical housing, whereby the antenna beam down tilt for each frequency band can be
controlled separately via a build-in Multi-antenna RET-device.

Benefits for the Customer:


Support for Multi-antenna RET devices by Flexi Multiradio BTS.

Functional Description:
An operator may deploy antenna types, supporting more than one frequency band (e. g. Dual
band antenna).
Prepared by Date Page
16.12.2013 71/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

For each supported frequency band the physical down tilt of the beam can be be configured per
given frequency band using a build-in Multi-antenna RET-device (Remote Electrical Tilt).
At the moment Flexi Multiradio BTS supports only single antenna RET-device.

This feature introduces Flexi Multiradio BTS support for communication to a Multi-antenna RET-
device, as used by antenna types supporting more than one frequency band (device type '0x11',
type 17), according to Iuant-interface specification (3GPP TS25.466).
Further on Flexi Multiradio BTS supports from an object modeling perspective the configuration
of a tilt for each supported frequency band (configuration of beam tilt per frequency band per
sector), which can be controlled and configured independently by NSN network management
system (NetAct/3prd party NMS or BTS Site Manager).

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 72/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

6.2.4 Extend maximum number of X2 links


Unique ID: 1708

Short Description:

Extend the maximum amount of potentially supported X2 links up to 256 for Flexi Multiradio 10
family and up to 128 X2 links for FSMD/E.

Benefits for the Customer:


With the increase of X2 links in the eNB, more flexible handling of neighbor relations is possible.
Learning of new important X2 links is not blocked even when seldom used X2 links are kept.

Functional Description:
The increase of the X2 links is done in following way:

• The number of supported X2 links is increased up to 256 for Flexi Multiradio 10 family and
up to 128 X2 links for FSMD/E. Those X2 links can be used arbitrary as enbControlled or
oamControlled.
• The X2 black-list table is also increased correspondingly.
• With the setup of 256 X2 links, also the learned neighbor cells are considered. Taking here
12 cells per eNB an overall amount of 256x12 + 11 = 3083 neighbor cells are able to be
considered (based on simple eNB level calculation)
• The PM Counter concept for the neighbor cell related counters is adapted to avoid
significant increase due to increase of the X2 links from 64 X2 links to 256 X2 links.
The neighbor cell related counters are based on the real neighbor cell relations (mapped to
LNREL object) instead to be based on all potential neighbor relations (mapped to LNADJL
objects).

The same concept is also applied for the neighbor cell related HO counters for GERAN and
WCDMA/TD-SCDMA.

• An operator parameter is introduced. This parameter is able to configure the maximum


amount of X2 links that are wanted by operator per eNB.

With the increase of the X2 links, the following restrictions are accepted:

1) The setup time for the X2 links is considered independent of eNB restart time. The
finalization of the X2 links setup might take much longer as the eNB restart time.

The oamControlled X2 links are setup first (as already today) within a time limit of 20 minutes.
The enbControlled X2 links can be setup after the oamControlled, but do not need to be
established within the time limit.
Prepared by Date Page
16.12.2013 73/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

2) The OAM driven ANR features in Optimizer (as LTE539, LTE492) are not be affected by this
increase and keep the values of the current design (64 LNADJ/ X2 links and PCI/IP mapping
table with up to 200 entries).
3) The LNREL (per LNCEL) amount will not increase and stay with 389.

HW Requirements: no specific HW requirements

Interdependencies between Features: With the change of the PM counter concept for the
neighbor related counters:

The following legacy features are affected by this change

· LTE56 Inter RAT handover to WCDMA

· LTE872 SRVCC to WCDMA

· LTE873 SRVCC to GSM

· LTE442 Network Assisted Cell Change to GSM

Changed requirements on PM counters related to above features is specified within CFAM


LTE1708.

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 OMS6.0 - - n/a
EP1 (RL60)

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -

6.2.5 ANR Intra-LTE, Inter-frequency - UE based


Unique ID: 556

Short Description:

Automated Neighbor Relation (ANR) for Intra-LTE, Inter-frequency neighbor cells is based on
UE measurements, searching on demand for currently unknown Intra-LTE, Inter-frequency
neighbor cells. It can be started to properly update and configure the Neighbor Cell List for
adjacent LTE cells.
Prepared by Date Page
16.12.2013 74/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

This feature handles the use case when an operator adds a new Flexi Multiradio BTS to the
network, operating on a different EUTRAN-carrier than the installed neighbor Flexi Multiradio
BTS.

Benefits for the Customer:


The automated detection of unknown adjacent Intra-LTE, Inter-frequency LTE-cells supports the
self configuration of the Neighbor Cell List for Intra-LTE, Inter-frequency neighbor cells reducing
operational expenses in neighbor cell planning and keeping neighbor relations up-to-date.

Functional Description:
In LTE networks the UE mobility in RRC Connected State trusts in information given by an
explicit neighbor cell list. To support and allow the automated configuration and update of Intra-
LTE, Inter-frequency neighbor cells without the need of a complete pre-planning of the neighbor
cell configurations a mechanism is implemented to discover unknown cells.

The trigger to start a search for Intra-LTE, Inter-frequency neighbors could be given from the
network management system or as result of internal RRM/Mobility Management algorithms.

The detection of unknown neighbor cells can happen during event triggered inter-frequency
measurements or during periodic measurements activated by the Flexi Multiradio BTS for ANR-
capable UEs.

Upon detection of an unknown cell, Flexi Multiradio BTS will try to resolve the corresponding
ECGI. This can be done ordering EGCI measurement at the UE, if supported by the UE, or via
any other information which may be locally available (e.g. from X2 interface).

In order to reduce the probability of call drops in case of a first HO to a newly detected neighbor
cell Flexi Multiradio BTS supports ANR-mechanisms in order to detect and configure any
unknown Intra-LTE, Inter-frequency neighbor cell as early as possible and not at the time when
the first HO to a newly detected cell is triggered. This kind of operational mode of ANR is further
referred to as active ANR.

Active ANR
If Active ANR handling is started, Flexi Multiradio BTS will pro-actively scan for unknown Inter-
frequency neighbor cells.

Passive ANR
If there are no new unknown neighbor cells detected anymore ANR will be operated more as
background task, e. g. Flexi Multiradio BTS does not configure ANR-specific measurements but
uses the normal measurement reports (as received for HO) for detection of unkn0own cells.
The operator is able to control the behavior of these ANR-mechanisms by providing
configuration parameters.

• switching ON/OFF ANR per Flexi Multiradio BTS


• operator-configurable parameters for switching between active and passive ANR
Prepared by Date Page
16.12.2013 75/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Monitoring of ANR is supported by means of performance measurements. The following events


can be monitored:
• number of successful/failed/attempted ECGI-resolutions
• number of successful/failed/attempted MMI-queries (IP@ resolution)
• number of successful/failed/attempted X2-setups
• number of HO-failures due to unresolved ECGI

After new neighbor cell relations have been successfully included into the local configuration
data the Flexi Multiradio BTS sends a configuration change notification to NetAct to inform the
operator about the new neighbor cell configurations.

HW Requirements: no specific HW requirements

Interdependencies between Features: LTE55 Inter frequency Handover required

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 x - 3GPP R8
EP1 UE
capabilities
Prepared by Date Page
16.12.2013 76/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
ASW SW Asset Monitoring -

6.2.6 Intelligent configuration synchronization


Unique ID: 954

Short Description:

This proposal introduces an e2e mechanism for data synchronization to avoid unnecessary
uploads. Configuration Change ID information is added in network element and provided to
NetAct with the change notifications. NetAct uses the information to check if configuration
upload is needed. In case an upload is needed, NetAct triggers an automatic upload of the CM
data of that eNB.

Benefits for the Customer:


The operator can reduce operating expenses due to more reliable date available in NetAct. No
upload required before planned configuration changes.
The feature increases the grade of service for the end user by maintaining up-to-date network
information automatically. No scheduled uploads are needed anymore.

Functional Description:
Today, to ensure that the actual configuration stored in NetAct databases is up to date, an
upload of the CM data of eNB has to be done to NetAct. This is because configuration change
events may be lost due to several reasons which may happen in the network, as e.g. outage of
management plan connection for longer time and limited storage capacity of change
notifications in network element.
With this feature an e2e mechanism for data synchronization is introduced. For Configuration
Change Notification (CCN) a Configuration Change ID information is added in eNB and
provided via OMS to NetAct.

The Configuration Change ID is increased in eNB when real changes are done to the
configuration.

In case of re-sending of CCNs, the Configuration Change ID is not changed. The configuration
change may be caused by an autonomous action in the network element , or CM change
executed from BTS SM or NetAct

NetAct uses the Configuration Change ID information to check if configuration upload is needed.
In case an upload is needed, NetAct triggers an automatic upload of the CM data of that eNB.
Prepared by Date Page
16.12.2013 77/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

When an upload is triggered by operator, NetAct requests first only the Configuration Change ID
value. An upload is then only requested to network element, if the Configuration Change ID
value in NetAct and network element does not match.

The Configuration Change ID is also checked in each management connection recovery.


Whether the mismatch in the value leads to automatic upload is up to the NetAct application and
operator preference.
The Configuration Change ID information is saved in network element's permanent memory.
Thus it is valid also after network element restart.

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 OMS6.0 - - n/a
EP1 (RL60)

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 78/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

6.3 O&M Security


6.3.1 Revocation management
Unique ID: 1245

Short Description:

This feature provides capabilities to manage cross-certified certificates and an enhanced


certificate revocation list (CRL) management with new activation and configuration capabilities
for multiple revocation list location

Benefits for the Customer:


The customer is able to include a partner operators PKI by a cross signed CA certificate in case
of RAN sharing (MOCN or MORAN). It adds flexible control of revocation list configuration and
execution for the own PKI as well as for a partner operators PKI system.

Functional Description:
Cross-signed certificate enrolment:

The BTS support the integration of a second operator PKI. In case the trust relation shall be
established by cross-certification the operator is able to store a cross signed certificate into the
BTS trust pool by the following options:
• Manually with the BTS Site Manager per individual BTS
• or with a NetAct script utilizing the BTS Site manager command line for a list of BTS

Cross-signed certificate update:


The operator may update a stored cross signed CA certificate at any point in time. Nevertheless
the BTS sends an alarm to NetAct when a cross-certificate is close to expire. The BTS applies
the same pre-warning time value as used for the own CA signing certificate expiry supervision.

If notified the operator may now add a cross-signed CA certificate manually via the BTS Site
Manager, either individual per BTS or with NetAct scripting for a list of BTS. The available cross
signed certificate is not automatically removed to allow a smooth migration to a new cross-
certification. Thus for a certain time 2 cross signed certificate can be handled by the BTS.

Cross-signed certificate removal:


An expired or unneeded cross-signed certificate can be deleted from the trust pool with the
NetAct NMCTool or with the BTS Site Manager. The BTS does not remove expired cross-
signed certificates autonomously.

Revocation List Management:


The revocation list management enhances the existing BTS CRL management by the capability
to configure additional CRL distribution points.
Prepared by Date Page
16.12.2013 79/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Overall CRL Activation:


The operator is able to activate or deactivate CRL handling for the whole BTS by a configurable
attribute with the BTS Site Manger and NetAct Configurator. If deactivated peers certificates are
not checked upon revocation.

CRL distribution points given within X.509 certificates:


The BTS ignores all CRL Distribution Points (CRLDP) contained within the entity certificate and
within all sub-ordinate CA certificates sent by the peers as part of the secured connection
establishment.

The BTS automatically downloads and regularly updates all CRL which may given as CRLDP
within the own entity certificate and all sub-ordinate CA certificates of the own signing chain.

Configurable CRL distribution points:


The BTS offers 8 additional OAM configurable CRL entries which can be configured for LDAP
download either as static IP address with path to directory or as FQDN with path to directory.
The parameters can be set with the BTS Site Manger and NetAct Configurator.

The operator may use them


• to configure CRLDP in addition or instead to the X.509 certificates method of the own
certification path and/or further CRL signing paths of the own operators PKI. A typical use
case would be if the security gateway is signed by a different sub-ordinate CA than the BTS.
• and to allow the revocation of corrupted SeGW certificates revoked by the partner operators
PKI by configuring additional CRL distribution points holding relating CRL information
according to operator agreements.

CRL information update:


CRL of the own certification path are initially added as part of the operator certificate enrollment
and updated with a later operator certificate update.

CRL of configurable CRLDP are added when a new CRLDP is configured.

A known CRL is updated (common for all types of CRLDP):


• Periodically when the BTS fetch timer expires(common for all types of CRLDP)
• With NextUpdate point in time given within a CRL (with random delay)
• At eNB start-up
• Triggered on demand by operator with NetAct NMCTool (with random delay) or with the BTS
Site Manager

A CRL is kept in the BTS as long as:


• a CRL is configured by CRLDP entry
Prepared by Date Page
16.12.2013 80/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

• a CRL is part of own certification path

CRL check behavior configuration:


The operator is able to configure the usage and behavior for the CRL handling with the BTS Site
Manger and NetAct Configurator in a flexible manner.

Possible settings:
1. only CRLDP found within the certificates of the own certification path are taken into account ,
possibly found operator configured CRLDP are ignored.

2. only operator configured CRLDP are taken into account.

3. both CRLD within certificates of the own certification path and operator configured ones are
taken into account.

Each operator configurable entry can contain 2 CRLDP:


• a primary CRLDP
• and an optional secondary CRLDP

In case of 2 entries found the BTS treats them a primary and secondary CRL source. Hence the
BTS tries first to download the CRL from the primary CRLDP (1st entry) and if this fails it tries
download the CRL from the CRLDP (2st entry).

An alarm is only sent if the access to both locations fails. If only one CRLDP found then an
alarm is always sent if the access to the file location fails.

Configurable Trust chain for configured CRLDP:


CRLs are signed by the issuing CA. In case of the CRLs issued by a s sub-ordinate CA within
the BTS own signing chain the CRL origin can be automatically validated up till the own Trust
Anchor to verify the authenticity of this CRLs.

CRLs obtained from configured CRLDPs may be issued by sub-ordinate CA(s) either from
within the BTS own PKI hierarchy or from a partner operator PKI hierarchy. Thus the operator is
able to configure up to 8 additional sub-ordinate CA certificates to allow proper check of the
CRL origins. These CRL verification certificates can be added with the BTS Site Manager, either
individual per BTS or with NetAct scripting for a list of BTS.

The BTS informs NetAct when such a sub-CA certificate is close to expire. The BTS applies the
same pre-warning time value as used for the own CA signing certificate expiry supervision.

An expired or unneeded CRL verification sub-CA certificate can be deleted from BTS with the
NetAct NMCTool or with the BTS Site Manager. The BTS does not remove expired certificates
autonomously.
Prepared by Date Page
16.12.2013 81/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 OMS6.0 - - n/a
EP1 (RL60)

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -
Prepared by Date Page
16.12.2013 82/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

7 Performance Monitoring

7.1 Additional QoS performance measurements


Unique ID: 1361

Short Description:

PM counters extension

Benefits for the Customer:


PM counters enhancements, according to customer requirements.

Functional Description:
Following PM-counters are implemented:

• Number of established E-RABs per QC


• NumberOfEstabERABperQCI (#1/#2/#3/#4/#5/#6/#7/#8/#9)
Use case:
• Provide feedback about the number of established (simultaneous) E-RAB per
supported QCI, implicitly the used services in the network (voice, streaming etc.)
• Delay Budget Monitoring per QCI
Use case:
• This measurement provides the PDCP SDU delay per QCI on the downlink. It is an
indicator for the delay experienced by the end-user. It also can be used to monitor
the packet delay budget characteristics of the E-RAB's QCI.
• The measurement is done separately per QCI#1, #2, #3, #4, #5, #6, #7, #8, #9

• Number of Uplink and Downlink PDCP Packet Loss (accord. to 3GPP 36.314) per QCI
(#5/#6/#7/#8 /#9)
Use case:
• The objective of this measurement is to measure user plane packets that are lost on
the air interface. As such, it can also be used to monitor the packet error loss rate
characteristics of the E-RAB's QCI.

NOTE:
Packet Loss PM-counters for QCI #1/#2#/3 /#4 implemented with CRL 734.

• Counters for RRC measuring RRC setup success rate, differentiating on additional
establishment causes as follows
• Mobile Originated Data (MO-Data)
• Mobile Orignated Signalling (MO-Signalling)
• Mobile Terminated Access (MT-Access)
Prepared by Date Page
16.12.2013 83/83

Nokia Solutions and Networks Approved by Doc number Version


LTE RAN 2.0

Use case:
• The objective is to be able to provide RRC Connection Establishment Success Rate
for RRCConnectionRequest message (from UE to eNB) in order to break down and
classify RRC Connection Setup failures currently for troubleshooting/drill down
purposes

HW Requirements: no specific HW requirements

Interdependencies between Features: no feature interdependencies

Dependency to other RATs: No dependency

RL Software Dependencies:
LTE BTS BTS NetAct OMS MME SAE UE
Flexi Flexi 10 GW
Release RL60 LBTS6.0 LBTS6.0 NetAct8 - - n/a
EP1

SW Sales Information:
BSW/ASW Licence Control in Network Licence Control Attributes
Element
BSW - -