IP Library Granted Patent US 10,805,364
Granted Patent B2
US 10,805,364 · App. 16/175,001 · Granted Oct 13, 2020

Routing of conference participant based on caller recognition

Inventors: Andrew James Broadworth (Thornton, CO); Gregory Thomas Ellison (Erie, CO)
Assignee: Level 3 Communications, LLC
H04L65/403H04L12/1818H04L65/1076H04L65/1093H04L65/4038H04M3/56H04M2203/5045
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 10,805,364
App. No.
16/175,001
Granted
Oct 13, 2020
Kind
B2
Abstract

Aspects of the present disclosure involve systems, methods, computer program products, and the like, for routing one or more requests to join or initiate a collaboration conference based on at least an identifier of a requesting device. In one embodiment, a telecommunications network obtains an identifier, such as the telephone number, of a device requesting to join or initiate a collaboration conference. The identifying information is then compared to a database of user accounts maintained by the network. The network may then prompt the user of the requesting device to join a particular conferencing bridge or provide particular conferencing features based on the one or more preferences associated with the user's account. A response to the prompt may be received and then acted upon by the network to connect the requesting device to a collaboration conference and/or provide the one or more conferencing features to the requesting device.

Claims (52)

1. A telecommunications network comprising:

at least one conference bridge; and

at least one routing device configured to:

receive a communication from a user of the telecommunications network, the communication comprising a request to access a collaboration conference event, wherein the collaboration conference event is established at a first time, and wherein the communication is received at a second time after the first time;

obtain an identifier of a communication device associated with the telecommunications network and the user, the identifier comprising a telephone number of the communication device from which the request is received and obtained through an Automatic Number Identification (ANI) feature of the telecommunication network;

identify, based on the telephone number of the communication device from which the request is received, the collaboration conference event; and

connect the communication device to the collaboration conference event based on the telephone number of the communication device from which the request is received.

2. The telecommunications network as recited in claim 1 wherein the at least one routing device is further configured to determine a first role of the user for the collaboration conference event and a second role of a second user for the collaboration conference event, wherein the first role comprises a chairperson of the collaboration conference event and the second role comprises a non-chairperson participant.

3. The telecommunication network as recited in claim 1 wherein the at least one routing device is further configured to:

transmit a first prompt to the communication device to select the collaboration conference event;

receive a response to the prompt from the communication device; and

in the event that the response to the prompt received from the communication device is a first type of response, transmit a second prompt to the communication device requesting entry of an access code associated with the user.

4. The telecommunications network as recited in claim 1 wherein the identifier is a text string associated with the communication device, the text string included in a header of the communication from the user.

5. A system for initiating a collaboration conference in a telecommunications network, the system comprising:

a network interface unit configured to receive a first communication from a user of a communications network to establish a collaboration conference event on the network, wherein the collaboration conference event is established at a first time, the first communication received at a second time after the first time from a communication device associated with the communications network;

an application server in communication with the network interface unit; and

a computer-readable medium connected to the application server configured to store information and instructions that, when executed by the application server, performs the operations of:

obtaining an identifier of the communication device associated with the communications network, the identifier comprising a telephone number of the communication device from which the request is received and obtained through an Automatic Number Identification (ANI) feature of the communications network;

identifying, based on the telephone number of the communication device from which the request is received, the collaboration conference event; and

connecting the communication device to the collaboration conference event based on the telephone number of the communication device from which the request is received.

6. The system as recited in claim 5 wherein the application server further performs the operations of determining, based on the identifier of the communication device, one or more preferences including at least one of high definition audio, high definition video, conference bridge location or a specific quality of service.

7. The system as recited in claim 5 wherein the application server further performs the operations of:

transmitting a first prompt to the communication device to select the collaboration conference event;

receive a response to the prompt from the communication device; and

in the event that the response to the prompt received from the communication device is a first type of response, transmit a second prompt to the communication device requesting entry of an access code associated with the user.

