Vehicle digital key task processing method, vehicle digital key system and vehicle

Abstract

This application discloses a vehicle digital key task processing method, a vehicle digital key system, and a vehicle, relating to the fields of communication and vehicle technology. The method includes: in response to receiving a wake-up signal from a mobile terminal via a control unit, controlling the control unit to execute a wake-up signal forwarding task, wherein the wake-up signal forwarding task is used to forward the wake-up signal to an on-chip system; after the wake-up signal forwarding task is completed, controlling the control unit to execute a first digital key activation task; in response to the on-chip system receiving a wake-up signal, controlling the on-chip system to execute a second digital key activation task; in response to the completion of both the first and second digital key activation tasks, controlling the control unit and the on-chip system to perform a handshake operation, and executing the digital key task after the handshake operation is completed. This application solves the technical problems of high cost and limited processing capacity in related vehicle digital key systems.

Description

Technical Field

[0001] This application relates to the fields of communication and vehicle technology, and more specifically, to a vehicle digital key task processing method, a vehicle digital key system, and a vehicle. Background Technology

[0002] A vehicle digital key system is an integrated system that uses wireless communication and cryptography technologies, with smart terminals (such as smartphones and smartwatches) as carriers, to replace the transmission of physical keys and achieve secure identity authentication and control of vehicles.

[0003] Currently, traditional vehicle digital key systems use a separate embedded microcontroller unit (MCU) as the core processing unit, coupled with a dedicated security chip and custom hardware, forming the basic architecture of the vehicle digital key system. However, using a dedicated security chip and custom hardware increases costs, and the limited processing power of embedded MCUs makes it difficult to quickly process complex encryption algorithms, thus limiting the functionality and performance of the vehicle digital key system.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a vehicle digital key task processing method, a vehicle digital key system, and a vehicle, to at least solve the technical problems of high cost and limited processing capacity of vehicle digital key systems in the related art.

[0006] According to one aspect of the embodiments of this application, a vehicle digital key task processing method is provided, applied to a vehicle digital key system in a vehicle. The vehicle digital key system includes a control unit and a system-on-a-chip (SoC). The method includes: in response to receiving a wake-up signal from a mobile terminal through the control unit, controlling the control unit to execute a wake-up signal forwarding task, wherein the wake-up signal forwarding task is used to forward the wake-up signal to the SoC, and the wake-up signal forwarding task has the highest execution priority among the tasks to be executed by the control unit; after the wake-up signal forwarding task is completed, controlling the control unit to execute a first digital key startup task, wherein the first digital key startup task is used to initialize the communication connection between the control unit and the mobile terminal; in response to the SoC receiving a wake-up signal, controlling the SoC to execute a second digital key startup task, wherein the second digital key startup task is used to load the software and functional modules corresponding to the digital key task, and the second digital key startup task has the highest execution priority among the tasks to be executed by the SoC; in response to the completion of both the first and second digital key startup tasks, controlling the control unit and the SoC to perform a handshake operation, and executing a digital key task after the handshake operation is completed, wherein the digital key task is used to perform access control operations and permission management operations on the vehicle.

[0007] Furthermore, in response to receiving a wake-up signal from the mobile terminal via the control unit, controlling the control unit to perform a wake-up signal forwarding task includes: in response to the vehicle being powered on, controlling the control unit to perform a bootloader operation; and during the execution of the bootloader, in response to receiving a wake-up signal from the mobile terminal via the control unit, controlling the control unit to perform a wake-up signal forwarding task.

[0008] Furthermore, in response to receiving a wake-up signal from the mobile terminal via the control unit, the control unit performs a wake-up signal forwarding task including: in response to the vehicle being powered on, the control unit performs a bootloader operation; in response to the completion of the bootloader operation, the control unit enters a startup mode, wherein the startup mode is used to initialize hardware and software resources; in the startup mode, in response to receiving a wake-up signal from the mobile terminal via the control unit, the control unit performs a wake-up signal forwarding task.

[0009] Furthermore, in the startup mode, in response to receiving a wake-up signal from the mobile terminal through the control unit, controlling the control unit to perform a wake-up signal forwarding task includes: in the startup mode, controlling the control unit to perform a security authentication operation, wherein the security authentication operation is used to verify the identity of the mobile terminal; in response to the completion of the security authentication operation and receiving a wake-up signal from the mobile terminal through the control unit, controlling the control unit to perform a wake-up signal forwarding task.

[0010] Furthermore, the method also includes: in startup mode, controlling the control unit to perform a security authentication operation, wherein the security authentication operation is used to verify the identity of the mobile terminal.

[0011] Furthermore, in response to receiving a wake-up signal from the mobile terminal via the control unit, controlling the control unit to perform a wake-up signal forwarding task includes: in response to the control unit exiting the startup mode, controlling the control unit to enter the application mode, wherein the application mode is used to start and run the application; within a preset time period of the application mode, in response to receiving a wake-up signal from the mobile terminal via the control unit, controlling the control unit to perform a wake-up signal forwarding task, wherein the preset time period is used to represent the time period from the first moment when the control unit enters the application mode to the second moment, the second moment being later than the first moment.

[0012] Furthermore, in response to the on-chip system receiving a wake-up signal, controlling the on-chip system to execute the second digital key startup task includes: in response to the on-chip system receiving a wake-up signal, controlling the on-chip system to execute a startup time reduction wake-up process; and during the startup time reduction wake-up process, controlling the on-chip system to execute the second digital key startup task.

[0013] Furthermore, in response to the completion of both the first and second digital key startup tasks, the control unit and the system-on-chip perform a handshake operation, and the execution of the digital key task after the handshake operation is completed includes: in response to the completion of both the first and second digital key startup tasks, the control unit and the system-on-chip perform a handshake operation, wherein the handshake operation is used to determine the communication connection status between the control unit and the system-on-chip; in response to the completion of the handshake operation, the control unit and the system-on-chip perform a signature verification operation to obtain a verification result, wherein the signature verification operation is used to verify the integrity of the communication data; in response to the verification result indicating that the verification is successful, the control unit and the system-on-chip execute the digital key task.

[0014] According to another aspect of the embodiments of this application, a vehicle digital key system is also provided. The vehicle digital key system includes at least a control unit and a system-on-a-chip (SoC). The SoC includes a driving domain, an entertainment domain, and a connectivity domain. The connectivity domain is used to perform digital key functions. The vehicle digital key system is used to perform the methods in the various embodiments of this application.

