A safety requirements integration method and system for autonomous driving systems

Abstract

The present invention discloses a method and system for integrating security requirements for an autonomous driving system. First, a list of network security requirements and a list of physical security requirements for the autonomous driving system are obtained. Then, a determination is made as to whether any network security requirement is completely identical to any physical security requirement. If they are completely identical, they are generated as identical security requirements. If they are not completely identical, the subject and object parts of the two security requirements are respectively identified to obtain the identified security requirements. Then, a determination is made as to whether the subjects of the identified security requirements have identical parts. If not, they are generated as independent security requirements. If identical parts exist, a determination is made as to whether the objects have identical parts. If identical parts exist, the two security requirements are generated as contradictory security requirements. Otherwise, they are generated as independent security requirements. The method of the present invention can quickly find the similarities, differences, and contradictions between network security requirements and physical security requirements, thus facilitating the safety assessment of autonomous vehicles.

Description

Technical Field

[0001] The present invention belongs to the field of autonomous driving technology, and specifically relates to a safety requirements integration method and system for an autonomous driving system. Background Art

[0002] Autonomous vehicles and autonomous driving technology have become increasingly popular topics, and with them comes the issue of autonomous vehicle safety. The safety of autonomous vehicles encompasses both physical safety and cybersecurity. To clarify the safety of autonomous vehicles, we need to redefine the safety requirements for autonomous vehicles by referencing two different standards: ISO 26262 and SAE J3061, both traditional road vehicle safety standards. To ensure the safety of autonomous vehicles, both physical and cybersecurity must be analyzed together. While the international standards ISO 26262 and SAE J3061 discuss the physical safety, cybersecurity, and even the manufacturing lifecycle of traditional road vehicles in detail, they do not establish specific safety standards or guidelines for autonomous vehicles.

[0003] Different drivers' control capabilities over autonomous vehicles can lead to different risk profiles. Depending on the risk profile, the corresponding safety requirements will vary accordingly. Currently, there are a variety of risk analysis methods available internationally, such as EVITA, US2, STPA, VERA, RACE, and CARL. EVITA and STPA are physical safety analysis methods that can determine physical safety requirements, while VERA, RACE, and CARL are network security analysis methods that can determine network security requirements. However, there is currently no analytical method or tool that can examine the physical and network security requirements of autonomous vehicles after risk analysis and identify similarities, differences, or conflicts between these different security requirements. Therefore, the present invention proposes a method for integrating security requirements for autonomous vehicles to identify similarities and differences between network and physical security requirements. This approach can help identify internal vulnerabilities and key risk points within the autonomous vehicle itself. Conflicting security requirements can compromise the autonomous vehicle's operating system and even cause loss of control, leading to serious traffic accidents. Therefore, identifying similarities, differences, and conflicts between security requirements is particularly important. Summary of the Invention

[0004] In response to the above technical requirements, the present invention proposes a safety requirement integration method and system for autonomous driving systems, which can meet the needs of finding similarities and differences in different safety requirements and obtain the similarities, differences and contradictions of the safety requirements of autonomous driving vehicles.

[0005] In order to achieve the above object, the present invention adopts the following technical solutions:

[0006] A safety requirements integration method for an autonomous driving system includes the following steps:

[0007] Step 1: Obtain a list of network security requirements and a list of physical security requirements for the autonomous driving system;

[0008] Step 2: Determine whether any network security requirement in the network security requirement list is identical to any physical security requirement in the physical security requirement list. If they are identical, generate them as identical security requirements. If not, proceed to step 3.

[0009] Step 3: Identify the subject and object of the network security requirements and physical security requirements to obtain the identified security requirements.

[0010] Step 4: Determine whether there are identical parts in the subject of the security requirements identified in step 3. If there are identical parts, proceed to step 5; otherwise, generate an independent security requirement.

[0011] Step 5: Determine whether there are identical parts in the object. If so, generate the two security requirements as conflicting security requirements; otherwise, generate them as independent security requirements.

[0012] Step 6: Repeat steps 2 to 5 until all network security requirements in the network security requirements list and all physical security requirements in the physical security requirements list are judged; finally, all independent security requirements, conflicting security requirements, and identical security requirements are obtained.

[0013] Preferably, in step 1, the VERA analysis method is used to obtain network security requirements, and the STPA analysis method is used to obtain physical security requirements.

[0014] Preferably, in step 1, the network security requirements and physical safety requirements of the autonomous driving system are first obtained, and are written into txt format files respectively. The text in the txt file is read as the corresponding ACSII code and then the data is inserted one by one into the initialized linked list to obtain the network security requirements linked list and the physical safety requirements linked list.

[0015] The present invention also discloses a safety requirement integration system for an autonomous driving system, specifically comprising: a safety requirement data acquisition module, a linked list generation module, an overall comparison module, an identification module, a subject part comparison module, an object part comparison module, an independent safety requirement database, a conflicting safety requirement database, and an identical safety requirement database;

