Vehicle power state management method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of smart vehicles, and provides a vehicle power state management method and device, electronic equipment and a storage medium. The method comprises the following steps of: receiving a vehicle message from a vehicle gateway through a vehicle-mounted microcontroller, analyzing the vehicle message to obtain vehicle event information, and respectively sending the vehicle information to a first vehicle system and a second vehicle system which are realized by different operating systems, the power state is determined based on the vehicle event information through the power state management modules respectively arranged in the first vehicle system and the second vehicle system, power state management can be synchronously carried out in multiple different vehicle-mounted systems, the universality and flexibility of power state management are improved, and the management efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of smart vehicle technology, and in particular to a vehicle power status management method, device, electronic device and storage medium. Background Art

[0002] As the degree of automobile electrification increases, people's requirements for automobile intelligence are getting higher and higher, and the concept of automobile intelligent cockpit has emerged. Generally speaking, the intelligent cockpit includes the central control system, full LCD instrument, in-vehicle infotainment system, HUD (Head Up Display), rear seat entertainment system, car networking system, etc. Each system interacts through the in-vehicle network system and is powered by the car's power system.

[0003] In response to different power supply states of the car, the vehicle system needs to control its own functions according to these states to control the current consumption and prevent the car battery from running out of power. Among the related technologies, only the Android system provides a native power management module, which determines and distributes the power state through a flag bit.

[0004] When it is necessary to synchronously manage the power status of multiple different systems in a vehicle, how to determine and distribute the power status is a technical problem that needs to be solved. Summary of the invention

[0005] In view of this, embodiments of the present application provide a vehicle power status management method, device, electronic device and storage medium to solve the problem of how to manage the power status in multiple different systems in a vehicle in the prior art.

[0006] According to a first aspect of an embodiment of the present application, a vehicle power state management method is provided, the method being executed by a vehicle-mounted microcontroller, comprising: Receive vehicle messages from the vehicle gateway; Determining corresponding vehicle event information based on the vehicle message; Sending the vehicle event information to a power state processing module of the first vehicle system so that the power state processing module of the first vehicle system determines the power state according to the vehicle event information; and Sending the vehicle event information to the power state processing module of the second vehicle system so that the power state management service module of the second vehicle system determines the power state according to the vehicle event information; Among them, the first vehicle system and the second vehicle system are two different systems divided in the same chip using virtualization technology, and the first vehicle system and the second vehicle system are implemented using different operating systems.

[0007] According to a second aspect of an embodiment of the present application, a vehicle power state management device is provided, comprising: an onboard microcontroller configured to receive a vehicle message from a vehicle gateway and determine corresponding vehicle event information based on the vehicle message; A power state processing module of the first vehicle system is configured to receive vehicle event information and determine a power state based on the vehicle event information; A power state processing module of the second vehicle system is configured to receive vehicle event information and determine a power state based on the vehicle event information; Among them, the first vehicle system and the second vehicle system are two different systems divided in the same chip using virtualization technology, and the first vehicle system and the second vehicle system are implemented using different operating systems.

[0008] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0009] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0010] Compared with the prior art, the embodiments of the present application have the following beneficial effects: the embodiments of the present application receive vehicle messages from a vehicle gateway through a vehicle-mounted microcontroller, parse the vehicle messages to obtain vehicle event information, and send the vehicle information to a first vehicle system and a second vehicle system implemented by different operating systems, respectively; the power status is determined based on the vehicle event information by power status management modules respectively provided in the first vehicle system and the second vehicle system, thereby enabling synchronous power status management in multiple different vehicle-mounted systems, improving the versatility and flexibility of power status management, and improving management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 It is a schematic diagram of the Android native power management architecture.

[0013] Figure 2 It is a flow chart of a vehicle power status management method provided in an embodiment of the present application.

[0014] Figure 3It is a flowchart of a method for a power status processing module of a first vehicle system to determine a power status according to vehicle event information provided in an embodiment of the present application.

[0015] Figure 4 It is a flowchart of a method for a power status processing module of a second vehicle system to determine a power status according to vehicle event information provided in an embodiment of the present application.

[0016] Figure 5 It is a flow chart of another vehicle power status management method provided in an embodiment of the present application.

[0017] Figure 6 It is a flow chart of another vehicle power status management method provided in an embodiment of the present application.

[0018] Figure 7 It is a flowchart of a method for a power status management module to determine a power status according to vehicle event information provided in an embodiment of the present application.

[0019] Figure 8 It is a schematic diagram of the system architecture for implementing the vehicle power management method provided in the embodiment of the present application.

