CN100461774C - A way to subscribe to presence information - Google Patents

Abstract

The invention discloses a method for subscribing to presence information. Applied in the field of wireless communication. It is used to solve the problem in the prior art that when the subscription fails, the instant message and presence service server does not send any message to the subscriber user, so that the user cannot determine whether the subscription is successful. The method of the present invention includes: the instant message and presence service server sends an authorization request message to the subscriber user according to the subscription request message sent by the subscriber user; C, after being confirmed by the subscriber user, sends an authorization confirmation message to the instant message and presence service server D. If the instant message and presence service server receives the authorization confirmation message and indicates that it accepts the subscription, then the instant message and presence service server sends a subscription success message to the subscriber user; otherwise, the instant message and presence service server sends a message to the subscriber The user sends a subscription failure message, or discards the subscription failure message, or temporarily stores the subscription failure message.

Description

A way to subscribe to presence information

technical field

The invention relates to the field of wireless communication, in particular to a method for subscribing presence information.

Background technique

Instant Messaging and Presence Service (IMPS) belongs to a person-to-person and person-to-group messaging mobile data service based on presence information (Presence), which is researched and provided by the IMPS working group of the International Standards Organization OMA (Open Mobile Alliance) Application frameworks and specifications.

A registered user of the IMPS service may subscribe to presence information of other registered users. The presence information includes: availability of the client device (for example: power on/off information, call status), user status (idle, not idle, meeting), location information, capability of the client device (for voice, text, GRPS, multimedia support); the presence information also includes: retrievable user information, such as: user's mood (happy, angry, etc.), user's hobbies (soccer, fishing, computing, dancing, etc.). Because the user's existence information is personalized and involves certain personal information, only relevant information approved by the user is disclosed to the public.

In the IMPS service, a user can obtain good user experience by subscribing to the presence information of other users. If the subscription is successful, the system will automatically notify the subscriber user when the subscribed existence information changes.

Currently, in the IMPS service system, the signaling flow chart of subscribing to the presence information of a single user is shown in FIG. 1 , and the signaling flow chart of subscribing to the presence information of multiple users is shown in FIG. 2 . User A sends a subscription request to subscribe to the presence information of user B. If the subscription is successful, the instant message and presence service server IMPS Server (Instant Messaging and Presence Service) sends a subscription success message (PresenceNotification) to subscriber user A. In the message Carry the attribute value of the existence information that has been successfully subscribed, that is, the subscriber user A will immediately receive the existence information of the subscribed user B. For example: User A subscribes to user B's location information and current call status. After the subscription is successful, the server will automatically carry user B's location information and current call status in the subscription success message and send it to user A.

However, if the subscription fails, according to the Wireless Village protocol (WirelessVillage) of the OMA standard organization, the IMPS Server will not send any message to the subscriber user. Therefore, the subscriber user cannot know whether the subscription is successful, let alone the reason for the subscription failure.

Contents of the invention

The present invention provides a method for subscribing presence information to solve the problem in the prior art that when the subscription fails, the instant message and presence service server IMPS Server does not send any message to the subscriber user, so that the user cannot determine whether the subscription is successful .

The present invention further solves the problem in the prior art that the subscriber user cannot know the cause of the subscription failure when the subscription fails.

In order to solve the above problems, the present invention provides the following technical solutions:

A method of subscribing to presence information, comprising the steps of:

A. The subscriber user sends a subscription request message to the instant message and presence service server;

B. The instant message and presence service server sends an authorization request message to the subscribed user according to the subscription request message;

C. After being confirmed by the subscribed user, send an authorization confirmation message to the instant message and presence service server;

D. If the instant message and presence service server receives the authorization confirmation message and indicates that it accepts the subscription, the instant message and presence service server sends a subscription success message to the subscriber user; otherwise, the instant message and presence service server judges the subscriber user Whether it is currently online, if the subscriber user is currently online, send a subscription failure message to the subscriber user, the subscription failure message includes the subscriber user information, and the subscriber user is at least one; if the subscriber user is not currently online , then discard the subscription failure message, or temporarily store the subscription failure message and send it to the subscriber user when he goes online again.

The subscribed user is one user or multiple users.

The format of the subscription failure message in step D is the format of the subscription success message that does not carry the existence information attribute, or is a self-defined format.

The reason information of the subscription failure is carried in the subscription failure message in the user-defined format.

The reason information of the subscription failure includes: the subscribed user responds overtime, or the subscribed user refuses to subscribe.

The subscription request message carries identification information for locating the subscribed user and information to be subscribed.

The subscribed user's presence information attribute value is carried in the subscription success message.

The beneficial effects of the present invention are as follows: the method of the present invention defines the format of the subscription failure message, and when the instant message and presence service server receives the authorization confirmation message sent by the subscribed user and indicates that the subscription is rejected, or the instant message and presence service When the server does not receive the authorization confirmation message from the subscribed user after a certain period of time, it will send a subscription failure message to the subscriber user, and may also carry the reason for the subscription failure in the subscription failure message, so that the subscriber user will receive the subscription failure message when the subscription fails. The subscription failure can be confirmed in time, and the reason for the subscription failure can be known, which can bring a good user experience to the user.

