Context aware security features for vehicle operating systems

Abstract

In general, various aspects of the technology are described for contextually aware security features for vehicle operating systems. A computing device may implement techniques, the computing device including: a memory configured to store an instance of a vehicle operating system; and one or more processors configured to execute an instance of a vehicle operating system. An example of a vehicle operating system is configured to: determine an operating context in which a vehicle is currently operating; and entering a protected operating mode in which the vehicle operating system dynamically adapts one or more operating characteristics of the vehicle operating system to facilitate safety of an operator of the vehicle based on the operating context.

Description

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 371,445, filed on August 15, 2022, entitled “CONTEXT AWARE SAFETY FEATURES FOR VEHICLE OPERATING SYSTEMS,” and U.S. Provisional Application Serial No. 63 / 371,451, filed on August 15, 2022, entitled “SINGLE-INSTANCE MULTI-USER SUPPORT FOR VEHICLE OPERATING SYSTEMS,” each of which is hereby incorporated by reference in its entirety as if fully set forth herein. Background Art

[0002] The vehicle head unit (which may be referred to as an infotainment system) may be configured to execute a vehicle operating system to facilitate control of, to name a few, entertainment (such as music, video, images, etc.), information, navigation, and voice calls, as well as vehicle systems (such as heating, ventilation and air conditioning (HVAC) systems, lighting systems, and seat control systems (including heating and / or cooling, seat adjustment, etc.)). The vehicle operating system may typically restrict access to certain features in order to avoid and / or reduce interference with the operator of the vehicle. These security restrictions may be hard-coded (or in other words, statically compiled) into the vehicle operating system to meet certain safety concerns and are generally difficult to override despite changes in operating scenarios. Summary of the invention

[0003] In general, various aspects of the technology set forth in this disclosure relate to context-aware safety features for vehicle operating systems. Rather than statically determining when a protected operating mode may be applied regardless of context, various aspects of the technology described in this disclosure may enable one or more instances of a vehicle operating system to determine an operating context in which a vehicle is currently operating, and based on the operating context, enter a protected operating mode in which the vehicle operating system dynamically adapts one or more operating features of the vehicle operating system to promote safety for an operator of the vehicle.

[0004] The operating context may include usage of an instance of the vehicle operating system by one or more occupants of the vehicle, the presence of one or more occupants in the vehicle, the weather conditions in which the vehicle is currently operating, and the operating state of the vehicle (e.g., whether the vehicle has been in an accident, the charge level of the battery for a hybrid electric vehicle and / or a pure electric vehicle, etc.). In response to these various aspects of the operating context, the vehicle operating system may reduce power consumption (e.g., in the case of a pure electric vehicle) via one or more displays (e.g., reducing the brightness of such displays or turning off such displays), currently executing applications (e.g., by entering night mode or other emergency mode execution that reduces current processing and / or display requirements), etc.

[0005] In this regard, various aspects of the technology can improve the operation of the vehicle head unit itself by dynamically entering a protected operating mode to potentially improve the level of safety associated with operating the vehicle. For example, in the context of battery life, the vehicle operating system can disable or reduce the operation of the display to maintain battery life so that the vehicle can reach a predetermined destination without depleting the battery powering the vehicle, which can improve safety, particularly when weather conditions may otherwise pose a significant risk to the health of the operator and / or passengers (e.g., when it is very cold or hot outside the controlled environment of the vehicle). Thus, various aspects of the technology described in the present disclosure can improve the operation of the vehicle itself in terms of providing safety for the operator and / or passengers (which can include "operators" in the context of autonomous vehicles).

[0006] Furthermore, by dynamically entering a protected operating mode only when certain conditions are met (or in other words, when the operating context makes it necessary to enter the protected operating mode), various aspects of the technology can reduce erroneous entry into such a protected operating mode in operating contexts where it is not necessary to enter such a protected operating mode. By avoiding unnecessary entry into an unnecessary protected operating mode, the vehicle operating system can improve the user experience while potentially still addressing operator and / or passenger safety issues in a variety of different ways.

[0007] In one example, the present disclosure describes a method comprising: executing an instance of a vehicle operating system via a vehicle head unit of a vehicle; determining, via the instance of the vehicle operating system, an operating context in which the vehicle is currently operating; and entering, via the instance of the vehicle operating system, based on the operating context, a protected operating mode in which the vehicle operating system dynamically adapts one or more operating features of the vehicle operating system to promote the safety of an operator of the vehicle.

[0008] In another example, the present disclosure describes a computing device comprising: a memory configured to store an instance of a vehicle operating system; and one or more processors for executing the instance of the vehicle operating system, wherein the instance of the vehicle operating system is configured to: determine an operating context in which a vehicle is currently operating; and based on the operating context, enter a protected operating mode of the vehicle operating system in which the vehicle operating system dynamically adapts one or more operating features of the vehicle operating system to promote the safety of an operator of the vehicle.

[0009] In another example, the present disclosure describes a non-transitory computer-readable storage medium having instructions stored thereon that, when executed, cause one or more processors to: execute an instance of a vehicle operating system; determine, through the instance of the vehicle operating system, an operating context in which the vehicle is currently operating; and enter, through the instance of the vehicle operating system, based on the operating context, a protected operating mode in which the vehicle operating system dynamically adapts one or more operating features of the vehicle operating system to facilitate the safety of an operator of the vehicle.

[0010] In another example, the present disclosure describes a device comprising: components for executing an instance of a vehicle operating system; components for determining an operating context in which a vehicle is currently operating; and components for entering a protected operating mode of the vehicle operating system based on the operating context in which one or more operating features of the vehicle operating system are dynamically adapted to promote safety of an operator of the vehicle.

[0011] The details of one or more examples are set forth in the accompanying drawings and the description below.Other features, objects, and advantages will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a block diagram illustrating an example computing system configured to provide a single-instance multi-user vehicle operating system in accordance with various aspects of the techniques described in this disclosure.

[0013] Figure 2 is a diagram illustrating an example of a vehicle including a computing system configured to execute a vehicle operating system that operates in accordance with various aspects of the single-instance multi-user techniques described in this disclosure.

[0014] Figure 3 is a diagram illustrating different interaction models with multiple displays including interactions that occur via a single-instance multi-user model and a multi-instance multi-user model according to the vehicle operating system techniques described in this disclosure.

[0015] Figure 4is a diagram illustrating an example vehicle including a vehicle head unit configured to control audio content in accordance with various aspects of the single-instance multi-user vehicle operating system techniques described in this disclosure.

[0016] Figure 5 and Figure 6 is a diagram illustrating audio control in a single-instance multi-user vehicle operating system in accordance with various aspects of the techniques described in this disclosure.

[0017] Figure 7 It is shown Figure 1 A flowchart of example operations of a computing system executing a vehicle operating system configured to perform various aspects of the safety techniques described in this disclosure is shown. DETAILED DESCRIPTION

[0018] Figure 1 is a block diagram illustrating an example computing system configured to provide a single-instance multi-user vehicle operating system in accordance with various aspects of the techniques described in this disclosure. Figure 1 As shown in the example of FIG. 1 , computing system 100 includes computing device 102. Although described with respect to a vehicle, computing system 100 may be used in different contexts, including stand-alone computing systems (including laptops, desktop computers, workstations, etc.), gaming systems, cellular phones (including so-called “smart phones”), media systems (including streaming media systems), audio / video (A / V) receivers, televisions (including so-called “smart TVs”), smart speakers, smart watches, thermostats (including so-called “smart thermostats”), smart glasses, or any other computing system.

[0019] Regardless, computing device 102 is an example of a vehicle computing device, such as a vehicle head unit. Figure 1 Only one particular example of computing device 102 is shown, and many other examples of computing device 102 may be used in other instances and may include a subset of the components included in the example computing device 102, or may include Figure 1 Additional components not shown.

[0020] like Figure 1As shown in the example of , the computing device 102 includes a presence-sensitive display 112, one or more processors 140, one or more communication units 142, one or more input components 144, one or more output components 146, and one or more storage devices 148 and a communication channel 149. The communication channel 149 can interconnect each of the components 112, 140, 142, 146, and / or 148 for inter-component communication (physically, communicatively, and / or operationally), and thereby allow the components 112, 140, 142, 146, and 148 to communicate with each other. In some examples, the communication channel 149 may include a system bus, a network connection, one or more inter-process communication data structures, or any other component for transmitting data (also referred to as information). Although shown as including components 112, 140, 142, 146, and 148, the vehicle head unit 102 may include other components in addition to the components shown or fewer components than the components shown, where such components may be included in other control units such as a telematics control unit (TCU).

[0021] One or more communication units 142 of computing device 102 can communicate with external devices by sending and / or receiving data. For example, computing device 102 can use one or more of communication units 142 to send and / or receive radio signals on a radio network (such as a cellular radio network). In some examples, communication unit 142 can send and / or receive satellite signals on a satellite network (such as a global positioning system (GPS) network). Examples of communication unit 142 include a network interface card (e.g., an Ethernet card), an optical transceiver, a radio frequency transceiver, a GPS receiver, or any other type of device that can send and / or receive information. Other examples of communication unit 142 may include shortwave radios (e.g., NFC, BLUETOOTH (including BLE)), GPS, 3G, 4G, 5G, and WIFI radios, and universal serial bus (USB) controllers, etc., found in mobile devices.

[0022] One or more input components 144 of computing device 102 can receive input. Examples of input are tactile input, audio input, kinetic input, and optical input, to name a few. In one example, input component 144 of computing device 102 includes a mouse, keyboard, touchpad, voice response system, camera, button, scroll wheel, dial, control pad, microphone (or in other words, audio capture device), or any other type of device for detecting input from a human or machine. Input component 144 may include a camera. In some examples, input component 144 may be a presence-sensitive input component separate from presence-sensitive display 112, which may include a presence-sensitive screen, a touch-sensitive screen, etc.

[0023] One or more output components 146 of computing device 102 may generate output. Examples of output are tactile output, audio output, and video output. In some examples, output components 146 of computing device 102 include a presence-sensitive screen (possibly separate from presence-sensitive display 112), a sound card, a video graphics adapter card, a speaker, a cathode ray tube (CRT) monitor, a liquid crystal display (LCD), an organic light emitting diode (OLED), or any other type of device for generating tactile output, audio output, and / or visual output to a human or machine.

