FDD Feature Planning Guide Release LA6.0

Use pursuant to applicable agreements
Title page
Alcatel-Lucent 9400
LTE Radio Access Network | Release LA6.0
FDD Feature Planning Guide
9YZ-03991-0005-FMZZA
Issue 1 | April 2013
Alcatel-Lucent – Proprietary
Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2013 Alcatel-Lucent. All rights reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside
Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.
Alcatel-Lucent – Proprietary
Contents
About this document

Purpose ............................................................................................................................................................................................. xi
xi
Audience .......................................................................................................................................................................................... xi
xi
Scope ................................................................................................................................................................................................. xi
xi
Supported systems ........................................................................................................................................................................ xi

xi
To obtain technical support, documentation, and training or submit feedback ...................................................... xi
How to comment ......................................................................................................................................................................... xii

xii
1 Introduction to the Feature Planning Guide
Overview ...................................................................................................................................................................................... 1-1

1-1
About the features in this document .................................................................................................................................. 1-1

1-1
Available in LA6.0 ................................................................................................................................................................... 1-2

1-2
Listing of features by Feature ID ........................................................................................................................................ 1-2

1-2
Listing of features by Feature Title .................................................................................................................................... 1-3

1-3
Listing of features by Program ............................................................................................................................................ 1-3

1-3
2 LA6.0 features
Overview ...................................................................................................................................................................................... 2-1

2-1
LR Cabinets and Configurations
Overview ...................................................................................................................................................................................... 2-3

2-3
157468 - lightRadio Cabinet LTE LA 5.0.2/6.0 ............................................................................................................ 2-3

2-3
164433 - Support of MCTRDU 1800 in LR Indoor cabinet .................................................................................... 2-7

2-7
LR Multi-Standard RF
Overview ...................................................................................................................................................................................... 2-9

2-9
L115868 - 1800MHz MC-TRDU in LTE Only Mode ................................................................................................ 2-9

2-9
....................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary iii
9YZ-03991-0005-FMZZA Release LA6.0 Use pursuant to applicable agreements
Issue 1 April 2013
Contents
....................................................................................................................................................................................................................................
LR Operational Effectiveness and Element Management System
Overview ................................................................................................................................................................................... 2-11

2-11
131966 - eNB Time Zone Management for FM Files ............................................................................................... 2-11

2-11
L103176 - ANR Support for Inter Freq Neighbours ................................................................................................. 2-13

2-13
L115627 - Performance Counter Enhancements ........................................................................................................ 2-16

2-16
L115811 - eNB Call Trace UPOS header optimization .......................................................................................... 2-17

2-17
LR Telecom Services and Application
Overview ................................................................................................................................................................................... 2-19

2-19
156132 - Overload Control - Outdated RRC messages management ................................................................. 2-19

2-19
L92127 - Commercial Mobile Alert System (CMAS) support ............................................................................. 2-21

2-21
L110547 - RoHC v1 Support for VoIP ........................................................................................................................... 2-23

2-23
L115222 - VoIP Emergency call for commercial deployment .............................................................................. 2-26

2-26
L115223 – Inter-freq Load Balancing ........................................................................................................................... 2-28

2-28
L115241 - Overload Control Evolutions ...................................................................................................................... 2-30

2-30
L115651 - Overload Control Improvements ................................................................................................................ 2-33

2-33
LR Transport and Security
Overview ................................................................................................................................................................................... 2-35

2-35
L112791 - Transport counters ........................................................................................................................................... 2-35

2-35
LTE Digital Evolution, Capacity and Performance
Overview ................................................................................................................................................................................... 2-37

2-37
159512 - LA6 bCEM Paging capacity increase ......................................................................................................... 2-37

2-37
160636 - Non-GBR prioritization .................................................................................................................................... 2-39

2-39
160815 - Optimized Segmentation (MCS Override) ................................................................................................ 2-41

2-41
163993 - eNodeB SW capacity for LA5.03 .................................................................................................................. 2-44

2-44
164117 – bCEM implementation of 163549 - Speed-up throughput recovery after smartphone

specific behavior ........................................................................................................................................................... 2-47
2-47
166046 - PUSCH improvements ...................................................................................................................................... 2-49

2-49
....................................................................................................................................................................................................................................
iv Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Use pursuant to applicable agreements 9YZ-03991-0005-FMZZA Release LA6.0
Issue 1 April 2013
Contents
....................................................................................................................................................................................................................................
L92639 - FDD RACH burst format 2 ............................................................................................................................. 2-50
2-50
L105587 - bCEM commercial introduction ................................................................................................................. 2-52

2-52
L114492 - Generalized OP-PUCCH ............................................................................................................................... 2-53

2-53
L115776 - eNodeB SW capacity ...................................................................................................................................... 2-55

2-55
L115938 - Dual-carrier support on one band ............................................................................................................... 2-57

2-57
LTE RF
Overview ................................................................................................................................................................................... 2-59

2-59
156783 - TMA/RET with AISG 2.0 Enhancements in LA/TLA6 (former L115277) ................................... 2-59
2-59
159276 - Support for RRH2x60-850 (LTE Only) ...................................................................................................... 2-62

2-62
L106226 - RDEM HW ......................................................................................................................................................... 2-65

2-65
L115158 - LTE RRH Antenna Cross Connect Capability Support in LA4.0.1 ............................................... 2-66
2-66
L115268 - PCS Band 2 RRH2x60 HW Requirements ............................................................................................ 2-71

2-71
L115269 - Advanced Technology CR RRH2x40-07L - HW Requirements ..................................................... 2-72

2-72
L115270 - Band 12/17 2x60-7L (Lower 700MHz) TRDU - HW Requirements ............................................ 2-74
2-74
L115512 - LTE HW Requirements for RRH4x40-19 (PCS) 65MHz ................................................................. 2-76

2-76
L115616 - Support for dual-band eNodeB with two modems ............................................................................... 2-77
2-77
L115629 - Support for RRH2x60-19 (LTE Only) ...................................................................................................... 2-79

2-79
Glossary
Index
....................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary v
Issue 1 April 2013
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
vi Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013
List of tables
2-1 Total PRB and RBG size for Different Carrier Configurations ............................................................. 2-39
2-2 User capacity for eNodeB equipped with eCEM in LA6.0 ..................................................................... 2-44
2-3 User capacity for eNodeB equipped with bCEM in LA6.0 ..................................................................... 2-44
2-4 Bearer capacity for eNodeB equipped with eCEM in LA6.0 ................................................................. 2-45
2-5 Bearer capacity for eNodeB equipped with bCEM in LA6.0 ................................................................. 2-45
2-6 Parameters for configuring capacity ................................................................................................................ 2-46
2-7 User capacity for an eNodeB equipped with eCEM in LA6.0 ............................................................... 2-55
2-8 Bearer capacity for an eNodeB equipped with eCEM in LA6.0 ........................................................... 2-55
2-9 Predecessor features and capabilities used by the RRH2x60 configurations .................................... 2-63
....................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary vii
Issue 1 April 2013
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
viii Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013
List of figures
2-1 Stacking the lightRadio™ cabinet ....................................................................................................................... 2-4
2-2 Configurations for the lightRadio™ outdoor cabinet ................................................................................... 2-5
2-3 ANR Support for Inter Freq Neighbours ........................................................................................................ 2-13
2-4 Supported Header Compression Protocols and Profiles ........................................................................... 2-24
2-5 Optimized segmentation ....................................................................................................................................... 2-42

2-42
2-6 eNodeB with antenna cross-connected for three sectors .......................................................................... 2-69
2-7 eNodeB with antenna cross-connected for two sectors ............................................................................. 2-70
....................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary ix
Issue 1 April 2013
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
x Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013
About this document
About this document
Purpose
This document gives a high-level description of all Frequency Division Duplex (FDD)
features introduced in the Long Term Evolution (LTE) Radio Access Network (RAN) in
LA6.0. The purpose of this document is to help service provider personnel prepare to
receive a new release.
Audience
The primary audience for this document is service provider personnel who work with the
LTE RAN in one of the following capacities:
• Network Operation and Maintenance Specialists
• Network Planners
• Engineers with responsibility for network planning, design, configuration, or
optimization
A secondary audience is Alcatel-Lucent personnel who are interested in learning about the
LTE RAN feature set.
Scope
This document lists features for the 9400 eNodeB only, not for the entire LTE Solution.
Supported systems
This document applies to the frequency division duplex (FDD) version of LTE RAN
Release LA6.0.
To obtain technical support, documentation, and training or submit feedback

