Development method and system based on SecOC real vehicle communication, vehicle and equipment

Abstract

The invention discloses a SecOC real vehicle communication-based development method and system, a vehicle and equipment. The invention discloses a SecOC real vehicle communication-based development method. The method comprises the following steps of: obtaining a key and a message authentication code from a hardware security module; developing a calculation function of a SecOC module according to the secret key and the message authentication code; after the calculation function of the SecOC module is developed, compiling the SecOC module to obtain a library file; and calling the library file to realize encrypted communication in the vehicle. The method has the advantages that the development difficulty is low, development can be carried out independently from the control unit, development is carried out only around the SecOC function, and the development capability standard is reduced. The system is convenient to transplant, can be matched with different control unit environments after being compiled into library files, and can be suitable for different controllers after being developed at a time. And the maintenance cost is reduced, the library file can be independently maintained and upgraded on the premise of keeping uniform interfaces, and the maintenance cost is reduced.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a development method, system, vehicle and equipment based on SecOC real-vehicle communication. Background Art

[0002] In the related art, the SecOC module is integrated at the AUTOSAR PduR level. Basically, the solution using AUTOSAR is to develop and integrate SecOC.

[0003] The following defects exist: SecOC modules are designed based on the AUTOSAR architecture, and SecOC relies on multiple modules, which increases the complexity of the system and limits its flexibility. Because the special features of SecOC may not be fully compatible with other systems or applications, some functions may not work properly or require additional adaptation work. Moreover, over time, SecOC functions need to be updated and maintained to improve security to cope with new security threats and challenges. However, these updates require the update of the entire communication protocol stack to upgrade and maintain according to the existing architecture, which is costly. Summary of the invention

[0004] Based on this, it is necessary to provide a development method, system, vehicle and equipment based on SecOC real-vehicle communication to address the above technical issues. The development difficulty is low and the development can be carried out independently of the control unit. The development is only centered around the SecOC function, which reduces the development capability standard. The porting is convenient and the compiled library files can be adapted to different control unit environments. It can be applied to different controllers after one development. The maintenance cost is reduced. The library files can be maintained and upgraded separately while maintaining the unified interface, which reduces the maintenance cost.

[0005] In a first aspect, a development method based on SecOC real vehicle communication is provided, including:

[0006] Obtain keys and message authentication codes from the hardware security module;

[0007] Develop the calculation function of the SecOC module based on the key and message authentication code;

[0008] After the computing function of the SecOC module is developed, the SecOC module is compiled to obtain a library file;

[0009] The library file is called to implement encrypted communication within the vehicle.

[0010] In some examples, obtaining a key and a message authentication code from a hardware security module includes:

[0011] The SecOC module presets the key in the hardware security module and uses the initialization interface in the hardware security module to perform key initialization management;

[0012] When the key is modified, the SecOC module synchronizes the key update with the hardware security module by modifying the preset key.

[0013] In some examples, calling the library file to implement encrypted vehicle communication includes:

[0014] The SecOC module performs CANID analysis according to the message input by the serial communication interface layer of the vehicle;

[0015] According to the analysis results, select the messages that need to be calculated by SecOC and process them separately.

[0016] After the processing is completed, the processing results are returned to the routing module in the vehicle.

[0017] In some examples, calling the library file to implement encrypted vehicle communication includes:

[0018] The SecOC module performs SecOC calculation on the message to which SecOC information needs to be added;

[0019] The calculation results are returned to the routing module in the vehicle.

[0020] In some examples, calling the library file to implement encrypted vehicle communication includes:

[0021] The SecOC module performs verification calculation on the received SecOC message and returns the verification result to the routing module in the vehicle, so that the routing module in the vehicle performs corresponding operation processing on the verification result.

[0022] In some examples, this also includes:

[0023] When an error occurs in the SecOC module during operation, a DTC error code is generated according to the error level, and the DTC error code is fed back.

[0024] In some examples, the library file is a dynamic library file or a static library file.

[0025] In the second aspect, a development system based on SecOC real vehicle communication is provided, including:

[0026] An acquisition module, used to obtain a key and a message authentication code from a hardware security module;

[0027] A function development module, used to develop a computing function of the SecOC module according to the key and the message authentication code;

[0028] The library file generation module is used to compile the SecOC module after the computing function of the SecOC module is developed to obtain a library file so that when the library file is called, encrypted communication in the vehicle can be realized.

[0029] In a third aspect, a vehicle is provided, comprising: a development system based on SecOC real-vehicle communication according to the second aspect.

[0030] In a fourth aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the development method based on SecOC real vehicle communication of the above-mentioned first aspect and any possible implementation method of the first aspect are implemented.

[0031] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the steps of the development method based on SecOC real-vehicle communication of the above-mentioned first aspect and any possible implementation method of the first aspect are implemented.

