Vehicle key management method, security service equipment, key management system

Abstract

The present invention discloses a vehicle key management method, a security service device, and a key management system. The vehicle key management method comprises: receiving a key management request sent by a terminal device, wherein the key management request comprises a service identifier and an ECU identifier of a vehicle electronic control unit ECU; obtaining key configuration information according to the service identifier, the ECU identifier, and preset configuration information; sending the key configuration information to a cryptographic machine so that the cryptographic machine obtains a vehicle service ciphertext according to the key configuration information; receiving the vehicle service ciphertext sent by the cryptographic machine, and sending the vehicle service ciphertext to the corresponding ECU through the terminal device. Thus, the vehicle key management method reduces the key management complexity while also reducing the key management cost and the risk of key leakage, thereby improving the safety of the vehicle, and by introducing the key configuration information, can better meet the differentiated requirements for keys between different services.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking, and in particular to a vehicle key management method, security service equipment, and a key management system. Background Art

[0002] With the rapid development of the intelligent connected vehicle industry, the electronic and electrical architecture is gradually migrating from the original distributed electronic and electrical architecture to the domain-centralized or vehicle-centralized electronic and electrical architecture. At present, most OEMs usually divide components into different domains according to their functions, such as the power domain, chassis domain, body domain, cockpit domain, and autonomous driving domain. Each domain has a domain controller as the processing center of the domain. Due to the introduction of domain controllers, Ethernet-based electronic and electrical architectures, and SOA (Service Oriented Architecture) technologies, in-vehicle security faces increasing challenges. Access between different domains needs to be strictly controlled, and cryptography can be used for security protection. However, for the symmetric key system in cryptography, there is no industry standard for vehicle key management. Each OEM and component manufacturer formulates a corresponding key management plan based on its own business functions. With the development of Internet of Vehicles technology, more and more components have the ability to interact with the outside world. As the capabilities are improved, the risk of vehicle key leakage also increases, which in turn brings more risks to the personal and property safety of end users.

[0003] In the related technologies, the key management of the OEM adopts the mode of one car one key. The OEM generates a random key for the vehicle and ensures that the key of each vehicle is different. At the same time, due to the complexity of the components and business scenarios in the vehicle, in order to simplify the complexity of key management, the OEM usually applies this key to all business scenarios and components that require keys, such as SecOC (Secure Onboard Communication, board-side encrypted communication), power anti-theft, in-vehicle communication authentication and other business scenarios. The components may include TBOX (Telematics BOX, Internet of Vehicles terminal), gateway, body domain controller, power domain controller, etc. This mode will have the following problems:

[0004] 1) Due to the large number of business scenarios and the involvement of many components, in some business scenarios, components may face more attack points, such as some networked business scenarios such as remote control and remote diagnosis. At the same time, some components may not be able to provide a sufficiently secure protection level for keys due to their own hardware limitations or vehicle model inheritance, resulting in a higher risk of key leakage. Once the key is leaked, all business scenarios will be affected. If business scenarios such as driving safety are affected, the personal safety and property safety of users will be affected;

[0005] 2) When the key of a vehicle is leaked, the OEM will generate a random key for the vehicle again. If the OEM generates 100,000 vehicles, it will need to store 100,000 vehicle keys. Since the key is highly sensitive information, the increasing number of keys will inevitably bring higher management difficulty and pressure to the OEM.

[0006] 3) With the development of vehicle electronic and electrical architecture, the business division interface and independence between domains are becoming stronger and stronger. However, due to different functional safety level requirements for services carried by different domains, different requirements for business component capabilities within each domain, and different information security requirements for each domain, the same vehicle key cannot meet the diverse requirements of business security needs in each domain;

[0007] 4) As vehicles become more and more intelligent, they will carry more and more important data involving personal privacy. Therefore, the encryption of similar important data and sensitive data must be different. The cryptographic technology used will also be different, and the key length will also be different, so the same key cannot be used to meet the requirements. Summary of the invention

[0008] The present invention aims to solve one of the technical problems in the related art to at least a certain extent. To this end, the first purpose of the present invention is to propose a vehicle key management method, which reduces the complexity of key management, reduces the key management cost and the risk of key leakage, improves the safety of the vehicle, and by introducing key configuration information, can better meet the differentiated requirements of different services for keys.

