Efficient headunit communication integration

• US 9,730,254 B2
• Filed: 04/23/2015
• Issued: 08/08/2017
• Est. Priority Date: 10/15/2009
• Status: Active Grant

• Current Assignee: Karma Automotive LLC (Wanxiang Group Corporation)
• Original Assignee: Airbiquity Incorporated
• Inventors: Hong, Leon, O'Meara, Mike, Pawar, Sagar
• Primary Examiner(s): TISSOT, ADAM D
• Application Number:
  US14/694,803
• Publication Number:
  US 20150230277A1
• Time in Patent Office: 838 Days
• Field of Search: 701 36, 701 1, 701 2, 701 334, 701425, 701454, 701 49, 455 306, 455345, 455 303, 455411, 715700, 340 1324, 340461, 340531, 700 17, 710 2
• CPC Class Codes: G01C 21/362 received from an external device or application, e.g. PDA, mobile phone or calendar application
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• 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: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04M 1/6083 by interfacing with the vehicle audio system
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 4/40 for vehicles, e.g. vehicle-to-pedestrians [V2P]
• CPC Class Codes: H04W 4/48 for in-vehicle communication
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 84/22 with access to wired networks
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

In an example, the mobile device may be configured to determine whether to authorize a request for the vehicle head unit to utilize a resource of the mobile device. The mobile device may be configured to utilize a proxy of the mobile device to establish a connection with a destination in response to determining to authorize the request.

Claims

1. A method, comprising:

receiving, at a mobile device, a request for a motor vehicle component coupled to the mobile device by at least one of a wire or a short range wireless transmitter;

responsive to receiving the request, determining, based on information about a destination of the request, whether to permit the motor vehicle component to utilize a resource of the mobile device, the resource including a long range wireless transmitter of the mobile device;

authorizing the request for the motor vehicle component to utilize the resource of the mobile device based on a result of the determination; and

utilizing a proxy of the mobile device to establish a connection with the destination if the request is authorized.

2. The method of claim 1, wherein determining, based on information about the destination of the request, whether to permit the motor vehicle component to utilize the resource of the mobile device further comprises comparing an identifier corresponding to the destination to a predefined list.

3. The method of claim 1, wherein determining, based on information about the destination of the request, whether to permit the motor vehicle component to utilize the resource of the mobile device further comprises:

determining, by the motor vehicle component, whether a subscription/account state corresponding to the request corresponds to a predefined subscription/account state; and

in response to determining, by the motor vehicle component, that the subscription/account state corresponds to the predefined subscription/account state, determining, by the mobile device, whether an identifier corresponding to the destination corresponds to an entry in a predefined list.

4. The method of claim 3, further comprising:

transmitting, by the motor vehicle component, a SOCKS (SOCKet Secure) proxy chaining communication to the mobile device in response to determining, by the motor vehicle component, that the subscription/account state corresponds to the predefined subscription/account state; and

recognizing, by the mobile device, the destination from the received SOCKS proxy chaining communication.

5. The method of claim 3, further comprising:

opening, by the motor vehicle component, a first socket to a well known port in response to determining, by the motor vehicle component, that the subscription/account state corresponds to the predefined subscription/account state; and

opening, by the mobile device, a second socket in response to determining, by the motor vehicle component, that the identifier corresponding to the destination corresponds to the entry in the predefined list.

6. The method of claim 1, further comprising:

identifying a port on which the request is received at the mobile device;

determining whether a mapping includes an entry corresponding to the identified port; and

in response to determining that the mapping includes the entry, identifying a value usable for establishing the connection to the destination responsive to data of the entry.

7. The method of claim 1, wherein the proxy of the mobile device comprises a first proxy server that is different than a second proxy server that transmitted the request from the motor vehicle component.

8. The method of claim 7, wherein the first proxy server comprises a first SOCKS proxy server.

9. The method of claim 1, further comprising:

identifying a port on which the request is received at the mobile device;

determining whether a mapping includes an entry corresponding to the identified port; and

in response to determining that the mapping includes the entry, identifying a value usable to establish the connection to the destination responsive to information of the entry.

10. The method of claim 9, further comprising:

checking, by the mobile device, a subscription/account state associated with the request; and

wherein the request is authorized in response to determining that the mapping includes the entry and the subscription/account state corresponds to a predefined subscription/account state.

11. A memory device having instructions stored thereon that, in response to execution by a processing device of a mobile device, cause the processing device to perform operations including:

identifying, at the mobile device, a request for a motor vehicle component coupled to the mobile device by at least one of a wire or a short range wireless transmitter;

responsive to identifying the request, determining, based on information about a destination of the request, whether to permit the motor vehicle component to utilize a resource of the mobile device, the resource including a long range wireless transmitter of the mobile device;

authorizing the request for the motor vehicle component to utilize the resource of the mobile device based on a result of the determination; and

utilizing a proxy of the mobile device to establish a connection with the destination if the request is authorized.

12. The memory device of claim 11, wherein determining based on the information about the destination of the request, whether to permit the motor vehicle component to utilize the resource of the mobile device further comprises determining, by the mobile device, whether an identifier corresponding to the destination corresponds to an entry in a predefined list only if a subscription/account state corresponding to the request corresponds to a predefined subscription/account state.

13. The memory device of claim 12, wherein the operations further comprise:

responsive to receiving a SOCKS (SOCKet Secure) proxy chaining communication originating from the motor vehicle component, recognizing, by the mobile device, the destination from the received SOCKS proxy chaining communication.

14. The memory device of claim 11, wherein the operations further comprise determining whether an identifier corresponding to the destination is included in a white list.

15. The memory device of claim 11, wherein the operations further comprise:

identifying a port on which the request is received at the mobile device;

determining whether a mapping includes an entry corresponding to the identified port; and

in response to determining that the mapping includes the entry, identifying a value usable to establish the connection to the destination responsive to data of the entry.

16. The memory device of claim 15, wherein the operations further comprise:

opening a socket based on the corresponding entry.

17. The memory device of claim 11, wherein the operations further comprise:

opening a socket in response to determining, by the motor vehicle component, that an identifier corresponding to the destination corresponds to the entry in the predefined list.

18. The memory device of claim 11, wherein the proxy of the mobile device comprises a first proxy server that is different than a second proxy server that transmitted the request from the motor vehicle component.

19. The memory device of claim 11, wherein the first proxy server comprises a first SOCKS proxy server.