[0015] According to another aspect of the embodiments of this application, a vehicle digital key task processing device is also provided, applied to a vehicle digital key system in a vehicle. The vehicle digital key system includes a control unit and a system-on-a-chip (SoC). The device includes: a first control module, configured to control the control unit to execute a wake-up signal forwarding task in response to receiving a wake-up signal from a mobile terminal via the control unit, wherein the wake-up signal forwarding task is used to forward the wake-up signal to the SoC, and the wake-up signal forwarding task has the highest execution priority among the tasks to be executed by the control unit; and a second control module, configured to control the control unit to execute a first digital key activation task after the wake-up signal forwarding task is executed, wherein the first digital key activation task is used to... The system initializes the communication connection between the control unit and the mobile terminal; the third control module is used to control the on-chip system to execute the second digital key startup task in response to the on-chip system receiving a wake-up signal, wherein the second digital key startup task is used to load the software and functional modules corresponding to the digital key task, and the second digital key startup task has the highest execution priority among the tasks to be executed in the on-chip system; the fourth control module is used to control the control unit and the on-chip system to perform a handshake operation in response to the completion of both the first and second digital key startup tasks, and to execute the digital key task after the handshake operation is completed, wherein the digital key task is used to perform access control operations and permission management operations on the vehicle.

[0016] According to another aspect of the embodiments of this application, a vehicle digital key system is also provided. The vehicle digital key system includes at least a control unit and a system-on-a-chip (SoC). The SoC includes a driving domain, an entertainment domain, and a connectivity domain. The connectivity domain is used to perform digital key functions. The vehicle digital key system is used to perform the methods in the various embodiments of this application.

[0017] According to another aspect of the embodiments of this application, a vehicle is also provided, including: a memory storing an executable program; and a processor for running the executable program, wherein the executable program performs the methods of various embodiments of this application when running on the processor.

[0018] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0019] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0020] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the methods in various embodiments of this application.

[0021] In this embodiment, if the control unit receives a wake-up signal from the mobile terminal, it executes a wake-up signal forwarding task. This task forwards the wake-up signal to the on-chip system (OSS) and has the highest execution priority among the control unit's tasks. After the wake-up signal forwarding task is completed, the control unit executes a first digital key startup task, which initializes the communication connection between the control unit and the mobile terminal. Subsequently, if the OSS receives a wake-up signal, it executes a second digital key startup task, which loads the corresponding software and functional modules. This task also has the highest execution priority among the OSS's tasks. Finally, after both the first and second digital key startup tasks are completed, the control unit and OSS perform a handshake operation. After the handshake is completed, the digital key task is executed. This task performs access control and permission management operations on the vehicle, achieving rapid response and efficient processing. This reduces costs and improves performance, thus solving the problems of high cost and limited processing capacity in related vehicle digital key systems. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0023] Figure 1 This is a schematic diagram of the structure of a traditional vehicle digital key system;

[0024] Figure 2 This is a flowchart illustrating a vehicle digital key task processing method according to an embodiment of this application;

[0025] Figure 3 This is a flowchart illustrating another vehicle digital key task processing method according to an embodiment of this application;

[0026] Figure 4 This is a schematic diagram of a vehicle digital key system according to an embodiment of this application;

[0027] Figure 5 This is a comparative schematic diagram of one solution according to an embodiment of this application;

[0028] Figure 6 This is a structural block diagram of a vehicle digital key system according to an embodiment of this application;

[0029] Figure 7 This is a structural block diagram of a vehicle digital key task processing device according to an embodiment of this application. Detailed Implementation

[0030] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] The digital key system establishes a security architecture consisting of a mobile terminal, an in-vehicle terminal, and a cloud server. Utilizing near-field communication (NFC) technology, it performs functions including but not limited to identity authentication, door unlocking, vehicle start, and access sharing. The digital key system comprises three parts: a mobile terminal, a cloud server, and an in-vehicle terminal system (i.e., the vehicle digital key system).

[0033] Figure 1 This is a schematic diagram of the structure of a traditional vehicle digital key system, such as... Figure 1 As shown, Figure 1 It includes a central domain computing platform, a digital key cloud platform server, a vehicle domain control platform, a Bluetooth Low Energy (BLE) module, an Ultra-Wideband (UWB) module, and a Near Field Communication (NFC) module.

[0034] The central domain computing platform is the central processing unit of the vehicle digital key system. It includes a system-on-chip (SOC) unit and an MCU unit. The SOC unit and the MCU unit communicate via a serial port.

[0035] As a high-performance computing center, the SOC unit is responsible for handling more complex computing tasks and employs Trusted Execution Environment (TEE) secure storage technology. The SOC unit includes three virtual subsystems: the driving domain, the entertainment domain, and the connectivity domain, representing the vehicle's driver assistance functions, entertainment system, and network connectivity functions, respectively.

[0036] The MCU unit is the control center of the digital key system. In traditional vehicle digital key systems, the MCU unit executes digital key functions and integrates the digital key vehicle application program (APP). In other words, the MCU unit is responsible for handling all tasks related to the digital key, such as authentication and key management. Traditional vehicle digital key systems also have a dedicated security SE (Secure Entity).

[0037] The digital key cloud platform server communicates bidirectionally with the network domain subsystem within the SOC unit via the Hypertext Transfer Protocol Secure (HTTPS) protocol, and is responsible for the authentication, distribution, and management of digital keys.

[0038] The vehicle body domain control platform, comprising UWB and NFC modules, acts as the actuator for vehicle control, performing operations such as unlocking and starting the vehicle according to instructions from the central domain computing platform. The UWB and NFC modules are responsible for ultra-wideband communication and short-range communication, respectively. They interact with the vehicle body domain control platform and exchange data with the central domain computing platform via the Controller Area Network Flexible Data Rate (CAN FD) bus.

[0039] The BLE module is responsible for Bluetooth communication with the mobile terminal. The BLE module and the MCU unit of the central domain computing platform conduct bidirectional data transmission through the Controller Area Network (CAN) bus.

[0040] It can be seen that traditional vehicle digital key systems have the following drawbacks:

[0041] Disadvantage (1): Traditional vehicle digital key systems typically use dedicated chips or dedicated electronic control units (ECUs) to implement digital key functions. They require independent dedicated security chips (such as secure elements (SE)), customized communication hardware, a large number of components, and high costs, which makes it difficult to popularize vehicle digital key systems.

[0042] Disadvantage (2): Traditional vehicle digital key systems are independent of the vehicle central computing platform, and the information interaction path is lengthy, resulting in a long time from user initiation of commands to vehicle display and execution response, and poor user experience.

[0043] Disadvantages (3): Traditional vehicle digital key systems are based on dedicated chips or hardware platforms and use embedded MCU processors to execute core functions. They cannot process complex encryption algorithms quickly, and multi-task concurrent processing is slow. Software programming is mostly in C language environment or small JavaCOS environment, which is not conducive to the rapid deployment of advanced functions and has little room for later function upgrades.

[0044] According to an embodiment of this application, a method embodiment for processing vehicle digital key tasks is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0045] This application provides a vehicle digital key task processing method, which can be used to provide vehicle digital key task processing functions for preset application scenarios. The preset application scenarios can include the following scenarios in the field of vehicles: commuting autonomous driving scenarios, artificial intelligence (AI) assisted driving scenarios for private cars, automatic parking assistance (APA) scenarios (such as memory parking for self-owned parking spaces in garages, intelligent parking for designated parking spaces in parking lots, etc.), and intelligent navigation-guided pilot (NGP) scenarios in urban areas or highway areas.

[0046] Figure 2 This is a flowchart illustrating a vehicle digital key task processing method according to an embodiment of this application. The method is applied to a vehicle digital key system, which includes a control unit and a system-on-a-chip (SoC), such as... Figure 2 As shown, the method includes the following steps:

[0047] Step S21: In response to receiving a wake-up signal from the mobile terminal through the control unit, the control unit is controlled to execute a wake-up signal forwarding task, wherein the wake-up signal forwarding task is used to forward the wake-up signal to the on-chip system, and the wake-up signal forwarding task has the highest execution priority among the tasks to be executed by the control unit.

[0048] In this embodiment of the application, the vehicle digital key system includes a control unit and a system on a chip. The control unit is an MCU unit, which is responsible for receiving, parsing and executing instructions from different sources, including but not limited to wake-up signals sent by mobile terminals, as well as various subsequent digital key operation instructions.

[0049] The system-on-a-chip (SoC) is a SOC unit, which is a SOC unit on a central computing domain platform with powerful processing capabilities and a complex operating system. The SOC unit is responsible for handling more complex computing tasks and adopts general-purpose TEE secure storage technology.

[0050] In this application, if a wake-up signal is received from a mobile terminal via the MCU unit, the MCU unit is controlled to perform a wake-up signal forwarding task. The wake-up signal is a signal sent by the mobile terminal to the vehicle's MCU unit via wireless communication technology (e.g., BLE, NFC, UWB technology) to trigger the activation of the vehicle's digital key system.

[0051] The mobile terminal is a smart device carrying a digital key, such as a smartphone or smartwatch. When the mobile terminal approaches the vehicle, it sends a wake-up signal to the vehicle's MCU unit via wireless communication technology, thereby triggering the vehicle's digital key system to wake up and start quickly.

[0052] The wake-up signal forwarding task has the highest execution priority among the tasks to be executed in the control unit. That is, the wake-up signal forwarding task is the first task executed by the MCU unit after receiving the wake-up signal. The wake-up signal forwarding task is used to instruct the MCU unit to immediately forward the wake-up signal to the SOC unit so that the SOC unit can respond quickly and enter the working state.

[0053] As can be seen, when the MCU unit in the vehicle digital key system receives the wake-up signal, the MCU unit will immediately regard the wake-up signal forwarding task as the highest priority. At this time, even if there are other tasks to be processed, the MCU unit will prioritize the execution of the wake-up signal forwarding task and promptly transmit the wake-up signal to the SOC unit.

[0054] Therefore, setting the wake-up signal forwarding task as the highest priority ensures that the wake-up signal can be processed and forwarded quickly. This allows the mobile terminal to instantly obtain the digital key function when approaching the vehicle, reducing waiting time and improving the user experience. Furthermore, priority control effectively manages the resource allocation of the MCU unit, ensuring the rapid execution of critical tasks.

[0055] Step S22: After the wake-up signal forwarding task is completed, the control unit executes the first digital key startup task, wherein the first digital key startup task is used to initialize the communication connection between the control unit and the mobile terminal.

[0056] In this embodiment, after the MCU unit completes the wake-up signal forwarding task, it will control the MCU unit to execute the first digital key startup task. The first digital key startup task is an internal task of the MCU unit used to initialize the communication connection between the MCU unit and the mobile terminal, thereby ensuring secure and efficient data exchange between the MCU unit and the mobile terminal.

[0057] As can be seen, after the MCU unit of this application forwards the wake-up signal to the SOC unit to wake up the task processing environment of the digital key, the MCU unit will execute the first digital key startup task, initialize the communication connection between the MCU unit and the mobile terminal, and establish a safe and reliable channel for subsequent data exchange.

[0058] For example, the first digital key initiation task may include, but is not limited to, the following operations: configuring wireless communication parameters, i.e., determining which wireless communication technology to use (such as BLE or UWB) and performing corresponding signal tuning and parameter settings; setting encryption and security mechanisms, such as Advanced Encryption Standard (AES), public-key encryption algorithms (Rivest-Shamir-Adleman, RSA), and authentication and session management protocols, such as Transport Layer Security (TLS); and verifying the communication channel, i.e., checking the integrity and validity of the communication link to ensure there is no external interference or hardware failure, so as to facilitate reliable data transmission.

[0059] Therefore, by executing the first digital key startup task, an encrypted and secure communication channel can be established between the MCU unit and the mobile terminal, ensuring that all subsequent communications will not be eavesdropped on or tampered with, thus improving the security of the vehicle digital key system.

[0060] Step S23: In response to the on-chip system receiving a wake-up signal, control the on-chip system to execute the second digital key startup task. The second digital key startup task is used to load the software and functional modules corresponding to the digital key task. The second digital key startup task has the highest execution priority among the tasks to be executed in the on-chip system.

[0061] In this embodiment, if the SOC unit receives a wake-up signal, it is controlled to execute the second digital key startup task. The second digital key startup task has the highest execution priority among the SOC unit's pending tasks; that is, the second digital key startup task is the first task executed by the SOC unit after receiving the wake-up signal. Even if the SOC unit receives other task requests simultaneously, the second digital key startup task will be processed first, ensuring a rapid response from the digital key system.

[0062] The second digital key startup task is used to load software and functional modules related to the digital key functionality. For example, the second digital key startup task may include encryption / decryption algorithms, a communication protocol stack, digital key application logic, etc.

[0063] As can be seen, after receiving the wake-up signal, the SOC unit in this application will immediately execute the second digital key startup task to ensure that the digital key application software and functional modules can be quickly loaded into memory to prepare for subsequent digital key business operations.

