WO2011003330A1

WO2011003330A1 - Method for selecting application front-end and user data storage

Info

Publication number: WO2011003330A1
Application number: PCT/CN2010/074419
Authority: WO
Inventors: 丁兆明
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-07-07
Filing date: 2010-06-24
Publication date: 2011-01-13
Also published as: CN101945375A

Abstract

A method for selecting an application front-end is provided, which includes: user data storage receives the request message sent by the application front-end, and saves the address information of application front-end included in the request message; when a notification message is sent, user data storage selects the saved address information of application front-end as the application front-end to send the notification message. A user data storage is also provided, and the invention can effectively solve the problem that the notification message is sent to its initial subscription.

Description

Method for selecting application front end and user data storage technology field

The present invention relates to a subscription notification technology in a User Data Convergence (UDC) network, and more particularly to a method for selecting an application front end and user data storage when a notification message is delivered. Background technique

With the development of hardware and software technologies and services of Internet technology (IT, Internet Technology), in addition to the traditional Public Switched Telephone Network (PSTN) and the second generation (2G, 2nd Generation) mobile communication network, More and more communication networks have been introduced and become standards, such as third-generation (3G, 3rd Generation) mobile communication networks, IP Multimedia Sub-System (IMS) networks, and global access for microwave access (WiMAX, Worldwide Interoperability for Microwave Access) networks, softswitch networks, etc., which result in a large increase in user data in the network.

With the proliferation of user data in the network, the original user data storage methods and delivery methods have become more and more difficult to adapt to the rapid development of the network. The decentralized management of data has led to the following problems: Operational Expenditure (OPEX, Operating Expenditure) Increased, garbage data is difficult to eliminate, data consistency is difficult to guarantee, data security guarantee is difficult, data mining analysis lacks effective means; coupled with the inconsistent external interface of data storage network elements, resulting in complex data access interfaces, tightly coupled interfaces and services, Data cannot be transmitted transparently, and new services are difficult to implement quickly and efficiently. User data management issues have become increasingly apparent.

To this end, the industry has proposed the concept of a unified user data model, namely: the data of the same user distributed on different network elements is merged, the user identification is used as the basic identifier, and organized according to a unified data structure, as the unique user data of all networks. source. For terminal data, access or core network Convergence, application and data decoupling of network data, business data and Internet service data, unified management and establishment of a unified user data center can simplify the network, shorten the time for new service release, promote business innovation, and provide operators with competitive capabilities. Business integration laid the foundation.

In physical implementation, the user data model can be unified in the network's unique data storage network element: the central database (CDB, Center Database), which stores the user's unified data model to ensure data consistency, reliability, and Security, providing an open interface independent of services and data, and providing data access services for other data query network elements.

Figure 1 depicts the network system model established by the 3rd Generation Partnership Project (3GPP) in the prior art on user data fusion. As shown in Figure 1, the UDC network includes user data warehousing and support. The application front end of the application, where the application front end processes data-independent application logic, is not responsible for storing user data information, and supports application front ends of different applications to be connected to different network entities, such as: application servers supporting or not supporting UDC, business support System (BSS, Business Supporting System), etc.; User data warehousing as a user data center in the network, which combines various application data and provides a unified open Ud interface for various application front ends.

The UDC network is relatively independent and does not affect the existing network system. That is, the existing interfaces between the application front end and the service layer application, BSS system, etc. are not affected. For example, an application front end supporting a home subscriber service (HSS) application needs to support a Diameter-based protocol interface supported by the HSS, including a Sh interface with an application server (AS, Application Server), which is referred to herein. HSS application front end. The UDC network needs to support the Provisioning function, that is, to provide service support for the BSS system, for example, user number registration, user service subscription data modification, etc., the Provisioning application front end is located between the BSS and the user data storage, and the implementation is related. Business processing, providing accessibility support for UDC networks.

When deploying a UDC network, the operator does not upgrade all the application servers related to it. The upgraded application server can embed the function of the application front end and directly provide user data. The access interface between the warehousing, referred to herein as the UDC-enabled application server. The un-upgraded application server does not have a direct interface with the user data warehousing. It needs to access the user data warehousing through the original Sh interface through the HSS application front end. This article refers to the application server that does not support UDC.

The UDC network supports the subscription notification function. FIG. 2 is a schematic diagram of establishing a subscription relationship based on the UDC network. As shown in FIG. 2, the user data storage preset notification trigger condition and notification type, and the notification trigger condition includes data subscription status and data change. Status, preset as data unsubscribed and data unchanged; the notification type is set to subscription data subscription notification.

An application server that supports user data fusion, including an application server application front end, directly sends a subscription subscription notification request message to the user data storage through the Ud interface, or carries a tampering data request message identified by a subscription to notification request (SNR, Subscription to Notification Request). Request to establish a subscription notification relationship. The application server that does not support user data fusion needs to send a subscription subscription notification request message through the existing Sh interface of the HSS application front end. The HSS application front end sends a subscription subscription notification request message to the user data storage through the Ud interface, or carries the SNR identifier. Modify the data request message to request to establish a subscription notification relationship.

After receiving the subscription subscription notification request, the user data warehouse establishes a subscription notification relationship, that is, saves the subscription data subscription notification data information, including the subscriber address and the subscription data, where the subscriber address is an application server identifier or address, or an application server application. The front end identifier or address; and, the data subscription status corresponding to the notification trigger condition is set to be subscribed. The subscription data describes the user subscription data corresponding to the subscription data subscription notification event, which may be a request data identifier or a request data domain name, rather than the specific content of the user subscription data.

FIG. 3 is a schematic diagram of a notification triggering process when the service subscription data is modified. As shown in FIG. 3, the notification triggering process includes the following steps:

Step S310, the BSS sends a modify service subscription data request message to the Provisioning application front end; Step S320, after receiving the modified service subscription data request message from the BSS, the Provisioning application front end sends a modify user data request message to the user data warehouse through a unified Ud interface with the user data storage, so as to be modified and saved in the user data storage. Business contract data;

Step S330, after receiving the modified user data request message sent by the Provisioning application front end, the user data storage performs access control.

After validating the Provisioning application front end and validly authorizing the request data, the user data warehouse performs an update operation of the service contract data;

Step S340, the user data warehousing check notification trigger condition, that is, determining whether the request data changes, and checking the subscription status of the request data; here, the request data service subscription data;

If the request data changes, and the change notification event of the request data has been subscribed, the user data warehousing triggers the notification process; otherwise, the notification process of step S350 and step S360 is not triggered, and the current process flow is ended;

Step S350a or S350b, the user data warehousing sends a notification message to the notification event subscriber through the Ud interface, the notification message carries the notification type and the notification data information; afterwards, step S370 is performed;

The notification type is set as a subscription data subscription notification, and is used to indicate that the application front end supporting the subscription notification application sends the subscription notification data to the subscriber;

The application front end supporting the subscription notification application may be the HSS application front end, and the subscription notification data is sent to the application server through the notification message of the Sh interface; or the AS application front end supporting the UDC network;

The notification data information includes a subscriber address, a user identifier, and subscription notification data, and the like; wherein the subscription notification data is the latest change content of the data subscribed to the subscription notification event; where the subscriber address is an application server identifier or address, or an application server Apply the front end identifier or address; The user identifier is used to uniquely identify a user identity, such as an International Mobile Subscriber Identity (IMSI);

Step S360a or S360b, the HSS application front end or the AS application front end returns a notification response message to the user data warehousing; after that, step S370 is performed;

Step S370, the user data warehousing returns a modify user data response message to the Provisioning application front end;

Step S380: The Provisioning application front end returns the result of the user data modification to the BSS by modifying the service subscription data response message.

As can be seen from the above steps, the initial subscriber of the notification message can be an AS or a specific application front end, for example, an application server application front end. When the notification message is triggered, the user data warehousing needs to send the notification message to the initial subscriber of the message. For example, when the initial subscriber is the application server, the user data warehousing needs to select a suitable HSS application front end, and indirectly forwards the notification message to Application server; When the initial subscriber is a specific application front end, the user data warehouse directly selects the application front end and sends a notification message to the application front end.

