CN1852530A - Method for reporting RAB assignation fault in wide-band CDMA system - Google Patents

Abstract

The invention discloses a method for reporting RAB assignment faults in a WCDMA system, which is characterized in that a RAB assignment fault parameter information set is established, the RAB assignment fault parameter information is set, and the RAB assignment fault parameter information set is set for reporting The parameter item, when the RAB assignment is established, includes the following steps: A. Monitor the RAB assignment connection and receive the fault signal sent by the system when the RRC connection fails; B. Query the RAB assignment fault according to the fault cause indicated by the fault signal The parameter items required to be reported in the information set; C. Obtain corresponding parameter values from the system according to the parameter items and write them into a fault report message; D. Send the fault report message to the network management center. The invention can obtain the specific reason of RAB assignment failure, thereby solving the problem of RAB assignment failure.

Description

The report method of RAB assignation fault in a kind of broadband CDMA system

Technical field

The present invention relates to mobile communication system, disclose the report method of RAB assignation fault in a kind of WCDMA (Wideband CodeDivision Multiple Access, Wideband Code Division Multiple Access (WCDMA)) system especially.

Background technology

The WCDMA system is an open system, this system mainly comprises CN (Core Network, core net), UTRAN (UMTS Trrestrial Radio Access Network, UMTS Terrestrial radio access network), and UE (User Equipment, user terminal) three parts (other as part such as webmaster and alarm subsystem not at the row of this patent description).(the Radio Network Controller of RNC wherein, radio network controller) belongs to the UTRAN part, RNC and other network element exist standard interface, such as and CN between the IU interface, and between the NodeB IUB interface, and be the IUR interface between other RNC, 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 RAB (Radio AccessBearer, RAB) assignation fault problem can become an emphasis in the process of network operation.

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 statistics cell update success/frequency of failure in a specific measuring period.And this statistical value fed back to network management system, and comprehensively analyze by network management system, instruct by analysis result and deal with problems and the network optimization.

The performance statistics function.Performance statistics is a kind of long-time, or perhaps a kind of statistical function of periodic duty, how many statistics RAB assignment success rate or mortalitys be in a period of time, this statistics itself is just very coarse, and this function is the statistical history data, can not carry out anomaly analysis to the reason that the RAB assignment is broken down.If improve the granularity of performance statistics, increase statistics to RAB Assignment Failure reason, will certainly cause the appearance of mass data, influential to regular traffic.

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) 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 subproblem simultaneously.

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, whether this tracking is not distinguished is cell update, the cell update success or not, can produce lot of data like this, present 2G total network signalling tracing has just been followed the tracks of the message between net, and 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, when especially needing to 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

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.

What in general alarm was paid close attention to all is equipment fault, fewer to the concern of user's fault.When causing the RAB assignation fault owing to wireless reason, in alarm, be to embody such as the user.So alarm can not reflect or solve the problem that the RAB assignment occurs basically.

Summary of the invention

The invention provides the report method of RAB assignation fault in a kind of WCDMA system, in order to solve in the prior art when Access Network is failed in execution RAB assignment process, network management center is not because of obtaining the problem that detailed field data can't be analyzed and locate.

The inventive method comprises:

The report method of RAB assignation fault is characterized in that in a kind of WCDMA system, sets up a RAB assignation fault parameter information collection, described RAB assignation fault parameter information is concentrated, RAB assignation fault parameter information collection is set reports parameter item, when the RAB assignment is set up, may further comprise the steps:

A, the fault-signal that monitoring RAB assignment connects and receiving system is sent when RAB assignment connection failure;

The parameter item that B, the concentrated requirement of failure cause inquiry RAB assignation fault information that indicates according to described fault-signal report;

C, from system, obtain corresponding parameters value and Write fault reporting message according to described parameter item;

D, described fault reporting message is sent to network management center.

Described RAB assignation fault information set is divided into RAB cell information part, optimum subdistrict message part, sub-district branch road message part, RRC state information part, the failure information part of user profile part, RAB message part, failure

With the frequency point information part.

Described user profile partly comprises international mobile subscriber identity.

Described RAB message part has comprised and has been about to set up or modification RAB list information; This RAB list information comprises: the time that type of service, core network information, descending maximum rate, maximum uplink rate, descending guarantee speed, up assurance speed, RAB sign and RAB set up or revise.

Described core network information comprises the core net sign.

The RAB cell information of described failure partly comprises the RAB tabulation of failure, and this tabulation comprises RAB sign, CN domain identifier and RAB Time To Failure.

Described optimum subdistrict information comprises cell ID and current area measurement result.

Described sub-district branch road message part comprises sub-district branch road information, and this sub-district branch road information comprises cell ID and current area measurement result.

Described current area measurement result comprises parameter: CPICH Ec/No and CPICH receive gross power.

Described RRC state information partly comprises source RRC state indication and the indication of target RRC state, and indication of this source RRC state and the indication of target RRC state comprise RRC state indication parameter.

Described failure information partly comprises the RAB failure cause.

Described RAB failure cause comprises RNC Internal failure, IUB interface error, the failure of UU interface, the failure of IU interface and the failure of IUR interface.

Described RNC Internal failure comprises the failure of calling access, UE limited ability, illegal RAB parameter, exceeds RNC specification, agreement or unmatched message error reason, ASN.1 error reason, L2 configuration error reason, ALCAP configuration error reason, user's face error reason and unknown error.

Described calling access failure comprises that small area jam, cell downlink spreading factor are not supported, the sub-district credit rating is not supported, the defeated resource of IUB oral instructions is unavailable and the IUR transfer resource is unavailable.

Described small area jam comprises carrier transmit power and receives gross power.