[0064] Therefore, by setting the execution of the second digital key activation task to the highest priority, the SOC unit can quickly respond to the wake-up signal and immediately enter the working state, effectively shortening the startup time of the vehicle digital key system from dormancy to activation. Furthermore, since the software and functional modules corresponding to the digital key task are loaded in the SOC unit, which possesses powerful computing capabilities and an advanced programming environment, it can fully utilize the SOC's computing resources and improve the execution efficiency of the vehicle digital key system.

[0065] In step S24, in response to the completion of both the first and second digital key startup tasks, the control unit and the on-chip system perform a handshake operation, and after the handshake operation is completed, the digital key task is executed. The digital key task is used to perform access control operations and permission management operations on the vehicle.

[0066] In this embodiment, after both the first and second digital key startup tasks are completed, the MCU unit and the SOC unit are controlled to jointly perform a handshake operation, and the digital key task is executed after the handshake operation is completed. The handshake operation is a communication mechanism used to confirm whether the data transmission link between the MCU unit and the SOC unit is normal; it can be understood as a process of checking and confirming the connection status between the two parties. That is, the handshake operation is used to determine the communication connection status between the control unit and the system-on-a-chip.

[0067] Digital key tasks are used to perform access control and permission management operations on vehicles, such as unlocking doors, starting the vehicle, and sharing permissions.

[0068] Access control is a collaborative process between the MCU and SOC units to verify the identity of the mobile terminal, ensuring the mobile terminal has the right to access the vehicle. Once authentication is successful, the vehicle's digital key system will perform operations such as unlocking or starting the vehicle. If authentication fails, the access request is denied, maintaining the vehicle's security.

[0069] Access control operations involve the MCU unit and SOC unit collaborating to manage digital key permissions, such as setting permission expiration periods and adding or deleting temporary keys. Access control operations ensure the flexibility and security of the vehicle digital key system, allowing users to adjust key access permissions as needed.

[0070] As can be seen, after the first and second digital key startup tasks are completed, this application controls the MCU unit and the SOC unit to perform a two-way handshake to confirm the communication link status and data transmission capability of both parties, ensuring the stability of subsequent communication and the correct transmission of data. After the two-way handshake is completed, the MCU unit and the SOC unit jointly enter the stage of executing digital key tasks. In this stage, the MCU unit and the SOC unit utilize the previously initialized communication connection and loaded software function modules to perform access control operations and permission management operations on the vehicle.

[0071] Therefore, the efficient execution of the first and second digital key activation tasks enables the digital key tasks to be completed quickly, allowing users to use the digital key function without long waiting times, thus improving user experience and satisfaction. Furthermore, through strict access control and permission management, the digital key tasks ensure that only authenticated mobile terminals can unlock or start the vehicle, effectively enhancing vehicle security.

[0072] In summary, this application integrates the core logic processing unit of the digital key task into the SOC unit of the central computing domain platform, eliminating the need for a dedicated security storage (SE) chip. This reduces the number of hardware units, simplifies the architecture of the vehicle digital key system, and lowers costs. Simultaneously, utilizing the computing resources within the SOC unit effectively improves the processing speed and efficiency of the vehicle digital key system. Furthermore, in both the MCU unit and the SOC unit, the digital key task is assigned the highest priority, ensuring that even in a multi-tasking environment, digital key-related tasks are processed first, guaranteeing rapid response and efficient execution.

[0073] In this embodiment, if the control unit receives a wake-up signal from the mobile terminal, it executes a wake-up signal forwarding task. This task forwards the wake-up signal to the on-chip system (OSS) and has the highest execution priority among the control unit's tasks. After the wake-up signal forwarding task is completed, the control unit executes a first digital key startup task, which initializes the communication connection between the control unit and the mobile terminal. Subsequently, if the OSS receives a wake-up signal, it executes a second digital key startup task, which loads the corresponding software and functional modules. This task also has the highest execution priority among the OSS's tasks. Finally, after both the first and second digital key startup tasks are completed, the control unit and OSS perform a handshake operation. After the handshake is completed, the digital key task is executed. This task performs access control and permission management operations on the vehicle, achieving rapid response and efficient processing. This reduces costs and improves performance, thus solving the problems of high cost and limited processing capacity in related vehicle digital key systems.

[0074] In an optional embodiment, in step S21, in response to receiving a wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform a wake-up signal forwarding task, including the following method steps:

[0075] In step S211, in response to the vehicle being powered on, the control unit executes the boot loading procedure.

[0076] Step S212: During the execution of the bootloader, in response to receiving a wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform a wake-up signal forwarding task.

[0077] In this embodiment of the application, when the MCU unit receives a wake-up signal from the mobile terminal and controls the MCU unit to perform a wake-up signal forwarding task, firstly after the vehicle is powered on, the MCU unit is controlled to perform a bootloader operation. During the execution of the bootloader, if the MCU unit receives a wake-up signal from the mobile terminal, the MCU unit is controlled to perform a wake-up signal forwarding task.

[0078] The bootloader is the first program that runs when the MCU unit starts up. It is responsible for initializing hardware devices, setting up the system environment, and loading the operating system or application into memory.

[0079] As can be seen, after the vehicle is powered on, the MCU unit begins executing the bootloader operation, initializing hardware devices such as the Central Processing Unit (CPU), memory, and communication interfaces, preparing for the subsequent loading of the operating system or application. During the bootloader execution, if the MCU unit receives a wake-up signal from the mobile terminal, the MCU unit will immediately interrupt the current bootloader execution and prioritize the wake-up signal forwarding task, thereby ensuring that the digital key system can quickly respond to user needs.

[0080] Therefore, the MCU unit of this application can quickly respond to the wake-up signal and prioritize the execution of digital key tasks by responding to the wake-up signal during the bootloader execution phase, and avoids additional initialization delays, significantly shortening the system's response time from sleep to active state and improving user experience.

[0081] In an optional embodiment, in step S21, in response to receiving a wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform a wake-up signal forwarding task, including the following method steps:

[0082] In step S213, in response to the vehicle being powered on, the control unit executes the boot loading procedure.

[0083] Step S214: In response to the completion of the bootloader operation, the control unit enters the startup mode, wherein the startup mode is used to initialize hardware resources and software resources.

[0084] Step S215: In startup mode, in response to receiving a wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform a wake-up signal forwarding task.

