US2015111553A1PendingUtilityA1

Method and system for automating conferencing in a communication session

Assignee: VONAGE NETWORK LLCPriority: Oct 21, 2013Filed: Dec 23, 2014Published: Apr 23, 2015
Est. expiryOct 21, 2033(~7.2 yrs left)· nominal 20-yr term from priority
H04L 65/104H04M 3/56H04L 65/403H04L 12/1818H04L 65/1033H04M 2203/5018H04L 12/189H04L 65/1069H04W 4/16H04L 65/65H04L 67/54H04L 65/1045H04L 65/1104H04M 3/563H04L 65/1093H04L 51/043H04L 12/1822
49
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Methods and system for automating conferencing in a communication session are provided herein. In some embodiments, a method for automating conferencing in a communication session includes detecting an established communication session between a first end-user device and a second end-user device, notifying a third end-user device associated with the first user device that the established communication session is available to be joined, receiving a request from the third end-user device to join the communication session, and establishing a conference session with the first end-user device, the second-end user device, and the third end-user device.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method for handling calls between associated devices of a shared telephony account, comprising:
 establishing a communication session between a first end-user device and a second end-user device;   receiving a first notification message from the first end-user device indicating that the communication session is at least one of visible or joinable by one or more devices associated with the first end-user device; and   sending a second notification message to the one or more devices associated with the first end-user device.   
     
     
         2 . The method of  claim 1 , wherein the first notification message designates the communication session as one of (a) visible and joinable by one or more devices associated with the first end-user device, (b) visible but not joinable by one or more devices associated with the first end-user device, or (c) joinable in listen only mode by one or more devices associated with the first end-user device. 
     
     
         3 . The method of  claim 1 , further comprising:
 receiving a request from at least one of the one or more devices associated with the first end-user device to join the communication session; and   establishing a conference session with the first end-user device, the second end-user device, and the at least one of the one or more devices associated with the first end-user device that requested to join the communication session.   
     
     
         4 . The method of  claim 3 , further comprising:
 receiving a request to establish a private line between the first end-user device and the at least one of the one or more devices associated with the first end-user device participating in the conference session.   
     
     
         5 . The method of  claim 4 , further comprising:
 establishing the private line between the first end-user device and the at least one of the one or more devices associated with the first end-user device participating in the conference session while the conference session is active.   
     
     
         6 . The method of  claim 3 , wherein establishing the conference session includes sending an invitation message to one or more devices associated with the first end-user device for a conference session; and
 sending a re-invitation message to the first end-user device and second-end user device for the conference session.   
     
     
         7 . The method of  claim 3 , wherein the communication session is established via a proxy server, and wherein establishing the conference session includes routing the communication session to a conference server hosting the conference session. 
     
     
         8 . The method of  claim 3 , wherein data streams from each end-user device are coordinated in the conference session via a media relay. 
     
     
         9 . The method of  claim 1 , further comprising:
 receiving a request to share screen images related to the communication session displayed on the first user device with the one or more devices associated with the first end-user device.   
     
     
         10 . A method for automating conferencing in a communication session, comprising:
 receiving a request to establish a communication session between a first end-user device and a second end-user device;   determining one or more third end-user devices associated with the first end-user device that should be notified of the communication session based on configuration settings stored in association with the first end-user device; and   sending a notification message to each of the determined one or more third end-user devices that should be notified to join the established communication session.   
     
     
         11 . The method of  claim 10 , further comprising:
 receiving a request from at least one of the one or more third end-user devices associated with the first end-user device to join the communication session; and   establishing a conference session with the first end-user device, the second end-user device, and the at least one of the one or more third end-user devices associated with the first end-user device that requested to join the communication session.   
     
     
         12 . The method of  claim 10 , wherein determining one or more third end-user devices associated with the first end-user device that should be notified of the communication session based on configuration settings includes:
 determining the one or more third end-user devices that are authorized in the configuration settings to participate in communication sessions associated with a communication identifier of the second end-user device.   
     
     
         13 . The method of  claim 10 , wherein determining one or more third end-user devices associated with the first end-user device that should be notified of the communication session based on configuration settings includes:
 determining the one or more third end-user devices that include a communication identifier of the second end-user device in their address book.   
     
     
         14 . The method of  claim 10 , wherein determining one or more third end-user devices associated with the first end-user device that should be notified of the communication session based on configuration settings includes:
 determining the one or more third end-user devices that have participated in previous calls with the second end-user device.   
     
     
         15 . The method of  claim 10 , wherein determining one or more third end-user devices associated with the first end-user device that should be notified of the communication session based on configuration settings includes:
 monitoring a communication session established between the first end-user device and the second end-user device;   determining that one or more words spoken during the communication session is similar to one or more predefined keywords; and   determining the one or more third end-user devices configured to be notified when a keyword similarity match is identified.   
     
     
         16 . A method for automating conferencing in a communication session, comprising:
 receiving, at a third end-user device associated with a first end-user device, a notification of an established communication session between the first end-user and a second end-user device;   displaying an indication of the communication session and whether the communication session may be joined based on the notification received;   sending a request to join the established communication session; and   establishing a conference session with the first end-user device, the second end-user device, and the third end-user device.   
     
     
         17 . The method of  claim 16 , wherein the received notification indicates that the communication session is one of joinable with full participation or joinable in listen only mode.

Join the waitlist — get patent alerts

Track US2015111553A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.