Shared key distribution method and device, vehicle, equipment and storage medium

Abstract

The invention discloses a shared key distribution method and device, a vehicle, equipment and a storage medium. The method comprises the following steps: at an updating moment, generating a latest shared key and storing the latest shared key in a storage area; determining a target controller passing the identity authentication; obtaining a latest shared key and a shared key generated last time from the storage area; encrypting the latest shared key by using the shared key generated last time to obtain an encrypted key; and sending the encryption key to the target controller. According to the method and the device, the shared key is dynamically updated, so that the risk that the shared key is leaked or cracked can be reduced, and potential security threats are reduced; and the shared key distribution end completes the actions of generating, storing and distributing the shared key, and for the target controller which needs to use the shared key and passes the identity authentication in the vehicle, the system does not need to have very strong safety protection capability, so that the cost of the controller can be effectively reduced, and adverse effects on the functions of the controller cannot be caused.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a shared key distribution method, apparatus, vehicle, equipment and computer-readable storage medium. Background Art

[0002] For communication between controllers in the vehicle, each controller needs to use a shared key to encrypt the communication information before transmitting it to the other controller. The shared key needs to be pre-written into the storage area of ​​each controller. To improve the security of the shared key, each controller needs to have security protection capabilities to prevent the shared key from being leaked. This will increase costs and affect other functions of the controller. Summary of the invention

[0003] The present application provides a shared key distribution method, apparatus, vehicle, equipment and computer-readable storage medium, which can solve the technical problems existing in the prior art that each controller performs security protection on the shared key, resulting in high cost and affected controller functions.

[0004] In a first aspect, an embodiment of the present application provides a shared key distribution method, the shared key distribution method comprising:

[0005] When it is time to update, generate the latest shared key and store it in the storage area;

[0006] Determine the target controller that has passed the identity authentication;

[0007] Get the latest shared key and the last generated shared key from the storage area;

[0008] Use the shared key generated last time to encrypt the latest shared key to obtain an encryption key;

[0009] Send the encryption key to the target controller.

[0010] In combination with the first aspect, in one implementation, when at the update time, generating the latest shared key and storing it in the storage area includes:

[0011] When the update time comes, the vehicle identification information and the time information corresponding to the update time are obtained;

[0012] The latest shared key is generated based on the vehicle identification information and time information through a key generation algorithm and stored in a storage area.

[0013] In combination with the first aspect, in one implementation, determining the target controller that has passed the identity authentication includes:

[0014] receiving an identity authentication value sent by the controller, wherein the identity authentication value is sent by the controller when waking up from a dormant state;

[0015] Detecting whether the identity authentication value is a valid identity authentication value;

[0016] If the identity authentication value is a valid identity authentication value, the controller sending the identity authentication value is determined to be the target controller.

[0017] In combination with the first aspect, in one implementation, determining the target controller that has passed the identity authentication includes:

[0018] Send authentication requests to each controller;

[0019] Based on the feedback of each controller to the identity authentication request, the target controller that passes the identity authentication is determined.

[0020] In combination with the first aspect, in one implementation, after the encryption processing is performed on the latest shared key using the last generated key to obtain the encryption key, the method further includes:

[0021] Determine key identification information of the latest shared key;

[0022] Send the encryption key and key identification information to the target controller.

[0023] In combination with the first aspect, in one implementation, adjacent update moments are separated by a first preset time length, and after the encryption key and the key identification information are sent to the target controller, the method further includes:

[0024] Sending key identification information to the target controller every second preset time period within the first preset time period;

[0025] When receiving a key sending request sent by the target controller, the encryption key and key identification information are sent to the target controller. The key sending request is sent by the target controller when it detects that the key identification information received last time is inconsistent with the key identification information received when the encryption key is received.

[0026] In a second aspect, an embodiment of the present application provides a shared key distribution device, the shared key distribution device comprising:

[0027] An update module, used to generate the latest shared key and store it in the storage area when it is at the update moment;

