IP Library Granted Patent US 11,575,530
Granted Patent B2
US 11,575,530 · App. 16/514,947 · Granted Feb 7, 2023

Systems and methods for call initiation based on mobile device proximity

Inventors: Salman Suhail (San Francisco, CA); Robyn Rapp (Sausalito, CA)
Assignee: Salesforce, Inc.
H04L12/1822G06F16/632G06F16/683H04L12/1818H04L12/1827
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 11,575,530
App. No.
16/514,947
Granted
Feb 7, 2023
Kind
B2
Abstract

Certain embodiments are directed to systems and methods for facilitating the process of joining a conference call within a conference environment. A conference call participant may initiate a conference call within a conference environment (e.g., a conference room), by causing the participant's client device to emit a unique audio tone (which may be human-audible or human-inaudible) that is detected by a call device within the conference room. The unique tone is indicative of unique conference call identification data, which may be utilized by the call device to initiate the conference call, without requiring additional user input by the conference call participant.

Claims (65)

1. A system configured for activating a connection to a call, wherein the system comprises:

one or more non-transitory memory storage repositories; and

one or more processors, wherein the one or more processors are collectively configured to:

receive, at a call device, an invitation for the call, the invitation indicating the call device to be utilized during the call, wherein the invitation is further configured for reception by a client device associated with an invitee of the call;

output, at the call device, an initialization audio signal for the call based on the invitation;

receive, at the call device, a responsive audio signal comprising audio signature data from the client device in response to the initialization audio signal for the call and based at least in part on the client device being associated with the invitee of the call;

determine a meeting identifier based at least in part on the audio signature data, wherein the meeting identifier is associated with the call; and

in response to determining the meeting identifier, establish a call connection for the call between the call device and an external call platform based at least in part on the determined meeting identifier and the invitation indicating the call device to be utilized during the call.

2. The system of claim 1 , wherein determining the meeting identifier comprises:

querying a lookup table stored within the one or more non-transitory memory storage repositories based at least in part on the audio signature data, wherein the lookup table maps respective audio signature data with meeting identifiers; and

in response to the querying, receiving the meeting identifier mapped to the audio signature data.

3. The system of claim 1 , wherein the audio signature data comprises header data and meeting identifier data, and wherein determining the meeting identifier comprises:

determining, based at least in part on the header data of the audio signature data, the external call platform for the call; and

determining, based at least in part on the meeting identifier data, the meeting identifier usable to initialize the call with the external call platform.

4. The system of claim 1 , wherein establishing the call connection for the call comprises initializing a real-time call connection via a network between the call device and the external call platform.

5. The system of claim 4 , wherein initializing the real-time call connection comprises initializing a real-time video call connection via the network between the call device and the external call platform.

6. The system of claim 1 , wherein the one or more processors are further configured to:

receive a call generation request;

determine meeting identifier data for the call generation request;

generate the audio signature data based at least in part on the meeting identifier data; and

transmit the audio signature data to one or more client devices comprising at least the client device, wherein the audio signature data causes the one or more client devices to emit an audio signal upon activation of the audio signature data.

7. The system of claim 1 , wherein the audio signature data comprises user identifier data, and wherein the one or more processors are further configured to:

identify a user identifier as a participant in the call based at least in part on receipt of the user identifier data as a part of the audio signature data.

8. A computer-implemented method for activating a connection to a call, wherein the method comprises:

receiving, at a call device, an invitation for the call, the invitation indicating the call device to be utilized during the call, wherein the invitation is further configured for reception by a client device associated with an invitee of the call;

outputting, at the call device, an initialization audio signal for the call based on the invitation;

receiving, at the call device, a responsive audio signal comprising audio signature data from the client device in response to the initialization audio signal for the call and based at least in part on the client device being associated with the invitee of the call;

determining a meeting identifier based at least in part on the audio signature data, wherein the meeting identifier is associated with the call; and

in response to determining the meeting identifier, establishing a call connection for the call between the call device and an external call platform based at least in part on the determined meeting identifier and the invitation indicating the call device to be utilized during the call.

9. The computer-implemented method of claim 8 , wherein determining the meeting identifier comprises:

querying a lookup table based at least in part on the audio signature data, wherein the lookup table maps respective audio signature data with meeting identifiers; and

in response to the querying, receiving the meeting identifier mapped to the audio signature data.

10. The computer-implemented method of claim 8 , wherein the audio signature data comprises header data and meeting identifier data, and wherein determining the meeting identifier comprises:

determining, based at least in part on the header data of the audio signature data, the external call platform for the call; and

determining, based at least in part on the meeting identifier data, the meeting identifier usable to initialize the call with the external call platform.

