WO2006053502A1

WO2006053502A1 - A method for ensuring the information consistency between the network nodes

Info

Publication number: WO2006053502A1
Application number: PCT/CN2005/001952
Authority: WO
Inventors: Yajuan Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2004-11-18
Filing date: 2005-11-18
Publication date: 2006-05-26
Also published as: CN100388864C; CN1780482A

Abstract

A method for ensuring the information consistency between the network nodes comprises that save the route information of the user acquired by Serving Call Session Control Function (S-CSCF) entity after S-CSCF entity acquires the user’s route information; S-CSCF entity acquires the user route information and the user profile information while S-CSCF entity restarts after a failure; S-CSCF informs the service control platform to implement the service control procedure corresponding to the de-registration of the user according to the acquired user profile information and informs the user to implement the de-registration procedure according to the acquired route information. The present invention ensures the information consistency between every network nodes so that the reliability and the security of the IMS network is improved greatly.

Description

Method for ensuring information consistency between network nodes

The present invention relates to mobile communication technologies, and in particular, to a method for ensuring information consistency between network nodes after a service call session control function entity fails to restart in an IP Multimedia Subsystem (IMS). Background of the invention

The IMS network is a network subsystem that implements IP multimedia communication control introduced on the packet bearer network by the 3rd Generation Mobile Communications Standardization Partnership Project (3GPP). The IMS network can provide a variety of access technologies, shield user access methods based on personalized user data, control the openness of business capabilities, and provide IP multimedia communication experience. The IMS network uses a packet domain (PS) or other IP access network as its bearer channel for upper layer control signaling and media transmission.

The main functional entities in the IMS include: Call Session Control Function (CSCF) entity, Media Gateway Control Function (MGCF, Media Gateway Control Function) entity, Media Resource Function (MRF), and Ownership Signing User Server (HSS, Home Subscriber Server), etc. Among them, HSS is the most important database for each user, and stores all the information related to user subscription, including: user identification, number and addressing information, user security information, user location information, and user profile information. ( user profile information ) and so on. A home network can have one or more HSSs, depending on the number of mobile subscription users, the capacity of network devices, and the specific networking conditions. The CSCF entity can be divided into three logical entities: Service CSCF (S-CSCF, Serving CSCF), Proxy CSCF (P-CSCF, Proxy CSCF), and Query CSCF (I-CSCF, Interrogating CSCF). The S-CSCF entity is the service switching center of the IMS, performs session control, maintains the session state, and is responsible for management. User information, generating charging information, etc.; P-CSCF entity is an access point for users to access IMS, complete user registration, responsible for service quality of service (QoS) control and security management; I-CSCF entity is responsible for IMS domain Interworking, managing the allocation of S-CSCF, hiding network topology and configuration, generating billing data, etc.

At present, for the failure of the S-CSCF entity, there is a process of ensuring the consistency of information between the network nodes. The process is: When the S-CSCF entity is completely broken, the registration update mechanism in the existing IMS network can be registered in one After receiving the re-registration message of the S-CSCF entity after the end of the period, the S-CSCF device is informed that the S-CSCF device is broken, so that the current session is released; or, within one registration period, it is sent to the S- by any one. The CSCF entity's message does not receive a response from the S-CSCF entity and learns that the S-CSCF device is broken, thereby releasing the current session.

However, at present, there is only a measure for ensuring that the information between the network nodes is consistent when the S-CSCF entity is completely broken, and there is no guarantee that each network node is restarted when the S-CSCF entity temporarily fails. A consistent measure of information. In this way, when the S-CSCF entity restarts soon after the temporary failure, the information stored by the S-CSCF entity and related to the service execution is lost, but there is currently no mechanism to ensure that the restart event of the S-CSCF entity can be Other nodes interacting with the S-CSCF entity know that the node interacting with the S-CSCF entity continues to send the session related message to the S-CSCF entity according to the normal service logic, resulting in a series of errors, for example, the S-CSCF entity. After the restart, the message sent by other nodes will be processed as the first message received from the node, or the message sent by the other node may not be identified and discarded, or the S-CSCF entity follows the default manner. Processing and so on, which leads to a series of errors in the user's billing, security and service implementation, so that the IMS network can not meet the reliability requirements of the carrier-class network, and reduce the user's satisfaction with the IMS network. Summary of the invention