[0028] Authentication module, used to determine the target controller that has passed the identity authentication;

[0029] An acquisition module, used for acquiring the latest shared key and the last generated shared key from the storage area;

[0030] The encryption module is used to encrypt the latest shared key using the shared key generated last time to obtain an encryption key;

[0031] The sending module is used to send the encryption key to the target controller.

[0032] In a third aspect, an embodiment of the present application provides a vehicle, comprising the shared key distribution device as described in the second aspect.

[0033] In a fourth aspect, an embodiment of the present application provides a shared key distribution device, comprising a processor, a memory, and a shared key distribution program stored on the memory and executable by the processor, wherein when the shared key distribution program is executed by the processor, the steps of the shared key distribution method described in the first aspect are implemented.

[0034] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a shared key distribution program is stored, wherein when the shared key distribution program is executed by a processor, the steps of the shared key distribution method described in the first aspect are implemented.

[0035] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0036] In this embodiment, when it is at the update moment, the latest shared key is generated and stored in the storage area; the target controller that has passed the identity authentication is determined; the latest shared key and the last generated shared key are obtained from the storage area; the latest shared key is encrypted using the last generated shared key to obtain an encryption key; and the encryption key is sent to the target controller. Through the embodiment of the present application, the shared key is dynamically updated, which can reduce the risk of the shared key being leaked or cracked, and reduce potential security threats; and the shared key distribution end completes the generation of the shared key, storage of the shared key, and distribution of the shared key. For the target controller in the car that needs to use the shared key and has passed the identity authentication, it does not need to have a strong security protection capability, which can effectively reduce the controller cost and will not have an adverse effect on the controller function. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 This is a flow chart of an embodiment of a shared key distribution method of the present application;

[0038] Figure 2 A flowchart of another embodiment of the shared key distribution method of the present application;

[0039] Figure 3 This is a functional module diagram of an embodiment of a shared key distribution device of the present application;

[0040] Figure 4 This is a schematic diagram of the hardware structure of the shared key distribution device involved in the embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0043] In a first aspect, an embodiment of the present application provides a shared key distribution method.

[0044] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of an embodiment of a method for distributing shared keys in this application. Figure 1 As shown, the shared key distribution method includes:

[0045] Step S10, when it is at the update time, generate the latest shared key and store it in the storage area;

[0046] In this embodiment, the execution subject of the shared key distribution method is the key distribution terminal. When the key distribution terminal detects that the current moment is the update moment, it generates the latest shared key and stores it in the storage area. The update moment is set according to actual needs. For example, every first preset time after the key distribution terminal is powered on is an update moment. Taking the first preset time as 1 hour as an example, the power-on moment of the key distribution terminal is t0, then t0 is the update moment; t1 is reached after 1 hour from t0, and t1 is the update moment; t2 is reached after 1 hour from t1, and t2 is the update moment, and so on.

[0047] The process of generating the latest shared key includes:

[0048] A secure random number generator is used to generate a random number, and the random number is used as the latest shared key, or the random number is further processed with entropy increase, and the result of the entropy increase processing is used as the latest shared key.

[0049] Further, in one embodiment, when at the update time, generating the latest shared key and storing it in the storage area includes:

[0050] When it is at the update time, the vehicle identification information and the time information corresponding to the update time are obtained; based on the vehicle identification information and the time information, the latest shared key is generated by the key generation algorithm and stored in the storage area.

[0051] In this embodiment, the vehicle identification information may be one or more of a vehicle identification number, a license plate number, a vehicle registration number, a vehicle type identification code, and a unique identification number of the vehicle engine. Each vehicle has a unique vehicle identification number VIN, which is usually composed of 17 characters, including letters and numbers, and is used to identify the manufacturer, brand, model, year, and other information of the vehicle. The license plate number, which is usually composed of letters and numbers, identifies the registration status and region of the vehicle. The vehicle type identification code is used to describe the type of vehicle, such as a sedan, SUV, truck, motorcycle, etc. The unique identification number of the vehicle engine is used to identify the model and production information of the engine.

