CN100396135C - A method for reporting RAB assignment failure in wideband code division multiple access 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 Parameter items required to be reported in the parameter information set; C. Obtain corresponding parameter values from the system according to the parameter items required to be reported 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

A method for reporting RAB assignment failure in wideband code division multiple access system

technical field

The invention relates to a mobile communication system, and particularly discloses a method for reporting RAB assignment faults in a WCDMA (Wideband Code Division Multiple Access, wideband code division multiple access) system.

Background technique

The WCDMA system is an open system, which mainly includes CN (Core Network, core network), UTRAN (UMTS Terrestrial Radio Access Network, UMTS Terrestrial Radio Access Network), and UE (User Equipment, user terminal) three parts (other Parts such as network management and alarm station are not listed in this patent description). Among them, the RNC (Radio Network Controller, radio network controller) belongs to the UTRAN part. There are standard interfaces between the RNC and other network elements, such as the IU interface with the CN, the IUB interface with the NodeB, and the IUB interface with other RNCs. The IUR interface, and of course the interface between the UE and the RNC is the UU interface. One RNC can be connected to one or more NodeBs, and one NodeB includes one or more cells. After the UE is turned on and resides in a cell, it starts to receive network-side services, such as receiving system messages and paging messages. When the UE makes a call or receives a call, the UE initiates a call in this cell and triggers a series of standard interface procedures, as shown in Figure 1 .

In the process of wireless network operation, especially in the initial stage of network construction, this kind of problem often occurs. How to find and solve this kind of problem is particularly important. At the same time, the 3GPP protocol does not have a corresponding protocol standard for this kind of TRACE. How to output the protocol to facilitate the positioning of RAB (Radio Access Bearer, radio access bearer) assignment failures will become a key point in the process of network operation.

In the daily maintenance work of the existing network, the fault analysis is carried out through the following methods;

1. Performance statistics function

Performance statistics measure the quality of the current network by counting key statistical items in the network. The method is to count the success/failure times of cell update within a specific measurement period. And the statistical value is fed back to the network management system, which conducts a comprehensive analysis, and guides problem solving and network optimization through the analysis results.

Performance statistics function. Performance statistics is a long-term, or a statistical function of periodic tasks. It counts the success rate or failure rate of RAB assignment within a period of time. The statistical results themselves are very rough, and this function is statistical history. data, and abnormal analysis cannot be performed on the reasons for RAB assignment failures. If the granularity of performance statistics is increased and statistics on the reasons for RAB assignment failures are increased, a large amount of data will inevitably appear, which will affect normal services.

2. Network-wide signaling detection method

The method of signaling tracking is to track the call process in the standard protocol interface (such as UU, IUB) through the signaling tracking instrument, especially the standard protocol messages from different network elements, and send these related messages to the network management center, through Analyze these captured messages, optimize the network according to the analysis results, and solve some problems at the same time.

The whole network tracking method is a kind of real-time tracking, which needs to be tracked by special third-party instruments on all interfaces. This tracking does not distinguish whether it is a cell update, or whether the cell update is successful or not, which will generate a large amount of data. The current 2G network-wide signaling trace only traces the messages between the networks, that is, the messages of the core network, and does not trace the access network. For the 3G system, these tracking messages will be massive, especially when it is necessary to track the messages of the access network. How to obtain useful information from a large number of message traces will be a very large workload. In addition, tracing through signaling also requires a lot of experience to be able to quickly discover problems in messages, and this method is not easy to popularize among maintenance personnel.

3. Alarm

When the system fails, the alarm system can send the cause of the alarm to the network management system in real time, and the network management system can analyze and eliminate the fault according to the cause of the alarm and the equipment.

Generally speaking, alarms focus on equipment failures, and less attention is paid to user failures. For example, when the user causes RAB assignment failure due to wireless reasons, it cannot be reflected in the alarm. Therefore, the alarm basically cannot reflect or solve the problem of RAB assignment.

Contents of the invention

The present invention provides a method for reporting RAB assignment faults in a WCDMA system, which is used to solve the problem that in the prior art, when the access network fails in the execution of RAB assignment, the network management center cannot obtain detailed on-site information. Analysis and localization of the problem.

The inventive method comprises:

A method for reporting RAB assignment faults in a WCDMA system, establishing a RAB assignment fault parameter information set, the RAB assignment fault parameter information set, setting the RAB assignment fault parameter information set to report parameter items, when the RAB assignment is established , including the following steps:

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 parameter 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 reported as required and write the fault report message;

D. Send the fault report message to the network management center.

The RAB assignment failure parameter information set is divided into user information part, RAB information part, failed RAB cell information part, optimal cell information part, cell branch information part, RRC status information part, failure information part

and frequency point information section.

The user information part includes an International Mobile Subscriber Identity.

The RAB information part includes the RAB list information that has been and will be established or has been and will be modified; the RAB list information includes: service type, core network information, downlink maximum rate, uplink maximum rate, downlink guaranteed rate, uplink guaranteed rate, RAB Identifier, the time when the RAB was established or modified.