The main object of the present invention is to provide a method for ensuring information consistency between network nodes, so as to ensure information consistency between network nodes after a temporary failure restart of the S-CSCF entity.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for ensuring information consistency between network nodes includes the following steps:

After the service call session control function entity obtains the routing information of the user, the routing information of the user acquired by the service call session control function entity is saved;

B. When the service call session control function entity fails and restarts, the service call session control function entity acquires the routing information of the user and the profile information of the user;

C. The service call session control function entity notifies the service control platform to perform a service control process related to the user logout according to the obtained profile information of the user, and notifies the user to perform the logout process according to the obtained route information.

In step A, the serving call session control function entity acquires routing information of the user from a registration request sent by the user.

In step A, the step of saving the routing information of the user acquired by the serving call session control function entity includes: the serving call session control function entity transmitting the obtained routing information of the user to the home subscription subscriber server, the home subscription subscriber server Save the routing information of the user;

In step B, the step of the service call session control function entity acquiring the routing information of the user and the profile information of the user includes:

Bl, the service call session control function entity sends its own identity and restart information to the home subscription user server;

B2. The home subscriber network server determines whether there is information about the user including the service call session control function entity identifier in the self, and if yes, the saved user's routing information The information and the profile information of the user are sent to the service call session control function entity.

In step A, the step of the service call session control function entity transmitting the acquired routing information of the user to the home subscription user server includes: the service call session control function entity in the user registration process or after the user registration is completed The obtained routing information of the user is sent to the home subscription subscriber server.

The method further includes: adding a cell to the existing Cx-Put message; in step A, the step of the serving call session control function entity transmitting the routing information of the user to the home subscription subscriber server comprises: the service call The session control function entity carries the routing information of the user on the added cell in the Cx-Put message and sends it to the home subscriber server.

In step A, the step of the service call session control function entity transmitting the routing information of the user to the home subscriber network server includes: the service call session control function entity carrying the routing information of the user in a newly defined message To the home subscriber network.

In step A, the step of saving the routing information of the user acquired by the serving call session control function entity includes: the serving call session control function entity saving the acquired routing information of the user in its own non-volatile memory. ;

In step B, the step of the service call session control function entity acquiring the routing information of the user includes: the service call session control function entity acquiring routing information of the user from its non-volatile memory.

The step A further includes: the service call session control function entity acquiring the profile information of the user from the home subscription server during the user registration process, and saving the acquired profile information of the user in the user registration process Non-volatile memory;

In step B, the step of the service call session control function entity acquiring the profile information of the user includes: the service call session control function entity from its own non-volatile storage Get the user's profile information.

In step B, the step of the service call session control function entity acquiring the profile information of the user includes: the service call session control function entity sending its own identity and restart information to the home subscription user server; the home subscription user server determines itself Whether there is information including the user of the service call session control function entity identifier, and if so, the user's profile information is sent to the service call session control function entity.

The method further includes: adding a cell to an existing server allocation notification SAR message;

The step of the service call session control function entity transmitting the identity identification and restart information to the home subscription subscriber server includes: the service call session control function entity carrying its own identity and restart information in the Cx-Notify message. The element is sent to the home subscriber server.

The step of the service call session control function entity sending the identity identification and the restart information to the home subscription subscriber server includes: the service call session control function entity carrying its own identity and restart information in a newly defined message and sending the message to the home message Sign up for a user server.

The method further includes: when the service call session control function entity interacts with each home subscription user server during the user registration process, the address information of the home subscription user server of the interaction information is saved in the service call session control function entity itself. Volatile memory;

