CN100358283C - Business appearing system and method of issuring and obtaining appeared information - Google Patents

Abstract

The present invention discloses a presence service system, comprising: a presence server for receiving, storing and distributing presence information, where the presence information includes presence information issued by a presentity client and an application server; a presence client for Publish the presence information of the presentity to the presence server, or receive the presence information issued by the presence server; the application server is used to provide application services, collect user information, and publish it as the user's presence information to the presence server. The invention also discloses an application server and a method for publishing and obtaining user information. According to the present invention, various user information of the presentity user on the application server can be released to the presence service, and the watcher client can obtain various user information of the presentity user on the application server, expanding the source of presence information. In addition, user information about the presentity can be provided even when the presentity client is not running.

Description

A method for presenting a business system and publishing and acquiring presentation information

technical field

The present invention relates to the field of the Internet and the field of wireless communication, in particular to an application server, a presentation service system and a method for issuing and acquiring presentation information.

Background technique

Presentation service (PRESENCE SERVICE) is a communication service for collecting and distributing presentation information (PRESENCE INFORMATION). Currently, it is usually provided together with instant message service (INSTANT MESSAGE SERVICE). Of course, presentation service can also be provided separately, or with other services Such as the combination of online games. The Internet Engineering Task Force IETF, the Open Mobile Alliance OMA and other international standard organizations have preliminarily formulated the corresponding standard specifications for presentation services, which are being continuously improved. In the present invention, the terminology in RFC2778 is mainly used, the one that provides the presence information to the presence service is called the presentity (PRESENTITY), and the one that requests the presence information from the presence service is called the watcher (WATCHER). The user of the presence service can be a natural person or a non-natural person, that is, both the presenter and the observer can correspond to a natural person or a non-natural person.

A system structure diagram of an existing presentation business system is shown in FIG. 1 . It can be seen from the figure that the existing system includes:

A presence server, and a presence client connected to it, where the presence client includes a presentity client and a viewer client. The presentity client includes: a presentity and a presence user agent (PRESENCE USER AGENT). The watcher client includes: watcher and watcher user agent (WATCHER USER AGENT).

Presence information is transmitted between the presence client and the presence server where the presentity or observer is located through the presence protocol (PRESENCE PROTOCOL).

The presentity user agent is used as a means for the presence user to interact with the system, and the presence user publishes presence information to the presence server through the presence user agent.

The watcher user agent is used as a means for the watcher user to interact with the system, and the watcher user receives the presence information sent by the presence server through the watcher user agent.

In the prior art, since the presentity client publishes the user's presence information to the presence server, the presence information only includes various status information that can be published by the presentity client, such as network status information (such as online, offline) , application status information (such as idle or active) and user status information (such as available or busy), excluding various status information between the user and certain application services.

However, in practical applications, the watcher client often also wants to obtain various status information of the presentity user on various application servers, such as game information, web page browsing information, watching video information, business activity information, etc., in order to further In-depth understanding of each other's hobbies and needs, making it easy to find friends or partners. In addition, relatives, friends, and even strangers have the need to pay attention to each other's specific behaviors, and users also hope to publish some user status information on the application server so that others can know it in time. Information such as games played on the application server or movies you are watching, so that people with the same hobbies can communicate with you. In addition, in the existing presence services, generally presentity users can only provide and update the user's presence information by running the presentity client, and the source of presence information has great limitations, because many times even if the user does not run the presentity client , there may still be a need to provide presentation information.

Therefore, solving the above-mentioned requirements is one of the urgent problems to be solved in the presentation business.

Contents of the invention

The purpose of the present invention is to provide a presence service system, which enables the watcher client to obtain various user information of the presentity user on the application server in the presence service. Another object of the present invention is to provide a method for publishing and acquiring presence information, which can publish the user information of the presentity user on the application server to the presence service, and the watcher client can obtain the presence information of the presentity user in the presence service. User information on the server. Another object of the present invention is to provide an application server that can collect user information on the application server and publish the user information to the presence server as presence information.

The purpose of the present invention is achieved by the following scheme.

The present invention provides a presentation service system, including:

The presence server is configured to receive, store and distribute presence information, where the presence information includes the presence information issued by the presentity client and the presence information issued by the application server;

a presence client, configured to publish the presence information of the presentity to the presence server, or to receive the presence information issued by the presence server;

The application server is configured to provide application services to the presentity user, collect user information of the presentity user on the application server, and publish it to the presence server as the user's presence information.

The application server includes:

The user information collector is used to collect the user information of the presentity user on the application server, and publish it as the user's presence information to the presence server;

The memory is used to store user information.

The application server also includes a business container, which is used to execute the business logic of the application service, and store real-time user information related to the user and the application service;

The user information collector collects the user information related to the application service of the presentity user from the storage and the service container, and publishes it as the user's presence information to the presence server.

The application server further includes a filter for filtering the presence information issued to the presence server.

The application server also includes a compressor for compressing user information sent to the presentation server;

The presence server also includes a decompressor for decompressing the received user information.

An open service access gateway is also included between the application server and the presence server, which is used to provide an application program interface for the application server to communicate with the presence server.

