CN103081558B

CN103081558B - For the network element of end-to-end (E2E) circuit service (CS) call follow function

Info

Publication number: CN103081558B
Application number: CN201080068560.0A
Authority: CN
Inventors: 王春波; 克劳斯·图锐那; 初海滨; 董正浩; 许明秋
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2010-08-10
Filing date: 2010-09-19
Publication date: 2016-01-20
Anticipated expiration: 2030-09-19
Also published as: CN103081558A

Abstract

According to the present invention, provide a kind of network element (NE), as the source NE for end-to-end (E2E) circuit service (CS) call follow function, this NE comprises: receiver, be configured for receiving package and activate message containing tracing control and configuration parameter in interior tracking, wherein, tracing control and configuration parameter at least comprise track reference, beginning trigger event, stop trigger event, E2E call follow option and follow the tracks of the address of collecting entity; Memory device, is configured for and stores the tracing control that receives of receiver and configuration parameter; Tracking data reporter, is configured for and starts trace session with track reference, when occurring starting trigger event, starts track record session with track record session reference, and according to stored tracing control and configuration parameter record and output tracking data; And transmitter, be configured for detecting and tracking activation message and comprise E2E call follow option, and comprise/send tracking extended field at the protocol sig-naling messages going to next NE, wherein, this tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity, wherein, tracking data reporter is also configured for when occurring stopping trigger event, stops track record session.In addition, present invention also offers the NE as middle NE and the NE as egress NE, the two is all for E2ECS call follow function.

Description

For the network element of end-to-end (E2E) circuit service (CS) call follow function

Technical field

The present invention relates to wireless communication system, more specifically, relating to a kind of for providing the scheme of end-to-end (E2E) circuit service (CS) call follow function and the related network elements for the program.

Background technology

In third generation Partnership Program (3GPP), propose and have studied the concept of following function.

Term and definition for following function in 3GPP technical specification is as follows:

Follow the tracks of:

For the generic term of subscriber, subscriber equipment (UE) and service tracks (service tracks is only for IP Multimedia System (IMS)).

Trace session:

Start with trace session activation and continue until the time interval (see Fig. 1) of this specific tracking session deexcitation.

Track reference:

Mark trace session, and be globally unique.

Track record session:

In trace session for just in tracked subscriber, UE or service creation time interval of track record.The trigger event of start and stop track record session is also defined in 3GPP technical specification.

Track record session reference:

Track record session in mark trace session.

Particularly, Fig. 1 is the schematic diagram of the concept illustrating trace session and track reference.

With reference to Fig. 1, trace session 110 starts with trace session activation 120, and trace session activation 120 comprises following parameter:

-International Mobile Subscriber the identification code (IMSI) for subscriber's tracking, the International Mobile Equipment Identity (IMEI) for UE tracking or IMEI software version (IMEI (SV)) or the public ID for service tracks;

-track reference; And

-tracing control and configuration parameter.

Trace session 110 will start with trace session deexcitation 130, and trace session deexcitation 130 at least comprises the track reference of trace session 110.

Fig. 2 is the schematic diagram of the concept illustrating track record session and track record session reference.

With reference to Fig. 2, trace session 110 can comprise some track record sessions, exemplarily shows 2 track record sessions 140 and 150.Each in track record session 140 and 150 starts to start trigger event, and to stop trigger event terminating.Both start and stop trigger events all define in 3GPP technical specification.In addition, each in track record session 140 and 150 is by being unique track record session reference mark in the trace session 110 comprising corresponding track record session.

3GPP technical specification defines the trace session activation mechanism based on management and the trace session activation mechanism based on signaling.

Fig. 3 illustrates to utilize the trace session activation based on signaling to follow the tracks of the sequential chart of the example of mobile source calling in circuit service (CS) territory.

With reference to Fig. 3, in step 301, element manager server (EMS) sends trace session activation to home subscriber servers (HSS).

In step 302, when HSS receives trace session activation from EMS, it stores the tracing control and configuration parameter that are associated with trace session.

In step 303, UE comes to network registry by sending LOCATIONUPDATINGREQUEST (position updating request) message to mobile handoff center (MSC) server (MSS)/Visited Location Registor (VLR).

In step 304, MSC server/VLR is by upgrading the positional information in HSS to HSS transmission MAP-UPDATE_LOCATION (MAP-renewal _ position) message.

In step 305, after receiving UPDATE_LOCATION message, HSS propagates tracing control and configuration parameter by sending MAP-ACTIVATE_TRACE_MODE (MAP-activation _ tracking _ pattern) message to MSC server/VLR.

In step 305, when HSS sends MAP-ACTIVATE_TRACE_MODE message to MSC server, message comprises following parameter (, " (M) " represents compulsory, and " (O) " represents optional) here:

-IMSI(M)。

-track reference (M).

-for the trigger event of MSC server (M) and MGW (M).

-tracking depths (M).

-the list (M) of NE type for following the tracks of.

-for the list of the interface of MSC server (O), MGW (O) and/or RNC (O).

Within step 306, when MCS server/VLR receives MAP-ACTIVATE_TRACE_MODE message from HSS, it stores tracing control and configuration parameter.

In step 307, MCS server/VLR is with trace session from the track reference that HSS receives.

