CN101800759B

CN101800759B - Invitation subscription realization system and method

Info

Publication number: CN101800759B
Application number: CN 200910077652
Authority: CN
Inventors: 邵伟翔; 糜正琨; 徐名海; 彭荣群
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2009-02-10
Filing date: 2009-02-10
Publication date: 2013-08-07
Anticipated expiration: 2029-02-10
Also published as: CN101800759A

Abstract

The invention discloses an invitation subscription realization system, which comprises a client, a server, an extensible markup language document management (XDM) server, wherein the server comprises an invitation subscription realization module used for realizing the invitation subscription, wherein the server is used for receiving an invitation subscription request, and the invitation subscription request is transferred to the XDM server through the invitation subscription realization module. The invention also discloses an invitation subscription realization method, which comprises the following steps that: users initiate the invitation subscription request through the client; the invitation subscription realization module of the server receives the invitation subscription request and sends the invitation subscription request to the XDM server; the XDM server generates an invited notification message and sends the invited notification message to clients of other users; the clients of other users send an invitation accepting message to the invitation subscription realization module; the invitation subscription realization module generates a subscription request; and the XDM server generates the subscription relationship. The system and the method of the invention can be adopted for realizing the invitation subscription.

Description

System and method for realizing invitation subscription

Technical Field

The present invention relates to a technology for implementing subscription invitation, and in particular, to a system and a method for implementing subscription invitation in a Converged Address Book (CAB) system.

Background

With the evolution of telecommunication networks towards Internet Protocol (IP) networks, new services for flexible communication, such as peer-to-peer communication and group communication, have emerged. Each service typically requires an address book to support, which exposes the user to the trouble of handling multiple address books on multiple terminals simultaneously. And since each terminal stores data independently, when a certain terminal is lost or malfunctions, the lost address book information is difficult to recover. In order to adapt to a new communication environment and improve user experience, a fused address book needs to be provided for a user to use, and a CAB system needs to be developed.

The CAB system provides the mechanisms: the CAB system can allow a user to conveniently manage address book information on a local terminal and also can allow a user to conveniently manage address book information stored on a network. The core of the CAB system is an address book information storage located on the network side. The address book information memory is not only convenient for the user to access and manage, but also keeps the data updating synchronization with various terminals all the time, and when the address book information stored at the network side changes, the CAB system also needs to synchronously update the changed data to each terminal of the user in time.

The CAB system also provides a mechanism for managing Personal Contact Card (PCC) information by a user. The user can store all his own contact information in the PCC on the network, the contact information including his own MSN/QQ number, cell phone number, email, etc. The CAB user who issues PCC information may provide a subset of its PCC to other CAB users by defining a contact view. Here, for the mode of the contact view, in brief, since the PCC includes all the contact information, when the CAB user who issues the PCC information issues information to other CAB users, it is usually necessary to customize different contact information in the PCC of the CAB user according to different needs of the CAB user and other CAB users, and present the customized contact information to other CAB users, so as to improve user experience of other CAB users. And the presentation of different contact information is realized by defining the contact view, and the manner of defining the contact view is equivalent to that of: and after all the contact information in the CAB user releasing the PCC information is selected and filtered according to needs, the contact information is presented to other CAB users according to needs so as to meet different needs of other CAB users.

Moreover, when the contact information in the PCC changes, the CAB user issuing the PCC information can also inform the CAB user receiving the PCC information through a subscription notification mechanism, so that the CAB user receiving the PCC information can obtain the update notification of the PCC information in time, and the problem that the original PCC information is invalid is effectively solved. It should be noted here that the CAB user actually issuing the PCC information is the inviting user, and the CAB user receiving the PCC information is the invited user. If the inviting user is represented by user a and the invited user is represented by user B, the process of inviting subscription is: user a invites user B to subscribe to the PCC information of user a itself. When the PCC information of the user A is updated, the user B is further informed to synchronously update the originally subscribed PCC information through a subscription notification mechanism. Since the PCC information of user a is subscribed to user B, user a may also be referred to as a subscribed user, and user B may also be referred to as a subscribing user.

The CAB system also provides the functions of searching, sharing and subscribing the CAB/PCC data within the domain or between domains by authorized users, and the function of interworking with conventional address book systems, such as vCard and other systems.

