# US 2014/0369483 A1 · Using physical gestures to initiate call transfers between devices

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0369483 A1
- Document ID: US20140369483A1
- Status: Published application
- Kind: A1
- Application number: 13/918,530
- Filed: 2013-06-14
- Published: 2014-12-18
- Earliest claimed: 2013-06-14
- Assignees: Microsoft Technology Licensing, LLC
- Inventors: Andrew William Lovitt; Jason Ryan Farmer; Michael Hall
- Web page: https://patentgrep.com/patent/US20140369483A1

## CPC

- G06F 3/017: {Gesture based interaction, e.g. based on a set of recognized hand gestures (interaction based on gestures traced on a digitiser G06F3/04883)}
- H04M 1/006: {Call diverting means}
- H04M 3/56: Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities (video conference systems H04N7/15)
- H04M 3/564: {whereby the feature is a sub-conference}
- H04M 3/567: {Multimedia conference systems}
- H04M 3/58: Arrangements for transferring received calls from one subscriber to another; Arrangements affording interim conversations between either the calling or the called party and a third party (substation line holding circuits H04M1/80)
- H04W 4/16: Communication-related supplementary services, e.g. call-transfer or call-hold
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04M 1/6066: {including a wireless connection}
- H04M 2203/2094: Proximity
- H04M 2203/5009: Adding a party to an existing conference
- H04M 2203/5018: Initiating a conference during a two-party conversation, i.e. three-party service or three-way call
- H04M 2203/5027: Dropping a party from a conference
- H04M 2250/02: including a Bluetooth® interface
- H04M 2250/04: including near field communication means, e.g. RFID
- H04W 4/023: {using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds}
- H04W 4/027: {using movement velocity, acceleration information}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## 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

### Claim 1

A method of joining a client device to an existing call, comprising:
detecting a physical gesture between a first client device a second client device, wherein the first client device is participating in a call at a time of detection of the physical gesture, and wherein the second client device is not participating in the call at the time of the detection of the physical gesture; and
responsive to the detection of the physical gesture, initiating participation of the second client device in the call, wherein initiation of the participation of the second client device in the call enables the second client device to be used by a user to participate in the call.

### Claim 2 (depends on 1)

The method of claim 1, wherein initiating the participation of the second client device in the call further comprises causing the call to transfer from the first client device to the second client device.

### Claim 3 (depends on 1)

The method of claim 1, wherein initiating the participation of the second client device in the call further comprises causing the second client device to join the call while the first client device continues to participate in the call.

### Claim 4 (depends on 1)

The method of claim 1, further comprising, responsive to the participation of the second client device in the call being initiated, sourcing the call to the second client device from the first client device.

### Claim 5 (depends on 1)

The method of claim 1, wherein initiating the participation of the second client device in the call further comprises transmitting a request to a server from the first client device, wherein the request causes the server to route the call to the second client device.

### Claim 6 (depends on 1)

The method of claim 1, wherein initiating the participation of the second client device in the call further comprises transmitting a signal to a switching center from the first client device, wherein the signal causes the switching center to route the call to the second client device.

### Claim 7 (depends on 1)

The method of claim 1, wherein initiating the participation of the second client device in the call further comprises transmitting call access information to the second client device, wherein the second client device employs the call access information to connect to the call.

### Claim 8 (depends on 1)

The method of claim 1, wherein the physical gesture comprises a tap between the second client device and the first client device.

### Claim 9 (depends on 1)

The method of claim 1, wherein the physical gesture comprises at least one of:
a tap between an agent of the first client device and the second client device;
a tap between the first client device and an agent of the second client device; or
a tap between the agent of the first client device and the agent of the second client device.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
identifying a gesture type of the physical gesture from a set of possible gesture types, wherein the possible gesture types in the set correspond to differing respective actions pertaining to the call; and
causing a particular action pertaining to the call corresponding to the gesture type responsive to the detection of the physical gesture and identification of the gesture type.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
discovering capabilities of the second client device;
selecting a connection technique based upon the capabilities of the second client device; and
initiating the participation of the second client device in the call utilizing the connection technique selected based upon the capabilities of the second client device.

### Claim 12 (depends on 1)

The method of claim 1, further comprising discerning an identifier of the second client device when the physical gesture between the second client device and the first client device is detected, wherein the identifier is utilized to initiate the participation of the second client device in the call.

### Claim 13

A client device, comprising:
a sensing component that detects a tap between the client device and a disparate client device, wherein the client device is participating in a call at a time of detection of the tap, and wherein the disparate client device is not participating in the call at the time of the detection of the tap; and
an access instigation component that initiates participation of the disparate client device in the call responsive to the detection of the tap between the client device and the disparate client device, wherein initiation of the participation of the disparate client device in the call enables the disparate client device to be used by a user to participate in the call.

### Claim 14 (depends on 13)

The client device of claim 13, further comprising a type evaluation component that identifies a tap type of the tap from a set of possible tap types, wherein the possible tap types in the set correspond to differing respective actions pertaining to the call, and wherein the access instigation component causes a particular action pertaining to the call corresponding to the tap type responsive to the detection of the tap and identification of the tap type.

### Claim 15 (depends on 14)

The client device of claim 14, wherein a first possible tap type corresponds to a transfer action where the call is transferred from the client device to the disparate client device, and wherein a second possible tap type corresponds to a conference action where the disparate client device is joined to the call while the client device continues to participate in the call.

### Claim 16 (depends on 14)

The client device of claim 14, wherein the type evaluation component identifies the tap type of the tap as a function of at least one of a location on a housing of the client device at which the tap is detected, an orientation of the disparate client device with respect to the client device during the tap, a time duration of the tap, or a number of occurrences of the tap.

### Claim 17 (depends on 13)

The client device of claim 13, wherein the access instigation component transmits a request to a server from the client device responsive to the detection of the tap between the client device and the disparate client device, wherein the request causes the server to route the call to the second client device.

### Claim 18

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.

### Claim 19

(canceled)

### Claim 20 (depends on 18)

The method of claim 18, 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.

### Claim 21 (depends on 10)

The method of claim 10, further comprising identifying the gesture type of the physical gesture as a function of at least one of a location on a housing at which the physical gesture is detected, a duration of the physical gesture, or a number of occurrences of the physical gesture.