The Online Customer Support (OLCS) web site (http://support.alcatel-lucent.com),
provides access to technical support, related documentation, related training, and
feedback tools. The site also provides account registration for new users.
...................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary xi
Issue 1 April 2013
About this document
....................................................................................................................................................................................................................................
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com) (comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
xii Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013
1 I1ntroduction to the
Feature Planning Guide
Overview
Purpose
This chapter explains how features were selected for this document.
Contents
About the features in this document 1-1

Available in LA6.0 1-2
Listing of features by Feature ID 1-2
Listing of features by Feature Title 1-3
Listing of features by Program 1-3
About the features in this document

Customer-viewable features
This document describes customer-viewable features that are new in this release.
Both optional and base

Both optional and base features are included.
Selection criteria
The following rules were applied when selecting the features to go into this document:
• Only LA6.0 features are included.
• Internal-only, tracking, parity, and demo features are not included. (Trial features,
however, are included.)
...................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary 1-1
Issue 1 April 2013
Introduction to the Feature Planning Guide About the features in this document
....................................................................................................................................................................................................................................
• Only eNodeB features are included.
• NPO features are not included.
What is a parity feature?

A parity feature is a feature that takes an existing feature and provides it on a new piece
of equipment.
Organizing principles
In this document, features are grouped using the following organizing principles:
• Features are grouped by program.
• Within program, features are presented in numerical order by Feature ID (FID).
What is a program?
A program is a development organization within Alcatel-Lucent charged with developing
a certain type of feature. From the customer's point of view the programs can be
considered general categories in which to group LTE RAN features.
Available in LA6.0
LA6.0
All features listed in this document are available in LA6.0.
Listing of features by Feature ID

Listed in index
To find a feature by the feature ID, look in the index.
....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013
Introduction to the Feature Planning Guide Listing of features by Feature Title
....................................................................................................................................................................................................................................
Listing of features by Feature Title

Listed in index
To find a feature by feature title, look in the index.
Listing of features by Program

Listed in index
To find a feature by its Program, look in the index.
....................................................................................................................................................................................................................................
Issue 1 April 2013
Introduction to the Feature Planning Guide Listing of features by Program
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 1 April 2013
2 LA6.0 features
2
Overview
Purpose
This chapter describes customer-viewable features introduced in LTE RAN LA6.0.
The features are sorted by program and, within program, by Feature ID (FID).
Contents
LR Cabinets and Configurations 2-3

157468 - lightRadio Cabinet LTE LA 5.0.2/6.0 2-3
164433 - Support of MCTRDU 1800 in LR Indoor cabinet 2-7
LR Multi-Standard RF 2-9
L115868 - 1800MHz MC-TRDU in LTE Only Mode 2-9
LR Operational Effectiveness and Element Management System 2-11
131966 - eNB Time Zone Management for FM Files 2-11
L103176 - ANR Support for Inter Freq Neighbours 2-13
L115627 - Performance Counter Enhancements 2-16
L115811 - eNB Call Trace UPOS header optimization 2-17
LR Telecom Services and Application 2-19
156132 - Overload Control - Outdated RRC messages management 2-19
L92127 - Commercial Mobile Alert System (CMAS) support 2-21
L110547 - RoHC v1 Support for VoIP 2-23
L115222 - VoIP Emergency call for commercial deployment 2-26
L115223 – Inter-freq Load Balancing 2-28
L115241 - Overload Control Evolutions 2-30
L115651 - Overload Control Improvements 2-33
...................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features Overview
....................................................................................................................................................................................................................................
LR Transport and Security 2-35

L112791 - Transport counters 2-35
LTE Digital Evolution, Capacity and Performance 2-37
159512 - LA6 bCEM Paging capacity increase 2-37
160636 - Non-GBR prioritization 2-39
160815 - Optimized Segmentation (MCS Override) 2-41
163993 - eNodeB SW capacity for LA5.03 2-44
164117 – bCEM implementation of 163549 - Speed-up throughput recovery 2-47
after smartphone specific behavior
166046 - PUSCH improvements 2-49
L92639 - FDD RACH burst format 2 2-50
L105587 - bCEM commercial introduction 2-52
L114492 - Generalized OP-PUCCH 2-53
L115776 - eNodeB SW capacity 2-55
L115938 - Dual-carrier support on one band 2-57
LTE RF 2-59
156783 - TMA/RET with AISG 2.0 Enhancements in LA/TLA6 (former 2-59
L115277)
159276 - Support for RRH2x60-850 (LTE Only) 2-62
L106226 - RDEM HW 2-65
L115158 - LTE RRH Antenna Cross Connect Capability Support in LA4.0.1 2-66
L115268 - PCS Band 2 RRH2x60 HW Requirements 2-71
L115269 - Advanced Technology CR RRH2x40-07L - HW Requirements 2-72
L115270 - Band 12/17 2x60-7L (Lower 700MHz) TRDU - HW Requirements 2-74
L115512 - LTE HW Requirements for RRH4x40-19 (PCS) 65MHz 2-76
L115616 - Support for dual-band eNodeB with two modems 2-77
L115629 - Support for RRH2x60-19 (LTE Only) 2-79
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Overview
Purpose
This section lists customer-viewable features that were developed in the LR Cabinets and
Configurations program for this release.
Contents
157468 - lightRadio Cabinet LTE LA 5.0.2/6.0 2-3

164433 - Support of MCTRDU 1800 in LR Indoor cabinet 2-7
157468 - lightRadio Cabinet LTE LA 5.0.2/6.0

157468 - lightRadio Cabinet LTE LA 5.0.2/6.0
Global Market
Feature Description
This feature provides a new state-of-the-art cabinet for the Alcatel-Lucent lightRadio™
product.
Note: Both indoor (9711) and outdoor (9712) versions of the cabinet are available.
Feature Benefits
The lightRadio™ 9711 Indoor and 9712 Outdoor cabinet family provides the following
benefits for the customer:
• A single cabinet family for all Alcatel-Lucent base station products.
• One physical housing for multiple technologies (Alcatel-Lucent 2G, 3G, and 4G BTS
hardware) to reduce customer total cost of ownership (TCO).
• More accurate frame alarms to describe faults associated with ancillary cabinet
hardware.
• A smooth migration path to the lightRadio™ cabinet.
• A variety of configuration options.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 157468 - lightRadio Cabinet LTE LA 5.0.2/6.0
....................................................................................................................................................................................................................................
Smaller, lighter cabinets
The lightRadio Outdoor Cabinet is sized such that craning is not required for installation
in those instances where local safety standards allow manual lifting of equipment of this
weight, and where lifting aids may be necessary as required by those standards.
In addition, lightRadio™ cabinets can be stacked to save floor space.
Figure 2-1 Stacking the lightRadio™ cabinet
Multiple configuration options

The lightRadio™ cabinet allows a variety of configurations. The lightRadio
small/compact cabinet set is basically two building blocks from which cabinet
configurations can be constructed to suit customer needs, as demonstrated in Figures 2-1
and 2-2.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Figure 2-2 Configurations for the lightRadio™ outdoor cabinet
Impacted Systems
LTE OAM software is affected by the cabinet design since the set of frame alarms and
how they are wired to the eNodeB alarm collection module differs from previous cabinet
designs.
Dependencies
Features
None.
Hardware
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Software
Requires SAM and NEM for reporting of new alarms.
Interworking
None.
Devices
None.
Standards
None.
Restrictions/Limitations
None.
Engineering Impacts
This feature affects installation and commissioning procedures in the following ways:
• If an LTE BBU is cabled to the eAM alarm collection module then it must be
programmed with the appropriate BTSPackaging value as defined below.
• If an LTE BBU is not cabled to the eAM (that is, another BBU within the cabinet is
cabled to the eAM and reports cabinet frame alarms) then it must be programmed
with a BTSPackaging value of 0x14.
• DIP switches on the lightRadio™ Cabinet Controller (LRCC) of each unit must be set
according to the unit type (Compact or Small) and presence of TRDU shelf (TRDU
Alarm enabled/disabled).
About alarms
Different versions of the lightRadio cabinet support different sets of alarms. Software
currently uses the BTSPackaging value to determine the proper alarm set for this cabinet
type. The following new package types are provided to describe the lightRadio™
cabinets:
• 0x32 = 9711 lightRadio™ Cabinet, Indoor, AC power
• 0x36 = 9711 lightRadio™ Cabinet, Indoor, DC power
• 0x33 = 9712 lightRadio™ Cabinet, Outdoor, AC power
• 0x37 = 9712 lightRadio™ Cabinet, Outdoor, DC power
• 0x38 = 9712 lightRadio™ Cabinet, Outdoor, AC power, North American Market
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Operational Requirements
Customer-viewable changes related to OA&M for these new cabinets include the
following:
• New Frame Type Identifiers
• New Frame Alarms
• New Frame Alarm Configurations
Feature Type
Base
164433 - Support of MCTRDU 1800 in LR Indoor cabinet

164433 - Support of MCTRDU 1800 in LR Indoor cabinet
Global Market
Feature Description
This feature provides support of MCTRDU 1800 in LR Indoor cabinet. This
configuration is based on bCEM for BBU.
Feature Benefits
This feature provides support of MCTRDU 1800 in LR Indoor cabinet. This
configuration is based on bCEM for BBU.
Impacted Systems
eNodeB hardware.
Dependencies
Features
None.
Hardware
None.
Software
None.
Interworking
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 164433 - Support of MCTRDU 1800 in LR Indoor cabinet
....................................................................................................................................................................................................................................
Devices
None.
Standards
None.
NA
Engineering Impacts
NA
NA
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Overview
Purpose
This section lists customer-viewable features that were developed in the LR
Multi-Standard RF program for this release.
Contents
L115868 - 1800MHz MC-TRDU in LTE Only Mode 2-9
L115868 - 1800MHz MC-TRDU in LTE Only Mode

L115868 - 1800MHz MC-TRDU in LTE Only Mode
Global Market
Feature Description
The Multi-Carrier Transmit Receive Duplexer Unit (MC-TRDU) is essentially a
frame-mounted Radio Frequency (RF) head. This feature provides the hardware and
eNodeB configurations for the MC-TRDU. Software support is provided for LTE-only
Band 3 operation, and supports a single 20MHz or 10MHz carrier.
Feature Benefits
This feature provides the MC-TRDU and eNodeB configurations with potential to
support many future enhancements. The initial release is capable of 60W RF output
which, in some deployments, may increase coverage or downlink data rates or both.
Impacted Systems
The impacts of this feature are mainly internal to the system. WPS, NPO Tools support
this feature.
Dependencies
Features
1800 MHz LTE Band 3 configurations and requirements are provided with 115292 in
LA5.0. Many hardware aspects of MC-TRDU are derived from work done for 113600
“1800 MHz MC-RRH in LTE-Only Mode”.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115868 - 1800MHz MC-TRDU in LTE Only Mode
....................................................................................................................................................................................................................................
Hardware
None.
Software
None.
Interworking
No dependencies.
Devices
No dependencies - 1800 MHz LTE Band 3 user equipment required for service.
Standards
eNodeBs will be CE marked 3GPP compliant at eNodeB. Antenna Interface Standards
Group (AISG) 2.0 is supported with an internal smart bias-tee on the first antenna port of
each MC-TRDU (sector) and by a separate AISG port.
The initial release operates in LTE-only mode. Alternative and multiple technologies may
be supported in future releases.
The initial release supports a single LTE carrier. Multiple carriers may be supported in
future releases.
The initial release supports a 20MHz and 10MHz carrier. Other carrier bandwidths may
be supported in future releases.
The initial release supports a single CPRI connection per MC-TRDU.
The initial release supports a single fan alarm for the two fans per MC-TRDU.
The initial release supports fixed CPRI rate 3.
Engineering Impacts
Cell planning, installation of hardware, and software configuration.
None.
Feature Type
Base.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LR Operational Effectiveness and Element Management
System
....................................................................................................................................................................................................................................
LR Operational Effectiveness and Element

Management System
Overview
Purpose
This section lists customer-viewable features that were developed in the LR Operational
Effectiveness and Element Management System program for this release.
Contents
131966 - eNB Time Zone Management for FM Files 2-11

L103176 - ANR Support for Inter Freq Neighbours 2-13
L115627 - Performance Counter Enhancements 2-16
L115811 - eNB Call Trace UPOS header optimization 2-17
131966 - eNB Time Zone Management for FM Files

131966 - eNB Time Zone Management for FM Files
USA Market, Partial Global Support
Feature Description
This feature provides enhanced Fault Management supporting the local time zone of the
eNodeB.
With this feature, the eNodeB provides and manages the UTC offset and the DST rules.
This feature displays the eNodeB local time with +/- UTC offset if timeZoneName is set
to “Non-UTC”.
The parameter timeZoneName, introduced in LA5.0, is also used to support this feature.
This parameter allows the operator to configure the timeZoneName for a particular
eNodeB via the SAM.
Note: The timeZoneName format matches with the Olson time zone database for
timeZoneName format.
This feature supports the eNodeB local time with UTC offset for eNodeB alarms, events
and state change.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 131966 - eNB Time Zone Management for FM Files
System
....................................................................................................................................................................................................................................
Note: For alarm time, the SAM displays the eNodeB local time; for event entry time,
the SAM displays the SAM local time. For state change time, the SAM does not
display. Note that the state change time is the time when alarm status change.
Feature Benefits
This feature provides the operator the actual time on the eNodeB, which can often be
different from the time of the management system. Having the actual time on the actual
eNodeB is an aid to troubleshooting the actual time in which fault and error conditions
may have occurred on the eNodeB.
Impacted Systems
SAM, NEM, eNodeB
Dependencies
None.
None.
Engineering Impacts
None.
This feature has no additional license or activation needed.
Feature activation flag: timeZoneName = “UTC” (feature is off) Activated by default: no
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L103176 - ANR Support for Inter Freq Neighbours
System
....................................................................................................................................................................................................................................
L103176 - ANR Support for Inter Freq Neighbours

L103176 - ANR Support for Inter Freq Neighbours
Global Market
Feature Description
This feature extends the functionality of the Automatic Neighbour Relation (ANR)
feature to include Inter-Frequency neighbours. The Inter-frequency neighbours
functionality broadens the scope to include the full range of deployable spectrum
allocation for LTE neighbours. Broadening the scope ensures support for all deployment
scenarios and provides the potential for future spectrum re-farming.
Inter-frequency ANR uses the following phases: active, dormant, and wake-up.
Figure 2-3 ANR Support for Inter Freq Neighbours
....................................................................................................................................................................................................................................
Issue 1 April 2013
System
....................................................................................................................................................................................................................................
What is Automatic Neighbor Relation (ANR)?
Automatic Neighbor Relation (ANR) is a capability that enables the eNodeB to create and
maintain its neighbor lists automatically, which reduces the operator’s maintenance
expenses and improves the accuracy of the neighbor lists. Features in previous releases
provided ANR for intra-frequency LTE neighbors (108172) and for UTRAN FDD
neighbors (108084). This feature, 103176, introduces commercial delivery of ANR
capability for LTE inter-frequency FDD and TDD neighbors.
How it works
The basic process for inter-frequency ANR is very similar to that for intra-frequency
ANR:
1. The active phase is triggered when the feature is enabled.
2. When a new neighbor is reported the eNodeB asks the UE to report the CGI.
3. When the CGI is reported the eNodeB adds a new entry to its neighbour list.
4. The procedure to attempt X2 link establishment is invoked.
ANR interworking
At any given time a particular UE will be asked to perform an ANR measurement for only
one frequency.
When multiple entities (intra-freq, inter-freq and IRAT) need to perform ANR, the ANR
measurements dispatch function prioritizes the requests. Priorities are based on each
frequency’s ANR priority, determined by the default Connected Priority Of Freq
parameter (defaultConnectedPriorityOfFreq) and the current phase (the active phase is
higher in priority than the wake-up phase).
The Service Provider can configure the number of UEs to target in the active and wake-up
phases of inter-frequency ANR.
Configurable by service provider

With this feature the service provider can configure:
• The number of measurements received before ending the active phase.
• The number of consecutive measurements received with no new neighbour discovered
before ending the active phase.
• The measurement configuration that is provided to UEs for the inter-frequency ANR
measurement.
• The neighboring LTE frequencies to include for ANR.
• The length of the DRX cycle used when requesting the UE to report the ECGI.
• The length of the garbage collection interval.
• The number of UE measurements to target for active phase and monitoring phase.
....................................................................................................................................................................................................................................
Issue 1 April 2013
System
....................................................................................................................................................................................................................................
• Whether to delay ANR for a particular frequency until an X2 link is established to an
eNodeB using that frequency.
• Whether to allow ANR to trigger X2 link establishment when ANR discovers a
neighbour for a particular frequency.
Compared to Intra-Freq ANR

The main difference between Inter-Freq ANR and Intra-Freq ANR is that with Inter-Freq
ANR there can be multiple LTE neighbour frequencies to manage (MIM currently allows
up to 9 LTE frequencies) and each frequency can be in a different ANR state.
Feature Benefits
This extension to the ANR feature is important since LTE will be deployed and will need
to interoperate in networks where LTE is deployed on more than one frequency band.
Impacted Systems
eNodeB, EMS
Dependencies
Features
Intra-frequency ANR (108172) must be enabled in order to use inter-frequency ANR.
Hardware
This feature is for bCEM. Inter-freq ANR for eCEM (103176.1) was introduced in a
previous release.
Software
None.
Interworking
None.
Devices
Note: A UE will not be asked to perform inter-frequency ANR measurements if it has
a GBR bearer established or if a Circuit Switched Fall Back (CSFB) indication has
been received on the S1 Application Protocol (S1-AP) interface.
With this feature, the UE must support all of the following:
• Frequency band to be measured (indicated in UE-EUTRA-Capability structure)
• Long DRX cycle and MAC DRX command (indicated by Feature Group Indicator bit
5)
....................................................................................................................................................................................................................................
Issue 1 April 2013
System
....................................................................................................................................................................................................................................
• The type of measurement event (FGI bit 14 indicates if events A4 and A5 are
supported)
• ANR related inter-frequency measurement (FGI bit 18)
Standards
36.331
This feature does not support inter-frequency ANR for a frequency with a different frame
structure than the serving frequency (FDD serving to TDD neighbour or TDD serving to
FDD neighbour).
Engineering Impacts
None.
None.
Feature Type
Optional
L115627 - Performance Counter Enhancements

L115627 - Performance Counter Enhancements
Global Market, NAR Market
Feature Description
This feature supports new Performance Measurement (PM) counters and the ability to
support Failed Connection attempt reporting. This additional information supports better
network troubleshooting and Key Performance Indicator (KPI) monitoring.
These improvements include the addition of counters for the following:
• DL Burst Volume and DL Burst Time per QCI
• Additional RRC Connection Success counters per Cause
• Average DL sector throughput
• Peak DL sector throughput
• Number of abnormally released active SAE bearers
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115627 - Performance Counter Enhancements
System
....................................................................................................................................................................................................................................
Feature Benefits
The benefits of this feature include reduced Operating Expenses (OPEX) and more
accurate counters for network optimization and stability purposes.
Impacted Systems
eNodeB (modem and callP)
Dependencies
This feature does not have any dependencies.
The counters are applicable for FDD only.
Engineering Impacts
None.
New performance measurement counters are introduced with this feature.
All of the counters in this feature are always reported (no feature activation is necessary).
Feature Type
Base
L115811 - eNB Call Trace UPOS header optimization

L115811 - eNB Call Trace UPOS header optimization
Global Market
Feature Benefits
This feature enables the 5620 SAM to collect call trace data from more eNodeBs while at
the same time reducing the backhaul traffic. This feature significantly optimizes the
header for streaming call trace messages, thereby reducing traffic on the backhaul.
Impacted Systems
The 5620 SAM, eNodeB, and all tools that analyze UPOS trace messages will be
impacted.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115811 - eNB Call Trace UPOS header optimization
System
....................................................................................................................................................................................................................................
The 3GPP formatted call trace file names on SAM will now contain the macroEnbID
instead of the macro eNBUuniqueName in the identification as explained below.
Call trace filename according to the 32.423 standard should be the following:
<Type><Startdate>.<Starttime>
<SenderType>.<SenderName>.[<TraceReference>].[<TraceRecordingSessionRef>]
Where SenderName field is the identifier of the NE that recorded and sent the trace file.
The unique identifier of the NE will be the macroEnbID.
Dependencies
Features
None.
Hardware
None.
Software
eNodeB, 5620 SAM, WTA, eDAT, Easy Analyser and any other debug trace analysis tool
Interworking
None.
Devices
None.
Standards
None.
None.
Engineering Impacts
This feature will significantly reduce the data streamed for call trace per eNodeB
resulting in improved efficiency of bandwidth usage.
The UPOS message is an internal stream from the eNodeB to the EMS. Changes in the
UPOS message internal stream will not impact any external customer tool.
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Overview
Purpose
This section lists customer-viewable features that were developed in the LR Telecom
Services and Application program for this release.
Contents
156132 - Overload Control - Outdated RRC messages management 2-19

L92127 - Commercial Mobile Alert System (CMAS) support 2-21
L110547 - RoHC v1 Support for VoIP 2-23
L115222 - VoIP Emergency call for commercial deployment 2-26
L115223 – Inter-freq Load Balancing 2-28
L115241 - Overload Control Evolutions 2-30
L115651 - Overload Control Improvements 2-33
156132 - Overload Control - Outdated RRC messages

management
156132 - Overload Control - Outdated RRC messages management
Global Market
Feature Description
In an overload situation some RRC Connection Request messages may be outdated when
treated by the Call Processing function. In order to avoid unnecessary processing and
signaling these messages will be discarded when the time spent in the eNodeB is greater
than the contention resolution timer.
Feature Benefits
This feature improves the eNodeB’s Overload Control mechanism.
Impacted Systems
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 156132 - Overload Control - Outdated RRC messages
LR Telecom Services and Application management
....................................................................................................................................................................................................................................
Dependencies
Features
None.
Hardware
None.
Software
None.
Interworking
None.
Devices
None.
Standards
None.
None.
Engineering Impacts
None.
New screening “TooLateEnbResponse” for existing counters:
• #12304 RRC connection failure
• #12310 RRC connection re-establishment failure
To ensure backwards compatibility with NPO or customer tools, the new screenings are
under activation flag.
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L92127 - Commercial Mobile Alert System (CMAS) support
....................................................................................................................................................................................................................................
L92127 - Commercial Mobile Alert System (CMAS) support

FID L92127 - Commercial Mobile Alert System (CMAS) support
Global Market
Feature Description
This feature provides the required eNodeB functionality for support of the Commercial
Mobile Alert system (CMAS). CMAS is a voluntary government regulatory mandate,
targeted mainly for public safety.
The figure below describes the high-level architecture for the end-to-end CMAS solution
across various Radio Access Technologies, including LTE.
The figure below illustrates the CMAS end-to-end message flow for a successful
scenario. Note that in this figure, SIB1 may also be updated at the same time as the
CMAS Indication in Paging in order to schedule SIB12.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Specific eNodeB functionality for the support of CMAS focuses on:

• Call Processing: S1-AP enhancement for receiving CMAS warning notification from
MME, mainly support for the Write-Replace procedure and the Kill Procedure in
TS36.413.
• Modem: Downlink scheduler support of delivery of CMAS alert to the UE including
creation of SIB12 to carry CMAS messages, paging enhancement, scheduling of
delivery, transmission, retransmission and stopping. TS36.331 provides relevant
specifications.
New parameters and counters are introduced for this new feature.
Feature Benefits
This feature provides the benefit of alerting subscribers of emergencies where life or
property is at imminent risk and some responsive action should be taken.
Note that this feature is Semi Mandatory for carrier networks starting around April 2012.
Impacted Systems
OAM, eNodeB.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Dependencies
Features
• m11005-01: MME support for Warning Message Delivery
• LS39000-01: End-to-End Support of CMAS
Hardware
• None
Software
• None
Interworking
• CMAS Server (CMSP Gateway)
Devices
• UE supporting CMAS
Standards
• TS 23.401 (architecture)
• TS 29.168 (SBc)
• TS36.331 (RRC) – sections 4.2.1, 4.4, 5.2, 5.3.2, 6.2.2, and 6.3.
• TS36.413 (S1-AP) – sections 8.12, 9.1 and 9.2
Feature Type
Optional
L110547 - RoHC v1 Support for VoIP

FID L110547 RoHC v1 Support for VoIP
Global Market
Feature Description
This feature supports a subset of version 1 of 3GPP Rel-8 RoHC profiles, in particular the
profiles that are useful for VoIP.
The following RoHC V1 profiles are supported:
• 0x0000 No compression RFC 4995
• 0x0001 RTP/UDP/IP RFC 3095, RFC 4815
• 0x0002 UDP/IP RFC 3095, RFC 4815
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L110547 - RoHC v1 Support for VoIP
....................................................................................................................................................................................................................................
Figure 2-4 Supported Header Compression Protocols and Profiles
Profile Identifier Usage Reference
0x0000 No compression RFC 4995

0x0001 RTP/UDP/IP RFC 3095, RFC 4815
0x0002 UDP/IP RFC 3095, RFC 4815
0x0003 ESP/IP RFC 3095, RFC 4815
0x0004 IP RFC 3843, RFC 4815
0x0006 TCP/IP RFC 4996
0x0101 RTP/UDP/IP RFC 5225
0x0102 UDP/IP RFC 5225
0x0103 ESP/IP RFC 5225
0x0104 IP RFC 5225
The following figure provides an example of the degree of header compression that can
be realized for the case of the AMR codec and the RTP/UDP/IP (IPv4 and IPv6) protocol
stack (expected to be the most widely used for the VoLTE application).
Note: This a bCEM-only feature since RoHC has been supported on the eCEM since
LA4.
Feature Benefits
This feature greatly reduces the header size of VoIP, so to increase the VoIP capacity.
Without this feature the VoIP capacity will not meet the commercial capacity
requirements.
Impacted Systems
OAM
• To configure RoHC on the eNodeB, the RoHC needs to be activated first via RoHC
activation flag "ActivationService::isRohcAllowed". This flag is global to the
eNodeB.
• Then for the VoIP bearer (determined by the QCI for that TRB), the RoHC profile
parameter "TrafficRadioBearerConf::rohcProfiles" must be set to "110000000" to
activate the two profiles of 0x0001 and 0x0002 (the no-compression profile 0x0000
will be activated if RoHC is activated for that radio bearer).
• In LA6.0, the QCI for VoIP bearer is determined by parameter "qCIforVoipRtpRtcp".
• There are no other parameters needed to activate RoHC. There are a number of RoHC
tuning parameters. Please refer to the Alcatel-Lucent customer documentation for
more information on those parameters.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Dependencies
Features
• L110547.1 - RoHC v1 support for VoIP trial
The LA6 RoHC support feature L110547 is the parity feature for L110547.1 for LA4.0.1
for VoIP trial support. Therefore L110547.1 must be certified first.
Hardware
None. The LA6 eNodeB shall be HW ready for this feature.
Software
None. The LA6 eNodeB shall be SW ready for this feature.
Interworking
IoT test with UE must be carried out. There is no IoT to the EPC, and to other eNodeBs.
Devices
• UE
RoHC runs between the UE and eNodeB. The UE must support RoHC v1 profiles per
3GPP and comply with relevant RFCs. The minimum requirement is that UE shall
support the three profiles - 0x0000, 0x0001 and 0x0002.
Standards
• RFCs
RoHCv1 profiles are defined by RFC 3095 frame work and RFC 4815 enhancements:
• RFC 3095 = ROHC frame work with 4 original profiles – IP, UDP, RTP and ESP
• RFC 4815 = clarification and correction to RFC 3095
Also RFC 4995 updates RFC3095.
• RoHC profiles
This feature supports only RoHC v1 profiles 0x0000, 0x0001 and 0x0002, and only for
VoIP TRBs. Other TRBs shall have RoHC deactivated.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Engineering Impacts
When implemented this feature has the following engineering impacts:
• The Uplane processing load will increase because of the extra processing needed for
the RoHC stack. However, because the increased processing is for VoIP only, the
increased load is minimal in LA6.
• In addition, this feature causes increased memory consumption to store RoHC
contexts. Again, this is minimal in LA6.
• The PLR will increase due to use of RoHC (decompression failure). Therefore. the
VoIP speech quality will be impacted.
• It is assumed the VoIP flows consist of only two subflows, one for RTP/UDP/IP
(profile 0x0001) and one for RTCP/UDP/IP (profile 0x0002). If there are more flows
in the VoIP channel, there will be no compression for other flows (using profile
0x0000).
If the RoHC parameter tuning is not properly done, the tuning can have a negative impact
on VoIP quality. In the worst case, if the parameters are not set properly, there might be
more burst errors for speech frame, causing a temporary dip in speech quality. To prevent
this problem, perform RoHC performance optimization.
Do not attempt to activate RoHC profiles for anything except the VoIP bearers. Doing so
may cause the system to become unstable.
Feature Type
Base
L115222 - VoIP Emergency call for commercial deployment

FID L115222 VoIP Emergency call for commercial deployment
Feature Description
This feature allows the eNodeB to support IMS Emergency VoIP calls. The following
capabilities are supported by this feature:
• NULL Integrity Protection algorithm (EIA0) for air interface – used for UEs making
an emergency call that cannot be authenticated.
• Broadcast indication of whether IMS Emergency calls are allowed for Limited
Service Mode (LSM) UEs.
• Ignore Handover Restriction List while an emergency call is ongoing.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115222 - VoIP Emergency call for commercial deployment
....................................................................................................................................................................................................................................
• Option to reserve some RRC connections at the cell level for emergency calls (IMS or
CSFB).
• When an emergency call needs to use a reserved connection then preemption can be
used in order to maintain the desired number of reserved connections.
• When at the limit on # of RRC connections at the eNodeB level a new emergency call
can be admitted if pre-emption is enabled and there is an existing UE that can be
preempted.
• Support of bearers combination: EC VoIP + regular VoIP.
Note that this is a bCEM-only feature since VoIP EC has been supported on the eCEM
since LA5.
Feature Benefits
This feature enables the eNodeB to support IMS Emergency VoIP calls, which is a
prerequisite of LTE VoIP launch due to regulatory requirements in some countries.
Impacted Systems
OAM and eNodeB
Dependencies
Features
End to End feature: LS30031-06 Commercial LBS/E-911
eNodeB feature: L115222.1 Voice over LTE for commercial deployment
Hardware
None
Software
None
Interworking
E2E Network solution for emergency call support, including UE, MME, IMS,
eSMLC/GMLC/SLP, and LRF.
The pre-emption actions for emergency calls are dependent on enabling LA4.0 L114539.
Regarding geolocation, while various geolocation methods may be applied in order to
locate a UE making an emergency call, the geolocation capabilities do not behave
differently depending on whether the call is an emergency one.
Devices
Requires 3GPP R9 with IMS client supporting Emergency VoIP and EIA0.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115222 - VoIP Emergency call for commercial deployment
....................................................................................................................................................................................................................................
Standards
3GPP R9 36.331, 36.413
None
Engineering Impacts
None
The feature needs to be enabled in eNodeB OA&M.
Access class barring information needs to be set in the eNodeB OA&M according to the
access class policy for an emergency call.
3GPP allows the disabling of EC for a UE in Limited Service Mode. The choice is service
provider and FCC dependent. If the service provider has chosen to allow EC for a UE in
Limited Service Mode, the support of NULL Integrity Protection algorithm (EIA0) has to
be set in the eNodeB OA&M.
The ARP priority for an emergency call has to be set in the eNodeB OA&M.
The number of connection contexts reserved for Emergency calls has to be set in the
eNodeB OA&M.
Feature Type
Base
L115223 – Inter-freq Load Balancing

L115223 - Inter-freq Load Balancing
Optional feature name

Inter-frequency Load Balancing
OI number
3BK36395DBAA
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115223 – Inter-freq Load Balancing
....................................................................................................................................................................................................................................
Feature Description
This feature introduces the capability of performing load balancing between eUTRAN
carriers.
The feature can be split by function, into three parts:
• Preventive offloading / load balancing: Includes the triggers and mechanisms used to
balance the load between LTE carriers in connected mode
• Load information exchange over X2, per 3GPP TS36.423: Allows the gathering of
load information from neighbor cells in eNodeBs connected through X2
– Aims to redirect UEs to another frequency within LTE when the cell becomes
loaded.
– Cell load is determined by the total number of UL/DL PRBs consumption.
– Threshold configurable by operator.
– Hysteresis configurable parameter (in the order of seconds) preventing load
balancing from being triggered too often.
• eMCTA load and capacity filtering: Allows the system to avoid triggering an
inter-frequency handover to a cell that is highly loaded.
The target cell load can be used by eMCTA as either a differentiator or as target cell
selection criteria.
As a differentiator, the information allows the cell with the lesser load to be selected.
As target cell selection criteria, the information can be used, along with a threshold
condition, to filter out target cells that have a certain load.
Note that this a bCEM-only feature since Interfreq LB has been supported on the eCEM
since LA5.
Feature Benefits
Service providers want to make the best possible use of their spectrum while ensuring the
best possible Quality of Service to their subscribers. One way to achieve this is through
ensuring proper balancing of the load across technologies/carriers.
Impacted Systems
OAM and eNodeB
Dependencies
Features
L115372 Transport CAC
Standards
36.423 X2 application protocol
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115223 – Inter-freq Load Balancing
....................................................................................................................................................................................................................................
If there are too many neighboring eNodeBs and the periodicity of resource status update
is too short, CPU load might be increased significantly.
Engineering Impacts
See "Restrictions/Limitations".
Feature Type
Optional
L115241 - Overload Control Evolutions

FID L115241 - Overload Control Evolutions
Feature description
This feature adds improvements to the Overload function introduced in LA3.0 by feature
L97930 Overload Control, including introduction of new Processor Occupancy counters.
This feature provides two types of overload control mechanisms
• Gradual overload, which provides a smooth adaptation by progressively restricting
some functionalities of the eNodeB as overload increases
• Panic overload, which uses a simple mechanism to prevent resource exhaustion and
avoid a board crash until the system starts to implement corrective actions triggered
by gradual overload mechanisms
About gradual overload
Gradual overload control has the following characteristics:
• Four overload levels are supported (OK, MINOR, MAJOR, CRITICAL).
• Overload Control is based on Processor Occupancy.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115241 - Overload Control Evolutions
....................................................................................................................................................................................................................................
• The following framework to compute and broadcast board overload levels inside the
eNodeB:
– Each board measures its CPU and global RAM consumption on a per-processor
basis.
– Reports CPU and RAM usage as new counters (Max, Average, and for CPU,
Histogram) and sends an event each time a threshold is crossed.
– Computes a consolidation board overload level from each board's critical threads
Processor Occupancy measures.
• Thresholds and hysteresis for MINOR and MAJOR levels are configurable by the
service provider.
• Selective defense actions are provided that are based on board and instance overload
conditions. For example, if one CEM board is overloaded, the other CEMs can still
admit new calls.
• Ratios of discarded messages for MINOR and MAJOR overload levels are
configurable by the service provider.
• As soon as Minor overload is detected, preemption is no longer allowed for normal
calls (non-emergency calls). Preemption continues to be possible for emergency calls,
but only in levels Minor and Major. In level Critical, preemption is no longer allowed
for any kind of call, emergency and non-emergency. This is all done automatically by
the software
About panic overload
Panic overload is detected when internal eNodeB message queues reach saturation. Once
panic overload is detected, messages that are marked internally as low priority can be
discarded, for example Pagings or RRC Connection Requests.
Operational aspects of feature L115241 include the following:
• For Configuration Management (CM)
– Parameters to set the overload level at which the following functions are inhibited:
ANR, PCMD, Call Trace, Debug Trace, and Dynamic Debug Trace
– Parameters for the thresholds and hysteresis of Minor and Major overload levels
– Parameters for the ratios of rejected procedures in Minor and Major overload
• For Fault Management (FM)
– Events for overload threshold crossing
• For Performance Measurement (PM)
– Counters for CPU and Memory consumption
– Counters for rejected procedures
• For WPS
– Checks to ensure consistency of configured thresholds
The Overload Control function does not adversely impact the eNodeB capacity.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Note that this a bCEM-only feature since Overload Control Evolution has been supported
on the eCEM since LA4.
Feature benefits
eNodeB overload occurs when the usage of any resource within the eNodeB is beyond the
engineering limit. The overload control mechanisms provided in this feature adapt the
behavior of the eNodeB when the eNodeB is facing an overload condition so as to limit
the severity of the overload condition and avoid any resource starvation.
The main objective of this feature is to avoid performance degradation and outages when
the eNodeB is facing traffic exceeding its processing capacity.
Impacted systems
OAM, eNodeB
Feature type
Base
Dependencies
Features
97930 eNB Overload Control (LA3.0)
Hardware
None
Software
None
Interworking
None
Devices
None
None.
Engineering Impacts
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
None.
Feature type
Base
L115651 - Overload Control Improvements

FID L115651 - Overload Control Improvements
Feature Description
This feature adds improvements to the Overload function introduced in LA3.0 by feature
L97930 Overload Control, including introduction of new Processor Occupancy counters.
Note: Note that this a bCEM-only feature since Overload Control Improvements have
been supported on the eCEM since LA5.
Operational Aspects
Operational aspects of the feature include the following;
• CM
– Parameters to set the overload level at which the following functions are inhibited:
ANR, PCMD, Call Trace, Debug Trace, Dynamic Debug Trace.
– Parameters for the thresholds and hysteresis of Minor and Major overload levels.
– Parameters for the ratios of rejected procedures in Minor and Major overload.
• FM - Events for overload threshold crossing.
• PM
– Counters for CPU (histogram) and Memory (peak and average) consumption.
– Counters for rejected procedures.
– Counter for number of overload period, total overload time.
• WPS - Checks to ensure consistency of configured thresholds
Feature Benefits
eNodeB overload occurs when the usage of any resource within the eNodeB is beyond the
engineering limit. The overload control mechanisms provided in this feature adapt the
behavior of the eNodeB when the eNodeB is facing an overload condition so as to limit
the severity of the overload condition and avoid any resource starvation.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115651 - Overload Control Improvements
....................................................................................................................................................................................................................................
The main objective of this feature is to avoid performance degradation and outages when
the eNodeB is facing traffic exceeding its processing capacity.
Impacted Systems
OAM and eNodeB
Dependencies
Features
L115241 - Overload Control Evolutions
Hardware
None.
Software
None.
Interworking
None.
Devices
None.
Standards
None.
Restrictions/ Limitations
None.
Engineering Impacts
None.
None.
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Overview
Purpose
This section lists customer-viewable features that were developed in the LR Transport and
Security program for this release.
Contents
L112791 - Transport counters 2-35
L112791 - Transport counters

L112791 - Transport counters
Feature Description
This feature provides the following new capabilities in the eNodeB:
• The eNodeB supports new counters to track the number of packets in and out per
types of traffic, for instance, S1u, S1c, X2u and X2c.
• The eNodeB supports new counters per VLAN.
Feature Benefits
This feature provides more visibility into traffic volume and traffic mix. This information
allows network utilization to be assessed. This in turn offers measures for assessing
network growth requirements.
Impacted Systems
OAM, eNodeB Platform
Dependencies
Features
None.
Hardware
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L112791 - Transport counters
....................................................................................................................................................................................................................................
Software
None.
Interworking
None.
Devices
None.
Standards
None.
None.
Engineering Impacts
None.
New counters are introduced with this feature.
Feature Type
Base
Feature activation flag: Yes
Activated by default: Yes
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Overview
Purpose
This section lists customer-viewable features that were developed in the LTE Digital
Evolution, Capacity and Performance program for this release.
Contents
159512 - LA6 bCEM Paging capacity increase 2-37

160636 - Non-GBR prioritization 2-39
160815 - Optimized Segmentation (MCS Override) 2-41
163993 - eNodeB SW capacity for LA5.03 2-44
164117 – bCEM implementation of 163549 - Speed-up throughput recovery 2-47
after smartphone specific behavior
166046 - PUSCH improvements 2-49
L92639 - FDD RACH burst format 2 2-50
L105587 - bCEM commercial introduction 2-52
L114492 - Generalized OP-PUCCH 2-53
L115776 - eNodeB SW capacity 2-55
L115938 - Dual-carrier support on one band 2-57
159512 - LA6 bCEM Paging capacity increase

159512 - LA6 bCEM Paging capacity increase
Feature Description
This feature increases by up to 500 messages per second the paging capacity of the
eNodeB.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 159512 - LA6 bCEM Paging capacity increase
....................................................................................................................................................................................................................................
Feature Benefits
This feature significantly improves the eNodeB paging capacity. Before this feature, the
eNodeB could only place a single page record in a page message, hence limiting the
eNodeB page capacity to 100 user pages per second. With this feature, the service
provider can handle much higher paging traffic demand brought by ever-increasing traffic
demand. This feature also helps the service provider to avoid dropped pages due to
limited eNodeB paging capacity, which not only impacts the user paging performance,
but also forces the EPS to retry the page, and is often propagated to much wider areas,
thus generating even more paging traffic in the network.
Impacted Systems
This feature is implemented in the PCCH scheduler module on the bCEM.
Dependencies
Features
None.
Hardware
This feature applies to the bCEM only.
Software
None.
Interworking
None.
Devices
None.
Standards
Relevant standard: TS36.331
This feature applies to the bCEM only.
Engineering Impacts
This feature improves the PCCH capacity from 100 pages per second to 600 pages per
second. Under random paging traffic arrivals with random IMSI assignments, the
engineering capacity on the PCCH is about 70-80% of the PCCH capacity.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 159512 - LA6 bCEM Paging capacity increase
....................................................................................................................................................................................................................................
To fully make use of the improved paging capacity, the configuration parameters need to
be set.
Once the value P is determined, the configuration parameter numberRBNotForPaging
should be set such that: numberRBNotForPaging ≤ TotalPRB –
RGBSize*roundup(P/RGBSize).
Table 2-1 Total PRB and RBG size for Different Carrier Configurations
Carrier 1.4MHz 3MHz 5MHz 10MHzH 15MHz 20Mz

BW
TotalPRB 6 15 25 50 75 100
RBGSize 1 2 2 3 4 4
Feature Type
Base
160636 - Non-GBR prioritization

160636 - Non-GBR prioritization
Global
Feature Description
This feature supports weighted proportional fair scheduling based on the QoS Class Index
(QCI) associated with the nonGBR bearer for both the downlink (DL) and uplink (UL)
directions. The scheduling weight is customer configurable per QCI, and is used to
determine the resource fairness among differing QCI traffic.
For example, let’s assume that the scheduling weight for QCI9 is set to be 1, and the
scheduler weight for QCI8 is set to be 2. Then under the condition that data demand is
sufficient, a QCI8 traffic would be allocated with double the RF resources compared with
the resources for QCI9 traffic. If the RF condition is the same, this leads to approximately
double the throughput for the QCI8 traffic compared with the QCI9 traffic.
Note: The primary objective of this feature is to provide nonGBR QoS differentiation.
As a safeguard, the feature offers per-QCI weight for GBR service as well as
preventing GBR performance from being impacted by nonGBR differentiation. By
this means the feature also allows further differentiation between GBR and nonGBR
service, or differentiation between different GBR classes.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 160636 - Non-GBR prioritization
....................................................................................................................................................................................................................................
For the eCEM, the range is restricted to {1/2, 16} but the bCEM has the full range.
12040 is only available on the bCEM.
Feature Benefits
Before this feature was available, the downlink offered a fixed nonGBR QoS
differentiation in LA4 via L92095 (PDB based QoS enforcement for nonGBR) as a
temporary solution. When the PDB feature is enabled, a fixed per-QCI weight based on
QCI priority is applied to each QCI to help differentiate the traffic performance. Between
adjacent QCI priorities, a resource ratio of about 3:1 is provided.
This feature, feature 160636, removes the fixed QCI priority differentiation brought about
by L92095. Feature 160636 enables customers to provide differentiated service to general
data traffic with configurable resource sharing strategy. For example, a tiered service plan
can be created and different levels of service can be offered to different subscribers. The
data traffic can be classified into different QCIs based on the service tier, which can then
be assigned with different scheduling weights in the eNodeB and obtain differentiated
performance.
Impacted Systems
Modem, CallP, SAM, WPS, NPO
Dependencies
Features
None.
Hardware
This feature applies to both eCEM and bCEM equipped eNodeBs.
Software
None.
Interworking
None.
Devices
None.
Standards
None.
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 160636 - Non-GBR prioritization
....................................................................................................................................................................................................................................
Engineering Impacts
Feature 160636 provides relative resource allocation differentiation among differing
traffic classes. Feature 160636 should not impact the RF capacity or the eNodeB user
capacity.
When feature 160636 is enabled (as indicated under “Feature Type,” below), the
following two configuration parameters can be configured for each traffic radio bearer
type:
• TrafficRadioBearerConf::ulQCISchedulingWeight
• TrafficRadioBearerConf::dlQCISchedulingWeight
Both parameters have a selection range of {1/8, ¼, ½, 1, 2, …, 128}.
Feature 160636 also offers several PM counters to assist in traffic performance
monitoring:
• 12039: VS.DLPRBUsedPerTypeService: screening per QCI5/6/7/8/9.
• 12040: VS.ULPRBUsedPerTypeService: screening per QCI5/6/7/8/9.
• 12105: VS.DLRlcPduKbytes: screening per QCI5/6/7/8/9
• 12106: VS.ULRlcPduKbytes: screening per QCI5/6/7/8/9
Feature Type
Optional.
Feature activation flag: isQciWeightEnabled.
Activated by default? No.
160815 - Optimized Segmentation (MCS Override)

160815 - Optimized Segmentation (MCS Override)
Global Market
Need for this feature

Uplink (UL) Voice over LTE (VoLTE) coverage is limited by the fragmentation of speech
frames and the associated sudden growth in delay/jitter as the UE moves towards the cell
edge.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 160815 - Optimized Segmentation (MCS Override)
....................................................................................................................................................................................................................................
As a VoLTE UE moves towards the cell edge, the UE Tx power limitations result in
smaller UL grants being issued by the UL Scheduler. A VoIP packet is segmented by the
DS scheduler into many separate MAC SDUs (for example, 8). This results in delay
buildup, which grows suddenly when new frames arrive before the previous frames are
completely transmitted.
Feature Description
This feature provides two enhancements to solve this problem:
• Modulation and Coding Scheme (MCS) Override
• Physical Resource Block (PRB) Override
Figure 2-5 Optimized segmentation
Note: This feature is for the eCEM only.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
MCS Override
MCS Override aims at reducing the number of segments.
A minimum Transport Block Size is enforced such that a VoIP packet is split into no more
than 4-5 segments over the air interface. Delay build-up due to segmentation is prevented.
The growth of delay with increasing path loss is gradual and coverage is extended.
PRB Override
PRB Override complements MCS Override.
PRB Override enforces a minimum number of PRBs (for example, 2). Enforcing a
minimum number of PRBs results in improved coding gain of the individual segments
which improves coverage.
Feature Benefits
Optimized Segmentation significantly increases VoLTE uplink path transmissions.
Impacted Systems
None.
Dependencies
None.
The design of this feature assumes that the VoLTE codec is a 12.65kbps AMR codec and
that RoHC is enabled. Optimal Segmentation for other codec rates requires additional
logic which needs to be introduced by another feature.
Engineering Impacts
MCS override yields a typical 2-3dB improvement in terms of maximum acceptable
uplink path loss (MAPL) for an AMR 12.65kbps codec managed with uplink dynamic
grants.
PRB override can bring in an additional 1dB gain, yielding an overall of 3-4dB gain for
the feature.
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Feature Type
Optional
Feature activation flag: bit #23of EnB.spare9 = 0
Activated by default but not until feature has been approved by the customer for default
activation
163993 - eNodeB SW capacity for LA5.03

163993 - eNodeB SW capacity for LA5.03
Global Market
Note: This feature title was created before the releases were renamed. Contents of this
feature apply to LA6.0.
Feature Description
This feature provides the eNodeB SW capacity for different carrier BWs and different
modem types, as listed in the following tables.
User capacity
Table 2-2 User capacity for eNodeB equipped with eCEM in LA6.0
eNodeB equipped with eCEM Max # of Active Users

Timeline Bandwith Per cell Per eNodeB
(3 cells / eNodeB)
LA5.0 20 MHz 54 162

and on 10 Mhz 200 600
5 MHz 167 501
3 MHz 100 300
1.4 MHz 48 144
Table 2-3 User capacity for eNodeB equipped with bCEM in LA6.0
eNodeB equipped with Max # of Active Users

bCEM
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 163993 - eNodeB SW capacity for LA5.03
....................................................................................................................................................................................................................................
Table 2-3 User capacity for eNodeB equipped with bCEM in LA6.0 (continued)

(3 cells / eNodeB)
LA6.0 20 MHz 167 (in CL2) 501
54 (in CL1)
10 Mhz 250 750
5 Mhz 200 600
Note: For dual band configurations, each bCEM can manage the capacity described in
this table. However, the global capacity of the eNodeB is limited to 750 according to
the current Alcatel-Lucent call profile.
Bearer capacity
Table 2-4 Bearer capacity for eNodeB equipped with eCEM in LA6.0
eNodeB equipped with eCEM Max # of Data Radio Bearers of which Max #VoLTE
Bearers
Timeline Bandwith Per cell Per eNodeB Per cell Per eNodeB
(3 cells / (3 cells /
eNodeB) eNodeB)
LA5.0 20 MHz 176 528 40 120
and on 10 Mhz 650 1950 100 300
5 MHz 543 1629 100 300
3 MHz 325 975
1.4 MHz 156 468
Table 2-5 Bearer capacity for eNodeB equipped with bCEM in LA6.0
eNodeB equipped with bCEM Max nb of Data Radio of which Max #VoLTE
Bearers Bearers
LA6.0 20 MHz 543 1629 100 300
10 Mhz 813 2439 100 300
5 MHz 650 1950 100 300
Feature Benefits
The feature specifies the eNodeB capacity growth roadmap.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Impacted Systems
Radio Admission Control: on per-cell level, radio admission control needs be able to
accommodate more calls/bearers based on the capacity targets.
RF Schedulers: On per-cell level, RF scheduler is able to support traffic from more
calls/bearers.
Capacity License: Higher eNodeB user license can be supported.
Dependencies
Features
None.
Hardware
This feature provides separate capacity targets for eCEM and bCEM equipped eNodeBs.
Software
None.
Interworking
None.
Devices
None.
Standards
None.
Information not available at this time.
Engineering Impacts
This feature allows higher users/bearers to be supported by the eNodeB and each cell. The
increased capacity needs to be considered in engineering efforts.
The new capacity targets are configured via the parameters listed in the following table.
Note that 5MHz has the same capacity as 20MHz, as shown in the previous table.
Table 2-6 Parameters for configuring capacity
Object Name Parameter identity

RadioCacCell maxNbOfDataBearersPerCell
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Table 2-6 Parameters for configuring capacity (continued)
Object Name Parameter identity

RadioCacCell maxNbrOfDataBearersPerQciGroup
RadioCacCell maxNbrOfUsers
RadioCacCell maxNbrOfVoip
RadioCacCell maxNbrOfVoipBearersForNonSpsCapableUe
RadioCacEnb maxNbOfDataBearersPereNodeB
RadioCacEnb maxNumberOfCallPereNodeB
Feature Type
Base
164117 – bCEM implementation of 163549 - Speed-up

throughput recovery after smartphone specific behavior
164117 - bCEM implementation of 163549 - Speed-up throughput recovery after smartphone
specific behavior
Global Market
Feature Description
This feature provides for the bCEM several fixes.
The fixes include Channel Quality Indicator (CQI) erasure handling, DTX management,
and several others.
What is CQI erasure handling?

CQI erasure handling is the process used to manage the case where the CQI is not
decoded by the eNodeB.
What is DTX?
DTX is the status set by the eNodeB when the response sent by the UE about the data
previously transmitted by the eNodeB is not identified properly.
Feature Benefits
Those fixes increase the reactivity of the eNodeB when the radio conditions for a given
UE change suddenly.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 164117 – bCEM implementation of 163549 - Speed-up
LTE Digital Evolution, Capacity and Performance throughput recovery after smartphone specific behavior
....................................................................................................................................................................................................................................
Impacted Systems
eNodeB only
Dependencies
Channel Quality Indicator (CQI) erasure handling — Before this feature, the eNodeB is
very conservative when handling CQI erasures because the eNodeB assumes that CQI
erasure handling is a very rare event. Whenever the eNodeB detects a CQI erasure, the
eNodeB applies very conservative Signal to Interference Noise Ratio (SINR) values to be
used for DL scheduling. . If two consecutive CQI erasures are detected, the downlink
(DL) scheduler will use only MCS1, leading to very low DL throughput. However, with
some smartphone-specific behavior, the smartphone may stop transmitting CQI in a
certain time window, causing CQI erasures in normal call scenarios. To avoid this
unnecessary DL performance degradation, this feature implements gradual decay of the
DL SINR when CQI erasures are detected, which improves DL performance.
ACK/NAK DTX management enhancement — Similarly, the eNodeB typically assumes
that Acknowledgement/Negative Acknowledgment (ACK/NAK) performance is reliable.
Hence any Discontinuous Transmission (DTX) detection is treated as NAK and causes
the DL Block Error Rate (BLER) control to react by lowering the MCS. With certain
smartphone-specific behavior, the UE may not listen to PDCCH grants in a certain time
window, causing ACK/NAK DTX. To avoid impacting the MCS assignment, this feature
allows the eNodeB to differentiate NAK and DTX. With this feature, DTX is no longer
considered as an input to BLER control. This way, the DL performance impact due to the
smartphone behavior is diminished.
None.
Engineering Impacts
None.
None.
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 166046 - PUSCH improvements
....................................................................................................................................................................................................................................
166046 - PUSCH improvements

166046 - PUSCH improvements
Global Market
Feature Description
Provides enhancements to Uplink Grant Stretching and IoT control.
Need for Grant Stretching

Typically the UL scheduler assigns a grant that does not exceed the PUSCH power
headroom limit. This maximizes the per-PRB spectrum efficiency. For example, if PHR
for 1PRB transmission is 6dB then the PUSCH grant will not be larger than 4 PRBs.
However, if there are some spare PUSCH PRB resources after all UEs have been served
in the current TTI, it makes sense to check if the served users’ throughput can be
increased by increasing the number of PRBs assigned to the UE beyond the power
headroom limitation. This reduces the spectral efficiency as the SINR per PRB goes
down, but can improve the edge user data rate.
What is PUSCH grant stretching?

With PUSCH grant stretching the grant size is increased for Nprb_initial to Nprb_new if
all the conditions are verified:
• The predicted per-PRB PUSCH SINR > SINR threshold value (e.g. -5dB)
• The predicted payload size is higher after grant extension than before:
SE(PUSCH_SINR(new)) * Nprb_new ≥ SE(PUSCH_SINR(initial)) * Nprb_initial
What is the enhancement to grant stretching in this release?

In this enhancement, the search order of the loop for grand scheduling is reversed. Instead
of the previous method, which provided incremental increases of the grant size until no
throughput gain is achieved, the new method tries the largest available grant increase and
consider iteratively the next smaller size until throughput gain is achieved. The enhanced
method is better because grant stretching does not achieve its maximum performance gain
in interfered and/or highly selective channel scenarios due to the fact that the grant
increase search stops at the first increase that does not yield an incremental throughput
gain.
What is the enhancement to IOT control in this release?

In this release, each eNodeB controls its own UL SINR target level based on its own
observed IoT condition. This avoids the excessively high IoT caused by a power-control
race between the eNodeB and neighboring eNodeBs.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 166046 - PUSCH improvements
....................................................................................................................................................................................................................................
Feature Benefits
Provides enhanced grant stretching, which makes better use of PRB resources. Also
provides high UL IoT control via dynamic SINR adaptation, which prevents excessive
battery drain on UEs in cases where high IoT occurs in the network.
Impacted Systems
eNodeB (modem)
Dependencies
None.
None.
Engineering Impacts
None.
None.
Feature Type
Base
L92639 - FDD RACH burst format 2

L92639 - FDD RACH burst format 2

FDD RACH burst format 2
OI number
3BK36392ALAA
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L92639 - FDD RACH burst format 2
....................................................................................................................................................................................................................................
Feature Description
This feature adds support for the Random Access Channel (RACH) preamble format-2,
which enables support of propagation delay based on a 29.5km cell radius. There is no
requirement to optimize VoIP performance for this configuration.
Feature benefits
The primary purpose of this feature is to support a large cell radius.
This feature also supports the deployment scenario of a small cell where the fiber delay
between the antenna and the radio is too large to be compensated by feature L100622.0.
Impacted systems
Modem, CallP, OAM. SAM and WPS
Dependencies
None.
This feature is supported only on the bCEM.
This feature is for FDD only.
Engineering impacts
None.
Operational requirements
N/A
Feature type
Optional (that is, requires cell-level license for activation)
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L105587 - bCEM commercial introduction
....................................................................................................................................................................................................................................
L105587 - bCEM commercial introduction

L105587 - bCEM commercial introduction
Global Market
Feature Description
This feature introduces the bCEM in LTE-FDD. The bCEM has the capability to be
configured for all 3 cells on the eNodeB and can support 6 cells with the dual band.
Note: The bCEM manages 1 carrier with 3 cells. The Digital 2 Unit (D2U) can
contain up to 3 bCEM and thus can manage up to 3 carriers and 9 cells (in this
release, the limitation is 2 carriers and 6 cells).
Feature Benefits
The bCEM modem has the ability to be configured for all 3 cells on the eNodeB. This
capability prepares the bCEM for evolution to multi-band.
Impacted Systems
OAM, Modem, NEM, WPS and SAM
Dependencies
The only dependency for the bCEM is to have LA5.0 eNodeB generic software installed.
Note: The eNodeB will have a dependency on V5 RUC when the V5 RUC is a
supported configuration.
None
Engineering Impacts
There are no engineering impacts other than having only one modem instead of 3.
eNodeB with LA5.0 generic software installed.
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L114492 - Generalized OP-PUCCH
....................................................................................................................................................................................................................................
L114492 - Generalized OP-PUCCH

L114492 - Generalized OP-PUCCH
NAR Market

Generalized OP-PUCCH
OI number
3BK36394REAA
Feature Description
This feature supports Narrowband-Sounding Reference Signal (SRS) of 16 Physical
Resource Blocks (PRBs) in the OP-PUCCH configuration for BC13 (10 MHz) such that
A-MPR is not applicable to SRS if NS_07 is enabled (TS 36.101). Note that Additional
Maximum Power Reduction (A-MPR) will still be applicable to PUSCH if NS_07 is
enabled.
NS_07+OP_PUCCH configurations may need to be enabled if the LTE UE
Out-Of-Band-Emissions (OOBE) into the Narrowband Public Safety (PS) spectrum
exceeds certain thresholds.
The potential scenario is that of an LTE UE’s UL transmission causing interference to the
downlink of a nearby PS device (for example, a walkie-talkie).
To reduce the OOBE, 3GPP supports an NS_07 configuration, that specifies a reduction
in UE transmit power as a function of the location and size of the PRBs.
The OP-PUCCH configuration allows the PUCCH region to be configured closer to the
center of the band to avoid being impacted by NS_07 UE transmit power reduction.
Feature benefits
Currently, LTE supports a Wideband-SRS signal. However, the Wideband SRS signal is
susceptible to transmit power reduction and hence reduced coverage, in cases where
NS_07 needs to be enabled. This feature's Narrowband SRS configuration has been
introduced to avoid the power reduction necessary with NS_07.
Impacted systems
OAM and eNodeB
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L114492 - Generalized OP-PUCCH
....................................................................................................................................................................................................................................
Dependencies
Features
None.
Hardware
None.
Software
None.
Interworking
None.
Devices
One of the sub-features needs UE support for narrowband SRS transmission as per
TS36.211 table 5.5.3.2-2.
Standards
TS36.211 and TS36.101.
Only Band 13, 10 MHz is supported.
This feature is only planned for the bCEM modem and is targeted for the FDD mode of
operation.
Engineering impacts
None.
Operational requirements
None.
Feature type
Optional, licensed.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115776 - eNodeB SW capacity
....................................................................................................................................................................................................................................
L115776 - eNodeB SW capacity

L115776 - eNodeB SW capacity
Global Market
Feature Description
This feature provides the eNodeB software capacity for the eCEM for different carrier
BWs and different modem types, as listed in the following tables.
Note: bCEM capacity in LA6.0 is represented by feature 163993, eNodeB SW
capacity for LA5.03.
User capacity
The following table shows user capacity for the eCEM for LA6.0.
Table 2-7 User capacity for an eNodeB equipped with eCEM in LA6.0
eNodeB equipped with eCEM Max # of Active Users

(3 cells / eNodeB)
LA5.0 20 MHz 54 162
and on 10 Mhz 200 600
5 MHz 167 501
3 MHz 100 300
Bearer capacity
The following table shows bearer capacity for the eCEM for LA6.0.
Table 2-8 Bearer capacity for an eNodeB equipped with eCEM in LA6.0
eNodeB equipped with eCEM Max # of Data Radio Bearers of which Max #VoLTE
Bearers
Timeline Bandwith Per cell Per eNodeB Per cell Per eNodeB
(3 cells / (3 cells /
eNodeB) eNodeB)
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115776 - eNodeB SW capacity
....................................................................................................................................................................................................................................
Table 2-8 Bearer capacity for an eNodeB equipped with eCEM in LA6.0
(continued)
LA5.0 20 MHz 176 528 40 120

and on 10 Mhz 650 1950 100 300
5 MHz 543 1629 100 300
3 MHz 325 975
1.4 MHz 156 468
Feature Benefits
The feature specifies the eNodeB capacity growth roadmap.
Impacted Systems
• Radio Admission Control: - On a per-cell level, radio admission control needs be able
to accommodate more calls/bearers based on the capacity targets.
• RF Schedulers: On a per-cell level, the RF scheduler is able to support traffic from
more calls/bearers.
• Capacity License: A higher eNodeB user license can be supported.
Dependencies
None.
None
Engineering Impacts
This feature allows more users/bearers to be supported by the eNodeB and each cell. The
increased capacity needs to be considered in engineering efforts.
Parameters for configuring the new capacity targets are listed in the feature description
for feature 163993 - eNodeB SW capacity for LA5.03.
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115938 - Dual-carrier support on one band
....................................................................................................................................................................................................................................
L115938 - Dual-carrier support on one band

L115938 - Dual-carrier support on one band
NAR Market
OI number
3BK36394IHAA

Dual-carrier in dual-band spectrum
Feature Description
This feature provides support for two carriers (5 MHz+ 5 MHz) on a single PCS band
(1900 MHz).
Feature Benefits
This feature enables operators to co-locate different carriers on the same LTE band within
a single eNodeB, when spectrum available in one carrier is not sufficient.
By adding a second bCEM board, the large bandwidth of the RRHs/TRDUs can be used
to allow twice the performance of the former configuration.
For more complex band/carrier configurations the next step will be Carrier Aggregation.
Impacted Systems
None.
Dependencies
Features
The following feature dependency exists for this feature.
Feature Number Feature Title Nature of Dependency

L115616 Support for dual-band Extended number of
eNodeB with two modems configurations to dual-carrier
same band.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115938 - Dual-carrier support on one band
....................................................................................................................................................................................................................................
Hardware
The hardware dependencies are listed in the following requirements that define the
hardware configuration for this feature:
• The eCCM-U (3JR20073CB) is to be supported with two bCEMP1.1; Both -48VDC
and +24VDC configurations need to be supported.
• One fiber link per sector (two carriers) is used from the BBU to the RRH; in case of
FDD configuration, CPRI rate 3 is used (two carriers of 5 MHz).
• FDD configuration: the radio configuration is the following one: 2x2 MIMO, 4 Rx, 5
MHz.
Software
For this feature, the isDualCarrierEnabled licensing parameter must be TRUE.
Interworking
None.
Devices
None.
Standards
None.
The feature addresses only the presented configurations.
Engineering Impacts
None.
None.
Feature Type
Optional
....................................................................................................................................................................................................................................
Issue 1 April 2013
LTE RF
....................................................................................................................................................................................................................................
LTE RF
Overview
Purpose
This section lists customer-viewable features that were developed in the LTE RF program
for this release.
Contents
156783 - TMA/RET with AISG 2.0 Enhancements in LA/TLA6 (former 2-59

L115277)
159276 - Support for RRH2x60-850 (LTE Only) 2-62
L106226 - RDEM HW 2-65
L115158 - LTE RRH Antenna Cross Connect Capability Support in LA4.0.1 2-66
L115268 - PCS Band 2 RRH2x60 HW Requirements 2-71
L115269 - Advanced Technology CR RRH2x40-07L - HW Requirements 2-72
L115270 - Band 12/17 2x60-7L (Lower 700MHz) TRDU - HW Requirements 2-74
L115512 - LTE HW Requirements for RRH4x40-19 (PCS) 65MHz 2-76
L115616 - Support for dual-band eNodeB with two modems 2-77
L115629 - Support for RRH2x60-19 (LTE Only) 2-79
156783 - TMA/RET with AISG 2.0 Enhancements in LA/TLA6

(former L115277)
156783 - TMA/RET with AISG 2.0 Enhancements in LA/TLA6 (formerly L115277)
Global Market
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 156783 - TMA/RET with AISG 2.0 Enhancements in LA/TLA6
LTE RF (former L115277)
....................................................................................................................................................................................................................................
Feature Description
This feature introduces enhanced capabilities to the Antenna Interface Standards Group
(AISG) 2.0 feature supported by the LTE eNodeB since LA3.0. The following upgrades
will be supported with this feature in LA6.0):
• The number of Remote Electrical Tilts (RETs) that can be supported in the RET (or
m-RET) increases to a maximum of 9 RETs per Radio Frequency Module (RFM).
(The limit of 20 RETs maximum per eNodeB is kept unchanged.)
• New Remote Radio Head (RRH) for the 700MHz band with AISG capability on
Tx/Rx Port 1 and Port 2 in addition to RS-485 port.
• The user can write to the user defined data area of a Remote Electrical Tilt/Tower
Mounted Amplifier (RET/TMA).
• The following parameters can be written to the appropriate fields in the RET/TMA
user defined data:
– Installed Mechanical tilt.
• Support for 4 new alarms on the RFM Object and 4 alarms for RET Subunit 3 and
RET Subunit 4.
• Support of LTE multi-band TMA.
This feature covers completion of AISG 2.0 support at the eNodeB level, including the
following:
• Support of Dual-band TMA managed by a multi-band eNodeB.
• Support of some additional fields for RET and TMA, such as Sector Id, eNodeB
Name and band Class.
• Support of up to 9 RET (or m-RET) in a daisy chain per RFM. The maximum limit of
20 RET or m-RET per eNodeB is kept unchanged.
• The number of TMA that can be in a daisy chain was increased to 6 in the software,
but the actual number of TMAs that can be in a daisy chain would be limited by the
maximum DC current that is supplied by the RRH/TRDU on the AISG bus.
• The recommended configuration for TMA is one on each RRH/TRDU RF port
(Single TMA) or one Dual TMA on one of the RF ports of the RRH/TRDU.
What is an RET?
An RET is a device that can change the tilt of an eNodeB antenna.
What are TMAs?