The Open Mobile Alliance (OMA) is making the CAB V1.0 specification. The requirements for the subscription function in CAB systems are: the CAB user is allowed to invite other CAB users to subscribe to PCC information of the CAB user according to the policy of the service provider, however, no specific implementation scheme for this requirement exists at present.

Disclosure of Invention

In view of the above, the main objective of the present invention is to provide a system and a method for implementing subscription invitation, which can meet the requirement of the CAB system for the subscription function and implement subscription invitation.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

an invitation subscription implementing system, the system comprising: client, server, XML document management XDM server; the server comprises an invitation subscription realizing module for realizing invitation subscription; wherein,

the client is used for sending an invitation subscription request initiated by a user to the server;

a server, configured to receive the invitation subscription request from the client, and forward the invitation subscription request to the XDM server by the invitation subscription implementing module; the client sides of other users send the invitation accepting message to the invitation subscription realizing module, and the invitation subscription realizing module generates a subscription request;

the XDM server is used for receiving the invitation subscription request from the invitation subscription realization module, generating an invited notification message and sending the invited notification message to the client sides of other users; and the XDM server receives the subscription request and generates a subscription relation.

The server also comprises a subscription realization module used for sending a subscription request;

the invitation subscription realizing module is further used for sending the subscription request to the subscription realizing module and transmitting the subscription request by the subscription realizing module; the XDM server is further configured to receive a subscription request from the subscription implementing module and generate a subscription relationship.

An implementation method for inviting subscription, the method comprising:

a user initiates a subscription invitation request through a client;

an invitation subscription realizing module of the server receives the invitation subscription request from the client and sends the request to the XDM server;

the XDM server generates an invited notification message and issues the invited notification message to the client of other users;

the other users accept the invitation, the client of the other users sends the invitation accepting message to the invitation subscription realizing module, the invitation subscription realizing module generates a subscription request, and the XDM server receives the subscription request and generates a subscription relationship.

Before the sending the invitation subscription request to the XDM server, the invitation subscription implementing module of the server further includes: after authentication of a network interface module of a network intercommunication proxy module/an initial session protocol SIP internet protocol IP core network of the server, the network intercommunication proxy module/the SIP IP core network interface module forwards the invitation subscription request to the invitation subscription realizing module; or,

and after passing the authentication of the server, the invitation subscription realizing module receives the invitation subscription request.

The method for generating the invited notification message and issuing the invited notification message to the client of the other user by the XDM server specifically comprises the following steps:

the PCC XDM service module of the personal contact card of the XDM server inquires the condition of the other user terminal and generates an invited notification message; the client issued to other users specifically comprises: and the network interworking agent module/SIP IP core network interface module of the server forwards the invited notification message to the client of other users or directly sends the invited notification message to the client of other users.

The method comprises the following steps that the other users accept the invitation, the invitation subscription realizing module generates a subscription request, and the XDM server generates a subscription relation specifically as follows:

the client of the other user forwards the message of accepting the invitation to the invitation subscription realizing module by the network intercommunication proxy module/SIP IP core network interface module of the server or directly sends the message to the invitation subscription realizing module;

inviting a subscription realizing module to generate a subscription request and sending the subscription request to the subscription realizing module, wherein the subscription realizing module sends the subscription request to a PCC XDM service module of the XDM server;

and the PCC XDM service module generates subscription relations between the users and other users according to the user preferences, the policies and the relevant contact views.

Wherein, the authentication mechanism of the authentication comprises: internet key exchange second version IKEv2, internet protocol encryption IPSec, digest authentication mechanism HTTP digest, generic authentication architecture, IP multimedia subsystem authentication, or transport layer security mechanism.

Wherein, the method also comprises: the invitation subscription realizing module broadcasts the invitation reservation in a multicast mode, and obtains the data of the broadcast invitation group user by accessing the shared group XDM server.

Wherein, after the generating the subscription relationship, the method further comprises:

and the PCC XDM service module inquires corresponding subscription information in PCC information of the user aiming at the subscription request, and sends the subscription information to other users according to the subscription relation.