[0024] In some examples, presence-sensitive display 112 of computing device 102 may include functionality of input component 144 and / or output component 146. Figure 1 In an example of , presence-sensitive display 112 may include presence-sensitive input (PSI) component 104 ("PSI component 104"), such as a presence-sensitive screen or a touch-sensitive screen. In some examples, presence-sensitive input component 104 may detect objects at and / or near the presence-sensitive input component. As an example range, presence-sensitive input component 104 may detect objects, such as a finger or stylus, within two inches or less of presence-sensitive input component 104. Presence-sensitive input component 104 may determine a location (e.g., (x, y) coordinates) of the presence-sensitive input component at which the object was detected. In another example range, presence-sensitive input component 104 may detect an object two inches or less from presence-sensitive input component 104, and other ranges are possible. Presence-sensitive input component 104 may use capacitive, inductive, and / or optical recognition techniques to determine the location of presence-sensitive input component 104 selected by a user's finger.

[0025] In some examples, presence-sensitive display 112 may also provide output to the user using tactile, audio, or video stimulation, as described with respect to output component 146. For example, presence-sensitive display 112 may include display component 103 that displays a graphical user interface. Display component 103 may be any type of output component that provides visual output, such as described with respect to output component 146. Although shown as an integrated component of computing device 102, presence-sensitive display 112 may be an external component that shares a data or information path with other components of computing device 102 to send and / or receive input and output in some examples. For example, presence-sensitive display 112 may be a built-in component of computing device 102 (e.g., an in-vehicle screen installed in a dashboard of a vehicle) that is located within and physically connected to an external package of computing device 102. In another example, presence-sensitive display 112 may be an external component of computing device 102 (e.g., a monitor, projector, etc. that shares a wired and / or wireless data path with an electronic control unit of a vehicle) that is located outside and physically separated from the package of computing device 102. In some examples, presence-sensitive display 112 , when located outside and physically separate from the packaging of computing device 102 , can be implemented by two separate components: presence-sensitive input component 104 for receiving input and display component 103 for providing output.

[0026] One or more storage devices 148 within computing device 102 may store information for processing during operation of computing device 102 (e.g., computing device 102 may store data accessed by operating system (OS) 160A and OS 160B during execution at computing device 102). Figure 1 As shown in the example of , one or more storage devices 148 can store a first instance of operating system 160A (OS 160A) and a second instance of operating system 160B (OS 160B). In some examples, storage devices 148 include temporary memory, meaning that the primary purpose of one or more storage devices 148 is not long-term storage. Storage devices 148 of computing device 102 can be configured as volatile memory for short-term storage of information, and therefore the stored contents are not retained when the computer is shut down. Examples of volatile memory include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), and other forms of volatile memory known in the art.

[0027] In some examples, storage device 148 also includes one or more computer-readable storage media. Storage device 148 includes one or more non-transitory computer-readable storage media in some examples. Storage device 148 can be configured to store a larger amount of information than is typically stored by volatile memory. Storage device 148 can be further configured as a non-volatile memory space for long-term storage of information and retain information after a power-on / power-off cycle. Examples of non-volatile memory include a magnetic hard disk, an optical disk, a flash memory, or a form of electrically programmable memory (EPROM) or electrically erasable and programmable (EEPROM) memory. Storage device 148 can store program instructions and / or information (e.g., data) associated with OS 160A and / or 160B. Storage device 148 may include a memory configured to store data or other information (not shown for ease of illustration) associated with OS 160A and OS 160B.

[0028] One or more processors 140 may implement functions associated with the computing device 102 and / or execute instructions associated with the computing device. Examples of processors 140 include application processors, display controllers, auxiliary processors, one or more sensor hubs, and any other hardware configured to function as a processor, processing unit, or processing device. OS 160A and / or 160B may be operated (or in other words, executed) by processor 140 to perform various actions, operations, or functions of computing device 102. That is, OS 160A and / or OS 160B may form executable bytecodes that, when executed, cause processor 140 to perform specific operations according to various aspects of the technology described herein (and thereby make computing device 102 a special-purpose computer for performing specific operations). For example, processor 140 of computing device 102 may retrieve and execute instructions stored by storage device 148 that cause processor 140 to perform operations attributed to OS 160A and / or 160B described herein. These instructions, when executed by processor 140 , may cause computing device 102 to store information in storage device 148 .

[0029] As described above, computing system 100 may be integrated or otherwise included in a vehicle. The vehicle may include one or more of the following: a bicycle, a tricycle, a unicycle, a motorcycle, an automobile, agricultural equipment (such as a tractor, a combine harvester, etc.), construction equipment (dump trucks, cranes, etc.), military vehicles or equipment (tanks, weaponry, etc.), a truck, a semi-trailer tractor (or in other words, a semitrailer), an aviation device (such as an airplane), a nautical device (such as a ship, a transport ship, a submarine, etc.), or any other type of vehicle.

[0030] Computing device 102 (which, as described above, may be referred to as vehicle head unit 102 as well as infotainment system 102) may be configured to execute a vehicle operating system, such as one or more of OS 160A and 160B (which may therefore also be referred to as vehicle OS 160A—VOS 160A—and VOS 160B), to facilitate control of, to name a few, entertainment (such as music, video, images, etc.), information, navigation, and voice calls, and vehicle systems (such as heating, ventilation, and air conditioning (HVAC) systems, lighting systems, and seat control systems (including heating and / or cooling, seat adjustment, etc.)). In some instances, the vehicle operating system may allow a single user profile to access a given instance of the vehicle operating system at once, where the single user profile is typically the operator of the vehicle.

[0031] The vehicle operating system may be referred to as a single-instance single-user vehicle operating system. That is, a single instance of the vehicle operating system may only allow a single user profile to access the single instance of the vehicle operating system and require a user profile switch in which the single user profile is replaced with another single user profile. In this regard, only a single user profile may access the single instance of the vehicle operating system at any given time.

[0032] To enable multiple concurrent user profiles, processor 140 may execute another instance of the vehicle operating system, which may require an additional processor and / or a processor with higher processing capacity (generally more expensive). However, it may be difficult to achieve efficient communication between the two instances of the vehicle operating system, making it impossible for users associated with multiple user profiles to share content with each other, thereby potentially limiting the user experience.

[0033] Thus, while an instance of a vehicle operating system may support multiple user profiles, the instance of the vehicle operating system may only allow a single user profile from the multiple user profiles to access (or in other words "log into") the instance of the vehicle operating system. The instance of the vehicle operating system may limit access to a single user profile to ensure that the operator of the vehicle is not distracted by the actions of other user profiles when operating the vehicle.

[0034] According to various aspects of the techniques described in this disclosure, computing system 100 may implement a single instance of a vehicle operating system, such as VOS 160A and / or 160B (“VOS 160”), that provides concurrent multi-user support. The single instance of VOS 160 described in this disclosure does not restrict access to the single instance of VOS 160 by a single user profile, but rather may allow multiple user profiles to access the single instance of VOS 160. As vehicles begin to integrate more and more displays, such as presence-sensitive enabled displays 150A-150N (“presence-sensitive enabled displays 150”, which may also be referred to as “displays 150”) in the passenger cabin of the vehicle, more users may safely interface with VOS 160 without interfering with the operator of the vehicle (given that in some examples, the operator has a limited view of these displays 150, or is unable to directly see these displays 150, which may be located behind the operator for use by rear seat passengers). Thus, multiple users associated with multiple user profiles can access VOS 160 and interact with computing device 102 to control various functions provided via computing device 102, such as entertainment, information, navigation, and voice calls, as well as various vehicle systems (which may depend to some extent on the multiple user locations within the vehicle).

[0035] Multiple users may also interface with the VOS 160 to jointly coordinate activities among the multiple users, such as sharing content among the multiple users, reviewing content viewed by other users of the multiple users, controlling audio playback among the multiple users (such as changing audio playback volume, coordinating playlists, etc.), passing messages among the multiple users, collaborating on navigation directions by the multiple users, etc. In some instances, the multiple users may use gestures (such as swipe gestures, pinch gestures, and tap gestures) to indicate sharing of such content, which may allow intuitive control of sharing among the multiple users.

[0036] In operation, Figure 1As shown in the example of , computing device 102 may be docked with display 150, which may be similar (if not substantially similar) to presence-sensitive display 112. However, rather than being integrated into computing device 102 like presence-sensitive display 112, display 150 may be communicatively coupled to computing device 102 (via wire or wirelessly) and integrated throughout the passenger cabin of a vehicle or separate from the vehicle. That is, in some instances, display 150 may also represent a tablet computer, a smartphone, a laptop computer, a portable gaming device, a portable video device, or any other device capable of docking with computing device 102 to present a user interface associated with VOS 160 (and / or applications executed in an application space presented by VOS 160, which application space may be separate from a privileged kernel space in which VOS 160 executes to facilitate interaction between applications and underlying hardware (such as components 112 and 140-148)).

[0037] Regardless, processor 140 may execute an instance of a vehicle operating system, such as VOS 160A or VOS 160B, wherein VOS 160A and / or 160B facilitates concurrent access to multiple user profiles that are configured to be used in a plurality of different environments. Figure 1 160A and UP 163A to 163N ("UP 163") of VOS 160B. UP 161 / 163 may each define a set of access rights (or in other words, privileges), preferences (e.g., for user interface, VOS 160 settings, etc.), and other user-specific configuration data or information. UP 161 / 163 may each be associated with a different user, but UP 161 and UP 163 may include a user profile of the same user. For example, UP 161A and UP 163A may be associated with the same user.

[0038] As an example, the processor 140 may execute the VOS 160A and authorize multiple user profiles of the UP 161 to interface with the VOS 160A. In order to authorize the multiple user profiles of the UP 161, each of the users may register with the VOS 160A, enter a username (associated with a given UP in the UP 161) and a password to log into the VOS 160A. Alternatively, any other means for logging into the VOS 160A may be enabled, such as scanning a quick response (QR) code using a smartphone's camera, entering a personal identification number (PIN), performing a biometric identification process (e.g., fingerprint scanning, retinal scanning, etc.), facial recognition, or any other means for registering a given user profile of the UP 161 with the VOS 160A. The OS 160A may compare the entered information with the authentication information stored to the UP 161 to authorize (or in other words, authenticate) each of the multiple user profiles of the UP 161 to interface with the VOS 160A.

[0039] Although discussed with respect to authentication, VOS 160A may also allow authorization to be provided in a guest user profile (as one of UP 161) without any authentication. In this regard, the guest user profile may provide a limited experience (compared to the authenticated UP 161) in terms of maintaining preferences, applications, etc. across different sessions, but still be able to implement the functionality described below with respect to sharing content between multiple UP 161, etc.