The prior art does not clarify the routing method when the user data warehouse sends a notification message in this application scenario. That is, in the UDC network, when the notification message is sent, how to effectively send the notification message to the initial subscriber of the message, that is, how to select a suitable application front end to send the notification message to the initial subscriber of the notification message, No effective solution has yet been proposed. Summary of the invention

In view of this, the main object of the present invention is to provide a method for selecting an application front end and user data storage, which can effectively solve the problem of sending a notification message to the initial subscriber of the message.

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

The present invention provides a method for selecting an application front end, including:

The user data warehouse receives the request message sent by the application front end, and saves the application front end address information in the request message; When the notification message is sent, the user data storage selects the saved application front end address information as an application front end for sending the notification message.

The method also includes: the user data warehousing sends a notification message to the selected application front end. In the above solution, the request message is a subscription subscription notification request message based on the Ud interface, or a modified user data request message carrying the subscription notification request SNR identifier.

In the above solution, the request message further includes subscription information; the user data warehousing further stores subscription information in the request message; wherein the subscription information includes subscriber address information and subscription data.

In the above solution, the subscriber address information and the application front-end address information are identifiers or addresses of the application server application front end; or the subscriber address information is an identifier or address of the application server, and the application front-end address information is the HSS. The ID or address of the application front end.

In the above solution, when the user data storage saves the application front end address information, the method further includes: the data subscription status corresponding to the trigger condition of the user data storage setting notification condition is subscribed.

The present invention also provides a user data storage, comprising: an information acquisition unit, an information storage unit, and an application front end selection unit;

The information acquiring unit is configured to receive a request message sent by the application front end, and obtain application front end address information carried in the request message;

The information saving unit is configured to save the acquired application front end address information;

The application front end selection unit is configured to select an application front end according to the saved application front end address information.

In the above solution, the user data warehousing further includes a notification message sending unit, configured to send the notification message to the selected application front end.

In the above solution, the information acquiring unit is further configured to acquire subscription information including subscription address information and subscription data, where the information storage unit is further configured to save the subscriber address information and the subscription. Data.

The method for selecting an application front end and the user data storage provided by the invention saves the application front end address information when the user data warehouse establishes a subscription notification relationship; correspondingly, when the notification message is sent, the user data storage is based on the saved application front end The address information selects an application front end, and then sends a notification message to the selected application front end. In this way, not only can the effective application front end be effectively selected, but the notification message is accurately sent to the initial subscriber of the message. Moreover, the invention is simple and convenient to implement, and does not need to make major changes to the original subscription notification mechanism, and effectively solves the problem. The technical problems existing in the prior art. DRAWINGS

1 is a schematic diagram of the composition of a UDC network in the prior art;

2 is a schematic diagram of an implementation of a subscription notification relationship established on a UDC network according to the prior art; FIG. 3 is a schematic diagram of a notification triggering process of modifying service subscription data based on a UDC network in the prior art;

4 is a schematic diagram of an implementation process of selecting an application front-end method according to the present invention;

FIG. 5 is a schematic diagram of an implementation process for establishing a subscription notification relationship in the present invention; FIG.

FIG. 6 is a schematic diagram of an implementation process of selecting an application front end when a notification of a service subscription data modification is triggered according to an embodiment of the present invention. detailed description

The basic idea of the present invention is: the user data warehousing saves the application front-end address information when establishing the subscription notification relationship; correspondingly, when the notification message is sent, the user data warehousing selects the application front-end according to the saved application front-end address information.

Further, the user data warehousing sends a notification message to the selected application front end.

Here, the user data repository also stores subscription information when establishing a subscription notification relationship, the subscription information including subscriber address information and subscription data. The subscription data is used to describe the user subscription data corresponding to the subscription data subscription notification event, including requesting the data identifier, or requesting the data domain name; the subscriber address information is used to describe the initial subscriber of the subscription notification message, and the subscriber address information is the subscription. The party identifier or the subscriber address. Specifically, the subscriber address information is the identifier or address of the AS, or the identifier or address of the AS application front end; the subscriber identifier is the host name, or host name, and i or name of the subscriber. The application front-end address information is the AS application front-end identifier or address, or the HSS application front-end identifier or address; the application front-end identifier is the application front-end host name, or host name and domain name.