Described cell downlink spreading factor does not support to comprise spreading factor and SF256 occupancy.

Described sub-district credit rating does not support to comprise credit information, and this credit information comprises: descending spreading factor, up spreading factor, home cell credit information and home cell group credit information.

Described local credit information and home cell group credit information include descending or up-downgoing ability credit rating, and the uplink capacity credit rating.

Unavailable up IUB bandwidth and the descending IUB bandwidth of comprising of resource failed in described IUB oral instructions; Perhaps, unavailable up IUR bandwidth and the descending IUR band of comprising of described IUR transfer resource.

Described UE limited ability comprises that UE physical channel ability is not supported, UE transmission channel ability is not supported and UE RLC ability is not supported.

Described UE physical channel ability is not supported to comprise: down physical channel ability and uplink physical channel ability, this down physical channel ability comprises every 10ms reception bit number of physical channel maximum at interval, and this uplink physical channel ability comprises every 10ms transmission bit number of physical channel maximum at interval.

Described UE transmission channel ability is not supported to comprise: descending transmission channel ability information part and uplink transport channel ability part;

Described descending transmission channel ability information partly comprises: the BIT number of the maximum TURBO coding that can receive in the BIT number of the maximum convolutional encoding that can receive in the maximum BIT number that can receive in the arbitrary time span, the arbitrary time span, the arbitrary time span, the transmission channel number of synchronization maximum, maximum transmission block number, maximum tfc number and the maximum transport format number that receives;

Described uplink transport channel ability partly comprises: the BIT number of the maximum TURBO coding that can send in the BIT number of the maximum convolutional encoding that can send in the maximum BIT number that can send in the arbitrary time span, the arbitrary time span, the arbitrary time span, the transmission channel number of synchronization maximum, maximum transmission block number, maximum tfc number and the maximum transport format number that sends.

Described UE RLC ability is not supported to comprise: total cache size of RLC affirmation mode, maximum RLC affirmation mode window size and maximum RLC affirmation mode number of entities.

The described RNC of exceeding specification information comprises and exceeds RNC specification cause parameter; Perhaps, described agreement or unmatched message error reason comprise: agreement or unmatched message error cause parameter; Perhaps, described L2 configuration error reason comprises L2 configuration error cause parameter; Perhaps, described ALCAP configuration error reason comprises: ALCAP configuration error cause parameter; Perhaps, described user's face error reason comprises: user's face error reason parameter.

Described IUB interface error comprises that NBAP RL foundation failure, NBAP RL reconfiguration failure, AAL2 foundation are failed, RL recovery indication is overtime, the AAL2 modification is failed and unknown error.

Described NBAP RL sets up failure and comprises: RL sets up failure cause, and RL sets up the timer expiry parameter; Perhaps, described NBAP RL reconfiguration failure comprises: RL reconfiguration failure reason, and RL reshuffles timer expiry; Perhaps, described AAL2 sets up to fail and comprises that AAL2 sets up the failure cause parameter; Perhaps, described AAL2 revises the failure cause parameter.

Described RL foundation failure is former to be comprised with RL reconfiguration failure reason: wireless network layer reason, transport layer reason, agreement reason and other reasons.

The failure of described UU interface comprises that RB sets up failure and mistake not.

Described RB sets up failure and comprises that RB sets up failure cause and RB sets up timer expiry; Described RB sets up failure cause and comprises: the TGPSI of failure cause, protocol error message, protocol error reason, deletion and TGPSI parameter.

Described IU interface failure comprises: IU bust this, AAL2 set up and fail, AAL2 revises failure, IUUP sets up failure and unknown error.

Described IU bust this comprises IU transmission network failure cause parameter; Described AAL2 sets up failure and comprises that AAL2 revises the failure parameter; Described IUUP sets up failure and comprises that IUUP sets up failure cause.

Described IUUP sets up failure cause and comprises user's face error reason parameter.

Described IUR interface failure comprises the unknown error parameter.

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:

Initial stage in the 3G network operation 3G network occurs through regular meeting and covers irrational situation, and is too much such as the planning of sub-district area coverage, causes local resource to exhaust when the user is too many.Perhaps terminal capability is limited, and the PDP speed signatory such as UE causes RAB can't set up success or the like with the ability that exceeds UE.These reasons all can cause Access Network to be failed when carrying out the RAB assignment process.

If above-mentioned situation can obtain the concrete reason of RAB Assignment Failure by the method that this patent is described, thereby can solve the problem of RAB Assignment Failure.

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 RAB of the present invention;

Fig. 3 reports the schematic flow sheet schematic flow sheet of fault message for the present invention.

Embodiment

The present invention provides a kind of call history (CHR), this record can be followed the tracks of RAB and set up the problem that occurs in the process, 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.

The RAB assignment process has comprised RAB foundation, modification and release flow process, below just to set up (DCH to DCH-is synchronous) with RAB be example description protocol process, as shown in Figure 1, comprise the steps:

1, CN sends RAB ASSIGNMENT REQUEST message to SRNC, comprises RAB parameter, user's surface model and transport layer relevant information in the message, and SRNC is user radio layer and transport layer resource by these information;

2, SRNC utilizes the ALCAP agreement to initiate the foundation of IU bearer context for data transmission.Comprised binding ID in the foundation request that ALCAP sends, this binding ID is used for binding IU bearer context for data transmission and RAB (not needing if this step RAB is the PS territory);

If 3 have DRNC, SRNC sends RADIO LINK RECONFIGURATIONPREPARE to DRNC, requires to increase the DCH of carrying RAB;

If 4 have DRNC, DRNC sends RADIO LINKRECONFIGURATION PREPARE to NODEB, requires NODEB to increase the DCH of carrying RAB;

