Automobile intelligent cabin hibernation method and device, electronic equipment and storage medium

Abstract

The application provides a car intelligent cockpit hibernation method and device, electronic equipment and storage medium, wherein the car intelligent cockpit hibernation method, in response to a system hibernation event, stops the service interaction between the protocol stack of the SoC and the upper layer application of the protocol stack of the SoC; sends an SPI communication connection end notification message to the MCU to stop the service interaction between the SPI protocol stack of the MCU and the upper layer application of the SPI protocol stack of the MCU; in response to the communication end response message sent by the MCU, disconnects the communication connection with the MCU; and executes the local hibernation processing logic of the SoC to complete the car intelligent cockpit hibernation. The car intelligent cockpit hibernation method provided by the application does not directly disconnect the physical SPI connection, but first completes the hibernation front service suspension and communication end confirmation at the SPI protocol stack level, and then disconnects the physical SPI connection, so the impact on the upper layer application is small, the upper layer application does not need to perceive the hibernation and wake-up process, and problems such as communication interruption, data loss and service error do not occur.

Description

Technical Field

[0001] This invention relates to the automotive field, and more specifically to a method, apparatus, electronic device, and storage medium for a smart cockpit to hibernate. Background Technology

[0002] In the hardware architecture of automotive intelligent cockpits, a dual-chip architecture is typically adopted, with SoC as the main control core and MCU as the auxiliary control unit. The two chips communicate with each other via SPI bus to achieve high-speed data interaction and command transmission, supporting the normal operation of various cockpit business applications.

[0003] The existing conventional technical solution is as follows: when the intelligent cockpit system triggers the whole-machine sleep process, the SPI communication link between the SoC and MCU is directly and physically disconnected. Subsequently, the SoC and MCU independently execute their own sleep logic to complete the whole-machine sleep. When the system is woken up, after the hardware link between the two parties is reconnected, the upper-layer business application re-initiates a series of operations such as SPI connection registration, link initialization, and communication parameter configuration to rebuild the data interaction channel. Therefore, the sleep disconnection method in the existing automotive intelligent cockpit technology has a significant impact on upper-layer applications. Summary of the Invention

[0004] The problem solved by this invention is that existing automotive intelligent cockpit hibernation methods cause significant interference to upper-level applications.

[0005] To address the above problems, this invention provides a method for hibernation in an automotive intelligent cockpit, wherein the method is applied to a System-on-Chip (SoC) and includes: In response to a system hibernation event, the business interaction between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC is stopped; Send an SPI communication connection termination notification message to the MCU to stop the business interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; In response to the communication termination acknowledgment message sent by the MCU, the communication connection with the MCU is disconnected; The SoC's local sleep processing logic is executed to complete the car's smart cockpit sleep process.

[0006] Optionally, the step of stopping the service interaction between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC in response to a system sleep event includes: In response to a system sleep event, the protocol stack of the SoC is stopped from receiving and processing SPI data transmission requests issued by the upper-layer application of the protocol stack of the SoC. Freeze the transmission of the current application message queue between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC.

[0007] Optionally, after executing the local sleep processing logic of the SoC to complete the car's smart cockpit sleep process, the method further includes: In response to a system wake-up event, re-establish communication with the MCU; Resume the transmission of the current application message queue between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC.

[0008] Optionally, re-establishing the communication connection with the MCU in response to a system wake-up event includes: In response to a system wake-up event, a handshake message is sent to the MCU; In response to the handshake reply sent by the MCU in response to the handshake message, a communication connection is established with the MCU.

[0009] This invention provides another method for sleep mode in an automotive intelligent cockpit, wherein the method is applied to an MCU and includes: In response to the SPI communication connection termination notification message sent by the SoC, the MCU's protocol stack stops receiving and processing SPI data transmission requests sent by the upper-layer application of the MCU's protocol stack; Freeze the transmission of the current application message queue between the protocol stack of the MCU and the upper-layer application of the protocol stack of the MCU; A communication termination response message is generated using the SPI protocol stack of the MCU; The communication termination response message is sent to the SoC via the SPI driver of the MCU; The local sleep processing logic of the MCU is executed to complete the sleep mode of the vehicle's smart cockpit.