[0052] It should be noted that this is only a schematic description of the vehicle identification information and does not constitute a limitation on the vehicle identification information. The vehicle identification information can be selected according to actual needs.

[0053] The time information corresponding to the update time may be the value of the timer at the update time, or the time clock information corresponding to the update time.

[0054] It is easy to understand that each time the latest shared key is generated by the key generation algorithm based on the vehicle identification information and time information, where the vehicle identification information can be fixed, but the time information is variable, that is, the calculation parameters used to generate the latest shared key are variable, then it can be ensured that the shared key obtained each time is different, where the latest shared key refers to the shared key obtained by the latest calculation.

[0055] Of course, referring to the above five examples of vehicle identification information, one of them can be obtained as the vehicle identification information in a polling manner. For example, when it is at the update time t0, the vehicle identification number and the time information T0 corresponding to the update time t0 are obtained, and the latest shared key is generated based on the vehicle identification number and T0 through the key generation algorithm and stored in the storage area; when it is at the update time t1, the license plate number and the time information T1 corresponding to the update time t1 are obtained, and the latest shared key is generated based on the license plate number and T1 through the key generation algorithm and stored in the storage area; when it is at the update time t2, the vehicle registration number and the time information T2 corresponding to the update time t2 are obtained, and the latest shared key is generated based on the vehicle registration number and T2 through the key generation algorithm and stored in the storage area; when it is at the update time t3, the vehicle type identification code and the time information T3 corresponding to the update time t3 are obtained, and the latest shared key is generated based on the vehicle type identification code and T3 through the key generation algorithm and stored in the storage area; when it is at the update time t4, the unique identification number of the vehicle engine and the time information T4 corresponding to the update time t4 are obtained, and the latest shared key is generated based on the unique identification number of the vehicle engine and T4 through the key generation algorithm and stored in the storage area.

[0056] It can be seen that each time a shared key is generated, the vehicle identification information used is changed, and the time information is also changed, that is, the calculation parameters used to generate the latest shared key are changed, which can ensure that the shared key obtained each time is different, where the latest shared key refers to the shared key obtained by the latest calculation.

[0057] Step S20, determining the target controller that has passed the identity authentication;

[0058] In this embodiment, assuming that there are 20 controllers in the car, these 20 controllers need to be authenticated first, and the controllers that pass the authentication are determined. For example, if controller 3 and controller 7 pass the authentication, controller 3 and controller 7 are used as target controllers.

[0059] Furthermore, in one embodiment, step S20 includes:

[0060] Send an authentication request to each controller; based on the feedback of each controller on the authentication request, determine the target controller that passes the authentication.

[0061] In this embodiment, the execution subject of this embodiment actively sends an identity authentication request to each controller, for example, sends an identity authentication request to controllers 1 to 20.

[0062] For each controller, if it can normally receive and parse the identity authentication request, it will send the identity authentication value of the local end to the execution subject of this embodiment.

[0063] For example, controller 3, controller 7 and controller 19 receive and parse the authentication request normally, and send the authentication value 3, authentication value 7 and authentication value 19 to the execution subject of this embodiment respectively. Other controllers cannot receive and parse the authentication request normally due to sleep or communication abnormalities. For the execution subject of this embodiment, the feedback of other controllers is empty.

[0064] In the execution subject end of the present embodiment, a valid identity authentication value list is stored, and valid identity authentication values ​​are recorded in the identity authentication value list. After receiving the identity authentication value 3, the identity authentication value 7, and the identity authentication value 19, it is detected whether the identity authentication value 3, the identity authentication value 7, and the identity authentication value 19 are recorded in the valid identity authentication value list. If the identity authentication value 3 and the identity authentication value 7 are recorded in the valid identity authentication value list, and the identity authentication value 19 is not recorded in the valid identity authentication value list, it is determined that the target controllers that have passed the identity authentication are controllers 3 and 7.