The serving call session control function entity performs the step of transmitting according to the address information of the home subscription subscriber server stored in its own non-volatile memory.

The method further includes: saving address information of all home subscriber network servers in a non-volatile memory of the serving call session control function entity;

The service call session control function entity is based on all saved in its own non-volatile memory The step of transmitting is performed by the address information of the home subscriber network.

The user information includes an identifier of the user;

The step B further includes: the home subscription subscriber server sending the cancellation reason to the service call session control function entity;

The step C further includes: the serving call session control function entity transmitting a logout reason to the user.

In step C, the step of the service call session control function entity notifying the user to perform the logout includes: the service call session control function entity notifying the corresponding proxy call session control function entity to perform a logout process according to the acquired routing information; The call session control function entity notifies the user to perform the logout process, and deletes the relevant registration information of the user saved in itself.

The step C further includes: the serving call session control function entity sending an indication of whether to re-register to the user, and the user decides whether to re-initiate registration to the network side according to the received indication of whether to re-register. process.

The step C further includes: the serving call session control function entity notifying the application server related to the user to perform processing related to the user's logout according to the obtained routing information of the user.

It can be seen that, in the present invention, the S-CSCF entity separately notifies the user and the service control platform to perform the logout process according to the obtained user routing information and the user description file, thereby ensuring the consistency of information on each network node in the IMS network, thereby avoiding A series of problems caused by the S-CSCF entity restart, which greatly improves the reliability and security of the IMS network operation. BRIEF DESCRIPTION OF THE DRAWINGS

1 is a flow chart of an embodiment for implementing the present invention.

2 is an embodiment of the present invention in which an S-CSCF entity acquires a user from an HSS Flowchart of routing information and user profile information.

Figure 3 is a flow diagram of the present invention when the S-CSCF entity obtains routing information for the user from itself. Mode for carrying out the invention

In the IMS network, the S-CSCF entity is a service switching center of the IMS network, performs session control, maintains session state, and is responsible for managing user information and generating charging information. Therefore, when the S-CSCF entity temporarily restarts, it must notify the node that the network side interacts with the S-CSCF entity to take corresponding measures to ensure session consistency. Otherwise, it will lead to session state and billing. a series of mistakes. Aiming at this feature, the present invention proposes a method for ensuring information consistency between network nodes. The core idea is: after the S-CSCF entity obtains the routing information of the user, the route of the user acquired by the S-CSCF entity is saved. The S-CSCF entity acquires the routing information of the user and the profile information of the user when the S-CSCF entity restarts; the S-CSCF entity notifies the service control platform to perform the operation according to the obtained profile information of the user. The user cancels the related business control process, and notifies the user to perform the logout process according to the obtained routing information.

The present invention will be further described in detail below with reference to the drawings and specific embodiments.

1 is a flow chart of an embodiment for implementing the present invention. Referring to Figure 1, in order to ensure the consistency of information between network nodes after the S-CSCF entity fails, the process of the present invention is:

Step 101: After the S-CSCF entity obtains the routing information of the user, the routing information of the user acquired by the S-CSCF entity is saved.

Here, the S-CSCF entity acquires the routing information of the user from the registration request sent by the user in the process of the user registering with the network side. For example, the S-CSCF entity is registered from the user. The routing information of the user is obtained in the information fields of the Request-URI header, the Route header, the Contact header, the From header, the To header, and the Via header in the request.

In this step, the process of saving the routing information of the user acquired by the S-CSCF entity may be: The S-CSCF entity saves the acquired routing information of the user in the non-volatile memory of the table itself. And, if the S-CSCF entity saves the acquired routing information of the user in its own non-volatile memory, the step may further include: the S-CSCF entity passes the HSS during the user registration process. The interaction process acquires the profile information of the user from the HSS, and saves the acquired profile information of the user in its own non-volatile memory.