[0020] Fig. 9 It is a schematic diagram of a vehicle power status management device provided in an embodiment of the present application.

[0021] Fig.10 It is a schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0023] A vehicle power status management method and device according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0024] As mentioned above, the various systems in the smart cockpit interact with each other through the vehicle network system and are powered by the car's power system. Normally, the car key has four gears, corresponding to the four power supply states of the car, namely OFF, ACC (Accessory), ON and START. The OFF gear disconnects the car's power supply (at this time, some electronic devices are still powered for controlling the car, such as locking the door), the ACC gear does not start the car but can power some electrical appliances in the car, including the full LCD instrument and the in-vehicle infotainment system, etc. The ON gear powers all electrical appliances in the car, and the START gear is a self-resetting switch, which automatically returns to the ON gear after starting the car.

[0025] For different power supply states of the car, the vehicle system needs to control its own functions according to these states to control the current consumption and prevent the car battery from running out of power. Usually, the car will convert these power supply states into software-defined working modes, including sleep, standby, ACC OFF / ON, IGN (Ignition) OFF / ON, etc., and notify the vehicle system through a professional MCU (Microcontroller Unit) so that the vehicle system can control its own behavior in different working modes.

[0026] On the other hand, as a software system, it usually includes shutdown, sleep, startup and normal operation states, which can be called the power state of the vehicle system to distinguish the working modes mentioned above. In addition to the above working modes and power states, the vehicle system also needs to process other information, such as input voltage, operating temperature, power saving mode, etc., so that the system can operate in the expected way.

[0027] In order to process the above-mentioned various types of power-related information in a unified way, the information involved in power management can be divided into the following three categories, each of which has its own separate processing method: 1) System power status: The system power on and off status is used as the system power status. The power status can be used to control the power on and off process of the system application layer; 2) System working mode: The system operation mode customized according to the status of the vehicle signal can be called the working mode, such as the standby mode, remote control mode and normal working mode. Different power states can correspond to different working modes; 3) Vehicle signal: Vehicle and system related information other than system on / off and working mode can be collectively referred to as vehicle signals. For example, the input voltage status of the vehicle computer and various power saving status in the system power saving strategy can be processed as vehicle signals to distinguish the working mode. In addition, ACC ON / OFF, IGN ON / OFF and hardware temperature information can also be processed as vehicle signals as needed. Different power states can correspond to different vehicle signals.

[0028] Among the related technologies, only the Android system provides a native power management architecture. Figure 1 This is a schematic diagram of the Android native power management architecture. Figure 1 As shown in the figure, the Android native power management architecture includes user space, framework space, system space and kernel space. The user space includes the vehicle power management module, the framework space includes the vehicle service module (CarService), and the vehicle service module may include the vehicle power management service module (CarPowerManagerService). The user's operation in the vehicle power management module can be transmitted to the vehicle power management service module in the framework space.

[0029] The system space may include a vehicle power policy monitoring interface (CarPowerPlicyDaemon). The vehicle power policy monitoring interface interacts with the hardware abstraction layer (VHAL). The hardware abstraction layer may also be connected to the vehicle power management service module and the vehicle processor.

[0030] The kernel space may include a suspend interface and a resume interface, which may be called by the vehicle power management service and connected to the vehicle power policy monitoring interface. The resume interface may also be connected to the vehicle processor.

[0031] However, with the continuous advancement of vehicle intelligence, a vehicle may include multiple different systems, and the multiple different systems are implemented using different operating systems. For example, the IVI (In-Vehicle Infotainment, the second vehicle system) in the vehicle is usually implemented using the Android operating system, but the first vehicle system in the vehicle is often implemented using the QNX (Fast Unix) or Linux operating system. For vehicle systems implemented using operating systems other than the Android operating system, the relevant technology does not provide a solution for managing the power status.

[0032] In view of this, an embodiment of the present application provides a vehicle power status management method, which receives vehicle messages from a vehicle gateway through a vehicle-mounted microcontroller, parses the vehicle messages to obtain vehicle event information, and sends the vehicle information to a first vehicle system and a second vehicle system implemented by different operating systems, respectively. The power status is determined based on the vehicle event information by power status management modules respectively provided in the first vehicle system and the second vehicle system, thereby enabling synchronous power status management in multiple different vehicle-mounted systems, thereby improving the versatility and flexibility of power status management and improving management efficiency.

[0033] Figure 2 FIG. 1 is a flow chart of a vehicle power status management method provided by an embodiment of the present application. Figure 2 As shown, the method comprises the following steps: In step S201 , a vehicle message is received from a vehicle gateway.