[0065] Furthermore, in one embodiment, step S20 includes:

[0066] Receive an identity authentication value sent by a controller, the identity authentication value is sent by the controller when waking up from a dormant state; detect whether the identity authentication value is a valid identity authentication value; if the identity authentication value is a valid identity authentication value, determine that the controller sending the identity authentication value is a target controller.

[0067] In this embodiment, considering that when the execution subject of this embodiment sends an identity authentication request, some controllers are in a dormant state and cannot provide feedback for the identity authentication request, each controller is set to send an identity authentication value to the execution subject of this embodiment when it wakes up from a dormant state. After the execution subject of this embodiment receives the identity authentication value sent by the controller, it detects whether the received identity authentication value is recorded in the valid identity authentication value list. If the identity authentication value is recorded in the valid identity authentication value list, it is determined that the controller sending the identity authentication value is the target controller that has passed the identity authentication.

[0068] Step S30, obtaining the latest shared key and the last generated shared key from the storage area;

[0069] Step S40, using the shared key generated last time to encrypt the latest shared key to obtain an encryption key;

[0070] Step S50: sending the encryption key to the target controller.

[0071] In this embodiment, determining the target controller is to determine the distribution object of the shared key. In order to further ensure the security of the shared key during the distribution process, the latest shared key and the last generated shared key are obtained from the storage area, and the latest shared key is encrypted using the last generated shared key to obtain the encryption key, which is then sent to the target controller.

[0072] In this embodiment, when it is at the update moment, the latest shared key is generated and stored in the storage area; the target controller that has passed the identity authentication is determined; the latest shared key and the last generated shared key are obtained from the storage area; the latest shared key is encrypted using the last generated shared key to obtain an encryption key; and the encryption key is sent to the target controller. Through the embodiment of the present application, the shared key is dynamically updated, which can reduce the risk of the shared key being leaked or cracked, and reduce potential security threats; and the shared key distribution end completes the generation of the shared key, storage of the shared key, and distribution of the shared key. For the target controller in the car that needs to use the shared key and has passed the identity authentication, it does not need to have a strong security protection capability, which can effectively reduce the controller cost and will not have an adverse effect on the controller function.

[0073] Further, in one embodiment, referring to Figure 2 , Figure 2 This is a flow chart of another embodiment of the shared key distribution method of the present application. Figure 2 As shown, after step S40, the following further includes:

[0074] Step S60, determining the key identification information of the latest shared key;

[0075] Step S70: Send the encryption key and key identification information to the target controller.

[0076] In this embodiment, when the shared key is generated for the first time during the process of powering on and off the vehicle, its key identification information is 1, and each time a new shared key is generated, the key identification information is increased by 1, so as to determine the key identification information of the newest shared key. Alternatively, the newest shared key is hashed and the hashed result is used as the key identification information of the newest shared key.

[0077] After determining the key identification information of the latest shared key, the encryption key and the key identification information are sent to the target controller. It is easy to understand that the encryption key and the key identification information need to be sent to the target controller in a message format composed of a specific communication protocol. If the reserved field in the message header of the message is sufficient to carry the key identification information, the key identification information is encapsulated in the reserved field of the message header, and the encryption key is encapsulated in the payload part of the message; if the reserved field in the message header of the message is insufficient to carry the key identification information, the key identification information and the encryption key are encapsulated together in the payload part of the message.

[0078] Furthermore, in one embodiment, the interval between adjacent update moments is a first preset time length, and after step S70, the method further includes:

[0079] Sending key identification information to the target controller every second preset time period within the first preset time period;

[0080] When receiving a key sending request sent by the target controller, the encryption key and key identification information are sent to the target controller. The key sending request is sent by the target controller when it detects that the key identification information received last time is inconsistent with the key identification information received when the encryption key is received.

