RU50 Feature Descriptions of NSN

1 Introduction to RU50 features

1.1 RU50 radio resource management featuresSee the following table for more detailed information on WCDMA RAN functions andfeature activation:

RU50 features

Table 1 RU50 radio resource management features

Feature

Other related descriptions

Related instructions

RAN2963: Data Session Profiling WCDMA RAN RRM Packet Scheduler

WCDMA RAN Packet Data TransferStates

Activating RAN2963: Data SessionProfiling

RAN2179: Dual Band HSDPA 42 Mbps WCDMA RAN HSDPA in BTS

WCDMA RAN RRM Handover Control

WCDMA RAN RRM HSDPA

WCDMA RAN RRM HSUPA

Activating RAN2179: Dual BandHSDPA 42 Mbps

RAN2482: Enhanced Virtual AntennaMapping

This information will be provided infuture deliveries.

Activating RAN2482: Enhanced VirtualAntenna Mapping

RAN1668: HSUPA Compressed Modefor LTE and Inter-frequency Handover


WCDMA RAN RRM HSUPA

WCDMA RAN SRNS Relocation

Activating RAN1668: HSUPACompressed Mode for LTE and Inter-frequency Handover

RAN2980: Measurement Based LTELayering

WCDMA RAN RRM HSUPA Activating RAN2980: MeasurementBased LTE Layering

RAN147: RRC Connection SetupRedirection

WCDMA RAN RRM Admission Control


WCDMA RAN RRM HSDPA

WCDMA RAN RRM HSUPA

RNC Overload Control

WCDMA RAN Call Setup and Release

Activating RAN147: RRC ConnectionSetup Redirection

RAN3069: RSRQ-based LTEReselection



Activating RAN3069: RSRQ-based LTEReselection

RAN2264: Smart LTE Handover WCDMA RAN RRM Handover Control

WCDMA RAN RRM HSUPA

Activating RAN2264: Smart LTEHandover

Introduction to RU50 features RU50 Feature Descriptions and Instructions

14 DN09146788 Issue: 01

Table 1 RU50 radio resource management features (Cont.)

Feature



WCDMA RAN SRNS Relocation

RAN2881: WCDMA and GSM LayerPriorities



Activating RAN2881: WCDMA andGSM Layer Priorities

1.2 RU50 telecom featuresThere are no RU50 features in the Telecom area.

1.3 RU50 transmission and transport featuresSee the following table for more detailed information on WCDMA RAN functions andfeature activation:

RU50 features

Table 2 RU50 transmission and transport features

Feature



RAN2243: Performance MonitoringBased on ETH Service OAM

WCDMA RAN IP Transport Activating RAN2243: PerformanceMonitoring Based on ETH Service OAM

1.4 RU50 operability featuresSee the following table for more detailed information on WCDMA RAN functions andfeature activation:

RU50 features

Table 3 RU50 operability features

Feature



RAN2199: BTS Event TriggeredSymptom Data Collection

This feature does not have any relateddescriptions.

Activating RAN2199: BTS EventTriggered Symptom Data Collection

RAN2554: Transport Configuration Fall-back


Activating RAN2554: TransportConfiguration Fall-back

RU50 Feature Descriptions and Instructions Introduction to RU50 features

Issue: 01 DN09146788 15

1.5 RU50 performance monitoring featuresThere are no RU50 features in the performance monitoring area.

1.6 RU50 RNC solution featuresSee the following table for more detailed information on WCDMA RAN functions andfeature activation:

RU50 features

Table 4 RU50 RNC solution features

Feature



RAN3047: RTT Improvement toenhance user experience

This feature does not have relateddescriptions.

This feature does not have relatedinstructions.

1.7 RU50 BTS solution featuresSee the following tables for more detailed information on WCDMA RAN functions andfeature activation:

RU50 features

Table 5 RU50 BTS solution features

Feature



RAN3017: Additional 6 WCDMA CellActivation


Activating RAN3017: Additional 6WCDMA Cell Activation

1.8 LicensingThe application software features (ASW) are under license key management. A licenseis a file that includes the feature information. Before a licensed feature can be activated,the license file needs to be transferred to and installed in the IPA-RNC. For informationon transferring the license, see License management operations in RNC in WCDMARAN License Operation. For information on installing the license, see Installing licensesin the network element in Managing License-based Features in IPA-RNC and ManagingLicense-based Features in Multicontroller RNC.


16 DN09146788 Issue: 01

g Some RNC-controlled features are activated using an RNC general parameterfile (PRFILE) or a feature information control file (FIFILE). For details, seeParameter-based option management in WCDMA RAN License Operation.

g There are no licenses in the Flexi Direct RNC.A license can be installed using NetAct or a local MML (IPA-RNC) or SCLI (mcRNC)interface. If it is installed using NetAct, the licensed feature state is automatically set toON state. If the MML/SCLI interface is used, the default value is OFF, and you need toset the feature to ON state manually. For information on feature states, see FeatureStates in WCDMA RAN License Operation. The license-related MML commands aredescribed in W7 - License and Feature Handling.

License management in mcRNCFor details on the mcRNC-specific license management, see License management inRNC in WCDMA RAN License Operation and Managing License-based Features inMulticontroller RNC.

License management in WBTSLicense management in WBTS is based on a pool concept. Each license contains aspecific amount of capacity that can be distributed among the selected WBTSs.Distributing licenses from the pool license decreases the amount of free capacity in thepool. Managing pool licenses and distributing to WBTSs is done via NetAct LicenceManager. Some basic license operations (for example, license installation or deletion)are also possible with BTS Site Manager.

For details on the WBTS-specific license management, see License management inWBTS in WCDMA RAN License Operation.

1.9 Reference documentationFor information on the parameters, counters and alarms related to each feature, see theManagement data section of the feature descriptions.

For parameter descriptions, see:

WCDMA Radio Network Configuration Parameters Excel in WCDMA RAN OperatingDocumentation, Parameters in NOLS PIC

IP Configuration Plan Interface Parameters for Multicontroller RNC Excel in WCDMARAN Operating Documentation, Parameters in NOLS PIC

OMS LDAP parameters Flexi Transport Module Parameters Excel in WCDMA RAN Operating

Documentation, Parameters in NOLS PIC Flexi Multiradio BTS WCDMA Parameters Excel in WCDMA RAN Operating

Documentation, Parameters in NOLS PIC Multicontroller Radio Network Configuration Parameters Excel in WCDMA RAN

Operating Documentation, Parameters in NOLS PIC ATM Configuration Plan Interface Parameters Excel in WCDMA RAN Operating

Documentation, Parameters in NOLS PIC Frequently Used Parameters for SS7 signalling over IP

RU50 Feature Descriptions and Instructions Introduction to RU50 features

Issue: 01 DN09146788 17

IP Configuration Plan Interface Parameters for Flexi Direct RNC Excel in WCDMARAN Operating Documentation, Parameters in NOLS PIC

Radio Network Parameters in Flexi Direct Excel in WCDMA RAN OperatingDocumentation, Parameters in NOLS PIC

Reference Information Service in NOLS for RNC parameters

For counter descriptions, see:

RNC Counters - RNW Part RNC Counters Transport and HW Part WBTS Counters Reference Information Service in NOLS

For alarm descriptions, see:

IPA-RNC Notices (0-999) IPA-RNC Disturbances (1000-1999) IPA-RNC Failure Printouts (2000-3999) IPA-RNC Diagnosis Reports (3700-3999) Multicontroller RNC, IPA-RNC and Flexi Direct RNC Base Station Alarms (7000-

9000) Flexi WCDMA Base Station Faults OMS Alarms

For key performance indicator descriptions, see:

WCDMA RAN Key Performance Indicators


18 DN09146788 Issue: 01

2 Radio resource management features

2.1 RAN2963: Data Session Profiling2.1.1 Description of RAN2963: Data Session Profiling

Introduction to the featureThe RAN2963: Data Session Profiling feature provides faster web browsing session forend user.

2.1.1.1 Benefits

End-user benefitsThis feature enables fast web browsing to the end user.

Operator benefitsThis feature benefits the operator as follows:

It allows operators to use higher thresholds for common channels. Keep-alive-typesignaling is moved to common channels, more HSPA resources are available fordata, what impacts end-user experience and increases satisfaction.

It allows for the usage of the Shorter Cell_DCH state inactivity timers, resulting in thefaster direct Cell_PCH - Cell_DCH allocation, what improves HSPA efficiency.

The large amounts of data sent in short time period are allocated to HSPA directly. Inthis case Cell_FACH state is skipped, and state change from Cell_PCH to Cell_DCHis approximately one second faster.

2.1.1.2 Requirements

Software requirementsTable 6: Software requirements lists the software required for this feature.

RAS Flexi Direct IPA-RNC mcRNC Flexi DirectRNC

OMS BTS Flexi

RU50 Planned forlater release

RN8.0 Planned forlater release

Planned forlater release

OMS3.0(RU50)

Support notrequired

Table 6 Software requirements

Flexi LiteBTS

BTS Flexi10

NetAct MSC SGSN MGW UE

Support notrequired

Support notrequired

NetAct 8EP1

Support notrequired

Support notrequired

Support notrequired

Support notrequired

Hardware requirementsThis feature requires no new or additional hardware.

