Centralized management of motor vehicle software applications and services

• US 8,838,332 B2
• Filed: 05/11/2010
• Issued: 09/16/2014
• Est. Priority Date: 10/15/2009
• Status: Active Grant

• Current Assignee: Karma Automotive LLC (Wanxiang Group Corporation)
• Original Assignee: Airbiquity Incorporated
• Inventors: Zhao, Lee, Moinzadeh, Kamyar, Hong, Leon L.
• Primary Examiner(s): TISSOT, ADAM D
• Application Number:
  US12/777,989
• Publication Number:
  US 20110093154A1
• Time in Patent Office: 1,589 Days
• Field of Search: 701/36, 701/1, 701/2, 701/24, 701/29.1, 701/29.6, 701/31.4, 701/33.2, 701/34.3, 701/425, 701/454, 455/411, 455/420, 455/457, 715/700, 715/716, 715/740, 715/741, 715/744, 715/771, 717/172, 340/426.19, 340/426.22, 340/426.23, 340/426.24, 340/461, 340/572.1, 340/5.31, 340/5.8, 700/17, 700/83
• US Class Current: 701/36
• CPC Class Codes: B60R 25/00 Fittings or systems for preventing or indicating unauthorised use or theft of vehicles locks for vehicles E05B77/00-E05B85/00
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: H04M 1/6091 including a wireless interface
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/724098 Interfacing with an on-board device of a vehicle for hands-free speaking in vehicles H04M1/6075
• CPC Class Codes: H04M 1/72463 to restrict the functionality of the device

Abstract

In one example, a network device stores a mapping of application operation modes to vehicle conditions such as a first condition of the vehicle powered but not moving and a second condition of the vehicle moving. The network device receives a wirelessly transmitted request for a particular application to utilize an interface powered by the vehicle. The network device compares an application identifier specified by the received request to the mapping. The network device then identifies a portion of the vehicle interface according to the comparison and signals control software on the vehicle to grant the particular application access to only the identified portion of the vehicle interface itself. The application can reside on the mobile device and utilize the vehicle interface as an extended interface, or the application can reside on the vehicle.

Claims

1. A memory encoded with instructions for centralized management of a plurality of vehicle user interfaces using a central server located remotely from the plurality of vehicle user interfaces, each of the vehicle user interfaces associated with a different vehicle, wherein the instructions, if executed, result in:

storing a mapping of vehicle conditions to resources of the plurality of vehicle user interfaces, wherein the vehicle conditions include at least a first condition of powered but not moving and a second condition of moving;

at the central server, receiving a request over a cellular telephone network for a particular application, wherein the received request is for one of the vehicle user interfaces and includes an application identifier;

at the central server, comparing the received request to the mapping and identifying a resource of said vehicle user interface responsive to the comparison;

transmitting a first control signal from the central server to control software on a corresponding one of the vehicles to permit the particular application to access only the identified resource of said vehicle user interface;

storing a plurality of graphical user interfaces remotely from the vehicles, wherein a first one of the plurality of graphical user interfaces is configured for a first vehicle configuration and a second one of the plurality of graphical user interfaces is configured for a second vehicle configuration that is different than the first vehicle configuration;

wherein the first vehicle configuration corresponds to a vehicle component to which the second vehicle configuration does not correspond;

probing with the central server the control software or said vehicle user interface; and

transmitting a second control signal from the central server to cause said vehicle user interface to display a particular one of the plurality of graphical user interfaces based on a result of said probing;

wherein said probing elicits a response specifying a make, model, and year of the corresponding vehicle, and wherein the instructions, if executed, result in selecting the particular graphical user interface responsive to the specified make, model, and year.

6. The memory of claim 1, wherein the instructions, if executed, result in:

receiving an indication of a new application to utilize said vehicle user interface as an extended interface for a portable mobile device or to install on said vehicle user interface;

checking for a graphical user interface update corresponding to the application identifier in response to receiving the indication; and

pushing a new graphical user interface to the corresponding vehicle responsive to said checking, wherein the new graphical user interface is to be installed and displayed on said vehicle user interface of the plurality of vehicle user interfaces.

7. The memory of claim 1, wherein the instructions, if executed, result in:

in response to said vehicle user interface of the plurality of vehicle user interfaces communicatively coupling to a mobile device, obtaining a phone number of the mobile device;

matching the obtained phone number to one of a plurality of profiles;

determining whether the matched profile is subject to parental control; and

transmitting a parental control message to the corresponding vehicle responsive to said determination.

8. The memory of claim 7, wherein the parental control message identifies a blocked application.

9. The memory of claim 7, wherein the parental control message identifies a conditionally blocked application, wherein the condition is based on a caller ID field value of an incoming call.

10. The memory of claim 1, wherein the particular application resides on a head unit of the corresponding vehicle.

11. The memory of claim 10, wherein the instructions, if executed, result in:

generating a first list of applications by accumulating applications submitted by third parties for operation with the corresponding vehicle;

generating a second list that is a subset of the applications from the first list based on vehicle manufacturer selections from the first list;

configuring an internet accessible user web portal with a web interface populating each of the download directories with a different combination of selections from the second list, wherein the second list is displayed on the internet accessible user web portal; and

configuring the internet accessible user web portal with a login procedure to identify a user and provide the user control over a particular one of the download directories based on the identification.

12. The memory of claim 11, wherein the instructions, if executed, result in:

setting a profile for a particular one of the identities as having parental control over a profile of a different user.