TMAs are low noise amplifiers that are mounted in the antenna to amplify the Rx signals.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
What is an RFM?
An RFM (Radio Frequency Module) is the generic name that represents the Radio
Transceiver unit in the eNodeB. An RFM can represent a RRH (Remote Radio Head) or a
Transmit Receive Duplexer Unit (TRDU) transceiver.
Feature Benefits
This feature expands the capabilities introduced with FRS-114909.3 in LA5.0 by the
introduction of additional functionalities and capacity that have been requested by our
customer. The following new capacities are expanded:
• Increase in number of RET/TMAs per RRH/TRDU to 9 in the software. The actual
number of TMAs that can be supported in a daisy chain per RRH/TRDU is limited by
the maximum current that can be drawn from the internal Bias in the RRH/TRDU.
• New 700MHz RRH with support for AISG on 3 Ports
• Support for Dual Band TMAs
• Support of AISG units in the dual band BBU configuration
• Capability of writing data to some of the parameters in the User Defined Data Record
of the RET and/or Subunit.
Impacted Systems
OAM, Platform, NEM
Dependencies
Features
FRS-114909.3
Hardware
This feature adds a new 700L RRH.
Software
This feature depends on new eNodeB OAM software.
Interworking
This feature can only be supported on RET and TMAs that have been approved to be used
with the Alcatel-Lucent eNodeBs.
Devices
This feature depends on RETs and TMAs that have been approved by the IOT lab.
Standards
This feature depends on the AISG 2.0 standard.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
This feature is only supported on RET/TMA devices that have been approved by the IOT
lab.
This feature will not support writing data to the TMA and/or TMA Subunit.
The actual number of TMAs that can be in the daisy chain is limited by the DC source in
the RRH/TRDU.
Engineering Impacts
None.
The feature is supported only from the NEM and/or a Remote NEM.
Feature Type
Base
Note: This feature depends on the predecessor feature FRS-114909.3, which is an
optional feature that requires a license fee.
159276 - Support for RRH2x60-850 (LTE Only)