[0016] The security requirement data acquisition module is used to obtain the network security requirements and physical security requirements of the autonomous driving system;

[0017] The linked list generation module is used to insert the network security requirements and physical security requirements data obtained by the security requirements data acquisition module into their respective corresponding linked lists to obtain a network security requirements linked list and a physical security requirements linked list;

[0018] The overall comparison module is used to compare each bit of data in the network security requirement list with the data in the physical security requirement list one by one. If they are exactly the same, the two security requirements are stored in the same security requirement database. If they are not exactly the same, they are transferred to the identification module.

[0019] The identification module is used to identify the subject and object parts of the network security requirements and the physical security requirements to obtain the identified security requirements;

[0020] The subject part comparison module is used to compare whether the subject parts of the marked security requirements have the same parts. If there are the same parts, the process is transferred to the object part comparison module. Otherwise, the two security requirements are stored in an independent security requirement database.

[0021] The object part comparison module is used to compare whether there are identical parts in the objects of the marked security requirements. If there are identical parts, the two security requirements are stored in the conflicting security requirements database; otherwise, the two security requirements are stored in the independent security requirements database.

[0022] Compared with the prior art, the present invention has the following beneficial effects:

[0023] The method of the present invention can identify similarities, differences, and conflicts between network security requirements and physical security requirements. It facilitates the safety assessment of autonomous vehicles and facilitates the research of autonomous vehicles and related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a flow chart of the method described in an embodiment of the present invention.

[0025] Figure 2 This is the result of the exact same security requirements as in Example 1 of the present invention.

[0026] Figure 3 This is the result of the different security requirements of Example 1 of the present invention.

[0027] Figure 4 This is the identification result of the non-identical security requirements in Example 1 of the present invention.

[0028] Figure 5 This is the result of the independent security requirements and conflicting security requirements of Example 1 of the present invention. DETAILED DESCRIPTION

[0029] Specific embodiments of the present invention are given below. It should be noted that the present invention is not limited to the following specific embodiments, and all equivalent changes made on the basis of the technical solution of this application fall within the protection scope of the present invention.

[0030] Example 1

[0031] This embodiment proposes a safety requirements integration method for autonomous driving systems, which is used to identify the similarities and differences between network risk analysis and physical risk analysis, so as to understand the internal vulnerabilities of the autonomous driving vehicle itself and the key points that are prone to risks through the similarities and differences. Figure 1 As shown, the method specifically includes the following steps:

[0032] Step 1: Obtain the cybersecurity requirements list and physical security requirements list of the autonomous driving system, specifically:

[0033] The data source for the autonomous driving system in this embodiment is the in-vehicle network system described in the document "J. Cui and B. Zhang, "VeRA: ASimplified Security Risk Analysis Method for Autonomous Vehicles," in IEEE Transactions on Vehicular Technology, vol. 69, no. 10, pp. 10494-10505, Oct. 2020, doi: 10.1109 / TVT.2020.3009165." This embodiment uses the VERA analysis method to perform a risk analysis on the network layer of the autonomous vehicle's in-vehicle network system, and the STPA analysis method to perform a risk analysis on the physical layer of the autonomous vehicle.

[0034] After obtaining the security requirements, they are written into txt format files respectively, the text in the txt files is read into the corresponding ACSII code and then the data is inserted one by one into the initialized linked list to obtain the network security requirements linked list and the physical security requirements linked list.

[0035] Step 2: Determine whether any network security requirement in the network security requirement list is exactly the same as any physical security requirement in the physical security requirement list. If they are exactly the same, generate them as identical security requirements. If they are not exactly the same, execute step 3. In the present invention, "identical" means that the expression patterns of the two security requirements are exactly the same.

[0036] Figure 2 The following are the same security requirements generated in this embodiment: Figure 3 The following are the different security requirements generated by this embodiment: Figure 3Those marked with "1" are network security requirements, and those marked with "2" are physical security requirements.

[0037] Step 3: Identify the subject and object of network security requirements and physical security requirements respectively, mark which are the subjects and which are the objects, and facilitate semantic recognition to obtain the identified security requirements. Figure 4 The following are the security requirements after identification in this embodiment: Figure 4 Those marked with "1" are network security requirements, and those marked with "2" are physical security requirements.

[0038] Step 4: Determine whether the subjects of the security requirements identified in step 3 contain the same parts, that is, whether the subjects contain the same words. For example, "OC" and "Software of OC" are considered to have the same parts. If they do, proceed to step 5. Otherwise, generate them as independent security requirements.

[0039] Step 5: Determine whether there are identical parts in the object, that is, whether there are identical words in the object. For example, "Camera data is transferred to OC after damage determination start engine and motor." and "Camera data is transferred to OC start engine and motor." are considered to have identical parts in the object. If so, the two safety requirements are generated as conflicting safety requirements; otherwise, they are generated as independent safety requirements.

