Vehicle comprising multi-operating system

• US 9,324,234 B2
• Filed: 11/16/2012
• Issued: 04/26/2016
• Est. Priority Date: 10/01/2010
• Status: Active Grant

• Current Assignee: AutoConnect Holdings LLC
• Original Assignee: AutoConnect Holdings LLC
• Inventors: Ricci, Christopher P., Reeves, Brian, Reeves, Paul E., Teltz, Richard, Reeves, David, Sirpal, Sanjiv, Tyghe, Chris
• Primary Examiner(s): Suryawanshi, Suresh
• Application Number:
  US13/679,459
• Publication Number:
  US 20130167159A1
• Time in Patent Office: 1,257 Days
• Field of Search: 713/2
• US Class Current: 1/1
• CPC Class Codes: B60K 2360/11 Instrument graphical user interfaces or menu aspects
• CPC Class Codes: B60K 2360/1438 Touch screens
• CPC Class Codes: B60K 2360/146 Instrument input by gesture
• CPC Class Codes: B60K 2360/1464 3D-gesture
• CPC Class Codes: B60K 2360/1472 Multi-touch gesture
• CPC Class Codes: B60K 2360/1476 Handwriting
• CPC Class Codes: B60K 2360/164 Infotainment
• CPC Class Codes: B60K 2360/166 Navigation
• CPC Class Codes: B60K 2360/21 using cameras
• CPC Class Codes: B60K 2360/566 Mobile devices displaying vehicle information
• CPC Class Codes: B60K 2360/5894 SIM cards
• CPC Class Codes: B60K 2360/5899 Internet
• CPC Class Codes: B60K 2360/691 Housings
• CPC Class Codes: B60K 2370/11 Graphical user interfaces or menu aspects
• CPC Class Codes: B60K 2370/1438 Touch screens
• CPC Class Codes: B60K 2370/146 Input by gesture
• CPC Class Codes: B60K 2370/1464 3D-gesture
• CPC Class Codes: B60K 2370/1472 Multi-touch gesture
• CPC Class Codes: B60K 2370/1476 Handwriting
• CPC Class Codes: B60K 2370/164 Infotainment
• CPC Class Codes: B60K 2370/166 : Navigation
• CPC Class Codes: B60K 2370/21 : using cameras
• CPC Class Codes: B60K 2370/566 : Mobile devices displaying vehicle information
• CPC Class Codes: B60K 2370/5894 : SIM cards
• CPC Class Codes: B60K 2370/5899 : Internet
• CPC Class Codes: B60K 2370/691 : Housings
• CPC Class Codes: B60K 2370/81 : Fastening of instruments, e.g. to dashboard
• CPC Class Codes: B60K 35/00 : Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
• CPC Class Codes: B60K 35/10 : Input arrangements, i.e. from user to vehicle, associated with vehicle functions or specially adapted therefor
• CPC Class Codes: B60K 35/28 : characterised by the type of the output information, e.g. video entertainment or vehicle dynamics information; characterised by the purpose of the output information, e.g. for attracting the attention of the driver
• CPC Class Codes: B60K 35/50 : Instruments characterised by their means of attachment to or integration in the vehicle B60K35/231 takes precedence
• CPC Class Codes: B60K 35/60 : Instruments characterised by their location or relative disposition in or on vehicles arrangements of lighting devices on dashboards B60Q3/10
• CPC Class Codes: B60K 35/80 : Arrangements for controlling instruments
• CPC Class Codes: B60K 35/85 : Arrangements for transferring vehicle- or driver-related data
• CPC Class Codes: B60K 37/00 : Dashboards as road-vehicle superstructure sub-units B62D25/14
• CPC Class Codes: B60R 16/037 : for occupant comfort , e.g. for automatic adjustment of appliances according to personal settings, e.g. seats, mirrors, steering wheel
• CPC Class Codes: B60R 21/01512 : Passenger detection systems
• CPC Class Codes: B60R 7/04 : in driver or passenger space , e.g. using racks B60R7/005, B60R7/08 take precedence
• CPC Class Codes: B60W 2040/0872 : Driver physiology
• CPC Class Codes: B60W 2040/0881 : Seat occupation; Driver or passenger presence
• CPC Class Codes: B60W 2050/0095 : Automatic control mode change
• CPC Class Codes: B60W 2540/043 : Identity of occupants
• CPC Class Codes: B60W 2540/22 : Psychological state; Stress level or workload
• CPC Class Codes: B60W 2540/221 : Physiology, e.g. weight, heartbeat, health or special needs
• CPC Class Codes: B60W 2540/26 : Incapacity
• CPC Class Codes: B60W 2555/60 : Traffic rules, e.g. speed limits or right of way
• CPC Class Codes: B60W 30/182 : Selecting between different operative modes, e.g. comfort and performance modes
• CPC Class Codes: B60W 40/04 : Traffic conditions
• CPC Class Codes: B60W 40/08 : related to drivers or passengers
• CPC Class Codes: B60W 40/09 : Driving style or behaviour
• CPC Class Codes: B60W 50/0098 : Details of control systems ensuring comfort, safety or stability not otherwise provided for
• CPC Class Codes: B60W 50/08 : Interaction between the driver and the control system
• CPC Class Codes: G01C 21/20 : Instruments for performing navigational calculations G01C21/24, G01C21/26 take precedence
• CPC Class Codes: G01S 19/13 : Receivers
• CPC Class Codes: G02B 27/0101 : characterised by optical features G02B27/0172 takes precedence
• CPC Class Codes: G06F 11/2023 : Failover techniques
• CPC Class Codes: G06F 11/3013 : where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems testing or monitoring of control systems or parts thereof G05B23/02
• CPC Class Codes: G06F 11/3065 : Monitoring arrangements determined by the means or processing involved in reporting the monitored data error or fault reporting or logging G06F11/0766
• CPC Class Codes: G06F 11/328 : Computer systems status display G06F11/327 takes precedence
• CPC Class Codes: G06F 13/14 : Handling requests for interconnection or transfer
• CPC Class Codes: G06F 13/364 : using independent requests or grants, e.g. using separated request and grant lines
• CPC Class Codes: G06F 16/24 : Querying
• CPC Class Codes: G06F 16/29 : Geographical information databases
• CPC Class Codes: G06F 17/00 : Digital computing or data processing equipment or methods, specially adapted for specific functions information retrieval, database structures or file system structures therefor G06F16/00
• CPC Class Codes: G06F 21/1062 : Editing
• CPC Class Codes: G06F 21/121 : Restricting unauthorised execution of programs
• CPC Class Codes: G06F 21/32 : using biometric data, e.g. fingerprints, iris scans or voiceprints
• CPC Class Codes: G06F 21/335 : for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/42 : using separate channels for security data
• CPC Class Codes: G06F 21/629 : to features or functions of an application
• CPC Class Codes: G06F 2203/04808 : Several contacts: gestures triggering a specific function, e.g. scrolling, zooming, right-click, when the user establishes several contacts with the surface simultaneously; e.g. using several fingers or a combination of fingers and pen
• CPC Class Codes: G06F 3/017 : Gesture based interaction, e.g. based on a set of recognized hand gestures interaction based on gestures traced on a digitiser G06F3/04883
• CPC Class Codes: G06F 3/0481 : based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/04817 : using icons graphical or visual programming using iconic symbols G06F8/34
• CPC Class Codes: G06F 3/0482 : Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0484 : for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 3/04842 : Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/04847 : Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 3/0486 : Drag-and-drop
• CPC Class Codes: G06F 3/0488 : using a touch-screen or digitiser, e.g. input of commands through traced gestures
• CPC Class Codes: G06F 3/04883 : for inputting data by handwriting, e.g. gesture or text
• CPC Class Codes: G06F 8/61 : Installation
• CPC Class Codes: G06F 9/44505 : Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/54 : Interprogram communication
• CPC Class Codes: G06N 5/02 : Knowledge representation; Symbolic representation
• CPC Class Codes: G06N 5/048 : Fuzzy inferencing
• CPC Class Codes: G06Q 30/0265 : Vehicular advertisement
• CPC Class Codes: G06Q 40/08 : Insurance
• CPC Class Codes: G06Q 50/26 : Government or public services business processes related to the transportation industry G06Q50/40
• CPC Class Codes: G06T 19/006 : Mixed reality object pose determination, tracking or camera calibration for mixed reality G06T7/00
• CPC Class Codes: G06V 20/59 : inside of a vehicle, e.g. relating to seat occupancy, driver state or inner lighting conditions
• CPC Class Codes: G06V 40/10 : Human or animal bodies, e.g. vehicle occupants or pedestrians; Body parts, e.g. hands
• CPC Class Codes: G06V 40/15 : Biometric patterns based on physiological signals, e.g. heartbeat, blood flow
• CPC Class Codes: G06V 40/28 : Recognition of hand or arm movements, e.g. recognition of deaf sign language static hand signs G06V40/113
• CPC Class Codes: G07C 5/006 : Indicating maintenance
• CPC Class Codes: G07C 5/008 : communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/02 : Registering or indicating driving, working, idle, or waiting time only apparatus forming part of taximeters G07B13/00
• CPC Class Codes: G07C 5/08 : Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
• CPC Class Codes: G07C 5/0808 : Diagnosing performance data testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005
• CPC Class Codes: G07C 5/0825 : using optical means
• CPC Class Codes: G07C 5/0833 : using audio means
• CPC Class Codes: G07C 5/085 : using electronic data carriers
• CPC Class Codes: G07C 5/0866 : the electronic data carrier being a digital video recorder in combination with video camera
• CPC Class Codes: G08C 19/00 : Electric signal transmission systems G08C17/00 takes precedence
• CPC Class Codes: G08G 1/0112 : from the vehicle, e.g. floating car data [FCD]
• CPC Class Codes: G08G 1/0116 : from roadside infrastructure, e.g. beacons
• CPC Class Codes: G08G 1/012 : from other sources than vehicle or roadside beacons, e.g. mobile networks
• CPC Class Codes: G08G 1/0129 : for creating historical data or processing based on historical data
• CPC Class Codes: G08G 1/0133 : for classifying traffic situation
• CPC Class Codes: G08G 1/0137 : for specific applications
• CPC Class Codes: G08G 1/0141 : for traffic information dissemination
• CPC Class Codes: G08G 1/017 : identifying vehicles G08G1/015, G08G1/054 take precedence
• CPC Class Codes: G08G 1/09 : Arrangements for giving variable traffic instructions railroad crossing signals B61L; reflectors E01F, G08B; indicating arrangements for variable information by selection or combination of individual elements G09F9/00
• CPC Class Codes: G08G 1/096716 : where the received information does not generate an automatic action on the vehicle control
• CPC Class Codes: G08G 1/096725 : where the received information generates an automatic action on the vehicle control
• CPC Class Codes: G08G 1/096775 : where the origin of the information is a central station
• CPC Class Codes: G08G 1/096783 : where the origin of the information is a roadside individual element
• CPC Class Codes: G08G 1/096791 : where the origin of the information is another vehicle
• CPC Class Codes: G08G 1/096827 : where the route is computed onboard
• CPC Class Codes: G08G 1/096844 : where the complete route is dynamically recomputed based on new data
• CPC Class Codes: G08G 1/143 : inside the vehicles
• CPC Class Codes: G08G 1/16 : Anti-collision systems road vehicle drive control systems for predicting or avoiding probable or impending collision otherwise than by control of a particular sub-unit B60W30/08
• CPC Class Codes: H04L 41/14 : Network analysis or design
• CPC Class Codes: H04L 51/56 : Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/125 : involving control of end-device applications over a network
• CPC Class Codes: H04N 21/41422 : located in transportation means, e.g. personal vehicle arrangements specially adapted for transportation systems in broadcast systems H04H20/62
• CPC Class Codes: H04N 21/4331 : Caching operations, e.g. of an advertisement for later insertion during playback
• CPC Class Codes: H04N 21/482 : End-user interface for program selection broadcast systems using EPGs H04H60/72
• 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 4/50 : Service provisioning or reconfiguring
• 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 4/90 : Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 8/22 : Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 84/005 : Moving wireless networks
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]

