Systems, methods and articles for providing communications and services via a peer-to-peer network over a data transport link

• US 9,503,886 B2
• Filed: 09/15/2014
• Issued: 11/22/2016
• Est. Priority Date: 05/24/2010
• Status: Active Grant

• Current Assignee: Cerence Operating Company (Cerence Inc.)
• Original Assignee: Nuance Communications, Inc. (Microsoft Corporation)
• Inventors: Bell, Jack W., Fishburn, Stephen
• Primary Examiner(s): Lai, Andrew
• Assistant Examiner(s): Ganguly, Sumitra
• Application Number:
  US14/486,837
• Publication Number:
  US 20150003258A1
• Time in Patent Office: 799 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/6418 Hybrid transport
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• 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 76/00 Connection management
• CPC Class Codes: H04W 8/183 Processing at user equipment or user record carrier
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]

Abstract

Network communications, Web-based services and customized services using the Web-based services may be provided over a peer-to-peer network from a first peer to a second peer (e.g., automobile head unit) wherein the first peer has a separate connection to a more general server-based network such as the Internet. A communications device application based on a peer communications framework component in communication with a peer network stack on the communications device may work as middleware, with a connection to both a more general server-based network such as the Internet and to an external device, such as a head unit of an automobile. Although the communications device has a separate connection out to the Internet via a general network stack co-existing on the same communications device, the peer network stack and the general network stack are not directly connected.

Claims

1. A method, comprising:

receiving, from a head unit of an automobile and by a communications device having a handheld form factor, a request for functionality from a remote server;

determining, by the communications device, whether to provide the head unit with the requested functionality using only information previously stored on the communications device;

in response to determining to provide the requested functionality using only the information previously stored on the communications device, providing the requested functionality by sending at least some of the information previously stored on the communications device to the head unit, and otherwise;

sending an updated request to the remote server for the requested functionality; and

forwarding, by the communications device, at least a portion of information received from the remote server to provide the requested functionality to the head unit.

2. The method of claim 1 wherein the sending of the updated request to the remote server for the requested functionality includes sending the request via a general network protocol stack of the communications device, and wherein the forwarding of the at least a portion of information received from the remote server to provide the requested functionality includes forwarding the at least a portion of information to the head unit via a peer-to-peer network protocol stack of the communications device.

3. The method of claim 1 wherein the information previously stored on the communications device is previously stored on the communications device based on monitoring, by the communications device, of types and patterns of requests received via a peer-to-peer network protocol stack of the communications device.

4. The method of claim 1 wherein the forwarding of the at least a portion of information received from the remote server includes forwarding the at least a portion of information to the head unit via a serial data transport link that includes at least one of a Bluetooth®

type or Universal Serial Bus (USB) type serial data transport link.

5. A method, comprising:

receiving, by a communications device, one or more requests from a head unit of an automobile for functionality from an indicated network-accessible service;

determining, by the communications device, that at least one of the one or more requests cannot be handled locally by the communications device; and

providing, by the communications device and based at least in part on the determining, a requested functionality in response to the at least one of the one or more requests by;

forwarding the at least one of the one or more requests to the indicated network-accessible service from the communications device via a general network protocol stack of the communications device;

receiving a response from the indicated network-accessible service via the general network protocol stack; and

forwarding at least a portion of the received response to the head unit via a peer-to-peer network protocol stack of the communications device that is separate from the general network protocol stack of the communications device.

6. The method of claim 5, further comprising:

receiving one or more additional requests from the head unit for functionality from the indicated network-accessible service;

determining that the one or more additional requests for the functionality from the indicated network-accessible service are to be handled locally by the communications device; and

responsive to the determination, providing the one or more additional requested functionality locally via the peer-to-peer network protocol stack of the communications device.

7. The method of claim 5 wherein network packets sent from the head unit containing the one or more requests do not include a network address of the communications device.

8. The method of claim 5, further comprising:

configuring a user interface of the head unit to visually match a corresponding user interface of the communications device by communicating information over a serial data transport link from the communications device to the head unit, the visually matched user interface including one or more controls of the communications device.

9. The method of claim 8 wherein the information included in the at least a portion of the received response forwarded to the head unit is for display on the user interface of the head unit configured to visually match the corresponding user interface of the communications device.

10. The method of claim 5, further comprising:

receiving, by the communications device and from the head unit, at least one additional request for functionality from a second indicated network-accessible service;

determining whether the second indicated network-accessible service corresponds to a service on a specified list of services; and

providing the at least one additional requested functionality only if it is determined that the second indicated network-accessible service corresponds to the service on the specified list of services.

11. The method of claim 5, further comprising:

caching at least a portion of the received response on the communications device based upon previous monitoring of types and patterns of the received one or more requests.

12. The method of claim 5 wherein the head unit and the communications device are communicatively coupled via a serial data transport link that is one of a Bluetooth®

Serial Port Profile (SPP) type serial data transport link or a Universal Serial Bus (USB) type serial data transport link.

13. A system, comprising:

at least one processor;

at least one non-transitory processor-readable storage medium coupled to the at least one processor;

a peer communications control component that is under control of the at least one processor;

a first communications component that is communicatively coupled to the peer communications control component and has a peer-to-peer network protocol stack to receive requests through a data transport connection from a head unit of an automobile and forward requests to the peer communications control component; and

a second communications component that is communicatively coupled to the peer communications control component and has a general network protocol stack to exchange communications with a server-based network that is external to the data transport connection, and wherein the second communications component;

in response to a first request for functionality of an indicated service received from the first communications component via the peer communications control component, determines that the first request cannot be satisfied locally;

based at least in part on the determination that the first request cannot be satisfied locally, forwards the first request to the indicated service via the server-based network using the general network protocol stack;

based at least in part on the forwarded first request, receives a response from the indicated service via the general network protocol stack; and

provides at least a portion of the response to the first communications component for forwarding to the head unit via the peer-to-peer network protocol stack.

14. The system of claim 13 wherein the at least one processor, the at least one non-transitory processor-readable storage medium, the peer communications control component, the first communications component, and the second communications component are all housed within a communications device having a handheld form factor.

15. The system of claim 13 further comprising a user interface having one or more user-selectable controls, wherein the peer communications control component causes a user interface of the head unit to visually match the user interface of the system.

16. The system of claim 15 wherein the peer communications control component configures the user interface of the head unit to visually match the user interface of the system by communicating information over a serial data transport link from the first communications component to the head unit for use by the head unit to configure the user interface of the head unit to visually match the user interface of the system.