159276 - Support for RRH2x60-850 (LTE Only)
NAR Market
Feature Description
This feature provides Remote Radio Head (RRH) hardware for Band 5 in support of
RRH2x60-850 (for LTE Only).
The RRH2x60w-850 supports 5MHz Bandwidth LTE carriers for LA6.0 RRH2x60w-850
in LTE mode only and meets the following requirements:
• The RRH2x60w-850 unit supports dual duplex antenna configurations.
• The RRH2x60w-850 supports two slave CPRI connections, where one CPRI
connection (a slave port) is connected to the LTE Baseband Unit (BBU). Note that the
BBU is the Common Public Radio Interface (CPRI) link master.
• The RRH2x60w-850 supports a maximum CPRI link length between the BBU and
RRH of at least 15 km. This is based on fiber delay support and RACH 2 delay
compensation.
• The RRH2x60w-850 supports LTE maintenance operations.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 159276 - Support for RRH2x60-850 (LTE Only)
LTE RF
....................................................................................................................................................................................................................................
• The RRH2x60w-850 reports faults to the LTE BBU and OAM software interfaces.
• Software management of the RRH2x60w-850 is provided via the LTE BBU and LTE
interface OAM software.
• The RRH2x60w-850 supports AISG 2.0 TMAs and RETs.
• The system supports managing and fault reporting for AISG V2.0 TMAs, RETs, and
ALDs on the LTE-only OAM system.
• The RRH2x60w-850 supports up to two simultaneous AISG V2.0 ports, one external
AISG port, and the internal smart bias Tee modem coupled to the RRH antenna port.
• The RRH2x60w-850 and LTE SW for the LTE BBU supports 2x2 MIMO Downlink
Transmission.
• The system supports eNodeB Commissioning of the RRH or TRDU via the LTE
NEM and SAM, including supporting configuration of carriers and RF monitoring.
The system for the RRH2x60w-850 supports six external user-defined alarm inputs.
Note: For further information, see Alcatel-Lucent Remote Radio Head 2x60W - 850,
1900 MHz Site Preparation, NN-20500-305.
Feature Benefits
The RRH2x60 allows the customer to support LTE cells in bandclass 5 (RRH2x60-85).
Impacted Systems
None.
Dependencies
Features
See also the following table.
Table 2-9 Predecessor features and capabilities used by the RRH2x60