Abstract

A mobile computing device with a mobile operating system and personal computer or vehicle processing module operating system running concurrently and independently on a shared kernel without virtualization. The mobile operating system provides a user experience for the mobile computing device that suits the mobile environment. The personal computer operating system provides a full personal computer user experience when the mobile computing device is docked to a secondary terminal environment. The vehicle processing module operating system provides a full vehicle processing module user experience when the mobile computing device is docked to a secondary terminal environment. The mobile computing device may be a smartphone running the Android mobile OS and a full desktop Linux distribution on a modified Android kernel.

Claims

1. A vehicle, comprising:

a power source to propel the vehicle;

a display panel to provide graphical information to a vehicle occupant; and

an on board processing module, comprising;

a first operating system running in a first execution environment on a shared kernel, the first operating system having a first application framework supporting a first vehicle-related application; and

a second operating system running concurrently with the first operating system in a second execution environment on the shared kernel, the second operating system having a second application framework supporting a second vehicle-related application, wherein the second vehicle-related application is incompatible with the first application framework, wherein the first operating system is based on the shared kernel and the second operating system is not based on the shared kernel, wherein the first and second operating systems run independently on the shared kernel, and wherein at least one of the first and second vehicle-related applications is one of the following;

a vehicle control application, an application associated with at least one vehicle function, an application related to a handicap and accessibility graphical user interface for the display panel, an email client, a web browser, a communications application, a game, an entertainment application, a vehicle satellite positioning system receiver application, an automotive navigation application, a medical information application, an emergency service application, a noise suppression application, a news-related application, a weather information-related application, a biometric application, a travel application, or a utility application.