The core network information includes a core network identifier.

The failed RAB cell information part includes a failed RAB list, and the list includes RAB ID, CN domain ID and RAB failure time.

The optimal cell information part includes optimal cell information, and the optimal cell information includes a cell identifier and a current cell measurement result.

The cell branch information part includes cell branch information, and the cell branch information includes a cell identifier and a current cell measurement result.

The current cell measurement result includes parameters: CPICH Ec/No and CPICH total received power.

The RRC state information part includes a source RRC state indication and a target RRC state indication, and the source RRC state indication and the target RRC state indication include RRC state indication parameters.

The failure information part includes RAB failure reasons.

The RAB failure reasons include RNC internal failure, IUB interface error, UU interface failure, IU interface failure and IUR interface failure.

The RNC internal failure includes call admission failure, UE capability limitation, illegal RAB parameter, error reason exceeding RNC specification, protocol or mismatch message, ASN.1 error reason, L2 configuration error reason, ALCAP configuration error reason, user face error reasons and unknown errors.

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.

The cell congestion includes carrier transmit power and total receive power.

The downlink spreading factor of the cell does not support spreading factor and SF256 occupancy rate.

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.

Both the local cell credit information and the local cell group credit information include downlink or uplink capability credit, and uplink capability credit.

The unavailable IUB port transmission resources include uplink IUB bandwidth and downlink IUB bandwidth; or, the unavailable IUR transmission resources include uplink IUR bandwidth and downlink IUR bandwidth.

The UE capability limitation includes UE physical channel capability not supported, UE transmission channel capability not supported and UE RLC capability not supported.

The UE physical channel capability does not support include: downlink physical channel capability and uplink physical channel capability, the downlink physical channel capability includes the maximum number of received bits of the physical channel every 10ms interval, and the uplink physical channel capability includes the maximum number of bits received by the physical channel every 10ms interval Number of bits sent.

The UE transmission channel capability does not support including: a downlink transmission channel capability information part and an uplink transmission channel capability information 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 information 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 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 the same time.

The UE RLC capability does not support include: the total buffer size of the RLC confirmation mode, the maximum RLC confirmation mode window size and the maximum number of RLC confirmation mode entities.

The information of exceeding the RNC specification includes the cause parameter exceeding the RNC specification; or, the error cause of the protocol or mismatch message includes: the error cause parameter of the protocol or mismatch message; or, the L2 configuration error reason includes the L2 configuration error reason parameter; or, the ALCAP configuration error reason includes: ALCAP configuration error reason parameter; or, the user plane error reason includes: user plane error reason parameter.

The IUB interface error includes NBAP RL establishment failure, NBAP RL reconfiguration failure, AAL2 establishment failure, RL recovery indication timeout, AAL2 modification failure and unknown error.

The NBAP RL establishment failure includes: RL establishment failure reasons, and RL establishment timer overtime parameters; or, the NBAP RL reconfiguration failure includes: RL reconfiguration failure reasons, RL reconfiguration timer overtime; or, the AAL2 The establishment failure includes AAL2 establishment failure reason parameters; or, the AAL2 modification failure includes AAL2 modification failure reason parameters.

The reasons for RL establishment failure and RL reconfiguration failure include: wireless network layer reasons, transport layer reasons, protocol reasons and other reasons.

The UU interface failure includes RB establishment failure and unknown error.

The RB establishment failure includes RB establishment failure reasons and RB establishment timer timeout; the RB establishment failure reasons include failure reasons, protocol error information, protocol error reasons, deleted TGPSI and TGPSI parameters.

The IU interface failure includes IU transmission failure, AAL2 establishment failure, AAL2 modification failure, IUUP establishment failure and unknown error.

The IU transmission failure includes IU transmission network failure reason parameters; the AAL2 establishment failure includes AAL2 establishment failure parameters; the AAL2 modification failure includes AAL2 modification failure parameters; the IUUP establishment failure includes IUUP establishment failure reasons.

The cause of the IUUP establishment failure includes a user plane error cause parameter.

The IUR interface failure includes an unknown error parameter.

In the fault report message, the information element carrying the current reported parameter value is set according to the parameter items of each level.

The fault report message also includes an information element carrying a message type identifier.

The method further includes the network management center receiving the fault report message and extracting parameter values from each information element.

The beneficial effects of the present invention are as follows:

In the early stage of 3G network operation, 3G network coverage often appears unreasonable, for example, the coverage area of the cell is too large, and when there are too many users, the resource of the cell is exhausted. Or the capability of the terminal is limited, for example, the PDP rate subscribed by the UE exceeds the capability of the UE, so that the RAB cannot be established successfully, and so on. These reasons will cause the access network to fail when performing the RAB assignment process.

If the above situation occurs, the specific reason for RAB assignment failure can be obtained through the method described in this patent, so that the problem of RAB assignment failure can be solved.

Description of drawings