[0009] The second objective of the present invention is to provide a security service device.

[0010] The third objective of the present invention is to provide a key management system.

[0011] In order to achieve the above-mentioned objectives, an embodiment of the first aspect of the present invention proposes a vehicle key management method, which includes: receiving a key management request sent by a terminal device, wherein the key management request includes a service identifier and an ECU identifier of a vehicle electronic control unit ECU; obtaining key configuration information according to the service identifier, the ECU identifier and preset configuration information; sending the key configuration information to a cryptographic machine so that the cryptographic machine obtains a vehicle service ciphertext according to the key configuration information; receiving the vehicle service ciphertext sent by the cryptographic machine, and sending the vehicle service ciphertext to the corresponding ECU through the terminal device.

[0012] According to the vehicle key management method of the embodiment of the present invention, firstly, a key management request sent by a terminal device is received, wherein the key management request includes a service identifier and an ECU identifier of the vehicle electronic control unit ECU; key configuration information is obtained according to the service identifier, ECU identifier and preset configuration information; the key configuration information is sent to the cryptographic machine so that the cryptographic machine obtains the vehicle service ciphertext according to the key configuration information; the vehicle service ciphertext sent by the cryptographic machine is received, and the vehicle service ciphertext is sent to the corresponding ECU through the terminal device. Therefore, the vehicle key management method reduces the complexity of key management while also reducing the key management cost and the risk of key leakage, thereby improving the safety of the vehicle, and by introducing key configuration information, it can better meet the differentiated requirements for keys between different services.

[0013] In addition, the vehicle key management method proposed in the above embodiment of the present invention may also have the following additional technical features:

[0014] In one embodiment of the present invention, the key configuration information includes a business root key identifier, a business root key derivation configuration information and a business master key derivation configuration information, and obtaining the vehicle business ciphertext based on the key configuration information includes: determining the business root key based on the business root key identifier; deriving the business root key using the business root key derivation configuration information to generate a business master key; deriving the business master key using the business master key derivation configuration information to generate a vehicle business key; and obtaining the vehicle business ciphertext based on the vehicle business key.

[0015] In one embodiment of the present invention, the business root key derivation configuration information includes a business root key derivation algorithm identifier and a business root key derivation factor, and the business root key derivation factor includes business master key configuration information and the business identifier, wherein the use of the business root key derivation configuration information to derive the business root key includes: determining a target business root key derivation algorithm based on the business root key derivation algorithm identifier, and using the target business root key derivation algorithm to derive the business root key based on the business master key configuration information and the business identifier.

[0016] In one embodiment of the present invention, the business master key derivation configuration information includes a business master key derivation algorithm identifier and a business master key derivation factor, and the business master key derivation factor includes vehicle business key configuration information and the ECU identifier, wherein the use of the business master key derivation configuration information to derive the business master key includes: determining a target business master key derivation algorithm according to the business master key derivation algorithm identifier, and using the target business master key derivation algorithm to derive the business master key according to the vehicle business key configuration information and the ECU identifier.

[0017] In one embodiment of the present invention, obtaining the vehicle business ciphertext according to the vehicle business key includes: encrypting the vehicle business key configuration information and the plaintext information of the vehicle business key according to a preset key derivation mechanism to obtain the vehicle business ciphertext.

[0018] In one embodiment of the present invention, there is a one-to-one or one-to-many correspondence between the service identifier and the ECU identifier.

[0019] In one embodiment of the present invention, when the number of the business identifiers is M and the number of the ECU identifiers is N, the number of the vehicle business ciphertexts is M, M≤N, and M and N are both positive integers; wherein, when the M vehicle business ciphertexts are sent to the terminal device, the M business identifiers and N ECU identifiers corresponding to the M vehicle business ciphertexts are also sent to the terminal device, so that the terminal device sends the corresponding vehicle business ciphertext to the corresponding ECU according to each business identifier and each ECU identifier.

[0020] In order to achieve the above-mentioned purpose, a second aspect of the present invention proposes a security service device, including a memory, a processor and a computer program stored in the memory, and when the computer program is executed by the processor, the above-mentioned vehicle key management method is implemented.