The sending of the subscription information to other users according to the subscription relationship is specifically: the PCCXDM service module sends an announcement message containing initial subscribed information or updated subscribed information to a subscription realization module according to the subscription relationship between the user and other users; and the information is sent to the client sides of other users after the aggregation processing of the subscription realization module.

The sending of the subscription information to other users according to the subscription relationship is specifically: the PCCXDM service module sends initial subscribed information or updated subscribed information to an address book XDM service module according to the subscription relation between the user and other users; the address book XDM service module synchronizes the initial subscribed information or the updated subscribed information to the clients of other users with a synchronization mechanism.

In the CAB system architecture added with the invitation subscription realizing module, the invitation subscription realizing module can receive an invitation subscription request, namely a subscribed request, sent by an inviting user, wherein the inviting user is a user who wants to publish the PCC information of the user; the invitation subscription realizing module responds to the invitation subscription request and executes the invitation operation of the background, and sends notification information to the invited users one by one, wherein the invited users are users receiving PCC information; if the invitation is successful, setting the corresponding relation between the inviting user and the invited user, and maintaining a binding relation table and subscription state information. The subscription operation of the invited user is transferred to be processed by the subscription realizing module.

The invention provides a solution for the requirement of the CAB system on the subscription function, and the adoption of the invention can realize the subscription invitation and better meet the requirement of the CAB system.

Drawings

FIG. 1 is a schematic diagram of the structure of the system of the present invention;

FIG. 2 is a schematic diagram of an exemplary embodiment of a system according to the present invention;

FIG. 3 is a schematic flow chart of the implementation of the method of the present invention;

FIG. 4 is a message flow diagram illustrating an exemplary implementation of an invite subscription;

FIG. 5 is a message flow diagram illustrating an exemplary implementation of an invite subscription;

FIG. 6 is a message flow diagram of a subscription announcement for an invitation subscription according to an embodiment of the invention;

fig. 7 is a message flow diagram of a subscription announcement implementing an invitation subscription according to another embodiment of the invention.

Detailed Description

The basic idea of the invention is: a user initiates a subscription invitation request through a client; an invitation subscription realizing module of the server sends an invitation subscription request to the XDM server; the XDM server generates an invited notification message and issues the invited notification message to the client of other users; other users accept the invitation, invite the subscription realizing module to generate a subscription request, and the XDM server receives the subscription request and generates a subscription relationship.

The following describes the embodiments in further detail with reference to the accompanying drawings.

The technical principles involved in the various information storage management in the CAB system of the present invention are briefly described below.

Various information in CAB systems include: PCC information as well as other information such as address book information, etc. This information is stored on the network in the form of documents in extensible markup language and requires that this information be located, accessed and managed. Management includes creating, changing, and deleting such information, and the like. The OMA organization determines to reuse an extensible markup language document management (XDM, XML document management) server to manage these extensible markup language (XML) documents. Reuse, i.e. reuse of the defined specifications. Furthermore, the XDM architecture document, AD-XDM, describes the architecture and characteristics of the XDM engine (Enabler) of OMA, while the XDM Core specification, XDM _ Core, defines a common protocol that authorizes users to access and manage these documents.

XDM Enabler defines a generic mechanism that enables service Enabler to access user service-related information. This information is stored on the network and can be located, accessed and managed. The XDM specification specifies how this information is defined in well-structured XML documents, and the general protocols that access and manage these XML documents.

The various features of XDM Enabler are defined in the XDM core specification, the first aspect relates to the XML Configuration and Access Protocol (XCAP). In particular, the XDM specification reuses the XCAP protocol, by which participating agents can use the hypertext transfer protocol (HTTP) to acquire, assign, and delete methods to store and manage service-related information stored on a network in the form of XML documents. A second aspect relates to an initial session protocol (SIP) subscription/notification mechanism. In particular, the XDM specification reuses the SIP event package mechanism defined by the Internet Engineering Task Force (IETF), by which subjects can be notified of changes to these files. A third aspect relates to a search mechanism. In particular, with this mechanism, the body can search for business-related information stored on the network in the form of an XML document using the limited XQuery expression using the HTTP post method.