5, SRNC sends RADIO LINK RECONFIGURATION PREPARE to NODEB, requires NODEB to increase the DCH of carrying RAB;

6, after the NODEB resource allocation is finished, return RADIO LINKRECONFIGURATION READY to DRNC;

7, DRNC sends RADIO LINK RECONFIGURATION READY notice SRNC to SRNC and has been ready to RL and reshuffles;

8, after the NODEB resource allocation is finished, return RADIO LINKRECONFIGURATION READY to SRNC;

9, SRNC utilizes the ALCAP agreement to initiate the foundation of IUB/IUR bearer context for data transmission.Comprised binding ID in the foundation request that ALCAP sends, this binding ID is used for binding IUB/IUR bearer context for data transmission and RAB;

10, SRNC utilizes the ALCAP agreement to initiate the foundation of IUB bearer context for data transmission.Comprised binding ID in the foundation request that ALCAP sends, this binding ID is used for binding IUB bearer context for data transmission and RAB;

If 11 have DRNC, SRNC sends down-going synchronous to NODEB, carries out the FP synchronizing process of IUB and IUR mouth;

12, SRNC sends down-going synchronous to NODEB, carries out the FP synchronizing process of IUB mouth;

13, it is synchronous that the NODEB of DRNC and SRNC carry out up FP;

14, it is synchronous that the NODEB of SRNC and SRNC carry out up FP;

If 15 have DRNC, SRNC sends RADIO LINKRECONFIGURATION COMMIT by the IUR mouth to SRNC;

If 16 have DRNC, DRNC sends RADIO LINKRECONFIGURATION COMMIT to NODEB;

17, SRNC sends RADIO LINK RECONFIGURATION COMMIT to NODEB.

18, SRNC sends RADIO BEARER SETUP message to UE;

19, UE returns RADIO BEARER SETUP COMPETE message to SRNC;

20, RNC returns RAB ASSIGNMENT RESPONSE message to CN.

From top message flow as can be seen, RAB sets up and has passed through many steps, mistake all might occur and cause RAB to set up failure in each step.

At top problem, the output content that does not have the RAB assignation fault at present in the 3GPP agreement, comprise that failure cause is described in detail, the invention provides the historical record CHR of RAB assignation fault positioning analysis, when breaking down in the RAB assignment process, RNC can send to network management center by message, and with relevant information with in the present message of the form body of agreement cell, so that provide the attendant to locate solution.

At first, the present invention is directed to this problem one RAB assignation fault parameter information collection is set, this RAB assignation fault parameter information is concentrated and the RAB assignation fault to be set to be reported parameter item, this RAB assignation fault parameter information collection, both the form of form can be, also tree structure commonly used in the network management at present can be.Behind the RAB Assignment Failure, send relevant parameter according to this RAB assignation fault parameter information collection to network management center, locate the problem of appearance, instruct operator to carry out the network optimization simultaneously.

The present invention according to described RAB assignation fault parameter information collection, selects relevant information in the RAB assignation fault.Send to the network manager after filling in, carry out dependent failure analysis and location.

As shown in Figure 4, when the RAB assignment, may further comprise the steps:

S1, the fault-signal that monitoring RAB assignment connects and receiving system is sent when RAB assignment connection failure;

The parameter item that S2, the concentrated requirement of failure cause inquiry RAB assignation fault information that indicates according to described fault-signal report;

S3, from system, obtain corresponding parameters value and Write fault reporting message according to described parameter item;

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 RAB assignation fault method for positioning analyzing, when connecting, sets up when breaking down in the process RRC, system 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.

For convenience of description, we form RAB assignation fault agreement tables with the concrete refinement of RAB assignation fault parameter information collection according to RAB assignation fault parameter information collection, will describe the dependency structure of this fault agreement tables below in detail.

Protocol architecture sees Table 1～table 21, and wherein whether each cell is that call parameter when carrying out the analysis of causes is divided into essential, optional, condition three classes according to its parameter of carrying, and concrete implication sees Table 0, and is defined in the Need row in each form.

Table 0

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

Wherein, the structure of table 1～table 21 parameter type is as required divided step by step, and table 1 is total class table, and divide step by step and set up corresponding sublist, according to the structure of table, be that index is easy-to-look-up with the type, reduce error rate.

Table 1 RAB assignation fault protocol architecture

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					Type of message (Message Type)	MP		Type of message (Message Type)
User profile part (UE information elements)
					International mobile subscriber identity (IMSI)	MP		International mobile subscriber identity (IMSI) reference table 12
RAB message part (RAB Information elements)
					And soon set up or revised RAB (RABs Setup Or Modified List)	MP		RAB list information (RAB List information) reference table 2
The RAB message part (Fail RABs Information elements) of failure
					The RAB tabulation (Failed RAB List) of failure	MP		RAB tabulation letter (Failed RAB List Information) reference table 11 of failure
Optimum subdistrict message part (Best Cell information elements)
					Optimum subdistrict information (Best Cell Information)	MP		Cell information (Cell Information) reference table 3
Sub-district branch road message part (Cell Leg Information elements)
					Sub-district branch road information (Cell Leg Information)	MP	0～6	Cell information (Cell Information) reference table 3
RRC state information part (RRC State information elements)
					Source RRC state indication (Source RRC State Indicator)	MP		RRC state indication (RRC State Indicator) reference table 15
Target RRC state indication (Destination RRC State Indicator)	MP		RRC state indication (RRC State Indicator) reference table 15
					Failure information part (Failure information elements)
RAB failure cause (RAB Failure Cause)	MP		RAB failure cause (RAB Failure Cause) reference table 4