[0021] According to the security service device of the embodiment of the present invention, it includes a memory, a processor and a computer program stored in the memory. When the computer program is executed by the processor, it first receives a key management request sent by a terminal device, wherein the key management request includes a service identifier and an ECU identifier of a vehicle electronic control unit ECU; obtains key configuration information according to the service identifier, ECU identifier and preset configuration information; sends the key configuration information to a cryptographic machine so that the cryptographic machine obtains a vehicle service ciphertext according to the key configuration information; receives the vehicle service ciphertext sent by the cryptographic machine, and sends the vehicle service ciphertext to the corresponding ECU through the terminal device. Therefore, the vehicle key management method reduces the complexity of key management while also reducing the key management cost and the risk of key leakage, thereby improving the safety of the vehicle, and by introducing key configuration information, it can better meet the differentiated requirements for keys between different services.

[0022] In order to achieve the above-mentioned purpose, the third aspect of the embodiment of the present invention proposes a key management system, which includes: a terminal device, a cryptographic machine and the above-mentioned security service device, wherein the security service device is communicatively connected to the terminal device and the cryptographic machine respectively.

[0023] According to an embodiment of the present invention, the key management system comprises a terminal device, a cryptographic machine and the above-mentioned security service device, wherein the security service device is respectively connected to the terminal device and the cryptographic machine for communication. Thus, through the key management system, the key management complexity is reduced, the key management cost and the key leakage risk are reduced, the safety of the vehicle is improved, and by introducing the key configuration information, the differentiated requirements for keys between different services can be better met.

[0024] In addition, the key management system proposed in the above embodiment of the present invention may also have the following additional technical features:

[0025] In one embodiment of the present invention, the terminal device includes an after-sales diagnostic instrument and / or a production line electrical inspection device.

[0026] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 is a flow chart of a vehicle key management method according to an embodiment of the present invention;

[0028] Figure 2 is a flow chart of a vehicle key management method according to a specific embodiment of the present invention;

[0029] Figure 3 is a schematic diagram of key derivation of a vehicle key management method according to an example of the present invention;

[0030] Figure 4 is a flow chart of a vehicle key management method according to an example of the present invention;

[0031] Figure 5 is a structural block diagram of a key management system according to an embodiment of the present invention;

[0032] Figure 6 It is a structural diagram of a key management system of an example of the present invention. DETAILED DESCRIPTION

[0033] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.

[0034] The vehicle key management method, security service device, and key management system according to embodiments of the present invention will be described below with reference to the accompanying drawings.

[0035] Figure 1 It is a flow chart of a vehicle key management method according to an embodiment of the present invention.

[0036] like Figure 1 As shown, the vehicle key management method of the embodiment of the present invention includes the following steps:

[0037] S101, receiving a key management request sent by a terminal device, wherein the key management request includes a service identifier and an ECU identifier of a vehicle electronic control unit ECU.

[0038] Specifically, the terminal device obtains a key management request from vehicle components, and the security service device receives the key management request sent by the terminal device. The key management request includes a service identifier and an ECU identifier of the vehicle's electronic control unit ECU (Electronic Control Unit), as well as a vehicle identification code, vehicle component information, ECU security module, and algorithm configuration information.

[0039] S102, obtaining key configuration information according to the service identifier, the ECU identifier and the preset configuration information.

[0040] Specifically, the security service device obtains the key configuration information according to the service identifier, the ECU identifier and the preset configuration information, wherein the preset configuration information corresponding to each service is configured in advance in the security service device.

[0041] In some embodiments of the present invention, the key configuration information includes a service root key identifier, service root key derivation configuration information, and service master key derivation configuration information. Specifically, the security service device uses the pre-configured preset configuration information to obtain the service root key identifier corresponding to the service according to the service identifier, and obtains the service root key derivation configuration information and the service master key derivation configuration information.

[0042] In some embodiments of the present invention, the service root key derivation configuration information includes a service root key derivation algorithm identifier and a service root key derivation factor, and the service root key derivation factor includes service master key configuration information and a service identifier.