The method for selecting an application front end according to the present invention is as shown in FIG. 4, and includes the following steps:

Step 401: The user data warehouse receives the request message sent by the application front end, and saves the application front end address information in the request message;

Here, the request message is a subscription subscription notification request message based on a Ud interface, or carried

a modified user data request message of the SNR identifier; the request message carries application front end address information;

The request message also carries subscription information including subscriber address information and subscription data; correspondingly, the user data repository also stores subscriber address information and subscription data.

For an application server that supports the UDC network, the application front-end address information is the identifier or address of the AS application front-end, and the subscriber address information is also the identifier or address of the AS application front-end; for an application server that does not support the UDC network, the application front-end The address information is the identifier or address of the HSS application front end, and the subscriber address information is the identifier or address of the application server.

Step 402: When the user data warehouse sends the notification message, the saved application front-end address information is selected as the application front end for sending the notification message; that is, the application front end corresponding to the saved application front-end address information is selected as the application front end for sending the notification message;

The notification message includes the subscriber address information and the subscription data, and the subscriber address information and the subscription data are collectively referred to as subscription information.

Further, the user data warehousing sends a notification message to the selected application front end. The implementation process of establishing a subscription notification relationship and selecting an application front-end method according to the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

FIG. 5 is a schematic diagram of an implementation process for establishing a subscription notification relationship in the present invention. As shown in FIG. 5, the establishment of a subscription notification relationship in the present invention includes the following steps:

In step S510, the AS application front end/HSS application front end sends a subscription subscription notification request message based on the Ud interface or a modified user data request message carrying the SNR identifier to the user data storage; here, the application server supporting the UDC network is applied through the AS. The front end sends a subscription subscription notification request message based on the Ud interface to the user data storage, or a modified data request message carrying the SNR identifier;

For an application server that does not support the UDC network, the SH interface-based subscription subscription notification request message is sent to the HSS application front end, and after the HSS application front end processing, the UD interface-based subscription subscription notification request message is sent to the user data storage, or A modified data request message carrying the SNR identifier.

The request message carries the subscriber address information and the application front-end address information. For the application server supporting the UDC network, the subscriber address information and the application front-end address information refer to the identifier or address of the application server application front end; The application server of the network, the address information of the subscriber refers to the identifier or address of the application server, and the application front-end address information refers to the identifier or address of the front end of the HSS application.

Step S520, the user data warehouse receives the subscription subscription notification request message, or the modification data request message carrying the SNR identifier, performs access control, performs authentication and authorization processing, performs effective authentication on the AS application front end or the HSS application front end, and performs request After the data is effectively authorized, the user data storage performs step S530;

Step S530, the user data storage saves the subscription information and the application front-end address information; wherein, the subscription information includes the subscriber address information and the subscription data; the subscription data is used to describe the user subscription data corresponding to the subscription data subscription notification event, and may be the request data identifier. , or Request a data domain name.

Further, the user data warehousing can set the data subscription status corresponding to the notification trigger condition to be subscribed. Here, setting the subscribed state is convenient for the subsequent process to be smoothly completed, as to what the notification triggering condition can be, how to set it is irrelevant to the present invention, and is a prior art, and will not be described in detail herein.

Step S540: The user data warehousing returns a subscription-based notification response message or a modified user data response message based on the Ud interface to the AS application front end or the HSS application front end.

6 is a schematic diagram of an implementation process of selecting an application front end when a notification of a service subscription data modification is triggered in the embodiment of the present invention. As shown in FIG. 6, the implementation process of selecting an application front end to be applied to the service subscription data modification notification process includes the following steps:

Steps S610 to S630 are the same as the processing of steps S310 to S330 in FIG. 3; Step S640, the user data warehouse inspection notifies the trigger condition, and checks the subscription status of the requested data;

