Reducing user interface power consumption

Abstract

To reduce power consumption of a user interface.SOLUTION: Power consumption of a user interface in a vehicle is reduced. At least one occupant in the vehicle is determined to be consuming content. The content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content are determined. The state of the at least one occupant associated with stopping consumption of the content is determined. On the basis of the state of the at least one occupant determined to have stopped consuming the content, a device of the at least one occupant associated with stopping consumption of the content is set to a power-saving mode.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] This specification relates to reducing power consumption in user interfaces. [Background technology]

[0002] The presentation of audio and / or video content in vehicles has become commonplace in many travel experiences. For example, vehicle drivers often listen to audio content (e.g., music and / or spoken text) while driving, and passengers often watch videos in the vehicle until they reach their destination. Additional content includes web browsing, streaming content, etc. Mobile devices or other media playback devices, such as in-vehicle infotainment (IVI) systems (also simply referred to as infotainment systems), can be used to access the content.

[0003] Content can be displayed on the display for each occupant in the vehicle. The occupant can stop consuming the content. For example, the occupant may stop consuming the content if the occupant falls asleep. However, continuing to play the content regardless of the occupant's intention may increase the vehicle's power consumption. Summary of the Invention

[0004] In at least one embodiment, a method for reducing power consumption of a user interface includes determining that at least one occupant in a vehicle is consuming content; determining a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content; determining a status of the at least one occupant associated with no longer consuming the content; and setting a device of the at least one occupant associated with no longer consuming the content to a power saving mode based on the status of the at least one occupant determined to no longer be consuming the content.

[0005] In at least one embodiment, an apparatus for reducing power consumption of a user interface includes a memory storing computer-readable instructions and a processor coupled to the memory, wherein the processor is configured to execute the computer-readable instructions to perform operations to determine that at least one occupant in a vehicle is consuming content, determine a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content, determine a state of the at least one occupant associated with no longer consuming the content, and set a device of the at least one occupant associated with no longer consuming the content to a power-saving mode based on the state of the at least one occupant determined to no longer be consuming the content.

[0006] In at least one embodiment, a non-transitory computer-readable medium having computer-readable instructions stored thereon, the computer-readable instructions, when executed by a processor, cause the processor to perform the following operations: determine that at least one occupant in a vehicle is consuming content; determine a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content; determine a state of the at least one occupant associated with no longer consuming the content; and set a device of the at least one occupant associated with no longer consuming the content to a power-saving mode based on the state of the at least one occupant determined to no longer be consuming the content. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 illustrates a vehicle cockpit according to at least one embodiment. [Figure 2] FIG. 2 is an interior view of a vehicle according to at least one embodiment. [Figure 3] FIG. 3 is a system architecture according to at least one embodiment. [Figure 4] FIG. 4 is a flowchart of a method for reducing power consumption of a user interface according to at least one embodiment. [Figure 5] FIG. 5 is a high-level functional block diagram of a processor-based system according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Features, aspects, and advantages of certain exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which like reference numerals indicate like elements, and in which:

[0009] The following detailed description of exemplary embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of implementations. Furthermore, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Furthermore, in the flowcharts and operational descriptions set forth below, it is understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed concurrently (at least in part), and the order of one or more operations may be rearranged unless such modifications affect the scope of the invention.

[0010] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, software, or a combination of hardware and software. The actual specific control hardware or software code used to implement such systems and / or methods is not intended to limit the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It will be understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0011] Although particular combinations of features may be recited in the claims and / or disclosed in the specification, such combinations are not intended to limit the disclosure of possible implementations. Indeed, many of such features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may depend directly on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the group.

[0012] No element, act, or instruction used herein should be construed as critical or required unless expressly stated as such. Additionally, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Where only one item is intended, the term "one" or similar terms are used. Additionally, as used herein, terms such as "have," "having," "include," and "including" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise. Furthermore, phrases such as "at least one of A and B," "A and / or B," or "at least one of A or B" should be understood to include A only, B only, or both A and B.

[0013] Additionally, spatially relative terms such as "below," "lower," "bottom," "above," and "top" are used herein for ease of description to describe the relationship of one element or feature to another, as shown in the figures. Spatially relative terms are intended to encompass various orientations of the device during use or operation in addition to the orientation shown in the figures. If the device is otherwise oriented (rotated 90 degrees or at another orientation), the spatially relative descriptors used herein will be interpreted accordingly.

[0014] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0015] In at least one embodiment, a method for reducing power consumption of a user interface includes determining that at least one occupant in a vehicle is consuming content; determining a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content; determining a status of the at least one occupant associated with no longer consuming the content; and setting a device of the at least one occupant associated with no longer consuming the content to a power saving mode based on the status of the at least one occupant determined to no longer be consuming the content.

[0016] Embodiments described herein provide methods that provide one or more advantages, such as allowing a cockpit domain controller to determine that a vehicle occupant is not consuming content on a device and reduce power consumption of a device associated with the vehicle occupant that is determined not to be consuming content.

[0017] FIG. 1 illustrates a vehicle cockpit 100 according to at least one embodiment.

[0018] In FIG. 1 , the vehicle cockpit includes a steering wheel 110, an accelerator pedal 112, a brake pedal 114, an instrument panel 120, an infotainment system 130, and an air conditioning system 140. The air conditioning system 140 is sometimes referred to as a heating, ventilation, and air conditioning (HVAC) system. The steering wheel is part of a steering system operated by a driver to control the steering system and the direction of the vehicle. By operating the steering wheel 110, the driver directs the direction of the vehicle via a linkage system to the front wheels. The accelerator pedal 112 is used to control the supply of fuel and air to the engine by applying pressure. The accelerator pedal 112 is also referred to as a throttle or accelerator. The brake pedal 114 is pressed to apply the brakes, which slows and / or stops the vehicle.

[0019] The instrument panel 120 is part of the dashboard behind the steering wheel 110. The instrument panel 120 includes various instruments and lights that inform the driver of the vehicle's current status. For example, the instrument panel 120 often includes a traction control indicator, engine temperature, a tachometer, a fuel gauge, a speedometer, an odometer, turn signals, a gear indicator, and various warning lights. The tachometer displays the engine's crankshaft rotations in revolutions per minute (RPM). The speedometer indicates the vehicle's speed. The odometer displays the total miles traveled since the vehicle began driving. The fuel gauge displays the amount of fuel remaining in the vehicle. The temperature gauge displays the current engine temperature. Separately, designated lights may be provided to warn of engine temperature issues, such as an overheating engine. Turn signals represent flashing lights on both sides of the vehicle that inform other drivers of the direction the driver intends to turn. A gear indicator, or gear position indicator, indicates the currently engaged gear, such as Park, Neutral, or Drive. Warning lights communicate various status items on the vehicle. Vehicles come pre-installed with various features such as ESC and ABS, not to mention more standard components or elements. Warning lights illuminate briefly at start-up as the vehicle checks to ensure the system is safe and ready for operation. In some cases, a single warning light may remain illuminated, indicating a problem with the engine, headlights, temperature, etc., for example.

[0020] The vehicle includes an infotainment system 130. In at least one embodiment, the infotainment system 130 is an in-vehicle infotainment (IVI) system (also referred to simply as an infotainment system). However, the embodiments described herein are not limited to IVI systems. The infotainment system 130 includes one or more displays 132 for presenting content to vehicle occupants. For example, one or more displays 132 can be positioned to present content to each seat within the vehicle.

[0021] A cockpit domain controller 140 provides a collection of hardware and software within the vehicle that provides content, such as audio, video, and other content or information, to vehicle occupants. The cockpit domain controller 140 controls the presentation of content and stores the state of each occupant. The vehicle may also include a camera system 150. The camera system 150 is configured to provide facial recognition of occupants, such as the driver and other passengers. The cockpit domain controller 140 can use the camera system 150 to detect occupant states, such as when an occupant falls asleep and stops consuming content. The camera 150 can monitor for signs of eye fatigue (blinking), signs of distraction through facial and head movements, and the path the vehicle steers within a roadway lane (departure or driver steering). Other devices (e.g., wearable devices, sensor-equipped seats, smartphone sensors) can also monitor occupant drowsiness in the vehicle. Such devices can detect changes in pulse and breathing that typically occur before a person falls asleep.

[0022] The data communication interface 160 communicates with devices outside the vehicle to provide content to a user within the vehicle. Such devices include smartphones, tablets, televisions, laptop computers, servers, etc. The data communication interface 160 supports communication using a wireless connection according to any IEEE 802.11 Wi-Fi protocol, Bluetooth® protocol, Bluetooth Low Energy (BLE), or other short-range protocol operating according to a wireless technology standard for exchanging data using licensed or unlicensed bands, such as mobile cellular systems using the Citizens Broadband Radio Service (CBRS) band, the 2.4 GHz band, the 5 GHz band, the 6 GHz band, etc. Furthermore, the wireless connection can operate according to, but is not limited to, the RF4CE protocol, the ZigBee® protocol, the Z-Wave protocol, or the IEEE 802.15.4 protocol. Those skilled in the art will appreciate that the data communication interface 160 is not intended to be limited to any particular communication system or protocol.

[0023] FIG. 2 is an interior view of a vehicle 200 according to at least one embodiment.

[0024] 2, infotainment system 210 is shown centrally located on a vehicle dashboard 212. Infotainment system 210 may be an in-vehicle infotainment (IVI) system (also simply referred to as an infotainment system). Infotainment system 210 includes a cockpit domain controller 220 that outputs content, stores final states associated with content consumed by an occupant, and manages power to a display to turn it off or place it in a power-saving mode in response to detecting that the occupant has fallen asleep.

[0025] The infotainment system 210 also includes a central display 230 for presenting content and information regarding the presentation of that content. Additional displays 232, 234 may be provided separately for each rear seat passenger. Those skilled in the art will appreciate that other arrangements and numbers of displays 230, 232, 234 may also be provided.

[0026] In the embodiment shown in FIG. 2, four cameras 240, 242, 244, and 246 are provided to implement the camera system. The first camera 240 is aimed at the driver. The second camera 242 is aimed at the front seat passenger. The third camera 244 and the fourth camera 246 are aimed at each of the two rear seat passengers. However, one skilled in the art will appreciate that the number of cameras implemented by the camera system may be more or less than four. For example, a single front camera 240 may be implemented to monitor the driver and front seat passenger. Other arrangements are contemplated in the embodiments described herein.

[0027] Other devices (e.g., wearable devices, seats with sensors, smartphone sensors, etc.) can also be used to monitor the drowsiness of vehicle occupants. Such devices can detect changes in pulse and breathing that typically occur before a person falls asleep. In FIG. 2 , sensors 250, 252, 254, and 256 are provided in the seats to detect changes in the occupant's pulse and breathing that typically occur before a person falls asleep. A connection 260 from the cockpit domain controller 220 to a smartphone 262 is shown. Here, the smartphone 262 includes an application that monitors changes in the occupant's pulse and breathing to detect whether the occupant has fallen asleep. Those skilled in the art will appreciate that other types of sensors can be used to determine the presence or absence of an occupant, such as, for example, an occupant exiting the vehicle. The cockpit domain controller 220 determines whether the occupant is drowsy or asleep based on input from at least one of the cameras 240, 242, 244, and 246, the seat sensors 250, 252, 254, and 256, or the device 262.

[0028] When the cockpit domain controller 220 detects that an occupant is dozing, it determines the final state of the content being presented to the occupant. The final state of the content, e.g., video, music, etc., being consumed by the occupant is associated with the time at which the cockpit domain controller 220 determined that the occupant was dozing. In response, the cockpit domain controller 220 can set at least one display 230, 232, 234 associated with the determined dozing occupant to a power-saving mode, e.g., a power-off mode or a sleep mode. The cockpit domain controller 220 determines the final state of the content associated with the time at which one or more displays 230, 232, 234 were set to the power-saving mode, thereby reducing power consumption.

[0029] In response to the occupant's operation to restore one or more displays 230, 232, 234 from the power saving mode, content can be played back from the last state, and information about the last state can be sent to the occupant's one or more displays 230, 232, 234, so that the user can manually resume playing the content from the last state.

[0030] In response to detecting that the occupant has stopped consuming the content—for example, the occupant has fallen asleep or the occupant has turned off the display—the final state of the content displayed on one or more displays 230, 232, 234 is stored in data storage or other storage available to the occupant. The final state can be indicated by a content identifier (content ID) for the content itself, along with a location indicator, such as a timestamp, scroll position, state function, etc. The content ID can be the name of a video, a link to the content, a web address, the name of a game, or a product code. When the cockpit domain controller 220 detects that the occupant has fallen asleep, the final state, identification information identifying the occupant, and the content ID are stored, for example, in data storage. The final state can be restored by the cockpit domain controller 220 in response to the user no longer falling asleep or via direct input from the user requesting restoration of the final state of the content.

[0031] FIG. 3 is a system architecture 300 according to at least one embodiment.

[0032] In FIG. 3 , infotainment system 302 includes a cockpit domain controller 310, a camera system / other sensors 320, one or more displays 330, and a data communication interface 340. Cockpit domain controller 310 determines whether at least one occupant in the vehicle is consuming content. Cockpit domain controller 310 provides content output, stores a final state 354 of content consumed for each occupant in the vehicle, and manages data for restoring the final state 354. One or more displays 330 are used to present content and present the identity of each occupant using a user interface 332. For example, an additional display 370 can be provided for each rear seat passenger. Content can include content that can be displayed on a screen, such as YouTube®, web browsing activity, video games, movies, music data, etc.

[0033] The camera system 320 can assist in facial recognition of occupants in each seat of the vehicle by providing the cockpit domain controller 310 with an image of at least one occupant of the vehicle. The cockpit domain controller 310 includes image analysis to determine whether an occupant in the image is actually dozing off. For example, the image analysis 312 can be performed using machine learning. Other sensors 320 (e.g., wearable devices, seats with sensors, smartphone sensors, etc.) can also be used to monitor the drowsiness of vehicle occupants. Such other sensors 320 can detect changes in pulse and breathing that typically occur before a person falls asleep. For example, an occupant analysis 314 is performed by the cockpit domain controller 310 to monitor the drowsiness of vehicle occupants. Such occupant analysis 314 can be performed using machine learning.