[0043] In some embodiments of the present invention, the business master key derivation configuration information includes a business master key derivation algorithm identifier and a business master key derivation factor, and the business master key derivation factor includes vehicle business key configuration information and an ECU identifier.

[0044] S103, sending the key configuration information to the cryptographic machine, so that the cryptographic machine obtains the vehicle business ciphertext according to the key configuration information.

[0045] In some embodiments of the present invention, the vehicle service ciphertext is obtained according to the key configuration information, and the vehicle service ciphertext is obtained according to the key configuration information. Figure 2 , which may include:

[0046] S301, determining a service root key according to a service root key identifier.

[0047] S302: derive the service root key using the service root key derivation configuration information to generate a service master key.

[0048] Specifically, the target business root key derivation algorithm is determined according to the business root key derivation algorithm identifier in the business root key derivation configuration information, and the business root key is derived according to the business master key configuration information and the business identifier using the target business root key derivation algorithm to generate a business master key.

[0049] S303: derive the business master key using the business master key derivation configuration information to generate a vehicle business key.

[0050] Specifically, the target business master key derivation algorithm is determined according to the business master key derivation algorithm identifier in the business master key derivation configuration information, and the target business master key derivation algorithm is used to derive the business master key according to the vehicle business key configuration information and the ECU identifier to generate a vehicle business key.

[0051] S304, obtaining the vehicle business ciphertext according to the vehicle business key.

[0052] Specifically, according to a preset key derivation mechanism, the vehicle service key configuration information and the plain text information of the vehicle service key are encrypted to obtain the vehicle service ciphertext.

[0053] It should be noted that the above-mentioned preset key derivation mechanism is a mechanism pre-agreed between the security service device or the cryptographic machine and the ECU security module inside the vehicle electronic control unit ECU.

[0054] S104, receiving the vehicle business ciphertext sent by the cipher machine, and sending the vehicle business ciphertext to the corresponding ECU through the terminal device.

[0055] Specifically, the cryptographic machine sends the vehicle business ciphertext to the security service device, the security service device sends the vehicle business ciphertext and its corresponding business identifier and ECU identifier to the terminal device, the terminal device sends the corresponding vehicle business ciphertext to the corresponding vehicle ECU based on the business identifier and ECU identifier, the vehicle ECU decrypts the vehicle business ciphertext according to the preset key derivation mechanism and stores it securely.

[0056] For the service identifier, ECU identifier, and vehicle service ciphertext sent to the terminal device, in the embodiment of the present invention, the following relationship exists:

[0057] There is a one-to-one or one-to-many correspondence between the service identifier and the ECU identifier. When the number of service identifiers is M and the number of ECU identifiers is N, the number of vehicle service ciphertexts is M, M≤N, and both M and N are positive integers. When M vehicle service ciphertexts are sent to the terminal device, the M service identifiers and N ECU identifiers corresponding to the M vehicle service ciphertexts are also sent to the terminal device, so that the terminal device sends the corresponding vehicle service ciphertext to the corresponding ECU according to each service identifier and each ECU identifier.

[0058] Figure 3 It is a schematic diagram of key derivation of a key management method according to an example of the present invention.

[0059] like Figure 3 As shown, ARK is the service root key. The OEM can create one or more service root keys ARK in the cryptographic machine according to different service requirements, such as different key algorithms and key technologies. The plaintext value of the root service key ARK never leaves the cryptographic machine. If there are multiple service root keys ARK, the security service device can use the service root key identifier to determine the service root key ARK. Generally speaking, for a specific key algorithm or key technology, multiple services can share one service root key ARK.

[0060] AMK is the business master key. The cryptographic machine uses the input business root key derivation configuration information to derive the business root key ARK. Since the business master key AMK is the process information of key derivation, it is not stored in the cryptographic machine, thus reducing the risk of leakage. Generally speaking, for a specific key algorithm or key technology, a business only needs one business master key AMK.

[0061] AVK is the vehicle business key, which is derived by the cryptographic machine using the input business master key derivation configuration information to generate the business master key AMK. After the cryptographic machine generates the vehicle business key AVK, it needs to use the preset key derivation mechanism to generate the vehicle business ciphertext, and send the vehicle business ciphertext to the vehicle ECU through the security service device and terminal device. The security module of the vehicle ECU decrypts the vehicle business ciphertext using the agreed preset key derivation mechanism and stores it securely in the security module of the ECU.