The system also includes an extensible markup language file management server, which is used to store the authorization rule file, and provide the authorization rule of the presentity user to the application server and the presence server.

The present invention also provides a method for publishing presence information, including:

A. The presentity user registers the presence service on the application server;

B. The application server provides application services to the presentity user, and collects user information of the presentity user on the application server;

C. The application server publishes the collected information to the presence server as the user's presence information.

Described step A specifically comprises:

A1. The presentity user sends a registration presentation request to the application server;

A2. The application server forwards the registration request to the presence server;

A3. The presence server sends a confirmation message to the presence client and forwards the confirmation result returned by the presence client to the application server;

A4. The application server records the corresponding registration result.

The registration presentation request includes a uniform resource identifier and a presentation service password.

Said step A further includes: setting an authorization list and authorization scope on the application server, so that the application server sends user information to the presence server according to the authorization list and authorization scope.

The step A further includes: setting filter conditions on the application server, so that the application server sends the filtered user information to the presentation server according to the filter conditions.

Described step A also includes:

Steps for reactive authorization or pre-defined authorization.

Described step B specifically comprises:

B1. The application server stores the static user information in the memory;

B2. The application server stores the real-time user information in the service container;

B3. The user information collector collects static user information and real-time user information from storage and service containers.

In step B3, the user information collector regularly collects user information from the storage and the service container according to a predetermined time interval.

The step B specifically includes: the application server collects user information according to the authorization range set by the presentity user.

The step B specifically includes: the application server collects the user information of the presentity user after the presentity user logs in or is using the application service.

The step C specifically includes: the application server publishes the user information to the presence server in an active publishing manner or a requesting publishing manner.

The step C specifically includes: the application server publishes the user information to the presence server through the open service access gateway.

The step C specifically includes: the application server releases user information in batches to the presence server.

Described step C specifically comprises:

C1. The application server compresses the user information before releasing the user information to the presence server;

C2. The presentation server decompresses the received user information and then updates the user information.

The present invention also provides a method for acquiring presentation information, including:

D. The observer client sends a request for acquiring presence information to the presence server;

E. The presence server notifies the application server to collect user information of the presentity according to the request for obtaining presence information, the application server is used to provide application services for the presentity user, and the application server publishes the collected user information as presence information to the presence server;

F. The presence server sends the user information of the presentity to the watcher client.

The step E further includes: the application server collects user information according to the authorization rules set by the presentity user, and publishes the user information as presence information to the presence server.

The request for acquiring presentation information includes filter conditions.

The step E specifically includes: the application server collects the user information of the presentity according to the filter condition.

The present invention also provides an application server, which is used to provide application services for presentity users, including: storage, used to store user information; user information collector, used to collect user information of presentity users in the storage of the application server information, and publish the collected user information to the presence server as the user's presence information.

The application server also includes:

The business container is used to execute the business logic of the application service, and store the real-time user information related to the user and the application service. The user information collector collects the user information related to the presentity user and the application service from the storage and the service container, and uses it as a user The presence information of is published to the presence server.

The application server also includes:

The filter is used to filter the presence information published to the presence server.

The application server also includes:

The compressor is used to compress the user information sent to the presence server.

Therefore, according to the present invention, various user information of the presentity user on the application server can be released to the presence service, and the watcher client can obtain various user information of the presentity user on the application server, which expands the provision of presence information source and delivery method. In addition, even when the presentity client is not running, it is possible to issue and acquire user information on the presentity.

Description of drawings

FIG. 1 shows a schematic diagram of a presentation service system in the prior art;

Fig. 2 shows a schematic diagram of the presentation service system of the present invention;

Fig. 3 shows the schematic diagram of the application server of the present invention;

Fig. 4 shows a flow chart of issuing and acquiring presence information according to the present invention;

Fig. 5 shows a flow chart of registering a presence service on an application server;

Fig. 6 shows the flow chart of modifying the presence service on the application server;

Fig. 7 shows the application scenario of the present invention in online games;

FIG. 8 shows a schematic diagram of changing and updating presentation information;

Fig. 9 shows the flow chart of authorization mechanism example 1;

Fig. 10 shows the flow chart of authorization mechanism example 2;

Fig. 11 shows a flow chart of obtaining presence information corresponding to the first example of the authorization mechanism;

FIG. 12 shows a flow chart of acquiring presence information corresponding to the second authorization mechanism example;

Figure 13 shows the authorization list;

Figure 14 shows another authorization list;

Fig. 15 shows a schematic diagram of changes in the authorization list.

Detailed ways

In order to facilitate those skilled in the art to understand and implement the present invention, the embodiments of the present invention are now described with reference to the accompanying drawings.

The present invention provides a presentation service system. As shown in FIG. 2 , the presentation service system of the present invention includes a presence server, a presence client and an application server, where the presence client is an observer client. The presentation service system of the present invention will be described in detail below with reference to the accompanying drawings.

The terminal where the presentity user is located does not need to run the presence client. The terminal may be a mobile phone, a computer, etc., and is connected to the application server. The presentity user logs in to the application server through the terminal. Register presentation services in the application server, and set authorization rules and policies, etc.

