17 ru50 new features
DESCRIPTION
nokia docuTRANSCRIPT
23-06-2014 – Version 1.3 - 1
Confidential
company.nokia.com
RU50 New Features
1 / 23
RU50 New Features
© Nokia 2014
RU50 New Features
© Nokia 2014
23-06-2014 – Version 1.3 - 2
Confidential
company.nokia.com
This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, sto
adapting or translating, any or all of this material requires the prior written consent of Nokia. This
material also contains confidential information, which may not be disclosed to others without the
prior written consent of Nokia.
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for
the use of Nokia´s customers only for the purpos
is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or
means without the prior written permission
used by professional and properly trained personnel, and the customer assumes full responsibility
when using it. Nokia welcomes customer comments as part of the process of continuous
development and improvement of the documentatio
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
arising in connection with such hardware or software produ
finally in a separate agreement betw
reasonable efforts to ensure that the instructions contained in the document are
free of material errors and omission
which may not be covered by the document.
Nokia will correct errors in this
LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT
LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,SUCH
AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
Other product names mentioned in this document may be trademarks of their respecti
and they are mentioned for identification purposes only.
2 / 23
This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, sto
adapting or translating, any or all of this material requires the prior written consent of Nokia. This
material also contains confidential information, which may not be disclosed to others without the
prior written consent of Nokia.
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for
customers only for the purposes of the agreement under which the document
is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or
means without the prior written permission of Nokia. The documentation has been prepared to
used by professional and properly trained personnel, and the customer assumes full responsibility
welcomes customer comments as part of the process of continuous
development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia and the customer. However, Nokia
reasonable efforts to ensure that the instructions contained in the document are
free of material errors and omissions. Nokia will, if deemed necessary
which may not be covered by the document.
will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA
LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT
LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,SUCH
T LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
This documentation and the product it describes are considered protected by copyrights and
r intellectual property rights according to the applicable laws.
Other product names mentioned in this document may be trademarks of their respecti
and they are mentioned for identification purposes only.
© Nokia 2014
This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, storing,
adapting or translating, any or all of this material requires the prior written consent of Nokia. This
material also contains confidential information, which may not be disclosed to others without the
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for
es of the agreement under which the document
is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or
. The documentation has been prepared to be
used by professional and properly trained personnel, and the customer assumes full responsibility
welcomes customer comments as part of the process of continuous
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
cts shall be defined conclusively and
and the customer. However, Nokia has made all
reasonable efforts to ensure that the instructions contained in the document are adequate and
will, if deemed necessary by Nokia, explain issues
documentation as soon as possible. IN NO EVENT WILL NOKIA BE
LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT
LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,SUCH
T LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
This documentation and the product it describes are considered protected by copyrights and
r intellectual property rights according to the applicable laws.
Other product names mentioned in this document may be trademarks of their respective owners,
© Nokia 2014
adapting or translating, any or all of this material requires the prior written consent of Nokia. This
material also contains confidential information, which may not be disclosed to others without the
es of the agreement under which the document
be
used by professional and properly trained personnel, and the customer assumes full responsibility
The information or statements given in this documentation concerning the suitability, capacity, or
ve owners,
23-06-2014 – Version 1.3 - 3
Confidential
company.nokia.com
Contents 1 Introduction ................................
2 Radio Resource Management and Telecom Features
2.1 Mobility Management
2.1.1 Smart LTE Handover
2.1.2 WCDMA and GSM Layer Priorities
2.1.3 Measurement based LTE Layering
2.1.4 RSRQ-based LTE Reselection
2.2 Admission Control
2.2.1 RRC Connection Setup Redirection
2.3 HSPA Mobility ................................
2.3.1 HSUPA Compressed Mode for LTE and Inter
2.4 Capacity and Efficiency
2.4.1 Dual Band HSDPA 42 Mbps
2.4.2 Enhanced Virtual Antenna Mapping
2.4.3 Data Session Profiling
3 Transmission & Transport
3.1 IP Transport ................................
3.1.1 Performance Monitoring Based on ETH Service OAM
4 Operability ................................
4.1 Network Monitoring and Maintenance
4.1.1 BTS Event Triggered Symptom Data Collection
4.2 Configuration Management
4.2.1 Transport Configura
5 RNC Solution ................................
5.1 WCDMA RNC Products
5.1.1 RTT Improvement to enhance user experience
6 BTS Solution ................................
6.1 Flexi WCDMA BTS Site Solutions and Features
6.1.1 Additional 6 WCDMA Cell Activation
3 / 23
................................................................................................
Radio Resource Management and Telecom Features
Mobility Management ................................................................
Smart LTE Handover ................................................................
WCDMA and GSM Layer Priorities ................................................................
Measurement based LTE Layering ................................
based LTE Reselection ................................................................
Admission Control ................................................................
RRC Connection Setup Redirection ................................
................................................................................................
HSUPA Compressed Mode for LTE and Inter-frequency Handover
acity and Efficiency ................................................................
Dual Band HSDPA 42 Mbps ................................................................
Enhanced Virtual Antenna Mapping ................................
ion Profiling ................................................................
Transmission & Transport ................................................................
................................................................................................
Performance Monitoring Based on ETH Service OAM
................................................................................................
Network Monitoring and Maintenance ................................
BTS Event Triggered Symptom Data Collection ................................
Configuration Management ................................................................
Transport Configuration Fall-back ................................
................................................................................................
WCDMA RNC Products................................................................
RTT Improvement to enhance user experience ................................
................................................................................................
Flexi WCDMA BTS Site Solutions and Features ................................
Additional 6 WCDMA Cell Activation................................
© Nokia 2014
............................................................. 4
Radio Resource Management and Telecom Features........................................................ 6
............................................................................. 6
............................................................................... 6
.......................................................... 7
........................................................................................ 8
................................................................ 9
................................................................................... 10
...................................................................................... 10
........................................................... 12
frequency Handover ................................. 12
........................................................................... 13
.................................................................... 13
...................................................................................... 14
............................................................................. 15
...................................................................... 17
.............................................................. 17
Performance Monitoring Based on ETH Service OAM ........................................................ 17
................................................................ 19
................................................................................. 19
................................................................. 19
................................................................... 20
........................................................................................ 20
............................................................ 22
............................................................................. 22
.................................................................. 22
............................................................. 22
................................................................... 22
...................................................................................... 22
© Nokia 2014
23-06-2014 – Version 1.3 - 4
Confidential
company.nokia.com
1 IntroductionThis document lists and describes the feature candidates fo
The scope of the RU50 includes Radio Network Controller RNC2600 and Flexi Base Station with
FSMC/D/E system modules
Direct, FSMF and Flexi Lite
RU50 release specification base line is 3GPP Release 11
BINDING and subject to changes at any time.
4 / 23
Introduction This document lists and describes the feature candidates for the WCDMA release RU50.
The scope of the RU50 includes Radio Network Controller RNC2600 and Flexi Base Station with
FSMC/D/E system modules. RU50 EP1 requires NetAct 8 EP1.
Direct, FSMF and Flexi Lite is delivered in RU50 EP1. RU50 EP1
RU50 release specification base line is 3GPP Release 11 March 2013
BINDING and subject to changes at any time.
© Nokia 2014
r the WCDMA release RU50.
The scope of the RU50 includes Radio Network Controller RNC2600 and Flexi Base Station with
1. RU50 functionality for mcRNC, Flexi
RU50 EP1 requires NetAct 8 EP2.
March 2013. This document is NON
© Nokia 2014
RU50 functionality for mcRNC, Flexi
23-06-2014 – Version 1.3 - 5
Confidential
company.nokia.com
Summary of changes
Version Date
1.0 20.09.2013
1.1 16.10.2013
1.2 14.04.2014
1.3 23.06.2014
5 / 23
Changes
.2013 C3 proposal
16.10.2013 C3 final version
14.04.2014 RAN2482 and RAN3047 added. RAN2199 description edited.
23.06.2014 C5 version
© Nokia 2014
RAN2482 and RAN3047 added. RAN2199 description edited.
© Nokia 2014
23-06-2014 – Version 1.3 - 6
Confidential
company.nokia.com
2 Radio Resource Management and Telecom Features
2.1 Mobility Management
2.1.1 Smart LTE Handover
Feature Component ID:
Summary: This feature introduces outgoing LTE PS handover.
Benefits for the Customer:
seamless handover experience for the end users.
Functional Description:
compressed mode measurements indicate that LTE coverage is available.
Following events can trigger HSDPA compressed mode measurements for LTE:
1) Cell_DCH to Cell_FACH, Cell_PCH or URA_PCH selection
2) HSDPA reconfiguration to tra
cause reconfiguration to DCH 0/0.
3) CS call release
4) Periodic trigger, operator definable timer
In uplink DCH is used during compressed mode. HSUPA compressed mode is supported with
RAN1668.
In case WCDMA cell load is not high and users can be provided good enough experience in WCDMA
layer, measurements and handover to LTE can be by
used to define if load is low enough for keeping terminals in WC
Both FDD-LTE and TDD
Current Implementation:
reselection takes place in idle, Cell_PCH and URA_PCH states when the LTE coverage is available.
RAN2717: Smart LTE Layering
LTE layers.
RAN2980: Measurement based LTE layering uses compressed mode measurements for confirming
LTE layer availability before redirection is started.
Interdependencies between Features:
For HSUPA compressed mode measurements RAN1668 is required.
This feature requires also support from CN and LTE.
HW Requirements: This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: WBTS9.0
6 / 23
Radio Resource Management and Telecom Features
Mobility Management
Smart LTE Handover
Feature Component ID: RAN2264
This feature introduces outgoing LTE PS handover.
Benefits for the Customer: Smart LTE Handover supports traffic steering to LTE layers, providing
seamless handover experience for the end users.
Functional Description: Inter-system handover from WCDMA to
compressed mode measurements indicate that LTE coverage is available.
Following events can trigger HSDPA compressed mode measurements for LTE:
1) Cell_DCH to Cell_FACH, Cell_PCH or URA_PCH selection
2) HSDPA reconfiguration to traditional DCH. For example high load and lack of cell resources may
cause reconfiguration to DCH 0/0.
4) Periodic trigger, operator definable timer
In uplink DCH is used during compressed mode. HSUPA compressed mode is supported with
In case WCDMA cell load is not high and users can be provided good enough experience in WCDMA
layer, measurements and handover to LTE can be by-passed. RNC level load parameter can be
used to define if load is low enough for keeping terminals in WC
-LTE are supported.
Current Implementation: RAN2067: LTE Interworking enables LTE cell
reselection takes place in idle, Cell_PCH and URA_PCH states when the LTE coverage is available.
RAN2717: Smart LTE Layering provides redirection based traffic steering functionality towards
RAN2980: Measurement based LTE layering uses compressed mode measurements for confirming
LTE layer availability before redirection is started.
Interdependencies between Features: This feature requires RAN2067: LTE Interworking.
For HSUPA compressed mode measurements RAN1668 is required.
This feature requires also support from CN and LTE.
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
dio System Module FSMF.
Software Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: Support not required
WBTS9.0 SGSN: Planned for later release
© Nokia 2014
Radio Resource Management and Telecom Features
This feature introduces outgoing LTE PS handover.
Smart LTE Handover supports traffic steering to LTE layers, providing
system handover from WCDMA to LTE can be started, if
compressed mode measurements indicate that LTE coverage is available.
Following events can trigger HSDPA compressed mode measurements for LTE:
ditional DCH. For example high load and lack of cell resources may
In uplink DCH is used during compressed mode. HSUPA compressed mode is supported with
In case WCDMA cell load is not high and users can be provided good enough experience in WCDMA
passed. RNC level load parameter can be
used to define if load is low enough for keeping terminals in WCDMA.
RAN2067: LTE Interworking enables LTE cell-reselection. Cell-
reselection takes place in idle, Cell_PCH and URA_PCH states when the LTE coverage is available.
provides redirection based traffic steering functionality towards
RAN2980: Measurement based LTE layering uses compressed mode measurements for confirming
This feature requires RAN2067: LTE Interworking.
For HSUPA compressed mode measurements RAN1668 is required.
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
NetAct 8 EP1
Support not required
Planned for later release
© Nokia 2014
Radio Resource Management and Telecom Features
Smart LTE Handover supports traffic steering to LTE layers, providing
ditional DCH. For example high load and lack of cell resources may
In case WCDMA cell load is not high and users can be provided good enough experience in WCDMA
RAN2980: Measurement based LTE layering uses compressed mode measurements for confirming
23-06-2014 – Version 1.3 - 7
Confidential
company.nokia.com
BTS Flexi 10: WBTS9.1
Flexi Lite: WL9.1
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
2.1.2 WCDMA and GSM Layer Priorities
Feature Component ID:
Summary: This feature allows idle mode traffic steering according to priorities given for WCDMA
and GSM layers.
Benefits for the Customer:
the end user throughput when the
Higher priority can be given for example to micro cell layer or high frequency band layer.
Functional Description:
reselection.
When layer specific absolute priority information is provided in the system information broadcast,
UE periodically measures higher priority layers. UE measurements are applicable when the UE is in
idle mode, Cell_PCH, or URA_PCH state. Also lower and equal priority layers ar
radio conditions in the camped frequency fall below search thresholds.
Based on measurements, UE performs priority based cell reselection using both coverage and
quality thresholds broadcast in SIB 19.
For WCDMA and GSM priority
In addition to the priority number for the layer, signal strength and quality thresholds are tools for
adjusting the cell re-selections. Frequency band prioritization can be adjusted with thresho
e.g. prefer 900MHz for cell edge UEs and 2100MHz for close by UEs. UEs above certain threshold
move to higher priority layer, whereas cell edge UEs prefer low priority layer as thresholds are not
met.
7 / 23
WBTS9.1 MGW: Support not required
UE: 3GPP Rel
ASW
RU00436 Smart LTE Handover LK
RAN
License control in network element: RNC LK
License control attributes: Long-term ON/OFF licence
WCDMA and GSM Layer Priorities
nent ID: RAN2881
This feature allows idle mode traffic steering according to priorities given for WCDMA
Benefits for the Customer: Idle mode traffic steering reduces need for handovers and improves
the end user throughput when the most appropriate layer for user is selected.
Higher priority can be given for example to micro cell layer or high frequency band layer.
Functional Description: This feature enables layer priority based WCDMA and GSM cell
absolute priority information is provided in the system information broadcast,
UE periodically measures higher priority layers. UE measurements are applicable when the UE is in
idle mode, Cell_PCH, or URA_PCH state. Also lower and equal priority layers ar
radio conditions in the camped frequency fall below search thresholds.
Based on measurements, UE performs priority based cell reselection using both coverage and
quality thresholds broadcast in SIB 19.
For WCDMA and GSM priority-based cell reselection these thresholds are specified in 3GPP Rel8.
In addition to the priority number for the layer, signal strength and quality thresholds are tools for
selections. Frequency band prioritization can be adjusted with thresho
e.g. prefer 900MHz for cell edge UEs and 2100MHz for close by UEs. UEs above certain threshold
move to higher priority layer, whereas cell edge UEs prefer low priority layer as thresholds are not
© Nokia 2014
Support not required
3GPP Rel-8
RU00436 Smart LTE Handover LK
term ON/OFF licence
This feature allows idle mode traffic steering according to priorities given for WCDMA
Idle mode traffic steering reduces need for handovers and improves
most appropriate layer for user is selected.
Higher priority can be given for example to micro cell layer or high frequency band layer.
This feature enables layer priority based WCDMA and GSM cell
absolute priority information is provided in the system information broadcast,
UE periodically measures higher priority layers. UE measurements are applicable when the UE is in
idle mode, Cell_PCH, or URA_PCH state. Also lower and equal priority layers are measured by UE if
radio conditions in the camped frequency fall below search thresholds.
Based on measurements, UE performs priority based cell reselection using both coverage and
ell reselection these thresholds are specified in 3GPP Rel8.
In addition to the priority number for the layer, signal strength and quality thresholds are tools for
selections. Frequency band prioritization can be adjusted with thresholds,
e.g. prefer 900MHz for cell edge UEs and 2100MHz for close by UEs. UEs above certain threshold
move to higher priority layer, whereas cell edge UEs prefer low priority layer as thresholds are not
© Nokia 2014
Idle mode traffic steering reduces need for handovers and improves
absolute priority information is provided in the system information broadcast,
UE periodically measures higher priority layers. UE measurements are applicable when the UE is in
e measured by UE if
In addition to the priority number for the layer, signal strength and quality thresholds are tools for
e.g. prefer 900MHz for cell edge UEs and 2100MHz for close by UEs. UEs above certain threshold
move to higher priority layer, whereas cell edge UEs prefer low priority layer as thresholds are not
23-06-2014 – Version 1.3 - 8
Confidential
company.nokia.com
Current Implementation:
Interworking feature.
Interdependencies between Features:
with this feature.
HW Requirements: This feature does not require any new or additional HW.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: Support not required
BTS Flexi 10: Support not required
Flexi Lite: Support not required
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
2.1.3 Measurement based LTE Layering
Feature Component ID:
Summary: Redirection from WCDMA to LTE can be used to move the UEs to LTE layer.
Compressed mode measurements are used to determine if LTE coverage is available.
Benefits for the Customer:
before terminal is redirected to LTE guarantee the successful LTE camping.
Functional Description:
for moving UEs to LTE, if compress
Following events can trigger HSDPA compressed mode measurements for LTE:
8 / 23
Current Implementation: Similar mechanism is available for LTE layer priorization with LTE
Interdependencies between Features: Hierarchical Cell Structure can not be used simultaneously
This feature does not require any new or additional HW.
ware Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: Support not required
Support not required SGSN: Support not required
Support not required MGW: Support not required
ort not required UE: 3GPP Rel
ASW
RU00529 WCDMA and GSM Layer Priorities LK
RAN
License control in network element: RNC LK
License control attributes: Long-term ON/OFF licence
asurement based LTE Layering
Feature Component ID: RAN2980
Redirection from WCDMA to LTE can be used to move the UEs to LTE layer.
Compressed mode measurements are used to determine if LTE coverage is available.
Benefits for the Customer: If the WCDMA cell has only partial LTE coverage, measurements
before terminal is redirected to LTE guarantee the successful LTE camping.
Functional Description: RRC Connection Release with Redirection command to LTE can be used
for moving UEs to LTE, if compressed mode measurements indicate that LTE coverage is available.
Following events can trigger HSDPA compressed mode measurements for LTE:
© Nokia 2014
ilable for LTE layer priorization with LTE
Hierarchical Cell Structure can not be used simultaneously
This feature does not require any new or additional HW.
NetAct 8 EP1
Support not required
Support not required
Support not required
3GPP Rel-8
RU00529 WCDMA and GSM Layer Priorities LK
term ON/OFF licence
Redirection from WCDMA to LTE can be used to move the UEs to LTE layer.
Compressed mode measurements are used to determine if LTE coverage is available.
CDMA cell has only partial LTE coverage, measurements
before terminal is redirected to LTE guarantee the successful LTE camping.
RRC Connection Release with Redirection command to LTE can be used
ed mode measurements indicate that LTE coverage is available.
Following events can trigger HSDPA compressed mode measurements for LTE:
© Nokia 2014
Hierarchical Cell Structure can not be used simultaneously
ed mode measurements indicate that LTE coverage is available.
23-06-2014 – Version 1.3 - 9
Confidential
company.nokia.com
1) Cell_DCH to Cell_FACH, Cell_PCH or URA_PCH selection
2) HSDPA reconfiguration to traditional DCH. For example high
cause reconfiguration to DCH 0/0.
3) CS call release
Above mentioned triggers are also used in the Smart LTE Layering feature. In addition to these,
this feature includes a trigger for terminals having long Cell_DCH res
4) Periodic trigger, operator definable timer
In uplink DCH is used during compressed mode. HSUPA compressed mode is supported with
RAN1668.
In case WCDMA cell load is not high and users can be provided good enough experience in
layer, measurements and redirection to LTE can be by
used to define if load is low enough for keeping terminals in WCDMA.
Both FDD-LTE and TDD
Current Implementation:
Layering (RAN2717). Blind redirection is good alternative when e.g. WCDMA and LTE cells are co
located and have well overlapping coverage areas.
Interdependencies between Features:
re-selection in idle, Cell_PCH and URA_PCH states.
For HSUPA compressed mode measurements RAN1668 is required.
HW Requirements: This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: WL9.1
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
2.1.4 RSRQ-based LTE Reselection
Feature Component ID:
9 / 23
1) Cell_DCH to Cell_FACH, Cell_PCH or URA_PCH selection
2) HSDPA reconfiguration to traditional DCH. For example high
cause reconfiguration to DCH 0/0.
Above mentioned triggers are also used in the Smart LTE Layering feature. In addition to these,
this feature includes a trigger for terminals having long Cell_DCH res
4) Periodic trigger, operator definable timer
In uplink DCH is used during compressed mode. HSUPA compressed mode is supported with
In case WCDMA cell load is not high and users can be provided good enough experience in
layer, measurements and redirection to LTE can be by-passed. RNC level load parameter can be
used to define if load is low enough for keeping terminals in WCDMA.
-LTE are supported.
Current Implementation: Redirection without measurements is supported with Smart LTE
Layering (RAN2717). Blind redirection is good alternative when e.g. WCDMA and LTE cells are co
located and have well overlapping coverage areas.
Interdependencies between Features: RAN2067: LTE Interworking provides s
selection in idle, Cell_PCH and URA_PCH states.
For HSUPA compressed mode measurements RAN1668 is required.
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
re Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: Support not required
WBTS9.0 SGSN: Support not required
WBTS9.1 MGW: Support not required
UE: 3GPP Rel
ASW
RU00539 Measurement based LTE Layering LK
RAN
License control in network element: RNC LK
License control attributes: Long-term ON/OFF licence
based LTE Reselection
ID: RAN3069
© Nokia 2014
2) HSDPA reconfiguration to traditional DCH. For example high load and lack of cell resources may
Above mentioned triggers are also used in the Smart LTE Layering feature. In addition to these,
this feature includes a trigger for terminals having long Cell_DCH reservations for PS services:
In uplink DCH is used during compressed mode. HSUPA compressed mode is supported with
In case WCDMA cell load is not high and users can be provided good enough experience in WCDMA
passed. RNC level load parameter can be
used to define if load is low enough for keeping terminals in WCDMA.
asurements is supported with Smart LTE
Layering (RAN2717). Blind redirection is good alternative when e.g. WCDMA and LTE cells are co-
RAN2067: LTE Interworking provides support for LTE cell
For HSUPA compressed mode measurements RAN1668 is required.
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
NetAct 8 EP1
Support not required
Support not required
Support not required
3GPP Rel-8
RU00539 Measurement based LTE Layering LK
term ON/OFF licence
© Nokia 2014
load and lack of cell resources may
WCDMA
23-06-2014 – Version 1.3 - 10
Confidential
company.nokia.com
Summary: RSRQ based LTE cell reselection is supported.
Benefits for the Customer:
case RSRQ is used in the LTE NW as reselection criteria.
Functional Description:
feature includes quality thresholds for LTE priority
3GPP Rel9. The Rel9 quality thresholds include the UTRA serving cell Ec/No threshold and E
neighbor cell RSRQ quality thresholds.
Current Implementation:
reselection.
Interdependencies between Features:
HW Requirements: This feature does not r
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: Support not required
BTS Flexi 10: Support not required
Flexi Lite: Support not required
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network el
License control attributes:
2.2 Admission Control
2.2.1 RRC Connection Setup Redirection
Feature Component ID:
Summary: In case the RRC connection is rejected the UE is proactively sent by RNC to 2G or to 3G
to a new frequency for a next try.
Benefits for the Customer:
congestion.
Functional Description:
and Load based Handover, Directed
Load Balancing. The mentioned features perform the load balancing actions during the UEs are
active or moving between inactive and active RRC states. However, this feature utilises the
balancing in very early phase by employing RRC Connection Setup Rejection message and
10 / 23
RSRQ based LTE cell reselection is supported.
Benefits for the Customer: Maximise LTE user experience. Smooth WCDMA
case RSRQ is used in the LTE NW as reselection criteria.
Functional Description: This feature is an upgrade to RAN2067 LTE Interworking feature. This
feature includes quality thresholds for LTE priority-based cell reselection, which are specified in
3GPP Rel9. The Rel9 quality thresholds include the UTRA serving cell Ec/No threshold and E
cell RSRQ quality thresholds.
Current Implementation: RAN2067 LTE Interworking feature supports RSRP based LTE
Interdependencies between Features: This feature requíres RAN2067 LTE Interworking feature.
This feature does not require any new or additional HW.
Software Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: Support not required
Support not required SGSN: Support not required
Support not required MGW: Support not required
Support not required UE: 3GPP Rel
ASW
This feature is included in the same sales item with
RAN2067 LTE interworking.
RAN
License control in network element: RNC LK
License control attributes: Not defined
RRC Connection Setup Redirection
Feature Component ID: RAN147
In case the RRC connection is rejected the UE is proactively sent by RNC to 2G or to 3G
or a next try.
Benefits for the Customer: Better subscriber experience due to less call setup delay in case of
Functional Description: This feature is extension to existing load balancing features like Service
and Load based Handover, Directed RRC connection setup, HSPA layering features and Multi
Load Balancing. The mentioned features perform the load balancing actions during the UEs are
active or moving between inactive and active RRC states. However, this feature utilises the
in very early phase by employing RRC Connection Setup Rejection message and
© Nokia 2014
Maximise LTE user experience. Smooth WCDMA-LTE interworking in
upgrade to RAN2067 LTE Interworking feature. This
based cell reselection, which are specified in
3GPP Rel9. The Rel9 quality thresholds include the UTRA serving cell Ec/No threshold and E-UTRA
RAN2067 LTE Interworking feature supports RSRP based LTE
This feature requíres RAN2067 LTE Interworking feature.
equire any new or additional HW.
NetAct 8 EP1
Support not required
Support not required
pport not required
3GPP Rel-9
This feature is included in the same sales item with
RAN2067 LTE interworking.
In case the RRC connection is rejected the UE is proactively sent by RNC to 2G or to 3G
Better subscriber experience due to less call setup delay in case of
This feature is extension to existing load balancing features like Service
RRC connection setup, HSPA layering features and Multi-Band
Load Balancing. The mentioned features perform the load balancing actions during the UEs are
active or moving between inactive and active RRC states. However, this feature utilises the
in very early phase by employing RRC Connection Setup Rejection message and
© Nokia 2014
UTRA
This feature is included in the same sales item with
In case the RRC connection is rejected the UE is proactively sent by RNC to 2G or to 3G
Band
23-06-2014 – Version 1.3 - 11
Confidential
company.nokia.com
directing the access to another cell of different WCDMA frequency or GSM system already in RRC
connection setup phase.
In case the RRC connection setup faces any kind of congestion
Rejection message to the UE. The message contains information where UE shall start cell selection
procedure. Target can be another WCDMA frequency layer or GSM system. For Rel
UEs also exact cell where cell sel
UEs just WCDMA frequency layer or GSM system can be identified. LTE cannot be target in this
feature. If RNC signaling unit overload is the reason for RRC connection rejection, then UE is
directed to GSM without target cell list.
RRC Connection Setup Redirection differs from the Directed RRC Connection Setup so that RRC
connection is not completed, but a RRC Connection Rejection message is sent to the UE. Directed
RRC Connection Setup can be
Setup Redirection can be done also to other BTSs' cells and to GSM cells.
The feature utilizes load status information of other WCDMA frequency layer cells and GSM cells in
the selection procedure of the target cell. Serving cell can have the load status information of
target cell based on RNSAP common load measurements over Iur, penalty which is set due to
rejected handover attempts to target cells and by means of internal signaling inside RN
The feature is controlled by the RNC. Target WCDMA frequency layer, WCDMA cell, GSM system or
GSM cell is selected with algorithm and cell based management parameters. It is possible to define
by operator where the redirection should be done depending
the RRC connection setup request. It is also possible to control whether this feature is utilized for
directing UEs to WCDMA or GSM, or to both.
Existing neighbor cell list is used for selecting target cell. The algorit
is not already high loaded.
Current Implementation:
Interdependencies between Features:
HW Requirements: This feature does not require any new or additional HW.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: Support not required
BTS Flexi 10: Support not required
Flexi Lite: Support not required
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
11 / 23
directing the access to another cell of different WCDMA frequency or GSM system already in RRC
connection setup phase.
In case the RRC connection setup faces any kind of congestion
Rejection message to the UE. The message contains information where UE shall start cell selection
procedure. Target can be another WCDMA frequency layer or GSM system. For Rel
UEs also exact cell where cell selection procedure is started can be identified. For Rel
UEs just WCDMA frequency layer or GSM system can be identified. LTE cannot be target in this
feature. If RNC signaling unit overload is the reason for RRC connection rejection, then UE is
irected to GSM without target cell list.
RRC Connection Setup Redirection differs from the Directed RRC Connection Setup so that RRC
connection is not completed, but a RRC Connection Rejection message is sent to the UE. Directed
RRC Connection Setup can be done only inside same WCDMA BTS and sector but RRC Connection
Setup Redirection can be done also to other BTSs' cells and to GSM cells.
The feature utilizes load status information of other WCDMA frequency layer cells and GSM cells in
edure of the target cell. Serving cell can have the load status information of
target cell based on RNSAP common load measurements over Iur, penalty which is set due to
rejected handover attempts to target cells and by means of internal signaling inside RN
The feature is controlled by the RNC. Target WCDMA frequency layer, WCDMA cell, GSM system or
GSM cell is selected with algorithm and cell based management parameters. It is possible to define
by operator where the redirection should be done depending
the RRC connection setup request. It is also possible to control whether this feature is utilized for
directing UEs to WCDMA or GSM, or to both.
Existing neighbor cell list is used for selecting target cell. The algorit
is not already high loaded.
Current Implementation: -
Interdependencies between Features: -
This feature does not require any new or additional HW.
Software Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: Support not required
Support not required SGSN: Support not required
Support not required MGW: Support not required
Support not required UE: Support not required
ASW
RU00527 RRC Connection Setup Redirection LK
RAN
License control in network element: RNC LK
License control attributes: Long-term ON/OFF licence
© Nokia 2014
directing the access to another cell of different WCDMA frequency or GSM system already in RRC
In case the RRC connection setup faces any kind of congestion RNC signals RRC Connection Setup
Rejection message to the UE. The message contains information where UE shall start cell selection
procedure. Target can be another WCDMA frequency layer or GSM system. For Rel-6 and newer
ection procedure is started can be identified. For Rel-5 and older
UEs just WCDMA frequency layer or GSM system can be identified. LTE cannot be target in this
feature. If RNC signaling unit overload is the reason for RRC connection rejection, then UE is
RRC Connection Setup Redirection differs from the Directed RRC Connection Setup so that RRC
connection is not completed, but a RRC Connection Rejection message is sent to the UE. Directed
done only inside same WCDMA BTS and sector but RRC Connection
Setup Redirection can be done also to other BTSs' cells and to GSM cells.
The feature utilizes load status information of other WCDMA frequency layer cells and GSM cells in
edure of the target cell. Serving cell can have the load status information of
target cell based on RNSAP common load measurements over Iur, penalty which is set due to
rejected handover attempts to target cells and by means of internal signaling inside RNC.
The feature is controlled by the RNC. Target WCDMA frequency layer, WCDMA cell, GSM system or
GSM cell is selected with algorithm and cell based management parameters. It is possible to define
by operator where the redirection should be done depending on the establishment cause value of
the RRC connection setup request. It is also possible to control whether this feature is utilized for
Existing neighbor cell list is used for selecting target cell. The algorithm also checks that target cell
This feature does not require any new or additional HW.
etAct 8 EP1
Support not required
Support not required
Support not required
Support not required
RU00527 RRC Connection Setup Redirection LK
term ON/OFF licence
© Nokia 2014
directing the access to another cell of different WCDMA frequency or GSM system already in RRC
RNC signals RRC Connection Setup
Rejection message to the UE. The message contains information where UE shall start cell selection
5 and older
connection is not completed, but a RRC Connection Rejection message is sent to the UE. Directed
done only inside same WCDMA BTS and sector but RRC Connection
The feature utilizes load status information of other WCDMA frequency layer cells and GSM cells in
The feature is controlled by the RNC. Target WCDMA frequency layer, WCDMA cell, GSM system or
GSM cell is selected with algorithm and cell based management parameters. It is possible to define
on the establishment cause value of
the RRC connection setup request. It is also possible to control whether this feature is utilized for
hm also checks that target cell
23-06-2014 – Version 1.3 - 12
Confidential
company.nokia.com
2.3 HSPA Mobility
2.3.1 HSUPA Compressed Mode for LTE a
Feature Component ID:
Summary: This feature introduces HSUPA compressed mode measurement for 3G to LTE
redirection and PS HO. Also HSUPA compressed mode measurement for inter
and HSUPA/HSDPA inter
Benefits for the Customer:
mode improve end user experience during inter
Functional Description:
frequency measurements. Compressed mode on HSUPA/HSDPA enables measurements without
UL channel type switching to DCH. HSUPA CM configuration for inter
single frame method with 7 slots tra
measurement is double frame method with >10 slots TGP. Compressed mode is supported while
the radio bearers are mapped to E
includes also the case where DL SRB is mapped to DCH or HSDPA.
This feature includes also HSUPA inter
frequency handover and HSPA serving cell change directly from HSUPA, without UL channel type
switching to DCH. Existing I
or inter-RNC cell.
HSUPA CM for LTE can be utilised by RAN2980 Measurement based LTE Layering and RAN2264
Smart LTE Handover. All the control, signaling and RRM decision making of measu
redirection and PS HO to LTE are included in those features.
Avoiding the channel type switch to UL DCH, will reduce the total handover execution time up to
1.5s. Also high HSUPA throughput can be maintained during compressed mode.
In case of HSDPA and DCH, there are also double frame compressed mode configurations needed
for LTE measurements. Those compressed mode configurations do not need this feature, but
they are supported in RAN2980 and RAN2264.
Current Implementation:
UL transport channel to DCH before compressed mode is started for IFHO measurements. After
inter-frequency handover using UL DCH, a switch back to HSPA can be performed. Direct switch
from HSPA to non-zero
feature.
For the case of SRB standalone with DCH on DL and HSPA on UL currently no interfrequency
measurements are performed.
Interdependencies between Features:
mode for LTE and IFHO measurements. HSDPA/HSUPA IFHO needs this feature and HSDPA Inter
frequency Handover (RAN1276) feature. HSUPA CM for LTE can be utilised by RAN2980
Measurement based LTE Layering and RAN2264 Smart LTE Ha
Operational Aspects: In order to distinguish HSUPA
new HSUPA Compressed Mode
12 / 23
HSUPA Compressed Mode for LTE and Inter-frequency Handover
Feature Component ID: RAN1668
This feature introduces HSUPA compressed mode measurement for 3G to LTE
redirection and PS HO. Also HSUPA compressed mode measurement for inter
and HSUPA/HSDPA inter-frequency handover are part of this feature.
Benefits for the Customer: Faster handover and higher data throughput during compressed
mode improve end user experience during inter-frequency and LTE measurements.
Functional Description: This feature introduces HSUPA compressed mode (CM) for LTE and inter
frequency measurements. Compressed mode on HSUPA/HSDPA enables measurements without
UL channel type switching to DCH. HSUPA CM configuration for inter
single frame method with 7 slots transmission gap pattern (TGP). HSUPA CM configuration for LTE
measurement is double frame method with >10 slots TGP. Compressed mode is supported while
the radio bearers are mapped to E-DCH in uplink and SRBs are mapped on DCH or E
e case where DL SRB is mapped to DCH or HSDPA.
This feature includes also HSUPA inter-frequency handover procedure. RNC performs inter
frequency handover and HSPA serving cell change directly from HSUPA, without UL channel type
switching to DCH. Existing IFHO reasons can trigger HSUPA IFHO. The target cell can be an intra
HSUPA CM for LTE can be utilised by RAN2980 Measurement based LTE Layering and RAN2264
Smart LTE Handover. All the control, signaling and RRM decision making of measu
redirection and PS HO to LTE are included in those features.
Avoiding the channel type switch to UL DCH, will reduce the total handover execution time up to
1.5s. Also high HSUPA throughput can be maintained during compressed mode.
HSDPA and DCH, there are also double frame compressed mode configurations needed
for LTE measurements. Those compressed mode configurations do not need this feature, but
they are supported in RAN2980 and RAN2264.
Current Implementation: Currently inter-frequency HSPA mobility is performed by switching the
UL transport channel to DCH before compressed mode is started for IFHO measurements. After
frequency handover using UL DCH, a switch back to HSPA can be performed. Direct switch
DCH and vice versa is supported with HSDPA Dynamic Resource Allocation
For the case of SRB standalone with DCH on DL and HSPA on UL currently no interfrequency
measurements are performed.
Interdependencies between Features: This feature can be us
mode for LTE and IFHO measurements. HSDPA/HSUPA IFHO needs this feature and HSDPA Inter
frequency Handover (RAN1276) feature. HSUPA CM for LTE can be utilised by RAN2980
Measurement based LTE Layering and RAN2264 Smart LTE Ha
In order to distinguish HSUPA-handovers new counters are introduced. Also
new HSUPA Compressed Mode-counters are introduced.
© Nokia 2014
frequency Handover
This feature introduces HSUPA compressed mode measurement for 3G to LTE
redirection and PS HO. Also HSUPA compressed mode measurement for inter-frequency handover
uency handover are part of this feature.
Faster handover and higher data throughput during compressed
frequency and LTE measurements.
SUPA compressed mode (CM) for LTE and inter-
frequency measurements. Compressed mode on HSUPA/HSDPA enables measurements without
UL channel type switching to DCH. HSUPA CM configuration for inter-frequency measurement is
nsmission gap pattern (TGP). HSUPA CM configuration for LTE
measurement is double frame method with >10 slots TGP. Compressed mode is supported while
DCH in uplink and SRBs are mapped on DCH or E-DCH. This
e case where DL SRB is mapped to DCH or HSDPA.
frequency handover procedure. RNC performs inter-
frequency handover and HSPA serving cell change directly from HSUPA, without UL channel type
FHO reasons can trigger HSUPA IFHO. The target cell can be an intra-
HSUPA CM for LTE can be utilised by RAN2980 Measurement based LTE Layering and RAN2264
Smart LTE Handover. All the control, signaling and RRM decision making of measurement based
Avoiding the channel type switch to UL DCH, will reduce the total handover execution time up to
1.5s. Also high HSUPA throughput can be maintained during compressed mode.
HSDPA and DCH, there are also double frame compressed mode configurations needed
for LTE measurements. Those compressed mode configurations do not need this feature, but
quency HSPA mobility is performed by switching the
UL transport channel to DCH before compressed mode is started for IFHO measurements. After
frequency handover using UL DCH, a switch back to HSPA can be performed. Direct switch
DCH and vice versa is supported with HSDPA Dynamic Resource Allocation
For the case of SRB standalone with DCH on DL and HSPA on UL currently no interfrequency
This feature can be used to support HSUPA compressed
mode for LTE and IFHO measurements. HSDPA/HSUPA IFHO needs this feature and HSDPA Inter-
frequency Handover (RAN1276) feature. HSUPA CM for LTE can be utilised by RAN2980
Measurement based LTE Layering and RAN2264 Smart LTE Handover features.
handovers new counters are introduced. Also
© Nokia 2014
frequency handover
-
frequency measurements. Compressed mode on HSUPA/HSDPA enables measurements without
nsmission gap pattern (TGP). HSUPA CM configuration for LTE
measurement is double frame method with >10 slots TGP. Compressed mode is supported while
HSDPA and DCH, there are also double frame compressed mode configurations needed
quency HSPA mobility is performed by switching the
DCH and vice versa is supported with HSDPA Dynamic Resource Allocation
-
handovers new counters are introduced. Also
23-06-2014 – Version 1.3 - 13
Confidential
company.nokia.com
HW Requirements: This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: WL9.1
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
2.4 Capacity and Efficiency
2.4.1 Dual Band HSDPA 42 Mbps
Feature Component ID:
Summary: Two 5 MHz WCDMA carriers are used simultaneously in DL for a single UE so that both 5
MHz frequencies are on different UMTS bands.
Benefits for the Customer:
MHz frequency allocation is available. Higher value from additional frequency band is obtained.
Lower band provides coverage while higher band provides increased capacity and peak rate.
NodeB based scheduling enables d
frequency band while users close by mainly utilize the high frequency. This approach maximizes
the sector coverage and capacity.
Functional Description:
bands in DL. Maximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available on
both frequencies. 3GPP Rel9 limits the feature so that the two frequencies can not be non
adjacent frequencies on same band. Also UL is r
is not allowed.
NodeB utilizes proportional fair scheduling and optimizes the sector coverage and capacity by
favoring low frequency band for cell edge UEs and high frequency band for UEs close to the
NodeB. This allows DB-DC
benefits of low frequency band for far away users.
In UL direction a single carrier is used.
Current Implementation:
same frequency band.
13 / 23
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
radio System Module FSMF.
Software Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: Support not required
WBTS9.0 SGSN: Support not required
WBTS9.1 MGW: Support not required
UE: 3GPP Rel
ASW
RU00533 HSUPA Inter
HSPA
License control in network element: RNC LK
License control attributes: Long-term ON/OFF licence
Efficiency
Dual Band HSDPA 42 Mbps
Feature Component ID: RAN2179
Two 5 MHz WCDMA carriers are used simultaneously in DL for a single UE so that both 5
MHz frequencies are on different UMTS bands.
Benefits for the Customer: DC-HSDPA benefits can be obtained even when no contiguous 10
MHz frequency allocation is available. Higher value from additional frequency band is obtained.
Lower band provides coverage while higher band provides increased capacity and peak rate.
NodeB based scheduling enables dynamic resource sharing so that far
frequency band while users close by mainly utilize the high frequency. This approach maximizes
the sector coverage and capacity.
Functional Description: DB-DC-HSDPA schedules data for capable UE o
bands in DL. Maximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available on
both frequencies. 3GPP Rel9 limits the feature so that the two frequencies can not be non
adjacent frequencies on same band. Also UL is restricted to single carrier HSUPA, DB or DC
NodeB utilizes proportional fair scheduling and optimizes the sector coverage and capacity by
favoring low frequency band for cell edge UEs and high frequency band for UEs close to the
DC-HSDPA to combine the gain of normal DC
benefits of low frequency band for far away users.
In UL direction a single carrier is used.
Current Implementation: RAN1906: Dual-Cell HSDPA 42 Mbps is available for adja
© Nokia 2014
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
NetAct 8 EP1
Support not required
Support not required
Support not required
3GPP Rel-6
RU00533 HSUPA Inter-frequency Handover LK
term ON/OFF licence
Two 5 MHz WCDMA carriers are used simultaneously in DL for a single UE so that both 5
e obtained even when no contiguous 10
MHz frequency allocation is available. Higher value from additional frequency band is obtained.
Lower band provides coverage while higher band provides increased capacity and peak rate.
ynamic resource sharing so that far-away UEs mainly use low
frequency band while users close by mainly utilize the high frequency. This approach maximizes
HSDPA schedules data for capable UE on two distinct frequency
bands in DL. Maximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available on
both frequencies. 3GPP Rel9 limits the feature so that the two frequencies can not be non-
estricted to single carrier HSUPA, DB or DC-HSUPA
NodeB utilizes proportional fair scheduling and optimizes the sector coverage and capacity by
favoring low frequency band for cell edge UEs and high frequency band for UEs close to the
HSDPA to combine the gain of normal DC-HSDPA scheduling and the
Cell HSDPA 42 Mbps is available for adjacent carriers on
© Nokia 2014
Two 5 MHz WCDMA carriers are used simultaneously in DL for a single UE so that both 5
bands in DL. Maximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available on
HSUPA
cent carriers on
23-06-2014 – Version 1.3 - 14
Confidential
company.nokia.com
Interdependencies between Features:
Use of 64QAM modulation requires RAN1643: HSPDA 64QAM. Licenses for two separate
frequency bands in the same NodeB and RNC ar
HW Requirements: This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Flexi Rel1, Rel2 or Rel3 RF modules can be used, but mixed configurations of Rel1 RF module with
Rel2 RF module or Rel1 RF mod
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: Not planned
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
2.4.2 Enhanced Virtual A
Feature Component ID:
Summary: In Virtual Antenna Mapping the WCDMA/HSDPA downlink signals of a cell, non
MIMO, are all sent from two physical antennas using a virtual antenna mapping matrix between
the virtual antennas and p
difference between the two physical antennas is tuned to obtain best signal quality for HSDPA.
Benefits for the Customer:
can be obtained for stationary or low speed UE:s with one Rx.
Functional Description:
MIMO, but it can be used in all cases where the base station is configured with two Tx, i.e. physi
MIMO configuration. With the VAM the cell is sent from two physical antennas using a virtual
antenna mapping between the virtual antennas and physical antennas, and the mapping can be
used for non-MIMO or MIMO cases.
VAM is beneficial for adding powe
diversity when the cross
14 / 23
Interdependencies between Features: This feature requires RAN1906: Dual Cell HSDPA 42 Mbps.
Use of 64QAM modulation requires RAN1643: HSPDA 64QAM. Licenses for two separate
frequency bands in the same NodeB and RNC are required.
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Flexi Rel1, Rel2 or Rel3 RF modules can be used, but mixed configurations of Rel1 RF module with
Rel2 RF module or Rel1 RF module with Rel3 RF module are not allowed.
Software Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: Support not required
WBTS9.0 SGSN: SG8.0
WBTS9.1 MGW: Support not required
Not planned UE: 3GPP Rel
ASW
RU00432 Dual
RAN
License control in network element: RNC LK
License control attributes: Long-term capacity licence
Enhanced Virtual Antenna Mapping
Feature Component ID: RAN2482
In Virtual Antenna Mapping the WCDMA/HSDPA downlink signals of a cell, non
MIMO, are all sent from two physical antennas using a virtual antenna mapping matrix between
the virtual antennas and physical antennas. In the Enhanced Virtual Antenna Mapping the phase
difference between the two physical antennas is tuned to obtain best signal quality for HSDPA.
Benefits for the Customer: Higher average HSDPA cell throughput can be achieved. Highest gain
can be obtained for stationary or low speed UE:s with one Rx.
Functional Description: Virtual Antenna Mapping (VAM) was introduced with the feature RAN1642:
MIMO, but it can be used in all cases where the base station is configured with two Tx, i.e. physi
MIMO configuration. With the VAM the cell is sent from two physical antennas using a virtual
antenna mapping between the virtual antennas and physical antennas, and the mapping can be
MIMO or MIMO cases.
VAM is beneficial for adding power of two PA:s instead of one PA and introducing polarization
diversity when the cross-polarized base station antennas are used.
© Nokia 2014
This feature requires RAN1906: Dual Cell HSDPA 42 Mbps.
Use of 64QAM modulation requires RAN1643: HSPDA 64QAM. Licenses for two separate
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Flexi Rel1, Rel2 or Rel3 RF modules can be used, but mixed configurations of Rel1 RF module with
ule with Rel3 RF module are not allowed.
NetAct 8 EP1
Support not required
SG8.0
Support not required
3GPP Rel-9
RU00432 Dual-Band HSDPA LK
term capacity licence
In Virtual Antenna Mapping the WCDMA/HSDPA downlink signals of a cell, non-MIMO or
MIMO, are all sent from two physical antennas using a virtual antenna mapping matrix between
hysical antennas. In the Enhanced Virtual Antenna Mapping the phase
difference between the two physical antennas is tuned to obtain best signal quality for HSDPA.
Higher average HSDPA cell throughput can be achieved. Highest gain
can be obtained for stationary or low speed UE:s with one Rx.
Virtual Antenna Mapping (VAM) was introduced with the feature RAN1642:
MIMO, but it can be used in all cases where the base station is configured with two Tx, i.e. physical
MIMO configuration. With the VAM the cell is sent from two physical antennas using a virtual
antenna mapping between the virtual antennas and physical antennas, and the mapping can be
r of two PA:s instead of one PA and introducing polarization
polarized base station antennas are used.
© Nokia 2014
This feature requires RAN1906: Dual Cell HSDPA 42 Mbps.
Flexi Rel1, Rel2 or Rel3 RF modules can be used, but mixed configurations of Rel1 RF module with
MIMO or
Virtual Antenna Mapping (VAM) was introduced with the feature RAN1642:
cal
23-06-2014 – Version 1.3 - 15
Confidential
company.nokia.com
The RAN2482: Enhanced Virtual Antenna Mapping (E
VAM further, by controlling the phase
RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase difference between the two
physical antennas to obtain the best signal quality for HSDPA. The channel quality indicators of
active non-MIMO UEs in the cell are used to obtain the best phase difference between the two
physical antennas. Tuning of the phase offset is dynamic and automatic. Cell throughput gain
increases when the number of simultaneous active HSDPA users decreases.
In the field tests cell throughput gain of 5
the most efficiently when the cell CQI distribution is between 16
obtained for one Rx UE:s.
Current Implementation:
control between the physical antennas.
Interdependencies between Features:
MIMO configuration is needed, i.e. two Tx per cell, where Enhanced Virtual Antenna Mapping is
going to be used.
HW Requirements: This feature requires RAN1016/RAN1848: Flexi BTS Multimode System
Module, double PA units and antenna lines. Both Flexi Rel 1 and Rel 2 RF modules can be used, but
mixed configurations of both Rel 1 and Rel 2 are not allowed.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: WL9.1
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
2.4.3 Data Session Profiling
Feature Component ID:
Summary: UE is moved directly from Cell_PCH t
amounts within short time period. Frequently sent large data amounts suggest that applications
are actively used in the UE side, for example web browsing session.
Benefits for the Customer:
are increased to 512B or 1kB, in order to allow keep alive packets on common channels. For small
15 / 23
The RAN2482: Enhanced Virtual Antenna Mapping (E-VAM) feature improves the performance of
VAM further, by controlling the phase difference between the two physical antennas. The
RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase difference between the two
physical antennas to obtain the best signal quality for HSDPA. The channel quality indicators of
UEs in the cell are used to obtain the best phase difference between the two
physical antennas. Tuning of the phase offset is dynamic and automatic. Cell throughput gain
increases when the number of simultaneous active HSDPA users decreases.
ests cell throughput gain of 5-50% compared to VAM only is achieved. E
the most efficiently when the cell CQI distribution is between 16
obtained for one Rx UE:s.
Current Implementation: Virtual Antenna Mapping has been
control between the physical antennas.
Interdependencies between Features: No dependencies. Please notice that at base station a
MIMO configuration is needed, i.e. two Tx per cell, where Enhanced Virtual Antenna Mapping is
This feature requires RAN1016/RAN1848: Flexi BTS Multimode System
Module, double PA units and antenna lines. Both Flexi Rel 1 and Rel 2 RF modules can be used, but
mixed configurations of both Rel 1 and Rel 2 are not allowed.
Software Dependencies for RU50:
NetAct: NetAct 8 EP1
mcRNC4.1 MSC: -
WBTS9.0 SGSN: -
WBTS9.1 MGW: -
UE: -
ASW
RU00535 Enhanc
RAN
License control in network element: RNC LK
License control attributes: Long-term capacity licence
Data Session Profiling
Feature Component ID: RAN2963
UE is moved directly from Cell_PCH to Cell_DCH if UE has been sending large data
amounts within short time period. Frequently sent large data amounts suggest that applications
are actively used in the UE side, for example web browsing session.
Benefits for the Customer: This feature has been designed for cells where Cell_FACH thresholds
are increased to 512B or 1kB, in order to allow keep alive packets on common channels. For small
© Nokia 2014
VAM) feature improves the performance of
difference between the two physical antennas. The
RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase difference between the two
physical antennas to obtain the best signal quality for HSDPA. The channel quality indicators of
UEs in the cell are used to obtain the best phase difference between the two
physical antennas. Tuning of the phase offset is dynamic and automatic. Cell throughput gain
increases when the number of simultaneous active HSDPA users decreases.
50% compared to VAM only is achieved. E-VAM works
the most efficiently when the cell CQI distribution is between 16-22. The best benefits are
Virtual Antenna Mapping has been implemented without a phase
No dependencies. Please notice that at base station a
MIMO configuration is needed, i.e. two Tx per cell, where Enhanced Virtual Antenna Mapping is
This feature requires RAN1016/RAN1848: Flexi BTS Multimode System
Module, double PA units and antenna lines. Both Flexi Rel 1 and Rel 2 RF modules can be used, but
mixed configurations of both Rel 1 and Rel 2 are not allowed.
NetAct 8 EP1
RU00535 Enhanced Virtual Antenna Mapping LK
term capacity licence
o Cell_DCH if UE has been sending large data
amounts within short time period. Frequently sent large data amounts suggest that applications
are actively used in the UE side, for example web browsing session.
designed for cells where Cell_FACH thresholds
are increased to 512B or 1kB, in order to allow keep alive packets on common channels. For small
© Nokia 2014
RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase difference between the two
Module, double PA units and antenna lines. Both Flexi Rel 1 and Rel 2 RF modules can be used, but
amounts within short time period. Frequently sent large data amounts suggest that applications
designed for cells where Cell_FACH thresholds
are increased to 512B or 1kB, in order to allow keep alive packets on common channels. For small
23-06-2014 – Version 1.3 - 16
Confidential
company.nokia.com
keep alive messages FACH/RACH channels are efficient; less signaling and HSPA resources can be
used for real data transmission.
End-user-experience is improved and not suffered from high Cell_FACH thresholds as RNC
detects if UE has been sending relatively large data amounts within short time period, and
allocates HSPA directly. State transition from Cell_PCH to Cel
state is skipped.
Shorter Cell_DCH state inactivity timers can be used, as direct Cell_PCH
fast. This further improves HSPA efficiency.
Functional Description:
exceeds defined theshold, UE is moved directly to Cell_DCH state if next data transmission starts
within defined time period.
Threshold for amount of data triggering the direct Cell_DCH state allocation is adjustable. A
time period used to monitor data session continuation is adjustable.
When 128B default Cell_FACH threshold in increased to 512B/1kB and this feature is activated in a
cell
- More smartphone keep
- More fast Cell_PCH - HSPA allocations, i.e. unnecessary Cell_FACH state transmission is skipped
with the help of this feature
When activated, Data Session Profiling is applicable by default to all UEs. Is preferred by operator,
feature can be disabled for HS
Current Implementation:
Interdependencies between Features:
and it is assumed that fast dormancy issue is handled with RAN2136 Fast Dormancy and RAN2451
Fast Dormancy Profiling features, and Cell_PCH state is used for keeping UEs connected. However,
RAN2136 and RAN2451 are not mandatory requirements.
RAN2494 Fast Cell_PCH Switching is recommended to be used with the Data Session Profiling
feature. It helps in achieving faster state transmissions to the Cell_DCH state.
HW Requirements: This feature does not require any new or additional HW.
Software Dependencies for RU50:
IPA-RNC: RN8.0
16 / 23
keep alive messages FACH/RACH channels are efficient; less signaling and HSPA resources can be
a transmission.
experience is improved and not suffered from high Cell_FACH thresholds as RNC
detects if UE has been sending relatively large data amounts within short time period, and
allocates HSPA directly. State transition from Cell_PCH to Cel
Shorter Cell_DCH state inactivity timers can be used, as direct Cell_PCH
fast. This further improves HSPA efficiency.
Functional Description: If amount of NRT data sent or received during Cell_DCH state allocation
exceeds defined theshold, UE is moved directly to Cell_DCH state if next data transmission starts
within defined time period.
Threshold for amount of data triggering the direct Cell_DCH state allocation is adjustable. A
time period used to monitor data session continuation is adjustable.
When 128B default Cell_FACH threshold in increased to 512B/1kB and this feature is activated in a
More smartphone keep-alive -type packets are expected on Cell_FACH
HSPA allocations, i.e. unnecessary Cell_FACH state transmission is skipped
with the help of this feature
When activated, Data Session Profiling is applicable by default to all UEs. Is preferred by operator,
feature can be disabled for HS-RACH capable UEs.
Current Implementation: This is a new feature.
Interdependencies between Features: This feature is further optimization for smartphone traffic,
and it is assumed that fast dormancy issue is handled with RAN2136 Fast Dormancy and RAN2451
Dormancy Profiling features, and Cell_PCH state is used for keeping UEs connected. However,
RAN2136 and RAN2451 are not mandatory requirements.
RAN2494 Fast Cell_PCH Switching is recommended to be used with the Data Session Profiling
achieving faster state transmissions to the Cell_DCH state.
This feature does not require any new or additional HW.
Software Dependencies for RU50:
NetAct: NetAct 8 EP1
© Nokia 2014
keep alive messages FACH/RACH channels are efficient; less signaling and HSPA resources can be
experience is improved and not suffered from high Cell_FACH thresholds as RNC
detects if UE has been sending relatively large data amounts within short time period, and
allocates HSPA directly. State transition from Cell_PCH to Cell_DCH is ~1s faster when Cell_FACH
Shorter Cell_DCH state inactivity timers can be used, as direct Cell_PCH - Cell_DCH allocation is
ved during Cell_DCH state allocation
exceeds defined theshold, UE is moved directly to Cell_DCH state if next data transmission starts
Threshold for amount of data triggering the direct Cell_DCH state allocation is adjustable. Also
time period used to monitor data session continuation is adjustable.
When 128B default Cell_FACH threshold in increased to 512B/1kB and this feature is activated in a
type packets are expected on Cell_FACH
HSPA allocations, i.e. unnecessary Cell_FACH state transmission is skipped
When activated, Data Session Profiling is applicable by default to all UEs. Is preferred by operator,
This feature is further optimization for smartphone traffic,
and it is assumed that fast dormancy issue is handled with RAN2136 Fast Dormancy and RAN2451
Dormancy Profiling features, and Cell_PCH state is used for keeping UEs connected. However,
RAN2494 Fast Cell_PCH Switching is recommended to be used with the Data Session Profiling
achieving faster state transmissions to the Cell_DCH state.
This feature does not require any new or additional HW.
NetAct 8 EP1
© Nokia 2014
keep alive messages FACH/RACH channels are efficient; less signaling and HSPA resources can be
exceeds defined theshold, UE is moved directly to Cell_DCH state if next data transmission starts
When 128B default Cell_FACH threshold in increased to 512B/1kB and this feature is activated in a
HSPA allocations, i.e. unnecessary Cell_FACH state transmission is skipped
When activated, Data Session Profiling is applicable by default to all UEs. Is preferred by operator,
This feature is further optimization for smartphone traffic,
and it is assumed that fast dormancy issue is handled with RAN2136 Fast Dormancy and RAN2451
Dormancy Profiling features, and Cell_PCH state is used for keeping UEs connected. However,
23-06-2014 – Version 1.3 - 17
Confidential
company.nokia.com
mcRNC: mcRNC4.1
BTS Flexi: Support not required
BTS Flexi 10: Support not required
Flexi Lite: Support not required
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
3 Transmission & Transport
3.1 IP Transport
3.1.1 Performance Monitoring Based on ETH Service OAM
Feature Component ID:
Summary: Performance monitoring as per ITU
Ethernet performance SLAs per VLAN.
Benefits for the Customer:
performance measurements at Ethernet level up t
Especially degradations in the network performance that happen slowly over time can be
identified early by supervising the trend in delay and delay variation related measurements. The
feature is suited to reduce op
maintenance and troubleshooting. The measured transport network quality characteristics have
impact on KPIs and, therefore, on end customer call quality perception.
Functional Description:
Performance Monitoring capabilities based on Ethernet Service OAM frames in the BTS.
The Ethernet OAM PM functions defined in ITU
following:
- Frame Loss Measurement both dual ended (ETH
- Frame Delay Measurement (ETH
Measurement.
ITU-T Ethernet service OAM standard Y.1731 and the IEEE standard 802.1ag require that the L2
network is set up based on hierarchical levels, with Maintenance Domains. Different Maintenance
Domain Levels can be allocated to users, service providers and operators. Maintenance end points
(MEPs) are assigned to the edges of each domain and maintenance in
17 / 23
mcRNC4.1 MSC: Support not required
Support not required SGSN: Support not required
Support not required MGW: Support not required
Support not required UE: Support not required
ASW
RU00521 Data Session Pr
RAN
License control in network element: RNC LK
License control attributes: Long-term ON/OFF licence
Transmission & Transport
Performance Monitoring Based on ETH Service OAM
Feature Component ID: RAN2243
Performance monitoring as per ITU-T Y.1731 is provided on the BTS to measure
Ethernet performance SLAs per VLAN.
Benefits for the Customer: Customers operating their own L2 backhaul network can obtain
performance measurements at Ethernet level up to the NodeB and monitor leased line SLAs.
Especially degradations in the network performance that happen slowly over time can be
identified early by supervising the trend in delay and delay variation related measurements. The
feature is suited to reduce operational expenditure related to bring
maintenance and troubleshooting. The measured transport network quality characteristics have
impact on KPIs and, therefore, on end customer call quality perception.
Functional Description: This feature enhances the RAN1880 Ethernet OAM feature to include
Performance Monitoring capabilities based on Ethernet Service OAM frames in the BTS.
The Ethernet OAM PM functions defined in ITU-T Y.1731 supported with this features are the
Loss Measurement both dual ended (ETH-CCM) and single
Frame Delay Measurement (ETH-DM): Two-way Delay and One
T Ethernet service OAM standard Y.1731 and the IEEE standard 802.1ag require that the L2
work is set up based on hierarchical levels, with Maintenance Domains. Different Maintenance
Domain Levels can be allocated to users, service providers and operators. Maintenance end points
(MEPs) are assigned to the edges of each domain and maintenance in
© Nokia 2014
Support not required
Support not required
Support not required
Support not required
RU00521 Data Session Profiling LK
term ON/OFF licence
T Y.1731 is provided on the BTS to measure
Customers operating their own L2 backhaul network can obtain
o the NodeB and monitor leased line SLAs.
Especially degradations in the network performance that happen slowly over time can be
identified early by supervising the trend in delay and delay variation related measurements. The
erational expenditure related to bring-up of the network, its
maintenance and troubleshooting. The measured transport network quality characteristics have
impact on KPIs and, therefore, on end customer call quality perception.
feature enhances the RAN1880 Ethernet OAM feature to include
Performance Monitoring capabilities based on Ethernet Service OAM frames in the BTS.
T Y.1731 supported with this features are the
CCM) and single-ended (ETH-LM)
way Delay and One-way Delay Variation
T Ethernet service OAM standard Y.1731 and the IEEE standard 802.1ag require that the L2
work is set up based on hierarchical levels, with Maintenance Domains. Different Maintenance
Domain Levels can be allocated to users, service providers and operators. Maintenance end points
(MEPs) are assigned to the edges of each domain and maintenance intermediate points (MIPs) to
© Nokia 2014
work is set up based on hierarchical levels, with Maintenance Domains. Different Maintenance
Domain Levels can be allocated to users, service providers and operators. Maintenance end points
termediate points (MIPs) to
23-06-2014 – Version 1.3 - 18
Confidential
company.nokia.com
ports within domains. This helps to define the relationships between all entities from a
maintenance perspective, to allow each entity to monitor the layers under its responsibility and
easily localize problems.
The feature supports initiating several frame loss measurement sessions and provides counters
for transmitted and received data frames between a pair of MEPs. Out of these counters, the
frame loss can be calculated for each direction. Near
are provided. Additionally, the feature responds to frame loss measurement sessions initiated
from remote MEPs, such as access routers/switches.
There are two methods for measuring frame loss defined in the standard:
- Dual-ended ETH-LM: proactive
- Single-ended ETH-LM: on
LMM and ETH-LMR).
The BTS supports both kinds of frame loss measurements. The measurement type is user
configurable.
The BTS offers the possibility to initiate Delay Measurement sessions and provide two
and one-way delay variation. The feature also responds to Delay Measurement sessions initiated
from the remote MEP. It is as well possible to configure thresho
delay variation measurements, based on which an alarm is raised, when the threshold value is
exceeded.
It must be taken into account that the standard foresees monitoring for point
connections. The measurement res
modeled as point-to-point ETH connections between the measurement MEPs (Maintenance
Association End Points).
Current Implementation:
- dependent on transport networks scenario
level.
Interdependencies between Features:
Transport Network Measurements".
HW Requirements: Requires NPGE in RNC a
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module
FSMF.
BTS Transport HW: Flexi FTIA
BTS Transport HW: Flexi FTJA
BTS Transport HW: Flexi FTIB
18 / 23
ports within domains. This helps to define the relationships between all entities from a
maintenance perspective, to allow each entity to monitor the layers under its responsibility and
easily localize problems.
ports initiating several frame loss measurement sessions and provides counters
for transmitted and received data frames between a pair of MEPs. Out of these counters, the
frame loss can be calculated for each direction. Near-end and far
are provided. Additionally, the feature responds to frame loss measurement sessions initiated
from remote MEPs, such as access routers/switches.
There are two methods for measuring frame loss defined in the standard:
LM: proactive measurement which uses dual
LM: on-demand measurement which uses single
The BTS supports both kinds of frame loss measurements. The measurement type is user
The BTS offers the possibility to initiate Delay Measurement sessions and provide two
way delay variation. The feature also responds to Delay Measurement sessions initiated
from the remote MEP. It is as well possible to configure thresho
delay variation measurements, based on which an alarm is raised, when the threshold value is
It must be taken into account that the standard foresees monitoring for point
connections. The measurement results are only accurate when the network configuration is
point ETH connections between the measurement MEPs (Maintenance
Association End Points).
Current Implementation: RAN1900 "IP Transport Network Measurements" made available in RU
dependent on transport networks scenario - serves similar purpose for measurement on L3
Interdependencies between Features: Requires RAN1880 "Ethernet OAM" and RAN1900 "IP
Transport Network Measurements".
Requires NPGE in RNC and Ethernet-enabled Transport Sub
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module
Flexi FTIA
Flexi FTJA
Flexi FTIB
© Nokia 2014
ports within domains. This helps to define the relationships between all entities from a
maintenance perspective, to allow each entity to monitor the layers under its responsibility and
ports initiating several frame loss measurement sessions and provides counters
for transmitted and received data frames between a pair of MEPs. Out of these counters, the
end and far-end frame loss measurement
are provided. Additionally, the feature responds to frame loss measurement sessions initiated
There are two methods for measuring frame loss defined in the standard:
measurement which uses dual-ended frames (ETH-CCM)
demand measurement which uses single-ended ETH-LM frames (ETH-
The BTS supports both kinds of frame loss measurements. The measurement type is user
The BTS offers the possibility to initiate Delay Measurement sessions and provide two-way delay,
way delay variation. The feature also responds to Delay Measurement sessions initiated
from the remote MEP. It is as well possible to configure thresholds for the two-way delay and
delay variation measurements, based on which an alarm is raised, when the threshold value is
It must be taken into account that the standard foresees monitoring for point-to-point ETH
ults are only accurate when the network configuration is
point ETH connections between the measurement MEPs (Maintenance
RAN1900 "IP Transport Network Measurements" made available in RU30
serves similar purpose for measurement on L3
Requires RAN1880 "Ethernet OAM" and RAN1900 "IP
enabled Transport Sub-Modules in BTS.
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module
© Nokia 2014
-
way delay,
way delay variation. The feature also responds to Delay Measurement sessions initiated
30
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module
23-06-2014 – Version 1.3 - 19
Confidential
company.nokia.com
BTS Transport HW: Flexi FTLB
BTS Transport HW: Flexi FTFB
BTS Transport HW: Flexi Multiradio System Module without Transport Sub
BTS Transport HW: Flexi Multiradio System Module with FTIF
BTS Transport HW: Flexi Lite without Transport Sub
Software Dependencies
IPA-RNC: Support not required
mcRNC: Support not required
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: WL9.1
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
4 Operability
4.1 Network Monitoring and Maintenance
4.1.1 BTS Event Trigger
Feature Component ID:
Summary: Operator-defined BTS fault triggered symptom data collection in base station.
This function is part of Centralized function to collect symptom data in network elements with self
triggered symptom data generation.
Benefits for the Customer:
active problem solving. Logs are available always after problem has triggered.
Functional Description:
benefit from immediate data collection right after fault helps the most in troubleshooting.
User can define any different BTS faults as triggers, and several can be active at the same time.
User can also set the threshold
collection is started.
For faults triggering BTS reset, symptom data is lost during reset.
19 / 23
Flexi FTLB
Flexi FTFB
Flexi Multiradio System Module without Transport Sub
Flexi Multiradio System Module with FTIF
Flexi Lite without Transport Sub-Module
Software Dependencies for RU50:
Support not required NetAct: NetAct 8 EP1
Support not required MSC: Support not required
WBTS9.0 SGSN: Support not required
WBTS9.1 MGW: Support not required
UE: Support n
ASW
RAN
License control in network element: TRS LK
License control attributes: Long-term ON/OFF licence
Network Monitoring and Maintenance
BTS Event Triggered Symptom Data Collection
Feature Component ID: RAN2199
defined BTS fault triggered symptom data collection in base station.
This function is part of Centralized function to collect symptom data in network elements with self
ymptom data generation.
Benefits for the Customer: Automatic symptom data collection gives possibility to focus on
active problem solving. Logs are available always after problem has triggered.
Functional Description: Automatic symptom data collection is
benefit from immediate data collection right after fault helps the most in troubleshooting.
User can define any different BTS faults as triggers, and several can be active at the same time.
User can also set the threshold which defines how many times the fault is set until symptom data
For faults triggering BTS reset, symptom data is lost during reset.
© Nokia 2014
Flexi Multiradio System Module without Transport Sub-Module
Flexi Multiradio System Module with FTIF
Module
NetAct 8 EP1
Support not required
Support not required
Support not required
Support not required
term ON/OFF licence
defined BTS fault triggered symptom data collection in base station.
This function is part of Centralized function to collect symptom data in network elements with self
Automatic symptom data collection gives possibility to focus on
active problem solving. Logs are available always after problem has triggered.
Automatic symptom data collection is based on BTS faults, so that the
benefit from immediate data collection right after fault helps the most in troubleshooting.
User can define any different BTS faults as triggers, and several can be active at the same time.
which defines how many times the fault is set until symptom data
For faults triggering BTS reset, symptom data is lost during reset.
© Nokia 2014
This function is part of Centralized function to collect symptom data in network elements with self
which defines how many times the fault is set until symptom data
23-06-2014 – Version 1.3 - 20
Confidential
company.nokia.com
Symptom data collection happens when BTS fault is set, which utilizes the BTS snapshot function
and contains short history before the fault happened.
Symptom data is compressed and named in a common way upon data collection.
In the symptom data file there is the catalog file which describes why the symptom data was
created (reason for troubleshooting
are included and what is their role.
Centralized symptom data transfer happens automatically to OMS immediately when symptom
data file is ready.
Old symptom data files are deleted automatically.
HW Requirements: This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: WL9.1
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
4.2 Configuration Management
4.2.1 Transport Configuration Fall
Feature Component ID:
Summary: If after configuration update the Flexi Multiradio BTS fails to connect to its
management network, the BTS fall
operator about the failed configuration update.
Benefits for the Customer:
maintenance by avoiding site visits and increases the Flexi Mul
outages.
Functional Description:
A fallback to the previous configuration happens when after a configuration update and activation
the BTS fails to (re)connect successfully
20 / 23
Symptom data collection happens when BTS fault is set, which utilizes the BTS snapshot function
d contains short history before the fault happened.
Symptom data is compressed and named in a common way upon data collection.
In the symptom data file there is the catalog file which describes why the symptom data was
created (reason for troubleshooting data collection), when it was done, what symptom data files
are included and what is their role.
Centralized symptom data transfer happens automatically to OMS immediately when symptom
Old symptom data files are deleted automatically.
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
NetAct: Support not required
mcRNC4.1 MSC: Support not required
TS9.0 SGSN: Support not required
WBTS9.1 MGW: Support not required
UE: Support not required
BSW
RAN
License control in network element: Not defined
License control attributes: Not defined
Configuration Management
Transport Configuration Fall-back
Feature Component ID: RAN2554
If after configuration update the Flexi Multiradio BTS fails to connect to its
management network, the BTS falls back to the former working configuration and informs the
operator about the failed configuration update.
Benefits for the Customer: Self healing reduces the effort for network management and
maintenance by avoiding site visits and increases the Flexi Mul
Functional Description: Autonomous fallback to previous configuration.
A fallback to the previous configuration happens when after a configuration update and activation
the BTS fails to (re)connect successfully to the RNC-OMU.
© Nokia 2014
Symptom data collection happens when BTS fault is set, which utilizes the BTS snapshot function
Symptom data is compressed and named in a common way upon data collection.
In the symptom data file there is the catalog file which describes why the symptom data was
data collection), when it was done, what symptom data files
Centralized symptom data transfer happens automatically to OMS immediately when symptom
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Support not required
Support not required
Support not required
Support not required
Support not required
If after configuration update the Flexi Multiradio BTS fails to connect to its
s back to the former working configuration and informs the
Self healing reduces the effort for network management and
maintenance by avoiding site visits and increases the Flexi Multiradio BTS availability due to less
Autonomous fallback to previous configuration.
A fallback to the previous configuration happens when after a configuration update and activation
© Nokia 2014
Symptom data collection happens when BTS fault is set, which utilizes the BTS snapshot function
A fallback to the previous configuration happens when after a configuration update and activation
23-06-2014 – Version 1.3 - 21
Confidential
company.nokia.com
First BTS tries to establish m
seconds between the attempts.
If this fails, BTS tries to establish the m
30 seconds between the attempts.
If the management plane can be established with the old configuration a notification is sent to the
Network Management System indicating that the new configuration was not activated.
If the old configuration fails as well the recei
with the regular link failure mechanism to continuously repeat the connection establishment with
the new configuration.
Current Implementation:
Interdependencies between Features:
HW Requirements: This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
IPA-RNC: Support not required
mcRNC: Support not required
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: WL9.1
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
21 / 23
First BTS tries to establish m-plane connection with the new configuration 10 times, waiting 30
seconds between the attempts.
If this fails, BTS tries to establish the m-plane connection with old configuration 10 times, waiting
between the attempts.
If the management plane can be established with the old configuration a notification is sent to the
Network Management System indicating that the new configuration was not activated.
If the old configuration fails as well the received new one is activated again and the BTS continues
with the regular link failure mechanism to continuously repeat the connection establishment with
Current Implementation: none
Interdependencies between Features: none
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
Support not required NetAct: Support not required
Support not required MSC: Support not require
WBTS9.0 SGSN: Support not required
WBTS9.1 MGW: Support not required
UE: Support not required
ASW
RAN2554LKC Transport configuration fallback LK
RAN
© Nokia 2014
plane connection with the new configuration 10 times, waiting 30
plane connection with old configuration 10 times, waiting
If the management plane can be established with the old configuration a notification is sent to the
Network Management System indicating that the new configuration was not activated.
ved new one is activated again and the BTS continues
with the regular link failure mechanism to continuously repeat the connection establishment with
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Support not required
Support not required
Support not required
Support not required
Support not required
RAN2554LKC Transport configuration fallback LK
© Nokia 2014
plane connection with old configuration 10 times, waiting
If the management plane can be established with the old configuration a notification is sent to the
ved new one is activated again and the BTS continues
with the regular link failure mechanism to continuously repeat the connection establishment with
23-06-2014 – Version 1.3 - 22
Confidential
company.nokia.com
License control in network element:
License control attributes:
5 RNC Solution
5.1 WCDMA RNC Products
5.1.1 RTT Improvement to enhance user experience
Feature Component ID:
Summary: RNC internal HSPA delay is reduced an
improved.
Benefits for the Customer:
thereby enhancing the user experience.
Functional Description:
internal delay in HS(D)PA Downlink data path.
1-4 ms overall end-to-end RTT delay reduction for small packets (32 bytes) can be expected. The
best benefit is achieved with HSUPA 2 ms TTI.
Software Dependencies for RU50:
IPA-RNC: RN8.0
mcRNC: mcRNC4.1
BTS Flexi: Support not required
BTS Flexi 10: Support not required
Flexi Lite: Support not required
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
6 BTS Solution
6.1 Flexi WCDMA BTS Site Solutions and Features
6.1.1 Additional 6 WCDMA Ce
Feature Component ID:
Summary: Additional 6 WCDMA cell activation license key enables increase of supported cells in
BTS configuration.
22 / 23
License control in network element: BTS LK
License control attributes: Not defined
RNC Solution
WCDMA RNC Products
RTT Improvement to enhance user experience
Feature Component ID: RAN3047
RNC internal HSPA delay is reduced and end to end latency of small packets is
Benefits for the Customer: Lower latency improves response times for interactive services,
thereby enhancing the user experience.
Functional Description: Improvement in Round Trip Time (RTT) is achieved by
internal delay in HS(D)PA Downlink data path.
end RTT delay reduction for small packets (32 bytes) can be expected. The
best benefit is achieved with HSUPA 2 ms TTI.
Software Dependencies for RU50:
NetAct: Support not required
mcRNC4.1 MSC: Support not required
Support not required SGSN: Support not required
Support not required MGW: Support not required
Support not required UE: Support not req
BSW
RAN
License control in network element: Not defined
License control attributes: Not defined
BTS Solution
Flexi WCDMA BTS Site Solutions and Features
Additional 6 WCDMA Cell Activation
Feature Component ID: RAN3017
Additional 6 WCDMA cell activation license key enables increase of supported cells in
© Nokia 2014
d end to end latency of small packets is
Lower latency improves response times for interactive services,
Improvement in Round Trip Time (RTT) is achieved by reducing the RNC
end RTT delay reduction for small packets (32 bytes) can be expected. The
Support not required
Support not required
Support not required
Support not required
Support not required
Additional 6 WCDMA cell activation license key enables increase of supported cells in
© Nokia 2014
end RTT delay reduction for small packets (32 bytes) can be expected. The
23-06-2014 – Version 1.3 - 23
Confidential
company.nokia.com
Benefits for the Customer:
MORAN or multi-band configurations.
Functional Description:
supported cells in BTS configuration. Step size is 6 cells. Need for License key(s) is checked based
on the cell setups in the
Amount of License keys needed:
0 - 12 cells: 0 x LK
13 - 18 cells: 1 x LK
Supported configurations are described in Flexi Multiradio BTS WCDMA Supported and Planned
Configurations document.
Current Implementation:
feature. RAN3017LK - 6 WCDMA cell activation License key must be used if BTS site configuration
has more than 12 cells.
Interdependencies between Features:
HW Requirements: This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
IPA-RNC: Support not required
mcRNC: Support not required
BTS Flexi: WBTS9.0
BTS Flexi 10: WBTS9.1
Flexi Lite: Not relevant
SW Sales Information:
BSW/ASW:
Sales item:
RAS SW component:
License control in network element:
License control attributes:
23 / 23
Benefits for the Customer: More than 12 cells per BTS site is typically needed in case of 6 sector
band configurations.
Functional Description: Additional 6 WCDMA cell activation license key enables increase of
supported cells in BTS configuration. Step size is 6 cells. Need for License key(s) is checked based
on the cell setups in the BTS. Up to 12 cells are enabled without a license key.
Amount of License keys needed:
Supported configurations are described in Flexi Multiradio BTS WCDMA Supported and Planned
Configurations document.
nt Implementation: Current RAN2736LK - 18 cell BTS License Key is replaced by this
6 WCDMA cell activation License key must be used if BTS site configuration
Interdependencies between Features: -
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Multiradio System Module FSMF.
Software Dependencies for RU50:
Support not required NetAct: Support not required
Support not required MSC: Support not required
WBTS9.0 SGSN: Support not required
WBTS9.1 MGW: Support not required
Not relevant UE: Support not required
ASW
RAN3017LK
RAN
l in network element: BTS LK
License control attributes: Long-term capacity licence
© Nokia 2014
More than 12 cells per BTS site is typically needed in case of 6 sector
Additional 6 WCDMA cell activation license key enables increase of
supported cells in BTS configuration. Step size is 6 cells. Need for License key(s) is checked based
BTS. Up to 12 cells are enabled without a license key.
Supported configurations are described in Flexi Multiradio BTS WCDMA Supported and Planned
18 cell BTS License Key is replaced by this
6 WCDMA cell activation License key must be used if BTS site configuration
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi
Support not required
Support not required
Support not required
Support not required
Support not required
term capacity licence
© Nokia 2014
More than 12 cells per BTS site is typically needed in case of 6 sector,
supported cells in BTS configuration. Step size is 6 cells. Need for License key(s) is checked based
6 WCDMA cell activation License key must be used if BTS site configuration