In this step, the process of saving the routing information of the user acquired by the S-CSCF entity may be: the S-CSCF entity sends the obtained routing information of the user to the HSS, and the HSS saves the S-CSCF entity. Get the routing information of the user. The S-CSCF entity may send the routing information of the user to the HSS after the user obtains the routing information of the user in the process of registering the user with the network side, or may route the user after the user completes the registration to the network side. Information is sent to the HSS. The implementation process of the S-CSCF entity sending the routing information of the user to the HSS may be: adding an SAR to the existing server allocation request SAR sent by the S-CSCF entity to the HSS, for example, adding a cell to the Cx-Put message. Thus, in this step, the S-CSCF entity carries the routing information of the user in the added cell in the Cx-Put message and sends it to the HSS; or the S-CSCF entity carries the routing information of the user in a new definition. The Cx interface message is sent to the HSS.

Step 102: When the S-CSCF entity restarts after the fault occurs, the S-CSCF entity acquires the routing information of the user and the profile information of the user.

Here, if the routing information of the user is saved by the HSS in step 101, in this step, the S-CSCF entity obtains the routing information of the user and the profile information of the user from the HSS, and the specific process of the obtaining may be referred to As shown in Figure 2, the following steps are specifically included: Step 201: The S-CSCF entity sends its own identity and restart information to the HSS.

Here, the S-CSCF entity sends the self-identification and restart information to the HSS to notify the HSS that the S-CSCF entity has a restart event. The notification process may be: pre-allocation of the existing server to the HSS by the S-CSCF entity. In the SAR, for example, the Cx-Notify message is added with a cell, so in this step, the S-CSCF entity carries the identity and restart information on the added cell in the Cx-Notify message and sends it to the HSS; or, S- The CSCF entity carries its own identity and restart information in a newly defined Cx interface message and sends it to

HSS.

It should be noted that, in the present invention, the S-CSCF entity may store the address information of the HSS of the interactive information in the non-volatile memory of the S-CSCF entity itself when the information is exchanged with each HSS during the user registration process. In this way, in the sending process corresponding to the foregoing step 101 and the step 201, the S-CSCF entity performs the sending process according to the address information of the HSS saved in the non-volatile memory, that is, the routing information of the user, The self-identification and the restart information are sent to the corresponding HSS; or, the address information of all the HSSs is stored in the non-volatile memory of the S-CSCF entity in advance, so that in the sending process corresponding to the above step 101 and the step 201, S The CSCF entity performs the transmission process according to the address information of all HSSs stored in its own non-volatile memory, that is, the user's routing information, self-identification and restart information are sent to all HSSs. Here, the address information of the HSS is stored in the non-volatile memory of the S-CSCF entity, so that the S-CSCF entity can still obtain the address information of the HSS after the S-CSCF entity fails to restart, without being faulty. Restart and lose the address information of the HSS.

Step 202: The HSS that receives the S-CSCF entity identifier and the restart information determines whether there is information about the user including the S-CSCF entity identifier in the self. If yes, step 203 is performed. Otherwise, the HSS returns to the S-CSCF entity. Failed to respond, ending the current process.

Step 203: The HSS saves the routing information saved in itself and the description file of the user. The information is carried in the response message and sent to the S-CSCF entity.

So far, the process of obtaining the routing information of the user and the profile information of the user from the HSS by the S-CSCF entity is implemented.

In addition, if in step 101, the S-CSCF entity stores the user's routing information and the user's profile information in its own non-volatile memory, then in this step, the S-CSCF entity is from its own non- The user's routing information and the user's profile information are obtained in the volatile memory.

If in step 101, the S-CSCF entity only saves the user's routing information in its own non-volatile memory, and does not acquire and save the user's profile information, then in this step, the S-CSCF entity is Acquiring the routing information of the user from the non-volatile memory of the user, and the S-CSCF entity acquires the profile information of the user from the HSS, where the S-CSCF entity obtains the profile information of the user from the HSS. The process is the same as the process shown in Figure 2 above. In this case, the process of the corresponding step 203 is that the HSS only carries the profile information of the user saved in itself in the response message and sends it to the S-CSCF entity.

