CN101212814A - Service processing method, system and network element after network element data failure or failure occurs - Google Patents

Abstract

The invention relates to a service processing method, system and network element after network element data failure or failure occurs. The method includes sending a service request message to a service network element in the network when a calling terminal, and storing When the user data of the calling terminal fails, a data invalidation message is sent to the calling terminal. When the service network element receives a service request message from the network to the called terminal and the user data becomes invalid, the service network element returns a data invalidation message of the called terminal to the network. The system includes a service request sending end, a service request receiving end and a service network element set in the network. The service network element is provided with a user data storage module, a user data comparison module and a user data sending end for sending the service request. An invalidation message sending module for invalidation messages. When the network element containing the user registration data is abnormal and the user registration data becomes invalid, the present invention can shorten the unavailable time of the user service and quickly recover the user service.

Description

Service processing method, system and network element after network element data failure or failure occurs

technical field

The invention relates to a service processing method, in particular to a service processing method after network element data fails in an IMS network and a service processing method after a network element fails. The present invention also relates to a service processing system, especially a system for performing service processing in an IMS network when network element data fails. The present invention also relates to a service processing network element, especially when a network element fails. A network element for business processing belongs to the technical field of communication.

Background technique

IMS is also called IP Multimedia Subsystem. IMS is a subsystem superimposed on the existing packet domain in the WCDMA network added in the third generation mobile communication standardization partnership project (referred to as 3GPP) R5 phase. For the bearer channel of order and media transmission, the SIP protocol (Session Initiation Protocol, Session Initiation Protocol) is introduced as a service control protocol. By utilizing the characteristics of SIP, which is simple, easy to expand, and convenient for media combination, by separating service control from bearer control, it provides rich multimedia business. The main functional entities in the IMS include the call control entity CSCF that controls functions such as user registration and session control, the home subscriber server HSS that centrally manages user subscription data, and the application server AS that provides various service logic control functions.

Fig. 1 is a network structure diagram of an IMS network. Among them, AS is an application server, HSS is a home subscriber server, I-CSCF is an inquiry call control entity (also called inquiry CSCF), P-CSCF is a proxy call control entity (also called proxy CSCF), and S-CSCF is a service call control entity. Entity (also called serving CSCF), UE is user equipment. As shown in Figure 1, the user’s service process is that after the user terminal UE is started, it first initiates the registration process to the IMS network, and the IMS network will save the user’s registration data and registration status in the corresponding network element after accepting the user’s registration request Information such as P-CSCF, S-CSCF, AS, and HSS all store user registration information. The user terminal will carry a registration period parameter in the registration message. After the user terminal successfully registers, it will periodically initiate a re-registration process to the IMS network to update the user's registration data and registration status. Only users who are registered on the corresponding network elements in the IMS network can perform corresponding user services, such as initiating a call as a calling party or accepting a call as a called party.

FIG. 2 is a flow chart of the user's service execution process in the IMS network described in the 3GPP standard. Specific steps are as follows:

1. After the user terminal is started, it sends a registration message Register to the P-CSCF;

2. The P-CSCF saves the user-related data locally, and forwards the registration message to the I-CSCF of the user's home domain;

3. The I-CSCF sends a request message UAR to the HSS to query the S-CSCF that can provide services for the user;

4. The HSS returns a response message UAA to the I-CSCF, carrying the S-CSCF that can provide services for the user;

5. The I-CSCF forwards the registration request message Register to the selected S-CSCF;

6. The S-CSCF sends a request message SAR to the HSS, requesting the user's subscription data from the HSS;

7. The HSS returns a response message SAA to the S-CSCF, carrying the subscription data of the user;

8. The S-CSCF initiates a third-party registration to the corresponding AS according to the user's subscription data, and saves the user-related data locally;

9. The AS returns a successful registration response of 200;

10. The S-CSCF returns a successful registration response;

11. The I-CSCF returns a successful registration response;

12. The P-CSCF returns a successful registration response;

13. After the user has registered successfully, the corresponding business process can be started;

14. When the UE registration period expires, the UE will initiate a re-registration process to update the user's registration data and registration status in the IMS network, so that the user can continue to perform business processes.

In the prior art, the UE initiates a registration request to the IMS network, and after successful registration, it will not actively initiate a re-registration process within a registration period. If a network element (P-CSCF, S-CSCF, AS, etc.) containing user registration data in the IMS network is abnormal during this period, causing the user registration data on the network element to become invalid (for example, if a network element restarts, User registration data lost). At this time, if the UE initiates a service request, the network element will consider that the UE is not registered and reject the user's service request, and the UE cannot perform calling services during the registration period. Moreover, as the called user, due to the inconsistency of user registration data on each network element (some network elements have user registration data and are registered, and some network elements have no user registration data), it is impossible to locate the called user , and cannot execute the corresponding called service.