In step 308-310, when appear in tracing control and configuration parameter define start arbitrarily trigger event time (such as, start (namely in mobile source calling, when MSC server receives CM_SERVICE_REQUEST (CM_ service _ request) message with the COS being set to source call setup), MSC server starts track record session, and tracing control and configuration parameter are propagated into media gateway (MGW) (by sending the trace packet with ADD order), and propagate into radio net (if this definition in tracing control and configuration parameter (network element (NE) type for following the tracks of)).

In the step 310, when MSC server has the trace packet of ADD order to MGW transmission, message comprises following parameters:

-IMSI or IMEI (SV) (M).

-track reference (M).

-track record session reference (M).

-for the trigger event (M) of MGW.

-tracking depths (M).

-for the list (O) of the interface of MGW.

In step 311, when receiving tracing control and configuration parameter from MSC server, MGW is with trace session from the track reference that MSC server receives.

In current 3GPP technical specification, only define the tracking based on subscriber for circuit service (CS) territory.During calling procedure, tracking and controlling parameter can be propagated into radio network controller (RNC)/base station controller (BSC) and MGW by MSC, but tracing control and configuration parameter can not be propagated into egress MSC (T-MSC) from source MSC (O-MSC).Due to this restriction:

(1) if two calling party are not in same MSC server, then can capture mobile source (MO) or mobile terminal (MT) calling procedure in a trace session, this depend on by MO subscriber identification (Id) or by MT subscriber identification (Id) for trace session activation.

(2) but, in this case, the signaling message running through gateway MSC (GMSC)/switching centre (TSC) for calling procedure cannot be captured.

In practice, operator often wants to utilize the call follow of both sides to follow the tracks of end-to-end (E2E) calling procedure, to have checking of an E2E to call activity, and effectively processes problematic calling.A kind of possibility solving above-mentioned restriction is the trace session activated at O-MSC place for calling party, and activates another trace session for callee at T-MSC place.But this is quite inconvenient for operator, and in most of the cases callee is not known in advance.

Summary of the invention

In order to solve the problem, the present invention proposes a kind of solution of supporting to follow the tracks of end-to-end (E2E) call activity comprising all-calls side involved in calling procedure.

Whether in the present invention, utilize E2E call follow option to expand tracing control and configuration parameter, be the session of E2E call follow to indicate this trace session.According to the present invention, if be provided with E2E call follow option, then tracing control and configuration parameter extended further to comprise following the tracks of and collect substance parameter, with the server indicating all tracking datas to be sent to.

For in a preferred embodiment of CS-CS call follow, be also incorporate at least comprise by track reference, track record session reference and follow the tracks of the tracking extended field collecting the parameter that entity is formed by the signaling extensions between the signaling between O-MSC and TSC/GMSC and GMSC/TSC and T-MSC.

Alternatively, for in another preferred embodiment of CS-CS call follow, also by the signaling extensions between the signaling between the signaling between O-MSC and TSC/GMSC, TSC/GMSC and HLR/HSS and HLR/HSS and T-MSC for comprising tracking extended field, described tracking extended field at least comprises following parameter: track reference, track record session reference and follow the tracks of collect entity.

For in a preferred embodiment of CS-IMS interworking call follow, also by the signaling between O-MSC and MGCF (MGCF) and the signaling extensions between MGCF and enquiry call conversation control function (CSCF) (I-CSCF)/serving CSCF (S-CSCF) for comprising tracking extended field, described tracking extended field at least comprises following parameter: track reference, track record session reference and follow the tracks of and collect entity.

Alternatively, in another preferred embodiment for CS-IMS interworking call follow, also by the signaling extensions in the signaling between O-MSC and S-CSCF and S-CSCF and services set and between continuity (SCC) application server (AS) for comprising tracking extended field, described tracking extended field at least comprises following parameter: track reference, track record session reference and follow the tracks of collect entity.

According to first scheme of the present invention, provide a kind of network element, as the source-end networks unit for end to end circuit service call following function, described network element comprises: receiver, be configured for receiving package and activate message containing tracing control and configuration parameter in interior tracking, wherein, tracing control and configuration parameter at least comprise track reference, beginning trigger event, stop trigger event, end-to-end call follow option and follow the tracks of the address of collecting entity; Memory device, is configured for and stores the tracing control that receives of receiver and configuration parameter; Tracking data reporter, is configured for and starts trace session with track reference, when occurring starting trigger event, starts track record session with track record session reference, and according to stored tracing control and configuration parameter record and output tracking data; And transmitter, be configured for detecting and tracking activation message and comprise end-to-end call follow option, and comprise/send tracking extended field at the protocol sig-naling messages going to next network element, wherein, this tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity, wherein, described tracking data reporter is also configured for when occurring stopping trigger event, stops track record session.

Preferably, described tracking data reporter is configured for and is recorded in trace file by all relevant tracked data, and after the described track record session of stopping, described tracking data reporter is configured for, according to following the tracks of the address of collecting entity, recorded trace file is outputted to tracking collection entity.

Preferably, described tracking data reporter is configured for: real time record tracking data, and according to following the tracks of the address of collecting entity, tracking data is outputted to tracking collection entity in real time.

Preferably, described network element is source mobile handoff central server; It is the MAP-ACTIVATE_TRACE_MODE message from home subscriber servers or the trace session activation message from element manager server that described tracking activates message; And described protocol sig-naling messages is BICC/ISUPIAM message or SIP:INVITE message.

According to alternative plan of the present invention, provide a kind of network element, as the intermediate network elements for end to end circuit service call following function, described network element comprises: receiver, be configured for receiving package follows the tracks of extended field the first protocol sig-naling messages containing first, and described first tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity; Tracking data reporter, is configured for the track reference that receives and the track record session reference that receives to start track record session, and follows the tracks of extended field record and output tracking data according to described first; And transmitter, be configured for and comprise/send the second tracking extended field at the second protocol signaling message going to next network element, it is identical that wherein said second tracking extended field and described first follows the tracks of extended field, or obtain from described first tracking extended field, wherein, described tracking data reporter is also configured for when there is the stopping trigger event for track record session, stops track record session.

Preferably, described network element is Gateway Mobile Switching Center server or sends main dispatching centre; Described first protocol sig-naling messages is BICC/ISUPIAM message; And described second protocol signaling message is BICC/ISUPIAM message or MAPSRI message.

Preferably, described network element is attaching position register; Described first protocol sig-naling messages is MAPSRI message; And described second protocol signaling message is MAPPRN message.

Preferably, described network element is MGCF entity; Described first protocol sig-naling messages is BICC/ISUPIAM message; And described second protocol signaling message is SIP:INVITE message.

Preferably, described network element is service call session control function entity; Described first protocol sig-naling messages is SIP:INVITE message; And described second protocol signaling message is SIP:INVITE message.

According to third program of the present invention, provide a kind of network element, as the egress network element for end to end circuit service call following function, described network element comprises: receiver, be configured for receiving package containing following the tracks of extended field at interior protocol sig-naling messages, described tracking extended field at least comprises track reference, starts recording conversation reference and follow the tracks of the address of collecting entity; And tracking data reporter, the track reference being configured for receive starts track record session with the track record session reference received, according to following the tracks of extended field record and output tracking data, and when there is the stopping trigger event for track record session, stop track record session.

Preferably, described network element is egress mobile handoff central server; And described protocol sig-naling messages is BICC/ISUPIAM message or MAPPRN message.

Preferably, described network element is service call session control function entity; And described protocol sig-naling messages is SIP:INVITE message.

According to fourth program of the present invention, provide a kind of for providing the method for end to end circuit service call following function, described method comprises step: receiving package activates message containing the tracking of tracing control and configuration parameter, wherein, this tracing control and configuration parameter at least comprise track reference, beginning trigger event, stop trigger event, end-to-end call follow option and follow the tracks of the address of collecting entity; Store the tracing control and configuration parameter that receive; Trace session is started with track reference; When occurring starting trigger event, start track record session with track record session reference; According to stored tracing control and configuration parameter record/output tracking data; Comprise at the protocol sig-naling messages going to next network element/send and follow the tracks of extended field, wherein, this tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity; And when occurring stopping trigger event, stop track record session.

Preferably, all relevant tracked data are recorded in trace file, and after the described track record session of stopping, described method also comprises step: according to following the tracks of the address of collecting entity, recorded trace file is outputted to tracking collection entity.

Preferably, real time record tracking data, and according to following the tracks of the address of collecting entity, tracking data is outputted to tracking collection entity in real time.

Preferably, described method is adopted by source mobile handoff central server; It is the MAP-ACTIVATE_TRACE_MODE message from home subscriber servers or the trace session activation message from element manager server that described tracking activates message; And described protocol sig-naling messages is BICC/ISUPIAM message or SIP:INVITE message.

According to the 5th scheme of the present invention, provide a kind of for providing the method for end to end circuit service call following function, described method comprises: receiving package follows the tracks of the first protocol sig-naling messages of extended field containing first, and described first tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity; With the track reference received and the track record session reference that receives to start track record session; Extended field record/output tracking data are followed the tracks of according to described first; Comprise/send second at the second protocol signaling message going to next network element and follow the tracks of extended field, it is identical that wherein said second tracking extended field and described first follows the tracks of extended field, or obtain from described first tracking extended field; And when there is the stopping trigger event for track record session, stop track record session.

Preferably, described method is adopted by Gateway Mobile Switching Center server or transmission main dispatching centre; Described first protocol sig-naling messages is BICC/ISUPIAM message; And described second protocol signaling message is BICC/ISUPIAM message or MAPSRI message.

Preferably, described method is adopted by attaching position register; Described first protocol sig-naling messages is MAPSRI message; And described second protocol signaling message is MAPPRN message.

Preferably, described method is adopted by MGCF entity; Described first protocol sig-naling messages is BICC/ISUPIAM message; And described second protocol signaling message is SIP:INVITE message.

Preferably, described method is adopted by service call session control function entity; Described first protocol sig-naling messages is SIP:INVITE message; And described second protocol signaling message is SIP:INVITE message.

According to the 6th scheme of the present invention, provide a kind of for providing the method for end to end circuit service call following function, described method comprises: receiving package is containing the protocol sig-naling messages following the tracks of extended field, and described protocol sig-naling messages at least comprises track reference, starts recording conversation reference and follow the tracks of the address of collecting entity; Track record session is started with the track reference received and the track record session reference received; According to tracking extended field record/output tracking data; And when there is the stopping trigger event for track record session, stop track record session.

Preferably, described method is adopted by egress mobile handoff central server; And described protocol sig-naling messages is BICC/ISUPIAM message or MAPPRN message.

Preferably, described method is adopted by service call session control function entity; And described protocol sig-naling messages is SIP:INVITE message.

Accompanying drawing explanation

By describing non-limiting embodiments of the present invention in detail below in conjunction with accompanying drawing, above-mentioned and other objects, features and advantages of the present invention will be made clearly, in the accompanying drawings:

Fig. 1 is the schematic diagram of the concept illustrating trace session and track reference;

Fig. 2 is the schematic diagram of the concept illustrating track record session and track record session reference;

Fig. 3 illustrates to utilize the trace session activation based on signaling to follow the tracks of the sequential chart of the example of mobile source calling in circuit service (CS) territory;

Fig. 4 is the sequential chart of the first embodiment of the present invention illustrated for end-to-end (E2E) CS-CS call follow scene;

Fig. 5 is the sequential chart of the second embodiment of the present invention illustrated for E2ECS-CS call follow scene;

Fig. 6 is the sequential chart of the third embodiment of the present invention illustrated for E2ECS-IMS interworking call follow scene;

Fig. 7 is the sequential chart of the fourth embodiment of the present invention illustrated for E2ECS-IMS interworking call follow scene;

Fig. 8 A is the schematic block diagram for the structure of exemplary network unit (NE) 8000 when being regarded as the O-MSC in above-mentioned first to fourth embodiment;

Fig. 8 B is for illustrating the flow chart of the operation of NE8000 when being regarded as O-MSC in above-mentioned first to fourth embodiment;

Fig. 9 A is for illustrating the schematic block diagram of the structure of NE9000 when being regarded as the MGCF/I-CSCF in TSC/GMSC or HSS in the TSC/GMSC in above-mentioned first embodiment, above-mentioned second embodiment, above-mentioned 3rd embodiment or the S-CSCF in above-mentioned 4th embodiment;

Fig. 9 B is for illustrating the flow chart of the operation of NE9000 when being regarded as the MGCF/I-CSCF in TSC/GMSC or HSS in the TSC/GMSC in above-mentioned first embodiment, above-mentioned second embodiment, above-mentioned 3rd embodiment or the S-CSCF in above-mentioned 4th embodiment;

The schematic block diagram of structure when Figure 10 A is the S-CSCF for illustrating NEA000 in the T-MSC be regarded as in above-mentioned first and second embodiments or above-mentioned third and fourth embodiment; And

The flow chart of operation when Figure 10 B is the S-CSCF for illustrating NEA000 in the T-MSC be regarded as in above-mentioned first and second embodiments or above-mentioned third and fourth embodiment.

Embodiment

Present invention is described with reference to the accompanying drawings.In the following description, the object of some specific embodiments only for describing, is not appreciated that any limitation of the invention, and is only its example.Traditional structure or structure will be omitted, cause to prevent the understanding of the present invention and obscure.

[the first embodiment]

Fig. 4 is the sequential chart of the first embodiment of the present invention illustrated for end-to-end (E2E) CS-CS call follow scene.

With reference to Fig. 4, in step 401, operation and maintenance (O & M) service (such as EMS) sends trace session activation to HSS/ attaching position register (HLR).

Whether in the present invention, tracing control and configuration parameter are expanded to and comprise E2E call follow option, be the session of E2E call follow to indicate this trace session.If include this E2E call follow option (namely, this trace session is the session of E2E call follow), then tracing control and configuration parameter are extended further to the parameter comprising and follow the tracks of and collect entity, to indicate the server that all tracking datas should be sent to.In the context of the present invention, the situation comprising E2E call follow option and follow the tracks of the parameter of collecting entity is described in detail, that is, operator indicators track E2E calling procedure.

In step 402, when HSS/HLR receives the trace session activation of serving from O & M, it stores the tracing control and configuration parameter that are associated with trace session, and wherein this tracing control and configuration parameter comprise E2E call follow option and follow the tracks of the parameter of collecting entity.

In step 403, UEA registers to network by sending LOCATIONUPDATINGREQUEST (position updating request) message to O-MSC server/VLR.

In step 404, O-MSC server/VLR is by upgrading the positional information in HSS to HSS transmission MAP-UPDATE_LOCATION (MAP-renewal _ position) message.

In step 405, after receiving UPDATE_LOCATION (renewal _ position) message, HSS/HLR, when sending MAP-ACTIVATE_TRACE_MODE (MAP-activation _ tracking _ pattern) message to O-MSC server/VLR, comprises E2E call follow option at tracing control and configuration parameter and follows the tracks of the parameter of collecting entity.

In step 405, when HSS/HLR sends MAP-ACTIVATE_TRACE_MODE message to MSC server, comprise following parameters (, (M) represents compulsory, and (O) represents optional) within the message here:

-IMSI(M)。

-track reference (M).

-E2E option (O).

-follow the tracks of and collect entity (O).

-for the trigger event of MSC server (M) and MGW (M).

-tracking depths (M).

-the list (M) of NE type for following the tracks of.

-for the list of the interface of MSC server (O), MGW (O) and/or RNC (O).

In a step 406, when O-MSC server/VLR receives MAP-ACTIVATE_TRACE_MODE message from HSS, it stores tracing control and configuration parameter (comprise E2E call follow option and follow the tracks of the parameter of collecting entity).

In step 407, O-MCS server/VLR is with trace session from the track reference that HSS receives.

In step 408 and 409, when appear in tracing control and configuration parameter define start arbitrarily trigger event time (such as, O-MSC server receives CM_SERVICE_REQUEST (CM_ service _ request) message with the COS being set to source call setup from UEA), O-MSC server starts track record session with track record session reference, and to record with configuration parameter according to tracing control and export the signaling message relevant to calling procedure.

In step 410, when starting track record session, if comprise (namely for corresponding trace session, arrange) E2E call follow option, then O-MSC comprises tracking extended field in bearer independent call control (BICC)/ISDN User Part (ISUP) initial address message (IAM) message of the striking out of going to TSC/GMSC.

Alternatively, O-MSC can determine whether comprising tracking extended field in the BICC/ISUPIAM message of striking out based on carrier policy.

Such as, carrier policy can be defined based on caller rs number, callee's number and/or Routing Category.Exemplarily, O-MSC can provide as follows for the detailed deterministic process of callee's number:

analyze callee's number,

determine whether this callee's number belongs to the predefined particular number classification of operator (such as, being international number or special services number),

if carrier policy is forbidden the tracking comprised for predefined particular number classification and expanded, then do not comprise in the BICC/ISUPIAM message of striking out and follow the tracks of expansion,

otherwise, expand if carrier policy does not forbid the tracking comprised for predefined particular number classification, then comprise in the BICC/ISUPIAM message of striking out and follow the tracks of expansion.

Tracking extended field for BICC/ISUPIAM at least comprises following tracing control and configuration parameter:

-track reference

-track record session reference

-trigger event

-tracking depths

-interface list

-follow the tracks of the IP address of collecting entity

For above-mentioned tracing control and the definition of configuration parameter and the same of defined in 3GPP technical specification." following the tracks of the IP address of collecting entity " is a concrete example of following the tracks of the parameter of collecting entity, this example relates to public tracking server, wherein based on track reference and track record session reference, the track record of the same call process being received from heterogeneous networks node is associated.

For following the tracks of the compatibility parameter of extended field according to BICC/ISUP standard configuration, and the MSC received not supporting to follow the tracks of expansion can not be made to refuse this calling.According to ITU-Q.1902.2, in BICC/ISUPIAM, there is optional parameters: parameter compatibility information, this parameter can be supported in BICC/ISUPIAM message adds new argument, and does not introduce the problem of backward compatibility.

In step 411, if TSC/GMSC is supported in the tracking extended field that BICC/ISUPIAM message comprises, then it is with the track reference received and track record session reference, start track record session, according to the tracing control in the tracking extended field comprised in the BICC/ISUPIAM message received and configuration parameter, record and export the signaling message relevant to calling procedure.

Equally, alternatively, whether TSC/GMSC can determine whether starting track record session and propagate to follow the tracks of expansion based on carrier policy.It should be noted that TSC/GMSC can be operated by the operator different from the operator of O-MSC, and the carrier policy that the operator that therefore carrier policy can be different from O-MSC provides (such as, list in step 410 those).

In step 412-415, GMSC, when inquiring HSS with routing call, sends MobileApplicationPart (MAP) (MAP) SendRoutingInformation (transmission routing iinformation) (SRI) message to HSS; Inquiry HSS sends MAPProvideRoamingNumber (Providing Roaming Number) (PRN) message to T-MSC; T-MSC is in response to from the MAPPRN that receives of inquiry HSS to return MAPPRN affirmative acknowledgement (ACK); And when receiving MAPPRNACK from T-MSC, inquiry HSS returns MAPSRIACK as the positive response for MAPSRI to GMSC.This process of step 412-415 and the identical of defined in 3GPP technical specification.

In step 416, after receiving MAPSRIACK from inquiry HSS, TSC/GMSC propagates and follows the tracks of extended field in the BICC/ISUPIAM message of striking out going to T-MSC.

In step 417, if T-MSC supports the tracking extended field in BICC/ISUPIAM message, then it is with the track reference received and track record session reference, starts track record session.After the session of beginning track record, T-MSC, according to the tracing control in tracking extended field included in the BICC/ISUPIAM message received and configuration parameter, records and exports the signaling message relevant to calling procedure.

Equally, alternatively, T-MSC can determine whether starting track record session based on carrier policy.Should note, T-MSC can be operated by the operator different from the operator of O-MSC and/or the operator of TSC/GMSC, and the carrier policy that the operator that therefore this carrier policy can be different from O-MSC and/or TSC/GMSC provides (such as, list in step 410 those).

In step 418, the UEB that T-MSC is calling out to UEA sends paging request.

Thereafter, between related entities, perform the normal running for the CS-CS calling procedure between UEA and UEB.

During calling procedure, O-MSC, TSC/GMSC or T-MSC can according to tracing control and configuration parameter record (in a centralised manner) with export (in real time fashion) signaling message relevant to calling procedure, until stop corresponding track record session.When track record conversation end, O-MSC, TSC/GMSC and/or T-MSC remove tracing control and configuration parameter, and stop tracing process.

All relevant tracked data are recorded in trace file according to centralized system by O-MSC, TSC/GMSC or T-MSC, and after there is the stopping trigger event for track record session, O-MSC, TSC/GMSC or T-MSC stop corresponding track record session, are then outputted to by recorded trace file to follow the tracks of to collect entity.

O-MSC, TSC/GMSC or T-MSC according to real-time mode by relevant tracked data record and output to follow the tracks of collect entity.

According to centralized system and real-time mode, track reference and track record session reference are correlated with for making identical calling procedure, and can being included in the title of recorded trace file (according to centralized system) or being included in tracking data, this tracking data is by real time record and output to follow the tracks of and collect entity.

Replace the operation performed in step 401-406, another kind of method directly activates the trace session with E2E call follow ability from element manager (EM) entity (such as EMS) to its MSC server managed.Such as, the MSC server that EMS can manage directly to it sends trace session activation, and require no HSS/HLR, and the MSC server managed stores tracing control and configuration parameter (comprise E2E call follow option and follow the tracks of the parameter of collecting entity).Thereafter, with class of operation in step 407 seemingly, MSC server with the track reference received from EM entity, start trace session.Trace session reference should be used, via management interface, the MSC server transmission managed to EM entity comprises the tracing control of E2E call follow option and the identity set of configuration parameter, follows the tracks of activate (reference pin is to the content described by step 401) as HSS.Compared with the method activated with the tracking from HSS, the activation based on management does not rely on HSS, but tracked subscriber can not register in the MSC server of EM management area.For the activation based on management, EM entity needs the uniqueness of the parameter of the track reference guaranteed in its management area.

In addition, for the activation based on HSS described in step 401-406 and the above-mentioned alternative activation based on management, operator also may have the safety concerns for the activation based on management, that is, the people only accessing some nodes (an EM region) can obtain the trace information of whole network.In order to eliminate this safety issue, operator can configure the credible list following the tracks of collection entity (that is, tracking server) in MSC server, and forbids that tracking data outputs to insincere tracking server.

In the above description, use BICC/ISUP as the agreement of Nc interface.The tracing control and configuration parameter that are used for E2E call follow can also be expanded to the Nc interface (this expansion can be included in encapsulation BICC/ISUP message in a sip message) based on SIP-I, or the call control protocol (such as, TUP) suitable arbitrarily used on Nc interface.But the expansion for other protocol types also should be guaranteed to send the compatibility between receiving node.When protocol type does not provide the compatibility as BICC/ISUP/SIP-I, only when receiving and all supporting extended field both sending node, just can comprise and follow the tracks of expansion.

Utilize above-mentioned first embodiment of the present invention, can following advantages be realized:

(1) Virtual network operator can provide good customer care service to mobile subscriber.Can perfect tracking locate the problem of each subscriber, thus accelerate the solution to problem.Which increase customer satisfaction, and reduce customer churn.

(2) operator can by catching the activity of E2E call follow a network node place activation trace session.Be convenient to operator's executive problem answer and functional verification.

(3) program can not cause the problem in interworking after introducing E2E and following the tracks of option.Do not support that the MSC of E2E follow-up control will ignore follow the tracks of extended field and continue call establishment.

[the second embodiment]

Fig. 5 is the sequential chart of the second embodiment of the present invention illustrated for end-to-end (E2E) CS-CS call follow scene.Step identical with Fig. 4 in Fig. 5 represents with identical Reference numeral, and therefore omits detailed description, lengthy and tedious to avoid.

After performing step 401-411, in step 512, GMSC, when inquiring HSS with routing call, comprises the extended field of tracing control and configuration parameter in MAP (SRI) message.

In step 513, if inquiry HSS supports to follow the tracks of expansion, then it propagates to T-MSC and follows the tracks of extended field in MAPPRN message.

On the other hand, if inquiry HSS does not support the tracking extended field in MAPSRI, then it will not comprise tracking extended field in MAPPRN message, then by the step 413-418 in execution first embodiment, with replace step 513 in the second embodiment, 517, the processing sequence of 414-416 and 418.

In step 517, if T-MSC detects tracking extended field in MAPPRN message, then it is with the track record session reference received, and starts track record session.After beginning track record session, T-MSC to record with configuration parameter according to the tracing control in the tracking extended field comprised in the MAPPRN message received and exports the signaling message relevant to calling procedure.

Equally, alternatively, T-MSC can determine whether start track record session based on carrier policy.Should note, T-MSC can be operated by the operator different from the operator of O-MSC and/or the operator of TSC/GMSC, and the carrier policy that the operator that therefore carrier policy can be different from O-MSC and/or TSC/GMSC provides (such as, list in step 410 those).

After step 414-416 and 418, between related entities, perform the normal running for the CS-CS calling procedure between UEA and UEB.

Although have impact on HLR/HSS (limit and dispose possibility), utilize above-mentioned second embodiment of the present invention, can following advantages be realized:

[the 3rd embodiment]

Fig. 6 is the sequential chart of the third embodiment of the present invention illustrated for end-to-end (E2E) CS-IMS interworking call follow scene.Step identical with Fig. 4 in Fig. 6 represents with identical Reference numeral, and therefore omits detailed description, lengthy and tedious to avoid.

After performing step 401-409, in step 610, for CS-IMS interworking scene, when track record session start, if comprise (namely for corresponding trace session, arrange) E2E call follow option, then O-MSC comprises tracking extended field in the BICC/ISUPIAM message of the striking out of going to MGCF (MGCF).

analyze callee's number,

-track reference

-track record session reference

-trigger event

-tracking depths

-interface list

-follow the tracks of the IP address of collecting entity

For following the tracks of the compatibility parameter of extended field according to BICC/ISUP standard configuration, and the MSC received not supporting to follow the tracks of expansion can not be made to refuse this calling.According to ITU-Q.1902.2, there is optional parameters at BICC/ISUPIAM: parameter compatibility information, this parameter can be supported in IBICC/ISUPIAM message adds new argument, and can not introduce the problem of backward compatibility.

In step 611, if MGCF is supported in the tracking extended field that BICC/ISUPIAM message comprises, then it is with the track reference received and track record session reference, start track record session, according to the tracing control in the tracking extended field comprised in the BICC/ISUPIAM message received and configuration parameter, record and export out Session initiation Protocol (SIP) signaling message relevant to calling procedure.

Equally, alternatively, MGCF can determine whether starting track record session and whether propagating tracing control and configuration parameter based on carrier policy.It should be noted that MGCF can be operated by the operator different from the operator of O-MSC, and the carrier policy that the operator that therefore carrier policy can be different from O-MSC provides (such as, list in step 610 those).

In step 616, MGCF, based on carrier policy, propagates tracing control and configuration parameter in the SIPINVITE message of striking out going to enquiry call conversation control function (CSCF) (I-CSCF)/serving CSCF (S-CSCF).

In step 617, I/S-CSCF, with the track reference received and track record session reference, starts track record session.After the session of beginning track record, I/S-CSCF, according to the tracing control comprised in the SIPINVITE message received and configuration parameter, records and exports the SIP signaling message relevant to calling procedure.

Still alternatively, I/S-CSCF determines whether start track record session based on carrier policy.Should note, I/S-CSCF can be operated by the operator different from the operator of O-MSC and/or the operator of MGCF, and the carrier policy that the operator that therefore carrier policy can be different from O-MSC and/or MGCF provides (such as, list in step 610 those).

In step 618, the UEB that S-CSCF is calling out to UEA sends SIPINVITE message.

Thereafter, between related entities, perform the normal running for the CS-IMS interworking calling procedure between UEA and UEB.

During calling procedure, O-MSC, MGCF or I/S-CSCF can according to tracing control and configuration parameter record (in a centralised manner) with export (in real time fashion) signaling message relevant to calling procedure, until stop corresponding track record session.When track record conversation end, O-MSC, MGCF and/or I/S-CSCF remove tracing control and configuration parameter, and stop tracing process.

All relevant tracked data are recorded in trace file according to centralized system by O-MSC, MGCF or I/S-CSCF, and after there is the stopping trigger event for track record session, O-MSC, MGCF or I/S-CSCF stop corresponding track record session, are then outputted to by recorded trace file to follow the tracks of to collect entity.

O-MSC, MGCF or I/S-CSCF according to real-time mode by relevant tracked data record and output to follow the tracks of collect entity.

Utilize above-mentioned 3rd embodiment of the present invention, can following advantages be realized:

[the 4th embodiment]

Fig. 7 is the sequential chart of the fourth embodiment of the present invention illustrated for end-to-end (E2E) CS-IMS interworking call follow scene.Step identical with Fig. 4 in Fig. 7 represents with identical Reference numeral, and therefore omits detailed description, lengthy and tedious to avoid.

In the fourth embodiment of the present invention, O-MSC enhancing is used for IMS centralized services (ICS), to be deployed in by O-MSC in the CS-IMS interworking scene based on ICS.

After performing step 401-409, in step 720, when starting track record session, if comprise (namely for corresponding trace session, arrange) E2E call follow option, then O-MSC comprises tracing control and configuration parameter in the SIPINVITE message of the striking out of going to S-CSCF.

Alternatively, O-MSC can determine whether comprising tracing control and configuration parameter in the SIPINVITE message of striking out based on carrier policy.

analyze callee's number,

if carrier policy is forbidden comprising the tracing control for predefined particular number classification and configuration parameter, then do not comprise tracing control and configuration parameter in the SIPINVITE message of striking out,

otherwise, if carrier policy is not forbidden comprising the tracing control for predefined particular number classification and configuration parameter, then comprise tracing control and configuration parameter in the SIPINVITE message of striking out.

List under at least comprising for the tracing control of SIPINVITE message and configuration parameter:

-track reference

-track record session reference

-trigger event

-tracking depths

-interface list

-follow the tracks of the IP address of collecting entity

In step 711, if S-CSCF is supported in tracing control and configuration parameter that SIPINVITE message comprises, then it is with the track reference received and track record session reference, start track record session, according to the tracing control comprised in the SIPINVITE message received and configuration parameter, record and export the out SIP signaling message relevant to calling procedure.

Equally, alternatively, S-CSCF can determine whether starting track record session and whether propagating tracing control and configuration parameter based on carrier policy.It should be noted that S-CSCF can be operated by the operator different from the operator of O-MSC, and the carrier policy that the operator that therefore carrier policy can be different from O-MSC provides (such as, list in step 720 those).

In step 716, S-CSCF based on carrier policy, to go in services set and continuity (SCC) application server (AS) striking out SIPINVITE message in propagate tracing control and configuration parameter.

In step 717, SCCAS, with the track reference received and track record session reference, starts track record session.After the session of beginning track record, SCCAS, according to the tracing control comprised in the SIPINVITE message received and configuration parameter, records and exports the SIP signaling message relevant to calling procedure.

Equally, alternatively, SCCAS determines whether start track record session based on carrier policy.Should note, SCCAS can be operated by the operator different from the operator of O-MSC and/or the operator of S-CSCF, and the carrier policy that the operator that therefore carrier policy can be different from O-MSC and/or S-CSCF provides (such as, list in step 720 those).

In step 720, SCCAS sends SIPINVITE message, as the response to the SIPINVITE message received from S-CSCF to S-CSCF.

In step 618, the UEB that S-CSCF is calling out to UEA sends SIPINVITE message.

During calling procedure, O-MSC, S-CSCF or SCCAS can according to tracing control and configuration parameter record (in a centralised manner) with export (in real time fashion) signaling message relevant to calling procedure, until stop corresponding track record session.When track record conversation end, O-MSC, S-CSCF and/or SCCAS remove tracing control and configuration parameter, and stop tracing process.

All relevant tracked data are recorded in trace file according to centralized system by O-MSC, S-CSCF or SCCAS, and after there is the stopping trigger event for track record session, O-MSC, S-CSCF or SCCAS stop corresponding track record session, are then outputted to by recorded trace file to follow the tracks of to collect entity.

O-MSC, S-CSCF or SCCAS according to real-time mode by relevant tracked data record and output to follow the tracks of collect entity.

Although for ICS, O-MSC is strengthened (system which increases disposes complexity), but utilizes above-mentioned 4th embodiment of the present invention, can following advantages be realized:

[structure of related network elements and operation]

Fig. 8 A is the schematic block diagram for the structure of exemplary network unit (NE) 8000 when being regarded as the O-MSC in above-mentioned first to fourth embodiment; And Fig. 8 B is the flow chart for the operation of exemplary network unit (NE) 8000 when being regarded as O-MSC in above-mentioned first to fourth embodiment.

With reference to Fig. 8 A, NE8000 comprises receiver 8100, memory device 8200, tracking data reporter 8300 and transmitter 8400.

Next, the operation of the unit of NE8000 is described with reference to Fig. 8 B.

In step S801, receiver 8100 receiving package of NE8000 activates message containing tracing control and configuration parameter in interior tracking, and tracing control and configuration parameter at least comprise track reference, start trigger event, stop trigger event, E2E call follow option and follow the tracks of the address of collecting entity.

In step S802, the memory device 8200 of NE8000 stores the tracing control and configuration parameter that receiver receives, and the tracking data reporter 8300 of NE8000 is with track reference, starts trace session.

In step S803, when occurring starting trigger event, the tracking data reporter 8300 of NE8000, with track record session reference, starts track record session, and the tracking data reporter 8300 of NE8000 is according to stored tracing control and configuration parameter, record and output tracking data.

In step S804, transmitter 8400 detecting and tracking of NE8000 activates message and comprises E2E call follow option, and comprise/send tracking extended field at the protocol sig-naling messages going to next network element, wherein, this tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity.

Alternatively, the transmitter 8400 of NE8000 can determine whether comprising tracking extended field at protocol sig-naling messages based on carrier policy (such as, list in the step 410 of the first embodiment those).

The tracking data reporter 8300 of NE8000 is according to track record session, and record is output tracking data also, until occur stopping trigger event.

In step S805, when occurring stopping trigger event, the tracking data reporter 8300 of NE8000 stops track record session.

On the other hand, all relevant tracked data are recorded in trace file by the tracking data reporter 8300 of NE8000, and after the described track record session of stopping, in step S806 (optionally), recorded trace file, according to following the tracks of the address of collecting entity, outputs to follow the tracks of and collects entity by the tracking data reporter 8300 of NE8000.

On the other hand, the tracking data reporter 8300 real time record tracking data of NE8000, and according to following the tracks of the address of collecting entity, tracking data being outputted in real time follow the tracks of and collecting entity.In this case, optional step S806 is optional.

In this case, in first to fourth embodiment, following the tracks of and activate message can be the MAP-ACTIVATE_TRACE_MODE message from HSS or the trace session activation message from EMS; And in the first to the 3rd embodiment, protocol sig-naling messages can be BICC/ISUPIAM message, or in the fourth embodiment, protocol sig-naling messages can be SIP:INVITE message.

Fig. 9 A is the schematic block diagram for the structure of exemplary network unit (NE) 9000 when being regarded as the MGCF/I-CSCF in TSC/GMSC or HSS in the TSC/GMSC in above-mentioned first embodiment, above-mentioned second embodiment, above-mentioned 3rd embodiment or the S-CSCF in above-mentioned 4th embodiment; And Fig. 9 B is the flow chart for the operation of exemplary network unit (NE) 9000 when being regarded as the MGCF/I-CSCF in TSC/GMSC or HSS in the TSC/GMSC in above-mentioned first embodiment, above-mentioned second embodiment, above-mentioned 3rd embodiment or the S-CSCF in above-mentioned 4th embodiment.

With reference to Fig. 9 A, NE9000 comprises receiver 9100, tracking data reporter 9300 and transmitter 9400.

Next, the operation of the unit of NE9000 is described with reference to Fig. 9 B.

In step S901, transmitter 9100 receiving package of NE9000 follows the tracks of the first protocol sig-naling messages of extended field containing first, and described first follows the tracks of extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity.

In step S902, the tracking data reporter 9300 of NE9000 is with track reference and the track record session reference that receives, start track record session, and the tracking data reporter 9300 of NE9000 follows the tracks of extended field according to described first, record is output tracking data also.

In step S903, the transmitter 9400 of NE9000 comprises/sends second at the second protocol signaling message going to next network element and follows the tracks of extended field, it is identical that wherein said second tracking extended field and described first follows the tracks of extended field, or obtain from described first tracking extended field.

Alternatively, the transmitter 9400 of NE9000 can determine whether comprise the second tracking extended field at second protocol signaling message based on its carrier policy (such as, list in the step 410 of the first embodiment those).

The tracking data reporter 9300 of NE9000 is according to track record session, and record is output tracking data also, until there is the stopping trigger event for track record session.

In step S904, when there is the stopping trigger event for track record session, the tracking data reporter 9300 of NE9000 stops track record session.

On the other hand, all relevant tracked data are recorded in trace file by the tracking data reporter 9300 of NE9000, and after the described track record session of stopping, in step S905 (optionally), recorded trace file, according to following the tracks of the address of collecting entity, outputs to follow the tracks of and collects entity by the tracking data reporter 9300 of NE9000.

On the other hand, the tracking data reporter 9300 real time record tracking data of NE9000, and according to following the tracks of the address of collecting entity, tracking data being outputted in real time follow the tracks of and collecting entity.In this case, optional step S905 is optional.

In this case, first and the 3rd in embodiment, first protocol sig-naling messages can be BICC/ISUPIAM message, in a second embodiment, first protocol sig-naling messages can be BICC/ISUPIAM message (for TSC/GMSC) or MAPSRI message (for HSS), in the fourth embodiment, the first protocol sig-naling messages can be SIP:INVITE message; In a first embodiment, second protocol signaling message can be BICC/ISUPIAM message, in a second embodiment, second protocol signaling message can be MAPSRI message (for GMSC) or MAPPRN message (for HSS) or BICC/ISUPIAM message (for TSC/GMSC), or in the third and fourth embodiment, second protocol signaling message can be SIP:INVITE message.

Figure 10 A is the schematic block diagram for the structure during S-CSCF of exemplary network unit (NE) A000 in the T-MSC be regarded as in above-mentioned first and second embodiments or above-mentioned third and fourth embodiment; And Figure 10 B is the flow chart for the operation during S-CSCF of exemplary network unit (NE) A000 in the T-MSC be regarded as in above-mentioned first and second embodiments or above-mentioned third and fourth embodiment.

With reference to Figure 10 A, NEA000 comprises receiver A100, tracking data reporter A300 and transmitter A400.

Next, the operation of the unit of NEA000 is described with reference to Figure 10 B.

In step S1001, the receiver A100 receiving package of NEA000 is containing following the tracks of extended field at interior protocol sig-naling messages, and tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity.

In step S1002, the tracking data reporter A300 of NEA000, with track reference and track record session reference, starts track record session, and the tracking data reporter A300 of NEA000 is according to tracking extended field, and record is output tracking data also.

The tracking data reporter A300 of NEA000 is according to track record session, and record is output tracking data also, until there is the stopping trigger event for track record session.

In the step s 1003, when occurring the stopping trigger event for track record session, the tracking data reporter A300 of NEA000 stops track record session.

On the other hand, all relevant tracked data are recorded in trace file by the tracking data reporter A300 of NEA000, and after the described track record session of stopping, in step S1004 (optionally), recorded trace file, according to following the tracks of the address of collecting entity, outputs to follow the tracks of and collects entity by the tracking data reporter A300 of NEA000.

On the other hand, the tracking data reporter A300 real time record tracking data of NEA000, and according to following the tracks of the address of collecting entity, tracking data being outputted in real time follow the tracks of and collecting entity.In this case, optional step S1004 is optional.

In this case, in a first embodiment, this protocol sig-naling messages can be BICC/ISUPIAM message, in a second embodiment, this protocol sig-naling messages can be MAPPRN message or BICC/ISUPIAM message, or in the third and fourth embodiment, this protocol sig-naling messages can be SIP:INVITE message.

More than describe and only give the preferred embodiments of the present invention, and be not intended to limit the present invention in any way.Therefore, scope of the present invention should be included in any amendment in spirit of the present invention and principle, replacement and improvement.

Claims

1. a network element, as the source-end networks unit for end to end circuit service call following function, described network element comprises:

Receiver, be configured for receiving package and activate message containing tracing control and configuration parameter in interior tracking, wherein, described tracing control and configuration parameter at least comprise track reference, beginning trigger event, stop trigger event, end-to-end call follow option and follow the tracks of the address of collecting entity;

Memory device, is configured for and stores the tracing control that receives of receiver and configuration parameter;

Tracking data reporter, is configured for and starts trace session with track reference, when occurring starting trigger event, starts track record session with track record session reference, and according to stored tracing control and configuration parameter record and output tracking data; And

Transmitter, be configured for detecting and tracking activation message and comprise end-to-end call follow option, and comprise/send tracking extended field at the protocol sig-naling messages going to next network element, wherein, this tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity

Wherein, described tracking data reporter is also configured for when occurring stopping trigger event, stops track record session.

2. network element according to claim 1, wherein

Described tracking data reporter is configured for and is recorded in trace file by all relevant tracked data, and after the described track record session of stopping, described tracking data reporter is configured for, according to following the tracks of the address of collecting entity, recorded trace file is outputted to tracking collection entity.

3. network element according to claim 1, wherein

Described tracking data reporter is configured for: real time record tracking data, and according to following the tracks of the address of collecting entity, tracking data is outputted to tracking collection entity in real time.

4. the network element according to any one of claim 1-3, wherein

Described network element is source mobile handoff central server;

It is the MAP-ACTIVATE_TRACE_MODE message from home subscriber servers or the trace session activation message from element manager server that described tracking activates message; And

Described protocol sig-naling messages is BICC/ISUPIAM message or SIP:INVITE message.

5. a network element, as the intermediate network elements for end to end circuit service call following function, described network element comprises:

Receiver, is configured for receiving package follows the tracks of extended field the first protocol sig-naling messages containing first, and described first follows the tracks of extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity;

Tracking data reporter, is configured for the track reference that receives and the track record session reference that receives starts track record session, and follows the tracks of extended field record and output tracking data according to described first; And

Transmitter, be configured for and comprise/send the second tracking extended field at the second protocol signaling message going to next network element, it is identical that wherein said second tracking extended field and described first follows the tracks of extended field, or obtain from described first tracking extended field

Wherein, described tracking data reporter is also configured for when there is the stopping trigger event for track record session, stops track record session.

6. network element according to claim 5, wherein

7. network element according to claim 5, wherein

8. the network element according to any one of claim 5-7, wherein

Described network element is Gateway Mobile Switching Center server or sends main dispatching centre;

Described first protocol sig-naling messages is BICC/ISUPIAM message; And

Described second protocol signaling message is BICC/ISUPIAM message or MAPSRI message.

9. the network element according to any one of claim 5-7, wherein

Described network element is attaching position register;

Described first protocol sig-naling messages is MAPSRI message; And

Described second protocol signaling message is MAPPRN message.

10. the network element according to any one of claim 5-7, wherein

Described network element is MGCF entity;

Described first protocol sig-naling messages is BICC/ISUPIAM message; And

Described second protocol signaling message is SIP:INVITE message.

11. network element according to any one of claim 5-7, wherein

Described network element is service call session control function entity;

Described first protocol sig-naling messages is SIP:INVITE message; And

Described second protocol signaling message is SIP:INVITE message.

12. 1 kinds of network element, as the egress network element for end to end circuit service call following function, described network element comprises:

Receiver, be configured for receiving package containing following the tracks of extended field at interior protocol sig-naling messages, described tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity; And

Tracking data reporter, the track reference being configured for receive starts track record session with the track record session reference received, according to following the tracks of extended field record and output tracking data, and when there is the stopping trigger event for track record session, stop track record session.

13. network element according to claim 12, wherein

14. network element according to claim 12, wherein

15. network element according to any one of claim 12-14, wherein

Described network element is egress mobile handoff central server; And

Described protocol sig-naling messages is BICC/ISUPIAM message or MAPPRN message.

16. network element according to any one of claim 12-14, wherein

Described network element is service call session control function entity; And

Described protocol sig-naling messages is SIP:INVITE message.

17. 1 kinds for providing the method for end to end circuit service call following function, described method comprises step:

Receiving package activates message containing tracing control and configuration parameter in interior tracking, and wherein, described tracing control and configuration parameter at least comprise track reference, beginning trigger event, stop trigger event, end-to-end call follow option and follow the tracks of the address of collecting entity;

Store the tracing control and configuration parameter that receive;

Trace session is started with track reference;

When occurring starting trigger event, start track record session with track record session reference;

According to stored tracing control and configuration parameter record/output tracking data;

Comprise at the protocol sig-naling messages going to next network element/send and follow the tracks of extended field, wherein, this tracking extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity; And

When occurring stopping trigger event, stop track record session.

18. methods according to claim 17, wherein

All relevant tracked data are recorded in trace file, and after the described track record session of stopping, described method also comprises step: according to following the tracks of the address of collecting entity, recorded trace file is outputted to tracking collection entity.

19. methods according to claim 17, wherein

Real time record tracking data, and according to following the tracks of the address of collecting entity, tracking data is outputted to tracking collection entity in real time.

20. methods according to any one of claim 17-19, wherein

Described method is adopted by source mobile handoff central server;

21. 1 kinds for providing the method for end to end circuit service call following function, described method comprises:

Receiving package follows the tracks of the first protocol sig-naling messages of extended field containing first, and described first follows the tracks of extended field at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity;

Track record session is started with the track reference received and the track record session reference that receives;

Extended field record/output tracking data are followed the tracks of according to described first;

Comprise/send second at the second protocol signaling message going to next network element and follow the tracks of extended field, it is identical that wherein said second tracking extended field and described first follows the tracks of extended field, or obtain from described first tracking extended field; And

When there is the stopping trigger event for track record session, stop track record session.

22. methods according to claim 21, wherein

23. methods according to claim 21, wherein

24. methods according to any one of claim 21-23, wherein

Described method is by Gateway Mobile Switching Center server or send main dispatching centre employing;

Described first protocol sig-naling messages is BICC/ISUPIAM message; And

25. methods according to any one of claim 21-23, wherein

Described method is adopted by attaching position register;

Described first protocol sig-naling messages is MAPSRI message; And

Described second protocol signaling message is MAPPRN message.

26. methods according to any one of claim 21-23, wherein

Described method is adopted by MGCF entity;

Described first protocol sig-naling messages is BICC/ISUPIAM message; And

Described second protocol signaling message is SIP:INVITE message.

27. methods according to any one of claim 21-23, wherein

Described method is adopted by service call session control function entity;

Described first protocol sig-naling messages is SIP:INVITE message; And

Described second protocol signaling message is SIP:INVITE message.

28. 1 kinds for providing the method for end to end circuit service call following function, described method comprises:

Receiving package is containing following the tracks of extended field at interior protocol sig-naling messages, and described protocol sig-naling messages at least comprises track reference, track record session reference and follows the tracks of the address of collecting entity;

Track record session is started with the track reference received and the track record session reference received;

According to tracking extended field record/output tracking data; And

29. methods according to claim 28, wherein

30. methods according to claim 28, wherein

31. methods according to any one of claim 28-30, wherein

Described method is adopted by egress mobile handoff central server; And

32. methods according to any one of claim 28-30, wherein

Described method is adopted by service call session control function entity; And

Described protocol sig-naling messages is SIP:INVITE message.