[0040] In any case, VOS 160A can present multiple user interfaces across multiple displays (such as display 112 and one or more of display 150) communicatively coupled to computing device 102. For authenticated UPs in UP 161, VOS 160A can present a user interface specific to each of the authenticated UPs, which maintains preferences in application organization, user interface themes, various VOS 160A settings (e.g., display configurations in terms of notifications, accessibility, brightness, resolution, orientation, etc., and any other type of OS settings). In any case, each of the multiple user interfaces is associated with one or more of UP 161.

[0041] Next, VOS 160A may interface with multiple users associated with multiple UPs in UP 161 via multiple user interfaces to enable multiple users to interface with VOS 160A to control functions associated with computing device 102. Such functions may include controlling navigation, changing content playback, changing user interface settings, controlling HVAC settings, sharing content between UPs 161, and other functions described in more detail below.

[0042] In some examples, processor 140 may represent a high processing capacity processor (which may be referred to as "processor 140A") and a low processing capacity processor (which may be referred to as "processor 140B"). In some instances, processor 140 may represent a processor with variable processing capacity, the processor having two or more different operating voltages, the processor implementing high processing capacity at the high voltage and low processing capacity at the low voltage. In this sense, a single processor may represent both processor 140A and processor 140B that switch between different processing modes (e.g., a high processing mode and a low processing mode) to facilitate power conservation. Processor 140A may provide additional processor cores compared to processor 140B (or in instances where a single processor switches between processing modes, additional cores are enabled in the high processing mode compared to the low processing mode).

[0043] Processor 140A may execute VOS 160A, while processor 140B may execute VOS 160B. Processor 140A may execute VOS 160A for tasks requiring higher processing, such as gaming, video conferencing, navigation, and other processor-intensive tasks / applications. Processor 140B may execute VOS 160B for tasks requiring lower processing, such as streaming audio, phone calls, viewing images, text messaging, or other tasks / applications that are less processor-intensive.

[0044] In some examples, processor 140A may execute VOS 160A concurrently with processor 140B executing VOS 160B. In instances of concurrent execution of VOS 160A and 160B, VOS 160A may present an interface that VOS 160B may use to communicate with VOS 160A to facilitate various functions of computing device 102. The interface may represent an application programming interface that VOS 160B may call to facilitate inter-VOS communication between VOS 160A and VOS 160B to collaboratively facilitate support for functions provided by computing device 102.

[0045] Utilizing processors of different processing capacities may facilitate reducing energy consumption. Further, installing a high processing capacity processor 140 with all the functionality supported by the computing device 102 may be cost-prohibitive, while a low processing capacity processor 140 may allow a manufacturer to upgrade over time to add additional processors with high processing capacity (and / or possibly low processing capacity). Providing a framework for inter-VOS communications may allow a manufacturer to upgrade over time without having to configure a separate inter-VOS communication interface for facilitating access to the functionality of the computing device 102 described in more detail below.

[0046] like Figure 1 As further shown in the example of , the computing device 102 can also be docked with supporting audio capture devices 152A to 152N ("supporting audio capture devices 152" or "audio capture devices 152"). The audio capture devices 152 can each represent a microphone or other transducer configured to capture audio data representing a sound field. The supporting audio capture devices 152 can also be referred to as "microphones 152". In some examples, the audio capture devices 152 can be integrated throughout one or more zones of the passenger cabin of the vehicle including the computing device 102. These zones may include an operator zone, one or more front passenger zones, and one or more rear passenger zones. As described in more detail below, these microphones 152 can capture (or in other words, record, detect, or otherwise sense) audio data, which the VOS 160 can use to adjust audio playback and support additional functionality provided by the computing device 102.

[0047] In this way, various aspects of the technology can promote a better user experience while the vehicle is traveling, while still maintaining safety concerns without interfering with the operator of the vehicle. Since multiple UPs 161 / 163 are allowed to access the VOS 160A / 160B, the VOS 160A / 160B can customize the user experience according to each individual UP in the UP 161 / 163, allowing the application of preferences specific to each individual UP. The VOS 160A / 160B system can also allow multiple users to coordinate activities (as described above), which can improve the user experience while the vehicle is traveling. Given that the additional display 150 (which can be separated from the main display (e.g., presence-sensitive display 112) of the vehicle head unit 102) may be located in the passenger cabin, where the operator of the vehicle cannot directly see the presented content, the VOS 160A / 160B can allow increased access to content while also potentially limiting any interference to the operator.

[0048] Additionally, the vehicle operating system may typically restrict access to certain features in order to avoid and / or reduce disruption to the operator of the vehicle. These security restrictions may be hard-coded (or in other words, statically compiled) into the vehicle operating system to meet certain security concerns and are typically difficult to override despite changes in operating scenarios. Given that standard infotainment systems typically include only a single display or perhaps two or three different displays that are all associated with the same single access user profile, the vehicle operating system may include these security restrictions.

[0049] In a context where multiple user profiles are concurrently accessing a single instance of a vehicle operating system, these security restrictions may not address the operating context in which the vehicle operating system exists, as the various security restrictions may only enable the operator to invoke certain safety functions that may otherwise facilitate more proactive safety measures that may assist both the operator and one or more passengers during an emergency or other situation. Thus, the vehicle operating system may limit functionality to the operator when such functionality may be extended to one or more passengers given the context. Furthermore, the vehicle operating system may enter a protected operating mode when the context does not make such a protected operating mode necessary, potentially frustrating the user's experience of the vehicle operating system (thereby potentially resulting in a waste of processing resources, such as processing cycles, memory consumption, bus bandwidth consumption, and associated power consumption).

[0050] According to various aspects of the technology described in this disclosure, VOS 160A can provide context-aware safety features. Rather than statically determining when a protected operating mode can be applied regardless of the context, various aspects of the technology described in this disclosure can enable VOS 160A and / or VOS 160B ("VOS 160") to determine the operating context in which the vehicle is currently operating, and based on the operating context, enter a protected operating mode in which VOS 160 dynamically adapts one or more operating features of VOS 160 to promote the safety of the operator of the vehicle.

[0051] The operating context may include usage of an instance of the vehicle operating system by one or more occupants of the vehicle, the presence of one or more occupants in the vehicle, the weather conditions in which the vehicle is currently operating, and the operating state of the vehicle (e.g., whether the vehicle has been in an accident, the charge level of the battery for a hybrid electric vehicle and / or a pure electric vehicle, etc.). In response to these various aspects of the operating context, the VOS 160 may reduce power consumption (e.g., in the case of a pure electric vehicle) by sensitive displays 112, 150 (e.g., reducing the brightness of such displays or turning off such displays), currently executing applications (e.g., by entering a night mode or other emergency mode execution that reduces current processing and / or display requirements), etc.

[0052] In operation, the processor 140 of the computing device 102 may execute an instance of a vehicle operating system (e.g., VOS 160A). The VOS 160A may determine the operating context in which the vehicle is currently operating. The VOS 160A may interface with any number of different vehicle sensors to determine the operating context, such as speed sensors, global positioning system (GPS) sensors, occupant sensors (e.g., which may sense weight applied to a seat), cameras, microphones, weather sensors (e.g., humidity, moisture, temperature, etc.), accelerometers, gyroscopes, infrared sensors, seat belt sensors, tire pressure sensors, or any other sensor capable of communicating with the computing device 102 (where such sensors may be represented by input components 144 and / or output components 146).

[0053] To determine the operating context, the VOS 160A may perform one or more of the following: determine usage of the VOS 160A by one or more occupants of the vehicle, determine the presence of one or more occupants of the vehicle (e.g., via one or more of occupancy status sensors, cameras, microphones, etc.), determine the weather conditions in which the vehicle is currently operating, and determine the operating state of the vehicle. The VOS 160A may also determine the state of occupant interaction state elements (e.g., physical buttons within the cabin of the vehicle that are disposed out of reach of the operator of the vehicle, such as physical buttons on a passenger door).

[0054] The VOS 160A may enter a protected operating mode in which the vehicle operating system dynamically adapts one or more operating characteristics of the vehicle operating system to promote the safety of an operator of the vehicle based on the operating context. For example, the VOS 160A may enter a protected operating mode in which the VOS 160A dynamically adjusts the power settings of the vehicle to reduce power consumption of a battery powering the vehicle (e.g., in a hybrid or pure electric vehicle).

[0055] As described above, the VOS 160A can present multiple user interfaces across multiple displays 150 communicatively coupled to the vehicle head unit 102, wherein each of the multiple user interfaces is associated with one or more of a plurality of user profiles. In this context, the VOS 160A can disable one or more of the displays 150 based on one or more of usage of the instance of the vehicle operating system, the presence of one or more occupants of the vehicle, weather conditions, and the operating state of the vehicle.

[0056] In this manner, various aspects of the technology can address the issue of multiple displays 112 / 150, as a multi-display configuration may use more power because the display is one of the most power-hungry modules. The power to the display 112 / 250 can be adjusted based on ambient conditions (represented by the operating context). The VOS 160 can manage the power of multiple displays 112 / 150 individually with respect to usage, user presence, weather conditions, battery life, etc. to dynamically switch power settings. Switching power settings can provide power savings in adverse conditions such as lower temperatures, while also continuing to power all displays in an emergency to help passengers report incidents / problems.

[0057] In some instances, as described above, the operating state of the vehicle includes battery life. The VOS 160A can enter a protected operating mode, which results in disabling one or more of the displays 112 / 150 based on weather conditions and battery life. That is, when it is very cold outside (e.g., below zero degrees Celsius), the battery may not perform optimally (compared to higher temperatures), and the battery life may be significantly shortened, thereby potentially reducing the driving range of a hybrid or pure electric vehicle. Therefore, the VOS 160A can disable certain displays 112 / 150 or limit the operation of the displays 112 / 150 to extend battery life, so that the operator / passenger can reach the intended destination without having to stop to recharge the battery (or in instances where no charger is available, the battery is depleted and the vehicle is stranded).

[0058] In conjunction with or as an alternative to the above examples, the VOS 160A can enter an emergency mode based on one or more of weather conditions and battery life, in which one or more applications executed by the vehicle operating system are executed in a limited access mode to maintain battery life. In this example, the VOS 160A can be executed in the emergency mode to execute applications in a so-called "dark mode" in which the display is dimmed or adapted to present applications using mostly dark colors that do not consume much power for display, reduce the execution of applications to resemble a low processing capacity processor state, or otherwise execute applications (or possibly stop executing certain high power consumption applications, such as streaming video applications) to save the life of the battery powering the vehicle.