RU50 Feature Descriptions and Instructions Radio resource management features

Issue: 01 DN09146788 19

2.1.1.3 Functional description

Functional overviewThe RAN2963: Data Session Profiling feature aims to provide faster web browsing. Thisis achieved by moving the terminal directly to the Cell_DCH, even though the initial dataamount suggests allocation to the Cell_FACH - the amount of data is below the RNPS -TrafVolThresholdULLow parameter.

When the large data amount is identified in the session (the LargeDataThr parametervalue is exceeded), after the end of the session (when the UE is moved to theCell/URA_PCH state), the timer defined by the LargeDataTime parameter is started.

The UE, being in the Cell/URA_PCH state, starts next data session by sending the RRC:CELL UPDATE message with cell update cause set as uplink data transmission. Whenthe time defined by the LargeDataTime parameter is not exceeded, the UE is moveddirectly to the Cell_DCH state, with the RRC: CELL UPDATE CONFIRM message. Aftersuccessful procedure, when the RRC: RADIO BEARER RECONFIGURATIONCOMPLETE message is successfully received from UE, the RNC updates theM1006C309: SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSIONPROFILING counter, if TVI is not set as TRUE in RRC: CELL UPDATE message.

The amount of data (LargeDataThr) and the time period (LargeDataTime) are theparameters defined by the operator.

The fast state change is performed both for sending and receiving data.

For the UEs capable of using the HS-RACH, an RNPS- HSChaPrefInDataSesProfparameter is used. It allows either a direct transfer the Cell_DCH state or staying in theCell_FACH state and using HS-RACH/FACH channels provided the data sessionprofiling conditions.

For proper functioning of the RAN2963 feature, please mind the following parameterconfiguration:

RNFC-DCHtoPCHEnabled should be set to its default value - enabled. RNFC-CUCforPCHtoDCHallowed should be set to its default value - true. WAC-MSActivitySupervision should be set to the value > 0.

2.1.1.4 System impact

Interdependencies between feature RAN1913: High Speed Cell_FACH

The feature enables a special handling for HS-RACH capable UE. If preferred, thefeature can be disabled for HS-RACH capable UEs withHSChaPrefInDataSesProf parameter.

RAN2494: Fast Cell_PCH SwitchingThis feature is recommended to be used with the Data Session Profiling feature. Ithelps in achieving faster state changes to the Cell_DCH state.

Impact on interfacesThis feature has no impact on interfaces.

Radio resource management features RU50 Feature Descriptions and Instructions

20 DN09146788 Issue: 01

Impact on commandsThere are no commands related to this feature.

Impact on network and network element management toolsThis feature has no impact on network management or network element managementtools.

Impact on system performance and capacityState transmission from the Cell_PCH to Cell_DCH is approximately one second faster.

2.1.1.5 RAN2963: Data Session Profiling management data

For information on alarm, counter, key performance indicator, and parameter documents,see Reference documentation.

AlarmsThere are no alarms related to this feature.

Measurements and countersTable 7: New counters lists counters introduced with this feature.

Table 7 New counters

Counter ID

Counter name

Measurement

M1006C309 SUCCESSFUL PCH TO DCH TRANS DUETO DATA SESSION PROFILING

RRC signalling (RNC)

Table 8: Related existing counters lists existing counters related to this feature.

Table 8 Related existing counters

Counter ID

Counter name

Measurement

M1006C174 STATE TRANSITION TIME PCH TO DCH RRC signalling (RNC)

M1006C175 DENOMINATOR FOR STATE TRANSITIONTIME PCH TO DCH


M1006C196 ATTEMPTED PCH TO DCH TRANSITIONSUSING UM-RLC


M1006C197 SUCCESSFUL PCH TO DCHTRANSITIONS USING UM-RLC


M1006C198 CELL RESELECTIONS DURING PCH TODCH TRANSITIONS USING UM-RLC



Issue: 01 DN09146788 21

Key performance indicatorsThere are no key performance indicators related to this feature.

ParametersTable 9: New parameters lists parameters introduced with this feature.

Table 9 New parameters

Full name

Abbreviated name

Managed object

Data Session Profiling Enabled DataSessionProfEnabled RNFC

Large DataThreshold LargeDataThr RNPS

Large Data Time LargeDataTime RNPS

HS-RACH/FACH Preferred in DataSession Profiling

HSChaPrefInDataSesProf RNPS

Table 10: Modified parameters lists parameters modified by this feature.

Table 10 Modified parameters

Full name

Abbreviated name

Managed object

RNCOptions RncOptions RNC

Uplink traffic volume measurement lowthreshold

TrafVolThresholdULLow RNPS

UL traffic volume threshold forSmartphone

SmartTrafVolThrUL WCEL

Downlink traffic volume measurementlow threshold

TrafVolThresholdDLLow WCEL

DL traffic volume threshold forSmartphone

SmartTrafVolThrDL WCEL

Downlink NAS signalling volumethreshold

NASsignVolThrDL WCEL


22 DN09146788 Issue: 01

2.1.1.6 Sales information

Table 11 Sales information

BSW/ASW

SW component

License control in network element

ASW RAN RNC LK

2.1.2 Activating RAN2963: Data Session ProfilingPurpose

Follow this procedure to activate this feature.

For more information on the feature, see the RAN2963: Data Session Profiling FeatureDescription.

Before you start

Restart of the RNC is not required after the activation of this feature.

This procedure does not require cell locking.

This procedure does not cause downtime, and it can be activated at any time of the day.

Make sure you have access to the following applications:

OMS Element Manager Application Launcher

This feature is controlled by a license. For information on managing licenses, seeLicensing.

To set the feature state to ON, use the following command:

for IPA-RNC:ZW7M: FEA=4654:ON;

The following feature is recommended to be activated/configured before activation ofRAN2963: Data Session Profiling feature:

RAN2494: Fast Cell_PCH Switching RAN1232: Fast Call Setup from Cell_PCH State

The following parameters need to be set as follows:

The WAC-MSActivitySupervision must be set to non-zero value, to allow theCell_PCH Data Session Profiling to function.

The RNFC-CUCforPCHtoDCHallowed parameter must be set to its default value -true - to allow the Data Session Profiling to function.

The following parameter is suggested to be set as follows:

The RNFC-DCHtoPCHEnabled is suggested to be set to the value 1 (enabled).


Issue: 01 DN09146788 23

1 Open the OMS Element Manager.

2 Go to the Topology Tree View.Select: Network Management Topology Tree View

3 Expand the RNFC object.

4 Configure the RNFC object.a) From the drop-down menu select Edit Parameters.

b) Set the DataSessionProfEnabled parameter value to Enabled.

5 Save the changes.a) Click the Apply button.

The RNFC - DataSessionProfEnabled parameter is visible as Enabled in the OMsElement Manager and as a result the feature RAN2963: Data Session Profiling isactivated.

2.1.3 Verifying RAN2963: Data Session ProfilingPurpose

Follow this procedure to verify that this feature works properly in the network.

1 Activate measurement M1006In the Application Launcher, activate the measurement M1006 and set themeasurement interval to 15 minutes.

2 Start the PS session with the smartphone.It can be internet-browsing, mailbox checking. The transmitted data amount must behigher then the value specified in the LargeDataThr parameter

3 During the session make pauses.During the data session make pauses, but keep the RRC connection. The pausesmust not be longer than the time value defined in the LargeDataTime parameter.

4 Resume the user-data transmission.After the pause, when the UE was moved from the Cell_DCH to Cell_PCH, renewthe user-data transmission. Even little data amount is sufficient for the purposes ofthe veneration process.The data transmission must not be longer than the time valuedefined in the LargeDataTime parameter.


24 DN09146788 Issue: 01

5 Open the Application Launcher

6 Use the RNW measurement management application to start measurements ofthe Cell_PCH to Cell_DCH transitions due to data session profiling counterThe value of the counter M1006C309 (SUCCESSFUL PCH TO DCH TRANS DUETO DATA SESSION PROFILING) should be larger than 0, that implies that the directtransmission from the Cell_PCH to Cell_DCH state occurred.

2.1.4 Deactivating RAN2963: Data Session ProfilingPurpose

Follow this procedure to deactivate this feature.


2 Go to the Topology Tree View.Select: Network Management Topology Tree View

3 Expand the RNFC object.

4 Configure the RNFC object.a) From the drop-down menu select Edit Parameters.

b) Set the DataSessionProfEnabled parameter value to Disable.

5 Save the changes.

a) Click the Apply button.

2.2 RAN2179: Dual Band HSDPA 42 Mbps2.2.1 Description of RAN2179: Dual Band HSDPA 42 Mbps

Introduction to the featureWith RAN2179: Dual Band HSDPA 42 Mbps, it is possible to use Dual Cell HSDPA withtwo carriers located in different frequency bands (example: Carrier 1 in band 2110-2170MHz and Carrier 2 in band 925-960 MHz). Dual Band HSDPA is therefore very similar toDual Cell HSDPA, the only difference is at Layer 1: the carriers are in different frequencybands. For more information on Dual Cell HSDPA, see RAN1906: Dual Cell HSDPA inWCDMA RAN, Rel. RU20, Feature Descriptions.


Issue: 01 DN09146788 25

2.2.1.1 Benefits

End-user benefitsWith this feature, end-user benefits from increased coverage and throughput.