[0034] In step S202 , corresponding vehicle event information is determined based on the vehicle message.

[0035] In step S203 , the vehicle event information is sent to the power state processing module of the first vehicle system, so that the power state processing module of the first vehicle system determines the power state according to the vehicle event information.

[0036] In step S204, the vehicle event information is sent to the power state processing module of the second vehicle system, so that the power state management service module of the second vehicle system determines the power state according to the vehicle event information.

[0037] Among them, the first vehicle system and the second vehicle system are two different systems divided in the same chip using virtualization technology, and the first vehicle system and the second vehicle system are implemented using different operating systems.

[0038] In certain embodiments of the present application, the method can be executed by an on-board MCU. The on-board MCU can be a microcontroller of the cockpit domain controller of the vehicle electronic system, which is responsible for the tasks of uplink and downlink data transparent transmission processing of vehicle signals, power management tasks, cockpit domain controller peripherals, and vehicle SoC (System on Chip) main chip power supply tasks. That is, the on-board MCU can realize the control and management of various functions such as the engine, transmission system, body electronic system, safety system, and infotainment system.

[0039] In some embodiments of the present application, the vehicle-mounted MCU can receive vehicle messages from the vehicle gateway. Moreover, the vehicle-mounted MCU can also determine the corresponding vehicle event information based on the vehicle message. In one example, the vehicle-mounted MCU can receive a CAN (Controller Area Network) signal from the vehicle gateway, and then parse the CAN signal to extract the vehicle event information therein. Among them, the vehicle event information can be, for example, information about the vehicle executing a specific action, or information about the device enabling the vehicle to process a specific mode.

[0040] In some implementations, the vehicle-mounted MCU may send the vehicle event information to a power status processing module of the first vehicle system, so that the power status processing module of the first vehicle system determines the power status according to the vehicle event information.

[0041] That is to say, a power status management module can be set in the first vehicle system of the vehicle, and the power status management module can determine the power status based on the vehicle event information transmitted by the on-board MCU, so that the power status can be determined efficiently and conveniently in the first vehicle system.

[0042] In other embodiments, the vehicle-mounted MCU may send the vehicle event information to a power status processing module of the second vehicle system, so that the power status processing module of the second vehicle system determines the power status according to the vehicle event information.

[0043] That is to say, a power status management module can also be set in the second vehicle system of the vehicle. The power status management module can determine the power status based on the vehicle event information transmitted by the on-board MCU, so that the power status can be determined efficiently and conveniently in the second vehicle system.

[0044] The specific method for determining the power status is described in detail below and will not be repeated here.

[0045] The first vehicle system and the second vehicle system may be two different systems obtained by partitioning the same SoC chip using virtualization technology, and the first vehicle system and the second vehicle system may be implemented using different operating systems. For example, the first vehicle system and the second vehicle system may be two different systems obtained by partitioning the same SoC chip using a Hypervisor, the first vehicle system may be an instrument system implemented using a QNX or Linux operating system, and the second vehicle system may be a cockpit entertainment system implemented using an Android system.

[0046] According to the technical solution provided in the embodiment of the present application, a vehicle message is received from a vehicle gateway through a vehicle-mounted microcontroller, the vehicle message is parsed to obtain vehicle event information, and the vehicle information is sent to a first vehicle system and a second vehicle system implemented by different operating systems, respectively. The power status is determined based on the vehicle event information through power status management modules respectively provided in the first vehicle system and the second vehicle system, thereby enabling simultaneous power status management in multiple different vehicle-mounted systems, thereby improving the versatility and flexibility of power status management and enhancing management efficiency.

[0047] It is understandable that when the vehicle also includes other systems and the other systems also need to perform power status management, a similar method can be used to set up a power status management module in the system to receive vehicle event information transmitted by the on-board MCU, and determine the power status based on the vehicle event information, thereby realizing the transplantation of the power status management solution and making the power status management method highly versatile.

[0048] In some embodiments of the present application, the first vehicle system may further include a vehicle service module, and the power state processing module of the first vehicle system may include a first power service module and a first power state management module. On the other hand, the power state management service module of the second vehicle system may include a second power service module, a second power state management module and a distributed bus.

[0049] Figure 3 FIG. 1 is a flow chart of a method for determining a power state according to vehicle event information by a power state processing module of a first vehicle system provided in an embodiment of the present application. Figure 3 As shown, the method comprises the following steps: In step S301 , the first power service module receives vehicle event information from the vehicle service module.

