WO2007140699A1

WO2007140699A1 - A method and apparatus for updating subscriber signed data

Info

Publication number: WO2007140699A1
Application number: PCT/CN2007/001564
Authority: WO
Inventors: Hui Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-06-06
Filing date: 2007-05-15
Publication date: 2007-12-13
Also published as: CN101047991A; CN100527876C

Abstract

A method and apparatus for updating subscriber signed data, for solving the problem that the existing typical flow couldn't be applied in the case of the specific data is changed. The method in the present invention includes the following step: when the network side updates the subscriber signed data, if the specific data therein is to be change, then performs corresponding process; and accomplishes the update of the subscriber signed data. The application of the present invention can make the network side adopt accurate process measure when the specific data in the subscriber signed data occurs change, so as to avoid the conflict between the change of specific data and the service providing.

Description

Method and device for updating user subscription data

The present invention relates to the field of communications, and in particular, to a method and apparatus for updating user subscription data. Background technique

SIP is a VoIP standard released by the Internet Engineering Task Force (IETF) in March 1999. SIP, as an important application of the Internet, adds telephone signaling and Quality of Service ("QoS") requirements, and has unique user addressing and positioning capabilities. Recently, the practical role of SIP has far exceeded the application of VoIP. SIP is a protocol for telephone signaling, used to initiate a session, can control the establishment and termination of multimedia sessions attended by multiple participants, and can dynamically adjust and modify session attributes, such as: session bandwidth requirements, transmission media type (voice, video) , data, etc.), media codec format, support for multicast and unicast, and more. Therefore, SIP facilitates the development of value-added services for multiple applications in conjunction with the Internet.

IMS is a subsystem superimposed by 3GPP on the packet network. It utilizes the control signaling channel of the packet domain and the bearer channel of the media transmission, and introduces the SIP protocol as a service control protocol to facilitate the use of SIP single, easy to expand, and media combination. The feature is to separate the service control from the bearer control to provide rich multimedia services. Referring to FIG. 1, the main functional entities in the IMS network include a call control entity CSCF that controls functions such as user registration and session control, an HSS that centrally manages user subscription data, and an AS that provides various service logic control functions.

The IMS network uses the registration process of the SIP protocol to implement user access to the IMS network. During the user registration process, the IMS network authenticates the user's private identity and establishes an access domain secure channel. After the user successfully registers, the relationship between the user's public identity and the current location of the user is established in the home domain S-CSCF, and the S-CSCF obtains the subscriber's subscription data from the HSS at the same time. The above registration process is shown in Figure 2 (more detailed process reference 3GPP TS24.229), including the following specific steps:

1. The UE initiates a registration request.

2. The P-CSCF saves the IPSec secure channel information and makes the home network address in the registration request. The DNS protocol is used to parse and obtain the address of the user's home network I-CSCF.

3-4. The I-CSCF queries the HSS for the user registration status, and then obtains the address of the S-CSCF assigned to the user according to the information returned by the HSS.

5. The I-CSCF sends a registration message to the S-CSCF.

6. The S-CSCF finds that it is the initial registration and obtains an authentication set from the HSS.

7. The HSS query obtains the authentication vector and returns it to the S-CSCF.

8. The S-CSCF selects an authentication vector and sends an authentication challenge (401 Challenge;) to the UE.

9. The I-CSCF returns the 401 message to the P-CSCF. '

10. The P-CSCF carries the security information according to the 401 message, and establishes a P-CSCF to the UE security channel. The message is then forwarded to the UE.

11. The UE authenticates the network according to the authentication vector of the 401 message, then calculates the authentication response, and re-initiates the registration process using the established secure channel.

12. The P-CSCF resolves the home network address in the registration request using the DNS protocol to obtain the address of the user's home network I-CSCF.

13-14 The I-CSCF queries the HSS for the user registration status and the S-CSCF information returned by the HSS.

15. The I-CSCF sends a registration message to the S-CSCF.

16-17. The S-CSCF checks the authentication response provided by the UE. If the match is successful, the authentication is successful, the registration information of the HSS is updated, and the subscription data of the user is downloaded.

18-20. The original way back to the registration success confirmation message.

21. The S-CSCF matches the registration message according to the initial filtering rule in the subscription data of the user. After the matching succeeds, the third-party registration is initiated to the corresponding AS.

22. The AS returns a registration success confirmation message.