Operator benefitsWith this feature, Dual Cell HSDPA benefits can be obtained even when no contiguous10 MHz frequency allocation is available. Gains are obtained from additional frequencyband. Lower band provides coverage, while higher band provides increased capacityand peak rate. BTS based scheduling enables dynamic resource sharing, so that far-away-UEs mainly use low frequency band, while close-by-UEs mainly use the highfrequency. This approach maximizes the sector coverage and capacity.




RAS

Flexi Direct

IPA-RNC

mcRNC

FlexiDirect RNC

OMS

Flexi BTS

RU50 Planned forlaterreleases

RN8.0 Planned forlaterreleases

Planned forlaterreleases

OMS3.0(RU50)

WN9.0

Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE

Notplanned


NetAct8EP1

Support notrequired

SG8.0 Support notrequired

3GPP Rel-9

Hardware requirementsFor Flexi Multiradio BTS WCDMA this feature requires one of the following features:

RAN2382: Flexi BTS Multimode System Module - FSMC RAN1016: Flexi BTS Multimode System Module - FSMD RAN1848: Flexi BTS Multimode System Module - FSME


With the RAN2179: Dual Band HSDPA 42 Mbps feature data for capable UE isscheduled on two distinct frequency bands in the downlink. With this feature, themaximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available onboth frequencies.


26 DN09146788 Issue: 01

The BTS uses proportional fair scheduling and optimizes the sector coverage andcapacity by favoring the low-frequency band for cell-edge-UEs and the high-frequencyband for UEs, that are closer to the BTS. This allows Dual Band HSDPA to combine thegain of normal Dual Cell HSDPA scheduling and the benefits of low frequency band forfaraway users.

The carrier selection is based both on the UE distance and current load on both uplinkcarriers. The RNC uses the RAN2172: Multi-Band Load Balancing feature for carrierselection.

Figure 1 Two HSDPA carriers located in two different frequency bands.

Table 13: Supported band combinations shows three band combinations supported bythe RAN2179: Dual Band HSDPA 42 Mbps feature.

Table 13 Supported band combinations

Dual Band HSDPAConfiguration

UL Band

DL Band

1 I or VIII I and VIII

2 II or IV II and IV

3 I or V I and V


Issue: 01 DN09146788 27

g Mixed RF module configurations, Rel 1+Rel2 or Rel1+Rel3, cannot be usedwith this feature.2.2.1.4 System impact

Interdependencies between features The RAN1906: Dual Cell HSDPA feature and all its preconditions are prerequisites

for this feature. Use of 64QAM modulation requires the RAN1643: HSDPA 64QAM feature. Licenses for two separate frequency bands in the same NodeB and RNC are

required.

Impact on interfacesRNC and BTS NBAP interface including new IE's in messages:

(BTS -> RNC) Audit Response: BTS informs RNC on DualBand-HSDPA capability

(BTS -> RNC) Resource Status Indication: BTS informs RNC which cell will supportDualBand-HSDPA.

Following NBAP procedures are unchanged between DC-HSDPA and DB-HSDPA:

Radio Link Setup Radio Link Reconfiguration

Changed NBAP procedures between DC-HSDPA and DB-HSDPA: Audit Response andResource Status Indication. These procedures are enhanced with new IE indicating thatNodeB has new DB-capability


Impact on system performance and capacityThe RAN2179: Dual Band HSDPA 42 Mbps feature can double maximum achievablepeak user throughput. It also increases cell capacity (by up to 40%) and cell edgethroughput.

2.2.1.5 RAN2179: Dual-Band HSDPA 42Mbps management data


AlarmsTable 14: Existing alarms lists alarms related to this feature.


28 DN09146788 Issue: 01

Table 14 Existing alarms

Alarm ID

Alarm name

3325 INCONSISTENCY IN CONFIGURATION PARAMETERS

7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG



Counter ID

Counter name

Measurement

M1001C728 UE SUPPORT FOR DB-HSDPA BANDREL9-1

Service Level


Service Level


Service Level

M1006C293 RB SETUP ATTEMPT FOR DB-HSDPA RRC signalling

M1006C294 SUCCESSFUL RB SETUP FOR DB-HSDPA

RRC signalling

M1006C295 RB SETUP FAIL FOR DB-HSDPA DUE TONO REPLY

RRC signalling

M1006C296 RB SETUP FAIL FOR DB-HSDPA DUE TOUE NACK

RRC signalling




Full name

Abbreviated name

Managed object

Dual Band HSDPA Enabled DBandHSDPAEnabled WCEL


Issue: 01 DN09146788 29

Table 16 New parameters (Cont.)

Full name

Abbreviated name

Managed object

Preferred Frequency Layer for DB-DC-HSDPA NRT

PFLDBHSDNRT PFL

Preferred Layer for DB-DC-HSDPA NRT PrefLayerDBHSDNRT PFL

Preferred Frequency Layer for DB-DC-HSDPA Streaming

PFLDBHSDStr PFL

Preferred Layer for DB-DC-HSDPAStreaming

PrefLayerDBHSDStr PFL

Preferred Frequency Layer for DB-DC-HSDPA AMR

PFLDBHSDAMR PFL

Preferred Layer for DB-DC-HSDPA AMR PrefLayerDBHSDAMR PFL

Preferred Frequency Layer for DB-DC-HSDPA AMR and NRT

PFLDBHSDAMRNRT PFL

Preferred Layer for DB-DC-HSDPA AMRand NRT

PrefLayerDBHSDAMRNRT PFL



Full name

Abbreviated name

Managed object

DC HSDPA Enabled DCellHSDPAenabled WCEL

Dual Cell versus MIMO preference DCellVsMIMOPreference RNC

Frame timing offset of a cell Tcell WCEL



BSW/ASW

SW component


ASW RAN RNC LK


30 DN09146788 Issue: 01

2.2.2 Activating RAN2179: Dual Band HSDPA 42 MbpsPurpose


Before you start

A restart of the RNC and the BTS is not required after the activation of this feature.

This procedure requires cell locking.


OMS Element Manager Application Launcher Man-machine interface (MMI)

Make sure that:

RAN1906: Dual-Cell HSDPA 42 Mbps feature is activated in the RNC. Dual Cell HSDPA must be activated to those cells that are going to be used for Dual

Band HSDPA. Used cells must be configured to those bands that are supported for Dual Band

HSDPA. Used frequencies (in two bands) must be handed with the same HSDPA scheduler

(similar to Dual Cell HSDPA uses frequencies in one band that must be handled withthe same scheduler).

For the allowed band combinations for Dual Band HSDPA, see Table 19: Allowed bandcombinations for Dual Cell and Dual Band HSDPA.

Table 19 Allowed band combinations for Dual Cell and Dual Band HSDPA

Dual Band - Dual CellHSDPA Configuration

Uplink band

Downlinkband

1 I or VIII I and VIII

2 II or IV II and IV

3 I or V I and V

The RAN2179: Dual Band HSDPA 42 Mbps feature is controlled by the capacity licensekey. For more information on licensing, see Licensing.

g The feature code for this feature is 2118.To set the the feature state to ON, use the following command:

for IPA-RNC:ZW7M:FEA=2118:ON;

No license is required in Flexi Direct RNC.


Issue: 01 DN09146788 31


2 Go to the Topology.

3 Expand the ROOT.

4 Expand the RNC object.

5 Expand the WBTS object.

6 Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needsto be activated:a) Select the WCEL object.

b) Select the cell in the WCell(s) table.

c) From the drop-down menu select "State Change State: Lock".

7 Configure the WCEL object:a) Select Edit parameters from the WCEL object.

b) Set the DBandHSDPAEnabled parameter to Enabled.

8 Unlock the WCEL.

9 Repeat the steps 6-8 for all the required cells.

2.2.3 Verifying RAN2179: Dual Band HSDPA 42 MbpsPurpose

Follow the procedure below to verify that the activation of the RAN2179: Dual BandHSDPA 42Mbps feature has been successful.


32 DN09146788 Issue: 01

1 Perform the RRC connection setup with UE that supports Dual Band HSDPAand send some data.

2 Open the RNW measurement management application from ApplicationLauncher.

3 Use the RNW measurement management application to start measurementsM1006 Traffic with 15 minute interval.Alternatively the measurement can be started using NetAct Administration ofMeasurements Application.Wait until the measurement interval starts.

4 After the measurement data has been collected, use the RNW Measurementpresentation GUI to check if any of the following counters has value greaterthan 0.

M1006C293 - RB SETUP ATTEMPT FOR DB-HSDPA M1006C294 - SUCCESSFUL RB SETUP FOR DB-HSDPA M1006C295 - RB SETUP FAIL FOR DB-HSDPA DUE TO NO REPLY M1006C296 - RB SETUP FAIL FOR DB-HSDPA DUE TO UE NACK M1001C728 - UE SUPPORT FOR DB-HSDPA BAND REL9-1 M1001C729 - UE SUPPORT FOR DB-HSDPA BAND REL9-2 M1001C730 - UE SUPPORT FOR DB-HSDPA BAND REL9-3

Expected outcome

Values of counters M1006C293 and M1006C294 are updated by a normal DB call setup,and value of counter M1006C295 or M1006C296 is updated by related failure RB setupscenarios.The approximate throughput is 42 Mbit/s. The RAN2179: Dual Band HSDPA42Mbps feature has been activated successfully.

