Professional Documents
Culture Documents
Nokia - LTE - RL30 - Features Description
Nokia - LTE - RL30 - Features Description
2012-05-15 1 (75)
The information in this document is subject to change without notice and describes only the product defined in the introduction of
this documentation. This document is intended for the use of Nokia Siemens 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 Siemens Networks. The document has been prepared to be used by professional
and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the documentation.
The information or statements given in this document 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 in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens 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 Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be
covered by the document.
Nokia Siemens Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SIEMENS
NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED
TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY 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 document and the product it describes are considered protected by copyrights and other intellectual property rights according to
the applicable laws.
Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a
registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for
identification purposes only.
Copyright © Nokia Siemens Networks 2012. All rights reserved.
Prepared by: LTE PLM Date Page
2012-05-15 3 (75)
Introduction .......................................................................................................................... 5
History .............................................................................................................................. 6
2. Transmission..................................................................................................... 22
2.1. Transport admission control ............................................................................... 22
2.2. IP Transport Network Measurement .................................................................. 23
2.3. Fast IP Rerouting................................................................................................ 24
2.4. Ethernet Jumbo Frames ...................................................................................... 25
4. Operability ........................................................................................................ 53
4.1. Configuration Management ............................................................................... 53
4.1.1. Synchronization of InterRAT neigbhors ............................................................ 53
4.1.2. Mobility Robustness........................................................................................... 54
4.1.3. PRACH management ......................................................................................... 58
4.1.4. Optimization of Intra-LTE neighbor relations ................................................... 59
4.1.5. ANR Fully UE based ......................................................................................... 60
4.1.6. ANR InterRAT UTRAN .................................................................................... 64
4.1.7. ANR InterRAT GERAN .................................................................................... 66
4.1.8. System Upgrade with Backward Compatibility ................................................. 68
4.2. Network Monitoring and Maintenance .............................................................. 70
4.2.1. Automatic interface alarm correlation................................................................ 70
4.2.2. LTE Timing Advance Evaluation ...................................................................... 71
4.2.3. Performance Management Administration ........................................................ 72
4.2.4. Configurable cell trace content .......................................................................... 73
4.3. Supplementary O&M features ........................................................................... 75
4.3.1. DNS support for certificate examination ........................................................... 75
Prepared by: LTE PLM Date Page
2012-05-15 5 (75)
Introduction
This document provides the list of new features for the LTE Radio Access System Release RL30.
The scope of the document includes evolved NodeB (eNB) and Transmission. The Flexi
Transmission Module provides the transmission interfaces for the eNB. The LTE is managed with the
Operations Support System (OSS) and it interfaces with Packet Switched (PS) Core Networks (CN)
over the S1 interface.
LTE Release RL30 specification baseline is 3GPP Rel-9 March 2010.
This document does not cover the Core Network, WCDMA, GSM system and Mobile Station support
but only Nokia Siemens Network's LTE RAN level issues.
The content of this document is subject to change mainly due to the status of standardization and the
actual release definition process.
HW requirements: Here it will be indicated if the feature requires a specific HW in RAN LTE
portfolio. It is left blank if the feature describes a HW item itself or has no specific requirements.
Interdependency between features: Here dependencies between NSN RAN LTE features will be
indicated.
History
FUD V2.0 LTE424 updated;
LTE 1101 and LTE1106 added
Fext V1.0 LTE1195 added
Fext V1.1 FXCC and FHEC added
Prepared by: LTE PLM Date Page
2012-05-15 7 (75)
For Distributed BTS (over 200 m optical link) and chained RF configurations are separate features.
HW Requirements:
Interdependencies between Features: Not supported at the same time with LTE447 RF sharing
LTE-GSM (with one FSME).
RL Software Dependencies:
1.3. Flexi low power RRH 850 2TX for optical repeater interface
Unique ID: 1106
Short Description: Flexi LTE low power RRH with 2 TX for optical repeater interface of Korean
market in Band 5 (tbd 6,18,19).
Benefits for the Customer: Indoor low power RRH optical repeater interface enables building LTE
indoor and outdoor coverage using repeater solutions that is already known in customers legacy cdma
systems.
Functional Description: Flexi RRH 2TX 850 repeater interface main features:
Antenna Port
Prepared by: LTE PLM Date Page
2012-05-15 9 (75)
Mechanical dimensions:
can fit to 19'' rack (height < 1U, depth > 40 cm)
Power supply:
27V/-48V
RL Software Dependencies:
HW Requirements:
Interdependencies between Features:
Software Sales Information:
On radio interface side one RIU is able to support up to three RF repeaters (cells or sectors) with three
analog RF interfrequency interfaces.
On optical interface side one RIM is able to support up to three LTE cells (sectors) with two optical
interfaces towards Flexi RF Modules. Optical interface has delay functionality with settable 0 - 100
microsecond delay to adjust the RF Module and RF repeater delay the same in downlink and uplink.
Benefits for the Customer: RIU is customized market and customer specific product enabling
operator to use their existing RF repeaters and analog-digital RF distribution system with new LTE
BTS and LTE RF units.
Functional Description:
On radio interface side one RIU is able to support up to three RF repeaters (cells or sectors) with
three analog interfrequency RF signal interfaces. RIU performs optical to IF radio conversion. 2TX
MIMO is supported with each interface.
On optical interface side one RIU is able to support up to three LTE cells (sectors) with two optical
interfaces towards Flexi RF Modules. Optical interface has delay functionality with settable 0 - 100
microsecond delay to adjust the RF Module and RF repeater delay the same in downlink and uplink.
2TX MIMO is supported for each cell.
Optical Mux/demux
- OBSAI signal splitting (same cell to Radio Unit and Repater) in downlink in Coupling Mode
- OBSAI signal summing (same cell from Radio Unit and Repeater) in uplink in Coupling Mode
- OBSAI signal handling in downlink and uplink in Dedicated Mode (Radio Unit and Repeater have
theit own cells)
Configurations:
Dedicated cell mode
• one RIU is connected and supports up to 3 cells for Flexi RF Modules and 3 separate own cells for
three Repeaters , max 6 cells @ 10 MHz for one System Module (FSME)
• one RIU can support up to 3 cells for three Repeaters, no Flexi RF units connected to RIU
-separately 3 cells with Flexi RF Modules or RRHs can be directly connected to Flexi System
Module FSME
Prepared by: LTE PLM Date Page
2012-05-15 11 (75)
Coupling mode
• one RIU is connected and supports up to 3 cells for Flexi RF Modules and three Repeaters
extending the coverage of the three macro cells
with two RIUs up to 6 macro cells @ 10 MHz (4 RF Modules) with up to 6 repeaters for one Flexi
System Module FSME
Mixed Mode:
• Dedicated and Coupling mode
• max 6 cells @ 10 MHz with FSME
• 3 cells with 2 RF Modules with RIU and 3 repeaters in coupling mode
• 3 dedicated repeater cells with second RIU
Figure:
RL Software Dependencies:
HW Requirements:
Interdependencies between Features:
Software Sales Information:
1.5. FHEC Flexi RRH 2TX 1800 low power Flexi RRH 2TX 2100
Unique ID: 1337
Short Description: FHEC Flexi RRH 2TX 1800 MHz low power for optical repeater interface of
Korean market in 3GPP Band 3.
Benefits for the Customer: Indoor low power RRH optical repeater interface enables building LTE
indoor and outdoor coverage using repeater solutions that is already known in customers legacy
CDMA systems.
Functional Description: FHEC Flexi RRH 2TX 1800 low power repeater interface main features:
Frequency band: 1840MHz~1850MHz on Tx (DL) 1745MHz~1755MHz Rx (UL)
Level(dBm): DL 0dBm @ max traffic, UL TBD
Output port: Each 2 ports per DL and UL, SMA type, MIMO
Signal Monitoring port: One per DL and UL, SMA type, 10 dB coupling
Configuration Dedicated: Sector (One cell)
Reference Signal: 10MHz, 4 ports
Environment: Indoor, 0~65°C IP20
Input Power: 48VDC only
Optic Interface: OBSAI RP3-1
Dimension(mm): 482.6 X TBD X 450 (W X H X D)
HW Requirements: -
Interdependencies between Features: no feature interdependencies
RL Software Dependencies:
instantaneous bandwidth support at 3GPP band 5. HW supports operation in 3GPP bands 5, 18 and
19.2-sector 2x 60 W RF Module general benefits:
Can be used in Feederless (DC up to 200 m) BTS sites. Also supports distributed sites up to 20km,
with SW feature LTE614.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
BTS System Modules and high capacity backhaul transport can be collected to one BTS hotel -type of
centralized secured location with shared BTS site support functions like battery back up (for System
Modules and transport).
Functional Description: Flexi System Module can be located (by an optical single mode interface
and single mode SFPs) up to 20 km away from the RF Module or RRH, typically closer to the
transmission termination point and other site support equipment (e.g. existing BTS shelter or inside
BTS or Site Support cabinet) and to the location with easier access for the operator.
Single Mode optical plugable tranceivers (SFP) can be installed to standard Flexi System Module and
RF Modules and RRH to support max 20 km optical single mode fiber.
Flexi RF Module or RRH is located close to antenna to support typically one sector with 2TX MIMO.
RF Module and RRH needs local 48 V power supply and optional battery back-up solution.
Maximum output power is 60 + 60 W per sector with 2TX MIMO with RF Module. Maximum output
power is 40 + 40 W per sector with RH 2TX MIMO with RRH.
Flexi System Module FSME can support three 15 or 20 MHz LTE cells. Each optical 3 Gbit/s link
can support one 15 MHz or 20 MHz LTE cell with 2TX MIMO and 2RX diversity.
HW Requirements:
Interdependencies between Features: Not supported at the same time with LTE447 RF sharing
LTE-GSM.
Following features will not work correctly together with distributed site in RL30:
If the features are applied, then the prepared values need to be re-worked manually.
RL Software Dependencies:
FSMD HW will be identical with the one used in WCDMA thus making the design common with
WCDMA and LTE. The architecture of System Module allows different product capacity variants of
1,2 or 3 BB processing units per one System Module. FSMD has two integrated BB units.FSMD is
able to support up to eight LTE cells with maximum 5 MHz bandwidth, or up to four 10 MHz cells or
up to 20 MHz cells with 2TX MIMO and 2-way uplink RX diversity up to full LTE air interface
capacity.
Implementation architecture will support also other configurations of the BB units, but it may not be
possible to support full load of air interface.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
Mechanical dimensions :
- less than 20 liters
- less than 20 kg
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
- Optimized for single sector deployment with 2TX MIMO one LTE cell with 2TX MIMO
up to 20 MHz LTE per sector.
- Optical chaining supported by HW (two optical connectors)
- IP65 with -35 to +50 °C with convection cooling two external RX outputs
(main and div with small SMA connectors) for future use (e.g. location device)
- external alarms and outputs
- AISG2.0 Antenna tilt support with external connector (RS485)
- MHA supported by both RX branches with adjustable 0...30 dB LNAs
- Other TX/RX branch with integrated BiasT to support AISG2.0 MHA
(or antenna tilt in future possible by the same HW)
- MHA SW support via integrated BiasT VSWR monitoring on both TX branches
Mechanical dimensions :
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
- the most cost and size and weight optimized 3-sector BTS site
- industry leading RF integration level
Prepared by: LTE PLM Date Page
2012-05-15 20 (75)
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
'RF unit' can be RRH or RF Module supporting one cell/sector with 2TX MIMO & 2RX diversity.
In feederless BTS site configuration max 200 m distance between System Module and two RF units
in one chain supporting two different RF bands (Dual band site).
In distributed BTS maximum 20 km distance between System Module and the last RRH/RFM in the
chain.
HW Requirements:
Interdependencies between Features: Not supported at the same time with LTE447 RF sharing
LTE-GSM.
LTE614 Distributed Site required (max 20 km distance between System Module and last RFM/RRH
in the chain) or LTE94 Feederless Site required (max 200m distance between System Module and last
RFM/RRH in the chain).
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 - - -
2. Transmission
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
The CQI offset shift between PDSCH and PDCCH is dynamically adapted based on PDSCH NACK
and DTX information. The control is based on UL HARQ feedback (NACK versus DTX) that is sent
in response to a downlink PDSCH transmission.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
Up to three different DRX profiles can be defined by the operator. Each DRX profile comprises of the
following set of parameters:
DRX Cycle
Specifies the periodic repetition of the On Duration followed by a possible period of inactivity. The
cycle provides a trade off between setup delay and UE battery power consumption. The maximum
supported DRX cycle length is 80 ms.
On Duration Timer
Specifies the number of consecutive TTIs during which the UE shall monitor the PDCCH for possible
allocations. The On Duration Timer is a part of a DRX Cycle.
Prepared by: LTE PLM Date Page
2012-05-15 28 (75)
The device type indication (non power limited) provided by the UE can be used in addition as a
selection criteria for a DRX profile. The device type indication is an optional 3GPP Rel. 9
functionality.
The DRX parameters itself are signaled via RRC messages to the UE.
DRX settings are only applied to UEs which have indicated according capabilities.
KPIs might be affected by the DRX functionality, e.g. longer ping delays.
The DRX functionality can be switched on/off per cell by O&M setting.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 - - - 3GPP R8
UE
capabilities
RL Software Dependencies:
Better channel estimation in case of RS boosting may improve the handover performance.
Functional Description: The Flexi Multiradio BTS supports the following DL power boost options
for MIMO and SIMO configurations:
Prepared by: LTE PLM Date Page
2012-05-15 30 (75)
The PCFICH provides information about the number of OFDM symbols used for the PDCCH.
The Flexi Multiradio BTS supports dedicated power control settings for the PCFICH in order to
ensure that especially cell edge UEs can properly receive the PCFICH.
A relative offset between the flat PSD on PDSCH and PCFICH can be configured by O&M on cell
level.
The Flexi Multiradio BTS supports dedicated power control settings for the PHICH in order to ensure
that the UE can properly receive the PHICH.
A maximum relative offset between the flat PSD on PDSCH and PHICH can be configured by O&M
on cell level.
The downlink reference symbols are used by the UE for the channel estimation and used for Cell
Measurements (Level, Quality) for Handover purposes.
The Flexi Multiradio BTS supports relative RS / PDSCH power control settings.
A relative offset between the PDSCH and RS can be configured by O&M on cell level.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
NACC is only applicable for NACC capable multimode devices supporting both LTE and GSM at the
according frequency band. The UE capabilites are provided to the eNB by the feature group indicator.
NACC trigger
The measurements events A2 and A1 are used to start and stop IRAT measurements and can be
configured by the operator.
The eNB will trigger IRAT measurements only for NACC capable UEs.
The UE capabilities are considered as well for the setup of the IRAT measurement configuration, e.g.
support of measurement gap and support of frequency bands..
The target cells for the IRAT measurements can be configured by the operator. Blacklisting of target
cells is supported.
The measurement configuration as source cell thresholds (RSRP), target cell thresholds (RSSI),
hysteresis, time to trigger and speed dependent scaling can be configured by the operator.
The Flexi Multiradio BTS initiates the NACC after receiving a measurement report form the UE by
sending a RRC: MobilityfromEUTRAcommand message with cell change order indication to the UE,
which forces the UE to a GSM cell.
Prepared by: LTE PLM Date Page
2012-05-15 32 (75)
Data forwarding
Performance counter
Performance counters are provided per cell in order to track the NACC performance, e.g.
The NACC functionality can be enabled / disabled per cell via O&M.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
The relative MME capacity value can be set as well to zero which would lead to the effect that new
UEs entering the MME pool will not be assigned to the corresponding MME.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
Two additional operator configurable DRX profiles (see LTE42) are introduced with this feature in
order to allow for a more flexible definition of different DRX use cases, e.g. Out-of-Sync handling or
ANR measurements.
The uplink Out-of-Sync. handling is as well introduced with this feature. It comprises of the
following two sub features:
By using very long settings for the DRX cycle, the UE may go to or is even actively sent to the uplink
Out-of-Sync status.
The eNode B initiates a random access procedure for UEs which are in uplink Out-of-Sync and have
data for downlink transmission. The eNode B provides in this case the RACH parameters via the
PDCCH order to the UE.
The UE may start during the uplink Out-of-Sync state as well a contention based random access
procedure in order to transmit data on uplink.
The following performance counters are provided in order to track the uplink Out-of-Sync behaviour
per cell, e.g.
HW Requirements:
Prepared by: LTE PLM Date Page
2012-05-15 35 (75)
Interdependencies between Features: LTE42 DRX in connected mode required. LTE42 and this
feature (LTE473) are enabled with the same parameter.
RL Software Dependencies:
A typical use case is national roaming where the SPID provided by the MME is used to identify own
subscribers and national roaming subscribers.
Another use case would be MOCN where each operator can define its own target frequency layer.
Functional Description: The feature allows the operator to assign subscriber profile IDs (SPID) to
mobility profiles.
The MME provides the subscriber profile ID to the eNode B via the S1AP:InitialContextSetup
message. The SPID is forwarded during intra LTE handovers either via X2AP:Handover Request or
via the S1AP:HandoverCommand message.
The SPID itself is mapped to a mobility profile. A default mobility profile is used when no SPID is
received or the SPID is unknown.
A mobility profile is a set of O&M configured target frequency layers for enabled inter-frequency and
inter-RAT mobility functions, e.g. handover, NACC, RRC connection release with redirect, SRVCC
or CSFB.
The eNode B will use only the neighbor cells out of the SPID related mobility profile for the different
mobility scenarios.
HW Requirements:
Interdependencies between Features: Related inter-frequency and IRAT mobility features required
and need to be enabled (eg LTE56 InterRAT HO to WCDMA).
RL Software Dependencies:
Prepared by: LTE PLM Date Page
2012-05-15 37 (75)
The introduction of operator specific QCIs requires an alignment with the EPC.
Benefits for the Customer: The operator specific QCIs allow for better user and service
differentiation for non-GBR services, e.g.
The operator specific QCIs can be used as well in case of RAN sharing to define a set of QCIs
dediacted for each operator, e.g.
Functional Description: The operator can define up to 21 additional QCIs for non GBR EPS bearers.
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)
- scheduling weight
- logical channel group ID
- DSCP
- scheduling priority
Prepared by: LTE PLM Date Page
2012-05-15 38 (75)
The Flexi Multiradio BTS supports up to 6 non-GBR QCI groups to combine QCI specific
performance counters. The mapping from the standard QCIs and the operator specific QCIs onto the
QCI group performance counters is operator configurable.
The support of operator specific QCIs can be enabled / disabled per eNode B by O&M settings.
Figure:
HW Requirements:
Interdependencies between Features: LTE9 Service differentiation for Non-GBR EPS bearer
required.
RL Software Dependencies:
many UE-associated S1-signaling connections with one message exchange between eNB and MME.
Benefits for the Customer: The procedure provides performance optimized release of UE-associated
signaling connections (both with respect to time and signaling requirements) for situations which
require simultaneous release of many UE-associated signaling connections.
S1 partial reset is used by O&M procedures (e.g. automatic lock of an individual cells) and to
clean-up node internal error situations.
Functional Description: The partial S1 reset can be initiated by the eNode B or the MME with the
S1AP:RESET message.
The indicated logical resources are released and the reset is acknowledged by a S1AP:RESET
ACKNOWLEDGE message.
The Flexi Multiradio BTS is able to handle multiple S1 partial reset procedures per S1 link in parallel.
The Flexi Multiradio BTS releases in addition related resources at the air interface via a RRC:RRC
CONNECTION RELEASE message.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 - x - n/a
The functionality is only applicable for multimode devices supporting both LTE and WCDMA at the
according frequency band and the according feature support.
Handover trigger
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. support measurement gap and
support of frequency of target cells.
The target cells for the IRAT measurements are operator configurable. Blacklisting of target cells is
supported as well. An ANR functionality might be applied optionally.
The measurement configuration as source cell thresholds (RSRP), target cell thresholds (RSCP,
EcN0), hysteresis, time to trigger and speed dependent scaling are operator configurable.
Handover preparation
The Flexi Multiradio BTS initiates a handover after receiving a measurement report form the UE by
sending a S1AP:HANDOVER REQUIRED message to the MME.
The Flexi Multimode BTS takes the first target cell indicated by the UE measurements for the
handover.
The MME responds to this with a S1AP:HANDOVER COMMAND message indicating that the
Prepared by: LTE PLM Date Page
2012-05-15 41 (75)
Handover execution
The Flexi Multiradio BTS sends after this a RRC:MobilityfromEUTRAcommand message to the UE,
which forces to the to a WCDMA cell.
The Flexi Multimode BTS performs handover retries to other target cells provided by the UE
measurements in case of unsuccessful handovers.
The Flexi Multiradio BTS supports the following counters per cell in order to track the performance:
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
The operator can configure the report amount and the report interval for the periodic reporting. The
measurement configuration is applied for all new UEe changing to RRC connected. The UE
capabilities are considered for the measurement configuration.
The periodic measurements reports can be captured and evaluated with related trace functionality, e.g.
subscriber and equipment trace or cell trace.
HW Requirements:
Interdependencies between Features: LTE163 Subscriber and Equipment trace or LTE433 LTE
Cell trace required.
RL Software Dependencies:
The coverage extension is achieved by controlling the uplink packet segmentation. This allows to
improve the coverage throughput and to optimize the PDCCH utilization by balancing new
transmissions and retransmissions. The enhancement in coverage throughput comes at the cost of cell
throughput. For a given modulation code scheme (MCS) as determined by the uplink link adaptation
and configured transport block size (TBS), the uplink scheduler determines the PRB allocation.
The uplink packet segmentation algorithm is controlled for cell edge UEs by
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
The adaptation is based on CCE blocking and used CCE (control channel elements).
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
UEs with a high TX power density will be preferably allocated to PRB regions with low noise and
interference in order to improve the cell edge performance.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
The location reporting functionality can be enabled / disabled by O&M setting per eNode B and its
subordinated cells.
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 - x - n/a
- expiry of the timer T310 (timer started after detection of physical layer problem) or
- random access problem indication from MAC or
- indication from RLC that the maximum number of retransmissions has been reached or- Handover
failure (T304 expiry) or
- Integrity check failure indication from lower layers or
- RRC connection reconfiguration failure
- in a serving cell,
- in a source cell or
- in a prepared target cell
The following counters are provided per cell in order to track the performance:
HW Requirements:
Prepared by: LTE PLM Date Page
2012-05-15 49 (75)
RL Software Dependencies:
The following O&M configurable parameters are supported for the cell re-selection form LTE to
CDMA/1xRTT:
- searchWindowSize
- cellReselectionPriority
- 1xrtt-Parameters
- cellReselectionPriority
- threshHigh
- threshLow
- tReselection
- 1xrtt-NeighborCellList
- 1xrtt-NeighborCellInfo
HW Requirements:
Interdependencies between Features:
Prepared by: LTE PLM Date Page
2012-05-15 50 (75)
RL Software Dependencies:
- MCS21,
- MCS22,
- MCS23 and
- MCS24
The max supported MCS can be configured via O&M on cell basis.
Cat5 devices are provided with max MCS20 even if LTE829 is enabled as in RL30 there is no
support of 64-QAM in UL.
Furthermore, should Sounding Reference Symbol (SRS) be enabled, support for MCS24 needs to be
Prepared by: LTE PLM Date Page
2012-05-15 51 (75)
MCS24 shall only be applied for PUSCH allocations > 9 PRBs to avoid cases where inband signaling
of CQI, dyn. ACK/NACK etc. would lead to code rate exceeding 1.
The existing performance counters for the MCS usage are extended accordingly.
With 20 MHz, totally 100 RBs can be used for DL and UL. In UL, min 2 RBs need to be reserved for
PUCCH. Thus, the max number of PRBs that can be allocated to PUSCH of a single UE falls back to
96 as PUSCH allocation need to be a multiple of 2, 3 and/or 5. Max number of PRBs to be allocated
in other bandwidths can be derived accordingly. Additionally for 10 MHz case, it is required to
support a configuration with 2 PRBs PUCCH and max 48 PRBs for PUSCH.
Based on 36.213 table 7.1.7.2.1-1, the max instantaneous PHY peak rate is defined for MCS24
(improvement over LTE694 and LTE000458 in brackets):
For TD-LTE, assume PRACH period is every 10ms, w/ frame configuration 1 (DSUUD), the
throughput increase are:
HW Requirements:
Interdependencies between Features: LTE788 Support of 16QAM in UL is required.
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 - - - 3GPP R8
mandatory
The offsets are sent to the UE as part of the measurement configuration. The UE takes the offsets for
the measurement reporting into consideration.
HW Requirements:
Interdependencies between Features: Related optional mobility features are required for part of the
functionality (eg LTE55 Interfrequency handover).
RL Software Dependencies:
4. Operability
Feature LTE 510 adds mechanism to establish new InterRAT neighbor relations also in case new
UTRAN/GERAN cells are created to optimization scope of an existing LTE cell.
Benefits for the Customer: This feature ensures up-to-date Inter RAT relationships, also in case
UTRAN/GERAN cells are added to the network.
Functional Description: Feature LTE 510 adds mechanism to establish new InterRAT neighbor
relations also in case new UTRAN/GERAN cells are created to optimization scope of an existing
LTE cell.
All relevant parameters for Inter RAT neighbor relation establishment will be provided by Nokia
Siemens network management system (NetAct) in case of a co-existing NokiaSiemens 2G/3G
network or by Nokia Siemens network management via northbound interface (Itf-N), in case of
another Nokia Siemens NetAct regional cluster or other vendor's co-existing 2G/3G network.
Figure:
HW Requirements:
Interdependencies between Features: Feature LTE 783 and LTE 784 are pre-requisite for operating
feature LTE 510.
RL Software Dependencies:
Reducing such events, number of call drops and/radio link failures, as well as exchanged signalling
will be also reduced as much as possible.
This feature has to be considered as a first step of MRO-implementation, covering not all
3GPP-defined use cases for MRO, e. g. HO to the wrong cell, but will be evolved furtheron in future
releases to become fully 3GPP compliant (see feature LTE 956 MRO-enhancements).
In order to cater as much as possible radio link failures due to mobility problems, HOs to the wrong
cell can be counted either as too early or too late HO events, whatever results to be more suited.
Benefits for the Customer: This features aims to increase the rado network performance by
increasing the robustness of mobility procedures, resulting in less call drops/radio link failures,
respectively increasing end user quality perception.
Functional Description: The feature Mobility Robustness (MRO) belongs to the set of SON-features
and enables adjustment of Handover-related thresholds like
from long-term evaluation of Performance Measurements reported by Flexi Multiradio BTS and
correlation of such PM with the relevant configuration parameters.
The feature aims to reduce the probability of Radio link failures as much as possible due to
sub-optimal configuration of mobility related parameters.
In the initial network planning the configuration of mobility-related parameters depends on the type
of Flexi Multiradio BTS-deployment. There may be different sets of mobility parameters for different
deployment categories like urban/dense urban/rural areas deployment and the used cell size/transmit
power.
However it is assumed that the initial configuration does not match best for all different Flexi
Multiradio BTS-sites so further fine tuning of these parameters is most often required after
deployment of a Flexi Multiradio BTS e. g. by performing drive tests and/or long-term evaluation of
KPIs.
MRO automates the work flow for fine tuinng of these mobility related parameters, based on the
long-term evaluation of corresponding KPIs.
For this purpose additional PM-counters will be implemented in Flexi Multiradio BTS in order to
enable cause differentiation for detection of too early/too late HOs.
-Too early HO PM counter of "type 2", covering the case of uncompleted HOs (i.e. the HO fails
before its completion)
For supporting the new PM-counters Flexi Multiradio BTS is making use of the Radio Link failure
indication and handover report messages on X2-interface, according to 3GPP Rel. 9.
Base for evaluating suboptimal HO performance will be the existing and/or the new PM counters,
collected by the Flexi Multiradio BTS and reported to NetAct. NetAct will visualize the PM-counters,
indicate performance problems and, possibly, propose new settings for the above listed parameters at
specific Flexi Multiradio BTS.
The feature is of semi-static nature and does not react on short-term to suddenly occuring HO
problems.
As result of system level simulations and system analysis it turned out that it is very essential to have
a crucial amount of performance feedback (PM-counters) from the network in order to trigger the
right measures. Therefore the MRO-algorithm will not operate if there is not enough performance
information available (PM-history).
Biggest gains of MRO are expected in case of scenarios with specific local propagation effects, e.g.
urban infrastructure deployments and specific arrangements of UE movements and cell coverage, like
highway movement on cell edge, etc.
The operator is able to specify policies (e.g. max or min parameter values; which cells should not be
subject to MRO optimisation) on how this feature should work.
The recalculated parameter values are proposed by MRO to the operator who can manually accept or
reject their implementation.
Prepared by: LTE PLM Date Page
2012-05-15 57 (75)
Figure:
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
The auto-configuration process is started by the NetAct Optimizer with selecting the cells to be
updated and providing the required input data.
NetAct Optimizer derives out of these input parameters the above mentioned output parameters. This
process is embedded into the LTE720 auto-configuration frame work.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 OSS5.3 - -
CD3
The feature increases the grade of service for the end user by maintaining well performing and robust
handover relationships (mobility procedures).
Functional Description: NetAct Optimizer utilizes Flexi Multiradio BTS configuration information
and performance counters (Intra-frequency and Inter-frequency Handovers) in order to perform the
analysis task. The evaluation may result in no action or blacklisting a neighbor cell relation.
--> Neighbour cell relations that have been created by the operator (network planning) or have been
created by SON-mechanisms like ANR (automated neighbor relation) and which have an insufficient
handover performance (e.g. weak handover success Rate; threshold is operator configurable) may be
blacklisted by an optimization mechanism or, optionally, manually by an operator.
--> Neighbours cell relations that have been created by the operator or have been created by
SON-mechanisms like ANR (automated neighbor relation) which had been blacklisted, can be
whitelisted/enabled again by the operator (e. g. if an operator wants to re-evaluate the performance of
a formerly blacklisted neighbor relation due to changed environment/toplogy).
--> Neighbours cell relations that have been created by the operator or have been created by
SON-mechanisms like ANR (automated neighbor relation) can be marked by an operator in a way
that they are excluded from optimization.
NOTE:
In case of a neighbor cell is blacklisted any outgoing handover to the target cell is not allowed, neither
via X2 nor via S1-interface.
- No action:
An analyzed relation showed no suspect behavior
- Blacklisting:
A given relation was identified to be unreliable/weak performing.
Prepared by: LTE PLM Date Page
2012-05-15 60 (75)
NetAct suggests a new configuration plan file with updated entries for appropriate Telecom/RRM
black lists.
The changes, proposed by optimization algorithms, can be taken over by pressing the “provisioning”
button.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
In case an unknown physical cell ID (PCI) is detected and reported by a UE to the Flexi Multiradio
BTS the corresponding EUTRAN Cell Global ID (ECGI) is derived with the help of the
UE-measurements.
The Flexi Multiradio BTS resolves the corresponding public IP address of the new found neighbor
Flexi Multiradio BTS and establishes the X2 connection to exchange neighbor cell information
respectively opens the X2 interface for control layer applications.
Benefits for the Customer: The automated detection and configuration of unknown cells
respectively sites supports the self configuration of the neighbor cell information without operator
involvement and planning efforts.
Functional Description: In LTE networks the UE mobility relies on information given by neighbor
cell relations and neighbor cell configurations. An automatic mechanism is implemented to discover
and integrate unknown cells. It supports and allows the automated configuration and update of
neighbor cell information without the need of an off-line planning update of the neighbor cell
configurations.
Prepared by: LTE PLM Date Page
2012-05-15 61 (75)
The UE reports all detected/strongest cells above a given threshold. Therefore it may report strong
cells which physical IDs are currently not yet known to the Flexi Multiradio BTS. In this case the
Flexi Multiradio BTS may send a measurement request to the UE to discover and report the
EUTRAN Cell Global ID (ECGI) for the previously reported unknown physical cell ID.
If the UE is able to deliver the ECGI to the Flexi Multiradio BTS, then the derived ECGI is used as
input to an IP address resolution procedure over S1 which retrieves the IP connectivity information
needed to address the neighbour Flexi Multiradio BTS parenting the new found cell. The procedures
to resolve the IP connectivity information belonging to a ECGI shall be done according 3GPP 36.413.
When the IP connectivity information is received and there is no X2 interface already established to
this neighbour Flexi Multiradio BTS the X2 connectivity is set-up including esstablishment of the
IPsec layer if network domain security is applied followed by the SCTP connection setup.
Note:
There may be cases when the Flexi Multiradio BTS cannot establish a X2 link:
- if the Flexi Multiradio BTS has already setup the max number of X2 connections
- if the target Flexi Multiradio BTS is in the operator's blacklist for X2 link connection (but not for
S1)
On X2 application layer the Flexi Multiradio BTS exchanges a list of served cells and subsequent
configuration parameters with the new neighbour as defined by 3GPP TS 36.423. The exchanged cell
information covers all served cells of a site and is stored in the configuration data bases of both sites.
When the new neighbours are 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 cell configurations.
Active/Passive ANR
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
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
Intra-frequency LTE cells.
Passive ANR
If there are no new unkown 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
normal measurements reports (as received for HO) for detection of unknown cells.
Prepared by: LTE PLM Date Page
2012-05-15 62 (75)
The operator is able to control the behaviour of these ANR-mechanisms by providing configuration
parameters.
Monitoring of ANR is supported by means of performance measurements. The following events can
be monitored:
After new neighbour 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 neigbhor cell configurations.
Both features LTE782 ANR fully UE based and LTE492 ANR can be activated at same time in the
network.
If a new PCI on a certain radio frequency RF is found and the 'PCI/RF IP@ lookup table' contains the
mapping information for this PCI and RF, then the information in the 'PCI/RF/IP@ lookup table' will
be applied.
If the new PCI and RF is not included in the 'PCI/RF/IP@ lookup table', then the LTE782 mechanism
will be applied to detect the required information.
Prepared by: LTE PLM Date Page
2012-05-15 63 (75)
Figure:
HW Requirements:
Interdependencies between Features: LTE 42 Support of DRX in RRC connected mode
RL Software Dependencies:
From creation time onwards the established relations are updated/synchronized automatically in case
of changes occurring at the UTRAN side (deletion of cell or change of the parameters), ensuring
up-to-date Inter RAT neighbor relationships.
Benefits for the Customer: Inter RAT interworking will be available to customers network as soon
as the network is setup and / or extended ensuring up-to-date Inter RAT neighbor relationships.
Functional Description: The configuration of Inter RAT neighbor relations will be handled by
NetAct whereby configuration data, relevant for Inter RAT neighbor relations, will be
uploaded/retrieved from any existing UTRAN network configuration management database and
corresponding Inter RAT neighbor relations are created for the concerned Flexi Multiradio BTS,
taking into account
· the geo-location of the source (LTE) and target UTRAN site / cell antenna,
· sectorization/antenna horizontal main lobe direction of source LTE and target UTRAN cells
(algorithm does basically not care if source and target are collocated),
The relevant parameters for Inter RAT neighbor relation establishment are provisioned by NetAct in
case of a co-existing Nokia Siemens UTRAN network or by NetAct northbound interface (Itf-N) as
external/foreign cells, in case of another Nokia Siemens NetAct regional cluster or other vendor's
co-existing 3G network.
In addition, NetAct Configurator updates/synchronizes LTE Inter RAT neighbor relation information
automatically in case of changes occurring at the UTRAN cells which are relevant for LTE Inter RAT
neighbor relations point of view, ensuring up-to-date Inter RAT neighbor relationships. This is part of
NetAct Configurator's plan prepare functionality.
Changes that may trigger an update/synchronization of the LTE Inter RAT neigbhor relation
configuration are:
Prepared by: LTE PLM Date Page
2012-05-15 65 (75)
Figure:
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
Benefits for the Customer: Inter RAT interworking will be available to customers network as soon
as the network is setup and / or extended ensuring up-to-date Inter RAT neighbor relationships.
Functional Description: The configuration of Inter RAT neighbor relations will be handled by
NetAct whereby configuration data, relevant for Inter RAT neighbor relations, will be
uploaded/retrieved from any existing 2G network configuration management database and
corresponding Inter RAT neighbor relations are created for the concerned Flexi Multiradio BTS,
taking into account
· the geo-location of the source (LTE) and target GERAN site / cell antenna,
· sectorization/antenna horizontal main lobe direction of source LTE and target GERAN cells
(algorithm does basically not care if source and target are collocated),
The relevant parameters for Inter RAT neighbor relation establishment are provisioned by NetAct in
case of a co-existing Nokia Siemens 2G network or by NetAct northbound interface (Itf-N), in case of
another Nokia Siemens NetAct regional cluster or other vendor's co-existing 2G network.
The process of neighbor ship generation can be triggered manually.
In addition, NetAct Configurator updates/synchronizes LTE Inter RAT neighbor relation information
automatically in case of changes occurring at the GERAN cells which are relevant for LTE Inter RAT
neighbor relations point of view, ensuring up-to-date Inter RAT neighbor relationships. This is part of
NetAct Configurator's plan prepare functionality.
Changes that may trigger an update of the LTE Inter RAT neigbhor relation configuration are:
* GERAN BTS deletion
* GERAN cell deletion
* GERAN cell-specific parameter change (for example, frequency, RAC, LAC)
Prepared by: LTE PLM Date Page
2012-05-15 67 (75)
Figure:
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
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 and the iOMS.
2) All operator configured data are 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.
· Adaptations done by operator for different (graphical) presentations in BTS SM or NetAct, e.g. top
level user interface: topology view, as e.g.
· PM configuration
3) System data will be stored before system upgrade. A user-friendly backup concept is in place. No
manual intervention shall be required. The data will be available after upgrade.
· Measurements, as PM data
In case there are command line or scripts used they need to be backward compatible or a converter is
Prepared by: LTE PLM Date Page
2012-05-15 69 (75)
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 OSS5.3 OMS3.0 - -
CD3
In the flat architecture of the LTE, meaning multiple S1 and X2 interfaces this is more important than
e.g. in WCDMA system where only few common interfaces are in place.
Depending on the failed connection and/or node, a single failure can cause in worst case up to
1000-2000 or even more alarm events.
By using alarm correlation instead of this big amount of alarms only a dedicated alarm is send to the
operator in case of interface problems.
Benefits for the Customer: Operator will receive dedicated correlated alarm in case of problems of a
central interface (X2, S1) or entity, avoiding a flood of single alarms.
Functional Description: The solution consists of
HW Requirements:
Interdependencies between Features: LTE424 is based on NetAct7Monitor
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 OSS5.3 - -
CD3
- Tracing evaluation with features cell trace and subscriber trace for network optimization and
troubleshooting to find out location areas with problems, e.g. to find out areas with high drop rates
For all UEs assigned with MAC resource, the TA values will be collected in realtime.
The trace reporting mechanism will be used for reporting of the instantaneous TA value to NetAct or
3rd party tool using trace management framework.
The timing advance (TA) value will be send at start of trace and when TA value changes.
A correlation of traced TA value to the traced UE can be done using the Trace Reference and Trace
Recording Session Reference contained in the Trace Report and Trace Records.
The evaluation tool (e.g. NetAct TraceViewer or 3rd party tool) is responsible to correlate the
instantaneous TA value with other traced messages based on the time sequence using the time stamp.
Ideas for using values of timing advance in evaluation of network performance (not part of this
feature, but may give here some indication for further processing)
- Coverage problems
- Some UEs in the given TA area are scheduled with very high priority (+good radio conditions)
which increases the average CQI
- Many drops proof there are still many UEs experiencing very bad conditions
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
The measurement period can be configured in the FlexiMultiradio BTS per measurement type. The
Prepared by: LTE PLM Date Page
2012-05-15 73 (75)
In default setting in Flexi Multiradio BTS all PM counters are activated and will be reported.
The PM Counters of a measurement type can now be activated/de-activated within a Flexi Multiradio
BTS with NetAct Configurator or BTS Site Manager.
Only counters belonging to activated measurement type are reported to NetAct or to the BTS Site
Manager.
Note: if some counters within a counter group belong to an optional feature then these counters are
only reported if the feature is enabled.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
Currently for all trace features in the LTE trace set (LTE433 Cell Trace, LTE163 Subscriber /
Equipment Trace) the interfaces can be selected to be traced with maximum trace depth as defined by
3GPP is supported.
Prepared by: LTE PLM Date Page
2012-05-15 74 (75)
Benefits for the Customer: Operator can select based on his needs the information he would like to
be kept in trace records.
By that the trace data amount can be limited to required scope and trace data analysis can be focused.
Functional Description: The operator is able to do a message based selection of trace content for cell
traces.
Based on the ASN.1 protocol the operator can choose which messages will be taken into the trace
record, e.g. only the handover messages. The selection is based on the information granularity as
provided with maximum trace depth. So this feature provides a reduction of trace content, but not an
addition to it.
This trace content definition is an addition to the standard defined trace depth steps. The definition is
3GPP conform as it makes use of the vendor specific extension for this purpose.
The configuration of this trace content is based on a simple input format with specific markings of the
messages which shall be collected to the trace content. It is possible to work with wildcards,
respectively an "all" selection is supported. No GUI support is planned for the message selection.
This message selection will be stored in a file and specifies a profile for the trace feature. For each
trace configuration in NetAct Trace Viewer it is possible to individually apply selected trace settings:
So either maximum trace depths or a specific trace profile can be applied.
The operator can easily understand which trace settings are used during the trace activation and the
trace data retrieval. The configuration applied is clearly indicated, e.g. the file name does include the
trace selection done and the applied trace content profile (e.g. file name and profile content) is
included in the content of the trace data once per trace session.
For operator usage already some trace profile selections are prepared as kind of templates for usual
use cases.
For each trace session an individual trace profile can be selected.
HW Requirements:
Interdependencies between Features: LTE433 Cell Trace or LTE163 Subscriber / Equipment Trace
required.
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 OSS5.3 OMS3.0 - - n/a
CD3
The DNS client is used to send the FQDN up to a DNS name sever which returns the corresponding
IP address assigned to the repository.
Supported functions:
Note: reverse lookup, e.g. providing the FQDN which belongs to a given IP address, is not needed in
the context of certificate examination.
HW Requirements:
Interdependencies between Features:
RL Software Dependencies:
LTE eNode B NetAct OMS MME SAE GW UE
Release RL30 LBTS3.0 - OMS3.0 - - n/a