The watcher client includes a watcher and a watcher user agent. The watcher user agent serves as a platform for watcher users to interact with the system; the watcher is used to receive the presence information of the presentity sent by the presence server. The observer of the observer client can be divided into a query body and a subscription body: the query body simply requests to query the user information of the presentity user on the application server; and the subscription body subscribes to the user information of the application server where the presentity user is ) changes, the updated presentation information can be received in time.

According to the present invention, the presence service system of the present invention further includes an application server connected between the presentity user and the presence server. Presentity users can register presence services on the application server. After the presence user registers the presence service on the application server, the application server will send the user information of the presentity user who has logged in and is using the application service as the user's presence information to the presence The server, if the presentity user is playing a game on the application server, can send its real-time user information and static user information (such as the current game name, current points, nickname, etc.) to the presence server; The information is sent to the watcher of the watcher client, and finally notified to the watcher user by the watcher user agent. It is worth mentioning that, according to the present invention, even if the presentity client is not running, the application server can send the presentity user information to the watcher client. In addition, in order to further control the release of user information of presentity users on the application server, that is, to control which observers can obtain which user information, authorization rules and policies can be set on the application server, and the application server provides user information according to the authorization rules. You can use Extensible Markup Language XML configuration authorization rules, for example, the sub-element contained in the "identity" element can be used to specify the uniform resource identifier URI of the authorized observer:

<identity><id entity=″user@example.com″/></identity>

As above, it means that the watcher whose URI is "user@example.com" has the right to obtain the user information of the presentity user on the application server, and there can be multiple URIs to form an authorization list. Similarly, the "provide-attribute" element can be used to limit which user information is provided, that is, the scope of authorization, such as:

<provide-attribute>

<attribute name="game-name"/>

<attribute name="score"/>

</provide-attribute>

As indicated above, the scope of authorization is to provide game name and point information. The authorization list and authorization scope can be used in combination, that is, the authorization scope is correspondingly set for an authorization list.

Since there may be multiple application servers, XML files for configuring authorization rules and policies such as authorization lists can be uniformly placed on the Extensible Markup Language Document Management Server (XDM Server), so that the authorization list can be shared by various application servers and presentation servers , without repeating the settings on each server. In addition, the presence server can uniformly determine the access rights of the presence information according to the authorization rules set on the XDM server, and the application server no longer limits the authorization rights, and is only responsible for publishing user information to the presence server.

As shown in Figure 3, the application server also includes a user information collector, a memory (such as a database) and a service container, the user information collector is connected to the database and the service container respectively, and can be presented according to the authorization authority of the client (such as an authorization list or authorization scope) to obtain user information and store the collected user information in memory. The database is used to store relatively stable user information, such as user registration information, and the service container will update the user information to the information in the database when the user quits the service or reaches a predetermined period of time. The service container stores user information when the presentity user is using the service of the application server. When real-time user information needs to be collected, the user information collector can access and acquire user information in the service container. The current way for the presence client to update the presence information is to publish the updated presence information to the presence server when it detects that the presence information has changed. However, the real-time user information on the application server changes very quickly, such as game points and game roles. Information such as location coordinates, if there is a change, it will cause too much system load if an update is issued to the presentation server. Therefore, the update interval can be set for real-time user information. For example, it is set to update and release every 5 minutes instead of real-time to update.

In addition, the application server can also perform batch publishing, that is, each time the user information of multiple users is released to the presence server, a compressor is set on the application server side, and a decompressor is set on the presence server side. A compressor is used to compress the user information to be released, and a decompressor on the presence server side decompresses the received user information, and then the presence server performs update processing of the presence information. This greatly improves the communication efficiency between the application server and the presence server.

The user information on the application server does not need to be published to the presence server. It can be selectively published according to the subscription status of the presence information. Unsubscribed user information will not be actively published, and only when the presence server requests these user information to the presence server. its provided. The subscription request sent by the observer client includes filter conditions, which specify which presentation information to receive. The filter conditions can be set in XML, such as:

<filter id="001" uri="sip:bob@example.com"><what>

<include type=″namespace″>urn:ietf:params:xml:ns:gamepidf</include>

<exclude>/gamepidf:realtime</exclude>

</what></filter>

As above, in the filter condition "filter" set by the observation body "sip:bob@example.com", the "include" element is used to set the presentation information to include the attributes given in the namespace "gamepidf", while the "exclude" element sets no Contains properties under "realtime" for realtime user information. The filter conditions are stored on the XDM server or the application server, and filters are set on the application server to filter the user information published to the presentation server according to the filter conditions. In addition to specifying which presence information to receive, filter conditions can also set which changes in presence information need to be notified to the observer. When these conditions are satisfied, the instant application server mainly releases the presence information in batches, and immediately releases the changed presence information separately. like:

<changed>/gamepidf:gameroom</changed>

Indicates that when the gameroom attribute of the presence information changes, the application server will immediately send the updated gameroom information and other user presence information to the presence server. You can further use "from" and "to" to limit which specific values change before releasing the presentation information:

<changed to="1000">/gamepidf:score</changed>

Indicates that when the integral "score" information exceeds 1000, the presentation information is released.

When the user does not log in to the application server or use the application service, usually the presence information does not change, and the application server does not need to publish the presence information to the presence server. The application server saves a list of users who have registered the presence service and have logged into the application server or are using the application service, and only collect and publish presence information for users in the user list.

The application server and the presence server are usually not located in the same network. For example, the presence server is located in the operator's network, while the application server is located in the Internet. The application server and the presence server do not communicate directly but through a gateway. Here, the Parlay/OSA open service access gateway can be set in the presentation service system. The Parlay/OSA application program interface is defined by the Parlay group (http://www.parlay.org/). OSA is an open service interface. It is cited in the mobile service association structure of 3GPP (Third Generation Mobile Communications Partnership Project, http://www.3gpp.org/) and 3GPP2, and Parlay is the API part of OSA. For details, please refer to relevant standard specifications . The application server publishes the collected user information to the Parlay/OSA gateway first, and then the Parlay/OSA gateway updates the user information to the presentation server. Generally, the Parlay/OSA gateway also provides interfaces for accessing other services or capabilities in the communication network, such as location services, billing, and call control.

Utilizing the above-mentioned presence service system, the present invention also provides a method for publishing and acquiring presence information, the basic idea of which is: presentity user registers presence service on the application server, that is, authorizes the application server to release user information to the presence server; the application server collects The user information of the presentity user is published to the presence server as a part of the presence information of the presentity user; the presence server sends the user information of the presentity user to the watcher client. The present invention will be described in detail below with reference to the accompanying drawings.

As shown in Fig. 4, in step 1, the presentity user registers the presence service on the application server.

The application server can be a different type of application server that provides various contents, such as game server, streaming media server, e-commerce server, web server, chat server, etc. These application servers can provide corresponding various application services, such as Services such as online games, streaming media playback, e-commerce, web browsing, and chatting.

The opportunity for the presentity user to register the presence service on the application server can be during registration or during the application process. When registering, you can use the registration page provided by the application server, and during the application process, you can use the application page provided by the application server. Usually, the presentity user has a corresponding account or identifier on the application server, such as the URI of the presentity, and the application server uses this to identify the user, and stores the user's registration information and business information together with the account or identifier, such as the user's basic information, billing information, customized service features, etc. The user who registers the presence service correspondingly saves corresponding flag information on the application server, indicating that the user wants to use the presence service capability of the application server, that is, publishes presence information through the application server.

In order to ensure the security of presence information, when the presentity user registers the presence service with the application server, the presentity user may be required to enter not only the corresponding account identifier such as URI in the presence service, but also the corresponding password, and the application server will pass the presence server The registration is successful only after the authentication is confirmed. In addition, the registration of the presence service is not mandatory. If the user does not want others to observe his user information on the application server through the presence service, he does not need to register. In order to further ensure the security of user information, the user information of the presentity user is only allowed to be known by certain people, or the user information of the presentity user is only allowed to be known by others under specific circumstances, the presentity user registers the presence on the application server After the transaction, the authorization list and authorization scope can be further registered on the application server, and the application server can judge which user information of the presentity user to provide to whom according to the authorization list and authorization scope. In addition, the final application server can send and store the authorization list and authorization range to the XDM server or the presence server, so that each application server and presence server can share.

The following describes the process of the presence user registering the presence service on the application server with reference to FIG. 5 and FIG. 6 .

As shown in FIG. 5 , the process of registering the presence service on the application server when the presentity user registers is described first.

In order to enable the presentity user to register the presence service on the application server during registration, the application server may provide a presence service registration item on the registration page, so that the presentity user registers the presence service when registering on the application server. When registering the presence service, the presentity user must register its presence service account in the presence service registration item, such as QQ account, MSN account, mobile phone number, etc., because these accounts correspond to the unique identity of the presentity user in the presence service, so that other users Identify and get information about its presence.

In step 50, when the presentity user terminal applies for registration on a certain online game server, the presentity user sees that the registration page of the online game server provides the presence service entry and its description, and the presentity user decides to use this Business characteristics, and register its presentation account (516870210) and password (******). It is also possible not to provide the password for the presence service to the application server, but to use another method for authentication, that is, after receiving the registration request sent by the user terminal of the presentity, the application server sends an authentication request including the presence account to the presence server, and the presence server sends an authentication request to the presence server. The presence client of the presence account or the mobile phone number registered with the presence account sends a confirmation message, and the presence server returns an authentication success message to the application server after confirmation, and the application server records the registration result, and the registration is completed.

In step 51, the presentity user further registers the authorization list and authorization scope on the online game server. The content of the authorization scope is different for different application servers. For example, FIG. 13 shows the authorization scope of user information in the online game.

As shown in Figure 13, the scope of authorization includes two parts: static user information and real-time user information. Each part of user information also includes multiple contents. For example, the static user information part has the following content options: nickname, gender, points, age, school, etc.; the real-time user information part has the following content options: location, game time , points, life value, mood, etc. In Figure 13, the presentity user chooses to publish static user information such as nickname, gender, school, etc., and real-time user information such as game time and life value, and the application server only collects the user information that the presentity user chooses to publish.

