CN100366120C - Wireless resource control connection fault information reporting method in wicle-band CDMA system - Google Patents
Wireless resource control connection fault information reporting method in wicle-band CDMA system Download PDFInfo
- Publication number
- CN100366120C CN100366120C CNB2005100886812A CN200510088681A CN100366120C CN 100366120 C CN100366120 C CN 100366120C CN B2005100886812 A CNB2005100886812 A CN B2005100886812A CN 200510088681 A CN200510088681 A CN 200510088681A CN 100366120 C CN100366120 C CN 100366120C
- Authority
- CN
- China
- Prior art keywords
- failure
- rrc
- information
- fault
- cell
- 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
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000005259 measurement Methods 0.000 claims description 27
- 108010003272 Hyaluronate lyase Proteins 0.000 claims description 16
- 239000012141 concentrate Substances 0.000 claims description 5
- 238000012544 monitoring process Methods 0.000 claims description 3
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 claims 3
- 230000008569 process Effects 0.000 description 11
- 230000011664 signaling Effects 0.000 description 11
- 238000004458 analytical method Methods 0.000 description 9
- 238000007726 management method Methods 0.000 description 9
- 230000001360 synchronised effect Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000008707 rearrangement Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 238000010998 test method Methods 0.000 description 2
- QXOQNNAWFUXKMH-UHFFFAOYSA-N 1-(Malonylamino)cyclopropanecarboxylic acid Chemical compound OC(=O)CC(=O)NC1(C(O)=O)CC1 QXOQNNAWFUXKMH-UHFFFAOYSA-N 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000000205 computational method Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 239000012467 final product Substances 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000005303 weighing Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention relates to method for reporting radio resource control (RRC) linkage fault information in a wideband CDMA system (WCDMA). An RRC linkage fault parameter information set is set, and parameter items for reporting RRC linkage faults are arranged in the RRC linkage fault parameter information set; when an RRC connection is established, the following step are comprised: A. the RRC connection is monitored, and a receiving system sends a fault signal when the RRC connection fails; B. the parameter items required to report in the RRC linkage fault information set are inquired according to fault reasons designated by the fault signal; C. corresponding parameter values are obtained from the system according to the parameter items and written into a fault reporting message; D. the fault reporting message is sent to a network management center. The method described by the present invention can obtain RRC connection fault reasons, and thereby, the problem that connection establishment fails can be solved.
Description
Technical field
The present invention relates to the communications field, relate in particular to Radio Resource control (RRC) connection fault information reporting method in a kind of broadband CDMA system (WCDMA).
Background technology
The WCDMA system is an open system, and this system mainly comprises core net (CN), UMTS wireless access network (UTRAN) and subscriber equipment (UE) three parts.RNC wherein belongs to the UTRAN part, and RNC and other network element exist standard interface, such as and CN between the IU interface, and be the IUB interface between the NodeB, and be the IUR interface between other RNC that also having the interface of UE and RNC certainly is the UU interface.
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 begin to receive the service of network side after resident, such as receiving system message and paging receiving message.When UE called or receive calls, UE will make a call in this sub-district so, and triggered the flow process of series of standards interface.
In the process of wireless network operation, especially the networking initial stage, through regular meeting this problem appears, and how to find and address this is that, what just show is particularly important.The agreement of 3GPP does not have the corresponding protocol standard to this TRACE simultaneously, how to carry out agreement output so that location RRC connects and sets up failure problems, can become an emphasis in the process of network operation.This patent has just proposed the solution of a cover standard agreement and the method for analysis at this problem.
In the line service of existing network, carry out accident analysis 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 that statistics RRC connection in a specific measuring period is set up successfully/frequency of failure, and this statistical value fed back to network management system, comprehensively analyze by network management system, instruct dilatation and problem to solve existing network by analysis result.
2) the whole network signaling test method.The method of signaling tracing be by the signaling tracing instrument in standard protocol interface (as UU, IUB) follow the tracks of calling procedure in especially from the standard agreement message of 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 subproblem simultaneously.
3) alarm.Network management system can be carried out the eliminating and the management of network failure to the processing and the analysis of warning information.When system breaks down, warning system can be real-time will alarm the reason that produces and send to network management system, and network management system can be analyzed and gets rid of the fault that is taken place according to producing alarm cause and equipment.
For the solution of prior art, all exist different shortcomings:
1) performance statistics function.Performance statistics is a kind of long-time, or perhaps a kind of statistical function of periodic duty, statistics RRC connects and to be created as power or how many mortalitys is in a period of time, this statistics itself is just very coarse, and this function is the statistical history data, can not connect the reason that breaks down to RRC and carry out anomaly analysis.If improve the granularity of performance statistics, increase statistics to RRC connection failure reason, will certainly cause the appearance of mass data, influential to regular traffic.
2) the whole network signaling test method.The whole network tracking is a kind of real-time tracking, need all to follow the tracks of at all interfaces by special third party's instrument, 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 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.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.What in general alarm was paid close attention to all is equipment fault, fewer to the concern of user's fault.When breaking down owing to wireless reason causes switching, in alarm, be to embody such as the user.So alarm can not reflect or solve the problem of switching appearance basically.
Summary of the invention
The invention provides among a kind of WCDMA RRC and connect fault information reporting method, have the fault information reporting complexity in order to solve in the prior art, can not be in time, the problem of accurately locating.
The inventive method comprises:
Radio Resource control (RRC) connects fault information reporting method in a kind of broadband CDMA system (WCDMA), set up a RRC and connect the fault parameter information set, described RRC connects fault parameter information and concentrates, RRC connection fault is set reports parameter item, when the RRC connection is set up, may further comprise the steps:
A, the fault-signal that monitoring RRC connects and receiving system is sent when the RRC connection failure;
B, the failure cause inquiry RRC that indicates according to described fault-signal connect the parameter item that fault message concentrates requirement to report;
C, the parameter item of concentrating requirement to report according to the RRC connection fault message that inquires obtain corresponding parameters value and Write fault reporting message from system;
D, described fault reporting message is sent to network management center.
Described RRC connects the fault parameter information set, comprises following content:
Terminal equipment message part, cell information part, RRC failure cause.
Described terminal equipment message part comprises:
Initial terminal device identification, RRC set up reason, RRC settling time.
Described initial terminal device identification comprises and selects the terminal iidentification type, and described selection terminal iidentification type comprises:
IMSI International Mobile Subscriber Identity (IMSI), Temporary Mobile Subscriber Identity (TMSI), Location Area Identification (LAI), packet TMSI (P-TMSI), Routing Area Identifier (RAI), international mobile subscriber identification code (IMEI).
Described IMSI is the numeral international mobile user identification.
Described LAI comprises:
Public Land Mobile Nerwork sign (PLMN) and Location Area Code (LAC).
Described RAI comprises: Routing Area sign indicating number (RAC).
Described IMEI is digital IMEI.
Described cell information part comprises cell ID.
Described RRC failure cause comprises RRC connection failure reason.
Described RRC connection failure reason comprises and selects the reason group, and described selection reason group comprises:
The RNC Internal failure is selected, the IUB interface error is selected, the failure of UU interface is selected, the failure of IU interface is selected, the failure of IUR interface is selected.
Described RNC Internal failure is selected, and further comprises:
Call out access failure, agreement or unmatched message failure reason, ASN.1 code error, layer 2 configuration error, ALCAP configuration error, unknown error.
Described agreement or unmatched message failure reason comprise:
Up spreading factor, descending spreading factor, home cell credit information, home cell group credit information.
Described home cell credit information comprises descending or the uplink capacity credit rating; Home cell group credit information comprises downlink or uplink ability credit rating.
Described IUB interface error is selected, and further comprises: NBAP RL sets up failure, RL and sets up failure cause, RL and set up overtime, AL CAP carrying and set up failure, unknown error.
Described AL CAP carrying is set up in the failure information, comprises that AL CAP carrying sets up failure cause.
Described UU interface failure is selected, and further comprises:
That RRC sets up is overtime, safe mode failure, overtime, the unknown error of initial direct-sending.
In the described safe mode failure information, comprise the safe mode failure cause.
Described IU interface failure is selected and the failure of IUR interface selects further to comprise unknown error.
Described RRC connects the fault parameter information set, also comprises: redirection information,
Described redirection information comprises:
Frequency information, different system information.
Described frequency information comprises preference pattern, and described preference pattern is up frequency and the descending frequency of FDD.
Described RRC connects the fault parameter information set, also comprises the metrical information part.
Described metrical information part comprises:
RACH channel measurement result, propagation delay time, the indication of target RRC state.
Described RACH channel measurement result comprises: current area measurement result, supervision collection cell measurement results.
Described current area measurement result comprises: select measured value, described selection measured value comprises CPICHEc/NO and CPICH RSCP.
Described supervision collection cell measurement results comprises main CPICH information, and described main CPICH information comprises measuring amount.
Described measuring amount comprises:
CPICH Ec/NO and CPICH RSCP.
Carry the current cell that reports parameter value according to parameter item settings at different levels in the described fault reporting message.
Also comprise in the described fault reporting message: the cell that carries the type of message sign.
Described method also comprises: described network management center receives described fault reporting message and extracting parameter value from each cell.
Beneficial effect of the present invention is as follows:
The present invention provides in the RRC fault, the report method of field data, can connect the problem that occurs in the process of setting up by RRC, and pass through the standard agreement message feedback and give network management system, network management system is analyzed the problem that occurs of calling out according to these historical records, and pass through these message cell problem analyses, and recover fault by corresponding means.
Initial stage in 3G network operation 3G network occurs through regular meeting and covers irrational situation, and is excessive such as the design of sub-district area coverage, because the user causes local resource to exhaust too much, perhaps Pei Zhi neighboring area signal is too poor or the like at the area of coverage.These reasons cause the user at these local access failures.
If above-mentioned situation at this time just can obtain the reason of RRC connection failure by the method that this patent is described, set up failure problem thereby can solve the RRC connection.
Description of drawings
Fig. 1 is a UTRAN system configuration schematic diagram in the prior art;
Fig. 2 is based upon schematic flow sheet on the dedicated channel for RRC of the present invention;
Fig. 3 is based upon schematic flow sheet on the common signal channel for RRC of the present invention;
Fig. 4 is a schematic flow sheet of the present invention.
Embodiment
Below in conjunction with the Figure of description explanation specific embodiment of the invention.
In WCDMA, RRC establishes dual mode:
1, RRC is based upon dedicated channel:
As shown in Figure 2, be that RRC connects the schematic flow sheet that is based upon dedicated channel, as seen from the figure, mainly may further comprise the steps:
1) UE sends the RRC connection and sets up request message on CCCH.Comprise initial UE ID in the message, set up reason, initial UE ability etc.
2) RNC judgement RRC connection is based upon on the DCH, distributes radio layer and transport layer resource simultaneously, is allocated successfully the back and sends RADIO LINK SETUP REQUEST to NodeB.
3) after NodeB received request message from RNC, Resources allocation began physical channel and receives, and sends corresponding corresponding message RADIO LINK SETUP RESPONSE immediately to RNC, and notice RNC Radio Link is set up and finished.
4) after RNC receives the success response of NodeB, begin to set up ALCAP transport layer part.
5) RNC sends down-going synchronous message, carries out down-going synchronous.
6) NODEB sends uplink synchronous message, carries out uplink synchronous.
7) RNC sends RRC CONNECTION SETUP to UE at CCCH.
8) UE sends RRC CONNECTION SETUP COMPLETE message at DCCH and informs that RNCRRC connects foundation and finishes.
2, RRC is based upon common signal channel:
As shown in Figure 3, be that RRC connects the schematic flow sheet that is based upon common signal channel, if RNC judgement RRC is based upon common signal channel (RACH/FACH), flow process is fairly simple, has omitted and has set up the Radio Link part.From top message flow as can be seen, after UE initiates RRC connection foundation request, a lot of processes all may go wrong, and cause UE to set up RRC in the sub-district of inserting, so how locate the problem of appearance? such as finding that as RNC Target cell is congested, so just can not send RADIOLINK SETUP REQUEST, thereby lead to the failure to NodeB, how to allow these reasons offer the network operation center, thus planning network or upgrading again?
The present invention is provided with a RRC and connects the fault parameter information set, this RRC connects the concentrated RRC connection fault that is provided with of fault parameter information and reports parameter item, this RRC connects the fault parameter information set, both can be the form of form, also can be tree structure commonly used in the network management at present.
The present invention sets up in the fault in the RRC connection, connects the fault parameter information set according to described RRC, selects relevant information.Send to the network manager after filling in, carry out dependent failure analysis and location.
As shown in Figure 4, when the RRC connection is set up, may further comprise the steps:
S1, the fault-signal that monitoring RRC connects and receiving system is sent when the RRC connection failure;
S2, the failure cause inquiry RRC that indicates according to described fault-signal connect the parameter item that fault message concentrates requirement to report;
S3, the parameter item of concentrating requirement to report according to the RRC connection fault message that inquires obtain corresponding parameters value and Write fault reporting message from system;
S4, described fault reporting message is sent to network management center.
Wherein carry the current cell that reports parameter value according to parameter item settings at different levels in the fault reporting message.In this fault reporting message, also comprise: the cell that carries the type of message sign.
Network management center receives described fault reporting message and extracting parameter value from each cell.
The invention provides RRC and connect the fault locating analysis method of setting up, when connecting, sets up when breaking down in the process RRC, RNC can send to network management center by the fault reporting message, and with dependent failure information with in the present message of the form body of cell, so that provide the attendant to locate solution.
Do not connect the output content of setting up fault in the 3GPP agreement at present, comprise that failure cause is described in detail, the present invention proposes a cover perfect scheme at RRC.After RRC set up failure, the relevant parameter that connects the output of fault parameter information set according to RRC was analyzed, and locatees the problem of appearance, instructs operator to carry out the network optimization.For convenience of description, we connect the concrete refinement of fault parameter information set with RRC, connect the fault parameter information set according to RRC and form the fault agreement tables, will describe the dependency structure of this fault agreement tables below in detail.
Explanation for some symbols in the table:
MP must exist;
OP can exist;
ENUMRATE 3G agreement predetermined data type (enumerating);
INTEGER 3G agreement predetermined data type (integer);
BIT STRING 3G agreement predetermined data type (BIT string).
Below the relation of each form, have a summary table (table 1), other several tables have been described the employed data structure of summary table, belong to the sublist of summary table, as long as the information of breaking down will be preserved according to the form of summary table, show or send.
Table 0: explanation
| Abbreviation | Implication |
| MP | This cell must be comprised in the protocol architecture cell |
| OP | This cell may be comprised in the protocol architecture cell |
| CV | When condition satisfies, this cell will be comprised in the protocol architecture cell, otherwise this cell will can not be comprised in the protocol architecture cell, comprise this cell when the CELL DCH state as CV-CELL DCH explanation UE |
The fault protocol architecture is set up in table 1:RRC connection:
| Information Element/Group name message part/information sets title | Need | ?Multi | Type?and?reference | ?Semantics ?description |
| Message Type (type of message) | MP | Message?Type | ||
| UE information elements (UE message part) | ||||
| Initial UE identity (initial UE sign) | MP | Initial UE identity sees Table 2 | ||
| RRC Establishment cause (reason is set up in Radio Resource control) | MP | RRC Establishment cause sees Table 3 | ||
| RRC Establishment Time (Radio Resource control settling time) | MP | BIT?STRING(32) | ?(DATE：HOUR：M ?INUTE：SECOND) |
| Cell information elements (cell information part) | ||||
| Cell identity (cell ID) | MP | Cell identity sees Table 4 | ||
| Measurement information elements (metrical information unit) | ||||
| Measured results on RACH (RACH channel measurement result) | OP | Measured results on RACH sees Table 5 | ||
| Propagation Delay (propagation delay time) | OP | Propagation Delay sees Table 6 | ||
| Destination RRC state indicator (indication of target RRC state) | OP | RRC state indicator sees Table 7 | ||
| Failure?information?elements | ||||
| RRC Failure Cause Radio Resource control failure cause | MP | RRC Failure Cause sees Table 8 | ||
| Redirection?information | ||||
| Redirection info redirection information | OP | Redirection info sees Table 9 |
Table 2: initial UE sign
| ?Information?Element/Group ?name | ?Need | ?Multi | Type?and?reference | Semantics description |
| CHOICE UE id type selects the terminal iidentification type | ?MP | |||
| ＞IMSI (GSM-MAP) IMSI International Mobile Subscriber Identity | IMSI (GSM-MAP) sees Table 12 | |||
| ?＞TMSI?and?LAI(GSM-MAP) | ||||
| ＞＞TMSI (GSM-MAP) Temporary Mobile Subscriber Identity | ?MP | TMSI (GSM-MAP) sees Table 13 | ||
| ＞＞LAI (GSM-MAP) lane place sign | ?MP | Location Area Identification sees Table 14 | ||
| ?＞P-TMSI?and?RAI(GSM-MAP) | ||||
| ＞＞P-TMSI (GSM-MAP) packet TMSI | ?MP | P-TMSI (GSM-MAP) sees Table 15 | ||
| ＞＞RAI (GSM-MAP) route distinctive emblem | ?MP | Routing Area Identifcation sees Table 16 | ||
| ＞IMEI international mobile subscriber identification code | IMEI sees Table 18 |
Table 3:RRC sets up reason
| Information?Element/Group name | ?Need | ?Multi | Type?and?reference | ?Semantics ?description |
| Establishment cause sets up reason | ?MP | ENUMERATED( Originating?Conversational?Call， Originating?Streaming?Call， Originating?Interactive?Call， Originating?Background?Call， Originating?Subscribed?traffic?Call， Terminating?Conversational?Call， Terminating?Streaming?Call， Terminating?Interactive?Call， Terminating?Background?Call， Emergency?Call， Inter-RAT?cell?re-selection， Inter-RAT?cell?change?order， Registration，Detach， Originating?High?Priority?Signalling， Originating?Low?Priority?Signalling， Call?re-establishment， Terminating?High?Priority Signalling， Terminating?Low?Priority?Signalling Terminating-cause?unknown) | ?Twelve?spare ?values?are ?needed. |
Table 4: cell ID
| Information?Element/Group name | Need | Multi | Type?and?reference | Semantics description |
| Cell identity cell ID | MP | BIT STRING (28) bit stream |
Table 5:RACH channel measurement result
| ?Information?Element/group ?name | Need | ?Multi | Type?and?reference | Semantics description |
| Measurement result for current cell current area measurement result | ||||
| ＞CHOICE measurement quantity selects measuring amount | MP | One?spare value?is needed. | ||
| ?＞＞CPICH?Ec/NO | INTEGER(0..49) | |||
| ?＞＞CPICH?RSCP | INTEGER(0..91) | |||
| Measurement results for monitored cells monitors the collection cell measurement results | OP | ?0?to?8 | ||
| ＞Primary CPICH info master CPICH information | MP | Primary CPICH info sees Table 19 | ||
| ?＞＞CHOICE?measurement ?quantity | OP | One?spare value?is needed. | ||
| ?＞＞＞CPICH?Ec/N0 | INTEGER(0..49) | |||
| ?＞＞＞CPICH?RSCP | INTEGER(0..91) |
Table 6: propagation delay time
| Information?Element/Group name | Need | Multi | Type?and?reference | Semantics description |
| Propagation Delay propagation delay time | INTEGER(0..255) | Unit：chip Range：0..765 chips Step：3chips |
The indication of table 7:RRC state
| Information?Element/Group name | Need | Multi | Type?and?reference | Semantics deseription |
| The indication of RRC State indicator RRC state | MP | ENUMERATED(CELL_DCH， CELL_FACH，CELL_PCH， URA_PCH) |
Table 8:RRC failure cause
| Information?Element/Group name | Need | Multi | Type?and?reference | ?Semantics ?description |
| CHOICE Cause Group selects the reason group | MP | |||
| ＞RNC Inner Failure Choice RNC Internal failure is selected | OP | |||
| ＞＞Call Admission Failure calls out the access failure | OP | Call Admission Failure sees Table 26 | ||
| ＞＞Protocol or Unmatched Message Error Cause agreement or unmatched message failure reason | OP | Protocol or Unmatched Message Error Cause sees Table 21 | ||
| ＞＞Asnl Encode Error ASN.1 code error | OP | ENUMERATED(Asn1?Encode Error， Asn1?Decode?Error， Asn1?Decode?Semantic?Error). | ||
| ＞＞L2 Configuration Error Cause layer 2 configuration error | OP | L2 Configuration Error Cause sees Table 22 | ||
| ＞＞ALCAP Configuration Error Cause ALCAP configuration error | OP | ALCAP Configuration Error Cause sees Table 23 | ||
| ＞＞Unspecified unknown error | OP | |||
| ＞IUB Interface Failure Choice IUB interface error is selected | OP | |||
| ＞＞NBAP RL Setup Failure NBAP RL sets up failure | OP | |||
| The RL Setup Failure cause RL of＞＞＞sets up failure cause | MP | Iub Interface Failure cause sees Table 25 | ||
| ＞＞RL Setup Timer Expired RL sets up overtime | OP | |||
| Failure is set up in＞＞ALCAP Bear Setup Failure ALCAP carrying | OP | |||
| Failure cause is set up in the ALCAP Bear Setup Failure Cause ALCAP of＞＞＞carrying | MP | ENUMERATED(IUUP?FAILURE， FPMDC?FAILURE，IURCFP FAILURE，RLC?FAILURE，PDCP FAILURE，MACC?FAILURE， MACD?FAILURE，UNSPECIFIED) |
| The unknown explanation of＞＞Unspecified | OP | |||
| The failure of＞UU Interface Failure Choice UU interface is selected | OP | |||
| ＞＞RRC Setup Timer Expire RRC sets up overtime | OP | |||
| The failure of＞＞security Mode Failure safe mode | OP | |||
| The Security Mode Failure Cause of＞＞＞safe mode failure cause | MP | UU Interface Failure cause sees Table 24 | ||
| ＞＞Initial DT Time Expired initial direct-sending is overtime | OP | |||
| ＞＞Unspecified unknown error | OP | |||
| The failure of＞IU Interface Failure Choice IU interface is selected | OP | |||
| ＞＞Unspecified unknown error | OP | |||
| The failure of＞IUR interface Failure Choice IUR interface is selected | OP | |||
| ＞＞Unspecified unknown error | OP |
Table 9: redirection information
| Information?Element/Group name | Need | Multi | Type?and?reference | Semantics description |
| CHOICE Redirection Information redirection information is selected | MP | |||
| ＞Frequency info frequency information | Frequency info sees Table 10 | |||
| The different system information of＞Inter-RAT info | Inter-RAT info sees Table 11 |
Table 10: frequency information
| ?Information?Element/Group ?name | Need | Multi | ?Type?and?reference | Semantics description |
| CHOICE mode preference pattern | MP | |||
| ?＞FDD | ||||
| The up frequency of＞＞UARFCN uplink (Nu) | OP | ?INTEGER(0..16383) | ||
| The descending frequency of＞＞UARFCN downlink (Nd) | MP | ?INTEGER(0..16383) |
Table 11: different system information
| Information?Element/Group name | Need | Multi | ?Type?and?reference | Semantics description |
| The different system information of Inter-RAT info | MP | ?ENUMERATED(GSM) |
Table 12: IMSI International Mobile Subscriber Identity
| Information Element/Group?name | Need | Multi | Type?and reference | ?Semantics?description |
| The IMSI IMSI International Mobile Subscriber Identity | MP | 6?to?21 | ?The?first?element?contains?the?first?IMSI ?digit，the?second?element?the?second ?IMSI?digit?and?so?on. ?Although?normally?upto?15?digits?are ?used?for?this?IE，a?bigger?length?is?used ?to?support?future?extension. | |
| ＞IMSI digit numeral international mobile user identification | MP | ?INTEGER(0..9) |
Table 13: Temporary Mobile Subscriber Identity
| Information Element/Group?name | Need | Multi | Type?and?reference | Semantics?description |
| TMSI (GSM-MAP) Temporary Mobile Subscriber Identity | MP | BIT?STRING(32) | ||
Table 14: Location Area Identification
| ?Information?Element/Group?name | Need | Multi | Type?and?reference | Semantics?description |
| PLMN identity Public Land Mobile Nerwork sign | MP | PLMN identity sees Table 15 | ||
| The LAC Location Area Code | MP | BIT?STRING(16) |
Table 15: packet TMSI
| Information?Element/Group name | Need | Multi | ?Type?and ?reference | Semantics?description |
| The P-TMSl packet TMSI | MP | ?BIT?STRING ?(32) |
Table 16: Tracking Area Identifier
| Information?Element/Group name | Need | Multi | Type?and reference | Semantics?description |
| RAC Routing Area sign indicating number | MP | Routing area code sees Table 17 |
Table 17: Routing Area sign indicating number
| Information?Element/Gronp name | Need | Multi | Type?and reference | Semantics?description |
| Routing Area Code Routing Area sign indicating number | MP | BIT STRING(8) |
Table 18: IMSI International Mobile Subscriber Identity
| Information?Element/Group name | Need | ?Multi | Type?and reference | Semantics?description |
| The IMEI IMSI International Mobile Subscriber Identity | MP | ?15 | ||
| ＞IMEI digit numeral international mobile user identification | MP | INTEGER(0. 15) |
Table 19: main CPICH information
| ?Information?Element/Group ?name | Need | Multi | Type?and reference | Semantics?description |
| Primary scrambling code master scrambler | MP | INTEGER(0.. 511) |
Table 20: credit information
| Information?Element/Group name | Need | Multi | Type?and?reference | ?Semantics?description |
| The up spreading factor of DL Spreading Factor | MP | ENUMERATED (4，8，16，32，64，128， 256，512) | ||
| The descending spreading factor of UL Spreading Factor | MP | ENUMERATED (4，8，16，32，64，128， 256，512) | ||
| Local Cell Credit Information home cell credit information | MP | |||
| Descending or the up-downgoing ability credit rating of＞DL Or Global Capacity Credit | MP | INTEGER(0..65535) | ||
| ＞UL Capacity Credit uplink capacity credit rating | OP | INTEGER(0..65535) | ||
| Local Cell Group Credit Information home cell group credit information | OP | |||
| Descending or the up-downgoing ability credit rating of＞DL Or Global Capacity Credit | MP | INTEGER(0..65535) | ||
| ＞UL Capacity Credit uplink capacity credit rating | OP | INTEGER(0..65535) |
Table 21: agreement or unmatched message error reason
| ?Information ?Element/Group?name | Need | Multi | ?Type?and?reference | Semantics Description |
| Protocol or Unmatched Message Error Cause agreement or unmatched message error reason | MP | ?Enumerated( ?RAB_CFG_TRANSP_LAYER_ADDR_LE ?N_ERROR， ?RAB_CFG_TRANS_ASSOCI_NO_TEID_ ?ERROR， ?RAB_MODIFY_VER_LIMIT_ERROR， ?RAB_ABSTRACT_SYNTAX_ERROR_R ?EJ， ?RAB_ABSTRACT_SYNTAX_ERROR_F ?AUSELY_CONSTRUCTED， ?RAB_INVALID_RAB_ID_ERROR， ?RAB_ASSIGN_HANDLE_RAB_NUM_Z ?ERO_ERROR， ?RAB_ASSIGN_HANDLE_RAB_ID_REP ?EATED_ERROR， ?RAB_TRAFFIC_CLASS_NOT_SUPP_ER ?ROR， ?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_L3 ?INFO， ?RELOC_IU_REQ_SECURITY_MODE_A ?LGOR_NOT_SUPP， ?RELOC_IU_CHANGE_SECURITY_MOD ?E_NOT_SUPP， ?COMM_IU_REQ_SECURITY_MODE_A ?LGOR_NOT_SUPP， ?COMM_IU_CHANGE_SECURITY_MOD ?E_NOT_SUPP， ?RL_CAUSE_NODEB_RSP_INVALID， ?RL_CAUSE_DRNC_RSP_INVALID， ?DRL_PARA_CHECK_FAIL， ?DRL_CHECK_DCH_MOD_FAIL， ?DRL_CHECK_DCH_ADD_FAIL， ?DRL_CHECK_DCH_DEL_FAIL， ?DRL_UL_SCRAMECODE_INVALID， ?DRL_CM_CMD_INVALID， ?DRL_DRNTI_EXIST， ?DRL_CELL_ID_INVALID， ?DRL_INVALID_CM_SETTING， ?DRL_QE_SELECTED_NUM_INVALID， ?DRL_TTI_INVALID， ?DRL_IE_CONFLICT， ?DRL_TFCS_INVALID， ?DRL_DL_SLOTFORMAT_ERROR， ?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_SUPPORT， ?DRL_HDSCH_NOT_SUPPORT， ?CU_REC_WRONG_CELL_UPDATE， ?SHO_RRC_TRANSID_UNEQUAL， ?CM_RRC_TRANSID_UNEQUAL， ?HHO_UE_RSP_MSG_INVALID， ?HHO_INVALID_TRANSACTION_ID， ?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 22: layer 2 configuration error reason
| ?Information ?Element/Group?name | Need | Multi | ?Type?and?reference | Semantics Description |
| L2 Configuration Error Cause layer 2 configuration error reason | MP | ?Enumerated( ?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_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_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 23:ALCAP configuration error reason
| ?Information ?Element/Group?name | Need | Multi | Type?and?reference | Semantics Description |
| ALCAP Configuration Error Cause ALCAP configuration error reason | MP | Enumerated( 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_TIMEOUT， IUR_AAL2_TIMEOUT， TYPE5_AAL2_TIMEOUT， AL_MODIFY_FAIL) |
Table 24:UU interface failure cause
| ?Information ?Element/Group?name | ?Need | Multi | ?Type?and?reference | ?Semantics ?Description |
| Failure cause error reason | ?MP | ?Enumerated(configuration ?unsupported，physical?channel ?failure，incompatible?simultaneous ?reconfiguration，protocol?error， ?compressed?mode?runtime?error，cell ?update?occurred，invalid ?configuration，configuration ?incomplete，unsupported ?measurement) | ?Rel-5 | |
| Protocol error information protocol error message | ?CV-Prot ?Err | |||
| ＞CHOICE diagnostics type selects determined type | ?MP | |||
| ＞＞Protocol error cause protocol error reason | ?Enumerated(ASN.1?violation?or ?encoding?error，Message?type ?non-existent?or?not?implemented， ?Message?not?compatible?with ?receiver?state，Information?element ?value?not?comprehended， ?Information?element?missing， ?Message?extension?not ?comprehended) | ?Rel-5 | ||
| The TGPSI of Deleted TGPSI deletion | ?CV- ?CompM ?odeErr | |||
| ?＞TGPSI | ?MP | ?Integer(1..MaxTGPS) | ?Rel-5 |
Table 25:Iub interface failure cause
| ?Information ?Element/Group?name | Need | Multi | Type?and?reference | Semantics Description |
| CHOICE Cause Group selects the reason group | M | |||
| ＞Radio Network Layer wireless network layer | ||||
| ＞＞Radio Network Layer Cause wireless network layer reason | M | ENUMERATED( 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?transpon?channel?established， SIB?Origination?in?Node?B?not?Supported， Requested?Tx?Diversity?Mode?not?supported， Unspecified， BCCH?scheduling?error， Measurement?Temporarily?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?temporarily?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?compatible， Requested?type?of?Bearer?Re-arrangement?not supported，Signalling?Bearer?Re-arrangement not?supported， Bearer?Re-arrangement?needed， Delayed?Activation?not?Supported， RL?Timing?Adjustment?not?supported) | ||
| ＞Transport Layer transport layer |
| ＞＞Transport Layer Cause transport layer reason | M | ENUMERATED( Transport?resource?unavailable， Unspecified， ...) | ||
| ＞Protocol agreement | ||||
| ＞＞Protocol Cause agreement reason | M | ENUMERATED( Transfer?syntax?error， Abstract?syntax?error(reject)， Abstract?syntax?error(ignore?and?notify)， Message?not?compatible?with?receiver?state， Semantic?error， Unspecified， Abstract?syntax?error(falsely?constructed message)， ...) | ||
| ＞Misc other | ||||
| The various reasons of＞＞Miscellaneous Cause | M | ENUMERATED( Control?processing?overload Hardware?failure， O&M?intervention， Not?enough?user?plane?processing?resources， Unspecified， ...) |
Table 26: call out the access failure
| Information?Element/Group name | Need | Multi | Type?and?reference | Semantics?deseription |
| Call Admission Failure calls out the access failure | ||||
| CHOICE selects | ||||
| ＞Cell Congestion small area jam | OP | |||
| ＞＞Transmitted Carrier Power Value carrier transmit power | MP | INTEGER(0..100) | ||
| ＞＞Received Total Wide Band Power Value receives total bandwidth power | MP | INTEGER(0..621) | ||
| ＞Cell DL SF not supported cell downlink spreading factor is not supported | OP | |||
| ＞＞Spreading Factor spreading factor | MP | ENUMERATED (4，8，16，32，64，128， 256，512) | ||
| ＞＞Occupied Rate of SF=256 SF occupancy=256 | MP | INTEGER(0..100) | ||
| ＞Cell Credit not supported sub-district credit rating is not supported | OP | |||
| ＞＞Credit information credit information | MP | Credit information sees Table 20 | ||
| ＞IUB Transport resource unavailable IUB transfer resource is not enough | OP | |||
| The up IUB bandwidth of＞＞UL IUB bandwidth | MP | INTEGER (0..65535) | Unit：byte | |
| The descending IUB bandwidth of＞＞DL IUB bandwidth | MP | INTEGER (0..65535) | Unit：byte |
| ＞IUR Transport resource Unavailable IUR transfer resource is not enough | OP | |||
| ＞＞UL IUR bandwidth UL IUR bandwidth | MP | INTEGER (0..65535) | Unit：byte | |
| The descending IUR bandwidth of＞＞DL IUR bandwidth | MP | INTEGER (0.65535) | Unit：byte |
The present invention in the RRC connection building process if mistake cause RRC to connect setting up procedure failure, then the form of setting according to the present invention reports form to come organizational information, can be with reference to the content of following embodiment.
Embodiment 1: as RNC in the step 2 in Fig. 2 is that RRC connects distribution radio layer resource and transport layer resource, find in the assigning process that the spreading factor that RRC need use is 128, but the minimum available spreading factor in the current area is 256, causes not having the bell idles resource and makes the RRC connection can't set up success.Therefore connect the description of setting up the fault protocol architecture according to table 1RRC, need note following information:
1) user's initial ID if directly connect in the request of foundation from RRC, can be IMSI, TMSI, P-TMSI or IMEI;
2) reason of RRC foundation comes from RRC and connects in the request of foundation, such as the caller session service;
3) RRC settling time, get the current time to get final product;
4) current area ID, and the RRC request of connect setting up reports the RSCP or the Ec/No of the sub-district of (can from Random Access Channel measurement report in the RRC connection request and cell quality measurement report);
5) propagation delay time of IUB interface is not if just fill out this time;
6) if target RRC state need be moved to CELL_DCH, it is CELL_DCH that target RRC state is set so;
7) failure cause is set, the contrast form can know, this reason should sum up in the point that RNC internal error-callings access failure-descending spreading factor inadequately-SF128.The occupancy that needs SF256 in the calculation plot simultaneously.Computational methods are that the descending spreading factor that takies is converted SF256, just are converted to 16 SF256 as SF16, and the number that takies is made as A, and the SF256 occupancy is exactly A/256 so.
8) redirection information if just do not fill in, is filled in according to the redirection information of RNC judgement if just have.
Embodiment 2: in step 3 in Fig. 2, NODEB does not return RADIO LINK SETUP RESPONSE in the time that RNC waits for, RNC can't carry out follow-up flow process, causes the failure of RRC connection building process.Therefore connect the description of setting up the fault protocol architecture according to table 1RRC, need note following information:
1) 2) 3) 4) 5) 6) with the description among the embodiment 1;
7) failure cause is set, the contrast form can know that this reason should sum up in the point that IUB interface error-RL sets up failure-RL and sets up timer expiry.
8) with the step 8) in (1).
Embodiment 3:
When the calling party moves to sub-district covering weak area, may trigger soft handover one time, so because the resource-constrained RRC that may occur of Target cell connects the foundation failure, but we are by the relevant information of these failures of output, can helping, we carry out the network optimization, so that the user can be switched flexibly.
Such as inserting difficulty, cause call failure when certain community user.Just can search for RRC this time and connect the CHR record of setting up failure.Record such as certain user is as follows:
Table 27: user record
| User ID | P-TMSI：C103ACF4 |
| MCC：460 | |
| MNC：07 | |
| LAC：2514 | |
| RAC：00 | |
| Reason is set up in the RRC connection | Originating?Conversational?Call |
| RRC settling time | 2005 07 month 14: 00: 31 on the 21st |
| Insert cell id | RNC：10，CELLID：101 |
| The RACH measurement report | Current area RSCP:-80dbm |
| Current area EcNo:-12db | |
| Other monitored cells: do not have |
| Transmission delay | Do not have |
| Failure cause is set up in the RRC connection | The RNC internal fault |
| Sub-district access failure | |
| Descending SF does not support | |
| Spreading factor: 128 | |
| Redirection information | Do not have |
Analyze this form and can obtain following information:
The signal of access point sub-district is no problem.The reason that RRC initiates is conversational service (may be AMR voice or video telephone) caller.
The descending spreading factor that RRC connects application when setting up is 128, but the application failure.
Follow-uply be not redirected.
Can know that from top output parameter it is because the down channel sign indicating number application of Target cell failure that this RRC connects the reason of setting up failure, cause the access failure and the RRC that causes connects and sets up failure, we can provide as drawing a conclusion so:
Whether Target cell is in hot zones, if, should optimize network so, such as increasing the same coverage cell of alien frequencies, in a sub-district access failure, can carry out the alien frequencies directed retry like this.
Whether the pilot power of Target cell is provided with too big, causes too many user to be linked in this sub-district.If should reduce power so, so that make the user can be evenly distributed to other neighbor cell.
The cell selecting of modifying target sub-district and reselecting parameters are so that make the user's easier gravity treatment free time in this sub-district arrive other adjacent area.
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 (31)
1. radio resource control RRC connects fault information reporting method among the broadband CDMA system WCDMA, it is characterized in that, set up a RRC and connect the fault parameter information set, described RRC connects fault parameter information and concentrates, RRC connection fault is set reports parameter item, when the RRC connection is set up, may further comprise the steps:
A, the fault-signal that monitoring RRC connects and receiving system is sent when the RRC connection failure;
B, the failure cause inquiry RRC that indicates according to described fault-signal connect the parameter item that fault message concentrates requirement to report;
C, the parameter item of concentrating requirement to report according to the RRC connection fault message that inquires obtain corresponding parameters value and Write fault reporting message from system;
D, described fault reporting message is sent to network management center.
2. the method for claim 1 is characterized in that, described RRC connects the fault parameter information set, comprises following content:
Terminal equipment message part, cell information part, RRC failure cause.
3. method as claimed in claim 2 is characterized in that, described terminal equipment message part comprises:
Initial terminal device identification, RRC set up reason, RRC settling time.
4. method as claimed in claim 3 is characterized in that, described initial terminal device identification comprises and selects the terminal iidentification type, and described selection terminal iidentification type comprises:
IMSI International Mobile Subscriber Identity IMSI, Temporary Mobile Subscriber Identity TMSI, Location Area Identification LAI, packet TMSI P-TMSI, Routing Area Identifier RAI, international mobile subscriber identification code IMEI.
5. method as claimed in claim 4 is characterized in that, described IMSI is the numeral international mobile user identification.
6. method as claimed in claim 5 is characterized in that, described LAI comprises:
Public Land Mobile Nerwork sign PLMN and Location Area Code LAC.
7. method as claimed in claim 4 is characterized in that, described RAI comprises:
Routing Area sign indicating number RAC.
8. method as claimed in claim 4 is characterized in that, described IMEI is digital IMEI.
9. method as claimed in claim 5 is characterized in that, described cell information part comprises cell ID.
10. method as claimed in claim 2 is characterized in that, described RRC failure cause comprises RRC connection failure reason.
11. method as claimed in claim 10 is characterized in that, described RRC connection failure reason comprises and selects the reason group, and described selection reason group comprises:
The RNC Internal failure is selected, the IUB interface error is selected, the failure of UU interface is selected, the failure of IU interface is selected, the failure of IUR interface is selected.
12. method as claimed in claim 11 is characterized in that, described RNC Internal failure is selected, and further comprises:
Call out access failure, agreement or unmatched message failure reason, ASN.1 code error, layer 2 configuration error, ALCAP configuration error, unknown error.
13. method as claimed in claim 12 is characterized in that, described agreement or unmatched message failure reason comprise:
Up spreading factor, descending spreading factor, home cell credit information, home cell group credit information.
14. method as claimed in claim 13 is characterized in that, described home cell credit information comprises descending or the uplink capacity credit rating; Home cell group credit information comprises downlink or uplink ability credit rating.
15. method as claimed in claim 11 is characterized in that, described IUB interface error is selected, and further comprises: NBAP RL sets up failure, RL and sets up failure cause, RL and set up overtime, AL CAP carrying and set up failure, unknown error.
16. method as claimed in claim 15 is characterized in that, described AL CAP carrying is set up in the failure information, comprises that AL CAP carrying sets up failure cause.
17. method as claimed in claim 11 is characterized in that, described UU interface failure is selected, and further comprises:
That RRC sets up is overtime, safe mode failure, overtime, the unknown error of initial direct-sending.
18. method as claimed in claim 17 is characterized in that, in the described safe mode failure information, comprises the safe mode failure cause.
19. method as claimed in claim 11 is characterized in that, described IU interface failure is selected and the failure of IUR interface selects further to comprise unknown error.
20. the method for claim 1 is characterized in that, described RRC connects the fault parameter information set, also comprises: redirection information,
21. method as claimed in claim 20 is characterized in that, described redirection information comprises:
Frequency information, different system information.
22. method as claimed in claim 21 is characterized in that, described frequency information comprises preference pattern, and described preference pattern is up frequency and the descending frequency of FDD.
23. the method for claim 1 is characterized in that, described RRC connects the fault parameter information set, also comprises the metrical information part.
24. method as claimed in claim 23 is characterized in that, described metrical information part comprises:
RACH channel measurement result, propagation delay time, the indication of target RRC state.
25. method as claimed in claim 24 is characterized in that, described RACH channel measurement result comprises: current area measurement result, supervision collection cell measurement results.
26. method as claimed in claim 25 is characterized in that, described current area measurement result comprises: select measured value, described selection measured value comprises CPICH Ec/NO and CPICH RSCP.
27. method as claimed in claim 25 is characterized in that, described supervision collection cell measurement results comprises main CPICH information, and described main CPICH information comprises measuring amount.
28. method as claimed in claim 27 is characterized in that, described measuring amount comprises:
CPICH Ec/NO and CPICH RSCP.
29. the method for claim 1 is characterized in that, carries the current cell that reports parameter value according to parameter item settings at different levels in the described fault reporting message.
30. method as claimed in claim 29 is characterized in that, also comprises in the described fault reporting message: the cell that carries the type of message sign.
31. as claim 29 or 30 described methods, it is characterized in that described method also comprises: described network management center receives described fault reporting message and extracting parameter value from each cell.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100886812A CN100366120C (en) | 2005-08-01 | 2005-08-01 | Wireless resource control connection fault information reporting method in wicle-band CDMA system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100886812A CN100366120C (en) | 2005-08-01 | 2005-08-01 | Wireless resource control connection fault information reporting method in wicle-band CDMA system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1852531A CN1852531A (en) | 2006-10-25 |
| CN100366120C true CN100366120C (en) | 2008-01-30 |
Family
ID=37133994
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100886812A Active CN100366120C (en) | 2005-08-01 | 2005-08-01 | Wireless resource control connection fault information reporting method in wicle-band CDMA system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100366120C (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| RU2754777C1 (en) * | 2018-04-05 | 2021-09-07 | Телефонактиеболагет Лм Эрикссон (Пабл) | Control of radio communication link failures in wireless communication networks |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101651899B (en) | 2008-08-12 | 2012-12-05 | 中兴通讯股份有限公司 | Method for requesting reestablishment of LTE RRC connection, method for setting cause value and terminal |
| CN101815314A (en) * | 2009-02-20 | 2010-08-25 | 华为技术有限公司 | Method, device and system for finding out radio network problems |
| CN103607733B (en) * | 2013-11-22 | 2017-06-06 | 大唐移动通信设备有限公司 | A kind of method, apparatus and system for detecting wireless access procedure failure reason |
| CN105101272A (en) * | 2014-05-13 | 2015-11-25 | 中兴通讯股份有限公司 | Wireless communication device online fault detection method and apparatus, and wireless communication device thereof |
| CN107370635A (en) * | 2016-05-12 | 2017-11-21 | 中国移动通信有限公司研究院 | Unexpected message report method, unexpected message method of reseptance, relevant device and system |
| CN113079587B (en) * | 2020-01-06 | 2023-05-19 | 维沃移动通信有限公司 | Failure information transmission method and communication equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1377096A1 (en) * | 2002-06-21 | 2004-01-02 | ASUSTeK Computer Inc. | Method for determining RLC entity re-establishment during SRNS relocation |
| WO2004088879A1 (en) * | 2003-04-01 | 2004-10-14 | Lg Electronics Inc. | Error processing apparatus and method for wireless communication system |
| WO2004114552A1 (en) * | 2003-06-20 | 2004-12-29 | Fujitsu Limited | Wcdma mobile communication system |
| CN1578490A (en) * | 2003-06-26 | 2005-02-09 | 北京三星通信技术研究有限公司 | Measurement method for switching inter RNC control frquency and intersystem |
-
2005
- 2005-08-01 CN CNB2005100886812A patent/CN100366120C/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1377096A1 (en) * | 2002-06-21 | 2004-01-02 | ASUSTeK Computer Inc. | Method for determining RLC entity re-establishment during SRNS relocation |
| WO2004088879A1 (en) * | 2003-04-01 | 2004-10-14 | Lg Electronics Inc. | Error processing apparatus and method for wireless communication system |
| WO2004114552A1 (en) * | 2003-06-20 | 2004-12-29 | Fujitsu Limited | Wcdma mobile communication system |
| CN1578490A (en) * | 2003-06-26 | 2005-02-09 | 北京三星通信技术研究有限公司 | Measurement method for switching inter RNC control frquency and intersystem |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| RU2754777C1 (en) * | 2018-04-05 | 2021-09-07 | Телефонактиеболагет Лм Эрикссон (Пабл) | Control of radio communication link failures in wireless communication networks |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1852531A (en) | 2006-10-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11272475B2 (en) | Wireless communication system and method for establishing a connection between user equipment and a mobility management entity thereof | |
| US7184710B2 (en) | Transmission of filtering/filtered information over the lur interface | |
| EP1360861B1 (en) | Handover in a shared radio access network environment using subscriber-dependent neighbour cell lists | |
| EP2027740B1 (en) | Method for setting up a connection in a mobile telecommunications network | |
| RU2407237C2 (en) | Method for decentralisation of events count in abnormal withdrawal of call based on each cellular cell in digital cellular communication networks | |
| US20040092259A1 (en) | Method for establishing a list of neighbouring cells in a mobile radiocommunication system | |
| CN100366120C (en) | Wireless resource control connection fault information reporting method in wicle-band CDMA system | |
| CN103200603A (en) | Drive test minimization (MDT) continuous measuring and reporting performing method under multiple public land mobile networks (PLMNs) | |
| CN100403837C (en) | Method for reporting fault of updating cell in WCDMA system | |
| US9888403B2 (en) | Method and apparatus for supporting minimization of drive tests for radio access network sharing in wireless communication system | |
| CN102938905A (en) | Method and device for minimizing road tests | |
| CN100531254C (en) | Dff-line fault information report method, device and off-line fault reason positioning system | |
| CN103037412B (en) | One kind minimizes drive test relevant information sending method and wireless access network | |
| US20150126130A1 (en) | Method for implementing mdt continuity | |
| CN103260176A (en) | Minimized drive test method, network element and system | |
| CN100396135C (en) | Method for reporting RAB assignation fault in wide-band CDMA system | |
| CN105376765A (en) | Method and device for reducing CSFB delay | |
| WO2008110124A1 (en) | Mobility processing method, device and system | |
| CN1859682B (en) | Irregular frequency hard switching fault analyzing method | |
| CN103428751A (en) | Minimum drive test service quality continuity measuring method and device | |
| CN108156622A (en) | The monitoring system and method for LTE network cell signal quality and link load | |
| CN100452910C (en) | Soft switching fault analyzing method | |
| CN103037426B (en) | The method and wireless access network of selection terminal during a kind of minimum drive test | |
| EP3335519A1 (en) | Method and system for enabling inter-plmn proximity services | |
| CN100550827C (en) | A kind of enhanced wireless network controller method of routing |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20211223 Address after: 450046 Floor 9, building 1, Zhengshang Boya Plaza, Longzihu wisdom Island, Zhengdong New Area, Zhengzhou City, Henan Province Patentee after: xFusion Digital Technologies Co., Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |