WO2008019622A1

WO2008019622A1 - A method and application of acquiring the circuit switched domain information for the ip multimedia subsystem application and a method, apparatus and system for changing the circuit switched domain information

Info

Publication number: WO2008019622A1
Application number: PCT/CN2007/070448
Authority: WO
Inventors: Dongming Zhu; Xiaoyan He; Hengliang Zhang; Songhai Ye; Chunyan Ding
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-08-16
Filing date: 2007-08-10
Publication date: 2008-02-21

Abstract

A method and application of acquiring the circuit switched domain information for the IP multimedia subsystem application are provided, the home subscriber server HSS receives the inquiry order from the application server AS through the sh interface; the HSS returns the response message according to the inquiry order, and it carries the user circuit switched domain information requested by the AS in the response message. Or, the HSS receives the subscribing request transmitted by the AS through the sh interface; the HSS records the subscribing relationship, and transmits the notification message to the AS when the user circuit switched domain information changes, which carries the user circuit switched domain information subscribed by the AS. The AS applies the user circuit switched domain information to the IP multimedia subsystem domain based on the service logic. Further more, a method, system and apparatus for changing the circuit switched domain service information are also provided. In the case of the current user subscribes both of the IMS domain and the CS domain and after the IMS domain service information updates, it can set the user CS domain service information related to the user IMS domain service information in phase, ensure the consistent of the two domains service setting, and improve the service experience of the user.

Description

Method for acquiring circuit switched domain information and application thereof, and method, device and system for changing circuit switched domain information The application is filed on August 16, 2006, the Chinese Patent Office, the application number is 200610109398.8, the name of the invention For the 'ΊΡ multimedia subsystem application method and its application to obtain circuit domain information'; submitted to the Chinese Patent Office on January 25, 2007, application number 200710000396.X, the invention name is "IP multimedia subsystem application acquisition circuit domain information And its application"; and the Chinese Patent Application submitted to the China Patent Office on March 19, 2007, application number 200710086851.2, the invention titled "a method, system and device for changing the business information of circuit-switched domain" is preferred. The entire contents of which are incorporated herein by reference.

Technical field

Embodiments of the present invention relate to the field of network communication technologies, and specifically, to a method, an application, and a method, device, and system for acquiring circuit switched domain information for an IP multimedia subsystem application.

Background technique

IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) is a subsystem that supports IP multimedia services proposed by the Third Generation Partnership Projects. Its core feature is SIP (Session Initiation Protocol). The initial protocol) protocol implements the functions of establishing, maintaining, and managing IP multimedia services, allowing operators to deploy multimedia services quickly and efficiently, without relying on network access methods and types of terminal devices, supporting fixed networks and 802.11, 802.15, Any type of session on a wireless network such as 802.16, CDMA (Code Division Multiple Access) or GSM (Global System For Mobile Communication), allowing service providers to provide users with a range of voice and data fusion Multimedia business.

The system structure of IMS is shown in Figure 1:

The CSCF (Call Session Control Function) entity is used to control functions such as user registration and session control. The AS (Application Server) 110 is used to provide various service logic control functions. HSS (Home Subscriber Server) , home subscriber server) 120 is used to centrally manage user subscription information; MGCF (Media Gateway Control) Function, media gateway control function) 130 entity is used to implement interworking with the circuit switched network; UE (User Equipment) 140 accesses the IMS through a proxy node P-CSCF (Proxy CSCF, proxy call session control function) 150; The service trigger control and the service control interaction with the AS 110 are performed by the home domain service node S-CSCF (Serving CSCF, Serving Call Session Control Function) 160 of its place of registration.

The IMS service provision architecture is shown in Figure 2:

The HSS 210 is the most important database for each user, and stores all the information related to the subscription, which is used to support the processing of calls and sessions by various network entities, including: the user's identification, number, and addressing information; Security information; user's location information and user's description information. A home network may have one or more HSSs 210, depending on the number of mobile subscribers, the capacity of the network equipment, and the specific networking conditions. The HSS 210 provides a business hall interface for user data maintenance (adding, modifying, and deleting user subscription information, etc.), while the HSS 210 supports the Cx interface (the interface between the HSS and the I-CSCF/S-CSCF), and the Sh interface ( User data download for the interface between HSS and AS).

The AS 220 provides IP multimedia value-added services for IMS users, which can be located on the user's home network or by third parties, including SIP AS, OSA AS (Open Service Access AS, Open Service Access Application Server), and IM-SSF (IP Multimedia). Subsystem switching function) 230, in which the OSA AS interacts with the IMS network element through the OSA SCS (Service Capability Servers) 250 instead of directly interacting with the IMS network element, and the IM-SSF 230 provides the IMS SIP to the CS. CAMEL Application Part (CAP) 240 CS (Circuit Switched, Circuit Switched) Domain Intelligent Application Protocol Mapping and SSP (Service Switch Point) triggering capability enables IMS domain voice over IP (VoIP) service users to The CS domain intelligent service is seamlessly inherited; the AS obtains user service related data and user status information through the interface with the HSS, wherein the interface between the 81?8-8 and 088-8 and the HSS is the Dia interface based on the Diameter protocol, IM-SSF and The HSS is a Si interface based on the MAP (Mobile Application Part) protocol.

During the evolution of the network to the IMS, there will be a period of coexistence of the CS domain and the IMS domain. In this case, there will also be dual-subscribers with contracted relationships in both domains. At this time, the operator hopes that there is a control point in the network that can centrally control the services of the two domains to achieve the purpose of cross-domain service control to reduce operating costs. In the existing mechanism, this centralized control point is generally in IMS. Network, implemented by AS.

In the process of implementing the present invention, the inventors have found through research that: in the prior art, the AS can only obtain limited user dynamic information (location information and registration status) in the CS domain and a small amount of subscription information by querying. Fee information and mobile subscriber ISDN number MSISDN). Obtaining only this information will make it impossible to meet the business requirements in some business applications, and the query efficiency is low. At the same time, querying the CS domain information during the business operation process will increase the delay of the current service.

In addition, after the service information of the IMS domain changes, the CS domain service information cannot be updated, so that the CS domain service information cannot be updated through the IMS domain. In addition, when the IMS domain service information changes in the HSS, the user CS domain service information cannot be modified synchronously.

Summary of the invention

The embodiment of the invention provides a method for acquiring the circuit switched domain information of the IP multimedia subsystem application and the application thereof, so that the Sh interface can support the transmission of the CS domain information of the user, so that the AS can obtain the required user in the CS domain as needed. Information to meet the needs of different businesses.

The embodiment of the invention further provides a method for automatically synchronizing the service information of the IMS domain to the CS, so that the service information of the CS domain can be changed in the IMS domain.

In an embodiment of the present invention, a method for acquiring circuit switching domain information by an IP multimedia subsystem application may be provided, including:

The home subscription server HSS receives the query command sent by the application server AS through the Sh interface. The HSS returns a response message to the AS according to the query command, where the response message carries the user circuit CS domain subscription information requested by the AS.

In another embodiment of the present invention, a method for acquiring circuit switching domain information by an IP multimedia subsystem application may be provided, including:

The home subscription server HSS receives the subscription request sent by the application server AS through the Sh interface. The HSS records the subscription relationship, and issues a notification message to the AS when the user CS domain information changes. The notification message carries the user CS domain of the AS subscription. information.

In another embodiment of the present invention, a method for exchanging domain information by an IP multimedia subsystem application circuit may be provided, including:

The application server AS obtains user CS domain information from the home subscription server HSS through the Sh interface; the AS performs the obtained user CS domain information in the IP multimedia subsystem domain according to the service logic. Application.

In another embodiment of the present invention, a method of changing circuit switched domain information may be provided, including:

The home subscriber unit obtains the user circuit exchange CS domain service information that needs to be updated; the home subscriber unit uses the user CS domain service information that needs to be updated, and is modified.

CS domain business information.

In another embodiment of the present invention, a system for modifying circuit switched domain information may be provided, including: a home subscription subscriber unit, where the home subscription subscriber unit includes:

a first obtaining unit, configured to obtain user CS domain service information that needs to be updated;

The first update unit is configured to modify the CS domain service information by using the user CS domain service information that is obtained by the first acquiring unit and needs to be updated.

In another embodiment of the present invention, a home subscription subscriber unit may be provided, including: a first acquisition unit, configured to obtain user CS domain service information that needs to be updated;

In another embodiment of the present invention, an application server may be provided, including: a second obtaining unit, configured to obtain user CS domain service information that needs to be updated;

And a first sending unit, configured to send, by the second acquiring unit, user CS domain service information that needs to be updated.

In another embodiment of the present invention, an apparatus for modifying circuit switched domain information may be provided, including:

a receiving unit, configured to receive user IMS domain service information from the application server AS that needs to be updated;

a mapping unit, configured to obtain user CS domain service information that needs to be updated corresponding to the user IMS domain service information according to the correspondence between the user IMS domain service information and the user CS domain service information; and an update unit, configured to use the user that needs to be updated CS domain service information, modify CS domain service information.

It can be seen that the technical solution provided by the embodiment of the present invention extends the Sh interface between the AS and the HSS, so that the Sh interface supports the transmission of the user circuit switched domain information. In turn, the AS can obtain the required information of the user in the circuit switched domain as needed.

In the embodiment of the present invention, the home subscriber unit obtains the user circuit exchange CS domain service information that needs to be updated, and uses the user CS domain service information that needs to be updated to modify the CS domain service information. Therefore, when the user has the subscription information in both the IMS domain and the CS domain, after the IMS domain service information is updated, the user CS domain service information associated with the user IMS domain service information is synchronously set, and the two domains are guaranteed. The consistency of business settings improves the user's business experience.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description For some embodiments of the present invention, other drawings may be obtained from those skilled in the art without departing from the drawings.

1 is a schematic structural diagram of a system of a prior art IMS;

2 is a schematic diagram of a prior art IMS service provision architecture;

3 is a flowchart of an implementation of a first embodiment of a method for acquiring CS domain information by an IP multimedia subsystem application of the present invention;

4 is a flowchart of an implementation of a second embodiment of a method for acquiring CS domain information by an IP multimedia subsystem application of the present invention;

5 is a flowchart showing an implementation of a first embodiment of a method for applying CS domain information by an IP multimedia subsystem according to the present invention;

Figure 6 shows the HSS acquiring the user from the HLR when the HSS and the HLR are located in different physical entities.

Message interaction flowchart of an embodiment of CS domain information;

7 is a flowchart showing an implementation of a second embodiment of a method for applying CS domain information by an IP multimedia subsystem according to the present invention;

8 is a message interaction flowchart of a first embodiment of an AS acquiring a CS domain user state change notification by using a subscription notification method;

9 is a message interaction flowchart of a second embodiment of the present invention for obtaining a circuit switching domain user state change notification by a subscription notification method;

10 is a message interaction flowchart of an embodiment of an AS acquiring a user CS domain subscription data by using a query manner in the present invention; 11 is a flow chart of message interaction of an AS using a user CS domain information for domain selection in an embodiment of the present invention;

12 is a flowchart of querying, by the personal network management server, all basic service information subscribed by a user to an HSS according to an embodiment of the present invention;

13 is a schematic flow chart of an embodiment of a method of the present invention;

14 is a schematic flowchart of Embodiment 3 of the present invention;

15 is a schematic flowchart of Embodiment 4 of the present invention;

16 is a schematic flowchart of Embodiment 5 of the present invention;

17 is a schematic flowchart of Embodiment 6 of the present invention;

18 is a schematic flowchart of Embodiment 7 of the present invention;

19 is a schematic flowchart of Embodiment 8 of the present invention;

20 is a schematic flowchart of Embodiment 9 of the present invention;

21a-21h are schematic structural views of an embodiment of a system of the present invention.

detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

The embodiment of the present invention extends the Sh interface between the AS and the HSS to support the query or subscription and notification of the user CS domain subscription information, so that the AS can query or subscribe to the HSS through the Sh interface, thereby obtaining the user. CS domain information. When the AS requests the CS domain subscription information from the HSS through the Sh interface, the HSS provides the subscription information of the user CS domain according to the request of the AS. When the AS subscribes to the CS domain information of the user through the Sh interface, the HSS notifies the AS of the change event and the user CS domain information according to the subscription information of the AS.

The embodiments of the present invention are further described in detail below with reference to the accompanying drawings and embodiments.

It is known in the art that in the prior art, the data reference parameters of the CS domain queried through the Sh interface are very limited, including only location information, registration status, charging information, and MSISDN number, and the AS can only perform this part of data. The query does not allow subscription notifications for this data. In response to this situation, the present invention extends the Sh interface to support AS-to-HSS queries or subscription user CS domain information transfers.

Referring to FIG. 3, FIG. 3 is a flowchart of an implementation of a first embodiment of a method for acquiring CS domain information by an IP multimedia subsystem application according to the present invention, including the following steps:

Step 301: The Sh interface is extended to support the query of the user CS domain subscription information.

The AS can use the existing Sh-Pull command to query the supplementary service information of the CS domain, and include the MSISDN number of the user to be queried in the command. In addition, the AS needs to add a new value to the data reference parameter in the existing Sh-Pull command. Each new value corresponds to a type of user CS domain supplementary service information that the AS needs to query. In this way, when the data reference parameter in the Sh-Pull command sent by the AS is the value added, it indicates that the AS requests to query the CS domain supplementary service information of the user. In addition, the Sh-Pull command can be further extended by adding the following parameters to the existing Sh-Pull command:

(1) A parameter for identifying the supplementary service information of a certain type of basic service requested by the AS, which is used to carry the basic service group code;

(2) Identify the parameters of the supplementary service requested by the AS for this query operation, and this parameter is used to carry the supplementary service code.

Step 302: The AS sends a Sh-Pull command to the HSS through the Sh interface to query the CS domain subscription information of the user.

In the request, the above two new parameters can appear at the same time, or only one of them appears, or does not appear. That is to say, the AS can send a Sh-Pull request to the HSS through the Sh interface, which can be as follows:

(1) The AS sends a Sh-Pull request containing only the MSISDN number and the data reference parameter to the HSS to query all basic services and supplementary service information.

(2) The AS sends a Sh-Pull request including the MSISDN number, the data reference parameter, and the basic service group code parameter to the HSS, and queries all supplementary service information hanged by the specific basic service group.

(3) The AS sends a Sh-Pull request including the MSISDN number, the data reference parameter, and the supplementary service code parameter to the HSS, and queries the specific supplementary service information that is connected to all the basic service groups.

(4) The AS sends a Sh-Pull request including the MSISDN number, the data reference parameter, the basic service group code parameter, and the supplementary service code parameter to the HSS, and queries the specific basic service group. The specific supplementary business information that is hanged.

Step 303: After receiving the query command, the HSS returns a response message, and carries the user CS domain subscription information requested by the AS in the response message.

After receiving the extended query command, the HSS first obtains the user CS domain subscription information from the HLR (Home Location Register) or the internal HLR subset, and then returns the obtained user CS domain subscription information to the AS. In this process, if the format of the user CS domain subscription information that can be identified by the AS and the HLR is different, the acquired user CS domain subscription information needs to be converted into the Diameter format before the HSS obtains the user CS domain subscription information. Or XML format.

The process by which the HSS obtains user CS domain subscription information from the HLR will be described in detail later.

The user CS domain subscription information that the HSS can obtain from the HLR includes supplementary service information, and specifically includes: a service code of the supplementary service, status information of the supplementary service, and corresponding basic service group code information.

Referring to FIG. 4, FIG. 4 is a flowchart of an implementation of a second embodiment of a method for acquiring CS domain information by an IP multimedia subsystem application according to the present invention, including the following steps:

Step 401: Extend the Sh interface between the AS and the HSS to support the subscription and notification of the user CS domain subscription information.

Specifically, in the present invention, the Sh interface is extended to support the user state change notification subscription and notification release of the user CS domain; in addition, the Sh interface can be extended to support the supplementary service information change notification of the user CS domain. Subscriptions and notifications are posted. This will be described in detail below.

Those skilled in the art know that in the prior art, the Sh interface does not support the function of CS domain information subscription notification. In the present invention, the Sh interface can be extended, and the existing Sh-Subs-Notif command is used as a user status change notification message of the subscriber CS domain, so that it supports the function of the user status change subscription notification of the CS domain; Add a new value to the data reference parameter in the existing Sh-Subs-Notif command. Each new value corresponds to a CS domain supplementary service information type that the AS needs to subscribe to, so that it supports the CS domain supplementary service information. The subscription notification function; the Sh-Subs-Notif command can be further extended, and a new class of parameters can be added in addition to the new value of the data reference parameter, and such new parameters are used to further identify the data requested by the AS. , can contain two specific parameters at the same time:

(1) Identify the supplementary service information of a certain basic service requested by the AS for this subscription operation. Parameter, which is used to carry the basic service group code.

(2) Identify the parameters of the supplementary service requested by the AS for this subscription operation, and the parameter is used to carry the supplementary service code.

These two parameters can appear at the same time in the Sh-Subs-Notif command, or they can only appear in any one of them, or not at the same time.

Step 402: The AS sends a Sh-Subs-Notif request to the HSS through the Sh interface, and subscribes to the CS domain information of the user.

The Sh-Subs-Notif request sent by the AS to the HSS can be as follows:

(1) The AS sends a Sh-Subs-Notif request containing only the MSISDN number and the data reference parameter to the HSS, and subscribes to all the basic services and the supplementary service information attached thereto.

(2) The AS sends a Sh-Subs-Notif request including the MSISDN number, the data reference parameter, and the basic service group code parameter to the HSS, and subscribes to all supplementary service information hanged by the specific basic service group.

(3) The AS sends a Sh-Subs-Notif request including the MSISDN number, the data reference parameter, and the supplementary service code parameter to the HSS, and subscribes to the specific supplementary service information advertised by all the basic service groups.

(4) The AS sends a Sh-Subs-Notif request including the MSISDN number, the data reference parameter, the basic service group code parameter, and the supplementary service code parameter to the HSS, and queries the hanging of the specific basic service group. This particular supplementary business information.

Step 403: After receiving the Sh-Subs-Notif request, the HSS records the subscription relationship.

Step 404: The HSS sends a notification message to the AS when the CS domain information of the user changes, where the CS domain information of the user subscribed by the AS is carried.

After the HLR senses that the user has the first attach operation after roaming or the VLR (Visitor Location Register) clears a user data event, the HLR sends a message to the HSS that the user status changes. After receiving the message that the user status sent by the HLR changes, the HSS sends the user status change event and the changed status to the AS according to the subscription relationship.

The HLR senses that the VLR sends the message synchronously updated data to the HLR or the administrator changes the user supplementary service data through the HLR interface, and then sends a message to the HSS that the user supplementary service changes. After receiving the message that the user supplementary service sent by the HLR changes, the HSS according to the subscription The status information and the basic service group of the changed supplementary service are sent to the AS.

The invention expands the Sh interface to support the query or subscription and notification of the user CS domain subscription information, so that the AS can query or subscribe to the HSS through the Sh interface, thereby obtaining the user CS domain information.

Referring to FIG. 5, FIG. 5 shows an implementation flow of a first embodiment of a method for applying CS domain information by an IP multimedia subsystem according to the present invention, including the following steps:

Step 501: The AS requests the user CS domain subscription information from the HSS through the Sh interface.

The AS can query the HSS for the user CS domain subscription information through the Sh interface, and can also subscribe the user CS domain subscription information to the HSS through the Sh interface. Which method is used can be determined according to actual needs.

Step 502: The HSS acquires the user CS domain subscription information from the HLR according to the request of the AS.

Because the information format supported by the AS and the HLR is different, the HSS needs to convert the obtained user CS domain subscription information into a Diameter format or an XML format that the AS can recognize.

Step 503: The HSS sends the obtained user CS domain subscription information to the AS.

If the HSS receives the AS query request, it returns the requested user CS domain subscription information to the AS after receiving the request.

If the AS has subscribed to the CS domain subscription information of the user through the Sh interface, the HSS sends a message to notify the AS of the change event and the changed user CS domain subscription information when the data related to the AS subscription changes.

Step 504: The AS applies the acquired user CS domain information in the IP multimedia subsystem domain according to the service logic.

After the AS obtains the CS domain subscription data information, the applicable applications include, but are not limited to: performing cross-domain service control, CS domain subscription information, and IMS domain subscription information in the IMS domain according to the subscription data of the CS domain. Synchronization settings, based on the acquired CS domain and IMS domain status information, subscription information, etc. for domain selection.

Since in the future network evolution, HSS and HLR may be located in the same physical entity (HSS embedded HLR subset), it may also be separated, that is, separate functional entities. For both cases, the present invention provides a detailed process for the HSS to obtain user CS domain subscription information from the HLR.

When the HSS embeds a subset of HLRs, the HSS obtains the user's various CSs from the HLR through the internal interface. Domain signing information. First, the HSS sends a request message for querying the CS domain information of the user to the HLR, where the message includes the MSISDN number of the user, the information indication to be queried, and the like; after receiving the request message, the HLR determines that the MSISDN number exists and returns the user CS to the HSS according to the request. Domain data information.

When the HSS and the HLR are located in different physical entities, the HSS obtains various CS domain subscription information of the user from the HLR through the external interface. In the specific implementation, you can use the following methods:

(1) The HSS intercepts the request sent to the HLR and the response message sent by all the HLRs by using the signaling interception manner, and obtains the CS domain subscription information of the user in the HLR according to the relationship between the request and the response;

(2) The HSS is used as the service control point. The SCP obtains the user CS domain subscription information from the HLR through the query mode.

(3) The HSS obtains the user CS domain subscription information from the HLR through the subscription notification method. 6 is a message interaction process of an embodiment in which an HSS acquires user CS domain information from an HLR when the HSS and the HLR are located in different physical entities, and includes the following steps:

61. The HSS sends an ATSI command (for WCDMA network) or a Service Request message (for CDMA network) to the HLR as required, requesting to query the user's CS domain data; 62. After receiving the request to determine the MSISDN number, the HLR determines the request. Whether the data is valid;

63. If the data requested in 62 is valid, the HLR returns the user CS domain data information, otherwise, the error port is returned.

Referring to FIG. 7, FIG. 7 shows an implementation flow of a second embodiment of a method for applying CS domain information by an IP multimedia subsystem according to the present invention, including the following steps:

Step 701: The AS subscribes to the user CS domain information to the HSS through the Sh interface.

Step 702: The HSS senses that the user CS domain information changes.

The user CS domain information includes: user CS domain subscription data, and/or user registration status, location information, and the like. The HSS can detect that the user CS domain information changes in the following manner: When the HSS embeds the HLR subset, the HLR discovers that the user CS domain information changes and unconditionally notifies the HSS through the internal interface;

When the HSS and the HLR are located in different physical entities, the HSS changes the user CS domain information from the HLR through the external interface. Specifically, the HSS may intercept the request sent to the HLR and the response message sent by all the HLRs by using the signaling interception manner, and obtain the user CS domain information that changes within the HLR according to the relationship between the request and the response; or the HSS serves as a service control point. SCP through order The notification mode changes from the HLR to the user CS domain information, and acquires the changed user CS domain information. The interface between the SCP and the HLR can be extended, so that the HSS/SCP can subscribe to the HLR, including but not limited to CSI (Camel Subscription Information), CB (Call Barring), CF (Call Forwarding) Forward) and other data.

Step 703: The HSS notifies the AS of the change event and the changed user according to the AS subscription information.

CS domain information.

Step 704: The AS applies the acquired user CS domain information in the IP multimedia subsystem domain according to the service logic.

FIG. 8 is a message interaction process of the first embodiment of the present invention for obtaining a CS domain user state change notification by using a subscription notification method, including the following steps:

81. The AS sends a Sh-Subs-Notif request to the HSS to subscribe to the user status change notification in the CS domain. The parameters in the request include: MSISDN, DataReference (User State User State). Requested-Domain (Value CS Domain CS) Domain );

82. The HSS returns a subscription success response to the AS Sh-Subs-Notif-Rsp;

83. Since the terminal does not contact the network for a long time or for other reasons, the VLR deletes the user data and sends a message to notify the HLR. The figure indicates the message name MAP_Purge_MS in the WCDMA network. In the CDMA network, the message name of the same function is MS Inactive;

84. The HLR sets this user's MNRF (Mobile Station Not Reachable Flag) to true and notifies the HSS of this event;

85. The HLR returns the Purge response message MAP— Purge—MS-Rsp to the VLR. In the CDMA network, the message name with the same function is MS Inactive Rsp;

86. The HSS sends a notification message to the AS, and informs the user that the CS domain status changes. The message includes the user MSISDN number, the changed status, and the status value NetworkDeterminedNotReachable;

87. The AS returns a notification response message Sh-Notif-Rsp. In this embodiment, the VLR causes the user state to change by clearing the user. The process of notifying the AS in the HLR caused by the first attachment or the like after the location update is performed is similar to the above, and is not described here.

FIG. 9 is a message interaction process of the second embodiment of the present invention for obtaining a CS domain user state change notification by using a subscription notification method, including the following steps:

In this embodiment, the AS queries the user CS domain to supplement the service status and subscribes to the information. The user modifies the supplementary service information through the terminal, and the HSS notifies the AS of the supplementary supplementary service status information.

91. The AS sends a Sh-Pull request to the HSS to query the supplementary service information of the user in the CS domain. The parameters in the request include: MSISDN, DataReference (indicating supplementary service information when adding value), ServiceCode (new parameter, The value is the supplementary service code of the query);

92. The HSS forwards the message to the internal HLR, and the HLR checks whether the MSISDN exists. If yes, the HLR organization needs to return the data and forward it to the HSS;

The HSS returns the query response message Sh-Pull-Rsp to the AS, which includes the supplementary service code, the four status values of the supplementary service, and the basic service group corresponding to the supplementary service (Basic Service Group);

The AS sends a Sh-Subs-Notif message to the HSS to subscribe to the user's supplementary service information change notification in the CS domain. The parameters in the request include: MSISDN, DataReference (the value is the added value indicating supplementary service information), ServiceCode (Add a parameter, the value is the supplementary service code of the query);

95. HSS returns a successful subscription response Sh-Subs-Notif-Rsp;

96. The user activates the supplementary service through the terminal operation. The figure shows the message Activate_S S in the WCDMA network, and the message of the same function in the CDMA network is named Feature Request;

97. The VLR modifies the local supplementary service information and sends a message to the HLR to request the synchronous data update operation. The figure shows the message MAP_Activation-SS in the WCDMA network, and the message with the same function in the CDMA network is named Feature Request;

98 - 99. The HLR updates the data and returns a response to the VLR. Step 99 shows the message MAP_Activate-SS-Rsp in the WCDMA network. The message with the same function in the CDMA network is named featreq;

910. The HLR notifies the HSS of the supplementary service information through the internal interface, and the HSS sends a notification to the AS through the Sh interface, where the message includes the MSISDN, the supplementary service code, the changed supplementary service status information, and the basic service group (Basic Service Group); 911. The AS returns a notification response Sh-Notif-Rsp to the HSS.

Other similar administrators change the user CS domain data in the MSC/VLR (Mobile Service Switching Center/Visit Location Register), HLR operation interface, or the user's CS domain data changes in the HLR through the terminal operation, and the AS subscription acquires the data notification implementation. The process is similar to the above, and is no longer here - enumerated.

FIG. 10 is a message interaction process of an embodiment of an AS acquiring information about a user's CS domain by means of a query, including the following steps:

In this embodiment, the AS queries the user CS domain to supplement the service information, and the administrator modifies the supplementary service information through the HLR business hall, and the AS queries the latest data again.

The AS sends a Sh-Pull request to the HSS to query the supplementary service information of the user in the CS domain. The parameters in the request include: MSISDN, DataReference (indicating that the added value indicates supplementary service information), no supplementary service code, indicating that Querying all supplementary business information of the user;

102. The HSS forwards the message to the internal HLR, and the HLR checks whether the MSISDN exists. If yes, the HLR organization needs to return the data and forward it to the HSS;

The HSS returns the query response message Sh-Pull-Rsp to the AS, which includes each supplementary service code subscribed by the user, four state values of each supplementary service, and a basic service group corresponding to each supplementary service (Basic)

Service Grou );

104. The administrator changes one or more supplementary business information of the user through the business hall operation provided by the HLR;

105-106. The HLR sends a message to the VLR for data synchronization operation, and the VLR returns a successful response. The figure shows the message MAP in the WCDMA network - Insert - Subscriber - Data and MAP - Insert - Subscriber - Data - Rsp in CDMA Messages of the same function in the network are named QUALDIR and qualdir;

107. The AS sends a Sh-Pull request to the HSS again to query the supplementary service information of the user in the CS domain. The parameters in the request include: MSISDN, DataReference (indicating the added service information for the new value), there is no supplementary service code, indicating To query all the supplementary business information of the user;

108. The HSS forwards the message to the internal HLR, and the HLR checks whether the MSISDN exists. If yes, the HLR organization needs to return the data and forward it to the HSS;

The HSS returns the query response message Sh-Pull-Rsp to the AS, which includes the latest data after modification, the supplementary service codes signed by the user, and the values of the four states of the supplementary services. Basic Service Group.

Other similar administrators change the user CS domain data on the MSC/VLR, or the user operates through the terminal, causing the user CS domain data in the HLR to change. The implementation process of the AS query to obtain data is similar to the above, and is not enumerated here.

As mentioned above, after the AS obtains the CS domain subscription data information, the application can be applied to: the corresponding cross-domain service control in the IMS domain according to the subscription data of the CS domain, and the CS domain subscription information and the IMS domain subscription Synchronization of information, based on the acquired CS domain and IMS domain status information, subscription information, etc. for domain selection. The following examples illustrate this.

Referring to FIG. 11, FIG. 11 shows a message interaction process in which the AS uses the user CS domain information for domain selection in the present invention, including the following steps:

111. The AS sends a Sh-Subs-Notif message to the HSS to subscribe to the registration status and service subscription information of the user in the CS domain and the IMS domain.

112. The HSS responds to the AS with a subscription response message Sh-Subs-Notif-Rsp;

113. The administrator sets up the CS domain forwarding service for the user through the business hall;

114-115. The HSS senses that the user CS domain service subscription changes, and notifies the AS of the event and the latest data;

116. The dual-signed user receives a new session request INVITE in his home IMS domain;

117. The S-CSCF triggers the application server AS by detecting the IFC (Initial Filter Criteria) of the user;

The AS performs domain selection according to the locally saved user information and service logic: The AS judges that the user is not registered in the IMS domain and the CS domain according to the locally saved user data, but only signs the forwarding service in the CS domain. Then, the AS performs domain selection, and decides to connect the call to the CS domain for processing, so that the user can still receive the incoming call in the CS domain, thereby improving the user experience;

119. The AS returns the redirected CS domain forwarding number CFN to the S-CSCF;

1110. The S-CSCF forwards the session request to a finally selected MGCF (Media Gateway Control Function);

1111. The MGCF sends an incoming request according to the number analysis of the gateway office GMSC (Gateway Mobile Switching Center) where the forwarder is located;

1112. The GMSC forwards the HLR requesting to obtain the user's routing information, as shown in the figure. For the WCDMA network, the message SRI (Send Routing Info), the same function of the message in the CDMA network is named locreq (location request);

1113-1114. The end office VMSC (visiting the mobile services switching center) where the HLR forwards the user is requested to obtain the roaming number information, where the picture shows the message PRN (Provide Roaming Number) in the WCDMA network. Messages of the same function in a CDMA network are named ROUTREQ and routreq (routing request);

1115-1116. The GMSC routes the obtained roaming number route to the end office where the forwarding party is currently roaming, initiates an incoming request, and completes the CS domain call setup part, where step 1115 in the figure shows the message SRI in the WCDMA network. The message of the same function in the CDMA network is named locreq. Step 1116 shows the message IAM (Initial Address Message) in the WCDMA network. The messages of the same function in the CDMA network have the same name.

This example only illustrates the application of the domain selection after the AS obtains the CS domain information. The application that can be performed after the AS obtains the information includes the synchronization setting of the CS domain subscription information and the IMS domain subscription information, and the CS domain. The contract information is used for corresponding cross-domain business control, etc., and the detailed process is no longer described here.

Referring to FIG. 12, FIG. 12 is a flowchart of querying the HSS for all basic service information subscribed by the user to the HSS according to the embodiment of the present invention.

In this embodiment, the process of initiating active activation by the user equipment (PNM UE) that has subscribed to the personal network service mainly includes the following steps:

1201. CS domain The PNM UE routes the VMSC/VLR (visiting the mobile services switching center/visiting location register) to send a request to the HSS to query the activation configuration information in the current personal network. The request carries the MSISDN to be queried.

1202. The HSS routes the registration request to the corresponding PNM server according to the saved USSD (Unstructured Supplementary Services Data) Camel subscription information U-CSI (USSD Service Smart Subscriber Information).

1203-1204. The PNM server returns the query result based on the locally saved activation configuration information.

The above steps 1201 to 1204 are optional, and the user is allowed but not forced to query the current configuration.

1205-1206. The CS domain user equipment UE sends an activation request to the HSS through the VMSC/VLR route. The request includes: IMSI, MSISDN, activation type, priority parameter, and so on. The HSS forwards the request to the PNM server based on the saved U-CSI information, where the activation type is global activation.

1207. The PNM server checks if the UE has been registered in the personal network by looking up whether there is an IMSI-MSISDN record locally.

1208-1209. Since the PNM server in the PNM service is both the AS of the IMS domain and the gsmSCF of the CS domain, the PNM server can use the Sh-Pull message of the Sh interface to send a request to the HSS to query the basic service information subscribed by the user, where Sh- The pull message includes the parameter MSISDN and the data reference parameter, and the value of the data reference parameter is a new value indicating the basic service information of the CS domain.

After receiving the Sh-Pull message, the HSS returns the service code of all basic services subscribed to by the MSISDN. If the MSISDN does not sign any basic service, it returns error or null data.

1210-1211. The PNM server acquires the capability information of the activated UE from the entity that stores the UE capability information.

1212. The PNM server compares the capability information and the subscription information of the activated UE with the required capability of the redirected service. If the service requirement is met, the UE is considered to be successful for the service.

1213. The PNM server subscribes to the CSS for the CS domain information change notification of the MSISDN. When the CS domain information of the MSISDN changes, the HSS needs to notify the PNM server, and the PNM server compares whether to change the activation setting.

The PNM server in the PNM service is both the AS of the IMS domain and the gsmSCF of the CS domain. Therefore, the PNM server can use the Sh-Subs-Notif message of the Sh interface to send basic service information to the HSS to subscribe to the subscriber subscription, where Sh- The Subs-Notif message includes the parameter MSISDN and the data reference parameter, and the value of the data reference parameter is a newly added value indicating the basic service information of the CS domain.

After receiving the Sh-Subs-Notif message, the HSS saves the subscription relationship if the PNM server is allowed to subscribe to the information, and then sends a message to notify the PNM server when the basic service subscribed by the user changes.

1214-1215. The HSS returns an activation response to the UE, indicating whether the activation operation is successful, and the partial activation of the global activation is successful. Therefore, the success activation response message needs to carry the successfully activated service code and MSISDN.

If the S-Pull request sent by the PNM server in the above step 1208 includes a specific basic service code in addition to the MSISDN number and the data reference parameter, it indicates that the PNM server queries the If the user subscribes to the basic service after receiving the query request, the HSS returns the basic service code in step 1209, and returns no error or null data if there is no subscription.

As shown in FIG. 13, the specific process of updating the CS domain service information in the embodiment of the present invention is as follows: Step 1301: The home subscription subscriber unit obtains the user CS domain service information that needs to be updated; where the home subscription subscriber unit obtains the user CS that needs to be updated. There are many ways to process domain information. The home subscription subscriber unit may obtain the user CS domain service information from the application server, for example, the application server obtains the user CS domain service information that needs to be updated, and sends the user CS domain service information that needs to be updated to the home subscription user. unit. Of course, when the application server determines that the IMS domain service information needs to be updated, the user IMS domain service information that needs to be updated may also be sent to the home subscription subscriber unit, where the home subscription subscriber unit utilizes the user IMS domain service that needs to be updated. The information updates the user IMS domain service information, and uses the correspondence between the user IMS domain service information and the user CS domain service information to obtain the CS domain service information of the user that needs to be updated corresponding to the user IMS domain service information. Here, the application server may send the user IMS domain service information that needs to be updated through the Sh interface.

The home subscriber unit may include the user CS domain service information from the application server in the following manners:

The first type: when the application server determines that the user IP multimedia domain service information changes, and needs to update the service information of the user CS domain, the application server obtains the updated service information of the user IMS domain, and according to the user IMS domain service. Corresponding relationship between the information and the CS domain service information of the user, the user CS domain service information that needs to be updated corresponding to the user IMS domain service information is obtained, and then the obtained user CS domain service information is sent to the home subscription subscriber unit.

There are many cases in which the application server can determine whether it is necessary to update the circuit switched domain service information. For example, a dual-mode user who can access both the IMS and the CS can maintain the consistency of the service settings of the two domains in order to provide a consistent service experience for the user. For example: When the user changes the forwarding number of the CFU (Call Forwarding Uncondition) service in the IMS domain, it also needs to update the forwarding number in the CS domain. At this time, the application server may need to update the user synchronously. Business information of the CS domain.

In addition, some service information such as: Active status of the CFU service. If the user sets the CFU service to the Deactive state in the IMS domain, the user may need to be in the active state. The CFU service of the CS domain is also set to the Deactive state. For example, if a user newly signs a new service in the IMS domain, then it may be necessary to synchronize the contract in the CS domain.

It should be noted that, in the correspondence between the user IMS domain service information and the user CS domain service information, the user IMS domain service information and the user CS domain service information may be the same information, or may not be the same information, but The IMS domain is related to the service in the CS domain. Therefore, there is a corresponding relationship between the two. For example, after a certain service change in the IMS domain, some services of the CS domain need to be implemented, such as VCC of the IMS domain. Call Continuity, Voice Call Continuity) After changing, you need to modify the mobile network Enhanced Logic Customization Application (CAMEL) subscription information in the CS domain.

Of course, in the first mode, the application server obtains the updated user IMS domain service information, which can be implemented as follows:

The user terminal updates the user IMS domain service information in the application server by using the Ut interface. The application server obtains the updated user IMS domain service information from the updated service information.

The user modifies the service data by applying, and after the home subscriber unit determines that the user IMS domain service information is modified, the home subscriber unit sends the modified user IMS domain service information to the application server.

In the first mode, the user CS domain service information may be sent to the home subscriber unit by using a request to update the user CS domain service information.

Here, the request for updating the user CS domain may be an extended Sh interface message, and the extended Sh interface message includes: a CS domain user identifier, a service data reference parameter to be updated, and a service data content to be updated.

The request for updating the user CS domain may be a MAP message that includes a validity verification identifier and a user CS domain service information that needs to be updated. Therefore, after receiving the MAP message, the home subscription subscriber unit needs to determine whether the MAP message contains legality. The authentication identifier, if included, can obtain the user CS domain service information that needs to be updated from the MAP message. The legality verification identifier includes a VLR number, or an AS number, or a preset identifier. Here, the MAP message includes a VLR number, and the VLR initiates an update command of the CS domain service information, so that the home subscriber unit can verify the validity of the message. The home subscription subscriber unit may also be configured to enable the home subscription subscriber unit to identify the AS number or a preset special identifier. When the MAP message contains the AS number or is in advance When the special identifier is set, the legality check processing is not performed, and it is directly considered that the legality verification identifier is included, that is, the verification is passed, and the CS domain service information of the user that needs to be updated is directly obtained from the message, and the CS domain routing update processing is performed. .

The second type: the user terminal sends a request for updating the CS domain service information to the application server, and after receiving the request, the application server directly obtains the CS domain service information that needs to be updated from the request.

The user terminal may send a request for updating the CS domain service information through the UT interface, or may send a request through other messages, for example, an Unstructured Supplementary Service Data (USSD) message.

Step 1302: The home subscription subscriber unit modifies the CS domain service information by using the user CS domain service information that needs to be updated.

The home subscription subscriber unit may include an HLR, and does not include an HSS, and may also include an HSS and an HLR. When the home subscription subscriber unit includes an HSS and an HLR, the HSS and the HLR may be an independent combination of the two. The physical entity can also be a separate two separate physical entities.

If the HLR and HSS are combined, the HSS changes the information of the user CS domain through internal messages between them. If the HLR and HSS are separated, the HSS changes the user's CS domain information through messages between them. In addition, if the HLR is a DRS disaster tolerant database, the HSS will also organize the data into HLR-recognized formats to automatically change the information in the HLR. It should be noted that if the CS domain service data in the AS update request is not in a format that the HLR can understand, the HSS needs to convert the updated CS domain service data into a format that the HLR can understand.

Since the data update command Sh-update in the current Sh interface only supports updating the transparent data (repository data) in the HSS, the activation status of the PSI (Public Service Identity), and the update of the DSAI (Dynamic Service Activation Info), The AS does not support the information of the supplementary service of the CS domain. Therefore, the embodiment of the present invention extends the Sh interface message, and the extended Sh interface message includes: a CS domain user identifier, a service data reference (DataReference) parameter to be updated, Business data content that needs to be updated.

Here, a new value may be added to the user identity, for example: the value is the MSISDN, and when the user does not use the IMS Public User Identity, the user may be identified by the MSISDN. Further, further expansion of Sh-Update is required. Adding a new value to the DataReference. When the value of the DataReference in the Sh-Update command sent by the AS is the value added above, it indicates that the AS requests to update the information of the supplementary service of the CS domain of the user. In addition, a new class needs to be added. Parameters, such new parameters are used to further identify the data that the AS requests to update;

For example, two new parameters are added, which are respectively used to carry the service code of the basic service group code and the supplementary service, and the parameter carrying the supplementary service service code (ServiceCode) is used to identify the supplementary service to be updated by the update operation AS, because one The user may sign a plurality of supplementary services at the same time; the parameter of the service group code (BasicGroup) carrying the basic service is used to identify the supplementary service information of a certain basic service to be updated by the AS in this update operation;

Based on the basic service group code carried in the Sh-Update and the parameters of the service code of the supplementary service, the HSS indicates that the AS requests to update the basic service of the user and the specific supplementary service information of the type.

When the home subscriber unit includes the HLR and the HSS, the home subscription subscriber unit updates the CS domain service information by: when the HSS determines that the user CS domain service information is to be updated, the subscriber MSISDN number is to be updated and updated. The update request of the user CS domain service information is sent to the HLR. If the HLR is set up, the HSS sends a message through the internal interface between them. If the HLR is separated from the HSS, the HSS sends an update message through the external interface between them.

FIG. 14 is a schematic flow chart of a third embodiment of the present invention.

In this embodiment, the AS updates the transparent data in the HSS, and the HSS understands the transparent data and updates to the CS domain synchronously. Here, the home subscriber unit may include the HSS and the HLR, that is, the case where the HSS and the HLR are combined into one independent physical entity, or may be directly a separate HLR. In the figure, only the HSS and the HLR are combined. If the HLR and the HSS are separated, the HSS sends a service data update command to the HLR through the message between the HLR and the HLR, and the HLR updates the service data of the CS domain of the user.

Referring to FIG. 14, the specific process of the embodiment of the present invention is as follows:

Step 1401: The UE sends the user IMS domain service information that needs to be updated to the AS through the Ut interface.

Step 1402: After receiving the service information of the user IMS domain, the AS updates the IMS domain service information of the user according to the request message. Step 1403: The AS sends a Sh interface update (Sh-Update) message to the home subscriber unit, where the user IMS domain service information is included.

Step 1404: The home subscriber unit resolves the message to obtain the user IMS domain service information, and determines the user corresponding to the user IMS domain service information by using the correspondence between the user IMS domain service information and the service information of the user CS domain. The service information of the CS domain, and the service information of the CS domain of the user is used to update the CS domain service information.

Step 1405: After completing the update, the home subscriber unit returns a user update response message to the AS.

FIG. 15 is a schematic flowchart diagram of Embodiment 4 of the present invention. In this embodiment, the user changes the service information of the user's IMS domain in the business hall, and the HSS sends the changed service information to the AS as an example. In this embodiment, the AS sends the CS domain service information through the extended Sh interface. . Moreover, FIG. 15 shows the case where the HSS and the HLR are combined. If the HLR and the HSS are separated, the HSS sends a service data update command to the HLR through the message between the HSS and the HLR, and the HLR updates the service data of the user's CS domain. .

Referring to FIG. 15, the specific process of this embodiment is as follows:

Step 1501: When the IMS domain service information is modified in the home subscriber unit, the HSS sends the service information of the changed IMS domain to the AS through the Sh-Notif message.

Step 1502: The AS returns a Sh-Notif response message to the home subscriber unit.

Step 1503: The AS determines, according to the changed IMS domain service information, whether the service information of the user CS domain needs to be changed, and if necessary, performs step 1504. Otherwise, the process ends.

Step 1504: The AS sends a Sh-update message to the HSS through the extended Sh interface. The parameters in the Sh-update message include the CS user identifier, the DataReference, and the ServiceCode. The CS user ID can be an MSISDN. The value of the DataReference is a new value, which indicates that the CS domain is supplementary service information, and the ServiceCode is a new parameter, indicating the updated supplementary service code.

Step 1505: The home subscription subscriber unit according to the new parameter in the Sh-update message Service

Code, changes the information of the corresponding CS domain service.

Step 1506: The home subscription subscriber unit returns a response to the AS update request Sh-Update. The above is only an example in which the AS discovers the service information of the user IMS domain, and then updates the corresponding service information of the CS domain as an example. In addition, the AS may also receive a request for the terminal to update the CS domain service information of the user. In addition, the service information of the CS domain of the user is directly updated.

16 is a schematic flow chart of the fifth embodiment. In this embodiment, the AS sends a MAP message containing the user CS domain service information to the HSS, and adds the VLR number of the user to the MAP message to avoid

HSS legality check. In the figure, only the case where the HSS and the HLR are combined is shown. If the HLR and the HSS are separated, the HSS sends a service data update command to the HLR through the message between the HSS and the HLR, and the HLR updates the service data of the CS domain of the user.

Referring to FIG. 16, the specific process of this embodiment is as follows:

Step 1601: The UE sends a request for registering CS domain service information to the AS.

Step 1602: After receiving the request for registering the service information of the CS domain, the AS determines that the CS domain service information needs to be updated, and sends a MAP message to the home subscriber unit, where the user needs to be updated.

CS domain service information, and the VLR number where the user is currently located;

Step 1603: The AS sends a MAP registration (MAP_REGISTER_SS) message to the home subscriber unit, where the user CS domain service information is included, where the user CS domain service information includes the registration status of the supplementary service.

Step 1604: After receiving the MAP message, the home subscriber unit determines that the VLR number is included, and does not perform the validity check. The MAP message sent directly from the AS obtains the service information of the user CS domain, and uses the registration of the supplementary service. Status update CS domain service information;

Step 1605: The home subscriber unit returns a response to the AS update request.

The above only uses REGISTER-SS as an example, and other operations such as ERASE-SS, ACTIVATE-SS, DEACTIVATE-SS, etc. are similar.

17 is a schematic diagram of a specific process of the sixth embodiment. In this embodiment, the AS sends a MAP message to the HSS, and the AS identifier is configured in the HSS, so that the HSS does not check the MAP message sent by the AS.

Referring to FIG. 17, the specific process of this embodiment is as follows:

Step 1701: The UE sends a request to register the CS domain service information to the AS;

Step 1702: The AS determines, according to the request for the registration of the CS domain service information, that the AS needs to update the user CS domain service information.

Step 1703: The AS sends a MAP_ERASE_SS message to the home subscriber unit, where the user CS domain service information that needs to be updated, and the identity of the user. Step 1704: After receiving the MAP_ERASE_SS message, the home subscriber unit may find that the AS identifier is included, and the validity of the message is not verified, and the verification is passed, directly according to the requirement in the MAP_ERASE_SS message. The updated user CS domain service information updates the user CS domain service information.

Step 1705: The home subscription subscriber unit returns a response to the AS update request.

The above is just an example of ERASE-SS, other operations such as REGISTER-SS, ACTIVATE-SS, DEACTIVATE-SS, etc.

In the figure, only the case where the HSS and the HLR are combined is shown. If the HLR and the HSS are separated, the HSS sends a service data update command to the HLR through the message between the HSS and the HLR, and the HLR updates the service data of the CS domain of the user.

18 is a schematic flow chart of the seventh embodiment. In this embodiment, the HSS receives a request to update the CS domain service information, and the HSS sends the data to the HLR in the format recognized by the HLR.

Referring to FIG. 18, the specific process of this embodiment is as follows:

Step 1801: The HSS finds that the information of the user CS domain is updated, and the data is organized into a format recognized by the HLR;

Step 1802: The HSS sends an update request to the HLR, which includes the user's Mobile Station International ISDN number (MSISDN), the information to be updated.

If the HLR is set up, the HSS sends a message through the internal interface between them. If the HLR is separated from the HSS, the HSS sends an update message through the external interface between them.

Step 1803: The HLR returns a response to the update request.

19 is a schematic diagram of a specific process of the eighth embodiment. In this embodiment, the user changes the service information of the IMS domain in the AS through the Ut interface, and the AS discovers that the synchronization needs to be updated to the CS domain. In this embodiment, the HSS and the HLR are two independent physical entities. When the HLR is included in the home subscriber unit, the AS directly updates the CS domain information to the HLR, and simulates the VLR to update the CS domain service information.

Referring to FIG. 19, the specific process of this embodiment is as follows:

Step 1901: The UE sends a service request for activating the IMS domain to the AS through the Ut interface. Step 1902: The AS determines, according to the service request, that the CS domain service information needs to be updated. Step 1903: The AS sends a MAP_ ACTIVE_SS message to the HLR to change the activation status of the CS domain service in the HLR, and add the VLR where the user is currently located in the MAP_ ACTIVE_SS. The number, as well as the service information of the user CS domain that needs to be changed, carries the VLR number to check the message through the HLR.

Step 1904: After receiving the MAP_ ACTIVE_SS, the HLR determines that the VLR number is included, and the validity verification succeeds, and directly changes the user CS domain according to the service information of the user CS domain that needs to be changed in the MAP_ ACTIVE_SS. Business information.

Step 1905: The HLR returns a response to the AS update request.

In the eighth embodiment, MAP_ ACTIVE_ SS is taken as an example, and other operations such as REGISTER_SS, ERASE-SS, DEACTIVATE-SS, etc. are similar.

20 is a schematic flow chart of Embodiment 9. In this embodiment, the HSS and the HLR are separately configured, and the AS directly updates the CS domain information to the HLR, and carries its own identifier.

Referring to Figure 20, the specific processing of the present invention is as follows:

Step 2001: The UE sends a request to the AS to activate the CS domain service.

Step 2002: After receiving the request, the AS determines that the CS domain service information of the user needs to be updated. Step 2003: The AS sends a MAP-DEACTIVE_SS message to change the activation status of the CS domain service in the HLR, where the user's CS domain service information is the CS domain service. Activation status information.

Step 2004: After receiving the MAP_DEACTIVE_SS message, the HLR determines that there is an AS identifier in the message, and then does not perform legality verification on the message, that is, the verification is passed, and according to the user CS domain service information in the message, directly Update the service information of the user CS domain.

Step 2005: The HLR returns a response to the AS update request.

In the embodiment 9, the DEACTIVE-SS is taken as an example, and other operations such as REGISTERIVATE SS, ERASE-SS, ACTIVATE-SS, etc. are similar.

As shown in FIG. 21a, the system for modifying the CS domain service information provided by the embodiment of the present invention includes: a home subscription subscriber unit 10, where the home subscription subscriber unit 10 may include: a first acquisition unit 11 and a first update Unit 12.

The first obtaining unit 11 is configured to obtain user CS domain service information that needs to be updated, and the first updating unit 12 is configured to modify the CS domain service information by using the user CS domain service information that needs to be updated.

The system may further include an AS 20, the AS 20 including a second acquisition unit 21 and a first transmission Unit 22. The second obtaining unit 21 is configured to obtain user CS domain service information that needs to be updated, and the first sending unit 22 is configured to send the user CS domain service information that needs to be updated to the home subscription user. unit.

Referring to FIG. 21b, the second obtaining unit 21 may include: a third obtaining unit 24 and a first mapping unit 23. The third obtaining unit 24 is configured to obtain the service information of the updated user IMS domain, where the first mapping unit 23 is configured to obtain the user IMS according to the correspondence between the user IMS domain service information and the user CS domain service information. User CS domain service information corresponding to the domain service information that needs to be updated.

Referring to FIG. 21c, the second obtaining unit 21 may include: a first receiving unit 29 and an analyzing unit 30. The first receiving unit 29 is configured to receive a request for updating the CS domain service information from the user terminal, and the parsing unit 30 is configured to parse the user that needs to be updated from the request that the user terminal updates the CS domain service information. CS domain business information.

Referring to FIG. 21d, the third obtaining unit 24 may include: a first determining unit 27 and an extracting unit 28. The first determining unit 27 is configured to determine whether the user terminal updates the user IMS domain service information. The extracting unit 28 is configured to: if the user terminal updates the user IMS domain service information, extract the updated IMS domain service. information.

Referring to FIG. 21e, the home subscription subscriber unit 10 may further include: a second determination unit 13 and a second transmission unit 14. The second determining unit 13 is configured to determine whether the service information of the user IMS domain is modified. The second sending unit 14 is configured to send the modified user IMS domain service information when the service information of the user IMS domain has been modified. Giving the third acquisition unit.

The AS further includes: a transmission interface, configured to transmit the user CS domain service information that needs to be updated to the home subscription subscriber unit.

The transmission interface includes an extended Sh interface, and the extended Sh interface is configured to send an extended Sh interface message to the home subscription subscriber unit, where the extended Sh interface message is used to carry the update required. CS domain service information;

The extended Sh interface message includes the following parameters:

CS domain user ID, data reference parameters of business data that need to be updated, and business data content that needs to be updated.

The transmission interface includes a MAP protocol interface, and the MAP protocol interface is used to return to the The loyalty subscriber unit sends a MAP message, where the MAP message includes a legality verification identifier and user CS domain service information that needs to be updated;

Referring to FIG. 21f, the home subscriber unit 10 further includes: an checking unit 15, configured to determine whether the received MAP message includes a validity verification identifier, and if so, instructing the first acquiring unit to The user's CS domain service information that needs to be updated is extracted from the MAP message; the legality verification identifier includes a VLR number, or an AS number, or a preset identifier.

Referring to Figure 21g, the system further includes an AS 20, the AS 20 including:

a third sending unit 31, configured to send user IMS domain service information that needs to be updated to the home subscriber unit;

The first obtaining unit 11 includes: a second mapping unit 111 and a second receiving unit 112. The second receiving unit 112 is configured to receive the user IMS domain service information that needs to be updated, and the second mapping unit 111 is configured to obtain the user according to the correspondence between the user IMS domain service information and the user CS domain service information. User CS domain service information corresponding to the IMS domain service information that needs to be updated.

Referring to FIG. 21h, an apparatus for modifying CS domain information provided by this embodiment includes: a receiving unit 81, a mapping unit 82, and an updating unit 83.

The receiving unit 81 is configured to receive user IMS domain service information that needs to be updated from the AS, and the mapping unit 82 is configured to obtain the user IMS domain service according to the correspondence between the user IMS domain service information and the user CS domain service information. The user CS domain service information that needs to be updated corresponding to the information; the updating unit 83 is configured to modify the CS domain service information by using the CS domain service information of the user that needs to be updated.

The device for changing the CS domain information provided in this embodiment may be an independent physical entity, which is set in the communication network as an enhanced network element, or may be set as a logical entity in an existing communication device, such as an HLR. Or in a physical entity that includes HLR and HSS. When acting as a stand-alone physical entity, the device needs to communicate with the AS, as well as devices that store CS domain service information (eg, HLR, or HLR/HSS), which can use the same between existing AS, HLR/HSS The communication protocol communicates, and other protocols can also be used for communication.

In addition, it should be understood that those skilled in the art can understand that all or part of the steps of implementing the above embodiments may be completed by hardware related to program instructions, and the program may be stored in a computer readable storage medium. The storage medium is, for example, a ROM/RAM, a magnetic disk, an optical disk, or the like. The embodiment of the present invention extends the Sh interface between the AS and the HSS, so that the Sh interface supports the transmission of the CS domain information of the user, so that the AS can obtain the required information of the user in the CS domain as needed. After the AS obtains the CS domain subscription data information, the AS can apply the information to perform various applications, for example: performing cross-domain service control in the IMS domain according to the subscription data of the CS domain, and synchronizing the CS domain subscription information with the IMS domain subscription information. Set, according to the obtained CS domain and IMS domain status information, subscription information, etc. for domain selection and other applications. It can be seen that, when the user has the contract in the CS domain and the IMS domain, the IMS application of the present invention can obtain not only the subscription information of the user IMS domain but also the CS domain subscription information of the user, so that the IMS application can These cross-domain business networks provide better business control.

In the embodiment of the present invention, the home subscriber unit needs to obtain the user CS domain service information to be updated; the home subscriber unit uses the user CS domain service information that needs to be updated to modify the CS domain service information. Therefore, the user CS domain service information associated with the user IMS domain service information is synchronously set after the IMS domain service information is updated, and the two domain services are guaranteed. The consistency of the settings improves the user's business experience.

While the invention has been described by the embodiments of the present invention, it will be understood that

Claims

Rights request

A method for acquiring circuit switched domain information by an IP multimedia subsystem, comprising:

The home subscription server HSS receives the query command sent by the application server AS through the Sh interface; the HSS returns a response message to the AS according to the query command, where the response message carries

User circuit requested by the AS CS domain subscription information.

2. The method according to claim 1, wherein the query command is a Sh-Pull query command, including:

The parameter of the supplementary service information type that is attached to the basic service requested by the AS, and is used to carry the basic service group code; and/or

Identifies the parameters of the supplementary service requested by the AS for this query operation. This parameter is used to carry the supplementary service code.

The method according to claim 2, wherein the Sh-Pull query command comprises: a mobile subscriber international number MSISDN number, a data reference parameter, and a basic service group code parameter, configured to query a specific basic service group to hang All supplementary business information; or

The MSISDN number, the data reference parameter, and the supplementary service code parameter are used to query specific supplementary service information that is hanged under all basic service groups; or

The MSISDN number, the data reference parameter, the basic service group code parameter, and the supplementary service code parameter are used to query specific supplementary service information that is hanged under a specific basic service group.

The method according to claim 2, wherein the Sh-Pull query command comprises:

The MSISDN number and the user that the AS requests to query the CS domain subscription information is the data reference parameter of the supplementary service information, and is used to query all the basic services and the supplementary service information that is attached thereto.

The method according to claim 1, wherein the query command is a Sh-Pull query command, including:

The parameter that identifies the basic service information requested by the AS, and is used to carry the basic service code; or

The MSISDN number and the user that the AS requests to query the CS domain subscription information is a new data reference parameter of the basic service information, and is used to query all basic service information subscribed by the user.

6. The method according to claim 1, wherein the HSS is based on the query The steps to return a response message include:

After receiving the query command, the HSS obtains the user CS domain subscription information from the home location register HLR or the internal HLR subset;

The HSS returns the obtained user CS domain subscription information to the AS.

7. The method according to claim 1, further comprising:

The AS is applied according to the acquired user CS domain subscription information, and the application includes: performing cross-domain service control, CS domain subscription information, and IMS domain subscription information synchronization setting and domain selection in the IP multimedia subsystem domain.

8. A method for acquiring circuit switched domain information by an IP multimedia subsystem, comprising:

The method according to claim 8, wherein the subscription request is a Sh-Subs-Notif subscription request, including:

Identifies the parameters of the supplementary service requested by the AS for this subscription operation. This parameter is used to carry the supplementary service code.

10. The method according to claim 9, wherein the Sh-Subs-Notif subscription request comprises:

The MSISDN number, the data reference parameter, and the basic service group code parameter are used to subscribe to all supplementary service information that is hanged under a specific basic service group; or

MSISDN number, data reference parameter and supplementary service code parameter, used to subscribe to specific supplementary service information hanged under all basic service groups; or

The method according to claim 9, wherein the Sh-Subs-Notif subscription request comprises: The MSISDN number and the user CS domain subscription information indicating the AS subscription are data reference parameters of the supplementary service information, and are used to subscribe to all the basic services and the supplementary service information that is attached thereto.

The parameter of the basic service information requested by the AS for the subscription operation, which is used to carry the basic service code; or

The MSISDN number and the user CS subscription information indicating the subscription of the AS are the new data reference parameters of the basic service information, and are used to subscribe to all basic service information subscribed by the user.

The method according to claim 8, wherein the step of the HSS issuing a notification message to the AS when the user CS domain information changes includes:

The HSS senses that the CS domain information changes.

The HSS notifies the AS of the change event and the changed user CS domain information according to the subscription information of the AS.

The method according to claim 13, wherein the user CS domain information comprises: user CS domain subscription data, and/or user registration status, location information.

The method according to claim 13, wherein the step of the HSS notifying the AS of the change event and the changed user CS domain information according to the subscription information of the AS includes:

When the HSS receives the message that the user registration status of the HLR changes, the user status change event and the changed status are sent to the AS; or

After receiving the message that the user supplementary service information sent by the HLR changes, the HSS sends the changed status information of the supplementary service and the basic service group to the AS.

16. The method according to claim 15, further comprising:

The HLR senses that the first attachment operation after the user has roamed or the location register VLR clears a user event, and sends a message to the HSS that the user status changes; or

The HLR senses that the VLR sends the message synchronization update data to the HLR or the administrator changes the user supplementary service data through the HLR interface, and then sends a message to the HSS that the user supplementary service changes.

17. The method according to claim 8, further comprising:

The AS performs the application according to the acquired CS domain information of the user, where the application includes: performing cross-domain service control, CS domain subscription information, and synchronization setting and domain of the IMS domain subscription information in the IP multimedia subsystem domain. Choose.

18. A method for applying circuit switching domain information by an IP multimedia subsystem, the method comprising:

The application server AS obtains the user circuit switched CS domain information from the home subscription server HSS through the Sh interface.

The AS applies the acquired user CS domain information in the IP multimedia subsystem domain according to the service logic.

The method according to claim 18, wherein the step of the AS acquiring the user CS domain information from the HSS through the Sh interface includes:

The AS obtains the user CS domain information from the HS interface through the Sh interface; or

The AS subscribes to the HSS through the Sh interface to obtain user CS domain information.

The method according to claim 19, wherein the step of the AS acquiring the CS domain information of the user by using the Sh interface to the HSS includes:

The Sh-Pull query command of the Sh interface between the AS and the HSS is extended to support the query of the user CS domain subscription information;

The AS sends the Sh-Pull query command to the HSS through the Sh interface to obtain the CS domain subscription information of the user.

The method according to claim 19, wherein the step of the AS subscribing to the HSS to obtain the user CS domain information through the Sh interface includes:

Extend the Sh-Subs-Notif subscription command of the Sh interface between AS and HSS to support users

Subscription of CS domain information;

The AS sends the Sh-Subs-Notif subscription command to the HSS through the Sh interface to obtain the CS domain subscription information of the user.

The method according to claim 19, wherein the step of the AS applying the acquired user CS domain information in the IP multimedia subsystem domain according to the service logic includes:

The AS performs cross-domain service control in the IP multimedia subsystem domain according to the obtained user CS domain information; or

The AS performs synchronization setting of the CS domain subscription information and the IMS domain subscription information in the IP multimedia subsystem domain according to the obtained user CS domain information; or The AS performs domain selection in the IP multimedia subsystem domain according to the acquired user CS domain information.

23. A method of changing circuit switched domain information, the method comprising:

The home subscriber unit obtains the CS circuit service information that needs to be updated. The home subscriber unit uses the user CS domain service information that needs to be updated to modify the CS domain service information.

The method according to claim 23, wherein the step of the home subscription subscriber unit obtaining the user CS domain service information that needs to be updated includes:

The application server AS obtains the user CS domain service information that needs to be updated;

The AS sends the user CS domain service information that needs to be updated to the home subscription subscriber unit.

The method according to claim 24, wherein, when the AS determines that the user IP multimedia domain service information changes, and needs to update the service information of the user CS domain, the method further includes: the AS obtaining the updated user IP multimedia subsystem IMS domain service information;

The AS obtains the user CS domain service information that needs to be updated according to the correspondence between the user IMS domain service information and the user CS domain service information.

The method according to claim 25, wherein the step of the AS obtaining the updated user IMS domain service information comprises:

The user terminal updates the user IMS domain service information in the AS;

The AS obtains updated user IMS domain service information from the updated service information.

After the home subscriber unit determines that the user IMS domain service information is modified, the home subscriber unit sends the modified user IMS domain service information to the AS.

The method according to claim 24, wherein the CS domain service information that needs to be updated is obtained by the AS from a request of the received user terminal to update the CS domain service information.

The method according to claim 24, wherein the step of the AS transmitting the obtained user CS domain service information that needs to be updated to the home subscription subscriber unit further comprises: the AS to the home subscription subscriber unit Sending a request to update the user CS domain, including user CS domain service information that needs to be updated; After receiving the request for updating the CS domain of the user, the home subscription subscriber unit obtains the user CS domain service information that needs to be updated from the request of the update user CS domain.

The method according to claim 29, wherein the request for updating the user CS domain is a mobile application part MAP message including a validity verification identifier and user CS domain service information that needs to be updated,

After the MME message is received by the home subscriber unit, the method further includes:

Determining that the MAP message includes a validity verification identifier, and obtaining, from the MAP message, user CS domain service information that needs to be updated;

The legality verification includes: a visit location register number, or an application server number, or a pre-set identifier.

The method according to claim 23, further comprising:

Sending, by the AS, user IMS domain service information that needs to be updated to the home subscription subscriber unit;

The home subscription subscriber unit updates the user IMS domain service information by using the user IMS domain service information that needs to be updated, and uses the correspondence between the user IMS domain service information and the user CS domain service information to obtain the service IMS domain service information corresponding to the user. The user CS domain business information needs to be updated.

32. A system for changing circuit switched domain information, comprising: a home subscription subscriber unit, wherein the home subscription subscriber unit comprises:

33. The system according to claim 32, further comprising an application server AS, the AS comprising:

a second obtaining unit, configured to obtain user CS domain service information that needs to be updated;

And a first sending unit, configured to send the user CS domain service information that needs to be updated obtained by the second acquiring unit to the home subscription subscriber unit.

The system according to claim 33, wherein the second obtaining unit comprises: a third obtaining unit, configured to obtain service information of the updated user IMS domain;

a first mapping unit, configured to perform, according to user IMS domain service information and user CS domain service information In response, the user CS domain service information that needs to be updated corresponding to the user IMS domain service information is obtained.

The system according to claim 32, wherein the second obtaining unit comprises: a first receiving unit, configured to receive a request for updating CS domain service information from a user terminal; and a parsing unit, configured to receive The user terminal updates the CS domain service information request to obtain the CS domain service information that needs to be updated.

The system according to claim 33, wherein the AS further comprises: a transmission interface, configured to transmit the user CS domain service information that needs to be updated to the home subscription subscriber unit.

The system according to claim 36, wherein the transmission interface comprises a MAP protocol interface, configured to send a MAP message to the home subscription subscriber unit, where the MAP message includes a legality verification identifier and needs to be updated. User CS domain service information;

The home subscription subscriber unit further includes:

An checking unit, configured to determine whether the received MAP message includes a validity verification identifier, and if yes, instructing the first obtaining unit to extract, from the MAP message, user CS domain service information that needs to be updated;

The validity verification includes a visit location register VLR number, or an AS number, or a pre-set identifier.

The system of claim 32, further comprising an application server AS, the AS comprising:

a third sending unit, configured to send user IMS domain service information that needs to be updated to the home subscription subscriber unit;

The first obtaining unit includes:

a second receiving unit, configured to receive the user IMS domain service information that needs to be updated, where the second mapping unit is configured to obtain the user IMS domain service information according to the correspondence between the user IMS domain service information and the user CS domain service information. Corresponding user CS domain service information that needs to be updated.

39. A home subscription subscriber unit, comprising:

The first update unit is configured to modify the CS domain service information by using the user CS domain service information that needs to be updated obtained by the first acquiring unit.

40. The home subscriber unit according to claim 39, wherein the first acquiring unit comprises:

a second receiving unit, configured to receive user IMS domain service information that needs to be updated from the AS, and a second mapping unit, configured to obtain the user IMS domain service according to the correspondence between the user IMS domain service information and the user CS domain service information The user CS domain service information corresponding to the information that needs to be updated.

41. An application server, comprising:

The application server according to claim 41, wherein the second acquiring unit comprises:

a third obtaining unit, configured to obtain service information of the updated user IMS domain;

The first mapping unit is configured to obtain, according to the corresponding relationship between the user IMS domain service information and the user CS domain service information, the user CS domain service information that needs to be updated corresponding to the user IMS domain service information.

43. An apparatus for modifying circuit switched domain information, comprising:

a mapping unit, configured to obtain user CS domain service information that needs to be updated corresponding to the user IMS domain service information according to the correspondence between the user IMS domain service information and the user CS domain service information; and an update unit, configured to use the user that needs to be updated CS domain service information, modify CS domain service letter