[0010] Optionally, after executing the MCU's local sleep processing logic to complete the vehicle's smart cockpit sleep process, the following steps are included: In response to the handshake message sent by the SoC, the handshake message is verified through the protocol stack of the MCU; In response to the verification that the handshake message is valid, a handshake response is generated; The handshake response is sent to the SoC to establish a communication connection with the SoC.

[0011] Optionally, after sending the handshake response to the SoC to establish a communication connection with the SoC, the method further includes: Resume the transmission of the current application message queue between the protocol stack of the MCU and the upper-layer application of the protocol stack of the MCU.

[0012] This application also provides an automotive intelligent cockpit hibernation device, including: The first response unit is used to stop the business interaction between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC in response to a system hibernation event. The sending unit is used to send an SPI communication connection termination notification message to the MCU to stop the business interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; The second response unit is used to disconnect the communication connection with the MCU in response to the communication end acknowledgment message sent by the MCU. An execution unit is used to execute the local sleep processing logic of the SoC to complete the sleep mode of the automotive smart cockpit.

[0013] Compared with the prior art, the technical effect achieved by adopting this technical solution is as follows: the electronic device in this embodiment operates as the car intelligent cockpit hibernation method of any embodiment of the present invention, and therefore has all the beneficial effects of the car intelligent cockpit hibernation method of any embodiment of the present invention, which will not be repeated here.

[0014] In another aspect, embodiments of the present invention also provide an electronic device, which includes a memory and a processor; the memory stores a computer program, and the processor is used to run the computer program in the memory, wherein when the program or instructions are executed by the processor, the steps of the automotive intelligent cockpit hibernation method as described in any of the above embodiments are implemented.

[0015] Compared with the prior art, the technical effect achieved by adopting this technical solution is as follows: the electronic device in this embodiment operates as the car intelligent cockpit hibernation method of any embodiment of the present invention, and therefore has all the beneficial effects of the car intelligent cockpit hibernation method of any embodiment of the present invention, which will not be repeated here.

[0016] In another aspect, embodiments of the present invention also provide a storage medium storing a program or instructions, which, when executed by a processor, implement the steps of the automotive intelligent cockpit hibernation method as described in any of the above embodiments.

[0017] Compared with the prior art, the technical effects achieved by adopting this technical solution are as follows: The readable storage medium in this embodiment is used to store the car intelligent cockpit hibernation method as in any embodiment of the present invention, and therefore it has all the beneficial effects of the car intelligent cockpit hibernation method as in any embodiment of the present invention, which will not be repeated here.

[0018] The automotive intelligent cockpit hibernation method provided in this application, in response to a system hibernation event, stops the service interaction between the SoC's protocol stack and the upper-layer application of the SoC's protocol stack; sends an SPI communication connection termination notification message to the MCU to stop the service interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; disconnects the communication connection with the MCU in response to the communication termination acknowledgment message sent by the MCU; and executes the SoC's local hibernation processing logic to complete the automotive intelligent cockpit hibernation. The automotive intelligent cockpit hibernation method provided in this application does not directly disconnect the physical SPI connection, but rather completes the pre-hibernation service suspension and communication termination confirmation at the SPI protocol stack level before disconnecting the physical SPI connection. Therefore, the impact on upper-layer applications is minimal; upper-layer applications do not need to be aware of the hibernation and wake-up process, and there will be no problems such as communication interruption, data loss, or service errors. Attached Figure Description

[0019] Figure 1 A flowchart illustrating the automotive intelligent cockpit hibernation method provided in this application embodiment; Figure 2 Another flowchart illustrating the automotive intelligent cockpit hibernation method provided in this application embodiment; Figure 3 Another flowchart illustrating the automotive intelligent cockpit hibernation method provided in this application embodiment; Figure 4 A schematic diagram illustrating the software system configuration in the automotive intelligent cockpit hibernation method provided in this application embodiment; Figure 5 A schematic diagram of the hibernation process in the automotive intelligent cockpit hibernation method provided in the embodiments of this application; Figure 6 A schematic diagram of the wake-up process in the automotive intelligent cockpit hibernation method provided in the embodiments of this application; Figure 7 A schematic diagram of an automotive intelligent cockpit hibernation device provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0020] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] This application provides a method, apparatus, electronic device, and storage medium for hibernation in an automotive smart cockpit. The automotive smart cockpit hibernation apparatus can be integrated into an in-vehicle embedded electronic device, which may include components such as an application processor (SoC), a microcontroller (MCU), memory, a power management module, and an SPI communication interface. It is suitable for hibernation / wake-up scenarios based on the collaborative operation of the MCU and SoC in smart cockpits, intelligent driving systems, or other in-vehicle control systems.

