Sustained VOIP call logs using PoC contact lists

• US 20060140173A1
• Filed: 05/11/2005
• Published: 06/29/2006
• Est. Priority Date: 12/24/2004
• Status: Active Grant

• Current Assignee: Sonim Technologies, Inc.
• Original Assignee: Sonim Technologies, Inc.
• Inventors: Hoover, Christopher
• Granted Patent: US 7,324,505 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/4061 Push-to services, e.g. push-to-talk or push-to-video
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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: H04M 3/2218 Call detail recording
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 84/08 Trunked mobile radio systems

Abstract

A method for logging Voice Over IP (VOIP) calls from a caller client device to a recipient client device. The method includes the steps of generating a VOIP call from the caller client device directed to the recipient client device; storing identification information associated with the caller client device in server call log resident on a hyper text transfer protocol (HTTP) server associated with the recipient client device; generating an update request at the recipient client device requesting updated call log information associated with the server call log from the HTTP server; transmitting the updated call log information from the HTTP server to the recipient client device; and updating a client call log resident on the recipient client device in response to the updated call log information.

Claims

1. In a cellular network, a method for logging Voice Over IP (VOIP) calls from a caller client device to a recipient client device, comprising the steps of:

generating a VOIP call from the caller client device directed to the recipient client device;

storing identification information associated with the caller client device in a server call log resident on a hyper text transfer protocol (HTTP) server associated with the recipient client device;

generating an update request at the recipient client device requesting updated call log information associated with the server call log from the HTTP server;

transmitting the updated call log information from the HTTP server to the recipient client device; and

updating a client call log resident on the recipient client device in response to the updated call log information.

2. The method recited in claim 1, wherein the identification information includes a SIP URI of the caller client device, time the VOIP call was generated, date the VOIP call was generated, and nickname of the caller client device.

3. The method recited in claim 1, wherein the server call log is associated with multiple client devices.

4. The method recited in claim 1, wherein the update request is an HTTP GET message.

5. The method recited in claim 1, further comprising the steps of:

notifying the recipient client device of the presence of a new VOIP call stored in the server call log.

6. The method recited in claim 5, wherein the notifying step transmits a XCAP notification or SMS message to the recipient client device.

7. The method recited in claim 1, further comprising the steps of:

providing a reject list resident on a server on the cellular network for blocking VOIP calls to the recipient client device;

determining if the caller client device is on the reject list;

if the caller client device is on the reject list, blocking the VOIP call from the caller client device;

if the caller client device is not on the reject list, allowing the VOIP call from the caller client device; and

if the caller client device is on the reject list, storing identification information associated with the caller client device resident on the HTTP server associated with the recipient client device.

8. The method recited in claim 1, further comprising the steps of:

providing a do not disturb flag resident on a server on the cellular network for blocking VOIP calls to the recipient client device;

in response to the VOIP call, determining the status of the do not disturb flag;

if the do not disturb flag is set to block VOIP calls, blocking the VOIP call from the caller client device and logging the call with reason code “

DnD”

; and

if the do not disturb flag is set to allow VOIP calls, allowing the VOIP call from the caller client device and logging the call with reason code “

unavailable”

if not successful.

9. The method recited in claim 1, further comprising the steps of:

subscribing at least one other client device, other than the recipient client device, to the server call log.

10. The method recited in claim 1, further comprising the steps of:

selecting a caller from the updated call log; and

generating a SIP Invite message directed to the selected caller.

11. The method recited in claim 10, further comprising the steps of:

if the selected caller is a group call having an associated SIP URI of a VOIP server, indicating on the recipient caller device whether the group call is active; and

transmitting a SIP message from the recipient client device to the associated SIP URI.

12. In a cellular network, a method for logging Voice Over IP (VOIP) calls from a caller client device to a recipient client device, comprising the steps of:

generating a VOIP call from the caller client device directed to the recipient client device;

storing identification information associated with the caller client device in a server call log resident on a hyper text transfer protocol (HTTP) server associated with the recipient client device;

providing a do not disturb flag resident on a server on the cellular network for blocking VOIP calls to the recipient client device;

providing a reject list resident on a server on the cellular network for blocking VOIP calls to the recipient client device;