Step 103: The S-CSCF entity notifies the service control platform to perform a service control process related to the user logout according to the filtering rule in the obtained user profile information.

Here, in this step, the S-CSCF entity may further notify the AS associated with the user to cancel the connection established with the user according to the received routing information.

Step 104: The S-CSCF entity notifies the corresponding P-CSCF entity to perform the logout process according to the obtained routing information.

Step 105: The P-CSCF entity notifies the user to perform the logout process, and deletes the related registration information of the user saved in itself.

At this point, each network node in the network, including the user, the P-CSCF entity, and the service control platform, performs a logout process for the user, thereby ensuring each network node. The consistency of information.

After the above step 105, the P-CSCF entity may return a response message to the S-CSCF entity without waiting for the response message from the user. After receiving the response message, the S-CSCF entity returns a response message to the HSS, and the HSS updates the user in the response. Registration information.

In the present invention, the HSS that receives the S-CSCF entity identifier and the restart information determines the user information including the S-CSCF entity identifier in the user, and after the user information exists in the user information, the HSS may further The user's identity and logout reason are sent to the S-CSCF entity. For example, the HSS can send the user's identity and logout reason in the registration termination request (Cx-Deregister) message to the S-CSCF entity. Thus, in step 104, the S-CSCF entity further sends the logout reason to the P-CSCF entity, and in step 105, the P-CSCF entity further sends the logout reason to the user.

In the above step 104, when the S-CSCF entity notifies the P-CSCF entity to perform the deregistration process, the S-CSCF entity may further send an indication of whether to re-register to the P-CSCF entity, and in step 105, the P-CSCF entity notifies the user. When the logout process is performed, an indication of whether to re-register may be further sent to the user, so that the user may decide whether to re-initiate the registration process to the network side according to the received indication of whether to re-register.

It should be noted that step 103 and step 104 to step 105 are only two steps that are distinguished for convenience of description. In a specific service implementation, there is no fixed execution sequence between step 103 and step 104 to step 105.

In summary, referring to FIG. 3, when the method of performing service control by the S-CSCF entity and obtaining the routing information of the user from the non-volatile memory is adopted in the present invention, the implementation process of the present invention can be simply described as The process shown in Figure 3:

1. The S-CSCF entity decides to initiate the logout process according to the restart event, and invokes the corresponding service logic, for example, notifying the related application server to perform and cancel the related operations;

2. The S-CSCF entity sends a logout message Deregister to the P-CSCF entity; 3. The P-CSCF entity sends a logout notification UE Inform to the user UE, and notifies the UE if there is a reason for the logout;

4. The P-CSCF entity returns a logout response message OK 200 to the S-CSCF entity;

5. In the case that the UE can return a response message, the UE returns a logout response message OK 200 to the P-CSCF entity, but since the UE may not be able to reply to the OK 200 message in some cases, the P-CSCF entity may be in the logout notification timing. After the device expires, it returns to the response message OK 200 in step 4, and does not need to wait for the response message returned by the UE; therefore, step 4 and step 5 can be performed in parallel;

6. The S-CSCF entity sends an update message Cx-Put to the HSS to update the related registration information in the HSS;

7. The HSS confirms the update process and returns an update response message Cx-Put resp to the S-CSCF entity.

In summary, the above description is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalents, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A method for ensuring information consistency between network nodes, characterized in that the method comprises:

The method according to claim 1, wherein in step A, the serving call session control function entity acquires routing information of the user from a registration request sent by the user.

The method according to claim 1, wherein in step A, the step of saving the routing information of the user acquired by the serving call session control function entity comprises: the service call session control function entity acquiring the obtained The routing information of the user is sent to the home subscriber server, and the home subscriber server stores the routing information of the subscriber.