[0059] The VOS 160A may determine the operating state as an emergency state in which the safety of the vehicle is threatened. The VOS 160A may utilize the above-mentioned vehicle sensors to determine that the vehicle has encountered a collision or other incident that reduces the safe operation of the vehicle (e.g., determining a flat tire via a tire pressure sensor). In these examples, rather than disabling all displays 112 / 150, the VOS 160A may enable all displays 112 / 150 based on the emergency state to enable multiple user profiles to report the emergency state of the vehicle.

[0060] In this way, various aspects of the technology can address various issues when driving in hazardous or extreme external conditions to maintain any vehicle resources (such as batteries) as much as possible. Examples of hazardous or extreme external conditions are driving a pure electric vehicle with a low battery on roads where stopping may not be recommended (e.g., hazardous roads) and / or driving a pure electric vehicle with a low battery when the outside temperature may be considered life-threatening (very low or very high temperatures). The VOS 160 may include a vehicle display service to run all entertainment apps in emergency mode (or even shut down) when vehicle conditions and current circumstances (external temperature or driving on hazardous roads / areas) are not ideal. The VOS 160 can disable the passenger's display 150 or any other related entertainment hardware, while limiting the operator's display 112 to run and display only necessary applications (e.g., as indicated by an emergency mode access control list - ACL).

[0061] As an alternative or in conjunction with the above examples, VOS 160 may enter a protected operating mode based on an emergency condition by disabling all audio playback of computing device 102. In this example, VOS 160 may lower the audio to enable the operator of the vehicle to potentially better focus on the emergency condition. In some instances, VOS 160 may disable all audio controls except those related to the emergency condition.

[0062] The VOS 160 may automatically communicate the status of the operator of the vehicle when in an emergency. The VOS 160 may report the status of the operator to emergency services, private security services, etc. The VOS 160 may then transfer audio control of the VOS 160 to one or more passengers based on the status of the operator of the vehicle. That is, if the operator of the vehicle is incapacitated, the VOS 160 may transfer audio control of the VOS 160 to one or more passengers so that the one or more passengers may contact emergency services on behalf of the operator. In other words, the VOS 160 may enable one or more passengers to initiate an emergency phone call to emergency services.

[0063] The VOS 160 may include a service that allows a signal to be sent from the OEM as an emergency signal. This signal will be used to disable all sounds in the car and disable controls for non-emergency audio use cases. This emergency service may also be used to signal when the driver is incapacitated and possibly transfer audio system control to other users in the car. Generally, this may also automatically enable other users to control the main cabin emergency system. Thus, in the event of a driver incapacitation, a user may be able to perform a phone call.

[0064] As described below, the vehicle head unit 102 may be located in a center console of a front dashboard of the vehicle and include a primary display 112 through which an operator of the vehicle interfaces with the vehicle head unit 102. The VOS 160 may determine whether the operator of the vehicle or one or more passengers of the vehicle are using the primary display 112 of the vehicle head unit 102. In response to determining that one or more passengers of the vehicle are using the primary display 112, the VOS 160 may then disable the protected operating mode to allow the one or more passengers to interface with the VOS 160 via the primary display 112.

[0065] The VOS 160 may determine, at least in part, whether one or more passengers of the vehicle are using the primary display 112 by determining the speed of the vehicle, determining the occupancy status of the one or more passengers, and determining the status of the passenger interactive state element. The VOS 160 may then disable the protected operating mode based on one or more of the speed of the vehicle, the occupancy status of the one or more passengers, and the status of the passenger interactive state element to allow the one or more passengers to interface with the VOS 160 via the primary display 112. The passenger interactive state element may include a physical button that is disposed out of reach of an operator of the vehicle.

[0066] In other words, various aspects of the technology described in the present disclosure include a vehicle head unit 102, a speed sensor, an occupancy status sensor, and an additional button (passenger UX button) for requesting the removal of restrictions. Speed ​​sensor: Through this sensor, the vehicle head unit 102 can identify whether the car is parked or moving. Occupancy status sensor: Through this sensor, the vehicle head unit 102 can identify whether a passenger is actually sitting on the passenger seat. Passenger UX button: This button should be placed out of the driver's reach and can mostly be placed on the passenger door control panel.

[0067] Here is the algorithm to apply this strategy: When the car is started, the state of the passenger UX button should be checked, if the button is initially on, we can assume that the button is broken and the de-restriction will stop working. When the car is moving and the head unit shows some UX. If the button is off, the head unit applies the car UX restrictions by definition. If the button is on and the occupancy status sensor indicates that there is an occupant, the vehicle head unit 102 may remove the car UX restrictions when the button is on (or a certain timeout may apply).

[0068] As described above, VOS 160 may determine an emergency state in which the safety of the vehicle is threatened. In response to determining the emergency state, VOS 160 may present an emergency mode user interface that includes a panic button for automatically requesting emergency services. VOS 160 may initiate communication with emergency services in response to receiving input corresponding to selection of the panic button.

[0069] In this way, after a car accident, the displays 112 / 150 enter an emergency mode. Emergency mode is the easiest way to call for help. An example of an emergency mode is that all displays show a 'panic' button, and pressing the button automatically calls for help (e.g., the car dials 911 with or without an automatic message).

[0070] The VOS 160 may determine, when determining the operating context, that the vehicle is entering a potentially unsafe operating context in which the operator of the vehicle requires additional attention. The VOS 160 may enter the protected operating mode by entering a protected operating mode in which the VOS 160 reduces the volume of the audio playback of the vehicle head unit in response to entering the potentially unsafe operating context. When configured to determine that the vehicle is potentially entering a potentially unsafe operating context, the VOS 160 may determine, as an example, that the vehicle is passing another vehicle by crossing into oncoming traffic. Thus, when the vehicle detects a stressful situation (e.g., another approaching vehicle in the opposite direction during an intrusion), it reduces the display volume or any other entertainment potential distraction.

[0071] In this regard, various aspects of the technology can improve the operation of the vehicle head unit 102 itself by dynamically entering a protected operating mode to potentially improve the level of safety associated with operating the vehicle. For example, in the context of battery life, the VOS 160 can disable or reduce the operation of the display 112 / 150 to maintain battery life so that the vehicle can reach a predetermined destination without depleting the battery powering the vehicle, which can improve safety, particularly when weather conditions may otherwise pose a significant risk to the health of the operator and / or passengers (e.g., when it is very cold or hot outside the controlled environment of the vehicle). Thus, various aspects of the technology described in the present disclosure can improve the operation of the vehicle itself in terms of providing safety for the operator and / or passengers (which can include the "operator" in the context of an autonomous vehicle).

[0072] Furthermore, by dynamically entering a protected operating mode only when certain conditions are met (or in other words, when the operating context warrants entering the protected operating mode), various aspects of the technology can reduce erroneous entry into a protected operating mode in operating contexts where such entry is not warranted. By avoiding unnecessary entry into an unnecessary protected operating mode, the VOS 160 can improve the user experience while potentially still addressing operator and / or passenger safety issues in a number of different ways.

[0073] Figure 2 is a diagram illustrating an example of a vehicle including a computing system configured to execute a vehicle operating system that operates in accordance with various aspects of the single-instance multi-user techniques described in the present disclosure. Figure 2 As shown in the example of , the interior of vehicle 200 (which may be referred to as the “cabin”) may include a computing system in the form of a vehicle head unit 202 , which represents an example of computing device 102 .