2.2.4 Deactivating RAN2179: Dual Band HSDPA 42 MbpsPurpose



Issue: 01 DN09146788 33



3 Expand the ROOT.


5 Expand the WBTS object.

6 Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needsto be activated:a) Select the WCEL object

b) Select the cell in the WCell(s) table.

c) From the drop-down menu select "Start Change state: Lock".

7 Configure the WCEL object:a) Select Edit parameters from the WCEL object.

b) Set the DBandHSDPAEnabled parameter to Disabled

8 Unlock the WCEL.

9 Repeat the steps 6-8 for all the required cells.

Further information

g A restart of the RNC and the BTS is not required after the deactivation of thisfeature.

2.3 RAN2482: Enhanced Virtual Antenna Mapping2.3.1 RAN2482: Enhanced Virtual Antenna Mapping

Introduction to the featureWith the Virtual Antenna Mapping the WCDMA or HSDPA downlink signals, either non-MIMO or MIMO, are all sent from two physical antennas using a virtual antenna mappingmatrix between the virtual antennas and physical antennas. The RAN2482: EnhancedVirtual Antenna Mapping feature tunes the phase difference between the two physicalantennas to obtain the best signal quality for HSDPA.


34 DN09146788 Issue: 01

2.3.1.1 Benefits

End-user benefitsThe end user benefits from an enhanced application experience because of higherHSDPA DL throughput.

Operator benefitsThe operator benefits from higher average DL throughput for HSDPA users, and thushigher average cell throughput.


Software requirementsTable 20: Software requirements lists software required for this feature.


RAS

Flexi Direct

IPA-RNC

mcRNC

Flexi DirectRNC

OMS

Flexi BTS

RU50 Not planned RN8.0 Planned forlaterreleases

Not planned OMS3.0(RU50)

WN9.0

Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE



NetAct 8EP1

Support notrequired

Support notrequired

Support notrequired

Supportnotrequired


RAN2382: Flexi BTS Multimode System Module - FSMC RAN1016: Flexi BTS Multimode System Module (FSMD) RAN1848: Flexi BTS Multimode System Module - FSME

This feature also requires double Tx and double antenna lines per sector. For supportedBTS configurations, see Flexi Multiradio BTS WCDMA Supported and PlannedConfigurations Excel in NOLS.


Virtual Antenna Mapping (VAM) was introduced with the feature RAN1642: MIMO and itcan be used in cells with two Tx like in physical MIMO configuration. With the VAM thecell area is covered with two physical antennas using virtual antenna mapping betweenphysical and virtual antennas. The mapping can be used for MIMO and non-MIMO


Issue: 01 DN09146788 35

configurations. However, VAM solution provides more efficient MIMO performance bytransmitting to non-MIMO UEs without transmit diversity but by Virtual Antenna Mappingfor power balancing. VAM is beneficial for adding power of two power amplifiers insteadof one and introducing polarization diversity when the cross-polarized base stationantennas are used.

The RAN2482: Enhanced Virtual Antenna Mapping (E-VAM) feature improves theperformance of VAM by controlling the phase difference between the physical antennas.The RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase differencebetween the two physical antennas to obtain the best signal quality for HSDPA. Thechannel quality indicators of active non-MIMO UEs in the cell are used to obtain the bestphase difference between the two physical antennas. Tuning of the phase offset isdynamic and automatic. The best benefits are obtained for UEs with one Rx.

The E-VAM can be activated only in cells with two Tx. Cell restart is required wheneverthe RAN2482: Enhanced Virtual Antenna Mapping feature is activated or deactivated.


Interdependencies between featuresThere is no interdependencies with other features.

Virtual Antenna Mapping (VAM) has to be configured in the cells prior to E-VAMactivation.


Impact on MML commandsThere are no MML commands related to this feature.


Impact on system performance and capacityThe feature increases the DL cell throughput.

2.3.1.5 RAN2482: Enhanced Virtual Antenna Mapping management data



Measurements and countersThere are no measurements and counters related to this feature.


36 DN09146788 Issue: 01




Full name

Abbreviated name

Managed object

EVAM in use EVAMInUse WCEL

Sweep time EvamTSweep WCEL

Keep time EvamTKeep WCEL

Phase offset amount EvamNumPhaseOffset WCEL

Initial Phase Offset EvamDInit WCEL

EVAM Capability EVAMCapability WCEL



BSW/ASW

RAS SW component

License control in networkelement

ASW RAN RNC LK

2.3.2 Activating RAN2482: Enhanced Virtual Antenna MappingPurpose

Follow this procedure to activate RAN2482: Enhanced Virtual Antenna Mapping feature.

Configuring Virtual Antenna Mapping

Before you start

Before activating the RAN2482: Enhanced Virtual Antenna Mapping feature, VirtualAntenna Mapping (VAM) needs to be configured first. The VAM is configured via BTSSite Manager only in MIMO-capable BTSs. After VAM configuration, BTS restart isrequired.

Although VAM was introduced with the RAN1642: MIMO feature, it does not require alicense to be configured.

Make sure you have access to the BTS Site Manager.


Issue: 01 DN09146788 37

1 Start the WCDMA BTS Site Manager application and establish the connectionto the BTS.Flexi Multiradio BTS WCDMA is able to autonomously request for missing licensefile(s) from the NetAct License Manager during the RAN2131: Automatic LicenceDistribution to Flexi BTS feature activation.Make sure that you have selected Automatic licensing in use checkbox in theAutomatic License Distribution Settings page.

g If the RAN2131: Automatic Licence Distribution to Flexi BTS feature is notactivated, the relevant license must be uploaded manually.

2 Upload the configuration plan file from the BTS.When BTSSM is connected to the BTS, it automatically uploads the currentconfiguration plan file from the BTS.

Select View Commissioning or click Commissioning on the View bar.

3 Configure Virtual Antenna Mapping in a cell.

a) In Commissioning, go to Local Cell Resources page and assign two Tx outputsfor a single cell to make MIMO settings section appear.

b) In MIMO settings section, select the Virtual antenna mapping in use checkboxand choose MIMO type from the drop-down list.

g Please note, that following this step allows to configure VAM only in onespecific cell. To configure VAM in multiple cells, run this step on each cellseparately.

4 Send the commissioning plan file to the BTS.Click Send Parameters button.You may save the parameters at this point.

5 The new commissioning plan file is automatically activated in the BTS.BTSSM automatically sends an activation command after finishing the file download.

6 Select Next to complete the commissioning.You can save the commissioning report, if required.

7 Backup commissioning files (if applicable).Select File Backup commissioning filesSave the complete backup commissioning file for further use.

Expected outcome

VAM is configured in chosen cells. Restart the BTS to make changes valid.


38 DN09146788 Issue: 01

Activating Enhanced Virtual Antenna Mapping

Before you start

The RAN2482: Enhanced Virtual Antenna Mapping feature activating procedure doesnot cause downtime and the feature can be activated at any time of the day.



The RAN2482: Enhanced Virtual Antenna Mapping feature is controlled by the long-termcapacity Enhanced Virtual Antenna mapping license key. Capacity license refers to thenumber of cells. For more information on licensing, see Licensing.

g Number of activated cells must not exceed the capacity of theEnhanced Virtual Antenna mapping license.

g The feature code for this feature is 3732.To set the feature state to ON, use the following command:


g Note that in FlexiDirect RNC there is no need to configure the license.



3 Expand the ROOT.

4 Go to the WCEL object by following the path:RNC object WBTSs folder WBTS object WCELs folder WCEL object

5 Configure the WCEL object:a) Lock the WCEL object.

b) Right-click on the WCEL object and select Edit parameters.

c) Set the EVAM in use (EVAMInUse) parameter to Enabled.The change of the parameter to Enabled consumes the license in terms ofnumber of cells.


Issue: 01 DN09146788 39

d) Unlock the WCEL object.

Expected outcome

The RAN2482: Enhanced Virtual Antenna Mapping feature has been activated in theRNC. After activating the feature, there is no need to reset the RNC or the BTS.

2.3.3 Verifying RAN2482: Enhanced Virtual Antenna MappingPurpose

In a cell which has MIMO hardware capability, E-VAM provides higher average DLthroughput for non-MIMO users and thus higher average cell throughput. Whencompared to VAM, the enhanced VAM is expected to increase stationary one-Rx UEsaverage throughput by at least 10%.

2.3.4 Deactivating RAN2482: Enhanced Virtual Antenna MappingPurpose




3 Expand the ROOT.

4 Go to the WCEL object following the path:RNC object WBTSs folder WBTS object WCELs folder WCEL object

5 Configure the WCEL object:a) Lock the WCEL object.

b) Right-click on the WCEL object and select Edit parameters.

c) Set the EVAM in use (EVAMInUse) parameter to Disabled.The change of the parameter to Disabled frees the license in terms of number ofcells.

d) Unlock the WCEL object.

Further information

g A restart of the RNC and the BTS is not required after the deactivation of thefeature.


40 DN09146788 Issue: 01

2.4 RAN1668: HSUPA Inter-frequency Handover2.4.1 Description of RAN1668: HSUPA Compressed Mode for