In step 17 of the above process, the structure of the subscription data of the user downloaded by the S-CSCF using the UML model is shown in FIG. It can be seen that the subscription data of the user downloaded by the S-CSCF includes one or more service profiles. The service description includes information such as public identity, core network service authorization, initial filtering rule set, and shared initial filtering rule set. The initial filtering rule is the service parameters of a group of users. A business description can contain columns of multiple initial filtering rules Table.

An initial filter rule contains the following information:

- the application server (AS) address that was triggered;

- the priority of the initial filtering rules;

- trigger point;

- default processing;

- Optional service information.

The S-CSCF matches the priority of the initial filtering rule from high to low, and receives the request message from the Mw interface according to the trigger information in the trigger point. If the match is successful, the S-CSCF sends the relevant request through the ISC interface to the AS that matches the initial filter rule.

If the subscription data saved by the HSS changes, the HSS actively sends a subscription data update request to the registered S-CSCF, and after receiving the subscription data update request, the S-CSCF updates the locally saved subscription data. The process is shown in Figure 4.

According to the description of 3GPP TS 29.228, after the subscription data of the user changes, the HSS actively initiates a subscription data update request to the registered S-CSCF. If the S-CSCF is able to process the received subscription data, it returns a successful confirmation after updating the locally saved subscription data, otherwise it returns a failure.

The inventor believes that the process described in the standard cannot be combined with some scenarios in which the special bead data in the user subscription data changes, for example:

1. The user ID being used is blocked;

2. The user ID being used is changed;

3. Increase the user ID in the implicit registration set;

4. Reduce the user ID in the implicit registration set;

5. The AS corresponding to the new registration filter rule is not registered immediately, resulting in the new subscription not being applied immediately. Summary of the invention

Embodiments of the present invention provide a method and apparatus for updating user subscription data to support user signing A scenario in which special data in the data changes.

The method of the embodiment of the present invention includes the following steps: When the network side updates the user subscription data, it finds that the special data is about to change, and then performs corresponding processing; and completes the update of the user subscription data.

The service call session control function entity of the embodiment of the present invention includes: a release session module, a user re-authentication module, and a logout module, where the service call session control function entity S-CSCF further includes: a comparison module, configured to be used The updated data is compared with the original subscription data to determine whether the special data is about to change, and the release session module, the user re-authentication module, and the logout module are triggered accordingly.

The home subscriber network server of the embodiment of the present invention is configured to store the subscription data of the user. The home subscriber network (HSS) further includes: a comparison module, configured to compare the data to be updated with the original subscription data to determine whether the special data is A change is to be made; an adding module is configured to add a corresponding indication information to the issued update user subscription data request message when the comparison module finds that the special data is about to change.

The embodiment of the present invention does not update all the data immediately when receiving the subscription data of the user to be updated, as in the prior art, but is to be updated when the HSS or the S-CSCF receives the user subscription data to be updated. The data is compared to the original contract data to identify the particular data that will change. If the special data changes, after the relevant processing is completed, the updated user subscription data is provided to provide normal services for the user. DRAWINGS

Figure 1 is a schematic diagram of the architecture of an existing IMS system.

Figure 2 shows the flow chart of the registration using the SIP protocol.

FIG. 3 is a schematic structural diagram of user subscription data downloaded by an existing S-CSCF.

Figure 4 is a flow chart of the existing HSS notifying the S-CSCF to update the subscription data.

FIG. 5 is a flow chart of steps of a method according to an embodiment of the present invention.

FIG. 6 is a schematic structural diagram of an S-CSCF according to an embodiment of the present invention. Figure 流程图 is a flow chart showing the steps of applying the S-CSCF of the embodiment of the present invention.

FIG. 8 is a schematic structural diagram of an HSS according to an embodiment of the present invention.

9 is a flow chart showing the steps of applying the HSS of the embodiment of the present invention.

FIG. 10 is a signaling flowchart of Embodiment 1 of the present invention.

FIG. 11 is a signaling flowchart of Embodiment 2 of the present invention.

FIG. 12 is a signaling flowchart of Embodiment 3 of the present invention. detailed description ,

In order to prevent the processing of the special data from being changed when the special data in the user subscription data is changed, the embodiment of the present invention provides a method for updating the user subscription data, as shown in FIG. 5 . As shown, the following main steps are included:

51. The network side receives the subscription data to be updated.

52. The network side compares the subscription data to be updated with the original subscription data to determine whether the special bead data is about to change, and if yes, proceeds to step S3; otherwise, directly proceeds to step S4.

53. If the special data is about to change, it will be processed accordingly.

54. Complete the update of the user subscription data.