Bl, the monthly service call session control function entity sends its own identity and restart information to the home subscription user server;

B2. The home subscriber network server determines whether there is information about the user including the service call session control function entity identifier, and if yes, sends the saved user routing information and the user profile information to the service call session control. Functional entity.

The method according to claim 3, wherein in step A, the step of the serving call session control function entity transmitting the acquired routing information of the user to the home subscription subscriber server comprises: the service call The session control function entity sends the obtained routing information of the user to the home subscription user server during the user registration process or after the user registration is completed.

The method according to claim 3, wherein the method further comprises: adding a cell to the existing server allocation request message;

In step A, the step of the service call session control function entity transmitting the routing information of the user to the home subscription user server includes: adding, by the service call session control function entity, the routing information of the user in the server allocation request message The cell is sent to the home subscriber server.

The method according to claim 3, wherein in step A, the step of the serving call session control function entity transmitting the routing information of the user to the home subscriber network server comprises: the service call session control function The entity carries the user's routing information in a newly defined message and sends it to the home subscriber server.

The method according to claim 1, wherein in step A, the step of saving the routing information of the user acquired by the serving call session control function entity comprises: the serving call session control function entity The obtained user's routing information is saved in its own non-volatile memory;

The method according to claim 7, wherein the step A further comprises: the serving call session control function entity acquiring the profile information of the user from the home subscription user server during the user registration process, And the user's description of the obtained user The piece of information is stored in its own non-volatile memory;

In step B, the step of the service call session control function entity acquiring the profile information of the user includes: the service call session control function entity acquiring the profile information of the user from the non-volatile memory.

The method according to claim 7, wherein in step B, the step of the service call session control function entity acquiring the profile information of the user comprises: the service call session control function entity identifying itself and The restart information is sent to the home subscription server; the home subscription server determines whether there is information about the user including the service call session control function entity identifier, and if yes, sends the user profile information to the service call. Session control function entity.

The method according to claim 3 or 9, wherein the method further comprises: adding a cell to an existing server allocation notification message;

The step of the service call session control function entity transmitting the self-identification and restart information to the home subscription user server includes: the service call session control function entity carrying its own identifier and restart information in a message added by the server allocation notification message The element is sent to the home subscriber server.

The method according to claim 3 or 9, wherein the step of the serving call session control function entity transmitting its own identity and restart information to the home subscription subscriber server comprises: the service call session control function entity The identity and restart information of the identity is carried in a newly defined message and sent to the home subscriber server.

The method according to claim 3 or 9, wherein the method further comprises: the serving call session control function entity locating the interaction information when interacting with each home subscriber server during the user registration process The address information of the subscription user server is saved in the non-volatile memory of the service call session control function entity itself;

The service call session control function entity is based on the attribution stored in its own non-volatile memory. The address information of the subscriber server performs the step of transmitting.

The method according to claim 3 or 9, wherein the method further comprises: saving address information of all the home subscriber servers in the non-volatile memory of the serving call session control function entity;

The serving call session control function entity performs the step of transmitting based on address information of all home subscription subscriber servers stored in its own non-volatile memory.

The method according to claim 3 or 9, wherein the user information includes an identifier of the user;

The method according to claim 1, wherein in step C, the step of the service call session control function entity notifying the user to perform the logout comprises: the service call session control function entity according to the acquired routing information Notifying the corresponding proxy call session control function entity to perform a logout process; the proxy call session control function entity notifies the user to perform the logout process, and deletes the relevant registration information of the user saved in itself.

The method according to claim 1, wherein the step C further comprises: the service call session control function entity sending an indication of whether to re-register to the user, where the user receives the data according to the received The indication of whether to re-register to decide whether to re-initiate the registration process to the network side.

The method according to claim 1, wherein the step C further comprises: the serving call session control function entity notifying an application server related to the user to perform execution with the user according to the acquired routing information of the user Log out related processing.