LTE and Inter-frequency HandoverIntroduction to the featureThe RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handoverfeature introduces compressed mode measurements with HSPA active without ULchannel type switching to DCH. The feature also introduces basic compressed modesupport for performing measurements related to inter-system handover to LTE.

Without this feature, during inter-frequency handover in HSPA, before compressed modeis started, switching the UL transport channel from HSUPA to DCH is needed. A switchback to HSPA is performed, after inter-frequency handover using UL DCH.

2.4.1.1 Benefits

End-user benefitsThe end-user benefits from fast HSPA inter-frequency handover and higher datathroughput during compressed mode.

Operator benefitsThis feature benefits the operator as follows:

HSPA inter-frequency handover (HO) is done faster when channel type switching toDCH is not needed first

The inter-system handover (ISHO) and redirection from HSPA to LTE becomes morereliable when LTE cells are measured before ISHO or redirection.

This feature reduces signaling for RNC, Iub, BTS, and the UE as channel typeswitching to DCH is not needed.




RAS

Flexi Direct

IPA-RNC

mcRNC

FlexiDirect RNC

OMS

Flexi BTS




Support notrequired

WN9.0


Issue: 01 DN09146788 41

Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE



NetAct8EP1

Support notrequired

Support notrequired

Support notrequired

3GPP Rel-6

Hardware requirementsThis feature requires the following features:

RAN2382: Flexi BTS Multimode System Module - FSMC RAN1016: Flexi BTS Multimode System Module-FSMD RAN1848: Flexi BTS Multimode System Module - FSME


The RAN1668: HSUPA Compressed Mode for LTE and Inter- frequency Handoverfeature introduces HSUPA compressed mode (CM) for LTE and inter-frequencymeasurements, without UL channel type switching to DCH.

HSUPA CM configuration for inter-frequency measurements is achieved using a single-frame method with 7 (or less)-slot transmission gap pattern (TGP). HSUPA CMconfiguration for LTE measurements is achieved using a double-frame method with 7 (ormore)-slot TGP. In NSN implementation the TGP for single frame method is always fixedto 7 slots and for double frame method, the TGP is fixed to 10 slots.

Compressed mode is supported while the radio bearers are mapped to E-DCH in uplinkand SRBs are mapped on DCH or E-DCH. This also includes the case where DL SRB ismapped to DCH or HSDPA.

Avoiding the channel-type switch to UL DCH reduces the total handover execution timeup to 1.5s. Also, the high HSUPA throughput can be experienced during compressedmode.

For inter-system handover to LTE, only the basic HSUPA compressed mode support iscovered in this feature. HSUPA compressed mode for LTE is used by the RAN2980:Measurement based LTE Layering feature and the RAN2264: Smart LTE Handoverfeature. All the control, signaling, and RRM decision making of measurement-basedredirection and PS HO to LTE are included in those features.

g In NSN implementation HSUPA CM is never enabled independently. It is alwaysdone in tandem with HSDPA CM, that is CM is always enabled in bothdirections together

g Note that HSUPA compressed mode is not supported over Iur.2.4.1.4 System impact

Interdependencies between featuresThe RAN1276: HSDPA Inter-frequency Handover feature is a prerequisite for using thisfeature.


42 DN09146788 Issue: 01

The RAN1276: Inter-frequency Handover feature covers the following direct handovercases:

DCH/HSDPA to DCH/HSDPA DCH/HSDPA to HSUPA/HSDPA DCH/HSDPA to DCH/DCH DCH/DCH to DCH/HSDPA DCH/DCH to HSUPA/HSDPA

With the RAN1668: HSUPA Compressed Mode For LTE and Inter-frequency Handoverfeature the following direct handover cases are supported in addition:

HSUPA/HSDPA to DCH/HSDPA HSUPA/HSDPA to HSUPA/HSDPA HSUPA/HSDPA to DCH/DCH

Impact on interfacesHSUPA CM is configured and activated using the following messages:

over Iub:

NBAP: Radio Link Setup Request procedure NBAP: Radio Link Re-configuration Procedure (Synchronized)

over Uu:

RRC: Transport Channel Re-configuration RRC: Physical Channel Re-configuration RRC: Measurement Control (Setup)

HSUPA CM is deactivated using the following messages:

over Iub:

NBAP: Compressed Mode Command NBAP: Radio Link Re-configuration Procedure (Synchronized only)

over Uu:

RRC: Transport Channel Re-configuration RRC: Physical Channel Re-configuration RRC: Measurement Control (Release)

g Note that only messages supported by NSN are listed.Impact on network and network element management toolsThis feature has no impact on network management or network element managementtools.

Impact on system performance and capacityThis feature impacts system performance as follows:


Issue: 01 DN09146788 43

HSPA IFHO is done faster, as channel type switching to DCH is not needed first. ISHO and redirection from HSPA to LTE becomes more reliable, as the LTE cells can

be measured before ISHO or redirection. The UL throughput is impacted since UE cannot transmit on each slot. The reduction

depends on the configured transmission time interval and whether the UE isperforming intra- or inter-system measurement.

This feature impacts system capacity as follows:

Signaling for RNC, Iub, BTS, and UE is reduced, as channel type switching to DCHis not needed for enabling CM.

In FSM3, a maximum 50% of the users with CM active can be supported, that is, amaximum 50% of the users can have CM active at the same time.

2.4.1.5 RAN1668: HSUPA Compressed Mode for LTE and Inter-frequencyHandover management data





Counter ID

Counter name

Measurement

M1002C676 ALLOCATION FOR HSUPA IFHOCOMPRESSED MODE

Traffic (RNC)

M1002C677 ALLOCATION DURATION FOR HSUPAIFHO COMPRESSED MODE

Traffic (RNC)

M1002C678 REJECTED HSUPA IFHO COMPRESSEDMODE

Traffic (RNC)

M1002C692 ALLO FOR COM MODE LTE Traffic (RNC)

M1002C693 ALLO DURA FOR COM MODE LTE Traffic (RNC)

M1006C312 HSUPA IFHO COMPRESSED MODE FAILDUE TO UE

RRC signalling

M1006C313 LTE COMPRESSED MODE FAIL DUE TOUE

RRC signalling

M1008C294 HSUPA IFHO ATTEMPTS Intra System Hard Handover(RNC)


44 DN09146788 Issue: 01

Table 24 New counters (Cont.)

Counter ID

Counter name

Measurement

M1008C295 SUCCESSFUL HSUPA IFHO Intra System Hard Handover(RNC)



Counter ID

Counter name

Measurement

M1002C623 ALLOCATION FOR HSDPA IFHOCOMPRESSED MODE

Traffic (RNC)

M1002C624 ALLOCATION DURATION FOR HSDPAIFHO COMPRESSED MODE

Traffic (RNC)

M1002C625 REJECTED HSDPA IFHO COMPRESSEDMODE

Traffic (RNC)

Key performance indicatorsTable 26: New key performance indicators lists key performance indicators introducedwith this feature.

Table 26 New key performance indicators

KPI ID

KPI name

RNC_5301a HSUPA Compressed Mode allocation success rate

There are no modified and existing key performance indicators related to this feature.



Full name

Abbreviated name

Managed object

TGPL for HSPA Inter FrequencyMeasurement

TGPLHSPAInterFreq RNHSPA



Issue: 01 DN09146788 45


Full name

Abbreviated name

Managedobject

BTS Support For HSPA CM BTSSupportForHSPACM WBTS

Max number of UEs in HSDPA CM dueto critical HO

MaxNumberUEHSPACmHO WCEL

Max number of UEs in HSDPA CM dueto NCHO

MaxNumberUEHSPACmNCHO WCEL

Table 29: Related existing parameters lists existing parameters related to this feature.

Table 29 Related existing parameters

Full name

Abbreviated name

Managedobject

Serving HS-DSCH cell change and SHOon/off switch

HSDPAMobility RNFC

Gap position single frame GAPPositionSingleFrame RNC

Gap position single frame GAPPositionSingleFrame RNMOBI

Recovery Period Power in ULCompressed Mode

UplinkRecoveryPeriodPowerMode RNAC

Initial transmit power in uplinkcompressed mode

UplinkInitialTransmitPowerMode RNC

UL Delta SIR1 in compressed mode DeltaSIRUplink RNC

UL Delta SIR1 in compressed mode DeltaSIRUplink WRAB

DL Delta SIR1 in compressed mode DeltaSIRDownlink RNC

DL Delta SIR1 in compressed mode DeltaSIRDownlink WRAB

UL Delta SIR after1 in compressedmode

DeltaSIRAfterUplink RNC

UL Delta SIR after1 in compressedmode

DeltaSIRAfterUplink WRAB

DL Delta SIR after1 in compressedmode

DeltaSIRAfterDownlink RNC


46 DN09146788 Issue: 01

Table 29 Related existing parameters (Cont.)

Full name

Abbreviated name

Managedobject

DL Delta SIR after1 in compressedmode

DeltaSIRAfterDownlink WRAB

Compressed Mode: Alternativescrambling code

AltScramblingCodeCM WCEL

Compressed mode master switch CmMasterSwitch RNFC



BSW/ASW

SW component


ASW HSPA RNC LK

2.4.2 Activating RAN1668: HSUPA Compressed Mode for LTEand Inter-frequency HandoverPurpose


