Guideline For Dummies

3G CDR CS Fast Analyze

2017 Ngayum.sastrowardoyo@gmail.com
CALL SETUP PROCEDURE
What is RRC and RAB?
RAB and RRC are two of the most important concepts
because they are responsible for all the negotiation
involved in calls
In addition to RAB and RRC, we still have some other
terms directly involved in context, as RB, SRB, TRB, among
others. These terms are also important concepts, since
without them RAB and RRC could not exist
we can divide a call into two parts: the signaling (or
control) and data (or information). Already ahead of key
concepts, we can understand the RRC as responsible for
the control, and the RAB as responsible for the
information part
The Analogy for RRC and RAB
Let's start imagining the following
scenario: two people are cut off
by a cliff.
There are:
a person (1) want to buy some
things that are for sale in a store
A store (2) or deposit on the right
side. In the right side, in addition
to the deposit,
we also have a seller (3), which
will help the buyer to contact
(negotiable) with the deposit
As additional or auxiliary objects
(4), we have some iron bars with
different sizes, and some cars -
some like train wagon, others like
remote control cars
 The Analogy for RRC and RAB
Let's continue with a possible solution:
the buyer on the left write his request
in a note, tie on a small stone,
and send (1) it to the seller on the
other side.
So, This stone carry the information or
initial
 The Analogy for RRC and RAB
The seller receives the request, but
the seller need to send it to the
deposit, in order for the shopping to
be sent.
The seller sends the request on a
remote control car (1), which run a
previously demarcated path to the
deposit.
 The Analogy for RRC and RAB
Some time later, the deposit response
arrives to seller (1), which then checks
to see whether the reseller will be
able to send the data or not
 The Analogy for RRC and RAB
Let's consider a condition for a positive
response; there is an item to buy (or the
'resources' are available)
The Seller realizes that to fulfill the
request, and be able to send the
purchases, the seller will need to build a
'path' (1) between the two ends of the
cliff, so the wagons could carry over
with the orders/receipts and purchases
Then, the seller uses some of iron bars to
create a bridge and creates a link
between the two sides
 The Analogy for RRC and RAB
Once the bridge are established,
requests can be sent from both sides
And any other information can be
transferred by different paths and
wagons/cars!
Technical point of view
RRC Connection
Iu Establishment
RAB Establishment
Summary
3G RADIO INTERFACE PROTOCOL
Interface Protocol
UMTS Protocol UMTS Protocol Type
RNL Application Protocol
General Flowchart - RRC, RAB and Others
Definition of the RRC Connection Success Rate

Collect the statistics of RRC Connection Request messages at point A and the statistics of RRC Connection Setup
Complete messages at point B in the preceding figure.

RRC connection success rate = VS.RRC.SuccConnEstab.Sum/VS.RRC.AttConnEstab.Sum

Page 20
Definition of the RAB Setup Success Rate

Collect the statistics of RAB Assignment Request messages at point C and the statistics of RAB Assignment
Response messages at point D in the figure above.
CS RAB setup success rate = VS.RAB.SuccEstabCS/VS.RAB.AttEstabCS
PS RAB setup success rate = VS.RAB.SuccEstabPS/VS.RAB.AttEstabPS
Page 21
Common Factors That Lead to UMTS Access Problems

1. KPIs of the migrated office
are not mapped.
2. A KPI formula is incorrectly
defined.
1. Parameters of the migrated office
are not mapped.
2. Parameters are not optimal.
3. Parameters are incorrectly
configured.
4. Parameters of feature services
affect UMTS access.
1. Equipment has fault alarms.
2. Transmission faults such
as packet loss exist.
1. A software version is
1. Equipment networking leads
defective.
to load imbalance.
2. Version algorithm change
2. Equipment networking falls
leads to KPI closed loop.
short of current load
requirements.

Parameters Equipment & Software version Network planning

KPI definition
transmission

1. Equipment resources 1. Abnormal standing wave ratio 1. Weather

(SWR) 1. Weak coverage 1. Seasonal user growth
including SPU, MPU, CPU,
2. Hardware fault of uplink 2. Coverage overlap 2. Long-term traffic growth 2. Traffic surge
and DSP are insufficient.
channel 3. Application server problem
2. Air interface resources such 3. Wide coverage
3. Incorrect feeder connection or 4. Abnormal terminals
as RTWP, TCP, CE, and
configuration
code are insufficient.
4. Inter-modulation interference
5. External interference

Long-term traffic Sporadic factors

Resource capacity RF channel Coverage growth and seasonal
user growth Abnormal terminals

Page 22
Classification of UMTS Access Failures Based on Traffic Measurement KPIs

Classify UMTS access failures based on access failure causes to facilitate identifying access failure types and locating problems.
Generally a majority of UMTS access failures are attributed to air interface failure. UMTS access failures in cells with heavy traffic are
generally due to resource congestion.

Classification of
UMTS Access Failure Classification of RRC Connection Failures Classification of PS RAB Setup Failures Classification of CS RAB Setup Failures
Causes
VS.RRC.Rej.DLIUBBandCong VS.RAB.FailEstabPS.DLIUBBand.Cong VS.RAB.FailEstabCS.DLIUBBand.Cong

VS.RRC.Rej.ULIUBBandCong VS.RAB.FailEstabPS.ULIUBBand.Cong VS.RAB.FailEstabCS.ULIUBBand.Cong

VS.RRC.Rej.UL.CE.Cong VS.RAB.FailEstabPS.ULCE.Cong VS.RAB.FailEstabCS.ULCE.Cong
Resource congestion VS.RRC.Rej.DL.CE.Cong VS.RAB.FailEstabPS.DLCE.Cong VS.RAB.FailEstabCS.DLCE.Cong
VS.RRC.Rej.Code.Cong VS.RAB.FailEstabPS.Code.Cong VS.RAB.FailEstabCS.Code.Cong
VS.RRC.Rej.Power.Cong VS.RAB.FailEstabPS.ULPower.Cong VS.RAB.FailEstabCS.ULPower.Cong

VS.RAB.FailEstabPS.DLPower.Cong VS.RAB.FailEstabCS.DLPower.Cong

VS.RRC.FailConnEstab.NoReply VS.RAB.FailEstabPS.RBInCfg VS.RAB.FailEstabCS.RBInCfg

Air interface failure VS.RAB.FailEstabPS.RBCfgUnsupp VS.RAB.FailEstabCS.RBCfgUnsupp

VS.RAB.FailEstabPS.UuNoReply VS.RAB.FailEstabCS.UuNoReply
VS.RAB.FailEstabPS.PhyChFail VS.RAB.FailEstabCS.PhyChFail
Equipment and VS.RRC.Rej.RL.Fail VS.RAB.FailEstabPS.IubFail VS.RAB.FailEstabCS.IubFail
transmission
VS.RRC.Rej.TNL.Fail VS.RAB.FailEstabPS.TNL VS.RAB.FailEstabCS.TNL
problems
Number of attempts-Number of failures- Number of attempts-Number of failures-Failure cause
Other causes Number of attempts-Number of failures-Failure cause values
Failure cause values values

Page 23
End Of The Slide