Here, the notification trigger condition is to determine whether the request data changes, that is, to determine whether the service subscription data changes;

If the request data changes, and the change notification event of the request data has been subscribed, the user data warehousing triggers the notification process, and proceeds to step S650; otherwise, the notification process is not triggered, skips steps S650, S660a, S670a, or skips Steps S650, S660b, S670b, directly executing step S680;

Step S650, the user data storage selects an application front end according to the application front end address information saved by itself, that is, directly selects the saved application front end;

Specifically, if the application front end address information is the HSS application front end, step S660a and step S670a are performed; if the application front end address information is the AS application front end, step S660b and step S670b are performed;

Steps S660a ~ S670a, user data warehousing is sent to the selected HSS application front end based on The notification message of the Ud interface, the notification process is the same as the process of steps S350a to S360a in FIG. 3; after that, steps S680 to S690 are performed;

Steps S660b ~ S670b, user data warehousing is sent to the selected AS application front end based on

The notification message of the Ud interface, the notification process is the same as the processing of steps S350b to S360b in FIG. 3; thereafter, steps S680 to S690 are performed;

Steps S680 to S690, the flow is the same as the processing of steps S370 to S380 in FIG.

In order to implement the above method, the present invention also provides a user data storage, including an information acquisition unit, an information storage unit, and an application front end selection unit;

For the application server supporting the UDC network, the subscriber address information and the application front-end address information refer to the identifier or address of the application server application front end; for the application server that does not support the UDC network, the subscriber address information refers to An identifier or an address of the application server, where the application front-end address information refers to an identifier or an address of the HSS application front end;

Further, the information acquiring unit is further configured to acquire subscription information including subscription address information and subscription data.

Further, the information saving unit is further configured to save the subscriber address information and the subscription data. The application front end selection unit is configured to select an application front end according to the saved application front end address information.

The user data warehousing can further include a notification message sending unit for transmitting the notification message to the selected application front end.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included. Within the scope of protection of the present invention.

Claims

Claim

A method for selecting an application front end, the method comprising:

The user data storage receives the request message sent by the application front end, and saves the application front end address information in the request message;

When the notification message is sent, the user data warehouse selects the saved application front-end address information as the application front end for sending the notification message.

2. The method of claim 1 wherein the method further comprises: the user data warehousing transmitting the notification message to the selected application front end.

The method according to claim 1 or 2, wherein the request message is a subscription subscription notification request message based on the Ud interface, or a modified user data request message carrying the subscription notification request SNR identifier.

The method according to claim 1 or 2, wherein the request message further includes subscription information; the user data warehousing further retains subscription information in the request message;

The subscription information includes subscriber address information and subscription data.

The method according to claim 4, wherein the subscriber address information and the application front-end address information are identifiers or addresses of the application server application front end; or the subscriber address information is an identifier of the application server. Or address, the application front end address information is an identifier or address of the HSS application front end.

The method according to claim 4, wherein, when the user data storage saves the application front-end address information, the method further includes: the user data storage setting notification triggering condition corresponding to the data subscription status is subscribed .

7. A user data storage, wherein the user data storage comprises: an information acquisition unit, an information storage unit, and an application front end selection unit; wherein

The information acquiring unit is configured to receive a request message sent by the application front end, and obtain application front end address information carried in the request message; The information storage unit is configured to save the acquired application front end address information, and the application front end selection unit is configured to select an application front end according to the saved application front end address information.

8. The user data warehousing according to claim 7, wherein the user data warehousing further comprises a notification message sending unit for transmitting the notification message to the selected application front end.

The user data storage unit according to claim 7 or 8, wherein the information obtaining unit is further configured to acquire subscription information including subscription address information and subscription data;

The information saving unit is further configured to save subscriber address information and subscription data.

The user data warehousing according to claim 9, wherein the subscriber address information and the application front end address information are identifiers or addresses of the application server application front end; or the subscriber address information is an application server. The identifier or address of the application, and the application front-end address information is an identifier or an address of the HSS application front end.