CN101945375A - Method for selecting application front end and user data warehouse - Google Patents
Method for selecting application front end and user data warehouse Download PDFInfo
- Publication number
- CN101945375A CN101945375A CN200910088683XA CN200910088683A CN101945375A CN 101945375 A CN101945375 A CN 101945375A CN 200910088683X A CN200910088683X A CN 200910088683XA CN 200910088683 A CN200910088683 A CN 200910088683A CN 101945375 A CN101945375 A CN 101945375A
- Authority
- CN
- China
- Prior art keywords
- application front
- user data
- subscription
- address information
- notification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000004048 modification Effects 0.000 description 15
- 238000012986 modification Methods 0.000 description 15
- 230000008569 process Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 7
- 230000008859 change Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 238000013499 data model Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 230000004927 fusion Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007689 inspection Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000007418 data mining Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000035755 proliferation Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a method for selecting an application front end, comprising the following steps: a user data warehouse receives a request message sent by the application front end and stores address information of the application front end in the request message; and while sending a notification message, the user data warehouse selects the stored address information of the application front end as the application front end for sending the notification message. The invention further discloses a user data warehouse. The invention can effectively solve the problem for sending the notification message to an initial subscriber of the message.
Description
Technical Field
The invention relates to a subscription notification technology in a User Data Convergence (UDC) network, in particular to a method for selecting an application front end when a notification message is issued and a User Data warehouse.
Background
With the development of Internet Technology (IT), hardware and software technologies and services, 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 are introduced and become standards, such as the third Generation (3G, 3rd Generation) mobile communication Network, the IP Multimedia Subsystem (IMS) Network, the Worldwide Interoperability for Microwave Access (WiMAX) Network, the soft switching Network, and so on, which results in a large increase of user data in the Network.
With the proliferation of user data in a network, the original user data storage mode and the original user data providing mode are more and more difficult to adapt to the rapid development of the network, and the distributed management of data causes the following problems: the operational Expenditure (OPEX) is increased, the junk data is difficult to eliminate, the data consistency is difficult to guarantee, the data security is difficult to guarantee, and an effective means is lacked in data mining analysis. In addition, the data storage network elements have inconsistent external interfaces, so that the data access interfaces are complex, the interfaces are tightly coupled with the services, the data cannot be transmitted transparently, new services are difficult to develop quickly and effectively, and the problem of user data management is increasingly obvious.
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 are fused, the user identification is used as a basic identification, and the data are organized according to a uniform data structure and are used as the only user data source of all networks. The integration, application and data decoupling are carried out on the terminal data, the access or core network data, the service data and the Internet service data, the unified user data center is managed and established in a unified mode, the network can be simplified, the time for releasing new services is shortened, the service innovation is promoted, and a foundation is laid for competitive service integration provided by operators.
In terms of physical implementation, the unified user data model can be stored in a unique data storage network element of the network: the Central Database (CDB) stores a unified data model of users, so as to ensure consistency, reliability and security of data, provide an open interface independent of business and data, and provide data access service for other data query network elements.
Fig. 1 illustrates a network system model established by the third generation partnership Project (3 GPP) organization in the prior art with respect to user data fusion, and as shown in fig. 1, a UDC network includes a user data repository and an application front-end supporting various applications, wherein the application front-end processes data-independent application logic and is not responsible for storing user data information, and the application front-end supporting different applications is connected to different network entities, such as: an application server, a service support System (BSS) and the like that support or do not support UDC; the user data warehouse is used as a user data center in the network, integrates various application data, and provides a uniform open Ud access interface for various different application front ends.
The UDC network is relatively independent and does not affect the existing network system, i.e.: 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 Server (HSS) Application needs to support a Diameter-based protocol interface supported by the HSS, including an Sh interface with an Application Server (AS), referred to herein AS an HSS Application front end. The UDC network needs to support Provisioning functions, namely: and providing service support for the BSS system, such as user number allocation, user service subscription data modification and the like, wherein the Provisioning application front end is positioned between the BSS and the user data warehouse, executes related service processing, and provides Provisioning function support for the UDC network.
When an operator deploys the UDC network, all application servers related to the UDC network are not upgraded, and the upgraded application servers can embed the function of the application front end and directly provide an access interface with a user data repository, which is referred to as an application server supporting the UDC. The uneupgraded application server has no direct interface with the user data repository, and needs to access the user data repository through the HSS application front end through the original Sh interface, which is referred to herein as an application server that does not support UDC.
The UDC network supports a subscription notification function, and FIG. 2 is a schematic diagram based on subscription relationship establishment under the UDC network. As shown in fig. 2, the user data warehouse presets a notification trigger condition and a notification type, where the notification trigger condition includes a data subscription state and a data change state, and is preset as a data unsubscribe state and a data unchanged state, respectively; the notification type is set as subscription data subscription notification.
An application server supporting user data fusion comprises an application server application front end, and directly sends a Subscription Notification Request message or a data modification Request message carrying a Subscription Notification Request (SNR) identifier to a user data warehouse through a Ud interface to Request for establishing a Subscription Notification relationship. The application server which does not support user data fusion needs to send a subscription notification request message through an existing Sh interface of an HSS application front end, and the HSS application front end sends the subscription notification request message or a data modification request message carrying an SNR (signal to noise ratio) identifier to a user data warehouse through a Ud interface to request for establishing a subscription notification relationship.
After the user data warehouse receives the subscription notification request, establishing a subscription notification relationship, namely: the subscription notification data information of the subscription data is stored, and comprises a subscriber address and subscription data, wherein the subscriber address is an application server identifier or address, or an application server application front-end identifier or address; and setting the data subscription state corresponding to the notification trigger condition as subscribed. The subscription data describes the user subscription data corresponding to the subscription data subscription notification event, and may be a request data identifier or a request data domain name, instead of the specific content of the user subscription data.
Fig. 3 is a schematic diagram of a notification trigger process when service subscription data is modified, and as shown in fig. 3, the notification trigger process includes the following steps:
step S310, BSS sends request message for modifying service subscription data to Provisioning application front end;
step S320, after receiving the request message for modifying the service subscription data from the BSS, the Provisioning application front end sends the request message for modifying the user data to the user data warehouse through a unified Ud interface with the user data warehouse so as to modify the service subscription data stored in the user data warehouse;
step S330, after receiving a request message for modifying user data sent by a Provisioning application front end, the user data warehouse executes access control;
after the Provisioning application front end is effectively authenticated and the request data is effectively authorized, the user data warehouse executes the updating operation of the service subscription data;
step S340, notifying the trigger condition for the user data warehouse inspection, namely: judging whether the request data changes or not, and checking the subscription state 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 is subscribed, triggering a notification process by the user data warehousing; otherwise, the notification process of step S350 and step S360 is not triggered, and the current processing process is ended;
step S350a or S350b, the user data warehouse sends a notification message to the notification event subscriber through the Ud interface, and the notification message carries notification type and notification data information;
the notification type is set as a subscription data subscription notification and is used for indicating an application front end supporting subscription notification application to send subscription notification data to a subscriber;
the application front end supporting the subscription notification application can be an HSS application front end, and sends subscription notification data to an application server through a notification message of an Sh interface; the front end can also be applied to an AS supporting the UDC network;
the notification data information comprises a subscriber address, a user identifier, subscription notification data and the like; the subscription notification data is the latest change content of the data subscribed by the subscription notification event; here, the subscriber address is an application server identifier or address, or an application server application front-end identifier or address; the subscriber Identity is used for uniquely identifying a subscriber 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 warehouse;
step S370, the user data warehouse returns a response message of modifying the user data to the Provisioning application front end;
in step S380, the Provisioning application front end returns the result of the user data modification to the BSS through the service subscription data modification response message.
AS can be seen from the above steps, the initial subscriber of the notification message may be an AS or a specific application front end, e.g. an application server application front end. When the notification message is triggered, the user data repository needs to send the notification message to an initial subscriber of the message, for example, when the initial subscriber is an application server, the user data repository needs to select a suitable HSS application front end, and indirectly forwards the notification message to the application server; when the initial subscriber is a particular application front-end, the user data repository directly selects the application front-end and sends a notification message to the application front-end.
The prior art does not specify a routing mode when the user data warehouse sends the notification message in the application scene. That is, in the UDC network, when a notification message is issued, how to effectively send the notification message to an 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 been proposed at present.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method for selecting an application front end and a user data repository, which can effectively solve the problem of sending a notification message to an initial subscriber of the message.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a method for selecting an application front end, which comprises the following steps:
the user data warehouse receives a request message sent by an application front end and stores the application front end address information in the request message;
when the notification message is issued, the user data warehouse selects the stored address information of the application front end as the application front end for sending the notification message.
The method further comprises the following steps: the user data repository sends notification messages to the selected application front-end.
In the above scheme, the request message is a subscription notification request message based on a Ud interface, or a request message for modifying user data carrying a subscription notification request SNR identifier.
In the above scheme, the request message further includes subscription information; the user data warehouse also stores subscription information in the request message; the subscription information comprises subscriber address information and subscription data.
In the above scheme, the subscriber address information and the application front-end address information are both identifiers or addresses of the application front end of the application server; or, the subscriber address information is an identifier or address of an application server, and the application front-end address information is an identifier or address of an HSS application front end.
In the above scheme, when the user data warehouse stores the application front-end address information, the method further includes: and setting the data subscription state corresponding to the notification trigger condition as subscribed data by the user data warehouse.
The invention also provides a user data warehouse, comprising: the system comprises an information acquisition unit, an information storage unit and an application front end selection unit; wherein,
the information acquisition unit is used for receiving a request message sent by an application front end and acquiring the address information of the application front end carried in the request message;
the information storage unit is used for storing the acquired application front-end address information;
and the application front end selecting unit is used for selecting the application front end according to the stored application front end address information.
In the above scheme, the user data repository further includes a notification message sending unit, configured to send a notification message to the selected application front end.
In the above scheme, the information obtaining unit is further configured to obtain subscription information including subscription address information and subscription data; the information storage unit is also used for storing the address information of the subscriber and the subscription data.
The method for selecting the application front end and the user data warehouse provided by the invention store the address information of the application front end when the subscription notification relationship is established in the user data warehouse, correspondingly, when the notification message is issued, the user data warehouse selects the application front end according to the stored address information of the application front end, and then sends the notification message to the selected application front end. Therefore, the required application front end can be effectively selected, and the notification message is accurately sent to the initial subscriber of the message; moreover, the invention is simple and convenient to realize, does not need to greatly change the original subscription notification machine, and effectively solves the technical problems in the prior art.
Drawings
FIG. 1 is a schematic diagram of a prior art UDC network;
fig. 2 is a schematic diagram illustrating an implementation of subscription notification relationship establishment based on a UDC network in the prior art;
fig. 3 is a schematic diagram of a notification trigger flow based on modification of service subscription data in a UDC network in the prior art;
FIG. 4 is a schematic diagram of an implementation flow of the method for selecting an application front end according to the present invention;
FIG. 5 is a schematic diagram of an implementation flow of establishing a subscription notification relationship in the present invention;
fig. 6 is a schematic diagram of an implementation flow of selecting an application front end when a notification of service subscription data modification is triggered in an embodiment of the present invention.
Detailed Description
The basic idea of the invention is: the user data warehouse stores the address information of the application front end when establishing a subscription notification relationship; correspondingly, when the notification message is issued, the user data warehouse selects the application front end according to the stored address information of the application front end.
Further, the user data repository sends a notification message to the selected application front-end.
Here, the user data repository also stores subscription information including subscriber address information and subscription data when establishing a subscription notification relationship.
The subscription data is used for describing user subscription data corresponding to a subscription data subscription notification event, and comprises a request data identifier or a request data domain name; the subscriber address information is used for describing an initial subscriber who subscribes to the notification message, and is a subscriber identifier or a subscriber address, specifically, the subscriber address information is an identifier or an address of an AS, or an identifier or an address of an application front end of the AS; the subscriber identity is a host name, or a host name and a domain name of the subscriber. The application front end address information is an AS application front end identifier or address or an HSS application front end identifier or address; the application front end identifier is a host name, or a host name and a domain name of the application front end.
The method for selecting the application front end of the present invention is shown in fig. 4, and comprises the following steps:
step 401: the user data warehouse receives a request message sent by an application front end and stores the application front end address information in the request message;
here, the request message is a subscription notification request message based on a Ud interface, or a request message carrying SNR identification for modifying user data; the request message carries application front-end address information;
the request message also carries subscription information including subscriber address information and subscription data, and correspondingly, the subscriber address information and the subscription data are also stored in the user data warehouse.
For an application server supporting a UDC network, the address information of an application front end is an identifier or an address of an AS application front end, and the address information of a subscriber is also the identifier or the address of the AS application front end; for an application server which does not support the UDC network, the address information of the application front end is the identifier or the address of the HSS application front end, and the address information of the subscriber is the identifier or the address of the application server.
Step 402: when the user data warehouse issues the notification message, selecting the stored application front-end address information as an application front end for sending the notification message; namely: selecting an application front end corresponding to the stored application front end address information as an application front end for sending a notification message;
the notification message includes subscriber address information and subscription data, and the combination of the subscriber address information and the subscription data is called subscription information.
Further, the user data repository sends notification messages to the selected application front-end.
The following describes in detail the implementation process of establishing a subscription notification relationship and selecting an application front-end method according to the present invention with reference to the accompanying drawings and specific embodiments.
Fig. 5 is a schematic view of an implementation flow of establishing a subscription notification relationship in the present invention, and as shown in fig. 5, the establishment of the subscription notification relationship in the present invention includes the following steps:
step S510, the AS application front end/HSS application front end sends subscription signing notification request information based on the Ud interface or user data modification request information carrying SNR identification to the user data warehouse;
here, for the application server supporting the UDC network, a subscription notification request message based on the Ud interface or a modification data request message carrying an SNR identifier is sent to the user data repository through the AS application front end; for an application server which does not support the UDC network, a subscription and subscription notification request message based on an Sh interface needs to be sent to an HSS application front end, and after being processed by the HSS application front end, the subscription and subscription notification request message based on a Ud interface or a data modification request message carrying an SNR (signal to noise ratio) identifier needs to be sent to a user data warehouse.
The request message carries address information of a subscriber and address information of an application front end; for an application server supporting a UDC network, both the subscriber address information and the application front-end address information refer to the identifier or the address of the application front end of the application server; for an application server which does not support the UDC network, the subscriber address information refers to an identifier or address of the application server, and the application front-end address information refers to an identifier or address of the HSS application front-end.
Step S520, the user data warehouse receives the subscription signing notification request message or the data modification request message carrying the SNR mark, executes access control, and performs authentication and authorization processing; after the AS application front end or the HSS application front end is effectively authenticated and the request data is effectively authorized, the user data warehousing executes step S530;
step S530, storing subscription information and application front-end address information in a user data warehouse;
the subscription information comprises subscriber address information and subscription data; the subscription data is used for describing user subscription data corresponding to the subscription data subscription notification event, and may be a request data identifier or a request data domain name.
Further, the user data warehouse may set the data subscription state corresponding to the notification trigger condition as subscribed. Here, the subscribed state is set to facilitate smooth completion of the subsequent process, and as to what the notification trigger condition may be, how to set the notification trigger condition is not relevant to the present invention, and is the prior art, and is not described in detail herein.
Step S540, the user data repository returns a subscription notification response message or a user data modification response message based on the Ud interface to the AS application front end or the HSS application front end.
Fig. 6 is a schematic diagram of an implementation flow of selecting an application front end when a notification of service subscription data modification is triggered in an embodiment of the present invention, and as shown in fig. 6, the implementation flow of selecting the application front end to apply to a service subscription data modification notification flow includes the following steps:
steps S610 to S630, which are the same as the processing procedures of steps S310 to S330 in fig. 3;
step S640, notifying a trigger condition by user data warehousing inspection, and checking the subscription state of the request data;
here, the notification trigger condition is to determine whether the request data has changed, that is: judging whether the service subscription data changes;
if the requested data changes and the change notification event of the requested data is subscribed, the user data warehousing triggers a notification process and continues to execute step S650; otherwise, the notification process is not triggered, skipping the steps S650, S660a, S670a, or skipping the steps S650, S660b, S670b, and directly executing the step S680;
step S650, the user data warehouse selects the application front end according to the application front end address information stored by the user data warehouse, namely: directly selecting a stored application front end;
specifically, if the application front end address information is the HSS application front end, step S660a and step S670a are executed; if the application front end address information is the AS application front end, executing step S660b and step S670 b;
step S660 a-S670 a, the user data warehouse sends a notification message based on the Ud interface to the selected HSS application front end, and the notification flow is the same as the processing of step S350 a-S360 a in fig. 3;
step S660 b-S670 b, the user data warehouse sends a notification message based on the Ud interface to the selected AS application front end, and the notification flow is the same AS the processing of step S350 b-S360 b in fig. 3;
the flow of steps S680 to S690 is the same as the processing of steps S370 to S380 in fig. 3.
In order to realize the method, the invention also provides a user data warehouse, which comprises an information acquisition unit, an information storage unit and an application front-end selection unit; wherein,
the information acquisition unit is used for receiving a request message sent by an application front end and acquiring the address information of the application front end carried in the request message;
for an application server supporting a UDC network, the subscriber address information and the application front-end address information both refer to an identifier or an address of an application front end of the application server; for an application server which does not support a UDC network, the subscriber address information refers to an identifier or an address of the application server, and the application front-end address information refers to an identifier or an address of an HSS application front end;
further, the information obtaining unit is further configured to obtain subscription information that includes subscription address information and subscription data.
The information storage unit is used for storing the acquired application front-end address information;
further, the information storage unit is also used for storing the subscriber address information and the subscription data.
And the application front end selecting unit is used for selecting the application front end according to the stored application front end address information.
The user data repository may further comprise a notification message sending unit for sending notification messages to the selected application front-end.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.
Claims (10)
1. A method for selecting an application front-end, the method comprising:
the user data warehouse receives a request message sent by an application front end and stores the application front end address information in the request message;
when the notification message is issued, the user data warehouse selects the stored address information of the application front end as the application front end for sending the notification message.
2. The method of claim 1, further comprising: the user data repository sends notification messages to the selected application front-end.
3. The method according to claim 1 or 2, wherein the request message is a subscription notification request message based on a Ud interface or a modified user data request message carrying a subscription notification request SNR identification.
4. The method according to claim 1 or 2, wherein the request message further comprises subscription information; the user data warehouse also stores subscription information in the request message;
the subscription information comprises subscriber address information and subscription data.
5. The method of claim 4, wherein the subscriber address information and the application front-end address information are both an identifier or an address of an application server application front-end; or, the subscriber address information is an identifier or address of an application server, and the application front-end address information is an identifier or address of an HSS application front end.
6. The method of claim 4, wherein when the user data repository stores application front-end address information, the method further comprises: and setting the data subscription state corresponding to the notification trigger condition as subscribed data by the user data warehouse.
7. A user data warehouse, comprising: the system comprises an information acquisition unit, an information storage unit and an application front end selection unit; wherein,
the information acquisition unit is used for receiving a request message sent by an application front end and acquiring the address information of the application front end carried in the request message;
the information storage unit is used for storing the acquired application front-end address information;
and the application front end selecting unit is used for selecting the application front end according to the stored application front end address information.
8. The user data repository according to claim 7, wherein the user data repository further comprises a notification message sending unit for sending notification messages to the selected application front-end.
9. The user data repository according to claim 7 or 8, wherein the information obtaining unit is further configured to obtain subscription information including subscription address information and subscription data;
the information storage unit is also used for storing the address information of the subscriber and the subscription data.
10. The user data repository of claim 9, wherein the subscriber address information and the application front-end address information are both an identification or an address of an application server application front-end; or, the subscriber address information is an identifier or address of an application server, and the application front-end address information is an identifier or address of an HSS application front end.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910088683XA CN101945375A (en) | 2009-07-07 | 2009-07-07 | Method for selecting application front end and user data warehouse |
| PCT/CN2010/074419 WO2011003330A1 (en) | 2009-07-07 | 2010-06-24 | Method for selecting application front-end and user data storage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910088683XA CN101945375A (en) | 2009-07-07 | 2009-07-07 | Method for selecting application front end and user data warehouse |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101945375A true CN101945375A (en) | 2011-01-12 |
Family
ID=43428779
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910088683XA Pending CN101945375A (en) | 2009-07-07 | 2009-07-07 | Method for selecting application front end and user data warehouse |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101945375A (en) |
| WO (1) | WO2011003330A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020118633A1 (en) * | 2018-12-13 | 2020-06-18 | Oppo广东移动通信有限公司 | Subscription message processing method and apparatus, and computer device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651063B1 (en) * | 2000-01-28 | 2003-11-18 | Andrei G. Vorobiev | Data organization and management system and method |
| CN1866833A (en) * | 2005-12-22 | 2006-11-22 | 华为技术有限公司 | Distributed data management system and its method for dynamically subscribing data |
| CN101127613A (en) * | 2006-08-16 | 2008-02-20 | 华为技术有限公司 | Method for obtaining circuit domain information in IP multimedia subsystem and its application |
| CN101415180A (en) * | 2008-11-28 | 2009-04-22 | 华为技术有限公司 | Method, apparatus and communication system for sending user data |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101069402B (en) * | 2004-10-26 | 2010-11-03 | 意大利电信股份公司 | Method and system for transparently authenticating a mobile user to access web services |
| CN100407812C (en) * | 2005-12-20 | 2008-07-30 | 华为技术有限公司 | Method for realizing multi-media broadcasting business in residence area |
-
2009
- 2009-07-07 CN CN200910088683XA patent/CN101945375A/en active Pending
-
2010
- 2010-06-24 WO PCT/CN2010/074419 patent/WO2011003330A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651063B1 (en) * | 2000-01-28 | 2003-11-18 | Andrei G. Vorobiev | Data organization and management system and method |
| CN1866833A (en) * | 2005-12-22 | 2006-11-22 | 华为技术有限公司 | Distributed data management system and its method for dynamically subscribing data |
| CN101127613A (en) * | 2006-08-16 | 2008-02-20 | 华为技术有限公司 | Method for obtaining circuit domain information in IP multimedia subsystem and its application |
| CN101415180A (en) * | 2008-11-28 | 2009-04-22 | 华为技术有限公司 | Method, apparatus and communication system for sending user data |
Non-Patent Citations (2)
| Title |
|---|
| 3GPP: "《3GPP TS 23.335,V0.1.0,User Data Convergence Technical Realization and Information Flows Stage 2 (Release 9)》", 13 May 2009, 3GPP * |
| NOKIA SIEMENS NETWORKS: "《3GPP TSG CT WG4 Meeting #44,C4-091758,Pseudo-CR on Subscription information flow》", 26 June 2009, 3GPP * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020118633A1 (en) * | 2018-12-13 | 2020-06-18 | Oppo广东移动通信有限公司 | Subscription message processing method and apparatus, and computer device and storage medium |
| US11991779B2 (en) | 2018-12-13 | 2024-05-21 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Subscription message processing method and apparatus, and computer device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2011003330A1 (en) | 2011-01-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2442597B1 (en) | User data convergence network system and method for subcription to a notification | |
| US9615346B2 (en) | Method and apparatus for notifying information change in wireless communication system | |
| EP2432154B1 (en) | Method, terminal, apparatus, and system for device management | |
| US9686230B2 (en) | Management of application server-related user data | |
| US20150365415A1 (en) | Method, system and apparatus for handling terminal capabilities | |
| US20130083761A1 (en) | Indicating radio bearer information to network applications | |
| CN102474523B (en) | Methods and apparatuses for initiating provisioning of subscriber data in a hss of an IP multimedia subsystem network | |
| US20080195535A1 (en) | Method for Flexibly Configuring Charging Modes in Ims Systems | |
| US8621572B2 (en) | Method, apparatus and system for updating authentication, authorization and accounting session | |
| KR20080094826A (en) | Representing network availability status information in presence information | |
| US20110173687A1 (en) | Methods and Arrangements for an Internet Multimedia Subsystem (IMS) | |
| US20190053295A1 (en) | Methods and Devices for Supporting Network Initiated PDU Session Establishment between an User Equipment, UE, and a Data Network Name, DNN, in a Telecommunication Network | |
| KR20110131995A (en) | Server and method for providing device management service and device to be provided the service | |
| CN114667751A (en) | Method for supporting authentication of user equipment | |
| CN101931939B (en) | Method and device for selecting application front end and user data warehouse | |
| WO2012130048A1 (en) | Method and apparatus for initializing gateway in device management system | |
| US9374710B2 (en) | Mediation server, control method therefor, communication device, control method therefor, communication system, and computer program | |
| CN102449955B (en) | Method, apparatus and system for controlling behaviors of machine type communication MTC terminals | |
| EP2656573B1 (en) | Remote provisioning of a downloadable identity module into one of several trusted environments | |
| EP2532143B1 (en) | Method and apparatus for routing xcap requests | |
| CN101945375A (en) | Method for selecting application front end and user data warehouse | |
| US20120275358A1 (en) | System, apparatus and method for updating communication services | |
| CN105306238A (en) | Terminal access method, terminal access device and terminal access system | |
| EP3669607A1 (en) | Methods and devices for supporting network initiated pdu session establishment between an user equipment, ue, and a data network name, dnn, in a telecommunication network. | |
| Bhadrapur | HSS Front-End implementation for a large scale common HLR/HSS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110112 |