[0032] In a sixth aspect, a computer program product is provided, on which a computer program is stored. When the program is executed by a processor, the steps of the development method based on SecOC real-vehicle communication of the above-mentioned first aspect and any possible implementation method of the first aspect are implemented.

[0033] According to the embodiment of the present application, the key and message authentication code are obtained from the hardware security module, and the computing function of the SecOC module is developed according to the key and the message authentication code. After the computing function of the SecOC module is developed, the SecOC module is compiled to obtain a library file so as to call the library file to realize encrypted communication in the vehicle. It is suitable for the automotive network architecture and meets the function of SecOC. As a library file, it can be developed independently of other control units. After development, it can be fully embedded in the development environment of the control unit, and it can be more flexibly adapted to the development environment of different control units, which is convenient for the transplantation and development of different controllers. Therefore, it has low development difficulty, can be developed independently of the control unit, and is only developed around the SecOC function, which reduces the development capability standard. It is easy to transplant, and the library file compiled can be adapted to different control unit environments, and can be applied to different controllers after one development. The maintenance cost is reduced, and the library file can be separately maintained and upgraded under the premise of maintaining the unified interface, which reduces the maintenance cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0035] Figure 1 A flowchart of a development method based on SecOC real-vehicle communication provided in an embodiment of the present application;

[0036] Figure 2 A schematic diagram of a development method based on SecOC real-vehicle communication provided in an embodiment of the present application;

[0037] Figure 3 A structural block diagram of a development system based on SecOC real-vehicle communication provided in an embodiment of the present application;

[0038] Figure 4 A structural block diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The present application is further described in detail below in conjunction with the embodiments and drawings. It is to be understood that the specific embodiments described herein are only used to explain the relevant application, rather than to limit the application. It is also necessary to explain that, for ease of description, only the parts related to the application are shown in the drawings.

[0040] It should be noted that, in the absence of conflict, the embodiments of the present application, that is, the features of the embodiments, can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0041] The following describes in detail the development method, system, device and medium based on SecOC real-vehicle communication according to the embodiments of the present application in conjunction with the accompanying drawings.

[0042] Figure 1 FIG. 1 is a flow chart of a development method based on SecOC real vehicle communication according to an embodiment of the present application. Figure 1 As shown, the development method based on SecOC real vehicle communication according to the embodiment of the present application includes the following steps:

[0043] S101: Obtain a key and a message authentication code from a hardware security module.

[0044] In one embodiment of the present application, obtaining a key and a message authentication code from a hardware security module includes: the SecOC module presetting the key in the hardware security module and using the initialization interface in the hardware security module to perform key initialization management; when the key is modified, the SecOC module synchronizes the key update with the hardware security module by modifying the preset key.

[0045] S102: Develop the calculation function of the SecOC module according to the key and the message authentication code.

[0046] S103: After the computing function of the SecOC module is developed, the SecOC module is compiled to obtain a library file.

[0047] In one embodiment of the present application, the library file may be a dynamic library file or a static library file, for example, a file compiled into .a or .so.

[0048] Specifically, the SecOC module will be compiled into a .a or .so file and integrated into the software. If it needs to be updated and maintained, you can recompile it and update the new library file to the software environment.

[0049] S104: Call the library file to implement encrypted communication within the vehicle.

[0050] In one embodiment of the present application, the library file is called to implement encrypted vehicle communication, and one application thereof includes: the SecOC module performs CANID parsing according to the message input by the serial communication interface layer of the vehicle;

[0051] According to the analysis results, the messages that need to be calculated by SecOC are selected for separate processing. After the processing is completed, the processing results are returned to the routing module in the vehicle.

[0052] In one embodiment of the present application, the library file is called to implement encrypted vehicle communication, and one application thereof includes: the SecOC module performs SecOC calculation on the message to which SecOC information needs to be added; and returns the calculation result to the routing module in the vehicle.

[0053] In one embodiment of the present application, the library file is called to implement encrypted vehicle communication, and one application thereof includes: the SecOC module performs verification calculations on the received SecOC message, and returns the verification result to the routing module in the vehicle, so that the routing module in the vehicle performs corresponding operations on the verification result.

[0054] In one embodiment of the present application, the development method based on SecOC real-vehicle communication also includes: when an error occurs in the SecOC module during operation, a DTC error code is generated according to the error level, and the DTC error code is fed back.

[0055] Combination Figure 2 As shown, HSM, or Hardware Security Module, is used to provide keys and calculate CMAC information (message authentication code) required for SecOC. SecOC will be independently developed and compiled into an independent library file to provide SecOC calculation functions for the communication protocol stack.

[0056] Among them, key initialization: The SecOC module can preset the key in the HSM and use the initialization interface in the HSM to manage the key initialization. When modifying the key, the preset key can be modified to synchronize the key update.

