METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR PROVIDING PRESENCE DATA FROM MULTIPLE PRESENCE INFORMATION PROVIDERS

• US 20100017472A1
• Filed: 06/15/2009
• Published: 01/21/2010
• Est. Priority Date: 06/13/2008
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Benedyk, Robby, Marsico, Peter J.
• Granted Patent: US 8,903,903 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 51/043 using or handling presence information
• CPC Class Codes: H04L 51/222 using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
• 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

Methods, systems, and computer readable medium for providing presence data from multiple presence information providers are disclosed. According to one aspect, the subject matter described herein includes a method for providing presence service using presence information from multiple presence information providers. The method includes, at a network node including at least one processor, receiving, from a message source, a first presence-related message that includes information identifying a user, using the information identifying a user to identify, from multiple presence information providers, a presence information provider that maintains presence information associated with the identified user, and relaying the first presence-related message to the identified presence information provider or sending a second presence-related message associated with the first presence-related message to the identified presence information provider.

Claims

1. A method for providing presence service using presence information from a plurality of presence information providers, the method comprising:

at a network node including at least one processor;

receiving, from a message source, a first presence-related message that includes information identifying a user;

using the information identifying a user to identify, from a plurality of presence information providers, a presence information provider that maintains presence information associated with the identified user; and

relaying the first presence-related message to the identified presence information provider or sending a second presence-related message associated with the first presence-related message to the identified presence information provider.

2. The method of claim 1 wherein relaying the first presence-related message includes one of:

forwarding the first presence-related message without modification; and

modifying the first presence-related message and forwarding the modified presence-related message.

3. The method of claim 1 comprising receiving, from the identified presence information provider, a third presence-related message that includes presence information associated with the identified user and, in response to receiving the third presence-related message, one of:

relaying the third presence-related message to the message source; and

correlating the third presence-related message to the second presence-related message and communicating to the message source the presence information associated with the identified user.

4. The method of claim 1 wherein the first presence-related message comprises one of a session initiation protocol (SIP) message, a session initiation protocol for instant messaging and presence leveraging extensions (SIMPLE) message, and an extensible messaging and presence protocol (XMPP) message.

5. The method of claim 1 wherein the first presence-related message comprises one of a presence registration request, a presence status update message, a presence status query, and a presence subscription request.

6. The method of claim 3 wherein the third presence-related message comprises one of a presence registration request response, a presence status update message response, a presence status query response, and a presence subscription request response.

7. The method of claim 3 wherein the identity of the presence information provider is hidden from and not communicated to the message source.

8. The method of claim 1 wherein identifying the presence information provider includes using E.164 number (ENUM) translation to determine an address of the presence information provider containing presence information associated with the identified user.

9. The method of claim 1 comprising, in response to receiving the first presence-related message, at least one of:

performing an authentication function;

performing an authorization function;

administering service level agreements between a plurality of network operators;

performing an accounting function;

performing a billing function;

performing a billing verification function;

performing a usage measurements function;

performing a protocol conversion function;

performing a network interworking function;

performing a protocol translation function; and

performing an address translation function.

10. The method of claim 1 wherein the plurality of presence information providers is managed by a same network operator.

11. The method of claim 1 wherein the plurality of presence information providers is managed by a plurality of network operators.

12. The method of claim 1 wherein the plurality of presence information providers comprises at least one presence database entity.

13. The method of claim 1 wherein at least one of the plurality of presence information providers comprises a presence server for maintaining presence information for groups of users.

14. The method of claim 1 wherein the first presence-related message is addressed to the network node.

15. A method for providing presence service using presence information from a plurality of network service providers, the method comprising:

at a network node including at least one processor;

maintaining a collection of user presence data collected from a plurality of network service providers;

receiving, from a message source, a first presence-related message that includes information identifying a user;

in response to receiving the first presence-related message, determining whether presence information associated with the identified user exists in the collection of user presence data;

in response to a determination that presence information associated with the identified user exists in the collection of user presence data, retrieving the presence information associated with the identified user and sending, to the message source, a second presence-related message that includes the presence information associated with the identified user.