FIG. 1 is a schematic structural diagram of a UTRAN system in the prior art;

Fig. 2 is the schematic flow chart of RAB establishment on the dedicated channel of the present invention;

Fig. 3 is a schematic flow chart of reporting fault information in the present invention.

Detailed ways

The present invention provides a kind of call history record (CHR), and this record can track the problem that occurs in the RAB establishment process, and feeds back to the network management system through the standard protocol message, and the network management system analyzes the problem that calls occur according to these historical records, And analyze the problem through these message cells, and recover the fault through corresponding means.

The RAB assignment process includes the RAB establishment, modification and release process. The following takes RAB establishment (DCH to DCH-synchronization) as an example to illustrate the protocol process, as shown in Figure 2, including the following steps:

1. The CN sends a RAB assignment request (RAB ASSIGNMENT REQUEST) message to the SRNC. The message includes RAB parameters, user plane mode and transport layer related information, and the SRNC provides user radio layer and transport layer resources through these information;

2. The SRNC uses the ALCAP protocol to initiate the establishment of the IU data transmission bearer. The establishment request sent to ALCAP contains a binding ID, which is used to bind the IU data transmission bearer and the radio access bearer (this step is not required if the RAB is a PS domain);

3. If there is a DRNC, the SRNC sends a radio link reassignment preparation (RADIOLINK RECONFIGURATION PREPARE) request message to the DRNC, requesting to increase the DCH carrying the RAB;

4. If there is DRNC, DRNC sends a radio link reassignment preparation (RADIOLINK RECONFIGURATION PREPARE) request message to NODEB, requesting NODEB to increase the DCH carrying RAB;

5. SRNC sends a radio link reassignment preparation (RADIO LINKRECONFIGURATION PREPARE) request message to NODEB, requesting NODEB to increase the DCH carrying RAB;

6. After the resource allocation of NODEB is completed, return the radio link reassignment ready (RADIO LINK RECONFIGURATION READY) message to DRNC;

7. The DRNC sends a radio link reassignment ready (RADIO LINKRECONFIGURATION READY) message to the SRNC to notify the SRNC that the RL is ready for reconfiguration;

8. After the NODEB resource allocation is completed, return the radio link reassignment ready (RADIO LINK RECONFIGURATION READY) message to SRNC;

9. The SRNC uses the ALCAP protocol to initiate the establishment of the IUB/IUR data transmission bearer. The establishment request sent to ALCAP contains the binding ID, which is used to bind the IUB/IUR data transmission bearer and radio access bearer;

10. The SRNC uses the ALCAP protocol to initiate the establishment of the IUB data transmission bearer. The establishment request sent to ALCAP contains the binding ID, which is used to bind the IUB data transmission bearer and the radio access bearer;

11. If there is DRNC, SRNC sends downlink synchronization to NODEB, and performs the FP synchronization process of IUB and IUR ports;

12. SRNC sends downlink synchronization to NODEB, and performs FP synchronization process of IUB port;

13. NODEB of DRNC and SRNC perform uplink FP synchronization;

14. NODEB of SRNC and SRNC perform uplink FP synchronization;

15. If there is a DRNC, the SRNC sends a radio link reassignment commit (RADIO LINK RECONFIGURATION COMMIT) message to the SRNC through the IUR port;

16. If there is a DRNC, the DRNC sends a radio link reassignment commit (RADIOLINK RECONFIGURATION COMMIT) message to NODEB;

17. The SRNC sends a radio link reassignment commit (RADIO LINKRECONFIGURATION COMMIT) message to the NODEB.

18. The SRNC sends a radio bearer setup (RADIO BEARER SETUP) message to the UE;

19. The UE returns a radio bearer setup complete (RADIO BEARER SETUPCOMPETE) message to the SRNC;

20. The RNC returns a radio bearer assignment response (RAB ASSIGNMENT RESPONSE) message to the CN.

From the above message flow, it can be seen that the RAB establishment has gone through many steps, and errors may occur in each step, which may cause the RAB establishment to fail.

In view of the above problems, there is no output content of RAB assignment failure in the current 3GPP protocol, including a detailed description of the cause of failure. The present invention provides a historical record CHR of RAB assignment fault location analysis. When a fault occurs during RAB assignment At this time, the RNC will send a message to the network management center, and reflect relevant information in the message in the form of a protocol cell, so as to provide maintenance personnel with a positioning solution.

First of all, the present invention sets a RAB assignment fault parameter information set for this problem, the RAB assignment fault parameter information is set in the RAB assignment fault reporting parameter item, and the RAB assignment fault parameter information set can be in the form of a table, It may also be a tree structure commonly used in current network management. After the RAB assignment fails, send relevant parameters to the network management center according to the RAB assignment failure parameter information set to locate the problem and guide the operator to optimize the network.

In the present invention, in the RAB assignment fault, the relevant information is selected according to the RAB assignment fault parameter information set. Fill it out and send it to the network administrator for related fault analysis and location.