[0034] The data communication interface 340 communicates with user devices. The data communication interface 340 enables the cockpit domain controller 310 to communicate with user devices using a wireless network. For example, the data communication interface 340 can communicate with a smartphone 360, a television 362, a content server 364, and a computing device 366 (e.g., a personal computer, a tablet, a laptop, etc.). The data communication interface 340 can use a wireless network. The cockpit domain controller 310 can also communicate with user devices using a wireless network. Examples of wireless networks include Wi-Fi, Internet hotspots, Bluetooth, Zigbee, Z-Wave, infrared (IR) radio, ultra-wideband (UWB), wireless gigabit (or WiGig), etc. The data communication interface 340 supports communication using a wireless connection according to any IEEE 802.11 Wi-Fi protocol, Bluetooth protocol, Bluetooth Low Energy (BLE), or other short-range protocol operating in accordance with a wireless technology standard for exchanging data using licensed or unlicensed bands, such as mobile cellular systems using the Citizens Broadband Radio Service (CBRS) band, the 2.4 GHz band, the 5 GHz band, the 6 GHz band, etc. Additionally, the data communication interface 340 supports wireless connections according to, but not limited to, the RF4CE protocol, the ZigBee protocol, the Z-Wave protocol, or the IEEE 802.15.4 protocol. Those skilled in the art will appreciate that the data communication interface 340 is not meant to be limited to any particular communication system or protocol.

[0035] The cockpit domain controller 310 can store information in a data storage 350, including identification information 352 associated with the vehicle occupant, a content identifier (ID), and a final state 354, indicated by, for example, a location indicator. According to at least one embodiment, the information can be stored locally in the data storage 350, in the cloud, in another storage system, or any other storage configuration.

[0036] The cockpit domain controller 310 identifies the user's state or level of attention as no longer paying attention to or consuming content. For example, the user is detected as falling asleep in the vehicle. Examples of detecting drowsiness include using image recognition via a camera and obtaining information from at least one occupant wearable device, such as a smartwatch, fitness tracker, etc. However, one skilled in the art will appreciate that the cockpit domain controller 310 can obtain information from other devices (e.g., wearable devices, seats with sensors, smartphone sensors, etc.) that can also monitor the drowsiness of a vehicle occupant. Such devices can detect changes in pulse and breathing that typically occur before a person falls asleep.

[0037] In response to the cockpit domain controller 310 identifying that the user is no longer consuming content, devices such as the content server, one or more displays 330, etc., are placed into a power-saving mode, such as a power-off mode or a sleep mode. The cockpit domain controller 310 may also detect that the user has turned off a display. Rather than immediately placing the one or more displays 330 into a power-saving mode, a notification 316 may be provided to the one or more displays 330 associated with the occupant to give the occupant an opportunity to prevent the one or more displays 330 from being turned off.

[0038] One or more displays 330 may be placed in a power-saving mode in response to not receiving input from a user within a predetermined time. For example, one or more displays 330 may not be placed in a power-saving mode in response to receiving input within a predetermined time. Also, content may not be stopped in response to the user not sleeping.

[0039] The final state 354 of the content displayed on one or more displays 330 is stored in data storage 350 or other storage available to the occupant in response to detecting that the occupant is no longer consuming the content, for example, because the occupant has fallen asleep or the occupant has turned off the display. The final state 354 may be indicated by a content identifier (content ID) for the content itself, as well as a location indicator, such as a timestamp, scroll position, state function, etc. The content ID may be the name of a video, a link to the content, a web address, the name of a game, or a product code.

[0040] When dozing is detected by the cockpit domain controller 310, the final state 354, the occupant identification information 352, and the content ID are stored, for example, in the data storage 350. The final state 354, the occupant identification information 352, and the content ID can be restored by the cockpit domain controller 310 in response to the user ceasing to doze off or via direct input from the user requesting restoration of the content's final state 354.

[0041] According to at least one embodiment, in a power saving mode, in response to detecting a drowsy occupant, one or more displays 330 are turned off, but audio content continues to be provided, so that other occupants, including the driver, can continue to enjoy the audio content.

[0042] The cockpit domain controller 310 determines whether at least one occupant is ready to resume consuming the content. In response to an occupant action causing one or more displays 330 to resume from a power-saving mode, the content can be played back from the final state 354. Information regarding the final state 354 can also be sent to the occupant's one or more displays 330, allowing the user to manually resume playing the content from the final state 354. Thus, the content can be continued or discontinued based on the user's selected preferences.

[0043] When the cockpit domain controller 310 detects that the occupant is dozing or has fallen asleep, the cockpit domain controller 310 can present a message on one or more displays 330 requesting permission to set the one or more displays 330 to a power-saving mode. The one or more displays 330 are set to the power-saving mode in response to no occupant operation being provided within a predetermined time, but are not set to the power-saving mode in response to occupant operation being provided within the predetermined time. Thus, the cockpit domain controller 310 can prevent content from being stopped when the occupant is not asleep.

[0044] FIG. 4 is a flowchart 400 of a method for reducing power consumption of a user interface, according to at least one embodiment.

[0045] In Figure 4, the process begins (S402) and determines that at least one occupant in the vehicle is consuming content (S410). Referring to Figure 3, the infotainment system 302 includes a cockpit domain controller 310, a camera system / other sensors 320, one or more displays 330, and a data communication interface 340. The cockpit domain controller 310 determines whether at least one occupant in the vehicle is consuming content. The cockpit domain controller 310 provides content output, stores a final state 354 of the content being consumed for each occupant in the vehicle, and manages data for restoring the final state 354.