XML documents accessed and managed through XCAP are stored in logical repositories called XDM servers on the network, each associated with a functional entity implementing a respective function. Each XML document stored in the XDM server is described as an XCAP application method, by which an application can use the documents through XCAP. XDM Enabler describes those application methods that can be reused by multiple enablers and stored in a shared XDM server, and there are four types, respectively: a shared list XDM server, a shared group XDM server, a shared policy XDM server, and a shared summary XDM server. Document types supported by these different types of XDM servers include: a URI list and a group method list document in a shared list XDM server; sharing a group document in a group XDM server; sharing a user access policy document in a policy XDM server; user profile in a shared profile XDM server. In addition to the four types of documents described above, the XDM Enabler also defines extended multicast documents.

The following describes the implementation of the present invention.

As shown in fig. 1, an implementation system for inviting subscriptions includes: client, server, XDM server; the server comprises an invitation subscription realizing module for realizing invitation subscription, and the invitation subscription realizing module is used for forwarding an invitation subscription request to the XDM server and generating a subscription request of a background. Here, the invitation subscription implementing module may be an invitation subscription agent module, a broadcast agent module, or an advertisement agent module.

The client is used for inviting the user to initiate an invitation subscription request through the client and sending the invitation subscription request initiated by the user to the server. The server is used for receiving the invitation subscription request from the client and forwarding the invitation subscription request to the XDM server by the invitation subscription realizing module; the client of other users sends the invitation accepting message to the invitation subscription realizing module, and the invitation subscription realizing module generates a subscription request. The XDM server is used for receiving the invitation subscription request from the invitation subscription realization module, generating an invited notification message and issuing the invited notification message to the client sides of other users; the XDM server receives the subscription request and generates a subscription relationship.

The server also comprises a subscription realizing module, an invitation subscription realizing module and a subscription realizing module, wherein the subscription realizing module is used for sending a subscription request, and further used for sending the subscription request to the subscription realizing module in the server and transmitting the subscription request by the subscription realizing module; the XDM server is further configured to receive a subscription request from the subscription implementing module and generate a subscription relationship. Here, the subscription implementing module may be a subscription agent module, and may also be a contact subscription function module.

Here, the interface form adopted between the invitation subscription implementing module and the client, the server and the XDM server is: at least one interface form of XDM-1SIP, XCAP, HTTP or XDM-10 SIP.

Here, the client is specifically a user terminal of the inviting user, and the other user clients are specifically user terminals of the invited user. Whether a client of a user or a terminal of a user, may include a CAB client; the CAB client includes: at least one type of an XDM client, a Data Synchronization (DS) client, or an Internet (WEB) client. Moreover, the CAB client is located on the user terminal, and is specifically implemented on the user terminal.

Here, the server further includes, in addition to the subscription implementing module: at least one module of a subscription realizing module, an aggregation proxy module, a search proxy module, a DS server function module, a sharing service module or a communication interface module; the subscription realizing module comprises: a subscription agent module or a contact subscription function module; the communication interface module includes: a network interworking agent module or a SIP IP core network interface module. The server includes: at least one of a CAB server or a contact control server.

Here, the XDM server further includes: at least one of an address book XDM service module, a PCC XDM service module, a CAB user preference setting XDM service module, a CAB user policy XDM service module, or a contact view management XDM service module. The XDM server includes: at least one type of CAB XDM server and OMA shared XDM server.

Fig. 2 is a schematic diagram illustrating a configuration structure of an example of the system of the present invention, in this example, the client is specifically a CAB client, the server is specifically a CAB server, the subscription implementing module is specifically a subscription broker module, the subscription inviting implementing module is specifically an invitation subscription broker module, and the XDM server specifically includes an address book XDM service module and a PCC XDM service module.

In summary, that is to say, the functional module of the invitation subscription implementing module may be a component or a functional module of any network element or device in the server. The server may be a CAB server or a contact control server. The invite subscription implementation module may work with other network elements or devices in existing CAB systems, including but not limited to: CAB client/CAB terminal/XDM client/DS client/WEB client, CAB server/contact control server, XDM server/CAB XDMs server/OMA shared XDM server, address book XDM server, PCC XDM server, CAB user preference setting XDM server, CAB user policy XDM server, subscription agent module/contact subscription function module, aggregation agent module, search agent module, interworking agent module/SIP IP core network interface module, DS server, shared server, etc.

