DT Events & Layer3 Messages

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 14

Layer 3 Messages for Call Attempt Event

Layer 3 Messages for Call Attempt Event


Layer 3 Messages for Call Setup & Call Established Event
When Ms put a request to BTS for channel Request, BTS assign First One
SDCCH in DL See in Slide One
After assigned SDCCH MS go in Dedicated mode See in Slide Two
After some process BTS give TCH Assignment command in DL and MS give its
completion command in UL See in Slide Two
Still MS is in Dedicated mode.. See in Slide Two
During this time BTS is doing some process and MS is waiting for Connect
command form BTS in DL
When MS will got Connect command from BTS in DL, it count as a Call Set up
Event .. See in Slide Three
Now MS will give Connect Acknowledge to BTS in UL, and it count as a Call
Established Event .. See in Slide Three
But in some cases Due to Interference or LAPD or some Protocol error after
receiving Assignment command form BTS, MS can receive Connect command
This cause some difference in Call Attempt and Call Established Event and this
is directly affect to Our Call Setup Success Rate (CSSR)
You can see some of example of Call Established failure in Next slide




Some Layer 3 message that cause for Call Establishment
Failure
T200 expired is some Protocol error due to Interference or LAPD Error
See Radio parameter at this time in next slide
High FER and Bad Rx Quality
Here After Assignment Complete .MS received Disconnect message in DL
Example of Human or Tems Operation Error
Here MS2 is already in Idle mode
He is giving Cell reselection Event..
But after that with out any Call Attempt and Call Established it give
Dropped Call Event
This can be happen due to above Recording Paused and Resumed the
Log file and at the same time mobile script is running
Example of Human or Tems Operation Error
Here MS1 is in Dedicated mode, It is Attempting Handover successfully
Then it give Dropped Call Event, and after call is dropped it still give
Handover Event..

MS1 has completed
the Intracell Handover
Above error makes big impact in our KPI
In BSC Drive test Round 7 we found total 6 Dropped call
(For Short call Only) and in Round 8 we found total 11
Dropped call (For Short call Only)
Big Difference in
Dropped Call
Rate
With Errored
Dropped Call
Without Errored
Dropped Call

You might also like