Frequency point information (Frequency information)
					Frequency point information (Frequency info)	OP		Frequency point information (Frequency info) reference table 16

Table 2, RAB list information (RAB List Information)

Maximum uplink rate (UL Maximum Bit Rate)	MP		INTEGER(1..16,000,000)
					Descending guarantee speed (DL Guaranteed Bit Rate)	OP		INTEGER(0..16,000,000)
Up assurance speed (UL Guaranteed Bit Rate)	OP		INTEGER(0..16,000,000)
					RAB identifies (RAB ID)	MP		BIT STRING(8)
RAB time (RAB Setup Or Modify Time) of setting up or revising	MP		BIT STRING(32)	(DATE:HOUR:MINUTE :SECOND)

Table 3, cell information (Cell Information)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					Sub-district ID (Cell identity)	MP		BIT STRING(28)
Current area measurement result (Measurement result for current cell)
					>CPICH Ec/N0 CPICH Ec/No	OP		INTEGER(0.. 49)	The EC/NO that obtains in the 1s before the call drop
Reception gross power (CPICH RSCP CPICH)	OP		INTEGER(0.. 91)

Table 4, RAB failure cause (RAB Failure Cause)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					CHOICE Cause Group	MP
RNC Internal failure (RNC Inner Failure Choice)	OP
					Calling access failure (Call Admission Failure)	OP		Call Admission Failure reference table 17
Limited ability (UE capability limited UE)	OP

The physical channel ability do not support (UE physical channel capablity not supported UE)	OP		UE Physical channel capability reference table 6
					The transmission channel ability do not support (UE Transport channel capability not supported UE)	OP		UE transport channel capability reference table 8
UE RLC ability do not support (UE RLC capability limited)	OP		RLC capability reference table 7
					Illegal RAB parameter (Invalid RAB parameter)	OP
Exceed RNC specification (Out of RNC specification)	OP		Out of RNC specification cause reference table 9
					Agreement or unmatched message error reason (Protocol or Unmatched Message Error Cause)	OP		Protocol or Unmatched Message Error Cause reference table 18
ASN.1 error reason (ASN1 Error Cause)	OP		ENUMERATED(Transfer Syntax Error，Abstract Syntax Error， Logical Error， ...).
					L2 configuration error reason (L2 Configuration Error Cause)	OP		L2 Configuration Error Cause reference table 19
ALCAP configuration error reason (ALCAP Configuration Error Cause)	OP		ALCAP Configuration Error Cause reference table 20
					User's face error reason (User Plane Error Cause)	OP		User Plane Error Cause reference table 21
Unknown error (Unspecified)	OP
					IUB interface error (IUB Interface Failure Choice)	OP
NBAP RL foundation failure (NBAP RL Setup Failure)	OP
					RL sets up failure cause (RL Setup Failure cause)	OP		RL Setup Failure cause reference table 14
RL sets up timer expiry (RL Setup Timer Expire)	OP
					NBAP RL reconfiguration failure (NBAP RL Reconfiguration Failure)	OP
RL reconfiguration failure reason (RL Reconfiguration Failure Cause)	MP		RL Setup Failure cause reference table 14
					RL reshuffles timer expiry (RL Reconfiguration Timer Expire)	OP
AAL2 foundation failure (AAL2 Setup Failure)	OP
					AAL2 sets up failure cause (AAL2 Setup Failure Cause)	MP		ENUMERATED(Inner Establish Failure，QAAL2 No AAL2 Route，QAAL2 No Resource， QAAL2 AN1 Unreachable， QAAL2 Temporary Error，Peer ECF Failure for Normal Cause，Peer ECF Failure for Other Cause， ...)
RL recovery indication overtime (RL Restore Indication timeout)	OP
					AAL2 revises failure	OP

(AAL2 Modify Failure)
					AAL2 revises failure cause (AAL2 Modify Failure Cause)	MP		ENUMERATED(QAAL2 Modify Collision， QAAL2 Modify Not Support， QAAL2 Modify No Resource， QAAL2 Modify Temporary Error， QAAL2 Modify Peer Failure， ...)
Unknown error (Unspecified)	OP
					UU interface failure (UU Interface Failure Choice)	OP
RB foundation failure (RB Setup Failure)	OP
					RB sets up failure cause (RB Setup Failure cause)	OP		UU Interface Failure cause reference table 10
RB sets up timer expiry (RB Setup Timer Expire)	OP
					Unknown error (Unspecified)	OP
IU interface failure (IU Interface Failure)	OP
					IU bust this (IU Transport Failure)	OP
IU transmission network failure cause (IU Transport NW Failure Cause)	MP		ENUMERATED(signalling transport resource failure， iu-transport-connection-failed-to-esta blish，...)
					AAL2 foundation failure (AAL2 Setup Failure)	OP
AAL2 sets up failure cause (AAL2 Setup Failure Cause)	MP
					AAL2 modification failure (AAL2 Modify Failure)	OP
AAL2 modification failure (AAL2 Modify Failure Cause)	MP		ENUMERATED(QAAL2 Modify Collision， QAAL2 Modify Not Support， QAAL2 Modify No Resource， QAAL2 Modify Temporary Error， QAAL2 Modify Peer Failure， ...)
					IUUP foundation failure (IUUP Setup Failure)	OP
IUUP sets up failure cause (IUUP Setup Failure Cause)	MP		User Plane Error Cause reference table 21
					Unknown error (Unspecified)	OP
IUR interface failure (IUR Interface Failure Choice)	OP
					Unknown error (Unspecified)	OP

Table 5, CN domain identity core network domain sign

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					Core network domain sign (CN domain identity)	MP		ENUMERATED(CS domain，PS domain)

