activating hsdpa

Activating HSDPA

Purpose

Follow this procedure to activate the HSDPA feature in the RNC.

Before you start

This feature belongs to the application software. Ensure that you have a valid licence. This feature is under licence key management.

Before the licensed features can be activated, the licence (a file containing the feature information) must be transferred to and installed in the RNC. The licence can be installed with NetAct or with a local MML interface. If NetAct is used for the installation, the state of any feature covered by the licence is automatically set to ON. If the MML interface is used, the user must set the feature state (ON/OFF/CONFIG) explicitely. In new installations, the default state is OFF. For more information on feature states, see Installing licences in the network element.

The parameters can be configured with the RNC RNW Object Browser GUI.

In order to activate the HSDPA soft pool, you need to know the present capacity step of your RNC. With this information, you can assign a predefined amount of DMCU capacity to the HSDPA soft pool. Select the correct capacity step from Table RNC capacity steps.

Give the following command to find out the current DMPG resource allocation situation:

ZWPI:S;

The starting point, when HSDPA has never been activated before, should be as follows:

MAIN LEVEL COMMAND <___>< ZWPI:S;

LOADING PROGRAM VERSION 8.10-0

INFORMATION OF DMPG SETUP USAGE:

ID DMPG POOL SETUP NAME CONFIGURED SHARE % ACTUAL SHARE % ---------------------------------------------------------------

0 DCH DMPG 100 100 1 HS DMPG 0 0

DMPG POOL SETUP DESCRIPTIONS:

DCH DMPG : PPC SETUP FOR DCH DMPG HS DMPG : PPC SETUP FOR HS DMPG

COMMAND EXECUTED

The fields in the printout have the following meanings:

Service pool name: name of the pool Configured share %: the target of the pool share (the percentage of units in the pool) set by the user

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=mmlwpi&edition=0&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=cmdwpi#cmdwpi

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=dn0554843&edition=511&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=may1661222111#may1661222111

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=dn0648584&edition=3&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=ned_top#ned_top


http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=general_glossary&edition=11&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=id010096#id010096


Actual share %: the current pool share state of the system

When the configured share and actual share are equal, pool allocation has been completed successfully.

Even if the resources have already been allocated and the printout is not exactly the same as above, you can still follow the steps below to activate the HSDPA pool.

Note that the Cell pool is not used.

Steps

Expand/collapse all

1. Select a capacity step from Table RNC capacity steps.

In this example, the capacity step RNC196/122M is used. Modify the commands accordingly when using a different capacity step.

2. Change the pool allocation.

According to Table RNC capacity steps, you must allocate 60% of the DMPGs to the normal pool (SETUP0) and 40% to the HSDPA1 pool (SETUP1).

Table: RNC capacity steps

Capacity step Normal pool share Used HSDPA pool HSDPA pool share

RNC196/48M 69% HSDPA1 31%

RNC196/85M 63% HSDPA1 38%

RNC196/122M 60% HSDPA1 40%

RNC196/159M 58% HSDPA1 42%

RNC196/196M 57% HSDPA1 43%

RNC196/300M 57% HSDPA1 43%

RNC196/450M 57% HSDPA1 43%

RNC450/150M 68% HSDPA1 32%

RNC450/150M/660 72% HSDPA1 28%

RNC450/150M/720 78% HSDPA1 22%

RNC450/150M/780 83% HSDPA1 17%

RNC450/150M/840 89% HSDPA1 11%

RNC450/300M 64% HSDPA1 36%

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=dn0554843&edition=511&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=may1661222111#may1661222111

Capacity step Normal pool share Used HSDPA pool HSDPA pool share

RNC450/300M/1200 78% HSDPA1 22%

RNC450/450M 57% HSDPA1 43%

RNC450/450M/1800 78% HSDPA1 22%

Pool shares are modified with the WPM command. In the syntax of the command, the pools are called SETUP0 and SETUP1. The parameters of the command and the correspondence between the soft pools and their names are explained in Table Parameters of the WPM command.

Table: Parameters of the WPM command

Parameter Explanation

SETUP0 The percentage of DMPG resources that will be allocated to the normal (non-HSDPA) pool.