As shown in Figure 3, when the RAB is assigned, the following steps are included:

S1. Monitor the RAB assignment connection and receive the fault signal sent by the system when the RAB assignment connection fails;

S2. Query the parameter items required to be reported in the RAB assignment fault parameter information set according to the fault cause indicated by the fault signal;

S3. Obtain corresponding parameter values from the system according to the parameter items reported as required, and write a fault report message;

S4. Send the fault report message to the network management center.

In the fault report message, the information element carrying the current reported parameter value is set according to the parameter items of each level. The fault report message also includes: an information element carrying a message type identifier.

The network management center receives the fault report message and extracts parameter values from each information element.

The invention provides a RAB assignment fault location analysis method. When a fault occurs during the RRC connection establishment process, the system will send a fault report message to the network management center, and reflect the relevant fault information in the message in the form of cells. In order to provide maintenance personnel positioning solution.

For the convenience of description, we detail the RAB assignment fault parameter information set, and form the RAB assignment fault protocol table according to the RAB assignment fault parameter information set. The relevant structure of the fault protocol table will be described in detail below.

The protocol structure is shown in Table 1 to Table 21, in which each cell is divided into mandatory, optional, and conditional categories according to whether the parameters it carries are necessary parameters for cause analysis. The specific meanings are shown in Table 0, and in each table Defined in the Need column.

table 0

abbreviation meaning MP This information element must be included in the protocol structure information element OP This information element may be included in the protocol structure information element CV When the conditions are met, the information element will be included in the protocol structure information element, otherwise, the information element will not be included in the protocol structure information element, such as CV-CELL_DCH indicates that the UE includes the information element when it is in the CELL_DCH state

Among them, the structure of Table 1 to Table 21 is divided step by step according to the required parameter types. Table 1 is the general category table, and the corresponding sub-tables are established step by step. According to the structure of the table, the type is used as the index to facilitate search and reduce the error rate.

Table 1 RAB Assignment Failure Protocol Structure

Information Element/Group name need Multi Type and reference Semanticsdescription Message Type MP Message Type User information part (UE informationelements) International Mobile Subscriber Identity (IMSI) MP International Mobile Subscriber Identity (IMSI) Reference Table 12 RAB information part (RAB Informationelements) Already and about to establish or modify RAB (RABs Setup Or Modified List) MP RAB list information (RAB List information) reference table 2 Fail RABsInformation elements Failed RAB List (Failed RAB List) MP Failed RAB List Information (FailedRAB List Information) reference table 11 Best Cellinformation elements Best Cell Information MP Cell Information (Cell Information) reference table 3 Cell LegInformation elements Cell Leg Information MP 0～6 Cell Information (Cell Information) reference table 3 RRC Stateinformation elements Source RRC State Indicator (Source RRC StateIndicator) MP RRC State Indicator (RRC State Indicator) reference table 15 Destination RRC State Indicator MP RRC State Indicator (RRC State Indicator) reference table 15 Failure information elements RAB Failure Cause (RAB Failure Cause) MP RAB Failure Cause (RAB Failure Cause) reference table 4

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

Table 2, RAB List Information (RAB List Information)

Table 3. Cell Information

Information Element/Groupname need Multi Type and reference Semantics description Cell ID (Cell identity) MP BITSTRING(28) Measurement result for current cell ＞CPICH Ec/N0 CPICH Ec/No OP INTEGER(0..49) EC/NO obtained in ls before call drop ＞Total receiving power (CPICH RSCP CPICH) OP INTEGER(0..91)

Table 4. RAB Failure Cause (RAB Failure Cause)

Information Element/Groupname need Multi Type and reference Semanticsdescription CHOICE Cause Group MP ＞RNC Internal Failure (RNC InnerFailure Choice) OP ＞＞Call Admission Failure OP Call Admission Failure Reference Table 17 ＞＞Capability limited (UE capability limited UE) OP

