Enhanced discovery for ad-hoc meetings

• US 10,432,676 B2
• Filed: 02/13/2017
• Issued: 10/01/2019
• Est. Priority Date: 06/02/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Cutler, Ross Garrett, Sinclair, Andrew Peter, Kauffman, Jonathan Adam, Krantz, Anton
• Primary Examiner(s): Hoang, Hieu T
• Application Number:
  US15/431,367
• Publication Number:
  US 20170155693A1
• Time in Patent Office: 960 Days
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04B 5/72 for local intradevice communication
• CPC Class Codes: H04L 12/1822 Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
• CPC Class Codes: H04L 12/1827 Network arrangements for conference optimisation or adaptation
• CPC Class Codes: H04L 65/1093 by adding participants; by removing participants
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 72/04 Wireless resource allocation

Abstract

Non-limiting examples disclosed herein describe processing capabilities for ad-hoc online meetings. In an implementation, an identifier is received that corresponds with a specific location. A proximity signal is received from one or more components associated with the specific location. The received proximity signal comprises one of: a modulated light signal, an audible sound, an inaudible sound and ambient noise. The identifier is validated based on a comparison of the proximity signal with a reference signal for the one or more components. A service identifier for a conferencing session is provided based on a validation of the identifier. In one example, a computing device is connected to the conference session based on receipt of a request that comprises the provided service identifier. In another example, the conference session is automatically transferred from a client computing device to a component associated with the specific location such as a room display device.

Claims

1. A method for proximity validation comprising:

receiving a query, from a client computing device, including a location identifier that corresponds with a specific location to identify a service identifier for the specific location, where the client computing device detects a transmitted proximity signal;

receiving a proximity signal, based on the transmitted proximity signal, comprising a proximity code from the client computing device, wherein the proximity signal comprises at least one of;

a modulated light signal, an audible sound, an inaudible sound, and an ambient noise;

decoding the proximity signal to obtain the proximity code;

comparing the proximity code to a reference signal to determine whether the client computing device is proximate to the specific location;

validating the location identifier in response to determining that the client computing device is proximate to the specific location; and

providing the service identifier for a conference session to the client computing device when the location identifier is validated.

2. The method of claim 1, further comprising:

automatically transferring the conference session from the client computing device to a component associated with the specific location.

3. The method of claim 1, further comprising:

requesting the proximity signal from one or more components associated with the specific location.

4. The method of claim 3, further comprising:

requesting another proximity signal from the one or more components associated with the specific location when the location identifier is determined to be un-validated, and re-validating the location identifier using the other proximity signal.

5. The method of claim 1, further comprising:

connecting the client computing device to the conference session based on receipt of a request that comprises the provided service identifier.

6. A system comprising:

at least one processor; and

a memory operatively connected with the at least one processor storing computer-executable instructions that, when executed by the at least one processor, causes the at least one processor to execute a method for proximity validation that comprises;

receiving a query, from a client computing device, including a location identifier that corresponds with a specific location to identify a service identifier for the specific location, where the client computing device detects a transmitted proximity signal;

receiving a proximity signal, based on the transmitted proximity signal, comprising a proximity code from the client computing device, wherein the proximity signal comprises one of;

a modulated light signal, an audible sound, an inaudible sound, and an ambient noise;

decoding the proximity signal to obtain the proximity code;

comparing the proximity code to a reference signal to determine whether the client computing device is proximate to the specific location;

validating the location identifier in response to determining that the client computing device is proximate to the specific location; and

providing the service identifier for a conference session to the client computing device when the location identifier is validated.

7. The system of claim 6, wherein the method, executed by the at least one processor, further comprises:

automatically transferring the conference session from the client computing device to a component associated with the specific location.

8. The system of claim 6, wherein the method, executed by the at least one processor, further comprises:

requesting the proximity signal from one or more components associated with the specific location.

9. The system of claim 8, wherein the method, executed by the at least one processor, further comprises:

requesting another proximity signal from the one or more components associated with the specific location when the location identifier is determined to be un-validated, and re-validating the location identifier using the other proximity signal.

10. The system of claim 6, wherein the method, executed by the at least one processor, further comprises:

connecting the client computing device to the conference session based on receipt of a request that comprises the provided service identifier.

11. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by at least one processor, causes the at least one processor to execute a method for proximity validation comprising:

receiving a query, from a client computing device, including a location identifier that corresponds with a specific location to identify a service identifier for the specific location, where the client computing device detects a transmitted proximity signal;

receiving a proximity signal, based on the transmitted proximity signal, comprising a proximity code from the client computing device, wherein the proximity signal comprises at least one of;

a modulated light signal, an audible sound, an inaudible sound, and an ambient noise;

decoding the proximity signal to obtain the proximity code;

comparing the proximity code to a reference signal to determine whether the client computing device is proximate to the specific location;

validating the location identifier in response to determining that the client computing device is proximate to the specific location; and

providing the service identifier for a conference session to the client computing device when the location identifier is validated.

12. The non-transitory computer-readable medium of claim 11, wherein the executed method further comprising:

automatically transferring the conference session from the client computing device to a component associated with the specific location.

13. The non-transitory computer-readable medium of claim 11, wherein the executed method further comprising:

requesting the proximity signal from one or more components associated with the specific location.

14. The non-transitory computer-readable medium of claim 11, wherein the executed method further comprising:

requesting another proximity signal from one or more other components associated with the specific location when the location identifier is determined to be un-validated, and re-validating the location identifier using the other proximity signal.

15. The non-transitory computer-readable medium of claim 11, wherein the proximity signal comprises the identifier that corresponds to the specific location.

16. The non-transitory computer-readable medium of claim 11, wherein the executed method further comprising:

connecting the client computing device to the conference session based on receipt of a request that comprises the provided service identifier.