configurations
Feature Feature Title Nature of Dependency

Number
L115615 Dual carrier Also provides support for dual carrier, but on a single modem
(128420) support on (LR13.0)
one modem
L84815.0 Single Implemented in LA5.0, provides support for single transmit cell
(128698) antenna (1T2R)
transmit
scheme
(bCEM
parity)
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features 159276 - Support for RRH2x60-850 (LTE Only)
LTE RF
....................................................................................................................................................................................................................................
Table 2-9 Predecessor features and capabilities used by the RRH2x60
configurations (continued)
L115401 Support for Allows operation of up to six RRH2x60 units per eNodeB.
six sectors in (LR13.0). Since this feature is in the future, 6-sector
one BBU configurations are not supported with the LA6.0 features in this
document.
Hardware
None.
Software
None.
Interworking
None.
Devices
None.
Standards
None.
None.
Engineering Impacts
None.
None.
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L106226 - RDEM HW
LTE RF
....................................................................................................................................................................................................................................
L106226 - RDEM HW
L106226 - RDEM HW
Global Market, USA Market
Feature Description
This feature adds two additional RX paths by means of simplex filtering and gain
(Receive Diversity Expansion Module [RDEM]) for converting a version of the
RRH2x40 into a four-branch uplink diversity reception-capable unit.
Feature Benefits
This feature provides the following benefits:
• An increased uplink cell range to allow larger cell sizes or overlay onto low frequency
cell sizes
• Fewer cells for a given area of coverage
• Better uplink performance
Impacted Systems
Dependencies
Features
This feature requires LTE features for BBU Modem 4-branch reception.
Hardware
None.
Software
None.
Interworking
None.
Devices
None.
Standards
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L106226 - RDEM HW
LTE RF
....................................................................................................................................................................................................................................
Engineering Impacts
Feature Type
Base
L115158 - LTE RRH Antenna Cross Connect Capability Support

