Professional Documents
Culture Documents
Operation Guide To Solving The TCH Assignment Failure: Huawei Technologies Co., LTD
Operation Guide To Solving The TCH Assignment Failure: Huawei Technologies Co., LTD
2005-11-23
Page1 of total13
Revision Record
Date 2002-11-12 2003-12-19 Version 1.00 Description Initial draft finished Condense the draft and add section 3.3 and 3.4 Author Assignment team Assignemtn team
1.01
2005-11-23
Page2 of total13
1 Instruction
This guide provides operation instruction to solve the on-site assignment problems. It gives the items that require feedback information. The on-site engineer is required to fill in the feedback information. It takes about five to fifteen minutes to finish all the items in this compact operation guide .
1. Judging from the Abis signaling, when a MS is assigned (immediate assignment) with a faulty TCH (SDCCH), the MS cannot access to the new channel, leading to TCH (SDCCH) seizure failure. 2. Judging from traffic statistics, TCH congestion rate (please refer to appendix for congestion rate judgment) suddenly exceeds 15% or successful SDCCH seizure times are low in a certain cell. After block faulty TRX or channel, congestion rate becomes normal. 3. Another problem is assignment failure occurs in some TRXs while other TRX assignments in the same cell are normal. 4..The problem can be solved by software resetting TRX. (Do not reset TRX when problem occurs and keep the site.)
2005-11-23
Page3 of total13
Note Do not reset TRX when problem occurs. Please call BSS deployment maintenance hotline: 008613601684779.
3 Operation Steps
3.1 Confirming software version of BTS by checking board information
Result:
For the signaling tracing in maintenance console, the tracing unit is TRX. Open more windows and trace all TRXs of the cells with problems respectively.
Signaling tracing must trace enough assignment failure signaling for analysis afterwards. Tracing time is flexible. As maintenance console has a limitation on the number of signaling in signaling tracing (2000 at most, the number is shown on the left), please save the signaling after each step of signaling tracing to avoid overwriting.
In signaling tracing, on noticing the number of signaling close to 2000,save the signaling and close the window. Open a new window to trace signaling and do the following operations while tracing. Result: See attachment
Attachment:[signaling file *.gmt] Attachment description:(Describe the attached file or attach a readme.txt file here.)
2005-11-23 All Rights Reserved Page4 of total13
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
2) Use the Abis message tracing function of the OMC Shell to trace signaling flow on the TRX and send the traced signaling result back. If problem still exists, go on with the following operations. (Note: Please refer to appendix to judge whether the problem is solved or not). Problem solved or not:[ ]
(Fill with Y or N. No matter problem is solved or not,
please attach the traced signaling result in attachment area) 2005-11-23 All Rights Reserved Page5 of total13
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file.)
Note: In self-define message, the red part is cell number (hexadecimal); the blue part is TRX number (hexadecimal). 2) Use the Abis message tracing function of OMC Shell to trace the signaling flow on the TRX and save the traced result. If the problem still exists, go on with the following operations. (Note: Please refer to appendix to judge whether the problem is solved or not.) Problem solved or not:[ ]
(Fill with Y or N. If solved, please attach the traced
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
2) Use the Abis message tracing function of the OMC Shell to trace the signaling flow on the TRX and save the traced result. If the problem still exists, go on with the following operation.
2005-11-23
Page6 of total13
(Fill with
Y or
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
2005-11-23
Page7 of total13
3) See if the problem is solved or not. If it is, use the Abis message tracing function of OMC Shell to trace signaling flow of this TRX and send the signaling tracing result back. 4) if the problem still exists, go on with the following operation. Problem solved or not:[ ]
(Fill with Y or N. Please attach the signaling and the
obtained physical configuration in attachment area. If problem solved, please do the operation again. Attach the signaling and re-obtained physical configuration in attachment area.)
Remark: Attachment 1:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
2005-11-23
Page8 of total13
flow of this TRX, send the signaling back and save it; if not, go on with the following operation. Problem solved or not:[
attachment area)
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
2005-11-23
Page9 of total13
3.13
Remark: Attachment:[gmt file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
3.14 Power off or Power on again the Faulty TRX in Peer End, If the Problem Still Exists, Replace the TRX.
Problem solved or not:[ Remark: ]
(Fill with Y or N.)
.1 Basic Information
BSC software version number:( )
Attachment description:(Describe the attached file or attach a readme.txt file here.) Data configuration:(Compress all OMC\BSC\BAM\DBF\*.* files and attach them in attachment area.) Attachment:[dbf file] Attachment description:(Describe the attached file or attach a readme.txt file here.) Log: Having obtained base station log in OMC Shell, save the log file in the following directory: OMC\BSC\BAM\WARN\DEBUG.LGDEBUG.LG1 DEBUG.LG2DEBUG.LG3 DEBUG.LG4 Please attach DEBUG.G, UG.LG1, UG.LG2, UG.LG3 and DEBUG.LG4 in the attachment area. Note: Please extract the faulty station log at the time when the traffic volume is not so high before obtaining base station working log. Attachment:[log file] Attachment description:(Describe the attached file or attach a readme.txt file here.) Alarm: Alarm files is usually saved in the following directory:OMC\BSC\BAM\WARN\HISTORY\*.WRN. Pleas attach alarm files in the attachment area. Attachment:[alarm file] Attachment description:(Describe the attached file or attach a readme.txt file here.)
Description: a. BTS type: BTS312BTS20BTS30BTS3001C BTS22C BTS30A or BTS3012A b. BTS configuration: S?/?/? or O?, etc.
2005-11-23 All Rights Reserved Page11 of total13
c. Faulty cell or TRX description: name of the faulty cell, serial number of the faulty TRX, and the severity of the problem, etc. d. If the number of faulty stations exceeds three, down extend the table.(Same in the following form)
2005-11-23
Page12 of total13
2005-11-23
Page13 of total13