CCPCH Configuration 2

RU20 support PCH bitrate of 8kbps and 24 kbps Check whether a large amount of signalling generated by cell, URA, location area or routing area updates. If so, consider adjusting the area boundaries.

Evaluate whether or not there is excessive user plane data transfer within CELL_FACH. If so, consider reducing the RLC buffer thresholds that trigger the transition to CELL_DCH

M1000C176 M1000C177

PCH24kbpsEnabled is configured to enabled with this configuration PCH bit rate is increased to 24 kbps

PCH is allocated its own separate S-CCPCH

SF128 is allocated to the PCH to support the increased bit rate

–Transport block size of 240 bits & 10 ms TTI

–24kbps paging channel require activation of second SCCPCH channel

24Kbps paging Channel - Impact to Code and power capacity

(B/coz Channelisation code for 24 kbps PCH uses a larger section of the code tree)

=a single cell can thus page maximum 100 UEs per second

HSDPA cannot use 15 HS-PDSCH codes when HSUPA 2 ms TTI is enabled with 24 kbps PCH

The transmit power of the S-CCPCH is defined using the parameters:

•PtxSCCPCH1 (PCH/FACH or only FACH)

•PtxSCCPCH2 (Standalone PCH)

•PtxSCCPCH3 (S-CCPCH for SAB)

•PtxSCCPCH2SF128 (Standalone PCH SF128 / 24kbps)

The PtxSCCPCH2SF128 parameter defines the transmit power of the S-CCPCH used to transfer the 24 kbps PCH All parameters define the transmit power of the data bits (rather than the transmit power of the TFCI and Pilot bits)

80 bits & carry a single paging record per TTI (10 ms TTI) single paging record can be broadcasted per 10 ms TTI

paging messages could get lost causing a bad user experience (‘non-reachability’ of UEs due to missing pages).

, we know that S-CCPCH can be shared with the FACH-c and FACH-u but PCH always has priority.

high Paging load has an impact upon FACH capacity when single S-CCPCH is configured.

When the amount of paging messages exceeds 50% of the nominal capacity, its good time to start thinking about actions to reduce paging channel load to avoid degradation in paging success rate.

feature can increase the paging channel capacity three times higher from the 8 kbps

6 - 12 dB 4 - 8 dB 4 - 8 dB 4 - 8 dB

2 dB

when there is not E-DCH connections with the cell]

for NRT scheduling when one or more E-DCH connections have been established. This can be adjusted between PrxTargetPSMax and PrxTargetPSMin.

It is suggested to configure this parameter to be greater than PrxTarget + PrxOffset because the Node B is more responsive than the RNC.

PrxMaxTargetBTS in order to provide capacity for HSUPA users

Recommended

When the amount of paging messages exceeds 50% of the nominal capacity, its good time to start thinking about actions to reduce paging channel load to avoid degradation in paging success rate.

CS/PS Access Failure Optimization: Call Setup analysis

HSDPA Access Failure Optimization:

1.1.1.1.1.        Accessibility Analysis (CS/PS/HS)

1.1.1.1.1.        Retainibility Analysis (CS/PS/HS)

Voice Drop Call Optimization:

R99 PS Drop Call Optimization:

HSDPA Throughput Optimization:

1.       Monitor Daily Performance Reports/KPIs Worksheet---Pick Worst Offenders

2.       Identify DCR top offenders…. few cells?…. Any particular area ? Known Coverage issue? Need a new site ? 3.       Was the availability of the site 100%?

4.       Any current alarms on the site / sector?

5.       Check the alarm history especially for transmission issues (NBAP link failures/T1 fluctuations?) 6.       Check if the sector is dropping the calls due to RF (Counter: Voice_Drops_due_to_radio_int) 7.       If not RF, check if the following counters are pegged:

•          Voice Drops due to Iu

•          Voice Drops due to BTS

•          Voice Drops due to Iur (Not applicable for Cleveland or Columbus now)

•          Voice Drops due to RNC

•          Voice Drops due to UE

7.       If drops are due to RF (Voice Drops due to radio int), check the Site location, Neighbors, Cell to cell HO statistics, PRACH delay distance and Ec/No quality distribution statistics 8.       Need Tilt / Azimuth change to improve the area?

9.       HO issue? All Neighbor Exists? SHO….ISHO……IFHO…….?? Neighbor Adds?

10.   It might be observed on some sites that although there is no alarm and cell is carrying traffic, some HW faults ( could be found only during the site visits) causing call drops e.g. bad feeder or antenna or MHA problem?

2.8.1.2.3        Throughput Optimization:

2.8.1.2.4. Capacity Analysis (Power, Codes, Node-B CE, RNC)

2.8.1.3        UMTS Special Feature Optimization 2.8.1.3.1       Multi Band Load Balancing(MBLB)

Measurement Based HO(With CM) -( Inactivity Timer Triggered & Mobility Triggered).

Trigger Events:

Optimization Strategy:

Confirmation to the recommended parameter set in most cases. Some market/Cluster/Site specific adjustments needed in order to meet performance KPI and balance traffic between PCS and AWS bands or between multiple carriers within a specific band.

Main Parameters to keep Track /Tune and Effects:

1. MBLBRABSetupEnabled; MBLBInactivityEnabled; MBLBStateTransEnabled; MBLBMobilityEnabled

(Each type can be enabled on cell level independently on others, by corresponding source cell WCEL parameter (enabling in target cell not needed)

Example: RNC-1 / PFLIdentifier-1

3. RSCP thresholds used to make upper or lower frequency bands appear more attractive:

BlindHORSCPThrAbove ; BlindHORSCPThrBelow.

4. Weights allocated to each component of the Preference Score calculation

LaySelWeightPrefLayer; LaySelWeightBand; LaySelWeightRSCP; LaySelWeightLoad 5. Whether or not increased weight is given to low loaded cells: LaySelLowLoadPref 6. Preferred layers for fast moving UE: PFLFastMovUECS , PFLFastMovUEPS

Candidates for MBLB are Inter Frequency neighbors on different freq layer, if prioritized higher than the source cell layer or neighbors in different bands supported by UE The complete MBLB feature basically consists of following three operations:

·         Triggering Events

·         Target Layer Selection Criteria

·         Handover Execution

1.Four Triggering Events: Radio Bearer Setup, Inactivity in Cell-DCH, State Transition to Cell-DCH, Mobility.

2.Four Target Layer Selection Criterion: Freq Layer Preference (based on UE capability, Requested Service, Speed etc), Band Preference, Better Coverage, Traffic/Load Balancing.

3.IFHO Execution: Blind HO (W/o Comp Mode)- (RB Setup Triggered & Transition to DCH state Triggered);

2. Preferred Frequency Layer Identifiers: (Parameters used to create/define the preferred network layer for each UE capability / service type combination) Up to 8 preferred frequencies can be listed for each 16 capability & service combination .

·         LaySelWeightLoad=50

GSM Voice Access Failure Analysis Process 2.8.2.2.        GSM Optimization Process using OSS KPI/Counters

2.8.2.2..1.        Voice Accessibility Analysis (SDCCH/TCH)

YES 1

=0 Modify the parameters accordingly

Escalate to NSN technical support