It should be noted that, when the invitation subscription implementing module and other network elements or devices in the existing CAB system work together, the adopted interface form is: at least one interface form of XDM-1SIP, XCAP, HTTP or XDM-10 SIP. For example, the CAB client may send an invite subscription request to the invite subscription implementing module through XDM-1SIP to request that PCC information of the CAB client is subscribed by other CAB clients; the CAB client can send an invitation subscription request to an invitation subscription implementation module through the XCAP so as to request that PCC information of the CAB client is subscribed by other CAB clients; the CAB client can access the CAB server by carrying the invitation list through HTTP, and then the CAB server internally forwards an invitation subscription request to the invitation subscription implementation module so as to request the PCC information of the CAB client to be subscribed by other CAB clients; the CAB client can also access the invitation subscription realization module through the network interworking agent module/SIP IP core network interface module based on the combination of the XDM-1SIP and the XDM-10 SIP.

It should be noted that, the above-mentioned service modules may be in the form of servers. For example, the PCC XDM service module may be a PCC XDM server.

As shown in fig. 3, an implementation method of invitation subscription includes the following steps:

step 101, a user initiates an invitation subscription request through a client.

Here, the client is specifically a client that invites the user.

Step 102, the invitation subscription implementing module of the server receives an invitation subscription request from the client and sends the request to the XDM server.

Here, the invitation subscription implementing module may be an invitation subscription agent module, a broadcast agent module, or an advertisement agent module.

Step 103, the XDM server generates an invited notification message and sends the invited notification message to the clients of other users.

Here, the client of the other user is specifically the client of the invited user.

Step 104, the other users accept the invitation, the client of the other users sends the invitation accepting message to the invitation subscription realizing module, the invitation subscription realizing module generates a subscription request, and the XDM server receives the subscription request and generates a subscription relationship.

An implementation method for inviting subscription, the method further comprises: the invitation subscription realizing module broadcasts the invitation reservation in a multicast mode, and obtains the data of the broadcast invitation group user by accessing the shared group XDM server.

Here, for step 102, step 102 also includes an authentication and authorization process before. Specifically, one case is: after authentication of the network intercommunication proxy module/SIP IP core network interface module of the server, the network intercommunication proxy module/SIP IP core network interface module forwards the invitation subscription request to the invitation subscription realizing module. Or the other case is: after passing the authentication of the server itself, the invitation subscription realizing module directly receives an invitation subscription request from the user client. It should be noted that the authentication mechanism of authentication includes: internet key exchange second edition (IKEv2), internet protocol encryption (IPSec), digest authentication mechanism (HTTP digest), generic authentication architecture, IP multimedia subsystem authentication, or transport layer security mechanism.

For step 103, the specific processing procedure of step 103 is: the network interworking agent module/SIP IP core network interface module of the server forwards the invited notification message to the client of other users, or directly sends the invited notification message to the client of other users.

For step 104, the specific processing procedure of step 104 is:

in step 1041, the client of other user will accept the message of invitation, and the network intercommunication proxy module/SIP IP core network interface module of server will forward it to the invitation subscription implementing module, or send the message of accepting invitation directly to the invitation subscription implementing module.

Step 1042, inviting the subscription implementing module to generate a subscription request and sending it to the subscription implementing module, which sends the subscription request to the PCC XDM service module of the XDM server.

Step 1043, the PCC XDM service module generates a subscription relationship between the user and other users according to the preferences, policies and related contact views of the inviting user.

It should be noted here that, in the subscription invitation process, the PCC XDM service module may cooperate with a user preference XDM service module, a user policy XDM service module, a contact view management XDM service module, and the like, so that the PCC XDM service module may generate a subscription relationship according to the user preference, the policy, and the related contact view. After the invitation subscription process is executed and the subscription relationship between the user and other users is generated, the method also comprises a notification process of subscribed information. The notification process of the subscribed information is as follows: and the PCC XDM service module inquires corresponding subscribed information in PCC information of the user terminal aiming at the subscription request, and sends the subscribed information to other users according to the subscription relation between the users and other users.