[0022] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the preferred order of the embodiments.

[0023] First, let's continue with the background of this application. Existing technologies that directly switch the SPI communication link between the SoC and MCU have the following problems: 1. Significant impact on upper-layer business applications: The existing solution directly and abruptly cuts off the SPI communication link without a smooth transition between the protocol layer and the application layer, which will cause abnormal business communication, data packet loss, and interruption of the interaction process in the upper-layer App, and is very likely to cause problems such as business crashes and logic errors.

[0024] 2. Complex wake-up connection recovery logic: After the system wakes up, the upper-layer application needs to actively participate in a large amount of customized adaptation development such as SPI link reconstruction, parameter adaptation, and session reconnection. The application development and adaptation workload is large and the transformation cost is high.

[0025] 3. Long wake-up time and poor system startup performance: It relies on manually rebuilding the communication link at the application layer. The initialization process is cumbersome and there are many interactive handshake steps, which prolongs the overall wake-up startup time, reduces the cold / warm wake-up response speed of the intelligent cockpit system, and affects the user experience.

[0026] 4. Lack of a unified link pause and resume mechanism: The lack of a unified sleep pre-processing and wake-up handshake mechanism at the SPI protocol stack level results in fragmented software and hardware link switching, making it impossible to achieve seamless continuity of link status.

[0027] This application proposes various embodiments that can solve the above-mentioned problems.

[0028] refer to Figure 1 , Figure 1 This is a flowchart illustrating the automotive intelligent cockpit hibernation method provided in an embodiment of this application. The method provided in this application specifically includes the following steps: 110. In response to a system hibernation event, stop the business interaction between the SoC's protocol stack and the upper-layer applications of the SoC's protocol stack.

[0029] In the method of this application, when the power management module of the SoC detects and receives a system sleep event, the SoC's SPI protocol stack actively executes the interaction pause logic with the upper-layer application, stopping the reception and processing of SPI data transmission requests sent by the upper-layer App, and freezing the application-side communication services. The upper-layer application in this application can refer to an App in a car's smart cockpit, such as a calling application or a navigation application.

[0030] 120. Send an SPI communication connection termination notification message to the MCU to stop the business interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack.

[0031] The SoC's SPI protocol stack sends an SPI communication connection termination notification message to the MCU via the underlying SPI driver. When the MCU's SPI driver receives this notification message, it reports it to the MCU's SPI protocol stack, which then synchronously suspends its interaction with the upper-layer application and stops responding to application-layer SPI transmit / receive service requests.

[0032] 130. In response to the communication termination acknowledgment message sent by the MCU, disconnect the communication connection with the MCU.

[0033] To notify the SoC that the communication connection can be disconnected, the MCU's SPI protocol stack generates a communication termination acknowledgment message and sends it back to the SoC via the SPI driver. Upon receiving the acknowledgment message, the SoC considers it safe to disconnect from the MCU. In other words, after receiving the acknowledgment message, the SoC confirms that the business interaction between the two parties has been suspended and the link pre-disconnection is complete, and the formal logic then cuts off the SPI communication connection.

[0034] 140. Execute the SoC's local sleep processing logic to complete the car's smart cockpit sleep.

[0035] When the communication connection is lost, the SoC can call its own power management module to execute local sleep processing logic, completing peripheral shutdown, clock frequency reduction, and power domain control, ultimately achieving overall sleep mode for the intelligent cockpit system. Understandably, the MCU can also call its own power management module at this time to execute local sleep processing logic.

[0036] The automotive intelligent cockpit hibernation method provided in this application, in response to a system hibernation event, stops the service interaction between the SoC's protocol stack and the upper-layer application of the SoC's protocol stack; sends an SPI communication connection termination notification message to the MCU to stop the service interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; disconnects the communication connection with the MCU in response to the communication termination acknowledgment message sent by the MCU; and executes the SoC's local hibernation processing logic to complete the automotive intelligent cockpit hibernation. The automotive intelligent cockpit hibernation method provided in this application does not directly disconnect the physical SPI connection, but rather completes the pre-hibernation service suspension and communication termination confirmation at the SPI protocol stack level before disconnecting the physical SPI connection. Therefore, the impact on upper-layer applications is minimal; upper-layer applications do not need to be aware of the hibernation and wake-up process, and there will be no problems such as communication interruption, data loss, or service errors.