In step 52, the application server requests the presence server for an authentication account and password.

In step 53, the presence server authenticates the presence account and password.

In step 54, the presence server notifies the application server of the authentication result.

In step 55, the application server performs registration processing on the authentication result, and displays the registration success or failure result to the presentity user.

In step 56, the application server sends a registration success or failure notification to the presentity client via the presence server, which is an optional step.

The above describes the process of the presence user registering the presence service with the application server during registration. When the presentity user operates on the application server, he can also register the presence service with the application server through the application interface, or modify the presence service information.

To register or modify presence services for presentity users when operating on the application server. The application server can provide the presence service registration option in the interface of the application client (such as the main interface of the game client), so that when the presentity user needs to modify the characteristics of the presence service (here, the modification includes establishment and cancellation), he can register the presence service at any time. Modify the relevant items in the item, as shown in Figure 6, the process of modifying the presentation service on the application interface will be described in detail below, and here the authentication is performed by not providing the presentation service password to the application server.

In step 61, the application client on the terminal where the presentity user is located sends a request to register or modify the presence service to the application server, and the request to register or modify the presence service includes the presence account. The application client and the presentity client can be on the same terminal.

In step 62, the application server determines the presence server to which the presence account belongs. Because there may be multiple presence servers, for example, there will be at least one presence server in the network of different operators, and the corresponding relationship between the presence account and the presence server can be saved on the application server. Corresponding to the address of the presence server, the application server determines the presence server to which the mobile phone number belongs according to the number segment of the mobile phone number. Another method is that in step 61, when the application client registers the presence service, it provides the user with the name of the presence service provider to which the user belongs, and the corresponding relationship between the presence service provider and the presence server address is pre-stored on the application server. The application server determines the corresponding presence server according to the name of the presentation service provider given by the user; of course, the corresponding relationship between the presentation service provider and its Parlay/OSA (Open Service Access) gateway can also be pre-stored on the application server, and the application server calls the corresponding Parlay The presence service interface of the /OSA gateway communicates with the presence server, and the Parlay/OSA gateway determines its belonging presence server according to the presence account. If there is only one presence server in the network, this step may not be necessary.

In step 63, the application server sends a presence account request authentication to the presence server.

In step 64, the presence server sends an authentication confirmation notification message to the presence client corresponding to the presence account.

In step 65, the presence client returns the result of the authentication confirmation process to the presence server.

In step 66, the presence server notifies the application server again.

In step 67, the application server modifies or registers the presence service according to the authentication result. If the authentication is successful, the application server modifies the item of the presence service according to the presentity user's request, otherwise it refuses the modification.

In step 68, the application server returns to the application client the result of the success or failure of modifying the presentation service.

Usually, authentication is only required when the user registers the presence service on the application server for the first time, and no authentication is required for subsequent settings of the authorization list and authorization scope and cancellation of the presence service. Of course, it is also possible to authenticate each operation of the presentation service to enhance security. For example, the presentation user modifies the authorized content, and then enters the presentation service entry on the main interface of the game client, and needs to enter the presentation account (516870210); After the presence server authenticates the presence account (516870210) through the presence client, the authorization scope can be set to user information as shown in Figure 14: nickname, gender, grade, sect, location, etc.

In step 2 of FIG. 4 , the application server collects the user information of the presentity user and publishes it to the presence server as a part of the presence information of the presentity user.

In order to collect the user information of the presentity user, a user information collector is set in the application server, and the user information collector can access and call the database and the presentity user information in the service container. Specifically, the user information collector collects the user information of the presentity user in the application server periodically or in real time according to the authorization range set by the presentity user when registering the presence service. The presentity user refers to the type of users who are requested to view the presence information. There may be multiple presentity users, that is, the user information of multiple presentity users can be collected at the same time at regular intervals or in real time.

The following uses the game server as an example to illustrate the process of collecting user information of presentity users. The database in the game server is a key component for the sustainable and stable operation of the game system. It stores static user information, such as grades, points, etc.; and the business container It not only loads and runs the game, but also stores real-time user information. When the user exits the game, the business container will update the latest user information to the database. In addition, the game server is provided with a user information collector, which can be connected to the database and the service container, and the user information collector can obtain the user information of the presentity user according to the set authorization scope. There are also two situations here:

In the first case, the presentity user is running the game. Because some information in the database is not real-time (updated when the user exits the game). At this time, the user information collector should collect the user information of the presentity user in the game service container, such as real-time points, real-time level, real-time life value, etc.; of course, if real-time information is not needed, it can still only collect relevant user information in the database.

In the second case, the presentity user is not running the game. At this time, the user information collector only needs to collect the user information of the presentity user in the database.

Next, the application server publishes the collected user information of the presentity user to the presence server in two ways:

The first release method: active release. The application server actively sends the collected user information of the presentity user to the presence server as a part of the presence information. At this time, the application server can also adopt timing or real-time publishing; in the case of active publishing, when the watcher client needs to present When the user information of the real user is provided, it may be directly provided by the presence server. Here, a presentity user refers to a user who is requested to view presence information, and there may be multiple presentity users, that is, the application server may publish user information of multiple presentity users at the same time. For example, the streaming media server simultaneously releases the collected user information of multiple presentity users (1, 2, 3...N) such as streaming media information being played to the presence server in batches. In order to improve the release efficiency, active release can be adopted.

The second release method: request release. Only when a request from the presence server is received, the application server sends the collected user information of the presentity user to the presence server as part of the presence information; When requesting user information, the presence server needs to request the application server to provide it. For example, if the presentity user wants to request the presentity user's user information (such as game name, game room, etc.) The user information of the user is sent to the presence server, and the presence server sends it to the watcher client.

In step 3 of FIG. 4 , the presence server sends the user information of the presentity user to the watcher client.

The application scenario of the present invention in online games is shown in FIG. 7 . In step 71, user A registers the presence service on the online game server, that is, entrusts the online game server to release its user information; in step 72, user A sets authorization rules and policies to allow user B to obtain his own presence information, including online game The user information issued by the server; in step 73, user A logs into the online game server, and starts to play games; in step 74, the online game server collects user information such as the game server and game room where user A is located, and in step 75, Publish the collected user information to the presence server; in step 76, the presence server notifies user B of the user information; in step 77, user B can log in to the online game server and enter the game room where user A is located to play with him game.

The following example illustrates the updating and changing process of the presentation information.

As shown in Figure 8, initially, the user information of the presentity user on the application server, the presence server and the watcher client (watcher) is P1; when the user information of the presentity user on the application server changes from P1 to P2, The application server sends the latest user information P2 to the presence server, and the presence server changes the user information of the presentity user from P1 to P2, and sends the modified user information P2 to the observer client; finally, the application server, presence server, The user information of the presentity users of the watcher client becomes P2.

For example, the presentity user is running a game on the online game server, and the initial user information when he first logs in is P1; The user information P2 is published to the presence server, and the presence server sends the user information P2 to the watcher client. FIG. 15 shows the change from user information P1 to user information P2.

In addition, in order to ensure the security and privacy of the user information of the application server, according to the present invention, authority control can also be set to provide the user information of the presentity user for the observer client. The authorization mechanism is described below, which is divided into responsive authorization and preset authorization. authorized.

Example 1 of the authorization mechanism, responsive authorization, when the watcher client requests the application server to subscribe to the user information of the presentity user on the application server through the presence server, the application server detects whether the current user has logged in or is using the application service, if If yes, send a confirmation notification to the application client, otherwise, the presence server sends a confirmation notification to the presentity client; the application client returns to the presence server through the application server, or the presence client directly returns to the presence server whether to allow the observer client Receive the user information of the presentity user in the application server. Not only that, you can also set the user information of what content is provided for the watcher. For example, only the observer client is allowed to obtain points, grades, and nickname information, but not other information. Specifically, the set authorization scope and the URI of the associated observer can be recorded in an XML file, and the XML file is stored in the application server and On the rendering server or on a standalone XDM server. The application server collects the required user information according to the authorization range set in the XML file (maybe a combination of multiple authorization ranges), and regularly publishes it to the presence server actively, and the presence server sends the user information according to the subscription authorization record in the XML file. Push to authorized watcher clients. The process of authorization mechanism 1 is described below with reference to FIG. 9 .

In step 91, the watcher client sends a subscription request to the presence server.

In step 92, the presence server forwards the subscription request to the application server, and the application server judges whether the subscribed presentity user has logged in or is using the application service, and if so, executes step 93: the application server sends a subscription confirmation notification to the application client, The application client returns a confirmation result message to the application server, and the application server notifies the presence server of the confirmation result; otherwise, execute step 94: the application server returns to the presence server a notification that the presentity user is not currently logged in or using the application service, and the presence server sends a notification to the presence server. The presence client sends a subscription confirmation notification, and the presence client returns a confirmation result message to the presence server.