[0074] exist Figure 2 In the example of FIG. 2 , the vehicle head unit 202 is integrated into a generally central portion of the front instrument panel 220 (e.g., a center console). The vehicle head unit 202 includes a display 212, which may represent an example of a presence-sensitive display 112. The vehicle 200 may also include displays 250A, 250B, and 250C, which may represent the above-mentioned Figure 1 The example of display 150 described above is shown as display 250A being integrated into the passenger side of front instrument panel 220. Figure 2 Not shown in the example of FIG. 2 , but a display similar to display 250A may be integrated into the operator side of the front instrument panel 220. Displays 250B and 250C are integrated into the rear passenger compartment of the cabin (i.e., in the Figure 2In the example of FIG. 2 , on both the operator side (display 250B) and the passenger side (display 250C) of the front seat's headrest.

[0075] As described above, VOS 160A may interface with a first user (front passenger) via a first user interface (e.g., presented by display 250A) associated with a first user profile (e.g., UP 161A) to interact with content presented by a second user interface (e.g., presented by display 250B) associated with a second user profile (e.g., UP 161B) in the plurality of UPs 161. In some instances, VOS 160A may interface with the first user to perform one or more of the following: view content presented by the second user interface at the first user interface or initiate playback of the content at the first user interface.

[0076] VOS 160A may also interface with the first user to control audio playback of a second user interface presented by display 250B. VOS 160A may interface with the first user to change the audio volume associated with audio playback of a second user interface presented by display 250B via the first user interface presented by display 250A.

[0077] The VOS 160A may also interface with the first user to enable the first user and a second user (e.g., an operator-side rear passenger) to jointly interact with content presented by a second user interface presented via the display 250B. In this example, the VOS 160A may interface with the first user to enable the first user and the second user to jointly facilitate audio playback of the second user interface (such as by jointly collaborating to build an audio playlist). As another example, the VOS 160A may also interface with the first user to enable the first user and the second user to jointly facilitate a multi-user activity presented by the second user interface, wherein such a multi-user activity may include a navigation activity in which both the first user and the second user facilitate navigation of a vehicle 200 that includes a vehicle head unit 202 and / or a multi-player video game presented by the second user interface.

[0078] Although illustrated as multiple physical displays 212 / 250, various aspects of the technology may operate with respect to a single physical display (or multiple physical displays) having separate logically separated displays (or so-called virtual displays). That is, a single physical display 212 / 250 may be logically split (e.g., via software) to represent two different physical displays (from the perspective of an instance of the VOS 160). In this regard, a single physical display may represent multiple different displays, and the displays 212 / 250 may each represent a logically separate virtual display.

[0079] In this regard, various aspects of the technology described herein may enable a number of different use cases, including the following: Parents want to know what their kids are watching; Parents or drivers wish to control the volume of the child display; Two or more passengers may want to contribute to a shared playlist; and Two or more passengers may want to interact with the same content (like multiple game players). The following use cases can be enabled given that the technology allows: Mirror display content when running on Android Auto; Allowing drivers and passengers to mirror their displays; and Allows the driver or passenger to send input (key, rotation, D-pad, touch, etc. events) to other passengers' displays.

[0080] In other words, various aspects of the technology described herein can solve problems associated with enabling mobile apps to interact with each other (same or different apps) across multiple concurrent users on a single Android instance. Thus, the technology can enable rear seat interaction with the operator to add a stop in navigation, and / or enable operator interaction with the rear seat (such as a child) to play a video.

[0081] VOS 160A may also interface with a first user (front passenger) of the plurality of users via a first user interface associated with UP 161A to share content presented by the first user interface with a second user interface of the plurality of user interfaces associated with UP 161B. For example, VOS 160A may receive a gesture at a first user interface presented by display 250A, for example, indicating that content presented by the first user interface is to be shared with a second user interface presented by, for example, display 250B. The gesture may include one or more of a swipe gesture, a pinch gesture, a tap gesture, or any other gesture associated with using a presence-sensitive display such as display 250A.

[0082] In some instances, VOS 160A may be configured to present an initiating animation at the first user interface indicating that content is being shared. Additionally or alternatively, VOS 160A may play initiating audio indicating that content is being shared. In some examples, VOS 160A may play spatialized audio to reflect the position of the first user interface relative to the position of the second user interface when playing the initiating audio indicating that content is being shared.

[0083] In this regard, various aspects of the technology can use advanced user interface technology to make cross-display interactions (such as shared screens) more immersive. Based on the positional relationship between passenger areas in the vehicle, the technology can achieve the following: Use gestures (swipe, tap, etc.) to send content from one display to another; Use animation to visualize interactions; and Use spatial audio to show where the content is moving to make it more immersive.

[0084] Figure 3 2 is a diagram illustrating different interaction models with multiple displays including interactions that occur via a single instance multi-user model and a multi-instance multi-user model according to the vehicle operating system techniques described in this disclosure. As discussed in this disclosure, vehicle displays (such as displays 212 and 250) are evolving from operator-centric to a total car experience where passengers may have: a curated selection of personal experiences on the commute; Enjoy the collective experience of a fun family trip; and Shared experience in a ridesharing environment.

[0085] Original Equipment Manufacturers (OEMs) can identify these needs and are building vehicles to provide these experiences to users. These are no longer seen as premium experiences, but rather as the value of a desirable vehicle.

[0086] In this regard, users may seek concurrent experiences across displays for a seamless and immersive experience, such as: Navigation - add stops of the current journey to the driver's display; Entertainment - Play and control videos or games for children in the back seat to keep them engaged and entertained; Users - access their own curated apps, content, and data for entertainment and / or productivity; and Personalization - Control my seat settings, HVAC controls, my seat alerts.

[0087] OEMs are considering following a user interaction model based on expectations of user behavior. There are three types of interaction models (e.g. Figure 3 ) as shown in the example: 1. The in-vehicle infotainment (IVI) display is the primary controller for content on the front seat entertainment (FSE) and rear seat entertainment (RSE); a. FSE and RSE have minimal controls - audio, play / pause, on / off, etc. 2. IVI screens are mirrored across FSE / RSE, with no content selection or control available on the passenger display; and 3. Content can be shared across all screens, each with its own individual controls.

[0088] The following user roles exist in a multi-monitor scenario: Driver: Interact with the instrument cluster and IVI screens for driving and interact with other screens in the car Front seat passengers: Use FSE to assist drivers with navigation and passengers with content Rear seat passengers: Interact with RSE for content, control and navigation advice to the driver Visitors: Traveling temporarily in a car and want to access some apps on the passenger display

[0089] Figure 4 is a diagram illustrating an example vehicle including a vehicle head unit configured to control audio content in accordance with various aspects of the single-instance multi-user vehicle operating system techniques described in this disclosure. Figure 4 In the example of FIG. 1 , vehicle 400 may represent vehicle 200 (eg Figure 24B) where vehicle head unit 202 can enable privacy and sharing between different audio zones 404A through 404D ("audio zones 404") within vehicle 400. Audio zone 404A can represent the front seat operator side zone (also represented as "front operator zone 404A"). Audio zone 404B can represent the front seat passenger side zone (also represented as "front passenger zone 404B"). Audio zone 404C can represent the operator side rear passenger zone, and audio zone 404D can represent the passenger side rear passenger zone.

[0090] In each of the audio zones 404, the vehicle 200 may include a corresponding audio capture device in audio capture devices 452A to 452D ("audio capture devices 452") and a corresponding speaker in speakers 454A to 454D ("speakers 454"). The audio capture device 452 may represent an example of the audio capture device 152. Both the audio capture device 452 and the speaker 454 may represent a transducer that, in the example of the audio capture device 452, is capable of converting sound pressure into an electrical signal representing a sound field, and in the example of the speaker 454, is capable of converting the electrical signal representing a sound field into a corresponding sound field.

[0091] Although described as having a single audio capture device in the audio capture device 452 and a single speaker in the speaker 454 in each of the audio zones 404, each of the audio zones 404 may include more or fewer audio capture devices 452 and more or fewer speakers 454. Further, although described as transducers, any type of device capable of capturing audio data (transformed from electrical signals captured by the audio capture device 452) and reproducing a sound field from electrical signals (transformed from audio data) may be utilized in one or more of the audio zones 404. Additionally, although described as transducers, any type of device capable of capturing audio data (transformed from electrical signals captured by the audio capture device 452) and reproducing a sound field from electrical signals (transformed from audio data) may be utilized in one or more of the audio zones 404. Figure 4 Four audio zones 404 are shown in the example of FIG. 4 , but vehicle 400 may include more or fewer audio zones 404 .

[0092] Regardless, VOS 160A may interface with multiple users to control audio playback within one or more of zones 404 of a passenger cabin of vehicle 400 that includes vehicle head unit 202. For example, VOS 160A may interface with multiple users to control the volume in a single one of zones 404 of the passenger cabin. As another example, VOS 160A may interface with multiple users to control the focus of audio playback in at least one of zones 404 of the passenger cabin.

[0093] Thus, various aspects of the technology may provide a central service for audio control for all users (e.g., driver and / or passenger) concurrently to control audio settings (volume up / volume down, mute, unmute, or any other control). To facilitate such control, the VOS 160A may provide services for managing audio controls (e.g., volume, mute, settings, ducking, blackouts, etc.) to provide the following: Manage controls independently for each user in their respective audio zone; Manage other users' focus in a separate zone; Also taking into account current security constraints; and Also take into account the current user role (driver, passenger, disabled passenger, rear seat passenger).

[0094] In addition, one or more of the audio capture devices 452 can capture audio data representing the sound field at each of the one or more zones 404 (which is another way of referring to the audio zones 404). The VOS 160A can determine that a first user of a plurality of users in a first zone (e.g., zone 404C) of the one or more zones is speaking in an attempt to vocally interface with the vehicle head unit 202 based on the audio data representing the sound field occurring at each of the zones 404. The VOS 160A can adjust the audio playback at the zones 404 based on the audio data representing the sound field occurring at each of the zones 404.

[0095] In terms of adjusting audio playback, the VOS 160A may determine a noise level based on audio data representing the sound field present at each of the zones 404. The VOS 160A may then adjust audio playback at one or more of the zones 404 based on the noise level.

[0096] In this regard, various aspects of the technology may address how to implement multi-microphone support for the VOS 160A. The VOS 160A may use the audio data captured by the audio capture device 452 to determine and / or perform the following: Using microphones to understand which user is talking and speaking, so that volume controls can be adjusted by identifying the user; Map to the display being used; Provide better assistant responses for (speaking) users; Detecting the noise level around each user (their corresponding area) and performing the audio changes required for audio playback to achieve comfortable audio listening; It also combines each user’s audio information to determine the noise level in the car and applies changes to the speakers for a better listening environment;

[0097] Figure 5 and Figure 6 is a diagram illustrating audio control in a single instance multi-user vehicle operating system in accordance with various aspects of the technology described in this disclosure. In some instances, the vehicle operating system is limited in scope in that such vehicle operating system can only send audio from one zone to another for that particular application unique identifier (UID). Various aspects of the technology described in this disclosure enable zone 404 to share audio to the cabin for the following purposes: Shared media audio from passengers to the main cabin; Providing a mechanism for passengers not in the main cabin to request that audio be played to the main zone (e.g., operator zone 404A); Provides a mechanism for drivers to allow audio to be played in the main zone; Provides a mechanism for sharing audio focus between two different zones; and Prohibit volume control by non-cabin owners;

[0098] For example, a passenger listening to media in a rear seat entertainment (RSE) zone (e.g., one of zones 404C or 404D) can send the audio to the main cabin to allow everyone in the car to listen to the audio. Although the passenger in the rear seat RSE would choose to send the audio to the main cabin, the operator (or main cabin user) would still maintain control over allowing the audio to play, as well as retaining control over the volume and other audio settings.

[0099] Figure 5 A high-level overview of the current audio architecture is shown. Audio zones 404 are defined in the configuration to set the audio routing for each audio zone 404. Each of the audio zones 404 is defined as a collection of volume groups; each group contains a set of devices that are controlled based on volume changes on the volume group. Each device can have different audio contexts routed into the device. The vehicle audio service can use the routing information for each audio zone to define a set of audio mixes that the VOS 160A can use to configure the audio routing for each of the zones 404.

[0100] Next reference Figure 6, shows the configuration setup between the vehicle audio service and the vehicle occupant zone service. For audio, the vehicle audio service can read the audio zone (audioZoneId) to occupant zone Id (occupantZoneId) mapping from the configuration. This information can be sent to the car occupant zone service to set up the occupant zone configuration during initialization. The occupant zone service can maintain information about the occupant zone configuration and display port mapping, which can be read from different configuration information.

[0101] The Car Audio Service can register a VehicleOccupantZoneCallback on the Occupant Zone Service. The VOS 160A can trigger this service when any of the following changes occur in the vehicle occupant zone: Display activation; Audio configuration changes; Crew area user assignment; Passenger starts; and Passengers stop.

[0102] When the audio service receives the onOccupantZoneConfigChanged signal from the callback, the audio service of the VOS 160A may automatically assign the user to its corresponding audio zone as follows: Uninstall previous user settings; Remove the previous user audio policy routing; Load audio settings for new users; Set up audio policy routing for new users; and Reset audio focus mapping for new users.

[0103] The audio service of VOS 160A may use the audio focus map to determine where incoming focus requests should be assigned.

[0104] To allow passengers to send audio to the main cabin, the following needs to happen: Handles focus requests in the main cabin; and Routing passenger audio to the main cabin Audio routing can be performed once the focus request is successfully changed from the passenger's own audio zone in the vehicle 400. For audio playback that has not yet started, the focus handling will automatically request focus in the main cabin zone according to the rules set with the audio usage priority (e.g., a current phone call will reject media audio).

[0105] The passenger should be able to request that the audio be sent to the main cabin, and a prompt will pop up for the driver to accept. Alternatively, the driver can enable a function that automatically allows the passenger to play audio. If accepted, the audio focus request can be transferred to the main cabin (if necessary) and playback can begin. If not accepted, the passenger can be prompted with a message.

[0106] Because one goal of this function is to play media for passengers in the main cabin, a passenger's focus request can be limited to media only. Focus requests for other sounds (e.g., alarms, calls, notifications, etc.) should remain in the passenger's corresponding zone. For media focus requests, the logic can be as follows: Send momentary focus loss to the passenger’s media app; Request focus for a passenger media app in the main cabin; If the focus request is granted, sending a focus gain; and If not approved due to a higher priority sound (emergency, phone call), then: Set the focus request to delayed focus; A focus is approved once a higher priority focus is completed; and Alternative: Send focus back to the user area

[0107] For passengers where user Ids are used, a possible driver for audio routing could be user id device affinity routing. This can still be used to send passenger audio to the main cabin as follows: Locate the main cabin media device (preferably a separate high-quality device); and Reset passenger device affinity to share cabin media devices.

[0108] Additionally, multi-zone audio (MZA) can facilitate individual users playing audio, all on each individual audio zone 404. This can allow users in the main cabin to play media or any other sound, while users in the rear entertainment system also play media in their respective zones. This enables OEMs to potentially design complex audio infotainment systems where each passenger can customize their own experience in the vehicle 400.

[0109] Example use cases include the following: In a car, the driver can play music while rear seat users can play their own music / media; Rear seat users can control their music volume without affecting the driver's music; A first-party music app launched in the rear seat can play the sound in the rear seat without any changes.

[0110] One mechanism for MZA is based on dynamic audio policy, specifically using UID / userId based routing. This can allow audio policy to define routing based on audio attribute usage, UID or userId. This can allow an application or service to take advantage of automatic routing of audio configured through dynamic audio policy. However, there are APIs that can be used to route audio outside of the assigned audio device. This has some impact on the car, as applications can send audio to a specific zone without user permission, for example: A rear seat entertainment (RSE) application from user A sends audio directly to the output device of the driver user in the main cabin. The RSE application from user A sends the audio directly to the output device assigned to a different RSE of user B. This may cause some concern about driver safety as the primary driver may be disturbed when unwanted sounds occur in the primary cabin.

[0111] One possible goal of this aspect of the technology is to allow current dynamic audio policies to continue to work, but restrict audio playback for users (and their corresponding applications / services) to avoid playing audio outside a set of assigned zones, regardless of the mechanism used to select devices for audio playback. For users in cars, a potential benefit is that such users will be able to continue listening to audio in the car in a private and consistent manner.

[0112] Dynamic audio policies can provide a mechanism to set devices available to users for automatic routing via the audio policy API. The audio policy API can be used or extended to restrict applications from routing audio outside of audio policy user-assigned restrictions using audio routing relative to a set of preferred devices. This should potentially limit "forced" routing to devices defined within the audio policy.

[0113] Figure 7 It is shown Figure 1 Flowchart of example operations of a computing system executing a vehicle operating system configured to perform various aspects of the safety techniques described in the present disclosure. As described above, the processor 140 of the computing device 102 can execute an instance of a vehicle operating system (e.g., VOS 160A) (700). The VOS 160A can determine an operating context in which the vehicle is currently operating (702). The VOS 160A can interface with any number of different vehicle sensors to determine the operating context, such as a speed sensor, a global positioning system (GPS) sensor, an occupant sensor (e.g., which can sense the weight applied to the seat), a camera, a microphone, a weather sensor (e.g., humidity, moisture, temperature, etc.), an accelerometer, a gyroscope, an infrared sensor, a seat belt sensor, a tire pressure sensor, or any other sensor capable of communicating with the computing device 102 (where such sensors can be represented by input components 144 and / or output components 146).

[0114] To determine the operating context, the VOS 160A may perform one or more of the following: determine usage of the VOS 160A by one or more occupants of the vehicle, determine the presence of one or more occupants of the vehicle (e.g., via one or more of occupancy status sensors, cameras, microphones, etc.), determine the weather conditions in which the vehicle is currently operating, and determine the operating state of the vehicle. The VOS 160A may also determine the state of occupant interaction state elements (e.g., physical buttons within the cabin of the vehicle that are disposed out of reach of the operator of the vehicle, such as physical buttons on a passenger door).

[0115] The VOS 160A may enter a protected operating mode in which the vehicle operating system dynamically adapts one or more operating characteristics of the vehicle operating system to promote safety of an operator of the vehicle based on the operating context (704). For example, the VOS 160A may enter a protected operating mode in which the VOS 160A dynamically adjusts power settings of the vehicle to reduce power consumption of a battery powering the vehicle (e.g., in a hybrid or all-electric vehicle).

[0116] In this manner, the above-described technology can implement the following examples.

[0117] Example 1. A method comprising: executing, via a vehicle head unit of a vehicle, an instance of a vehicle operating system; determining, via the instance of the vehicle operating system, an operating context in which the vehicle is currently operating; and entering, via the instance of the vehicle operating system, based on the operating context, a protected operating mode in which the vehicle operating system dynamically adapts one or more operating features of the vehicle operating system to promote the safety of an operator of the vehicle.

[0118] Example 2. The method of Example 1, wherein entering the protected operating mode comprises entering a protected operating mode in which the vehicle operating system dynamically adjusts power settings of the vehicle to reduce power consumption of a battery powering the vehicle.

[0119] Example 3. A method as described in any combination of Examples 1 and 2, wherein determining the operating context includes one or more of the following: determining usage of the instance of the vehicle operating system by one or more passengers in the vehicle; determining the presence of the one or more passengers in the vehicle; determining the weather conditions in which the vehicle is currently operating; and determining an operating state of the vehicle.

[0120] Example 4. A method as described in Example 3, wherein the instance of the vehicle operating system facilitates concurrent access to multiple user profiles, wherein the method further includes presenting multiple user interfaces through the instance of the vehicle operating system across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of the multiple user profiles, and wherein entering the protected operating mode includes disabling one or more of the multiple displays based on one or more of the usage of the instance of the vehicle operating system, the presence of the one or more occupants of the vehicle, the weather conditions, and the operating state of the vehicle.

[0121] Example 5. The method of Example 4, wherein the one or more passengers of the vehicle are associated with at least one of the plurality of user profiles.

[0122] Example 6. A method as described in any combination of Examples 3 to 5, wherein the instance of the vehicle operating system facilitates concurrent access to multiple user profiles, wherein the operating state of the vehicle includes battery life, wherein the method further includes presenting multiple user interfaces through the instance of the vehicle operating system across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of the multiple user profiles, and wherein entering the protected operating mode includes disabling one or more of the multiple displays based on the weather conditions and the battery life.

[0123] Example 7. A method as described in any combination of Examples 3 to 6, wherein the instance of the vehicle operating system facilitates concurrent access to multiple user profiles, wherein the operating state of the vehicle includes battery life, wherein the method further includes presenting multiple user interfaces through the instance of the vehicle operating system across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of the multiple user profiles, and wherein entering the protected operating mode includes entering an emergency mode based on one or more of the weather conditions and the battery life, in which one or more applications executed by the vehicle operating system are executed in a restricted access mode to maintain the battery life.

[0124] Example 8. A method as described in any combination of Examples 3 to 7, wherein determining the operating state of the vehicle includes determining an emergency state in which the safety of the vehicle is threatened, wherein the method further includes presenting, through the instance of the vehicle operating system, multiple user interfaces across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of a plurality of user profiles, and wherein entering the protected operating mode includes enabling all of the multiple displays based on the emergency state to enable the multiple user profiles to report the emergency state of the vehicle.

[0125] Example 9. A method as described in any combination of Examples 3 to 8, wherein determining the operating state of the vehicle includes determining an emergency state in which the safety of the vehicle is threatened, and wherein entering the protected operating mode includes disabling all audio playback of the vehicle head unit based on the emergency state.

[0126] Example 10. A method as described in any combination of Examples 3 to 9, wherein determining the operating state of the vehicle includes determining an emergency state in which the safety of the vehicle is threatened, and wherein entering the protected operating mode includes disabling all audio controls except audio controls related to the emergency state.

[0127] Example 11. A method as described in any combination of Examples 3 to 10, wherein determining the operating state of the vehicle includes determining an emergency state in which the safety of the vehicle is threatened, and wherein entering the protected operating mode includes: automatically transmitting the state of the operator of the vehicle when in the emergency state; and transferring audio control of the vehicle operating system to the one or more passengers based on the state of the operator of the vehicle.

[0128] Example 12. The method of Example 11, wherein transferring the audio control of the vehicle operating system enables the one or more passengers to initiate an emergency telephone call to emergency services.

[0129] Example 13. A method as described in any combination of Examples 3 to 12, wherein the vehicle head unit is located in a center console of a front dashboard of the vehicle and includes a main display through which the operator of the vehicle interfaces with the vehicle head unit, wherein determining the usage of the instance of the vehicle operating system includes determining whether the operator of the vehicle or the one or more passengers of the vehicle are using the main display of the vehicle head unit, and wherein entering the protected operating mode includes disabling the protected operating mode to allow the one or more passengers to interface with the vehicle operating system via the main display in response to determining that the one or more passengers of the vehicle are using the main display.

[0130] Example 14. A method as described in Example 13, wherein determining whether the one or more passengers of the vehicle are using the main display includes one or more of the following: determining the speed of the vehicle; determining the occupancy status of the one or more passengers; and determining the state of a passenger interaction status element.

[0131] Example 15. A method as described in Example 14, wherein entering the protected operating mode includes disabling the protected operating mode based on one or more of the speed of the vehicle, the occupancy status of the one or more passengers, and the state of the passenger interaction state element to allow the one or more passengers to interface with the vehicle operating system via the main display.

[0132] Example 16. The method of any combination of Examples 14 and 15, wherein the passenger interactive state element comprises a physical button disposed out of reach of the operator of the vehicle.

[0133] Example 17. A method as described in any combination of Examples 3 to 16, wherein determining the operating state of the vehicle includes determining an emergency state in which the safety of the vehicle is threatened, and wherein entering the protected operating mode includes: presenting an emergency mode user interface including a panic button, through which emergency services are automatically requested; and initiating communication with the emergency services in response to receiving input corresponding to selection of the panic button.

[0134] Example 18. A method as described in any combination of Examples 1 to 17, wherein determining the operating context includes determining that the vehicle is entering a potentially unsafe operating context in which the operator of the vehicle requires additional attention, and wherein entering the protected operating mode includes entering a protected operating mode in which the vehicle operating system reduces the volume of audio playback of the vehicle head unit in response to entering the potentially unsafe operating context.

[0135] Example 19. The method of Example 18, wherein determining that the vehicle is potentially entering the potentially unsafe operating situation includes determining that the vehicle is passing another vehicle by crossing into oncoming traffic.

[0136] Example 20. A method as described in any combination of Examples 1 to 19, wherein the instance of the vehicle operating system facilitates concurrent access to multiple user profiles, wherein the method further includes: authorizing the multiple user profiles to interface with the instance of the vehicle operating system through the instance of the vehicle operating system; presenting multiple user interfaces through the instance of the vehicle operating system across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of the multiple user profiles; and interfacing with multiple users associated with the one or more of the multiple user profiles via the multiple user interfaces to enable the multiple users to interface with the instance of the vehicle operating system to control functions associated with the vehicle head unit.

[0137] Example 21. A method as described in Example 20, wherein the instance of the vehicle operating system includes a first instance of the vehicle operating system, wherein the method further includes executing a second instance of the vehicle operating system, and wherein the first instance of the vehicle operating system includes an interface for communicating with the second instance of the vehicle operating system to facilitate concurrent access to the multiple user profiles.

[0138] Example 22. A method as described in Example 21, wherein the vehicle head unit includes a high processing capacity processor that executes the first instance of the vehicle operating system, wherein the vehicle head unit includes a low processing capacity processor that executes the second instance of the vehicle operating system, and wherein the high processing capacity processor provides more processing capacity than the low processing capacity processor.

[0139] Example 23. The method of any combination of Examples 20 and 21, wherein the plurality of displays are displaced around a passenger cabin of a vehicle including the vehicle head unit.

[0140] Example 24. A method as described in any combination of Examples 20 to 23, wherein the multiple displays include two or more of the following: a first display, which is integrated into an operator side of a front dashboard of a passenger cabin of a vehicle including the vehicle head unit; a second display, which is integrated into a center console of the front dashboard; a third display, which is integrated into a passenger side of the front dashboard; and a fourth display, which is integrated into a rear passenger compartment of the passenger cabin.

[0141] Example 25. The method of any combination of Examples 20 to 24, wherein the plurality of displays includes one or more computing devices associated with at least one user of the plurality of users who is a passenger in a vehicle including the vehicle head unit.

[0142] Example 26. A computing device comprising: a memory configured to store an instance of a vehicle operating system; and one or more processors for executing the instance of the vehicle operating system, wherein the instance of the vehicle operating system is configured to: determine an operating context in which the vehicle is currently operating; and based on the operating context, enter a protected operating mode of the vehicle operating system in which one or more operating features of the vehicle operating system are dynamically adapted to facilitate the safety of an operator of the vehicle.

[0143] Example 27. A computing device as described in Example 26, wherein the instance of the vehicle operating system is configured to enter a protected operating mode in which the vehicle operating system dynamically adjusts power settings of the vehicle to reduce power consumption of a battery powering the vehicle.

[0144] Example 28. A computing device as described in any combination of Examples 26 and 27, wherein the instance of the vehicle operating system is configured to perform one or more of the following: determining usage of the instance of the vehicle operating system by one or more passengers in the vehicle; determining the presence of the one or more passengers in the vehicle; determining the weather conditions in which the vehicle is currently operating; and determining an operating state of the vehicle.

[0145] Example 29. A computing device as described in Example 28, wherein the instance of the vehicle operating system facilitates concurrent access to multiple user profiles, wherein the instance of the vehicle operating system is further configured to present multiple user interfaces across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of the multiple user profiles, and wherein the instance of the vehicle operating system is configured to disable one or more of the multiple displays based on one or more of the usage of the instance of the vehicle operating system, the presence of the one or more occupants of the vehicle, the weather conditions, and the operating state of the vehicle.

[0146] Example 30. The computing device of Example 29, wherein the one or more passengers of the vehicle are associated with at least one of the plurality of user profiles.

[0147] Example 31. A computing device as described in any combination of Examples 28 to 30, wherein the instance of the vehicle operating system facilitates concurrent access to multiple user profiles, wherein the operating state of the vehicle includes battery life, wherein the instance of the vehicle operating system is further configured to present multiple user interfaces across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of the multiple user profiles, and wherein the instance of the vehicle operating system is configured to disable one or more of the multiple displays based on the weather conditions and the battery life.

[0148] Example 32. A computing device as described in any combination of Examples 28 to 31, wherein the instance of the vehicle operating system facilitates concurrent access to multiple user profiles, wherein the operating state of the vehicle includes battery life, wherein the instance of the vehicle operating system is further configured to present multiple user interfaces across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of the multiple user profiles, and wherein entering the protected operating mode includes entering an emergency mode based on one or more of the weather conditions and the battery life, in which one or more applications executed by the vehicle operating system are executed in a restricted access mode to maintain the battery life.

[0149] Example 33. A computing device as described in any combination of Examples 28 to 32, wherein the instance of the vehicle operating system is configured to determine an emergency state in which the safety of the vehicle is threatened, wherein the instance of the vehicle operating system is further configured to present multiple user interfaces across multiple displays communicatively coupled to the vehicle head unit, each of the multiple user interfaces being associated with one or more of a plurality of user profiles, and wherein the instance of the vehicle operating system is configured to enable all of the multiple displays based on the emergency state to enable the multiple user profiles to report the emergency state of the vehicle.

[0150] Example 34. A computing device as described in any combination of Examples 28 to 33, wherein the instance of the vehicle operating system is configured to determine an emergency state in which the safety of the vehicle is threatened, and wherein the instance of the vehicle operating system is configured to disable all audio playback of the vehicle head unit based on the emergency state.

[0151] Example 35. A computing device as described in any combination of Examples 28 to 34, wherein the instance of the vehicle operating system is configured to determine an emergency state in which the safety of the vehicle is threatened, and wherein the instance of the vehicle operating system is configured to disable all audio controls except audio controls related to the emergency state.

[0152] Example 36. A computing device as described in any combination of Examples 28 to 35, wherein the instance of the vehicle operating system is configured to determine an emergency state in which the safety of the vehicle is threatened, and wherein the instance of the vehicle operating system is configured to: automatically transmit the status of the operator of the vehicle when in the emergency state; and transfer audio control of the vehicle operating system to the one or more passengers based on the status of the operator of the vehicle.

[0153] Example 37. The computing device of Example 36, wherein the instance of the vehicle operating system is configured to transfer the audio control of the vehicle operating system to enable the one or more passengers to initiate an emergency telephone call to emergency services.

[0154] Example 38. A computing device as described in any combination of Examples 28 to 37, wherein the vehicle head unit is located in a center console of a front dashboard of the vehicle and includes a main display through which the operator of the vehicle interfaces with the vehicle head unit, wherein the instance of the vehicle operating system is configured to determine whether the operator of the vehicle or the one or more passengers of the vehicle is using the main display of the vehicle head unit, and wherein the instance of the vehicle operating system is configured to disable the protected operating mode to allow the one or more passengers to interface with the vehicle operating system via the main display in response to determining that the one or more passengers of the vehicle are using the main display.

[0155] Example 39. A computing device as described in Example 38, wherein the instance of the vehicle operating system is configured to perform one or more of the following: determining a speed of the vehicle; determining an occupancy status of the one or more passengers; and determining a state of a passenger interaction state element.

[0156] Example 40. A computing device as described in Example 39, wherein the instance of the vehicle operating system is configured to disable the protected operating mode based on one or more of the speed of the vehicle, the occupancy status of the one or more passengers, and the state of the passenger interaction state element to allow the one or more passengers to interface with the vehicle operating system via the primary display.

[0157] Example 41. The computing device of any combination of Examples 39 and 40, wherein the passenger interaction state element comprises a physical button disposed out of reach of the operator of the vehicle.

[0158] Example 42. A computing device as described in any combination of Examples 28 to 41, wherein the instance of the vehicle operating system is configured to determine an emergency state in which the safety of the vehicle is threatened, and wherein the instance of the vehicle operating system is configured to: present an emergency mode user interface including a panic button, through which emergency services are automatically requested; and initiate communication with the emergency services in response to receiving input corresponding to selection of the panic button.

[0159] Example 43. A computing device as described in any combination of Examples 26 to 42,

[0160] wherein the instance of the vehicle operating system is configured to: determine that the vehicle is entering a potentially unsafe operating situation in which the operator of the vehicle requires additional attention; and in response to entering the potentially unsafe operating situation, enter a protected operating mode of the vehicle operating system in which the volume of audio playback of the vehicle head unit is reduced.

[0161] Example 44. The computing device of Example 43, wherein the instance of the vehicle operating system is configured to determine that the vehicle is passing another vehicle by crossing into oncoming traffic.

[0162] Example 45. A computing device as described in any combination of Examples 26 to 44, wherein the instance of the vehicle operating system includes a first instance of the vehicle operating system, wherein the one or more processors are further configured to execute a second instance of the vehicle operating system, and wherein the first instance of the vehicle operating system includes an interface for communicating with the second instance of the vehicle operating system to facilitate concurrent access to the multiple user profiles.

[0163] Example 46. A computing device as described in Example 45, wherein the one or more processors include a high processing capacity processor that executes the first instance of the vehicle operating system, wherein the one or more processors include a low processing capacity processor that executes the second instance of the vehicle operating system, and wherein the high processing capacity processor provides more processing capacity than the low processing capacity processor.

[0164] Example 47. The computing device of any combination of Examples 45 and 46, wherein the plurality of displays are displaced around a passenger cabin of a vehicle including the vehicle head unit.

[0165] Example 48. A computing device as described in any combination of Examples 45 to 47, wherein the multiple displays include two or more of the following: a first display, the first display being integrated into an operator side of a front dashboard of a passenger cabin of a vehicle including the vehicle head unit; a second display, the second display being integrated into a center console of the front dashboard; a third display, the third display being integrated into a passenger side of the front dashboard; and a fourth display, the fourth display being integrated into a rear passenger compartment of the passenger cabin.

[0166] Example 49. A computing device as described in any combination of Examples 45 to 48, wherein the plurality of displays includes one or more computing devices associated with at least one user of the plurality of users who is a passenger in a vehicle including the vehicle head unit.

[0167] Example 50. A non-transitory computer-readable storage medium having instructions stored thereon, which, when executed, cause one or more processors to: execute an instance of a vehicle operating system; determine, via the instance of the vehicle operating system, an operating context in which the vehicle is currently operating; and enter, via the instance of the vehicle operating system, based on the operating context, a protected operating mode in which the vehicle operating system dynamically adapts one or more operating features of the vehicle operating system to facilitate the safety of an operator of the vehicle.

[0168] In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or sent through a computer-readable medium as one or more instructions or codes and executed by a hardware-based processing unit. A computer-readable medium may include a computer-readable storage medium corresponding to: a tangible medium, such as a data storage medium; or a communication medium, including, for example, any medium that facilitates the transfer of a computer program from one place to another according to a communication protocol. In this manner, a computer-readable medium may generally correspond to (1) a non-transitory tangible computer-readable storage medium or (2) a communication medium such as a signal or carrier wave. A data storage medium may be any available medium that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in the present disclosure. A computer program product may include a computer-readable medium.

[0169] By way of example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, flash memory, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves are used to send instructions from a website, server or other remote source, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of the medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carriers, signals or other temporary media, but rather relate to non-temporary tangible storage media. Disks and optical disks such as used include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blue optical disks, ultra blue light, etc., where disks usually reproduce data magnetically, and optical disks reproduce data optically with lasers. The combination of the above items should also be included in the scope of computer-readable media.

[0170] The instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuit systems. Thus, the term "processor" as used may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Additionally, in some aspects, the described functionality may be provided within dedicated hardware and / or software modules. Furthermore, the techniques may be fully implemented in one or more circuits or logic elements.

[0171] The techniques of the present disclosure may be implemented in a variety of devices or apparatuses, including wireless handsets, integrated circuits (ICs), or a set of ICs (e.g., a chipset). Various components, modules, or units are described in the present disclosure to emphasize the functional aspects of a device configured to perform the disclosed techniques, but the components, modules, or units do not necessarily need to be implemented by different hardware units. Rather, as described above, the various units may be combined in a hardware unit, or provided by a collection of interoperable hardware units including one or more processors as described above in combination with appropriate software and / or firmware.

[0172] Various examples have been described. These and other examples are within the scope of the following claims.

Claims

1. A method comprising: executing an instance of a vehicle operating system via a vehicle head unit of the vehicle; determining, by the instance of the vehicle operating system, an operating context in which the vehicle is currently operating; as well as A protected operating mode is entered, by the instance of the vehicle operating system based on the operating context, in which one or more operating characteristics of the vehicle operating system are dynamically adapted to promote safety of an operator of the vehicle.

2. The method of claim 1, wherein entering the protected operating mode comprises entering a protected operating mode in which the vehicle operating system dynamically adjusts power settings of the vehicle to reduce power consumption of a battery powering the vehicle.

3. The method of any one of claims 1 and 2, wherein determining the operating context comprises one or more of the following: determining usage of the instance of the vehicle operating system by one or more occupants of the vehicle; determining the presence of the one or more passengers in the vehicle; determining weather conditions in which the vehicle is currently operating; as well as An operating state of the vehicle is determined.

4. The method according to claim 3, wherein said instance of said vehicle operating system facilitates concurrent access by multiple user profiles, wherein the method further comprises presenting, by the instance of the vehicle operating system, a plurality of user interfaces across a plurality of displays communicatively coupled to the vehicle head unit, each of the plurality of user interfaces being associated with one or more of the plurality of user profiles, and Wherein entering the protected operating mode includes disabling one or more of the plurality of displays based on one or more of the usage of the instance of the vehicle operating system, the presence of the one or more occupants of the vehicle, the weather conditions, and the operating state of the vehicle. 5 . The method of claim 4 , wherein the one or more passengers of the vehicle are associated with at least one of the plurality of user profiles.

6. The method according to any one of claims 3 to 5, wherein said instance of said vehicle operating system facilitates concurrent access by multiple user profiles, wherein the operating state of the vehicle includes battery life, wherein the method further comprises presenting, by the instance of the vehicle operating system, a plurality of user interfaces across a plurality of displays communicatively coupled to the vehicle head unit, each of the plurality of user interfaces being associated with one or more of the plurality of user profiles, and Wherein entering the protected operating mode comprises disabling one or more of the plurality of displays based on the weather conditions and the battery life.

7. The method according to any one of claims 3 to 6, wherein said instance of said vehicle operating system facilitates concurrent access by multiple user profiles, wherein the operating state of the vehicle includes battery life, wherein the method further comprises presenting, by the instance of the vehicle operating system, a plurality of user interfaces across a plurality of displays communicatively coupled to the vehicle head unit, each of the plurality of user interfaces being associated with one or more of the plurality of user profiles, and Wherein entering the protected operating mode includes entering an emergency mode based on one or more of the weather conditions and the battery life, in which the emergency mode executes one or more applications executed by the vehicle operating system in a restricted access mode to maintain the battery life.

8. The method according to any one of claims 3 to 7, wherein determining the operating state of the vehicle comprises determining an emergency state in which the safety of the vehicle is threatened, wherein the method further comprises presenting, by the instance of the vehicle operating system, a plurality of user interfaces across a plurality of displays communicatively coupled to the vehicle head unit, each of the plurality of user interfaces being associated with one or more of a plurality of user profiles, and Wherein entering the protected operating mode includes enabling all of the plurality of displays based on the emergency status to enable the plurality of user profiles to report the emergency status of the vehicle.

9. The method according to any one of claims 3 to 8, wherein determining the operating state of the vehicle comprises determining an emergency state in which the safety of the vehicle is threatened, and Wherein entering the protected operating mode includes disabling all audio playback of the vehicle head unit based on the emergency state.

10. The method according to any one of claims 3 to 9, wherein determining the operating state of the vehicle comprises determining an emergency state in which the safety of the vehicle is threatened, and Wherein entering the protected operating mode includes disabling all audio controls except audio controls related to the emergency state.

11. The method according to any one of claims 3 to 10, wherein determining the operating state of the vehicle comprises determining an emergency state in which the safety of the vehicle is threatened, and Wherein entering the protected operation mode comprises: automatically communicating a status of the operator of the vehicle when in the emergency state; as well as Audio control of the vehicle operating system is transferred to the one or more passengers based on the state of the operator of the vehicle.

12. The method of claim 11, wherein transferring the audio control of the vehicle operating system enables the one or more passengers to initiate an emergency telephone call to emergency services.

13. The method according to any one of claims 3 to 12, wherein the vehicle head unit is located in a center console of a front dashboard of the vehicle and includes a main display, through which the operator of the vehicle interfaces with the vehicle head unit, wherein determining the usage of the instance of the vehicle operating system includes determining whether the operator of the vehicle or the one or more passengers of the vehicle are using the main display of the vehicle head unit, and Wherein entering the protected operating mode includes disabling the protected operating mode in response to determining that the one or more occupants of the vehicle are using the primary display to allow the one or more occupants to interface with the vehicle operating system via the primary display.

14. The method according to any one of claims 1 to 13, wherein determining the operating context includes determining that the vehicle is entering a potentially unsafe operating context in which the operator of the vehicle requires additional attention, and Wherein entering the protected operating mode includes entering a protected operating mode in which the vehicle operating system reduces a volume of audio playback of the vehicle head unit in response to entering the potentially unsafe operating context.

15. The method according to any one of claims 1 to 14, wherein said instance of said vehicle operating system facilitates concurrent access by multiple user profiles, Wherein the method further comprises: authorizing, via the instance of the vehicle operating system, the plurality of user profiles to interface with the instance of the vehicle operating system; presenting, by the instance of the vehicle operating system, a plurality of user interfaces across a plurality of displays communicatively coupled to the vehicle head unit, each of the plurality of user interfaces being associated with one or more of the plurality of user profiles; as well as Interfacing with a plurality of users associated with the one or more of the plurality of user profiles via the plurality of user interfaces to enable the plurality of users to interface with the instance of the vehicle operating system to control functions associated with the vehicle head unit.

16. A computing device comprising: a memory configured to store an instance of a vehicle operating system; as well as one or more processors configured to execute the instance of the vehicle operating system, wherein the instance of the vehicle operating system is configured to: determining an operating context in which the vehicle is currently operating; and A protected operating mode is entered into the vehicle operating system based on the operating context in which one or more operating characteristics of the vehicle operating system are dynamically adapted to promote safety of an operator of the vehicle.

17. A computing device as described in claim 16, wherein the instance of the vehicle operating system is configured to enter a protected operating mode in which the vehicle operating system dynamically adjusts power settings of the vehicle to reduce power consumption of a battery powering the vehicle.

18. The computing device of any one of claims 16 and 17, wherein the instance of the vehicle operating system is configured to perform one or more of the following: determining usage of the instance of the vehicle operating system by one or more occupants of the vehicle; determining the presence of the one or more passengers in the vehicle; determining weather conditions in which the vehicle is currently operating; as well as An operating state of the vehicle is determined.

19. The computing device of claim 18, wherein said instance of said vehicle operating system facilitates concurrent access by multiple user profiles, wherein the instance of the vehicle operating system is further configured to present a plurality of user interfaces across a plurality of displays communicatively coupled to the computing device, each of the plurality of user interfaces being associated with one or more of the plurality of user profiles, and Wherein the instance of the vehicle operating system is configured to disable one or more of the multiple displays based on one or more of the usage of the instance of the vehicle operating system, the presence of the one or more occupants of the vehicle, the weather conditions, and the operating state of the vehicle.

20. A non-transitory computer-readable storage medium having stored thereon instructions that, when executed, cause one or more processors to: executing an instance of a vehicle operating system; determining, by the instance of the vehicle operating system, an operating context in which the vehicle is currently operating; and A protected operating mode is entered, by the instance of the vehicle operating system based on the operating context, in which one or more operating characteristics of the vehicle operating system are dynamically adapted to promote safety of an operator of the vehicle.

Images