Professional Documents
Culture Documents
Course Purpose:
Grasp the means of interface trace and the method of analyzing it to aid us for fault handling.
How to learn this course:
Copy the interface trace result files. Use the maintenance consoles interface trace review function to study,
Attention:
It is strictly forbidden to use the interface tracing function when the system is busy or the system is under heavy duty.
Page 2
Chapter 1 Location Update Flow Chapter 2 Call Setup (Originating) Chapter 3 Intra-BSC Handover Chapter 4 Inter-BSC Handover Chapter 5 BSC Normal Release Chapter 6 BSC Local-end Release
Page 3
Page 4
Reference
BSC
MSC
The message number in this page is the SN of the messages in the result file.
CC
Location Updating Accepted (10) TMSI Reallocation Complete(NOTE 2) (11) (NOTE 1)
SABM: Set asynchronous balanced mode command--Initial access frame UA: Unnumbered acknowledgement response
(NOTE 3)
Clear_CMD Clear_CMP
Page 5
Notes
TMSI. When VLR cannot identify the TMSI or TMSI authentication fails, MSC will start Identification flow. That means MSC will send transparent transfer message Identity Request to MS and MS will report Identity Response message which involves IMSI.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 6
Notes
NOTE 2:
NOTE3:
In this flow we have simplified the release flow. To know
Page 7
Abnormal Occasion
BSC receives Location Updating Rejected message from
MSC. The possible reason is listed below: A. MSC has not configured the CGI which has been configured in BSC. B. Communication failed between MSC and VLR. C. MS has not been registered in HLR.
Page 8
BTS
MSC
IMMEDIATE ASSIGN COMMAND (3) First SABM Establish_IND(CM Service Req) (5) CR(Complete_L3_information) (0) CC (1) CM Service Accepted (9) (NOTE 1) (2) (3) Setup (10) (4) Call Processing (11) Assignment_Req (5) Channel_Active (NOTE 2) (12) Channel_Active_Ack (13) ASSIGNMENT COMMAND (14) First SABM Establish_IND (18) ASSIGNMENT CMP (23) Assignment_CMP (7) Alerting (40) Connect (63) (18) Connect Ack (65) (19) (NOTE 3) (21) Conversation Disconnect (200) (24) Release (201) (25) Release Complete (203) (28) Clear_CMD (32) (NOTE 4) Clear_CMP (33)
Page 9
1. Authentication, encrytion, identification are optional. See Note 1 in Location Update Flow.
2. Class mark update flow: For dual-band MS, after the SCCP connection is established and before receiving message "CM Service Accepted" there will be a class mark update flow. CR message reports the information of class mark 2. And in the class mark update flow, MS will report class mark 3 information which is related to the dual-band capabilty.
Page 10
In Immediate Assignment TCH is directly assigned. When MSC sends Assignment _Req message, BSC will not assign new channel but perform Mode Modify flow. After Mode Modify BSS will report Assignment _CMP message to MSC.
Page 11
Abnormal Situation
Abnormal Occasion 1: MSC has sent Assignment_Req and
BSC does not send ASSIGNMENT CMD but sends a Assignment_Fail message. Possible reason: A. BSC has not available TCH. B. The CIC assigned by the MSC is not idle in BSC. C. There are transmission faults or interference in the uplink. BTS cannot receive the uplink signal correctly.
Abnormal Occasion2: BSC has sent ASSIGNMENT CMD
message but MS sends ASSIGNMENT FAIL. Possible reason: Downlink bit error rate is too high.
Page 12
Channel_Active_Ack (125)
HANDOVER COMMAND (126) Handover Access Handover_Detect (127) PHYINFO PHYINFO First SABM Establish_IND (128) HANDOVER COMPLETE (132) Handover_Performed (NOTE 2)
Page 13
Notes
BTS1 and BTS2 belong to the same base station. Actually they are too cells of one base site. In such occasion there will not be PHY INFO message, After Handover Access message, MS will send SABM very rapidly.
NOTE2
After reporting Handover_Performed message to MSC, BSC will
start the local-end release flow for the previous channel (in BTS 2).
Page 14
Abnormal Occasion
Abnormal Occasion
sent PHY INFO message to the maximum time but still cant the MS access the new channel, BTS1 will send CONN FAIL IND message. Its causing value is handover access failure.
Page 15
MSC
BSC2
BTS2
MS
PHY INFO
PHY INFO First SABM Establish_INO HANDOVER COMPLETE
Handover_Cmp
Page 16
Notes
Two BSCs do not belong to the same MSC. The A-interface messages are same for the two occasions above.
NOTE2
When BSC1 receives Clear_CMD message from MSC it will start local-
Page 17
BTS
(NOTE 1) Disconnect
BSC
(200)
MSC
Release
(201)
Release Complete (203) Clear_CMD CHANNEL RELEASE First DISC UA (204) Clear_CMP
Page 18
Notes
NSS originating release MS originating release In these two different occasions all the messages are
Page 19
BTS
BSC
MSC
Page 20
Case Description
BTS sends several EST IND messages. Later MS sends ASSIGNMENT FAIL message and the causing value is Protocol error unspecified.
Page 21
Case Analysis
Case Analysis
message to BSC. So we know now that the MS must have sent many SABM frame to the BTS.
BTS can decode the SABM frame sent by MS but MS cannot
decode the UA frame sent by BTS. And this causes that the BTS reports many EST IND messages.
Page 22
Case Analysis
Case realize:
In
the lab we can simulate. Disconnect the TX antenna to make the downlink signal pure. Trace the A-bis signaling we can find that BTS sends several EST IND messages to BSC for the newly assigned TCH but cant succeed. And then MS sends ASSIGNMENT FAIL via the previous SDCCH and the causing value is Protocol error unspecified.
Conclusion:
In the field when it appears many ASSIGNMENT FAIL messages, the main reason might be the pure downlink receiving power level or receiving quality. Connection between TRX and SCU (CDU).
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 23
3 (m m 5)W W ( ) 3 4 7 d B3 6 d B 2 4 (m 2) W 3 3 d B 5W 0m .2 8) ( 9 d B 2 2
Page 24
Page 25