[0040] Step 6: Repeat steps 2 to 5 until all network security requirements in the network security requirements list and all physical security requirements in the physical security requirements list are judged; finally, all independent security requirements, conflicting security requirements, and identical security requirements are obtained.

[0041] Figure 5 The left side of the file processing window shows the results of all conflicting security requirements, and the right side of the window shows the results of all independent security requirements. Figure 5 Those marked with "1" are network security requirements, and those marked with "2" are physical security requirements. Figure 2 The results for all the same security requirements are shown. It can be seen that the method of the present invention can quickly find the similarities, differences and contradictions between network security requirements and physical security requirements.

[0042] Example 2

[0043] This embodiment discloses a safety requirement integration system for an autonomous driving system, including: a safety requirement data acquisition module, a linked list generation module, an overall comparison module, an identification module, a subject part comparison module, an object part comparison module, an independent safety requirement database, a conflicting safety requirement database, and an identical safety requirement database.

[0044] Among them, the security requirement data acquisition module is used to obtain the network security requirements and physical security requirements of the autonomous driving system;

[0045] The linked list generation module is used to insert the network security requirements and physical security requirements data obtained by the security requirements data acquisition module into their respective corresponding linked lists to obtain the network security requirements linked list and the physical security requirements linked list; reading the security requirements txt file into the linked list is achieved through the FileRead function.

[0046] The overall comparison module is used to compare each bit of data in the network security requirement list with the data in the physical security requirement list. If they are identical, the two security requirements are stored in the same security requirement database. If they are not identical, they are transferred to the identification module.

[0047] The identification module is used to identify the subject and object parts of network security requirements and physical security requirements to obtain the identified security requirements;

[0048] The subject part comparison module is used to compare whether the subject parts of the marked security requirements have the same parts. If there are the same parts, the process will be transferred to the object part comparison module. Otherwise, the two security requirements will be stored in an independent security requirement database.

[0049] The object part comparison module is used to compare whether there are identical parts in the objects of the marked security requirements. If there are identical parts, the two security requirements are stored in the conflicting security requirements database; otherwise, the two security requirements are stored in the independent security requirements database.

Claims

1. A safety requirements integration method for an autonomous driving system, characterized in that: The following steps are involved: Step 1: Obtain a list of network security requirements and a list of physical security requirements for the autonomous driving system; Step 2: Determine whether any network security requirement in the network security requirement list is identical to any physical security requirement in the physical security requirement list. If they are identical, generate them as identical security requirements. If not, proceed to step 3. Step 3: Identify the subject and object of the network security requirements and physical security requirements to obtain the identified security requirements. Step 4: Determine whether there are identical parts in the subject of the security requirements identified in step 3. If there are identical parts, proceed to step 5; otherwise, generate an independent security requirement. Step 5: Determine whether there are identical parts in the object. If so, generate the two security requirements as conflicting security requirements; otherwise, generate them as independent security requirements. Step 6: Repeat steps 2 to 5 until all network security requirements in the network security requirements list and all physical security requirements in the physical security requirements list are judged; finally, all independent security requirements, conflicting security requirements, and identical security requirements are obtained.

2. The safety requirements integration method for an autonomous driving system according to claim 1, wherein: In step 1, the VERA analysis method is used to obtain network security requirements, and the STPA analysis method is used to obtain physical security requirements.

3. The safety requirements integration method for an autonomous driving system according to claim 1, wherein: In step 1, the network security requirements and physical safety requirements of the autonomous driving system are first obtained, and are written into txt format files respectively. The text in the txt file is read as the corresponding ACSII code and then the data is inserted one by one into the initialized linked list to obtain the network security requirements linked list and the physical safety requirements linked list.

4. A safety requirements integration system for autonomous driving systems, characterized by: include: Security requirement data acquisition module, linked list generation module, overall comparison module, identification module, subject part comparison module, object part comparison module, independent security requirement database, conflicting security requirement database and identical security requirement database; The security requirement data acquisition module is used to obtain the network security requirements and physical security requirements of the autonomous driving system; The linked list generation module is used to insert the network security requirements and physical security requirements data obtained by the security requirements data acquisition module into their respective corresponding linked lists to obtain a network security requirements linked list and a physical security requirements linked list; The overall comparison module is used to compare each bit of data in the network security requirement list with the data in the physical security requirement list one by one. If they are exactly the same, the two security requirements are stored in the same security requirement database. If they are not exactly the same, they are transferred to the identification module. The identification module is used to identify the subject and object parts of the network security requirements and the physical security requirements to obtain the identified security requirements; The subject part comparison module is used to compare whether the subject parts of the marked security requirements have the same parts. If there are the same parts, the process is transferred to the object part comparison module. Otherwise, the two security requirements are stored in an independent security requirement database. The object part comparison module is used to compare whether there are identical parts in the objects of the marked security requirements. If there are identical parts, the two security requirements are stored in the conflicting security requirements database; otherwise, the two security requirements are stored in the independent security requirements database.

Images