2. The system of claim 1, wherein the first operating system includes a first set of user libraries in the first execution environment, wherein each of the first and second operating systems have access to memory and system resources of the processing module, and wherein the second vehicle-related application is incompatible with the first set of user libraries.

3. The system of claim 1, wherein the shared kernel is running on a first processor of the processing module, and wherein the first and second operating systems run on the shared kernel without virtualization.

4. The system of claim 1, wherein the processing module is installed in a vehicle, wherein the first execution environment is one of a personal computing device operating system and mobile device operating system, wherein the second execution environment is vehicle processing system operating system, and further including a secondary terminal environment, wherein the second operating system is associated with the secondary terminal environment.

5. The system of claim 1, further including a secondary terminal environment, wherein the processing module and the secondary terminal environment are connected with a single dock connector that includes a display interface and serial communications interface.

6. The system of claim 1, the processing module further including a physical memory device, wherein the first operating system is associated with a first frame buffer in the physical memory device and the second operating system is associated with a second frame buffer in the physical memory device, each of the first and second frame buffers being associated with respective first and second frame buffer devices in the shared kernel, wherein the first operating system renders an associated first graphical user interface by writing graphics data to the first frame buffer device, an external display driver of the shared kernel then writes the graphics data to the first operating system frame buffer for output by the processing module, wherein the second operating system renders an associated second graphical user interface by writing the graphics data to the second frame buffer device, an external display driver of the shared kernel then writes the graphics data to the second operating system frame buffer for output by the processing module.