SETUP1

The HSDPA1 pool size according to the capacity step of the RNC.

Select the capacity step of the RNC from Table RNC capacity steps above and assign the appropriate percentage values to the SETUP0 and SETUP1 pools.

Give the following command to change the size of the pool:

ZWPM:SETUP0=60,SETUP1=40:;

The output of the whole command is as follows:

< ZWPM


/* PARAMETERS:

USAGE OF DMPG POOL SETUP 0,USAGE OF DMPG POOL SETUP 1;*/WPM:

/* IDENTIFY POOL SETUP USAGES:

PARAMETER NAMES

SETUP0 ... USAGE OF DMPG POOL SETUP 0 (DCH DMPG) SETUP1 ... USAGE OF DMPG POOL SETUP 1 (HS DMPG) */WPM:SETUP0

/* IDENTIFY THE USAGE OF DMPG POOL SETUP 0:

PERCENTAGE UNIT

0 ..... 100 */

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=mmlwpm&edition=0&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=cmdwpm#cmdwpm




WPM:SETUP0=60


PARAMETER NAMES

SETUP0 ... USAGE OF DMPG POOL SETUP 0 (DCH DMPG) SETUP1 ... USAGE OF DMPG POOL SETUP 1 (HS DMPG) */WPM:SETUP0=60,SETUP1

/* IDENTIFY THE USAGE OF DMPG POOL SETUP 1:

PERCENTAGE UNIT

0 ..... 100 */

WPM:SETUP0=60,SETUP1=40


PARAMETER NAMES

SETUP0 ... USAGE OF DMPG POOL SETUP 0 (DCH DMPG) SETUP1 ... USAGE OF DMPG POOL SETUP 1 (HS DMPG) */WPM:SETUP0=60,SETUP1=40,:;

3. Execute the pool change.

You have three alternatives for executing the pool change.

a. Restart the RNC. Use this option only if you need to restart the RNC for some other reason.b. Restart the DMPG units by entering the following command:

ZUSU:DMCU,<index>;

Note that the master DMPGs should not be restarted. The master DMPGs can be recognised by their index number, which is divisible by four.

It is recommended that this operation be performed during the night-time in order to minimise impact on call traffic.

c. Perform a controlled DMPG state change. This option can be used to avoid interrupting call traffic.

Note that the master DMPGs should not be restarted. The master DMPGs can be recognised by their index number, which is divisible by four.

Give the following command to change the DMPG to state Blocked – BL:

ZUSC:DMPG,<index>:BL;

When the state of the DMPG is changed to BL (blocked), no more resources from this DMPG will be allocated to users. Over a period of time, the resources will be released as users complete their calls until eventually all the resources for the DMPG are free and the system can change the state of the DMPG to BL. The state of the DMPG cannot be changed to the

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=mmlusc&edition=0&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=cmdusc#cmdusc

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=mmlusu&edition=0&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=cmdusu#cmdusu

next state until it has changed to BL, that is, until no more active calls are being handled by the DMPG.

Give one of the following commands to monitor the state of the DMPG(s):

ZUSI:DMPG; (to view the state of all DMPGs)

or

ZUSI:DMPG,<index>; (to view the state of one specific DMPG)

When a unit is in the BL-ID state, give the following commands to initiate the DMPG pool configuration and place the DMPG back into service (working state):

ZUSC:DMPG,<index>:TE;

ZUSC:DMPG,<index>:WO;

If the configured HSDPA share is 25% this means that 25% of the configured DMPGs need to be restarted in order to achieve the total actual share.

Note that only two DMPGs per DMCU may be allocated to HSDPA.

4. Monitor the progress.

You can monitor the progress of the overall pool configuration change procedure with the following command:

MAIN LEVEL COMMAND <___>< WPI:S;







COMMAND EXECUTED

The printout indicates that the pool percentage is being updated.



http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=mmlusi&edition=0&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=cmdusi#cmdusi

http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=mmlusi&edition=0&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=cmdusi#cmdusi

Expected outcome

The pool configuration is complete. You can verify this with the following command:

MAIN LEVEL COMMAND <___>< ZWPI:S;







COMMAND EXECUTED