In the foregoing step S2, the subscription data to be updated is compared with the original subscription data to determine whether the special data is about to change, and may be completed by different network elements on the network side. Thus, embodiments of the present invention provide two processing strategies.

For the first processing strategy, an embodiment of the present invention provides an S-CSCF. As shown in FIG. 6, the method includes a release session module connected to the comparison module, a user re-authentication module, and a logout module.

The comparing module is configured to compare the data to be updated with the original subscription data to determine whether the special data is about to change, and trigger the release session module and/or the user re-authentication module, or correspondingly The release session module and the logout module are triggered.

The release session module is configured to release the current session of the related user identifier after receiving the trigger signal of the comparison module.

The user re-authentication module is configured to send a trigger signal to the user after receiving the trigger signal of the comparison module The side sends a re-authentication indication to enable the user to complete the re-authentication operation.

The logout module is configured to log out the registration information of the user after receiving the trigger signal of the comparison module.

Applying the foregoing S-CSCF, as shown in FIG. 7, the method in the embodiment of the present invention includes the following specific steps:

Al, HSS received the contract data and updated.

A2. The HSS initiates a subscription data update request to the registered S-CSCF, and sends the updated subscription data to the S-CSCF.

A3. After receiving the subscription data sent by the HSS, the S-CSCF checks whether the data is acceptable. If it is acceptable, go to step a4, otherwise, the update will fail.

A4. The S-CSCF compares the subscription data to be updated with the original subscription data, and completes the update of the user subscription data.

In this step, if the S-CSCF finds that the special data is going to change through the comparison operation, there are three cases:

Case 1: The S-CSCF finds that the changed special data is to delete the user ID registered by the user, and then process it by the following steps:

The S-CSCF checks if the user is conducting a session with the user identity, and if so, releases the session.

The S-CSCF rejects the calling side or called side request sent by the user identity.

The S-CSCF logs out the user.

Case 2: The S-CSCF finds that the changed special data indicates the user ID that the blocked user is using, or indicates that the user identifier that the user is using is changed. Then the following steps are taken: The S-CSCF checks whether the user is using the user identifier. Session, if yes, release the session.

The S-CSCF rejects the calling side or called side request sent by the blocked user identity. The S-CSCF rejects the calling side or called side request sent by the user identifier before the change before the user re-authentication succeeds. The S-CSCF uses the original subscription data to inform the user of the re-authentication.

After receiving the re-authentication request message sent by the user, the S-CSCF uses the subscription data processing request message to be updated, including carrying the implicit registration user identifier and the default user identifier in the new subscription data in the response message. User; update the status of the user ID; perform third-party registration based on the filtering rules in the new contract data. After the user is successfully registered, the caller side or called party request of the user ID after the change is started.

Case 3: The S-CSCF finds that the changed special data indicates that the user identifier in the implicit registration set is added, or the user identifier in the implicit registration set is reduced, or the AS that needs to be registered by the third party is added in the filtering rule, or the change is indicated. The priority of the third-party registered filtering rule is processed by the following steps:

The S-CSCF uses the original subscription data to inform the user of the re-authentication.

After receiving the re-authentication request message sent by the user, the S-CSCF uses the subscription data processing request message to be updated, including carrying the implicit registration user identifier and the default user identifier in the new subscription data in the response message. User; update the status of the user ID; perform third-party registration based on the filtering rules in the new contract data. After the user is successfully registered, the caller side or called party request of the modified user ID is processed.

If the S-CSCF does not find that the special data is going to change through the comparison operation, the user subscription data is updated according to the existing standard process.

For the second processing strategy, an embodiment of the present invention provides an HSS having a function of storing subscription data of a user. Referring to FIG. 8, the method further includes a comparison module and an adding module that are connected to each other.

The comparison module is configured to compare the data to be updated with the original subscription data to determine whether the special data among them is about to change.

The adding module is configured to add corresponding indication information in the sent update user subscription data request message when the comparison module finds that the special data is to be changed.

Applying the foregoing HSS, as shown in FIG. 9, the method in the embodiment of the present invention includes the following specific steps: bl, the HSS receives the subscription data.

B2, the HSS compares the subscription data to be updated with the original subscription data, and sends an update to the S-CSCF. A request message for user subscription data.

In this step, if the HSS finds that the special data is going to change through the comparison operation, there are three cases:

Case 1: The HSS finds that the changed special data indicates that the user identifier already registered by the user is deleted, and then sends a request message for updating the user subscription data to the S-CSCF, and adds a release session indication and a logout instruction to the message, so that S- The CSCF releases the current session of the user identity and instructs the user to log out.

