IP Library › Granted Patent US 12,438,923
Granted Patent B2
US 12,438,923 · App. 16/799,722 · Granted Oct 7, 2025

Establishing and managing connections for real time communications

Inventors: Rameshkumar Ayyasamy Jayapal (Mount Laurel, NJ); Manoj Chaudhari (Dayton, NJ); Naresh Mudupu (Mount Laurel, NJ); Chris Wendt (Exton, PA); Saravanan Muthusamy (Wayne, PA); Balachandar Gurusamy (King of Prussia, PA); Neppoliyan Thangavelu (Philadelphia, PA)
Assignee: Comcast Cable Communications, LLC
H04L65/1069H04L65/1104H04L67/02H04L67/1031H04L67/141H04L67/146H04L69/40H04M3/42076H04M3/42119H04W76/10H04M7/0075H04W76/19
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,438,923
App. No.
16/799,722
Granted
Oct 7, 2025
Kind
B2
Abstract

Methods and systems related to supporting real time communications are disclosed. In one type of a real time communication session, prior to an offer and acceptance to perform real time communications, a communication channel may be established between a caller device and a callee device. Information related to addresses of the caller and callee devices can be contained in, or pointed to, by a Universal Resource Locators (URLs) for the caller and callee devices. A network computing device may communicate messages relating to establishing and maintaining the communication channel between the caller and callee devices. In a scenario where the network computing device becomes unavailable, another network computing device can use the URLs and other channel information that may be stored in the database, to handle messages.

Claims (34)

1. A method comprising:

establishing, based on a request from a caller device, a communication channel with a callee device, wherein the communication channel is associated with at least a caller device address and a first callee device address;

receiving, from the callee device, a first message indicating a second callee device address;

sending, to the caller device based on the first message and in order to maintain the communication channel, a notification, comprising the first callee device address and the second callee device address, indicating that the callee device is associated with the second callee device address;

receiving, from the caller device, a second message comprising the second callee device address; and

based on the second message comprising the second callee device address, forwarding, via the communication channel and to the callee device, the second message.

2. The method of claim 1 , wherein the caller device address and the first callee device address is stored by at least one computing device.

3. The method of claim 2 , wherein the stored information is updated, based on the first message, by the at least one computing device.

4. The method of claim 1 , wherein the first callee device address comprises a first Universal Resource Locator (URL) associated with the callee device, and wherein the second callee device address comprises a second URL associated with the callee device.

5. The method of claim 1 , wherein the first message and the second message between the caller device and callee device are communicated via a different computing device of a plurality of computing devices and without accessing a shared persistent database.

6. The method of claim 1 , wherein the notification prevents the second message from comprising the first callee device address and being erroneously forwarded to the first callee device address.

7. A device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the device to:

establish based on a request from a caller device, a communication channel with a callee device, wherein the communication channel is associated with at least a caller device address and a first callee device address;

receive, from a callee device, a first message indicating a second callee device address;

send, to the caller device based on the first message and in order to maintain the communication channel, a notification, comprising the first callee device address and the second callee device address, indicating that the callee device is associated with the second callee device address;

receive, from the callee device, a message comprising the second callee device address; and

based on the second message comprising the second callee device address, forward, via the communication channel and to the callee device, the second message.

8. The device of claim 7 , wherein the caller device address and the first callee device address is stored by at least one computing device.

9. The device of claim 8 , wherein the stored information is updated, based on the first message, by the at least one computing device.

10. The device of claim 7 , wherein the first callee device address comprises a first Universal Resource Locator (URL) associated with the callee device, and wherein the second callee device address comprises a second URL associated with the callee device.

11. The device of claim 7 , wherein the first message and second message between the caller device and callee device are communicated via a different computing device of the plurality of computing devices and without accessing a shared persistent database.

12. The device of claim 7 , wherein the notification prevents the second message from comprising the first callee device address and being erroneously forwarded to the first callee device address.

13. A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by one or more processors, cause:

establishing, based on a request from a caller device, a communication channel with a callee device, wherein the communication channel is associated with at least a caller device address and a first callee device address;

receiving, from the callee device, a first message indicating a second callee device address;