[0057] CANID parsing: The SecOC module can perform CANID parsing based on the messages input from the COM layer, and select the messages that need to be calculated by SecOC for separate processing. This allows for flexible configuration of the SecOC function, reduces resource consumption for SecOC communication of all messages, and facilitates users to customize security based on their actual communication needs.

[0058] Adding SecOC information: The SecOC module performs SecOC calculation on the message that needs to add SecOC information, and returns the message after calculating the relevant information to the PDUR (ie, the routing module) for the next step of sending.

[0059] Verify SecOC information: The SecOC module verifies the received SecOC message and returns the verification result to PDUR for processing. PDUR performs corresponding operations on the verification result according to its own logic.

[0060] Report DTC: If a special error occurs during the operation of the SecOC module, a DTC error code can be generated according to the error level and fed back to the system software for easy query and processing.

[0061] According to the development method based on SecOC real vehicle communication of the embodiment of the present application, the key and message authentication code are obtained from the hardware security module, and the calculation function of the SecOC module is developed according to the key and message authentication code. After the calculation function of the SecOC module is developed, the SecOC module is compiled to obtain a library file so as to call the library file to realize encrypted communication in the vehicle. It is suitable for automobile network architecture and meets the function of SecOC. As a library file, it can be developed independently of other control units. After development, it can be fully embedded in the development environment of the control unit, and it can be more flexibly adapted to the development environment of different control units, which is convenient for the transplantation and development of different controllers. Therefore, it has low development difficulty, can be developed independently of the control unit, and is only developed around the SecOC function, which reduces the development capability standard. It is easy to transplant, and the library file compiled can be adapted to different control unit environments, and can be applied to different controllers after one development. The maintenance cost is reduced, and the library file can be separately maintained and upgraded under the premise of maintaining the unified interface, which reduces the maintenance cost.

[0062] In addition, the SecOC module can also perform CANID analysis and customize specific CANID messages for SecOC communication, which greatly reduces the consumption of communication resources. In addition, due to the form of an independent library, it is more flexible and low-cost in the later key replacement, maintenance and upgrade.

[0063] Figure 3 FIG. 1 is a structural block diagram of a development system based on SecOC real vehicle communication according to an embodiment of the present application. Figure 3 As shown, according to an embodiment of the present application, the development system based on SecOC real vehicle communication includes: an acquisition module 310, a function development module 320 and a library file generation module 330, wherein:

[0064] An acquisition module 310 is used to obtain a key and a message authentication code from a hardware security module;

[0065] A function development module 320, for developing a computing function of a SecOC module according to the key and the message authentication code;

[0066] The library file generating module 330 is used to compile the SecOC module after the computing function of the SecOC module is developed to obtain a library file, so that when the library file is called, encrypted communication in the vehicle can be realized.

[0067] According to the development system based on SecOC real vehicle communication of the embodiment of the present application, the key and message authentication code are obtained from the hardware security module, and the calculation function of the SecOC module is developed according to the key and message authentication code. After the calculation function of the SecOC module is developed, the SecOC module is compiled to obtain a library file so as to call the library file to realize encrypted communication in the vehicle. It is suitable for the automotive network architecture and meets the functions of SecOC. As a library file, it can be developed independently of other control units. After development, it can be fully embedded in the development environment of the control unit, and it can be more flexibly adapted to the development environment of different control units, which is convenient for the transplantation and development of different controllers. Therefore, it has low development difficulty, can be developed independently of the control unit, and is only developed around the SecOC function, which reduces the development capability standard. It is easy to transplant, and the library file compiled can be adapted to different control unit environments, and can be applied to different controllers after one development. The maintenance cost is reduced, and the library file can be separately maintained and upgraded under the premise of maintaining the unified interface, reducing the maintenance cost.

[0068] For the specific limitations of the development system based on SecOC real-vehicle communication, please refer to the limitations of the development method based on SecOC real-vehicle communication mentioned above, which will not be repeated here. The various modules of the above-mentioned development system based on SecOC real-vehicle communication can be implemented in whole or in part through software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0069] In one embodiment, a vehicle is provided, comprising: a development system based on SecOC real vehicle communication according to the above embodiment, the vehicle can obtain a key and a message authentication code from a hardware security module, and develop the calculation function of the SecOC module according to the key and the message authentication code. After the calculation function of the SecOC module is developed, the SecOC module is compiled to obtain a library file so as to call the library file to realize encrypted communication in the vehicle. It is applicable to the automotive network architecture and meets the function of SecOC. As a library file, it can be developed independently of other control units, and can be fully embedded in the development environment of the control unit after development, and can be more flexibly adapted to the development environment of different control units, which is convenient for the transplantation and development of different controllers. Therefore, it has low development difficulty, can be developed independently of the control unit, and is only developed around the SecOC function, which reduces the development capability standard. It is easy to transplant, and the library file compiled can be adapted to different control unit environments, and can be applied to different controllers after one development. The maintenance cost is reduced, and the library file can be separately maintained and upgraded under the premise of maintaining a unified interface, which reduces the maintenance cost.