Table 6, UE physical channel ability (UE Physical channel capability)

Information Element/Group name	Need	Multi	Type and Reference	Semantics deseription
					Down physical channel ability (FDD downlink physical channel capability)
The every 10ms reception BIT number (Maximum number of physical channel bits received in any 10ms interval) of physical channel maximum at interval	MP		INTEGER (1200，2400，3600，4800，7200， 9600，14400，19200，28800， 38400，48000，57600，67200， 76800)
					Uplink physical channel ability (FDD uplink physical channel capability)
The every 10ms transmission BIT number (Maximum number of DPDCH bits transmitted per 10ms) of physical channel maximum at interval	MP		INTEGER(600，1200，2400， 4800.9600，19200.28800，38400， 48000，57600)

Table 7, UE RLC ability (UE RLC capability)

Information Element/Group name	Need	Multi	Type and Reference	Semantics description
					Total buffer memory size of RLC affirmation mode (Total RLC AM buffer size)	MP		INTEGER	10，50，100，150，50 0，1000)
Maximum RLC affirmation mode window size (Maximum RLC AM Window Size)	MP		INTEGER(2047，4 095)
					Maximum RLC affirmation mode number of entities (Maximum number of AM entities)	MP		INTEGER (4，5，6，8，16，30)

Table 8, UE transmission channel ability (UE Transport channel capability)

Information Element/Group name	Need	Multi	Type and Reference	Semantics description
					Descending transmission channel ability information part (Downlink transport channel capability information elements)
The maximum BIT number (Maximum number of bits being received at an arbitrary time instant) that can receive in the arbitrary time span	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)

The BIT number (Maximum number of convolutionally coded bits being received at an arbitrary time instant) of the maximum convolutional encoding that can receive in the arbitrary time span	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
					The BIT number (Maximum number of turbo coded bits being received at an arbitrary time instant) of the maximum TURBO coding that can receive in the arbitrary time span	OP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
The transmission channel number of synchronization maximum (Maximum number of simultaneous transport channels)	MP		INTEGER(4，8，16，32)
					The maximum transmission block number (Maximum number of received transport blocks) that receives	MP		INTEGER(4，8，16，32，48，64， 96，128，256，512)
Maximum tfc number (Maximum number of TFC)	MP		INTEGER(16，32，48，64，96， 128，256，512，1024)
					Maximum transport format number (Maximum number of TF)	MP		INTEGER(32，64，128，256， 512，1024)
Uplink transport channel ability information part (Uplink transport channel capability information elements)
					The maximum BIT number (Maximum number of bits being transmitted at an arbitrary time instant) that can send in the arbitrary time span	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
The BIT number (Maximum number of convolutionally coded bits being transmitted at an arbitrary time instant) of the maximum convolutional encoding that can send in the arbitrary time span	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
					The BIT number (Maximum number of turbo coded bits being transmitted at an arbitrary time instant) of the maximum TURBO coding that can send in the arbitrary time span	OP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
The transmission channel number of synchronization maximum (Maximum number of simultaneous transport channels)	MP		INTEGER(4，8，16，32)
					The maximum transmission block number Maximum number of transmitted transport blocks that sends)	MP		INTEGER(4，8，16，32，48，64， 96，128，256，512)
Maximum tfc number (Maximum number of TFC)	MP		INTEGER(16，32，48，64，96， 128，256，512，1024)
					Maximum transport format number (Maximum number of TF)	MP		INTEGER(32，64，128，256， 512，1024)

Table 9, exceed RNC specification reason (Out of RNC specification cause)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					Exceed RNC specification reason (Out of RNC specification cause)	MP		INTEGER(TFC number more than 256 is not supported， DPCH multi-codes in downlink is not supported，Maximum number of RAB is not supported， RAB type is not supported)

Table 10, UU interface failure cause (UU Interface Failure cause)

Information Element/Group name	Need	Multi	Type and reference	Semantics Description
					Failure cause (Failure cause)	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 message (Protocol error information)	CV-Prot Err
					>CHOICE diagnostics type	MP
Protocol error reason (Protocol error cause)			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 (Deleted TGPSI) of deletion	CV- CompM odeErr
>TGPSI	MP		Integer(1..MaxTGPS)	Rel-5

Table 11, failure RAB list information (Failed RAB List Information)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					The RAB tabulation (Failed RAB List) of failure		1 to 255
>RAB ID	MP		BIT STRING(8)
					CN domain identifier (CN Domain Identity)	MP		CN Domain Identity reference table 5
RAB Time To Failure (RAB Failure Time)	MP		BIT STRING(32)	(DATE:HOUR:MI NUTE:SECOND)

Table 12, IMSI (GSM-MAP)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					International mobile subscriber identity (IMSI)	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	MP		INTEGER(0.. 9)

Table 13, credit information (Credit information)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					Descending spreading factor (DL Spreading Factor)	MP		ENUMERATED (4，8，16，32，64，128， 256，512)
Up spreading factor (UL Spreading Factor)	MP		ENUMERATED (4，8，16，32，64，128， 256，512)
					Home cell credit information (Local Cell Credit Information)	MP
Descending or up-downgoing ability credit rating (DL Or Global Capacity Credit)	MP		INTEGER(0..65535)
					Uplink capacity credit rating (UL Capacity Credit)	OP		INTEGER(0..65535)
Home cell group credit information (Local Cell Group Credit Information)	OP
					Descending or up-downgoing ability credit rating (DL Or Global Capacity Credit)	MP		INTEGER(0..65535)
Uplink capacity credit rating (UL Capacity Credit)	OP		INTEGER(0..65535)

Table 14, RL set up failure cause (RL Setup Failure cause)