7. The system of claim 6, wherein the first frame buffer is associated with and output to the display panel.

8. The system of claim 7, further including a secondary terminal environment, wherein the secondary terminal environment includes a second display device, and wherein the second frame buffer is associated with and output to the second display device.

9. The system of claim 8, wherein the second vehicle-related application is displayed on the second display device through the second frame buffer and wherein the processing module selects one of the first and second operating systems as a primary operating system based on whether or not the processing module is docked to a computing device.

10. The system of claim 1, the processing module further including a physical storage device, wherein the second execution environment is logically isolated from the first execution environment on the physical storage device.

11. The system of claim 1, further including an input device connected to the processing module, wherein input commands from the input device are available to the first operating system in the first execution environment and to the second operating system in the second execution environment.

12. The system of claim 11, wherein the first operating system is one of a mobile operating system and a desktop operating system, wherein the second operating system is the other of a mobile operating system and desktop operating system, wherein graphics data from an application executing in the first operating system is accessed directly by an application executing in the second operating system, whereby a surface of the application in the first operating system is maintained in a shared memory space and passed to the application in the second operating system by passing file descriptors to the shared memory, and wherein the second operating system accesses input commands from the input device through the shared kernel.

13. The system of claim 1, wherein the processing module is configured using a boot process that includes the steps of:

starting, in response to a power on event, a boot loader;

establishing, by the boot loader, the first execution environment;

starting, by the boot loader, the shared kernel;

initializing, by the shared kernel, the first operating system;

starting, by the shared kernel, the first application framework;

starting, in the first operating system, a first monitor service;

establishing, by the first monitor service, the second execution environment within the first execution environment; and

starting, by the first monitor service, the second application framework.

14. A method of providing multiple operating systems on a single physical processor of a processing module of a vehicle, the method comprising:

running a first application on a first operating system, the first operating system running on a shared kernel of the vehicle processing module and having a first application framework; and

running a second application on a second operating system, the second operating system running concurrently with the first operating system on the shared kernel and having a second application framework, wherein the second application is incompatible with the first application framework, wherein the first operating system is based on the shared kernel and the second operating system is not based on the shared kernel, wherein the first and second operating systems run independently on the shared kernel, and wherein at least one of the first and second applications is one of the following;

a vehicle control application, an application associated with at least one vehicle function, an application related to a handicap and accessibility graphical user interface for a vehicle display panel, a vehicle satellite positioning system receiver application, an automotive navigation application, and a vehicle emergency service application.

15. The method of claim 14, wherein each of the first and second operating systems have access to memory and system resources of the processing module, wherein the first and second operating systems run on the shared kernel without virtualization, wherein the first operating system is one of a mobile operating system and a desktop operating system, wherein the second operating system is the other of a mobile operating system and desktop operating system, and further comprising:

allocating, by the shared kernel, a first frame buffer memory associated with the first operating system; and

allocating, by the shared kernel, a second frame buffer memory associated with the second operating system.

16. The method of claim 15, further comprising:

rendering, by the first operating system, the first application in the first frame buffer memory through the shared kernel; and

rendering, by the second operating system, the second application in the second frame buffer memory through the shared kernel, each of the first and second frame buffer memories being associated with respective first and second frame buffer devices in the shared kernel, wherein the first operating system renders an associated first graphical user interface by writing graphics data to the first frame buffer device, an external display driver of the shared kernel then writes the graphics data to the first operating system frame buffer memory for output by the processing module, wherein the second operating system renders an associated second graphical user interface by writing the graphics data to the second frame buffer device, an external display driver of the shared kernel then writes the graphics data to the second operating system frame buffer memory for output by the processing module.

25. The method of claim 14, wherein the selected processing resource is installed in a vehicle, wherein the second execution environment is one of a MAC™

operating system and Microsoft Windows™

operating system, and further including a secondary terminal environment, wherein the second operating system is associated with the secondary terminal environment.

26. The method of claim 14, wherein the selected processing resource selects one of the first and second operating systems as a primary operating system based on whether or not the selected processing resource is docked to a computing device.

17. A processing module of a vehicle including a tangible and non-transitory computer-readable medium storing instructions for a physical processor, the instructions, when executed, causing the processor to perform steps comprising:

running a first operating system in a first execution environment on a shared kernel, the first operating system having a first application framework supporting a first application; and