in LA4.0.1
L115158 - LTE RRH Antenna Cross Connect Capability Support in LA4.0.1
Note: Although the title of this feature mentions LA4.0.1, this feature becomes
available in LA6.0.1.
Feature Description
This feature provides enhancement to the capabilities introduced by FRS-92812. With the
implementation of FRS-115158, the eNodeB supports the following capabilities:
1. The RRH will support fault isolation to each of the two transceiver paths.
a. Critical faults on one of the transceiver paths do not impact the other path.
b. Path delay measurements have an accuracy of ± 25 nSec.
2. The eNodeB OAM handles the RRH isolated failure of each of the RRH transceiver
paths to determine the affected ltecell. If the critical fault is in the RRH transceiver
paths that support the control channels of an ltecell, the ltecell control channels are
dynamically moved to the other RRH that supports the second RF path of the ltecell.
3. The ltecell object supports an availability status equal to "degraded" when one of the
ltecell paths has failed.
4. The 5620 SAM displays the RRH isolated transceiver alarms.
5. The 5620 SAM displays the ltecell in degraded mode when there is a critical fault on
one of the RRH transceiver paths.
6. The following restrictions in LA3.0.2 are removed with FRS-115158:
a. The fibers and antenna cable length restriction are removed with the introduction
of full delay calibration and compensation for cross-connected configurations.
b. The requirement that a failed RRH has to be replaced with the same model from
the same vendor has been removed.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115158 - LTE RRH Antenna Cross Connect Capability
LTE RF Support in LA4.0.1
....................................................................................................................................................................................................................................
c. The previous limited fault management capabilities have been replaced with the
capability to switch between SISO and MIMO when there is failure and recovery
of an RRH fault.
d. The restriction that the downlink forward power must be set to the same value for
all the ltecells in the eNodeB has been removed.
e. The restriction that limited the X-Connect feature to eNodeBs with 3 sectors is
removed. This feature will also support eNodeBs with 2 sectors with antennas
cross-connected.
Feature Benefits
This feature provides the following benefits:
• The eNodeB availability time is improved.
• The eNodeB will continue to support traffic on all three sectors if there is a single
RRH failure.
• If the eNodeB only support two sectors, the eNodeB will continue support on the two
sectors in degraded mode if one of the RRH fails.
• The service provider is notified when ltecells are operating in degraded mode due to
an RRH failure.
Impacted Systems
eNodeB OAM
Most of the changes to the OAM-C code were introduced with FRS-92812. Additional
changes and modifications to the OAM-C code have been introduced.
The following fault management functions are new or modified by FID 115158:
✓ RRH faults are handled based on the specific RF paths that are affected by the critical
error. If the critical fault affects the whole RRH, then the recovery procedure includes
both of the ltecells supported on the RRH.
✓ The RRH critical fault is analyzed to determine if the fault impacts one or both of the
ltecells supported on the RRH.
✓ The ltecell MO supports an availability state equal to "degraded" if a critical fault on
an RRH impacted one or both of the ltecell RF paths.
✓ During the dynamic switch there is no need to turn off the transmitter of the RRH that
supports the diversity path of the affected ltecell. Zeros are placed on the CPRI data
packets associated with diversity path of the affected ltecell prior to replacing this data
with the control channel data of the ltecell. The same operation has been implemented
in reverse when the critical fault on the RRH recovers.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
✓ Additional configurations are supported. Both three sectors configuration and two
sectors configuration are supported. One sector configuration does not use the antenna
cross-connected feature.
MIM Impact
There is no impact to the MIM.
Dependencies
Features
• FID 1 - FRS-92812 Antenna Cross Connected Capabilities in LA3.0
• FID 2 - FRS-84815 Single Antenna Transmit Scheme (SIMO)
Hardware
The feature is intended to be used with Remote RF Heads. This feature was only tested
with RRHs for the 700L and certain proprietary bands.
Software
This feature depends on eNodeB Software version LA4.0.1 and SAM R9.5.
Interworking
None.
Devices
No impact to LTE Mobiles.
Standards
None.
The feature was only tested on RRHs that support the 700L and certain proprietary bands
using 5 Mhz and 10 Mhz carrier. The feature does not depend on the LTE carrier
bandwidth, but the feature was only tested on those carrier's bandwidths.
Engineering Impacts
Since this feature supports antenna cross-connected, there is a specific eNodeB
installation document that guides the customer on how to cross-connect the RRH output
ports to the antenna panels that support each of the sectors. The figures shown below
illustrate how the RRH's RF outputs must be routed to each of the antenna panels.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Figure 2-6 eNodeB with antenna cross-connected for three sectors
The next figure shows how an eNodeB that supports 2 sectors with the antenna
cross-connected must have the RRH's output ports routed to each antenna panel.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Figure 2-7 eNodeB with antenna cross-connected for two sectors
This feature requires the customer to purchase a license for each of the eNodeBs that are
configured to support the antenna cross-connected. If the customer does not purchase a
license for an eNodeB that has its antenna cross-connected, the eNodeB will fail the
initialization. The error message will notify the customer that a license is required for the
eNodeB with antenna cross-connected.
NEM supports for eNodeB with antenna Cross-Connected