8. The system as recited in claim 5 wherein the application server further performs the operations of:

receiving the telephone number of the communication device of the communication device from which the request is received from the user through a user interface; and

storing the telephone number of the communication device from which the request is received in the account of the user as an identifier of the user.

9. The system as recited in claim 8 wherein the application server further performs the operations of:

receiving one or more collaboration conference preferences from the user; and

storing the one or more collaboration conference preferences in the account of the user.

10. The system as recited in claim 5 wherein the application server further logging a date and time of a second communication received from the communication device, the second communication configured to request to join a particular collaboration conference event; and

logging a date and time of a second communication received from the communication device, the second communication configured to request to join a particular collaboration conference event; and

storing the date and time of the second communication in the account of the user.

11. The system as recited in claim 10 wherein the application server further performs the operations of:

logging one or more collaboration conference selections received from the user through the communication device; and

storing the one or more collaboration conference selections as one or more collaboration conference preferences in the account of the user.

12. The system as recited in claim 9 wherein the receiving the one or more collaboration conference preferences from the user operation comprises accessing a program associated with the user, the program including the one or more collaboration conference preferences.

13. A method for initiating a collaboration conference in a telecommunications network comprising:

receiving a request message for access to a collaboration conference event from a requester's communication device, wherein the collaboration conference event is established at a first time, and wherein the request message is received at a second time after the first time;

obtaining an identifier of the requester's communication device, the identifier comprising a telephone number of the requester's communication device from which the request is received and obtained through an Automatic Number Identification (ANI) feature of the telecommunications network;

identifying, based on the telephone number of the requester's communication device from which the request is received, the collaboration conference event; and

connecting the requester's communication device to the collaboration conference event based on the telephone number of the requester's communication device from which the request is received.

14. The method as recited in claim 13 further comprising:

transmitting a first prompt to the requester's communication device, the first prompt configured to elicit a selection of the collaboration conference event; and

receive a response to the prompt from the requester's communication device.

15. The method as recited in claim 14 further comprising:

retrieving one or more collaboration conference preferences associated with the account of the requester; and

applying the one or more collaboration conference preferences to the collaboration conference event.

16. The telecommunications network as recited in claim 1 wherein the identifier of the communication device is a first identifier, wherein the at least one routing device is further configured to determine, based on the telephone number of the communication device from which the request is received, a second identifier associated with the user and at least one other user, and wherein to identify the collaboration conference event comprises to determine, based on the second identifier, the collaboration conference event.

17. The system as recited in claim 5 wherein the identifier of the communication device is a first identifier, wherein the application server further performs the operations of determining, based on the telephone number of the communication device from which the request is received, a second identifier associated with the user and at least one other user, and wherein identifying the collaboration conference event comprises determining, based on the second identifier, the collaboration conference event.

18. The method as recited in claim 13 wherein the identifier of the communication device is a first identifier, further comprising determining, based on the telephone number of the requestor's communication device from which the request is received, a second identifier associated with the requester and at least one other user, and wherein identifying the collaboration conference event comprises determining, based on the second identifier, the collaboration conference event.

Assignments (3)
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (SECOND LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0749 →
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (FIRST LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0858 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 14, 2018
From: BROADWORTH, ANDREW JAMES; ELLISON, GREGORY THOMAS
To: LEVEL 3 COMMUNICATIONS, LLC
Reel/Frame 047496/0851 →
Continuity (10)
Continuation 13971531 · Aug 20, 2013
Continuation In Part 13708713 · Dec 7, 2012
Provisional Application 61584115 · Jan 6, 2012
Provisional Application 61584122 · Jan 6, 2012
Provisional Application 61578803 · Dec 21, 2011
Provisional Application 61578810 · Dec 21, 2011
Provisional Application 61578798 · Dec 21, 2011
Provisional Application 61578794 · Dec 21, 2011
Provisional Application 61578807 · Dec 21, 2011
Related Publication 20190075144A1 · Mar 7, 2019