Source: https://patents.google.com/patent/US8903903B2/en
Timestamp: 2018-09-25 22:16:32
Document Index: 736693929

Matched Legal Cases: ['Application No. 200680049126', 'Application No. 06826548', 'Application No. 06', 'application No. 08153801', 'Application No. 08', 'Application No. 2580', 'Application No. 09763799', 'Application No. 2580', 'Application No. 2580', 'Application No. 200680049126', 'Application No. 05725442', 'Application No. 05725463', 'Application No. 09763799', 'Application No. 200680049126', 'application No. 05725442']

US8903903B2 - Methods, systems, and computer readable media for providing presence data from multiple presence information providers - Google Patents
Methods, systems, and computer readable media for providing presence data from multiple presence information providers Download PDF
US8903903B2
US8903903B2 US12484857 US48485709A US8903903B2 US 8903903 B2 US8903903 B2 US 8903903B2 US 12484857 US12484857 US 12484857 US 48485709 A US48485709 A US 48485709A US 8903903 B2 US8903903 B2 US 8903903B2
US12484857
US20100017472A1 (en )
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.
This application claims the benefit of U.S. Provisional Patent Application Ser. Nos. 61/061,425, 61/061,464, and 61/061,477, each filed on Jun. 13, 2008, and the disclosures of which are incorporated herein by reference in their entireties.
The subject matter described herein relates to communicating presence information in a computer network. More particularly, the subject matter described herein relates to methods, systems, and computer readable media for providing presence data from multiple presence information providers.
In computer networks, presence information is used to indicate a user's ability and/or willingness to communicate with other users, typically expressed as a “status”. More precisely, however, presence information consists of an arbitrary number of elements, called presence tuples, where a tuple is a data object containing two or more components. Each presence tuple may consist of a status marker, an optional communication address, and an optional presence markup. Common presence status markers indicating the user's availability to communicate may include “online”, “offline”, “busy”, “away”, or “do not disturb”. Presence information may also include positional or geolocation information, such as the current Cartesian coordinates or global positioning system (GPS) coordinates of a presentity. An optional communication address may include both a communication means and a contact address for the user. According to RFC 2778, one type of communication means defined by the presence information model is instant message (IM) service and one type of contact address is an instant inbox instant messaging systems, such as AOL, ICQ, MSN, and Google. Other types of communication means and contact addressed for use in a presence tuple may include various forms of telephony and telephone numbers.
Presence information may be managed via a presence client operating on the user's computer. Presence clients may send presence information via a network connection to a presence service, which stores the presence information to make it available for distribution to other users. For example, a presence service may store presence information for multiple users in one or more presence information databases. Presence information databases may distribute presence information to users within the same presence network or across network boundaries to users associated with other presence services. It is appreciated that a single human user may be associated with multiple presence services. This may be accomplished, for example, by operating multiple presence clients where each presence client is associated with a different presence service or, alternatively, by operating a multi-service presence client. When a user belongs to multiple presence services, each presence service may independently maintain presence information for the user. Accordingly, synchronization of presence information across multiple presence services is not required (i.e., a user may be both “online” in AOL and “away” in MSN).
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.
According to yet another aspect, the subject matter described herein includes a universal presence server for providing presence service using presence information from a plurality of network service providers. The universal presence server includes a presence information database for storing and maintaining presence information collected from a plurality of network service providers and a universal presence service module that is implemented by at least one processor. The universal presence service module receives from a message source a first presence-related message that includes information identifying a user, and, in response to receiving the first presence-related message, determines 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, the universal presence service module retrieves the presence information associated with the identified user and sends to the message source a second presence-related message that includes the presence information associated with the identified user.
The subject matter described herein for providing presence service using presence information from a plurality of presence information providers may be implemented in hardware, software, firmware, or any combination thereof. As such, the terms “function” or “module” as used herein refer to hardware, software, and/or firmware for implementing the feature being described. In one exemplary implementation, the subject matter described herein may be implemented using a computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps. Exemplary computer readable media suitable for implementing the subject matter described herein include disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
In accordance with the subject matter disclosed herein, systems, methods, and computer readable media are provided for providing presence service using presence information from a plurality of presence information providers.
FIG. 1A is a block diagram illustrating a network entity for providing presence service using presence information from a plurality of presence information providers according to an embodiment of the subject matter described herein. Referring to FIG. 1A, network entity (NE) 100 includes a communications network interface (CNI) 102 for sending and receiving messages having a message source and including information identifying a user and a presence service module (PSM) 104, which receives presence-related messages from CNI 102 and uses the information identifying a user to identify, from multiple presence information providers (PIP) 106, a presence information provider (PIP) that maintains presence information associated with the identified user. A presence information provider may be an entity that provides or maintains presence information for one or more users, such as a presence server. In the embodiment illustrated in FIG. 1A, the presence-related messages may be session initiation protocol (SIP) messages, but in other embodiments, presence-related messages of other protocols may be used, including session initiation protocol for instant messaging and presence leveraging extensions (SIMPLE) messages, extensible messaging and presence protocol (XMPP) messages, and others. In one embodiment, presence service module 104 may be implemented by one or more processors, which may be executing suitable software or firmware programs. In one embodiment, the presence service providers may be presence servers.
In the embodiment illustrated in FIG. 1A, NE 100 functions as a presence service relay, and relays a first presence-related message (FIG. 1A, message 1, hereinafter “M1”) to the identified presence information provider, which sends an acknowledgement message (FIG. 1A, message 2, hereinafter “M2”) to the sender of the first message. In this embodiment, NE 100 may be said to be operating in presence relay mode. In presence relay mode, the acknowledgement message is not sent to NE 100, but to the sender of the original message M1. In one embodiment, NE 100 may forward message M1 without modification. In an alternative embodiment, NE 100 may modify the original message M1, such as by changing the destination of the original message from NE 100 to the target presence information provider, e.g., PIP 106C, and forward the modified message to the target presence information provider. The operation of NE 100 in presence relay mode will be described in more detail in FIG. 3, below.
In the embodiment illustrated in FIG. 1B, NE 100 functions as a presence service proxy, which receives a first presence-related message (FIG. 1B, message 3, hereinafter “M3”) and then sends a second presence-related message associated with the first presence-related message (FIG. 1B, message 4, hereinafter “M4”) to the identified presence information provider. In this embodiment, NE 100 may be said to be operating in presence proxy mode.
In this embodiment, NE 100 receives an ACK message (FIG. 1B, message 5, hereinafter “M5”) in response to M4, and then sends another ACK message (FIG. 1B, message 6, hereinafter “M6”) to the sender of the first message. NE 100 may send M6 either before or after NE 100 has received M5. For example, in one embodiment, NE 100 sends M6 immediately after receiving M3. This may be appropriate where M3 is a subscription request or other message that requires a simple ACK to acknowledge receipt of the subscription request or presence information query. In an alternative embodiment, NE 100 may wait for the receipt of M5 before sending out M6. This may be appropriate where M3 is a request for status or other message that expects more than just an ACK, but instead expects some specific data in return.
At block 200, a first presence-related message is received at a network entity for processing presence-related messages. The first presence-related message is received from a message source and includes information identifying a user. For example, message M1 in FIG. 1A is a presence query sent from message source PIP 106A to NE 100. M1 may be a request to subscribe to receive presence information for a user that happens to be a subscriber to network B 110B. M1 may include the name of the user or other information that identifies the user.
At block 206, NE 100 is operating in presence proxy mode and therefore sends a second presence-related message associated with the first presence related message to the identified presence information provider. For example, referring to FIG. 1B, NE 100 may receive a first presence-related message (e.g., M3) that includes information identifying a user that is a subscriber of network B 110B, and send a second presence-related message (e.g., M4) that is associated with the first presence-related message (e.g., M3) to the identified presence information provider (e.g., 106C.) PIP 106C may respond to M4 by sending a response message (e.g., ACK M5) to NE 100. NE 100 may respond to M3 by sending a response message (e.g., ACK M6) to the message source (e.g., PIP 106A).
FIG. 3 is a message flow diagram (ladder diagram) illustrating signaling messages exchanged between an exemplary network element 100 operating in presence relay mode according to an embodiment of the subject matter described herein. Elements within FIG. 3 correspond to like-numbered elements within FIG. 1A, and their description will therefore not be repeated here. For brevity and ease of explanation, presence information providers 106A, 106B, and 106C are hereinafter respectively referred to as “A”, “B”, and “C”, and NE 100 operating in presence relay mode is hereinafter referred to as “R”. For the purposes of this example, A maintains presence information for subscribers Alice and Andy. B maintains presence information for subscribers Bob and Brenda. C maintains presence information for subscribers Carrie and Chuck. The messages and events illustrated in FIG. 3 will now be described with reference to FIGS. 1 and 3.
At 300, a presence-related message sent from A to R. A subscriber within network A 110A, “Alice”, requests a subscription to presence-related information regarding user “Bob”. The message contains source and destination fields, identified as “S” and “D”, respectively. In this example, message 300 indicates that the message came from Alice@A and is addressed to R. At 302, R determines which of A, B, and C maintains presence-related information for Bob, and determines that Bob's presence information is maintained by B. At 304, R relays to B the presence-related message that it received from A, after first modifying the message by changing the value of the destination field from R to B. At 306, B receives the relayed message. Since the message is a request to subscribe Alice@A to receive updates of Bob's presence status, B adds Alice@A to the list of subscribers to be notified of changes to Bob's presence status, referred to as Bob's “notify list”. At 308, B sends an ACK message back to the original source of the message, Alice@A.
At 310, another subscriber, Brenda@B, sends a request to subscribe to presence information associated with a user named “Carrie”. The request is sent from B to R. At 312, R determines that user Carrie is a subscriber of C, i.e., Carrie's presence information is maintained by C. At 314, R relays to C the presence-related message that it received from B, after first changing the destination field from R to C. At 316, C receives the relayed message. Since the message is a request to subscribe Brenda@B to receive updates of Carrie's presence status, C adds Brenda@B to Carrie's notify list. At 318, C sends an ACK message to Brenda@B.
FIG. 4 is a message flow diagram (ladder diagram) illustrating signaling messages exchanged between an exemplary network element 100 operating in presence proxy mode according to an embodiment of the subject matter described herein. For brevity, NE 100 operating in presence proxy mode will hereinafter be referred to as “P”. Presence information providers 106A, 106B, and 106C will continue to be respectively referred to as “A”, “B”, and “C”.
Note that in the embodiments illustrated in FIG. 4, P terminates each received message. That is, P responds to received messages with an ACK to the sender of the message. In the embodiments illustrated in FIG. 4, P terminates each message received before proxying each message forward to the intended destination. For example, P receives subscription request 400 and sends ACK 406 back to A before proxying the subscription request 408 forward to B. Likewise, P receives presence status update message 418 and sends an ACK 420 to B before proxying the update message 424 forward to A.
In one embodiment, universal presence server 500 may include a universal presence service module 504 for receiving, from a message source, a first presence-related message, such as message 1 in FIG. 5, that includes information identifying a user, and in response to receiving the first presence-related message, determining whether presence information associated with the identified user exists in PIDB 502. If presence information associated with the identified user exists in PIDB 502, universal presence service module 504 may retrieve the presence information associated with the identified user, and send to the message source a second presence-related message, such as message 2 in FIG. 5, that includes the presence information associated with the identified user. In one embodiment, universal presence service module 504 may be implemented using one or more processors, which may be executing suitable software or firmware programs.
maintaining, in the network node, a presence routing database storing address information for a plurality of presence information providers, at least some of the presence information providers being associated with different network operators;
receiving, from a message source, a first presence-related message that includes information identifying a user, the message source being a node associated with a first network operator;
using the information identifying a user to identify, from the presence routing database, a presence information provider that is currently maintaining presence information associated with the identified user, the identified presence information provider being associated with a second network operator different from the first network operator; and
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 3 wherein the third presence-related message comprises one of a presence status update message response, a presence status query response, and a presence subscription request response.
5. The method of claim 3 wherein the identity of the presence information provider is hidden from and not communicated to the message source.
6. 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.
7. The method of claim 1 wherein the first presence-related message comprises one of a presence status update message, a presence status query, and a presence subscription request.
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 at least some of the plurality of presence information providers are managed by a same network operator.
11. The method of claim 1 wherein the plurality of presence information providers comprises at least one presence database entity.
12. 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.
13. The method of claim 1 wherein the first presence-related message is addressed to the network node.
14. A method for providing presence service using presence information from a plurality of network service providers, the method comprising:
maintaining, at the network node, a presence information database containing a collection of user presence data collected from a plurality of different network operators;
receiving, from a message source associated with a first network operator, a first presence-related message that includes information identifying a user;
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, the identified user being a subscriber of a second network operator different from the first network operator.
15. The method of claim 14 comprising in response to a determination that presence information associated with the identified user does not exist in the presence information database, 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.
16. The method of claim 15 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.
17. The method of claim 14 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.
18. The method of claim 14 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.
19. The method of claim 14 comprising, in response to receiving the first presence-related message, at least one of:
performing a firewall function;
20. The method of claim 14 wherein maintaining the presence information database includes receiving presence status update messages from the plurality of network service providers.
21. The method of claim 14 wherein at least one of the plurality of network operators includes a presence server for maintaining presence information for groups of users.
22. A network entity for providing presence service using presence information from a plurality of presence information providers, the network entity comprising:
a presence routing database for storing address information for a plurality of presence information providers, at least some of the presence information providers being associated with different network operators;
a communications network interface for receiving, from a message source, a first presence-related message that includes information identifying a user, the message source being a node associated with a first network operator; 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 the presence routing database, a presence information provider that is currently maintaining presence information associated with the identified user, the identified presence information provider being associated with a second network operator different from the first network operator, 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.
23. The network entity of claim 22 wherein relaying the first presence related message includes one of:
24. The network entity of claim 22 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:
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.
25. The network entity of claim 24 wherein the third presence-related message comprises one of a presence status update response, a presence status query response, and a presence subscription request response.
26. The network entity of claim 24 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.
27. The network entity of claim 22 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.
28. The network entity of claim 22 wherein the first presence-related message comprises one of presence status update message, a presence status query, and a presence subscription request.
29. The network entity of claim 22 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.
30. The network entity of claim 22 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).
31. The network entity of claim 22 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.
32. 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 different network operators; and
a universal presence service module, implemented by at least processor, for:
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, the identified user being a subscriber of a second network operator different from the first network operator.
33. The universal presence server of claim 32 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.
34. The universal presence server of claim 33 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.
35. The universal presence server of claim 32 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.
36. The universal presence server of claim 32 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.
37. The universal presence server of claim 32 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).
38. The universal presence server of claim 32 wherein the universal presence service module is configured to, in response to receiving the first presence-related message, at least one of:
39. The universal presence server of claim 32 wherein maintaining the presence information database includes receiving presence status update messages from the plurality of network operators and updating the presence information stored in the presence information database.
40. 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:
41. 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:
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 a second presence-related message to the message source, the second presence-related message that includes the presence information associated with the identified user, the identified user being a subscriber of a second network operator different from the first network operator.
US12484857 2008-06-13 2009-06-15 Methods, systems, and computer readable media for providing presence data from multiple presence information providers Active 2031-09-23 US8903903B2 (en)
US6147708 true 2008-06-13 2008-06-13
US6142508 true 2008-06-13 2008-06-13
US6146408 true 2008-06-13 2008-06-13
US12484857 US8903903B2 (en) 2008-06-13 2009-06-15 Methods, systems, and computer readable media for providing presence data from multiple presence information providers
US20100017472A1 true US20100017472A1 (en) 2010-01-21
US8903903B2 true US8903903B2 (en) 2014-12-02
US12484857 Active 2031-09-23 US8903903B2 (en) 2008-06-13 2009-06-15 Methods, systems, and computer readable media for providing presence data from multiple presence information providers
WO (1) WO2009152512A3 (en)
US20140064460A1 (en) * 2008-03-19 2014-03-06 Telecommunications Systems, Inc. End-to-End Logic Tracing of Complex Call Flows in a Distributed Call System
US20160234227A1 (en) * 2006-12-28 2016-08-11 Perftech, Inc. System, method and computer readable medium for message authentication to subscribers of an internet service provider
US20010024950A1 (en) 2000-03-21 2001-09-27 Hakala Harri Tapani Transmission of call detail records in a telecommunications system
US20060244638A1 (en) 2005-03-11 2006-11-02 Ty Lettau System and method for displaying information using a compass
WO2008036645A2 (en) 2006-09-20 2008-03-27 Useful Networks Providing subscriber specific information across wireless networks
Aggarwal et al., "Transport Protocol for Presence Information/Instant Messaging," Internet draft, draft-ietf-impp-pitp-mitp-01, Network Working Group, p. 1-21, (Mar. 9, 2000).
Applicant-Initiated Interview Summary for U.S. Appl. No. 12/762,908 (Jan. 9, 2012).
Chinese Offical Action for Chinese Patent Application No. 200680049126.1 (Feb. 24, 2011).
Commonly-assigned, co-pending U.S. Appl. No. 12/624,974 for "Methods, Systems, and Computer-Readable Media for Providing Geo-Location Proximity Updates to a Presence System," (Unpublished, filed Nov. 24, 2009).
Communication of European publication number and information on the application of Article 67(3) EPC for European Application No. 06826548.7 (Jun. 25, 2008).
Communication pursuant to Article 94(3) EPC for European Application No. 06 826 548.7 (Feb. 20, 2014).
Communication pursuant to Article 94(3) EPC for European application No. 08153801.9 (May 28, 2010).
Communication under Rule 71(3) EPC for European Application No. 08 153 801.9 (Apr. 23, 2012).
Day et al., "A Model for Presence and Instant Messaging," Request for Comments: 2778, Network Working Group, p. 1-17, (Feb. 2000).
Day et al., "Instant Messaging/Presence Protocol Requirements," Request for Comments: 2779, Network Working Group, p. 1-26, (Feb. 2000).
European Search Report for European application Mo. 08153801.9 (Jan. 27, 2010).
Examination Report for Indian Patent Application No. 2580/CHENP/2008 (Oct. 31, 2013).
Extended European Search Report for European Application No. 09763799.5 (Oct. 14, 2011).
Final Office Action for U.S. Appl. No. 12/624,974 (Feb. 6, 2013).
Final Official Action for Divisional U.S. Appl. No. 12/762,908 (Nov. 9, 2011).
Final Official Action for U.S. Appl. No. 11/077,711 (Jun. 23, 2010).
Final Official Action for U.S. Appl. No. 11/077,711 (Mar. 16, 2009).
First Examination Report for Indian Application No. 2580/CHENP/2008 (Nov. 29, 2012).
Handley et al. "SDP: Session Description Protocol," Request for Comments: 2327, Network Working Group, p. 1-42, (Apr. 1998).
Interview Summary for Divisional U.S. Appl. No. 12/762,908 (Jun. 28, 2011).
Interview Summary for U.S. Appl. No. 11/077,711 (Dec. 21, 2010).
Interview Summary for U.S. Appl. No. 11/077,711 (Dec. 3, 2010).
Interview Summary for U.S. Appl. No. 11/077,711 (Mar. 4, 2010).
Interview Summary for U.S. Appl. No. 11/120,324 (Mar. 1, 2011).
Interview Summary for U.S. Appl. No. 12/762,908 (Aug. 23, 2012).
Non-Final Official Action for U.S. Appl. No. 11/120,324 (Nov. 1, 2011).
Non-Final Official Action for U.S. Appl. No. 12/624,974 (Aug. 3, 2012).
Non-Final Official Action for U.S. Appl. No. 12/762,908 (Apr. 25, 2012).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/077,711 (Dec. 20, 2010).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/120,324 (Feb. 22, 2012).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/624,974 (May 13, 2014).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/762,908 (Dec. 18, 2012).
Notice of Grant for Indian Patent Application No. 2580/CHENP/2008 (Dec. 3, 2013).
Notice of Granting Patent Right for Invention for Chinese Patent Application No. 200680049126.1 (Aug. 6, 2012).
Notification of European publication number and information on the application of Article 67(3) EPC for European Application No. 05725442.7 (Nov. 22, 2006).
Notification of European publication number and information on the application of Article 67(3) EPC for European Application No. 05725463.3 (Nov. 29, 2006).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or Declaration for International Application No. PCT/US05/08307 (Mar. 11, 2005).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2006/41451 (Jul. 7, 2008).
Noting of loss of rights pursuant to Rule 112(1) EPC for European Application No. 09763799.5 (Feb. 7, 2012).
Office Action for U.S. Appl. No. 11/077,711 (Jun. 26, 2008).
Official Action for Divisional U.S. Appl. No. 12/762,908 (Apr. 14, 2011).
Official Action for U.S. Appl. No. 09/627,253 (Aug. 25, 2006).
Official Action for U.S. Appl. No. 11/077,711 (Dec. 24, 2009).
Official Action for U.S. Appl. No. 11/120,324 (Mar. 1, 2011).
Official Action for U.S. Appl. No. 11/120,324 (Oct. 19, 2000).
Second Office Action of Chinese Patent Application No. 200680049126.1 (Dec. 6, 2011).
Stracke, J., "Message Information Data Format," Internet draft, draft-ietf-impp-midf-01.txt, Network Working Group, p. 1-4, (Jan. 19, 2000).
Sugano et al., "Presence Information Data Format for IMPP," Internet draft, draft-ietf-impp-pidf-01.text, Network Working Froup, p. 1-17, (Mar. 10, 2000).
Supplemental Notice of Allowability for U.S. Appl. No. 11/077,711 (Feb. 16, 2011).
Supplemental Notice of Allowability for. U.S. Appl. No. 11/077,711 (Feb. 16, 2011).
Supplementary European Search Report for European application No. 05725442.7 (Aug. 16, 2011).
Tekelec, "IP7 Secure Gateway Release 1.0", Tekelec Release Documentation, 910-2046-01 Revision A (Nov. 1999).
Wideberg et al., "Driving Traffic Data From a Cellular Network," World Congress on Intelligent Transport System and Services, World Congress on Intelligent Transport System and Services (13). No. 13. Londres, UK, Ertico, (2006).
US9042522B2 (en) * 2008-03-19 2015-05-26 Telecommunication Systems, Inc. End-to-end logic tracing of complex call flows in a distributed call system
WO2009152512A3 (en) 2010-03-18 application
EP2307976A2 (en) 2011-04-13 application
WO2009152512A2 (en) 2009-12-17 application
EP2307976A4 (en) 2011-11-16 application
US20100017472A1 (en) 2010-01-21 application
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BENEDYK, ROBBY;MARSICO, PETER;REEL/FRAME:023310/0695