18. The memory of claim 1, wherein the probing indicates whether said vehicle component is located in the corresponding vehicle, and wherein the instructions, if executed, result in:

responsive to an indication that said vehicle component is located in the corresponding vehicle, causing said vehicle user interface to display the first one of the plurality of graphical user interfaces; and

responsive to an indication that said vehicle component is not located in the corresponding vehicle, causing said vehicle user interface to display the second one of the plurality of graphical user interfaces.

2. A memory encoded with instructions for centralized management of a plurality of vehicle user interfaces using a central server located remotely from the plurality of vehicle user interfaces, each of the vehicle user interfaces associated with a different vehicle, wherein the instructions, if executed, result in:

storing a mapping of vehicle conditions to resources of the plurality of vehicle user interfaces, wherein the vehicle conditions include at least a first condition of powered but not moving and a second condition of moving;

at the central server, receiving a request over a cellular telephone network for a particular application, wherein the received request is for one of the vehicle user interfaces and includes an application identifier;

at the central server, comparing the received request to the mapping and identifying a resource of said vehicle user interface responsive to the comparison;

transmitting a first control signal from the central server to control software on a corresponding one of the vehicles to permit the particular application to access only the identified resource of said vehicle user interface;

storing a plurality of graphical user interfaces remotely from the vehicles, wherein a first one of the plurality of graphical user interfaces is configured for a first vehicle configuration and a second one of the plurality of graphical user interfaces is configured for a second vehicle configuration that is different than the first vehicle configuration;

wherein the first vehicle configuration corresponds to a vehicle component to which the second vehicle configuration does not correspond;

probing with the central server the control software or said vehicle user interface; and

transmitting a second control signal from the central server to cause said vehicle user interface to display a particular one of the plurality of graphical user interfaces based on a result of said probing;

wherein said probing elicits a response specifying whether or not the vehicle of said vehicle user interface of the plurality of vehicle user interfaces includes a display device with a native resolution greater than a preset threshold, and wherein the instructions, if executed, result in selecting the particular graphical user interface responsive to said specification.

3. The memory of claim 2, wherein the instructions, if executed, result in:

identifying a remote desktop viewing server of a portable mobile device responsive to signaling from the control software; and

signaling the control software on the corresponding vehicle to permit or deny displaying of a current view of the portable mobile device on said vehicle user interface of the plurality of vehicle user interfaces, the current view from a remote desktop viewing client running on the corresponding vehicle, wherein said permission or denial is based at least in part on a value of the application identifier.

4. The memory of claim 3, wherein said permission or denial is further based at least in part on whether the corresponding vehicle is currently in the first condition or the second condition.

5. The memory of claim 4, wherein the instructions, if executed, result in:

receiving a wirelessly transmitted signal including a telephone number;

wherein said permission or denial is further based at least in part on a value of the telephone number.

13. A method, comprising:

providing a central server configured for communication with a plurality of vehicle user interfaces for centralized management of the plurality of vehicle user interfaces using the central server, each of the vehicle user interfaces of a different vehicle;

storing a mapping of vehicle conditions to resources of the plurality of vehicle user interfaces, wherein the vehicle conditions include at least a first condition of powered but not moving and a second condition of moving;

at the central server, receiving a request over a cellular telephone network for a particular application, wherein the received request is for one of the vehicle user interfaces of the plurality of vehicle user interfaces and includes an application identifier;

at the central server, comparing the received request to the mapping and identifying a resource of said vehicle user interface of the plurality of vehicle user interfaces responsive to the comparison;

storing a plurality of graphical user interfaces remotely from the vehicles, wherein a first one of the plurality of graphical user interfaces is configured for a first vehicle configuration and a second one of the plurality of graphical user interfaces is configured for a second vehicle configuration that is different than the first vehicle configuration;

wherein the first vehicle configuration corresponds to a vehicle component to which the second vehicle configuration does not correspond;

transmitting a first control signal from the central server to control software on a corresponding one of the vehicles to permit the particular application to access only the identified resource of said vehicle user interface;

using the central server to communicate with the control software or said vehicle user interface of the plurality of vehicle user interfaces; and

transmitting a second control signal from the central server to cause said vehicle user interface to display a particular one of the plurality of graphical user interfaces based on a result of said communicating;

wherein said communicating elicits a response specifying a make, model, and year of the corresponding vehicle, and wherein the instructions, if executed, result in selecting the particular graphical user interface responsive to the specified make, model, and year.

14. The method of claim 13, further comprising:

identifying a remote control capability of a portable mobile device responsive to signaling from the control software; and

signaling the control software on the corresponding vehicle to permit or deny displaying of a current view of the portable mobile device on said vehicle user interface of the plurality of vehicle user interfaces, wherein said permission or denial is based at least in part on a value of the application identifier.

15. The method of claim 13, further comprising:

checking for a graphical user interface update corresponding to the application identifier in response to receiving the request; and

pushing a new graphical user interface to the corresponding vehicle responsive to said checking, wherein the new graphical user interface is to be installed and displayed on said vehicle user interface of the plurality of vehicle user interfaces.

16. The method of claim 13, further comprising:

in response to said vehicle user interface of the plurality of vehicle user interfaces communicatively coupling to a mobile device, obtaining a phone number of the mobile device;

matching the obtained phone number to one of a plurality of profiles;

determining whether the matched profile is subject to parental control; and

transmitting a parental control message to the corresponding vehicle responsive to said determination.

17. The method of claim 16, wherein the parental control message identifies a blocked application or a conditionally blocked application.