In short, if a network element including user registration data in the IMS network is abnormal, the user registration data becomes invalid, and the user cannot perform corresponding services within a registration period. In the current standard, there is no mechanism to notify the UE to initiate re-registration in this case.

In addition, in the prior art, if a network element fails, there is no corresponding service processing method to terminate the current service process, the network service is in a stagnant state, and the user's network service cannot be restored in time.

Contents of the invention

The purpose of the present invention is to overcome the deficiencies in the prior art, so that when the network element containing user registration data in the IMS network is abnormal and causes the user registration data to fail, the user can quickly restore the corresponding service, or send data invalidation information , so that the network will not be in an unresponsive state and ensure the smooth execution of services.

Another object of the present invention is to provide a service processing method after a network element fails, which can restore the user's network service in time when the network element fails.

For this reason, the present invention provides a kind of service processing method after network element data failure, comprises the following steps:

When the calling terminal sends a service request message to a service network element in the network, and the user data of the calling terminal stored in the service network element becomes invalid, the service network element sends a data invalidation message to the calling terminal;

The service network element may also send a trigger message for re-registration to the calling end while sending the data invalidation message. After receiving the trigger message, the calling end initiates an operation of restoring user data to the service network element.

The operation of restoring user data initiated by the calling terminal may specifically be:

The calling terminal initiates a re-registration operation request to the service network element according to the trigger message; the service network element performs a re-registration operation on the calling terminal, and uses the re-registered user data to register the stored user data. The data is updated, and after the recovery of the user data is completed, the service network element performs corresponding service processing according to the service request message.

The present invention also provides another service processing method after the network element data fails, including the following steps:

When the service network element receives a service request message from the network to the called terminal, and the user data of the called terminal stored in the service network element becomes invalid, the service network element returns the The data invalidation message of the called end.

After the network receives the data invalidation message, it can judge whether the service request can be transferred to another network that does not need to perform communication operations based on the called user data stored in the network element according to the content of the service request message, If yes, convert the service request into a request message compatible with the other network, and hand over the other network to complete the corresponding service operation; if not, forward the data invalidation message to the service request message the sender.

The present invention also provides a service processing system after the network element data fails, including a service request sending end, a service request receiving end and a service network element arranged in the network, and the service network element is provided with a user data storage module and a user The data comparison module is characterized in that the service network element is also provided with an invalidation message sending module for sending a user data invalidation message to the service request sending end.

The service network element may also be provided with a trigger message sending module for sending a re-registration message according to the user data invalidation message and a re-registration module for restoring user data.

The network may also be provided with a service request judging module that performs service judgment according to the user data invalidation message and the service request message sent by the service request sending end, and the service request judging module is used to judge whether the service request is It is possible to transfer to another network that does not need to perform communication operations based on the user data stored in the user data storage module; the network also has a service that transfers the service request to the other network for communication operations Request a conversion module.

The network may also be provided with an invalidation message forwarding module that forwards the user data invalidation message to the service request sending end.

The service request sending end and the service request receiving end may be user terminals or information processing network elements in the network.

The service network element may be a proxy call control entity, an inquiry call control entity or a serving call control entity.

The present invention also provides a service processing method after a network element fails, including:

After receiving the service request message, the previous hop network element of the failed network element returns a network element failure message to the calling terminal that sent the service request message.

The present invention also provides a service processing network element after a network element fails, including:

A service request message receiving module, configured to receive a service request message;

The network element failure message sending module is used to return a network element failure message to the calling terminal that sent the service request message when the next hop network element of the current network element fails.

Based on the above technical scheme, the present invention has the following advantages:

The present invention solves the deficiencies in the 3GPP standard. Anomalies occur in network elements (P-CSCF, S-CSCF, AS, etc.) containing user registration data, resulting in failure of user registration data on network elements. After receiving the user data invalidation message after the request, the user terminal can identify the user data invalidation message, and initiate a re-registration process according to the user data invalidation message. If the user data invalidation message is received after the service request sent by other network elements, other network elements can identify the user data invalidation message, and trigger the user's unregistered service according to the user data invalidation message. Through this process, the unavailable time of user services can be shortened and user services can be quickly restored. And through the service processing method after the network element fails, the current service process can be terminated in time when the network element fails, and the calling terminal can be notified, thereby reducing the waste of network element system resources

The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments.