[0046] A content identifier (ID) associated with the content and an identifier associated with at least one occupant consuming the content are determined (S414). Referring to Figure 3, the cockpit domain controller 310 can store information in data storage 350 including identification information 352 associated with the vehicle occupants, the content identifier (ID), and a final state 354 indicated, for example, by a location indicator.

[0047] A state of at least one occupant associated with no longer consuming the content is determined (S418). Referring to FIG. 3, the cockpit domain controller 310 identifies the user's state or level of attention as no longer paying attention to or no longer consuming the content. For example, the user is detected as falling asleep in the vehicle. Examples of detecting drowsiness include using image recognition via a camera and obtaining information from at least one wearable device of the occupant, such as a smartwatch or fitness tracker. However, one skilled in the art will appreciate that the cockpit domain controller 310 can obtain information from other devices (e.g., wearable devices, seats with sensors, smartphone sensors, etc.) that can also monitor the drowsiness of the vehicle occupant. Such devices can detect changes in pulse and breathing that typically occur before a person falls asleep.

[0048] Based on the determination that at least one passenger has stopped consuming content, at least one passenger's device is set to a power-saving mode (S422). Referring to FIG. 3 , in response to the cockpit domain controller 310 identifying that a user has stopped consuming content, devices such as the content server, one or more displays 330, and the like are set to a power-saving mode, such as a power-off mode or a sleep mode. In response to detecting that a passenger has stopped consuming content, for example, that the passenger has fallen asleep or turned off a display, a final state 354 of the content displayed on the one or more displays 330 is stored in the data storage 350 or other storage available to the passenger. The final state 354 can be indicated by a content identifier (content ID) for the content itself, along with a location indicator such as a timestamp, scroll position, or state function. The content ID can be the name of a video, a link to the content, a web address, a game name, or a product code. The cockpit domain controller 310 can also detect that a user has turned off a display. Rather than immediately placing one or more displays 330 in a power-saving mode, a notification 316 may be provided to one or more displays 330 associated with the occupant to give the occupant an opportunity to prevent the one or more displays 330 from turning off. One or more displays 330 may be placed in a power-saving mode in response to not receiving input from a user within a predetermined time. For example, one or more displays 330 may not be placed in a power-saving mode in response to receiving input within a predetermined time. Content may also not be stopped in response to the user not sleeping.

[0049] A final state associated with the content is determined (S426) when the device is set to a power-saving mode. Referring to FIG. 3 , the final state 354 of the content displayed on one or more displays 330 is stored in data storage 350 or other storage available to the occupant in response to detecting that the occupant is no longer consuming the content, e.g., the occupant has fallen asleep, the occupant has turned off the display, etc. The final state 354 may be indicated by a content identifier (content ID) for the content itself, as well as a location indicator, e.g., a timestamp, scroll position, state function, etc. The content ID may be the name of a video, a link to the content, a web address, the name of a game, or a product code.

[0050] A content identifier ID associated with the content, an identifier associated with at least one occupant consuming the content, and a final state associated with the content at the time at which at least one occupant's device was set to a power-saving mode are saved (S430). Referring to Figure 3, when dozing is detected by the cockpit domain controller 310, the final state 354, the occupant identification information 352, and the content ID are stored, for example, in data storage 350. The final state 354 can be restored by the cockpit domain controller 310 in response to the user not dozing or via direct input from the user requesting restoration of the content's final state 354.

[0051] Determine that at least one occupant is ready to resume consuming the content (S434). Referring to Figure 3, the cockpit domain controller 310 determines whether at least one occupant is ready to resume consuming the content.

[0052] A content identifier (ID) associated with the content, an identifier associated with at least one occupant who is ready to resume consuming the content, and a final state associated with the content are retrieved (S438). Referring to Figure 3, the final state 354, occupant identification information 352, and content ID can be restored by the cockpit domain controller 310 in response to the user ceasing to doze off or via direct input from the user requesting restoration of the content's final state 354.

[0053] The content provided to the at least one occupant is resumed from the time associated with the final state (S442) based on a determination that the at least one occupant is ready to resume consuming the content. Referring to FIG. 3, the cockpit domain controller 310 determines whether the at least one occupant is ready to resume consuming the content. In response to the occupant's action waking one or more displays 330 from a power-saving mode, the content can be played from the final state 354. The final state 354 can be indicated by a position indicator, such as a timestamp, scroll position, or state function, along with a content identifier (content ID) for the content itself. The content ID can be the name of a video, a link to the content, a web address, the name of a game, or a product code.

[0054] The process then ends (S440).

[0055] At least one embodiment of a method for reducing power consumption of a user interface includes determining that at least one occupant in a vehicle is consuming content; determining a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content; determining a status of the at least one occupant associated with no longer consuming the content; and setting a device of the at least one occupant associated with no longer consuming the content to a power saving mode based on the status of the at least one occupant determined to no longer be consuming the content.

[0056] FIG. 5 is a high-level functional block diagram of a processor-based system 500 according to at least one embodiment.