[0037] Since the method of this application does not require physically disconnecting the connection between the SoC and the MCU, there is no need for customized development such as SPI reconnection, parameter configuration, and session recovery in the upper-layer business application. This reduces the workload of application-side code modification and logic adaptation. Furthermore, it can automatically complete handshake connection establishment, queue retransmission, and data notification at the protocol stack layer, saving the time spent on manual initialization and reconnection at the application layer, shortening the overall machine wake-up and startup time, and improving the cockpit response speed.

[0038] refer to Figure 2 , Figure 2 Another flowchart illustrating the automotive intelligent cockpit hibernation method provided in this application embodiment shows that, in some embodiments, in response to a system hibernation event, the service interaction between the SoC's protocol stack and the upper-layer application of the SoC's protocol stack is stopped, including: 201. In response to a system sleep event, stop the SoC's protocol stack from receiving and processing SPI data transmission requests sent by upper-layer applications of the SoC's protocol stack.

[0039] 202. Freeze the transmission of the current application message queue between the SoC's protocol stack and the upper-layer application of the SoC's protocol stack.

[0040] For the currently transmitting application message queue, this application can freeze the current application message queue during hibernation to ensure the continuity of business communication before and after hibernation. It is understood that when the system wakes up, i.e., when hibernation ends, the frozen current application message queue needs to be restored in this embodiment. Therefore, in some embodiments, step 202 further includes: in response to a system wake-up event, re-establishing a communication connection with the MCU; and restoring the transmission of the current application message queue between the SoC's protocol stack and the upper-layer application of the SoC's protocol stack. It is evident that the method link state of this embodiment can seamlessly connect before and after hibernation, freezing the application message queue during hibernation and automatically retransmitting backlogged data after wake-up, ensuring the continuity of business communication before and after hibernation and guaranteeing the stability of intelligent cockpit business operation.

[0041] refer to Figure 3 , Figure 3 This is another flowchart illustrating the automotive smart cockpit sleep method provided in the embodiments of this application. In some embodiments, in response to a system wake-up event, a communication connection with the MCU is re-established, including: 301. In response to a system wake-up event, send a handshake message to the MCU.

[0042] 302. In response to the handshake reply sent by the MCU in response to the handshake message, establish a communication connection with the MCU.

[0043] Understandably, before sending the handshake message, both the SoC and MCU receive wake-up interrupt signals, and their respective power management modules initiate local hardware wake-up initialization, clock and power domain recovery. After the basic hardware is ready, the SoC, acting as the SPI Master, actively initiates link reconstruction and sends an SPI connection establishment handshake message to the MCU.

[0044] On the MCU side, the MCU's SPI driver receives the handshake message and reports it to the SPI protocol stack. After the MCU protocol stack verifies its validity, it generates a connection establishment handshake response and sends it back to the SoC. Upon receiving the response, the SoC and MCU complete the SPI communication link handshake confirmation and re-establish the logical communication connection. The SPI protocol stacks of the SoC and MCU respectively restore the interaction path with the upper-layer application, automatically retrieve and check the local application message sending queue, and transmit the application messages that were backlogged before hibernation to the other end through the SPI driver. Afterwards, the SPI protocol stacks of both sides actively notify the corresponding upper-layer application of the received application data messages. The upper-layer application does not need to reconnect or initialize and can directly resume normal operation of the business logic before hibernation.

[0045] For ease of understanding, via Figures 4-6 The process of one implementation scenario of this application is described below. Figure 4 A schematic diagram illustrating the software system configuration in the automotive intelligent cockpit hibernation method provided in this application embodiment; Figure 5A schematic diagram of the hibernation process in the automotive intelligent cockpit hibernation method provided in the embodiments of this application; Figure 6 This is a schematic diagram of the wake-up process in the automotive intelligent cockpit hibernation method provided in this application embodiment; wherein, through Figure 4 and Figure 5 The system hibernation process can be seen through the following steps: When the SoC's power management module detects and receives a system sleep event, the SoC's SPI protocol stack actively executes the interaction pause logic with the upper-layer App, stops receiving and processing SPI data transmission requests sent by the upper-layer App, and freezes application-side communication services.

