CN100367817C - Reporting method for switching fault between systems - Google Patents

Abstract

The present invention discloses a method for reporting switch faults between systems, which is applied to a switch from a 2G system to a 3G system. The method comprises the following steps: a parameter information set of switch faults between systems is established for setting reporting parameter items of switch faults between systems, when the systems are switched, the following steps are carried out: A. a switching process between the systems is monitored, and a fault signal is sent out by a receiving system when the switch is failed; B. the parameter items required to report in the parameter information set of switch faults between systems are inquired according to failing reasons pointed out by the fault signal; C. corresponding parameter values are obtained from the systems according to the parameter items, and a fault reporting message is written in; D. the fault reporting message is sent to a network management center. The method of the present invention can report fault information in time, determine the failing reasons and thereby guide network optimization.

Description

Reporting method for switching fault between a kind of system

Technical field

The present invention relates to the switching to the 3G system, refer to reporting method for switching fault between a kind of system especially from the 2G system.

Background technology

The WCDMA system is an open system, and this system mainly comprises CN (Core Network, core net), UTRAN (UMTS Terrestrial radio access network) and UE (user terminal) three parts.RNC wherein (radio network controller) belongs to the UTRAN part, and RNC and other network element exist standard interface, such as and CN between the IU interface, and be the IUB interface between the NodeB (base station), and between other RNC the IUR interface, and the UU interface between UE and the RNC, as shown in Figure 1.

Switching between system is exactly that UE switches to 3G (WCDMA) system from 2G system (GSM), and business is not interrupted.Because at the initial stage of construction network, operator only can lay the 3G system at some hot zones, with the controlled investment scale, other areas all are to finish covering by the 2G system, like this, be easy to occur such application scenarios, a user who has opened the 3G service in operator, when he does not have now in the coverage of 3G system, operator can only provide the service of 2G to him, if at this moment he converse in 2G cell, in the time of near the user moves to 2G cell and boundary, 3G sub-district, operator wishes this user to be cut into from 2G cell smoothly the sub-district of 3G, and enjoyment 3G service and assurance current talking are not interrupted, and the WCDMA system has proposed to switch between system the notion of going into for this reason.

Switching between system is a important component part in the mobile management of 3G system.Between system, switch in the process of going into to handle, related to the most of network element of 3G and 2G, comprise MSC (mobile switching centre), the BSC (base station controller) of 2G and CN, RNC, SGSN (the Serving GPRS SupportNode of 3G; Serving GPRS Support Node) etc., cause switching between system the processing failure owing to exist some accidents or abnormal situation, congested such as switching the Target cell of going between system, perhaps the Target cell quality is too poor, so because the appearance of this situation, cause handoff failure, and then may cause call drop.

In the process of wireless network operation, especially the networking initial stage, switch unavoidably between system, therefore, how to find and resolve the problem of handoff failure between system, just seem particularly important.Because existing 3GPP agreement is followed the tracks of (TRACE) and is not had the corresponding protocol standard switching, how when breaking down, switching to carry out agreement output so that switch between navigation system and go into failure problems, in the process of network operation, can become an emphasis.

In the line service of existing network, carry out accident analysis by the following method;

(1) performance statistics: performance statistics is a quality of weighing current network by statistical items crucial in the statistics network, this method is that statistics was switched between system to go into to prepare in a specific measuring period, switch to go into to run succeeded/frequency of failure between system, and this statistical value fed back to network management system, comprehensively analyze by network management system, instruct dilatation and problem to solve existing network by analysis result.

(2) the whole network signaling test method: the method for signaling tracing be by the signaling tracing instrument in standard protocol interface (as UU, IUB) follow the tracks of calling procedure in, especially from the standard agreement message in the different network elements, and the message that these are relevant sends to network management center, these message of catching are analyzed, according to analysis result network is optimized, solves subproblem simultaneously.

(3) alarm method: network management system can be carried out the eliminating and the management of network failure to the processing and the analysis of warning information.When system breaks down, warning system can be real-time will alarm the reason that produces and send to network management system, and network management system can be analyzed and gets rid of the fault that is taken place according to producing alarm cause and equipment.

The shortcoming that above-mentioned prior art exists is as follows:

(1) performance statistics is a kind of long-time, a kind of statistical function of periodic duty in other words conj.or perhaps, in a period of time, switch success rate between statistical system or how many mortalitys is, this statistics itself is just very coarse, and this function is the statistical history data, can not carry out anomaly analysis to switching the reason of going into failure between system.If improve the precision of performance statistics, increase switching the statistics of going into failure cause between system, will certainly cause the appearance of mass data, influential to regular traffic.

(2) the whole network tracking is a kind of real-time tracking, need all will follow the tracks of by special third party's instrument at all interfaces, and this tracking can produce lot of data.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, especially if follow the tracks of the message of Access Network part.How obtaining Useful Information from a large amount of tracking messages, workload is very big.

(3) the general concern of alarm method all is equipment fault, fewer to the concern of user's fault.Break down owing to wireless reason causes switching such as the user, in alarm, can't embody.So alarm can not solve the problem that occurs in the handoff procedure basically.

Summary of the invention

The invention provides reporting method for switching fault between a kind of system.When solving in the prior art between generation systems switch failure, network management system can not in time, accurately, intactly be obtained the problem of fault in-situ parameter information.

The inventive method is applied to the switching to the 3G system from the 2G system, and this method comprises: set up switch failure parameter information collection between a system, be used to be provided with that switch failure reports parameter item between system, when carrying out switching between system, carry out following steps:

The fault-signal that handoff procedure and receiving system are sent when handoff failure between A, monitoring system;

The switch failure parameter information is concentrated and is required the parameter item that reports between B, the failure cause inquiry system that indicates according to described fault-signal;

The described parameter item that C, basis inquire obtains corresponding parameters value and Write fault reporting message from system;

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

Switch failure parameter information collection comprises between described system:

User profile part, RAB (RAB) message part, cell information part and failure cause part.

Comprise the international mobile subscriber identification code (IMSI) that switches UE in the described user profile part.

At least comprise following parameter in the described RAB message part:

The time of type of service, descending maximal bit (BIT) speed, up maximum BIT speed, RAB sign and RAB foundation/modification.

Comprise radio network controller (RNC) Internal failure information, IUB interface failure information, UU interface failure information, IU interface failure information and IUR interface failure information one of them or its combination in the described failure cause part.

Described RNC Internal failure information comprises sub-district access failure information, illegal RAB parameter information, the inner cause information of RNC, ASNl encoding and decoding error message, storage allocation failure information, UE capabilities limits information and unknown error message one of them or its combination.

Described sub-district access failure information comprises not one of them or its combination of support information, the unavailable information of IUB interface transfer resource and the unavailable information of IUR interface transfer resource of support information, cell ability of small area jam information, cell downlink spreading code.

Described small area jam information comprises emission carrier power and received bandwidth total power.

Described cell downlink spreading code not support information to comprise spreading code and spreading factor be 256 occupancy.

Described cell ability not support information comprises cell capacity information.

The unavailable information of described IUB interface transfer resource comprises up IUB port band width and descending IUB port band width.

The unavailable information of described IUR interface transfer resource comprises up IUR port band width and descending IUR port band width.

Described ASNl encoding and decoding error message comprises transfer syntax error reason, abstract syntax error reason and logic error reason one of them or its combination.

Described UE capabilities limits information comprises not one of them or its combination of support information and UE Radio Link control (RLC) limited ability information of support information, UE transmission channel ability of UE physical channel ability.

Described UE physical channel ability not support information comprises FDD down physical channel ability information and FDD uplink physical channel ability information;

Described FDD down physical channel ability information comprises the greatest physical channel bit number of reception;

Described FDD uplink physical channel ability information comprises the maximum number bits of per 10 milliseconds of DPDCH Channel Transmission.

Described UE transmission channel ability not support information comprises descending transmission channel ability information and uplink transport channel ability information;

Described descending transmission channel ability information comprises the maximum number of the maximum number bits that can receive, the maximum convolution code that can receive, maximum transmitted channel multiplexing number, receptible maximum transmitted piece number, transformat combination (TFC) and the maximum number of transformat (TF);

Described uplink transport channel ability information comprises the maximum number bits that can receive, the maximum convolution code that can receive, maximum transmitted channel multiplexing number, receptible maximum transmitted piece number, the maximum number of TFC and the maximum number of TF.

Also comprise the maximum Turbo code that can receive respectively in described descending transmission channel ability information and the described uplink transport channel ability information.

Described UE RLC limited ability information comprises time window maximum and maximum affirmation mode (AM) number of entities under RLC AM pattern lower bumper total length, the RLC AM pattern.

Described IUB interface failure information comprises Radio Link (RL) and sets up failure or unknown error message.

Described RL sets up failure information and comprises that RL sets up failure reason value and/or RL sets up time-out information.

Described RL sets up failure reason value and comprises wireless network layer error reason value, transport layer error reason value, protocol error cause value and other mixing error reason values.

Described UU interface failure information comprises UE migration to be finished time-out information, UE and reports the migration information failure information, waits for that UE reports migration information time-out information and unknown message one of them or its combination.

Described UE reports the migration information failure information to comprise and reports the migration information failure cause.

Described IU interface failure information comprises migration failure reason value or unknown error message.

IUR interface failure information comprises unknown error message.

Also comprise the predefine cell in the described fault reporting message, whether record UE has adopted pre-configured and default configuration.

The switch failure parameter information concentrates step by step that switch failure reports parameter item between the described system of classification setting between described system.

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:

(1) the present invention is by being provided with the complete fault agreement of a cover, the fault parameter information set that in this fault agreement, should report during handoff failure between define system, and corresponding fault reporting message, when between generation systems during switch failure, failure cause according to System Reports, inquire about the fault parameter information set that defines in this fault agreement, obtain the corresponding parameter item that reports; And obtain the parameter value of current time, notify at once to network management center by the fault reporting message; Network management center is determined failure cause, thereby is instructed the network optimization according to reporting parameter value to carry out the system exception analysis.

(2) in fault agreement of the present invention, the parameter that different failure causes is related is classified, and adopt hierarchical relationship to manage; System is according to the concrete reason of this handoff failure, can conveniently inquire the concrete parameter that such fault should report in the fault agreement, those related parameter values are reported, and the parameter information of having avoided a large amount of and failure cause not being had direct relation reports network management center; Thereby solved in the prior art because reporting of a large amount of statisticss influences the problem of regular traffic.

(3) because in fault of the present invention association justice, therefore the parameter information that clear and definite different failure cause correspondence reports, after network management center is received the fault reporting message, by this message is resolved, gets access to the corresponding parameter that reports; Report parameter just can corresponding determine concrete failure cause according to these, need from a large amount of tracking messages, to obtain useful information the problem that workload is big thereby solved in the prior art.

(4) in the fault agreement of the present invention, carried out comprehensive statistics classification, conveniently oriented concrete failure cause switching involved various network elements, interface and link parameter between system.

Description of drawings

Fig. 1 is the UTRAN schematic network structure;

Fig. 2 goes into flow chart for switching between the circuit domain system;

Fig. 3 goes into flow chart for switching between grouping domain system;

Fig. 4 is the inventive method flow chart.

Embodiment

Fig. 2 goes into flow chart for switching between the circuit domain system, comprises following signaling process:

When 1, GSM BSS decision was carried out switching between system on based measurement, BSC sent handoff request (Handover Required) message and gives GSM MSC, and requiring method, system is that switching is ready between system;

2, GSM MSC transmits this request and gives WCDMA CN (sending PrepareHandover by MAP/E message);

3, WCDMA CN sends out re-positioning request (Relocation Request) to RNC;

4, WCDMA UTRAN is that RNC responded re-positioning request acknowledge message (Relocation Request Ack) and gives WCDMA CN after switching was ready to resource between system;

5, WCDMA CN sends MAP/E message and prepares handoff response (Prepare HandoverResponse) to GSM MSC;

6, GSM MSC is by sending the initial request of switching command (Handover Command) acknowledgement messaging BSC;

7, by already present wireless connections, BSC sends to portable terminal (MS) and switches to UTRAN system command Inter-System to UTRAN Handover Command) message, require MS to carry out switching between system from GSM to WCDMA;

8-10, MS carry out the switching (direct-cut operation) to WCDMA from GSM, after switching is finished, MS sends switching and finishes (Handover Complete) message to RNC, and notice RNC switching is finished, and RNC sends reorientation and finishes (Relocation Complete) message to WCDMA CN;

11, when detect MS in the WCDMA coverage after, WCDMA CN sends end signal request (Send End Signal Request) message and gives GSM MSC, notice GSM MSC switches and finishes, and can discharge the GSM Internet resources that this MS takies;

12-14, GSM MSC send out clear command (Clear Command) and give BSC, and the BSC before notice is switched discharges related resource; After the release of relevant bearer resource was finished among the GSM BSS, GSM MSC echoed to WCDMA CN and answers, and the hand off signaling flow process finishes.

Fig. 3 goes into flow chart for switching between grouping domain system, comprises following signaling step:

1, switches between MS or BSS decision the carrying out system of packet domain, make MS be cut into a new WCDMA sub-district, stop the transmission of MS and internetwork data simultaneously;

2, MS sends the Routing Area Update request to new 3G-SGSN, and it is that Routing Area Update or associating RA/LA (routing area/location) upgrade or band IMSI (International Mobile Subscriber Identity that updating type (Update Type) indicates; International mobile subscriber identification code) the associating RA/LA that adheres to upgrades; SRNC can add the RAC (Routing Area Code route district sign indicating number) and LAC (the Location Area Code of MS region before the transmission user message is to SGSN; Location Area Code) Routing Area Identifier.

3,3G-SGSN obtains old 2G-SGSN address by the old Routing Area Identifier that obtains from MS, send SGSN context request (SGSN Context Request) message then and give old 2G-SGSN, in the hope of MM (mobile management) context and the PDP(Packet Data Protocol that obtains this user; Data pack protocol) context; P-TMSI (the PS Temporary MobileSubscriber IdentitiesPS domain temporary mobile subscriber identification code) signature of old 2G-SGSN checking MS, if P-TMSI signature is effective or the 3G-SGSN indication was carried out authentication to MS, 2G-SGSN starts a timer;

4, old 2G-SGSN returns SGSN context response information (SGSN Context Response), wherein comprises MM Context and PDP Contexts;

5, initiate a safe procedures;

6,3G-SGSN sends SGSN context affirmation (SGSN Context Acknowledge) message and gives 2G-SGSN, makes 2G-SGSN know the related data packets of the PDP Context that 3G-SGSN can accept to have activated;

7,2G-SGSN duplicates and buffer memory N-PDUs (all protocol Data Units) and begin packet is sent to 3G-SGSN; The N-PDUs that additionally received from GGSN before timer expiry will be replicated and be sent to 3G-SGSN; Behind timer expiry, will not have N-PDUs and send to 3G-SGSN;

8,3G-SGSN sends and upgrades PDP Context request (Update PDP Context Request) message to each relevant GGSN; Each GGSN upgrades its PDP Context and responds and upgrade PDP Context response (Update PDP Context Response) message;

9,3G-SGSN changes by sending renewal GPRS location (Update GPRS Location) message informing attaching position register (HLR) generation SGSN;

10, HLR sends cancellation location (Cancel Location) message and gives old 2G-SGSN; Behind the 2G-SGSN timer expiry, old 2G-SGSN will delete MM context and PDP Context; 2G-SGSN sends cancellation positioning confirmation (Cancel Location Ack) message and responds;

11, HLR sends and inserts user data (Insert Subscriber Data) message to 3G-SGSN; 3G-SGSN sets up the MM context and responds and insert user data affirmation (Insert Subscriber DataAck) message to HLR;

12, the HLR affirmation is revised and is finished, and sends to 3G-SGSN and upgrades GPRS positioning confirmation (UpdateGPRS Location Ack) message;

13 if set up related, Update Type indicates the associating RA/LA renewal that band IMSI adheres to, if perhaps LA changes in Routing Area Update, so new SGSN sends position updating request (LocationUpdate Request) message and gives VLR, notify new VLR to initiate the position and upgrade, VLR creates or upgrades related by preserving SGSN number;

If the user data among 14 VLR is indicated the affirmation of not passing through HLR, VLR will notify HLR, and VLR that the HLR cancellation is old and insertion user data comprise to new VLR:

A. new VLR sends and upgrades location (Update Location) to HLR;

B.HLR is by sending the data among the old VLR of cancellation breath location (Cancel Location) message cancellation to old VLR; Old VLR is with cancellation location (Cancel Location) response;

C.HLR sends and inserts user data (Insert Subscriber Data) to new VLR;

D. new VLR confirms (Insert Subscriber Data Ack) in response to insert user data;

E.HLR gives new VLR in response to upgrade positioning confirmation (Update Location Ack).

15, new VLR distributes a new TMSI to upgrade acceptance (Location UpdateAccept) message informing 3G-SGSN by the position;

16,3G-SGSN verifies MS in new route district, if check that by all 3G-SGSN sets up user's MM context and PDP Context; 3G-SGSN sends Routing Area Update and accepts (Routeing Area Update Accept) message to MS;

17, MS finishes (Routing Area Update Complete) newly assigned PTMSI of message authentication by sending Routing Area Update;

If 18 obtain the affirmation of MS, 3G-SGSN sends the TMSI reorientation and finishes (TMSIReallocation Complete) message to new VLR;

If 19 MS have up data or signaling, will send a service request (ServiceRequest) message and give SGSN; COS indicates the service (data or signaling) of requirement;

If 20 MS have sent service request, 3G-SGSN sends RAB assignment request (RABAssignment Request) message and requires SRNS to set up a RAB; SRNS sends radio bearer and sets up request (Radio Bearer Setup Request) message to MS; MS returns radio bearer and sets up response (Radio Bearer Setup Complete); SRNS sends RAB assignment response (RABAssignment Response) message and gives SGSN; SRNS sends to MS with N-PDUs.

From top message flow as can be seen, triggered between system switch go into flow process after, there are a lot of places all may go wrong in the process of 3G system handles, switch between system and cause RNC to finish, for the fault message that in time occurs in the handoff procedure between reporting system, make things convenient for the system management center to carry out fault location, the invention provides a set of fault agreement, the fault parameter information set and the corresponding fault reporting message that in this fault agreement, should report during handoff failure between define system, when system's handoff failure, the failure cause that indicates in the error message according to System Reports inquires the fault parameter information set that defines in the fault agreement and requires the relevant parameter item that reports; A parameter current value that gets parms; Become the fault reporting message to send to network management center by the format combination of arranging the parameter value that obtains.

Concentrated each parameter item that comprises of the fault parameter information of fault protocol definition of the present invention and hierarchical relationship each other thereof, to shown in the table 13, wherein symbol description is as follows in the table as following table 1:

MP: the expression respective items is an essential option;

OP: the expression respective items is an option;

The data type (enumerating) that the ENUMRATE:3GPP agreement is used;

The data type (integer) that the INTEGER:3GPP agreement is used;

The data type (Bit String) that BIT STRING:3GPP agreement is used;

Multi: as be the restriction of its array number of array type element representation.

Wherein, the fault parameter information summary table that table 1 reports for fault protocol requirement provided by the invention, indicate the cell that should comprise in the fault reporting message, described in the correspondence table of indicating in the concrete structure of each cell " type and parameter " list item in table 1, the concrete structure of table 1-table 13 is as follows:

Table 1

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and reference (type and parameter)	Syntactic description (Semantics description)
					Type of message (Message Type)	MP		Message Type	Error message can be with the form output of message, and the effect of type of message is this message of sign.
UE message part (UE information elements)				Be used to identify the UE of failure.
					International mobile subscriber identification code sign indicating number (IMSI)	MP		IMSI is referring to table 2	Be used for UE of unique sign.
RAB message part (RAB Information elements)				UE is moving when being used to be recorded in failure business and service parameter.
					RAB information (RAB information)	MP		RAB list information (RAB List Information) is referring to table 3
Predefine message part (Pre-configuration Information elements)				Be used to write down UE and whether adopted pre-configured and default configuration.
					Select predefined pattern (CHOICE Pre-configuration mode)
＞predetermined configuration (Predefine Configuration)	OP		Predetermined configuration ID (Predefined configuration identity) is referring to table 4
					＞default configuration (Default Configuration)	OP		Default configuration ID (Default configuration identiyt) is referring to table 5
Cell information part (Cell information elements)				Be used to write down the 3G sub-district that UE will move into

Target cell ID (Target Cell identity)	MP		BIT STRING(28)
					Failure information (Failure information elements)				Write down the mistake of the sub-district failure of moving into
Switch to go into to UTRAN failure cause (Handover to UTRAN Failure Cause)	MP		Referring to table 6

In following each table of last table neutralization, "＞" and "＞＞" and "＞＞＞" is in order to represent each parameter hierarchical relationship each other, "＞" expression last layer level parameter wherein, "＞＞" expression subordinate's a time level parameter, "＞＞＞" expression orlop parameter.

Table 2

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics description)
					International mobile subscriber identification service codes (IMSI)	MP	6to21		First cell comprises an IMSI numeral, and second cell comprises the 2nd IMSI numeral, by that analogy.Though only using 15 numerals usually uses for this IE, but kept longer length and supported following expansion. (The first element contains the first IMSI digit, the second element the second IMSI digit and so on. Although normally up to 15 digits are used for this IE, a bigger length is used to support future extension.)
＞IMSI numeral (IMSI digit)	MP		INTEGER (0..9)

Table 3

Message part/information sets title (IE/Group Name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics description)
					RABs information list (RABs Information List)		1～255		The maximum number code value is 256 (Maximum no. of RABs for one UE.Value is 256)
＞type of service (Traffic Class)	MP		ENUMERATED ((session (conversational), stream (streaming), mutual (interactive), background (background) ...)
					＞CNID(CN Information identity)	OP		CN domain identifier (CN Domain identity)
＞descending maximum BIT speed (DL Maximum Bit Rate)	MP		INTEGER(1..16,000,000)
					＞up maximum BIT speed (UL Maximum Bit Rate)	MP		INTEGER(1..16,000,000)
＞up assurance BIT speed (UL Guaranteed Bit Rate)	OP		INTEGER(0..16,000,000)

＞descending guarantee BIT speed (DL Guaranteed Bit Rate)	OP		INTEGER(0..16,000,000)
					＞RAB identifies (RAB ID)	MP		BIT STRING(8)
＞RAB sets up or modification time (RAB To Be Setup Or Modified Time)	MP		BIT STRING(32)	(date: hour: minute: second)

Table 4

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics description)
					The pre-configured sign of radio layer (Predefined radio configuration identity)	MP		Integer(0..15)