[0062] In order to better understand the vehicle key management method of the embodiment of the present invention, as an example, refer to Figure 4 The process of the vehicle key management method in the OEM production line includes the following steps:

[0063] Step 1: The terminal device obtains a key management request from vehicle components, including vehicle identification code, service identification, component information, ECU security module, and algorithm configuration information.

[0064] Step 2: The terminal device submits the obtained key management request to the security service device.

[0065] Step 3: The security service device obtains the business root key identifier ARK_ID corresponding to the business from the preset configuration information according to the input business identifier, and generates the business root key derivation configuration information ARK_DIV_CFG, which mainly includes the business root key derivation algorithm identifier ARK_DIV_ALGO_ID, the business root key derivation factor ARK_DIV_FACTOR including the business master key configuration information AMK_HEADER and the business identifier.

[0066] Step 4: The security service device obtains relevant information from the preset configuration information based on the input business identifier and generates the business master key derivation configuration information AMK_DIV_CFG, which mainly includes the business master key derivation algorithm identifier AMK_DIV_ALGO_ID, the vehicle business key configuration information AVK_HEADER, and the business master key derivation factor AMK_DIV_FACTOR containing the ECU identifier.

[0067] Step 5: The security service device submits the service root key identifier ARK_ID, service root key derivation configuration information ARK_DIV_CFG, and service master key derivation configuration information AMK_DIV_CFG to the cryptographic machine.

[0068] Step 6: The cryptographic machine obtains the business root key ARK according to the business root key identifier ARK_ID, and then uses the target business root key derivation algorithm and business root key derivation factor ARK_DIV_FACTOR determined by the business root key derivation algorithm identifier ARK_DIV_ALGO_ID in the business root key derivation configuration information ARK_DIV_CFG to generate the business master key AMK.

[0069] Step 7: The cipher machine uses the target business master key derivation algorithm and business master key derivation factor AMK_DIV_FACTOR determined by the business master key derivation algorithm identifier AMK_DIV_ALGO_ID in the business master key derivation configuration information AMK_DIV_CFG to generate the vehicle business key AVK, and uses the preset key derivation mechanism to encrypt and encapsulate the plaintext value of the vehicle business key configuration information AVK_HEADER and the vehicle business key AVK to generate the vehicle business ciphertext.

[0070] Step 8: The cryptographic machine returns the vehicle business ciphertext to the security service device.

[0071] Step 9: The security service device returns the service ID, vehicle service ciphertext and ECU ID to the terminal device.

[0072] Step 10: The terminal device sends the corresponding vehicle service ciphertext to the corresponding vehicle ECU according to the ECU identifier and service identifier.

[0073] Step 11: The vehicle ECU decrypts the vehicle business ciphertext according to the preset key derivation mechanism and stores it securely.

[0074] In the above specific example, the OEM can maintain a unified list of business identifiers by introducing business identifiers, and isolate the business master keys of each business through key derivation. Specifically, since a vehicle component supports multiple businesses, the corresponding business identifier is written into the component on the component production line. When the OEM production line performs key filling, the supported business identifier can be read from the component, thereby reducing the management complexity of the OEM production line and related equipment for the components and business identifiers. At the same time, by introducing the vehicle identification code in the key derivation, it can ensure that the same business of different vehicles is isolated from each other, and the leakage of a vehicle's business key will not affect other vehicles.

[0075] Secondly, by introducing the business root key derivation configuration information, the business root key derivation factor includes the business identifier, so as to ensure that the business master keys of each business are isolated from each other; by introducing the business master key derivation configuration information, the business master key derivation factor includes the ECU identifier, so as to ensure that the vehicle business keys of each vehicle are isolated from each other. Among them, the business root key derivation configuration information and the business master key derivation configuration information can be managed by the security service device, and different businesses can use different key derivation configuration information to meet the diversity of business needs.

