CN100531254C - Dff-line fault information report method, device and off-line fault reason positioning system - Google Patents
Dff-line fault information report method, device and off-line fault reason positioning system Download PDFInfo
- Publication number
- CN100531254C CN100531254C CNB2005100902957A CN200510090295A CN100531254C CN 100531254 C CN100531254 C CN 100531254C CN B2005100902957 A CNB2005100902957 A CN B2005100902957A CN 200510090295 A CN200510090295 A CN 200510090295A CN 100531254 C CN100531254 C CN 100531254C
- Authority
- CN
- China
- Prior art keywords
- call drop
- drop fault
- fault
- reason
- unit
- 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.)
- Active
Links
Images
Abstract
The method includes steps: setting up parameter of tone drop fault to be recorded in advance; recording each parameter value corresponding to a calling procedure respectively, and recording each time for recording corresponding each parameter value based on the parameter of tone drop fault setup; when tone drop fault occurs in the call, recorded data are reported to network management center. Correspondingly, the invention also discloses equipment for reporting information of tone drop fault, and system for positioning causation of tone drop fault. When tone drop fault occurs, the invention makes network device possible to report obtained information of tone drop fault to network management center in time, precisely and integrally.
Description
Technical field
The present invention relates to the optimisation technique of mobile communication network, relate in particular to a kind of report method and the reporting device of call drop fault message and system that the call drop failure cause is positioned of call drop fault message.
Background technology
Wideband Code Division Multiple Access (WCDMA) (WCDMA, Wideband Code Division Multiple Access) system is an open system, this system mainly comprises core net (CN, Core Network), UMTS Terrestrial radio access network (UTRAN, UMTS Terrestrial Radio Access Network) and user terminal (UE, User Equipment) three parts (other as webmaster and part such as alarm platform etc. not at the row of this patent description).As shown in Figure 1, radio network controller (RNC wherein, Radio NetworkController) belongs to the UTRAN part, exist standard interface between RNC and other network element, comprise: and the IU interface between the CN, and the IUB interface between the NodeB, and the IUR interface between other RNC, and and UE between the UU interface.
As shown in Figure 1, a RNC can connect one or more NodeB, and a NodeB comprises one or more sub-district.After the UE start, in a sub-district, just can receive the service of network side after resident, such as receiving system message and beep-page message.When other Packet Services such as UE conversation or browsing page, UE can trigger the flow process of series of standards interface in this sub-district, until finishing call establishment.
Just be initially located in talking state after the user access network success, for wireless communication system, it is resident that the user can choose a proper cell according to the cell selecting criterion of predesignating, all there is certain coverage each sub-district, and number of users is relevant in the transmitting power of this coverage and NodeB and the sub-district.But, because user's the mobility and the complexity of wireless network environment itself still may cause Call failures such as call drop.
In the wireless network running, especially at the networking initial stage, appear at this problem of generation call drop in the calling procedure through regular meeting, this will badly influence the communication quality problem, therefore how find and will address this is that, and just seem particularly important.
In the line service of existing network, carry out the analysis and the location of call drop reason usually by the following method:
1, performance statistics function
Performance statistics is a quality of weighing current network by statistical items crucial in the statistics network, this method is statistics number of dropped calls in a specific measuring period, and this statistical value fed back to network management center, comprehensively analyze by network management center, instruct by analysis result and deal with problems and carry out the network optimization.
But, performance statistics is a kind of long-time, a kind of statistical function of periodic duty in other words conj.or perhaps, adds up cutting off rate in a period of time, and this statistics itself is just very coarse, concrete scene information in the time of can not providing call drop is unfavorable for the concrete reason that causes the call drop fault is analyzed.
2, the whole network signaling test method
The method of signaling tracing is to follow the tracks of calling procedure especially from the standard agreement message in the different network elements in standard protocol interface (as UU, IUB etc.) by the signaling tracing instrument, 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 the call drop subproblem in the calling procedure simultaneously.
But, the whole network tracking is a kind of real-time tracking, need follow the tracks of by third party's instrument (as the signaling tracing instrument) in all standard protocol interface, this tracking can produce lot of data, present 2G total network signalling tracing has just been followed the tracks of the message between net, just the message of core net part is not followed the tracks of Access Network message partly.For the 3G system, these tracking messages will be magnanimity, when especially needing to follow the tracks of the message of Access Network part.How to obtain Useful Information from a large amount of tracking messages, will be very large workload.Also need very rich experience by signaling tracing 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.
3, alarm
When Radio Network System breaks down, as when the call drop fault takes place, warning system can be real-time the call drop fault is sent to network management center with the form of warning information, network management center can be by handling and analyze the warning information that receives, and to reach network failure (as the call drop fault) analyzed and got rid of.
But, what in general alarm was paid close attention to all is equipment fault, concern to user's fault is fewer, such as the user because wireless network environment is former thereby when causing call drop, adopt the alarm mode just can't embody, so alarm can not reflect or solve the failure and the orientation problem of call drop reason basically.
Summary of the invention
The technical problem to be solved in the present invention is to propose a kind of report method of call drop fault message, so that when the call drop fault takes place, the network equipment can be in time, accurately, intactly give network management center with the call drop fault information reporting that gets access to.
The technical problem to be solved in the present invention also is to propose a kind of reporting device of call drop fault message.
The technical problem to be solved in the present invention also is to propose a kind of system that the call drop failure cause is positioned.
For addressing the above problem, the technical scheme that the present invention proposes is as follows:
A kind of report method of call drop fault message is applied to broadband CDMA system, comprises step:
Preestablish the call drop fault parameter that will write down;
According to the call drop fault parameter that sets, each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record;
When the call drop fault appearred in this calling, the data that record is obtained reported network management center.
Preferably, described method also comprises step:
By the data that receive being analyzed, locate the reason that this calling produces the call drop fault at described network management center.
Preferably, described method also comprises step:
Preestablish code encoding/decoding mode;
The data that record obtains are encoded according to described code encoding/decoding mode, report network management center behind the formation code stream.
Preferably, described method also comprises step:
Described network management center is decoded to receiving code stream according to described code encoding/decoding mode, obtains corresponding data; And
By the data that obtain are analyzed, locate the reason that this calling produces the call drop fault.
Preferably, the described call drop fault parameter that will write down is set by operator.
Preferably, described code encoding/decoding mode is set by operator.
Preferably, described code encoding/decoding mode is ASN Abstract Syntax Notation 1 code encoding/decoding mode.
Preferably, the described call drop fault parameter that will write down comprises:
The RAB information before fault type, call drop reason, call drop time, user's international mobile subscriber identity, the indication of Radio Resource control connection state, the call drop and the RAB information of call drop.
Preferably, the described call drop fault parameter that will write down also comprises:
The type of the settling time of Radio Resource control connection, the current process of living in of user, best cell information and sub-district branch road information.
Preferably, described fault type is the call drop fault.
Preferably, described call drop reason comprises:
The inner reason of radio network controller, UU interface failure cause, IUB interface failure cause, IU interface failure cause and IUR interface failure cause.
Preferably, the inner reason of described radio network controller comprises:
Emission carrier power value, reception carrier performance number, common signal channel type and common signal channel sign.
Preferably, the inner reason of described radio network controller also comprises:
Congestion state, sub-district abnormality, common signal channel deexcitation, Signaling Radio Bearer reset, ASN Abstract Syntax Notation 1 error reason, L2 layer configuration failure reason, transport layer configuration failure reason, Memory Allocation failure and user's face are unusual.
Preferably, described sub-district abnormality comprises:
Sub-district deletion information, sub-district deexcitation information and sub-district blockage information.
Preferably, described UU interface failure cause comprises: UU interface reason and UU interface are overtime.
Preferably, described IUB interface failure cause comprises: IUB interface reason and IUB interface are overtime.
Preferably, described IU interface failure cause comprises: IU interface reason and IU interface are overtime.
Preferably, described IUR interface failure cause comprises: IUR interface reason and IUR interface are overtime.
Preferably, described Radio Resource control connection state is designated as:
The user is in the indication of CELL_DCH state; Or
The user is in the indication of CELL_FACH state; Or
The user is in the indication of CELL_PCH state; Or
The user is in the indication of URA_PCH state.
Preferably, the type of the current process of living in of described user is:
The Radio Resource control connection is set up process; Or
The wireless access load-bearing allocation process; Or
Soft switching process; Or
Direct-cut operation; Or
Repositioning process; Or
Different system changes to process; Or
The different system process that swaps out; Or
Cell updating course.
Preferably, the RAB information before the described call drop comprises:
Type of service, maximum bit rate for downlink, uplink maximum bit rate, wireless access bearing sign and RAB are set up or modification time.
Preferably, the RAB information before the described call drop also comprises:
Core network domain sign, guaranteed bit rate for downlink and up assurance bit rate.
Preferably, the RAB information of described call drop comprises: wireless access bearing sign and core network domain sign.
Preferably, described best cell information, sub-district branch road information comprise respectively:
Cell ID, Common Pilot Channel signal to noise ratio and Common Pilot Channel received signal code power.
Accordingly, the invention allows for a kind of reporting device of call drop fault message, be applied to broadband CDMA system, comprising:
First setup unit is used to preestablish the call drop fault parameter that will write down;
Record cell is used for the call drop fault parameter set according to described first setup unit, and each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record; With
Report the unit, be used for when the call drop fault appears in this calling, the data that described recording unit records is obtained report network management center.
Preferably, described device also comprises:
Second setup unit is used to preestablish code encoding/decoding mode; With
Coding unit, the code encoding/decoding mode that the data that are used for that described recording unit records is obtained are set according to described second setup unit carries out encoding process; The described unit that reports reports network management center with the code stream that coding unit coding back forms.
Preferably, in described first setup unit, set the call drop fault parameter that will write down by operator.
Preferably, in described second setup unit, set code encoding/decoding mode by operator.
Accordingly, the invention allows for a kind of system that the call drop failure cause is positioned, be applied to broadband CDMA system, comprise call drop fault information reporting device and network management center, described call drop fault information reporting device comprises:
First setup unit is used to preestablish the call drop fault parameter that will write down;
Record cell is used for the call drop fault parameter set according to described first setup unit, and each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record; With
Report the unit, be used for when the call drop fault appears in this calling, the data that described recording unit records is obtained report network management center;
Described network management center is located the reason that this calling produces the call drop fault by the described data that report the unit to report are analyzed.
Preferably, in described first setup unit, set the call drop fault parameter that will write down by operator.
Accordingly, the invention allows for a kind of system that the call drop failure cause is positioned, be applied to broadband CDMA system, comprise call drop fault information reporting device and network management center, described call drop fault information reporting device comprises:
First setup unit is used to preestablish the call drop fault parameter that will write down;
Second setup unit is used to preestablish code encoding/decoding mode;
Record cell is used for the call drop fault parameter that will write down set according to described first setup unit, and each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record;
Coding unit is used for when the call drop fault appears in this calling, and the code encoding/decoding mode that the data that described recording unit records is obtained are set according to described second setup unit carries out encoding process;
Report the unit, be used for the code stream that coding unit coding back forms is reported network management center;
Described network management center comprises:
Decoding unit is used for the code encoding/decoding mode that the described code stream that reports the unit to report is set according to described second setup unit is carried out decoding processing, to obtain corresponding data;
Analytic unit is used for the data that described decoding unit decodes obtains are analyzed, and locatees the reason that this calling produces the call drop fault.
Preferably, in described first setup unit, set the call drop fault parameter that will write down by operator; And in second setup unit, set code encoding/decoding mode.
The beneficial effect that the present invention can reach is as follows:
The present invention is by unified each call drop fault parameter that will write down of setting, with each call drop fault parameter that will write down according to unified setting, come the corresponding parameter value in a certain calling procedure is carried out record, and the writing time of each parameter value of corresponding record, and when the call drop fault appears in this calling, the data that record is obtained report network management center, thereby can be so that each equipment supplier can be according to the call drop fault parameter of (operator) regulation record, the call drop fault data is comparatively complete, in time, report network management center accurately, make the network management center side more accurate in locating handle to carry out the more autotelic network optimization to the reason that the call drop fault takes place.
Description of drawings
Fig. 1 is existing UTRAN architectural schematic;
Fig. 2 is the main realization principle flow chart of the report method of call drop fault message of the present invention;
Fig. 3 is the main composition structured flowchart of the reporting device of call drop fault message of the present invention;
Fig. 4 is that the reporting device of call drop fault message of the present invention increases the main structured flowchart of forming by decoding unit;
The composition structured flowchart of the system that first kind of proposing for the present invention of Fig. 5 positions the call drop failure cause;
The composition structured flowchart of the system that second kind of proposing for the present invention of Fig. 6 positions the call drop failure cause.
Embodiment
Design philosophy of the present invention provides a kind of call history (CHR, CALL HISTORYRECORD), the problem that occurs in the calling procedure can be followed the tracks of in this record, and feed back to network management center by the standard agreement form of message, can analyze the reason that call drop appears in calling according to these historical records in the network management center side, and recover fault by taking to handle means (as the network optimization, software upgrading etc.) accordingly, reach the purpose of the network optimization.
Be explained in detail below in conjunction with the main realization principle and the embodiment thereof of each accompanying drawing the report method of call drop fault message of the present invention.Please refer to Fig. 2, this figure is the main realization principle flow chart of the report method of call drop fault message of the present invention, and its main implementation procedure is as follows:
Step S10 preestablishes the call drop fault parameter that will write down; Wherein can unify to set each call drop fault parameter that will write down by operator;
Step S20 according to above-mentioned predefined each call drop fault parameter, carries out record respectively to each parameter value of correspondence in the calling procedure, and the writing time of each parameter value of corresponding record;
Step S30, when the call drop fault appearred in this calling, the data that above-mentioned record is obtained reported network management center;
Step S40, by the data that receive being analyzed in the network management center side, locate the reason of this calling generation call drop fault, and call drop failure cause by navigating to, adopt corresponding means (as the network optimization, software upgrading etc.) to recover the call drop fault, to reach the purpose of the network optimization.
Wherein can also preestablish a standard code encoding/decoding mode, as the code encoding/decoding mode set can but be not limited to: ASN Abstract Syntax Notation 1 (ASN.1, Abstract Syntax Notation One) code encoding/decoding mode, wherein the ASN.1 code encoding/decoding mode is the standard encoding and decoding agreement in the 3GPP standard criterion.Preferably, the code encoding/decoding mode that can unify established standards by operator.
In above-mentioned steps S30, just can carry out encoding process to the data that record obtains like this, report network management center behind the formation code stream according to the standard code encoding/decoding mode of setting;
Network management center carries out decoding processing according to the standard code encoding/decoding mode of above-mentioned setting to receiving code stream again, obtains corresponding data;
In the network management center side again by the data that obtain are analyzed, locate the reason of this calling generation call drop fault, and the call drop failure cause by navigating to, adopt corresponding means (as the network optimization, software upgrading etc.) to recover the call drop fault, to reach the purpose of the network optimization.
The design philosophy of the report method of call drop fault message wherein of the present invention is based on the output content that the call drop fault log is not write down in the present 3GPP standard and is described, and comprises the descriptions such as crucial scene information of call drop reason and call drop.The present invention is exactly at this problem, has proposed unified, the perfect call drop fault log record output content of a cover, with the output content of standard call drop fault log record.Under the call drop situation, can analyze by the related parameter values that the call drop fault log record of this standard is exported, locate the reason that the call drop fault occurs, carry out the network optimization to instruct operator.
As shown in the table, these contents (are the above-mentioned described predefined call drop fault parameter that will write down, below each parameter is referred to as " network element "), each net element information (the call drop fault parameter value that will write down) all can obtain at network side, when call drop takes place, network side need be exported following cell information, and according to the output of encoding of the ASN.1 code encoding/decoding mode of 3GPP standard.
Table 1: the description of all cell information is divided into essential, optional, condition and selects three classes
The abbreviation implication
This cell of MP must be comprised in the failure cause record
This cell of OP may be comprised in the failure cause record
When C satisfies in condition, this cell will be comprised in the failure cause record
In, otherwise this cell will can not be comprised in the failure cause record,
Wherein the predefined call drop fault parameter that will write down comprise:
RAB (RAB) information before fault type, call drop reason, call drop time, user's international mobile subscriber identity (IMSI), the indication of Radio Resource control connection (RRC) state, the call drop and RAB (RAB) information of call drop;
The predefined call drop fault parameter that will write down also comprise:
The settling time of Radio Resource control connection (RRC), the type of the current process of living in of user, best cell information and sub-district branch road information.
Concrete, network side need be exported each cell information shown in the following form (each cell information is represented a call drop fault parameter) when the call drop fault took place, wherein the cell in this form can be expanded from now on, extended mode adopts the EXTENSION mode among the ASN.1, to guarantee the compatibility of expansion front and back:
Table 2: each cell that network side need be exported when the call drop fault took place:
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Syntactic description (Semantics description) |
Failure Type | MP | Failure Type 2.2.2.2 | Fault type | |
Failure information elements | ||||
>Drop Cause | MP | Drop Cause 2.2.2.3 | The call drop reason | |
>Drop Time | MP | BIT STRING(32) | The call drop time (date: the time: divide: second) | |
UE information elements | ||||
>IMSI | MP | IMSI 2.2.2.4 | International mobile subscriber identity | |
>RRC Establishment Time | MP | BIT STRING(32) | RRC settling time (date: the time: divide: second) | |
>RRC State Indicator | MP | RRC State Indicator 2.2.2.5 | The RRC connection status | |
Current Procedure | OP | Procedure Type 2.2.2.6 | The active procedure type | |
RAB Information elements | ||||
>RAB information | MP | RAB List Information 2.2.2.7 | RAB list information before the call drop | |
>Drop RAB information | MP | Failed RAB List Information 2.2.2.8 | The RAB list information of call drop | |
Best Cell information elements | ||||
>Best Cell Information | MP | Cell Information 2.2.2.9 | Best cell information | |
Cell Leg Information elements | ||||
>Cell Leg Information | MP | 0~6 | Cell Information 2.2.2.9 | Sub-district branch road information |
Because fault type is the call drop fault, so need be DROP, represent call drop with record trouble in the fault type cell, the form of fault type is as shown in the table:
Table 3: fault type, then select DROP when being call drop as fault
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Syntactic description (Semantics description) |
Failure Type | MP | Enumerate ENUMERATED RRC SETUP; RAB ASSIGNMENT; SOFT HANDOVER; HARD HANDOVER; RELOCATION; INTER RAT; HANDOVER IN; INTER RAT HANDOVER OUT; CELL UPDATE; DROP; NULL) | Fault type is enumerated the Radio Resource control connection and is set up; Wireless access load-bearing allocation; Soft handover; Direct-cut operation; Reorientation; Different system switch into; Different system switches; Cell update; Call drop; Other) |
Wherein the call drop reason comprises: the inner reason of radio network controller (RNC), UU interface failure cause, IUB interface failure cause, IU interface failure cause and IUR interface failure cause:
Wherein the inner reason of RNC comprises:
Emission carrier power value, reception carrier performance number, common signal channel type and common signal channel sign; Comprise also that congestion state, sub-district abnormality, common signal channel deexcitation, Signaling Radio Bearer reset (SRB resets), ASN Abstract Syntax Notation 1 error reason, L2 layer configuration failure reason, transport layer configuration failure reason, Memory Allocation failure and user's face be unusual;
Wherein the sub-district abnormality comprises: sub-district deletion information, sub-district deexcitation information and sub-district blockage information; Wherein UU interface failure cause comprises: UU interface reason and UU interface are overtime; Wherein IUB interface failure cause comprises: IUB interface reason and IUB interface are overtime.Wherein IU interface failure cause comprises: IU interface reason and IU interface are overtime.Wherein IUR interface failure cause comprises: IUR interface reason and IUR interface are overtime.
Table 4: the detailed reason of call drop
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Syntactic description (Semantics description) |
CHOICE Cause Group | MP | |||
>RNC Inner Failure Choice | OP | The inner reason of RNC | ||
>>Congestion | OP | Congested | ||
>>>Transmitted Carrier Power Value | MP | INTEGER(0..100) | The emission carrier power | |
>>>Received Total Wide Band Power Value | MP | INTEGER(0..621) | Reception carrier power | |
>>Cell Abnormal | OP | ENUMERATED(RNC Trigger,NodeB Trigger | The sub-district is unusual | |
>>>CHOICE | ||||
>>>>Cell Delete | OP | The sub-district deletion | ||
>>>>Cell Disable | OP | The sub-district deexcitation | ||
>>>>Cell Block | OP | The sub-district is blocked | ||
>>Common Channel disable | OP | ENUMERATED(RNC Trigger,NodeB Trigger) | The common signal channel deexcitation | |
>>>Common Channel Type | MP | ENUMERATED Common Physical Channel; Common Transport Channel; | The common signal channel type is enumerated public physic channel; Common transport channel; | |
>>>Common Channel Identity | MP | INTEGER(0..255) | Common signal channel ID | |
>>SRB reset | OP | Signaling RB resets | ||
>>ASN.1 Error Cause | ENUMERATED Transfer Syntax Error; Abstract Syntax Error; Logical Error; | ASN Abstract Syntax Notation mistake 1 is enumerated the transfer syntax mistake; The abstract syntax mistake; Logic error; | ||
>>L2 Configuration Error Cause | OP | L2 Configuration Error Cause | The L2 configuration failure | |
>>Transport layer Configuration Error Cause | OP | Transport layer Configuration Error Cause | The transport layer configuration failure | |
>>Allocation Memory Failure | OP | The Memory Allocation failure | ||
>>User Plane Error Cause | OP | User Plane Error Cause | User's face is unusual | |
>>Unspecified | OP | |||
>UU Interface Failure Choice | OP | The failure of UU interface is selected | ||
>>UU Cause | OP | UU cause | UU interface reason, referring to |
3GPP TS25.331 | ||||
>>UU Time Out | OP | The UU interface is overtime | ||
>IUB Interface Failure Choice | OP | The failure of IUB interface is selected | ||
>>IUB Cause | OP | IUB cause | IUB interface reason is referring to 3GPP TS25.433 | |
>>IUB Time Out | OP | The IUB interface is overtime | ||
>IU Interface Failure Choice | OP | The failure of IU interface is selected | ||
>>IU Cause | OP | IU cause | IU interface reason is referring to 3GPP TS25.413 | |
>>IU Time Out | OP | The IU interface is overtime | ||
>IUR Interface Failure Choice | OP | The failure of IUR interface is selected | ||
>>IUR Cause | OP | IUR cause | IUR interface reason is referring to 3GPP TS25.423 | |
>>IUR Time Out | OP | The IUR interface is overtime |
Table 5:IMSI (GSM-MAP)
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Syntactic description (Semantics description) |
IMSI | MP | 6 to 21 | The first element contains the first IMSI digit, (first cell comprises first IMSI numeral to the second element the second IMSI digit and so on., second cell comprises second IMSI numeral .... and the like) Although normally upto 15 digits are used for this IE, a bigger length is used to support future extension. (using 15 numerals usually, expansion after being used for supporting above 15) | |
>IMSI digit | MP | INTEGER(0.. 9) |
Wherein, the indication of RRC connection status comprises:
The user is in the indication of CELL_DCH state; Or
The user is in the indication of CELL_FACH state; Or
The user is in the indication of CELL_PCH state; Or
The user is in the indication of URA_PCH state;
Table 6:RRC State Indicator
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Syntactic description (Semantics description) |
RRC State indicator | MP | Enumerate ENUMERATED (CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH) | The indication of wireless connection control state |
Wherein the type of the current process of living in of user is:
RRC connects the process of setting up; Or RAB assignment process; Or soft switching process; Or direct-cut operation; Or repositioning process; Or different system changes to process; Or the different system process that swaps out; Or cell updating course;
Table 7: the residing procedural type of active user (Procedure Type)
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Syntactic description (Semantics description) |
Procedure Type | MP | ENUMERATED RRC SETUP; RAB ASSIGNMENT; SOFT HANDOVER; HARD HANDOVER; RELOCATION; INTER RAT; HANDOVER IN; INTER RAT HANDOVER OUT; CELL UPDATE; NULL) | Procedural type is enumerated the Radio Resource control connection and is set up; Wireless access load-bearing allocation; Soft handover; Direct-cut operation; Reorientation; Different system switch into; Different system switches; Cell update; Other |
Wherein the RAB information before the conversation loss comprises: type of service, maximum bit rate for downlink, uplink maximum bit rate, wireless access bearing sign and RAB are set up or modification time; Also comprise core network domain sign, guaranteed bit rate for downlink and up assurance bit rate;
Table 8: the RAB information list (RAB List Information) that the user is current
IE/Group Name | Whether need (Need) | Multi | Reftype (Type and referenee) | Syntactic description (Semantics description) |
RABs Information List | 1~ maxnoo f RABs | The maximum RAB number of 256 1 UE of RAB information list Maximum no.of RABs for one UE.Value is is 256 | ||
>Traffic Class | MP | ENUMERATED conversational; streaming; Interactive; Background;... | Type of service is enumerated session; Business Stream; Interactive service; Background service; | |
>CN Information identity | OP | CN Domain identity | The CN domain identifier | |
>DL Maximum Bit Rate | MP | INTEGER (1..16,000,000) | Descending maximum BIT leads | |
>UL Maximum Bit Rate | MP | INTEGER (1..16,000,000) | Up maximum BIT leads | |
>DL Guaranteed Bit Rate | OP | INTEGER (0..16,000,000) | Descending guarantee BIT leads | |
>UL Guaranteed Bit Rate | OP | INTEGER (0..16,000,000) | Up assurance BIT leads | |
>RAB ID | MP | BIT STRING(8) | Wireless access bearing sign | |
>RAB To Be Setup Or Modified Time | MP | BIT STRING (32) | RAB sets up or modification time (date DATE: hour HOUR: minute MINUTE: second SECOND) |
Wherein the RAB information of conversation loss comprises: wireless access bearing sign and core network domain sign;
Table 9: the RAB information list of conversation loss (Failed RAB List Information)
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Parametric description (Semantics description) |
Fail RABs List | 1 to255 | The RAB tabulation of conversation loss | ||
>RAB ID | MP | BIT STRING(8) | Wireless access bearing sign | |
>CN Domain Identity | MP | CN Domain Identity | The CN domain identifier |
Wherein best cell information and sub-district branch road information comprise respectively: cell ID, Common Pilot Channel signal to noise ratio and Common Pilot Channel received signal code power;
Table 10: cell information (Cell Information)
Cell name (Information Element/Group name) | Whether need (Need) | Multi | Reftype (Type and reference) | Syntactic description (Semantics description) |
Cell identity | MP | BIT STRING(28) | Cell ID | |
Measurement result for current cell | The measurement result of current area | |||
>CPICH Ec/N0 | MP | INTEGER(0.. 49) | Common Pilot Channel Ec/N0 | |
>CPICH RSCP | OP | INTEGER(0.. 91) | The Common Pilot Channel received signal code power |
Below by an example specific implementation process of the report method of call drop fault message of the present invention, call drop analysis examples are described:
Carrying out the PS data of 64K when carrying out the CS12.2K voice communication such as the user and downloading, call drop takes place suddenly in the user in moving process;
After network management center is received user's complaint, can be according to this user's phone number (MSISDN, Mobile Station Identifier Number), find the IMSI of this user mobile phone, in the call drop fault log record that receives, search for this user's call drop fault message according to the time period of IMSI and customer complaint.Search Results finds to have two failure loggings, and table 11 shows that fault is a call drop, and table 12 shows that fault is the soft handover failure, and is as follows respectively:
Table 11: call drop fault log record
Table 12: soft handover fault log record:
User ID (IMSI) | 460070114001271 |
Fault type | The soft handover failure |
Failure cause | The failure of Target cell access |
Small area jam: RTWP:403 TCP:90 | |
Fault time | 09:38:24 on the 30th |
RRC settling time | 09:25:12 on the 30th |
The RRC connection status | DCH |
Business is set up information before the call drop | 2 |
CS DOMAIN, CONVERSATIONAL (circuit domain, session service); UL/DL Bit Rate:12200 (on/descending BIT lead); UL/DL Guaranteed Bit Rate:4.75K (up-downgoing guarantees that BIT leads); Settling time: 9:30:15 RABID:2 (RAB sign) on the 30th; PS DOMAIN, BACKGROUD (packet domain, background service); UL/DL Bit Rate:64K/64K (on/descending BIT lead); Settling time: 9:25:15 RABID:1 (RAB sign) on the 30th; | |
Best cell | RNC:10,CELLID:101 |
Best cell RSCP | -80dbm |
Best cell EcNo | -12db |
Other Serving cell | Do not have |
Other Serving cells RSCP | Do not have |
Other Serving cells EcNo | Do not have |
Detected set sub-district 1 information | RNC:10,CELLID:109 |
Detected set sub-district 1RSCP | -85dbm |
Detected set sub-district 1EcNo | -10db |
Detected set sub-district 2 information | RNC:10,CELLID:120 |
Detected set sub-district 2RSCP | -83dbm |
Detected set sub-district 2EcNo | -12db |
Switching target small area information | RNC:10,CELLID:109 |
Can obtain following information by analytical table 11:
1) the call drop reason is that SRB resets, and the call drop time is 09:40:40;
2) RSCP of current best cell is-95dbm, and best cell EcNo is-15db to illustrate that the best cell signal quality is very poor;
Can obtain following information by analytical table 12:
11) in preceding 2 seconds of call drop, just the fault that soft handover is failed takes place in 09:38:24;
12) user has moved to the common area of coverage of sub-district 101 and 109 at that time, this moment, the quality of best cell 101 still was good, and the thresholding of soft handover 1A incident (the 1A incident: the cell signal quality reaches reporting range) has been satisfied in the sub-district of sub-district 109, thereby UE has reported the 1A incident No. 109 sub-districts;
13) after RNC judges these No. 109 sub-districts and satisfies soft handoff condition, triggered soft handover (illustrating that 101 and No. 109 sub-districts belong to same NODEB), but because the current load in No. 109 sub-districts is very high, wherein carrier transmit power TCP has reached 90%, has surpassed the thresholding that inserts this sub-district;
14) because Target cell 109 loads have very heavily caused the soft handover failure.
The above analysis as can be known, the reason of conversation loss is: user's moving process Central Plains cell quality variation, and the Target cell load is overweight can not in time switch to the sub-district of better quality and caused call drop.
Through top analysis as can be known, the overload of Target cell, optimize personnel thus and can take following measure to carry out the elimination of call drop fault:
A) whether Target cell is in the center of focus, if, should optimize network so, minimizing with this Target cell as the adjacent area;
B) whether the pilot power of Target cell is provided with too greatly, causes too many user to be linked in this sub-district; If should reduce the pilot power of this Target cell so, so that make the user can be evenly distributed to other neighbor cell;
C) cell selecting of modifying target sub-district and reselecting parameters are so that make the easier at one's leisure gravity treatment of user in this sub-district arrive other adjacent area.
This shows; at the initial stage of 3G network operation; occur because 3G network covers irrational situation through regular meeting; excessive such as the design of sub-district area coverage; owing to the user causes local resource to exhaust too much, perhaps Pei Zhi neighboring area signal is in reason such as the area of coverage is too poor, and these reasons will cause the user to call out in these places or be in user in the calling procedure and moved to these local time; the signal of communication non-constant that can become just call drop can occur when serious.At this situation, the report method of call drop fault message of the present invention can help to optimize the solution that man analysis call drop reason and guides failure problems, also can make fault log write down output information and format specificationization, form one share, open fault location platform.
Accordingly, the invention allows for a kind of reporting device of call drop fault message, as shown in Figure 3, this figure is the main composition structured flowchart of the reporting device of call drop fault message of the present invention, it is mainly by first setup unit 10, record cell 20 with report unit 30 to form, the effect of each component units and between annexation specific as follows:
Please refer to Fig. 4, this figure is that the reporting device of call drop fault message of the present invention increases the main structured flowchart of forming by decoding unit, it is on the basis of above-mentioned main composition structure, and also increasing has second setup unit 40 and coding unit 50, and these two effects that increase the unit are specific as follows:
Accordingly, the invention allows for two kinds of systems that the call drop failure cause is positioned, as follows respectively:
Please refer to Fig. 5, the composition structured flowchart of this figure system that to be first kind of proposing of the present invention position the call drop failure cause; It mainly is made up of call drop fault information reporting device 100 and network management center 200, wherein mainly comprises in the call drop fault information reporting device 100:
Please refer to Fig. 6, the composition structured flowchart of this figure system that to be second kind of proposing of the present invention position the call drop failure cause; It mainly is made up of call drop fault information reporting device 100 and network management center 200, wherein mainly comprises in the call drop fault information reporting device 100:
Wherein mainly comprise in the network management center 200:
Decoding unit 210 exists logic to be connected with the unit 30 that reports in the call drop fault information reporting device 100, and is used for the code encoding/decoding mode that the code stream that reports unit 30 to report is set according to second setup unit 40 is carried out decoding processing, to obtain corresponding data;
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (32)
1, a kind of report method of call drop fault message is applied to broadband CDMA system, it is characterized in that, comprises step:
Preestablish the call drop fault parameter that will write down;
According to the call drop fault parameter that sets, each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record;
When the call drop fault appearred in this calling, the data that record is obtained reported network management center.
2, the method for claim 1 is characterized in that, also comprises step:
By the data that receive being analyzed, locate the reason that this calling produces the call drop fault at described network management center.
3, the method for claim 1 is characterized in that, also comprises step:
Preestablish code encoding/decoding mode;
The data that record obtains are encoded according to described code encoding/decoding mode, report network management center behind the formation code stream.
4, method as claimed in claim 3 is characterized in that, also comprises step:
Described network management center is decoded to receiving code stream according to described code encoding/decoding mode, obtains corresponding data; And
By the data that obtain are analyzed, locate the reason that this calling produces the call drop fault.
As the described method of 1~4 any claim, it is characterized in that 5, the described call drop fault parameter that will write down is set by operator.
6, method as claimed in claim 3 is characterized in that, described code encoding/decoding mode is set by operator.
As claim 3 or 6 described methods, it is characterized in that 7, described code encoding/decoding mode is ASN Abstract Syntax Notation 1 code encoding/decoding mode.
8, the method for claim 1 is characterized in that, the described call drop fault parameter that will write down comprises:
The RAB information before fault type, call drop reason, call drop time, user's international mobile subscriber identity, the indication of Radio Resource control connection state, the call drop and the RAB information of call drop.
9, method as claimed in claim 8 is characterized in that, the described call drop fault parameter that will write down also comprises:
The type of the settling time of Radio Resource control connection, the current process of living in of user, best cell information and sub-district branch road information.
10, method as claimed in claim 8 is characterized in that, described fault type is the call drop fault.
11, method as claimed in claim 8 is characterized in that, described call drop reason comprises:
The inner reason of radio network controller, UU interface failure cause, IUB interface failure cause, IU interface failure cause and IUR interface failure cause.
12, method as claimed in claim 11 is characterized in that, the inner reason of described radio network controller comprises:
Emission carrier power value, reception carrier performance number, common signal channel type and common signal channel sign.
13, method as claimed in claim 12 is characterized in that, the inner reason of described radio network controller also comprises:
Congestion state, sub-district abnormality, common signal channel deexcitation, Signaling Radio Bearer reset, ASN Abstract Syntax Notation 1 error reason, L2 layer configuration failure reason, transport layer configuration failure reason, Memory Allocation failure and user's face are unusual.
14, method as claimed in claim 13 is characterized in that, described sub-district abnormality comprises:
Sub-district deletion information, sub-district deexcitation information and sub-district blockage information.
15, method as claimed in claim 11 is characterized in that, described UU interface failure cause comprises: UU interface reason and UU interface are overtime.
16, method as claimed in claim 11 is characterized in that, described IUB interface failure cause comprises: IUB interface reason and IUB interface are overtime.
17, method as claimed in claim 11 is characterized in that, described IU interface failure cause comprises: IU interface reason and IU interface are overtime.
18, method as claimed in claim 11 is characterized in that, described IUR interface failure cause comprises: IUR interface reason and IUR interface are overtime.
19, method as claimed in claim 8 is characterized in that, described Radio Resource control connection state is designated as:
The user is in the indication of CELL_DCH state; Or
The user is in the indication of CELL_FACH state; Or
The user is in the indication of CELL_PCH state; Or
The user is in the indication of URA_PCH state.
20, method as claimed in claim 9 is characterized in that, the type of the current process of living in of described user is:
The Radio Resource control connection is set up process; Or
The wireless access load-bearing allocation process; Or
Soft switching process; Or
Direct-cut operation; Or
Repositioning process; Or
Different system changes to process; Or
The different system process that swaps out; Or
Cell updating course.
21, method as claimed in claim 8 is characterized in that, the RAB information before the described call drop comprises:
Type of service, maximum bit rate for downlink, uplink maximum bit rate, wireless access bearing sign and RAB are set up or modification time.
22, method as claimed in claim 21 is characterized in that, the RAB information before the described call drop also comprises:
Core network domain sign, guaranteed bit rate for downlink and up assurance bit rate.
23, method as claimed in claim 8 is characterized in that, the RAB information of described call drop comprises: wireless access bearing sign and core network domain sign.
24, method as claimed in claim 9 is characterized in that, described best cell information, sub-district branch road information comprise respectively:
Cell ID, Common Pilot Channel signal to noise ratio and Common Pilot Channel received signal code power.
25, a kind of reporting device of call drop fault message is applied to broadband CDMA system, it is characterized in that, comprising:
First setup unit is used to preestablish the call drop fault parameter that will write down;
Record cell is used for the call drop fault parameter set according to described first setup unit, and each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record; With
Report the unit, be used for when the call drop fault appears in this calling, the data that described recording unit records is obtained report network management center.
26, device as claimed in claim 25 is characterized in that, also comprises:
Second setup unit is used to preestablish code encoding/decoding mode; With
Coding unit, the code encoding/decoding mode that the data that are used for that described recording unit records is obtained are set according to described second setup unit carries out encoding process; The described unit that reports reports network management center with the code stream that coding unit coding back forms.
27, as claim 25 or 26 described devices, it is characterized in that, in described first setup unit, set the call drop fault parameter that will write down by operator.
28, device as claimed in claim 26 is characterized in that, sets code encoding/decoding mode by operator in described second setup unit.
29, a kind of system that the call drop failure cause is positioned is applied to broadband CDMA system, it is characterized in that, comprises call drop fault information reporting device and network management center, and described call drop fault information reporting device comprises:
First setup unit is used to preestablish the call drop fault parameter that will write down;
Record cell is used for the call drop fault parameter set according to described first setup unit, and each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record; With
Report the unit, be used for when the call drop fault appears in this calling, the data that described recording unit records is obtained report network management center;
Described network management center is located the reason that this calling produces the call drop fault by the described data that report the unit to report are analyzed.
30, system as claimed in claim 29 is characterized in that, sets the call drop fault parameter that will write down by operator in described first setup unit.
31, a kind of system that the call drop failure cause is positioned is applied to broadband CDMA system, it is characterized in that, comprises call drop fault information reporting device and network management center, and described call drop fault information reporting device comprises:
First setup unit is used to preestablish the call drop fault parameter that will write down;
Second setup unit is used to preestablish code encoding/decoding mode;
Record cell is used for the call drop fault parameter that will write down set according to described first setup unit, and each parameter value of correspondence in the calling procedure is carried out record respectively, and the writing time of each parameter value of corresponding record;
Coding unit is used for when the call drop fault appears in this calling, and the code encoding/decoding mode that the data that described recording unit records is obtained are set according to described second setup unit carries out encoding process;
Report the unit, be used for the code stream that coding unit coding back forms is reported network management center;
Described network management center comprises:
Decoding unit is used for the code encoding/decoding mode that the described code stream that reports the unit to report is set according to described second setup unit is carried out decoding processing, to obtain corresponding data;
Analytic unit is used for the data that described decoding unit decodes obtains are analyzed, and locatees the reason that this calling produces the call drop fault.
32, system as claimed in claim 31 is characterized in that, sets the call drop fault parameter that will write down by operator in described first setup unit; And in second setup unit, set code encoding/decoding mode.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2005100902957A CN100531254C (en) | 2005-08-12 | 2005-08-12 | Dff-line fault information report method, device and off-line fault reason positioning system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2005100902957A CN100531254C (en) | 2005-08-12 | 2005-08-12 | Dff-line fault information report method, device and off-line fault reason positioning system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1852347A CN1852347A (en) | 2006-10-25 |
CN100531254C true CN100531254C (en) | 2009-08-19 |
Family
ID=37133814
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB2005100902957A Active CN100531254C (en) | 2005-08-12 | 2005-08-12 | Dff-line fault information report method, device and off-line fault reason positioning system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN100531254C (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI664835B (en) * | 2017-10-18 | 2019-07-01 | 中華電信股份有限公司 | An intelligent method for analyzing subscriber's session drop reason in mobile network |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101212308A (en) | 2006-12-30 | 2008-07-02 | 华为技术有限公司 | Statistical report method |
CN102572888B (en) * | 2010-12-24 | 2014-10-08 | 中国移动通信集团北京有限公司 | Method and device for determining road dropped call event |
CN102612063A (en) * | 2011-01-20 | 2012-07-25 | 华为技术有限公司 | Method and device for obtaining environmental information of wireless channel, and wireless network control equipment |
WO2013082762A1 (en) * | 2011-12-06 | 2013-06-13 | 华为技术有限公司 | Communication method and device |
DE112013000236B4 (en) | 2013-11-19 | 2018-06-21 | Komatsu Ltd. | Communication management system and communication management method |
CN105873094A (en) * | 2015-12-08 | 2016-08-17 | 乐视移动智能信息技术(北京)有限公司 | Call-drop testing method and device |
CN108156622A (en) * | 2018-01-05 | 2018-06-12 | 武汉虹旭信息技术有限责任公司 | The monitoring system and method for LTE network cell signal quality and link load |
CN108494976A (en) * | 2018-03-26 | 2018-09-04 | 安徽德特信息技术有限公司 | Call drop failure auto-alarm-signal keying device uploading system based on signalling analysis and its method |
CN110944347A (en) * | 2019-10-23 | 2020-03-31 | 宇龙计算机通信科技(深圳)有限公司 | Dropped call detection method, dropped call detection device, storage medium and terminal |
-
2005
- 2005-08-12 CN CNB2005100902957A patent/CN100531254C/en active Active
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI664835B (en) * | 2017-10-18 | 2019-07-01 | 中華電信股份有限公司 | An intelligent method for analyzing subscriber's session drop reason in mobile network |
Also Published As
Publication number | Publication date |
---|---|
CN1852347A (en) | 2006-10-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN100531254C (en) | Dff-line fault information report method, device and off-line fault reason positioning system | |
RU2425466C2 (en) | Detecting neighbouring cells | |
US20180035321A1 (en) | Method and system for collecting terminal measurement data | |
CN101273556B (en) | Method and device for arranging and changing schedule of packet data service | |
CN100544275C (en) | Detect the wireless network air interface | |
US20070099561A1 (en) | System and method for tracking UMTS cell traffic | |
Kreher | UMTS performance measurement: a practical guide to KPIs for the UTRAN environment | |
US8098586B2 (en) | Determining configuration parameters of a mobile network | |
EP1765026A2 (en) | Allocation of a performance indicator among cells in a cellular communication system | |
KR100932485B1 (en) | How to Provide Broadcast and / or Multicast Services | |
CN104662948A (en) | Communication device, mobile terminal, and methods for traffic hotspot measurement | |
US20110064059A1 (en) | Apparatuses, Methods and Computer Program for Cell Reselection Evaluation | |
CN102783200A (en) | Geographical determination of coverage in communications systems | |
US8219075B2 (en) | Method for testing performance of a mobile telecommunications network | |
US20080220766A1 (en) | Method for Control of Radio Measurements in a Cellular Mobile Radio Communication System | |
US6885645B2 (en) | Method and mobile station for controlling bearer assignment | |
CN100403837C (en) | Method for reporting fault of updating cell in WCDMA system | |
US8744432B2 (en) | Performance management for a telecommunication network | |
US20050163074A1 (en) | Method of communication | |
CN103260176A (en) | Minimized drive test method, network element and system | |
US20200413271A1 (en) | Automatically optimizing cell parameter of serving base station | |
CN106993314B (en) | Fallback performance judgment method and device for circuit switched fallback | |
CN100396136C (en) | Method for reporting fault in 3-to-2G system switching-over course | |
EP1215928A2 (en) | Intelligent optimisation system and method of optimising communication performance in a cellular telecommunications network | |
CN100366120C (en) | Wireless resource control connection fault information reporting method in wicle-band CDMA system |
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 |