FUD_RU50_11

Prepared by

Date 16.10.2013

/23

Nokia Solutions and Networks WCDMA/HSPA

Approved by

Doc number

Version 1.1

FEATURES UNDER DEVELOPMENT DOCUMENT WCDMA RELEASE RU50

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks´ customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Solutions and Networks 2013. All rights reserved.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

Table of Contents 1 Introduction ......................................................................................................................... 4

2 Radio Resource Management and Telecom Features ........................................................ 6

2.1 Mobility Management ................................................................................................... 6

2.1.1 Smart LTE Handover ............................................................................................ 6

2.1.2 WCDMA and GSM Layer Priorities ....................................................................... 7

2.1.3 Measurement based LTE Layering ....................................................................... 9

2.1.4 RSRQ-based LTE Reselection ............................................................................10

2.2 Admission Control .......................................................................................................11

2.2.1 RRC Connection Setup Redirection .....................................................................11

2.3 HSPA Mobility .............................................................................................................13

2.3.1 HSUPA Compressed Mode for LTE and Inter-frequency Handover .....................13

2.4 Capacity and Efficiency ...............................................................................................14

2.4.1 Dual Band HSDPA 42 Mbps ................................................................................14

2.4.2 Data Session Profiling ..........................................................................................15

3 Transmission & Transport ..................................................................................................17

3.1 IP Transport ................................................................................................................17

3.1.1 Performance Monitoring Based on ETH Service OAM .........................................17

4 Operability ..........................................................................................................................20

4.1 Network Monitoring and Maintenance .........................................................................20

4.1.1 BTS Event Triggered Symptom Data Collection ...................................................20

4.2 Configuration Management .........................................................................................21

4.2.1 Transport Configuration Fall-back ........................................................................21

5 BTS Solution ......................................................................................................................23

5.1 Flexi WCDMA BTS Site Solutions and Features .........................................................23

5.1.1 Additional 6 WCDMA Cell Activation ....................................................................23

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

1 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. FSMF and mcRNC support is included in RU50 EP1. RU50 release specification base line is 3GPP Release 11 March 2013. All the features in this document are Feature Candidates and there may be changes to the final solutions due to the final screening and 3GPP's standardisation changes. The content of this document is subject to change mainly due to the status of standardisation and the actual release definition process. This document is NON BINDING and subject to changes at any time.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

Summary of changes

Version Date Changes

1.0 20.09.2013 C3 proposal

1.1 16.10.2013 C3 final version

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

2 Radio Resource Management and Telecom Features

2.1 Mobility Management

2.1.1 Smart LTE Handover

Feature Component ID: RAN2264

Summary: 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 LTE can be started, if 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.

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-passed. RNC level load parameter can be used to define if load is low enough for keeping terminals in WCDMA.

Both FDD-LTE and TDD-LTE are supported.

Current Implementation: 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.

RAN2717: Smart LTE Layering provides redirection based traffic steering functionality towards LTE layers.

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.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

For HSUPA compressed mode measurements RAN1668 is required.

This feature requires also support from CN and LTE.

HW Requirements: This feature requires RAN1016/RAN1848: Flexi BTS Multimode System Module.

Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: Support not required BTS Flexi: WBTS9.0 SGSN: NS4.0 BTS Flexi 10: WBTS9.1 MGW: Support not required UE: 3GPP Rel-8 SW Sales Information: BSW/ASW: ASW Sales item: RU00436 Smart LTE Handover LK License control in network element: RNC LK License control attributes: Long-term ON/OFF licence

2.1.2 WCDMA and GSM Layer Priorities


Summary: This feature allows idle mode traffic steering according to priorities given for WCDMA and GSM layers.

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 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 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 quality thresholds broadcast in SIB 19.

For WCDMA and GSM priority-based cell reselection these thresholds are specified in 3GPP Rel8.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

Current Implementation: Similar mechanism is available for LTE layer priorization with LTE Interworking feature.

Interdependencies between Features: Hierarchical Cell Structure can not be used simultaneously with this feature.

HW Requirements: This feature does not require any new or additional HW.

Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: Support not required BTS Flexi: Support not required SGSN: Support not required BTS Flexi 10: Support not required MGW: Support not required UE: 3GPP Rel-8

SW Sales Information: BSW/ASW: ASW Sales item: RU00529 WCDMA and GSM Layer Priorities LK License control in network element: RNC LK License control attributes: Long-term ON/OFF licence

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

2.1.3 Measurement based LTE Layering


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: 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:

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.

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 reservations for PS services:

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

Both FDD-LTE and TDD-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 support for LTE cell re-selection in idle, Cell_PCH and URA_PCH states.

For HSUPA compressed mode measurements RAN1668 is required.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1


Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: Support not required BTS Flexi: WBTS9.0 SGSN: Support not required BTS Flexi 10: WBTS9.1 MGW: Support not required UE: 3GPP Rel-8

