IP Library › Granted Patent US 9,100,488
Granted Patent B2
US 9,100,488 · App. 13/918,530 · Granted Aug 4, 2015

Using physical gestures to initiate call transfers between devices

Inventors: Andrew William Lovitt (Redmond, WA); Jason Ryan Farmer (Snohomish, WA); Michael Hall (Snohomish, WA)
Assignee: Microsoft Technology Licensing, LLC
H04M3/56G06F3/017H04M1/006H04M3/564H04M3/58H04W4/16H04M1/6066H04M2203/2094H04M2203/5009H04M2250/02
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 9,100,488
App. No.
13/918,530
Granted
Aug 4, 2015
Kind
B2
Abstract

Various technologies described herein pertain to using detected physical gestures to cause calls to transfer between client devices. A physical gesture between a first client device and a second client device can be detected (e.g., utilizing the first client device, the second client device, a disparate client-side device, a server, etc.). The first client device participates in a call, while the second client device is not participating in the call at a time of the detection of the physical gesture. Responsive to detection of the physical gesture, participation of the second client device in the call can be initiated. Participation of the second client device in the call can be initiated by causing the call to transfer from the first client device to the second client device or causing the second client device to join the call while the first client device continues to participate in the call.

Claims (48)

1. A method of routing a call, comprising:

transmitting data packets that are part of the call to a first client device;

receiving a request to route the data packets that are part of the call to a second client device, wherein the request is responsive to a detected physical gesture between the first client device and the second client device, and wherein the data packets that are part of the call are not routed to the second client device prior to receipt of the request;

determining whether to grant the request or deny the request; and

responsive to a determination to grant the request:

transmitting the data packets that are part of the call to the second client device;

determining, based at least in part upon the request, whether to continue to transmit the data packets that are part of the call to the first client device or discontinue transmission of the data packets that are part of the call to the first client device; and

one of:

continuing to transmit the data packets that are part of the call to the first client device; or

discontinuing the transmission of the data packets that are part of the call to the first client device.

2. The method of claim 1 , further comprising determining whether to grant the request or deny the request utilizing a predefined policy based upon conditions of at least one of the call, the first client device, or the second client device.

3. The method of claim 1 , further comprising:

transmitting data packets that are part of a disparate call to the second client device prior to receiving the request; and

responsive to the determination to grant the request, combining the call and the disparate call.

4. The method of claim 1 , further comprising:

transmitting data packets that are part of a disparate call to the second client device prior to receiving the request; and

responsive to the determination to grant the request, discontinuing transmission of the data packets that are part of the disparate call to the second client device.

5. The method of claim 1 , further comprising detecting the physical gesture between the first client device and the second client device based on respective data received from the first client device and the second client device.

6. The method of claim 5 , wherein the respective data received from the first client device and the second client device comprise respective outputs of sensors of the first client device and the second client device within a period of time.

7. The method of claim 1 , wherein the request to route the data packets that are part of the call to the second client device is received from the first client device.

8. The method of claim 1 , wherein the request to route the data packets that are part of the call to the second client device is received from the second client device.

9. The method of claim 1 , wherein the request specifies an Internet Protocol (IP) address of the second client device.

10. The method of claim 1 , further comprising generating call access information, the call access information being provided to the second client device, and the call access information being utilized by the second client device to generate the request.

11. The method of claim 1 , further comprising determining whether to grant the request or deny the request based upon at least one of a location of the first client device, a location of the second client device, a type of the first client device, a type of the second client device, an identity of the first client device, an identity of the second client device, whether the first client device is domain joined, or whether the second client device is domain joined.

12. The method of claim 1 , further comprising determining whether to continue to transmit the data packets that are part of the call to the first client device or discontinue the transmission of the data packets that are part of the call to the first client device based upon at least one of a location of the first client device, a location of the second client device, a type of the first client device, a type of the second client device, an identity of the first client device, an identity of the second client device, whether the first client device is domain joined, or whether the second client device is domain joined.

13. The method of claim 1 , further comprising determining whether to grant the request or deny the request based upon a type of physical gesture detected between the first client device and the second client device.

14. The method of claim 13 , wherein the request comprises information specifying the type of the physical gesture detected between the first client device and the second client device.

15. The method of claim 1 , further comprising determining whether to continue to transmit the data packets that are part of the call to the first client device or discontinue the transmission of the data packets that are part of the call to the first client device based upon a type of physical gesture detected between the first client device and the second client device.

16. A call server, comprising:

an interface component that:

transmits data packets that are part of a call to a first client device;

receives a request to route the data packets that are part of the call to a second client device, wherein the request is responsive to a detected physical gesture between the first client device and the second client device, and wherein the data packets that are part of the call are not routed to the second client device prior to receipt of the request; and

transmits the data packets that are part of the call to the second client device responsive to granting the request; and

a connection management component that, responsive to granting the request and based at least in part upon the request, determines whether the interface component continues to transmit the data packets that are part of the call to the first client device or discontinues transmission of the data packets that are part of the call to the first client device.

17. The call server of claim 16 , the connection management component further determines whether to grant the request or deny the request.

18. The call server of claim 16 , further comprising a sensing component that detects the physical gesture between the first client device and the second client device based on respective data received from the first client device and the second client device.

19. A method of routing a call, comprising:

transmitting data packets that are part of the call to a first client device;

receiving respective data from the first client device and a second client device;

detecting a physical gesture between the first client device and the second client device based on the respective data received from the first client device and the second client device, wherein the data packets that are part of the call are not routed to the second client device prior to detection of the physical gesture between the first client device and the second client device;

responsive to the detection of the physical gesture between the first client device and the second client device, determining whether to transmit the data packets that are part of the call to the second client device; and

responsive to a determination to transmit the data packets that are part of the call to the second client device:

transmitting the data packets that are part of the call to the second client device;

determining whether to continue to transmit the data packets that are part of the call to the first client device or discontinue transmission of the data packets that are part of the call to the first client device; and

one of:

continuing to transmit the data packets that are part of the call to the first client device; or

discontinuing the transmission of the data packets that are part of the call to the first client device.

20. The method of claim 19 , further comprising determining whether to continue to transmit the data packets that are part of the call to the first client device or discontinue transmission of the data packets that are part of the call to the first client device utilizing a predefined policy based upon conditions of at least one of the call, the first client device, or the second client device.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2015
From: MICROSOFT CORPORATION
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 035867/0773 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2015
From: LOVITT, ANDREW WILLIAM; FARMER, JASON RYAN; HALL, MICHAEL
To: MICROSOFT CORPORATION
Reel/Frame 035876/0760 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2015
From: MICROSOFT CORPORATION
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 039025/0454 →
Continuity (1)
Related Publication 20140369483A1 · Dec 18, 2014