Process for real-time data exchange between users on a phone call

• US 9,866,684 B2
• Filed: 02/16/2015
• Issued: 01/09/2018
• Est. Priority Date: 02/16/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Eilts, Jason, Chardon, Alvin, Greenier, Ben
• Primary Examiner(s): Williams, Kimberly A
• Application Number:
  US14/623,057
• Publication Number:
  US 20160241711A1
• Time in Patent Office: 1,058 Days
• Field of Search: 455415
• CPC Class Codes: H04M 1/575 Means for retrieving and displaying personal data about calling party
• CPC Class Codes: H04M 1/724 User interfaces specially adapted for cordless or mobile telephones
• CPC Class Codes: H04M 1/72451 according to schedules, e.g. using calendar applications
• CPC Class Codes: H04M 1/72454 according to context-related or environment-related conditions
• CPC Class Codes: H04M 2203/351 Pre or post-call/conference information service
• CPC Class Codes: H04M 2203/352 In-call/conference information service
• CPC Class Codes: H04M 2250/10 including a GPS signal receiver
• CPC Class Codes: H04M 2250/12 including a sensor for measuring a physical value, e.g. temperature or motion
• CPC Class Codes: H04M 3/42042 Notifying the called party of information on the calling party details within substation equipment H04M1/57, signalling details H04Q3/72
• CPC Class Codes: H04M 3/42093 Notifying the calling party of information on the called or connected party
• CPC Class Codes: H04M 7/0036 where the data service is an information service
• CPC Class Codes: H04W 4/16 Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: Y02B 70/30 Systems integrating technologies related to power network operation and communication or information technologies for improving the carbon footprint of the management of residential or tertiary loads, i.e. smart grids as climate change mitigation technology in the buildings sector, including also the last stages of power distribution and the control, monitoring or operating management systems at local level
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A process for real-time data exchange allows for sharing data, including metadata such as user data and phone data, between multiple handsets so that handsets may automatically display such data upon initiation or establishment of a telephone call, and in some arrangements throughout the life of the call. In this way, the need for subsequent data transmissions is reduced or eliminated, making bandwidth usage more efficient and conserving battery power.

Claims

1. A method performed by a service that is operable on devices engaged in a network communication, comprising:

a. configuring a network accessible service to interoperate with respective local clients on each of two or more devices, including a first and second device, each respective local client gathering local data associated with the respective device;

b. during initiation of a voice call between the first and second devices;

i. identifying metadata that has relevance to the voice call, the metadata being derived from the selected local data; and

ii. filtering the identified metadata to eliminate metadata that does not meet a predetermined freshness criteria, wherein the predetermined freshness criteria varies for different types of metadata;

iii. transmitting the metadata meeting the predetermined freshness criteria for the corresponding type of metadata to the second device using the service for display on the second device, wherein data transmissions are reduced for less-frequently-varying data; and

iv. transmitting default data having relevance to the voice call, the default data set by a user for at least one data type for the first device for which no analysis is available for metadata identified in said identifying step.

2. The method of claim 1, further comprising downloading each local client to the respective device.

3. The method of claim 1, further comprising continuing to gather local data and performing the transmitting the identified metadata step during the voice call.

4. The method of claim 1, wherein the identifying metadata that has relevance to the voice call includes identifying metadata pertaining to a low battery life of the first device, data pertaining to an upcoming appointment stored as calendar data within the first device, data about a proximity of the first device to the second device, data about whether the first device is using an internal speaker, a speakerphone, or a wireless headset, contact data associated with a user of the first device, or combinations thereof.

5. The method of claim 1, wherein the service is configured to receive local data from a wearable device in voice call with the first device.

6. The method of claim 1, wherein the service is implemented by a service component on a cloud server that exposes a REST API to respective client service components operating on the devices.

7. The method of claim 1, further comprising transmitting a file between the first and second devices using the service.

8. The method of claim 7, wherein the file is a meeting invitation.

9. The method of claim 1, wherein the identifying metadata that has relevance to the voice call includes identifying metadata pertaining to an upcoming appointment stored as calendar data within the first device.

10. A method performed by a first device used in communication with a second device, comprising:

a. operating a local data gathering client on the first device, the operating including collecting data from one or more data sources associated with the first device, and identifying a portion of the same as relevant to a communication, the identifying based on comparing the collected data to one or more criteria;

b. transmitting the identified data as first metadata to a service;

c. during initiation of a communication from the first device to a second device, identifying a portion of real-time data as relevant to a communication using the local data gathering client, the identifying based on comparing the real-time data to one or more criteria, filtering the identified relevant real-time data to eliminate data that does not meet a predetermined freshness criteria, wherein the predetermined freshness criteria varies for different types of metadata, and transmitting the filtered identified real-time data meeting the freshness criteria as second metadata to the service, wherein data transmissions are reduced for less-frequently-varying data; and

d. transmitting default data relevant to the communication, the default data set by a user for at least one data type for which data is unavailable to the local data gathering client,

such that during the initiation of the communication, at least a portion of the first or second metadata, or both, and default data, are transmitted to the second device from the service for display on a user interface of the second device.

11. The method of claim 10, wherein the one or more data sources include one or more selected from the group consisting of:

an accelerometer, GPS circuitry, a database for a calendar application, settings data, battery data, local Wi-Fi or other geolocation data, phone application data, exercise application data, data input by a user on a user interface, data from a wearable device in communication with the first device, and combinations thereof.

12. The method of claim 10, wherein the real-time data is received from a source selected from the group consisting of:

GPS circuitry, a database for a calendar application, battery data, and combinations thereof.

13. The method of claim 10, wherein the service is configured to perform an additional step of determining which of the first or second metadata, or both, are identified as relevant to the communication and provided to the second device for display.

14. The method of claim 13, wherein the service performs an urgency determination, and wherein the urgency determination is based on metadata pertaining to an upcoming appointment stored as calendar data within the first device, data about a proximity of the first device to the second device, location data associated with the first device, contact data associated with a user of the first device, or combinations thereof.

15. A local device having telephony capabilities for making and receiving calls to and from a remote device, comprising:

a. one or more processors;

b. a user interface for displaying call information including selected metadata;

c. a network interface for sending and receiving information pertaining to a call; and

d. a memory device storing computer-executable instructions which, when executed by the one or more processors, implements;

i. a local data gathering client configured for harvesting data from one or more data sources available to the local device, the harvesting being performed in real time during initiation or pendency of the call responsively to one or more relevancy criteria,

ii. a service interface for communicating the harvested data to a remote service over the network interface and for receiving data from the remote service, the communicating being performed according to variability of the harvested data, and for transmitting default data having relevance to the call to the remote device, the default data set by a user for at least one data type for the local device for which no analysis is available for data harvested by the local data gathering client, and

iii. a local data rendering client for determining which data received from the remote service is rendered as selected metadata on the user interface.

16. The device of claim 15, wherein the one or more data sources include one or more selected from the group consisting of:

an accelerometer, GPS circuitry, a database for a calendar application, settings data, battery data, local Wi-Fi or other geolocation data, phone application data, exercise application data, data input by a user on a user interface, data from a wearable device in communication with the local device, and combinations thereof.

17. The device of claim 16, wherein the remote service is configured to analyze data from at least two data sources, and to transmit an icon or message for display on a user interface of the remote device based on the analysis.