For more information on the feature, see the Description of RAN1668: HSUPACompressed Mode for LTE and Inter-frequency Handover in WCDMA RAN, rel. RU50,feature descriptions.Before you start

Restart of the RNC is not required after the activation of this feature.

This procedure does not cause downtime, and can be activated at any time of the day.



Before activating this feature, activate the RAN1276: HSDPA Inter-frequency Handoverfeature (see Activating RAN1276: HSDPA Inter-frequency Handover).

Before activating this feature make sure that basic HSUPA and HSDPA mobility areenabled.

This feature is controlled by the long-term ON/OFF license key. For more information onlicensing, see Licensing.

g The feature code for this feature is 4783.


Issue: 01 DN09146788 47




48 DN09146788 Issue: 01



3 Expand the ROOT.


5 Expand the RNHSPAs folder.

6 Configure the RNHSPA object:a) Select Edit Parameters from the RNHSPA object.

b) In Packet Scheduler tab set the TGPLHSPAInterFreq parameter to 5 if thisfeature is used for inter-frequency handovers or/and set the value of theTGPLForLTEMeas parameter to 6 if this feature is used for LTE handover orlayering. Set the TGPLAMRHSDPAInterFreq parameter and theTGPLHSDPAInterFreq parameter to default value 4.

c) Navigate back to the RNC object.

7 Expand the WBTSs folder.

8 Configure the WBTS object:a) Select Edit Parameters from the WBTS object.

b) In Packet Scheduler tab set the value of the BTSSupportForHSPACMparameter to "HSPA CM supported".


9 Expand the RNFCs folder.

10 Enable compressed mode by configuring the RNFC object:a) Select Edit Parameters from the RNFC object.

b) In Packet Scheduler tab set the CmMasterSwitch parameter to "Used".


11 Go to the WCEL object by the following path:RNC object WBTSs folder WBTS object WCELs folder WCEL object


Issue: 01 DN09146788 49

12 Configure the WCEL object.a) Select Edit Parameters from the WCEL object.

b) In Packet Scheduler tab, set value greater than 0 for the parameterMaxNumberUEHSPACmHO .

c) In Packet Scheduler tab, set value greater than 0 for the parameterMaxNumberUEHSPACmNCHO.

2.4.3 Verifying RAN1668: HSUPA Compressed Mode for LTE andInter-frequency HandoverPurpose

Follow this procedure to verify that this feature works properly in the network.

Before you start

1. Make sure that the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is activated in the RNC (see Activating RAN1668:HSUPA Compressed Mode for LTE and Inter-frequency Handover).

2. Set BTS 1 CELL 2 as inter-frequency adjacent cell of BTS 1 CELL 1.3. Set the value of FMCI - IFHOcauseCPICHEcNo parameter to 1 ('Enabled') in

FMCI_ID assigned to BTS 1 CELL 1 (HsdpaFmciIdentifier orNrtFmciIdentifier parameter).

4. Set the value of FMCS - HHoEcNoTimeHysteresis parameter to 6 (100 ms) inFMCS_ID assigned to BTS1 CELL1 (HspaFmcsIdentifier,HsdpaFmcsIdentifier, or NrtFmcsIdentifier parameter).

5. Set WCEL parameter MaxNumberUECmHO to value greater than or equal to thevalue of WCEL-MaxNumberUEHSPACmHO parameter in BTS1 CELL1 (for the accesspath, see step 11 and step 12 in Activating RAN1668: HSUPA Compressed Mode forLTE and Inter-frequency Handover).


50 DN09146788 Issue: 01

1 Make an NRT interactive call with the UE (Rel-6/Rel-7/Rel-8/Rel-9), RAB onHSPA in BTS 1 CELL 1 and send data.

2 Adjust the signal of BTS 1 CELL 1, so that it is lower than the threshold valueof the HHoEcNoThreshold parameter.

3 Adjust the signal of BTS 1 CELL 2, so that it is stronger than the signal of BTS1 CELL 1.

4 Release the call.

5 Collect the log for "step 1", "step 2", "step 3", and "step 4" and analyze the log.

6 Verify that:

The UE sends out RRC: MEASUREMENT REPORT with Measured Results forintra-frequency event 1f.

In NBAP message RADIO LINK RECONFIGURATION PREPARE the values ofIEs in Transmission Gap Pattern Sequence Information are as follows:TGPS Identifier xxtGSN xxtGL1 7tGD xxtGPL1 5uL/DL mode UL/DLDownlink Compressed Mode Method sf/2Uplink Compressed Mode Method sf/2Downlink Frame Type xxDeltaSIR1 xxDeltaSIRafter1 xx

g xx means that the value of the IE is not relevant for verifying thisfeature. In RRC message PHYSICAL CHANNEL RECONFIGURATION the values of IEs

are as follows:tgp-SequenceList {{tgpsi xx,tgps-Status activate : {tgcfn xx },tgps-ConfigurationParams {tgmp fdd-Measurement,tgprc xx,tgsn xx,tgl1 7,tgd xx,tgpl1 5,rpp xx,itp xx,


Issue: 01 DN09146788 51

ul-DL-Mode ul-and-dl : {ul sf-2,dl sf-2 },dl-FrameType dl-FrameTypeA,deltaSIR1 xx,deltaSIRAfter1 xx }}}

g xx means that the value of the IE is not relevant for verifying thisfeature. Counters M1002C676 ALLO_CM_HSUPA_IFHO and M1002C623

ALLO_CM_HSDPA_IFHO are updated: 1 is added to their value.

Expected outcome

HSUPA compressed mode starts successfully and call release is normal. Logs data areas specified above and counters are updated.

2.4.4 Deactivating RAN1668HSUPA Compressed Mode for LTEand Inter-frequency HandoverPurpose




3 Expand the ROOT.


5 Expand the WBTSs folder.

6 Configure the WBTS object:a) Select Edit Parameters from the WBTS object.

b) In Packet Scheduler tab set the value of the BTSSupportForHSPACMparameter to "Only DCH CM supported" or "HSDPA CM supported".

Further information

After deactivating the feature, set the feature state to OFF.


52 DN09146788 Issue: 01

2.5 RAN2980: Measurement Based LTE Layering2.5.1 Description of RAN2980: Measurement Based LTE

LayeringIntroduction to the featureIn the current system implementation, the RAN2717: Smart LTE Layering featuresupports redirection from WCDMA to LTE. This redirection is performed blindly, that iswithout prior measurements of LTE layer. It is a good alternative when, for example,WCDMA and LTE cells are co-located and have largely overlapping coverage areas.However, UEs could face problem in cell reselection which can cause unsatisfying end-user experience.

The RAN2980: Measurement Based LTE Layering feature supports the redirection of UEto LTE layer only if measurement results indicate that LTE-capable UE could camp onLTE cell successfully. This ensures seamless LTE camping even if the WCDMA cell hasonly partial LTE coverage. Both FDD-LTE and TDD-LTE are supported.

2.5.1.1 Benefits

End-user benefitsEnsuring a successful LTE camping improves end-user experience.

Operator benefitsOperator benefits from having two types of WCDMA to LTE redirections available: withand without a measurement. Operator can choose if the trigger activates with- or without-measurement-based redirection.




RAS

Flexi Direct

IPA-RNC

mcRNC

Flexi DirectRNC

OMS

Flexi BTS




OMS3.0(RU50)

WN9.0


Issue: 01 DN09146788 53

Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE



NetAct 8EP1

Support notrequired

Support notrequired

Support notrequired

3GPPRel-8


RAN2382: Flexi BTS Multimode System Module - FSMC RAN1016: Flexi BTS Multimode System Module - FSMD RAN1848: Flexi BTS Multimode System Module - FSME


Functional overviewRRC connection release with redirection command to LTE can be used for moving LTE-capable UE to LTE, if compressed mode measurements indicate that LTE coverage isavailable. Each of the following events triggers compressed mode measurements forLTE:

RCC state change from Cell_DCH to Cell_FACH, Cell_PCH, or URA_PCH channel type change from HSDPA/HSPA to DCH/DCH CTS CS call release when UE has CS and PS connection active periodic trigger with operator-definable timer:

When LTE-capable UE enters the Cell_DCH state having only PS RAB(s), its timer(controlled with LTEPeriodicTriggerTimer parameter) is set. At the expiry oftimer, measurements for redirection to LTE are started and timer is set again. Ifmeasurement results lead to decision to redirect UE to LTE system, UE is thenredirected. If the measurement results do not trigger UEs redirection to LTE and UEstill continues data activity, then at the expiry of the timer the new timer is set andmeasurements are started again.

First three of the above mentioned triggers are also used in the RAN2717: Smart LTELayering feature. The RAN2980: Measurement Based LTE Layering feature introducesthe fourth trigger for UEs keeping long Cell_DCH reservations for PS services. Note thatwhen the RAN2980: Measurement Based LTE Layering feature is active, all four triggersare valid and there is no need to have the RAN2717: Smart LTE Layering featureinstalled separately.

In uplink, DCH is used during compressed mode. HSPA compressed mode, alsoincluding HSUPA compressed mode, is supported by the RAN1668: HSUPACompressed Mode for LTE and Inter-frequency Handover feature. If the RAN1668:HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is notimplemented in the network, the RAN2980: Measurement Based LTE Layering featuresupports HSDPA/DCH, and DCH/DCH. If there is HSUPA (E-DCH) in uplink, then it isreconfigured to DCH, before initiating the compressed mode measurements.


