METHOD AND SYSTEM FOR PROVIDING PRESENCE INFORMATION

• US 20080098297A1
• Filed: 11/26/2007
• Published: 04/24/2008
• Est. Priority Date: 05/26/2006
• Status: Abandoned Application

• Current Assignee: Chenghui Peng, Hongging Bao, Linyi Tian, Qian Sun, Xuefei Song, Yan Zhao
• Original Assignee: Chenghui Peng, Hongging Bao, Linyi Tian, Qian Sun, Xuefei Song, Yan Zhao
• Inventors: Bao, Hongging, Tian, Linyi, Zhao, Yang, Peng, Chenghui, Song, Xuefei, SUN, Qian
• Application Number:
  US11/945,088
• Publication Number:
  US 20080098297A1
• Time in Patent Office: Days
• US Class Current: 715/234
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users

Abstract

The present invention discloses a method for providing presence information, including: setting a validity period of the presence information; publishing, by a presentity client, the received presence information and the validity period to a presence server; and distributing the received presence information and the validity period to a watcher client by the presence server. Thus, the watcher client knows the validity period of the presence information, such as an end time of a current presence time, and thereby selects timely an appropriate time for communication with the presentity client. Furthermore, the present invention also provides a start time of the current presence information, and thus the watcher client knows a duration of the current presence information of the presentity client. The present invention further discloses a system for providing presence information.

Claims

1. A method for providing presence information, comprising:

publishing, by a presentity client, presence information and a validity period of the presence information to a presence server; and

receiving, by a watcher client, the presence information and the validity period distributed by the presence server.

2. The method according to claim 1, further comprises:

setting the validity period for the presence information; and

setting an end time of the presence information as the validity period of the presence information, the presence information being current presence information of the presentity client.

3. The method according to claim 1, further comprises:

setting a start time of the presence information as the validity period or a period corresponding to the start time and the end time of the presence information as the validity period and associating the validity period with the future presence information;

the presence information being a future presence information of the presentity client,

4. The method according to claim 1, wherein the presence information is contained in an XML document, and the validity period is set in an attribute of a corresponding presence information element, or in an element parallel to the corresponding presence information element, or in a sub-element of the corresponding presence information element.

5. The method according to claim 4, further comprising:

setting text note information corresponding to the validity period for the presence information; and

publishing, by the presentity client, the presence information, the validity period, and the corresponding text note information to the presence server;

distributing, by the presence server, the received presence information, the validity period, and the corresponding text note information to the watcher client; and

receiving and displaying, by the watcher client, the presence information, the validity period, and the corresponding text note information of the presentity client.

6. The method according to claim 4, wherein, when aggregating the same presence information elements with identical values received from one presentity client, reserving, by the presence server or the watcher client, the same presence information with different attributes of the validity period.

7. The method according to claim 2, further comprising:

when the presence server or the watcher client detects that the end time of the validity period corresponding to the presence information is earlier than current time, deleting the validity period.

8. The method according to claim 1, wherein:

a start time of current presence information of the presentity client is distributed along with the corresponding presence information to the watcher client.

9. The method according to claim 8, wherein the watcher client displays the current presence information of the presentity client and the start time of the current presence information.

10. The method according to claim 8, wherein the watcher client displays the current presence information of the presentity client and a duration of the current presence information, the duration being obtained by the watcher client from a difference between a current time and the start time.

11. A method for providing presence information, comprising:

publishing, by a presentity client, the presence information to a presence server; and

distributing, by the presence server, current presence information of the presentity client and a start time of the current presence information to a watcher client.

12. The method according to claim 11, wherein the start time is obtained through the steps of:

comparing, by the presence server, the received current presence information published by the presentity client with presence information of the presentity client stored on the presence server; and

if the received current presence information and the presence information of the presentity client are different or the presence server has stored no presence information of the presentity client, taking and storing a current time as the start time of the presence information;

otherwise,

reserving a stored start time of the presence information.

13. The method according to claim 11, wherein the start time is set by the presentity client and is published along with the corresponding presence information to the presence server.

14. The method according to claim 13, wherein, publishing, by the presentity client, music or video information played locally as the presence information and the start time for playing to the presence server;

and playing, by the watcher client, a corresponding music or video or displaying a music lyrics or a video subtitle synchronously after receiving the music information or video information and the start time.

15. The method according to claim 14, wherein, using the time information in a message sent from the presence server, calculating, by the presentity client, the start time, and calculating, by the watcher client, a corresponding duration.

16. The method according to claim 11, wherein the presence information is contained in an XML document and the start time is set in an attribute of a corresponding presence information element, or in an element parallel to a corresponding presence information element, or in a sub-element of a corresponding presence information element.

17. The method according to claim 11, further comprising:

displaying, by the watcher client, both the current presence information and the start time of the presentity client.

18. A system for providing presence information, comprising a presence server, a presentity client, and a watcher client, wherein:

the presentity client is adapted to publish the presence information and the validity period of the presence information to the presence server;

the presence server is adapted to distribute the received presence information and the validity period of the presence information to a watcher client; and

the watcher client is adapted to receive the presence information of the presentity client and the validity period of the presence information.

19. A method for providing event history information, comprising:

recording event information;

receiving a request for obtaining event history information sent by a client, the request being a SIP (Session Initiation Protocol) SUBSCRIBE request and the SUBSCRIBE request comprising an indication for obtaining event history information and a time parameter;

obtaining, by the server, recorded corresponding event history information, according to the indication and the time parameter in the SUBSCRIBE request; and

sending, by the server, the event history information to the client through a SIP NOTIFY message.

20. The method according to claim 19, wherein, a filter in a message body of the SUBSCRIBE request comprises the time parameter for determining a duration range of the event history information;

or, an event head filed of the SUBSCRIBE request comprises the time parameter.

21. The method according to claim 19, wherein, an element or an attribute node whose event history information is to be obtained is indicated with an XPath in the SUBSCRIBE request message.

22. The method according to claims 19, wherein, a NOTIFY message body sent by the server comprises a node identifier for an event information element, at least one corresponding event information value, and a start time and/or an end time corresponding to each event information value.

23. The method according to claim 19, wherein, the time parameter in the request indicates the event history information at a specified time point to be obtained, and the event history information sent by the server further comprises an actual start time and/or end time of the event history information at the specified time point.

24. The method according to claim 19, wherein, when the server receives the request for obtaining the event history information sent by the client and determines that the history information of current event status is to be obtained, the server sends a start time corresponding to current event status to a requesting client.

25. A method for providing a start time of event information, comprising:

recording, the start time of the event information;

receiving, a request for obtaining event history information sent by a client, the request being a SIP (Session Initiation Protocol) SUBSCRIBE request and an event head field in the SUBSCRIBE request comprising an indication for obtaining a start time of the event information, and a message body comprising a node identifier of the event information;

obtaining, by the server, the start time of corresponding event information according to the SUBSCRIBE request; and

sending, by the server, the start time of the corresponding event information to the client through a SIP NOTIFY message.