running a second operating system concurrently with the first operating system in a second execution environment on the shared kernel, the second operating system having a second application framework supporting a second application, wherein the second application is incompatible with the first application framework, wherein the first operating system is based on the shared kernel and the second operating system is not based on the shared kernel, wherein the first and second operating systems run independently on the shared kernel, and wherein at least one of the first and second applications is one of the following;

a vehicle control application, an application associated with at least one vehicle function, an application related to a handicap and accessibility graphical user interface for a vehicle display panel, a vehicle satellite positioning system receiver application, an automotive navigation application, or an emergency service application.

18. The processing module of claim 17, wherein the second execution environment comprises a chrooted environment.

19. The processing module of claim 17, wherein each of the first and second operating systems have access to memory and system resources of the processing module, wherein the first and second operating systems run on the shared kernel without virtualization, and further comprising mobile telephony capabilities.

20. The processing module of claim 17, further comprising:

rendering, by the first operating system, the first application in the first frame buffer memory through the shared kernel; and

rendering, by the second operating system, the second application in the second frame buffer memory through the shared kernel, each of the first and second frame buffer memories being associated with respective first and second frame buffer devices in the shared kernel, wherein the first operating system renders an associated first graphical user interface by writing graphics data to the first frame buffer device, an external display driver of the shared kernel then writes the graphics data to the first operating system frame buffer memory for output by the processing module, wherein the second operating system renders an associated second graphical user interface by writing the graphics data to the second frame buffer device, an external display driver of the shared kernel then writes the graphics data to the second operating system frame buffer memory for output by the processing module.

21. The processing module of claim 17, further comprising:

rendering, by the first operating system, the first application in the first frame buffer memory through the shared kernel; and

rendering, by the second operating system, the second application in the second frame buffer memory through the shared kernel, each of the first and second frame buffer memories being associated with respective first and second frame buffer devices in the shared kernel, wherein the first operating system renders an associated first graphical user interface by writing graphics data to the first frame buffer device, an external display driver of the shared kernel then writes the graphics data to the first operating system frame buffer memory for output by the processing module, wherein the second operating system renders an associated second graphical user interface by writing the graphics data to the second frame buffer device, an external display driver of the shared kernel then writes the graphics data to the second operating system frame buffer memory for output by the processing module.

22. The processing module of claim 17, further comprising:

rendering, by the first operating system, the first application in the first frame buffer memory through the shared kernel; and

rendering, by the second operating system, the second application in the second frame buffer memory through the shared kernel, each of the first and second frame buffer memories being associated with respective first and second frame buffer devices in the shared kernel, wherein the first operating system renders an associated first graphical user interface by writing graphics data to the first frame buffer device, an external display driver of the shared kernel then writes the graphics data to the first operating system frame buffer memory for output by the processing module, wherein the second operating system renders an associated second graphical user interface by writing the graphics data to the second frame buffer device, an external display driver of the shared kernel then writes the graphics data to the second operating system frame buffer memory for output by the processing module.

23. The processing module of claim 17, wherein at least one of the first and second applications is one of the following:

the vehicle control application, and the application associated with at least one vehicle function.

24. A method, comprising:

selecting, by a processor, a processing resource from among a plurality of processing resources on board a vehicle to execute simultaneously first and second operating systems, the first operating system being a native operating system of the selected processing resource and the second operating system not being a native operating system of selected processing resource, wherein the first operating system is a vehicle operating system and the second operating system is selected from a MAC™

operating system, an Android™

operating system, an Apple™

operating system, a Microsoft Windows™

operating system, a Nokia Symbian™

operating system, a Palm™

operating system, or an HP™

web operating system; and

executing, by the processor executing the second operating system, an application on the selected processing resource and providing the results to the second processing resource for presentation to a user.

27. The method of claim 24, wherein the selection of the processing resource is based on one or more of where a user selected software application is located, by which output device a user desires to access the selected software application, the application and operating system requirements of the selected software application as compared to the capabilities of each of the processing resources, and power levels in each of the processing resources.

28. A method, comprising:

starting, in response to a power on event, a boot loader of an on board vehicle processing module;