[0046] The SoC's SPI protocol stack sends an SPI communication connection termination notification message to the MCU via the underlying SPI driver. The MCU's SPI driver receives this notification message and reports it to the MCU's SPI protocol stack. The MCU's SPI protocol stack then simultaneously suspends its interaction with the upper-layer application and stops responding to application-layer SPI transmit / receive service requests.

[0047] The MCU's SPI protocol stack generates a communication termination response message and sends it back to the SoC via the SPI driver. Upon receiving the response message, the SoC confirms that the business interaction between the two parties has been suspended and the link pre-disconnection is complete, and the formal logic disconnects the SPI communication connection.

[0048] The SoC and MCU each call their own power management modules to execute local sleep processing logic, complete peripheral shutdown, clock frequency reduction, and power domain control, and finally realize the overall sleep of the intelligent cockpit system.

[0049] pass Figure 4 and Figure 6 The system wake-up process involves the following steps: After the system triggers wake-up, the SoC and MCU respectively receive the wake-up interrupt signal, and their respective power management modules start local hardware wake-up initialization, clock and power domain recovery.

[0050] After the basic hardware is ready, the SoC, acting as the SPI Master, actively initiates link reconstruction and sends an SPI connection establishment handshake message to the MCU.

[0051] The MCU's SPI driver receives the handshake message and reports it to the SPI protocol stack. After the MCU protocol stack verifies the validity, it generates a connection establishment handshake response and sends it back to the SoC.

[0052] After the SoC receives the response, both parties complete the SPI communication link handshake confirmation and re-establish the logical communication connection.

[0053] The SPI protocol stacks of the SoC and MCU respectively restore the interaction path with the upper-layer App, automatically retrieve and check the local application message sending queue, and transmit the application messages that were backed up before hibernation to the other end through the SPI driver.

[0054] The SPI protocol stacks of both parties will actively notify the corresponding upper-layer App of the received peer application data packets. The upper-layer application does not need to reconnect or initialize, and can directly continue the normal operation of the business logic before hibernation.

[0055] Therefore, this application has at least the following beneficial effects: 1. Completely seamless and unobtrusive to the application layer: The SPI protocol stack layer uniformly completes the suspension of business interaction, pre-disconnection of links and subsequent automatic recovery. The upper layer application does not need to be aware of the sleep and wake-up process, and there will be no communication interruption, data loss, business error, etc., achieving transparent processing of the application.

[0056] 2. Significantly reduce application adaptation costs: No need for customized development of upper-layer business applications such as SPI reconnection, parameter configuration, and session recovery, reducing the workload of application-side code modification and logic adaptation.

[0057] 3. Improve system wake-up and startup performance: Automatically complete handshake connection establishment, queue retransmission, and data notification at the protocol stack layer, saving the time spent on manual initialization and reconnection at the application layer, shortening the overall wake-up and startup time, and improving the cockpit response speed.

[0058] 4. Seamless continuity of link status: The application message queue is frozen during hibernation, and the backlogged data is automatically resent after wake-up, ensuring the continuity of business communication before and after hibernation and ensuring the stability of intelligent cockpit business operation.

[0059] 5. Standardized dual-chip architecture adaptation: Based on the existing App, SPI protocol stack, SPI driver, and power management layered architecture, no additional hardware circuits are required. It can be implemented simply through software process optimization, with strong compatibility and portability.

[0060] To facilitate better implementation of the automotive intelligent cockpit hibernation method provided in this application embodiment, an automotive intelligent cockpit hibernation device is also provided in one embodiment. The meanings of the terms used are the same as in the above-described automotive intelligent cockpit hibernation method, and specific implementation details can be found in the description of the method embodiment.