54 DN09146788 Issue: 01

LTE-capable UEs are checked for their measurement capabilities. UEs with dual receiverdo not require compressed mode for creating gaps to listen to other frequencies. Forsuch UEs, compressed-mode-related information is not required and thus not sent tothem.

If WCDMA cell load is not high and users can be provided good enough experiencewithin WCDMA layer, measurements and redirection to LTE can be bypassed. RNC loadlevel parameter can be used to define if load is low enough for keeping UEs in WCDMA.

With the RAN2980: Measurement Based LTE Layering feature operator can:

enable LTE redirection without measurements for the first three redirection triggers(also provided with the RAN2717: Smart LTE Layering feature) and measurement-based redirection to LTE for the periodic trigger

establish measurement-based redirection to LTE for all four redirection triggers select the frequencies to which UEs in Cell_DCH state are redirected in LTE system

as well as define camping priorities for those frequencies exclude some LTE carrier frequencies from LTE target camping layers disable the WCDMA cell load check which will result in automatic LTE redirection

every time the LTE coverage is available


Interdependencies between featuresThe RAN2067: LTE Interworking feature provides support for LTE cell reselection in idlemode Cell_PCH and URA_PCH states.

Impact on interfacesThis feature affects Uu and Iub interfaces and uses standard signaling procedures.



Impact on system performance and capacityThis feature has no impact on system performance or capacity.

2.5.1.5 RAN2980: Measurement Based LTE Layering management data




Issue: 01 DN09146788 55



Counter ID

Counter name

Measurement

M1001C747 RRC SETUP ATT CSFB Service Level

M1001C748 RC SETUP ACCESS FAIL CSFB Service Level

M1001C749 RRC ACCESS RELEASE CSFB Service Level

M1001C750 RRC SETUP ATT REPEAT CSFB Service Level

M1006C310 RRC CONN RELEASE LTE REDIR IN DCH RRC signaling

M1010C237 LTE CARRIER NOT FOUND FOR REDIRECTION Inter System HardHandover

M1010C238 LTE REDIRECTION STARTED AFTERMEASUREMENT

Inter System HardHandover

M1010C239 DURATION OF LTE CARRIER MEASUREMENT Inter System HardHandover




Full name

Abbreviated name

Managedobject

FMCL Identifier FMCLId RNC

FMCL

Change origin for FMCL object FMCLChangeOrigin FMCL

LTE Measurement Averaging Window LTEMeasAveWindow FMCL

LTE Maximum Measurement Period LTEMaxMeasPeriod FMCL

LTE Minimum Measurement Interval LTEMinMeasInterval FMCL


56 DN09146788 Issue: 01


Full name

Abbreviated name

Managedobject

LTE Neighbor Carrier Frequency SearchPeriod

LTENcarrFreqSearchPeriod FMCL

Measurement Based LTE Layering andHandover Activation

LTELayeringMeasAndHOActivation

WCEL

LTE Periodic trigger timer LTEPeriodicTriggerTimer RNC

Adjacent LTE Selected Frequency( EARFCN)

AdjLSelectFreq ADJL

WCDMA Cell Load Threshold WCDMACellLoadThreshold WCEL

FMCL Identifier FMCLIdentifier WCEL

Adjacent LTE Frequency Priority AdjLFreqPriority HOPL

LTE Carrier frequency selectionMinimum Rx Power level

AdjLMinRSRPLevel HOPL

LTE Carrier frequency selectionMinimum Rx qual level

AdjLMinRSRQLevel HOPL

Transmission Gap Length for LTECarrier frequency measurements

TGPLForLTEMeas RNHSPA



Full name

Abbreviated name

Managedobject

RNC Options RncOptions RNC

Smart LTE Layering Enabled SmartLTELayeringEnabled WCEL

Smart LTE Layering RSCP threshold SmartLTELayeringRSCP WCEL

Smart LTE Layering NRT user amountthreshold

SmartLTELayeringUA WCEL

Smart LTE Layering service control SmartLTELayeringServ RNMOBI

Timer for Smart LTE Layering Preventio SmartLTELayeringPrevT RNMOBI


Issue: 01 DN09146788 57

Table 34 Modified parameters (Cont.)

Full name

Abbreviated name

Managedobject

Smart LTE Layering Target SystemSelection

SmartLTELayeringTSysSel WCEL



BSW/ASW

SW component


ASW RAN RNC LK

2.5.2 Activating RAN2980: Measurement Based LTE LayeringPurposeFollow this procedure to activate the RAN2980: Measurement Based LTE Layeringfeature.Before you start

After activating this feature there is no need to restart neither the RNC, nor the BTS.Activating procedure does not cause downtime and the feature can be activated at anytime of the day.

Activate the license of the RAN2067: LTE Interworking feature using LTE Interworkinglicense key. For more information, see Activating RAN2067: LTE Interworking.

Activate the license of the RAN2980: Measurement Based LTE Layering feature usingMeasurement Based LTE Layering license key.



For more information on managing licenses, see Licensing.

Before activating the RAN2980: Measurement Based LTE Layering feature, the LTEneighbors must be configured according to the RAN2067: LTE Interworking feature.

HSDPA compressed mode measurements for LTE requires setting theBTSSupportForHSPACM WBTS parameter value to 1. If HSDPA CM is not activated,then the HS-DSCH to DCH channel switching is needed before starting the LTEmeasurements. Note that if the RAN1276: HSDPA Inter-frequency Handover featurelicense is ON, HSDPA Compressed Mode measurements for IFHO to the BTS inquestion is activated, provided the BTSSupportForHSPACM parameter value is set to 1.

The HSUPA compressed mode measurement support for LTE is provided with theRAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. Ifthat feature is not activated, then the E-DCH to uplink DCH channel switching is needed


58 DN09146788 Issue: 01

before starting the LTE measurements. The HSPA (HSUPA/HSDPA) compressed modemeasurements for LTE requires that the license of RAN1668: HSUPA Compressed Modefor LTE and Inter-frequency Handover feature is ON and the value of theBTSSupportForHSPACM parameter is set to 2.

Configure the following database objects and relevant parameters for the RAN2980:Measurement Based LTE Layering feature and attach them to the WCDMA cell:

FMCL parameters for controlling inter-RAT (LTE) measurement:

LTEMeasAveWindow LTEMaxMeasPeriod LTEMinMeasInterval LTENcarrFreqSearchPeriod

HOPL parameters for controlling inter-RAT (LTE) neighbor frequency:

AdjLFreqPriority AdjLMinRSRPLevel AdjLMinRSRQLevel

ADJL parameters for defining inter-RAT (LTE) neighbor frequency:

AdjLEARFCN AdjLMeasBw

WCEL parameters for identifying the Measurement Control Parameter Set andcontrolling redirection triggers:

FMCLIdentifier LTELayeringMeasActivation

g Note that the listed parameters are optional and have a default value. Only theAdjLEARFCN ADJL parameter, for defining the E-UTRA Absolute RadioFrequency Channel Number of the neighboring E-UTRA frequency, ismandatory.

g Redirection to LTE happens only when the cell has at least one Cell_DCHadjacency defined with the AdjLSelectFreq RNC/WBTS/WCEL/ADJLparameter. Operator can exclude chosen frequency from redirection targetusing the AdjLSelectFreq parameter. In order to use redirection to LTE,value 0 for the AdjLSelectFreq parameter must be used for at least one LTEfrequency configured in the cell.

g Ensure that RSRP and RSRQ thresholds in both LTE and WCDMA networksare aligned. Corresponding parameters related to this feature areAdjLMinRSRPLevel and AdjLMinRSRQLevel.

Additionally, the following parameters can be used for tuning the RAN2980:Measurement Based LTE Layering feature:

LTEPeriodicTriggerTimer RNC parameter SmartLTELayeringServ RNMOBI parameter LTETargetFreqCriterion RNMOBI parameter LTELayerCellHSLoad WCEL parameter SmartLTELayeringUA WCEL parameter


Issue: 01 DN09146788 59

SmartLTELayeringTSysSel WCEL parameter SmartLTELayeringRSCP WCEL parameter

g It is crucial to ensure the correctness of AdjLEARFCN and AdjLMeasBwneighboring LTE parameters while configuring, because RNC O&M is not ableto verify the values of these parameters.


2 Go to Topology and expand the ROOT directory.

3 Expand the RNC object and then the WBTS object.

4 Configure the WCEL object:a) Right-click on the WCEL object and select Edit parameters.

b) In Handover Control tab, set the value of the SmartLTELayeringEnabledparameter to Enabled.

5 In Handover Control tab, set the value LTELayeringMeasActivationparameter to:

0 for setting T1, T2, T3 as triggers for redirection without measurements and T4as a trigger for redirection with measurements

1 for setting T1, T2, T3, T4 as triggers for redirection with measurements

Further information

SmartLTELayeringEnabled WCEL parameter enables triggers (T) for the RAN2980:Measurement Based LTE Layering feature as follows:

value (0) = T1, T2, T3, and T4 disabled value (1) = T1 enabled value (2) = T1 and T2 enabled value (3) = T1 and T3 enabled value (4) = T1, T2, and T3 enabled value (5) = T1 and T4 enabled value (6) = T1, T2, and T4 enabled value (7) = T1, T3, and T4 enabled value (8) = T1, T2, T3, and T4 enabled