Here, the specific implementation of the notification process of the subscribed information includes two cases. One situation is: the PCCXDM service module sends a notification message containing initial subscribed information or updated subscribed information to a subscription realization module according to the subscription relationship between the user terminal and other user terminals; and after the aggregation processing of the subscription realization module, the data are sent to the clients of other users. The other situation is that: the PCC XDM service module sends the initial subscribed information or the updated subscribed information to the address book XDM service module according to the subscription relation between the user and other users; the address book XDM service module synchronizes the initial subscribed information or the updated subscribed information to the clients of other users with a synchronization mechanism.

The following implementation of the inventive method example relates to functional entities such as CAB client, CAB server/contact control server, XDM server, etc. and their corresponding interfaces. The following method examples all use SIP and XCAP protocols as protocol interfaces between CAB client, CAB server/contact control server, and XDM server. The CAB client comprises a CAB client of an inviting user A and a CAB client of an invited user B. The CAB server/contact control server comprises a communication interface module, a subscription realization module and an invitation subscription realization module. The following method examples all employ CAB servers. Moreover, the communication interface module can be a network intercommunication proxy module or a network interface module of an SIP IP core network, and the following method examples all adopt the network intercommunication proxy module; the subscription realizing module can be a contact subscription function module or a subscription agent module, and the following method examples all adopt the subscription agent module; the invitation subscription implementing module can be an invitation subscription agent module, a broadcast agent module or an advertisement agent module, and the following method examples all adopt the invitation subscription agent module. The XDM server includes an XDM service module stored with related address information, and the XDM service module stored with related address information may be a CAB XDM service module or an address book XDM service module. The XDM server further includes an XDM service module for storing personal information about the invited user, and the XDM service module for storing personal information about the invited user may include a PCC XDM service module, a contact view management XDM service module, a CAB user preference setting XDM service module, or a CAB user policy XDM service module. The following method example employs the PCC XDM service module shown only.

The first method example is as follows: the process of implementing the invitation subscription of the invitation subscription agent can also be understood as the process of the invitation subscription. In the example of the method, the CAB server needs to be authenticated by a network intercommunication proxy module or an SIP IP core network interface module to ensure that the invited user is a legal and authorized CAB user, so that the system security is improved. Then, the network intercommunication agent module or the SIP IP core network interface module forwards the invitation subscription request of the inviting user to the invitation subscription agent module for subsequent processing.

That is to say, on the one hand, the request that the inviting user wants the personal contact view, that is, the PCC information of the inviting user is subscribed, is initiated from the CAB client, and the inviting subscription request is transmitted to the inviting subscription agent module after the authentication of the network interworking agent module/SIP IP core network interface module of the CAB server. The inviting subscription agent module informs all invited users of the inviting subscription request, and after the invited users respond, the binding relationship between the inviting users and the invited users can be established. On the other hand, the invited user subscribes the PCC information of the invited user according to the information in the invitation subscription request notice through the subscription agent module, so that the subsequent subscription process is carried out.

As shown in fig. 4, a message flow diagram related to the present embodiment is shown, and a method flow for implementing an invitation subscription of an invitation subscription agent of the present embodiment includes the following steps:

step 201, inviting the CAB client and CAB server of the user a to establish bidirectional authentication, which includes a complete authentication process.

Step 202, the inviting user a initiates an invite subscription request to the network interworking agent module of the CAB server through the CAB client of the inviting user a.

Step 203, the network interworking agent module of the CAB server forwards the invitation subscription request to the invitation subscription agent module.

Step 204, the invite subscription broker module forwards the invite subscription request to the PCC XDM service module of the inviting user a in the XDM server.

Step 205, the PCC XDM service module queries the terminal condition owned by the invited user B, and generates an invited notification message.

Step 206, the PCC XDM service module sends the invited notification message to the interworking agent module of the CAB server.

Step 207, the network interworking agent module of the CAB server sends the invited notification message to the invited user B.

Step 208, the invited user B sends a message of accepting the invitation to the network interworking agent module of the CAB server.

Step 209, the interworking agent module of the CAB server forwards the message of the invited user B for accepting the invitation to the invitation subscription agent module.

Step 210, inviting the subscription agent module to initiate operation in the background, and notifying the subscription agent module of a subscription request for generating a relevant invitation.

Step 211, the subscription broker module initiates a subscription request to the PCC XDM service module of the inviting user a.

Step 212, invite the PCC XDM service module of user a to obtain user related preferences and policies.