Once the code loading is completed, the configured share should equal the actual share. However, the actual share may not be exactly equal to the configured share, as the actual share depends on the number of DSP units and how this number is divisible by the given percentage values. In the RNC, all the DSPs for each DMPG must be in the same pool (that is, at least eight DSPs change the pool at a time).

5. Configure WBTS and CoCo.

For the WBTS object, set the values for the following parameters:

o PtxnonHSDPA averaging window size for LC (WinLCHSDPA)

o Shared HSDPA AAL2 allocation (SharedHSDPAallocation)

o Number of overbooked HSDPA users (NbrOfOverbookedHSDPAUsers)

o Release timer for shared HSDPA allocation (ReleaseTimerForSharedHSDPAallocation)

o Shared HSDPA AAL2 VCC selection method (SharedHSDPAVCCSelectionMethod)

o Shared HSDPA flow control allocation (SharedHSDPAFlowControlAllocation)

As there are no HSDPA-specific parameters for the CoCo object, set the values normally according to the transmission network planning. The default values can be used initially.



For more information on WBTS and CoCo, see Creating a WCDMA BTS site, Modifying WCDMA BTS parameters, Creating a radio network connection configuration, and Modifying radio network connection configuration parameters.

For more information on the relevant WBTS and COCO parameters, see WCDMA RAN Parameter Dictionary.

2. Configure FMCS/FMCI/FMCG.

Set the values for the FMCS, FMCI, and FMCG parameters listed below. With these parameters, you can adjust the sensitivity of the transfer from HS-DSCH to DCH. The default values can be used initially.

Note that it is not always necessary to create a new FMCS/FMCI/FMCG set for HSDPA; you can also use the same FMCS/FMCI/FMCG set as for RT and NRT calls. The ID of the HSDPA FMCS set (HsdpaFmcsIdentifier) can, for example, be the same as the ID of the RT or NRT FMCS set

(RtFmcsIdentifier or NrtFmcsIdentifier).

o FMCS is needed if ADJS is defined for WCEL.o FMCI is needed if ADJI is defined for WCEL.

o FMCG is needed if ADJG is defined for WCEL.

FMCS parameters

o Addition Window (AdditionWindow)

o Addition Time (AdditionTime)

o Addition Reporting Interval (AdditionReportingInterval)

o CPICH Ec/No Filter Coefficient (EcNoFilterCoefficient)

o CPICH Ec/No HHO Threshold (HHoEcNoThreshold)

o CPICH Ec/No HHO Time Hysteresis (HHoEcNoTimeHysteresis)

o CPICH RSCP HHO Filter Coefficient (HHoRscpFilterCoefficient)

o CPICH RSCP HHO Threshold (HHoRscpThreshold)

o CPICH RSCP HHO Time Hysteresis (HHoRscpTimeHysteresis)

FMCI parameters

o IFHO caused by UE TX Power (IFHOcauseTxPwrUL)

o IFHO caused by CPICH Ec/No (IFHOcauseCPICHEcNo)

o IFHO caused by CPICH RSCP (IFHOcauseCPICHrscp)

o UE TX Power Filter Coefficient (InterFreqUETxPwrFilterCoeff)

o UE TX Power Threshold for NRT PS (InterFreqUETxPwrThrNrtPS)

o UE TX Power Time Hysteresis (InterFreqUETxPwrTimeHyst)

FMCG parameters















o GSM HO caused by CPICH Ec/No (GSMcauseCPICHEcNo)

o GSM HO caused by CPICH RSCP (GSMcauseCPICHrscp)

o GSM HO caused by UE TX Power (GSMcauseTxPwrUL)

o UE TX Power Filter Coefficient (GsmUETxPwrFilterCoeff)

o UE TX Power Threshold for NRT PS (GsmUETxPwrThrNrtPS)

o UE TX Power Time Hysteresis (GsmUETxPwrTimeHyst)

For more information on FMC, see Creating frequency measurement control and Modifying frequency measurement control parameters.

For more information on the relevant FMCS, FMCI, and FMCG parameters, see WCDMA RAN Parameter Dictionary.

3. Configure HOPS.

Set the values for the following HOPS parameters:

o HHO Margin for Average Ec/No (HHOMarginAverageEcNo)

o HHO Margin for Peak Ec/No (HHOMarginPeakEcNo)

o Release Margin for Average Ec/No (ReleaseMarginAverageEcNo)

o Release Margin for Peak Ec/No (ReleaseMarginPeakEcNo)

o CPICH Ec/No Averaging Window (EcNoAveragingWindow)

o Enable RRC Connection Release (EnableRRCRelease)

The default values can be used initially. HSDPA-specific HOPS is needed for advanced features such as HSDPA CELL FACH inter RNC mobility.

HOPS is needed if the HSDPA-enabled WCEL has ADJS. If HOPS is not configured, the mobility of the UE in the network cannot be guaranteed.

For more information on HOPS, see Creating handover path and Modifying handover path parameters.

For more information on the relevant HOPS parameters, see WCDMA RAN Parameter Dictionary.

4. Configure ADJS.

Configure the ADJS for the WCEL by setting the value for the HSDPAHopsIdentifier parameter. Use the same value as in step 7.

For more information on the relevant ADJS parameters, see WCDMA RAN Parameter Dictionary.

5. Configure WCEL.

Before you start

Ensure that the PLMN ID of the circuit-switched core network and packet-switched core network is correct (according to the network planning). The PLMN identity must be configured when creating the core network. For more information, see WCELCSCNId (CS Core Network Identity) and WCELPSCNId (PS Core Network Identity) in WCDMA RAN Parameter Dictionary.












In the WCEL object modification operation, the WCEL must be locked before the value of the parameter HSDPAenabled can be changed. The WCEL must also be locked when modifying the

PtxMaxHSDPA parameter.

a. Set the values for the following parameters. The default values can be used initially, except for HSDPA enabled (HSDPAenabled).

Target for transmitted non-HSDPA power (PtxTargetHSDPA)

Maximum allowed HSDPA power (PtxMaxHSDPA)

Offset for transmitted non-HSDPA power (PtxOffsetHSDPA)

HSDPA FMCS identifier (HSDPAFmcsIdentifier)

HSDPA FMCI identifier (HSDPAFmciIdentifier)

HSDPA FMCG identifier (HSDPAFmcgIdentifier)

HSDPA enabled (HSDPAenabled) - Set this parameter to enabled.

Directed RRC connection setup enabled (DirectedRRCEnabled)

Select the required parameters from the HC, AC, and LC tabs of the Modify WCEL dialogue box. The default values can be used initially.

b. Set the correct FMCS, FMCI, and FMCG references corresponding to the HSDPA FMCS identifier, HSDPA FMCI identifier, and HSDPA FMCG identifier parameters.

c. After the HSDPA parameters have been configured as planned, set the value for the HSDPA enabled parameter to Enabled. This activates HSDPA functionality for the cell.

For more information, see Creating a WCDMA cell and Modifying WCDMA cell parameters. For more information on the relevant WCEL parameters, see WCDMA RAN Parameter Dictionary.

Expected outcome

The HSDPA feature is activated in the cell(s) of the RNC. The BTS informs the RNC when HSDPA is active. The HSDPA state can be seen on the WCEL parameter Operational HS-DSCH state. The expected state is Enabled.

Unexpected outcome

If something goes wrong when the RNC requests configuration or reconfiguration of the HSDPA channels to the BTS, the following alarm is set:

7772 Physical shared channel configuration failed

If the BTS informs that the Operational HS-DSCH state is Disabled, the following alarm occurs:

7776 HSDPA failure in WCEL

Do not cancel the alarms. The system cancels the alarms automatically when the fault has been corrected.

Next successful configuration of the HSDPA channels cancels alarm 7772.

For more information on the alarms and troubleshooting instructions, see Base Station Alarms (7000–7900).

Further information


http://127.0.0.1:43231/NED/NED?action=retrieve&library=ran_rnc_rel_06_3_0_v2&identifier=al7772&edition=0&language=en&coverage=global&encoding=xhtml_1_0&component=data&item=data&pointer=ned_top#ned_top





It is not necessary to reset the RNC after activating this feature.

activating hsdpa

Documents