[0076] In addition, the above-mentioned business root key derivation configuration information and business master key derivation configuration information also include configuration information for identifying keys, such as introducing business master key configuration information and vehicle business key configuration information for business master keys and vehicle business keys, which can be used for subsequent full life cycle management of keys. For example, key version information can be used to update keys. The cryptographic machine or security service device can detect whether the vehicle continues to use the leaked key by comparing the key configuration information, thereby triggering whether the key is updated. If a key leak occurs, the derived key can be updated by changing the key configuration information without changing the derived key. At the same time, the use of key configuration information can better meet the differentiated requirements for keys due to different business needs, that is, due to different cryptographic algorithms, that is, cryptographic technologies.

[0077] Therefore, the vehicle key management method, by introducing key derivation technology and key configuration information, only needs to manage a few business root keys or business master keys, and then uses key derivation technology to support massive vehicle business keys. In addition, by adjusting the key configuration information only on the platform side, new business master keys can be quickly generated for new businesses, or new algorithms can be generated and business master keys can be updated for existing businesses, thereby meeting the dynamic expansion needs of the business.

[0078] In summary, the vehicle key management method of the embodiment of the present invention first receives a key management request sent by a terminal device, wherein the key management request includes a service identifier and an ECU identifier of the vehicle electronic control unit ECU; obtains key configuration information according to the service identifier, ECU identifier and preset configuration information; sends the key configuration information to the cryptographic machine so that the cryptographic machine obtains the vehicle service ciphertext according to the key configuration information; receives the vehicle service ciphertext sent by the cryptographic machine, and sends the vehicle service ciphertext to the corresponding ECU through the terminal device. Therefore, the vehicle key management method reduces the complexity of key management while also reducing the key management cost and the risk of key leakage, and provides a key isolation mechanism for each service and each vehicle, thereby improving the safety of the vehicle, and by introducing key configuration information, it can better meet the differentiated requirements for keys between different services.

[0079] Furthermore, the present invention provides a security service device.

[0080] In an embodiment of the present invention, the security service device includes a memory, a processor, and a computer program stored in the memory. When the computer program is executed by the processor, the above-mentioned vehicle key management method is implemented.

[0081] The security service device of the embodiment of the present invention, when the computer program on it is executed by the processor, first receives a key management request sent by the terminal device, wherein the key management request includes a service identifier and an ECU identifier of the vehicle electronic control unit ECU; obtains key configuration information according to the service identifier, ECU identifier and preset configuration information; sends the key configuration information to the cryptographic machine so that the cryptographic machine obtains the vehicle service ciphertext according to the key configuration information; receives the vehicle service ciphertext sent by the cryptographic machine, and sends the vehicle service ciphertext to the corresponding ECU through the terminal device. Therefore, the vehicle key management method reduces the complexity of key management while also reducing the key management cost and the risk of key leakage, and provides a key isolation mechanism for each service and each vehicle, thereby improving the safety of the vehicle, and by introducing key configuration information, it can better meet the differentiated requirements for keys between different services.

[0082] Furthermore, the present invention proposes a key management system.

[0083] Figure 5 It is a structural block diagram of a key management system according to an embodiment of the present invention.

[0084] like Figure 5 As shown, the key management system 100 includes a terminal device 10, a cryptographic machine 20 and a security service device 30, wherein the security service device 30 is communicatively connected with the terminal device 10 and the cryptographic machine 20 respectively.

[0085] In some embodiments of the present invention, the terminal device 10 includes an after-sales diagnostic instrument and / or a production line electrical inspection device. Figure 6 The terminal device 10 serves as a communication bridge between vehicle components and the security service device 30. It can directly call the interface of the security service device 30, send a key management request to the security service device 30, and obtain the vehicle business ciphertext sent by the security service device 30, and send the vehicle business ciphertext to the vehicle ECU.

[0086] The key management system of the embodiment of the present invention includes a terminal device, a cryptographic machine and a security service device, wherein the security service device is respectively connected to the terminal device and the cryptographic machine for communication. Thus, the key management system reduces the complexity of key management, reduces the key management cost and the risk of key leakage, and provides a key isolation mechanism for each service and each vehicle, thereby improving the safety of the vehicle. Moreover, by introducing key configuration information, the differentiated requirements for keys between different services can be better met.

