INTERACTING WITH DEVICES BASED ON PHYSICAL DEVICE-TO-DEVICE CONTACT

• US 20090153342A1
• Filed: 01/11/2008
• Published: 06/18/2009
• Est. Priority Date: 12/12/2007
• Status: Active Grant

• Current Assignee: Sony Corporation (Sony Group Corp.)
• Original Assignee: Sony Ericsson Mobile Communications USA Incorporated (Sony Group Corp.)
• Inventors: THORN, Ola Karl
• Granted Patent: US 8,482,403 B2
• Time in Patent Office: Days
• US Class Current: 340/669
• CPC Class Codes: G06F 1/1626 with a single-body enclosure integrating a flat display, e.g. Personal Digital Assistants [PDAs]
• CPC Class Codes: G06F 1/1684 Constructional details or arrangements related to integrated I/O peripherals not covered by groups G06F1/1635 - G06F1/1675
• CPC Class Codes: G06F 1/1694 the I/O peripheral being a single or a set of motion sensors for pointer control or gesture input obtained by sensing movements of the portable computer
• CPC Class Codes: G06F 1/1698 the I/O peripheral being a sending/receiving arrangement to establish a cordless communication link, e.g. radio or infrared link, integrated cellular phone details of antennas disposed inside a computer H01Q1/2266
• CPC Class Codes: G06F 2200/1636 Sensing arrangement for detection of a tap gesture on the housing
• CPC Class Codes: G06F 3/011 Arrangements for interaction with the human body, e.g. for user immersion in virtual reality blind teaching G09B21/00
• CPC Class Codes: H04M 1/72412 using two-way short-range wireless interfaces
• CPC Class Codes: H04M 1/7243 with interactive means for internal management of messages
• CPC Class Codes: H04M 2250/12 including a sensor for measuring a physical value, e.g. temperature or motion telephones including GPS signal receivers H04M2250/10
• CPC Class Codes: H04M 2250/64 file transfer between terminals download of applications H04M1/72406; transfer of messages, e.g. SMS, e-mail or MMS H04M1/7243
• CPC Class Codes: H04W 4/21 for social networking applications

Abstract

A first device may receive a signal from a sensor coupled to the first device, determine whether the first device is tapped one or more times against a second device, send a message to the second device when it is determined that the first device has been tapped one or more times against the second device, determine if the one or more taps are valid user input based on a response from the second device, and perform an application specific action when the one or more taps are valid user input.

Claims

1. A method comprising:

receiving a signal from a sensor coupled to a first device;

determining whether the first device is tapped one or more times against a second device;

sending a message to the second device when it is determined that the first device has been tapped one or more times against the second device;

determining if the one or more taps are valid user input based on a response from the second device; and

performing an application specific action when the one or more taps are valid user input.

2. The method of claim 1, where receiving a signal includes:

receiving the signal from an accelerometer.

3. The method of claim 2, where determining whether the first device is tapped one or more times against the second device includes:

determining whether samples of the signal match a predetermined acceleration pattern.

4. The method of claim 1, where sending a message includes:

obtaining parameters regarding the one or more taps; and

sending the parameters to the second device.

5. The method of claim 4, where obtaining parameters includes:

obtaining locations of the one or more taps on a surface of the first device;

determining time between two consecutive taps;

or

determining time of occurrence of at least one of the one or more taps.

6. The method of claim 4, where determining if the one or more taps are valid user input includes:

receiving the response, the response indicating whether the sent parameters match parameters that are obtained from one or more taps on the second device.

7. The method of claim 1, where determining if the one or more taps are valid user input includes:

receiving parameters associated with one or more taps on the second device in response to the message;

determining if the received parameters match parameters that are extracted from the signal when the first device is tapped one or more times against the second device; and

determining whether the one or more taps are valid by comparing the received parameters to the extracted parameters.

8. The method of claim 1, where performing an application specific action includes:

coordinating at least one of an audio task or a visual task with the second device.

9. The method of claim 1, where performing an application specific action includes one of:

sending an audio signal to the second device for output by a speaker;

or

sending a video signal to the second device for display.

10. The method of claim 1, where performing an application specific action includes at least one of:

receiving personal contact information from the second device;

conducting a commercial transaction with the second device;

or

receiving a video clip, audio clip, image, or text from the second device.

11. A device comprising:

a sensor; and

a processor configured to;

receive a signal from the sensor;

detect taps based on the signal;

extract parameters that are associated with the detected taps;

send a request to a second device to verify if the extracted parameters match parameters that correspond to taps on the second device;

determine if the detected taps are valid user input based on a response from the second device; and

interact with the second device over a communication channel when the taps are valid user input.

12. The device of claim 11, where the parameters include at least one of:

time between consecutive taps;

or

time of occurrence of a tap.

13. The device of claim 11, where the sensor includes at least one of:

an accelerometer;

or

an electric field sensor.

14. The device of claim 11, where the second device includes at least one of:

a cell phone with a display or a speaker;

a headset;

or

a laptop.

15. The device of claim 11, where the device comprises:

a cell phone.

16. The device of claim 11, where the communication channel includes:

a Bluetooth communication channel.

17. The device of claim 11, where the request includes the extracted parameters and the response includes information that indicates whether the extracted parameters match parameters that correspond to taps on the second device.

18. The device of claim 11, where the response includes parameters that are obtained from taps by the second device.

19. A device comprising:

means for sensing an acceleration of the device and outputting acceleration values;

means for receiving the acceleration values from the means for sensing the acceleration;

means for detecting taps that are produced by a first device and a second device based on the acceleration values;

means for sending a message to the second device when the taps are detected;

means for determining if the detected taps are valid user input based on a response from the second device; and

means for interacting with the second device when the taps are valid user input.

20. The device of claim 19, where the message includes:

time of occurrence of at least one of the detected taps.