SW Sales Information: BSW/ASW: ASW Sales item: RU00539 Measurement based LTE Layering LK License control in network element: RNC LK License control attributes: Long-term ON/OFF licence

2.1.4 RSRQ-based LTE Reselection


Summary: RSRQ based LTE cell reselection is supported.

Benefits for the Customer: Maximise LTE user experience. Smooth WCDMA-LTE interworking in 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-UTRA neighbor cell RSRQ quality thresholds.

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

Current Implementation: RAN2067 LTE Interworking feature supports RSRP based LTE reselection.

Interdependencies between Features: This feature requires RAN2067 LTE Interworking feature.


Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: - BTS Flexi: - SGSN: - BTS Flexi 10: Support not required MGW: - UE: 3GPP Rel-9

SW Sales Information: BSW/ASW: ASW Sales item: This feature is included in the same sales item

with RAN2067 LTE interworking. License control in network element: The same license with RAN2067 LTE

interworking. License control attributes: Not defined

2.2 Admission Control

2.2.1 RRC Connection Setup Redirection


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: Better subscriber experience due to less call setup delay in case of congestion.

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-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 balancing in very early phase by employing RRC Connection Setup Rejection message and 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 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 UEs also exact cell where cell selection 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.

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.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

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 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 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 directing UEs to WCDMA or GSM, or to both.

Existing neighbor cell list is used for selecting target cell. The algorithm also checks that target cell is not already high loaded.

If RRC: Establishment cause is "Inter-RAT cell re-selection" or "Inter-RAT cell change order" target system cannot be GSM.

Current Implementation: -

Interdependencies between Features: -

HW Requirements: -

Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: - BTS Flexi: - SGSN: - BTS Flexi 10: - MGW: - UE: -

SW Sales Information: BSW/ASW: ASW Sales item: RU00527 RRC Connection Setup Redirection LK License control in network element: RNC LK License control attributes: Long-term ON/OFF licence

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

2.3 HSPA Mobility

2.3.1 HSUPA Compressed Mode for LTE and Inter-frequency Handover


Summary: This feature introduces HSUPA compressed mode measurement for 3G to LTE redirection and PS HO. Also HSUPA compressed mode measurement for inter-frequency handover 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-frequency measurement is 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-DCH. This includes also the 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- 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 measurement based 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: Currently inter-frequency HSPA mobility is performed by switching the 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 DCH and vice versa is supported with HSDPA Dynamic Resource Allocation feature.

For the case of SRB standalone with DCH on DL and HSPA on UL currently no interfrequency measurements are performed.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

Interdependencies between Features: 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.

Operational Aspects: In order to distinguish HSUPA-handovers new counters are introduced. Also new HSUPA Compressed Mode-counters are introduced.


Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: Support not required BTS Flexi: WBTS9.0 SGSN: Support not required BTS Flexi 10: WBTS9.1 MGW: Support not required UE: 3GPP Rel-6

SW Sales Information: BSW/ASW: ASW Sales item: RU00533 HSUPA Inter-frequency Handover LK License control in network element: RNC LK License control attributes: Long-term ON/OFF licence

2.4 Capacity and Efficiency

2.4.1 Dual Band HSDPA 42 Mbps


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: 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-away UEs mainly use low 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 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

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

not be non-adjacent frequencies on same band. Also UL is restricted to single carrier HSUPA, DB or DC-HSUPA 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-HSDPA to combine the gain of normal DC-HSDPA scheduling and the 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 adjacent carriers on same frequency band.

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.

HW Requirements: This feature requires RAN1016/RAN1848: Flexi BTS Multimode System Module. For RNC196 and RNC450, RAN2261 Flexible User Plane Capacity in RNC196 and RNC450 is required.

Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: Support not required BTS Flexi: WBTS9.0 SGSN: SG8.0 BTS Flexi 10: WBTS9.1 MGW: Support not required UE: 3GPP Rel-9

SW Sales Information: BSW/ASW: ASW Sales item: RU00432 Dual-Band HSDPA LK License control in network element: RNC LK License control attributes: Long-term capacity licence

2.4.2 Data Session Profiling


Summary: 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

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

channels. For small 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 Cell_DCH is ~1s faster when Cell_FACH state is skipped.

Shorter Cell_DCH state inactivity timers can be used, as direct Cell_PCH - Cell_DCH allocation is 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. 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 cell

- More smartphone keep-alive -type packets are expected on Cell_FACH

- 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-RACH capable UEs.

Current Implementation: This is a new feature.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

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


Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: NetAct 8 EP1 mcRNC: mcRNC4.1 MSC: Support not required BTS Flexi: Support not required SGSN: Support not required BTS Flexi 10: Support not required MGW: Support not required UE: Support not required