In order to simplify the configuration of eNodeB with antenna cross-connected, the NEM
was updated to support a pre-configuration template that automatically configure the
eNodeB antenna ports to use the antenna cross-connected for 3 sectors or 2 sectors.
....................................................................................................................................................................................................................................
Issue 1 April 2013
....................................................................................................................................................................................................................................
Feature Type
Base
L115268 - PCS Band 2 RRH2x60 HW Requirements

L115268 - PCS Band 2 RRH2x60 HW Requirements
NAR Market
Feature Description
This feature provides new Remote Radio Head (RRH) hardware to support the North
American Region (NAR) PCS band. This feature includes the hardware requirements to
support both Long Term Evolution (LTE) and LTE/WCDMA.
Feature Benefits
This feature provides for the development of Remote Radio Head (RRH) software on top
of the WCDMA RRH 2x60 1900 hardware to support either WCDMA or LTE on the
same RRH hardware.
Impacted Systems
eNodeB Hardware
Dependencies
Features
None.
Hardware
None.
Software
None
Interworking
None
Devices
None
Standards
None.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115268 - PCS Band 2 RRH2x60 HW Requirements
LTE RF
....................................................................................................................................................................................................................................
N/A
Engineering Impacts
N/A
N/A
Feature Type
Base
L115269 - Advanced Technology CR RRH2x40-07L - HW

Requirements
FID L115269 - Advanced Technology CR RRH2x40-07L - HW Requirements
Global Market
Feature Description
The RRH2x40-07L_AT is a self-contained radio module, containing the following:
• • Transmit paths:
– Two transmit paths of up to 40W each path
– DL 729 -745 MHz, 15.5 MHz instantaneous bandwidth
• Receive paths:
– Two main receive paths, two Aux Rx ports
– 699-715 MHz, 15.5 MHz instantaneous bandwidth
• Support for 5 and 10 MHz LTE carriers. The hardware is capable of supporting a
single or multiple technologies (WCDMA and LTE), and single or multiple carriers.
• Multi Carrier Power Amplifiers (MCPA):
– Two MCPA
• RF front end filters
– Two duplexers
• Two CPRI interfaces
• AISG interface & connector, (one AISG and two internal smart bias-T)
• Its own cooling system via convection
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115269 - Advanced Technology CR RRH2x40-07L - HW
LTE RF Requirements
....................................................................................................................................................................................................................................
The RRH is linked to the BTS using optical fibers supporting CPRI, carrying downlink
and uplink (main and diversity) base band signals, OAM information, and timing
information.
Feature Benefits
This feature is one of the platform products supporting multiple technologies, LTE is
supported in this release, and the RRH is hardware ready to support WCDMA in the
future,
Benefits of this feature include the following:
• Support for high RF power, high capacity applications in a small form factor.
• Support of 2x2 MIMO for increased data rates.
• Support for both continuous and noncontinuous spectrum applications within up to
15.5 MHz.
• The RRH is virtually a no footprint solution that eases problems of site acquisition.
• RRH modules are light, so no craning is needed, which eases site installation.
• RRH Site maintenance is not required.
• Use of the RRH leads to reduced power consumption with the same BTS radio
capacity.
• RRH doesn’t use any fan, therefore offering a noise-free BTS solution.
Impacted Systems
Hardware
Dependencies
Features
None
Hardware
None
Software
None
Interworking
None
Devices
None
Standards
None
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115269 - Advanced Technology CR RRH2x40-07L - HW
LTE RF Requirements
....................................................................................................................................................................................................................................
Restrictions/ Limitations
None
Engineering Impacts
N/A
None
Feature Type
Base
L115270 - Band 12/17 2x60-7L (Lower 700MHz) TRDU - HW

Requirements
L115270 - Band 12/17 2x60-7L (Lower 700MHz) TRDU - HW Requirements
NAR Market
Feature Description
The TRDU2x60-07L is a self-contained radio module, including the following:
• Transmit paths
– Two transmit paths of up to 60W (nominal at EAC) each path (EAC_1 and
EAC_2)
– DL 729 -745 MHz, 15.5 MHz instantaneous bandwidth
– Two Multi-Carrier Power Amplifiers (MCPAs)
– Two duplex filters (each EAC is both transmit and receive).
Receive paths
– Two main receive paths (EAC_1 and EAC_2), plus two auxiliary receive ports
– UL 699-715 MHz, 15.5 MHz instantaneous bandwidth
• Support of 5 and 10 MHz LTE carriers. The hardware is capable of supporting single
or multiple technologies (WCDMA and LTE), and single or multiple carriers.
• Two Common Public Radio Interface (CPRI) interfaces (Primary and Secondary fiber
optic connections with field replaceable SFPs for SM or MM fiber optic connectivity.)
• AISG supported with two smart bias tees (one per antenna port) and an AISG
connector.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115270 - Band 12/17 2x60-7L (Lower 700MHz) TRDU - HW
LTE RF Requirements
....................................................................................................................................................................................................................................
The TRDU is linked to the BTS using either metallic or optical cable supporting CPRI,
carrying downlink and uplink base band signals for two paths (for 2x2 MIMO DL support
and two-way diversity reception), OAM information, and timing information.
Feature Benefits
This feature is one of the platform products supporting multiple technologies and multiple
bands; LTE is supported in this release.
Other benefits of this feature include the following:
• Support for high RF power, high capacity applications in a small form factor.
• Support of Downlink LTE 2x2 MIMO for increased data rates.
• Support of Uplink two-way diversity reception.
• Support for both continuous and noncontinuous spectrum applications within either
band 12 or band 17 (DL 734 – 745, UL 704 – 715 MHz).
Impacted Systems
eNodeB Hardware
Dependencies
None.
N/A
Engineering Impacts
N/A
N/A
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115512 - LTE HW Requirements for RRH4x40-19 (PCS)
LTE RF 65MHz
....................................................................................................................................................................................................................................
L115512 - LTE HW Requirements for RRH4x40-19 (PCS) 65MHz

L115512 - LTE HW Requirements for RRH4x40-19 (PCS) 65MHz
NAR Market Only
Feature Description
This feature adds OA&M support for the 65 MHz 3GPP Band 25 RRH (RRH4x40-19).
Feature Benefits
The RRH4x40-19 allows LTE operation within the 3GPP2 PCS band A through F plus G
blocks.
Impacted Systems
The following systems are impacted:
• OAM
• Platform
• SAM
• NEM
Dependencies
Features
This feature is not dependent on any other software feature.
Hardware
This feature applies to those configurations equipped with the RRH4x40-19.
Software
There are no software dependencies for this feature.
Interworking
None
Devices
None
Standards
None.
This feature is for FDD only.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115512 - LTE HW Requirements for RRH4x40-19 (PCS)
LTE RF 65MHz
....................................................................................................................................................................................................................................
Engineering Impacts
None.
This feature covers operation of the RRH4x40-19 in LTE-only mode. While in this mode
the RFM control mode should be Standalone (MIM parameter CpriRadioEquipment::rfm-
ControlMode set to ‘Standalone’). Note that in other configurations this RRH may be
operated in a shared mode with CDMA. In that case the RFM control mode should be
‘Secondary’.
Note also that this feature modifies how the LTE cell transmit and receive branches are
mapped within the MIM database to RFM antenna ports, in preparation for support in a
later release of multiple LTE cells per RFM. This mapping is done via the new
LteCell/CellAntennaPort object. Each CellAntennaPort instance describes one transmit or
receive branch of the LTE cell, and each instance includes an antennaPortId parameter
used to link this cell branch to a specific RFM antenna port
(CpriRadioEquipment/AntennaPort) instance. Migration rules from LA4.0 to LA5.0.0
handle conversion of previous cell-to-antenna links to this new linkage mechanism.
Feature Type
Base
L115616 - Support for dual-band eNodeB with two modems

FID L115616 Support for dual-band eNodeB with two modems
OI number
3BK36394IHAA

Dual-carrier in dual-band spectrum
Feature Description
This feature details the configurations that are based on two bands inside the same BBU,
with two modems.
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115616 - Support for dual-band eNodeB with two modems
LTE RF
....................................................................................................................................................................................................................................
Feature Benefits
The customer can now configure on each modem one band with one carrier and one
bandwidth. This brings a better coverage by allowing support for two frequency bands in
one eNodeB.
Impacted Systems
OAM, CallP, WPS, and SAM
Dependencies
Features
• L103792 – Inter-frequency Intra FDD/TDD Mobility
• L115223 – Inter-Frequency Balancing
• L115657 – Compatibility Check between Configuration and Modem Card
• L115853 – Factory, Commissioning, 3GPP 36.104/141 Conformance and Customer
Acceptance Test support
Hardware
Controller board eCCM
Software
LA5.0 eNodeB generic software
Restricted to only bands/bandwidth configurations presented by this feature.
There are also some restrictions on antenna cross-connect.
Engineering Impacts
All mentioned dependencies must be solved (updated and/or implemented).
eNodeB with LA5.0 generic software installed
Feature Type
Optional
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115629 - Support for RRH2x60-19 (LTE Only)
LTE RF
....................................................................................................................................................................................................................................
L115629 - Support for RRH2x60-19 (LTE Only)

L115629 - Support for RRH2x60-19 (LTE Only)
NAR Market
Feature Description
This feature provides software and hardware support for LTE on the RRH2x60-19
(Remote Radio Head) for Personal Communication Services (PCS).
Feature Benefits
Increased support for LTE.
Impacted Systems
eNodeB hardware
Dependencies
Features
UMTS feature described in FSD120413 RRH2x60-1900 with 9396 d2U
Hardware
HW developed under UMTS feature described in FSD-110546 - RRH2x60-1900
Software
None.
Interworking
None.
Devices
None.
Standards
TS 36.104, TS 37.104
None.
Engineering Impacts
N/A
....................................................................................................................................................................................................................................
Issue 1 April 2013
LA6.0 features L115629 - Support for RRH2x60-19 (LTE Only)
LTE RF
....................................................................................................................................................................................................................................
N/A
Feature Type
Base
....................................................................................................................................................................................................................................
Issue 1 April 2013
Glossary
...................................................................................................................................................................................................................................
Numerics
2x
'2x' refers to the number of transmit paths supported by the unit, so, for example, an RRH2x60
can transmit on two antenna ports with a maximum of 60 Watts per antenna port.
3GPP 3rd (Generation Partnership Project)

The joint standardization partnership responsible for standardizing UMTS, HSPA and LTE.
3GPP2 3rd (Generation Partnership Project 2)

The joint standardization partnership responsible for standardizing CDMA 2000 and it
derivatives.
...................................................................................................................................................................................................................................
A ASME (Access Security Management Entity)

The entity that receives the top-level keys in an access network from the Home Subscriber Server
(HSS).
...................................................................................................................................................................................................................................
B BCCH (Broadcast Control Channel)

In LTE, the logical channel carrying broadcast system information.
BER (Bit Error Rate)

A measure of received signal quality: the proportion of received bits that is decoded erroneously.
BSIC (Base Station Identification Code)

A 6-bit code that allows a mobile station to distinguish between different neighboring GSM base
stations. The BSIC is made up of a Network Color Code (NCC) and a Base Station Color Code
(BCC).
BSR (Buffers Status Report)

Medium Access Control (MAC)-level messages transmitted by the UE to the serving eNodeB to
provide the eNodeB with information about the amount of data in the uplink buffers of the UE.
BW (Bandwidth)
A measure of the width of a range of frequencies, measured in Hertz.
...................................................................................................................................................................................................................................
C C/I (Carrier-to-Interference Ratio)

The ratio between the power of the Radio Frequency (RF) carrier bearing the wanted signal and
....................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary GL-1
Issue 1 April 2013
Glossary
....................................................................................................................................................................................................................................
the total power of interfering signals.
CAC (Call Admission Control)

The process by which the network decides whether or not to admit a new call.
CDMA (Code Division Multiple Access)

A scheme allowing multiple users to access a given radio channel by the use of CDM to multiplex
the data signals of the different users.
CINR (Carrier-to-Interference-and-Noise Ration)

The ratio between the power of the Radio Frequency (RF) carrier bearing the wanted signal and
the total power of interfering signals and thermal noise.
CQI erasure handling

The process used to manage the case where the CQI is not decoded by the eNodeB.
...................................................................................................................................................................................................................................
D DCCH (Dedicated Control Channel)

In LTE, a logical channel used to deliver dedicated control information relating to a specific UE
(in both uplink and downlink directions), when the UE has a Radio Resource Control (RRC)
connection with the eNodeB.
DCI (Downlink Control Information)

The term used to describe the control signaling messages transmitted on the Physical Downlink
Control Channel (PDCCH), including for example downlink resource assignments (for the
Physical Downlink Shared Channel [PDDSCH]) and uplink transmission grants (for the Physical
Uplink Shared Channel [PUSCH]).
DHCP (Dynamic Host Configuration Protocol)

A protocol used to allocate Internet Protocol (IP) addresses and other configuration parameters to
devices in an IP network.
DL (Downlink)
The radio link in the direction from the base station to the mobile terminal.
DRX (Discontinuous Reception)

The periodic switching off of a receiver, usually to save energy. DRX cycles can be configured in
the LTE downlink so that the UE does not have to decode the Physical Downlink Control Channel
(PDCCH) or receive Physical Downlink Shared CHannel (PDSCH) transmissions in certain sub
frames.
DTX
The status set by the eNodeB when the response sent by the UE about the data previously
transmitted by the eNodeB is not identified properly.
...................................................................................................................................................................................................................................
E E-UTRAN ( Evolved Universal Terrestrial Radio Access Network)

Consists of eNodeBs, providing the User-plane (Packet Data Convergence Protocol [PDCP],
....................................................................................................................................................................................................................................
GL-2 Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013
Glossary
....................................................................................................................................................................................................................................
Radio Link Control [RLC], Medium Access Control [MAC] and PHYsical [PHY] layers) and
Control-plane (Radio Resource Control [RRC]) protocol terminations towards the UE. The
eNodeBs can be interconnected with each other by means of the X2 interface. The eNodeBs are
connected by means of the S1 interface to the Evolved Packet Core (EPC).
eNB
See eNodeB
eNodeB (Evolved NodeB)

The base station in LTE systems. Each eNodeB serves one or more E-UTRAN cells.
EPC (Evolved Packet Core)

The Core Network (CN) in the LTE/System Architecture Evolution (SAE) system. The EPC is
responsible for the overall control of the UE and establishment of the bearers. The main logical
nodes of the EPC are the Packet Data Network Gateway (P-GW), Serving-Gateway (S-GW) and
Mobility Management Entity (MME).
EPS (Evolved Packet System)

