October 2012

Arum Setyo sweet.arum@gmail.com

Source Coding: convert analog to digital

Channel Coding: add redundant bit

Spreading: anti jamming

Scrambling: secure transmission

Modulation: digital to radio signal converter

Transmit: send data via radio propagation

Logical Channel

Control Channel: content data for signaling

Service Channel: content data for traffic

Transport Channel

Dedicated Channel

Common Channel

Physical Channel

UL/DL Physical Channel

Dedicated carrier phase

code (OVSF, SC)

Capacity

Coverage

QoS

(they will give affect to each other)

Working mode and working state of 3G is

purposed for power and paging efficiency

based on its load (light or heavy traffic).

The purpose of the spreading is to make the

signal more reliable to the noise/jammer.

When site A and B have no relation, while A

and C and D have relation, C and D coverage

will causing some pollutant in x. EcNo in x

will be bad.

15–25 NodeBs in a cluster is recommended

A cluster must cover different areas based on density of user traffic/clutter

A cluster can define based on landform factor Mountains block signal propagation, so they are natural borders for

dividing clusters.

Rivers causes a longer propagation distance, so they affect dividing clusters in various aspects. If a river is narrow, the signals along two banks will interact. If the

transportation between two banks allows, divide sites along the two banks in the same cluster.

If a river is wide, the upstream and downstream will interact. In this situation, the transportation between two banks is inconvenient, dividing clusters by the bank according to actual situation.

A cluster can define based on network project maintenance

A cluster can define based on Administrative areas

A cluster can define based on DT workload The DT must be performed within a day for a cluster

Create neighbour script and upload the script

to RNC system

Give DT route, Site info, latest dump and

celfile to DT team

Check alarm and site availability on LMT

If the all condition is okay, send DT team to

the field.

Cross feeder check

Functionality test

Test call MT/OT

SMS test MT/OT

Data test (throughput)

The condition where there is a DN that is

located (geographically) near to AS1 and the

DN level signal RSCP and EcN0 is better or

slightly the same as AS (on good condition,

strong signal).

The condition where there are more than 3

strong signals with the condition of RSCP and

EcNo signal closely as strong as Active set.

SHO Overhead happens when there is so

many SHO is happenng on certain area of DT.

The event related to this problem is 1a and

1b event.

1 TP = 234 Meters

RTWP can be caused by bad weather, feeder

broken, port feeder broken, or traffic

fluctuation (load).

3G to 3G (same carrier): SHO

3G to 3G (different carrier): IFHO

3G to DCS: IRATHO/ISHO

3G to GSM: IRATHO/ISHO

2G to 3G: UMFI

Increase CIO offset: Make HO easy

Decrease CIO offset: Make HO hard to do

CPICH RSCP

Good: > -75dB

Bad: < -85dB

CPICH EcN0

Good: > -4dB

Bad: < -8dB

Cch256,0

Excluding the distance variable, overshooting

is a condition where the signal level serve

more than 2 layers of neighbor site.

Transmission Alarm

High BER

RTWP exceed

Board failure

NCP/CCP alarm

MDT: Pattern still changed

+++ MDT: got additional side lobe, Coverage

decreased

--- MDT: side lobe decrease, Coverage increase

EDT: Pattern still the same

+++ EDT: Coverage decreased

--- EDT: Coverage increase

Scanning test (DT)

Do scanning (via drive test)

Locate pollutant area

Do Neighbor list verification

Remove nbr that is not measured but in Nbr list

Add missing neighbor

Check pollutant, whether it’s from

overshooting site or site nearby

Check and Adjust physical configuration

Check and Adjust CPICH Power

CSSR

DCR

SHO, IFHO, IRATHO

CSSR : RAB Failure

DCR : RAB Loss/ RAB Abnormal Release

Uu Fail happens when UE and NodeB cannot

communicate because the Uu Interface is

failure. Check for alarm and invalid

configuration in RNC

No Reply happens when NodeB doesn’t

receive any reply from UE.

This problem happens because of the

distance between nodeB and UE is changing

(UE move leaving the nodeB)

Check for physical config, geographically

contour, and alarm.

Steps for choosing WPC candidate:

Look KPI degradation in RNC Daily/BH Level

Get the highest failure cause in RNC daily/BH

Level

Get failure cause counter per cell daily/BH Level

Select Rate below threshold

Sort Failure number in descending (Higest to Lowest)

Do weighting process to choose the cell with high

attempt and bad rate [weighting = (rate*fail number)]

Get your Top5 or Top10 candidate to optim

Blocking CE

Blocking Code

Blocking IuB

Blocking Power

Upgrade

Downgrade

UPGRADE

Blocking High

Utilization High

DOWNGRADE

Blocking Low

Utilization Low

Resource Configured more than 2

Cek Parameter Setting if:

Blocking High

Utilization Low

VS.RAB.AbnormRel.PS.RF.SRBReset

VS.RAB.AbnormRel.PS.RF.ULSync

VS.RAB.AbnormRel.PS.RF.UuNoReply

VS.RAB.AbnormRel.PS.RF.TRBReset

VS.RAB.FailEstCs.ULPower.Cong

VS.RAB.FailEstCs.DLPower.Cong

VS.RAB.FailEstCs.Code.Cong

VS.RAB.FailEstab.CS.DLIUBBand.

VS.RAB.FailEstab.CS.ULIUBBand.

VS.RAB.FailEstCs.ULCE.Cong

VS.RAB.FailEstCs.DLCE.Cong

Database 2G-3G Consistecy Check

Cross check 2G CFGMML with External 2G on 3G

CFGMML (parameter check on 2G: MCC, MNC,

LACCI, NCC, BCC, BCCH, RAC)

Old database still not yet erased

Failure on 2G due to cell unavailable/Alarm

Cross check IRATHO NCell

Failure on 2G due to congestion (PDCH Block)

Cross check IRATHO NCell

WCDMA system got two frequency carrier

Handle more traffic with limited physical

configuration.