In step 95, the presence server generates or modifies the XML file containing the subscription authorization record according to the confirmation result. The XML file containing the subscription authorization record can be sent to the XDM server and the application server synchronously. In addition, if there is an XDM server, in steps 93 and 94, both the application client and the presentity client can directly send the confirmation result to the XDM server with the XML Configuration Access Protocol (XCAP (XMLConfiguration Access Protocol).

Example 2 of the authorization mechanism, preset authorization, the presentity client pre-sets the authorization list and authorization scope, and then sends it to the XDM server through the XCAP protocol. When the observer client requests the presence server to obtain the When the user information on the server is obtained, the presence server obtains the corresponding XML file content from the XDM server, decides whether to provide the user information of the presentity user to the observer client and what user information is provided according to the authorization list and authorization scope, and then sends the The application server requests to acquire the user information of the presentity user. As shown in Figure 10, the process of authorization mechanism 2 is described below.

In step 101, the presentity client sets the authorization list and authorization scope and sends them to the XDM server.

In step 102, the watcher client sends a request to the presentity server to acquire user information of the presentity user.

In step 103, the presence server queries the XDM server to determine whether the request and/or request range of the watcher client is allowed, and if so, executes step 104: the presence server sends authorized user information to the watcher client; otherwise, executes step 105 : The presence server sends a rejection message to the watcher client.

Next, assume that the presentity user has registered the presence service on the application server, and on the basis of the authorization mechanism example 1, take the user information of the subscribed presentity user obtained by the subscriber on the application server as an example, and refer to Figure 11 to illustrate its message flow, as shown in Figure 11.

In step 111, the watcher client (subscriber) sends a subscription request to the presence server, that is, requests to subscribe to the user information of the presentity user on the application server. The subscription request may include filter conditions, that is, specify the content of the subscribed information, and send an information update notification when the information changes.

In step 112, the presence server forwards the subscription request to the presentity client. Here, the subscription request confirmed by the presentity client is taken as an example, of course, the subscription request may also be confirmed by the application client.

In step 113, the presentity client decides whether to allow the subscription and the scope of the subscription, and generates an authorization or rejection message.

In step 114, the presence client sends an authorization or rejection message to the presence server.

In step 115, the presence server forwards the authorization or denial message to the watcher client.

If the subscription request is rejected, such as an anonymous request, the presence client sends the rejection information to the observer client through the presence server. In addition, the presentity client can reject some subscribers in a polite way, that is, accepting subscription requests on the surface without providing any content, so as to avoid mutual embarrassment. The presence server returns a subscription success message to the watcher client, but does not send the user information of the presentity to it, and then ends the process.

If the authorized subscription request is accepted, then in step 116, the application server collects user information of the presentity user.

In step 117, on the basis of the authorized subscription, if the user information changes, the application server sends the changed user information to the presence server.

In step 118, the presence server forwards the user information to the watcher client according to the authorization.

In addition, the presentity client and the observer client can also unsubscribe from the presence information, and the subscription cancellation generally needs to notify the subscriber.

Next, we assume that the presentity user has registered the presence service on the application server, and on the basis of the authorization mechanism example 2, take the query body requesting the user information of the presentity user on the application server as an example, and refer to Figure 12 , explaining its message flow:

In step 121, the presentity client sends the authorization list and authorization scope to the XDM server.

In step 122, the watcher client (query body) sends a query request for the presentity to the presence server, that is, requests to query the user information of the presentity user on the application server.

In step 123, the presence server judges whether to allow the query and the scope of the query according to the authorization list provided by the presentity client on the XDM server.

If the query request is rejected, such as a stranger's request, then step 125 is performed: the presence server forwards the rejection information to the watcher client, and then ends the process.

If the query request is authorized, step 124 is executed: the presence server forwards the query request to the application server.

In step 126, the application server collects user information of the presentity user.

In step 127, the application server sends the user information to the presence server.

In step 128, the presence server forwards the received user information to the watcher client.

In order to facilitate the query, the observer client can be allowed not to specify a specific presentity, but to include the retrieval conditions in the query request sent to the presence server, for example, the game name in the user information is "Go", and the presence server searches to meet the above conditions The user list of the presentity user on the game server is sent to the watcher client, so that the watcher client can find users who meet the conditions, and further query the user information of the specified presentity on the application server.

It is worth noting that while the application server publishes the user information of the presentity user, the information of the application server, such as advertisement information, can be released as part of the presence information, such as the URL of the application server, so that the supply of application servers can be expanded. It is a channel for vendors to promote their application services, so that more people can know the information of the application server, thereby attracting more customers.

According to the present invention, the watcher client can obtain richer presence information, so as to know more information about the presentity user and information about using application services.

Although the present invention has been described by the embodiments, those of ordinary skill in the art know that, without departing from the spirit and essence of the present invention, the present invention can have many modifications and variations, and the scope of the present invention is defined by the appended rights Requirements to limit.

Claims (30)

1, a kind of operation system that presents is characterized in that, comprising:

Presence server is used for receiving, storage and distribution presentation information, and presentation information comprises the presentation information that presents the issue of body client and the presentation information of application server issue;

Present client, be used for presenting the presentation information of body, perhaps be used to receive the presentation information that described presence server issues to described presence server issue;

Application server is used for providing application service to presenting the body and function family, and collects and to present the user profile of body and function family on application server, and its presentation information as the user is published to presence server.

2, the system as claimed in claim 1 is characterized in that, described application server comprises:

The user information collection device is used to collect and presents the user profile of body and function family on application server, and its presentation information as the user is published to presence server;

Memory is used for storing subscriber information.

3, system as claimed in claim 2 is characterized in that, described application server also comprises professional container, is used to carry out the service logic of application service, and the storage user active user information relevant with application service;

The user information collection device is collected from memory and professional container and is presented the body and function family user profile relevant with application service, and its presentation information as the user is published to presence server.

4, system as claimed in claim 2 is characterized in that, described application server also comprises filter, and the presentation information that is used for the issue of subtend presence server is filtered.

5, the system as claimed in claim 1 is characterized in that, described application server also comprises compressor reducer, is used to compress the user profile that mails to presence server;

Described presence server also comprises decompression machine, is used for the user profile of receiving is carried out decompress(ion).

6, the system as claimed in claim 1, it is characterized in that, between described application server and described presence server, also comprise an open service IAD, be used for providing application programming interfaces that itself and presence server are communicated to application server.

7, the system as claimed in claim 1 is characterized in that, but described system also comprises extension flag language file management server, is used to store the authorization rule file, provides the authorization rule that presents the body and function family to application server and presence server.

8, a kind of method of issuing and presenting information is characterized in that, comprising:

A, present the body and function family and on application server, register and present business;

B, application server provide application service to presenting the body and function family, collect to present the user profile of body and function family on application server;

C, application server are published to presence server with the information of collecting as user's presentation information.

9, the method for issuing and presenting information according to claim 8 is characterized in that, described steps A specifically comprises:

A1, present the body and function family and send registration to application server and present request;

The request of will registering of A2, application server is transmitted to presence server;

A3, presence server send acknowledge message and will present the affirmation result that client returns and be transmitted to application server to presenting client;

A4, application server write down corresponding enrollment results.

10, the method for issuing and presenting information according to claim 8 is characterized in that, described registration presents request and comprises the unified resource sign and present professional password.

11, the method for issuing and presenting information according to claim 8, it is characterized in that, described steps A also comprises: the grant column list and the scope of authority are set, so that application server is issued presence server according to the grant column list and the scope of authority with user profile on application server.

12, the method for issuing and presenting information according to claim 8 is characterized in that, described steps A also comprises: filtercondition is set, so that the user profile of application server after will filtering according to filtercondition is issued presence server on application server.

13, the method for issuing and presenting information according to claim 8 is characterized in that, described steps A also comprises:

Carry out the step of response type mandate or default formula mandate.

14, the method for issuing and presenting information according to claim 8 is characterized in that, described step B specifically comprises:

B1, application server leave static subscriber's information in the memory in;

B2, application server leave active user information in the professional container in;

B3, user information collection device are collected static subscriber's information and active user information from memory and professional container.

15, the method for issuing and presenting information according to claim 14 is characterized in that, the user information collection device is regularly collected user profile at interval according to preset time among the described step B3 from memory and professional container.

16, the method for issuing and presenting information according to claim 8 is characterized in that, described step B specifically comprises: application server is according to presenting the scope of authority collection user profile that the body and function family is provided with.

17, the method for issuing and presenting information according to claim 8 is characterized in that, described step B specifically comprises: application server is collected the user profile that presents the body and function family when presenting login back, body and function family or using application service.

18, the method for issuing and presenting information according to claim 8 is characterized in that, described step C specifically comprises: application server is issued user profile with active published method or request published method to presence server.

19, the method for issuing and presenting information according to claim 8 is characterized in that, described step C specifically comprises: application server is issued user profile by the open service IAD to presence server.

20, the method for issuing and presenting information according to claim 8 is characterized in that, described step C specifically comprises: application server is issued user profile in batches to presence server.

21, the method for issuing and presenting information according to claim 8 is characterized in that, described step C specifically comprises:

C1, application server compress described user profile earlier before presence server issue user profile;

C2, presence server carry out the renewal of user profile after to the user profile decompress(ion) of receiving again to be handled.

22, a kind of method that gets access to the information presented is characterized in that, comprising:

D, observation body client send the request of getting access to the information presented to presence server;

E, presence server are collected the user profile that presents body according to the described request notice application server that gets access to the information presented, described application server is used to and presents the body and function family application service is provided, and application server is distributed to presence server with the user profile of collecting as presentation information;

F, presence server will present the user profile of body and issue observation body client.

23, the method that gets access to the information presented according to claim 22, it is characterized in that, described step e also comprises: application server is collected user profile according to the authorization rule that presents the setting of body and function family, and user profile is distributed to presence server as presentation information.

24, the method that gets access to the information presented according to claim 22 is characterized in that, the described request of getting access to the information presented comprises filtercondition.

25, the method that gets access to the information presented according to claim 24 is characterized in that, described step e specifically comprises: application server is collected the user profile that presents body according to filtercondition.

26, a kind of application server, it is used to and presents the body and function family application service is provided, and comprises memory, is used for storing subscriber information, it is characterized in that, also comprises:

The user information collection device is used for collecting and presents the user profile of body and function family at the memory of application server, and the user profile of collecting is published to presence server as user's presentation information.

27, application server according to claim 26 is characterized in that, also comprises:

Professional container, be used to carry out the service logic of application service, and the storage user active user information relevant with application service, the user information collection device is collected from memory and professional container and is presented the body and function family user profile relevant with application service, and its presentation information as the user is published to presence server.

28, as claim 26 or 27 described application servers, it is characterized in that, also comprise:

Filter, the presentation information that is used for the issue of subtend presence server is filtered.

29, as claim 26 or 27 described application servers, it is characterized in that, also comprise:

Compressor reducer is used to compress the user profile that mails to presence server.

30, application server as claimed in claim 28 is characterized in that, also comprises:

Compressor reducer is used to compress the user profile that mails to presence server.

Images