[0057] In at least one embodiment, processing circuitry 500 manages content displayed within a vehicle. Processing circuitry 500 uses processor 502 to implement a method for reducing power consumption of a user interface. Processing circuitry 500 also includes a non-transitory computer-readable storage medium 504 used to implement the method for reducing power consumption of a user interface. Non-transitory computer-readable storage medium 504 is encoded with, or stores, instructions 506, or computer program code, that are executed by processor 502, among other things. The instructions 506 cause processor 502 to perform operations for reducing power consumption of the user interface. Execution of instructions 506 by processor 502 represents (at least in part) an application that implements at least a portion of the methods described herein (hereinafter, processes and / or methods) in accordance with one or more embodiments.

[0058] The processor 502 is electrically coupled to a non-transitory computer-readable storage medium 504 via a bus 508. The processor 502 is electrically coupled by the bus 508 to an input / output (I / O) interface 510. A network interface 512 is also electrically connected to the processor 502 via the bus 508. The network interface 512 is connected to a network 514 such that the processor 502 and the non-transitory computer-readable storage medium 504 are connected to external elements via the network 514.

[0059] The processor 502 is configured to execute instructions 506 encoded on a non-transitory computer-readable storage medium 504 such that the processing circuit 500 is operable to perform at least portions of processes and / or methods. In one or more embodiments, the processor 502 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application specific integrated circuit (ASIC), and / or other suitable processing unit.

[0060] Processing circuit 500 includes an I / O interface 510. I / O interface 510 is coupled to external circuitry. In one or more embodiments, I / O interface 510 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor direction keys for communicating information and commands to processor 502.

[0061] Processing circuit 500 also includes a network interface 512 coupled to processor 502. Network interface 512 enables processing circuit 500 to communicate with a network 514 to which one or more other computer systems are connected. Network interface 512 includes a wireless network interface such as Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA), or a wired network interface such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers (IEEE) 864.

[0062] The processing circuit 500 is configured to receive information via an I / O interface 510. The information received via the I / O interface 510 includes one or more of instructions, data, design rules, libraries of cells, and / or other parameters for processing by the processor 502. The information is transferred to the processor 502 via a bus 508. The processing circuit 500 is configured to receive information related to a user interface (UI) via the I / O interface 510. The information is stored in the non-transitory computer-readable storage medium 504 as a UI 520.

[0063] In one or more embodiments, instructions 506 (in compressed or uncompressed form) are stored on one or more non-transitory computer-readable storage media 504. The instructions 506 may be used to program a computer, processor, or other electronic device to perform the processes or methods described herein. The one or more non-transitory computer-readable storage media 504 include one or more of an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, etc.