Case 2: The HSS finds that the changed special data indicates the user ID that the blocked user is using, or indicates that the user identifier that the user is using is changed, and sends a request message for updating the user subscription data to the S-CSCF, and adds a release message to the message. The session indication and the re-authentication indication are such that the S-CSCF releases the current session of the user identity and instructs the user to re-authenticate.

Case 3: The special data indicated by the HSS changes indicates that the user identifier in the implicit registration set is added, indicating that the user identifier in the implicit registration set is reduced, indicating that the application server AS requiring third party registration is added in the filtering rule, or the change third party is indicated. The priority of the registered filtering rule is sent to the S-CSCF to update the user subscription data request message, and a re-authentication indication is added to the message, so that the S-CSCF instructs the user to perform re-authentication.

If the HSS does not find that the special data is to be changed by the comparison operation, the request message for updating the user subscription data is sent to the S-CSCF according to the existing standard procedure.

B3 > After receiving the subscription data sent by the HSS, the S-CSCF checks whether the data is acceptable. If yes, go to step b4, otherwise, the update will fail.

B4. The S-CSCF completes the update of the user subscription data according to the indication in the request message for updating the user subscription data.

Corresponding to case 1 in step b2, the S-CSCF performs the following steps:

The S-CSCF detects the release session indication.

The S-CSCF detects the logout indication. The S-CSCF rejects the calling side or called side request sent by the user identity.

The S-CSCF logs out the user.

Corresponding to case 2 in step b2, the S-CSCF performs the following steps:

The S-CSCF detects the release session indication.

The S-CSCF checks whether the corresponding user identity has an ongoing session, and if so, releases the session.

The S-CSCF rejects the calling side or called side request sent by the blocked user identity. The S-CSCF rejects the calling party or called party request sent by the user ID before the change before the user re-authentication succeeds.

The S-CSCF detects the re-authentication indication.

Corresponding to the third case in step b2, the S-CSCF processes the following steps:

The S-CSCF detects the re-authentication indication.

If the request message for updating the user subscription data received by the S-CSCF does not include the relevant indication, that is, the received request message for updating the user subscription data conforms to the existing standard, the user subscription data is updated according to the existing standard procedure. The following is specifically described by three examples.

Embodiment 1: The default user identifier in the user subscription data is blocked, and the subscription data is compared by the S-CSCF, and the update is completed. Referring to Figure 10, the following specific steps are included:

1. After the user subscription data is updated, the HSS initiates a request to update the user subscription data to the S-CSCF.

2. The S-CSCF receives the updated user subscription data, and after checking and saving the data, the response is answered.

3. The S-CSCF checks the user subscription data, finds that the original default user identifier of the user is blocked, then releases the ongoing session corresponding to the user identifier, and uses the original subscription data to notify the UE to re-authenticate.

4. The UE responds to the re-authentication notification message. '

5. The UE initiates a re-authentication request message.

6. The S-CSCF processes the user re-authentication request message using the new user subscription data, and carries the new user identity in the response message.

Embodiment 2: A third-party registration filtering rule is added to the user subscription data, and the subscription data is compared by the S-CSCF, and the update is completed. See Figure 11 for the following specific steps:

2. The S-CSCF receives the updated user subscription data, and after checking and saving the data, it responds to the HSS.

3. The S-CSCF checks the user subscription data, and finds that the third-party registration filtering rule is added to the user subscription data, and then uses the original subscription data to notify the UE to re-authenticate.

4. The UE responds to the re-authentication notification message.

5. The UE initiates a re-authentication request message.

7. The S-CSCF initiates a third party registration request using the new user subscription data. 8. The registered AS responds to the third party registration request message.

Embodiment 3: The default user identifier in the subscriber subscription data is changed, the HSS compares the subscription data, and the HSS sends a request message for updating the subscriber subscription data to the S-CSCF, and adds a relevant indication to the message to complete the update. Referring to Figure 12, the following specific steps are included:

1. After receiving the subscription data of the user to be updated, the HSS saves the subscription data, and checks the user subscription data, and finds that the original default user identifier of the user is changed. The HSS then sends a request message for updating the subscriber subscription data to the S-CSCF, and adds a release session indication and a re-authentication indication to the message. At the same time, update the user subscription data of the local end.

3. The S-CSCF detects that the request message includes a release session indication, and then releases the ongoing session corresponding to the user identifier; the S-CSCF detects that the request message includes a re-authentication indication, and then uses the original subscription data. The UE is notified to re-authenticate.

4. The UE responds to the re-authentication notification message.

