Method and device for keeping wake-up state of in-vehicle infotainment system, vehicle, storage medium and product
By listening for wake-up events in the vehicle infotainment system and adjusting the wake-up duration according to priority, the problem of energy waste in the vehicle T-Box system is solved, and the system achieves efficient energy consumption management and stable operation.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-07
- Publication Date
- 2026-04-07
AI Technical Summary
In existing technologies, the low-power management system of in-vehicle T-Box often uses a simplified timing strategy to maintain the wake-up state of the vehicle's infotainment system, which results in the system being unable to sleep for a long time, causing energy waste.
By listening for wake-up events during the countdown of the wake-up hold duration in the vehicle system, identifying the wake-up source type, and dynamically adjusting the wake-up hold duration according to priority, the wake-up hold duration of high-priority events is ensured to cover the remaining duration of low-priority events, thus enabling the system to go into sleep mode in a timely manner.
It effectively reduces system energy consumption, ensures that critical services receive full service duration, avoids wake-up time redundancy caused by fixed duration reset or superposition, and improves system operation stability and battery life.
Smart Images
Figure CN121815383A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of vehicle network technology, and particularly relates to a method, device, vehicle, storage medium and product for maintaining the wake-up state of a vehicle's infotainment system. Background Technology
[0002] In the low-power management system of the in-vehicle T-Box (Telematics Box), maintaining the wake-up state of the vehicle's infotainment system is a core factor determining system power consumption and response performance. The system needs to handle various wake-up events from the vehicle network, user remote control, scheduled tasks, and cloud commands.
[0003] In existing technologies, common wake-up state preservation schemes often employ simplified timing strategies. This may lead to problems such as the system being unable to sleep for extended periods and wasting energy. Summary of the Invention
[0004] This application provides a method, apparatus, vehicle, storage medium, and product for maintaining the wake-up state of an in-vehicle infotainment system, enabling the system to enter hibernation mode in a timely manner, thereby saving vehicle energy consumption.
[0005] In a first aspect, embodiments of this application provide a method for maintaining the wake-up state of a vehicle infotainment system, the method comprising: During the countdown of the first wake-up duration in the vehicle system, listen for any newly triggered wake-up events; the first wake-up duration is the wake-up duration corresponding to the first wake-up source, and the first wake-up source is the wake-up source corresponding to the first wake-up event; Upon detecting a newly triggered second wake-up event, determine the type of the second wake-up source corresponding to the second wake-up event; The duration of the second wake-up hold for the vehicle system is determined based on the type of the second wake-up source. If the priority of the second wake-up source type is higher than that of the first wake-up source type, the wake-up hold duration of the vehicle system will be updated to the second wake-up hold duration.
[0006] In one feasible implementation, the method further includes: If the priority of the second wake-up source type is lower than or equal to the priority of the first wake-up source type, the wake-up hold duration of the vehicle system will be maintained as the remaining countdown duration of the first wake-up hold duration.
[0007] In one feasible implementation, before listening for a newly triggered wake-up event during the countdown of the first wake-up duration of the vehicle infotainment system, the method further includes: Listen for wake-up events; Upon detecting the first wake-up event, determine the type of the first wake-up source corresponding to the first wake-up event; The first wake-up duration of the vehicle system is determined based on the type of the first wake-up source. In response to the vehicle infotainment system being woken up, a countdown for the first wake-up duration of the vehicle infotainment system is initiated.
[0008] In one feasible implementation, the method further includes: If no new wake-up event is detected by the end of the countdown, the vehicle's infotainment system will enter sleep mode.
[0009] In one feasible implementation, before updating the wake-up hold duration of the vehicle system to the second wake-up hold duration when the priority of the second wake-up source type is higher than that of the first wake-up source type, the method further includes: Compare the duration of the second wake-up to the duration of the first wake-up; If the second wake-up duration is less than or equal to the first wake-up duration, the priority of the second wake-up source type is determined to be lower than or equal to the priority of the first wake-up source type. If the second wake-up duration is longer than the first wake-up duration, the priority of the second wake-up source type is determined to be higher than that of the first wake-up source type.
[0010] In one feasible implementation, the system listens for newly triggered wake-up events, including at least one of the following: Listen for any newly triggered vehicle CAN network wake-up events; Remote vehicle control events; Data upload event.
[0011] Secondly, embodiments of this application provide a wake-up state maintenance device for a vehicle infotainment system, the device comprising: The monitoring module is used to monitor for newly triggered wake-up events during the countdown of the first wake-up hold duration of the vehicle system; the first wake-up hold duration is the wake-up hold duration corresponding to the first wake-up source, and the first wake-up source is the wake-up source corresponding to the first wake-up event; The wake-up source type determination module is used to determine the second wake-up source type corresponding to the second wake-up event when a newly triggered second wake-up event is detected. The duration determination module is used to determine the second wake-up duration of the vehicle system based on the second wake-up source type. The duration update module is used to update the wake-up hold duration of the vehicle system to the second wake-up hold duration when the priority of the second wake-up source type is higher than that of the first wake-up source type.
[0012] Thirdly, embodiments of this application provide a vehicle, the vehicle including: a processor, and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement any of the vehicle system wake-up state maintenance methods.
[0013] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, wherein any one of the computer program instructions, when executed by a processor, implements a method for maintaining the wake-up state of a vehicle-mounted system.
[0014] Fifthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, implements any of the methods for maintaining the wake-up state of a vehicle system in the above embodiments.
[0015] The vehicle infotainment system wake-up state maintenance method, apparatus, vehicle, storage medium, and product of this application embodiment can promptly capture wake-up sources by listening for newly triggered wake-up events during the countdown period of the first wake-up maintenance duration of the vehicle infotainment system. This provides a data source for timely subsequent response. Upon detecting a newly triggered second wake-up event, the system determines the type of the second wake-up source corresponding to the second wake-up event. Based on the second wake-up source type, the system determines the second wake-up maintenance duration of the vehicle infotainment system. The system then determines the priority of the first and second wake-up source types. If the priority of the second wake-up source is higher than that of the first wake-up source, the wake-up maintenance duration of the vehicle infotainment system is updated to the second wake-up maintenance duration. Based on this, this embodiment configures independent countdowns for different wake-up events. When a new event arrives, the wake-up duration of the new event is updated to the original duration, rather than the two durations being superimposed. This allows the system to enter a sleep state promptly without affecting normal operation and functionality, significantly reducing energy consumption. Attached Figure Description
[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 This is a flowchart illustrating a scenario where a first wake-up event is detected, as provided in an embodiment of this application. Figure 2 This is a flowchart illustrating a method for maintaining the wake-up state of a vehicle infotainment system according to an embodiment of this application. Figure 3 This is a flowchart illustrating a wake-up hold time update process provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a wake-up state maintenance device for a vehicle infotainment system provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation
[0018] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.
[0019] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.
[0020] As the background technology indicates, in the low-power management system of an in-vehicle T-Box, the management of wake-up sources is a core element determining system power consumption and response performance. The system needs to handle various wake-up events from the vehicle network, user remote control, scheduled tasks, and cloud commands.
[0021] In existing technologies, common wake-up source management schemes often employ simplified timing strategies. Each time a wake-up source is received, a fixed amount of time is added to the existing wake-up hold time, keeping the system in a wake-up state for an extended period. This can lead to problems such as the system being unable to sleep for extended periods and wasting energy.
[0022] To address the problems in the prior art, embodiments of this application provide a method, apparatus, vehicle, storage medium, and product for maintaining the wake-up state of a vehicle's infotainment system.
[0023] In the embodiments of this application, during the countdown of the first wake-up duration in the vehicle system, the system listens for newly triggered wake-up events to capture wake-up sources in a timely manner, providing a data source for subsequent timely responses. Upon detecting a newly triggered second wake-up event, the type of the second wake-up source corresponding to the second wake-up event is determined. Based on the second wake-up source type, the second wake-up duration of the vehicle system is determined. Then, the priorities of the first and second wake-up source types are compared. If the priority of the second wake-up source is higher than that of the first wake-up source, the wake-up duration of the vehicle system is updated to the second wake-up duration. Based on this, this embodiment configures independent countdowns for different wake-up events. When a new event arrives, the wake-up duration of the new event is updated to the original duration, rather than the two durations being superimposed. This allows the system to enter a sleep state in a timely manner without affecting normal operation and functionality, significantly reducing energy consumption.
[0024] The wake-up state maintenance method of the vehicle system provided in the embodiments of this application will be introduced first.
[0025] Figure 1 This illustration shows a flowchart of a method for maintaining the wake-up state of a vehicle infotainment system according to an embodiment of this application. Figure 1 As shown, the method may include the following steps S110-S140: S110, during the countdown of the first wake-up duration of the vehicle system, listens for any newly triggered wake-up events; the first wake-up duration is the wake-up duration corresponding to the first wake-up source, and the first wake-up source is the wake-up source corresponding to the first wake-up event.
[0026] Specifically, monitoring for newly triggered wake-up events can include at least one of the following A1-A3: A1: Monitor for newly triggered vehicle CAN network wake-up events; A2: Remote vehicle control event; A3: Data upload event.
[0027] By clearly defining and integrating vehicle CAN network events, remote vehicle control commands, and data upload tasks as the core monitoring targets, comprehensive management of wake-up signals across all vehicle operation scenarios is achieved. This allows the system to seamlessly connect with changes in the vehicle's local status, user remote interaction needs, and autonomous system tasks, ensuring that all service requests from the vehicle, user, and system ends are captured and responded to in real time.
[0028] As an example, when the vehicle's infotainment system is awakened by a first wake-up event, such as remotely turning on the air conditioning, and enters the countdown for the first wake-up duration (e.g., at the 50th second of the 2-minute countdown), the system does not stop listening for potential new events. At this time, the hardware interrupt service routine and the software listening thread continue to work in parallel, scanning and capturing any new wake-up events that may be triggered from the vehicle's CAN bus, cellular network module, timers, and other interfaces. For example, at the 50th second of the 2-minute countdown for the aforementioned air conditioning control command, the system can still listen for a newly triggered "remote vehicle search" request or a signal from the vehicle collision sensor. This continuous listening mechanism ensures that the system, while maintaining its current wake-up state, can immediately detect new service requests or emergency events.
[0029] In this way, by introducing an independent countdown management and priority override mechanism based on wake-up source type, the power management challenge of in-vehicle systems in multi-event concurrent scenarios is effectively solved. While ensuring that various services can be responded to and processed in a timely manner, it intelligently prevents short-term, low-frequency events from unnecessarily prolonging the system wake-up time, thereby significantly reducing the system's dynamic power consumption. Simultaneously, through the collaborative design of the state machine and wake-up source, the synchronization and reliability of the MPU and MCU dual-core system during state switching are improved, avoiding system anomalies caused by state conflicts or management chaos, and enhancing the vehicle's operational stability and range in long-term parking and complex network environments.
[0030] S120, upon detecting a newly triggered second wake-up event, determines the type of the second wake-up source corresponding to the second wake-up event.
[0031] As an example, when the vehicle's infotainment system is in the first wake-up duration countdown, such as when the air conditioning is remotely turned on and the countdown is in its 2-minute phase, and it detects a newly triggered second wake-up event, such as receiving a "remote vehicle search" command from the cloud via the cellular network, the system immediately interrupts the current business flow to analyze the new event. The system extracts the feature code or event identifier from the command and matches it against an internally predefined wake-up source type mapping table. For example, based on a specific command field in the command, the system accurately maps it to a "remote vehicle control" wake-up source and identifies it as the second wake-up source type, for example, identified as "ACTIVE_REMOTE_CTRL". Through this process, the system can clearly distinguish and identify different event sources triggered within overlapping time periods, providing accurate type basis for subsequent priority comparison and update decisions regarding wake-up duration.
[0032] In this way, by quickly identifying and accurately classifying newly triggered events during overlapping wake-up events, intelligent judgment and dynamic management of the system state are achieved. The system can instantly distinguish the types of concurrent wake-up events, providing an accurate basis for subsequent duration decisions based on event priority, thereby avoiding state management conflicts or power waste caused by confusion of event types.
[0033] S130, determine the second wake-up duration of the vehicle system based on the second wake-up source type.
[0034] As an example, once the vehicle system determines the type of the second wake-up source corresponding to the second wake-up event, such as identifying the event as belonging to "Remote Vehicle Control" and then "Remotely Activate Sentry Mode," the system immediately queries the internally predefined "Wake-up Source Type - Hold Duration" mapping configuration table. Based on the configuration rules in the table, the system sets the second wake-up hold duration associated with events like "Remotely Activate Sentry Mode" to 5 minutes. This process is completed by looking up configuration data, ensuring that each wake-up source type corresponds to a clear and preset hold duration value, thus providing an accurate comparison benchmark for subsequent decisions on whether to update the system's current wake-up hold duration.
[0035] S140, if the priority of the second wake-up source type is higher than that of the first wake-up source type, the wake-up hold duration of the vehicle system is updated to the second wake-up hold duration.
[0036] As an example, when the system determines that the priority of the second wake-up source type is higher than that of the current first wake-up source type, for instance, when the countdown for the first wake-up event "remote vehicle search" has 2 minutes remaining, and the system detects and identifies the second wake-up event as "remotely activate sentry mode" with a duration of 5 minutes, since 5 minutes is longer than the current remaining 1 minute, meaning the second wake-up duration is longer than the remaining value of the first wake-up duration, the system determines that the second wake-up source type has a higher priority. The system then stops the current countdown and updates the vehicle system's wake-up duration to the second wake-up duration, i.e., 5 minutes. Simultaneously, it re-initializes and starts a new countdown from this new duration value. This process is achieved by updating the target value of the system's global timer, ensuring that high-priority tasks receive their required full service time and cover the remaining time of low-priority tasks.
[0037] Understandably, when the priority of the second wake-up source type is lower than that of the first wake-up source type, the original wake-up duration remains unchanged. Details will follow later. In this way, by updating the wake-up hold duration of the vehicle system to the second wake-up hold duration when the priority of the second wake-up source type is higher than that of the first wake-up source type, a duration-based priority comparison and dynamic overriding mechanism is implemented, directly realizing intelligent duration management of the system in multi-event concurrent scenarios. When a high-priority wake-up event occurs, the system can interrupt and overwrite the remaining countdown of the low-priority event in real time, and restart the countdown with the longer hold duration corresponding to the high-priority event, thereby ensuring that critical services obtain the complete and uninterrupted service window they need. This not only effectively prevents low-priority tasks from inappropriately shortening or interfering with the execution of high-priority tasks, but also avoids system wake-up time redundancy caused by fixed duration resets or simple superposition, significantly improving the reliability of important task completion, while optimizing the overall energy efficiency under multi-task scheduling.
[0038] In summary, by monitoring for newly triggered wake-up events during the countdown of the first wake-up duration in the vehicle infotainment system, the wake-up source is captured in a timely manner, providing a data source for subsequent timely responses. Upon detecting a newly triggered second wake-up event, the type of the second wake-up source corresponding to the second wake-up event is determined. Based on the second wake-up source type, the second wake-up duration of the vehicle infotainment system is determined. Then, the priorities of the first and second wake-up source types are compared. If the priority of the second wake-up source is higher than that of the first wake-up source, the wake-up duration of the vehicle infotainment system is updated to the second wake-up duration. Based on this, this embodiment configures independent countdowns for different wake-up events. When a new event arrives, the wake-up duration of the new event is updated to the original duration, rather than the two durations being superimposed. This allows the system to enter a sleep state in a timely manner without affecting normal operation and functionality, significantly reducing energy consumption.
[0039] Figure 2 This illustration shows a flowchart of a scenario where a first wake-up event is detected, according to an embodiment of this application. Figure 2 As shown, the method may include steps S210-S240: S210, vehicle infotainment system wake-up event monitoring.
[0040] S220, upon detecting the first wake-up event, determine the type of the first wake-up source corresponding to the first wake-up event.
[0041] As an example, when the vehicle's infotainment system is in sleep or low-power mode, it continuously monitors for wake-up signals from multiple interfaces. These signals may include activity on the vehicle's CAN network, such as opening doors or plugging / unplugging charging guns; remote vehicle control commands, such as user requests to locate the vehicle or turn on the air conditioning sent via a mobile app; and periodic reporting tasks, such as periodic heartbeat packets or data reports. When the system detects the first wake-up event, such as receiving a "remotely turn on the air conditioning" command from the cloud, the system will parse the wake-up source identifier corresponding to the command and determine the first wake-up source type corresponding to the event based on a preset wake-up source type mapping table. For example, a remote control type wake-up source identified as "ACTIVE_REMOTE_CTRL". In this way, the system can accurately identify the source and type of wake-up events, providing a basis for subsequent wake-up duration management.
[0042] S230, determine the first wake-up duration of the vehicle system based on the first wake-up source type; As an example, once the vehicle's infotainment system identifies the first wake-up source type corresponding to the first wake-up event, the system automatically queries and determines the corresponding first wake-up hold duration based on the preset mapping relationship between wake-up source types and hold durations. For instance, if the first wake-up source type is determined to be a "remote vehicle control event," and the wake-up event is a vehicle-finding command sent by the user through a mobile app, the system retrieves the preset hold duration of this type of event from the configuration table, which is 2 minutes, thus determining the first wake-up hold duration to be 2 minutes. This process is implemented through an internal mapping table or configuration logic, ensuring that each wake-up source type has its own independent hold duration, providing an accurate time reference for subsequent wake-up state management.
[0043] It should be noted that this application may also introduce the concept of a hold source. After the wake-up source and the hold source are matched, the hold source determines the hold duration.
[0044] Specifically, regarding wake-up sources and hold sources: A wake-up source is a signal source that can wake up the MPU from its sleep state.
[0045] It is represented using 2 bytes, with each wake-up source occupying 1 bit.
[0046] Here are some examples of wake-up sources: In the structure below, the value corresponding to each wake-up source represents which bit. For example, the byte representation of WAKEUP_CALL is 0x00, indicating that the 0th bit corresponds to the phone wake-up source. Similarly, the byte representation of WAKEUP_SIM is 0x01, indicating that the 1st bit corresponds to the ID card wake-up source; the byte representation of WAKEUP_4G is 0x02, indicating that the 2nd bit corresponds to the network connection wake-up source; the byte representation of WAKEUP_EXT is 0x03, indicating that the 3rd bit corresponds to the external device wake-up source; the byte representation of WAKEUP_REMOTE_CTRL is 0x04, indicating that the 4th bit corresponds to the remote control wake-up source; and the byte representation of WAKEUP_RTC_DATA_UPLOAD is 0x05, indicating that the 5th bit corresponds to the timed data reporting wake-up source. The byte representation of WAKEUP_NET_DISCONNECT is 0x07, indicating the 7th bit as the wake-up source when the network is disconnected; the byte representation of WAKEUP_CMD_CHARGE is 0x09, indicating the 9th bit as the wake-up source when charging; the byte representation of WAKEUP_CAR_RESERV is 0x0b, indicating the 11th bit as the wake-up source when the vehicle is reserved; and the byte representation of WAKEUP_POWER_ON is 0x0d, indicating the 13th bit as the wake-up source when the power is on.
[0047] The above flags allow you to set wake-up sources, clear wake-up sources, and read the status of all wake-up sources. Each wake-up source has a corresponding hold source; when we set a wake-up source, we indirectly set the corresponding hold source.
[0048] A hold source is a signal source that keeps the MPU from entering a sleep state while the MPU is not shutting down.
[0049] It is represented using 2 bytes, with each wake-up source occupying 1 bit.
[0050] The following hold sources can be set accordingly: ACTIVE_CALL (byte representation 0x00), ACTIVE_SIM (byte representation 0x01), ACTIVE_4G (byte representation 0x02), ACTIVE_EXT (byte representation 0x03), ACTIVE_REMOTE_CTRL (byte representation 0x04), ACTIVE_RTC_DATA_UPLOAD (byte representation 0x05), ACTIVE_NET_DISCONNECT (byte representation 0x07), ACTIVE_LOG_UP (byte representation 0x08), ACTIVE_CMD_CHARGE (byte representation 0x09), ACTIVE_CHARGING (byte representation 0x0a), ACTIVE_CAR_RESERV (byte representation 0x0b), ACTIVE_RECONNECT (byte representation 0x0c), ACTIVE_POWER_ON (byte representation 0x0d), and ACTIVE_FOTA_STA (byte representation 0x0f).
[0051] The above flags can be used to set a hold source, initialize the time counter of that hold source, clear the hold source, and read the status of all hold sources.
[0052] S140, in response to the vehicle infotainment system being woken up, starts the countdown for the first wake-up duration of the vehicle infotainment system.
[0053] As an example, once the vehicle's infotainment system is activated and enters operational mode in response to the first wake-up event, it immediately initializes and starts an independent countdown timer based on the predetermined first wake-up duration. For instance, if the first wake-up duration is 2 minutes, the system sets a decrementing counter in seconds, starting the countdown from 120 seconds. This countdown timer runs continuously in the background, tracking the remaining wake-up duration in real time, providing the system with an accurate time reference for determining when to initiate the hibernation process when no new events are triggered.
[0054] This embodiment listens for wake-up events when the vehicle infotainment system is in a low-power sleep state. Upon detecting a first wake-up event, it determines the first wake-up source type and, based on this type, determines the first wake-up duration for the system. In response to the system being woken up, a countdown for this first wake-up duration is initiated. This approach distinguishes and binds the source of various wake-up events that might otherwise be handled uniformly or responded to vaguely, enabling the system to accurately match the preset, reasonable working duration based on the event type. Furthermore, by instantly activating an independent countdown timer, it achieves predictable and quantifiable proactive management of the working duration of a single wake-up event. It should be noted that some keep-alive sources have a valid response time, which needs to be reset to zero after the time expires to prevent affecting sleep mode. To achieve this, keep-alive source management is required, which calls two functions: Wake-up source countdown function: This function is called once per second to decrement all hold source counters by one, thus implementing a hold source countdown.
[0055] Wake-up source clearing function: This function is called once per second to check the counter of each holding source. When the counter is zero, the corresponding holding source is cleared so that the corresponding holding source is cleared after the countdown ends.
[0056] In some embodiments, the method further includes: if the priority of the second wake-up source type is lower than or equal to the priority of the first wake-up source type, maintaining the wake-up duration of the vehicle system as the remaining countdown duration of the first wake-up duration.
[0057] As an example, when the vehicle's infotainment system is woken up due to remote vehicle location, with a corresponding hold time of 2 minutes, and is currently in the countdown period of the first wake-up hold time, with 1 minute remaining, the system detects a newly triggered periodic heartbeat data report, with a hold time of only 10 seconds. The system parses this event and determines that its second wake-up source type is "data reporting type," subsequently finding that its second wake-up hold time is 10 seconds. By comparison, since the second wake-up hold time of 10 seconds is much shorter than the remaining time of 1 minute of the first wake-up hold time, the system determines that the priority of the second wake-up source type is lower than that of the first wake-up source type. Therefore, the system does not reset or update the countdown, but continues to maintain the original countdown; the wake-up hold time of the vehicle's infotainment system remains the remaining countdown time of the first wake-up hold time, that is, it continues to decrease from approximately 1 minute.
[0058] In this way, by maintaining the wake-up duration of the vehicle system at the remaining countdown of the first wake-up duration when the priority of the second wake-up source type is lower than or equal to the priority of the first wake-up source type, the system effectively avoids unnecessary interference and interruption of long-running tasks caused by short-term, low-frequency tasks when it determines that the priority of a newly triggered wake-up event is not higher than the current event, by maintaining the original countdown instead of resetting or extending it. This mechanism ensures that high-priority services can enjoy a complete and continuous execution window, while significantly reducing the additional state switching overhead and dynamic power consumption accumulation caused by frequent countdown resets. Thus, it achieves refined control of system energy consumption and simultaneous improvement of task scheduling stability in complex multi-event scenarios.
[0059] In some embodiments, the method further includes: if no new wake-up event is detected when the countdown ends, controlling the vehicle system to enter a sleep state.
[0060] As an example, when the vehicle's infotainment system is woken up by a remote vehicle location command and enters a countdown, the system continuously listens for various interfaces during the 2-minute countdown. If the countdown ends without detecting any new wake-up events, the system initiates a hibernation process.
[0061] In this way, by entering sleep mode after confirming that no new wake-up event has been detected when the countdown ends, the system can automatically and smoothly switch to a low-power sleep state when the preset wake-up duration ends and no new event is generated, thus avoiding the waste of static power consumption caused by idling or delay after the countdown ends.
[0062] In some embodiments, such as Figure 3 As shown, when the priority of the second wake-up source type is higher than that of the first wake-up source type, before updating the wake-up hold duration of the vehicle system to the second wake-up hold duration, the method may further include steps S310-S330: S310, compare the second wake-up duration with the first wake-up duration.
[0063] S320, if the second wake-up duration is less than or equal to the first wake-up duration, determine that the priority of the second wake-up source type is lower than or equal to the priority of the first wake-up source type.
[0064] S330, if the second wake-up duration is longer than the first wake-up duration, determine that the priority of the second wake-up source type is higher than the priority of the first wake-up source type.
[0065] As an example, when the vehicle's infotainment system remotely activates the air conditioning due to a first wake-up event (with a 2-minute wake-up duration), and is in the countdown phase, if the system detects a newly triggered second wake-up event that remotely activates sentry mode, it first queries the configuration table to obtain the second wake-up duration of 5 minutes corresponding to the second wake-up source type. Then, the system executes priority judgment logic: comparing the 5-minute second wake-up duration with the original preset value of the 2-minute first wake-up duration. Since 5 minutes is greater than 2 minutes, the system determines that the second wake-up source type has a higher priority than the first wake-up source type.
[0066] Thus, by comparing the second wake-up hold duration with the first wake-up hold duration, the priority of the second wake-up source type is determined to be lower than or equal to the priority of the first wake-up source type if the second wake-up hold duration is less than or equal to the first wake-up hold duration. If the second wake-up hold duration is greater than the first wake-up hold duration, the priority of the second wake-up source type is determined to be higher than the priority of the first wake-up source type. This priority is based on the hold duration and aims to ensure that tasks can be executed completely. The hold duration is updated accordingly so that the system can hibernate promptly after completing tasks requiring a longer execution time.
[0067] Based on the above-described method for maintaining the wake-up state of a vehicle infotainment system, this application also provides a device for maintaining the wake-up state of a vehicle infotainment system.
[0068] Figure 4 This is a schematic diagram of a device structure provided in an embodiment of this application. Figure 4 As shown, the device may include: The monitoring module 410 is used to monitor whether a new wake-up event is triggered during the countdown of the first wake-up hold duration of the vehicle system; the first wake-up hold duration is the wake-up hold duration corresponding to the first wake-up source, and the first wake-up source is the wake-up source corresponding to the first wake-up event; The wake-up source type determination module 420 is used to determine the second wake-up source type corresponding to the second wake-up event when a newly triggered second wake-up event is detected. The duration determination module 430 is used to determine the second wake-up duration of the vehicle system based on the second wake-up source type; The duration update module 440 is used to update the wake-up hold duration of the vehicle system to the second wake-up hold duration when the priority of the second wake-up source type is higher than that of the first wake-up source type.
[0069] In this way, by executing the listening module 410, the wake-up source type determination module 420, the duration determination module 430, and the duration update module 440, the complete wake-up state maintenance process is decomposed into four core functional modules: listening, identification, decision-making, and execution. This achieves refined, automated, and highly reliable system power consumption management. Based on this, this embodiment configures independent countdowns for different wake-up events. When a new event arrives, the system wake-up state maintenance time is updated only if its required maintenance time is longer than the current remaining time, allowing the system to enter a sleep state in a timely manner and significantly reducing energy consumption.
[0070] In some embodiments, the device further includes: The priority module is used to maintain the wake-up duration of the vehicle system as the remaining countdown duration of the first wake-up duration when the priority of the second wake-up source type is lower than or equal to the priority of the first wake-up source type.
[0071] In some embodiments, the device further includes: The listening module is used to listen for wake-up events; The type determination module is used to determine the type of the first wake-up source corresponding to the first wake-up event when the first wake-up event is detected. The duration determination module is used to determine the first wake-up duration of the vehicle system based on the first wake-up source type. The countdown module is used to start a countdown for the first wake-up duration of the vehicle infotainment system in response to the system being woken up.
[0072] In some embodiments, the device further includes: The control module is used to control the vehicle system to enter a sleep state if no new wake-up event is detected when the countdown ends.
[0073] In some embodiments, the device further includes: The comparison module is used to compare the second wake-up duration with the first wake-up duration. The first determining module is used to determine, when the second wake-up duration is less than or equal to the first wake-up duration, that the priority of the second wake-up source type is lower than or equal to the priority of the first wake-up source type. The second determining module is used to determine that the priority of the second wake-up source type is higher than the priority of the first wake-up source type when the second wake-up hold duration is longer than the first wake-up hold duration.
[0074] In some embodiments, the listening module 410 may also be used to perform at least one of the following: Listen for any newly triggered vehicle CAN network wake-up events; Remote vehicle control events; Data upload event.
[0075] Based on the above embodiments, this application also provides a vehicle embodiment. Figure 5 A schematic diagram of the hardware structure of the vehicle provided in an embodiment of this application is shown.
[0076] The vehicle may include a processor 501 and a memory 502 storing computer program instructions.
[0077] Specifically, the processor 501 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.
[0078] Memory 502 may include mass storage for data or instructions. For example, and not limitingly, memory 502 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. In one instance, memory 502 may include removable or non-removable (or fixed) media, or memory 502 may be non-volatile solid-state storage. Memory 502 may be internal or external to the integrated gateway disaster recovery device.
[0079] Memory 502 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.
[0080] The processor 501 reads and executes computer program instructions stored in the memory 502 to achieve... Figure 1 The method for maintaining the wake-up state of the vehicle's infotainment system in the illustrated embodiment.
[0081] In one example, the vehicle may also include a communication interface 503 and a bus 504. Wherein, as... Figure 4 As shown, the processor 501, memory 502, and communication interface 503 are connected through bus 504 and complete communication with each other.
[0082] The communication interface 503 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.
[0083] Bus 504 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not as a limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 504 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.
[0084] Furthermore, in conjunction with the methods for maintaining the wake-up state of the vehicle's infotainment system in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the methods for maintaining the wake-up state of the vehicle's infotainment system in the above embodiments.
[0085] This application also provides a computer program product, including a computer program, which, when executed by a processor, implements any of the methods for maintaining the wake-up state of a vehicle system in the above embodiments.
[0086] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.
[0087] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.
[0088] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.
[0089] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.
[0090] It should be noted that the acquisition, storage, use, and processing of data in this application embodiment all comply with the relevant provisions of national laws and regulations.
[0091] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.
[0092] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.
Claims
1. A method for maintaining the wake-up state of a vehicle infotainment system, characterized in that, include: During the countdown of the first wake-up duration of the vehicle infotainment system, listen for any newly triggered wake-up events; The first wake-up duration is the wake-up duration corresponding to the first wake-up source, and the first wake-up source is the wake-up source corresponding to the first wake-up event; Upon detecting a newly triggered second wake-up event, determine the type of the second wake-up source corresponding to the second wake-up event; The second wake-up duration of the vehicle system is determined based on the second wake-up source type. If the priority of the second wake-up source type is higher than that of the first wake-up source type, the wake-up hold duration of the vehicle system is updated to the second wake-up hold duration.
2. The method for maintaining the wake-up state of a vehicle infotainment system according to claim 1, characterized in that, The method further includes: If the priority of the second wake-up source type is lower than or equal to the priority of the first wake-up source type, the wake-up hold duration of the vehicle system is maintained as the remaining countdown duration of the first wake-up hold duration.
3. The method for maintaining the wake-up state of a vehicle infotainment system according to claim 1, characterized in that, Before listening for newly triggered wake-up events during the countdown of the first wake-up duration of the vehicle infotainment system, the method further includes: Listen for wake-up events; Upon detecting the first wake-up event, determine the type of the first wake-up source corresponding to the first wake-up event; The first wake-up duration of the vehicle system is determined based on the first wake-up source type. In response to the vehicle infotainment system being woken up, a countdown for the first wake-up duration of the vehicle infotainment system is initiated.
4. The method for maintaining the wake-up state of a vehicle infotainment system according to claim 1, characterized in that, The method further includes: If no new wake-up event is detected by the end of the countdown, the vehicle's infotainment system will enter sleep mode.
5. The method for maintaining the wake-up state of a vehicle infotainment system according to any one of claims 1-4, characterized in that, Before updating the wake-up hold duration of the vehicle system to the second wake-up hold duration when the priority of the second wake-up source type is higher than the priority of the first wake-up source type, the method further includes: Compare the second wake-up duration with the first wake-up duration; If the second wake-up duration is less than or equal to the first wake-up duration, the priority of the second wake-up source type is determined to be lower than or equal to the priority of the first wake-up source type. If the second wake-up hold duration is longer than the first wake-up hold duration, the priority of the second wake-up source type is determined to be higher than the priority of the first wake-up source type.
6. The method for maintaining the wake-up state of a vehicle infotainment system according to any one of claims 1-5, characterized in that, The monitoring for newly triggered wake-up events includes at least one of the following: Listen for any newly triggered vehicle CAN network wake-up events; Remote vehicle control events; Data upload event.
7. A device for maintaining the wake-up state of a vehicle infotainment system, characterized in that, The device includes: The monitoring module is used to monitor whether a new wake-up event is triggered during the countdown of the first wake-up duration of the vehicle system; the first wake-up duration is the wake-up duration corresponding to the first wake-up source, and the first wake-up source is the wake-up source corresponding to the first wake-up event; The wake-up source type determination module is used to determine the second wake-up source type corresponding to the second wake-up event when a newly triggered second wake-up event is detected. The duration determination module is used to determine the second wake-up duration of the vehicle system based on the second wake-up source type. The duration update module is used to update the wake-up hold duration of the vehicle system to the second wake-up hold duration when the priority of the second wake-up source type is higher than the priority of the first wake-up source type.
8. A vehicle, characterized in that, The vehicle includes: a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the vehicle system wake-up state maintenance method as described in any one of claims 1-6.
9. A computer storage medium, characterized in that, The computer storage medium stores computer program instructions, which, when executed by the processor, implement the wake-up state maintenance method of the vehicle system as described in any one of claims 1-6.
10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the wake-up state maintenance method for the vehicle system as described in any one of claims 1-6.