[0050] Among them, vehicle event information is transmitted from the on-board microcontroller to the vehicle service module.

[0051] In step S302, the first power service module inputs the vehicle event information into the first power state management module.

[0052] In step S303, the first power state management module determines the power state according to the vehicle event information.

[0053] In some embodiments of the present application, a vehicle service module may be provided in the first vehicle system to receive vehicle event information transmitted by the on-board MCU and distribute the vehicle event information.

[0054] In the first vehicle system, the vehicle service module can directly transmit the vehicle event information to the first power service module, and then the first power service module transmits the vehicle event information to the first power state management module. The first power state management module can determine the power state according to the vehicle event information.

[0055] In one example, the first power state module can determine the power state according to a preset mapping relationship table. For example, a preset mapping relationship table can be stored in the first power state module, and the preset mapping relationship table stores the correspondence between different vehicle events and different power states. By searching for the power state corresponding to the received vehicle event information, the current power state of the vehicle can be determined.

[0056] In another example, the first power state module may also use a state machine to determine the power state. The specific implementation method of using the state machine to determine the power state is described in detail below and will not be repeated here.

[0057] Figure 4 FIG. 1 is a flow chart of a method for determining a power state according to vehicle event information by a power state processing module of a second vehicle system provided in an embodiment of the present application. Figure 4 As shown, the method comprises the following steps: In step S401 , the distributed bus receives vehicle event information from a vehicle service module.

[0058] Among them, vehicle event information is transmitted from the on-board microcontroller to the vehicle service module.

[0059] In step S402 , the second power service module receives vehicle event information from the distributed bus.

[0060] In step S403, the second power service module inputs the vehicle event information into the second power state management module.

[0061] In step S404, the second power state management module determines the power state according to the vehicle event information.

[0062] In some embodiments of the present application, the second vehicle system can receive vehicle event information from the vehicle service module in the first vehicle system via a distributed bus. Since the first vehicle system can be a system implemented using a QNX or Linux operating system, and the second vehicle system can be a system implemented using an Android operating system, the former starts faster, so configuring the vehicle service module on the first vehicle system side can better meet the signal requirements when the first vehicle system starts.

[0063] The second power service module in the second vehicle system can receive vehicle event information from the distributed bus and input the vehicle event information into the second power state management module. The second power state management module can determine the power state according to the vehicle event information.

[0064] Likewise, the second power state management module may determine the power state using a preset mapping table, a state machine or other methods, which are not limited herein.

[0065] It can be understood that if the first vehicle system is a system implemented using the Android operating system, and the second vehicle system is a system implemented using the QNX or Linux operating system, the vehicle service module can be configured on the second vehicle system side, and a distributed bus can be set in the first vehicle system to receive vehicle event information from the vehicle service module and forward the vehicle event information to the first power service module of the first vehicle system.

[0066] In some embodiments of the present application, Figure 4 The method for the power state processing module of the second vehicle system in the illustrated embodiment to determine the power state according to the vehicle event information may further include the following steps: In step S405, in response to determining that the second vehicle system does not include a power status processing module, or the power status processing module of the second vehicle system cannot determine the power status, the distributed bus sends vehicle event information to the hardware description module of the second vehicle system.

[0067] In step S406 , the hardware description module sends the vehicle event information to the vehicle power management service module, so that the vehicle power management service module determines the power state based on the vehicle event information.

[0068] As mentioned above, the second vehicle system may be a cockpit entertainment system implemented using the Android operating system, so in addition to setting up a distributed bus and a power state management module, the second vehicle system may also be compatible with the Android native power management architecture. That is, a hardware description module and a vehicle power management service module may be set up in the second vehicle system.

[0069] If the power state management module is not configured in the second vehicle system, or the power state management module in the second vehicle system cannot determine the power state, the distributed center can send the vehicle event information to the hardware description module, and then the hardware description module sends the vehicle event information to the vehicle power management service module to determine the power state using the native Android architecture. In this way, the versatility of the power state management method can be further improved.

[0070] Figure 5is a flow chart of another vehicle power state management method provided by an embodiment of the present application. Figure 5 Steps S501 to S503 in the embodiment shown are Figure 2 Steps S201 to S203 in the illustrated embodiment are substantially the same, and Figure 5 Step S506 in the illustrated embodiment is Figure 2 Step S204 in the illustrated embodiment is substantially the same and will not be described in detail herein. Figure 5 As shown, the method also includes the following steps: In step S504, the power state is sent to the function application module of the first vehicle system, so that the function application module of the first vehicle system determines the working mode of the target vehicle instrument function based on the power state.