Information Element/Group name	Need	Multi	Type and reference	Semantics Description
					CHOICE Cause Group	M
Wireless network layer (Radio Network Layer)
					Wireless network layer reason (Radio Network Layer Cause)	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 Unayailable， Measurement not supported for the object， Combining Resources not available， Requested configuration not supported， Synchronization failure， Priority transport channel established， SIB Origination in Node B not Supported， Requested Tx Diversity Mode not supported， Unspecified， 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 reason (Transport Layer Cause)	M		ENUMERATED( Transport resource unavailable， Unspecified， ...)
					Agreement (Protocol)
Agreement reason (Protocol Cause)	M		ENUMERATED( Transfer syntax error， Abstract syntax error(reject)， Abstract syntax error(ignoreand notify)， Message not compatible with receiver state， Semantic error， Unspecified， Abstract syntax error(falsely constructed message)， ...)
					Other (Misc)
Other reason (Miscellaneous Cause)	M		ENUMERATED( Control processing overload Hardware failure， O&M intervention， Not enough user plane processing resources， Unspecified， ...)

Table 15, RRC state indication (RRC State Indicator)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					The indication of RRC State indicator RRC state	MP		ENUMERATED(CELL_DCH， CELL_FACH，CELL_PCH， URA_PCH)

Table 16, frequency point information (Frequency info)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					CHOICE mode	MP
>FDD
					Up frequency (UARFCN uplink (Nu))	OP		INTEGER(0..1 6383)
Descending frequency (UARFCN downlink (Nd))	MP		INTEGER(0.. 16383)

Table 17, calling access failure (Call Admission Failure)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					Call out access failure (Call Admission Failure)
CHOICE
					Small area jam (Cell Congestion)	OP

Carrier transmit power (Transmitted Carrier Power Value)	MP		INTEGER(0..100)
					Accept gross power (Received Total Wide Band Power Value)	MP		INTEGER(0..621)
The cell downlink spreading factor do not support (Cell DL SF not supported)	OP
					Spreading factor (Spreading Factor)	MP		ENUMERATED (4，8，16，32，64，128， 256，512)
SF256 occupancy (Occupied Rate of SF=256)	MP		INTEGER(0..100)
					The sub-district credit rating do not support (Cell Credit not supported)	OP
Credit information (Credit information)	MP		Credit information reference table 13
					The defeated resource unavailable (IUB Transport resource unavailable) of IUB oral instructions	OP
Up IUB bandwidth (UL IUB bandwidth)	MP		INTEGER (0..65535)	Unit：byte
					Descending IUB bandwidth (DL IUB bandwidth)	MP		INTEGER (0..65535)	Unit：byte
IUR transfer resource unavailable (IUR Transport resource unavailable)	OP
					Up IUR bandwidth (UL IUR bandwidth)	MP		INTEGER (0..65535)	Unit：byte
Descending IUR bandwidth (DL IUR bandwidth)	MP		INTEGER (0..65535)	Unit：byte

Table 18, agreement or unmatched message error reason (Protocol or Unmatched Message ErrorCause)

Information Element/Group name	Need	Multi	Type and reference	Semantics Description
					Agreement or unmatched message error reason (Protocol or Unmatched Message Error Cause)	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 19, layer two configuration error reason (L2 Configuration Error Cause)

Information Element/Group name	Need	Multi	Type and reference	Semantics Description
					Layer two configuration error reason (L2 Configuration Error Cause)	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 20, ALCAP configuration error reason (ALCAP Configuration Error Cause)

Information Element/Group name	Need	Multi	Type and reference	Semantics Description
					ALCAP configuration error reason (ALCAP Configuration Error Cause)	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 21, user's face error reason (User Plane Error Cause)

Information Element/Group name	Need	Multi	Type and reference	Semantics description
					User's face error reason (User Plane Error Cause)	MP		Enumerated( IUUP_ERROR， FPMDC_ERROR， IURCFP_ERROR， MACC_ERROR， MACD_ERROR， RLC_ERROR， PDCP_ERROR， GPPU_ERROR， IUUP_ERROR， BMC_ERROR， ...)

The function of this patent hereinafter is described by some examples.

One, CHR information organization method

In the RAB assignment procedure if mistake, assignment process failure is if report form to come organizational information according to the CHR that mentions of this paper so.

1), as in step 1 shown in Figure 1, SRNC comes allocation of parameters according to the RAB information of CN assignment, find in the assigning process that the spreading factor that RAB need use is 8, but the minimum available spreading factor in the current area is 64, causes not having the bell idles resource and makes RAB can't set up success.Therefore according to the description of the assignation fault of RAB shown in the table 1 protocol architecture, need note following information:

(1), user's IMSI (set up in the flow process of SRNC before assignment and can get access to COMMON ID from CN when IU connects);

(2), the type of service in the RAB parameter in the RAB ASSIGNMENT REQUEST message, up-downgoing maximum rate, up-downgoing guarantee speed and RAB ID;

(3), CN territory sign is obtained in connection according to IU, as CS or PS;

(4), current area ID, and UE the last time report 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) if also have other sub-districts in the active set, handle similar (4);

(6), current RRC connection status, be CELL_FACH if the current CELL_FACH of being in state just is set to source RRC state; 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-SF8.

Two, the RAB assignation fault analyzes 1

The calling party in Hot Spot, because Target cell is resource-constrained RAB assignment (foundation) procedure failure may to occur, we can help by the relevant information of these failures of output that we carry out the network optimization, set up RAB so that the user can success.

Such as the customer responsiveness data service can't activate or success rate very low.Just can be by user's phone number, MSISDN just finds the IMSI of this user mobile phone according to MSISDN, and is as follows such as the record that inquires:

User ID RAB assignation information	IMSI：460070114001271
		Traffic Class：Interactive
	CN Domain Ind：PS
		DL Maximum Bit Rate：384000bps
	UL Maximum Bit Rate：64000bps
		DL Guaranteed Bit Rate：None
	UL Guaranteed Bit Rate：None
		RAB ID：5
	RAB Setup Or Modify Time:2005 07 month 14: 00: 31 on the 21st
		The RAB failure information	RAB ID：5
CN Domain Ind：PS
	RAB Fail Time:2005 07 month 14: 00: 32 on the 21st
Optimum subdistrict information			RNC：10，CELLID：101
	RSCP：-80dbm
		EcNo：-12db
	Other active set cell information		None
Source RRC state		CELL_DCH
	Target RRC state		CELL_DCH
RAB Assignment Failure reason		The RNC internal error

	The failure of calling access
		Descending SF do not support
	>>>>SF：8
		Frequency point information	UARFCN uplink：none
UARFCN downlink：10613

Analyze this form and can obtain following information:

1, the signal of access point sub-district is no problem.RAB is the mutual industry affair of PS UL:64K/DL:384K.

The descending spreading factor of application was 8 when 2, the RRC connection was set up, but cell code resource is limited, the application failure.

Can know that from top output parameter the reason that this RAB sets up failure is because the down channel sign indicating number application of Target cell failure, cause the access failure and the RAB that causes sets up failure, we can provide as drawing a conclusion so:

1, whether Target cell is in hot zones, if, can suitably increase the same coverage cell of alien frequencies, increase the capacity of hot zones data service.

2, 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 power so, so that make the user can be evenly distributed to other neighbor cell.

Three, the RAB assignation fault analyzes 2

Can't receive calls when data service being arranged such as customer responsiveness.By user's phone number, MSISDN just finds the IMSI of this user mobile phone according to MSISDN, and is as follows such as the record that inquires:

User ID RAB assignation information 1	IMSI：460070114001271
		Traffic Class：Interactive
	CN Domain Ind：PS
		DL Maximum Bit Rate：384000bps
	UL Maximum Bit Rate：64000bps
		DL Guaranteed Bit Rate：None
	UL Guaranteed Bit Rate：None
		RAB ID：5
		RAB Setup Or Modify Time:2005 07 month 13: 00: 31 on the 21st
	RAB assignation information 2		Traffic Class：Conversational
CN Domain Ind：CS
		DL Maximum Bit Rate：12200bps
UL Maximum Bit Rate：12200bps
		DL Guaranteed Bit Rate：4750bps
UL Guaranteed Bit Rate：4750bps
		RAB ID：1
RAB Setup Or Modity Time:2005 07 month 14: 00: 31 on the 21st

The RAB failure information	RAB ID：1
		CN Domain Ind：CS
	RAB Fail Time:2005 07 month 14: 00: 32 on the 21st
		Optimum subdistrict information	RNC：10，CELLID：101
RSCP：-80dbm
	EcNo：-12db
Other active set cell information			None
	Source RRC state	CELL_DCH
Target RRC state			CELL_DCH
	RAB Assignment Failure reason	The RNC internal error
UE physical channel ability do not support
		The down physical channel ability
The every 10ms reception BIT number of physical channel maximum at interval: 9600
		The uplink physical channel ability
The every 10ms reception BIT number of physical channel maximum at interval: 1200
		Frequency point information	UARFCN uplink：none
UARFCN downlink：10613

Analyze this form and can obtain following information:

1, the signal of access point sub-district is no problem.Having set up a RAB is the mutual industry affair of PS UL:64K/DL:384K.

2, AMR voice 12.2K calls out owing to UE physical channel scarce capacity is failed.

Can know that from top output parameter the reason that this RAB sets up failure is that we can provide as drawing a conclusion so: user's mobile phone capacity is lower because the physical channel ability of UE is too poor.Can not concurrent voice-and-data business of while.

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 (36)