SW Sales Information: BSW/ASW: ASW Sales item: RU00521 Data Session Profiling LK License control in network element: RNC LK License control attributes: Long-term ON/OFF licence

3 Transmission & Transport

3.1 IP Transport

3.1.1 Performance Monitoring Based on ETH Service OAM


Summary: 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-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.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

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 following:

- Frame Loss Measurement both dual ended (ETH-CCM) and single-ended (ETH-LM)

- Frame Delay Measurement (ETH-DM): Two-way Delay and One-way Delay Variation 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 intermediate points (MIPs) to 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-end and far-end frame loss measurement 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 measurement which uses dual-ended frames (ETH-CCM)

- Single-ended ETH-LM: on-demand measurement which uses single-ended ETH-LM frames (ETH-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-way delay, 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 thresholds for the two-way delay and 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-to-point ETH connections. The measurement results are only accurate when the network configuration is modeled as point-to-point ETH connections between the measurement MEPs (Maintenance Association End Points).

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

Current Implementation: RAN1900 "IP Transport Network Measurements" made available in RU30 - dependent on transport networks scenario - serves similar purpose for measurement on L3 level.

Interdependencies between Features: Requires RAN1880 "Ethernet OAM" and RAN1900 "IP Transport Network Measurements".

HW Requirements: Requires NPGE in RNC and Ethernet-enabled Transport Sub-Modules in BTS

BTS Transport HW: Flexi FTIA

BTS Transport HW: Flexi FTJA

BTS Transport HW: Flexi FTIB

BTS Transport HW: Flexi FTLB

BTS Transport HW: Flexi FTFB

BTS Transport HW: Flexi Multiradio System Module without Transport Sub-Module

BTS Transport HW: Flexi Multiradio System Module with FTIF

Software Dependencies for RU50: IPA-RNC: Support not required NetAct: NetAct 8 EP1 mcRNC: Support not required MSC: Support not required BTS Flexi: WBTS9.0 SGSN: Support not required BTS Flexi 10: WBTS9.1 MGW: Support not required UE: Support not required

SW Sales Information: BSW/ASW: ASW Sales item:

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

License control in network element: TRS LK License control attributes: Long-term ON/OFF licence

4 Operability

4.1 Network Monitoring and Maintenance

4.1.1 BTS Event Triggered Symptom Data Collection


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: 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 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. User can also set the threshold which defines how many times the fault is set until symptom data collection is started.

For faults triggering BTS reset, symptom data is lost during reset.

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 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 data file is ready.

Old symptom data files are deleted automatically.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1


Software Dependencies for RU50: IPA-RNC: RN8.0 NetAct: Support not required mcRNC: mcRNC4.1 MSC: Support not required BTS Flexi: WBTS9.0 SGSN: Support not required BTS Flexi 10: WBTS9.1 MGW: Support not required UE: Support not required

SW Sales Information: BSW/ASW: BSW Sales item: License control in network element: Not defined License control attributes: Not defined

4.2 Configuration Management

4.2.1 Transport Configuration Fall-back


Summary: 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 Multiradio BTS availability due to less outages.

Functional Description: Autonomous fallback to previous configuration:

A fallback to the previous configuration happens when after a remote configuration update and activation the BTS fails to (re)connect successfully to the RNC-OMU. 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 one 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.

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

Current Implementation: none

Interdependencies between Features: none


Software Dependencies for RU50:

IPA-RNC: Support not required NetAct: Support not required mcRNC: Support not required MSC: Support not required BTS Flexi: WBTS9.0 SGSN: Support not required BTS Flexi 10: WBTS9.1 MGW: Support not required UE: Support not required

SW Sales Information: BSW/ASW: ASW Sales item: RAN2554LKC Transport configuration fallback LK License control in network element: BTS LK License control attributes: Not defined

Prepared by

Date 16.10.2013

/23


Approved by

Doc number

Version 1.1

5 BTS Solution

5.1 Flexi WCDMA BTS Site Solutions and Features

5.1.1 Additional 6 WCDMA Cell Activation


Summary: Additional 6 WCDMA cell activation license key enables increase of supported cells in BTS configuration.

Benefits for the Customer: More than 12 cells per BTS site is typically needed in case of 6 sector, MORAN or multi-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: 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: Current RAN2736LK - 18 cell BTS License Key is replaced by this feature. RAN3017LK - 6 WCDMA cell activation License key must be used if BTS site configuration has more than 12 cells.

Interdependencies between Features: -


Software Dependencies for RU50: IPA-RNC: - NetAct: - mcRNC: - MSC: Support not required BTS Flexi: WBTS9.0 SGSN: Support not required BTS Flexi 10: WBTS9.1 MGW: - UE: Support not required

SW Sales Information: BSW/ASW: ASW

Sales item: RAN3017LK License control in network element: BTS LK License control attributes: Long-term capacity licence

FUD_RU50_11

Documents

Transcript of FUD_RU50_11