Step 213, inviting the PCC XDM service module of the user a to obtain the relevant contact view of the user.

Step 214, the PCC XDM service module of the inviting user a generates a subscription relationship between the inviting user a and the invited user B according to the user preferences, policies and the relevant contact view.

The second method example is: the process of implementing the invitation subscription of the invitation subscription agent can also be understood as the process of the invitation subscription. In the method example, different from the first method example, authentication is directly realized through an authentication mechanism of the CAB server, so that the invited user is a legal and authorized CAB user, and the system security is improved. The invitation subscription agent module directly receives the invitation subscription request of the inviting user for subsequent processing.

That is, on the one hand, the request for the inviting user to want the personal contact view, i.e., the PCC information itself, subscribed, is initiated from the CAB client, and the invite subscription request may be sent directly to the invite subscription broker module. The inviting subscription agent module informs all invited users of the inviting subscription request, and can establish the binding relationship between the inviting user and the invited users after receiving the response of the inviting user. On the other hand, the invited user subscribes the PCC information of the invited user according to the information in the invitation subscription request notice through the subscription agent module, so that the subsequent subscription process is carried out.

As shown in fig. 5, a message flow diagram related to the present method example, where the method flow for implementing the invitation subscription of the invitation subscription agent of the present method example includes the following steps:

step 301, inviting the CAB client and CAB server of the user a to establish bidirectional authentication, which includes a complete authentication process.

Step 302, the inviting user a initiates an invite subscription request to the invite subscription agent module through the CAB client of the inviting user a.

Step 303, the invite subscription broker module forwards the invite subscription request to the PCC XDM service module of the inviting user in the XDM server.

Step 304, the PCC XDM service module queries the terminal situation owned by the invited user B, and generates an invited notification message.

Step 305, the PCC XDM service module sends the invited notification message to the invited user B.

Step 306, the invited user B sends a message of accepting the invitation to the invitation subscription agent module.

Step 307, inviting the subscription agent module to initiate operation in the background, and notifying the subscription agent module of a subscription request for generating a relevant invitation.

Step 308, the subscription broker module initiates a subscription request to the PCC XDM service module of the inviting user a.

Step 309, inviting the PCC XDM service module of user a to obtain user-related preferences and policies.

Step 310, inviting the PCC XDM service module of the user a to acquire a relevant contact view of the user.

Step 311, the PCC XDM service module of the inviting user a generates a subscription relationship between the inviting user a and the invited user B according to the user preferences, policies and the relevant contact view.

The third method example is: the subscription notification method process for inviting the subscription broker can also be understood as a subscription process executed after the process of inviting the subscription is completed and the subscription relationship is established. In the example of the method, after the subscription relationship is established, the notification message containing the subscribed information needs to be aggregated by the subscription agent module in the CAB server and then forwarded to the client of the user of the invited user.

That is, after the subscription relationship is generated and established, the PCC XDM service module of the inviting user in the XDM server generates an advertisement message containing the initial subscribed information, and once the subscribed information changes, the PCC XDM service module generates an advertisement message containing updated subscribed information, and the advertisement message may be first sent to the subscription broker module in the CAB server. And after aggregation processing, the subscription agent module sends the notification message to the invited user.

As shown in fig. 6, a message flow diagram related to the present embodiment is a flow diagram of a subscription notification method for inviting a subscription agent, where the flow diagram of the present embodiment includes the following steps:

step 401, inviting the PCC XDM service module of the user a to send an announcement message containing the current subscribed information to the subscription broker module in the CAB server.

Here, the current subscribed information is the initial subscribed information.

Step 402, the subscription broker module aggregates a plurality of advertisement messages.

Step 403, the subscription agent module sends the post-aggregation notification message to the network interworking agent module.

Step 404, the network interworking agent module returns the aggregated notification message to the invited user B; the invited user B parses the message to obtain the current subscribed information of the inviting user a.

Step 405, the subscribed information of the PCC XDM service module of the inviting user a is updated.

Step 406, inviting the PCC XDM service module of the user a to send an announcement message containing the updated subscribed information to the subscription broker module in the CAB server.

Step 407, the subscription broker module aggregates the plurality of advertisement messages.

Step 408, the subscription agent module sends the aggregated notification message to the network interworking agent module.