11. The computer-implemented method of claim 8 , wherein establishing the call connection for the call comprises initializing a real-time call connection via a network between the call device and the external call platform.

12. The computer-implemented method of claim 11 , wherein initializing the real-time call connection comprises initializing a real-time video call connection via the network between the call device and the external call platform.

13. The computer-implemented method of claim 8 , further comprising:

receiving a call generation request;

determining meeting identifier data for the call generation request;

generating the audio signature data based at least in part on the meeting identifier data; and

transmitting the audio signature data to one or more client devices comprising at least the client device, wherein the audio signature data causes the one or more client devices to emit an audio signal upon activation of the audio signature data.

14. The computer-implemented method of claim 8 , wherein the audio signature data comprises user identifier data, and wherein the computer-implemented method further comprises:

identifying a user identifier as a participant in the call based at least in part on receipt of the user identifier data as a part of the audio signature data.

15. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a call device, cause the call device to:

receive, at the call device, an invitation for a call, the invitation indicating the call device to be utilized during the call, wherein the invitation is further configured for reception by a client device associated with an invitee of the call;

output, at the call device, an initialization audio signal for the call based on the invitation;

receive, at the call device, a responsive audio signal comprising audio signature data from the client device in response to the initialization audio signal for the call and based at least in part on the client device being associated with the invitee of the call;

determine a meeting identifier based at least in part on the audio signature data, wherein the meeting identifier is associated with the call; and

in response to determining the meeting identifier, establish a call connection for the call between the call device and an external call platform based at least in part on the determined meeting identifier and the invitation indicating the call device to be utilized during the call.

16. The non-transitory computer-readable storage medium of claim 15 , wherein determining the meeting identifier comprises:

querying a lookup table based at least in part on the audio signature data, wherein the lookup table maps respective audio signature data with meeting identifiers; and

in response to the querying, receiving the meeting identifier mapped to the audio signature data.

17. The non-transitory computer-readable storage medium of claim 15 , wherein the audio signature data comprises header data and meeting identifier data, and wherein determining the meeting identifier comprises:

determining, based at least in part on the header data of the audio signature data, the external call platform for the call; and

determining, based at least in part on the meeting identifier data, the meeting identifier usable to initialize the call with the external call platform.

18. The non-transitory computer-readable storage medium of claim 15 , wherein establishing the call connection for the call comprises initializing a real-time call connection via a network between the call device and the external call platform.

19. The non-transitory computer-readable storage medium of claim 18 , wherein initializing the real-time call connection comprises initializing a real-time video call connection via the network between the call device and the external call platform.

20. The non-transitory computer-readable storage medium of claim 15 , further comprising instructions, which when executed by the one or more processors of the call device, cause the call device to:

receive a call generation request;

determine meeting identifier data for the call generation request;

generate the audio signature data based at least in part on the meeting identifier data; and

transmit the audio signature data to one or more client devices comprising at least the client device, wherein the audio signature data causes the one or more client devices to emit an audio signal upon activation of the audio signature data.

21. The non-transitory computer-readable storage medium of claim 15 , wherein the audio signature data comprises user identifier data, and further comprising instructions, which when executed by the one or more processors of the call device, cause the call device to:

identify a user identifier as a participant in the call based at least in part on receipt of the user identifier data as a part of the audio signature data.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2025
From: SLACK TECHNOLOGIES, LLC
To: SALESFORCE, INC.
Reel/Frame 070001/0469 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NEWLY MERGED ENTITY'S NEW NAME, AND TO REMOVE THE PERIOD PREVIOUSLY RECORDED AT REEL: 057254 FRAME: 0738. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER AND CHANGE OF NAME. Recorded Sep 9, 2021
From: SKYLINE STRATEGIES II LLC; SLACK TECHNOLOGIES, INC.
To: SLACK TECHNOLOGIES, LLC
Reel/Frame 057514/0930 →
MERGER Recorded Aug 2, 2021
From: SLACK TECHNOLOGIES, INC.; SKYLINE STRATEGIES I INC.
To: SLACK TECHNOLOGIES, INC.
Reel/Frame 057254/0693 →
MERGER AND CHANGE OF NAME Recorded Aug 2, 2021
From: SKYLINE STRATEGIES II LLC; SLACK TECHNOLOGIES, INC.; SLACK TECHNOLOGIES, LLC
To: SLACK TECHNOLOGIES, LLC.
Reel/Frame 057254/0738 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2020
From: SUHAIL, SALMAN; RAPP, ROBYN
To: SLACK TECHNOLOGIES, INC.
Reel/Frame 052109/0075 →