[0071] In step S505, the power status is sent to the dashboard to display the power status.

[0072] The target vehicle instrument function is a vehicle instrument function that operates in different operating modes under different vehicle power states.

[0073] In some embodiments of the present application, after determining the power state, the power state management service module in the first vehicle system may send the power state to the function application module of the first vehicle system, so that the function application module of the first vehicle system determines the working mode of the target vehicle instrument function based on the power state. The function application module may include a function service module and an application module.

[0074] In one example, if the first vehicle system is an instrument system, the power status management service module in the first vehicle system can send the power status directly to the ICU (Instrument Cluster Unit) application on the user application side, so that the ICU application can determine its own working mode or signal status based on the power status.

[0075] In another example, the power status management service module in the first vehicle system can also send the power status to the functional service modules of various applications in the first vehicle system, so that the functional service modules of various applications can determine their own working modes or signal status based on the power status.

[0076] On the other hand, after determining the power status, the power status management service module in the first vehicle system may also send the power status to the instrument panel to display the power status.

[0077] Figure 6 is a flow chart of another vehicle power state management method provided in an embodiment of the present application. Figure 6Steps S601 to S604 in the embodiment shown are Figure 2 Steps S201 to S204 in the illustrated embodiment are substantially the same and will not be described in detail herein. Figure 6 As shown, the method also includes the following steps: In step S605, the power status is sent to the function application module of the second vehicle system, so that the function application module of the second vehicle system determines the working mode of the target cockpit entertainment function based on the power status.

[0078] Among them, the target cockpit entertainment function is a cockpit entertainment function that works in different working modes under different vehicle power states.

[0079] In some embodiments of the present application, after determining the power state, the power state management service module in the second vehicle system may send the power state to the function application module of the second vehicle system, so that the function application module of the second vehicle system determines the working mode of the target cockpit entertainment function based on the power state. The function application module may include a function service module and an application module.

[0080] In one example, if the second vehicle system is a cockpit entertainment system, the power status management service module in the second vehicle system can send the power status directly to the IVI application on the user application side, so that the IVI application determines its own working mode or signal status based on the power status.

[0081] In another example, the power status management service module in the second vehicle system can also send the power status to the functional service modules of various applications in the second vehicle system, so that the functional service modules of various applications can determine their own working modes or signal status based on the power status.

[0082] Figure 7 FIG. 1 is a flow chart of a method for determining a power state according to vehicle event information by a power state management module provided in an embodiment of the present application. Figure 7 As shown, the method comprises the following steps: In step S701, a state machine is configured in a power state management module.

[0083] The state machine includes at least one state, and each state corresponds to a power state.

[0084] In step S702, in response to the power state management module receiving the vehicle event information, a target state that satisfies the condition corresponding to the vehicle event information is determined.

[0085] In step S703, it is determined that the target state is a power state.

[0086] As mentioned above, in some embodiments of the present application, the power state module can determine the power state using a state machine. When the power state is determined using a state machine, a state machine can be set in the power state module, and the state machine includes at least one state, and each state corresponds to a power state. Different power states have different state transition conditions, and when the power state module receives a target condition that satisfies the target state, the state machine will transition to the target state.

[0087] Therefore, the power state management module can receive vehicle event information and determine whether the vehicle event information meets the target condition, which can be any condition in the state machine that triggers a state transition. If the power state management module determines that the vehicle event information it receives meets the target condition, the state machine transitions to the target state, which is the state corresponding to the target condition. The power state management module can determine that the target state is the power state.

[0088] Figure 8 Schematic diagram of the system architecture for implementing the vehicle power management method provided in the embodiment of the present application. Figure 8 As shown, the system architecture includes a first vehicle system implemented by a QNX operating system and a second vehicle system implemented by an Android operating system.

[0089] The QNX operating system includes a custom vehicle service module, a first power service module, a first power state management module, a functional service module, an ICU application module, and a display module. The Android operating system includes a distributed bus (FDbus), a second power service module, a second power state management module, a hardware abstraction layer (VHAL), a vehicle power management service module, a functional service module, and an IVI application module.

[0090] The vehicle service module receives vehicle event information from the on-board MCU, and sends the vehicle event information to the customized first power service module. The first power service module then sends the vehicle event information to the customized first power state management module, so that the first power state management module determines the power state based on the vehicle event information. The first power state management module can send the determined power state directly to the display module for display, or send the power state to the functional service module or ICU application, so that it can determine the working mode or signal state of the functional service or application based on the power state.