establishing, by the boot loader and on the on board vehicle processing module, a first execution environment, wherein a first operating system runs in the first execution environment on a shared kernel, the first operating system having a first application framework supporting a first application;

starting, by the boot loader and on the on board vehicle processing module, the shared kernel;

initializing, by the shared kernel, the first operating system;

starting, by the shared kernel, the first application framework;

starting, in the first operating system, a first monitor service;

establishing, by the first monitor service, a second execution environment within the first execution environment, wherein a second operating system runs concurrently with the first operating system in the second execution environment on the shared kernel, the second operating system having a second application framework supporting a second application, wherein the second application is incompatible with the first application framework; and

starting, by the first monitor service, the second application framework.

29. The method of claim 28, wherein the first operating system is a vehicle operating system and the second operating system is selected from a MAC™

operating system, an Android™

operating system, an Apple™

operating system, a Microsoft Windows™

operating system, a Nokia Symbian™

operating system, a Palm™

operating system, and an HP™

web operating system.

30. The method of claim 28, wherein the first operating system is based on the shared kernel and the second operating system is not based on the shared kernel and wherein the first and second operating systems run independently on the shared kernel.

31. The method of claim 28, wherein the shared kernel is Linux-based and the second operating system is an Android™

operating system.

32. A vehicle, comprising:

a power source to propel the vehicle;

a display panel to provide graphical information to a vehicle occupant;

an on board processing module, comprising;

a first operating system running in a first execution environment on a shared kernel, the first operating system having a first application framework supporting a first application;

a second operating system running concurrently with the first operating system in a second execution environment on the shared kernel, the second operating system having a second application framework supporting a second application, wherein the second application is incompatible with the first application framework; and

a physical memory device, wherein the first operating system is associated with a first frame buffer in the physical memory device and the second operating system is associated with a second frame buffer in the physical memory device, each of the first and second frame buffers being associated with respective first and second frame buffer devices in the shared kernel, wherein the first operating system renders an associated first graphical user interface by writing graphics data to the first frame buffer device and an external display driver of the shared kernel then writes the graphics data to the first operating system frame buffer for output by the computing device, wherein the second operating system renders an associated second graphical user interface by writing the graphics data to the second frame buffer device and an external display driver of the shared kernel then writes the graphics data to the second operating system frame buffer for output by the computing device, and wherein at least one of the first and second applications is one of the following;

a vehicle control application, application associated with at least one vehicle function, an application related to a handicap and accessibility graphical user interface for the display panel, a vehicle satellite positioning system receiver application, an automotive navigation application, or a vehicle emergency service application.

33. The system of claim 32, wherein the first operating system is based on the shared kernel and the second operating system is not based on the shared kernel and wherein the first and second operating systems run independently on the shared kernel.

34. The system of claim 32, wherein the first operating system is a vehicle operating system and the second operating system is one of a a MAC™

operating sysem, an Android™

operating system, an Apple™

operating system, a Microsoft Windows™

operating system, a Nokia Symbian™

operating system, a Palm™

operating system, and an HP™

web operating system.

35. The system of claim 32, wherein the first operating system is based on the shared kernel and the second operating system is not based on the shared kernel and wherein the first and second operating systems run independently on the shared kernel.

36. The system of claim 32, wherein the shared kernel is Linux-based and the second operating system is an Android™

operating system.

37. A vehicle, comprising:

a power source to propel the vehicle;

a display panel to provide graphical information to a vehicle occupant;

an on board processing module, comprising;

a first operating system running in a first execution environment on a shared kernel, the first operating system having a first application framework supporting a first vehicle-related application; and

a second operating system running concurrently with the first operating system in a second execution environment on the shared kernel, the second operating system having a second application framework supporting a second vehicle-related application, wherein the second vehicle-related application is incompatible with the first application framework, wherein the first and second operating systems run independently on the shared kernel, and wherein at least one of the first and second vehicle-related applications is one of the following;

a vehicle control application, an application associated with at least one vehicle function, or an emergency vehicle service application.