＞＞＞Physical channel capability not supported (UE physical channel capability not supported UE) OP UE Physical channel capability reference table 6 ＞＞＞Transport channel capability not supported (UE Transport channelcapability not supported UE) OP UE transport channel capability reference table 8 ＞＞＞UE RLC capability not supported (UERLC capability limited) OP RLC capability reference table 7 ＞＞Illegal RAB parameter (InvalidRAB parameter) OP ＞＞Out of RNC specification (Out of RNC specification) OP Out of RNC specification cause reference table 9 ＞＞Protocol or UnmatchedMessage Error Cause OP Protocol or Unmatched MessageError Cause Reference Table 18 ＞＞ASN.1 Error Cause (ASN1 Error Cause) OP ENUMERATED(Transfer SyntaxError, Abstract Syntax Error, Logical Error, ...). ＞＞L2 Configuration Error Cause (L2Configuration Error Cause) OP L2 Configuration Error Cause Reference Table 19 ＞＞ALCAP Configuration Error Cause (ALCAP Configuration ErrorCause) OP ALCAP Configuration Error Cause Reference Table 20 ＞＞User Plane Error Cause OP User Plane Error Cause Reference Table 21 ＞＞Unknown error (Unspecified) OP ＞IUB Interface Error (IUB Interface FailureChoice) OP ＞＞NBAP RL setup failure (NBAP RL Setup Failure) OP ＞＞＞RL Setup Failure cause (RL Setup Failure cause) OP RL Setup Failure cause reference table 14 ＞＞＞RL Setup Timer Expire OP ＞＞NBAP RL Reconfiguration Failure (NBAP RL ReconfigurationFailure) OP ＞＞＞RL Reconfiguration Failure Cause (RL Reconfiguration FailureCause) MP RL Setup Failure cause reference table 14 ＞＞＞RL Reconfiguration Timer Expire (RL Reconfiguration TimerExpire) OP ＞＞AAL2 Setup Failure (AAL2 Setup Failure) OP ＞＞＞AAL2 Setup Failure Cause (AAL2 Setup Failure Cause) MP ENUMERATED(Inner EstablishFailure, QAAL2 No AAL2Route, QAAL2 No Resource, QAAL2 AN1 Unreachable, QAAL2 Temporary Error, PeerECF Failure for Normal Cause, PeerECF Failure for Other Cause,...) ＞＞RL Restore Indication timeout (RL Restore Indication timeout) OP ＞＞AAL2 modification failed OP

(AAL2 Modify Failure) ＞＞＞AAL2 Modify Failure Cause (AAL2 Modify FailureCause) MP ENUMERATED(QAAL2 ModifyCollision, 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 FailureChoice) OP ＞＞RB Setup Failure OP ＞＞＞RB Setup Failure cause (RB Setup Failure cause) OP UU Interface Failure cause reference table 10 ＞＞＞RB Setup Timer Expire OP ＞＞Unknown error (Unspecified) OP ＞IU Interface Failure (IU Interface Failure) OP ＞＞IU Transport Failure OP ＞＞＞IU Transport NW FailureCause MP ENUMERATED(signallingtransport resource failure, iu-transport-connection-failed-to-establish, ...) ＞＞AAL2 Setup Failure (AAL2 Setup Failure) OP ＞＞＞AAL2 Setup Failure Cause (AAL2 Setup FailureCause) MP ＞＞AAL2 Modify Failure (AAL2 Modify Failure) OP ＞＞＞AAL2 modification failure (AAL2Modify FailureCause) MP ENUMERATED(QAAL2 ModifyCollision, QAAL2 Modify Not Support, QAAL2 Modify No Resource, QAAL2 Modify Temporary Error, QAAL2 Modify Peer Failure,...) ＞＞IUUP Setup Failure (IUUP Setup Failure) OP ＞＞＞IUUP Setup Failure Cause (IUUP Setup FailureCause) MP User Plane Error Cause Reference Table 21 ＞＞Unknown error (Unspecified) OP ＞IUR Interface Failure (IURInterface Failure Choice) OP ＞＞Unknown error (Unspecified) OP

Table 5. CN domain identity core domain identity

Information Element/Groupname need Multi Type and reference Semanticsdescription CN domain identity MP ENUMERATED(CS domain, PS domain)

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

Information Element/Groupname need Multi Type and Reference Semanticsdescription Downlink physical channel capability (FDDdownlink physical channelcapability) ＞The maximum number of physical channel bits received in any 10ms interval (Maximum number of physical channel bits received inany 10ms interval) MP INTEGER(1200, 2400, 3600, 4800, 7200, 9600, 14400, 19200, 28800, 38400, 48000, 57600, 67200, 76800) Uplink physical channel capability (FDD uplink physical channelcapability) ＞Maximum number of DPDCH bits transmitted per 10ms per physical channel MP INTEGER(600, 1200, 2400, 4800.9600, 19200.28800, 38400, 48000, 57600)

Table 7, UE RLC capability (UE RLC capability)

Information Element/Group name need Multi Type and Reference Semantics description The total buffer size of RLC confirmation mode (Total RLC AM buffer size) MP INTEGER(10, 50, 100, 150, 500, 1000) Maximum RLC AM WindowSize (Maximum RLC AM WindowSize) MP INTEGER(2047, 4095) The maximum number of RLC confirmation mode entities (Maximum number of AM entities) MP INTEGER (4, 5, 6, 8, 16, 30)

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

Information Element/Groupname need Multi Type and Reference Semanticsdescription Downlink transport channel capability information elements The maximum number of bits being received at an arbitrary time instant (Maximum number of bits being received at an arbitrary time instant) MP INTEGER(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840)