[0085] In this embodiment, when the MCU unit receives a wake-up signal from the mobile terminal and controls the MCU unit to perform a wake-up signal forwarding task, firstly, after the vehicle is powered on, the MCU unit is controlled to execute the Bootloader, and after the Bootloader completes execution, the MCU unit is controlled to enter the startup mode. In the startup mode, if the MCU unit receives a wake-up signal from the mobile terminal, the MCU unit is controlled to perform a wake-up signal forwarding task.

[0086] The boot mode is the mode the MCU unit enters after completing the bootloader. In boot mode, the MCU unit initializes hardware and software resources to prepare for executing digital keys and other functions. For example, in boot mode, the MCU unit initializes hardware such as the CPU, memory, and communication interfaces, as well as loads and configures software such as the operating system, drivers, and applications, making the MCU unit executable.

[0087] As can be seen, after the vehicle is powered on, the MCU unit first executes the Bootloader, which is responsible for initializing the vehicle's basic hardware facilities, such as the CPU, memory, and communication modules, thereby ensuring that the vehicle's basic hardware can start correctly. After the Bootloader finishes executing, the MCU unit enters Boot mode and begins to initialize more detailed hardware and software resources, ensuring that all necessary hardware devices are in normal working order, and then loads the operating system and applications.

[0088] During the boot mode and initialization process of the MCU unit, if a wake-up signal is received from the mobile terminal, the MCU unit will immediately execute the wake-up signal forwarding task, transmitting the wake-up signal to the SOC unit immediately. This ensures that the SOC unit can receive the wake-up signal in a timely manner, quickly respond, and initiate the relevant functions of the digital key. This shortens the delay in the SOC unit's digital key activation, improving the overall system response speed and user experience.

[0089] In an optional embodiment, in step S215, in startup mode, in response to receiving a wake-up signal from the mobile terminal via the control unit, the control unit is controlled to perform a wake-up signal forwarding task, including the following method steps:

[0090] In step S2151, in startup mode, the control unit performs a security authentication operation, wherein the security authentication operation is used to verify the identity of the mobile terminal.

[0091] In step S2152, in response to the completion of the security authentication operation and the receipt of a wake-up signal from the mobile terminal by the control unit, the control unit is controlled to perform the wake-up signal forwarding task.

[0092] In this embodiment of the application, in Boot mode, when the MCU unit receives a wake-up signal from the mobile terminal and controls the MCU unit to perform a wake-up signal forwarding task, it can first control the MCU unit to perform a security authentication operation. After the security authentication operation is completed, if the MCU unit receives a wake-up signal from the mobile terminal, it can control the MCU unit to perform a wake-up signal forwarding task.

[0093] The security authentication operation is used to verify the identity of the mobile terminal that sends the wake-up signal. For example, the security authentication operation typically includes steps such as the execution of encryption algorithms, key exchange, and the execution of authentication protocols to ensure that only authorized mobile devices can wake up the digital key system.

[0094] As can be seen, when the vehicle is powered on and the MCU unit is in Boot mode, the MCU unit can first perform a security authentication operation to verify whether the wake-up signal comes from an authorized mobile terminal, ensuring that only an authenticated mobile terminal can activate the vehicle's digital key system, thereby improving vehicle security.

[0095] After the security authentication process is completed and the verification result is successful, if the MCU unit receives a wake-up signal from the mobile terminal, the MCU unit will execute a wake-up signal forwarding task, forwarding the received wake-up signal to the SOC unit. This ensures that only wake-up signals that have passed security authentication are forwarded to the SOC unit, further enhancing the security of the vehicle digital key system.

[0096] In an optional embodiment, the method further includes the following method steps:

[0097] In step S2153, in startup mode, the control unit performs a security authentication operation, wherein the security authentication operation is used to verify the identity of the mobile terminal.

[0098] In this embodiment of the application, the security authentication operation can also be performed after the MCU unit performs the wake-up signal forwarding task. That is, in the startup mode, if the MCU unit first receives the wake-up signal from the mobile terminal, then the MCU unit is controlled to perform the wake-up signal forwarding task, and then the MCU unit is controlled to perform the security authentication operation.

[0099] Therefore, by performing the wake-up signal forwarding task before security authentication, the waiting time is reduced. The SOC unit can immediately begin the digital key-related startup tasks without waiting for the entire operating system to fully boot, which helps improve the overall startup efficiency and response speed of the vehicle's digital key system. This advantage in response speed is particularly pronounced in emergency situations.

[0100] In an optional embodiment, in step S21, in response to receiving a wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform a wake-up signal forwarding task, including the following method steps:

[0101] Step S216: In response to the control unit exiting the startup mode, the control unit is controlled to enter the application mode, wherein the application mode is used to start and run the application.

[0102] Step S217: Within a preset time period of the application mode, in response to receiving a wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform a wake-up signal forwarding task. The preset time period is used to represent the time period between the first moment when the control unit enters the application mode and the second moment, where the second moment is later than the first moment.

[0103] In this embodiment, when the MCU unit receives a wake-up signal from the mobile terminal and controls the MCU unit to perform a wake-up signal forwarding task, if the MCU unit exits Boot mode, it is controlled to enter application mode. Within a preset time period in application mode, if the MCU unit receives a wake-up signal from the mobile terminal, it is controlled to perform a wake-up signal forwarding task.

[0104] The application mode (APP mode) is used to launch and run applications. The MCU unit launches and runs various applications in APP mode, including digital key applications.

[0105] The preset time period is a predetermined period of time within the APP mode. Specifically, the preset time period represents the time between the first moment when the MCU unit enters APP mode and the second moment, where the second moment is later than the first moment. The first moment is the moment when the MCU unit enters APP mode, and the second moment can be 1 second after the first moment; there is no restriction here. In other words, the preset time period is the very initial moment when the MCU unit enters APP mode.

[0106] As can be seen, after the MCU unit completes all initialization operations for the Bootloader and Boot mode, the MCU unit will enter APP mode. If the MCU unit receives a wake-up signal at the initial moment of entering APP mode, the MCU unit will execute the wake-up signal forwarding task.

[0107] Therefore, during the initial startup phase of the APP mode, resources are relatively idle. Executing the wake-up signal forwarding task at this time avoids competition with other applications, ensures the priority of wake-up signal processing, and thus quickly wakes up the SOC unit and starts the digital key service. Furthermore, by prioritizing wake-up signal processing, the SOC unit can quickly enter the working state, reducing waiting time and unnecessary resource consumption.

[0108] In an optional embodiment, in step S23, in response to the on-chip system receiving a wake-up signal, the on-chip system is controlled to execute a second digital key startup task, including the following method steps:

[0109] Step S231: In response to the on-chip system receiving a wake-up signal, control the on-chip system to perform a wake-up process that reduces startup time.

[0110] Step S232: During the on-chip system's wake-up process of reducing startup time, control the on-chip system to execute the second digital key startup task.

[0111] In this embodiment of the application, if the SOC unit receives a wake-up signal and controls the SOC unit to execute the second digital key startup task, it can first control the on-chip system to execute the startup time reduction wake-up process, and then control the SOC unit to execute the second digital key startup task during the startup time reduction wake-up process.

[0112] The Start-up Time Reduction (STR) wake-up process is a series of optimization measures performed by the SOC unit after receiving the wake-up signal to shorten the time from sleep state to full startup and improve response speed.

[0113] It can be seen that if the SOC unit receives a wake-up signal, the control SOC unit immediately executes a series of wake-up processes designed to reduce startup time, namely the STR wake-up process, to ensure that the SOC unit can quickly switch from low-power mode to high-performance mode, thereby quickly responding to the startup requirements of the digital key function.

[0114] Then, while the SOC unit executes the STR wake-up process, it simultaneously begins executing the second digital key startup task. This ensures that while the SOC unit can quickly enter a working state, the core functions of the digital key can also be seamlessly activated. Thus, the parallel processing of the SOC unit fully utilizes its multi-core computing capabilities, improving the overall efficiency of the system.

[0115] In an optional embodiment, in step S24, in response to the completion of both the first digital key startup task and the second digital key startup task, the control unit and the on-chip system execute the digital key task, including the following method steps:

[0116] In step S241, in response to the completion of both the first digital key startup task and the second digital key startup task, the control unit and the system on chip perform a handshake operation, wherein the handshake operation is used to determine the communication connection status between the control unit and the system on chip.

[0117] In step S242, in response to the completion of the handshake operation, the control unit and the on-chip system perform a signature verification operation to obtain a verification result. The signature verification operation is used to verify the integrity of the communication data.

[0118] In step S243, in response to the verification result indicating that the verification has passed, the control unit and the on-chip system execute the digital key task.

[0119] In this embodiment of the application, if both the first digital key startup task and the second digital key startup task are completed, when controlling the MCU unit and the SOC unit to execute the digital key task, the MCU unit and the SOC unit can first be controlled to perform a handshake operation, and then the MCU unit and the SOC unit can be controlled to perform a signature verification operation to obtain the verification result. After the verification is passed, the MCU unit and the SOC unit can then be controlled to execute the digital key task.

[0120] The signature verification operation is the process of verifying digital signatures to ensure the integrity of data during transmission and prevent data from being tampered with or impersonated. In other words, the signature verification operation is used to verify the integrity of communication data.

[0121] As can be seen, after the first digital key startup task of the MCU unit and the second digital key startup task of the SOC unit are completed, the MCU unit and the SOC unit will first perform a handshake operation to confirm the communication link status and data transmission capability of both parties, so as to ensure the stability of subsequent communication and the correct transmission of data.

[0122] Once the handshake operation is complete, the MCU unit and the SOC unit will perform a signature verification operation to verify the digital signature of the communication data, ensuring that the data has not been tampered with during transmission and maintaining data integrity and security.

[0123] Subsequently, if the verification result indicates that the data has passed the integrity check, the MCU unit and SOC unit will begin executing digital key tasks, including but not limited to unlocking the vehicle, starting the engine, and sharing permissions. Thus, through security authentication, handshake, and data integrity verification, the security and reliability of executing digital key tasks are ensured, providing users with a secure and reliable vehicle unlocking and control environment.

[0124] In summary, this application provides a performance optimization method for vehicle digital keys implemented based on a central domain computing platform (SOC) unit. While vehicle digital key systems based on embedded SOC systems possess powerful computing capabilities, their response speed is relatively slow. This application provides a performance optimization method that enables embedded SOC systems to achieve rapid startup and response, allowing vehicle digital key onboard terminal systems based on SOC units to also meet the rapid startup requirements of digital keys.

[0125] Figure 3 This is a flowchart illustrating another vehicle digital key task processing method according to an embodiment of this application, such as... Figure 3 As shown, it includes the following steps:

[0126] S31: The MCU receives a wake-up signal from the mobile terminal (from Bluetooth or near field communication).

[0127] S32: The MCU treats this wake-up signal as a highest priority task and processes it accordingly. Immediately after power-on, the MCU sends the wake-up signal to the SOC to wake it up. For example, the MCU executes the SOC wake-up task via a hard-wired pulse signal during the bootloader startup phase. Alternatively, the MCU executes the SOC wake-up task at the very beginning of the APP startup phase.

[0128] S33: After that, the MCU continues to load the remaining APP functions normally and transmits the specific configuration or status signals associated with the digital key function to the SOC through the serial port, that is, using a dedicated message to notify the SOC to start the system.

[0129] S34: After receiving the wake-up signal, the SOC begins executing the STR wake-up process and then executes the startup program for the digital key task.

[0130] S35: During the wake-up process, the SOC recognizes this event as a digital key task and processes it as the highest priority, that is, the SOC prioritizes loading the digital key task.

[0131] S36: The MCU and SOC execute the relevant startup tasks in parallel. After the startup is completed almost synchronously, the MCU and SOC handshake each other to confirm that both are ready.

[0132] S37: The MCU and SOC begin exchanging data for the digital key task, performing the two-way key task signing (encrypted signature) and verification (signature verification) process, that is, the MCU and SOC synchronize key information and load the remaining tasks.

[0133] S38: At this point, the digital key task has been successfully started and is working normally.

[0134] Figure 4 This is a schematic diagram of a vehicle digital key system according to an embodiment of this application, as shown below. Figure 4 As shown, Figure 4 It includes a central domain computing platform, a digital key cloud platform server, a vehicle domain control platform, a BLE module, a UWB module, and an NFC module.

[0135] The central domain computing platform is the central processing unit of the vehicle digital key system. It includes a System-on-Chip (SOC) unit and a Microcontroller Unit (MCU) unit. The SOC unit and the MCU unit communicate via a serial port.

[0136] As a high-performance computing center, the SOC unit is responsible for handling more complex computing tasks and adopts general-purpose TEE secure storage technology. The SOC unit includes three virtual subsystems: the driving domain, the entertainment domain, and the connectivity domain, which respectively represent the vehicle's driving assistance functions, entertainment system, and network connectivity functions.

[0137] The driving domain primarily handles functions directly related to driving safety, vehicle control, and powertrain management, such as the Anti-lock Braking System (ABS), Electronic Stability Program (ESP), and engine control.

[0138] The entertainment domain is responsible for functions related to passenger comfort and entertainment needs, such as media playback, navigation, and infotainment systems.

[0139] The connected domain is responsible for handling the vehicle's connection and communication with external networks, including Wireless Fidelity (Wi-Fi), Bluetooth, cellular network connections, as well as services such as vehicle information updates, remote control, and data uploads via the network.

[0140] This application places the digital key function in the network domain for processing, that is, the vehicle digital key system is arranged to run in the network domain part of the SOC unit, which enables the vehicle digital key system to exchange data with mobile terminals more efficiently, and also facilitates synchronization and authentication with the cloud platform.

[0141] The MCU unit is the control center of the digital key system. The MCU unit in this application does not need to be equipped with a dedicated security SE, thereby reducing costs.

[0142] The digital key cloud platform server communicates bidirectionally with the network domain subsystem within the SOC unit via the HTTPS protocol, and is responsible for the authentication, distribution and management of digital keys.

[0143] The vehicle body domain control platform, comprising UWB and NFC modules, acts as the actuator for vehicle control, performing operations such as unlocking and starting the vehicle according to instructions from the central domain computing platform. The UWB and NFC modules are responsible for ultra-wideband communication and short-range communication, respectively. The UWB and NFC modules interact with the vehicle body domain control platform and exchange data with the central domain computing platform via the CAN FD bus.

[0144] The BLE module is responsible for Bluetooth communication with the mobile terminal, and bidirectional data transmission between the BLE module and the MCU unit of the central domain computing platform is carried out via the CAN bus.

[0145] In other words, this application places the core logic processing unit of the digital key (the digital key tearing APP) within the complex operating system SOC unit of the central computing platform. This saves the use of dedicated security storage (SE) chips and maximizes the powerful computing capabilities of the SOC chip, providing more computing power reserves for future key function upgrades. Complex operating system SOC units typically employ high-level general-purpose programming environments such as C++, resulting in simple software deployment, high efficiency, and rapid function updates and iterations.

[0146] Figure 5 This is a comparative schematic diagram of one solution according to an embodiment of this application. Figure 5 The diagram illustrates the execution flow of a traditional solution. After vehicle ignition is turned on (IG ON), the MCU enters the boot phase, typically involving hardware initialization and loading the bootloader, which takes approximately 80 milliseconds. After the bootloader is loaded, the MCU begins loading the main application (APPmain), which takes approximately 80 milliseconds. Following the main application loading, the MCU sends the first frame of Network Management (NM) data for network initialization and other operations, taking approximately 100 milliseconds. Finally, the MCU opens the serial port and sends a wake-up signal to wake up the SOC.

[0147] Figure 5 The document also illustrates Scheme 1 of this application, which places the wake-up signal forwarding task in the initial stage of the MCU APP main program. Specifically, when the vehicle IG ON, the MCU starts from Boot mode and then begins loading the APP main. At the very beginning of the APP main stage, the MCU sends a wake-up signal to the SOC through a predetermined protocol or mechanism. After waking up the SOC, the MCU further opens the serial communication interface (serial port) to establish a communication connection with the SOC for data exchange and synchronization. Thus, this application moves the SOC wake-up task forward to the MCU's APP main loading stage, allowing the SOC wake-up and the MCU's APP main loading to proceed in parallel, shortening the time interval for the digital key function to be ready.

[0148] Figure 5The document also illustrates schemes 2 and 3 of this application, which place the wake-up signal forwarding task during the Boot phase. Specifically, in scheme 2, the wake-up signal forwarding task is executed before the security authentication during the Boot phase, running in parallel with the MCU's regular startup process, thus improving the response speed of the digital key system. In scheme 3, the wake-up signal forwarding task is executed after the security authentication during the Boot phase. This pre-authentication of security ensures that the SOC is only activated after the security environment is confirmed, which not only improves security but also avoids unnecessary SOC wake-ups and extends the SOC's lifespan.

[0149] In summary, this application can be implemented based on a complex and general-purpose operating system for digital key tasks and its fast startup performance optimization method. In addition, it can also be implemented using other hardware chips.

[0150] The core wake-up strategy of this application lies in the wake-up task on the MCU front-end SOC side, in order to improve the startup time of the entire system. This includes placing the wake-up task in the initial stage of the MCU APP main program, or placing the wake-up task in the Boot stage (including before or after security authentication).

[0151] The SOC system of this application virtualizes three virtual task systems: driving domain, connectivity domain, and entertainment domain. This application places the digital key task in the connectivity domain for processing. Alternatively, the digital key task can also be placed in the driving domain and entertainment domain.

[0152] In other words, this application proposes a digital key system based on a central computing platform. This application implements the digital key task in a general-purpose complex operating system, which has the advantages of easy development and maintenance and low cost (saving the dedicated SE chip on the MCU side).

[0153] This application proposes a method to optimize the fast startup performance of digital key tasks. By using a pre-wake signal on the MCU side, the key tasks of the MCU and SOC are loaded in parallel and the task handshake is completed synchronously. This improves the fast startup performance of the key tasks of the entire central computing platform, meets the user's performance requirements for fast unlocking of digital key tasks, and reduces the startup time of the key system from 1.5 seconds to 800 milliseconds. This allows the startup performance requirements to be met based on a complex general-purpose operating system hardware platform.

[0154] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0155] According to an embodiment of this application, a vehicle digital key system is provided. It should be noted that this system can be used to execute the above-described vehicle digital key task processing method.

[0156] Figure 6 This is a structural block diagram of a vehicle digital key system according to an embodiment of this application, such as... Figure 6 As shown, the vehicle digital key system includes at least a control unit and a system-on-a-chip (SoC). The SoC includes a driving domain, an entertainment domain, and a connectivity domain. The connectivity domain is used to perform digital key functions, and the vehicle digital key system is used to perform the aforementioned vehicle digital key task processing method.

[0157] For a detailed description, please refer to the description of the foregoing embodiments, which will not be repeated here.

[0158] According to an embodiment of this application, an apparatus embodiment for a vehicle digital key task processing method is provided. It should be noted that the apparatus can be used to execute the above-described vehicle digital key task processing method.

[0159] Figure 7 This is a structural block diagram of a vehicle digital key task processing device according to one embodiment of the present application. The device is applied to a vehicle digital key system in a vehicle. The vehicle digital key system includes a control unit and a system-on-a-chip, such as... Figure 7 As shown, the vehicle digital key task processing device 700 includes: a first control module 701, used to control the control unit to execute a wake-up signal forwarding task in response to receiving a wake-up signal from a mobile terminal through the control unit, wherein the wake-up signal forwarding task is used to forward the wake-up signal to the on-chip system, and the wake-up signal forwarding task has the highest execution priority among the tasks to be executed by the control unit; a second control module 702, used to control the control unit to execute a first digital key startup task after the wake-up signal forwarding task is completed, wherein the first digital key startup task is used to initialize the communication connection between the control unit and the mobile terminal; a third control module 703, used to control the on-chip system to execute a second digital key startup task in response to receiving a wake-up signal, wherein the second digital key startup task is used to load the software and functional modules corresponding to the digital key task, and the second digital key startup task has the highest execution priority among the tasks to be executed by the on-chip system; and a fourth control module 704, used to control the control unit and the on-chip system to perform a handshake operation in response to the completion of both the first and second digital key startup tasks, and to execute a digital key task after the handshake operation is completed, wherein the digital key task is used to perform access control operations and permission management operations on the vehicle.

[0160] Embodiments of this application also provide a vehicle, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods described in various embodiments of this application when it runs.

[0161] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0162] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0163] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the methods in various embodiments of this application.

[0164] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0165] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0166] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0167] Furthermore, the functional units in the various embodiments of this application 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 integrated unit can be implemented in hardware or as a software functional unit.

[0168] If the integrated unit is implemented as 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 technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0169] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for processing vehicle digital key tasks, characterized in that, A vehicle digital key system applied in a vehicle, the vehicle digital key system including a control unit and a system-on-a-chip, the method comprising: In response to receiving a wake-up signal from a mobile terminal through the control unit, the control unit is controlled to execute a wake-up signal forwarding task, wherein the wake-up signal forwarding task is used to forward the wake-up signal to the on-chip system, and the wake-up signal forwarding task has the highest execution priority among the tasks to be executed by the control unit; After the wake-up signal forwarding task is completed, the control unit is controlled to execute the first digital key startup task, wherein the first digital key startup task is used to initialize the communication connection between the control unit and the mobile terminal; In response to the system-on-a-chip receiving the wake-up signal, the system-on-a-chip is controlled to execute the second digital key startup task, wherein the second digital key startup task is used to load the software and functional modules corresponding to the digital key task, and the second digital key startup task has the highest execution priority among the tasks to be executed in the system-on-a-chip. In response to the completion of both the first digital key startup task and the second digital key startup task, the control unit and the on-chip system are controlled to perform a handshake operation, and the digital key task is executed after the handshake operation is completed. The digital key task is used to perform access control operation and permission management operation on the vehicle.

2. The method according to claim 1, characterized in that, The step of controlling the control unit to perform a wake-up signal forwarding task in response to receiving a wake-up signal from the mobile terminal via the control unit includes: In response to the vehicle being powered on, the control unit is controlled to execute the boot loading procedure. During the execution of the bootloader, in response to receiving the wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform the wake-up signal forwarding task.

3. The method according to claim 1, characterized in that, The step of controlling the control unit to perform a wake-up signal forwarding task in response to receiving a wake-up signal from the mobile terminal via the control unit includes: In response to the vehicle being powered on, the control unit is controlled to execute the boot loading procedure. In response to the completion of the bootloader operation, the control unit is controlled to enter the startup mode, wherein the startup mode is used to initialize hardware resources and software resources; In the startup mode, in response to receiving the wake-up signal from the mobile terminal through the control unit, the control unit is controlled to perform the wake-up signal forwarding task.

4. The method according to claim 3, characterized in that, In the startup mode, in response to receiving the wake-up signal from the mobile terminal through the control unit, controlling the control unit to perform the wake-up signal forwarding task includes: In the startup mode, the control unit is controlled to perform a security authentication operation, wherein the security authentication operation is used to verify the identity of the mobile terminal; In response to the completion of the security authentication operation and the receipt of the wake-up signal from the mobile terminal by the control unit, the control unit is controlled to execute the wake-up signal forwarding task.

5. The method according to claim 3, characterized in that, The method further includes: In the startup mode, the control unit is controlled to perform a security authentication operation, wherein the security authentication operation is used to verify the identity of the mobile terminal.

6. The method according to claim 1, characterized in that, The step of controlling the control unit to perform a wake-up signal forwarding task in response to receiving a wake-up signal from the mobile terminal via the control unit includes: In response to the control unit exiting the startup mode, the control unit is controlled to enter the application mode, wherein the application mode is used to start and run the application. Within a preset time period of the application mode, in response to receiving the wake-up signal from the mobile terminal through the control unit, the control unit is controlled to execute the wake-up signal forwarding task, wherein the preset time period is used to represent the time period from the first moment when the control unit enters the application mode to the second moment, and the second moment is later than the first moment.

7. The method according to claim 1, characterized in that, The step of controlling the on-chip system to execute the second digital key startup task in response to the on-chip system receiving the wake-up signal includes: In response to the on-chip system receiving the wake-up signal, the on-chip system is controlled to perform a wake-up process that reduces startup time; During the startup time reduction wake-up process performed by the on-chip system, the on-chip system is controlled to perform the second digital key startup task.

8. The method according to any one of claims 1-7, characterized in that, The step of controlling the control unit and the system-on-a-chip to perform a handshake operation in response to the completion of both the first digital key startup task and the second digital key startup task, and executing the digital key task after the handshake operation is completed, includes: In response to the completion of both the first digital key startup task and the second digital key startup task, the control unit and the system on chip are controlled to perform the handshake operation, wherein the handshake operation is used to determine the communication connection status between the control unit and the system on chip; In response to the completion of the handshake operation, the control unit and the system on chip are controlled to perform a signature verification operation to obtain a verification result, wherein the signature verification operation is used to verify the integrity of the communication data; In response to the verification result indicating that the verification passed, the control unit and the system-on-a-chip are controlled to execute the digital key task.

9. A vehicle digital key system, characterized in that, The vehicle digital key system includes at least a control unit and a system-on-a-chip (SoC), wherein the SoC includes a driving domain, an entertainment domain, and a connectivity domain, the connectivity domain is used to perform digital key functions, and the vehicle digital key system is used to perform the vehicle digital key task processing method as described in any one of claims 1 to 8.

10. A vehicle, characterized in that, include: Memory, which stores executable programs; A processor for running the executable program, wherein the executable program, when running on the processor, performs the vehicle digital key task processing method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the vehicle digital key task processing method as described in any one of claims 1 to 8 when run on a computer or processor.

Images