The term describing LTE and System Architecture Evolution (SAE) together, comprising both an
evolved core network and an evolved ratio access network.
...................................................................................................................................................................................................................................
F FDD (Frequency Division Duplex)

A mode of bidirectional communications in which transmission and reception take place at the
same time on different carrier frequencies.
FTP (File Transfer Protocol)

A communication protocol used to exchange files through a Transmission control
Protocol/Internet Protocol (TCP/IP) network.
...................................................................................................................................................................................................................................
G GWCN (Gateway Core Network)

A network sharing configuration in which parts of the core network (MSCs/SGSNs/MMEs) are
also shared.
...................................................................................................................................................................................................................................
I IMS (Internet Protocol Multimedia Subsystem)

An architectural framework for delivering Internet Protocol (IP) multimedia services via UTRAN
and EUTRAN.
International Commission on Non-Ionizing Radiation Protection (ICNIRP)

Standards body that sets limits on RF radiation exposure.
...................................................................................................................................................................................................................................
L LTE (Long-Term Evolution)

A radical step in the development of UMTS beyond the original 3rd generation Wideband Code
....................................................................................................................................................................................................................................
Issue 1 April 2013
Glossary
....................................................................................................................................................................................................................................
Division Multiple Access (WCDMA) radio access technology. LTE comprises a new radio
interface and radio access network architecture.
...................................................................................................................................................................................................................................
M MAC (Medium Access Control)

The protocol sublayer above the physical layer and below the Radio Link Control (RLC) layer in
the LTE protocol stack. The connection to the physical layer below is through transport channels,
and the connection to the RLC layer above is through logical channels. The MAC layer performs
data transmission scheduling and multiplexing/demultiplexing between logical channels and
transport channels. In the UE, it is also responsible for control of random access, timing advance
and discontinuous reception.
Management Entity (See , MME)
MIMO (Multiple-Input Multiple-Output)

A transmission scheme between a transmitter and receiver both equipped with multiple antennas.
MME (Mobility Management Entity)

The control node that processes the signaling between the UE and the Core Network (CN) and
provides Visitor Location Register (VLR) functionality for the Evolved Packet System (EPS). It
supports functions related to bearer and connection management.
...................................................................................................................................................................................................................................
O Optical link budget

Applies to the CPRI link connecting RRH to digital (baseband) unit. Different CPRI transceivers
support different rates.
...................................................................................................................................................................................................................................
P PLMN (Public Land Mobile Network area)

The geographical area in which communication services are provided according to the
specifications to mobile users.
...................................................................................................................................................................................................................................
Q QCI (Quality of Service [QoS] Class Identifier)

A parameter of the QoS profile of an Evolved Packet System (EPS) bearer. The QoS Class
Identifier refers to access node specific parameters that control bearer-level packet forwarding
treatment (for example, scheduling weights, admission thresholds, queue management thresholds,
link layer protocol configuration).
...................................................................................................................................................................................................................................
R RACH (Random Access Channel)

A transport channel used for access to the network when the UE does not have accurate uplink
timing synchronization, or when the UE does not have any allocated uplink transmission resource.
The RACH is normally contention-based, which may result in collisions between UEs.
....................................................................................................................................................................................................................................
Issue 1 April 2013
Glossary
....................................................................................................................................................................................................................................
RET
An RET is a device that can change the tilt of an eNodeB antenna.
RFM
An RFM (Radio Frequency Module) is the generic name that represents the Radio Transceiver
unit in the eNodeB. An RFM can represents: a RRH (Remote Radio Head) or a TRDU
transceiver.
RRM (Radio Resource Management)

RRM consists of the system-level control mechanisms used to manage radio resources in the air
interface. The objective of RRM is to maximize the system spectral efficiency and to support
mobility for the users. RRM therefore involves strategies and algorithms for resources allocation,
Modulation and Coding Scheme (MCS), transmission power selection, and mobility.
RSRQ (Reference Signal Received Quality)

N x RSRP/ RSSI, where N is the number of resource blocks across which RSSI was measured.
RUC (Rack User Commissioning)

Entity that sets up the power for the system, stores the serial number for the cabinet, stores
commissioning data, and manages the power and fan speed.
...................................................................................................................................................................................................................................
S S-GW (Serving Gateway)

The gateway that terminates the interface towards the EUTRAN.
For each UE associated with the Evolved Packet System (EPS), at a given point in time, there is a
single S-GW.
...................................................................................................................................................................................................................................
T TMA
TMAs are low noise amplifiers that are mounted in the antenna to amplify the Rx signals.
...................................................................................................................................................................................................................................
U UE (User Equipment)
The mobile unit that allows a user to access network services, connecting to the UTRAN or
E-UTRAN via the radio interface. A UE can be subdivided into a Universal Integrated Circuit
Card (UICC) and a Mobile Equipment (ME).
UL (Uplink)
The radio link in the direction from the mobile to the base station.
....................................................................................................................................................................................................................................
Issue 1 April 2013
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 1 April 2013
Index
Numerics ............................................................. FID 166046, 2-49

1800MHz MC-TRDU in LTE FID L103176, 2-13
D DTX
Only Mode, 2-9
defined, 2-47 FID L105587, 2-52
9711 indoor cabinet, 2-3
Dual-carrier support on one band, FID L106226, 2-65
9712 outdoor cabinet, 2-3
2-57 FID L110547, 2-23
.............................................................
............................................................. FID L112791, 2-35
A Advanced Technology CR
E eNB Call Trace UPOS header FID L114492, 2-53
RRH2x40-07L - HW
optimization, 2-17
Requirements, 2-72 FID L115158, 2-66
eNB Time Zone Management for
ANR Support for Inter Freq FID L115222, 2-26
FM Files, 2-11
Neighbours, 2-13 FID L115223, 2-28
eNodeB SW capacity, 2-55
.............................................................
FID L115241, 2-30
eNodeB SW capacity for LA5.03,
B Band 12/17 2x60-7L (Lower 2-44 FID L115268, 2-71
700MHz) TRDU - HW
Requirements, 2-74 ............................................................. FID L115269, 2-72
F FDD RACH burst format 2, 2-50 FID L115270, 2-74

bCEM commercial introduction,
2-52 FID 131966, 2-11 FID L115512, 2-76
bCEM implementation of 163549 FID 156132, 2-19 FID L115616, 2-77
- Speed-up throughput recovery
FID 156783, 2-59 FID L115627, 2-16
after smartphone specific
behavior, 2-47 FID 157468, 2-3 FID L115629, 2-79
............................................................. FID L115651, 2-33
FID 159276, 2-62
C Commercial Mobile Alert System FID 159512, 2-37 FID L115776, 2-55
(CMAS) support, 2-21 FID L115811, 2-17
FID 160636, 2-39
CQI erasure handling FID L115868, 2-9
FID 160815, 2-41
defined, 2-47 FID L115938, 2-57
FID 163993, 2-44
FID 164117, 2-47 FID L92127, 2-21
FID 164433, 2-7 FID L92639, 2-50
....................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary IN-1
Issue 1 April 2013
Index
....................................................................................................................................................................................................................................
............................................................. FID L115223, 2-28 .............................................................
G Generalized OP-PUCCH, 2-53 FID L115241, 2-30 N Non-GBR prioritization, 2-39
Grant stretching FID L115616, 2-77 .............................................................
defined, 2-49 FID L115651, 2-33

O optical link budget
need for, 2-49 FID L92127, 2-21
defined, 2-74
............................................................. LR Transport and Security
Optimized Segmentation (MCS
Program
Override), 2-41
I Inter-freq Load Balancing, 2-28,
FID L112791, 2-35
2-33 Overload Control - Left-overs
LTE Digital Evolution, Capacity from previous release, 2-19
.............................................................
and Performance Program
Overload Control Evolutions, 2-30
L LA6 bCEM Paging capacity
FID 159512, 2-37
increase, 2-37 .............................................................
FID 160636, 2-39
LA6.0.1, features in P PCS Band 2 RRH2x60 HW
FID 160815, 2-41 Requirements, 2-71
FID L115629, 2-79
FID 163993, 2-44 Performance Counter
lightRadio Cabinet LTE LA
FID 164117, 2-47 Enhancements, 2-16
5.0.2/6.0, 2-3
FID 166046, 2-49 PUSCH grant stretching
lightRadio cabinets
FID L105587, 2-52 defined, 2-49
indoor and outdoor, 2-3
FID L114492, 2-53 PUSCH improvements, 2-49
Program FID L115776, 2-55 .............................................................
FID 157468, 2-3 FID L115938, 2-57 R RDEM HW, 2-65

FID 164433, 2-7 FID L92639, 2-50 RET
LR Multi-Standard RF Program LTE HW Requirements for defined, 2-60
FID L115868, 2-9 RRH4x40-19 (PCS) 65MHz,
RoHC v1 Support for VoIP, 2-23
2-76
LR Operational Effectiveness and .............................................................
Element Management System LTE RF Program
Program S state change time
FID 159276, 2-62
FID 131966, 2-11 FID L106226, 2-65 defined, 2-11
FID L103176, 2-13 FID L115158, 2-66 Support for dual-band eNodeB
with two modems, 2-77
FID L115627, 2-16 FID L115268, 2-71
Support for RRH2x60-19 (LTE
FID L115811, 2-17 FID L115269, 2-72 Only), 2-79
LR Telecom Services and FID L115270, 2-74 Support for RRH2x60-850 (LTE
Application Program
FID L115512, 2-76 Only), 2-62
FID 156132, 2-19
FID L115629, 2-79 Support of MCTRDU 1800 in LR
FID L110547, 2-23 Indoor cabinet, 2-7
LTE RRH Antenna Cross Connect
FID L115222, 2-26 Capability Support in LA4.0.1,
2-66
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013
Index
....................................................................................................................................................................................................................................
.............................................................
T TMA
defined, 2-60
TMA/RET with AISG 2.0
Enhancements in LA/TLA6
(formerly L115277)
FID 156783, 2-59
Transport counters, 2-35
.............................................................
V VoIP Emergency call for

commercial deployment, 2-26
....................................................................................................................................................................................................................................
Alcatel-Lucent 9400 Alcatel-Lucent – Proprietary IN-3
Issue 1 April 2013
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-4 Alcatel-Lucent – Proprietary Alcatel-Lucent 9400
Issue 1 April 2013

FDD Feature Planning Guide Release LA6.0

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FDD Feature Planning Guide Release LA6.0

Загружено:

Авторское право:

Доступные форматы

Use pursuant to applicable agreements

About this document

Supported systems ........................................................................................................................................................................ xi

To obtain technical support, documentation, and training or submit feedback ...................................................... xi

How to comment ......................................................................................................................................................................... xii

1 Introduction to the Feature Planning Guide

Overview ...................................................................................................................................................................................... 1-1

About the features in this document .................................................................................................................................. 1-1

Available in LA6.0 ................................................................................................................................................................... 1-2

Listing of features by Feature ID ........................................................................................................................................ 1-2

Listing of features by Feature Title .................................................................................................................................... 1-3

Listing of features by Program ............................................................................................................................................ 1-3

Overview ...................................................................................................................................................................................... 2-1

LR Cabinets and Configurations

Overview ...................................................................................................................................................................................... 2-3

157468 - lightRadio Cabinet LTE LA 5.0.2/6.0 ............................................................................................................ 2-3

164433 - Support of MCTRDU 1800 in LR Indoor cabinet .................................................................................... 2-7

Overview ...................................................................................................................................................................................... 2-9

L115868 - 1800MHz MC-TRDU in LTE Only Mode ................................................................................................ 2-9

Overview ................................................................................................................................................................................... 2-11

131966 - eNB Time Zone Management for FM Files ............................................................................................... 2-11

L103176 - ANR Support for Inter Freq Neighbours ................................................................................................. 2-13

L115627 - Performance Counter Enhancements ........................................................................................................ 2-16

L115811 - eNB Call Trace UPOS header optimization .......................................................................................... 2-17

LR Telecom Services and Application

Overview ................................................................................................................................................................................... 2-19

156132 - Overload Control - Outdated RRC messages management ................................................................. 2-19

L92127 - Commercial Mobile Alert System (CMAS) support ............................................................................. 2-21

L110547 - RoHC v1 Support for VoIP ........................................................................................................................... 2-23

L115222 - VoIP Emergency call for commercial deployment .............................................................................. 2-26

L115223 – Inter-freq Load Balancing ........................................................................................................................... 2-28

L115241 - Overload Control Evolutions ...................................................................................................................... 2-30

L115651 - Overload Control Improvements ................................................................................................................ 2-33

LR Transport and Security

Overview ................................................................................................................................................................................... 2-35

L112791 - Transport counters ........................................................................................................................................... 2-35

LTE Digital Evolution, Capacity and Performance

Overview ................................................................................................................................................................................... 2-37

159512 - LA6 bCEM Paging capacity increase ......................................................................................................... 2-37

160636 - Non-GBR prioritization .................................................................................................................................... 2-39

160815 - Optimized Segmentation (MCS Override) ................................................................................................ 2-41

163993 - eNodeB SW capacity for LA5.03 .................................................................................................................. 2-44

164117 – bCEM implementation of 163549 - Speed-up throughput recovery after smartphone

166046 - PUSCH improvements ...................................................................................................................................... 2-49

L105587 - bCEM commercial introduction ................................................................................................................. 2-52

L114492 - Generalized OP-PUCCH ............................................................................................................................... 2-53

L115776 - eNodeB SW capacity ...................................................................................................................................... 2-55

L115938 - Dual-carrier support on one band ............................................................................................................... 2-57

Overview ................................................................................................................................................................................... 2-59

159276 - Support for RRH2x60-850 (LTE Only) ...................................................................................................... 2-62

L106226 - RDEM HW ......................................................................................................................................................... 2-65

L115268 - PCS Band 2 RRH2x60 HW Requirements ............................................................................................ 2-71

L115269 - Advanced Technology CR RRH2x40-07L - HW Requirements ..................................................... 2-72

L115512 - LTE HW Requirements for RRH4x40-19 (PCS) 65MHz ................................................................. 2-76

L115629 - Support for RRH2x60-19 (LTE Only) ...................................................................................................... 2-79

2-6 Parameters for configuring capacity ................................................................................................................ 2-46

2-1 Stacking the lightRadio™ cabinet ....................................................................................................................... 2-4

2-2 Configurations for the lightRadio™ outdoor cabinet ................................................................................... 2-5

2-3 ANR Support for Inter Freq Neighbours ........................................................................................................ 2-13

2-4 Supported Header Compression Protocols and Profiles ........................................................................... 2-24

2-5 Optimized segmentation ....................................................................................................................................... 2-42

To obtain technical support, documentation, and training or submit feedback

About the features in this document 1-1

About the features in this document