Step 409, the network intercommunication agent module returns the aggregated notification message to the invited user B; the invited user B parses the message to obtain updated subscribed information of the inviting user a.

Example four of the method is: the process of implementing the subscription notification method for inviting the subscription agent can also be understood as a subscription notification process executed after the process of inviting the subscription is completed and the subscription relationship is established. In the method example, different from the method example three, after the subscription relationship is established, the subscribed information is directly and synchronously updated to the user client of the invited user.

That is, after the subscription relationship is generated and established, the PCC XDM service module of the inviting user in the XDM server sends the initial subscribed information to the address book XDM service module of the invited user, and once the subscribed information changes, the PCC XDM service module also sends the updated subscribed information to the address book XDM service module of the invited user, and then the address book XDM service module triggers a synchronization mechanism to synchronously send the initial subscribed information or the updated subscribed information to the client of the invited user.

As shown in fig. 7, a message flow diagram related to the present embodiment is a flow diagram of a subscription notification method for inviting a subscription agent, where the flow diagram of the present embodiment includes the following steps:

step 501, the PCC XDM service module of the inviting user a sends the currently subscribed information to the address book XDM service module of the invited user.

Here, the currently subscribed information is the initially subscribed information.

Step 502, an address book XDM service module of the invited user B triggers a synchronization mechanism, and the current subscribed information is synchronously sent to all clients owned by the invited user B; the invited user parses the message to obtain the current subscribed information of the inviting user a.

Step 503, inviting the subscribed information of the PCC XDM service module of user a to be updated.

Step 504, the PCC XDM service module of the inviting user a sends the updated subscribed information to the address book XDM service module of the invited user.

Step 505, the address book XDM service module of the invited user B triggers a synchronization mechanism, and sends the updated synchronization of the subscribed information to all clients owned by the invited user B; the invited user parses the message to obtain updated subscribed information for the inviting user a.

It should be noted that the present invention is applicable to any mobile terminal, wired terminal or WEB client.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. An invitation subscription implementing system, the system comprising: client, server, XML document management XDM server; the server comprises an invitation subscription realizing module for realizing invitation subscription; wherein,

2. The system of claim 1, wherein the server further comprises a subscription implementation module configured to send a subscription request;

3. An implementation method for invitation subscription, the method comprising:

a user initiates a subscription invitation request through a client;

4. The method of claim 3, wherein before the invitation subscription implementing module of the server sending the invitation subscription request to the XDM server, further comprises: after authentication of a network interface module of a network intercommunication proxy module/an initial session protocol SIP internet protocol IP core network of the server, the network intercommunication proxy module/the SIP IP core network interface module forwards the invitation subscription request to the invitation subscription realizing module; or,

5. The method according to claim 3, wherein the XDM server generates the invited notification message and issues the invited notification message to the client of the other user specifically as follows:

6. The method according to claim 3, wherein the other users accept the invitation, the invitation subscription implementing module generates the subscription request, and the XDM server generates the subscription relationship specifically as follows:

7. The method of claim 4, wherein the authentication mechanism of the authentication certificate comprises: internet key exchange second version IKEv2, internet protocol encryption IPSec, digest authentication mechanism http digest, generic authentication architecture, IP multimedia subsystem authentication, or transport layer security mechanism.

8. The method of claim 3, further comprising: the invitation subscription realizing module broadcasts the invitation reservation in a multicast mode, and obtains the data of the broadcast invitation group user by accessing the shared group XDM server.

9. The method according to claim 5 or 6, wherein the generating of the subscription relationship further comprises:

10. The method according to claim 9, wherein the sending the subscription information to the other users according to the subscription relationship is specifically: the PCC XDM service module sends an announcement message containing initial subscribed information or updated subscribed information to a subscription realizing module according to the subscription relation between the user and other users; and the information is sent to the client sides of other users after the aggregation processing of the subscription realization module.

11. The method according to claim 9, wherein the sending the subscription information to the other users according to the subscription relationship is specifically: the PCC XDM service module sends the initial subscribed information or the updated subscribed information to the address book XDM service module according to the subscription relation between the user and other users; the address book XDM service module synchronizes the initial subscribed information or the updated subscribed information to the clients of other users with a synchronization mechanism.