5. The UE initiates a re-authentication request message.

In summary, the embodiment of the present invention does not update all the data immediately when receiving the subscription data of the user to be updated, as in the prior art, but receives the user subscription data to be updated in the HSS or the S-CSCF. When the data to be updated is compared with the original contract data, the special data to be changed is identified. If the special data changes, after the relevant processing is completed, the user is provided with normal services according to the updated user subscription data. In order to support the method of the present invention, the present invention also provides a Serving Call Session Control Function Entity S-CSCF, and a Home Signing Subscriber Server HSS. The implementation of the embodiment of the present invention can make the network side take correct processing decisions when the special data in the user subscription data changes, and avoid conflicts between special data changes and service provision.

Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from the invention. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

Rights request

A method for updating user subscription data, comprising: the following steps: when updating the user subscription data, the network side finds that the special data is to be changed, and then performs corresponding processing;

Complete the update of user subscription data.

The method according to claim 1, wherein the special data is to be changed at least: indicating that the user identifier that the user has registered is deleted, indicating the user identifier that the user is using, indicating that the user being used by the user is changed. The identifier indicates that the user identifier in the implicit registration set is added, indicating that the user identifier in the implicit registration set is reduced, indicating that the application server AS that needs to be registered by the third party is added in the filtering rule, or the priority of the filtering rule registered by the third party changes.

3. The method according to claim 2, wherein after the serving call session control function entity S-CSCF receives the request for updating the user subscription data sent by the home subscription subscriber server HSS, the S-CSCF will update the data to be updated. Compare with the original contract data to identify the special data that will change.

The method according to claim 3, wherein if the S-CSCF finds that the changed special data indicates that the user identifier already registered by the user is deleted, the current session of the user identifier is released, and the user is instructed to log off.

5. The method according to claim 3, wherein if the S-CSCF finds that the changed special data indicates that the user identifier is being used by the blocking user, or indicates that the user identifier being used by the user is changed, the user identifier is released. The current session, and the user is instructed to initiate re-authentication.

6. The method according to claim 3, wherein if the S-CSCF finds that the changed disparity data indicates increasing the user identifier in the implicit registration set, indicating that the user identifier in the implicit registration set is reduced, indicating the filtering rule Adding an application server AS that requires third-party registration, or indicating the priority of the filtering rule that changes the third-party registration, indicates that the user performs re-authentication.

7. The method according to claim 2, wherein, when the HSS updates the user subscription data, the data to be updated is compared with the original subscription data to identify the special data to be changed.

8. The method according to claim 7, wherein if the HSS finds that the changed special data indicates that the user identifier that the user has already registered is deleted, sending a request message for updating the user subscription data to the S-CSCF, and in the message A release session indication and a logout indication are added to cause the S-CSCF to release the current session of the user identity and to instruct the user to log out.

9. The method of claim 7, wherein the update user is sent to the S-CSCF if the HSS finds that the changed special data indicates the user identity being used by the blocked user, or indicates that the user identity being used by the user is changed. A request message for signing data, and adding a release session indication and a re-authentication indication to the message, so that the S-CSCF releases the current session of the user identity, and instructing the user to perform re-authentication.

The method according to claim 7, wherein if the HSS finds that the changed special data indicates that the user identifier in the implicit registration set is increased, indicating that the user identifier in the implicit registration set is reduced, indicating that the filtering rule is added The third-party registered application server AS, or the priority of the filtering rule indicating that the third-party registration is changed, sends a strange request message for updating the user subscription data to the S-CSCF, and adds a re-authentication indication to the message, so that S - The CSCF instructs the user to re-authenticate.

The method according to claim 5, 6, 9, or 10, wherein the S-CSCF indicates that the user performs re-authentication, including the following steps:

The S-CSCF notifies the user of the re-authentication right with the original contract data;

After receiving the re-authentication request message of the user, the S-CSCF completes the update of the user subscription data with the data to be updated.

A service call session control function entity, comprising: a release session module, a user re-authentication module, and a logout module, wherein the service call session control function entity S-CSCF further comprises:

The comparison module is configured to compare the data to be updated with the original subscription data to determine whether the special data is about to change, and trigger the release session module, the user re-authentication module, and the logout module.

13. A home subscription subscriber server, configured to store subscription data of a user, where The home subscriber network server HSS also includes:

a comparison module, configured to compare data to be updated with original contract data to determine whether special data is to be changed;

The adding module is configured to add corresponding indication information to the issued update user subscription data request message when the comparison module finds that the special data is to be changed.