Table 5

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics description)	Version (Version)
						Default configuration sign (Default configuration identity)	MP		Integer(0..10
11，12)		REL-4

Table 6

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics description)
					Select reason group (CHOICE Cause Group) according to reason	MP
The inner reason (RNC Inner Failure Choice) of＞RNC
					＞＞sub-district access failure (Call Admission Failure)	OP		Referring to table 7
The RAB parameter of＞＞illegal (Invalid RAB parameter)	OP
					＞＞inner reason (Inner Cause)	OP		Inner reason
＞＞ASNl encoding and decoding mistake (ASNl Error Cause)			ENUMERATED (transfer syntax mistake (Transfer Syntax Error), abstract syntax mistake (Abstract Syntax Error), logic error (Logical Error))

＞＞storage allocation failure (Allocation Memory Failure)	OP
					＞＞UE capabilities limits (UE capability limited)
The UE of＞＞＞physical channel ability is not supported (UE physical channel capability not supported)	OP		UE physical channel ability (UE Physical channel capability) is referring to table 8
					The UE of＞＞＞transmission channel ability is not supported (UE Transport channel capability not supported)	OP		UE transmission channel ability (UE transport channel capability) is referring to table 9	The UE of＞＞＞transmission channel ability is not supported (UE Transport channel capability not supported)
The UE RLC of＞＞＞limited ability (UE RLC capability limited)	OP		RE RLC ability (UE RLC capability) is referring to table 10	The UE RLC of＞＞＞limited ability (UE RLC capability limited)
					＞＞unknown error (Unspecified)	OP
＞IUB interface error (IUB Interface Failure Choice)
					＞＞RL sets up failure (NBAP RL Setup Failure)	OP
The RL of＞＞＞sets up failure cause (RL Setup Failure cause)			RL sets up failure cause (RL Setup Failure cause) referring to table 11
					The RL of＞＞＞sets up overtime (RL Setup Timer Expire)
＞＞unknown error (Unspecified)	OP
					(UU Interface Failure Choice) selected in the failure of＞UU interface
＞＞switch to UTRAN finishes overtime (Handover To UTRAN Complete Timer Expire)	OP
					＞＞UE reports UTRAN migration failure (UTRAN Mobility Info Failure)	OP
＞＞＞failure cause (UTRAN Mobility Info Failure Cause)	MP		UU interface failure cause (UU Interface Failure Cause) is referring to table 12	＞＞＞failure cause (UTRAN Mobility Info Failure Cause)
					＞＞UE reports UTRAN migration overtime (UTRAN Mobility Info Timer Expire)	OP
＞＞unknown error (Unspecified)	OP
					(IU Interface Failure Choice) selected in the failure of＞IU interface	OP
＞＞migration failure cause (Relocation Failure	OP

Cause)
					＞＞unknown error (Unspecified)	OP
＞IUR interface error is selected (IUR Interface Failure Choice)	OP
					＞＞unknown error (Unspecified)	OP

Table 7

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics description)
					Call out access failure (Call Admission Failure)
Select (CHOICE)
					＞small area jam (Cell Congestion)	OP
＞＞emission carrier power (Transmitted Carrier Power Value)	MP		INTEGER(0.100)
					＞＞received bandwidth total power (Received Total Wide Band Power Value)	MP		INTEGER(0..621)
＞cell downlink spreading code is not supported (Cell DL SF not supported)	OP
					＞＞spreading code (Spreading Factor)	MP		ENUMERATED (4，8，16，32，64，128， 256，512)
＞＞spreading factor is 256 occupancy (Occupied Rate of SF=256)	MP		INTEGER(0..100)
					＞cell ability is not supported (Cell Credit not supported)	OP
＞＞cell capacity information (Credit information)	MP		Cell capacity information is referring to table 13
					＞IUB interface transfer resource unavailable (IUB Transport resource unavailable)	OP
＞＞up IUB port band width (UL IUB bandwidth)	MP		INTEGER(0..65535)	Unit: byte
					＞＞descending IUB port band width (DL IUB bandwidth)	MP		INTEGER(0..65535)	Unit: byte
＞IUR interface transfer resource unavailable (IUR Transport resource unavailable)	OP
					＞＞up IUR port band width (UL IUR bandwidth)	MP		INTEGER(0..65535)	Unit: byte
＞＞descending IUR port band width (DL IUR bandwidth)	MP		NTEGER(0..65535)	Unit: byte

Table 8

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and Reference)	Syntactic description (Semantics description)
					FDD down physical channel ability (FDD downlink physical channel capability)
The non-physical channel bit number of＞receptible maximum (Max no physical channel bits received)	MP		INTEGER (1200，2400，3600，4800，7200， 9600，14400，19200，28800，38400， 48000，57600，67200，76800)
					FDD uplink physical channel ability (FDD uplink physical channel capability)
The maximum number bits of＞per 10 milliseconds of DPDCH Channel Transmission (Maximum number of DPDCH bits transmitted per 10ms)	MP		INTEGER(600，1200，2400，4800. 9600，19200.28800，38400，48000， 57600)

Table 9

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and Reference)	Syntactic description (Semantics description)
					Descending transmission channel ability information (Downlink transport channel capability information elements)