[0064] For example, the non-transitory computer-readable storage medium 504 may include, but is not limited to, a hard drive, a floppy disk, an optical disk, a read-only memory (ROM), a random-access memory (RAM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a magnetic or optical card, a solid-state memory device, or any other type of physical medium suitable for storing electronic instructions. In one or more embodiments using an optical disk, the one or more non-transitory computer-readable storage media 504 may include a compact disk read-only memory (CD-ROM), a compact disk read / write (CD-R / W), and / or a digital moving image disk (DVD).

[0065] In one or more embodiments, the non-transitory computer-readable storage medium 504 stores instructions 506 configured to cause the processor 502 to implement at least a portion of a process and / or method for reducing power consumption of a user interface. In one or more embodiments, the non-transitory computer-readable storage medium 504 also stores information, such as algorithms, that facilitate implementation of at least a portion of the process and / or method for reducing power consumption of a user interface.

[0066] Thus, in at least one embodiment, the processor 502 executes instructions 506 stored on one or more non-transitory computer-readable storage media 504 to implement a method for reducing power consumption of a user interface. The processor 502 implements an infotainment system that includes a cockpit domain controller 530. The cockpit domain controller 530 manages power to displays to set power-saving modes, output content, store final states associated with content consumed by an occupant, and turn displays off or set them to power-saving modes in response to detecting that an occupant has fallen asleep. The processor 502 is configured to use the cockpit domain controller 530 to set one or more displays 580 to power-saving modes based on inputs from a camera system 550, other sensors 552, etc.

[0067] The processor 502 is coupled to the cockpit domain controller 530 and implements a data communication interface 540 for communicating with devices inside or outside the vehicle. For example, the data communication interface 540 can use a wireless network. The processor uses the cockpit domain controller 530 to obtain identification information 560 to identify at least one occupant who is viewing some content. The content is associated with the occupant through the identification information 560. The identification information 560 includes information that identifies the occupant, such as a facial image, a device ID, etc.

[0068] A camera system 550 including one or more cameras may be coupled to the cockpit domain controller 530 to monitor vehicle occupants for drowsiness.

[0069] The processor 502 performs facial recognition using image analysis 532 of the cockpit domain controller 530 to identify occupants in each area of ​​the vehicle based on images from the camera system 550 and determine whether the occupants are drowsy, falling asleep, or have fallen asleep. Image analysis 532, e.g., machine learning, can be used to analyze images of the occupants to determine each occupant's identity 560. The processor 502 also uses other sensors 552. For example, the processor 502 uses occupant analysis 534 of the cockpit domain controller 530 to process data from the other sensors 552 to detect whether the occupant is drowsy.

[0070] When processor 502 detects that the occupant is drowsy, falling asleep, or has fallen asleep, it determines a final state 570 of the content associated with identification information 560. Final state 570 includes a location indicator 572 of the content, e.g., video, music, etc., that the occupant is consuming, where location indicator 572 is associated with the time at which the occupant was determined to be drowsy and no longer consuming the content. Final state 570 is indicated by location indicator 572, e.g., timestamp, scroll position, state function, etc., along with a content identifier (content ID 574) for the content itself. Processor 502 uses content ID 574 to determine the name of the video, a link to the content, a web address, the name of a game, a product code, etc.

[0071] The processor 502 causes the cockpit domain controller 530 to store information including the content ID 574 and the final state 570, for example as indicated by the location indicator 572. However, according to at least one embodiment, the information can be stored in the data storage 516 or in the cloud, another storage system, or other storage configuration.

[0072] The processor 502 then determines, using the cockpit domain controller 530, whether the occupant is ready to resume consuming the content. The cockpit domain controller 530 identifies that the occupant is ready to resume consuming the content according to the identification information 560, and then retrieves a content ID 574 associated with the re-boarding occupant and a final state 570 of the content. The processor 502 uses the final state 570 to cause the cockpit domain controller 530 to resume the content from the point when one or more displays 580 were set to a power-saving mode.

[0073] Final state 570 includes a location indicator 572, which may be a timestamp associated with the content when the occupant exited the vehicle, an approximate final location, a calculated estimate of final state 570, etc. For example, in response to location indicator 572 indicating that final state 570 is at the 10 minute position, processor 502 may cause cockpit domain controller 530 to resume playback from, for example, 9 minutes 50 seconds. Information regarding final state 570 of the content may be transmitted to the occupant. For example, the information may be transmitted via data communications interface 540 to a user device such as a smartphone, a personal computer or laptop, a television, etc.

[0074] The processor 502 may present the content using one or more displays 580 and present the identity of each occupant using a user interface 582 including identification information 584. Information regarding the final state 570 of the content may be presented on one or more displays 580. The information regarding the final state 570 may be sent to the occupant via a notification 536 sent to the occupant via at least one of a text message, an email, a push notification to an application, a voicemail message, etc. The user interface 582 presents a notification 592 on one or more of the displays 580. The occupant may use the user interface 582 to retrieve the final state 586 of the content in the vehicle.

[0075] The processor 502 may present information about the content and, optionally, the final status 586, including a location indicator 588, on one or more displays 580 in the vehicle, such as an infotainment system. When the cockpit domain controller 530 determines that the occupant is ready to resume consuming the content, the processor 502 causes the cockpit domain controller 530 to access the data storage 516 to determine existing entries that may be associated with the occupant determined to be ready to resume consuming the content.

[0076] In some situations, cockpit domain controller 530 may not identify any entries associated with the crew member. In this situation, cockpit domain controller 530 can query the crew member for information such as content ID 590 and location via user interface 582. In other situations, processor 502 causes cockpit domain controller 530 to identify multiple entries associated with the crew member. Again, cockpit domain controller 530 can communicate with the crew member via the crew member's device or one or more displays 580 to determine which entry the crew member wants to use.

[0077] The processor 502 can also cause the cockpit domain controller 530 to use a default setting that uses the most recent entry. In response to an occupant exiting the vehicle, the cockpit domain controller 530 can also delete the old entry and store the current entry, thereby preventing multiple entries from being used. In response to the cockpit domain controller 530 determining that the occupant is ready to resume consuming content, the processor 502 reads the entry from the data storage 516 and then deletes the entry. In this way, an occupant determined to be ready to resume consuming content can resume consuming content from their last location.

[0078] The embodiments described herein provide a method that provides one or more advantages. For example, a cockpit domain controller may determine that a vehicle occupant is not consuming content on a device and reduce power consumption of devices associated with the determined vehicle occupant. Separate instances of such programs may run on or be distributed across any number of separate computer systems. Thus, although particular steps have been described as being performed by particular devices, software programs, processes, or entities, this is not necessarily the case. Those skilled in the art will recognize various alternative implementations.

[0079] Furthermore, those skilled in the art will readily appreciate that the above-described techniques can be utilized in a variety of devices, environments, and contexts. Although the embodiments have been described in language specific to structural features or methodological acts, the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claims.

Claims

1. 1. A processor-implemented method for reducing power consumption of a user interface, comprising: determining that at least one occupant in a vehicle is consuming content; determining a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content; determining a state of the at least one occupant associated with no longer consuming the content; setting a device of the at least one occupant associated with no longer consuming the content to a power-saving mode based on a state of the at least one occupant determined to no longer be consuming the content; Including, The method, wherein the step of setting the device of the at least one occupant to the power saving mode includes providing a message to the at least one occupant requesting permission to set the device to the power saving mode.

2. 2. The method of claim 1, wherein the step of determining a state of the at least one occupant associated with no longer consuming the content includes at least one of performing image recognition of an image of the at least one occupant or obtaining information from at least one wearable device of the at least one occupant.

3. 3. The method of claim 1 or 2, wherein the step of setting the device to the power saving mode includes reducing power to the device of the at least one occupant or stopping the provision of content to the device of the at least one occupant.

4. The step of setting the device of the at least one occupant to the power saving mode comprises:

3. The method of claim 1 or 2, comprising setting the device of the at least one occupant to the power saving mode in response to not receiving input from the at least one occupant within a predetermined time.

5. determining a final state associated with the content at the time the device was placed in the power save mode; determining whether the at least one occupant is ready to resume consuming the content; Retrieving the content identifier (ID) associated with the content, the identifier associated with the at least one occupant ready to resume consumption of the content, and the final status associated with the content; resuming the supply of the content to the at least one occupant from a time associated with the final state based on the determination that the at least one occupant is ready to resume consuming the content; The method of claim 1 or 2, further comprising:

6. 6. The method of claim 5, wherein the step of resuming the supply of the content includes determining at least one of a timestamp, a scroll position, or a state function associated with the content at the time the device of the at least one occupant determined to no longer be consuming the content was set to the power saving mode.

7. 1. An apparatus for reducing power consumption of a user interface, comprising: a memory storing computer readable instructions; a processor, coupled to the memory, operable to execute the computer-readable instructions, determining that at least one occupant in the vehicle is consuming content; determining a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content; determining a state of the at least one occupant associated with no longer consuming the content; a processor configured to perform operations based on a state of the at least one occupant determined to no longer be consuming the content, to place a device of the at least one occupant associated with no longer consuming the content into a power-saving mode; Equipped with the processor is further configured to place the device in the power saving mode by reducing power to the device of the at least one occupant or stopping the provision of content to the device of the at least one occupant.

8. 8. The apparatus of claim 7, wherein the processor is further configured to determine a state of the at least one occupant associated with no longer consuming the content by at least one of performing image recognition of an image of the at least one occupant or obtaining information from at least one wearable device of the at least one occupant.

9. 9. The apparatus of claim 7 or 8, wherein the processor is further configured to place the device in the power saving mode by reducing power to the device of the at least one occupant or stopping the supply of content to the device of the at least one occupant.

10. 9. The apparatus of claim 7 or 8, wherein the processor is further configured to set the device of the at least one occupant to the power saving mode by setting the device of the at least one occupant to the power saving mode in response to not receiving input from the at least one occupant within a predetermined time.

11. The processor: determining a final state associated with the content at the time the device was placed into the power save mode; determining whether the at least one occupant is ready to resume consuming the content; Retrieving the content identifier (ID) associated with the content, the identifier associated with the at least one occupant who is ready to resume consuming the content, and the final status associated with the content; The device of claim 7 or 8, further configured to resume supplying the content to the at least one occupant from a time associated with the final state based on the determination that the at least one occupant is ready to resume consuming the content.

12. 12. The device of claim 11, wherein the processor is further configured to resume supply of the content by determining at least one of a timestamp, a scroll position, or a state function associated with the content at the time the device of the at least one occupant determined to no longer consume the content was set to the power saving mode.

13. determining that at least one occupant in the vehicle is consuming content; determining a content identifier (ID) associated with the content and an identifier associated with the at least one occupant consuming the content; determining a state of the at least one occupant associated with no longer consuming the content; a computer program product that causes a processor to perform an operation of setting a device of the at least one occupant associated with no longer consuming the content to a power saving mode based on a state of the at least one occupant that is determined to no longer consume the content, the computer program product comprising: The computer program product, wherein setting the device of the at least one occupant to the power saving mode includes providing a message to the at least one occupant requesting permission to set the device to the power saving mode.

14. 14. The computer program product of claim 13, wherein determining a state of at least one occupant associated with no longer consuming the content includes at least one of performing image recognition on an image of the at least one occupant or obtaining information from at least one wearable device of the at least one occupant.

15. 15. The computer program product of claim 13 or 14, wherein setting the device to the power saving mode comprises reducing power to the device of the at least one occupant or stopping the provision of content to the device of the at least one occupant.

16. 15. The computer program product of claim 13 or 14, wherein setting the device of the at least one occupant to the power saving mode comprises setting the device of the at least one occupant to the power saving mode in response to not receiving input from the at least one occupant within a predetermined time period.

17. determining a final state associated with the content at the time the device was placed into the power save mode; determining whether the at least one occupant is ready to resume consuming the content; Retrieving the content identifier (ID) associated with the content, the identifier associated with the at least one occupant who is ready to resume consuming the content, and the final status associated with the content; 15. The computer program of claim 13, further causing the processor to perform an operation of resuming the supply of the content to the at least one occupant from a time associated with the final state based on the determination that the at least one occupant is ready to resume consuming the content.

18. 20. The computer program product of claim 17, wherein resuming the supply of the content includes determining at least one of a timestamp, a scroll position, or a state function associated with the content at the time the device of the at least one occupant determined to no longer be consuming the content was set to the power saving mode.

Images