sending, to the caller device based on the first message and in order to maintain the communication channel, a notification, comprising the first callee device address and the second callee device address, indicating that the callee device is associated with the second callee device address;

receiving, from the caller device, a second message comprising the second callee device address; and

based on the second message comprising the second callee device address, forwarding, via the communication channel and to the callee device, the second message.

14. The non-transitory computer-readable storage medium of claim 13 , wherein caller device address and the first callee device address is stored by at least one computing device, and wherein the stored information is updated, based on the first message, by the at least one computing device.

15. The non-transitory computer-readable storage medium of claim 13 , wherein the first callee device address comprises a first Universal Resource Locator (URL) associated with the callee device, and wherein the second callee device address comprises a second URL associated with the callee device.

16. The non-transitory computer-readable storage medium of claim 13 , wherein the first message and second message between the caller device and callee device are communicated via a different computing device of a plurality of computing devices and without accessing a shared persistent database.

17. The non-transitory computer-readable storage medium of claim 13 , wherein the notification prevents the second message from comprising the first callee device address and being erroneously forwarded to the first callee device address.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2021
From: JAYAPAL, RAMESHKUMAR AYYASAMY; CHAUDHARI, MANOJ; MUDUPU, NARESH; WENDT, CHRIS; MUTHUSAMY, SARAVANAN; GURUSAMY, BALACHANDAR; THANGAVELU, NEPPOLIYAN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 056251/0171 →
Continuity (2)
Continuation 15138439 · Apr 26, 2016
Related Publication 20200336515A1 · Oct 22, 2020
References Cited (28)
US 20040121765A1 · Idnani · 2004 [cited by examiner]
US 20050207361A1 · Rosenberg et al. · 2005 [cited by applicant]
US 20090022145A1 · Bakshi · 2009 [cited by examiner]
US 20090161843A1 · Sylvain · 2009 [cited by applicant]
US 20090238358A1 · Ramanathan · 2009 [cited by examiner]
US 20100015980A1 · Seta et al. · 2010 [cited by applicant]
US 20100266111A1 · Crausaz et al. · 2010 [cited by applicant]
US 20100278099A1 · Lee · 2010 [cited by examiner]
US 20110044319A1 · Younis · 2011 [cited by examiner]
US 20110116492A1 · Byron · 2011 [cited by examiner]
US 20120155445A1 · Javaregowda · 2012 [cited by examiner]
US 20140333713A1 · Shoemake et al. · 2014 [cited by applicant]
US 20150236905A1 · Bellan · 2015 [cited by examiner]
US 20150281234A1 · Sylvain · 2015 [cited by applicant]
US 20160212074A1 · Yu et al. · 2016 [cited by applicant]
US 20160219093A1 · Gangadharan et al. · 2016 [cited by applicant]
US 20160308977A1 · Ezell · 2016 [cited by examiner]
US 20170111407A1 · Kotnis · 2017 [cited by examiner]
US 20170289200A1 · Mendiratta et al. · 2017 [cited by applicant]
US 20170289201A1 · Mendiratta · 2017 [cited by examiner]
US 20170325141A1 · Laliberte · 2017 [cited by examiner]
Wikipedia, “High-availability cluster”, Oct. 22, 2015, total 4 pages (Year: 2016). [cited by examiner]
Rfc3261, “SIP: Session Initiation Protocol”, Network Working Group, Jun. 2002. (Year: 2002). [cited by examiner]
Rfc4566, “SDP: Session Description Protocol”, Network Working Group, Jul. 2006. (Year: 2006). [cited by examiner]
“The Session Description Protocol (SDP)”, Nick Galea, CEO, 3CX, Oct. 11, 2009. (Year: 2009). [cited by examiner]
Acharya et al., “Unleashing the Power of Wearable Devices in a SIP Infrastructure”, Proceedings of the 3rd IEEE Int'l Conf. on Pervasive Computing and Communications (PerCom 2005), 10 Pages. (Year: 2005). [cited by applicant]
RFC 3261, “SIP: Session Initiation Protocol”. [cited by applicant]
Rosenberg, et al., “RFC 3261, SIP: Session Initiation Protocol”, Network Working Group, Standards Track, Jun. 2002, 269 Pages. (Year: 2002). [cited by applicant]