[0087] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0088] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiment, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. If implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0089] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0090] In the description of this specification, the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, and do not indicate or imply that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and cannot be understood as a limitation on the present invention.

[0091] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0092] In the description of this specification, unless otherwise specified, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements, unless otherwise clearly defined. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0093] In the present invention, unless otherwise clearly specified and limited, a first feature being "above" or "below" a second feature may mean that the first and second features are in direct contact, or the first and second features are in indirect contact through an intermediate medium. Moreover, a first feature being "above", "above" or "above" a second feature may mean that the first feature is directly above or obliquely above the second feature, or simply means that the first feature is higher in level than the second feature. A first feature being "below", "below" or "below" a second feature may mean that the first feature is directly below or obliquely below the second feature, or simply means that the first feature is lower in level than the second feature.

[0094] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.

Claims

1. A vehicle key management method, characterized in that: The method comprises: Receiving a key management request sent by a terminal device, wherein the key management request includes a service identifier and an ECU identifier of an electronic control unit ECU of a vehicle; Obtaining key configuration information according to the service identifier, the ECU identifier and preset configuration information; Sending the key configuration information to a cryptographic machine so that the cryptographic machine obtains the vehicle service ciphertext according to the key configuration information; Receiving the vehicle business ciphertext sent by the cipher machine, and sending the vehicle business ciphertext to the corresponding ECU through the terminal device; The key configuration information includes a service root key identifier, service root key derivation configuration information and service master key derivation configuration information, the service root key derivation configuration information includes a service root key derivation algorithm identifier and a service root key derivation factor, the service root key derivation factor includes service master key configuration information and the service identifier, the service master key derivation configuration information includes a service master key derivation algorithm identifier and a service master key derivation factor, the service master key derivation factor includes vehicle service key configuration information and the ECU identifier, and obtaining a vehicle service ciphertext according to the key configuration information includes: Determining a service root key according to the service root key identifier; Deriving the service root key using the service root key derivation configuration information to generate a service master key; Deriving the business master key using the business master key derivation configuration information to generate a vehicle business key; Obtaining the vehicle business ciphertext according to the vehicle business key; The obtaining the vehicle business ciphertext according to the vehicle business key includes: encrypting the vehicle business key configuration information and the plain text information of the vehicle business key according to a preset key derivation mechanism to obtain the vehicle business ciphertext.

2. The vehicle key management method according to claim 1, characterized in that: The deriving the service root key using the service root key derivation configuration information includes: The target business root key derivation algorithm is determined according to the business root key derivation algorithm identifier, and the business root key is derived according to the business master key configuration information and the business identifier using the target business root key derivation algorithm.

3. The vehicle key management method according to claim 1, characterized in that: The deriving the business master key by using the business master key derivation configuration information includes: A target business master key derivation algorithm is determined according to the business master key derivation algorithm identifier, and the business master key is derived according to the vehicle business key configuration information and the ECU identifier using the target business master key derivation algorithm.

4. The vehicle key management method according to claim 1, characterized in that: There is a one-to-one or one-to-many correspondence between the service identifier and the ECU identifier.

5. The vehicle key management method according to claim 4, characterized in that: When the number of the service identifiers is M and the number of the ECU identifiers is N, the number of the vehicle service ciphertexts is M, M≤N, and both M and N are positive integers; Among them, when the M vehicle business ciphertexts are sent to the terminal device, the M business identifiers and N ECU identifiers corresponding to the M vehicle business ciphertexts are also sent to the terminal device, so that the terminal device sends the corresponding vehicle business ciphertext to the corresponding ECU according to each business identifier and each ECU identifier.

6. A security service device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory, wherein when the computer program is executed by the processor, the vehicle key management method as claimed in any one of claims 1 to 5 is implemented.

7. A key management system, characterized in that: The system comprises: a terminal device, a cryptographic machine and a security service device according to claim 6, wherein the security service device is communicatively connected with the terminal device and the cryptographic machine respectively.

8. The key management system according to claim 7, characterized in that: The terminal equipment includes an after-sales diagnostic instrument and / or a production line electrical inspection device.

Images