[0061] The car's intelligent cockpit hibernation device can be integrated into computer equipment, such as... Figure 7 As shown, the automotive intelligent cockpit hibernation device may include: a first response unit 701, a sending unit 702, a second response unit 703, and an execution unit 704, as detailed below: The first response unit 701 is used to stop the business interaction between the SoC's protocol stack and the upper-layer application of the SoC's protocol stack in response to a system sleep event. The sending unit 702 is used to send an SPI communication connection termination notification message to the MCU to stop the business interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; The second response unit 703 is used to disconnect the communication connection with the MCU in response to the communication end acknowledgment message sent by the MCU. Execution unit 704 is used to execute the SoC's local sleep processing logic to complete the automotive smart cockpit sleep process.

[0062] This application also provides an electronic device, which may be an in-vehicle embedded electronic device, such as... Figure 8 As shown, it illustrates a structural schematic diagram of the in-vehicle embedded electronic device involved in the embodiments of this application. Specifically: The vehicle-mounted embedded electronic device may include components such as a processor 1001 with one or more processing cores, a memory 1002 with one or more computer-readable storage media, a power supply 1003, and an input unit 1004. Those skilled in the art will understand that... Figure 8 The automotive embedded electronics structure shown does not constitute a limitation on automotive embedded electronics, and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein: The processor 1001 is the control center of the vehicle-mounted embedded electronic device. It connects various parts of the device via various interfaces and lines, and executes software programs and / or modules stored in the memory 1002, as well as calling data stored in the memory 1002, to perform various functions and process data, thereby providing overall monitoring of the device. Optionally, the processor 1001 may include one or more processing cores; preferably, the processor 1001 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and computer programs, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 1001.

[0063] The memory 1002 can be used to store software programs and modules. The processor 1001 executes various functional applications and data processing by running the software programs and modules stored in the memory 1002. The memory 1002 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, computer programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the vehicle-mounted embedded electronic device, etc. In addition, the memory 1002 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 1002 may also include a memory controller to provide the processor 1001 with access to the memory 1002.

[0064] The vehicle-mounted embedded electronic device also includes a power supply 1003 that supplies power to various components. Preferably, the power supply 1003 can be logically connected to the processor 1001 through a power management system, thereby realizing functions such as power domain control, power-on / off timing control, sleep / wake-up power management, and power consumption management. The power module 1003 may also include components such as a vehicle-mounted DC power input interface, a power management chip, a voltage regulator circuit, a power fault detection circuit, and a power status detection circuit.

[0065] The vehicle-mounted embedded electronic device may also include an input unit 1004, which can be used to receive input digital or character information, and generate signal inputs such as vehicle switches, steering wheel buttons, touch screens, knobs or joysticks related to user settings and function control.

[0066] Although not shown, the vehicle-mounted embedded electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 1001 in the vehicle-mounted embedded electronic device loads the executable files corresponding to the processes of one or more computer programs into the memory 1002 according to the following instructions, and the processor 1001 runs the computer programs stored in the memory 1002 to realize various functions, as follows: In response to a system sleep event, stop the business interaction between the SoC's protocol stack and the upper-layer applications of the SoC's protocol stack; Send an SPI communication connection termination notification message to the MCU to stop the business interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; In response to the communication termination acknowledgment message sent by the MCU, the communication connection with the MCU is disconnected; Execute the SoC's local sleep processing logic to complete the car's smart cockpit sleep.

[0067] Therefore, the automotive intelligent cockpit hibernation method provided in this application, in response to a system hibernation event, stops the service interaction between the SoC's protocol stack and the upper-layer application of the SoC's protocol stack; sends an SPI communication connection termination notification message to the MCU to stop the service interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; disconnects the communication connection with the MCU in response to the communication termination acknowledgment message sent by the MCU; and executes the SoC's local hibernation processing logic to complete the automotive intelligent cockpit hibernation. The automotive intelligent cockpit hibernation method provided in this application does not directly disconnect the physical SPI connection, but rather completes the pre-hibernation service suspension and communication termination confirmation at the SPI protocol stack level before disconnecting the physical SPI connection. Therefore, the impact on upper-layer applications is minimal, and upper-layer applications do not need to be aware of the hibernation and wake-up process, thus avoiding problems such as communication interruption, data loss, and service errors.

[0068] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0069] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium (also referred to as a storage medium). A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations of the above embodiments.

[0070] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by a computer program, or by a computer program controlling related hardware. The computer program can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0071] Therefore, embodiments of this application provide a storage medium storing a computer program that can be loaded by a processor to execute the steps in any of the automotive smart cockpit hibernation methods provided in embodiments of this application.