Description of drawings

FIG. 1 is a signaling flow chart of the existing information of subscription single users in the prior art;

FIG. 2 is a signaling flow chart of subscribing to multi-user presence information in the prior art;

Fig. 3 is a flow chart of the steps of subscribing to the existence information of single users in the method of the present invention;

Fig. 4 is a signaling flow chart of the method of the present invention for subscribing to the presence information of a single user;

Fig. 5 is a flow chart of the steps of subscribing to multi-user presence information by the method of the present invention;

Fig. 6 is a signaling flow chart of subscribing to multi-user presence information in the method of the present invention.

Detailed ways

In order to enable the subscriber user to determine whether the subscription is successful after performing the subscription operation, and to know the reason for the subscription failure when the subscription fails. The method of the present invention defines the format of the subscription failure message. When the subscribed user refuses to subscribe, or when the subscribed user does not respond after a certain period of time, the subscription failure message is sent to the subscriber user, and can be included in the subscription failure message. Carry the subscription failure reason, so that the subscriber user can confirm the subscription failure in time when the subscription fails, and can know the subscription failure reason. The process of the present invention's method of subscribing to the user's existence information is shown in Figure 3 and Figure 4, and its specific implementation steps are as follows:

S1. The subscriber user sends a subscription request message to the server.

First of all, both the subscriber user A and the subscribed user B are registered users of the IMPS service, otherwise, obviously the subscriber user A cannot enjoy this service, and similarly, there is no existence information attribute of the subscribed user B in the IMPS Server value records.

Under the above premise, when the subscriber user A wants to subscribe to the existence information of the subscribed user B, user A sends a subscription request message to the IMPS Server. The subscription request message carries identification information for locating user B and information to be subscribed.

S2. The server sends an authorization request message to the subscribed user.

Based on the identification information and subscription information carried in the subscription request message sent by user A, IMPS Server judges that user A's subscription operation is for user B, and learns what existence information user A wants to subscribe to user B.

According to the above information learned by the IMPS Server, an authorization request message is constructed, and the authorization request message is sent to user B. The authorization request message carries the existence information that user A wants to subscribe and the identification information of user A, so that user B can make a decision whether to agree to subscribe or not.

S3. The subscribed user sends an authorization confirmation message to the server.

User B makes a decision to accept or reject the subscription based on the identification information of user A carried in the authorization request message sent by IMPS Server and the information that user A wants to subscribe. And carry the decision in the authorization confirmation message and send it to IMPS Server.

S4. The IMPS Server judges whether the subscription is successful, and sends a subscription notification message.

If the IMPS Server receives the authorization confirmation message and indicates that it accepts the subscription, it determines that the subscription is successful. Afterwards, the IMPS Server sends a subscription success message to user A, in which the subscription success message carries the existence information attribute value of user B, that is, the relevant information that user A wants to know. So far the process is over.

If the IMPS Server does not receive the authorization confirmation message within a certain period of time after sending the authorization request message; or, the IMPS Server receives the authorization confirmation message, but indicates that it refuses to subscribe. It is determined that the subscription has failed.

Afterwards, IMPS Server judges whether user A is currently online. If user A is currently offline, IMPS Server has two processing methods:

Method 1: Discard the subscription failure message. In this way, the IMPS Server does not temporarily store the subscription failure message, and discards the subscription failure message directly after judging that user A is offline. Although this reduces the load on the IMPS Server and reduces the data processing capacity of the IMPS Server, if User A is offline at this time, he will not receive the subscription failure message, and cannot confirm whether the subscription is successful, which will affect the user experience.

Method 2: Temporarily store the subscription failure message. In this way, after judging that user A is offline, the IMPS Server temporarily stores the subscription failure message, and sends it to user A when it goes online again. The pros and cons of doing so are opposite to the one described above.

If user A is currently online, the IMPS Server sends a subscription failure message to user A. The format of the subscription failure message is different from that of the subscription success message. Its format is the format of the subscription success message already defined in the existing OMA standard specification, but the message body of the subscription success message does not carry any existence information attribute value to show that it is different from the subscription success message; or, Customize the format of the subscription failure message. As long as the difference from the subscription success message is satisfied, it should be within the protection scope of the present invention. In this way, the subscriber user (user A) can confirm the subscription failure in time when the subscription fails. The subscription failure message in the self-defined format may carry subscription failure reason information, and the subscription failure reason information includes: the subscriber user (user B) responds to timeout, the subscriber user rejects the subscription request, or other causes of subscription failure reason. In this way, the user can know what caused the subscription failure, and then decide whether it is necessary to subscribe again. For example, if the reason for the subscription failure is that the subscribed user's response timed out, the subscription request can be submitted again when the network is not busy. So far the process is over.