The maximum bit number (Max Number of bits received) that can receive	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
					The maximum convolution code (Max convolutionally coded bits received) that can receive	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
The maximum Turbo code (Max turbo coded bits received) that can receive	OP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
					Maximum transmitted channel multiplexing number (Maximum number of simultaneous transport channels)	MP		INTEGER(4，8，16，32)
Receptible maximum transmitted piece number (Max Number of received transport blocks)	MP		INTEGER(4，8，16，32，48，64， 96，128，256，512)
					The maximum number of TFC (Maximum number of TFC)	MP		INTEGER(16，32，48，64，96， 128，256，512，1024)
The maximum number of TF (Maximum number of TF)	MP		INTEGER(32，64，128，256， 512，1024)
					Uplink transport channel ability (Uplink transport channel capability information elements)
The maximum bit number (Max Number of bits transmitted) that can receive	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)

The maximum convolution code (Max convolutionally coded bits transmitted) that can receive	MP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
					The maximum Turbo code (Max turbo coded bits transmitted) that can receive	OP		INTEGER(640，1280，2560， 3840，5120，6400，7680，8960， 10240，20480，40960，81920， 163840)
Maximum transmitted channel multiplexing number (Maximum number of simultaneous transport channels)	MP		INTEGER(4，8，16，32)
					Receptible maximum transmitted piece number (Max Number of transmitted transport blocks)	MP		INTEGER(4，8，16，32，48，64， 96，128，256，512)
The maximum number of TFC (Maximum number of TFC)	MP		INTEGER(16，32，48，64，96， 128，256，512，1024)
					The maximum number of TF (Maximum number of TF)	MP		INTEGER(32，64，128，256， 512，1024)

Table 10

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and Reference)	Syntactic description (Semantics description)
					Buffer total length under the RLC AM pattern (Total RLC AM buffer size)	MP		INTEGER (10，50，100，15 0，500，1000)
Time window maximum under the RLC AM pattern (Maximum RLC AM Window Size)	MP		INTEGER(20 47，4095)
					Maximum AM number of entities (Maximum number of AM entities)	MP		INTEGER (4，5，6，8，16，30 )

Table 11

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics Description)
					Select reason group (CHOICE Cause Group)	M
＞wireless network layer (Radio Network Layer)
					＞＞wireless network layer mistake (Padio Network Layer Cause)	M		ENUMERATED (the C-ID of cited the unknown (unknown C-ID), sub-district unavailable (Cell not available), power level is not supported (Power level not supported), DL radio resource unavailable (DL radio resources not available), UL radio resource unavailable (UL radio resources not available), RL be activated/distribute (RL Already Activated/allocated), Node B resource unavailable (Node B Resources Unavailable), unit of measurement or measures (measurement) not by target support (Measurement not supported for the object), resource is in conjunction with unavailable (Combining Resources not available), the configuration of being asked is not supported (Requested configuration not supported), synchronization failure (Synchronization failure), the prioritised transmission channel is established (Priority transport channel established), rising of SIB in the Node B is not supported (SIB Origination in Node B not Supported), the transmitter of being asked (Tx) hierarchical pattern is not supported (Requested Tx Diversity Mode not supported), unspecified (Unspecified), BCCH scheduling mistake (BCCH scheduling error), unit of account or measures (measurement) temporarily unavailable (Measurement Temporarily not Available), invalid CM is provided with, reshuffle CFN and do not finish (Invalid CM Setting, Reconfiguration CFN not elapsed), the quantity of DL code is not supported (Number of DL codes not supported), S-CPICH is not supported (S-CPICH not supported), in conjunction with not being supported (Combining not supported), UL SF is not supported (UL SF not supported), DL SF is not supported (DL SF not supponed), public transmission channel kinds is not supported (Common Transport Channel Type not supponed), the dedicated transmission channel type is not supported (Dedicated Transport Channel Type not supported), the downlink sharied signal channel type is not supported (Downlink Shared Channel Type not supported), and the uplink shared channel type is not supported (Uplink

			Shared Channel Type not supported), CM is not supported (CM not supported), the Tx diversity no longer is supported (Tx diversity no longer supported), unknown home cell ID (Unknown Local Cell ID), ..., the quantity of UL code is not supported (Number of UL codes not supported), information temporarily unavailable (Information temporarily not available), the information supply is not by target support (Information Proyision not supported for the object), the sub-district is not supported synchronously, (Cell Synchronisation not supported) synchronous adjustment in sub-district is not supported (Cell Synchronisation Adjustment not supported), the change of DPC pattern is not supported (DPC Mode Change not Supported), IPDL be activated (IPDL already activated), IPDL is not supported (IPDL not supported), IPDL parameter unavailable (IPDL parameters not available), frequency acquisition is not supported (Frequency Acquisition not supported), the power-balance state is not by compatible (Power Balancing status not compatible), the bearer types of being asked is arranged again and is not supported (Requested type of Bearer Re-arrangement not supported), signaling bear is arranged again and is not supported (Signalling Bearer Re-arrangement not supported), needed carrying arrange again (Bearer Re-arrangement needed), activation after the delay is not supported (Delayed Activation not Supported), and RL regularly adjusts and is not supported (RL Timing Adjustment not supported))
					＞transport layer (Transport Layer)
＞＞transport layer mistake (Transport Layer Cause)	M		Cited (transfer resource is unavailable, and is unspecified ...) ENUMERATED (Transport resource unavailable, Unspecified ...)
					＞agreement (Protocol)