[0091] On the other hand, the vehicle service module can also send vehicle event information to the FDbus in the Android operating system.

[0092] On the one hand, FDbus can send the vehicle event information to a customized second power service module. The second power service module then sends the vehicle event information to a customized second power state management module, so that the second power state management module determines the power state based on the vehicle event information.

[0093] On the other hand, FDbus can also send the vehicle event information to Android's native VHAL, and then VHAL sends the vehicle event information to the vehicle power management service module, so that the vehicle power management service module determines the power status based on the vehicle event information.

[0094] The second power state management module and the vehicle power management service module may both send the determined power state to the functional service module or the IVI application, so that the functional service or the IVI application can determine the working mode or signal state of the functional service or the application based on the power state.

[0095] That is to say, the custom vehicle service module can process the CAN signal transmitted by the MCU and transparently transmit the processing result to the next node. The entry and exit SoC ends of all CAN signals of the cockpit entertainment system are custom vehicle service modules. The MCU can also transparently transmit the downlink signal of the whole vehicle to the SoC, and transmit the uplink signal of the SoC to the whole vehicle controller.

[0096] The first power service module is the core power management service on the QNX operating system side, which is mainly used to pass the power status to the first power status management module. At the same time, it supports providing other power status or status passed by other MCUs to QNX side applications or services to meet the application scenario requirements on the instrument side.

[0097] The first power state management module is a power state management service. Its main function is to manage the main power states such as OFF, ACC, ON and START, and transmit them uniformly to the QNX upper-layer application scenario.

[0098] The display module can be a backlight management module for the instrument screen, which is used to manage the on / off functions of the instrument screen and the central control screen according to different power states. The functional service module in the QNX operating system is mainly an upper-layer application on the instrument side.

[0099] FDbus is an inter-domain communication service, which is used to receive all CAN signals (including power management status signals) transparently transmitted from the QNX side. The signal source is the MCU, but it must be transparently transmitted to the Android side through the vehicle service module, because the same signal and status are also needed by the QNX side system and Android, so the signal transmission chain MCU—>QNX (vehicle service module)—>Android (FDbus) is designed here. The design of this link makes the signal link unidirectional and closed-loop, and the link is also short. The QNX system starts faster than Android, and the vehicle service module design on the QNX side can also well meet the signal needs when the QNX system starts.

[0100] VHAL is the Vehicle HAL layer service on the native Android side, which is used to transparently transmit signals to the native vehicle power management service module for use by Android upper-layer applications and services.

[0101] The second power service module and the second power state management module are both custom modules, which are used to parse and process the signals transmitted by FDBUS into corresponding signal state identifiers so that Android upper-layer applications can correspond one by one according to specific needs.

[0102] That is to say, the uplink on the QNX system side is: MCU->Vehicle Service Module->First Power Service Module->First Power State Management Module->QNX Upper-layer Applications and Services. The downlink on the QNX system side is:QNX Upper-layer Applications and Services->First Power State Management Module->First Power Service Module->Vehicle Service Module->MCU.

[0103] The uplink on the Android side is: MCU->Vehicle Service Module->Fdbus->Second Power Service Module->Second Power State Management Module->IVI Upper-layer Applications and Services. The downlink on the Android side is:VI Upper-layer Applications and Services->Second Power State Management Module->Second Power Service Module->Fdbus->Vehicle Service Module->MCU.

[0104] For example, when the user turns on the ignition key or clicks the one-button start button, the vehicle gateway (Gateway) will transmit the vehicle power status to the MCU through the CAN bus. The MCU will transmit the power on signal to the vehicle service module.

[0105] On the one hand, the vehicle service module can pass this signal to the first power service module on the QNX side, and the first power service module service will then pass this signal to the first power status management module for overall management, and then report this signal status to the QNX side application and service to know that the entire vehicle is Power On at this time, and can respond to some business scenarios in the Power On power state, such as playing welcome audio, etc.

[0106] On the other hand, the vehicle service module can also pass this signal to the Fdbus on the Android side, and Fdbus then passes this power status signal to the second power service module. The second power service module then passes this signal to the second power status management module for overall management, and then reports the corresponding power status signal to the Android side applications and services to meet the Android side's needs for power management status monitoring.

[0107] By adopting the technical solution of the embodiment of the present application and designing a customized vehicle power state management process, the power management requirements of the IVI Android cockpit entertainment system side and the QNX instrument system side can be covered, so that the vehicle power state management method has high reusability, portability and versatility.