The process of subscribing to multi-user presence information by the method of the present invention is shown in Fig. 5 and Fig. 6 . Its specific implementation steps are as follows:

S1. The subscriber user sends a subscription request message to the server.

Firstly, the subscriber user A, the subscribed user B, and the subscribed user C are all registered users of the IMPS service.

Under the above premise, when the subscriber user A wants to subscribe to the existence information of the subscribed user B and the subscribed user C, user A sends a subscription request message to the IMPS Server. The subscription request message carries identification information for locating user B and user C, and information to be subscribed.

S2. The server sends an authorization request message to the subscribed user.

According to the identification information and subscription information carried in the subscription request message sent by user A, IMPS Server judges that the subscription operation of user A is for user B and user C, and learns that user A wants to subscribe user B and user C respectively Which information exists.

According to the above information learned by the IMPS Server, the authorization request messages are respectively constructed, and the corresponding authorization request messages are sent to user B and user C respectively. The authorization request message carries the existence information that user A wants to subscribe and the identification information of user A, so that user B and user C can decide whether to agree to subscribe or not.

S3. The subscribed user sends an authorization confirmation message to the server.

User B and user C make a decision to accept or reject the subscription according to the identification information of user A carried in the authorization request message sent by IMPS Server and the information that user A wants to subscribe. And carry the decision in the authorization confirmation message and send it to IMPS Server.

S4. The IMPS Server judges whether the subscription is successful, and sends a subscription notification message.

If the IMPS Server receives the authorization confirmation message from user B and indicates that it accepts the subscription, it determines that the subscription for user B is successful. Afterwards, the IMPS Server sends a subscription success message for user B to user A. The subscription success message carries the attribute value of user B's presence information, that is, the relevant information that user A wants to know.

If the IMPS Server does not receive the authorization confirmation message from user B within a certain period of time after sending the authorization request message; or, the IMPS Server receives the authorization confirmation message, but indicates that it refuses to subscribe. Then it is determined that the subscription for user B fails.

The IMPS Server judges whether the user A is currently online, and if the user A is currently offline, the IMPS Server discards the subscription failure message, or temporarily stores the subscription failure message.

If user A is currently online, the IMPS Server sends a subscription failure message for user B to user A. The format of the subscription failure message is different from that of the subscription success message. Its format is the format of the subscription success message already defined in the existing OMA standard specification, but the message body of the subscription success message does not carry any existence information attribute value to show that it is different from the subscription success message; or, Customize the format of the subscription failure message. As long as the difference from the subscription success message is satisfied, it should be within the protection scope of the present invention. In this way, the subscriber user can confirm the subscription failure in time when the subscription fails. The subscription failure message in the self-defined format may carry subscription failure reason information, and the subscription failure reason information includes: the subscribed user responds overtime, the subscribed user rejects the subscription request, or other reasons for subscription failure.

S5. The IMPS Server judges whether all the users targeted by user A have been processed. If it is judged that user C has not completed the processing, it waits for the processing result of user C, and after obtaining the processing result of user C, sends a subscription success message or subscription failure message for user A to user A. So far the process is over.

The IMPS Server may not immediately send a subscription failure message to the subscriber user when it determines that a certain subscribed user refuses to subscribe, but determines that several subscribed users refuse to subscribe, or determines that the processing of each subscribed user is not valid. When it has ended, several subscription failure messages, or related information of all subscription failure messages are included in a subscription notification message, and then sent to the subscriber user.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (7)

1. A method for subscribing to presence information, comprising the following steps: A. The subscriber user sends a subscription request message to the instant message and presence service server; B. The instant message and presence service server sends an authorization request message to the subscribed user according to the subscription request message; C. The subscribed user confirms whether to accept the subscription, and returns the confirmation result to the instant message and presence service server; D. If the confirmation result shows that the subscription is accepted, the instant message and presence service server sends a subscription success message to the subscriber user; otherwise, the instant message and presence service server judges whether the subscriber user is currently online; if the subscriber user is currently online, Then send a subscription failure message to the subscriber user, the subscription failure message includes the subscriber user information, the subscriber user is at least one; if the subscriber user is not currently online, then discard the subscription failure message, or temporarily Save the subscription failure message, and send it to the subscriber user when he goes online again. 2. The method according to claim 1, wherein the subscribed user is one user or multiple users. 3. The method according to claim 2, wherein the format of the subscription failure message in step D is the format of the subscription success message that does not carry the existence information attribute, or is a self-defined format. 4. The method according to claim 3, characterized in that, the reason information of subscription failure is carried in the subscription failure message in the user-defined format. 5. The method according to claim 4, wherein the reason information of the subscription failure includes: the subscribed user responds overtime, or the subscribed user refuses to subscribe. 6. The method according to claim 1, wherein the subscription request message carries identification information for locating the subscribed user and information to be subscribed. 7. The method according to claim 1, wherein the subscription success message carries the attribute value of the existence information of the subscribed user.

Images