CN1859682A - Irregular frequency hard switching fault analyzing method - Google Patents
Irregular frequency hard switching fault analyzing method Download PDFInfo
- Publication number
- CN1859682A CN1859682A CNA2005100363561A CN200510036356A CN1859682A CN 1859682 A CN1859682 A CN 1859682A CN A2005100363561 A CNA2005100363561 A CN A2005100363561A CN 200510036356 A CN200510036356 A CN 200510036356A CN 1859682 A CN1859682 A CN 1859682A
- Authority
- CN
- China
- Prior art keywords
- information
- alien frequencies
- accordingly
- cut operation
- failure
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention discloses pilot frequency hard switching fault analysis method for analyzing hard switching fault reason. It contains providing ought to outputting message when pilot frequency hard switching failing fault occurring to analyze fault reason, these message including type of message, IMSI, optima cell message, pilot frequency neighbouring areas message, pilot frequency hard switching fault reason, active set message, wireless accessing bearing message, target cell message, and pilot frequency hard switching trigger etc; and providing analyzing fault reason method from these message.
Description
Technical field
The present invention relates to the handoff technique in the mobile communication, particularly the alien frequencies hard-switching technology of broadband CDMA system.
Background technology
WCDMA (Wideband Code Division Multiple Access, be called for short " WCDMA ") be one of international standard of International Telecommunications Union's (International Telecommunications Union is called for short " ITU ") Global 3G mobile communication of admitting. Also can be described as the 3-G (Generation Three mobile communication system) that puts it into commercial operation the earliest in the world, is the standard of European 3-G (Generation Three mobile communication system) FDD (Frequency Division Duplex is called for short " FDD ") frequency range simultaneously. Because UMTS adopts WCDMA (Wideband Code Division Multiple Access is called for short " WCDMA ") air interface technologies, therefore, usually also the UMTS system is called the WCDMA communication system.
As shown in Figure 1, the UMTS system has adopted and the similar structure of second generation mobile communication system, by subscriber equipment (the User Equipment such as cell phone, portable computer, vehicular phone, be called for short " UE "), be responsible for processing all and UMTS grounding wireless access network (the UMTS Terrestrial Radio Access Network of wireless relevant function, be called for short " UTRAN "), and be responsible for to process that all voice calls are connected with data in the UMTS system, and the core net of the exchange of realization and external network and routing function (Core Net is called for short " CN ") consists of.
Wherein CN is from being divided in logic circuit switching (Circuit Switching is called for short " CS ") territory and packet switch (Packet Switching is called for short " PS ") territory.
And UTRAN comprises one or several RNS (Radio Network Subsystem is called for short " RNS "). As shown in Figure 2, each RNS is comprised of a radio network controller (Radio Network Controller is called for short " RNC ") and one or more base-station node (Node Base Station is called for short " NodeB "). Wherein, be connected by the Iu interface between RNC and the CN; NodeB is connected Iub interface with RNC and connects; Connect by the Iur interface between the RNC, the Iur interface can connect by the connection of the direct physical between the RNC or by transmission network to be realized.
In said structure, RNC is responsible for distributing and is attached thereto with control or the Radio Resource of relevant NodeB, in other words, namely be responsible for the Radio Resource of control UTRAN, mainly finish the functions such as connection foundation and disconnection, switching, the merging of grand diversity, RRM control.
NodeB then is responsible for finishing the conversion of the data flow between Iub interface and the UU interface, also participates in a part of RRM simultaneously. Specifically, it comprises radio receiving-transmitting unit and Base-Band Processing parts, as mentioned above, by Iub interface and the RNC interconnection of standard, mainly finishes the processing of UU interface PHY. Its major function is spread spectrum, modulation, chnnel coding and despreading, demodulation, channel-decoding, also comprises the functions such as mutual conversion of baseband signal and radiofrequency signal.
After the UE start, just begin to receive the service of network side after resident in a residential quarter, such as receiving system message and paging receiving message. When UE called or receive calls, UE will make a call in this residential quarter so, and triggered the flow process of series of standards interface.
After accessing successfully, the user just is initially located in talking state, while but many times the user is a difference of mobile phone and landline telephone (Here it is) making a phone call to move. For wireless communication system, each residential quarter is that certain coverage is arranged, user's number is relevant in the transmitting power of this coverage and NodeB and the residential quarter, in general at the edge of residential quarter, because path loss is very large, so the signal that UE receives is generally all more weak, NodeB receives that the transmitting power of UE also can be very weak accordingly simultaneously, what will cause like this that the user's communication quality becomes is very poor, in addition because signal is too weak call drop.
In other words, the overlay area of a NodeB is limited, and along with the movement of UE, for keep communicating by letter continuously, UE and internetwork wireless connections must be transferred to the another one residential quarter by a residential quarter, switching that Here it is. In the WCDMA system, switch and comprise direct-cut operation, soft handover and intersystem handover.
Direct-cut operation is an important component part in the mobile management of 3G system. Direct-cut operation refers to that UE is in the switching of alien frequencies neighboring interval, at this time UE can increase link in current alien frequencies adjacent area first, after new link establishment is finished, just can discharge the link in the original residential quarter, do like this continuity that has kept on the one hand conversation, increased the covering of network, discharged simultaneously original link, reduced taking wireless and transfer resource, the alien frequencies direct-cut operation is to solve the important method that wireless network covers, and it comprises: the alien frequencies direct-cut operation in two residential quarters of same NodeB; Same RNC, the alien frequencies direct-cut operation between the different N odeB; Alien frequencies direct-cut operation between different RNCs.
In the process that direct-cut operation is processed, RNC, NodeB and UE three part network elements have been related to, owing to exist some accidents or deviant circumstance causes direct-cut operation to be processed unsuccessfully: congested or the Target cell quality is too poor such as the Target cell of switching, because the appearance of this situation, cause handoff failure, and then may cause call drop.
In the process of wireless network operation; especially at the networking initial stage, often this problem can occur, the agreement of 3GPP does not have corresponding consensus standard to this TRACE simultaneously; how to carry out agreement output so that location direct-cut operation failure problems can become an emphasis in the process of network operation.
The below introduces failure analysis methods commonly used in several prior aries:
One, performance statistics function.
Performance statistics is the quality of weighing current network by statistical items crucial in the statistics network, the method is statistics direct-cut operation success/frequency of failure within a specific measuring period, and this statistical value fed back to NMS, comprehensively analyzed by NMS, instruct dilatation and problem to existing network to solve by analysis result.
Two, the whole network signaling test method.
The method of signaling tracing be by the signaling tracing instrument in standard protocol interface (such as UU, IUB) follow the tracks of calling procedure in especially from the standard agreement message in the different network elements, and the message that these are relevant sends to network management center, analyze by the message that these are caught, according to analysis result network is optimized, solves simultaneously subproblem.
Three, alarm.
NMS can be carried out eliminating and the management of network failure to processing and the analysis of warning information. When system broke down, the reason that warning system can be real-time produces alarm sent to NMS, and NMS can be analyzed and gets rid of the fault that occurs according to the reason that produces alarm and equipment.
In actual applications, there is following problem in such scheme: efficient looking up the fault reason. Specifically, for the performance statistics function, performance statistics is a kind of long-time, or perhaps a kind of statistical function of periodic duty, how many statistics direct-cut operation success rate or mortalitys be within a period of time, this statistics itself is just very coarse, and this function is the statistical history data, can not carry out anomaly analysis to the reason that direct-cut operation breaks down. If improve the dynamics of performance statistics, increase the statistics to the direct-cut operation failure cause, will certainly cause the appearance of mass data, influential to regular traffic. For the whole network signaling test method, this is a kind of real-time tracking, need to all to follow the tracks of by special third party's instrument at all interfaces, this tracking can produce a large amount of data, present 2G total network signalling tracing has just been followed the tracks of the message between net, namely the message of core net part is not followed the tracks of the Access Network part. For the 3G system, these tracking messages will be magnanimity, especially if follow the tracks of the message of Access Network part. How to obtain Useful Information from a large amount of message is followed the tracks of, will be very large workload. Need also that by signaling tracing very rich experience is arranged in addition, the problem that exists in the discovery message that can be very sharp, this method also are not easy to promote in the attendant. For alarm, what in general alarm was paid close attention to all is equipment fault, fewer to the concern of user malfunction. When breaking down owing to wireless reason causes switching such as the user, be to embody in alarm. So alarm can not reflect or solve the problem of switching appearance basically.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of irregular frequency hard switching fault analyzing method, so that can analyze efficiently the failure cause of alien frequencies direct-cut operation.
For achieving the above object, the invention provides a kind of irregular frequency hard switching fault analyzing method, comprise following steps:
When the failure of alien frequencies direct-cut operation or when breaking down, the information of the equipment output specified type of control handoff procedure;
According to the information of described specified type, analyze the reason of described alien frequencies direct-cut operation fault.
Wherein, described method is applied to broadband CDMA system, and the equipment of described control handoff procedure is radio network controller.
In this external described method, the information of described specified type comprises:
International mobile station identity number can be analyzed accordingly and learn the user of breaking down;
Optimum subdistrict information can be analyzed accordingly and learn that residential quarter best for the subscriber equipment signal when breaking down, this residential quarter also are the residential quarters of serving for this subscriber equipment at that time;
The alien frequencies neighboring BS information can be analyzed accordingly and learn the adjacent area that might carry out the alien frequencies switching when alien frequencies direct-cut operation occurs;
Alien frequencies direct-cut operation failure cause can be analyzed the reason of the alien frequencies direct-cut operation failure that the system of learning provides accordingly.
In this external described method, described radio network controller sends to operation maintenance center by message with the information of described specified type, comprises type of message in this message;
Described operation maintenance center parses the information of described specified type according to described type of message from the message of receiving.
In this external described method, described alien frequencies direct-cut operation failure cause further comprises one of following information or its any combination:
The call admission failure can be analyzed the reason that causes the Target cell failure when alien frequencies direct-cut operation occurs accordingly;
Agreement or do not mate the message error reason can be learnt in the message from other network element to have mistake accordingly;
The ASN1 error reason can be learnt the requirement of not satisfying encoding and decoding from the message of other network element accordingly, needs further to check that corresponding network element is to confirm reason;
Layer 2 configuration error reason, possible problem is Frame Protocol fault or inadequate resource;
Access link configuration error reason can be analyzed the further reason that radio network controller goes wrong accordingly when the configuration transport layer;
The wireless link failure cause can be analyzed the reason of learning the NodeB failure accordingly;
Wireless link is overtime, accordingly the fault of check system scheduling message or IUB interface link;
The access link mobile network strengthens the customization applying portion carrying of logic and sets up failure cause, can analyze accordingly fault to have occurred when setting up what process;
Atm adaptation layer 2 is set up failure cause, whether can analyze accordingly because the transport layer fault causes;
The Frame Protocol synchronization failure can be analyzed generation problem when up or descending accordingly;
Physical channel reconfiguration failure reason can be analyzed accordingly and learn why subscriber equipment can return physical channel reconfiguration failure message;
Physical channel is reshuffled overtime, can further analyze accordingly to cause this overtime reason;
IUR interface wireless link establishment failure cause can be known when striding the alien frequencies direct-cut operation of IUR interface to go wrong accordingly;
The link establishment of IUR interface wireless is overtime, can know accordingly when striding the alien frequencies direct-cut operation of IUR interface to go wrong.
In this external described method, described call admission failure further comprises one of following information or its any combination:
The transmission power level of NodeB and total received power in broadband value, congested if the residential quarter occurs, can analyze accordingly the residential quarter congested reason occurs;
The cell downlink spreading factor is unavailable, can know accordingly that one of reason of causing the call admission failure is that the descending spreading factor applied for is not supported in present residential quarter;
The cell uplink spreading factor is unavailable, can know accordingly that one of reason of causing the call admission failure is that the up spreading factor applied for is not supported in present residential quarter;
The residential quarter credit rating do not support, can know accordingly that one of reason of causing the call admission failure is that the credit information of current NodeB is not enough, can check further whether the credit information of NodeB is reasonable;
IUB interface transfer resource is unavailable, can know accordingly the bandwidth that needs the corresponding IUB interface of increase system;
IUR interface transfer resource is unavailable, can know accordingly the bandwidth that needs the corresponding IUR interface of increase system.
In this external described method, the information of described specified type also can comprise following a kind of or its any combination:
RAB information wherein comprises the speed of various RAB information;
Active set information if at least two residential quarters are arranged in the active set, illustrates that then subscriber equipment is in soft changing state before the alien frequencies direct-cut operation occurs;
Whether target cell information is normal as the residential quarter of switching target in the time of can analyzing accordingly the generation of alien frequencies direct-cut operation;
Alien frequencies direct-cut operation trigger can be analyzed the reason that triggers the alien frequencies direct-cut operation accordingly.
In this external described method, described target cell information is divided into increases cell information and deletion cell information two classes, and each class further comprises again following information:
The sign of Target cell can be analyzed the position that the alien frequencies direct-cut operation occurs accordingly;
Cell synchronization information, the accordingly timing relationship between evaluating objects residential quarter and the optimum subdistrict.
In this external described method, described optimum subdistrict information, active set information and alien frequencies neighboring BS information comprise one of following information or its any combination:
Cell ID can know accordingly which residential quarter is problem occur in;
The Ec/No of CPICH Common Pilot Channel, the RSCP of CPICH Common Pilot Channel can know cell signal quality at that time accordingly.
In this external described method, described alien frequencies direct-cut operation trigger further comprises one of following information or its any combination:
Based on the information of coverage, comprise the switching of periodic measurement triggering and the switching of Event triggered;
Information based on load;
Information based on blind switching.
By relatively finding, the main distinction of technical scheme of the present invention and prior art is, when the failure of alien frequencies direct-cut operation or when breaking down, the information of equipment (such as RNC) the output specified type of control handoff procedure, network management center (such as OMC) is analyzing failure cause accordingly. The information of the specified type of output comprises: type of message, IMSI, optimum subdistrict information, alien frequencies neighboring BS information, alien frequencies direct-cut operation call drop reason, active set information, RAB information, target cell information, alien frequencies direct-cut operation trigger etc.; Also pointed out simultaneously how to utilize these information to carry out accident analysis.
Difference on this technical scheme, brought comparatively significantly beneficial effect, namely the information because of specified type has covered the every aspect relevant with the alien frequencies direct-cut operation, thus can help the webmaster personnel effectively to analyze out of order reason, and then take corresponding corrective measure.
Because only output information just in the failure of alien frequencies direct-cut operation or when breaking down so the added burden that whole GSM is increased is very little, can process to the regular traffic of system exerting an influence hardly.
Description of drawings
Fig. 1 is UMTS system architecture schematic diagram;
Fig. 2 is the UTRAN structural representation;
Fig. 3 is the schematic flow sheet according to the irregular frequency hard switching fault analyzing method of the first embodiment of the present invention.
The specific embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with accompanying drawing.
Generally speaking, principle of the present invention is, when the failure of alien frequencies direct-cut operation or when breaking down, and the information of the equipment output specified type of control handoff procedure, and according to the information of described specified type, analyze more efficiently the reason of described alien frequencies direct-cut operation fault. Fig. 3 illustrates the flow process of irregular frequency hard switching fault analyzing method according to an embodiment of the invention.
As shown in the figure, at first in step 310, after the success of UE call setup, RNC will send to UE and measure control message, and notice UE carries out mass measurement to the alien frequencies adjacent area. UE measures in mobile process in real time, when discovery has the quality of alien frequencies adjacent area to satisfy the condition (in detail referring to 3GPPTS25331) of measurement report triggering, UE sends measurement report (Measurement Report) to RNC, comprises the information of Target cell in this message.
After this, in step 320, if RNC according to from the measurement report of UE, if judge and can switch, then the NodeB to the Target cell place sends wireless link request " Radio Link Setup Request " message.
Then, in step 330, after NodeB received request message from RNC, to RNC feedback wireless link response " Radio Link Setup Response " message, notice RNC wireless link was finished immediately.
In step 340, after RNC receives the success response of NodeB, begin to set up ALCAP transport layer part. Set up (ALCAP Iub Data Transport Bearer Setup) referring to the ALCAP Iub bearer context for data transmission among the figure.
In step 350, after transport layer is set up and is finished, RNC sends DDCH to UE: physical channel is reshuffled " DCCH:Physical Channel Reconfiguration " message, and notice UE revises corresponding parameter, in order to receive the information from the another one residential quarter.
After this, in step 360, at this moment because UE moves the residential quarter below the arrival target NodeB, source NodeB sends Radio Link Failure indication (Radio Link Failure Indication) to RNC, and this UE of notice RNC is with the NodeB step-out.
Then, in step 370, target NodeB sends wireless link recovery indication " Radio Link Restore Indicator " message informing RNC, and UE is at present at target NodeB wireless link recovery.
In step 380, this moment, UE sent DCCH to RNC: physical channel is reshuffled and is finished " DCCH:Physical Channel Reconfiguration Complete " message, inform that the RNC physical channel is reshuffled and finish, can send data at new link.
Then, in step 390, RNC sends Radio Link removal request " Radio Link deletion Request " message to source NodeB, the Radio Link above discharging.
At last, source NodeB sends wireless link response " Radio Link Deletion Response " message to RNC.
In above-mentioned steps, the direct-cut operation failure all may appear. For instance, when RNC finds that Target cell is congested, so just can not send wireless link request " Radio Link Setup Request " message to NodeB, thereby cause the handoff procedure failure, if the direct-cut operation failure occurs, then RNC is to (Operations ﹠ Maintenance Center, the network management center that is called for short " OMC " and so on sends relevant message, wherein comprises the information of specified type such as operation maintenance center. The webmaster personnel of OMC can know the direct-cut operation failure cause, and take appropriate measures by the analysis to these information.
The below will be by table 1～table 19, and to above-mentioned " information of specified type ", and the analytical method of these information describes. Wherein, boldface type partly is the group name of information element grouping, the non-black-body word be cell.
Table 1: alien frequencies direct-cut operation fault protocol architecture
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Message Type (type of message) | MP (essential) | Message Type (type of message) | ||
| UE information elements (UE information element) | ||||
| IMSI (international mobile station identity number) | MP (essential) | Referring to table 5 | The user represents, can know the user of breaking down according to this ID | |
| RAB Information elements (RAB information element) | ||||
| RAB Information (RAB information) | MP (essential) | Referring to table 6 | Active user's RAB information comprises the speed of various RAB information etc. | |
| Best Cell information elements (optimum subdistrict information element) | ||||
| Best Cell Information (optimum subdistrict information) | MP (essential) | Referring to table 7 | Current UE place best cell information can know that UE accepts service in that residential quarter at present | |
| Active Cell Information elements (active set information element) | ||||
| Active Cell Information (active set information) | MP (essential) | 0～6 | Referring to table 7 | Identify this UE and whether be in soft changing state, what kind of active set information is. |
| Inter-frequency cell information elements (alien frequencies neighboring BS information element) | ||||
| Inter-frequency neighbour cell information (alien frequencies neighboring BS information) | MP (essential) | 1～32 | Referring to table 7 | The alien frequencies neighboring BS information |
| Inter-frequency measured elements (different-frequency measure element) | ||||
| Target Cell Information (target cell information) | MP (essential) | Referring to table 8 | The Target cell that switches. |
| Hard Handover Trigger (alien frequencies direct-cut operation trigger) | MP (essential) | Referring to table 16 | The current alien frequencies direct-cut operation what reason triggers, the still load switching of the Event triggered whether UE reports causes. | |
| Failure information elements (failure information element) | ||||
| Hard Handover Failure Cause (alien frequencies direct-cut operation failure cause) | MP (essential) | Referring to table 4 | Alien frequencies direct-cut operation failure cause |
Table 2:Inter-frequency Measurement Report type (different-frequency measure reporting type)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Measurement Report type (measurement report type) | MP (essential) | |||
| CHOICE of Report (reporting option) | ||||
| ＞Periodic (cycle) | OP (optional) | |||
| ＞Event (event) | OP (optional) | |||
| ＞＞Inter-frequency event identity (different-frequency measure event identifier) | MP (essential) | Referring to table 3 |
Table 3:Inter-frequency event identity (alien frequencies event identifier)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Inter-frequency event identity (alien frequencies event identifier) | MP (essential) | ENUMERATED (enumerating) (2a, 2b, 2c, 2d, 2e, 2f) |
Table 4:Hard Handover Failure Cause (alien frequencies direct-cut operation failure cause)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| CHOICE Cause Group (reason group option) | MP (essential) | |||
| ＞RNC Inner Failure Choice (RNC internal fault option) | OP (optional) | |||
| ＞＞Call Admission Failure (call admission failure) | OP (optional) | Referring to table 15 | Call admission failure can be known according to this cause value and to switch when occuring, Target cell is failure cause why, congested causing, or transmission is not enough to be caused. | |
| ＞＞Protocol or Unmatched Message Error Cause (agreement or do not mate the message error reason) | OP (optional) | Referring to table 17 | Agreement or message error can know that according to this reason there is mistake in the message that message at standard interface comes from other network element. | |
| ＞＞ASN1 Error Cause (ASN1 error reason) | ENUMERATED (enumerating) (Transfer Syntax Error, Abstract Syntax Error, Logical Error). | Mistake appears in the message encoding and decoding, illustrates that the message that comes from other network element does not satisfy the requirement of encoding and decoding, needs so to confirm reason with respective network elements. | ||
| ＞＞L2 Configuration Error Cause (layer 2 configuration error reason) | OP (optional) | Referring to table 18 | In the handoff procedure kind, need to carry out the parameter configuration of L2, carry out the foundation of FP or MACD such as needs, mistake appears in this stage, and whether the inadequate resources such as fault or MACD have appearred in FP. | |
| ＞＞AL Configuration Error Cause (access link configuration error reason) | OP (optional) | Referring to table 19 | In handoff procedure, need to carry out the foundation of the transport layers such as ALCAP, if there is this part reason, illustrate when carrying out the transport layer configuration, fault has occured in RNC, solves according to these failure reason analysis why RNC goes wrong in the configuration transport layer. | |
| ＞＞User Plane Error Cause (user's face error reason) | OP (optional) | Other is unknowable is ready. | ||
| ＞＞Unspecified (undefined) | OP (optional) | |||
| ＞IUB Interface Failure choice (IUB interface fault option) | OP (optional) | |||
| ＞＞NBAP RL Setup Failure (NBAP RL sets up unsuccessfully) | MP (essential) | |||
| The RL Setup Failure cause of＞＞＞(RL sets up unsuccessfully) | OP (optional) | Referring to table 10 | According to the failure cause of standard I UB interface, failure can occur in the NODEB that can know-why, thereby jointly solves failure problem. | |
| The RL Setup Timer Expire of＞＞＞(RL sets up overtime) | OP (optional) | Wireless link is overtime, and RNC does not have successful transmission RL to set up message or NODEB not receive RL and set up message, more or |
| The person has been information drop-out, can check whether the system message scheduling goes wrong, and perhaps there is fault in the IUB interface link by this reason. | ||||
| ＞＞ALCAP Bear Setup Failure (the access link mobile network strengthens the customization applying portion carrying of logic and sets up fault) | OP (optional) | |||
| The ALCAP Bear Setup Failure Cause of＞＞＞(the access link mobile network strengthens the customization applying portion carrying of logic and sets up fault) | MP (essential) | ENUMERATED (enumerating) (IUUP FAILURE, FPMDC FAILURE, IURCFP FAILURE, RLC FAILURE, PDCP FAILURE, MACC FAILURE, MACD FAILURE, UNSPECIF IED) | This partial fault appears at the process kind that IUB sets up ALCAP and mistake occurs, can know setting up what process according to the cause value of mistake and break down. | |
| ＞＞AAL2 Setup Failure (atm adaptation layer 2 is set up unsuccessfully) | OP (optional) | |||
| The AAL2 Setup Failure Cause of＞＞＞(atm adaptation layer 2 is set up failure cause) | MP (essential) | ENUMERATED (enumerating) (Inner Establish Failure, QAAL2 No AAL2 Route, QAAL2 No Resource, QAAL2 AN1 Unreachable, QAAL2 Temporary Error, Peer ECF Failure for Normal Cause, Peer ECF Failure for Other Cause) | The carrying that alien frequencies direct-cut operation kind needs are set up AAL2, this reason unsuccessfully may be because the transport layer fault cause, and can know-why according to failure cause occurs unsuccessfully. | |
| ＞＞FP Synchronization Failure (Frame Protocol synchronization failure) | OP (optional) | ENUMERATED (enumerating) (Uplink Synchronization Failure, Downlink Synchronization Failure). | Carry out occurring unsuccessfully in synchronous at FP, can know up or descending failure according to failure cause. | |
| The FP Synchronization Timer Expired of＞＞＞(Frame Protocol Synchronization timeout) | OP (optional) | Carried out the FP Synchronization timeout with NODEB. | ||
| ＞＞Unspecified (undefined) | OP (optional) | |||
| ＞UU Interface Failure Choice (UU interface fault option) | OP (optional) | |||
| ＞＞Physical Channel Reconfiguration Failure (physical channel reconfiguration failure) | MP (essential) | |||
| The Physical Channel Reconfiguration Failure cause of＞＞＞(physical channel reconfiguration failure reason) | OP (optional) | Referring to table 11 | Need to send physical channel to UE and reshuffle carrying out alien frequencies direct-cut operation kind, can know according to failure cause why UE has returned the physical channel reconfiguration failure. | |
| ＞＞＞Physical Channel | OP (optional) | Physical channel is reshuffled overtime. |
| Reconfiguration Failure Expire (physical channel is reshuffled overtime) | ||||
| ＞＞Unspecified (undefined) | OP (optional) | |||
| ＞IU Interface Failure Choice (IU interface fault option) | OP (optional) | |||
| ＞＞Unspecified (undefined) | OP (optional) | |||
| ＞IUR Interface Failure Choice (IUR interface fault option) | OP (optional) | |||
| ＞＞IUR RL Setup Failure (IUR RL sets up unsuccessfully) | MP (essential) | |||
| The IUR RL Setup Failure Cause of＞＞＞(IUR RL sets up failure cause) | OP (optional) | Referring to table 12 | This reason is set up failure cause with the RL of IUB interface. Can know when striding the soft handover of IUR interface according to this reason and to go wrong. | |
| The IUR RL Setup Timer Expire of＞＞＞(IUR RL sets up overtime) | OP (optional) | Striding IUR interface RL sets up overtime. | ||
| ＞＞Unspecified (undefined) | OP (optional) |
Table 5:IMSI (GSM-MAP) (international mobile station identity number)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| IMSI (international mobile station identity number) | MP (essential) | 6 to 21 | ||
| ＞IMSI digit | MP (essential) | INTEGER(0..9) |
Table 6:RAB List Information (RAB list information)
| IE/Group Name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| RABs Information List (wireless access information list) | 1～255 | |||
| ＞Traffic Class (type of service) | MP (essential) | ENUMERATED (enumerating) (conversational, streaming, interactive, background ...) | ||
| ＞CN Information identity (CN message identification) | MP (essential) | CN Domain identity 2.2.2.13 | ||
| ＞DL Maximum Bit Rate (downlink Maximum Bit Rate) | MP (essential) | INTEGER (1..16,000,000) | ||
| ＞UL Maximum Bit Rate (up-link Maximum Bit Rate) | MP (essential) | INTEGER (1..16,000,000) | ||
| ＞UL Guaranteed Bit Rate (up-link assurance bit rate) | OP (optional) | INTEGER (0..16,000,000) | ||
| ＞DL Guaranteed Bit Rate (downlink assurance bit rate) | OP (optional) | INTEGER (0..16,000,000) | ||
| ＞RAB ID | MP (essential) | BIT STRING(8) |
| ＞RAB To Be Setup Or Modified Time (RAB sets up or modification time) | MP (essential) | BIT STRING(32) | (DATE：HOUR：MINUTE： SECOND) |
Table 7:Cell Information (cell information)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Cell identity (cell ID) | MP (essential) | BIT STRING(28) | Cell ID is known according to this residential quarter ID to occur in that residential quarter | |
| Measurement result for current cell (current area measurement result) | ||||
| ＞CPICH Ec/NO | OP (optional) | INTEGER(0..49) | The quality of residential quarter, the quality that can know the residential quarter according to this value how. | |
| ＞CPICH RSCP | OP (optional) | INTEGER(0..91) | The quality of residential quarter, the quality that can know the residential quarter according to this value how. |
Table 8:Target Cell Information (target cell information)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Target Cell Information (target cell information) | MP (essential) | |||
| ＞Added Cell information (being added into the information of residential quarter) | OP (optional) | 1～6 | ||
| ＞＞Cell Information (cell information) | MP (essential) | Cell Information 2.2.2.7 | Target cell information. | |
| ＞＞Cell synchronization information (cell synchronization information) | OP (optional) | Cell synchronization information 2.2.2.14 | ||
| ＞Deleted Cell Information (information of deleted residential quarter) | OP (optional) | 1～6 | ||
| ＞＞Cell Information (cell information) | MP (essential) | Cell Information 2.2.2.7 | ||
| ＞＞Cell synchronization (cell synchronization information) information | OP (optional) | Cell synchronization information 2.2.2.14 |
Table 9:Credit information (credit information)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| UL Spreading Factor (up-link spreading factor) | MP (essential) | ENUMERATED (enumerating) (4,8,16,32,64,128,256,512) | ||
| DL Spreading Factor (downlink spreading factor) | MP (essential) | ENUMERATED (enumerating) (4,8,16,32,64,128,256,512) | ||
| Local Cell Credit Information (home cell credit information) | MP (essential) | |||
| ＞DL Or Global Capacity Credit (downlink or overall ability credit rating) | MP (essential) | INTEGER(0..65535) | ||
| ＞UL Capacity Credit (uplink capability credit rating) | OP (optional) | INTEGER(0..65535) | ||
| Local Cell Group Credit Information (home cell group credit information) | OP (optional) | |||
| ＞DL Or Global Capacity Credit (downlink or overall ability credit rating) | MP (essential) | INTEGER(0..65535) | ||
| ＞UL Capacity Credit (uplink capability credit rating) | OP (optional) | INTEGER(0..65535) |
Table 10:RL Setup Failure cause (wireless link failure cause)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| CHOICE Cause Group (reason group option) | M (essential) | |||
| ＞Radio Network Layer (wireless network layer) | ||||
| ＞＞Radio Network Layer Cause (wireless network layer reason) | M (essential) | ENUMERATED (enumerating) (unknown C-ID, Cell not available, Power level not supported, DL radio resources not available, UL radio resources not available, RL Already Activated/allocated, Node B Resources Unavailable, Measurement not supported for the object, Combining Resources not available, Requested configuration not supported, Synchronization failure, Priority transport channel established, SIB Origination in Node B not Supported, Requested Tx Diversity Mode not supported, Unspecified (undefined), BCCH scheduling error, Measurement TeMP (essential) orarily not Available, Invalid CM Setting, Reconfiguration CFN not elapsed, Number of DL codes not supported, S-CPICH not supported, Combining not supported, UL SF not supported, DL SF not supported, Common Transport Channel Type not supported, Dedicated Transport Channel Type not supported, Downlink Shared Channel Type not supported, Uplink Shared Channel Type not supported, CM not supported, Tx diversity no longer supported, Unknown Local Cell ID, ..., Number of UL codes not supported, Information teMP (essential) orarily not available, Information Provision not supported for the object, Cell Synchronisation not supported, Cell Synchronisation Adjustment not supported |
| DPC Mode Change not Supported, IPDL already activated, IPDL not supported, IPDL parameters not available, Frequency Acquisition not supported, Power Balancing status not coMP (essential) atible, Requested type of Bearer Re-arrangement not supported, Signalling Bearer Re-arrangement not supported, Bearer Re-arrangement Need (necessity) ed, Delayed Activation not Supported, RL Timing Adjustment not supported) | ||||
| ＞Transport Layer (transport layer) | ||||
| ＞＞Transport Layer Cause (transport layer reason) | M (essential) | ENUMERATED (enumerating) (Transport resource unavailable, Unspecified (undefined) ...) | ||
| ＞Protocol (agreement) | ||||
| ＞＞Protocol Cause (agreement reason) | M (essential) | ENUMERATED (enumerating) (Transfer syntax error, Abstract syntax error (reject), Abstract syntax error (ignore and notify), Message not coMP (essential) atible with receiver state, Semantic error, Unspecified (undefined), Abstract syntax error (falsely constructed message) ...) | ||
| ＞Misc (miscellaneous) | ||||
| ＞＞Miscellaneous Cause (miscellaneous reason) | M (essential) | ENUMERATED (enumerating) (Control processing overload Hardware failure, O﹠M intervention, Not enough user plane processing resources, Unspecified (undefined) ...) |
Table 11:UU Interface Failure cause (UU interface failure cause)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Failure cause (failure cause) | MP (essential) | ENUMERATED (enumerating) (configuration unsupported, physical channel failure, incoMP (essential) atible simultaneous reconfiguration, protocol error, coMP (essential) ressed mode runtime error, cell update occurred, invalid configuration, configuration incoMP (essential) lete, unsupported measurement) | ||
| Protocol error information (protocol error message) | OP (optional) | |||
| ＞CHOICE diagnostics type (diagnostic-type option) | MP (essential) | |||
| ＞＞Protocol error cause (protocol error message) | ENUMERATED (enumerating) (ASN.1 violation or encoding error, Message type non-existent or not iMP (essential) lemented, Message not coMP (essential) atible with receiver state, Information element value not coMP (essential) rehended, Information element missing, Message extension not coMP (essential) rehended) | |||
| Deleted TGPSI (TGPSI of deletion) | OP (optional) | |||
| ＞TGPSI | MP (essential) | Integer(1..MaxTGPS) |
Table 12:RL Setup Failure Cause For Iur (Iur wireless link failure cause)
| IE/Group Name (information element/group name) | Prese nce (necessity) | Ran ge (scope) | IE Type and reference (type and quote) | Semantics descriptio n (semantic description) |
| CHOICE Cause Group (reason group option) | M (essential) | |||
| ＞Radio Network Layer (wireless network layer) | ||||
| ＞＞Radio Network Layer Cause (wireless network layer reason) | M (essential) | ENUMERATED (enumerating) (Unknown C-ID, Cell not Available, Power Level not Supported, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Measurement not Supported For The Object, Combining Resources Not Available, Combining not Supported, Reconfiguration not Allowed, Requested Configuration not Supported, Synchronisation Failure, Requested Tx Diversity Mode not Supported, Measurement TeMP (essential) orarily not Available, Unspecified (undefined), Invalid CM Settings, Reconfiguration CFN not Elapsed, Number of DL Codes Not Supported, Dedicated Transport Channel Type not Supported, DL Shared Channel Type not Supported, UL Shared Channel Type not Supported, Common Transport Channel Type not Supported, UL Spreading Factor not Supported, DL Spreading Factor not Supported, CM not Supported, Transaction not Supported by Destination Node B, RL Already Activated/Allocated, ..., Number of UL Codes Not Supported, Cell reserved for OP (optional) erator use, DPC Mode Change not Supported, Information teMP (essential) orarily not available, Information Provision not supported for the object, Power Balancing status not coMP (essential) atible, Delayed Activation not Supported, RL Timing Adjustment Not Supported, Unknown RNTI) | ||
| ＞Transport Layer (transport layer) |
| ＞＞Transport Layer Cause (transport layer) | M (essential) | ENUMERATED (enumerating) (Transport Resource Unavailable, Unspecified (undefined) ...) | ||
| ＞Protocol (agreement) | ||||
| ＞＞Protocol Cause (agreement reason) | M (essential) | ENUMERATED (enumerating) (Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not CoMP (essential) atible with Receiver State, Semantic Error, Unspecified (undefined), Abstract Syntax Error (Falsely Constructed Message) ...) | ||
| ＞Misc (miscellaneous) | ||||
| ＞＞Miscellaneous Cause (miscellaneous reason) | M (essential) | ENUMERATED (enumerating) (Control Processing Overload, Hardware Failure, O﹠M Intervention, Not enough User Plane Processing Resources, Unspecified (undefined) ...) |
Table 13:CN domain identity (CN domain identifier)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| CN domain identity (CN domain identifier) | MP (essential) | ENUMERATED (enumerating) (CS domain, PS domain) |
Table 14:Cell synchronization information (cell synchronous speech breath)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| OFF (biasing) | MP (essential) | INTEGER(0..255) | in frames | |
| Tm (biasing) | MP (essential) | INTEGER(0..38399) | in chips |
Table 15:Call Admission Failure (call admission failure)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Call Admission Failure (call admission failure) | ||||
| CHOICE (option) | ||||
| ＞Cell Congestion (residential quarter is congested) | OP (optional) | The residential quarter has occured congested, can know-why congested according to following parameter. | ||
| ＞＞Transmitted Carrier Power Value (transmission power level) | MP (essential) | INTEGER(0..100) | How much descending power of current NODEB is | |
| ＞＞Received Total Wide Band Power Value (receiving the broadband total power value) | MP (essential) | INTEGER(0..621) | How much up power of current NODEB is | |
| ＞Cell DL SF not supported (the descending spreading factor in residential quarter is unavailable) | OP (optional) | Descending spreading factor is unavailable, and the spreading factor of applying for is described, the residential quarter is not supported at present | ||
| ＞＞Spreading Factor (spreading factor) | MP (essential) | ENUMERATED (enumerating) (4,8,16,32,64,128,256) | ||
| ＞Cell UL SF not supported (the up spreading factor in residential quarter is unavailable) | OP (optional) | Up spreading factor is unavailable, and the spreading factor of applying for is described, the residential quarter is not supported at present | ||
| ＞＞Spreading Factor (spreading factor) | MP (essential) | ENUMERATED (enumerating) (4,8,16,32,64,128,256) | ||
| ＞Cell Credit not supported (the residential quarter credit rating is not supported) | OP (optional) | The CREDIT information of current NODEB is not enough, can not satisfy this and call out, and needs so to check whether the CREDIT information of NODEB is reasonable. | ||
| ＞＞Credit information (credit rating information) | MP (essential) | Credit information 2.2.2.7 | ||
| ＞IUB Transport resource unavailable (IUB interface transfer resource is unavailable) | OP (optional) | The transmission bandwidth of IUB interface is not enough, can unsuccessfully increase the IUB bandwidth according to this | ||
| ＞＞UL IUB bandwidth (UL IUB bandwidth) | MP (essential) | INTEGER (0..65535) | Unit:byte (unit: byte) | |
| ＞＞DL IUB bandwidth (DL IUB bandwidth) | MP (essential) | INTEGER (0..65535) | Unit:byte (unit: byte) | |
| ＞IUR Transport resource Unavailable (IUR interface transfer resource is unavailable) | OP (optional) | The transmission bandwidth of IUR interface is not enough, can unsuccessfully increase the IUR bandwidth according to this | ||
| ＞＞UL IUR bandwidth (UL IUB bandwidth) | MP (essential) | INTEGER (0..65535) | Unit:byte (unit: byte) | |
| ＞＞DL IUR bandwidth (DL IUB bandwidth) | MP (essential) | INTEGER (0..65535) | Unit:byte (unit: byte) |
Table 16:Hard handover trigger (direct-cut operation trigger)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Hard handover trigger (direct-cut operation trigger) | MP (essential) | |||
| CHOICE of trigger (trigger option) | ||||
| ＞Based on converge (based on covering) | ||||
| ＞＞Periodic (cycle) | OP (optional) | The switching that period measurement triggers | ||
| ＞＞Event (event) | OP (optional) | The measurement that event triggers | ||
| The Inter-frequency event identity of＞＞＞(alien frequencies event identifier) | MP (essential) | Referring to table 3 | ||
| ＞Based on Load (based on load) | OP (optional) | Switching based on load | ||
| ＞Based on Blind (based on blind switching) | OP (optional) | Blind switching |
Table 17:Protocol or Unmatched Message Error Cause (agreement or unmatched message error reason)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| Protocol or Unmatched Message Error Cause (agreement or unmatched message error reason) | MP (essential) | ENUMERATED (enumerating) (RAB_CFG_TRANSP_LAYER_AD DR_LEN_ERROR, RAB_CFG_TRANS_ASSOCI_NO _ TEID_ERROR, RAB_MODIFY_VER_LIMIT_ERR OR, RAB_ABSTRACT_SYNTAX_ERR OR_REJ, RAB_ABSTRACT_SYNTAX_ERR OR_FAUSELY_CONSTRUCTED, RAB_INVALID_RAB_ID_ERROR, RAB_ASSIGN_HANDLE_RAB_N UM_ZERO_ERROR, RAB_ASSIGN_HANDLE_RAB_ID REPEATED_ERROR, RAB_TRAFFIC_CLASS_NOT_S UPP_ERROR, RELOC_MSG_DATA_ERR, RELOC_RAB_ID_ERR, RELOC_RB_ID_ERR, RELOC_SOME_RAB_FAIL, RELOC_MISS_URNTI, RELOC_SYS_HO_RELOC_CMD _ NO_L3INFO, RELOC_IU_REQ_SECURITY_M ODE_ALGOR_NOT_SUPP, RELOC_IU_CHANGE_SECURIT Y_MODE_NOT_SUPP, COMM_IU_REQ_SECURITY_MO DE_ALGOR_NOT_SUPP, COMM_IU_CHANGE_SECURITY _ MODE_NOT_SUPP, RL_CAUSE_NODEB_RSP_INVA LID, RL_CAUSE_DRNC_RSP_INVALI D, DRL_PARA_CHECK_FAIL, DRL_CHECK_DCH_MOD_FAIL, DRL_CHECK_DCH_ADD_FAIL, DRL_CHECK_DCH_DEL_FAIL, DRL_UL_SCRAMECODE_INVAL ID, DRL_CM_CMD_INVALID, DRL_DRNTI_EXIST, DRL_CELL_ID_INVALID, DRL_INVALID_CM_SETTING, DRL_QE_SELECTED_NUM_INV ALID, DRL_TTI_INVALID, DRL_IE_CONFLICT, DRL_TFCS_INVALID, DRL_DL_SLOTFORMAT_ERRO R |
| DRL_FIND_DCH_FAIL， DRL_FIND_CODCH_FAIL， DRL_FIND_FP_INDEX_FAIL， DRL_FIND_RECFG_RL_FAIL， DRL_DSCH_NOT_SUPPORT， DRL_DL_DCH_ONLY_NOT_SUP PORT， DRL_HDSCH_NOT_SUPPORT， CU_REC_WRONG_CELL_UPDA TE， SHO_RRC_TRANSID_UNEQUAL ， CM_RRC_TRANSID_UNEQUAL， HHO_UE_RSP_MSG_INVALID， HHO_INVALID_TRANSACTION_I D， COMM_INTEG_CHECK_XMACI_ NOT_EQUAL_MACI， CMCH_CRITICDATA_ERR， CORRM_IU_SEMANTIC_ERR， FHHO_RRC_STATE_WRONG， FHHO_TRANSC_ID_WRONG， SHO_NO_NORM_RL_left， SHO_FSM_REJ， RELOC_UE_STATE_ERROR， RELOC_FSM_REJ，) |
Table 18:L2 Configuration Error Cause (layer 2 configuration error reason)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| L2 Configuration Error Cause (configuration error reason) | MP (essential) | ENUMERATED (enumerating) (SIG_RLC_RESET_FAIL, TRAFFIC_RLC_RESET_FAIL, ALL_RLC_RESET_FAIL, IUB_FP_FAIL, IUR_FP_FAIL, MDC_FAIL, MACC_LOCH_FAIL, MACD_FAIL, RLC_FAIL, PDCP_FAIL, GTPU_FAIL, IUUP_FAIL, PDCP_RELEASE_FAIL, RLC_SUSPEND_FAIL, RLC_Stop (optional) _ FAIL, FP_TYCH_SYNC_FAIL, PDCP_GET_SN_FAIL, UPT_URNTI_FAIL, RLC_CIPHER_QUERY_FAIL, MACD_CIPHER_QUERY_FAIL, RLC_CIPHER_CONIFG_FAIL, MACD_CIPHER_CONFIG_FAIL, FP_TIMEOUT, MDC_TIMEOUT, MACC_TIMEOUT, MACD_TIMEOUT, RLC_TIMEOUT, PDCP_TIMEOUT, GTPU_TIMEOUT, IUUP_TIMEOUT, PDCP_REL_RSP_TIMEOUT, MACD_CIPHER_QUERY_RSP_TIMEOU T, RLC_CIPHER_QUERY_RSP_TIMEOUT, RLC_CIPHER_CONFIG_RSP_TIMEOUT, MACD_CIPHER_CONFIG_RSP_TIMEO UT, RLC_SUSPEND_RSP_TIMEOUT, RLC_Stop (optional) _ RSP_TIMEOUT, UPT_URNTI_RSP_TIMEOUT, FP_TRCH_SYNC_RSP_TIMEOUT, PDCP_GET_SN_RSP_TIMEOUT, RLC_ASSIST_DATA_DELIV_TIMEOUT, L2RECFG_FAIL, FP_RECFG_FAIL, FP_SETUP_FAIL, FP_TRCH_SYNC_FAIL, GTPU_RECFG_FAIL, GTPU_SETUP_FAIL, NBM_URNTI_FAIL, RECV_ABNORMAL_MSG) |
Table 19:AL Configuration Error Cause (access link configuration error reason)
| Information Element/Group name (information element/group name) | Need (necessity) | Multi (quantity) | Type and reference (type and quote) | Semantics description (semantic description) |
| AL Configuration Error Cause (access link configuration error reason) | MP (essential) | ENUMERATED (enumerating) (IU_AAL2_FAIL, IU_AAL2_ALLOC_CID_FAIL, IUB_AAL2_FAIL, IUB_AAL2_ALLOC_CID_FAIL, IUR_AAL2_FAIL, IUR_AAL2_ALLOC_CID_FAIL, MACD_MACC_AAL2_FAIL, AL_SETUP_TYPE3_FAIL, AL_SETUP_TYPE5_FAIL, IU_AAL2_TIMEOUT, IUB_AAL2_IMEOUT, IUR_AAL2_TIMEOUT, TYPE5_AAL2_TIMEOUT, AL_MODIFY_FAIL) |
According to the above description, if the user is carrying out the CS12.2K voice call, when moving to little area edge, carry out the alien frequencies direct-cut operation, but failure. Can be by user's phone number, MSISDN namely finds the IMSI of this user's mobile phone according to MSISDN. Perhaps search for by the residential quarter, generate following form:
| ID (IMSI) | 460070114001271 |
| Business is set up information before the call drop | 1 |
| CS DOMAIN, CONVERSATIONAL UL/DL Bit Rate:12200 UL/DL Guaranteed Bit Rate:4.75K Time Created: 2005-06-30 9:28 RABID:1 | |
| Best residential quarter | RNC：10，CELLID：101 |
| Best residential quarter RSCP | -101dbm |
| Best residential quarter EcNo | -12db |
| Other Serving cell | Nothing |
| Other Serving cells RSCP | Nothing |
| Other Serving cells EcNo | Nothing |
| Alien frequencies adjacent area 1 information | RNC：10，CELLID：109 |
| Alien frequencies adjacent area 1RSCP | -95dbm |
| Alien frequencies adjacent area 1EcNo | -10db |
| Alien frequencies adjacent area 2 information | RNC：10，CELLID：120 |
| Alien frequencies adjacent area 2RSCP | -83dbm |
| Alien frequencies adjacent area 2EcNo | -12db |
| Switch Target cell information | RNC：10，CELLID：109 |
| Alien frequencies switches type | 2D |
| Alien frequencies direct-cut operation failure cause: | |
| RNC internal fault: Target cell access failure | |
| The residential quarter is congested: RTWP:403 TCP:90 |
By the analysis to content in the above table, can obtain following information: one, present user has moved to the common area of coverage of residential quarter 101 and 120, this moment, the quality of best residential quarter 101 was poor, and UE detects the thresholding that alien frequencies direct-cut operation 2D has been satisfied in the residential quarter of residential quarter 120, thereby UE has reported the 2D event. Two, after RNC judges these No. 120 residential quarters and satisfies alien frequencies direct-cut operation condition, triggered the alien frequencies direct-cut operation, but because the current load in No. 120 residential quarters is very high. Wherein TCP has reached 90%, has surpassed the thresholding that accesses this residential quarter, thereby causes the alien frequencies direct-cut operation in the failure of 120 residential quarters.
Can know from top output parameter, the reason of this alien frequencies direct-cut operation failure is because load of Target cell is very heavy, the switching failure that causes the access failure and cause can draw following analysis result thus: the first, and whether Target cell is in the center of focus. If so, so should optimized network, minimizing with this Target cell as the adjacent area; The second, whether the pilot power of Target cell arranges too large, causes too many user to be linked in this residential quarter. If so, should reduce power so, so that so that the user can be evenly distributed to other neighbor cell; The 3rd, revise the residential quarter of Target cell and select and the gravity treatment parameter, so that so that other adjacent area is arrived in the easier gravity treatment free time of the user in this residential quarter; The 4th, the alien frequencies direct-cut operation that whether should be modified to Target cell starts thresholding, reduces to the switching of Target cell.
The below enumerates a direct-cut operation failure cause again and analyzes example. This example still adopts above-mentioned situation, but the user only has the business of a PS384K, and alien frequencies direct-cut operation fault output form is as follows:
| ID (IMSI) | 460070114001271 |
| Business is set up information before the call drop | 1 |
| PS DOMAIN, BACKGROUD UL/DL Bit Rate:64K/384K Time Created: 2005-06-30 7:45 RABID:1 | |
| Best residential quarter | RNC：10，CELLID：101 |
| Best residential quarter RSCP | -102dbm |
| Best residential quarter EcNo | -12db |
| Other Serving cell | Nothing |
| Other Serving cells RSCP | Nothing |
| Other Serving cells EcNo | Nothing |
| Detected set residential quarter 2 information | RNC：10，CELLID：120 |
| Detected set residential quarter 2RSCP | -83dbm |
| Detected set residential quarter 2EcNo | -10db |
| Switch Target cell information | RNC：10，CELLID：120 |
| Alien frequencies direct-cut operation type | 2D |
| Alien frequencies direct-cut operation failure cause: | |
| The inner handling failure of RNC: the IUB interface bandwidth is not enough | |
| The IUB interface band width resource is not enough: IUB upstream bandwidth: 780k byte IUB downlink bandwidth: 457k byte |
Can obtain following information from the output of alien frequencies direct-cut operation failure: one, the signal quality that receives of this user non-constant, need to switch in order to continue to satisfy the requirement of conversation, otherwise will call drop; Two, the Target cell of alien frequencies direct-cut operation is No. 120 residential quarters of RNC 10, and the quality of this residential quarter is well, can arrive this residential quarter by the alien frequencies direct-cut operation, in addition except behind this residential quarter, does not have other adjacent area mass ratio better; Three, after RNC has triggered the alien frequencies direct-cut operation, find that the transmission bandwidth of IUB interface can not satisfy the professional required bandwidth of 384K, so this alien frequencies direct-cut operation failure.
We can know from top information, and current IUB interface resource is not enough, can't set up Radio Link at the IUB interface, thereby have caused the failure of alien frequencies direct-cut operation. Thus, by above-mentioned output, can draw transmission channel bandwidth resource that the PS business of following analysis result: the first, 384K takies the chances are about 570k byte, should these users be switched on the lighter NodeB of load for the switching of PS business as far as possible. Such as in the network planning, the residential quarter polygamy on the NodeB that these PS users can be concentrated is put the lighter residential quarter of some loads as the adjacent area, so that the alien frequencies direct-cut operation that these users can be successful in mobile process is to other residential quarter. Second, check the IUB interface bandwidth, whether this band width configuration is improper, because may be because the user be few at the networking initial stage, transmission bandwidth is generally all smaller so, but along with the increasing of user, the customer service amount will increase accordingly so, so just should increase according to actual conditions the bandwidth of IUB interface, to meet consumers' demand.
By the analysis to foregoing, be appreciated that the present invention in order to analyze efficiently the failure cause of alien frequencies direct-cut operation, in the failure of alien frequencies direct-cut operation or when breaking down, the information of type is specified in the equipment output of control switching process, and network management center is analyzing failure cause accordingly. The information of the appointment type of output comprises: type of message, IMSI, optimum residential quarter information, alien frequencies neighboring BS information, alien frequencies direct-cut operation call drop reason, active set information, RAB information, Target cell information, alien frequencies direct-cut operation trigger etc.; Also pointed out simultaneously how to utilize these information to carry out accident analysis. Since specify the information of type to cover the every aspect relevant with the alien frequencies direct-cut operation, thus can help the webmaster personnel effectively to analyze out of order reason, and then take corresponding corrective measure. In addition, the present invention is output information just in the failure of alien frequencies direct-cut operation or when breaking down only, so the added burden that whole GSM is increased is very little, can process to the regular traffic of system hardly having a negative impact.
Although by reference some preferred embodiment of the present invention, the present invention is illustrated and describes, but those of ordinary skill in the art should be understood that and can do various changes to it in the form and details, and without departing from the spirit and scope of the present invention.
Claims (10)
1. an alien frequencies direct-cut operation failure analysis methods is characterized in that, comprises following steps:
When the failure of alien frequencies direct-cut operation or when breaking down, the information of type is specified in the equipment output of control switching process;
According to the information of described appointment type, analyze the reason of described alien frequencies direct-cut operation fault.
2. alien frequencies direct-cut operation failure analysis methods according to claim 1 is characterized in that described method is applied to broadband CDMA system, and the equipment that process is switched in described control is radio network controller.
3. alien frequencies direct-cut operation failure analysis methods according to claim 2 is characterized in that the information of described appointment type comprises:
International mobile station identity number can be analyzed accordingly and learn the user of breaking down;
Optimum residential quarter information can be analyzed accordingly and learn that residential quarter best for the subscriber equipment signal when breaking down, this residential quarter also are the residential quarters of serving for this subscriber equipment at that time;
The alien frequencies neighboring BS information can be analyzed accordingly and learn the adjacent area that might carry out the alien frequencies switching when alien frequencies direct-cut operation occurs;
Alien frequencies direct-cut operation failure cause can be analyzed the reason of the alien frequencies direct-cut operation failure that the system of learning provides accordingly.
4. alien frequencies direct-cut operation failure analysis methods according to claim 3 is characterized in that, described radio network controller sends to operation maintenance center by message with the information of described appointment type, comprises type of message in this message;
Described operation maintenance center parses the information of described appointment type according to described type of message from the message of receiving.
5. alien frequencies direct-cut operation failure analysis methods according to claim 3 is characterized in that, described alien frequencies direct-cut operation failure cause further comprises one of following information or its any combination:
The call admission failure can be analyzed the reason that causes the Target cell failure when alien frequencies direct-cut operation occurs accordingly;
Agreement or do not mate the message error reason can be learnt in the message from other network element to have mistake accordingly;
The ASN1 error reason can be learnt the requirement of not satisfying encoding and decoding from the message of other network element accordingly, needs further to check that corresponding network element is to confirm reason;
Layer 2 configuration error reason, possible problem is Frame Protocol fault or inadequate resource;
Access link configuration error reason can be analyzed the further reason that radio network controller goes wrong accordingly when the configuration transport layer;
The wireless link failure cause can be analyzed the reason of learning the NodeB failure accordingly;
Wireless link is overtime, accordingly the fault of check system scheduling message or IUB interface link;
The access link mobile network strengthens the customization applying portion carrying of logic and sets up failure cause, can analyze accordingly fault to have occurred when setting up what process;
Atm adaptation layer 2 is set up failure cause, whether can analyze accordingly because the transport layer fault causes;
Frame Protocol is failure synchronously, can analyze accordingly problem occurs when up or descending;
Physical channel is reshuffled failure cause, can analyze accordingly and learn why subscriber equipment can return physical channel and reshuffle failed message;
Physical channel is reshuffled overtime, can further analyze accordingly to cause this overtime reason;
IUR interface wireless link establishment failure cause can be known when striding the alien frequencies direct-cut operation of IUR interface to go wrong accordingly;
The link establishment of IUR interface wireless is overtime, can know accordingly when striding the alien frequencies direct-cut operation of IUR interface to go wrong.
6. alien frequencies direct-cut operation failure analysis methods according to claim 5 is characterized in that, described call admission failure further comprises one of following information or its any combination:
The transmission power level of NodeB and total received power in broadband value, congested if the residential quarter occurs, can analyze accordingly the residential quarter congested reason occurs;
The descending spreading factor in residential quarter is unavailable, can know accordingly that one of reason of causing the call admission failure is that the descending spreading factor applied for is not supported in present residential quarter;
The up spreading factor in residential quarter is unavailable, can know accordingly that one of reason of causing the call admission failure is that the up spreading factor applied for is not supported in present residential quarter;
The residential quarter credit rating do not support, can know accordingly that one of reason of causing the call admission failure is that the credit rating information of current NodeB is not enough, can check further whether the credit rating information of NodeB is reasonable;
IUB interface transfer resource is unavailable, can know accordingly the bandwidth that needs the corresponding IUB interface of increase system;
IUR interface transfer resource is unavailable, can know accordingly the bandwidth that needs the corresponding IUR interface of increase system.
7. alien frequencies direct-cut operation failure analysis methods according to claim 3 is characterized in that, the information of described appointment type also can comprise following a kind of or its any combination:
RAB information wherein comprises the speed of various RAB information;
Active set information if at least two residential quarters are arranged in the active set, illustrates that then subscriber equipment is in the soft handover state before the alien frequencies direct-cut operation occurs;
Whether Target cell information is normal as the residential quarter of switching target in the time of can analyzing accordingly the generation of alien frequencies direct-cut operation;
Alien frequencies direct-cut operation trigger can be analyzed the reason that triggers the alien frequencies direct-cut operation accordingly.
8. alien frequencies direct-cut operation failure analysis methods according to claim 7 is characterized in that, described Target cell information is divided into increases residential quarter information and deletion residential quarter information two classes, and each class further comprises again following information:
The sign of Target cell can be analyzed the position that the alien frequencies direct-cut operation occurs accordingly;
Cell synchronous information, the accordingly timing relationship between evaluating objects residential quarter and the optimum residential quarter.
9. alien frequencies direct-cut operation failure analysis methods according to claim 7 is characterized in that, described optimum residential quarter information, active set information and alien frequencies neighboring BS information comprise one of following information or its any combination:
Cell ID can know accordingly which residential quarter is problem occur in;
The Ec/No of CPICH Common Pilot Channel, the RSCP of CPICH Common Pilot Channel can know residential quarter signal quality at that time accordingly.
10. alien frequencies direct-cut operation failure analysis methods according to claim 7 is characterized in that, described alien frequencies direct-cut operation trigger further comprises one of following information or its any combination:
Based on the information of coverage, comprise the switching of periodic measurement triggering and the switching that event triggers;
Information based on load;
Information based on blind switching.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2005100363561A CN1859682B (en) | 2005-08-02 | 2005-08-02 | Irregular frequency hard switching fault analyzing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2005100363561A CN1859682B (en) | 2005-08-02 | 2005-08-02 | Irregular frequency hard switching fault analyzing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1859682A true CN1859682A (en) | 2006-11-08 |
| CN1859682B CN1859682B (en) | 2010-04-28 |
Family
ID=37298533
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2005100363561A Expired - Fee Related CN1859682B (en) | 2005-08-02 | 2005-08-02 | Irregular frequency hard switching fault analyzing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1859682B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011113396A2 (en) * | 2011-04-28 | 2011-09-22 | 华为技术有限公司 | Method, device and system for mobility management |
| CN102026243B (en) * | 2009-09-10 | 2013-06-05 | 联芯科技有限公司 | Method and system for processing user equipment |
| CN104247491A (en) * | 2013-02-01 | 2014-12-24 | 华为技术有限公司 | Radio link control method and apparatus, radio network controller and user equipment |
| CN107113650A (en) * | 2015-01-22 | 2017-08-29 | 英特尔Ip公司 | The transmission of congestion control information |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FI105993B (en) * | 1997-08-20 | 2000-10-31 | Nokia Mobile Phones Ltd | Procedures and systems for controlling radio communication systems and radio network controllers |
| CN1223148C (en) * | 2002-09-28 | 2005-10-12 | 华为技术有限公司 | Method for implementing signaling link fault reason report |
-
2005
- 2005-08-02 CN CN2005100363561A patent/CN1859682B/en not_active Expired - Fee Related
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102026243B (en) * | 2009-09-10 | 2013-06-05 | 联芯科技有限公司 | Method and system for processing user equipment |
| WO2011113396A2 (en) * | 2011-04-28 | 2011-09-22 | 华为技术有限公司 | Method, device and system for mobility management |
| WO2011113396A3 (en) * | 2011-04-28 | 2012-03-22 | 华为技术有限公司 | Method, device and system for mobility management |
| CN104247491A (en) * | 2013-02-01 | 2014-12-24 | 华为技术有限公司 | Radio link control method and apparatus, radio network controller and user equipment |
| CN107113650A (en) * | 2015-01-22 | 2017-08-29 | 英特尔Ip公司 | The transmission of congestion control information |
| CN107113650B (en) * | 2015-01-22 | 2021-08-13 | 苹果公司 | Transmission of congestion control information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1859682B (en) | 2010-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Yi et al. | Radio Protocols for LTE and LTE-advanced | |
| US7937086B2 (en) | Method and system for a handoff in a broadcast communication system | |
| JP5302338B2 (en) | Automatic management of inter-RAT / frequency adjacency list | |
| FI113140B (en) | Handoff in cellular system | |
| TWI583217B (en) | Method of handling cell reselection | |
| KR100964684B1 (en) | Method for providing broadcast and multicast service in mobile communication system | |
| TWI382701B (en) | Resources management in dual services terminal | |
| US8126464B2 (en) | Radio communication base station device | |
| US9648524B2 (en) | Method, node, and system for selecting target cell | |
| US8718651B2 (en) | Method, apparatus and system for informing a serving cell handover | |
| JP2007129706A (en) | System and method for tracking umts cell traffic | |
| CN1954632B (en) | Reestablishing wireless communication between a radio access network and a mobile station | |
| EP1962535B1 (en) | Cumulative neighboring cell list | |
| CN1822700A (en) | A radio network controller, a mobile communication system, and a neighbor-cell-list filtering method | |
| CN1695389A (en) | Method for optimizing resources in radio system, and radio system | |
| CN100531254C (en) | Dff-line fault information report method, device and off-line fault reason positioning system | |
| CN111937427A (en) | Method for constructing recorded measurement entries and device for supporting the method | |
| CN100403837C (en) | Method for reporting fault of updating cell in WCDMA system | |
| CN100366120C (en) | Wireless resource control connection fault information reporting method in wicle-band CDMA system | |
| KR20080085827A (en) | Method for improving intercellular handovers in mobile radio communication cellular systems | |
| CN100396135C (en) | Method for reporting RAB assignation fault in wide-band CDMA system | |
| CN101043716A (en) | Method for wireless resource management in wireless evolvement network and apparatus thereof | |
| CN1859682A (en) | Irregular frequency hard switching fault analyzing method | |
| CN1852532A (en) | Reporting method for switching fault between systems | |
| CN100452910C (en) | Soft switching fault analyzing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20180426 Address after: California, USA Patentee after: Global innovation polymerization LLC Address before: London, England Patentee before: GW partnership Co.,Ltd. Effective date of registration: 20180426 Address after: London, England Patentee after: GW partnership Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100428 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |