CN100396136C - Method for reporting fault in 3-to-2G system switching-over course - Google Patents

Abstract

The present invention discloses a method for reporting a failure in a switching process from a third generation communication system to a second generation communication system. The reporting method comprises the following steps; the failure in the switching process is monitored; if the failure is monitored, failure site information is captured according to content of a failure parameter information set, and the failure site information is organized into a failure reporting message, then the failure reporting message is sent to a network management center; otherwise, the failure in the switching process is continued with monitoring. Because failure appeared site information is recorded when the failure occurs, after the failure appeared site information is sent to the network management system, fundamental reasons that the failure occurs in a calling process can be effectively discovered by analyzing failure reasons and associated information in the inter-system switching process in the network management center by the network management system; thereby, the failure can be solved by corresponding means.

Description

A kind of from 3G to the 2G net system switching process the report method of fault

Technical field

The present invention relates to a kind of communication technology, relate in particular to a kind of from 3G (third generation) communication system to 2G (second generation) communication system handoff procedure the report method of fault.

Background technology

The covering of 2G communication network such as GSM/GPRS (mobile communication system/general grouping wireless service system) network is more complete at present, and at initial stage that 3G network such as WCDMA (Wideband Code Division Multiple Access (WCDMA)) put it into commercial operation, operator considers based on number one, can not cover on a large scale, therefore the situation that in one period, is certainly existing WCDMA network and GSM/GPRS network and depositing.In order to ensure 3G communication system such as WCDMA to the switching between 2G communication system such as the GSM/GPRS.Need in time to obtain on-site parameters, the especially on-site parameters when breaking down in the handoff procedure,, network configuration is adjusted and optimized so that determine failure cause in time according to these on-site parameters.

In the prior art, in order to determine failure cause and optimization network configuration, take following method:

1) performance statistics function.Performance statistics is a quality of weighing current network by statistical items crucial in the statistics network, this method is to add up to switch between system in a specific measuring period success/frequency of failure, and this statistical value fed back to network management system, comprehensively analyze by network management system, instruct dilatation and problem to solve existing network by analysis result;

Yet, because performance accounting method is a kind of statistical function of periodic duty, in a period of time, switches between statistical system and success rate or how many mortalitys is, the reason to fault does not reflect.If improve the granularity of performance statistics, increase switching the statistics that failure cause between system, will certainly cause the appearance of mass data, influential to regular traffic.

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

Yet, because the whole network tracking is a kind of real-time tracking, need all to follow the tracks of, because normal and fault are not distinguished in this tracking, so can produce a large amount of tracking messages at all interfaces by third party's instrument.Because the basic reason of various faults is not quite similar, how from a large amount of tracking messages, to obtain the useful information of this time of location fault, will have great workload.Signaling tracing also needs very rich experience in addition, requires to find fault basic reason implicit in the message observantly, and the threshold of Fen Xiing is higher like this, is not easy to promote in the attendant.

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

Yet, all be equipment fault owing to what alarm in general concern, fewer to the concern of user's fault.When breaking down owing to wireless reason causes switching, in alarm, be to embody such as the user.And can only reflect certain fault point in three of publishing picture at most, can not fully reflect out of order because of.So alarm can not reflect the fault that occurs in the switching between system basically.

In sum, because above-mentioned prior art all exists such or such shortcoming, make when determining failure cause, to seem very inconvenient, even can not determine failure cause.

Summary of the invention

Target of the present invention provided a kind of from the 3G communication system to 2G communication system handoff procedure the report method of fault, can conveniently determine failure cause according to the content that reports.

The invention provides a kind of from third generation communication system to second generation communication system handoff procedure the report method of fault, comprising: set up switch failure parameter information collection, be used to be provided with switch failure and report parameter item,, may further comprise the steps when in handoff procedure:

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

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

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

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

Described switch failure parameter information collection comprises terminal equipment message part, RAB message part, optimum subdistrict message part, active set cell message part, isosystem measurement message part, fault message part and extend information part.

Described terminal equipment message part comprises that logic moves service codes information.

Described RAB message part comprises type of service, down link Maximum Bit Rate, up link Maximum Bit Rate and radio bearer sign.

Described RAB message part comprises that also core network domain sign, down link guarantee that bit rate and up link guarantee bit rate combination in any wherein.

Described optimum subdistrict message part and active set cell message part comprise cell ID respectively.

Described optimum subdistrict message part and active set cell message part also comprise the signal to noise ratio of Common Pilot Channel and/or the sign indicating number received power of Common Pilot Channel respectively.

Described isosystem measurement message part comprises handover trigger reason between GSM cell information, switching target GSM cell information and system.

Described GSM cell information and switching target GSM cell information comprise Location Area Identification, Network Color Code, BCC, different system cell sign, different system cell frequency combination in any wherein respectively.

Described Location Area Identification comprises Mobile Network Code, Mobile Country Code MCC and Location Area Code.

Described GSM cell information and switching target GSM cell information also comprise respectively: the BSIC combination in any wherein of GSM carrier wave RSSI, the BSIC of verification, non-verification.

The handover trigger reason comprises triggering selection and isosystem measurement Report Type between described system.

Between described system the handover trigger reason also comprise based on cover, based on load, based on the reason combination in any wherein of blind switching, the directed retry of different system and directed retry.

Described isosystem measurement Report Type comprises that switching outgoing event between measurement report type and system identifies.

Described isosystem measurement Report Type also comprises preiodic type and/or event mode.

Described fault message partly comprises selects the reason group.

Described fault message part also comprises RNC internal fault, IUB interface fault, UU interface fault and IU interface fault combination in any wherein.

Described switch failure parameter information is concentrated the parameter item of the described inquiry of classification setting step by step.

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.

Owing to when fault takes place, write down the field data that breaks down, and after it is fed back to network management system, by network management system to wherein between contained system failure cause in the handoff procedure and relevant information analyze, can find effectively root that fault in the calling procedure occurs because of, thereby can solve fault by corresponding means.

Description of drawings

Fig. 1 is for being switched to the switching flow figure of gsm system by the WCDMA system;

Fig. 2 is for being switched to the switching flow figure of gprs system by the WCDMA system;

Fig. 3 shows the schematic diagram of fault tree;

Fig. 4 shows the flow chart of report method of the present invention.

Embodiment

Understand and realization the present invention the existing embodiments of the invention of describing in conjunction with the accompanying drawings for the ease of persons skilled in the art.

For illustrate of the present invention from the 3G communication system to 2G communication system handoff procedure the report method of fault, at first with UE from 3G such as WCDMA system to 2G such as gsm system or gprs system be example explanation handoff procedure.Only consider the situation of WCDMA and GSM core net in the handoff procedure below.

At first the handoff procedure of UE (subscriber equipment) from the WCDMA system to gsm system described with reference to Fig. 1.

Step 1:RNC (radio network controller) finishes the switch decision algorithm according to the attribute of current area, adjacent cell configuration attribute with to information such as UE measurement results.When RNC judgement UE should carry out the switching of different system, send Relocation Required (re-positioning request) message to CN (core net), trigger the once handoff procedure of different system;

Step 2, CN send to this request by the MAP/E interface MSC (mobile switching centre) of gsm system after receiving this message;

Step 3,4 is the conventional handoff procedure among the GSM, omits its explanation at this;

Step 5, by the MAP/E interface, MSC returns Prepare Handover Response (preparation handoff response) message to core net, switches between system to be ready to complete;

Step 6, core net are returned Relocation Command (reorientation order) to SRNC (service wireless network controller), show that target GSM BSS (base station sub-system of GSM) distributes Radio Resource and other resources for UE;

Step 7, SRNC send to UE with the information of GSM BSS by Uu interface Handover from UtranCommand (from the order of Utran) message.From then on UE explains the radio channel resource information (frequency/timeslot number/initial power or the like) of GSM/BSS for its distribution in the message, inserts different system cell;

Step 8,9,10 is the conventional handoff procedure among the GSM, omits its explanation at this;

Step 11, MSC detect UE and have inserted GSM, then send SendEnd Signal Request (sending the end signal request) message by the MAP/E interface to CN;

Step 12,13, when UE inserts after different system cell finishes, CN can send Iu ReleaseCommand (IU release command) and give SRNC.SRNC begins to discharge UE context, Radio Resource and the related resource of this side.(annotate: this moment, RRC herein (Radio Resource control) discharges flow process need not discharge UE again because UE has been moved to GSM);

Step 14, at the MAP/E interface, CN sends Send End Signal Response (sending the end signal response) message, switches between system flow process and finish.

Below with reference to the handoff procedure of Fig. 2 description from the WCDMA system to gprs system.

Switch between the system of step 1, MS (travelling carriage) or UTRAN judgement initiation data field, MS is switched in the new sub-district of a GPRS;

Step 2, MS initiate the Routing Area Update request to the SGSN of 2G+3G, updating type will indicate Routing Area Update, perhaps uniting RA/LA upgrades, perhaps the associating RA/LA that adheres to IMSI (global mobile user identification) upgrades, and BSS will receive the band RAC of adding sub-district, place in the message and the cellular global identity (CGI) of LAC before message is delivered to SGSN;

Step 3, if MS is in connection status, then 2G+3G SGSN sends SRSN ContextRequest message to SRNS;

After step 4, SRNS receive this message, beginning buffer memory and stop to send data PDU (protocol Data Unit) to MS, and return SRNS Context Response (sequence number that contains PDP, GTP) to 2G+3G SGSN;

Step 5, execution safe procedures;

Step 6, if MS is in PMM-CONNECTED (connection status) state, then 2G+3G SGSN sends data forwarding order (Data Forward Command) to SRNS, shows that 2G+3G SGSN is ready to, and can receive packet;

Step 7, SRNS send data in buffer PDU to 2G+3G SGSN;

Step 8,2G+3G SGSN will send Iu Release Command message to RNC and give SRNS, and SRNS responds by Iu Release Complete message after data forwarding regularly finishes;

If step 9 association will be established, so new 2G SGSN sends Location Update Request (reorientation update request) and gives VLR (VLR Visitor Location Register).Notify new MSC/VLR to initiate the position and upgrade, VLR can create or upgrades association by preserving the SGSN number;

If the user data among step 10 VLR is indicated the affirmation of not passing through HLR, VLR will notify HLR.VLR that the HLR cancellation is old and insertion user data are to new VLR, and step 10 comprises following six steps:

A. new VLR sends Update Location (upgrading the location) and gives HLR;

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

C. old VLR responds with Cancel Location;

D.HLR sends Insert Subscriber Data Ack to new VLR;

E. new VLR with Insert Subscriber Data Ack in response;

F.HLR gives new VLR in response with Update Location Ack.

Step 11, new VLR are MS distribution T MSI, send Location Update Accep notice 2G+3GSGSN;

Step 12,2G+3G SGSN verify the legitimacy of MS in new route district, if all are checked successfully, 2G+3G SGSN is set up MM (mobile management) context and PDP Context to the user, distribute new PTMSI (packet TMSI), and initiating between MS and 2G+3G SGSN, to set up a logical links, 2G+3G SGSN responds MS Routing Area Update Accept (Routing Area Update acceptance) message;

Step 13, MS are by sending the newly assigned PTMSI of Routing Area Update Complete (Routing Area Update is finished) message authentication, and all successfully send to the data PDU of MS before Routing Area Update is initiated to comprise affirmation;

Step 14,2G+3G SGSN transmission message TMSI ReallocationComplete notice VLR TMSI after obtaining the MS affirmation redistributes and finishes.

Step 15,2G+3G SGSN and BSS carry out BSS Packet Flow Context procedure.

In above-mentioned two flow processs, related to RNC, NodeB and CN three part network elements, and a large amount of communication messages has been arranged between network element, each network element internal is realized comparatively complexity simultaneously, therefore, the factor that relates to when breaking down is many.However, for single network element, when fault takes place, always in the mode of a chain, begin to transmit from producing unusual root (Root Cause), progressively show as Fault (be difficult to or not can be the user discovers) or Failure (for the user discovers).

According to the present invention, for the reason of clear failure, above-mentioned handoff procedure can be divided by level, level is extended to the upper strata from bottom, as shown in Figure 3, and represent with the form of traffic failure tree.For example, at the client layer call drop, can cause by network element RNC at business system layer, can be to cause further in subsystem layer by the signaling plane fault, further between the internal module layer is by system, switch to be out of order and cause, further on OS layer resource, fail, cause sending Handover from Utran Command message failure to UE by the application resource.

In order to obtain fault in-situ information comprehensively, data message related in the handoff procedure is defined as switch failure parameter information collection, and switch failure parameter information collection is divided by level, the concrete division shows this level as table 4 to table 13.

In table 2-13, the title of message part/information sets is shown in first tabulation, and whether this message part of secondary series information representation is essential message part, and its implication is as shown in table 1.The number of this message part is shown in the 3rd tabulation, can be a span, and omitting expression only has one.Type, its span or the reference table of this message part shown in the 4th tabulation.The 5th classifies the implication of this message part as.This information decision by its sub-information of this information is represented in the omission of secondary series, the 4th column information.

Table 1 abbreviation implication table

Abbreviation	Implication
		M	This message part must be comprised in the failure cause record
O	This message part may be comprised in the failure cause record
		C	When condition satisfies, this message part will be comprised in the failure cause record, otherwise this message part will can not be comprised in the failure cause record,

Table 2 fault message body structure

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					Type of message (MessageType)	M		Message Type
UE message part (UE information elements)	M			UE message part (mainly being IMSI)
					RAB message part (RAB Information elements)	M			RAB message part (characteristic of current business)
Best cell message part (BestCell information elements)	M			Best cell message part (current best cell and uplink and downlink signals quality thereof)
					Sub-district message part in the active set (Cell Leg lnformation elements)	M			Sub-district message part in the active set (current active collection sub-district and uplink and downlink signals quality thereof)
Isosystem measurement message part (Inter-Rat measured elements)	M			Isosystem measurement message part (2G cell and signal quality thereof)
					Fault message part (Failure information elements)	M		Referring to table 3	Fault message part (structure is asked for an interview 2.2.2)
Extend information part (Extended inform ation elements)	O			This message part is used to describe the message part of follow-up increase, if the message part of no follow-up increase then need not to be with this message part

Table 3 fault message part (Failure information elements)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					CHOICE Cause Group	M
＞RNC internal fault (RNC Inner Failure Choice)	O			The RNC internal fault
					＞IUB interface fault (IUB Interface Failure Choice)	O			The IUB interface fault
＞UU interface fault (UU Interface Failure Choice)	O			The UU interface fault
					＞IU interface fault (IU Interface Failure Choice)	O			The IU interface fault

Table 2 and table 3 show switch failure parameter information lump body structure of the present invention, as shown in table 2, the structure of this switch failure parameter information collection comprises and contains sub-district message part (current active collection sub-district and uplink and downlink signals quality thereof) in UE message part (mainly being IMSI), RAB message part (characteristic of current business), best cell message part (current best cell and uplink and downlink signals quality thereof), the active set, isosystem measurement message part (2G cell and signal quality thereof), fault message part and expansion.

As shown in table 3, the fault message part-structure adopts the method for dividing by standard interface and network element, be directed to Fig. 1, the part of WCDMA in the flow process among Fig. 2, make mistakes at standard interface (for example: receive that unexpected message (contains the transport layer mistake, user's face mistake etc.), or receive failed message, or the timer expiry that waits for the arrival of news), or RNC internal error (such as message code error when sending, or user's face/signaling plane L2 makes mistakes, or transmission AL makes mistakes, or application memory failure when distributing relevant example resource) time, at this moment fault in-situ information can be pressed the form of switch failure parameter information collection and form the fault reporting message, report to network management center, perhaps export daily record to, so that fault is positioned and handles.

Table 4 to table 13 shows the detailed level structure of fault message body of the present invention.

The detailed structure of table 4 switch failure parameter information collection

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					Message Type	M		Message Type	Selecting type is to switch between system
UE information elements
					IMSI	M		Referring to table 5	The IMSI information of UE
RAB Information elements
					RAB business information (RAB information)	M		RABs Information List (referring to table 6)	Business information among the current WCDMA
Best Cell information elements
					Optimum subdistrict information (Best Cell Information)	M		Cell Information (referring to table 7)	The information of optimum subdistrict
Cell Leg Information elements

Active set cell information (Cell Leg Information)	M	0～6	CelI Information (referring to table 7)	The information of active set cell
					Inter-Rat measured elements
GSM cell information (GSM Cell Information)	M	0～32	GSM Cell Information (referring to table 8)	The information of GSM sub-district (containing a plurality of)
					Purpose GSM cell information (Target GSM Cell Information)	M		GSM Cell Information (referring to table 8)	Switch the information (unique) of purpose GSM sub-district
Handover trigger reason between system (InterRat Handover Trigger)	M		InterRat handover trigger (referring to table 10)	The triggering reason of switching between system
					Failure information elements
Handoff failure reason (Handover From UTRAN Failure Cause)	M		Handover From UTRAN Failure Cause (referring to table 13)	From switching the detailed reason that is out of order between the UTRAN system

The IMSI information of table 5UE

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					IMSI	M	6to 21		The first element contains the first IMSI digit, the second element the second IMSI digit and so on. Although normally upto 15 digits are used for this IE, abigger Iength is used to support future extension. (, not adding explanation) at this because IMSI is the basic conception of mobile communication
＞IMSI digit	M		INTEGER(0.. 9)

Business information among the current WCDMA of table 6 (RABs Information List)

Message part part/information sets title (IE/Group Name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					RABs Information List		1～ maxnoofRA Bs		Maximum no.of RABs for one UE.Value is 256
＞type of service (Traffic Class)	M		ENUMERATED (conversational，streaming， interactive，background，...)	Type of service (session, stream, mutual, background)
					＞CN domain identifier (CN Information identity)	O		CN Domain identity	CN territory ID
＞down link Maximum Bit Rate (DL Maximum Bit Rate)	M		INTEGER(1..16,000,000)	The maximum Bit of DL leads
					＞up link Maximum Bit Rate (UL Maximum Bit Rate)	M		INTEGER(1..16,000,000)	The maximum Bit of UL leads
＞down link guarantees bit rate (DL Guaranteed Bit Rate)	O		INTEGER(0..16,000,000)	DL guarantees that Bit leads
					＞up link guarantees bit rate (UL Guaranteed Bit Rate)	O		INTEGER(0..16,000,000)	UL guarantees that Bit leads
＞service identification (RAB ID)	M		BIT STRING(8)	Traffic ID/wireless access bearing sign

Table 7 cell information (Cell Information)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					Cell ID (Cellidentity)	M		BIT STRING(28)	Sub-district ID
Measurement result for current cell
					The signal to noise ratio of＞Common Pilot Channel (CPICH Ec/N0)	O		INTEGER(0.. 49)	The signal to noise ratio of Common Pilot Channel
The sign indicating number received power of＞Common Pilot Channel (CPICH RSCP)	O		INTEGER(0.. 91)	The sign indicating number received power of Common Pilot Channel

Table 8GSM cell information (GSM Cell Information)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					GSM Cell Information
＞Location Area Identification (Location area identity)	M		Referring to table 9	Location Area Identification
					＞Network Color Code (NCC)	M		INTEGER(0.7)	Network Color Code
＞BCC (BCC)	M		INTEGER(0..7)	BCC
					＞GSM carrier wave RSSI (GSM carrier RSSI)	O		BIT STRING(6)	GSM carrier wave RSSI
＞＞CHOICE BSIC
					＞＞＞Verified BSIC	O
＞＞＞＞inter-RAT cell id	M
					＞＞＞Non verified BSIC	O
The frequency point number (BCcharFCN) of＞＞＞＞this sub-district BCCH channel carrier frequency	M		INTEGER (0..1023)	The frequency point number of this sub-district BCCH channel carrier frequency

Table 9 Location Area Identification (Location Area Identity)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					Location Area Identity
＞Mobile Network Code (MNC)	M			Mobile Network Code
					＞Mobile Country Code MCC (MCC)	M		Inter-Rat Measurement Report type	Mobile Country Code MCC
＞Location Area Code (Location Area Code)	M		INTEGER(1..65535) 0and 65534 is reserved	Location Area Code

Handover trigger information between table 10 system (Inter-Rat handover trigger)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					CHOICE of trigger	M
＞based on covering (Based on Coverage)	O			Based on covering
					＞＞isosystem measurement Report Type (Inter-Rat Measurement Report type)	M		Referring to table 11	The isosystem measurement Report Type
＞based on load (Based on Load)	O			Based on load
					＞based on blind switching (Based on Blind)	O			Based on blind switching
＞different system directed retry (Direct Retry)	O			The directed retry of different system
					The reason of＞＞directed retry (Direct Retry Cause)				The reason of directed retry

Table 11 isosystem measurement Report Type (Inter-Rat Measurement Report type)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					Measurement Report type	M
CHOICE of Report
					＞preiodic type (Periodic)	O			Preiodic type
＞event mode (Event)	O			Event mode
					Switch outgoing event sign (Inter-Rat event identity) between＞＞system	M		Referring to table 12	Switch outgoing event ID between system

Table 12 isosystem measurement event id (Inter-Rat event identity)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					Switch outgoing event sign (Inter-Rat event identity) between system	M		ENUMERAT ED(3a，3b， 3c，3d)	Switch outgoing event ID between system, see 3GPP 25.331 agreements for details

Table 13 fault detail reason (Handover From UTRAN Failure Cause)

Message part part/information sets title (Information Element/Group name)	Need	Multi	Type and reference	Semantics description (Chinese implication)
					CHOICE Cause Group	M
＞RNC Inner Failure Choice	O
					The error reason (Protocol or Unmatched Message Error Cause) that＞＞protocol message or message are incompatible	O			The error reason that protocol message or message are incompatible, relevant with inner realization, specifically do not provide at this
＞＞ASN1 error reason (ASN1 Error Cause)	O		ENUMERATED(Tran sfer Syntax Error， Abstract Syntax Error， Logical Error).	ASN1 error reason (transfer syntax mistake, abstract syntax mistake, logic error)
					＞＞L2 configuration error reason (L2 Configuation Error Cause)	O		L2 Configuration Error Cause	L2 configuration error reason, relevant with inner realization, specifically do not provide at this
＞＞AL configuration error reason (AL Configuration Error Cause)	O		AL Configuration Error Cause	AL configuration error reason, relevant with inner realization, specifically do not provide at this
					＞＞Memory Allocation failure (Allocation Memory Failure)	O			The Memory Allocation failure
＞＞other faults (Unspecified)	O			Other faults
					＞IUB interface fault (IUB Interface Failure Choice)	O			The IUB interface fault does not have the IUB interface fault during owing to switching between system, so slightly
＞UU interface fault (UU Interface Failure Choice)	O			The UU interface fault
					＞＞UU standard interface mistake (UE Inter RAT hahdover failure)	O		UE Inter RAT handover failure	The UU mouth receives the Inter Rat HandOver Failure message that UE sends, and is UU standard interface mistake, and the concrete reason value please see 3GPP 25.331 for details
＞＞other faults (Unspecified)	O			Other faults
					＞IU interface fault (IU Interface Failure Choice)	O			The IU interface fault
Failure cause (Relocation Preparation Failure Cause) is prepared in＞＞reorientation	O		IU Interface Failure Cause	Reloc Prep procedure fault reason is IU standard interface mistake, and the concrete reason value please see 3GPP 25.413 for details

＞＞reorientation order wait timeout (Relocation Command Timer Expire)	O			Wait for Reloc Command message timer expiry
					＞＞IU release command overtime (IU Release Command Timer Expire)	O			Wait for IU Release Command message timer expiry
＞＞other faults (Unspecified)	O			Other faults

Following his-and-hers watches 4 carry out brief description to table 13, and table 4 is the expansion general structure of the switch failure parameter information collection shown in the table 1, below it are successively described.As shown in table 5, described UE message part only comprises IMSI (global mobile user identification) information, and this is an essential option.

As shown in table 6, RAB (RAB) message part comprises four essential options: type of service, DL (down link) Maximum Bit Rate, UL (up link) Maximum Bit Rate and radio bearer sign and three option: CN (core net) domain identifier, DL guarantee that bit rate, UL guarantee bit rate.

As shown in table 7, optimum subdistrict information and active set cell message part comprise an essential option respectively: cell ID, two options: the signal to noise ratio of Common Pilot Channel and sign indicating number received power.

As shown in table 4, isosystem measurement information comprises three essential options: handover trigger reason between GSM cell information, switching target GSM cell information and system.

As shown in table 8, GSM cell information and switching target GSM cell information comprise four essential options respectively: Location Area Identification, Network Color Code, BCC, inter-RAT cell id (different system cell sign), BCCH ARFCN (frequency of different system cell), three options: GSM carrier wave RSSI (signal strength signal intensity that receives indicates), Verified BSIC (BSIC that has verified), Non verified BSIC (not verified BSIC).

As shown in table 9, Location Area Identification comprises three essential options: Mobile Network Code, Mobile Country Code MCC and Location Area Code.

As shown in table 10, the handover trigger reason comprises three essential options between system: triggering selection, isosystem measurement Report Type and following option: based on cover, based on load, based on the reason of blind switching, the directed retry of different system and directed retry.

As shown in table 11, the isosystem measurement Report Type comprises following essential option: switch outgoing event ID and following option between measurement report type, system: preiodic type and event mode.

As shown in table 12, fault message partly comprises an essential option: select reason group and following option: RNC internal fault, IUB interface fault, UU interface fault and IU interface fault.Each option also comprises some projects.

In sum, the present invention has set up fault and has reported agreement, reports in the agreement in fault: at first set up switch failure parameter information collection, set up a set of fault report method then.Described switch failure parameter information collection above in detail, described switch failure parameter information is concentrated classification setting parameter item step by step, describes the fault report method below in detail.

As shown in Figure 4, in step 1, the fault-signal that monitoring handoff procedure and receiving system are sent when handoff failure.

In step 2, the parameter item that the concentrated requirement of failure cause inquiry switch failure information that indicates according to described fault-signal reports.

In step 3, from system, obtain corresponding parameters value and Write fault reporting message according to described parameter item; Carry the current cell and the cell that carries the type of message sign that reports parameter value according to parameter item settings at different levels in the fault reporting message.

In step 4, described fault reporting message is sent to network management center.Network management center receive the fault reporting message and from each cell the extracting parameter value so that fault is positioned.

Like this, owing to when fault takes place, write down the field data that breaks down, and after it is fed back to network management system, by network management system to wherein between contained system failure cause in the handoff procedure and relevant information analyze, as press cause statistics, perhaps the flow according to record carries out flow control etc.Can find the basic reason that fault occurs in the handoff procedure effectively, thereby can solve fault by corresponding means.

According to representation for fault method of the present invention, catching for information about and reporting in the time of fault in the switching flow between system can being taken place, thus can reflect the detailed situation of this calling when fault takes place; Because failure cause of the present invention presses hierarchical organization, thus can the out of order basic reason of clear reflection; In addition, according to the present invention, only output fault in-situ information when fault takes place can significantly reduce output message, is convenient to fault location; In addition, from above-mentioned table 4-13 as can be known, switch failure parameter information collection of the present invention comprises the relevant information of common faults, therefore, need not to depend on other localization methods, but with regard to fault location.

Embodiment 1

Below by an example application of the present invention is described.

Be arranged in the process of the user terminal of WCDMA system in conversation, move to the WCMA network edge, enter the overlay area of GSM network, at this moment if user terminal is found the wireless signal relatively poor (being lower than certain measurement thresholding) in the WCDMA network, and the wireless signal in the network of GSM better (is higher than another and measures thresholding), under the cooperation of network side, process will switch.According to the present invention, if in this handoff procedure, break down, receive Relocation Preparation Failure message as RNC, perhaps wait for the timer expiry of Relocation Command message, or other unexpected messages take place, then RNC can collect fault in-situ information according to fault field information body, and fault field information soma reported to network management center for the fault reporting message, perhaps export switch failure parameter information collection to daily record, then, existing switching flow rollback or termination, and may produce call drop.At this moment, the network manager can be according to switch failure parameter information set content analyzing failure cause, so that fault is handled.Processing procedure is as follows, obtains its fault in-situ information according to IMSI, according to fault in-situ information this fault is handled then.In addition, according to the present invention, when receiving user's complaint, also can handle it according to user's complaint in time, its processing procedure is as follows, phone number (MSISDN just) according to the user finds the IMSI of this user terminal and the time period of customer complaint, then according to IMSI in log record (or the record form of other form, as database) the middle fault message of searching for this user, then this fault message is analyzed, like this, just can be saved the fault location time, as early as possible fault is handled, increased user's satisfaction.Can draw analysis report such as table 14.

Table 14 far

Fault time	09:38:24 on the 30th
		RRC settling time during fault	09:25:12 on the 30th
RRC connection status before the fault	DCH
		User ID (IMSI)	460070114001271
Fault type	Switch between system and failure
		Business is set up information before the call drop	1
	CONVERSATIONAL CS DOMAIN UL/DL Bit Rate：12200 UL/DL Guaranteed Bit Rate：4.75K RABID：2
		Optimum subdistrict information	RNC：10，CELLID：101

	RSCP：-80dbm EcNo：-12db
		Active set cell information	Active set cell 1 information RNC:10, CELLID:109 active set cell 1RSCP-85dbm active set cell 1EcNo-17db active set cell 2 information RNC:10, CEL LID:120 active set cell 2RSCP-89dbm active set cell 2EcNo-15db
The GSM cell information	Sub-district 1 Location Area Code: 9491 Network Color Codes: 0 BCC: the frequency of the different system cell of 0 GSM carrier wave RSSI:-50dbm: 9250 sub-districts, 2 Location Area Codes: 9493 Network Color Codes: 0 BCC: the frequency of the different system cell of 0 GSM carrier wave RSSI:-65dbm: 9300
		Purpose GSM cell information	Sub-district 1 Location Area Code: 9491 Network Color Codes: 0 BCC: the frequency of the different system cell of 0 GSM carrier wave RSSI:-50dbm: 9250
Handover trigger reason between system	Based on covering isosystem measurement Report Type Report Type: event mode different system event ID:3a
		From switching the detailed reason that is out of order between the UTRAN system	Fault type: IU interface fault Reloc Prep procedure fault reason: transport layer reason: Signalling Transport Resource Failure

As can be seen from Table 14:

The time of breaking down in the handoff procedure between system is 09:38:24 on the 30th;

Switch reasons is based on coverage information between system, moves to the GSM network from the edge of WCDMA network, and by relatively EcNo, RSCP and RSSI, at this moment the cell signal of WCDMA network is relatively poor as can be seen, and the cell signal of GSM is better;

Fault has taken place in the IU interface in the handoff procedure between system, and GSM is with signaling transfer resource fault takes place between CN.

Therefore,,, can determine the reason that fault takes place exactly by collecting the content that the switch failure parameter information is concentrated according to the present invention, for follow-up troubleshooting of faults provides strong help, help to analyze root that fault takes place because of.In addition, because the present invention can export when fault takes place, thereby significantly reduced output message stream, improved the accuracy of fault location, reduced the difficulty of fault location, and for the not influence of normal business, if adopt the method for compression in the later stage, the flow of fault output is less, thereby can ignore basically to the influence of business; Because switch failure parameter information collection is with level form performance, institute is so that follow-up processing again (for example add up etc.).

Though described the present invention by embodiment, those of ordinary skills know, without departing from the spirit and substance in the present invention, just can make the present invention that many distortion and variation are arranged, and scope of the present invention is limited to the appended claims.

Claims (21)

1. One kind from third generation communication system to second generation communication system handoff procedure the report method of fault, it is characterized in that, set up switch failure parameter information collection, be used to be provided with switch failure and report parameter item, when in handoff procedure, may further comprise the steps:

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

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

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

   D, described fault reporting message is sent to network management center.
2. 2. report method according to claim 1, it is characterized in that described switch failure parameter information collection comprises terminal equipment message part, RAB message part, optimum subdistrict message part, active set cell message part, isosystem measurement message part, fault message part and extend information part.
3. 3. report method according to claim 2 is characterized in that, described terminal equipment message part comprises global mobile user identification information.
4. 4. report method according to claim 2 is characterized in that, described RAB message part comprises type of service, down link Maximum Bit Rate, up link Maximum Bit Rate and radio bearer sign.
5. 5. report method according to claim 4 is characterized in that, described RAB message part comprises that also core network domain sign, down link guarantee that bit rate and up link guarantee bit rate combination in any wherein.
6. 6. report method according to claim 2 is characterized in that, described optimum subdistrict message part and active set cell message part comprise cell ID respectively.
7. 7. report method according to claim 6 is characterized in that, described optimum subdistrict message part and active set cell message part also comprise the signal to noise ratio of Common Pilot Channel and/or the sign indicating number received power of Common Pilot Channel respectively.
8. 8. report method according to claim 2 is characterized in that, described isosystem measurement message part comprises handover trigger reason between GSM cell information, switching target GSM cell information and system.
9. 9. report method according to claim 8, it is characterized in that described GSM cell information and switching target GSM cell information comprise Location Area Identification, Network Color Code, BCC, different system cell sign, different system cell frequency combination in any wherein respectively.
10. 10. report method according to claim 9 is characterized in that described Location Area Identification comprises Mobile Network Code, Mobile Country Code MCC and Location Area Code.
11. 11. report method according to claim 9 is characterized in that, described GSM cell information and switching target GSM cell information also comprise respectively: the BSIC combination in any wherein of GSM carrier wave RSSI, the BSIC of verification, non-verification.
12. 12. report method according to claim 8 is characterized in that, the handover trigger reason comprises triggering selection and isosystem measurement Report Type between described system.
13. 13. report method according to claim 12, it is characterized in that the handover trigger reason also comprises based on coverage information, based on load information, based on blind handover information, different system directed retry information and directed retry cause information combination in any wherein between described system.
14. 14. report method according to claim 12 is characterized in that, described isosystem measurement Report Type comprises that switching outgoing event between measurement report type and system identifies.
15. 15. report method according to claim 14 is characterized in that, described isosystem measurement Report Type also comprises preiodic type information and/or event mode information.
16. 16. report method according to claim 2 is characterized in that, described fault message partly comprises selects the reason group.
17. 17. report method according to claim 16 is characterized in that, described fault message part also comprises RNC internal fault, IUB interface fault, UU interface fault and IU interface fault combination in any wherein.
18. 18. report method as claimed in claim 1 is characterized in that, described switch failure parameter information is concentrated the parameter item of the described inquiry of classification setting step by step.
19. 19. report method as claimed in claim 18 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.
20. 20. report method as claimed in claim 19 is characterized in that, also comprises in the described fault reporting message: the cell that carries the type of message sign.
21. 21. as claim 19 or 20 described report 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