[0081] In this embodiment, assuming that the first preset time is 1 hour and the second preset time is 10 minutes, sending key identification information to the target controller every 10 minutes can maintain the activity of the communication connection between the execution subject of this embodiment and the target controller and prevent the communication connection from being interrupted due to long-term inactivity.

[0082] In addition, the key identification information sent by the execution subject of this embodiment is used to identify the latest shared key; for the target controller, if the key identification information it received last time is inconsistent with the key identification information received when receiving the encryption key, it is possible that an error occurred in data transmission when performing step S70, that is, the encryption key received by the target controller is wrong, and the decryption result must be different from the latest shared key. Therefore, when this happens, the target controller sends a key sending request to the execution subject of this embodiment, so that the execution subject of this embodiment can resend the encryption key and key identification information to the target controller, thereby ensuring that each target controller can use the same latest shared key for encrypted communication.

[0083] It should be noted that the first preset time length of 1 hour and the second preset time length of 10 minutes are only for illustrative purposes. The first preset time length and the second preset time length can be set according to actual needs, as long as the first preset time length is greater than the second preset time length.

[0084] In a second aspect, an embodiment of the present application also provides a shared key distribution device.

[0085] In one embodiment, referring to Figure 3 , Figure 3 This is a functional module diagram of an embodiment of a shared key distribution device of the present application. Figure 3 As shown, the shared key distribution device includes:

[0086] An updating module 10, used to generate a latest shared key and store it in a storage area when in an updating moment;

[0087] An authentication module 20, used to determine a target controller that has passed identity authentication;

[0088] An acquisition module 30, used to acquire the latest shared key and the last generated shared key from the storage area;

[0089] The encryption module 40 is used to encrypt the latest shared key using the shared key generated last time to obtain an encryption key;

[0090] The sending module 50 is used to send the encryption key to the target controller.

[0091] Furthermore, in one embodiment, the update module 10 is used to:

[0092] When the update time comes, the vehicle identification information and the time information corresponding to the update time are obtained;

[0093] The latest shared key is generated based on the vehicle identification information and time information through a key generation algorithm and stored in a storage area.

[0094] Furthermore, in one embodiment, the authentication module 20 is used to:

[0095] receiving an identity authentication value sent by the controller, wherein the identity authentication value is sent by the controller when waking up from a dormant state;

[0096] Detecting whether the identity authentication value is a valid identity authentication value;

[0097] If the identity authentication value is a valid identity authentication value, the controller sending the identity authentication value is determined to be the target controller.

[0098] Furthermore, in one embodiment, the authentication module 20 is used to:

[0099] Send authentication requests to each controller;

[0100] Based on the feedback of each controller to the identity authentication request, the target controller that passes the identity authentication is determined.

[0101] Furthermore, in one embodiment, the shared key distribution device further includes a determination module, which is used to:

[0102] Determine key identification information of the latest shared key;

[0103] The sending module 50 is further used to send the encryption key and key identification information to the target controller.

[0104] Furthermore, in one embodiment, adjacent update moments are separated by a first preset time period, and the shared key distribution device further includes a keep-alive module, which is used to:

[0105] Sending key identification information to the target controller every second preset time period within the first preset time period;

[0106] The sending module 50 is also used to send the encryption key and key identification information to the target controller when receiving a key sending request sent by the target controller. The key sending request is sent by the target controller when it detects that the key identification information received most recently is inconsistent with the key identification information received when the encryption key is received.

[0107] Among them, the functional implementation of each module in the above-mentioned shared key distribution device corresponds to the various steps in the above-mentioned shared key distribution method embodiment, and its functions and implementation processes are no longer repeated here one by one.

[0108] In a third aspect, an embodiment of the present application also provides a vehicle.

[0109] The vehicle of the present application includes the shared key distribution device as described in the second aspect.

[0110] In a fourth aspect, an embodiment of the present application provides a shared key distribution device, which may be a device with data processing capabilities such as a vehicle computer and a server.

[0111] Reference Figure 4 , Figure 4 The hardware structure diagram of the shared key distribution device involved in the embodiment of the present application is shown in FIG. In the embodiment of the present application, the shared key distribution device may include a processor, a memory, a communication interface, and a communication bus.

[0112] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0113] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the shared key distribution device, and the interface used to realize the interconnection between the shared key distribution device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0114] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0115] The processor may be a general-purpose processor, and the general-purpose processor may call the shared key distribution program stored in the memory and execute the shared key distribution method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the shared key distribution program is called may refer to the various embodiments of the shared key distribution method of the present application, and will not be repeated here.

[0116] Those skilled in the art will understand that Figure 4 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0117] In a fifth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0118] A shared key distribution program is stored on the computer-readable storage medium of the present application, wherein when the shared key distribution program is executed by a processor, the steps of the shared key distribution method as described above are implemented.

[0119] Among them, the method implemented when the shared key distribution program is executed can refer to the various embodiments of the shared key distribution method of the present application, and will not be repeated here.

[0120] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0121] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0122] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0123] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0124] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0125] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0126] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A shared key distribution method, characterized in that: The shared key distribution method comprises: When it is time to update, generate the latest shared key and store it in the storage area; Determine the target controller that has passed the identity authentication; Get the latest shared key and the last generated shared key from the storage area; Use the shared key generated last time to encrypt the latest shared key to obtain an encryption key; Send the encryption key to the target controller.

2. The shared key distribution method according to claim 1, characterized in that: When the update is in progress, the latest shared key is generated and stored in the storage area, including: When the update time comes, the vehicle identification information and the time information corresponding to the update time are obtained; The latest shared key is generated based on the vehicle identification information and time information through a key generation algorithm and stored in a storage area.

3. The shared key distribution method according to claim 1, characterized in that: The target controller for determining that the identity authentication is passed includes: receiving an identity authentication value sent by the controller, wherein the identity authentication value is sent by the controller when waking up from a dormant state; Detecting whether the identity authentication value is a valid identity authentication value; If the identity authentication value is a valid identity authentication value, the controller sending the identity authentication value is determined to be the target controller.

4. The shared key distribution method according to claim 1, characterized in that: The target controller for determining that the identity authentication is passed includes: Send authentication requests to each controller; Based on the feedback of each controller to the identity authentication request, the target controller that passes the identity authentication is determined.

5. The shared key distribution method according to claim 1, characterized in that: After the encryption process is performed on the latest shared key using the key generated last time to obtain the encryption key, the method further includes: Determine key identification information of the latest shared key; Send the encryption key and key identification information to the target controller.

6. The shared key distribution method according to claim 5, characterized in that: Adjacent update moments are separated by a first preset time period, and after the encryption key and the key identification information are sent to the target controller, the method further includes: Sending key identification information to the target controller every second preset time period within the first preset time period; When receiving a key sending request sent by the target controller, the encryption key and key identification information are sent to the target controller. The key sending request is sent by the target controller when it detects that the key identification information received last time is inconsistent with the key identification information received when the encryption key is received.

7. A shared key distribution device, characterized in that: The shared key distribution device comprises: An update module, used to generate the latest shared key and store it in the storage area when it is at the update moment; Authentication module, used to determine the target controller that has passed the identity authentication; An acquisition module, used for acquiring the latest shared key and the last generated shared key from the storage area; The encryption module is used to encrypt the latest shared key using the shared key generated last time to obtain an encryption key; The sending module is used to send the encryption key to the target controller.

8. A vehicle, characterized in that: The vehicle comprises the shared key distribution device according to claim 7.

9. A shared key distribution device, characterized in that: The shared key distribution device includes a processor, a memory, and a shared key distribution program stored in the memory and executable by the processor, wherein when the shared key distribution program is executed by the processor, the steps of the shared key distribution method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a shared key distribution program, wherein when the shared key distribution program is executed by a processor, the steps of the shared key distribution method according to any one of claims 1 to 6 are implemented.

Images