＞＞protocol error (Protocol Cause)	M		Cited (Transformational Grammar mistake, extract syntax error (refusal), extract syntax error (ignore and notify), message and receiver state are incompatible, semantic error, unspecified, extract syntax error (by the wrong message that constitutes) ENUMERATED (Transfer syntax error, Abstract syntax error (reject), Abstract syntax error (ignore and notify, Message not compatible with receiver state, Semantic error, Unspecified, Abstract syntax error (falsely constructed

			message)， ...)
					＞Misc
＞＞other mix wrong (Miscellaneous Cause)	M		Cited (control and treatment overload, hard crass, O﹠M interferes, and user platform (plane) is handled inadequate resource, and is unspecified, ...) ENUMERATED (Control processing overload, Hardware failure, O﹠M intervention, Not enough user plane processing resources, Unspecified ..)

Table 12

Message part/information sets title (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Syntactic description (Semantics Description
					Failure cause (Failure cause)	MP		Cited (disposes and is not supported, the physical channel failure, can not reshuffle in the time of compatibility, protocol error, compact model mistake running time, cell update is caused, invalid configuration, configuration not exclusively, unsupported measurement) Enumerated (configuration unsupported, physical channel failure, incompatible simultaneous reconfiguration, protocol error, compressed mode runtime error, cell update occurred, invalid configuration, configuration incomplete, unsupported measurement)	Version 5 (Rel-5)
Protocol error message (Protocol error information)	CV-ProtErr
					＞CHOICE diagnostics type	MP
＞＞protocol error (Protocol error cause)			Cited (ASN.1 foul or code error, type of message does not exist or Pending The Entry Into Force, message and receiver state are incompatible, cell numerical value is unintelligible, cell loss concealment, message expands unintelligible) Enumerated (ASN.1violation 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)	Version 5 (Rel-5)
					The TGPSI that deletes (Deleted TGPSI)	CV- CompModeEr r
＞TGPSI	MP		Integer(1..MaxTGPS)	Version 5 (Rel-5)

Table 13

Message part/information sets fame and gain claims (Information Element/Group name)	Whether need (Need)	Multi	Type and parameter (Type and reference)	Speed (Semantics description) retouched in grammer
					Downstream spread spectrum code (DL Spreading Factor)	MP		ENUMERATED (4，8，16，32，64，128， 256，512)
Up spreading code (UL Spreading Factor)	MP		ENUMERATED (4，8，16，32，64，128， 256，512)
					Home cell ability information (Local Cell Credit Information)	MP
＞descending or whole abilities (DL Or Global Capacity Credit)	MP		INTEGER(0..65535)
					＞uplink capacity (UL Capacity Credit)	OP		INTEGER(0..65535)
Home cell group ability information (Local Cell Group Credit Information)	OP
					＞descending or whole abilities (DL Or Global Capacity Credit)	MP		INTEGER(0..65535)
＞uplink capacity (UL Capacity Credit)	OP		INTEGER(0..65535)

How to use for embodiment explanation below that each parameter list reports failure message in the above-mentioned fault agreement provided by the invention.

Suppose that user's mobile roaming is to when 2G cell covers weak area, may trigger and switch between primary system, handoff failure may occur because Target cell is resource-constrained so, by exporting the relevant information of these failures, can help fault location, so that carry out the network optimization.

Table 14

User ID (IMSI)	460070114001271
		Business is set up information (RAB Information) before the call drop	1
	CS DOMAIN, CONVERSATIONAL UL/DL Bit Rate:12200 UL/DL Guaranteed Bit Rate:4.75K settling time: 2005-06-30 9:28 RABID:l
		Switching target small area information (Cell information elements)	RNC：10，CELLID：109
Failure cause (Failure information elements)
			RNC internal fault: Target cell access failure small area jam: RTWP:403 TCP:90

In the table 14, user ID (IMSI) is 460070114001271;

According to the RAB information that requires in the table 1 to insert, inquiry correspondence table 3 is obtained this professional relevant parameter, is specially:

Use the CS territory, belong to interaction service; On/downlink bit rate is: 12200; And professional settling time etc. information;

Switching to go in the Target cell, inserting the 3G RNC sign (10) of request incision and the sign (109) of Target cell;

In the failure cause that reports, question blank 6, former according to this handoff failure because the failure of Target cell access then inquires corresponding concrete parameter from table 7, comprising:

Failure cause: small area jam;

The currency of received bandwidth total power (RTWP) is 403;

The currency of emission carrier power (TCP) is 90.

Analyze this form and can obtain following information:

The technical staff readily appreciates that from top output parameter, and switching the reason of going into failure between this subsystem is because Target cell load is very heavy, causes the access failure and the handoff failure that causes, therefore, can draw as drawing a conclusion:

1) whether target 3G sub-district is in the center of 2G cell, if, should optimize network so, minimizing with this Target cell as the adjacent area.

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 3G or 2G cell.

3) cell selecting of modifying target sub-district and reselecting parameters are so that make the user's easier gravity treatment free time in this sub-district arrive other adjacent area.

4) whether should be modified to switch between the system of Target cell and start thresholding, reduce to the switching of Target cell.

In sum, the present invention passes through switch failure parameter information collection between define system by a set of fault agreement is set in this fault agreement, the parameter item that switch failure should report between appointing system, and when carrying out switching between system, execution in step comprises as shown in Figure 4:

The fault-signal that handoff procedure and receiving system are sent when handoff failure between step S1, monitoring system;

The switch failure parameter information is concentrated and is required the parameter item that reports between step S2, the failure cause inquiry system that indicates according to described fault-signal;

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

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

The network management center technical staff is according to the failure message orientation problem.

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

1. reporting method for switching fault between a system is applied to the switching to the 3G system from the 2G system, and this method comprises:

Set up switch failure parameter information collection between a system, be used to be provided with that switch failure reports parameter item between system, when carrying out switching between system, carry out following steps:

The fault-signal that handoff procedure and receiving system are sent when handoff failure between A, monitoring system;

The switch failure parameter information is concentrated and is required the parameter item that reports between B, the failure cause inquiry system that indicates according to described fault-signal;

The described parameter item that C, basis inquire obtains corresponding parameters value and Write fault reporting message from system;

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

2. the method for claim 1 is characterized in that, switch failure parameter information collection comprises between described system:

User profile part, RAB RAB message part, cell information part and failure cause part.

3. method as claimed in claim 2 is characterized in that, comprises the international mobile subscriber identification code IMSI that switches UE in the described user profile part.

4. method as claimed in claim 2 is characterized in that, comprises following parameter in the described RAB message part at least:

Type of service, descending maximal bit BIT speed, up maximum BIT speed, RAB sign and RAB foundation/modification time.

5. method as claimed in claim 2, it is characterized in that, comprise radio network controller (RNC) Internal failure information, IUB interface failure information, UU interface failure information, IU interface failure information and IUR interface failure information one of them or its combination in the described failure cause part.

6. method as claimed in claim 5, it is characterized in that described RNC Internal failure information comprises sub-district access failure information, illegal RAB parameter information, the inner cause information of RNC, ASN1 encoding and decoding error message, storage allocation failure information, UE capabilities limits information and unknown error message one of them or its combination.

7. method as claimed in claim 6, it is characterized in that described sub-district access failure information comprises not one of them or its combination of support information, the unavailable information of IUB interface transfer resource and the unavailable information of IUR interface transfer resource of support information, cell ability of small area jam information, cell downlink spreading code.

8. method as claimed in claim 7 is characterized in that, described small area jam information comprises emission carrier power and received bandwidth total power.

9. method as claimed in claim 7 is characterized in that, described cell downlink spreading code not support information to comprise spreading code and spreading factor be 256 occupancy.

10. method as claimed in claim 7 is characterized in that described cell ability not support information comprises cell capacity information.

11. method as claimed in claim 7 is characterized in that, the unavailable information of described IUB interface transfer resource comprises up IUB port band width and descending IUB port band width.

12. method as claimed in claim 7 is characterized in that, the unavailable information of described IUR interface transfer resource comprises up IUR port band width and descending IUR port band width.

13. method as claimed in claim 6 is characterized in that, described ASN1 encoding and decoding error message comprises transfer syntax error reason, abstract syntax error reason and logic error reason one of them or its combination.

14. method as claimed in claim 6 is characterized in that, described UE capabilities limits information comprises not one of them or its combination of support information and UE Radio Link control RLC limited ability information of support information, UE transmission channel ability of UE physical channel ability.

15. method as claimed in claim 14 is characterized in that, described UE physical channel ability not support information comprises FDD down physical channel ability information and FDD uplink physical channel ability information;

Described FDD down physical channel ability information comprises the greatest physical channel bit number of reception;

Described FDD uplink physical channel ability information comprises the maximum number bits of per 10 milliseconds of DPDCH Channel Transmission.

16. method as claimed in claim 14 is characterized in that, described UE transmission channel ability not support information comprises descending transmission channel ability information and uplink transport channel ability information;

Described descending transmission channel ability information comprises the maximum number bits that can receive, the maximum convolution code that can receive, maximum transmitted channel multiplexing number, receptible maximum transmitted piece number, the maximum number of transformat combination TFC and the maximum number of transformat TF;

Described uplink transport channel ability information comprises the maximum number bits that can receive, the maximum convolution code that can receive, maximum transmitted channel multiplexing number, receptible maximum transmitted piece number, the maximum number of TFC and the maximum number of TF.

17. method as claimed in claim 16 is characterized in that, also comprises the maximum Turbo code that can receive respectively in described descending transmission channel ability information and the described uplink transport channel ability information.

18. method as claimed in claim 14 is characterized in that, described UE RLC limited ability information comprises time window maximum and maximum affirmation mode AM number of entities under RLC AM pattern lower bumper total length, the RLC AM pattern.

19. method as claimed in claim 5 is characterized in that, described IUB interface failure information comprises Radio Link RL and sets up failure or unknown error message.

20. method as claimed in claim 19 is characterized in that, described RL sets up failure information and comprises that RL sets up failure reason value and/or RL sets up time-out information.

21. method as claimed in claim 20 is characterized in that, described RL sets up failure reason value and comprises wireless network layer error reason value, transport layer error reason value, protocol error cause value and other mixing error reason values.

22. method as claimed in claim 5 is characterized in that, described UU interface failure information comprises UE migration to be finished time-out information, UE and reports the migration information failure information, waits for that UE reports migration information time-out information and unknown message one of them or its combination.

23. method as claimed in claim 22 is characterized in that, described UE reports the migration information failure information to comprise and reports the migration information failure cause.

24. method as claimed in claim 5 is characterized in that, described IU interface failure information comprises migration failure reason value or unknown error message.

25. method as claimed in claim 5 is characterized in that, IUR interface failure information comprises unknown error message.

26. method as claimed in claim 2 is characterized in that, also comprises the predefine cell in the described fault reporting message, whether record UE has adopted pre-configured and default configuration.

27. the method for claim 1 is characterized in that, the switch failure parameter information concentrates step by step that switch failure reports parameter item between the described system of classification setting between described system.

28. method as claimed in claim 27 is characterized in that, carries the current cell that reports parameter value according to parameter item settings at different levels in the described fault reporting message.

29. method as claimed in claim 28 is characterized in that, also comprises in the described fault reporting message: the cell that carries the type of message sign.

30. as claim 28 or 29 described methods, it is characterized in that described method also comprises: described network management center receives described fault reporting message and extracting parameter value from each cell.

Images