Maximum number of convolutionally coded bits being received at an arbitrary time instant MP INTEGER(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Maximum number of turbo coded bits being received at an arbitrary time instant OP INTEGER(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) The maximum number of simultaneous transport channels at the same time (Maximum number ofsimultaneous transport channels) MP INTEGER(4, 8, 16, 32) The maximum number of received transport blocks (Maximum number of received transport blocks) MP INTEGER(4, 8, 16, 32, 48, 64, 96, 128, 256, 512) The maximum number of transport format combinations (Maximum number of TFC) MP INTEGER(16, 32, 48, 64, 96, 128, 256, 512, 1024) Maximum number of transmission formats (Maximumnumber of TF) MP INTEGER(32, 64, 128, 256, 512, 1024) Uplink transport channel capability information elements The maximum number of bits being transmitted at an arbitrary time instant (Maximum number of bits being transmitted at an arbitrary time instant) MP INTEGER(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Maximum number of convolutionally coded bits being transmitted at an arbitrary time instant MP INTEGER(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) The maximum number of turbo coded bits being transmitted at an arbitrary time instant that can be sent in any time interval OP INTEGER(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) The maximum number of simultaneous transport channels at the same time (Maximum number ofsimultaneous transport channels) MP INTEGER(4, 8, 16, 32) The maximum number of transmitted transport blocks (Maximum number of transmitted transport blocks) MP INTEGER(4, 8, 16, 32, 48, 64, 96, 128, 256, 512) The maximum number of transport format combinations (Maximum number of TFC) MP INTEGER(16, 32, 48, 64, 96, 128, 256, 512, 1024) Maximum number of transmission formats (Maximumnumber of TF) MP INTEGER(32, 64, 128, 256, 512, 1024)

Table 9. Out of RNC specification cause

Information Element/Groupname need Multi Type and reference Semanticsdescription Out of RNC specification cause (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)

InformationElement/Group name need Multi Type and reference SemanticsDescription Failure cause MP Enumerated(configuration unsupported, physical channel failure, incompatiblesimultaneous reconfiguration, protocolerror, compressed mode runtime error, cell update occurred, invalidconfiguration, configuration incomplete, unsupported measurement) Rel-5 Protocol error information CV-ProtErr ＞CHOICE diagnostics type MP ＞＞Protocol error cause Enumerated(ASN.1 violation orencoding error, Message typenon-existent or not implemented, Message not compatible with receiverstate, Information element value notcomprehended, Information elementmissing, Message extension notcomprehended) Rel-5 Deleted TGPSI (Deleted TGPSI) CV-CompModeErr > TGPSI MP Integer(1..MaxTGPS) Rel-5

Table 11. Failed RAB List Information

Information Element/Group name need Multi Type and reference Semanticsdescription Failed RAB List (Failed RAB List) 1 to 255 ＞RAB ID MP BIT STRING(8) ＞CN Domain Identity MP CN DomainIdentity Reference Table 5 ＞RAB Failure Time (RAB Failure Time) MP BIT STRING(32) (DATE: HOUR: MINUTE: SECOND)

Table 12. IMSI (GSM-MAP)

Information Element/Groupname 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 up to 15digits are used for this IE, abigger length is used to support future extension. ＞IMSI digit MP INTEGER(0..9)

Table 13. Credit information

Information Element/Groupname need Multi Type and reference Semantics description Downlink Spreading Factor (DL SpreadingFactor) MP ENUMERATED(4, 8, 16, 32, 64, 128, 256, 512) Uplink Spreading Factor (UL SpreadingFactor) MP ENUMERATED(4, 8, 16, 32, 64, 128, 256, 512) Local Cell Credit Information MP ＞Downlink or Uplink Capacity Credit (DL Or Global CapacityCredit) MP INTEGER(0..65535) ＞Uplink Capacity Credit (UL CapacityCredit) OP INTEGER(0..65535) Local Cell Group Credit Information OP ＞Downlink or Uplink Capacity Credit (DL Or Global CapacityCredit) MP INTEGER(0..65535) ＞Uplink Capacity Credit (UL Capacity Credit) OP INTEGER(0..65535)

Table 14. RL Setup Failure cause (RL Setup Failure cause)

InformationElement/Group name need Multi Type and reference SemanticsDescription CHOICE Cause Group m ＞Wireless Network Layer (RadioNetwork Layer) ＞＞Radio Network LayerCause 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 not the object, Combining avResources ，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 notelapsed，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, Uphann Link Shared 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 Synchronization not supported, Cell Adjustment Synchronization, PC 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 needed, Re-arrangement not supported Delayed Activation not Supported，RL Timing Adjustment not supported) ＞Transport Layer (TransportLayer)

＞＞Transport Layer Cause m ENUMERATED(Transport resource unavailable, Unspecified,...) ＞Protocol ＞＞ProtocolCause 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),... ＞Others (Misc) ＞＞Other reasons (MiscellaneousCause) m ENUMERATED(Control processing overloadHardware failure, O&M intervention, Not enough user plane processing resources, Unspecified,...)

Table 15. RRC State Indicator (RRC State Indicator)

Information Element/Groupname need Multi Type and reference Semanticsdescription RRC State indicator RRC state indication MP ENUMERATED(CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH)

Table 16. Frequency info