[0072] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0073] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0074] Since the computer program stored in the storage medium can execute the steps in any of the automotive intelligent cockpit hibernation methods provided in the embodiments of this application, the beneficial effects that any of the automotive intelligent cockpit hibernation methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0075] The above provides a detailed description of a method, apparatus, electronic device, and storage medium for hibernation in an intelligent automotive cockpit, as provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, those skilled in the art will recognize that there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for hibernation in an automotive intelligent cockpit based on SPI communication, characterized in that, The method is applied to a SoC and includes: In response to a system hibernation event, the business interaction between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC is stopped; Send an SPI communication connection termination notification message to the MCU to stop the business interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; In response to the communication termination acknowledgment message sent by the MCU, the communication connection with the MCU is disconnected; The SoC's local sleep processing logic is executed to complete the car's smart cockpit sleep process.

2. The automotive intelligent cockpit hibernation method according to claim 1, characterized in that, The step of stopping the service interaction between the protocol stack of the SoC and the upper-layer application of the protocol stack in response to a system sleep event includes: In response to a system sleep event, the protocol stack of the SoC is stopped from receiving and processing SPI data transmission requests issued by the upper-layer application of the protocol stack of the SoC. Freeze the transmission of the current application message queue between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC.

3. The automotive intelligent cockpit hibernation method according to claim 2, characterized in that, After executing the local sleep processing logic of the SoC to complete the sleep mode of the vehicle's smart cockpit, the method further includes: In response to a system wake-up event, re-establish communication with the MCU; Resume the transmission of the current application message queue between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC.

4. The automotive intelligent cockpit hibernation method according to claim 3, characterized in that, The step of re-establishing a communication connection with the MCU in response to a system wake-up event includes: In response to a system wake-up event, a handshake message is sent to the MCU; In response to the handshake reply sent by the MCU in response to the handshake message, a communication connection is established with the MCU.

5. A method for hibernation in an automotive intelligent cockpit based on SPI communication, characterized in that, The method is applied to an MCU and includes: In response to the SPI communication connection termination notification message sent by the SoC, the MCU's protocol stack stops receiving and processing SPI data transmission requests sent by the upper-layer application of the MCU's protocol stack; Freeze the transmission of the current application message queue between the protocol stack of the MCU and the upper-layer application of the protocol stack of the MCU; A communication termination response message is generated using the SPI protocol stack of the MCU; The communication termination response message is sent to the SoC via the SPI driver of the MCU; The local sleep processing logic of the MCU is executed to complete the sleep mode of the vehicle's smart cockpit.

6. The automotive intelligent cockpit hibernation method according to claim 5, characterized in that, After executing the MCU's local sleep processing logic to complete the vehicle's smart cockpit sleep process, the following steps are included: In response to the handshake message sent by the SoC, the handshake message is verified through the protocol stack of the MCU; In response to the verification that the handshake message is valid, a handshake response is generated; The handshake response is sent to the SoC to establish a communication connection with the SoC.

7. The automotive intelligent cockpit hibernation method according to claim 6, characterized in that, After sending the handshake response to the SoC to establish a communication connection with the SoC, the method further includes: Resume the transmission of the current application message queue between the protocol stack of the MCU and the upper-layer application of the protocol stack of the MCU.

8. A car intelligent cockpit hibernation device based on SPI communication, characterized in that, include: The first response unit is used to stop the business interaction between the protocol stack of the SoC and the upper-layer application of the protocol stack of the SoC in response to a system hibernation event. The sending unit is used to send an SPI communication connection termination notification message to the MCU to stop the business interaction between the MCU's SPI protocol stack and the upper-layer application of the MCU's SPI protocol stack; The second response unit is used to disconnect the communication connection with the MCU in response to the communication end acknowledgment message sent by the MCU. An execution unit is used to execute the local sleep processing logic of the SoC to complete the sleep mode of the automotive smart cockpit.

9. An electronic device, characterized in that, It includes a memory and a processor; the memory stores a computer program, and the processor is used to run the computer program in the memory to perform the automotive intelligent cockpit hibernation method according to any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium stores multiple computer programs, which are adapted for loading by a processor to execute the automotive intelligent cockpit hibernation method according to any one of claims 1 to 7.

Images