[0108] At the same time, when processing power state changes, the MCU notifies the QNX-side power management through CAN communication or Ethernet communication, and then communicates with the IVI Android-side power management logic through inter-domain communication to make judgments and apply power strategies. This can provide a faster response time to power state changes and improve the flexibility of processing logic, thereby meeting the power management state in fast-response automotive application scenarios, increasing user experience and vehicle safety.

[0109] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0110] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0111] Fig. 9 Schematic diagram of a vehicle power status management device provided by an embodiment of the present application. Fig. 9 As shown, the device comprises: The vehicle-mounted microcontroller 901 is configured to receive a vehicle message from a vehicle gateway and determine corresponding vehicle event information based on the vehicle message.

[0112] The power state processing module 902 of the first vehicle system is configured to receive vehicle event information and determine the power state based on the vehicle event information.

[0113] The power state processing module 903 of the second vehicle system is configured to receive vehicle event information and determine the power state based on the vehicle event information.

[0114] Among them, the first vehicle system and the second vehicle system are two different systems divided in the same chip using virtualization technology, and the first vehicle system and the second vehicle system are implemented using different operating systems.

[0115] According to the technical solution provided in the embodiment of the present application, a vehicle message is received from a vehicle gateway through a vehicle-mounted microcontroller, the vehicle message is parsed to obtain vehicle event information, and the vehicle information is sent to a first vehicle system and a second vehicle system implemented by different operating systems, respectively. The power status is determined based on the vehicle event information through power status management modules respectively provided in the first vehicle system and the second vehicle system, thereby enabling simultaneous power status management in multiple different vehicle-mounted systems, thereby improving the versatility and flexibility of power status management and enhancing management efficiency.

[0116] In some embodiments, the first vehicle system also includes a vehicle service module, and the power state processing module of the first vehicle system includes a first power service module and a first power state management module; the power state processing module of the first vehicle system determines the power state according to the vehicle event information, including: the first power service module receives the vehicle event information from the vehicle service module, and the vehicle event information is transmitted to the vehicle service module by the on-board microcontroller; the first power service module inputs the vehicle event information into the first power state management module; the first power state management module determines the power state according to the vehicle event information.

[0117] In some embodiments, the first vehicle system also includes a vehicle service module, and the power state management service module of the second vehicle system includes a second power service module, a second power state management module and a distributed bus; the power state management service module of the second vehicle system determines the power state based on vehicle event information, including: the distributed bus receives vehicle event information from the vehicle service module, and the vehicle event information is transmitted to the vehicle service module by the on-board microcontroller; the second power service module receives vehicle event information from the distributed bus; the second power service module inputs the vehicle event information into the second power state management module; the second power state management module determines the power state based on the vehicle event information.

[0118] In some embodiments, in response to determining that the second vehicle system does not include a power status processing module, or the power status processing module of the second vehicle system cannot determine the power status, vehicle event information is sent by the distributed bus to a hardware description module of the second vehicle system; the hardware description module sends the vehicle event information to the vehicle power management service module, so that the vehicle power management service module determines the power status based on the vehicle event information.

[0119] In some embodiments, the first vehicle system is an instrument system; after the power status processing module of the first vehicle system determines the power status, the method also includes: sending the power status to the function application module of the first vehicle system, so that the function application module of the first vehicle system determines the working mode of the target vehicle instrument function based on the power status; and / or sending the power status to the instrument panel to display the power status; wherein the target vehicle instrument function is a vehicle instrument function that operates in different working modes under different vehicle power states.

[0120] In some embodiments, the second vehicle system is a cockpit entertainment system; after the power status processing module of the second vehicle system determines the power status, the method also includes: sending the power status to the function application module of the second vehicle system, so that the function application module of the second vehicle system determines the working mode of the target cockpit entertainment function based on the power status; wherein the target cockpit entertainment function is a cockpit entertainment function that operates in different working modes under different vehicle power states.

[0121] In some embodiments, the power state management module determines the power state based on vehicle event information, including: configuring a state machine in the power state management module, the state machine including at least one state, each state corresponding to a power state; in response to the power state management module receiving vehicle event information, determining a target state that satisfies conditions corresponding to the vehicle event information; and determining that the target state is the power state.

[0122] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0123] Fig.10 Schematic diagram of an electronic device provided in an embodiment of the present application. Fig.10 As shown, the electronic device 10 of this embodiment includes: a processor 1001, a memory 1002, and a computer program 1003 stored in the memory 1002 and executable on the processor 1001. When the processor 1001 executes the computer program 1003, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 1001 executes the computer program 1003, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0124] The electronic device 10 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 10 may include, but is not limited to, a processor 1001 and a memory 1002. Those skilled in the art will appreciate that Fig.10The electronic device 10 is merely an example and does not limit the electronic device 10 . The electronic device 10 may include more or fewer components than shown in the figure, or different components.