Information Element/Groupname need Multi Type and reference Semantics description CHOICE mode MP ＞FDD ＞＞Uplink frequency (UARFCN uplink(Nu)) OP INTEGER(0..16383) ＞＞Downlink frequency (UARFCN downlink(Nd)) MP INTEGER(0..16383)

Table 17. Call Admission Failure

Information Element/Groupname need Multi Type and reference Semantics description Call Admission Failure CHOICE ＞Cell Congestion OP

＞＞Carrier transmit power (TransmittedCarrier Power Value) MP INTEGER(0..100) ＞＞Received TotalWide Band Power Value MP INTEGER(0..621) ＞Cell downlink spreading factor not supported (CellDL SF not supported) OP ＞＞Spreading Factor MP ENUMERATED(4, 8, 16, 32, 64, 128, 256, 512) ＞＞SF256 occupancy rate (Occupied Rateof SF＝256) MP INTEGER(0..100) ＞Cell Credit not supported OP ＞＞Credit information MP Credit information reference table 13 ＞IUB Transport resource unavailable OP ＞＞Uplink IUB bandwidth (UL IUB bandwidth) MP INTEGER(0..65535) Unit: byte ＞＞Downlink IUB bandwidth (DL IUB bandwidth) MP INTEGER(0..65535) Unit: byte ＞IUR Transport resource unavailable (IUR Transport resource unavailable) OP ＞＞Uplink IUR bandwidth (UL IUR bandwidth) MP INTEGER(0..65535) Unit: byte ＞＞Downlink IUR bandwidth (DL IUR bandwidth) MP INTEGER(0..65535) Unit: byte

Table 18. Protocol or Unmatched Message Error Cause (Protocol or Unmatched Message ErrorCause)