[0070] In addition, other structures and functions of the vehicle according to the embodiment of the present application are known to ordinary technicians in the field and will not be elaborated here.

[0071] In one embodiment, a computer device is provided. Figure 4 This is a block diagram of the computer device provided in the embodiment of the present application, refer to Figure 4 The computer device includes a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the aforementioned development method embodiment based on SecOC real vehicle communication is implemented. For example, the following is performed: obtaining a key and a message authentication code from a hardware security module;

[0072] Develop the calculation function of the SecOC module based on the key and message authentication code;

[0073] After the computing function of the SecOC module is developed, the SecOC module is compiled to obtain a library file;

[0074] The library file is called to implement encrypted communication within the vehicle.

[0075] The embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and the processor implements the aforementioned development method embodiment based on SecOC real vehicle communication when executing the computer program. For example, the following is executed: obtaining a key and a message authentication code from a hardware security module;

[0076] Develop the calculation function of the SecOC module based on the key and message authentication code;

[0077] After the computing function of the SecOC module is developed, the SecOC module is compiled to obtain a library file;

[0078] The library file is called to implement encrypted communication within the vehicle.

[0079] The present application embodiment provides a computer program product, which includes instructions. When the instructions are executed, the method described in the embodiment of the present application is executed. For example, it can be executed Figure 1 The steps of the development method based on SecOC real-vehicle communication shown, for example, are performed: obtaining a key and a message authentication code from a hardware security module;

[0080] Develop the calculation function of the SecOC module based on the key and message authentication code;

[0081] After the computing function of the SecOC module is developed, the SecOC module is compiled to obtain a library file;

[0082] The library file is called to implement encrypted communication within the vehicle.

[0083] Those of ordinary skill in the art can understand that all or part of the processes in the methods for implementing the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0084] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0085] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the patent application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent application shall be subject to the attached claims.

Claims

1. A development method based on SecOC real vehicle communication, characterized in that: include: Obtain keys and message authentication codes from the hardware security module; Develop the calculation function of the SecOC module based on the key and message authentication code; After the computing function of the SecOC module is developed, the SecOC module is compiled to obtain a library file; The library file is called to implement encrypted communication within the vehicle.

2. The development method based on SecOC real vehicle communication according to claim 1 is characterized in that: The obtaining of a key and a message authentication code from a hardware security module comprises: The SecOC module presets the key in the hardware security module and uses the initialization interface in the hardware security module to perform key initialization management; When the key is modified, the SecOC module synchronizes the key update with the hardware security module by modifying the preset key.

3. The development method based on SecOC real vehicle communication according to claim 1 is characterized in that: The calling of the library file to realize encrypted vehicle communication includes: The SecOC module performs CANID analysis according to the message input by the serial communication interface layer of the vehicle; According to the analysis results, the messages that need to be calculated by SecOC are selected for separate processing. After the processing is completed, the processing results are returned to the routing module in the vehicle.

4. The development method based on SecOC real vehicle communication according to claim 1 is characterized in that: The calling of the library file to realize encrypted vehicle communication includes: The SecOC module performs SecOC calculation on the message to which SecOC information needs to be added; The calculation results are returned to the routing module in the vehicle.

5. The development method based on SecOC real vehicle communication according to claim 1 is characterized in that: The calling of the library file to realize encrypted vehicle communication includes: The SecOC module performs verification calculation on the received SecOC message and returns the verification result to the routing module in the vehicle, so that the routing module in the vehicle performs corresponding operation processing on the verification result.

6. The development method based on SecOC real vehicle communication according to claim 1 is characterized in that: Also includes: When an error occurs in the SecOC module during operation, a DTC error code is generated according to the error level, and the DTC error code is fed back.

7. The development method based on SecOC real vehicle communication according to any one of claims 1 to 6, characterized in that: The library file is a dynamic library file or a static library file.

8. A development system based on SecOC real vehicle communication, characterized in that: include: An acquisition module, used to obtain a key and a message authentication code from a hardware security module; A function development module, used to develop a computing function of the SecOC module according to the key and the message authentication code; The library file generation module is used to compile the SecOC module after the computing function of the SecOC module is developed to obtain a library file so that when the library file is called, encrypted communication in the vehicle can be realized.

9. A vehicle, characterized in that: include: A development system based on SecOC real vehicle communication according to claim 8.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the development method based on SecOC real-vehicle communication according to any one of claims 1-7 is implemented.

Images