[0125] The processor 1001 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0126] The memory 1002 may be an internal storage unit of the electronic device 10, for example, a hard disk or memory of the electronic device 10. The memory 1002 may also be an external storage device of the electronic device 10, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card (FlashCard), etc. equipped on the electronic device 10. The memory 1002 may also include both an internal storage unit of the electronic device 10 and an external storage device. The memory 1002 is used to store computer programs and other programs and data required by the electronic device.

[0127] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0128] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0129] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A vehicle power status management method, characterized in that: The method is performed by an on-board microcontroller and includes: Receive vehicle messages from the vehicle gateway; determining corresponding vehicle event information based on the vehicle message; Sending the vehicle event information to a power state processing module of a first vehicle system so that the power state processing module of the first vehicle system determines a power state according to the vehicle event information; and Sending the vehicle event information to a power state processing module of a second vehicle system so that a power state management service module of the second vehicle system determines a power state according to the vehicle event information; The first vehicle system and the second vehicle system are two different systems divided in the same chip using virtualization technology, and the first vehicle system and the second vehicle system are implemented using different operating systems.

2. The method according to claim 1, characterized in that The first vehicle system further comprises a vehicle service module, and the power state processing module of the first vehicle system comprises a first power service module and a first power state management module; The power state processing module of the first vehicle system determines the power state according to the vehicle event information, including: The first power service module receives the vehicle event information from the vehicle service module, and the vehicle event information is transmitted to the vehicle service module by the vehicle microcontroller; The first power service module inputs the vehicle event information into the first power state management module; The first power state management module determines a power state according to the vehicle event information.

3. The method according to claim 1, characterized in that The first vehicle system further comprises a vehicle service module, and the power state management service module of the second vehicle system comprises a second power service module, a second power state management module and a distributed bus; The power state management service module of the second vehicle system determines the power state according to the vehicle event information, including: The distributed bus receives the vehicle event information from the vehicle service module, and the vehicle event information is transmitted from the vehicle microcontroller to the vehicle service module; The second power service module receives the vehicle event information from the distributed bus; The second power service module inputs the vehicle event information into the second power state management module; The second power state management module determines a power state according to the vehicle event information.

4. The method according to claim 3, characterized in that The method further comprises: In response to determining that the second vehicle system does not include a power state processing module, or the power state processing module of the second vehicle system cannot determine the power state, sending the vehicle event information to a hardware description module of the second vehicle system via the distributed bus; The hardware description module sends the vehicle event information to the vehicle power management service module, so that the vehicle power management service module determines the power state based on the vehicle event information.

5. The method according to claim 1, characterized in that The first vehicle system is an instrument system; After the power state processing module of the first vehicle system determines the power state, the method further includes: Sending the power state to a function application module of the first vehicle system so that the function application module of the first vehicle system determines an operating mode of a target vehicle instrument function based on the power state; and / or sending the power status to a dashboard to display the power status; The target vehicle instrument function is a vehicle instrument function that operates in different operating modes under different vehicle power states.

6. The method according to claim 1, characterized in that The second vehicle system is a cockpit entertainment system; After the power state processing module of the second vehicle system determines the power state, the method further includes: sending the power state to a function application module of the second vehicle system, so that the function application module of the second vehicle system determines a working mode of a target cockpit entertainment function based on the power state; Among them, the target cockpit entertainment function is a cockpit entertainment function that works in different working modes under different vehicle power states.

7. The method according to claim 2 or 3, characterized in that: The power state management module determines the power state according to the vehicle event information, including: Configuring a state machine in the power state management module, the state machine comprising at least one state, each state corresponding to a power state; In response to the power state management module receiving the vehicle event information, determining a target state that satisfies a condition corresponding to the vehicle event information; The target state is determined to be the power state.

8. A vehicle power status management device, characterized in that: include: an onboard microcontroller configured to receive a vehicle message from a vehicle gateway and determine corresponding vehicle event information based on the vehicle message; A power state processing module of the first vehicle system is configured to receive the vehicle event information and determine a power state based on the vehicle event information; A power state processing module of the second vehicle system is configured to receive the vehicle event information and determine a power state based on the vehicle event information; The first vehicle system and the second vehicle system are two different systems divided in the same chip using virtualization technology, and the first vehicle system and the second vehicle system are implemented using different operating systems.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images