InformationElement/Group name need Multi Type and reference SemanticsDescription Protocol or Unmatched Message Error Cause (Protocol or UnmatchedMessage Error Cause) MP Enumerated(RAB_CFG_TRANSP_LAYER_ADDR_LEN_ERROR，RAB_CFG_TRANS_ASSOCI_NO_TEID_ERROR，RAB_MODIFY_VER_LIMIT_ERROR，RAB_ABSTRACT_SYNTAX_ERROR_REJ，RAB_ABSTRACT_SYNTAX_ERROR_FAUSELY_CONSTRUCTED，RAB_INVALID_RAB_ID_ERROR，RAB_ASSIGN_HANDLE_RAB_NUM_ZERO_ERROR，RAB_ASSIGN_HANDLE_RAB_ID_REPEATED_ERROR，RAB_TRAFFIC_CLASS_NOT_SUPP_ERROR，RELOC_MSG_DATA_ERR，RELOC_RAB_ID_ERR，RELOC_RB_ID_ERR，RELOC_SOME_RAB_FAIL，RELOC_MISS_URNTI，RELOC_SYS_HO_RELOC_CMD_NO_L3INFO，RELOC_IU_REQ_SECURITY_MODE_ALGOR_NOT_SUPP，RELOC_IU_CHANGE_SECURITY_MODE_NOT_SUPP，COMM_IU_REQ_SECURITY_MODE_ALGOR_NOT_SUPP，COMM_IU_CHANGE_SECURITY_MODE_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. L2 Configuration Error Cause

InformationElement/Group name need Multi Type and reference SemanticsDescription Cause of Layer 2 Configuration Error (L2 Configuration ErrorCause) 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_TIMEOUT，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 Cause

InformationElement/Group name need Multi Type and reference SemanticsDescription ALCAP Configuration Error Cause (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 Plane Error Cause

InformationElement/Groupname need Multi Type and reference Semanticsdescription 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 is illustrated below through some examples.

1. CHR information organization method

If an error occurs during the RAB assignment process and the assignment process fails, then if the information is organized according to the CHR reporting format mentioned in this article.

1), as shown in Figure 1 in step 1, the SRNC allocates parameters according to the RAB information assigned by the CN. During the allocation process, it is found that the spreading factor that the RAB needs to use is 8, but the minimum available spreading factor in the current cell If it is 64, there will be no idle code resources and the RAB cannot be established successfully. Therefore, according to the description of the RAB assignment failure protocol structure shown in Table 1, the following information needs to be recorded:

(1), the user's IMSI (SRNC will obtain the COMMON ID from the CN when establishing the IU connection in the pre-assignment process);

(2) The service type, maximum uplink and downlink rate, guaranteed uplink and downlink rate, and RAB ID in the RAB parameter in the RAB ASSIGNMENT REQUEST message;

(3), obtain the CN domain mark according to the IU connection, such as CS or PS;

(4), the current cell ID, and the RSCP or Ec/No of the cell reported by the UE last (which may come from the random access channel measurement report and the cell quality measurement report in the RRC connection request);

(5) If there are other communities in the activity concentration, proceed similarly to (4);

(6), the current RRC connection state, if it is currently in the CELL_FACH state, set the source RRC state to CELL_FACH; if the target RRC state needs to be migrated to CELL_DCH, then set the target RRC state to CELL_DCH;

(7) The cause of the setting failure can be known from the table. This reason should be attributed to an internal error of the RNC-call admission failure-insufficient downlink spreading factor-SF8.

2. RAB assignment failure analysis 1

When the calling user is in a hotspot cell, the RAB assignment (establishment) process may fail due to the limited resources of the target cell. We can help us optimize the network by outputting relevant information about these failures, so that the user can successfully establish RAB .

For example, users report that the data service cannot be activated or the success rate is very low. You can find the IMSI of the user's mobile phone based on the user's mobile phone number, that is, MSISDN. For example, the records found are as follows:

Analyzing the table yields the following information:

1. There is no problem with the signal of the access point cell. RAB is PS interactive line service UL: 64K/DL: 384K.

2. The downlink spreading factor applied for when the RRC connection is established is 8, but the resource of the cell code is limited, so the application fails.

From the above output parameters, we can know that the reason for the RAB establishment failure this time is that the downlink channel code application of the target cell failed, which resulted in the RAB establishment failure caused by the admission failure, then we can draw the following conclusions:

1. Whether the target cell is in a hotspot area, if so, you can appropriately increase the number of cells with different frequencies and the same coverage, and increase the capacity of data services in the hotspot area.

2. Whether the pilot power of the target cell is set too high, causing too many users to access the cell. If yes, then the power should be reduced so that users can be evenly distributed to other neighboring cells.

3. RAB assignment fault analysis 2

For example, users report that they cannot answer calls when they have data services. Through the user's mobile phone number, that is, MSISDN, the IMSI of the user's mobile phone can be found according to the MSISDN. For example, the queried records are as follows:

Analyzing the table yields the following information:

1. There is no problem with the signal of the access point cell. A RAB has been established for the PS interactive line service UL: 64K/DL: 384K.

2. The AMR voice 12.2K call fails due to insufficient UE physical channel capability.

From the above output parameters, it can be known that the reason for the RAB establishment failure this time is that the physical channel capability of the UE is too poor, so we can draw the following conclusion: the mobile phone capability of the user is relatively low. Voice and data services cannot be performed concurrently.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (36)

1. A reporting method for RAB assignment failure in a WCDMA system, characterized in that, a RAB assignment failure parameter information set is set up, the RAB assignment failure parameter information set is set, and the RAB assignment failure 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 parameter 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 reported as required 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 parameter information set is divided into a user information part, an RAB information part, a failed RAB cell information part, an optimal cell information part, and a cell branch Information part, RRC status information part, failure information part and frequency point information part. 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 RAB list information that has been and will be established or has been and will be modified; the RAB list information includes: service type, core network information, downlink maximum rate, uplink maximum rate, downlink guaranteed rate, uplink guaranteed rate, RAB identifier, 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 an RAB identifier, a CN domain identifier and RAB failure time. 7. The method according to claim 2, wherein the optimal cell information part includes optimal cell information, and the optimal cell information includes a cell identifier 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 current cell measurement result includes parameters: CPICH Ec/No and CPICH received total 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 part 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 internal failure of the RNC includes call admission failure, limited UE capability, illegal RAB parameters, exceeding RNC specifications, protocol or mismatched message error reasons, 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 downlink spreading factor of the cell 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 cell 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 port transmission resources include uplink IUB bandwidth and downlink IUB bandwidth; or, the unavailable IUR transmission resources include uplink IUR bandwidth and downlink IUR bandwidth. 20. The method according to claim 13, wherein the limited UE capability includes that UE physical channel capability does not support, UE transmission channel capability does not support, and UE RLC capability does not support. 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 information 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 information 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 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 the same time. 23. The method according to claim 20, wherein the UE RLC capability does not support includes: the total buffer size of the RLC acknowledgment mode, the maximum RLC acknowledgment mode window size and the maximum number of RLC acknowledgment mode entities. 24. The method according to claim 13, wherein the information exceeding the RNC specification includes exceeding the RNC specification reason parameter; or, the protocol or the mismatched message error reason include: the protocol or the 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 comprises NBAPRL establishment failure, NBAP RL reconfiguration failure, AAL2 establishment failure, RL recovery indication overtime, AAL2 modification failure and unknown error. 26. The method according to claim 25, wherein, the NBAP RL establishment failure comprises: RL establishment failure reasons, and RL establishment timer overtime parameters; or, the NBAP RL reconfiguration failure comprises: RL reconfiguration The reason for the failure is that the RL reconfiguration timer expires; or, the AAL2 establishment failure includes the AAL2 establishment failure reason parameter; or, the AAL2 modification failure includes the AAL2 modification failure reason 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 unknown 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 the IU transmission network failure reason parameter; the AAL2 establishment failure includes the AAL2 establishment failure reason parameter; the AAL2 modification failure includes the AAL2 modification failure reason Parameter; the failure to establish the IUUP includes the cause of the failure to establish the IUUP. 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 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