16. The method of claim 15 comprising in response to a determination that presence information associated with the identified user does not exist in the collection of user presence data, sending a query to at least one of the plurality of network service providers for presence information associated with the identified user, and, in response to receiving a reply to the at least one query, the reply including presence information associated with the identified user, sending to the message source a second presence-related message that includes the presence information associated with the identified user.

17. The method of claim 16 comprising, in response to receiving a reply to the at least one query, storing in the collection of presence data the presence information associated with the identified user.

18. The method of claim 15 wherein the first presence-related message comprises one of a session initiation protocol (SIP) message, a session initiation protocol for instant messaging and presence leveraging extensions (SIMPLE) message, and an extensible messaging and presence protocol (XMPP) message.

19. The method of claim 15 wherein the first presence-related message comprises one of a presence registration request, a presence status update message, a presence status query, and a presence subscription request.

20. The method of claim 15 comprising, in response to receiving the first presence-related message, at least one of:

performing an authentication function;

performing an authorization function;

administering service level agreements between a plurality of network operators;

performing a firewall function;

performing an accounting function;

performing a billing function;

performing a billing verification function;

performing a usage measurements function;

performing a protocol conversion function;

performing a network interworking function;

performing a protocol translation function; and

performing an address translation function.

21. The method of claim 15 wherein maintaining the collection of user presence data includes receiving presence status update messages from the plurality of network service providers.

22. The method of claim 15 wherein maintaining the collection of user presence data includes using a database to store and retrieve presence data associated with users of the plurality of network service providers.

23. The method of claim 22 wherein using a database to store and retrieve presence data includes using a database co-located with the network node.

24. The method of claim 22 wherein using a database to store and retrieve presence data includes using a database not co-located with the network node.

25. The method of claim 24 wherein the network node accesses the database using at least one of a transaction capabilities application part (TCAP) protocol, a mobile application part (MAP) protocol, a simple object access protocol (SOAP), an extended markup language (XML) protocol, a hypertext transfer protocol (HTTP), and a session initiation protocol (SIP).

26. The method of claim 15 wherein at least one of the plurality of network service providers includes a presence server for maintaining presence information for groups of users.

27. A network entity for providing presence service using presence information from a plurality of presence information providers, the network entity comprising:

a communications network interface for receiving, from a message source, a first presence-related message that includes information identifying a user; and

a presence service module, implemented by at least one processor, for receiving the first presence-related message from the communications network interface, using the information identifying a user to identify, from a plurality of presence information providers, a presence information provider that maintains presence information associated with the identified user, and relaying the first presence-related message to the identified presence information provider or sending a second presence-related message associated with the first presence-related message to the identified presence information provider.

28. The network entity of claim 27 wherein relaying the first presence related message includes one of:

forwarding the first presence-related message without modification; and

modifying the first presence-related message and forwarding the modified presence-related message.

29. The network entity of claim 27 wherein, in response to receiving, from the identified presence information provider, a third presence-related message that includes presence information associated with the identified user, the presence service module performs one of:

relaying the third presence-related message to the message source; and

correlating the third presence-related message to the second presence-related message and communicating the presence information associated with the identified user to the message source.

30. The network entity of claim 27 wherein the first presence-related message comprises one of a session initiation protocol (SIP) message, a session initiation protocol for instant messaging and presence leveraging extensions (SIMPLE) message, and an extensible messaging and presence protocol (XMPP) message.

31. The network entity of claim 27 wherein the first presence-related message comprises one of a presence registration request, presence status update message, a presence status query, and a presence subscription request.

32. The network entity of claim 29 wherein the third presence-related message comprises one of a registration request response, a presence status update response, a presence status query response, and a presence subscription request response.

33. The network entity of claim 29 wherein the presence service module hides the identity of the presence information provider from the message source and does not communicate the identity of the presence information provider to the message source.

34. The network entity of claim 27 wherein the presence service module identifies the presence information provider by using E.164 number (ENUM) translation to determine an address of the presence information provider containing presence information associated with the identified user.

35. The network entity of claim 27 wherein the network entity comprises one of a session initiation protocol (SIP) router, a SIP application server (SAS), a signal transfer point (STP), and a service control point (SCP).

36. The network entity of claim 27 wherein the network entity is configured to, in response to receiving the first presence-related message, at least one of:

perform an authentication function;

perform an authorization function;

administer service level agreements between a plurality of network operators;

perform an accounting function;

perform a billing function;

perform a billing verification function;

perform a usage measurements function;

perform a protocol conversion function;

perform a network interworking function;

perform a protocol translation function; and

perform an address translation function.

37. The network entity of claim 27 comprising a presence routing database (PRDB) for maintaining information used by the presence service module to identify, from a plurality of presence information providers, a presence information provider that maintains presence information associated with the identified user.

38. A universal presence server for providing presence service using presence information from a plurality of network service providers, the universal presence server comprising:

a presence information database for storing and maintaining presence information collected from a plurality of network service providers; and

a universal presence service module, implemented by at least processor, for;

receiving, from a message source, a first presence-related message that includes information identifying a user;

in response to receiving the first presence-related message, determining whether presence information associated with the identified user exists in the presence information database;

in response to a determination that presence information associated with the identified user exists in the presence information database, retrieving the presence information associated with the identified user and sending to the message source a second presence-related message that includes the presence information associated with the identified user.

39. The universal presence server of claim 38 wherein, in response to a determination that presence information associated with the identified user does not exist in the presence information database, the universal presence service module sends a query for presence information associated with the identified user to at least one of the plurality of network service providers, and wherein, in response to receiving the requested presence information associated with the identified user, the universal presence service module communicates the requested presence information to the message source.

40. The universal presence server of claim 39 wherein, in response to receiving the requested presence information associated with the identified user, the universal presence module stores the requested presence information in the presence information database.

41. The universal presence server of claim 38 wherein the first presence-related message comprises one of a session initiation protocol (SIP) message, a session initiation protocol for instant messaging and presence leveraging extensions (SIMPLE) message, and an extensible messaging and presence protocol (XMPP) message.

42. The universal presence server of claim 38 wherein the first presence-related message comprises one of a presence registration request, a presence status update message, a presence status query and a presence subscription request.

43. The universal presence server of claim 38 wherein the universal presence server comprises one of a session initiation protocol (SIP) router, a SIP application server (SAS), a signal transfer point (STP), and a service control point (SCP).

44. The universal presence server of claim 38 wherein the universal presence service module is configured to, in response to receiving the first presence-related message, at least one of:

perform an authentication function,

perform an authorization function;

administer service level agreements between a plurality of network operators;

perform an accounting function;

perform a billing function;

perform a billing verification function;

perform a usage measurements function;

perform a protocol conversion function;

perform a network interworking function;

perform a protocol translation function; and

perform an address translation function.

45. The universal presence server of claim 38 wherein maintaining presence information collected from the plurality of network service providers includes receiving presence status update messages from the plurality of network service providers and updating the presence information stored in the presence information database.

46. The universal presence server of claim 38 wherein the presence information database is co-located with the universal presence service module.

47. The universal presence server of claim 38 wherein the presence information database is not co-located with the universal presence service module.

48. The universal presence server of claim 47 wherein the universal presence server is configured to access the presence information database using at least one of a transaction capabilities application part (TCAP) protocol, a mobile application part (MAP) protocol, a simple object access protocol (SOAP), an extended markup language (XML) protocol, a hypertext transfer protocol (HTTP), and a session initiation protocol (SIP).

49. A computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps comprising:

at a network node in a telecommunication network;

receiving, from a message source, a first presence-related message that includes information identifying a user;

using the information identifying a user to identify, from a plurality of presence information providers, a presence information provider that maintains presence information associated with the identified user; and

relaying the first presence-related message to the identified presence information provider or sending a second presence-related message associated with the first presence-related message to the identified presence information provider.

50. A computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps comprising:

at a network node in a telecommunication network;

maintaining a collection of user presence data collected from a plurality of network service providers;

receiving, from a message source, a first presence-related message that includes information identifying a user;

in response to receiving the first presence-related message, determining whether presence information associated with the identified user exists in the collection of user presence data;

in response to a determination that presence information associated with the identified user exists in the collection of user presence data, retrieving the presence information associated with the identified user and sending a second presence-related message to the message source, the second presence-related message that includes the presence information associated with the identified user.