in response to the VOIP call, determining the status of the do not disturb flag;

if the do not disturb flag is set to block VOIP calls, blocking the VOIP call from the caller client device;

if the do not disturb flag is set to allow VOIP calls, determining if the identification information of the caller client device to the reject list;

if the caller client device is on the reject list, blocking the VOIP call from the caller client device; and

if the caller client device is not on the reject list, allowing the VOIP call from the caller client device.

13. The method recited in claim 12, further comprising the steps of:

generating an update request at the recipient client device requesting updated call log information associated with the server call log from the HTTP server;

transmitting the updated call log information from the HTTP server to the recipient client device; and

updating a client call log resident on the recipient client device in response to the updated call log information.

14. The method recited in claim 12, wherein the server call log is associated with multiple client devices.

15. The method recited in claim 13, wherein the update request is an HTTP GET message.

16. The method recited in claim 12, further comprising the steps of:

notifying the recipient client device of the presence of a new VOIP call stored in the server call log.

17. The method recited in claim 16, wherein the notifying step transmits a XCAP or SMS message to the recipient client device.

18. In a cellular network, a hyper text transfer protocol (HTTP) server associated with a recipient client device for logging Voice Over IP (VOIP) calls from a caller client device to the recipient client device, comprising:

means for receiving a VOIP call from the caller client device directed to the recipient client device;

means for storing identification information associated with the caller client device in a server call log; and

means for transmitting the updated call log information to the recipient client device in response to an update request from the recipient client device.

19. The server recited in claim 18, wherein the identification information includes a SIP URI of the caller client device, time the VOIP call was generated, date the VOIP call was generated, and nickname of the caller client device.

20. The server recited in claim 18, wherein the server call log is associated with multiple client devices.

21. The server recited in claim 18, wherein the update request is an HTTP GET message.

22. The server recited in claim 18, further comprising:

means for notifying the recipient client device of the presence of a new VOIP call stored in the server call log.

23. The server recited in claim 22, wherein the means for notifying transmits a XCAP or SMS message to the recipient client device.

24. The server recited in claim 18, further comprising:

means for providing a reject list resident for blocking VOIP calls to the recipient client device;

means for determining if the caller client device is on the reject list; and

if the caller client device is on the reject list, means for blocking the VOIP call from the caller client device.

25. The server recited in claim 18, further comprising:

means for providing a do not disturb flag for blocking VOIP calls to the recipient client device;

means for providing a reject list for blocking VOIP calls to the recipient client device;

means for determining the status of the do not disturb flag; and

if the do not disturb flag is set to block VOIP calls, means for blocking the VOIP call from the caller client device.

26. The server recited in claim 18, further comprising:

means for subscribing at least one other client device, other than the recipient client device, to the server call log.

27. In a cellular network, a hyper text transfer protocol (HTTP) server associated with a recipient client device for logging Voice Over IP (VOIP) calls from a caller client device to the recipient client device, comprising:

means for receiving a VOIP call from the caller client device directed to the recipient client device;

means for storing identification information associated with the caller client device in a server call log;

means for providing a do not disturb flag for blocking VOIP calls to the recipient client device;

means for providing a reject list for blocking VOIP calls to the recipient client device;

means for determining the status of the do not disturb flag;

if the do not disturb flag is set to block VOIP calls, means for blocking the VOIP call from the caller client device;

if the do not disturb flag is set to allow VOIP calls, means for determining if the identification information of the caller client device to the reject list;

if the caller client device is on the reject list, means for blocking the VOIP call from the caller client device; and

if the caller client device is not on the reject list, means for allowing the VOIP call from the caller client device.

28. The server recited in claim 27, further comprising:

means for transmitting the updated call log information to the recipient client device in response to an update request from the recipient client device.

29. The server recited in claim 27, wherein the server call log is associated with multiple client devices.

30. The server recited in claim 28, wherein the update request is an HTTP GET message.

31. The server recited in claim 27, further comprising:

means for notifying the recipient client device of the presence of a new VOIP call stored in the server call log.

32. The server recited in claim 31, wherein means for notifying transmits a XCAP or SMS message to the recipient client device.