1. A method for reporting RAB assignment faults in a WCDMA system, characterized in that a RAB assignment fault parameter information set is set up, the RAB assignment fault parameter information set is set, and the RAB assignment fault parameter information set is set to report parameter items , when the RAB assignment is established, the following steps are included: A. Monitor the RAB assignment connection and receive the fault signal sent by the system when the RAB assignment connection fails; B. Query the parameter items required to be reported in the RAB assignment fault information set according to the fault cause indicated by the fault signal; C. Obtain the corresponding parameter value from the system according to the parameter item and write the fault report message; D. Send the fault report message to the network management center. 2. The method according to claim 1, wherein the RAB assignment failure information set is divided into user information, RAB information, failed RAB cell information, optimal cell information, and cell branch information part, RRC status information part, failure information part and frequency point information section. 3. The method of claim 2, wherein the subscriber information portion includes an International Mobile Subscriber Identity. 4. The method according to claim 2, wherein the RAB information part includes the information about the established or modified RAB list; the RAB list information includes: service type, core network information, maximum downlink rate, maximum uplink rate rate, guaranteed downlink rate, guaranteed uplink rate, RAB identifier, and RAB establishment or modification time. 5. The method according to claim 4, wherein the core network information includes a core network identifier. 6. The method according to claim 2, wherein the failed RAB cell information part includes a failed RAB list, and the list includes RAB ID, CN domain ID and RAB failure time. 7. The method according to claim 2, wherein the optimal cell information includes a cell identity and a current cell measurement result. 8. The method according to claim 2, wherein the cell branch information part includes cell branch information, and the cell branch information includes a cell identifier and a current cell measurement result. 9. The method according to claim 7 or 8, wherein the measurement result of the current cell includes parameters: CPICH Ec/No and CPICH total received power. 10. The method according to claim 2, wherein the RRC status information part includes a source RRC status indication and a target RRC status indication, and the source RRC status indication and the target RRC status indication include RRC status indication parameters. 11. The method of claim 10, wherein the failure information portion includes a reason for RAB failure. 12. The method according to claim 11, wherein the RAB failure reasons include RNC internal failure, IUB interface error, UU interface failure, IU interface failure and IUR interface failure. 13. The method according to claim 12, wherein the RNC internal failure includes call admission failure, limited UE capability, illegal RAB parameter, exceeding RNC specification, protocol or mismatched message error reason, ASN. 1 Error reason, L2 configuration error reason, ALCAP configuration error reason, user plane error reason and unknown error. 14. The method according to claim 13, wherein the call admission failure includes cell congestion, cell downlink spreading factor not supported, cell credit not supported, IUB port transmission resource unavailable and IUR transmission resource unavailable . 15. The method according to claim 14, wherein the cell congestion includes carrier transmit power and total receive power. 16. The method according to claim 14, wherein the cell downlink spreading factor does not support including spreading factor and SF256 occupancy rate. 17. The method according to claim 14, wherein the cell credit does not support including credit information, and the credit information includes: downlink spreading factor, uplink spreading factor, local cell credit information and local cell group credit information . 18. The method according to claim 17, wherein the local credit information and the local cell group credit information both include downlink or uplink and downlink capability credits, and uplink capability credits. 19. The method according to claim 14, wherein the unavailable IUB transmission resources include uplink IUB bandwidth and downlink IUB bandwidth; or, the unavailable IUR transmission resources include uplink IUR bandwidth and downlink IUR band. 20. The method according to claim 13, wherein the limited UE capability includes UE physical channel capability not supported, UE transport channel capability not supported and UE RLC capability not supported. 21. The method according to claim 20, wherein the UE physical channel capability does not support includes: a downlink physical channel capability and an uplink physical channel capability, and the downlink physical channel capability includes the maximum received bit of the physical channel at an interval of 10 ms The uplink physical channel capability includes the maximum number of transmitted bits of the physical channel per 10 ms interval. 22. The method according to claim 20, wherein the UE transmission channel capability does not support includes: a downlink transmission channel capability information part and an uplink transmission channel capability part; The downlink transmission channel capability information part includes: the maximum number of BITs that can be received in any time interval, the maximum number of BITs that can be received in any time interval with convolutional coding, the maximum number of BITs that can be received in any time interval with TURBO coding, The maximum number of transport channels, the maximum number of received transport blocks, the maximum number of transport format combinations and the maximum number of transport formats at the same time; The uplink transmission channel capability part includes: the maximum number of BITs that can be sent in any time interval, the maximum number of BITs that can be sent in convolutional codes in any time interval, the maximum number of BITs that can be sent in TURBO codes in any time interval, the same The maximum number of transport channels, the maximum number of transmitted transport blocks, the maximum number of transport format combinations and the maximum number of transport formats at any time. 23. The method according to claim 20, wherein the UE RLC capability does not support include: the total buffer size of the RLC acknowledged mode, the maximum RLC acknowledged mode window size and the maximum number of RLC acknowledged mode entities. 24. The method according to claim 13, characterized in that, the information exceeding the RNC specification includes a cause parameter exceeding the RNC specification; or, the error cause of the protocol or mismatched message comprises: protocol or mismatched message error reason parameter; or, the L2 configuration error reason includes an L2 configuration error reason parameter; or, the ALCAP configuration error reason includes: an ALCAP configuration error reason parameter; or, the user plane error reason includes: a user plane error reason parameter. 25. The method according to claim 12, wherein the IUB interface error includes NBAPRL establishment failure, NBAP RL reconfiguration failure, AAL2 establishment failure, RL recovery indication timeout, AAL2 modification failure and unknown error. 26. The method according to claim 25, wherein the NBAP RL establishment failure includes: RL establishment failure reasons, and RL establishment timer timeout parameters; or, the NBAP RL reconfiguration failure includes: RL reconfiguration The reason for failure is that the RL reconfiguration timer expires; or, the AAL2 establishment failure includes an AAL2 establishment failure cause parameter; or, the AAL2 modification failure cause parameter. 27. The method according to claim 26, wherein the reasons for RL establishment failure and RL reconfiguration failure include: wireless network layer reasons, transport layer reasons, protocol reasons and other reasons. 28. The method according to claim 12, wherein the UU interface failure includes RB establishment failure and no error. 29. The method according to claim 28, wherein the RB establishment failure includes RB establishment failure reasons and RB establishment timer overtime; the RB establishment failure reasons include: failure reasons, protocol error information, protocol error reasons , Deleted TGPSI and TGPSI parameters. 30. The method according to claim 12, wherein the IU interface failure includes: IU transmission failure, AAL2 establishment failure, AAL2 modification failure, IUUP establishment failure and unknown error. 31. The method according to claim 30, wherein the IU transmission failure includes IU transmission network failure reason parameters; the AAL2 establishment failure includes AAL2 modification failure parameters; and the IUUP establishment failure includes IUUP establishment failure reasons. 32. The method according to claim 31, wherein the cause of the IUUP establishment failure includes a user plane error cause parameter. 33. The method of claim 12, wherein the IUR interface failure includes an unknown error parameter. 34. The method according to claim 1, wherein the information element carrying the current reported parameter value is set in the fault report message according to the parameter items of each level. 35. The method according to claim 34, wherein the fault report message further includes: an information element carrying a message type identifier. 36. The method according to claim 34 or 35, further comprising: the network management center receiving the fault report message and extracting parameter values from each information element.

Images