System and Method of Updating Presence Information

• US 20080214170A1
• Filed: 01/10/2008
• Published: 09/04/2008
• Est. Priority Date: 01/10/2007
• Status: Active Grant

• Current Assignee: Synchronica PLC (Myriad Group AG)
• Original Assignee: OZ Communications Incorporated (Nokia Corporation)
• Inventors: Legault, Sylvain, Maiorano, Nick, Southiere, Alain, Laflamme, Manuel
• Granted Patent: US 8,078,191 B2
• Time in Patent Office: Days
• US Class Current: 455/418
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 51/043 using or handling presence information
• 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
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/5651 Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04M 3/42374 where the information is provided to a monitoring entity such as a potential calling party or a call processing server

Abstract

A network node provides presence updates to mobile users. The node reduces the amount of network traffic by eliminating the need for explicit messaging used to inform a user of presence updates. Additionally, the node reduces network traffic by consolidating presence updates, and sending the user only changed portions of the presence information.

Claims

1. A method of providing presence updates to a client, the method comprising:

consolidating presence updates received from a presence server to create a consolidated presence update; and

sending the consolidated presence update to the client responsive to receiving an unsolicited client request for presence information.

2. The method of claim 1 wherein consolidating presence updates comprises accumulating state transitions for one or more presence attributes to determine a final state for said presence attributes, and including only the final state for said presence attributes in the consolidated presence update.

3. The method of claim 2 wherein consolidating presence updates further comprises remembering the last reported state for said presence attributes, comparing the final state of each presence attribute to the last reported state, and including presence attributes in the consolidated presence update only if the final state is different from the last reported state.

4. The method of claim 1 wherein the unsolicited client request comprises a fetch request.

5. The method of claim 1 wherein the unsolicited client request comprises a polling request.

6. The method of claim 1 further comprising subscribing to receive presence updates for a client in response to a request from the client.

7. The method of claim 6 wherein subscribing to receive presence updates for a client is responsive to a subscription request from the client.

8. The method of claim 6 wherein subscribing to receive presence updates for a client is responsive to a fetch request from the client.

9. A network node comprising:

a communication port configured to receive a client request for presence information; and

a controller configured to;

consolidate presence updates received from a presence server to create a consolidated presence update; and

receive an unsolicited client request for presence information; and

send the consolidated presence update to the client responsive to the unsolicited client request.

10. The network node of claim 9 wherein the controller is further configured to:

accumulate state transitions for one or more presence attributes to determine a final state for said presence attributes; and

include only the final state for said presence attributes in the consolidated presence update.

11. The network node of claim 10 wherein the controller is further configured to:

remember the last reported state for said presence attributes;

compare the final state of each presence attribute to the last reported state; and

include the presence attributes in the consolidated presence update only if the final state is different from the last reported state.

12. The network node of claim 9 wherein the unsolicited client request comprises a fetch request.

13. The network node of claim 9 wherein the unsolicited client request comprises a polling request.

14. The network node of claim 9 wherein the controller is further configured to subscribe to receive the presence updates for the client in response to the client request.

15. The network node of claim 14 wherein the controller is further configured to subscribe to the presence server to receive the presence updates responsive to receiving a fetch request from the client.

16. The network node of claim 14 wherein the controller is further configured to subscribe to the presence server to receive the presence updates responsive to receiving a subscription request from the client.

17. The network node of claim 9 wherein the controller is further configured to add new presence attributes to the consolidated presence update.

18. A method of providing presence updates to a client, the method comprising:

accumulating state transitions for one or more presence attributes of a presentity to determine a final state for the presence attributes; and

sending a consolidated presence update to the client, the consolidated presence update including only the final state for said presence attributes.

19. The method of claim 18 wherein accumulating state transitions for one or more presence attributes comprises:

remembering the last reported state for the presence attributes;

comparing the final state of each presence attribute to the last reported state; and

including presence attributes in the consolidated presence update only if the final state is different from the last reported state.

20. The method of claim 18 further comprising receiving an unsolicited client request for presence information and wherein sending the consolidated presence update to the client is responsive to the unsolicited client request.

21. The method of claim 20 wherein the unsolicited client request comprises a fetch request.

22. The method of claim 20 wherein the unsolicited client request comprises a polling request.

23. The method of claim 18 further comprising subscribing to receive presence updates for the client in response to a request from the client.

24. The method of claim 23 wherein subscribing to receive presence updates for a client is responsive to a subscription request from the client.

25. The method of claim 23 wherein subscribing to receive presence updates for a client is responsive to a fetch request from the client.

26. A network node comprising:

a communication port configured to receive a client request for presence information; and

a controller configured to;

accumulate state transitions for one or more presence attributes of a presentity to determine a final state for the presence attributes; and

send a consolidated presence update to the client, the consolidated presence update including only the final state for said presence attributes.

27. The network node of claim 26 wherein the controller is further configured to:

remember the last reported state for the presence attributes;

compare the final state of each presence attribute to the last reported state; and

include the presence attributes in the consolidated presence update only if the final state is different from the last reported state.

28. The network node of claim 26 wherein the client request for presence information comprises an unsolicited client request for presence information, and wherein the controller is configured to send the consolidated presence update to the client responsive receiving to the unsolicited client request.

29. The network node of claim 28 wherein the unsolicited client request comprises a fetch request.

30. The network node of claim 28 wherein the unsolicited client request comprises a polling request.

31. The network node of claim 26 wherein the controller is further configured to subscribe to receive the presence updates for the client in response to the client request.

32. The network node of claim 31 wherein the controller is further configured to subscribe to the presence server to receive the presence updates responsive to receiving a fetch request from the client.

33. The network node of claim 31 wherein the controller is further configured to subscribe to the presence server to receive the presence updates responsive to receiving a subscription request from the client.

34. The network node of claim 26 wherein the controller is further configured to add new presence attributes to the consolidated presence update.