Description of drawings

FIG. 1 is a network structure diagram of an IMS network in the prior art;

FIG. 2 is a flow chart of the user's service execution process in the IMS network described by the 3GPP standard in the prior art;

3 is a schematic diagram of a service processing system after network element data failure according to Embodiment 4 of the present invention;

FIG. 4 is a schematic diagram of a service processing system after network element data failure according to Embodiment 5 of the present invention;

FIG. 5 is a first schematic diagram of a service processing system after network element data failure according to Embodiment 6 of the present invention;

FIG. 6 is a second schematic diagram of the service processing system after network element data failure according to Embodiment 6 of the present invention;

FIG. 7 is a schematic diagram of a service processing system after network element data failure according to Embodiment 7 of the present invention;

FIG. 8 is a signaling flow chart of Embodiment 1 of the service processing method after a network element fails in the present invention;

FIG. 9 is a signaling flowchart of Embodiment 2 of the service processing method after a network element fails in the present invention;

FIG. 10 is a schematic structural diagram of Embodiment 1 of a service processing network element after a network element fails in the present invention;

FIG. 11 is a schematic structural diagram of Embodiment 2 of a service processing network element after a network element fails in the present invention;

FIG. 12 is a schematic structural diagram of Embodiment 3 of a service processing network element after a network element fails in the present invention.

Detailed ways

Example 1

The service processing method after network element data failure of the present invention comprises the following steps:

When the calling terminal sends a service request message to a service network element in the network, and the user data of the calling terminal stored in the service network element becomes invalid, the service network element sends a data invalidation message to the calling terminal. The calling end can initiate re-registration immediately, or re-register when the registration period comes.

Example 2

In order to enable the calling terminal to resume normal communication services in time, the service network element may also send a trigger message for re-registration to the calling terminal while sending the data invalidation message; the calling terminal does not need to wait until The re-registration is initiated only when the registration period is up, so that the business can be resumed in time. After the service network element sends a data invalidation message, the calling terminal can initiate an operation to restore user data, and the operation can be specifically: the calling terminal initiates a re-registration operation to the service network element according to the trigger message request; the service network element re-registers the calling terminal, and uses the re-registered user data to update the saved user data. After the user data is restored, the service network element follows the service Request messages for corresponding business processing.

Example 3

Embodiment 1 only solves the problem of the calling terminal after data failure, and since the called terminal and the calling terminal may not be within the coverage of the same service network element, its processing method is different from that of the calling terminal. When the service network element receives a service request message from the network to the called terminal, and the user data of the called terminal stored in the service network element becomes invalid, the service network element returns the The data invalidation message of the called end.

After the network receives the data invalidation message, it can judge whether the service request can be transferred to another network that does not need to perform communication operations according to the called user data stored in the network element according to the content of the service request message, If so, convert the service request into a request message suitable for the other network, and transfer it to the other network to complete the corresponding service operation, for example: the network receives a user data invalidation message, which can trigger the user's unregistered Business, send prompt message and response message. The unregistered service may be forwarding the call to the user's voice mailbox, forwarding the call to other specified users, sending a prompt tone to the calling user, and so on. If the service request cannot be transferred to another network, the data invalidation message is forwarded to the sender of the service request message.

Example 4

As shown in Figure 3, this embodiment is a service processing system after the network element data in the IMS network of the present invention fails, including a service request sending end 2, a service request receiving end 3 and a service network element 1 set in the IMS network. The service network element is provided with a user data storage module and a user data comparison module, and the service network element is also provided with an invalidation message sending module 11 for sending a user data invalidation message to the service request sending end.

Example 5

As shown in Figure 4, the difference from Embodiment 4 is that the service network element is also provided with a trigger message sending module for sending a re-registration message according to the user data invalidation message and a module for restoring user data. Re-register module 12.

Example 6

As shown in Figure 5 and Figure 6, on the basis of Embodiment 4 and Embodiment 5, a service is added in the network according to the user data invalidation message and the service request message sent by the service request sender. Judging business request judging module 4, the business request judging module is used to judge whether the business request can be transferred to another network that does not need to carry out communication operations according to the user data stored in the user data saving module; the network There is also a service request conversion module 5 for transferring the service request to the other network for communication operation.

Example 7

As shown in FIG. 7 , the difference from Embodiment 5 is that the network further includes an invalidation message forwarding module 6 that forwards the user data invalidation message to the service request sending end. This module is mainly used when the calling user and the called user are not within the coverage of the same network element, and when the data of the called user fails, the network element where the calling user or the main user is located can be notified through this module.