where the triggers are:

T1: RRC state change Cell_DCH to CCH T2: HSDPA/HSPA to DCH/DCH CTS T3: CS RAB release T4: periodic trigger


60 DN09146788 Issue: 01

For more information on triggers, see Description of RAN2980: Measurement Based LTELayering.

The RAN2980: Measurement Based LTE Layering feature is supported for the followingPS QoS classes:

interactive (NRT) background (NRT) streaming (RT)

2.5.3 Verifying RAN2980: Measurement Based LTE Layering

Purpose

Follow these tips to verify that the RAN2980: Measurement Based LTE Layering featureworks properly in the network.

Redirection to LTE, provided with the RAN2980: Measurement Based LTE Layeringfeature, is done after successful LTE measurements and sending the UE the RRCCONNECTION RELEASE message by the RNC. Feature's performance can be verifiedwith the following counters:

M1006C310 RRC CONN RELEASE LTE REDIR IN DCHwhich is updated when the RNC sends RRC connection release message to the UE,because of LTE redirection started by periodic trigger

M1010C238 LTE REDIRECTION STARTED AFTER MEASUREMENTwhich is updated when the LTE carrier measurement performed by the UE finds acarrier frequency with the quality acceptable to perform redirection and the RNCinitiates the redirection procedure

g Note that for verification using counters, the end-user has to make a PS call.Expected outcome

Redirection to LTE is successful and visible in the listed counters.

Unexpected outcome

Redirection to LTE is not successful and is visible in the following counter:

M1010C237 LTE CARRIER NOT FOUND FOR REDIRECTIONwhich is updated when the LTE carrier frequency measurement performed by the UEdoes not result in a carrier frequency with the quality acceptable to performredirection

Further information

g The following counter can be used for more detailed monitoring theRAN2980: Measurement Based LTE Layering feature: M1010C239 DURATION OF LTE CARRIER MEASUREMENT

Counters related to CS Fallback:

M1001C747 RRC SETUP ATT CSFB M1001C748 RRC SETUP ACCESS FAIL CSFB


Issue: 01 DN09146788 61

M1001C749 RRC ACCESS RELEASE CSFB M1001C750 RRC SETUP ATT REPEAT CSFB

2.5.4 Deactivating RAN2980: Measurement Based LTE Layering

Follow this procedure to deactivate the RAN2980: Measurement Based LTE Layeringfeature.


2 Go to Topology and expand the ROOT directory.

3 Expand the RNC object and then the WBTS object.

4 Configure the WCEL object:a) Right-click on the WCEL object and select Edit parameters.

b) In Handover Control tab, set the value of the SmartLTELayeringEnabledparameter to Disabled.

2.6 RAN147: RRC Connection Setup Redirection2.6.1 Description of RAN147: RRC Connection Setup

RedirectionIntroduction to the featureIn case the RRC connection is rejected due to the admission control reasons, the RNCsends the UE to 2G or 3G, to a new frequency for the next try. If RRC connection isrejected due to the signaling unit overload reason, the RNC sends UE to 2G.

2.6.1.1 Benefits

End-user benefitsBetter subscriber experience because of less call setup delay.

Operator benefitsThis feature helps to reduce call setup delay in case of congestion.


Software requirementsSoftware requirements lists the software required for this feature.


62 DN09146788 Issue: 01

RAS

Flexi Direct

IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite

RU50 Not planned RN8.0 Planned forlaterreleases

OMS3.0(RU50)

Support notrequired

Supportnotrequired

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

Support notrequired

NetAct 8 EP1 Support notrequired

Support notrequired

Support notrequired

Support notrequired

Hardware requirementsThis feature does not require any new or additional hardware.


Functional overviewThe RAN 147: RRC Connection Setup Redirection feature enables to redirect an RRCconnection to another 3G frequency or GSM. The redirection happens if admissioncontrol rejects the RRC connection request. The Figure 2: RRC connection setupredirection illustrates the described situation.

Figure 2 RRC connection setup redirection

The redirection info sent in the RRC message RRC CONNECTION REJECT depends onthe target system. If the target system is GSM, then the redirection info is a list of targetcells for the UE with release rel-6 or newer. If the UE release is older than rel-6, then theredirection info is just the target system, for example, GSM.


Issue: 01 DN09146788 63

If the target system is 3G, then the redirection info is a target frequency (UTRA AbsoluteRadio Frequency Channel Number). The inter-frequency neighbor cell AdjiUARFCNparameter defines it for downlink. The RNC calculates it for uplink in legacy way fromvalue of the AdjiARFCN parameter and duplex distance used in the RF band.

RRC connection sets up on Cell_DCH state, when the redirection is triggered. RRCconnection can be setup also on common channels. For more information, see RAN1797Common channel setup.

There is no Admission control in common channels thus it cannot fail, when RRCconnection is setup on common channels.

RRM decides about the target system on the basis of establishment cause of the RRCConnection Request and the new management RRCReDirTargetSys parameter. TheRRCReDirTargetSys parameter defines the target system for each establishmentcause. Also, if the RNC tries to redirect the RRC connection into GSM but UE is not ableto camp to the new target cell in GSM, then the RNC is allowed to redirect the RRCconnection into 3G. Value for each parameter need to be planned based on functionalityof actual establishment cause and available radio access technologies. Especially needto be considered if this certain functionality can be performed on GSM.

The RRCReDirBlockedCellAllowed parameter defines if cells, which are marked asblocked in SLHO or MBLB procedure, should not be used as a target cell of an RRCconnection redirection. If MBLB load information is not available, then only SLHOinformation (loaded or not loaded) is used. If both MBLB and SLHO load information isnot available, then SLHO and MBLB blocked cells are not reduced from the target celllist, although the RRCReDirBlockedCellAllowed parameter indicates that theblocked cells should not be used as a target cell of an RRC connection redirection.

The AdjiPriorityReDir parameter defines priority for each inter-frequency cell in theneighbor cell list if congestion of Iub transmission or BTS causes the rejection.

The AdjiPriorityQuality parameter defines priority for cells in the neighbor cell listif the RRC connection is rejected because of downlink power, uplink interference ordownlink spreading code congestion. The frequency of feasible target cell with thehighest priority is selected as the target frequency for redirection.

For more information, see the Figure 3: Selection process of redirection information.

Figure 3 Selection process of redirection information


64 DN09146788 Issue: 01

If the RNC signaling unit overload is the reason to reject the RRC Connection Request,UE can be redirected to GSM network without target cell list.


Interdependencies between featuresThere are no interdependencies between this and any other feature.




Impact on system performance and capacityThis feature has no impact on system performance or capacity.

2.6.1.5 RAN147: RRC Connection Setup Redirection management data





Counter ID

Counter name

Measurement

M1006C305 RRC_CONN_REDIR_GSM_FAIL 1006 - RRC signalling (RNC)



Counter ID

Counter name

Measurement

M1006C70 RRC_CONN_REJ_DIR_SETUP 1006 - RRC signalling (RNC)


Issue: 01 DN09146788 65

Table 37 Related existing counters (Cont.)

Counter ID

Counter name

Measurement

M1001C618 RRC CONN SETUP FAIL DUE TO ICSUOVERLOAD

1001 - RRC signaling (RNC)




Full name

Abbreviated name

Managed object

Enabling RRC connection Redirection RRCReDirEnabled RNFC

RRC Connection Redirection TargetSystem

RRCReDirTargetSys WCEL

RCC Connection Redirection TargetSystem for conversational causes

TargetsystemConversationalCall

WCEL

RRC Connection Redirection TargetSystem for streaming causes

TargetsystemStreamingCall WCEL

RCC Connection Redirection TargetSystem for interactive causes

TargetsystemInteractiveCall WCEL

RCC Connection Redirection TargetSystem for background causes

TargetsystemBackgroundCall WCEL

RCC Connection Redirection TargetSystem for subscribed traffic causes

TargetsystemSubscribedTraffic

WCEL

RCC Connection Redirection TargetSystem for emergency call causes

TargetsystemEmergencyCall WCEL

RCC Connection Redirection TargetSystem for inter-RAT re-selectioncauses

TargetsysteminterRATreselection

WCEL

RCC Connection Redirection TargetSystem for inter-RAT cell change ordercauses

TargetsysteminterRATchangeorder

WCEL

RCC Connection Redirection TargetSystem for registration causes

Targetsystemregistration WCEL


66 DN09146788 Issue: 01


Full name

Abbreviated name

Managed object

RCC Connection Redirection TargetSystem for detach causes

TargetsystemDetach WCEL

RCC Connection Redirection TargetSystem for high priority signallingcauses

TargetsystemHighPrioritySignalling

WCEL

RCC Connection Redirection TargetSystem for low priority signalling causes

TargetsystemLowPrioritySignalling

WCEL

RCC Connection Redirection TargetSystem for call re-establishment causes

Targetsystemreestablishment WCEL

RCC Connection Redirection TargetSystem for unknown causes

Targetsystemunknown WCEL

RCC Connection Redirection TargetSystem for MBMS reception causes

TargetsystemMBMSreception WCEL

RCC

RU50 Feature Descriptions of NSN

Documents