Beruflich Dokumente
Kultur Dokumente
Knowledge about telecommunications, including the principles of Global System for Mobile Communications (GSM), switching system, Pulse Code Modulation (PCM) and Synchronous Digital Hierarchy (SDH).
Product knowledge, including BSS functional configuration, radio interface theory, calling flow, traffic flow, etc. Related signaling and protocols, including SS7, LAPD, LAPDm, etc. Related international technical specifications. PC network fundamentals, including Ethernet, TCP/IP, Client/Server, database, etc. Skills in BSS routine operation, PC operation and instrument operation.
BSS hardware configuration and performance parameters. Networking topology between BSC and each BTS and multiplexing ratio and trunk mode on the Abis interface. BSS cell distribution and attributes. BSS handover and power control parameters. Network configuration and channel allocation of the related transmission devices.
operation process. The severity trouble should be handled by the personnel who have received Grade B (or above) training from Huawei Technologies Co., Ltd. Besides, the BSS maintenance personnel should also know:
Which operations may cause interruption over part or all of the traffics. Which operations may cause equipment damage. Which operations may cause MS complaints. Which emergency or standby measures are provided.
Test MS Power meter Antenna & feeder analyzer Signaling analyzer Multimeter Oscilloscope Spectrum analyzer Frequency meter
I. Essential
To process the fault, the fault information should be collected first. There are four sources of fault information collection:
Fault complaint from the customer or customer center; Analysis on traffic statistics items; Alarm output of the BSS alarm system; Routine maintenance or abnormality found during the scout
During BSS routine maintenance, most fault information is from the former three sources. However, usually the initially obtained fault information cannot describe the trouble completely and thoroughly, especially when the information is got via a phone call. The information cannot represent the essence of the fault unless it is given in detail. Nowadays, the network size is growing and the complication of networking is
increasing. The change in and interference from the various internal and external factors may constitute a negative impact on the normal running of the BSS. Consequently BSS faults might result from some more complex causes. This makes it more and more difficult to locate a BSS fault. It is no use to just analyze the problem and try to solve it based on the inadequate information. It may enlarge the scope of faults to be located and increase the difficulty of solving them, even lead to the error processing methods, thus losing the best chance to remove the faults. So, it is essential to collect various original informations.
II. Practical
Although there are many factors for the fault of the BSS, they seldom function simultaneously. That is, only some or one of them function(s) at the specified time point. It implements the possibility to locate the fault by using the exclusive method. In the initial stage of fault processing, the collection of original information shall help the maintenance personnel in locating the fault, and improve the efficiency of fault processing, reduce the possibility of error operation, thus making the customer more satisfied.
The maintenance personnel should collect the original information, especially in case of serious fault, so as to perform the next step. The maintenance personnel are strongly recommended to study the system theory, GSM theory, GSM specification and relative signaling knowledge so as to solve the problem as quickly as possible.
When answering the fault complaint call, the maintenance personnel is suggested to gather as much information as possible. The maintenance personnel are also suggested to create the environment with their companion, under which they are able to communicate and ask for help easily.
Handover fault; Congestion fault; Access fault; Voice fault; Call drop fault; Antenna and feeder fault;
The original information analysis is used to judge the fault scope, specify the fault type, and to provide the gist for reducing the fault scope and initial locating of fault. If the maintenance personnel are experienced, they are even able to locate the fault directly. The BSS maintenance personnel usually can get more than what they expect if they do well in collecting the original information and analyzing it effectively and thoroughly. Besides handling the MS related trouble, the original information analysis can also be used to handle other troubles, especially the trunk trouble. Trunk is related to transmission system interconnection and signaling matching; therefore, the original information collection seems to be vital to trunk troubleshooting. Such original information includes the operating status (normal or not) of transmission system, state (modified or not) of data at the peer office, definitions of some signaling parameters, etc.
When the indicator LIU1 is ON, it can be considered that the first E1 cable of the board is not connected with the corresponding BTS. The reason may be that the E1 cable is wrongly connected or that the transmission equipment is erroneous.
When the indicator ACT is ON, it can be considered that the board acts as an active board.
[Notes] The maintenance personnel should be familiar with the meanings of indicator status so as to respond quickly in case of faults.
Transceiver Station), BSC (Base Station Controller), trunk system, etc. [Example] There was a BTS30 with configuration of S(1/1/1). Its three cells were respectively at the frequency of 119, 123 and 105. The call initiated via this BTS had no voice, whether the call was to an MS or to a fixed phone. The troubleshooting process is given below:
1) 2) 3)
At the remote maintenance console, the maintenance personnel viewed the TRX and TMU states and found they were normal and no alarm was generated. Via signaling trace, the maintenance personnel found the call procedure was complete. The BTS was located in the second module of the BSC where the other BTSs were normal. The maintenance personnel checked the BSC data configuration and found no problem.
4) 5)
The maintenance personnel opened the back door of the BTS to check the cables and found everything was all right. The maintenance personnel performed soft & hard reset over the BTS, pulled the TMU out and then reinserted it and reloaded the software. However, the trouble was not removed yet. He then replaced the TMU and TRX, but the trouble still existed.
6)
In the BSC equipment room, the maintenance personnel changed the BTS to another trunk port and found that call can be set up via that BTS with that configuration. The possibility of BTS failure was excluded.
7) 8)
The maintenance personnel pulled out the BIE and then reinserted it, replaced the trunk cable and HW; however, the trouble still existed. The maintenance personnel performed several dialing tests using an MS and found the MS could not be disconnected. He suspected that the problem lied in time slot interchange. As is known, time slot interchange problem is usually caused by E3M or GNET failure.
9)
The maintenance personnel switched over the GNET and found call voice could be heard. When he switched the active GNET back, the call voice disappeared again. He then replaced the active GNET with the standby and found the call voice could not be heard yet. It indicated that the problem lied in both the active GNET and the corresponding slot.
[Notes] The calling test is one of the mostly used methods in the routine maintenance. It is often employed along with the interface message trace, and used widely in the testing of various functions of the BSS.
wave analysis and error code detection, etc. [Example] Call drop rate was high. The troubleshooting process is given below:
1) 2) 3) 4)
The maintenance personnel intercepted the signaling of some dropped calls using MA10. He analyzed the signaling and found the TA approached 63. It indicated that the reason was that the TA was too great. The maintenance personnel modified the data configuration to reduce the cell coverage. Then the call drop rate decreased.
1)
According to the traffic statistics on TCH cell measurement, the number of TCH call drops of the cell 1 under that BTS was 63 and TCH call drop rate reached 3.7%. The number of A interface failures during TCH occupation was 63. The average number of idle TCHs in interference band 3 was 0.94, that in interference band 4 was 0.33 and that in interference band 5 was 1.21. According to the traffic statistics on intracell handover measurement, the number of unsuccessful outgoing BSC handovers of that cell was 35 and the number of unsuccessful incomming BSC handovers of that cell was 12. From the traffic statistics on outgoing cell handover measurement, the maintenance personnel found that the cause of outgoing cell handover was that the uplink quality of that cell was poor.
2)
Since it was after the BTS expansion that the items of the cell 1 under that BTS
indicated worse performance, the problem most probably lied in hardware connection or data configuration.
3) 4)
The maintenance personnel checked the CDUs, TRXs and all RF cables and found they were all properly and securely connected. As the average number of idle TCHs in interference bands 3, 4 and 5 increased from 0 after the BTS expansion, it could be considered that the more A interface failures, lower outgoing/incoming cell handover success rate and higher TCH call drop rate were all related to interference.
5)
The maintenance personnel checked the frequency planning data to see whether there were inter-frequency and co-BSIC adjacent cells and whether the frequency of TCH was adjacent to that of BCCH. No unreasonable setting was found.
6)
The maintenance personnel checked whether the hopping related data configuration was right. For example, he checked whether BCC was identical to the training sequence No. (TSN) and whether the mobile allocation index offset (MAIO) and hopping sequence No. (HSN) were properly configured. He laid the checking emphasis on [Frequency Hopping Table], [Radio Channel Configuration Table], [TRX Configuration Table], [Cell Configuration Data Table] and [Cell Allocation Table].
7)
When checking the [Radio Channel Configuration] Table, he found the MAIOs corresponding to the eight TRXs TRX0, TRX1, TRX2, TRX3, TRX4, TRX5, TRX10 and TRX11 of the cell 1 were respectively 0, 1, 2, 3, 4, 5, 7 and 8. Obviously such setting was erroneous. The maintenance personnel modified the MAIOs respectively to 0, 1, 2, 3, 4, 5, 6 and 7, set the whole table to the specified module and then reset the BTS at the fourth hierarchy.
8)
One hour later, the maintenance personnel viewed the traffic statistics on TCH cell measurement. He found that the average number of idle TCHs in interference bands 3, 4 and 5 was all 0, that the number of A interface failures during TCH occupation was 0 and that the number of TCH call drops was 1. He then viewed the traffic statistics on intracell handover measurement and found that the number of unsuccessful outgoing BSC handovers of that cell was 0 and the number of unsuccessful incomming BSC handovers of that cell was also 0.
9)
When the maintenance personnel performed dialing tests near the BTS, the beep affect disappeared. So the trouble was removed.
[Notes] The traffic statistics analysis is often used along with the signaling trace and analysis, and it plays an important role in high call drop ratio, low handover successful ratio, call abnormality, etc. The maintenance personnel are strongly suggested to master it.
connection and inter-office signaling cooperation, etc. The trace result can help to find the cause of call failure directly and locate the problem or to get the index for the subsequent analysis. [Example] There were two Huawei BSCs (BSC1 and BSC4). The BSC1 was connected with Huawei MSC1 and BSC4 with MSC2 from the manufacturer S. During operation, it was found the BSC4-to-BSC1 handover success rate was over 90% while the BSC1to-BSC4 handover success rate was only about 20%. The troubleshooting process is given below:
1)
During a light traffic period, the maintenance personnel performed a handover test on the site. He traced the signaling on the internal interface and that on the A interface via the maintenance console. Then he analyzed the collected data.
2)
The signaling traced on the user interface of MSC1 was shown in Figure I.1. Upon receipt of the message "Prepare Handover", MSC2 should have returned the message "Prepare Handover ACK"; however it returned the message "Abort" actually.
MSC2
MSC1
Prepare Handover
Abort
10
4)
The maintenance personnel checked the message "Handover Request" from MSC2 to BSC4 and found that MSC2 had transmitted the "Handover Required" message properly and transparently and the speech version information was specified via the channel type. 0B IE 04 Length 01 Speech 08 Full rate TCH channel Bm 91 GSM speech full rate version 2 01 GSM speech full rate version 1 The message "Handover Request ACK" BSC4 returned to MSC2 upon receipt of that message from MSC2 contained the following: Layer 3 information: 17 0D 06 2B 38 51 0C 00 0C B3 05 DB 63 01 90 Chosen encryption algorithm: 2C 01 Layer 3 information of the message indicated the Channel Mode: 63 IE 01 Speech Full rate TCH or Half Rate version 1 Then MSC sent the message "Clear Command" to BSC with "Cause: Protocol Error between MSC-BSC". Since the phase version of the A interface between MSC2 and BSC4 was Phase 2, analysis over the signaling on the A interface should be based on Phase 2 protocol. The difference between successful signaling and failed signaling lies in the speech version in channel type. So MSC2 expected the message "Handover Request ACK" returned from BSC4 could further indicate the speech version information. However, as is specified in Phase 2 GSM 08.08 protocol, the message "Handover Request ACK" contains no speech version information but the Channel Mode information that is indicated in Layer 3 information. However, according Phase 2+ protocol, the message "Handover Request ACK" should contain the "Speech Version (Chosen)" when BSS selects a speech version. Details are cited below. (See "GSM 08.08 version 7.6.0".) 3.2.1.10 HANDOVER REQUEST ACKNOWLEDGE This message is sent from the BSS to the MSC and indicates that the request to support a handover at the target BSS can be supported by the BSS, and also to which radio channel(s) the MS should be directed. The message is sent via the BSSAP SCCP connection associated with the dedicated resource. INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN Message Type 3.2.2.1 BSS-MSC M 1 Layer 3 Information 3.2.2.24 BSS-MSC M (1)11-n Chosen Channel
11
3.2.2.33 BSS-MSC O (4) 2 Chosen Encryption Algorithm 3.2.2.44 BSS-MSC O (5) 2 Circuit Pool 3.2.2.45 BSS-MSC O (2) 2 Speech Version (Chosen) 3.2.2.51 BSS-MSC O (6) 2 Circuit Identity Code 3.2.2.2 BSS-MSC O (3) 3 LSA Identifier 3.2.2.15 BSS-MSC O (7)5 1 This information field carries a radio interface HANDOVER COMMAND message. 2 Shall be included when several circuit pools are present on the BSS MSC interface and a circuit was allocated by the HANDOVER REQUEST message. 3 The Circuit identity code information element is included mandatorily by the BSS if the BSS allocates the A interface circuits and a circuit is needed. 4 Included at least when the channel rate/type choice was done by the BSS. 5 Included at least when the encryption algorithm has been selected by the BSS. 6 Included at least when the speech version choice was done by the BSS. 7 Shall be included if a new potential current LSA in the target cell has been identified (see GSM 03.73). Not included means that there is no potential current LSA in the target cell. Based on the above analysis, it could be concluded that the A interface phase version configured at MSC2 was different from that configured at BSC4 or that MSC2 processing on Phase 2 protocol was erroneous.
5)
The
maintenance
personnel
modified
the
interface
phase
version
configurations at those two sides and made them consistent with each other. From the traffic statistics, the maintenance personnel found the BSC1-to-BSC4 handover success rate became over 90%. So the trouble was removed. [Notes] The interface trace is able to locate the fault cause accurately and provide the valuable reference information, it is one of the widely used method in the BSS routine maintenance and fault processing.
12
[Example] One office was to be expanded. During the expansion process, the office maintenance personnel decided to add an SS7 link with SLC of 2 (consistent with that at MSC) besides the expanded parts. The maintenance personnel then manually modified the data. After resetting the whole BSC, the maintenance personnel found the links configured automatically were all normal while the one added manually could not be established. Three data tables were modified manually on the site: [E3M E1 Configuration Table], [MTP Link Table] and [Trunk Circuit Table]. The troubleshooting process is given below:
1)
The maintenance personnel checked the related data and found that all data was right. The link was configured in the FTC 13. The maintenance personnel checked the [Trunk Circuit Table] and found that all the time slots with No. of 16 in the corresponding TCSM were properly set as Unavailable and they were described to act as A or Pb interface signaling links. The SS7 link run through the port 1 in the last BIE and it was configured to involve the time slot 16; therefore, the corresponding trunk circuit No. was right 2096.
2)
The other two links in that module run through the port 0 in the transparent transmission BIE and were normal. The maintenance personnel suspected that the problem lied in the port 1. He replaced the port 0 with the port 1, modified the corresponding data configuration and set the whole table. The latter two links were still normal. The possibility of port 1 failure was excluded.
3) 4) 5) 6) 7)
Via check, the maintenance personnel found the FTC indicator was in the normal state and that circuits of the FTC 13 were all normal. The maintenance personnel looped back the BIE and found the link was normal. He looped back the E3M and found the link was also normal. Then he looped back the FTC and found the link was abnormal now. It indicated that the problem lied in the parts between the E3M and TCSM. The maintenance personnel suspected that data configuration in AM/CM was wrong. He vied the Host and found the SS7 that should have been added to the [E3M E1 Configuration Table] was not added. It indicated that the data was not written into the Host. It could be concluded that the problem lied in the DIP switch.
8)
The maintenance personnel checked the GMCC DIP switches in AM/CM and found the DIP switches with name of S1-2 and S1-4 were all set to ON (indicating that frozen data should be used). The maintenance personnel modified the DIP switches with name of S1-2 and S1-3 to ON and those with name of S1-4 to OFF. After he reloaded the data, the SS7 link became normal.
[Notes] The test and loop back methods are usually employed along in the location of transmission fault. The loop back can be classified into hardware loop back and software loop back. The operation of software loop back is simple and flexible, but its reliability is not as good as the hardware loop back. In addition, the BSS trunk self loop is also often used to judge whether the parameters of local office and the
13
outgoing route data are set correctly during the office deployment and trunk expansion.
1.3.9 Comparison/Interchange
Comparison is to compare the faulted components or phenomenon with the normal ones, and find the differences so as to find the problem. It is usually used in the situation with simple fault range. Interchange is to interchange the normal components (such as board, optical fiber, etc.) with the potential faulted components if the fault range or part can not be located even after the standby components are replaced, and to compare the work status change after the interchange so as to specify the fault range or part. It is usually used in the situation with complicated fault range. [Example] During power-on commissioning over one BSC, the maintenance personnel found the GALM in AM/CM was displayed in red (indicating the faulty state). When the alarm box was powered on, it was still in red and the GALM communication alarm was generated additionally. The troubleshooting process is given below:
1) 2)
The maintenance personnel checked the data and found no problem. It is normal that the GALM in AM/CM is displayed in red when the alarm box is not powered on. The maintenance personnel powered on the alarm box; however, the GALM was still displayed in red and the trouble still existed.
3) 4)
The maintenance personnel viewed the DIP switch of the alarm box and found no problem. The maintenance personnel then checked whether the GALM was faulty by replacing the GALM in AM/CM with that in BM. He performed the replacing by modifying the GALM related DIP switch & jumper settings. Note: the AM/CM and BM use the same type of GALM except that the GALM related DIP switch & jumper settings of them are different. After replacing, the GALM in AM/CM was still displayed to be faulty.
5)
The GALM in AM/CM may be displayed in red when communication between it and alarm box interrupts. The maintenance personnel suspected the problem lied in the signal cables of the alarm box. He replaced the alarm signal cables in BM with those in AM/CM. Now the GALM in AM/CM became normal.
6)
Then the maintenance personnel checked the alarm signal cables carefully. He found the alarm signal cables in AM/CM were mixed up with those in BM. That was the reason why the communication between GALM in AM/CM and alarm box interrupted and GALM was displayed in red. The GALM in BM could not be displayed in red though its communication with the alarm box also interrupted because it itself operated normally.
[Notes] In the actual fault location, various methods are used together, and in the above example, the methods of loop back, interchange, test and comparison are all used.
14
We can see that the master of various methods will be quite helpful for the fault processing.
Caution: It should be pointed out that the interchange is of a little risk, for example, after the short-circuited board is put to the normal frame, the normal frame may become faulted. So, cautions should be exercised in performing the interchange method so as to avoid new fault.
1.3.10 Switching/Resetting
Switching is to perform the manual switching for the switching device under the active/standby work mode, that is to forward the services from the active device to the standby. Compare the running status of the device after the switching to confirm whether the active device or the active/standby relationship is normal or not. Resetting is to restart manually some the whole switching device or some parts of it. It is used to exclude software running is confused. The switching and resetting can not locate the fault cause accurately, and due to the randomness of software running, the fault may be not able to re-occur after the switching or resetting, thus it is difficult to know the real fault and solve the problem. So, this method is just an emergency method, applicable only in the emergent situation.
Caution: Back up the main control boards before switching them so as to avoid the losing of system data. Because the resetting often interrupt the system service, even makes the system down due to the error operation, which will bring the severe negative consequences for the routine running of the BSS. So, the operation of switching and resetting is quite restricted, and is not recommended to use it.
15
Time of fault occurring Detailed description of fault Software version of the office or site Actions performed after the faults occurring and the results Problem level and the time you wish to solve the problem
We shall arrange our engineers to process your problems. In addition, you can get the latest technical documents from our technical support website: http://support.huawei.com.
16