In all the above-mentioned embodiments, the service request sending end and the service request receiving end may be user terminals or information processing network elements in the network, such as: call control entity CSCF, application server AS; the service network element may be a proxy call Controlling Entity, Inquiry Calling Controlling Entity or Serving Calling Controlling Entity.

The service processing method after the network element fault data fails in the embodiment of the present invention includes the following steps:

After receiving the service request message, the previous hop network element of the failed network element terminates the previous service process, and returns a network element failure message to the calling terminal that sent the service request message.

Wherein, the network element failure message returned by the previous hop network element of the failed network element to the calling terminal may include information triggering the calling terminal to re-register. After receiving the message, the calling terminal re-registers, so that the faulty network element can be avoided in the new service.

Among them, for some network elements, there is a fault detection mechanism between the network elements (for example, the network elements detect each other through the heartbeat function to see if the other party has a fault), and through the fault detection mechanism, the network element can know whether the next network element has a fault. Therefore, the previous hop network element of the failed network element can detect that the failed network element has failed through the failure detection mechanism.

For a network element without a fault detection mechanism, service processing can be performed in the following manner: After receiving the service request message, the previous hop network element of the faulty network element forwards the service request message to the next hop network element. If no response message from the failed network element is received within the set time, the previous service process is terminated, and a network element failure message is returned to the calling terminal that sent the service request message. For example, when an S-CSCF fails and a user registered on the failed S-CSCF initiates a service request, if the last hop network element of the S-CSCF is the P-CSCF, the P-CSCF sends the caller The terminal returns an invalidation message.

Referring to FIG. 8, it is a signaling flow chart of Embodiment 1 of the service processing method after a network element fails in the present invention, including the following steps:

Step A1, the calling terminal initiates an initial service request; the network element can judge whether it is the network element on the calling side through the parameter flag in the message.

Step A2, the last hop network element of the failed network element detects that its next hop network element (i.e. the failed network element) has broken down, then terminates the previous service process, and sends the service request message to the master Call the network element failure message returned by the terminal. The upper hop network element of the faulty network element determines the address of the next hop network element according to the routing information in the message, and can detect the status of the next hop network element before forwarding the service request to the next hop.

In step A3, the calling terminal re-initiates registration after receiving the network element failure message.

Referring to FIG. 9, it is a signaling flow chart of Embodiment 2 of the service processing method after a network element fails in the present invention, including the following steps:

Step B1, the calling terminal initiates an initial service request;

Step B2, the upper hop network element of the failed network element forwards the initial service request message to its next hop network element (that is, the failed network element);

Step B3: If no response message is received within the preset time, the previous service process is terminated, and a network element failure message is returned to the calling terminal that sent the service request message.

Step B4. After receiving the network element failure message, the calling terminal re-initiates the registration.

Referring to FIG. 10 , it is a schematic structural diagram of Embodiment 1 of a service processing network element after a network element fails in the present invention, including:

The service request message receiving module C1 is configured to receive the service request message.

The network element failure message sending module C2 is used to return a network element failure message to the calling terminal that sent the service request message when the next-hop network element of the current network element fails.

Referring to FIG. 11 , it is a schematic structural diagram of Embodiment 2 of a service processing network element after a network element fails in the present invention. On the basis of FIG. 10 , it also includes:

The fault detection module C3 is configured to perform fault detection on the next-hop network element of the current network element, and when a fault is detected, trigger the network element failure message sending module to send a network element failure message. The service request message received by the service request message receiving module includes the routing information of the next-hop network element of the current network element, and the fault detection module can determine the next-hop network element according to the routing information, and perform fault detection on it, and then, can The sending instruction triggers the network element failure message sending module to send the network element failure message.

Referring to FIG. 12 , it is a schematic structural diagram of Embodiment 2 of a service processing network element after a network element fails in the present invention. On the basis of FIG. 10 , it also includes:

The service request message forwarding module C4 is used to forward the service request message to the next-hop network element of the current network element;

The response message reception detection module C5 is used to detect whether a response message is received within a preset time, and if the response message returned by the next-hop network element is not received, trigger the network element failure message sending module to A network element failure message returned by the calling terminal that sent the service request message. After the service request message forwarding module forwards the service request message, it will trigger the response message reception detection module to detect the response message, if the corresponding response message is not received within the preset time (can be determined by setting a timer) completed), the network element failure message sending module is triggered to send the failure message.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention without limitation. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be The scheme shall be modified or equivalently replaced without departing from the spirit and scope of the technical scheme of the present invention.

Claims (18)

1. the method for Business Processing is characterized in that after a network element data lost efficacy, and comprised the steps:

When the business network element of calling terminal in network sends business request information, and the user data of the described calling terminal of preserving in this business network element was when losing efficacy, and described business network element sends data failure message to described calling terminal.

2. method according to claim 1, it is characterized in that described business network element sends described data failure message, and send the triggering message that is used to re-register to described calling terminal, after described calling terminal is received described triggering message, initiate the operation of restoring user data to described business network element.

3. method according to claim 2 is characterized in that, the operation of the restoring user data that described calling terminal is initiated is specially:

The operation requests that described calling terminal re-registers to described business network element initiation according to described triggering message; Described business network element re-registers operation to this calling terminal, and this user data of being preserved is upgraded with the user data that re-registers, after finishing described user data recovery, described business network element carries out corresponding service processing according to described business request information.

4. the method for Business Processing is characterized in that after a network element data lost efficacy, and comprised the steps:

When business network element receives automatic network, the business request information of initiating to called end, and the user data of the described called end of preserving in this business network element was when losing efficacy, and described business network element returns the data failure message of described called end to described network.

5. method according to claim 4, it is characterized in that, described network is after receiving described data failure message, content according to described business request information, judge another network that whether this service request can change over to does not need to carry out according to preservation called party data in the network element communication operation, if can, then this service request is converted to the request message that adapts with described another network, and delivers by this another network and finish the corresponding service operation; If can not, then with the transmitting terminal of described data failure forwards to this business request information.

6. transaction processing system after a network element data lost efficacy, comprise the service request transmitting terminal, service request receiving terminal and the business network element that are arranged in the network, be provided with user data in this business network element and preserve module and user data comparing module, it is characterized in that, also be provided with the thrashing message sending module that is used for sending the user data thrashing message in the described business network element to described service request transmitting terminal.

7. system according to claim 6 is characterized in that, also is provided with in the described business network element according to described user data thrashing message, sends the module that re-registers that re-registers the triggering message transmission module of message and be used to carry out the user data recovery.

8. according to claim 6 or 7 described systems, it is characterized in that, also be provided with the business request information that is sent according to described user data thrashing message and described service request transmitting terminal in the described network and carry out the professional service request judge module of judging, this service request judge module is used for judging whether described service request can change over to does not need to preserve another network that user data that module preserves carries out communication operation according to described user data; Also be provided with in the described network and change described service request over to service request modular converter that described another network communicates operation.

9. system according to claim 8 is characterized in that, also is provided with thrashing message forwarding module from described user data thrashing message to described service request transmitting terminal that transmit in the described network.

10. according to the arbitrary described system of claim 6-9, it is characterized in that described service request transmitting terminal and service request receiving terminal are the information processing network element in user terminal or the network.

11., it is characterized in that described business network element is agent call controlled entity, query call controlled entity or service call controlled entity according to the arbitrary described system of claim 6-9.

12. the method for the Business Processing after a network element breaks down is characterized in that, comprising:

After the previous dive network element of the network element that breaks down receives business request information, and the network element thrashing message that returns to the calling terminal that sends described business request information.

13. method according to claim 12 is characterized in that, the network element thrashing message that the previous dive network element of the network element that breaks down returns to described calling terminal comprises the information that described calling terminal is registered again that triggers.

14. method according to claim 12 is characterized in that, also comprises: the previous dive network element of the described network element that breaks down detects the described network element that breaks down by fault detection mechanism fault has taken place.

15. method according to claim 12, it is characterized in that, after the previous dive network element of the described network element that breaks down receives business request information, jump network element to next and transmit described service request, if in the predefined time, do not receive the response message of the described network element that breaks down, operation flow before then stopping, and the network element thrashing message that returns to the calling terminal that sends described business request information.

16. the business processing network element after a network element breaks down is characterized in that, comprising:

The business request information receiver module is used to receive business request information;

Network element thrashing message sending module is used for jumping under the situation that network element breaks down in next of current network, the network element thrashing message that returns to the calling terminal that sends described business request information.

17. business processing network element according to claim 16 is characterized in that, also comprises:

Fault detection module is used for next jumping network element of current network is carried out fault detect, after detecting fault, triggers described network element thrashing message sending module and sends the network element thrashing message.

18. business processing network element according to claim 16 is characterized in that, also comprises:

The business request information forwarding module, next that is used for to current network jumped network element forwarding business request information;

Response message receives detection module, be used in the predefined time, detecting whether receive response message, if do not receive the response message that described next jumping network element returns, then trigger the network element thrashing message that described network element thrashing message sending module returns to the calling terminal that sends described business request information.

Images